Hi
> 3. I have read the PXE HOWTO you referenced, but am kind of turned off by
> having to tag different kernels for different network chips. I know I only
> have one client type right now, but when I get more (with PXE) I don't want
> to have to worry about which ones use which chipsets. With PXE, I don't
> have to worry about it, nor do I have to maintain a bunch of different
> NIC-specific Etherboot-tagged kernels.
>
> Based on my (admittedly limited) knowledge of LTSP, I have concluded that if
> you have PXE clients, using PXE offers some real advantages. Enough that I
> decided to use it.
>
> Differing opinions, ideas, or insights are welcome.
PXE, Etherboot, and the kernel do not affect one another.
Use LTSP 3.0's initrd way of loading the network drivers.
Use an etherboot image for your NIC
In any event no PXE or etherboot solution affects how your kernel
handles the NIC. (Its easy to boot via PXE, and etherboot a kernel that
won't run - panic can't load NFS as the network card is not supported)
PXE-Etherboot-initrdKernel works well and is easy
(Many PXE MBs use intel eth100 or rtl8139 NICs.)
James
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net
