UbuntuThis forum is for the discussion of Ubuntu Linux.
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.
As a quick explanation, I bought a Ubuntu-preloaded laptop from Dell. After a few weeks of use, I ended up switching hard drives with a friend, and got a smaller drive than the one I had. Using some magic, all the data I had on my drive was ghosted and then placed back onto the new, smaller drive.
To my utter surprise, everything loaded. During the first boot up process after the procedure, Ubuntu did a drive check because of some mismatch, said it fixed some bad blocks and moved on. The laptop came up fine after that.
There seems to be one problem, though, and it has me stumped. If I press the log out button as soon as my desktop comes up after booting, nothing happens at first. Other programs load fine, and I can honestly go on to check mail and surf the web. About four-five minutes later, the screen with the different log out options will finally come up. After wards, the button works normally. Also, if I wait five minutes and not press the log out button, then it will also work fine.
It's as if for about five minutes after bootup something else runs that won't allow for that logout box to come up, but does not affect any other program (tested with Openoffice, tbird, and firefox).
Any ideas how I could see what's going on?
Er: Using Feisty Fawn, fully updated as of about a week ago.
Nothing unusual except these three lines (although they look to be part of the start up).
kinit: name_to_dev_t(/dev/sda5) = sda5(8,5)
kinit: trying to resume from /dev/sda5
kinit: No resume image, doing normal boot
I have to mention that sda5 is actually my swap partition, so I have no idea why it's looking for a boot image in there, but oh well.
Is there a way to see what exactly happens at boot time when normally there's the Ubuntu screen with a line scrolling across it? Like something that would let me see, line by line, what is actually loading.