You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently a lot of system bootstrap tasks, like loading YANG models and startup-config, is done in runlevel S. When completed, the system proceeds to runlevel 2 to bring up networking and system services.
This presents bit of a problem for board bring-up and debugging.
An alternative bootstrap could be to let runlevel S only do the absolute minimal so that a kernel command line argument S could bring the system to single user mode (runlevel 1) without having loaded YANG models and startup-config, and thus leaving the system in a "debuggable" state -- provided of course the Infix image has password-less root login enabled.
The impact of the change on the system would be minimal (if any):
current runlevel S tasks move to runlevel 2
add a task in runlevel 2 that waits for startup-config to be loaded and trigger change to runlevel 3
all services currently starting in runlevel 2 would be moved to runlevel 3
Currently a lot of system bootstrap tasks, like loading YANG models and
startup-config
, is done in runlevel S. When completed, the system proceeds to runlevel 2 to bring up networking and system services.This presents bit of a problem for board bring-up and debugging.
An alternative bootstrap could be to let runlevel S only do the absolute minimal so that a kernel command line argument
S
could bring the system to single user mode (runlevel 1) without having loaded YANG models andstartup-config
, and thus leaving the system in a "debuggable" state -- provided of course the Infix image has password-less root login enabled.The impact of the change on the system would be minimal (if any):
Idea by: @wkz
The text was updated successfully, but these errors were encountered: