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

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

Is on kbin.social but created this profile on kbin.run during a week-long outage.

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

  • 0 Posts
  • 22 Comments
Joined 28 days ago
cake
Cake day: June 4th, 2024

help-circle





  • palordrolap@kbin.runtolinuxmemes@lemmy.worldbin or bin??
    link
    fedilink
    arrow-up
    39
    arrow-down
    1
    ·
    10 days ago

    I don’t know about that. Non-binary files have been put into bin directories for decades at this point. (Feel free to marvel at the analogy.)

    Delete the contents and it’s not just binaries going to the bit-bucket.

    The joke here is more “Tony Lazuto said to execute these files.”


  • An analogy:

    My Swiss Army knife has a screwdriver on it. It’s nice to have, and I even used it recently.

    It juts out perpendicular to the middle of the knife’s body though, making a literal " |- " shape, so for many applications it’s too awkward for the job.

    I also have a more traditional screwdriver. As and when I come to build a new PC, I don’t think I’ll be using the one on the knife.


  • xterm is a terminal emulator, not a shell. Anything that produces a terminal-compatible text stream can be started as the first program.

    e.g. xterm -e nano, assuming you have the nano editor installed, has no instance of a traditional shell (e.g. bash, zsh) running between the xterm and the editor, but the editor still works.

    You could argue that makes the editor itself a shell of sorts, because it’s interactive and you can do things with it, but it’s still not the xterm that inherits that title.



  • You might have some files hard-linked across directories, or worse (but less likely), there’s a directory hard-link (not supposed to happen) somewhere.

    For the uninitiated, a hard-link is when more than one filename points at the same file data on the disk. This is not the same as a symbolic link. Symbolic links are special files that contain a file or directory name and the OS knows to follow them to that destination. (And they can be used to link to directories safely.)

    Some programs are not hard-link aware and will count a hard-linked file as many times as it sees it through its different names. Likewise they will count the entire contents of a hard-linked directory through each name.

    Programs tend not to be fooled by symlinks because it’s more obvious what’s going on.

    Try running a duplicate file finder. Don’t use it to delete anything, but it might help you determine which directories the files are in and maybe why it’s like that.

    Also back up everything important and arrange for a fsck on next boot. If it’s a hard-linked directory fsck might be able to fix it safely, but it might choose the wrong name to be the main one and remove the other, breaking something. Or remove both. Or it’s something else entirely, which by “fixing” will stabilise the system but might cause some other form data loss.

    That’s all unlikely, but it’s nice to have that backup just in case.


  • This whole saga reminds me of the time I somehow ended up with Windows 9x’s “Recent Documents” feature pointed at the root of a drive, so when I pushed the button to “clear recent documents” it dutifully started deleting all the files on the drive.

    At the time, the “Recent Documents” feature created shortcuts to, as you might guess, recently opened documents and put them in a user folder specifically for that purpose. Clearing them was only supposed to remove the shortcuts.

    Or perhaps more relevantly, that one Steam bash script that could delete things it shouldn’t under some very rare circumstances.



  • There are probably pre-written awk scripts out there that already do what you want, not that I know where they’d be.

    That said, you might be better off using one of the bigger but still fairly commonly installed languages. There’s bound to be things on PyPI (for Python) or CPAN (for Perl) that could be bolted together for example.

    If you’re really lucky there might even be something that covers your whole use-case, but I haven’t checked.


  • Duplication of resources mainly. Bloat upon bloat. Worse, a Flatpak can ignore things that it probably should use on the system, and I’m not sure that’s a good thing.

    Don’t get me wrong, there are supposed “bare metal” installs that duplicate all sorts of things too, and I don’t like it when that happens either. Steam, for example, keeps at least one extra copy of itself as well as a bunch of other things.

    And there’s that Flatpaks an entirely different ecosystem that require their own set of updates.

    I get it. I understand there are benefits. Doesn’t mean I like it.


  • Listen, I don’t even like Flatpaks, but at least they’re multi-platform and non-proprietary.

    But the original poster is probably of the opinion that “pro-consumer” means something that “just works”, and if it’s a walled garden, so what?

    “Why is there barbed wire at the top of that wall?” “Don’t worry about it.”





  • Kind of redundant. Both .zip and .rar store an index of files within the archive and are a bit ‘inside-out’ when it comes what we get from tar.gz.

    That is, ZIP is pretty close to what you’d get if you first gzipped all your files and then put them into a .tar.

    RAR does a little more (if I remember correctly), such as generating a dictionary of common redundancies between files and then uses that knowledge to compress the files individually, but better. Something akin to a .tar file is still the result though.