Path: utzoo!utgpu!watserv1!watmath!att!att!emory!samsung!know!newmedia!jim
From: jim@newmedia.UUCP (Jim Beveridge)
Newsgroups: comp.unix.sysv386
Subject: Re: SCO-Unix - booting to single user mode and then crash
Summary: Increasing inodes & using cpio
Message-ID: <412@newmedia.UUCP>
Date: 23 Oct 90 19:10:17 GMT
References: <9010171604.AA24053@decpa.pa.dec.com> <7965@star.cs.vu.nl>
Organization: New Media Graphics, Billerica, MA
Lines: 48

In article <7965@star.cs.vu.nl> you write:
>paine@fungus.dec.com (Willy Paine) writes:
>>    How can I upgrade this from disk instead of installing from scratch?
>	You should create an 'emergency boot floppy' and a 'root
>	filesystem floppy' (sysadmsh->filesystems->floppy). This procedure
>	and restoring your root filesystem is very poorly documented and 
>	what the manual says about it is **not** correct.
>	You should at least do the following:
>	- Make a boot and root floppy

You can do this by "mkdev fd"

>	- When your root filesystem is too big (development system, etc)
>	  you probably get 'out of inodes' on the floppy. I don't know
>	  yet what to do about that.

You can increase the number of inodes by modifying line 399 of
/usr/lib/mkdev/fd.  It says:

	mkfilesys ${swplo}:640 || {

You need to increase the 640 value to something
larger (This is the number of inodes that will be created on
the floppy).  Considering that the default frequently doesn't work,
the difficulty of finding this is ridiculous.

>	- You have to make a mount point on the 'root filesystem floppy'
>	  for the hard disk.
>	- You should first remove your old root filesystem or create
>	  a new root filesystem on your hard disk. Otherwise you still
>	  can have old (bogus) files in your system.
>		Ronald van der Pol  <rvdp@cs.vu.nl>

If you have made an "Unscheduled" backup, or a level 0 scheduled backup,
then you can use cpio to restore the system.  The directions on
page 65 in "Tips, Tricks and Troubleshooting" in the User's Guide
have worked for me before to successfully restore a crashed
ODT system.

To do this, you *should* do as suggested above and rebuild the
root partition if it has crashed.  All of this is a real pain
in the ass and poorly documented.

Now if I could just figure out why custom(ADM) keeps giving me
and error 10, (10, not 11) I'd be all set.

		Good luck,
		Jim