-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mick wrote:
Of course not necessary for the kernel (as Michael Weyershäuser
already said), but what about the copy of the .config file?
OK, copying the .config file to /boot/ would be a good idea if you do
so. However it is not necessary to do
On 13/06/06, Ryan Tandy [EMAIL PROTECTED] wrote:
Anthony E. Caudel wrote:
How? make modules_install or the whole thing: make make
modules_install then just modprobe the new module?
# make modules modules_install
# modprobe module
Do you also need to run make install or is it not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mick wrote:
Do you also need to run make install or is it not necessary to
copy anything to /boot?
No need for that if you have only added modules. make modules only
builds the modules, not the kernel itself, so copying the kernel to
/boot
Mick wrote:
On 13/06/06, Ryan Tandy [EMAIL PROTECTED] wrote:
Anthony E. Caudel wrote:
How? make modules_install or the whole thing: make make
modules_install then just modprobe the new module?
# make modules modules_install
# modprobe module
Do you also need to run make install or
On 17/06/06, Anthony E. Caudel [EMAIL PROTECTED] wrote:
Mick wrote:
On 13/06/06, Ryan Tandy [EMAIL PROTECTED] wrote:
Anthony E. Caudel wrote:
How? make modules_install or the whole thing: make make
modules_install then just modprobe the new module?
# make modules modules_install
#
I like compile-in, generally less work must be done (just a hair, but
it is less)
On 6/17/06, Mick [EMAIL PROTECTED] wrote:
On 17/06/06, Anthony E. Caudel [EMAIL PROTECTED] wrote:
Mick wrote:
On 13/06/06, Ryan Tandy [EMAIL PROTECTED] wrote:
Anthony E. Caudel wrote:
How? make
On Mon, 12 Jun 2006, Anthony E. Caudel wrote:
I was wondering what gentoo-users think and practice about kernel
modules. Do most compile them in the kernel or load them at boot-up.
Note that I'm _NOT_ talking about those modules that have to be compiled
in such as for your filesystem.
Teresa and Dale wrote:
Care to guess how much I like modules:
[EMAIL PROTECTED] / # lsmod
Module Size Used by
nvidia 4551892 12
[EMAIL PROTECTED] / #
I would have that one in there if I could. I never did like them.
Why?
--
Those who would give up
Anthony E. Caudel wrote:
I was wondering what gentoo-users think and practice about kernel
modules. Do most compile them in the kernel or load them at boot-up.
Note that I'm _NOT_ talking about those modules that have to be compiled
in such as for your filesystem. This is about the other
oh, there is one thing where it is useful to have modules. That would
be projects where the codebase will be updated more often than you
update your kernels (I'm looking at you ALSA). In those circumstances
it may be more valuable to have the flexibility to update code without
having to reboot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I usualy start with a kernel with almost everything compiled in (but
only things I definitely need), only using modules when I have to
(USB for suspend2 comes to my mind). Over time whenever I need
something new (filesystem, hardware driver,...) I
On 6/12/06, Michael Weyershäuser [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I usualy start with a kernel with almost everything compiled in (but
only things I definitely need), only using modules when I have to
(USB for suspend2 comes to my mind). Over time whenever
On 6/11/06, Anthony E. Caudel [EMAIL PROTECTED] wrote:
I was wondering what gentoo-users think and practice about kernel
modules. Do most compile them in the kernel or load them at boot-up.
I have heard a security argument made that it is safer to compile
everything into the kernel, and
Evan Klitzke wrote:
I have heard a security argument made that it is safer to compile
everything into the kernel, and disable support for modules entirely.
I would say this is a must on server. This way you would close
one potential security leak. Of course, it does not help if you
leave a few
On Mon, 12 Jun 2006 11:16:56 -0700, Evan Klitzke wrote:
I have heard a security argument made that it is safer to compile
everything into the kernel, and disable support for modules entirely.
The reason for this is that if someone can load malicious modules on
your system they can basically
Evan Klitzke wrote:
On 6/11/06, Anthony E. Caudel [EMAIL PROTECTED] wrote:
I was wondering what gentoo-users think and practice about kernel
modules. Do most compile them in the kernel or load them at boot-up.
I have heard a security argument made that it is safer to compile
everything into
Michael Weyershäuser wrote:
I usualy start with a kernel with almost everything compiled in (but
only things I definitely need), only using modules when I have to
(USB for suspend2 comes to my mind). Over time whenever I need
something new (filesystem, hardware driver,...) I tend to compile it
Yea, of course you can do that, though you have to be careful if your
kernel tree has changed to a different version than the one you're
booted from (usually you can still just force the module to load, but
a module from a different kernel tree may not want to play nicely with
everything else).
Anthony E. Caudel wrote:
Teresa and Dale wrote:
Care to guess how much I like modules:
[EMAIL PROTECTED] / # lsmod
Module Size Used by
nvidia 4551892 12
[EMAIL PROTECTED] / #
I would have that one in there if I could. I never did like them.
I was wondering what gentoo-users think and practice about kernel
modules. Do most compile them in the kernel or load them at boot-up.
Note that I'm _NOT_ talking about those modules that have to be compiled
in such as for your filesystem. This is about the other ones.
I generally like to load
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Anthony E. Caudel wrote:
I was wondering what gentoo-users think and practice about kernel
modules. Do most compile them in the kernel or load them at boot-up.
Note that I'm _NOT_ talking about those modules that have to be compiled
in such as
21 matches
Mail list logo
