So it's that time of year again, where classes are starting, it's time to put the games down, install my favourite Linux distribution and get on with my assignments and work. As always. I generally run Linux for my system, It's a delicate balance for me, Netflix works, has the driver support I need, and even allows me to sync my files to my freely provided OneDrive account by my education institute. I know, I know. I can do this on FreeBSD, though, as far as I'm aware, no app makes use of kqueue to sync my changes to one drive automatically. Though, I can always do it via the web app. Anyways, back to my main point.
Classes had started back up, after a massive summer of playing nothing but games to relax after a successful year in education and meeting all my targets, it was finally time to remove that distraction, pop back Linux back onto my machine and restore my backup. (Though I couldn't decrypt my full system backup on Windows, it just didn't like GPG). So I rush over to the ArchLinux website and grab the latest ISO to copy to my USB drive. Eager to things set up quickly, and get back to my work. Then, nothing but issues happened. (It had only been a month since college finished for the summer mind).
First copy to USB, and no good. Grub errors and won't proceed with the boot, though not unusual, I still had the USB drive in my USB 3.0 port which grub doesn't like for some reason, so again, I plugged it into the USB 2.1 slot, and still the same. I thought "Maybe it's because I copied it when I had it plugged into USB 3.0", so I copied it again. Still no go. No worries, I'll use DD mode to copy it... Again, still no go. Eventually, I switched application, as I had been using UNetbootin at this point. Switching to Rufus worked, I finally had a bootable CD, so I boot up, and I shit you not, the most idiotic thing happened, which I'll get into below.
So my machine starts, as usual, POSTS, as usual, num lock key lights up, I tap F12 to choose my boot device. Take note of the working keyboard here. Eventually, after SystemD worked its magic, I'm automatically logged in as root, I go to start trying to partition my disks, to my surprise, no keyboard. Weird I thought... I've been using Unix since around 2004, no issues with keyboards, but after some more experimentation, I realise it does not jut keyboard, but I have no mouse. Over 14 years without an input issue and I finally get one. I figured it was just a bug with ArchLinux, but after some digging, nearly all distros are having an issue with kernel 4.17 and above plagued with no input.
No input, I don't know about you, but to me, a computer takes input, processes it and generally gives you output. However, these cowboys who managed to sit and read a PDF of how to learn c in 24 hours and are submitting commits to Linux have done it, they've fucked up soo badly, you can't even do what a computer is intended, and that is to give it input.
Reading scourges of posted about how this version is meant to be the best, they've gutted loads of code, and they've tidied it up, it's the best release yet. Though it can't even do a simple thing like take input from a keyboard? What am I mean to do? Install a webcam and wink in morse code to give it input. Stupid. It is. So after all this time, out of the box, a simple USB keyboard doesn't even function on Linux. The same keyboard I've used for many systems.
I downgraded the kernel to 4.16 the one I used a month ago, and keyboard functionality was back, so I knew it was a kernel issue, so somewhere in the last month, they've cocked up soo badly, that keyboard functionality isn't even available out of the box. It was at this point I thought "You know what, f*ck this shit, I'm going back to FreeBSD" and that's what I did. Immediately, out of the box, I was wowed with keyboard functionality. I could tap away, give my machine instructions again, tell that cute little thing precisely what to do. I was in control again at last. Thanks, FreeBSD. I don't even know why I went to Linux in the first place, the ever-changing piece of crap that breaks when an idiot who doesn't understand what basic functionality is needed in a computer system gets to mess with it.
Typically, this wouldn't bother me, but after working for soo many years and this issue is present in the last TWO release, it's not just the latest kernel version, but the last two 4.17 and 4.18, and I even install the testing kernel from ArchLinux repository, and the same thing happened. It's the fact that they've broken it which bothers me, I have no idea what they've done, but imagine a new user, with no experience, trying for the first time. They may assume they are at fault when it's the monkeys spitting out shitty code over at linux.org.
After this little charade, it's safe to say, as much as I love Unix, I will never, ever go back to Linux ever again, it just doesn't have the professional feel that FreeBSD has, management or the solid foundation that it offers.
So it looks like my platform for achieving my studies on is now FreeBSD. So Hey guys.
I apologize for any language, i tried to keep it to a minimum, but this is truly stupid.
Classes had started back up, after a massive summer of playing nothing but games to relax after a successful year in education and meeting all my targets, it was finally time to remove that distraction, pop back Linux back onto my machine and restore my backup. (Though I couldn't decrypt my full system backup on Windows, it just didn't like GPG). So I rush over to the ArchLinux website and grab the latest ISO to copy to my USB drive. Eager to things set up quickly, and get back to my work. Then, nothing but issues happened. (It had only been a month since college finished for the summer mind).
First copy to USB, and no good. Grub errors and won't proceed with the boot, though not unusual, I still had the USB drive in my USB 3.0 port which grub doesn't like for some reason, so again, I plugged it into the USB 2.1 slot, and still the same. I thought "Maybe it's because I copied it when I had it plugged into USB 3.0", so I copied it again. Still no go. No worries, I'll use DD mode to copy it... Again, still no go. Eventually, I switched application, as I had been using UNetbootin at this point. Switching to Rufus worked, I finally had a bootable CD, so I boot up, and I shit you not, the most idiotic thing happened, which I'll get into below.
So my machine starts, as usual, POSTS, as usual, num lock key lights up, I tap F12 to choose my boot device. Take note of the working keyboard here. Eventually, after SystemD worked its magic, I'm automatically logged in as root, I go to start trying to partition my disks, to my surprise, no keyboard. Weird I thought... I've been using Unix since around 2004, no issues with keyboards, but after some more experimentation, I realise it does not jut keyboard, but I have no mouse. Over 14 years without an input issue and I finally get one. I figured it was just a bug with ArchLinux, but after some digging, nearly all distros are having an issue with kernel 4.17 and above plagued with no input.
No input, I don't know about you, but to me, a computer takes input, processes it and generally gives you output. However, these cowboys who managed to sit and read a PDF of how to learn c in 24 hours and are submitting commits to Linux have done it, they've fucked up soo badly, you can't even do what a computer is intended, and that is to give it input.
Reading scourges of posted about how this version is meant to be the best, they've gutted loads of code, and they've tidied it up, it's the best release yet. Though it can't even do a simple thing like take input from a keyboard? What am I mean to do? Install a webcam and wink in morse code to give it input. Stupid. It is. So after all this time, out of the box, a simple USB keyboard doesn't even function on Linux. The same keyboard I've used for many systems.
I downgraded the kernel to 4.16 the one I used a month ago, and keyboard functionality was back, so I knew it was a kernel issue, so somewhere in the last month, they've cocked up soo badly, that keyboard functionality isn't even available out of the box. It was at this point I thought "You know what, f*ck this shit, I'm going back to FreeBSD" and that's what I did. Immediately, out of the box, I was wowed with keyboard functionality. I could tap away, give my machine instructions again, tell that cute little thing precisely what to do. I was in control again at last. Thanks, FreeBSD. I don't even know why I went to Linux in the first place, the ever-changing piece of crap that breaks when an idiot who doesn't understand what basic functionality is needed in a computer system gets to mess with it.
Typically, this wouldn't bother me, but after working for soo many years and this issue is present in the last TWO release, it's not just the latest kernel version, but the last two 4.17 and 4.18, and I even install the testing kernel from ArchLinux repository, and the same thing happened. It's the fact that they've broken it which bothers me, I have no idea what they've done, but imagine a new user, with no experience, trying for the first time. They may assume they are at fault when it's the monkeys spitting out shitty code over at linux.org.
After this little charade, it's safe to say, as much as I love Unix, I will never, ever go back to Linux ever again, it just doesn't have the professional feel that FreeBSD has, management or the solid foundation that it offers.
So it looks like my platform for achieving my studies on is now FreeBSD. So Hey guys.
I apologize for any language, i tried to keep it to a minimum, but this is truly stupid.
