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.
If you can do stuff with a gui, then do it that way, well to start with. Its just easier until you "get your head round command-line stuff".
Any how, mandrake always installs it'self as default, but to change it, boot up the mandrake, go into the mandrake control centre>boot>drakeboot in the top right hand corner click on configure > first box called main bootloader options, just click ok
Second drakboot box highlight the windows box and click modify, select the check box or radio button to make it the default and OK (personally I also change the name to XP.), then I modify "linux" to read mandrake and ok.
I't a good one to remember, cos if you have to re install for any reason, then You know to change the default first.
p.s. Tobias, don't be tempted to do the modification via command or text unless you are VERY sure of what you are doing. I know it looks enticing, but as far as I can work out, it's also very easy to screw up. Use the "MCC" first, the look into/learn the text and command route after.
Perhaps you can understand my suggestion for changing things via the mandrake control centre. I'm sure someone with expert knowledge/experience would know which bits can be safely ignored, but as you can see, there are similarities, and also enough differences to discourage me from changing it via command or text mode.
p.s. I also think that if you can change something via GUI then more often than not, its easier. IMO that is.
I did what you told me to do and now when i look at my lilo.conf it has changed but when i restart my computer nothing has changed in LILO. It still got the old names, like lunix and windows, and the default OS is still set to Linux.
Here is what my lilo.conf looks like now:
Absolutely not necessary (well I'll correct that) shouldn't be necessary.
If you follow the route I have suggested to modify you lilo with the graphic input, you DO NOT need to run lilo in a terminal - that's the whole point of having the facility running with the graphic interface.
Worry about bloody command line shit AFTER you've got some basic knowledge - then you may have enough know how to exploit the apparent power of command line.
I done some digging around and am stumped as to why you can't modify the lilo.
So I will stand back and let someone else confuse the hell out of you - my humble efforts are only available in english - some of the others out there only speak "geek", and I don't know if you are familiar with that dialect!
You are quite correct. But I still suffer from having too much residual windows stuff in my head.
The experienced users approach of "if in doubt reach for the command line" is ok for EXPERIENCED users.
But vvv frustrating for n00b's.
Sure, I have heard of various commands, but that is absolutely no good, if I don't or can't understand what is happening when using the commands or interpreting the output.
From the n00b angle, at least if you are dropping/dragging stuff or imputing into dialogue boxes - it SEEMS more straight forward.
You have to admit, your view is going to be coloured by you superior levels of knowledge and issuing commands (and understanding what the commands are doing) should, at your level, be second nature.
Hence I often take the no command line view - I have enough trying to follow what mandrake is trying to tell me that it's doing, without additional confusion of command line input/output. The only part of most output that I can understand is that magic word
I assumed he already knew that to do this task at the command line he would have to be Root user - (next time I won't assume this)
Second - It's not sufficient - as was suggested - just to save any changes to the Expert tab in Mandrake and for that to have created the neccesary changes for next boot - whether you change Lilo.conf from the Expert tab or from an Editor, you always have to run the map installer /sbin/lilo - simply because - in running this program, amongst other things, LILO reads the lilo.conf file and creates a new map file based on the directives within - including the default = directive - it also re-installs itself to the boot sector designated in the boot = directive.
Just the mere act of saving lilo.conf on its own, whether in the Expert tab or in an Editor - does none of these things.