DePriest, Jason R. gmail.com> writes:
> Will your proposed changes in coreutils fix the following problem I
> just discovered today?
This is the exact same problem documented earlier in this thread, and yes,
coreutils-6.9-1 will fix it (I'm getting closer; I've finally completed my
testing of
On 4/9/07, Eric Blake wrote:
[ cut out lots of useful information to save space ]
Will your proposed changes in coreutils fix the following problem I
just discovered today?
Create a symbolic link
ln -s /usr/bin/foo /foo
where /usr/bin/foo is really usr/bin/foo.exe
ls -l /foo
returns
foo -> /us
> Brian Dessent wrote:
> > Eric Blake wrote:
>
> > when creating symlinks, I plan to still auto-append the .exe to the link
> > target if necessary (otherwise, exec*() succeeds but open() fails when
> > dereferencing the symlink), but not to the link name.
>
> That sounds correct. If open() fai
Eric Blake wrote:
> when creating symlinks, I plan to still auto-append the .exe to the link
> target if necessary (otherwise, exec*() succeeds but open() fails when
> dereferencing the symlink), but not to the link name.
That sounds correct. If open() fails on a link target that's missing an
.e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Revisiting an old thread...
According to Corinna Vinschen on 1/24/2007 7:38 AM:
> On Jan 24 06:45, Eric Blake wrote:
>> According to Corinna Vinschen on 1/24/2007 2:48 AM:
>>> This looks rather like a problem with the exe magic in coreutils. FWIW,
>>
On Jan 24 06:45, Eric Blake wrote:
> According to Corinna Vinschen on 1/24/2007 2:48 AM:
> > This looks rather like a problem with the exe magic in coreutils. FWIW,
> > I never liked the idea to create "foo.exe.lnk" symlinks. They only slow
> > down the symlink processing in Cygwin.
>
> Should w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 1/24/2007 2:48 AM:
>
> This looks rather like a problem with the exe magic in coreutils. FWIW,
> I never liked the idea to create "foo.exe.lnk" symlinks. They only slow
> down the symlink processing in Cygwin.
Shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Pierre A. Humblet on 1/23/2007 4:07 PM:
> When a user runs exim-config, the following line is executed:
>ln -s -f /usr/bin/exim /usr/sbin/sendmail
>
> Do you want to link /usr/sbin/sendmail to /usr/sbin/ssmtp (y/N)? y
> and it runs
>
On Jan 23 20:36, Christopher Layne wrote:
> On Tue, Jan 23, 2007 at 06:07:17PM -0500, Pierre A. Humblet wrote:
> > /usr/sbin: ls -l sendmail*
> > lrwxrwxrwx 1 p-humblet sw 13 Jan 23 17:40 sendmail -> /usr/bin/exim*
> > lrwxrwxrwx 1 p-humblet sw 19 Jan 23 17:29 sendmail.exe ->
> > /usr/sbin/ssmtp.e
On Tue, Jan 23, 2007 at 06:07:17PM -0500, Pierre A. Humblet wrote:
> /usr/sbin: ls -l sendmail*
> lrwxrwxrwx 1 p-humblet sw 13 Jan 23 17:40 sendmail -> /usr/bin/exim*
> lrwxrwxrwx 1 p-humblet sw 19 Jan 23 17:29 sendmail.exe -> /usr/sbin/ssmtp.exe*
>
> so that the commands "sendmail" and "sendmail.
When a user runs exim-config, the following line is executed:
ln -s -f /usr/bin/exim /usr/sbin/sendmail
If later the user switches to ssmtp, ssmtp-config asks
(6) link /usr/sbin/sendmail to /usr/sbin/ssmtp?
Some programs (e.g. cron) expect /usr/sbin/sendmail to handle mail.
Currently it is a
11 matches
Mail list logo
