<feed xmlns='http://www.w3.org/2005/Atom'>
<title>buildroot/system/Config.in, branch 2016.08</title>
<subtitle>OpenPOWER buildroot sources</subtitle>
<id>https://git.raptorcs.com/git/buildroot/atom?h=2016.08</id>
<link rel='self' href='https://git.raptorcs.com/git/buildroot/atom?h=2016.08'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/'/>
<updated>2016-08-14T14:11:46+00:00</updated>
<entry>
<title>system: sysvinit needs MMU</title>
<updated>2016-08-14T14:11:46+00:00</updated>
<author>
<name>Yann E. MORIN</name>
<email>yann.morin.1998@free.fr</email>
</author>
<published>2016-08-13T16:57:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=8a8546e5847c5281002bfc443a544f2ed8e80601'/>
<id>urn:sha1:8a8546e5847c5281002bfc443a544f2ed8e80601</id>
<content type='text'>
It uses spawn() and thus fork(), so it needs an MMU.

Fixes a build issue reported on IRC for a cortex-m4 build:
    http://pastebin.com/dGCsy0sr

Signed-off-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
</content>
</entry>
<entry>
<title>system: zoneinfo usable by musl, too</title>
<updated>2016-08-09T20:50:21+00:00</updated>
<author>
<name>Yann E. MORIN</name>
<email>yann.morin.1998@free.fr</email>
</author>
<published>2016-08-09T20:25:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=aae8513c401e287af7a9cd74548828182a1473da'/>
<id>urn:sha1:aae8513c401e287af7a9cd74548828182a1473da</id>
<content type='text'>
Currently, we limit installing zoneinfo to non-musl toolchain, by lack
of knowledge on how it would work on musl.

Turns out that musl uses the same zoneinfo format as glibc does.

Make it possible to install the TZ info whatever the C library; for
musl, use tzdata as for glibc.

Thanks Rich! ;-)

Signed-off-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Cc: Rich Felker &lt;dalias@aerifal.cx&gt;
Cc: Marc Khouri &lt;marc@khouri.ca&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
</content>
</entry>
<entry>
<title>system: move locale purging options to the "System configuration" menu</title>
<updated>2016-08-03T19:17:21+00:00</updated>
<author>
<name>Thomas Petazzoni</name>
<email>thomas.petazzoni@free-electrons.com</email>
</author>
<published>2016-08-02T22:19:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=a77e8d275f98259674768ea0a6cb5ab35ead140d'/>
<id>urn:sha1:a77e8d275f98259674768ea0a6cb5ab35ead140d</id>
<content type='text'>
The options to purge locales and to generate locale data are currently
located in the toolchain menu. However, these options are not really
related to the toolchain per-se, they are more system-level
configuration options, much like the timezone selection option we
already have in the "System configuration" menu.

Therefore, it makes more sense to have the locale-related options in
the "System configuration" menu as well.

Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>system: do not set hostname and issue for custom skeleton</title>
<updated>2016-07-18T21:45:49+00:00</updated>
<author>
<name>Yann E. MORIN</name>
<email>yann.morin.1998@free.fr</email>
</author>
<published>2016-07-17T08:44:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=8c8b9b6ad782957941fed25a86a470638f3b4347'/>
<id>urn:sha1:8c8b9b6ad782957941fed25a86a470638f3b4347</id>
<content type='text'>
We expect the custom skeleton to be fully filled with the necessary
files, now. There is definitely no reason we should handle setting the
hostname and the issue file in there. A user using a custom skeleton
should be fully responsible for providing a functional skeleton.

Signed-off-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Reviewed-by: Romain Naour &lt;romain.naour@gmail.com&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
</content>
</entry>
<entry>
<title>system: do not handle network settings for custom skeleton</title>
<updated>2016-07-18T21:45:34+00:00</updated>
<author>
<name>Yann E. MORIN</name>
<email>yann.morin.1998@free.fr</email>
</author>
<published>2016-07-17T08:44:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=65329a102485c7a760a0129643b128f44c73c0f4'/>
<id>urn:sha1:65329a102485c7a760a0129643b128f44c73c0f4</id>
<content type='text'>
We expect the custom skeleton to be fully filled with the necessary
files, now. There is definitely no reason we should handle network
settings in there. A user using a custom skeleton should be fully
responsible for providing a functional skeleton.

