On Wed, Mar 26, 2008 at 04:12:15PM +1100, Russell Coker wrote:
How much can you fit into one char before it gets confusing?
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
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
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.
Actually I'm more worried about the ease of machine parsing of ls output. I'm
sure that someone will suggest a better option than having a shell script
grep ls output, but there are a lot of people who are used to grepping ls
output and it would be nice not to break things for them.
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.)
Mike Stone
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
