• 17 Posts
  • 2.01K Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle
  • Yes, exactly.

    Not only is it insanely power hungry and will drive up electric bill, it’s storage and memory limited, and worst of all, 32-bit.

    You wouldn’t be able to run much as far as modern software goes on it, and even then, not for long. You probably won’t even find a working distribution because of the age of the hardware, and the fact that large swaths of 32-bit drivers have been removed from the kernel over the years.

    Just chalk it up to being E-Waste, and take it to someplace that will properly recycle it.



  • Okay, well they were very clear about it, and they have a pro version, so aren’t removing the customizations that exist.

    Secondly, that isn’t a “phone home” bit that you hacked around, it’s literally a header that loads a GitHub badge, and that’s it. It’s part of a lot of open source projects.

    Blocking the DNS of the GitHub host it’s calling back to is sufficient enough for everyone if this is a concern (it’s of no security concern, freal), and you don’t need a fork for this to be fixed. Maintaining a fork is an insane amount of work, and trusting someone who is maintaining a forked repo is WAYYYYYY more risky than just using the official repo, which has thousands of stars, and multitudes of users poking through it’s code.

    I for one would never touch your forked repo without doing a full diff, and I’m not going to worry about doing that every time a release is missed by you, or a fix isn’t upstreamed…yada yada. I would just use the official repo, and block the offending GitHub domain if I found it offensive, which I don’t.

    Know what I mean?





  • This only works for specific mechanical failures, and I’d say about 25% of the time. It works because metal shrinks when cold, and this can sort of let a drive limp along for a short period of time to get small amounts of data off.

    Drive clicking is the drive arm malfunctioning, and I wouldn’t expect the freezer trick to do much if it’s a messed up actuator or something. You already know the drive is bad though, so why not.











  • Affected your user and not the system as a whole, yes.

    If you want to be a hyper technical dick like the other person responded, the old way to refer to the term “userspace” is basically anything that doesn’t affect the kernel, HOWEVER, it is now more commonly used to refer to specific local user settings, yes. The old reference was way before people starting writing things to be hyper-local to individual users, as things are arranged now.


  • It doesn’t have anything to do with the distro. With that many files, you’re torturing the hell out of your disks, and your machine’s memory. Depending on how the code is written, it depends on if this is a filesystem scan of the folders that are then imported to a local db which is looked up to go back and find the found files, or a simple approach which is to just scan the directory every time you go to open something.

    I’d really think about properly organizing your files. If that’s not an option, you can dig into the settings or code and find the hard limits set (probably for a good reason) on the number of files being scanned or imported.