From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [question] implentation of smb-browsing: kernel space or user space?
Date: 19 Jan 2002 13:58:31 -0800 [thread overview]
Message-ID: <a2cq67$2dq$1@cesium.transmeta.com> (raw)
In-Reply-To: <E16RtOX-0007Ao-00@mrvdom00.kundenserver.de>
Followup to: <E16RtOX-0007Ao-00@mrvdom00.kundenserver.de>
By author: Christian =?iso-8859-1?q?Borntr=E4ger?=
<linux-kernel@borntraeger.net>
In newsgroup: linux.dev.kernel
>
> My question is: Do you think, that this kind of filesystem is sensible, or do
> you think that smb-stuff has to be in user space. (for example using the
> filesystem in userspace approach, shown some weeks ago)?
>
It REALLY should be in user space. Putting this kind of crap in the
kernel is insane. Note also that *browsing* (network 'hood) is
different from *mounting* -- even on Windows it is very common that
there are computers you can't see in your browse windows that you can
access by name.
Consider DNS -- it *used* to be possible to enumerate DNS (these days,
most servers will deny access to you if you try), but it has been a
long, long time since it was ever practical. However, you can do
blind resolution quite trivially.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
prev parent reply other threads:[~2002-01-19 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-19 11:08 [question] implentation of smb-browsing: kernel space or user space? Christian Bornträger
2002-01-19 11:30 ` Oliver Neukum
2002-01-19 12:39 ` Urban Widmark
2002-01-19 22:01 ` H. Peter Anvin
2002-01-26 10:53 ` Mark H. Wood
2002-01-19 21:58 ` H. Peter Anvin [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='a2cq67$2dq$1@cesium.transmeta.com' \
--to=hpa@zytor.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