Not that the built in PXE server mode is not good, Its Great! and i wouldnt like it removed, im shure it could be usefull in many circumstances, but i think there are also circumstances where we would like to "manually" setup our own "Pxe server" in our own boxes, without the need to boot that pc with SRCD. And in some cases, we might need that pc (the one acting as the PXE server) to be running our own OSs, maybe even Windows! :)
In short, the same kind of flexibility that PloP linux has. :)
For Example, there are cases where it would be great to have my netbook running windows, and serving SRCD via PXE at the same time, then i could (for example) boot the other (broken) PC from my netbook via PXE, mount the local partitions on that pc, "share them" with samba, and viola! im able to access all the files from my windows netbook for backup purpuses, or even to use my allready installed and updated virus scan software to scan those partitions for viruses.
No aditional comercial software would be needed for the user, tftpd32 works great for this, and its free & open source. That takes care of the TFTP and the DHCP services, and a simple windows share would provide filesystem "service" for the late boot stages.
The only things required for this to happen are...
1.- add support for samba filesystems at startup. Then, instead of using something like:
Code: Select all
netboot=http://192.168.157.1:8080/sysrcd.dat // or netboot=nbd://192.168.157.1:2000 // we could use something like smbmount=//10.0.0.1/srcd:MyUser:MyPW
3.- There is no Nª 3. Thats it! :)
I think these simnple changes could be easily implemented, and would greatly increase the flexibility and usability of this (allready) wonderfull tool.
P.S. I would gladly voulunteer to develop these changes myself and share them, but even tho i do know some programming, networking, and other "computer stuff" (im a computer technician), my linux and C/C++ skills dont go that far :(
Best regards, Ernesto