From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] libc umount and umount2 can't both be right
Date: Wed, 14 May 2003 08:31:24 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705783@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705762@msgid-missing>
Ian Wienand <ianw@gelato.unsw.edu.au> writes:
|> [originally cc: libc-alpha but screwed up the cc line so it was rejected here]
|>
|> >On Tue, May 13, 2003 at 04:06:41PM -0400, MONTGOMERY,BOB (HP-FtCollins,ex1) wrote:
|> > In libc, umount and umount2 are the same code. They both use
|> > syscall number 1044 without introducing a call layer.
|>
|> looks like a typo in libc to me
|>
|> -i
|> ianw@gelato.unsw.edu.au
|> http://www.gelato.unsw.edu.au
|>
|> --- libc/sysdeps/unix/sysv/linux/ia64/syscalls.list.old 2003-05-14 09:10:04.000000000 +1000
|> +++ libc/sysdeps/unix/sysv/linux/ia64/syscalls.list 2003-05-14 09:09:40.000000000 +1000
|> @@ -1,6 +1,6 @@
|> # File name Caller Syscall name # args Strong name Weak names
|>
|> -umount2 - umount 2 __umount2 umount2
|> +umount2 - umount2 2 __umount2 umount2
Except there is no umount2 syscall on ia64.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-05-14 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 20:06 [Linux-ia64] libc umount and umount2 can't both be right MONTGOMERY,BOB (HP-FtCollins,ex1)
2003-05-13 23:24 ` Ian Wienand
2003-05-14 8:31 ` Andreas Schwab [this message]
2003-05-14 11:37 ` Ian Wienand
2003-05-14 14:43 ` Andreas Schwab
2003-05-14 15:47 ` MONTGOMERY,BOB (HP-FtCollins,ex1)
2003-05-15 0:26 ` Ulrich Drepper
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-105590723705783@msgid-missing \
--to=schwab@suse.de \
--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.