<feed xmlns='http://www.w3.org/2005/Atom'>
<title>buildroot/system, branch 2019.02-op-build</title>
<subtitle>OpenPOWER buildroot sources</subtitle>
<id>https://git.raptorcs.com/git/buildroot/atom?h=2019.02-op-build</id>
<link rel='self' href='https://git.raptorcs.com/git/buildroot/atom?h=2019.02-op-build'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/'/>
<updated>2019-02-06T16:11:38+00:00</updated>
<entry>
<title>system: allow selecting merged /usr along with custom rootfs skeleton</title>
<updated>2019-02-06T16:11:38+00:00</updated>
<author>
<name>Carlos Santos</name>
<email>casantos@datacom.ind.br</email>
</author>
<published>2018-05-07T14:44:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=0dd0a583510f72ef14b73e4fa2d44ff65febd833'/>
<id>urn:sha1:0dd0a583510f72ef14b73e4fa2d44ff65febd833</id>
<content type='text'>
If the user is brave enough to use a custom rootfs skeleton then we must
not prevent using merged /usr too. Actually it is already possible to do
this, although indirectly, by selecting BR2_INIT_SYSTEMD.

Signed-off-by: Carlos Santos &lt;casantos@datacom.ind.br&gt;
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) &lt;arnout@mind.be&gt;
</content>
</entry>
<entry>
<title>skeleton: use BR2_SYSTEM_DEFAULT_PATH as default PATH</title>
<updated>2018-12-31T13:32:44+00:00</updated>
<author>
<name>Markus Mayer</name>
<email>mmayer@broadcom.com</email>
</author>
<published>2018-12-20T17:58:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=df20a836c14ca50ea2fd761046144b93f9551224'/>
<id>urn:sha1:df20a836c14ca50ea2fd761046144b93f9551224</id>
<content type='text'>
We substitute the path specified in system/skeleton/etc/profile with
the path specified in the configuration variable
$(BR2_SYSTEM_DEFAULT_PATH).

$(BR2_SYSTEM_DEFAULT_PATH) is a Kconfig string, so it is already
double quoted. This means that export PATH=value will now be export
PATH="value" in /etc/profile, which is perfectly fine.

Signed-off-by: Markus Mayer &lt;mmayer@broadcom.com&gt;
Reviewed-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
[Thomas: rework commit log about the double quoting]
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@bootlin.com&gt;
</content>
</entry>
<entry>
<title>system: introduce BR2_SYSTEM_DEFAULT_PATH option</title>
<updated>2018-12-31T13:32:20+00:00</updated>
<author>
<name>Markus Mayer</name>
<email>mmayer@broadcom.com</email>
</author>
<published>2018-12-20T17:58:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=375f7488758d8cf75af2b56f2ff01af0eb2de933'/>
<id>urn:sha1:375f7488758d8cf75af2b56f2ff01af0eb2de933</id>
<content type='text'>
The configuration option BR2_SYSTEM_DEFAULT_PATH allows the user to
override the default path, which can be used by /etc/profile and some
system daemons.

It defaults to the value previously hard-coded in /etc/profile. This
default should be suitable for most users.

Signed-off-by: Markus Mayer &lt;mmayer@broadcom.com&gt;
Reviewed-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@bootlin.com&gt;
</content>
</entry>
<entry>
<title>system cfg: remove mkpasswd MD5 format option</title>
<updated>2018-12-15T10:33:29+00:00</updated>
<author>
<name>Matt Weber</name>
<email>matthew.weber@rockwellcollins.com</email>
</author>
<published>2018-12-06T02:06:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=bf3626002fbdf9802372b0127195b4824faf1337'/>
<id>urn:sha1:bf3626002fbdf9802372b0127195b4824faf1337</id>
<content type='text'>
As SHA256 is now default, removing weak MD5 option.  C libraries now
all support the SHA methods.
    glibc 2.7+
    uclibc (bdd8362a88 package/uclibc: defconfig: enable sha-256...)
    musl 1.1.14+

One issue this would prevent, is a host tool issue with a FIPS enabled
system where weak ciphers/methods are disabled. It seems the crypt(3)
call is impacted by /proc/sys/crypto/fips_enabled (per crypt(3) man
page). It results in mkpasswd returning "(EPERM) crypt failed."
Rather then create a Buildroot host dependency check, this patch
removes the potential corner case from being selected.

Acked-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Cc: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Signed-off-by: Matthew Weber &lt;matthew.weber@rockwellcollins.com&gt;
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>system cfg: set mkpasswd default to SHA256</title>
<updated>2018-12-15T10:26:37+00:00</updated>
<author>
<name>Matt Weber</name>
<email>matthew.weber@rockwellcollins.com</email>
</author>
<published>2018-12-06T02:06:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=9cf2280846b60ba081ed21339b407e2c761b599d'/>
<id>urn:sha1:9cf2280846b60ba081ed21339b407e2c761b599d</id>
<content type='text'>
This patch changes the default mkpasswd method to SHA256 from MD5.
The change both improves the quality of the hash used and prepares
for eventually removing MD5 as a option.

