|
From: <ebi...@ln...> - 2003-08-03 18:02:35
|
ke...@et... (Ken Yap) writes: > >methods are setting up a RIS server (ugly) or somehow try to get the RIS > >boot disk tagged for etherboot (ugly, especially considering the likely > >lack of support for my NIC, the sis900). =20 > > Have you looked? There is a sis900 driver. > > >Is this too far outside to purview of the etherboot project to be done?=20 > >Etherboot would then have to maintain some process in memory to be able > >to communicate with the iscsi server while the machine was running. > > Etherboot gets displaced by whatever it's loading so it cannot "maintain > some process in memory". > > I don't know how feasible it is to boot off iscsi. It may require a more > complex network stack, i.e. TCP, than Etherboot has. We now have the proof of concept tcp stack now and at first glance it does not look two hideous. We do have an infrastructure for disk drivers now so running iscsi over that would probably work. But in the case of Etherboot I would really recommend something that takes the Windows preinstallation environment and wraps the whole thing up into an ELF executable and give that to etherboot. Unless it has really nasty dependencies that should work fairly cleanly. Eric |
