From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: MOHAMMED HASSAN <hassanchattarki@gmail.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] continuous security updates for the Linux system
Date: Mon, 9 Oct 2023 16:11:26 +0200 [thread overview]
Message-ID: <4c05da5d-9e30-4018-bef6-b40d91227157@bootlin.com> (raw)
In-Reply-To: <12652.1696857725620212439@lists.yoctoproject.org>
Hi Hassan
On 09.10.23 at 15:22, MOHAMMED HASSAN wrote:
> On Mon, Oct 9, 2023 at 06:12 AM, Josef Holzmayr wrote:
>
> Please see https://wiki.yoctoproject.org/wiki/System_Update
>
> Thanks for your reply. I am aware of the system_updates feature though
> still yet to implement. Is it possible to update the yocto version (i
> use dunfell) to the latest one, to update the linux version(mine is
> 5.4.180) to the latest and to update the tools to the latest using
> these features. Actually i have no clarity with this so I am asking.
Which version of Yocto are you using? If you have one that is still
supported (like Kirkstone or Dunfell), I'd recommend to stick to these
and just rebuild with the latest release update. This way you have the
latest vulnerability fixes supported by the Yocto Project. Once a new
image is generated, you can deploy it using one of the tools Josef
mentioned.
Moving to the latest version of Yocto will represent more work, all the
more as the latest one should be replaced this month.
As far as the Linux kernel is concerned, I'd rather work with a stable
LTS kernel (https://kernel.org/category/releases.html), as I guess the
Yocto Project releases can't match the stable kernels in terms of
vulnerability fixes and how quickly they are deployed. That's my own
opinion though.
I hope this helps
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-10-09 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 12:56 continuous security updates for the Linux system MOHAMMED HASSAN
2023-10-09 13:11 ` [yocto] " Josef Holzmayr
2023-10-09 13:22 ` MOHAMMED HASSAN
2023-10-09 14:02 ` [yocto] " adrian.freihofer
2023-10-09 14:11 ` Michael Opdenacker [this message]
2023-10-09 14:24 ` MOHAMMED HASSAN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c05da5d-9e30-4018-bef6-b40d91227157@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=hassanchattarki@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox