On a similar topic, I notice that if I do a --revision.1.0 and later a
--revision.2.0, that the --revision.1.0 still shows up as being installed.
Is there a way to remove it without causing problems with 2.0, since there
is only one /lib/modules/2.x.x directory? I got arount this by cp'ing the
mod
On Wed, Jan 27, 1999 at 03:43:55PM -0600, Nathan E Norman wrote:
> As someone else suggested, be sure to use the `--revision=foo' option to
> make-kpkg, and that should solve the problem. It's never failed me
> here.
But depending on what you make your --revision, dselect might still
upgrade it.
On Wed, 27 Jan 1999, Nathan E Norman wrote:
: On Wed, 27 Jan 1999, Ed Cogburn wrote:
:
: : Steven Feinstein wrote:
:
: [ snip dselect de-selected my custom kernel ]
:
: : Dselect may have interpreted your kernel as being earlier/older
: : than the one on the CD, and thus did an 'up
It looks like you didn't include the 'revision=' parameter when running
make-kpkg. This should give the kernel you make a unique revision number
which will be higher than the one on the CD and it will not be replaced.
Bob
On 27 Jan 1999, Steven Feinstein wrote:
> Hi,
>
> I've rebuilt the kerne
On Wed, 27 Jan 1999, Ed Cogburn wrote:
: Steven Feinstein wrote:
[ snip dselect de-selected my custom kernel ]
: Dselect may have interpreted your kernel as being earlier/older
: than the one on the CD, and thus did an 'update' automatically.
: In any case, you can use the 'hold' featu
Steven Feinstein wrote:
>
> Hi,
>
> I've rebuilt the kernel (using Debian v2). I created a deb using
> make-kpkg --zImage kernel_image
> and installed the new kernel using dpkg -i.
>
> I rebooted the machine and everything works fine. later, I decided to install
> another package from the main
6 matches
Mail list logo
