public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems installing
Date: Thu, 04 Aug 2005 15:35:33 -0700	[thread overview]
Message-ID: <42F29835.7050009@gmail.com> (raw)
In-Reply-To: <200508041708.13248.yeahsowhat@gmail.com>

Chris Cox wrote:
> On Thursday 04 August 2005 04:41 pm, Daniel da Veiga wrote:
> 
>>Well, if you use genkernel, it should automatically place the initrd
>>and the kernel image at your /boot (at least it does for me). Maybe
>>check your genkernel command to compile the kernel.
>>
> 
> 
> Whats wrong with compiling a kernel the normal way ? 
> 
> emerge gentoo-sources (or whatever flavor you prefer)
> cd /usr/src/linux && zcat /proc/config.gz >.config 
> make oldconfig
> make menuconfig
> * tweak it to your liking
> make install modules modules_install
> update your boot loader
> umount /boot
> exit chroot 
> reboot
> 
>  Isn't that covered in the Install guide ?  
> 

No on said anything was wrong with with doing it the normal way. ;-)

In fact, genkernel is not really different from "the normal way".  It runs basically the same commands that you would run by hand.  Personally, I use it to generate my initramfs.  I'm fully awary that genkernel can be a needless complication for n00bs.

Zac
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-08-04 22:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 21:26 [gentoo-user] Problems installing Stewart Taylor
2005-08-04 21:41 ` Daniel da Veiga
2005-08-04 22:08   ` Chris Cox
2005-08-04 22:35     ` Zac Medico [this message]
2005-08-05 18:38     ` Stewart Taylor
2005-08-04 21:58 ` Zac Medico
2005-08-05 18:33   ` Stewart Taylor
2005-08-04 22:39 ` C.Beamer
  -- strict thread matches above, loose matches on Subject: below --
2005-08-04 21:50 Bryce

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=42F29835.7050009@gmail.com \
    --to=zmedico@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