This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: /usr/local, /var and */tmp in c:\Users\Public
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Warren Young <wyml at etr-usa dot com>, cygwin at cygwin dot com
- Date: Fri, 14 Nov 2014 01:37:35 +0300
- Subject: Re: /usr/local, /var and */tmp in c:\Users\Public
- Authentication-results: sourceware.org; auth=none
- References: <81578012-FD3F-4463-BC56-ADB092317DD4 at etr-usa dot com> <20141113095547 dot GJ2782 at calimero dot vinschen dot de> <F45083BB-8AC2-408E-BD52-3E019F6272E4 at etr-usa dot com>
- Reply-to: cygwin at cygwin dot com
Greetings, Warren Young!
>>> I propose that this or something like it be added to the default
>>> fstab.
>>
>> No. This would even break Setup right now.
> I’m guessing this is because setup.exe doesn’t know what to do with a
> redirected /var and /usr/local on the first install, when /etc/fstab doesn’t exist yet?
> I assume setup.exe does obey /etc/fstab on subsequent installs. If not, I
> can see that this will break the installation of any package that puts files in either location.
I can't see, why it ever should care about /etc/fstab at all.
The postinstall scripts - they do, but again, they run in cygwin environment,
not native.
> I don’t see that the */tmp changes would bother setup.exe.
> None of these problems seem difficult. Doesn’t setup.exe write the initial
> /etc/fstab, and so is in a position to know what it will contain on first install?
Even if it does, there's no reason to read it on subsequent updates.
The expectation is that the directory tree is in one place. If you really want
to scatter it, use native tools. It is possible and way less intrusive.
--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 14.11.2014, <01:34>
Sorry for my terrible english...