Re: Resolving dependancies.
inthane-chan wrote:
I ran the dpkg command - got a whole bunch 'o spew back...
Yeah, I'll often filter it through grep.
...same version as the old XFree that was on the laptop. I take it all those packages need to be pinned up to the new version.
Well, not pinned. But if there's even the possibility of mixed versions of XFree86 packages, it's worth visually scanning through "dpkg -l" output to catch them. This used to be a problem with old systems based on XFree86 3.3.x that you would try to upgrade to XFree86 4.x. You'd get some packages from the old XFree86 architecture and some from the new, which is not a happy situation.
Anyhow, if you say you somehow got some packages from XFree86 4.2.1 and some from an earlier 4.x release, I believe you, but apt-get ought to catch that. Still, shit happens. Thus the benefit of vgrepping the package list.
Aw, frell - I'm just going to start a new thread, since I'm running into some issues compiling the kernel as well.
You shouldn't have to do this, just to get a 2.4 kernel. Look among the available kernel-image-2.4* packages. There's almost certainly one that meets your needs. On the other hand, if you simply feel like rolling your own, great! Here's the way to do it so that Debian knows about the kernel. (Yes, this is indeed from my Debian Tips file:
To compile kernels and auto-generate .deb packages, install and use the
kernel-package package (which provides the make-kpkg utility).
$ cd /directory/where/you/unpacked/a/kernel/tarball
$ make config | make menuconfig | make xconfig | make oldconfig
$ make-kpkg clean
$ make-kpkg --initrd --revision=custom.1.0 kernel_image
# (as root, or using fakeroot) dpkg -i ../kernel-image-X.XXX_1.0_.deb
Rick Moen
rick@linuxmafia.com
