Images 💾⌗

Last commit ⭐⌗ 

commit ed67a877a3998a968ebdec27cf210d2dbb6ca0da
Author:     Liav A <liavalb@gmail.com>
AuthorDate: Sat Jan 28 19:00:54 2023 +0200
Commit:     Andrew Kaster <akaster@serenityos.org>
CommitDate: Sat Feb 4 15:32:45 2023 -0700

    Kernel+SystemServer+Base: Introduce the RAMFS filesystem
    
    This filesystem is based on the code of the long-lived TmpFS. It differs
    from that filesystem in one keypoint - its root inode doesn't have a
    sticky bit on it.
    
    Therefore, we mount it on /dev, to ensure only root can modify files on
    that directory. In addition to that, /tmp is mounted directly in the
    SystemServer main (start) code, so it's no longer specified in the fstab
    file. We ensure that /tmp has a sticky bit and has the value 0777 for
    root directory permissions, which is certainly a special case when using
    RAM-backed (and in general other) filesystems.
    
    Because of these 2 changes, it's no longer needed to maintain the TmpFS
    filesystem, hence it's removed (renamed to RAMFS), because the RAMFS
    represents the purpose of this filesystem in a much better way - it
    relies on being backed by RAM "storage", and therefore it's easy to
    conclude it's temporary and volatile, so its content is gone on either
    system shutdown or unmounting of the filesystem.