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/)BI
bizdelnick @lemmy.ml
Posts 4
Comments 344
/media or /mnt or anywhere ? Discussion.
  • Technically, no. Until you want to mount something but find /mnt is busy or simply forget about this and mount something there, losing access to previously mounted stuff. The only problem is that you have to remember which mountpoint you use for particular filesystem, while the FHS is designed to avoid this and abstract from physical devices as much as possible.

  • /media or /mnt or anywhere ? Discussion.
  • Why though?

    The filesystem is organized to store data by its type, not by the physical storage. In DOS/Windows you stick to separate "disks", but not in Unix-like OSes. This approach is inconvenient in case of removable media, that's why /media exists. And /mnt is not suited for any particular purpose, just for the case when you need to manually mount some filesystem to perform occasional actions, that normally never happens.

    Just media files, downloads, images , music kinda stuff.

    That's what usually goes to /home/<username>. Maybe mount that device directly to /home? Or, if you want to extend your existent /home partition, use LVM or btrfs to join partitions from various drives. Or mount the partition to some subdirectory of /home/<username>, or even split it and mount its parts to /home/<username>/Downloads, /home/<username>/Movies etc. So you keep the logic of filesystem layout and don't need to remember where you saved some file (in /home/<username>/Downloads or in /whatever-mountpoint-you-use/downloads).

  • Why does nobody here ever recommend Fedora to noobs?
  • And not only did everything “just work” flawlessly, but it’s so much faster and more polished than I ever knew Linux to be!

    Congrats, you are very lucky. But try to survive couple of version upgrades before recommending it to noobs.

  • What programming language ruby, python og javascript?
  • Take a look at Dart+Flutter.

    Python would be OK. Ruby is nearly dead nowadays. JS itself is used rarely, better consider using TS (however I don't recommend using them for anything other than web frontend). Go is a great language but it's unpopular in GUI development.

  • Is it possible to use Linux without the command line?
  • It’s just generally faster to use the terminal if you know what you’re doing.

    It's also true for other distros. Not because they have poor GUI tools but because CLI is faster than GUI if you know what you are doing.

  • what hardware should I buy for storage purposes? what brands?
  • Be careful if you buy a Samsung 8x0 SSD. They have long standing bugs that may cause data loss. They are worked around in the kernel, however you have to ensure that the workaround for your particular model exists in the kernel version you use.

  • Building and distributing binaries
  • Glibc preserves backward compatibility, so if you build against the oldest version you want to support, the resulting binary will work with newer ones.

    However that's definitely not what I recommend to do. Better learn packaging and build native packages for distros you are going to support. OBS can make this a bit easier (if your software is FOSS), but any modern CI will also do the job.

  • The standard backup question
  • What kind of changes? Package installation, removal and configuration? Use apt-mark showmanual to save list of manually installed packages, dpkg --get-selections | grep 'deinstall$' to save list of removed packages, debconf --get-selections to save debconf package settings, backup files that you edited in /etc. This should be enough for restoration, wouldn't take a long time for backup and avoid risk of filesystem inconsistency.

  • preslav.me Interfaces Are Not Meant for That

    It's time to ask ourselves how much abstraction in our Go code really makes sense.

    Interfaces Are Not Meant for That
    0

    Techniques and methods for obtaining access to data protected by linux-based encryption

    0

    Finding unreachable functions with deadcode / Alan Donovan

    go.dev Finding unreachable functions with deadcode - The Go Programming Language

    deadcode is a new command to help identify functions that cannot be called.

    Finding unreachable functions with deadcode - The Go Programming Language
    0

    Markdown code blocks are broken

    What a hell is going on? I expect to see everything inside backticks exactly as I typed, but something happens to ''>" and "&lt;" characters. In the preview everything is fine, but after submitting the post it breaks:

    • "&lt;" → &lt;
    • ">" → >
    • "&lt;&lt;" → &lt;&lt;
    • ">>" → >>
    • "&lt;a>" → ``
    • "&lt;/a>" → ``
    4