Received: (from majordomo@localhost) by oss.sgi.com (8.11.3/8.11.3) id f43JefZ14901 for linux-xfs-outgoing; Thu, 3 May 2001 12:40:41 -0700 Received: from UberGeek.coremetrics.com ([209.184.141.163]) by oss.sgi.com (8.11.3/8.11.3) with ESMTP id f43JeeF14898 for ; Thu, 3 May 2001 12:40:41 -0700 Received: from localhost (austin@localhost) by UberGeek.coremetrics.com (8.11.2/8.11.2) with ESMTP id f43JbW529015; Thu, 3 May 2001 14:37:32 -0500 X-Authentication-Warning: UberGeek.coremetrics.com: austin owned process doing -bs Date: Thu, 3 May 2001 14:37:32 -0500 (CDT) From: Austin Gonyou To: Jan-Frode Myklebust cc: Subject: Re: devfsd-1.3.11-1 In-Reply-To: <20010503205516.A633@ii.uib.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I should've been more specific. I was under the assumption that you couldn't really use devfsd if devfs was not compiled into the kernel. Sorry for the confusion. What I really want to do is patch a 2.4.4 kernel to use XFS without using devfs. That part I don't think would be an issue, and I understand all that's involved here. One thing I'd like to be able to do though is to know how to properly patch a 2.4.4 kernel upto xfs. Should I get a 2.4.2 kernel, patch it with xfs, then patch it up to 2.4.4? Ideas? -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com