FreeBSD 5.3-BETA2 live filesystem CD problems

From: Peter Jeremy <PeterJeremy_at_optushome.com.au>
Date: Thu, 2 Sep 2004 18:21:24 +1000
I've been doing some experiments with the fixit shell from the live
filesystem CD and found a few problems.  These were all picked up on
the Alpha but I believe most are generic problems.

1) Ctrl-C breaks into sysinstall rather than killing the running process.

2) Running fsck reports:
Fixit# fsck /dev/da0[ade]
fstab: /etc/fstab:0: No such file or directory
fstab: /etc/fstab:0: No such file or directory
fsck: exec fsck_4.2bsd for /dev/da0a in /sbin:/usr/sbin: No such file or directory
fstab: /etc/fstab:0: No such file or directory
fstab: /etc/fstab:0: No such file or directory
fsck: exec fsck_4.2bsd for /dev/da0d in /sbin:/usr/sbin: No such file or directory
fstab: /etc/fstab:0: No such file or directory
fstab: /etc/fstab:0: No such file or directory
fsck: exec fsck_4.2bsd for /dev/da0e in /sbin:/usr/sbin: No such file or directory
  Explicitly using fsck_ffs works OK.

3) "mount 192.168.123.200:/back /mnt" reports:
boot_crunch: nfs not compiled in
usage: boot_crunch <prog> <args> ..., where <prog> is one of:
 hostname pwd rm sh -sh test [ cpio dhclient fsck_ffs ifconfig mount_nfs newfs
 route rtsol slattach tunefs camcontrol find minigzip gzip gunzip zcat sed arp
 ppp sysinstall usbd usbdevs boot_crunch
Fixit# 
   Again, using /sbin/mount_nfs works OK.

3) tar doesn't work.  tar is a symlink to /usr/bin/bsdtar which doesn't
   exist.  The symlink needs to be relative rather than absolute.

-- 
Peter Jeremy
Received on Thu Sep 02 2004 - 06:21:26 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:10 UTC