From: Herbert Poetzl <herbert@13thfloor.at>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Debian GNU/Linux m68k <debian-68k@lists.debian.org>,
uClinux list <uclinux-dev@uclinux.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: `new' syscalls for m68k
Date: Mon, 13 Sep 2004 15:08:44 +0200 [thread overview]
Message-ID: <20040913130844.GB1774@MAIL.13thfloor.at> (raw)
In-Reply-To: <Pine.GSO.4.58.0409131316430.21429@waterleaf.sonytel.be>
On Mon, Sep 13, 2004 at 01:17:10PM +0200, Geert Uytterhoeven wrote:
> On Sun, 12 Sep 2004, Herbert Poetzl wrote:
> > On Fri, Sep 10, 2004 at 10:48:16PM +0100, Alan Cox wrote:
> > > On Gwe, 2004-09-10 at 21:57, Geert Uytterhoeven wrote:
> > > > - What about sys_vserver()?
> >
> > I would be happy to add a syscall reservation
> > to the list of already reserved syscalls for
> > i386, x86_64, s390, sparc/64, sh3/4, ppc/64
> > and mips * ...
>
> Also for m68k?
of course, linux-vserver is except for 2-3 tiny
arch specific modifications which might go away
sooner or later (ptrace and uname) completely
arch agnostic, so there should be no problem
using it on m68k ...
TIA,
Herbert
> Gr{oetje,eeting}s,
>
> Geert
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
next prev parent reply other threads:[~2004-09-13 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 20:57 Geert Uytterhoeven
2004-09-10 21:48 ` Alan Cox
2004-09-12 21:22 ` Herbert Poetzl
2004-09-13 11:17 ` Geert Uytterhoeven
2004-09-13 13:08 ` Herbert Poetzl [this message]
2004-09-12 0:35 ` Rik van Riel
2004-09-16 8:23 ` Geert Uytterhoeven
2004-09-16 14:52 ` Herbert Poetzl
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=20040913130844.GB1774@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=debian-68k@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=uclinux-dev@uclinux.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
all inboxes | Powered by JetHome®