I've been tracking each of -STABLE & -CURRENT for a while now, so
it's been almost a year since I tried the -STABLE -> -CURRENT upgrade
path.  Still, I was a bit skeptical when someone on the #FreeBSD
channel at irc.sage-members.org indicated that the "make installworld"
was failing for him, typically with /bin/sh dying in some strange way.

In an effort to get a better idea of what any issues might be,
therefore, after I built today's -STABLE (on slice 1) and today's
-CURRENT (on slice 4), I did the following on my SMP (2x866MHz PIII)
build machine:

* cloned slice 1 to slice 3 (dump|restore ad0s1a -> ad0s3a & ad0s1e ->
  ad0s3e, followed by tweaking etc/fstab on ad0s3a & changing the
  obj symlink on ad0s3e to point to /common/S3/obj instead of

* reboot from slice 3 (multi-user mode); verify that I was running 4.6-S
  as of this morning.

* rm -fr /usr/obj/usr/src

* rm -fr /usr/src/*

* cd /usr && cvs -d /cvs/freebsd checkout src [/cvs/freebsd is the
  FreeBSD portion of my local CVS repository; my ~/.cvsrc has "-P" as an
  automatic command-line flag for the "checkout" command.]

* cd src/i386/conf && ln -s /common/local/src/kernels/current/FREEBEAST .

* whoami && mount && cd /usr/src && uname -a && date && make -j8
  buildworld && date && make kernel KERNCONF=FREEBEAST && date
  [This proceeded OK up to the "make kernel," at which point I was
  reminded that I should only go so far as "make buildkernel" before
  copying /sys/i386/conf/GENERIC.hints to /boot/device.hints.]

* (per above) cp sys/i386/conf/GENERIC.hints /boot/device.hints &&
  date && make kernel KERNCONF=FREEBEAST && date

* reboot (single-user mode)
  Now, at this step, I see something a bit odd:

Console: serial port
BIOS drive A: is disk0
BIOS drive C: is disk1
BIOS 639kB/523200kB available memory

FreeBSD/i386 bootstrap loader, Revision 1.1
([EMAIL PROTECTED], Sun Aug 11 09:29:25 PDT 2002)
Loading /boot/defaults/loader.conf 
Warning: syntax error on file /boot/device.hints
machine         i386
Warning: syntax error on file /boot/loader.conf
/boot/kernel/kernel text=0x237e0c data=0x35db4+0x6f72c syms=[0x4+0x36820+0x4+0x421d1]

* fsck -p

* mount -u /

* mount -a

* cd /usr/src

* adjkerntz -i

* mergemaster -p

* make installworld

... and this step appears to fail to terminate in a useful manner:  I
get as far as:

===> usr.bin/biff
install -s -o root -g wheel -m 555   biff /usr/bin
install -o root -g wheel -m 444 biff.1.gz  /usr/share/man/man1
===> usr.bin/brandelf
install -s -o root -g wheel -m 555   brandelf /usr/bin
install -o root -g wheel -m 444 brandelf.1.gz  /usr/share/man/man1
===> usr.bin/bzip2
install -s -o root -g wheel -m 555   bzip2 /usr/bin
install -o root -g wheel -m 444 bzip2.1.gz  /usr/share/man/man1
/usr/share/man/man1/bunzip2.1.gz -> /usr/share/man/man1/bzip2.1.gz
/usr/share/man/man1/bzcat.1.gz -> /usr/share/man/man1/bzip2.1.gz
===> usr.bin/bzip2/doc
install-info --quiet  --defsection="Programming & development tools."  --defentry=  
bzip2.info /usr/share/info/dir
install -o root -g wheel -m 444  bzip2.info.gz /usr/share/info
/usr/bin/bunzip2 -> /usr/bin/bzip2
/usr/bin/bzcat -> /usr/bin/bzip2
===> usr.bin/c89
install -s -o root -g wheel -m 555   c89 /usr/bin
install -o root -g wheel -m 444 c89.1.gz  /usr/share/man/man1
===> usr.bin/calendar
insptall -o root -g iwheel -m 444  /ud 
~z*M~3~W~IK~~k~n%C19K~=c~~1+=K#rB*J~iS~jj~M+IC){I)v~V[{){11~IKv  }s!c    

and the machine appears at this point to be non-responsive.  I had
cut/pasted the above from the serial console; seeing no way to get
the machine to wake up, I'll hit the reset button... and I find
that after "boot -s" I see:

Type '?' for a list of commands, 'help' for more detailed help.
OK boot -s
/boot/kernel/acpi.ko text=0x2e29c data=0x1804+0x6e0 syms=[0x4+0x50b0+0x4+0x6913]

where things just sit.  (I.e., the "spinner" doesn't spin.)

OK; I hit the magic reset button, then hit "space" soon enough to
intercept the attempt to load /boot/loader from slice 3, and told it
to load the one from slice 1, boot single-user, and I'm doing a "fsck -p"
as I type.

OK; I brought it back up under today's -STABLE, and looking at the typescript
file, I see that it ends thusly:

===> usr.bin/cap_mkdb
install -s -o root -g wheel -m 555   cap_mkdb /usr/bin
install -o root -g wheel -m 444 cap_mkdb.1.gz  /usr/share/man/man1
===> usr.bin/catman
install -s -o root -g wheel -m 555   catman /usr/bin
install -o root -g wheel -m 444 catman.1.gz  /usr/share/man/man1
===> usr.bin/chat
install -s -o root -g wheel -m 555   chat /usr/bin
install -o root -g wheel -m 444 chat.8.gz  /usr/share/man/man8
===> usr.bin/checknr
install -s -o root -g wheel -m 555   checknr /usr/bin
install -o root -g wheel -m 444 checknr.1.gz  /usr/share/man/man1
===> usr.bin/chflags
install -s -o root -g wheel -m 555   chflags /bin
install -o root -g wheel -m 444 chflags.1.gz  /usr/share/man/man1
===> usr.bin/chpass
[ ! -e /usr/bin/chpass ] ||  chflags noschg /usr/bin/chpass || true
*** Signal 12

Stop in /usr/src/usr.bin/chpass.
*** Error code 1

Stop in /usr/src/usr.bin.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

So I get the impression that folks who are complaining about the shell
getting a SIGSYS probably aren't hallucinating (about that, anyway), and
to the extent that there's a (non-recovered) mistake in the procedure I
followed, perhaps the effected folks are doing something similar.

At least my -CURRENT built under -CURRENT (same kernel config file)
seems OK....

David H. Wolfskill                              [EMAIL PROTECTED]
To paraphrase David Hilbert, there can be no conflicts between Microsoft
and the discipline of systems administration, since they have nothing in

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to