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 want to try something different, that seems to always work for me on the regular ata controllers......swap the drives. If you install lilo in the first drive, it'll be the linux drive anyways. You can add Windows to the bootloader by "fooling it" into thinking its the first drive. You add
to the windows line, if its regular ata. 0x80 is the BIOS equiv of first ata drive. I find this to be a better solution as it doesn't replace the win bootloader at all.
If you go into your BIOS screen, does it have the actual hex values of the drives it finds?
Windows is on my first drive, first and only partition (hde1)
LInux is on my second drive, 4th partition (hdf4)
So you are saying that I should swap the drives with the IDE controllers (which would make hdf4 be hde4, and hde1 would then be hdf1) right? Then after I do that, boot into Linux and then install LILO, but first add "boot-as=0x80" to the Windows section in LILO. What does "boot-as=0x80" mean?
I think I'm going to try this:
I reformat my 80GB hard drive, I'll put Linux on first, I don't REALLY need Windows except for maybe certain games, so I'll probably create a 10 GB partiton dedicated to Windows. I'll probably create a swap partition, a partition for "/" at about 5-10 GB, and the rest for "/home". That equals 4 total partitions, the maximum amount allowed to be created. Does that sound like a good setup???
Good plan, but put Windows on first, as it likes to be first. If you do it all from one drive, you should have no trouble installing lilo or grub properly. It should pick up that windows is there and make its own entry. Good luck.
Oh ok, thanks for the tip (about windows being first, i would not have done that lol)...
And about the hex values, were you saying to use those so I wouldn't have to switch the hard drives on the IDE cable? I would specify a hex number with the drive path itself. Am I getting the right idea?
If you put both on the same drive, as you describe, you won't really have to worry about that. But, yeah, the lilo mini-howto recommends such an action when booting from a drive that's not the first one. Check that page out. It describes what's going on better than I can.
Reading this page, leads me to believe that you may have a utility available to you to determine the bios ids of your drives. Perhaps the website of your ata controller card has a utility to identify your hardware better. If you could get something like that, it'd save you a headache if you want to spread the OS/s over more than one drive.
An even better and faster way to determine your I/O values.
Last edited by vectordrake; 06-01-2004 at 09:45 PM.
Wow, thanks for the quick reply. I think I will do the setup I stated above, but I am glad to know that the other way is possible (booting from the second drive). You have helped a lot! Thankyou so much, I'm going to get things started, too bad I have to install Windows first lol, it takes too long.
Heh. You don't have to go to Winupdate until after the bootloader is installed. LOL. That'll sve you a bit of time, updating. Good luck with that whole mess. I'm sure you'll know your controller inside out before you know it.
LOL yeah Windows Update.... wow I can't believe it has so much to download to get up to date... Speaking of up to date, I have also been wondering about swaret... I downloaded Slackware 9.1 a while back (which we all know is old, I believe it came out in September). I also downloaded Slackware Current (dated 5/21/04) on, well, the 21st. Unfortunately it looks like you "Vectordrake" don't use Slackware, but I have been wondering, if I tell swaret to retrieve and update to Slackware current then will it update KDE from 3.1.4 to 3.2.3 (or whatever the latest version is)? Hmm, maybe I should create a new thread for this message, but if you do know, thanks!
I've only played with swaret a little bit, but it looked promising. I had a bit of a problem when i used it with Vector 4, trying to upgrade to Slack Current. I couldn't get it to point to the right X stuff, as Vector used a different desktop configurator than I'm used to (and I did most of it reading only the configs - no manuals - hey, I am a man, after all - instructions?), but it seemed to upgrade everything spiffy kewl. Its a necessity, as far as I can recommend. You'll have to point your swaret config file to CURRENT instead of 9.1, otherwise your idea won't work. But, if you want it fast and right, I think you're bang on the right path.