make-kpkg

[MaD dUCK <madduck@madduck.net>]

so i am almost down with make-kpkg, and have now set up a local server
with a script so that i only have to type 26 characters on the
terminal, then apt-get update && upgrade at each system to update the
kernel. it's nice.

i have three questions, though:

(1) one thing i don't quite get yet is the revision stuff. i call my
revision numbers "yyyymmdd.x" (like named zone file serial numbers),
but isn't it that make-kpkg should increment the 'x' every single
build? right now, i do

  make-kpkg clean
  make-kpkg --arch_in_name --flavour <machine> --revision yyyymmdd.x
    kernel-image

but that way, i specify the revision everytime. nevertheless,
afterwards, i don't see it stored anywhere, so how should make-kpkg
know the next time, what to increment? also, i have to run make-kpkg
clean everytime since i am compiling for multiple machines. right now
i help myself by setting the revision=`date "+%Y%m%d.%H%M`, which is
perfect, but i'd still like to know how to do it The Right Way (tm).

(2) --arch_in_name   works for the i486 machine, yielding a filename
  kernel-image-2.4.5-embryo-i486_20010628.2129_i386.deb, but
compiling it for either the pentium I, the pentium II, the AMD K6-2,
or the Athlon yields a mere
  kernel-image-2.4.5-seamus_20010628.1453_i386.deb.

What gives?

(3) i use a mixture of stable/unstable/testing. i figure that i have
to compile everything on the lowest common denominator, so i use a
stable machine. but i think that it is bad (performance, security) for
me to run a kernel compiled on stable on a system that runs testing or
unstable. is there a good way to use one system to compile for all
three releases?

martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck
-- 
oxymoron: micro$oft works