On 05/19/2013 01:05 PM, Canek Peláez Valdés wrote: > On Sun, May 19, 2013 at 9:34 AM, Peter Stuge <pe...@stuge.se> wrote: >> J. Roeleveld wrote: >>> I don't see how this will avoid the issue of a limited amount of >>> inodes. >>> That is what I usually run out of before the disk is full when >>> storing lots of smaller files. >> >> I guess the number of unit files is on the order of hundreds > > (Sorry, sent email before it was ready). > > Laptop running full GNOME: > > # find /usr/lib/systemd/system -type f | wc > 154 154 7012 > > Server running Apache+MySQL+Mailman+Squid+Other services: > > # find /usr/lib/systemd/system -type f | wc > 121 121 5560 > > And as you said, you can always use INSTALL_MASK. If 154 files are > going to deplete your inodes, I think your problem lies somewhere > else. > > Regards. > -- > Canek Peláez Valdés > Posgrado en Ciencia e Ingeniería de la Computación > Universidad Nacional Autónoma de México >
That's missing the point. If you don't run systemd, having unit files is pointless. Thankfully there's INSTALL_MASK and whatnot, but that seems like a hack instead of something more robust. Why include systemd unit files (by default, with no systemd USE flag, thanks to the council...) on a system that's not using it? 154 files isn't negligible unless you're flippant with your system and don't care about bloat. Unused software sitting around *is* a waste of disk-space. Some people (like myself) came to Gentoo to avoid putting systemd on their systems and to make use of the great choice that Gentoo allows. This push to make systemd a "first level citizen" or whatever reeks of marketing. If there is desire among users for unit files, they can contact upstream or maintain their own set of unit files. It's not like they're hard to write.
