VUMOUNT(1)

πŸ’– VUMOUNT(1) β€” the mount(1) girlies' manual page πŸ’–

okay bestie, welcome to the vumount page, part of the General Commands Manual situation. it's giving "i just want to talk to mount(2) directly, no middleman, no drama." let's get into it 🫢


✨ NAME ✨

vumount β€” mount a filesystem or a resource πŸ’…


🌸 SYNOPSIS 🌸

vumount [options ...]  source destination

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so, literally everything is (or can be seen as) a file. that's like, the whole philosophy of UNIX, no cap. the file hierarchy is the global naming facility. iconic behavior honestly.

VUOS follows this principle fr fr: VUOS modules use mount(2) not only to mount virtual filesystems but also to activate other virtual services. the mountpoint β€” that's the destination in the synopsis β€” is the name that will be used to identify the virtual entity/service. it's the main character of the naming situation πŸ‘‘

for example, in vudev it's possible to mount devices, in vunet the mountpoint is the name of the networking stack, and vustack(1) uses the path of the mountpoint to set the current stack for processes. slay.

vumount is just a command interface to mount(2). now, mount(8) is a whole complex tool which includes several features like the management of /etc/fstab and /etc/mtab. mount(8) is a root setuid executable and performs security checks before the actual mount(2) syscall request. mount(8) can be used in VUOS in place of vumount but it requires the (virtual) real uid of the executing process to be 0 (root). e.g. vusu(1) can be used to set the virtual real uid to 0.

vumount has been designed for VUOS but can be used to run the mount system call directly, without all the other management actions provided by mount(8).

🚨 important bestie: vumount is not setuid root. so like, know that about her.

πŸŽ€ OPTIONS πŸŽ€

  • -h, --help β€” print a short help message and exit. she's helpful and then she's gone πŸ’¨
  • -o list, --options list β€” comma-separated list of mount options
  • -t fstype, --types fstype β€” define the filesystem type
  • -r, --read-only β€” mount the filesystem read-only (same as -o ro)
  • -w, --rw, --read-write β€” mount the filesystem read-write (this is the default btw)
  • -B, --bind β€” mount a subtree somewhere else (same as -o bind)
  • -M, --move β€” move a subtree to some other place
  • -R, --rbind β€” mount a subtree and all submounts somewhere else

πŸ‘€ SEE ALSO πŸ‘€

umvu(1), vu_insmod(1), vu_lsmod(1), vu_rmmod(1), vuumount(1), vudebug(1)

go read those next, bestie, they're all part of the friend group 🫢


πŸ’œ AUTHOR πŸ’œ

VirtualSquare. Project leader: Renzo Davoli


and that's the whole page, periodt ✨ this cutie came to you from VirtualSquare-VUOS, dated November 2024, and yeah she's rocking that VUMOUNT(1) title at the top and the VUMOUNT(1) footer at the bottom, as she should πŸ’– bye bestie, go mount something πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from