Unix Technical Forum

a/module-init-tools-3.2.2-i486-1.tgz

This is a discussion on a/module-init-tools-3.2.2-i486-1.tgz within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hi there, Anyone know what's behind this Changelog entry? a/module-init-tools-3.2.2-i486-1.tgz: Upgraded to module-init-tools-3.2.2. This new version of module-init-tools has ...


Go Back   Unix Technical Forum > Unix Operating Systems > Slackware Linux Support

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 02-20-2008, 03:29 PM
Grant
 
Posts: n/a
Default a/module-init-tools-3.2.2-i486-1.tgz

Hi there,

Anyone know what's behind this Changelog entry?

a/module-init-tools-3.2.2-i486-1.tgz: Upgraded to module-init-tools-3.2.2.
This new version of module-init-tools has been patched to look for module
configuration information in /etc/modprobe.conf only for 2.4.x kernels.
For 2.6.x kernels, files found in the directory /etc/modprobe.d/ are used
instead. Eventually, /etc/modprobe.conf will be phased out in favor of
the /etc/modprobe.d/ approach. If you have anything in your
/etc/modprobe.conf that you need, and you are using a 2.6.x kernel, be sure
to copy the configuration to a file (or files) in /etc/modprobe.d/.
Hint: ALSA expects sound modules to be configured in /etc/modprobe.d/sound.

2.4.x kernels use /etc/modules.conf, whay change that?

Grant.
--
Memory fault -- brain fried
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 02-20-2008, 03:29 PM
Damjan
 
Posts: n/a
Default Re: a/module-init-tools-3.2.2-i486-1.tgz

It looks like an error in the ChangeLog to me.

For 2.4.x kernels, a separate binaries are used anyway, and from what I
see those are not patched at all.

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 02-20-2008, 03:29 PM
Grant
 
Posts: n/a
Default Re: a/module-init-tools-3.2.2-i486-1.tgz

On 29 Mar 2006 05:14:32 -0800, "Damjan" <gdamjan@gmail.com> wrote:

>It looks like an error in the ChangeLog to me.
>
>For 2.4.x kernels, a separate binaries are used anyway, and from what I
>see those are not patched at all.


I'm still waiting for the source to dribble in (local rsync mirror)
so I can see the 'patch' referred to. Got the source, no mention
of modules.conf... So it is 2.6 + modprobe.conf only. Basically
the patch puts /etc/modprobe.d/ ahead of /etc/modprobe.conf:

--- ./modprobe.c.orig 2005-12-01 17:42:09.000000000 -0600
+++ ./modprobe.c 2006-03-16 19:12:39.000000000 -0600
@@ -1211,8 +1211,8 @@

static const char *default_configs[] =
{
- "/etc/modprobe.conf",
"/etc/modprobe.d",
+ "/etc/modprobe.conf",
};

So yeah, looks like a typo in the Changelog when it refer to 2.4.X

Grant.
--
Memory fault -- brain fried
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 09:15 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.2.0
www.UnixAdminTalk.com