/usr/local, /var and */tmp in c:\Users\Public
Wed Nov 12 22:35:00 GMT 2014
Greetings, cyg Simple!
>> I didn’t want to derail the discussion about the future of /home with this,
>> so I’m starting a new thread.
>> I think it would be an improvement to Cygwin if c:\cygwin contained only
>> things that can be reinstalled from your local setup.exe download cache, in
>> the same way that you can nuke "c:\Program Files\Microsoft Office $version”
>> and reinstall without losing anything you created locally.
> What local changes/installations get lost?
What get lost, if you nuke Cygwin folder in default installation?
Everything. Every single piece you could think about.
>> Further design principles follow from this:
>> - User data should live in directories that those users are normally allowed to write to.
>> - Per-machine software and per-machine configuration should be in directories that local Administrators can normally write to.
>> - Software built from source (/usr/local) should not be in c:\cygwin; it is per-machine configuration, and so should be elsewhere.
>> - If you tighten down what remains so that normal users only get read permission, it should continue to function, in the same way that normal users on a Linux box don’t need write access to, say, /usr/include.
>> This /etc/fstab addition mostly accomplishes that:
>> c:/Users/Public/Cygwin/var /var ntfs auto 0 0
>> c:/Users/Public/Cygwin/usr/local /usr/local ntfs auto 0 0
>> c:/Users/Public/Cygwin/tmp /tmp ntfs notexec 0 0
>> c:/Users/Public/Cygwin/tmp /usr/tmp ntfs notexec 0 0
>> c:/Users/Public/Cygwin/tmp /var/tmp ntfs notexec 0 0
>> I propose that this or something like it be added to the default fstab.
> Please NO not by default or offering an option. A back end tool maybe
> in cygutils that can be run manually.
Give one good reason, other than impulsive screaming?
Andrey Repin (firstname.lastname@example.org) 13.11.2014, <01:19>
Sorry for my terrible english...
More information about the Cygwin