From owner-kernel-audit@nl.linux.org Tue Jan 9 20:09:44 2001 Received: by humbolt.nl.linux.org id ; Tue, 9 Jan 2001 20:08:22 +0100 Received: from terra.geo.uu.nl ([131.211.29.16]:32169 "EHLO terra.geo.uu.nl") by humbolt.nl.linux.org with ESMTP id ; Tue, 9 Jan 2001 20:07:42 +0100 Received: from creeper.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by terra.geo.uu.nl (8.9.3/8.9.3/TvZ) with ESMTP id UAA20454 for ; Tue, 9 Jan 2001 20:07:40 +0100 (MET) Received: from ec02-hou.bmc.com (localhost [127.0.0.1]) by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id f09J7DK06051 for ; Tue, 9 Jan 2001 13:07:13 -0600 (CST) Received: by EC02-HOU.bmc.com with Internet Mail Service (5.5.2650.21) id ; Tue, 9 Jan 2001 13:07:26 -0600 Message-ID: From: "Burns, John" To: "'kernel-audit@mail.nl.linux.org'" Subject: project status Date: Tue, 9 Jan 2001 13:10:55 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-kernel-audit@nl.linux.org Precedence: bulk Return-Path: X-Orcpt: rfc822;kernel-audit-list So what's going on? Is this project still active? Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/ From owner-kernel-audit@nl.linux.org Tue Jan 9 21:27:56 2001 Received: by humbolt.nl.linux.org id ; Tue, 9 Jan 2001 21:26:46 +0100 Received: from terra.geo.uu.nl ([131.211.29.16]:26797 "EHLO terra.geo.uu.nl") by humbolt.nl.linux.org with ESMTP id ; Tue, 9 Jan 2001 21:26:17 +0100 Received: from creeper.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by terra.geo.uu.nl (8.9.3/8.9.3/TvZ) with ESMTP id VAA22174 for ; Tue, 9 Jan 2001 21:26:15 +0100 (MET) Received: from ec02-hou.bmc.com (localhost [127.0.0.1]) by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id f09KNBj17673; Tue, 9 Jan 2001 14:23:16 -0600 (CST) Received: by EC02-HOU.bmc.com with Internet Mail Service (5.5.2650.21) id ; Tue, 9 Jan 2001 14:23:24 -0600 Message-ID: From: "Burns, John" To: "'George Capehart'" , "Burns, John" Cc: "'kernel-audit@mail.nl.linux.org'" Subject: RE: project status Date: Tue, 9 Jan 2001 14:26:53 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-kernel-audit@nl.linux.org Precedence: bulk Return-Path: X-Orcpt: rfc822;kernel-audit-list I'm ready for an assignment now. I don't know very much about compiling the kernel but I can at least point out common programming errors. Just tell me a file to examine or however this project is done. -----Original Message----- From: George Capehart [mailto:gwc@capehassoc.com] Sent: Tuesday, January 09, 2001 2:18 PM To: Burns, John Cc: 'kernel-audit@mail.nl.linux.org' Subject: Re: project status "Burns, John" wrote: > > So what's going on? Is this project still active? > > Kernel-audit: discussion list for security and the linux kernel > Archive: http://mail.nl.linux.org/kernel-audit/ Ya got me! I've stayed on the list 'cause I thought someone was taking it over. Then there was nothing . . . I'm assuming that since the list is alive that there is still some interest. If nothing else, those of us that are left can "do it by committee." FWIW -- George W. Capehart PCS Phone: +1 704.277.4561 Fax: +1 704.853.2624 Capehart Associates LLC 1604 Nottingham Drive To send a text message: Gastonia, NC 28054 http://www.messaging.sprintpcs.com Meskimen's Law of Quality: "There's never time to do it right, but there's always time to do it over." Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/ From owner-kernel-audit@nl.linux.org Tue Jan 9 21:44:26 2001 Received: by humbolt.nl.linux.org id ; Tue, 9 Jan 2001 21:43:04 +0100 Received: from brutus.conectiva.com.br ([200.250.58.146]:15867 "EHLO brinquedo.distro.conectiva") by humbolt.nl.linux.org with ESMTP id ; Tue, 9 Jan 2001 21:42:38 +0100 Received: by brinquedo.distro.conectiva (Postfix, from userid 501) id 9C7D62739; Tue, 9 Jan 2001 16:54:42 -0200 (EST) Date: Tue, 9 Jan 2001 16:54:42 -0200 From: Arnaldo Carvalho de Melo To: "Burns, John" Cc: "'George Capehart'" , "'kernel-audit@mail.nl.linux.org'" Subject: Re: project status Message-ID: <20010109165442.E24523@conectiva.com.br> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from John_Burns@bmc.com on Tue, Jan 09, 2001 at 02:26:53PM -0600 X-Url: http://advogato.org/person/acme Sender: owner-kernel-audit@nl.linux.org Precedence: bulk Return-Path: X-Orcpt: rfc822;kernel-audit-list Em Tue, Jan 09, 2001 at 02:26:53PM -0600, Burns, John escreveu: > I'm ready for an assignment now. I don't know very much about compiling > the kernel but I can at least point out > common programming errors. Just tell > me a file to examine or however this > project is done. look at http://bazar.conectiva.com.br/~acme/TODO plenty of things to fix Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/ From owner-kernel-audit@nl.linux.org Tue Jan 9 21:45:46 2001 Received: by humbolt.nl.linux.org id ; Tue, 9 Jan 2001 21:44:36 +0100 Received: from www.lemuria.org ([62.197.4.112]:19468 "EHLO mail.lemuria.org") by humbolt.nl.linux.org with ESMTP id ; Tue, 9 Jan 2001 21:43:39 +0100 Received: from unicorn.lemuria.org (pd950067c.dip.t-dialin.net [217.80.6.124]) by mail.lemuria.org (Postfix) with ESMTP id B11E827AEC for ; Tue, 9 Jan 2001 21:41:16 +0100 (MET) Received: by unicorn.lemuria.org (Postfix, from userid 1000) id 78EA9175182; Tue, 9 Jan 2001 21:40:57 +0100 (CET) Date: Tue, 9 Jan 2001 21:40:57 +0100 From: Tom To: kernel-audit@nl.linux.org Subject: Re: project status Message-ID: <20010109214056.E17136@lemuria.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from John_Burns@bmc.com on Tue, Jan 09, 2001 at 02:26:53PM -0600 Sender: owner-kernel-audit@nl.linux.org Precedence: bulk Return-Path: X-Orcpt: rfc822;kernel-audit-list > Ya got me! I've stayed on the list 'cause I thought someone was taking > it over. Then there was nothing . . . I'm assuming that since the list > is alive that there is still some interest. If nothing else, those of > us that are left can "do it by committee." there's definitely interest, but lack of time and other projects seem to be keeping most people (including me) away from actually doing anything. -- -- http://www.lemuria.org -- http://www.Nexus-Project.net -- Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/ From owner-kernel-audit@nl.linux.org Tue Jan 9 23:14:31 2001 Received: by humbolt.nl.linux.org id ; Tue, 9 Jan 2001 23:13:00 +0100 Received: from mail.securityportal.com ([64.85.88.246]:48393 "EHLO securityportal.com") by humbolt.nl.linux.org with ESMTP id ; Tue, 9 Jan 2001 23:12:31 +0100 Received: from [127.0.0.1] (HELO sQa) by securityportal.com (CommuniGate Pro SMTP 3.3.2) with SMTP id 228215 for kernel-audit@nl.linux.org; Tue, 09 Jan 2001 14:12:28 -0800 From: Bryan Paxton Reply-To: bpaxton@securityportal.com To: kernel-audit@nl.linux.org Subject: LKAP belongs to you... Date: Tue, 9 Jan 2001 16:05:48 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Message-Id: <01010916054801.00952@sQa> Content-Transfer-Encoding: 8bit Sender: owner-kernel-audit@nl.linux.org Precedence: bulk Return-Path: X-Orcpt: rfc822;kernel-audit-list Because of the discussion that has occured through out the day I've decided to put my two cents in. There is no need to wait around for an "official" project leader. Aaron Grothe of heimdall-linux has/had planned to take over managing efforts, or rather simply adopt these efforts. (which I'm sure you all saw his email) The status on this adoption is now unclear, but this does not change the fact that Linux belongs to you/us the community. Although it's quite clear that such a project did and still does need someone(s) in charge of managment (this includes taking over the list or setting up a new list). But the fact still remains... This belongs to you... . The communities actions will _always_ set the course that this project takes, whether it's progression or demise. I'm sure you all know this, but perhaps everyone needed to be reminded (including myself). As far as management... We'll wait and see what happens. But a community comitee by and for this project is definately the right direction IMHO. Regards, Bryan -- Bryan Paxton SecurityPortal, your focal point for security on the net. http://www.securityportal.com/ Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/ From owner-kernel-audit@nl.linux.org Wed Jan 10 00:00:12 2001 Received: by humbolt.nl.linux.org id ; Tue, 9 Jan 2001 23:58:43 +0100 Received: from terra.geo.uu.nl ([131.211.29.16]:28597 "EHLO terra.geo.uu.nl") by humbolt.nl.linux.org with ESMTP id ; Tue, 9 Jan 2001 23:58:09 +0100 Received: from newshub1-work.home.com (newshub1-work.home.com [24.0.0.24]) by terra.geo.uu.nl (8.9.3/8.9.3/TvZ) with ESMTP id XAA25437 for ; Tue, 9 Jan 2001 23:57:48 +0100 (MET) Received: from heimdall-linux.com (omhas1A-hfc-0251-d1da1639.ne.coxatwork.com [209.218.22.57] (may be forged)) by newshub1-work.home.com (8.11.0/8.11.0) with ESMTP id f09MvBm23440; Tue, 9 Jan 2001 14:57:21 -0800 (PST) Message-ID: <3A5B97BD.55B12763@heimdall-linux.com> Date: Tue, 09 Jan 2001 16:59:09 -0600 From: Aaron Grothe X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: bpaxton@securityportal.com CC: kernel-audit@nl.linux.org Subject: LKAP status Update References: <01010916054801.00952@sQa> Content-Type: multipart/mixed; boundary="------------FB111158AFB229F86D25E940" Sender: owner-kernel-audit@nl.linux.org Precedence: bulk Return-Path: X-Orcpt: rfc822;kernel-audit-list This is a multi-part message in MIME format. --------------FB111158AFB229F86D25E940 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi to all, I've been out of the office most of the day so I've just caught up on the mailing list activity. It is good to see some activity on the mailing list. :-) Basically, I'm still planning on following the initial plan I laid out in the manifesto. My schedule has been a bit busier lately than I would prefer so efforts have unfortunately lagged a bit. I never really heard anything back on the manifesto. A couple of people had some nice suggestions on the using a gcc with all the warning flags, and possibly making some mods to the lclint checker. If people could hit the mail archive and read my manifesto and give some feedback on it that would be tremendous. I'm going to try and mock up a few pages and examples to cover some of what I was talking about over the next week/week and a half. I'll post to the list when they are ready. And then hopefully, we can have a discussion and see if that is the way we should keep trying to go on things. And then we can see about implementing the system that results. As Bryan says everybody has to play a part if LKAP is going to be a success. If anybody has really good web skills and wants to volunteer to help with some of the layout it would be greatly appreciated. Regards, Aaron =-=-= "The Journey is the Reward" - Old Zen Buddhist Saying --------------FB111158AFB229F86D25E940 Content-Type: text/x-vcard; charset=us-ascii; name="grothe.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Aaron Grothe Content-Disposition: attachment; filename="grothe.vcf" begin:vcard n:Grothe;Aaron tel;cell:(402) 639-1380 tel;fax:(603) 299-8393 tel;home:(402) 561-9547 tel;work:(402) 934-1133 x-mozilla-html:FALSE url:http://www.heimdall-linux.com org:Heimdall Linux Incorporated;Management version:2.1 email;internet:grothe@heimdall-linux.com title:President/CEO adr;quoted-printable:;;3035 Harney Street=0D=0ASuite #102;Omaha;Nebraska;68131;United States of America fn:Aaron Grothe end:vcard --------------FB111158AFB229F86D25E940-- Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/ From owner-kernel-audit@nl.linux.org Wed Jan 10 00:13:42 2001 Received: by humbolt.nl.linux.org id ; Wed, 10 Jan 2001 00:12:01 +0100 Received: from terra.geo.uu.nl ([131.211.29.16]:58805 "EHLO terra.geo.uu.nl") by humbolt.nl.linux.org with ESMTP id ; Wed, 10 Jan 2001 00:11:35 +0100 Received: from polaris.net (nexus.polaris.net [199.44.34.2]) by terra.geo.uu.nl (8.9.3/8.9.3/TvZ) with ESMTP id AAA25672 for ; Wed, 10 Jan 2001 00:11:33 +0100 (MET) Received: from localhost by polaris.net (8.9.2/8.7.6) with SMTP id SAA29898 for ; Tue, 9 Jan 2001 18:11:30 -0500 (EST) Date: Tue, 9 Jan 2001 18:11:29 -0500 (EST) From: "E. Ratliff" To: kernel-audit@nl.linux.org Subject: Re: LKAP belongs to you... In-Reply-To: <01010916054801.00952@sQa> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-kernel-audit@nl.linux.org Precedence: bulk Return-Path: X-Orcpt: rfc822;kernel-audit-list Aaron outlines some pretty ambitious jobs in his manifesto. I think we need to discuss whether we want to adapt a source code browser to have the features he describes and whether that should be a part of this project or a separate associated project. I am willing to volunteer to set up the CVS tree on sourceforge to spur along some of the other things that Aaron mentioned and set up a tasks page, if you will give me access rights on sourceforge. My sourceforge userid is ratliff. I think that spending a little time kicking off this project (filling out the website and the sourceforge information) will help people see what tools they can apply to what files and how to document their findings. Right now the project is wide open and any effort will help, including suggestions on how to document results. Aaron wrote a great document on how to get this started. Now we just have to jump in and get it done. Unfortunately, I don't think that I will be able to attend the BOF in New York. -E E. Ratliff ratliff@polaris.net Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/ From owner-kernel-audit@nl.linux.org Wed Jan 10 03:19:48 2001 Received: by humbolt.nl.linux.org id ; Wed, 10 Jan 2001 03:18:27 +0100 Received: from [194.73.73.176] ([194.73.73.176]:51701 "EHLO protactinium") by humbolt.nl.linux.org with ESMTP id ; Wed, 10 Jan 2001 03:17:57 +0100 Received: from [213.1.67.148] (helo=tank.local) by protactinium with esmtp (Exim 3.03 #83) id 14GApm-0000X6-00; Wed, 10 Jan 2001 02:17:54 +0000 Received: from athlon.local (davej@athlon.local [172.16.0.6]) by tank.local (8.11.1/8.11.1/Debian 8.11.0-6) with ESMTP id f0A2HnX16296; Wed, 10 Jan 2001 02:17:50 GMT Date: Wed, 10 Jan 2001 02:17:39 +0000 (GMT) From: X-X-Sender: To: Arnaldo Carvalho de Melo cc: "Burns, John" , "'George Capehart'" , "'kernel-audit@mail.nl.linux.org'" Subject: Re: project status In-Reply-To: <20010109165442.E24523@conectiva.com.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-kernel-audit@nl.linux.org Precedence: bulk Return-Path: X-Orcpt: rfc822;kernel-audit-list On Tue, 9 Jan 2001, Arnaldo Carvalho de Melo wrote: > look at http://bazar.conectiva.com.br/~acme/TODO plenty of things to fix How about creating a common TODO someplace (sourceforge?) and putting it into CVS ? I know a few people have them (including myself), and a lot of them contain things that could be good for a newcomer to kernel-hacking to cut their teeth on. The reason for putting it in CVS would be merging of multiple peoples TODO's, whilst allowing a lot more people to see them. I foresee this could work out something like.. 1. Someone checks out the TODO from CVS. 2. Picks something, mentions to the list "I'm about to tackle item 38" (In case someone else already is working on it, in which case pointing them to the relevant person may be advisable. A project admin with CVS write access maybe marks it in the TODO file ?). 3. After hacking fixups, the patch is sent here. 4. If the patch looks ok, its recommended to be sent to l-k/Linus/Alan. Sound sensible ? regards, Davej. -- | Dave Jones. http://www.suse.de/~davej | SuSE Labs Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/ From owner-kernel-audit@nl.linux.org Wed Jan 10 06:39:16 2001 Received: by humbolt.nl.linux.org id ; Wed, 10 Jan 2001 06:37:57 +0100 Received: from [216.161.55.93] ([216.161.55.93]:28910 "EHLO blue.int.wirex.com") by humbolt.nl.linux.org with ESMTP id ; Wed, 10 Jan 2001 06:37:22 +0100 Received: (from greg@localhost) by blue.int.wirex.com (8.9.3/8.9.3) id VAA24368; Tue, 9 Jan 2001 21:39:35 -0800 Date: Tue, 9 Jan 2001 21:39:35 -0800 From: Greg KH To: davej@suse.de Cc: Arnaldo Carvalho de Melo , "Burns, John" , "'George Capehart'" , "'kernel-audit@mail.nl.linux.org'" Subject: Re: project status Message-ID: <20010109213935.A24213@wirex.com> References: <20010109165442.E24523@conectiva.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from davej@suse.de on Wed, Jan 10, 2001 at 02:17:39AM +0000 X-Operating-System: Linux 2.4.0 (i686) Sender: owner-kernel-audit@nl.linux.org Precedence: bulk Return-Path: X-Orcpt: rfc822;kernel-audit-list On Wed, Jan 10, 2001 at 02:17:39AM +0000, davej@suse.de wrote: > I foresee this could work out something like.. > > 1. Someone checks out the TODO from CVS. > 2. Picks something, mentions to the list "I'm about to tackle item 38" > (In case someone else already is working on it, in which case pointing > them to the relevant person may be advisable. > A project admin with CVS write access maybe marks it in the TODO > file ?). > 3. After hacking fixups, the patch is sent here. And to the code's maintainer. Please remember them :) > 4. If the patch looks ok, its recommended to be sent to l-k/Linus/Alan. This should probably say: 4. If the maintainer agrees, then _they_ forward it on up the proper chain of command. There is usually someone else in charge of the larger subsystem, that then will forward it to Linus in the end. Let's not do an end run around the current kernel submission process. thanks, greg k-h -- greg@(kroah|wirex).com http://immunix.org/~greg Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/ From owner-kernel-audit@nl.linux.org Wed Jan 10 07:30:36 2001 Received: by humbolt.nl.linux.org id ; Wed, 10 Jan 2001 07:29:08 +0100 Received: from [206.15.28.226] ([206.15.28.226]:46832 "EHLO obi.sb.xuma.com") by humbolt.nl.linux.org with ESMTP id ; Wed, 10 Jan 2001 07:28:23 +0100 Received: (from yoda@localhost) by obi.sb.xuma.com (8.9.3/8.9.3) id WAA25824; Tue, 9 Jan 2001 22:36:38 -0800 X-Authentication-Warning: obi.sb.xuma.com: yoda set sender to yoda@xuma.com using -f Date: Tue, 9 Jan 2001 22:36:38 -0800 From: Jesse Nelson To: Greg KH Cc: davej@suse.de, Arnaldo Carvalho de Melo , "Burns, John" , "'George Capehart'" , "'kernel-audit@mail.nl.linux.org'" Subject: Re: project status Message-ID: <20010109223638.A25756@obi.sf.xuma.com> References: <20010109165442.E24523@conectiva.com.br> <20010109213935.A24213@wirex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.9i In-Reply-To: <20010109213935.A24213@wirex.com>; from greg@wirex.com on Tue, Jan 09, 2001 at 09:39:35PM -0800 Sender: owner-kernel-audit@nl.linux.org Precedence: bulk Return-Path: X-Orcpt: rfc822;kernel-audit-list I can go ahead an start a source forge pjoject for the list and goals. I have webspace, and a bit of time to maintain the web-side of the effort. I think somthing kinda like bugzilla would be a better solution to the todo list Idea. Maybee I will lookinto this tonight and maybe put somthing up on my domain. anyone have objections with this ?.. Previously, Greg KH wrote: > On Wed, Jan 10, 2001 at 02:17:39AM +0000, davej@suse.de wrote: > > I foresee this could work out something like.. > > > > 1. Someone checks out the TODO from CVS. > > 2. Picks something, mentions to the list "I'm about to tackle item 38" > > (In case someone else already is working on it, in which case pointing > > them to the relevant person may be advisable. > > A project admin with CVS write access maybe marks it in the TODO > > file ?). > > 3. After hacking fixups, the patch is sent here. > > And to the code's maintainer. Please remember them :) > > > 4. If the patch looks ok, its recommended to be sent to l-k/Linus/Alan. > > This should probably say: > > 4. If the maintainer agrees, then _they_ forward it on up the proper > chain of command. > > There is usually someone else in charge of the larger > subsystem, that then will forward it to Linus in the end. Let's not do > an end run around the current kernel submission process. > > thanks, > > greg k-h > > -- > greg@(kroah|wirex).com > http://immunix.org/~greg > > Kernel-audit: discussion list for security and the linux kernel > Archive: http://mail.nl.linux.org/kernel-audit/ -- Jesse Nelson X U M A X .~. Senior 160 Pine Street, 2nd Floor U /V\ Engineer San Francisco, CA 94111 M // \\ tel: 415.777.9988 I /( )\ http://www.xuma.com X ^`~'^ PGP Key fingerprint = 9DE9 4C9F 014D F68E 893D 097E 079D 5FF3 9614 3E86 Absence makes the heart grow fonder -- of somebody else. Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/ From owner-kernel-audit@nl.linux.org Wed Jan 10 20:36:26 2001 Received: by humbolt.nl.linux.org id ; Wed, 10 Jan 2001 20:35:07 +0100 Received: from [194.73.73.138] ([194.73.73.138]:22771 "EHLO ruthenium") by humbolt.nl.linux.org with ESMTP id ; Wed, 10 Jan 2001 20:34:37 +0100 Received: from [62.7.46.39] (helo=tank.local) by ruthenium with esmtp (Exim 3.03 #83) id 14GR0w-0000cp-00; Wed, 10 Jan 2001 19:34:31 +0000 Received: from athlon.local (davej@athlon.local [172.16.0.6]) by tank.local (8.11.1/8.11.1/Debian 8.11.0-6) with ESMTP id f0AJYJX20469; Wed, 10 Jan 2001 19:34:23 GMT Date: Wed, 10 Jan 2001 19:34:06 +0000 (GMT) From: X-X-Sender: To: Greg KH cc: Arnaldo Carvalho de Melo , "Burns, John" , "'George Capehart'" , "'kernel-audit@mail.nl.linux.org'" Subject: Re: project status In-Reply-To: <20010109213935.A24213@wirex.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-kernel-audit@nl.linux.org Precedence: bulk Return-Path: X-Orcpt: rfc822;kernel-audit-list On Tue, 9 Jan 2001, Greg KH wrote: > > 1. Someone checks out the TODO from CVS. > > 2. Picks something, mentions to the list "I'm about to tackle item 38" > > (In case someone else already is working on it, in which case pointing > > them to the relevant person may be advisable. > > A project admin with CVS write access maybe marks it in the TODO > > file ?). > > 3. After hacking fixups, the patch is sent here. > > And to the code's maintainer. Please remember them :) *nod*, of course. An oversight on my part. > > 4. If the patch looks ok, its recommended to be sent to l-k/Linus/Alan. > This should probably say: > > 4. If the maintainer agrees, then _they_ forward it on up the proper > chain of command. > > There is usually someone else in charge of the larger > subsystem, that then will forward it to Linus in the end. Let's not do > an end run around the current kernel submission process. Agreed. It may even be worth letting the maintainer know that item x is being worked on by someone. It would be a pain if a. The maintainer already had the fix in their private tree. b. That item was due to become irrelevant due to code rewrite c. Someone else already sent the maintainer that fix, but no-one else knew about it d. The maintainer knows a better way to fix the problem than the proposed fix, but hadn't yet implemented it. So yes, keeping the maintainer up to date with what's going on is also an essential item. regards, Davej. -- | Dave Jones. http://www.suse.de/~davej | SuSE Labs Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/ From owner-kernel-audit@nl.linux.org Wed Jan 10 21:30:37 2001 Received: by humbolt.nl.linux.org id ; Wed, 10 Jan 2001 21:29:13 +0100 Received: from smtp07.phx.gblx.net ([206.165.6.137]:45244 "EHLO smtp07.phx.gblx.net") by humbolt.nl.linux.org with ESMTP id ; Wed, 10 Jan 2001 21:28:39 +0100 Received: (from daemon@localhost) by smtp07.phx.gblx.net (8.9.3/8.9.3) id NAA248106; Wed, 10 Jan 2001 13:27:56 -0700 Received: from 64-211-79-22.dsl1.BRV.gblx.net(64.211.79.22), claiming to be "plato" via SMTP by smtp07.phx.gblx.net, id smtpdk.awya; Wed Jan 10 13:27:43 2001 Received: by localhost with Microsoft MAPI; Wed, 10 Jan 2001 14:26:43 -0600 Message-ID: <01C07B11.5AC711B0.dwagle@frontiernet.net> From: David Wagle Reply-To: "dwagle@frontiernet.net" To: "'davej@suse.de'" , Greg KH Cc: Arnaldo Carvalho de Melo , "Burns, John" , "'George Capehart'" , "'kernel-audit@mail.nl.linux.org'" Subject: RE: project status Date: Wed, 10 Jan 2001 14:26:42 -0600 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 Sender: owner-kernel-audit@nl.linux.org Precedence: bulk Return-Path: X-Orcpt: rfc822;kernel-audit-list I've asked about a dozen times to be removed from this list. I have followed the available instructions. EVery so often I get put back on it for some damn reason. PLEASE GET ME THE FUCK OFF THIS THING NOW AND DON"T PUT ME BACK ON< EVER! Thank you very much. -----Original Message----- From: davej@suse.de [SMTP:davej@suse.de] Sent: Wednesday, January 10, 2001 1:34 PM To: Greg KH Cc: Arnaldo Carvalho de Melo; Burns, John; 'George Capehart'; 'kernel-audit@mail.nl.linux.org' Subject: Re: project status On Tue, 9 Jan 2001, Greg KH wrote: > > 1. Someone checks out the TODO from CVS. > > 2. Picks something, mentions to the list "I'm about to tackle item 38" > > (In case someone else already is working on it, in which case pointing > > them to the relevant person may be advisable. > > A project admin with CVS write access maybe marks it in the TODO > > file ?). > > 3. After hacking fixups, the patch is sent here. > > And to the code's maintainer. Please remember them :) *nod*, of course. An oversight on my part. > > 4. If the patch looks ok, its recommended to be sent to l-k/Linus/Alan. > This should probably say: > > 4. If the maintainer agrees, then _they_ forward it on up the proper > chain of command. > > There is usually someone else in charge of the larger > subsystem, that then will forward it to Linus in the end. Let's not do > an end run around the current kernel submission process. Agreed. It may even be worth letting the maintainer know that item x is being worked on by someone. It would be a pain if a. The maintainer already had the fix in their private tree. b. That item was due to become irrelevant due to code rewrite c. Someone else already sent the maintainer that fix, but no-one else knew about it d. The maintainer knows a better way to fix the problem than the proposed fix, but hadn't yet implemented it. So yes, keeping the maintainer up to date with what's going on is also an essential item. regards, Davej. -- | Dave Jones. http://www.suse.de/~davej | SuSE Labs Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/ Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/ From owner-kernel-audit@nl.linux.org Wed Jan 10 21:58:08 2001 Received: by humbolt.nl.linux.org id ; Wed, 10 Jan 2001 21:56:59 +0100 Received: from mail.securityportal.com ([64.85.88.246]:43534 "EHLO securityportal.com") by humbolt.nl.linux.org with ESMTP id ; Wed, 10 Jan 2001 21:56:27 +0100 Received: from [127.0.0.1] (HELO sQa) by securityportal.com (CommuniGate Pro SMTP 3.3.2) with SMTP id 229226 for kernel-audit@nl.linux.org; Wed, 10 Jan 2001 12:56:25 -0800 From: Bryan Paxton Reply-To: bpaxton@securityportal.com To: kernel-audit@nl.linux.org Subject: Re: project status Date: Wed, 10 Jan 2001 14:49:42 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" References: In-Reply-To: MIME-Version: 1.0 Message-Id: <01011014494200.01133@sQa> Content-Transfer-Encoding: 8bit Sender: owner-kernel-audit@nl.linux.org Precedence: bulk Return-Path: X-Orcpt: rfc822;kernel-audit-list > > > I've asked about a dozen times to be removed from this list. I have > followed the available instructions. EVery so often I get put back on it > for some damn reason. > There is no need to carry out _your_ problem (which has nothing to do with the kernel) out with the rest of the public... Also I highly doubt majordomo decided to put you back on the list without confirmation from you, this also known as lUser error. I am now removing you from this list. Please do not subscribe to this list again. On a related note: I do not approve requests for unsubscription to this list from an email address which is not already subscribed to this list. In other words, use the email address you subscribed with to unsubscribe. Approval for others will always be rejected by me. Thanks Bryan Paxton Kernel-audit: discussion list for security and the linux kernel Archive: http://mail.nl.linux.org/kernel-audit/