From: "Rüdiger, Christoph" <Christoph.Ruediger@thyssenkrupp.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Feature Request: Option to install man pages
Date: Wed, 4 Mar 2015 12:14:11 +0000 [thread overview]
Message-ID: <1E9AED858BEB204B9DE4F807C7ED0EF61B0CED73@EMSRVWIN2934.apps.edc.thyssenkrupp.com> (raw)
In-Reply-To: <54F6E22E.3080209@gmx.net>
> The ability to create small rootfs images was basically my primary reason to
> use ptxdist many years ago, when I had just 32 MB of flash for all and
> everything.
>
> However the smart phone boom of the last few years dramatically changed
> the definition of 'small' - the smallest flash devices for our embedded HW
> starts now around 2-4 *Giga*bytes. And as smallest does NOT mean
> cheapest, the standard flash device at work - right now - is 4 GB eMMC,
> which will probably increase the usual 2^n steps the next months/years.
Our usual device configuration is 64 MB Flash at the moment. There are some devices with MMC outside, but just for application data storage, not for Root-FS.
> And with this change the following question is now poping up over and over
> again: Why using a crippeled rootfs without man pages just to save some few
> MB out of several 1000s?
>
> So I would like to propose to add some global switch to the ptxdist
> configuration, which optionally allows users to install docs. Docs usually mean
> man pages, but options for info or similar would be fine, too. And of course a
> set of macros for the targetinstall stage, which conditionally picks up man
> pages at the usual places, when enabled.
Would it be possible to have the man pages in the sysroot folder for NFS usage, but not in the generated images for flashing on the device? In such a configuration, it would fit the needs for man pages in development stage, but you do not mess up the storage in your final product. However, I don't know yet how the different root-fs folders and the image files are generated.
Or add man pages to the debug sysroot, but not to the release sysroot?
Just my two cents,
Christoph
--
Christoph Ruediger
Developer
ThyssenKrupp Elevator Innovation GmbH
PDC Neuhausen
TKEI Elevator Control
Bernhaeuser Straße 45
73765 Neuhausen, Germany
Phone +49 7158 12-2615
christoph.ruediger@thyssenkrupp.com
Company domicile: Essen Commercial register: Essen HRB 20 839
Postal address: ThyssenKrupp Allee 1, 45143 Essen, Germany
Executive Board: Gerhard Thumm, Katrin Huenger, Philippe Choleau
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-03-04 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 10:45 Carsten Schlote
2015-03-04 12:14 ` Rüdiger, Christoph [this message]
2015-03-04 18:40 ` Bruno Thomsen
2015-03-04 19:18 ` Alexander Dahl
2015-03-05 12:59 ` Guillermo Rodriguez
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=1E9AED858BEB204B9DE4F807C7ED0EF61B0CED73@EMSRVWIN2934.apps.edc.thyssenkrupp.com \
--to=christoph.ruediger@thyssenkrupp.com \
--cc=ptxdist@pengutronix.de \
/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