summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2013-January/021747.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2013-January/021747.html')
-rw-r--r--zarb-ml/mageia-dev/2013-January/021747.html146
1 files changed, 146 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-January/021747.html b/zarb-ml/mageia-dev/2013-January/021747.html
new file mode 100644
index 000000000..225721b79
--- /dev/null
+++ b/zarb-ml/mageia-dev/2013-January/021747.html
@@ -0,0 +1,146 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] GRUB can't see HD from chroot unless parent /dev is bind-mounted in chroot ?
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20GRUB%20can%27t%20see%20HD%20from%20chroot%20unless%20parent%20/dev%0A%20is%20bind-mounted%20in%20chroot%20%3F&In-Reply-To=%3C50F7C837.6070307%40colin.guthr.ie%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="021739.html">
+ <LINK REL="Next" HREF="021748.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] GRUB can't see HD from chroot unless parent /dev is bind-mounted in chroot ?</H1>
+ <B>Colin Guthrie</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20GRUB%20can%27t%20see%20HD%20from%20chroot%20unless%20parent%20/dev%0A%20is%20bind-mounted%20in%20chroot%20%3F&In-Reply-To=%3C50F7C837.6070307%40colin.guthr.ie%3E"
+ TITLE="[Mageia-dev] GRUB can't see HD from chroot unless parent /dev is bind-mounted in chroot ?">mageia at colin.guthr.ie
+ </A><BR>
+ <I>Thu Jan 17 10:45:27 CET 2013</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="021739.html">[Mageia-dev] GRUB can't see HD from chroot unless parent /dev is bind-mounted in chroot ?
+</A></li>
+ <LI>Next message: <A HREF="021748.html">[Mageia-dev] GRUB can't see HD from chroot unless parent /dev is bind-mounted in chroot ?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#21747">[ date ]</a>
+ <a href="thread.html#21747">[ thread ]</a>
+ <a href="subject.html#21747">[ subject ]</a>
+ <a href="author.html#21747">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>'Twas brillig, and Bruno Cornec at 16/01/13 23:41 did gyre and gimble:
+&gt;<i> Colin Guthrie said on Wed, Jan 16, 2013 at 09:17:46PM +0000:
+</I>&gt;<i>
+</I>&gt;&gt;&gt;<i> C) of course, udev is not inside systemd, so it appears the new way is now to
+</I>&gt;&gt;&gt;<i> somehow spawn a systemd process inside the chroot (maybe systemd-nspawn?)
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Personally I think that's overkill.
+</I>&gt;<i>
+</I>&gt;<i> +1 and systemd works badly with chrooted prcesses itself as I
+</I>&gt;<i> experienced recently with squid :-( I'd like to have more time to
+</I>&gt;<i> experiment with LXC, maybe a easier solution for systemd usage (but not
+</I>&gt;<i> for what you tried to achieve).
+</I>
+Perhaps squid is not configured right, but systemd works very well with
+chrooted processes - it's one of the core features to make chrooting
+easier and prevent the need for boiler plate setup in numerous packages.
+That said some changes may be required to make best use of this.
+
+See part 6 in the (currently) 20 part series of blog posts regarding
+systemd for administrators:
+
+<A HREF="http://0pointer.de/blog/projects/changing-roots.html">http://0pointer.de/blog/projects/changing-roots.html</A>
+
+(for full list see here:
+<A HREF="http://www.freedesktop.org/wiki/Software/systemd">http://www.freedesktop.org/wiki/Software/systemd</A> and look for &quot;The
+systemd for Administrators Blog Series&quot;)
+
+
+Depending on the need for access to socket paths (e.g. for unix sockets)
+then the /run on tmpfs can cause some problems (e.g. with cyrus-sasl
+auth and chrooted postfix - previously hardlinks were used to allow the
+chroot and host to see the &quot;same&quot; socket, but this was hacky at best as
+there was no guarantee the chroot and host were on the same filesystem -
+now they are guaranteed not to be on the same fs).
+
+
+If you would like to detail the problems with squid and point at a
+detailed bug report I can take a look or at least advise on the best
+steps to take to get a really solid system.
+
+Col
+
+
+
+--
+
+Colin Guthrie
+colin(at)mageia.org
+<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
+
+Day Job:
+ Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
+Open Source:
+ Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
+ PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
+ Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="021739.html">[Mageia-dev] GRUB can't see HD from chroot unless parent /dev is bind-mounted in chroot ?
+</A></li>
+ <LI>Next message: <A HREF="021748.html">[Mageia-dev] GRUB can't see HD from chroot unless parent /dev is bind-mounted in chroot ?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#21747">[ date ]</a>
+ <a href="thread.html#21747">[ thread ]</a>
+ <a href="subject.html#21747">[ subject ]</a>
+ <a href="author.html#21747">[ 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>