On 5/3/19 9:09 AM, DJ Lucas via blfs-dev wrote:
On May 1, 2019 5:30:13 PM CDT, Tim Tassonis via blfs-dev
<blfs-dev@lists.linuxfromscratch.org> wrote:
On 5/1/19 10:52 PM, Pierre Labastie via blfs-dev wrote:
Well, I didn't know that systemd could use sysv bootscripts... So
my question
is irrelevant. OTOH, this package needs LSB conform bootscripts,
which ours in
the SysV book are not...
Did they change something in LSB that made them incompatible? That was the
entire point of the rewrite - well that and fixing some stuff in early rc
(early boot logging, interactive boot, etc.).
and nm has:
# Provides: networkmanager
# Required-Start: dbus udev
# Required-Stop: dbus
# Default-Start: 3 4 5
# Default-Stop: 0 1 6
Runlevel 2 is multiuser without networking, nm should stop in rl2, and
$remote_fs does not make sense here, but to be compliant, the install prefix
for nm should be /, not /usr/ -- remote /usr is an almost impossible goal
nowadays, but I believe this is still not FHS compliant for that reason, unless
they've relaxed that requirement as well with the merged /usr stuff.
after my edits...
It originally has:
# Provides: networkmanager
# Required-Start: $remote_fs dbus udev
# Required-Stop: $remote_fs dbus udev
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
In my scripts, I took out all level 2 references and all $remote_fs
stuff, as I don't have nfs installed on all systems and $remote_fs
should really not be a hard dependency for any package.
No, never required, but it should almost always be a soft dep where BLFS is
concerned (see below).
This is not the fault of init-tools, but no service should rely per
default on a running nfs-client service. No idea how that got in.
$remote_fs != nfs
nfs provides nfs, netfs provides $remote_fs, that's how it got in, and is
correct for everything that is not pre network available in BLFS.
Should-start: $remote_fs
should appear in *every* script that starts a daemon that is installed in /usr
to allow for the possibility of a shared /usr.
--DJ
Ok, I see now where I got it wrong: the netfs bootscript is actually not
strictly a part of nfs-utils, but is mentioned also generally in
"Configuring for Network Filesystems". This however comes after
nfs-utils in the book, so the init script ended up in my nfs-utils
install and if I choose not to install nfs-utils on a machine, the netfs
init script was not installed and caused all init scripts requiring
$remote_fs to complain about it.
So, as you say, the scripts should be adjusted to move every occurrence
of $remote_fs from Required-Start: to Should-Start: ?
Bye
Tim
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
