How to make a desktop into a wireless thin client?

[senthilarumugam]

Hi ALL,

How to make a desktop machine - HP [intel Celeron ] machine - wireless , as a Thin Client machine.

Please Tell me the steps to do ;

I'm a new user to Puppy and also having less knowledge in networking. So, I need a clear, step by step procedure to follow.It will be more useful for me if you tell me about;

DESKTOP:
1. How to make a desktop machine - [wireless] as a thin client in a network architecture,using Puppy Os ?
2.How to make a desktop machine - [Ehernet] as a thin client in a network architecture,using Puppy Os?
LAPTOP
3. How to make a laptop machine - [wireless] as a thin client in a network architecture, Using Puppy OS?
4.How to make a laptop machine - [Ehernet] as a thin client in a network architecture, Using Puppy OS?

Thank You So Much

[raffy]

Puppy is ready for the machines you described. Just burn the latest Puppy ISO to CD and boot. Version 2.14 is recommended for a smaller footprint: http://puppylinux.org/user/news.php Later, you can try the bigger ISO.

For wireless, see http://puppylinux.org/wikka/WirelessWorking and also this if you get problems.

[robert_m]

This is an old post, but I will comment for others who might come upon it while searching for "thin client".
A thin client is a terminal that has a monitor, keyboard and usually a mouse and possible audio capabilities. The server does most of the processing. It boots from the server, and thus the software management is on the server side.
A thick client has more processing power and runs programs internally.

1) the OP asks for help making a thin client. I take that to mean they wish to boot Puppy using PXE.
- Puppy is great for diskless machines and can boot with PXE :
http://murga-linux.com/puppy/viewtopic.php?p=426062

2) Wireless booting of diskless devices would require boot code on the client sufficient to operate the wireless hardware AND establish an IP address so it could load the OS from the server, requirements that are avoided in a wired system because the PXE capable NIC of a wired thin client has built in code to communicate with the server to which it is attached.

3) Raffy offers a solution for getting Puppy to run on the OP's hardware, but presumes the systems have a cd drive. Regardless, this solution does not make the units thin clients.

4) Perhaps the OP imagined booting puppy on their systems and using it as an nth stage boot loader to install an image provided by the server and boot to that? ... possible, but not practical, and certainly the "how to" would not be offered in a cookbook format.

[rufwoof]

Subjective to the choice of 'thin client' definition. Wikipedia for instance

A thin client is a lightweight computer that has been optimized for establishing a remote connection with a server-based computing environment. The server does most of the work, which can include launching software programs, performing calculations, and storing data.

I have a 15MB boot choice that fundamentally just has wireless net connect and ssh. When booted and wireless net connected I ssh into hashbang (from UK to US) from where I can run email, irc, web browsing ...etc. and it all routes through the ssh tunnel. My local ISP just sees that encrypted flow, remote web sites see my US hashbang IP (DNS lookups are also via hashbang). If I add X and chrome or whatever to that I can also run a local browser with again all traffic flowing through the ssh tunnel (socks5 proxy) - but then that's arguably no longer really a thin client.

[mikeb]

Fatdog and lighthouse had pxe booting but wirelessly would be a problem as the technique usually requires having a lan card that is capable... wifi ones are not known for such things.
mike