* Re: /var on a separate partition
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
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Kay Sievers @ 2011-11-08 19:35 UTC (permalink / raw)
To: linux-hotplug
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.
Kay
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: /var on a separate partition
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
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: William Hubbs @ 2011-11-08 22:39 UTC (permalink / raw)
To: linux-hotplug
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
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?
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: /var on a separate partition
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
2011-11-08 23:45 ` Kay Sievers
4 siblings, 0 replies; 6+ messages in thread
From: Kay Sievers @ 2011-11-08 22:46 UTC (permalink / raw)
To: linux-hotplug
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. :)
Kay
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: /var on a separate partition
2011-11-08 18:38 /var on a separate partition William Hubbs
` (2 preceding siblings ...)
2011-11-08 22:46 ` Kay Sievers
@ 2011-11-08 23:37 ` William Hubbs
2011-11-08 23:45 ` Kay Sievers
4 siblings, 0 replies; 6+ messages in thread
From: William Hubbs @ 2011-11-08 23:37 UTC (permalink / raw)
To: linux-hotplug
[-- 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 --]
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: /var on a separate partition
2011-11-08 18:38 /var on a separate partition William Hubbs
` (3 preceding siblings ...)
2011-11-08 23:37 ` William Hubbs
@ 2011-11-08 23:45 ` Kay Sievers
4 siblings, 0 replies; 6+ messages in thread
From: Kay Sievers @ 2011-11-08 23:45 UTC (permalink / raw)
To: linux-hotplug
On Wed, Nov 9, 2011 at 00:37, William Hubbs <w.d.hubbs@gmail.com> wrote:
> 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.
We do. The ACTION="remove" in there makes no sense.
> 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.
That does not matter. The rule is meant to run and will work fine in
hotplug cases. During bootup it can gracefully fail without causing
any problems, the systemd service, started later, will take care that
/var is there, when the formerly failed device inits, are applied.
Kay
^ permalink raw reply [flat|nested] 6+ messages in thread