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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
previously i put lilo on the MBR, which works fine except i would like to keep my win & linux hard disks totally separate, so i could take out linux hdb and windows would still boot.
what i am now doing is telling lilo to go onto the root part of hdb, and it automatically puts the boot DOS option in it too. (slack 9.1, choose Simple lilo config, then ROOT (not floppy or MBR)).
it loads linux fine, so long as i get the bios to boot from IDE1, but windows doesnt load when i choose it. it just says 'loading windows' and then stares at me as if im a newbie... the cheek.
when i set the bios to boot IDE0, it loads windows fine (no LILO), which is what i want.
i'd like to be able to set the bios to load IDE1, then LILO, but for the windows option to work. is this possible or has it already gone past the stage of booting windows if lilo boots from root on hdb?
hey, im using slackware, i want it to work MY way!
Last edited by Mr Marmmalade; 05-11-2004 at 03:14 PM.
i have the windows bootloader installed on the MBR of hda which boots windows
and i have grub installed on the MBR of hdb which boots linux.
i use boot options in bios (F8) to select what to boot,
and i can remove any hard disk, stick it in anouther machine, and each disk is un-effected by the loss of its friend.
I've got a harddrive from another machine, with windows on it. I just put it on the secondary of my Promise UltraATA/66 card, and can get to it from linux as /dev/hde1. My primary carries my linux drive, as /dev/hdc, with various partitions mounted as /, /home,/var, and such.
I want to modify lilo.conf to let me boot (or see if it is bootable) my windows hd from the other machine. I've tried the "boot-as=0x80" and lilo chokes, saying something about unrecognized tokens at or near line ##. Here is my lilo.conf:
Distribution: SuSE Pro Releases 7.3, 9.0, CentOS 4.0, Kubuntu 6.0x
Posts: 103
Rep:
qwijibow:
Quote:
Originally posted by qwijibow yeah you can do that...
i have the windows bootloader installed on the MBR of hda which boots windows
and i have grub installed on the MBR of hdb which boots linux.
i use boot options in bios (F8) to select what to boot,
and i can remove any hard disk, stick it in anouther machine, and each disk is un-effected by the loss of its friend.
Hi,
excuse me for the newbie-question, but how did you configure the GRUB loader (or probably it should be the LILO one?) in order to be able to boot from hdb without hda?!
I'm trying just the same thing with my SuSE 9.0 but it doesn't work. I have to put the bootloader (LILO or GRUB) into the MBR of hda in order to be able to boot the instalation on hdb.
When I put GRUB on MBR on the hdb disk, then it says just "GRUB " and freezes on the screen, if I use LILO instead then the LILO prints one screen with "99"s and freezes too. Puting the bootloader in the /boot section of the the /root partition on hdb causes the BIOS not to recognize this disk as bootable and to proceed directly to the next boot disk (I use BIOS to switch the boot drives sequence to: 1st = HDD-1, wich is hdb, then 2nd = CDROM, 3rd = Floppy).
My SuSE 9.0 installation on hdb has only two primary partitions on hdb, hdb1 is the swap (1GB) and the hdb2 is the native Linux partition (40 GB), both have as file system the reiserfs.
Now, like mrmarmmalade above, I get the "loading windows" thing, and nothing else. Here is what lilo says about the 0x80 thing in the windows stanza:
Unrecognized token "boot-as" at or above line 45 in file '/etc/lilo.conf'
If I try the "bios=0x80" lilo says there is a syntax error.
Any help would be keen.
Thanks,
Dan
the config looks alright to me, maybe your version of lilo is too old, IIRC the "boot-as" directive is not supported in versions below 22.5.5.
assuming you only have 2 harddrives, try this one:
Hi,
excuse me for the newbie-question, but how did you configure the GRUB loader (or probably it should be the LILO one?) in order to be able to boot from hdb without hda?!
I'm trying just the same thing with my SuSE 9.0 but it doesn't work. I have to put the bootloader (LILO or GRUB) into the MBR of hda in order to be able to boot the instalation on hdb.
When I put GRUB on MBR on the hdb disk, then it says just "GRUB " and freezes on the screen, if I use LILO instead then the LILO prints one screen with "99"s and freezes too. Puting the bootloader in the /boot section of the the /root partition on hdb causes the BIOS not to recognize this disk as bootable and to proceed directly to the next boot disk (I use BIOS to switch the boot drives sequence to: 1st = HDD-1, wich is hdb, then 2nd = CDROM, 3rd = Floppy).
My SuSE 9.0 installation on hdb has only two primary partitions on hdb, hdb1 is the swap (1GB) and the hdb2 is the native Linux partition (40 GB), both have as file system the reiserfs.
Many thanks in advance.
Kind regards,
sbogus
Try installing GRUB manually using the GRUB shell, first create a /boot/grub/device.map file if it doesn't exist and make sure it has the following content:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.