1 |
Thats basically what I was doing although I don't know what you mean by |
2 |
ram duplication. |
3 |
|
4 |
The other thing I was having a problem with was the netmount script. |
5 |
Seems it either mounts the network drives too late, which screws the |
6 |
other scripts up or it unmounts too early and cant shut down properly. |
7 |
|
8 |
Any ideas? |
9 |
|
10 |
Jon. |
11 |
|
12 |
On Sun, 2004-07-18 at 05:48, Jimmy Rosen wrote: |
13 |
> Yes, some areas must of course be individual, but that's a minor issue. |
14 |
> Just some files/directories in /var for logs and some software |
15 |
> settings, /etc for allowing different configurations on different |
16 |
> nodes, /lib for allowing different hardware setups in kernel module |
17 |
> loading, and then I also allow /root to be individual for each node for |
18 |
> simplicity in maintainance and testing. |
19 |
> These can be mounted in ram duplication or network file distribution, |
20 |
> depending on need and interest. |
21 |
> |
22 |
> Harebrafolk |
23 |
> Jimmy |
24 |
> |
25 |
> |
26 |
> |
27 |
> On Sunday 18 July 2004 00.16, Jonathan Taylor wrote: |
28 |
> > Hi, |
29 |
> > |
30 |
> > I am doing this on a 20 or so node x86 cluster. I am really puzzled as |
31 |
> > to how you share the same image. Can you give me some hints? It seemed |
32 |
> > to me that the nodes should have write access to certain /var areas etc. |
33 |
> > |
34 |
> > Any help is appreciated. |
35 |
> > |
36 |
> > Jon. |
37 |
> > |
38 |
> > |
39 |
> > -- |
40 |
> > gentoo-cluster@g.o mailing list |
41 |
> |
42 |
> -- |
43 |
> gentoo-cluster@g.o mailing list |
44 |
> |
45 |
|
46 |
|
47 |
-- |
48 |
gentoo-cluster@g.o mailing list |