• 2 Posts
  • 44 Comments
Joined 11 months ago
cake
Cake day: July 23rd, 2023

help-circle










  • Install Linux in a VirtualBox virtual machine to try it out. No change to your existing Windows system is needed.

    Better: install it in a virtual machine on a second hard drive: if you like it and you’re ready to switch, switch to booting the real Linux hard-drive and turn the Windows hard drive into the virtual machine, to use within Linux when you need it.

    If you switch to Linux, this will happen:

    • It’s gonna be tough: it’s a different system, you’re not used to it. Like everything else, it’s hard to change and get used to new things. So realistically expect some learning curve and some pain. It’s normal.

    • If you give it an honest shot but you decide Linux is not for you, you’ll switch back to Windows. You’ll be back to your old normal, but you’ll start to notice how infuriating and spirit-crushing it is a lot more, having been exposed to a non-insane, user-centric OS for a while. And then you’ll be that much sadder in Windows and you’ll wish you had the best of both OSes - which you can’t.

    Just be aware than exposure to a non-Windows OS will probably make you hate Windows more and make your life in Windows ever slightly more miserable, even if you don’t stick to the non-Windows OS.




  • Compiling kernels makes no sense anymore.

    Back in the days - Linux versions 2 and below - the kernel was much less modular, and resources wasn’t as plentiful. So it often made sense to build kernels with the stuff you needed statically compiled for speed, and the rest left out fo save memory and shorten boot time. Not to mention, Lilo (the thing we used before Grub) had limitations with respect to kernel size.

    Nowadays, Grub can load a kernel of any size from anywhere on the disk. There’s plenty enough memory and CPU to leave the kernel core slightly bloated with stuff almost nobody needs with zero practical impact on boot time and memory usage, and most everything else is compiled as modules and loaded as needed - again with next to no boot time or running speed impact.

    If you custom-build a kernel today, you’ll boot a tiny bit faster and it’ll run a tiny bit faster, and you’ll have a tiny bit more free memory - all of which you will never notice. What you will notice however is that kernel updates are a PITA on a regular basis.




  • I had no idea what you’re talking about so I had to look it up 🙂

    I think you’re making assumptions on what I need many serial ports for and it’s nothing like what you think.

    I work for a company that makes measuring instruments that talk serial (RS232, RS422 and UART), we have many variants of our products and I’m tired of plugging and unplugging devices to the same serial ports to test code. Also, I can’t do that remotely when I work from home. So I have many serial ports and all the different devices I need to test my code on regularly are all plugged in and powered at the same time.

    No lighting here 🙂