public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Vince Rice <vrice@solidrocksystems.com>
To: cygwin@cygwin.com
Subject: Re: cygserver - /usr/sbin vs /usr/bin
Date: Tue, 14 Aug 2018 21:31:00 -0000	[thread overview]
Message-ID: <147E77BD-7FF6-4026-B08B-E2BCBE000DAA@solidrocksystems.com> (raw)
In-Reply-To: <f0c86634-a16f-0c63-dcaf-6e0e6a6bba50@gmail.com>

> On Aug 14, 2018, at 3:05 PM, cyg Simple wrote:
> 
> On 8/13/2018 10:41 AM, Corinna Vinschen wrote:
>> …
>> 
>> cyglsa.dll requires an install script that would have to be change as
>> well.  In contrast, you'd have to make sure your new solution still
>> works for existing installations.  What's the gain?  Does it *hurt* to
>> have the stuff in /usr/bin like everything else?
>> 
> 
> No but then why have cygserver.exe in /usr/sbin?  Either there should be
> a separation because of required administrative rights or there
> shouldn't be at all.  Having it both ways is just confusing even if the
> confusion isn't apparent to you.

And just because it's confusing to you doesn't mean it's confusing to everyone
else. I for one have never been confused.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-08-14 20:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10 15:28 cyg Simple
2018-08-12 13:33 ` cyg Simple
2018-08-13  7:50 ` Corinna Vinschen
2018-08-13 12:50   ` cyg Simple
2018-08-13 14:42     ` Corinna Vinschen
2018-08-14 20:43       ` cyg Simple
2018-08-14 21:31         ` Vince Rice [this message]
2018-08-16  3:32           ` cyg Simple

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=147E77BD-7FF6-4026-B08B-E2BCBE000DAA@solidrocksystems.com \
    --to=vrice@solidrocksystems.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).