You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: Other Issues » Unusual kernel defconfigs » 2024-10-26 23:54:46
That is certainly a helpful resource that I may use once I get past the main.
That said, *it is not working as advertised* for localmodconfig.
#2 Re: Other Issues » Unusual kernel defconfigs » 2024-10-25 03:35:59
Well this is disheartening. After running make localmodconfig, which prompted me for about 200 answers via readline (I just hit enter for all) I went and checked, for example, Networking Support. What I saw:
Amateur radio: enabled Yes. I have no such equipment.
Bluetooth: enabled Module. I have no such equipment.
RFSwithc: enabled Yes. I have no wireless.
Device Drivers -> Network Device Support:
- FibreChannel driver support: Enabled yes, I have no such equipment.
- FDDI Driver support: Enabled yes, I have no such equipment.
- HIPPI Driver support: Enabled yes, I have no such equipment.
- Wireless LAN: Everything enabled yes except Texas Instruments.
- ISDN Support: Enabled yes.
Network device support -> Ethernet device support:
- Pretty much every top-level network card driver enabled, despite my machine only having a Realtek 8169.
And so on. While R8169 was enabled as a module, clearly make localmodconfig *is not working as advertised* because at least hundred of things that should clearly be disabled are enabled.
I am tempted to file a bug report, but who with? devuan, debian, or Mr. Torvalds? I can't identify who is responsible for maintaining Kbuild.
I am not enthusiastic about reasearching the majority of the 6000+ kernel options. Surely there is a better way.
#3 Re: Other Issues » Unusual kernel defconfigs » 2024-10-25 01:18:57
Thank you, the localmodconfig target looks promising - except near as I can figure out, you have to have everything that you're ever going to use plugged in and enabled while you run make? A mild hassle, not an impossibility. Shall test.
#4 Other Issues » Unusual kernel defconfigs » 2024-10-24 20:54:59
- peterrooney
- Replies: 9
I'm going through the kernel menuconfig hoping to create a smaller desktop kernel.
Going through and looking at each option, it's striking how often I come across help text that reads like, "If you don't know what this is, it is safe to say no here" - yet it's enabled.
And there's a lot of help text that looks... legacy. Like, KVM. What common off-the-shelf processors nowadays do not support it?
So anyways, the question: is there a straightforward way to turn off the things that don't need enabling except for owning arcane hardware? I get that having gone to the trouble of writing a module might bias an author to suggest it needs to be on by default!
#5 Re: Documentation » HOWTO: Post-Installation Configurations » 2024-06-21 20:51:35
Entirely aside from philisophical issues with sudo,
NEVER EDIT THE SUDOERS FILE DIRECTLY.
instead, read the man page before trying 'EDITOR=/bin/nano visudo` instead. There are ways to set the order of preferred editors. Read the man page because if visudo suspects anything wrong when nano exits, it does not give you choices or reminders, but instead expects you know which keys to press.
Pages: 1
Board footer
