The Linux Thread - The Autist's OS of Choice

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
KDE is one of the better examples of Wayland development but that doesn't change the fact that fire needs to be lit under some asses, and that might be the case for 2024 and beyond. Also I wouldn't give into one-sided doomerisms about Xorg being abandoned, "understaffed" does not necessarily mean dead.

I don't know how much water this would carry, being a random Reddit post and all that, but apparently FVWMs maintainer might step in and help with Xorg. OpenBSDs Xenocara seems to address these "security" concerns with X11, so that will be interesting if it becomes the "legacy solution".

1703781360562.png
 
Last edited:
Rsync copies, not moves. Very slow and hard on the drive when moving terabytes of videosm
Why not "cp -al" then delete the source tree?
Or "rsync -av --link-dest=/foo/bar/source /foo/bar/source /foo/bar/dest" and then delete the source tree, or maybe --remove-source-files if you're really trusting.
 
  • Agree
Reactions: pylosurf
Is there anything that speeds this up?
Use MV, as it just updates all of the file path pointers for the files. But it doesn't like to merge directories automatically hence the script
Why not "cp -al" then delete the source tree?
Or "rsync -av --link-dest=/foo/bar/source /foo/bar/source /foo/bar/dest" and then delete the source tree, or maybe --remove-source-files if you're really trusting.
...hardlinks are witchcraft
 
  • Informative
Reactions: Flatline
Use MV, as it just updates all of the file path pointers for the files. But it doesn't like to merge directories automatically hence the script

...hardlinks are witchcraft
I hate to tell you this...
the simplest implementation of "mv" is using hardlinks.
link new directory entry, unlink old one.

These days it's all an incomprehensible kernel function, but it used to be just that simple.
 
  • Horrifying
Reactions: Sperg Coalition
Normally I'd take this opportunity to point out that ZFS supports block cloning, which is perfect for this sort of thing.
But since this particular feature recently turned out to cause massive pool corruption, I'll just shut up about my favourite file system this one time.
 
That sounds awful. Did it affect your own system or were you lucky enough to just read about it?
Nah, I was spared. But it really was a horror scenario. Kernel panics unless the pool was imported read-only, and the only recovery was to copy the data off to another pool and then recreating the original. Pretty big problem for homelabbers, who rarely bother with a backup.
 
Nah, I was spared. But it really was a horror scenario. Kernel panics unless the pool was imported read-only, and the only recovery was to copy the data off to another pool and then recreating the original. Pretty big problem for homelabbers, who rarely bother with a backup.

Yeah, its concerning that there is a lack of adequate testing in place for openzfs.
 
I’m a little torn over Wayland. I like that it has no screen tearing but it doesn’t feel ready.
Bash:
xrandr --output <your output screen> --set TearFree on
A compositor is optional on X11 in this case if you don't care about windows transparency, animations, shadows, etc.
Hell on X11 the compositor can even be a separate application (see xcompmgr, picom, etc.)

Holy shit if this dude manages to actually get this up and running and actually improves X11 (maybe there's a chance for an X12) imagine the salt that wayfags will produce! Shit will be glorious to watch unfold.:story:
 
What should I use for a server?
Depends. Your question is kind of like asking, "What vehicle do I need to drive to town?" Most of them can do it perfectly well, some are ludicrously specialized and can't, but your specific use-case might make one of them somewhat better of an option. If you want stability, you could try Debian. If you want industry-standards-compliance, try CentOS (Edit: isn't it kil?) or Red Hat or whatever they do in Enterprise Land. If you want to suffer every few months when an update needs manual intervention, use Arch.
no
 
Depends. Your question is kind of like asking, "What vehicle do I need to drive to town?" Most of them can do it perfectly well, some are ludicrously specialized and can't, but your specific use-case might make one of them somewhat better of an option. If you want stability, you could try Debian. If you want industry-standards-compliance, try CentOS (Edit: isn't it kil?) or Red Hat or whatever they do in Enterprise Land. If you want to suffer every few months when an update needs manual intervention, use Arch.

no
freetard
 
What should I use for a server?
Something you can stick a lot of drives into if you want a media server, something extremely powerful if you want to do heavy computational tasks, or something cheap and small if you just want to do basic home automation.

If you do want a media server, something with a recent Intel CPU with graphics is ideal as they will have the best video transcoding abilities.
 
  • Like
Reactions: Doctor Neo Cortex
Back