Oddball wrote:
Sid Boyce schreef:
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.
Maybe they misunderstood the responsibility that came with it, and confused it with paranoia...;)
Nowadays there seem to be too much agendas. Too many things changing at the same time, will make control on the consequenses more difficult, as you discribe out of reality here. The timeframe and order to change fundamental stuf, is important, to keep grip on the situation. I understand deadlines, but i also understand reality, and haste does not fit in there...
What i am trying to say is that time to achieve 'real' changes, may spread 3 GM versions. When major changes might jepperdize a version, try to spread them over 3. There is no need to rush, because others do. Keep sanity. to create a thrustworthy distribution. New, but stable. Like we ourselves want to have it, and not how someone thinks, unexisting, might be newbies, might want to have it, if they would choose... A good distro is. (To Be, or Not To Be.) What does not function, has to be fixed or replaced.
What is it we do not like about openSuSE now, that has to change?, exept what doesn't work?
The thing I most like about openSUSE is that it is pretty much up to date, which means that if I have to install a new application from sources, I don't have to go on the hunt for a host of new library sources as previously needed for building apps such as Flightgear. It's proof that old isn't necessarily solid or stable. The only thing I would like to see added is OpenSceneGraph which is used by applications other than FlightGear and would be a useful addition for people doing graphical work -- looks like a feature request is due. It's probably understandable what newbies think they need and form a bad opinion of a solid and extensive distro, complaints like too much software, too long to install, long boot up time, difficulty in finding software, etc. I have a friend who is a long time SuSE/openSUSE user, still using 10.2 as he has had problems with anything later, especially in the area of Wifi support, but seemingly with other things also, though one early 10.3 Alpha box seems OK for him. I am puzzled as 10.2 Alpha through to 11.0 Alpha3 have been fine on every box I have. Better Wifi and other hardware support is in later kernels, tools are better. I shall recommend he upgrades his kernel so as not to have to use ndiswrapper, though he says he can't risk any problems with the 10.2 box. I can't help but feel that there is something he is doing that I'm not or vice versa. From his side anything later than 10.2 is a disaster. I must find some time and see for myself the install of the latest openSuSE one one of his boxes. I just can't figure it - possibly a bad DVD writer giving openSUSE a bad name, I have had quite a few fail and only 2 out of 5 here seem OK. Media check works on the box that generated the DVD, then the install on another box fails in strange ways, mainly with file integrity problems. 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