Re: [PATCH 4/4] Set ANACONDA=1 in the udev environment early in anaconda.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/14/2011 07:24 PM, Chris Lumens wrote:
We need this so udev will trigger all our special rules, since we are no
longer starting udev ourselves and there's no clean way to add this into the
systemd service file.
---
  anaconda |    2 ++
  1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/anaconda b/anaconda
index cddb581..dadcba4 100755
--- a/anaconda
+++ b/anaconda
@@ -827,6 +827,8 @@ if __name__ == "__main__":
      log.info("Default encoding = %s " % sys.getdefaultencoding())
      setupDisplay(anaconda, opts)

+    os.system("udevadm control --env=ANACONDA=1")
+

Hi,

I'm just wondering, isn't it too late for this in anaconda? We depend on udev to detect the devices in loader (see hardware.c:detectHardware) and before systemd we set this in init.c. The question is if we need those rules so early or not.

If this is about some kind of systemd concurrency business then I think systemd should provide something that will let us to wait for the udev daemeon to be up before we call detectHardware() for the first time.

Ales

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux