linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Hubbs <w.d.hubbs@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: /var on a separate partition
Date: Tue, 08 Nov 2011 23:37:12 +0000	[thread overview]
Message-ID: <20111108233712.GB19188@linux1> (raw)
In-Reply-To: <20111108183853.GA18064@linux1>

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

On Tue, Nov 08, 2011 at 11:46:10PM +0100, Kay Sievers wrote:
> On Tue, Nov 8, 2011 at 23:39, William Hubbs <w.d.hubbs@gmail.com> wrote:
> > On Tue, Nov 08, 2011 at 08:35:53PM +0100, Kay Sievers wrote:
> >> On Tue, Nov 8, 2011 at 19:38, William Hubbs <w.d.hubbs@gmail.com> wrote:
> >> > I know that having /usr on a separate file system with the latest udev
> >> > doesn't work without using an initramfs.
> >> >
> >> > Are there any other file systems that should be pre-mounted by the
> >> > initramfs, such as /var? It looks like /var has to be pre-mounted if you
> >> > have alsa installed, but I want to confirm whether folkson this list
> >> > know this.
> >>
> >> There is no need for that. Systemd can bring up the box without /var,
> >> and sort the services which need that after /var is mounted.
> >>
> >> Alsa has its own systemd service which initializes hardware at that
> >> point, in case the coldplug run did not do it already from udev.
> >
> > In that case, shouldn't we have the alsa-utils folks drop
> > /lib/udev/rules.d/90-alsa-restore.rules from their package?
> 
> Udev still takes care for hardware you connect later. Udev does the
> hotplug path, the systemd service does the initial init during bootup.
> Both are needed.
> 
> But the ACTION=="remove" rule in that file can surely be killed, not
> sure who expected saving the state of a device that is already removed
> to work. :)

I'm not sure we are talking about the same file, so I will include the
one I have for reference, this is from alsa-utils-1.0.24.2.

ACTION=="add", SUBSYSTEM=="sound", KERNEL=="controlC*", KERNELS=="card*", \
        RUN+="/usr/sbin/alsactl restore $attr{number}"

		The problem is the run+= portion. "alsactl restore" reads state
		information from /var/lib/alsa by default, so it will fail if
		/var is not mounted.

William


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

  parent reply	other threads:[~2011-11-08 23:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 18:38 /var on a separate partition William Hubbs
2011-11-08 19:35 ` Kay Sievers
2011-11-08 22:39 ` William Hubbs
2011-11-08 22:46 ` Kay Sievers
2011-11-08 23:37 ` William Hubbs [this message]
2011-11-08 23:45 ` Kay Sievers

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=20111108233712.GB19188@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 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).