Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Thanks Ript! I'll check it out later when I'm sober (just came backfrom a birthday party). Thanks again. I'll post here FFR if it works and details how to do it.
XOSL indeed appears to be a great bootloader, but was not the best solution for me, as it would have required repartitioning, reformating, and reinstalling both OS's.
Instead, I used the same procedure for GRUB as previously used for LILO, and it works great. See the original post for info on my hard disks.
For reference, during linux install, I chose to use GRUB instaed of LILO, and to put GRUB in the first part of /boot instead of in the MBR.
To get everything working right, here is what I did (all as root):
Boot into linux and get a command prompt (you have to use a boot disk to boot into linux at this point).
Type the following command, replacing "/dev/hda5" with the partition you made /boot:
dd if=/dev/hda5 of=/bootsect.lnx bs=512 count=1
This copies the first 512 bytes of the specified partition into the file bootsect.lnx
You will need to copy this file to your windows system drive root folder, in my case C: You can do this very easily if you have mounted your windows drive(s) in linux. Otherwise, copy it to a floppy, then boot into windows and copy it from the floppy to your windows system drive.
Once in windows, use notepad or another text editor and open C:\boot.ini
Windows will try and hide the file from you, but it is usually there.
Add the following line to the end of the file:
C:\bootsect.lnx="Redhat 7.2 Enigma"
Note that you can replace the text in quotes above with whatever text you want to appear in the windows bootloader menu list. Save your changes and close the file.
Open Start>>Settings>>Control Panel>>System. Click on the advanced tab, then click on Startup And Recovery. In the dialog box, you can choose the default OS to boot, and the timeout. Make any changes, then close the dialog box and reboot.
Choosing windows from NT's boot menu will load windows, and choosing linux will load GRUB. You can change GRUB's defaults (like you just did to windows) by editing the grub.conf file. Note that in GRUB, your menu choices are a zero-based list, meaning that the first menu item is #0, the second is #1, etc.
Set Default=N where N is the number of the OS you want to load by default.
Set Timeout=N where N is the number of seconds to wait before loading the default OS.
This solution worked for me; your milage may vary.
I knew there was a way to use the NT/2k/XP boot loader to load linux. I systemed my drive with win98 before I installed 2k, so I installed XOSL on that drive, yes without a "DOS" partition, XOSL isnt a good soulution. Scince I have become used to using XOSL, I always install NT/2K/XP that way, first sys the drive with 98/95 boot disk. I also forgot this step on XP, and wenjt ahead and sys'ed it anyway, then ran a repair form the XP setup, but it pretty much did a total re-install, but I did end up witl all my same settings, etc except the video driver and then I had "DOS" on the drive also..................
Yea, I had Lilo but I wanted somthing 3rd party, so if I decide to change anything, it doesnt affect my boot loader. Sided Lilo is like text...
call be a GUI head...
I am running Red Hat 7.2 and installed GRUB into the laptop instead of LILO. I am having problems configuring X for my screen and the only instructions available for it involved using LILO and changing lilo.conf to boot into VGA mode. How can I do this in GRUB? Alternatively, how can I get LILO to install into the MBR instead of GRUB?
I reinstalled RH 7.2 and chose the LILO option, but every time I boot up it appears that LILo has not been written into the MBR and GRUB (from a previous installation) comes up instead.
I currently have Win98 / Win 2K Advanced Server / RH7.2 on a single hard drive running from a RAID controller. I have GRUB installed to the MBR that either boots Linux or Windows.
When Windows is selected, the Windows 2000 multi-boot menu kicks in and allows you to select Windows 98 or 2000.
I guess I'm in the minority having GRUB in the MBR
I have got a simliar setup that seems to work fine I am dual booting redhat 7.2 with windows 98 and 2k I was told not to use grub for some reason i don't know why, So I have been using lilo and it works fine.
Hi guys. Well since this is a decussion between the two boot loaders Grub and lilo I just wanna give a little info.
I think Lilo is a wonderful bootloader, it usually always works correctly. The problem, which I am a witness of, is how easy it is to break into your computer and gain root access when you have lilo installed in your MRB. If you guys recall, lilo has like a 5 second period in which is lets you choose which OS to boot into. If you use what they call "legacy" lilo you get the nice gui lilo splash screen, and if you recall at the bottom left side it says to press ctrl+x if you want to input a command into the lilo prompt. Well, that is the main problem since when you get that prompt you only need 2 steps to gain root access to that linux box.
Anyway, this is the reason why I decided to change from lilo to Grub. However, i am not sure how much secure Grub is than lilo, and if you ask me, I would be reluctant to say a whole lot more but I think is at least less simple to gain root access than it is using lilo. They both are great bootloaders independet from how secure they are though.
Distribution: FreeBSD, OBSD maybe Gentoo and Winblech XP
Posts: 291
Rep:
boot pass
Well why would I give out my boot passwd?
I can also set one on the bios, and disallow booting from floppy or cd. Then again I agree. There must be some level of physical security. In fact I agree whole heartedly. Because security is a practice, not a technology. It's more of a series of technologies.
Security is like a castle. There is a stronghold. With lookouts in the towers, and a rampart or two. Accessed only by a drawbridge over a moat with crocodiles....on on a steep ridge....
I actually have an old 486 with a lock on it. It protects the power and reset buttons. I guess you can unplug it...but plugging it back in doesn't start it up.
I feel off topic. I wonder if marktaff acheived the config he desired.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.