[elbe-devel] installing klogd/sysklogd
John Ogness
jogness at linutronix.de
Sat Oct 26 09:48:35 CEST 2013
Hi,
If you want to install klogd/sysklogd (as a replacement for rsyslog),
you cannot do this by adding klogd to the pkg-list. The reason is
because rsyslog conflicts with klogd/sysklogd and is already part of the
base installation. When elbe resolves this conflict it decides to keep
the already installed rsyslog instead of installing klogd/sysklogd.
You can install klogd/sysklogd using finetuning. Here are the finetuning
entries that are required to do that:
<finetuning>
<command>apt-get -y install klogd</command>
<command>mount -t proc none proc</command>
<command>chroot . apt-get -y install klogd</command
<command>chroot . dpkg --purge rsyslog</command>
<command>chroot . /etc/init.d/klogd stop</command>
<command>chroot . /etc/init.d/sysklogd stop</command>
<command>umount proc</command>
</finetuning>
Here is the explanation to the above finetuning commands.
apt-get -y install klogd
First we install klogd to the host image. (sysklogd is also installed
because it is a dependency.) We need to install it to the host image
because the install.iso generated later uses the dpkg repository from
the host image and we want klogd/sysklogd to be part of install.iso.
mount -t proc none proc
Next we mount /proc for the target. We need to do this because klogd
uses /proc and klogd/sysklogd are automatically started upon
installation.
chroot . apt-get -y install klogd
chroot . dpkg --purge rsyslog
Next we install klogd (and sysklogd as a dependency) and cleanup the
replaced rsyslog. This is done in the target root directory using
chroot.
chroot . /etc/init.d/klogd stop
chroot . /etc/init.d/sysklogd stop
Next we stop the klogd/sysklogd services that were started upon
installation. This is necessary because klogd uses /proc. We need to
unmount /proc later so klogd must be stopped first. (Note: we are
stopping the services within the target chroot, not the services running
on the host image)
umount proc
Last we unmount /proc for the target.
Some possible suggestions for changes to elbe:
1. Take the apt-repositories from the target for install.iso instead of
the apt-repositories from the host.
2. Automatically mount /target/proc for the finetuning phase.
I do not mind working with elbe the way it is now. Using finetuning it
is possible to install klogd/sysklogd and have them show up in
install.iso. My suggestions may have other unwanted side-effects in
elbe. I will leave it as an excercise for the elbe designers to decide
if the suggestions are more useful than harmful.
John Ogness
More information about the elbe-devel
mailing list