Was mich immer nervt ist dass anscheinend niemand der das nutzt sich ueber sowas Gedanken macht, und wenn man das anspricht wird man ausgelacht. Prominentes Beispiel waere Uber - ich hatte die damals nicht genutzt weil einfach klar ist dass die den Taxipreis nur schlagen koennen wenn sie Teile der Taxidienstleistungen nicht bieten, und/oder die Fahrer verhungern lassen. Beides haben sie gemacht - siehe z.B. surge pricing. Taxi hat Befoerderungspflicht und feste Preise.

Essenslieferdienste sind ein anderes Beispiel, da wurde massiv Restauranteigene Inrastruktur zerstoert, und sowohl fuer Kunden als auch Fahrer sind die Bedingungen schlechter. Absolut absehbar, und haette man verhindern koennen wenn man von Anfang an die entsprechenden Dienste vermieden haette. War ich aber auch wieder wohl praktisch der einzige - ich hab die letzten Monate dann doch mal ueber Foodora bestellt weil alles andere jetzt eben weg ist.

I see you're not working in any industry having to deal with Qualcomm.

JBOD relies on an optional SATA extension, which most of your controllers won't have.

That leaves you with RAID in the controller - which is a bad idea, as you don't have much control over what is going on, and recovery if it fails will possibly messy.

We're doing pretty much everything a customer wants. Part of my stuff is for being able to get access to stuff to diagnose/repair it, part is for security consulting (or just for a quick unrelated demo as conversation starter, or to shorten discussions).

I typically carry a GDP pocket 3 with KVM module installed, running Linux.

Additionally I may carry one or several of

• Thinkpad x230, custom firmware, Linux
• Windows on an Arm64 notebook
• MacBook Air M1, MacOS

depending on what I expect to be doing. I also often have a boox epaper tablet for notetaking.

Homepage?

At least my kid remembers quite a few things from that time. She sometimes goes "remember when I was crying so much.." following by an increasingly detailed description of a situation until I do remember. And then she tells me what the issue was back then, which she didn't have the ability to explain yet back then.

Windows NT 3.5 and later NT 4 had C2 security certifications - assuming the system was not connected to a network, and didn't have floppy drives (this was before USB was a thing).

So yeah, his patch may be underwhelming. But the help and credit he got for days or weeks of unpaid work was basically nothing. You may be okay with spending days and only getting credits for the bug report, but I suspect many aren't and will not contribute again after such an experience.

Especially in this particular case the effort is in debugging the problem, not doing the actual fix - which is the bug report, where he got credited for. lkml is not the place for "how I debugged this problem" - that'd be what goes into his blog. And if you look around you'll see a lot of "how I helped solving this problem" kind of blog posts.

This change is so simple that guiding him to do it in a good way would involve fixing it yourself in the explanation - and then you'd not show the code so he can do it himself? That's just silly. If he cares about that he came out of that with quite a bit of experience on how to handle it the next time - and he mentions he even got an (assumed to be starter friendly) other issue suggested if he wants to have code in the kernel.

From the perspective of hiring people he turned this from a "nice work debugging a problem, might be a useful candidate" to "tries getting low quality code merged for vanity reasons, let's avoid that guy"

One small issue that people seem to have, is their unwillingness to talk about core boot or libre boot, but that's a small thing.

It's a major issue for me - currently I'm keeping my old x230 alive, but eventually that'll have to be replaced.

I'm running it with heads, which allows me to do secure boot under my control. I don't really want to have my main notebook without that nowadays.

I don't like any of the current notebook keyboards, so it'll be a "build yourself" project anyway - and the framework mainboard would be nice as they keep the dimensions stable, even though I'm not a fan of some other hardware choices.

The problem is having a competent team to manage your infrastructure. You can do a lot with a handful of people - but you need competences spanning a lot of areas, and finding that is pretty hard.

If you can get a competent team the only advantage cloud still has is the ability to quickly scale up and down - but if there might be a need for that it'd still be better to go hybrid, most on your own hardware, and just the prepared ability to quickly bring up cloud workers if needed. The cost savings of properly doing it yourself are so huge that it still might be cheaper to just have some pre-provisioned standby hardware for that, though.

Without them forcing you to go through their server for user authentication it'd be a thing local to your network - where it wouldn't really matter. Without that stupid requirement you also could just keep unsupported clients running by yourself.

They've been dicks for two decades, just playing a bit nicee doesn't really change anything. If they work properly with open source, and enable proper in kernel drivers for the next decade or so I might consider buying something nvidia.