El dom, 11-03-2007 a las 10:27 -0700, Matt Zimmerman escribió: > On Sun, Mar 11, 2007 at 05:55:52PM +0100, Mario Izquierdo (mariodebian) wrote: > > Package: wnpp > > Severity: wishlist > > Owner: "Mario Izquierdo (mariodebian)" <mariodebian@gmail.com> > > > > > > * Package name : initramfs-tools-tcos > > Version : 0.67 > > Upstream Author : Mario Izquierdo (mariodebian) <mariodebian@gmail.com> > > * URL : http://cls-tcos.forja.rediris.es > > * License : GPL > > Programming Lang: Shell, Python > > Description : TCOS, a debian thin client operating system > > > > (Include the long description here.) > > > > TCOS is a new thin client implementation based on debian kernel, libs and bins. > > The image generation is very simple, TCOS add some hooks to initramfs-tools to > > build a initramfs file with all app that thin client have to use: > > > > dhclient > > udev > > wireless > > discover > > ssh server (dropbear) > > sound (alsa modules and libs) > > pulseaudio (networked sound server better than esound) > > vnc server > > rdesktop client > > Xorg (with a small number of files) > > > > Thin clients with more than 38 Mb of RAM will boot in "PXES mode", downloading > > with tftp the needed files. > > > > Thin clients with less than 38 Mb of RAM will try to mount a NFS server shared > > dir where gentcos has uncompressed initramfs image. > > Not complete distro like LTSP do. > > What is the difference relative to LTSP? Is it that it runs directly from > the initramfs where there is enough RAM? > > If so, wouldn't this be better added as a feature to LTSP rather than a new > thin client implementation? I thought about adding it at one point, but > didn't have a need for it yet. > LTSP 4.2 patch and compile kernel and packages specially for using in thin clients. LTSP 5.0 uses a chroot (Muekow ??) and install a debian/ubuntu with debotstrap. In LTSP 4.2 and LTSP 5.0, NFS server is required and nowadays with thin clients with more RAM it isn't necesary. I think that LTSP is a very big project and will be very difficult to make TCOS as LTSP feature. In other hand I have tried a lot of times to show my project to them but nobody ear my. With TCOS I build a small initramfs (5 Mb) and usr-x.x.x.squashfs (10-15Mb) (where some of utils are: Xorg, etc...). With 38 Mb aprox of RAM thin client don't need swap, with 32 can use hard disk swap automatically. Requirement are higher that LTSP or PXES because thin clients are running normal Xorg 7.1 and normal kernel 2.6.18-486 (for example) We are using Pentium 350 with 64Mb with 24h/365d uptime without problems. TCOS don't modify any debian package, only copy binaries and dep libs (ldd based) into initramfs or external squashfs. Thin client while booting download usr.squashfs and don't need NFS. TCOS has more utils like a XMLRPC server to make a dialog between server and thin clients, a GUI Monitor to control all hosts and a GUI (similar to pxeconfig) to create images. All GUI utils use gettext and are translated in english and spanish. SVN repos: https://forja.rediris.es/svn/cls-tcos/trunk/ Screenshots of GUI utils: http://soleup.eup.uva.es/mediawiki/index.php/TCOS-config/es http://soleup.eup.uva.es/mediawiki/index.php/TcosMonitor/Screenshots http://soleup.eup.uva.es/mediawiki/index.php/TcosVolumeManager Spanish Debian/ubuntu based distros (Guadalinex, Linex, Molinux..) are working to put TCOS in their repos to create terminal servers very easy. We are using in a production environment (Free access room of University) since October 2006, and we are installing in a lot of schools in our city. TCOS was presented last year to Google SOC and not was selected. Matt, thanks for your attention, and excuse my english. -- http://soleup.eup.uva.es/mariodebian
Attachment:
signature.asc
Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente