Solaris

I did exactly that DGPickett.

---------- Post updated at 03:02 PM ---------- Previous update was at 03:01 PM ----------

And it worked.I knew it worked immediately because the CPU has been near 100% this whole time and it dropped down to 1%.I've test it and it all seems good.

Sure glad you had that file manager, it was getting ugly!

---------- Post updated at 04:04 PM ---------- Previous update was at 04:03 PM ----------

Not the people, the idea of building a system from scratch.

I tried to go in and now rename "lib_old" back to just "lib", but it won't let me because the symlink I just created is called "lib."Should I just leave it alone now?

Let me ask the Solaris 8 experts if I should continue the installation of libxml2 because I need it for PHP. If I do that, will it fix the mess I've made?Also, I don't understand the implications of libxml2 messing with my lib directory, can it mess anything up? Will I loose an configurations that are important for the server and the websites it hosts?

And, if it's safe, what options should I turn on when I do the configuration? There are lots. Ultimately, I'm just trying to get to a point where I can install phpMYADMIN so that I can edit the existing mysql databases in a manner I'm comfortable with... But I'll only be able to use that if I can somehow do it remotely on the network, because the Sun only has Netscape on it...

This fails?

Code:

mv -f /usr/lib_old /usr/lib

He never had the idea to build or reinstall from scratch. His other plan was to boot from an install disk, mount the partition and fix the problem; something that most of us could have already accomplished hours ago, LOL.

It does fail: "insufficient arguments..."

Normally "short cuts" take longer than just doing the work properly.

Instead of shooting blindly and getting advice based on "best guesses" why not shorten your time to success and mount your disk using your boot disk and fix the problem from the console?

You could have fixed this problem a number of hours ago if you had of mounted the filesystem and fixed the problem, IMHO.

We cannot be 100% sure, based on your posts, that /lib was a symlink to /usr/lib ... this is just a "best guess". Instead of guessing, why not just fix it properly?

---------- Post updated at 22:34 ---------- Previous update was at 22:26 ----------

Note:

Solaris allows you to boot from the CD-ROM into single user mode which, in turn, will allow you to mount your filesystems and repair the problem. To boot into single user mode from CD-ROM, from the ok (bootprom) prompt do this:

Code:

boot cdrom -s

This will give you a root prompt (#) with a functional but limited Solaris filesystem from the CDROM. To access your filesystems, you need to mount them. For example, if your root filesystem is c0t0d0s0, use:

Code:

mount /dev/dsk/c0t0d0s0 /mnt

Then you can work in the /mnt filesystem and make changes to your real root filesystem. You can mount other filesystems on their usual mount points within the root (/mnt) filesystem. Once you have fixed whatever you need, just reboot.