minimizing footprint

Paul Fox pgf at
Sun Mar 24 18:34:56 EDT 2013

i think the point john (gilmore) was making is that it's a bad
precedent that simply because a) systemd offers a second-rate API for
scheduling events, and b) we only have a couple of uses for an event
scheduler, that we should therefore switch from a well-established API
to a lousy API.  instead, if systemd can be made to support the cron
API properly, it would be worth making it do so.

barring that, or if it's too much work (likely), then if it saves us
boatloads of disk to make the switch, and our use-cases don't lose
functionality or correctness as a result, then i guess we should

but when systemd falls out of favor in a year or two we'll just have
to change things again -- either to something new, or back to cron
(which will most certainly still be available).


gonzalo wrote:
 > On Sun, Mar 24, 2013 at 11:29 AM, Tony Anderson <tony_anderson at>wrote:
 > > On 03/24/2013 09:38 AM, devel-request at wrote:
 > >
 > >> It's true, we need learn new tricks, but does not have sense have a
 > >> service
 > >> not needed on every xo, if we can do it in a better way.
 > >>
 > >
 > > Does this logic apply generally?
 > >
 > > 12.1.0 has a control panel entry 'Modem configuration'. How many XOs
 > > require this capability?
 > >
 > >
 > Generally.
 > In the case we are discussing, we don't need remove a feature,
 > only implement it in a different way.
 > Gonzalo
 > part 2     text/plain                 129
 > _______________________________________________
 > Devel mailing list
 > Devel at

 paul fox, pgf at

More information about the Devel mailing list