From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: util-linux-2.25.2-2
Date: Tue, 24 Mar 2015 00:02:00 -0000 [thread overview]
Message-ID: <87zj73gx5x.fsf@Rainer.invalid> (raw)
In-Reply-To: <1427148223.912.37.camel@cygwin.com> (Yaakov Selkowitz's message of "Mon, 23 Mar 2015 17:03:43 -0500")
Yaakov Selkowitz writes:
> On Mon, 2015-03-23 at 22:26 +0100, Achim Gratz wrote:
>> Yaakov Selkowitz writes:
>> > This update adds /sbin/nologin and moves most of the /usr/sbin
>> > executables to /sbin where they are generally expected to be found.
>>
>> So Cygwin will grow another mount /sbin -> /usr/sbin to keep things
>> consistent? Last time I've asked Corinna said she doesn't intend to do
>> that.
>
> Probably not, the reason being it is would be quite difficult to
> implement a new mount without breaking existing setups.
Which you are doing just now, for folks that have learned to look for
these tools in /usr/sbin. There is (or at least should not be) anything
in /sbin on Cygwin, so keeping things in /usr/sbin and either symlinking
or mounting /sbin onto /usr/sbin would let you use scripts that expect
something in /sbin.
Modern Linux (with systemd) has most if not all of /sbin symlinked into
/usr/sbin (where the real action is). I would prefer if these things
are kept in /usr/sbin for Cygwin (old expectations notwithstanding).
There are few genuine reasons to put things into /sbin specifically and
none of them apply to Cygwin (since it doesn't boot itself).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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
prev parent reply other threads:[~2015-03-23 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 19:38 Yaakov Selkowitz
2015-03-23 21:27 ` Achim Gratz
2015-03-23 22:35 ` Yaakov Selkowitz
2015-03-24 0:02 ` Achim Gratz [this message]
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=87zj73gx5x.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).