Autoloading a particular driver, based on a detected specific kernel
Clash Royale CLAN TAG#URR8PPP
I need to write a script and determining its placement within Debian 7.9 filesystem. The script needs to be executed automatically on startup and, after checking what kernel is currently loaded (2.6.x vs. 3.2.x), unload the incorrect network driver, if loaded, and load the correct one. This question is the follow-up for my prior question and represents the only missing piece of that puzzle, as I've already figured out cross-kernel compiling of network driver by myself.
In terms of the location, I think that the script should be placed into "/etc/rcX.d" directories.
debian shell-script linux-kernel kernel-modules startup
add a comment |
I need to write a script and determining its placement within Debian 7.9 filesystem. The script needs to be executed automatically on startup and, after checking what kernel is currently loaded (2.6.x vs. 3.2.x), unload the incorrect network driver, if loaded, and load the correct one. This question is the follow-up for my prior question and represents the only missing piece of that puzzle, as I've already figured out cross-kernel compiling of network driver by myself.
In terms of the location, I think that the script should be placed into "/etc/rcX.d" directories.
debian shell-script linux-kernel kernel-modules startup
add a comment |
I need to write a script and determining its placement within Debian 7.9 filesystem. The script needs to be executed automatically on startup and, after checking what kernel is currently loaded (2.6.x vs. 3.2.x), unload the incorrect network driver, if loaded, and load the correct one. This question is the follow-up for my prior question and represents the only missing piece of that puzzle, as I've already figured out cross-kernel compiling of network driver by myself.
In terms of the location, I think that the script should be placed into "/etc/rcX.d" directories.
debian shell-script linux-kernel kernel-modules startup
I need to write a script and determining its placement within Debian 7.9 filesystem. The script needs to be executed automatically on startup and, after checking what kernel is currently loaded (2.6.x vs. 3.2.x), unload the incorrect network driver, if loaded, and load the correct one. This question is the follow-up for my prior question and represents the only missing piece of that puzzle, as I've already figured out cross-kernel compiling of network driver by myself.
In terms of the location, I think that the script should be placed into "/etc/rcX.d" directories.
debian shell-script linux-kernel kernel-modules startup
debian shell-script linux-kernel kernel-modules startup
edited Dec 20 '18 at 7:29
Rui F Ribeiro
39k1479130
39k1479130
asked Jan 2 '16 at 15:28
Aleksandr Blekh
1137
1137
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The location you guessed is nearly correct. But /etc/rcX.d
directories usually contain only links to scripts in /etc/init.d/
, so that a script only has to exist once but can be called at different runlevels.
Good points (+1). Thank you!
– Aleksandr Blekh
Dec 20 '18 at 18:30
Happy to can help – if you liek you can also 'accept' this as correct answer, like mot people are used to on StackOverflow
– Jaleks
Dec 20 '18 at 20:03
Sorry, forgot to accept. Done. Happy holidays! :-)
– Aleksandr Blekh
Dec 20 '18 at 21:54
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f252867%2fautoloading-a-particular-driver-based-on-a-detected-specific-kernel%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The location you guessed is nearly correct. But /etc/rcX.d
directories usually contain only links to scripts in /etc/init.d/
, so that a script only has to exist once but can be called at different runlevels.
Good points (+1). Thank you!
– Aleksandr Blekh
Dec 20 '18 at 18:30
Happy to can help – if you liek you can also 'accept' this as correct answer, like mot people are used to on StackOverflow
– Jaleks
Dec 20 '18 at 20:03
Sorry, forgot to accept. Done. Happy holidays! :-)
– Aleksandr Blekh
Dec 20 '18 at 21:54
add a comment |
The location you guessed is nearly correct. But /etc/rcX.d
directories usually contain only links to scripts in /etc/init.d/
, so that a script only has to exist once but can be called at different runlevels.
Good points (+1). Thank you!
– Aleksandr Blekh
Dec 20 '18 at 18:30
Happy to can help – if you liek you can also 'accept' this as correct answer, like mot people are used to on StackOverflow
– Jaleks
Dec 20 '18 at 20:03
Sorry, forgot to accept. Done. Happy holidays! :-)
– Aleksandr Blekh
Dec 20 '18 at 21:54
add a comment |
The location you guessed is nearly correct. But /etc/rcX.d
directories usually contain only links to scripts in /etc/init.d/
, so that a script only has to exist once but can be called at different runlevels.
The location you guessed is nearly correct. But /etc/rcX.d
directories usually contain only links to scripts in /etc/init.d/
, so that a script only has to exist once but can be called at different runlevels.
answered Dec 20 '18 at 10:33
Jaleks
1,384424
1,384424
Good points (+1). Thank you!
– Aleksandr Blekh
Dec 20 '18 at 18:30
Happy to can help – if you liek you can also 'accept' this as correct answer, like mot people are used to on StackOverflow
– Jaleks
Dec 20 '18 at 20:03
Sorry, forgot to accept. Done. Happy holidays! :-)
– Aleksandr Blekh
Dec 20 '18 at 21:54
add a comment |
Good points (+1). Thank you!
– Aleksandr Blekh
Dec 20 '18 at 18:30
Happy to can help – if you liek you can also 'accept' this as correct answer, like mot people are used to on StackOverflow
– Jaleks
Dec 20 '18 at 20:03
Sorry, forgot to accept. Done. Happy holidays! :-)
– Aleksandr Blekh
Dec 20 '18 at 21:54
Good points (+1). Thank you!
– Aleksandr Blekh
Dec 20 '18 at 18:30
Good points (+1). Thank you!
– Aleksandr Blekh
Dec 20 '18 at 18:30
Happy to can help – if you liek you can also 'accept' this as correct answer, like mot people are used to on StackOverflow
– Jaleks
Dec 20 '18 at 20:03
Happy to can help – if you liek you can also 'accept' this as correct answer, like mot people are used to on StackOverflow
– Jaleks
Dec 20 '18 at 20:03
Sorry, forgot to accept. Done. Happy holidays! :-)
– Aleksandr Blekh
Dec 20 '18 at 21:54
Sorry, forgot to accept. Done. Happy holidays! :-)
– Aleksandr Blekh
Dec 20 '18 at 21:54
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f252867%2fautoloading-a-particular-driver-based-on-a-detected-specific-kernel%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown