In-kernel Gopher server
From: John Bradford (john_at_grabjohn.com)
Date: 10/23/03
- Previous message: Zoltan Menyhart: "Re: [RFC] prevent "dd if=/dev/mem" crash"
- Next in thread: Zwane Mwaikambo: "Re: In-kernel Gopher server"
- Reply: Zwane Mwaikambo: "Re: In-kernel Gopher server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 23 Oct 2003 10:30:00 +0100 To: linux-kernel@vger.kernel.org
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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Zoltan Menyhart: "Re: [RFC] prevent "dd if=/dev/mem" crash"
- Next in thread: Zwane Mwaikambo: "Re: In-kernel Gopher server"
- Reply: Zwane Mwaikambo: "Re: In-kernel Gopher server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
