Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: ralf@gnu.org
Cc: linux-mips@linux-mips.org
Subject: Re: linux-vserver syscall ...
Date: Mon, 24 May 2004 21:05:08 +0200	[thread overview]
Message-ID: <20040524190508.GC27481@MAIL.13thfloor.at> (raw)
In-Reply-To: <20040524182915.GA27481@MAIL.13thfloor.at>

On Mon, May 24, 2004 at 08:29:15PM +0200, Herbert Poetzl wrote:
> 
> Hi Ralf!
> 
> obviously I forgot to ask you to reserve a
> syscall for linux-vserver, and I just discovered
> this as the currently used number (273) was used
> up by some other syscall (in 2.6.7-rc1) ...
> 
> so I'm asking you now, could you please reserve
> a syscall for this project, so that we do not
> need to change it on every new kernel release?
> 
> here is a list of currently reserved syscalls
> (for other archs) and some links to the project
> (in case you care)

hmm, "a brain, I need a brain for my master" ...

okay here are the promised links:

  http://www.linux-vserver.org/
  http://vserver.13thfloor.at/Stuff/PAPER-05.4.txt

best,
Herbert

>    arch     number maintainer               
> --------------------------------------------
>    x86_64   236    [Andi Kleen]             
>    s390     263    [Martin Schwidefsky]     
>    sparc/64 267    [David S.Miller]         
>    i386     273    [Rik/Linus/Andrew]       
>    sh3/sh4  273    [Kazumoto Kojima]        
>    ppc/64   257    [Benjamin Herrenschmidt] 
> 
> thanks in advance,
> Herbert
> 

  reply	other threads:[~2004-05-24 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24 18:29 linux-vserver syscall Herbert Poetzl
2004-05-24 19:05 ` Herbert Poetzl [this message]
2004-06-08 23:54 ` Ralf Baechle
2004-06-09 14:44   ` 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=20040524190508.GC27481@MAIL.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@gnu.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