Hi,
Unfortunately, providing the config file, and getting rid of
the psdatabase* files, and also the symlink /Sytem.{map,old} are
features of the unstable kernel-package. Firstly, I think that there
is a dependency on dpkg-dev >= 1.4.0.9, which (if I remember
correctly) is not in 1.3.1
-BEGIN PGP SIGNED MESSAGE-
On Tue, 12 Aug 1997, Peter S Galbraith wrote:
> I see that the Debian `way' of placing kernels is:
>
> /vmlinuz -> boot/vmlinuz-2.0.30
> /boot/vmlinuz-2.0.30
> /boot/psdatabase-2.0.30
> /boot/psdatabase -> /boot/psdatabase-2.0.30
> /boot/System.map-2.0.30
>
>
As a side question... I don't use this package to compile kernels, I
do it by hand the old Slackware way. When I'm done compiling, I simply:
cp /usr/src/linux/arch/i386/boot/zImage /zImage-someName
Somehow, a `map' file also gets created as /boot/map
I then edit lilo.conf, adding an entry for
G'day deb's
Someone (Manoj?) mentioned that the new kernel-package creates
kernel-image deb's that put the kernel config file in /boot. I just
created a kernel-image using the kernel-package that comes in the stable
distribution of debian 1.3.1, and it definitely didn't do this.
Is this a feature
4 matches
Mail list logo
