Hay aren't you forgetting the most important usage.
Use the fixit cdrom to boot small running FBSD environment so
you can restore your tape backup to the failed hard drive, or dd
your bkup image.

-----Original Message-----
[mailto:[EMAIL PROTECTED]]On Behalf Of Mike Meyer
Sent: Thursday, January 30, 2003 9:54 AM
Cc: Chuck Swiger; Giorgos Keramidas; [EMAIL PROTECTED]
Subject: Re: Fixit instructions

> Quoting Mike Meyer <[EMAIL PROTECTED]>:
> > You don't have to boot the fixit cd - just mount it and look.
I'm sure
> > that what you will find on the CD is a pretty complete FreeBSD
> > with the layout described in the hier man page.
> Close, but...
> root@BAPhD ~ #ls /cdrom
> .cshrc          bin             etc             modules
> .profile        boot            filename.txt    proc
> COPYRIGHT       cdrom.inf       floppies        root
> CVS-REPO        commerce        kernel.GENERIC  rr_moved
> README.TXT      dev             mnt             sbin
> Note the absence of mnt2 and stand, both of which I was aked to
examine.  Those
> directories are set up on booting the cdrom and entering Fixit
> bin, sbin and usr/bin on the cd are indeed readable ( and
extensive) directly
> from the CD.

Right. Those aren't on the fixit disk, they are on the root file
system used by the boot process. That's a stripped system file
used for installing FreeBSD. It mounts the fixit cdrom to give you
rest of the FreeBSD world.

> I don't mean to be difficult or over-demanding about this,
especially to people
> who are offering help, but what I was expecting was trhat some
helpful guru
> would have prepared a "Fixit Handbook" which might have chapters
like "Repairing
> a corrupt partition table" and "Restoring a lost directory" and
...  whatever.
>  Perhaps the book Chuck suggested would do that.

If such a book exists, I don't know about it. Part of the problem is
that the commands for this only exist at two levels: the
straightforward (you want fsck), and the incredibly baroque world of
hex file editors that you're going to point at the disk. One handles
all the cases you are liable to run into in real life. The other
requires an intimate knowledge of the on-disk file structure, and a
hex calculator - and even then what you are doing is incredibly

> Reading man pages doesn't tell me with any clarity which commands
go with what
> do do something.  One really needs far more knowledge than I have
to make sense
> of it all.

On the other hand, a "reading guide" might do a lot of good, and
a lot of sense. Something that says things like "For problems with
partitions (aka slices), see fdisk(8), boot0cfg(8) and
/usr/include/sys/disklabel.h. For problems with FreeBSD partitions,
see disklabel(8) and /usr/include/sys/disklabel.h. For problems with
the file system, see fsck(8), /usr/include/ufs/ufs/dinode.h and

Come to think of it, about the only reason one should be mounting
fixit CDROM is because your root file system is screwed. I think I
just covered everything you need to know about fixing broken file

The problem is, that's not complete. You may need to know how to
create dev entries - at least on 4.7. You'll want to know about
in order to mount working file systems, and to check the broken file
system once you've fixed it. If the breakage causes you to change
what's mounted where, I tend to fix that in fixit mode with ed, so
may want to know about that.

Maybe what's needed is an "Essential BSD commands" handbook entry,
that covers the lists the commands available in Fixit mode that are
actually useful for fixing a broken system?

Independent WWW/Perforce/FreeBSD/Unix consultant, email for more

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

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

Reply via email to