public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.x - Switching to udev from systemd
Date: Thu, 26 Oct 2023 10:00:01 +0100	[thread overview]
Message-ID: <5BD94CC3-3EC9-45D5-88FA-45ACB155B7DC@ipfire.org> (raw)
In-Reply-To: <20231021173809.3530-1-stefan.schantl@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]

Hello Stefan,

Thank you for working on this so swiftly.

I would like to merge this into Core Update 181, because I feel quite confident about this.

There should not be any major differences between the former eudev and this version, so let’s be brave and roll it out quickly.

Please see my comment on a required change on one of the patches. Otherwise I feel that this is good to be merged.

-Michael

> On 21 Oct 2023, at 18:38, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
> 
> Hello devopment folks,
> 
> the eudev project got abandoned by the main development team some time ago.
> 
> See: https://gitweb.gentoo.org/proj/eudev.git/commit/?id=f559dc96f4105f605272defac9276ef9cb6f5dc6
> 
> Currently this old code base works very well on our systems, but we are getting troubles to compile
> some newer sort of software with it. The second very important point is
> we need a maintainded udev code base again.
> 
> Sadly the only remaining udev code base is the officiall one, which got
> part of systemd and as a result of the pointed issues above the
> following patch series aims to bring a maintained udev back to IPFire.
> 
> The first two patches will add some additional packages which are
> required by the build system.
> 
> The third patch will adjust the LFS file to build udev from the systemd
> source code as minimal as possible (all systemd stuff is stripped).
> 
> The last patch will adjust the build order of some packages to get udev
> and depending packages build.
> 
> The new version of udev successfully has been compiled and tested in a
> virtual environment (KVM) which worked well.
> 
> Because udev is a very critical part of the boot process, this changes
> have to be tested very well until we can merge this patchset.
> 
> Please help testing and share your feedback.
> 
> Best regards,
> 
> -Stefan
> 
> 


      parent reply	other threads:[~2023-10-26  9:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21 17:38 Stefan Schantl
2023-10-21 17:38 ` [PATCH 1/4] python3-MarkupSafe: New package Stefan Schantl
2023-10-26  8:58   ` Michael Tremer
2023-10-29 18:21     ` Stefan Schantl
2023-10-30 10:00       ` Michael Tremer
2023-10-21 17:38 ` [PATCH 2/4] python3-Jinja2: " Stefan Schantl
2023-10-21 17:38 ` [PATCH 3/4] udev: Switch to udev from systemd Stefan Schantl
2023-10-21 17:38 ` [PATCH 4/4] make.sh: Adjust build order to proper build udev (systemd) Stefan Schantl
2023-10-26  9:00 ` Michael Tremer [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=5BD94CC3-3EC9-45D5-88FA-45ACB155B7DC@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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