Earlier quoted context omitted.
> most of the work on Linux kernel nowadays is done by salaried employees. That's been the case for decades, probably since just after Linus released it.
It really depends on how you measure the value of the contributions. Simply looking for lines of code (LOC)? Looking for LOC but without drivers? But even if: is every LOC to be seen as equal contribution?
Linux 5.6
121–130 of 153 posts
Re: Linux 5.6
#122If anyone else - like me - has tried updating the kernel this morning and figured out wifi with an intel card was broken: It seems they broke the iwlwifi driver [1] and here [2] is the patch to fix it. [1] https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.... [2] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.g...
Fedora 32 looks to be on-schedule for an April 21 release, pending release blocking bugs getting fixed up by then; and it will be shipping with Linux 5.6.
Re: Linux 5.6
#123Earlier quoted context omitted.
Glitches like this are very infrequent if you run well chosen hardware. If you run e.g. an all-Intel setup which is a few months old, it's rare. If you are afraid of things getting broken, simply use NixOS. All upgrades can be easily rolled back, and you can freeze updates of some packages, or get packages through different channels with different stability compromises. I prefer to get everything through rolling rele…
> Glitches like this are very infrequent if you run well chosen hardware. 1 point sample here but I never manage to get reliable WiFi on a NUC6i7KYK. Hardware that should be included in the “well known” category.
Re: Linux 5.6
#124Earlier quoted context omitted.
Being worried about the current trajectory of macOS, I’ve been thinking more and more about Linux and imagining how far it must have come since I last used it in the early 2000s. Reading things like this really dampen my enthusiasm for trying Linux again.
Glitches like this are very infrequent if you run well chosen hardware. If you run e.g. an all-Intel setup which is a few months old, it's rare. If you are afraid of things getting broken, simply use NixOS. All upgrades can be easily rolled back, and you can freeze updates of some packages, or get packages through different channels with different stability compromises. I prefer to get everything through rolling rele…
Moreover, I gave up on NixOS the second time around because an update completely hosed my system, including all my rollbacks. Something with XServer broke across all snapshots.
Re: Linux 5.6
#125Earlier quoted context omitted.
If you cannot recommend KDE because "there's always this little bug here or there", you cannot recommend anything. When people prefer Windows over Linux, or macOS over Windows, or Linux over macOS, it's often because they don't want to exchange their well-known set of bugs for an exciting and unknown new set of bugs.
not as simple as that. For example, on debian buster, the Discover search bar doesn't work if used several times; the favorites in the start menu sometimes reappear after being deleted; when I quit kmail by using the windows close button, Kmail complains it exited in an unexpected way, etc. These are not little quirks, these are apparent in a normal daily usage. I use Windows at work and it's past those issues. But y…
The button to install itunes was not working. It threw a very generic error message. And that seemed to be the only way to install itunes (Apple's webpages pointed to Windows store).
Took me hours to find and install an alternative third party itunes installer from random untrusted sources.
Windows, quality-wise, is simply unbearable for me in terms of usability, reliability, performance and UX.
Disclaimer: I have had small contributions to KDE.
Re: Linux 5.6
#126Earlier quoted context omitted.
I recently put Linux on a MacBook Air. It’s the same as it’s ever been - extremely finicky and time consuming to get all your stuff working smoothly. Requires scouring random bug reports, stack overflow etc to find all the little work arounds. This is for what I consider critical stuff: network drivers, suspend/sleep, power management, display brightness etc. My impression is that it is not any more or less of a mess…
What MacBook Air version?
It’s mid-2012 model. Core 2 cpu with Broadcom 43xx
Re: Linux 5.6
#127Earlier quoted context omitted.
Finding where to start was the precise issue I looked to solve by setting up that issue tracker. And by being patient, leaving low hanging fruit, taking the time to file issues (explain, demonstrate, guide, enable), we've been able to help many people including yourself make their first contributions to Linux and LLVM. I'm proud of you, Ilie!
Honestly, probably the hardest part of Open source ATM. Contributing to a project is, frankly, super intimidating. Doubly so when it is something as important as the Kernel.
Sink or swim!
Re: Linux 5.6
#128Upgraded to a system with an X570 motherboard and an RX 5700 XT graphics card... for the most part, since Kernel 5.3, every release has been more stable and mostly better performing... though having to manually download drivers a couple times from the kernel git repo has been a pain, I really appreciate the effort. ----- Rant ahead... If only the front end could button up more... Gnome's blank screen + password seems…
Re: Linux 5.6
#129I definitely appreciate how Linus mentioned his daughter identified him as a "social distancing champ" - many of us developers have been practising social distancing long before anyone heard of COVID-19 ;-)
I would even argue that we invented the internet to solve exactly that problem, keeping our distance from other meatbags :-)
Re: Linux 5.6
#130Earlier quoted context omitted.
I only did some small fixes for building the kernel with the clang compiler. Probably the most confusing thing when getting started is finding something to work on. There's no real centralized issue tracker/TODO list/ideas list - discussion happens mostly in mailing lists [0][1] for specific topics. If you follow the discussion on YOUR_FAVORITE_TOPIC long enough you should be able to find easy work items, people able…
Finding where to start was the precise issue I looked to solve by setting up that issue tracker. And by being patient, leaving low hanging fruit, taking the time to file issues (explain, demonstrate, guide, enable), we've been able to help many people including yourself make their first contributions to Linux and LLVM. I'm proud of you, Ilie!