[SOLVED] Which kernel do I need to upgrade to to be safe from vulnerabilites?

[Member h2]

Helpful

Up

0

::

Xecure, inxi is in far more isos now than it used to be, but there’s always a very reasonable debate in each distro about what has to be in an iso vs what could be in it, I don’t involve myself in that. My personal feeling is that any distro that caters to newer type users would benefit from including inxi in their iso since then they can always know that when they ask for say, inxi -Fxzy, the user can just type that in and post the rseults. There’s another obvious benefit, if networking is failing, it’s difficult to install inxi to get a network report, lol.

Oh, I almost forgot, I made a HUGE mistake on 3.0, it was simply an oversight, I forgot to make -y alone default to 80 columns width, that really made it harder than it should ever have been for support people, since now they have to learn what inxi version the person has before asking for something like -Fazy, if it’s previous to 3.1.01, -y alone will result in error. I really wish I had not forgotten that. Also, for support people, -y1 is kind of awesome if you want to discover how inxi actually ‘sees’ your system data, since it puts out a dmidecode like key: value pair per line output, indented, so you can easily see what belongs to what.

That came later, -y1 was very hard to implement and required a significant refactor of the entire output logic internally.

I don’t think your old inxi had -Ga full output support, that was added later, just one example of how much stuff changes. Yes, checked, that was added in 3.1.00

pinxi -Gy1a
Graphics:
  Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series]
    vendor: XFX Pine
    driver: radeon
      v: kernel
    bus-ID: 09:00.0
    chip-ID: 1002:68f9
    class-ID: 0300
  Display: x11
    server: X.Org 1.20.11
    compositor: xfwm4
      v: 4.16.1
    driver: 
      loaded: modesetting
    display-ID: :0.0
    screens: 1
    Screen-1: 0 
      s-res: 2560x1024
      s-dpi: 96
      s-size: 677x270mm (26.7x10.6")
      s-diag: 729mm (28.7")
      Monitor-1: DVI-I-1
        res: 1280x1024
        hz: 60
        dpi: 96
        size: 338x270mm (13.3x10.6")
        diag: 433mm (17")
      Monitor-2: VGA-1
        res: 1280x1024
        hz: 60
        dpi: 86
        size: 376x301mm (14.8x11.9")
        diag: 482mm (19")
  OpenGL: 
    renderer: AMD CEDAR (DRM 2.50.0 / 5.10.0-4.3-liquorix-amd64 LLVM 11.0.1)
    v: 3.3 Mesa 20.3.4
    compat-v: 3.1
    direct render: Yes

• This reply was modified 1 year, 9 months ago by h2.
• This reply was modified 1 year, 9 months ago by h2.

inxi system information script (install info) :: inxi git

[Member Xecure]

Helpful

Up

0

::

h2 wrote:

Also, for support people, -y1 is kind of awesome if you want to discover how inxi actually ‘sees’ your system data

Wow, extremely cool! I see myself asking for the -y option more often, to get more graphical information, including monitor dimensions, which we usually never see.

Thanks very much for the info.

About creating a personal repo you mentioned, I was looking for a way to do so for gitlab, and while searching found this article, which should automate package building and repo hosting using gitlab pages.
I don’t know if you can do the same in github (it should be possible), but worst case scenario you could create a gitlab account, mirror your projects from github and set up in gitlab the automatic-packaging-repo, so every time you push a new update to your github hosted inxi project, it will automatically (after a few hours), update the gitlab repo.

• This reply was modified 1 year, 9 months ago by Xecure.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member h2]

Helpful

Up

0

::

Oh, that’s interesting information. Honestly I don’t like github, I only used it initially because googlecode only offered a transfer tool to github when googlecode shutdown, I would have rather used gitlab, but now I use github mainly because it’s what most people have accounts on so odds of issues getting files and noticed are higher. This might work if gitlab supports auto syncs to github, otherwise it would be a pain.

That’s interesting information re auto packaging of project, that might be worth taking a look into, appreciate the tip. The thing with inxi is that quite literally I could package it for Debian Sarge and ALL debian/ubuntu distros that have ever existed since then could use that package, unaltered, except for I assume changes in packaging syntax.

I think I’ll take a look at this, I have off and on thought of making an inxi package, but since it really doesn’t solve any issues for me or most users, I haven’t spent any further time looking into it. The main benefit I could see would be to offer distro packagers a pre-packaged inxi they can always grab without having to do the work themselves.

There’s a fairly prominent distro forum support guy who asks for various inxi features to make his job easier, the -y1 and -Ga were both the results of his suggestions. A lot of subtle and less subtle things have come from his requests over the years.

• This reply was modified 1 year, 9 months ago by h2.
• This reply was modified 1 year, 9 months ago by h2.

inxi system information script (install info) :: inxi git

[Member h2]

Helpful

Up

0

::

-a is –admin, so -Ga is what gives that verbose graphics output. -y is -y80, which is –width 80. My mistake was not making -y be default for 80 columns, which is what most forums should display to avoid horizontal side scrolls, which makes the output really hard to read and scan. -y with no numeric arguments following can only be used if it’s > 3.1.00 inxi, otherwise it will exit with unsupported argument error.

-a triggers various technical and sometimes difficult to explain outputs, for -G, for instance, it’s how xorg itself uses the terms, a ‘display’ is the entire set of ‘screens’, and a ‘screen’ can be 1 more monitors. The screen dimensions are what xorg ‘sees’ when it decides where to put stuff on your desktops, particularly in > 1 monitor settings. –admin options I tend to not try to make too user friendly, and more technically accurate.

• This reply was modified 1 year, 9 months ago by h2.

inxi system information script (install info) :: inxi git

[Author]

Posts