Re: setup - duplicating cygwin

Jim Easton wrote: cd /cygdrive/c/cygwin cd proc For which I received the message: "bash: cd: proc: No such file or directory" Of course. As you surmised, these two are *NOT* the same. The literal path "/proc" (and "/dev") are treated specially. Unlike on linux, "mount" is not modifying the

Re: setup - duplicating cygwin

Hi Corinna, > On Jun 20 02:58, Jim Easton wrote: > > Question: is /proc implemented and I just haven't figured out how to > > install it? > > Did you try > > $ cd /proc > $ ls -l > > before asking? Oh Dear! I tried: cd /cygdrive/c/cygwin cd proc For which I received the message: "bash:

Re: setup - duplicating cygwin

On Jun 20 02:58, Jim Easton wrote: > Question: is /proc implemented and I just haven't figured out how to > install it? Did you try $ cd /proc $ ls -l before asking? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cy

Re: setup - duplicating cygwin

Hi Igor, > > Tell me; In case things go wrong, to recover my present configuration > > is it sufficient to simply restore /cygdrive/c/cygwin and > > /cygdrive/c/cygwin.disk or is there something more subtle going on. > > If you didn't change the mounts, it should be sufficient to restore > c:\cyg

Re: setup - duplicating cygwin

On Mon, 19 Jun 2006, Jim Easton wrote: > Hi Igor > > > > 1) using windows read "installed.db" into "my documents" > > > 2) the version numbers were already set to zero. > > > > Whup. Stop right here. When you say "the version numbers were already > > set to zero", you don't mean those extra zero

Re: setup - duplicating cygwin

Hi Igor > > 1) using windows read "installed.db" into "my documents" > > 2) the version numbers were already set to zero. > > Whup. Stop right here. When you say "the version numbers were already > set to zero", you don't mean those extra zeroes at the end of each line, > do you? Because if yo

RE: setup - duplicating cygwin

On Sun, 18 Jun 2006, Igor Peshansky wrote: > On Sun, 18 Jun 2006, Jim Easton wrote: > > > Hi, > > > > Tue, 16 May 2006 I wrote: > > > Would someone please tell me what file(s) I would have to take with > > > me (eg. on a disk) to someone else's machine, both running windows XP, > > > whereby I cou

RE: setup - duplicating cygwin

On Sun, 18 Jun 2006, Jim Easton wrote: > Hi, > > Tue, 16 May 2006 I wrote: > > Would someone please tell me what file(s) I would have to take with > > me (eg. on a disk) to someone else's machine, both running windows XP, > > whereby I could get setup to download the same cygwin components that >

RE: setup - duplicating cygwin

Hi, Tue, 16 May 2006 I wrote: > Would someone please tell me what file(s) I would have to take with > me (eg. on a disk) to someone else's machine, both running windows XP, > whereby I could get setup to download the same cygwin components that > are on my machine? Wed, 17 May 2006 I wrote: > I s

Re: setup - duplicating cygwin

Hi Igor, > Ugh, top-posting... Reformatted. Oops - sorry. Some people prefer it :-( Does not include me actually. It gets a little hard to follow if it's not consistent. > On Wed, 17 May 2006, Jim Easton wrote: > > > > From: "Dave Korn" <[EMAIL PROTECTED]> > >

RE: setup - duplicating cygwin

Ugh, top-posting... Reformatted. On Wed, 17 May 2006, Jim Easton wrote: > > From: "Dave Korn" <[EMAIL PROTECTED]> . Thanks. > > On 16 May 2006 09:20, Jim Easton wrote: > > > > > Hi, > > > > > > Would someone please tell me what file(s) I would

RE: setup - duplicating cygwin

Hi Dave, Thank you for the suggestion. Correct me if I'm wrong but I take it that that would be the stuff in cygwin.disk? I should clarify. I have no problem with loading new versions of things, what I was after was a way of priming setup with the list of names at the "Select packages" step. I

RE: setup - duplicating cygwin

On 16 May 2006 09:20, Jim Easton wrote: > Hi, > > Would someone please tell me what file(s) I would have to take with > me (eg. on a disk) to someone else's machine, both running windows XP, > whereby I could get setup to download the same cygwin components that > are on my machine? How about