Since MikroTik changed the way raw disk images work, autorun.scr no longer works. This is since 6.43.10 stable.
The second partition was removed from the raw image and autorun.scr was disabled. There is no significance in the changelog as to why this happened.
I am trying to create a simple modification script of the CHR image to install an IP, route and set the default admin user’s password, in order to update a script which converts a VPS into a MikroTik CHR. Found here: https://gist.github.com/stroebs/54fc09734a3911e91eeeb43434f117df
This version is currently working with v6.37 but I want to install a new version by default to take advantage of disk auto-resizing.
Well, the previous image method had an autorun.scr file in the second partition in the /rw/ folder. This worked flawlessly.
The current image method still has /rw/autorun.scr, so I can only assume that because the file exists, that is the file that we’re supposed to be using. I’ve tried naming it autorun.rsc, which doesn’t work either.
There’s also zero documentation on this as I’m assuming it’s something that’s purely intended for resellers/distributors for branding or regulatory limit control. Doesn’t make sense to remove this functionality or reserve it for them in the case of CHR though.
After reading title I just think about https://wiki.mikrotik.com/wiki/Manual:Configuration_Management#Automatic_Import with script_name.auto.rsc but on this chroot-ed type of installation the autor of script or MikroTik support can give you proper feedback. We know the /import name.rsc and this topic is not normal script for ROS.
Sure, I get that, but there are official MikroTik people who frequent this forum who can reply to posts like this to educate the wider community about previous methods which used to work but have been deprecated or removed because of “xyz”.
There is a huge open source community who are hacking on MikroTiks and having a public response from MikroTik about this to educate us would be incredibly helpful.
In any case, I will email their support and bother a support representative about it.
FWIW, I am at point 3, per the support@mikrotik.com auto-responder… So it’s not unwarranted to ask for support here too:
