4 ms·

You don't have to blacklist or delete anything if it is not there to begin with, which is the point of OP.

nix23 4y ago
It's kind of crazy, people always say bloat here bloat there, but then come up with blacklisting....ahhh the forgotten "art" of just having the code you need on your machine ;)
- mbreese 4y ago
  I get the sentiment, but there is also something to be said for having a consistent and stable starting configuration. Yes, you might end up removing Bluetooth modules from servers, but you know exactly what the starting kernel config is. When you have completely custom kernels for each server, you’ll spend half of your time just figuring out what the starting configuration is. Compiling kernels is really a lost art that many people have never done. It’s probably best to avoid too much of that in production until it’s absolutely necessary.
  - nix23 4y ago
    >It’s probably best to avoid too much of that in production until it’s absolutely necessary. Well yes, being organized is always important, like a customer of mine wanted all Linux server with GUI and installed all of them as "Desktop-Role" aka preempt-kernel. Gui-Server...bleh..but Customer is King, but i could at least change he's mind about the kernel so Gui-Server-Role it was.
nequo 4y ago
If you blacklist it, it is also not there since it’s not loaded, and you get the added benefit of not having to recompile the kernel every time there’s an update.
- nix23 4y ago
  It's there but not loaded. A slimmed-down kernel make the difference from ~100MB (kernel) + 32MB (Modules) to 2MB (Kernel + Modules), faster load, or for smaller devices, and overall less potential attack surface.
  - cassianoleal 4y ago
    Surely you don't reduce 132Mb of kernel+modules to 2Mb just by disabling bluetooth.
    - deleted 4y ago
      [deleted]
    - nix23 4y ago
      >>A slimmed-down kernel The magic of reading....
      - cassianoleal 4y ago
        I think you're missing my point. By the time you want to slim down the kernel that much, Linux, OpenBSD, FreeBSD, they're not that different. That was not the point of this thread, so back at ya: > The magic of reading....
        nix23 4y ago
        It should be clear that Bluetooth is not 90% of the kernel size...that's why i wrote "slimmed down" which means disable/not-compile everything not needed (like just one of 3 firewalls, filesystems, network-stacks etc). >By the time you want to slim down the kernel that much, Linux, OpenBSD, FreeBSD, they're not that different. Yes, but you don't do that by blacklisting modules right? Because that was your solution ;)
        cassianoleal 4y ago
cassianoleal 4y ago
If you need to rebuild the kernel to disable it, it means it was there to begin with. Otherwise it's just an implementation choice: recompile kernel, or blacklist+delete modules.

It's kind of crazy, people always say bloat here bloat there, but then come up with blacklisting....ahhh the forgotten "art" of just having the code you need on your machine ;)

mbreese 4y ago
I get the sentiment, but there is also something to be said for having a consistent and stable starting configuration. Yes, you might end up removing Bluetooth modules from servers, but you know exactly what the starting kernel config is. When you have completely custom kernels for each server, you’ll spend half of your time just figuring out what the starting configuration is. Compiling kernels is really a lost art that many people have never done. It’s probably best to avoid too much of that in production until it’s absolutely necessary.
- nix23 4y ago
  >It’s probably best to avoid too much of that in production until it’s absolutely necessary. Well yes, being organized is always important, like a customer of mine wanted all Linux server with GUI and installed all of them as "Desktop-Role" aka preempt-kernel. Gui-Server...bleh..but Customer is King, but i could at least change he's mind about the kernel so Gui-Server-Role it was.

nequo 4y ago

If you blacklist it, it is also not there since it’s not loaded, and you get the added benefit of not having to recompile the kernel every time there’s an update.

nix23 4y ago
It's there but not loaded. A slimmed-down kernel make the difference from ~100MB (kernel) + 32MB (Modules) to 2MB (Kernel + Modules), faster load, or for smaller devices, and overall less potential attack surface.
- cassianoleal 4y ago
  Surely you don't reduce 132Mb of kernel+modules to 2Mb just by disabling bluetooth.
  - deleted 4y ago
    [deleted]
  - nix23 4y ago
    >>A slimmed-down kernel The magic of reading....
    - cassianoleal 4y ago
      I think you're missing my point. By the time you want to slim down the kernel that much, Linux, OpenBSD, FreeBSD, they're not that different. That was not the point of this thread, so back at ya: > The magic of reading....
      - nix23 4y ago
        It should be clear that Bluetooth is not 90% of the kernel size...that's why i wrote "slimmed down" which means disable/not-compile everything not needed (like just one of 3 firewalls, filesystems, network-stacks etc). >By the time you want to slim down the kernel that much, Linux, OpenBSD, FreeBSD, they're not that different. Yes, but you don't do that by blacklisting modules right? Because that was your solution ;)
        cassianoleal 4y ago

cassianoleal 4y ago

If you need to rebuild the kernel to disable it, it means it was there to begin with. Otherwise it's just an implementation choice: recompile kernel, or blacklist+delete modules.