31

A fair while ago (~ 2004) I was told to always create a separate partition for the boot directory. And since then I always have. But after reading a few questions about partitioning questions, I'm curious. Do I still need a /boot partition?

Note: If helpful, I'm dual booting (Win XP or 7) & Ubuntu 10.04. I also have one partition (using ext2/3) which I use to share files between the two operating systems.

M. Tibbits
  • 1,378

3 Answers3

33

If you don't use LVM, root volume encryption, software RAID, etc., and otherwise just have your root volume on a plain-jane filesystem with no intermediate layers, then you don't need it.

Really, the most important files in booting are the kernel image (vmlinuz) and the initramfs image (initrd.img). If both of those (and the GRUB configuration files) are accessible by GRUB with no special handling, then a separate /boot volume is not necessary.

  • My question is probably enough of a duplicate to close, but your answer intrigues me. I do use LVM on my webserver & there I must use a separate boot partition -- but I guess this is the only condition to really use one. Thanks to "@Chris Jester-Young" and @Jorge! – M. Tibbits Oct 12 '10 at 17:40
  • 6
    Since Grub2 (i.e. since Ubuntu 9.10), LVM doesn't require a separate LVM partition. (Even before, Lilo had supported LVM for a long time, but of course has the downside of not being Grub.) Software RAID-1 never required a separate /boot, and Grub2 now supports most (all?) of Linux's RAID modes, as well as some encryption modes. The upshot is that there's very rarely a need for a separate /boot nowadays. – Gilles 'SO- stop being evil' Oct 12 '10 at 21:06
10

Generally speaking, unless you're dealing with encryption, or RAID, you don't need a separate /boot partition.

That said, I occasionally find a use for adding a separate /boot partition as a FAT partition. This allows your dual-boot system to make alterations to your GRUB config, so you can create a batch file to shut down windows and alter the default menu choice so that it boots something else next. Most people don't need this, but I've had a few projects which required switching back and forth, and it allows it to be done entirely by script.

Perkins
  • 636
  • And won't a /boot partition easier to backup, in case of frequent OS removals/addings? – Quidam Apr 24 '20 at 12:08
  • @Quidam Not really any easier to back up, but if you have multiple Linux OS installs it can be easier to keep all their boot files together depending on just how you're using the setup. – Perkins Apr 27 '20 at 22:10
5

This response probably answers your question:

Generally speaking, you shouldn't bother with a separate /home or /boot partition unless you're running multiple Linux distributions at once.

The Ubuntu installers for both the desktop CD and server/alternate CD have the ability to install over an existing system, preserving your home directory (and the local system driectories: /usr/local, /usr/src, and /var/local). This functionality also reuses the user ID and group ID of an existing user, if it has the same username as the user you're creating during installation.

To use this option when installing, choose the option for advanced partitioning, then select your existing / or /home partition. In the box that appears, make sure the filesystem selected matches the existing filesystem of that partition, and that the format box is not checked. Proceed as normal through the rest of the options.

In Ubuntu 10.10 we had hoped to add an option to the installer that detected when you had an existing copy of Ubuntu installed and offered to replace it with the newer version you were attempting to install (using the aforementioned functionality behind the scenes). While it did not make the final cut, it is likely to arrive in Ubuntu 11.04.

As for a separate /boot partition, that's a relic of hardware constraints of the past (the bootloader 1024 cylinder limit). I can think of no practical advantage a separate /boot would have on a modern system, and if not given an arguably excessive amount of space, it will potentially fill up and create problems of its own, given that Ubuntu does not automatically remove old kernels.

Jorge Castro
  • 71,754