On Sat, Apr 05, 2003 at 02:00:33PM -0500, Igor Pechtchanski wrote:
>On Sat, 5 Apr 2003, John Morrison wrote:
>
>> > From: Pierre A. Humblet
>> >
>> > Have we heard from the maintainer of base-files-mketc.sh recently?
>>
>> Yeah - I'm here ;)
&
On Sat, 5 Apr 2003, John Morrison wrote:
> > From: Pierre A. Humblet
> >
> > Have we heard from the maintainer of base-files-mketc.sh recently?
>
> Yeah - I'm here ;)
>
> > About two months ago there was a discussion about putting Windows
> > paths in t
> From: Pierre A. Humblet
>
> Have we heard from the maintainer of base-files-mketc.sh recently?
Yeah - I'm here ;)
> About two months ago there was a discussion about putting Windows
> paths in the symlinks (to avoid problems when changing /cygdrive
> and with user dep
Have we heard from the maintainer of base-files-mketc.sh recently?
About two months ago there was a discussion about putting Windows
paths in the symlinks (to avoid problems when changing /cygdrive
and with user dependent mounts), but the script was never updated.
Pierre
On Tue, 2003-02-04 at 05:26, Igor Pechtchanski wrote:
> True, but doesn't mean we can't do it on initial install, at least. We
> could also pop up a warning box... This actually gives merit to the idea
> of the "Advanced" button, since most users probably will not go there.
'Advanced' buttons
I guess it would have been simpler if I had
sent the new version directly (tested on WinME)
Pierre
#!/bin/sh
#--
# Create symbolic links from some /etc files to the Windows equivalents
#--
FILES="hosts protocols services networks"
OSNAME="`/bin/uname -s`"
WINHOME="`/bin/cygpath -w -W`"
CYGWI
On Mon, 3 Feb 2003, Max Bowsher wrote:
> Igor Pechtchanski wrote:
> > Perhaps, instead of making
> > a whole bunch of new controls in one propsheet, we should have an
> > "Advanced..." button that would pop up a dialog with all the extra
> > options... What do people think?
>
> > IMHO, changing t
> On Mon, 3 Feb 2003, Igor Pechtchanski wrote:
>
> >If I understand the (new style) symlink implementation correctly, both the
> >POSIX path and the Windows path are needed in the corresponding shortcut.
On Mon, 3 Feb 2003, Pierre A. Humblet wrote:
> [snip]
>
> I haven't looked into the implement
On Mon, 3 Feb 2003, Pierre A. Humblet wrote:
> At 12:29 PM 2/3/2003 -0500, Igor Pechtchanski wrote:
> >> What else do you think of?
> >
> >Hmm, I'm not sure. You may be right for the moment (on a new install, in
> >any case). However, any postinstall script using the `cygpath -u ...`
> >syntax w
Igor Pechtchanski wrote:
> Perhaps, instead of making
> a whole bunch of new controls in one propsheet, we should have an
> "Advanced..." button that would pop up a dialog with all the extra
> options... What do people think?
> IMHO, changing the cygdrive prefix is an advanced user action, and th
At 12:29 PM 2/3/2003 -0500, Igor Pechtchanski wrote:
>> What else do you think of?
>
>Hmm, I'm not sure. You may be right for the moment (on a new install, in
>any case). However, any postinstall script using the `cygpath -u ...`
>syntax would have that problem, and who can guarantee that no othe
On Mon, 3 Feb 2003, Pierre A. Humblet wrote:
> At 11:46 AM 2/3/2003 -0500, Igor Pechtchanski wrote:
>
> >FYI, base-files-mketc.sh uses the `cygpath -u ...` syntax to get the
> >directory.
> Yep, I saw that.
>
> >Thus, if your cygdrive prefix is changed *before* the
&
At 11:46 AM 2/3/2003 -0500, Igor Pechtchanski wrote:
>FYI, base-files-mketc.sh uses the `cygpath -u ...` syntax to get the
>directory.
Yep, I saw that.
>Thus, if your cygdrive prefix is changed *before* the
>postinstall scripts run, the script should pick up the correct on
w install.
> It would be more robust (and easier and efficient) to use the Windows
> paths in the symlinks.
>
> Pierre
Pierre,
FYI, base-files-mketc.sh uses the `cygpath -u ...` syntax to get the
directory. Thus, if your cygdrive prefix is changed *before* the
postinstall scripts run, th
Having recently installed Cygwin on a new machine, I noticed
that the symbolic links to the base files in /etc use Cygwin
syntax (/cygdrive/c/).
They break when /cygdrive is modified, which is frequently the
case on a new install.
It would be more robust (and easier and efficient) to use the
On Wed, 30 Oct 2002, Christopher Faylor wrote:
> On Mon, Oct 28, 2002 at 04:37:49PM -0500, Igor Pechtchanski wrote:
> >On Mon, 28 Oct 2002, Christopher Faylor wrote:
> >> Maybe someone will be kind enough to tell me what this is in reference to.
> >
> >The -l option in the cygpath distributed with
On Mon, Oct 28, 2002 at 04:37:49PM -0500, Igor Pechtchanski wrote:
>On Mon, 28 Oct 2002, Christopher Faylor wrote:
>> Maybe someone will be kind enough to tell me what this is in reference to.
>
>The -l option in the cygpath distributed with the cygwin package prints
>out garbage. The same cygpath
On Wed, Oct 30, 2002 at 09:29:40PM -, John Morrison wrote:
>> >> The -l option in the cygpath distributed with the cygwin package prints
>> >> out garbage. The same cygpath compiled anew works. The problem is
>> >> described (among other places) here:
>> >> http://cygwin.com/ml/cygwin/2002-09
Christopher; what does
cygpath -w -l "/cygdrive/c/WINNT/system32/drivers/etc"
output on your system?
J.
> >> The -l option in the cygpath distributed with the cygwin package prints
> >> out garbage. The same cygpath compiled anew works. The problem is
> >> described (among other places) here:
> >> http://cygwin.com/ml/cygwin/2002-09/msg00749.html
> >>Igor
> >
> >It would be nice to add this scr
On Wed, Oct 30, 2002 at 08:52:27PM -, John Morrison wrote:
>cfg: did this help?
>
>> From: Igor Pechtchanski
>>
>> On Mon, 28 Oct 2002, Christopher Faylor wrote:
>> > > I don't know what it is with the build process employed by cgf
>> > > that breaks cygpath...
>> >
>> > Maybe someone will be k
cfg: did this help?
> From: Igor Pechtchanski
>
> On Mon, 28 Oct 2002, Christopher Faylor wrote:
> > > I don't know what it is with the build process employed by cgf
> > > that breaks cygpath...
> >
> > Maybe someone will be kind enough to tell me what this is in
> reference to.
> > I've just down
On Mon, 28 Oct 2002, Christopher Faylor wrote:
> On Mon, Oct 28, 2002 at 10:00:47AM -0500, Igor Pechtchanski wrote:
> >On Mon, 28 Oct 2002, Paul Johnston wrote:
> >
> >> Hi,
> >>
> >> > Cygpath is part of the cygwin package. I'm running the current latest
> >> > 1.3.14-1, which was compiled on We
On Mon, Oct 28, 2002 at 10:00:47AM -0500, Igor Pechtchanski wrote:
>On Mon, 28 Oct 2002, Paul Johnston wrote:
>
>> Hi,
>>
>> > Cygpath is part of the cygwin package. I'm running the current latest
>> > 1.3.14-1, which was compiled on Wed, 23 Oct. It still has the bug.
>> >
>> > Perhaps this shoul
On Mon, 28 Oct 2002, Paul Johnston wrote:
> Hi,
>
> > Cygpath is part of the cygwin package. I'm running the current latest
> > 1.3.14-1, which was compiled on Wed, 23 Oct. It still has the bug.
> >
> > Perhaps this should be fixed first?
>
> Yes, I agree. The problem was something to do with it
> From: Paul Johnston [mailto:paj@;pajhome.org.uk]
>
> Hi,
>
> > Cygpath is part of the cygwin package. I'm running the
> current latest
> > 1.3.14-1, which was compiled on Wed, 23 Oct. It still has the bug.
> >
> > Perhaps this should be fixed first?
>
> Yes, I agree. The problem was somethi
Hi,
> Cygpath is part of the cygwin package. I'm running the current latest
> 1.3.14-1, which was compiled on Wed, 23 Oct. It still has the bug.
>
> Perhaps this should be fixed first?
Yes, I agree. The problem was something to do with it being linked against
the wrong version of a library. I t
> From: Morrison, John [mailto:John.Morrison@;uk.experian.com]
(I hate replying to myself :(
> > From: Paul Johnston [mailto:paj@;pajhome.org.uk]
> >
> > Hi John,
> >
> > It's true that it doesn't work with the broken cygpath, but
> > it doesn't do
> > anything bad in that case, and the bug is
> From: Paul Johnston [mailto:paj@;pajhome.org.uk]
>
> Hi John,
>
> It's true that it doesn't work with the broken cygpath, but
> it doesn't do
> anything bad in that case, and the bug is very clearly with
> the cygpath binary.
>
> One thought I had was to add the second line to this error mes
Hi John,
It's true that it doesn't work with the broken cygpath, but it doesn't do
anything bad in that case, and the bug is very clearly with the cygpath
binary.
One thought I had was to add the second line to this error message:
echo "Directory $WINETC does not exist; exiting" >&2
echo "If
30 matches
Mail list logo
