All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Alexander Viro <viro@math.psu.edu>
Cc: Erik Andersen <andersen@codepoet.org>, linux-kernel@vger.kernel.org
Subject: Re: klibc and logging
Date: 13 Aug 2002 08:27:12 -0600	[thread overview]
Message-ID: <m18z3arfzz.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.GSO.4.21.0208130626481.1689-100000@weyl.math.psu.edu>

Alexander Viro <viro@math.psu.edu> writes:

> On Tue, 13 Aug 2002, Erik Andersen wrote:
> 
> > I would love to see an example of how to do an NFS mount w/o
> > resorting to the C library at all.  Plainly, having generic RPC
> > code in the C library sucks, even if you trim it down.  Having
> > the entire NFS mount process live in application space, and not
> > in the C library, is clearly a win....
> 
> See below - it's crud, but it works.  Based of fs/nfs/nfsroot.c, moved
> to userland with RPC done via syscalls and nothing else.  Arguments are
> passed via environment variables, replacing that with use of argv is
> trivial...   Other than syscalls uses: alarm(3), getenv(3), str... and
> mem..., {s,}printf(3), htonl(3) and htons(3).  About 4Kb of .text + .data
> and aforementioned functions shouldn't add much to that.
> 
> Hardly usable as generic-purpose mount_nfs(8), but for nfsroot...  I'd
> prefer to have timeouts handled properly and code - cleaned up, but
> other than that it should be usable.

It might be worth looking at etherboot (www.etherboot.org).  It isn't
exactly userspace but it also has a minimal nfs client that can mount
an nfs filesystem and read a file, and timeouts are handled.  If
nothing else it should generate some ideas.

Eric

  reply	other threads:[~2002-08-13 14:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-13  7:12 klibc and logging H. Peter Anvin
2002-08-13  7:52 ` Erik Andersen
2002-08-13  8:04   ` Alexander Viro
2002-08-13 10:12     ` Erik Andersen
2002-08-13 10:38       ` Alexander Viro
2002-08-13 14:27         ` Eric W. Biederman [this message]
2002-08-13 18:05         ` H. Peter Anvin
2002-08-13  9:42 ` Miquel van Smoorenburg
2002-08-13 17:41   ` H. Peter Anvin
2002-08-13 17:54     ` Benjamin LaHaise
2002-08-13 17:59       ` H. Peter Anvin
2002-08-13 17:55     ` Randy.Dunlap
2002-08-16  5:05     ` Oliver Xymoron
2002-08-19 13:27 ` Russell King
2002-08-19 13:59   ` H. Peter Anvin
2002-08-19 16:54     ` Russell King
2002-08-19 16:58       ` H. Peter Anvin
2002-08-19 17:25         ` Russell King
2002-08-19 17:27           ` H. Peter Anvin
2002-08-19 17:29           ` H. Peter Anvin
2002-08-19 19:37             ` Alan Cox
2002-08-19 19:40               ` H. Peter Anvin
2002-08-20 13:22       ` Thunder from the hill
2002-08-20 14:45         ` Russell King

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=m18z3arfzz.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=andersen@codepoet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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.