On 8/1/07, Dan Cowsill <[EMAIL PROTECTED]> wrote:
>
/etc/genkernel.conf
# Run 'make menuconfig' before compiling this kernel?
MENUCONFIG="no"
# Run 'make clean' before compilation?
# If set to NO, implies MRPROPER WILL NOT be run
# Also, if clean is NO, it won't copy over any configuration
# file, it will use what's there.
CLEAN="no"
# Run 'make mrproper' before configuration/compilation?
MRPROPER="no"
# Save the new configuration in /etc/kernels upon
# successfull compilation
SAVE_CONFIG="yes"
# Debug Level
DEBUGLEVEL=5
Set those, and then I recommend just stay with using genkernel, it
basically converts genkernel from a kernel configurator, to merely a
nice automated build-and-install script.
that way you can configure your kernel custome like usual, and then just
genkernel --kernname=somenickname all
and go away and leave it and it will take care of the rest :)
--
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print "enNOSPicAMreil [EMAIL PROTECTED]"[(2*x)..(2*x+1)]}'
--
[EMAIL PROTECTED] mailing list
