From owner-freebsd-current Sat Mar 30 12:20:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA07683 for current-outgoing; Sat, 30 Mar 1996 12:20:31 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA07669 for ; Sat, 30 Mar 1996 12:20:25 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id VAA25009; Sat, 30 Mar 1996 21:00:29 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by gun.de (8.7.5/8.7.3) with SMTP id TAA04941; Sat, 30 Mar 1996 19:33:54 +0100 (MET) Date: Sat, 30 Mar 1996 19:33:53 +0100 (MET) From: Andreas Klemm To: paul@netcraft.co.uk cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org, handy@sxt2.space.lockheed.com Subject: Re: Fixit Floppy Broken? In-Reply-To: <199603301231.MAA00590@originat.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- On Sat, 30 Mar 1996, Paul Richards wrote: > In reply to J Wunsch who said > > > > 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. > > > > 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 strongly disagree. The fixit floppy needs to be completely redone. I > wasn't aware that there was a single gzipped binary on it (has this > changed recently?) but that's frankly ridiculous. The fixit floppy > should work on any system as a last resort tool to recover from a fatal > error. Support for gzipped binaries isn't even present in a lot of kernels! > > I think it's a design error to have fixit be shoe-horned into sysinstall. > Let's just have a plain and simple set of tools. If you're damaged to the > point where you need to use it then you're into the "expert" area and > a nice gui is not very relevant and is just a waste of space. > > Now, if someone is concerned about naive users spamming themselves then > perhaps we need to think about an automated recovery disk but that's not > what fixit is all about. I think you're deadly right in this point... A simple nice boot disk with a generic kernel with tools like: fsck, scsi, ed, cat, more, newfs, mkfs, ls, rm ... and ,friends' is badly needed ;-) And of course a nicely working MAKEDEV, that creates the needed /dev/ entries, if you have for example 2 SCSI disks and perhaps even more. - -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ $$ Support Unix - aklemm@wup.de $$ pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMV1+kvMLpmkD/U+FAQHW9AP+M5hhrDakT1okHi6EJUt1NdsR9j3TI52K fcw6ZViW8nM9krCwbOaRJnMi50959ILCLZ893fu0DVqzY5Lq/+gSUf8hXfkxpUZF SQ9X+W0lkHvd7zOATNmyIjDU6zlz7RgNnydtAQd9OEeQYopI+83WO2ZAM3eOFUvZ nLilP8n/P+8= =tJpu -----END PGP SIGNATURE-----