linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: Dan Yocum <yocum@fnal.gov>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	linux-kernel@vger.kernel.org
Subject: Re: XFS merged in 2.4
Date: Mon, 8 Dec 2003 12:48:20 -0500	[thread overview]
Message-ID: <20031208174820.GA18504@rdlg.net> (raw)
In-Reply-To: <3FD4AA4C.7080102@fnal.gov>

[-- Attachment #1: Type: text/plain, Size: 2432 bytes --]


Thus spake Dan Yocum (yocum@fnal.gov):

> Marcelo, Christoph, et al.,
> 
> Thanks for finally including XFS in the vanilla 2.4 tree.  We greatly 
> appreciate it.
> 
> I hear that the acls and dmapi bits were excluded, but our ~300TB are used 
> mainly for online data caching so we don't generally use these features.
> 
> Again, thanks for making my life somewhat easier.  :-)
> 
> Cheers,
> Dan
> 
> 
> Marcelo Tosatti wrote:
> >FYI
> >
> >Christoph reviewed XFS patch which changed generic code, and it was
> >stripped down later to a set of changes which dont modify the code
> >behaviour (except for a few bugfixes which should have been included
> >separately anyway) and are pretty obvious.
> >
> >So its that has been merged, along with fs/xfs/.
> >
> >
> >
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at  http://www.tux.org/lkml/
> >
> 


While I think this is a good idea in general:
make bzImage gives this:
make[4]: Leaving directory `/exp/src1/kernels/2.4.23/Desktop/linux-2.4.23/fs/vfat'
make -C xfs fastdep
make: *** xfs: No such file or directory.  Stop.
make: Entering an unknown directorymake: Leaving an unknown directorymake[3]: *** [_sfdep_xfs] Error 2
make[3]: Leaving directory `/exp/src1/kernels/2.4.23/Desktop/linux-2.4.23/fs'
make[2]: *** [fastdep] Error 2
make[2]: Leaving directory `/exp/src1/kernels/2.4.23/Desktop/linux-2.4.23/fs'
make[1]: *** [_sfdep_fs] Error 2
make[1]: Leaving directory `/exp/src1/kernels/2.4.23/Desktop/linux-2.4.23'
make: *** [dep-files] Error 2

The main problem?

root:/usr/src/kernels/2.4.23/Desktop/linux-2.4.23# grep -i xfs .config   
# CONFIG_XFS_FS is not set
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_RT is not set
# CONFIG_XFS_TRACE is not set
# CONFIG_XFS_DEBUG is not set




:wq!
---------------------------------------------------------------------------
Robert L. Harris                     | GPG Key ID: E344DA3B
                                         @ x-hkp://pgp.mit.edu
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.

Life is not a destination, it's a journey.
  Microsoft produces 15 car pileups on the highway.
    Don't stop traffic to stand and gawk at the tragedy.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-12-08 17:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 11:22 XFS merged in 2.4 Marcelo Tosatti
2003-12-08 12:48 ` Michael D. Harnois
2003-12-08 12:58   ` Marcelo Tosatti
2003-12-08 16:43 ` Dan Yocum
2003-12-08 17:48   ` Robert L. Harris [this message]
2003-12-09  5:04     ` Keith Owens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031208174820.GA18504@rdlg.net \
    --to=robert.l.harris@rdlg.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=yocum@fnal.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).