This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Reading /proc/registry/... returns extra char
- From: Andrey Repin <anrdaemon at freemail dot ru>
- To: Dave Korn <dave dot korn dot cygwin at gmail dot com>, cygwin at cygwin dot com
- Date: Fri, 4 Jun 2010 01:17:19 +0400
- Subject: Re: Reading /proc/registry/... returns extra char
- References: <20100513181249.GE13784@cupro.opengvs.com> <2BF01EB27B56CC478AD6E5A0A28931F2F01D44@A1DAL1SWPES19MB.ams.acs-inc.net> <20100526114733.GG10652@calimero.vinschen.de> <1254830174.20100526174227@mtu-net.ru> <20100526143428.GN10652@calimero.vinschen.de> <326990670.20100530001515@mtu-net.ru> <20100531081411.GE16885@calimero.vinschen.de> <14428931.20100601034233@mtu-net.ru> <4C046662.5060207@gmail.com>
- Reply-to: Andrey Repin <cygwin at cygwin dot com>
Greetings, Dave Korn!
>> Erm... how about ":type" suffix? Don't know how "POSIXy" it is, but it's close
>> enough to similar functionality of NTFS (file streams).
> To save having the whole discussion again, here's the summary from last time:
> http://www.cygwin.com/ml/cygwin-developers/2006-03/msg00003.html
*carefully raising eyebrows* Thanks for the link.
I didn't though about cross-compatibility issues, and these concerns are
understandable.
My opinion is that there's no solution to the p.3 due to the fact that files
don't have strict typization (other than file/directory/reparse).
Using some kind of suffixing won't do much because it raising a mountain of
ambiguity due to a wide range of characters allowed in value names (including
"/:?*" as well as more trivial commas and dots, which are also allowed in file
names)
--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 04.06.2010, <1:05>
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple