DHCP

Would it be possible to change the time DHCP is activated?

Currently it takes up to 30 seconds before the desktop starts.

At this point could it be changed to either (user choice which) Start with a user defined static IP, start with the previously leased IP or start with the interface down?

Then later in the boot sequence do a DHCP request in the background.

At some point (when I dig out my notes and get some free time), I’ll hopefully be able to send Rik the instructions to implement autoconfig addresses properly. That won’t solve the 30s delay issue though – I’d suggest that the ideal solution for that would be to check the link state and either disable the interface or revert to a static / autoconfig IP immediately if down. That does depend on whatever code drives the ethernet hardware itself being able to pass on the link state, though.

Personally, I think DHCP should be a background task anyway (though the initial DHCPREQUEST in linux isn’t), but I’m guessing there’s technical reasons it isn’t during riscos boot.

It should really be possible to leave DHCP permanently enabled (unless you want a static IP) and have the OS behave in a sensible way depending on the circumstances.

Would it be possible to change the time DHCP is activated?

Get a faster DHCP server? Seriously my £10 off ebay 3com router dishes them out pretty fast.

The reason the boot sequence must block is to allow for network boot (ie. the bits after that could/can include things set up by a network manager held on a central server), rushing past and into the desktop would then leave you with no applications.

Get a faster DHCP server? Seriously my £10 off ebay 3com router dishes them out pretty fast.

So does mine, but since we have no wifi support I have to use a client wifi access point, which doesn’t start in time.

The reason the boot sequence must block is to allow for network boot (ie. the bits after that could/can include things set up by a network manager held on a central server), rushing past and into the desktop wou

Surely, only if you utilise this facility, otherwise it doesn’t matter.

But given this feed back I shall modify the request.

Could the predesk DHCP timeout and the action on failure be user defined?

It’d be nice, at the very least, if the timeout output some text saying “will timeout after 30 seconds” or even a count-down.

It’d be nice, at the very least, if the timeout output some text saying “will timeout after 30 seconds”

Surely all that is needed is to change the message in !Boot.Choices.Internet.Startup to read as such rather than what it says now?

rushing past and into the desktop would then leave you with no applications.

I don’t see why the network applications couldn’t boot in the fullness of time, much as opening a suitable directory containing them would.

I don’t see why the network applications couldn’t boot in the fullness of time, much as opening a suitable directory containing them would.

In principle, but they are ‘in line’ at the moment in case you want to boot from the network (I think).