I got a quick question about the implementation of this project. Would it be easier to start building the OS from various pieces (essentially from scratch), or would it be better to start out with a minimal working intallation and removing parts section by section? Thanks for the help so far! ~AD Bourdon Jens> The /dev/fb is no problem, I'd just have to subclass Jens> rfb::Framebuffer. The real work is to convert keyboard input Jens> from /dev/tty... to X Windows (RFB) keycodes and to get Jens> mouse events from /dev/mouse or gpm. I didn't have much time Jens> to check this out yet. Any ideas? Btw, I'd use a linux Jens> 2.4.x kernel for that, they've got more framebuffer drivers. Jens> So, whats needed? - Kernel with /dev/fb and network support Jens> - linux 2.4 - /sbin/init binary and a small sh-script - Jens> simpleinit? - a very small shell - ? - a very small libc Jens> (not glibc, it's too large) - ? - insmod / ifconfig / route Jens> (to configure the nic) - loadkeys (not everybody's got an Jens> english keyboard) - gpm (mouse driver) - a vnc client Jens> supporting /dev/fb, /dev/tty and gpm Jens> Did I miss anything? Debian's bootfloppies could be used for this - the boot-floppies package has a set of scripts to build a boot floppy (actually 2 floppies now the kernel has grown so much, but this could be squeezed back down to 1 presumably). This includes busybox, which could be used on its own - there is also a busybox-static package :- Package: busybox-static Priority: optional Section: shells Installed-Size: 872 Maintainer: Erik Andersen <[EMAIL PROTECTED]> Architecture: i386 Source: busybox Version: 0.48-1 Filename: pool/main/b/busybox/busybox-static_0.48-1_i386.deb Size: 403218 MD5sum: ac1713a40ad025896ee112874d3d9ebb Description: Provides a stand alone rescue shell with tons of builtin utilities. BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides minimalist replacements for the most common utilities you would usually find on your desktop system (i.e. ls, cp, mv, mount, tar, etc). The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however, the options that are included provide the expected functionality and behave very much like their GNU counterparts. . BusyBox-static provides you with a statically linked simple stand alone shell that provides all the utilities available in BusyBox. This package is intended to be used as a rescue shell, in the event that you screw up your system. Invoke "busybox sh" and you have a standalone shell ready to save your system from certain destruction. Invoke "busybox", and it will list the available builtin commands. But busybox does not seem to contain networking commands itself (well it has telnet, but no ifconfig, netstat, route). The boot-floppies scripts require additional packages to build a boot floppy. Sincerely, Adrian Phillips ______________________________________________ FREE Personalized Email at Mail.com Sign up at http://www.mail.com/?sr=signup --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to [EMAIL PROTECTED] See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
