On Wed, Apr 17, 2013 at 11:49 PM, Josh Triplett <j...@joshtriplett.org> wrote:
> + - Replace utmp, wtmp, btmp, and lastlog completely with journal We should definitely add the data needed to constuct this information, if they are not already there. The tools could just use the journal directly, but there is the glibc api. > + - Provide one or more FUSE filesystems: > + - Emulate utmp, wtmp, btmp, lastlog; read/write, recording credentials > for all writes rather than limiting permissions That sounds like overkill. We should surely externalize the creation of the files from systemd and make it optional to support legacy stuff, otherwise these files should rather be phased out, than emulated, I think. > + - Provide /var/spool/crash or equivalent, exposing an index of coredumps > directly Coredump are really not consumed by any legacy thing that would need a file system. What do you have in mind here. Specialized apps that need that should just use the native API, not expect a file system, I think. > + - Provide decoded text logs in /var/log I really don't think these plain text streams make much sense today. If people want them, they should install syslog. Or some other project can do that, I'm confident we do not want that code in systemd. > + - Port upower to use the journal for historical power information used in > future calculations Yeah, that would be useful. > + - Support optional database-style indexes for frequent or > performance-critical queries Well, it is not a database, it's a pretty specialized format based on bisection lists. What specific thing do you have in mind? Kay _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
