This revision patches the source file 'rngd_entsource.c', adding 'O_NOCTTY'
flag to the open() call that opens the entropy source for rngd.
Gentoo-Bug: https://bugs.gentoo.org/556456
Package-Manager: portage-2.2.20.1
Linux hw_random driver provides a unified interface for multiple RNGs
and the RNG source is exposed through /dev/hwrng device node. There is
no need for the init script to look for other device nodes under
/dev. By default, rngd uses /dev/hwrng as the entropy source,
therefore it's not required to specify it on the command line
explicitly.
The creation of /dev/hwrng requires CONFIG_DEVTMPFS support in the
kernel. Due to the way hw_random module is written, some device
managers may fail to create /dev/hwrng successfuly. Mdev, for example,
incorrectly creates /dev/hw_random instead of /dev/hwrng, mistaking
module's own name for the device node's name (see related bug
561102). However, per gentoo wiki [1], CONFIG_DEVTMPFS is part of the
mdev setup and these systems will have two device nodes
(/dev/hw_random and /dev/hwrng) that point to the same device. Even in
such setups, rngd will successfuly find /dev/hwrng.
[1] https://wiki.gentoo.org/index.php?title=Mdev&oldid=246636
Gentoo-Bug: https://bugs.gentoo.org/481254
Package-Manager: portage-2.2.20.1
rngd-initd-r1-4.1 has been created as a result of the patch
proposed for bug 481254. However, one chunk has been missed
and did not make it to the commit.
The variable DEFAULT_DEVICE isn't used by the init script.
Remove the related lines from the script.
Package-Manager: portage-2.2.20.1
New maintainer added & supported under the proxy-maintainers herd, testing
and revision carried out thanks also to wraeth, fix to broken .png file
applied according to past bug #466190 supplied by Blackb|rd, all patches and
revisons of ebuilds supplied via bug cited below, releases after -3.2.12
skipped, holding off from beta versions of version 5.x for now, removed old
versions prior to -3.2.12. Finally closes the gentoo bug.
Gentoo-Bug: 506052
Package-Manager: portage-2.2.20.1
Upstream release notes:
https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.5.2
Some additional improvements were made to the ebuilds in this bump.
1. The incorrect requirement on BLK_DEV_LOOP was removed from sys-fs/zfs-kmod
in favor of a cups ebuild style warning in sys-fs/zfs when BLK_DEV_LOOP is not
avaliable and the test suite has been installed.
2. The regression where we remove the dracut module has been fixed.
3. The failure to migrate users to the zfs-zed script from the zed script has
been fixed.
4. The 9999 ebuilds have been synchronized with the 0.6.5.2 ebuilds.
5. The sys-fs/zfs-kmod-0.6.5 has been removed due to the regression that
prompted sys-fs/zfs-kmod-0.6.5-r1.
Package-Manager: portage-2.2.20.1
Signed-off-by: Richard Yao <ryao@gentoo.org>
USE flags that are not available for an arch should be masked in their
profile, not have ad-hoc checks in ebuilds. Since the arm profile was
updated at some point to mask USE=glusterfs, we can drop the wrong code
in these ebuilds.
Justin Lecher
Julian Ospald
Patrice Clement
Gokturk Yuksek
Lars Wendler
Agostino Sarubbo
Hans de Graaff
Ian Delaney
Richard Yao
Mike Frysinger