Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Hiya,
I'm currently dual-booting win xp and ubuntu 8.04 on my desktop machine (dual-booting using grub). I'm now planning of getting rid of ubuntu and replacing with the slack 13.
There are a lot of tutorials online about dual boooting, and the slackbook also has a nice section on it as well but I'm not really sure what the best thing to do is given my current situation.
If I format my ubuntu partition and replace it with slackware i'll lose my grub config file (as it's in the ubuntu partition). Should i somehow "delete" grub, install slackware (and lilo), and then configure lilo to boot either my win xp or slack? If so how do i go about deleting or overwriting grub?
Assuming you format your current root partition, the grub config will be gone. Then you can install slack, with lilo. Just install lilo to the mbr, that will replace the mbr that now points to grub. The slack install should 'see' the XP install and create an entry for booting windbloze. If that fails for any reason, you can manually add an entry for windoze after you boot up slack.
Not a dumb question at all. Better to think ahead, than after the fact...
you have the choice when installing the new system (slackware) ... if you install it to the MBR, then it will become your new boot loader for all the systems and over write grub. If you install lilo to the slackware root partition... then you will have to manually edit grub to chainload lilo-slackware or the slackware kernel directly.
I have another machine that dual-boots slack and ubuntu, but i use grub on this. Think I wanna have a play with lilo as i've never used it before so i might go for the "overwriting grub" option.
Nothing wrong with learning to use something new. You can keep your grub by saving your configurations. Then adding the boot for your Slackware. This way if you desire to revert then things will be a lot easier.
I prefer 'lilo' myself but whenever testing anything that is alien I will save my current configuration(s) but that is easy since my test bench systems can be reverted with ease. I never work experiments on my production equipment or systems. Sure tweaks may be made but even those have been tested elsewhere.
When you say "Then adding the boot for your Slackware." is that the method where I should chose to install Lilo to my slack root partition thus keeping my grub in the mbr?
Does anyone have any experience with grub4dos as a boot loader... the website presents it as a silver bullet that will load all systems, usb, cd, iso and make your toast. Grub legacy that I stuck with because I can edit it manually, is being fazed out for grub2.. and I have not found it as stable as lilo. However lilo is not as fexible or as forgiving as grub legacy.
Hope this is not off the main subject here.
Does anyone have any experience with grub4dos as a boot loader... the website presents it as a silver bullet that will load all systems, usb, cd, iso and make your toast. Grub legacy that I stuck with because I can edit it manually, is being fazed out for grub2.. and I have not found it as stable as lilo. However lilo is not as fexible or as forgiving as grub legacy.
Hope this is not off the main subject here.
I'm using Grub4dos, I like it a lot better than Grub2.
There's also instructions to chainload from LILO on SlackBuilds (This is how I run it)
The menu.lst syntax is the same as Grub legacy
EDIT:
Something kind of annoying.
When you install Grub4dos to the MBR, it will move your old MBR to the second sector of your hard drive and on every boot it gives you 5 seconds to press the hotkey (spacebar) to load it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.