In Linux, I've created the root file system (rootfs) by following commands: dd if=/dev/zero of=ramdisk.img bs=1M count=4 mkfs.ext2 ramdisk.img sudo mount -o loop ramdisk.img rootfs sudo cp init ...
If I do mount -o bind /my/dir /mnt/tmp, I can see the content of /my/dir within /mnt/temp. However, if I type cat /proc/mounts, I get the following output: /dev/sda7 /my ext4 ...
I'm getting the following output when the mount command is executed. [root@]# mount /dev/sda2 on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type ...
I'm struggling with a program that creates a file system in a file and mounts it as a loopback device. The purpose of the program is to create a clone of the root file system and it thinks it's being ...
IIRC then the mount options shown in /proc/mounts have changed. Some time ago acl and user_xattr were shown, now it seems that only noacl and nouser_xattr are shown if these features are turned off. ...
Why does Linux require that a user be root/using sudo/specifically authorized per mount in order to mount something? It seems like the decision as to whether to allow a user to mount something should ...