Linked by Leo Spalteholz on Wed 9th Jun 2004 07:59 UTC
I'm sure everyone is sick of reading reviews of Suse 9.1 by now but perhaps this one is a little different. This is not an ordinary review in the sense that I don't provide lots of colourful screenshots, or ramble on endlessly about the included software versions and other trivial things. Written from the point of view of a Debian user trying to switch to an "easier" distribution, I concentrated on how Suse stacks up compared to some of the traditional Debian strengths.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
To everyone who is telling this guy to visit the pacman page, you will see that the number of packages available there is very limited compared to Debain's repositories or Mandrake's contrib and plf repositories.
Mandrake and Debian have always been community oriented distro's while SuSE has always been a business oriented distro. SuSE does not encourage 3rd party software repositories because of the destabilizing effect incorrectly compiled software can have on their products. When customers complain to SuSE's support network that package X isn't working they don't usually mention that they installed package Y which broke X's dependencies.
Instead of putting Apache's directory in /var/www where most distributions put it, Suse puts in /srv/www/htdocs. Ok, fair enough, I can adapt to that.
SuSE is LSB Certified and that means their filestructure follows the defined standards as set in the FHS 2.2.
But sofware installation of stuff that is not on the CDs is a huge pain as are a few major things.
You intend to install non-certified software on a production server at your company.......right, carry on. Do you at least attempt to install these packages to a test server first or are you installing directly to your production server?
By default, it makes all new users part of the same "users" group, which means that all users have read and write access to each other's directories.
The way Yast is structured it requires a group to be pre-existing before a user can be added to it. I don't see a workaround for what you want using Yast. Have you tried writing a bash script for useradd?
<p>But I have also good reasons to believe that apt has SuSe' unofficial blessing: there is a link to apt in Konqueror and this time it is quite remarkable that the component 'base' contains the same identical packages as the official CDs.</p>
Apt4RPM support in SuSE is a result of SuSE's UnitedLinux connection to Connectiva. I doubt that it will ever be fully supported.
For that matter, I don't see what Apt4RPM does that Yast doesn't when you are only installing the RPMs that SuSE officially distributes.