Your message dated Thu, 22 Jun 2017 15:39:06 +0200
with message-id <65f9a020-b923-e0cc-c99c-caf4484d7...@debian.org>
and subject line Re: Bug#865536: systemd-sysv: Causes kernel panic if /usr 
isn't mounted due to liblz4.so being in /usr/lib
has caused the Debian Bug report #865536,
regarding systemd-sysv: Causes kernel panic if /usr isn't mounted due to 
liblz4.so being in /usr/lib
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
865536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-sysv
Version: 232-25
Severity: important

After the upgrade to stretch, my kernel paniced on boot.  I eventually
tracked the problem down to /usr not yet being mounted, and /sbin/init
needing liblz4.so which was in /usr.

The init system should not need anything that is typically in /usr or
/var, because those are often mounted by the init system itself.


-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-sysv depends on:
ii  systemd  232-25

systemd-sysv recommends no packages.

systemd-sysv suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi,

Am 22.06.2017 um 14:56 schrieb John Goerzen:
> After the upgrade to stretch, my kernel paniced on boot.  I eventually
> tracked the problem down to /usr not yet being mounted, and /sbin/init
> needing liblz4.so which was in /usr.

This was documented in the release notes, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830829

Using a separate /usr is fine, but then you'll need an initramfs which
mounts /usr (initramfs-tools and dracut do that).

If this did not happen in your case, please file a bug report against
either dracut or initramfs-tools.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Reply via email to