Crashed system

In general, file system mounting is controlled by /etc/default/filesys.
However, I thought that only applied AFTER leaving single user mode on the
way to multi-user mode. In general, you can just delete the lines refering
to the filesystem in question and that will cause it to not try to mount.

Again, I'm used to manipulating it for filesystems that get mounted AFTER
leaving single user mode...

Good luck,
Fabio

mkdir /u2
vi /etc/default filesys
find the paragraph the has mountdir=/usr
change it to say mountdir=/u2

that will stop it from mounting other hard drive over top of /usr at the
next boot.
it wil mount it on /u2 so you still have access to the data and use of the
drive. You can wipe it with mkfs and use the space for something else.

Before you do that, *especially* before you reboot, you better make sure the
/usr on the main drive is fully and correctly populated!

You might also want to run divvy on the 2nd drive. If the original installer
created /usr as a seperate filesystem, possibly they named it "usr" in
divvy, which created a /dev/usr and /dev/ruser. You don't _have_ to change
those. If you did nothing but exactly what I said above the filesystem on
the 2nd drive would continue to have a device name of /dev/usr but be
mounted on /u2. Mostly no one cares what the device name is but it's going
to be confusing to anyone who doesn't know the saga of this box.

I personally would probably figure out the real device name for the whole
disk, by looking at the major/minor numbers of /dev/usr, and comparing with
the contents of /dev/dsk.

Probably the second disk, if scsi, is /dev/dsk/1s0
I would edit /etc/default/filesys a little more than what I said above and
make a paragraph that looks like this:
( from my own actual /etc/default/filesys actually)
# 36G u320
bdev=/dev/dsk/1s0 cdev=/dev/rdsk/1s0 \
mountdir=/u2 mount=yes fstyp=HTFS \
fsck=dirty fsckflags= rcmount=yes \
rcfsck=dirty mountflags=

then:
umount /usr (local /usr better be there!)
mkfs /dev/dsk/1s0
mkdir /u2
rm /dev/usr
mount /u2
mkdir /u2/lost+found
chown bin:bin /u2/lost+found
cp /bin/* /u2/lost+found
rm /u2/lost+found/*

Call me funny, I just don't like divvy partitions :)

--
Brian K. White -- -- #
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani

ADDENDUM: Have restored the system to a new hard drive and got the
system to boot to single user again. Noticed that /usr is being
mounted as a separate filesystem just before the prompt to login to
single-user mode. I want to turn this off and have it use /usr on the
new hard drive. Does anyone know where this setting would be. My
search has come up empty so far.

TIA

There were 15-20 manufacturers of multi-CPU 386 and 486 systems. Altos
was one of the early and prolific manufacturers (later bought by Acer,
but they kept the Altos brand name for their higher end gear).

The 486SX and "487SX" upgrade socket were a completely different deal.
Over the years Intel has offered various CPUs in a reduced-function "SX"
version. There was the 386SX (16-bit bus vs. the normal 32-bit bus of
the 386), then the 486SX (disabled FPU), and I'm not sure if there were
any others. From those two alone you can work out that "SX" stood for
"sucks"...

...

I remember back in high school reading about motherboards of which were
dual 486's.

The chips them selves didn't have any inate ability, but there were
work-arounds for it by chipset manufacturers.

That being said, I never got to see one.

bkx

Can't help you, but this bit bugs me. Are you sure it's a 486? I
thought pentiums were the first to be dual cpu-able. 486s did have the
upgrade socket, but in that case the original CPU is deactivated and
chugs along consuming 5% power without giving anything back. Never been
quite sure why this was better than ripping out the original, but hey,
I'm no hardware designer.

Anyway, might want to check that.

--
Scott Burns
Mirrabooka Systems

Tel +61 7 3857 7899
Fax +61 7 3857 1368