On Fri, Nov 14, 2003 at 06:38:28AM +1100, Bruce Evans wrote: > On Thu, 13 Nov 2003, John Hay wrote: > > > Is it ok to run a new kernel (after the statfs changes) and older > > programs? I thought so from what i gathered out of the commit > > messages, but my test box doesn't like it at all... Well except > > if something else broke stuff: > > I have no problems with a current kernel and an old world. > > > ###### > > ... > > Mounting root from ufs:/dev/da0s1a > > pid 50 (sh), uid 0: exited on signal 12 > > Enter full pathname of shell or RETURN for /bin/sh: > > # ls > > pid 56 (ls), uid 0: exited on signal 12 > > Bad system call > > # > > ###### > > Maybe you don't have old programs. Unfortunately, even /bin/sh is > affected by the changes (it has a reference to fstatfs). I'm pretty sure it is old binaries because they work with my old kernel: beast# ls -l /bin/*sh* /boot/kernel.work/kernel /boot/kernel/kernel -r-xr-xr-x 2 root wheel 879252 Nov 11 14:52 /bin/csh -r-xr-xr-x 1 root wheel 751752 Nov 11 14:52 /bin/sh -r-xr-xr-x 2 root wheel 879252 Nov 11 14:52 /bin/tcsh -r-xr-xr-x 1 root wheel 2673454 Nov 3 09:17 /boot/kernel.work/kernel -r-xr-xr-x 1 root wheel 2758305 Nov 13 09:01 /boot/kernel/kernel The binaries work just fine with kernel.work but not with kernel. Maybe I should try a few other things, like a UP kernel. Luckily the old reboot still works on the new kernel. :-) John -- John Hay -- John.Hay_at_icomtek.csir.co.za / jhay_at_FreeBSD.orgReceived on Thu Nov 13 2003 - 12:14:30 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:28 UTC