From: Ian Hastie <ianh@iahastie.clara.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Re: modules
Date: Sat, 5 Nov 2005 02:12:59 +0000 [thread overview]
Message-ID: <20051105021259.75ccbb93@iahastie.local.net> (raw)
In-Reply-To: <pan.2005.11.04.20.35.18.345644@cox.net>
On Fri, 04 Nov 2005 13:35:19 -0700
Duncan <1i5t5.duncan@cox.net> wrote:
> Sebastian Redl posted <436BBEE8.1070303@getdesigned.at>, excerpted
> below, on Fri, 04 Nov 2005 21:04:56 +0100:
>
> > Duncan wrote:
> >
> >>You don't need to load /any/ modules at boot, if you compile
> >>everything you'd normally load at boot and never unload, into the
> >>kernel itself, instead of as modules.
> >>
> >>
> > The single exception here are binary-only modules, usually
> > proprietary drivers. The ATI graphics driver fglrx comes to mind.
>
> True, except that you shouldn't need to load it /at/ /boot/ either,
> only when you run X. The rest of the time the normal kernel console
> video driver should be fine.
Which is true unless you run a display manager and log in through
that. The only hard and fast rule of Linux is that there are no hard
and fast rules.
--
Ian.
EOM
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-05 2:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 12:40 [gentoo-amd64] modules DR GM SEDDON
2005-11-04 13:49 ` [gentoo-amd64] modules Duncan
2005-11-04 20:04 ` Sebastian Redl
2005-11-04 20:35 ` [gentoo-amd64] " Duncan
2005-11-05 2:12 ` Ian Hastie [this message]
2005-11-07 9:42 ` Paul de Vrieze
2005-11-04 21:25 ` [gentoo-amd64] " Steve Herber
2005-11-05 9:24 ` [gentoo-amd64] " Duncan
-- strict thread matches above, loose matches on Subject: below --
2005-11-04 22:55 [gentoo-amd64] " Dmitri Pogosyan
2005-11-05 0:05 ` Nuitari
2005-11-05 9:39 ` [gentoo-amd64] " Duncan
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=20051105021259.75ccbb93@iahastie.local.net \
--to=ianh@iahastie.clara.net \
--cc=gentoo-amd64@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