28 Mar 2024 |
0xC0ncord | So things that are critical to the system should generally be built in | 20:34:38 |
0xC0ncord | But that's more just a general rule of thumb | 20:34:51 |
0xC0ncord | It's not super easy to explain since it's situational and depends on both what the feature itself is and what your use case is | 20:35:30 |
igawaasagi007 | I see.. | 20:41:46 |
parona |
- also firmware. if you build in something that requires firmware then you will need to explicitly include that firmware in the kernel. its a manual process and you need to know what you need.
effects gpu drivers and networking
| 20:41:48 |
igawaasagi007 | I appreciate it | 20:41:50 |
parona | * + also firmware. if you build in something that requires firmware then you will need to explicitly include that firmware in the kernel. its a manual process and you need to know what you need.
effects gpu drivers and networking | 20:42:15 |
igawaasagi007 | I guess where I get confused is, some of the application specific Gentoo wiki pages, in the kernel config section, it looks like they always build in the feature needed. | 20:43:02 |
igawaasagi007 | But I suppose that's not mandatory. Like on the wireguard page for example... | 20:43:24 |
0xC0ncord | Yeah it's not mandatory. However there are some features that can only be loaded as a built in and not as a module (things like library code) | 20:43:47 |
igawaasagi007 | They Enable the "Wireguard secure network tunnel" option | 20:43:47 |
igawaasagi007 | By default, that's set as a module | 20:44:02 |
igawaasagi007 | So I'm guessing that really didn't need to be changed | 20:44:14 |
0xC0ncord | My personal rule of thumb for builtins vs modules is: if the feature is something that is critical to my system or is literally built into the hardware (network driver, disk driver, GPU drivers, sound drivers, etc) I will make it a builtin. Anything else I will usually make into a module which will include things like external USB devices or webcams, etc | 20:45:36 |
igawaasagi007 | Ok cool. Thank you | 20:46:00 |
igawaasagi007 | I think in my case as far as file systems go, I am currently using Ext4 so I'll want to build that in.. I can disable basically most other things I've never heard of. But maybe I decide to format some external drive as btrfs... So, I may want to make btrfs a module | 20:47:41 |
0xC0ncord | In reply to @igawaasagi007:matrix.org I think in my case as far as file systems go, I am currently using Ext4 so I'll want to build that in.. I can disable basically most other things I've never heard of. But maybe I decide to format some external drive as btrfs... So, I may want to make btrfs a module That's what I would do personally | 20:48:20 |
igawaasagi007 | Or as another example I have a dual boot with MacOS... So I'll want to set that APFS+ or whatever file system they use as a module too in the event I ever wanted to try and mount that on my Linux system | 20:49:04 |
igawaasagi007 | Idk if that's even an option but just throwing an example out | 20:49:54 |
parona | is there even apfs driver on linux. like in kernel and not fuse | 20:49:59 |
parona | * is there even apfs driver on linux? like in kernel and not via fuse | 20:50:10 |
0xC0ncord | In reply to @parona:matrix.org is there even apfs driver on linux? like in kernel and not via fuse I don't think so but I am not 100% sure | 21:01:49 |
29 Mar 2024 |
haoyi | I migrating to musl-llvm profile | 00:18:45 |
haoyi | * I am migrating to musl-llvm profile | 02:30:30 |
haoyi | * I am migrating to the musl-llvm profile | 02:30:39 |
Shaorin | In reply to @admin:reticentadmin.com I am migrating to the musl-llvm profile sounds fun :) | 03:11:42 |
Shaorin | morning | 03:11:44 |
guntherdw | In reply to @igawaasagi007:matrix.org So I'm guessing that really didn't need to be changed Unless you borked up your system somehow and it's not detecting/loading the module when you need it, no | 03:48:53 |
| tath joined the room. | 06:38:26 |
duc | Hello Immolo | 07:05:55 |