• 1 Post
  • 133 Comments
Joined 10 months ago
cake
Cake day: January 17th, 2024

help-circle





  • glibc’s malloc increases the stacksize of threads depending on the number of cpu cores you have. The JVM might spawn a shitload of threads. That can increase the memory usage outside of the JVMs heap considerably. You could try to run the jvm with tcmalloc (which will replace malloc calls for the spawned process). Also different JVMs bundle different memory allocators. I think Zulu could also improve the situation out of the box. tcmalloc might still help additionally.












  • Offlive account during install works only when you are not connected to the internet from that PC. Maybe also only with Win Pro, not Home.

    The crap you have to disable are all dark patterns and I hope the EU rips them a few more holes.

    “Just update”… I think I went into enough details about what pissed me off in my initial comment.

    Almost every Linux distro would have been: boot the installer, select disk, select meta packages, username, password, done. 10 mins later you have an up to date system with no shady online crap.


  • I remember buying a bunch of old HP ISA 100Mbit NICs to turn an old computer into a router/server combo. Naive as I was I put them all in and nothing worked. Turns out they were all configured to use the same IRQ (since they likely came from independent machines), and that caused them to overwrite each others settings… including the MAC adress. Thankfully I found some nice hacker that worked with these cards before and published a little C tool to rewrite their EEPROMs. I contacted him if he sees a chance to resurrect the cards and that saint indeed hacked the necessary features into his tool so I could rewrite the MAC adresses, change the IRQ one by one and ended up with a working network. Good times.


  • Heh, yeah. I had to fix that earlier this year on another machine, but that one was ooold and went through a bunch of upgrades so I figured it was due to its age (even though I still didn’t get how they could be so lazy to not automate this process as part of the update or … well… slim down the rescue tools again). But then they apparently didn’t even care enough to release a new installer that prevents the issue. So they either don’t give a crap or even do it deliberately to break Win 10 in favor of Win 11. Either case: that’s not what I pay for.