[SOLVED] Lacking rc.modules-$(uname -r) after upgrade to Slackware64 14.2, is this right?

j12i · 09-26-2016, 04:37 PM

Hello,
after the upgrade to Slackware64 14.2, I do not have a /etc/rc.d/rc.modules-$(uname -r) file anymore.
Is this right?

I wondered if I was supposed to copy the file from the last kernel I used on 14.1, but I did not do it because

the documentation (UPGRADING.TXT & CHANGES_AND_HINTS.TXT) did not say anything about this
I thought there must have been some important changes with the kernel major version jump.

On the other hand

I am a bit worried because the old rc.modules-X stressed the importance of loading the "thermal" module
for one I am pretty sure I need to load the "lp" module for printing (but, maybe I am supposed to do this in another place after the upgrade?).

Love & Light

PS.: Yes, I have a parallel printer, and no, it does not work, regardless of lp being loaded. But that is an issue for another thread, and I would like to work the above out first.

Richard Cranium · 09-26-2016, 04:44 PM

Please see http://www.linuxquestions.org/questi...on-4175483641/

You can skip the first two pages if you wish; the meat's at the end.

EDIT: the tl;dr version is...

Create the file /etc/rc.d/rc.modules.local and put your special modprobe commands in there.

But the thread is interesting in that it explains the thought processes involved.

zk1234 · 09-26-2016, 04:56 PM

rc.modules was written in the early Cretaceous Period. At that time Tyrannosaurus was still alive, but there was no udev daemon. Now we have have udev, so both rc.modules and T. Rex are somewhat depreciated.

.

GazL · 09-27-2016, 02:53 AM

Just because much of what it did is now done on-demand by (e)udev doesn't mean it no longer has a role to play. There are modules other than those which load hardware support, and which can't be loaded on-demand by udev. They need to be loaded somewhere, and rc.modules seems as good a place as any.

Don't dis the Dinos; if it wasn't for an unfortunate encounter with an asteroid they'd be walking around now... eating Ubuntu users!

zk1234 · 09-27-2016, 04:07 AM

Quote:

Originally Posted by GazL

Just because much of what it did is now done on-demand by (e)udev doesn't mean it no longer has a role to play. There are modules other than those which load hardware support, and which can't be loaded on-demand by udev. They need to be loaded somewhere, and rc.modules seems as good a place as any.

That's true. Some modules are not loaded on demand. The lp module mentioned by TS is a good example. The same with loop (*) and some others.

(*) Yes, I know. The "loop" module is built-in into the kernel image by default in Slackware.

.

GazL · 09-27-2016, 05:19 AM

Quote:

Originally Posted by zk1234

(*) Yes, I know. The "loop" module is built-in into the kernel image by default in Slackware.

.

Actually it's not, at least not for the 'generic' kernels. It used to be a built-in but Pat changed that a few years ago and added a rc.loop to run the modprobe. It's not a change I agree with but it's Pat's decision to make so what I think doesn't matter.

zk1234 · 09-27-2016, 05:47 AM

Quote:

Originally Posted by GazL

Actually it's not, at least not for the 'generic' kernels. It used to be a built-in but Pat changed that a few years ago and added a rc.loop to run the modprobe. It's not a change I agree with but it's Pat's decision to make so what I think doesn't matter.

It looks that I am also slowly becoming a depreciated T.Rex :-)

.