Signed-off-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Reviewed-by: Romain Naour &lt;romain.naour@gmail.com&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
</content>
</entry>
<entry>
<title>system: move the rootfs skeleton choice</title>
<updated>2016-07-18T21:45:29+00:00</updated>
<author>
<name>Yann E. MORIN</name>
<email>yann.morin.1998@free.fr</email>
</author>
<published>2016-07-17T08:44:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=a661e0ba5eb44d8d9fbd8845b3c4e6cc28c728c5'/>
<id>urn:sha1:a661e0ba5eb44d8d9fbd8845b3c4e6cc28c728c5</id>
<content type='text'>
In the following commits, we'll be switching more options to be
conditional on the default or custom skeleton.

So, it makes sense that those options come after the choice of a
skeleton.

Signed-off-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Reviewed-by: Romain Naour &lt;romain.naour@gmail.com&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
</content>
</entry>
<entry>
<title>system: provide no default for custom skeleton path</title>
<updated>2016-07-18T21:40:06+00:00</updated>
<author>
<name>Yann E. MORIN</name>
<email>yann.morin.1998@free.fr</email>
</author>
<published>2016-07-17T08:44:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=b541b9ff94af8d0464deeb6e902dcc653b9c44b4'/>
<id>urn:sha1:b541b9ff94af8d0464deeb6e902dcc653b9c44b4</id>
<content type='text'>
Being custom means that our default one is not suitable to start with.
So there is no reason to offer it as the default path.

Add a check that it is not empty.

Add a separating empty line, for good measure, too.

Signed-off-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Cc: Romain Naour &lt;romain.naour@openwide.fr&gt;
Cc: Arnout Vandecappelle &lt;arnout@mind.be&gt;
Reviewed-by: Romain Naour &lt;romain.naour@gmail.com&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
</content>
</entry>
<entry>
<title>system: systemd only really supports a R/W rootfs</title>
<updated>2016-07-05T13:29:28+00:00</updated>
<author>
<name>Yann E. MORIN</name>
<email>yann.morin.1998@free.fr</email>
</author>
<published>2016-06-22T19:07:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=886f3109bc6e77fa1a6b7edb9647a3c4ab0ec431'/>
<id>urn:sha1:886f3109bc6e77fa1a6b7edb9647a3c4ab0ec431</id>
<content type='text'>
Supporting a R/O rootfs needs a bit more love to be fully operational.
This will come in later patches...

Signed-off-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Reviewed-by: Romain Naour &lt;romain.naour@gmail.com&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
</content>
</entry>
<entry>
<title>fs/common: add option to execute custom scripts under fakeroot</title>
<updated>2016-07-03T18:58:46+00:00</updated>
<author>
<name>Yann E. MORIN</name>
<email>yann.morin.1998@free.fr</email>
</author>
<published>2016-07-03T15:08:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=9cdb281fa64eb2b58ec1d25cb62c29268aa4b906'/>
<id>urn:sha1:9cdb281fa64eb2b58ec1d25cb62c29268aa4b906</id>
<content type='text'>
Some users have the need to be able to tweak the content of the target
rootfs with root-like rights, that is, from inside the fakeroot script.

Add a new system option to allow those users to provide a list of
scripts, like the post-build and post-image scripts, that will be run
from our fakeroot script.

[Peter: pass TARGET_DIR to scripts, tweak help text]
Signed-off-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Cc: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
Cc: Peter Korsgaard &lt;peter@korsgaard.com&gt;
Cc: Cam Hutchison &lt;camh@xdna.net&gt;
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>makedevs: add capability support</title>
<updated>2016-06-30T10:13:38+00:00</updated>
<author>
<name>Philippe Reynes</name>
<email>philippe.reynes@sagemcom.com</email>
</author>
<published>2016-06-29T15:19:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=688059ebb23227fb13aad319df6e78686ea6e14a'/>
<id>urn:sha1:688059ebb23227fb13aad319df6e78686ea6e14a</id>
<content type='text'>
Add the support of capability to makedevs as extended attribute.
Now, it's possible to add a  line "|xattr &lt;capability&gt;" after a
file description to also add a capability to this file. It's
possible to add severals capabilities with severals lines.

[Peter: extend doc, reword Config.in, extend error message,
	use HOST_MAKEDEVS_CFLAGS/LDFLAGS for all flags]
Signed-off-by: Philippe Reynes &lt;philippe.reynes@sagemcom.com&gt;
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
</feed>
