blob: 225721b799f1f7805e115168da3e41eba7458312 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
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:
><i> Colin Guthrie said on Wed, Jan 16, 2013 at 09:17:46PM +0000:
</I>><i>
</I>>>><i> C) of course, udev is not inside systemd, so it appears the new way is now to
</I>>>><i> somehow spawn a systemd process inside the chroot (maybe systemd-nspawn?)
</I>>><i>
</I>>><i> Personally I think that's overkill.
</I>><i>
</I>><i> +1 and systemd works badly with chrooted prcesses itself as I
</I>><i> experienced recently with squid :-( I'd like to have more time to
</I>><i> experiment with LXC, maybe a easier solution for systemd usage (but not
</I>><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 "The
systemd for Administrators Blog Series")
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 "same" 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>
|
