Re: pxesconfig makes copies instead of symlinks

On Monday 28 March 2005 01:15, Chris Gianelloni wrote:
> On Sun, 2005-03-27 at 23:30 +0200, Thorsten Huefner wrote:
> > I've a bit of trouble with a fresh pxes-0.9 installation on gentoo. It is
> > not the first installation in this kind but the first doesn't work.
>
> If you think it is a Gentoo bug, then file a bug with Gentoo instead.

No Chris, i dont't think that this is a gentoo bug. It is not the first 
installation of pxes on gentoo, I'm using only gentoo since some years. 
And I have two other boxes with the same gtk-perl, glade-perl, perl and pxes  
versions,  and that works. One box is running the same kernel (2.6.9-ac12) 
like the "buggy", i don't know what is the difference. (and i don't think 
that the kernel has anything to do with that)

[...]
> The initrd size should be generated dynamically, but it is quite
> possible that the sandbox used by portage is causing the problem.

No, probably not. The pxes stock is right, symlinks to busybox. The ramdisc 
size is calculated for using symlinks, and pxesconfig copies busyboy (and 
most probably all others that should be a symlink) instead of making 
symlinks, that is the disaster. 
>
> Try running:
>
> emerge -C pxes && FEATURES="-sandbox -usersandbox" emerge pxes

That should not make a difference, but i've tried it. No difference.
>
> If that works, then I'll have to look into the tarball and manually
> create every symlink within the ebuild.

No, your ebuild is right. That works perfect on the other box (wich one is 
identical to the buggy, IMHO)
Fancy ;-)





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click