Re: Patch for rc.conf(8) man page
The existing text, Create and edit a _new_ rc.conf.local file seems fine to me - man pages are generally non-verbose - if copying was intended, the manual would have said so. Disagree. Create and edit... is ambiguous. I can create a new file by copying an old file and often do so. If you want the new file start out empty then say so. We strongly suggest you do not alter .Nm rc.conf . Instead, create an empty file named .Nm rc.conf.local . Edit the new file ... blah blah blah
Re: hostname.if(5) clarification
To pass a line directly to ifconfig and prevent it from being
interpreted as a packed format, use !ifconfig \$if flags.
Yes.
(I think I may change my files to !ifconfig ... format
now, it's ugly but it will avoid errors; not least because
then I can use /prefix notation rather than netmasks).
Yes. I'm switching to !ifconfig for everything but trivial addresses.
How about a minimal change to hostname.* processing that adds a keyword used
to pass the rest of the line to ifconfig. Minimal change that is, IMHO,
less obnoxious that typing !ifconfig \$if. Maybe something like
pass ifconfig args for interface
--- netstartSun Dec 11 13:31:14 2011
+++ netstart.newTue Nov 27 10:57:27 2012
@@ -79,6 +79,9 @@
!*) # parse commands
cmd=${af#*!} ${name} ${mask} ${bcaddr} ${ext1} ${ext2}
;;
+ pass)
+ cmd=ifconfig $if ${name} ${mask} ${bcaddr} ${ext1}
${ext2}
+ ;;
dhcp)
[ $name = NONE ] name=
[ $mask = NONE ] mask=
Re: Threads related SIGSEGV in random.c
On Sep 18, 2012, at 3:27 PM, Paul Irofti p...@irofti.net wrote: Because most of the guys in the hackingroom didn't get this, the reference is to a book named 'American Gods' by Neil Gaimen. Wednesday is Odin from the Norse Sagas in that book. Gaiman, not Gaimen. http://www.neilgaiman.com/ Pretty awesome reference if you ask me. I enjoyed it a lot! nod.
Re: libpthread: don't context switch to yourself
On Jul 2, 2011, at 3:06 PM, Philip Guenther wrote: In libpthread, if the scheduler picks the current thread as the next to run, it still does the full save+restore of errno, FPU, and regs, saving them and then restoring the same values again. That's kinda silly, so jump around that if switching to the current thread. oks? Looks reasonable to me. I have not looked at all the assembler code to see if there are side effects of task switching to yourself that some other part of the code depends upon. /\/\arc
Re: pf.conf, comments and continuation lines
so I would be happier to have it in the text rather than as an example if it can be done clearly, but I haven't managed it... For pf and pf like code: Notice: Line continuation processing occurs BEFORE comment removal. For ksh and ksh like code: Notice: Comments are removed BEFORE line continuation processing. Without an example of each, though, I don't know if the repercussions will be understood. /\/\arc
Re: document ldapd schema files
I've always thought Bob's comment from 2/11/2005, was worth adding to quotes, but it might be a bit long. Bob might even remember why I say that. I remember. Your response was priceless /\/\arc
Re: Patch for bogus pointer arithmetic in adw(4)
FWIW, the original UNIX had bcopy. Which makes me an ignorant idiot. So it goes. /\/\arc
