Your message dated Mon, 02 Jun 2014 23:58:02 +0200
with message-id <538cf36a.4020...@debian.org>
and subject line Re: Bug#750360: systemd-sysv: /sbin/init should be a relative
symlink
has caused the Debian Bug report #750360,
regarding systemd-sysv: /sbin/init should be a relative symlink
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.)
--
750360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-sysv
Version: 204-10
Severity: important
/sbin/init is installed as a symbolic link to the absolute path
//lib/systemd/systemd.
This breaks in environments where the root filesystem is not mounted at /,
for example, when inspecting a chroot from outside or, which is
worse, when being first mounted from initramfs.
I just spent quite some time figuring out why the initramfs on a PXE
boot client behaved oddly, and it turned out that the nfs root mount
script in initramfs has a logic that repeatedly checks for the existence
of /root/sbin/init, with the soon-to-be rootfs being mounted at /root.
With the absolute symlink of systemd-sysv in place, /sbin/init points
outside the /root directory holding the rootfs, and thus renders the
link target non-existent.
Just updating the /sbin/init symlink to point to a relative path fixes
the issue without side effects:
/sbin/init -> ../lib/systemd/systemd
Please fix this in the script so systemd can work in all environments
where sysv-init worked!
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd-sysv depends on:
ii systemd 204-10
systemd-sysv recommends no packages.
systemd-sysv suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 02.06.2014 22:29, schrieb Dominik George:
> Package: systemd-sysv
> Version: 204-10
> Severity: important
>
> /sbin/init is installed as a symbolic link to the absolute path
> //lib/systemd/systemd.
This symlink is created via debian/systemd-sysv.links by dh_link.
I don't know the reasons why dh_links creates relative symlinks, but
you'll need to talk to the debhelper maintainers if you want to see this
behaviour changed. I assume there are reasons for that, but you'll need
to talk to the debhelper maintainers.
This is nothing which can be fixed in the systemd package, thus closing
the bug report.
Please feel free to report this issue against the debhelper package,
which ships dh_link.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
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
