From: Pat LaVarre Subject: Re: diff "lk 2.4 udf.ko" "lk 2.6 udf.ko" Date: 02 Dec 2003 14:01:15 -0700 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1070398874.3699.1.camel@patibmrh9> References: <1070323536.8454.8.camel@patibmrh9> <1070394858.4338.12.camel@patibmrh9> <1070397983.7531.4.camel@patibmrh9> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from email-out2.iomega.com ([147.178.1.83]:31459 "EHLO email.iomega.com") by vger.kernel.org with ESMTP id S264396AbTLBVBt (ORCPT ); Tue, 2 Dec 2003 16:01:49 -0500 Received: from royntex01.iomegacorp.com (unknown [147.178.90.120]) by email.iomega.com (Postfix) with ESMTP id A77811C79 for ; Tue, 2 Dec 2003 14:01:47 -0700 (MST) To: linux-fsdevel@vger.kernel.org In-Reply-To: <1070397983.7531.4.camel@patibmrh9> List-Id: linux-fsdevel.vger.kernel.org > I see linux-2.5.37 arrives from kernel.org ready to try writing udf: > > $ make defconfig > ... > $ grep UDF .config > CONFIG_UDF_FS=m > CONFIG_UDF_RW=y > $ Ouch, sorry, this result I cannot easily repeat. Possibly `make defconfig` and/or `make xconfig` is producing inconsistent .config, depending on in which config those commands are entered. Pat LaVarre