From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20110424/004165.html | 76 +++++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110424/004165.html (limited to 'zarb-ml/mageia-dev/20110424/004165.html') diff --git a/zarb-ml/mageia-dev/20110424/004165.html b/zarb-ml/mageia-dev/20110424/004165.html new file mode 100644 index 000000000..b9017aaa4 --- /dev/null +++ b/zarb-ml/mageia-dev/20110424/004165.html @@ -0,0 +1,76 @@ + + + + [Mageia-dev] How should an init script determine if it is being run during install or regular boot? + + + + + + + + + +

[Mageia-dev] How should an init script determine if it is being run during install or regular boot?

+ David W. Hodgins + davidwhodgins at gmail.com +
+ Sun Apr 24 19:38:46 CEST 2011 +

+
+ +
+The patch submitted for the named init script in
+https://bugs.mageia.org/show_bug.cgi?id=871
+fixes the problem of the openssl engines not being
+available in the chroot environment, during a normal
+bootup, however during an upgrade using the beta 2
+pre-release iso's, it fails as the init script is
+using absolute path names.
+
+While I can submit a new patch that checks to see
+if /var/lib/named or /mnt/var/lib/named exists, to
+determine if the script is running in an install or
+a normal bootup, I'm wondering if there is a "standard"
+way for an init script to determine which environment
+it's being run in.
+
+Regards, Dave Hodgins
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1