Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Sorry to take so long to get back to you. This makes it look like you don't have a shell specified in /etc/passwd. Go back into rescue mode and make sure. Remember, you will need to get a chrooted environment by running "chroot /mnt/sysimage' (you needed to do that for the previous instrctions as well).
Forrestt: The response to the first code was: mike:x:500:500:mike v:/home/mike:/bin/bash.
I rebooted but nothing changed.
I'm thinking at this point there's no practical solution to this problem. I have a backup drive that has ver.7 kde that I just discovered within the last several days. I have in the past tried to retrieve files from an older version of linux when a newer verion was installed on my PC but have never been able to mount the drive. Can you explain how I can accomplish this. My PC has four 5 1/4 slots with removable drive bays installed so its very easy to go from one Op.Sys.to another. If I can pull my files then I think I'll do a DoD wipe of the drive/check it for errors with spinrite & load ver.9 Kde and be done with it. I want to thank you so much for all your help & if you didn't live so far away I'd have you over for the biggest Porterhouse you've ever had.Thanks Again, Mike
There really isn't any need to DoD wipe your disk until you are totally done with it (i.e. you are about to throw it away or sell it). Reformatting it is enough.
I'd like for you to do one more thing for me though. Boot back into rescue mode, go into your chrooted environment, and run: 'cat /etc/fstab' and post the contents back here. After that, I can give you much cleaner commands to mount your current drive after booting from the ver.7 drive.
Forrestt: Wow..there's just too much there to absorb. I don't know where to start. I don't understand why its so difficult to see another drive of the same type.How in the world does anyone wanting to use another drive for storage get it done. I'm not a big fan of windows but this just isn't an issue under that system.It would be cool if someone with the knowhow could incorporate this feature into the next release. I thank you just the same for all your help Forrestt. Mike
Forrestt: You've heard the statement.....if anything can go wrong it will.....lets see...I'll start at the beginning.
1): I found out that the video onboard is S3 Unichrome Pro VGA Adapter. This may come in handy in a few minutes.
2): I wiped the drive & attempted a clean install. What happened is that every time I got the graphic's page early in the install, it would lockup. If I chose install-text mode- the install went ok but I only get black & white screen with text & login name(something it never asked for during install)(I did choose password but nothing was asked about login name)
3): After the install a screen appeared with various config options & if I choose X system config as long as I navigate using the tab key I can move around but If I choose anything with the mouse and/or exit the screen,it locks up.
4): I thought to myself I'll boot my Ver.7 drive which I've never had a problem with & see if there's an update to Ver.9 or perhaps try Ubuntu etc.
You may recall that 1 option we tried was to boot ver.7 with ver.9 in sec.slot to get files from that drive, which didn't work. Now My ver.7 drive won't boot. I get this error:
fsck.ext3: Unable to resolve 'UUID=0ac530-7ea2-43dd-9385-8d5a820b2681'
It attempts this 3 times then tells me an error occurred during the file system check.
Am I really screwed now or can this be saved. I'm thinking that somehow the file system has become corrupted when I had both drives installed. I really need some help now. Mike
Well....its official....The Video chip was the culprit all along. Now I need to get another card & have been told nvidea is the way to go. I downloaded the latest Ubuntu & thankfully this install had a generic vesa driver which at least enabled me to use it till a replacement is installed. Any thoughts on a new card?? Mike
Last edited by ironhorse99; 12-26-2008 at 08:42 PM.