SMP oddity

2000-03-17 Thread Matt Heckaman
Morning, Some of you will probably remember my request for opinions about SMP performance in 3.4-stable, and I went with it - I'm quite happy at the result as well, it runs beautifully. One very strange thing I've noticed though, from dmesg: CPU: Pentium III (686-class CPU) Origin = "GenuineIn

Re: 4.0

2000-03-17 Thread Kris Kennaway
On Thu, 16 Mar 2000, David Bushong wrote: > > Well, I couldn't replicate this when I tried (under several different > > conditions). The only bug I found with compiling without crypto support > > was in tcpdump. Perhaps you have a stale /usr/obj? > > > I got this exact behavior from having only

Re: 3 to 4 Upgrade, missing crypto bugs, and random thoughts

2000-03-17 Thread Kris Kennaway
On Fri, 17 Mar 2000, Tom Legg wrote: > I've reproduced the missing crypto bug when compiling a kernel. > I think I've isolated it. If you try to build a custom kernel with > IPSEC options the make will bomb. This will happen even after the > current UPDATING instructions are complete. You

3 to 4 Upgrade, missing crypto bugs, and random thoughts

2000-03-17 Thread Tom Legg
So having pushed myself through two machine upgrades in the last couple of days I've reproduced the missing crypto bug when compiling a kernel. I think I've isolated it. If you try to build a custom kernel with IPSEC options the make will bomb. This will happen even after the current U

Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions

2000-03-17 Thread Daniel C. Sobral
Marcel Moolenaar wrote: > > You can make a kernel like this: > cd /usr/src > make buildkernel KERNEL=YOUR_KERNEL_HERE > > The new `buildkernel' and `installkernel' targets make use of the tools > build by buildworld and effectively works around the bootstrap problem. IIRC, /etc/

Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions

2000-03-17 Thread Daniel C. Sobral
Warner Losh wrote: > > When I tried the installkernel it installed things as /YOUR_KERNEL_HERE > > I'll have to update things. Well, for people who like to build multiple kernels like me, the above works... :-) Alas, I have kernel="/DCS" in my /boot/loader.conf. -- Daniel C. Sobral

Re: Desperate help upgrading from 3.2-R > 3.4-S

2000-03-17 Thread Jim Weeks
This may be your problem. You either need to specify all, or each one individually. I have had trouble using the all option > src-all > src-crypto > src-eBones > src-secure You shouldn't need to use this in 3.x-stable > USA_RESIDENT= YES It is not necessary to upgrade from 3.2 if y

Re: Desperate help upgrading from 3.2-R > 3.4-S

2000-03-17 Thread Kris Kennaway
On Fri, 17 Mar 2000, Lester A. Mesa wrote: > and while running the make buildworld is where I get the following error: > > ===> share/doc/usd/13.viref > sed -e\ 's:\(\.so[\ \ ][\ > ]*\)\(vi.ref\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/ > docs/USD.doc/vi.ref/\2:' -e\ 's:\(

Re: Dynamic linker bug in 3.4-RELEASE (I think)

2000-03-17 Thread Tom
On Fri, 17 Mar 2000, Randall Hopper wrote: > I have a small program I wrote that uses sigwait and takes about 1 second > to complete. > > If I run it over-and-over many times repeatedly, occasionally the dynamic > linker will fail to resolve the "sigwait" symbol. > > Here is how I run it in t

Missing man pages: ld.so, sigwait()

2000-03-17 Thread Randall Hopper
sigwait is available but there's no man page. Also I don't find one for ld.so, though it's mentioned in the ldd man page. Worth a PR? Randall # grep sigwait /usr/include/signal.h int sigwait __P((const sigset_t *, int *)); int sigwaitinfo __P((cons

Dynamic linker bug in 3.4-RELEASE (I think)

2000-03-17 Thread Randall Hopper
I have a small program I wrote that uses sigwait and takes about 1 second to complete. If I run it over-and-over many times repeatedly, occasionally the dynamic linker will fail to resolve the "sigwait" symbol. Here is how I run it in tcsh: while (1) hw4-1 > /dev/null echo