All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Hubbs <w.d.hubbs@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Allow disabling the build of all of systemd, leaving just udev
Date: Mon, 04 Jun 2012 01:50:30 +0000	[thread overview]
Message-ID: <20120604015030.GA14215@linux1> (raw)
In-Reply-To: <4FC9B938.6020608@kadzban.is-a-geek.net>

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

On Sun, Jun 03, 2012 at 03:00:27PM -0700, Bryan Kadzban wrote:
> > One more thing though, thinking about it, is that we will need the
> > systemd-tmpfiles tool because udev is not going to support the
> > /lib/udev/devices directory any longer for creating custom devices, so
> > you might want to still build and install all of the parts of that for a
> > standalone udev build if doing so doesn't bring in more dependencies.
> 
> I'd rather not replace "cp -a /lib/udev/devices/* /dev" in a boot script
> with a binary that nothing else uses, plus its configuration (which
> doesn't use nodes in /lib/udev/devices like what has been the udev ABI
> for *years*, but instead uses a list of device descriptions), plus any
> systemd-level libraries it may or may not need in the future.

Actually other things could use it because of /tmp and /run and
creating/removing files/directories there on bootup.

> If a system is already running systemd, then systemd-tmpfiles may or may
> not be the best place to do this (the ABI change is a problem for those
> systems, unless I'm missing something in the *tmpfiles* manpages). But
> if systemd is not running, then sticking to the previous ABI explicitly
> is the right way to go I think.

Unless you don't have a previous abi. Gentoo relies on udev copying
things from /lib/udev/devices, which is gone with this version of udev,
so we need the new abi.

So, how about an extra switch --enable-tmpfiles-d that will toggle on or
off whether that is built on a standalone udev build?

William


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-06-04  1:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-02  6:56 [PATCH] Allow disabling the build of all of systemd, leaving just udev Bryan Kadzban
2012-06-02 20:49 ` William Hubbs
2012-06-03 16:55 ` Bryan Kadzban
2012-06-03 21:21 ` Bryan Kadzban
2012-06-03 21:22 ` William Hubbs
2012-06-03 22:00 ` Bryan Kadzban
2012-06-04  1:50 ` William Hubbs [this message]
2012-06-04  2:13 ` Bryan Kadzban
2012-06-04 18:51 ` William Hubbs
2012-06-05  3:10 ` Bryan Kadzban
2012-06-05 17:56 ` William Hubbs
2012-06-06  3:45 ` Bryan Kadzban
2012-06-06  4:23 ` Bruce Dubbs
2012-06-06 12:38 ` Dan Nicholson
2012-06-06 16:52 ` William Hubbs
2012-06-06 17:15 ` William Hubbs
2012-06-06 18:51 ` Bruce Dubbs
2012-06-06 22:53 ` William Hubbs
2012-06-07 13:34 ` Dan Nicholson

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=20120604015030.GA14215@linux1 \
    --to=w.d.hubbs@gmail.com \
    --cc=linux-hotplug@vger.kernel.org \
    /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.