me no rtfm (prefers girstickenpoken)

[Dennis Veatch]

On Sunday, May 01, 2011 11:43:05 PM Auke Kok wrote:
> On 05/01/2011 04:27 AM, Dennis Veatch wrote:
> > I seriously doubt you have systemd properly installed and afaict its
> > --with- distro=other means we need to do some massaging of Lunar to use
> > most of it.
> > 
> > As I understand it, to be certain you are actually using systemd the
> > kernel needs `init=/bin/systemd`. When I have tried that on two boxes
> > the first errors you see after "Welcome to Linux!" are;
> > 
> > /sbin/modprobe failed with error code 1
> > 
> > Cannot open /etc/machine-id: No such file or directory
> > 
> > /etc/mtab is not a symlink; should point to /proc/self/mounts
> > 
> > /lib/systemd/system/udev.service Invalid executable path, ignoring
> > 
> > udev.service lacks ExecStart setting. Refusing
> > 
> > /bin/loadkeys failed with error 1<--- kbd module instalss in /usr/bin
> > /bin/setfont failed with error 1<--- kbd module installs in /usr/bin
> > 
> > 
> > 
> > So afaict Lunar is in no shape for systemd to be a drop-in.
> 
> it's nowhere near done, correct
> 
> most of the things above are not a real problem, but in the current
> setup, will give problems down the road one way or another.
> 
> the /etc/mtab is one of the bigger issues. /etc/fstab contains lots of
> vfs's in lunar too which is an issue. it all adds up.
> 
> Auke
> 
> _______________________________________________

No agrument there. Lunar and/or systemd will need adjustments. Just for grins 
I did try it on another box with one drive and two partitions; swap and /. 
That setup was ok so far as mount goes. There was still the items above that 
happened issuing init=/bin/systemd.