All of lore.kernel.org
 help / color / mirror / Atom feed
From: Norbert Lange <nolange79@gmail.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>,
	"Yann E. MORIN" <yann.morin.1998@free.fr>,
	buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/systemd: Allow extra config options
Date: Sat, 8 Jan 2022 22:31:32 +0100	[thread overview]
Message-ID: <CADYdroOofT_jFTyAFuTd+iZGbmYwFwofJ8aHYnuz4TAbk4C80A@mail.gmail.com> (raw)
In-Reply-To: <CADvTj4p=60BwS0f6+UZABNYRw6BYph+qkTU7L9Gv+=LOJewsMQ@mail.gmail.com>

Am Sa., 8. Jan. 2022 um 20:04 Uhr schrieb James Hilliard
<james.hilliard1@gmail.com>:
>
> On Thu, Nov 26, 2020 at 8:28 AM Norbert Lange <nolange79@gmail.com> wrote:
> >
> > Systemd has very many options, adding a way for the user
> > to set custom options can help customizations
> > without changing buildroot files.
>
> I'm not sure this is a good idea, if a configuration option needs
> customizability it
> probably needs a specific kconfig option. Systemd config options tend to require
> dependency selection and special handling so this seems likely to cause
> spurious errors due to improper usage. Seems to be a pretty big footgun IMO.

Sure, you are aware that many of my buildroot patches are stuck in limbo
since early 2020?
Just doesnt seem feasible to timely fix everything and version bumps often leave
more untapped options. Some part of the necessity would be just being pragmatic.

One example would be using the unified cgroups hierarchy
(-Ddefault-hierarchy=unified), hybrid is pretty much deprecated,
and some systemd features that buildroot allows to enable (OOMD for example)
wont work without it.

>
> What systemd configure option would you want to be using that isn't
> currently able to be enabled?

FYI those are the ones I currently use:

-Ddefault-hierarchy=unified \
-Dutmp=false \
-Ddefault-dnssec=no \
-Didn=false \
-Denvironment-d=false \
-Dxdg-autostart=false \
-Ddns-over-tls=false \
-Ddefault-llmnr=no \
-Ddns-over-tls=false \
-Ddefault-mdns=no \
-Dlz4=false

Norbert
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-01-08 21:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 15:28 [Buildroot] [PATCH 1/1] package/systemd: Allow extra config options Norbert Lange
2022-01-08 11:04 ` Romain Naour
2022-01-08 14:23   ` Arnout Vandecappelle
2022-01-08 14:36   ` Norbert Lange
2022-01-08 19:04 ` James Hilliard
2022-01-08 21:31   ` Norbert Lange [this message]
2022-01-08 22:37     ` Arnout Vandecappelle
2022-01-09 22:40     ` James Hilliard
2022-01-09 22:52       ` Norbert Lange
2022-01-10  7:26         ` Arnout Vandecappelle
2022-01-10  8:28           ` Norbert Lange

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=CADYdroOofT_jFTyAFuTd+iZGbmYwFwofJ8aHYnuz4TAbk4C80A@mail.gmail.com \
    --to=nolange79@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=maxime.hadjinlian@gmail.com \
    --cc=yann.morin.1998@free.fr \
    /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.