Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 10/10] package/mdevd: bump version to 0.1.1.0
Date: Tue, 1 Oct 2019 08:50:20 +0200	[thread overview]
Message-ID: <20191001085020.43b52a31@windsurf.home> (raw)
In-Reply-To: <20190930231441.GB11114@itchy>

On Tue, 1 Oct 2019 01:14:41 +0200
Eric Le Bihan <eric.le.bihan.dev@free.fr> wrote:

> I did not know about the daemon mode of mdev, but mdevd was created to
> overcome the mdev forking issue [1] and predates the daemon option [2].
> 
> So in the end, they provide the same features, with mdevd also complying
> with s6 notification mechanism [3], making it more tightly coupled with
> this init system.
> 
> Given that there is no option in menuconfig to use a s6-based init
> system [4], I see no reason to add a "devtmpfs+mdevd" option ATM.

But then there is nothing that prevents them from enabling
devtmpfs+eudev as the /dev management system, and separately enable
mdevd. That wouldn't work very well.

On the other hand, if a user enables both openssh and dropbear, in
their default configuration, both will try to listen on TCP port 22,
which won't work as well. So perhaps we can live with having mdevd as a
standalone package, with no specific handling in the /dev management
choice. I'm just a bit worried about users who will enable this mdevd
package, while they are looking for Busybox mdev.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-10-01  6:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-29 17:10 [Buildroot] [PATCH 00/10] Bump skarnet packages to 2019.09 release Eric Le Bihan
2019-09-29 17:10 ` [Buildroot] [PATCH 01/10] package/skalibs: bump version to 2.9.0.0 Eric Le Bihan
2019-09-29 17:10 ` [Buildroot] [PATCH 02/10] package/execline: bump version to 2.5.2.0 Eric Le Bihan
2019-09-29 17:10 ` [Buildroot] [PATCH 03/10] package/s6-portable-utils: bump version to 2.2.2.0 Eric Le Bihan
2019-09-29 17:10 ` [Buildroot] [PATCH 04/10] package/s6-linux-utils: bump version to 2.5.1.0 Eric Le Bihan
2019-09-29 17:10 ` [Buildroot] [PATCH 05/10] package/s6-dns: bump version to 2.3.1.0 Eric Le Bihan
2019-09-29 17:10 ` [Buildroot] [PATCH 06/10] package/s6-networking: " Eric Le Bihan
2019-09-29 17:10 ` [Buildroot] [PATCH 07/10] package/s6: bump version to 2.9.0.0 Eric Le Bihan
2019-09-29 17:10 ` [Buildroot] [PATCH 08/10] package/s6-rc: bump version to 0.5.1.0 Eric Le Bihan
2019-09-29 17:10 ` [Buildroot] [PATCH 09/10] package/s6-linux-init: bump version to 1.0.3.0 Eric Le Bihan
2019-09-29 17:10 ` [Buildroot] [PATCH 10/10] package/mdevd: bump version to 0.1.1.0 Eric Le Bihan
2019-09-30 20:57   ` Thomas Petazzoni
2019-09-30 21:25     ` Peter Korsgaard
2019-09-30 23:14       ` Eric Le Bihan
2019-10-01  6:50         ` Thomas Petazzoni [this message]
2019-10-01  8:35           ` Arnout Vandecappelle
2019-10-02 19:25             ` Yann E. MORIN
2019-10-06 15:43               ` Eric Le Bihan
2019-10-06 15:33             ` Eric Le Bihan
2019-10-27 12:02   ` Arnout Vandecappelle
2019-09-30 20:56 ` [Buildroot] [PATCH 00/10] Bump skarnet packages to 2019.09 release Thomas Petazzoni
2019-09-30 22:52   ` Eric Le Bihan

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=20191001085020.43b52a31@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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