The x isn't just "execute"...my understanding is that it's also akin to
"file access"
On Thu, 2 Nov 2000, David Brett wrote:
> Hi SoloCDM
>
> I though 'w' gave acces to writing files. Why would 'x' access be
> required to write a file via tftp?
>
>
> david
>
> On Wed, 1 Nov 2000, SoloCDM wrote:
>
> > > On Wed, 1 Nov 2000, David Brett wrote:
> > >
> > > > Hi Mike
> > > >
> > > > Here is the access rights of the directory:
> > > > -rw-rw-rw- 1 root root 0 Nov 1 09:45 test.txt
> > > >
> > > >
> > > > This is what the logs show when I attempt to write to the directory via
> > > > tftp:
> > > >
> > > > Nov 1 09:49:29 mxw-monitor tftpd[24848]: tftpd: trying to get file:
> > > > test.txt
> > > > Nov 1 09:49:29 mxw-monitor tftpd[24848]: tftpd: serving file from
> > > > /tftpboot
> >
> > All directories, files, mounted directories, etc. are files in a Linux
> > environment/OS, to eliminate unnecessary tediousness. The bits decide
> > what the Linux OS will do with the files. To have a files perform an
> > executions -- they need the "x" bit set.
> >
> > In other words, you can read and write to a directory name, but it
> > won't allow visibility, writing, or reading under its name until you
> > set the "x" bit.
> >
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
