I've been damned to having to use it, just often enough.
> Exactly. This is why I've changed my mind. In an effort to make it a little
> less sucky all traces of the short names should be hidden from linux. It'll
I hope not, I feel it's easier to type progra~1 than the entire thing (which
I normally do when looking through things)
> then be sane if a little limited. You then have a couple of ioctls to read
> and write the short names for programs that _must_ have them. (A shortname
> write that would cause a collision will error)
What would be funny if you really wanted to have an 8.3 file ending with ~1
and another already exists <g>
> Hopefully this is what Alexander will do, I don't see and problem living
> with a "sfn_backup". Or with an LD_PRELOAD you could simulate the brain
> damage and/or uglyness of any of the other schemes suggested here. (Mine
> included)
Preload should be the way to go on this. What's 'sfn_backup'? I don't
recall it.
> BY Alexander Viro <viro@math.psu.edu>
> > Some @#$^ing programs apparently want to be able to access the files via
> > short names.
What about the user too lazy to type in all those blasted spaces? =)
> Then they use the ioctls.
> In fact, Alexander, be nice to them, provide one that gives the long
> name given the short name ... as well as vis-versa.
Personally, I prefer it just the way it is, we really don't need to see the
sfn anyway. But still I'd like to access it as I said above.
> Remember they are already providing special code for VFAT partitons,
> it shouldn't be too difficult to use a slightly more hidden (but still
> documented) interface.
>
> Well Alexander, is that the decision ?
As long as everyone can have it their way with mount options.. I understand
that some people are too afraid of options <g>
-- Lab tests show that use of micro$oft causes cancer in lab animals- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/