On Thu, 25.08.11 22:59, Tom Gundersen ([email protected]) wrote: > This is useful to be able to use systemd-analyze with initrd's that don't > have systemd support. In particular, Arch's initrd exports RD_TIMESTAMP > on this format. I also believe dracut falls back to this when > systemd-timestamp > is not present.
When I wrote this I was thinking about allowing the /proc/uptime format for this, but decided against it for a number of reasons. Instead I preppaed systemd-timestamp for inclusion in initrds. I am not a fan of allowing too many variables in the game where they bring no clear benefit. Hence my question: why? Why can't your initrd simply include systemd-timestamp in the image, the same way we do it on dracut? (the binary has no deps, so there's nothing stopping you really). Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
