Re: incompatibilities between utilities/busybox/busybox.links & scripts/rootdisk/LINKS

[Erik Andersen <andersen@xmission.com>]

On Fri Nov 12, 1999 at 12:09:44AM +0100, Eric Delaunay wrote:
> 
> Hello,
> 
>   I discovered some problems with hardlinks to busybox in rootdisk:
> true & false are disabled in busybox.def.h but links are still made in the root
> image.

I have no problem with re-enabling them.  Is that what people want?

> It seems there are 2 files that list the names of hardlinks: one built
> dynamically during busybox compilation and named utilities/busybox/busybox.links
> and another static in scripts/rootdisk/LINKS.
> The latter is used to create rootdisk's hardlinks but is not up-to-date.

Hmm.  Why not use something like what I have in the busybox.spec file, i.e:

    mkdir -p $DIRECTORY/bin
    h=`cat busybox.links`
    for i in $h ; do
	    mkdir -p $DIRECTORY/`echo $i | sed -e 's/\(^.*\/\)\(.*\)/\1/g' `
	    (cd $DIRECTORY/bin ; ln -s busybox `echo $i | sed -e 's/\(^.*\/\)\(.*\)/\2/g' ` );
    done
    rm -f $DIRECTORY/bin/busybox
    install -m 755 busybox $DIRECTORY/bin/busybox

that way the links are autogenerated from whatever the current busybox
includes in the build...

> Another problem is about loadkmap: it is put in /usr/bin by rootdisk.sh but is
> assumed to be in /bin by dbootstrap (see main_menu.c, line 212) and in /sbin by
> busybox (see busybox.links).  Where is the right directory?
> This conflict in directory naming has the side effect of disabling keyboard
> configuration step in dbootstrap.

Somebody tell me where they want it if not in /sbin...

 -Erik

--
Erik B. Andersen   Web:    http://www.xmission.com/~andersen/ 
                   email:  andersee@debian.org
--This message was written using 73% post-consumer electrons--