Please next time let's do a bit more trials. And I believe the changes made to the configuration files needs to be coordinated with most GPL software out there.
Most GPLed software is already on the SuSE disks. They work. The major thing is to get things to work with non-GPLed programs, and a lot of those in the past has been prepared for redhat systems only. Admittedly I haven't tried many of those since I installed 8.0, but they should have a better chance of working "out of the box" now.
I guess it was not caught but I had mentioned a few and important ones
like Apache, Lprng, Ifhp and Adaptec RAID drivers. Which it is true they
come with SuSE from the box but perhaps there should be a warning do not
download the latest from the actual apache.org or Lprng.com or adaptec.
The configuration program does not pickup any of the SuSE changes made to
configuration. So is either wait for SuSE to SuSEified all program
delivered with it or your are on your own if you download it from the WEB.
I am not saying that this is totally wrong but there should have been
more detailed changes information on this subject, especially in the book
delivered. Which granted is more geared towards new users and it is good
for that.
Thanks for the other clues as to how to make changes to configuration.
Percy Cardenas
MIS Director
River Oaks Furniture, Inc.
Anders Johansson
The move of configuration files (etc/rc.config to /etc/sysconfig and restructuring of /etc/rc.d and /etc/init.d) has definitely made the SuSE configuration imcompatible to many GPL software that one can download. Most are still expecting to find configuration files based on what SuSe prior version 8 was (ie. Apache, Lprng, Ifhp)
I think you'll find that the whole point of the move was exactly the opposite. So many programs on the net expect to find the redhat /etc/sysconfig system and very few were "SuSEified" to use START_FOO variables. The move should mean that *more* programs work with SuSE without modification, not less. At least if it's done right.
Myself, I still trying to figure out how to stop sendmail from the Yast2 interface. I have one server with Domino and I do not need the sendmail.
Runlevel editor->uncheck all checked boxes on the "sendmail" line. Or, from the command line, "insserv -r sendmail".
Not quite a check mate, I still have a few moves to try by learning how to use the configuration files in the /etc/sysconfig.
As far as I can see the only difference is the removal of the START_FOO variables, and a splitting of rc.config into separate files for each application. Apart from that it's more or less identical to what it used to be.
Please next time let's do a bit more trials. And I believe the changes made to the configuration files needs to be coordinated with most GPL software out there.
Most GPLed software is already on the SuSE disks. They work. The major thing is to get things to work with non-GPLed programs, and a lot of those in the past has been prepared for redhat systems only. Admittedly I haven't tried many of those since I installed 8.0, but they should have a better chance of working "out of the box" now.
Unless SuSE is content with modifying and keeping up to date to its own changes all these software so that it can install correctly in SuSE.
Isn't that what SuSE has always been the best at? //Anders -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com