----- Original Message -----
On Wed, 17.07.13 21:00, Ding Yi Chen (dchen@redhat.com) wrote:
If you never want any changes, then Fedora is simply not the distribution for you. Slackware might be.
I want sane changes that does not break my system.
Well, this won't "break" systems as the change is only for new installations. Existing systems will stay exactly as they are, rsyslog stays installed, and will work as always.
1. What if they update the system like this: Backed up user data/script -> Fresh install -> Restore user data/script For that, it won't work.
2. Like other already point out, Windows/Fedora dual boot. You can see /var/log/messages from Windows, but how can you get journalctl output in Windows?
Please update your knowledge, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428097
They have /var/log/messages, yes, it might be different with ours. But yes, they have that.
So, they store different stuff in it. The interesting stuff is mostly in daemon.log on Debian. So with your suggested program you'd miss out all the interesting bit son Debian. This stuff is certainly not standardized on Unix systems...
a) If debian output the thing I want in /var/log/messages anyway, why should I care whether other daemon output in other files? b) If my environment only contains RHEL and Fedora, why should I care how Debian, Arch and Ubuntu handle their logs?
Innovation should not be the cost of reliability and portability.
This change touches neither. /var/log/messages already isn't standard in whether it exists at all, and what it contains, so we certainly don't make "portability" worse...
Something is not standard does not mean nobody using it. Especially it is there quite a long time. Remove it simply break their expectation and scripts. For that, you do make the portability worse.