Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

eric2.valette at orange.com eric2.valette at orange.com
Tue Jun 16 12:46:35 BST 2015


On 06/16/2015 01:30 PM, Michael Biebl wrote:
> Am 16.06.2015 um 13:18 schrieb eric2.valette at orange.com:
>> On 06/16/2015 11:58 AM, Michael Biebl wrote:
>>> My suggestion would be, to fix your setup to either use an initramfs
>>> like initramfs-tools or dracut, which mounts your /usr partition, or
>>> use no separate /usr partition at all. There is just to much stuff
>>> that is (silently) broken by this.
>> I just have about 20 or even more systems installed this way for years,
>> so its not about fixing one PC, its about fixing more than 20s. Libs
>> that are needed for system to boot should not be in usr even if this has
>> been pseudo obsoleted by initrd usage or the / and /usr should be merged
>> mantra. But having initrd, to just mount /usr (no driver or firmware
>> needed) and do a pivoroot because systemd is that way, makes me cry.
> And it makes me cry, that we are doing the pointless work of moving
> libraries around without any real gain.
I can understand that, that is the backward compatibility problem in 
general exacerbated by putting way too much functional stuff in systemd 
binary...

And BTW, moving libseccomp libraries to /lib does indeed fix the 
problem. Can't you add a test at build time that checks that systemd 
does not depend on /usr/lib libraries? (ldd systemd | grep /usr/lib => 
automatically detect possible breakage before they really happen).

-- eric


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.




More information about the Pkg-systemd-maintainers mailing list