On Mon, Aug 29, 2005 at 11:35:03PM -0400, Roberto C. Sanchez wrote: > On Mon, Aug 29, 2005 at 07:56:32PM -0700, Steve Langasek wrote:
> > > The kernel is likely going to be upgraded automatically because users will > > > be using the kernel-image-2.6-xxx packages. > > Is that a problem for some reason? > > > So we're going to have another release with a very elaborate upgrade > > > procedure in the release notes (which a lot of users, especially desktop > > > users, don't read anyway)? > > 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. > However, if you have to compile your own kernel, do you upgrade kernel, > dist-upgrade and then recompile with the new gcc? Why? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
