Tag Info

New answers tagged

1

Use normal Linux/Unix permissions on your dude/photos to make sure that popolo can't access them. Assuming that popolo isn't the owner of those files and directories and isn't in the group, then a simple chmod -R o-rwx dude/photos should make sure that popolo can't access those files. Or: An alternative way would be to give popolo and empty chroot home ...


0

NVM - It was formatting, I needed to use a comma between users and rw instead of a dash


3

Linux definitely does provide the tools to do this automatically. Rather than using mount, you should be using findmnt. man mount 2>/dev/null | grep -m1 -B1 findmnt For more robust and customizable output use findmnt(8), especially in your scripts. printf '%s%s 0 0\n' '/dev/disk/by-uuid/' \ "$(findmnt -n -o ...


0

You need to manually edit the file fstab. To find out what to put in there, issue the mount command and look at its output.


1

Files in /proc are generated by the kernel, not by the mount utility. The kernel omits options that are in their default kernel setting. The defaults of the mount utility don't always match the kernel defaults. You can check the defaults for your kernel version in the source code, in fs/proc_namespace.c. For example, as of version 3.15, noexec is displayed ...


1

man mount has a good list. But induvidual filesystem can define their own flags -> there is a separate list for every filesystem. But there are common flags and they are listed on the mount manpage. exec is a default flag. The list of the defaults mount flags are also in the man mount (AFAIK in the kernel sys_mount() syscall there is no such thing). But if ...


2

The reason is probably that exec is the opposite of noexec, and it is noexec that is listed. Thus if noexec is absent, the user knows that exec is in effect. This is similar to dev / nodev. It seems that the exception is rw, which is listed even though it is in the default list. Note: while the mount(8) man page says that defaults is a fixed list of default ...


0

If 0, dump will ignore the file system; This statement is incorrect: -level# The dump level (any integer). A level 0, full backup, specified by -0 guarantees the entire file system is copied (but see also the -h option below). A level number above 0, incremental backup, tells dump to copy all files new or ...


1

Try changing options => "-o loop", to options => "loop", The error shows mount -o -o loop so you'd want to get rid of one of the -o arguments


1

From man fstab: Instead of giving the device explicitly, one may indicate the (ext2 or xfs) filesystem that is to be mounted by its UUID or volume label (cf. e2label(8) or xfs_admin(8)), writing LABEL= or UUID=, e.g., 'LABEL=Boot' or 'UUID=3e6be9de-8139-11d1-9106- a43f08d823a6'. This will make the system more robust: adding or removing a ...


1

Unfortunately not. From man mount: the user must be member of the group of the special file. Note that it says special file and not mount point. If you run ls -l against your partitions you'll note that the group owner is disk. Therefore, make user1 a member of the disk group and he/she will be able to mount the partition as long as the group ...


1

In the following, LABEL can be anything you want, /dev/sdb1 is the partition you create and choose to use on your new HDD and /var/www/myfiles is where your files are currently located. Alter these to suint your scenario. Partition the new HDD. You can have one partition that takes up the whole disk, or make a smaller partition which leaves you space on ...


1

In the end, I've followed the advices of @frostschutz. I've used an encrypted LV as key ! lvcreate -L 4M -n LogVolKey vg cryptsetup luksFormat /dev/vg/LogVolKey (here we set the global passphrase) cryptsetup luksOpen /dev/vg/LogVolKey LogVolKeyDecrypted dd if=/dev/urandom of=/dev/mapper/LogVolKeyDecrypted cryptsetup luksFormat /dev/vg/LogVolXxx (here we ...


1

Don't know what OS you are using; but FreeBSD best-practice for this sort of thing is to use glabel to attach a label to the file system. Then the labels appear as /dev/ufs/[label] and you use that in your fstab specification. For example, if these are USB devices and they all autoconfig alternatively to /dev/ad0s0a, /dev/ad2s0a, and /dev/ad3s0a, you can ...


1

As far as I'm aware mount doesn't scan past the first match. One thing you could do (should consider?) is to set-up udev rules that create the same symlink for all your NTFS disks under /dev ... then a single line in fstab will do for any/all of them.



Top 50 recent answers are included