On Sat, 2014-06-07 at 17:54 +0200, Bardur Arantsson wrote:
On 2014-06-07 17:46, Ralf Mardorf wrote: [--snip--]
I suspect it's just the evil policy of those systemd folks, who want to teach everybody to follow there ways, as the only right ways.
Please don't insinuate conspiracies without good evidence.
It's not a bug, nothing needs to be fixed [1]. So what is the reason for this decision, when it's not a bug? It worked with _all_ systemd versions until now, it still works with sysvinit and upstart. It _never_ cause trouble to use localtime the last 11 years on my machines, just the current systemd upgrade for my Arch Linux, for the first time ever in 11 years does cause trouble. Perhaps we shouldn't spoil the list, you perhaps could explain me the reason for this decision off-list. Maybe I simply miss something. Regards, Ralf [1] -------- Forwarded Message -------- From: Arch Linux <bugs@archlinux.org> Reply-to: bugs@archlinux.org To: bugs@archlinux.org Subject: FS#40706: [systemd] cannot boot with 213-5 Date: Sat, 07 Jun 2014 15:55:34 +0000 Mailer: Flyspray THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#40706 - [systemd] cannot boot with 213-5 User who did this - Dave Reisner (falconindy) ---------- Your "superblock issue" is solved by not using localtime. Nothing to be fixed in systemd. ---------- More information can be found at the following URL: https://bugs.archlinux.org/task/40706#comment124000 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.