New Linux Patches Cleanup Code For Running x86 32-bit Kernels On x86_64 CPUs

[schmidtbag]

Caring about 1k lines is like caring about 2000 bytes on your 1 TB drive.

But hey you removed that 2000 byte file and broke the 2 users in the world who still relied on it. Congratulations, time well spent.

If your goal is to save space then yeah, it's stupid. You should be smart enough to know that if you encounter a 2000B file that you have an incentive to delete, saving space isn't the primary objective.

[Weasel]

1K lines isn't an insignificant amount for features that are insignificant today. It's really no different than telling someone to stop eating out every night or to quit smoking cigarettes - sure, the money you save isn't going to buy that hypothetical Ferrari in a few years, and for some the money saved might be a drop in the bucket compared to all other expenses, but for each one of these things you dismiss, they pile up into something noteworthy.

The kernel is full of useless crumbs, that collectively could add up to make a substantial difference. It may not be a good idea for devs to spend time looking for unused cruft but in the even they stumble upon something that isn't used, it should be removed. We can't just let the kernel get infinitely big.

Caring about 1k lines is like caring about 2000 bytes on your 1 TB drive.

But hey you removed that 2000 byte file and broke the 2 users in the world who still relied on it. Congratulations, time well spent.

[schmidtbag]

Only 1k lines of code cleaned up? What a waste of time.

Obviously not worth breaking even 2 users. Like legit just leave the fucking code alone.

1K lines isn't an insignificant amount for features that are insignificant today. It's really no different than telling someone to stop eating out every night or to quit smoking cigarettes - sure, the money you save isn't going to buy that hypothetical Ferrari in a few years, and for some the money saved might be a drop in the bucket compared to all other expenses, but for each one of these things you dismiss, they pile up into something noteworthy.

The kernel is full of useless crumbs, that collectively could add up to make a substantial difference. It may not be a good idea for devs to spend time looking for unused cruft but in the even they stumble upon something that isn't used, it should be removed. We can't just let the kernel get infinitely big.

[billyswong]

I have an old asus t100ta, has to be an 32bit efi

I look up ASUS T100TA. Some of their user manuals in https://www.asus.com/supportonly/t10...lpdesk_manual/ mention how to enable CSM mode for DOS boot. But some of them don't. I don't know if they released 2 different models for different regions or they just thought some people aren't interested in this function.

[Quackdoc]

Why no? Are there really any x86 systems with 32-bit efi but no bios csm in the wild?

I have an old asus t100ta, has to be an 32bit efi

[gotar]

He is such a cringe. Linux kernel should be forked, governed by a democratically elected group of people under an organisation, and developed independently of HIS project.

You bureaucrats always think that bureaucracy solves problems. Go ahead, start such organization right away! You could be CEO, that means something.

[billyswong]

sadly, no go.

Why no? Are there really any x86 systems with 32-bit efi but no bios csm in the wild?

[Phoronos]

I block Weasel the troll.
I don't have time to explain such basic things.

[Weasel]

You are wrong : cleaning up obsolete code is usefull.

How about you start by telling us how useful it was for you? Let's hear it champ.

[Weasel]

What has democracy has to do with this ?

SCIENCE is NOT BASED on DEMOCRACY, it is based on COMPETENCE.

Wrong. Science is based on the SCIENTIFIC METHOD, which is a way of saying VERIFIABLE DATA.

Nobody gives a shit how competent you are if they can't verify your claims independently, then it's not science.