On 02/02/2016 08:05 AM, Simon Hobson wrote:
> Exposing my ignorance here, what would need to write to the EFI stuff ? That
> article quotes someone as saying mounting it read-only would break some
> userspace stuff - so what would it break and why does it need to write there ?
> Not having actual
Hi all,
an occasional rant from you humble almost-lurker.
From: Rainer Weikusat
In all seriousness, what is the guy supposed to do if some
less-than-informed person accidentally deletes something he'd better
Let's not lose the point: while stupidly issuing rm -rf / was possibly
intention
On 02/02/16 15:51, Steve Litt wrote:
>
> Poettering's final post reminds me so much of Don Armstrong on
> Debian-User. "My way or the highway, no further discussion!"
>
LOL.. me too :-)
signature.asc
Description: OpenPGP digital signature
___
D
Edward Bartolo writes:
> This is enough evidence to be very vigilant where an OS uses systemd.
> Breaking hardware is a very serious issue, will not fix is not acceptable
> as a responsible reply.
In all seriousness, what is the guy supposed to do if some
less-than-informed person accidentally de
On Tue, 2 Feb 2016 10:49:10 +0100
Jaromil wrote:
> On Tue, 02 Feb 2016, Wim wrote:
>
> >[2]https://github.com/systemd/systemd/issues/2402
> >Well, you've probably guessed the answer - Won't fix.
>
> meanwhile, on the background, the usual bullying goes on among the
> systemd hooligans
This is enough evidence to be very vigilant where an OS uses systemd.
Breaking hardware is a very serious issue, will not fix is not acceptable
as a responsible reply.
On Feb 2, 2016 2:25 PM, "Rainer Weikusat"
wrote:
> Jaromil writes:
> > On Tue, 02 Feb 2016, Wim wrote:
> >
> >>[2]https://gi
Jaromil writes:
> On Tue, 02 Feb 2016, Wim wrote:
>
>>[2]https://github.com/systemd/systemd/issues/2402
>>Well, you've probably guessed the answer - Won't fix.
>
> meanwhile, on the background, the usual bullying goes on among the
> systemd hooligans, sarcastically liquidating the concern
Jaromil wrote:
> meanwhile, on the background, the usual bullying goes on among the
> systemd hooligans, sarcastically liquidating the concern with some
> cynical remarks, as if it would be a deserved punition for users
> caught into a bricked laptop rather than an erased filesystem:
>
> http://
On Tue, 02 Feb 2016, Wim wrote:
>[2]https://github.com/systemd/systemd/issues/2402
>Well, you've probably guessed the answer - Won't fix.
meanwhile, on the background, the usual bullying goes on among the
systemd hooligans, sarcastically liquidating the concern with some
cynical remarks,
On 02/01/2016 08:59 PM, Clarke Sideroad wrote:
> On 02/01/2016 06:12 PM, Wim wrote:
>> Hi all,
>>
>> It seems you can delete EFI vars if you're not careful. Someone found
>> that executing "rm -rf --no-preserve-root /" also deleted EFI vars,
>> turning his MSI Notebook into a brick.
>>
>> It also
On 02/01/2016 06:12 PM, Wim wrote:
> Hi all,
>
> It seems you can delete EFI vars if you're not careful. Someone found
> that executing "rm -rf --no-preserve-root /" also deleted EFI vars,
> turning his MSI Notebook into a brick.
>
> It also seems mounting these is hardcoded into systemd:
>
> h
Hi all,
It seems you can delete EFI vars if you're not careful. Someone found that
executing "rm -rf --no-preserve-root /" also deleted EFI vars, turning his MSI
Notebook into a brick.
It also seems mounting these is hardcoded into systemd:
https://bbs.archlinux.org/viewtopic.php?id=207549
efib
12 matches
Mail list logo
