Re: Can you MOP boot an install kernel directly?
Paul Koning <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.vax |
|---|---|
| Message-ID | <[email protected]> |
> On Aug 4, 2025, at 5:47 PM, Johnny Billquist <[email protected]> wrote: > > On 2025-08-04 19:01, Paul Koning wrote: >>> On Aug 4, 2025, at 12:36 PM, Jason Thorpe <[email protected]> wrote: >>> >>> >>> >>>> On Aug 4, 2025, at 7:45 AM, Johnny Billquist <[email protected]>wrote: >>>> >>>> I'll just top-post to be lazy. >>>> >>>> First of all, as you know, MOP is the "native" way to netboot DEC machines from back in the day. And MOP sortof fills the place of both DHCP and TFTP in one. But it's more targeted for the explicit need of netbooting and remote management. But in a sense, for VAXen, it would be great if we had the possibility of getting all the netbooting though MOP and not need DHCP and TFTP. Not sure if that is possible, though. >>> >>> Can MOP supply the IP address to the system? If not, you're not goingto be eliminating DHCP (or BOOTP). >> MOP has a "parameter load" message that can supply a couple of things, such as the system DECnet node address. But there is no parameter code for IP address, unfortunately. Not even in the Phase V version of MOP. > > If you have the information around, or in your head, I don't care what they call the "address" field. But is it limited to two bytes, or can it be of different sizes? If we can get four bytes in there, then it can certainly be an IP address. No, it's specified as 2 bytes. paul