[Chromebook XE303C12] Systemd doesn't boot after upgrade

[WarheadsSE]

No. It is a compile-time option.

[Razrael]

Hi psychoacoustic
You could chroot into your arm system via qemu on your laptop. Then a simple 'pacman -Suy' should work.
This will give you some hints: http://tinkering-is-fun.blogspot.ch/200 ... pc_12.html

I've done it this way and it worked

[psychoacoustic]

@WarheadsSE: Ah Ok, thanks for the info.

@Razrael: Cool info thanks!

But in the end I just grabbed an old (1G!!!) USB stick and put a new install on that. One chroot later and my SD card is back to running. I'm keeping that stick for any future unexpected breakages...

Thanks and cheers to everyone!

(...and now I'm wondering if this thing - rendering a system unbootable even in single-user mode - would even be possible with the old rc script startup, but I don't know enough about systemd to make a coherent argument either way...)

[hcs]

I just ran into this (or something suspiciously similar) again with systemd 213-9.1 => 214-2, just a word of warning. I'm ignoring systemd and libsystemd and sticking with 213-9.1 for now.

[doragasu1]

Thanks for the warning!

It looks like upgrading our Chromebooks without ignoring systemd is like playing russian roulette...

[WarheadsSE]

They removed the ability to disable xattrs ....

[hcs]

214-2.1 fixes it, thanks for the quick fix. You folks running ALARM don't get enough credit.

[WarheadsSE]

Danke