On Tue, Sep 26, 2000 at 05:58:11AM -0700, Nate Amsden wrote:
> couldn't you just remove the kernel package?
...
> i run my own kernels too but they usually have unique names for the most
> part:
...
I tried that but found that the installation process had not gotten far
enough into things to crea
Quoting Nate Amsden ([EMAIL PROTECTED]):
> couldn't you just remove the kernel package?
There isn't a "kernel" package. There are packages with names like
kernel-package, kernel-image..., kernel-source..., etc.
> apt-get has never(thankfully) touched my kernel(s). i run home brew
> kernels on eve
couldn't you just remove the kernel package?
aphro:/home/aphro# dpkg -l | grep kernel
ii device3dfx 2.3-6 Device driver for 3Dfx boards for 2.x
kernel
ii pciutils 2.1.2-2Linux PCI Utilities (for 2.[123].x
kernels)
ii pump 0.7.3-2Simple DHCP/BOOTP cli
Yeah, but when you do that, you'll have to repeat the process each time you do
an apt-get because your custom kernel is older than the newer.
// joey tsai
:: Kenward Vaughan ::
> I decided I likely had answered my own question. Copied the modules directory
> and modules.conf files, then
I decided I likely had answered my own question. Copied the modules
directory and modules.conf files, then let apt install over my image (after
which the upgrade finished normally). I then immediately reinstalled the
custom over that. Recopied the old files back and was done.
Kenward
On Mon,
I had the same problem. I just did a make-kpkg with "-revision 2:Custom.2" (my
previous custom kernel was "Custom.1") and installed the new custom kernel. I
don't know if this is the "right" or "best" way, but apt is cool now.
// joey tsai
:: Kenward Vaughan ::
> I'm in the middle of
I'm in the middle of a woody upgrade, and discovered that the latest
greatest kernel image has been DL'd and is attemping to overwrite my custom
2.2.17 kernel. I stopped that process when queried about the modules
directory, but apt refuses to continue with the rest of the upgrade.
I used aptitud
7 matches
Mail list logo
