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
|
<!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=%3C4EAF021A.5020000%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="009246.html">
<LINK REL="Next" HREF="009245.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Please test: initscripts+systemd in updates_testing</H1>
<B>Colin Guthrie</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=%3C4EAF021A.5020000%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] Please test: initscripts+systemd in updates_testing">mageia at colin.guthr.ie
</A><BR>
<I>Mon Oct 31 21:16:26 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="009246.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing
</A></li>
<LI>Next message: <A HREF="009245.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9249">[ date ]</a>
<a href="thread.html#9249">[ thread ]</a>
<a href="subject.html#9249">[ subject ]</a>
<a href="author.html#9249">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and Thomas Backlund at 31/10/11 19:01 did gyre and gimble:
><i> Colin Guthrie skrev 31.10.2011 19:47:
</I>>>><i> Just have initramfs mount / and /usr, no need to merge.
</I>>><i>
</I>>><i> Yes, this is exactly what is intended, but it depends on the use case:
</I>>><i>
</I>><i>
</I>><i> Then I have misread something somewhere along the way... :/
</I>
Yeah the link Olav provided (
<A HREF="http://www.freedesktop.org/wiki/Software/systemd/separate-usr-is-broken">http://www.freedesktop.org/wiki/Software/systemd/separate-usr-is-broken</A>
) is certainly worth reading if you've not already done so. The "Going
Forward" section in particular starts with this quote:
"/usr on its own filesystem is useful in some custom setups. But instead
of expecting the traditional Unix way to (sometimes mindlessly)
distributing tools between /usr and /, and require more and more tools
to move to /, we now just expect /usr to be pre-mounted from inside the
initramfs, to be available before 'init' starts."
>><i> For simple installs, such as on my laptop or typical "desktop" linux,
</I>>><i> then having separate / and /usr is something I've specifically avoided
</I>>><i> for just about ever (I sometimes have separate /boot for "complicated
</I>>><i> rootfs" reasons and I almost always have a separate /home, but other
</I>>><i> than that, I like to keep my desktops/laptops simple). In other words
</I>>><i> there just are not sufficient benefits in doing this.
</I>><i>
</I>><i> Yes,
</I>><i> I agree for the desktop/laptop/pad/ use there is no need for splitting
</I>><i> besides /home and maybe separate /boot if you want to use encryption.
</I>
Nod
>><i> But on the server, especially on a farm of servers with a potentially
</I>>><i> shared /usr across several machines, then yes, keeping it as something
</I>>><i> that can be mounted by the initramfs is perfectly feasible. This is a
</I>>><i> specific use case that Lennart + Co are trying to design for.
</I>>><i>
</I>><i>
</I>><i> Ok, this is exactly the part that have raised my concerns that it was
</I>><i> about to be "forgotten" in favour of "simplicity".
</I>><i>
</I>><i> Server installs usually want to be more "free" to finetune.
</I>><i>
</I>><i> Another use case is to be able to split up the system on more harddisks
</I>><i> to even the load on the disks.
</I>><i>
</I>><i> And yet another is simply to get more space depending on hw.
</I>><i> (yes I know lvm exists but it's also an extra layer / point of failure
</I>><i> that is not always worth it)
</I>
Totally agree about LVM (and to a lesser degree the RAID layer)... I'm
looking forward to btrfs which merges in the RAID layers and (I think -
I've not fully read up on it) the LVM functionality too.
Currently, I've found performance really takes a hit with my RAID+LVM
setups... 40M/s write speeds where as just plain RAID was getting closer
to 160M/s... this is likely in part due to 4k sector sizes too of
course. But I digress!
><i> But if this part is the "some specific usecases" then I guess I need to
</I>><i> start re-reading some stuff :)
</I>
:<i>)
</I>
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="009246.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing
</A></li>
<LI>Next message: <A HREF="009245.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9249">[ date ]</a>
<a href="thread.html#9249">[ thread ]</a>
<a href="subject.html#9249">[ subject ]</a>
<a href="author.html#9249">[ 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>
|
