public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: rct@gherkin.frus.com (Bob_Tracy)
To: linux-kernel@vger.kernel.org
Cc: braam@clusterfs.com
Subject: 2.5.X: intermezzo compile errors
Date: Tue, 21 May 2002 09:41:57 -0500 (CDT)	[thread overview]
Message-ID: <m17AApp-0005khC@gherkin.frus.com> (raw)

Are people actually using the intermezzo fs with recent 2.5.X kernels?
The compile has been broken for quite some time due to the following:

(1) linux/include/linux/intermezzo_psdev.h: ISLENTO() define references
    a "p_pptr" structure member that has been replaced by "parent".

(2) In the 2.5.5 timeframe, the "i_zombie" member of "struct inode"
    went away, and most of the filesystem code was modified accordingly.
    The intermezzo fs never got "the treatment" as far as I can tell.
    Affected source files are linux/fs/intermezzo/vfs.c and dir.c.

(3) linux/fs/intermezzo/super.c: no "read_super" structure member.

(4) linux/fs/intermezzo/psdev.c: syntax error (missing brace) causes
    numerous compilation errors.  After adding the missing brace,
    there's still a problem with the third arg of lento_mknod() at
    line 773.

If there's an intermezzo patch set somewhere, I'm sure someone will
point me to it :-).

-- 
-----------------------------------------------------------------------
Bob Tracy                   WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------

             reply	other threads:[~2002-05-21 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 14:41 Bob_Tracy [this message]
2002-05-21 18:44 ` 2.5.X: intermezzo compile errors Peter J. Braam
2002-05-21 19:00   ` Dave Jones

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=m17AApp-0005khC@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=braam@clusterfs.com \
    --cc=linux-kernel@vger.kernel.org \
    /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