Re: unable to mount removable media with xfce4 version 4.10.1
On Mon, Jun 9, 2014 at 10:01 AM, Reco <recoverym4n@gmail.com> wrote:
> On Mon, Jun 09, 2014 at 09:01:24AM -0400, Tom H wrote:
>>> Allow me to remind you this story:
>>>
>>> http://lkml.org/lkml/2012/10/3/484
>>>
>>> The whole mess started once udev (systemd) upstream took the liberty to
>>> rewrite udev's firmware loader, and blamed kernel for the resulting
>>> breakage. And what was the reason of rewriting said firmware loader?
>>> Some part of systemd design.
>>
>> AIUI it was a good change for udev because boot was previously being
>> delayed while waiting for userspace to load firwmware.
>
> Or, it was the change for the sake of change. YMMV.
>
>> Given the hate generally directed at the two main systemd
>> developers, submitting a kernel patch like the one that was finally
>> written and merged would've been, at the very least, good PR. But some
>> people, like Lennart, Kay, and Mark Shuttleworth, seem to be incapable
>> of pre-smoothing ruffled feathers.
>
> Wait, wait, wait. It was 2012, back then systemd was not the one and
> only pid=1 everyone and their dog used. 'Hate' directed at Lennart - the
> guy brought it upon himself with PulseAudio. But 'Hate' directed at Kay
> - the relatively unknown udev maintainer? That seems unlikely.
>
>> So it was more of a storm in a teacup than anything else. It just gave
>> and gives people who dislike systemd more ammunition for sniping.
>
> No, it was a real problem, giving that said breakage added minutes to
> the boot time of poor Fedora users. Still, the problem resolved to
> everyone's satisfaction - kernel started loading firmware without
> userspace helpers, udev deprectated firmware loading - everyone's happy.
>
> But that's not the point. The point of this story is - udev and systemd
> share one upstream, every change made in udev is made because systemd
> upstream wants udev to behave systemd special way.
>
> To make myself clear I'd like to add that I have nothing against
> systemd.
I'd forgotten that when it comes to systemd, you argue for the sake of
argument rather than have an open mind.
I shouldn't have wasted any time in posting...
Reply to: