I'm just a kernel newbie looking at small issues in my free time, but seeing my name in the shortlog feels very rewarding.
Linux 5.6
111–120 of 153 posts
Re: Linux 5.6
#112Re: Linux 5.6
#113Earlier quoted context omitted.
Yes, I think you're right. In that case, it certainly wasn't the case back when Linux started. Intel and Redhat are the biggest contributors according to the Linux Kernel Development Report from 2017: Intel 10,833 13.1% none 6,819 8.2% Red Hat 5,965 7.2% So, "none", although it's the second biggest category, only accounts for 8.2% of contributions.
A lot of kernel developers hide who pays their bills.
Re: Linux 5.6
#114Earlier quoted context omitted.
> 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.
Sometimes even this fails, what can I say. Ubuntu runs a certification program. I wish there was an independent party certifying hardware for Linux. And they looked into all the details, such as battery discharge triggering ACPI events, 802.11 functions supported by wireless card and things like that.
Not blaming you :D
Re: Linux 5.6
#115Earlier quoted context omitted.
One special thing about exfat is that when it gets corrupted you are screwed.
In difference to ... ?
1: https://en.wikipedia.org/wiki/Journaling_file_system
2: https://en.wikipedia.org/wiki/Copy-on-write#In_computer_stor...
Re: Linux 5.6
#116Earlier 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.
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…
Re: Linux 5.6
#117Re: Linux 5.6
#118Earlier 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!
Re: Linux 5.6
#119I'm just a kernel newbie looking at small issues in my free time, but seeing my name in the shortlog feels very rewarding.
Re: Linux 5.6
#120I hope wireguard improves it’s tooling. It feels a bit crude for me.
If you want to do something like make a point-to-point VPN, then wg-quick is that layer on top. If you want to build a mesh network from endpoints authenticated with a third-party identity provider, you want something like Tailscale. Wireguard is just a low-level building block that handles the crypto in those use cases; making something high-level is left as an exercise to the reader.