On Sunday 03 Aug 2003 12:08 am, Bill Mullen wrote: > On Sat, 2 Aug 2003, Anne Wilson wrote: > > OK - I umounted /holding and mounted the new /usr. I ran a cat > > command, then a cp one. I then used vi to change fstab, and ran > > telinit 5. > > Well, that's not much of a workout of /usr, I'm afraid - at least > here on my 9.0 system, both of those commands live in /bin ... but > vi worked, and we've seen that that links to /usr/bin/vim-enhanced, > so that counts. :) > I really couldn't think what else to do, but these were all things I had not been able to do before, so it was worth a try.
> > I did not hear the kde splash tune, but apart from that > > everything seems fine. The directory /holding still shows in > > konqueror, but I presume it is the mount point created earlier, > > not a directory as such? Anyway, it shows as empty. fstab is, > > as expected, pointing hde10 to /usr. What other checks should I > > run, before taking the plunge and deleting the old /usr contents? > > Yes, /holding is now merely an empty directory, the former mount > point of that partition. Remember, the only difference between a > mount point and a plain directory is that the former is also used > to mount a partition. If you stop mounting things there, it stops > being a mount point. :) > > I'd say that the key to knowing when you're done is that you've > given the system a good workout. First, make sure that fstab says > this exactly: > > /dev/hde10 /usr ext3 defaults 1 2 > Yes, exactly that > Then do everything you normally would, and watch for oddities. This > would include rebooting, logging in and out (perhaps with various > WMs), running familiar apps, pulling up a few man pages, pretty > much anything that will exercise the programs and files on /usr and > verify to your satisfaction that the copy is a completely accurate > one. > > First thing I'd do is log out and in again, and listen for that KDE > sound; that should work just as it did before, along with > everything else. If it still doesn't, time to investigate why not. > Start that with a reboot. > This still isn't working, either with a login or with a reboot. What's more, I can't preview any files, including sound files, when as root. Could this be connected? It works as user, though, and I suppose that the login .wav comes after I've logged in as user, so probably not. > Once you're satisfied that things are working as they should, go > for it. I'll try out all the apps I frequently use, and see if they all work. Meanwhile, if you've any thoughts on the significance of that missing startup .wav I'd like to hear them. Anne
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
