Greetings, Eliot Moss!
> On 12/22/2019 7:34 AM, Andrey Repin wrote:
>> Drive has specific network path, use it.
> Thank you, Andrey, but with (admittedly minimal) searching and
> playing around, I could not figure out how to determine what
> that path is. This is a locally attached (USB) extern
On 12/23/2019 3:55 AM, Brian Inglis wrote:> On 2019-12-22 20:16, Eliot Moss
wrote:
>>
>> So can a \\?\Volume{...} guid name for a volume be used in Cygwin's fstab?
>> What would the syntax be like for that?
>
> Each entry must be on a single line:
>
> #|/bin/cygwin1.dll
> # /etc/fstab - https://c
On 2019-12-22 20:16, Eliot Moss wrote:
>
> So can a \\?\Volume{...} guid name for a volume be used in Cygwin's fstab?
> What would the syntax be like for that?
Each entry must be on a single line:
#|/bin/cygwin1.dll
# /etc/fstab - https://cygwin.com/cygwin-ug-net/using.html#mount-table
#
So can a \\?\Volume{...} guid name for a volume be used in Cygwin's fstab?
What would the syntax be like for that?
Regards - Eliot Moss
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Uns
On 2019-12-22 06:08, Eliot Moss wrote:
> On 12/22/2019 7:34 AM, Andrey Repin wrote:
>
>> Drive has specific network path, use it.
>
> Thank you, Andrey, but with (admittedly minimal) searching and
> playing around, I could not figure out how to determine what
> that path is. This is a locally at
On 12/22/2019 7:34 AM, Andrey Repin wrote:
Drive has specific network path, use it.
Thank you, Andrey, but with (admittedly minimal) searching and
playing around, I could not figure out how to determine what
that path is. This is a locally attached (USB) external drive.
And I may be on networ
Greetings, Eliot Moss!
>> For things outside Cygwin root, I strongly suggest "noacl" option.
>> Then you won't even need to chown or chmod, except in dire circumstances,
>> where some careless program forcibly set permissions to something like 0750.
> So how would I do that for a removable NTFS
Greetings, Eliot Moss!
> Dear cygwiners --
> For a long time I _had_ things working, but somehow in switching over to using
> cygwin64 as primary, I messed up permissions on the directories where a backup
> program (EaseUS) puts things. I made the permissions similar to elsewhere in
> by cygwin
And indeed, the problem was that when putting in to use 64-bit
xlaunch, I did not set "Run as administrator". Once I set that
things worked fine. Ah, the little twiddles we forget!
Sorry for wasting your bandwidth, but maybe there was some
entertainment value in it for you! EM
--
Problem rep
Addendum: here is output from id:
uid=197609(moss) gid=197609(moss) groups=197609(moss),401408(Medium Mandatory
Level),197610(Cygwin),197611(docker-users),559(Performance Log
Users),545(Users),4(INTERACTIVE),66049(CONSOLE LOGON),11(Authenticated Users),15(This
Organization),68585(microsoftacco
10 matches
Mail list logo
