Page History

...

1.  In the foreground w/screens 
   • linuxRT_viocConsole.sh vioc-b34-fb01
2. In the background w/screens
   •  linuxRT_startup_vioc.sh vioc-b34-fb01
3. In the foreground without screens
   • linuxRT_startupConsole.sh vioc-b34-fb01
     
     

Development Mode:

If you're going to be frequently changing what viocs start automatically and don't want to keep changing the screeniocs file, you can define $LOCAL_IOCS in your kernel-modules.cmd file to override what's in screeniocs. Examples:

export LOCAL_IOCS=( vioc-abc-123 vioc-456-def vioc-789-ghi )
or to start nothing
export LOCAL_IOCS=(  )

Don't do this with stable production systems. It's there to give you flexibility during development without changing screeniocs all the time.

If using the screen program:

• ctrl a d : detach from the screen session
• ctrl a { : scroll up through the start-up messages.
• View all vioc's on host cpu: screen -ls
• Attach to vioc: screen -r <vioc_name>
• Attaching to a linuxRT screen session multiple times with  "laci"  concurrently:
  screen  -x <vioc_name>
  

• Note: The "screen" program supports multi-display mode. When you attach an existing screen session, you can use "-x". It allows an user to attach to "a not detached screen session." The -r option allows a user to attach to a "detached screen session".
  
  
  

Development Mode:

If you're going to be frequently changing what viocs start automatically and don't want to keep changing the screeniocs file, you can define $LOCAL_IOCS in your kernel-modules.cmd file to override what's in screeniocs.

Examples:

export LOCAL_IOCS=( vioc-abc-123 vioc-456-def vioc-789-ghi )
or to start nothing
export LOCAL_IOCS=(  )

    

Common Linux Commands Used

...