Linux 2.6.39-rc3
Quoted 6 lines
Gaah, yes. Apparently that placement is correct and documented, and has been since the beginning.
However, reality always takes precedence, so I think that for now we'll just have to revert the commit that added the uid: tag, and we can re-visit this issue when hopefully the tools have been fixed.
Note that the discussion on the libmount mailing list revealed a possible kernel workaround: escape the hyphens as \055. Damn hard to read for a human, but it does parse correctly, and the workaround can be fixed once the library updates have propagated.
In case it's useful.
Quoted 5 lines · George Spelvin
Note that the discussion on the libmount mailing list revealed a possible kernel workaround: escape the hyphens as \055. Damn hard to read for a human, but it does parse correctly, and the workaround can be fixed once the library updates have propagated.
I'd rather replace it with some non-dash character that is human-readable, like '+' or some utf-8 sequence that _looks_ like a dash.
So it wouldn't parse as a uuid to some code - big deal. Clearly neither does the correct dash. Using \055 would be just ugly.
Of course, not exposing it at all is also a reasonable strategy.
Who uses /proc/self/mountinfo? I see the problem on my alpha Fedora-15 test-machine, but Fedora-14 doesn't seem to do it. Ubuntu? SuSE? Do we know how widespread the breakage is?
If it is _just_ Fedora-15, then I presume that pushing out the util-linux fix and waiting a few weeks will fix it (since anybody using F-15 right now lives on the edge anyway, and a real release hasn't happened). But if we have real releases using it, then we may need to look at workarounds using non-'-' characters if people really want the uuid showing up any time soon.
Linus
Hi!
Quoted 8 lines
Quoted 4 lines
Note that the discussion on the libmount mailing list revealed a possible kernel workaround: escape the hyphens as \055. Damn hard to read for a human, but it does parse correctly, and the workaround can be fixed once the library updates have propagated.
I'd rather replace it with some non-dash character that is human-readable, like '+' or some utf-8 sequence that _looks_ like a dash.
Just delete the dashes? IIRC UUIDs are fixed length binary numbers, so no info will be lost.
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html