Stein !
To kar si nazadnje omenil "boot preko mreže" bo pa težko izvedljivo!
Nekoč so bili časi ko si v mrežno kartico vstavil ROM z boot loaderjem za Novell in potem se je to zgodilo,
danes pa kar tako za običajen PC - hm, hm, veliko preveč dela!
Na temle naslovu imaš še več tega:
http://www.kegel.com/linux/pxe.html
Remote Network Boot via PXE
Let's say you're responsible for a network of 100 computers shared by students. What do you do if one of those computers starts acting funny? If you're like me, you'll just do a clean install of the operating system. But that's a lot of work, especially if you have to do it several times a week. Fortunately, most PCs sold since 2001 follow the PC99 guidelines from Intel and Microsoft, which among other things says that new computers with Ethernet interfaces must implement two useful features: wake-on-LAN and network boot.
Wake-on-LAN
If your BIOS is set to enable Wake-On-LAN, and is off, it will turn itself on when it receives a packet containing 6 bytes of FFh followed by 16 copies of its Ethernet address. (See the Wake-On-Lan mini-HOWTO for more details.) This can be used to help force reinstalls of the operating system in the middle of the night, when nobody's there.
Network Boot
There are several ways computers can boot over a network, but the one mandated by PC99 is called PXE. PXE is a kind of DHCP extension, so all you need is an up-to-date DHCP server and a TFTP server.
Back when PC99 and PXE were new, the normal DHCP server hadn't yet been updated to handle PXE, so Red Hat created a package called 'pxe', and has shipped it with all versions of their Linux since 6.2. You probably don't want to use it, though, now that the normal ISC DHCP software shipped with Linux can handle PXE.
Together, a DHCP server and a TFTP server can be set up to handle PXE boot requests. It's up to you what to give the PCs when they boot; several possibilities include