* checksec.sh: Updated to 1.11.1
* checksec.sh: resolved issues with readelf
* checksec.sh: Added docker images for testing
* checksec.sh: Added armhf and aarch64 libc locations
* checksec.sh: Replace FS_COUNT with fgrep
* checksec.sh: Fixed symbols count in csv
* checksec.sh: Fixed RW-RPATH and
Hi,
Upon further inspection, I found a previous commit that appears to
have a bit more information:
python: Restructure python packaging and replace it with autopackaging
(http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=8d94b9db221d1def42f091b991903faa2d1651ce)
The following text appears
Hello,
I upgraded to Sumo(2.5) and now bitbake is complaining that nothing
rprovides python3-signal.
ERROR: Nothing RPROVIDES 'python3-signal' (but
/home/worker/building/sources/meta-bluetooth/recipes-bluetooth/bluetooth-app/bluetooth-app.bb
RDEPENDS on or otherwise requires it)
After some
Hi Bruce,
Both these changes are only for master and are specific to v5.1.
On Thu, 2019-05-16 at 10:26 +0800, Anuj Mittal wrote:
> This has been removed starting v5.1 and nf_nat_ipv4,6 have been
> merged
> in nat core.
>
>
This has been removed starting v5.1 and nf_nat_ipv4,6 have been merged
in nat core.
https://github.com/torvalds/linux/commit/3bf195ae6037e310d693ff3313401cfaf1261b71
Signed-off-by: Anuj Mittal
---
features/netfilter/netfilter.cfg | 1 -
1 file changed, 1 deletion(-)
diff --git
These have been removed and are now controlled by CONFIG_FS_ENCRYPTION
which is enabled by standard/preempt-rt.cfg.
https://github.com/torvalds/linux/commit/643fa9612bf1a29153eee46fd398117632f93cbe
Signed-off-by: Anuj Mittal
---
cfg/fs/ext4.cfg | 2 --
1 file changed, 2 deletions(-)
diff
Glad to hear that it works now. I am planning on attending the YP DevDay.
:rjs
On Wed, May 15, 2019, 13:53 Greg Wilson-Lindberg
wrote:
> Thank you very much, that got me back on the right path.
>
> Maybe I'll see you at the Yocto day at the Embedded Linux Conference.
>
> Regards,
>
> [image:
Bruce, Yocto kernel folks:
Here is the next 4.18.x stable update "extension" primarily created
for the Yocto project, continuing from the previous v4.18.37 release.
There is one trivial one line commit to fix a build error on PPC64 from
the MDS patches of v4.18.37 - which was also present in
Hi!
I'm facing some trouble with the X-Server on the Raspberry Pi 3 B+. No
matter if I use a screen on the HDMI port or running the 7" touch screen,
they remain black. After testing with sumo - where at least a splash screen
was shown - I moved on to thud, as recommended by Andrei Gherzan to sort
On Wed, May 15, 2019 at 4:09 PM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> > The core-image-kernel-dev image is how I do all my on target
> > testing when I introduce a new reference kernel for a release.
>
> Maybe you are correct. Maybe I should use/add in my local.conf the
>
Thank you very much, that got me back on the right path.
Maybe I'll see you at the Yocto day at the Embedded Linux Conference.
Regards,
Greg Wilson-Lindberg
Principal Firmware Engineer | Sakura Finetek USA, Inc.
1750 W 214th Street | Torrance, CA 90501 | U.S.A.
T: +1 310 783 5075
F: +1 310
Instead of
useradd -p `openssl passwd test` sakura
which attempts to add the user and set the password which fails if the
user already exists, use
usermod -p `openssl passwd test` sakura
which sets the user's password.
:rjs
On 5/15/19 1:18 PM, Greg Wilson-Lindberg wrote:
Ok, I had
Ok, I had been using the useradd class in a couple of other recipes to allow me
to copy files to the sakura user directory and another location, but owned by
sakura. That seems to have been what was causing the problem.
I had been using the extrausers class in my top level image recipe.
So
> The core-image-kernel-dev image is how I do all my on target
> testing when I introduce a new reference kernel for a release.
Maybe you are correct. Maybe I should use/add in my local.conf the following:
KERNEL_DEV_TOOLS ?= "packagegroup-core-tools-profile
packagegroup-core-buildessential
The ! for the password in /etc/shadow indicates that the account is
disabled:
sakura:!:18031:0:9:7:::
Either there is something wrong with the password generation or it gets
disabled by something else. Maybe it's worth trying with a plain image
without Boot2Qt or anything else.
:rjs
Hi Rudolf,
1st, yes I inherit extrausers. Attached are the passwd & shadow files.
It shouldn't make any difference, but I'm building this for an RPi3 using the
Qt Boot2Qt version of the Yocto environment, distro 2.5.3.
Greg
From: Rudolf J Streif
Sent:
Hi Greg,
> I've also tried both the back-quote and the single-quote, no difference.
Help me to understand this. the back-quotes are the right ones. If you
use the single ones your password in the /etc/shadow ends up being
'openssl passwd test' (without the quotes), unless the build fails
Hi Rudolf,
Thanks for the reply, and the information on how openssl works.
I'm trying to create a user with the same group name so the code that I'm using
reduces to:
EXTRA_USERS_PARAMS = "\
useradd -p `openssl passwd test` sakura; \
usermod -a -G sudo ${SAKURA_USER}; \
"
I
Hi Greg,
Well, I suppose I wrote the book you are referring to...
Using
useradd -p PASSWORD USER
takes the password hash for PASSWORD hence the use of openssl in:
useadd -p `openssl passwd PASSWORD` USER
openssl password creates the password hash using the original crypt hash
algorithm if
On Wed, May 15, 2019 at 3:44 AM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> > That's correct. That command only adds the kernel source and
> > build infrastructure to the SDK, not to your target image. *You'd still*
> *> need to arrange to have the kernel-devsrc package
Hi all,
I need to include in my native sdk the ODB compiler in order to produce
some sources. Since it is a nativesdk- only package, I wrote the following
nativesdk-odb-compiler_2.5.0.bb
On Wed, May 15, 2019 at 1:47 PM Belisko Marek
wrote:
> Hi,
>
> I'm trying to update some artifact after image is build using wic tool.
> I've tried wic rm image.wic:2/boot/uImage and this works fine (verified
> with wic ls). While when I want to copy something to ext4 partition (I've
> tried to
Hi,
I'm trying to update some artifact after image is build using wic tool.
I've tried wic rm image.wic:2/boot/uImage and this works fine (verified
with wic ls). While when I want to copy something to ext4 partition (I've
tried to copy to vfat boot partition and it works fine) like:
wic cp
I see that my custom layers are not being copied in
/sdk-ext/image/opt/${DISTRO}/${POKY_VERSION}/layers. Though
the conf files at
/sdk-ext/image/opt/${DISTRO}/${POKY_VERSION}/conf.
How can I include my layers also in this?
Warm Regards,
Priyanshu Sharma
On Thu, May 2, 2019 at 3:12 PM Priyanshu
> That's correct. That command only adds the kernel source and
> build infrastructure to the SDK, not to your target image. *You'd still*
*> need to arrange to have the kernel-devsrc package installed on the*
*> target image if you want it on the board's rootfs.* How you arrange
> to have the
25 matches
Mail list logo
