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
|
<!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=%3C201111021627.44292.cooker%40solbu.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="009290.html">
<LINK REL="Next" HREF="009298.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Please test: initscripts+systemd in updates_testing</H1>
<B>Johnny A. Solbu</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=%3C201111021627.44292.cooker%40solbu.net%3E"
TITLE="[Mageia-dev] Please test: initscripts+systemd in updates_testing">cooker at solbu.net
</A><BR>
<I>Wed Nov 2 16:27:39 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="009290.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing
</A></li>
<LI>Next message: <A HREF="009298.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9297">[ date ]</a>
<a href="thread.html#9297">[ thread ]</a>
<a href="subject.html#9297">[ subject ]</a>
<a href="author.html#9297">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Wednesday 02 November 2011 07:47, andre999 wrote:
><i> Without a special reason to have a separate /usr,
</I>><i> I would say that it is better to avoid it.
</I>
The one issiue left then is how to solve the fact that many users do have a separate /usr, when they upgrade the distro to a version with systemd.
If systemd currently require /usr to be on the same filesystem as /, then the upgrade should be halted or interrupted with a warning to warn the user about the fact that currently he can't upgrade, and why. Or something to that effect, as there are many systems that have / of only a gigabyte, or so. For instance, all of my systems have this setup.
Providing that systemd, or something systemd depends on, actually require that. :-)=
One way to solve it is to do what Ubuntu (i believe) does, where the installation routine require the root filesystem to be at least 12 Gigabyte. It won't continue the installation untill / is at least 12 G.
Perhaps one can create the abillity to have the installer merge the two partitions into one. I have no idea if that actually is possible without having to reformat the new big partition. Nor do I know if it's even a good idea. (Just sharing the idea, thinking out loud.)
--
Johnny A. Solbu
PGP key ID: 0xFA687324
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/mageia-dev/attachments/20111102/f5fff131/attachment.asc>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="009290.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing
</A></li>
<LI>Next message: <A HREF="009298.html">[Mageia-dev] Please test: initscripts+systemd in updates_testing
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9297">[ date ]</a>
<a href="thread.html#9297">[ thread ]</a>
<a href="subject.html#9297">[ subject ]</a>
<a href="author.html#9297">[ 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>
|
