sysvinit problem

[Terry Chan]

Although sysvinit is part of the moonbase, and as you have found
you can not really lin sysvinit while you are booted from the
same hard drive.  Since "init" is the parent of all processes
you can't replace it while "init" is running.  So you really have
to boot your lunar system from a Lunar boot/rescue ISO, mount the
hard drive, do a chroot and then you can "lin sysvinit".

Most users simply get the new sysvinit when they reinstall from
a newer Lunar ISO, that will already have the updated sysvinit
in place.

Terry Chan
----------------------------------------------------------------
On Sun, Sep 21, 2003 at 02:37:58PM -0600, Richard B. Pyne wrote:
> I'm going to try this again.....
> 
> In trying to resolve a problem, I am trying to "lin -r -c
> sysvinit".
> 
> Everything works fine until it gets to the install and then 
> barfs
> with 
> 
> make: Entering directory `/usr/src/sysvinit-2.85/src'
> install -o root -g root -m 755 halt init killall5 sulogin \
>                 runlevel shutdown /sbin
> install: cannot remove `/sbin/init': Operation not permitted
> make: *** [install] Error 1 make: Leaving directory
> `/usr/src/sysvinit-2.85/src'
> 
> I was able to manually install eveything except init.
> 
> How is one supposed to update init if the system won't allow
> writing the file?
> 
> Also, I noticed that when I did the lin sysvinit that it was a
> newer version and that lunar update had not updated it.
> 
> --Richard
> 
> 
> -- 
> Richard B. Pyne
> rpyne at kinfolk.org
>