summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/20111112/005824.html
blob: 2ef4d607448ec06173ebdae0a35cac5559a291f8 (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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-discuss] KDE compatibility issue
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20KDE%20compatibility%20issue&In-Reply-To=%3C4EBE9D39.3070707%40unige.ch%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="005822.html">
   <LINK REL="Next"  HREF="005823.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-discuss] KDE compatibility issue</H1>
    <B>Juergen Harms</B> 
    <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20KDE%20compatibility%20issue&In-Reply-To=%3C4EBE9D39.3070707%40unige.ch%3E"
       TITLE="[Mageia-discuss] KDE compatibility issue">Juergen.Harms at unige.ch
       </A><BR>
    <I>Sat Nov 12 17:22:17 CET 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="005822.html">[Mageia-discuss] KDE compatibility issue
</A></li>
        <LI>Next message: <A HREF="005823.html">[Mageia-discuss] BRe:  KDE startup time
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#5824">[ date ]</a>
              <a href="thread.html#5824">[ thread ]</a>
              <a href="subject.html#5824">[ subject ]</a>
              <a href="author.html#5824">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>I am using precisely the same solution as morgan: for each bootable 
file-system its own /home directory, all my permanent data live in a 
separate (non-bootable) file-system (yes, and with binary uid/gid-to- 
alphanumeric name mappings that match).

Several advantages to this solution:
- coexistance between conflicting version-dependant private folders (the 
problem of Barry. for instance .kde4/..., but the same problem may 
arrise for other applications)
- sharing of permanent data between bootable file-systems (multi-boot 
between different OSses - or cauldron and Mageia1)
- ease for backup - I make daily backups only of the permanent data 
file-system.

To make life easy with such a solution, I use a script that, when I 
install a new system, creates links form its /home directory to 
directories in the file-system that contains my permanent data. (Except 
for the user to be declared at sys-install, uid/gid-to-name mapping can 
also be standardised with the help of simple scripts - not really 
necessary if there are just some few users.)

De-facto, my /home directory has only 3 functions: (1) contain files and 
directories like .bashrc or .kde4/, (2) contain the links to my 
permanent data directories, (3) for use as support for scratch data that 
is not backed up and does not need to be carefully structured.
</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="005822.html">[Mageia-discuss] KDE compatibility issue
</A></li>
	<LI>Next message: <A HREF="005823.html">[Mageia-discuss] BRe:  KDE startup time
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#5824">[ date ]</a>
              <a href="thread.html#5824">[ thread ]</a>
              <a href="subject.html#5824">[ subject ]</a>
              <a href="author.html#5824">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
mailing list</a><br>
</body></html>