Hi!
-
AFAIK we found a resource or Win32 object refcount leak:
If I do a $ mount nfsdir_as_Y ; cd /cygdrive/y ; ls -l ; cd / ; umount
Y: #, the the VNetRoot used by the filesystem's kernel module is not
finalised (e.g. |MRxFinalizeVNetRoot()| is not being called).
If I do the same with just
In order for these formats to be machine-parseable, characters used as
delimiters must be escaped. Linux escapes space, tab, newline,
backslash, and hash (because code that parses mounts/mtab and fstab
would handle comments) using octal escapes. Replicate that behavior
here.
Addresses:
In order for these formats to be machine-parseable, characters used as
delimiters must be escaped. Linux escapes space, newline, backslash,
and hash (because code that parses mounts/mtab and fstab would handle
comments) using octal escapes. Replicate that behavior here.
Addresses:
On Mon, 3 Jun 2024, Jeremy Drake via Cygwin wrote:
> /proc/self/mounts and /proc/self/mountinfo use octal escapes for ' ' and
> \n (I was rather surprised they didn't escape \r also, but I guess they
> don't have to because only ' ' and \n are used as delimiters):
Went looking at Linux source
Steps to reproduce:
$ mkdir /$'My New\r\nFolder'
$ mount c: /$'My New\r\nFolder'
$ mount
C:/cygwin64/bin on /usr/bin type ntfs (binary,auto)
C:/cygwin64/lib on /usr/lib type ntfs (binary,auto)
C:/cygwin64 on / type ntfs (binary,auto)
C: on /My New
Folder type ntfs (binary,user)
$ cat /proc/self
(not what is reported by Cygwin)
> 3. I issue the rsync with something like: rsync -avSHP /f/some-dir/
> /s/some-dir/
> The issue here is that it appears mount related options such as noacl are
> evaluated differently when native symlinks are used. If I change the
> destinatio
rwxrwxrwx 1 clayne None 11 Apr 24 12:24 /s -> /cygdrive/s
3. I issue the rsync with something like: rsync -avSHP /f/some-dir/ /s/some-dir/
The issue here is that it appears mount related options such as noacl are
evaluated differently when native symlinks are used. If I change the
desti
On Dec 1 04:55, Andrey Repin via Cygwin wrote:
> Greetings, Martin Wege!
>
> > Cygwin mount(1) is (per docs) limited to 64 mounts. Why was that
> > limitation chosen, and does it apply even if I create bind mounts to
> > UNC paths (not DOS letters)? DOS let
Greetings, Martin Wege!
> Cygwin mount(1) is (per docs) limited to 64 mounts. Why was that
> limitation chosen, and does it apply even if I create bind mounts to
> UNC paths (not DOS letters)? DOS letters might be restricted by the
> ASCII A-Z, but UNC paths are unlimited.
More
Hello,
Cygwin mount(1) is (per docs) limited to 64 mounts. Why was that
limitation chosen, and does it apply even if I create bind mounts to
UNC paths (not DOS letters)? DOS letters might be restricted by the
ASCII A-Z, but UNC paths are unlimited.
Thanks,
Martin
--
Problem reports
Good evening!
Can I mount a Windows share (CIFS, builtin Windows, ms-nfsv41, ...) at
Windows 10 system boot time, so all users (and Cygwin sessions) can
use it?
Ced
--
Cedric Blancher
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
--
Problem reports: https://cygwin.com
On Aug 11 17:37, Cedric Blancher via Cygwin wrote:
> On Tue, 8 Aug 2023 at 20:53, Corinna Vinschen
> wrote:
> >
> > On Aug 8 16:52, Cedric Blancher via Cygwin wrote:
> > > Good afternoon!
> > >
> > > How do I set mount posix=1 option for an exi
On Tue, 8 Aug 2023 at 20:53, Corinna Vinschen wrote:
>
> On Aug 8 16:52, Cedric Blancher via Cygwin wrote:
> > Good afternoon!
> >
> > How do I set mount posix=1 option for an existing bind mount? mount -o
> > remount does not work.
>
> Did you read https:/
On Aug 8 16:52, Cedric Blancher via Cygwin wrote:
> Good afternoon!
>
> How do I set mount posix=1 option for an existing bind mount? mount -o
> remount does not work.
Did you read https://cygwin.com/cygwin-ug-net/mount.html?
Mount points created by mount(1) only exist in the
Good afternoon!
How do I set mount posix=1 option for an existing bind mount? mount -o
remount does not work.
Ced
--
Cedric Blancher
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
--
Problem reports: https://cygwin.com/problems.html
FAQ: https
version 4 client daemon:
ms-nfs41-client-x64/nfsd_debug.exe -d 3 --noldap --gid 3620 --uid 3620
4. Mount NFS version 4 directory:
ms-nfs41-client-x64/ms-nfs41-client-x64/nfs_mount.exe -p -o sec=sys X
'lordbatman.bias.dfn.de:/export/home/mlw'
Expectation:
Cygwin ls -l should list file user/group as mlw/m
reproduce:
> > 1. Download and install cygwin.
> > 2. Download http://www.citi.umich.edu/projects/nfsv4/windows/120612/
> > and install it.
> > 3. Start NFS version 4 client daemon:
> > ms-nfs41-client-x64/nfsd_debug.exe -d 3 --noldap --gid 3620 --uid 3620
> >
rt NFS version 4 client daemon:
> ms-nfs41-client-x64/nfsd_debug.exe -d 3 --noldap --gid 3620 --uid 3620
> 4. Mount NFS version 4 directory:
> ms-nfs41-client-x64/ms-nfs41-client-x64/nfs_mount.exe -p -o sec=sys X
> 'lordbatman.bias.dfn.de:/export/home/mlw'
>
> Expectation:
> Cygwin l
20)
Steps to reproduce:
1. Download and install cygwin.
2. Download http://www.citi.umich.edu/projects/nfsv4/windows/120612/
and install it.
3. Start NFS version 4 client daemon:
ms-nfs41-client-x64/nfsd_debug.exe -d 3 --noldap --gid 3620 --uid 3620
4. Mount NFS version 4 directory:
ms-nfs41-client-x6
Hi!
Does Cygwin have something like a Solaris/Linux autofs-style
automounter ? The idea is to mount NFS home dirs automagically the
first time someone uses them, e.g. $ cd /home/chickenmonster/ #
automagically mounts NFS dir mymonsternfs:/export/home/chickenmonster/
Bye,
Roland
On Jan 22 12:56, Brian Inglis via Cygwin wrote:
> On 2023-01-22 12:21, Corinna Vinschen via Cygwin wrote:
> > On Jan 21 11:30, Jeremy Hetzler via Cygwin wrote:
> > > First, thank you for many years of Cygwin.
> > >
> > > I'm unable to get Cygwin to moun
t; >> I'm unable to get Cygwin to mount Windows SMB shares where the share
> >> name begins with underscore. mount gives an error "Invalid argument".
> >
> > Yes, that's actually a bug. The mount code path in Cygwin checks
> > the path for being a share (i.e. \
On 2023-01-22 12:21, Corinna Vinschen via Cygwin wrote:
On Jan 21 11:30, Jeremy Hetzler via Cygwin wrote:
First, thank you for many years of Cygwin.
I'm unable to get Cygwin to mount Windows SMB shares where the share
name begins with underscore. mount gives an error "Invalid argument&qu
On Jan 21 11:30, Jeremy Hetzler via Cygwin wrote:
> All,
>
> First, thank you for many years of Cygwin.
>
> I'm unable to get Cygwin to mount Windows SMB shares where the share
> name begins with underscore. mount gives an error "Invalid argument".
Yes, that's act
On 2020-11-26 04:12, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
-Original Message-
From: Cygwin On Behalf Of Brian Inglis
Sent: 25 November 2020 21:59
On 2020-11-25 11:26, Vlado via Cygwin wrote:
On 25.11.2020 15:18, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
Mount -s was removed in 2008
> -Original Message-
> From: Cygwin On Behalf Of Brian Inglis
> Sent: 25 November 2020 21:59
>
> On 2020-11-25 11:26, Vlado via Cygwin wrote:
> > On 25.11.2020 15:18, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>
> Mount -s was removed in 2008:
> https:
On 2020-11-25 11:26, Vlado via Cygwin wrote:
On 25.11.2020 15:18, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
Mount -s was removed in 2008:
https://sourceware.org/git/?p=newlib-cygwin.git;a=commitdiff;h=5f853b3fc5277da8cb5ba3ac7406447fe82e65de
three months after it was set to be ignored
On 25.11.2020 15:18, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
-
if [ -n "`uname -s |grep -i cygwin_`" ]; then
# If we are on an new version of Cygnus we need to turn :/ in
# the path to/cygdrive//
CYGDRIVE=`mount -p | tail -1 | awk '{print $1}' |
by running:
-
$ ./oracle_common/common/bin/config.sh
mount: unknown option -- s
Try `mount --help' for more information.
Error: Could not find or load main class com.oracle.cie.wizard.WizardController
-
The problem is located in the following script:
oracle_common/common/bin/commBaseEnv.sh:
-
if [
On Oct 14 16:57, Mario Emmenlauer wrote:
> On 14.10.20 13:50, Corinna Vinschen wrote:
> > On Oct 14 11:06, Mario Emmenlauer wrote:
> >> On 14.10.20 10:28, Corinna Vinschen wrote:
> >>> Actually, not really. It's weird in fact, given ls(1) shows the
> >>> desired result. That would point to a bug
On 14.10.20 13:50, Corinna Vinschen wrote:
> On Oct 14 11:06, Mario Emmenlauer wrote:
>> On 14.10.20 10:28, Corinna Vinschen wrote:
>>> Actually, not really. It's weird in fact, given ls(1) shows the
>>> desired result. That would point to a bug in access(2), but there's
>>> no special code in
On Oct 14 11:06, Mario Emmenlauer wrote:
> On 14.10.20 10:28, Corinna Vinschen wrote:
> > Actually, not really. It's weird in fact, given ls(1) shows the
> > desired result. That would point to a bug in access(2), but there's
> > no special code in access(2) for NFS. For filesystems not
On 14.10.20 10:28, Corinna Vinschen wrote:
On Oct 13 21:00, Mario Emmenlauer wrote:
On 13.10.20 20:36, Corinna Vinschen wrote:
Everything seems to work quite well, and in `ls -la` I can see the
file permissions and user and group entries. But when using `test`
to check for read (`test -r`) or
ths ago.
>
> I did use a script to install Cygwin via its installer in an automated
> fashion, but I've run the normal, graphical installer a few times since
> then to make sure everything is nice and clean.
>
> Calling "which test" shows "/usr/bin/test", but since I use
only "weak link" in my setup is the NFS mount. I'm no expert
in exporting NFS, nor in mounting NFS from Windows. Maybe something
is fishy there, albeit I did not use any special parameters or
quirks (again, to the best of my knowledge). What I can say is that
I'm limited to NFS v3 since
On Oct 6 18:10, Mario Emmenlauer wrote:
>
> Dear Andrey,
>
> On 06.10.20 17:46, Andrey Repin wrote:
> > Greetings, Mario Emmenlauer!
> >
> >> thanks for the awesome Cygwin, its really great!
> >
> >> Everything seems to work quite well, and in `ls -la` I can see the
> >> file permissions and
Dear Andrey,
On 06.10.20 17:46, Andrey Repin wrote:
> Greetings, Mario Emmenlauer!
>
>> thanks for the awesome Cygwin, its really great!
>
>> Everything seems to work quite well, and in `ls -la` I can see the
>> file permissions and user and group entries. But when using `test`
>> to check
Greetings, Mario Emmenlauer!
> thanks for the awesome Cygwin, its really great!
> But since today I met a problem: I mounted a Linux NFSv3 share using
> the Windows 10 shipped NFS client. The user and group ID are mapped
> via registry settings AnonymousUid and AnonymousGid in the entry
>
On 10/1/2020 6:22 AM, Mario Emmenlauer wrote:
On 22.09.20 22:14, Mario Emmenlauer wrote:
But since today I met a problem: I mounted a Linux NFSv3 share using
the Windows 10 shipped NFS client. The user and group ID are mapped
via registry settings AnonymousUid and AnonymousGid in the entry
On 22.09.20 22:14, Mario Emmenlauer wrote:
> But since today I met a problem: I mounted a Linux NFSv3 share using
> the Windows 10 shipped NFS client. The user and group ID are mapped
> via registry settings AnonymousUid and AnonymousGid in the entry
>
Dear All,
thanks for the awesome Cygwin, its really great!
But since today I met a problem: I mounted a Linux NFSv3 share using
the Windows 10 shipped NFS client. The user and group ID are mapped
via registry settings AnonymousUid and AnonymousGid in the entry
:[SMB3][PATCH] add mount option to allow retrieving POSIX mode
from special ACE
Date: Mon, 24 Jun 2019 02:11:57 -0500
From: Steve French
To: CIFS
See e.g.
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/hh509017(v=ws.10)
where
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=367c1ae16185e7a81aea5bcc2388e4a7a473c92e
commit 367c1ae16185e7a81aea5bcc2388e4a7a473c92e
Author: Corinna Vinschen
Date: Mon Feb 18 10:12:07 2019 +0100
Cygwin: mount: define binary mount as default
Commit
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=f76c8519ac662e244ab4c1c14d9f809c08e384b4
commit f76c8519ac662e244ab4c1c14d9f809c08e384b4
Author: Corinna Vinschen
Date: Mon Feb 18 10:03:19 2019 +0100
Cygwin: mount: remove unused method mount_info::set_flags_from_win32_path
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=c1023ee353705671aa9a8e4e1179022277add2aa
commit c1023ee353705671aa9a8e4e1179022277add2aa
Author: Corinna Vinschen
Date: Sun Jan 6 17:44:20 2019 +0100
Cygwin: path_conv: decouple path_types from mount types
- Remove
On 12/2/2018 12:09 PM, Andrey Repin wrote:
> Greetings, john doe!
>
>> How can I do the following on Cygwin?:
>
>
>> /sbin/mount.cifs //server/share /mount-point -o user=different-user
>
>> In other words, how can I mount a windows share with a speci
Greetings, john doe!
> How can I do the following on Cygwin?:
> /sbin/mount.cifs //server/share /mount-point -o user=different-user
> In other words, how can I mount a windows share with a specific user ?
You can't. Cygwin is not a kernel module, it's a userspace program, and Cygw
Hi,
How can I do the following on Cygwin?:
/sbin/mount.cifs //server/share /mount-point -o user=different-user
In other words, how can I mount a windows share with a specific user ?
--
John Doe
--
Problem reports: http://cygwin.com/problems.html
FAQ: http
On 2018-10-27 19:32, hauck.adrian451 wrote:
> I was review the urls indicated and install the command pkg-config:
> - Created the file fuse.pc indicated the location the dll:
> user@cliente~/winfsp-master/opt/cygfuse/fuse
> $ more fuse.pc
> arch=x64
> prefix=${pcfiledir}/..
> incdir=C:\Program
On 10/27/2018 8:32 PM, hauck.adrian451 wrote:
> - Created the file fuse.pc indicated the location the dll:
>
> user@cliente~/winfsp-master/opt/cygfuse/fuse
> $ more fuse.pc
> arch=x64
> prefix=${pcfiledir}/..
> incdir=C:\Program Files (x86)\WinFsp
> implib=C:\Program Files
Am 28.10.2018 um 02:32 schrieb hauck.adrian451:
Hi,
Thank you for the help.
I was review the urls indicated
Have you in the PATH the directory where
winfsp-x64.dll is located ?
If it is located in
"C:\Program Files(x86)\WinFsp\bin"
you should have a something like the output of cygpath
$
Hi,
Thank you for the help.
I was review the urls indicated and install the command pkg-config:
- Created the file fuse.pc indicated the location the dll:
user@cliente~/winfsp-master/opt/cygfuse/fuse
$ more fuse.pc
arch=x64
prefix=${pcfiledir}/..
incdir=C:\Program Files (x86)\WinFsp
On 2018-10-26 17:54, hauck.adrian451 wrote:
> Excuse me, but I have found the library. It was in "C:\Program Files
> (x86)\WinFsp\bin".
> I have find where the references of dll in cygwin in this files:
> C:\cygwin64\bin\cygfuse-2.8.dll
> C:\cygwin64\bin\cygfuse-3.2.dll
>
Hi,
Excuse me, but I have found the library. It was in "C:\Program Files
(x86)\WinFsp\bin".
I have find where the references of dll in cygwin in this files:
C:\cygwin64\bin\cygfuse-2.8.dll
C:\cygwin64\bin\cygfuse-3.2.dll
/proc/registry32/HKEY_LOCAL_MACHINE/Software/WinFsp/InstallDir
The
Hi,
Yes, I have installed "winfsp-1.3.18160.msi" and when the setup full options
"Core, Developer and FUSE for Cygwin":
Directorio de C:\Program Files\SSHFS-Win\bin
26/10/2018 23:45 .
26/10/2018 23:45 ..
30/11/2017 23:0912.819 cygcom_err-2.dll
30/11/2017
Am 26.10.2018 um 18:03 schrieb hauck.adrian451:
Thank you,
I execute:
- ninja
- ninja install
user@cliente ~/sshfs-sshfs-3.5.0/build
$ ninja
[5/6] Compiling C object 'sshfs@exe/sshfs.c.o'.
../sshfs.c: En la función ‘sshfs_init’:
../sshfs.c:1746:28: aviso: ‘~’ on a boolean expression
Thank you,
I execute:
- ninja
- ninja install
user@cliente ~/sshfs-sshfs-3.5.0/build
$ ninja
[5/6] Compiling C object 'sshfs@exe/sshfs.c.o'.
../sshfs.c: En la función ‘sshfs_init’:
../sshfs.c:1746:28: aviso: ‘~’ on a boolean expression [-Wbool-operation]
cfg->nullpath_ok =
On 10/26/2018 7:28 AM, hauck.adrian451 wrote:
>
> mssg@ltmssg ~/sshfs-sshfs-3.5.0/build
> $ sshfs
> -bash: sshfs: no se encontró la orden
>
>
> Can you help me?
>
https://superuser.com/questions/1264732/how-to-use-sshfs-on-cygwin
--
cyg Simple
--
Problem reports:
Hi,
I could install the sshfs in cygwin, but goes on wihout found:
user@cliente ~/sshfs-sshfs-3.5.0/build
$ meson --reconfigure
The Meson build system
Version: 0.48.1
Source dir: /home/mssg/sshfs-sshfs-3.5.0
Build dir: /home/mssg/sshfs-sshfs-3.5.0/build
Build type: native build
Project name:
On 08/16/2018 04:08 PM, Edward Diener wrote:
The 'mount' function in cygwin is decidedly different from Linux. What
is the reason for this ?
- POSIX does not specify mount(1) - it is inherently non-portable and
platform specific. So any expectation of similarity between platforms
is bound
The 'mount' function in cygwin is decidedly different from Linux. What
is the reason for this ?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=8eada332236791bb3757091d867d3ef5f93a13d3
commit 8eada332236791bb3757091d867d3ef5f93a13d3
Author: Corinna Vinschen <cori...@vinschen.de>
Date: Wed Jun 14 13:22:56 2017 +0200
cygwin: readdir: don't lookup mount target
On Jun 13 11:12, Joe Lowe wrote:
>
> This patch fixes a minor compatibility issue w/ cygwin mount point handling
> in readdir(), compared to equivalent behavior of Linux and MacOS.
> dentry.d_ino should indicate the INO of the mount point itself, not the
> target volume root folde
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=0a9edd73e3abb85162f9d79bc57cf4df1f9d8f1e
commit 0a9edd73e3abb85162f9d79bc57cf4df1f9d8f1e
Author: Joe Lowe <j...@pismotec.com>
Date: Tue Jun 13 11:12:50 2017 -0700
readdir() with mount point dentry, return mount poi
This patch fixes a minor compatibility issue w/ cygwin mount point
handling in readdir(), compared to equivalent behavior of Linux and
MacOS. dentry.d_ino should indicate the INO of the mount point itself,
not the target volume root folder.
Changed return type from
Greetings, Pan Ruochen!
> Hi Andrey Repin,
>>
>> No, why? Your mount options choice is very sane, IMO.
>>
> I just dislike cygwin treats every file as executable.
This is a core Windows behavior, nothing Cygwin can do about it, not it
should. In Windows, any file is,
Am 05.04.2017 um 16:07 schrieb Pan Ruochen:
Hi Andrey Repin,
No, why? Your mount options choice is very sane, IMO.
I just dislike cygwin treats every file as executable.
It doesn't --- not when the files' ACLs are set up correctly, anyway.
Nor is futzing with mount options the right
On 4/5/2017 10:07 AM, Pan Ruochen wrote:
> Hi Andrey Repin,
>
>>
>> No, why? Your mount options choice is very sane, IMO.
>>
>
> I just dislike cygwin treats every file as executable. Comparing mount
> options of msys2 against cygwin, msys2 has an extra noacl op
>
> Add /etc/fstab.d/ with your own mount options.
> Be aware that noacl uses only the readonly attribute to
> inhibit write in POSIX permissions, and checks file suffixes
> and contents to determine execute permissions, so may be
> even slower.
>
/etc/fstab.d/ works. Than
Hi Andrey Repin,
>
> No, why? Your mount options choice is very sane, IMO.
>
I just dislike cygwin treats every file as executable. Comparing mount
options of msys2 against cygwin, msys2 has an extra noacl option. So I
guess noacl may turn off this cygwin `feature`. And I also wish thi
Greetings, Pan Ruochen!
> On my computer, runing mount shows
> C: on /c type ntfs (binary,posix=0,user,noumount,auto)
> D: on /d type ntfs (binary,posix=0,user,noumount,auto)
> E: on /e type ntfs (binary,posix=0,user,noumount,auto)
> Is it possible to change the default mount op
On 2017-04-03 20:19, Pan Ruochen wrote:
> On my computer, runing mount shows
>
> C: on /c type ntfs (binary,posix=0,user,noumount,auto)
> D: on /d type ntfs (binary,posix=0,user,noumount,auto)
> E: on /e type ntfs (binary,posix=0,user,noumount,auto)
>
> Is it possible to cha
On my computer, runing mount shows
C: on /c type ntfs (binary,posix=0,user,noumount,auto)
D: on /d type ntfs (binary,posix=0,user,noumount,auto)
E: on /e type ntfs (binary,posix=0,user,noumount,auto)
Is it possible to change the default mount options for every
partition, for example , to
binary
osed solution?
> You do know that MS originally called junctions "mountpoints",
> right? So why would cygwin treating them as such be a "questionable
> workaround"?
How they are called, and how they behave is a two different questions.
> How would
Corinna Vinschen wrote:
He's right. The mount point handling in Cygwin is based on the
in-memory mount table.
I'm not wanting a mount point fake. Just wanting it to look
like a normal dir just like the mountvol-junctions.
There's no reasonable way to fake some
reparse point to look
efits of your proposed solution?
>
> You do know that MS originally called junctions "mountpoints",
> right? So why would cygwin treating them as such be a "questionable
> workaround"?
He's right. The mount point handling in Cygwin is based on the
in-memory mou
Andrey Repin wrote:
I would argue against all junctions being treated blindly.
The difference with bind mounts in Linux is that in Linux
you don't have the
information available within the filesystem itself, and have
no other option,
than to treat them as regular directories.
Only direct
Greetings, L. A. Walsh!
> Didn't see a response to this, so reposting, as this
> would provide a needed vol and subdir mount facility as
> exists on linux...
> Especially, since there was a misunderstanding of what
> was needed or wanted w/regards to the JUNCTION file-system
>
Didn't see a response to this, so reposting, as this
would provide a needed vol and subdir mount facility as
exists on linux...
Especially, since there was a misunderstanding of what
was needed or wanted w/regards to the JUNCTION file-system
mounts in Windows. Didn't need mount table updated
ch is if this is technically undefined
> behavior and might conceivably break something or is it OK (less the
> drive listing limitation mentioned above).
>
I've used the / as /cygdrive since the beginning of /cygdrive. The
issue you see is the fact that Cygwin doesn't require a physical
Greetings, L. A. Walsh!
>> If you want to access Windows path, recommended route lies through the use of
>> cygpath utility to convert native paths to the Cygwin scheme. Et vice versa.
>>
> I wouldn't recommend that -- it's too hard to type:
I didn't say "typing" anywhere.
I did mean
Andrey Repin wrote:
Accessing drive letters directly from inside Cygwin is often
considered a grey area.
How is it grey?
Too much may happen on this border. You have to clearly understand, how Cygwin
interact with other system, to avoid issues.
I.e. if you think you may have
Greetings, Rustam!
> I've added an extra / mountpoint in /etc/fstab in order to be able to
> access C: without /cygdrive like this:
> none /cygdrive cygdrive binary,posix=0,user 0 0
> none / cygdrive binary,posix=0,user 0 0
Only one cygdrive mount is effective.
> It s
ht conceivably break something or is it OK (less the
drive listing limitation mentioned above).
Thanks,
Rustam
The way that I do it (and have for a long time) is a line in my
.bash_profile file:
mount --change-cygdrive-prefix /
then ls /c does what you want
but ls / may not
HTH
--
Problem
I've added an extra / mountpoint in /etc/fstab in order to be able to
access C: without /cygdrive like this:
none /cygdrive cygdrive binary,posix=0,user 0 0
none / cygdrive binary,posix=0,user 0 0
It seems to work, I can access the C: drive with just /c.
But normally an "ls /cygdrive"
Greetings, Fergus!
> I have set
> /bin/mount -c "/"
> in ~/.bashrc with many subsequent easements in use.
Do that in /etc/fstab
The example is at the very top of it.
Uncomment and change the mount path as you see fit.
> In /usr/share/fonts/microsoft/ there are unfortun
Fergus bonhard.uklinux.net> writes:
> I have set
> /bin/mount -c "/"
> in ~/.bashrc with many subsequent easements in use.
> In /usr/share/fonts/microsoft/ there are unfortunately
> multiple links referring to files in
> /cygdrive/c/Windows/Fonts/; all broken.
On 24/06/2016 11:52, Fergus wrote:
I have set
/bin/mount -c "/"
in ~/.bashrc with many subsequent easements in use.
In /usr/share/fonts/microsoft/ there are unfortunately
multiple links referring to files in
/cygdrive/c/Windows/Fonts/; all broken.
Similarly in /etc/, several link
I have set
/bin/mount -c "/"
in ~/.bashrc with many subsequent easements in use.
In /usr/share/fonts/microsoft/ there are unfortunately
multiple links referring to files in
/cygdrive/c/Windows/Fonts/; all broken.
Similarly in /etc/, several links pointing to files in
/cygdrive
On 21/01/2016 06:34, Miya Miller wrote:
$ mount
C:/cygwin64/bin on /usr/bin type ntfs (binary,auto)
C:/cygwin64/lib on /usr/lib type ntfs (binary,auto)
C:/cygwin64 on / type ntfs (binary,auto)
C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
D: on /cygdrive/d type ntfs (binary
$ mount
C:/cygwin64/bin on /usr/bin type ntfs (binary,auto)
C:/cygwin64/lib on /usr/lib type ntfs (binary,auto)
C:/cygwin64 on / type ntfs (binary,auto)
C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
D: on /cygdrive/d type ntfs (binary,posix=0,user,noumount,auto)
F: on /cygdrive/f
At the moment I'm using $(/usr/bin/cygpath -S -u) to get the system
> directory. Since the /cygdrive prefix could be anything, I'd either
> have to first figure it out via $(dirname $(/usr/bin/cygpath -u C:))
> since the output from mount is a bit unwieldy. Maybe we should just
> force
Corinna Vinschen writes:
> No offense, but you didn't understand what I mean, it seems.
I did, I think -- but read my request again.
> Don't call cygpath. Just use /proc/cygdrive directly. It's that
> simple. While the cygdrive prefix changes, /proc/cygdrive will
> *never* change. E.g.
I
thetical
--8<---cut here---start->8---
WINETC="$(/usr/bin/cygpath -S -U)/drivers/etc"
--8<---cut here---end--->8---
BTW, the path comprising the cygdrive prefix probably needs to be
sanitized to avoid things like
--
On 12/6/2015 9:28 AM, Achim Gratz wrote:
> Corinna Vinschen writes:
>> No offense, but you didn't understand what I mean, it seems.
>
> I did, I think -- but read my request again.
>
>> Don't call cygpath. Just use /proc/cygdrive directly. It's that
>> simple. While the cygdrive prefix
cyg Simple writes:
> Use the $WINDIR variable to find the Windows path and manipulate its
> value to prepend /proc/cygdrive/ and suffix its value with /system32.
> The system32 directory will always be in $WINDIR/sytem32.
That's just as ugly as the solution I have plus that one doesn't rely on
drive prefix could be anything, I'd either
have to first figure it out via $(dirname $(/usr/bin/cygpath -u C:))
since the output from mount is a bit unwieldy. Maybe we should just
force the cygdrive prefix to be /cygdrive for postinstall scripts
anyway.
But there really ought to be a way to simply ha
On Dec 6 15:28, Achim Gratz wrote:
> Corinna Vinschen writes:
> > No offense, but you didn't understand what I mean, it seems.
>
> I did, I think -- but read my request again.
>
> > Don't call cygpath. Just use /proc/cygdrive directly. It's that
> > simple. While the cygdrive prefix changes,
Corinna Vinschen writes:
>> I need cygpath to get the system directory (hint: it need not be in
>> C:\Windows\System32) and cygpath delivers that directory with the
>> cygdrive prefix and not /proc/cygpath prepended. I wouldn't mind if all
>> those special directories would also be available via
On 11/26/2015 1:04 PM, Achim Gratz wrote:
> Corinna Vinschen writes:
>> Achim, any chance to tweak base-file accordingly?
>
> Noted, but it might take a while.
>
That should work. Thanks for listening and working through the problem.
--
cyg Simple
--
Problem reports:
1 - 100 of 877 matches
Mail list logo
