4 ms·

Why should we trust you? Sure you set the mirror to rackspace but easily things can go wrong and if your competent enough to get iPXE running you should be doin

by damm 9y ago

Why should we trust you? Sure you set the mirror to rackspace but easily things can go wrong and if your competent enough to get iPXE running you should be doing the job your damn self.

nacs 9y ago
It's OSS: https://github.com/antonym/netboot.xyz https://github.com/antonym/netboot.xyz Run it on your own server and point it at that if you have trust issues.
posguy 9y ago
In addition to the trust factor, what happens when this service dies? Netboot.me offered essentially the same service years ago, but disappeared and stopped working, with many guides written for and around their service.
- pmoriarty 9y ago
  I wonder if something like this could be built around torrents, or maybe one of the persistent distributed archive networks (whose names escape me at the moment).
- devttyeu 9y ago
  I made an IPFS(the torrent+git+ thing) based fork of this because of these reasons. It uses IPFS gateway setup in local network, this enables: * Caching of downloaded data (this is useful when using it to boot multiple computers in one LAN) * More trust: boot menu is served from local IPFS gateway using immutable hashes. It is also really easy to review it by hand. * It's a bit more service-dies-scenario proof Downsides include lack of better documentation and messy code in places - it's a large scale refactor that changes the basics of how the tool works and isn't quite polished. It lives at https://netboot.devtty.eu/ https://netboot.devtty.eu/. There is no set-up instructions(tr;dr setup: run lan-open ipfs gateway, add A dns record 'ipfs.local' pointing at it in your lan DNS server, rest like netboot.xyz).
  - voltagex_ 9y ago
    I'm pretty sure you're not supposed to use .local as a unicast domain name due to its use in mDNS/Zeroconf
jlgaddis 9y ago
There's nothing stopping you from pointing it at your own server -- which is what I did when I played with this months ago.

by damm 9y ago

Why should we trust you? Sure you set the mirror to rackspace but easily things can go wrong and if your competent enough to get iPXE running you should be doing the job your damn self.

nacs 9y ago

It's OSS: https://github.com/antonym/netboot.xyz https://github.com/antonym/netboot.xyz Run it on your own server and point it at that if you have trust issues.

posguy 9y ago

In addition to the trust factor, what happens when this service dies? Netboot.me offered essentially the same service years ago, but disappeared and stopped working, with many guides written for and around their service.

pmoriarty 9y ago
I wonder if something like this could be built around torrents, or maybe one of the persistent distributed archive networks (whose names escape me at the moment).
devttyeu 9y ago
I made an IPFS(the torrent+git+ thing) based fork of this because of these reasons. It uses IPFS gateway setup in local network, this enables: * Caching of downloaded data (this is useful when using it to boot multiple computers in one LAN) * More trust: boot menu is served from local IPFS gateway using immutable hashes. It is also really easy to review it by hand. * It's a bit more service-dies-scenario proof Downsides include lack of better documentation and messy code in places - it's a large scale refactor that changes the basics of how the tool works and isn't quite polished. It lives at https://netboot.devtty.eu/ https://netboot.devtty.eu/. There is no set-up instructions(tr;dr setup: run lan-open ipfs gateway, add A dns record 'ipfs.local' pointing at it in your lan DNS server, rest like netboot.xyz).
- voltagex_ 9y ago
  I'm pretty sure you're not supposed to use .local as a unicast domain name due to its use in mDNS/Zeroconf

jlgaddis 9y ago

There's nothing stopping you from pointing it at your own server -- which is what I did when I played with this months ago.