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] /var/run after /usr/move
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20/var/run%20after%20/usr/move&In-Reply-To=%3C50C76458.1070505%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="020743.html">
<LINK REL="Next" HREF="020808.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] /var/run after /usr/move</H1>
<B>Colin Guthrie</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20/var/run%20after%20/usr/move&In-Reply-To=%3C50C76458.1070505%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] /var/run after /usr/move">mageia at colin.guthr.ie
</A><BR>
<I>Tue Dec 11 17:50:32 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="020743.html">[Mageia-dev] /var/run after /usr/move
</A></li>
<LI>Next message: <A HREF="020808.html">[Mageia-dev] /var/run after /usr/move
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20746">[ date ]</a>
<a href="thread.html#20746">[ thread ]</a>
<a href="subject.html#20746">[ subject ]</a>
<a href="author.html#20746">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Hiya,
'Twas brillig, and Olivier Thauvin at 11/12/12 16:26 did gyre and gimble:
><i> The "/usr move" included the move of /var/run to /run, however this has
</I>><i> not been done into packages, like quagga:
</I>><i>
</I>><i> [...]
</I>><i> %dir %attr(0750,root,root) /var/run/quagga
</I>><i> [...]
</I>><i>
</I>><i> Shouldn' this be changed ?
</I>
Yes, I've mentioned this on the list a few times and also have worked
through a few of the main, high profile packages already.
I've also pushed a new rpmlint-mageia-policy update which bans files in
/var/run, /var/lock and /run. It also bans udev rule files in
/etc/udev.d and tmpfiles in /etc/ (the /etc/ tree is for admin config,
and packaged files should be in /usr/lib/udev/rules.d and
/usr/lib/tmpfiles.d respectively).
It would be good to get this updated set of rules pushed to the
infrastructure before the mass rebuild and beta2.
Help here on updating packages is most welcome. The files/dirs in these
folders basically need to be translated to tmpfiles configs instead.
I've written a wiki page to document about how to handle tmpfiles:
<A HREF="https://wiki.mageia.org/en/System_Service_policy">https://wiki.mageia.org/en/System_Service_policy</A>
This will give you a nice list:
urpmf "^/var/(run|lock)/" | sort -u
Unfortunetly in the last week or so, some new ones are appearing:
ngircd
tomcat
so the sooner the lint policy is added the better IMO :)
I do also still have one problem (reported on this list) that needs
fixing that's the postfix+cyrus-sasl saslauth socket issue. Previously
it was hardlinked, such that chrooted postfix worked OK. This is no
longer possible due to it crossing filesystems, so we'll have to do some
bind-mounting black magic I think :s
><i> BTW: I recently updated a fresh mga2 to mga-cualdron and separated /var
</I>><i> is still not handle automatically when moving /usr.
</I>
How recently? I pushed a new mageia-prepare-upgrade package to mga2
core/updates_testing on Sunday which should handle /var mounting in the
initramfs for processing the usrmove. Certainly it worked fine for me in
my tests (ext4 / + swap + LVM /var and LVM /usr + encrypted LVM /home
(all on the same Volume Group) and it worked fine with that somewhat
overly complex example. Minor problem with the vga= line from the kernel
not being propagated to the newly installed bootloader entry but other
than that it worked fine, not tested with lilo tho' - only grub,
although all manipulation is via our tools so should be OK in theory)
I mentioned this already on the "ANN: Upgrading from Mageia 2 via urpmi"
thread which has seen several new posts over the last few days, so there
may be some additional info in there.
Hope this helps.
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="020743.html">[Mageia-dev] /var/run after /usr/move
</A></li>
<LI>Next message: <A HREF="020808.html">[Mageia-dev] /var/run after /usr/move
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#20746">[ date ]</a>
<a href="thread.html#20746">[ thread ]</a>
<a href="subject.html#20746">[ subject ]</a>
<a href="author.html#20746">[ 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>
|
