Added some interesting functionality to my cygwin sandbox

Christopher Faylor
Wed Jul 2 01:46:00 GMT 2003

On Tue, Jul 01, 2003 at 09:38:58PM -0400, Igor Pechtchanski wrote:
>On Tue, 1 Jul 2003, Corinna Vinschen wrote:
>> On Tue, Jul 01, 2003 at 12:23:51PM -0400, Christopher Faylor wrote:
>> > On Tue, Jul 01, 2003 at 06:20:46PM +0200, Corinna Vinschen wrote:
>> > >I think I recall they have some fixed root level dirs like /windir,
>> > >/sysdir, /registry.
>> >
>> > We could do this in a cygwin post-install script if there is consensus
>> > that it would be useful.
>> That would involve symlinks to a path outside of the Cygwin root again,
>> which would be broken when the use changes the cygdrive prefix.
>> This reminds me, wouldn't it make sense to store the cygdrive prefix
>> inside of symlinks in a form which is independent of the actual
>> cygdrive prefix string?  I mean, instead of having a
>>   /cygdrive/d/foo
>> the symlink could contain something representing
>>   ${cygdriveprefix}/d/foo
>> In that case symlinks would still be valid if the user changes the
>> prefix or, worse, on a multiuser system where users have different
>> user cygdrive prefixes.
>> Corinna
>FWIW, I like this idea.  Either that, or have a hard-coded cygdrive prefix
>that's *always* recognized, in addition to the user-changeable one
>(although I'd prefer changing the symlinks instead).

How do you deal with the fact that '$', '{', and '}' are allowable filename
characters now?


More information about the Cygwin-developers mailing list