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.
After successfully installing SuSE 9.2 pro on my dell latitude laptop last week, I played around with 'suspend to disk' yesterday fand tested it a few times and it worked - was able to suspend, and recover. Great.
Then I decided to do my first 'YOU' (YaST Online Update). Seemed to go well, in that all messages were fine.
However, on reboot, I had all kinds of issues with the file system - reiserfs, reporting bad blocks, etc. With help from this forum, I was able to 'fix' this and reboot (ran reiserfsck with the --rebuild-tree option).
Now, my 'only' problem is that tty1 does not work. After booting successfully all the way into the gui, when I ctrl-alt-F1 to tty1, it shows the tail-end of the boot process, but is non-responsive, and there is a message that appears every 5 mins or so - INIT: Id "1" respawning too fast: disabled for 5 minutes'.
Doing a grep on messages, I see a lot of 'linux mingetty [xxx]: /dev/tty1: No such file or directory' lines.
looking in /dev, there are tty0, tty2, tty3, etc but no tty1 ...
So somehow /dev/tty1 is gone ... how do I recover it?
Is this likely to be a consequence of the suspend to disk experiments, the online update, or some random failure in my filesystem ...?
It can be re-created with 'mknod /dev/tty1 c 4 1' (creates a character device, major number 4, minor 1. The ownership should be root:root, permission 0600. If your dev files are created by an auto-system like udev, this won't survive a reboot. You'll need to check your udev config (/etc/udev directory) if that's the case.
Edit to add: Suspend to disk may be the culprit here -- I've heard of it doing wacky things, and it's not fully bug-free yet.
The way I usually see it is that terminals with no one logged in have permission 600. Those with a user logged in have permissions 640 root:tty so that anyone in the tty group can write tpo the terminal (this is for the write or wall programs). Ithink getty or login sets that all up when you login, but I'm not 100% certain.