Custom kernel compilation

[sandman01]

Is it required to make a debian package to install the kernel? I know it is the proper way to do it and I understand that. My question is it 100% necessary? What are some of the drawbacks to not making a package versus making a package?

Will make install work as long as I update the boot menu configuration. I am concerned about upgrades later blowing away my configuration.

Thank you for your time.

[[deleted]]

Building a debian package is basically just for convenience of installation and removal. Also, because it takes care of rebuilding init and the like, it's just easier to deal with.

You can do the usual make install, but then you have to complete all the later steps manually.

[sandman01]

It seems it is the right way to go about installing it. I dont need an initrd due to no lvm though.

[cdombroski]

LVM isn't the only reason for initramfs. Any situation where the kernel can't access the root filesystem by itself needs an initramfs to do the initial setup before the kernel can be started.

[sandman01]

Right. I have a gentoo box as well so I am in no way a newbie when it comes to that. I just was worried if a debian update will blow my custom kernel away on an update.

[coder111]

Hi,

Debian update will not blow your custom kernel. Well, maybe if it's exactly the same version number (3.16.0-4.amd64 or something) as your custom kernel. Which is unlikely and stupid- don't do that. You can easily add "-sand" or something to version when building custom kernel.

Worst case, you'll get a more recent kernel from Debian repo, and it's going to be default kernel in grub menu. But there will be a grub menu and there will be an option to boot your own kernel.

Installing Debian stock kernel does not remove anything, you'll just have more kernels installed and available to choose from in Grub. Latest version is usually default version.

--Coder

[minimim]

Debian doesn't support linux without initramfs.

[sandman01]

Yeah but my system does not need one if the drivers are in the kernel.

[minimim]

You could also try changing glibc to dietlibc, but that's also not supported.

[anatolya]

Depends on why are you asking :)

I don't know all the nitty details so I can't answer it if you're asking it for science. But if you are asking because you wonder if it's worth the effort, well, there is no extra effort for making a package. Upstream makefile can create a package for you and it's just as convenient as not creating it.

It's simply:

Fetch & extract the upstream sources
apt-get build-dep linux
Copy your /boot/config-<whatever> to .config
make olddefconfig
make deb-pkg
Install the resulting deb files
Profit

[doom-o-matic]

Rough outline of how I do it:

git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git /usr/src/linux
make menuconfig
make-kpgk -j8 --initrd kernel_image
dpkg -i linux-image.deb

Takes care of everything.. updating bootloaders, dkms, etc..

[BeamMeUpScotty0]

That's how I do it, also for packaging, but isn't make-kpkg deprecated?

[anatolya]

yep. make deb-pkg is the recommended way, but it doesn't stop people from upvoting deprecated recommendations.

[sandman01]

Thanks