linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>, Anthony Brock <Anthony_Brock@ous.edu>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] uml_mconsole issue
Date: Sun, 18 Jul 2004 21:34:30 +0200	[thread overview]
Message-ID: <200407182134.30301.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200407122036.i6CKa3Ys001604@ccure.user-mode-linux.org>

Alle 22:36, lunedì 12 luglio 2004, Jeff Dike ha scritto:
> Anthony_Brock@ous.edu said:
> > (gdb) bt
> > #0  0xa00730df in link_path_walk (name=0xa0a59ca9 "uptime",
> > nd=0xa3fd3aa4) at fs/namei.c:591
>
> This is known, and I haven't got around to fixing it yet.
What about calling directly the inline version of read() from asm/unistd.h 
(something like kernel/kmod.c calling execve())? I also think that someone 
would kill you for such code duplication. Or not?
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id\x10040&opÌk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2004-07-18 19:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-07  5:14 [uml-devel] uml_mconsole issue Anthony Brock
2004-07-07  5:35 ` Anthony Brock
2004-07-07 17:14 ` BlaisorBlade
2004-07-07 20:36   ` Anthony Brock
2004-07-07 20:43   ` Anthony Brock
2004-07-12 20:36     ` Jeff Dike
2004-07-18 19:34       ` BlaisorBlade [this message]

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=200407182134.30301.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=Anthony_Brock@ous.edu \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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