From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] USE Linux 2.6.x
Date: 21 Oct 2003 16:15:42 -0400 [thread overview]
Message-ID: <1066767342.14019.11.camel@orange-pc.ces.clemson.edu> (raw)
In-Reply-To: <200310211044.48299.cbrewer@stealthaccess.net>
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
> 1,2,3 things that haven't been done yet.. Personally I compile mine in /opt,
> because my /home is pretty full...
So you move the sources from /usr/src/ to /opt, or you don't use the
various kernel-sources ebuilds? If you're moving the sources, what
makes /opt better than /usr/src?
Incidentally, I'm quite glad that /usr/src/linux is the target of a lot
of our ebuilds, since it's fairly common for me to build and install
alsa, pcmcia, and nvidia modules for the kernel I'm about to boot into.
(Why do I want to build the modules before rebooting? Because that way I
don't have to spend twenty minutes in console mode before I can have
working sound, video, and networking.)
-g2boojum-
--
Grant Goodyear <g2boojum@gentoo.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-21 20:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 12:48 [gentoo-dev] USE Linux 2.6.x Dhruba Bandopadhyay
2003-10-21 12:58 ` Mike Frysinger
2003-10-21 15:39 ` C. Brewer
2003-10-21 16:25 ` Thomas de Grenier de Latour
2003-10-21 17:44 ` C. Brewer
2003-10-21 20:15 ` Grant Goodyear [this message]
2003-10-22 3:11 ` C. Brewer
2003-10-21 20:53 ` Martin Schlemmer
2003-10-21 22:25 ` Spider
2003-10-22 3:44 ` C. Brewer
2003-10-22 8:15 ` Chris Smith
2003-10-22 8:17 ` Paul de Vrieze
2003-10-22 18:27 ` C. Brewer
2003-10-22 18:46 ` Brian Jackson
2003-10-22 19:23 ` Paul de Vrieze
2003-10-22 19:47 ` C. Brewer
2003-10-22 20:06 ` Spider
2003-10-22 10:40 ` Spider
2003-10-22 18:07 ` C. Brewer
2003-10-22 19:01 ` Spider
2003-10-22 11:20 ` Patrick Lauer
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=1066767342.14019.11.camel@orange-pc.ces.clemson.edu \
--to=g2boojum@gentoo.org \
--cc=gentoo-dev@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