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@lists.xensource.com
http://lists.xensource.com/xen-users
Luke Crawford
2006-Sep-19 04:29 UTC
Re: [Xen-users] prebuilt tar ball installation problems
Hah. I''ve run into #1. do a google for "tar symlink" there are many versions of tar running around; some follow symlinks by default, others clobber symlinks by default. If I recall correctly, RHEL3 does one thing, RHEL4 does another. It''s a pain in the ass. really, you have to figure out what verson of tar you are using and then use the ''follow symlinks'' option to get it to work as expected. On Tue, 19 Sep 2006, Jitendra Nair wrote:> Date: Tue, 19 Sep 2006 09:52:47 +0530 > From: Jitendra Nair <jnair@ensim.com> > To: xen users <xen-users@lists.xensource.com> > Subject: [Xen-users] prebuilt tar ball installation problems > > > 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@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users