Jonathan Corbet wrote:

I'm getting more SELinux-related weirdness on my x86_64 rawhide box. I just did a reboot after an update, and init croaked with:

/sbin/init: symbol lookup error: /sbin/init: undefined symbol: selinux_getenforcemode

You need to update you libselinux rpm.

Needless to say, I didn't get the nice graphical login screen I was hoping for. Tossing an older SysVinit package onto the system made it bootable, but this episode does bring to mind a few questions:

• Why am I getting things failing with weird, missing selinux symbols?

And why is nobody else complaining about it?

You must have a partially upgraded system

• Why isn't init staticly linked? As a general rule, I like it better

when init actually works regardless of what else might be hosed on the system.

I know I have read a reason for this, but do not know it off hand.

• Any chance you could cram a couple more colons into the error message?

Yes this does need a colonoscapy.

The most pressing question for me is the "why only me?" part. Where is selinux_getenforcemode supposed to be defined? libselinux.so would seem to be a likely one, but I don't find it there...

Upgrade to the lastest libselinux.

Thanks,

jon

Jonathan Corbet Executive editor, LWN.net corbet@lwn.net