Joris Huizer wrote: <!-- snip -->
Most of my actions were the same, but there's one big difference - do you know why this article recommends: make-kpkg -rev Custom.1 kernel_image while the other article I used says: make-kpkg --append-to-version=bla kernel_image
Well, if -rev is the same as --revision, then the chief difference seems to be this:
"--revision" affects the name of the Debian package itself but not the kernel name, so "uname -r" won't show the revision, and it will use the same modules as other revisions of the same version.
"--append-to-version=bla" affects the name of the Debian package itself _and_ the kernel name, so "uname -r" will show up as 2.4.18.bla, and this kernel will have its own set of modules, separate from the default kernel 2.4.18.
The latter might be useful if you want to try out some beta version of a kernel module, with an easy way to reboot back to the old version if it hangs your system. Maybe someone else could give another example?
HTH
-- Cheers!
.~. /V\ // \\ /( )\ ^`~´^ < hugge >
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
