[opensuse-factory] again I ask
Hey Group; openSuSE 11.3 M6 What in the world causes every directory and file to be permission ending in a dot. It has made this system darn near useless. No application is able to write to a file. No program can pull up a previous saved file. Sample -rw-r--r--. 1 donn users 274 2009-06-13 17:53 signature.comcast drwxr-xr-x. 2 donn users 4096 2009-10-16 11:35 .skel/ drwx------. 3 donn users 4096 2010-03-04 21:04 .Skype/ drwxr-xr-x 2 donn users 4096 2010-02-24 22:59 .solarwolf/ drwxr-xr-x. 22 donn users 4096 2010-03-11 11:42 SQL/ drwxr-xr-x. 3 donn users 4096 2009-06-13 17:53 student/ drwxr-xr-x. 3 donn users 4096 2010-01-02 19:58 .subversion/ drwx------. 4 donn users 4096 2009-11-21 00:06 .thumbnails/ ^ | Note dot Every directory, sub directory and file end in this Which security program has caused this problem? -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb@comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb@arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On May 1, 10:16pm, Donn Washburn wrote:
drwxr-xr-x. 3 donn users 4096 2010-01-02 19:58 .subversion/ drwx------. 4 donn users 4096 2009-11-21 00:06 .thumbnails/ ^ | Note dot Every directory, sub directory and file end in this
Which security program has caused this problem?
Following the bunny trail, from ls through "info coreutils 'ls invocation'" leads to this: 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. So you have a SELinux security context that says "no access". HTH, Steve -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On May 1, 9:12pm, Space Case wrote:
So you have a SELinux security context that says "no access".
Or rather than "no access", I should say, "it's protected." Steve -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 05/02/2010 12:16 AM, Space Case pecked at the keyboard and wrote:
On May 1, 9:12pm, Space Case wrote:
So you have a SELinux security context that says "no access".
Or rather than "no access", I should say, "it's protected."
Steve
Looks like someone shot them self in the foot. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 05/01/2010 11:12 PM, Space Case wrote:
On May 1, 10:16pm, Donn Washburn wrote:
drwxr-xr-x. 3 donn users 4096 2010-01-02 19:58 .subversion/ drwx------. 4 donn users 4096 2009-11-21 00:06 .thumbnails/ ^ | Note dot Every directory, sub directory and file end in this
Which security program has caused this problem? Following the bunny trail, from ls through "info coreutils 'ls invocation'" leads to this:
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.
So you have a SELinux security context that says "no access".
HTH, Steve
This Selinux issue has caused me to completely reload after discovering that every directory and file was unuseable because of a "." This problem came from a zypper dup or up. Question is how do I get rid of the "." on my home directroy and files. -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb@comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb@arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On May 3, 4:58pm, Donn Washburn wrote:
On 05/01/2010 11:12 PM, Space Case wrote:
On May 1, 10:16pm, Donn Washburn wrote:
drwxr-xr-x. 3 donn users 4096 2010-01-02 19:58 .subversion/ drwx------. 4 donn users 4096 2009-11-21 00:06 .thumbnails/ ^ | Note dot
GNU `ls' uses a `.' character to indicate a file with an SELinux security context, but no other alternate access method.
So you have a SELinux security context that says "no access".
This Selinux issue has caused me to completely reload after discovering that every directory and file was unuseable because of a "." This problem came from a zypper dup or up.
Question is how do I get rid of the "." on my home directroy and files.
How to Disable SELinux http://www.crypt.gen.nz/selinux/disable_selinux.html Then, fix your contexts. I can't help you there. Steve -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Donn Washburn -
Ken Schneider - openSUSE -
wormey＠eskimo.com