Comment 3 for bug 353534
Revision history for this message
| Stefan Bader (smb) wrote Re: dapper->hardy->intrepid upgrade path leaves user with unsupported kernel | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
From the configuration Dapper knew 3 flavours there
- 386 (CONFIG_M486 set)
- 686 (CONFIG_M686 set) and
- k7 (CONFIG_MK7 set)
In Hardy we have
- 386 (CONFIG_M486 set)
- generic (CONFIG_M586 set)
So the one question is, can we selectively move those which can go to 586 to generic and keep the ones who need 486 on the -386 kernel. And also to get the -i386 kernel in Jaunty better in sync with the generic kernel (as the -386 is in ports now). For Jaunty the sync is better but still the -386 kernel is a ports kernel.
-