Oddball wrote:
Felix-Nicolai Müller schreef:
Sid Boyce schrieb: | There is nothing wrong with having the largest user base, but it should | not be gained at the expense of good and essential fundamentals. I know | that openSUSE and family are very robust, designed to be deployed in | environments where security is important, the tools are as easy as any, | citing YaST, zypper and 1-click, just that they are not very widely | known on the outside. All the complaints against the distro I've ever | read show a lack of SuSE knowledge on the reviewer's part, while hardly | a day goes by when you don't see an article about how to do things in | Ubuntu, this does help explain and encourage people to try Ubuntu - they | can read enough to coax them into having a go. | | I could imagine a Ubuntu pitch to a corporate customer telling them how | simple it was with their distro because root and user shared the same | password. All hell would erupt in some, in others, they'd politely | promise to call.... | | Live systems are always going to be tricky in your situation. The best | policy would be a long test cycle before deploying live and to have a | ready fallback should you hit problems.
+1
+1.
I agree on the fact that out of experience shows, that things that work should not be altered, but that the focus must be on things that realy must be improved. Most times it is fatal to change too many at the same time, because if things go bad/wrong, it is difficult to find the 'real' cause.
My changes are not as drastic as they once were, then I kept a local log of all changes as typically a problem will surface may be a week or two after a change is made. The large IT mainframe shops going way back all have had a Change Control department that documented all proposed and actual changes which were thoroughly discussed in minute detail for possible impact. As a vendor, we were also subjected to the same process and I have had to travel up to 175 miles to explain and discuss any changes we proposed. We found however that the typical Solaris shops were not too good at it and on one occasion a programmer made a change over a weekend and on Monday the system croaked, but it was not until the Tuesday when he came back to work that they discovered the change had been made, he backed it out and the system came up. To demonstrate the thinking, the same customer attended their first Amdahl Share meeting in Copenhagen and on their return they were making fun of how paranoid mainframe customers were. Perhaps the culture has changed as many mainframe shops are now heavily into "Open" systems and staff migrate across the cultures. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org