I take my shitposts very seriously.

  • 0 Posts
  • 3 Comments
Joined 2 years ago
cake
Cake day: June 24th, 2023

help-circle

  • If you have a specific purpose in mind for the drive, then mounting it statically is probably the easiest solution.

    My setup is:

    • 2 TB NVMe
      • 200 GB partition at /
      • The rest (~1.8 TB) mounted at /games
    • 1 TB SATA SSD mounted at /home
    • 3 TB HDD mounted at /hdd

    /mnt and /media are used differently based on the OS. /mnt is supposed to be used for temporary manual mounts, but you can use it (or a subdirectory) as a permanent mount point. /media is meant to contain mount points for dynamically mounted removable devices, but modern systems generally use /run/media/$USER for that purpose; I would personally avoid it nevertheless.


  • I just simply set up a script to export my Trilium notes

    edit the notes with an external editor, and then you can just re-import the note

    Those two lines right there.

    I value interoperability between software. Using a container format to store plaintext files and metadata introduces an XKCD 927 situation where it’s just another reinvention of the wheel that requires additional software support or a whole other workflow for no real benefit. Why is it necessary, for example, to store plaintext data and the related hierarchical structure in a container format when the same feature is already present in the filesystem with files and directories? It adds unnecessary complexity, roadblocks, and points of failure.

    I’m using QOwnNotes at the moment. If I want to edit a note, for example, using neovim through SSH, all I need to do is navigate to the markdown file and open it. No scripts, no export/import. Only text files, and that is all it ever needs to be.