Received: by oss.sgi.com id ; Mon, 17 Jul 2000 21:56:15 -0700 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:64827 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Mon, 17 Jul 2000 21:55:51 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id WAA04459 for ; Mon, 17 Jul 2000 22:01:06 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id OAA04163; Tue, 18 Jul 2000 14:54:11 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) id OAA03270; Tue, 18 Jul 2000 14:54:08 +1000 (EST) From: "Nathan Scott" Message-Id: <10007181454.ZM3411@wobbly.melbourne.sgi.com> Date: Tue, 18 Jul 2000 14:54:07 -0500 In-Reply-To: Daniel Moore "Re: Who do I talk to contribute?" (Jul 18, 1:23pm) References: <200007180318.NAA02682@clouds.melbourne.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Daniel Moore , William L Jones Subject: Re: Who do I talk to contribute? Cc: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-xfs-outgoing hi, On Jul 18, 1:23pm, Daniel Moore wrote: > Subject: Re: Who do I talk to contribute? > > William L Jones writes: > > => I would like to contribute to the effort. I could work on the fsr port. > => Which means I probaly should do the "Finish the implementing the syssgi() > => command" work item first if it is not alrady taken. > > Just as an aside: > > Most of the XFS specific syssgi calls are already available through ioctls, > and the remaining growfs specific calls are in-progress in our group. > There are XFS syssgi's which have not been ported as yet, e.g. the SGI_FS_SWAPEXT syssgi call which fsr_xfs uses. We (the Aussies) haven't started looking into this yet. The folk in Eagan will be best to get things rolling on this one since (I think?) they wrote that code originally & know it best (is that right?). It would be a relatively simple exercise for me to get the fsr code compiling initially and checked in with the other user tools (which I don't mind doing if noone else jumps on it). However, I don't know the code at all, so I wouldn't be the best person to handle merging of patches back into the tree & I'm unsure how much of the kernel side of things is in place in the current Linux code... (?) cheers. -- Nathan