[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] Etherboot NIC Detection thoughts

I've thought about that, too. The logical extension of such an effort would be a Knoppix LTSP server CD and a Knoppix LTSP client CD, to be used for demo purposes. Then you could walk into any place, put the server CD in the 'biggest' box, put the client CD(s) and blank floppy into the various clients, and show it off. It could be a good way to say to the customer "You don't need to buy all new machines, just one, and perhaps not even that". Wish I had the time to work on such a setup.

In the Knoppix menus there is a "Terminal Server' app, but when I tried it briefly, it seemed that what it really did was allow a client to boot the Knoppix system from across the wire rather than the local CD, but once it was all booted, all the apps ran on the client, not the boot server.


Les Mikesell wrote:
On Tue, 2003-10-28 at 08:17, Petre Scheie wrote:

I understand what you want, but if you think about it, it can't work that way. The purpose of the boot ROM/floppy/PXE is to provide a bit of software to use the client's ethernet card to 1) request and get an IP address, and 2) request and get an Operating System. The point is the whole process is driven from the client end, starting with turning on the power to the client. It can't be driven by the server. How would the server know to send anything to the client if the client didn't first request it? And to send the request, the client must have some mechanism for talking to the ethernet card in a barebones way. HTH.

Perhaps someone could build a knoppix/morphix CD that contained a
script that would identify the hardware and write the correct
floppy to perform subsequent network boots on that type of client.

  Les Mikesell
   les futuresource com

K12OSN mailing list
K12OSN redhat com
For more info see <http://www.k12os.org>

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]