Reviewed-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Signed-off-by: Matthew Weber &lt;matthew.weber@rockwellcollins.com&gt;
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>system cfg: update mkpasswd SHA option txt</title>
<updated>2018-12-15T10:24:02+00:00</updated>
<author>
<name>Matt Weber</name>
<email>matthew.weber@rockwellcollins.com</email>
</author>
<published>2018-12-06T02:06:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=2e104e22ea23478e3d7cd6113dba340533140e41'/>
<id>urn:sha1:2e104e22ea23478e3d7cd6113dba340533140e41</id>
<content type='text'>
This patch drops the comment about checking the C libraries version as
they now all support it by default
    glibc 2.7+
    uclibc (bdd8362a88 package/uclibc: defconfig: enable sha-256...)
    musl 1.1.14+

Reviewed-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Cc: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Signed-off-by: Matthew Weber &lt;matthew.weber@rockwellcollins.com&gt;
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>package/systemd: needs glibc</title>
<updated>2018-11-22T16:15:33+00:00</updated>
<author>
<name>Yann E. MORIN</name>
<email>yann.morin.1998@free.fr</email>
</author>
<published>2018-11-21T21:05:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=0d61846b5f267839911a76ed2aeed505575de0bd'/>
<id>urn:sha1:0d61846b5f267839911a76ed2aeed505575de0bd</id>
<content type='text'>
Since version v239, systemd-nspawn unconditioanlly uses prlimit(2),
which is not implemented in uClibc-ng. systemd-nspawn can not be
disabled.

This makes systemd glibc-only again.

After a bit of discussion with upstream (om IRC), it looks very
improbable that they accept a patch making systemd-nspawn optional.
They would probably consider a patch that provides that syscall wrapper
if it is missing, though, but that's less trivial...

Signed-off-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Cc: Waldemar Brodkorb &lt;wbx@openadk.org&gt;
Cc: Thomas Petazzoni &lt;thomas.petazzoni@bootlin.com&gt;
Cc: Peter Korsgaard &lt;peter@korsgaard.com&gt;
Reviewed-by: Matt Weber &lt;matthew.weber@rockwellcollins.com&gt;
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>system: update Config.in comment about systemd dependencies</title>
<updated>2018-09-14T22:05:48+00:00</updated>
<author>
<name>Thomas Petazzoni</name>
<email>thomas.petazzoni@bootlin.com</email>
</author>
<published>2018-09-12T14:17:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=3c631c741c35f4afd9c7b6a41bcbcae40ecf8d49'/>
<id>urn:sha1:3c631c741c35f4afd9c7b6a41bcbcae40ecf8d49</id>
<content type='text'>
In commit 879fa7f82a86ffdc6d1cf7c9bfbb5cf830583d69, the
BR2_INIT_SYSTEMD option was changed to allow selecting with a uClibc
toolchain. Unfortunately, the corresponding Config.in comment, which
was already bogus, was not updated to take into account the numerous
dependencies of BR2_INIT_SYSTEMD.

Due to this, even if you have uClibc enabled, the BR2_INIT_SYSTEMD
option may not be visible, and the Config.in comment may also not be
visible, leaving the user in the dark.

This commit fixes the dependencies of the Config.in comment so that
they match the one of the BR2_INIT_SYSTEMD option.

Reported-by: Raphael Jacob &lt;r.jacob2002@gmail.com&gt;
Cc: Raphael Jacob &lt;r.jacob2002@gmail.com&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@bootlin.com&gt;
</content>
</entry>
<entry>
<title>skeleton: PAGER without blank and unset at end of for loop</title>
<updated>2018-06-05T16:50:49+00:00</updated>
<author>
<name>Florian La Roche</name>
<email>F.LaRoche@pilz.de</email>
</author>
<published>2018-06-05T13:47:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=903b8446a8db2aff042cdefd398d3598023bed0c'/>
<id>urn:sha1:903b8446a8db2aff042cdefd398d3598023bed0c</id>
<content type='text'>
The PAGER environment variable is including a blank character at the
end. Remove this.
A for loop has been unsetting the variable inside the loop, this is only
needed once at the end of the loop.

Signed-off-by: Florian La Roche &lt;F.LaRoche@pilz.de&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@bootlin.com&gt;
</content>
</entry>
<entry>
<title>skeleton: add /dev/fd, /dev/std{in, out, err} symlinks for static /dev on readonly rootfs</title>
<updated>2018-05-01T19:53:45+00:00</updated>
<author>
<name>Peter Korsgaard</name>
<email>peter@korsgaard.com</email>
</author>
<published>2018-05-01T19:41:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=2b21ba2fac486cf550399be7e6247de4e269595a'/>
<id>urn:sha1:2b21ba2fac486cf550399be7e6247de4e269595a</id>
<content type='text'>
Some applications, e.g. bashs process subsitution feature, rely on the
convention of `/dev/fd` being a symbolic link to `/proc/self/fd`.

When a static /dev is used on a readonly rootfs then the runtime ln
invocations in the inittab will fail, so we need to add the symlinks at
build time.  Makedevs doesn't support creating symlinks, so instead add the
symlinks to the default skeleton.

For non-static /dev setups, the kernel will mount devtmpfs which shadows the
/dev of the rootfs, but then the runtime ln invocations in inittab will
create the symlinks.

Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
</feed>
