Hello
Joseph Jones (<[EMAIL PROTECTED]>) wrote:
> /dev/hdb1 gets set to read-only when I do any of these:
>
> Any kind of chmod command on anything in the mountpoint.
> And kind of deletion with KDE.
>
> I'm running Sid.
What Kernel do you use? What file system do you use? What does
/var/log/
/dev/hdb1 gets set to read-only when I do any of these:
Any kind of chmod command on anything in the mountpoint.
And kind of deletion with KDE.
I'm running Sid.
Please help!
Joe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Lo, on Monday, January 15, Thomas J. Hamman did write:
> On Mon, Jan 15, 2001 at 03:11:53AM -0600, Rob VanFleet wrote:
> I have a related question: How come almost every file in my home
> directory has s or S permissions set? Even if I change them to x, I
> find later on th
Lo, on Monday, January 15, Fernando Carvajal did write:
> it's the suid bit but the file have no execution permission
Minor nit, but drw-r-Sr-- is actually the set*gid* bit; setuid would be
drwSr--r--.
Richard
On Mon, Jan 15, 2001 at 03:11:53AM -0600, Rob VanFleet wrote:
> I know what s is, when designated in the permissions of a file, but what
> does a capitol 'S' stand for? ie:
>
> drw-r-Sr--
I have a related question: How come almost every file in my home
directory has
Rob VanFleet wrote:
> On Mon, Jan 15, 2001 at 03:34:04AM -0600, Rob VanFleet wrote:
> > Why would that exist on a directory one just untarred?
> Ugh, never mind about the above, I wasn't thinking.
>
> Any clues as to why I would not be able to cd into the directory though?
You need the 'x' bit se
On Mon, Jan 15, 2001 at 03:34:04AM -0600, Rob VanFleet wrote:
> Why would that exist on a directory one just untarred?
Ugh, never mind about the above, I wasn't thinking.
Any clues as to why I would not be able to cd into the directory though?
> I noticed this
> right after I untarred a tar.gz an
On Mon, 15 Jan 2001, Rob VanFleet wrote:
> I know what s is, when designated in the permissions of a file, but what
> does a capitol 'S' stand for? ie:
>
> drw-r-Sr--
It means the s bit is set, but the x bit is *not* set.
Not used very much...
On Mon, Jan 15, 2001 at 10:21:01AM +0100, Fernando Carvajal wrote:
> it's the suid bit but the file have no execution permission
Why would that exist on a directory one just untarred? I noticed this
right after I untarred a tar.gz and was subsequently unable to cd into
it, for why I don't know.
Fleet [mailto:[EMAIL PROTECTED]
Enviado el: lunes 15 de enero de 2001 10:12
Para: debian-user@lists.debian.org
Asunto: 'S' permissions
I know what s is, when designated in the permissions of a file, but what
does a capitol 'S' stand for? ie:
drw-r-Sr--
-Rob
--
To UNS
I know what s is, when designated in the permissions of a file, but what
does a capitol 'S' stand for? ie:
drw-r-Sr--
-Rob
11 matches
Mail list logo
