[Raion]

For years we've been saying you need bootp(), which flew in the face of modern network configs where bootp() actively can cause confusion on a DHCP enabled network. 

After trying https://wiki.irixnet.org/Network-Install-NetBSD which I revised from user Linear's post, I was able to myself confirm this. This is pretty momentous, and moreover it makes it far easier to install IRIX. Big thanks to Linear for confirming this, though I doubt she's the first just because of the age of the community. Things got lost in Nekochan, we know this haha!

Anyways, I'll be updating the guides. Rejoice, and those who have programs they maintain (i.e. irixboot, booterizer) you can update that!

This also enables my eventual FreeBSD and other guides to be far less... fussy.

[lunatic]

You mean like this?

https://tools.ietf.org/html/rfc1534

[Raion]

I'm aware that DHCP and Bootp are designed to be compatible. It's just not that useful though in practice, and problematic often.

[massiverobot]

Booterizer, while enabling bootp is only using isc's dhcpd, and it's not a complex config. Does you dhcp config expliciting _not_ enable bootp?

https://github.com/unxmaal/booterizer/bl...pd.conf.j2

-massive

[Raion]

IIRC, booterizer recommends a direct connection to the machine in question. The configs our guides use allow for that not to be a factor. In my case I have a script that turns on and off RSH as needed and reboots inetd on whichever box I am currently using as an install server.

Bootp just seems demonstrably unnecessary here, as I said, as we don't even have it on the enabled services list.