summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-October/009239.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-October/009239.html')
-rw-r--r--zarb-ml/mageia-dev/2011-October/009239.html139
1 files changed, 139 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-October/009239.html b/zarb-ml/mageia-dev/2011-October/009239.html
new file mode 100644
index 000000000..4b437e161
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-October/009239.html
@@ -0,0 +1,139 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Please test: initscripts+systemd in updates_testing
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Please%20test%3A%20initscripts%2Bsystemd%20in%20updates_testing&In-Reply-To=%3C1320077259.2218.22.camel%40localhost%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="009229.html">
+ <LINK REL="Next" HREF="009242.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Please test: initscripts+systemd in updates_testing</H1>
+ <B>Michael Scherer</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Please%20test%3A%20initscripts%2Bsystemd%20in%20updates_testing&In-Reply-To=%3C1320077259.2218.22.camel%40localhost%3E"
+ TITLE="[Mageia-dev] Please test: initscripts+systemd in updates_testing">misc at zarb.org
+ </A><BR>
+ <I>Mon Oct 31 17:07:39 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="009229.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing
+</A></li>
+ <LI>Next message: <A HREF="009242.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#9239">[ date ]</a>
+ <a href="thread.html#9239">[ thread ]</a>
+ <a href="subject.html#9239">[ subject ]</a>
+ <a href="author.html#9239">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le dimanche 30 octobre 2011 &#224; 14:19 +0200, Thomas Backlund a &#233;crit :
+&gt;<i> Colin Guthrie skrev 30.10.2011 13:26:
+</I>&gt;<i> &gt; 'Twas brillig, and Thomas Backlund at 29/10/11 21:13 did gyre and gimble:
+</I>&gt;<i>
+</I>&gt;<i> &gt;&gt; So?
+</I>&gt;<i> &gt;&gt; it's less impact on / than stuffing all of /usr on /
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; I don't understand what point you're trying to make here. You'd be
+</I>&gt;<i> &gt; moving a whole bunch of stuff to /... And it becomes very tricky to
+</I>&gt;<i> &gt; administer exactly what to move to / as the dependencies are non-trivial
+</I>&gt;<i> &gt; to work out, the QA burden is very high to test all the various
+</I>&gt;<i> &gt; combinations of setups to ensure all the required bits have been moved to /
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; After doing all that QA and ensuring all is well, then the whole
+</I>&gt;<i> &gt; separate of /usr and / is totally blurred anyway. As someone campaigning
+</I>&gt;<i> &gt; to keep /usr on a separate partition, I'd have thought this was what you
+</I>&gt;<i> &gt; were trying to protect against in the first place... it seems totally
+</I>&gt;<i> &gt; contradictory to suggest this as a solution.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Keep in mind that one of the key aims in highlighting this issue via
+</I>&gt;<i> &gt; systemd is to actually ALLOW /usr to be a useful and self contained
+</I>&gt;<i> &gt; filesystem. If /usr is properly configured without leaking half of it to
+</I>&gt;<i> &gt; / it could be shared across multiple machines far more easily or even
+</I>&gt;<i> &gt; mounted as ro by default which could prove handy for security. Again,
+</I>&gt;<i> &gt; this is about highlighting the issues with an aim to making /usr much
+</I>&gt;<i> &gt; more useful. This is a laudable aim but you seem to be shooting it down
+</I>&gt;<i> &gt; due to gut reactions and prejudice. I've not yet seen any technical
+</I>&gt;<i> &gt; arguments from you about the topic.
+</I>&gt;<i> &gt;
+</I>&gt;<i>
+</I>&gt;<i> I'm saying moving the stuff that is _really_ needed, not based on &quot;udev
+</I>&gt;<i> might run&quot;...
+</I>&gt;<i>
+</I>&gt;<i> well, thinking some more on it I guess the real design flaw (not systemd
+</I>&gt;<i> specific) is using all of udev in init. Init should not care about more
+</I>&gt;<i> than getting disc access (and probably network for pxe boots)
+</I>
+That's the point that Lennart make, ie :
+&quot;we used to have / to mount all partition and /usr to be mounted, now,
+we have initramfs to mount /, and then / to mount /usr, so it would be
+simpler to merge / and /usr&quot;
+
+So that's simple. For stuff needed for initial boot, we have initrd, for
+the rest, that's /usr/
+
+<A HREF="http://www.spinics.net/lists/fedora-devel/msg158642.html">http://www.spinics.net/lists/fedora-devel/msg158642.html</A>
+
+&gt;<i> Then we wouldn't have to worry about &quot;what udev might run&quot; and could
+</I>&gt;<i> keep a very clean /
+</I>&gt;<i>
+</I>&gt;<i> &gt;&gt; Well, it _is_ idiotic if it breaks working setups / possibilities to
+</I>&gt;<i> &gt;&gt; finetune systems.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; It depends on your definition of &quot;working&quot;. Sure if you specifically
+</I>&gt;<i> &gt; work around the know limitations of the design then you may get a
+</I>&gt;<i> &gt; bootable system, which you could classify as working, but I wouldn't say
+</I>&gt;<i> &gt; this is a robust base. Just a house of cards waiting for the next
+</I>&gt;<i> &gt; failure. I'd rather try and address the problems properly and be frank
+</I>&gt;<i> &gt; about it in the discussions.
+</I>&gt;<i> &gt;
+</I>&gt;<i>
+</I>&gt;<i> Well, it has worked 24/7 for servers for atleast last 15 years for
+</I>&gt;<i> servers I maintain, so I'd say that is pretty robust.
+</I>
+That's also what people say about manually compiling software in
+solaris, and I think they are wrong, so that's not really a compeling
+argument to my eyes.
+
+In fact &quot;using packages prevent me from finetuning my software&quot; is also
+a common and recuring theme from the same people ( well, slightly less
+recuring nowadays as I didn't meet people telling me so since gentoo and
+slackware usage slightly dropped ).
+
+We have unix server since 1970, that doesn't mean the assumption that
+lead to some design decision are not open to be revisited.
+--
+Michael Scherer
+
+</PRE>
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="009229.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing
+</A></li>
+ <LI>Next message: <A HREF="009242.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#9239">[ date ]</a>
+ <a href="thread.html#9239">[ thread ]</a>
+ <a href="subject.html#9239">[ subject ]</a>
+ <a href="author.html#9239">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>