golden45 wrote:Thanks will try liquorix next time ,but you have to remove the former kernel manually.Am I right?thanks john

Nope.

I think what Steveo is saying is that you can install and use the newkernel without removing the former kernel. They'll both be in the "Advanced" menu item under "MX17" if you expand it but the newer one will be on top. If you just click the main "MX17" boot menu item, the default kernel for booting will be latest one.

But if you do WANT to remove the old kernel after ensuring the new one works properly on boot up, then yes, you have to remove it manually. Just that you don't HAVE to.

Ubuntu uses the same packaging management system (deb and apt) and with each development cycle pulls in the latest packages from Debian and then adapts them to Ubuntu specifics and adds more features and patches where necessary. They also push changes back to Debian and often developers are Ubuntu and Debian developers.
It looks to me that packages are worked on by both ubuntu and debian by developers of the systems.thanks john

[red bold text highlighted by me]

The "latest" could mean the latest branch of Debian, beyond what works on MX17's Stretch Branch. So it may not be that the changes that are pushed back are immediately useable by MX17/Stretch.

As I understand it in my non-expert knowledge, the type of package manager and packaging system/format is not the same as having the same version of a package that is created or built using the same system.

It's like if you have the same person wrapping gifts who always wraps presents in shiny red paper and a gold ribbon, and uses the same sized box and folds the wrapping paper in exactly the same way every time, but the contents in the box that he wraps may be different depending who the recipient is.

So both Debian and Ubuntu use the same packaging format, but the stuff that is packed in a .deb file format can be different.

golden45 wrote:Why is gdebi package manager used to by mxlinux if we cannot use it to install deb packages from ubuntu?thanks for replies john

Gdebi will install an Ubuntu package if its list of dependencies are compatible. Mostly they will work, but not always. You have found that some Ubuntu packages won't install at all. Gdebi is keeping you from breaking your system. That is a feature, not a bug. You are on your own if you run an Ubuntu kernel, though they seem to work.

The only way to be certain a package is compatible to build it for our own repo, with tweaks if needed, or get it from a compatible repo such as Debian backports. That's why we had to rebuild the Sid 4.14.13 kernel from source for MX, with tweaks, instead of just putting the Sid debs in our repository.

asqwerth wrote:As I understand it in my non-expert knowledge, the type of package manager and packaging system/format is not the same as having the same version of a package that is created or built using the same system.

It's like if you have the same person wrapping gifts who always wraps presents in shiny red paper and a gold ribbon, and uses the same sized box and folds the wrapping paper in exactly the same way every time, but the contents in the box that he wraps may be different depending who the recipient is.

So both Debian and Ubuntu use the same packaging format, but the stuff that is packed in a .deb file format can be different.

Yes, I can buy brake calipers online, and they come shipped in exactly the same box, but what fits my car will not necessarily fit your car.

By the way, we don't need the wall of text if you just want to show your kernel..."uname -a" will work for that.

still running ubuntu kernel 4.15 will not use liquorix image updates again as I think The ubuntu image kernel and the debain kernels are the same
if I use ukuu to remove older kernels and have had no problemns.I say this after using on both 32 AND 64 BIT SYSYTEMS .thanks john