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.
I've basically been using the system by booting into run level 4 for the past few days, so that after booting the linux goes straight to gdm. For some reason when using gdm I cannot access any of the virtual terminals, but if I boot into run level 3 and use startx then I can access the virtual terminals just fine. Well, I just decided to screw up my xorg.conf and have set the color depth too high for my card. Of course I get an error from X11 and then it kicks me into the CLI, only I'm not getting any the CLI. No matter what virtual terminal I try to switch to I get the same thing: a black screen and I can't put in any commands. I've tried booting off a slackware 10.1 installation disk and then mounting /hda2, but then I can't seem to access it. So now I'm all out of ideas, but all I need is just edit my damn xorg.conf file. So if anyone can help, it'll be much appreciated. Thanks ahead of time.
Last edited by losingfight; 04-27-2005 at 12:22 AM.
With that you can get a fresh start on that config file. You may want to save the old one so you can copy it back, just in case something goes wrong and you can't get anything but a ugly error message.
Hope that helps. It has been a while since I have had to run that.
Of course, it has been a while since I rebooted too.
I know exactly what the problem with the xorg.conf is, I can fix that. The problem is that when X11 tells me there is an error I'm supposed to go to the CLI. I just get a blinking box and blank screens with a blinking box at the top of each virtual terminal. I need a way to get into the default CLI without going into X or whatever. Sorry if my problem isn't quite clear.
Last edited by losingfight; 04-27-2005 at 12:35 AM.
Originally posted by losingfight I've tried booting off a slackware 10.1 installation disk and then mounting /hda2, but then I can't seem to access it.
So you booted into rescue (single user) mode and you say you were able to mount /hda2 but not access it? I have not used rescue mode in the Slackware 8 that I have and don't know if it would give you access.
If you have a LiveCD you could boot and mount your /hda2, however, it would most likely still be read-only, but I think you could use this command in su mode:
mount -o remount,rw /mnt/
may have to use:
sudo mount -o remount,rw /mnt/
This should mount all file systems in fstab to read-write, allowing you to edit your xorg.conf file.
What do you mean by rescue mode? What I meant was that I managed to boot using the installation disk for slack 10.1 (is that the same as LiveCD?). After booting there it would not let me go into su mode. I used /mount -t ext2 rw /dev/hda2 /mnt i think, but then it woudln't let go into the /mnt/hda2 directory. Thanks for all the help, I got it to work.
Last edited by losingfight; 04-27-2005 at 01:29 AM.
It doesn't have to be this complicated. When booting slackware, you always have your first terminal, it is always accessible (CTRL + ALT + F1), it could be busy, that I don't remember, but then F6 is there as well.
So no mather what happens, you can always access those.
in slackware 10, they did this neat thing. the second install disc IS the rescue disk, and from that you can do anything you want. I've had to play with that a few times, so I can tell you it's definately a helpful tool. c
as for the vitual consoles, what I used to do is just add, I think the path is "/opt/kde/bin/kdm" to /etc/rc.d/rc.local
this way I'd have a windows manager start up, and I've have the virtual consoles.
So you're saying to add the path of gdm to rc.local, but then should i be booting in run level 3? Run level 4 would seem redundant. Either way, I've tried adding the gdm path to rc.local and have booted in both run levels 3 and 4. At 3 all I get is the standard CLI, and at 4 I get an error that rc.4 cannot be executed. I've checked the rc.4 file and it's perfectly fine. So I guess i'm not quite sure how adding the gdm path to rc.local might help. Thanks for the suggestion though.
no, don't do this, the fourth runlevel is specifically made for this kind of thing. Take a good look at /etc/inittab, there should be a man page about this as well. You can add those terminals in that file.
the number just before :respawn apoints the terminal to certain runlevels, e.g. 23 is runlevel 2 and 3, 2345 is runlevel 2,3,4 and 5. Get it? All you have to do is put 4 in with those you'd like.
This is a cleaner solution then starting that window manager manually.