[SOLVED] Grub2, moving /boot to separate partition
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.
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.
Yes but if you run update-grub it will change grub.cfg back plus any changes in distros that you have made. When I install grub2 to a separate partition I make my own grub.cfg and then disable os-prober. One easy way is to copy your grub.cfg from the installed linux distro and paste it in your new /boot/grub partition.
I chainload my partitions so I find it easier to build my own grub.cfg.
No, the code "knows" where it was installed from - based on the parameters passed to (or defaulted) the grub-install.
After doing the grub-install from the "old" configuration you need to update fstab for the new /boot, reboot or remount /boot to sda1, then (re-)run the update-grub. Things should then all be pointing in the correct direction(s).