Laurent: > On 2015-06-20 11:56, k...@aspodata.se wrote: > > # grep /boot/init.sysvinit /var/log/all.log > > Jun 20 11:33:47 opal kernel: [ 0.000000] Kernel command line: > > BOOT_IMAGE=312 ro root=901 noinitrd init=/boot/init.sysvinit > > Jun 20 11:33:47 opal kernel: [ 2.332734] Failed to execute > > /boot/init.sysvinit. Attempting defaults... > > # ls -l /boot/init.sysvinit > > lrwxrwxrwx 1 root root 12 Jun 20 11:30 /boot/init.sysvinit -> ../sbin/init > > Was /boot on the same filesystem as / ? > My machines (kernels 3.10.62 and 3.19.1) boot on /etc/init which > is a symbolic link, and it's never been a problem.
Well spotted, it seems to work perfectly well: # cat /proc/cmdline BOOT_IMAGE=312 ro root=901 noinitrd # ls -l /sbin/init* /etc/alternatives/init lrwxrwxrwx 1 root root 24 Jun 20 13:06 /etc/alternatives/init -> ../../sbin/init.sysvinit lrwxrwxrwx 1 root root 24 Jun 20 13:06 /sbin/init -> ../etc/alternatives/init -rwxr-xr-x 1 root root 35216 Jul 18 2013 /sbin/init.sysvinit # Regards, /Karl Hammar ----------------------------------------------------------------------- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
