Two Intel E31220L 9.0-Stable systems, 'kern.random' missing on one?

2012-12-03 Thread Karl Pielorz
Hi, I have two SuperMicro E31220L based systems - both had identical /etc/sysctl.conf - I then shifted them from 9.0-R to 9.0-Stable (as of 2012/12/03). Now I've noticed of them complains at boot time that a bunch of OID's are missing - and sure enough: sysctl kern.random sysctl:

$* and $@ exhibit same behaviour - those of $*

2012-12-03 Thread rank1seeker
I've noticed this under 9.0-RELEASE-p5 #!/bin/sh # ftest_dot () { local i for i in $* { echo $i } } ftest_monkey () { local i for i in $@ { echo $i } } echo ftest_dot one 'spaced

Re: $* and $@ exhibit same behaviour - those of $*

2012-12-03 Thread rank1seeker
Looks fine to me. Try quoting $@ in ftest_monkey. -Garrett Yes, it did a trick. That tiny detail. Thanks ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to

Re: $* and $@ exhibit same behaviour - those of $*

2012-12-03 Thread Bryan Drewery
On 12/3/2012 11:09 AM, rank1see...@gmail.com wrote: I've noticed this under 9.0-RELEASE-p5 #!/bin/sh # ftest_dot () { local i for i in $* { echo $i } } ftest_monkey () { local i for i in $@

Missing quote in comment in 8.3 9.0 9.1RC2 etc/sendmail/freebsd.mc

2012-12-03 Thread Julian H. Stacey
Hi hack...@freebsd.org There is a missing double quote in 8.3 9.0 9.1RC2 src/etc/sendmail/freebsd.mc 8.2-RELEASE earlier are OK. Here's a diff -c to .mc The diff is not to fix it, but to help generate a freebsd.cf to understand the difference. The patch for a fix would befar more trivial

Re: Two Intel E31220L 9.0-Stable systems, 'kern.random' missing on one?

2012-12-03 Thread Konstantin Belousov
On Mon, Dec 03, 2012 at 03:11:21PM +, Karl Pielorz wrote: Hi, I have two SuperMicro E31220L based systems - both had identical /etc/sysctl.conf - I then shifted them from 9.0-R to 9.0-Stable (as of 2012/12/03). Now I've noticed of them complains at boot time that a bunch of OID's

[PATCH] Bugs in DTrace debug locking code

2012-12-03 Thread Ryan Stone
DTrace has an unused logging facility built-in. The logging is intended to be safe to be called from the handler of a DTrace probe (what DTrace calls probe context). Because a DTrace probe could be enabled almost anywhere in the kernel, this means that it can't use standard FreeBSD