On Aug 7 01:53, Cyrille Lefevre wrote:
> some times ago, someone (you?) modifies cygpath to handle /dev/sdXY paths.
>
> however, it seems there is a problem somewhere ?
>
> v2$ uname -a
> CYGWIN_NT-6.0 pcvista 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
>
> v2$ /usr/sbin/blkid
> /dev/sda1: LA
Le 29/07/2011 22:15, Corinna Vinschen a écrit :
On Jul 29 15:34, Schwarz, Konrad wrote:
Can you answer the following question:
Given a volume label, how does one figure out where the
corresponding
volume has been mounted into the Cygwin namespace?
We're not mounting volumes, we're mounting
On Mon, Aug 01, 2011 at 08:10:30AM -0500, Nellis, Kenneth wrote:
>> From: Corinna Vinschen
>>
>> Konrad means blkid. It's in the util-linux package.
>
>That's funny. Setup indicates my util-linux package is up-to-date
>with version 2.17.2-1, but yet:
>
>$ type blkid
>-bash: type: blkid: not found
> From: Corinna Vinschen
>
> Konrad means blkid. It's in the util-linux package.
That's funny. Setup indicates my util-linux package is up-to-date
with version 2.17.2-1, but yet:
$ type blkid
-bash: type: blkid: not found
$ which blkid
which: no blkid in (/usr/local/bin:/usr/bin:/cygdrive/c/Pro
On Jul 30 00:52, Christopher Faylor wrote:
> On Fri, Jul 29, 2011 at 10:15:56PM +0200, Corinna Vinschen wrote:
> >On Jul 29 15:34, Schwarz, Konrad wrote:
> >> > > Can you answer the following question:
> >> > >
> >> > > Given a volume label, how does one figure out where the
> >> > corresponding
On Fri, Jul 29, 2011 at 10:15:56PM +0200, Corinna Vinschen wrote:
>On Jul 29 15:34, Schwarz, Konrad wrote:
>> > > Can you answer the following question:
>> > >
>> > > Given a volume label, how does one figure out where the
>> > corresponding
>> > > volume has been mounted into the Cygwin namespa
Schwarz, Konrad sent the following at Friday, July 29, 2011 9:34 AM
>> > Given a volume label, how does one figure out where the
>> corresponding
>> > volume has been mounted into the Cygwin namespace?
>>
>> We're not mounting volumes, we're mounting Win32 paths.
>> There is no direct correspondenc
On Jul 29 15:34, Schwarz, Konrad wrote:
> > > Can you answer the following question:
> > >
> > > Given a volume label, how does one figure out where the
> > corresponding
> > > volume has been mounted into the Cygwin namespace?
> >
> > We're not mounting volumes, we're mounting Win32 paths.
>
> > Can you answer the following question:
> >
> > Given a volume label, how does one figure out where the
> corresponding
> > volume has been mounted into the Cygwin namespace?
>
> We're not mounting volumes, we're mounting Win32 paths.
> There is no direct correspondence between volumes and
On Jul 29 09:45, Schwarz, Konrad wrote:
> > From: Christopher Faylor
> > We're not
> > going to introduce this level of recursive confusion to the
> > mount table handling.
>
> The proposal is sound. It works on Linux, after all.
Ok, so I assume Cygwin should be able to load Linux kernel mod
> -Original Message-
> From: Christopher Faylor
> Subject: Re: Device names in /proc/mounts
> The "drive letters" above could be anything that
> Windows maps to a drive letter. A drive does not necessarily
> directly map to a physical device.
That'
On Thu, Jul 28, 2011 at 10:18:26AM +0200, Schwarz, Konrad wrote:
>As far as I understand, Cygwin mount knows about
>- fixed mounts /, /usr/bin, /usr/lib
>- user-defined mounts taken from /etc/fstab, /etc/fstab.d, and the command-line
>- Win32 drive letters implicitly mounted under /cygdrive
>
>The
> From: Corinna Vinschen
> Sent: Wednesday, July 27, 2011 11:41 AM
> Subject: Re: Device names in /proc/mounts
> D:/foo/bar /baz xyz binary,posix=0 0 0
> //server/share/some/path /home/dummy smbfs binary,noacl 0 0
>
> how would you map them to devices? Both paths are n
On Wed, Jul 27, 2011 at 11:40:51AM +0200, Corinna Vinschen wrote:
>On Jul 27 10:35, Schwarz, Konrad wrote:
>>>From: Corinna Vinschen On Jul 25 14:29, Schwarz, Konrad wrote:
There seems no way of mapping device names (resp. Win32 Device
Namespace names) to mount points --
>>>
>>>Cygwin moun
On Jul 27 10:35, Schwarz, Konrad wrote:
> > From: Corinna Vinschen
> > On Jul 25 14:29, Schwarz, Konrad wrote:
> > > There seems no way of mapping device names (resp. Win32 Device
> > > Namespace names) to mount points --
> >
> > Cygwin mount pounts are not mapping disk devices to POSIX
> > path
> -Original Message-
> From: Corinna Vinschen
> Sent: Monday, July 25, 2011 4:01 PM
> Subject: Re: Device names in /proc/mounts
>
> On Jul 25 14:29, Schwarz, Konrad wrote:
> > There seems no way of mapping device names (resp. Win32 Device
> > Na
> -Original Message-
> From: Corinna Vinschen
> Sent: Monday, July 25, 2011 4:01 PM
> Subject: Re: Device names in /proc/mounts
>
> On Jul 25 14:29, Schwarz, Konrad wrote:
> > There seems no way of mapping device names (resp. Win32 Device
> > Na
On Mon, Jul 25, 2011 at 02:29:46PM +0200, Schwarz, Konrad wrote:
>Hi,
>
>in Linux, /proc/mounts maps device names (/dev/sda2) to mount points (/home).
>
>in Cygwin, /proc/mounts maps DOS names (C:) to cygwin names (/cygdrive/c).
>This is not terribly useful.
This is a literal dump of the Cygwin mo
On Jul 25 14:29, Schwarz, Konrad wrote:
> There seems no way of mapping device names (resp. Win32 Device Namespace
> names) to mount points --
Cygwin mount pounts are not mapping disk devices to POSIX pathnames, but
Win32 pathnames to POSIX pathnames.
> the Cygwin User's Guide suggests using com
Hi,
in Linux, /proc/mounts maps device names (/dev/sda2) to mount points (/home).
in Cygwin, /proc/mounts maps DOS names (C:) to cygwin names (/cygdrive/c).
This is not terribly useful.
There seems no way of mapping device names (resp. Win32 Device Namespace names)
to mount points --
the Cygwin
20 matches
Mail list logo
