On Wed, 2012-07-11 at 09:04 -0400, Gary Dale wrote: > The reason machine A is not bootable is because a minor hardware change > is capable of doing that with a custom kernel.
+1 I almost exclusively use self-build kernels only, because I need them, but I don't drop too much hardware support, usually I try to use as much of the config of a distro's default kernel as possible. As somebody already mentioned, even on machines where RAM is an issue, there's no need to load all modules. Since compiling a kernel does take a long time, I would like to get rid of stuff I never ever will need, but to get rid of it IMO is too time consuming itself. My way is to copy a distro's kernel config, to patch my kernel, choose my settings (add what is needed and what must be removed) and to run make oldconfig. On disk the needed space can become an issue, when collecting many, many, many kernels, but one or a few kernels shouldn't be an issue. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1342014007.2072.55.camel@precise
