On Mon, 29 Oct 2018, David - DCPC wrote:

Another cas where I use partitions is to avoid FS saturation on the root or important FS.

Yep.

Like if a log goes crazy, we can only freeze the /var fs, and then you can still manage the system. If the / is full, it's harder to debug (seen cases where even login was impossible with 0 byte free...), and sure that system crash and potential data lost.

Exactly. The Mac also shoves everything under / as well, and I don't like it for the same reasons. Those who believe in a single file system have obviously never experienced the joys of filling up the root file system.

I also have security concerns about world-writable directories e.g. /tmp and /var/tmp on the root file system.

Then again, what would I know?  I've been using Unix for only 40+ years...

But sure that i work more on servers than personnal laptop :)

Well, I use my laptops to access my FreeBSD server; here's its layout:

    aneurin% df -h
    Filesystem     Size    Used   Avail Capacity  Mounted on
    /dev/ad0s1a    496M    302M    154M    66%    /
    devfs          1.0K    1.0K      0B   100%    /dev
    tmpfs          989M     76K    989M     0%    /tmp
    /dev/ad0s1d    2.9G    1.4G    1.3G    53%    /usr
    /dev/ad0s1e    989M    538M    372M    59%    /var
    /dev/ad0s1f    3.9G    1.5G    2.1G    41%    /home
    /dev/ad0s1g    8.9G    7.1G    1.0G    87%    /usr/local
    fdescfs        1.0K    1.0K      0B   100%    /dev/fd
    procfs         4.0K    4.0K      0B   100%    /proc

Everything nice and isolated from each other...  Yes, it's a small system.

Interesting topic, even if i didn't have SSD for servers on recent install.

I still don't trust SSDs, because you never know what's really happening.

-- Dave

Reply via email to