• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2024

help-circle


  • The main concern with old hardware is probably powerdraw/efficiency, depending on how old your PC is, it might not be the best choice. But remember: companies are getting rid of old hardware fairly quickly, they can be a good choice and might be available for dirt cheap or even free.

    I recently replaced my old Synology NAS from 2011 with an old Dell Optiplex 3050 workstation that companies threw away. The system draws almost twice the power (25W) compared to my old synology NAS (which only drew 13W, both with 2 spinning drives), but increase in processing power and flexibility using TrueNAS is very noticable, it allowed me to also replace an old raspberry pi (6W) that only ran pihole.

    So overall, my new home-server is close in power draw to the two devices it replaced, but with an immense increase in performance.







  • I bought a kindle when amazon sold them for a special price of 25 Euro. It’s a cool device for reading books, but I found their UI horrendously cluttered and filled with “suggestions” instead of focusing on the content I already have. I have since jailbroken the device and am using koreader on the device to read my ebooks transfered as epubs via calibre.

    That has the advantage that when I buy DRM-free books in epub format, I am not relying on amazon to properly convert the file to a kindle proprietary format.






  • I don’t think we can count the AUR repository as the “default package” because:

    1. AUR is a community driven project, for users, by users. Repos are not maintained by the Arch team.
    2. Arch user needs to explicitely get out of their way to access and use AUR, it is not enabled by default
    3. AUR repos are not even packages (usually). They are build-instructions. There are specific -bin repos that provide packaged binaries, but that was not the case here, because the emulators license doesn’t allow that.

    The issue here was that stenzek moved the emulator to a source-available license, which does not allow Arch to provide packages in their package repo. So people were using build instructions to build the emulator from source. And when that caused issues because something broke, people came to stenzek for support instead of the person maintaining the build instrucions.