Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
That indicates an alternate file access control method applies, such as ACLs or from SELinux.
A quick DDG search found multiple references to this:
Code:
From info coreutils 'ls invocation'...
Following the file mode bits is a single character that specifies
whether an alternate access method such as an access control list
applies to the file. When the character following the file mode
bits is a space, there is no alternate access method. When it is
a printing character, then there is such a method.
GNU `ls' uses a `.' character to indicate a file with an SELinux
security context, but no other alternate access method.
A file with any other combination of alternate access methods is
marked with a `+' character.
Thks guys
In fact, I'm trying to share a NTFS Harddisk in an Ubuntu environment...and I find some problems with the rights...
Might be, working on the ACL acces will help me solving my sharing problems ( sharing NTFS disk an a Linux Ubuntu environment )
thks for the tips
I have this line in my /etc/fstab
/dev/sdc6 /media/claude/partage ntfs-3g -o rw,uid=1000, gid=1000, utf8, umask=0022 0 1
With this umask, I should have the following rights rwxr-xr-x associated to the mount point partage no ?
but when the HD gets mounted
1) partage belongs to root , root with rwxrwxrwx rights !!!
In additon, once mounted, if I issue a simple mount command, here is what I'm getting
/dev/sdc6 on /media/claude/partage type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
Why the hell, what I wrote in the fstab is not taken into consideration ...
Pretty confused !!!
and thks again for any clarification
Also, was that from a manually issued mount command? If so, you need to give the mount command just one non-flag argument, either the device or the mount point. That will make the command look at /etc/fstab for the other argument, and it will pick up the options too. If you give both the device and the mount point, /etc/fstab is not consulted at all and you get the kernel's default mount options.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.