* In-kernel Gopher server
@ 2003-10-23 9:30 John Bradford
2003-10-23 14:27 ` Zwane Mwaikambo
0 siblings, 1 reply; 5+ messages in thread
From: John Bradford @ 2003-10-23 9:30 UTC (permalink / raw)
To: linux-kernel
Apparently my suggestion of a couple of weeks ago, for an in-kernel
gopher server to aid remote administration and configuration, wasn't
clear enough.
Having just read:
http://lwn.net/Articles/53019/
I get the impression that I was understood to be suggesting we
implement a generic in-kenrel gopher server, much like the kernel
webserver that was removed.
The point is that if you look after systems that are on-line 24-hours
a day, being able to have a look at data in /proc, or the .config of
the current kernel from a portable device would be quite useful, if
you suddenly start getting calls saying something like a webserver
isn\'t responding.
Implementing a web-based interface to such data is all very well until
you want to access it on a device the size of a wristwatch.
John.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: In-kernel Gopher server
2003-10-23 9:30 In-kernel Gopher server John Bradford
@ 2003-10-23 14:27 ` Zwane Mwaikambo
2003-10-23 15:01 ` John Bradford
0 siblings, 1 reply; 5+ messages in thread
From: Zwane Mwaikambo @ 2003-10-23 14:27 UTC (permalink / raw)
To: John Bradford; +Cc: linux-kernel
On Thu, 23 Oct 2003, John Bradford wrote:
> Implementing a web-based interface to such data is all very well until
> you want to access it on a device the size of a wristwatch.
Wristwatch /proc frobnicating aside, I think your clients are paying for
support, perhaps getting yourself to a desk and normal computer might be
in their best interests. And anyway if you must, what's wrong with a
normal pda, ssh and cat(1)?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: In-kernel Gopher server
2003-10-23 14:27 ` Zwane Mwaikambo
@ 2003-10-23 15:01 ` John Bradford
2003-10-23 15:12 ` Zwane Mwaikambo
0 siblings, 1 reply; 5+ messages in thread
From: John Bradford @ 2003-10-23 15:01 UTC (permalink / raw)
To: Zwane Mwaikambo; +Cc: linux-kernel
Quote from Zwane Mwaikambo <zwane@arm.linux.org.uk>:
> On Thu, 23 Oct 2003, John Bradford wrote:
>
> > Implementing a web-based interface to such data is all very well until
> > you want to access it on a device the size of a wristwatch.
>
> Wristwatch /proc frobnicating aside, I think your clients are paying for
> support, perhaps getting yourself to a desk and normal computer might be
> in their best interests.
Obviously I'm not suggesting it as a normal method of support, it's
just another option. There might be times when a desk and a normal
computer are more than five minutes away, and having something to
think about on the way there is useful.
> And anyway if you must, what's wrong with a
> normal pda, ssh and cat(1)?
Nothing, but if we were going to export configuration data at all, it
might as well be done using something more light weight than HTTP and
HTML.
Maybe the wristwatch example was a bit extreme, but what about a
system with very low bandwidth for connectivity? What if you were
trying to get configuration data back from a spacecraft millions of
miles away? At 300 BPS or less, and hours of latency, Gopher starts
to look a bit more realistic than getting a shell prompt via ssh :-).
John.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: In-kernel Gopher server
2003-10-23 15:01 ` John Bradford
@ 2003-10-23 15:12 ` Zwane Mwaikambo
2003-10-23 15:22 ` John Bradford
0 siblings, 1 reply; 5+ messages in thread
From: Zwane Mwaikambo @ 2003-10-23 15:12 UTC (permalink / raw)
To: John Bradford; +Cc: linux-kernel
On Thu, 23 Oct 2003, John Bradford wrote:
> Maybe the wristwatch example was a bit extreme, but what about a
> system with very low bandwidth for connectivity? What if you were
> trying to get configuration data back from a spacecraft millions of
> miles away? At 300 BPS or less, and hours of latency, Gopher starts
> to look a bit more realistic than getting a shell prompt via ssh :-).
Ok so i've missed the point as to why we need it in the kernel.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: In-kernel Gopher server
2003-10-23 15:12 ` Zwane Mwaikambo
@ 2003-10-23 15:22 ` John Bradford
0 siblings, 0 replies; 5+ messages in thread
From: John Bradford @ 2003-10-23 15:22 UTC (permalink / raw)
To: Zwane Mwaikambo; +Cc: linux-kernel
Quote from Zwane Mwaikambo <zwane@arm.linux.org.uk>:
> On Thu, 23 Oct 2003, John Bradford wrote:
>
> > Maybe the wristwatch example was a bit extreme, but what about a
> > system with very low bandwidth for connectivity? What if you were
> > trying to get configuration data back from a spacecraft millions of
> > miles away? At 300 BPS or less, and hours of latency, Gopher starts
> > to look a bit more realistic than getting a shell prompt via ssh :-).
>
> Ok so i've missed the point as to why we need it in the kernel.
There probably isn't one. It would be perfectly do-able in userspace.
John.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-10-23 15:21 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-10-23 9:30 In-kernel Gopher server John Bradford
2003-10-23 14:27 ` Zwane Mwaikambo
2003-10-23 15:01 ` John Bradford
2003-10-23 15:12 ` Zwane Mwaikambo
2003-10-23 15:22 ` John Bradford
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®