Netscript over-written during upgrade installation

[haiqu]

The file /boot/system/boot/netscript contains examples of how to set up some network parameters. If this file is actually set up, it will be over-written next time the system is upgraded from sources.

Suggest changing the filename to netscript.sample and thus allowing the actual netscript to remain available without re-editing every time.

[scottmc]

Shouldn't users not be changing things in the /boot/system folders?

[haiqu]

Usually, except that this file needs to be configured for the specific NIC in the user's system.

In fact I'm unsure whether it's even used with the current networking stack, maybe someone should check into that first.

[mmadia]

Replying to scottmc:

Shouldn't users not be changing things in the /boot/system folders?

This is 100% correct. The system folder is off limits to 3rd party applications and the end user. Granted, this is currently done by convention and is not enforced by the system.

While one could argue that the system folder needs to be modified in the case of sound drivers conflicting with OSS, I would point out that the desired functionality -- preventing such collision, has not yet been implemented.

Rob, looking at Haiku's /boot/system/boot/Netscript file, the example commands appear to be CLI commands. In addition to this, looking at R5Bone's Netscript, it explicitly states to not edit the file and to instead add the commands to /boot/home/config/boot/UserBootScript. Could you try placing your customizations in UserBootScript? If it works, then Haiku's Netscript file should include a similar explanatory text comment to help avoid future confusion.

[mmadia]

/boot/system should not be modified by users.