Date: Sat, 30 Mar 1996 09:04:39 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-current@FreeBSD.org (FreeBSD-current users) Cc: handy@sxt2.space.lockheed.com (Brian N. Handy) Subject: Re: Fixit Floppy Broken? Message-ID: <199603300804.JAA03375@uriah.heep.sax.de> In-Reply-To: <Pine.ULT.3.91.960329150032.18461A-100000@sxt2.space.lockheed.com> from "Brian N. Handy" at Mar 29, 96 03:05:24 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As Brian N. Handy wrote: > I had hoped we could fix this with the fixit floppy, but I'm having bad > luck with these. The fixit floppy seems broken. I can boot from it This is a known problem: gzipp'ed executables are broken in -current, but nobody has had an idea by now, what is broken, and how to fix it. All the binaries on the fixit floppy (actually, only one large super- binary anway) are gzipp'ed. > once, but never really get anywhere. If I try booting with it again it > doesn't work. The file system is unclean after the first crash, and sysinstall doesn't attempt to fsck it. However, it's *not* the fixit floppy that's broken, it's the kernel on the boot (installation) floppy. You can boot a plain 2.1R installation floppy, select F)ixit, and stick in a 2.2-SNAP fixit floppy then. > I complained earlier about 'ls' not working on the floppy drive...but I I've read it, but your description is too vague. I cannot reproduce the problem (it seems like some FS-related vnode locking, i don't think this is particularly dependant on happening on the floppy drive itself), and seriously, about nobody really uses file systems on floppies... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603300804.JAA03375>