[systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

[Reindl Harald]

Am 29.06.2015 um 17:01 schrieb jon:
> On Mon, 2015-06-29 at 14:21 +0000, Jóhann B. Guðmundsson wrote:
>>
>> On 06/29/2015 02:08 PM, jon wrote:
>>> https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system
>>>
>>> I just installed debian 8.1, on the whole my reaction is mixed, one
>>> thing however really pisses me off more than any other
>>>
>>> "5.6.1. Stricter handling of failing mounts during boot under systemd"
>>>
>>> This is not "Stricter" it is a change in default behaviour.
>>>
>>> This change is a shit idea, who do I shout at to get the behaviour
>>> modified to back to sensible ?
>>>
>>
>> The systemd community only recommends what downstream consumers of it
>> should do but does not dictate or othewise decided anything how those
>> consumers eventually decide to implement systemd so if you dont like how
>> systemd is implemented in Debian you should voice your concerns with the
>> Debian community.
> Ok
>
> Who writes/maintains the code that parses "nofail" in /etc/fstab ?
> Who writes/maintains the typical system boot code (whatever has replaced
> rc.sysinit) ?
>
> I suspect the answer to both is the systemd maintainers, in which case
> is this not the correct place to bitch about it?

i don't get what is there to "bitch about" at all

you have a mountpoint in /etc/fstab and don't care if it don't get 
mounted at boot and instead data get written into the folder instead the 
correct filesystem?

normally that is not what somebody expects and if that is the desired 
behavior for you just say that to your operating system and add "nofail"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20150629/3e439a68/attachment.sig>