Well, at least on my Android 7.1.2 (toybox --version 0.7.1-3125af0e06f4-android) mktemp doesn't recognize the -t option (https://github.com/landley/toybox/blob/0.7.1/toys/lsb/mktemp...). So it seems to be fixed in newer versions, but I am sure there will be some installations with the old versions around for a while.
Instead, I could use --tmpdir, but somehow that one seems to be buggy:
$ mktemp -d --tmpdir name.XXXXXX
mktemp: Failed to create directory name.XXXXXX/name.XXXXXX/tmp.sL2WbI: No such file or directory
The macOS version, on the other hand, does work with those options, but it creates a file like name.XXXXXX.veCNnwkX (instead of name.veCNnwkX) so not a deal-breaker, but it is certainly not what you would have expected. And using --tmpdir with macOS doesn't work either.
So yes, in theory, it shouldn't be too hard but sadly, the reality is often buggy and outdated :-/
Honestly, I sort of looked at it for conventional backup strategy...as in, i wonder if it could work as a replacement for tar-zipping up a directory, etc. But, not sure if the use cases is appropriate.
This is what I mean when I say that tmux config is unintuitive. Ideally there should be one or two directives needed to make this work. It took me weeks to get as far as I did, and I'm still not completely happy with it.
Wait, does that mean that programs like FTP server[0] wont work anymore? I use that very often to transfer files from my file manager to and from my phone (e.g. capture a video).
Or there is a way to bypass that and have access to the underlying FS?
does not seem trivial given the differing permission model, but not impossible either. for fat32 I wonder though if the total absence of permissions allows for that.
Basically, the --dotfiles option was not working with directories so you had to have things that look like this: lazygit/.config/lazygit and now it looks like: lazygit/dot-config/lazygit.
Really a small issue that bugged me forever - shouldn't have made it seem like it was core a problem with stow!
> am meticulous at making sure the structure and filenames are correct before dumping anything new to the library
Me too! General rules of thumb: as long as your content matches the name on https://www.themoviedb.org/ Jellyfin will recognize it and have excellent metadata, posters, etc. Even if you change the filenames later you can re-scan the library and it will be updated to reflect the new names.
Note that the bun install [1] seems to be hosted as an HTML file, not as a text file. I'm not sure to what extent that causes issues, but it seems atypical.
Older thread with people having discussed this that back up my words right up top. I don't have a single issue with KirbyCMS + NTFS, I have distributed back end stuff as I desire, and it just works and has mature documentation.
Instead, I could use --tmpdir, but somehow that one seems to be buggy:
The macOS version, on the other hand, does work with those options, but it creates a file like name.XXXXXX.veCNnwkX (instead of name.veCNnwkX) so not a deal-breaker, but it is certainly not what you would have expected. And using --tmpdir with macOS doesn't work either.So yes, in theory, it shouldn't be too hard but sadly, the reality is often buggy and outdated :-/
reply