4 ms·

That's fine with soft partitions like ZFS datasets, HAMMER pseudofilesystems or btrfs subvolumes. But OpenBSD doesn't have anything like that. The pain of "my /

That's fine with soft partitions like ZFS datasets, HAMMER pseudofilesystems or btrfs subvolumes. But OpenBSD doesn't have anything like that. The pain of "my /usr is not big enough and it's a hard disklabel partition with a completely separate filesystem omg how do I resize it" makes the partitioning sooooo not worth it.

Gracana 9y ago
This is not really an issue in practice, it just requires you to consider what you'll use the system for.
- majewsky 9y ago
  That's assuming that the answer to this question is constant. I'm frequently running into the problem of / being too small on my notebook (I only have /, /home and /boot partitions) since I didn't anticipate my 2017 needs when installing the system in 2012. I really need to set aside some time to reinstall it...
- the_af 9y ago
  This always makes me very anxious with Linux. I don't know beforehand what I'll use my laptop for, it's not a server! Some development, some gaming, some general use. Who knows? I always end up creating 3 partitions: /boot (is this really necessary?), a single huge /, and swap. I know a separate /home is recommended (something about backups and seamless distro upgrades, which I never do anyway), but I never know how to size it relative to /. I admit I do cargo-cult partitioning. I don't really know whether the recommendations out there are current, outdated, mistaken or what. I find a lot of recommendations about partitioning, swap, memory etc, at least for Linux, are cargo cult anyway, or at least outdated and/or poorly explained, which amounts to the same.
  - saghm 9y ago
    One potential solution for this is to use LVM, which lets you resize the partitions later. Even if you do just want to use /, /boot, and swap, it can be useful if you later want to change your swap size or reduce the root partition size to add new partitions if you decide you want to dual boot.
- floatboth 9y ago
  Easy example: create a 10gb EC2 instance with OpenBSD, start installing stuff, boom, you're out of space on some partition. But really, just having rigid partitions makes me feel uneasy. ZFS datasets all share the same space, and you can set quotas if you want that can be changed anytime.
  - Gracana 9y ago
    That is an example of not considering your use case and failing, yes. :P Flexible/resizable partitions are definitely easier, but I think you could have gotten the fixed scheme right if you had tried.
    - floatboth 9y ago
      When could I try? The scheme was already there: > create a 10gb EC2 instance

Gracana 9y ago

This is not really an issue in practice, it just requires you to consider what you'll use the system for.

majewsky 9y ago
That's assuming that the answer to this question is constant. I'm frequently running into the problem of / being too small on my notebook (I only have /, /home and /boot partitions) since I didn't anticipate my 2017 needs when installing the system in 2012. I really need to set aside some time to reinstall it...
the_af 9y ago
This always makes me very anxious with Linux. I don't know beforehand what I'll use my laptop for, it's not a server! Some development, some gaming, some general use. Who knows? I always end up creating 3 partitions: /boot (is this really necessary?), a single huge /, and swap. I know a separate /home is recommended (something about backups and seamless distro upgrades, which I never do anyway), but I never know how to size it relative to /. I admit I do cargo-cult partitioning. I don't really know whether the recommendations out there are current, outdated, mistaken or what. I find a lot of recommendations about partitioning, swap, memory etc, at least for Linux, are cargo cult anyway, or at least outdated and/or poorly explained, which amounts to the same.
- saghm 9y ago
  One potential solution for this is to use LVM, which lets you resize the partitions later. Even if you do just want to use /, /boot, and swap, it can be useful if you later want to change your swap size or reduce the root partition size to add new partitions if you decide you want to dual boot.
floatboth 9y ago
Easy example: create a 10gb EC2 instance with OpenBSD, start installing stuff, boom, you're out of space on some partition. But really, just having rigid partitions makes me feel uneasy. ZFS datasets all share the same space, and you can set quotas if you want that can be changed anytime.
- Gracana 9y ago
  That is an example of not considering your use case and failing, yes. :P Flexible/resizable partitions are definitely easier, but I think you could have gotten the fixed scheme right if you had tried.
  - floatboth 9y ago
    When could I try? The scheme was already there: > create a 10gb EC2 instance