All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] __ia64_syscall ?
Date: Mon, 23 Jul 2001 12:22:24 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005863@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005861@msgid-missing>

Hi Jes,

> __ia64_syscall is obsolete. The reiserfs-tools package should use the
> syscall() interface instead. What they doing is also wrong on the ia32
> though it happens to work.

Thanks for the quick response.

> That said please be aware that I do not think reiserfs has been ported
> to 64 bit architectures yet. That and the number of severe problem
> reports that keeps coming in about it, I'd strongly recommend you stay
> far away from it and try a better file system.

ReiserFS works on SuSE/IA64. Andreas Schwab told me so (I wouldn't believe
it either), I tried it here (not extensively, though) and so far I have
had no problems. It appears that ReiserFS "simply" needs a few additional patches
the SuSE kernels include.

I am currently trying to find out what these patches are.

> If you want a journaled
> file system, I recommend you take a look at XFS or EXT3. I know that
> Martin Petersen got XFS going on the Alpha so it should work fine on
> the ia64 as well.

It seems that SGI is now providing XFS patches against recent kernels.
Might be worth a try now ... so far I've refused to use their CVS kernel
tree.

Thanks again,
Martin

-- 
Martin Wilck     <Martin.Wilck@fujitsu-siemens.com>
FSC EP PS DS1, Paderborn      Tel. +49 5251 8 15113





  parent reply	other threads:[~2001-07-23 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-23 11:44 [Linux-ia64] __ia64_syscall ? Martin Wilck
2001-07-23 12:02 ` Jes Sorensen
2001-07-23 12:21 ` Andreas Schwab
2001-07-23 12:22 ` Martin Wilck [this message]
2001-07-23 12:43 ` Jes Sorensen
2001-07-23 12:45 ` Jes Sorensen
2001-07-23 14:17 ` 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=marc-linux-ia64-105590693005863@msgid-missing \
    --to=martin.wilck@fujitsu-siemens.com \
    --cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.