How does "DONTEVAL@LOAD DOCOPY" affect loadups?

[Nick Briggs]

In the LLNS source we have (DECLARE%: DONTEVAL@LOAD DOCOPY (\NSINIT)), likewise for (\PUPINIT) in the PUP sources.

That implies to me that \NSINIT (and \PUPINIT) should be being called when the compiled files are loaded, and they should be setting up the basics of the networking in the new images we're creating, independent of whether the ethernet is available or not during loadup.

When the sysout is restarted, the only hook we're going to get is likely from (\ETHEREVENTFN 'AFTERMAKESYS) -- but I don't think there's anything that will really do what's necessary to get the 10 Mb net running. I don't recall ever having to call (TURN.ON.ETHER) or (ASSURE.ETHER.ON) or (RESTART.ETHER) or (\NSINIT) or anything else like that in my init files or by hand.

I'm currently building sysouts with the original LLETHER, which doesn't check for ethernet being available, and always starting lde/ldex with ethernet available, and yet it comes up with \PACKET.FILTERS being NIL -- which means that you have to call (\NSINIT) (either directly or indirectly) before networking works.

At this point I'm wondering if when some of the networking files were remade with networking disabled it captured the current value of a variable that affects networking as the wrong value...?

Any ideas how this is *supposed* to start up?

-- Nick

[Nick Briggs]

I found some of the missing info -- the network initialization got removed from the loadup lisp script when it was converted to a function in a managed file.

However, I still don't have a cleanly restarting network - even when the network is enabled it needs another call to \NSINIT before things work properly.