Bug#241497: RFC and status report: Kernel upgrades for woody->sarge upgrades
Hi Carlos, On Mon, Mar 28, 2005 at 01:19:53PM -0500, Carlos O'Donell wrote: > On Thu, Mar 24, 2005 at 02:08:25PM -0800, Steve Langasek wrote: > > On Thu, Mar 24, 2005 at 01:54:38PM +, Matthew Wilcox wrote: > > > On Thu, Mar 24, 2005 at 02:31:55PM +0100, Frank Lichtenheld wrote: > > > > As many of you may know on some machines users will need to install > > > > a current kernel before they will be able to upgrade woody to sarge > > > > (or better: glibc of woody to glibc of sarge). I've tried to use the > > > > available information to provide the needed files for these kernel > > > > upgrades. > > > > To my knowledge the affected machines/architecures are currently > > > > hppa64, sparc sun4m (only some of them) and 80386. > > > It's all hppa machines, not just hppa64. > > Then why does the libc6 preinst say that the minimum kernel is 2.4.17 for > > parisc, and 2.4.19 for parisc64? If this is an error, it will need to be > > reconciled before release. > It is not an error. I submitted the patch. Userspace requires a 32-bit > kernel of atleast 2.4.17, and a 64-bit kernel of atleast 2.4.19. The > 64-bit code has some orthogonal issues that took time to fix. > Both could be made to require 2.4.19, and infact the upstream glibc > patch set the requirement to 2.4.19. Well, requiring 2.4.19 for 32-bit would imply a need for additional upgrade testing; so if it's not actually needed, I think we're best off leaving glibc's preinst the way it is. Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#241497: RFC and status report: Kernel upgrades for woody->sarge upgrades
On Thu, Mar 24, 2005 at 02:08:25PM -0800, Steve Langasek wrote: > On Thu, Mar 24, 2005 at 01:54:38PM +, Matthew Wilcox wrote: > > On Thu, Mar 24, 2005 at 02:31:55PM +0100, Frank Lichtenheld wrote: > > > As many of you may know on some machines users will need to install > > > a current kernel before they will be able to upgrade woody to sarge > > > (or better: glibc of woody to glibc of sarge). I've tried to use the > > > available information to provide the needed files for these kernel > > > upgrades. > > > To my knowledge the affected machines/architecures are currently > > > hppa64, sparc sun4m (only some of them) and 80386. > > > It's all hppa machines, not just hppa64. > > Then why does the libc6 preinst say that the minimum kernel is 2.4.17 for > parisc, and 2.4.19 for parisc64? If this is an error, it will need to be > reconciled before release. It is not an error. I submitted the patch. Userspace requires a 32-bit kernel of atleast 2.4.17, and a 64-bit kernel of atleast 2.4.19. The 64-bit code has some orthogonal issues that took time to fix. Both could be made to require 2.4.19, and infact the upstream glibc patch set the requirement to 2.4.19. c. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#241497: RFC and status report: Kernel upgrades for woody->sarge upgrades
Actualy the SS5 (at least the one I have got here) does have the problem for libc6 version I need a kernel above 2.4.21, and for that kernel I need that libc6 version. - Original Message - From: "Steve Langasek" <[EMAIL PROTECTED]> To: ; Cc: <[EMAIL PROTECTED]> Sent: Thursday, March 24, 2005 11:44 PM Subject: Re: RFC and status report: Kernel upgrades for woody->sarge upgrades -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#241497: RFC and status report: Kernel upgrades for woody->sarge upgrades
On Thu, Mar 24, 2005 at 02:57:35PM +0100, Robin Harmsen wrote: > at this moment I am testing the Debian Installer on a SS5 (sun4m I thougt) > cause I wanted a newer kernel then 2.2.20. but it isn't working very well > I am willing to test this upgrade-kernel to get a beter kernel and be able > to do a woody->sarge upgrade > I think I will start with it right afther I finished my test with the > debian installer and filled in a report > I hope I will be able to help :) To the best of our knowledge, the SS5 is not one of the systems affected by this upgrade issue; only systems using the Cypress chips are known to be affected. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#241497: RFC and status report: Kernel upgrades for woody->sarge upgrades
On Thu, Mar 24, 2005 at 01:54:38PM +, Matthew Wilcox wrote: > On Thu, Mar 24, 2005 at 02:31:55PM +0100, Frank Lichtenheld wrote: > > As many of you may know on some machines users will need to install > > a current kernel before they will be able to upgrade woody to sarge > > (or better: glibc of woody to glibc of sarge). I've tried to use the > > available information to provide the needed files for these kernel > > upgrades. > > To my knowledge the affected machines/architecures are currently > > hppa64, sparc sun4m (only some of them) and 80386. > It's all hppa machines, not just hppa64. Then why does the libc6 preinst say that the minimum kernel is 2.4.17 for parisc, and 2.4.19 for parisc64? If this is an error, it will need to be reconciled before release. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#241497: RFC and status report: Kernel upgrades for woody->sarge upgrades
I installed a minimal basic "stable" installation of Debian (no packages selected with tasksel or dselect) when doing the upgade as stated on http://higgs.djpig.de/upgrade/upgrade-kernel/ via the dpkg method. I first needed to install zlib1g, ash and stat. maby it is better to mention that those need to be installed prior. and there is no mentioning of what to change in silo.conf cause you need to specify the initrd somehow. I added: initrd=1/initrd.img is this correct? afther rebooting I get the following error(s): modprobe: Noting to load ??? Specify at least a module or a wildcard like \* pivot_root: No such file or directory /sbin/init: cannot open dev/console: no such file Kernel panic: Attempted to kill init! - Original Message - From: "Frank Lichtenheld" <[EMAIL PROTECTED]> To: ; ; Cc: <[EMAIL PROTECTED]> Sent: Thursday, March 24, 2005 2:31 PM Subject: RFC and status report: Kernel upgrades for woody->sarge upgrades Hi all. As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. Because of the pain to maintain a kernel backport over the lifetime of sarge we have decided to only offer backports of the needed tools (modutils, module-init-tools and initrd-tools) to use stock sarge kernels on woody. It is planned to upload these files together with some documentation into a upgrade-kernel (or whatever else name the ftpmasters will prefer) directory in the archive. I've prepared the necessary backports and some rudimentary documentation and put it online at http://higgs.djpig.de/upgrade/upgrade-kernel/ We now need people that - test the backports - read/comment on/improve the documentation Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#241497: RFC and status report: Kernel upgrades for woody->sarge upgrades
I installed a minimal basic "stable" installation of Debian (no packages selected with tasksel or dselect) when doing the upgade as stated on http://higgs.djpig.de/upgrade/upgrade-kernel/ via the dpkg method. I first needed to install zlib1g, ash and stat. maby it is better to mention that those need to be installed prior. and there is no mentioning of what to change in silo.conf cause you need to specify the initrd somehow. I added: initrd=1/initrd.img is this correct? afther rebooting I get the following error(s): modprobe: Noting to load ??? Specify at least a module or a wildcard like \* pivot_root: No such file or directory /sbin/init: cannot open dev/console: no such file Kernel panic: Attempted to kill init! - Original Message - From: "Frank Lichtenheld" <[EMAIL PROTECTED]> To: ; ; Cc: <[EMAIL PROTECTED]> Sent: Thursday, March 24, 2005 2:31 PM Subject: RFC and status report: Kernel upgrades for woody->sarge upgrades Hi all. As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. Because of the pain to maintain a kernel backport over the lifetime of sarge we have decided to only offer backports of the needed tools (modutils, module-init-tools and initrd-tools) to use stock sarge kernels on woody. It is planned to upload these files together with some documentation into a upgrade-kernel (or whatever else name the ftpmasters will prefer) directory in the archive. I've prepared the necessary backports and some rudimentary documentation and put it online at http://higgs.djpig.de/upgrade/upgrade-kernel/ We now need people that - test the backports - read/comment on/improve the documentation Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#241497: RFC and status report: Kernel upgrades for woody->sarge upgrades
Hi Matthew, On Thursday, 24 Mar 2005, you wrote: > On Thu, Mar 24, 2005 at 02:31:55PM +0100, Frank Lichtenheld wrote: > > As many of you may know on some machines users will need to install > > a current kernel before they will be able to upgrade woody to sarge > > (or better: glibc of woody to glibc of sarge). I've tried to use the > > available information to provide the needed files for these kernel > > upgrades. > > To my knowledge the affected machines/architecures are currently > > hppa64, sparc sun4m (only some of them) and 80386. > > It's all hppa machines, not just hppa64. IIRC we did some upgrade tests on hppa(32) at the BSP in Frankfurt in November last year and had no problems with that, but i might be wrong. Frank, could you please confirm this, as i recall you and Uli did these tests Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#241497: RFC and status report: Kernel upgrades for woody->sarge upgrades
On Thu, Mar 24, 2005 at 02:31:55PM +0100, Frank Lichtenheld wrote: > As many of you may know on some machines users will need to install > a current kernel before they will be able to upgrade woody to sarge > (or better: glibc of woody to glibc of sarge). I've tried to use the > available information to provide the needed files for these kernel > upgrades. > To my knowledge the affected machines/architecures are currently > hppa64, sparc sun4m (only some of them) and 80386. It's all hppa machines, not just hppa64. > I've prepared the necessary backports and some rudimentary documentation > and put it online at > http://higgs.djpig.de/upgrade/upgrade-kernel/ I'll give it a try now. -- "Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception." -- Mark Twain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#241497: RFC and status report: Kernel upgrades for woody->sarge upgrades
Hi, at this moment I am testing the Debian Installer on a SS5 (sun4m I thougt) cause I wanted a newer kernel then 2.2.20. but it isn't working very well I am willing to test this upgrade-kernel to get a beter kernel and be able to do a woody->sarge upgrade I think I will start with it right afther I finished my test with the debian installer and filled in a report I hope I will be able to help :) Greetings Robin Harmsen [EMAIL PROTECTED] http://www.rharmsen.nl - Original Message - From: "Frank Lichtenheld" <[EMAIL PROTECTED]> To: ; ; Cc: <[EMAIL PROTECTED]> Sent: Thursday, March 24, 2005 2:31 PM Subject: RFC and status report: Kernel upgrades for woody->sarge upgrades Hi all. As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. Because of the pain to maintain a kernel backport over the lifetime of sarge we have decided to only offer backports of the needed tools (modutils, module-init-tools and initrd-tools) to use stock sarge kernels on woody. It is planned to upload these files together with some documentation into a upgrade-kernel (or whatever else name the ftpmasters will prefer) directory in the archive. I've prepared the necessary backports and some rudimentary documentation and put it online at http://higgs.djpig.de/upgrade/upgrade-kernel/ We now need people that - test the backports - read/comment on/improve the documentation Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#241497: RFC and status report: Kernel upgrades for woody->sarge upgrades
Frank Lichtenheld wrote: > Hi all. > > As many of you may know on some machines users will need to install > a current kernel before they will be able to upgrade woody to sarge > (or better: glibc of woody to glibc of sarge). I've tried to use the > available information to provide the needed files for these kernel > upgrades. > To my knowledge the affected machines/architecures are currently > hppa64, sparc sun4m (only some of them) and 80386. JFTR, all mips/mipsel subarchitectures are also affected. For those, however, the sarge kernel without userland backports is good enough, because modules aren't needed for basic system operation. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#241497: RFC and status report: Kernel upgrades for woody->sarge upgrades
Hi all. As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. Because of the pain to maintain a kernel backport over the lifetime of sarge we have decided to only offer backports of the needed tools (modutils, module-init-tools and initrd-tools) to use stock sarge kernels on woody. It is planned to upload these files together with some documentation into a upgrade-kernel (or whatever else name the ftpmasters will prefer) directory in the archive. I've prepared the necessary backports and some rudimentary documentation and put it online at http://higgs.djpig.de/upgrade/upgrade-kernel/ We now need people that - test the backports - read/comment on/improve the documentation Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
