Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote: > > Unfortunately, the boot loader is already using a different method > > to > > access the boot image - I don't think it would be desirable to have > > two > > different methods for the same thing, especially when you have to > > start > > two different servers for serving the image. > Yeah, I would simply write a kernel device driver for the protocol I > used. > The alternative is to add NBD support to the boot loader, but that > would > require us to add TCP support, too. Which is not an option, if you ask me :-) > > I hope Ingo will continue with this some day, anyway :-) > Yeah, with the FreeBSD compatibility layer, porting the network > device > driver for my Mac is hopefully a trifle, now. So, one day... :-) Let's hope for the best, then :) > > I didn't yet think about a new name for nbd; maybe "remote_disk" > > would > > do. > How about the obvious: "network_block_device"? Now that's a bit redundant, don't you think? But if you want to keep remote_disk for the boot loader's protocol only, then I certainly won't mind, either. Bye, Axel.