On Sun, Jul 18, 2004 at 01:43:18PM +0100, Dave Korn wrote:
Another possible place to mention the Cygwin-specific READMEs is in the
man cygwin page. :-)
Another possibility would be for the very last dialog in setup.exe, the
one that says download/install complete, to also say in very big
letters
On Fri, Jul 16, 2004 at 09:53:44PM -0400, Igor Pechtchanski wrote:
On Fri, 16 Jul 2004, Christopher Faylor wrote:
On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote:
I'm partial to:
cygcheck -l ssmtp|fgrep README|xargs less
myself. Works for other
-Original Message-
From: cygwin-owner On Behalf Of Igor Pechtchanski
Sent: 16 July 2004 20:12
This is a usability issue. It's hard enough to teach
people to type:
man command-name
teaching them to type:
more
[EMAIL PROTECTED] wrote:
(= Dave K, I believe)
Another possibility would be for the very last dialog in setup.exe,
the one that says download/install complete, to also say in very
big letters For Cygwin-specific documentation, see
/usr/share/doc/Cygwin. It could maybe even have a tickbox to
At 10:51 AM 7/18/2004, you wrote:
[EMAIL PROTECTED] wrote:
(= Dave K, I believe)
Another possibility would be for the very last dialog in setup.exe,
the one that says download/install complete, to also say in very
big letters For Cygwin-specific documentation, see
/usr/share/doc/Cygwin. It
-Original Message-
From: cygwin-owner On Behalf Of Larry Hall
Sent: 18 July 2004 18:13
At 10:51 AM 7/18/2004, you wrote:
[EMAIL PROTECTED] wrote:
(= Dave K, I believe)
Another possibility would be for the very last dialog in
setup.exe,
the one that says download/install
On Jul 16 12:01, [EMAIL PROTECTED] wrote:
On 15 Jul, Corinna Vinschen wrote:
Incidentally is it appropriate to include Cygwin-port-specific
information in a man page?
Well, from a user perspective it might be cool, but IMHO the original
man page shouldn't be changed, unless
On Fri, 16 Jul 2004, Corinna Vinschen wrote:
On Jul 16 12:01, luke.kendallSPLATcisra.canon.com.au wrote:
On 15 Jul, Corinna Vinschen wrote:
Incidentally is it appropriate to include Cygwin-port-specific
information in a man page?
Well, from a user perspective it might be cool,
On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote:
This is a usability issue. It's hard enough to teach people to type:
man command-name
teaching them to type:
more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y
I'm partial to:
cygcheck -l ssmtp|fgrep
On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote:
On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote:
This is a usability issue. It's hard enough to teach people to type:
man command-name
teaching them to type:
more
On Fri, 16 Jul 2004, Christopher Faylor wrote:
On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote:
On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote:
This is a usability issue. It's hard enough to teach people to type:
man command-name
teaching them
On Fri, Jul 16, 2004 at 09:53:44PM -0400, Igor Pechtchanski wrote:
On Fri, 16 Jul 2004, Christopher Faylor wrote:
On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote:
On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote:
This is a usability issue. It's hard enough
On Jul 15 10:01, you wrote:
On 14 Jul, Igor Pechtchanski wrote:
Yep, that would be a very good idea. In particular, it should point out
that the information in the READMEs in /usr/share/doc/Cygwin takes
precedence over that in the package READMEs and manpages.
Maybe even an
On 14 Jul, Pierre A. Humblet wrote:
At 12:02 PM 7/15/2004 +1000, [EMAIL PROTECTED] wrote:
On 14 Jul, Pierre A. Humblet wrote:
Thanks for the feedback.
The problem is that the exim startup code thinks that you are a
privileged
user (see privileged 1 above). It does that by
On 15 Jul, To: Pierre A. Humblet wrote:
: /home/luke ; mkgroup -l /etc/group
Incidentally, after doing that I see:
: /home/luke ; exim -oi luke /tmp/smff3624
2004-07-15 17:56:06 Exim configuration file /etc/exim.conf has the wrong owner, group,
or mode
: /home/luke ; ls -l /etc/exim.conf
On Jul 15 01:39, Robert R Schneck wrote:
Pierre A. Humblet wrote:
Luke Kendall wrote:
or that it creates a symlink to sendmail.
exim doesn't. That symlink is created by the cygwin specific exim-config
script under explicit user control. That avoids possible conflicts with
postinstall
On Jul 15 17:57, [EMAIL PROTECTED] wrote:
On 15 Jul, To: Pierre A. Humblet wrote:
: /home/luke ; mkgroup -l /etc/group
Incidentally, after doing that I see:
: /home/luke ; exim -oi luke /tmp/smff3624
2004-07-15 17:56:06 Exim configuration file /etc/exim.conf has the wrong owner,
Robert R Schneck wrote on Thursday, July 15, 2004 3:39 AM:
Pierre A. Humblet wrote:
Luke Kendall wrote:
or that it creates a symlink to sendmail.
exim doesn't. That symlink is created by the cygwin specific
exim-config script under explicit user control. That avoids possible
conflicts
At 05:57 PM 7/15/2004 +1000, [EMAIL PROTECTED] wrote:
On 15 Jul, To: Pierre A. Humblet wrote:
: /home/luke ; mkgroup -l /etc/group
Incidentally, after doing that I see:
: /home/luke ; exim -oi luke /tmp/smff3624
2004-07-15 17:56:06 Exim configuration file /etc/exim.conf has the wrong
owner,
At 10:18 AM 7/15/2004 +0200, Corinna Vinschen wrote:
On Jul 15 01:39, Robert R Schneck wrote:
Pierre A. Humblet wrote:
Luke Kendall wrote:
or that it creates a symlink to sendmail.
exim doesn't. That symlink is created by the cygwin specific exim-config
script under explicit user
On Thu, 15 Jul 2004 09:47:39 +0200, Corinna Vinschen wrote:
Can I also suggest that the FAQ's section called Where can I get more
information? / Where's the documentation? would be an excellent place
to mention that all the per-package readme files are collected together
in
On 15 Jul, Pierre A. Humblet wrote:
: /home/luke ; exim -oi luke /tmp/smff3624
2004-07-15 17:56:06 Exim configuration file /etc/exim.conf has the wrong
owner, group, or mode
: /home/luke ; ls -l /etc/exim.conf
-rwx--+ 1 luke Domain U22025 Aug 29 2002 /etc/exim.conf
On 15 Jul, Corinna Vinschen wrote:
Incidentally is it appropriate to include Cygwin-port-specific
information in a man page?
Well, from a user perspective it might be cool, but IMHO the original
man page shouldn't be changed, unless it's a change which should be
send upstream
On Fri, Jul 16, 2004 at 11:24:01AM +1000, luke kendal at cisra.canon.com.au wrote:
On 15 Jul, Pierre A. Humblet wrote:
: /home/luke ; exim -oi luke /tmp/smff3624
2004-07-15 17:56:06 Exim configuration file /etc/exim.conf has the wrong
owner, group, or mode
: /home/luke ; ls -l
At 12:47 AM 7/14/2004, you wrote:
Larry Hall [EMAIL PROTECTED] wrote:
At 10:16 PM 7/13/2004, you wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I appear to have both exim and ssmtp installed; but I see that
/usr/sbin/sendmail is a symlink to /usr/bin/ssmtp. Fair enough, if
interesting.
In
On Jul 14 10:31, Larry Hall wrote:
At 12:47 AM 7/14/2004, you wrote:
Larry Hall [EMAIL PROTECTED] wrote:
At 10:16 PM 7/13/2004, you wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I appear to have both exim and ssmtp installed; but I see that
/usr/sbin/sendmail is a symlink to
At 11:07 AM 7/14/2004, you wrote:
On Jul 14 10:31, Larry Hall wrote:
At 12:47 AM 7/14/2004, you wrote:
Larry Hall [EMAIL PROTECTED] wrote:
At 10:16 PM 7/13/2004, you wrote:
[EMAIL PROTECTED] xxx wrote:
I appear to have both exim and ssmtp installed; but I see that
/usr/sbin/sendmail is a
On Jul 14 12:45, Larry Hall wrote:
At 11:07 AM 7/14/2004, you wrote:
I don't think cron should contain a dependency to ssmtp though. It would
be the same as to have a dependency to exim.
Well, I brought it up since it explicitly creates the link to ssmtp. An
easier alternative would
At 01:17 PM 7/14/2004, you wrote:
On Jul 14 12:45, Larry Hall wrote:
At 11:07 AM 7/14/2004, you wrote:
I don't think cron should contain a dependency to ssmtp though. It would
be the same as to have a dependency to exim.
Well, I brought it up since it explicitly creates the link to ssmtp.
Corinna Vinschen [EMAIL PROTECTED] wrote:
I don't think cron should contain a dependency to ssmtp though. It
would be the same as to have a dependency to exim. And why should
cron.README contain hints about how to set up ssmtp? That's the job
for the ssmtp README, isn't it?
It might save
On Wed, 14 Jul 2004, Robert R Schneck wrote:
Corinna Vinschen [EMAIL PROTECTED] wrote:
I don't think cron should contain a dependency to ssmtp though. It
would be the same as to have a dependency to exim. And why should
cron.README contain hints about how to set up ssmtp? That's the job
On Wed, 14 Jul 2004, Igor Pechtchanski wrote:
On Wed, 14 Jul 2004, Robert R Schneck wrote:
Corinna Vinschen [EMAIL PROTECTED] wrote:
[snip]
Whoops, and a (very belated) http://cygwin.com/acronyms/#PCYMTNQREAIYR
to both of us... :-)
Igor
--
On 14 Jul, Robert R Schneck wrote:
I also see that my /etc/ssmtp directory is completely empty. Someone
on the list mentioned /usr/local/exim/README.Cygwin, but there is no
/usr/local/exim directory on my machine.
You should have read /usr/share/doc/Cygwin/ssmtp-2.60.9.README.
On 14 Jul, Igor Pechtchanski wrote:
Yep, that would be a very good idea. In particular, it should point out
that the information in the READMEs in /usr/share/doc/Cygwin takes
precedence over that in the package READMEs and manpages.
Maybe even an FAQ entry like I've followed
Larry Hall wrote:
Corinna Vinschen wrote:
Methinks that a correct approach (for a given value of correct) would
be to create the symlink in an ssmtp postinstall script. That's what
exim does, too. Creating the symlink in the cron postinstall script
was a hack at one point. I'd be happy to get
On 14 Jul, Pierre A. Humblet wrote:
exim -oi luke /tmp/sample
I got this error:
set{u,g}id failed: 22
2004-07-14 10:48:44 unable to set gid=544 or uid=18 (euid=11021): privilege not
needed
(Which I assume means the opposite: that some privilege *is*
At 10:14 AM 7/15/2004 +1000, [EMAIL PROTECTED] wrote:
On 14 Jul, Pierre A. Humblet wrote:
(That message was rejected by the list spam filter,
I hope this one will make it through)
exim -oi luke /tmp/sample
I got this error:
set{u,g}id failed: 22
2004-07-14 10:48:44
On Thu, Jul 15, 2004 at 09:44:45AM +1000, [EMAIL PROTECTED] wrote:
snip
I also noticed that the exim man page doesn't mention that it can
replace sendmail
That's the standard exim man page, wrong list..
or that it creates a symlink to sendmail.
exim doesn't. That symlink is created by
Pierre A. Humblet wrote:
Luke Kendall wrote:
or that it creates a symlink to sendmail.
exim doesn't. That symlink is created by the cygwin specific exim-config
script under explicit user control. That avoids possible conflicts with
postinstall scripts.
Hmmm. So perhaps the appropriate new
On 14 Jul, Pierre A. Humblet wrote:
Thanks for the feedback.
The problem is that the exim startup code thinks that you are a privileged
user (see privileged 1 above). It does that by checking that you have the
Create Token privilege (you have not answered my question about having
At 12:02 PM 7/15/2004 +1000, [EMAIL PROTECTED] wrote:
On 14 Jul, Pierre A. Humblet wrote:
Thanks for the feedback.
The problem is that the exim startup code thinks that you are a
privileged
user (see privileged 1 above). It does that by checking that you have
the
Create Token
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I appear to have both exim and ssmtp installed; but I see that
/usr/sbin/sendmail is a symlink to /usr/bin/ssmtp. Fair enough, if
interesting.
In fact, the ssmtp package does not create the sendmail symlink.
As far as I can tell, no Cygwin package
At 10:16 PM 7/13/2004, you wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I appear to have both exim and ssmtp installed; but I see that
/usr/sbin/sendmail is a symlink to /usr/bin/ssmtp. Fair enough, if
interesting.
In fact, the ssmtp package does not create the sendmail symlink.
As far
Larry Hall [EMAIL PROTECTED] wrote:
At 10:16 PM 7/13/2004, you wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I appear to have both exim and ssmtp installed; but I see that
/usr/sbin/sendmail is a symlink to /usr/bin/ssmtp. Fair enough, if
interesting.
In fact, the ssmtp package does not
44 matches
Mail list logo
