Menu
CONFIG_UNIX=m I know what y and n stand for,but what about m?
222
y = yes (always installed) m = loadable module (can install and uninstall as you wish) n = no (never installed)
A kernel configuration file is used to build a kernel and, on some platforms, a set of loadable kernel modules. A kernel configuration file has a list of kernel options and then a list of devices and device options.
make menuconfig , with a menu-driven user interface, allows the user to choose the features of Linux (and other options) that will be compiled. It is normally invoked using the command make menuconfig ; menuconfig is a target in Linux Makefile.
You can look at /proc/config. gz if you're in luck, it will be there. If you have the kernel source, it's worth having a look at /arch/arm/configs - most Android kernel's I've seen will have the default config for your CPU and you can start from there.
I assume, this refers to the same as the (y,n,m) prompt when running make config; in that case it would be "module".
Note that compiling Unix domain sockets (CONFIG_UNIX) as module is probably not a good idea. A lot of system components and programs depend on them, and some services might fail to start up if the module has not been loaded at that time.
Most functionality in the Linux kernel can either be compiled in ("y") or left out ("n"), and much of it can also be compiled as a loadable module. This makes sense when you don't know for certain whether you will need some feature in the future.
If you compile it as module and it turns out that it is needed, it will work, but until then it will not bloat the kernel.
It does not, however, really make sense to configure Unix domain sockets as a module, because they are needed almost everywhere (e.g. udev will fail to launch at startup).
If you know you will need something anyway, that should be "y", not "m"
53
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
