1. There was talk about dropping some support for legacy hardware. I figure that this probably includes a lot of "Old World" macs or
-----Original Message----- From: LarryStotler To: olh@suse.de Sent: Fri, 02 Jun 2006 11:49:30 -0400 Subject: Re: [suse-ppc] openSuSE v10.2 goals? There was some talk of dropping support for legacy hardware back when we were working on v10.0. I can't remember what was said, but I don't think that it went anywhere. That's why I said there was talk.....However, I can't see the continued support of machines that won't be physically capable of even runing the installer. The 55/6500 maxes out at 128MB RAM. the 54/6400 maxes at 136MB. Now, the main line desktops and towers do support between 768MB(G3 beige), 1GB(73/75/76/85/9509) and 1.5GB(86/9600). I never do an upgrade to begin with. I just do a fresh install on another drive and then work the kinks out. I've been using SuSE since v5.3 and I've only managed to do like 2 succssful updates. Probably something I was doing wrong, but I just decided to start from scrath from then on. Heck, to get mplayer to compile properly on my 2.4Ghz celeron, I had to go from v10.0(seg faulted, gccv4.02) to v9.3(compiled properly). Of course, on that machine, it will never do anything but re-encode movies and play them, so no big deal, andmplayer isn't exactly the easier program to set up. Wow - a Gig needed to do an upgrade. My first install of SuSE was on a P75 w/ 32MB RAM and ran X. Talk about changes. I don't even have a GB in any of my machines. Most only have 256MB and some even less. And considering that I worl on a lot of computers, I don't see that many with more than 512 either. I hope that work is being done to improve that. Not being a programmer, I only have testing and bug reports to offer..... -----Original Message----- From: Olaf Hering <olh@suse.de> pre-G3
machines.
Who said that? It will likely get harder to install as time passes and YaST+inst-sys gets fatter. Someone has to walk through the code and fix the memleaks, error paths and reduce overall memory consumption. Its a fulltime job. 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. Testing and doing good bugreports early will certainly help to detect breakage early. ___________________________________________________ Try the New Netscape Mail Today! Virtually Spam-Free | More Storage | Import Your Contact List http://mail.netscape.com
Hello, larrystotler@netscape.net wrote:
I never do an upgrade to begin with. I just do a fresh install on another drive and then work the kinks out. Just like me, my earlier experiences were very negative. But 10.0 -> 10.1 went without any trouble on my Pegasos PPC. Heck, to get mplayer to compile properly on my 2.4Ghz celeron, I had to go from v10.0(seg faulted, gccv4.02) to v9.3(compiled properly). Of course, on that machine, it will never do anything but re-encode movies and play them, so no big deal, andmplayer isn't exactly the easier program to set up. First of all, you don't need to compile, packman has it available. Anyway it's strange, I recompiled the packman MPlayer rpm on PPC, and did not have any trouble. But I must admit, that their source rpm includes a good number of gcc4 related patches.
Wow - a Gig needed to do an upgrade.
My Pegasos has just 256MB, and the upgrade went without any trouble. The only thing I did is that I used the 'start_shell' boot parameter, and activated swap before starting up YaST. About 150M of swap was used.
My first install of SuSE was on a P75 w/ 32MB RAM and ran X. S.u.S.E 4.2 on 486 with 16MB of RAM and half of the HDD was dedicated to Linux. That was 150MB, with X, games and Netscape, and plenty of free space :-) Bye,
-- CzP http://peter.czanik.hu/
My main machine is a Dual Xeon 500Mhz Dell. It's still chugging along on v9.2. Quite frankly, other than maybe installing the newer kernel to see if it solves some of my sound problems(SMP is weird. I have IRQs in the 180s), I'm pretty happy with it and don't see much need to upgrade. Mencoder is much fast when recompiled from source. At least 50%.from what I have seen. I'm still not that impressed with the P4s. I'm only getting 13fps xvid 1st pass on this 2.4Celeron Mobile and I get about 10 1st pass on my Xeon(mencoder does not support SMP). My first was v5.3. I THINK I bought just about every version up to 8.1. Never had a high speed connection till then. 5 CDs d/ls SLOW on dial up. Feature bloat is a big gripe of mine. It is irritating to be REQUIRED to install files to support ISDN, bluetooth, etc, when I have never had this hardware and probably never will. I would like to see YaST be able to scan the hardware and then offer to install support for devices that you may have that aren't currently plugged in. It's a waste of HD and memory to have these unneccessary files forced on us. I don't even install OpenOffice. KOffice does just fine for me. -----Original Message----- From: Peter Czanik <pczanik@fang.fa.gau.hu> Just like me, my earlier experiences were very negative. But 10.0 -> 10.1 went without any trouble on my Pegasos PPC. First of all, you don't need to compile, packman has it available. Anyway it's strange, I recompiled the packman MPlayer rpm on PPC, and did not have any trouble. But I must admit, that their source rpm includes a good number of gcc4 related patches. My Pegasos has just 256MB, and the upgrade went without any trouble. The only thing I did is that I used the 'start_shell' boot parameter, and activated swap before starting up YaST. About 150M of swap was used. S.u.S.E 4.2 on 486 with 16MB of RAM and half of the HDD was dedicated to Linux. That was 150MB, with X, games and Netscape, and plenty of free space :-) Bye, ___________________________________________________ Try the New Netscape Mail Today! Virtually Spam-Free | More Storage | Import Your Contact List http://mail.netscape.com
participants (2)
-
larrystotler＠netscape.net -
Peter Czanik