Thanks a million to all who got to me so quick. I got
in total 25 replies in 10 mins.
What I didn't let you know before:
I use sudo, so I moved shlib to shlib.old, hence sudo
rendered useless. Couldn't switch to root to copy the
right file in place.
I have two shlib directories, and I switch between
them from time to time when trying something. This
time, instead of being in #, i just did $sudo mv shlib
shlib.old!!!!!!!! I have 4.0G with AdvFS
What worked:
I powered off the system, and at srm >>> boot
It booted all the way up and failed on initiating
sia..., dont remember what, hence reverted to single
user mode. Entered root passwd, mounted /usr, and
copied my files, reboot, boom, I am back.
What was very technically suggested, might think of
printing it out for the future scenario is shown
below:
**************From John Francini*****************
Ascertain which physical disk and partition of that
disk contains
your /usr file system. You'll need it in the steps
that follow.
Boot an installation CD. Instead of actually
proceeding with the
installation, when offered the opportunity to go to a
UNIX shell (at
a question that gives you the choice of "Standard
installation/Custom
Installation/UNIX Shell"), take it. (Graphical
installations will
present a screen with three buttons labelled as above.
Click the
UNIX Shell button.
The installation will exit (and leave graphics mode if
your system
has a graphics head) and give you a shell prompt.
Once at the shell prompt, mount your /usr file system:
(a) AdvFS:
# mkdir /etc/fdmns/usr_domain
# ln -s /dev/rzxxy (v4.x)
# ln -s /dev/disk/dskxy (v5.x)
where x is a number and y is the partition where
the /usr
partition lives
# mount usr_domain#usr /mnt
(b) UFS:
mount /dev/rzxxy /mnt (v4.x)
mount /dev/disk/dskxy (v5.x)
Once mounted:
# mv /mnt/shlib.old /mnt/shlib
# sync
# halt
Now reboot your system normally.
Hope this helps,
John Francini
John Francini <mailto:francini_at_zk3.dec.com>
>My device is re0g for usr file system.
>so went inside /etc/fdmns/usr_domain and created a
>link
>ln /dev/re0g re0g
>gives me an error, re0g is not a block device.....
oops. Forgot that the device special files don't
exist in that
temporary system-disk environment at that point. They
have to be
made beforehand.
In the boot environment, before making the softlink:
# cd /dev
# ./MAKEDEV re0
# cd /etc/fdmns/usr_domain
# ln -s /dev/re0g (you don't need any
other arguments; it will
leave a file named re0g
in that directory)
then do the mount.
j
=====
Richard F. Mollel
Systems Administrator
SAIC
Greenbelt, MD
Experience is what allows you to recognize
a mistake the second time you make it.
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
Received on Fri Dec 22 2000 - 17:53:19 NZDT