From mej at caosity.org Mon Oct 2 15:12:42 2006 From: mej at caosity.org (Michael Jennings) Date: Mon, 2 Oct 2006 18:12:42 -0400 Subject: [cAos] LAN (Realtek) Drivers In-Reply-To: <20060930032721.GZ16425@kainx.org> References: <9360993f0609231234k35d13df3r7cebdfb6b3351d2e@mail.gmail.com> <76A9034D-98C5-4021-94B4-A81C1B614D53@runlevelzero.net> <20060929183212.GQ16425@kainx.org> <20060930032721.GZ16425@kainx.org> Message-ID: <20061002221242.GP23858@kainx.org> On Friday, 29 September 2006, at 23:27:21 (-0400), Michael Jennings wrote: > http://mirror.caosity.org/cAos-2/install/caos-2-2.2a.i386.iso Boned. :-( This ISO has some fairly serious issues. I've posted a corrected ISO here: http://mirror.caosity.org/cAos-2/install/caos-2-2.2b.i386.iso This one has the very latest kernel and has successfully been installed on a brand-spankin-new Supermicro 6025B-T/8, so you shouldn't have any problems with it. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "I don't mind the sun sometimes, the images it shows. I can taste you on my lips and smell you in my clothes. Cinnamon-and-sugary and softly-spoken lies. You never know just how you look through other people's eyes." -- Butthole Surfers, "Pepper" From benjamin at py-soft.co.uk Wed Oct 4 04:35:39 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Wed, 04 Oct 2006 12:35:39 +0100 Subject: [cAos] caos3 development In-Reply-To: <00e601c6dad0$05abb670$0d00a8c0@astevens> References: <20060604050900.GB14645@aries.runlevelzero.net><450D77C6.9050203@py-soft.co.uk> <00e601c6dad0$05abb670$0d00a8c0@astevens> Message-ID: <45239C8B.7070604@py-soft.co.uk> Arthur A. Stevens wrote: > Looks like Ben just volunteered for all kinds of projects ;) I'm hoping that it's mostly tidying up stuff that I've already got running under cAos-2 - thus making the swap easier! :-) I've just finished a long stint at work and I've now got some time off... so I should hopefully make some progress! :-) Take care, Ben From slaton at berkeley.edu Thu Oct 5 00:09:16 2006 From: slaton at berkeley.edu (slaton) Date: Thu, 5 Oct 2006 00:09:16 -0700 (PDT) Subject: [cAos] LAN (Realtek) Drivers In-Reply-To: <20061002221242.GP23858@kainx.org> References: <9360993f0609231234k35d13df3r7cebdfb6b3351d2e@mail.gmail.com> <76A9034D-98C5-4021-94B4-A81C1B614D53@runlevelzero.net> <20060929183212.GQ16425@kainx.org> <20060930032721.GZ16425@kainx.org> <20061002221242.GP23858@kainx.org> Message-ID: Thanks for the 2-2.2b iso. Worked great here. :) Actually it was pretty burnt initially -- i used an xfs boot partition, which of course triggers a well known bug that causes grub to die nastily when installing the bootloader. BUG : xfs_io/14625 lock held at task exit time! [dfa25970] {init_once} held by: xfs_io: 14625 [e26cf550, (18) I think previous versions of cinch i've used had a specific warning about this bug, or maybe even forbid it. thanks again slaton Slaton Lipscomb Nogales Lab, Howard Hughes Medical Institute http://cryoem.berkeley.edu On Mon, 2 Oct 2006, Michael Jennings wrote: > On Friday, 29 September 2006, at 23:27:21 (-0400), > Michael Jennings wrote: > > > http://mirror.caosity.org/cAos-2/install/caos-2-2.2a.i386.iso > > Boned. :-( > > This ISO has some fairly serious issues. I've posted a corrected ISO > here: > > http://mirror.caosity.org/cAos-2/install/caos-2-2.2b.i386.iso > > This one has the very latest kernel and has successfully been installed > on a brand-spankin-new Supermicro 6025B-T/8, so you shouldn't have any > problems with it. > > Michael From benjamin at py-soft.co.uk Thu Oct 5 06:51:44 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Thu, 05 Oct 2006 14:51:44 +0100 Subject: [cAos] caos3 development In-Reply-To: References: <20060604050900.GB14645@aries.runlevelzero.net> <450D77C6.9050203@py-soft.co.uk> Message-ID: <45250DF0.90608@py-soft.co.uk> Greg Kurtzer wrote: > Interested for cAos-3! :) Initial patches for pam_lastlog and the lastlog utility sent to your private email. Ben From benjamin at py-soft.co.uk Thu Oct 5 06:56:50 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Thu, 05 Oct 2006 14:56:50 +0100 Subject: [cAos] caos3 development In-Reply-To: <45115121.6060802@py-soft.co.uk> References: <20060604050900.GB14645@aries.runlevelzero.net> <450D88B6.8080905@py-soft.co.uk> <20060918031313.GD22369@kainx.org> <450E789A.6000908@py-soft.co.uk> <20060919032457.GG4415@kainx.org> <45115121.6060802@py-soft.co.uk> Message-ID: <45250F22.2080805@py-soft.co.uk> Benjamin Donnachie wrote: > Hopefully cAos should be fully supported in v1.2.9! :-) rkhunter 1.2.9 now supports cAos! I've submitted hashes for several versions and hopefully they should be available on the mirrors soon. Ben From benjamin at py-soft.co.uk Thu Oct 5 07:38:22 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Thu, 05 Oct 2006 15:38:22 +0100 Subject: [cAos] Postfix plea! In-Reply-To: <45073832.2020806@py-soft.co.uk> References: <03924a02b80f765745415e374a6677a4@www.py-soft.co.uk> <20060912203623.GD3630@kainx.org> <45073832.2020806@py-soft.co.uk> Message-ID: <452518DE.9090305@py-soft.co.uk> Benjamin Donnachie wrote: > I'm no longer using cAos on my desktop machine so I haven't been able to > test this... Compiles fine with cAos-3, but haven't got time to test fully at the moment. Ben From benjamin at py-soft.co.uk Thu Oct 5 09:03:04 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Thu, 05 Oct 2006 17:03:04 +0100 Subject: [cAos] Postfix plea! In-Reply-To: <452518DE.9090305@py-soft.co.uk> References: <03924a02b80f765745415e374a6677a4@www.py-soft.co.uk> <20060912203623.GD3630@kainx.org> <45073832.2020806@py-soft.co.uk> <452518DE.9090305@py-soft.co.uk> Message-ID: <45252CB8.2030007@py-soft.co.uk> Benjamin Donnachie wrote: > Compiles fine with cAos-3, but haven't got time to test fully at the moment. I still haven't got time, but I couldn't resist... # telnet localhost 25 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. 220 example.net ESMTP Postfix ehlo example.com [...] 250-STARTTLS [...] So patch works with cAos-3. Ben From mej at caosity.org Thu Oct 5 12:19:13 2006 From: mej at caosity.org (Michael Jennings) Date: Thu, 5 Oct 2006 15:19:13 -0400 Subject: [cAos] LAN (Realtek) Drivers In-Reply-To: References: <9360993f0609231234k35d13df3r7cebdfb6b3351d2e@mail.gmail.com> <76A9034D-98C5-4021-94B4-A81C1B614D53@runlevelzero.net> <20060929183212.GQ16425@kainx.org> <20060930032721.GZ16425@kainx.org> <20061002221242.GP23858@kainx.org> Message-ID: <20061005191913.GC6356@kainx.org> On Thursday, 05 October 2006, at 00:09:16 (-0700), slaton wrote: > Thanks for the 2-2.2b iso. Worked great here. :) Good to hear. :) I've got some boxes with I2O controllers needing to be rescued from RHEL3 hell by this new ISO. :-) > Actually it was pretty burnt initially -- i used an xfs boot > partition, which of course triggers a well known bug that causes > grub to die nastily when installing the bootloader. /boot defaulted to ext3 for my install; did it not for you, or did you manually put in XFS without realizing the problem? Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "Every little look inside your eyes is all it takes to make me realize we can last forever. Every little moment we can share, gonna let you know how much I care. I'll always be there." -- Chicago, "We Can Last Forever" From gmk at runlevelzero.net Thu Oct 5 12:35:49 2006 From: gmk at runlevelzero.net (Greg Kurtzer) Date: Thu, 5 Oct 2006 12:35:49 -0700 Subject: [cAos] Postfix plea! In-Reply-To: <45252CB8.2030007@py-soft.co.uk> References: <03924a02b80f765745415e374a6677a4@www.py-soft.co.uk> <20060912203623.GD3630@kainx.org> <45073832.2020806@py-soft.co.uk> <452518DE.9090305@py-soft.co.uk> <45252CB8.2030007@py-soft.co.uk> Message-ID: Fixed in caos3 postfix. :) I am not familiar with the configuration in postfix, so can you post some defaults that I can put in the config file? I would like to add them to the default configuration file commented out with a brief description of how to enable (if any other steps are necessary). Many thanks! Greg On Oct 5, 2006, at 9:03 AM, Benjamin Donnachie wrote: > Benjamin Donnachie wrote: >> Compiles fine with cAos-3, but haven't got time to test fully at >> the moment. > > I still haven't got time, but I couldn't resist... > > # telnet localhost 25 > Trying 127.0.0.1... > Connected to localhost.localdomain (127.0.0.1). > Escape character is '^]'. > 220 example.net ESMTP Postfix > ehlo example.com > [...] > 250-STARTTLS > [...] > > So patch works with cAos-3. > > Ben > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos -- Greg Kurtzer gmk at runlevelzero.net From benjamin at py-soft.co.uk Tue Oct 10 07:29:34 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Tue, 10 Oct 2006 15:29:34 +0100 Subject: [cAos] Postfix plea! In-Reply-To: References: <03924a02b80f765745415e374a6677a4@www.py-soft.co.uk> <20060912203623.GD3630@kainx.org> <45073832.2020806@py-soft.co.uk> <452518DE.9090305@py-soft.co.uk> <45252CB8.2030007@py-soft.co.uk> Message-ID: <452BAE4E.1060408@py-soft.co.uk> Greg Kurtzer wrote: > I am not familiar with the configuration in postfix, so can you post > some defaults that I can put in the config file? Sent direct. Ben From slaton at berkeley.edu Tue Oct 10 14:39:49 2006 From: slaton at berkeley.edu (slaton) Date: Tue, 10 Oct 2006 14:39:49 -0700 (PDT) Subject: [cAos] LAN (Realtek) Drivers In-Reply-To: <20061005191913.GC6356@kainx.org> References: <9360993f0609231234k35d13df3r7cebdfb6b3351d2e@mail.gmail.com> <76A9034D-98C5-4021-94B4-A81C1B614D53@runlevelzero.net> <20060929183212.GQ16425@kainx.org> <20060930032721.GZ16425@kainx.org> <20061002221242.GP23858@kainx.org> <20061005191913.GC6356@kainx.org> Message-ID: > > Actually it was pretty burnt initially -- i used an xfs boot > > partition, which of course triggers a well known bug that causes grub > > to die nastily when installing the bootloader. > > /boot defaulted to ext3 for my install; did it not for you, or did you > manually put in XFS without realizing the problem? i initially used one partition for everything (save swap). this is just a small, underperforming dell box and i didn't want to mess with fdisk. so i selected xfs for / (which i believe was default). maybe cinch only defaults to ext3 for dedicated /boot partition? anyway, once i realized the error of my ways i went back and made an ext3 /boot partition. all good. thanks slaton From mej at caosity.org Tue Oct 10 14:44:33 2006 From: mej at caosity.org (Michael Jennings) Date: Tue, 10 Oct 2006 17:44:33 -0400 Subject: [cAos] LAN (Realtek) Drivers In-Reply-To: References: <9360993f0609231234k35d13df3r7cebdfb6b3351d2e@mail.gmail.com> <76A9034D-98C5-4021-94B4-A81C1B614D53@runlevelzero.net> <20060929183212.GQ16425@kainx.org> <20060930032721.GZ16425@kainx.org> <20061002221242.GP23858@kainx.org> <20061005191913.GC6356@kainx.org> Message-ID: <20061010214433.GJ31605@kainx.org> On Tuesday, 10 October 2006, at 14:39:49 (-0700), slaton wrote: > maybe cinch only defaults to ext3 for dedicated /boot partition? That's my guess. I smell a cinch bug. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "A study in the Washington Post says that women have better verbal skills than men. I just want to say to the authors of that study: Duh." -- Conan O'Brien From slaton at berkeley.edu Tue Oct 10 14:45:39 2006 From: slaton at berkeley.edu (slaton) Date: Tue, 10 Oct 2006 14:45:39 -0700 (PDT) Subject: [cAos] questions re: libexpat required by ati driver... Message-ID: Am installing the ati driver (fglrx_6_8_0-8.29.6-1.i386.rpm) on a box according to the caos wiki directions: https://wiki.caosity.org/tiki-index.php?page=ATI%20Xorg%206.8%20Driver A dependency comes up for libexpat.so.1. Latest stable package expat-1.95.5-6 includes libexpat.so.0.4.0. Nothing newer in current or testing. Anyone done this and know if i can just --nodeps and be happy? thanks slaton Slaton Lipscomb Nogales Lab, Howard Hughes Medical Institute http://cryoem.berkeley.edu From slaton at berkeley.edu Tue Oct 17 13:15:11 2006 From: slaton at berkeley.edu (slaton) Date: Tue, 17 Oct 2006 13:15:11 -0700 (PDT) Subject: [cAos] possible missing symlink in gcc-g77 Message-ID: Fwiw.... i had to add a symlink for libg2c.so to /usr/lib in order to get the package SUPRIM (http://ami.scripps.edu/software/suprim/) to build. /usr/lib/libg2c.so -> libg2c.so.0 Don't have any non-caos boxes around anymore ;) to check and see if this is standard with other distros' gcc packages. slaton Slaton Lipscomb Nogales Lab, Howard Hughes Medical Institute http://cryoem.berkeley.edu From baucom at msg.ucsf.edu Tue Oct 24 10:48:10 2006 From: baucom at msg.ucsf.edu (Albion Baucom) Date: Tue, 24 Oct 2006 10:48:10 -0700 Subject: [cAos] Samba File Size Support Message-ID: <2A625A0C-E723-4497-B1B3-3BB807BB4CDA@msg.ucsf.edu> It appears that using smbfs in cAos has a 2GB file size limit. Is this a limitation I can overcome by rolling my own kernel, or a client/server issue? I am using the samba client version 3.0.23b-1 with Caos kernel version 2.6.17.11-102. Can anyone comment on this particular limitation? I have posted to the Samba list with nary a responce ... and have attempted to use CIFS as an alternate mount protocol, although I have been unable to figure out permissions using CIFS (permissions work fine with smbfs). Thanks Albion From gmk at runlevelzero.net Tue Oct 24 17:36:50 2006 From: gmk at runlevelzero.net (Greg Kurtzer) Date: Tue, 24 Oct 2006 17:36:50 -0700 Subject: [cAos] New bug tracking system implemented Message-ID: <4AD51DB8-5EE1-45C7-AF3E-8954C255FA53@runlevelzero.net> I have implemented a new bug tracking system for Caos Linux. It can be found at: http://bugs.caoslinux.org If you have any open bugs in any versions of Caos that are still causing you problems, please get an account with the new system and repost it. The reason for the change is that the new system is more suited for distribution maintenance (IMHO) and all of the testers have reported that they felt it was easier to use and a nicer general interface. Thanks. -- Greg Kurtzer gmk at runlevelzero.net From slaton at berkeley.edu Wed Oct 25 20:19:32 2006 From: slaton at berkeley.edu (slaton) Date: Wed, 25 Oct 2006 20:19:32 -0700 (PDT) Subject: [cAos] USB flash drives, haldaemon & grsecurity Message-ID: USB flash drives aren't working for me since the recent kernel upgrades that added grsecurity. Scratching the surface a bit reveals that the user hald (HAL daemon) process is being killed by grsec. Example: hald[495]: segfault at 0000000000000000 rip 00002ae602113290 rsp 00007fffa9420668 error 4 grsec: signal 11 sent to /usr/sbin/hald[hald:495] uid/euid:0/0 gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 for /usr/sbin/hald[hald:495] uid/euid:0/0 gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 Anyone found a workaround for this issue? I assume there is some grsec policy i need to create or amend, but i'm a grsec n00b. Didn't see anything in the grsec forums related to this. Fwiw i am seeing this on both i386 and x86_64 platforms. thanks slaton Slaton Lipscomb Nogales Lab, Howard Hughes Medical Institute http://cryoem.berkeley.edu From gmk at runlevelzero.net Thu Oct 26 09:15:12 2006 From: gmk at runlevelzero.net (Greg Kurtzer) Date: Thu, 26 Oct 2006 09:15:12 -0700 Subject: [cAos] USB flash drives, haldaemon & grsecurity In-Reply-To: References: Message-ID: <7E98A643-971F-4FB7-8630-E9C8A03A17C2@runlevelzero.net> I believe that GRSecurity policies are only engaged if your running gradm but with that said, the GRSec kernel patches add a bit more sanity checking. I would suggest to add this to the new bug tracking system. :) Thanks! On Oct 25, 2006, at 8:19 PM, slaton wrote: > USB flash drives aren't working for me since the recent kernel > upgrades > that added grsecurity. > > Scratching the surface a bit reveals that the user hald (HAL daemon) > process is being killed by grsec. Example: > > hald[495]: segfault at 0000000000000000 rip 00002ae602113290 rsp > 00007fffa9420668 error 4 > > grsec: signal 11 sent to /usr/sbin/hald[hald:495] uid/euid:0/0 > gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 > > grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE > against > limit 0 for /usr/sbin/hald[hald:495] uid/euid:0/0 gid/egid:0/0, parent > /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 > > Anyone found a workaround for this issue? I assume there is some grsec > policy i need to create or amend, but i'm a grsec n00b. Didn't see > anything in the grsec forums related to this. > > Fwiw i am seeing this on both i386 and x86_64 platforms. > > thanks > slaton > > Slaton Lipscomb > Nogales Lab, Howard Hughes Medical Institute > http://cryoem.berkeley.edu > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos -- Greg Kurtzer gmk at runlevelzero.net From martyn at theendofhistether.org.uk Thu Oct 26 12:24:28 2006 From: martyn at theendofhistether.org.uk (Martyn) Date: Thu, 26 Oct 2006 20:24:28 +0100 Subject: [cAos] USB flash drives, haldaemon & grsecurity In-Reply-To: <7E98A643-971F-4FB7-8630-E9C8A03A17C2@runlevelzero.net> References: <7E98A643-971F-4FB7-8630-E9C8A03A17C2@runlevelzero.net> Message-ID: <45410B6C.3090305@theendofhistether.org.uk> I too am seeing lots of GRSec kernel errors, and yup hald isn't running here because of it too. I'm wondering if it's also what's not allowing me to get dri/drm in X on my laptop. That deserves a bug report when I get time too :-) -- Martyn (Joran) Greg Kurtzer wrote: > I believe that GRSecurity policies are only engaged if your running > gradm but with that said, the GRSec kernel patches add a bit more > sanity checking. > > I would suggest to add this to the new bug tracking system. :) > > Thanks! > > On Oct 25, 2006, at 8:19 PM, slaton wrote: > > >> USB flash drives aren't working for me since the recent kernel >> upgrades >> that added grsecurity. >> >> Scratching the surface a bit reveals that the user hald (HAL daemon) >> process is being killed by grsec. Example: >> >> hald[495]: segfault at 0000000000000000 rip 00002ae602113290 rsp >> 00007fffa9420668 error 4 >> >> grsec: signal 11 sent to /usr/sbin/hald[hald:495] uid/euid:0/0 >> gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 >> >> grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE >> against >> limit 0 for /usr/sbin/hald[hald:495] uid/euid:0/0 gid/egid:0/0, parent >> /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 >> >> Anyone found a workaround for this issue? I assume there is some grsec >> policy i need to create or amend, but i'm a grsec n00b. Didn't see >> anything in the grsec forums related to this. >> >> Fwiw i am seeing this on both i386 and x86_64 platforms. >> >> thanks >> slaton >> >> Slaton Lipscomb >> Nogales Lab, Howard Hughes Medical Institute >> http://cryoem.berkeley.edu >> _______________________________________________ >> cAos mailing list >> cAos at caosity.org >> http://lists.caosity.org/mailman/listinfo/caos >> > > -- > Greg Kurtzer > gmk at runlevelzero.net > > > > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.infiscale.org/pipermail/caos/attachments/20061026/79d73af8/attachment.html From astevens at gravitypark.com Thu Oct 26 12:50:56 2006 From: astevens at gravitypark.com (Arthur A. Stevens) Date: Thu, 26 Oct 2006 12:50:56 -0700 Subject: [cAos] USB flash drives, haldaemon & grsecurity References: Message-ID: <001801c6f938$0d97ba10$0d00a8c0@astevens> have you tried to chpax or paxctl (on newer versions) the hal daemon or anything else getting killed? I will play with caos2 this weekend with the grsec and start making a list of stuff we can do to smooth out these issues. we can setup a pax.cfg that allows hald, x, and others to run without complaints. thanks for the heads up :) ----- Original Message ----- From: "slaton" To: "Community Assembled OS" Sent: Wednesday, October 25, 2006 8:19 PM Subject: [cAos] USB flash drives, haldaemon & grsecurity > USB flash drives aren't working for me since the recent kernel upgrades > that added grsecurity. > > Scratching the surface a bit reveals that the user hald (HAL daemon) > process is being killed by grsec. Example: > > hald[495]: segfault at 0000000000000000 rip 00002ae602113290 rsp > 00007fffa9420668 error 4 > > grsec: signal 11 sent to /usr/sbin/hald[hald:495] uid/euid:0/0 > gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 > > grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE against > limit 0 for /usr/sbin/hald[hald:495] uid/euid:0/0 gid/egid:0/0, parent > /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 > > Anyone found a workaround for this issue? I assume there is some grsec > policy i need to create or amend, but i'm a grsec n00b. Didn't see > anything in the grsec forums related to this. > > Fwiw i am seeing this on both i386 and x86_64 platforms. > > thanks > slaton > > Slaton Lipscomb > Nogales Lab, Howard Hughes Medical Institute > http://cryoem.berkeley.edu > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos > From mej at caosity.org Thu Oct 26 13:06:43 2006 From: mej at caosity.org (Michael Jennings) Date: Thu, 26 Oct 2006 16:06:43 -0400 Subject: [cAos] USB flash drives, haldaemon & grsecurity In-Reply-To: References: Message-ID: <20061026200643.GK11672@kainx.org> On Wednesday, 25 October 2006, at 20:19:32 (-0700), slaton wrote: > USB flash drives aren't working for me since the recent kernel upgrades > that added grsecurity. > > Scratching the surface a bit reveals that the user hald (HAL daemon) > process is being killed by grsec. Example: > > hald[495]: segfault at 0000000000000000 rip 00002ae602113290 rsp > 00007fffa9420668 error 4 > > grsec: signal 11 sent to /usr/sbin/hald[hald:495] uid/euid:0/0 > gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 > > grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE against > limit 0 for /usr/sbin/hald[hald:495] uid/euid:0/0 gid/egid:0/0, parent > /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 Same here, but it's not keeping me from using USB jump drives or anything. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "I am everything you want; I am everything you need. I am everything inside of you that you wish you could be. I say all the right things at exactly the right time, but I mean nothing to you and I don't know why." -- Vertical Horizon, "Everything" From slaton at berkeley.edu Thu Oct 26 13:40:24 2006 From: slaton at berkeley.edu (slaton) Date: Thu, 26 Oct 2006 13:40:24 -0700 (PDT) Subject: [cAos] USB flash drives, haldaemon & grsecurity In-Reply-To: <001801c6f938$0d97ba10$0d00a8c0@astevens> References: <001801c6f938$0d97ba10$0d00a8c0@astevens> Message-ID: Hi Arthur, Thanks for the reply. Other than knowing that grsecurity is a package that includes the PaX kernel patches, i'm admittedly a bit confused about the difference between PaX and grsecurity. Anyway.... I don't have any of the PaX utilities. Do you know which caos package, if any, includes paxctl? Or did you roll your own? thanks slaton Slaton Lipscomb Nogales Lab, Howard Hughes Medical Institute http://cryoem.berkeley.edu On Thu, 26 Oct 2006, Arthur A. Stevens wrote: > have you tried to chpax or paxctl (on newer versions) the hal daemon or > anything else getting killed? I will play with caos2 this weekend with the > grsec and start making a list of stuff we can do to smooth out these issues. > we can setup a pax.cfg that allows hald, x, and others to run without > complaints. > > thanks for the heads up :) > > > ----- Original Message ----- > From: "slaton" > To: "Community Assembled OS" > Sent: Wednesday, October 25, 2006 8:19 PM > Subject: [cAos] USB flash drives, haldaemon & grsecurity > > > > USB flash drives aren't working for me since the recent kernel > > upgrades that added grsecurity. > > > > Scratching the surface a bit reveals that the user hald (HAL daemon) > > process is being killed by grsec. Example: > > > > hald[495]: segfault at 0000000000000000 rip 00002ae602113290 rsp > > 00007fffa9420668 error 4 > > > > grsec: signal 11 sent to /usr/sbin/hald[hald:495] uid/euid:0/0 > > gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 > > > > grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE > > against limit 0 for /usr/sbin/hald[hald:495] uid/euid:0/0 > > gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 > > > > Anyone found a workaround for this issue? I assume there is some grsec > > policy i need to create or amend, but i'm a grsec n00b. Didn't see > > anything in the grsec forums related to this. > > > > Fwiw i am seeing this on both i386 and x86_64 platforms. > > > > thanks > > slaton > > > > Slaton Lipscomb > > Nogales Lab, Howard Hughes Medical Institute > > http://cryoem.berkeley.edu From slaton at berkeley.edu Thu Oct 26 18:50:29 2006 From: slaton at berkeley.edu (slaton) Date: Thu, 26 Oct 2006 18:50:29 -0700 (PDT) Subject: [cAos] New hardware....new x86_64 install image? Message-ID: Busy day here on the caos list ;) We have a new x86_64 box here that has an Asus KFN32-D SLI motherboard. Well it looks like i didn't do my homework as a couple of things here are more bleeding-edge than i prefer. They certainly aren't supported by the current (2.2.1a) x86_64 caos installer. - NVIDIA MCP55 Pro onboard HBA (sata controller). - Broadcom BCM5754 chip (dual gbit lan). Wrt the sata controller, i think a newer image might save the day here, as I believe the sata_nv driver was patched to support the MCP55 in late 2005. As for the BCM5754, newer versions of the tg3 driver support it. I believe the tg3 included with kernel 2.6.17.11-102 has this support -- this is version 3.59 from June 8 2006. According to the changelog support for 5754 was added March 20 2006. So....you knew this was where i was going...:) Could i trouble someone to roll an x86_64 build of the install image KainX recently posted (2.2.2b), assuming it includes 2.6.17.11? Or explain to me how to do it... :) thanks slaton Slaton Lipscomb Nogales Lab, Howard Hughes Medical Institute http://cryoem.berkeley.edu From mej at caosity.org Thu Oct 26 20:24:26 2006 From: mej at caosity.org (Michael Jennings) Date: Thu, 26 Oct 2006 23:24:26 -0400 Subject: [cAos] New hardware....new x86_64 install image? In-Reply-To: References: Message-ID: <20061027032426.GB9037@kainx.org> On Thursday, 26 October 2006, at 18:50:29 (-0700), slaton wrote: > So....you knew this was where i was going...:) Could i trouble > someone to roll an x86_64 build of the install image KainX recently > posted (2.2.2b), assuming it includes 2.6.17.11? Or explain to me > how to do it... :) Got an x86_64 box I can borrow? :) Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "I have gotten into the habit of recording important meetings. One never knows when an inconvenient truth will fall between the cracks and vanish." -- Ambassador Londo Mollari, Babylon Five From astevens at gravitypark.com Fri Oct 27 08:21:31 2006 From: astevens at gravitypark.com (Arthur A. Stevens) Date: Fri, 27 Oct 2006 08:21:31 -0700 Subject: [cAos] USB flash drives, haldaemon & grsecurity References: <001801c6f938$0d97ba10$0d00a8c0@astevens> Message-ID: <006901c6f9db$94ec8380$0d00a8c0@astevens> Hi Slaton, I rolled mine myself, but if you give me today to get with GMK, I will make sure we have something that you can just yum install this weekend. I'll get those hal issues rectified as well. Thanks, Arthur ----- Original Message ----- From: "slaton" To: "Community Assembled OS" Sent: Thursday, October 26, 2006 1:40 PM Subject: Re: [cAos] USB flash drives, haldaemon & grsecurity > Hi Arthur, > > Thanks for the reply. Other than knowing that grsecurity is a package that > includes the PaX kernel patches, i'm admittedly a bit confused about the > difference between PaX and grsecurity. > > Anyway.... I don't have any of the PaX utilities. Do you know which caos > package, if any, includes paxctl? Or did you roll your own? > > thanks > slaton > > Slaton Lipscomb > Nogales Lab, Howard Hughes Medical Institute > http://cryoem.berkeley.edu > > On Thu, 26 Oct 2006, Arthur A. Stevens wrote: > >> have you tried to chpax or paxctl (on newer versions) the hal daemon or >> anything else getting killed? I will play with caos2 this weekend with >> the >> grsec and start making a list of stuff we can do to smooth out these >> issues. >> we can setup a pax.cfg that allows hald, x, and others to run without >> complaints. >> >> thanks for the heads up :) >> >> >> ----- Original Message ----- >> From: "slaton" >> To: "Community Assembled OS" >> Sent: Wednesday, October 25, 2006 8:19 PM >> Subject: [cAos] USB flash drives, haldaemon & grsecurity >> >> >> > USB flash drives aren't working for me since the recent kernel >> > upgrades that added grsecurity. >> > >> > Scratching the surface a bit reveals that the user hald (HAL daemon) >> > process is being killed by grsec. Example: >> > >> > hald[495]: segfault at 0000000000000000 rip 00002ae602113290 rsp >> > 00007fffa9420668 error 4 >> > >> > grsec: signal 11 sent to /usr/sbin/hald[hald:495] uid/euid:0/0 >> > gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 >> > >> > grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE >> > against limit 0 for /usr/sbin/hald[hald:495] uid/euid:0/0 >> > gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 >> > >> > Anyone found a workaround for this issue? I assume there is some grsec >> > policy i need to create or amend, but i'm a grsec n00b. Didn't see >> > anything in the grsec forums related to this. >> > >> > Fwiw i am seeing this on both i386 and x86_64 platforms. >> > >> > thanks >> > slaton >> > >> > Slaton Lipscomb >> > Nogales Lab, Howard Hughes Medical Institute >> > http://cryoem.berkeley.edu > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos > From slaton at berkeley.edu Fri Oct 27 10:43:40 2006 From: slaton at berkeley.edu (slaton) Date: Fri, 27 Oct 2006 10:43:40 -0700 (PDT) Subject: [cAos] USB flash drives, haldaemon & grsecurity In-Reply-To: <006901c6f9db$94ec8380$0d00a8c0@astevens> References: <001801c6f938$0d97ba10$0d00a8c0@astevens> <006901c6f9db$94ec8380$0d00a8c0@astevens> Message-ID: Arthur, thanks. Although i have to admit that Michael is correct. ;) Flash drives are indeed working....(now that i have a properly configured autofs that is...) thanks slaton Slaton Lipscomb Nogales Lab, Howard Hughes Medical Institute http://cryoem.berkeley.edu On Fri, 27 Oct 2006, Arthur A. Stevens wrote: > Hi Slaton, > > I rolled mine myself, but if you give me today to get with GMK, I will make > sure we have something that you can just yum install this weekend. I'll get > those hal issues rectified as well. > > Thanks, > > Arthur > ----- Original Message ----- > From: "slaton" > To: "Community Assembled OS" > Sent: Thursday, October 26, 2006 1:40 PM > Subject: Re: [cAos] USB flash drives, haldaemon & grsecurity > > > > Hi Arthur, > > > > Thanks for the reply. Other than knowing that grsecurity is a package that > > includes the PaX kernel patches, i'm admittedly a bit confused about the > > difference between PaX and grsecurity. > > > > Anyway.... I don't have any of the PaX utilities. Do you know which caos > > package, if any, includes paxctl? Or did you roll your own? > > > > thanks > > slaton > > > > Slaton Lipscomb > > Nogales Lab, Howard Hughes Medical Institute > > http://cryoem.berkeley.edu > > > > On Thu, 26 Oct 2006, Arthur A. Stevens wrote: > > > >> have you tried to chpax or paxctl (on newer versions) the hal daemon or > >> anything else getting killed? I will play with caos2 this weekend with > >> the > >> grsec and start making a list of stuff we can do to smooth out these > >> issues. > >> we can setup a pax.cfg that allows hald, x, and others to run without > >> complaints. > >> > >> thanks for the heads up :) > >> > >> > >> ----- Original Message ----- > >> From: "slaton" > >> To: "Community Assembled OS" > >> Sent: Wednesday, October 25, 2006 8:19 PM > >> Subject: [cAos] USB flash drives, haldaemon & grsecurity > >> > >> > >> > USB flash drives aren't working for me since the recent kernel > >> > upgrades that added grsecurity. > >> > > >> > Scratching the surface a bit reveals that the user hald (HAL daemon) > >> > process is being killed by grsec. Example: > >> > > >> > hald[495]: segfault at 0000000000000000 rip 00002ae602113290 rsp > >> > 00007fffa9420668 error 4 > >> > > >> > grsec: signal 11 sent to /usr/sbin/hald[hald:495] uid/euid:0/0 > >> > gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 > >> > > >> > grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE > >> > against limit 0 for /usr/sbin/hald[hald:495] uid/euid:0/0 > >> > gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0 > >> > > >> > Anyone found a workaround for this issue? I assume there is some grsec > >> > policy i need to create or amend, but i'm a grsec n00b. Didn't see > >> > anything in the grsec forums related to this. > >> > > >> > Fwiw i am seeing this on both i386 and x86_64 platforms. > >> > > >> > thanks > >> > slaton > >> > > >> > Slaton Lipscomb > >> > Nogales Lab, Howard Hughes Medical Institute > >> > http://cryoem.berkeley.edu > > _______________________________________________ > > cAos mailing list > > cAos at caosity.org > > http://lists.caosity.org/mailman/listinfo/caos > > > > > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos > From slaton at berkeley.edu Fri Oct 27 10:44:30 2006 From: slaton at berkeley.edu (slaton) Date: Fri, 27 Oct 2006 10:44:30 -0700 (PDT) Subject: [cAos] New hardware....new x86_64 install image? In-Reply-To: <20061027032426.GB9037@kainx.org> References: <20061027032426.GB9037@kainx.org> Message-ID: No problem, will contact you off-list. slaton Slaton Lipscomb Nogales Lab, Howard Hughes Medical Institute http://cryoem.berkeley.edu On Thu, 26 Oct 2006, Michael Jennings wrote: > On Thursday, 26 October 2006, at 18:50:29 (-0700), > slaton wrote: > > > So....you knew this was where i was going...:) Could i trouble someone > > to roll an x86_64 build of the install image KainX recently posted > > (2.2.2b), assuming it includes 2.6.17.11? Or explain to me how to do > > it... :) > > Got an x86_64 box I can borrow? :) > > Michael > > -- > Michael Jennings (a.k.a. KainX) http://www.kainx.org/ > n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) > ----------------------------------------------------------------------- > "I have gotten into the habit of recording important meetings. One > never knows when an inconvenient truth will fall between the cracks > and vanish." -- Ambassador Londo Mollari, Babylon Five From mej at caosity.org Mon Oct 30 14:23:17 2006 From: mej at caosity.org (Michael Jennings) Date: Mon, 30 Oct 2006 17:23:17 -0500 Subject: [cAos] Samba File Size Support In-Reply-To: <2A625A0C-E723-4497-B1B3-3BB807BB4CDA@msg.ucsf.edu> References: <2A625A0C-E723-4497-B1B3-3BB807BB4CDA@msg.ucsf.edu> Message-ID: <20061030222317.GM10901@kainx.org> On Tuesday, 24 October 2006, at 10:48:10 (-0700), Albion Baucom wrote: > It appears that using smbfs in cAos has a 2GB file size limit. Is > this a limitation I can overcome by rolling my own kernel, or a > client/server issue? I am using the samba client version 3.0.23b-1 > with Caos kernel version 2.6.17.11-102. > > Can anyone comment on this particular limitation? I have posted to > the Samba list with nary a responce ... and have attempted to use > CIFS as an alternate mount protocol, although I have been unable to > figure out permissions using CIFS (permissions work fine with > smbfs). Googling suggests there's an option ("lf" or "lfs" or something) to enable large file support. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "I don't care if you win or lose, just as long as you win." -- Vince Lombardi From mej at caosity.org Mon Oct 30 14:34:42 2006 From: mej at caosity.org (Michael Jennings) Date: Mon, 30 Oct 2006 17:34:42 -0500 Subject: [cAos] silence? In-Reply-To: References: <20061023205343.GC29557@kainx.org> Message-ID: <20061030223442.GN10901@kainx.org> On Tuesday, 24 October 2006, at 17:03:56 (+0200), Alex Solli wrote: > I tried the beta 3, but it gave me error messages about my hard disk > not being found. I burned the ISO image again, but the same message > came. This sounds like a hardware support issue. Are your hard drives on some kind of RAID controller? SATA? What type of drives are they? > So, cAos 2.2 is on the way? Any release date? The 2.2 ISO for IA-32 is already posted. The ISO for x86_64 is pending testing. > Do you have an exact adress to the mirror where I can download the > lates cAos version? http://mirror.caosity.org/ Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "I gather myself around my faith, for the Light is the Darkness most feared." -- Jewel, "Hands" From mej at caosity.org Tue Oct 31 23:33:04 2006 From: mej at caosity.org (Michael Jennings) Date: Wed, 1 Nov 2006 02:33:04 -0500 Subject: [cAos] silence? In-Reply-To: <20061030223442.GN10901@kainx.org> References: <20061023205343.GC29557@kainx.org> <20061030223442.GN10901@kainx.org> Message-ID: <20061101073304.GO11672@kainx.org> On Monday, 30 October 2006, at 17:34:42 (-0500), Michael Jennings wrote: > The 2.2 ISO for IA-32 is already posted. The ISO for x86_64 is > pending testing. And thanks to Slaton, that testing is complete. 2.2b ISO's are now current and posted on master.caosity.org; mirrors should soon follow. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "Feel your breath on my shoulder, and I know we couldn't get any closer. I don't want to act tough; I just want to fall in love as we move into the night." -- Peter Cetera and Crystal Bernard, "(I Wanna Take) Forever Tonight"