From gartim at gmail.com Thu Apr 1 09:45:02 2010 From: gartim at gmail.com (gary artim) Date: Thu, 1 Apr 2010 09:45:02 -0700 Subject: [Caos] dmesg - klogctl: Operation not permitted / top, only shows users jobs. Message-ID: Hi -- Quick question. New install of caos-perceus. not running grsecurity and getting klogctl message " klogctl: Operation not permitted ". also, running 'top' command only shows current users jobs. this is probably a feature, but one i'd like removed or changed. any help greatfully appreciated! -- G. From gartim at gmail.com Thu Apr 1 11:44:02 2010 From: gartim at gmail.com (gary artim) Date: Thu, 1 Apr 2010 11:44:02 -0700 Subject: [Caos] dmesg - klogctl: Operation not permitted / top, only shows users jobs. In-Reply-To: References: Message-ID: these two issues seems related to /proc, but havent found what needs changing mount output: /proc on /proc type proc (rw,nosuid) On Thu, Apr 1, 2010 at 9:45 AM, gary artim wrote: > Hi -- > > Quick question. New install of caos-perceus. not running grsecurity and getting > klogctl message " klogctl: Operation not permitted ". > > also, running 'top' command only shows current users jobs. > > this is probably a feature, but one i'd like removed or changed. > > any help greatfully appreciated! > > -- G. > From slaton.lipscomb at gmail.com Tue Apr 6 21:27:38 2010 From: slaton.lipscomb at gmail.com (Slaton Lipscomb) Date: Tue, 6 Apr 2010 21:27:38 -0700 Subject: [Caos] Illegal instruction when linking against libatlas Message-ID: I've run into an issue trying to compile UMFPACK, a sparse matrix package that is a prerequisite for building NumPy (and therefore SciPy). Platform is Caos-NSA x86_64 (AMD Opteron). UMFPACK includes among its prerequisites BLAS, LAPACK, and ATLAS. So I have the following Caos-NSA packages installed: atlas-3.8.2-1.caos.x86_64 atlas-devel-3.8.2-1.caos.x86_64 lapack-3.1.1-2.caos.x86_64 lapack-devel-3.1.1-2.caos.x86_64 blas-3.1.1-2.caos.x86_64 blas-devel-3.1.1-2.caos.x86_64 Using the following UFconfig.mk options: F77 = gfortran F77FLAGS = -O -m64 -fPIC CC = gcc CFLAGS = -O3 -fexceptions -m64 -fPIC BLAS = -L/usr/lib64 -L/usr/lib64/atlas -L/sw/appion/build/scipy/lib -llapack -lf77blas -lcblas -latlas -lgfortran LAPACK = -L/usr/lib64 -L/usr/lib64/atlas -L/sw/appion/build/scipy/lib -llapack -lf77blas -lcblas -latlas -lgfortran libumfpack.a appears to build, but then there's a fatal error during the makefile's scripted post-compile tests: make[1]: [run] Error 1 (ignored) ./umfpack_zi_demo > my_umfpack_zi_demo.out /bin/sh: line 1: 26275 Illegal instruction ./umfpack_zi_demo >my_umfpack_zi_demo.out make[1]: *** [run] Error 132 make[1]: Leaving directory `/tmp/scipy/UMFPACK/Demo' make: *** [library] Error 2 Further investigation with gdb shows this is occurring in libatlas: Program received signal SIGILL, Illegal instruction. [Switching to Thread 0x2b5dbec9fe80 (LWP 30803)] 0x00002b5dbde91f1f in NLOOP () from /usr/lib64/atlas/libatlas.so.3 Where can I find the src.rpm for the atlas packages so I can try doing a local rebuild? thanks slaton From pierreyves.langlois at gmail.com Wed Apr 7 03:49:28 2010 From: pierreyves.langlois at gmail.com (Pierre-Yves Langlois) Date: Wed, 7 Apr 2010 06:49:28 -0400 Subject: [Caos] Illegal instruction when linking against libatlas In-Reply-To: References: Message-ID: Hi... I used libatlas once when I compiled xhpl. In my case I compiled it using the static version of the lib atlas. Maybe you could try that... LAdir = /usr/lib64/atlas LAinc = -I/usr/include/atlas LAlib = $(LAdir)/libcblas.a $(LAdir)/libatlas.a $(LAdir)/liblapack.a Here is the full make to compile xhpl... http://pastebin.com/f65a6ba2 I hope this could help... On Wed, Apr 7, 2010 at 12:27 AM, Slaton Lipscomb wrote: > I've run into an issue trying to compile UMFPACK, a sparse matrix > package that is a prerequisite for building NumPy (and therefore > SciPy). Platform is Caos-NSA x86_64 (AMD Opteron). > > UMFPACK includes among its prerequisites BLAS, LAPACK, and ATLAS. So I > have the following Caos-NSA packages installed: > > atlas-3.8.2-1.caos.x86_64 > atlas-devel-3.8.2-1.caos.x86_64 > lapack-3.1.1-2.caos.x86_64 > lapack-devel-3.1.1-2.caos.x86_64 > blas-3.1.1-2.caos.x86_64 > blas-devel-3.1.1-2.caos.x86_64 > > Using the following UFconfig.mk options: > > F77 = gfortran > F77FLAGS = -O -m64 -fPIC > CC = gcc > CFLAGS = -O3 -fexceptions -m64 -fPIC > > BLAS = -L/usr/lib64 -L/usr/lib64/atlas -L/sw/appion/build/scipy/lib > -llapack -lf77blas -lcblas -latlas -lgfortran > LAPACK = -L/usr/lib64 -L/usr/lib64/atlas -L/sw/appion/build/scipy/lib > -llapack -lf77blas -lcblas -latlas -lgfortran > > libumfpack.a appears to build, but then there's a fatal error during > the makefile's scripted post-compile tests: > > make[1]: [run] Error 1 (ignored) > ./umfpack_zi_demo > my_umfpack_zi_demo.out > /bin/sh: line 1: 26275 Illegal instruction ? ? ./umfpack_zi_demo >>my_umfpack_zi_demo.out > make[1]: *** [run] Error 132 > make[1]: Leaving directory `/tmp/scipy/UMFPACK/Demo' > make: *** [library] Error 2 > > Further investigation with gdb shows this is occurring in libatlas: > > Program received signal SIGILL, Illegal instruction. > [Switching to Thread 0x2b5dbec9fe80 (LWP 30803)] > 0x00002b5dbde91f1f in NLOOP () from /usr/lib64/atlas/libatlas.so.3 > > Where can I find the src.rpm for the atlas packages so I can try doing > a local rebuild? > > thanks > slaton > _______________________________________________ > Caos mailing list > Caos at lists.infiscale.org > http://lists.infiscale.org/mailman/listinfo/caos > From slaton.lipscomb at gmail.com Wed Apr 7 14:22:21 2010 From: slaton.lipscomb at gmail.com (Slaton Lipscomb) Date: Wed, 7 Apr 2010 14:22:21 -0700 Subject: [Caos] Illegal instruction when linking against libatlas In-Reply-To: References: Message-ID: Pierre, Thanks for the reply. But alas, I've already tried compiling against the static library which (while itself successful) unfortunately produced the same Illegal Instruction error during testing. regards slaton On Wed, Apr 7, 2010 at 3:49 AM, Pierre-Yves Langlois wrote: > Hi... I used libatlas once when I compiled xhpl. In my case I compiled > it using the static version of the lib atlas. Maybe you could try > that... > > LAdir ? ? ? ?= /usr/lib64/atlas > LAinc ? ? ? ?= -I/usr/include/atlas > LAlib ? ? ? ?= $(LAdir)/libcblas.a $(LAdir)/libatlas.a $(LAdir)/liblapack.a > > Here is the full make to compile xhpl... > http://pastebin.com/f65a6ba2 > > I hope this could help... > > On Wed, Apr 7, 2010 at 12:27 AM, Slaton Lipscomb > wrote: >> I've run into an issue trying to compile UMFPACK, a sparse matrix >> package that is a prerequisite for building NumPy (and therefore >> SciPy). Platform is Caos-NSA x86_64 (AMD Opteron). >> >> UMFPACK includes among its prerequisites BLAS, LAPACK, and ATLAS. So I >> have the following Caos-NSA packages installed: >> >> atlas-3.8.2-1.caos.x86_64 >> atlas-devel-3.8.2-1.caos.x86_64 >> lapack-3.1.1-2.caos.x86_64 >> lapack-devel-3.1.1-2.caos.x86_64 >> blas-3.1.1-2.caos.x86_64 >> blas-devel-3.1.1-2.caos.x86_64 >> >> Using the following UFconfig.mk options: >> >> F77 = gfortran >> F77FLAGS = -O -m64 -fPIC >> CC = gcc >> CFLAGS = -O3 -fexceptions -m64 -fPIC >> >> BLAS = -L/usr/lib64 -L/usr/lib64/atlas -L/sw/appion/build/scipy/lib >> -llapack -lf77blas -lcblas -latlas -lgfortran >> LAPACK = -L/usr/lib64 -L/usr/lib64/atlas -L/sw/appion/build/scipy/lib >> -llapack -lf77blas -lcblas -latlas -lgfortran >> >> libumfpack.a appears to build, but then there's a fatal error during >> the makefile's scripted post-compile tests: >> >> make[1]: [run] Error 1 (ignored) >> ./umfpack_zi_demo > my_umfpack_zi_demo.out >> /bin/sh: line 1: 26275 Illegal instruction ? ? ./umfpack_zi_demo >>>my_umfpack_zi_demo.out >> make[1]: *** [run] Error 132 >> make[1]: Leaving directory `/tmp/scipy/UMFPACK/Demo' >> make: *** [library] Error 2 >> >> Further investigation with gdb shows this is occurring in libatlas: >> >> Program received signal SIGILL, Illegal instruction. >> [Switching to Thread 0x2b5dbec9fe80 (LWP 30803)] >> 0x00002b5dbde91f1f in NLOOP () from /usr/lib64/atlas/libatlas.so.3 >> >> Where can I find the src.rpm for the atlas packages so I can try doing >> a local rebuild? >> >> thanks >> slaton >> _______________________________________________ >> Caos mailing list >> Caos at lists.infiscale.org >> http://lists.infiscale.org/mailman/listinfo/caos >> > _______________________________________________ > Caos mailing list > Caos at lists.infiscale.org > http://lists.infiscale.org/mailman/listinfo/caos > From slaton.lipscomb at gmail.com Sun Apr 11 13:56:57 2010 From: slaton.lipscomb at gmail.com (Slaton Lipscomb) Date: Sun, 11 Apr 2010 13:56:57 -0700 Subject: [Caos] Illegal instruction when linking against libatlas In-Reply-To: References: Message-ID: To any Caos folks, I'd still like to try rebuilding the atlas and atlas-devel packages from srpm. Where can I find the srpms for Caos-NSA? One additional tidbit, turns out this illegal instruction error triggered an error caught by syslog: umfpack_zi_demo[26275] trap invalid opcode ip:2b3f881d5f1f sp:7fff70490f98 error:0 in libatlas.so.3.0[2b3f87c6d000+695000] thanks slaton On Wed, Apr 7, 2010 at 2:22 PM, Slaton Lipscomb wrote: > Pierre, > > Thanks for the reply. > > But alas, I've already tried compiling against the static library > which (while itself successful) unfortunately produced the same > Illegal Instruction error during testing. > > regards > slaton > > On Wed, Apr 7, 2010 at 3:49 AM, Pierre-Yves Langlois > wrote: >> Hi... I used libatlas once when I compiled xhpl. In my case I compiled >> it using the static version of the lib atlas. Maybe you could try >> that... >> >> LAdir ? ? ? ?= /usr/lib64/atlas >> LAinc ? ? ? ?= -I/usr/include/atlas >> LAlib ? ? ? ?= $(LAdir)/libcblas.a $(LAdir)/libatlas.a $(LAdir)/liblapack.a >> >> Here is the full make to compile xhpl... >> http://pastebin.com/f65a6ba2 >> >> I hope this could help... >> >> On Wed, Apr 7, 2010 at 12:27 AM, Slaton Lipscomb >> wrote: >>> I've run into an issue trying to compile UMFPACK, a sparse matrix >>> package that is a prerequisite for building NumPy (and therefore >>> SciPy). Platform is Caos-NSA x86_64 (AMD Opteron). >>> >>> UMFPACK includes among its prerequisites BLAS, LAPACK, and ATLAS. So I >>> have the following Caos-NSA packages installed: >>> >>> atlas-3.8.2-1.caos.x86_64 >>> atlas-devel-3.8.2-1.caos.x86_64 >>> lapack-3.1.1-2.caos.x86_64 >>> lapack-devel-3.1.1-2.caos.x86_64 >>> blas-3.1.1-2.caos.x86_64 >>> blas-devel-3.1.1-2.caos.x86_64 >>> >>> Using the following UFconfig.mk options: >>> >>> F77 = gfortran >>> F77FLAGS = -O -m64 -fPIC >>> CC = gcc >>> CFLAGS = -O3 -fexceptions -m64 -fPIC >>> >>> BLAS = -L/usr/lib64 -L/usr/lib64/atlas -L/sw/appion/build/scipy/lib >>> -llapack -lf77blas -lcblas -latlas -lgfortran >>> LAPACK = -L/usr/lib64 -L/usr/lib64/atlas -L/sw/appion/build/scipy/lib >>> -llapack -lf77blas -lcblas -latlas -lgfortran >>> >>> libumfpack.a appears to build, but then there's a fatal error during >>> the makefile's scripted post-compile tests: >>> >>> make[1]: [run] Error 1 (ignored) >>> ./umfpack_zi_demo > my_umfpack_zi_demo.out >>> /bin/sh: line 1: 26275 Illegal instruction ? ? ./umfpack_zi_demo >>>>my_umfpack_zi_demo.out >>> make[1]: *** [run] Error 132 >>> make[1]: Leaving directory `/tmp/scipy/UMFPACK/Demo' >>> make: *** [library] Error 2 >>> >>> Further investigation with gdb shows this is occurring in libatlas: >>> >>> Program received signal SIGILL, Illegal instruction. >>> [Switching to Thread 0x2b5dbec9fe80 (LWP 30803)] >>> 0x00002b5dbde91f1f in NLOOP () from /usr/lib64/atlas/libatlas.so.3 >>> >>> Where can I find the src.rpm for the atlas packages so I can try doing >>> a local rebuild? >>> >>> thanks >>> slaton >>> _______________________________________________ >>> Caos mailing list >>> Caos at lists.infiscale.org >>> http://lists.infiscale.org/mailman/listinfo/caos >>> >> _______________________________________________ >> Caos mailing list >> Caos at lists.infiscale.org >> http://lists.infiscale.org/mailman/listinfo/caos >> > From ohiomike at ces-eng.net Sun Apr 11 14:25:31 2010 From: ohiomike at ces-eng.net (Michael C Castle) Date: Sun, 11 Apr 2010 17:25:31 -0400 Subject: [Caos] Illegal instruction when linking against libatlas In-Reply-To: References: Message-ID: <4BC23E4B.3060302@ces-eng.net> What CPU are you running on? I found out the hard way that some X64 opcodes are legal on AMD's and newer Intel's are illegal on a Pentium D (and maybe some earlier Xeon's). On 4/11/2010 16:56, Slaton Lipscomb wrote: > To any Caos folks, > > I'd still like to try rebuilding the atlas and atlas-devel packages > from srpm. Where can I find the srpms for Caos-NSA? > > One additional tidbit, turns out this illegal instruction error > triggered an error caught by syslog: > > umfpack_zi_demo[26275] trap invalid opcode ip:2b3f881d5f1f > sp:7fff70490f98 error:0 in libatlas.so.3.0[2b3f87c6d000+695000] > > thanks > slaton > > On Wed, Apr 7, 2010 at 2:22 PM, Slaton Lipscomb > wrote: > >> Pierre, >> >> Thanks for the reply. >> >> But alas, I've already tried compiling against the static library >> which (while itself successful) unfortunately produced the same >> Illegal Instruction error during testing. >> >> regards >> slaton >> >> On Wed, Apr 7, 2010 at 3:49 AM, Pierre-Yves Langlois >> wrote: >> >>> Hi... I used libatlas once when I compiled xhpl. In my case I compiled >>> it using the static version of the lib atlas. Maybe you could try >>> that... >>> >>> LAdir = /usr/lib64/atlas >>> LAinc = -I/usr/include/atlas >>> LAlib = $(LAdir)/libcblas.a $(LAdir)/libatlas.a $(LAdir)/liblapack.a >>> >>> Here is the full make to compile xhpl... >>> http://pastebin.com/f65a6ba2 >>> >>> I hope this could help... >>> >>> On Wed, Apr 7, 2010 at 12:27 AM, Slaton Lipscomb >>> wrote: >>> >>>> I've run into an issue trying to compile UMFPACK, a sparse matrix >>>> package that is a prerequisite for building NumPy (and therefore >>>> SciPy). Platform is Caos-NSA x86_64 (AMD Opteron). >>>> >>>> UMFPACK includes among its prerequisites BLAS, LAPACK, and ATLAS. So I >>>> have the following Caos-NSA packages installed: >>>> >>>> atlas-3.8.2-1.caos.x86_64 >>>> atlas-devel-3.8.2-1.caos.x86_64 >>>> lapack-3.1.1-2.caos.x86_64 >>>> lapack-devel-3.1.1-2.caos.x86_64 >>>> blas-3.1.1-2.caos.x86_64 >>>> blas-devel-3.1.1-2.caos.x86_64 >>>> >>>> Using the following UFconfig.mk options: >>>> >>>> F77 = gfortran >>>> F77FLAGS = -O -m64 -fPIC >>>> CC = gcc >>>> CFLAGS = -O3 -fexceptions -m64 -fPIC >>>> >>>> BLAS = -L/usr/lib64 -L/usr/lib64/atlas -L/sw/appion/build/scipy/lib >>>> -llapack -lf77blas -lcblas -latlas -lgfortran >>>> LAPACK = -L/usr/lib64 -L/usr/lib64/atlas -L/sw/appion/build/scipy/lib >>>> -llapack -lf77blas -lcblas -latlas -lgfortran >>>> >>>> libumfpack.a appears to build, but then there's a fatal error during >>>> the makefile's scripted post-compile tests: >>>> >>>> make[1]: [run] Error 1 (ignored) >>>> ./umfpack_zi_demo> my_umfpack_zi_demo.out >>>> /bin/sh: line 1: 26275 Illegal instruction ./umfpack_zi_demo >>>> >>>>> my_umfpack_zi_demo.out >>>>> >>>> make[1]: *** [run] Error 132 >>>> make[1]: Leaving directory `/tmp/scipy/UMFPACK/Demo' >>>> make: *** [library] Error 2 >>>> >>>> Further investigation with gdb shows this is occurring in libatlas: >>>> >>>> Program received signal SIGILL, Illegal instruction. >>>> [Switching to Thread 0x2b5dbec9fe80 (LWP 30803)] >>>> 0x00002b5dbde91f1f in NLOOP () from /usr/lib64/atlas/libatlas.so.3 >>>> >>>> Where can I find the src.rpm for the atlas packages so I can try doing >>>> a local rebuild? >>>> >>>> thanks >>>> slaton >>>> _______________________________________________ >>>> Caos mailing list >>>> Caos at lists.infiscale.org >>>> http://lists.infiscale.org/mailman/listinfo/caos >>>> >>>> >>> _______________________________________________ >>> Caos mailing list >>> Caos at lists.infiscale.org >>> http://lists.infiscale.org/mailman/listinfo/caos >>> >>> >> > _______________________________________________ > Caos mailing list > Caos at lists.infiscale.org > http://lists.infiscale.org/mailman/listinfo/caos > > > From slaton.lipscomb at gmail.com Sun Apr 11 14:56:52 2010 From: slaton.lipscomb at gmail.com (Slaton Lipscomb) Date: Sun, 11 Apr 2010 14:56:52 -0700 Subject: [Caos] Illegal instruction when linking against libatlas In-Reply-To: <4BC23E4B.3060302@ces-eng.net> References: <4BC23E4B.3060302@ces-eng.net> Message-ID: Hi Michael, These are Opteron 2435 (compute nodes) and older Opteron 246 on the master node. Thanks for the reply. cheers slaton On Sun, Apr 11, 2010 at 2:25 PM, Michael C Castle wrote: > What CPU are you running on? I found out the hard way that some X64 > opcodes are legal > on AMD's and newer Intel's are illegal on a Pentium D (and maybe some > earlier Xeon's). > > > On 4/11/2010 16:56, Slaton Lipscomb wrote: >> To any Caos folks, >> >> I'd still like to try rebuilding the atlas and atlas-devel packages >> from srpm. Where can I find the srpms for Caos-NSA? >> >> One additional tidbit, turns out this illegal instruction error >> triggered an error caught by syslog: >> >> umfpack_zi_demo[26275] trap invalid opcode ip:2b3f881d5f1f >> sp:7fff70490f98 error:0 in libatlas.so.3.0[2b3f87c6d000+695000] >> >> thanks >> slaton >> >> On Wed, Apr 7, 2010 at 2:22 PM, Slaton Lipscomb >> ?wrote: >> >>> Pierre, >>> >>> Thanks for the reply. >>> >>> But alas, I've already tried compiling against the static library >>> which (while itself successful) unfortunately produced the same >>> Illegal Instruction error during testing. >>> >>> regards >>> slaton >>> >>> On Wed, Apr 7, 2010 at 3:49 AM, Pierre-Yves Langlois >>> ?wrote: >>> >>>> Hi... I used libatlas once when I compiled xhpl. In my case I compiled >>>> it using the static version of the lib atlas. Maybe you could try >>>> that... >>>> >>>> LAdir ? ? ? ?= /usr/lib64/atlas >>>> LAinc ? ? ? ?= -I/usr/include/atlas >>>> LAlib ? ? ? ?= $(LAdir)/libcblas.a $(LAdir)/libatlas.a $(LAdir)/liblapack.a >>>> >>>> Here is the full make to compile xhpl... >>>> http://pastebin.com/f65a6ba2 >>>> >>>> I hope this could help... >>>> >>>> On Wed, Apr 7, 2010 at 12:27 AM, Slaton Lipscomb >>>> ?wrote: >>>> >>>>> I've run into an issue trying to compile UMFPACK, a sparse matrix >>>>> package that is a prerequisite for building NumPy (and therefore >>>>> SciPy). Platform is Caos-NSA x86_64 (AMD Opteron). >>>>> >>>>> UMFPACK includes among its prerequisites BLAS, LAPACK, and ATLAS. So I >>>>> have the following Caos-NSA packages installed: >>>>> >>>>> atlas-3.8.2-1.caos.x86_64 >>>>> atlas-devel-3.8.2-1.caos.x86_64 >>>>> lapack-3.1.1-2.caos.x86_64 >>>>> lapack-devel-3.1.1-2.caos.x86_64 >>>>> blas-3.1.1-2.caos.x86_64 >>>>> blas-devel-3.1.1-2.caos.x86_64 >>>>> >>>>> Using the following UFconfig.mk options: >>>>> >>>>> F77 = gfortran >>>>> F77FLAGS = -O -m64 -fPIC >>>>> CC = gcc >>>>> CFLAGS = -O3 -fexceptions -m64 -fPIC >>>>> >>>>> BLAS = -L/usr/lib64 -L/usr/lib64/atlas -L/sw/appion/build/scipy/lib >>>>> -llapack -lf77blas -lcblas -latlas -lgfortran >>>>> LAPACK = -L/usr/lib64 -L/usr/lib64/atlas -L/sw/appion/build/scipy/lib >>>>> -llapack -lf77blas -lcblas -latlas -lgfortran >>>>> >>>>> libumfpack.a appears to build, but then there's a fatal error during >>>>> the makefile's scripted post-compile tests: >>>>> >>>>> make[1]: [run] Error 1 (ignored) >>>>> ./umfpack_zi_demo> ?my_umfpack_zi_demo.out >>>>> /bin/sh: line 1: 26275 Illegal instruction ? ? ./umfpack_zi_demo >>>>> >>>>>> my_umfpack_zi_demo.out >>>>>> >>>>> make[1]: *** [run] Error 132 >>>>> make[1]: Leaving directory `/tmp/scipy/UMFPACK/Demo' >>>>> make: *** [library] Error 2 >>>>> >>>>> Further investigation with gdb shows this is occurring in libatlas: >>>>> >>>>> Program received signal SIGILL, Illegal instruction. >>>>> [Switching to Thread 0x2b5dbec9fe80 (LWP 30803)] >>>>> 0x00002b5dbde91f1f in NLOOP () from /usr/lib64/atlas/libatlas.so.3 >>>>> >>>>> Where can I find the src.rpm for the atlas packages so I can try doing >>>>> a local rebuild? >>>>> >>>>> thanks >>>>> slaton >>>>> _______________________________________________ >>>>> Caos mailing list >>>>> Caos at lists.infiscale.org >>>>> http://lists.infiscale.org/mailman/listinfo/caos >>>>> >>>>> >>>> _______________________________________________ >>>> Caos mailing list >>>> Caos at lists.infiscale.org >>>> http://lists.infiscale.org/mailman/listinfo/caos >>>> >>>> >>> >> _______________________________________________ >> Caos mailing list >> Caos at lists.infiscale.org >> http://lists.infiscale.org/mailman/listinfo/caos >> >> >> > _______________________________________________ > Caos mailing list > Caos at lists.infiscale.org > http://lists.infiscale.org/mailman/listinfo/caos > From krisp.caos at gmail.com Mon Apr 12 16:18:01 2010 From: krisp.caos at gmail.com (Krishna Prabhala) Date: Mon, 12 Apr 2010 19:18:01 -0400 Subject: [Caos] caos wiki site hacked? Message-ID: Hi, The Caos wiki page seems to be hacked. It is displaying some garbage. I was trying to install caos linux on one of our clusters today but the package installation halts midway. Connection to the package repository breaks after installing 20% or so. Can someone please fix the problem asap? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.infiscale.org/pipermail/caos/attachments/20100412/f046143b/attachment.html From krisp.caos at gmail.com Tue Apr 13 07:50:03 2010 From: krisp.caos at gmail.com (Krishna Prabhala) Date: Tue, 13 Apr 2010 10:50:03 -0400 Subject: [Caos] Thanks! Message-ID: Thanks for fixing the wiki page. Just wanted to mention that while installing caos from live media (CD), the default package installation during setup still quits with a 'Service temporarily Overloaded' message. I could install the packages I wanted using the smart package manager, thanks to the howto on Wiki. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.infiscale.org/pipermail/caos/attachments/20100413/c92bb3b5/attachment.html From astevens at infiscale.com Thu Apr 15 01:55:33 2010 From: astevens at infiscale.com (astevens at infiscale.com) Date: Thu, 15 Apr 2010 08:55:33 +0000 Subject: [Caos] caos wiki site hacked? In-Reply-To: References: Message-ID: <183039060-1271321732-cardhu_decombobulator_blackberry.rim.net-404910324-@bda505.bisx.prod.on.blackberry> All fixed up, we have had to set permissions a little less open than we like for an open source wiki but you know how that goes.. Was not hacked, someone with an account was just a jerk. Guess we got to feel like wikipedia for the day ;) Sent via BlackBerry from T-Mobile -----Original Message----- From: Krishna Prabhala Date: Mon, 12 Apr 2010 19:18:01 To: Subject: [Caos] caos wiki site hacked? _______________________________________________ Caos mailing list Caos at lists.infiscale.org http://lists.infiscale.org/mailman/listinfo/caos