Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #264590

Re: Need clarifications about how to deal with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)

Show all headers | View raw

On 11 Dec 2023 04:31 +0100, from rewefie@gmx.com (Stella Ashburne):
> Someone on a social media platform stated that there are only two
> "canonical" [sic] ways to verify the version of Debian installed on
> a system. They are:
> 
> uname -a
> 
> /proc/version
> 
> Do you agree with the above statement?

No.

Running `uname -a` or looking at the contents of `/proc/version` will
only tell you about the _currently running_ _kernel_. There is no
guarantee that a given kernel version maps exactly to any given Debian
release or point-in-time state.

If you want to specify the installation state of a Debian system, you
should specify the point release you're on (from /etc/debian_version
on any modern Debian) and the full _package_ version of any relevant
packages (as reported by e.g. dpkg -l). Note that the package version
may be different from the version reported by a program itself.

A lot of the time, something like "current up-to-date Bookworm" or
"Bookworm per <UTC timestamp>" is sufficiently precise, as long as you
have confirmed that this is actually the case.


>>> sudo dpkg -i linux-image-6.1.0-13-amd64
>>> [...]
>>> Is the above the correct way to install kernels that are not in the official repos?
>> 
>> Not quite, because dpkg -i wants a file path, not a package name
>> (that's for apt/apt-get).
> 
> 2. sudo dpkg -i openvpn_2.6.8-bookworm0_amd64.deb

linux-image-6.1.0-13-amd64 is a package name. (You can check this with
apt-cache show.)

openvpn_2.6.8-bookworm0_amd64.deb is presumably a file name.

"File path" does not necessarily require specifying a directory
component of the path; a bare file name is also a (relative) path.

-- 
Michael Kjörling                     🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) Stella Ashburne <rewefie@gmx.com> - 2023-12-10 13:50 +0100
  Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-10 14:40 +0100
    Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) Stella Ashburne <rewefie@gmx.com> - 2023-12-11 04:40 +0100
      Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) Greg Wooledge <greg@wooledge.org> - 2023-12-11 04:50 +0100
        Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) Stella Ashburne <rewefie@gmx.com> - 2023-12-11 11:30 +0100
      Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-11 08:30 +0100
        Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) Stella Ashburne <rewefie@gmx.com> - 2023-12-11 11:40 +0100
      Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-11 09:30 +0100
  Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-10 14:50 +0100
    Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) Greg Wooledge <greg@wooledge.org> - 2023-12-10 16:10 +0100
      Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) Greg Wooledge <greg@wooledge.org> - 2023-12-10 19:10 +0100
        Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) Stella Ashburne <rewefie@gmx.com> - 2023-12-11 03:30 +0100
      Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) Stella Ashburne <rewefie@gmx.com> - 2023-12-11 03:40 +0100
        Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) Greg Wooledge <greg@wooledge.org> - 2023-12-11 04:30 +0100
          Re: Need clarifications about how to deal with the installed  problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1) Stella Ashburne <rewefie@gmx.com> - 2023-12-11 04:50 +0100
        Release process notes [WAS Re: Need clarifications about how to deal  with the installed problematic kernel, linux-image-6.1.0-14-amd64  (6.1.64-1)] "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-11 08:20 +0100
          Re: Release process notes [WAS  Need clarifications about how to  deal with the installed problematic kernel, linux-image-6.1.0-14-amd64  (6.1.64-1)] Stella Ashburne <rewefie@gmx.com> - 2023-12-11 14:40 +0100
            Re: Release process notes [WAS  Need clarifications about how to  deal with the installed problematic kernel, linux-image-6.1.0-14-amd64  (6.1.64-1)] Greg Wooledge <greg@wooledge.org> - 2023-12-11 15:20 +0100
              Re: Release process notes [WAS  Need clarifications about how to  deal with the installed problematic kernel, linux-image-6.1.0-14-amd64  (6.1.64-1)] Stella Ashburne <rewefie@gmx.com> - 2023-12-11 16:00 +0100

csiph-web