Re: [Devil-Linux-discuss] adding binaries to initial boot process

[Serge L. <fi...@in...>]

John,

I'm not sure you should copy binaries from 'big" system to initrd, because the
majority of ordinary files are dynamically linked and you will need to copy all
libs as well or rebuild tools in order to get statically linked binaries.

In initrd we use busybox - please check if busybox has mkfs.ext2 and sfdisk in
the list of supported applets.

Sincerely,
Serge


On 03/03/2010 06:48 PM, John Dailey wrote:
> Further information....I'm still having problems executing these
> commands.  I successfully have the files available during the iso boot,
> but they won't execute.
> 
> What I keep ending up with is this:
> 
> /init: line 348: /sbin/mkfs.ext2: not found
> 
> But if I include commands before the mkfs.ext2 like "which mkfs.ext2" it
> prints out /sbin/mkfs.ext2.  And if I do a "ls -l /sbin" I see my files
> there with the execute bit set on.
> 
> Both mkfs.ext2 and sfdisk give this same error, yet both appear to be
> available from the output from the "ls -l /sbin" command
> 
> All this is done from the linuxrc file, not from later scripts.
> 
> I'm sure I'm missing something important here.
> 
> -John
> 
> On Wed, Mar 3, 2010 at 6:37 PM, John Dailey <jd...@cp...
> <mailto:jd...@cp...>> wrote:
> 
>     OK, I may be answering my own question here -- hopefully someone can
>     stop me if I'm going down the wrong track.
> 
>     Browsing through the code, it looks like the initrdtree is built
>     piecemeal by the install make target of all the various packages.
>      So I altered the scripts ~/scripts/e2fsprogs and
>     ~/scripts/util-linux and did a manual cp to $INITRDDIR at the end of
>     the install block.
> 
>     I'm hoping this is a sensible way of doing this.
> 
>     -John
> 
> 
>     On Wed, Mar 3, 2010 at 4:04 PM, John Dailey <jd...@cp...
>     <mailto:jd...@cp...>> wrote:
> 
>         Hello,  I'm practicing customizing devil-linux, and am not quite
>         sure how to continue:
> 
>         I'm wanting to alter the boot-up procedure to auto format a
>         local hard drive in a certain way automatically during boot,
>         then use one of the partitions as the configuration store.  I've
>         found how to edit ~/config/etc/initrd/linuxrc, and clear the
>         build flag at ~/tmp/FLAGS/install/create-etc.  I'm successfully
>         rebuilding the iso file, and my changes are reflected during the
>         new boot.
> 
>         The problem is that during the boot process, I don't have access
>         to two utilities I need: sfdisk, and mkfs.ext2.  
> 
>         What is the 'correct' way to get those binaries to find their
>         way into a place accessible during boot.  Am I wanting to see
>         them show up in ~/tmp/ISO/initrdtree/bin?  Where do I make a
>         change to have them show up there?
> 
>         Also, if anyone thinks I'm going to run into some dependency
>         problems with those binaries, other suggestions are welcome.
> 
>         Thank you for any help you can provide.
> 
>         -John Dailey
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> 
> 
> 
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss