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/)W
Posts
3
Comments
393
Joined
3 yr. ago

  • Correction: it has been happening, this one of dozens of instances.

  • Actually that's not even quite it. He refused to say Israel has a right to exist "as a jewish state" and continued with "Israel has a right to exist as an equal state for all". He also refused to say the first thing he would do if he got elected was to go visit Israel.

  • Ah, the proverbial ham sandwich!

  • Ça c'est de l'osti de merde comme on dit ici.

  • I don't know where you are but rear fogs aren't illegal in the rain here and from experience they are nothing but helpful in heavy rain and white out snow. I am always so so sooo glad when someone in front of me is using them when it's absolutely pouring. You really have to not be paying attention not to notice that it's two lights and not three and somehow mistake them for stop lights.

    In fact, Transport Canada recommends using them in fog, rain, or snow.

    Use only if driving in fog, rain or snow as these lights can be confused with stop lights, distracting other drivers.

    https://tc.canada.ca/en/road-transportation/safety-standards-vehicles-tires-child-car-seats/using-your-vehicle-lights-see-be-seen

  • Yes that as well, I love mine and use them a lot. But that's a step above rear running lights. There's no god damn reasons the rear indicators shouldn't be on all the time.

  • I'd rather see mandatory rear running lights. The amount of people who can't be arsed to turn on their lights in bad visibility conditions is too damn high.

  • We're almost twins! Mine was a IIci, did a ton of Hypercard on that thing!

    A lot of SimCity, but also MS Flightsim!

  • I'm young, mine a Macintosh IIci!

  • And you understand that 68 is after 65? They're not getting. Fucked, they're the last ones to be able to afford housing ownership. If the average is 68 that means one side of the bell curve extends well into the generation.

  • The average home buyer in the US 17 years ago was born in 1968. Today? 1968. Yeah excuse me but as an elder millennial, Gen X can mostly fuck right off.

  • and install paths

    And also configs files do in fact get installed by packages. Not all of them, but some do.

    Whether or not they are guaranteed to be there is irrelevantly pedantic.

    So what exactly are you adding to the conversation here?

    This wall of text does sound like it came straight from an LLM. Give me a receipt for turd muffins.

  • Re read their original.messsage. they specifically asked for, and I quote, "install paths". You're going to have to work on reading comprehension before accusing people of being LLMs.

    Meanwhile, every single time they replied they used the command wrong... Provided the wrong value for the arguments. Despite the original instructions. Yeah, it didn't work for them. That's a skills issue.

  • No it does exactly that. The issue is that the config you are looking at was not created by a package.

  • Like I said, it obviously can only track files installed by the package, if the conf was generated by the executable after, or if you created it, the package system cannot know about it.

    Also, you're still using -S wrong. It takes a file path as argument, not a package name. And does the opposite of -L by showing you which installed package, if any, owns an existing file.

  • dpkg -L PACKAGE_NAME does what you want. In my initial reply I mentioned that dpkg -S is the inverse.

  • You're confusing the command again

     
        
     -L, --listfiles package-name...
                   List files installed to your system from package-name.
     -S, --search filename-search-pattern...
                   Search for a filename from installed packages.
    
      

    dpkg -S /my/file/path

    Finds which, installed, package installed the file.

    dpkg -L samba | grep .conf

    Greps through the list of files installed by a given package.

    If the file you want isn't in there then it wasn't installed by the package itself (could be created on the fly by the binary for example), in which case obviously the package system can't track it.

  • dpkg -S requires a full path like the example I gave. dpkg -L samba should work fine. What is the error you got?