All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] logrotate scripts policy
Date: Tue, 11 May 2010 18:05:15 -0500	[thread overview]
Message-ID: <4BE9E2AB.5020106@mwester.net> (raw)
In-Reply-To: <201005111904.06230.khimov@altell.ru>

Roman I Khimov wrote:
...
> This way all *-logrotate packages will get installed by default, but not the 
> logrotate program. So, it will eat some little space in /etc/logrotate.d for 
> everyone by default (but you can get rid of those packages if you really don't 
> want them), but would allow to switch rotation on/off easily with just one 
> package included or not in the image.

The NSLU2 has a grand total of 8MB of flash space for bootloader,
kernel, and the filesystem.  We don't have even a few KB left right now
for those extra packages.  Keep in mind that even a 20-byte script will
have a large footprint in the opkg database that's on the filesystem, so
that space is in addition.

It's really really difficult to build an image without a whole lot of
extraneous stuff in it, and I suspect that extraneous stuff is all in
there for the same reasoning, which goes along the lines of "It's only a
little bit of space..." -- but it all adds up, and when your total
rootfs can only be 5.5 MB or so...

I'm not going to NAK this, but I will ask that if you do this please
spend some time with the SlugOS image recipes to remove all the packages
that this adds by default, with whatever mechanism you meant when you
say "but you can get rid of those packages if you really don't want them".

-Mike (mwester)



  parent reply	other threads:[~2010-05-11 23:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11 15:04 [RFC] logrotate scripts policy Roman I Khimov
2010-05-11 15:10 ` Roman I Khimov
2010-05-11 16:07   ` Roman I Khimov
2010-05-11 15:15 ` Martin Jansa
2010-05-11 16:01   ` Roman I Khimov
2010-05-11 23:05 ` Mike Westerhof [this message]
2010-05-12 10:19   ` Roman I Khimov

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=4BE9E2AB.5020106@mwester.net \
    --to=mike@mwester.net \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.