Re: [Xen-users] prebuilt tar ball installation problems

[Tim Post <tim.post@xxxxxxxxxxxxxxx>]

If you have /etc/rc.d/init.d then I'm assuming you're on some kind of
white box flavor, which means tar is going to treat symlinks a little
differently by default.

You can fix this just by issuing:

mv /etc/init.d/* /etc/rc.d/init.d/

then re-link it via

rm -rf /etc/init.d
ln -s /etc/rc.d/init.d/ /etc/init.d

then run a chkconfig --list to be sure everything is on or off in the
appropriate run levels.

As for your initrd, that should be rather easy to make :

mkinitrd /boot/initrd-(kernelname).img `uname -r` may do the trick, if
not specify your kernel version so mkinitrd knows what modules to build
in the initrd image. (kernelname) should be the same as uname -r.

Not sure if you were just posting your experiences, or asking for
help .. so sorry if my reply seems rather pedantic :)

HTH
-Tim

On Tue, 2006-09-19 at 09:52 +0530, Jitendra Nair wrote:
> Hi All ,
> 
>   I  used  the  Pre-built installations of Xen 3.0 (3.0.2) , after the 
> installation my /etc/init.d  conatined just
>   1) xend and 2) xendomains   and all other stuff was gone , and on boot 
> gave me lot of errors .
> 
>   But as /etc/init.d is a symlink to /etc/rc.d/init.d my old stuff was  
> lying safe in there .
>  
> question1 )  It seems the installer deleted the symlink and created a 
> new /etc/init.d , so is this the
>                   correct installer behavior
>  
> question 2 ) The installer  did the install the initrd  image . 
> 
> 
> TIA
> regards
> Jitendra Nair
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users