Posts by rtfazeberdee

no, the init scripts are not too hard but they are all basically the same content so there is a lot of files with duplicated code which seems daft. Plus the SysV init systems on Redhat, opensuse, arch debian etc were all slightly different in implementation and file locations so you couldn;t just move use one script across all systems without modification or learning new stuff. with systemd the startup with be common to all distros that use it i.e. making life easier for the admin that has various OS's to maintain. Plus, if you want to still use your init scripts within systemd, you can just configure to to use them.

sorry but you are just a typical troll dishing out lies about "suboptimal design", bad code etc, you've never looked at the code. typical comments from someone who does not know what he/she is talking about.

its not "binary configuration", all the config files are ascii format. the journal is stored in binary format with the configurable option to offload the logs to the current syslog system. it won't make any difference to someone who does not dabble in system start up.

Re: Can't there be a simple and effective Linux distribution?

"The guy is just a programmer (and not a very good one, at that)," - he'll wipe the floor with you, just as well you posted as an Anon Coward

Re: read around...

yeah, we all believe what an Anon Coward says.......

True, but when you post them on their employers facebook page, the intent is obvious

Re: My take on all this

Where have you done your reading? Forums like this? Try reading up about systemd at the freedesktop site and check out some presentations online , you'll then find out that you can also have text logging, run scripts as normal etc. You are falling victim to ignorant posters who regurgitate crap from other ignorant posters

Re: If systemd is so bad...

@Sir Alien

Not true, where are you getting your facts? from the bottom of your shoe?. Only Gentoo and Slackware linux do not/will not use systemd, Ubuntu currently uses their own version called upstart but will be upgrading to systemd shortly.

SO that makes Fedora, opensuse, Arch, CoreOS, Magiea, RHEL, SLES, Tizen, Debian using it now.

Re: Hasn't this happened already with Upstart?

journald starts logging at an earlier stage that it is possible for rsyslog to start logging and long after rsyslog has to stop logging during shutdown and it produces a lot more information. It also has a great viewing tool for the logs, journalctl. If you are really interested in logs, have a look at what you get.

Re: @John Hughes

You need to read up on systemd before you make rash decisions. pssttt, you can configure systemd have text logs too to dismiss just one of your misinformed criticisms

Re: This is gold

What "manners of hardware support"? its broken nothing on my machines, maybe you need a training course on systemd.

Re: What is systemd

"That may be the case. However some have, including myself. " - i guess you must be smarter than the Red Hat, Suse etc teams then, i'm sure they are going to release a system to their customers that doesn;t work.

From what i've read of your posts on systemd, you are being ideological and do not have any real technical problems to point out, just your inability to make it work.

Re: What is systemd

If you admin a systems and loads and kills a lot of VMs, boot speed is required and that is the reason, a by product is that it benefits the desktop user.

Re: Off to a bad start

Before you run off another distro find out about the logging instead of listening to ignorant crap posted in these forums. ALL LOGS CAN BE CONFIGURED IN SYSTEMD TO BE SENT TO RSYSLOG IN TEXT as per normal.

i really can't believe this crap about binary logging is still being propagated

Re: Off to a bad start

"Does that REQUIRE, absolutely REQUIRE binary logs?" - no, it doesn't but systemd starts logging so much earlier in the process that rsyslog can and long after rsyslog exits at shutdown. THE logging can be configured to send the logs in text to rsyslog as per normal so binary is a non-issue. Its a stupid argument by people who have not looked into the issue. Systemd makes boot-up faster by allowing parallel startup of services and its faster to do than starting by scripts. Most startup scripts are generic so doing it via systemd is sensible as systemd still allows you to run scripts as per normal - its all down to configuration.

You are making a lot of decisions/assumptions about something you have not even investigated and relying on misinformed posters

Re: Off to a bad start

If you don't understand shell scripting syntax, you won't have a clue what its doing. Its the same with systemd, if you don't learn about how it works, you won't know how it works.

Re: Hasn't this happened already with Upstart?

Do some research , don't rely on idiots who don't do any. You can configure systemd to spit out text logs to rsyslog as per normal alongside the more comprehensive binary logs.

Re: This is gold

try looking at the advantages for admins who administer VMs - VMs get created and destroyed a lot of times so boot time is important

Re: Hasn't this happened already with Upstart?

"Also systemd does its own logging. In binary. Not using syslog. You can't cat or edit the logs any more. No. Just no." You need to read up about systemd before you trash it. You can configure systemd to produce text logs to rsyslog in addition to the default of binary logs. systemd requires udev. You just lack the skill of configuring systemd to suit your requirements and blame it for your failures