Mark Wagnon wrote:
>
> Jean-Yves F. Barbier wrote:
> >
> > Had the same (under 2.0.36), its because the executable version on CDz is
> > 2.0.36-3, but when you compile, the version number is, by default 1.00.
> > Change your revision number (read man make-dpkg) to a correct value, and
> > remov
On Sat, Jun 12, 1999 at 06:31:40PM -0700, Mark Wagnon wrote:
> Bob Nielsen wrote:
> >
> > The best way I've found around this is to use epochs when compiling my
> > own kernel with make-kpkg:
> >
> > make-kpkg --revision=1:custom.1.0 kernel_image
> >
> > This is discussed in the kernel-package d
Bob Nielsen wrote:
>
> The best way I've found around this is to use epochs when compiling my
> own kernel with make-kpkg:
>
> make-kpkg --revision=1:custom.1.0 kernel_image
>
> This is discussed in the kernel-package docs.
Thanks. Forgive my ignorance, but what are epochs? Hmmm. I'm off to
cha
Jean-Yves F. Barbier wrote:
>
> Had the same (under 2.0.36), its because the executable version on CDz is
> 2.0.36-3, but when you compile, the version number is, by default 1.00.
> Change your revision number (read man make-dpkg) to a correct value, and
> remove
> the original kernel.
Ah, that m
On Sat, Jun 12, 1999 at 12:43:12AM -0700, Mark Wagnon wrote:
> I run apt-get update/upgrade daily. Everytime I do, I'm always prompted
> about replacing my kernel-image. I don't want to cuz I've compiled my
> own. How do I get it to stop? Do I have to go into dselect and put it on
> hold? Or is the
Mark Wagnon wrote:
>
> I run apt-get update/upgrade daily. Everytime I do, I'm always prompted
> about replacing my kernel-image. I don't want to cuz I've compiled my
Had the same (under 2.0.36), its because the executable version on CDz is
2.0.36-3, but when you compile, the version number is, b
6 matches
Mail list logo
