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 have a few dual-boot systems that have Fedora Core 5 and Windows XP.
GOAL : to be able to control remotely how to reboot any one system.
So, if I'm in a SSH session and I want to reboot in Windows (and Linux is currently the default in grub.conf), all I need to do is edit grub.conf, and voilą.
However, if I'm in Windows (remote desktop), and the current default in grub.conf is also Windows, and I want to reboot in Linux, I'm screwed.
Solution 1 : Windows driver to access Linux partition (ext3)
I've looked at ext2fsd, but it seems not to support ext3 in write mode... Any comments ?
Solution 2 : Make a (small) fat32 partition, somehow transfer the grub.conf there, and I'd be all set.
This seems like a good enough solution. I can figure out how to physically transfer the files from ext3 to fat32, but can anyone tell me how to configure the Linux boot process so that Linux will look on the new fat32 partition for grub.conf ? Detailed steps would really be appreciated here... thanks...