On 06/04/2014 06:12 AM, Damian Ivanov wrote:
Yes Anton, but this arguing about what the default should be. The original claims were that systemd breaks that which is a lie. :)
First: as I, very obviously, subscribe to the list, there is no need to cc me on your replies. Defaults are fine but getting hung up on them is unrealistic. Any real system is going to need configuring and massaging to get it to perform well (for whatever value of 'well' you choose) in a real setting. Context, as I keep saying, is everything, and the defaults are neither sacrosanct nor immutable. One of the entries that I've seen my random signature quote dig out and use in past email which impressed me reads Be very glad that your PC is insecure --it means that after you buy it, you can break into it and install whatever software you want. What YOU want, not what [content providers] want. -- John Gilmore of the EFF The reality is that we begin customizing with the install process an continue to make many hundreds of customization decisions. The more 'geeky' of us might use CLI and VI on the config files, but there's always Yast :-) In a commercial/industrial setting one can be absolutely sure that the system will be customized! Personally I run rsyslog alongside the systemd logger on my home system. Yes, there are ... I'm not sure I'd call them lies, but certainly there are scurrilous and unsubstantiated rumours and assertions which get elevated into hard assertions. Some people have gone overboard in their denunciation of systemd and are making assertions that range from 'easily disproven', through 'redefinition of terms' to 'screaming obscenities'. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org