Obviously SuSE or we wouldn't be using it :-)) Actually, I was a RedHat user from v4.0 to v7.0, I then used a free copy of SuSE Live and had to buy SuSE 7.1 Since then I have noticed some peculiarities, i.e. SuSE runs and compiles KDE stuff with generally no problems, but I have difficulty with gnome apps, especially gnome apps that are not SuSE specific RedHat runs and compiles gnome apps pretty well, but I always had trouble with KDE. Yast2 is pretty good, but so is Linuxconf in RedHat, they both do pretty much the basic configuration well. Obtaining Kernel sources and patches seems easier for RedHat, I tried loading linux-2.4.2 source from ftp.kernel.org & compilling and had some problems with modules etc. I then got the lx_suse_242 source from SuSE and it compiled and installed fine As I was used to RedHat for so long it has taken a fair bit of learning to be able to try and configure SuSE without the aid of Yast. This was pretty easy under RedHat as linuxconf was just a gui for standard config files. Take a look at /etc/rc.config in both distro's to see what I mean. The desktop environment in SuSE is setup streets ahead of RedHat (IMHO). Now I am familiar with SuSE I'll stick with it. The things I would change? Standard configuration files - back to a more basic level IMore commonality between filesystem layout (this goes across all distro's. As a user / developer it would be great if the underlying file system structure was identical across distro's and the distributors concentrated on the configuration tools / environments. Just my 2cents worth. Phil On Monday 07 May 2001 21:49, you wrote:
Hello,
I'm a newbie and just purchased SuSe 7.1 I was wondering if some experienced users could comment on the difference between SuSe and Redhat. Which one is better in terms of support and operation?
Thanks,
Frank Rocco St. Elizabeth Medical Center
"In order to make an apple pie from scratch, you must first create the universe." - Carl Sagan
---------------------------------------- Content-Type: text/html; charset="iso-8859-1"; name="Attachment: 1" Content-Transfer-Encoding: quoted-printable Content-Description: ----------------------------------------