Path confusion

2005-03-23 Thread Luke Kendall
Here's something that stunned me: I see different contents of a directory I want to be "empty-ish" (c:/cygwin/home), depending on how I refer to it. I think it's because sometimes, "c:/cygwin" == "/". $ cygpath -m / C:/cygwin $ ls c:/cygwin/home 00-THIS-DIRECTORY-SHOULD-BE-EMPTY.txt $ cd c:/cyg

Re: Path confusion

2005-03-23 Thread Brian Dessent
Luke Kendall wrote: > Here's something that stunned me: I see different contents of a > directory I want to be "empty-ish" (c:/cygwin/home), depending on how I > refer to it. I think it's because sometimes, "c:/cygwin" == "/". > > $ cygpath -m / > C:/cygwin > > $ ls c:/cygwin/home > 00-THIS-DIR

Re: Path confusion

2005-03-31 Thread Luke Kendall
On 23 Mar, Brian Dessent wrote: > Luke Kendall wrote: > > > Here's something that stunned me: I see different contents of a > > directory I want to be "empty-ish" (c:/cygwin/home), depending on how I > > refer to it. I think it's because sometimes, "c:/cygwin" == "/". > > > > $ cygpath -m / >

Re: Path confusion

2005-03-31 Thread Igor Pechtchanski
On Fri, 1 Apr 2005, Luke Kendall wrote: > On 23 Mar, Brian Dessent wrote: > > Luke Kendall wrote: > > > > > Here's something that stunned me: I see different contents of a > > > directory I want to be "empty-ish" (c:/cygwin/home), depending on how I > > > refer to it. I think it's because someti

Re: Path confusion

2005-03-31 Thread Luke Kendall
On 31 Mar, Igor Pechtchanski wrote: > > The problem is then that there are two /home directories: the real > > /home that's mounted on, say d:/home, and the fake /home, formed by > > re-writing "c:/cygwin" as "/", and tacking on the home subdirectory. > > > > I think the solution is that I

Re: Path confusion

2005-03-31 Thread Brian Dessent
Luke Kendall wrote: > find `cygpath -m /` -xdev -user $USER -print \ >| tr "\n" "\000" \ >| xargs -0 chown Administrators.SYSTEM You can use -print0, and since find is a cygwin application I don't see what the point of using cygpath is: find / -xdev -user $USER -print0 | xarg

Re: Path confusion

2005-03-31 Thread Igor Pechtchanski
Luke, Please make sure your mailer respects the Reply-To: header -- I set it for a reason. On Fri, 1 Apr 2005, Luke Kendall wrote: > On 31 Mar, Igor Pechtchanski wrote: > > > The problem is then that there are two /home directories: the real > > > /home that's mounted on, say d:/home, and the

Re: Path confusion

2005-03-31 Thread Igor Pechtchanski
On Thu, 31 Mar 2005, Brian Dessent wrote: > Luke Kendall wrote: > > > find `cygpath -m /` -xdev -user $USER -print \ > >| tr "\n" "\000" \ > >| xargs -0 chown Administrators.SYSTEM > > You can use -print0, and since find is a cygwin application I don't see > what the point of u

Re: Path confusion

2005-03-31 Thread Luke Kendall
On 1 Apr, Igor Pechtchanski wrote: > Please make sure your mailer respects the Reply-To: header -- I set it for > a reason. My apologies. I actually went looking for a Mail-Followup-To header in your messge, http://cr.yp.to/proto/replyto.html> and, not seeing one, wrongly assumed that you (l

Re: Path confusion

2005-03-31 Thread Luke Kendall
On 1 Apr, Igor Pechtchanski wrote: > > Luke Kendall wrote: > > > > > find `cygpath -m /` -xdev -user $USER -print \ > > >| tr "\n" "\000" \ > > >| xargs -0 chown Administrators.SYSTEM Brian Dessent: > > > > You can use -print0, and since find is a cygwin applicatio

Re: Path confusion

2005-03-31 Thread Luke Kendall
On 1 Apr, To: cygwin@cygwin.com wrote: > > You must mean 'chown -R --from="$USER" ...' :-) > > Hmm, sounds better still. :-) D'oh! Not possible: there's no -xdev option on chown, so that would do a whole lot more chown-ing than intended, as it reached across the network, or at least in

Re: Path confusion

2005-04-01 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [moving feature request portion of thread to bug-coreutils] According to Luke Kendall on 4/1/2005 12:11 AM: find / -xdev -user "$USER" -print0 | xargs -0 chown Administrators.SYSTEM >>> >>> You must mean 'chown -R --from="$USER" ...' :-) >>

Re: Path confusion

2005-04-01 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Luke Kendall on 4/1/2005 12:11 AM: > While just checking that, I also discovered that "man chown" now > produces no output. Other man entries seem fine. > > $ cygcheck -s | grep "^cygwin " > cygcheck: dump_sysinfo: GetVolumeInformation()

Re: Path confusion

2005-04-01 Thread Igor Pechtchanski
On Fri, 1 Apr 2005, Luke Kendall wrote: > On 1 Apr, To: [EMAIL PROTECTED] wrote: ^ Eh? :-) > > > You must mean 'chown -R --from="$USER" ...' :-) > > > > Hmm, sounds better still. :-) > > D'oh! Not possible: there's no -xdev option on chown, so that would > d

Re: Path confusion

2005-04-01 Thread Bob Proulx
Eric Blake wrote: > [moving feature request portion of thread to bug-coreutils] > > According to Luke Kendall on 4/1/2005 12:11 AM: > find / -xdev -user "$USER" -print0 | xargs -0 chown Administrators.SYSTEM > >>> > >>> You must mean 'chown -R --from="$USER" ...' :-) > >> > >> Hmm, sound

Re: Path confusion

2005-04-01 Thread Jim Meyering
Eric Blake <[EMAIL PROTECTED]> wrote: > How about it - does it make sense to add an --xdev option to all of the > recursive descent tools (chown, chmod, ls, ...) to force the recursion to > stop at mount points, or is find/xargs the only supported idiom for this? It's seductive, but I don't think

Re: Path confusion

2005-04-03 Thread Luke Kendall
On 1 Apr, Igor Pechtchanski wrote: > On Fri, 1 Apr 2005, Luke Kendall wrote: > > > On 1 Apr, To: [EMAIL PROTECTED] wrote: > ^ > Eh? :-) A peculiarity of my MUA, when used to reply to my own messages. Sorry. [...] > > While just checking that, I also discov