public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: brian@worldcontrol.com, linux-kernel@vger.kernel.org
Subject: Re: more on 2.4.19pre... & swsusp
Date: 06 Apr 2002 20:33:27 -0500	[thread overview]
Message-ID: <1018143212.8480.99.camel@psuedomode> (raw)
In-Reply-To: <E16tz9Q-0002sH-00@the-village.bc.nu>

On Sat, 2002-04-06 at 17:59, Alan Cox wrote:
> > On a different note.  Why doesn't the ac branch have ftpfs yet?  Besides
> > the fact that it sometimes has problems with ls'ing a directory because
> 
> Because its perfectly doable in user space. Its for testing useful stuff not
> a dumping ground
> -



Wouldn't that be true of any networked filesystem?  They should all be
able to be done in userspace.  The problem with that would be it loses
it's transparency to the user and increases latency.  Sure ftpfs can be
done in userspace, but the point of it is so i dont have to interface
with ftp's through a specific client.  I'm sure people would love it if
they had to open samba-view whenever they wanted to copy to and from
samba shares, same for nfs etc.  

There are more than a couple examples of things in the kernel that can
also be completely functional just done in userspace,  Both autofs (why
we continue to ship an older version when the newer one is reverse
compat is a mystery to me) implementations are two such examples.  

I have nothing against not including something for personal preferences
( it is your branch) or because something is too untested.. but because
it can be done in userspace just doesn't hold up when you look at some
of the things in the kernel already.   But i've wasted enough time
arguing about something that doesn't require any changes. heh 


  reply	other threads:[~2002-04-07  1:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-06 20:09 more on 2.4.19pre... & swsusp brian
2002-04-06 21:18 ` Ed Sweetman
2002-04-06 22:59   ` Alan Cox
2002-04-07  1:33     ` Ed Sweetman [this message]
2002-04-07 16:22       ` Pavel Machek
2002-04-07 16:21   ` Pavel Machek

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=1018143212.8480.99.camel@psuedomode \
    --to=ed.sweetman@wmich.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=brian@worldcontrol.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox