Hey Gang,
I have just finished installing SuSE for the firt time. I am a big Linux fan so it's not my first linux distro. After getting abit miffed with Fedora I decided to try something else out and it so how happens that APC puts a copy of SuSE on tehir DVD. I have been using it for one hour or so; so far so good.
I wanted to get others opinions on this distro. I am aware that it's designed to be user friendly but at the moment i am willing to try any thing.
What's your views on the piece of software?
Learning abit about SuSE
I used Suse a long while ago (Personal 8.0), and thought it was alright. I wasn't happy with the way they bundled things - kde is sorta forced on you. I attempted to install with gnome, and the installation manager forced me to install all kde components anyway, by some sort of dependency thing. So that was kinda lame. Suse's look seems streamlined for kde anyway.
I believe their package manager is called Yast. It was rather easy to find tools that will allow you to convert deb and rpm packages, so no worries there. By now, they probably have native rpm support, but don't quote me on that.
I believe their package manager is called Yast. It was rather easy to find tools that will allow you to convert deb and rpm packages, so no worries there. By now, they probably have native rpm support, but don't quote me on that.
suse uses rpms too, but of course they are suse rpms
and they have the whole yast2 thing which will act a little like other automatic system upgrading things, like apt and so forth. suse's rpms are often similar enough to red hat and mandrake ones (i think suse and RH rpms tend to be more similar than mandrake and RH ones) that you can just use RH rpms in your SUSE system, but sometimes you can't. it's worth checking rpm.pbone.net first for a specific suse rpm of something if you need it i would say.
and they have the whole yast2 thing which will act a little like other automatic system upgrading things, like apt and so forth. suse's rpms are often similar enough to red hat and mandrake ones (i think suse and RH rpms tend to be more similar than mandrake and RH ones) that you can just use RH rpms in your SUSE system, but sometimes you can't. it's worth checking rpm.pbone.net first for a specific suse rpm of something if you need it i would say.
I would not suggest mixing RPMs from SUSE and RedHat/Fedora. In fact I would not even recommend mixing RPMs from differing versions of each distribution. I still prefer to use "apt" (and synaptic if you must) on SUSE. Makes life easier when managing software is done in the same way on all the systems I use (Debian, Fedora/RH, SUSE, etc):
apt for SUSE:
http://linux01.gwdg.de/apt4rpm/
Here's a thread where with more info:
http://voidmain.is-a-geek.net/forums/vi ... .php?t=307
apt for SUSE:
http://linux01.gwdg.de/apt4rpm/
Here's a thread where with more info:
http://voidmain.is-a-geek.net/forums/vi ... .php?t=307
i wouldn't recommend it either, but, it's easier to do it with suse and red hat than with mandrake and red hat, in my experience. often if there's only one rpm available, it's for red hat (the ymessenger rpm for instance, until quite recently) but the red hat rpm simply means it was built on red hat but will work on others.
but no, i wouldn't recommend it as a rule.
but no, i wouldn't recommend it as a rule.
What I do if there isn't an RPM for Red Hat but there is for another platform is grab the SRPM from the other platform and build it for my machine. Very often it's as simple as:
# rpmbuild --rebuild myobscureprogram.src.rpm
Sometimes it takes a little more work to get a compile but if the above is successful you know that the binaries are linked against the versions of libraries you have installed, not against the versions that were installed on the other distro or release of distro that the original binary RPM was built on.
# rpmbuild --rebuild myobscureprogram.src.rpm
Sometimes it takes a little more work to get a compile but if the above is successful you know that the binaries are linked against the versions of libraries you have installed, not against the versions that were installed on the other distro or release of distro that the original binary RPM was built on.
