Good point. But I wonder if ipxe.pxe/kpxe/kkpxe would be even more save to use?? AFAIK the iPXE devs mostly point people to use ipxe.pxe in their forum as it comes with native drivers as well as UNDI capability. I am not really sure which we should make the default?!
Patience, I’ve found, makes all the difference.
Report bugs, request features, or get the latest progress.
@tian Some of the updating is kind of to be expected. It was literally adding more and more backslashes to the whole of the command. So, in some cases, the single backslash would remain, but depending on the following letters or characters \n \r \t \7 or any other slash statement would be literally interpreted to their respective escaped character (\n == newline, \t == tab, etc…)
To fix I have to escape all the characters especially those dealing with a backslash as a direct part. So this should be fixed and functional, though I’m sure there could be the potential for some funny things down the road (funny being I don’t know what to expect and maybe you won’t either).