Re: Non-Debian kernel source
> >>>>> "Vittorio" == vdemart <Vittorio> writes:
>
> Vittorio> Hi, I'm using potato with Bunk's 2.4.9 kernel suitably
> Vittorio> compiled for my hardware.
>
> Vittorio> Now I wonder if - according to your very revered opinion
> Vittorio> - it would be reproachable, disgusting to install a
> Vittorio> 2.4.12 (or better the forthcoming 2.4.13) kernel
> Vittorio> downloaded directly from www.kernel.org and compiled in
> Vittorio> the ordinary way make dep clean bzImage .....
>
> Vittorio> I mean: what really is against it?
>
On 17 Oct 2001, Brian Button wrote:
> Nothing at all, other than risk. There have been a few problems with
> 2.4.11 and 2.4.12 as they first came out, but its always been easy to
> go back to a previous kernel. I download the kernel source bz2 from
> kernel.org and follow the instructions in /usr/share/doc/debian/FAQ
> about building kernels with make-kpkg. I've also done it manually as
> you say, with make dep clean bzImage modules modules_install, but
> make-kpkg is *much* easier.
>
> This route will build a .deb for you that will automatically install
> your kernel, update maps, set symlinks, etc. It will even run
> /sbin/lilo for you. Just edit /etc/lilo.conf before you install this
> new package to add a stanza for your new kernel, and everything else
> happens for you.
I second that. All you need to do is run
make-kpkg --**check manpage for appropriate options*** kernel_source
to make a debianised source tree.
Then do
make config
make-kpkg clean
make-kpkg --**check manpage for appropriate options*** kernel_image
One point: use --flavour (on stable) or --add_to_version (on
testing/unstable) to add an extra string to your kernel version, the date
of your compilation for example.
In this way, you can compile several different builds of the same
kernel version without over-writing the modules, which are stored in
/lib/modules/kernel-version-with-any-extra-string. In this way you could
build and boot several builds of the same kernel version.
E.g. if yesterday you did
make-kpkg --add_to_version -2001.10.16
and today you did
make-kpkg --add-to-version -2001.10.17
the modules would be stored in the following two directories:
/lib/modules/2.4.12-2001.10.16
/lib/modules/2.4.12-2001.10.17
whereas if you didn't, they'd be stored in
/lib/modules/2.4.12
and today's modules would overwrite yesterday's.
In case you want to do this using the source directly, then edit the
Makefile in the top level of the kernel source tree and add your extra
string to the variable EXTRAVERSION.
Best regards,
George Karaolides 8, Costakis Pantelides St.,
tel: +35 79 68 08 86 Strovolos,
email: george@karaolides.com Nicosia CY 2057,
web: www.karaolides.com Republic of Cyprus
Reply to: