Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)AL
Posts
2
Comments
141
Joined
2 yr. ago

  • Correct. You know how JavaScript is not Java? Same thing. If memory serves me correctly there was a bit of a race to be the next Windows script language between NT4 and 2000 (to replace batch), and it was between VBScript and Kixtart (the former won out).

  • I always found Fedora to be a little unstable for my work use. I switched to CentOS because of that, and that was truly rock solid. I even used CentOS Stream for a while (but switched to Alma and Rocky eventually).

  • What? Modules (drivers) are absolutely updated all the time. What do you mean between major versions? Of the distro or the kernel? The distros generally choose a specific kernel (lts or otherwise) for their release cycle, but to think it's static or that backports isn't a thing isn't true.

  • I kinda get it, but I also feel this going to be yet another 'standards' thing.

    Most config files are here:

    • /etc/
    • /opt/PROG/etc/

    User specific tends to be in:

    • /home/USER/.config/

    And when it comes to Windows, take your pick of the registry hive (HKLM, HKCU, ...the other ones...), Prog Files, Prog Files x86, AppData (Local, Roaming, LocalLow), etc.

    If it's not, it's usually trvial to find the config file from the running process as part of the launch command, or indeed in a softlock from their lsof output.

    But, what if the config is not in a dedicated file? What if the config is read from a database? What if the config is interactively set at launch shudder?

    I get it, the person is asking for it to be explicity pointed out in the documentation/help. However, if it's not documented, then it's probably shitty software - so why would you expect them to follow this rule just for config files?

    I think, inevitably, this actually comes down to sysadmins who don't bother to RTFM but also don't push back on devs/managers when asked to fix something they can't. Also, again, see the XKCD...

  • Very similar here. Smoking buddy at work was turning 40 and was like "If we don't quit now, we never will!" so headed to a random vape shop. Bought a vape for lke £50, was on 1.2mg nicotine strength. First day was fine. 2nd day was tough. 3rd was also tough. 4th day I realised "oh shit, never going back to smoking...I feel fine. I can work with this." So that caused me to panick but then thought ok, bought the same vape as a redundancy (so as to not have to fall back on ciagarettes).

    Then, after 6 months switched to 0.6mg nicotine. 6 months after that, 0.3mg. 3 months after that 0.2mg (put my high school chemistry hat on, figured 10ml 0.3mg + 10ml 0.3mg + 10ml 0.0mg mixed up in a 30ml bottle = 0.2mg per 10ml). 1 month after that 0.1mg, 1 month after that 0.0mg - 1 month later, stopped entirely (you genuinely just start forgetting about it, it's weird).

    Went from 30 cigarettes a day to no nicotine and no vape in 18 months.

  • Assuming you're talking about the firmware on the device and not the firmware distributed with the kernel/distro to interface with the hardware, I would identify a vendor that uploads to the Linux Vendor Firmware Service for their SSDs.