I never had a value for "Script to run on first boot" should I do it now?

The gl-mt6000 wiki says

If creating a custom image, do not leave the “Script to run on first boot (uci-defaults)” box empty. If you do, the default reflash will be “Keep Configuration”, causing problems later. A simple `#` entered into the empty box is sufficient.

When I got mine a while ago, I did not know about this so I just flashed a sysupgrade image and it has been fine. If I want to follow the advice now, what will happen if I build an image with this file in it files/usr/libexec/uci-defaults/fake.sh

#!/bin/sh
# comment
exit 0

The wiki isn’t clear on the “causing problems later” part.

as I read it this is only valid for initial flashing from stock to OpenWRT ?
a post flash reset should solve any issues that may occur ?

2 Likes

That's how I read it, too. You certainly don't need an empty defaults script after you've installed OpenWrt...

Since you are already running real OpenWrt, basically nothing; that just eats another few bytes in flash and does not change functionality in any way.

I am confused as "stock" is an OpenWrt fork as I understand it.

This is referring to the firmware selector.

If you are just downloading the standard image, you do not need to do anything.

If you are clicking "Customize installed packages and/or first boot script" so you can modify what is listed in the " Installed Packages" textbox, then you should NOT leave the " Script to run on first boot (uci-defaults)" text box empty. Either add some lines of script to do what you want it to do or add the "#" symbol - this means "comment" or "no-op".

1 Like

"All" routers run Openwrt to some extent, even the unsupported/able ones..

What gl.inet is using as an USP could technically be used by all vendors.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.