On Tue, May 31, 2005 at 10:30:42PM +0100, Matthew Wilcox wrote: > On Tue, May 31, 2005 at 09:45:13PM +0200, Martin Zobel-Helas wrote: > > One of these things is the upgrade path for machines running with a > > 64bit capable HP PA-Risc CPUs. If a HPPA is running woody with a 64bit > > kernel, a newer kernel than 2.4.17 (woody distri kernel) is needed by > > libc. That's the reason why we provide upgrade kernel. All these things > > are described on the release notes at [1] and [2] we are currently > > working on. > > I keep hearing that 64-bit thing, but I don't understand it. Why are > 32-bit machines OK and 64-bit ones not? My understanding is that the > problem is that libc depends on a very recent kernel version. So the > problem should be the same on 32 and 64 bit. Can you explain?
The libc.preinst wants you to upgrade to 2.4.19-64 if it sees you have a 64-bit kernel. It's not a requirement, glibc still only wants 2.4.17. 64-bit kernels did not have a working signal trampoline and would write 64-bit values to userspace. This was fixed in 2.4.19-64, and enough userspace applications required a good ucontenxt that we thought it a good idea to have the preinst ask you to upgrade. I say "thought" because you have already convinced me that I was wrong in this case. Please don't kick my teeth in... :/ c. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
