Yeah right

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

help-circle
  • It’s either Slackware (Linux, no systemd), OpenBSD or NetBSD.

    True story: I install a Red Hat server with a disk shelf with about 12 SAS disk in it. Red Hat has systemd. Everything works fine for a month.

    One (1) disk out of the 12 fails. No biggie. Shutdown the server cleanly. Replace disk. Flip power back on. Rebuild disk config. Simple, right?

    Wrong. You see, systemd is unhappy. It detects a new disk. It has lost a previous disk. And so, it refuses to boot. Period.

    Yes, there are ways out of this. But that was the day I decided systemd was the down of the devil.




  • Once you understand Slackware, you realize it is really simple and stable. It comes with an excellent selection of software in the base install, and does not contain any “surprises”. I have had uptime in the 200-300+ days range on my home server, updates and security patches are quick and painless, etc.

    In other words, it is a Linux optimized for usability and Unix compatibility, not necessarily user friendliness. It assumes you know what you are doing and gets out of your way.





  • How do I configure my Linux, on a laptop, to consume as little battery as possible?

    A bit of context: one of my laptop ran Ubuntu, with acceptable battery drain (up to 3h30 of usage, running desktop applications: Firefox, terminal, vim, etc). This is a high-end laptop: 12 AMD Ryzen + AMD Rembrandt.

    I switched to open use, and now battery drains in one hour, running the exact same applications. Installed tuned, selected power save, tried power top, applied different parameters, etc, but no result: battery still dies after 1h. No improvement at all.

    I am going to investigate on my own, but any help is greatly appreciated.


  • If it’s several python modules, then yes, choose a license and then contact pypi and see if you can distribute your modules through them.

    One very important thing is that you have to make sure everything is ready for distribution: check your project will work (possibly starting with a blank VM), what its dependencies are, that the requirements.txt file is good and operational, that automated tests are available for people to run after installing, etc.

    In other words, the ideal project is not just a question of license but also all the scaffoldings you supply with it.

    Thanks for opening your code!