On Tue, 09.10.12 11:30, Matthew Miller (mattdm@xxxxxxxxxxxxxxxxx) wrote: > On Tue, Oct 09, 2012 at 05:24:42PM +0200, Richard Marko wrote: > > > Compared to the other things I mentioned this is less important (because > > > hey, sysadmins can learn new ways!), but I wanted to elaborate on where this > > > is coming from. > > +1. For example swapping action and name parameters for systemctl > > compared to service calls is just annoying. > > Yes. Again, you're not the first person I've heard this from. Likewise, > needing to fill out the .service extension. Both make a certain logical > sense from a design point of view, but they're not putting the user first. Note that in F18 we will append ".service" if a unit name otherwise makes no sense. In fact, there are a number of other little gimmicks in there: "systemctl status foobar" is equivalent to "systemctl status foobar.service" "systemctl status /dev/sda" is equivalent to "systemctl status dev-sda.device" "systemctl status /home" is equivalent to "systemctl status home.mount" "systemctl status dödel.service" is equivalent to "systemctl status d\xc3\xb6del.service" Or with other words: we now have rules to qualify strings that otherwise make no sense or are invalid with a very minimal, simple and static logic. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
