I'm interested in solving the problem mentioned by someone here:
There are indeed valid scenarios where the information printed by
/etc/rc.banner on the console may be needed but cannot be seen without
rebooting the m0n0wall, and I have been faced with this situation
I'm not sure whether it's a desirable to run /etc/rc.banner before the
console setup menu in every iteration of the loop in /etc/rc.initial,
but if not then at least there should be an option in the console menu
that runs /etc/rc.banner. However, the output of rc.banner plus
rc.initial is already 25 lines so it would be necessary eliminate some
of the blank lines output or otherwise modify the output of these
files in order to add another option.
Alternatively, the banner option could be part of a submenu that would
be accessible from the main console menu. (eg. Change option 6 to
"Additional options", which would be a submenu including "Ping Host"
and "System information"--or something intuitive that runs
/etc/rc.banner) This makes sense to me as it would leave the most
important options on the main menu and move debug/info options ping
and banner to a submenu.
Or, a very simple fix would be an unlisted console menu option eg.
'info' that would cause /etc/rc.banner to be run.
I have already implemented some of these ideas, but I would like to
find out what is Manuel's preference regarding the console menu, and
then I will submit a patch. Feedback is welcome.