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.

Not to be as a$$, but I just wanted to correct TigerOC slightly. When the grub config file is saved, no data is actually written to the mbr. Grub has the ability to read ext2 filesystems, and will mount/read the menu/config/etc file directly. This is why you don't need to do anything other than save the file for the changes to take effect.

Beg pardon but with Debian it does - don't know about other distros.
Ok I follow - sorry I did not know the menu.lst was read by grub but thought it was written to the mbr. No matter - the end result is the same.

GRUB's configuration file is read from the disk every time the system boots, preventing the user from having to write over the MBR every time a change the boot options is made. Most boot loaders are not sophisticated enough to read configuration files and use them to set up boot options. For example, to change a LILO boot configuration, such as changing the default operating system to boot, users must change a LILO configuration file and run a command that overwrites the system's MBR with the new configuration data. This is more risky than GRUB's method, because a misconfigured MBR would leave the system unbootable. With GRUB, if the configuration file is erroneously configured and rebooted, it will simply default to a command line and allow the user to manually type commands that will launch the operating system. The MBR is not touched except to update the Stage 1, Stage 2, or menu configuration file locations, and this is rarely necessary.

Originally posted by TigerOC This is an interesting one because Debian does not have such a configuration file. I see it mentioned in regard to other distros but there isn't one in Debian i.e. no /etc/grub

Originally posted by earth.hero Im just start using Linux, so i know little bout it.
Can u tell me how to log on as root?
plz

Damn, just finished an answer

To the discussion re grub - that Redhat link is useful, but don't treat it as gospel.
As an aside the code looks for menu.lst. Lots of distros symlink this to grub.conf, some patch the code to look for grub.conf.
Some flip-flop between the two - the Gentoo guys can look at the patch set that comes down with the emerge of a new version of grub. Changes from one to the next.
Makes it difficult to offer good advice on sites like this that have a mix of user competence, and a mix of distros.
The OP in this case hasn't told us what distro (s)he uses.