peter/infix
1
0
Fork 0
mirror of https://github.com/kernelkit/infix.git synced 2026-08-01 21:33:02 +02:00
Code Issues Packages Projects Releases Wiki Activity

doc: when logging in you now land in UNIX shell by default

Browse Source 
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
This commit is contained in:
Joachim Wiberg
2024-04-03 16:08:37 +02:00
parent 3611d881ff
commit 7828636dd7
2 changed files with 21 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/cli/introduction.md
+6 -4
View File
@@ -12,10 +12,12 @@ short guide intends to help you with that.
## Key Concepts
The two modes in the CLI are the admin-exec and the configure context.
When logging in to the system, be it from console or SSH, you land in
admin-exec. Here you can inspect the system status and do operations
to debug networking issues, e.g. ping. You can also enter configure
context by typing: `configure`
When logging in to the system, be it from console or SSH, you first have
a stopover in a UNIX shell, usually Bash. Type `cli` to enter the CLI
and finally land in admin-exec. Here you can inspect system status and
do operations to debug networking issues, e.g. ping. You can also enter
configure context by typing: `configure`
The system has several datastores (or files):
doc/introduction.md
+15 -5
View File
@@ -21,11 +21,21 @@ is very useful to know how to navigate and use the CLI.
## Key Concepts
The two modes in the CLI are the admin-exec and the configure context.
When logging in to the system, from the console port or SSH, you land in
admin-exec. Here you can inspect the system status and do operations to
debug networking issues, e.g. ping. You can also enter configure
context by typing: `configure` followed by commands to `set`, `edit`,
apply changes using `leave`, or `abort` and return to admin-exec.
However, when logging in to the system, from the console port or SSH,
you land in a standard UNIX shell, Bash. This is for advanced users
and remote scripting purposes (production equipment). To enter the
CLI type:
admin@example:~$ cli
admin@example:/>
The prompt, constructed from your username and the device's hostname,
changes slightly. You are now in the admin-exec context of the CLI.
Here you can inspect system status and do operations to debug networking
issues, e.g. ping. You can also enter configure context by typing:
`configure` followed by commands to `set`, `edit`, apply changes using
`leave`, or `abort` and return to admin-exec.
> The [CLI Introduction](cli/introduction.md) can be useful to skim
> through at this point.