Some middle-aged guy on the Internet. Seen a lot of it, occasionally regurgitating it, trying to be amusing and informative.

Lurked Digg until v4. Commented on Reddit (same username) until it went full Musk.

Was on kbin.social (dying/dead) and kbin.run (mysteriously vanished). Now here on fedia.io.

Really hoping he hasn’t brought the jinx with him.

Other Adjectives: Neurodivergent; Nerd; Broken; British; Ally; Leftish

  • 0 Posts
  • 143 Comments
Joined 2 years ago
cake
Cake day: August 13th, 2024

help-circle

  • I don’t think we got one that tracked back to lunchtime specifically, and those tend to be slightly less well aligned or frequent anyway, but the one that was being caused by a freight elevator’s motor was a devil to track down before we knew what it was.

    And we may not have found it if the engineer had used the stairs to come back from the basement where the router was. Lazy engineer plus angry motor = DSL died when engineer still present. “It died again! What did you do?” “What did I what now?”


  • Reminds me of when I did DSL customer service. Once every few months we’d get a customer (never the same one twice) calling up saying that their connection was terrible, and when we checked the logs, their connection would dropping at incredibly regular intervals aligned well with human units of time. On the hour (or a few minutes past) every hour, for example, or every 10 minutes.

    We figured, and told them, that it had to be something on a timer causing an EMP or other interference at their end because there ought to be nothing outside their premises acting with such specific regularity.

    The caller usually went away and we’d see the connection stabilise not long after, leaving us none the wiser, but hey, fixed!





  • What I shall take from this:

    Overclock screwdriver labor. - That’s what electric screwdrivers are for, right?

    Thermal paste RAM format. - Intriguing. Tell me more. Is this a new zRAM thing?

    Underclock yourself. - Sound advice. Overwork leads to burnout. Take your time.

    Rebooting legally bottlenecks dial-up warranty - I can’t believe this parses as a sentence and actually makes some kind of sense. I mean, if you’re self-important enough to think it’s worth asking, your ISP will almost certainly say you’re not going to be able to use the internet when you’re rebooting your modem.


  • This was the in the UK over a decade ago, back in the bad old days of migration codes and everything being underpinned by BT Openreach who basically had their arm twisted to allow other ISPs to exist and use that infrastructure. And even then they guarded everything jealously (and sometimes incompetently, but that’s another story).

    We didn’t sell telephone lines, so every DSL we sold was on an existing POTS line that each customer already had. Most of our customers wouldn’t have known about getting a separate POTSless line even if that was possible at the time. And the customer in question certainly didn’t.

    They had it installed on their company’s one and only telecommunications line. Of all the hundreds of customers I dealt with over the years, it only ever happened the once… although we did have to warn at least one other customer off the idea when it happened to come up in conversation.


  • Once upon a time I worked for a company that provided DSL internet.

    One day we got a call from a customer complaining that they had no connection.

    We investigated and discovered that their line had been completely cancelled from under us and ask the customer what happened to their telephone line.

    They said they had set up VoIP on their internet connection, and thus no longer had need of their telephone line and so they cancelled it.

    The telephone line on which we had provisioned their DSL internet…

    “No more hand-written code” sounds to me an awful lot like “we don’t need that telephone line any more”.

    The real shame here is that the fall-out won’t be as sudden and the people who ought to be getting the brunt of it will manage to squirm out of any responsibility.






  • Ctrl+C and Ctrl+V for copy and paste come from non-Unix (I’d say Windows itself, but they may have stolen it from elsewhere), and so it makes sense that those two keys have other special meanings under Unix and its descendants.

    Specifically, they mean “Stop what you’re doing” and “The next character is to be entered without special meaning” in most shells, the most common programs that run, often as the main program, in/on a terminal.

    As such, most terminal emulators in Linux GUIs reserve those keypresses for their Unix-y functions. Most of the good ones move copy and paste to Ctrl+Shift+C and Ctrl+Shift+V instead.

    MS-DOS and Windows command prompts also inherit their use of Ctrl+C from Unix, by way of 86-DOS and CP/M, and were in there long before Microsoft adopted Ctrl+C for copy in a GUI, which is where those other Insert-based keybinds you mention came in.

    For an example of Unix Ctrl+V, try echo hello[Ctrl+V][Ctrl+H]world in a Linux terminal shell and press Enter. You’ll see the command as echo hello^Hworld and when you press Enter, it will display hellworld, because that embedded Ctrl+H is a backspace.



  • What I’ve read just now is what I’d deliberately not gone looking for up to this point in case I found this out.

    Linux and Windows happen to require that the executables that access that information be run with root privileges, but it looks like that’s merely an affectation.

    It seems that any old piece of software, without root or other privileges, can independently run the CPUID instruction that obtains a processor’s serial number.

    I do not like this one bit.



  • I would be very interested to know how they are able to identify a specific CPU. The article speculates but does not answer this question.

    The fact that this is even possible is a security nightmare.


    OK, I’ve done a bit more digging and pieced it together. Acknowledgement to @dual_sport_dork@lemmy.world for prompting me to try (again) to find a command that might do it among other things.

    IMO, this sort of information shouldn’t be in processors in the first place, but apparently it is there and needs admin/root access to, well, access it.

    … and the game in question requires kernel-level anti-cheat, so of course, it has the necessary access.

    The command for Linux is sudo dmidecode -t processor, which dumps a lot of info including an ID field, which is supposedly the CPU’s specific identifier. It can be grepped for or otherwise filtered out.

    My own Ryzen gives 8 hexadecimal pairs, so it’s a 64-bit value.

    I would not know that that was unique to my specific individual processor if I had not been told, but I’ll assume that at least part of it is not unique between Ryzens of the same calibre. (I won’t be posting any of it for comparison, for obvious reasons.)

    So the upshot is, if you don’t want to be identified right down to your CPU, don’t run programs as root if there’s any chance of them phoning home.