Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Sometimes (actually most of the time) whenever I shut down and restart I get nothing but a blank screen. I can usually get it goiing after turning my PC on and off a couple of times. Whenever it does finally boot up it goes straight into my BIOS. Anyone know the problem.
Every distribution creates its own version of the shutdown scripts. The
standard place to locate the shutdown scripts is somewhere in /etc. SuSE calls their two shutdown scripts /etc/init.d/halt and /etc/init.d/reboot.
Once you find your shutdown scripts look for one or more of these commands: halt, reboot, and shutdown. Your shutdown script(s) will use some variation of each of these commands to shut the system down after going through some complicated logic to see what is running and exactly what you want to do. Follow the logic of the scripts until you decipher which command and command parameters are used to service your reboot request.
You can use the man command to learn what the commands and their command parameters actually do (i.e. man shutdown).
You can set up your own shutdown script to test out how you think that
shutdown should really work. For example: You could set up a file called
/root/test/myshutdown and set its attribute to executable. I would suggest
starting by setting /root/test/myshutdown to a simple command like:
/sbin/shutdown -r Then as root issue the command /root/test/myshutdown. See what happens and take it from there.
You're pretty brave to just dive right into Linux but I think it's time for you go and out and buy a book on Linux or two. That can save you quite a bit of time on basic questions. However I bought a book on Samba and am working through it but I still can't print to my samba printer.
At this point in time you probably don't have enough information to
pinpoint what the problem is. The problem could possibly be one of several
hardware or software problems. I suggest that you do some debugging analysis.
First off, does your problem occur sometimes when you simply power on, i.e.
you turn your machine on for the first time that day. If it occurs at times
other than reboot then it is most likely a hardware problem. If the problem
occurs only when you reboot Linux then it could be either a hardware or software
problem or a subtle combination of the two.
If it is a hardware problem power off the computer and check to see
if all your connections are good. This means reseat your memory sticks, make
sure all power connectors are tight, reseat your PCI cards, press down all
unsoldered chips, etc. It may be that your power supply is too small or dying a
You can try to isolate the problem as either hardware or software by
issueing different variations of the shutdown, halt, reboot, and poweroff
commands. Do these tests from the command line, do not have X Window running because abruptly terminating Gnome or KDE can cause disk file corruption.
I suggest you first try: shutdown -r now
David Phillips recommends first trying: poweroff
What you try next depends on the results of your tests. If your problem is intermittent you might have to do the same test several times because the results can vary from test to test. You can read the man pages for these commands: halt poweroff reboot shutdown
Depending on the results, work through the various shutdown type of
commands in an attempt to isolate whether you have a buggy shutdown script or flaky hardware.