Re: fw_update
On 2024-05-02 21:25:00, Stuart Henderson wrote: You have an old fw_update(1) manual lying around which should be removed. It moved to fw_update(8). "Moved"? And yet another BTW: https://man.openbsd.org/OpenBSD-7.5/ seems to be forgotten. Regards Harri
Re: panic: unix: lock not held
On Fri, 03 May 2024 04:29:24 +0200, Amit Kulkarni wrote: > > Unable to boot to a prompt. How do I recover by booting an older kernel? > There is no /obsd to try out. Keep current /bsd as /obsd in the case of snapshot migth work only if you're updating quite oftne, otherwise the userland migth not work with old kernel due to changes in syscalls for example. -- wbr, Kirill
Re: Relayd forward to multiple ports on one target host?
On 2024-05-02 07:32, Manuel Giraud wrote:
table { 127.0.0.1 }
table { 127.0.0.1 }
table { 127.0.0.1 }
On 2024-05-02 07:02, Zé Loff wrote:
table { 10.17.16.10 }
table { 10.17.16.10 }
table { 10.17.16.10 }
Multiple tables - I didn't see that!
I'm going with something like this to keep things simple for myself:
table { 192.0.2.99 }
table { 192.0.2.99 }
table { 192.0.2.99 }
Thank you,
Paul
Re: fw_update
On 2024-05-03, Harald Dunkel wrote: > On 2024-05-02 21:25:00, Stuart Henderson wrote: >> >> You have an old fw_update(1) manual lying around which should be >> removed. It moved to fw_update(8). >> > > "Moved"? Yes. It used to be in section 1, it has moved to section 8. Unless you remove the extra file, man(1) will by default show the obsolete section 1 manual.
Re: panic: unix: lock not held
On Fri, May 3, 2024 at 1:15 AM Stuart Henderson wrote: > On 2024-05-03, Amit Kulkarni wrote: > > Hi all, > > Referring to the existing email chain on bugs@ > > https://marc.info/?l=openbsd-bugs&m=171468519914343&w=2 > > > > Unable to boot to a prompt. How do I recover by booting an older kernel? > > There is no /obsd to try out. > > sysupgrade doesn't save old kernels (and it would be problematic if > it did, space on / often gets tight) so you'll need to find one from > elsewhere (openbsd.cs.toronto.edu and ftp.hostserver.de carry old > snapshots in an archive directory) and install it using either your > existing bsd.rd (if it works) or by booting from a downloaded install > img/iso or network boot a downloaded bsd.rd. > > Thanks a lot, was able to recover just by using bsd.rd and downloading all new kernels first. Now going to download a fresh set of binaries to keep them all in sync. Amit
Re: Relayd forward to multiple ports on one target host?
Paul Pace writes:
> On 2024-05-02 07:32, Manuel Giraud wrote:
>> table { 127.0.0.1 }
>> table { 127.0.0.1 }
>> table { 127.0.0.1 }
>
> On 2024-05-02 07:02, Zé Loff wrote:
>> table { 10.17.16.10 }
>> table { 10.17.16.10 }
>> table { 10.17.16.10 }
>
> Multiple tables - I didn't see that!
Yes, AFAIU, a table is *not* just an alias for say 192.0.2.99. It is
the structure that maintain the link between a protocol an a relay
(surely this explanation is not quite right: you better read the man
pages ;)
--
Manuel Giraud
