From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Dave Hansen <dave@sr71.net>, Ilia Mirkin <imirkin@alum.mit.edu>
Cc: dave.hansen@linux.intel.com, john@johnmccutchan.com,
rlove@rlove.org, eparis@parisplace.org, viro@zeniv.linux.org.uk,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fs: inotify: systemd needs it so make it depend on CONFIG_EMBEDDED
Date: Mon, 22 Jun 2015 08:20:58 -0400 [thread overview]
Message-ID: <5587FDAA.4040301@gmail.com> (raw)
In-Reply-To: <55848E3C.9010206@sr71.net>
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
On 2015-06-19 17:48, Dave Hansen wrote:
> On 06/19/2015 11:18 AM, Ilia Mirkin wrote:
>> Is systemd depending on something really reason enough to make it
>> depend on EMBEDDED? For example all the cgroups stuff is not only not
>> dependent on embedded, but also off by default, and I'm sure there are
>> a boatload of other dependencies which any normal system has no
>> business worrying about but that are required by systemd.
>
> Does the lack of cgroups keep a (normal) system from booting, though?
Define 'normal'. Just because userspace software depends on something
doesn't mean we should force that on everyone, even if disabling it
could make some systems fail to boot (that is an inherent risk in
building your own kernel). dnotify (inotify's predecessor) is an
excellent example of this: nfs-utils depends on it, and that not working
can definitely make a system fail to boot, yet it is not hidden behind
some other config option, but defaults to being on.
Making inotify default to on (like dnotify) is a better solution to
this, anyone who is going around turning off options that default to on
in kconfig should be prepared to deal with a system that doesn't boot
anyway, and EMBEDDED is intended (AFAICT) for saving space on systems
with limited memory, not hiding userspace dependencies that have other
legitimate reasons to be disabled.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]
prev parent reply other threads:[~2015-06-22 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 18:07 [PATCH] fs: inotify: systemd needs it so make it depend on CONFIG_EMBEDDED Dave Hansen
2015-06-19 18:18 ` Ilia Mirkin
2015-06-19 18:54 ` Austin S Hemmelgarn
2015-06-19 21:48 ` Dave Hansen
2015-06-22 12:20 ` Austin S Hemmelgarn [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=5587FDAA.4040301@gmail.com \
--to=ahferroin7@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@sr71.net \
--cc=eparis@parisplace.org \
--cc=imirkin@alum.mit.edu \
--cc=john@johnmccutchan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlove@rlove.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.