I found a mkinitrd script that runs on gentoo from LFS....someone want to make an ebuild of it ? maybe tweak it a little. I have tested it & it works fine... Before you run it emerge busybox....also edit the script & enter your root device.

----->CUT
# Begin /etc/initrd.conf
#
# This is a file that is used to create an initrd image.
# The only items need to be listed in this file are ones that
# you need to boot up. IE a SCSI controller that has hard drives
# on it.
#
# If you use this to create a initial ram disk for scsi you
# must include the following modules
# scsi_mod sd_mod
#
# File format is as follows
# module:options_for_module
# Example
# aic7xxx:io=0xc00
# Example without options
# aic7xxx:

# SCSI
scsi_mod:
aic7xxx:
sd_mod:

# End /etc/initrd.conf

<----- CUT

Last edited by col on Thu Oct 10, 2002 3:43 am; edited 2 times in total

No I think an ebuild because it requires the busybox ebuild to be installed. I know it may be overkill but would save people a little hassle downloading the script then emerge busy box ... maybe they wont realise they need busybox when they download it ?

Well, now they know... (you just said it)
The main reason I would be against an ebuild for it is that it can be quite simply copied and pasted, and people now know they need busybox.
It's simply not worth it, quite honestly. There are a dozens of scripts in "Documentation, Tips & Tricks" that do very nifty things, but to be quite honest none of them deserve an ebuild. Ebuilds are mainly for things that are either built from source, or huge binary trees of things. Basically, something that is more than one file, and a dependancy of another ebuild.

I'm not going to stop you from doing this, because quite frankly I can't. But it is a bad idea.
That is what this area is for... to fill the grey area between ebuild and nothing.