<feed xmlns='http://www.w3.org/2005/Atom'>
<title>buildroot/fs, branch 2017.02.2</title>
<subtitle>OpenPOWER buildroot sources</subtitle>
<id>https://git.raptorcs.com/git/buildroot/atom?h=2017.02.2</id>
<link rel='self' href='https://git.raptorcs.com/git/buildroot/atom?h=2017.02.2'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/'/>
<updated>2017-03-02T07:20:38+00:00</updated>
<entry>
<title>fs/iso9660: doesn't support (grub2) EFI</title>
<updated>2017-03-02T07:20:38+00:00</updated>
<author>
<name>Arnout Vandecappelle</name>
<email>arnout@mind.be</email>
</author>
<published>2017-03-01T20:05:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=b73c73d802366adc90128d6034fb16428ad08029'/>
<id>urn:sha1:b73c73d802366adc90128d6034fb16428ad08029</id>
<content type='text'>
The iso9660 generation for grub2 assumes that grub-eltorito.img is
available. However, this image is only available for the i386-pc target
(i.e. legacy BIOS). An EFI-bootable iso9660 requires a different layout.

Since we currently can't generate the EFI-bootable iso9660 layout,
require the i386-pc target to be selected in grub.

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) &lt;arnout@mind.be&gt;
Reported-by: arnaud.miche@orange.com
Reviewed-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
(cherry picked from commit 3e57fa370cb8e4d5f80c6abb34671f0c0467e506)
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>fs/tar: make --no-recursion effective</title>
<updated>2016-12-28T09:13:21+00:00</updated>
<author>
<name>Baruch Siach</name>
<email>baruch@tkos.co.il</email>
</author>
<published>2016-12-27T17:42:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=d91ce1aa08016fa3fb186be9e6ef425dad6f050f'/>
<id>urn:sha1:d91ce1aa08016fa3fb186be9e6ef425dad6f050f</id>
<content type='text'>
The tar --no-recursion option is position sensitive. It only affects following
file listing options. Move --no-recursion before the -T option to make it
effective. This fixes duplication of entries in the generated rootfs.tar
archive.

Signed-off-by: Baruch Siach &lt;baruch@tkos.co.il&gt;
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>fs: set packages permissions even with no system device tables</title>
<updated>2016-12-14T22:45:48+00:00</updated>
<author>
<name>Yann E. MORIN</name>
<email>yann.morin.1998@free.fr</email>
</author>
<published>2016-12-14T22:28:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=5b272e3e551e723bae78140f7de4029b9026d961'/>
<id>urn:sha1:5b272e3e551e723bae78140f7de4029b9026d961</id>
<content type='text'>
Currently, when there is no syztem device table (permissions or static
devices) defined, then package permissions are not applied, because they
are guarded by the check on the system device tables being non empty.

Fix that by narrowing the guarding condition.

Note that the dependency on host-makedevs was not conditional; we always
build it even if we don't need it. Making it conditional is not
possible, because we don't know all the packages permissions by the time
the fs infra is parsed (packages from br2-external are parsed after it).

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;
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>fs/ext2: default to ext2 rev1</title>
<updated>2016-12-14T14:59:38+00:00</updated>
<author>
<name>Peter Korsgaard</name>
<email>peter@korsgaard.com</email>
</author>
<published>2016-12-13T08:18:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=219d0b5db2b9f36c34d750e5c3567f9002eed9db'/>
<id>urn:sha1:219d0b5db2b9f36c34d750e5c3567f9002eed9db</id>
<content type='text'>
Rev0 is very old (E.G. from before Linux was maintained in git), the kernel
prints a scary warning when used:

EXT4-fs warning (device sda): ext4_update_dynamic_rev:746: updating to rev 1
because of new feature flag, running e2fsck is recommended

And rev0 support is broken in u-boot 2016.11:
http://lists.denx.de/pipermail/u-boot/2016-December/275916.html

