Blakey might blow a gasket or somesuch



  • updated one of the linux-boxes here @home right now:
    175e0dc9-2b45-4648-8b48-f03f465f10e6-image.png

    huh: mokutil, whatsit?

    man mokutil
    

    36463eab-c751-4248-98d8-f37045759fb9-image.png

    hmm, let's scroll down, there has to be a description or somesuch?
    e62ec512-ea76-404b-8392-550cb1566daf-image.png

    ahh, now this clears any open questions, right? right?

    Doing IT-related shite for 20+ years now but only recently I've come to appreciate https://de.wikipedia.org/wiki/Blinkenlights_(Jargon) which might also be read as "It just works, don't ask why because it might stop and then it's your fault" as my go-to mantra.

    /self-rating: 3/10, am not that proficient in [swearing in English]

    //let's try that in my native language: was zum hupenden Fick bringt mir eine manpage für [frotz] wenn da nur aufgelistet wird welche Parameter [frotz] denn akzeptiert aber nirgendwo auch nur ansatzweise der größere Kontext angesprochen wird?

    Gegenbeispiel:

    man fstab
    

    .. das ist bei einem "Kaltstart" immer noch ziemlich viel ..Gibberish.. aber zumindest ist mehr zu sehen / lesen als ein simpler dump der erkannten / möglichen Parameter und man kann sich weiterhangeln wenn man denn will.

    /end rant


  • Notification Spam Recipient

    German is such a romantic language.



  • @iKnowItsLame fuck all documentation that assumes you already know what it already means.



  • @iKnowItsLame said in Blakey might blow a gasket or somesuch:

    hupenden Fick

    honking fuck.

    I think that translates pretty well.

    E_ADDITIONAL_SWEARING_NOT_FOUND


  • ♿ (Parody)

    @cvi said in Blakey might blow a gasket or somesuch:

    @iKnowItsLame said in Blakey might blow a gasket or somesuch:

    hupenden Fick

    honking fuck.

    I think that translates pretty well.

    E_ADDITIONAL_SWEARING_NOT_FOUND

    Sounds Canadian. 🚎


  • Discourse touched me in a no-no place

    I read that and wondered "WTF is shim and why does it have MOKs?" on the grounds that it's a word often used to indicate a thing used to hackily adapt one system to another. After a little guessing, I got:

    Boot Loader To Chain-Load Signed Boot Loaders Under Secure Boot

    This package provides a minimalist boot loader which allows verifying signatures of other UEFI binaries against either the Secure Boot DB/DBX or against a built-in signature database. Its purpose is to allow a small, infrequently-changing binary to be signed by the UEFI CA, while allowing an OS distributor to revision their main bootloader independently of the CA.

    OK, that makes sense, and Machine Owner Keys make sense there as they're delegates for the having things like Linux kernels and drivers signed by the UEFI CA (which would be a pain). It's about moving roots of trust from being externally-determined (UEFI) to being internally determined (you!), formally decreasing security but definitely increasing usability and possibly also trust.

    The manual page is not particularly good, saying what things do but not why one might care about them. It's about what you get when someone who only knows the code from the inside writes the manual.

    blakeyrat would hate it. But he'd also hate the sort of crappy GUI that those sorts of people would wrap around the outside; it would provide all the options but none of the explanations. Reality seems to shit out that sort of thing over and over.

    https://youtu.be/aZe77wShCbE?si=bUT1QrneB5vzxW-n&start=79&end=88



  • @dkf said in Blakey might blow a gasket or somesuch:

    The manual page is not particularly good, saying what things do but not why one might care about them.

    My experience is that a lot of manpages are written that way, especially when it comes to explaining the possible options for the command. I tend to use them (manpages, that is) to find the options etc. I know exist but don’t quite (or at all) remember what they are, rather than finding out what a given command can actually do for me.



  • @DogsB said in Blakey might blow a gasket or somesuch:

    German is such a romantic language.

    No, it's not, it's a Germanic language.



  • @boomzilla said in Blakey might blow a gasket or somesuch:

    @cvi said in Blakey might blow a gasket or somesuch:

    @iKnowItsLame said in Blakey might blow a gasket or somesuch:

    hupenden Fick

    honking fuck.

    I think that translates pretty well.

    E_ADDITIONAL_SWEARING_NOT_FOUND

    Sounds Canadian. 🚎

    Or @Gąskanian.


  • Java Dev

    Also, better hope your motherboard/computer manufacturer did load all the trusted MOKs to start with and not just the Windows MOKs so it actually does work with Linux too without having to manually add MOKs to the key store. Because whoever designed the EFI command line made it some abomination combining cmd.exe with BSD-isms or something. The syntax and commands are dumb.

    But hey, at least it's not the grub command line. Although I have managed to boot an OS from the command line the experience was... special.



  • @Atazhaia said in Blakey might blow a gasket or somesuch:

    Because whoever designed the EFI command line made it some abomination combining cmd.exe with BSD-isms or something. The syntax and commands are dumb.

    Oh yes. When bcdedit.exe feels nicer than everything efibootmgr offers: :trwtf:

    But hey, at least it's not the grub command line.
    Try to find & install a GUI for Grub, I dare you.
    I sometimes miss the halcyone days where one could write a lilo.conf by memory with en-US as active charset on a DE-keyboard...
    /forgetting to run

    /sbin/lilo
    

    afterwards: not so much.

    Although I have managed to boot an OS from the command line the experience was... special.

    War story from yesteryear:
    had to P2V SCO OpenServer 5.x (+ somePatches running a Progress 9.x-DB /w Patches) from a PentiumPro 180 to a -then recent- ESX / Xeon.
    Difficulty: the old machine had a Mylex ..whatever.. 960 comes to mind (EISA) as boot-disk, the oldest available SCSI-Controller on ESX was a NCRxxx or something which SCO 5.x didn't recognize.

    Solution:

    1. Boot VM from SCO-Install-Disk#1
    2. ..load driver..-Option or something
    3. Insert ..driver-disk.. from a SCO 6.x (or later) -> magic incantations -> driver loads, disks available (!yay!)
      -> Minimal 5.x-install (base OS, Network, telnet; nothing else)
    4. whip up two shell-scripts (basically tar cv... | netcat on the old machine and netcat | tar x .. on the new one) which copied everything except /[b|r]oot over
    5. some more magic incantations re printers
    6. reboot + test: success & open a beer or five ;-)

    Basically https://aplawrence.com/scofaq/ saved the bacon.
    I never found out how to prevent the NIC-crash after ~30 days uptime (up, no errors but nothing got transmitted any more) but a cron-scheduled reboot every 3rd sunday at 0400 "fixed" that too.

    Sweet memories.



  • @iKnowItsLame said in Blakey might blow a gasket or somesuch:

    Mylex

    :triggered: When your coworkers tell you, on your first day on the job, what a 💩 company you've just started working for, believe them.



  • @HardwareGeek said in Blakey might blow a gasket or somesuch:

    When your coworkers tell you, on your first day on the job, what a company you've just started working for, believe them.

    We recent were presented a graph of employee satisfaction from a recent survey. Bar-style plot with the y-axis being split between (essentially) happy/unhappy % of the group in question and the x-axis being subdivided into a few buckets of how long they've been here.

    At a first glance, it's not so bad. 50%-50% on generally unhappy vs. generally happy. Then you realize that the x-axis is essentially log(time at employer). Then you realize that all the "happy" answers are in the 0-3 months and 3-9 months (or whatever) range, and all the "unhappy" ones are in the in the 2-4, 4-N and N+ year brackets.

    Then you realize the person presenting the data, who is also claiming that things aren't that bad -certainly not from what they've seen- is firmly in the 3-9 month bracket.

    Well, statistically speaking, they'll come around soon enough.


  • Java Dev

    @cvi Or they leave and are replaced by new young optimists.



  • @HardwareGeek said in Blakey might blow a gasket or somesuch:

    @iKnowItsLame said in Blakey might blow a gasket or somesuch:

    Mylex

    :triggered: When your coworkers tell you, on your first day on the job, what a 💩 company you've just started working for, believe them.

    Sorry, this one I do not get....

    AFAIR the Mylex weren't so bad (a.k.a. top of the morning, the others are far worse!) then.

    /having to cope with <business process from yesteryear>: umm.. I don't know where you earning the spread on your bread but exactly this "old" shite is my job 'cos the young'uns seem to break everything else every quarter and the one left with the shovel is always me.



  • @iKnowItsLame I'm reluctant to say much outside the Lounge, but not so much business processes as work environment and management-employee interactions. It was by far the most toxic workplace I've ever experienced.


Log in to reply