public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kent Fredric" <kentfredric@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Switching from Genkernel to manual build
Date: Wed, 1 Aug 2007 21:17:21 +1200	[thread overview]
Message-ID: <8cd1ed20708010217h4d67f160r18fa471e8cc70240@mail.gmail.com> (raw)
In-Reply-To: <4ef07b8c0707312108i56bc5129qac7e179e049f9890@mail.gmail.com>

On 8/1/07, Dan Cowsill <danthehat@gmail.com> 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 kdrtf@gma.com"[(2*x)..(2*x+1)]}'
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2007-08-01  9:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01  4:08 [gentoo-user] Switching from Genkernel to manual build Dan Cowsill
2007-08-01  6:08 ` Abraham Marín Pérez
2007-08-01  7:15   ` Dale
2007-08-01 18:40   ` Don Jerman
2007-08-01  9:17 ` Kent Fredric [this message]
2007-08-01 16:59   ` Volker Armin Hemmann
2007-08-01 20:28     ` Kent Fredric
2007-08-01 21:05       ` Neil Bothwick
2007-08-01 21:22         ` Daniel da Veiga

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8cd1ed20708010217h4d67f160r18fa471e8cc70240@mail.gmail.com \
    --to=kentfredric@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox