Bug#763197: closed by md at Linux.IT (Marco d'Itri) (Re: Bug#763197: systemd: upgrade to systemd 215 broke boot with personal kernel)

Josh Triplett josh at joshtriplett.org
Mon Oct 6 00:02:58 BST 2014


On Mon, 06 Oct 2014 00:11:50 +0200 Michael Biebl <biebl at debian.org> wrote:
> Am 05.10.2014 um 23:38 schrieb Samuel Thibault:
> > On Sep 28, Samuel Thibault <sthibault at debian.org> wrote:
> >>
> >>> After upgrading to systemd 215 to report information for 760916, I can't
> >>> boot with my own 3.16 kernel, I can only boot with the Debian-provided 3.16
> >> # CONFIG_FHANDLE is not set
> >>
> >> /usr/share/doc/systemd/README.gz
> > 
> > Could those requirements be simply checked and warned about by systemd?
> 
> Would probably be a good idea. Do you know a reliable way to test that
> for a running kernel (and the other requirements listed in README.gz)?

config="/boot/config-$(uname -r)"
if [ -r "$config" ]; then
    . "$config"
elif [ -r /proc/config.gz ]; then
    eval "$(zcat /proc/config.gz)"
else
    # Complain about failing to find the config for the running kernel.
    echo FIXME
fi
for required_config in DEVTMPFS CGROUPS OTHER_THINGS; do
    if [ "$(eval echo \$CONFIG_$required_config)" != y ]; then
        missing_config="${missing_config:+$missing_config }CONFIG_$required_config"
    fi
done
if [ -n "$missing_config" ]; then
    # This should be a debconf error
    echo "Missing kernel configuration options required to run systemd:"
    echo "$missing_config"
    exit 1
fi




More information about the Pkg-systemd-maintainers mailing list