From: "MOHAMMED HASSAN" <hassanchattarki@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: Re: continuous security updates for the Linux system
Date: Mon, 09 Oct 2023 07:24:19 -0700 [thread overview]
Message-ID: <12652.1696861459372790739@lists.yoctoproject.org> (raw)
In-Reply-To: <4c05da5d-9e30-4018-bef6-b40d91227157@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]
On Mon, Oct 9, 2023 at 07:11 AM, Michael Opdenacker wrote:
>
> 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.
>
>
Hi Michael,
Thanks for your reply.
I am currently using dunfell 3.1.11 and my kernel release is Linux 5.4.180-amlogic. Going by your suggestion i should rebuild to the latest dunfell update i.e 3.1.28. Moving to kirkstone would take more work.
I will search on how to update my yocto release version and get into it.
Thanks
Hassan
[-- Attachment #2: Type: text/html, Size: 2185 bytes --]
prev parent reply other threads:[~2023-10-09 14:24 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
2023-10-09 14:24 ` MOHAMMED HASSAN [this message]
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=12652.1696861459372790739@lists.yoctoproject.org \
--to=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