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!
Notices
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.
Would it not be better to figure out why it is crashing?
Quote:
Originally Posted by priyadarshan
Yes it would be... but we are looking for temporary makeshift solution...
I cannot imagine a rationale in which that could apply, so I won't try...
But if it saves you some time, your line
Code:
cat /dev/ttyS0 > file.txt
...does not do anything useful. It tells the the system to wait for input from /dev/ttyS0 (hang, as you say) and send whatever is typed to file.txt.
But any such action within the init sequence would be pretty pointless and the result dependent on where it was in that sequence - before or after filesystems were mounted, whether mounted readonly, the total context of the as-yet-not-fully-inited system.
Code:
cat /dev/ttyS0 > file.txt
...does not do anything useful. It tells the the system to wait for input from /dev/ttyS0 (hang, as you say) and send whatever is typed to file.txt.
It really isn't possible to provide any meaningful help the way that you have described the problem.
And I and most others (as if I can speak for them) would be reluctant to spend time troubleshooting a makeshift workaround while knowing that another problem existed, but not knowing anything about it - potentially a huge time waster!
If you would like to get help troubleshooting the actual problem then please post the GNU/Linux version, kernel version, basic hardware and a good description of what happens when the boot fails, with some output from dmesg and syslog.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.