openSuSE v10.2 goals?
What are the goals for the next version? Is this something that is posted on the openSuSE.org site, or is this something that some of us can get into some discussion about. I realized that keeping synched with the main x86 tree is probably the most important, but what kind of PPC specific stuff is planned? 1. There was talk about dropping some support for legacy hardware. I figure that this probably includes a lot of "Old World" macs or pre-G3 machines. 2. What type of restrictions are in place regarding the code? I've seen versions for the x86 like Super/SLICK. Would it be possible to have an informal split to concentrate on older hardware? 3. YaST and the current problems with integrating Zen. What can be done to make it leaner and better? I've only installed v10.1 on my B&W G3, and even then it is text only and doesn't get used due to the video problems I have had(I do have a Rage128 on the way, so hopefully that will be resolved). I can't install it at all on any "Old World" machines. What type of info would be helping to getting this taken care of? Or is it possible to start a v10.1 install by using the v10.0 bootup? I'm going to make every effort to be as involved as I was in the v10.0 process, and hopefully more so. I am not a programmer, but anything I can do to contribute let me know. Thanx ___________________________________________________ Try the New Netscape Mail Today! Virtually Spam-Free | More Storage | Import Your Contact List http://mail.netscape.com
On Wed, May 31, larrystotler@netscape.net wrote:
What are the goals for the next version? Is this something that is posted on the openSuSE.org site, or is this something that some of us can get into some discussion about. I realized that keeping synched with the main x86 tree is probably the most important, but what kind of PPC specific stuff is planned?
Hopefully Pegasos will be supported better in YaST.
1. There was talk about dropping some support for legacy hardware. I figure that this probably includes a lot of "Old World" macs or pre-G3 machines.
Who said that? It will likely get harder to install as time passes and YaST+inst-sys gets fatter.
2. What type of restrictions are in place regarding the code? I've seen versions for the x86 like Super/SLICK. Would it be possible to have an informal split to concentrate on older hardware?
3. YaST and the current problems with integrating Zen. What can be done to make it leaner and better?
Someone has to walk through the code and fix the memleaks, error paths and reduce overall memory consumption. Its a fulltime job.
install it at all on any "Old World" machines. What type of info would be helping to getting this taken care of? Or is it possible to start a v10.1 install by using the v10.0 bootup?
This will not work due to incompatible changes to the inst-sys. An upgrade will take much longer than a fresh install because almost every package calls ldconfig in the postinstall. This reads large parts of the installed system into memory, it really trashes your disk if you have less then a gig of memory.
I'm going to make every effort to be as involved as I was in the v10.0 process, and hopefully more so. I am not a programmer, but anything I can do to contribute let me know.
Testing and doing good bugreports early will certainly help to detect breakage early.
participants (2)
-
larrystotler＠netscape.net -
Olaf Hering