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
  • 1.06K Comments
Joined 2 years ago
cake
Cake day: August 13th, 2024

help-circle
  • Pipewire is newer and emulates PulseAudio so that it can be used as a drop-in replacement. There’s literally a command called pipewire-pulse related to this.

    It makes me wonder if they really have both installed or are mistaking Pipewire’s emulation for an active PulseAudio installation, and so it’s just Pipewire that’s acting up.

    I’d say reboot, but being in space might be one of those times where that’s a non-starter. In which case, they’re going to have to get their hands dirty unpicking system hooks and trying to reattach them all again as and when Pipewire’s working again, assuming it doesn’t do that automatically.

    I never had a problem with either Pipewire or real PulseAudio back when that was current. I had motherboard sound physically pop, requiring the purchase of a separate sound card, but never a driver issue, so I can’t even imagine what might be going on.


  • At a guess, the counter goes up by fractions of a day internally, but it’s reset by subtracting the integer part, rounded.

    The original version wouldn’t have had the rounding but they “fixed” that after the first time they did a reset and it went to 1 not 0.

    As to why they wouldn’t just set it to zero, well here we have the joke under a microscope and it’s struggling to stay alive. Put the scalpel down.



  • Easy: House cat.

    One of the well-looked-after, non-abused ones, naturally.

    I already know about the monkey’s paw curses for that.

    You have the constant recurrent belief that your owners are not pampering you at all times on purpose. And that they’re basically stupid big kittens who meow all the time and are terrible hunters. And that they control the rain but won’t turn it off for you. And also I don’t like this brand of food any more.

    And hairballs.

    I suppose it’s time I had another nap.

    … but I think I can live with all that.



  • Considering there’s rarely anyone around for me to say anything to, I’d probably let fly a few choice words and then start trying to work out where the next one was going to land and try to be under it.

    That’s assuming you mean nuclear mushroom cloud anyway.

    Other, sufficiently large ordnance also generates mushroom clouds and we’ve recovered from a handful of those before.

    So any research would be trying to find out whether it was nuclear or not.

    I’ve seen Threads. And a whole heap of post-apocalypse stories. I do not want to live in those worlds.




  • I’m going to assume you’re not kidding, in which case, no, I mean the first letter of the command name it was called by.

    There are already commands that do this. For example, on my machine, ex is the head of a symlink chain that leads to the vim text editor’s executable and if I run ex, vim will know that it was started with the name ex and will start in ex mode. ex was an editor that worked in a different way but was vim’s ancestor, so backwards compatibility is built right in for those strange people who love ex, (or have some kind of automation reliance on it being present).

    Usually, the main command has a command line option that achieves the same effect as the special name. Here, vim -e is the less clever way to start vim in ex mode.

    For yes, symlinking the name no to it and then calling that should arguably cause it to print n repeatedly, but it doesn’t, for historical reasons, hence my suggestion to go back in time and make it act differently.

    (None of this touches on the fact that the GNU philosophy wants nothing to do with clever tricks like this. They prefer to compile separate executables for each and every use case. For example, most Linuxes have dir and vdir as variants of the ls command. Their functionality could have been implemented through this symlink trick, but instead there are three near-identical executables taking up space instead.)




  • The two commands are not equivalent. sed 11q prints 11 lines whereas head’s default is 10.

    Personally I would prefer head -11 in this situation as it more clearly indicates, for the sake of the meme, that something is being removed from the head.

    There’s also that head seems to be ever-so-slightly quicker, perhaps proving what we already knew about thinking being quicker than speech.

    TL;DR That’s what she sed?


  • The BeOS command line command set were all borrowed from or based upon Unix and/or Linux (IIRC many were straight from GNU), which is the basis for my comparison.

    The kernel and graphics were all from-scratch and radically different from Linux, sure, but the same could be said of Linux when compared to the original Unix, or any of the BSDs.