I was attempting to compile my own kernel as a debian package, following
these directions:
https://www.debian.org/releases/jessie/i386/ch08s06.html.en
When I got to the point where it has you run make-kpkg itself, where it
suggests the following command:
# fakeroot make-kpkg --initrd --revision
ibc complains about kernel subversion > 255. Well, my kernel is:
> 2.4.261.01.mrh -> due to policy I've read in man make-kpkg, revision
> number should not contain any hyphen, special characters (only
> alphanumerics + . is allowed).
>
> Well, so I did follo
Hello,
after compiling 2.4.26 kernel I'm in trouble upgrading debian/unstable.
glibc complains about kernel subversion > 255. Well, my kernel is:
2.4.261.01.mrh -> due to policy I've read in man make-kpkg, revision
number should not contain any hyphen, special characters (onl
Am Dienstag, 11. Mai 2004 09:17 schrieb Michal R. Hoffmann:
> of them has the separate directory. The good practice is to save your
> .config files to all of compiled kernels to keep track of what is in the
> kernel you use, for example:
>
> 2.4.26_1.01.mrh_.config
Or you look in /boot. There is
a new kernel it is very reasuring to
be able to rerify whitch is working this way.
why don't you use both (I do):
make-kpkg --revision 1.01.mrh --append-to-version 1.01.mrh kernel_image
gives me my own deb package version, just as adds the same EXTRAVERSION.
This causes also, that I ca
Have read a few kernel build howto amd was wondering is there anything
wrong with just using EXTRAVERSION rather than -revision. It seems
better as you can tell whitch kernel you are using from uname -a. I'me
a bit parinoid and after I install a new kernel it is very reasuring to
be able to
Having heard of people having problems with --append to version and 2.6,
I decided to try with --revision. However, I get undefined references to
cmpxchg in functions tdfx_lock_transfer, tdfx_lock_take, tdfx_lock_free,
tdfx_notifier, radeon_lock_take. I then get error 1 (something to do
with .t
7 matches
Mail list logo