So default to rev1 instead.

Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'next'</title>
<updated>2016-12-01T21:29:56+00:00</updated>
<author>
<name>Peter Korsgaard</name>
<email>peter@korsgaard.com</email>
</author>
<published>2016-12-01T21:22:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=8852f08eeda3c9ff4c5f9cc90a169338bda1bff9'/>
<id>urn:sha1:8852f08eeda3c9ff4c5f9cc90a169338bda1bff9</id>
<content type='text'>
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>Revert "fs: use pseudo instead of fakeroot"</title>
<updated>2016-11-27T20:24:10+00:00</updated>
<author>
<name>Peter Korsgaard</name>
<email>peter@korsgaard.com</email>
</author>
<published>2016-11-27T20:13:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=79061fe52f9cf5925f603d938feddfe41aab340e'/>
<id>urn:sha1:79061fe52f9cf5925f603d938feddfe41aab340e</id>
<content type='text'>
This reverts commit 8035ceb56cc3ba2541aba0d0ead3f29900d9e310.

Moving to pseudo brought a number of issues (and longer compilation time),
so lets stick with fakeroot now that the reported ubi issue has been worked
around.

Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>Revert "fs: call the pseudo wrapper"</title>
<updated>2016-11-27T20:12:23+00:00</updated>
<author>
<name>Peter Korsgaard</name>
<email>peter@korsgaard.com</email>
</author>
<published>2016-11-27T20:11:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=9b2f9b137ce14bbca01f18c3a4357bd3219a6b9f'/>
<id>urn:sha1:9b2f9b137ce14bbca01f18c3a4357bd3219a6b9f</id>
<content type='text'>
This reverts commit 74a3e75bb8208a8f3bb8426549fce1ea09b3be8a.

Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>fs/ubifs: work around fakeroot / sed -i issue on systems with SELinux enabled</title>
<updated>2016-11-27T19:31:37+00:00</updated>
<author>
<name>Peter Korsgaard</name>
<email>peter@korsgaard.com</email>
</author>
<published>2016-11-26T23:40:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=01354e1a0f4333ffee40a20260a5689e3846560c'/>
<id>urn:sha1:01354e1a0f4333ffee40a20260a5689e3846560c</id>
<content type='text'>
Fixes #9386

GNU sed -i misbehaves on systems with SELinux enabled, as it tries to copy
to the SELinux security context (xattr) from the source file to to the new
destination file, which fails under fakeroot and leaves the file with 000
permissions, causing ubinize to fail when it cannot read to configuration
file.

So as a workaround, combine the install and tweak steps in a single
sed with a redirect to the destination file instead.

Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>fs/common: lock modification times in $TARGET_DIR</title>
<updated>2016-11-23T21:59:21+00:00</updated>
<author>
<name>Jérôme Pouiller</name>
<email>jezz@sysmic.org</email>
</author>
<published>2016-11-23T12:58:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=68db7210fd8e76120c27cdc4a1fe591de67c06c2'/>
<id>urn:sha1:68db7210fd8e76120c27cdc4a1fe591de67c06c2</id>
<content type='text'>
Make sure all files in $TARGET_DIR have a defined modification time
before to generate filesystems.

This work was sponsored by `BA Robotic Systems'.

Signed-off-by: Jérôme Pouiller &lt;jezz@sysmic.org&gt;
Reviewed-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) &lt;arnout@mind.be&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
</content>
</entry>
<entry>
<title>fs/tar: make results reproducible</title>
<updated>2016-11-23T21:55:34+00:00</updated>
<author>
<name>Jérôme Pouiller</name>
<email>jezz@sysmic.org</email>
</author>
<published>2016-11-23T12:58:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=59f9c4ca9feb2c070df508c7196f06a6e87307b4'/>
<id>urn:sha1:59f9c4ca9feb2c070df508c7196f06a6e87307b4</id>
<content type='text'>
In order to make tar images reproducible, force files order in tarball.

This work was sponsored by `BA Robotic Systems'.

Signed-off-by: Jérôme Pouiller &lt;jezz@sysmic.org&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
</content>
</entry>
</feed>
