Multiple custom kernels vs linux-libc-dev
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
The goal: compile and install a new kernel (compiled from a different source) alongside the existing (stock) one.
I have been out of touch with kernel building for the last few years. In the good old days, I would compile a new kernel package, install it, and it would show up alongside my existing kernels when booting.
I did essentially the same, but I ended up with more packages that I used to:
make deb-pkg
linux-headers....deb
linux-image....deb
linux-firmware-image....deb
linux-libc-dev....deb // <---
Upon checking the contents of these packages, most of them have a versioned subdir. linux-libc-dev....deb, however, just spits its content into /usr, without an special path prefix. Meaning it will overwrite whatever the stock package / the custom build before it has put in there...
The question: how can I use multiple kernels on th same system?
Is it somehow safe to install a dozen versions of linux-libc-dev....deb over-and-over?
Shall I just forgo installing, and pretend this is not there, and the stock version linux-libc-dev....deb will do a perfect job supporting another kernel?
Not sure, if its relevant, I am building a newer kernel than I have as stock, going from 4.9.144 to 4.9.160, and 4.20.11. (I am trying to test out an error with different kernels.)
I DID see a lot of posts on "what is linux-libc-dev", none of which answered my question.
kernel compiling debian
asked Feb 24 at 22:04
Zoltan K.Zoltan K.
1083
add a comment |
The goal: compile and install a new kernel (compiled from a different source) alongside the existing (stock) one.
I have been out of touch with kernel building for the last few years. In the good old days, I would compile a new kernel package, install it, and it would show up alongside my existing kernels when booting.
I did essentially the same, but I ended up with more packages that I used to:
make deb-pkg
linux-headers....deb
linux-image....deb
linux-firmware-image....deb
linux-libc-dev....deb // <---
Upon checking the contents of these packages, most of them have a versioned subdir. linux-libc-dev....deb, however, just spits its content into /usr, without an special path prefix. Meaning it will overwrite whatever the stock package / the custom build before it has put in there...
The question: how can I use multiple kernels on th same system?
Is it somehow safe to install a dozen versions of linux-libc-dev....deb over-and-over?
Shall I just forgo installing, and pretend this is not there, and the stock version linux-libc-dev....deb will do a perfect job supporting another kernel?
Not sure, if its relevant, I am building a newer kernel than I have as stock, going from 4.9.144 to 4.9.160, and 4.20.11. (I am trying to test out an error with different kernels.)
I DID see a lot of posts on "what is linux-libc-dev", none of which answered my question.
kernel compiling debian
asked Feb 24 at 22:04
Zoltan K.Zoltan K.
1083
You need image and headers.
– Pilot6
Feb 24 at 22:11
Could you expand on it, in that case, in which situation would the linux-libc-dev....deb needed?
– Zoltan K.
Feb 24 at 23:29
add a comment |
The goal: compile and install a new kernel (compiled from a different source) alongside the existing (stock) one.
I have been out of touch with kernel building for the last few years. In the good old days, I would compile a new kernel package, install it, and it would show up alongside my existing kernels when booting.
I did essentially the same, but I ended up with more packages that I used to:
make deb-pkg
linux-headers....deb
linux-image....deb
linux-firmware-image....deb
linux-libc-dev....deb // <---
Upon checking the contents of these packages, most of them have a versioned subdir. linux-libc-dev....deb, however, just spits its content into /usr, without an special path prefix. Meaning it will overwrite whatever the stock package / the custom build before it has put in there...
The question: how can I use multiple kernels on th same system?
Is it somehow safe to install a dozen versions of linux-libc-dev....deb over-and-over?
Shall I just forgo installing, and pretend this is not there, and the stock version linux-libc-dev....deb will do a perfect job supporting another kernel?
Not sure, if its relevant, I am building a newer kernel than I have as stock, going from 4.9.144 to 4.9.160, and 4.20.11. (I am trying to test out an error with different kernels.)
I DID see a lot of posts on "what is linux-libc-dev", none of which answered my question.
kernel compiling debian
asked Feb 24 at 22:04
Zoltan K.Zoltan K.
1083
The goal: compile and install a new kernel (compiled from a different source) alongside the existing (stock) one.
I have been out of touch with kernel building for the last few years. In the good old days, I would compile a new kernel package, install it, and it would show up alongside my existing kernels when booting.
I did essentially the same, but I ended up with more packages that I used to:
make deb-pkg
linux-headers....deb
linux-image....deb
linux-firmware-image....deb
linux-libc-dev....deb // <---
Upon checking the contents of these packages, most of them have a versioned subdir. linux-libc-dev....deb, however, just spits its content into /usr, without an special path prefix. Meaning it will overwrite whatever the stock package / the custom build before it has put in there...
The question: how can I use multiple kernels on th same system?
Is it somehow safe to install a dozen versions of linux-libc-dev....deb over-and-over?
Shall I just forgo installing, and pretend this is not there, and the stock version linux-libc-dev....deb will do a perfect job supporting another kernel?
Not sure, if its relevant, I am building a newer kernel than I have as stock, going from 4.9.144 to 4.9.160, and 4.20.11. (I am trying to test out an error with different kernels.)
I DID see a lot of posts on "what is linux-libc-dev", none of which answered my question.
kernel compiling debian
kernel compiling debian
asked Feb 24 at 22:04
Zoltan K.Zoltan K.
1083
asked Feb 24 at 22:04
Zoltan K.Zoltan K.
1083
asked Feb 24 at 22:04
Zoltan K.Zoltan K.
1083
asked Feb 24 at 22:04
Zoltan K.Zoltan K.
1083
asked Feb 24 at 22:04
Zoltan K.Zoltan K.
1083
1083
You need image and headers.
– Pilot6
Feb 24 at 22:11
Could you expand on it, in that case, in which situation would the linux-libc-dev....deb needed?
– Zoltan K.
Feb 24 at 23:29
add a comment |
You need image and headers.
– Pilot6
Feb 24 at 22:11
Could you expand on it, in that case, in which situation would the linux-libc-dev....deb needed?
– Zoltan K.
Feb 24 at 23:29
You need image and headers.
– Pilot6
Feb 24 at 22:11
You need image and headers.
– Pilot6
Feb 24 at 22:11
Could you expand on it, in that case, in which situation would the linux-libc-dev....deb needed?
– Zoltan K.
Feb 24 at 23:29
Could you expand on it, in that case, in which situation would the linux-libc-dev....deb needed?
– Zoltan K.
Feb 24 at 23:29
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f1120965%2fmultiple-custom-kernels-vs-linux-libc-dev%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1120965%2fmultiple-custom-kernels-vs-linux-libc-dev%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
You need image and headers.
– Pilot6
Feb 24 at 22:11
Could you expand on it, in that case, in which situation would the linux-libc-dev....deb needed?
– Zoltan K.
Feb 24 at 23:29