On Fri, Aug 29, 2008 at 06:02:23PM +0200, Albrecht Schlosser wrote:
> Christopher Faylor wrote:
>> On Fri, Aug 29, 2008 at 11:14:23AM +0200, Corinna Vinschen wrote:
>>
>>> On Aug 29 10:22, Albrecht Schlosser wrote:
>>>>As I understand it, cygwin 1.7 won'
Christopher Faylor wrote:
On Fri, Aug 29, 2008 at 11:14:23AM +0200, Corinna Vinschen wrote:
On Aug 29 10:22, Albrecht Schlosser wrote:
As I understand it, cygwin 1.7 won't support the old 1.5 managed
mounts, but will have another filename encoding for non-ASCII
filenames. IIRC, I
On Fri, Aug 29, 2008 at 11:14:23AM +0200, Corinna Vinschen wrote:
>On Aug 29 10:22, Albrecht Schlosser wrote:
>>As I understand it, cygwin 1.7 won't support the old 1.5 managed
>>mounts, but will have another filename encoding for non-ASCII
>>filenames. IIRC, I read
On Aug 29 10:22, Albrecht Schlosser wrote:
> As I understand it, cygwin 1.7 won't support the old 1.5 managed
> mounts, but will have another filename encoding for non-ASCII
> filenames. IIRC, I read that all code for the old managed mounts
> has been removed from cygwin 1.7.
>
As I understand it, cygwin 1.7 won't support the old 1.5 managed
mounts, but will have another filename encoding for non-ASCII
filenames. IIRC, I read that all code for the old managed mounts
has been removed from cygwin 1.7.
I'm just curious: How would users of managed mounts trans
John P. Rouillard wrote:
Hello:
I have read a couple of comments (one from cfg IIRC) that managed
mounts are dissapearing from cygwin in version 1.7. So I guess I have
two questions:
1) if I have a managed mount point working well under 1.5, how do
I use the data in the mount point
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John P. Rouillard wrote:
> I have read a couple of comments (one from cfg IIRC) that managed
> mounts are dissapearing from cygwin in version 1.7. So I guess I have
> two questions:
This should answer most of your questions:
http://cygwi
Hello:
I have read a couple of comments (one from cfg IIRC) that managed
mounts are dissapearing from cygwin in version 1.7. So I guess I have
two questions:
1) if I have a managed mount point working well under 1.5, how do
I use the data in the mount point under 1.7?
2) what happens
On 15 January 2008 03:11, Gary R. Van Sickle wrote:
>> From: Dave Korn
>> Sent: Monday, January 14, 2008 8:25 PM
>> Subject: RE: [1.7.0 HEAD]: Cygwin no longer encoding/decoding names on
>> managed mounts
>>
>> On 14 January 2008 21:41, Nicholas Wourms w
Corinna Vinschen wrote:
> On Jan 14 16:41, Nicholas Wourms wrote:
>> Hi All,
>>
>> I'm not sure when this cropped up, but it happened sometime after the
>> great "win 9x" code purge. The problem is that the Cygwin dll no longer
>> decodes o
On Jan 14 16:41, Nicholas Wourms wrote:
> Hi All,
>
> I'm not sure when this cropped up, but it happened sometime after the
> great "win 9x" code purge. The problem is that the Cygwin dll no longer
> decodes or encodes file/directory names on managed mounts.
File h
> From: Dave Korn
> Sent: Monday, January 14, 2008 8:25 PM
> Subject: RE: [1.7.0 HEAD]: Cygwin no longer encoding/decoding
> names on managed mounts
>
> On 14 January 2008 21:41, Nicholas Wourms wrote:
>
> > I'm not sure when this cropped up, but it happened
On 14 January 2008 21:41, Nicholas Wourms wrote:
> I'm not sure when this cropped up, but it happened sometime after the
> great "win 9x" code purge. The problem is that the Cygwin dll no longer
> decodes or encodes file/directory names on managed mounts.
Isn't tha
Hi All,
I'm not sure when this cropped up, but it happened sometime after the
great "win 9x" code purge. The problem is that the Cygwin dll no longer
decodes or encodes file/directory names on managed mounts.
Steps to reproduce (WinXP SP2 x32):
f2EF "/cygdrive/c/Documents and Settings/Francky Leyn/My
Documents/accounts/"
Otherwise, when crossing managed boundaries, you currently have to do:
cp -pR dirA dirB && rm -Rf dirA
[I still wish that attempting a rename(2) on directories between managed
and non-managed mounts woul
On Thu, 2 Aug 2007, Andrew Kruse wrote:
> Hi,
>
> I'm trying to create a new managed mount point and am running into
> some problems.
>
> The exact command I am running: (after successfully creating both
> /usr/.managed/portage and /usr/portage as myself in the cygwin shell)
> mount -o managed `cy
Hi,
I'm trying to create a new managed mount point and am running into
some problems.
The exact command I am running: (after successfully creating both
/usr/.managed/portage and /usr/portage as myself in the cygwin shell)
mount -o managed `cygpath -m /usr/.managed/portage` /usr/portage
Results
While poking around with managed mounts following yesterday's mail, it
occured to me that the managed-mount filename munging misses some cases,
namely, filenames with trailing spaces, and filenames that look like Windows
short-form names corresponding to existing file names.
Here's
On Tuesday, February 20 2007, "Eric Blake" wrote to "Jonathan Lennox,
cygwin@cygwin.com" saying:
> > Cygwin managed mounts give surprising (to me) results if a filename that's
> > not in its canonical form manages to get below the managed mountpoint:
&g
> Cygwin managed mounts give surprising (to me) results if a filename that's
> not in its canonical form manages to get below the managed mountpoint:
The real fix, which I've mentioned before, would be
altering rename() to fail with EXDEV when renaming
files across managed mount p
Cygwin managed mounts give surprising (to me) results if a filename that's
not in its canonical form manages to get below the managed mountpoint:
$ mkdir managed unmanaged
$ mount -o managed `cygpath -aw managed` $PWD/managed
$ mkdir unmanaged/dir
$ touch unmanaged/dir/Foo
$ mv unmanage
I don't know if this warrants a fix, or if the fix would introduce an
unacceptable speed penalty, but managed mounts currently have
strange behavior when creating a file that looks like a drive specifier.
$ cd managed
$ touch ./a:
$ stat ./a:
File: `./a:'
Size: 0
Nicholas Wourms wrote:
> I've discovered a small bug in how Cygwin (CVS HEAD as of Saturday) handles
> reserved dos names created on managed mounts. I discovered this while
> working with a FreeBSD cross-compiler (actually CVS discovered it). Rather
> then bore you with
(Note: I have not re-subscribed to the list yet and probably won't for another
week or so, so please CC me in any replies - TIA)
Hi,
I've discovered a small bug in how Cygwin (CVS HEAD as of Saturday) handles
reserved dos names created on managed mounts. I discovered this while wor
;
>>* path.cc (path_conv::check): retain trailing dots and
>> spaces for managed mounts.
>Er, this patch apparently just leaves the trailing dots in the
>"converted" path, bypassing the loop which attempts to remove them.
>That's not the way to do this. Sorry.
I
On Jul 22 18:30, Dave Korn wrote:
> No it isn't. NTFS is case *preserving*; neither NTFS nor windoze are case
> *sensitive*.
That's only half the truth, though...
> I am right that using the //./ notation invokes the NtCreateFile function,
> aren't I? I think that's why the syntax works for
Dave Korn wrote:
My ${CURRENCY_UNIT}*1e-2: rather than guessing, cvs should *find out*, by
creating a file in the current directory using a name that is known not to
exist, try to unlink it using a shifted version of that name, and then see
if it's gone or not. I *think* that would do the job, w
ase-sensitivity (or otherwise) and how to
>handle it has been a topic of some heated debate on the subversion and
>tortoisesvn maling lists on and off. Consensus on how to handle this
>has proved, shall we say, 'elusive'.
If you're talking about cygwin then why not just u
> -Original Message-
> From: cygwin-owner On Behalf Of Hughes, Bill
> Sent: 22 July 2004 17:24
> From: Ronald Landheer-Cieslak Sent: 22 July 2004 16:49
>
> ..snip..
>
> > OK, the problem is with CVS - the managed mounts are
> working properly.
> >
7;t think many people would be interested in
downloading the sources for cvs to see what you're talking about. From
your description it is difficult to tell if your problem is with cygwin
managed mounts or with cvs.
OK, the problem is with CVS - the managed mounts are working properly.
CVS as
From: Ronald Landheer-Cieslak Sent: 22 July 2004 16:49
..snip..
> OK, the problem is with CVS - the managed mounts are working properly.
> CVS assumes Cygwin is/runs on a case-insensitive (file)system, which is
> usually the case. On managed mounts, however, the assumption fails, a
rested in
downloading the sources for cvs to see what you're talking about. From
your description it is difficult to tell if your problem is with cygwin
managed mounts or with cvs.
OK, the problem is with CVS - the managed mounts are working properly.
CVS assumes Cygwin is/runs on a case
interested in a fix? I don't think many people would be interested in
downloading the sources for cvs to see what you're talking about. From
your description it is difficult to tell if your problem is with cygwin
managed mounts or with cvs.
>The patch would probably be Cygwin-specific,
Hello CVS maintainer (et al.),
I've got a slight problem with CVS when running it on a directory
mounted in managed mode: the directory being case-sensitive, ``cvs
update'' should *IMHO* not warn about a file whose name might clash with
another due to its case (and on ``cvs checkout'', it doesn'
On Feb 21 23:07, Robert R Schneck wrote:
> Igor Pechtchanski <[EMAIL PROTECTED]> wrote:
> > FWIW, WinNT/2k/XP allow executables to not have a .exe extension.
>
> I wasn't aware of it, and haven't been able to figure it out in a couple
> of minutes of playing around and Googling. How?
On NT, the
Igor Pechtchanski <[EMAIL PROTECTED]> wrote:
> On Sat, 21 Feb 2004, Robert R Schneck-McConnell wrote:
>> Hey, it might be interesting for managed mounts *really* to identify the
>> filenames "foo" and "foo.exe". (Maybe they already do?)
>
> Huh? Wh
On Sat, 21 Feb 2004, Robert R Schneck-McConnell wrote:
> [snip]
> Hey, it might be interesting for managed mounts *really* to identify the
> filenames "foo" and "foo.exe". (Maybe they already do?)
>
> Robert
Huh? What do you mean by "identify"
Hi all,
I gather this isn't going to be fixed, which is fine by me, since cp -a
-preserve=all works equally as well. However, I would like to note for
the record and the archives that `mv` is also experiencing problems when
moving non-managed folders to managed mounts as was hypothesiz
accomplish this?
Lester
On Thu, Nov 27, 2003 at 10:36:49AM -0800, Lester Ingber wrote:
>(1)
>I have two managed mounts:
>@lester:~% mount
>C:\cygwin\usr\X11R6\lib\X11\fonts on /usr/X11R6/lib/X11/fonts type system (binmode)
>e:\Carchive\cygwin\managed on /cygdrive/e/Carchive/cygw
On Thu, Nov 27, 2003 at 05:59:45PM -0500, Christopher Faylor wrote:
>On Thu, Nov 27, 2003 at 10:36:49AM -0800, Lester Ingber wrote:
>>I don't understand when and why ".lnk" is attached as a suffix when I
>>create soft links.
>
>Cygwin has a random "mean" mode. It is very effective in producing
>un
On Thu, Nov 27, 2003 at 10:36:49AM -0800, Lester Ingber wrote:
>(1)
>I have two managed mounts:
>@lester:~% mount
>C:\cygwin\usr\X11R6\lib\X11\fonts on /usr/X11R6/lib/X11/fonts type system (binmode)
>e:\Carchive\cygwin\managed on /cygdrive/e/Carchive/cygwin/managed type system
&g
(1)
I have two managed mounts:
@lester:~% mount
C:\cygwin\usr\X11R6\lib\X11\fonts on /usr/X11R6/lib/X11/fonts type system (binmode)
e:\Carchive\cygwin\managed on /cygdrive/e/Carchive/cygwin/managed type system
(binmode,managed)
c:\cygwin\managed on /managed type system (binmode,managed)
C:\cygwin
On Wed, Sep 17, 2003 at 12:29:27PM +0900, Dylan Cuthbert wrote:
>Any trick to get around this "error"? (I presume once -o managed is fully
>debugged this limitation will be removed anyway, or overridable by an option
>at least?)
This is permanent limitation of managed mode. The directory has to
I've tried this out and it seems to work but as Igor pointed out, I can only
use this on empty directories.
The trouble is I have existing directories that need to be backed up via
rsync and I can't change their paths (there are many apps using them in
their current locations).
Any trick to get a
44 matches
Mail list logo
