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.
Is bootloader a must when you have one one os that is linux?
Does attaching the hard disk as primary master or primary slave make any difference?
What does no boot loader option actually do during installation?
I am getting grub> command prompt after installation without boot loader. Configured harddisk as primary slave.
A bootloader is a must, regardless of how many OSes there are, because the bootloader is the thing that loads the OS.
You can set the bootloader so it doesn't display a menu or wait for using action, but just boots: Then you don't have to interact with it. But it has to be there.
The Grub command line is a useful thing: You can boot into an OS from there easily. There's several guides on how to do it online
A bootloader is a must, regardless of how many OSes there are, because the bootloader is the thing that loads the OS.
You can set the bootloader so it doesn't display a menu or wait for using action, but just boots: Then you don't have to interact with it. But it has to be there.
The Grub command line is a useful thing: You can boot into an OS from there easily. There's several guides on how to do it online
I agree with you, What is the option no boot loader during installation prompted for?
A bootloader is a must, regardless of how many OSes there are, because the bootloader is the thing that loads the OS.
You can set the bootloader so it doesn't display a menu or wait for using action, but just boots: Then you don't have to interact with it. But it has to be there.
The Grub command line is a useful thing: You can boot into an OS from there easily. There's several guides on how to do it online
The linux boot sequence for x86 is very roundabout for historical reasons. Back in the day (and I mean waaaaay back in the day), the kernel was supposed to be bootable (raw). Part of the code that is now LILO was then in the kernel.
Nowadays, however, almost all OS's (including linux) require a separate bootloader to function.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Bootloader when only one OS
