Thread: [SSI] SSI/UML user experiences
Brought to you by:
brucewalker,
rogertsang
From: Tobias G. O. <tob...@gm...> - 2002-09-15 12:19:18
|
Hello, I've started toying around with CI-SSI on UML. Here is a short report of my experiences. In short: 1. Installation of SSI/UML was pretty easy (the HOWTO is very clear) 2. Bringing up a 2-node cluster and after that adding a third one is working well. 3. Bringing up a 3-node cluster at once almost never worked for me (see the attached [hope the list accepts attachements] logs for 4 unsuccessful attempts). 4. 512MB Ram and a 800 MHz CPU results in reasonable performance for testing purposes. Greets, Tobias Host System =========== Debian 3.0 (woody) Linux version 2.4.18-bf2.4 (root@zombie) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Son Apr 14 09:53:28 CEST 2002 Intel PIII-800 Coppermine 512 MB PC133 Ram 30G IBM running at Promise U-DMA 100 SSI Release =========== ssiuml-root-rh72-0.6.5-1.tar.bz2 ssiuml-utils-0.6.5-1.tar.bz2 uml_utilities_20020428.tar.bz2 Additional Software =================== dpkg -i libncurses5-dev_5.2.20020112a-7_i386.deb dpkg -i libreadline4-dev_4.2a-5_i386.deb Cluster Startup Times ===================== 1. bringing up 2 nodes (ssi-start 2) time up to login prompt on node 1: 1:34 time up to login prompt on node 2: 2:40 2. adding one more node in addition to an already running cluster of 2 nodes (ssi-add 3) time up to login prompt on node 3: 1:22 |
From: Brian J. W. <Bri...@hp...> - 2002-09-17 01:02:14
|
> 1. Installation of SSI/UML was pretty easy (the HOWTO is very clear) Thanks! > 3. Bringing up a 3-node cluster at once almost never worked for me > (see the attached [hope the list accepts attachements] logs for 4 > unsuccessful attempts). Many simultaneous boot problems (perhaps not all) have been fixed since the 0.6.5 release. I've tried to update the root and utils packages to 0.7.1, but something's broken that causes the nodes to panic early in boot. If someone's feeling adventurous enough to tackle this problem, I can post the images in the contrib/ directory of the project website. > 4. 512MB Ram and a 800 MHz CPU results in reasonable performance > for testing purposes. Cool! I'll add this information to the HOWTO. Thanks for the detailed report. -Brian |
From: Tobias G. O. <tob...@gm...> - 2002-09-19 07:17:04
|
Brian, > Many simultaneous boot problems (perhaps not all) have been fixed since > the 0.6.5 release. Good to hear. > I've tried to update the root and utils packages to > 0.7.1, but something's broken that causes the nodes to panic early in > boot. If someone's feeling adventurous enough to tackle this problem, I > can post the images in the contrib/ directory of the project website. Yes please. I think the UML/SSI distribution is a terrific idea and could attract more people - and if it's just for playing around and bug reporting / fixing. For me, I'm quite experienced in C++/userland but just starting to get interested in kernel stuff - so I'm "adventurous" but, eh well;) Tobias. P.S. I've tried to build the _current_ cvs .. and failed. I'm just reporting it below for comepleteness. But if it wouldn't boot either .. anyway: This is what I've done to a fresh 2.4.16 tree and after a fresh checkout of CI & SSI: patch -p1 <../../ssic-linux/3rd-party/uml-patch-2.4.18-22 cp -alf ../../ssic-linux/ssi-kernel/. . cp -alf ../../ci-linux/ci-kernel/. . patch -p1 <../../ssic-linux/3rd-party/opengfs-ssi.patch I suppose applying this patch to a 2.4.16 is correct even if the patch contains the substring "2.4.18" because this is what the "Creating SSI Clusters Using UML HOWTO" says. The problem: in linux/include/cluster/ssi/rcopy.h there are some references to a strcuture "current" where e.g. "cltnode" should be a member but is not. gcc -D__KERNEL__ -I/home/toberste/sandbox/linux2.4.16/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -g -U__i386__ -Ui386 -DUM_FASTCALL -D__arch_um__ -DSUBARCH=\"i386\" -DNESTING=0 -D_LARGEFILE64_SOURCE -I/home/toberste/sandbox/linux2.4.16/linux/arch/um/include -Derrno=kernel_errno -c -o init/main.o init/main.c In file included from /home/toberste/sandbox/linux2.4.16/linux/include/asm/uaccess.h:15, from /home/toberste/sandbox/linux2.4.16/linux/include/asm/unistd.h:10, from /home/toberste/sandbox/linux2.4.16/linux/include/linux/unistd.h:9, from init/main.c:17: /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h: In function `ssi_rcopy_is_remote': /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:43: structure has no member named `cltnode' /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:44: warning: control reaches end of non-void function /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h: In function `ssi_procstate_get': /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:54: structure has no member named `epid' /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:58: structure has no member named `cttynode' /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:59: structure has no member named `cttydev' /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h: In function `ssi_procstate_set': /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:68: structure has no member named `cltnode' /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:70: structure has no member named `cltnode' /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:71: structure has no member named `epid' /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:75: structure has no member named `cttynode' /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:76: structure has no member named `cttydev' make: *** [init/main.o] Error 1 Now, I've looked to find the location where the structure "current" is declared .. but were unable to. The strange thing is, grepping for "cltnode" looks like it is nowhere! toberste@stalker$ pwd /home/toberste/sandbox/linux2.4.16/linux toberste@stalker$ grep -r cltnode * cluster/ssi/cfs/cfs.x: int cia_cltnode; cluster/ssi/util/rcopy.c: clusternode_t to_node = current->cltnode; cluster/ssi/util/rcopy.c: clusternode_t to_node = current->cltnode; cluster/ssi/util/rcopy.c: clusternode_t to_node = current->cltnode; cluster/ssi/util/rcopy.c: clusternode_t to_node = current->cltnode; cluster/ssi/util/rcopy.c: clusternode_t to_node = current->cltnode; cluster/ssi/util/rcopy.c: clusternode_t to_node = current->cltnode; cluster/ssi/vproc/rproc.x: * cltnode, p_vproc, p_vfparent, p_opptr, p_pptr, p_cptr, cluster/ssi/vproc/rproc_platform.x: * cltnode, p_vproc, p_vfparent, p_opptr, p_pptr, p_cptr, include/cluster/ssi/rcopy.h: return (current->cltnode != 0); include/cluster/ssi/rcopy.h: current->cltnode = sp->sps_node; include/cluster/ssi/rcopy.h: current->cltnode = 0; |
From: Laura R. <lra...@ka...> - 2002-09-20 21:31:52
|
Hi Tobias, > > I've tried to build the _current_ cvs .. and failed. I'm just reporting > it below for comepleteness. But if it wouldn't boot either .. anyway: > > This is what I've done to a fresh 2.4.16 tree and after a fresh > checkout of CI & SSI: > > patch -p1 <../../ssic-linux/3rd-party/uml-patch-2.4.18-22 > cp -alf ../../ssic-linux/ssi-kernel/. . > cp -alf ../../ci-linux/ci-kernel/. . > patch -p1 <../../ssic-linux/3rd-party/opengfs-ssi.patch From the above steps, it looks like you did the cp's out of order. The ci-kernel needs to be copied first, since the ssi-kernel has some overlapping files which get overwritten with the ssi version. In your case, it seems that the ci version overwrote the ssi version and so alot of the ssi fields are missing. laura > > I suppose applying this patch to a 2.4.16 is correct even if > the patch contains the substring "2.4.18" because this is what > the "Creating SSI Clusters Using UML HOWTO" says. > > The problem: in linux/include/cluster/ssi/rcopy.h there are some > references to a strcuture "current" where e.g. "cltnode" should be > a member but is not. > > > gcc -D__KERNEL__ -I/home/toberste/sandbox/linux2.4.16/linux/include > -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing > -fno-common -g -U__i386__ -Ui386 -DUM_FASTCALL -D__arch_um__ > -DSUBARCH=\"i386\" -DNESTING=0 -D_LARGEFILE64_SOURCE > -I/home/toberste/sandbox/linux2.4.16/linux/arch/um/include > -Derrno=kernel_errno -c -o init/main.o init/main.c > In file included from > /home/toberste/sandbox/linux2.4.16/linux/include/asm/uaccess.h:15, > from > /home/toberste/sandbox/linux2.4.16/linux/include/asm/unistd.h:10, > from > /home/toberste/sandbox/linux2.4.16/linux/include/linux/unistd.h:9, > from init/main.c:17: > /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h: In > function `ssi_rcopy_is_remote': > /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:43: > structure has no member named `cltnode' > /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:44: > warning: control reaches end of non-void function > /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h: In > function `ssi_procstate_get': > /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:54: > structure has no member named `epid' > /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:58: > structure has no member named `cttynode' > /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:59: > structure has no member named `cttydev' > /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h: In > function `ssi_procstate_set': > /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:68: > structure has no member named `cltnode' > /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:70: > structure has no member named `cltnode' > /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:71: > structure has no member named `epid' > /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:75: > structure has no member named `cttynode' > /home/toberste/sandbox/linux2.4.16/linux/include/cluster/ssi/rcopy.h:76: > structure has no member named `cttydev' > make: *** [init/main.o] Error 1 > > > Now, I've looked to find the location where the structure "current" is > declared .. but were unable to. > > The strange thing is, grepping for "cltnode" looks like it is nowhere! > > > toberste@stalker$ pwd > /home/toberste/sandbox/linux2.4.16/linux > toberste@stalker$ grep -r cltnode * > cluster/ssi/cfs/cfs.x: int cia_cltnode; > cluster/ssi/util/rcopy.c: clusternode_t to_node = current->cltnode; > cluster/ssi/util/rcopy.c: clusternode_t to_node = current->cltnode; > cluster/ssi/util/rcopy.c: clusternode_t to_node = current->cltnode; > cluster/ssi/util/rcopy.c: clusternode_t to_node = current->cltnode; > cluster/ssi/util/rcopy.c: clusternode_t to_node = current->cltnode; > cluster/ssi/util/rcopy.c: clusternode_t to_node = current->cltnode; > cluster/ssi/vproc/rproc.x: * cltnode, p_vproc, p_vfparent, > p_opptr, p_pptr, > p_cptr, > cluster/ssi/vproc/rproc_platform.x: * cltnode, p_vproc, p_vfparent, > p_opptr, > p_pptr, p_cptr, > include/cluster/ssi/rcopy.h: return (current->cltnode != 0); > include/cluster/ssi/rcopy.h: current->cltnode = sp->sps_node; > include/cluster/ssi/rcopy.h: current->cltnode = 0; > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > ssic-linux-devel mailing list > ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel |
From: Brian J. W. <Bri...@hp...> - 2002-10-01 00:06:38
|
> > If someone's feeling adventurous enough to tackle this problem, I > > can post the images in the contrib/ directory of the project website. > > Yes please. Sorry for the delay. I was working our demo at HP World last week. The images are available at: http://ssic-linux.sourceforge.net/contrib/ The files are as follows: ssiuml-root-rh72-0.7.1-pre1.tar.bz2 Root image updated with Cluster Tools 0.7.1 and SSI 0.7.1 kernel modules ssiuml-utils-0.7.1-pre1.tar.bz2 Updated with kernel image and ramdisk for SSI 0.7.1. linux-uml-0.7.1-pre1.tar.bz2 The source tree used to build the SSI 0.7.1 kernel image and modules. The config file used was config.uml. opengfs-uml-0.7.1-pre1.tar.bz2 The source tree used to build the OpenGFS modules for the SSI 0.7.1 kernel. > I think the UML/SSI distribution is a terrific idea and > could attract more people - and if it's just for playing around and > bug reporting / fixing. Thanks! > For me, I'm quite experienced in C++/userland > but just starting to get interested in kernel stuff - so I'm > "adventurous" but, eh well;) Good luck trying to make it work. If it gets a little too involved, don't hesitate to ask questions on this mailing list. -Brian |
From: Brian J. W. <Bri...@hp...> - 2002-10-16 20:27:47
|
"Brian J. Watson" wrote: > Sorry for the delay. I was working our demo at HP World last week. The > images are available at: > http://ssic-linux.sourceforge.net/contrib/ > > The files are as follows: > ssiuml-root-rh72-0.7.1-pre1.tar.bz2 > Root image updated with Cluster Tools 0.7.1 and SSI 0.7.1 > kernel modules > ssiuml-utils-0.7.1-pre1.tar.bz2 > Updated with kernel image and ramdisk for SSI 0.7.1. > linux-uml-0.7.1-pre1.tar.bz2 > The source tree used to build the SSI 0.7.1 kernel image > and modules. The config file used was config.uml. > opengfs-uml-0.7.1-pre1.tar.bz2 > The source tree used to build the OpenGFS modules for the > SSI 0.7.1 kernel. I discovered that these images work just fine on a Red Hat 7.2 kernel. The problems I was seeing had something to do with the configuration of the custom host kernel I was using. -- Brian Watson | "Now I don't know, but I been told it's Software Developer | hard to run with the weight of gold, Open SSI Clustering Project | Other hand I heard it said, it's Hewlett-Packard Company | just as hard with the weight of lead." | -Robert Hunter, 1970 mailto:Bri...@hp... http://opensource.compaq.com/ |
From: Tobias G. O. <tob...@gm...> - 2002-09-19 07:27:20
|
>Brian J. Watson wrote: >>4. 512MB Ram and a 800 MHz CPU results in reasonable performance >> for testing purposes. > > > Cool! I'll add this information to the HOWTO. If you're updating it anyway.. here might be another addon detail: There is a SSI 0.6.5 and a 0.6.5a tarball. Only for the latter (ssi-linux-2.4.16-v0.6.5a.tar.bz2) I managed to build a new kernel. In doing so, I followed exactly the instructions in the HOWTO. In the end, it's just one "a" more;) P.S. purpose was to make a new SSI-UML image that includes standard dev tools and sources. My host system is debian 3.0, 2.4.18-bf2.4, gcc version 2.95.4 20011002 (Debian prerelease)). I also had to replace (by hard linking) awk with gawk because it bailed out. Greets, Tobias |
From: Aneesh K. K.V <ane...@di...> - 2002-09-19 08:19:02
|
Hi, On Thu, 2002-09-19 at 12:55, Tobias G. Oberstein wrote: > > P.S. purpose was to make a new SSI-UML image that includes > standard dev tools and sources. My host system is debian 3.0, > 2.4.18-bf2.4, gcc version 2.95.4 20011002 (Debian prerelease)). > I also had to replace (by hard linking) awk with gawk because > it bailed out. It failed at what point ?. I guess we will have to move all the 'awk' appearance to gawk.( becuase on debian awk is actually provided by mawk. IIRC ) We have done some similar modification before. -aneesh |
From: Tobias G. O. <tob...@gm...> - 2002-09-19 21:37:55
|
Hello, >>P.S. purpose was to make a new SSI-UML image that includes >>standard dev tools and sources. My host system is debian 3.0, >>2.4.18-bf2.4, gcc version 2.95.4 20011002 (Debian prerelease)). >>I also had to replace (by hard linking) awk with gawk because >>it bailed out. > > > It failed at what point ?. I guess we will have to move all the 'awk' > appearance to gawk.( becuase on debian awk is actually provided by mawk. > IIRC ) We have done some similar modification before. > > -aneesh Below is a log of what I get with mawk. Greets, Tobias tar jxvf /var/downloads/linux/linux-2.4.16.tar.bz2 tar jxvf /var/downloads/ssi/ssi-linux-2.4.16-v0.6.5a.tar.bz2 cd linux patch -p1 < ../ssi-linux-2.4.16-v0.6.5a/ssi-linux-2.4.16-v0.6.5.patch cp config.uml .config make oldconfig ARCH=um then .. toberste@stalker$ make dep make -C /tmp/linux/cluster clustersymlinks make[1]: Entering directory `/tmp/linux/cluster' /tmp/linux/cluster/lnrel.sh /tmp/linux/cluster/arch/i386/include /tmp/linux/include/cluster/arch make -C ssi clustersymlinks make[2]: Entering directory `/tmp/linux/cluster/ssi' make -C vproc clustersymlinks make[3]: Entering directory `/tmp/linux/cluster/ssi/vproc' /tmp/linux/cluster/lnrel.sh /tmp/linux/cluster/arch/i386/vproc arch make -C arch clustersymlinks make[4]: Entering directory `/tmp/linux/cluster/arch/i386/vproc' make[4]: Nothing to be done for `clustersymlinks'. make[4]: Leaving directory `/tmp/linux/cluster/arch/i386/vproc' make[3]: Leaving directory `/tmp/linux/cluster/ssi/vproc' make -C clreg clustersymlinks make[3]: Entering directory `/tmp/linux/cluster/ssi/clreg' make[3]: Nothing to be done for `clustersymlinks'. make[3]: Leaving directory `/tmp/linux/cluster/ssi/clreg' make -C ipc clustersymlinks make[3]: Entering directory `/tmp/linux/cluster/ssi/ipc' make[3]: Nothing to be done for `clustersymlinks'. make[3]: Leaving directory `/tmp/linux/cluster/ssi/ipc' make -C util clustersymlinks make[3]: Entering directory `/tmp/linux/cluster/ssi/util' make[3]: Nothing to be done for `clustersymlinks'. make[3]: Leaving directory `/tmp/linux/cluster/ssi/util' make[2]: Leaving directory `/tmp/linux/cluster/ssi' make -C clms clustersymlinks make[2]: Entering directory `/tmp/linux/cluster/clms' make[2]: Nothing to be done for `clustersymlinks'. make[2]: Leaving directory `/tmp/linux/cluster/clms' make -C ics clustersymlinks make[2]: Entering directory `/tmp/linux/cluster/ics' make -C ics_tcp clustersymlinks make[3]: Entering directory `/tmp/linux/cluster/ics/ics_tcp' make[3]: Nothing to be done for `clustersymlinks'. make[3]: Leaving directory `/tmp/linux/cluster/ics/ics_tcp' make[2]: Leaving directory `/tmp/linux/cluster/ics' make -C util clustersymlinks make[2]: Entering directory `/tmp/linux/cluster/util' make[2]: Nothing to be done for `clustersymlinks'. make[2]: Leaving directory `/tmp/linux/cluster/util' make[1]: Leaving directory `/tmp/linux/cluster' make -C /tmp/linux/cluster clustergen make[1]: Entering directory `/tmp/linux/cluster' make -C rpcgen make[2]: Entering directory `/tmp/linux/cluster/rpcgen' cc -DNSCRPCGEN -D_GNU_SOURCE -c -o rpc_main.o rpc_main.c cc -DNSCRPCGEN -D_GNU_SOURCE -c -o rpc_hout.o rpc_hout.c cc -DNSCRPCGEN -D_GNU_SOURCE -c -o rpc_cout.o rpc_cout.c cc -DNSCRPCGEN -D_GNU_SOURCE -c -o rpc_parse.o rpc_parse.c cc -DNSCRPCGEN -D_GNU_SOURCE -c -o rpc_scan.o rpc_scan.c cc -DNSCRPCGEN -D_GNU_SOURCE -c -o rpc_util.o rpc_util.c cc -DNSCRPCGEN -D_GNU_SOURCE -c -o rpc_svcout.o rpc_svcout.c cc -DNSCRPCGEN -D_GNU_SOURCE -c -o rpc_clntout.o rpc_clntout.c cc -DNSCRPCGEN -D_GNU_SOURCE -c -o rpc_tblout.o rpc_tblout.c cc -DNSCRPCGEN -D_GNU_SOURCE -c -o rpc_sample.o rpc_sample.c cc -o nscrpcgen rpc_main.o rpc_hout.o rpc_cout.o rpc_parse.o rpc_scan.o rpc_util.o rpc_svcout.o rpc_clntout.o rpc_tblout.o rpc_sample.o make[2]: Leaving directory `/tmp/linux/cluster/rpcgen' make -C /tmp/linux/include/cluster/gen genfiles make[2]: Entering directory `/tmp/linux/include/cluster/gen' awk -f type_template.awk \ ics_proto_gen.h.template ics_proto_gen.h.list >ics_proto_gen.h awk: type_template.awk: line 83: improper use of next make[2]: *** [ics_proto_gen.h] Error 2 make[2]: Leaving directory `/tmp/linux/include/cluster/gen' make[1]: *** [clustergen] Error 2 make[1]: Leaving directory `/tmp/linux/cluster' make: *** [clustergen] Error 2 toberste@stalker$ |
From: Aneesh K. K.V <ane...@di...> - 2002-09-20 03:44:31
|
On Fri, 2002-09-20 at 03:06, Tobias G. Oberstein wrote: > Hello, <<<< cut >>>>> > make[2]: Leaving directory `/tmp/linux/cluster/rpcgen' > make -C /tmp/linux/include/cluster/gen genfiles > make[2]: Entering directory `/tmp/linux/include/cluster/gen' > awk -f type_template.awk \ > ics_proto_gen.h.template ics_proto_gen.h.list >ics_proto_gen.h > awk: type_template.awk: line 83: improper use of next > make[2]: *** [ics_proto_gen.h] Error 2 > make[2]: Leaving directory `/tmp/linux/include/cluster/gen' > make[1]: *** [clustergen] Error 2 > make[1]: Leaving directory `/tmp/linux/cluster' > make: *** [clustergen] Error 2 > toberste@stalker$ I works for me on my debian woody. I tried the below mawk -f type_template.awk ics_proto_gen.h.template ics_proto_gen.h.list The mawk version that i have is 1.3.3-8 . Any how I will change the awk to gawk because it won't fail on potato any other old releases . -aneesh |
From: Tobias G. O. <tob...@gm...> - 2002-09-20 08:01:02
|
Hi, >>make[2]: Leaving directory `/tmp/linux/cluster/rpcgen' >>make -C /tmp/linux/include/cluster/gen genfiles >>make[2]: Entering directory `/tmp/linux/include/cluster/gen' >>awk -f type_template.awk \ >>ics_proto_gen.h.template ics_proto_gen.h.list >ics_proto_gen.h >>awk: type_template.awk: line 83: improper use of next >>make[2]: *** [ics_proto_gen.h] Error 2 >>make[2]: Leaving directory `/tmp/linux/include/cluster/gen' >>make[1]: *** [clustergen] Error 2 >>make[1]: Leaving directory `/tmp/linux/cluster' >>make: *** [clustergen] Error 2 >>toberste@stalker$ > > > I works for me on my debian woody. > I tried the below > > mawk -f type_template.awk ics_proto_gen.h.template ics_proto_gen.h.list this exactly bails out on my system with abaove error. the offending line 83 was changed for ssi 0.7.1 (precisely, the file is part of ci but the version labeled for ssi 0.7.1 is the newer one). please see: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ci-linux/ci-linux/ci-kernel/include/cluster/gen/type_template.awk.diff?r1=1.1&r2=1.2 > > The mawk version that i have is 1.3.3-8 . toberste@stalker$ mawk -W version mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan compiled limits: max NF 32767 sprintf buffer 1020 > Any how I will change the awk > to gawk because it won't fail on potato any other old releases . yep, that's cool. Tobias. |
From: Brian J. W. <Bri...@hp...> - 2002-09-24 01:28:47
|
"Tobias G. Oberstein" wrote: > There is a SSI 0.6.5 and a 0.6.5a tarball. Only for the latter > (ssi-linux-2.4.16-v0.6.5a.tar.bz2) I managed to build a new kernel. > In doing so, I followed exactly the instructions in the HOWTO. > In the end, it's just one "a" more;) Actually, there are no kernel differences between 0.6.5 and 0.6.5a. The reason for the "a" release is that some bugs were found in Cluster Tools after the 0.6.5 release. Since the SSI release tarball includes Cluster Tools, I had to push out another release of the same SSI kernel with the new and improved Cluster Tools. -Brian |
From: Brian J. W. <Bri...@hp...> - 2002-09-17 01:22:13
|
> 2. adding one more node in addition to an already running > cluster of 2 nodes (ssi-add 3) > > time up to login prompt on node 3: 1:22 It occurred to me that dependent nodes will join quicker with the 0.7.1 release. This is due to some streamlining David Zafman did to dependent node rc scripts. -Brian |