.de EX.nr x \\$1v\\!h0c n \\nx 0...de FG		\" start figure caption: .FG filename.ps verticalsize.KF.BP \\$1 \\$2.sp .5v.EX \\$2v.ps -1.vs -1...de fg		\" end figure caption (yes, it is clumsy).ps.vs.br\l'1i'.KE..\" step numbers.nr ,s 0 1.af ,s a.am NH.nr ,s 0 1...de Sn		\" .Sn "step"•\ Step \\n(H1\\n+(,s: \\$1...de Ss.P1.B.Sn "\\$1".P2...TLInstalling the Inferno Software.AUVita Nuova.brsupport@vitanuova.com.br12 June 2003.SP 4.LPInferno can run as either a native operating system, in the usual way, or as a.I hostedvirtual operating system,running as an application on another operating system.This paper explains how to install Inferno from the distribution mediato a hosted environment and how to configure the system forbasic networking..LPInferno can run as a hosted virtual operating system on top ofPlan 9, Unix or Windows.In this paper, the term.I Unixis used to cover all supported variants, currently FreeBSD, Linux, HP/UX, Irix and Solaris,and the term.I Windowscovers Microsoft Windows (98, Me, Nt, 2000, and XP).(Windows 98 might first require installation of the Unicode layer update from Microsoft.).NHPreparation.LPYou should ensure at least 150 Mbytes of free space on the filesystem.The installation program will copy files from the distribution CD to adirectory on the filesystem called the.I inferno_rootdirectory.You can choose the location of this directory.If you are installing to a multiuser filesystem outside your control a subdirectory of your homedirectory might be most sensible. If you plan to share the Infernosystem with other users then common choices for.I inferno_rootare.CW /usr/infernoon Unix and Plan 9 systems, and.CW c:\einfernoon Windows systems.Where these appear in examples in this paper you should substituteyour own.I inferno_rootdirectory..Ss "Choose the \fIinferno_root\fP directory."Ensure that the user who will run the installation program hasappropriate filesystem permissions to create the.I inferno_rootdirectory andfiles and subdirectories beneath it..NHCopying Files.LPOn all platforms the files will be owned by the user doing the installation,except for installation onto a FAT file system (eg, on Windows), where the filesappear to be owned by.CW Everyonebecause FAT does not record ownership..Ss "Insert the distribution CD into the CD drive."On Unix and Plan 9,mount the CD to a suitable location on the filesystem, call this location.I cd_path .On Windows, note the drive letter of the CD, call this drive letter.I cd_drive .The files will be copied by an Inferno hosted installation program which runsdirectly from the CD.The directory.CW /installon the CD contains an installation program for each supported platform \- a shellscript for Unix and Plan 9 and an executable for Windows.The Plan 9 install script is called.CW Plan9.rcand determines the CPU type from the environment variable.CW cputype .The Unix install scripts all have names of the form.CW \fIhost_os\fP-\fIhost_arch\fP.shwhere.I host_oswill be one of:.CW FreeBSD ,.CW Linux ,or.CW Solarisand.I host_archwill be one of:.CW 386 ,.CW mips ,.CW poweror.CW sparc .Most platforms offer just the one obvious combination.The Windows installation program is called.CW setup.exe ;it is used on all varieties of Windows.The next step describes how to begin the installation by running the programthat corresponds to your host system..Ss "Run the installation script."The installation program will copy files from the CD to the filesystem.The Windows installation program will also create registry entries and addan Inferno item to the Windows.I startmenu.On Plan 9, run.P1rc \fIcd_path\fP/install/Plan9.rc \fIinferno_root\fP.P2Where.I inferno_rootis the path to the chosen Inferno root directory. The CPU architecturewill be inferred from the environment variable.CW cputype .On Unix, run.P1sh \fIcd_path\fP/install/\fIhost-os\fP-\fIhost_arch\fP.sh  \fIinferno_root\fP.P2Where.I host_osis the Unix variant name.CW FreeBSD , (.CW Irix ,.CW Linuxor.CW Solaris )..I host_archis the CPU type (eg,.CW 386 ), and.I inferno_rootis the path to the chosen Inferno directory.On Windows, run.P1\fIcd_drive\f(CW:\einstall\esetup.exe.P2The Windows installation program will ask you to choose the location of the installationdirectory on the hard disk..LPOn all platforms, a copy of Infernoon the CD will install from various installation packages on the CD to the.I inferno_rootsubtree on the filesystem.On any platform it installs support for all..LPInferno is now installed, but it needs to be configuredfor your site.The process acts as a quick tour of parts of the system.The main tasks are to add local parameters to the network data base,and to set up the authentication system.If you are going to run Inferno standalone, for instance to experiment with Limboand the file serving interface,most of what follows can be deferred indefinitely.It is still worthwhile skimming through it, because the first few sections tell howto start up Inferno with correct parameters (eg, root directory and graphics resolution).(A configuration program that runs under the window system would be more convenient,and fairly easy to do, but that has not yet been done.).NHRunning Inferno.LPInferno host executables are all kept in a single directory correspondingto the combination of host operating system and CPU architecture \- the Inferno.CW bindirectory..P1\fIinferno_root\fP/\fIhost_os\fP/\fIhost_arch\fP/bin.P2(On Windows the path might need.CW \enot.CW /of course.)That directory can be added to the search path of the host system's command interpreter,and that process will be described first, although as discussed later one can use a scriptinstead and that is sometimes more convenient.(Of course, the script will still need to refer to that directory.).LP.I "Plan 9:\ \ "Plan 9 users should add a line to their.CW lib/profilefile that binds this directory after their.CW /bindirectory..P1bind -a /usr/inferno/Plan9/$cputype/bin /bin.P2The bind is done after the existing.I bindirectory to avoid hiding the existing Plan 9 compilers.If, at a later stage, you build either the hosted or native Inferno kernels for ARM or StrongARMyou should ensure that the Inferno compilers are used rather thanthe Plan 9 compilers, since they differ in the implementation offloating-point instructions (the Plan 9 ARM suite uses a byte order that is more plausiblethan the order ARM dictates but therefore wrong).That difference is likely to be resolved at some point but it has not yet been done..LP.I "Windows:\ \"The.I host_osis always.CW Nt(even for Windows 98, 2000 or XP)and.I host_archis always.CW 386and the installation program will create an entry on the.I "start menu"to invoke Inferno.For Unix systems or Windows systems in which Inferno will be startedfrom a command shell, the environment variable.CW PATHshould be set to include the Inferno.CW bindirectory.For Windows 95 and Windows 98 this should be done in the.CW \eautoexec.batfile by adding a line like.P1PATH=c:\einferno\eNt\e386\ebin;%PATH%.P2You will need to reboot Windows to have the system reread the.CW \eautoexec.batfile.For Windows NT and Windows 2000 modify the.CW Pathenvironment variable through.I "Control Panel -> System -> Environment" ..LPIf you are using an MKS or Cygwin Unix-like shell environment,you might instead set:.P1PATH="c:/inferno/Nt/386/bin;$PATH".P2and export it if necessary..LP.I "Unix:\ \"For Unix  systems, for.CW shderivatives, the environment variable.CW PATHshould be set to include the Inferno.CW bindirectory.This might be done in your.CW .profilefile by adding a line like.P1PATH="/usr/inferno/Linux/386/bin:$PATH".P2Don't forget to ensure that.CW PATHis exported.You may need to log out and back in again for the changes to take effect..KS.Ss "Start Inferno."Hosted inferno is run by invoking an executable called.I emu ..KEOn Windows, select the Inferno option from the.I "start menu" .This will invoke.I emuwith appropriate arguments to find its files in.I inferno_root .If you need to change any of the options passed to.I emuwhen invoked from the.I "start menu"you need to do this by clicking the right mouse buttonon the Windows task bar and choosing.I "Properties -> Start Menu Programs -> Advanced"to modify the shortcut used for Inferno.For Unix and Plan 9, you will need to tell.I emuwhere to find the Inferno file tree by passing it the.CW -r\fIrootpath\f(CWcommand line option. For example.P1emu -r/usr/john/inferno.P2Without the.CW -roption it will look for the file tree in.CW /usr/infernoon Plan 9 and Unix and, when invoked from the command line on WIndows,the default is.CW \einfernoon the current drive.(The Windows start menu by contrast has already been set to use the right directory by the installation software.).LPWhen using graphics,.I emuwill use a window with a resolution of 640 x 480 pixels by default. To use a larger resolutionyou will need to pass.I emuan option.CW -g\fIXsize\f(CWx\fIYsize\f(CWon the command line. So, for example, to invoke.I emuas above but with a resolution of 1024 x 768 pixels the full command linewould be.P1emu -r/usr/john/inferno -g1024x768.P2When invoked in this way.I emudisplays a command window running the Inferno shell.CW /dis/sh.dis .To avoid typing the command line options each time you invoke.I emuyou can store them in the environment variable.CW EMUwhich is interrogated when.I emuis started and might as well be set along side the.CW PATHenvironment variable if the same configuration options are to be used oneach invocation..P1set EMU="-rd:\eDocuments and Settings\ejohn\einferno -g1024x768".P2for Windows..P1EMU=(-r/usr/john/inferno -g1024x768).P2for Plan 9, and.P1EMU="-r/usr/john/inferno -g1024x768".P2for Unix.An alternative to using the.CW EMUenvironment variable is to place the correct invocation in ascript file (or batch file, for Windows) and invoke that insteadof running.I emudirectly.It is important to note that for Windows the.CW -roption also serves to indicate both the drive and directory on to which the softwarehas been installed. Without a drive letter the system will assume thecurrent 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.P1emu.P2or the appropriate script file,should result in it starting up Inferno's command interpreter.I sh (1),which prompts with a semicolon:.P1; .P2You can add a further option.CW -c1to start up.I emuin amode in which the system compiles a module'sDis operations to native machine instructions when a moduleis loaded.(See the.I emu (1)manual page.) In.I compilemode programs that do significant computation will run much faster.Whether in compiled or interpreted mode you should now have a functionalhosted Inferno system.When Inferno starts the initial.CW /dis/sh.disit reads commands from the file.CW /lib/sh/profilebefore becoming interactive. See the manual pages for the shell.I sh (1)to learn more about tailoring the initial environment..LPThe semicolon is the default shell prompt. From this command windowyou should be able to see the installed Inferno files and directories.P1lc /.P2The command.I lcpresents the contents of its directory argument in columnar fashion to standardoutput in the command window..P1; lc /FreeBSD/     Unixware/    icons/       libkern/     man/         prof/Hp/          acme/        include/     libkeyring/  mkconfig     prog/Inferno/     appl/        keydb/       libmath/     mkfile       services/Irix/        asm/         legal/       libmemdraw/  mkfiles/     tmp/LICENCE      chan/        lib/         libmemlayer/ mnt/         tools/Linux/       dev/         lib9/        libtk/       module/      usr/MacOSX/      dis/         libbio/      licencedb/   n/           utils/NOTICE       doc/         libcrypt/    limbo/       net/         wrap/Nt/          emu/         libdraw/     locale/      nvfs/Plan9/       env/         libfreetype/ mail/        o/Solaris/     fonts/       libinterp/   makemk.sh    os/;.P2Only the files and directories in and below the.I inferno_rootdirectory on the host filesystem are immediately visible to an Inferno process;these files are made visible in the root of the Inferno file namespace.If you wish to import or export filesfrom and to the host filesystem you will need to use tools on yourhost to move them in or out of the Inferno visible portion of your hostfilesystem (see the manual pages.I os (1)and.I cmd (3)for an interface to host commands).(We plan to make such access direct, but the details are still being worked out.)From this point onwards in this paper all file paths not qualified with.I inferno_rootare assumed to be in the Inferno namespace.Files created in the host filesystem will be created with the user id ofthe user that started.I emuand on Unix systems with that user's group id..NHSetting the site's time zone.LPTime zone settings are defined byfiles in the directory.CW /locale .The setting affects only how the time is displayed; the internal representation does not vary.For instance, the file.CW /locale/GMTdefines Greenwich Mean Time,.CW /locale/GB-Eiredefines time zones for Great Britain and the Irish Republic(GMT and British Summer Time), and.CW /locale/US_Easterndefines United StatesEastern Standard Time and Eastern Daylight Time.The time zone settings used by applications are read(by.I daytime (2))from the file.CW /locale/timezone ,which is initially a copy of.CW /locale/GB-Eire .If displaying time as the time in London is adequate, you need change nothing.To set a different time zone for the whole site,copy the appropriate time zone file into.CW /locale/timezone :.P1cp /locale/US_Eastern /locale/timezone.P2To set a different time zone for a user or window,.I bind (1)the file containing the time zone setting over.CW /locale/timezone ,either in the user's profile or in a name space description file:.P1bind /locale/US_Eastern /locale/timezone.P2.NHRunning theWindow Manager

Lines 1–500 of 1423. Load more