Bug#785525: systemd fails to boot if non-essential block device is missing

[Michael Biebl]

Hello Thibaut,

Am 17.05.2015 um 15:32 schrieb Thibaut Varène:
> 
> On 17 mai 2015, at 14:59, Thibaut Varène <varenet at debian.org> wrote:
> 
>>
>> On 17 mai 2015, at 14:57, Martin Pitt <mpitt at debian.org> wrote:
>>>
>>> Thibaut VARENE [2015-05-17 14:41 +0200]:
>>>> Just upgraded my system from wheezy to jessie. Boot stopped after initial reboot, with prompt to enter root password. After looking at the logs, it seems that systemd choked on this line of my fstab:
>>>>
>>>> UUID="8633-12F1"	/media/WDX360	vfat	user,auto,utf8=no,iocharset=iso8859-1	0	2

..

> While I'm there, your argument about what should and shouldn't be considered "essential" seems rather bogus considering all of that is made pretty clear by the FHS:
> http://www.pathname.com/fhs/pub/fhs-2.3.html#REQUIREMENTS
> 
> This also states that /media is for removable media, so a hard fail on anything below that mount point seems equally wrong.

We discussed this further with the pkg-systemd team. I think the idea to
treat mount points under /media as nofail even if not explicitly
configured, has some merit, even though it's not specified like this in
the FHS.
We do not want to change the upstream behaviour though, so I'll try to
start a discussion on the upstream mailing list and see what they think.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20150608/77525b10/attachment-0001.sig>