Linux

48314 readers

412 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

115

What are the best practices to partition a linux system with? (lemm.ee)

submitted 1 year ago by [email protected] to c/[email protected]

53 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Molecular0079 5 points 1 year ago (2 children)

Nowadays you don't even need a /boot unless you're doing full disk encryption and I actually recommend keeping /boot on / if you're doing BTRFS root snapshots. Being able to include your kernel images in your snapshots makes rollbacks painlessly easy.

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (1 children)

UEFI forum made it a requirement for motherboard constructors (hp, dell, msi...) to make their UEFI implementation to be able to at least read fat(12/16/32) filesystems. That is why you need a fat(12/16/32) partition flagged ESP (efi system partition) for holding your boot files.

So, I dont think you can do that unless you fall back to the old outdated BIOS/MBR or you have some *nix filesystem in your uefi implementation which I dont trust.

[–] Molecular0079 1 points 1 year ago (2 children)

You're only partially correct. /boot doesn't have to also be your EFI partition. In fact, most distros by default will separate the two, with the EFI partition mounted at /boot/efi and /boot being a separate ext4 based partition. My suggestion is that, if you're running BTRFS, you should merge /boot and / as one partition. You're still free to have a FAT32-based EFI mounted at /boot/efi or better yet /efi.

[–] [email protected] 1 points 1 year ago (1 children)

I use systemd-boot and my mount point is /efi. /efi/EFI/ is where my bootloaders live.

If I rollback to an old enough snapshot, I have to reinstall my kernels from a chroot. It'd be cool if I could get around that.

[–] Molecular0079 1 points 1 year ago (1 children)

Where's your /boot?

[–] [email protected] 1 points 1 year ago

Separate FAT32 part.

[–] [email protected] 1 points 1 year ago (1 children)

It has been a while since I used grub that I forgot tgat esp could only be used to hold the boot files residing on /boot/efi.

[–] Molecular0079 2 points 1 year ago (1 children)

I am guessing you're on systemd-boot? Yeah, one of the reasons why I hesitate to use it is how it requires EFI contain the kernel images. I am currently using refind.

[–] [email protected] 1 points 1 year ago

Yeah, I'm on systemd-boot, it requires the kernel to be located in the ESP partition which I mount in /boot, resulting in cleaner setup.