On Sat 12 Jul 2025 at 02:51:25 (+), David wrote:
> Again: when you mount something on a mountpoint, all underlying data of
> that mountpoint becomes hidden and inaccessible and irrelevant.
In linux, that isn't entirely true, as you can use a bind mount
to read what lies "underneath". (I haven
On Sat, Jul 12, 2025 at 02:51:25AM +, David wrote:
In fact it has been my practice for some years now to 'chown root:' and
'chmod 0' on all my mountpoints and set the immutable bit on them, to avoid
accidentally writing into directories that are intended only as
mountpoints.
And I have never
David wrote:
> Something that I am curious to learn more about, if anyone has ideas, is
> the discussion at the above link about the need to have at least 'chmod
> 111' on mountpoint directories.
>
> I have not found that necessary, and so I wonder if that advice is
> outdated, or somehow not rel
On Fri, 11 Jul 2025 at 18:49, Hans wrote:
> > Permissions are stored for the root directory of each filesystem, which
> > are used as the permissions of the mount point when the drive is
> > mounted.
> Thanks, this is explaining all my questions. I always thought wrong, that
> mounted devices an
> Permissions are stored for the root directory of each filesystem, which
> are used as the permissions of the mount point when the drive is
> mounted.
Thanks, this is explaining all my questions. I always thought wrong, that
mounted devices and folders on it, get the ownership from the folder, i
Hans wrote:
> > You have to chown/chmod the mount point *after* the drive is mounted. If
> > you do it before the drive is mounted it won't have any effect on the
> > mounted drive. (As you can see.) I really am not sure what else to say,
> > this is how it works.
>
> Ok, I did as adviced. Change
On Fri, Jul 11, 2025 at 08:19:47PM +0200, Hans wrote:
Just for understanding: What does this procedure affect? Does ist set the
ownerships to this device or does it somehow let the kernel remember or is
this owneship stored somewher else?
Permissions are stored for the root directory of each fi
On 7/11/25 20:02, Hans wrote:
Where are the permission be set at the drive? It is just a hardware without
any folders or files on. Freshly formatted. What can be done wrong at this?
Nothing is wrong. After a fresh format (mke2fs) the root directory
belongs to root:root, and that is what you se
> You have to chown/chmod the mount point *after* the drive is mounted. If
> you do it before the drive is mounted it won't have any effect on the
> mounted drive. (As you can see.) I really am not sure what else to say,
> this is how it works.
Ok, I did as adviced. Changed permissions and ownersh
On Jul 11, 2025, Hans wrote:
> Dear list,
>
> I am struggeling with a strange behavior when automounting my inbuilt
> harddrives.
>
> I have 3 harddrives, which are mounted to
>
> /space(sdc1) ext4
> /daten1 (sdd1) ext4
> /daten2 (sde1) ext4
>
> So all are the sam
On Fri, Jul 11, 2025 at 08:02:48PM +0200, Hans wrote:
Why wasn't it what you "wanted"? It answers your questions.
What I want is, starting the machine and want all 3 drives automatically been
mounted with the same rights (here: like /daten1 and /space)
Do what you were told is the proper proc
> Why wasn't it what you "wanted"? It answers your questions.
What I want is, starting the machine and want all 3 drives automatically been
mounted with the same rights (here: like /daten1 and /space)
I do NOT want to remount it manually at every boot.
>
>
> Because you are probably confused
On Fri, Jul 11, 2025 at 07:29:15PM +0200, Hans wrote:
This is not, what I wanted. The questions are:
1. Why does this happen only with one of the 3 drives?
You probably set the permissions on the other two drives after they were
mounted.
Hi,
On Fri, Jul 11, 2025 at 07:29:15PM +0200, Hans wrote:
> > The ownership of the underlying mount point is ignored (and should
> > generally be set to root:root mode 755 to avoid possible complications
> > in odd cases). You need to chown the directory *after* it is mounted.
>
> This is not, wh
> The ownership of the underlying mount point is ignored (and should
> generally be set to root:root mode 755 to avoid possible complications
> in odd cases). You need to chown the directory *after* it is mounted.
This is not, what I wanted. The questions are:
1. Why does this happen only with o
On Fri, Jul 11, 2025 at 07:06:19PM +0200, Hans wrote:
So all are the same, and the mountpoints shall all have
ownership user:group = root:backup
However, the latest harddrive I added, wbhich is sde1 shows wrong ownerhips,
The ownership of the underlying mount point is ignored (and should
ge
Dear list,
I am struggeling with a strange behavior when automounting my inbuilt
harddrives.
I have 3 harddrives, which are mounted to
/space (sdc1) ext4
/daten1 (sdd1) ext4
/daten2 (sde1) ext4
So all are the same, and the mountpoints shall all have
ownership user:group = r
On 23 Jul 2024 14:49 -0300, from edua...@kalinowski.com.br (Eduardo M
KALINOWSKI):
> As described on the sshfs manpage, by default only the mounting user (root,
> in your case) can access the filesystem.
>
> You can use -o allow_other to allow other users. Or, if it's only eben
> that'll be acces
On 23/07/2024 14:40, Eben King wrote:
And after I issue this command:
root@cerberus:~# sshfs -o default_permissions
sshd@white_mycloud:/mnt/HD/HD_a2/Public /mnt/white_mycloud/
sshd@white_mycloud's password:
By the prompt (and the behavior below) I assume you're mounting as root.
it looks like
I have an older WD Mycloud Connect NAS. I'm currently trying to mount it
via sshfs (I prefer NFS, but can't make it work either). When it's not
mounted, /mnt looks like this to me:
eben@cerberus:~$ \ls -l /mnt
total 16
drwxr-xr-x 2 root root 4096 Mar 11 23:39 server
drwxr-xr-x 2 root root 4096
On Sun 04 Jun 2023 at 11:59:21 (-0400), ce wrote:
> I have a mountpoint where all files under it have a group `fuse`.
>
> This is strange to me.
>
> As far as I can remember, Ubuntu doesn't do this.
Is this a system that's been around since wheezy? Up until then,
Debian had a system group called
I think you have a partition with filesystem btrfs that uses compression
with lzop.
Perhaps inside of it you have a file that is a compressed filesystem (that
is fuse: *Filesystem in Userspace* )
what can you see when you type in
$ cd /mnt/part2
$ ls -la
El lun, 5 jun 2023 a las 6:32, ce () escr
On 6/5/23 7:23 AM, Greg Wooledge wrote:
>
> You can run the command "mount" with no arguments to see the details of
> each mounted file system. You don't even have to be root. I don't know
> how btrfs subvolumes work, so I don't know whether they appear in the
> output of mount, but you could
On Sun, Jun 04, 2023 at 11:00:18PM -0400, ce wrote:
> On 6/4/23 5:46 PM, Greg Wooledge wrote:
> > What kind of hardware is this file system on?
> >
> > What kind of file system is it?
> >
> > How did you mount it? (Show the command you used, and any output that
> > it produced.)
> >
> > What does
On 6/4/23 5:46 PM, Greg Wooledge wrote:
> On Sun, Jun 04, 2023 at 11:59:21AM -0400, ce wrote:
> > I have a mountpoint where all files under it have a group `fuse`.
>
> You need to provide details, or else nobody can help you with anything.
>
> What kind of hardware is this file system on?
>
> Wh
On Sun, Jun 04, 2023 at 11:59:21AM -0400, ce wrote:
> I have a mountpoint where all files under it have a group `fuse`.
You need to provide details, or else nobody can help you with anything.
What kind of hardware is this file system on?
What kind of file system is it?
How did you mount it? (S
I have a mountpoint where all files under it have a group `fuse`.
This is strange to me.
As far as I can remember, Ubuntu doesn't do this.
On 9/2/17, 6:01 AM, Eduardo M KALINOWSKI wrote:
On 02-09-2017 09:29, Federico Beffa wrote:
I'm using Debian Stretch with Gnome. When I plug-in an external USB
hard drive (ext4) it gets automatically mounted at /media/beffa/label.
but the device is still only writable by root.
How can I tell t
Federico Beffa writes:
> Hi,
>
> I'm using Debian Stretch with Gnome. When I plug-in an external USB
> hard drive (ext4) it gets automatically mounted at /media/beffa/label.
> However, the drive is read-only for the user owning the Gnome shell
> (beffa). I've tried adding default ACL entries to /
On 02-09-2017 09:29, Federico Beffa wrote:
> I'm using Debian Stretch with Gnome. When I plug-in an external USB
> hard drive (ext4) it gets automatically mounted at /media/beffa/label.
>
>
> but the device is still only writable by root.
>
> How can I tell the system to make it writable for the us
Hi,
I'm using Debian Stretch with Gnome. When I plug-in an external USB
hard drive (ext4) it gets automatically mounted at /media/beffa/label.
However, the drive is read-only for the user owning the Gnome shell
(beffa). I've tried adding default ACL entries to /media/beffa as
follows
# file: .
#
On Tue, May 11, 2004 at 03:15:12PM +0100, Matthew Kay wrote:
> Hi,
>
> I'm trying to mount my windows NTFS partition with
> this line in my fstab:
>
> /dev/hda1 /mnt/winntfs
> rw,auto,users,exec 0 0
>
Try
/dev/hda1 /mnt/winntfs ro,auto,users,exec,umask
On Tue, May 11, 2004 at 03:15:12PM +0100, Matthew Kay wrote:
> Hi,
>
> I'm trying to mount my windows NTFS partition with
> this line in my fstab:
>
> /dev/hda1 /mnt/winntfs
> rw,auto,users,exec 0 0
>
> It works fine with this or read-only (ro) option,
> for root, bu
hi ya matt
On Tue, 11 May 2004, Matthew Kay wrote:
> /dev/hda1 /mnt/winntfs
> rw,auto,users,exec 0 0
>
> It works fine with this or read-only (ro) option,
> for root,
root can do anything to itself, but necessarily to
a remote partition on a different machine
> but
Hi,
I'm trying to mount my windows NTFS partition with
this line in my fstab:
/dev/hda1 /mnt/winntfs
rw,auto,users,exec 0 0
It works fine with this or read-only (ro) option,
for root, but I can't get it to stay
user-readable. When I mount it as read-only I
can't ch
> when my FAT32 file systems are mounted at
> boot time the owner and group are "root".
> As a regular user I can read files but not
> write them.
>
> I have the user option in my /etc/fstab file
> like so:
> /dev/hdc6 /matrox/mx6 vfat defaults,user 0 2
>
> so I can `umount' and then `remount' a
On Fri, Oct 27, 2000 at 10:06:16PM -0700, Mr. Strockbine wrote:
> when my FAT32 file systems are mounted at
> boot time the owner and group are "root".
> As a regular user I can read files but not
> write them.
>
> I have the user option in my /etc/fstab file
> like so:
> /dev/hdc6 /matrox/mx6 vf
Use 'noauto' as an option in your fstab entry-- see man fstab .
On Fri, Oct 27, 2000 at 10:06:16PM -0700, Mr. Strockbine wrote:
> when my FAT32 file systems are mounted at
> boot time the owner and group are "root".
> As a regular user I can read files but not
> write them.
>
> I have the user op
when my FAT32 file systems are mounted at
boot time the owner and group are "root".
As a regular user I can read files but not
write them.
I have the user option in my /etc/fstab file
like so:
/dev/hdc6 /matrox/mx6 vfat defaults,user 0 2
so I can `umount' and then `remount' as a regular
user and
On 1 Feb 98 at 11:18, Remco Blaakmeer wrote:
> On Sun, 1 Feb 1998, Art Lemasters wrote:
> > Now, for the reason this is coming from my M$ OS.
> > I mounted a second, older hard drive to use as /home.
> > Although I set permissions for the one user (me) with
> > chown and chmod, I still do no
On Sun, 1 Feb 1998, Art Lemasters wrote:
> Now, for the reason this is coming from my M$ OS.
> I mounted a second, older hard drive to use as /home.
> Although I set permissions for the one user (me) with
> chown and chmod, I still do not have access to the
> device (/dev/hdc1 mounted in /ho
Now, for the reason this is coming from my M$ OS.
I mounted a second, older hard drive to use as /home.
Although I set permissions for the one user (me) with
chown and chmod, I still do not have access to the
device (/dev/hdc1 mounted in /home). Do any of you
have any ideas as to the cause o
42 matches
Mail list logo
