Tracking userland tools and kernel version compatibility
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I'm using CentOS 7, which is originally shipped with 3.10 kernel. At some point I needed to upgrade kernel version to 4.4 and add some modules support, so I've built a new kernel from vanilla sources using make rpm method. I guess the next step I need to perform is to update all userland tools that somehow relate to the kernel version (e.g. xfsprogs). What is the right way to track down all the packages I need to update?
centos linux-kernel upgrade
edited Dec 30 '17 at 13:02
Jeff Schaller
31.9k848109
asked Dec 13 '17 at 16:00
Sergey Vinogradov
11
add a comment |Â
up vote
0
down vote
favorite
I'm using CentOS 7, which is originally shipped with 3.10 kernel. At some point I needed to upgrade kernel version to 4.4 and add some modules support, so I've built a new kernel from vanilla sources using make rpm method. I guess the next step I need to perform is to update all userland tools that somehow relate to the kernel version (e.g. xfsprogs). What is the right way to track down all the packages I need to update?
centos linux-kernel upgrade
edited Dec 30 '17 at 13:02
Jeff Schaller
31.9k848109
asked Dec 13 '17 at 16:00
Sergey Vinogradov
11
1
The kernel developers take it as a point of pride that they do not break the kernel/userspace interface. I suspect that you can upgrade the kernel without having to change any userspace tools.
– Andy Dalton
Dec 13 '17 at 16:19
Well, xfsprogs depend on kernel version indirectly. For example, new XFS driver may introduce some changes to the on-disk format and old xfsrepair will consider the FS corrupted.
– Sergey Vinogradov
Dec 13 '17 at 16:30
No. If XFS adds a new feature, that'd be a feature that would be enabled at filesystem creation time. Existing filesystems would not be modified. See: xfs.org/index.php/…
– Andy Dalton
Dec 13 '17 at 16:37
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm using CentOS 7, which is originally shipped with 3.10 kernel. At some point I needed to upgrade kernel version to 4.4 and add some modules support, so I've built a new kernel from vanilla sources using make rpm method. I guess the next step I need to perform is to update all userland tools that somehow relate to the kernel version (e.g. xfsprogs). What is the right way to track down all the packages I need to update?
centos linux-kernel upgrade
edited Dec 30 '17 at 13:02
Jeff Schaller
31.9k848109
asked Dec 13 '17 at 16:00
Sergey Vinogradov
11
I'm using CentOS 7, which is originally shipped with 3.10 kernel. At some point I needed to upgrade kernel version to 4.4 and add some modules support, so I've built a new kernel from vanilla sources using make rpm method. I guess the next step I need to perform is to update all userland tools that somehow relate to the kernel version (e.g. xfsprogs). What is the right way to track down all the packages I need to update?
centos linux-kernel upgrade
edited Dec 30 '17 at 13:02
Jeff Schaller
31.9k848109
asked Dec 13 '17 at 16:00
Sergey Vinogradov
11
edited Dec 30 '17 at 13:02
Jeff Schaller
31.9k848109
edited Dec 30 '17 at 13:02
Jeff Schaller
31.9k848109
edited Dec 30 '17 at 13:02
Jeff Schaller
31.9k848109
31.9k848109
asked Dec 13 '17 at 16:00
Sergey Vinogradov
11
asked Dec 13 '17 at 16:00
Sergey Vinogradov
11
asked Dec 13 '17 at 16:00
Sergey Vinogradov
11
11
1
The kernel developers take it as a point of pride that they do not break the kernel/userspace interface. I suspect that you can upgrade the kernel without having to change any userspace tools.
– Andy Dalton
Dec 13 '17 at 16:19
Well, xfsprogs depend on kernel version indirectly. For example, new XFS driver may introduce some changes to the on-disk format and old xfsrepair will consider the FS corrupted.
– Sergey Vinogradov
Dec 13 '17 at 16:30
No. If XFS adds a new feature, that'd be a feature that would be enabled at filesystem creation time. Existing filesystems would not be modified. See: xfs.org/index.php/…
– Andy Dalton
Dec 13 '17 at 16:37
add a comment |Â
1
The kernel developers take it as a point of pride that they do not break the kernel/userspace interface. I suspect that you can upgrade the kernel without having to change any userspace tools.
– Andy Dalton
Dec 13 '17 at 16:19
Well, xfsprogs depend on kernel version indirectly. For example, new XFS driver may introduce some changes to the on-disk format and old xfsrepair will consider the FS corrupted.
– Sergey Vinogradov
Dec 13 '17 at 16:30
No. If XFS adds a new feature, that'd be a feature that would be enabled at filesystem creation time. Existing filesystems would not be modified. See: xfs.org/index.php/…
– Andy Dalton
Dec 13 '17 at 16:37
1
1
The kernel developers take it as a point of pride that they do not break the kernel/userspace interface. I suspect that you can upgrade the kernel without having to change any userspace tools.
– Andy Dalton
Dec 13 '17 at 16:19
The kernel developers take it as a point of pride that they do not break the kernel/userspace interface. I suspect that you can upgrade the kernel without having to change any userspace tools.
– Andy Dalton
Dec 13 '17 at 16:19
Well, xfsprogs depend on kernel version indirectly. For example, new XFS driver may introduce some changes to the on-disk format and old xfsrepair will consider the FS corrupted.
– Sergey Vinogradov
Dec 13 '17 at 16:30
Well, xfsprogs depend on kernel version indirectly. For example, new XFS driver may introduce some changes to the on-disk format and old xfsrepair will consider the FS corrupted.
– Sergey Vinogradov
Dec 13 '17 at 16:30
No. If XFS adds a new feature, that'd be a feature that would be enabled at filesystem creation time. Existing filesystems would not be modified. See: xfs.org/index.php/…
– Andy Dalton
Dec 13 '17 at 16:37
No. If XFS adds a new feature, that'd be a feature that would be enabled at filesystem creation time. Existing filesystems would not be modified. See: xfs.org/index.php/…
– Andy Dalton
Dec 13 '17 at 16:37
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f410675%2ftracking-userland-tools-and-kernel-version-compatibility%23new-answer', 'question_page');
);
Post as a guest
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
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
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
1
The kernel developers take it as a point of pride that they do not break the kernel/userspace interface. I suspect that you can upgrade the kernel without having to change any userspace tools.
– Andy Dalton
Dec 13 '17 at 16:19
Well, xfsprogs depend on kernel version indirectly. For example, new XFS driver may introduce some changes to the on-disk format and old xfsrepair will consider the FS corrupted.
– Sergey Vinogradov
Dec 13 '17 at 16:30
No. If XFS adds a new feature, that'd be a feature that would be enabled at filesystem creation time. Existing filesystems would not be modified. See: xfs.org/index.php/…
– Andy Dalton
Dec 13 '17 at 16:37