j1m: переводы

→Netstat prints information about network connections. You should see several lines of output, each one
describing an announced TCP or UDP service. Depending upon the contents of the network configuration
files we included on the CD, you might see output something like this:

→That starts cs(8). Try the ls /net again to check that the cs file has appeared.

Step 11b: Generate a server key set.

→(see ls(1)) should result in something like

→If you are just going to use Inferno for local Limbo programming, and not use its networking interface, you
can skip to the section ??Adding new users?? at the end of this document. You can always come back to this
step later.
To use IP networking, the IP device ip(3)) must have been bound into /net. Typing

→i) the host filesystem device ?#U? (see fs(3)) containing the inferno_root subtree of the host filesystem at
the root of the Inferno filesystem,
ii) the console device ?#c? (see cons(3)) in /dev,
iii) the prog device ?#p? (see prog(3)) onto /prog,
iv) the IP device ?#I? (see ip(3)) in /net, and
v) the environment device ?#e? (see env(3)) at /dev/env.

→The initial Inferno namespace is built by placing the root device ?#/? (see root(3)) at the root of the names-
pace and binding

→or the appropriate script file, should result in it starting up Inferno?s command interpreter sh(1), which
prompts with a semicolon:

→for Unix. An alternative to using the EMU environment variable is to place the correct invocation in a script
file (or batch file, for Windows) and invoke that instead of running emu directly. It is important to note that
for Windows the -r option also serves to indicate both the drive and directory on to which the software has
been installed. Without a drive letter the system will assume the current drive and will fail if the user
changes to an alternative drive. Once the environment variables or scripts are set up, as described above,
invoking plain

→for Plan 9, and

→for Windows.

→When invoked in this way emu displays a command window running the Inferno shell /dis/sh.dis. To
avoid typing the command line options each time you invoke emu you can store them in the environment
variable EMU which is interrogated when emu is started and might as well be set along side the PATH envi-
ronment variable if the same configuration options are to be used on each invocation.

→and log in as user inferno. When you log in, wm/logon will change directory to /usr/inferno and then
write the name inferno to /dev/user. If the file /usr/inferno/namespace exists it will be used to
construct a new namespace for the user based on the commands that it contains (see newns(2)).

→and then run

→You should now have a fully functional Inferno system. You will need to have a three button mouse to use
acme, wm, or plumbing.
To learn more you could start with the manual pages for: intro(1), emu(1), wm(1), wm-misc(1), sh(1), acme(1),
and limbo(1) and also the papers in sections 1, 2 and 3 of Volume 2 of The Inferno Programmer?s Manual.

→which should show something like the following:

→You can see the sequence of commands required to construct the current namespace by running

→Choose the shell option from the menu to open up a shell window. The configuration of Inferno will be
done from this shell window.

→You should see a new window open with a blue-greybackground and a small Vita Nuova logo in the bot-
tom left hand corner. Click on the logo with mouse button 1 to reveal a small menu. Selecting the Edit entry
will start wm/edit. In common with most wm programs the editor has three small buttons in a line at its top
right hand corner. Clicking on the X button, the rightmost button, will close the program down. The left-
most of the three buttons will allow the window to be resized ? after clicking it drag the window from a
point near to either one of its edges or one of its corners. The middle button will minimise the window, cre-
ating an entry for it in the application bar along the bottom of the main wm window. You can restore a min-
imised window by clicking on its entry in the application bar. The initial wm configuration is determined
by the contents of the shell script /lib/wmsetup (see toolbar(1) and sh(1)).

Step 5b: Open a shell window.

→Graphical Inferno programs normally run under the window manager wm(1). Inferno has a simple editor,
wm/edit, that can be used to edit the inferno configuration files. The ?power environment? for editing and
program development is acme(1), but rather that throwing you in at the deep end, we shall stick to the sim-
pler one for now. If you already know Acme from Plan 9, however, or perhaps Wily from Unix, feel free to
use Inferno?s acme instead of edit.

Step 5a: Start the window manager.

→if the manual page appears in more than one section.