From: "John Stoffel" <john@stoffel.org>
To: Wols Lists <antlists@youngman.org.uk>
Cc: Jes Sorensen <jes.sorensen@gmail.com>, NeilBrown <neilb@suse.com>,
John Stoffel <john@stoffel.org>,
Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: [mdadm PATCH] mdopen: call "modprobe md_mod" if it might be needed.
Date: Tue, 26 Sep 2017 16:55:15 -0400 [thread overview]
Message-ID: <22986.48819.81116.815726@quad.stoffel.home> (raw)
In-Reply-To: <59CAA6AE.9060908@youngman.org.uk>
>>>>> "Wols" == Wols Lists <antlists@youngman.org.uk> writes:
Wols> On 26/09/17 16:11, Jes Sorensen wrote:
>> I completely agree, I also think we shouldn't hardcode imposed layouts
>> unless there are very strong reasons for it. Someone may want to put
>> this into an initramfs or somewhere else and want to put it in a
>> different location.
Wols> Plus isn't /sbin deprecated?
LOL!
Wols> Iirc (very debatable :-) the end goal of the FHS is to have a
Wols> read-only / with all executables in /bin. Okay it's going to
Wols> take a looonngg time to get there, but if I'm right hard-coding
Wols> already-deprecated standards isn't the best move.
Heh heh.
Wols> (Again, iirc :-) sbin stood for *static* binaries needed for
Wols> system recovery, so its original purpose has long been abused
Wols> ... :-)
I agree. I more think of it as 'system binaries' myself. Stuff
that's needed by the barebones system to just even run.
But others haven't asuaged my concerns, so I think we're ok.
John
next prev parent reply other threads:[~2017-09-26 20:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 5:52 [mdadm PATCH] mdopen: call "modprobe md_mod" if it might be needed NeilBrown
2017-09-25 15:26 ` John Stoffel
2017-09-25 23:50 ` NeilBrown
2017-09-26 15:11 ` Jes Sorensen
2017-09-26 19:12 ` Wols Lists
2017-09-26 20:55 ` John Stoffel [this message]
2017-09-27 21:30 ` Jes Sorensen
[not found] ` <cba5f77f-d6de-7a6b-35b0-70b7c56eb3f7@suse.com>
2017-10-10 20:16 ` NeilBrown
2017-10-11 7:39 ` Zhilong Liu
2017-10-12 0:06 ` NeilBrown
2017-10-12 3:55 ` Zhilong Liu
2017-10-12 8:48 ` NeilBrown
2017-10-13 9:16 ` Zhilong Liu
2017-10-15 22:41 ` NeilBrown
2017-10-12 9:55 ` Wols Lists
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=22986.48819.81116.815726@quad.stoffel.home \
--to=john@stoffel.org \
--cc=antlists@youngman.org.uk \
--cc=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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 NNTP newsgroup(s).