On Wednesday 26 March 2008 21:30, Michael Stone <[EMAIL PROTECTED]> wrote: > >Character 10 in "ls -l" output can have values from "xtT", character 7 can > >have values from "xsS", and character 1 can have many values. > > Yes, and we've learned that it's pretty confusing. It will be even more
Obviously opinion varies, I didn't find it any more confusing than the rest of the "ls -l" output when I was learning how ls works. > confusing for a non-standard set of character codes than it is for a set > that have been used for decades. We've already identified a need for > 3 bits of information encoded into that byte, and I suspect that it's I'm not sure that Jim was really serious about the user-xattr. > not impossible that there'd be more. The more I think about it, the more > uploading a version with a space in the next couple of days, because > working out a long-term fix is probably going to take a while. That would be good. Have Lenny be the same as Etch in this regard. What we REALLY don't want to do is to have Lenny do something one way and then decide in Lenny+1 that it was wrong and back it out. > Right, that's why I thought that using + unconditionally for acls was a > good idea. (I think it's less likely that existing processes would be > special casing selinux based on ls output; it would be easier for a > script to simply check up front whether selinux was in use.) Yes, programs that do things related to SE Linux will run a program such as "getenforce" and then change their operation based on it's output. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
