Sys::F...:Linux(3pm)

📦 version 1.408, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu resolute, ubuntu stonking

💖 Sys::Filesystem::Linux 💖

okay bestie so listen — this is Sys::Filesystem::Linux, a lil Perl module from the User Contributed Perl Documentation corner of the universe (it's a 3pm page, iykyk). Its whole job? Handing Linux filesystem tea over to Sys::Filesystem. That's it, that's the gig. She's serving, she's iconic, she's lowkey just a little backend goblin doing the lord's work. 🧚

✨ NAME ✨

Sys::Filesystem::Linux — literally just returns Linux filesystem info back to Sys::Filesystem. no cap.

🌸 SYNOPSIS 🌸

okay so, plot twist: there's no synopsis of its own here.

See Sys::Filesystem. that's the whole thing bestie, go look over there 💅

🦋 INHERITANCE 🦋

the family tree, and it's giving lineage:

Sys::Filesystem::Linux
ISA Sys::Filesystem::Unix
  ISA UNIVERSAL

she got it from her mama, who got it from UNIVERSAL. generational excellence fr fr 👑

🎀 METHODS 🎀

  • version () — returns the version of the (sub)module. that's it. that's the method. short queen behavior. ✨

🌈 ATTRIBUTES 🌈

so here's the list of filesystem properties you can query as methods through the parent Sys::Filesystem object. not me getting emotional over a properties list 😭

  • fs_spec — describes the block special device, or the remote filesystem, that's about to get mounted.

for ordinary mounts it's gonna hold (a link to) a block special device node — the kind mknod(8) makes — for the device being mounted, like /dev/cdrom or /dev/sdb7. for NFS mounts you get <host>:<dir>, e.g. knuth.aeb.nl:/. and for procfs, you just write proc.

and instead of naming the device directly, you can point at the (ext2 or xfs) filesystem by its UUID or volume label (peep e2label(8) or xfs_admin(8)), writing LABEL=<label> or UUID=<uuid>, like LABEL=Boot or UUID=3e6be9de-8139-11d1-9106-a43f08d823a6. and why would you do that? because it makes the system way more robust, bestie: adding or removing a SCSI disk changes the disk device name but NOT the filesystem volume label. glow up achieved 💅

  • fs_file — describes the mount point for the filesystem. for swap partitions this field should be specified as none. and if the name of the mount point has spaces in it, those can be escaped as \040. sneaky but valid.
  • fs_vfstype — describes the type of the filesystem. (yes, the original says "Dscribes", we're all doing our best here 🙈)

Linux supports so many filesystem types, like: adfs, affs, autofs, coda, coherent, cramfs, devpts, efs, ext2, ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs, nfs, ntfs, proc, qnx4, reiserfs, romfs, smbfs, sysv, tmpfs, udf, ufs, umsdos, vfat, xenix, xfs, and possibly others. the range?? unmatched.

for more details, see mount(8). for the filesystems currently supported by the running kernel, see /proc/filesystems. an entry of swap denotes a file or partition to be used for swapping — cf. swapon(8). an entry of ignore causes the line to be ignored, which is genuinely useful for showing disk partitions that are currently unused. periodt.

  • fs_mntops — describes the mount options associated with the filesystem.

it's formatted as a comma separated list of options. it contains at least the type of mount, plus any additional options appropriate to the filesystem type. for docs on the available options for non-nfs file systems, see mount(8). for documentation on all the nfs-specific options, have a look at nfs(5).

common to all types of file system are these options:

  • noauto — do not mount when mount -a is given, e.g. at boot time
  • user — allow a user to mount
  • owner — allow the device owner to mount
  • _netdev — the device requires network to be available

heads up: the owner and _netdev options are Linux-specific. for more details, see mount(8). 🫶

  • fs_freq — used for these filesystems by the dump(8) command to figure out which filesystems need to be dumped. if the fifth field isn't present, a value of zero is returned and dump will assume that the filesystem does not need to be dumped. chill.
  • fs_passno — used by the fsck(8) program to determine the order in which filesystem checks get done at reboot time. the root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize the parallelism available in the hardware. if the sixth field isn't present or is zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked. multitasking king 🧚

👑 SEE ALSO 👑

  • Sys::Filesystem
  • Sys::Filesystem::Unix
  • fstab(5)

💜 AUTHOR 💜

Copyright 2004,2005,2006 Nicola Worthington.

Copyright 2009-2020 Jens Rehsack.

This software is licensed under The Apache Software License, Version 2.0.

<http://www.apache.org/licenses/LICENSE-2.0>

legal girlies stay winning 💅 read the license, it's short and it's serving.

okay and that's the whole page babes, tysm for reading 🫶 this was perl v5.30.3, dated 2020-10-24, and honestly? she ate. no crumbs. mwah 💖✨🌸

📦 where this page comes from