Re: disk not seen after adminstrative re-install

2005-03-12 Thread Corinna Vinschen
On Mar 11 14:04, Chris Winne wrote: > > Could you please send the output of `cacls e:\' to > > the list? > e:\ Everyone:<0I>F Bummer. That's incredible. I've tried to reproduce the effect and the only way to reproduce it was to drop my "read data" and "read attributes" permissions from the root

Re: disk not seen after adminstrative re-install

2005-03-12 Thread Corinna Vinschen
On Mar 11 22:10, Corinna Vinschen wrote: > On Mar 11 15:49, Fran?ois-David Collin wrote: > > without "notraverse" : > > Filesystem 1K-blocks Used Available Use% Mounted on > > df: `/usr/X11R6/lib/X11/fonts': Permission denied > > df: `/usr/bin': Permission denied > > df: `/usr/lib':

Re: disk not seen after adminstrative re-install

2005-03-11 Thread Chris Winne
> > In other words, cygwin appears to work properly when > started manually through a dos window, while not > when started by "clicking" on the cygwin icon. Further info on this (I asked someone who knows windows what a dos window was): 1) When the CYGWIN=traverse, in a window started with cyg

Re: disk not seen after adminstrative re-install

2005-03-11 Thread Chris Winne
> Could you please send the output of `cacls e:\' to > the list? With notraverse set, both a cygwin window and the dos window (produced with cmd from the run in the start menu), give e:\ Everyone:<0I>F With traverse set, the cygwin window gives, e:\ Access is denied. while we still get "e:\ Ev

Re: disk not seen after adminstrative re-install

2005-03-11 Thread Corinna Vinschen
On Mar 11 15:49, Fran?ois-David Collin wrote: > without "notraverse" : > Filesystem 1K-blocks Used Available Use% Mounted on > df: `/usr/X11R6/lib/X11/fonts': Permission denied > df: `/usr/bin': Permission denied > df: `/usr/lib': Permission denied > df: `/': Permission denied > g:

Re: disk not seen after adminstrative re-install

2005-03-11 Thread Corinna Vinschen
On Mar 11 08:39, Chris Winne wrote: > This one gives some information on e:/ > > 3) df2.trace from: "strace -o df2.trace df" after the > above mount. Yes, too bad. The only useful information in the strace is the fact that GetVolumeInformation fails with "permission denied". Could you please s

Re: disk not seen after adminstrative re-install

2005-03-11 Thread Chris Winne
--- Corinna Vinschen <[EMAIL PROTECTED]> wrote: > What means "without fail"? without notraverse, drive e is never mounted. It is always mounted with notraverse as environmental variable. > Could you please generate an strace of df instead of mount? I have attached 3 traces... 1) df1.trace fr

Re: disk not seen after adminstrative re-install

2005-03-11 Thread François-David Collin
On Fri, 11 Mar 2005 15:47:06 +0100, François-David Collin <[EMAIL PROTECTED]> wrote: > On Thu, 10 Mar 2005 21:57:04 +0100, Corinna Vinschen > <[EMAIL PROTECTED]> wrote: > > On Mar 10 10:30, Chris Winne wrote: > > > --- Corinna Vinschen <[EMAIL PROTECTED]> > > > wrote: > > > > > > > If you can still

Re: disk not seen after adminstrative re-install

2005-03-11 Thread François-David Collin
On Thu, 10 Mar 2005 21:57:04 +0100, Corinna Vinschen <[EMAIL PROTECTED]> wrote: > On Mar 10 10:30, Chris Winne wrote: > > --- Corinna Vinschen <[EMAIL PROTECTED]> > > wrote: > > > > > If you can still reproduce the behaviour, please > > > drop "notraverse" > > > from the CYGWIN variable again and c

Re: disk not seen after adminstrative re-install

2005-03-10 Thread Corinna Vinschen
On Mar 10 10:30, Chris Winne wrote: > --- Corinna Vinschen <[EMAIL PROTECTED]> > wrote: > > > If you can still reproduce the behaviour, please > > drop "notraverse" > > from the CYGWIN variable again and call `strace -o > > mount.trace mount' > > and send the bzip'd mount.trace file to this list.

Re: disk not seen after adminstrative re-install

2005-03-10 Thread Chris Winne
--- Corinna Vinschen <[EMAIL PROTECTED]> wrote: > If you can still reproduce the behaviour, please > drop "notraverse" > from the CYGWIN variable again and call `strace -o > mount.trace mount' > and send the bzip'd mount.trace file to this list. > (should be below > 6 or 7K). > It reproduces wi

Re: disk not seen after adminstrative re-install

2005-03-09 Thread Corinna Vinschen
On Mar 8 13:15, Chris Winne wrote: > Corinna Vinschen wrote: > > The best way to solve that would be to > > revisit the permissions on the toplevel directory on > > drive e. > > Is that through windows? I did go (as user) to the e: > properties-security-advanced where everyone was > allowed full

Re: disk not seen after adminstrative re-install

2005-03-08 Thread Chris Winne
--- Corinna Vinschen <[EMAIL PROTECTED]> wrote: > On Mar 8 09:38, Chris Winne wrote: > > > Also, out from standard error with cygcheck, I got > the > > following: > > > > cygcheck: dump_sysinfo: GetVolumeInformation() > failed: > > 5 > > cygcheck: dump_sysinfo: GetVolumeInformation() > failed:

Re: disk not seen after adminstrative re-install

2005-03-08 Thread Corinna Vinschen
On Mar 8 09:38, Chris Winne wrote: > I should know that if it ain't broke, don't fix it, > but... > > In any case, seeing in installation that installing as > user did not provide all functionality, I decided to > reinstall as administrator. Following installation > and relogging in as myself, m

RE: disk not seen after adminstrative re-install

2005-03-08 Thread Igor Pechtchanski
On Tue, 8 Mar 2005, Dave Korn wrote: > This shouldn't be a problem. The system-level mounts should all be found > before the user-level ones and simply override them harmlessly. Actually, it's the other way around. The system-level mounts are indeed traversed before the user level mounts, but

RE: disk not seen after adminstrative re-install

2005-03-08 Thread Dave Korn
Original Message >From: Chris Winne >Sent: 08 March 2005 17:39 > I should know that if it ain't broke, don't fix it, > but... Um so does that mean you would consider it _good_ news if I tell you that it looks very much like it was broke after all? > In any case, seeing in installa

disk not seen after adminstrative re-install

2005-03-08 Thread Chris Winne
I should know that if it ain't broke, don't fix it, but... In any case, seeing in installation that installing as user did not provide all functionality, I decided to reinstall as administrator. Following installation and relogging in as myself, my first sign of something fishy was an extra cygwi