public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Reusing systemd unit file format / forking systemd
Date: Sun, 26 May 2013 13:47:19 +0200	[thread overview]
Message-ID: <51A1F647.3010508@gentoo.org> (raw)
In-Reply-To: <20130526133111.5b8ae745@gmail.com>

On 5/26/13 1:31 PM, Robert David wrote:
> Come on, it is 2013, wasting few inodes. I did not got these problems
> in the old good times with my 386 with 4mb ram and few MB hdd.
> Those with embedded system will mask many other files, not only
> systemd units (so they save one inode more with my approach, when need
> no initscript-wrapper).
> Users of regular server/desktops/laptops, 10-20 inodes more? They would
> rather won't use Gentoo with its portage tree or do not compile
> kernel sources, etc.

The fact we are already the worst offenders won't make thinking about 
impacting a little less not that important.

System with the problem keep portage in a separate fs.

lu



  reply	other threads:[~2013-05-26 11:47 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25 16:14 [gentoo-dev] Going against co-maintainer's wishes (ref. bug 412697) Ben de Groot
2013-05-25 16:48 ` Michał Górny
2013-05-25 17:38   ` Rich Freeman
2013-05-25 20:02     ` Chí-Thanh Christopher Nguyễn
2013-05-25 20:40       ` Rich Freeman
2013-05-25 20:45       ` Michał Górny
2013-05-25 21:38   ` Luca Barbato
2013-05-26  7:23   ` Ben de Groot
2013-05-26  7:43     ` Michał Górny
2013-05-26 10:04       ` Rich Freeman
2013-05-26 15:21         ` Ben de Groot
2013-05-26 16:15           ` Rick "Zero_Chaos" Farina
2013-05-26 17:14             ` Matt Turner
2013-05-26 17:19             ` Andreas K. Huettel
2013-05-26  7:54     ` Pacho Ramos
2013-05-25 17:00 ` Pacho Ramos
2013-05-25 17:14   ` Carlos Silva
2013-05-26  7:15   ` Ben de Groot
2013-05-26  7:44     ` Pacho Ramos
2013-05-26  7:45     ` Michał Górny
2013-05-26  9:59       ` Luca Barbato
2013-05-25 18:13 ` Markos Chandras
2013-05-25 19:53   ` Anthony G. Basile
2013-05-25 19:58     ` Mike Gilbert
2013-05-25 21:55       ` Anthony G. Basile
2013-05-25 19:59     ` Rich Freeman
2013-05-26  7:00     ` Michał Górny
2013-05-26  7:22     ` Tiziano Müller
2013-05-26  7:46       ` Pacho Ramos
2013-05-26  7:49       ` Michał Górny
2013-05-26  7:00   ` Ben de Groot
2013-05-26  7:37 ` [gentoo-dev] Reusing systemd unit file format / forking systemd (was: Going against co-maintainer's wishes (ref. bug 412697)) Michał Górny
2013-05-26  8:32   ` Ben de Groot
2013-05-26  9:49     ` Rich Freeman
2013-05-26 10:12       ` Robert David
2013-05-26 10:31         ` Michał Górny
2013-05-26 11:12           ` Rich Freeman
2013-05-26 11:31           ` Robert David
2013-05-26 11:47             ` Luca Barbato [this message]
2013-05-26 10:23   ` [gentoo-dev] Reusing systemd unit file format / forking systemd Luca Barbato
2013-05-26 11:15     ` Michał Górny
2013-05-26 11:59       ` Luca Barbato
2013-05-26 13:35         ` Sergei Trofimovich
2013-05-26 14:22           ` Luca Barbato

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51A1F647.3010508@gentoo.org \
    --to=lu_zero@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox