Hacker News Reader

Comment by vid | Hacker News Reader

Someone should tell the author about the great lshw, it lists full details of the system board (and everything else) without having to go to a GUI display.

  azalp
    description: Desktop Computer
    product: B660M AORUS PRO AX DDR4 (Default string)
    vendor: Gigabyte Technology Co., Ltd.
    version: -CF
    serial: Default string
    width: 64 bits
    capabilities: smbios-3.4.0 dmi-3.4.0 smp vsyscall32
    configuration: boot=normal chassis=desktop family=B660 MB sku=Default string uuid=dotdotdot

People posting those CPU and SSD screens shots rather than, say, some linked data that contributes to make a graph to forums has such a deleterious effect on people's ability to reason. I suppose eventually we'll end up screen scraping the screen shots.

View on HN

Also, dmidecode is very handy.

  # dmidecode 3.4
  Getting SMBIOS data from sysfs.
  SMBIOS 2.7 present.

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
          Manufacturer: Dell Inc.
          Product Name: 02##K5
          Version: A01
          Serial Number: /BGK####/CN#######/
          Asset Tag: Not Specified
          Features:
                  Board is a hosting board
                  Board is replaceable
          Location In Chassis: Not Specified
          Chassis Handle: 0x0003
          Type: Motherboard
          Contained Object Handles: 0

This. I generally have few problems with the people I work with one exception is when they start posting screenshots on Slack. If it's some gui and you can't get a good export then I understand the frustration - but this will be a screen shot of terminal.

Why? I mean do you hate the future? Did a month from the present beat you up as a child? Perhaps when you were 10 years old 2 years from now kicked sand in your face and now you're going to punish it. I don't know. But they need to get over it for everyone's sake.

In tech support, I'd frequently get screenshots of a few lines of a terminal window pasted into PowerPoint slides and Word docs — usually via some heavily compressed remote desktop-running-on-another-remote-desktop — with the information I actually needed invariably a few lines higher. My favorite was flash photos of a monitor taken with a non-smartphone from fully airgapped sites, where the turnaround for running a command and getting the output would be at least 5 minutes because the on-site user had to leave the server closet and go down a few halls to get back to a network-connected system, copy the photo off the camera to the computer, and attach it to the ticket.

Eventually I rigged up a tool to automatically pull screenshots from tickets via the ticket system's API, then raise contrast on them with imagemagick and run them through OCR. Some red error text on a black background screencapped through multiple layers of compression might as well not exist, even if it's perfectly readable to the end user, so I'd even done comparisons (that I've since unfortunately lost) of how different command-line OCR tools fared with low-contrast color text, because Tesseract wasn't always the most functional option.

Nice to see hinv finally found its way ;) I agree, those neofetch screenshots are more about desktop GUI and such. They don't cover the hardware enough.

Reply on news.ycombinator.com