unsubscribe
********************************************************************************
The information contained in this communication is confidential, may be
attorney-client privileged, may constitute inside information, and is intended
only for the use of the addressee. It is the property of the company of the
sender of this e-mail. Unauthorized use, disclosure, or copying of this
communication or any part thereof is strictly prohibited and may be unlawful.
If you have received this communication in error, please notify us immediately
by return e-mail and destroy this communication and all copies thereof,
including all attachments.
********************************************************************************
Good day,
anyone managed to compile an SMP kernel on an IBM RS6000 machine? Distribution
lists 'default' kernel only.
Tried to compile a kernel myself by installing kernel source and
'kernel-smp-nonsrc' package (found at rpm.pbone.net) but got an error:
[quote]
f50:/usr/src/packages/SPECS # rpmbuild -bb ./kernel-smp.spec
error: Architecture is not included: ppc
[unquote]
Guess I overlooked something pretty simple; this is my first
experience with SuSE, used only Red Hat/Fedora Core before (had no
issues with SMP on this 7025-F50 machine - worked out of the box).
Regards
AlexB
Yeah, but at least we are given the option of removing some things from
the installation. My gripe has more to do with stuff that YaST swears
is a dependency like K-Pilot and all the other crap that isn't needed.
And, it could also be the coder's fault. Operating Systems today are
really a disaster. IMHO, I think that when a program is installed, it
should be installed under a directory like /programs and ALL of it's
files should go in that directory. Ex. - OpenOffice should be
installed in the /programs/openoffice-2.02 directory and all it's files
should be under it. Then, the OS should have a list of al the files
that the program installs, so that when you remove it you don't have to
search for stuff. It's not that hard to do this. It just requires
that programmers be required to follow a strict set of rules. Too many
programmers and especially commercial programs want to install
themselves everywhere. Further, SuSE doesn't use all the standard file
system conventions of the full Linux system. I would like to see more
use of the United Linux or Linux Standard Base specs. Also, a
universal installer is a real need. Having specific RPMs for not only
each distro like Red Hat and SuSE, you have different RPMs for
different versions of the same distro. That's a huge problem and a
great deal of extra work that is really uneccessary. The one advantage
that my friends runing Windows have is that when they get some
software, they know it will install. With Linux, I have to look for
the RPM for my distro and version. And, then if it is not available, I
have to compile from source, which doesn't always work because of
changing dependencies......It's too frustrating for most people.
Sometimes, I wonder why I bother. I would have stuck with OS/2 if they
would have kept it going. It worked, and it worked well.
-----Original Message-----
From: Nathan Moore <nmoore(a)winona.edu>
> memory to have these unneccessary files forced on us. I don't even
> install OpenOffice. KOffice does just fine for me.
I'll second that, vim+LaTeX is just fine for me.
___________________________________________________
Try the New Netscape Mail Today!
Virtually Spam-Free | More Storage | Import Your Contact List
http://mail.netscape.com
-----Original Message-----
From: LarryStotler
To: olh(a)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(a)suse.de>
> 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.
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
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
Hello,
I sent it originally to the openSUSE mailing list, but i was warned,
that some people might read only suse-ppc, so here it is :-) Bye,
CzP
-------- Eredeti üzenet --------
Tárgy: PackMan packages for SUSE Linux 10.1 are ready
Dátum: Wed, 17 May 2006 18:22:52 +0200
Feladó: Peter Czanik <pczanik(a)fang.fa.gau.hu>
Címzett: opensuse(a)opensuse.org
Hello,
I'm glad to announce, that after long days of compiling, testing and
debuging, I put on-line a large number PackMan packages for SUSE Linux
10.1 PPC. For those of you, who don't know it yet: these are the
packages, which make SUSE Linux a lot more useful, but are left out from
the official SUSE release mainly for legal reasons (mp3, divx, DVD
support, etc.), or sometimes newer versions of included packages. More
info on Packman is available at http://packman.links2linux.de
About my recompilation of Packman packages: these are maintained by
different people without a standardized environment. For reproducibility
I used y2pmbuild, and modified sources to compile in this strict,
chrooted environment.
I had to leave out a number of packages:
- some few, special interest packages did not compile, like synfig
animation studio
- requiring lot's of additional work, like haskel development
environment and related packages, as it needs to be bootstrapped on PPC
- x86 binary only, like the official divx drivers, rar support, etc.
For obvious reasons, I could not sign it with SUSE private keys, so the
installer complains, but installs these packages.
As I needed to modify sources and SPEC files, my packages are not yet
integrated with the rest of the PackMan website, mirror system. You can
download them using ftp, from:
ftp://spike.fa.gau.hu/pub/pmppc101/
Which can also be used as an installation source.
Please let me know, if you have any troubles! And of course, remember to
have a lot of fun! (SUSE (tm)) Smile
CzP
