On Mon, Aug 29, 2005 at 09:43:33PM -0700, Steve Langasek wrote: > > > 1) upgrade your kernel > > > 2) dist-upgrade > > > > That doesn't seem terribly elaborate to me? And if people choose not to > > > read, well, they get a failure on dist-upgrade and get to figure it out > > > for themselves, I guess. > > > Will that still apply in the case of a home-rolled kernel? > > Yes, of course. The reason this is such an issue in the first place is > because kernel dependencies are *not* expressed as package dependencies; > instead, udev checks the running kernel version in the preinst. > Thanks for the clarification. > > However, if you have to compile your own kernel, do you upgrade kernel, > > dist-upgrade and then recompile with the new gcc? > > Why? > Becuase I roll my own kernel. If I upgrade the kernel with gcc-3.3 (currently the Sarge default) and then upgrade to Etch (which will have gcc-4.0 for a default) I will run into problems if I decide to add new modules to my kernel. Thus, those with a self-compiled kernel are in a situation where you can a) dist-upgrade without first upgrading the kernel and risk breakage; or b) upgrade the kernel twice. Once before and once after. I suppose that it is possible to build the new kernel inside of a chroot (or sbuild or pbuilder) if kernel-package is being used. I am simply pointing out that there is a potential issue that needs to at least be addressed in the release notes. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto
Attachment:
pgpM89Dwd0Sl3.pgp
Description: PGP signature