|
From: John D. <jd...@cp...> - 2010-03-03 23:37:51
|
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...> 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 > |