diff options
Diffstat (limited to 'release/sysinstall/help')
140 files changed, 14731 insertions, 0 deletions
diff --git a/release/sysinstall/help/XF86.hlp b/release/sysinstall/help/XF86.hlp new file mode 100644 index 0000000..c789eaa --- /dev/null +++ b/release/sysinstall/help/XF86.hlp @@ -0,0 +1,500 @@ +README for XFree86 3.1.1u1 on FreeBSD 2.0.5 +Rich Murphey, David Dawes +20 January 1995 + +1. What and Where is XFree86? +------------------------------ + +XFree86 is a port of X11R6 that supports several versions of Intel- +based Unix. It is derived from X386 1.2, which was the X server +distributed with X11R5. This release consists of many new features +and performance improvements as well as many bug fixes. The release +is available as source patches against the X Consortium X11R6 code, as +well as binary distributions for many architectures. + +See the Copyright Notice (COPYRIGHT.html). + +The sources for XFree86 are available as part of the FreeBSD 2.0.5 +distribution, or by anonymous ftp from: + +ftp.XFree86.org:/pub/XFree86/current +(ftp://ftp.XFree86.org/pub/XFree86/current) + + +Binaries for XFree86 on FreeBSD are also available as part of +2.0.5 or from: + +ftp.XFree86.org:/pub/XFree86/current/binaries/FreeBSD-2.0 +(ftp://ftp.XFree86.org/pub/XFree86/current/binaries/FreeBSD-2.0) + +XFree86.cdrom.com:/pub/XFree86/current/binaries/FreeBSD-2.0 +(ftp://XFree86.cdrom.com/pub/XFree86/current/binaries/FreeBSD-2.0) + +Send email to Rich-Murphey@Rice.edu or XFree86@XFree86.org if you have +comments or suggestions about this file and we'll revise it. + + +2. Installing the Binaries +--------------------------- + +In the FreeBSD 2.0.5 distribution, XFree86 comes in 3 major sections: +"basic" distributions, fonts and servers. At the minimum, you will +need the binaries and libraries from the basic distribution, the +"misc" fonts collection and at least one server. The smallest usable +distribution is around 9MB. + +If you can't decide what to pick and you have 52Mb of disk +space, it's safe to unpack everything. + +What follows is a description of the various distribution files +comprising XFree86. If you are installing this as part of FreeBSD +2.0.5 then there's no need to use these files directly: You may +simply check the desired components off the installation menus +provided for that purpose. If you're installing this manually, +then the following information should prove useful: + + Required (6.7Mb): + + X311bin.tgz + all the executable X client applications and shared libs + + X311fnts.tgz + the misc and 75 dpi fonts + + X311lib.tgz + data files needed at runtime + + + Required unless you have already customized your configuration + files: + + X311xicf.tgz + customizable xinit runtime configuration file + + X311xdcf.tgz + customizable xdm runtime configuration file + + Choose at least one server ( 2.3Mb): + + X3118514.tgz + 8-bit color for IBM 8514 and true compatibles. + + X311AGX.tgz + 8-bit color for AGX boards. + + X311Mch3.tgz + 8 and 16-bit color for ATI Mach32 boards. + + X311Mch8.tgz + 8-bit color for ATI Mach8 boards. + + X311Mono.tgz + 1-bit monochrome for VGA, Super-VGA, Hercules, and others. + + X311P9K.tgz + 8, 16, and 24-bit color for Weitek P9000 boards (Diamond + Viper). + + X311S3.tgz + 8, 16 and 24-bit color for S3 boards (#9 GXE, Actix GE32, + SPEA Mercury, STB Pegasus) + + X311SVGA.tgz + 8-bit color for Super-VGA cards. + + X311VG16.tgz + 4-bit color for VGA and Super-VGA cards + + X311W32.tgz + 8-bit Color for ET4000/W32, /W32i and /W32p cards. + + X311nest.tgz + A nested server running as a client window on another + display. + + Optional: + + X311doc.tgz + (.5Mb) READMEs and XFree86 specific man pages + + X311man.tgz + (1.7Mb) man pages except XFree86 specific ones in etc archive + + X311f100.tgz + (1.8Mb) 100dpi fonts + + X311fscl.tgz + (1.6Mb) Speedo and Type1 fonts + + X311fnon.tgz + (3.3Mb) Japanese, Chinese and other non-English fonts + + X311fsrv.tgz + (.3Mb) the font server and it's man page + + X311prog.tgz + (3.9Mb) config, lib*.a and *.h files needed only for + compiling + + X311link.tgz + (7.8Mb) X server reconfiguration kit + + X311pex.tgz + (.5Mb) PEX fonts and shared libs needed by PEX applications. + + X311lbx.tgz + (.2Mb) low bandwidth X proxy server and libraries. + +Note that there is no longer a separate xdm archive. FreeBSD 2.0 +and later handles this in shared libraries now, so that the xdm +binary does not itself contain des and there is no more need for +us to provide separate tar balls. + + +2.1. Full Install: +------------------- + +[ Note: Unless you're installing XFree86 3.1.1u1 manually, that is + to say not as part of the FreeBSD 2.0.5 installation, you may skip + to section 2.3 ] + + 1. You must be logged in as root to unpack the archives because + several executables are set-user-id. Otherwise the server may + abort if you unpack it as an ordinary user. You must also use a + ``umask'' value of 022 because the X server requires special + permissions. + + % su + # umask 022 + + + 2. If you have 52Mb free in the /usr partition ``cd /usr'' and skip + to no. 3. Otherwise, create a directory on another partition + and sym link it into /usr: + + # cd /usr/local + # mkdir X11R6 + # ln -s /usr/local/X11R6 /usr/X11R6 + + + 3. Unpack everything: + + If you are using sh (as root usually does): + + # for i in X311*.tgz; do + # tar -xzf $i + # done + + + Else, if you are using csh: + + % foreach i (X311*.tgz) + % tar -xzf $i + % end + + + 4. Create a symbolic link ``X'' that points to the server that + matches your video card. The XF86_* man pages list which vga + chip sets are supported by each server. For example, if you + have an ET4000 based card you will use the XF86_SVGA server: + + # cd /usr/X11R6/bin; rm X; ln -s XF86_SVGA X + + +2.2. Minimal Install: +---------------------- + +First do numbers 1 and 2 above. Then unpack the required archives: + + # for i in bin fnts lib xicf; do + # tar -xzf X311$i.tgz + # done + + +Then unpack a server archive corresponding to your vga card. The +server man pages, X11R6/man/man1/XF86_*, list the vga chip sets +supported by each server. For example, if you have an ET4000 based +card you will use the XF86_SVGA server: + + # tar -xzf X311SVGA.tgz + # cd /usr/X11R6/bin; rm X; ln -s XF86_SVGA X + + +2.3. After either Full or Minimal Install above: +------------------------------------------------- + +Add /usr/X11R6/bin to the default path for sh in /etc/profile and for +csh in /etc/csh.login if they are not already there: + + # echo 'set path = ($path /usr/X11R6/bin)' >>/etc/csh.login + # echo 'PATH=$PATH:/usr/X11R6/bin' >>/etc/profile + + +Or make sure all who use X put /usr/X11R6/bin in their shell's +``path'' variable. + +Next either reboot or invoke ldconfig as root to put the shared +libraries in ld.so's cache: + + # ldconfig /usr/lib /usr/local/lib /usr/X11R6/lib + + +If you had already configured X11R6/lib/X11/xinit/xinitrc or +X11R6/lib/X11/xdm/* omit the xinit-config or xdm-config archive or +unpack it separately and merge in your customizations. + +The fscl and f100 archives are optional and can be omitted if you are +short on space. The optional link archive allows you to reconfigure +and customize a X server binary. The optional prog archive is needed +only for writing or compiling X applications. The optional pex +archive contains pex clients and libraries for building 3D graphics +applications. + + NOTE: You don't need to uncompress the font files, but if + you uncompress them anyway you must run mkfontdir in the + corresponding font directory; otherwise your server will + abort with the message ``could not open default font + 'fixed'''. + + +3. Installing The Display Manager (xdm) +---------------------------------------- + +The display manager makes your PC look like an X terminal. That is, +it presents you with a login screen that runs under X. + +The easiest way to automatically start the display manager on boot is +to add a line in /etc/ttys to start it on one of the unoccupied +virtual terminals: + + ttyv4 "/usr/X11R6/bin/xdm -nodaemon" xterm on secure + +You should also make sure that /usr/X11R6/bin/X is a symbolic link to +the Xserver that matches your video card or edit the file Xservers in +/usr/X11R6/lib/X11/xdm to specify the pathname of the X server. + +The change to /etc/ttys won't take effect until you either reboot or +``kill -HUP 1'' to force initd to reread /etc/ttys. You can also test +the display manager manually by loging in as root on the console and +typing ``xdm -nodaemon''. + + +4. Configuring X for Your Hardware +----------------------------------- + +The XF86Config file tells the X server what kind of monitor, video +card and mouse you have. You must create it to tell the server what +specific hardware you have. + +XFree86 3.1 uses a new configuration file format. Consult the +XF86Config man page and the general INSTALL (INSTALL.html) file for +instructions. + +If you have a Xconfig file for XFree86 2.x, use reconfig to translate +part of it into the new format: + + # reconfig <Xconfig >XF86Config + +and complete the rest according to the XF86Config man page and the +XF86Config.sample file as a template. + +In order to protect your hardware from damage, the server no longer +will read XF86Config files from a user's home directory, but requires +that it be in /etc/XF86Config, /usr/X11R6/lib/X11/XF86Config.hostname +or /usr/X11R6/lib/X11/XF86Config. + +You'll need info on your hardware: + + o Your mouse type, baud rate and it's /dev entry. + + o The video card's chipset (e.g. ET4000, S3, etc). + + o Your monitor's sync frequencies. + +The easiest way to find which device your mouse is plugged into is to +use ``cat'' or ``kermit'' to look at the output of the mouse. Connect +to it and just make sure that it generates output when the mouse is +moved or clicked: + + % cat < /dev/cuaa0 + +If you can't find the right mouse device then use ``dmesg|grep sio'' +to get a list of devices that were detected upon booting: + + % dmesg|grep sio + sio0 at 0x3f8-0x3ff irq 4 on isa + +Then double check the /dev entries corresponding to these devices. +Use the script /dev/MAKEDEV to create entries if they don't already +exist: + + % cd /dev + % sh MAKEDEV cuaa0 + +If you plan to fine tune the screen size or position on your monitor +you'll need the specs for sync frequencies from your monitor's manual. + + +5. Running X +------------- + +8mb of memory is a recommended minimum for running X. The server, +window manager, display manager and an xterm take about 8Mb of virtual +memory themselves. Even if their resident set size is smaller, on a +8Mb system that leaves very space for other applications such as gcc +that expect a few meg free. The R6 X servers may work with 4Mb of +memory, but in practice compilation while running X can take 5 or 10 +times as long due to constant paging. + +The easiest way for new users to start X windows is to type ``startx +>& startx.log''. Error messages are lost unless you redirect them +because the server takes over the screen. + +To get out of X windows, type: ``exit'' in the console xterm. You can +customize your X by creating .xinitrc, .xserverrc, and .twmrc files in +your home directory as described in the xinit and startx man pages. + + +6. Rebuilding Kernels for X +---------------------------- + +The GENERIC FreeBSD 2.0 kernel supports XFree86 without any +modifications required. You do not need to make any changes to the +GENERIC kernel or any kernel configuration which is a superset. + +For a general description of BSD kernel configuration get +smm.02.config.ps.Z +(ftp://gatekeeper.dec.com/pub/BSD/manuals/smm.02.config.ps.Z). It is +a ready-to-print postscript copy of the kernel configuration chapter +from the system maintainers manual. + +If you do decide to reduce your kernel configuration file, do not +remove the two lines below (in /sys/arch/i386/conf). They are both +required for X support: + + options XSERVER #Xserver + options UCONSOLE #X Console support + +The generic FreeBSD 2.0 kernel is configured by default with the +syscons driver. To configure your kernel similarly it should have a +line like this in /usr/src/sys/i386/conf/GENERIC: + + device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr + +The maximum number of virtual consoles can be set using the MAXCONS +option: + + options "MAXCONS=4" #4 virtual consoles + + +Otherwise, the default without a line like this is 12. You must have +more VTs than gettys as described in the end of section 3, and 4 is a +reasonable minimum. + +The server supports several console drivers: pccons, syscons and pcvt. +The syscons driver is the default in FreeBSD 1.1.5 and higher. They +are detected at runtime and no configuration of the server itself is +required. + +The pcvt console driver is bundled into FreeBSD and may be enabled +by changing the `sc0' line in your kernel configuration file to +`vt0'. See /sys/i386/conf/LINT for more details. + +The XFree86 servers include support for the MIT-SHM extension. The +GENERIC kernel does not support this, so if you want to make use of +this, you will need a kernel configured with SYSV shared memory +support. To do this, add the following line to your kernel config +file: + + options SYSVSHM # System V shared memory + options SYSVSEM # System V semaphores + options SYSVMSG # System V message queues + + +If you are using a SoundBlaster 16 on IRQ 2 (9), then you need a patch +for sb16_dsp.c. Otherwise a kernel configured with the SoundBlaster +driver will claim interrupt 9 doesn't exist and X server will lock up. + +S3 cards and serial port COM 4 cannot be installed together on a +system because the I/O port addresses overlap. + + +7. Rebuilding XFree86 +---------------------- + +The server link kit allows you to build an X server using a minimum +amount of disk space. Just unpack it, make the appropriate changes to +site.def, type ``./mkmf' and ``make'' to link the server. See +README.LinkKit (LinkKit.html) for more info. + +The source tree takes about 114Mb before compiling and an additional +100Mb after ``make World''. You should configure the distribution by +editing xf86site.def and site.def in xc/config/cf before compiling. +By default, the config files are set up to build shared libraries. If +you are running a version of FreeBSD that doesn't include shared +library support, add the following line to site.def: + + #define BuildBsdSharedLibs NO + +If your system doesn't have support or SYSV shared memory (for +example, if you don't have the <sys/shm.h> header), you should disable +the MIT-SHM extension by adding the following line to site.def: + + #define HasShm NO + +To compile the sources on FreeBSD 1.1 and later, type: + + make World + + +8. Building Other X Clients +---------------------------- + +The easiest way to build a new client (X application) is to use xmkmf +if an Imakefile is included with it. Type ``xmkmf -a'' to create the +Makefiles, then type ``make''. Whenever you install additional man +pages you should update whatis.db by running ``makewhatis +/usr/X11R6/man''. + +Note: Starting with XFree86 2.1 and FreeBSD 1.1, the symbol __386BSD__ +no longer gets defined either by the compiler or via the X config +files for FreeBSD systems. When porting clients to BSD systems, make +use of the symbol BSD for code which is truly BSD-specific. The value +of the symbol can be used to distinguish different BSD releases. For +example, code specific to the Net-2 and later releases can use: + + #if (BSD >= 199103) + +To ensure that this symbol is correctly defined, include <sys/param.h> +in the source that requires it. Note that the symbol CSRG_BASED is +defined for *BSD systems in XFree86 3.1.1 and later. This should be +used to protect the inclusion of <sys/param.h>. + +For code that really is specific to a particular i386 BSD port, use +__FreeBSD__ for FreeBSD, __NetBSD__ for NetBSD, __386BSD__ for 386BSD, +and __bsdi__ for BSD/386. + + +9. Thanks +---------- + +Many thanks to: + + o Pace Willison for providing initial *BSD support. + + o Amancio Hasty for 386BSD kernel and S3 chipset support. + + o David Greenman, Nate Williams, Jordan Hubbard for FreeBSD kernel + support. + + o Rod Grimes, Jordan Hubbard and Jack Velte for the use of Walnut + Creek Cdrom's hardware. + + o Orest Zborowski, Simon Cooper and Dirk Hohndel for ideas from + the Linux distribution. + +$XConsortium: FreeBSD.sgml,v 1.3 95/01/23 15:34:41 kaleb Exp $ +Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/FreeBSD.sgml,v 3.10 1995/01/28 16:01:28 dawes Exp $ + + +$XFree86: xc/programs/Xserver/hw/xfree86/doc/READ.FreeBSD,v 3.12 1995/01/28 16:19:37 dawes Exp $ diff --git a/release/sysinstall/help/configure.hlp b/release/sysinstall/help/configure.hlp new file mode 100644 index 0000000..49980d4 --- /dev/null +++ b/release/sysinstall/help/configure.hlp @@ -0,0 +1,14 @@ +This menu allows you to configure your system after the installation +process is complete. At the minimum, you should probably set the +system manager's password and the system time zone. + +For extra goodies like bash, emacs, pascal, etc., you should look at +the Packages item in this menu. Currently, the Packages option is +only useful if you have a CDROM or an existing packages collection +somewhere in the file system hierarchy where the package management +tool can locate it. The automatic transfer of packages via FTP is not +yet supported! + +For setting the timezone after the system is installed, type +``tzsetup''. For more information on the general system +configuration, see the ``/etc/sysconfig'' file. diff --git a/release/sysinstall/help/da_DK.ISO8859-1/README b/release/sysinstall/help/da_DK.ISO8859-1/README new file mode 100644 index 0000000..42b16ae --- /dev/null +++ b/release/sysinstall/help/da_DK.ISO8859-1/README @@ -0,0 +1,98 @@ + ------------------------------------------- + FreeBSD 2.0.5 --- RELEASE Versionen , , + ------------------------------------------- /( )` + \ \___ / | +Velkommen til 2.0.5 releasen af FreeBSD. 2.0.5 er /- _ `-/ ' +en mellem release af FreeBSD, der udfylder det (/\/ \ \ /\ +tidsmæssigt store hul mellem 2.0R (fra november / / | ` \ +'94) og 2.1R, som kommer i slutningen af juli O O ) / | +'95. FreeBSD 2.0.5 indeholder mange væsentlige `-^--'`< ' +forbedringer i forhold til 2.0R. 2.0.5 er (_.) _ ) / +væsentligt mere stabil, indeholder adskillige `.___/` / +nye ting, og har et væsentligt forbedret `-----' / +installationsprogram. Release noterne <----. __ / __ \ +indeholder flere detaljer om nyhederne <----|====O)))==) \) /==== +i FreeBSD 2.0.5! <----' `--' `.__,' \ + | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +Hvad er FreeBSD? FreeBSD er et operativsystem baseret på 4.4 BSD Lite, +og kører på Intel, Cyrix eller NexGen "x86" baseret PC hardware. FreeBSD +understøtter en bred vifte af PC udstyr og PC konfigurationer. Det kan +bruges til alt fra softwareudvikling til at udbyde Internet opkobling. +Den travleste maskine på nettet - ftp.cdrom.com - er en FreeBSD maskine. + +Denne release af FreeBSD indeholder alt, hvad du behøver for at lave et +sådant system, samt fuld kildetekst til det hele. Med kildeteksten +installeret kan du bogstaveligt talt rekompilere hele systemet fra bunden +med een komando. Dette er ideelt for studerende, forskere samt folk, der +blot ønsker at se, hvordan det hele hænger sammen. + +En stor samling tredje parts software (kaldet "the ports collection") +medfølger ligeledes, således at det er enkelt for dig at få og installere +alle dine favorit UNIX programmer sammen med FreeBSD. Over 270 programmer +fra editorer over programmeringssprog til grafikprogrammer gør FreeBSD til +et stærkt og altomfattende system, der ligger på linje med mange store +workstations med hensyn til brugbarhed og styrke. + + +Hvis du ønsker mere dokumentation til systemet, vil vi anbefale, at du +køber 4.4BSD dokumentationen ("the 4.4BSD Document Set") fra O'Reilly +Associates og USENIX Association (ISBN 1-56592-082-1). Vi har ingen +forbindelse til O'Reilly, vi er blot tilfredse kunder! + +Det vil være en god ide at læse hardware guiden *før* du fortsætter med +installationen. At konfigurere en PC til at køre andet end DOS/Windows +(som egentlig ikke stiller nogen særlige krav til den underliggende +hardware), er i praksis væsentligt sværere end det ser ud til, og hvis du +mener at forstå PCere, så har du tydeligvis ikke anvendt dem længe nok :-) +Denne guide vil give dig nogle tips til at konfigurere din hardware, og +hvilke symptomer du skal holde øje med i tilfælde af problemer. Guiden +er tilgængelig i dokumentations menuen på FreeBSD boot disketten. + +BEMÆRK: Selvom gruppen bag FreeBSD har gjort sit bedste for at forhindre +datatab, så er der stadig en reel mulighed for at DU KOMMER TIL AT SLETTE +HELE DIN HARDDISK under installationen. Lad være med at fortsætte til den +endelige FreeBSD installations-menu medmindre at du har lavet en sikkerheds- +kopi af alle vigtige data (det er også en god ide at check-læse sikkerheds- +kopien). Dette er ikke for sjov, vi er dybt seriøse på dette punkt. + +Tekniske kommentarer til denne release sendes (på engelsk!) til: + + hackers@FreeBSD.org + + +Fejl-rapporter bør sendes ved hjælp af `send-pr' kommandoen, hvis du fik +installeret systemet. Ellers sendes de (ligeledes på engelsk) til: + + bugs@FreeBSD.org + +Husk at gøre opmærksom på HVILKEN VERSION af FreeBSD du kører i alle fejl- +rapporter. + +Generelle spørgsmål kan (på engelsk) sendes til: + + questions@FreeBSD.org + +Vær venligst tålmodig, hvis dine spørgsmål ikke bliver besvaret umiddelbart. +Dette er en specielt travl tid for os, og alle vores (frivillige) resourcer +bliver udnyttet til grænsen. Alle fejl-rapporter, der bliver sendt med +send-pr kommandoen, bliver logget og holdt øje med i vores fejl database, +og du vil blive holdt informeret om alle ændringer af status for fejlen +gennem hele fejlens levetid. Det samme gælder for ønsker om forbedringer. + +Vores WEB adresse - http://www.freebsd.org - er ligeledes et godt sted at +kigge efter opdateret information, og giver flere faciliteter for avanceret +dokumentation. Du kan benytte BSDI versionen af Netscape til at køre World +Wide Web direkte fra FreeBSD. + +Du kan også kigge i /usr/share/FAQ og /usr/share/doc efter yderligere +information om systemet. + + +Tak for at du tog dig tid til at læse alt dette. Vi håber oprigtigt at +du får glæde af denne release af FreeBSD! diff --git a/release/sysinstall/help/da_DK.ISO8859-1/configure.hlp b/release/sysinstall/help/da_DK.ISO8859-1/configure.hlp new file mode 100644 index 0000000..b698b6d --- /dev/null +++ b/release/sysinstall/help/da_DK.ISO8859-1/configure.hlp @@ -0,0 +1,16 @@ +Denne menu lader dig foretage små ændringer af konfigurationen, +efter at systemet er installeret. Som et minimum bør du sætte +password'et for system operatøren og systemets tidszone. + +For at installere ekstra software såsom bash, emacs, pascal etc. +bør du kigge i Packages objektet i denne menu. Bemærk at for +nærværende er dette kun reelt nyttigt, hvis du har en CD-ROM eller +en eksisterende pakke samling et sted i dit filsystem, hvor pakke +administrator programmet kan se den. Automatisk overførsel af +pakker via FTP er endnu ikke supporteret. + +Hvis du ønsker at bruge pakke installations programmet efter at +du har forladt system installationen, så hedder kommandoen +``pkg_manage''. Hvis du vil sætte tidszonen - tast ``tzsetup''. +Se ``/etc/sysconfig'' filen for mere information om den generelle +system konfiguration. diff --git a/release/sysinstall/help/da_DK.ISO8859-1/language.hlp b/release/sysinstall/help/da_DK.ISO8859-1/language.hlp new file mode 100644 index 0000000..e7464c6 --- /dev/null +++ b/release/sysinstall/help/da_DK.ISO8859-1/language.hlp @@ -0,0 +1,13 @@ +Benyt denne menu til at vælge dit foretrukne sprog. For nærværende +vil dette kun sætte default sproget, for de forskellige hjælpefiler +der vises. + +I senere udgaver vil dette også ændre opsætningen/udlægningen af +tastaturet, skærm karakter-sæt, NLS opsætning (sysinstall vil selv +benytte tekst kataloger, således at alle menuer er på det ønskede sprog) +og implementere andre I18N funktioner for at imødekomme diverse standarder. + +Indtil disse forbedringer er lavet, vil du sikkert finde, at det er lettere +at ændre /etc/sysconfig filen i hånden, når systemet er fuldt installeret. +Der er kommentarer i filen, som beskriver præsis, hvad der skal ændres, samt +eksempler på enkelte eksisterende ikke engelske opsætninger. diff --git a/release/sysinstall/help/da_DK.ISO8859-1/usage.hlp b/release/sysinstall/help/da_DK.ISO8859-1/usage.hlp new file mode 100644 index 0000000..fd242f1 --- /dev/null +++ b/release/sysinstall/help/da_DK.ISO8859-1/usage.hlp @@ -0,0 +1,56 @@ +BRUG AF DETTE SYSTEM +==================== + +TAST FUNKTION +---- -------- +PIL OP Flyt til foregående objekt (eller op, i et tekstfelt). +PIL NED Flyt til næste objekt (eller ned, i et tekstfelt). +TAB Flyt til næste objekt eller gruppe. +HØJRE PIL Flyt til næste objekt eller gruppe (det samme som TAB). +SHIFT-TAB Flyt til foregående objekt eller gruppe. +VENSTRE PIL Flyt til foregående objekt eller gruppe (det samme som + SHIFT-TAB). +RETUR Vælg objekt. +PAGE UP Gå en side op, i et tekstfelt. +PAGE DOWN Gå en side ned, i et tekstfelt. +MELLEMRUM I en "radio" eller flervalgs menu, skift status for det + nuværende objekt. +F1 Hjælp (i skærme, der har denne funktionalitet). + +Hvis du også ser små "^(-)" eller "v(+)" symboler i kanten af en menu, betyder +det, at der er flere linjer ovenover eller nedenunder de nuværende, som ikke +vises (fordi der ikke er nok plads på skærmen). Ved hjælp af pil-op og pil-ned +kan menuen rulles op og ned. Når et af symbolerne forsvinder, betyder det at +du er i toppen (eller bunden) af menuen. + +I tekstfelter vil mængden af tekst over den nuværende position blive vist som +en procentdel i det nedre højre hjørne. 100% betyder at du er i bunden af +feltet. + +Valg af OK i en menu vil vælge/bekræfte det som menuen omhandler. +Valg af Cancel vil afbryde en operation, og generelt returnere dig til den +foregående menu. + + +SPECIAL-FUNKTIONER +================== + +Det er muligt at vælge et objekt i en menu ved at taste den første karakter +af navnet (hvis unikt). Disse "accelerator" karakterer vil være specielt +fremhævet i objekt navnet. + +Konsol driveren indeholder en buffer, der gør det muligt at bladre tilbage +og se information, der er rullet op over toppen af skærmen. For at aktivere +denne funktion, tryk på "Scroll Lock" tasten og brug piletasterne eller +Page Up/Page Down tasterne til at bladre gennem den gemte tekst. Funktionen +forlades ved igen at trykke på "Scroll Lock" tasten. Denne funktion er mest +brugbar i forbindelse med sub-shells og andre specialfunktioner, der ikke +bruger menuer. + +Når systemet er fuldt installeret og kører i "multi-user" tilstand, vil du +bemærke, at du har flere "virtuelle konsoller", der kan benyttes til at have +flere aktive sessioner samtidigt. Brug ALT-F<n> til at skifte mellem dem +(hvor `F<n>' er den funktionstast, der svarer til den skærm, som du ønsker +at se). Systemet er standard installeret med 3 virtuelle konsoller. Du kan +lave flere ved at editere /etc/ttys filen når systemet er oppe (maximum er +12). diff --git a/release/sysinstall/help/da_DK.ISO_8859-1/README b/release/sysinstall/help/da_DK.ISO_8859-1/README new file mode 100644 index 0000000..42b16ae --- /dev/null +++ b/release/sysinstall/help/da_DK.ISO_8859-1/README @@ -0,0 +1,98 @@ + ------------------------------------------- + FreeBSD 2.0.5 --- RELEASE Versionen , , + ------------------------------------------- /( )` + \ \___ / | +Velkommen til 2.0.5 releasen af FreeBSD. 2.0.5 er /- _ `-/ ' +en mellem release af FreeBSD, der udfylder det (/\/ \ \ /\ +tidsmæssigt store hul mellem 2.0R (fra november / / | ` \ +'94) og 2.1R, som kommer i slutningen af juli O O ) / | +'95. FreeBSD 2.0.5 indeholder mange væsentlige `-^--'`< ' +forbedringer i forhold til 2.0R. 2.0.5 er (_.) _ ) / +væsentligt mere stabil, indeholder adskillige `.___/` / +nye ting, og har et væsentligt forbedret `-----' / +installationsprogram. Release noterne <----. __ / __ \ +indeholder flere detaljer om nyhederne <----|====O)))==) \) /==== +i FreeBSD 2.0.5! <----' `--' `.__,' \ + | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +Hvad er FreeBSD? FreeBSD er et operativsystem baseret på 4.4 BSD Lite, +og kører på Intel, Cyrix eller NexGen "x86" baseret PC hardware. FreeBSD +understøtter en bred vifte af PC udstyr og PC konfigurationer. Det kan +bruges til alt fra softwareudvikling til at udbyde Internet opkobling. +Den travleste maskine på nettet - ftp.cdrom.com - er en FreeBSD maskine. + +Denne release af FreeBSD indeholder alt, hvad du behøver for at lave et +sådant system, samt fuld kildetekst til det hele. Med kildeteksten +installeret kan du bogstaveligt talt rekompilere hele systemet fra bunden +med een komando. Dette er ideelt for studerende, forskere samt folk, der +blot ønsker at se, hvordan det hele hænger sammen. + +En stor samling tredje parts software (kaldet "the ports collection") +medfølger ligeledes, således at det er enkelt for dig at få og installere +alle dine favorit UNIX programmer sammen med FreeBSD. Over 270 programmer +fra editorer over programmeringssprog til grafikprogrammer gør FreeBSD til +et stærkt og altomfattende system, der ligger på linje med mange store +workstations med hensyn til brugbarhed og styrke. + + +Hvis du ønsker mere dokumentation til systemet, vil vi anbefale, at du +køber 4.4BSD dokumentationen ("the 4.4BSD Document Set") fra O'Reilly +Associates og USENIX Association (ISBN 1-56592-082-1). Vi har ingen +forbindelse til O'Reilly, vi er blot tilfredse kunder! + +Det vil være en god ide at læse hardware guiden *før* du fortsætter med +installationen. At konfigurere en PC til at køre andet end DOS/Windows +(som egentlig ikke stiller nogen særlige krav til den underliggende +hardware), er i praksis væsentligt sværere end det ser ud til, og hvis du +mener at forstå PCere, så har du tydeligvis ikke anvendt dem længe nok :-) +Denne guide vil give dig nogle tips til at konfigurere din hardware, og +hvilke symptomer du skal holde øje med i tilfælde af problemer. Guiden +er tilgængelig i dokumentations menuen på FreeBSD boot disketten. + +BEMÆRK: Selvom gruppen bag FreeBSD har gjort sit bedste for at forhindre +datatab, så er der stadig en reel mulighed for at DU KOMMER TIL AT SLETTE +HELE DIN HARDDISK under installationen. Lad være med at fortsætte til den +endelige FreeBSD installations-menu medmindre at du har lavet en sikkerheds- +kopi af alle vigtige data (det er også en god ide at check-læse sikkerheds- +kopien). Dette er ikke for sjov, vi er dybt seriøse på dette punkt. + +Tekniske kommentarer til denne release sendes (på engelsk!) til: + + hackers@FreeBSD.org + + +Fejl-rapporter bør sendes ved hjælp af `send-pr' kommandoen, hvis du fik +installeret systemet. Ellers sendes de (ligeledes på engelsk) til: + + bugs@FreeBSD.org + +Husk at gøre opmærksom på HVILKEN VERSION af FreeBSD du kører i alle fejl- +rapporter. + +Generelle spørgsmål kan (på engelsk) sendes til: + + questions@FreeBSD.org + +Vær venligst tålmodig, hvis dine spørgsmål ikke bliver besvaret umiddelbart. +Dette er en specielt travl tid for os, og alle vores (frivillige) resourcer +bliver udnyttet til grænsen. Alle fejl-rapporter, der bliver sendt med +send-pr kommandoen, bliver logget og holdt øje med i vores fejl database, +og du vil blive holdt informeret om alle ændringer af status for fejlen +gennem hele fejlens levetid. Det samme gælder for ønsker om forbedringer. + +Vores WEB adresse - http://www.freebsd.org - er ligeledes et godt sted at +kigge efter opdateret information, og giver flere faciliteter for avanceret +dokumentation. Du kan benytte BSDI versionen af Netscape til at køre World +Wide Web direkte fra FreeBSD. + +Du kan også kigge i /usr/share/FAQ og /usr/share/doc efter yderligere +information om systemet. + + +Tak for at du tog dig tid til at læse alt dette. Vi håber oprigtigt at +du får glæde af denne release af FreeBSD! diff --git a/release/sysinstall/help/da_DK.ISO_8859-1/configure.hlp b/release/sysinstall/help/da_DK.ISO_8859-1/configure.hlp new file mode 100644 index 0000000..b698b6d --- /dev/null +++ b/release/sysinstall/help/da_DK.ISO_8859-1/configure.hlp @@ -0,0 +1,16 @@ +Denne menu lader dig foretage små ændringer af konfigurationen, +efter at systemet er installeret. Som et minimum bør du sætte +password'et for system operatøren og systemets tidszone. + +For at installere ekstra software såsom bash, emacs, pascal etc. +bør du kigge i Packages objektet i denne menu. Bemærk at for +nærværende er dette kun reelt nyttigt, hvis du har en CD-ROM eller +en eksisterende pakke samling et sted i dit filsystem, hvor pakke +administrator programmet kan se den. Automatisk overførsel af +pakker via FTP er endnu ikke supporteret. + +Hvis du ønsker at bruge pakke installations programmet efter at +du har forladt system installationen, så hedder kommandoen +``pkg_manage''. Hvis du vil sætte tidszonen - tast ``tzsetup''. +Se ``/etc/sysconfig'' filen for mere information om den generelle +system konfiguration. diff --git a/release/sysinstall/help/da_DK.ISO_8859-1/language.hlp b/release/sysinstall/help/da_DK.ISO_8859-1/language.hlp new file mode 100644 index 0000000..e7464c6 --- /dev/null +++ b/release/sysinstall/help/da_DK.ISO_8859-1/language.hlp @@ -0,0 +1,13 @@ +Benyt denne menu til at vælge dit foretrukne sprog. For nærværende +vil dette kun sætte default sproget, for de forskellige hjælpefiler +der vises. + +I senere udgaver vil dette også ændre opsætningen/udlægningen af +tastaturet, skærm karakter-sæt, NLS opsætning (sysinstall vil selv +benytte tekst kataloger, således at alle menuer er på det ønskede sprog) +og implementere andre I18N funktioner for at imødekomme diverse standarder. + +Indtil disse forbedringer er lavet, vil du sikkert finde, at det er lettere +at ændre /etc/sysconfig filen i hånden, når systemet er fuldt installeret. +Der er kommentarer i filen, som beskriver præsis, hvad der skal ændres, samt +eksempler på enkelte eksisterende ikke engelske opsætninger. diff --git a/release/sysinstall/help/da_DK.ISO_8859-1/usage.hlp b/release/sysinstall/help/da_DK.ISO_8859-1/usage.hlp new file mode 100644 index 0000000..fd242f1 --- /dev/null +++ b/release/sysinstall/help/da_DK.ISO_8859-1/usage.hlp @@ -0,0 +1,56 @@ +BRUG AF DETTE SYSTEM +==================== + +TAST FUNKTION +---- -------- +PIL OP Flyt til foregående objekt (eller op, i et tekstfelt). +PIL NED Flyt til næste objekt (eller ned, i et tekstfelt). +TAB Flyt til næste objekt eller gruppe. +HØJRE PIL Flyt til næste objekt eller gruppe (det samme som TAB). +SHIFT-TAB Flyt til foregående objekt eller gruppe. +VENSTRE PIL Flyt til foregående objekt eller gruppe (det samme som + SHIFT-TAB). +RETUR Vælg objekt. +PAGE UP Gå en side op, i et tekstfelt. +PAGE DOWN Gå en side ned, i et tekstfelt. +MELLEMRUM I en "radio" eller flervalgs menu, skift status for det + nuværende objekt. +F1 Hjælp (i skærme, der har denne funktionalitet). + +Hvis du også ser små "^(-)" eller "v(+)" symboler i kanten af en menu, betyder +det, at der er flere linjer ovenover eller nedenunder de nuværende, som ikke +vises (fordi der ikke er nok plads på skærmen). Ved hjælp af pil-op og pil-ned +kan menuen rulles op og ned. Når et af symbolerne forsvinder, betyder det at +du er i toppen (eller bunden) af menuen. + +I tekstfelter vil mængden af tekst over den nuværende position blive vist som +en procentdel i det nedre højre hjørne. 100% betyder at du er i bunden af +feltet. + +Valg af OK i en menu vil vælge/bekræfte det som menuen omhandler. +Valg af Cancel vil afbryde en operation, og generelt returnere dig til den +foregående menu. + + +SPECIAL-FUNKTIONER +================== + +Det er muligt at vælge et objekt i en menu ved at taste den første karakter +af navnet (hvis unikt). Disse "accelerator" karakterer vil være specielt +fremhævet i objekt navnet. + +Konsol driveren indeholder en buffer, der gør det muligt at bladre tilbage +og se information, der er rullet op over toppen af skærmen. For at aktivere +denne funktion, tryk på "Scroll Lock" tasten og brug piletasterne eller +Page Up/Page Down tasterne til at bladre gennem den gemte tekst. Funktionen +forlades ved igen at trykke på "Scroll Lock" tasten. Denne funktion er mest +brugbar i forbindelse med sub-shells og andre specialfunktioner, der ikke +bruger menuer. + +Når systemet er fuldt installeret og kører i "multi-user" tilstand, vil du +bemærke, at du har flere "virtuelle konsoller", der kan benyttes til at have +flere aktive sessioner samtidigt. Brug ALT-F<n> til at skifte mellem dem +(hvor `F<n>' er den funktionstast, der svarer til den skærm, som du ønsker +at se). Systemet er standard installeret med 3 virtuelle konsoller. Du kan +lave flere ved at editere /etc/ttys filen når systemet er oppe (maximum er +12). diff --git a/release/sysinstall/help/de_DE.ISO8859-1/README b/release/sysinstall/help/de_DE.ISO8859-1/README new file mode 100644 index 0000000..8ce9c18 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO8859-1/README @@ -0,0 +1,106 @@ + + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Version , , + ----------------------------------------- /( )` + \ \___ / | +Willkommen zum Release 2.0.5 von FreeBSD, einem /- _ `-/ ' +Zwischen-Release von FreeBSD, das eine eine Lücke (/\/ \ \ /\ +füllt zwischen 2.0R (das im Nov. 94 erschien) und / / | ` \ +2.1R, das Ende Juli '95 erscheinen wird, die oft O O ) / | +beklagt wurde. FreeBSD 2.0.5 enthält wesentliche `-^--'`< ' +Verbesserungen gegenüber 2.0R, deren wichtigste (_.) _ ) / +eine erhöhte Systemstabilität (wesentlich besser), `.___/` / +Dutzende neuer Features und ein stark `-----' / +verbessertes Installationsprogramm <----. __ / __ \ +sind. Die Release Notes enthalten <----|====O)))==) \) /==== +weitere Details bzgl. der Neuheiten <----' `--' `.__,' \ +in FreeBSD 2.0.5. | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + + +Was ist FreeBSD? FreeBSD ist ein 4.4BSD-Lite-basiertes Betriebssystem für +Intel, AMD, Cyrix oder NexGen "x86"-PC-Hardware. Es arbeitet mit einer +großen Anzahl von PC-Peripherie und -Konfigurationen zusammen. Es kann für +die Software-Entwicklung bis hin zum Anbieten von Internet-Diensten +eingesetzt werden; der meist genutzte Rechner im Internet, ftp.cdrom.com, +ist ein FreeBSD-Rechner. + +Dieses FreeBSD-Release enthält alles, was man zur Nutzung eines solchen +Systems braucht; zusätzlich erhält man den kompletten Quellcode. Wenn man +den Quellcode installiert hat, kann man das ganze Betriebssystem von Grund +auf mit einem einzigen Befehl übersetzen; dies eignet es in idealer Weise +für Studenten, Forscher oder einfach Leute, die sehen wollen, wie alles +funktioniert. + +Es gibt ebenfalls eine große Anzahl portierter Dritt-Software (die "ports +collection"), um die Verfügbarkeit und die Installation traditioneller +Lieblings-UNIX-Utilities für FreeBSD zu erleichtern. Über 270 Portierun- +gen, von Editoren über Programmiersprachen bis zu Grafikanwendungen, machen +FreeBSD zu einem mächtigen und umfassenden Betriebssystem, das keinen +Vergleich zu dem großer Workstations scheut. + +Als weitere Dokumentation zu diesem System empfehlen wir die 4.4BSD- +Dokumentation von O'Reilly Associates und der USENIX Association, ISBN +1-56592-082-1. Wir haben nichts mit O'Reilly zu tun, außer daß wir +zufriedene Kunden sind! + +Wir empfehlen, die HARDWARE-ANLEITUNG *vor* jeglicher Fortführung der +Installation zu lesen. PC-Hardware für irgend etwas anderes als DOS/ +Windows (das keine großen Anforderungen an die Hardware stellt) zu +konfigurieren, ist schwieriger, als es zunächst aussieht. Und wenn man +glaubt, PCs zu verstehen, dann hat man diese nur noch nicht lange genug +benutzt. :) Diese Anleitung gibt einige Tips zur Hardwarekonfiguration und +sagt, auf welche Symptome man bei Schwierigkeiten achten muß. Die Anlei- +tung ist im Dokumentations-Menü der FreeBSD-Bootfloppy verfügbar. + +VORBEHALT: Obwohl FreeBSD alles versucht, vorhandene Daten gegen versehent- +lichen Verlust zu schützen, ist es mit dieser Installation mehr als nur +möglich, DIE GESAMTE FESTPLATTE ZU LÖSCHEN! Bitte nicht mit der endgül- +tigen Installation von FreeBSD fortfahren, ohne zuerst alle wichtigen Daten +angemessen gesichert zu haben! Wir empfehlen es eindringlichst! + +Technische Kommentare zu diesem Release sollten an: + + hackers@FreeBSD.org + +gesandt werden (wenn möglich, in englisch). + +Fehlermeldungen sollten bei erfolgreicher Installation mittels des +`send-pr'-Kommandos, ansonsten an: + + bugs@FreeBSD.org + +gesandt werden. + +Bitte in jeder Fehlermeldung die genutzte FreeBSD-VERSION nennen! + +Allgemeine Fragen sollten an: + + questions@FreeBSD.org + +gesandt werden. + +Wir bitten um Geduld, wenn die Fragen nicht sofort beantwortet werden - +dieses sind besonders arbeitsintensive Zeiten für uns, und unsere Resourcen +(auf freiwilliger Basis) sind oft bis an die Grenzen ausgereizt! Mittels +send-pr verschickte Fehlermeldungen werden registriert und in unserer +Datenbank verfolgt. Über Statusänderungen wird über die gesamte Lebensdauer +des Fehlers (oder der Forderung nach einem Feature) informiert. + +Unsere WEB Site, http://www.freebsd.org, ist ebenfalls eine gute Quelle +für neue Informationen und enthält einige weitere, fortführende Infor- +mationen. Man kann die BSDI-Version von Netscape zum Browsen (Blättern) +im World Wide Web direkt aus FreeBSD heraus nutzen. + +Wir empfehlen auch in /usr/share/FAQ und /usr/share/doc zu weiteren +Informationen zum System nachzuschauen. + +Wir danken für die Aufmerksamkeit und hoffen, daß dieses Release von +FreeBSD viel Freude bereitet. + + Jordan Hubbard, + für das FreeBSD Projekt diff --git a/release/sysinstall/help/de_DE.ISO8859-1/RELNOTES b/release/sysinstall/help/de_DE.ISO8859-1/RELNOTES new file mode 100644 index 0000000..c3d2aa6 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO8859-1/RELNOTES @@ -0,0 +1,766 @@ + RELEASE NOTES + FreeBSD + Release 2.0.5 + +1. Technischer Überblick +------------------------ + +FreeBSD ist eine im Quellcode frei verfügbare Version eines 4.4-Lite- +basierten Betriebssystems für PC's auf der Basis von Intel-i386/i486/ +Pentium-Prozessoren (oder kompatiblen). Es basiert hauptsächlich auf +Software der Computer-Gruppe (CSRG) der Universität Kalifornien Berkeley +mit einigen Erweiterungen aus den Systemen NetBSD, 386BSD und von der +Free Software Foundation. + +Seit der Freigabe unserer Version FreeBSD 2.0 vor etwa 8 Monaten hat sich +die Leistungsfähigkeit, der Funktionsumfang und die Stabilität von +FreeBSD dramatisch verbessert. Die umfangreichste Änderung ist das neu +gefaßte System der virtuellen Speicherverwaltung (VM) mit einem vereinig- +ten VM/Dateipuffer, wodurch sich nicht nur die Leistungsfähigkeit verbes- +sert, sondern auch der Mindestspeicherbedarf von FreeBSD reduziert werden +konnte, so daß auch Konfigurationen mit nur 4 MB Hauptspeicher wieder +akzeptabel werden können. Unter den weiteren Verbesserungen befinden +sich volle Unterstützung für NIS sowohl auf Client- als auch Serverseite, +,,Transaction TCP'', PPP mit automatischer Leitungswahl bei Bedarf, ein +verbessertes SCSI-Subsystem, anfängliche ISDN-Unterstützung, Treiber für +FDDI- und "Fast Ethernet"-Adapter (100 MBit/s), verbesserter Unter- +stützung der Adaptec 2940-SCSI-Adapter (sowohl WIDE- als auch +Normal-SCSI) sowie viele hunderte Bugfixes. + +Zuzüglich zur Basis-Distribution bietet FreeBSD nun eine neue Sammlung +portierter Software an mit etwa 270 häufig gewünschten Programmen. Die +Liste der ,,Ports'' reicht dabei von HTTP-(WWW-)Servern, Spielen, Pro- +grammiersprachen, Editoren und so gut wie allem, was dazwischenliegt. +Die komplette Port-Sammlung benötigt nun nur noch 10 MB Speicherplatz, da +alle Ports als ,,Deltas'' gegenüber ihren originalen Quellen ausgedrückt +werden. Das macht es uns einfacher, die Ports auf dem Laufenden zu +halten, und es reduziert gegenüber der Ports-Sammlung aus Version 1.0 +drastisch den Speicherbedarf. Um einen Port zu übersetzen, wechselt man +einfach ins Verzeichnis des gewünschten Ports, tippt ,,make'' ein, und +läßt das System den Rest vornehmen. Es wird dabei automatisch die komp- +lette Original-Quelle von der CDROM oder einem lokalen FTP-Server geholt, +so daß man lediglich hinreichend Plattenplatz benötigt, um die gewünsch- +ten Ports zu übersetzen. (Fast) jeder Port wird auch als vorübersetztes +,,Package'' zur Verfügung gestellt, das man mit einem einfachen Kommando +(pkg_add) installieren kann, wenn man nicht von der originalen Quelle +übersetzen möchte. All dies ist in der Datei + /usr/share/FAQ/Text/ports.FAQ +genauer beschrieben. + +Seit unserer ersten Version FreeBSD 1.0 vor etwa zwei Jahren hat sich +FreeBSD fast vollständig geändert. Eine neue Portierung wurde vorge- +nommen, ausgehend vom 4.4-Lite-Code der Universität Berkeley, womit der +rechtliche Status des Systems einwandfrei geworden ist, einschließlich +einer ,Absegnung' durch Novell (dem neuen Eigentümer der USL und des +Warenzeichens UNIX). Die 4.4-Portierung brachte gleichzeitig eine Menge +neuer Eigenschaften, Dateisysteme und verbesserte Treiber. Mit der +geklärten Rechtslage haben wir nun allen Grund zur Hoffnung, daß wir ohne +künftige juristische Querelen auch weiterhin ein Betriebssystem von guter +Qualität regelmäßig herausgeben können. + +FreeBSD 2.0.5 representiert die zweijährige Arbeit eines internationalen +Entwicklerteams, das viele tausend Mann-Stunden eingebracht hat. Wir +hoffen sehr, daß es Anklang findet! + +Eine Reihe weiterer Dokumente, die während der Installation und im Betrieb +von FreeBSD hilfreich sein können, befindet sich im Verzeichnis ,,FAQ'', +entweder in einem installierten System unter /usr/share/FAQ, oder aber in +der obersten Ebene der CDROM- oder FTP-Distribution, in der ebendiese Datei +zu finden ist. Ein Überblick der im FAQ-Verzeichnis enthaltenen Dokumen- +tation befindet sich in der Datei FAQ/Text/ROADMAP. + +Eine Liste all derjenigen, die zum Projekt beigetragen haben, verbunden +mit einer allgemeinen Beschreibung des Projektes selbst, befindet sich in +der Datei ,,CONTRIB.FreeBSD'' in der Binär-Distribution. + +Die Datei ,,REGISTER.FreeBSD'' enthält eine Beschreibung, wie man sich +beim "Free BSD user counter" registrieren läßt. Dieser Zähler ist für +ALLE freien BSD-Derivate, nicht nur FreeBSD, und wir legen jedem die +Anmeldung dort nahe. + +Die Kerndistribution von FreeBSD enthält keinen DES-Code, weil dies ihren +Export außerhalb der USA verhindern würde. Es existiert ein Zusatzpaket, +das nur in den USA verwendet werden darf und die Programme zusammenfaßt, +die normalerweise DES benutzen. Alle anderen zusätzlich angebotenen +Pakete können von jedermann genutzt werden. Eine freie und (aus Sicht +von außerhalb der USA) exportierbare Distribution für Nicht-US-Benutzer +existiert aber auch. Sie ist in der FreeBSD-FAQ beschrieben. + +Soweit jedoch die Paßwortsicherheit alles ist, was gewünscht wird, und +kein Bedarf besteht, die verschlüsselten Paßwörter zwischen verschiedenen +Architekturen (Sun's, DEC-Maschinen usw.) auszutauschen, ist das von +FreeBSD benutzte, auf einer MD5-Verschlüsselung aufsetzende Sicherheits- +system völlig ausreichend! Wir sind der Meinung, daß unser standard- +mäßiges Sicherheitsmodell mehr als ein Ausgleich für DES ist, und das, +ohne daß wir uns mit ärgerlichen Exportbeschränkungen herumschlagen +müßten. Es ist einen Versuch wert, für alle außerhalb (oder sogar auch +innerhalb) der USA! (Anm.: MD5 implementiert keine Verschlüsselung im +Sinne der amerikanischen Exportbestimmungen, sondern kann ausschließ- +lich zur Zugangskontrolle verwendet werden. Damit fällt es nicht unter +die Exportbeschränkungen der USA. -- Jörg) + + +1.1 Was ist neu in 2.0.5? +------------------------- + +Die folgenden Funktionen wurden im Zeitraum zwischen der Freigabe von +Version 2.0 und dieser Version 2.0.5 entweder hinzugefügt oder grundle- +gend verbessert. Um eine bessere Kommunikation zu ermöglichen, ist die +Person (oder die Personen), die für die jeweilige Verbesserung verant- +wortlich ist, aufgelistet. Jegliche Fragen bezüglich der neuen Funkiona- +lität sollte zuerst an denjenigen gerichtet werden. + + +KERNEL: + +Vereinigter VM/Dateipuffer-Cache +-------------------------------- +Der Entwurf eines vereinten VM/Dateipuffer-Caches verbessert die gesamte +Leistungsfähigkeit des Systems erheblich und erlaubt eine Reihe optimier- +ter Speicherbelegungsstrategien, die vorher unmöglich waren. + +Verantwortlich: David Greenman (davidg@FreeBSD.org) and + John Dyson (dyson@implode.root.com) + + +Optimierter Hash-Algorithmus für Netzwerk-Protokollsteuerblöcke (PCB's) +----------------------------------------------------------------------- +Für Systeme mit einer großen Anzahl aktiver TCP-Verbindungen (z. B. +WEB- und FTP-Server) wird dadurch die Suche für ein ankommendes Paket +nach der dazugehörigen Verbindung erheblich beschleunigt. + +Verantwortlich: David Greenman (davidg@FreeBSD.org) + + +Optimierung des Dateinamen-Caches +--------------------------------- +Der Namens-Cache faßt nunmehr alle gleichen Namen im gleichen Speicher- +block zusammen, so daß z. B. alle ,,..''-Einträge im gleichen Block +landen. Die Version für das Elternverzeichnis wurde einbezogen, um +den Hash durcheinanderzubringen, und die Cache-Verwaltung wurde ver- +bessert, da gerade an diesem Teil gearbeitet wurde. + +Verantwortlich: Poul-Henning Kamp (phk@FreeBSD.org) + David Greenman (davidg@FreeBSD.org) + + +Weniger einschränkende Konfigurierung von Swap-Bereichen +-------------------------------------------------------- +Die Notwendigkeit, die Namen der Swap-Geräte in den Kernel zu kompilie- +ren, wurde beseitigt. ,swapon' akzeptiert numehr jedes Block-Gerät bis +zur Maximalzahl der in den Kernel konfigurierten Swap-Geräte. + +Verantwortlich: Poul-Henning Kamp (phk@FreeBSD.org) + David Greenman (davidg@FreeBSD.org) + + +,,Vorverdrahtete'' SCSI-Geräte +------------------------------ +FreeBSD-Versionen vor 2.0.5 haben die Gerätenummernzuweisung für SCSI- +Geräte ausschließlich dynamisch vorgenommen in der Reihenfolge, wie die +Geräte gefunden wurden, so daß infolge Fehlfunktion eines SCSI-Gerätes +sich möglicherweise die Gerätenummer ändern konnte. Dieses hatte zur +Folge, daß selbst die Zuordnung der Dateisysteme auf den noch funktio- +nierenden Geräten nicht mehr möglich war und die Dateisysteme nicht +gemountet werden konnten. Durch ,,Vorverdrahtung'' ist es jetzt möglich, +statisch die Zuordnung zwischen Gerätenummern (und damit Gerätenamen) und +SCSI-Geräten vorzunehmen, wobei die SCSI-ID und die Nummer des SCSI- +Busses als Basis dienen. Diese Zuordnung wird in der Konfigurations- +datei des Kernels vorgenommen und ist sowohl in der Manual-Seite scsi(4) +als auch in der LINT-Beispielkonfiguration dokumentiert. + +Verantwortlich: Peter Dufault (dufault@hda.com) +Betroffene Dateien: sys/scsi/* usr.sbin/config/* + + +Unterstützung für ,,Slices'' +---------------------------- +FreeBSD unterstützt nunmehr die Abstraktion von ,,Slices'' (globalen +Platten-Partitionen), so daß die Zusammenarbeit mit Partitionen anderer +Betriebssysteme verbessert wird. Damit ist es FreeBSD möglich, vor- +handene DOS-Partitionen (ohne weitere Vorkehrungen) mitzunutzen. + +Verantwortlich: Bruce Evans (bde@FreeBSD.org) +Betroffene Dateien: sys/disklabel.h sys/diskslice.h sys/dkbad.h + kern/subr_diskslice.c kern/subr_dkbad.c + i386/isa/diskslice_machdep.c + i386/isa/wd.c scsi/sd.c dev/vn/vn.c + + +Unterstützung für Version 6.0 des OnTrack Disk-Managers +------------------------------------------------------- +Es wurde die Möglichkeit geschaffen, Platten zu nutzen, die durch den +OnTrack Disk-Manager verwaltet werden. Das fdisk-Programm jedoch weiß +darüber noch nichts, so daß alle Änderungen entweder im Installations- +programm der Bootdiskette (boot.flp) oder aber im OnTrack Disk-Manager +aus DOS heraus vorgenommen werden müssen. + +Verantwortlich: Poul-Henning Kamp (phk@FreeBSD.org) + + +Bad144 ist wieder da und funktioniert +------------------------------------- +Bad144 funktioniert wieder. Die Semantik jedoch hat sich gegenüber +früher geringfügig geändert. Die Fehlerstellen werden nunmehr relativ +zur ,,Slice'' gezählt und nicht mehr absolut bezüglich der ganzen +Platte. + +Verantwortlich: Bruce Evans (bde@FreeBSD.org) + Poul-Henning Kamp (phk@FreeBSD.org) + + +UNTERSTÜTZUNG NEUER GERÄTE: + + SCSI- und CDROM-Geräte + +Matsushita/Panasonic (Creative) CD-ROM-Treiber +---------------------------------------------- +Die Laufwerke Matsushita/Panasonic CR-562 und CR-563 werden nunmehr +unterstützt, wenn sie an einen SoundBlaster- oder 100% kompatiblen +Hostadapter angeschlossen sind. Bis zu vier Hostadapter sind möglich, so +daß maximal 16 CD-ROM-Laufwerke angeschlossen werden können. Die +Audio-Funktionen sind ebenfalls unterstützt einschließlich des ,,Karoke +variable speed playback''. + +Verantwortlich: Frank Durda IV bsdmail@nemesis.lonestar.org +Betroffene Dateien: isa/matcd + + +Adaptec 2742/2842/2940 SCSI-Treiber +----------------------------------- +Der originale Treiber für 274X-/284X-Adapter wurde gegenüber der Version +2.0 beträchtlich geändert. Nunmehr gibt es auch volle Unterstützung der +2940-Serie sowie der ,,Wide-SCSI''-Modelle dieser Karten. Der Bug in der +Bus-Arbitrierung (sowie viele weitere) wurde beseitigt, der Treiberprob- +leme mit schnellen SCSI-Geräten verursacht hat. Es existiert sogar eine +experimentelle Unterstützung für ,,tagged queuing'' (Kernel-Option +,,AHC_TAGENABLE''). Weiterhin hat John Aycock den Code für den Sequen- +cer nunmehr mit einem ,,Berkeley''-Copyright freigegeben, so daß die +Restriktionen der GPL nicht mehr auf den Treiber zutreffen. + +Verantwortlich: Justin Gibbs (gibbs@FreeBSD.org) +Betroffene Dateien: isa/aic7770.c pci/aic7870.c i386/scsi/* + sys/dev/aic7xxx/* + + +NCR5380/NCR53400 SCSI ("ProAudio Spectrum") Treiber +--------------------------------------------------- +Verantwortlich: Core-Team +Eingereicht von: Serge Vakulenko (vak@cronyx.ru) +Betroffene Dateien: isa/ncr5380.c + + +Sony CDROM-Treiber +------------------ +Verantwortlich: Core-Team +Eingereicht von: Mikael Hybsch (micke@dynas.se) +Betroffene Dateien: isa/scd.c + + + Serielle Geräte + +Treiber für SDL Communications Riscom/8 Serial Board +---------------------------------------------------- +Verantwortlich: Andrey Chernov (ache@FreeBSD.org) +Betroffene Dateien: isa/rc.c isa/rcreg.h + + +Treiber für Cyclades Cyclom-y Serial Board +------------------------------------------ +Verantwortlich: Bruce Evans (bde@FreeBSD.org) +Eingereicht von: Andrew Werple (andrew@werple.apana.org.au) and + Heikki Suonsivu (hsu@cs.hut.fi) +Entnommen aus: NetBSD +Betroffene Dateien: isa/cy.c + + +Serieller Treiber Cronyx/Sigma sync/async-Geräte +------------------------------------------------ +Verantwortlich: Core-Team +Eingereicht von: Serge Vakulenko +Betroffene Dateien: isa/cronyx.c + + + + Netzwerk + +Plattenloses Booten +------------------- +Das plattenlose Booten wurde in Version 2.0.5 stark verbessert. Das +Boot-Programm befindet sich in src/sys/i386/boot/netboot und kann sowohl +von MSDOS aus gestartet als auch in einen EPROM gebrannt werden. Lokales +Swappen ist ebenfalls möglich. Gegenwärtig werden Ethernet-Karten von +WD, SMC, 3Com und Novell unterstützt. + + +Treiber für DEC DC21140 ,,Fast Ethernet''-Adapter +------------------------------------------------- +Dieser Treiber unterstützt die zahlreichen Netzwerkadapter auf Basis +des DEC DC21140-Chipsatzes einschließlich der 100 MBit/s DEC-500-XA und +SMC 9332. + +Verantwortlich: Core-Team +Eingereicht von: Matt Thomas (thomas@lkg.dec.com) +Betroffene Dateien: pci/if_de.c pci/dc21040.h + +Treiber für DEC FDDI (DEFPA/DEFEA) +---------------------------------- +Verantwortlich: Core-Team +Eingereicht von: Matt Thomas (thomas@lkg.dec.com) +Betroffene Dateien: pci/if_pdq.c pci/pdq.c pci/pdq_os.h pci/pdqreg.h + + +Treiber für 3Com 3c505 (Etherlink/+) Karten +------------------------------------------- +Verantwortlich: Core-Team +Eingereicht von: Dean Huxley (dean@fsa.ca) +Entnommen aus: NetBSD +Betroffene Dateien: isa/if_eg.c + + +Treiber für die Fujitsu-MB86960A-Netzwerkkarten-Familie +------------------------------------------------------- +Verantwortlich: Core-Team +Eingereicht von: M.S. (seki@sysrap.cs.fujitsu.co.jp) +Betroffene Dateien: isa/if_fe.c + + +Treiber für Intel EtherExpress +------------------------------ +Verantwortlich: Rodney W. Grimes (rgrimes@FreeBSD.org) +Betroffene Dateien: isa/if_ix.c isa/if_ixreg.h + + +Treiber für 3Com 3c589 +---------------------- +Verantwortlich: Core-Team +Eingereicht von: "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp), + Seiji Murata (seiji@mt.cs.keio.ac.jp) and + Noriyuki Takahashi (hor@aecl.ntt.jp) +Betroffene Dateien: isa/if_zp.c + + +Treiber für IBM-Kreditkarten +---------------------------- +Verantwortlich: Core-Team +Eingereicht von: "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp) +Betroffene Dateien: isa/pcic.c isa/pcic.h + + +Treiber für EDSS1- und 1TR6-ISDN-Interface +------------------------------------------ +Verantwortlich: Core-Team +Eingereicht von: Dietmar Friede (dfriede@drnhh.neuhaus.de) and + Juergen Krause (jkr@saarlink.de) +Betroffene Dateien: gnu/isdn/* + + + Diverse Treiber + +Treiber für Joystick +-------------------- +Verantwortlich: Jean-Marc Zucconi (jmz@FreeBSD.org) +Betroffene Dateien: isa/joy.c + + +Treiber für National Instruments "LabPC" +---------------------------------------- +Verantwortlich: Peter Dufault (dufault@hda.com) +Betroffene Dateien: isa/labpc.c + + +Treiber für WD7000 +------------------ +Verantwortlich: Olof Johansson (offe@ludd.luth.se) + + +Pcvt-Console-Treiber +-------------------- +Verantwortlich: Jörg Wunsch (joerg@FreeBSD.org) +Eingereicht von: Hellmuth Michaelis (hm@altona.hamburg.com) +Betroffene Dateien: isa/pcvt/* usr.sbin/pcvt/* + + +BSD-audio Emulator für den VAT-Treiber +-------------------------------------- +Verantwortlich: Amancio Hasty (ahasty@FreeBSD.org) and + Paul Traina (pst@FreeBSD.org) +Betroffene Dateien: isa/sound/vat_audio.c isa/sound/vat_audioio.h + + +Treiber für National Instruments AT-GPIB and AT-GPIB/TNT GPIB +------------------------------------------------------------- +Verantwortlich: Core-Team +Eingereicht von: Fred Cawthorne (fcawth@delphi.umd.edu) +Betroffene Dateien: isa/gpib.c isa/gpib.h isa/gpibreg.h + + +Treiber für Genius GS-4500 Handscanner +-------------------------------------- +Verantwortlich: Core-Team +Eingereicht von: Gunther Schadow (gusw@fub46.zedat.fu-berlin.de) +Betroffene Dateien: isa/gsc.c isa/gscreg.h + + +CORTEX-I Frame Grabber +---------------------- +Verantwortlich: Core-Team +Eingereicht von: Paul S. LaFollette, Jr. +Betroffene Dateien: isa/ctx.c isa/ctxreg.h + + +Video Spigot video capture card +------------------------------- +Verantwortlich: Jim Lowe + + + +1.2 Experimentelle Funktionalität +--------------------------------- + +Von den Dateisystemen unionfs und LFS ist bekannt, daß sie in Version +2.0.5 stark mangelhaft sind. Das ist teilweise alten Bugs geschuldet, zu +deren Beseitigung wir noch keine Zeit gefunden haben, sowie der noch +ausstehenden Umstellung auf das neue VM-System. Wir hoffen, daß wir +diese Probleme ein einer späteren Version von FreeBSD beseitigen können. + +FreeBSD kann nunmehr Binaries laufen lassen, die dem iBCS2-Standard ge- +nügen. (SCO UNIX 3.2.2 & 3.2.4 und ISC 2.2 COFF-Format sind gegenwärtig +unterstützt.) Der iBCS2-Emulator befindet sich noch in seinen Anfängen, +aber er funktioniert. Wir haben noch keine erschöpfenden Tests vornehmen +können (mangels kommerzieller Applikationen), aber beinahe alle Binaries +für SCO 3.2.2 laufen, so z. B. ein altes INFORMIX-2.10 für SCO. Zur +Vervollständigung dieses Projektes sind weitere Tests nötig. Es sind +weiterhin Arbeiten im Gange, um ELF- und XOUT-Programme starten zu kön- +nen. Der Großteil der ,,system call wrapper'' für SVR4 ist bereits ge- +schrieben. + +FreeBSD implementiert mittlerweile auch genügend Linux-Kompatibilität, +um DOOM laufen zu lassen! Für eine vollständige Dokumentation, wie +dies einzurichten ist, kann man im Verzeichnis ,,xperimnt'' (auf dem +lokalen FTP-Server oder der CDROM) nachsehen. + +Verantwortlich: Søren Schmidt (sos) & Sean Eric Fagan (sef) +Betroffene Dateien: sys/i386/ibcs2/* sowie diverse Kernelmodifikationen +======= + + +2. Unterstützte Konfigurationen +------------------------------- + +FreeBSD läuft derzeit auf einer großen Vielfalt von ISA-, VLB-, EISA- und +PCI-Bus-basierten PC's, beginnend beim 386sx bis hin zu Maschinen der +Pentium-Klasse (obwohl der 386sx nicht zu empfehlen ist). Es gibt Unter- +stützung für allgemeine IDE- oder ESDI-Laufwerke, verschiedene SCSI- +Controller, Netzwerk- und serielle Karten. + +Nachfolgend eine Liste aller Platten-Controller und Ethernet-Karten, von +denen gegenwärtig bekannt ist, daß sie mit FreeBSD zusammenarbeiten. +Andere Konfigurationen können ebenfalls funktionieren, wir haben ledig- +lich darüber noch nichts erfahren. + + +2.1. Platten-Controller + +WD1003 (beliebige MFM/RLL) +WD1007 (beliebige IDE/ESDI) +WD7000 +IDE +ATA + +Adaptec 152x Serie ISA SCSI-Controller +Adaptec 154x Serie ISA SCSI-Controller +Adaptec 174x Serie EISA SCSI-Controller, Standard und ,,Enhanced'' Mode. +Adaptec 274X/284X/2940 (Narrow/Wide/Twin) Serie ISA/EISA/PCI SCSI-Controller +Adaptec AIC-6260- und AIC-6360-basierte Karten, einschließlich AHA-152x +und SoundBlaster SCSI-Karten. + +** Anmerkung: Von den Soundblaster-Karten kann nicht gebootet werden, da +sie kein BIOS besitzen, was Voraussetzung wäre, um das Boot-Gerät in das +System-BIOS abzubilden. Sie sind jedoch ohne weiteres benutzbar für +externe Bandlaufwerke, CDROM's usw. Gleiches trifft auf AIC-6x60- +basierte Karten ohne Boot-ROM zu. Manche dieser Karten besitzen jedoch +einen Boot-ROM, was man allgemein an irgendeiner Mitteilung beim System- +start nach dem Einschalten oder einem Reset erkennen kann. Im Zweifels- +falle sollte man die Systemdokumentation konsultieren. + +[Hinweis: Buslogic nannte sich früher ,,Bustec''] +Buslogic 545S & 545c +Buslogic 445S/445c VLB SCSI-Controller +Buslogic 742A, 747S, 747c EISA SCSI-Controller. +Buslogic 946c PCI SCSI-Controller +Buslogic 956c PCI SCSI-Controller + +NCR 53C810 und 53C825 PCI SCSI-Controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI-Controller. + +DTC 3290 EISA SCSI-Controller in 1542 Emulations-Mode. + +UltraStor 14F, 24F und 34F SCSI-Controller. + +Seagate ST01/02 SCSI-Controller. + +Future Domain 8xx/950 Serie SCSI-Controller. + +Für alle unterstützten SCSI-Controller wird volle Unterstützung für alle +SCSI-I- und SCSI-II-Peripherie gewährt, einschließlich Platten, Bandlauf- +werke (auch DAT) und CD-ROM-Laufwerke. + +Folgende CD-ROM-Systeme sind derzeit unterstützt: + +(cd) SCSI (auch ProAudio Spectrum und SoundBlaster SCSI) +(mcd) Mitsumi Interface-Karte +(matcd) Matsushita/Panasonic (Creative) Interface-Karte +(scd) Sony Interface-Karte + +Hinweis: CD-Laufwerke mit IDE-Interface sind derzeit noch nicht unter- +stützt. + +Einige Controller sind hinsichtlich ihrer Kommunikation mit mehr als 16 +MB Hauptspeicher eingeschränkt, da der ISA-Bus nur 24 Bit Adreßraum +besitzt und folglich nur 16 MB adressieren kann. Dies trifft selbst auf +einige EISA-Adapter zu (die an sich 32 Bit Adreßraum haben), wenn sie auf +ISA-Emulation geschaltet werden, weil sie dies dann in *jeder* Hinsicht +tun. Diese Probleme treten nicht mit IDE-Adaptern auf (da sie kein DMA +vornehmen), echten EISA-Controllern (wie UltraStor, Adaptec 1742A oder +Adaptec 2742) sowie den meisten VLB-(Local-Bus)-Controllern. Sowie es +notwendig wird, belegt das System ,,bounce buffer'', um mit den Adaptern +zu kommunizieren, so daß es dennoch möglich ist, mehr als 16 MB Haupt- +speicher problemlos zu nutzen. + + +2.2 Ethernet-Karten + +SMC Elite 16 WD8013 Ethernet-Interfaces, sowie die meisten anderen +WD8003E-, WD8003EBT-, WD8003W-, WD8013W-, WD8003S-, WD8003SBT- and +WD8013EBT-basierten Clones. SMC Elite Ultra wird ebenfalls unterstützt. + +DEC EtherWORKS III NICs (DE203, DE204, and DE205) +DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) +DEC DC21140 based NICs (SMC???? DE???) +DEC FDDI (DEFPA/DEFEA) NICs + +Fujitsu MB86960A Familie + +Intel EtherExpress + +Isolan AT 4141-0 (16 bit) +Isolink 4110 (8 bit) + +Novell NE1000, NE2000, und NE2100 Ethernet-Interface. + +3Com 3C501 Karten + +3Com 3C503 Etherlink II + +3Com 3c505 Etherlink/+ + +3Com 3C507 Etherlink 16/TP + +3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III + +Toshiba Ethernet-Karten + +PCMCIA Ethernet-Karten von IBM und National Semiconductor werden +ebenfalls unterstützt. + + +2.3. Verschiedenes + +AST 4-Port serielle Karten unter Nutzung von ,,shared interrupt''. + +ARNET 8-Port serielle Karten unter Nutzung von ,,shared interrupt''. + +BOCA ATIO66 6-Port serielle Karten unter Nutzung von ,,shared interrupt''. + +Cyclades Cyclom-y Serial Board. + +STB 4-Port serielle Karten unter Nutzung von ,,shared interrupt''. + +Mitsumi (alle Modelle) CDROM-Interface und -Laufwerk. + +SDL Communications Riscom/8 Serial Board. + +Soundblaster SCSI und ProAudio Spectrum SCSI CDROM-Interface und -Laufwerk. + +Matsushita/Panasonic (Creative SoundBlaster) CDROM-Interface und -Laufwerk. + +Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound +und Roland MPU-401 Sound-Karten. + +FreeBSD unterstützt derzeit KEINE IBM-Microchannel (MCA) Bussysteme, +jedoch ist die Unterstützung nahe an der Fertigstellung. Einzelheiten +werden gepostet sowie sich die Situation entwickelt. + + +3. Wie kann man FreeBSD bekommen? +--------------------------------- + +FreeBSD kann man in einer Vielzahl von Möglichkeiten erhalten: + +1. FTP/Mail + +FreeBSD selbst oder all seine wahlfreien Pakete können per ftp von +,ftp.freebsd.org' bezogen werden -- der offiziellen Vertriebsstelle von +FreeBSD. + +Server, die diese Site spiegeln, sind in der Datei MIRROR.SITES aufge- +listtet. Es wird darum gebeten, die Distribution von der netzwerkmäßig +nächstgelegenen Site zu beziehen. + +Für diejenigen ohne direkten Internetzugang, aber mit der Möglichkeit, +eMail zu empfangen, steht der Weg über ,ftpmail@decwrl.dec.com' offen. +Einfach das Schlüsselwort ,,help'' als Mail dorthin schicken, und man +bekommt eine genaue Information, wie man Dateien von ,ftp.freebsd.org' +beziehen kann. Achtung: diese Variante führt zum Versenden einiger *zehn +Megabyte* über Mail und sollte daher wirklich nur als allerletzte +Möglichkeit in Betracht gezogen werden! + + +2. CDROM + +FreeBSD 2.0.5 kann man auf CDROM bestellen bei: + + Walnut Creek CDROM + 4041 Pike Lane, Suite D + Concord CA 94520 + +1-510-674-0783, +1-510-674-0821 (Fax) + +Oder über Internet bei orders@cdrom.com oder http://www.cdrom.com. +Der aktuelle Katalog kann mittels FTP bezogen werden als + ftp://ftp.cdrom.com/cdrom/catalog. + +Die CDROM kostet US-$ 39.95. Der Versand kostet (pro Bestellung, nicht +pro CD) US-$ 10.00. Visa, Mastercard und American Express werden in +Zahlung genommen. + +Die CD's können bei Nichtgefallen bedingungslos zurückgegeben werden. + + +Berichten von Bugs, Verbesserungsvorschläge, Einreichen von Code +---------------------------------------------------------------- + +Jegliche Fehlerberichte und Beiträge von Code sind herzlich willkommen. +Fehler sollten in jedem Falle gemeldet werden (nach Möglichkeit mit einem +,Fix'). + +Die wünschenswerte Methode zum Einsenden eines Problemberichtes von einer +Maschine mit Internet-Mailzugang ist die Nutzung des Programmes send-pr. +Diese Berichte werden sorgfältig von unserem Bugfile-Programm regi- +striert, und es wird alles getan, so schnell wie möglich darauf zu +antworten. + +Ist es aus irgendeinem Grunde nicht möglich, das Programm ,,send-pr'' +zu nutzen, so können Fehlerberichte auch direkt an + + bugs@FreeBSD.org + +gesandt werden. Außerdem steht die Liste + + questions@FreeBSD.org + +für allgemeine Fragen zur Verfügung. + +(Bitte, wenn möglich, an diese Listen in englischer Sprache schreiben.) + +Selbstverständlich sind wir, da all unsere Arbeit auf der Basis von Frei- +willigkeit geschieht, jederzeit über zusätzliche Helfer erfreut -- es +gibt jetzt schon mehr zu tun, als wir jemals zu tun in der Lage sein +werden! Technische Diskussionsbeiträge oder Hilfsangebote können an + + hackers@FreeBSD.org + +gesandt werden. Diese Listen verursachen in der Regel ein beträcht- +liches Mailaufkommen. Für diejenigen, die einen langsamen oder teuren +Mailanschluß haben und nur an den Ankündigungen wichtiger Ereignisse +interessiert sind, mag daher + + announce@FreeBSD.org + +interessant sein. + + +All diesen Gruppen mit Ausnahme von freebsd-bugs kann jeder Interessierte +jederzeit beitreten. Eine Mail an ,,MajorDomo@FreeBSD.org'' geschickt, +mit lediglich dem Schlüsselwort ,,help'' auf einer eigenen Zeile in der +Nachricht, wird mit der Information über die vorhandenen Listen und +Teilnahmemöglichkeiten beantwortet. Neben den hier genannten Listen +existieren noch weitere, die auf bestimmte Interessengruppen ausgerichtet +sind, so daß die Anfrage durchaus lohnt! + + +6. Würdigungen +-------------- + +FreeBSD verkörpert die Arbeit vieler Dutzender, wenn nicht Hunderte, +Einzelner aus der ganzen Welt, die hart gearbeitet haben, um diese +Version fertigzustellen. Es wäre sehr schwierig oder schier unmöglich, +jeden aufzuzählen, der in irgendeiner Form zu FreeBSD beigetragen hat. +Nichtsdestotrotz soll der Versuch unternommen werden (natürlich in +alphabetischer Reihenfolge). Sollte ein Name fehlen, so ist dieses +ausschließlich ein Versehen. + + +Die Computer Systems Research Group (CSRG), U.C. Berkeley. + +Bill Jolitz, für seine ersten Arbeiten am 386BSD. + +Das FreeBSD-Core-Team +(in alphabetischer Reihenfolge der Vornamen): + + Andreas Schulz <ats@FreeBSD.org> + Andrey A. Chernov <ache@FreeBSD.org> + Bruce Evans <bde@FreeBSD.org> + David Greenman <davidg@FreeBSD.org> + Garrett A. Wollman <wollman@FreeBSD.org> + Gary Palmer <gpalmer@FreeBSD.org> + Geoff Rehmet <csgr@FreeBSD.org> + Jack Vogel <jackv@FreeBSD.org> + John Dyson <dyson@FreeBSD.org> + Jordan K. Hubbard <jkh@FreeBSD.org> + Justin Gibbs <gibbs@FreeBSD.org> + Paul Richards <paul@FreeBSD.org> + Poul-Henning Kamp <phk@FreeBSD.org> + Rich Murphey <rich@FreeBSD.org> + Rodney W. Grimes <rgrimes@FreeBSD.org> + Satoshi Asami <asami@FreeBSD.org> + Søren Schmidt <sos@FreeBSD.org> + +Besondere Erwähnung verdienen: + + Walnut Creek CDROM, ohne deren Hilfe und ständige Unterstützung + diese Ausgabe nie möglich geworden wäre. + + Dermot McDonnell für seine Bereitstellung eines Toshiba XM3401B + CDROM-Laufwerkes. + + Weitere Helfer und Beta-Tester von FreeBSD: + + J.T. Conklin Julian Elischer + Frank Durda IV Peter Dufault + Sean Eric Fagan Jeffrey Hsu + Terry Lambert L Jonas Olsson + Chris Provenzano Dave Rivers + Guido van Rooij Steven Wallace + Atsushi Murai Scott Mace + Nate Williams + + sowie alle an der Montana State University für ihre anfängliche + Unterstützung. + + +Jordan möchte weiterhin besonders Poul-Henning Kamp und Gary Palmer +danken, die ihm beide in vielstündiger Arbeit geholfen haben, das neue +Installationssystem zusammenzustellen. Poul, kürzlich stolzer Vater +geworden, hat es trotz seines enormen Zeitdrucks immer noch geschafft, +eine beträchtliche Menge an Arbeit in das Projekt zu investieren. Diese +Version wäre ohne ihn nicht geworden! Dank Euch Beiden! + +Weiterhing geht Dank an all diejenigen, die mitgeholfen haben, besonders +auch an alle Nichtgenannten. Wir hoffen, daß diese Ausgabe von FreeBSD +allgemeinen Anklang findet! + + Das FreeBSD Core-Team + +$Id: RELNOTES,v 1.2 1995/06/07 05:51:03 jkh Exp $ +======================================================================= diff --git a/release/sysinstall/help/de_DE.ISO8859-1/configure.hlp b/release/sysinstall/help/de_DE.ISO8859-1/configure.hlp new file mode 100644 index 0000000..468c1b5 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO8859-1/configure.hlp @@ -0,0 +1,18 @@ +Mit diesem Menü kann man das System nach der Installation ein wenig +konfigurieren. Es sollten wenigstens das Paßwort für den System- +verwalter gesetzt sowie die Zeitzone eingestellt werden. + +Für zusätzliche ,,Rosinen'' wie bash, emacs, pascal usw. ist es wohl +immer notwendig, einen Blick auf den Menüpunkt ,,Packages'' zu werfen. +Dies ist gegenwärtig nur sinnvoll, wenn man entweder von einer CDROM +installiert oder aber die Package-Sammlung irgendwo in der Datei- +systemhierarchie bereits vorhanden ist, so daß die Package-Verwaltung +darauf zugreifen kann. Eine automatische Übertragung der Packages +mittels FTP ist derzeit noch nicht vorgesehen. + +Soll das Installationsprogramm für die Packages nach Beenden der +Systeminstallation nochmals aufgerufen werden, der Kommandoname +dafür ist ,,pkg_manage''. Das Einstellen der Zeitzone geschieht +mit dem Kommando ,,tzsetup''. Weitere Informationen bezüglich der +allgemeinen Systemkonfiguration befinden sich in der Datei +,,/etc/sysconfig''. diff --git a/release/sysinstall/help/de_DE.ISO8859-1/drives.hlp b/release/sysinstall/help/de_DE.ISO8859-1/drives.hlp new file mode 100644 index 0000000..41681f0 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO8859-1/drives.hlp @@ -0,0 +1,29 @@ +Sowie die ernsthafte Absicht besteht, wirklich irgendetwas von FreeBSD +auf einem Laufwerk zu instellieren, sollte man sich UNBEDINGT VERSICHERN, +daß die vom Partition-Editor berichtete Geometrie (siehe Installations- +Menü) auch die richtige für die Kombination aus Laufwerk und Controller +ist! + +IDE-Laufwerke ,,lernen'' oftmals ihre Geometrie über das Setup des BIOS, +oder (für größere Laufwerke), ihre Geometrie wird entweder vom IDE- +Controller oder aber einem speziellen Werkzeug, das zur Bootzeit geladen +wird, wie dem OnTrack Systems Disk- Manager, uminterpretiert (,,remap- +ped''). In solchen Fällen ist das Erkennen der richtigen Geometrie noch +schwerer, da man nicht einfach auf dem Laufwerk oder im BIOS-Setup +nachsehen kann. Dann ist es das Beste, ein DOS zu booten (von der +Festplatte, nicht von einer Diskette!) und mittels des im tools/-Ver- +zeichnis auf der FreeBSD-CDROM oder auf einem FTP-Server bereitgestellten +Programmes ,,pfdisk'' die Geometrie zu vergleichen. Dieses Programm +berichtet die Geometrie, wie DOS sie sieht, die allgemein als die +richtige angenommen werden kann. + +Falls gar keine DOS-Partition gewünscht wird, kann es sich dennoch als +sinnvoll erweisen, eine solche (sehr kleine) vorerst einzurichten, um +sich über die Laufwerksgeometrie zu informieren. Sie kann dann später +wieder gelöscht werden. + +Es ist aber tatsächlich gar nicht so schlecht (ob man's glaubt oder +nicht), eine bootfähige DOS-Partition auf der Platte zu haben: falls die +Maschine später instabil wird oder einfach ,,spinnt'', so kann man von da +aus bequem eines der kommerziell erhältlichen System-Diagnose-Programme +laufen lassen. diff --git a/release/sysinstall/help/de_DE.ISO8859-1/install.hlp b/release/sysinstall/help/de_DE.ISO8859-1/install.hlp new file mode 100644 index 0000000..420eb95 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO8859-1/install.hlp @@ -0,0 +1,450 @@ + INSTALLATIONSANLEITUNG FÜR FreeBSD 2.0.5 + +Diese Beschreibung dokumentiert die Installation von FreeBSD 2.0.5 auf der +Maschine. Vor dem Beginn ist es ratsam, die Hardware-Anleitung zu studie- +ren, um sich über die hardware-spezifischen Installationshinweise zu in- +formieren (Konfiguration der Hardware, worauf man achten sollte usw.). + + +Inhalt: +======= + +1.0 Fragen und Antworten für DOS-Benutzer + 1.1 Wie schaffe ich Platz für FreeBSD? + 1.2 Kann ich von FreeBSD aus komprimierte DOS-Dateisysteme nutzen? + 1.3 Kann ich erweiterte DOS-Partitions nutzen? + 1.4 Kann ich DOS-Programme unter FreeBSD laufen lassen? + +2.0 Vorbereitung der Installation + 2.1 Vor dem Installieren von CDROM + 2.2 Vor dem Installieren von Diskette + 2.3 Vor dem Installieren von einer DOS-Partition + 2.4 Vor dem Installieren von einem QIC- oder SCSI-Bandlaufwerk + 2.5 Vor dem Installieren über Netz + 2.5.1 Vorbereiten einer NFS-Installation + 2.5.2 Vorbereiten einer FTP-Installation + +3.0 Installieren von FreeBSD + + + +1.0 Fragen und Antworten für DOS-Benutzer +=== ===================================== + +1.1 Hilfe! Kein Platz mehr! Muß ich nun erst alles löschen? + +Wenn auf der Maschine bereits ein DOS installiert ist und nun nur noch +wenig oder gar kein freier Platz mehr für eine FreeBSD-Installation bleibt, +so muß man nicht gleich alle Hoffnung aufgeben! Das Hilfsprogramm FIPS, +das sich im Unterverzeichnis tools/ auf der FreeBSD-CDROM oder auf den +verschiedenen FreeBSD-FTP-Servern befindet, kann sich hier als sehr nütz- +lich erweisen. + +FIPS erlaubt die Aufteilung einer bestehenden DOS-Partition in zwei Teile, +wobei der ursprüngliche Inhalt der Originalpartition erhalten bleibt und +das zweite Stück zum Installieren von FreeBSD verfügbar wird. Man defrag- +mentiert die Partition zuerst mittels des Programmes ,,DEFRAG'' von DOS 6 +oder mittels der Norton Disk Tools und läßt anschließend FIPS laufen. Das +Programm erfragt dann den Rest der benötigten Informationen. Danach kann +man neu booten und FreeBSD in der freigewordenen ,Slice' installieren. Im +Menüpunkt ,,Distributions'' kann man eine Abschätzung vornehmen, wieviel +freien Platz man für die gewünschte Installation etwa benötigt. + + +1.2 Kann ich von FreeBSD aus komprimierte DOS-Dateisysteme nehmen? + +Nein. Wenn man ein Programm wie Stacker (TM) oder DoubleSpace (TM) be- +nutzt, so kann FreeBSD nur den Bereich des (DOS-)Dateisystems nutzen, der +nicht komprimiert worden ist. Der Rest erscheint dann als eine einzige +große Datei (die Stacker- oder DoubleSpace-Datei). DIESE DATEI UNTER +KEINEN UMSTÄNDEN LÖSCHEN! Das würde man nachher bereuen! + + +1.3 Kann ich erweiterte DOS-Partitions nehmen? + +Diese Möglichkeit bietet FreeBSD 2.0.5 noch nicht, aber sie ist für Version +2.1 vorgesehen. Die Grundlagen dafür sind bereits geschaffen, es ist nur +noch 1 % an Restarbeit nötig. + + +1.4 Kann ich DOS-Programme unter FreeBSD laufen lassen? + +Noch nicht. Wir hätten das gern irgendwann, aber bisher hat sich noch +niemand gefunden, der die Arbeit machen würde. Die voranschreitenden +Arbeiten mit dem Linux-DOSEMU-Programm bringen uns aber näher ans Ziel. +Diejenigen, die sich an der Arbeit beteiligen möchten, können sich mittels +einer Mail an hackers@freebsd.org gern melden! + +Es gibt jedoch in der ,,Ports collection'' ein nettes Programm namens +,,pcemu''. Es emuliert einen 8088 sowie ausreichend BIOS-Dienste, um +DOS-Programme im Textmode laufen zu lassen. Es benötigt ein X-Window- +System zum Arbeiten. + + + +2.0 Vorbereitung der Installation +=== ============================= + +2.1 Vor dem Installieren von CDROM: + +Wenn es sich bei dem CDROM-Laufwerk um eins handelt, was nicht unterstützt +wird (z. B. ein IDE-CDROM-Laufwerk), dann bitte bei Punkt 2.3 (,,Vor dem +Installieren von einer DOS-Partition'') weiterlesen. + +Es bedarf keiner großen Vorbereitungen, um von einer der FreeBSD-CDROMs von +Walnut Creek zu installieren. (Andere CDROM-Distributionen können genauso +einfach zu nutzen zu sein, aber da wir keinerlei Einfluß auf deren Gestal- +tung haben, können wir darüber nichts aussagen.) Man kann entweder mittels +des von Walnut Creek gelieferten Scriptes ,,install.bat'' direkt die CDROM +booten, oder aber man fertigt sich mittels ,,makeflp.bat'' eine Boot-Dis- +kette an. + +Der allereinfachste Weg (von DOS aus) ist, einfach ,,go'' einzutippen. Es +erscheint ein kleines DOS-Menü, das einen durch die verfügbaren Möglich- +keiten geleitet. + +Will man die Bootdiskette von einem Unix-System aus erstellen, so führt +vielleicht ein Kommando wie ,,dd if=floppies/boot.flp of=/dev/rfd0'' oder +aber ,,dd if=floppies/boot.flp of=/dev/floppy'' zum Ziel, abhängig von der +verwendeten Hardware und dem Betriebssystem. + +Sowie man von DOS oder einer Diskette aus gebootet hat, kann man sich im +Menüpunkt ,,Media menu'' des Installationsprogrammes die CDROM als Medium +aussuchen und die komplette Distribution davon laden. Es werden keine +weiteren Medien benötigt. + +Nachdem das System installiert ist und man von der Festplatte neu gebootet +hat, müßte die CD im Verzeichnis /cdrom gemountet sein. Das Hilfsprogramm +,lndir', das zusammen mit der XFree86-Distribution kommt, kann hier sehr +nützlich sein: man kann damit einen Baum von symbolischen Links aufbauen, +der das nicht beschreibbare Medium CDROM auf der Festplatte spiegelt. Als +kleines Beispiel: + + mkdir /usr/ports + lndir /cdrom/ports /usr/ports + +Danach kann man dann ,,cd /usr/ports; make'' eintippen, alle Quellen werden +von der CD gelesen, aber alle Zwischendateien werden unterhalb /usr/ports +angelegt, das sich zweckmäßig auf einem besser beschreibbaren Medium befin- +den sollte! :-) + +WICHTIGER HINWEIS: Vor Beginn der Installation unbedingt davon überzeugen, +daß die CDROM im Laufwerk ist, so daß sie beim Test gefunden wird! Dies +ist auch nötig, wenn man gern die CDROM automatisch während der Installa- +tion in die Standard-Konfiguration aufgenommen haben möchte (unabhängig +davon, ob die Installation selbst von CDROM erfolgt). Dies wird sich in +Version 2.1 ändern, aber gegenwärtig ist dies eine einfache Methode um +festzustellen, daß die CDROM tatsächlich zugreifbar ist. + +Schließlich ist es ein Leichtes, wenn man es anderen ermöglichen will, +FreeBSD direkt von der CDROM in der eigenen Maschine mittels FTP installie- +ren zu lassen. Es ist lediglich nach Vollenden der Installation nötig, +folgende Zeile in die Datei /etc/master.passwd aufzunehmen (bitte mit dem +Kommando ,,vipw''): + + ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent + +Mehr ist nicht nötig. Alle anderen können nun in ihrem Installationsmenü +,,FTP'' als Medium auswählen und als Servernamen (über den Menüpunkt +,,Other'') eintragen: ftp://<Adresse dieser Maschine>! + + +2.2 Vor dem Installieren von Diskette + +Wenn man von Disketten installieren will, weil z. B. die Hardware nicht +anders unterstützt wird oder aber für diejenigen, die schwierige Wege +mögen, so muß man zuerst einige Installationsdisketten vorbereiten. + +Die erste Diskette, die man (außer der Bootdiskette) benötigt, ist die +,,floppies/root.flp''. Sie ist insofern etwas Besonderes, daß es sich +nicht um eine Diskette mit DOS-Dateisystem handelt, sondern um ein Abbild +(,image') binärer Daten (genauer gesagt, um ein mit ,gzip' komprimiertes +cpio-Archiv). Man kann dieses Abbild entweder unter DOS mittels des +Programmes ,,rawrite.exe'' auf die Diskette bringen, oder unter Unix mit +dem ,,dd''-Kommando (siehe Bemerkungen in Punkt 2.1 für die Datei +,,floppies/boot.flp''). Nachdem diese Diskette fertig ist, kann es mit den +Distributions-Disketten weitergehen. + +Man benötigt mindestens so viele 1.44-MB- oder 1.2-MB-Disketten, wie nötig +sind, um die Dateien im Verzeichnis ,bin' (Binärdistribution) aufzunehmen. +DIESE Disketten *müssen* DOS-formatiert sein, entweder mit dem Kommando +,,FORMAT'' in DOS oder dem Dateimanager in Microsoft Windows (TM). Man +sollte vorformatierten Disketten nicht trauen und sie sicherheitshalber +nochmals selbst formatieren! + +In der Vergangenheit wurden wiederholt Probleme mit mangelhaft formatier- +ten Datenträgern berichtet, daher hier nochmals obiger Hinweis! + +Nach dem Formatieren der Disketten müssen nun die Dateien darauf über- +tragen werden. Die Distributions-Dateien sind in Stücke zerlegt, von denen +5 auf eine gewöhnliche 1.44-MB-Diskette passen. Man packt einfach alle +vorhandenen Dateien auf die Disketten, so viele, wie auf jede draufpassen, +bis das Ende erreicht ist. Jede Distribution muß dabei in einem eigenen +Untervezeichnis auf den Disketten abgelegt werden, also z. B.: +a:\bin\bin.aa, a:\bin\bin.ab, ... + +Sowie im Installationsprogramm der Menüpunkt zur Medienauswahl erreicht +wird, wählt man ,,Floppy'' aus - der Rest wird dann abgefragt. + + +2.3 Vor dem Installieren von einer DOS-Partition + +In Vorbereitung der Installation von einer DOS-Partition kopiert man +einfach alle Dateien der Distribution(en) in ein Verzeichnis, das +,,FREEBSD'' heißen soll. Um also eine Minimalinstallation von FreeBSD +vorzunehmen, wobei man die Dateien von der CDROM auf die DOS-Partition +kopiert: + + C> MD C:\FREEBSD + C> XCOPY /S E:\DISTS\BIN C:\FREEBSD + C> XCOPY /S E:\FLOPPIES C:\FREEBSD + +...in der Annahme, daß auf ,C:' der nötige freie Platz ist und die CDROM +,E:' genannt wird. Es ist wesentlich, daß auch das Verzeichnis FLOPPIES +mit kopiert wird, da die Datei ,root.flp' daraus während einer Installation +von einer DOS-Partition automatisch entnommen wird. + +Man kann all die gewünschten ,DISTS' unterhalb ,C:\FREEBSD' plazieren - die +,BIN'-Distribution ist lediglich das notwendige Minimum. + + +2.4 Vor dem Installieren von einem QIC- oder SCSI-Bandlaufwerk + +Die Installation von einem Bandlaufwerk ist wohl die einfachste Variante, +wenn man keine Online-FTP-Installation oder Installation von CDROM vorneh- +men kann. Das Installationsprogramm erwartet die Distributions-Dateien +einfach im tar-Format auf dem Band. Nachdem man also alle interessierenden +Dateien geholt hat, kann man das Band einfach mit folgenden Kommandos er- +stellen: + + cd /freebsd/distdir + tar cvf /dev/rwt0 (or /dev/rst0) dist1 .. dist2 + +Das Verzeichnis ,floppies/' muß als eine der ,dist's in obigem Beispiel mit +angegeben worden sein, da das Installationsprogram vom Band die Datei +,floppies/root.flp' lesen muß. + +Während der Installation muß es auch gewährleistet sein, daß man genügend +Platz in einem Zwischenverzeichnis besitzt (der Name dafür wird abgefragt), +um den KOMPLETTEN Inhalt des erzeugten Installationsbandes dort ablegen zu +können. Da sich Bänder nicht wahlfrei zugreifen lassen, benötigt man +vorübergehend die gleiche Menge an Plattenplatz zusätzlich, die auch auf +das Band geschrieben worden ist! + +WICHTIGER HINWEIS: Zu Beginn der Installation muß sich das Band bereits im +Laufwerk befinden, *bevor* man die Bootdiskette startet. Damit wird +sichergestellt, daß der Test während der Installation das Band auch +wirklich erkennt. + + +2.5 Vor dem Installieren über Netz + +Netzwerkinstallationen kann man über drei verschiedene Kommunikations- +medien vornehmen: + + Serieller port: SLIP oder PPP + Parallelport: PLIP (mittels ,Laplink'-Kabel) + Ethernet: mittels Standard-Ethernet-Adapter (einschließlich + einiger PCMCIA-Adapter). + +SLIP-Unterstützung ist eher primitiv und auf festverdrahtete Verbindungen +beschränkt (beispielsweise ein serielles Kabel zwischen einem Laptop und +einem anderen Computer). Die Festverdrahtung ist nötig, da die Installa- +tion über SLIP derzeit keien Möglichkeiten zum Aufbau einer Wählverbindung +anbietet; letzteres kann man aber mittels PPP machen, das man ohnehin +soweit möglich dem SLIP vorziehen sollte. + +Bei Benutzung eines Modems ist PPP sicherlich die einzige Chance. Man +sollte sich rechtzeitig die Informationen des Internet-Dienstanbieters +bereitlegen, da sie früh innerhalb des Installationsprozesses abge- +fragt werden. Minimal wird die IP-Adresse des Dienstanbieters sowie +die eigene benötigt (die aber auch freigelassen werden kann, so daß +PPP sie mit der Gegenseite aushandelt). Auch ist Kenntnis der ver- +schiedenen ,,AT''-Kommandos des benutzten Modems nötig, da das Wähl- +programm für PPP keine Kenntnisse über Modems besitzt. + +Falls eine Festverbindung zu einer anderen FreeBSD-Maschine (mit Ver- +sion 2.0R oder höher) benutzt wird, so kann man auch die Variante mit +einem ,,Laplink''-Kabel über den Parallelport in Betracht ziehen. Die +typische Datenrate über einen Parallelport ist um einiges größer als +das, was sich über serielle Leitungen erzielen läßt; Geschwindigkeiten +um die 50 KB/s sind nicht ungewöhnlich. + +Schließlich ist für eine schnellstmögliche Installation ein Ethernet- +Adapter natürlich eine gute Variante! FreeBSD unterstützt die meisten +gängigen Ethernet-Karten, wobei sich im Hardware-Wegweiser (im Menü- +punkt ,,documentation'' auf der Bootdiskette) eine Tabelle der nötigen +Einstellungen findet. Bei Nutzung eines der unterstützten PCMCIA- +Adapter muß sichergestellt sein, daß sie _vor_ dem Einschalten des +Laptops eingesteckt sind! Leider unterstützt FreeBSD gegenwärtig +keinen Austausch von PCMCIA-Karten im Betrieb. + +Natürlich benötigt man auch noch die IP-Adresse im Netzwerk, die +,,Netzwerkmaske'' für das gewählte Netzwerk, sowie den Maschinennamen. +Der lokale Systemverwalter oder Netzwerkverantwortliche kann über +diese Angaben informieren. Für den Zugriff auf andere Hosts über +Namen anstatt unhandlicher IP-Adressen ist auch noch die Adresse eines +Name-Servers und ggf. eines Gateways vonnöten (bei PPP in der Regel +der Internet-Dienstanbieter). All diese Angaben sollten man _vor_ +Beginn der Installation vom zuständigen System- oder Netzwerkverwalter +einholen. + +Sowie man auf irgendeine Weise eine Netzwerkanbindung aufgebaut hat, kann +man die Installation über NFS oder FTP fortsetzen. + + +2.5.1 Vorbereiten einer NFS-Installation + + Eine Installation über NFS ist recht einfach: man kopiert die + gewünschten FreeBSD-Distributions-Dateien irgendwo auf einen + Server und gibt deren Standort in der NFS-Medienauswahl an. + + Falls dieser Server nur Zugriffe über einen ,,privilegierten'' + Port erlaubt (wie allgemein bein Sun-Workstations üblich), so + muß man die entsprechende Option im ,,Options''-Menü setzen, + bevor man weitermacht. + + Falls man nur eine schlechte Ethernet-Karte besitzt, die sehr + langsam arbeitet, so sollte man ebenfalls die entsprechende + Option einschalten. + + Damit eine NFS-Installation funktioniert, muß der Server das + Mounten von Unterverzeichnissen erlauben; hat man also beispiels- + weise die Distribution von FreeBSD 2.0.5 im Verzeichnis + ziggy:/usr/archive/stuff/FreeBSD untergebracht, so muß der Server + das direkte Mounten von /usr/archive/stuff/FreeBSD erlauben, nicht + nur /usr oder /usr/archive/stuff. + + In FreeBSD's /etc/export-Datei wird dies mittels der Option + ``-alldirs'' gesteuert. Andere NFS-Server haben dafür andere + Konventionen. Wenn man während der Installation Meldungen vom + Server bekommt, die ,,Permission denied'' heißen, so ist dies + wahrscheinlich das Problem! + + +2.5.2 Vorbereiten einer FTP-Installation + + Eine Installation über FTP kann man von jedem Server vornehmen, der + eine einigermaßen aktuelle Kopie der FreeBSD-Version 2.0.5 gespie- + gelt hält. Das Menü ,,FTP sites'' enthält eine gute Auswahl von + FTP-Servern aus der ganzen Welt. + + Wenn man von einem anderen Server installieren will, der nicht + aufgeführt ist, oder Probleme mit der Konfiguration des Name- + Servers hat, so kann man durch Auswahl des Menüpunktes ,,Other'' in + diesem Menü auch seine eigene URL eingeben. Da eine URL auch eine + numerische IP-Adresse enthalten kann, kann man bei Fehlen eines + Name-Servers also auch eingeben: + + ftp://192.216.222.4/pub/FreeBSD/2.0.5-RELEASE + + Wenn man mittels FTP in einer Umgebung installiert, die hinter + einem ,,Firewall'' gelegen ist, so sollte man ,,Passive mode'' FTP + benutzen (was bereits standardmäßig eingestellt ist). Falls man + aus irgendeinem Grunde auf einen Server angewiesen ist, der keinen + Passiv-Modus unterstützt, kann man im ,,Options''-Menü stattdessen + Aktiv-Modus auswählen. + + +3.0 Installieren von FreeBSD +--- ------------------------ + +Nachdem man die entsprechenden Vorbereitungen getroffen hat, sollte die +Installation von FreeBSD ohne Schwierigkeiten vor sich gehen. + +Falls dies doch nicht zutrifft, so hat man vielleicht einen wichtigen +Hinweis bei der Vorbereitung der Installationsmedien verpaßt (siehe +Abschnit 2.X) und sollte nochmals dort nachlesen? Im Falle von Hardware- +problemen (oder wenn FreeBSD gar nicht erst bootet) kann die Hardware- +Anleitung auf der Boot-Diskette Hinweise zur Problembeseitigung geben. + +Die FreeBSD-Bootdiskette enthält alle benötigte Online-Dokumentation, damit +man sich in der Installation zurechtfindet. Falls dies nicht der Fall ist, +so hätten wir gern gewußt, an welcher Stelle die Probleme auftauchen! Es +ist das Ziel von FreeBSD's Installationsprogramm (sysinstall), ausreichend +selbstdokumentierend zu sein, um langwierige ,,Schritt für Schritt''- +Anleitungen hinfällig werden zu lassen. Wir werden sicher noch ein wenig +brauchen, bis dieses Ziel erreicht ist -- aber es ist das Ziel! + +Unterdessen mag die folgende ,,typische Bootreihenfolge'' ganz nützlich +sein: + +o Die Diskette booten. Nach einer Folge von Boot-Schritten, die je nach + der Hardware zwischen 30 Sekunden und 3 Minuten dauern kann, sollte das + Anfangsmenü erscheinen. Wenn die Diskette gar nicht bootet oder das + System während des Bootens hängenbleibt, sollte man den Abschnitt mit + ,,Fragen und Antworten'' in der Hardware-Anleitung hinsichtlich möglicher + Ursachen konsultieren. + +o Taste F1 drücken. Es folgen einige grundlegende Hinweise über die + Nutzung des Menüsystems. Alle diejenigen, die dieses Menüsystem noch + nicht zuvor genutzt haben, sollten sich das BITTE sorgfältig durchlesen! + +o Für diejenigen, die Englisch nicht als Muttersprache sprechen, sei die + Auswahl einer anderen Sprache im Menüpunkt ,,Language'' empfohlen (was ja + ganz offensichtlich geschehen ist :). Ein Teil der Dokumentation wird + dann in der gewählten Sprache anstatt in Englisch angeboten. + +o Auswahl der Sonderwünsche im Menüpunkt ,,Options''. + +o ,,Proceed'' anwählen, um mit dem Istallationsmenü fortzusetzen. + +Das Installationsmenü: + +o Man kann in diesem Menü alles vornehmen, ohne am bestehenden System + irgendetwas zu ändern, solange man nicht ,,Commit'' auswählt; erst damit + werden alle angeforderten Änderungen auch tatsächlich ausgeführt. + + Wenn an irgendeiner Stelle Probleme auftauchen, so bringt die Taste F1 + normalerweise die richtigen Hinweise für das Bild, in dem man sich gerade + befindet. + + o Der erste Schritt ist normalerweise ,Partition', bei dem man + die von FreeBSD zu nutzenden Plattenlaufwerke auswählen kann. + + o Danach kann man mit dem ,Label'-Editor den für FreeBSD vorge- + sehenen Platz aufteilen oder aber eine nicht-FreeBSD-Partition + (z. B. DOS) ins System einbinden. + + o Danach wählt man im ,Media'-Menü das gewünschte Installations- + medium. Sowie alle benötigten Informationen für die Installation + beisammen sind, beendet sich dieses Menü selbst; andernfalls + werden weitere Fragen gestellt (abhängig vom Medium). + + o Schließlich bestätigt man mit dem ,Commit'-Menüpunkt auf einmal + alle ausgewählten Aktionen (ohne diese Bestätigung wurde noch + nichts auf die Festplatte geschrieben). Es werden alle Infor- + mationen über neue oder geänderte Partitions geschrieben, die + Dateisysteme angelegt oder zerstörungsfrei neu markiert (abhängig + von der ,,newfs''-Markierung im Label-Editor) und schließlich + alle gewünschten Distributions ausgepackt. + + o Über das ,Configure'-Menü kann man die FreeBSD-Installation + weiter konfigurieren. Man kann hier menügesteuert die einzelnen + Vorgabewerte für Systemparameter einstellen. Einige Punkte, wie + z. B. die Netzwerkparameter, sind besonders wesentlich, wenn man + von CDROM/Band/Diskette installiert hat und daher den Netzwerk- + zugang noch nicht konfiguriert hat (sofern vorhanden). Wenn man + hier bereits das Netzwerk richtig konfiguriert, so hat man schon + beim ersten Neustart von der Festplatte einen funktionierenden + Zugriff zum Netz. + + o Mittels ,Exit' gelangt man wieder zum Hauptmenü. + + +An dieser Stelle hat man seine Arbeit mit dem sysinstall-Programm beendet. +Man kann schließlich ,Quit' anwählen. Wurde sysinstall als Erstinstalla- +tionsprogramm benutzt (bevor das System also eingerichtet war), so erfolgt +an dieser Stelle ein Neustart. Hatte man einen Boot-Manager ausgewählt, so +erscheint dann ein kleines Boot-Menü mit den Zeichen ,,F?'' als Eingabe- +aufforderung. Nachdem man die entsprechende Funktionstaste für FreeBSD +gedrückt hat (wird angezeigt), sollte FreeBSD von der Festplatte aus ge- +startet werden. + +Falls dies aus irgendeinem Grunde nicht klappt, sei wiederum auf den +Abschnitt ,,Fragen und Antworten'' in der Hardware-Anleitung verwiesen! + + Jordan (für die Anleitung) + Jörg (für die deutsche Übersetzung) + +---- Ende der Installations-Anleitung --- diff --git a/release/sysinstall/help/de_DE.ISO8859-1/language.hlp b/release/sysinstall/help/de_DE.ISO8859-1/language.hlp new file mode 100644 index 0000000..cd7a834 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO8859-1/language.hlp @@ -0,0 +1,17 @@ +In diesem Menü kann man die Vorzugssprache einstellen. Vorerst wird +damit nur die Sprache ausgewählt, in der die diversen Hilfedateien +angezeigt werden. + +In späteren Versionen werden davon auch das Tastaturlayout, der Bild- +schirmzeichensatz und verschiedene NLS-Einstellungen betroffen sein +(sysinstall selbst wird dann auch ,,message catalogs'' benutzen, so +daß alle Menüs automatisch in der richtigen Sprache erscheinen). Auch +sind weitere Internationalisierungsmaßnahmen vorgesehen, so daß die +entsprechenden Standards eingehalten werden. + +Solange diese Verbesserungen noch nicht vorgenommen sind, mag es +einfacher erscheinen, die Datei ,,/etc/sysconfig'' mit der Hand zu +editieren, sobald das System erstmals vollständig installiert ist. +Diese Datei enthält eine Anzahl (allerdings englischer) Kommentare, +die die jeweiligen Änderungen beschreiben, sowie auch einige Beispiele +nicht-englischer Voreinstellungen. diff --git a/release/sysinstall/help/de_DE.ISO8859-1/media.hlp b/release/sysinstall/help/de_DE.ISO8859-1/media.hlp new file mode 100644 index 0000000..a591468 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO8859-1/media.hlp @@ -0,0 +1,30 @@ +Von den folgenden Medien kann man installieren: + + CDROM - eines der folgenden Laufwerke ist nötig: + + Sony CDU 31/33A + Matushita/Panasonic "Sound Blaster" CDROM. + Mitsumi FX-001{A-D} (alte nicht-IDE Laufwerke). + SCSI - Jedes beliebige Standard-SCSI-CDROM-Laufwerk, das + an einen unterstützten Controller angeschlossen ist + (siehe auch Hardware-Wegweiser). + + DOS - eine primäre DOS-Partition, auf die die notwendigen + FreeBSD-Distribution-Dataien kopiert worden sind (also + z. B. (C:\FREEBSD\). + + FS - setzt ein existierendes FreeBSD-System voraus, in dem + die Dateien der neuen Distribution abgelegt worden sind. + + Diskette - Entnahme der Distributions-Dateien von einer oder + mehreren DOS-formatierten Disketten. + + FTP - Entnahme der Distributions-Dateien von einem anonymen + FTP-Server (eine Liste wird angeboten). + + NFS - Einlesen der Distributions-Dateien über einen irgendwo + gelegenen NFS-Server (dessen Zugriffsrechte dies natür- + lich erlauben müssen!) + + Tape - Einlesen der Distributions-Dateien in ein Zwischenver- + zeichnis und Auspacken von dort. diff --git a/release/sysinstall/help/de_DE.ISO8859-1/network_device.hlp b/release/sysinstall/help/de_DE.ISO8859-1/network_device.hlp new file mode 100644 index 0000000..1d4e498 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO8859-1/network_device.hlp @@ -0,0 +1,56 @@ +Eine Netzwerkinstallation kann über eine von drei verschiedenen Arten +von Verbindungen vorgenommen werden: + + Serielle Ports: SLIP / PPP + Parallelport: PLIP (benötigt ein ,,Laplink''-Kabel) + Ethernet: von einem Standard-Ethernet-Controller (ein- + schließlich einiger PCMCIA-Controller) + +Unterstützung für SLIP ist eher primitiv und auf festverdrahtete Ver- +bindungen beschränkt, wie z. B. eine serielle Leitung zwischen einem +Laptop und einem anderen PC. Es existiert gegenwärtig keine Möglich- +keit, eine Wählverbindung über ein Modem herzustellen. Dies kann je- +doch mittels des PPP-Programmes vorgenommen werden, was soweit möglich +stets dem SLIP vorgezogen werden sollte. Bei der Auswahl eines +seriellen Ports wird später die Möglichkeit geboten, die Parameter für +das slattach-Kommando anzugeben. Es wird davon ausgegangen, daß in +diesem Moment entweder slattach oder ein anderes geeignetes Kommando +auf der Gegenseite der Verbindung gestartet worden ist, um die Verbin- +dung aufzubauen. FreeBSD wird dann über diesen Anschluß installiert, +wobei die Geschwindigkeit bis zu 115.2 kBaud betragen kann (was die +empfehlenswerte Geschwindigkeit für eine festverdrahtete Leitung ist). + +Bei Benutzung eines Modems ist PPP sicherlich die einzige Chance. Man +sollte sich rechtzeitig die Informationen des Internet-Dienstanbieters +bereitlegen, da sie früh innerhalb des Installationsprozesses abge- +fragt werden. Minimal wird die IP-Adresse des Dienstanbieters sowie +die eigene benötigt (die aber auch freigelassen werden kann, so daß +PPP sie mit der Gegenseite aushandelt). Auch ist Kenntnis der ver- +schiedenen ,,AT''-Kommandos des benutzten Modems nötig, da das Wähl- +programm für PPP keine Kenntnisse über Modems besitzt. + +Falls eine Festverbindung zu einer anderen FreeBSD-Maschine (mit Ver- +sion 2.0R oder höher) benutzt wird, so kann man auch die Variante mit +einem ,,Laplink''-Kabel über den Parallelport in Betracht ziehen. Die +typische Datenrate über einen Parallelport ist um einiges größer als +das, was sich über serielle Leitungen erzielen läßt; Geschwindigkeiten +um die 50 KB/s sind nicht ungewöhnlich. + +Schließlich ist für eine schnellstmögliche Installation ein Ethernet- +Adapter natürlich eine gute Variante! FreeBSD unterstützt die meisten +gängigen Ethernet-Karten, wobei sich im Hardware-Wegweiser (im Menü- +punkt ,,documentation'' auf der Bootdiskette) eine Tabelle der nötigen +Einstellungen findet. Bei Nutzung eines der unterstützten PCMCIA- +Adapter muß sichergestellt sein, daß sie _vor_ dem Einschalten des +Laptops eingesteckt sind! Leider unterstützt FreeBSD gegenwärtig +keinen Austausch von PCMCIA-Karten im Betrieb. + +Natürlich benötigt man auch noch die IP-Adresse im Netzwerk, die +,,Netzwerkmaske'' für das gewählte Netzwerk, sowie den Maschinennamen. +Der lokale Systemverwalter oder Netzwerkverantwortliche kann über +diese Angaben informieren. Für den Zugriff auf andere Hosts über +Namen anstatt unhandlicher IP-Adressen ist auch noch die Adresse eines +Name-Servers und ggf. eines Gateways vonnöten (bei PPP in der Regel +der Internet-Dienstanbieter). All diese Angaben sollten man _vor_ +Beginn der Installation vom zuständigen System- oder Netzwerkverwalter +einholen. diff --git a/release/sysinstall/help/de_DE.ISO8859-1/partition.hlp b/release/sysinstall/help/de_DE.ISO8859-1/partition.hlp new file mode 100644 index 0000000..90041c0 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO8859-1/partition.hlp @@ -0,0 +1,85 @@ +Dies ist der DiskLabel-Editor von FreeBSD. + +Für Neulinge in dieser Installation ist es zuerst wichtig, FreeBSD's neues +Prinzip der ,,Slices'' zu verstehen, das auf die Plattenspeicher angewandt +wird. Es ist nicht sehr schwer. Ein ,,vollständig angegebener Slice- +Name'', d. h. der Name der Gerätedatei, die unterhalb von /dev angespro- +chen wird, um mit dem Gerät zu kommunizieren, läßt sich wahlweise in +3 Teile zerlegen: + + Das erste ist der Name der Platte. In der Annahme, daß ein + System zwei SCSI-Platten haben möge, wären das ,sd0' und + ,sd1'. + + Das nächste ist die ,,Slice''- (oder ,,primäre Partition''-) + Nummer. Wenn sd0 also z. B. zwei solche Partitions hat, eine + für FreeBSD und eine für DOS, so ergibt das sd0s1 und sd0s2. + Ist dann weiterhin sd1 völlig für FreeBSD reserviert, so hat + sie nur die Slice sd1s1. + + Wenn dann weiterhin eine Slice vom FreeBSD-Typ ist, so besitzt + diese eine Reihe (verwirrenderweise auch so genannter) ,,Par- + titions''. Diese FreeBSD-Partitions bilden die Grundlage für + die verschiedenen Dateisysteme oder den Swap-Bereich. Für die + genannte hypothetische Maschine könnte das Layout für sd0 etwa + so aussehen: + + Name Mountpunkt + ---- ---------- + sd0s1a / + sd0s1b <Swap-Bereich> + sd0s1e /usr + + Aus historischen Gründen existiert auch noch ein Kurzschluß, + eine ,,Kompatibilitäts-Slice'', mit der man einfacher auf die + erste FreeBSD-Slice einer Platte zugreifen kann. Damit + arbeiten auch die Programme, die mit dem Slice-Schema noch + nicht zurechtkommen, wie gehabt. Die Kompatibilitäts-Slice + für genannte Platte würde dann so aussehen: + + Name Mountpoint + ---- ---------- + sd0a / + sd0b <Swap-Bereich> + sd0e /usr + + Die Zuordnung der Kompatibilitäts-Slice zur ersten gefundenen + FreeBSD-Slice (in diesem Falle sd0s1) erfolgt automatisch. Es + kann mehrere FreeBSD-Slices auf einer Platte geben, aber nur + die erste wird als Kompatibilitäts-Slice zugeordnet! + + Möglicherweise wird die Kompatibilitäts-Slice später elimi- + niert, aber gegenwärtig ist sie noch aus folgenden Gründen + nötig: + + 1. Wie bereits erwähnt, kennen einige Programme noch + nicht das Slice-Prinzip und benötigen noch Zeit, + bis sie überarbeitet worden sind. + + 2. Im Moment sind die Bootblöcke von FreeBSD noch + nicht in der Lage, von irgendeinem Root-Dateisystem + außer dem in der Kompatibilitäts-Slice zu booten. + Daher wird die Root also immer auf ,,sd0a'' er- + scheinen (bezogen auf das Beispiel), auch wenn sie + sich eigentlich auf sd0s1a befindet und ansonsten + über den vollen Slice-Namen angesprochen wird. + +Sowie man diese Prinzipien verstanden hat, ist die Benutzung des Disk- +label-Editors eigentlich einfach. Entweder, man teilt die FreeBSD- +Slices, wie sie oben auf dem Bildschirm angezeigt werden, in kleinere +Stücke auf (in der Mitte des Schirmes zu sehen) und plaziert dann +später FreeBSD-Dateisysteme darauf, oder aber man mountet existierende +Slices/Partitions in die Dateisystemhierarchie; dieser Editor erlaubt +beides. Da eine DOS-Partition aus FreeBSD-Sicht auch nur eine weitere +Slice ist, kann man sie mit diesem Editor auch ganz einfach in die +Dateisystemhierarchie eingliedern. Für FreeBSD-Partitions kann man +auch noch den ,,newfs''-Status umschalten, so daß die Partitions ent- +weder von Grund auf neu-/wiedererzeugt werden oder aber einfach nur +überprüft und gemountet (wobei ihr Inhalt erhalten bleibt). + +Wenn man fertig ist, beendet man den Editor mit ,,Q''. + +Es werden keinerlei Änderungen auf die Platte geschrieben, solange man +nicht mittels ,,(C)ommit'' aus dem Installationsmenü alles bestätigt +hat! Der Disklabel-Editor (und der ,,FDISK Partition''-Editor) ar- +beiten mit einer Art Kopie der Disklabels. diff --git a/release/sysinstall/help/de_DE.ISO8859-1/slice.hlp b/release/sysinstall/help/de_DE.ISO8859-1/slice.hlp new file mode 100644 index 0000000..c2c92e2 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO8859-1/slice.hlp @@ -0,0 +1,28 @@ +Dies ist der Editor für die primären Partitions (oder ,,Slices''). + +Unten werden die möglichen Kommandos angezeigt, ober der Inhalt des Master +Boot Records. Man kann mit den Pfeiltasten nach oben und unten fahren und +mittels ,,(C)reate'' eine neue Partition anlegen, wenn sich der ,Balken' +über einer Partition befindet, deren Status als ,,unused'' markiert ist. + +Hier die Zeichenerklärung für das Feld ,,flags'': + + '=' -- Partition ist ordnungsgemäß ausgerichtet. + '>' -- Die Partition endet nicht unterhalb von Zylinder 1024. + 'R' -- Ist markiert, das Root-Dateisystem zu enthalten. + 'B' -- Partition benutzt Fehlersektorenbehandlung nach Bad144. + 'C' -- Dies ist die FreeBSD-2.0-Kompatibilitätspartition. + 'A' -- Die Partition ist als ,aktiv' (bootfähig) markiert. + +Bei der Auswahl einer Partition für Bad144-Behandlung wird diese vor +Erzeugung der Dateisystem auf fehlerhafte Stellen untersucht. + +Wenn keine Partition als ,aktiv' markiert ist, so muß man entweder einen +Boot-Manager installieren (dies wird später im Installationsprozeß ange- +boten) oder aber eine als ,aktiv' markieren, bevor man dieses Menü wieder +verläßt. + +Es werden keinerlei Änderungen auf die Platte geschrieben, solange man +nicht mittels ,,(C)ommit'' aus dem Installationsmenü alles bestätigt hat! +Der ,,FDISK Partition''-Editor (und der Disklabel-Editor) arbeiten mit +einer Art Kopie der Disklabels. diff --git a/release/sysinstall/help/de_DE.ISO8859-1/tcp.hlp b/release/sysinstall/help/de_DE.ISO8859-1/tcp.hlp new file mode 100644 index 0000000..d2a3b27 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO8859-1/tcp.hlp @@ -0,0 +1,32 @@ +In diesem Menü kann man sowohl die allgemeinen Netzwerkparameter ein- +stellen (Hostname, Domainname, DNS-Server usw.) als auch die Parameter für +ein bestimmtes Interface (das vom zuvor angezeigten Menü ausgewählt worden +ist). + +Man kann zwischen den Feldern mittels der Tasten TAB, Rückwärts-TAB (Shift+ +TAB) und RETURN hin- und herspringen. Mittels DELETE oder BACKSPACE kann +man ein Feld editieren. Mittels ^A (control-A) gelangt man an den Anfang +einer Zeile, mittels ^E (control-E) ans Ende. ^F (control-F) geht ein +Zeichen nach vorn, ^B (control-B) eins nach hinten; ^D (control-D) löscht +das Zeichen unter dem Cursor, und ^K (control-K) löscht alles bis zum Zei- +lenende. Im Prinzip handelt es sich um die wesentlichsten Emacs-Editier- +kommandos. + +Das Feld ,,Extra options to ifconfig'' ist ein wenig besonders (oder auch: +ein Hack :-). + +Damit kann man beispielsweise die Gegenseite einer SLIP- oder PLIP-Ver- +bindung angeben (einfach die numerische IP-Adresse eingeben), oder aber +einen bestimmten Steckverbinder einer Ethernetkarte auswählen, falls +mehrere zur Auswahl sind (z. B. AUI, 10BaseT [twisted pair], 10Base2 [BNC] +usw.). Die folgenden Steckverbinder werden akzeptiert: + + link0 - AUI * höchste Wertigkeit + link1 - BNC + link2 - UTP * niedrigste Wertigkeit + +Man kann also eins der Worte ,,link0'', ,,link1'' oder ,,link2'' in das +,,Extra options''-Feld eintragen. + +Am Ende einfach ,,OK'' anwählen. + diff --git a/release/sysinstall/help/de_DE.ISO8859-1/usage.hlp b/release/sysinstall/help/de_DE.ISO8859-1/usage.hlp new file mode 100644 index 0000000..a8beada --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO8859-1/usage.hlp @@ -0,0 +1,57 @@ +BENUTZUNG DES SYSTEMS +===================== + +TASTE WIRKUNG +----- ------- +PFEIL NACH OBEN Zum vorherigen Feld (oder eine Zeile nach oben im Text). +PFEIL NACH UNTEN Zum nächsten Feld (oder eine Zeile nach unten im Text). +TAB Zum nächsten Feld oder zur nächsten Gruppe. +PFEIL NACH RECHTS Zum nächsten Feld oder zur nächsten Gruppe (wie TAB). +SHIFT-TAB Zum vorherigen Feld oder zur vorherigen Gruppe. +PFEIL NACH LINKS Zum vorherigen Feld oder zur vorherigen Gruppe (wie SH-TAB). +RETURN Menüpunkt auswählen. +BILD NACH OBEN Innerhalb von Textkästen: eine Seite zurück. +BILD NACH UNTEN Innerhalb von Textkästen: eine Seite vor. +LEERTASTE In Menüs mit mehreren Auswahlmöglichkeiten: umschalten. +F1 Hilfe (sofern unterstützt). + +Wenn an den Seiten eines Menüs kleine "^(-)"- oder "v(+)"-Symbole zu +sehen sind, so bedeutet das, daß weitere Menüpunkte ober- oder unter- +halb des aktuellen Punktes existieren, die (infolge fehlenden Platzes +auf dem Bildschirm) gerade nicht dargestellt werden können. Mittels +der Pfeiltasten (nach oben oder unten) kann man das Menü rollen las- +sen. Sowie eins der Symbole verschwindet heißt das, daß man ganz oben +oder unten im Menü ist. + +In Textkästen wird die Stelle, an der man sich befindet, als Prozent- +zahl in der rechten unteren Ecke angezeigt. 100 % bedeuten, daß man +sich am Ende befindet. + +Die Auswahl von ,,OK'' in einem Menü bewirkt die durch dieses Menü +ausgelöste Handlung. Die Auswahl von ,,Cancel'' bewirkt einen Abbruch +und die Rückkehr zum vorherigen Menü. + +BESONDERE EIGENSCHAFTEN +======================= + +Menüpunkte können auch durch Eintippen des ersten Zeichens ihres +Namens ausgewählt werden, sofern dies eindeutig ist. In diesem Falle +werden die entsprechenden Zeichen hervorgehoben. + +Der Bildschirmtreiber enthält auch einen Puffer, mit dem man sich die +Sachen ansehen kann, die bereits herausgerollt worden sind. Um diese +Funktion zu nutzen, muß man die ,,ScrollLock''-Taste (,,Rollen V'') +drücken und danach die Pfeiltasten oder die Bild-auf/ab-Tasten. +Dieser Modus wird durch nochmaliges Drücken der ,,ScrollLock''-Taste +wieder verlassen. Diese Möglichkeit ist vor allem nützlich für +Subshells oder andere ,,Expertenmodi'', die keine Menüs nutzen. + +Sowie das System vollständig installiert ist und im Multi-User-Modus +läuft, werden mehrere ,,virtuelle Terminals'' aktiviert, auf denen man +parallel mehrere aktive Sessions bedienen kann. Mittels ALT-F<n> kann +zwischen diesen umgeschaltet werden, wobei ,,F<n>'' die Funktionstaste +(F-Taste) ist, die der Nummer des gewünschten Bildschirms entspricht. +Das System kommt vorkonfiguriert mit 3 virtuellen Terminals. Wenn +mehr davon gewünscht werden, so kann dies nach dem Hochfahren des +Systems geschehen, indem man sie in der Datei /etc/ttys freischaltet. +Die maximale Anzahl ist 12. diff --git a/release/sysinstall/help/de_DE.ISO_8859-1/README b/release/sysinstall/help/de_DE.ISO_8859-1/README new file mode 100644 index 0000000..8ce9c18 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO_8859-1/README @@ -0,0 +1,106 @@ + + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Version , , + ----------------------------------------- /( )` + \ \___ / | +Willkommen zum Release 2.0.5 von FreeBSD, einem /- _ `-/ ' +Zwischen-Release von FreeBSD, das eine eine Lücke (/\/ \ \ /\ +füllt zwischen 2.0R (das im Nov. 94 erschien) und / / | ` \ +2.1R, das Ende Juli '95 erscheinen wird, die oft O O ) / | +beklagt wurde. FreeBSD 2.0.5 enthält wesentliche `-^--'`< ' +Verbesserungen gegenüber 2.0R, deren wichtigste (_.) _ ) / +eine erhöhte Systemstabilität (wesentlich besser), `.___/` / +Dutzende neuer Features und ein stark `-----' / +verbessertes Installationsprogramm <----. __ / __ \ +sind. Die Release Notes enthalten <----|====O)))==) \) /==== +weitere Details bzgl. der Neuheiten <----' `--' `.__,' \ +in FreeBSD 2.0.5. | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + + +Was ist FreeBSD? FreeBSD ist ein 4.4BSD-Lite-basiertes Betriebssystem für +Intel, AMD, Cyrix oder NexGen "x86"-PC-Hardware. Es arbeitet mit einer +großen Anzahl von PC-Peripherie und -Konfigurationen zusammen. Es kann für +die Software-Entwicklung bis hin zum Anbieten von Internet-Diensten +eingesetzt werden; der meist genutzte Rechner im Internet, ftp.cdrom.com, +ist ein FreeBSD-Rechner. + +Dieses FreeBSD-Release enthält alles, was man zur Nutzung eines solchen +Systems braucht; zusätzlich erhält man den kompletten Quellcode. Wenn man +den Quellcode installiert hat, kann man das ganze Betriebssystem von Grund +auf mit einem einzigen Befehl übersetzen; dies eignet es in idealer Weise +für Studenten, Forscher oder einfach Leute, die sehen wollen, wie alles +funktioniert. + +Es gibt ebenfalls eine große Anzahl portierter Dritt-Software (die "ports +collection"), um die Verfügbarkeit und die Installation traditioneller +Lieblings-UNIX-Utilities für FreeBSD zu erleichtern. Über 270 Portierun- +gen, von Editoren über Programmiersprachen bis zu Grafikanwendungen, machen +FreeBSD zu einem mächtigen und umfassenden Betriebssystem, das keinen +Vergleich zu dem großer Workstations scheut. + +Als weitere Dokumentation zu diesem System empfehlen wir die 4.4BSD- +Dokumentation von O'Reilly Associates und der USENIX Association, ISBN +1-56592-082-1. Wir haben nichts mit O'Reilly zu tun, außer daß wir +zufriedene Kunden sind! + +Wir empfehlen, die HARDWARE-ANLEITUNG *vor* jeglicher Fortführung der +Installation zu lesen. PC-Hardware für irgend etwas anderes als DOS/ +Windows (das keine großen Anforderungen an die Hardware stellt) zu +konfigurieren, ist schwieriger, als es zunächst aussieht. Und wenn man +glaubt, PCs zu verstehen, dann hat man diese nur noch nicht lange genug +benutzt. :) Diese Anleitung gibt einige Tips zur Hardwarekonfiguration und +sagt, auf welche Symptome man bei Schwierigkeiten achten muß. Die Anlei- +tung ist im Dokumentations-Menü der FreeBSD-Bootfloppy verfügbar. + +VORBEHALT: Obwohl FreeBSD alles versucht, vorhandene Daten gegen versehent- +lichen Verlust zu schützen, ist es mit dieser Installation mehr als nur +möglich, DIE GESAMTE FESTPLATTE ZU LÖSCHEN! Bitte nicht mit der endgül- +tigen Installation von FreeBSD fortfahren, ohne zuerst alle wichtigen Daten +angemessen gesichert zu haben! Wir empfehlen es eindringlichst! + +Technische Kommentare zu diesem Release sollten an: + + hackers@FreeBSD.org + +gesandt werden (wenn möglich, in englisch). + +Fehlermeldungen sollten bei erfolgreicher Installation mittels des +`send-pr'-Kommandos, ansonsten an: + + bugs@FreeBSD.org + +gesandt werden. + +Bitte in jeder Fehlermeldung die genutzte FreeBSD-VERSION nennen! + +Allgemeine Fragen sollten an: + + questions@FreeBSD.org + +gesandt werden. + +Wir bitten um Geduld, wenn die Fragen nicht sofort beantwortet werden - +dieses sind besonders arbeitsintensive Zeiten für uns, und unsere Resourcen +(auf freiwilliger Basis) sind oft bis an die Grenzen ausgereizt! Mittels +send-pr verschickte Fehlermeldungen werden registriert und in unserer +Datenbank verfolgt. Über Statusänderungen wird über die gesamte Lebensdauer +des Fehlers (oder der Forderung nach einem Feature) informiert. + +Unsere WEB Site, http://www.freebsd.org, ist ebenfalls eine gute Quelle +für neue Informationen und enthält einige weitere, fortführende Infor- +mationen. Man kann die BSDI-Version von Netscape zum Browsen (Blättern) +im World Wide Web direkt aus FreeBSD heraus nutzen. + +Wir empfehlen auch in /usr/share/FAQ und /usr/share/doc zu weiteren +Informationen zum System nachzuschauen. + +Wir danken für die Aufmerksamkeit und hoffen, daß dieses Release von +FreeBSD viel Freude bereitet. + + Jordan Hubbard, + für das FreeBSD Projekt diff --git a/release/sysinstall/help/de_DE.ISO_8859-1/RELNOTES b/release/sysinstall/help/de_DE.ISO_8859-1/RELNOTES new file mode 100644 index 0000000..c3d2aa6 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO_8859-1/RELNOTES @@ -0,0 +1,766 @@ + RELEASE NOTES + FreeBSD + Release 2.0.5 + +1. Technischer Überblick +------------------------ + +FreeBSD ist eine im Quellcode frei verfügbare Version eines 4.4-Lite- +basierten Betriebssystems für PC's auf der Basis von Intel-i386/i486/ +Pentium-Prozessoren (oder kompatiblen). Es basiert hauptsächlich auf +Software der Computer-Gruppe (CSRG) der Universität Kalifornien Berkeley +mit einigen Erweiterungen aus den Systemen NetBSD, 386BSD und von der +Free Software Foundation. + +Seit der Freigabe unserer Version FreeBSD 2.0 vor etwa 8 Monaten hat sich +die Leistungsfähigkeit, der Funktionsumfang und die Stabilität von +FreeBSD dramatisch verbessert. Die umfangreichste Änderung ist das neu +gefaßte System der virtuellen Speicherverwaltung (VM) mit einem vereinig- +ten VM/Dateipuffer, wodurch sich nicht nur die Leistungsfähigkeit verbes- +sert, sondern auch der Mindestspeicherbedarf von FreeBSD reduziert werden +konnte, so daß auch Konfigurationen mit nur 4 MB Hauptspeicher wieder +akzeptabel werden können. Unter den weiteren Verbesserungen befinden +sich volle Unterstützung für NIS sowohl auf Client- als auch Serverseite, +,,Transaction TCP'', PPP mit automatischer Leitungswahl bei Bedarf, ein +verbessertes SCSI-Subsystem, anfängliche ISDN-Unterstützung, Treiber für +FDDI- und "Fast Ethernet"-Adapter (100 MBit/s), verbesserter Unter- +stützung der Adaptec 2940-SCSI-Adapter (sowohl WIDE- als auch +Normal-SCSI) sowie viele hunderte Bugfixes. + +Zuzüglich zur Basis-Distribution bietet FreeBSD nun eine neue Sammlung +portierter Software an mit etwa 270 häufig gewünschten Programmen. Die +Liste der ,,Ports'' reicht dabei von HTTP-(WWW-)Servern, Spielen, Pro- +grammiersprachen, Editoren und so gut wie allem, was dazwischenliegt. +Die komplette Port-Sammlung benötigt nun nur noch 10 MB Speicherplatz, da +alle Ports als ,,Deltas'' gegenüber ihren originalen Quellen ausgedrückt +werden. Das macht es uns einfacher, die Ports auf dem Laufenden zu +halten, und es reduziert gegenüber der Ports-Sammlung aus Version 1.0 +drastisch den Speicherbedarf. Um einen Port zu übersetzen, wechselt man +einfach ins Verzeichnis des gewünschten Ports, tippt ,,make'' ein, und +läßt das System den Rest vornehmen. Es wird dabei automatisch die komp- +lette Original-Quelle von der CDROM oder einem lokalen FTP-Server geholt, +so daß man lediglich hinreichend Plattenplatz benötigt, um die gewünsch- +ten Ports zu übersetzen. (Fast) jeder Port wird auch als vorübersetztes +,,Package'' zur Verfügung gestellt, das man mit einem einfachen Kommando +(pkg_add) installieren kann, wenn man nicht von der originalen Quelle +übersetzen möchte. All dies ist in der Datei + /usr/share/FAQ/Text/ports.FAQ +genauer beschrieben. + +Seit unserer ersten Version FreeBSD 1.0 vor etwa zwei Jahren hat sich +FreeBSD fast vollständig geändert. Eine neue Portierung wurde vorge- +nommen, ausgehend vom 4.4-Lite-Code der Universität Berkeley, womit der +rechtliche Status des Systems einwandfrei geworden ist, einschließlich +einer ,Absegnung' durch Novell (dem neuen Eigentümer der USL und des +Warenzeichens UNIX). Die 4.4-Portierung brachte gleichzeitig eine Menge +neuer Eigenschaften, Dateisysteme und verbesserte Treiber. Mit der +geklärten Rechtslage haben wir nun allen Grund zur Hoffnung, daß wir ohne +künftige juristische Querelen auch weiterhin ein Betriebssystem von guter +Qualität regelmäßig herausgeben können. + +FreeBSD 2.0.5 representiert die zweijährige Arbeit eines internationalen +Entwicklerteams, das viele tausend Mann-Stunden eingebracht hat. Wir +hoffen sehr, daß es Anklang findet! + +Eine Reihe weiterer Dokumente, die während der Installation und im Betrieb +von FreeBSD hilfreich sein können, befindet sich im Verzeichnis ,,FAQ'', +entweder in einem installierten System unter /usr/share/FAQ, oder aber in +der obersten Ebene der CDROM- oder FTP-Distribution, in der ebendiese Datei +zu finden ist. Ein Überblick der im FAQ-Verzeichnis enthaltenen Dokumen- +tation befindet sich in der Datei FAQ/Text/ROADMAP. + +Eine Liste all derjenigen, die zum Projekt beigetragen haben, verbunden +mit einer allgemeinen Beschreibung des Projektes selbst, befindet sich in +der Datei ,,CONTRIB.FreeBSD'' in der Binär-Distribution. + +Die Datei ,,REGISTER.FreeBSD'' enthält eine Beschreibung, wie man sich +beim "Free BSD user counter" registrieren läßt. Dieser Zähler ist für +ALLE freien BSD-Derivate, nicht nur FreeBSD, und wir legen jedem die +Anmeldung dort nahe. + +Die Kerndistribution von FreeBSD enthält keinen DES-Code, weil dies ihren +Export außerhalb der USA verhindern würde. Es existiert ein Zusatzpaket, +das nur in den USA verwendet werden darf und die Programme zusammenfaßt, +die normalerweise DES benutzen. Alle anderen zusätzlich angebotenen +Pakete können von jedermann genutzt werden. Eine freie und (aus Sicht +von außerhalb der USA) exportierbare Distribution für Nicht-US-Benutzer +existiert aber auch. Sie ist in der FreeBSD-FAQ beschrieben. + +Soweit jedoch die Paßwortsicherheit alles ist, was gewünscht wird, und +kein Bedarf besteht, die verschlüsselten Paßwörter zwischen verschiedenen +Architekturen (Sun's, DEC-Maschinen usw.) auszutauschen, ist das von +FreeBSD benutzte, auf einer MD5-Verschlüsselung aufsetzende Sicherheits- +system völlig ausreichend! Wir sind der Meinung, daß unser standard- +mäßiges Sicherheitsmodell mehr als ein Ausgleich für DES ist, und das, +ohne daß wir uns mit ärgerlichen Exportbeschränkungen herumschlagen +müßten. Es ist einen Versuch wert, für alle außerhalb (oder sogar auch +innerhalb) der USA! (Anm.: MD5 implementiert keine Verschlüsselung im +Sinne der amerikanischen Exportbestimmungen, sondern kann ausschließ- +lich zur Zugangskontrolle verwendet werden. Damit fällt es nicht unter +die Exportbeschränkungen der USA. -- Jörg) + + +1.1 Was ist neu in 2.0.5? +------------------------- + +Die folgenden Funktionen wurden im Zeitraum zwischen der Freigabe von +Version 2.0 und dieser Version 2.0.5 entweder hinzugefügt oder grundle- +gend verbessert. Um eine bessere Kommunikation zu ermöglichen, ist die +Person (oder die Personen), die für die jeweilige Verbesserung verant- +wortlich ist, aufgelistet. Jegliche Fragen bezüglich der neuen Funkiona- +lität sollte zuerst an denjenigen gerichtet werden. + + +KERNEL: + +Vereinigter VM/Dateipuffer-Cache +-------------------------------- +Der Entwurf eines vereinten VM/Dateipuffer-Caches verbessert die gesamte +Leistungsfähigkeit des Systems erheblich und erlaubt eine Reihe optimier- +ter Speicherbelegungsstrategien, die vorher unmöglich waren. + +Verantwortlich: David Greenman (davidg@FreeBSD.org) and + John Dyson (dyson@implode.root.com) + + +Optimierter Hash-Algorithmus für Netzwerk-Protokollsteuerblöcke (PCB's) +----------------------------------------------------------------------- +Für Systeme mit einer großen Anzahl aktiver TCP-Verbindungen (z. B. +WEB- und FTP-Server) wird dadurch die Suche für ein ankommendes Paket +nach der dazugehörigen Verbindung erheblich beschleunigt. + +Verantwortlich: David Greenman (davidg@FreeBSD.org) + + +Optimierung des Dateinamen-Caches +--------------------------------- +Der Namens-Cache faßt nunmehr alle gleichen Namen im gleichen Speicher- +block zusammen, so daß z. B. alle ,,..''-Einträge im gleichen Block +landen. Die Version für das Elternverzeichnis wurde einbezogen, um +den Hash durcheinanderzubringen, und die Cache-Verwaltung wurde ver- +bessert, da gerade an diesem Teil gearbeitet wurde. + +Verantwortlich: Poul-Henning Kamp (phk@FreeBSD.org) + David Greenman (davidg@FreeBSD.org) + + +Weniger einschränkende Konfigurierung von Swap-Bereichen +-------------------------------------------------------- +Die Notwendigkeit, die Namen der Swap-Geräte in den Kernel zu kompilie- +ren, wurde beseitigt. ,swapon' akzeptiert numehr jedes Block-Gerät bis +zur Maximalzahl der in den Kernel konfigurierten Swap-Geräte. + +Verantwortlich: Poul-Henning Kamp (phk@FreeBSD.org) + David Greenman (davidg@FreeBSD.org) + + +,,Vorverdrahtete'' SCSI-Geräte +------------------------------ +FreeBSD-Versionen vor 2.0.5 haben die Gerätenummernzuweisung für SCSI- +Geräte ausschließlich dynamisch vorgenommen in der Reihenfolge, wie die +Geräte gefunden wurden, so daß infolge Fehlfunktion eines SCSI-Gerätes +sich möglicherweise die Gerätenummer ändern konnte. Dieses hatte zur +Folge, daß selbst die Zuordnung der Dateisysteme auf den noch funktio- +nierenden Geräten nicht mehr möglich war und die Dateisysteme nicht +gemountet werden konnten. Durch ,,Vorverdrahtung'' ist es jetzt möglich, +statisch die Zuordnung zwischen Gerätenummern (und damit Gerätenamen) und +SCSI-Geräten vorzunehmen, wobei die SCSI-ID und die Nummer des SCSI- +Busses als Basis dienen. Diese Zuordnung wird in der Konfigurations- +datei des Kernels vorgenommen und ist sowohl in der Manual-Seite scsi(4) +als auch in der LINT-Beispielkonfiguration dokumentiert. + +Verantwortlich: Peter Dufault (dufault@hda.com) +Betroffene Dateien: sys/scsi/* usr.sbin/config/* + + +Unterstützung für ,,Slices'' +---------------------------- +FreeBSD unterstützt nunmehr die Abstraktion von ,,Slices'' (globalen +Platten-Partitionen), so daß die Zusammenarbeit mit Partitionen anderer +Betriebssysteme verbessert wird. Damit ist es FreeBSD möglich, vor- +handene DOS-Partitionen (ohne weitere Vorkehrungen) mitzunutzen. + +Verantwortlich: Bruce Evans (bde@FreeBSD.org) +Betroffene Dateien: sys/disklabel.h sys/diskslice.h sys/dkbad.h + kern/subr_diskslice.c kern/subr_dkbad.c + i386/isa/diskslice_machdep.c + i386/isa/wd.c scsi/sd.c dev/vn/vn.c + + +Unterstützung für Version 6.0 des OnTrack Disk-Managers +------------------------------------------------------- +Es wurde die Möglichkeit geschaffen, Platten zu nutzen, die durch den +OnTrack Disk-Manager verwaltet werden. Das fdisk-Programm jedoch weiß +darüber noch nichts, so daß alle Änderungen entweder im Installations- +programm der Bootdiskette (boot.flp) oder aber im OnTrack Disk-Manager +aus DOS heraus vorgenommen werden müssen. + +Verantwortlich: Poul-Henning Kamp (phk@FreeBSD.org) + + +Bad144 ist wieder da und funktioniert +------------------------------------- +Bad144 funktioniert wieder. Die Semantik jedoch hat sich gegenüber +früher geringfügig geändert. Die Fehlerstellen werden nunmehr relativ +zur ,,Slice'' gezählt und nicht mehr absolut bezüglich der ganzen +Platte. + +Verantwortlich: Bruce Evans (bde@FreeBSD.org) + Poul-Henning Kamp (phk@FreeBSD.org) + + +UNTERSTÜTZUNG NEUER GERÄTE: + + SCSI- und CDROM-Geräte + +Matsushita/Panasonic (Creative) CD-ROM-Treiber +---------------------------------------------- +Die Laufwerke Matsushita/Panasonic CR-562 und CR-563 werden nunmehr +unterstützt, wenn sie an einen SoundBlaster- oder 100% kompatiblen +Hostadapter angeschlossen sind. Bis zu vier Hostadapter sind möglich, so +daß maximal 16 CD-ROM-Laufwerke angeschlossen werden können. Die +Audio-Funktionen sind ebenfalls unterstützt einschließlich des ,,Karoke +variable speed playback''. + +Verantwortlich: Frank Durda IV bsdmail@nemesis.lonestar.org +Betroffene Dateien: isa/matcd + + +Adaptec 2742/2842/2940 SCSI-Treiber +----------------------------------- +Der originale Treiber für 274X-/284X-Adapter wurde gegenüber der Version +2.0 beträchtlich geändert. Nunmehr gibt es auch volle Unterstützung der +2940-Serie sowie der ,,Wide-SCSI''-Modelle dieser Karten. Der Bug in der +Bus-Arbitrierung (sowie viele weitere) wurde beseitigt, der Treiberprob- +leme mit schnellen SCSI-Geräten verursacht hat. Es existiert sogar eine +experimentelle Unterstützung für ,,tagged queuing'' (Kernel-Option +,,AHC_TAGENABLE''). Weiterhin hat John Aycock den Code für den Sequen- +cer nunmehr mit einem ,,Berkeley''-Copyright freigegeben, so daß die +Restriktionen der GPL nicht mehr auf den Treiber zutreffen. + +Verantwortlich: Justin Gibbs (gibbs@FreeBSD.org) +Betroffene Dateien: isa/aic7770.c pci/aic7870.c i386/scsi/* + sys/dev/aic7xxx/* + + +NCR5380/NCR53400 SCSI ("ProAudio Spectrum") Treiber +--------------------------------------------------- +Verantwortlich: Core-Team +Eingereicht von: Serge Vakulenko (vak@cronyx.ru) +Betroffene Dateien: isa/ncr5380.c + + +Sony CDROM-Treiber +------------------ +Verantwortlich: Core-Team +Eingereicht von: Mikael Hybsch (micke@dynas.se) +Betroffene Dateien: isa/scd.c + + + Serielle Geräte + +Treiber für SDL Communications Riscom/8 Serial Board +---------------------------------------------------- +Verantwortlich: Andrey Chernov (ache@FreeBSD.org) +Betroffene Dateien: isa/rc.c isa/rcreg.h + + +Treiber für Cyclades Cyclom-y Serial Board +------------------------------------------ +Verantwortlich: Bruce Evans (bde@FreeBSD.org) +Eingereicht von: Andrew Werple (andrew@werple.apana.org.au) and + Heikki Suonsivu (hsu@cs.hut.fi) +Entnommen aus: NetBSD +Betroffene Dateien: isa/cy.c + + +Serieller Treiber Cronyx/Sigma sync/async-Geräte +------------------------------------------------ +Verantwortlich: Core-Team +Eingereicht von: Serge Vakulenko +Betroffene Dateien: isa/cronyx.c + + + + Netzwerk + +Plattenloses Booten +------------------- +Das plattenlose Booten wurde in Version 2.0.5 stark verbessert. Das +Boot-Programm befindet sich in src/sys/i386/boot/netboot und kann sowohl +von MSDOS aus gestartet als auch in einen EPROM gebrannt werden. Lokales +Swappen ist ebenfalls möglich. Gegenwärtig werden Ethernet-Karten von +WD, SMC, 3Com und Novell unterstützt. + + +Treiber für DEC DC21140 ,,Fast Ethernet''-Adapter +------------------------------------------------- +Dieser Treiber unterstützt die zahlreichen Netzwerkadapter auf Basis +des DEC DC21140-Chipsatzes einschließlich der 100 MBit/s DEC-500-XA und +SMC 9332. + +Verantwortlich: Core-Team +Eingereicht von: Matt Thomas (thomas@lkg.dec.com) +Betroffene Dateien: pci/if_de.c pci/dc21040.h + +Treiber für DEC FDDI (DEFPA/DEFEA) +---------------------------------- +Verantwortlich: Core-Team +Eingereicht von: Matt Thomas (thomas@lkg.dec.com) +Betroffene Dateien: pci/if_pdq.c pci/pdq.c pci/pdq_os.h pci/pdqreg.h + + +Treiber für 3Com 3c505 (Etherlink/+) Karten +------------------------------------------- +Verantwortlich: Core-Team +Eingereicht von: Dean Huxley (dean@fsa.ca) +Entnommen aus: NetBSD +Betroffene Dateien: isa/if_eg.c + + +Treiber für die Fujitsu-MB86960A-Netzwerkkarten-Familie +------------------------------------------------------- +Verantwortlich: Core-Team +Eingereicht von: M.S. (seki@sysrap.cs.fujitsu.co.jp) +Betroffene Dateien: isa/if_fe.c + + +Treiber für Intel EtherExpress +------------------------------ +Verantwortlich: Rodney W. Grimes (rgrimes@FreeBSD.org) +Betroffene Dateien: isa/if_ix.c isa/if_ixreg.h + + +Treiber für 3Com 3c589 +---------------------- +Verantwortlich: Core-Team +Eingereicht von: "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp), + Seiji Murata (seiji@mt.cs.keio.ac.jp) and + Noriyuki Takahashi (hor@aecl.ntt.jp) +Betroffene Dateien: isa/if_zp.c + + +Treiber für IBM-Kreditkarten +---------------------------- +Verantwortlich: Core-Team +Eingereicht von: "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp) +Betroffene Dateien: isa/pcic.c isa/pcic.h + + +Treiber für EDSS1- und 1TR6-ISDN-Interface +------------------------------------------ +Verantwortlich: Core-Team +Eingereicht von: Dietmar Friede (dfriede@drnhh.neuhaus.de) and + Juergen Krause (jkr@saarlink.de) +Betroffene Dateien: gnu/isdn/* + + + Diverse Treiber + +Treiber für Joystick +-------------------- +Verantwortlich: Jean-Marc Zucconi (jmz@FreeBSD.org) +Betroffene Dateien: isa/joy.c + + +Treiber für National Instruments "LabPC" +---------------------------------------- +Verantwortlich: Peter Dufault (dufault@hda.com) +Betroffene Dateien: isa/labpc.c + + +Treiber für WD7000 +------------------ +Verantwortlich: Olof Johansson (offe@ludd.luth.se) + + +Pcvt-Console-Treiber +-------------------- +Verantwortlich: Jörg Wunsch (joerg@FreeBSD.org) +Eingereicht von: Hellmuth Michaelis (hm@altona.hamburg.com) +Betroffene Dateien: isa/pcvt/* usr.sbin/pcvt/* + + +BSD-audio Emulator für den VAT-Treiber +-------------------------------------- +Verantwortlich: Amancio Hasty (ahasty@FreeBSD.org) and + Paul Traina (pst@FreeBSD.org) +Betroffene Dateien: isa/sound/vat_audio.c isa/sound/vat_audioio.h + + +Treiber für National Instruments AT-GPIB and AT-GPIB/TNT GPIB +------------------------------------------------------------- +Verantwortlich: Core-Team +Eingereicht von: Fred Cawthorne (fcawth@delphi.umd.edu) +Betroffene Dateien: isa/gpib.c isa/gpib.h isa/gpibreg.h + + +Treiber für Genius GS-4500 Handscanner +-------------------------------------- +Verantwortlich: Core-Team +Eingereicht von: Gunther Schadow (gusw@fub46.zedat.fu-berlin.de) +Betroffene Dateien: isa/gsc.c isa/gscreg.h + + +CORTEX-I Frame Grabber +---------------------- +Verantwortlich: Core-Team +Eingereicht von: Paul S. LaFollette, Jr. +Betroffene Dateien: isa/ctx.c isa/ctxreg.h + + +Video Spigot video capture card +------------------------------- +Verantwortlich: Jim Lowe + + + +1.2 Experimentelle Funktionalität +--------------------------------- + +Von den Dateisystemen unionfs und LFS ist bekannt, daß sie in Version +2.0.5 stark mangelhaft sind. Das ist teilweise alten Bugs geschuldet, zu +deren Beseitigung wir noch keine Zeit gefunden haben, sowie der noch +ausstehenden Umstellung auf das neue VM-System. Wir hoffen, daß wir +diese Probleme ein einer späteren Version von FreeBSD beseitigen können. + +FreeBSD kann nunmehr Binaries laufen lassen, die dem iBCS2-Standard ge- +nügen. (SCO UNIX 3.2.2 & 3.2.4 und ISC 2.2 COFF-Format sind gegenwärtig +unterstützt.) Der iBCS2-Emulator befindet sich noch in seinen Anfängen, +aber er funktioniert. Wir haben noch keine erschöpfenden Tests vornehmen +können (mangels kommerzieller Applikationen), aber beinahe alle Binaries +für SCO 3.2.2 laufen, so z. B. ein altes INFORMIX-2.10 für SCO. Zur +Vervollständigung dieses Projektes sind weitere Tests nötig. Es sind +weiterhin Arbeiten im Gange, um ELF- und XOUT-Programme starten zu kön- +nen. Der Großteil der ,,system call wrapper'' für SVR4 ist bereits ge- +schrieben. + +FreeBSD implementiert mittlerweile auch genügend Linux-Kompatibilität, +um DOOM laufen zu lassen! Für eine vollständige Dokumentation, wie +dies einzurichten ist, kann man im Verzeichnis ,,xperimnt'' (auf dem +lokalen FTP-Server oder der CDROM) nachsehen. + +Verantwortlich: Søren Schmidt (sos) & Sean Eric Fagan (sef) +Betroffene Dateien: sys/i386/ibcs2/* sowie diverse Kernelmodifikationen +======= + + +2. Unterstützte Konfigurationen +------------------------------- + +FreeBSD läuft derzeit auf einer großen Vielfalt von ISA-, VLB-, EISA- und +PCI-Bus-basierten PC's, beginnend beim 386sx bis hin zu Maschinen der +Pentium-Klasse (obwohl der 386sx nicht zu empfehlen ist). Es gibt Unter- +stützung für allgemeine IDE- oder ESDI-Laufwerke, verschiedene SCSI- +Controller, Netzwerk- und serielle Karten. + +Nachfolgend eine Liste aller Platten-Controller und Ethernet-Karten, von +denen gegenwärtig bekannt ist, daß sie mit FreeBSD zusammenarbeiten. +Andere Konfigurationen können ebenfalls funktionieren, wir haben ledig- +lich darüber noch nichts erfahren. + + +2.1. Platten-Controller + +WD1003 (beliebige MFM/RLL) +WD1007 (beliebige IDE/ESDI) +WD7000 +IDE +ATA + +Adaptec 152x Serie ISA SCSI-Controller +Adaptec 154x Serie ISA SCSI-Controller +Adaptec 174x Serie EISA SCSI-Controller, Standard und ,,Enhanced'' Mode. +Adaptec 274X/284X/2940 (Narrow/Wide/Twin) Serie ISA/EISA/PCI SCSI-Controller +Adaptec AIC-6260- und AIC-6360-basierte Karten, einschließlich AHA-152x +und SoundBlaster SCSI-Karten. + +** Anmerkung: Von den Soundblaster-Karten kann nicht gebootet werden, da +sie kein BIOS besitzen, was Voraussetzung wäre, um das Boot-Gerät in das +System-BIOS abzubilden. Sie sind jedoch ohne weiteres benutzbar für +externe Bandlaufwerke, CDROM's usw. Gleiches trifft auf AIC-6x60- +basierte Karten ohne Boot-ROM zu. Manche dieser Karten besitzen jedoch +einen Boot-ROM, was man allgemein an irgendeiner Mitteilung beim System- +start nach dem Einschalten oder einem Reset erkennen kann. Im Zweifels- +falle sollte man die Systemdokumentation konsultieren. + +[Hinweis: Buslogic nannte sich früher ,,Bustec''] +Buslogic 545S & 545c +Buslogic 445S/445c VLB SCSI-Controller +Buslogic 742A, 747S, 747c EISA SCSI-Controller. +Buslogic 946c PCI SCSI-Controller +Buslogic 956c PCI SCSI-Controller + +NCR 53C810 und 53C825 PCI SCSI-Controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI-Controller. + +DTC 3290 EISA SCSI-Controller in 1542 Emulations-Mode. + +UltraStor 14F, 24F und 34F SCSI-Controller. + +Seagate ST01/02 SCSI-Controller. + +Future Domain 8xx/950 Serie SCSI-Controller. + +Für alle unterstützten SCSI-Controller wird volle Unterstützung für alle +SCSI-I- und SCSI-II-Peripherie gewährt, einschließlich Platten, Bandlauf- +werke (auch DAT) und CD-ROM-Laufwerke. + +Folgende CD-ROM-Systeme sind derzeit unterstützt: + +(cd) SCSI (auch ProAudio Spectrum und SoundBlaster SCSI) +(mcd) Mitsumi Interface-Karte +(matcd) Matsushita/Panasonic (Creative) Interface-Karte +(scd) Sony Interface-Karte + +Hinweis: CD-Laufwerke mit IDE-Interface sind derzeit noch nicht unter- +stützt. + +Einige Controller sind hinsichtlich ihrer Kommunikation mit mehr als 16 +MB Hauptspeicher eingeschränkt, da der ISA-Bus nur 24 Bit Adreßraum +besitzt und folglich nur 16 MB adressieren kann. Dies trifft selbst auf +einige EISA-Adapter zu (die an sich 32 Bit Adreßraum haben), wenn sie auf +ISA-Emulation geschaltet werden, weil sie dies dann in *jeder* Hinsicht +tun. Diese Probleme treten nicht mit IDE-Adaptern auf (da sie kein DMA +vornehmen), echten EISA-Controllern (wie UltraStor, Adaptec 1742A oder +Adaptec 2742) sowie den meisten VLB-(Local-Bus)-Controllern. Sowie es +notwendig wird, belegt das System ,,bounce buffer'', um mit den Adaptern +zu kommunizieren, so daß es dennoch möglich ist, mehr als 16 MB Haupt- +speicher problemlos zu nutzen. + + +2.2 Ethernet-Karten + +SMC Elite 16 WD8013 Ethernet-Interfaces, sowie die meisten anderen +WD8003E-, WD8003EBT-, WD8003W-, WD8013W-, WD8003S-, WD8003SBT- and +WD8013EBT-basierten Clones. SMC Elite Ultra wird ebenfalls unterstützt. + +DEC EtherWORKS III NICs (DE203, DE204, and DE205) +DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) +DEC DC21140 based NICs (SMC???? DE???) +DEC FDDI (DEFPA/DEFEA) NICs + +Fujitsu MB86960A Familie + +Intel EtherExpress + +Isolan AT 4141-0 (16 bit) +Isolink 4110 (8 bit) + +Novell NE1000, NE2000, und NE2100 Ethernet-Interface. + +3Com 3C501 Karten + +3Com 3C503 Etherlink II + +3Com 3c505 Etherlink/+ + +3Com 3C507 Etherlink 16/TP + +3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III + +Toshiba Ethernet-Karten + +PCMCIA Ethernet-Karten von IBM und National Semiconductor werden +ebenfalls unterstützt. + + +2.3. Verschiedenes + +AST 4-Port serielle Karten unter Nutzung von ,,shared interrupt''. + +ARNET 8-Port serielle Karten unter Nutzung von ,,shared interrupt''. + +BOCA ATIO66 6-Port serielle Karten unter Nutzung von ,,shared interrupt''. + +Cyclades Cyclom-y Serial Board. + +STB 4-Port serielle Karten unter Nutzung von ,,shared interrupt''. + +Mitsumi (alle Modelle) CDROM-Interface und -Laufwerk. + +SDL Communications Riscom/8 Serial Board. + +Soundblaster SCSI und ProAudio Spectrum SCSI CDROM-Interface und -Laufwerk. + +Matsushita/Panasonic (Creative SoundBlaster) CDROM-Interface und -Laufwerk. + +Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound +und Roland MPU-401 Sound-Karten. + +FreeBSD unterstützt derzeit KEINE IBM-Microchannel (MCA) Bussysteme, +jedoch ist die Unterstützung nahe an der Fertigstellung. Einzelheiten +werden gepostet sowie sich die Situation entwickelt. + + +3. Wie kann man FreeBSD bekommen? +--------------------------------- + +FreeBSD kann man in einer Vielzahl von Möglichkeiten erhalten: + +1. FTP/Mail + +FreeBSD selbst oder all seine wahlfreien Pakete können per ftp von +,ftp.freebsd.org' bezogen werden -- der offiziellen Vertriebsstelle von +FreeBSD. + +Server, die diese Site spiegeln, sind in der Datei MIRROR.SITES aufge- +listtet. Es wird darum gebeten, die Distribution von der netzwerkmäßig +nächstgelegenen Site zu beziehen. + +Für diejenigen ohne direkten Internetzugang, aber mit der Möglichkeit, +eMail zu empfangen, steht der Weg über ,ftpmail@decwrl.dec.com' offen. +Einfach das Schlüsselwort ,,help'' als Mail dorthin schicken, und man +bekommt eine genaue Information, wie man Dateien von ,ftp.freebsd.org' +beziehen kann. Achtung: diese Variante führt zum Versenden einiger *zehn +Megabyte* über Mail und sollte daher wirklich nur als allerletzte +Möglichkeit in Betracht gezogen werden! + + +2. CDROM + +FreeBSD 2.0.5 kann man auf CDROM bestellen bei: + + Walnut Creek CDROM + 4041 Pike Lane, Suite D + Concord CA 94520 + +1-510-674-0783, +1-510-674-0821 (Fax) + +Oder über Internet bei orders@cdrom.com oder http://www.cdrom.com. +Der aktuelle Katalog kann mittels FTP bezogen werden als + ftp://ftp.cdrom.com/cdrom/catalog. + +Die CDROM kostet US-$ 39.95. Der Versand kostet (pro Bestellung, nicht +pro CD) US-$ 10.00. Visa, Mastercard und American Express werden in +Zahlung genommen. + +Die CD's können bei Nichtgefallen bedingungslos zurückgegeben werden. + + +Berichten von Bugs, Verbesserungsvorschläge, Einreichen von Code +---------------------------------------------------------------- + +Jegliche Fehlerberichte und Beiträge von Code sind herzlich willkommen. +Fehler sollten in jedem Falle gemeldet werden (nach Möglichkeit mit einem +,Fix'). + +Die wünschenswerte Methode zum Einsenden eines Problemberichtes von einer +Maschine mit Internet-Mailzugang ist die Nutzung des Programmes send-pr. +Diese Berichte werden sorgfältig von unserem Bugfile-Programm regi- +striert, und es wird alles getan, so schnell wie möglich darauf zu +antworten. + +Ist es aus irgendeinem Grunde nicht möglich, das Programm ,,send-pr'' +zu nutzen, so können Fehlerberichte auch direkt an + + bugs@FreeBSD.org + +gesandt werden. Außerdem steht die Liste + + questions@FreeBSD.org + +für allgemeine Fragen zur Verfügung. + +(Bitte, wenn möglich, an diese Listen in englischer Sprache schreiben.) + +Selbstverständlich sind wir, da all unsere Arbeit auf der Basis von Frei- +willigkeit geschieht, jederzeit über zusätzliche Helfer erfreut -- es +gibt jetzt schon mehr zu tun, als wir jemals zu tun in der Lage sein +werden! Technische Diskussionsbeiträge oder Hilfsangebote können an + + hackers@FreeBSD.org + +gesandt werden. Diese Listen verursachen in der Regel ein beträcht- +liches Mailaufkommen. Für diejenigen, die einen langsamen oder teuren +Mailanschluß haben und nur an den Ankündigungen wichtiger Ereignisse +interessiert sind, mag daher + + announce@FreeBSD.org + +interessant sein. + + +All diesen Gruppen mit Ausnahme von freebsd-bugs kann jeder Interessierte +jederzeit beitreten. Eine Mail an ,,MajorDomo@FreeBSD.org'' geschickt, +mit lediglich dem Schlüsselwort ,,help'' auf einer eigenen Zeile in der +Nachricht, wird mit der Information über die vorhandenen Listen und +Teilnahmemöglichkeiten beantwortet. Neben den hier genannten Listen +existieren noch weitere, die auf bestimmte Interessengruppen ausgerichtet +sind, so daß die Anfrage durchaus lohnt! + + +6. Würdigungen +-------------- + +FreeBSD verkörpert die Arbeit vieler Dutzender, wenn nicht Hunderte, +Einzelner aus der ganzen Welt, die hart gearbeitet haben, um diese +Version fertigzustellen. Es wäre sehr schwierig oder schier unmöglich, +jeden aufzuzählen, der in irgendeiner Form zu FreeBSD beigetragen hat. +Nichtsdestotrotz soll der Versuch unternommen werden (natürlich in +alphabetischer Reihenfolge). Sollte ein Name fehlen, so ist dieses +ausschließlich ein Versehen. + + +Die Computer Systems Research Group (CSRG), U.C. Berkeley. + +Bill Jolitz, für seine ersten Arbeiten am 386BSD. + +Das FreeBSD-Core-Team +(in alphabetischer Reihenfolge der Vornamen): + + Andreas Schulz <ats@FreeBSD.org> + Andrey A. Chernov <ache@FreeBSD.org> + Bruce Evans <bde@FreeBSD.org> + David Greenman <davidg@FreeBSD.org> + Garrett A. Wollman <wollman@FreeBSD.org> + Gary Palmer <gpalmer@FreeBSD.org> + Geoff Rehmet <csgr@FreeBSD.org> + Jack Vogel <jackv@FreeBSD.org> + John Dyson <dyson@FreeBSD.org> + Jordan K. Hubbard <jkh@FreeBSD.org> + Justin Gibbs <gibbs@FreeBSD.org> + Paul Richards <paul@FreeBSD.org> + Poul-Henning Kamp <phk@FreeBSD.org> + Rich Murphey <rich@FreeBSD.org> + Rodney W. Grimes <rgrimes@FreeBSD.org> + Satoshi Asami <asami@FreeBSD.org> + Søren Schmidt <sos@FreeBSD.org> + +Besondere Erwähnung verdienen: + + Walnut Creek CDROM, ohne deren Hilfe und ständige Unterstützung + diese Ausgabe nie möglich geworden wäre. + + Dermot McDonnell für seine Bereitstellung eines Toshiba XM3401B + CDROM-Laufwerkes. + + Weitere Helfer und Beta-Tester von FreeBSD: + + J.T. Conklin Julian Elischer + Frank Durda IV Peter Dufault + Sean Eric Fagan Jeffrey Hsu + Terry Lambert L Jonas Olsson + Chris Provenzano Dave Rivers + Guido van Rooij Steven Wallace + Atsushi Murai Scott Mace + Nate Williams + + sowie alle an der Montana State University für ihre anfängliche + Unterstützung. + + +Jordan möchte weiterhin besonders Poul-Henning Kamp und Gary Palmer +danken, die ihm beide in vielstündiger Arbeit geholfen haben, das neue +Installationssystem zusammenzustellen. Poul, kürzlich stolzer Vater +geworden, hat es trotz seines enormen Zeitdrucks immer noch geschafft, +eine beträchtliche Menge an Arbeit in das Projekt zu investieren. Diese +Version wäre ohne ihn nicht geworden! Dank Euch Beiden! + +Weiterhing geht Dank an all diejenigen, die mitgeholfen haben, besonders +auch an alle Nichtgenannten. Wir hoffen, daß diese Ausgabe von FreeBSD +allgemeinen Anklang findet! + + Das FreeBSD Core-Team + +$Id: RELNOTES,v 1.2 1995/06/07 05:51:03 jkh Exp $ +======================================================================= diff --git a/release/sysinstall/help/de_DE.ISO_8859-1/configure.hlp b/release/sysinstall/help/de_DE.ISO_8859-1/configure.hlp new file mode 100644 index 0000000..468c1b5 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO_8859-1/configure.hlp @@ -0,0 +1,18 @@ +Mit diesem Menü kann man das System nach der Installation ein wenig +konfigurieren. Es sollten wenigstens das Paßwort für den System- +verwalter gesetzt sowie die Zeitzone eingestellt werden. + +Für zusätzliche ,,Rosinen'' wie bash, emacs, pascal usw. ist es wohl +immer notwendig, einen Blick auf den Menüpunkt ,,Packages'' zu werfen. +Dies ist gegenwärtig nur sinnvoll, wenn man entweder von einer CDROM +installiert oder aber die Package-Sammlung irgendwo in der Datei- +systemhierarchie bereits vorhanden ist, so daß die Package-Verwaltung +darauf zugreifen kann. Eine automatische Übertragung der Packages +mittels FTP ist derzeit noch nicht vorgesehen. + +Soll das Installationsprogramm für die Packages nach Beenden der +Systeminstallation nochmals aufgerufen werden, der Kommandoname +dafür ist ,,pkg_manage''. Das Einstellen der Zeitzone geschieht +mit dem Kommando ,,tzsetup''. Weitere Informationen bezüglich der +allgemeinen Systemkonfiguration befinden sich in der Datei +,,/etc/sysconfig''. diff --git a/release/sysinstall/help/de_DE.ISO_8859-1/drives.hlp b/release/sysinstall/help/de_DE.ISO_8859-1/drives.hlp new file mode 100644 index 0000000..41681f0 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO_8859-1/drives.hlp @@ -0,0 +1,29 @@ +Sowie die ernsthafte Absicht besteht, wirklich irgendetwas von FreeBSD +auf einem Laufwerk zu instellieren, sollte man sich UNBEDINGT VERSICHERN, +daß die vom Partition-Editor berichtete Geometrie (siehe Installations- +Menü) auch die richtige für die Kombination aus Laufwerk und Controller +ist! + +IDE-Laufwerke ,,lernen'' oftmals ihre Geometrie über das Setup des BIOS, +oder (für größere Laufwerke), ihre Geometrie wird entweder vom IDE- +Controller oder aber einem speziellen Werkzeug, das zur Bootzeit geladen +wird, wie dem OnTrack Systems Disk- Manager, uminterpretiert (,,remap- +ped''). In solchen Fällen ist das Erkennen der richtigen Geometrie noch +schwerer, da man nicht einfach auf dem Laufwerk oder im BIOS-Setup +nachsehen kann. Dann ist es das Beste, ein DOS zu booten (von der +Festplatte, nicht von einer Diskette!) und mittels des im tools/-Ver- +zeichnis auf der FreeBSD-CDROM oder auf einem FTP-Server bereitgestellten +Programmes ,,pfdisk'' die Geometrie zu vergleichen. Dieses Programm +berichtet die Geometrie, wie DOS sie sieht, die allgemein als die +richtige angenommen werden kann. + +Falls gar keine DOS-Partition gewünscht wird, kann es sich dennoch als +sinnvoll erweisen, eine solche (sehr kleine) vorerst einzurichten, um +sich über die Laufwerksgeometrie zu informieren. Sie kann dann später +wieder gelöscht werden. + +Es ist aber tatsächlich gar nicht so schlecht (ob man's glaubt oder +nicht), eine bootfähige DOS-Partition auf der Platte zu haben: falls die +Maschine später instabil wird oder einfach ,,spinnt'', so kann man von da +aus bequem eines der kommerziell erhältlichen System-Diagnose-Programme +laufen lassen. diff --git a/release/sysinstall/help/de_DE.ISO_8859-1/install.hlp b/release/sysinstall/help/de_DE.ISO_8859-1/install.hlp new file mode 100644 index 0000000..420eb95 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO_8859-1/install.hlp @@ -0,0 +1,450 @@ + INSTALLATIONSANLEITUNG FÜR FreeBSD 2.0.5 + +Diese Beschreibung dokumentiert die Installation von FreeBSD 2.0.5 auf der +Maschine. Vor dem Beginn ist es ratsam, die Hardware-Anleitung zu studie- +ren, um sich über die hardware-spezifischen Installationshinweise zu in- +formieren (Konfiguration der Hardware, worauf man achten sollte usw.). + + +Inhalt: +======= + +1.0 Fragen und Antworten für DOS-Benutzer + 1.1 Wie schaffe ich Platz für FreeBSD? + 1.2 Kann ich von FreeBSD aus komprimierte DOS-Dateisysteme nutzen? + 1.3 Kann ich erweiterte DOS-Partitions nutzen? + 1.4 Kann ich DOS-Programme unter FreeBSD laufen lassen? + +2.0 Vorbereitung der Installation + 2.1 Vor dem Installieren von CDROM + 2.2 Vor dem Installieren von Diskette + 2.3 Vor dem Installieren von einer DOS-Partition + 2.4 Vor dem Installieren von einem QIC- oder SCSI-Bandlaufwerk + 2.5 Vor dem Installieren über Netz + 2.5.1 Vorbereiten einer NFS-Installation + 2.5.2 Vorbereiten einer FTP-Installation + +3.0 Installieren von FreeBSD + + + +1.0 Fragen und Antworten für DOS-Benutzer +=== ===================================== + +1.1 Hilfe! Kein Platz mehr! Muß ich nun erst alles löschen? + +Wenn auf der Maschine bereits ein DOS installiert ist und nun nur noch +wenig oder gar kein freier Platz mehr für eine FreeBSD-Installation bleibt, +so muß man nicht gleich alle Hoffnung aufgeben! Das Hilfsprogramm FIPS, +das sich im Unterverzeichnis tools/ auf der FreeBSD-CDROM oder auf den +verschiedenen FreeBSD-FTP-Servern befindet, kann sich hier als sehr nütz- +lich erweisen. + +FIPS erlaubt die Aufteilung einer bestehenden DOS-Partition in zwei Teile, +wobei der ursprüngliche Inhalt der Originalpartition erhalten bleibt und +das zweite Stück zum Installieren von FreeBSD verfügbar wird. Man defrag- +mentiert die Partition zuerst mittels des Programmes ,,DEFRAG'' von DOS 6 +oder mittels der Norton Disk Tools und läßt anschließend FIPS laufen. Das +Programm erfragt dann den Rest der benötigten Informationen. Danach kann +man neu booten und FreeBSD in der freigewordenen ,Slice' installieren. Im +Menüpunkt ,,Distributions'' kann man eine Abschätzung vornehmen, wieviel +freien Platz man für die gewünschte Installation etwa benötigt. + + +1.2 Kann ich von FreeBSD aus komprimierte DOS-Dateisysteme nehmen? + +Nein. Wenn man ein Programm wie Stacker (TM) oder DoubleSpace (TM) be- +nutzt, so kann FreeBSD nur den Bereich des (DOS-)Dateisystems nutzen, der +nicht komprimiert worden ist. Der Rest erscheint dann als eine einzige +große Datei (die Stacker- oder DoubleSpace-Datei). DIESE DATEI UNTER +KEINEN UMSTÄNDEN LÖSCHEN! Das würde man nachher bereuen! + + +1.3 Kann ich erweiterte DOS-Partitions nehmen? + +Diese Möglichkeit bietet FreeBSD 2.0.5 noch nicht, aber sie ist für Version +2.1 vorgesehen. Die Grundlagen dafür sind bereits geschaffen, es ist nur +noch 1 % an Restarbeit nötig. + + +1.4 Kann ich DOS-Programme unter FreeBSD laufen lassen? + +Noch nicht. Wir hätten das gern irgendwann, aber bisher hat sich noch +niemand gefunden, der die Arbeit machen würde. Die voranschreitenden +Arbeiten mit dem Linux-DOSEMU-Programm bringen uns aber näher ans Ziel. +Diejenigen, die sich an der Arbeit beteiligen möchten, können sich mittels +einer Mail an hackers@freebsd.org gern melden! + +Es gibt jedoch in der ,,Ports collection'' ein nettes Programm namens +,,pcemu''. Es emuliert einen 8088 sowie ausreichend BIOS-Dienste, um +DOS-Programme im Textmode laufen zu lassen. Es benötigt ein X-Window- +System zum Arbeiten. + + + +2.0 Vorbereitung der Installation +=== ============================= + +2.1 Vor dem Installieren von CDROM: + +Wenn es sich bei dem CDROM-Laufwerk um eins handelt, was nicht unterstützt +wird (z. B. ein IDE-CDROM-Laufwerk), dann bitte bei Punkt 2.3 (,,Vor dem +Installieren von einer DOS-Partition'') weiterlesen. + +Es bedarf keiner großen Vorbereitungen, um von einer der FreeBSD-CDROMs von +Walnut Creek zu installieren. (Andere CDROM-Distributionen können genauso +einfach zu nutzen zu sein, aber da wir keinerlei Einfluß auf deren Gestal- +tung haben, können wir darüber nichts aussagen.) Man kann entweder mittels +des von Walnut Creek gelieferten Scriptes ,,install.bat'' direkt die CDROM +booten, oder aber man fertigt sich mittels ,,makeflp.bat'' eine Boot-Dis- +kette an. + +Der allereinfachste Weg (von DOS aus) ist, einfach ,,go'' einzutippen. Es +erscheint ein kleines DOS-Menü, das einen durch die verfügbaren Möglich- +keiten geleitet. + +Will man die Bootdiskette von einem Unix-System aus erstellen, so führt +vielleicht ein Kommando wie ,,dd if=floppies/boot.flp of=/dev/rfd0'' oder +aber ,,dd if=floppies/boot.flp of=/dev/floppy'' zum Ziel, abhängig von der +verwendeten Hardware und dem Betriebssystem. + +Sowie man von DOS oder einer Diskette aus gebootet hat, kann man sich im +Menüpunkt ,,Media menu'' des Installationsprogrammes die CDROM als Medium +aussuchen und die komplette Distribution davon laden. Es werden keine +weiteren Medien benötigt. + +Nachdem das System installiert ist und man von der Festplatte neu gebootet +hat, müßte die CD im Verzeichnis /cdrom gemountet sein. Das Hilfsprogramm +,lndir', das zusammen mit der XFree86-Distribution kommt, kann hier sehr +nützlich sein: man kann damit einen Baum von symbolischen Links aufbauen, +der das nicht beschreibbare Medium CDROM auf der Festplatte spiegelt. Als +kleines Beispiel: + + mkdir /usr/ports + lndir /cdrom/ports /usr/ports + +Danach kann man dann ,,cd /usr/ports; make'' eintippen, alle Quellen werden +von der CD gelesen, aber alle Zwischendateien werden unterhalb /usr/ports +angelegt, das sich zweckmäßig auf einem besser beschreibbaren Medium befin- +den sollte! :-) + +WICHTIGER HINWEIS: Vor Beginn der Installation unbedingt davon überzeugen, +daß die CDROM im Laufwerk ist, so daß sie beim Test gefunden wird! Dies +ist auch nötig, wenn man gern die CDROM automatisch während der Installa- +tion in die Standard-Konfiguration aufgenommen haben möchte (unabhängig +davon, ob die Installation selbst von CDROM erfolgt). Dies wird sich in +Version 2.1 ändern, aber gegenwärtig ist dies eine einfache Methode um +festzustellen, daß die CDROM tatsächlich zugreifbar ist. + +Schließlich ist es ein Leichtes, wenn man es anderen ermöglichen will, +FreeBSD direkt von der CDROM in der eigenen Maschine mittels FTP installie- +ren zu lassen. Es ist lediglich nach Vollenden der Installation nötig, +folgende Zeile in die Datei /etc/master.passwd aufzunehmen (bitte mit dem +Kommando ,,vipw''): + + ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent + +Mehr ist nicht nötig. Alle anderen können nun in ihrem Installationsmenü +,,FTP'' als Medium auswählen und als Servernamen (über den Menüpunkt +,,Other'') eintragen: ftp://<Adresse dieser Maschine>! + + +2.2 Vor dem Installieren von Diskette + +Wenn man von Disketten installieren will, weil z. B. die Hardware nicht +anders unterstützt wird oder aber für diejenigen, die schwierige Wege +mögen, so muß man zuerst einige Installationsdisketten vorbereiten. + +Die erste Diskette, die man (außer der Bootdiskette) benötigt, ist die +,,floppies/root.flp''. Sie ist insofern etwas Besonderes, daß es sich +nicht um eine Diskette mit DOS-Dateisystem handelt, sondern um ein Abbild +(,image') binärer Daten (genauer gesagt, um ein mit ,gzip' komprimiertes +cpio-Archiv). Man kann dieses Abbild entweder unter DOS mittels des +Programmes ,,rawrite.exe'' auf die Diskette bringen, oder unter Unix mit +dem ,,dd''-Kommando (siehe Bemerkungen in Punkt 2.1 für die Datei +,,floppies/boot.flp''). Nachdem diese Diskette fertig ist, kann es mit den +Distributions-Disketten weitergehen. + +Man benötigt mindestens so viele 1.44-MB- oder 1.2-MB-Disketten, wie nötig +sind, um die Dateien im Verzeichnis ,bin' (Binärdistribution) aufzunehmen. +DIESE Disketten *müssen* DOS-formatiert sein, entweder mit dem Kommando +,,FORMAT'' in DOS oder dem Dateimanager in Microsoft Windows (TM). Man +sollte vorformatierten Disketten nicht trauen und sie sicherheitshalber +nochmals selbst formatieren! + +In der Vergangenheit wurden wiederholt Probleme mit mangelhaft formatier- +ten Datenträgern berichtet, daher hier nochmals obiger Hinweis! + +Nach dem Formatieren der Disketten müssen nun die Dateien darauf über- +tragen werden. Die Distributions-Dateien sind in Stücke zerlegt, von denen +5 auf eine gewöhnliche 1.44-MB-Diskette passen. Man packt einfach alle +vorhandenen Dateien auf die Disketten, so viele, wie auf jede draufpassen, +bis das Ende erreicht ist. Jede Distribution muß dabei in einem eigenen +Untervezeichnis auf den Disketten abgelegt werden, also z. B.: +a:\bin\bin.aa, a:\bin\bin.ab, ... + +Sowie im Installationsprogramm der Menüpunkt zur Medienauswahl erreicht +wird, wählt man ,,Floppy'' aus - der Rest wird dann abgefragt. + + +2.3 Vor dem Installieren von einer DOS-Partition + +In Vorbereitung der Installation von einer DOS-Partition kopiert man +einfach alle Dateien der Distribution(en) in ein Verzeichnis, das +,,FREEBSD'' heißen soll. Um also eine Minimalinstallation von FreeBSD +vorzunehmen, wobei man die Dateien von der CDROM auf die DOS-Partition +kopiert: + + C> MD C:\FREEBSD + C> XCOPY /S E:\DISTS\BIN C:\FREEBSD + C> XCOPY /S E:\FLOPPIES C:\FREEBSD + +...in der Annahme, daß auf ,C:' der nötige freie Platz ist und die CDROM +,E:' genannt wird. Es ist wesentlich, daß auch das Verzeichnis FLOPPIES +mit kopiert wird, da die Datei ,root.flp' daraus während einer Installation +von einer DOS-Partition automatisch entnommen wird. + +Man kann all die gewünschten ,DISTS' unterhalb ,C:\FREEBSD' plazieren - die +,BIN'-Distribution ist lediglich das notwendige Minimum. + + +2.4 Vor dem Installieren von einem QIC- oder SCSI-Bandlaufwerk + +Die Installation von einem Bandlaufwerk ist wohl die einfachste Variante, +wenn man keine Online-FTP-Installation oder Installation von CDROM vorneh- +men kann. Das Installationsprogramm erwartet die Distributions-Dateien +einfach im tar-Format auf dem Band. Nachdem man also alle interessierenden +Dateien geholt hat, kann man das Band einfach mit folgenden Kommandos er- +stellen: + + cd /freebsd/distdir + tar cvf /dev/rwt0 (or /dev/rst0) dist1 .. dist2 + +Das Verzeichnis ,floppies/' muß als eine der ,dist's in obigem Beispiel mit +angegeben worden sein, da das Installationsprogram vom Band die Datei +,floppies/root.flp' lesen muß. + +Während der Installation muß es auch gewährleistet sein, daß man genügend +Platz in einem Zwischenverzeichnis besitzt (der Name dafür wird abgefragt), +um den KOMPLETTEN Inhalt des erzeugten Installationsbandes dort ablegen zu +können. Da sich Bänder nicht wahlfrei zugreifen lassen, benötigt man +vorübergehend die gleiche Menge an Plattenplatz zusätzlich, die auch auf +das Band geschrieben worden ist! + +WICHTIGER HINWEIS: Zu Beginn der Installation muß sich das Band bereits im +Laufwerk befinden, *bevor* man die Bootdiskette startet. Damit wird +sichergestellt, daß der Test während der Installation das Band auch +wirklich erkennt. + + +2.5 Vor dem Installieren über Netz + +Netzwerkinstallationen kann man über drei verschiedene Kommunikations- +medien vornehmen: + + Serieller port: SLIP oder PPP + Parallelport: PLIP (mittels ,Laplink'-Kabel) + Ethernet: mittels Standard-Ethernet-Adapter (einschließlich + einiger PCMCIA-Adapter). + +SLIP-Unterstützung ist eher primitiv und auf festverdrahtete Verbindungen +beschränkt (beispielsweise ein serielles Kabel zwischen einem Laptop und +einem anderen Computer). Die Festverdrahtung ist nötig, da die Installa- +tion über SLIP derzeit keien Möglichkeiten zum Aufbau einer Wählverbindung +anbietet; letzteres kann man aber mittels PPP machen, das man ohnehin +soweit möglich dem SLIP vorziehen sollte. + +Bei Benutzung eines Modems ist PPP sicherlich die einzige Chance. Man +sollte sich rechtzeitig die Informationen des Internet-Dienstanbieters +bereitlegen, da sie früh innerhalb des Installationsprozesses abge- +fragt werden. Minimal wird die IP-Adresse des Dienstanbieters sowie +die eigene benötigt (die aber auch freigelassen werden kann, so daß +PPP sie mit der Gegenseite aushandelt). Auch ist Kenntnis der ver- +schiedenen ,,AT''-Kommandos des benutzten Modems nötig, da das Wähl- +programm für PPP keine Kenntnisse über Modems besitzt. + +Falls eine Festverbindung zu einer anderen FreeBSD-Maschine (mit Ver- +sion 2.0R oder höher) benutzt wird, so kann man auch die Variante mit +einem ,,Laplink''-Kabel über den Parallelport in Betracht ziehen. Die +typische Datenrate über einen Parallelport ist um einiges größer als +das, was sich über serielle Leitungen erzielen läßt; Geschwindigkeiten +um die 50 KB/s sind nicht ungewöhnlich. + +Schließlich ist für eine schnellstmögliche Installation ein Ethernet- +Adapter natürlich eine gute Variante! FreeBSD unterstützt die meisten +gängigen Ethernet-Karten, wobei sich im Hardware-Wegweiser (im Menü- +punkt ,,documentation'' auf der Bootdiskette) eine Tabelle der nötigen +Einstellungen findet. Bei Nutzung eines der unterstützten PCMCIA- +Adapter muß sichergestellt sein, daß sie _vor_ dem Einschalten des +Laptops eingesteckt sind! Leider unterstützt FreeBSD gegenwärtig +keinen Austausch von PCMCIA-Karten im Betrieb. + +Natürlich benötigt man auch noch die IP-Adresse im Netzwerk, die +,,Netzwerkmaske'' für das gewählte Netzwerk, sowie den Maschinennamen. +Der lokale Systemverwalter oder Netzwerkverantwortliche kann über +diese Angaben informieren. Für den Zugriff auf andere Hosts über +Namen anstatt unhandlicher IP-Adressen ist auch noch die Adresse eines +Name-Servers und ggf. eines Gateways vonnöten (bei PPP in der Regel +der Internet-Dienstanbieter). All diese Angaben sollten man _vor_ +Beginn der Installation vom zuständigen System- oder Netzwerkverwalter +einholen. + +Sowie man auf irgendeine Weise eine Netzwerkanbindung aufgebaut hat, kann +man die Installation über NFS oder FTP fortsetzen. + + +2.5.1 Vorbereiten einer NFS-Installation + + Eine Installation über NFS ist recht einfach: man kopiert die + gewünschten FreeBSD-Distributions-Dateien irgendwo auf einen + Server und gibt deren Standort in der NFS-Medienauswahl an. + + Falls dieser Server nur Zugriffe über einen ,,privilegierten'' + Port erlaubt (wie allgemein bein Sun-Workstations üblich), so + muß man die entsprechende Option im ,,Options''-Menü setzen, + bevor man weitermacht. + + Falls man nur eine schlechte Ethernet-Karte besitzt, die sehr + langsam arbeitet, so sollte man ebenfalls die entsprechende + Option einschalten. + + Damit eine NFS-Installation funktioniert, muß der Server das + Mounten von Unterverzeichnissen erlauben; hat man also beispiels- + weise die Distribution von FreeBSD 2.0.5 im Verzeichnis + ziggy:/usr/archive/stuff/FreeBSD untergebracht, so muß der Server + das direkte Mounten von /usr/archive/stuff/FreeBSD erlauben, nicht + nur /usr oder /usr/archive/stuff. + + In FreeBSD's /etc/export-Datei wird dies mittels der Option + ``-alldirs'' gesteuert. Andere NFS-Server haben dafür andere + Konventionen. Wenn man während der Installation Meldungen vom + Server bekommt, die ,,Permission denied'' heißen, so ist dies + wahrscheinlich das Problem! + + +2.5.2 Vorbereiten einer FTP-Installation + + Eine Installation über FTP kann man von jedem Server vornehmen, der + eine einigermaßen aktuelle Kopie der FreeBSD-Version 2.0.5 gespie- + gelt hält. Das Menü ,,FTP sites'' enthält eine gute Auswahl von + FTP-Servern aus der ganzen Welt. + + Wenn man von einem anderen Server installieren will, der nicht + aufgeführt ist, oder Probleme mit der Konfiguration des Name- + Servers hat, so kann man durch Auswahl des Menüpunktes ,,Other'' in + diesem Menü auch seine eigene URL eingeben. Da eine URL auch eine + numerische IP-Adresse enthalten kann, kann man bei Fehlen eines + Name-Servers also auch eingeben: + + ftp://192.216.222.4/pub/FreeBSD/2.0.5-RELEASE + + Wenn man mittels FTP in einer Umgebung installiert, die hinter + einem ,,Firewall'' gelegen ist, so sollte man ,,Passive mode'' FTP + benutzen (was bereits standardmäßig eingestellt ist). Falls man + aus irgendeinem Grunde auf einen Server angewiesen ist, der keinen + Passiv-Modus unterstützt, kann man im ,,Options''-Menü stattdessen + Aktiv-Modus auswählen. + + +3.0 Installieren von FreeBSD +--- ------------------------ + +Nachdem man die entsprechenden Vorbereitungen getroffen hat, sollte die +Installation von FreeBSD ohne Schwierigkeiten vor sich gehen. + +Falls dies doch nicht zutrifft, so hat man vielleicht einen wichtigen +Hinweis bei der Vorbereitung der Installationsmedien verpaßt (siehe +Abschnit 2.X) und sollte nochmals dort nachlesen? Im Falle von Hardware- +problemen (oder wenn FreeBSD gar nicht erst bootet) kann die Hardware- +Anleitung auf der Boot-Diskette Hinweise zur Problembeseitigung geben. + +Die FreeBSD-Bootdiskette enthält alle benötigte Online-Dokumentation, damit +man sich in der Installation zurechtfindet. Falls dies nicht der Fall ist, +so hätten wir gern gewußt, an welcher Stelle die Probleme auftauchen! Es +ist das Ziel von FreeBSD's Installationsprogramm (sysinstall), ausreichend +selbstdokumentierend zu sein, um langwierige ,,Schritt für Schritt''- +Anleitungen hinfällig werden zu lassen. Wir werden sicher noch ein wenig +brauchen, bis dieses Ziel erreicht ist -- aber es ist das Ziel! + +Unterdessen mag die folgende ,,typische Bootreihenfolge'' ganz nützlich +sein: + +o Die Diskette booten. Nach einer Folge von Boot-Schritten, die je nach + der Hardware zwischen 30 Sekunden und 3 Minuten dauern kann, sollte das + Anfangsmenü erscheinen. Wenn die Diskette gar nicht bootet oder das + System während des Bootens hängenbleibt, sollte man den Abschnitt mit + ,,Fragen und Antworten'' in der Hardware-Anleitung hinsichtlich möglicher + Ursachen konsultieren. + +o Taste F1 drücken. Es folgen einige grundlegende Hinweise über die + Nutzung des Menüsystems. Alle diejenigen, die dieses Menüsystem noch + nicht zuvor genutzt haben, sollten sich das BITTE sorgfältig durchlesen! + +o Für diejenigen, die Englisch nicht als Muttersprache sprechen, sei die + Auswahl einer anderen Sprache im Menüpunkt ,,Language'' empfohlen (was ja + ganz offensichtlich geschehen ist :). Ein Teil der Dokumentation wird + dann in der gewählten Sprache anstatt in Englisch angeboten. + +o Auswahl der Sonderwünsche im Menüpunkt ,,Options''. + +o ,,Proceed'' anwählen, um mit dem Istallationsmenü fortzusetzen. + +Das Installationsmenü: + +o Man kann in diesem Menü alles vornehmen, ohne am bestehenden System + irgendetwas zu ändern, solange man nicht ,,Commit'' auswählt; erst damit + werden alle angeforderten Änderungen auch tatsächlich ausgeführt. + + Wenn an irgendeiner Stelle Probleme auftauchen, so bringt die Taste F1 + normalerweise die richtigen Hinweise für das Bild, in dem man sich gerade + befindet. + + o Der erste Schritt ist normalerweise ,Partition', bei dem man + die von FreeBSD zu nutzenden Plattenlaufwerke auswählen kann. + + o Danach kann man mit dem ,Label'-Editor den für FreeBSD vorge- + sehenen Platz aufteilen oder aber eine nicht-FreeBSD-Partition + (z. B. DOS) ins System einbinden. + + o Danach wählt man im ,Media'-Menü das gewünschte Installations- + medium. Sowie alle benötigten Informationen für die Installation + beisammen sind, beendet sich dieses Menü selbst; andernfalls + werden weitere Fragen gestellt (abhängig vom Medium). + + o Schließlich bestätigt man mit dem ,Commit'-Menüpunkt auf einmal + alle ausgewählten Aktionen (ohne diese Bestätigung wurde noch + nichts auf die Festplatte geschrieben). Es werden alle Infor- + mationen über neue oder geänderte Partitions geschrieben, die + Dateisysteme angelegt oder zerstörungsfrei neu markiert (abhängig + von der ,,newfs''-Markierung im Label-Editor) und schließlich + alle gewünschten Distributions ausgepackt. + + o Über das ,Configure'-Menü kann man die FreeBSD-Installation + weiter konfigurieren. Man kann hier menügesteuert die einzelnen + Vorgabewerte für Systemparameter einstellen. Einige Punkte, wie + z. B. die Netzwerkparameter, sind besonders wesentlich, wenn man + von CDROM/Band/Diskette installiert hat und daher den Netzwerk- + zugang noch nicht konfiguriert hat (sofern vorhanden). Wenn man + hier bereits das Netzwerk richtig konfiguriert, so hat man schon + beim ersten Neustart von der Festplatte einen funktionierenden + Zugriff zum Netz. + + o Mittels ,Exit' gelangt man wieder zum Hauptmenü. + + +An dieser Stelle hat man seine Arbeit mit dem sysinstall-Programm beendet. +Man kann schließlich ,Quit' anwählen. Wurde sysinstall als Erstinstalla- +tionsprogramm benutzt (bevor das System also eingerichtet war), so erfolgt +an dieser Stelle ein Neustart. Hatte man einen Boot-Manager ausgewählt, so +erscheint dann ein kleines Boot-Menü mit den Zeichen ,,F?'' als Eingabe- +aufforderung. Nachdem man die entsprechende Funktionstaste für FreeBSD +gedrückt hat (wird angezeigt), sollte FreeBSD von der Festplatte aus ge- +startet werden. + +Falls dies aus irgendeinem Grunde nicht klappt, sei wiederum auf den +Abschnitt ,,Fragen und Antworten'' in der Hardware-Anleitung verwiesen! + + Jordan (für die Anleitung) + Jörg (für die deutsche Übersetzung) + +---- Ende der Installations-Anleitung --- diff --git a/release/sysinstall/help/de_DE.ISO_8859-1/language.hlp b/release/sysinstall/help/de_DE.ISO_8859-1/language.hlp new file mode 100644 index 0000000..cd7a834 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO_8859-1/language.hlp @@ -0,0 +1,17 @@ +In diesem Menü kann man die Vorzugssprache einstellen. Vorerst wird +damit nur die Sprache ausgewählt, in der die diversen Hilfedateien +angezeigt werden. + +In späteren Versionen werden davon auch das Tastaturlayout, der Bild- +schirmzeichensatz und verschiedene NLS-Einstellungen betroffen sein +(sysinstall selbst wird dann auch ,,message catalogs'' benutzen, so +daß alle Menüs automatisch in der richtigen Sprache erscheinen). Auch +sind weitere Internationalisierungsmaßnahmen vorgesehen, so daß die +entsprechenden Standards eingehalten werden. + +Solange diese Verbesserungen noch nicht vorgenommen sind, mag es +einfacher erscheinen, die Datei ,,/etc/sysconfig'' mit der Hand zu +editieren, sobald das System erstmals vollständig installiert ist. +Diese Datei enthält eine Anzahl (allerdings englischer) Kommentare, +die die jeweiligen Änderungen beschreiben, sowie auch einige Beispiele +nicht-englischer Voreinstellungen. diff --git a/release/sysinstall/help/de_DE.ISO_8859-1/media.hlp b/release/sysinstall/help/de_DE.ISO_8859-1/media.hlp new file mode 100644 index 0000000..a591468 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO_8859-1/media.hlp @@ -0,0 +1,30 @@ +Von den folgenden Medien kann man installieren: + + CDROM - eines der folgenden Laufwerke ist nötig: + + Sony CDU 31/33A + Matushita/Panasonic "Sound Blaster" CDROM. + Mitsumi FX-001{A-D} (alte nicht-IDE Laufwerke). + SCSI - Jedes beliebige Standard-SCSI-CDROM-Laufwerk, das + an einen unterstützten Controller angeschlossen ist + (siehe auch Hardware-Wegweiser). + + DOS - eine primäre DOS-Partition, auf die die notwendigen + FreeBSD-Distribution-Dataien kopiert worden sind (also + z. B. (C:\FREEBSD\). + + FS - setzt ein existierendes FreeBSD-System voraus, in dem + die Dateien der neuen Distribution abgelegt worden sind. + + Diskette - Entnahme der Distributions-Dateien von einer oder + mehreren DOS-formatierten Disketten. + + FTP - Entnahme der Distributions-Dateien von einem anonymen + FTP-Server (eine Liste wird angeboten). + + NFS - Einlesen der Distributions-Dateien über einen irgendwo + gelegenen NFS-Server (dessen Zugriffsrechte dies natür- + lich erlauben müssen!) + + Tape - Einlesen der Distributions-Dateien in ein Zwischenver- + zeichnis und Auspacken von dort. diff --git a/release/sysinstall/help/de_DE.ISO_8859-1/network_device.hlp b/release/sysinstall/help/de_DE.ISO_8859-1/network_device.hlp new file mode 100644 index 0000000..1d4e498 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO_8859-1/network_device.hlp @@ -0,0 +1,56 @@ +Eine Netzwerkinstallation kann über eine von drei verschiedenen Arten +von Verbindungen vorgenommen werden: + + Serielle Ports: SLIP / PPP + Parallelport: PLIP (benötigt ein ,,Laplink''-Kabel) + Ethernet: von einem Standard-Ethernet-Controller (ein- + schließlich einiger PCMCIA-Controller) + +Unterstützung für SLIP ist eher primitiv und auf festverdrahtete Ver- +bindungen beschränkt, wie z. B. eine serielle Leitung zwischen einem +Laptop und einem anderen PC. Es existiert gegenwärtig keine Möglich- +keit, eine Wählverbindung über ein Modem herzustellen. Dies kann je- +doch mittels des PPP-Programmes vorgenommen werden, was soweit möglich +stets dem SLIP vorgezogen werden sollte. Bei der Auswahl eines +seriellen Ports wird später die Möglichkeit geboten, die Parameter für +das slattach-Kommando anzugeben. Es wird davon ausgegangen, daß in +diesem Moment entweder slattach oder ein anderes geeignetes Kommando +auf der Gegenseite der Verbindung gestartet worden ist, um die Verbin- +dung aufzubauen. FreeBSD wird dann über diesen Anschluß installiert, +wobei die Geschwindigkeit bis zu 115.2 kBaud betragen kann (was die +empfehlenswerte Geschwindigkeit für eine festverdrahtete Leitung ist). + +Bei Benutzung eines Modems ist PPP sicherlich die einzige Chance. Man +sollte sich rechtzeitig die Informationen des Internet-Dienstanbieters +bereitlegen, da sie früh innerhalb des Installationsprozesses abge- +fragt werden. Minimal wird die IP-Adresse des Dienstanbieters sowie +die eigene benötigt (die aber auch freigelassen werden kann, so daß +PPP sie mit der Gegenseite aushandelt). Auch ist Kenntnis der ver- +schiedenen ,,AT''-Kommandos des benutzten Modems nötig, da das Wähl- +programm für PPP keine Kenntnisse über Modems besitzt. + +Falls eine Festverbindung zu einer anderen FreeBSD-Maschine (mit Ver- +sion 2.0R oder höher) benutzt wird, so kann man auch die Variante mit +einem ,,Laplink''-Kabel über den Parallelport in Betracht ziehen. Die +typische Datenrate über einen Parallelport ist um einiges größer als +das, was sich über serielle Leitungen erzielen läßt; Geschwindigkeiten +um die 50 KB/s sind nicht ungewöhnlich. + +Schließlich ist für eine schnellstmögliche Installation ein Ethernet- +Adapter natürlich eine gute Variante! FreeBSD unterstützt die meisten +gängigen Ethernet-Karten, wobei sich im Hardware-Wegweiser (im Menü- +punkt ,,documentation'' auf der Bootdiskette) eine Tabelle der nötigen +Einstellungen findet. Bei Nutzung eines der unterstützten PCMCIA- +Adapter muß sichergestellt sein, daß sie _vor_ dem Einschalten des +Laptops eingesteckt sind! Leider unterstützt FreeBSD gegenwärtig +keinen Austausch von PCMCIA-Karten im Betrieb. + +Natürlich benötigt man auch noch die IP-Adresse im Netzwerk, die +,,Netzwerkmaske'' für das gewählte Netzwerk, sowie den Maschinennamen. +Der lokale Systemverwalter oder Netzwerkverantwortliche kann über +diese Angaben informieren. Für den Zugriff auf andere Hosts über +Namen anstatt unhandlicher IP-Adressen ist auch noch die Adresse eines +Name-Servers und ggf. eines Gateways vonnöten (bei PPP in der Regel +der Internet-Dienstanbieter). All diese Angaben sollten man _vor_ +Beginn der Installation vom zuständigen System- oder Netzwerkverwalter +einholen. diff --git a/release/sysinstall/help/de_DE.ISO_8859-1/partition.hlp b/release/sysinstall/help/de_DE.ISO_8859-1/partition.hlp new file mode 100644 index 0000000..90041c0 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO_8859-1/partition.hlp @@ -0,0 +1,85 @@ +Dies ist der DiskLabel-Editor von FreeBSD. + +Für Neulinge in dieser Installation ist es zuerst wichtig, FreeBSD's neues +Prinzip der ,,Slices'' zu verstehen, das auf die Plattenspeicher angewandt +wird. Es ist nicht sehr schwer. Ein ,,vollständig angegebener Slice- +Name'', d. h. der Name der Gerätedatei, die unterhalb von /dev angespro- +chen wird, um mit dem Gerät zu kommunizieren, läßt sich wahlweise in +3 Teile zerlegen: + + Das erste ist der Name der Platte. In der Annahme, daß ein + System zwei SCSI-Platten haben möge, wären das ,sd0' und + ,sd1'. + + Das nächste ist die ,,Slice''- (oder ,,primäre Partition''-) + Nummer. Wenn sd0 also z. B. zwei solche Partitions hat, eine + für FreeBSD und eine für DOS, so ergibt das sd0s1 und sd0s2. + Ist dann weiterhin sd1 völlig für FreeBSD reserviert, so hat + sie nur die Slice sd1s1. + + Wenn dann weiterhin eine Slice vom FreeBSD-Typ ist, so besitzt + diese eine Reihe (verwirrenderweise auch so genannter) ,,Par- + titions''. Diese FreeBSD-Partitions bilden die Grundlage für + die verschiedenen Dateisysteme oder den Swap-Bereich. Für die + genannte hypothetische Maschine könnte das Layout für sd0 etwa + so aussehen: + + Name Mountpunkt + ---- ---------- + sd0s1a / + sd0s1b <Swap-Bereich> + sd0s1e /usr + + Aus historischen Gründen existiert auch noch ein Kurzschluß, + eine ,,Kompatibilitäts-Slice'', mit der man einfacher auf die + erste FreeBSD-Slice einer Platte zugreifen kann. Damit + arbeiten auch die Programme, die mit dem Slice-Schema noch + nicht zurechtkommen, wie gehabt. Die Kompatibilitäts-Slice + für genannte Platte würde dann so aussehen: + + Name Mountpoint + ---- ---------- + sd0a / + sd0b <Swap-Bereich> + sd0e /usr + + Die Zuordnung der Kompatibilitäts-Slice zur ersten gefundenen + FreeBSD-Slice (in diesem Falle sd0s1) erfolgt automatisch. Es + kann mehrere FreeBSD-Slices auf einer Platte geben, aber nur + die erste wird als Kompatibilitäts-Slice zugeordnet! + + Möglicherweise wird die Kompatibilitäts-Slice später elimi- + niert, aber gegenwärtig ist sie noch aus folgenden Gründen + nötig: + + 1. Wie bereits erwähnt, kennen einige Programme noch + nicht das Slice-Prinzip und benötigen noch Zeit, + bis sie überarbeitet worden sind. + + 2. Im Moment sind die Bootblöcke von FreeBSD noch + nicht in der Lage, von irgendeinem Root-Dateisystem + außer dem in der Kompatibilitäts-Slice zu booten. + Daher wird die Root also immer auf ,,sd0a'' er- + scheinen (bezogen auf das Beispiel), auch wenn sie + sich eigentlich auf sd0s1a befindet und ansonsten + über den vollen Slice-Namen angesprochen wird. + +Sowie man diese Prinzipien verstanden hat, ist die Benutzung des Disk- +label-Editors eigentlich einfach. Entweder, man teilt die FreeBSD- +Slices, wie sie oben auf dem Bildschirm angezeigt werden, in kleinere +Stücke auf (in der Mitte des Schirmes zu sehen) und plaziert dann +später FreeBSD-Dateisysteme darauf, oder aber man mountet existierende +Slices/Partitions in die Dateisystemhierarchie; dieser Editor erlaubt +beides. Da eine DOS-Partition aus FreeBSD-Sicht auch nur eine weitere +Slice ist, kann man sie mit diesem Editor auch ganz einfach in die +Dateisystemhierarchie eingliedern. Für FreeBSD-Partitions kann man +auch noch den ,,newfs''-Status umschalten, so daß die Partitions ent- +weder von Grund auf neu-/wiedererzeugt werden oder aber einfach nur +überprüft und gemountet (wobei ihr Inhalt erhalten bleibt). + +Wenn man fertig ist, beendet man den Editor mit ,,Q''. + +Es werden keinerlei Änderungen auf die Platte geschrieben, solange man +nicht mittels ,,(C)ommit'' aus dem Installationsmenü alles bestätigt +hat! Der Disklabel-Editor (und der ,,FDISK Partition''-Editor) ar- +beiten mit einer Art Kopie der Disklabels. diff --git a/release/sysinstall/help/de_DE.ISO_8859-1/slice.hlp b/release/sysinstall/help/de_DE.ISO_8859-1/slice.hlp new file mode 100644 index 0000000..c2c92e2 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO_8859-1/slice.hlp @@ -0,0 +1,28 @@ +Dies ist der Editor für die primären Partitions (oder ,,Slices''). + +Unten werden die möglichen Kommandos angezeigt, ober der Inhalt des Master +Boot Records. Man kann mit den Pfeiltasten nach oben und unten fahren und +mittels ,,(C)reate'' eine neue Partition anlegen, wenn sich der ,Balken' +über einer Partition befindet, deren Status als ,,unused'' markiert ist. + +Hier die Zeichenerklärung für das Feld ,,flags'': + + '=' -- Partition ist ordnungsgemäß ausgerichtet. + '>' -- Die Partition endet nicht unterhalb von Zylinder 1024. + 'R' -- Ist markiert, das Root-Dateisystem zu enthalten. + 'B' -- Partition benutzt Fehlersektorenbehandlung nach Bad144. + 'C' -- Dies ist die FreeBSD-2.0-Kompatibilitätspartition. + 'A' -- Die Partition ist als ,aktiv' (bootfähig) markiert. + +Bei der Auswahl einer Partition für Bad144-Behandlung wird diese vor +Erzeugung der Dateisystem auf fehlerhafte Stellen untersucht. + +Wenn keine Partition als ,aktiv' markiert ist, so muß man entweder einen +Boot-Manager installieren (dies wird später im Installationsprozeß ange- +boten) oder aber eine als ,aktiv' markieren, bevor man dieses Menü wieder +verläßt. + +Es werden keinerlei Änderungen auf die Platte geschrieben, solange man +nicht mittels ,,(C)ommit'' aus dem Installationsmenü alles bestätigt hat! +Der ,,FDISK Partition''-Editor (und der Disklabel-Editor) arbeiten mit +einer Art Kopie der Disklabels. diff --git a/release/sysinstall/help/de_DE.ISO_8859-1/tcp.hlp b/release/sysinstall/help/de_DE.ISO_8859-1/tcp.hlp new file mode 100644 index 0000000..d2a3b27 --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO_8859-1/tcp.hlp @@ -0,0 +1,32 @@ +In diesem Menü kann man sowohl die allgemeinen Netzwerkparameter ein- +stellen (Hostname, Domainname, DNS-Server usw.) als auch die Parameter für +ein bestimmtes Interface (das vom zuvor angezeigten Menü ausgewählt worden +ist). + +Man kann zwischen den Feldern mittels der Tasten TAB, Rückwärts-TAB (Shift+ +TAB) und RETURN hin- und herspringen. Mittels DELETE oder BACKSPACE kann +man ein Feld editieren. Mittels ^A (control-A) gelangt man an den Anfang +einer Zeile, mittels ^E (control-E) ans Ende. ^F (control-F) geht ein +Zeichen nach vorn, ^B (control-B) eins nach hinten; ^D (control-D) löscht +das Zeichen unter dem Cursor, und ^K (control-K) löscht alles bis zum Zei- +lenende. Im Prinzip handelt es sich um die wesentlichsten Emacs-Editier- +kommandos. + +Das Feld ,,Extra options to ifconfig'' ist ein wenig besonders (oder auch: +ein Hack :-). + +Damit kann man beispielsweise die Gegenseite einer SLIP- oder PLIP-Ver- +bindung angeben (einfach die numerische IP-Adresse eingeben), oder aber +einen bestimmten Steckverbinder einer Ethernetkarte auswählen, falls +mehrere zur Auswahl sind (z. B. AUI, 10BaseT [twisted pair], 10Base2 [BNC] +usw.). Die folgenden Steckverbinder werden akzeptiert: + + link0 - AUI * höchste Wertigkeit + link1 - BNC + link2 - UTP * niedrigste Wertigkeit + +Man kann also eins der Worte ,,link0'', ,,link1'' oder ,,link2'' in das +,,Extra options''-Feld eintragen. + +Am Ende einfach ,,OK'' anwählen. + diff --git a/release/sysinstall/help/de_DE.ISO_8859-1/usage.hlp b/release/sysinstall/help/de_DE.ISO_8859-1/usage.hlp new file mode 100644 index 0000000..a8beada --- /dev/null +++ b/release/sysinstall/help/de_DE.ISO_8859-1/usage.hlp @@ -0,0 +1,57 @@ +BENUTZUNG DES SYSTEMS +===================== + +TASTE WIRKUNG +----- ------- +PFEIL NACH OBEN Zum vorherigen Feld (oder eine Zeile nach oben im Text). +PFEIL NACH UNTEN Zum nächsten Feld (oder eine Zeile nach unten im Text). +TAB Zum nächsten Feld oder zur nächsten Gruppe. +PFEIL NACH RECHTS Zum nächsten Feld oder zur nächsten Gruppe (wie TAB). +SHIFT-TAB Zum vorherigen Feld oder zur vorherigen Gruppe. +PFEIL NACH LINKS Zum vorherigen Feld oder zur vorherigen Gruppe (wie SH-TAB). +RETURN Menüpunkt auswählen. +BILD NACH OBEN Innerhalb von Textkästen: eine Seite zurück. +BILD NACH UNTEN Innerhalb von Textkästen: eine Seite vor. +LEERTASTE In Menüs mit mehreren Auswahlmöglichkeiten: umschalten. +F1 Hilfe (sofern unterstützt). + +Wenn an den Seiten eines Menüs kleine "^(-)"- oder "v(+)"-Symbole zu +sehen sind, so bedeutet das, daß weitere Menüpunkte ober- oder unter- +halb des aktuellen Punktes existieren, die (infolge fehlenden Platzes +auf dem Bildschirm) gerade nicht dargestellt werden können. Mittels +der Pfeiltasten (nach oben oder unten) kann man das Menü rollen las- +sen. Sowie eins der Symbole verschwindet heißt das, daß man ganz oben +oder unten im Menü ist. + +In Textkästen wird die Stelle, an der man sich befindet, als Prozent- +zahl in der rechten unteren Ecke angezeigt. 100 % bedeuten, daß man +sich am Ende befindet. + +Die Auswahl von ,,OK'' in einem Menü bewirkt die durch dieses Menü +ausgelöste Handlung. Die Auswahl von ,,Cancel'' bewirkt einen Abbruch +und die Rückkehr zum vorherigen Menü. + +BESONDERE EIGENSCHAFTEN +======================= + +Menüpunkte können auch durch Eintippen des ersten Zeichens ihres +Namens ausgewählt werden, sofern dies eindeutig ist. In diesem Falle +werden die entsprechenden Zeichen hervorgehoben. + +Der Bildschirmtreiber enthält auch einen Puffer, mit dem man sich die +Sachen ansehen kann, die bereits herausgerollt worden sind. Um diese +Funktion zu nutzen, muß man die ,,ScrollLock''-Taste (,,Rollen V'') +drücken und danach die Pfeiltasten oder die Bild-auf/ab-Tasten. +Dieser Modus wird durch nochmaliges Drücken der ,,ScrollLock''-Taste +wieder verlassen. Diese Möglichkeit ist vor allem nützlich für +Subshells oder andere ,,Expertenmodi'', die keine Menüs nutzen. + +Sowie das System vollständig installiert ist und im Multi-User-Modus +läuft, werden mehrere ,,virtuelle Terminals'' aktiviert, auf denen man +parallel mehrere aktive Sessions bedienen kann. Mittels ALT-F<n> kann +zwischen diesen umgeschaltet werden, wobei ,,F<n>'' die Funktionstaste +(F-Taste) ist, die der Nummer des gewünschten Bildschirms entspricht. +Das System kommt vorkonfiguriert mit 3 virtuellen Terminals. Wenn +mehr davon gewünscht werden, so kann dies nach dem Hochfahren des +Systems geschehen, indem man sie in der Datei /etc/ttys freischaltet. +Die maximale Anzahl ist 12. diff --git a/release/sysinstall/help/distributions.hlp b/release/sysinstall/help/distributions.hlp new file mode 100644 index 0000000..b81efbf --- /dev/null +++ b/release/sysinstall/help/distributions.hlp @@ -0,0 +1,88 @@ +An ``X-'' prefixed before a distribution set means that the XFree86 +3.1.1u1 base distribution, libraries, manual pages, SVGA server and a +set of default fonts will be selected in addition to the set itself. + +If you select such a set, you will also be presented with a set of +menus for customizing the selections to your desired X Window System +setup. + +N.B. All references in this document to `complete source' mean the +complete source tree minus any legally encumbered cryptography code. + +The current "canned" installations are as follows: + +Developer: Base ("bin") distribution, man pages, dictionary + files, profiling libraries and the complete source tree. + + +Kern-Developer: As above, but with only kernel sources instead of + the complete source tree. + + +User: The base distribution, man pages, dictionary files and + the FreeBSD 1.x and 2.0 compatibility sets. + + +Minimal: Only the base distribution. + + +Everything: The base distribution, man pages, dictionary files, + profiling libraries, the FreeBSD 1.x and the FreeBSD 2.0 + compatibility libraries, the complete source tree, + games and your choice of XFree86 distribution components. + N.B. Still no cryptocraphy source code! + + +Custom: Allows you to modify or create your distribution set on + a piece-by-piece basis. + + +Reset: Clear all currently selected distributions. + + +--- + +When using Custom, most of the sub-distribution choices are fairly +obvious, though two possible exceptions may be the "commerce" and +"xperimnt" distributions: + + * The "commerce" directory, as its name implies, is devoted to + commercial offerings. This includes commercial products released + under special arrangement, limited functionality demos, shareware + products (you like it, you buy it), etc. + + At the time of this writing, there are unfortunately not enough + commercial offerings to justify a fully split distribution set, + so each product is available both as a subdirectory and as part + of one large archive file. If you select "commerce" from the + distributions submenus then you'll get the big file containing + the entire collection copied to your hard disk. Don't do this + unless you've got at least 10MB to devote to it! + + + * The "xperimnt" directory contains, not surprisingly, experimental + offerings. Unfinished (or work-in-progress) features, special + purpose drivers and packages, strange proof-of-concept stuff, + it's a mixed bag! Select this item on a distribution menu and + you'll get the whole collection (between 10 and 30MB). + + + If you're installing from CDROM then all of the commercial and + "experimental" offerings are also easily available in their + individual subdirectories and can be copied to hard disk at + any time. + + +You may also notice that certain distributions, like "des" and "krb", +are marked "NOT FOR EXPORT!" This is because it's illegal to +export them from the United States (or any other country which +considers encryption technology to be on its restricted export +list). Since breaking this law only gets the _originating_ site +(US!) in trouble, please do not load these distributions from U.S. +servers! + +A number of "foreign" servers do exist for the benefit of +non-U.S. sites, one of which is "skeleton.mikom.csir.co.za". + +Please get all such export restricted software from there +if you are outside the U.S., thanks! diff --git a/release/sysinstall/help/drives.hlp b/release/sysinstall/help/drives.hlp new file mode 100644 index 0000000..ef1c4fe --- /dev/null +++ b/release/sysinstall/help/drives.hlp @@ -0,0 +1,29 @@ +If you are going to actually install some portion of FreeBSD on a +drive then PLEASE BE VERY CERTAIN that the Geometry reported in the +Partition Editor (see Installation Menu) is the correct one for your +drive and controller combination! + +IDE drives often have a certain geometry set during the PC BIOS setup, +or (in the case of larger IDE drives) have their geometry "remapped" +by either the IDE controller or a special boot-sector translation +utility such as that by OnTrack Systems. In these cases, knowing the +correct geometry gets even more complicated as it's not something you +can easily tell by looking at the drive or the PC BIOS setup. The +best way of verifying that your geometry is being correctly calculated +in such situations is to boot DOS (from the hard disk, not a floppy!) +and run the ``pfdisk'' utility provided in the tools/ subdirectory of +the FreeBSD CDROM or FTP site. It will report the geometry that DOS +sees, which is generally the correct one. + +If you have no DOS partition sharing the disk at all, then you may +find that you have better luck with Geometry detection if you create a +very small DOS partition first, before installing FreeBSD. Once +FreeBSD is installed you can always delete it again if you need the +space. + +It's actually not a bad idea (believe it or not) to have a small bootable +DOS partition on your FreeBSD machine anyway: Should the machine become +unstable or exhibit strange behavior at some point in the future (which +is not uncommon behavior for PC hardware!) you can then at least use +DOS for installing and running one of the commercially available system +diagnostic utilities. diff --git a/release/sysinstall/help/en_US.ISO8859-1/README b/release/sysinstall/help/en_US.ISO8859-1/README new file mode 100644 index 0000000..c166e26 --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/README @@ -0,0 +1,104 @@ + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Version , , + ----------------------------------------- /( )` + \ \___ / | +Welcome to the 2.0.5 release of FreeBSD! 2.0.5 is /- _ `-/ ' +an interim release of FreeBSD, filling a critical (/\/ \ \ /\ +gap during the period between 2.0R (which was / / | ` \ +released in Nov 94) and 2.1R, which will be O O ) / | +released in late July of '95. FreeBSD 2.0.5 `-^--'`< ' +contains many substantial improvements from 2.0R, (_.) _ ) / +not least of which is greater stability (by `.___/` / +a considerable margin), dozens of new `-----' / +features and a greatly enhanced <----. __ / __ \ +installation program. See the release <----|====O)))==) \) /==== +notes for more details on what's new in <----' `--' `.__,' \ +FreeBSD 2.0.5! | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +What is FreeBSD? FreeBSD is an operating system based on 4.4 BSD Lite +for Intel, AMD, Cyrix or NexGen "x86" based PC hardware. It works +with a very wide variety of PC peripherals and configurations and can +be used for everything from software development to Internet Service +Provision; the busiest site on the Internet, ftp.cdrom.com, is a +FreeBSD machine! + +This release of FreeBSD contains everything you need to run such a +system, plus full source code for everything. With the source +distribution installed you can literally recompile the entire system +from scratch with one command, making it ideal for students, +researchers or folks who simply want to see how it all works. + +A large collection of 3rd party ported software (the "ports +collection") is also provided to make it easier for you to obtain and +install all your favorite traditional UNIX utilities for FreeBSD. +Over 270 ports, from editors to programming languages to graphical +applications, make FreeBSD a powerful and comprehensive operating +environment that rivals that of many large workstations for general utility +and power. + + +For more documentation on this system, it is recommended that you +purchase the 4.4BSD Document Set from O'Reilly Associates and the +USENIX Association, ISBN 1-56592-082-1. We have no connection with +O'Reilly, we're just satisfied customers! + +You may also wish to read the HARDWARE GUIDE *before* proceeding any +further with the installation. Configuring PC hardware for anything +other than DOS/Windows (which don't actually make very significant +demands on the hardware) is actually quite a bit harder than it looks, +and if you think you understand PCs then you clearly haven't been +using them for long enough! :) This guide will give you some tips on +how to configure your hardware and what symptoms to watch for in case +of trouble. This guide is available in the Documentation menu of the +FreeBSD boot floppy. + +DISCLAIMER: While FreeBSD does its best to safeguard against accidental +loss of data, it's still more than possible to WIPE OUT YOUR ENTIRE DISK +with this installation! Please do not proceed to the final FreeBSD +installation menu unless you've adequately backed up any important +data first! We really mean it! + +Technical comments on this release should be sent (in English!) to: + + hackers@FreeBSD.org + + +Bug reports should be sent using the `send-pr' command, if you were +able to get the system installed, otherwise to: + + bugs@FreeBSD.org + +Please be sure to indicate WHICH VERSION of FreeBSD you're running in +any bug reports! + + +General questions should be sent to: + + questions@FreeBSD.org + +Please have patience if your questions are not answered right away - +this is an especially busy time for us, and our volunteer resources +are often strained to the limit! Bug reports submitted with the +send-pr command are logged and tracked in our bugs database, and +you'll be kept informed of any changes in status during the life of +the bug (or feature request). + +Our WEB site, http://www.freebsd.org, is also a very good source for +updated information and provides a number of advanced documentation +facilities. You may use the BSDI version of Netscape for browsing the +World Wide Web directly from FreeBSD. + +You may also wish to look in /usr/share/FAQ and /usr/share/doc for +further information on the system. + + +Thanks for reading all of this, and we sincerely hope you enjoy this +release of FreeBSD! + + Jordan Hubbard, + for The FreeBSD Project diff --git a/release/sysinstall/help/en_US.ISO8859-1/RELNOTES b/release/sysinstall/help/en_US.ISO8859-1/RELNOTES new file mode 100644 index 0000000..9d6284f --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/RELNOTES @@ -0,0 +1,747 @@ + RELEASE NOTES + FreeBSD + Release 2.0.5 + +1. Technical overview +--------------------- + +FreeBSD is a freely available, full source 4.4 BSD Lite based release +for Intel i386/i486/Pentium (or compatible) based PC's. It is based +primarily on software from U.C. Berkeley's CSRG group, with some +enhancements from NetBSD, 386BSD, and the Free Software Foundation. + +Since our release of FreeBSD 2.0 some 8 months ago, the performance, +feature set, and stability of FreeBSD has improved dramatically. The +largest change is a revamped VM system with a merged VM/file buffer +cache that not only increases performance, but reduces FreeBSD's +memory footprint, making a 4MB configuration a more acceptable +minimum. Other enhancements include full NIS client and server +support, transaction TCP support, dial-on-demand PPP, an improved SCSI +subsystem, early ISDN support, support for FDDI and Fast Ethernet +(100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and +narrow) and many hundreds of bug fixes. + +We've also taken the comments and suggestions of many of our users to +heart and have attempted to provide what we hope is a more sane and +easily understood installation process. Your feedback on this +(constantly evolving) process is especially welcome! + +In addition to the base distributions, FreeBSD offers a new ported +software collection with some 270 commonly sought-after programs. The +list of ports ranges from http (WWW) servers, to games, languages, +editors and almost everything in between. The entire ports collection +requires only 10MB of storage, all ports being expressed as "deltas" +to their original sources. This makes it much easier for us to update +ports, and greatly reduces the disk space demands made by the older +1.0 ports collection. To compile a port, you simply change to the +directory of the program you wish to install, type make and let the +system do the rest. The full original distribution for each port you +build is retrieved dynamically off of CDROM or a local ftp site, so +you need only enough disk space to build the ports you want. (Almost) +every port is also provided as a pre-compiled "package" which can be +installed with a simple command (pkg_add) by those who do not wish to +compile their own ports from source. See the file: + /usr/share/FAQ/Text/ports.FAQ +for a more complete description of the ports collection. + + +Since our first release of FreeBSD 1.0 nearly two years ago, FreeBSD +has changed almost entirely. A new port from the Berkeley 4.4 code +base was done, which brought the legal status of the system out of the +shadows with the blessing of Novell (the new owners of USL and UNIX). The +port to 4.4 has also brought in a host of new features, filesystems +and enhanced driver support. With our new unencumbered code base, we +have every reason to hope that we'll be able to release quality +operating systems without further legal encumbrance for some time to +come! + +FreeBSD 2.0.5 represents the culmination of 2 years of work and many +thousands of man hours put in by an international development team. +We hope you enjoy it! + +A number of additional documents which you may find very helpful in +the process of installing and using FreeBSD may also be found in +the "FAQ" directory, either under /usr/share/FAQ on an installed +system or at the top level of the CDROM or FTP distribution from +where you're reading this file. Please consult FAQ/Text/ROADMAP +for a brief description of the resources provided by the FAQ directory. + +For a list of contributors and a general project description, please see +the file "CONTRIB.FreeBSD" which should be bundled with your binary +distribution. + +Also see the "REGISTER.FreeBSD" file for information on registering +with the "Free BSD user counter". This counter is for ALL freely +available variants of BSD, not just FreeBSD, and we urge you to register +yourself with it. + +The core of FreeBSD does not contain DES code which would inhibit its +being exported outside the United States. There is an add-on package +to the core distribution, for use only in the United States, that +contains the programs that normally use DES. The auxiliary packages +provided separately can be used by anyone. A freely (from outside the +U.S.) exportable European distribution of DES for our non-U.S. users also +exists and is described in the FreeBSD FAQ. + +If password security for FreeBSD is all you need, and you have no +requirement for copying encrypted passwords from different hosts +(Suns, DEC machines, etc) into FreeBSD password entries, then +FreeBSD's MD5 based security may be all you require! We feel that our +default security model is more than a match for DES, and without any +messy export issues to deal with. If you're outside (or even inside) +the U.S., give it a try! + + +1.1 What's new in 2.0.5? +------------------------ + +The following features were added or substantially improved between +the release of 2.0 and this 2.0.5 release. In order to facilitate +better communication, the person, or persons, responsible for each +enhancement is noted. Any questions regarding the new functionality +should be directed to them first. + +KERNEL: + +Merged VM-File Buffer Cache +--------------------------- +A merged VM/buffer cache design greatly enhances overall system +performance and makes it possible to do a number of more optimal +memory allocation strategies that were not possible before. + +Owner: David Greenman (davidg@FreeBSD.org) and + John Dyson (dyson@implode.root.com) + + +Network PCB hash optimization +----------------------------- +For systems with a great number of active TCP connections (WEB and ftp +servers, for example), this greatly speeds up the lookup time required +to match an incoming packet up to its associated connection. + +Owner: David Greenman (davidg@FreeBSD.org) + + +Name cache optimization +----------------------- +The name-cache would cache all files of the same name to the same bucket, +which would put for instance all ".." entries in the same bucket. We added +the parent directory version to frustrate the hash, and improved the +management of the cache in various other ways while we were at it. + +Owner: Poul-Henning Kamp (phk@FreeBSD.org) + David Greenman (davidg@FreeBSD.org) + + +Less restrictive swap-spaces +---------------------------- +The need to compile the names of the swap devices into the kernel has been +removed. Now swapon will accept any block devices, up to the maximum +number of swap devices configured in the kernel. + +Owner: Poul-Henning Kamp (phk@FreeBSD.org) + David Greenman (davidg@FreeBSD.org) + + +Hard Wired SCSI Devices +----------------------- +Prior to 2.0.5, FreeBSD performed dynamic assignment of unit numbers +to SCSI devices as they were probed, allowing a SCSI device failure to +possibly change unit number assignment and prevent filesystems on +still functioning disks from mounting. Hard wiring allows static +allocation of unit numbers (and hence device names) to scsi devices +based on SCSI ID and bus. SCSI configuration occurs in the kernel +config file. Samples of the configuration syntax can be found in the +scsi(4) man page or the LINT kernel config file. + +Owner: Peter Dufault (dufault@hda.com) +Sources involved: sys/scsi/* usr.sbin/config/* + + +Slice Support +------------- +FreeBSD now supports a "slice" abstraction which makes it more +completely interoperable with other operating system partitions. This +support will allow FreeBSD to inhabit DOS extended partitions. + +Owner: Bruce Evans (bde@FreeBSD.org) +Sources involved: sys/disklabel.h sys/diskslice.h sys/dkbad.h + kern/subr_diskslice.c kern/subr_dkbad.c + i386/isa/diskslice_machdep.c + i386/isa/wd.c scsi/sd.c dev/vn/vn.c + + +Support for Ontrack Disk Manager Version 6.0 +-------------------------------------------- +Support has been added for disks which use Ontrack Disk Manager. The +fdisk program does NOT know about it however, so make all changes +using the install program on the boot.flp or the Ontrack Disk Manager +tool under DOS. + +Owner: Poul-Henning Kamp (phk@FreeBSD.org) + + +Bad144 is back and working +-------------------------- +Bad144 works again, though the semantics are slightly different than +before in that the bad-spots are kept relative to the slice rather +than absolute on the disk. + +Owner: Bruce Evans (bde@FreeBSD.org) + Poul-Henning Kamp (phk@FreeBSD.org) + + +NEW DEVICE SUPPORT: + + SCSI and CDROM Devices + +Matsushita/Panasonic (Creative) CD-ROM driver +--------------------------------------------- +The Matsushita/Panasonic CR-562 and CR-563 drives are now supported +when connected to a Sound Blaster or 100% compatible host adapter. Up +to four host adapters are supported for a total of 16 CD-ROM drives. +The audio functions are supported, along with access to the raw (2352 byte) +data frames of any compact disc. Audio discs may be played using Karoke +variable speed functions. + +Owner: Frank Durda IV bsdmail@nemesis.lonestar.org +Sources involved: isa/matcd + + +Adaptec 2742/2842/2940 SCSI driver +---------------------------------- +The original 274x/284x driver has evolved considerably since the 2.0 +release. We now offer full support for the 2940 series as well as the +Wide models of these cards. The arbitration bug (as well as many +others) that caused the driver problems with fast devices has been +corrected and there is even experimental tagged queuing support +(kernel option "AHC_TAGENABLE"). John Aycock has also released the +sequencer code under a "Berkeley style" copyright making the driver +entirely clean of the GPL. + +Owner: Justin Gibbs (gibbs@FreeBSD.org) +Sources involved: isa/aic7770.c pci/aic7870.c i386/scsi/* + sys/dev/aic7xxx/* + + +NCR5380/NCR53400 SCSI ("ProAudio Spectrum") driver +-------------------------------------------------- +Owner: core +Submitted by: Serge Vakulenko (vak@cronyx.ru) +Sources involved: isa/ncr5380.c + + +Sony CDROM driver +----------------- +Owner: core +Submitted by: Mikael Hybsch (micke@dynas.se) +Sources involved: isa/scd.c + + + Serial Devices + +SDL Communications Riscom/8 Serial Board Driver +----------------------------------------------- +Owner: Andrey Chernov (ache@FreeBSD.org) +Sources involved: isa/rc.c isa/rcreg.h + + +Cyclades Cyclom-y Serial Board Driver +------------------------------------- +Owner: Bruce Evans (bde@FreeBSD.org) +Submitted by: Andrew Werple (andrew@werple.apana.org.au) and + Heikki Suonsivu (hsu@cs.hut.fi) +Obtained from: NetBSD +Sources involved: isa/cy.c + + +Cronyx/Sigma sync/async serial driver +------------------------------------- +Owner: core +Submitted by: Serge Vakulenko +Sources involved: isa/cronyx.c + + + + Networking + +Diskless booting +---------------- +Diskless booting in 2.0.5 is much improved. The boot-program is in +src/sys/i386/boot/netboot, and can be run from an MSDOS system or +burned into an EPROM. Local swapping is also possible. WD, SMC, 3COM +and Novell ethernet cards are currently supported. + + +DEC DC21140 Fast Ethernet driver +-------------------------------- +This driver supports any of the numerous NICs using the DC21140 chipset +including the 100Mb DEC DE-500-XA and SMC 9332. + +Owner: core +Submitted by: Matt Thomas (thomas@lkg.dec.com) +Sources involved: pci/if_de.c pci/dc21040.h + + +DEC FDDI (DEFPA/DEFEA) driver +----------------------------- +Owner: core +Submitted by: Matt Thomas (thomas@lkg.dec.com) +Sources involved: pci/if_pdq.c pci/pdq.c pci/pdq_os.h pci/pdqreg.h + + +3Com 3c505 (Etherlink/+) NIC driver +----------------------------------- +Owner: core +Submitted by: Dean Huxley (dean@fsa.ca) +Obtained from: NetBSD +Sources involved: isa/if_eg.c + + +Fujitsu MB86960A family of NICs driver +------------------------------------- +Owner: core +Submitted by: M.S. (seki@sysrap.cs.fujitsu.co.jp) +Sources involved: isa/if_fe.c + + +Intel EtherExpress driver +------------------------- +Owner: Rodney W. Grimes (rgrimes@FreeBSD.org) +Sources involved: isa/if_ix.c isa/if_ixreg.h + + +3Com 3c589 driver +----------------- +Owner: core +Submitted by: "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp), + Seiji Murata (seiji@mt.cs.keio.ac.jp) and + Noriyuki Takahashi (hor@aecl.ntt.jp) +Sources involved: isa/if_zp.c + + +IBM Credit Card Adapter driver +------------------------------ +Owner: core +Submitted by: "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp), +Sources involved: isa/pcic.c isa/pcic.h + + +EDSS1 and 1TR6 ISDN interface driver +------------------------------------ +Owner: core +Submitted by: Dietmar Friede (dfriede@drnhh.neuhaus.de) and + Juergen Krause (jkr@saarlink.de) +Sources involved: gnu/isdn/* + + + Miscellaneous Drivers + +Joystick driver +--------------- +Owner: Jean-Marc Zucconi (jmz@FreeBSD.org) +Sources involved: isa/joy.c + + +National Instruments "LabPC" driver +----------------------------------- +Owner: Peter Dufault (dufault@hda.com) +Sources involved: isa/labpc.c + + +WD7000 driver +------------- +Owner: Olof Johansson (offe@ludd.luth.se) + + +Pcvt Console driver +------------------- +Owner: Joerg Wunsch (joerg@FreeBSD.org) +Submitted by: Hellmuth Michaelis (hm@altona.hamburg.com) +Sources involved: isa/pcvt/* usr.sbin/pcvt/* + + +BSD-audio emulator for VAT driver +--------------------------------- +Owner: Amancio Hasty (ahasty@FreeBSD.org) and + Paul Traina (pst@FreeBSD.org) +Sources involved: isa/sound/vat_audio.c isa/sound/vat_audioio.h + + +National Instruments AT-GPIB and AT-GPIB/TNT GPIB driver +-------------------------------------------------------- +Owner: core +Submitted by: Fred Cawthorne (fcawth@delphi.umd.edu) +Sources involved: isa/gpib.c isa/gpib.h isa/gpibreg.h + + +Genius GS-4500 hand scanner driver +---------------------------------- +Owner: core +Submitted by: Gunther Schadow (gusw@fub46.zedat.fu-berlin.de) +Sources involved: isa/gsc.c isa/gscreg.h + + +CORTEX-I Frame Grabber +---------------------- +Owner: core +Submitted by: Paul S. LaFollette, Jr. +Sources involved: isa/ctx.c isa/ctxreg.h + + +Video Spigot video capture card +------------------------------- +Owner: Jim Lowe + + + +1.2 Experimental features +------------------------- + +The unionfs and LFS file systems are known to be severely broken in +2.0.5. This is in part due to old bugs that we haven't had time to +resolve yet and the need to update these file systems to deal with the +new VM system. We hope to address these issues in a later release of +FreeBSD. + +FreeBSD now supports running iBCS2 compatible binaries (currently SCO +UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported). The iBCS2 +emulator is in its early stages, but it is functional, we haven't been +able to do exhaustive testing (lack of commercial apps), but almost +all of SCO's 3.2.2 binaries are working, so is an old INFORMIX-2.10 +for SCO. Further testing is nessesary to complete this project. There +is also work under way for ELF & XOUT loaders, and most of the svr4 +syscall wrappers have been written. + +FreeBSD also implements enough of its Linux compatibility that we +can now run Linux DOOM! See the ``xperimnt'' directory (on your local +FTP server or CDROM) for full docs on how to set this up. + +Owner: Soren Schmidt (sos) & Sean Eric Fagan (sef) +Sources involved: sys/i386/ibcs2/* + misc kernel changes. + + +2. Supported Configurations +--------------------------- + +FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus +based PC's, ranging from 386sx to Pentium class machines (though the +386sx is not recommended). Support for generic IDE or ESDI drive +configurations, various SCSI controller, network and serial cards is +also provided. + +Following is a list of all disk controllers and ethernet cards currently +known to work with FreeBSD. Other configurations may very well work, and +we have simply not received any indication of this. + + +2.1. Disk Controllers +--------------------- + +WD1003 (any generic MFM/RLL) +WD1007 (any generic IDE/ESDI) +IDE +ATA + +Adaptec 152x series ISA SCSI controllers +Adaptec 154x series ISA SCSI controllers +Adaptec 174x series EISA SCSI controller in standard and enhanced mode. +Adaptec 274X/284X/2940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI controllers +Adaptec AIC-6260 and AIC-6360 based boards, which includes +the AHA-152x and SoundBlaster SCSI cards. + +** Note: You cannot boot from the SoundBlaster cards as they have no + on-board BIOS, which is necessary for mapping the boot device into the + system BIOS I/O vectors. They're perfectly usable for external tapes, + CDROMs, etc, however. The same goes for any other AIC-6x60 based card + without a boot ROM. Some systems DO have a boot ROM, which is generally + indicated by some sort of message when the system is first powered up + or reset. Check your system/board documentation for more details. + +[Note that Buslogic was formerly known as "Bustec"] +Buslogic 545S & 545c +Buslogic 445S/445c VLB SCSI controller +Buslogic 742A, 747S, 747c EISA SCSI controller. +Buslogic 946c PCI SCSI controller +Buslogic 956c PCI SCSI controller + +NCR 53C810 and 53C825 PCI SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + +DTC 3290 EISA SCSI controller in 1542 emulation mode. + +UltraStor 14F, 24F and 34F SCSI controllers. + +Seagate ST01/02 SCSI controllers. + +Future Domain 8xx/950 series SCSI controllers. + +WD7000 SCSI controller. + +With all supported SCSI controllers, full support is provided for +SCSI-I & SCSI-II peripherals, including Disks, tape drives (including +DAT) and CD ROM drives. + +The following CD-ROM type systems are supported at this time: +(cd) SCSI (also includes ProAudio Spectrum and SoundBlaster SCSI) +(mcd) Mitsumi proprietary interface +(matcd) Matsushita/Panasonic (Creative) proprietary interface +(scd) Sony proprietary interface + +Note: CD-Drives with IDE interfaces are not supported at this time. + +Some controllers have limitations with the way they deal with >16MB of +memory, due to the fact that the ISA bus only has a DMA address space +of 24 bits. If you do your arithmetic, you'll see that this makes it +impossible to do direct DMA to any address >16MB. This limitation is +even true of some EISA controllers (which are normally 32 bit) when +they're configured to emulate an ISA card, which they then do in *all* +respects. This problem is avoided entirely by IDE controllers (which +do not use DMA), true EISA controllers (like the UltraStor, Adaptec +1742A or Adaptec 2742) and most VLB (local bus) controllers. In the +cases where it's necessary, the system will use "bounce buffers" to +talk to the controller so that you can still use more than 16Mb of +memory without difficulty. + + +2.2. Ethernet cards +------------------- + +Allied-Telesis AT1700 and RE2000 cards +SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, +WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT +based clones. SMC Elite Ultra is also supported. + +DEC EtherWORKS III NICs (DE203, DE204, and DE205) +DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) +DEC DC21140 based NICs (SMC???? DE???) +DEC FDDI (DEFPA/DEFEA) NICs + +Fujitsu FMV-181 and FMV-182 + +Intel EtherExpress + +Isolan AT 4141-0 (16 bit) +Isolink 4110 (8 bit) + +Novell NE1000, NE2000, and NE2100 ethernet interface. + +3Com 3C501 cards + +3Com 3C503 Etherlink II + +3Com 3c505 Etherlink/+ + +3Com 3C507 Etherlink 16/TP + +3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III + +Toshiba ethernet cards + +PCMCIA ethernet cards from IBM and National Semiconductor are also +supported. + + +2.3. Misc +--------- + +AST 4 port serial card using shared IRQ. + +ARNET 8 port serial card using shared IRQ. + +BOCA ATIO66 6 port serial card using shared IRQ. + +Cyclades Cyclom-y Serial Board. + +STB 4 port card using shared IRQ. + +Mitsumi (all models) CDROM interface and drive. + +SDL Communications Riscom/8 Serial Board. + +SoundBlaster SCSI and ProAudio Spectrum SCSI CDROM interface and drive. + +Matsushita/Panasonic (Creative SoundBlaster) CDROM interface and drive. + +Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound +and Roland MPU-401 sound cards. + +FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but +support is apparently close to materializing. Details will be posted +as the situation develops. + + +3. Obtaining FreeBSD +-------------------- + +You may obtain FreeBSD in a variety of ways: + +1. FTP/Mail + +You can ftp FreeBSD and any or all of its optional packages from +`ftp.freebsd.org' - the official FreeBSD release site. + +For other locations that mirror the FreeBSD software see the file +MIRROR.SITES. Please ftp the distribution from the nearest site +to you netwise. + +If you do not have access to the internet and electronic mail is your +only recourse, then you may still fetch the files by sending mail to +`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message +to get more information on how to fetch files from ftp.freebsd.org. +Note: This approach will end up sending many *tens of megabytes* +through the mail, and should only be employed as an absolute LAST +resort! + + +2. CDROM + +FreeBSD 2.0.5 may be ordered on CDROM from: + + Walnut Creek CDROM + 4041 Pike Lane, Suite D + Concord CA 94520 + 1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax) + +Or via the internet from orders@cdrom.com or http://www.cdrom.com. +Their current catalog can be obtained via ftp as: + ftp://ftp.cdrom.com/cdrom/catalog. + +Cost per CD is $39.95, or $24.95 with a FreeBSD subscription. With +a subscription, you will automatically receive updates as they +are released. Your credit card will be billed when each disk is shipped +and you may cancel your subscription at any time without further obligation. + +Walnut Creek CDROM also sells a full line of FreeBSD related merchandise such +as T-shirts ($14.95, available in "child", Large and XL sizes), coffee mugs +($9.95), tattoos ($0.25 each) and posters ($3.00). + +Shipping (per order not per disc) is $5 in the US, Canada or +Mexico and $9.00 overseas. They accept Visa, Mastercard, Discover, +American Express or checks in U.S. Dollars and ship COD within the +United States. California residents please add 8.25% sales tax. + +Should you be dissatisfied for any reason, the CD comes with an +unconditional return policy. + + +Reporting problems, making suggestions, submitting code +------------------------------------------------------- + +Your suggestions, bug reports and contributions of code are always +valued - please do not hesitate to report any problems you may find +(preferably with a fix attached if you can!). + +The preferred method to submit bug reports from a machine with +internet mail connectivity is to use the send-pr command. Bug reports +will be dutifully filed by our faithful bugfiler program and you can +be sure that we'll do our best to respond to all reported bugs as soon +as possible. + +If, for some reason, you are unable to use the send-pr command to +submit a bug report, you can try to send it to: + + bugs@FreeBSD.org + + +Otherwise, for any questions or suggestions, please send mail to: + + questions@FreeBSD.org + +Additionally, being a volunteer effort, we are always happy to have +extra hands willing to help - there are already far more enhancements +to be done than we can ever manage to do by ourselves! To contact us +on technical matters, or with offers of help, you may send mail to: + + hackers@FreeBSD.org + +Since these mailing lists can experience significant amounts of +traffic, if you have slow or expensive mail access and you are +only interested in keeping up with significant FreeBSD events, you may +find it preferable to subscribe to: + + announce@FreeBSD.org + + +All but the freebsd-bugs groups can be freely joined by anyone wishing +to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword +`help' on a line by itself somewhere in the body of the message. This +will give you more information on joining the various lists, accessing +archives, etc. There are a number of mailing lists targeted at +special interest groups not mentioned here, so send mail to majordomo +and ask about them! + + +6. Acknowledgements +------------------- + +FreeBSD represents the cumulative work of many dozens, if not +hundreds, of individuals from around the world who have worked very +hard to bring you this release. It would be very difficult, if not +impossible, to enumerate everyone who's contributed to FreeBSD, but +nonetheless we shall try (in alphabetical order, of course). If your +name is not mentioned, please be assured that its omission is entirely +accidental. + + +The Computer Systems Research Group (CSRG), U.C. Berkeley. + +Bill Jolitz, for his initial work with 386BSD. + +The FreeBSD Core Team +(in alphabetical order by first name): + + Andreas Schulz <ats@FreeBSD.org> + Andrey A. Chernov <ache@FreeBSD.org> + Bruce Evans <bde@FreeBSD.org> + David Greenman <davidg@FreeBSD.org> + Garrett A. Wollman <wollman@FreeBSD.org> + Gary Palmer <gpalmer@FreeBSD.org> + Geoff Rehmet <csgr@FreeBSD.org> + Jack Vogel <jackv@FreeBSD.org> + John Dyson <dyson@FreeBSD.org> + Jordan K. Hubbard <jkh@FreeBSD.org> + Justin Gibbs <gibbs@FreeBSD.org> + Paul Richards <paul@FreeBSD.org> + Poul-Henning Kamp <phk@FreeBSD.org> + Rich Murphey <rich@FreeBSD.org> + Rodney W. Grimes <rgrimes@FreeBSD.org> + Satoshi Asami <asami@FreeBSD.org> + Søren Schmidt <sos@FreeBSD.org> + +Special mention to: + + Walnut Creek CDROM, without whose help (and continuing support) + this release would never have been possible. + + Dermot McDonnell for his donation of a Toshiba XM3401B CDROM + drive. + + Additional FreeBSD helpers and beta testers: + + J.T. Conklin Julian Elischer + Frank Durda IV Peter Dufault + Sean Eric Fagan Jeffrey Hsu + Terry Lambert L Jonas Olsson + Chris Provenzano Dave Rivers + Guido van Rooij Steven Wallace + Atsushi Murai Scott Mace + Nate Williams + + And everyone at Montana State University for their initial support. + + +Jordan would also like to give special thanks to Poul-Henning Kamp and +Gary Palmer, both of whom put in long hours helping him to construct +the new installation utility. Poul, being a proud new father, was +especially pressed for time and yet somehow managed to put in +a significant amount of effort anyway. This release could not have +happened without him! Thank you both! + +Thanks also to everyone else who helped, especially those not +mentioned, and we sincerely hope you enjoy this release of FreeBSD! + + + The FreeBSD Core Team + +$Id: RELNOTES,v 1.9 1995/06/10 02:40:11 jkh Exp $ diff --git a/release/sysinstall/help/en_US.ISO8859-1/XF86.hlp b/release/sysinstall/help/en_US.ISO8859-1/XF86.hlp new file mode 100644 index 0000000..c789eaa --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/XF86.hlp @@ -0,0 +1,500 @@ +README for XFree86 3.1.1u1 on FreeBSD 2.0.5 +Rich Murphey, David Dawes +20 January 1995 + +1. What and Where is XFree86? +------------------------------ + +XFree86 is a port of X11R6 that supports several versions of Intel- +based Unix. It is derived from X386 1.2, which was the X server +distributed with X11R5. This release consists of many new features +and performance improvements as well as many bug fixes. The release +is available as source patches against the X Consortium X11R6 code, as +well as binary distributions for many architectures. + +See the Copyright Notice (COPYRIGHT.html). + +The sources for XFree86 are available as part of the FreeBSD 2.0.5 +distribution, or by anonymous ftp from: + +ftp.XFree86.org:/pub/XFree86/current +(ftp://ftp.XFree86.org/pub/XFree86/current) + + +Binaries for XFree86 on FreeBSD are also available as part of +2.0.5 or from: + +ftp.XFree86.org:/pub/XFree86/current/binaries/FreeBSD-2.0 +(ftp://ftp.XFree86.org/pub/XFree86/current/binaries/FreeBSD-2.0) + +XFree86.cdrom.com:/pub/XFree86/current/binaries/FreeBSD-2.0 +(ftp://XFree86.cdrom.com/pub/XFree86/current/binaries/FreeBSD-2.0) + +Send email to Rich-Murphey@Rice.edu or XFree86@XFree86.org if you have +comments or suggestions about this file and we'll revise it. + + +2. Installing the Binaries +--------------------------- + +In the FreeBSD 2.0.5 distribution, XFree86 comes in 3 major sections: +"basic" distributions, fonts and servers. At the minimum, you will +need the binaries and libraries from the basic distribution, the +"misc" fonts collection and at least one server. The smallest usable +distribution is around 9MB. + +If you can't decide what to pick and you have 52Mb of disk +space, it's safe to unpack everything. + +What follows is a description of the various distribution files +comprising XFree86. If you are installing this as part of FreeBSD +2.0.5 then there's no need to use these files directly: You may +simply check the desired components off the installation menus +provided for that purpose. If you're installing this manually, +then the following information should prove useful: + + Required (6.7Mb): + + X311bin.tgz + all the executable X client applications and shared libs + + X311fnts.tgz + the misc and 75 dpi fonts + + X311lib.tgz + data files needed at runtime + + + Required unless you have already customized your configuration + files: + + X311xicf.tgz + customizable xinit runtime configuration file + + X311xdcf.tgz + customizable xdm runtime configuration file + + Choose at least one server ( 2.3Mb): + + X3118514.tgz + 8-bit color for IBM 8514 and true compatibles. + + X311AGX.tgz + 8-bit color for AGX boards. + + X311Mch3.tgz + 8 and 16-bit color for ATI Mach32 boards. + + X311Mch8.tgz + 8-bit color for ATI Mach8 boards. + + X311Mono.tgz + 1-bit monochrome for VGA, Super-VGA, Hercules, and others. + + X311P9K.tgz + 8, 16, and 24-bit color for Weitek P9000 boards (Diamond + Viper). + + X311S3.tgz + 8, 16 and 24-bit color for S3 boards (#9 GXE, Actix GE32, + SPEA Mercury, STB Pegasus) + + X311SVGA.tgz + 8-bit color for Super-VGA cards. + + X311VG16.tgz + 4-bit color for VGA and Super-VGA cards + + X311W32.tgz + 8-bit Color for ET4000/W32, /W32i and /W32p cards. + + X311nest.tgz + A nested server running as a client window on another + display. + + Optional: + + X311doc.tgz + (.5Mb) READMEs and XFree86 specific man pages + + X311man.tgz + (1.7Mb) man pages except XFree86 specific ones in etc archive + + X311f100.tgz + (1.8Mb) 100dpi fonts + + X311fscl.tgz + (1.6Mb) Speedo and Type1 fonts + + X311fnon.tgz + (3.3Mb) Japanese, Chinese and other non-English fonts + + X311fsrv.tgz + (.3Mb) the font server and it's man page + + X311prog.tgz + (3.9Mb) config, lib*.a and *.h files needed only for + compiling + + X311link.tgz + (7.8Mb) X server reconfiguration kit + + X311pex.tgz + (.5Mb) PEX fonts and shared libs needed by PEX applications. + + X311lbx.tgz + (.2Mb) low bandwidth X proxy server and libraries. + +Note that there is no longer a separate xdm archive. FreeBSD 2.0 +and later handles this in shared libraries now, so that the xdm +binary does not itself contain des and there is no more need for +us to provide separate tar balls. + + +2.1. Full Install: +------------------- + +[ Note: Unless you're installing XFree86 3.1.1u1 manually, that is + to say not as part of the FreeBSD 2.0.5 installation, you may skip + to section 2.3 ] + + 1. You must be logged in as root to unpack the archives because + several executables are set-user-id. Otherwise the server may + abort if you unpack it as an ordinary user. You must also use a + ``umask'' value of 022 because the X server requires special + permissions. + + % su + # umask 022 + + + 2. If you have 52Mb free in the /usr partition ``cd /usr'' and skip + to no. 3. Otherwise, create a directory on another partition + and sym link it into /usr: + + # cd /usr/local + # mkdir X11R6 + # ln -s /usr/local/X11R6 /usr/X11R6 + + + 3. Unpack everything: + + If you are using sh (as root usually does): + + # for i in X311*.tgz; do + # tar -xzf $i + # done + + + Else, if you are using csh: + + % foreach i (X311*.tgz) + % tar -xzf $i + % end + + + 4. Create a symbolic link ``X'' that points to the server that + matches your video card. The XF86_* man pages list which vga + chip sets are supported by each server. For example, if you + have an ET4000 based card you will use the XF86_SVGA server: + + # cd /usr/X11R6/bin; rm X; ln -s XF86_SVGA X + + +2.2. Minimal Install: +---------------------- + +First do numbers 1 and 2 above. Then unpack the required archives: + + # for i in bin fnts lib xicf; do + # tar -xzf X311$i.tgz + # done + + +Then unpack a server archive corresponding to your vga card. The +server man pages, X11R6/man/man1/XF86_*, list the vga chip sets +supported by each server. For example, if you have an ET4000 based +card you will use the XF86_SVGA server: + + # tar -xzf X311SVGA.tgz + # cd /usr/X11R6/bin; rm X; ln -s XF86_SVGA X + + +2.3. After either Full or Minimal Install above: +------------------------------------------------- + +Add /usr/X11R6/bin to the default path for sh in /etc/profile and for +csh in /etc/csh.login if they are not already there: + + # echo 'set path = ($path /usr/X11R6/bin)' >>/etc/csh.login + # echo 'PATH=$PATH:/usr/X11R6/bin' >>/etc/profile + + +Or make sure all who use X put /usr/X11R6/bin in their shell's +``path'' variable. + +Next either reboot or invoke ldconfig as root to put the shared +libraries in ld.so's cache: + + # ldconfig /usr/lib /usr/local/lib /usr/X11R6/lib + + +If you had already configured X11R6/lib/X11/xinit/xinitrc or +X11R6/lib/X11/xdm/* omit the xinit-config or xdm-config archive or +unpack it separately and merge in your customizations. + +The fscl and f100 archives are optional and can be omitted if you are +short on space. The optional link archive allows you to reconfigure +and customize a X server binary. The optional prog archive is needed +only for writing or compiling X applications. The optional pex +archive contains pex clients and libraries for building 3D graphics +applications. + + NOTE: You don't need to uncompress the font files, but if + you uncompress them anyway you must run mkfontdir in the + corresponding font directory; otherwise your server will + abort with the message ``could not open default font + 'fixed'''. + + +3. Installing The Display Manager (xdm) +---------------------------------------- + +The display manager makes your PC look like an X terminal. That is, +it presents you with a login screen that runs under X. + +The easiest way to automatically start the display manager on boot is +to add a line in /etc/ttys to start it on one of the unoccupied +virtual terminals: + + ttyv4 "/usr/X11R6/bin/xdm -nodaemon" xterm on secure + +You should also make sure that /usr/X11R6/bin/X is a symbolic link to +the Xserver that matches your video card or edit the file Xservers in +/usr/X11R6/lib/X11/xdm to specify the pathname of the X server. + +The change to /etc/ttys won't take effect until you either reboot or +``kill -HUP 1'' to force initd to reread /etc/ttys. You can also test +the display manager manually by loging in as root on the console and +typing ``xdm -nodaemon''. + + +4. Configuring X for Your Hardware +----------------------------------- + +The XF86Config file tells the X server what kind of monitor, video +card and mouse you have. You must create it to tell the server what +specific hardware you have. + +XFree86 3.1 uses a new configuration file format. Consult the +XF86Config man page and the general INSTALL (INSTALL.html) file for +instructions. + +If you have a Xconfig file for XFree86 2.x, use reconfig to translate +part of it into the new format: + + # reconfig <Xconfig >XF86Config + +and complete the rest according to the XF86Config man page and the +XF86Config.sample file as a template. + +In order to protect your hardware from damage, the server no longer +will read XF86Config files from a user's home directory, but requires +that it be in /etc/XF86Config, /usr/X11R6/lib/X11/XF86Config.hostname +or /usr/X11R6/lib/X11/XF86Config. + +You'll need info on your hardware: + + o Your mouse type, baud rate and it's /dev entry. + + o The video card's chipset (e.g. ET4000, S3, etc). + + o Your monitor's sync frequencies. + +The easiest way to find which device your mouse is plugged into is to +use ``cat'' or ``kermit'' to look at the output of the mouse. Connect +to it and just make sure that it generates output when the mouse is +moved or clicked: + + % cat < /dev/cuaa0 + +If you can't find the right mouse device then use ``dmesg|grep sio'' +to get a list of devices that were detected upon booting: + + % dmesg|grep sio + sio0 at 0x3f8-0x3ff irq 4 on isa + +Then double check the /dev entries corresponding to these devices. +Use the script /dev/MAKEDEV to create entries if they don't already +exist: + + % cd /dev + % sh MAKEDEV cuaa0 + +If you plan to fine tune the screen size or position on your monitor +you'll need the specs for sync frequencies from your monitor's manual. + + +5. Running X +------------- + +8mb of memory is a recommended minimum for running X. The server, +window manager, display manager and an xterm take about 8Mb of virtual +memory themselves. Even if their resident set size is smaller, on a +8Mb system that leaves very space for other applications such as gcc +that expect a few meg free. The R6 X servers may work with 4Mb of +memory, but in practice compilation while running X can take 5 or 10 +times as long due to constant paging. + +The easiest way for new users to start X windows is to type ``startx +>& startx.log''. Error messages are lost unless you redirect them +because the server takes over the screen. + +To get out of X windows, type: ``exit'' in the console xterm. You can +customize your X by creating .xinitrc, .xserverrc, and .twmrc files in +your home directory as described in the xinit and startx man pages. + + +6. Rebuilding Kernels for X +---------------------------- + +The GENERIC FreeBSD 2.0 kernel supports XFree86 without any +modifications required. You do not need to make any changes to the +GENERIC kernel or any kernel configuration which is a superset. + +For a general description of BSD kernel configuration get +smm.02.config.ps.Z +(ftp://gatekeeper.dec.com/pub/BSD/manuals/smm.02.config.ps.Z). It is +a ready-to-print postscript copy of the kernel configuration chapter +from the system maintainers manual. + +If you do decide to reduce your kernel configuration file, do not +remove the two lines below (in /sys/arch/i386/conf). They are both +required for X support: + + options XSERVER #Xserver + options UCONSOLE #X Console support + +The generic FreeBSD 2.0 kernel is configured by default with the +syscons driver. To configure your kernel similarly it should have a +line like this in /usr/src/sys/i386/conf/GENERIC: + + device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr + +The maximum number of virtual consoles can be set using the MAXCONS +option: + + options "MAXCONS=4" #4 virtual consoles + + +Otherwise, the default without a line like this is 12. You must have +more VTs than gettys as described in the end of section 3, and 4 is a +reasonable minimum. + +The server supports several console drivers: pccons, syscons and pcvt. +The syscons driver is the default in FreeBSD 1.1.5 and higher. They +are detected at runtime and no configuration of the server itself is +required. + +The pcvt console driver is bundled into FreeBSD and may be enabled +by changing the `sc0' line in your kernel configuration file to +`vt0'. See /sys/i386/conf/LINT for more details. + +The XFree86 servers include support for the MIT-SHM extension. The +GENERIC kernel does not support this, so if you want to make use of +this, you will need a kernel configured with SYSV shared memory +support. To do this, add the following line to your kernel config +file: + + options SYSVSHM # System V shared memory + options SYSVSEM # System V semaphores + options SYSVMSG # System V message queues + + +If you are using a SoundBlaster 16 on IRQ 2 (9), then you need a patch +for sb16_dsp.c. Otherwise a kernel configured with the SoundBlaster +driver will claim interrupt 9 doesn't exist and X server will lock up. + +S3 cards and serial port COM 4 cannot be installed together on a +system because the I/O port addresses overlap. + + +7. Rebuilding XFree86 +---------------------- + +The server link kit allows you to build an X server using a minimum +amount of disk space. Just unpack it, make the appropriate changes to +site.def, type ``./mkmf' and ``make'' to link the server. See +README.LinkKit (LinkKit.html) for more info. + +The source tree takes about 114Mb before compiling and an additional +100Mb after ``make World''. You should configure the distribution by +editing xf86site.def and site.def in xc/config/cf before compiling. +By default, the config files are set up to build shared libraries. If +you are running a version of FreeBSD that doesn't include shared +library support, add the following line to site.def: + + #define BuildBsdSharedLibs NO + +If your system doesn't have support or SYSV shared memory (for +example, if you don't have the <sys/shm.h> header), you should disable +the MIT-SHM extension by adding the following line to site.def: + + #define HasShm NO + +To compile the sources on FreeBSD 1.1 and later, type: + + make World + + +8. Building Other X Clients +---------------------------- + +The easiest way to build a new client (X application) is to use xmkmf +if an Imakefile is included with it. Type ``xmkmf -a'' to create the +Makefiles, then type ``make''. Whenever you install additional man +pages you should update whatis.db by running ``makewhatis +/usr/X11R6/man''. + +Note: Starting with XFree86 2.1 and FreeBSD 1.1, the symbol __386BSD__ +no longer gets defined either by the compiler or via the X config +files for FreeBSD systems. When porting clients to BSD systems, make +use of the symbol BSD for code which is truly BSD-specific. The value +of the symbol can be used to distinguish different BSD releases. For +example, code specific to the Net-2 and later releases can use: + + #if (BSD >= 199103) + +To ensure that this symbol is correctly defined, include <sys/param.h> +in the source that requires it. Note that the symbol CSRG_BASED is +defined for *BSD systems in XFree86 3.1.1 and later. This should be +used to protect the inclusion of <sys/param.h>. + +For code that really is specific to a particular i386 BSD port, use +__FreeBSD__ for FreeBSD, __NetBSD__ for NetBSD, __386BSD__ for 386BSD, +and __bsdi__ for BSD/386. + + +9. Thanks +---------- + +Many thanks to: + + o Pace Willison for providing initial *BSD support. + + o Amancio Hasty for 386BSD kernel and S3 chipset support. + + o David Greenman, Nate Williams, Jordan Hubbard for FreeBSD kernel + support. + + o Rod Grimes, Jordan Hubbard and Jack Velte for the use of Walnut + Creek Cdrom's hardware. + + o Orest Zborowski, Simon Cooper and Dirk Hohndel for ideas from + the Linux distribution. + +$XConsortium: FreeBSD.sgml,v 1.3 95/01/23 15:34:41 kaleb Exp $ +Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/FreeBSD.sgml,v 3.10 1995/01/28 16:01:28 dawes Exp $ + + +$XFree86: xc/programs/Xserver/hw/xfree86/doc/READ.FreeBSD,v 3.12 1995/01/28 16:19:37 dawes Exp $ diff --git a/release/sysinstall/help/en_US.ISO8859-1/configure.hlp b/release/sysinstall/help/en_US.ISO8859-1/configure.hlp new file mode 100644 index 0000000..2d14031 --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/configure.hlp @@ -0,0 +1,14 @@ +This menu allows you to configure your system after the installation process +is complete. At the minimum, you should probably set the system manager's +password and the system time zone. + +For extra goodies like bash, emacs, pascal, etc., you should look at the +Packages item in this menu. Currently, the Packages option is only useful +if you have a CDROM or an existing packages collection somewhere in the +file system hierarchy where the package management tool can locate it. +The automatic transfer of packages via FTP is not yet supported! + +If you wish to re-invoke the package installation tool after leaving +the system installation, the command is ``pkg_manage''. For setting +the timezone, type ``tzsetup''. For more information on the general +system configuration, see the ``/etc/sysconfig'' file. diff --git a/release/sysinstall/help/en_US.ISO8859-1/distributions.hlp b/release/sysinstall/help/en_US.ISO8859-1/distributions.hlp new file mode 100644 index 0000000..b81efbf --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/distributions.hlp @@ -0,0 +1,88 @@ +An ``X-'' prefixed before a distribution set means that the XFree86 +3.1.1u1 base distribution, libraries, manual pages, SVGA server and a +set of default fonts will be selected in addition to the set itself. + +If you select such a set, you will also be presented with a set of +menus for customizing the selections to your desired X Window System +setup. + +N.B. All references in this document to `complete source' mean the +complete source tree minus any legally encumbered cryptography code. + +The current "canned" installations are as follows: + +Developer: Base ("bin") distribution, man pages, dictionary + files, profiling libraries and the complete source tree. + + +Kern-Developer: As above, but with only kernel sources instead of + the complete source tree. + + +User: The base distribution, man pages, dictionary files and + the FreeBSD 1.x and 2.0 compatibility sets. + + +Minimal: Only the base distribution. + + +Everything: The base distribution, man pages, dictionary files, + profiling libraries, the FreeBSD 1.x and the FreeBSD 2.0 + compatibility libraries, the complete source tree, + games and your choice of XFree86 distribution components. + N.B. Still no cryptocraphy source code! + + +Custom: Allows you to modify or create your distribution set on + a piece-by-piece basis. + + +Reset: Clear all currently selected distributions. + + +--- + +When using Custom, most of the sub-distribution choices are fairly +obvious, though two possible exceptions may be the "commerce" and +"xperimnt" distributions: + + * The "commerce" directory, as its name implies, is devoted to + commercial offerings. This includes commercial products released + under special arrangement, limited functionality demos, shareware + products (you like it, you buy it), etc. + + At the time of this writing, there are unfortunately not enough + commercial offerings to justify a fully split distribution set, + so each product is available both as a subdirectory and as part + of one large archive file. If you select "commerce" from the + distributions submenus then you'll get the big file containing + the entire collection copied to your hard disk. Don't do this + unless you've got at least 10MB to devote to it! + + + * The "xperimnt" directory contains, not surprisingly, experimental + offerings. Unfinished (or work-in-progress) features, special + purpose drivers and packages, strange proof-of-concept stuff, + it's a mixed bag! Select this item on a distribution menu and + you'll get the whole collection (between 10 and 30MB). + + + If you're installing from CDROM then all of the commercial and + "experimental" offerings are also easily available in their + individual subdirectories and can be copied to hard disk at + any time. + + +You may also notice that certain distributions, like "des" and "krb", +are marked "NOT FOR EXPORT!" This is because it's illegal to +export them from the United States (or any other country which +considers encryption technology to be on its restricted export +list). Since breaking this law only gets the _originating_ site +(US!) in trouble, please do not load these distributions from U.S. +servers! + +A number of "foreign" servers do exist for the benefit of +non-U.S. sites, one of which is "skeleton.mikom.csir.co.za". + +Please get all such export restricted software from there +if you are outside the U.S., thanks! diff --git a/release/sysinstall/help/en_US.ISO8859-1/drives.hlp b/release/sysinstall/help/en_US.ISO8859-1/drives.hlp new file mode 100644 index 0000000..d924f8d --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/drives.hlp @@ -0,0 +1,28 @@ +If you are going to actually install some portion of FreeBSD on a +drive then PLEASE BE VERY CERTAIN that the Geometry reported in the +Partition Editor (see Installation Menu) is the correct one for your +drive and controller combination! + +IDE drives often have a certain geometry set during the PC BIOS setup, +or (in the case of larger IDE drives) have their geometry "remapped" +by either the IDE controller or a special boot-sector translation +utility such as that by OnTrack Systems. In these cases, knowing +the correct geometry gets even more complicated as it's not something +you can easily tell by looking at the drive or the PC BIOS setup. The +best way of verifying that your geometry is being correctly calculated +in such situations is to boot DOS (from the hard disk, not a floppy!) +and run the ``pfdisk'' utility provided in the tools/ subdirectory of the +FreeBSD CDROM or FTP site. It will report the geometry that DOS sees, +which is generally the correct one. + +If you have no DOS partition sharing the disk at all, then you may find that +you have better luck with Geometry detection if you create a very small +DOS partition first, before installing FreeBSD. Once FreeBSD is installed +you can always delete it again if you need the space. + +It's actually not a bad idea (believe it or not) to have a small bootable +DOS partition on your FreeBSD machine anyway: Should the machine become +unstable or exhibit strange behavior at some point in the future (which +is not uncommon behavior for PC hardware!) you can then at least use +DOS for installing and running one of the commercially available system +diagnostic utilities. diff --git a/release/sysinstall/help/en_US.ISO8859-1/hardware.hlp b/release/sysinstall/help/en_US.ISO8859-1/hardware.hlp new file mode 100644 index 0000000..fba5633 --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/hardware.hlp @@ -0,0 +1,384 @@ +Hardware Documentation Guide: $Id: hardware.hlp,v 1.11 1995/06/09 13:29:19 jkh Exp $ + +Table of Contents +----------------- + +0. Document Conventions +1. Using UserConfig to change FreeBSD kernel settings +2. Default Configuration (GENERIC kernel) +3. LINT - other possible configurations. +4. Known Hardware Problems. + +========================================================================= + +0. Document Conventions +-- -------------------- + +We have `underlined' text which represents user input with `-' +symbols throughout this document to differentiate it from +the machine output. + +1. Using UserConfig to change FreeBSD kernel settings +-- -------------------------------------------------- + +The UserConfig utility allows you to override various settings of +the FreeBSD kernel before the system has booted. This allows you to +make minor adjustments to the various drivers in the system without +necessarily having to recompile the kernel. + +UserConfig is activated by specifying the `-c' flag at the initial +boot prompt. For example: + + >> FreeBSD BOOT @ 0x10000: 640/7168 k of memory + Use hd(1,a)/kernel to boot sd0 when wd0 is also installed. + Usage: [[wd(0,a)]/kernel][-abcCdhrsv] + Use ? for file list or press Enter for defaults + + Boot: -c + -- + +This command causes the system to boot the default kernel ("/kernel") and +the UserConfig utility to be started once the kernel is loaded into memory. + +The `-c' flag follows any of the other parameters you may need to provide +for the system to boot properly. For example, to boot off the second of +two SCSI drives installed and run UserConfig, you would type: + + Boot: sd(1,a)/kernel -c + ----------------- + +As always, the kernel will report some information on your processor +and how much memory your system has. Then UserConfig will be invoked +and you will see the prompt: + + config> + +To see the list of commands that UserConfig accepts, you may type '?' and +press [ENTER]. The help message looks something like this: + +Command Description +------- ----------- +attach <devname> Return results of device attach +ls List currently configured devices +port <devname> <addr> Set device port (i/o address) +irq <devname> <number> Set device irq +drq <devname> <number> Set device drq (DMA Request) +iomem <devname> <addr> Set device maddr (memory address) +iosize <devname> <size> Set device memory size +flags <devname> <mask> Set device flags +enable <devname> Enable device +probe <devname> Return results of device probe +disable <devname> Disable device (will not be probed) +quit Exit this configuration utility +help This message + + +You may alter nearly all of the default settings present in the FreeBSD +generic kernel. This includes reassigning IRQs, disabling troublesome +devices (or drivers that conflict with the hardware your system has), +setting special device flags, etc. + +The most common use of UserConfig is to adjust or disable a driver +which is causing trouble. The "ls" command displays the current +settings for all the drivers present in the booted kernel, and +once you have located an entry of interest you may use the displayed +device name to change its settings or even disable the driver completely. + +For example, to change the memory address of network adapter 'ed0' to +the address 0xd4000, you would type + + config> iomem ed0 0xd4000 + ----------------- + +To entirely disable a device driver you are not using, use the +"disable" command. In this example, you would disable device +`ie0' by typing: + + config> disable ie0 + ----------- + +You can use the "ls" command to verify your changes and correct +any other problems before continuing the boot process. + +Once you are happy with a given configuration you may type: "quit" + +This will cause the kernel to boot with the new settings you +have chosen. + +Once you have a fully installed system (e.g. the `bin' distribution +has been successfully extracted), any changes you make in UserConfig +are permanently stored in the `/kernel' file on the root filesystem. +This action is performed by the `dset' utility, which will ensure that +these settings remain in effect until you replace the kernel with +a new one. If you do not want your changes to be permanently +stored like this, remove `dset' from the /etc/rc file before you +make any changes. + +If you accidentally change a setting for a device that you did not mean +to change, the safest thing to do is to reset the computer and start +over. Do not allow the boot to proceed (e.g. do not type "quit") with +bad settings as these may be permanently stored by dset and +leave your system in a state where it will no longer run properly. + +We suggest as a general rule that you disable any drivers that are not +used by your particular hardware configuration. There are known problems +with certain device drivers (see section 4.0) that can cause conflicts +with other devices if they're also not disabled. You should move or +disable any device that resides at the same port or IRQ as a device +you actually have! + +You can also remove drivers that are not needed by building yourself a +custom kernel that contains only the device drivers which your system +really needs (see section 6.0 of the FreeBSD.FAQ). If your system has +sufficient free disk space to store and compile the kernel sources, +this is the option we most highly recommend. + + + +2. Default (GENERIC) Configuration +-- ------------------------------- + +The following table contains a list of all of the devices that are present +in the GENERIC kernel, which is the kernel (the operating system) that was +placed on your computer during the FreeBSD installation process. +(A compressed version of the GENERIC kernel is also used on the +installation floppy diskettes.) + +The table describes the various parameters used by the driver to communicate +with the hardware in your system. There are four parameters in the +table, but not all are used by each device. They are: + + Port the starting I/O port used by the device, shown in hexadecimal. + + IOMem the lowest (or starting) memory address used by the device, + also shown in hexadecimal. + + IRQ the interrupt the device uses to alert the driver to an event, + given in decimal. + + DRQ the DMA (direct memory access) channel the device uses to move + data to and from main memory, also given in decimal. + +If an entry in the table has `n/a' for the value, it means that the +parameter does not apply to that device. A value of `dyn' means that the +correct value should be determined automatically by the kernel when the +system boots. + + +FreeBSD GENERIC kernel: + + Port IRQ DRQ IOMem Description + ---- --- --- ----- --------------------------------- +fdc0 3f0 6 2 n/a Floppy disk controller +wdc0 1f0 14 n/a n/a IDE/MFM/RLL disk controller +wdc1 170 15 n/a n/a IDE/MFM/RLL disk controller + +ncr0 n/a n/a n/a n/a NCR PCI SCSI controller +ahc0 n/a n/a n/a n/a Adaptec 294x PCI SCSI controller +bt0 330 dyn dyn dyn Buslogic SCSI controller +uha0 330 dyn 6 dyn Ultrastore 14f +ahc1 dyn dyn dyn dyn Adaptec 274x/284x SCSI controller +ahb0 dyn dyn dyn dyn Adaptec 174x SCSI controller +aha0 330 dyn 5 dyn Adaptec 154x SCSI controller +aic0 340 11 dyn dyn Adaptec 152x/AIC-6360 SCSI + controller +nca0 1f88 10 dyn dyn ProAudioSpectrum cards +nca1 350 5 dyn dyn ProAudioSpectrum cards +sea0 dyn 5 dyn c8000 Seagate ST01/02 8 bit controller + +wt0 300 5 1 dyn Wangtek and Archive QIC-02/QIC-36 + +mcd0 300 10 n/a n/a Mitsumi CD-ROM +mcd1 340 11 n/a n/a Mitsumi CD-ROM + +matcd0 dyn n/a n/a n/a Matsushita/Panasonic CD-ROM + +scd0 230 n/a n/a n/a Sony CD-ROM + +sio0 3f8 4 n/a n/a Serial Port 0 (COM1) +sio1 2f8 3 n/a n/a Serial Port 1 (COM2) +sio2 3e8 5 n/a n/a Serial Port 2 (COM3) +sio3 2e8 9 n/a n/a Serial Port 3 (COM4) + +lpt0 dyn 7 n/a n/a Printer Port 0 +lpt1 dyn dyn n/a n/a Printer Port 1 +lpt2 dyn dyn n/a n/a Printer Port 2 + +de0 DEC DC21x40 PCI based cards + (including 21140 100bT cards) +ed0 280 5 dyn d8000 WD & SMC 80xx; Novell NE1000 & + NE2000; 3Com 3C503 +ed1 300 5 dyn d8000 Same as ed0 +eg0 310 5 dyn dyn 3Com 3C505 +ep0 300 10 dyn dyn 3Com 3C509 +ie0 360 7 dyn d0000 AT&T StarLAN 10 and EN100; + 3Com 3C507; NI5210 +ix0 300 10 dyn d0000 Intel EtherExpress cards +le0 300 5 dyn d0000 Digital Equipment EtherWorks + 2 and EtherWorks 3 +lnc0 280 10 n/a dyn Lance/PCnet cards + (Isolan, Novell NE2100, NE32-VL) +lnc1 300 10 n/a dyn See lnc0 +ze0 300 5 dyn d8000 IBM/National Semiconductor + PCMCIA Ethernet Controller +zp0 300 10 dyn d8000 3Com PCMCIA Etherlink III + Ethernet Controller +--- End of table --- + + +If the hardware in your computer is not set to the same settings as +those shown in this table and the item is not marked 'dyn', you will +have to either reconfigure your hardware, or use UserConfig ('-c' boot +option) to reconfigure the kernel to match the way your hardware is +currently set (see section 1.0). + +If the settings do not match, the kernel may be unable to locate +or reliably access the devices in your system. + + + +3. LINT - other possible configurations +-- ------------------------------------ + +The following drivers are not in the GENERIC kernel but remain +available to those who do not mind compiling a custom kernel (see +section 6 of FreeBSD.FAQ). The LINT configuration file +(/sys/i386/conf/LINT) also contains prototype entries for just about +every device supported by FreeBSD and is a good general reference. + +The device names and a short description of each are listed below. The port +numbers, etc, are not meaningful here since you will need to compile a +custom kernel to gain access to these devices anyway and can thus +adjust the addresses to match the hardware in your computer in the process. +The LINT file contains prototype entries for all of the below which you +can easily cut-and-paste into your own file (or simply copy LINT and edit +it to taste): + +apm: Laptop Advanced Power Management (experimental) +ctx: Cortex-I frame grabber +cx: Cronyx/Sigma multiport sync/async +cy: Cyclades high-speed serial driver +el: 3Com 3C501 +fe: Fujitsu MB86960A/MB86965A Ethernet cards +fea: DEV DEFEA EISA FDDI adater +fpa: DEC DEFPA PCI FDDI adapter +gp: National Instruments AT-GPIB and AT-GPIB/TNT board +gsc: Genius GS-4500 hand scanner +gus: Gravis Ultrasound - Ultrasound, Ultrasound 16, Ultrasound MAX +gusmax: Gravis Ultrasound MAX (currently broken) +gusxvi: Gravis Ultrasound 16-bit PCM +joy: Joystick +labpc: National Instrument's Lab-PC and Lab-PC+ +mpu: Roland MPU-401 stand-alone card +mse: Logitech & ATI InPort bus mouse ports +mss: Microsoft Sound System +nic: Dr Neuhaus NICCY 3008, 3009 & 5000 ISDN cards +opl: Yamaha OPL-2 and OPL-3 FM - SB, SB Pro, SB 16, ProAudioSpectrum +pas: ProAudioSpectrum PCM and MIDI +pca: PCM audio ("/dev/audio") through your PC speaker +psm: PS/2 mouse port +rc: RISCom/8 multiport card +sb: SoundBlaster PCM - SoundBlaster, SB Pro, SB16, ProAudioSpectrum +sbmidi: SoundBlaster 16 MIDI interface +sbxvi: SoundBlaster 16 +spigot: Create Labs Video Spigot video-acquisition board +uart: Stand-alone 6850 UART for MIDI +wds: Western Digital WD7000 IDE + +--- end of list --- + + +4. Known Hardware Problems, Q & A: +-- ------------------------------- + +Q: mcd0 keeps thinking that it has found a device and this stops my Intel + EtherExpress card from working. + +A: Use the UserConfig utility (see section 1.0) and disable the probing of + the mcd0 and mcd1 devices. Generally speaking, you should only leave + the devices that you will be using enabled in your kernel. + + +Q: The system finds my ed network card, but I keep getting device + timeout errors. + +A: Your card is probably on a different IRQ from what is specified in the + kernel configuration. The ed driver will no longer use the `soft' + configuration by default (values entered using EZSETUP in DOS), but it + will use the software configuration if you specify `?' in the IRQ field + of your kernel config file. The reason for the change is because the + ed driver used to read and try to use the soft configuration information + even when the card was jumpered to use a hard configuration, and this + caused problems. + + Either move the jumper on the card to a hard configuration setting + (altering the kernel settings if necessary), or specify the IRQ as + `-1' in UserConfig or `?' in your kernel config file. This will + tell the kernel to use the soft configuration. + + Another possibility is that your card is at IRQ 9, which is shared + by IRQ 2 and frequently a cause of problems (especially when you + have a VGA card using 2! :). You should not use IRQ 2 or 9 if at + all possible. + + +Q: I go to boot from the hard disk for the first time after installing + FreeBSD, but the Boot Manager prompt just prints `F?' at the boot menu + each time but the boot won't go any further. + +A: The hard disk geometry was set incorrectly in the Partition editor when + you installed FreeBSD. Go back into the partition editor and specify + the actual geometry of your hard disk. You must reinstall FreeBSD + again from the beginning with the correct geometry. + + If you are failing entirely in figuring out the correct geometry for + your machine, here's a tip: Install a small DOS partition at the + beginning of the disk and install FreeBSD after that. The install + program will see the DOS partition and try to infer the correct + geometry from it, which usually works. + + +Q: I have a Matsushita/Panasonic CD-ROM drive but it isn't recognized + by the system, even if I use UserConfig to change the Port address to + 630, which is what my card uses. + +A: Not all of the companies that sell the Matsushita/Panasonic CR-562 + and CR-563 drives use the same I/O ports and interface that the + matcd driver in FreeBSD expects. The only adapters that are supported + at this time are those that are 100% compatible with the Creative + Labs (SoundBlaster) host interface. See matcd.4 documentation for a + list of host adapters that are known to work. + + +Q: I'm trying to install from a tape drive but all I get is something like: + st0(aha0:1:0) NOT READY csi 40,0,0,0 + on the screen. Help! + +A: There's a limitation in the current sysinstall that the tape MUST + be in the drive while sysinstall is started or it won't be detected. + Try again with the tape in the drive the whole time. + + +Q: I've installed FreeBSD onto my system, but it hangs when booting from + the hard drive with the message: ``Changing root to /dev/sd0a''. + +A: This problem may occur in a system with a 3com 3c509 ethernet adaptor. + The ep0 device driver appears to be sensitive to probes for other + devices that also use address 0x300. Boot your FreeBSD system by power + cycling the machine (turn off and on). At the ``Boot:'' prompt specify + the ``-c''. This will invoke UserConfig (see Section 1. above). Use + the ``disable'' command to disable the device probes for all devices + at address 0x300 except the ep0 driver. On exit, your machine should + successfully boot FreeBSD. + + +Q: My system hangs during boot, right after the "fd0: [my floppy drive]" + line. + +A: This is not actually a hang, simply a very LONG "wdc0" probe that + often takes a long time to complete on certain systems (where there + usually _isn't_ a WD controller). Be patient, your system will boot! + To eliminate the problem, boot with the -c flag and eliminate the wdc0 + device, or compile a custom kernel. + +[ Please add more hardware tips to this Q&A section! ] diff --git a/release/sysinstall/help/en_US.ISO8859-1/install.hlp b/release/sysinstall/help/en_US.ISO8859-1/install.hlp new file mode 100644 index 0000000..945c81b --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/install.hlp @@ -0,0 +1,447 @@ + INSTALLATION GUIDE FOR FreeBSD 2.0.5 + +This manual documents the process of installing FreeBSD on your +machine. Please also see the Hardware Guide for hardware-specific +installation instructions (how to configure your hardware, what sorts +of things to watch out for, etc) before starting a new installation. + + +Table of Contents: +================== + +1.0 DOS User's Q&A section. + 1.1 How do I make space for FreeBSD? + 1.2 Can I use compressed DOS filesystems from FreeBSD? + 1.3 Can I use DOS extended partitions? + 1.4 Can I run DOS executables under FreeBSD? + +2.0 Preparing for the installation. + 2.1 Before installing from CDROM + 2.2 Before installing from Floppy + 2.3 Before installing from a DOS partition + 2.4 Before installing from QIC/SCSI tape + 2.5 Before installing over a network + 2.5.1 Preparing for NFS Installation + 2.5.2 Preparing for FTP Installation + +3.0 Installing FreeBSD. + + + +1.0 DOS user's Question and Answer section +=== ====================================== + +1.1 Help! I have no space! Do I need to delete everything first? + +If your machine is already running DOS and has little or no free space +available for FreeBSD's installation, all is not lost! You may find +the "FIPS" utility, provided in the tools/ subdirectory on the FreeBSD +CDROM or on the various FreeBSD ftp sites, to be quite useful. + +FIPS allows you to split an existing DOS partition into two pieces, +preserving the original partition and allowing you to install onto the +second free piece. You first "defrag" your DOS partition, using the +DOS 6.xx "DEFRAG" utility or the Norton Disk tools, then run FIPS. It +will prompt you for the rest of the information it needs. Afterwards, +you can reboot and install FreeBSD on the new free slice. See the +Distributions menu for an estimation of how much free space you'll +need for the kind of installation you want. + + +1.2 Can I use compressed DOS filesystems from FreeBSD? + +No. If you are using a utility such as Stacker(tm) or DoubleSpace(tm), +FreeBSD will only be able to use whatever portion of the filesystem +you leave uncompressed. The rest of the filesystem will show up as +one large file (the stacked/dblspaced file!). DO NOT REMOVE THAT +FILE! You will probably regret it greatly! + +It is probably better to create another uncompressed DOS primary +partition and use this for communications between DOS and FreeBSD. + + +1.3 Can I mount my DOS extended partitions? + +This feature isn't in FreeBSD 2.0.5 but should be in 2.1. We've laid +all the groundwork for making this happen, now we just need to do the +last 1% of the work involved. + + +1.4 Can I run DOS binaries under FreeBSD? + +Not yet! We'd like to add support for this someday, but are still +lacking anyone to actually do the work. Ongoing work with Linux's +DOSEMU utility may bring this much closer to being a reality sometime +soon. Send mail to hackers@freebsd.org if you're interested in +joining this effort! + +However, there is a neat utility called "pcemu" in the ports collection +which emulates an 8088 and enough BIOS services to run DOS text mode +applications. It requires the X Window System (provided as +XFree86 3.1.1u1). + + + +2.0 Preparing for the installation +=== ============================== + +2.1 Before installing from CDROM: + +If your CDROM is of an unsupported type, such as an IDE CDROM, then +please skip to section 2.3: Before installing from a DOS partition. + +There is not a lot of preparatory work that needs to be done to +successfully install from one of Walnut Creek's FreeBSD CDROMs (other +CDROM distributions may work as well, we simply cannot say as we +have no hand or say in their creation). You can either boot into the +CD installation directly from DOS using Walnut Creek's supplied +``install.bat'' batch file or you can make a boot floppy with +the ``makeflp.bat'' command. + +For the easiest interface of all (from DOS), type "go". This +will bring up a DOS menu utility that leads you through all +the available options. + +If you're creating the boot floppy from a UNIX machine, you may find +that ``dd if=floppies/boot.flp of=/dev/rfd0'' or +``dd if=floppies/boot.flp of=/dev/floppy'' works well, depending on +your hardware and operating system environment. + +Once you've booted from DOS or floppy, you should then be able to select +CDROM as the media type in the Media menu and load the entire +distribution from CDROM. No other types of installation media should +be required. + +After your system is fully installed and you have rebooted from the +hard disk, you should find the CD mounted on the directory /cdrom. A +utility called `lndir' comes with the XFree86 distribution which you +may also find useful: It allows you to create "link tree" directories +to things on Read-Only media like CDROM. One example might be +something like this: + + mkdir /usr/ports + lndir /cdrom/ports /usr/ports + +Which would allow you to then "cd /usr/ports; make" and get all the +sources from the CD, but yet create all the intermediate files in +/usr/ports, which is presumably on a more writable media! :-) + +SPECIAL NOTE: Before invoking the installation, be sure that the +CDROM is in the drive so that the "probe" can find it! +This is also true if you wish the CDROM to be added to the default +system configuration automatically during the install (whether or +not you actually use it as the installation media). This will be +fixed for 2.1, but for now this simple work-around will ensure that +your CDROM is detected properly. + +Finally, if you would like people to be able to FTP install +FreeBSD directly from the CDROM in your machine, you'll find +it quite easy. After the machine is fully installed, you simply +need to add the following line to the password file (using +the vipw command): + + ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent + +No further work is necessary. The other installers will now be able +to chose a Media type of FTP and type in: ftp://<your machine> +after picking "Other" in the ftp sites menu! + + +2.2 Before installing from Floppy: + +If you must install from floppy disks, either due to unsupported +hardware or just because you enjoy doing things the hard way, you must +first prepare some floppies for the install. + +The first floppy you'll need is ``floppies/root.flp'', which is +somewhat special in that it's not a DOS filesystem floppy at all, but +rather an "image" floppy (it's actually a gzip'd cpio file). You can +use the rawrite.exe program to do this under DOS, or ``dd'' to do it +on a UNIX Workstation (see notes in section 2.1 concerning the +``floppies/boot.flp'' image). Once this floppy is made, go on +to make the distribution set floppies: + +You will need, at minimum, as many 1.44MB or 1.2MB floppies as it takes +to hold all files in the bin (binary distribution) directory. THESE +floppies *must* be formatted using MS-DOS, using the FORMAT command in +MS-DOS or the File Manager format command in Microsoft Windows(tm). +Don't trust Factory Preformatted floppies! Format them again yourself, +just to make sure! + +Many problems reported by our users in the past have resulted from the +use of improperly formatted media, so we simply take special care to +mention it here! + +After you've DOS formatted the floppies, you'll need to copy the files +onto them. The distribution files are split into chunks conveniently +sized so that 5 of them will fit on a conventional 1.44MB floppy. Go +through all your floppies, packing as many files as will fit on each +one, until you've got all the distributions you want packed up in this +fashion. Each distribution should go into a subdirectory on the +floppy, e.g.: a:\bin\bin.aa, a:\bin\bin.ab, ... + +Once you come to the Media screen of the install, select +"Floppy" and you'll be prompted for the rest. + + +2.3 Before installing from a DOS partition: + +To prepare for installation from an MS-DOS partition you should +simply copy the files from the distribution into a directory called +"FREEBSD". For example, to do a minimal installation of FreeBSD from +DOS using files copied from the CDROM, you might do something like +this: + + C> MD C:\FREEBSD + C> XCOPY /S E:\DISTS\BIN C:\FREEBSD + C> XCOPY /S E:\FLOPPIES C:\FREEBSD + +Asssuming that `C:' was where you had free space and `E:' was where +your CD was mounted. Note that you need the FLOPPIES directory +because the `root.flp' image is automatically looked for there when +you're doing a DOS installation. + +For as many `DISTS' as you wish to install from DOS (and you have free +space for), install each one under `C:\FREEBSD' - the BIN dist is only +the minimal requirement. + + +2.4 Before installing from QIC/SCSI Tape: + +Installing from tape is probably the easiest method, short of an +on-line install using FTP or a CDROM install. The installation program +expects the files to be simply tar'ed onto the tape, so after getting +all of the files for distribution you're interested in, simply tar +them onto the tape with a command like: + + cd /freebsd/distdir + tar cvf /dev/rwt0 (or /dev/rst0) dist1 .. dist2 + +Make sure that the `floppies/' directory is one of the "dists" given +above, since the installation will look for `floppies/root.flp' on +the tape. + +When you go to do the installation, you should also make sure that you +leave enough room in some temporary directory (which you'll be allowed +to choose) to accommodate the FULL contents of the tape you've +created. Due to the non-random access nature of tapes, this method of +installation requires quite a bit of temporary storage! You should +expect to require as much temporary storage as you have stuff written +on tape. + +SPECIAL NOTE: When going to do the installation, the tape must be in +the drive *before* booting from the boot floppy. The installation +"probe" may otherwise fail to find it. + + +2.5 Before installing over a network: + +You can do network installations over 3 types of communications links: + + Serial port: SLIP / PPP + Parallel port: PLIP (laplink cable) + Ethernet: A standard ethernet controller (includes some PCMCIA). + +SLIP support is rather primitive, and limited primarily to hard-wired +links, such as a serial cable running between a laptop computer and +another computer. The link should be hard-wired as the SLIP +installation doesn't currently offer a dialing capability; that +facility is provided with the PPP utility, which should be used in +preference to SLIP whenever possible. + +If you're using a modem, then PPP is almost certainly your only +choice. Make sure that you have your service provider's information +handy as you'll need to know it fairly soon in the installation +process. You will need to know, at the minimum, your service +provider's IP address and possibly your own (though you can also leave +it blank and allow PPP to negotiate it with your ISP). You also need +to know how to use the various "AT commands" to dial the ISP with your +particular modem as the PPP dialer provides only a very simple +terminal emulator. + +If a hard-wired connection to another FreeBSD (2.0R or later) machine +is available, you might also consider installing over a "laplink" +parallel port cable. The data rate over the parallel port is much +higher than what is typically possible over a serial line (up to +50k/sec), thus resulting in a quicker installation. + +Finally, for the fastest possible network installation, an ethernet +adaptor is always a good choice! FreeBSD supports most common PC +ethernet cards, a table of supported cards (and their required +settings) is provided as part of the FreeBSD Hardware Guide - see the +Documentation menu on the boot floppy. If you are using one of the +supported PCMCIA ethernet cards, also be sure that it's plugged in +_before_ the laptop is powered on! FreeBSD does not, unfortunately, +currently support "hot insertion" of PCMCIA cards. + +You will also need to know your IP address on the network, the +"netmask" value for your address class, and the name of your machine. +Your system administrator can tell you which values to use for your +particular network setup. If you will be referring to other hosts by +name rather than IP address, you'll also need a name server and +possibly the address of a gateway (if you're using PPP, it's your +provider's IP address) to use in talking to it. If you do not know +the answers to all or most of these questions, then you should +really probably talk to your system administrator _first_ before +trying this type of installation! + +Once you have a network link of some sort working, the installation +can continue over NFS or FTP. + +2.5.1 Preparing for NFS installation: + + NFS installation is fairly straight-forward: Simply copy the + FreeBSD distribution files you want onto a server somewhere + and then point the NFS media selection at it. + + If this server supports only "privileged port" access (as is + generally the default for Sun workstations), you will need to set + this option in the Options menu before installation can proceed. + + If you have a poor quality ethernet card which suffers from very + slow transfer rates, you may also wish to toggle the appropriate + Options flag. + + In order for NFS installation to work, the server must support + "subdir mounts"; e.g., if your FreeBSD 2.0.5 distribution directory + lives on: ziggy:/usr/archive/stuff/FreeBSD + Then ziggy will have to allow the direct mounting of + /usr/archive/stuff/FreeBSD, not just /usr or /usr/archive/stuff. + + In FreeBSD's /etc/exports file, this is controlled by the + ``-alldirs'' option. Other NFS servers may have different + conventions. If you are getting `Permission Denied' messages + from the server then it's likely that you don't have this + enabled properly! + + +2.5.2 Preparing for FTP Installation + + FTP installation may be done from any mirror site containing a + reasonably up-to-date version of FreeBSD 2.0.5. A full menu of + reasonable choices from almost anywhere in the world is provided + by the FTP site menu. + + If you are installing from some other FTP site not listed in this + menu, or you are having troubles getting your name server configured + properly, you can also specify your own URL by selecting the ``Other'' + choice in that menu. A URL can also be a direct IP address, so + the following would work in the absence of a name server: + + ftp://192.216.222.4/pub/FreeBSD/2.0.5-RELEASE + + [Substitute "ALPHA" for "RELEASE" during the ALPHA test period!] + + If you are installing through a firewall then you should probably + select ``Passive mode'' ftp, which is the default. If you are + talking to a server which does not support passive mode for some + reason, see the Options menu to select Active mode transfers. + + +3. Installing FreeBSD +-- ------------------ + +Once you've taken note of the appropriate preinstallation steps, you +should be able to install FreeBSD without any further trouble. + +Should this not be true, then you may wish to go back and re-read the +relevant preparation section (section 2.x) for the installation media +type you're trying to use - perhaps there's a helpful hint there that +you missed the first time? If you're having hardware trouble, or +FreeBSD refuses to boot at all, read the Hardware Guide provided on +the boot floppy for a list of possible solutions. + +The FreeBSD boot floppy contains all the on-line documentation you +should need to be able to navigate through an installation and if it +doesn't then I'd like to know what you found most confusing! It is +the objective of the FreeBSD installation program (sysinstall) to be +self-documenting enough that painful "step-by-step" guides are no +longer necessary. It may take us a little while to reach that +objective, but that's the objective! + +Meanwhile, you may also find the following "typical installation sequence" +to be helpful: + +o Boot the boot floppy. After a boot sequence which can take + anywhere from from 30 seconds to 3 minutes, depending on your + hardware, you should be presented with a menu of initial + choices. If the floppy doesn't boot at all, or the boot + hangs at some stage, go read the Q&A section of the Hardware + Guide for possible causes. + +o Press F1. You should see some basic usage instructions on + the menu system and general navigation. If you haven't used this + menu system before then PLEASE read this thoroughly! + +o If English is not your native language, you may wish to proceed + directly to the Language option and set your preferred language. + This will bring up some of the documentation in that language + instead of english. + +o Select the Options item and set any special preferences you + may have. + +o Select Proceed, bringing you to the Installation Menu. + +Installation Menu: + +o You can do anything you like in this menu without altering + your system _except_ for "Commit", which will perform any + requests to alter your system you may have made. + + If you're confused at any point, the F1 key usually pulls + up the right information for the screen you're in. + + o The first step is generally `Partition', which allows + you to chose how your drives will be used for FreeBSD. + + o Next, with the `Label' editor, you can specify how the space + in any allocated FreeBSD partitions should be used by FreeBSD, + or where to mount a non-FreeBSD partition (such as DOS). + + o Next, the `Distributions' menu allows you to specify which + parts of FreeBSD you wish to load. A good choice is + "User" for a small system or "Developer" for someone + wanting a bit more out of FreeBSD. If none of the existing + collections sound applicable, select Custom. + + o Next, the `Media' menu allows you to specify what kind of + media you wish to install from. If a desired media choice is + found and configured automatically then this menu will simply + return, otherwise you'll be asked for additional details on + the media device type. + + o Finally, the Commit command will actually perform all the + actions at once (nothing has been written to your disk + so far, nor will it until you give the final confirmation). + All new or changed partition information will be written + out, file systems will be created and/or non-destructively + labelled (depending on how you set their newfs flags in the + Label editor) and all selected distributions will be + extracted. + + o The Configure menu choice allows you to furthur configure your + FreeBSD installation by giving you menu-driven access to + various system defaults. Some items, like networking, may + be especially important if you did a CDROM/Tape/Floppy + installation and have not yet configured your network + interfaces (assuming you have some). Properly configuring + your network here will allow FreeBSD to come up on the network + when you first reboot from the hard disk. + + o Exit returns you to the top menu. + + + At this point, you're generally done with the sysinstall utility and +can select the final `Quit'. If you're running it as an installer +(e.g., before the system is all the way up) then the system will now +reboot. If you selected the boot manager option, you will see a small +boot menu with an `F?' prompt. Press the function key for BSD (it +will be shown) and you should boot up into FreeBSD off the hard disk. + + If this fails to happen for some reason, see the Q & A section +of the Hardware Guide for possible clues! + + Jordan + +---- End of Installation Guide --- diff --git a/release/sysinstall/help/en_US.ISO8859-1/language.hlp b/release/sysinstall/help/en_US.ISO8859-1/language.hlp new file mode 100644 index 0000000..23f176b --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/language.hlp @@ -0,0 +1,14 @@ +Use this menu to select your preferred language. For now, this only +sets the default language in which various help files are displayed. + +In later releases this will also change the keyboard layout, screen +map, NLS settings (sysinstall itself will also use message catalogs so +that all menus are in the appropriate language) and implement other +I18N features to meet various standards. + +Until these improvements are made, you may find it easier to simply +edit the /etc/sysconfig file yourself once the system is fully +installed. There are a number of comments in that file that detail +just what should be changed, as well as a few examples of existing +non-english setups. + diff --git a/release/sysinstall/help/en_US.ISO8859-1/media.hlp b/release/sysinstall/help/en_US.ISO8859-1/media.hlp new file mode 100644 index 0000000..8b081bc --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/media.hlp @@ -0,0 +1,29 @@ +You can install from the following types of media: + + CDROM - requires one of the following supported CDROM drives: + + Sony CDU 31/33A + Matushita/Panasonic "Sound Blaster" CDROM. + Mitsumi FX-001{A-D} (older non-IDE drives). + SCSI - Any standard SCSI CDROM drive hooked to + a supported controller (see Hardware Guide). + + DOS - A DOS primary partition with the required FreeBSD + distribution files copied onto it (e.g. C:\FREEBSD\) + + FS - Assuming a disk or partition with an existing + FreeBSD file system and distribution set on it, + get the distribution files from there. + + Floppy - Get distribution files from one or more DOS formatted + floppies. + + FTP - Get the distribution files from an anonymous ftp server + (you will be presented with a list). + + NFS - Get the distribution files from an NFS server somewhere + (make sure that permissions on the server allow this!) + + Tape - Extract distribution files from tape into a temporary + directory and install from there. + diff --git a/release/sysinstall/help/en_US.ISO8859-1/network_device.hlp b/release/sysinstall/help/en_US.ISO8859-1/network_device.hlp new file mode 100644 index 0000000..95c42ae --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/network_device.hlp @@ -0,0 +1,54 @@ +You can do network installations over 3 types of communications links: + + Serial port: SLIP / PPP + Parallel port: PLIP (laplink cable) + Ethernet: A standard ethernet controller (includes some PCMCIA). + +SLIP support is rather primitive and limited primarily to hard-wired +links, such as a serial cable running between a laptop computer and +another PC. The link must be hard-wired as the SLIP installation +doesn't currently offer a dialing capability; that facility is provided +with the PPP utility, which should be used in preference to SLIP +whenever possible. When you choose a serial port device, you'll +be given the option later to edit the slattach command before it's +run on the serial line. It is expected that you'll run slattach +(or some equivalent) on the other end of the link at this time and +bring up the line. FreeBSD will then install itself over the link +at speeds of up to 115.2K/baud (the recommended speed for a hardwired +cable). + +If you're using a modem then PPP is almost certainly your only +choice. Make sure that you have your service provider's information +handy as you'll need to know it fairly early in the installation +process. You will need to know, at the minimum, your service +provider's IP address and possibly your own (though you can also leave +it blank and allow PPP to negotiate it with your ISP). You will also +need to know how to use the various "AT commands" to dial the ISP with +your particular brand of modem as the PPP dialer provides only a very +simple terminal emulator and has no "modem capabilities database". + +If a hard-wired connection to another FreeBSD (2.0R or later) machine +is available, you might also consider installing over a "laplink" +parallel port cable. The data rate over the parallel port is much +higher than what is typically possible over a serial line with +speeds of up to 50k/sec. + +Finally, for the fastest possible network installation, an ethernet +adaptor is always a good choice! FreeBSD supports most common PC +ethernet cards, a table of which is provided in the FreeBSD +Hardware Guide (see the Documentation menu on the boot floppy). +If you are using one of the supported PCMCIA ethernet cards, also be +sure that it's plugged in _before_ the laptop is powered on! FreeBSD +does not, unfortunately, currently support "hot insertion" of PCMCIA +cards. + +You will also need to know your IP address on the network, the "netmask" +value for your address class, and the name of your machine. +Your system administrator can tell you which values to use for your +particular network setup. If you will be referring to other hosts by +name rather than IP address, you'll also need a name server and +possibly the address of a gateway (if you're using PPP, it's your +provider's IP address) to use in talking to it. If you do not know +the answers to all or most of these questions, then you should +really probably talk to your system administrator _first_ before +trying this type of installation! diff --git a/release/sysinstall/help/en_US.ISO8859-1/options.hlp b/release/sysinstall/help/en_US.ISO8859-1/options.hlp new file mode 100644 index 0000000..c30180c --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/options.hlp @@ -0,0 +1,95 @@ +The following options may be set from this screen: + +NFS Secure: NFS server talks only on a secure port + + This is most commonly used when talking to Sun workstations, which + will not talk NFS over "non priviledged" ports. + + +NFS Slow: User is using a slow PC or ethernet card + + Use this option if you have a slow PC (386) or an ethernet card + with poor performance being "fed" by NFS on a higher-performance + workstation. This will throttle the workstation back to prevent + the PC from becoming swamped with data. + + +FTP Abort: On transfer failure, abort + + This is pretty self-explanatory. If you're transfering from a + host that drops the connection or cannot provide a file, abort + the installation of that piece. + + +FTP Reselect: On transfer failure, ask for another host + + This is more useful to someone doing an interactive installation. + If the current host stops working, ask for a new ftp server to + resume the installation from. The install will attempt to pick + up from where it left off on the other server, if at all possible. + + +FTP Active: Use "active mode" for standard FTP + + For all FTP transfers, use "Active" mode. This will not work + through firewalls, but will often work with older ftp servers + that do not support passive mode. If your connection hangs + with passive mode (the default), try active! + + +FTP Passive: Use "passive mode" for firewalled FTP + + For all FTP transfers, use "Passive" mode. This allows the user + to pass through firewalls that do not allow incoming connections + on random port addresses. + + NOTE: ACTIVE AND PASSIVE MODES ARE NOT THE SAME AS A `PROXY' + CONNECTION, WHERE A PROXY FTP SERVER IS LISTENING ON A DIFFERENT + PORT! + + In such situations, you should specify the URL as something like: + + ftp://foo.bar.com:1234/pub/FreeBSD + + Where "1234" is the port number of the proxy ftp server. + + +Debugging: Turn on the extra debugging flag + + This turns on a lot of extra noise over on the second screen + (ALT-F2 to see it, ALT-F1 to switch back). If your installation + should fail for any reason, PLEASE turn this flag on when + attempting to reproduce the problem. It will provide a lot of + extra debugging at the failure point and may be very helpful to + the developers in tracking such problems down! + + +Yes To All: Assume "Yes" answers to all non-critical dialogs + + This flag should be used with caution. It will essentially + decide NOT to ask the user about any "boundry" conditions that + might not constitute actual errors but may be warnings indicative + of other problems. + + +FTP userpass: Specify username and password instead of anonymous. + + By default, the installation attempts to log in as the + anonymous user. If you wish to log in as someone else, + specify the username and password with this option. + + +Clear: Clear All Option Flags + + Reset all option flags back to their default values. + +---- + +Some of these items, like "FTP Active" or "FTP Passive", are actually +mutually-exclusive even though you can turn all of them on or off at +once. This is a limitation of the menuing system, and is compensated +for by checks that ensure that the various flags are not in conflict. +If you re-enter the Options menu again after leaving it, you'll see +the settings it's actually using after checking for any possible +conflicts. + diff --git a/release/sysinstall/help/en_US.ISO8859-1/partition.hlp b/release/sysinstall/help/en_US.ISO8859-1/partition.hlp new file mode 100644 index 0000000..fd16a45 --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/partition.hlp @@ -0,0 +1,77 @@ +This is the FreeBSD DiskLabel Editor. + +If you're new to this installation, then you should first understand +how FreeBSD 2.0.5's new "slices" paradigm for looking at disk storage +works. It's not very hard to understand. A "fully qualified slice name", +that is the name of the file we open in /dev to talk to the slice, +is optionally broken into 3 parts: + + First you have the disk name. Assume we have two SCSI + drives in our system, which gives us `sd0' and `sd1'. + + Next you have the "Slice" (or "FDISK Partition") number, + as seen in the Partition Editor. Assume that our sd0 contains + two slices, a FreeBSD slice and a DOS slice. This gives us + sd0s1 and sd0s2. Let's also say that sd1 is completely devoted + to FreeBSD, so we have only one slice there: sd1s1. + + Next, if a slice is a FreeBSD slice, you have a number of + (confusingly named) "partitions" you can put inside of it. + These FreeBSD partitions are where various filesystems or swap + areas live, and using our hypothetical two-SCSI-disk machine + again, we might have something like the following layout on sd0: + + Name Mountpoint + ---- ---------- + sd0s1a / + sd0s1b <swap space> + sd0s1e /usr + + Because of historical convention, there is also a short-cut, + or "compatibility slice", that is maintained for easy access + to the first FreeBSD slice on a disk for those programs which + still don't know how to deal with the new slice scheme. + The compatibility slice names for our filesystem above would + look like: + + Name Mountpoint + ---- ---------- + sd0a / + sd0b <swap space> + sd0e /usr + + FreeBSD automatically maps the compatibility slice to the first + FreeBSD slice it finds (in this case, sd0s1). You may have multiple + FreeBSD slices on a drive, but only the first one may be the + compatibility slice! + + The compatibility slice will eventually be phased out, but + it is still important right now for several reasons: + + 1. Some programs, as mentioned before, still don't work + with the slice paradigm and need time to catch up. + + 2. The FreeBSD boot blocks are unable to look for + a root file system in anything but a compatibility + slice right now. This means that our root will always + show up on "sd0a" in the above scenario, even though + it really lives over on sd0s1a and would otherwise be + referred to by its full slice name. + +Once you understand all this, then the label editor becomes fairly +simple. You're either carving up the FreeBSD slices displayed at the +top of the screen into smaller pieces (displayed in the middle of the +screen) and then putting FreeBSD file systems on them, Or you're just +mounting existing partitions/slices into your filesystem hierarchy; +this editor lets you do both. Since a DOS partition is also just +another slice as far as FreeBSD is concerned, you can mount one into +in your filesystem hierarchy just as easily with this editor. For +FreeBSD partitions you can also toggle the "newfs" state so that +the partitions are either (re)created from scratch or simply checked +and mounted (the contents are preserved). + +When you're done, type `Q' to exit. + +No actual changes will be made to the disk until you (C)ommit from the +Install menu! You're working with what is essentially a copy of +the disk label(s), both here and in the FDISK Partition Editor. diff --git a/release/sysinstall/help/en_US.ISO8859-1/slice.hlp b/release/sysinstall/help/en_US.ISO8859-1/slice.hlp new file mode 100644 index 0000000..e055ca4 --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/slice.hlp @@ -0,0 +1,28 @@ +This is the Main Partition (or ``Slice'') Editor. + +Possible commands are printed at the bottom, and the Master Boot Record +contents are at the top. You can move up and down with the arrow keys +and can (C)reate a new partition whenever the "bar" is over a partition +whose type is set to "unused". + +The flags field has the following legend: + + '=' -- Partition is properly aligned. + '>' -- The partition doesn't end before cylinder 1024 + 'R' -- Has been marked as containing the root (/) filesystem + 'B' -- Partition employs BAD144 bad-spot handling + 'C' -- This is the FreeBSD 2.0-compatibility partition (default) + 'A' -- This partition is marked active. + +If you select a partition for Bad144 handling, it will be scanned +for bad blocks before any new filesystems are made on it. + +If no partition is marked Active, you will need to either install +a Boot Manager (the option for which will be presented later in the +installation) or set one Active before leaving this screen. + +To leave this screen, type `Q'. + +No actual changes will be made to the disk until you (C)ommit from the +Install menu! You're working with what is essentially a copy of +the disk label(s), both here and in the Label Editor. diff --git a/release/sysinstall/help/en_US.ISO8859-1/tcp.hlp b/release/sysinstall/help/en_US.ISO8859-1/tcp.hlp new file mode 100644 index 0000000..3ab5d7c --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/tcp.hlp @@ -0,0 +1,27 @@ +This screen allows you to set up your general network parameters +(hostname, domain name, DNS server, etc) as well as the settings for a +given interface (which was selected from the menu before this screen). + +You can move through the fields with the TAB, BACK-TAB and RETURN +keys. To edit a field, use DELETE or BACKSPACE. You may also use ^A +(control-A) to go to the beginning of the line, ^E (control-E) to go +to the end, ^F (control-F) to go forward a character, ^B (control-B) +to go backward one character, ^D (control-D) to delete the character +under the cursor and ^K (control-K) to delete to the end of the line. +Basically, the standard EMACS motion sequences. + +The ``Extra options to ifconfig'' is kind of special (read: a hack :-). + +You can use it for specifying the foreign side of a PLIP or SLIP line +(simply type the foreign address in) as well as selecting a given +"link" on an ethernet card that has more than one (e.g. AUI, 10BT, +10B2, etc). The following links are recognised: + + link0 - AUI * highest precedence + link1 - BNC + link2 - UTP * lowest precedence + +That is to say that you can enter one of "link0", "link1" or "link2" +into the `Extra options' field to select a different link. + +When you're done with this form, select OK. diff --git a/release/sysinstall/help/en_US.ISO8859-1/usage.hlp b/release/sysinstall/help/en_US.ISO8859-1/usage.hlp new file mode 100644 index 0000000..b01a94b --- /dev/null +++ b/release/sysinstall/help/en_US.ISO8859-1/usage.hlp @@ -0,0 +1,54 @@ +HOW TO USE THIS SYSTEM +====================== + +KEY ACTION +--- ------ +UP ARROW Move to previous item (or up, in a text field). +DOWN ARROW Move to next item (or down, in a text field). +TAB Move to next item or group. +RIGHT ARROW Move to next item or group (same as TAB). +SHIFT-TAB Move to previous item or group. +LEFT ARROW Move to previous item or group (same as SHIFT-TAB). +RETURN Select item. +PAGE UP In text boxes, scrolls up one page. +PAGE DOWN In text boxes, scrolls down one page. +SPACE In "radio" or multiple choice menus, toggle the current item. +F1 Help (in screens that provide it). + +If you also see small "^(-)" or "v(+)" symbols at the edges of a menu, +it means that there are more items above or below the current one that +aren't being shown (due to insufficient screen space). Using the +up/down arrow keys will cause the menu to scroll. When a symbol +disappears, it means you are at the top (or bottom) of the menu. + +In text fields, the amount of text above the current point will be +displayed as a percentage in the lower right corner. 100% means +you're at the bottom of the field. + +Selecting OK in a menu will confirm whatever action it's controlling. +Selecting Cancel will cancel the operation and generally return you to +the previous menu. + + +SPECIAL FEATURES: +================= + +It is also possible to select a menu item by typing the first +character of its name, if unique. Such "accelerator" characters will +be specially highlighted in the item name. + +The console driver also contains a scroll-back buffer for reviewing +things that may have scrolled off the screen. To use scroll-back, +press the "Scroll Lock" key on your keyboard and use the arrow or +Page Up/Page Down keys to move through the saved text. To leave +scroll-back mode, press the Scroll Lock key again. This feature +is most useful for dealing with sub-shells or other "wizard modes" +that don't use menus. + +Once the system is fully installed and running "multi-user", you will +also find that you have multiple "virtual consoles" and can use them to +have several active sessions at once. Use ALT-F<n> to switch between +them, where `F<n>' is the function key corresponding to the screen you +wish to see. By default, the system comes with 3 virtual consoles enabled. +You can create more by editing the /etc/ttys file, once the system is up, +for a maximum of 12. diff --git a/release/sysinstall/help/en_US.ISO_8859-1/README b/release/sysinstall/help/en_US.ISO_8859-1/README new file mode 100644 index 0000000..c166e26 --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/README @@ -0,0 +1,104 @@ + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Version , , + ----------------------------------------- /( )` + \ \___ / | +Welcome to the 2.0.5 release of FreeBSD! 2.0.5 is /- _ `-/ ' +an interim release of FreeBSD, filling a critical (/\/ \ \ /\ +gap during the period between 2.0R (which was / / | ` \ +released in Nov 94) and 2.1R, which will be O O ) / | +released in late July of '95. FreeBSD 2.0.5 `-^--'`< ' +contains many substantial improvements from 2.0R, (_.) _ ) / +not least of which is greater stability (by `.___/` / +a considerable margin), dozens of new `-----' / +features and a greatly enhanced <----. __ / __ \ +installation program. See the release <----|====O)))==) \) /==== +notes for more details on what's new in <----' `--' `.__,' \ +FreeBSD 2.0.5! | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +What is FreeBSD? FreeBSD is an operating system based on 4.4 BSD Lite +for Intel, AMD, Cyrix or NexGen "x86" based PC hardware. It works +with a very wide variety of PC peripherals and configurations and can +be used for everything from software development to Internet Service +Provision; the busiest site on the Internet, ftp.cdrom.com, is a +FreeBSD machine! + +This release of FreeBSD contains everything you need to run such a +system, plus full source code for everything. With the source +distribution installed you can literally recompile the entire system +from scratch with one command, making it ideal for students, +researchers or folks who simply want to see how it all works. + +A large collection of 3rd party ported software (the "ports +collection") is also provided to make it easier for you to obtain and +install all your favorite traditional UNIX utilities for FreeBSD. +Over 270 ports, from editors to programming languages to graphical +applications, make FreeBSD a powerful and comprehensive operating +environment that rivals that of many large workstations for general utility +and power. + + +For more documentation on this system, it is recommended that you +purchase the 4.4BSD Document Set from O'Reilly Associates and the +USENIX Association, ISBN 1-56592-082-1. We have no connection with +O'Reilly, we're just satisfied customers! + +You may also wish to read the HARDWARE GUIDE *before* proceeding any +further with the installation. Configuring PC hardware for anything +other than DOS/Windows (which don't actually make very significant +demands on the hardware) is actually quite a bit harder than it looks, +and if you think you understand PCs then you clearly haven't been +using them for long enough! :) This guide will give you some tips on +how to configure your hardware and what symptoms to watch for in case +of trouble. This guide is available in the Documentation menu of the +FreeBSD boot floppy. + +DISCLAIMER: While FreeBSD does its best to safeguard against accidental +loss of data, it's still more than possible to WIPE OUT YOUR ENTIRE DISK +with this installation! Please do not proceed to the final FreeBSD +installation menu unless you've adequately backed up any important +data first! We really mean it! + +Technical comments on this release should be sent (in English!) to: + + hackers@FreeBSD.org + + +Bug reports should be sent using the `send-pr' command, if you were +able to get the system installed, otherwise to: + + bugs@FreeBSD.org + +Please be sure to indicate WHICH VERSION of FreeBSD you're running in +any bug reports! + + +General questions should be sent to: + + questions@FreeBSD.org + +Please have patience if your questions are not answered right away - +this is an especially busy time for us, and our volunteer resources +are often strained to the limit! Bug reports submitted with the +send-pr command are logged and tracked in our bugs database, and +you'll be kept informed of any changes in status during the life of +the bug (or feature request). + +Our WEB site, http://www.freebsd.org, is also a very good source for +updated information and provides a number of advanced documentation +facilities. You may use the BSDI version of Netscape for browsing the +World Wide Web directly from FreeBSD. + +You may also wish to look in /usr/share/FAQ and /usr/share/doc for +further information on the system. + + +Thanks for reading all of this, and we sincerely hope you enjoy this +release of FreeBSD! + + Jordan Hubbard, + for The FreeBSD Project diff --git a/release/sysinstall/help/en_US.ISO_8859-1/RELNOTES b/release/sysinstall/help/en_US.ISO_8859-1/RELNOTES new file mode 100644 index 0000000..9d6284f --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/RELNOTES @@ -0,0 +1,747 @@ + RELEASE NOTES + FreeBSD + Release 2.0.5 + +1. Technical overview +--------------------- + +FreeBSD is a freely available, full source 4.4 BSD Lite based release +for Intel i386/i486/Pentium (or compatible) based PC's. It is based +primarily on software from U.C. Berkeley's CSRG group, with some +enhancements from NetBSD, 386BSD, and the Free Software Foundation. + +Since our release of FreeBSD 2.0 some 8 months ago, the performance, +feature set, and stability of FreeBSD has improved dramatically. The +largest change is a revamped VM system with a merged VM/file buffer +cache that not only increases performance, but reduces FreeBSD's +memory footprint, making a 4MB configuration a more acceptable +minimum. Other enhancements include full NIS client and server +support, transaction TCP support, dial-on-demand PPP, an improved SCSI +subsystem, early ISDN support, support for FDDI and Fast Ethernet +(100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and +narrow) and many hundreds of bug fixes. + +We've also taken the comments and suggestions of many of our users to +heart and have attempted to provide what we hope is a more sane and +easily understood installation process. Your feedback on this +(constantly evolving) process is especially welcome! + +In addition to the base distributions, FreeBSD offers a new ported +software collection with some 270 commonly sought-after programs. The +list of ports ranges from http (WWW) servers, to games, languages, +editors and almost everything in between. The entire ports collection +requires only 10MB of storage, all ports being expressed as "deltas" +to their original sources. This makes it much easier for us to update +ports, and greatly reduces the disk space demands made by the older +1.0 ports collection. To compile a port, you simply change to the +directory of the program you wish to install, type make and let the +system do the rest. The full original distribution for each port you +build is retrieved dynamically off of CDROM or a local ftp site, so +you need only enough disk space to build the ports you want. (Almost) +every port is also provided as a pre-compiled "package" which can be +installed with a simple command (pkg_add) by those who do not wish to +compile their own ports from source. See the file: + /usr/share/FAQ/Text/ports.FAQ +for a more complete description of the ports collection. + + +Since our first release of FreeBSD 1.0 nearly two years ago, FreeBSD +has changed almost entirely. A new port from the Berkeley 4.4 code +base was done, which brought the legal status of the system out of the +shadows with the blessing of Novell (the new owners of USL and UNIX). The +port to 4.4 has also brought in a host of new features, filesystems +and enhanced driver support. With our new unencumbered code base, we +have every reason to hope that we'll be able to release quality +operating systems without further legal encumbrance for some time to +come! + +FreeBSD 2.0.5 represents the culmination of 2 years of work and many +thousands of man hours put in by an international development team. +We hope you enjoy it! + +A number of additional documents which you may find very helpful in +the process of installing and using FreeBSD may also be found in +the "FAQ" directory, either under /usr/share/FAQ on an installed +system or at the top level of the CDROM or FTP distribution from +where you're reading this file. Please consult FAQ/Text/ROADMAP +for a brief description of the resources provided by the FAQ directory. + +For a list of contributors and a general project description, please see +the file "CONTRIB.FreeBSD" which should be bundled with your binary +distribution. + +Also see the "REGISTER.FreeBSD" file for information on registering +with the "Free BSD user counter". This counter is for ALL freely +available variants of BSD, not just FreeBSD, and we urge you to register +yourself with it. + +The core of FreeBSD does not contain DES code which would inhibit its +being exported outside the United States. There is an add-on package +to the core distribution, for use only in the United States, that +contains the programs that normally use DES. The auxiliary packages +provided separately can be used by anyone. A freely (from outside the +U.S.) exportable European distribution of DES for our non-U.S. users also +exists and is described in the FreeBSD FAQ. + +If password security for FreeBSD is all you need, and you have no +requirement for copying encrypted passwords from different hosts +(Suns, DEC machines, etc) into FreeBSD password entries, then +FreeBSD's MD5 based security may be all you require! We feel that our +default security model is more than a match for DES, and without any +messy export issues to deal with. If you're outside (or even inside) +the U.S., give it a try! + + +1.1 What's new in 2.0.5? +------------------------ + +The following features were added or substantially improved between +the release of 2.0 and this 2.0.5 release. In order to facilitate +better communication, the person, or persons, responsible for each +enhancement is noted. Any questions regarding the new functionality +should be directed to them first. + +KERNEL: + +Merged VM-File Buffer Cache +--------------------------- +A merged VM/buffer cache design greatly enhances overall system +performance and makes it possible to do a number of more optimal +memory allocation strategies that were not possible before. + +Owner: David Greenman (davidg@FreeBSD.org) and + John Dyson (dyson@implode.root.com) + + +Network PCB hash optimization +----------------------------- +For systems with a great number of active TCP connections (WEB and ftp +servers, for example), this greatly speeds up the lookup time required +to match an incoming packet up to its associated connection. + +Owner: David Greenman (davidg@FreeBSD.org) + + +Name cache optimization +----------------------- +The name-cache would cache all files of the same name to the same bucket, +which would put for instance all ".." entries in the same bucket. We added +the parent directory version to frustrate the hash, and improved the +management of the cache in various other ways while we were at it. + +Owner: Poul-Henning Kamp (phk@FreeBSD.org) + David Greenman (davidg@FreeBSD.org) + + +Less restrictive swap-spaces +---------------------------- +The need to compile the names of the swap devices into the kernel has been +removed. Now swapon will accept any block devices, up to the maximum +number of swap devices configured in the kernel. + +Owner: Poul-Henning Kamp (phk@FreeBSD.org) + David Greenman (davidg@FreeBSD.org) + + +Hard Wired SCSI Devices +----------------------- +Prior to 2.0.5, FreeBSD performed dynamic assignment of unit numbers +to SCSI devices as they were probed, allowing a SCSI device failure to +possibly change unit number assignment and prevent filesystems on +still functioning disks from mounting. Hard wiring allows static +allocation of unit numbers (and hence device names) to scsi devices +based on SCSI ID and bus. SCSI configuration occurs in the kernel +config file. Samples of the configuration syntax can be found in the +scsi(4) man page or the LINT kernel config file. + +Owner: Peter Dufault (dufault@hda.com) +Sources involved: sys/scsi/* usr.sbin/config/* + + +Slice Support +------------- +FreeBSD now supports a "slice" abstraction which makes it more +completely interoperable with other operating system partitions. This +support will allow FreeBSD to inhabit DOS extended partitions. + +Owner: Bruce Evans (bde@FreeBSD.org) +Sources involved: sys/disklabel.h sys/diskslice.h sys/dkbad.h + kern/subr_diskslice.c kern/subr_dkbad.c + i386/isa/diskslice_machdep.c + i386/isa/wd.c scsi/sd.c dev/vn/vn.c + + +Support for Ontrack Disk Manager Version 6.0 +-------------------------------------------- +Support has been added for disks which use Ontrack Disk Manager. The +fdisk program does NOT know about it however, so make all changes +using the install program on the boot.flp or the Ontrack Disk Manager +tool under DOS. + +Owner: Poul-Henning Kamp (phk@FreeBSD.org) + + +Bad144 is back and working +-------------------------- +Bad144 works again, though the semantics are slightly different than +before in that the bad-spots are kept relative to the slice rather +than absolute on the disk. + +Owner: Bruce Evans (bde@FreeBSD.org) + Poul-Henning Kamp (phk@FreeBSD.org) + + +NEW DEVICE SUPPORT: + + SCSI and CDROM Devices + +Matsushita/Panasonic (Creative) CD-ROM driver +--------------------------------------------- +The Matsushita/Panasonic CR-562 and CR-563 drives are now supported +when connected to a Sound Blaster or 100% compatible host adapter. Up +to four host adapters are supported for a total of 16 CD-ROM drives. +The audio functions are supported, along with access to the raw (2352 byte) +data frames of any compact disc. Audio discs may be played using Karoke +variable speed functions. + +Owner: Frank Durda IV bsdmail@nemesis.lonestar.org +Sources involved: isa/matcd + + +Adaptec 2742/2842/2940 SCSI driver +---------------------------------- +The original 274x/284x driver has evolved considerably since the 2.0 +release. We now offer full support for the 2940 series as well as the +Wide models of these cards. The arbitration bug (as well as many +others) that caused the driver problems with fast devices has been +corrected and there is even experimental tagged queuing support +(kernel option "AHC_TAGENABLE"). John Aycock has also released the +sequencer code under a "Berkeley style" copyright making the driver +entirely clean of the GPL. + +Owner: Justin Gibbs (gibbs@FreeBSD.org) +Sources involved: isa/aic7770.c pci/aic7870.c i386/scsi/* + sys/dev/aic7xxx/* + + +NCR5380/NCR53400 SCSI ("ProAudio Spectrum") driver +-------------------------------------------------- +Owner: core +Submitted by: Serge Vakulenko (vak@cronyx.ru) +Sources involved: isa/ncr5380.c + + +Sony CDROM driver +----------------- +Owner: core +Submitted by: Mikael Hybsch (micke@dynas.se) +Sources involved: isa/scd.c + + + Serial Devices + +SDL Communications Riscom/8 Serial Board Driver +----------------------------------------------- +Owner: Andrey Chernov (ache@FreeBSD.org) +Sources involved: isa/rc.c isa/rcreg.h + + +Cyclades Cyclom-y Serial Board Driver +------------------------------------- +Owner: Bruce Evans (bde@FreeBSD.org) +Submitted by: Andrew Werple (andrew@werple.apana.org.au) and + Heikki Suonsivu (hsu@cs.hut.fi) +Obtained from: NetBSD +Sources involved: isa/cy.c + + +Cronyx/Sigma sync/async serial driver +------------------------------------- +Owner: core +Submitted by: Serge Vakulenko +Sources involved: isa/cronyx.c + + + + Networking + +Diskless booting +---------------- +Diskless booting in 2.0.5 is much improved. The boot-program is in +src/sys/i386/boot/netboot, and can be run from an MSDOS system or +burned into an EPROM. Local swapping is also possible. WD, SMC, 3COM +and Novell ethernet cards are currently supported. + + +DEC DC21140 Fast Ethernet driver +-------------------------------- +This driver supports any of the numerous NICs using the DC21140 chipset +including the 100Mb DEC DE-500-XA and SMC 9332. + +Owner: core +Submitted by: Matt Thomas (thomas@lkg.dec.com) +Sources involved: pci/if_de.c pci/dc21040.h + + +DEC FDDI (DEFPA/DEFEA) driver +----------------------------- +Owner: core +Submitted by: Matt Thomas (thomas@lkg.dec.com) +Sources involved: pci/if_pdq.c pci/pdq.c pci/pdq_os.h pci/pdqreg.h + + +3Com 3c505 (Etherlink/+) NIC driver +----------------------------------- +Owner: core +Submitted by: Dean Huxley (dean@fsa.ca) +Obtained from: NetBSD +Sources involved: isa/if_eg.c + + +Fujitsu MB86960A family of NICs driver +------------------------------------- +Owner: core +Submitted by: M.S. (seki@sysrap.cs.fujitsu.co.jp) +Sources involved: isa/if_fe.c + + +Intel EtherExpress driver +------------------------- +Owner: Rodney W. Grimes (rgrimes@FreeBSD.org) +Sources involved: isa/if_ix.c isa/if_ixreg.h + + +3Com 3c589 driver +----------------- +Owner: core +Submitted by: "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp), + Seiji Murata (seiji@mt.cs.keio.ac.jp) and + Noriyuki Takahashi (hor@aecl.ntt.jp) +Sources involved: isa/if_zp.c + + +IBM Credit Card Adapter driver +------------------------------ +Owner: core +Submitted by: "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp), +Sources involved: isa/pcic.c isa/pcic.h + + +EDSS1 and 1TR6 ISDN interface driver +------------------------------------ +Owner: core +Submitted by: Dietmar Friede (dfriede@drnhh.neuhaus.de) and + Juergen Krause (jkr@saarlink.de) +Sources involved: gnu/isdn/* + + + Miscellaneous Drivers + +Joystick driver +--------------- +Owner: Jean-Marc Zucconi (jmz@FreeBSD.org) +Sources involved: isa/joy.c + + +National Instruments "LabPC" driver +----------------------------------- +Owner: Peter Dufault (dufault@hda.com) +Sources involved: isa/labpc.c + + +WD7000 driver +------------- +Owner: Olof Johansson (offe@ludd.luth.se) + + +Pcvt Console driver +------------------- +Owner: Joerg Wunsch (joerg@FreeBSD.org) +Submitted by: Hellmuth Michaelis (hm@altona.hamburg.com) +Sources involved: isa/pcvt/* usr.sbin/pcvt/* + + +BSD-audio emulator for VAT driver +--------------------------------- +Owner: Amancio Hasty (ahasty@FreeBSD.org) and + Paul Traina (pst@FreeBSD.org) +Sources involved: isa/sound/vat_audio.c isa/sound/vat_audioio.h + + +National Instruments AT-GPIB and AT-GPIB/TNT GPIB driver +-------------------------------------------------------- +Owner: core +Submitted by: Fred Cawthorne (fcawth@delphi.umd.edu) +Sources involved: isa/gpib.c isa/gpib.h isa/gpibreg.h + + +Genius GS-4500 hand scanner driver +---------------------------------- +Owner: core +Submitted by: Gunther Schadow (gusw@fub46.zedat.fu-berlin.de) +Sources involved: isa/gsc.c isa/gscreg.h + + +CORTEX-I Frame Grabber +---------------------- +Owner: core +Submitted by: Paul S. LaFollette, Jr. +Sources involved: isa/ctx.c isa/ctxreg.h + + +Video Spigot video capture card +------------------------------- +Owner: Jim Lowe + + + +1.2 Experimental features +------------------------- + +The unionfs and LFS file systems are known to be severely broken in +2.0.5. This is in part due to old bugs that we haven't had time to +resolve yet and the need to update these file systems to deal with the +new VM system. We hope to address these issues in a later release of +FreeBSD. + +FreeBSD now supports running iBCS2 compatible binaries (currently SCO +UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported). The iBCS2 +emulator is in its early stages, but it is functional, we haven't been +able to do exhaustive testing (lack of commercial apps), but almost +all of SCO's 3.2.2 binaries are working, so is an old INFORMIX-2.10 +for SCO. Further testing is nessesary to complete this project. There +is also work under way for ELF & XOUT loaders, and most of the svr4 +syscall wrappers have been written. + +FreeBSD also implements enough of its Linux compatibility that we +can now run Linux DOOM! See the ``xperimnt'' directory (on your local +FTP server or CDROM) for full docs on how to set this up. + +Owner: Soren Schmidt (sos) & Sean Eric Fagan (sef) +Sources involved: sys/i386/ibcs2/* + misc kernel changes. + + +2. Supported Configurations +--------------------------- + +FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus +based PC's, ranging from 386sx to Pentium class machines (though the +386sx is not recommended). Support for generic IDE or ESDI drive +configurations, various SCSI controller, network and serial cards is +also provided. + +Following is a list of all disk controllers and ethernet cards currently +known to work with FreeBSD. Other configurations may very well work, and +we have simply not received any indication of this. + + +2.1. Disk Controllers +--------------------- + +WD1003 (any generic MFM/RLL) +WD1007 (any generic IDE/ESDI) +IDE +ATA + +Adaptec 152x series ISA SCSI controllers +Adaptec 154x series ISA SCSI controllers +Adaptec 174x series EISA SCSI controller in standard and enhanced mode. +Adaptec 274X/284X/2940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI controllers +Adaptec AIC-6260 and AIC-6360 based boards, which includes +the AHA-152x and SoundBlaster SCSI cards. + +** Note: You cannot boot from the SoundBlaster cards as they have no + on-board BIOS, which is necessary for mapping the boot device into the + system BIOS I/O vectors. They're perfectly usable for external tapes, + CDROMs, etc, however. The same goes for any other AIC-6x60 based card + without a boot ROM. Some systems DO have a boot ROM, which is generally + indicated by some sort of message when the system is first powered up + or reset. Check your system/board documentation for more details. + +[Note that Buslogic was formerly known as "Bustec"] +Buslogic 545S & 545c +Buslogic 445S/445c VLB SCSI controller +Buslogic 742A, 747S, 747c EISA SCSI controller. +Buslogic 946c PCI SCSI controller +Buslogic 956c PCI SCSI controller + +NCR 53C810 and 53C825 PCI SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + +DTC 3290 EISA SCSI controller in 1542 emulation mode. + +UltraStor 14F, 24F and 34F SCSI controllers. + +Seagate ST01/02 SCSI controllers. + +Future Domain 8xx/950 series SCSI controllers. + +WD7000 SCSI controller. + +With all supported SCSI controllers, full support is provided for +SCSI-I & SCSI-II peripherals, including Disks, tape drives (including +DAT) and CD ROM drives. + +The following CD-ROM type systems are supported at this time: +(cd) SCSI (also includes ProAudio Spectrum and SoundBlaster SCSI) +(mcd) Mitsumi proprietary interface +(matcd) Matsushita/Panasonic (Creative) proprietary interface +(scd) Sony proprietary interface + +Note: CD-Drives with IDE interfaces are not supported at this time. + +Some controllers have limitations with the way they deal with >16MB of +memory, due to the fact that the ISA bus only has a DMA address space +of 24 bits. If you do your arithmetic, you'll see that this makes it +impossible to do direct DMA to any address >16MB. This limitation is +even true of some EISA controllers (which are normally 32 bit) when +they're configured to emulate an ISA card, which they then do in *all* +respects. This problem is avoided entirely by IDE controllers (which +do not use DMA), true EISA controllers (like the UltraStor, Adaptec +1742A or Adaptec 2742) and most VLB (local bus) controllers. In the +cases where it's necessary, the system will use "bounce buffers" to +talk to the controller so that you can still use more than 16Mb of +memory without difficulty. + + +2.2. Ethernet cards +------------------- + +Allied-Telesis AT1700 and RE2000 cards +SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, +WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT +based clones. SMC Elite Ultra is also supported. + +DEC EtherWORKS III NICs (DE203, DE204, and DE205) +DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) +DEC DC21140 based NICs (SMC???? DE???) +DEC FDDI (DEFPA/DEFEA) NICs + +Fujitsu FMV-181 and FMV-182 + +Intel EtherExpress + +Isolan AT 4141-0 (16 bit) +Isolink 4110 (8 bit) + +Novell NE1000, NE2000, and NE2100 ethernet interface. + +3Com 3C501 cards + +3Com 3C503 Etherlink II + +3Com 3c505 Etherlink/+ + +3Com 3C507 Etherlink 16/TP + +3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III + +Toshiba ethernet cards + +PCMCIA ethernet cards from IBM and National Semiconductor are also +supported. + + +2.3. Misc +--------- + +AST 4 port serial card using shared IRQ. + +ARNET 8 port serial card using shared IRQ. + +BOCA ATIO66 6 port serial card using shared IRQ. + +Cyclades Cyclom-y Serial Board. + +STB 4 port card using shared IRQ. + +Mitsumi (all models) CDROM interface and drive. + +SDL Communications Riscom/8 Serial Board. + +SoundBlaster SCSI and ProAudio Spectrum SCSI CDROM interface and drive. + +Matsushita/Panasonic (Creative SoundBlaster) CDROM interface and drive. + +Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound +and Roland MPU-401 sound cards. + +FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but +support is apparently close to materializing. Details will be posted +as the situation develops. + + +3. Obtaining FreeBSD +-------------------- + +You may obtain FreeBSD in a variety of ways: + +1. FTP/Mail + +You can ftp FreeBSD and any or all of its optional packages from +`ftp.freebsd.org' - the official FreeBSD release site. + +For other locations that mirror the FreeBSD software see the file +MIRROR.SITES. Please ftp the distribution from the nearest site +to you netwise. + +If you do not have access to the internet and electronic mail is your +only recourse, then you may still fetch the files by sending mail to +`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message +to get more information on how to fetch files from ftp.freebsd.org. +Note: This approach will end up sending many *tens of megabytes* +through the mail, and should only be employed as an absolute LAST +resort! + + +2. CDROM + +FreeBSD 2.0.5 may be ordered on CDROM from: + + Walnut Creek CDROM + 4041 Pike Lane, Suite D + Concord CA 94520 + 1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax) + +Or via the internet from orders@cdrom.com or http://www.cdrom.com. +Their current catalog can be obtained via ftp as: + ftp://ftp.cdrom.com/cdrom/catalog. + +Cost per CD is $39.95, or $24.95 with a FreeBSD subscription. With +a subscription, you will automatically receive updates as they +are released. Your credit card will be billed when each disk is shipped +and you may cancel your subscription at any time without further obligation. + +Walnut Creek CDROM also sells a full line of FreeBSD related merchandise such +as T-shirts ($14.95, available in "child", Large and XL sizes), coffee mugs +($9.95), tattoos ($0.25 each) and posters ($3.00). + +Shipping (per order not per disc) is $5 in the US, Canada or +Mexico and $9.00 overseas. They accept Visa, Mastercard, Discover, +American Express or checks in U.S. Dollars and ship COD within the +United States. California residents please add 8.25% sales tax. + +Should you be dissatisfied for any reason, the CD comes with an +unconditional return policy. + + +Reporting problems, making suggestions, submitting code +------------------------------------------------------- + +Your suggestions, bug reports and contributions of code are always +valued - please do not hesitate to report any problems you may find +(preferably with a fix attached if you can!). + +The preferred method to submit bug reports from a machine with +internet mail connectivity is to use the send-pr command. Bug reports +will be dutifully filed by our faithful bugfiler program and you can +be sure that we'll do our best to respond to all reported bugs as soon +as possible. + +If, for some reason, you are unable to use the send-pr command to +submit a bug report, you can try to send it to: + + bugs@FreeBSD.org + + +Otherwise, for any questions or suggestions, please send mail to: + + questions@FreeBSD.org + +Additionally, being a volunteer effort, we are always happy to have +extra hands willing to help - there are already far more enhancements +to be done than we can ever manage to do by ourselves! To contact us +on technical matters, or with offers of help, you may send mail to: + + hackers@FreeBSD.org + +Since these mailing lists can experience significant amounts of +traffic, if you have slow or expensive mail access and you are +only interested in keeping up with significant FreeBSD events, you may +find it preferable to subscribe to: + + announce@FreeBSD.org + + +All but the freebsd-bugs groups can be freely joined by anyone wishing +to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword +`help' on a line by itself somewhere in the body of the message. This +will give you more information on joining the various lists, accessing +archives, etc. There are a number of mailing lists targeted at +special interest groups not mentioned here, so send mail to majordomo +and ask about them! + + +6. Acknowledgements +------------------- + +FreeBSD represents the cumulative work of many dozens, if not +hundreds, of individuals from around the world who have worked very +hard to bring you this release. It would be very difficult, if not +impossible, to enumerate everyone who's contributed to FreeBSD, but +nonetheless we shall try (in alphabetical order, of course). If your +name is not mentioned, please be assured that its omission is entirely +accidental. + + +The Computer Systems Research Group (CSRG), U.C. Berkeley. + +Bill Jolitz, for his initial work with 386BSD. + +The FreeBSD Core Team +(in alphabetical order by first name): + + Andreas Schulz <ats@FreeBSD.org> + Andrey A. Chernov <ache@FreeBSD.org> + Bruce Evans <bde@FreeBSD.org> + David Greenman <davidg@FreeBSD.org> + Garrett A. Wollman <wollman@FreeBSD.org> + Gary Palmer <gpalmer@FreeBSD.org> + Geoff Rehmet <csgr@FreeBSD.org> + Jack Vogel <jackv@FreeBSD.org> + John Dyson <dyson@FreeBSD.org> + Jordan K. Hubbard <jkh@FreeBSD.org> + Justin Gibbs <gibbs@FreeBSD.org> + Paul Richards <paul@FreeBSD.org> + Poul-Henning Kamp <phk@FreeBSD.org> + Rich Murphey <rich@FreeBSD.org> + Rodney W. Grimes <rgrimes@FreeBSD.org> + Satoshi Asami <asami@FreeBSD.org> + Søren Schmidt <sos@FreeBSD.org> + +Special mention to: + + Walnut Creek CDROM, without whose help (and continuing support) + this release would never have been possible. + + Dermot McDonnell for his donation of a Toshiba XM3401B CDROM + drive. + + Additional FreeBSD helpers and beta testers: + + J.T. Conklin Julian Elischer + Frank Durda IV Peter Dufault + Sean Eric Fagan Jeffrey Hsu + Terry Lambert L Jonas Olsson + Chris Provenzano Dave Rivers + Guido van Rooij Steven Wallace + Atsushi Murai Scott Mace + Nate Williams + + And everyone at Montana State University for their initial support. + + +Jordan would also like to give special thanks to Poul-Henning Kamp and +Gary Palmer, both of whom put in long hours helping him to construct +the new installation utility. Poul, being a proud new father, was +especially pressed for time and yet somehow managed to put in +a significant amount of effort anyway. This release could not have +happened without him! Thank you both! + +Thanks also to everyone else who helped, especially those not +mentioned, and we sincerely hope you enjoy this release of FreeBSD! + + + The FreeBSD Core Team + +$Id: RELNOTES,v 1.9 1995/06/10 02:40:11 jkh Exp $ diff --git a/release/sysinstall/help/en_US.ISO_8859-1/XF86.hlp b/release/sysinstall/help/en_US.ISO_8859-1/XF86.hlp new file mode 100644 index 0000000..c789eaa --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/XF86.hlp @@ -0,0 +1,500 @@ +README for XFree86 3.1.1u1 on FreeBSD 2.0.5 +Rich Murphey, David Dawes +20 January 1995 + +1. What and Where is XFree86? +------------------------------ + +XFree86 is a port of X11R6 that supports several versions of Intel- +based Unix. It is derived from X386 1.2, which was the X server +distributed with X11R5. This release consists of many new features +and performance improvements as well as many bug fixes. The release +is available as source patches against the X Consortium X11R6 code, as +well as binary distributions for many architectures. + +See the Copyright Notice (COPYRIGHT.html). + +The sources for XFree86 are available as part of the FreeBSD 2.0.5 +distribution, or by anonymous ftp from: + +ftp.XFree86.org:/pub/XFree86/current +(ftp://ftp.XFree86.org/pub/XFree86/current) + + +Binaries for XFree86 on FreeBSD are also available as part of +2.0.5 or from: + +ftp.XFree86.org:/pub/XFree86/current/binaries/FreeBSD-2.0 +(ftp://ftp.XFree86.org/pub/XFree86/current/binaries/FreeBSD-2.0) + +XFree86.cdrom.com:/pub/XFree86/current/binaries/FreeBSD-2.0 +(ftp://XFree86.cdrom.com/pub/XFree86/current/binaries/FreeBSD-2.0) + +Send email to Rich-Murphey@Rice.edu or XFree86@XFree86.org if you have +comments or suggestions about this file and we'll revise it. + + +2. Installing the Binaries +--------------------------- + +In the FreeBSD 2.0.5 distribution, XFree86 comes in 3 major sections: +"basic" distributions, fonts and servers. At the minimum, you will +need the binaries and libraries from the basic distribution, the +"misc" fonts collection and at least one server. The smallest usable +distribution is around 9MB. + +If you can't decide what to pick and you have 52Mb of disk +space, it's safe to unpack everything. + +What follows is a description of the various distribution files +comprising XFree86. If you are installing this as part of FreeBSD +2.0.5 then there's no need to use these files directly: You may +simply check the desired components off the installation menus +provided for that purpose. If you're installing this manually, +then the following information should prove useful: + + Required (6.7Mb): + + X311bin.tgz + all the executable X client applications and shared libs + + X311fnts.tgz + the misc and 75 dpi fonts + + X311lib.tgz + data files needed at runtime + + + Required unless you have already customized your configuration + files: + + X311xicf.tgz + customizable xinit runtime configuration file + + X311xdcf.tgz + customizable xdm runtime configuration file + + Choose at least one server ( 2.3Mb): + + X3118514.tgz + 8-bit color for IBM 8514 and true compatibles. + + X311AGX.tgz + 8-bit color for AGX boards. + + X311Mch3.tgz + 8 and 16-bit color for ATI Mach32 boards. + + X311Mch8.tgz + 8-bit color for ATI Mach8 boards. + + X311Mono.tgz + 1-bit monochrome for VGA, Super-VGA, Hercules, and others. + + X311P9K.tgz + 8, 16, and 24-bit color for Weitek P9000 boards (Diamond + Viper). + + X311S3.tgz + 8, 16 and 24-bit color for S3 boards (#9 GXE, Actix GE32, + SPEA Mercury, STB Pegasus) + + X311SVGA.tgz + 8-bit color for Super-VGA cards. + + X311VG16.tgz + 4-bit color for VGA and Super-VGA cards + + X311W32.tgz + 8-bit Color for ET4000/W32, /W32i and /W32p cards. + + X311nest.tgz + A nested server running as a client window on another + display. + + Optional: + + X311doc.tgz + (.5Mb) READMEs and XFree86 specific man pages + + X311man.tgz + (1.7Mb) man pages except XFree86 specific ones in etc archive + + X311f100.tgz + (1.8Mb) 100dpi fonts + + X311fscl.tgz + (1.6Mb) Speedo and Type1 fonts + + X311fnon.tgz + (3.3Mb) Japanese, Chinese and other non-English fonts + + X311fsrv.tgz + (.3Mb) the font server and it's man page + + X311prog.tgz + (3.9Mb) config, lib*.a and *.h files needed only for + compiling + + X311link.tgz + (7.8Mb) X server reconfiguration kit + + X311pex.tgz + (.5Mb) PEX fonts and shared libs needed by PEX applications. + + X311lbx.tgz + (.2Mb) low bandwidth X proxy server and libraries. + +Note that there is no longer a separate xdm archive. FreeBSD 2.0 +and later handles this in shared libraries now, so that the xdm +binary does not itself contain des and there is no more need for +us to provide separate tar balls. + + +2.1. Full Install: +------------------- + +[ Note: Unless you're installing XFree86 3.1.1u1 manually, that is + to say not as part of the FreeBSD 2.0.5 installation, you may skip + to section 2.3 ] + + 1. You must be logged in as root to unpack the archives because + several executables are set-user-id. Otherwise the server may + abort if you unpack it as an ordinary user. You must also use a + ``umask'' value of 022 because the X server requires special + permissions. + + % su + # umask 022 + + + 2. If you have 52Mb free in the /usr partition ``cd /usr'' and skip + to no. 3. Otherwise, create a directory on another partition + and sym link it into /usr: + + # cd /usr/local + # mkdir X11R6 + # ln -s /usr/local/X11R6 /usr/X11R6 + + + 3. Unpack everything: + + If you are using sh (as root usually does): + + # for i in X311*.tgz; do + # tar -xzf $i + # done + + + Else, if you are using csh: + + % foreach i (X311*.tgz) + % tar -xzf $i + % end + + + 4. Create a symbolic link ``X'' that points to the server that + matches your video card. The XF86_* man pages list which vga + chip sets are supported by each server. For example, if you + have an ET4000 based card you will use the XF86_SVGA server: + + # cd /usr/X11R6/bin; rm X; ln -s XF86_SVGA X + + +2.2. Minimal Install: +---------------------- + +First do numbers 1 and 2 above. Then unpack the required archives: + + # for i in bin fnts lib xicf; do + # tar -xzf X311$i.tgz + # done + + +Then unpack a server archive corresponding to your vga card. The +server man pages, X11R6/man/man1/XF86_*, list the vga chip sets +supported by each server. For example, if you have an ET4000 based +card you will use the XF86_SVGA server: + + # tar -xzf X311SVGA.tgz + # cd /usr/X11R6/bin; rm X; ln -s XF86_SVGA X + + +2.3. After either Full or Minimal Install above: +------------------------------------------------- + +Add /usr/X11R6/bin to the default path for sh in /etc/profile and for +csh in /etc/csh.login if they are not already there: + + # echo 'set path = ($path /usr/X11R6/bin)' >>/etc/csh.login + # echo 'PATH=$PATH:/usr/X11R6/bin' >>/etc/profile + + +Or make sure all who use X put /usr/X11R6/bin in their shell's +``path'' variable. + +Next either reboot or invoke ldconfig as root to put the shared +libraries in ld.so's cache: + + # ldconfig /usr/lib /usr/local/lib /usr/X11R6/lib + + +If you had already configured X11R6/lib/X11/xinit/xinitrc or +X11R6/lib/X11/xdm/* omit the xinit-config or xdm-config archive or +unpack it separately and merge in your customizations. + +The fscl and f100 archives are optional and can be omitted if you are +short on space. The optional link archive allows you to reconfigure +and customize a X server binary. The optional prog archive is needed +only for writing or compiling X applications. The optional pex +archive contains pex clients and libraries for building 3D graphics +applications. + + NOTE: You don't need to uncompress the font files, but if + you uncompress them anyway you must run mkfontdir in the + corresponding font directory; otherwise your server will + abort with the message ``could not open default font + 'fixed'''. + + +3. Installing The Display Manager (xdm) +---------------------------------------- + +The display manager makes your PC look like an X terminal. That is, +it presents you with a login screen that runs under X. + +The easiest way to automatically start the display manager on boot is +to add a line in /etc/ttys to start it on one of the unoccupied +virtual terminals: + + ttyv4 "/usr/X11R6/bin/xdm -nodaemon" xterm on secure + +You should also make sure that /usr/X11R6/bin/X is a symbolic link to +the Xserver that matches your video card or edit the file Xservers in +/usr/X11R6/lib/X11/xdm to specify the pathname of the X server. + +The change to /etc/ttys won't take effect until you either reboot or +``kill -HUP 1'' to force initd to reread /etc/ttys. You can also test +the display manager manually by loging in as root on the console and +typing ``xdm -nodaemon''. + + +4. Configuring X for Your Hardware +----------------------------------- + +The XF86Config file tells the X server what kind of monitor, video +card and mouse you have. You must create it to tell the server what +specific hardware you have. + +XFree86 3.1 uses a new configuration file format. Consult the +XF86Config man page and the general INSTALL (INSTALL.html) file for +instructions. + +If you have a Xconfig file for XFree86 2.x, use reconfig to translate +part of it into the new format: + + # reconfig <Xconfig >XF86Config + +and complete the rest according to the XF86Config man page and the +XF86Config.sample file as a template. + +In order to protect your hardware from damage, the server no longer +will read XF86Config files from a user's home directory, but requires +that it be in /etc/XF86Config, /usr/X11R6/lib/X11/XF86Config.hostname +or /usr/X11R6/lib/X11/XF86Config. + +You'll need info on your hardware: + + o Your mouse type, baud rate and it's /dev entry. + + o The video card's chipset (e.g. ET4000, S3, etc). + + o Your monitor's sync frequencies. + +The easiest way to find which device your mouse is plugged into is to +use ``cat'' or ``kermit'' to look at the output of the mouse. Connect +to it and just make sure that it generates output when the mouse is +moved or clicked: + + % cat < /dev/cuaa0 + +If you can't find the right mouse device then use ``dmesg|grep sio'' +to get a list of devices that were detected upon booting: + + % dmesg|grep sio + sio0 at 0x3f8-0x3ff irq 4 on isa + +Then double check the /dev entries corresponding to these devices. +Use the script /dev/MAKEDEV to create entries if they don't already +exist: + + % cd /dev + % sh MAKEDEV cuaa0 + +If you plan to fine tune the screen size or position on your monitor +you'll need the specs for sync frequencies from your monitor's manual. + + +5. Running X +------------- + +8mb of memory is a recommended minimum for running X. The server, +window manager, display manager and an xterm take about 8Mb of virtual +memory themselves. Even if their resident set size is smaller, on a +8Mb system that leaves very space for other applications such as gcc +that expect a few meg free. The R6 X servers may work with 4Mb of +memory, but in practice compilation while running X can take 5 or 10 +times as long due to constant paging. + +The easiest way for new users to start X windows is to type ``startx +>& startx.log''. Error messages are lost unless you redirect them +because the server takes over the screen. + +To get out of X windows, type: ``exit'' in the console xterm. You can +customize your X by creating .xinitrc, .xserverrc, and .twmrc files in +your home directory as described in the xinit and startx man pages. + + +6. Rebuilding Kernels for X +---------------------------- + +The GENERIC FreeBSD 2.0 kernel supports XFree86 without any +modifications required. You do not need to make any changes to the +GENERIC kernel or any kernel configuration which is a superset. + +For a general description of BSD kernel configuration get +smm.02.config.ps.Z +(ftp://gatekeeper.dec.com/pub/BSD/manuals/smm.02.config.ps.Z). It is +a ready-to-print postscript copy of the kernel configuration chapter +from the system maintainers manual. + +If you do decide to reduce your kernel configuration file, do not +remove the two lines below (in /sys/arch/i386/conf). They are both +required for X support: + + options XSERVER #Xserver + options UCONSOLE #X Console support + +The generic FreeBSD 2.0 kernel is configured by default with the +syscons driver. To configure your kernel similarly it should have a +line like this in /usr/src/sys/i386/conf/GENERIC: + + device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr + +The maximum number of virtual consoles can be set using the MAXCONS +option: + + options "MAXCONS=4" #4 virtual consoles + + +Otherwise, the default without a line like this is 12. You must have +more VTs than gettys as described in the end of section 3, and 4 is a +reasonable minimum. + +The server supports several console drivers: pccons, syscons and pcvt. +The syscons driver is the default in FreeBSD 1.1.5 and higher. They +are detected at runtime and no configuration of the server itself is +required. + +The pcvt console driver is bundled into FreeBSD and may be enabled +by changing the `sc0' line in your kernel configuration file to +`vt0'. See /sys/i386/conf/LINT for more details. + +The XFree86 servers include support for the MIT-SHM extension. The +GENERIC kernel does not support this, so if you want to make use of +this, you will need a kernel configured with SYSV shared memory +support. To do this, add the following line to your kernel config +file: + + options SYSVSHM # System V shared memory + options SYSVSEM # System V semaphores + options SYSVMSG # System V message queues + + +If you are using a SoundBlaster 16 on IRQ 2 (9), then you need a patch +for sb16_dsp.c. Otherwise a kernel configured with the SoundBlaster +driver will claim interrupt 9 doesn't exist and X server will lock up. + +S3 cards and serial port COM 4 cannot be installed together on a +system because the I/O port addresses overlap. + + +7. Rebuilding XFree86 +---------------------- + +The server link kit allows you to build an X server using a minimum +amount of disk space. Just unpack it, make the appropriate changes to +site.def, type ``./mkmf' and ``make'' to link the server. See +README.LinkKit (LinkKit.html) for more info. + +The source tree takes about 114Mb before compiling and an additional +100Mb after ``make World''. You should configure the distribution by +editing xf86site.def and site.def in xc/config/cf before compiling. +By default, the config files are set up to build shared libraries. If +you are running a version of FreeBSD that doesn't include shared +library support, add the following line to site.def: + + #define BuildBsdSharedLibs NO + +If your system doesn't have support or SYSV shared memory (for +example, if you don't have the <sys/shm.h> header), you should disable +the MIT-SHM extension by adding the following line to site.def: + + #define HasShm NO + +To compile the sources on FreeBSD 1.1 and later, type: + + make World + + +8. Building Other X Clients +---------------------------- + +The easiest way to build a new client (X application) is to use xmkmf +if an Imakefile is included with it. Type ``xmkmf -a'' to create the +Makefiles, then type ``make''. Whenever you install additional man +pages you should update whatis.db by running ``makewhatis +/usr/X11R6/man''. + +Note: Starting with XFree86 2.1 and FreeBSD 1.1, the symbol __386BSD__ +no longer gets defined either by the compiler or via the X config +files for FreeBSD systems. When porting clients to BSD systems, make +use of the symbol BSD for code which is truly BSD-specific. The value +of the symbol can be used to distinguish different BSD releases. For +example, code specific to the Net-2 and later releases can use: + + #if (BSD >= 199103) + +To ensure that this symbol is correctly defined, include <sys/param.h> +in the source that requires it. Note that the symbol CSRG_BASED is +defined for *BSD systems in XFree86 3.1.1 and later. This should be +used to protect the inclusion of <sys/param.h>. + +For code that really is specific to a particular i386 BSD port, use +__FreeBSD__ for FreeBSD, __NetBSD__ for NetBSD, __386BSD__ for 386BSD, +and __bsdi__ for BSD/386. + + +9. Thanks +---------- + +Many thanks to: + + o Pace Willison for providing initial *BSD support. + + o Amancio Hasty for 386BSD kernel and S3 chipset support. + + o David Greenman, Nate Williams, Jordan Hubbard for FreeBSD kernel + support. + + o Rod Grimes, Jordan Hubbard and Jack Velte for the use of Walnut + Creek Cdrom's hardware. + + o Orest Zborowski, Simon Cooper and Dirk Hohndel for ideas from + the Linux distribution. + +$XConsortium: FreeBSD.sgml,v 1.3 95/01/23 15:34:41 kaleb Exp $ +Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/FreeBSD.sgml,v 3.10 1995/01/28 16:01:28 dawes Exp $ + + +$XFree86: xc/programs/Xserver/hw/xfree86/doc/READ.FreeBSD,v 3.12 1995/01/28 16:19:37 dawes Exp $ diff --git a/release/sysinstall/help/en_US.ISO_8859-1/configure.hlp b/release/sysinstall/help/en_US.ISO_8859-1/configure.hlp new file mode 100644 index 0000000..2d14031 --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/configure.hlp @@ -0,0 +1,14 @@ +This menu allows you to configure your system after the installation process +is complete. At the minimum, you should probably set the system manager's +password and the system time zone. + +For extra goodies like bash, emacs, pascal, etc., you should look at the +Packages item in this menu. Currently, the Packages option is only useful +if you have a CDROM or an existing packages collection somewhere in the +file system hierarchy where the package management tool can locate it. +The automatic transfer of packages via FTP is not yet supported! + +If you wish to re-invoke the package installation tool after leaving +the system installation, the command is ``pkg_manage''. For setting +the timezone, type ``tzsetup''. For more information on the general +system configuration, see the ``/etc/sysconfig'' file. diff --git a/release/sysinstall/help/en_US.ISO_8859-1/distributions.hlp b/release/sysinstall/help/en_US.ISO_8859-1/distributions.hlp new file mode 100644 index 0000000..b81efbf --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/distributions.hlp @@ -0,0 +1,88 @@ +An ``X-'' prefixed before a distribution set means that the XFree86 +3.1.1u1 base distribution, libraries, manual pages, SVGA server and a +set of default fonts will be selected in addition to the set itself. + +If you select such a set, you will also be presented with a set of +menus for customizing the selections to your desired X Window System +setup. + +N.B. All references in this document to `complete source' mean the +complete source tree minus any legally encumbered cryptography code. + +The current "canned" installations are as follows: + +Developer: Base ("bin") distribution, man pages, dictionary + files, profiling libraries and the complete source tree. + + +Kern-Developer: As above, but with only kernel sources instead of + the complete source tree. + + +User: The base distribution, man pages, dictionary files and + the FreeBSD 1.x and 2.0 compatibility sets. + + +Minimal: Only the base distribution. + + +Everything: The base distribution, man pages, dictionary files, + profiling libraries, the FreeBSD 1.x and the FreeBSD 2.0 + compatibility libraries, the complete source tree, + games and your choice of XFree86 distribution components. + N.B. Still no cryptocraphy source code! + + +Custom: Allows you to modify or create your distribution set on + a piece-by-piece basis. + + +Reset: Clear all currently selected distributions. + + +--- + +When using Custom, most of the sub-distribution choices are fairly +obvious, though two possible exceptions may be the "commerce" and +"xperimnt" distributions: + + * The "commerce" directory, as its name implies, is devoted to + commercial offerings. This includes commercial products released + under special arrangement, limited functionality demos, shareware + products (you like it, you buy it), etc. + + At the time of this writing, there are unfortunately not enough + commercial offerings to justify a fully split distribution set, + so each product is available both as a subdirectory and as part + of one large archive file. If you select "commerce" from the + distributions submenus then you'll get the big file containing + the entire collection copied to your hard disk. Don't do this + unless you've got at least 10MB to devote to it! + + + * The "xperimnt" directory contains, not surprisingly, experimental + offerings. Unfinished (or work-in-progress) features, special + purpose drivers and packages, strange proof-of-concept stuff, + it's a mixed bag! Select this item on a distribution menu and + you'll get the whole collection (between 10 and 30MB). + + + If you're installing from CDROM then all of the commercial and + "experimental" offerings are also easily available in their + individual subdirectories and can be copied to hard disk at + any time. + + +You may also notice that certain distributions, like "des" and "krb", +are marked "NOT FOR EXPORT!" This is because it's illegal to +export them from the United States (or any other country which +considers encryption technology to be on its restricted export +list). Since breaking this law only gets the _originating_ site +(US!) in trouble, please do not load these distributions from U.S. +servers! + +A number of "foreign" servers do exist for the benefit of +non-U.S. sites, one of which is "skeleton.mikom.csir.co.za". + +Please get all such export restricted software from there +if you are outside the U.S., thanks! diff --git a/release/sysinstall/help/en_US.ISO_8859-1/drives.hlp b/release/sysinstall/help/en_US.ISO_8859-1/drives.hlp new file mode 100644 index 0000000..d924f8d --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/drives.hlp @@ -0,0 +1,28 @@ +If you are going to actually install some portion of FreeBSD on a +drive then PLEASE BE VERY CERTAIN that the Geometry reported in the +Partition Editor (see Installation Menu) is the correct one for your +drive and controller combination! + +IDE drives often have a certain geometry set during the PC BIOS setup, +or (in the case of larger IDE drives) have their geometry "remapped" +by either the IDE controller or a special boot-sector translation +utility such as that by OnTrack Systems. In these cases, knowing +the correct geometry gets even more complicated as it's not something +you can easily tell by looking at the drive or the PC BIOS setup. The +best way of verifying that your geometry is being correctly calculated +in such situations is to boot DOS (from the hard disk, not a floppy!) +and run the ``pfdisk'' utility provided in the tools/ subdirectory of the +FreeBSD CDROM or FTP site. It will report the geometry that DOS sees, +which is generally the correct one. + +If you have no DOS partition sharing the disk at all, then you may find that +you have better luck with Geometry detection if you create a very small +DOS partition first, before installing FreeBSD. Once FreeBSD is installed +you can always delete it again if you need the space. + +It's actually not a bad idea (believe it or not) to have a small bootable +DOS partition on your FreeBSD machine anyway: Should the machine become +unstable or exhibit strange behavior at some point in the future (which +is not uncommon behavior for PC hardware!) you can then at least use +DOS for installing and running one of the commercially available system +diagnostic utilities. diff --git a/release/sysinstall/help/en_US.ISO_8859-1/hardware.hlp b/release/sysinstall/help/en_US.ISO_8859-1/hardware.hlp new file mode 100644 index 0000000..fba5633 --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/hardware.hlp @@ -0,0 +1,384 @@ +Hardware Documentation Guide: $Id: hardware.hlp,v 1.11 1995/06/09 13:29:19 jkh Exp $ + +Table of Contents +----------------- + +0. Document Conventions +1. Using UserConfig to change FreeBSD kernel settings +2. Default Configuration (GENERIC kernel) +3. LINT - other possible configurations. +4. Known Hardware Problems. + +========================================================================= + +0. Document Conventions +-- -------------------- + +We have `underlined' text which represents user input with `-' +symbols throughout this document to differentiate it from +the machine output. + +1. Using UserConfig to change FreeBSD kernel settings +-- -------------------------------------------------- + +The UserConfig utility allows you to override various settings of +the FreeBSD kernel before the system has booted. This allows you to +make minor adjustments to the various drivers in the system without +necessarily having to recompile the kernel. + +UserConfig is activated by specifying the `-c' flag at the initial +boot prompt. For example: + + >> FreeBSD BOOT @ 0x10000: 640/7168 k of memory + Use hd(1,a)/kernel to boot sd0 when wd0 is also installed. + Usage: [[wd(0,a)]/kernel][-abcCdhrsv] + Use ? for file list or press Enter for defaults + + Boot: -c + -- + +This command causes the system to boot the default kernel ("/kernel") and +the UserConfig utility to be started once the kernel is loaded into memory. + +The `-c' flag follows any of the other parameters you may need to provide +for the system to boot properly. For example, to boot off the second of +two SCSI drives installed and run UserConfig, you would type: + + Boot: sd(1,a)/kernel -c + ----------------- + +As always, the kernel will report some information on your processor +and how much memory your system has. Then UserConfig will be invoked +and you will see the prompt: + + config> + +To see the list of commands that UserConfig accepts, you may type '?' and +press [ENTER]. The help message looks something like this: + +Command Description +------- ----------- +attach <devname> Return results of device attach +ls List currently configured devices +port <devname> <addr> Set device port (i/o address) +irq <devname> <number> Set device irq +drq <devname> <number> Set device drq (DMA Request) +iomem <devname> <addr> Set device maddr (memory address) +iosize <devname> <size> Set device memory size +flags <devname> <mask> Set device flags +enable <devname> Enable device +probe <devname> Return results of device probe +disable <devname> Disable device (will not be probed) +quit Exit this configuration utility +help This message + + +You may alter nearly all of the default settings present in the FreeBSD +generic kernel. This includes reassigning IRQs, disabling troublesome +devices (or drivers that conflict with the hardware your system has), +setting special device flags, etc. + +The most common use of UserConfig is to adjust or disable a driver +which is causing trouble. The "ls" command displays the current +settings for all the drivers present in the booted kernel, and +once you have located an entry of interest you may use the displayed +device name to change its settings or even disable the driver completely. + +For example, to change the memory address of network adapter 'ed0' to +the address 0xd4000, you would type + + config> iomem ed0 0xd4000 + ----------------- + +To entirely disable a device driver you are not using, use the +"disable" command. In this example, you would disable device +`ie0' by typing: + + config> disable ie0 + ----------- + +You can use the "ls" command to verify your changes and correct +any other problems before continuing the boot process. + +Once you are happy with a given configuration you may type: "quit" + +This will cause the kernel to boot with the new settings you +have chosen. + +Once you have a fully installed system (e.g. the `bin' distribution +has been successfully extracted), any changes you make in UserConfig +are permanently stored in the `/kernel' file on the root filesystem. +This action is performed by the `dset' utility, which will ensure that +these settings remain in effect until you replace the kernel with +a new one. If you do not want your changes to be permanently +stored like this, remove `dset' from the /etc/rc file before you +make any changes. + +If you accidentally change a setting for a device that you did not mean +to change, the safest thing to do is to reset the computer and start +over. Do not allow the boot to proceed (e.g. do not type "quit") with +bad settings as these may be permanently stored by dset and +leave your system in a state where it will no longer run properly. + +We suggest as a general rule that you disable any drivers that are not +used by your particular hardware configuration. There are known problems +with certain device drivers (see section 4.0) that can cause conflicts +with other devices if they're also not disabled. You should move or +disable any device that resides at the same port or IRQ as a device +you actually have! + +You can also remove drivers that are not needed by building yourself a +custom kernel that contains only the device drivers which your system +really needs (see section 6.0 of the FreeBSD.FAQ). If your system has +sufficient free disk space to store and compile the kernel sources, +this is the option we most highly recommend. + + + +2. Default (GENERIC) Configuration +-- ------------------------------- + +The following table contains a list of all of the devices that are present +in the GENERIC kernel, which is the kernel (the operating system) that was +placed on your computer during the FreeBSD installation process. +(A compressed version of the GENERIC kernel is also used on the +installation floppy diskettes.) + +The table describes the various parameters used by the driver to communicate +with the hardware in your system. There are four parameters in the +table, but not all are used by each device. They are: + + Port the starting I/O port used by the device, shown in hexadecimal. + + IOMem the lowest (or starting) memory address used by the device, + also shown in hexadecimal. + + IRQ the interrupt the device uses to alert the driver to an event, + given in decimal. + + DRQ the DMA (direct memory access) channel the device uses to move + data to and from main memory, also given in decimal. + +If an entry in the table has `n/a' for the value, it means that the +parameter does not apply to that device. A value of `dyn' means that the +correct value should be determined automatically by the kernel when the +system boots. + + +FreeBSD GENERIC kernel: + + Port IRQ DRQ IOMem Description + ---- --- --- ----- --------------------------------- +fdc0 3f0 6 2 n/a Floppy disk controller +wdc0 1f0 14 n/a n/a IDE/MFM/RLL disk controller +wdc1 170 15 n/a n/a IDE/MFM/RLL disk controller + +ncr0 n/a n/a n/a n/a NCR PCI SCSI controller +ahc0 n/a n/a n/a n/a Adaptec 294x PCI SCSI controller +bt0 330 dyn dyn dyn Buslogic SCSI controller +uha0 330 dyn 6 dyn Ultrastore 14f +ahc1 dyn dyn dyn dyn Adaptec 274x/284x SCSI controller +ahb0 dyn dyn dyn dyn Adaptec 174x SCSI controller +aha0 330 dyn 5 dyn Adaptec 154x SCSI controller +aic0 340 11 dyn dyn Adaptec 152x/AIC-6360 SCSI + controller +nca0 1f88 10 dyn dyn ProAudioSpectrum cards +nca1 350 5 dyn dyn ProAudioSpectrum cards +sea0 dyn 5 dyn c8000 Seagate ST01/02 8 bit controller + +wt0 300 5 1 dyn Wangtek and Archive QIC-02/QIC-36 + +mcd0 300 10 n/a n/a Mitsumi CD-ROM +mcd1 340 11 n/a n/a Mitsumi CD-ROM + +matcd0 dyn n/a n/a n/a Matsushita/Panasonic CD-ROM + +scd0 230 n/a n/a n/a Sony CD-ROM + +sio0 3f8 4 n/a n/a Serial Port 0 (COM1) +sio1 2f8 3 n/a n/a Serial Port 1 (COM2) +sio2 3e8 5 n/a n/a Serial Port 2 (COM3) +sio3 2e8 9 n/a n/a Serial Port 3 (COM4) + +lpt0 dyn 7 n/a n/a Printer Port 0 +lpt1 dyn dyn n/a n/a Printer Port 1 +lpt2 dyn dyn n/a n/a Printer Port 2 + +de0 DEC DC21x40 PCI based cards + (including 21140 100bT cards) +ed0 280 5 dyn d8000 WD & SMC 80xx; Novell NE1000 & + NE2000; 3Com 3C503 +ed1 300 5 dyn d8000 Same as ed0 +eg0 310 5 dyn dyn 3Com 3C505 +ep0 300 10 dyn dyn 3Com 3C509 +ie0 360 7 dyn d0000 AT&T StarLAN 10 and EN100; + 3Com 3C507; NI5210 +ix0 300 10 dyn d0000 Intel EtherExpress cards +le0 300 5 dyn d0000 Digital Equipment EtherWorks + 2 and EtherWorks 3 +lnc0 280 10 n/a dyn Lance/PCnet cards + (Isolan, Novell NE2100, NE32-VL) +lnc1 300 10 n/a dyn See lnc0 +ze0 300 5 dyn d8000 IBM/National Semiconductor + PCMCIA Ethernet Controller +zp0 300 10 dyn d8000 3Com PCMCIA Etherlink III + Ethernet Controller +--- End of table --- + + +If the hardware in your computer is not set to the same settings as +those shown in this table and the item is not marked 'dyn', you will +have to either reconfigure your hardware, or use UserConfig ('-c' boot +option) to reconfigure the kernel to match the way your hardware is +currently set (see section 1.0). + +If the settings do not match, the kernel may be unable to locate +or reliably access the devices in your system. + + + +3. LINT - other possible configurations +-- ------------------------------------ + +The following drivers are not in the GENERIC kernel but remain +available to those who do not mind compiling a custom kernel (see +section 6 of FreeBSD.FAQ). The LINT configuration file +(/sys/i386/conf/LINT) also contains prototype entries for just about +every device supported by FreeBSD and is a good general reference. + +The device names and a short description of each are listed below. The port +numbers, etc, are not meaningful here since you will need to compile a +custom kernel to gain access to these devices anyway and can thus +adjust the addresses to match the hardware in your computer in the process. +The LINT file contains prototype entries for all of the below which you +can easily cut-and-paste into your own file (or simply copy LINT and edit +it to taste): + +apm: Laptop Advanced Power Management (experimental) +ctx: Cortex-I frame grabber +cx: Cronyx/Sigma multiport sync/async +cy: Cyclades high-speed serial driver +el: 3Com 3C501 +fe: Fujitsu MB86960A/MB86965A Ethernet cards +fea: DEV DEFEA EISA FDDI adater +fpa: DEC DEFPA PCI FDDI adapter +gp: National Instruments AT-GPIB and AT-GPIB/TNT board +gsc: Genius GS-4500 hand scanner +gus: Gravis Ultrasound - Ultrasound, Ultrasound 16, Ultrasound MAX +gusmax: Gravis Ultrasound MAX (currently broken) +gusxvi: Gravis Ultrasound 16-bit PCM +joy: Joystick +labpc: National Instrument's Lab-PC and Lab-PC+ +mpu: Roland MPU-401 stand-alone card +mse: Logitech & ATI InPort bus mouse ports +mss: Microsoft Sound System +nic: Dr Neuhaus NICCY 3008, 3009 & 5000 ISDN cards +opl: Yamaha OPL-2 and OPL-3 FM - SB, SB Pro, SB 16, ProAudioSpectrum +pas: ProAudioSpectrum PCM and MIDI +pca: PCM audio ("/dev/audio") through your PC speaker +psm: PS/2 mouse port +rc: RISCom/8 multiport card +sb: SoundBlaster PCM - SoundBlaster, SB Pro, SB16, ProAudioSpectrum +sbmidi: SoundBlaster 16 MIDI interface +sbxvi: SoundBlaster 16 +spigot: Create Labs Video Spigot video-acquisition board +uart: Stand-alone 6850 UART for MIDI +wds: Western Digital WD7000 IDE + +--- end of list --- + + +4. Known Hardware Problems, Q & A: +-- ------------------------------- + +Q: mcd0 keeps thinking that it has found a device and this stops my Intel + EtherExpress card from working. + +A: Use the UserConfig utility (see section 1.0) and disable the probing of + the mcd0 and mcd1 devices. Generally speaking, you should only leave + the devices that you will be using enabled in your kernel. + + +Q: The system finds my ed network card, but I keep getting device + timeout errors. + +A: Your card is probably on a different IRQ from what is specified in the + kernel configuration. The ed driver will no longer use the `soft' + configuration by default (values entered using EZSETUP in DOS), but it + will use the software configuration if you specify `?' in the IRQ field + of your kernel config file. The reason for the change is because the + ed driver used to read and try to use the soft configuration information + even when the card was jumpered to use a hard configuration, and this + caused problems. + + Either move the jumper on the card to a hard configuration setting + (altering the kernel settings if necessary), or specify the IRQ as + `-1' in UserConfig or `?' in your kernel config file. This will + tell the kernel to use the soft configuration. + + Another possibility is that your card is at IRQ 9, which is shared + by IRQ 2 and frequently a cause of problems (especially when you + have a VGA card using 2! :). You should not use IRQ 2 or 9 if at + all possible. + + +Q: I go to boot from the hard disk for the first time after installing + FreeBSD, but the Boot Manager prompt just prints `F?' at the boot menu + each time but the boot won't go any further. + +A: The hard disk geometry was set incorrectly in the Partition editor when + you installed FreeBSD. Go back into the partition editor and specify + the actual geometry of your hard disk. You must reinstall FreeBSD + again from the beginning with the correct geometry. + + If you are failing entirely in figuring out the correct geometry for + your machine, here's a tip: Install a small DOS partition at the + beginning of the disk and install FreeBSD after that. The install + program will see the DOS partition and try to infer the correct + geometry from it, which usually works. + + +Q: I have a Matsushita/Panasonic CD-ROM drive but it isn't recognized + by the system, even if I use UserConfig to change the Port address to + 630, which is what my card uses. + +A: Not all of the companies that sell the Matsushita/Panasonic CR-562 + and CR-563 drives use the same I/O ports and interface that the + matcd driver in FreeBSD expects. The only adapters that are supported + at this time are those that are 100% compatible with the Creative + Labs (SoundBlaster) host interface. See matcd.4 documentation for a + list of host adapters that are known to work. + + +Q: I'm trying to install from a tape drive but all I get is something like: + st0(aha0:1:0) NOT READY csi 40,0,0,0 + on the screen. Help! + +A: There's a limitation in the current sysinstall that the tape MUST + be in the drive while sysinstall is started or it won't be detected. + Try again with the tape in the drive the whole time. + + +Q: I've installed FreeBSD onto my system, but it hangs when booting from + the hard drive with the message: ``Changing root to /dev/sd0a''. + +A: This problem may occur in a system with a 3com 3c509 ethernet adaptor. + The ep0 device driver appears to be sensitive to probes for other + devices that also use address 0x300. Boot your FreeBSD system by power + cycling the machine (turn off and on). At the ``Boot:'' prompt specify + the ``-c''. This will invoke UserConfig (see Section 1. above). Use + the ``disable'' command to disable the device probes for all devices + at address 0x300 except the ep0 driver. On exit, your machine should + successfully boot FreeBSD. + + +Q: My system hangs during boot, right after the "fd0: [my floppy drive]" + line. + +A: This is not actually a hang, simply a very LONG "wdc0" probe that + often takes a long time to complete on certain systems (where there + usually _isn't_ a WD controller). Be patient, your system will boot! + To eliminate the problem, boot with the -c flag and eliminate the wdc0 + device, or compile a custom kernel. + +[ Please add more hardware tips to this Q&A section! ] diff --git a/release/sysinstall/help/en_US.ISO_8859-1/install.hlp b/release/sysinstall/help/en_US.ISO_8859-1/install.hlp new file mode 100644 index 0000000..945c81b --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/install.hlp @@ -0,0 +1,447 @@ + INSTALLATION GUIDE FOR FreeBSD 2.0.5 + +This manual documents the process of installing FreeBSD on your +machine. Please also see the Hardware Guide for hardware-specific +installation instructions (how to configure your hardware, what sorts +of things to watch out for, etc) before starting a new installation. + + +Table of Contents: +================== + +1.0 DOS User's Q&A section. + 1.1 How do I make space for FreeBSD? + 1.2 Can I use compressed DOS filesystems from FreeBSD? + 1.3 Can I use DOS extended partitions? + 1.4 Can I run DOS executables under FreeBSD? + +2.0 Preparing for the installation. + 2.1 Before installing from CDROM + 2.2 Before installing from Floppy + 2.3 Before installing from a DOS partition + 2.4 Before installing from QIC/SCSI tape + 2.5 Before installing over a network + 2.5.1 Preparing for NFS Installation + 2.5.2 Preparing for FTP Installation + +3.0 Installing FreeBSD. + + + +1.0 DOS user's Question and Answer section +=== ====================================== + +1.1 Help! I have no space! Do I need to delete everything first? + +If your machine is already running DOS and has little or no free space +available for FreeBSD's installation, all is not lost! You may find +the "FIPS" utility, provided in the tools/ subdirectory on the FreeBSD +CDROM or on the various FreeBSD ftp sites, to be quite useful. + +FIPS allows you to split an existing DOS partition into two pieces, +preserving the original partition and allowing you to install onto the +second free piece. You first "defrag" your DOS partition, using the +DOS 6.xx "DEFRAG" utility or the Norton Disk tools, then run FIPS. It +will prompt you for the rest of the information it needs. Afterwards, +you can reboot and install FreeBSD on the new free slice. See the +Distributions menu for an estimation of how much free space you'll +need for the kind of installation you want. + + +1.2 Can I use compressed DOS filesystems from FreeBSD? + +No. If you are using a utility such as Stacker(tm) or DoubleSpace(tm), +FreeBSD will only be able to use whatever portion of the filesystem +you leave uncompressed. The rest of the filesystem will show up as +one large file (the stacked/dblspaced file!). DO NOT REMOVE THAT +FILE! You will probably regret it greatly! + +It is probably better to create another uncompressed DOS primary +partition and use this for communications between DOS and FreeBSD. + + +1.3 Can I mount my DOS extended partitions? + +This feature isn't in FreeBSD 2.0.5 but should be in 2.1. We've laid +all the groundwork for making this happen, now we just need to do the +last 1% of the work involved. + + +1.4 Can I run DOS binaries under FreeBSD? + +Not yet! We'd like to add support for this someday, but are still +lacking anyone to actually do the work. Ongoing work with Linux's +DOSEMU utility may bring this much closer to being a reality sometime +soon. Send mail to hackers@freebsd.org if you're interested in +joining this effort! + +However, there is a neat utility called "pcemu" in the ports collection +which emulates an 8088 and enough BIOS services to run DOS text mode +applications. It requires the X Window System (provided as +XFree86 3.1.1u1). + + + +2.0 Preparing for the installation +=== ============================== + +2.1 Before installing from CDROM: + +If your CDROM is of an unsupported type, such as an IDE CDROM, then +please skip to section 2.3: Before installing from a DOS partition. + +There is not a lot of preparatory work that needs to be done to +successfully install from one of Walnut Creek's FreeBSD CDROMs (other +CDROM distributions may work as well, we simply cannot say as we +have no hand or say in their creation). You can either boot into the +CD installation directly from DOS using Walnut Creek's supplied +``install.bat'' batch file or you can make a boot floppy with +the ``makeflp.bat'' command. + +For the easiest interface of all (from DOS), type "go". This +will bring up a DOS menu utility that leads you through all +the available options. + +If you're creating the boot floppy from a UNIX machine, you may find +that ``dd if=floppies/boot.flp of=/dev/rfd0'' or +``dd if=floppies/boot.flp of=/dev/floppy'' works well, depending on +your hardware and operating system environment. + +Once you've booted from DOS or floppy, you should then be able to select +CDROM as the media type in the Media menu and load the entire +distribution from CDROM. No other types of installation media should +be required. + +After your system is fully installed and you have rebooted from the +hard disk, you should find the CD mounted on the directory /cdrom. A +utility called `lndir' comes with the XFree86 distribution which you +may also find useful: It allows you to create "link tree" directories +to things on Read-Only media like CDROM. One example might be +something like this: + + mkdir /usr/ports + lndir /cdrom/ports /usr/ports + +Which would allow you to then "cd /usr/ports; make" and get all the +sources from the CD, but yet create all the intermediate files in +/usr/ports, which is presumably on a more writable media! :-) + +SPECIAL NOTE: Before invoking the installation, be sure that the +CDROM is in the drive so that the "probe" can find it! +This is also true if you wish the CDROM to be added to the default +system configuration automatically during the install (whether or +not you actually use it as the installation media). This will be +fixed for 2.1, but for now this simple work-around will ensure that +your CDROM is detected properly. + +Finally, if you would like people to be able to FTP install +FreeBSD directly from the CDROM in your machine, you'll find +it quite easy. After the machine is fully installed, you simply +need to add the following line to the password file (using +the vipw command): + + ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent + +No further work is necessary. The other installers will now be able +to chose a Media type of FTP and type in: ftp://<your machine> +after picking "Other" in the ftp sites menu! + + +2.2 Before installing from Floppy: + +If you must install from floppy disks, either due to unsupported +hardware or just because you enjoy doing things the hard way, you must +first prepare some floppies for the install. + +The first floppy you'll need is ``floppies/root.flp'', which is +somewhat special in that it's not a DOS filesystem floppy at all, but +rather an "image" floppy (it's actually a gzip'd cpio file). You can +use the rawrite.exe program to do this under DOS, or ``dd'' to do it +on a UNIX Workstation (see notes in section 2.1 concerning the +``floppies/boot.flp'' image). Once this floppy is made, go on +to make the distribution set floppies: + +You will need, at minimum, as many 1.44MB or 1.2MB floppies as it takes +to hold all files in the bin (binary distribution) directory. THESE +floppies *must* be formatted using MS-DOS, using the FORMAT command in +MS-DOS or the File Manager format command in Microsoft Windows(tm). +Don't trust Factory Preformatted floppies! Format them again yourself, +just to make sure! + +Many problems reported by our users in the past have resulted from the +use of improperly formatted media, so we simply take special care to +mention it here! + +After you've DOS formatted the floppies, you'll need to copy the files +onto them. The distribution files are split into chunks conveniently +sized so that 5 of them will fit on a conventional 1.44MB floppy. Go +through all your floppies, packing as many files as will fit on each +one, until you've got all the distributions you want packed up in this +fashion. Each distribution should go into a subdirectory on the +floppy, e.g.: a:\bin\bin.aa, a:\bin\bin.ab, ... + +Once you come to the Media screen of the install, select +"Floppy" and you'll be prompted for the rest. + + +2.3 Before installing from a DOS partition: + +To prepare for installation from an MS-DOS partition you should +simply copy the files from the distribution into a directory called +"FREEBSD". For example, to do a minimal installation of FreeBSD from +DOS using files copied from the CDROM, you might do something like +this: + + C> MD C:\FREEBSD + C> XCOPY /S E:\DISTS\BIN C:\FREEBSD + C> XCOPY /S E:\FLOPPIES C:\FREEBSD + +Asssuming that `C:' was where you had free space and `E:' was where +your CD was mounted. Note that you need the FLOPPIES directory +because the `root.flp' image is automatically looked for there when +you're doing a DOS installation. + +For as many `DISTS' as you wish to install from DOS (and you have free +space for), install each one under `C:\FREEBSD' - the BIN dist is only +the minimal requirement. + + +2.4 Before installing from QIC/SCSI Tape: + +Installing from tape is probably the easiest method, short of an +on-line install using FTP or a CDROM install. The installation program +expects the files to be simply tar'ed onto the tape, so after getting +all of the files for distribution you're interested in, simply tar +them onto the tape with a command like: + + cd /freebsd/distdir + tar cvf /dev/rwt0 (or /dev/rst0) dist1 .. dist2 + +Make sure that the `floppies/' directory is one of the "dists" given +above, since the installation will look for `floppies/root.flp' on +the tape. + +When you go to do the installation, you should also make sure that you +leave enough room in some temporary directory (which you'll be allowed +to choose) to accommodate the FULL contents of the tape you've +created. Due to the non-random access nature of tapes, this method of +installation requires quite a bit of temporary storage! You should +expect to require as much temporary storage as you have stuff written +on tape. + +SPECIAL NOTE: When going to do the installation, the tape must be in +the drive *before* booting from the boot floppy. The installation +"probe" may otherwise fail to find it. + + +2.5 Before installing over a network: + +You can do network installations over 3 types of communications links: + + Serial port: SLIP / PPP + Parallel port: PLIP (laplink cable) + Ethernet: A standard ethernet controller (includes some PCMCIA). + +SLIP support is rather primitive, and limited primarily to hard-wired +links, such as a serial cable running between a laptop computer and +another computer. The link should be hard-wired as the SLIP +installation doesn't currently offer a dialing capability; that +facility is provided with the PPP utility, which should be used in +preference to SLIP whenever possible. + +If you're using a modem, then PPP is almost certainly your only +choice. Make sure that you have your service provider's information +handy as you'll need to know it fairly soon in the installation +process. You will need to know, at the minimum, your service +provider's IP address and possibly your own (though you can also leave +it blank and allow PPP to negotiate it with your ISP). You also need +to know how to use the various "AT commands" to dial the ISP with your +particular modem as the PPP dialer provides only a very simple +terminal emulator. + +If a hard-wired connection to another FreeBSD (2.0R or later) machine +is available, you might also consider installing over a "laplink" +parallel port cable. The data rate over the parallel port is much +higher than what is typically possible over a serial line (up to +50k/sec), thus resulting in a quicker installation. + +Finally, for the fastest possible network installation, an ethernet +adaptor is always a good choice! FreeBSD supports most common PC +ethernet cards, a table of supported cards (and their required +settings) is provided as part of the FreeBSD Hardware Guide - see the +Documentation menu on the boot floppy. If you are using one of the +supported PCMCIA ethernet cards, also be sure that it's plugged in +_before_ the laptop is powered on! FreeBSD does not, unfortunately, +currently support "hot insertion" of PCMCIA cards. + +You will also need to know your IP address on the network, the +"netmask" value for your address class, and the name of your machine. +Your system administrator can tell you which values to use for your +particular network setup. If you will be referring to other hosts by +name rather than IP address, you'll also need a name server and +possibly the address of a gateway (if you're using PPP, it's your +provider's IP address) to use in talking to it. If you do not know +the answers to all or most of these questions, then you should +really probably talk to your system administrator _first_ before +trying this type of installation! + +Once you have a network link of some sort working, the installation +can continue over NFS or FTP. + +2.5.1 Preparing for NFS installation: + + NFS installation is fairly straight-forward: Simply copy the + FreeBSD distribution files you want onto a server somewhere + and then point the NFS media selection at it. + + If this server supports only "privileged port" access (as is + generally the default for Sun workstations), you will need to set + this option in the Options menu before installation can proceed. + + If you have a poor quality ethernet card which suffers from very + slow transfer rates, you may also wish to toggle the appropriate + Options flag. + + In order for NFS installation to work, the server must support + "subdir mounts"; e.g., if your FreeBSD 2.0.5 distribution directory + lives on: ziggy:/usr/archive/stuff/FreeBSD + Then ziggy will have to allow the direct mounting of + /usr/archive/stuff/FreeBSD, not just /usr or /usr/archive/stuff. + + In FreeBSD's /etc/exports file, this is controlled by the + ``-alldirs'' option. Other NFS servers may have different + conventions. If you are getting `Permission Denied' messages + from the server then it's likely that you don't have this + enabled properly! + + +2.5.2 Preparing for FTP Installation + + FTP installation may be done from any mirror site containing a + reasonably up-to-date version of FreeBSD 2.0.5. A full menu of + reasonable choices from almost anywhere in the world is provided + by the FTP site menu. + + If you are installing from some other FTP site not listed in this + menu, or you are having troubles getting your name server configured + properly, you can also specify your own URL by selecting the ``Other'' + choice in that menu. A URL can also be a direct IP address, so + the following would work in the absence of a name server: + + ftp://192.216.222.4/pub/FreeBSD/2.0.5-RELEASE + + [Substitute "ALPHA" for "RELEASE" during the ALPHA test period!] + + If you are installing through a firewall then you should probably + select ``Passive mode'' ftp, which is the default. If you are + talking to a server which does not support passive mode for some + reason, see the Options menu to select Active mode transfers. + + +3. Installing FreeBSD +-- ------------------ + +Once you've taken note of the appropriate preinstallation steps, you +should be able to install FreeBSD without any further trouble. + +Should this not be true, then you may wish to go back and re-read the +relevant preparation section (section 2.x) for the installation media +type you're trying to use - perhaps there's a helpful hint there that +you missed the first time? If you're having hardware trouble, or +FreeBSD refuses to boot at all, read the Hardware Guide provided on +the boot floppy for a list of possible solutions. + +The FreeBSD boot floppy contains all the on-line documentation you +should need to be able to navigate through an installation and if it +doesn't then I'd like to know what you found most confusing! It is +the objective of the FreeBSD installation program (sysinstall) to be +self-documenting enough that painful "step-by-step" guides are no +longer necessary. It may take us a little while to reach that +objective, but that's the objective! + +Meanwhile, you may also find the following "typical installation sequence" +to be helpful: + +o Boot the boot floppy. After a boot sequence which can take + anywhere from from 30 seconds to 3 minutes, depending on your + hardware, you should be presented with a menu of initial + choices. If the floppy doesn't boot at all, or the boot + hangs at some stage, go read the Q&A section of the Hardware + Guide for possible causes. + +o Press F1. You should see some basic usage instructions on + the menu system and general navigation. If you haven't used this + menu system before then PLEASE read this thoroughly! + +o If English is not your native language, you may wish to proceed + directly to the Language option and set your preferred language. + This will bring up some of the documentation in that language + instead of english. + +o Select the Options item and set any special preferences you + may have. + +o Select Proceed, bringing you to the Installation Menu. + +Installation Menu: + +o You can do anything you like in this menu without altering + your system _except_ for "Commit", which will perform any + requests to alter your system you may have made. + + If you're confused at any point, the F1 key usually pulls + up the right information for the screen you're in. + + o The first step is generally `Partition', which allows + you to chose how your drives will be used for FreeBSD. + + o Next, with the `Label' editor, you can specify how the space + in any allocated FreeBSD partitions should be used by FreeBSD, + or where to mount a non-FreeBSD partition (such as DOS). + + o Next, the `Distributions' menu allows you to specify which + parts of FreeBSD you wish to load. A good choice is + "User" for a small system or "Developer" for someone + wanting a bit more out of FreeBSD. If none of the existing + collections sound applicable, select Custom. + + o Next, the `Media' menu allows you to specify what kind of + media you wish to install from. If a desired media choice is + found and configured automatically then this menu will simply + return, otherwise you'll be asked for additional details on + the media device type. + + o Finally, the Commit command will actually perform all the + actions at once (nothing has been written to your disk + so far, nor will it until you give the final confirmation). + All new or changed partition information will be written + out, file systems will be created and/or non-destructively + labelled (depending on how you set their newfs flags in the + Label editor) and all selected distributions will be + extracted. + + o The Configure menu choice allows you to furthur configure your + FreeBSD installation by giving you menu-driven access to + various system defaults. Some items, like networking, may + be especially important if you did a CDROM/Tape/Floppy + installation and have not yet configured your network + interfaces (assuming you have some). Properly configuring + your network here will allow FreeBSD to come up on the network + when you first reboot from the hard disk. + + o Exit returns you to the top menu. + + + At this point, you're generally done with the sysinstall utility and +can select the final `Quit'. If you're running it as an installer +(e.g., before the system is all the way up) then the system will now +reboot. If you selected the boot manager option, you will see a small +boot menu with an `F?' prompt. Press the function key for BSD (it +will be shown) and you should boot up into FreeBSD off the hard disk. + + If this fails to happen for some reason, see the Q & A section +of the Hardware Guide for possible clues! + + Jordan + +---- End of Installation Guide --- diff --git a/release/sysinstall/help/en_US.ISO_8859-1/language.hlp b/release/sysinstall/help/en_US.ISO_8859-1/language.hlp new file mode 100644 index 0000000..23f176b --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/language.hlp @@ -0,0 +1,14 @@ +Use this menu to select your preferred language. For now, this only +sets the default language in which various help files are displayed. + +In later releases this will also change the keyboard layout, screen +map, NLS settings (sysinstall itself will also use message catalogs so +that all menus are in the appropriate language) and implement other +I18N features to meet various standards. + +Until these improvements are made, you may find it easier to simply +edit the /etc/sysconfig file yourself once the system is fully +installed. There are a number of comments in that file that detail +just what should be changed, as well as a few examples of existing +non-english setups. + diff --git a/release/sysinstall/help/en_US.ISO_8859-1/media.hlp b/release/sysinstall/help/en_US.ISO_8859-1/media.hlp new file mode 100644 index 0000000..8b081bc --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/media.hlp @@ -0,0 +1,29 @@ +You can install from the following types of media: + + CDROM - requires one of the following supported CDROM drives: + + Sony CDU 31/33A + Matushita/Panasonic "Sound Blaster" CDROM. + Mitsumi FX-001{A-D} (older non-IDE drives). + SCSI - Any standard SCSI CDROM drive hooked to + a supported controller (see Hardware Guide). + + DOS - A DOS primary partition with the required FreeBSD + distribution files copied onto it (e.g. C:\FREEBSD\) + + FS - Assuming a disk or partition with an existing + FreeBSD file system and distribution set on it, + get the distribution files from there. + + Floppy - Get distribution files from one or more DOS formatted + floppies. + + FTP - Get the distribution files from an anonymous ftp server + (you will be presented with a list). + + NFS - Get the distribution files from an NFS server somewhere + (make sure that permissions on the server allow this!) + + Tape - Extract distribution files from tape into a temporary + directory and install from there. + diff --git a/release/sysinstall/help/en_US.ISO_8859-1/network_device.hlp b/release/sysinstall/help/en_US.ISO_8859-1/network_device.hlp new file mode 100644 index 0000000..95c42ae --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/network_device.hlp @@ -0,0 +1,54 @@ +You can do network installations over 3 types of communications links: + + Serial port: SLIP / PPP + Parallel port: PLIP (laplink cable) + Ethernet: A standard ethernet controller (includes some PCMCIA). + +SLIP support is rather primitive and limited primarily to hard-wired +links, such as a serial cable running between a laptop computer and +another PC. The link must be hard-wired as the SLIP installation +doesn't currently offer a dialing capability; that facility is provided +with the PPP utility, which should be used in preference to SLIP +whenever possible. When you choose a serial port device, you'll +be given the option later to edit the slattach command before it's +run on the serial line. It is expected that you'll run slattach +(or some equivalent) on the other end of the link at this time and +bring up the line. FreeBSD will then install itself over the link +at speeds of up to 115.2K/baud (the recommended speed for a hardwired +cable). + +If you're using a modem then PPP is almost certainly your only +choice. Make sure that you have your service provider's information +handy as you'll need to know it fairly early in the installation +process. You will need to know, at the minimum, your service +provider's IP address and possibly your own (though you can also leave +it blank and allow PPP to negotiate it with your ISP). You will also +need to know how to use the various "AT commands" to dial the ISP with +your particular brand of modem as the PPP dialer provides only a very +simple terminal emulator and has no "modem capabilities database". + +If a hard-wired connection to another FreeBSD (2.0R or later) machine +is available, you might also consider installing over a "laplink" +parallel port cable. The data rate over the parallel port is much +higher than what is typically possible over a serial line with +speeds of up to 50k/sec. + +Finally, for the fastest possible network installation, an ethernet +adaptor is always a good choice! FreeBSD supports most common PC +ethernet cards, a table of which is provided in the FreeBSD +Hardware Guide (see the Documentation menu on the boot floppy). +If you are using one of the supported PCMCIA ethernet cards, also be +sure that it's plugged in _before_ the laptop is powered on! FreeBSD +does not, unfortunately, currently support "hot insertion" of PCMCIA +cards. + +You will also need to know your IP address on the network, the "netmask" +value for your address class, and the name of your machine. +Your system administrator can tell you which values to use for your +particular network setup. If you will be referring to other hosts by +name rather than IP address, you'll also need a name server and +possibly the address of a gateway (if you're using PPP, it's your +provider's IP address) to use in talking to it. If you do not know +the answers to all or most of these questions, then you should +really probably talk to your system administrator _first_ before +trying this type of installation! diff --git a/release/sysinstall/help/en_US.ISO_8859-1/options.hlp b/release/sysinstall/help/en_US.ISO_8859-1/options.hlp new file mode 100644 index 0000000..c30180c --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/options.hlp @@ -0,0 +1,95 @@ +The following options may be set from this screen: + +NFS Secure: NFS server talks only on a secure port + + This is most commonly used when talking to Sun workstations, which + will not talk NFS over "non priviledged" ports. + + +NFS Slow: User is using a slow PC or ethernet card + + Use this option if you have a slow PC (386) or an ethernet card + with poor performance being "fed" by NFS on a higher-performance + workstation. This will throttle the workstation back to prevent + the PC from becoming swamped with data. + + +FTP Abort: On transfer failure, abort + + This is pretty self-explanatory. If you're transfering from a + host that drops the connection or cannot provide a file, abort + the installation of that piece. + + +FTP Reselect: On transfer failure, ask for another host + + This is more useful to someone doing an interactive installation. + If the current host stops working, ask for a new ftp server to + resume the installation from. The install will attempt to pick + up from where it left off on the other server, if at all possible. + + +FTP Active: Use "active mode" for standard FTP + + For all FTP transfers, use "Active" mode. This will not work + through firewalls, but will often work with older ftp servers + that do not support passive mode. If your connection hangs + with passive mode (the default), try active! + + +FTP Passive: Use "passive mode" for firewalled FTP + + For all FTP transfers, use "Passive" mode. This allows the user + to pass through firewalls that do not allow incoming connections + on random port addresses. + + NOTE: ACTIVE AND PASSIVE MODES ARE NOT THE SAME AS A `PROXY' + CONNECTION, WHERE A PROXY FTP SERVER IS LISTENING ON A DIFFERENT + PORT! + + In such situations, you should specify the URL as something like: + + ftp://foo.bar.com:1234/pub/FreeBSD + + Where "1234" is the port number of the proxy ftp server. + + +Debugging: Turn on the extra debugging flag + + This turns on a lot of extra noise over on the second screen + (ALT-F2 to see it, ALT-F1 to switch back). If your installation + should fail for any reason, PLEASE turn this flag on when + attempting to reproduce the problem. It will provide a lot of + extra debugging at the failure point and may be very helpful to + the developers in tracking such problems down! + + +Yes To All: Assume "Yes" answers to all non-critical dialogs + + This flag should be used with caution. It will essentially + decide NOT to ask the user about any "boundry" conditions that + might not constitute actual errors but may be warnings indicative + of other problems. + + +FTP userpass: Specify username and password instead of anonymous. + + By default, the installation attempts to log in as the + anonymous user. If you wish to log in as someone else, + specify the username and password with this option. + + +Clear: Clear All Option Flags + + Reset all option flags back to their default values. + +---- + +Some of these items, like "FTP Active" or "FTP Passive", are actually +mutually-exclusive even though you can turn all of them on or off at +once. This is a limitation of the menuing system, and is compensated +for by checks that ensure that the various flags are not in conflict. +If you re-enter the Options menu again after leaving it, you'll see +the settings it's actually using after checking for any possible +conflicts. + diff --git a/release/sysinstall/help/en_US.ISO_8859-1/partition.hlp b/release/sysinstall/help/en_US.ISO_8859-1/partition.hlp new file mode 100644 index 0000000..fd16a45 --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/partition.hlp @@ -0,0 +1,77 @@ +This is the FreeBSD DiskLabel Editor. + +If you're new to this installation, then you should first understand +how FreeBSD 2.0.5's new "slices" paradigm for looking at disk storage +works. It's not very hard to understand. A "fully qualified slice name", +that is the name of the file we open in /dev to talk to the slice, +is optionally broken into 3 parts: + + First you have the disk name. Assume we have two SCSI + drives in our system, which gives us `sd0' and `sd1'. + + Next you have the "Slice" (or "FDISK Partition") number, + as seen in the Partition Editor. Assume that our sd0 contains + two slices, a FreeBSD slice and a DOS slice. This gives us + sd0s1 and sd0s2. Let's also say that sd1 is completely devoted + to FreeBSD, so we have only one slice there: sd1s1. + + Next, if a slice is a FreeBSD slice, you have a number of + (confusingly named) "partitions" you can put inside of it. + These FreeBSD partitions are where various filesystems or swap + areas live, and using our hypothetical two-SCSI-disk machine + again, we might have something like the following layout on sd0: + + Name Mountpoint + ---- ---------- + sd0s1a / + sd0s1b <swap space> + sd0s1e /usr + + Because of historical convention, there is also a short-cut, + or "compatibility slice", that is maintained for easy access + to the first FreeBSD slice on a disk for those programs which + still don't know how to deal with the new slice scheme. + The compatibility slice names for our filesystem above would + look like: + + Name Mountpoint + ---- ---------- + sd0a / + sd0b <swap space> + sd0e /usr + + FreeBSD automatically maps the compatibility slice to the first + FreeBSD slice it finds (in this case, sd0s1). You may have multiple + FreeBSD slices on a drive, but only the first one may be the + compatibility slice! + + The compatibility slice will eventually be phased out, but + it is still important right now for several reasons: + + 1. Some programs, as mentioned before, still don't work + with the slice paradigm and need time to catch up. + + 2. The FreeBSD boot blocks are unable to look for + a root file system in anything but a compatibility + slice right now. This means that our root will always + show up on "sd0a" in the above scenario, even though + it really lives over on sd0s1a and would otherwise be + referred to by its full slice name. + +Once you understand all this, then the label editor becomes fairly +simple. You're either carving up the FreeBSD slices displayed at the +top of the screen into smaller pieces (displayed in the middle of the +screen) and then putting FreeBSD file systems on them, Or you're just +mounting existing partitions/slices into your filesystem hierarchy; +this editor lets you do both. Since a DOS partition is also just +another slice as far as FreeBSD is concerned, you can mount one into +in your filesystem hierarchy just as easily with this editor. For +FreeBSD partitions you can also toggle the "newfs" state so that +the partitions are either (re)created from scratch or simply checked +and mounted (the contents are preserved). + +When you're done, type `Q' to exit. + +No actual changes will be made to the disk until you (C)ommit from the +Install menu! You're working with what is essentially a copy of +the disk label(s), both here and in the FDISK Partition Editor. diff --git a/release/sysinstall/help/en_US.ISO_8859-1/slice.hlp b/release/sysinstall/help/en_US.ISO_8859-1/slice.hlp new file mode 100644 index 0000000..e055ca4 --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/slice.hlp @@ -0,0 +1,28 @@ +This is the Main Partition (or ``Slice'') Editor. + +Possible commands are printed at the bottom, and the Master Boot Record +contents are at the top. You can move up and down with the arrow keys +and can (C)reate a new partition whenever the "bar" is over a partition +whose type is set to "unused". + +The flags field has the following legend: + + '=' -- Partition is properly aligned. + '>' -- The partition doesn't end before cylinder 1024 + 'R' -- Has been marked as containing the root (/) filesystem + 'B' -- Partition employs BAD144 bad-spot handling + 'C' -- This is the FreeBSD 2.0-compatibility partition (default) + 'A' -- This partition is marked active. + +If you select a partition for Bad144 handling, it will be scanned +for bad blocks before any new filesystems are made on it. + +If no partition is marked Active, you will need to either install +a Boot Manager (the option for which will be presented later in the +installation) or set one Active before leaving this screen. + +To leave this screen, type `Q'. + +No actual changes will be made to the disk until you (C)ommit from the +Install menu! You're working with what is essentially a copy of +the disk label(s), both here and in the Label Editor. diff --git a/release/sysinstall/help/en_US.ISO_8859-1/tcp.hlp b/release/sysinstall/help/en_US.ISO_8859-1/tcp.hlp new file mode 100644 index 0000000..3ab5d7c --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/tcp.hlp @@ -0,0 +1,27 @@ +This screen allows you to set up your general network parameters +(hostname, domain name, DNS server, etc) as well as the settings for a +given interface (which was selected from the menu before this screen). + +You can move through the fields with the TAB, BACK-TAB and RETURN +keys. To edit a field, use DELETE or BACKSPACE. You may also use ^A +(control-A) to go to the beginning of the line, ^E (control-E) to go +to the end, ^F (control-F) to go forward a character, ^B (control-B) +to go backward one character, ^D (control-D) to delete the character +under the cursor and ^K (control-K) to delete to the end of the line. +Basically, the standard EMACS motion sequences. + +The ``Extra options to ifconfig'' is kind of special (read: a hack :-). + +You can use it for specifying the foreign side of a PLIP or SLIP line +(simply type the foreign address in) as well as selecting a given +"link" on an ethernet card that has more than one (e.g. AUI, 10BT, +10B2, etc). The following links are recognised: + + link0 - AUI * highest precedence + link1 - BNC + link2 - UTP * lowest precedence + +That is to say that you can enter one of "link0", "link1" or "link2" +into the `Extra options' field to select a different link. + +When you're done with this form, select OK. diff --git a/release/sysinstall/help/en_US.ISO_8859-1/usage.hlp b/release/sysinstall/help/en_US.ISO_8859-1/usage.hlp new file mode 100644 index 0000000..b01a94b --- /dev/null +++ b/release/sysinstall/help/en_US.ISO_8859-1/usage.hlp @@ -0,0 +1,54 @@ +HOW TO USE THIS SYSTEM +====================== + +KEY ACTION +--- ------ +UP ARROW Move to previous item (or up, in a text field). +DOWN ARROW Move to next item (or down, in a text field). +TAB Move to next item or group. +RIGHT ARROW Move to next item or group (same as TAB). +SHIFT-TAB Move to previous item or group. +LEFT ARROW Move to previous item or group (same as SHIFT-TAB). +RETURN Select item. +PAGE UP In text boxes, scrolls up one page. +PAGE DOWN In text boxes, scrolls down one page. +SPACE In "radio" or multiple choice menus, toggle the current item. +F1 Help (in screens that provide it). + +If you also see small "^(-)" or "v(+)" symbols at the edges of a menu, +it means that there are more items above or below the current one that +aren't being shown (due to insufficient screen space). Using the +up/down arrow keys will cause the menu to scroll. When a symbol +disappears, it means you are at the top (or bottom) of the menu. + +In text fields, the amount of text above the current point will be +displayed as a percentage in the lower right corner. 100% means +you're at the bottom of the field. + +Selecting OK in a menu will confirm whatever action it's controlling. +Selecting Cancel will cancel the operation and generally return you to +the previous menu. + + +SPECIAL FEATURES: +================= + +It is also possible to select a menu item by typing the first +character of its name, if unique. Such "accelerator" characters will +be specially highlighted in the item name. + +The console driver also contains a scroll-back buffer for reviewing +things that may have scrolled off the screen. To use scroll-back, +press the "Scroll Lock" key on your keyboard and use the arrow or +Page Up/Page Down keys to move through the saved text. To leave +scroll-back mode, press the Scroll Lock key again. This feature +is most useful for dealing with sub-shells or other "wizard modes" +that don't use menus. + +Once the system is fully installed and running "multi-user", you will +also find that you have multiple "virtual consoles" and can use them to +have several active sessions at once. Use ALT-F<n> to switch between +them, where `F<n>' is the function key corresponding to the screen you +wish to see. By default, the system comes with 3 virtual consoles enabled. +You can create more by editing the /etc/ttys file, once the system is up, +for a maximum of 12. diff --git a/release/sysinstall/help/es_ES.ISO8859-1/README b/release/sysinstall/help/es_ES.ISO8859-1/README new file mode 100644 index 0000000..27020bf --- /dev/null +++ b/release/sysinstall/help/es_ES.ISO8859-1/README @@ -0,0 +1,108 @@ + ------------------------------------------ + FreeBSD 2.0.5 --- Versión DEFINITIVA , , + ------------------------------------------ /( )` + \ \___ / | +¡Bienvenido a la versión 2.0.5 de FreeBSD! 2.0.5 es /- _ `-/ ' +una versión intermedia de FreeBSD que rellena el (/\/ \ \ /\ +hueco existente entre 2.0R (publicada en Noviembre / / | ` \ +de 1994) y 2.1R, que se publicará a finales de O O ) / | +Julio de 1995. FreeBSD 2.0.5 contiene gran `-^--'`< ' +cantidad de mejoras significativas respecto de (_.) _ ) / +2.0R, entre las que destacan una mayor estabilidad `.___/` / +(por un considerable margen), docenas de `-----' / +características nuevas y un programa <----. __ / __ \ +de instalación muy mejorado. Vea las <----|====O)))==) \) /==== +notas a la versión para más detalles <----' `--' `.__,' \ +sobre las novedades de FreeBSD 2.0.5. | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +¿Qué es FreeBSD? FreeBSD es un sistema operativo basado en 4.4 BSD Lite +para hardware PC basado en "x86" de Intel, AMD, Cyrix o NexGen. Funciona +con un abanico muy amplio de periféricos y configuraciones de PC y se +puede utilizar para todo tipo de actividades, desde el desarrollo de +software hasta la provisión de servicios de Internet; ¡el lugar más +concurrido de la Internet, ftp.cdrom.com, es una máquina con FreeBSD! + +Esta versión de FreeBSD contiene todo lo que necesita para montar +un sistema así, además del código fuente completo. Con la distribución +de las fuentes instalada, puede recompilar literalmente el sistema +entero desde cero con un solo comando, lo que lo hace ideal para +estudiantes, investigadores o quienes simplemente deseen ver cómo +funciona todo. + +También se proporciona una gran recopilación de software de terceros +adaptado (la "colección de adaptaciones") para facilitarle la +obtención e instalación de todas sus utilidades tradicionales de UNIX +favoritas bajo FreeBSD. Son más de 270 adaptaciones, que abarcan desde +editores hasta lenguajes de programación o aplicaciones gráficas, lo +cual hace de FreeBSD un potente y completo entorno de trabajo, capaz de +rivalizar en utilización general y potencia con el de muchas estaciones +de trabajo grandes. + + +Para obtener más documentación sobre este sistema, se recomienda que +adquiera el juego de publicaciones sobre 4.4BSD de O'Reilly Associates +y la asociación USENIX, ISBN 1-56592-082-1. No tenemos ninguna conexión +con O'Reilly, ¡simplemente somos consumidores satisfechos! + +Quizá también desee leer la GUIA DEL HARDWARE *antes* de avanzar más +con la instalación. La configuración del hardware del PC para algo que +no sea DOS/Windows (los cuales en realidad no exigen demasiado al +hardware) es realmente un poco más complicada de lo que parece, y si +cree que comprende los PC, está claro que aún no los ha utilizado +durante el tiempo suficiente. :) Esta guía le proporcionará algunos +consejos sobre cómo configurar el hardware, así como los síntomas que hay +que buscar en caso de problema. Esta guía está disponible en el menú +Documentación del disquete de arranque de FreeBSD. + +ADVERTENCIA: Aunque FreeBSD hace todo lo posible para prevenir la pérdida +accidental de datos, ¡sigue siendo más que posible BORRAR EL DISCO ENTERO +con esta instalación! Por favor, ¡no pase al menú final de la instalación +de FreeBSD hasta haber realizado primero una copia de seguridad adecuada +de todos los datos importantes! ¡Lo decimos en serio! + +Los comentarios técnicos sobre esta versión deben enviarse (en inglés) a: + + hackers@FreeBSD.org + + +Los informes sobre errores deben enviarse mediante el comando 'send-pr', +si fue posible instalar el sistema, o en otro caso a: + + bugs@FreeBSD.org + +Por favor, asegúrese de indicar QUE VERSION de FreeBSD utiliza en todos +los informes sobre errores. + + +Las preguntas generales deben enviarse a: + + questions@FreeBSD.org + +Por favor sea paciente si no se responde a sus preguntas de inmediato, +pues este es un momento especialmente atareado para nosotros y nuestros +recursos voluntarios a menudo están copados hasta el límite. Los informes +sobre errores enviados con el comando send-pr se registran y se siguen en +nuestra base de datos de errores y se le mantendrá informado sobre todos +los cambios en su estado durante la vida del error (o de la petición de +nuevas características). + +Nuestro nodo del WEB, http://www.freebsd.org, también es una fuente muy +buena de información actualizada y proporciona una serie de facilidades +avanzadas de documentación. Puede utilizar la versión de Netscape para +BSDI para ojear el World Wide Web directamente desde FreeBSD. + +Puede que también desee inspeccionar /usr/share/FAQ y /usr/share/doc para +más información sobre el sistema. + + +Gracias por leer todo esto; ¡esperamos sinceramente que disfrute esta +versión de FreeBSD! + + Jordan Hubbard, + para El Proyecto FreeBSD + diff --git a/release/sysinstall/help/es_ES.ISO8859-1/configure.hlp b/release/sysinstall/help/es_ES.ISO8859-1/configure.hlp new file mode 100644 index 0000000..608c691 --- /dev/null +++ b/release/sysinstall/help/es_ES.ISO8859-1/configure.hlp @@ -0,0 +1,18 @@ +Este menú le permite configurar un poco el sistema después de +haberlo instalado. Como mínimo, probablemente deberá establecer +la contraseña del administrador del sistema y el huso horario +del sistema. + +Para otras cosas extra como bash, emacs, pascal, etc. es muy +probable que también tenga que activar la opción Packages (Paquetes) +de este menú. Observe que actualmente esto sólo tiene alguna utilidad +si dispone de un CDROM o de una colección existente de paquetes en +algún lugar de la jerarquía del sistema de ficheros a donde pueda +acceder la herramienta de gestión de paquetes. La transferencia +automática de paquetes por FTP aún no está soportada. + +Si desea volver a invocar la herramienta de instalación de paquetes +después de salir de la instalación del sistema, el comando es +``pkg_manage''. Para establecer el huso horario, escriba ``tzsetup''. +Para más información sobre la configuración general del sistema, vea +el fichero ``/etc/sysconfig''. diff --git a/release/sysinstall/help/es_ES.ISO8859-1/language.hlp b/release/sysinstall/help/es_ES.ISO8859-1/language.hlp new file mode 100644 index 0000000..a76895b --- /dev/null +++ b/release/sysinstall/help/es_ES.ISO8859-1/language.hlp @@ -0,0 +1,15 @@ +Utilice este menú para seleccionar el idioma deseado. Por el momento, +esto únicamente sirve para establecer el idioma por defecto con que +se visualizan diversos ficheros de ayuda. + +En versiones posteriores también cambiará la disposición del teclado, +el mapa de pantalla, los ajustes de NLS (el propio sysinstall usará +catálogos de mensajes, de forma que todos los menús estén en el +idioma adecuado) e implementará otras características I18N para +ajustarse a diversos estándares. + +Hasta que se efectúen dichas mejoras, puede que encuentre más sencillo +editar por su cuenta el fichero /etc/sysconfig una vez que el sistema +esté totalmente instalado. Hay un buen número de comentarios en ese +fichero que detallan lo que debería cambiarse, así como unos pocos +ejemplos de configuraciones no inglesas. diff --git a/release/sysinstall/help/es_ES.ISO8859-1/usage.hlp b/release/sysinstall/help/es_ES.ISO8859-1/usage.hlp new file mode 100644 index 0000000..762c358 --- /dev/null +++ b/release/sysinstall/help/es_ES.ISO8859-1/usage.hlp @@ -0,0 +1,57 @@ +COMO USAR ESTE SISTEMA +====================== + +TECLA ACCIO'N +----- ------- +FLECHA ARRIBA Ir al elemento anterior (o superior, en un campo de texto). +FLECHA ABAJO Ir al elemento siguiente (o inferior, en un campo de texto). +TAB Ir al siguiente elemento o grupo. +FLECHA DERECHA Ir al siguiente elemento o grupo (Ide'ntico a TAB). +MAYUSCULAS-TAB Ir al elemento anterior o grupo. +FLECHA IZQ. Ir al elemento anterior o grupo (Ide'ntico a MAYUSCULAS-TAB). +RETORNO Seleccionar el elemento. +PAGINA ARRIBA Regresa una pa'gina, en a'reas de texto. +PAGINA ABAJO Presenta la siguiente pa'gina, en areas de texto. +ESPACIO En menus de opcio'n mu'ltiple (radio), cambia el elemento actual +F1 Ayuda (en pantallas que la tengan disponible). + +En caso de que vea pequen~os si'mbolos "^(-)" o "v(+)" al margen de un menu', +significa que hay ma's elementos arriba o abajo del elemento actual, los +cuales no se presentan actualmente (debido a falta de espacio en la pantalla). +El menu' se puede recorrer haciendo uso de las flechas arriba/abajo. Cuando +el si'mbolo desaparezca, significa que ha llegado al inicio (o final) del +menu'. + +En campos de texto, la cantidad de texto arriba de su posicio'n en el mensaje +sera' mostrada como un porcentaje en la esquina inferior izquierda. 100% +significa que esta' al final del campo. + +Al seleccionar OK en un menu', confirmara' cualquier accio'n que e'ste +controle. El seleccionar Cancel interrumpira' la operacio'n, y generalmente +le regresara' al menu' anterior. + + +CARACTERI'STICAS ESPECIALES: +============================ + +Es posible tambie'n seleccionar un elemento del menu' oprimiendo el primer +caracter de su nombre, si e'ste es u'nico. Dichos caracteres "aceleradores" +estara'n remarcados especialmente en el nombre del elemento. + +El manejador de la consola tambie'n contiene una memoria de retorno, que le +permitira' regresar y revisar cosas que ya hayan salido de la pantalla. +Para usar el retorno, oprima la tecla "Bloqueo Despliegue" en su teclado, +y use las flechas o las teclas "Pa'gina anterior/Pa'gina siguiente" para +moverse a trave's del texto grabado. Para abandonar el modo de retorno, +oprima la tecla "Bloqueo Despliegue" nuevamente. Esta caracteri'stica es +muy u'til cuando se trabaja con sub-inte'rpretes de comandos, y otros +modos para usuarios avanzados o "magos" que no usan menu'es. + +Una vez que el sistema este' completamente instalado y funcionando en modo +"multi-usuario", encontrara' que tiene varias "consolas virtuales" y puede +utilizarlas para tener varias sesiones activas al mismo tiempo. Use la +combinacio'n ALT-F<n> para cambiar la sesio'n activa, 'F<n>' es la tecla +de funcio'n que corresponde a la pantalla que desee ver. El sistema viene +normalmente con 3 consolas virtuales habilitadas. Puede crear ma's editando +el archivo /etc/ttys una vez que el sistema este instalado, hasta un ma'ximo +de 12. diff --git a/release/sysinstall/help/es_ES.ISO_8859-1/README b/release/sysinstall/help/es_ES.ISO_8859-1/README new file mode 100644 index 0000000..27020bf --- /dev/null +++ b/release/sysinstall/help/es_ES.ISO_8859-1/README @@ -0,0 +1,108 @@ + ------------------------------------------ + FreeBSD 2.0.5 --- Versión DEFINITIVA , , + ------------------------------------------ /( )` + \ \___ / | +¡Bienvenido a la versión 2.0.5 de FreeBSD! 2.0.5 es /- _ `-/ ' +una versión intermedia de FreeBSD que rellena el (/\/ \ \ /\ +hueco existente entre 2.0R (publicada en Noviembre / / | ` \ +de 1994) y 2.1R, que se publicará a finales de O O ) / | +Julio de 1995. FreeBSD 2.0.5 contiene gran `-^--'`< ' +cantidad de mejoras significativas respecto de (_.) _ ) / +2.0R, entre las que destacan una mayor estabilidad `.___/` / +(por un considerable margen), docenas de `-----' / +características nuevas y un programa <----. __ / __ \ +de instalación muy mejorado. Vea las <----|====O)))==) \) /==== +notas a la versión para más detalles <----' `--' `.__,' \ +sobre las novedades de FreeBSD 2.0.5. | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +¿Qué es FreeBSD? FreeBSD es un sistema operativo basado en 4.4 BSD Lite +para hardware PC basado en "x86" de Intel, AMD, Cyrix o NexGen. Funciona +con un abanico muy amplio de periféricos y configuraciones de PC y se +puede utilizar para todo tipo de actividades, desde el desarrollo de +software hasta la provisión de servicios de Internet; ¡el lugar más +concurrido de la Internet, ftp.cdrom.com, es una máquina con FreeBSD! + +Esta versión de FreeBSD contiene todo lo que necesita para montar +un sistema así, además del código fuente completo. Con la distribución +de las fuentes instalada, puede recompilar literalmente el sistema +entero desde cero con un solo comando, lo que lo hace ideal para +estudiantes, investigadores o quienes simplemente deseen ver cómo +funciona todo. + +También se proporciona una gran recopilación de software de terceros +adaptado (la "colección de adaptaciones") para facilitarle la +obtención e instalación de todas sus utilidades tradicionales de UNIX +favoritas bajo FreeBSD. Son más de 270 adaptaciones, que abarcan desde +editores hasta lenguajes de programación o aplicaciones gráficas, lo +cual hace de FreeBSD un potente y completo entorno de trabajo, capaz de +rivalizar en utilización general y potencia con el de muchas estaciones +de trabajo grandes. + + +Para obtener más documentación sobre este sistema, se recomienda que +adquiera el juego de publicaciones sobre 4.4BSD de O'Reilly Associates +y la asociación USENIX, ISBN 1-56592-082-1. No tenemos ninguna conexión +con O'Reilly, ¡simplemente somos consumidores satisfechos! + +Quizá también desee leer la GUIA DEL HARDWARE *antes* de avanzar más +con la instalación. La configuración del hardware del PC para algo que +no sea DOS/Windows (los cuales en realidad no exigen demasiado al +hardware) es realmente un poco más complicada de lo que parece, y si +cree que comprende los PC, está claro que aún no los ha utilizado +durante el tiempo suficiente. :) Esta guía le proporcionará algunos +consejos sobre cómo configurar el hardware, así como los síntomas que hay +que buscar en caso de problema. Esta guía está disponible en el menú +Documentación del disquete de arranque de FreeBSD. + +ADVERTENCIA: Aunque FreeBSD hace todo lo posible para prevenir la pérdida +accidental de datos, ¡sigue siendo más que posible BORRAR EL DISCO ENTERO +con esta instalación! Por favor, ¡no pase al menú final de la instalación +de FreeBSD hasta haber realizado primero una copia de seguridad adecuada +de todos los datos importantes! ¡Lo decimos en serio! + +Los comentarios técnicos sobre esta versión deben enviarse (en inglés) a: + + hackers@FreeBSD.org + + +Los informes sobre errores deben enviarse mediante el comando 'send-pr', +si fue posible instalar el sistema, o en otro caso a: + + bugs@FreeBSD.org + +Por favor, asegúrese de indicar QUE VERSION de FreeBSD utiliza en todos +los informes sobre errores. + + +Las preguntas generales deben enviarse a: + + questions@FreeBSD.org + +Por favor sea paciente si no se responde a sus preguntas de inmediato, +pues este es un momento especialmente atareado para nosotros y nuestros +recursos voluntarios a menudo están copados hasta el límite. Los informes +sobre errores enviados con el comando send-pr se registran y se siguen en +nuestra base de datos de errores y se le mantendrá informado sobre todos +los cambios en su estado durante la vida del error (o de la petición de +nuevas características). + +Nuestro nodo del WEB, http://www.freebsd.org, también es una fuente muy +buena de información actualizada y proporciona una serie de facilidades +avanzadas de documentación. Puede utilizar la versión de Netscape para +BSDI para ojear el World Wide Web directamente desde FreeBSD. + +Puede que también desee inspeccionar /usr/share/FAQ y /usr/share/doc para +más información sobre el sistema. + + +Gracias por leer todo esto; ¡esperamos sinceramente que disfrute esta +versión de FreeBSD! + + Jordan Hubbard, + para El Proyecto FreeBSD + diff --git a/release/sysinstall/help/es_ES.ISO_8859-1/configure.hlp b/release/sysinstall/help/es_ES.ISO_8859-1/configure.hlp new file mode 100644 index 0000000..608c691 --- /dev/null +++ b/release/sysinstall/help/es_ES.ISO_8859-1/configure.hlp @@ -0,0 +1,18 @@ +Este menú le permite configurar un poco el sistema después de +haberlo instalado. Como mínimo, probablemente deberá establecer +la contraseña del administrador del sistema y el huso horario +del sistema. + +Para otras cosas extra como bash, emacs, pascal, etc. es muy +probable que también tenga que activar la opción Packages (Paquetes) +de este menú. Observe que actualmente esto sólo tiene alguna utilidad +si dispone de un CDROM o de una colección existente de paquetes en +algún lugar de la jerarquía del sistema de ficheros a donde pueda +acceder la herramienta de gestión de paquetes. La transferencia +automática de paquetes por FTP aún no está soportada. + +Si desea volver a invocar la herramienta de instalación de paquetes +después de salir de la instalación del sistema, el comando es +``pkg_manage''. Para establecer el huso horario, escriba ``tzsetup''. +Para más información sobre la configuración general del sistema, vea +el fichero ``/etc/sysconfig''. diff --git a/release/sysinstall/help/es_ES.ISO_8859-1/language.hlp b/release/sysinstall/help/es_ES.ISO_8859-1/language.hlp new file mode 100644 index 0000000..a76895b --- /dev/null +++ b/release/sysinstall/help/es_ES.ISO_8859-1/language.hlp @@ -0,0 +1,15 @@ +Utilice este menú para seleccionar el idioma deseado. Por el momento, +esto únicamente sirve para establecer el idioma por defecto con que +se visualizan diversos ficheros de ayuda. + +En versiones posteriores también cambiará la disposición del teclado, +el mapa de pantalla, los ajustes de NLS (el propio sysinstall usará +catálogos de mensajes, de forma que todos los menús estén en el +idioma adecuado) e implementará otras características I18N para +ajustarse a diversos estándares. + +Hasta que se efectúen dichas mejoras, puede que encuentre más sencillo +editar por su cuenta el fichero /etc/sysconfig una vez que el sistema +esté totalmente instalado. Hay un buen número de comentarios en ese +fichero que detallan lo que debería cambiarse, así como unos pocos +ejemplos de configuraciones no inglesas. diff --git a/release/sysinstall/help/es_ES.ISO_8859-1/usage.hlp b/release/sysinstall/help/es_ES.ISO_8859-1/usage.hlp new file mode 100644 index 0000000..762c358 --- /dev/null +++ b/release/sysinstall/help/es_ES.ISO_8859-1/usage.hlp @@ -0,0 +1,57 @@ +COMO USAR ESTE SISTEMA +====================== + +TECLA ACCIO'N +----- ------- +FLECHA ARRIBA Ir al elemento anterior (o superior, en un campo de texto). +FLECHA ABAJO Ir al elemento siguiente (o inferior, en un campo de texto). +TAB Ir al siguiente elemento o grupo. +FLECHA DERECHA Ir al siguiente elemento o grupo (Ide'ntico a TAB). +MAYUSCULAS-TAB Ir al elemento anterior o grupo. +FLECHA IZQ. Ir al elemento anterior o grupo (Ide'ntico a MAYUSCULAS-TAB). +RETORNO Seleccionar el elemento. +PAGINA ARRIBA Regresa una pa'gina, en a'reas de texto. +PAGINA ABAJO Presenta la siguiente pa'gina, en areas de texto. +ESPACIO En menus de opcio'n mu'ltiple (radio), cambia el elemento actual +F1 Ayuda (en pantallas que la tengan disponible). + +En caso de que vea pequen~os si'mbolos "^(-)" o "v(+)" al margen de un menu', +significa que hay ma's elementos arriba o abajo del elemento actual, los +cuales no se presentan actualmente (debido a falta de espacio en la pantalla). +El menu' se puede recorrer haciendo uso de las flechas arriba/abajo. Cuando +el si'mbolo desaparezca, significa que ha llegado al inicio (o final) del +menu'. + +En campos de texto, la cantidad de texto arriba de su posicio'n en el mensaje +sera' mostrada como un porcentaje en la esquina inferior izquierda. 100% +significa que esta' al final del campo. + +Al seleccionar OK en un menu', confirmara' cualquier accio'n que e'ste +controle. El seleccionar Cancel interrumpira' la operacio'n, y generalmente +le regresara' al menu' anterior. + + +CARACTERI'STICAS ESPECIALES: +============================ + +Es posible tambie'n seleccionar un elemento del menu' oprimiendo el primer +caracter de su nombre, si e'ste es u'nico. Dichos caracteres "aceleradores" +estara'n remarcados especialmente en el nombre del elemento. + +El manejador de la consola tambie'n contiene una memoria de retorno, que le +permitira' regresar y revisar cosas que ya hayan salido de la pantalla. +Para usar el retorno, oprima la tecla "Bloqueo Despliegue" en su teclado, +y use las flechas o las teclas "Pa'gina anterior/Pa'gina siguiente" para +moverse a trave's del texto grabado. Para abandonar el modo de retorno, +oprima la tecla "Bloqueo Despliegue" nuevamente. Esta caracteri'stica es +muy u'til cuando se trabaja con sub-inte'rpretes de comandos, y otros +modos para usuarios avanzados o "magos" que no usan menu'es. + +Una vez que el sistema este' completamente instalado y funcionando en modo +"multi-usuario", encontrara' que tiene varias "consolas virtuales" y puede +utilizarlas para tener varias sesiones activas al mismo tiempo. Use la +combinacio'n ALT-F<n> para cambiar la sesio'n activa, 'F<n>' es la tecla +de funcio'n que corresponde a la pantalla que desee ver. El sistema viene +normalmente con 3 consolas virtuales habilitadas. Puede crear ma's editando +el archivo /etc/ttys una vez que el sistema este instalado, hasta un ma'ximo +de 12. diff --git a/release/sysinstall/help/fr_FR.ISO8859-1/README b/release/sysinstall/help/fr_FR.ISO8859-1/README new file mode 100644 index 0000000..13ef060 --- /dev/null +++ b/release/sysinstall/help/fr_FR.ISO8859-1/README @@ -0,0 +1,104 @@ + ----------------------------------------- + FreeBSD version 2.0.5 , , + ----------------------------------------- /( )` + \ \___ / | + /- _ `-/ ' +Bienvenue dans FreeBSD, version 2.0.5 ! C'est une (/\/ \ \ /\ +version intermédiaire après une longue période / / | ` \ +nécessaire depuis la version 2.0 de Novembre 94 O O ) / | +et en attendant la version 2.1 prévue pour fin `-^--'`< ' +Juillet 95. FreeBSD 2.0.5 constitue une nette (_.) _ ) / +amélioration depuis la version 2.0 : un effort `.___/` / +considérable du point de vue de la stabilité ainsi `-----' / +que des nouveautés par douzaines. Pour <----. __ / __ \ +obtenir plus de détails concernant ces <----|====O)))==) \) /==== +nouveautés, consultez le fichier <----' `--' `.__,' \ +RELNOTES | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + +FreeBSD est un système d'exploitation basé sur 4.4 BSD Lite, pour les +PC munis de processeurs de type "x86" d'Intel, AMD, Cyrix ou NexGen. +FreeBSD supporte une très large quantité de périphériques et de +configurations. Il est utilisé pour de multiples tâches, allant du +développement logiciel jusqu'à l'accès aux services d'Internet. Le +site le plus utilisé sur Internet, ftp.cdrom.com, est une machine +FreeBSD ! + +Cette version de FreeBSD contient tout ce dont vous pouvez avoir +besoin pour implanter ce système sur votre machine. Les sources de +tous les programmes étant fournis, vous pouvez recompiler à loisir la +distribution complète en une unique commande. C'est idéal pour les +étudiants, les chercheurs et tous ceux qui sont simplement curieux de +voir comment est conçu un tel système. + +Une importante collection de logiciels supportés (les « ports ») est +aussi fournie pour vous aider à obtenir et à installer sur FreeBSD, +les logiciels traditionnels du domaine UNIX. Plus de 270 ports sont +ainsi disponibles, des éditeurs de texte aux langages de programmation, +en passant par les applications graphiques... Tout cela contribue à +faire autour de FreeBSD, un environnement puissant et accessible, +capable de rivaliser avec beaucoup de stations de travail. + +En complément, il est recommandé d'acquérir les ouvrages relatifs à +4.4BSD, chez « O'Reilly Associates » et « USENIX Association », +ISBN 1-56592-082-1. Nous n'avons pas d'intérêts dans la vente de ces +ouvrages, nous sommes simplement des lecteurs satisfaits. + +Il est conseillé de lire le guide des configurations matérielles avant +d'aller plus loin dans l'installation. La configuration d'un PC pour +d'autres systèmes que DOS/Windows (qui n'est pas très exigeant sur ce +point) est certainement un peu plus difficile qu'il n'y paraît, et si +vous pensez maîtriser la situation, c'est sans doute que vous n'avez +pas utilisé un PC depuis quelque temps. :) Ce guide donne les +renseignements indiquant comment configurer votre machine et quels +symptômes rechercher en cas de problème. Ce guide est disponible par +le menu Documentation de la disquette de démarrage de FreeBSD. + +MISE EN GARDE : Malgré toutes les précautions, FreeBSD ne peut +garantir contre une perte accidentelle des données. Il se peut que +cette procédure d'installation efface complètement le contenu de votre +disque dur. Il est donc fortement conseillé de faire une sauvegarde de +votre disque avant de continuer cette installation. + +Les commentaires techniques à propos de cette version peuvent être +adressés à : + + hackers@FreeBSD.org (en anglais) + +Les rapports de dysfonctionnement « bug reports » peuvent être +notifiés par la commande « send-pr » dès que votre système est +installé. Dans le cas contraire, ils peuvent être adressés à : + + bugs@FreeBSD.org (en anglais) + +N'oubliez par de joindre à votre requête, le numéro de la version de +FreeBSD concernée. + +Les questions d'ordre général sont à diriger vers : + + questions@FreeBSD.org (en anglais) + +Ne soyez pas impatient si vos questions ne trouvent pas réponse dans +la minute, car c'est beaucoup d'investissement que d'y répondre et il +n'est pas rare que toute notre bonne volonté ne suffise pas. Les +problèmes soumis par le biais de la commande « send-pr » sont +automatiquement répertoriés dans une base de données. Vous resterez +informés de toute évolution concernant votre demande. + +Notre site WEB est http://www.freebsd.org. C'est aussi une bonne +source pour obtenir les dernières informations en date. Ce site +propose de nombreuses facilités de documentation. La version de +Netscape compilée pour BSDI peut être utilisée pour découvrir le +« World Wide Web » directement à partir de FreeBSD. + +Pour de plus amples détails, consultez les fichiers contenus dans les +répertoires /usr/share/FAQ et /usr/share/doc. + +Merci de votre attention, nous espérons sincèrement que cette version +de FreeBSD vous donnera entière satisfaction. + + Jordan Hubbard, + pour le projet FreeBSD diff --git a/release/sysinstall/help/fr_FR.ISO8859-1/configure.hlp b/release/sysinstall/help/fr_FR.ISO8859-1/configure.hlp new file mode 100644 index 0000000..4f3ed97 --- /dev/null +++ b/release/sysinstall/help/fr_FR.ISO8859-1/configure.hlp @@ -0,0 +1,16 @@ +Ce menu permet de configurer votre système dès la fin de son +installation. Le minimum conseillé est d'ajouter un mot de passe pour +l'administrateur du système, et d'indiquer le fuseau horaire de votre +localisation. + +Pour installer des utilitaires supplémentaires, tels que bash, emacs, +pascal, etc., vous pouvez utiliser l'entrée « Packages » dans ce +menu. L'obtention automatique de ces outils via FTP n'étant pas encore +disponible, une installation à partir du disque ou du CDROM est +nécessaire. + +Une installation ultérieure de ces outils sera toujours possible, à +l'aide de la commande « pkg_manage ». Un ajustement de l'heure peut +aussi être effectué grâce à « tzsetup ». Enfin, pour modifier la +configuration générale de votre système, reportez vous au contenu du +fichier /etc/sysconfig. diff --git a/release/sysinstall/help/fr_FR.ISO8859-1/language.hlp b/release/sysinstall/help/fr_FR.ISO8859-1/language.hlp new file mode 100644 index 0000000..f4a99ea --- /dev/null +++ b/release/sysinstall/help/fr_FR.ISO8859-1/language.hlp @@ -0,0 +1,13 @@ +Ce menu permet de choisir parmi plusieurs, le langage que vous +préférez. Pour l'instant cela n'est utilisé que dans certains fichiers +d'aide. + +Les versions suivantes permettront d'adapter le clavier, les codes +écran, la configuration NLS (le programme « sysinstall » utilisera +alors des menus en conséquence), et d'autres caractéristiques suivant +votre choix. + +En attendant, la méthode la plus simple consiste à éditer le fichier +/etc/sysconfig dès la fin de l'installation. Les nombreux commentaires +de ce fichier indiquent comment obtenir une configuration personnelle +et proposent quelques exemples. diff --git a/release/sysinstall/help/fr_FR.ISO8859-1/usage.hlp b/release/sysinstall/help/fr_FR.ISO8859-1/usage.hlp new file mode 100644 index 0000000..dd1d41a --- /dev/null +++ b/release/sysinstall/help/fr_FR.ISO8859-1/usage.hlp @@ -0,0 +1,54 @@ +COMMENT UTILISER CE SYSTÈME DE MENUS +==================================== + +TOUCHE ACTION +------ ------ +FLÈCHE HAUT Aller sur la rubrique précédente (ou remonter, dans du texte). +FLÈCHE BAS Aller sur la rubrique suivante (ou descendre, dans du texte). +TAB Aller sur la rubrique ou le groupe suivant. +FLÈCHE DROITE Aller sur la rubrique suivante. (même chose que TAB). +MAJ-TAB Aller sur la rubrique ou le groupe précédent. +FLÈCHE GAUCHE Aller sur la rubrique précédente. (même chose que MAJ-TAB). +ENTRÉE Sélectionne la rubrique. +PAGE PRÉC. Remonte d'une page, dans les boîtes de texte. +PAGE SUIV. Descend d'une page, dans les boîtes de texte. +ESPACE Sélectionne/désélectionne l'élément (menus à choix multiples). +F1 Aide (pour les écrans qui en proposent). + +De même, des symboles du genre "^(-)" ou "v(+)" sur les côtés d'un menu, +indiquent d'autres rubriques non affichées (par manque de place) plus haut ou +plus bas (respectivement). Les flèches haut ou bas feront défiler le menu et +feront apparaître les autres rubriques. Le symbole disparaît dès que le début +(ou la fin) du menu est atteint. + +Dans les boîtes de texte, le pourcentage de texte déjà affiché est indiqué +dans le coin inférieur droit. 100% veut dire qu'il n'y a plus rien à afficher. + +Sélectionner OK dans un menu pour confirmer votre choix. +Sélectionner Cancel pour annuler l'opération et revenir au menu précédent. + + +PARTICULARITÉS. +=============== + +On peut aussi choisir une rubrique dans un menu en tapant la première lettre +de son nom, si il n'y pas d'ambiguïté. Ces lettres "accélératrices" +apparaîtront en sur-brillance dans le nom de la rubrique. + +Il est aussi possible de remonter et revoir du texte qui a déjà défilé. Pour +cela, appuyez sur la touche "arrêt défil" ("Scroll Lock" en anglais) puis +utilisez la flèche-haut ou les touches Page Préc./Page Suiv. pour faire +défiler le texte. Pour quitter ce mode, appuyez à nouveau sur la touche +"arrêt défil.". Cette particularité est utile lorsque l'on est dans un +sous-shell ou dans un mode qui ne présente pas de menu. + +Dès que le système est complètement installé et fonctionne en mode +"multi-utilisateurs", il est possible d'utiliser des "écrans virtuels" +et d'avoir une session dans chacun d'eux. Il suffit d'utiliser +la combinaison de touches ALT-F<n> pour passer de l'un à l'autre : +ALT-F1 pour aller sur la session "1", ALT-F2 pour la session "2", etc. +3 écrans virtuels sont disponibles par défaut mais il est possible d'en +ajouter d'autres en éditant le fichier /etc/ttys (la limite supérieure est +fixée à 12) +Les utilisateurs de X11 pourront noter que ces écrans sont toujours +disponibles depuis X mais par les combinaisons CTRL-ALT-F<n>. diff --git a/release/sysinstall/help/fr_FR.ISO_8859-1/README b/release/sysinstall/help/fr_FR.ISO_8859-1/README new file mode 100644 index 0000000..13ef060 --- /dev/null +++ b/release/sysinstall/help/fr_FR.ISO_8859-1/README @@ -0,0 +1,104 @@ + ----------------------------------------- + FreeBSD version 2.0.5 , , + ----------------------------------------- /( )` + \ \___ / | + /- _ `-/ ' +Bienvenue dans FreeBSD, version 2.0.5 ! C'est une (/\/ \ \ /\ +version intermédiaire après une longue période / / | ` \ +nécessaire depuis la version 2.0 de Novembre 94 O O ) / | +et en attendant la version 2.1 prévue pour fin `-^--'`< ' +Juillet 95. FreeBSD 2.0.5 constitue une nette (_.) _ ) / +amélioration depuis la version 2.0 : un effort `.___/` / +considérable du point de vue de la stabilité ainsi `-----' / +que des nouveautés par douzaines. Pour <----. __ / __ \ +obtenir plus de détails concernant ces <----|====O)))==) \) /==== +nouveautés, consultez le fichier <----' `--' `.__,' \ +RELNOTES | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + +FreeBSD est un système d'exploitation basé sur 4.4 BSD Lite, pour les +PC munis de processeurs de type "x86" d'Intel, AMD, Cyrix ou NexGen. +FreeBSD supporte une très large quantité de périphériques et de +configurations. Il est utilisé pour de multiples tâches, allant du +développement logiciel jusqu'à l'accès aux services d'Internet. Le +site le plus utilisé sur Internet, ftp.cdrom.com, est une machine +FreeBSD ! + +Cette version de FreeBSD contient tout ce dont vous pouvez avoir +besoin pour implanter ce système sur votre machine. Les sources de +tous les programmes étant fournis, vous pouvez recompiler à loisir la +distribution complète en une unique commande. C'est idéal pour les +étudiants, les chercheurs et tous ceux qui sont simplement curieux de +voir comment est conçu un tel système. + +Une importante collection de logiciels supportés (les « ports ») est +aussi fournie pour vous aider à obtenir et à installer sur FreeBSD, +les logiciels traditionnels du domaine UNIX. Plus de 270 ports sont +ainsi disponibles, des éditeurs de texte aux langages de programmation, +en passant par les applications graphiques... Tout cela contribue à +faire autour de FreeBSD, un environnement puissant et accessible, +capable de rivaliser avec beaucoup de stations de travail. + +En complément, il est recommandé d'acquérir les ouvrages relatifs à +4.4BSD, chez « O'Reilly Associates » et « USENIX Association », +ISBN 1-56592-082-1. Nous n'avons pas d'intérêts dans la vente de ces +ouvrages, nous sommes simplement des lecteurs satisfaits. + +Il est conseillé de lire le guide des configurations matérielles avant +d'aller plus loin dans l'installation. La configuration d'un PC pour +d'autres systèmes que DOS/Windows (qui n'est pas très exigeant sur ce +point) est certainement un peu plus difficile qu'il n'y paraît, et si +vous pensez maîtriser la situation, c'est sans doute que vous n'avez +pas utilisé un PC depuis quelque temps. :) Ce guide donne les +renseignements indiquant comment configurer votre machine et quels +symptômes rechercher en cas de problème. Ce guide est disponible par +le menu Documentation de la disquette de démarrage de FreeBSD. + +MISE EN GARDE : Malgré toutes les précautions, FreeBSD ne peut +garantir contre une perte accidentelle des données. Il se peut que +cette procédure d'installation efface complètement le contenu de votre +disque dur. Il est donc fortement conseillé de faire une sauvegarde de +votre disque avant de continuer cette installation. + +Les commentaires techniques à propos de cette version peuvent être +adressés à : + + hackers@FreeBSD.org (en anglais) + +Les rapports de dysfonctionnement « bug reports » peuvent être +notifiés par la commande « send-pr » dès que votre système est +installé. Dans le cas contraire, ils peuvent être adressés à : + + bugs@FreeBSD.org (en anglais) + +N'oubliez par de joindre à votre requête, le numéro de la version de +FreeBSD concernée. + +Les questions d'ordre général sont à diriger vers : + + questions@FreeBSD.org (en anglais) + +Ne soyez pas impatient si vos questions ne trouvent pas réponse dans +la minute, car c'est beaucoup d'investissement que d'y répondre et il +n'est pas rare que toute notre bonne volonté ne suffise pas. Les +problèmes soumis par le biais de la commande « send-pr » sont +automatiquement répertoriés dans une base de données. Vous resterez +informés de toute évolution concernant votre demande. + +Notre site WEB est http://www.freebsd.org. C'est aussi une bonne +source pour obtenir les dernières informations en date. Ce site +propose de nombreuses facilités de documentation. La version de +Netscape compilée pour BSDI peut être utilisée pour découvrir le +« World Wide Web » directement à partir de FreeBSD. + +Pour de plus amples détails, consultez les fichiers contenus dans les +répertoires /usr/share/FAQ et /usr/share/doc. + +Merci de votre attention, nous espérons sincèrement que cette version +de FreeBSD vous donnera entière satisfaction. + + Jordan Hubbard, + pour le projet FreeBSD diff --git a/release/sysinstall/help/fr_FR.ISO_8859-1/configure.hlp b/release/sysinstall/help/fr_FR.ISO_8859-1/configure.hlp new file mode 100644 index 0000000..4f3ed97 --- /dev/null +++ b/release/sysinstall/help/fr_FR.ISO_8859-1/configure.hlp @@ -0,0 +1,16 @@ +Ce menu permet de configurer votre système dès la fin de son +installation. Le minimum conseillé est d'ajouter un mot de passe pour +l'administrateur du système, et d'indiquer le fuseau horaire de votre +localisation. + +Pour installer des utilitaires supplémentaires, tels que bash, emacs, +pascal, etc., vous pouvez utiliser l'entrée « Packages » dans ce +menu. L'obtention automatique de ces outils via FTP n'étant pas encore +disponible, une installation à partir du disque ou du CDROM est +nécessaire. + +Une installation ultérieure de ces outils sera toujours possible, à +l'aide de la commande « pkg_manage ». Un ajustement de l'heure peut +aussi être effectué grâce à « tzsetup ». Enfin, pour modifier la +configuration générale de votre système, reportez vous au contenu du +fichier /etc/sysconfig. diff --git a/release/sysinstall/help/fr_FR.ISO_8859-1/language.hlp b/release/sysinstall/help/fr_FR.ISO_8859-1/language.hlp new file mode 100644 index 0000000..f4a99ea --- /dev/null +++ b/release/sysinstall/help/fr_FR.ISO_8859-1/language.hlp @@ -0,0 +1,13 @@ +Ce menu permet de choisir parmi plusieurs, le langage que vous +préférez. Pour l'instant cela n'est utilisé que dans certains fichiers +d'aide. + +Les versions suivantes permettront d'adapter le clavier, les codes +écran, la configuration NLS (le programme « sysinstall » utilisera +alors des menus en conséquence), et d'autres caractéristiques suivant +votre choix. + +En attendant, la méthode la plus simple consiste à éditer le fichier +/etc/sysconfig dès la fin de l'installation. Les nombreux commentaires +de ce fichier indiquent comment obtenir une configuration personnelle +et proposent quelques exemples. diff --git a/release/sysinstall/help/fr_FR.ISO_8859-1/usage.hlp b/release/sysinstall/help/fr_FR.ISO_8859-1/usage.hlp new file mode 100644 index 0000000..dd1d41a --- /dev/null +++ b/release/sysinstall/help/fr_FR.ISO_8859-1/usage.hlp @@ -0,0 +1,54 @@ +COMMENT UTILISER CE SYSTÈME DE MENUS +==================================== + +TOUCHE ACTION +------ ------ +FLÈCHE HAUT Aller sur la rubrique précédente (ou remonter, dans du texte). +FLÈCHE BAS Aller sur la rubrique suivante (ou descendre, dans du texte). +TAB Aller sur la rubrique ou le groupe suivant. +FLÈCHE DROITE Aller sur la rubrique suivante. (même chose que TAB). +MAJ-TAB Aller sur la rubrique ou le groupe précédent. +FLÈCHE GAUCHE Aller sur la rubrique précédente. (même chose que MAJ-TAB). +ENTRÉE Sélectionne la rubrique. +PAGE PRÉC. Remonte d'une page, dans les boîtes de texte. +PAGE SUIV. Descend d'une page, dans les boîtes de texte. +ESPACE Sélectionne/désélectionne l'élément (menus à choix multiples). +F1 Aide (pour les écrans qui en proposent). + +De même, des symboles du genre "^(-)" ou "v(+)" sur les côtés d'un menu, +indiquent d'autres rubriques non affichées (par manque de place) plus haut ou +plus bas (respectivement). Les flèches haut ou bas feront défiler le menu et +feront apparaître les autres rubriques. Le symbole disparaît dès que le début +(ou la fin) du menu est atteint. + +Dans les boîtes de texte, le pourcentage de texte déjà affiché est indiqué +dans le coin inférieur droit. 100% veut dire qu'il n'y a plus rien à afficher. + +Sélectionner OK dans un menu pour confirmer votre choix. +Sélectionner Cancel pour annuler l'opération et revenir au menu précédent. + + +PARTICULARITÉS. +=============== + +On peut aussi choisir une rubrique dans un menu en tapant la première lettre +de son nom, si il n'y pas d'ambiguïté. Ces lettres "accélératrices" +apparaîtront en sur-brillance dans le nom de la rubrique. + +Il est aussi possible de remonter et revoir du texte qui a déjà défilé. Pour +cela, appuyez sur la touche "arrêt défil" ("Scroll Lock" en anglais) puis +utilisez la flèche-haut ou les touches Page Préc./Page Suiv. pour faire +défiler le texte. Pour quitter ce mode, appuyez à nouveau sur la touche +"arrêt défil.". Cette particularité est utile lorsque l'on est dans un +sous-shell ou dans un mode qui ne présente pas de menu. + +Dès que le système est complètement installé et fonctionne en mode +"multi-utilisateurs", il est possible d'utiliser des "écrans virtuels" +et d'avoir une session dans chacun d'eux. Il suffit d'utiliser +la combinaison de touches ALT-F<n> pour passer de l'un à l'autre : +ALT-F1 pour aller sur la session "1", ALT-F2 pour la session "2", etc. +3 écrans virtuels sont disponibles par défaut mais il est possible d'en +ajouter d'autres en éditant le fichier /etc/ttys (la limite supérieure est +fixée à 12) +Les utilisateurs de X11 pourront noter que ces écrans sont toujours +disponibles depuis X mais par les combinaisons CTRL-ALT-F<n>. diff --git a/release/sysinstall/help/hardware.hlp b/release/sysinstall/help/hardware.hlp new file mode 100644 index 0000000..6bcfb0b --- /dev/null +++ b/release/sysinstall/help/hardware.hlp @@ -0,0 +1,390 @@ +Hardware Documentation Guide: $Id: hardware.hlp,v 1.12.2.1 1995/08/14 10:49:29 rgrimes Exp $ + +Table of Contents +----------------- + +0. Document Conventions +1. Using UserConfig to change FreeBSD kernel settings +2. Default Configuration (GENERIC kernel) +3. LINT - other possible configurations. +4. Known Hardware Problems. + +========================================================================= + +0. Document Conventions +-- -------------------- + +We have `underlined' text which represents user input with `-' +symbols throughout this document to differentiate it from +the machine output. + +1. Using UserConfig to change FreeBSD kernel settings +-- -------------------------------------------------- + +The UserConfig utility allows you to override various settings of +the FreeBSD kernel before the system has booted. This allows you to +make minor adjustments to the various drivers in the system without +necessarily having to recompile the kernel. + +UserConfig is activated by specifying the `-c' flag at the initial +boot prompt. For example: + + >> FreeBSD BOOT @ 0x10000: 640/7168 k of memory + Use hd(1,a)/kernel to boot sd0 when wd0 is also installed. + Usage: [[wd(0,a)]/kernel][-abcCdhrsv] + Use ? for file list or press Enter for defaults + + Boot: -c + -- + +This command causes the system to boot the default kernel ("/kernel") and +the UserConfig utility to be started once the kernel is loaded into memory. + +The `-c' flag follows any of the other parameters you may need to provide +for the system to boot properly. For example, to boot off the second of +two SCSI drives installed and run UserConfig, you would type: + + Boot: sd(1,a)/kernel -c + ----------------- + +As always, the kernel will report some information on your processor +and how much memory your system has. Then UserConfig will be invoked +and you will see the prompt: + + config> + +To see the list of commands that UserConfig accepts, you may type '?' and +press [ENTER]. The help message looks something like this: + +Command Description +------- ----------- +attach <devname> Return results of device attach +ls List currently configured devices +port <devname> <addr> Set device port (i/o address) +irq <devname> <number> Set device irq +drq <devname> <number> Set device drq (DMA Request) +iomem <devname> <addr> Set device maddr (memory address) +iosize <devname> <size> Set device memory size +flags <devname> <mask> Set device flags +enable <devname> Enable device +probe <devname> Return results of device probe +disable <devname> Disable device (will not be probed) +quit Exit this configuration utility +help This message + + +You may alter nearly all of the default settings present in the FreeBSD +generic kernel. This includes reassigning IRQs, disabling troublesome +devices (or drivers that conflict with the hardware your system has), +setting special device flags, etc. + +The most common use of UserConfig is to adjust or disable a driver +which is causing trouble. The "ls" command displays the current +settings for all the drivers present in the booted kernel, and +once you have located an entry of interest you may use the displayed +device name to change its settings or even disable the driver completely. + +For example, to change the memory address of network adapter 'ed0' to +the address 0xd4000, you would type + + config> iomem ed0 0xd4000 + ----------------- + +To entirely disable a device driver you are not using, use the +"disable" command. In this example, you would disable device +`ie0' by typing: + + config> disable ie0 + ----------- + +You can use the "ls" command to verify your changes and correct +any other problems before continuing the boot process. + +Once you are happy with a given configuration you may type: "quit" + +This will cause the kernel to boot with the new settings you +have chosen. + +Once you have a fully installed system (e.g. the `bin' distribution +has been successfully extracted), any changes you make in UserConfig +are permanently stored in the `/kernel' file on the root filesystem. +This action is performed by the `dset' utility, which will ensure that +these settings remain in effect until you replace the kernel with +a new one. If you do not want your changes to be permanently +stored like this, remove `dset' from the /etc/rc file before you +make any changes. + +If you accidentally change a setting for a device that you did not mean +to change, the safest thing to do is to reset the computer and start +over. Do not allow the boot to proceed (e.g. do not type "quit") with +bad settings as these may be permanently stored by dset and +leave your system in a state where it will no longer run properly. + +We suggest as a general rule that you disable any drivers that are not +used by your particular hardware configuration. There are known problems +with certain device drivers (see section 4.0) that can cause conflicts +with other devices if they're also not disabled. You should move or +disable any device that resides at the same port or IRQ as a device +you actually have! + +You can also remove drivers that are not needed by building yourself a +custom kernel that contains only the device drivers which your system +really needs (see section 6.0 of the FreeBSD.FAQ). If your system has +sufficient free disk space to store and compile the kernel sources, +this is the option we most highly recommend. + + + +2. Default (GENERIC) Configuration +-- ------------------------------- + +The following table contains a list of all of the devices that are present +in the GENERIC kernel, which is the kernel (the operating system) that was +placed on your computer during the FreeBSD installation process. +(A compressed version of the GENERIC kernel is also used on the +installation floppy diskettes.) + +The table describes the various parameters used by the driver to communicate +with the hardware in your system. There are four parameters in the +table, but not all are used by each device. They are: + + Port the starting I/O port used by the device, shown in hexadecimal. + + IOMem the lowest (or starting) memory address used by the device, + also shown in hexadecimal. + + IRQ the interrupt the device uses to alert the driver to an event, + given in decimal. + + DRQ the DMA (direct memory access) channel the device uses to move + data to and from main memory, also given in decimal. + +If an entry in the table has `n/a' for the value, it means that the +parameter does not apply to that device. A value of `dyn' means that the +correct value should be determined automatically by the kernel when the +system boots. + + +FreeBSD GENERIC kernel: + + Port IRQ DRQ IOMem Description + ---- --- --- ----- --------------------------------- +fdc0 3f0 6 2 n/a Floppy disk controller +wdc0 1f0 14 n/a n/a IDE/MFM/RLL disk controller +wdc1 170 15 n/a n/a IDE/MFM/RLL disk controller + +ncr0 n/a n/a n/a n/a NCR PCI SCSI controller +ahc0 n/a n/a n/a n/a Adaptec 294x PCI SCSI controller +bt0 330 dyn dyn dyn Buslogic SCSI controller +uha0 330 dyn 6 dyn Ultrastore 14f +ahc1 dyn dyn dyn dyn Adaptec 274x/284x SCSI controller +ahb0 dyn dyn dyn dyn Adaptec 174x SCSI controller +aha0 330 dyn 5 dyn Adaptec 154x SCSI controller +aic0 340 11 dyn dyn Adaptec 152x/AIC-6360 SCSI + controller +nca0 1f88 10 dyn dyn ProAudioSpectrum cards +nca1 350 5 dyn dyn ProAudioSpectrum cards +sea0 dyn 5 dyn c8000 Seagate ST01/02 8 bit controller + +wt0 300 5 1 dyn Wangtek and Archive QIC-02/QIC-36 + +mcd0 300 10 n/a n/a Mitsumi CD-ROM +mcd1 340 11 n/a n/a Mitsumi CD-ROM + +matcd0 dyn n/a n/a n/a Matsushita/Panasonic CD-ROM + +scd0 230 n/a n/a n/a Sony CD-ROM + +sio0 3f8 4 n/a n/a Serial Port 0 (COM1) +sio1 2f8 3 n/a n/a Serial Port 1 (COM2) +sio2 3e8 5 n/a n/a Serial Port 2 (COM3) +sio3 2e8 9 n/a n/a Serial Port 3 (COM4) + +lpt0 dyn 7 n/a n/a Printer Port 0 +lpt1 dyn dyn n/a n/a Printer Port 1 +lpt2 dyn dyn n/a n/a Printer Port 2 + +de0 DEC DC21x40 PCI based cards + (including 21140 100bT cards) +ed0 280 5 dyn d8000 WD & SMC 80xx; Novell NE1000 & + NE2000; 3Com 3C503 +ed1 300 5 dyn d8000 Same as ed0 +eg0 310 5 dyn dyn 3Com 3C505 +ep0 300 10 dyn dyn 3Com 3C509 +ie0 360 7 dyn d0000 AT&T StarLAN 10 and EN100; + 3Com 3C507; NI5210 +ix0 300 10 dyn d0000 Intel EtherExpress cards +le0 300 5 dyn d0000 Digital Equipment EtherWorks + 2 and EtherWorks 3 +lnc0 280 10 n/a dyn Lance/PCnet cards + (Isolan, Novell NE2100, NE32-VL) +lnc1 300 10 n/a dyn See lnc0 +ze0 300 5 dyn d8000 IBM/National Semiconductor + PCMCIA Ethernet Controller +zp0 300 10 dyn d8000 3Com PCMCIA Etherlink III + Ethernet Controller +--- End of table --- + + +If the hardware in your computer is not set to the same settings as +those shown in this table and the item is not marked 'dyn', you will +have to either reconfigure your hardware, or use UserConfig ('-c' boot +option) to reconfigure the kernel to match the way your hardware is +currently set (see section 1.0). + +If the settings do not match, the kernel may be unable to locate +or reliably access the devices in your system. + + + +3. LINT - other possible configurations +-- ------------------------------------ + +The following drivers are not in the GENERIC kernel but remain +available to those who do not mind compiling a custom kernel (see +section 6 of FreeBSD.FAQ). The LINT configuration file +(/sys/i386/conf/LINT) also contains prototype entries for just about +every device supported by FreeBSD and is a good general reference. + +The device names and a short description of each are listed below. The port +numbers, etc, are not meaningful here since you will need to compile a +custom kernel to gain access to these devices anyway and can thus +adjust the addresses to match the hardware in your computer in the process. +The LINT file contains prototype entries for all of the below which you +can easily cut-and-paste into your own file (or simply copy LINT and edit +it to taste): + +apm: Laptop Advanced Power Management (experimental) +ctx: Cortex-I frame grabber +cx: Cronyx/Sigma multiport sync/async +cy: Cyclades high-speed serial driver +el: 3Com 3C501 +fe: Fujitsu MB86960A/MB86965A Ethernet cards +fea: DEV DEFEA EISA FDDI adater +fpa: DEC DEFPA PCI FDDI adapter +gp: National Instruments AT-GPIB and AT-GPIB/TNT board +gsc: Genius GS-4500 hand scanner +gus: Gravis Ultrasound - Ultrasound, Ultrasound 16, Ultrasound MAX +gusmax: Gravis Ultrasound MAX (currently broken) +gusxvi: Gravis Ultrasound 16-bit PCM +joy: Joystick +labpc: National Instrument's Lab-PC and Lab-PC+ +mpu: Roland MPU-401 stand-alone card +mse: Logitech & ATI InPort bus mouse ports +mss: Microsoft Sound System +nic: Dr Neuhaus NICCY 3008, 3009 & 5000 ISDN cards +opl: Yamaha OPL-2 and OPL-3 FM - SB, SB Pro, SB 16, ProAudioSpectrum +pas: ProAudioSpectrum PCM and MIDI +pca: PCM audio ("/dev/audio") through your PC speaker +psm: PS/2 mouse port +rc: RISCom/8 multiport card +sb: SoundBlaster PCM - SoundBlaster, SB Pro, SB16, ProAudioSpectrum +sbmidi: SoundBlaster 16 MIDI interface +sbxvi: SoundBlaster 16 +spigot: Create Labs Video Spigot video-acquisition board +uart: Stand-alone 6850 UART for MIDI +wds: Western Digital WD7000 IDE + +--- end of list --- + + +4. Known Hardware Problems, Q & A: +-- ------------------------------- + +Q: mcd0 keeps thinking that it has found a device and this stops my Intel + EtherExpress card from working. + +A: Use the UserConfig utility (see section 1.0) and disable the probing of + the mcd0 and mcd1 devices. Generally speaking, you should only leave + the devices that you will be using enabled in your kernel. + + +Q: The system finds my ed network card, but I keep getting device + timeout errors. + +A: Your card is probably on a different IRQ from what is specified in the + kernel configuration. The ed driver will no longer use the `soft' + configuration by default (values entered using EZSETUP in DOS), but it + will use the software configuration if you specify `?' in the IRQ field + of your kernel config file. The reason for the change is because the + ed driver used to read and try to use the soft configuration information + even when the card was jumpered to use a hard configuration, and this + caused problems. + + Either move the jumper on the card to a hard configuration setting + (altering the kernel settings if necessary), or specify the IRQ as + `-1' in UserConfig or `?' in your kernel config file. This will + tell the kernel to use the soft configuration. + + Another possibility is that your card is at IRQ 9, which is shared + by IRQ 2 and frequently a cause of problems (especially when you + have a VGA card using 2! :). You should not use IRQ 2 or 9 if at + all possible. + + +Q: I go to boot from the hard disk for the first time after installing + FreeBSD, but the Boot Manager prompt just prints `F?' at the boot menu + each time but the boot won't go any further. + +A: The hard disk geometry was set incorrectly in the Partition editor when + you installed FreeBSD. Go back into the partition editor and specify + the actual geometry of your hard disk. You must reinstall FreeBSD + again from the beginning with the correct geometry. + + If you are failing entirely in figuring out the correct geometry for + your machine, here's a tip: Install a small DOS partition at the + beginning of the disk and install FreeBSD after that. The install + program will see the DOS partition and try to infer the correct + geometry from it, which usually works. + + +Q: I have a Matsushita/Panasonic CD-ROM drive but it isn't recognized + by the system, even if I use UserConfig to change the Port address to + 630, which is what my card uses. + +A: Not all of the companies that sell the Matsushita/Panasonic CR-562 + and CR-563 drives use the same I/O ports and interface that the + matcd driver in FreeBSD expects. The only adapters that are supported + at this time are those that are 100% compatible with the Creative + Labs (SoundBlaster) host interface. See matcd.4 documentation for a + list of host adapters that are known to work. + + +Q: I'm trying to install from a tape drive but all I get is something like: + st0(aha0:1:0) NOT READY csi 40,0,0,0 + on the screen. Help! + +A: There's a limitation in the current sysinstall that the tape MUST + be in the drive while sysinstall is started or it won't be detected. + Try again with the tape in the drive the whole time. + + +Q: I've installed FreeBSD onto my system, but it hangs when booting from + the hard drive with the message: ``Changing root to /dev/sd0a''. + +A: This problem may occur in a system with a 3com 3c509 ethernet adaptor. + The ep0 device driver appears to be sensitive to probes for other + devices that also use address 0x300. Boot your FreeBSD system by power + cycling the machine (turn off and on). At the ``Boot:'' prompt specify + the ``-c''. This will invoke UserConfig (see Section 1. above). Use + the ``disable'' command to disable the device probes for all devices + at address 0x300 except the ep0 driver. On exit, your machine should + successfully boot FreeBSD. + + +Q: My system hangs during boot, right after the "fd0: [my floppy drive]" + line. + +A: This is not actually a hang, simply a very LONG "wdc0" probe that + often takes a long time to complete on certain systems (where there + usually _isn't_ a WD controller). Be patient, your system will boot! + To eliminate the problem, boot with the -c flag and eliminate the wdc0 + device, or compile a custom kernel. + +Q: My sytem can not find an Intel EtherExpress 16 card. + +A: You must set your Intel EtherExpress 16 card to be memory mapped at + address 0xD0000, and set the amount of mapped memory to 32K using + the Intel supplied softset.exe program. + +[ Please add more hardware tips to this Q&A section! ] diff --git a/release/sysinstall/help/install.hlp b/release/sysinstall/help/install.hlp new file mode 100644 index 0000000..95d060c --- /dev/null +++ b/release/sysinstall/help/install.hlp @@ -0,0 +1,447 @@ + INSTALLATION GUIDE FOR FreeBSD 2.0.5 + +This manual documents the process of installing FreeBSD on your +machine. Please also see the Hardware Guide for hardware-specific +installation instructions (how to configure your hardware, what sorts +of things to watch out for, etc) before starting a new installation. + + +Table of Contents: +================== + +1.0 DOS User's Q&A section. + 1.1 How do I make space for FreeBSD? + 1.2 Can I use compressed DOS filesystems from FreeBSD? + 1.3 Can I use DOS extended partitions? + 1.4 Can I run DOS executables under FreeBSD? + +2.0 Preparing for the installation. + 2.1 Before installing from CDROM + 2.2 Before installing from Floppy + 2.3 Before installing from a DOS partition + 2.4 Before installing from QIC/SCSI tape + 2.5 Before installing over a network + 2.5.1 Preparing for NFS Installation + 2.5.2 Preparing for FTP Installation + +3.0 Installing FreeBSD. + + + +1.0 DOS user's Question and Answer section +=== ====================================== + +1.1 Help! I have no space! Do I need to delete everything first? + +If your machine is already running DOS and has little or no free space +available for FreeBSD's installation, all is not lost! You may find +the "FIPS" utility, provided in the tools/ subdirectory on the FreeBSD +CDROM or on the various FreeBSD ftp sites, to be quite useful. + +FIPS allows you to split an existing DOS partition into two pieces, +preserving the original partition and allowing you to install onto the +second free piece. You first "defrag" your DOS partition, using the +DOS 6.xx "DEFRAG" utility or the Norton Disk tools, then run FIPS. It +will prompt you for the rest of the information it needs. Afterwards, +you can reboot and install FreeBSD on the new free slice. See the +Distributions menu for an estimation of how much free space you'll +need for the kind of installation you want. + + +1.2 Can I use compressed DOS filesystems from FreeBSD? + +No. If you are using a utility such as Stacker(tm) or DoubleSpace(tm), +FreeBSD will only be able to use whatever portion of the filesystem +you leave uncompressed. The rest of the filesystem will show up as +one large file (the stacked/dblspaced file!). DO NOT REMOVE THAT +FILE! You will probably regret it greatly! + +It is probably better to create another uncompressed DOS primary +partition and use this for communications between DOS and FreeBSD. + + +1.3 Can I mount my DOS extended partitions? + +This feature isn't in FreeBSD 2.0.5 but should be in 2.1. We've laid +all the groundwork for making this happen, now we just need to do the +last 1% of the work involved. + + +1.4 Can I run DOS binaries under FreeBSD? + +Not yet! We'd like to add support for this someday, but are still +lacking anyone to actually do the work. Ongoing work with Linux's +DOSEMU utility may bring this much closer to being a reality sometime +soon. Send mail to hackers@freebsd.org if you're interested in +joining this effort! + +However, there is a neat utility called "pcemu" in the ports collection +which emulates an 8088 and enough BIOS services to run DOS text mode +applications. It requires the X Window System (provided as +XFree86 3.1.1u1). + + + +2.0 Preparing for the installation +=== ============================== + +2.1 Before installing from CDROM: + +If your CDROM is of an unsupported type, such as an IDE CDROM, then +please skip to section 2.3: Before installing from a DOS partition. + +There is not a lot of preparatory work that needs to be done to +successfully install from one of Walnut Creek's FreeBSD CDROMs (other +CDROM distributions may work as well, we simply cannot say as we +have no hand or say in their creation). You can either boot into the +CD installation directly from DOS using Walnut Creek's supplied +``install.bat'' batch file or you can make a boot floppy with +the ``makeflp.bat'' command. + +For the easiest interface of all (from DOS), type "go". This +will bring up a DOS menu utility that leads you through all +the available options. + +If you're creating the boot floppy from a UNIX machine, you may find +that ``dd if=floppies/boot.flp of=/dev/rfd0'' or +``dd if=floppies/boot.flp of=/dev/floppy'' works well, depending on +your hardware and operating system environment. + +Once you've booted from DOS or floppy, you should then be able to select +CDROM as the media type in the Media menu and load the entire +distribution from CDROM. No other types of installation media should +be required. + +After your system is fully installed and you have rebooted from the +hard disk, you should find the CD mounted on the directory /cdrom. A +utility called `lndir' comes with the XFree86 distribution which you +may also find useful: It allows you to create "link tree" directories +to things on Read-Only media like CDROM. One example might be +something like this: + + mkdir /usr/ports + lndir /cdrom/ports /usr/ports + +Which would allow you to then "cd /usr/ports; make" and get all the +sources from the CD, but yet create all the intermediate files in +/usr/ports, which is presumably on a more writable media! :-) + +SPECIAL NOTE: Before invoking the installation, be sure that the +CDROM is in the drive so that the "probe" can find it! +This is also true if you wish the CDROM to be added to the default +system configuration automatically during the install (whether or +not you actually use it as the installation media). This will be +fixed for 2.1, but for now this simple work-around will ensure that +your CDROM is detected properly. + +Finally, if you would like people to be able to FTP install +FreeBSD directly from the CDROM in your machine, you'll find +it quite easy. After the machine is fully installed, you simply +need to add the following line to the password file (using +the vipw command): + + ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent + +No further work is necessary. The other installers will now be able +to chose a Media type of FTP and type in: ftp://<your machine> +after picking "Other" in the ftp sites menu! + + +2.2 Before installing from Floppy: + +If you must install from floppy disks, either due to unsupported +hardware or just because you enjoy doing things the hard way, you must +first prepare some floppies for the install. + +The first floppy you'll need is ``floppies/root.flp'', which is +somewhat special in that it's not a DOS filesystem floppy at all, but +rather an "image" floppy (it's actually a gzip'd cpio file). You can +use the rawrite.exe program to do this under DOS, or ``dd'' to do it +on a UNIX Workstation (see notes in section 2.1 concerning the +``floppies/boot.flp'' image). Once this floppy is made, go on +to make the distribution set floppies: + +You will need, at minimum, as many 1.44MB or 1.2MB floppies as it takes +to hold all files in the bin (binary distribution) directory. THESE +floppies *must* be formatted using MS-DOS, using the FORMAT command in +MS-DOS or the File Manager format command in Microsoft Windows(tm). +Don't trust Factory Preformatted floppies! Format them again yourself, +just to make sure! + +Many problems reported by our users in the past have resulted from the +use of improperly formatted media, so we simply take special care to +mention it here! + +After you've DOS formatted the floppies, you'll need to copy the files +onto them. The distribution files are split into chunks conveniently +sized so that 5 of them will fit on a conventional 1.44MB floppy. Go +through all your floppies, packing as many files as will fit on each +one, until you've got all the distributions you want packed up in this +fashion. Each distribution should go into a subdirectory on the +floppy, e.g.: a:\bin\bin.aa, a:\bin\bin.ab, ... + +Once you come to the Media screen of the install, select +"Floppy" and you'll be prompted for the rest. + + +2.3 Before installing from a DOS partition: + +To prepare for installation from an MS-DOS partition you should +simply copy the files from the distribution into a directory called +"FREEBSD". For example, to do a minimal installation of FreeBSD from +DOS using files copied from the CDROM, you might do something like +this: + + C> MD C:\FREEBSD + C> XCOPY /S E:\DISTS\BIN C:\FREEBSD\BIN + C> XCOPY /S E:\FLOPPIES C:\FREEBSD\FLOPPIES + +Asssuming that `C:' was where you had free space and `E:' was where +your CD was mounted. Note that you need the FLOPPIES directory +because the `root.flp' image is automatically looked for there when +you're doing a DOS installation. + +For as many `DISTS' as you wish to install from DOS (and you have free +space for), install each one in a directory under `C:\FREEBSD' - the +BIN dist is only the minimal requirement. + + +2.4 Before installing from QIC/SCSI Tape: + +Installing from tape is probably the easiest method, short of an +on-line install using FTP or a CDROM install. The installation program +expects the files to be simply tar'ed onto the tape, so after getting +all of the files for distribution you're interested in, simply tar +them onto the tape with a command like: + + cd /freebsd/distdir + tar cvf /dev/rwt0 (or /dev/rst0) dist1 .. dist2 + +Make sure that the `floppies/' directory is one of the "dists" given +above, since the installation will look for `floppies/root.flp' on +the tape. + +When you go to do the installation, you should also make sure that you +leave enough room in some temporary directory (which you'll be allowed +to choose) to accommodate the FULL contents of the tape you've +created. Due to the non-random access nature of tapes, this method of +installation requires quite a bit of temporary storage! You should +expect to require as much temporary storage as you have stuff written +on tape. + +SPECIAL NOTE: When going to do the installation, the tape must be in +the drive *before* booting from the boot floppy. The installation +"probe" may otherwise fail to find it. + + +2.5 Before installing over a network: + +You can do network installations over 3 types of communications links: + + Serial port: SLIP / PPP + Parallel port: PLIP (laplink cable) + Ethernet: A standard ethernet controller (includes some PCMCIA). + +SLIP support is rather primitive, and limited primarily to hard-wired +links, such as a serial cable running between a laptop computer and +another computer. The link should be hard-wired as the SLIP +installation doesn't currently offer a dialing capability; that +facility is provided with the PPP utility, which should be used in +preference to SLIP whenever possible. + +If you're using a modem, then PPP is almost certainly your only +choice. Make sure that you have your service provider's information +handy as you'll need to know it fairly soon in the installation +process. You will need to know, at the minimum, your service +provider's IP address and possibly your own (though you can also leave +it blank and allow PPP to negotiate it with your ISP). You also need +to know how to use the various "AT commands" to dial the ISP with your +particular modem as the PPP dialer provides only a very simple +terminal emulator. + +If a hard-wired connection to another FreeBSD (2.0R or later) machine +is available, you might also consider installing over a "laplink" +parallel port cable. The data rate over the parallel port is much +higher than what is typically possible over a serial line (up to +50k/sec), thus resulting in a quicker installation. + +Finally, for the fastest possible network installation, an ethernet +adaptor is always a good choice! FreeBSD supports most common PC +ethernet cards, a table of supported cards (and their required +settings) is provided as part of the FreeBSD Hardware Guide - see the +Documentation menu on the boot floppy. If you are using one of the +supported PCMCIA ethernet cards, also be sure that it's plugged in +_before_ the laptop is powered on! FreeBSD does not, unfortunately, +currently support "hot insertion" of PCMCIA cards. + +You will also need to know your IP address on the network, the +"netmask" value for your address class, and the name of your machine. +Your system administrator can tell you which values to use for your +particular network setup. If you will be referring to other hosts by +name rather than IP address, you'll also need a name server and +possibly the address of a gateway (if you're using PPP, it's your +provider's IP address) to use in talking to it. If you do not know +the answers to all or most of these questions, then you should +really probably talk to your system administrator _first_ before +trying this type of installation! + +Once you have a network link of some sort working, the installation +can continue over NFS or FTP. + +2.5.1 Preparing for NFS installation: + + NFS installation is fairly straight-forward: Simply copy the + FreeBSD distribution files you want onto a server somewhere + and then point the NFS media selection at it. + + If this server supports only "privileged port" access (as is + generally the default for Sun workstations), you will need to set + this option in the Options menu before installation can proceed. + + If you have a poor quality ethernet card which suffers from very + slow transfer rates, you may also wish to toggle the appropriate + Options flag. + + In order for NFS installation to work, the server must support + "subdir mounts"; e.g., if your FreeBSD 2.0.5 distribution directory + lives on: ziggy:/usr/archive/stuff/FreeBSD + Then ziggy will have to allow the direct mounting of + /usr/archive/stuff/FreeBSD, not just /usr or /usr/archive/stuff. + + In FreeBSD's /etc/exports file, this is controlled by the + ``-alldirs'' option. Other NFS servers may have different + conventions. If you are getting `Permission Denied' messages + from the server then it's likely that you don't have this + enabled properly! + + +2.5.2 Preparing for FTP Installation + + FTP installation may be done from any mirror site containing a + reasonably up-to-date version of FreeBSD 2.0.5. A full menu of + reasonable choices from almost anywhere in the world is provided + by the FTP site menu. + + If you are installing from some other FTP site not listed in this + menu, or you are having troubles getting your name server configured + properly, you can also specify your own URL by selecting the ``Other'' + choice in that menu. A URL can also be a direct IP address, so + the following would work in the absence of a name server: + + ftp://192.216.222.4/pub/FreeBSD/2.0.5-RELEASE + + [Substitute "ALPHA" for "RELEASE" during the ALPHA test period!] + + If you are installing through a firewall then you should probably + select ``Passive mode'' ftp, which is the default. If you are + talking to a server which does not support passive mode for some + reason, see the Options menu to select Active mode transfers. + + +3. Installing FreeBSD +-- ------------------ + +Once you've taken note of the appropriate preinstallation steps, you +should be able to install FreeBSD without any further trouble. + +Should this not be true, then you may wish to go back and re-read the +relevant preparation section (section 2.x) for the installation media +type you're trying to use - perhaps there's a helpful hint there that +you missed the first time? If you're having hardware trouble, or +FreeBSD refuses to boot at all, read the Hardware Guide provided on +the boot floppy for a list of possible solutions. + +The FreeBSD boot floppy contains all the on-line documentation you +should need to be able to navigate through an installation and if it +doesn't then I'd like to know what you found most confusing! It is +the objective of the FreeBSD installation program (sysinstall) to be +self-documenting enough that painful "step-by-step" guides are no +longer necessary. It may take us a little while to reach that +objective, but that's the objective! + +Meanwhile, you may also find the following "typical installation sequence" +to be helpful: + +o Boot the boot floppy. After a boot sequence which can take + anywhere from from 30 seconds to 3 minutes, depending on your + hardware, you should be presented with a menu of initial + choices. If the floppy doesn't boot at all, or the boot + hangs at some stage, go read the Q&A section of the Hardware + Guide for possible causes. + +o Press F1. You should see some basic usage instructions on + the menu system and general navigation. If you haven't used this + menu system before then PLEASE read this thoroughly! + +o If English is not your native language, you may wish to proceed + directly to the Language option and set your preferred language. + This will bring up some of the documentation in that language + instead of english. + +o Select the Options item and set any special preferences you + may have. + +o Select Proceed, bringing you to the Installation Menu. + +Installation Menu: + +o You can do anything you like in this menu without altering + your system _except_ for "Commit", which will perform any + requests to alter your system you may have made. + + If you're confused at any point, the F1 key usually pulls + up the right information for the screen you're in. + + o The first step is generally `Partition', which allows + you to chose how your drives will be used for FreeBSD. + + o Next, with the `Label' editor, you can specify how the space + in any allocated FreeBSD partitions should be used by FreeBSD, + or where to mount a non-FreeBSD partition (such as DOS). + + o Next, the `Distributions' menu allows you to specify which + parts of FreeBSD you wish to load. A good choice is + "User" for a small system or "Developer" for someone + wanting a bit more out of FreeBSD. If none of the existing + collections sound applicable, select Custom. + + o Next, the `Media' menu allows you to specify what kind of + media you wish to install from. If a desired media choice is + found and configured automatically then this menu will simply + return, otherwise you'll be asked for additional details on + the media device type. + + o Finally, the Commit command will actually perform all the + actions at once (nothing has been written to your disk + so far, nor will it until you give the final confirmation). + All new or changed partition information will be written + out, file systems will be created and/or non-destructively + labelled (depending on how you set their newfs flags in the + Label editor) and all selected distributions will be + extracted. + + o The Configure menu choice allows you to furthur configure your + FreeBSD installation by giving you menu-driven access to + various system defaults. Some items, like networking, may + be especially important if you did a CDROM/Tape/Floppy + installation and have not yet configured your network + interfaces (assuming you have some). Properly configuring + your network here will allow FreeBSD to come up on the network + when you first reboot from the hard disk. + + o Exit returns you to the top menu. + + + At this point, you're generally done with the sysinstall utility and +can select the final `Quit'. If you're running it as an installer +(e.g., before the system is all the way up) then the system will now +reboot. If you selected the boot manager option, you will see a small +boot menu with an `F?' prompt. Press the function key for BSD (it +will be shown) and you should boot up into FreeBSD off the hard disk. + + If this fails to happen for some reason, see the Q & A section +of the Hardware Guide for possible clues! + + Jordan + +---- End of Installation Guide --- diff --git a/release/sysinstall/help/it_IT.ISO8859-1/README b/release/sysinstall/help/it_IT.ISO8859-1/README new file mode 100644 index 0000000..cd6f64b --- /dev/null +++ b/release/sysinstall/help/it_IT.ISO8859-1/README @@ -0,0 +1,107 @@ + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Version , , + ----------------------------------------- /( )` + \ \___ / | +Benvenuti alla release 2.0.5 di FreeBSD! 2.0.5 e` /- _ `-/ ' +una release completa di FreeBSD che riempie il lungo (/\/ \ \ /\ +intervallo tra la 2.0R (introdotta a Nov.94) e la / / | ` \ +2.1R (che uscira` a fine luglio '95). FreeBSD 2.0.5 O O ) / | +contiene molti importanti miglioramenti rispetto `-^--'`< ' +alla versione 2.0R, non ultimo una stabilita` molto (_.) _ ) / +maggiore, decine di nuove opzioni e un programma `.___/` / +di installazione molto migliorato. `-----' / +Maggiori dettagli su cosa c'e' di <----. __ / __ \ +nuovo in FreeBSD 2.0.5 sono nelle <----|====O)))==) \) /==== +release notes. <----' `--' `.__,' \ + | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +Cos'e` FreeBSD ? E` un sistema operativo basato su 4.4 BSD Lite +per PC basati su hardware Intel, AMD, Cyrix o NexGen "x86". Supporta +moltissime periferiche e configurazioni hardware e puo` essere +usato per applicazioni che vanno dallo sviluppo di software alla +fornitura di servizi Internet. Il nodo piu` gettonato della Internet, +ftp.cdrom.com, e` una macchina FreeBSD! + +Questa versione di FreeBSD contiene tutto quello che serve per far +funzionare il sistema, e inoltre i sorgenti completi del sistema +e di ogni applicazione. Installando la distribuzione dei sorgenti +sarete in grado di ricompilare l'intero sistema operativo da zero +con un solo comando: questa e` una caratteristica ideale per +studenti, ricercatori o altri interessati a vedere come funziona +il tutto. + +E` anche disponibile (la "ports collection") un gran numero di +pacchetti software forniti da terze parti e portati su FreeBSD, +per semplificarvi il compito di cercare e installare tutte le +utilities tradizionali di Unix su FreeBSD. Ci sono oltre 270 +applicazioni, che comprendono editor, linguaggi di programmazione, +applicazioni grafiche, e rendono FreeBSD un ambiente operativo +potente e completo che rivaleggia, per potenza e utilita`, quello +di molte workstation di grosse dimensioni. + +Maggiori informazioni e documentazione sul sistema si possono +trovare sul "4.4BSD Document Set", della O'Reilly Associates e +USENIX Association, ISBN 1-56592-082-1. Non abbiamo nessuna +connessione con la O'Reilly, siamo solo acquirenti soddisfatti! + +Si consiglia la lettura della HARDWARE GUIDE *prima* di procedere +con l'installazione. La configurazione dell'hardware di un PC per +applicazioni che non siano DOS/Windows (queste di fatto sfruttano +ben poco l'hardware) e` piu` difficile di quanto sembri, e se +pensate di conoscere i PC e` semplicemente perche' non li avete +usati abbastanza a lungo! :) Questa guida vi fornira` qualche +suggerimento su come configurare il vostro hardware e a quali +sintomi fare attenzione in caso di problemi. La guida e` disponibile +nel menu "Documentazione" del disco di boot di FreeBSD. + +ATTENZIONE: FreeBSD fa il possibile per salvaguardarvi da perdite +accidentali di dati, ma l'imprevisto e` sempre in agguato, ed e` +sempre possibile che IL VOSTRO DISCO POSSA ESSERE COMPLETAMENTE +CANCELLATO durante l'installazione. Quindi, per vostra sicurezza, +non procedete con l'installazione se non avete prima fatto una +copia di informazioni importanti che si trovano sullo stesso! Uomo +avvisato, mezzo salvato! + +Commenti e osservazioni tecniche su questa release possono essere +inviate (in inglese!) a + + hackers@FreeBSD.org + +Segnalazioni di bachi (bug) possono essere inviate col comando +`send-pr' (se siete riusciti a installare il sistema), o altrimenti +per email a: + + bugs@FreeBSD.org + +Per favore indicate esattamente a QUALE VERSIONE di FreeBSD si +riferisce il problema a cui fate riferimento. + +Domande di tipo generale si possono inviare a: + + questions@FreeBSD.org + +Pazientate se le vostre domande non ricevono risposta immediata - +questo e` un periodo di grande impegno per noi, e il tempo dei +nostri volontari e` spesso tirato al limite! Le indicazioni di bug +inviate col comando send-pr sono registrate e gestite dal nostro +database per la gestione dei bug, e sarete quindi informati di +eventuali cambiamenti nel loro stato. + +Il nostro sito WEB, http://www.freebsd.org, e` una buona sorgente +di informazioni aggiornate e fornisce un buon numero di informazioni +avanzate. Su FreeBSD potete usare la versione per BSDI di Netscape +per navigare su World Wide Web. + +Potete anche cercare in /usr/share/FAQ e /usr/share/doc per ulteriori +informazioni sul sistema. + +Grazie per essere arrivati fino a questo punto. Speriamo che questa +versione di FreeBSD vi soddisfi! + + Jordan Hubbard, + per il "FreeBSD Project" diff --git a/release/sysinstall/help/it_IT.ISO8859-1/configure.hlp b/release/sysinstall/help/it_IT.ISO8859-1/configure.hlp new file mode 100644 index 0000000..d144cf1 --- /dev/null +++ b/release/sysinstall/help/it_IT.ISO8859-1/configure.hlp @@ -0,0 +1,16 @@ +Questo menu vi permette di scegliere la configurazione iniziale +del sistema dopo l'installazione. Come minimo, andrebbero definite +la password del system manager e il fuso orario locale. + +Per applicazioni addizionali quali bash, emacs, pascal ecc. fate +riferimento alla voce "Packages" in questo menu. Si noti che questa +voce e` utile solo se avete a disposizione il CDROM o la collezione +dei sorgenti delle applicazioni da qualche parte nel file system. +Il trasferimento automatico, via FTP, dei sorgenti non e` ancora +supportato. + +Se volete invocare nuovamente il software di installazione delle +applicazioni dopo aver finito l'installazione, dovete usare il +comando ``pkg_manage''. Per scegliere il fuso orario, battere +``tzsetup''. Per ulteriori informazioni sulla configurazione generale +del sistema, guardare il file ``/etc/sysconfig''. diff --git a/release/sysinstall/help/it_IT.ISO8859-1/language.hlp b/release/sysinstall/help/it_IT.ISO8859-1/language.hlp new file mode 100644 index 0000000..2bc2a0e --- /dev/null +++ b/release/sysinstall/help/it_IT.ISO8859-1/language.hlp @@ -0,0 +1,15 @@ + +Usate questo menu per scegliere il vostro linguaggio preferito. Al +momento, questa selezione influenza solo il linguaggio nel quale +sono mostrati i files di help. + +In future release, questa selezione cambiera` anche il layout della +tastiera, la tabella dei caratteri, le funzioni di supporto ai +linguaggi nazionali, e altre funzioni I18N che fanno parte dei vari +standard. + +Fino a quando tutte queste funzionalita` non saranno attive, e` +probabilmente piu` semplice editare a mano il file /etc/sysconfig +una volta che il sistema e` installato completamente. Nel file ci +sono diversi commenti che spiegano cosa dovrebbe essere cambiato, +e anche alcuni esempi di settaggi per lingue diverse dall'inglese. diff --git a/release/sysinstall/help/it_IT.ISO8859-1/usage.hlp b/release/sysinstall/help/it_IT.ISO8859-1/usage.hlp new file mode 100644 index 0000000..bc4fd38 --- /dev/null +++ b/release/sysinstall/help/it_IT.ISO8859-1/usage.hlp @@ -0,0 +1,56 @@ +COME USARE QUESTO SISTEMA +========================= + +TASTO AZIONE +----- ------ +FRECCIA IN ALTO voce precedente (o linea in alto, in un'area di testo) +FRECCIA IN BASSO voce successiva (o linea in basso, in un'area di testo) +TAB voce o gruppo successivo +FRECCIA A DESTRA voce o gruppo successivo (come TAB) +SHIFT-TAB voce o gruppo precedente +FRECCIA A SINISTRA voce o gruppo precedente (come SHIFT-TAB) +RETURN selezione voce corrente +PAGINA SU nelle aree di testo, va alla pagina precedente +PAGINA GIU nelle aree di testo, va alla pagina successiva +SPAZIO cambia stato alla voce corrente (menu "radio") +F1 aiuto (nelle schermate che lo prevedono). + +I simboli "^(-)" or "v(+)" ai lati del menu indicano che ci sono +altre voci oltre a quella corrente che non sono visualizzate per +carenza di spazio sullo schermo. Le frecce in alto/basso provocano +lo scroll del menu. Quando uno di questi simboli scompare, si e` +raggiunto l'inizio o la fine del menu. + +Nei campi di tipo testo, la percentuale rimanente del testo e` +mostrata nell'angolo in masso a destra. 100% significa che si e` +posizionati alla fine del campo. + +Selezionando OK in un menu si conferma l'azione che esso controlla. +Selezionando Cancel si cancella l'operazione e di solito si ritorna +al menu precedente. + + +FUNZIONI SPECIALI +================= + +E` possibile selezionare una voce di un menu anche battendo il +primo carattere del suo nome, se unico. Questi caratteri "acceleratori" +saranno evidenziati nel nome del menu. + +Il driver della console contiene anche un buffer che permette di +rivedere cose che sono scomparse dallo schermo a causa dello scroll. +Per usare questa funzione (scroll-back), premere il tasto +"Scroll Lock" sulla tastiera e usare i tasti "Pagina Su"/"Pagina Giu" per +muoversi attraverso il testo salvato. Per tornare al funzionamento +normale, premere nuovamente il tasto "Scroll Lock". Questa funzione +e` utile soprattutto all'interno di sotto-shell o altre funzioni +speciali che non usano i menu. + +Quando il sistema e` installato e completamente funzionante in +modo multiutente, e` possibile usare le "console virtuali" per +avere diverse sessioni contemporanee. I tasti ALT-F<n> possono +essere usati per commutare tra le finestre disponibili, dove F<n> +e` il tasto funzione corrispondente allo schermo desiderato. La +configurazione di default prevede 3 console abilitate, ma se ne +possono creare altre -- fino a 12 -- modificando il file /etc/ttys +quando il sistema e` in modo multiutente. diff --git a/release/sysinstall/help/it_IT.ISO_8859-1/README b/release/sysinstall/help/it_IT.ISO_8859-1/README new file mode 100644 index 0000000..cd6f64b --- /dev/null +++ b/release/sysinstall/help/it_IT.ISO_8859-1/README @@ -0,0 +1,107 @@ + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Version , , + ----------------------------------------- /( )` + \ \___ / | +Benvenuti alla release 2.0.5 di FreeBSD! 2.0.5 e` /- _ `-/ ' +una release completa di FreeBSD che riempie il lungo (/\/ \ \ /\ +intervallo tra la 2.0R (introdotta a Nov.94) e la / / | ` \ +2.1R (che uscira` a fine luglio '95). FreeBSD 2.0.5 O O ) / | +contiene molti importanti miglioramenti rispetto `-^--'`< ' +alla versione 2.0R, non ultimo una stabilita` molto (_.) _ ) / +maggiore, decine di nuove opzioni e un programma `.___/` / +di installazione molto migliorato. `-----' / +Maggiori dettagli su cosa c'e' di <----. __ / __ \ +nuovo in FreeBSD 2.0.5 sono nelle <----|====O)))==) \) /==== +release notes. <----' `--' `.__,' \ + | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +Cos'e` FreeBSD ? E` un sistema operativo basato su 4.4 BSD Lite +per PC basati su hardware Intel, AMD, Cyrix o NexGen "x86". Supporta +moltissime periferiche e configurazioni hardware e puo` essere +usato per applicazioni che vanno dallo sviluppo di software alla +fornitura di servizi Internet. Il nodo piu` gettonato della Internet, +ftp.cdrom.com, e` una macchina FreeBSD! + +Questa versione di FreeBSD contiene tutto quello che serve per far +funzionare il sistema, e inoltre i sorgenti completi del sistema +e di ogni applicazione. Installando la distribuzione dei sorgenti +sarete in grado di ricompilare l'intero sistema operativo da zero +con un solo comando: questa e` una caratteristica ideale per +studenti, ricercatori o altri interessati a vedere come funziona +il tutto. + +E` anche disponibile (la "ports collection") un gran numero di +pacchetti software forniti da terze parti e portati su FreeBSD, +per semplificarvi il compito di cercare e installare tutte le +utilities tradizionali di Unix su FreeBSD. Ci sono oltre 270 +applicazioni, che comprendono editor, linguaggi di programmazione, +applicazioni grafiche, e rendono FreeBSD un ambiente operativo +potente e completo che rivaleggia, per potenza e utilita`, quello +di molte workstation di grosse dimensioni. + +Maggiori informazioni e documentazione sul sistema si possono +trovare sul "4.4BSD Document Set", della O'Reilly Associates e +USENIX Association, ISBN 1-56592-082-1. Non abbiamo nessuna +connessione con la O'Reilly, siamo solo acquirenti soddisfatti! + +Si consiglia la lettura della HARDWARE GUIDE *prima* di procedere +con l'installazione. La configurazione dell'hardware di un PC per +applicazioni che non siano DOS/Windows (queste di fatto sfruttano +ben poco l'hardware) e` piu` difficile di quanto sembri, e se +pensate di conoscere i PC e` semplicemente perche' non li avete +usati abbastanza a lungo! :) Questa guida vi fornira` qualche +suggerimento su come configurare il vostro hardware e a quali +sintomi fare attenzione in caso di problemi. La guida e` disponibile +nel menu "Documentazione" del disco di boot di FreeBSD. + +ATTENZIONE: FreeBSD fa il possibile per salvaguardarvi da perdite +accidentali di dati, ma l'imprevisto e` sempre in agguato, ed e` +sempre possibile che IL VOSTRO DISCO POSSA ESSERE COMPLETAMENTE +CANCELLATO durante l'installazione. Quindi, per vostra sicurezza, +non procedete con l'installazione se non avete prima fatto una +copia di informazioni importanti che si trovano sullo stesso! Uomo +avvisato, mezzo salvato! + +Commenti e osservazioni tecniche su questa release possono essere +inviate (in inglese!) a + + hackers@FreeBSD.org + +Segnalazioni di bachi (bug) possono essere inviate col comando +`send-pr' (se siete riusciti a installare il sistema), o altrimenti +per email a: + + bugs@FreeBSD.org + +Per favore indicate esattamente a QUALE VERSIONE di FreeBSD si +riferisce il problema a cui fate riferimento. + +Domande di tipo generale si possono inviare a: + + questions@FreeBSD.org + +Pazientate se le vostre domande non ricevono risposta immediata - +questo e` un periodo di grande impegno per noi, e il tempo dei +nostri volontari e` spesso tirato al limite! Le indicazioni di bug +inviate col comando send-pr sono registrate e gestite dal nostro +database per la gestione dei bug, e sarete quindi informati di +eventuali cambiamenti nel loro stato. + +Il nostro sito WEB, http://www.freebsd.org, e` una buona sorgente +di informazioni aggiornate e fornisce un buon numero di informazioni +avanzate. Su FreeBSD potete usare la versione per BSDI di Netscape +per navigare su World Wide Web. + +Potete anche cercare in /usr/share/FAQ e /usr/share/doc per ulteriori +informazioni sul sistema. + +Grazie per essere arrivati fino a questo punto. Speriamo che questa +versione di FreeBSD vi soddisfi! + + Jordan Hubbard, + per il "FreeBSD Project" diff --git a/release/sysinstall/help/it_IT.ISO_8859-1/configure.hlp b/release/sysinstall/help/it_IT.ISO_8859-1/configure.hlp new file mode 100644 index 0000000..d144cf1 --- /dev/null +++ b/release/sysinstall/help/it_IT.ISO_8859-1/configure.hlp @@ -0,0 +1,16 @@ +Questo menu vi permette di scegliere la configurazione iniziale +del sistema dopo l'installazione. Come minimo, andrebbero definite +la password del system manager e il fuso orario locale. + +Per applicazioni addizionali quali bash, emacs, pascal ecc. fate +riferimento alla voce "Packages" in questo menu. Si noti che questa +voce e` utile solo se avete a disposizione il CDROM o la collezione +dei sorgenti delle applicazioni da qualche parte nel file system. +Il trasferimento automatico, via FTP, dei sorgenti non e` ancora +supportato. + +Se volete invocare nuovamente il software di installazione delle +applicazioni dopo aver finito l'installazione, dovete usare il +comando ``pkg_manage''. Per scegliere il fuso orario, battere +``tzsetup''. Per ulteriori informazioni sulla configurazione generale +del sistema, guardare il file ``/etc/sysconfig''. diff --git a/release/sysinstall/help/it_IT.ISO_8859-1/language.hlp b/release/sysinstall/help/it_IT.ISO_8859-1/language.hlp new file mode 100644 index 0000000..2bc2a0e --- /dev/null +++ b/release/sysinstall/help/it_IT.ISO_8859-1/language.hlp @@ -0,0 +1,15 @@ + +Usate questo menu per scegliere il vostro linguaggio preferito. Al +momento, questa selezione influenza solo il linguaggio nel quale +sono mostrati i files di help. + +In future release, questa selezione cambiera` anche il layout della +tastiera, la tabella dei caratteri, le funzioni di supporto ai +linguaggi nazionali, e altre funzioni I18N che fanno parte dei vari +standard. + +Fino a quando tutte queste funzionalita` non saranno attive, e` +probabilmente piu` semplice editare a mano il file /etc/sysconfig +una volta che il sistema e` installato completamente. Nel file ci +sono diversi commenti che spiegano cosa dovrebbe essere cambiato, +e anche alcuni esempi di settaggi per lingue diverse dall'inglese. diff --git a/release/sysinstall/help/it_IT.ISO_8859-1/usage.hlp b/release/sysinstall/help/it_IT.ISO_8859-1/usage.hlp new file mode 100644 index 0000000..bc4fd38 --- /dev/null +++ b/release/sysinstall/help/it_IT.ISO_8859-1/usage.hlp @@ -0,0 +1,56 @@ +COME USARE QUESTO SISTEMA +========================= + +TASTO AZIONE +----- ------ +FRECCIA IN ALTO voce precedente (o linea in alto, in un'area di testo) +FRECCIA IN BASSO voce successiva (o linea in basso, in un'area di testo) +TAB voce o gruppo successivo +FRECCIA A DESTRA voce o gruppo successivo (come TAB) +SHIFT-TAB voce o gruppo precedente +FRECCIA A SINISTRA voce o gruppo precedente (come SHIFT-TAB) +RETURN selezione voce corrente +PAGINA SU nelle aree di testo, va alla pagina precedente +PAGINA GIU nelle aree di testo, va alla pagina successiva +SPAZIO cambia stato alla voce corrente (menu "radio") +F1 aiuto (nelle schermate che lo prevedono). + +I simboli "^(-)" or "v(+)" ai lati del menu indicano che ci sono +altre voci oltre a quella corrente che non sono visualizzate per +carenza di spazio sullo schermo. Le frecce in alto/basso provocano +lo scroll del menu. Quando uno di questi simboli scompare, si e` +raggiunto l'inizio o la fine del menu. + +Nei campi di tipo testo, la percentuale rimanente del testo e` +mostrata nell'angolo in masso a destra. 100% significa che si e` +posizionati alla fine del campo. + +Selezionando OK in un menu si conferma l'azione che esso controlla. +Selezionando Cancel si cancella l'operazione e di solito si ritorna +al menu precedente. + + +FUNZIONI SPECIALI +================= + +E` possibile selezionare una voce di un menu anche battendo il +primo carattere del suo nome, se unico. Questi caratteri "acceleratori" +saranno evidenziati nel nome del menu. + +Il driver della console contiene anche un buffer che permette di +rivedere cose che sono scomparse dallo schermo a causa dello scroll. +Per usare questa funzione (scroll-back), premere il tasto +"Scroll Lock" sulla tastiera e usare i tasti "Pagina Su"/"Pagina Giu" per +muoversi attraverso il testo salvato. Per tornare al funzionamento +normale, premere nuovamente il tasto "Scroll Lock". Questa funzione +e` utile soprattutto all'interno di sotto-shell o altre funzioni +speciali che non usano i menu. + +Quando il sistema e` installato e completamente funzionante in +modo multiutente, e` possibile usare le "console virtuali" per +avere diverse sessioni contemporanee. I tasti ALT-F<n> possono +essere usati per commutare tra le finestre disponibili, dove F<n> +e` il tasto funzione corrispondente allo schermo desiderato. La +configurazione di default prevede 3 console abilitate, ma se ne +possono creare altre -- fino a 12 -- modificando il file /etc/ttys +quando il sistema e` in modo multiutente. diff --git a/release/sysinstall/help/ja_JP.JIS/README b/release/sysinstall/help/ja_JP.JIS/README new file mode 100644 index 0000000..fd43dd3 --- /dev/null +++ b/release/sysinstall/help/ja_JP.JIS/README @@ -0,0 +1,97 @@ + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Version , , + ----------------------------------------- /( )` + \ \___ / | +$B$h$&$3$=(B FreeBSD $B$N(B 2.0.5 $B%j%j!<%9$X(B! 2.0R ($B$3$l$O(B /- _ `-/ ' +94 $BG/(B 11 $B7n$K%j%j!<%9$5$l$^$7$?(B) $B$H!"(B95 $BG/(B 7 $B7n=*$j(B (/\/ \ \ /\ +$B$4$m%j%j!<%9$5$l$kM=Dj$N(B 2.1R $B$H$N4V$rKd$a$k$?$a$K(B / / | ` \ +$BI,MW$H$5$l$?$?$a!"(B2.0.5 $B$O;CDjE*$K%j%j!<%9$5$l$^$7(B O O ) / | +$B$?!#(BFreeBSD 2.0.5 $B$O(B 2.0R $B$+$iB?$/$N=EMW$J2~NI$,9T(B `-^--'`< ' +$B$o$l$^$7$?!#$H$F$b0BDj$7$F$$$k(B ($B$+$J$j$NM>M5$r;}$C(B (_.) _ ) / +$B$F(B) $B$@$1$G$O$J$/!"$?$/$5$s$N?7$7$$FCD'$d$H$F$b3HD%(B `.___/` / +$B$5$l$?%$%s%9%H!<%k%W%m%0%i%`$b$"$j$^$9!#(B `-----' / +FreeBSD 2.0.5 $B$G?7$7$/$J$C$?ItJ,$K$D$$$F(B <----. __ / __ \ +$B$h$j>\$7$/$O!"%j%j!<%9%N!<%D$rFI$s$G$/$@(B <----|====O)))==) \) /==== +$B$5$$(B! <----' `--' `.__,' \ + | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +FreeBSD $B$C$F2?(B? FreeBSD $B$O(B 4.4 BSD Lite $B$r85$K$7!"(BIntel$B!"(BAMD$B!"(BCyrix$B!"(B +NexGen $B$J$I$N!V(Bx86$B!W%Y!<%9$N(B PC $B$GF0:n$9$k%*%Z%l!<%F%#%s%0%7%9%F%`$G$9!#(B +$BMM!9$J(B PC $BMQ<~JU5!4o$d9=@.$GF0:n$7!"%=%U%H%&%'%"3+H/$+$i(B Internet $B%5!<(B +$B%S%9Ds6!$^$G$"$i$f$k$3$H$K;HMQ$G$-$^$9!#(BInternet $B>e$N>&6HE*%5%$%H$G$"(B +$B$k(B ftp.cdrom.com $B$O(B FreeBSD $B%^%7%s$G$9(B! + +FreeBSD $B$N$3$N%j%j!<%9$G$O!"$3$&$$$C$?%7%9%F%`$r<B9T$9$k$?$a$KI,MW$JJ*(B +$BA4$F$,!"40A4$J%=!<%9%3!<%IIU$G4^$^$l$F$$$^$9!#%=!<%9%G%#%9%H%j%S%e!<%7%g(B +$B%s$r%$%s%9%H!<%k$9$l$P!"0l$D$N%3%^%s%I$G!"J8;zDL$jA4$F$N%7%9%F%`$r%3%s(B +$B%Q%$%k$7D>$9$3$H$,$G$-$^$9!#$3$l$O!"3X@8!"8&5f<T!"$b$7$/$O$I$&$d$C$FF0(B +$B:n$7$F$$$k$+$rCN$j$?$$?M$?$A$K$H$C$F$OM}A[E*$G$9!#(B + +$BEAE}E*$J(B UNIX $B%f!<%F%#%j%F%#!<$r<j$KF~$l!"(BFreeBSD $B$K%$%s%9%H!<%k$7$d$9(B +$B$$$h$&$K!"%5!<%I%Q!<%F%#!<$N0\?"$7$?%=%U%H%&%(%"$,$?$/$5$s=8$a$F$"$j$^(B +$B$9(B ("ports collection")$B!#(BEMACS $B%(%G%#%?$+$i(B lisp $B=hM}7O$^$G$NA4$F$r4^(B +$B$`(B 270 $B0J>e$N(B ports $B$K$h$C$F!"(BFreeBSD $B$O0lHLE*$J<BMQ@-$dG=NO$G$OB??t$N(B +$B%o!<%/%9%F!<%7%g%s$KI$E($9$k!"6/NO$GJq3gE*$J%*%Z%l!<%F%#%s%0%7%9%F%`$H(B +$B$J$C$F$$$^$9!#(B + + +$B$3$N%7%9%F%`$N$h$jB?$/$NJ8=q$K$D$$$F$O!"(BO'Reilly Associates and the +USENIX Associations $B$N(B 4.4BSD Document Set (ISBM 1-56592-082-1) $B$r9XF~(B +$B$7$F$/$@$5$$!#;dC#$O(B O'Reilly $B$H$O2?$N4X78$b$"$j$^$;$s!#;dC#$O$?$@8\5R(B +$B$H$7$FK~B-$7$F$$$k$@$1$G$9!#(B + +$B%$%s%9%H!<%k$r9T$&A0$K!"(BHARDWARE GUIDE $B$rFI$_$?$/$J$k$+$b$7$l$^$;$s!#(B +PC $B$r(B DOS/Windows ($B$3$l$i$O$"$^$j%O!<%I%&%'%"$rMW5a$7$^$;$s(B) $B0J30$N$?(B +$B$a$K@_Dj$9$k$N$O$o$j$HFq$7$$$3$H$G$9!#$b$7!"(BPC $B$N$3$H$OM}2r$7$F$$$k$H(B +$B;W$C$F$$$k$H$7$?$i!"$^$@==J,D9$/;H$C$F$J$$$C$F$3$H$G$9(B! :) $B$3$N%,%$%I(B +$B$K$O!"$I$s$J$U$&$K%O!<%I%&%'%"$r@_Dj$9$l$P$$$$$N$+!"%H%i%V%k$N>l9g$O$I(B +$B$s$JC{8u$r4Q;!$9$l$P$$$$$N$+$K$D$$$F$NHk7m$,$"$j$^$9!#$3$N%,%$%I$O!"(B +FreeBSD $B%V!<%H%U%m%C%T!<$N(B Documentation $B%a%K%e!<$K$"$j$^$9!#(B + +$BH]G'@<L@J8(B: FreeBSD $B$O;v8N$G%G!<%?$,$J$/$J$k$3$H$N$J$$$h$&!"%Y%9%H$r?T(B +$B$/$7$F$$$^$9$,!"%$%s%9%H!<%kCf$K%G%#%9%/A4BN$r>C$7$F$7$^$&2DG=@-$O0MA3(B +$B$H$7$FB8:_$7$^$9(B! $B:G=i$K=EMW$J%G!<%?$N%P%C%/%"%C%W$r$-$A$s$H$H$C$F$J$$(B +$B$J$i!":G8e$N(B FreeBSD $B%$%s%9%H!<%k%a%K%e!<$O<B9T$7$J$$$G$/$@$5$$(B! $B$A$c(B +$B$s$H8@$$$^$7$?$h(B! + +$B$3$N%j%j!<%9$K4X$9$k5;=QE*$J%3%a%s%H$O0J2<$KAw$C$F$/$@$5$$(B: + + hackers@FreeBSD.org + + +$B%P%0%l%]!<%H$O!"%7%9%F%`$r%$%s%9%H!<%k$G$-$?$J$i!V(Bsend-pr$B!W%3%^%s%I$r(B +$B;H$C$FAw$C$F$/$@$5$$!#$=$&$G$J$$$J$i!"0J2<$KAw$C$F$/$@$5$$(B: + + bugs@FreeBSD.org + +$B%P%0%l%]!<%H$G$O!"$I$N%P!<%8%g%s$N(B FreeBSD $B$r;H$C$F$$$k$N$+$rL@5-$9$k(B +$B$h$&5$$r$D$1$F$/$@$5$$!#(B + + +$B0lHLE*$J<ALd$O0J2<$KAw$C$F$/$@$5$$(B: + + questions@FreeBSD.org + +$B<ALd$KBP$9$k2sEz$,$9$0$KF@$i$l$J$/$F$b$,$^$s$7$F$/$@$5$$(B $B!=(B $B8=:_$O;dC#(B +$B$K$H$C$F$H$F$bK;$7$$;~$G$9$7!"%\%i%s%F%#%"C#$b8B3&$^$G$,$s$P$C$F$$$^$9(B! +send-pr $B%3%^%s%I$GDs=P$5$l$?%P%0%l%]!<%H$O%P%0%G!<%?%Y!<%9$K5-O?$5$l!"(B +$BDI@W$5$l$^$9!#$=$7$F!"$=$N%P%0(B ($B$^$?$O;EMM$K4X$9$kMW5a(B) $B$,B8:_$9$k4V$O(B +$B$"$i$f$k>uBV$NJQ99$,$"$J$?$KDLCN$5$l$^$9!#(B + +$B;dC#$N(B WEB $B%5%$%H$G$"$k(B http://www.freebsd.org $B$b!"99?7$5$l$?>pJs$N$h(B +$B$$>pJs85$G$9$7!"$?$/$5$s$N9bEY$JJ8=q$,MQ0U$5$l$F$$$^$9!#(BBSDI $BMQ$N(B +Netscape $B$r;HMQ$9$k$H!"(BWorld Wide Web $B$rD>@\(B FreeBSD $B$+$i1\Mw$G$-$^$9!#(B + +/usr/share/FAQ $B$d(B /usr/share/doc $B$K$O!"$5$i$K>pJs$,$"$j$^$9!#(B + + +$BFI$s$G$/$@$5$C$F$"$j$,$H$&!#$I$&$>$3$N%j%j!<%9$N(B FreeBSD $B$r$*$?$N$7$_(B +$B$/$@$5$$(B! + + Jordan Hubbard, + for The FreeBSD Project diff --git a/release/sysinstall/help/ja_JP.JIS/configure.hlp b/release/sysinstall/help/ja_JP.JIS/configure.hlp new file mode 100644 index 0000000..3860fb9 --- /dev/null +++ b/release/sysinstall/help/ja_JP.JIS/configure.hlp @@ -0,0 +1,13 @@ +$B$3$N%a%K%e!<$G$O!"%$%s%9%H!<%k8e$K%7%9%F%`$N@_Dj$r$7$^$9!#>/$J$/$H$b!"(B +$B%7%9%F%`4IM}<T$H%7%9%F%`$N%?%$%`%>!<%s$N@_Dj$O$7$F$/$@$5$$!#(B + +bash$B!"(Bemacs$B!"(Bpascal $B$J$I$N!"$5$i$J$kL%NOE*$JJ*$K$D$$$F$O!"$3$N%a%K%e!<(B +$B$N(B Package $B$N9`L\$r8+$F$/$@$5$$!#8=:_$N$H$3$m!"(BCD-ROM $B$r;}$C$F$$$k$+!"(B +$B%U%!%$%k%7%9%F%`>e$K%Q%C%1!<%8%3%l%/%7%g%s$r;}$C$F$$$k>l9g$N$_!"K\Ev$K(B +$BJXMx$G$"$k$H$$$&$3$H$r3P$($F$*$$$F$/$@$5$$!#%Q%C%1!<%8$r<+F0E*$K(B FTP +$B$GE>Aw$7$F$/$k5!G=$O$^$@$"$j$^$;$s!#(B + +$B%7%9%F%`$N%$%s%9%H!<%k$,=*$C$?8e$G!"%Q%C%1!<%8$r%$%s%9%H!<%k$9$k%D!<%k(B +$B$rF0$+$9$K$O!"!V(Bpkg_manage$B!W$H$$$&%3%^%s%I$r;HMQ$7$^$9!#%?%$%`%>!<%s$r(B +$B;XDj$9$k$K$O!V(Btzsetup$B!W$HF~NO$7$F$/$@$5$$!#$3$l0J>e$N0lHLE*$J%7%9%F%`(B +$B$N@_Dj$K4X$9$k>pJs$K$D$$$F$O!"!V(B/etc/sysconfig$B!W%U%!%$%k$r8+$F$/$@$5$$!#(B diff --git a/release/sysinstall/help/ja_JP.JIS/language.hlp b/release/sysinstall/help/ja_JP.JIS/language.hlp new file mode 100644 index 0000000..9871dbb --- /dev/null +++ b/release/sysinstall/help/ja_JP.JIS/language.hlp @@ -0,0 +1,12 @@ +$B9%$_$N8@8l$rA*Br$9$k$K$O!"$3$N%a%K%e!<$r;HMQ$7$F$/$@$5$$!#8=:_$N$H$3$m!"(B +$BMM!9$J%X%k%W$G;HMQ$5$l$k%G%U%)%k%H$N8@8l$r@_Dj$9$k$@$1$G$9!#(B + +$B>-Mh$N%j%j!<%9$G$O!"$3$N%a%K%e!<$K$h$C$F%-!<%\!<%I%l%$%"%&%H!"%9%/%j!<(B +$B%s%^%C%W!"(BNLS $B$N@_Dj(B (sysinstall $B<+BN$bA4$F$N%a%K%e!<$rE,@Z$J8@8l$GI=(B +$B<($9$k$N$K!"%a%C%;!<%8%+%?%m%0$r;HMQ$9$k$h$&$K$J$j$^$9(B)$B!"$=$7$FMM!9$J(B +$BI8=`$KE,9g$5$;$k$?$a$N$=$NB>$N9q:]2=5!G=$rJQ99$7$^$9!#(B + +$B$3$l$i$N2~NI$,9T$o$l$k$^$G$O!"%7%9%F%`$,A4$F%$%s%9%H!<%k$5$l$?8e$G(B +/etc/sysconfig $B$rJT=8$9$k$N$,4JC1$G$7$g$&!#$3$N%U%!%$%k$K$O!"JQ99$9$k(B +$B$Y$-ItJ,$K$D$$$F$N$?$/$5$s$N%3%a%s%H$d!"1Q8l0J30$N8@8l$N@_Dj$K4X$9$k$$(B +$B$/$D$+$NNc$,$"$j$^$9!#(B diff --git a/release/sysinstall/help/ja_JP.JIS/usage.hlp b/release/sysinstall/help/ja_JP.JIS/usage.hlp new file mode 100644 index 0000000..a3b6871 --- /dev/null +++ b/release/sysinstall/help/ja_JP.JIS/usage.hlp @@ -0,0 +1,50 @@ +$B$3$N%7%9%F%`$N;H$$J}(B +==================== + +$B%-!<(B $B%"%/%7%g%s(B +---- ---------- +UP ARROW $BA0$N9`L\(B ($B%F%-%9%H%U%#!<%k%I$G$O>e(B) $B$K0\F0$7$^$9!#(B +DOWN ARROW $B<!$N9`L\(B ($B%F%-%9%H%U%#!<%k%I$G$O2<(B) $B$K0\F0$7$^$9!#(B +TAB $B<!$N9`L\$^$?$O%0%k!<%W$K0\F0$7$^$9!#(B +RIGHT ARROW $B<!$N9`L\$^$?$O%0%k!<%W$K0\F0$7$^$9!#(B(TAB $B$HF1$8(B) +SHIFT-TAB $BA0$N9`L\$^$?$O%0%k!<%W$K0\F0$7$^$9!#(B +LEFT ARROW $BA0$N9`L\$^$?$O%0%k!<%W$K0\F0$7$^$9!#(B(SHIFT-TAB $B$HF1$8(B) +RETURN $B9`L\$rA*Br$7$^$9!#(B +PAGE UP $B%F%-%9%H%\%C%/%9$G!"A0$N%Z!<%8$KLa$j$^$9!#(B +PAGE DOWN $B%F%-%9%H%\%C%/%9$G!"<!$N%Z!<%8$K?J$_$^$9!#(B +SPACE $B!V%i%8%*%\%?%s!W$dJ#?t$NA*Br;h$,$"$k%a%K%e!<$G!"8=:_$N(B + $B9`L\$r%H%0%k$7$^$9!#(B +F1 ($BB8:_$9$k2hLL$G$O(B) $B%X%k%W$rI=<($7$^$9!#(B + +$B%a%K%e!<$NC<$K!V(B^(-)$B!W$+!V(Bv(+)$B!W$H$$$&5-9f$,$"$k>l9g$O!"(B($B2hLL$N%9%Z!<(B +$B%9$,IT==J,$J$?$a(B) $BI=<($7$-$l$J$$9`L\$,B8:_$7$^$9(B $B!#>e2<%+!<%=%k%-!<$r(B +$B;HMQ$7$F%a%K%e!<$r%9%/%m!<%k$5$;$F$/$@$5$$!#$I$A$i$+$N5-9f$,>C$($?;~$O!"(B +$B%a%K%e!<$N@hF,(B ($B$^$?$O:G8e(B) $B$G$9!#(B + +$B%F%-%9%H%U%#!<%k%I$G$O!"8=:_$N%F%-%9%H$N0LCV$,1&2<$K%Q!<%;%s%HI=<($5$l(B +$B$^$9!#%U%#!<%k%I$N:G8e$G$O(B 100% $B$HI=<($5$l$^$9!#(B + +OK $B$rA*Br$9$k$H!"8=:_$NF0:n$r3NG'$9$k$3$H$K$J$j$^$9!#(BCancel $B$rA*Br$9$k(B +$B$H!"8=:_$NA`:n$r%-%c%s%;%k$7!"0JA0$N%a%K%e!<$KLa$j$^$9!#(B + + +$BFCJL$J5!G=(B: +=========== + +$B%a%K%e!<$N9`L\$rA*Br$9$k$N$K!":G=i$NJ8;z$rF~NO$9$k$3$H$b$G$-$^$9(B ($B0l0U(B +$B$KDj$^$k>l9g(B)$B!#$3$N$h$&$J!V%"%/%;%i%l!<%?!WJ8;z$O%O%$%i%$%H$GI=<($5$l(B +$B$^$9!#(B + +$B%3%s%=!<%k%I%i%$%P$O!"%9%/%m!<%k$7$F9T$C$?2hLL$r$b$&0lEYI=<($9$k$?$a$N(B +$B%9%/%m!<%k%P%C%/%P%C%U%!$r;}$C$F$$$^$9!#%9%/%m!<%k%P%C%/$9$k$K$O!"(B +$B!V(BScroll Lock$B!W%-!<$r2!$7$F$+$i%+!<%=%k%-!<$d!V(BPage Up$B!W!V(BPage Down$B!W(B +$B%-!<$r;HMQ$7$^$9!#%9%/%m!<%k%P%C%/%b!<%I$+$iH4$1$k$K$O!":FEY!V(BScroll +Lock$B!W%-!<$r2!$7$^$9!#$3$N5!G=$O%5%V%7%'%k$d$=$NB>$N!V%&%$%6!<%I%b!<%I!W(B +$B$J$I!"%a%K%e!<$r;HMQ$7$J$$>l9g$KJXMx$G$9!#(B + +$B%7%9%F%`$N%$%s%9%H!<%k$,=*N;$7!"!V%^%k%A%f!<%6!<!W$GF0:n$7$F$$$k;~$O!"(B +$BF1;~$K$$$/$D$+$N%;%C%7%g%s$r07$($k!V2>A[%3%s%=!<%k!W$r;HMQ$9$k$3$H$,$G(B +$B$-$^$9!#%3%s%=!<%k$r@ZBX$($k$K$O!"(BALT-F<n> $B$r;HMQ$7$F$/$@$5$$!#!V(BF<n>$B!W(B +$B$O8+$?$$2hLL$KBP1~$9$k%U%!%s%/%7%g%s%-!<$G$9!#I8=`$G$O(B 3 $B$D$N2>A[%3%s(B +$B%=!<%k$,;HMQ$G$-$^$9$,!"%U%!%$%k(B /etc/ttys $B$rJT=8$9$k$3$H$G:GBg(B 12 $B8D(B +$B$^$GA}$d$9$3$H$,$G$-$^$9!#(B diff --git a/release/sysinstall/help/ja_JP.ROMAJI/README b/release/sysinstall/help/ja_JP.ROMAJI/README new file mode 100644 index 0000000..53b4357 --- /dev/null +++ b/release/sysinstall/help/ja_JP.ROMAJI/README @@ -0,0 +1,105 @@ + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Version , , + ----------------------------------------- /( )` + \ \___ / | +youkoso FreeBSD no 2.0.5 release he! 2.0R (koreha /- _ `-/ ' +94 nen 11 gatsu ni release saremashita) to, 95 nen (/\/ \ \ /\ +7 gatsu owari goro release sareru yotei no 2.1R to / / | ` \ +no aida wo umeru tameni hitsuyou to saretatame, O O ) / | +2.0.5 ha zantei teki ni release saremashita. `-^--'`< ' +FreeBSD 2.0.5 ha 2.0R kara ooku no juuyou na (_.) _ ) / +kairyou ga okonawaremashita. totemo antei shiteiru `.___/` / +(kanari no yoyuu wo motte) dakedenaku, `-----' / +takusan no atarashii tokuchou ya totemo <----. __ / __ \ +kakuchou sareta install program mo <----|====O)))==) \) /==== +arimasu. FreeBSD 2.0.5 de atarashiku <----' `--' `.__,' \ +natta bubun ni tsuite yori kuwashikuha, | | +release notes wo yonde kudasai! \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +FreeBSD tte nani? FreeBSD ha 4.4 BSD Lite wo motoni shi, Intel, AMD, +Cyrix, NexGen nadono "x86" base no PC de dousasuru operating system +desu. samazama na PC you shuuhen kiki ya kousei de dousa si, software +kaihatsu kara Internet service teikyou made arayurukotoni shiyou +dekimasu. Internet jou no shougyou teki site de aru ftp.cdrom.com ha +FreeBSD machine desu! + +FreeBSD no kono release deha, kouitta system wo jikkou suru tameni +hitsuyouna mono subete ga, kanzen na source code tsuki de fukumarete +imasu. source distribution wo install sureba, hitotsu no command de, +moji doori subeteno system wo compile shinaosu kotoga dekimasu. +koreha, gakusei, kenkyuusya, moshikuha douyatte dousa shiteirukawo +shiritai hitotachini totteha risoutekidesu. + +dentou teki na UNIX utility wo teniire, FreeBSD ni install shiyasui +youni, third party no ishoku shita software ga takusan atumete arimasu +("ports collection"). EMACS editor kara lisp shorikei madeno subetewo +fukumu 270 ijou no ports ni yotte, FreeBSD ha ippantekina jitsuyousei +ya nouryokudeha, tasuu no workstation ni hitteki suru, kyouryoku de +houkatsuteki na operating system to natte imasu. + + +kono system no yori ookuno bunsyo ni tsuiteha, O'Reilly Associates and +the USENIX Associations no 4.4BSD Document Set (ISBN 1-56592-082-1) wo +kounyuu shitekudasai. watashitachi ha O'Reilly toha nan'no kankei mo +arimasen. watashitachi ha tada kokyaku toshite manzoku shiteiru +dakedesu. + +install wo okonau maeni, HARDWARE GUIDE wo yomitaku narukamo +shiremasen. PC wo DOS/Windows (koreraha amari hardware wo youkyuu +shimasen) igai no tameni settei surunoha warito muzukashii kotodesu. +moshi, PC no kotoha rikai shiteiru to omotteiru toshitara, mada juubun +nagaku tsukattenai tte kotodesu! :) kono guide niha, dn'na fuuni +hardware wo settei surebaiinoka, trouble no baai ha don'na choukou wo +kansatsu sureba iinoka ni tsuiteno hiketsuga arimasu. kono guide ha, +FreeBSD boot floppy no Documentation menu ni arimasu. + +HININ SEIMEN BUN: FreeBSD ha jiko de data ga nakunaru kotono naiyou, +best wo tsukushite imasuga, install chuu ni disk zentai wo +keshiteshimau kanousei ha izentoshite sonzai shimasu! saisho ni +juuyou na data no backup wo kichinto totte inainara, saigono FreeBSD +install menu ha jikkou shinaide kudasai! chanto iimashita yo! + +kono release ni kansuru gijutsuteki na commento ha ika ni okutte +kudasai: + + hackers@FreeBSD.org + + +bug report ha, system wo install dekitanara `send-pr' command wo +tsukatte okutte kudasai. soude nai nara, ika ni okutte kudasai: + + bugs@FreeBSD.org + +bug report deha, dono version no FreeBSD wo tsukatte irunokawo meiki +suruyou ki wo tsukete kudasai. + + +ippan teki na shitsumon ha ika ni okutte kudasai: + + questions@FreeBSD.org + +shitsumon ni taisuru kaitou ga suguni erarenakutemo gaman shite +kudasai - genzai ha watashi tachi ni tottemo isogashii toki desushi, +volunteer tachi mo genkai made ganbatte imasu! send-pr command de +teishutsu sareta bug report ha bug database ni kirokusare, tsuiseki +saremasu. soshite, sono bug (mataha shiyou ni kansuru youkyuu) ga +sonzai suru aidaha arayuru joutai no henkou ga anatani tsuuchi +saremasu. + +watashi tachi no WEB site de aru http://www.freebsd.org mo, koushin +sareta jouhou no yoi jouhougen desusi, takusan no koudo na bunsyo ga +youi sarete imasu. BSDI you no Netscape wo shiyou suruto, World Wide +Web wo chokusetsu FreeBSD kara etsuran dekimasu. + +/usr/share/FAQ ya /usr/share/doc niha, sarani jouhou ga arimasu. + + +yonde kudasatte arigatou. douzo kono release no FreeBSD wo otanoshimi +kudasai! + + Jordan Hubbard, + for The FreeBSD Project diff --git a/release/sysinstall/help/ja_JP.ROMAJI/configure.hlp b/release/sysinstall/help/ja_JP.ROMAJI/configure.hlp new file mode 100644 index 0000000..c152796 --- /dev/null +++ b/release/sysinstall/help/ja_JP.ROMAJI/configure.hlp @@ -0,0 +1,16 @@ +kono menu deha, install go ni system no settei wo shimasu. +sukunakutomo, system kanrisha to system no time zone no settei ha +shite kudasai. + +bash, emacs, pascal nadono, saranaru miryokuteki na mono ni tsuiteha, +kono menu no Package no koumoku wo mite kudasai. genzai no tokoro, +CD-ROM wo motteiruka, file system jou ni package collection wo +motteiru baai nomi, hontouni benridearu toiukotowo oboete oite +kduasai. package wo jidouteki ni FTP de tensou shitekuru kinou ha +mada arimasen. + +system no install ga owatta atode, package wo install suru tool wo +ugokasu niha, ``pkg_manage'' toiu command wo shiyou shimasu. time +zone wo shitei suruniha ``tzsetup'' to nyuuryoku shitekudasai. kore +ijou no ippanteki na system no settei ni kansuru jouhou ni tsuiteha, +``/etc/sysconfig'' file wo mite kudasai. diff --git a/release/sysinstall/help/ja_JP.ROMAJI/language.hlp b/release/sysinstall/help/ja_JP.ROMAJI/language.hlp new file mode 100644 index 0000000..a167099 --- /dev/null +++ b/release/sysinstall/help/ja_JP.ROMAJI/language.hlp @@ -0,0 +1,14 @@ +konomi no gengo wo sentaku suruniha, kono menu wo shiyou shite +kduasai. genzai no tokoro, samazama na help de shiyou sareru default +no gengo wo settei surudakedesu. + +shourai no release deha, kono menu ni yotte keyboard layout, screen +map, NLS no settei (sysinstall jitai mo subete no menu wo tekisetsu na +gengo de hyouji surunoni, message catalog wo shiyou suruyouni +narimasu), soshite samazamana hyoujun ni tekigou saseru tameno +sonohokano kokusaika kinou wo henkou shimasu. + +korerano kairyou ga okonawareru madeha, system ga subete install +sareta atode /etc/sysconfig wo henshuu surunoga kantan deshou. kono +file niha, henkou surubeki bubun ni tsuiteno takusan no comment ya, +eigo igai no gengo no settei ni kansuru ikutsukano reiga arimasu. diff --git a/release/sysinstall/help/ja_JP.ROMAJI/usage.hlp b/release/sysinstall/help/ja_JP.ROMAJI/usage.hlp new file mode 100644 index 0000000..df58c20 --- /dev/null +++ b/release/sysinstall/help/ja_JP.ROMAJI/usage.hlp @@ -0,0 +1,52 @@ +KONO SYSTEM NO TSUKAIKATA +========================= + +KEY ACTION +--- ------ +UP ARROW mae no koumoku (text field deha ue) ni idou shimasu. +DOWN ARROW tsugi no koumoku (text field deha shita) ni idou shimasu. +TAB tsugi no koumoku mataha group ni idou shimasu. +RIGHT ARROW tsugi no koumoku mataha group ni idou shimasu (TAB to onaji). +SHIFT-TAB mae no koumoku mataha group ni idou shimasu. +LEFT ARROW mae no koumoku mataha group ni idou shimasu. (SHIFT-TAB to + onaji). +RETURN koumoku wo sentaku shimasu. +PAGE UP text box de, mae no page ni modorimasu. +PAGE DOWN text box de, tsugi no page ni susumimasu. +SPACE "radio button" ya fukusuu no sentakushi ga aru menu de, + genzai no koumoku wo toggle shimasu. +F1 (sonzai suru gamen deha) help wo hyouji shimasu. + +menu no hashi ni "^(-)" ka "v(+)" to iu kigou ga aru baai ha, (gamen no +space ga fujuubun na tame) hyouji shikirenai koumoku ga sonzai shimasu. +jou-ge cursor key wo shiyou shite menu wo scroll sasete kudasai. +dochirakano kigou ga kieta toki ha, menu no sentou (mataha saigo) desu. + +text field deha, genzai no text no ichi ga migi-shita ni percent +hyouji saremasu. field no saigo deha 100% to hyouji saremasu. + +OK wo sentaku suruto, genzai no dousa wo kakunin surukotoni narimasu. +Cancel wo sentaku suruto, genzai no sousa wo cancel shi, izen no menu ni +modorimasu. + + +TOKUBETU NA KINOU: +================== + +menu no koumoku wo sentaku surunoni, saisho no moji wo nyuuryoku +surukotomo dekimasu (ichi-i ni sadamaru baai). konoyouna "accellerator" +moji ha highlight de hyouji saremasu. + +console driver ha, scroll shiteitta gamen wo mouichido hyouji surutameno +scroll-back buffer wo motteimasu. scroll-back surutameniha, "Scroll +Lock" key wo oshitekara cursor key ya "Page Up" "Page Down" key wo +shiyou shimasu. kono kinou ha sub-shell ya sonohokano "wizard mode" +nado, menu wo shiyou shinai baai ni benridesu. + +system no install ga shuuryou shi, "multi-user" de dousa shiteiru +tokiha, douji ni ikutsukano session wo atsukaeru "kasou console" wo +shiyou surukotoga dekimasu. console wo kirikaeruniha, ALT-F<n> wo +shiyou shitekudasai. 'F<n>' ha mitai gamen ni taiousuru function key +desu. hyoujun deha 3tsuno kasou console ga shiyou dekimasuga, file +/etc/ttys wo henshuu surukotode saidai 12ko made fuyasukotoga +dekimasu. diff --git a/release/sysinstall/help/media.hlp b/release/sysinstall/help/media.hlp new file mode 100644 index 0000000..8b081bc --- /dev/null +++ b/release/sysinstall/help/media.hlp @@ -0,0 +1,29 @@ +You can install from the following types of media: + + CDROM - requires one of the following supported CDROM drives: + + Sony CDU 31/33A + Matushita/Panasonic "Sound Blaster" CDROM. + Mitsumi FX-001{A-D} (older non-IDE drives). + SCSI - Any standard SCSI CDROM drive hooked to + a supported controller (see Hardware Guide). + + DOS - A DOS primary partition with the required FreeBSD + distribution files copied onto it (e.g. C:\FREEBSD\) + + FS - Assuming a disk or partition with an existing + FreeBSD file system and distribution set on it, + get the distribution files from there. + + Floppy - Get distribution files from one or more DOS formatted + floppies. + + FTP - Get the distribution files from an anonymous ftp server + (you will be presented with a list). + + NFS - Get the distribution files from an NFS server somewhere + (make sure that permissions on the server allow this!) + + Tape - Extract distribution files from tape into a temporary + directory and install from there. + diff --git a/release/sysinstall/help/network_device.hlp b/release/sysinstall/help/network_device.hlp new file mode 100644 index 0000000..95c42ae --- /dev/null +++ b/release/sysinstall/help/network_device.hlp @@ -0,0 +1,54 @@ +You can do network installations over 3 types of communications links: + + Serial port: SLIP / PPP + Parallel port: PLIP (laplink cable) + Ethernet: A standard ethernet controller (includes some PCMCIA). + +SLIP support is rather primitive and limited primarily to hard-wired +links, such as a serial cable running between a laptop computer and +another PC. The link must be hard-wired as the SLIP installation +doesn't currently offer a dialing capability; that facility is provided +with the PPP utility, which should be used in preference to SLIP +whenever possible. When you choose a serial port device, you'll +be given the option later to edit the slattach command before it's +run on the serial line. It is expected that you'll run slattach +(or some equivalent) on the other end of the link at this time and +bring up the line. FreeBSD will then install itself over the link +at speeds of up to 115.2K/baud (the recommended speed for a hardwired +cable). + +If you're using a modem then PPP is almost certainly your only +choice. Make sure that you have your service provider's information +handy as you'll need to know it fairly early in the installation +process. You will need to know, at the minimum, your service +provider's IP address and possibly your own (though you can also leave +it blank and allow PPP to negotiate it with your ISP). You will also +need to know how to use the various "AT commands" to dial the ISP with +your particular brand of modem as the PPP dialer provides only a very +simple terminal emulator and has no "modem capabilities database". + +If a hard-wired connection to another FreeBSD (2.0R or later) machine +is available, you might also consider installing over a "laplink" +parallel port cable. The data rate over the parallel port is much +higher than what is typically possible over a serial line with +speeds of up to 50k/sec. + +Finally, for the fastest possible network installation, an ethernet +adaptor is always a good choice! FreeBSD supports most common PC +ethernet cards, a table of which is provided in the FreeBSD +Hardware Guide (see the Documentation menu on the boot floppy). +If you are using one of the supported PCMCIA ethernet cards, also be +sure that it's plugged in _before_ the laptop is powered on! FreeBSD +does not, unfortunately, currently support "hot insertion" of PCMCIA +cards. + +You will also need to know your IP address on the network, the "netmask" +value for your address class, and the name of your machine. +Your system administrator can tell you which values to use for your +particular network setup. If you will be referring to other hosts by +name rather than IP address, you'll also need a name server and +possibly the address of a gateway (if you're using PPP, it's your +provider's IP address) to use in talking to it. If you do not know +the answers to all or most of these questions, then you should +really probably talk to your system administrator _first_ before +trying this type of installation! diff --git a/release/sysinstall/help/nl_NL.ISO8859-1/README b/release/sysinstall/help/nl_NL.ISO8859-1/README new file mode 100644 index 0000000..35c2c90 --- /dev/null +++ b/release/sysinstall/help/nl_NL.ISO8859-1/README @@ -0,0 +1,106 @@ + + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Versie , , + ----------------------------------------- /( )` + \ \___ / | +Welkom bij de 2.0.5 release van FreeBSD! 2.0.5 is /- _ `-/ ' +een interim release, die de leemte moet vullen die (/\/ \ \ /\ +onstaan is sinds de laatste release van FreeBSD, / / | ` \ +versie 2.0 in Nov 94, tot de release van FreeBSD, O O ) / | +2.1, verwacht eind juli 95. FreeBSD 2.0.5 bevat `-^--'`< ' +veel substantiële verbeteringen ten opzichte van (_.) _ ) / +2.0R, niet in de laatste plaats de aanzienlijk `.___/` / +verbeterde stabiliteit, vele nieuwe `-----' / +features en een sterk verbeterd <----. __ / __ \ +installatie programma. Zie ook de <----|====O)))==) \) /==== +'release notes' voor meer details m.b.t. <----' `--' `.__,' \ +tot wat nieuw is in FreeBSD 2.0.5 | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + +Wat is FreeBSD? FreeBSD is een operating systeem, gebaseerd op +4.4 BSD Lite for Intel, AMD, Cyrix of NexGen "x86" gebaseerde PC +hardware. Het werkt met een uitgebreide keuze aan PC randapparatuur +en configuraties en kan gebruikt worden voor de meest uiteenlopende +activiteiten, van programma ontwikkeling tot Internet Service +Voorziening; de drukste machine op het Internet, ftp.cdrom.com, +is een FreeBSD machine. + +Deze release van FreeBSD bevat alles wat u nodig heeft om zo'n +systeem te draaien, met de volledige broncode voor elk onderdeel +van het systeem. Als de broncode distributie geïnstalleerd is +kunt u letterlijk, met één kommando het volledige systeem +opnieuw compileren. Hierdoor is het ideaal voor studenten, +researchers of voor iedereen die gewoon wil zien hoe het allemaal +werkt. + +Een grote verzameling extra software, overgezet op FreeBSD (de +"ports" verzameling) wordt ook beschikbaar gesteld, om het +makkelijker te maken om al uw favoriete traditionele UNIX +utilities te installeren. +Meer dan 270 "ports", die software omvatten van tekstverwerkers +tot programmeertalen, maken van FreeBSD een krachtige +en veelomvattende operating omgeving die kan concureren met die +van veel grote werkstations op het gebied van algemene inzet- +baarheid en verwerkingskracht. + +Om meer documentatie over dit systeem te verkrijgen, is het aan- +bevolen om de '4.4BSD Document Set' te kopen van O'Reilly Associates +en de USENIX Association, ISBN 1-56592-082-1. We hebben niets +met O'Reilly te maken, maar zijn slechts tevreden klanten! + +Voordat u verder gaat met de installatie is het aan te bevelen +*eerst* de 'HARDWARE GUIDE' te lezen. PC hardware configuren voor +iets anders dan DOS/Windows (die de hardware niet zo erg belasten) +is wat moeilijker dan het lijkt, en als u denkt dat u PC's begrijpt +dan heeft u ze duidelijk nog niet lang genoeg gebruikt :) +De 'HARDWARE GUIDE' geeft u wat tips om uw hardware te configureren +en op welke symptomen te letten als er problemen zijn. Deze gids is +aanwezig in het Documentatie menu van de FreeBSD start-diskette. + +Ofschoon FreeBSD zijn uiterste best doet om te hoeden voor +gegevensverlies, is het nog steeds meer dan mogelijk om AL UW +GEGEVENS OP UW HARDDISK KWIJT TE RAKEN met deze installatie. Ga +niet verder met installatiemenu voordat er van alle belangrijke +gegevens een backup is gemaakt! + +Technisch commentaar op deze release moet gestuurd worden naar: + + hackers@FreeBSD.org + +Meldingen van gevonden fouten in FreeBSD moeten gestuurd worden +met het 'send-pr' kommando als u er in geslaagd bent om het +systeem te installeren, anders naar: + + bugs@FreeBSD.org + +Vermeld duidelijk om WELKE VERSIE van FreeBSD het gaat in berichten +over fouten. + +Algemene vragen kunnen gestuurd worden naar: + + questions@FreeBSD.org + +Heb een beetje geduld als uw vraag niet meteen beantwoord wordt - +we hebben het erg druk op het moment, en ons vrijwilligers werk +belast ons vaak tot aan de limiet. Foutmeldingen die verstuurd zijn +m.b.v. 'send-pr' worden opgeslagen en bijgehouden in onze +'bug'-database. U wordt geïnformeerd over de veranderingen in de +status van de fout (of vraag naar een feature) tijdens de levensduur +ervan. + +Onze WEB server, http://www.freebsd.org, is een goede bron voor +nieuwe of bijgewerkte informatie en biedt ook een aantal geavan- +ceerde documentatie faciliteiten. U kunt de BSDI versie van +Netscape gebruiken om over het 'World Wide Web' te 'surfen'. + +Zie ook /usr/share/FAQ en /usr/share/doc voor informatie over +het systeem. + +Bedankt voor het lezen en we hopen dat deze release van FreeBSD +u goed bevalt. + + Jordan Hubbard, + voor het FreeBSD project diff --git a/release/sysinstall/help/nl_NL.ISO8859-1/configure.hlp b/release/sysinstall/help/nl_NL.ISO8859-1/configure.hlp new file mode 100644 index 0000000..91c39f5 --- /dev/null +++ b/release/sysinstall/help/nl_NL.ISO8859-1/configure.hlp @@ -0,0 +1,16 @@ +Dit menu stelt u in staat om uw systeem tot op zekere hoogte +te configureren na de installatie. In ieder geval kunt u hiermee +het wachtwoord van de systeembeheerder en de tijdzone instellen. + +Voor extra programmatuur zoals bash, emacs, pascal, etc. is het +aan te raden naar het 'Packages' item te kijken in dit menu. Op +het moment is het helaas alleen bruikbaar als u een CDROM heeft of +ergens op uw harddisk packages heeft staan waar het package +installatie programma erbij kan. Automatische overdracht van +packages via FTP wordt nog niet ondersteund. + +Als u na de installatie het packages installatie programma opnieuw +wilt gebruiken kunt u dit oproepen door het kommando 'pkg_manage'. +Om de tijdzone te veranderen kunt u 'tzsetup' gebruiken. Voor +meer informatie over algemene systeem configuratie zie het bestand +'/etc/sysconfig'. diff --git a/release/sysinstall/help/nl_NL.ISO8859-1/language.hlp b/release/sysinstall/help/nl_NL.ISO8859-1/language.hlp new file mode 100644 index 0000000..48fac09 --- /dev/null +++ b/release/sysinstall/help/nl_NL.ISO8859-1/language.hlp @@ -0,0 +1,15 @@ +Met dit menu kunt u een andere taal selecteren. Op het moment worden +alleen de help bestanden in de gekozen taal weergegeven. + +In een volgende release zal ook de toetsenbord layout, scherm +aansturing, NLS instellingen ('sysinstall' zelf zal ook 'message +catalogs' gebruiken zodat alle menu's in de gekozen taal worden +weergegeven) veranderd worden en andere I18N instellingen om +aan diverse standaarden te voldoen. + +Totdat deze verbeteringen zijn doorgevoerd kunt u het beste deze +veranderingen zelf aan te brengen door het bestand '/etc/sysconfig' +te bewerken nadat het systeem is geïnstalleerd. Er is commentaar +in het bestand aanwezig dat aangeeft wat er verander moet worden. +Er zijn ook wat voorbeelden van niet-Engelse configuraties. + diff --git a/release/sysinstall/help/nl_NL.ISO8859-1/usage.hlp b/release/sysinstall/help/nl_NL.ISO8859-1/usage.hlp new file mode 100644 index 0000000..50a2808 --- /dev/null +++ b/release/sysinstall/help/nl_NL.ISO8859-1/usage.hlp @@ -0,0 +1,56 @@ +GEBRUIKSINSTRUCTIES VOOR DIT SYSTEEM +==================================== + +TOETS AKTIE +===== ===== +PIJL OMHOOG Ga naar het vorige item (of omhoog in een tekst veld) +PIJL OMLAAG Ga naar het volgende item (of omlaag, in een tekst veld) +TAB Ga naar het volgende item of groep +PIJL RECHTS Ga naar het volgende item of groep (hetzelfde als TAB) +SHIFT-TAB Ga naar het vorige item of groep +PIJL LINKS Ga naar het vorige item of groep (hetzelfde als SHIFT-TAB) +RETURN Selecteer item +PAGE UP Ga een pagina omhoog in tekst vensters +PAGE DOWN Ga een pagina omlaag in tekst vensters +SPATIEBALK Selecteer/deselecteer het huidige item in "radio" of + multiple choice menus. +F1 Help (indien het huidige scherm er in voorziet) + +Als er meer menu-items zijn dan getoond kunnen worden, verschijnen er +symbolen om aan te geven of dit aan de bovenkant is: "^(-)" of aan de +onderkant "v(+)". Gebruik de PIJL OMHOOG/OMLAAG toetsen om te bladeren. +Als een van de symbolen verdwijnt dan ben je aan de onderkant +(of bovenkant) van het menu. + +In tekst vensters wordt de hoeveelheid tekst die nog getoond moet +worden als een percentage weergegeven in de rechter onderhoek. 100% +betekent dat je het einde van de tekst hebt bereikt. + +Selektie van <OK> in een menu bevestigt de aktie die erdoor gekontro- +leerd wordt. Selektie van <Cancel> annuleert de aktie en zal je over +het algemeen terugbrengen in het vorige menu. + +SPECIALE MOGELIJKHEDEN +====================== + +Het is ook mogelijk om een menu item te selekteren door de eerste +letter (of cijfer) van de naam te typen, als deze uniek is. Deze +letters (of cijfers) zijn vetgedrukt (of in een andere kleur weer- +gegeven) om ze te onderscheiden. + +Het is ook mogelijk om terug te bladeren als er regels aan de +bovenkant van het scherm zijn gerold. Deze 'terug-blader-modus' +kan geaktiveerd worden door op de "Scroll Lock" toets te drukken. +Nu kun je m.b.v. PIJL OMHOOG/OMLAAG of Page Up/Page Down door de +bewaarde regels bladeren. Druk nogmaals op "Scroll Lock" om deze +modus te beëindigen. Deze mogelijkheid is erg handig als je in een +sub-shell zit of andere expert-modes gebruikt die geen menus +hebben. + +Na installatie, en als het systeem in "multi-user" mode draait, kun +je gebruik maken van "virtuele consoles" om meerdere aktieve +sessies tegelijk te kunnen gebruiken. Gebruik ALT-F<n> om tussen de +verschillende sessies te wisselen, 'F<n>' is de funktietoets die +overeenkomt met de sessie die je wilt zien. Standaard is het +systeem geconfigureerd voor 4 virtuele consoles. Bewerk /etc/ttys +om meer virtuele consoles te configureren. Het maximum aantal is 12. diff --git a/release/sysinstall/help/nl_NL.ISO_8859-1/README b/release/sysinstall/help/nl_NL.ISO_8859-1/README new file mode 100644 index 0000000..35c2c90 --- /dev/null +++ b/release/sysinstall/help/nl_NL.ISO_8859-1/README @@ -0,0 +1,106 @@ + + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Versie , , + ----------------------------------------- /( )` + \ \___ / | +Welkom bij de 2.0.5 release van FreeBSD! 2.0.5 is /- _ `-/ ' +een interim release, die de leemte moet vullen die (/\/ \ \ /\ +onstaan is sinds de laatste release van FreeBSD, / / | ` \ +versie 2.0 in Nov 94, tot de release van FreeBSD, O O ) / | +2.1, verwacht eind juli 95. FreeBSD 2.0.5 bevat `-^--'`< ' +veel substantiële verbeteringen ten opzichte van (_.) _ ) / +2.0R, niet in de laatste plaats de aanzienlijk `.___/` / +verbeterde stabiliteit, vele nieuwe `-----' / +features en een sterk verbeterd <----. __ / __ \ +installatie programma. Zie ook de <----|====O)))==) \) /==== +'release notes' voor meer details m.b.t. <----' `--' `.__,' \ +tot wat nieuw is in FreeBSD 2.0.5 | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + +Wat is FreeBSD? FreeBSD is een operating systeem, gebaseerd op +4.4 BSD Lite for Intel, AMD, Cyrix of NexGen "x86" gebaseerde PC +hardware. Het werkt met een uitgebreide keuze aan PC randapparatuur +en configuraties en kan gebruikt worden voor de meest uiteenlopende +activiteiten, van programma ontwikkeling tot Internet Service +Voorziening; de drukste machine op het Internet, ftp.cdrom.com, +is een FreeBSD machine. + +Deze release van FreeBSD bevat alles wat u nodig heeft om zo'n +systeem te draaien, met de volledige broncode voor elk onderdeel +van het systeem. Als de broncode distributie geïnstalleerd is +kunt u letterlijk, met één kommando het volledige systeem +opnieuw compileren. Hierdoor is het ideaal voor studenten, +researchers of voor iedereen die gewoon wil zien hoe het allemaal +werkt. + +Een grote verzameling extra software, overgezet op FreeBSD (de +"ports" verzameling) wordt ook beschikbaar gesteld, om het +makkelijker te maken om al uw favoriete traditionele UNIX +utilities te installeren. +Meer dan 270 "ports", die software omvatten van tekstverwerkers +tot programmeertalen, maken van FreeBSD een krachtige +en veelomvattende operating omgeving die kan concureren met die +van veel grote werkstations op het gebied van algemene inzet- +baarheid en verwerkingskracht. + +Om meer documentatie over dit systeem te verkrijgen, is het aan- +bevolen om de '4.4BSD Document Set' te kopen van O'Reilly Associates +en de USENIX Association, ISBN 1-56592-082-1. We hebben niets +met O'Reilly te maken, maar zijn slechts tevreden klanten! + +Voordat u verder gaat met de installatie is het aan te bevelen +*eerst* de 'HARDWARE GUIDE' te lezen. PC hardware configuren voor +iets anders dan DOS/Windows (die de hardware niet zo erg belasten) +is wat moeilijker dan het lijkt, en als u denkt dat u PC's begrijpt +dan heeft u ze duidelijk nog niet lang genoeg gebruikt :) +De 'HARDWARE GUIDE' geeft u wat tips om uw hardware te configureren +en op welke symptomen te letten als er problemen zijn. Deze gids is +aanwezig in het Documentatie menu van de FreeBSD start-diskette. + +Ofschoon FreeBSD zijn uiterste best doet om te hoeden voor +gegevensverlies, is het nog steeds meer dan mogelijk om AL UW +GEGEVENS OP UW HARDDISK KWIJT TE RAKEN met deze installatie. Ga +niet verder met installatiemenu voordat er van alle belangrijke +gegevens een backup is gemaakt! + +Technisch commentaar op deze release moet gestuurd worden naar: + + hackers@FreeBSD.org + +Meldingen van gevonden fouten in FreeBSD moeten gestuurd worden +met het 'send-pr' kommando als u er in geslaagd bent om het +systeem te installeren, anders naar: + + bugs@FreeBSD.org + +Vermeld duidelijk om WELKE VERSIE van FreeBSD het gaat in berichten +over fouten. + +Algemene vragen kunnen gestuurd worden naar: + + questions@FreeBSD.org + +Heb een beetje geduld als uw vraag niet meteen beantwoord wordt - +we hebben het erg druk op het moment, en ons vrijwilligers werk +belast ons vaak tot aan de limiet. Foutmeldingen die verstuurd zijn +m.b.v. 'send-pr' worden opgeslagen en bijgehouden in onze +'bug'-database. U wordt geïnformeerd over de veranderingen in de +status van de fout (of vraag naar een feature) tijdens de levensduur +ervan. + +Onze WEB server, http://www.freebsd.org, is een goede bron voor +nieuwe of bijgewerkte informatie en biedt ook een aantal geavan- +ceerde documentatie faciliteiten. U kunt de BSDI versie van +Netscape gebruiken om over het 'World Wide Web' te 'surfen'. + +Zie ook /usr/share/FAQ en /usr/share/doc voor informatie over +het systeem. + +Bedankt voor het lezen en we hopen dat deze release van FreeBSD +u goed bevalt. + + Jordan Hubbard, + voor het FreeBSD project diff --git a/release/sysinstall/help/nl_NL.ISO_8859-1/configure.hlp b/release/sysinstall/help/nl_NL.ISO_8859-1/configure.hlp new file mode 100644 index 0000000..91c39f5 --- /dev/null +++ b/release/sysinstall/help/nl_NL.ISO_8859-1/configure.hlp @@ -0,0 +1,16 @@ +Dit menu stelt u in staat om uw systeem tot op zekere hoogte +te configureren na de installatie. In ieder geval kunt u hiermee +het wachtwoord van de systeembeheerder en de tijdzone instellen. + +Voor extra programmatuur zoals bash, emacs, pascal, etc. is het +aan te raden naar het 'Packages' item te kijken in dit menu. Op +het moment is het helaas alleen bruikbaar als u een CDROM heeft of +ergens op uw harddisk packages heeft staan waar het package +installatie programma erbij kan. Automatische overdracht van +packages via FTP wordt nog niet ondersteund. + +Als u na de installatie het packages installatie programma opnieuw +wilt gebruiken kunt u dit oproepen door het kommando 'pkg_manage'. +Om de tijdzone te veranderen kunt u 'tzsetup' gebruiken. Voor +meer informatie over algemene systeem configuratie zie het bestand +'/etc/sysconfig'. diff --git a/release/sysinstall/help/nl_NL.ISO_8859-1/language.hlp b/release/sysinstall/help/nl_NL.ISO_8859-1/language.hlp new file mode 100644 index 0000000..48fac09 --- /dev/null +++ b/release/sysinstall/help/nl_NL.ISO_8859-1/language.hlp @@ -0,0 +1,15 @@ +Met dit menu kunt u een andere taal selecteren. Op het moment worden +alleen de help bestanden in de gekozen taal weergegeven. + +In een volgende release zal ook de toetsenbord layout, scherm +aansturing, NLS instellingen ('sysinstall' zelf zal ook 'message +catalogs' gebruiken zodat alle menu's in de gekozen taal worden +weergegeven) veranderd worden en andere I18N instellingen om +aan diverse standaarden te voldoen. + +Totdat deze verbeteringen zijn doorgevoerd kunt u het beste deze +veranderingen zelf aan te brengen door het bestand '/etc/sysconfig' +te bewerken nadat het systeem is geïnstalleerd. Er is commentaar +in het bestand aanwezig dat aangeeft wat er verander moet worden. +Er zijn ook wat voorbeelden van niet-Engelse configuraties. + diff --git a/release/sysinstall/help/nl_NL.ISO_8859-1/usage.hlp b/release/sysinstall/help/nl_NL.ISO_8859-1/usage.hlp new file mode 100644 index 0000000..50a2808 --- /dev/null +++ b/release/sysinstall/help/nl_NL.ISO_8859-1/usage.hlp @@ -0,0 +1,56 @@ +GEBRUIKSINSTRUCTIES VOOR DIT SYSTEEM +==================================== + +TOETS AKTIE +===== ===== +PIJL OMHOOG Ga naar het vorige item (of omhoog in een tekst veld) +PIJL OMLAAG Ga naar het volgende item (of omlaag, in een tekst veld) +TAB Ga naar het volgende item of groep +PIJL RECHTS Ga naar het volgende item of groep (hetzelfde als TAB) +SHIFT-TAB Ga naar het vorige item of groep +PIJL LINKS Ga naar het vorige item of groep (hetzelfde als SHIFT-TAB) +RETURN Selecteer item +PAGE UP Ga een pagina omhoog in tekst vensters +PAGE DOWN Ga een pagina omlaag in tekst vensters +SPATIEBALK Selecteer/deselecteer het huidige item in "radio" of + multiple choice menus. +F1 Help (indien het huidige scherm er in voorziet) + +Als er meer menu-items zijn dan getoond kunnen worden, verschijnen er +symbolen om aan te geven of dit aan de bovenkant is: "^(-)" of aan de +onderkant "v(+)". Gebruik de PIJL OMHOOG/OMLAAG toetsen om te bladeren. +Als een van de symbolen verdwijnt dan ben je aan de onderkant +(of bovenkant) van het menu. + +In tekst vensters wordt de hoeveelheid tekst die nog getoond moet +worden als een percentage weergegeven in de rechter onderhoek. 100% +betekent dat je het einde van de tekst hebt bereikt. + +Selektie van <OK> in een menu bevestigt de aktie die erdoor gekontro- +leerd wordt. Selektie van <Cancel> annuleert de aktie en zal je over +het algemeen terugbrengen in het vorige menu. + +SPECIALE MOGELIJKHEDEN +====================== + +Het is ook mogelijk om een menu item te selekteren door de eerste +letter (of cijfer) van de naam te typen, als deze uniek is. Deze +letters (of cijfers) zijn vetgedrukt (of in een andere kleur weer- +gegeven) om ze te onderscheiden. + +Het is ook mogelijk om terug te bladeren als er regels aan de +bovenkant van het scherm zijn gerold. Deze 'terug-blader-modus' +kan geaktiveerd worden door op de "Scroll Lock" toets te drukken. +Nu kun je m.b.v. PIJL OMHOOG/OMLAAG of Page Up/Page Down door de +bewaarde regels bladeren. Druk nogmaals op "Scroll Lock" om deze +modus te beëindigen. Deze mogelijkheid is erg handig als je in een +sub-shell zit of andere expert-modes gebruikt die geen menus +hebben. + +Na installatie, en als het systeem in "multi-user" mode draait, kun +je gebruik maken van "virtuele consoles" om meerdere aktieve +sessies tegelijk te kunnen gebruiken. Gebruik ALT-F<n> om tussen de +verschillende sessies te wisselen, 'F<n>' is de funktietoets die +overeenkomt met de sessie die je wilt zien. Standaard is het +systeem geconfigureerd voor 4 virtuele consoles. Bewerk /etc/ttys +om meer virtuele consoles te configureren. Het maximum aantal is 12. diff --git a/release/sysinstall/help/no_NO.ISO8859-1/README b/release/sysinstall/help/no_NO.ISO8859-1/README new file mode 100644 index 0000000..d3d2989 --- /dev/null +++ b/release/sysinstall/help/no_NO.ISO8859-1/README @@ -0,0 +1,107 @@ + ----------------------------------------- + FreeBSD 2.0.5 --- UTGITT Version , , + ----------------------------------------- /( )` + \ \___ / | +Velkommen til 2.0.5 versjonen av FreeBSD! 2.0.5 er /- _ `-/ ' +en midlertidig utgave av FreeBSD som er ment til (/\/ \ \ /\ +å fylle gapet mellom 2.0R (som var / / | ` \ +utgitt i Nov 94) og 2.1R, som kommer til O O ) / | +å bli utgitt sent i Juli d.å.. FreeBSD 2.0.5 `-^--'`< ' +inneholder mange vesentlige forbedringer til 2.0R, (_.) _ ) / +ikke minst av dem er større stabilitet (med `.___/` / +en betraktelig margin), dusinvis av nye `-----' / +momenter og et mye forbedret installasjons<----. __ / __ \ +program. Se utgivelse-notatene for mere <----|====O)))==) \) /==== +detaljer om hva som er nytt i <----' `--' `.__,' \ +FreeBSD 2.0.5! | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +Hva er FreeBSD? FreeBSD er et operativ system basert på 4.4 BSD Lite +for Intel, AMD, Cyrix or NexGen "x86" basert PC maskinvare. Det fungerer +med et veldig stor utvalg av PC ytre-enheter og konfigurasjoner og kan +bli brukt til alt fra programvare utvikling til Internet Service +Provision; den travleste plassen på Internetet, ftp.cdrom.com, er en +FreeBSD maskin! + +Denne utgaven av FreeBSD inneholder alt du trenger for å drive et slikt +system, pluss full kilde-kode til hele systemet. Med kilde-koden +installert kan du om-kompilere hele systemet fra grunnen opp med +en kommando, noe som gjøer systemet ideelt for studenter, +forskere eller folk som bare vil se hvordan det hele virker. + +En stor samling av program som har blitt flyttet over av andre ("flytte +samlingen") er også tilbrakt for å gjøre det enklere for deg +å få tak i og installere dine yndlings program for UNIX. +Over 270 program har blitt flyttet over til FreeBSD, fra +redigerings-program til programmerings språk til grafiske applikasjoner, +noe som gjør FreeBSD et kraftig og omfattende operativ miljø som +er på likhet med mange store arbeidsmaskiner når det gjelder generell +anvendelse og styrke. + + +For mere dokumentasjon om dette systemet, anbefaler vi at du +kjøper 4.4BSD Dokumentasjons settet fra O'Reilly Associates og +USENIX Foreningen, ISBN 1-56592-082-1. Vi har ingen forbindelse med +O'Reilly, vi er bare tilfredstilte kunder! + +Det er å anbefale at du også leser MASKINVARE GUIDEN *før* +du fortsetter videre med installasjonen. Oppsett av PC +maskinvare for alt annet enn DOS/Windows ( som ikke akkurat belaster +maskinvaren ) er faktisk en hel del vanskeligere enn det ser ut til. Dersom +du tror at du forstår deg på PCer, så har du tydeligvis ikke +brukt dem lenge nok! :) Denne rettledningen vil gi deg noen tips om hvordan +å sette opp maskinvaren og hva slags symptomer å se etter om du +skulle få vanskeligheter. Denne rettledningen er tilgjengelig fra +Dokumentasjons menyen på FreeBSD oppstartings-disketten. + +FRALEGGELSE: Selv om FreeBSD gjør sitt beste til å beskytte mot +tilfeldig tap av data er det fremdeles mulig å slette ut hele disken +i forbindelse med denne installasjonen. Vær så vennlig ikke å +fortsette til den siste FreeBSD installasjons menyen uten at du har +et sikkerhetskopi av alle viktige data først! Dette mener vi på +alvor! + +Tekniske kommentarer om denne utgaven bør sendes (på Engelsk!) til: + + hackers@FreeBSD.org + + +Programfeil-rapporter bør sendes med å bruke `send-pr' kommandoen, +dersom du var i stand til å installere systemet, ellers til: + + bugs@FreeBSD.org + +Vær sikker på å indikere HVILKEN VERSJON av FreeBSD du kjrøer +i enhver programfeil rapport! + + +Generelle spørsmål bør sendes til: + + questions@FreeBSD.org + +Vær så snill å ha tålmodighet dersom du ikke får svar +med en gang - dette er en spesielt travel tid for oss, og våre +frivillige resurser er ofte strekt til grensen! Programfeil rapporter +som har blitt lagt fram med 'send-pr' kommandoen er ajourført og +etterfulgt i vår programfeil database, og du kommer til å bli +informert om enhver status-forandring så lenge programfeilen (eller +moment etterspørsel) eksisterer. + +Vår WEB plass, http://www.freebsd.org, er også en veldig god kilde for +oppdatert informasjon og tilbyr flere avanserte dokumenterings hjelpemidler. +Du kan bruke BSDI versonen av Netscape for å surfe World Wide Web +direkte fra FreeBSD. + +Du kan også se i /usr/share/FAQ og /usr/share/doc for videre informasjon +om systemet. + + +Takk for at du tok deg tid til å lese alt dette, og vi håper +oppriktig at du vil nyte denne utgaven av FreeBSD! + + Jordan Hubbard, + for FreeBSD Prosjektet diff --git a/release/sysinstall/help/no_NO.ISO8859-1/configure.hlp b/release/sysinstall/help/no_NO.ISO8859-1/configure.hlp new file mode 100644 index 0000000..6a02435 --- /dev/null +++ b/release/sysinstall/help/no_NO.ISO8859-1/configure.hlp @@ -0,0 +1,16 @@ +Denne menyen lar deg konfigurere systemet ditt etter at det er +installert. Du burde ihvertfall sette passordet til system-bestyreren og +tidssonen for systemet. + +For ekstra godbiter som bash, emacs, pascal, osv. bør du ta en titt +på Packages valget i denne menyen. Merk at dette valget, så langt, +bare virker ordentlig dersom du har en CDROM eller en eksisterende +pakke samling en eller annen plass i fil-hierarkiet hvor pakke-bestyrer +programmet kan finne det. Automatisk overføring av pakkene via FTP +er ikke mulig ennå! + +Dersom du ønsker å pøkalle pakke installasjons programmet på +nytt etter at du har forlatt system-installasjons-programmet, bruk +kommandoen ''pkg_manage''. For å sette tidssonen, skriv ''tzsetup''. +For mere informasjon om konfigurasjonen av systemet, se i /etc/sysconfig +filen. diff --git a/release/sysinstall/help/no_NO.ISO8859-1/language.hlp b/release/sysinstall/help/no_NO.ISO8859-1/language.hlp new file mode 100644 index 0000000..efdd21f --- /dev/null +++ b/release/sysinstall/help/no_NO.ISO8859-1/language.hlp @@ -0,0 +1,13 @@ +Bruk denne menyen til å velge språket du foretrekker. Dette setter +bare språket som blir brukt når hjelpefilene er vist fram. + +I framtidige utgaver vil dette også forandre tastaturet, skjerm kartet, +NLS oppsettet ( sysinstall vil også bruke beskjed kataloger slik at +alle menyene blir vist frem i språket du valgte) og utføre andre +I18N momenter for å følge forskjellige normer. + +Inntil disse forbedringene er utført, vil du kanskje finne det +enklest å redigere /etc/sysconfig filen selv etter systemet er +ferdig installert. Det er mange merknader i den filen som beskriver +hva som må forandres, og ett par eksempler på eksisterende +språk oppsett. diff --git a/release/sysinstall/help/no_NO.ISO8859-1/usage.hlp b/release/sysinstall/help/no_NO.ISO8859-1/usage.hlp new file mode 100644 index 0000000..01c3d1d --- /dev/null +++ b/release/sysinstall/help/no_NO.ISO8859-1/usage.hlp @@ -0,0 +1,56 @@ +HVORDAN Å BRUKE SYSTEMET +========================= + +TAST FUNKSJON +---- -------- +PIL OPP Flytte til forrige dataelement (eller opp, i et tekstfelt). +PIL NED Flytte til neste dataelement (eller ned, i et tekstfelt). +TAB Flytte til neste dataelement eller gruppe. +HØYRE PIL Flytte til neste dataelement eller gruppe (samme som TAB). +SKIFT-TAB Flytte til forrige dataelement eller gruppe. +VENSTRE PIL Flytte til forrige dataelement eller gruppe (samme + som SKIFT-TAB). +RETUR Velge dataelement. +SIDE OPP I tekstbokser, ruller opp en side. +SIDE NED I tekstbokser, ruller ned en side. +MELLOMROM I "radio" eller flervalgs menyer, markere inneværende + dataelement. +F1 Hjelp (i de skjermene som støtter dette). + +Dersom du også ser små "^(-)" eller "v(+)" symboler på kantene av +en meny, betyr det at det er flere dataelementer ovenfor eller nedenfor +det aktive elementet som ikke blir fremvist (p.g.a. mangel på skjermplass). +Pil Opp/Ned-tastene ruller menyen. Når ett av disse symbolene forsvinner, +betyr det at du er på toppen (eller bunnen) av menyen. + +I et tekstfelt vil prosenten av igjenomgått tekst bli vist i nedre høyre +hjørne av feltet. 100% betyr at du er på bunnen av feltet. + +Valg av OK i en meny, bekrefter den funksjonen som menyen kontrollerer. +Valg av Cancel vil avbryte operasjonen og generelt sett returnere til +forrige meny. + + +SPESIELLE MOMENTER: +=================== + +Det er også mulig å velge et meny element ved å trykke på første +bokstaven av navnet, dersom den er unik. Slike "akselerasjonsbokstaver" +vil være spesielt markert i elementnavnet. + +Konsolldriveren har en innebygget rulle-tilbake buffer some en kan bruke +til å inspisere ting som har rullet ut av skjermen. For å bruke +rulle-tilbake funksjonen, trykk på "Scroll Lock" tasten på tastaturet. +Piltastene og Side Opp/Ned tastene kan nå brukes til å gå +igjennom den lagrede teksten. For å forlate rulle-tilbake modusen, +trykk på "Scroll Lock" tasten igjen. Dette momentet er best egnet for å +håndtere underordnede-skjell og andre "vidundermoduser" som ikke bruker +menyer. + +Når systemet er ferdig installert og kjører i fler-bruker modus, vil +du også finne at du har mange "virtuelle konsoller" til rådighet og +kan bruke dem til å ha flere aktive sesjoner på en gang. Bruk ALT-F<n> +til å velge mellom dem, hvor 'F<n>' er funksjons-tasten som korresponderer +med den skjermen du ønsker å se. Systemet, som det blir installert, har +normalt 3 virtuelle konsoller. Du kan lage flere med å redigere /etc/ttys +filen, etter systemet har kommet opp, opptil et maksimum av 12. diff --git a/release/sysinstall/help/no_NO.ISO_8859-1/README b/release/sysinstall/help/no_NO.ISO_8859-1/README new file mode 100644 index 0000000..d3d2989 --- /dev/null +++ b/release/sysinstall/help/no_NO.ISO_8859-1/README @@ -0,0 +1,107 @@ + ----------------------------------------- + FreeBSD 2.0.5 --- UTGITT Version , , + ----------------------------------------- /( )` + \ \___ / | +Velkommen til 2.0.5 versjonen av FreeBSD! 2.0.5 er /- _ `-/ ' +en midlertidig utgave av FreeBSD som er ment til (/\/ \ \ /\ +å fylle gapet mellom 2.0R (som var / / | ` \ +utgitt i Nov 94) og 2.1R, som kommer til O O ) / | +å bli utgitt sent i Juli d.å.. FreeBSD 2.0.5 `-^--'`< ' +inneholder mange vesentlige forbedringer til 2.0R, (_.) _ ) / +ikke minst av dem er større stabilitet (med `.___/` / +en betraktelig margin), dusinvis av nye `-----' / +momenter og et mye forbedret installasjons<----. __ / __ \ +program. Se utgivelse-notatene for mere <----|====O)))==) \) /==== +detaljer om hva som er nytt i <----' `--' `.__,' \ +FreeBSD 2.0.5! | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +Hva er FreeBSD? FreeBSD er et operativ system basert på 4.4 BSD Lite +for Intel, AMD, Cyrix or NexGen "x86" basert PC maskinvare. Det fungerer +med et veldig stor utvalg av PC ytre-enheter og konfigurasjoner og kan +bli brukt til alt fra programvare utvikling til Internet Service +Provision; den travleste plassen på Internetet, ftp.cdrom.com, er en +FreeBSD maskin! + +Denne utgaven av FreeBSD inneholder alt du trenger for å drive et slikt +system, pluss full kilde-kode til hele systemet. Med kilde-koden +installert kan du om-kompilere hele systemet fra grunnen opp med +en kommando, noe som gjøer systemet ideelt for studenter, +forskere eller folk som bare vil se hvordan det hele virker. + +En stor samling av program som har blitt flyttet over av andre ("flytte +samlingen") er også tilbrakt for å gjøre det enklere for deg +å få tak i og installere dine yndlings program for UNIX. +Over 270 program har blitt flyttet over til FreeBSD, fra +redigerings-program til programmerings språk til grafiske applikasjoner, +noe som gjør FreeBSD et kraftig og omfattende operativ miljø som +er på likhet med mange store arbeidsmaskiner når det gjelder generell +anvendelse og styrke. + + +For mere dokumentasjon om dette systemet, anbefaler vi at du +kjøper 4.4BSD Dokumentasjons settet fra O'Reilly Associates og +USENIX Foreningen, ISBN 1-56592-082-1. Vi har ingen forbindelse med +O'Reilly, vi er bare tilfredstilte kunder! + +Det er å anbefale at du også leser MASKINVARE GUIDEN *før* +du fortsetter videre med installasjonen. Oppsett av PC +maskinvare for alt annet enn DOS/Windows ( som ikke akkurat belaster +maskinvaren ) er faktisk en hel del vanskeligere enn det ser ut til. Dersom +du tror at du forstår deg på PCer, så har du tydeligvis ikke +brukt dem lenge nok! :) Denne rettledningen vil gi deg noen tips om hvordan +å sette opp maskinvaren og hva slags symptomer å se etter om du +skulle få vanskeligheter. Denne rettledningen er tilgjengelig fra +Dokumentasjons menyen på FreeBSD oppstartings-disketten. + +FRALEGGELSE: Selv om FreeBSD gjør sitt beste til å beskytte mot +tilfeldig tap av data er det fremdeles mulig å slette ut hele disken +i forbindelse med denne installasjonen. Vær så vennlig ikke å +fortsette til den siste FreeBSD installasjons menyen uten at du har +et sikkerhetskopi av alle viktige data først! Dette mener vi på +alvor! + +Tekniske kommentarer om denne utgaven bør sendes (på Engelsk!) til: + + hackers@FreeBSD.org + + +Programfeil-rapporter bør sendes med å bruke `send-pr' kommandoen, +dersom du var i stand til å installere systemet, ellers til: + + bugs@FreeBSD.org + +Vær sikker på å indikere HVILKEN VERSJON av FreeBSD du kjrøer +i enhver programfeil rapport! + + +Generelle spørsmål bør sendes til: + + questions@FreeBSD.org + +Vær så snill å ha tålmodighet dersom du ikke får svar +med en gang - dette er en spesielt travel tid for oss, og våre +frivillige resurser er ofte strekt til grensen! Programfeil rapporter +som har blitt lagt fram med 'send-pr' kommandoen er ajourført og +etterfulgt i vår programfeil database, og du kommer til å bli +informert om enhver status-forandring så lenge programfeilen (eller +moment etterspørsel) eksisterer. + +Vår WEB plass, http://www.freebsd.org, er også en veldig god kilde for +oppdatert informasjon og tilbyr flere avanserte dokumenterings hjelpemidler. +Du kan bruke BSDI versonen av Netscape for å surfe World Wide Web +direkte fra FreeBSD. + +Du kan også se i /usr/share/FAQ og /usr/share/doc for videre informasjon +om systemet. + + +Takk for at du tok deg tid til å lese alt dette, og vi håper +oppriktig at du vil nyte denne utgaven av FreeBSD! + + Jordan Hubbard, + for FreeBSD Prosjektet diff --git a/release/sysinstall/help/no_NO.ISO_8859-1/configure.hlp b/release/sysinstall/help/no_NO.ISO_8859-1/configure.hlp new file mode 100644 index 0000000..6a02435 --- /dev/null +++ b/release/sysinstall/help/no_NO.ISO_8859-1/configure.hlp @@ -0,0 +1,16 @@ +Denne menyen lar deg konfigurere systemet ditt etter at det er +installert. Du burde ihvertfall sette passordet til system-bestyreren og +tidssonen for systemet. + +For ekstra godbiter som bash, emacs, pascal, osv. bør du ta en titt +på Packages valget i denne menyen. Merk at dette valget, så langt, +bare virker ordentlig dersom du har en CDROM eller en eksisterende +pakke samling en eller annen plass i fil-hierarkiet hvor pakke-bestyrer +programmet kan finne det. Automatisk overføring av pakkene via FTP +er ikke mulig ennå! + +Dersom du ønsker å pøkalle pakke installasjons programmet på +nytt etter at du har forlatt system-installasjons-programmet, bruk +kommandoen ''pkg_manage''. For å sette tidssonen, skriv ''tzsetup''. +For mere informasjon om konfigurasjonen av systemet, se i /etc/sysconfig +filen. diff --git a/release/sysinstall/help/no_NO.ISO_8859-1/language.hlp b/release/sysinstall/help/no_NO.ISO_8859-1/language.hlp new file mode 100644 index 0000000..efdd21f --- /dev/null +++ b/release/sysinstall/help/no_NO.ISO_8859-1/language.hlp @@ -0,0 +1,13 @@ +Bruk denne menyen til å velge språket du foretrekker. Dette setter +bare språket som blir brukt når hjelpefilene er vist fram. + +I framtidige utgaver vil dette også forandre tastaturet, skjerm kartet, +NLS oppsettet ( sysinstall vil også bruke beskjed kataloger slik at +alle menyene blir vist frem i språket du valgte) og utføre andre +I18N momenter for å følge forskjellige normer. + +Inntil disse forbedringene er utført, vil du kanskje finne det +enklest å redigere /etc/sysconfig filen selv etter systemet er +ferdig installert. Det er mange merknader i den filen som beskriver +hva som må forandres, og ett par eksempler på eksisterende +språk oppsett. diff --git a/release/sysinstall/help/no_NO.ISO_8859-1/usage.hlp b/release/sysinstall/help/no_NO.ISO_8859-1/usage.hlp new file mode 100644 index 0000000..01c3d1d --- /dev/null +++ b/release/sysinstall/help/no_NO.ISO_8859-1/usage.hlp @@ -0,0 +1,56 @@ +HVORDAN Å BRUKE SYSTEMET +========================= + +TAST FUNKSJON +---- -------- +PIL OPP Flytte til forrige dataelement (eller opp, i et tekstfelt). +PIL NED Flytte til neste dataelement (eller ned, i et tekstfelt). +TAB Flytte til neste dataelement eller gruppe. +HØYRE PIL Flytte til neste dataelement eller gruppe (samme som TAB). +SKIFT-TAB Flytte til forrige dataelement eller gruppe. +VENSTRE PIL Flytte til forrige dataelement eller gruppe (samme + som SKIFT-TAB). +RETUR Velge dataelement. +SIDE OPP I tekstbokser, ruller opp en side. +SIDE NED I tekstbokser, ruller ned en side. +MELLOMROM I "radio" eller flervalgs menyer, markere inneværende + dataelement. +F1 Hjelp (i de skjermene som støtter dette). + +Dersom du også ser små "^(-)" eller "v(+)" symboler på kantene av +en meny, betyr det at det er flere dataelementer ovenfor eller nedenfor +det aktive elementet som ikke blir fremvist (p.g.a. mangel på skjermplass). +Pil Opp/Ned-tastene ruller menyen. Når ett av disse symbolene forsvinner, +betyr det at du er på toppen (eller bunnen) av menyen. + +I et tekstfelt vil prosenten av igjenomgått tekst bli vist i nedre høyre +hjørne av feltet. 100% betyr at du er på bunnen av feltet. + +Valg av OK i en meny, bekrefter den funksjonen som menyen kontrollerer. +Valg av Cancel vil avbryte operasjonen og generelt sett returnere til +forrige meny. + + +SPESIELLE MOMENTER: +=================== + +Det er også mulig å velge et meny element ved å trykke på første +bokstaven av navnet, dersom den er unik. Slike "akselerasjonsbokstaver" +vil være spesielt markert i elementnavnet. + +Konsolldriveren har en innebygget rulle-tilbake buffer some en kan bruke +til å inspisere ting som har rullet ut av skjermen. For å bruke +rulle-tilbake funksjonen, trykk på "Scroll Lock" tasten på tastaturet. +Piltastene og Side Opp/Ned tastene kan nå brukes til å gå +igjennom den lagrede teksten. For å forlate rulle-tilbake modusen, +trykk på "Scroll Lock" tasten igjen. Dette momentet er best egnet for å +håndtere underordnede-skjell og andre "vidundermoduser" som ikke bruker +menyer. + +Når systemet er ferdig installert og kjører i fler-bruker modus, vil +du også finne at du har mange "virtuelle konsoller" til rådighet og +kan bruke dem til å ha flere aktive sesjoner på en gang. Bruk ALT-F<n> +til å velge mellom dem, hvor 'F<n>' er funksjons-tasten som korresponderer +med den skjermen du ønsker å se. Systemet, som det blir installert, har +normalt 3 virtuelle konsoller. Du kan lage flere med å redigere /etc/ttys +filen, etter systemet har kommet opp, opptil et maksimum av 12. diff --git a/release/sysinstall/help/options.hlp b/release/sysinstall/help/options.hlp new file mode 100644 index 0000000..c30180c --- /dev/null +++ b/release/sysinstall/help/options.hlp @@ -0,0 +1,95 @@ +The following options may be set from this screen: + +NFS Secure: NFS server talks only on a secure port + + This is most commonly used when talking to Sun workstations, which + will not talk NFS over "non priviledged" ports. + + +NFS Slow: User is using a slow PC or ethernet card + + Use this option if you have a slow PC (386) or an ethernet card + with poor performance being "fed" by NFS on a higher-performance + workstation. This will throttle the workstation back to prevent + the PC from becoming swamped with data. + + +FTP Abort: On transfer failure, abort + + This is pretty self-explanatory. If you're transfering from a + host that drops the connection or cannot provide a file, abort + the installation of that piece. + + +FTP Reselect: On transfer failure, ask for another host + + This is more useful to someone doing an interactive installation. + If the current host stops working, ask for a new ftp server to + resume the installation from. The install will attempt to pick + up from where it left off on the other server, if at all possible. + + +FTP Active: Use "active mode" for standard FTP + + For all FTP transfers, use "Active" mode. This will not work + through firewalls, but will often work with older ftp servers + that do not support passive mode. If your connection hangs + with passive mode (the default), try active! + + +FTP Passive: Use "passive mode" for firewalled FTP + + For all FTP transfers, use "Passive" mode. This allows the user + to pass through firewalls that do not allow incoming connections + on random port addresses. + + NOTE: ACTIVE AND PASSIVE MODES ARE NOT THE SAME AS A `PROXY' + CONNECTION, WHERE A PROXY FTP SERVER IS LISTENING ON A DIFFERENT + PORT! + + In such situations, you should specify the URL as something like: + + ftp://foo.bar.com:1234/pub/FreeBSD + + Where "1234" is the port number of the proxy ftp server. + + +Debugging: Turn on the extra debugging flag + + This turns on a lot of extra noise over on the second screen + (ALT-F2 to see it, ALT-F1 to switch back). If your installation + should fail for any reason, PLEASE turn this flag on when + attempting to reproduce the problem. It will provide a lot of + extra debugging at the failure point and may be very helpful to + the developers in tracking such problems down! + + +Yes To All: Assume "Yes" answers to all non-critical dialogs + + This flag should be used with caution. It will essentially + decide NOT to ask the user about any "boundry" conditions that + might not constitute actual errors but may be warnings indicative + of other problems. + + +FTP userpass: Specify username and password instead of anonymous. + + By default, the installation attempts to log in as the + anonymous user. If you wish to log in as someone else, + specify the username and password with this option. + + +Clear: Clear All Option Flags + + Reset all option flags back to their default values. + +---- + +Some of these items, like "FTP Active" or "FTP Passive", are actually +mutually-exclusive even though you can turn all of them on or off at +once. This is a limitation of the menuing system, and is compensated +for by checks that ensure that the various flags are not in conflict. +If you re-enter the Options menu again after leaving it, you'll see +the settings it's actually using after checking for any possible +conflicts. + diff --git a/release/sysinstall/help/partition.hlp b/release/sysinstall/help/partition.hlp new file mode 100644 index 0000000..19b6ce1 --- /dev/null +++ b/release/sysinstall/help/partition.hlp @@ -0,0 +1,122 @@ +This is the FreeBSD DiskLabel Editor. + +You should use this editor to create at least the following +filesystems: + + Name Purpose Min Size? Optional? + ---- ------- --------- --------- + / Root filesystem 20MB No + swap Swap space 2 * MEM No + /usr System & user files 80MB or more Yes + +Note: If you do not create a /usr filesystem then your / filesystem +will need to be bigger - at least 100MB. This is not recommended as +any media errors that may occur during disk I/O to user files will +corrupt the filesystem containing vital system files as well. It is +for this reason that / is generally kept on its own filesystem, where +it's basically considered "read only" by the system and hence a good +deal safer. + +Swap space is a little tricker, and the rule of "2 * MEM" is simply a +best-guess approximation and not necessarily accurate for your +intended usage of the system. If you intend to use the system heavily +in a server or multi-user application, you may be well advised to +increase this size. You may also create swap space on multiple drives +for a larger "total" swap and this is, in fact, recommended if you +have multiple, fast drives for which such load-balancing can only help +overall I/O performance. + +The /usr filesystem should be sized according to what kind of +distributions you're trying to load and how many packages you intend +to install in locations like /usr/local. You can also make /usr/local +a separate filesystem if you don't want to risk filling up your /usr +by mistake. + +Another useful filesystem to create is /var, which contains mail, news +printer spool files and other temporary items. It is a popular +candidate for a separate paritition and should be sized according to +your estimates of the amount of mail, news or spooled print jobs that +may be stored there. + +WARNING: If you do not create a separate filesystem for /var, space +for such files will be allocated out of the root (/) filesystem +instead. You may therefore wish to make the / partition bigger if you +expect a lot of mail or news and do not want to make /var its own +partition. + + +If you're new to this installation, you should also first understand +how FreeBSD 2.0.5's new "slices" paradigm for looking at disk storage +works. It's not very hard to grasp. A "fully qualified slice name", +that is the name of the file we open in /dev to talk to the slice, is +optionally broken into 3 parts: + + First you have the disk name. Assume we have two SCSI + drives in our system, which gives us `sd0' and `sd1'. + + Next you have the "Slice" (or "FDISK Partition") number, + as seen in the Partition Editor. Assume that our sd0 contains + two slices, a FreeBSD slice and a DOS slice. This gives us + sd0s1 and sd0s2. Let's also say that sd1 is completely devoted + to FreeBSD, so we have only one slice there: sd1s1. + + Next, if a slice is a FreeBSD slice, you have a number of + (confusingly named) "partitions" you can put inside of it. + These FreeBSD partitions are where various filesystems or swap + areas live, and using our hypothetical two-SCSI-disk machine + again, we might have something like the following layout on sd0: + + Name Mountpoint + ---- ---------- + sd0s1a / + sd0s1b <swap space> + sd0s1e /usr + + Because of historical convention, there is also a short-cut, + or "compatibility slice", that is maintained for easy access + to the first FreeBSD slice on a disk for those programs which + still don't know how to deal with the new slice scheme. + The compatibility slice names for our filesystem above would + look like: + + Name Mountpoint + ---- ---------- + sd0a / + sd0b <swap space> + sd0e /usr + + FreeBSD automatically maps the compatibility slice to the first + FreeBSD slice it finds (in this case, sd0s1). You may have multiple + FreeBSD slices on a drive, but only the first one may be the + compatibility slice! + + The compatibility slice will eventually be phased out, but + it is still important right now for several reasons: + + 1. Some programs, as mentioned before, still don't work + with the slice paradigm and need time to catch up. + + 2. The FreeBSD boot blocks are unable to look for + a root file system in anything but a compatibility + slice right now. This means that our root will always + show up on "sd0a" in the above scenario, even though + it really lives over on sd0s1a and would otherwise be + referred to by its full slice name. + +Once you understand all this, then the label editor becomes fairly +simple. You're either carving up the FreeBSD slices displayed at the +top of the screen into smaller pieces (displayed in the middle of the +screen) and then putting FreeBSD file systems on them, Or you're just +mounting existing partitions/slices into your filesystem hierarchy; +this editor lets you do both. Since a DOS partition is also just +another slice as far as FreeBSD is concerned, you can mount one into +in your filesystem hierarchy just as easily with this editor. For +FreeBSD partitions you can also toggle the "newfs" state so that +the partitions are either (re)created from scratch or simply checked +and mounted (the contents are preserved). + +When you're done, type `Q' to exit. + +No actual changes will be made to the disk until you (C)ommit from the +Install menu! You're working with what is essentially a copy of +the disk label(s), both here and in the FDISK Partition Editor. diff --git a/release/sysinstall/help/readme.hlp b/release/sysinstall/help/readme.hlp new file mode 100644 index 0000000..c166e26 --- /dev/null +++ b/release/sysinstall/help/readme.hlp @@ -0,0 +1,104 @@ + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Version , , + ----------------------------------------- /( )` + \ \___ / | +Welcome to the 2.0.5 release of FreeBSD! 2.0.5 is /- _ `-/ ' +an interim release of FreeBSD, filling a critical (/\/ \ \ /\ +gap during the period between 2.0R (which was / / | ` \ +released in Nov 94) and 2.1R, which will be O O ) / | +released in late July of '95. FreeBSD 2.0.5 `-^--'`< ' +contains many substantial improvements from 2.0R, (_.) _ ) / +not least of which is greater stability (by `.___/` / +a considerable margin), dozens of new `-----' / +features and a greatly enhanced <----. __ / __ \ +installation program. See the release <----|====O)))==) \) /==== +notes for more details on what's new in <----' `--' `.__,' \ +FreeBSD 2.0.5! | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +What is FreeBSD? FreeBSD is an operating system based on 4.4 BSD Lite +for Intel, AMD, Cyrix or NexGen "x86" based PC hardware. It works +with a very wide variety of PC peripherals and configurations and can +be used for everything from software development to Internet Service +Provision; the busiest site on the Internet, ftp.cdrom.com, is a +FreeBSD machine! + +This release of FreeBSD contains everything you need to run such a +system, plus full source code for everything. With the source +distribution installed you can literally recompile the entire system +from scratch with one command, making it ideal for students, +researchers or folks who simply want to see how it all works. + +A large collection of 3rd party ported software (the "ports +collection") is also provided to make it easier for you to obtain and +install all your favorite traditional UNIX utilities for FreeBSD. +Over 270 ports, from editors to programming languages to graphical +applications, make FreeBSD a powerful and comprehensive operating +environment that rivals that of many large workstations for general utility +and power. + + +For more documentation on this system, it is recommended that you +purchase the 4.4BSD Document Set from O'Reilly Associates and the +USENIX Association, ISBN 1-56592-082-1. We have no connection with +O'Reilly, we're just satisfied customers! + +You may also wish to read the HARDWARE GUIDE *before* proceeding any +further with the installation. Configuring PC hardware for anything +other than DOS/Windows (which don't actually make very significant +demands on the hardware) is actually quite a bit harder than it looks, +and if you think you understand PCs then you clearly haven't been +using them for long enough! :) This guide will give you some tips on +how to configure your hardware and what symptoms to watch for in case +of trouble. This guide is available in the Documentation menu of the +FreeBSD boot floppy. + +DISCLAIMER: While FreeBSD does its best to safeguard against accidental +loss of data, it's still more than possible to WIPE OUT YOUR ENTIRE DISK +with this installation! Please do not proceed to the final FreeBSD +installation menu unless you've adequately backed up any important +data first! We really mean it! + +Technical comments on this release should be sent (in English!) to: + + hackers@FreeBSD.org + + +Bug reports should be sent using the `send-pr' command, if you were +able to get the system installed, otherwise to: + + bugs@FreeBSD.org + +Please be sure to indicate WHICH VERSION of FreeBSD you're running in +any bug reports! + + +General questions should be sent to: + + questions@FreeBSD.org + +Please have patience if your questions are not answered right away - +this is an especially busy time for us, and our volunteer resources +are often strained to the limit! Bug reports submitted with the +send-pr command are logged and tracked in our bugs database, and +you'll be kept informed of any changes in status during the life of +the bug (or feature request). + +Our WEB site, http://www.freebsd.org, is also a very good source for +updated information and provides a number of advanced documentation +facilities. You may use the BSDI version of Netscape for browsing the +World Wide Web directly from FreeBSD. + +You may also wish to look in /usr/share/FAQ and /usr/share/doc for +further information on the system. + + +Thanks for reading all of this, and we sincerely hope you enjoy this +release of FreeBSD! + + Jordan Hubbard, + for The FreeBSD Project diff --git a/release/sysinstall/help/relnotes.hlp b/release/sysinstall/help/relnotes.hlp new file mode 100644 index 0000000..d4e30e7 --- /dev/null +++ b/release/sysinstall/help/relnotes.hlp @@ -0,0 +1,747 @@ + RELEASE NOTES + FreeBSD + Release 2.0.5 + +1. Technical overview +--------------------- + +FreeBSD is a freely available, full source 4.4 BSD Lite based release +for Intel i386/i486/Pentium (or compatible) based PC's. It is based +primarily on software from U.C. Berkeley's CSRG group, with some +enhancements from NetBSD, 386BSD, and the Free Software Foundation. + +Since our release of FreeBSD 2.0 some 8 months ago, the performance, +feature set, and stability of FreeBSD has improved dramatically. The +largest change is a revamped VM system with a merged VM/file buffer +cache that not only increases performance, but reduces FreeBSD's +memory footprint, making a 4MB configuration a more acceptable +minimum. Other enhancements include full NIS client and server +support, transaction TCP support, dial-on-demand PPP, an improved SCSI +subsystem, early ISDN support, support for FDDI and Fast Ethernet +(100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and +narrow) and many hundreds of bug fixes. + +We've also taken the comments and suggestions of many of our users to +heart and have attempted to provide what we hope is a more sane and +easily understood installation process. Your feedback on this +(constantly evolving) process is especially welcome! + +In addition to the base distributions, FreeBSD offers a new ported +software collection with some 270 commonly sought-after programs. The +list of ports ranges from http (WWW) servers, to games, languages, +editors and almost everything in between. The entire ports collection +requires only 10MB of storage, all ports being expressed as "deltas" +to their original sources. This makes it much easier for us to update +ports, and greatly reduces the disk space demands made by the older +1.0 ports collection. To compile a port, you simply change to the +directory of the program you wish to install, type make and let the +system do the rest. The full original distribution for each port you +build is retrieved dynamically off of CDROM or a local ftp site, so +you need only enough disk space to build the ports you want. (Almost) +every port is also provided as a pre-compiled "package" which can be +installed with a simple command (pkg_add) by those who do not wish to +compile their own ports from source. See the file: + /usr/share/FAQ/Text/ports.FAQ +for a more complete description of the ports collection. + + +Since our first release of FreeBSD 1.0 nearly two years ago, FreeBSD +has changed almost entirely. A new port from the Berkeley 4.4 code +base was done, which brought the legal status of the system out of the +shadows with the blessing of Novell (the new owners of USL and UNIX). The +port to 4.4 has also brought in a host of new features, filesystems +and enhanced driver support. With our new unencumbered code base, we +have every reason to hope that we'll be able to release quality +operating systems without further legal encumbrance for some time to +come! + +FreeBSD 2.0.5 represents the culmination of 2 years of work and many +thousands of man hours put in by an international development team. +We hope you enjoy it! + +A number of additional documents which you may find very helpful in +the process of installing and using FreeBSD may also be found in +the "FAQ" directory, either under /usr/share/FAQ on an installed +system or at the top level of the CDROM or FTP distribution from +where you're reading this file. Please consult FAQ/Text/ROADMAP +for a brief description of the resources provided by the FAQ directory. + +For a list of contributors and a general project description, please see +the file "CONTRIB.FreeBSD" which should be bundled with your binary +distribution. + +Also see the "REGISTER.FreeBSD" file for information on registering +with the "Free BSD user counter". This counter is for ALL freely +available variants of BSD, not just FreeBSD, and we urge you to register +yourself with it. + +The core of FreeBSD does not contain DES code which would inhibit its +being exported outside the United States. There is an add-on package +to the core distribution, for use only in the United States, that +contains the programs that normally use DES. The auxiliary packages +provided separately can be used by anyone. A freely (from outside the +U.S.) exportable European distribution of DES for our non-U.S. users also +exists and is described in the FreeBSD FAQ. + +If password security for FreeBSD is all you need, and you have no +requirement for copying encrypted passwords from different hosts +(Suns, DEC machines, etc) into FreeBSD password entries, then +FreeBSD's MD5 based security may be all you require! We feel that our +default security model is more than a match for DES, and without any +messy export issues to deal with. If you're outside (or even inside) +the U.S., give it a try! + + +1.1 What's new in 2.0.5? +------------------------ + +The following features were added or substantially improved between +the release of 2.0 and this 2.0.5 release. In order to facilitate +better communication, the person, or persons, responsible for each +enhancement is noted. Any questions regarding the new functionality +should be directed to them first. + +KERNEL: + +Merged VM-File Buffer Cache +--------------------------- +A merged VM/buffer cache design greatly enhances overall system +performance and makes it possible to do a number of more optimal +memory allocation strategies that were not possible before. + +Owner: David Greenman (davidg@FreeBSD.org) and + John Dyson (dyson@implode.root.com) + + +Network PCB hash optimization +----------------------------- +For systems with a great number of active TCP connections (WEB and ftp +servers, for example), this greatly speeds up the lookup time required +to match an incoming packet up to its associated connection. + +Owner: David Greenman (davidg@FreeBSD.org) + + +Name cache optimization +----------------------- +The name-cache would cache all files of the same name to the same bucket, +which would put for instance all ".." entries in the same bucket. We added +the parent directory version to frustrate the hash, and improved the +management of the cache in various other ways while we were at it. + +Owner: Poul-Henning Kamp (phk@FreeBSD.org) + David Greenman (davidg@FreeBSD.org) + + +Less restrictive swap-spaces +---------------------------- +The need to compile the names of the swap devices into the kernel has been +removed. Now swapon will accept any block devices, up to the maximum +number of swap devices configured in the kernel. + +Owner: Poul-Henning Kamp (phk@FreeBSD.org) + David Greenman (davidg@FreeBSD.org) + + +Hard Wired SCSI Devices +----------------------- +Prior to 2.0.5, FreeBSD performed dynamic assignment of unit numbers +to SCSI devices as they were probed, allowing a SCSI device failure to +possibly change unit number assignment and prevent filesystems on +still functioning disks from mounting. Hard wiring allows static +allocation of unit numbers (and hence device names) to scsi devices +based on SCSI ID and bus. SCSI configuration occurs in the kernel +config file. Samples of the configuration syntax can be found in the +scsi(4) man page or the LINT kernel config file. + +Owner: Peter Dufault (dufault@hda.com) +Sources involved: sys/scsi/* usr.sbin/config/* + + +Slice Support +------------- +FreeBSD now supports a "slice" abstraction which makes it more +completely interoperable with other operating system partitions. This +support will allow FreeBSD to inhabit DOS extended partitions. + +Owner: Bruce Evans (bde@FreeBSD.org) +Sources involved: sys/disklabel.h sys/diskslice.h sys/dkbad.h + kern/subr_diskslice.c kern/subr_dkbad.c + i386/isa/diskslice_machdep.c + i386/isa/wd.c scsi/sd.c dev/vn/vn.c + + +Support for Ontrack Disk Manager Version 6.0 +-------------------------------------------- +Support has been added for disks which use Ontrack Disk Manager. The +fdisk program does NOT know about it however, so make all changes +using the install program on the boot.flp or the Ontrack Disk Manager +tool under DOS. + +Owner: Poul-Henning Kamp (phk@FreeBSD.org) + + +Bad144 is back and working +-------------------------- +Bad144 works again, though the semantics are slightly different than +before in that the bad-spots are kept relative to the slice rather +than absolute on the disk. + +Owner: Bruce Evans (bde@FreeBSD.org) + Poul-Henning Kamp (phk@FreeBSD.org) + + +NEW DEVICE SUPPORT: + + SCSI and CDROM Devices + +Matsushita/Panasonic (Creative) CD-ROM driver +--------------------------------------------- +The Matsushita/Panasonic CR-562 and CR-563 drives are now supported +when connected to a Sound Blaster or 100% compatible host adapter. Up +to four host adapters are supported for a total of 16 CD-ROM drives. +The audio functions are supported, along with access to the raw (2352 byte) +data frames of any compact disc. Audio discs may be played using Karoke +variable speed functions. + +Owner: Frank Durda IV bsdmail@nemesis.lonestar.org +Sources involved: isa/matcd + + +Adaptec 2742/2842/2940 SCSI driver +---------------------------------- +The original 274x/284x driver has evolved considerably since the 2.0 +release. We now offer full support for the 2940 series as well as the +Wide models of these cards. The arbitration bug (as well as many +others) that caused the driver problems with fast devices has been +corrected and there is even experimental tagged queuing support +(kernel option "AHC_TAGENABLE"). John Aycock has also released the +sequencer code under a "Berkeley style" copyright making the driver +entirely clean of the GPL. + +Owner: Justin Gibbs (gibbs@FreeBSD.org) +Sources involved: isa/aic7770.c pci/aic7870.c i386/scsi/* + sys/dev/aic7xxx/* + + +NCR5380/NCR53400 SCSI ("ProAudio Spectrum") driver +-------------------------------------------------- +Owner: core +Submitted by: Serge Vakulenko (vak@cronyx.ru) +Sources involved: isa/ncr5380.c + + +Sony CDROM driver +----------------- +Owner: core +Submitted by: Mikael Hybsch (micke@dynas.se) +Sources involved: isa/scd.c + + + Serial Devices + +SDL Communications Riscom/8 Serial Board Driver +----------------------------------------------- +Owner: Andrey Chernov (ache@FreeBSD.org) +Sources involved: isa/rc.c isa/rcreg.h + + +Cyclades Cyclom-y Serial Board Driver +------------------------------------- +Owner: Bruce Evans (bde@FreeBSD.org) +Submitted by: Andrew Werple (andrew@werple.apana.org.au) and + Heikki Suonsivu (hsu@cs.hut.fi) +Obtained from: NetBSD +Sources involved: isa/cy.c + + +Cronyx/Sigma sync/async serial driver +------------------------------------- +Owner: core +Submitted by: Serge Vakulenko +Sources involved: isa/cronyx.c + + + + Networking + +Diskless booting +---------------- +Diskless booting in 2.0.5 is much improved. The boot-program is in +src/sys/i386/boot/netboot, and can be run from an MSDOS system or +burned into an EPROM. Local swapping is also possible. WD, SMC, 3COM +and Novell ethernet cards are currently supported. + + +DEC DC21140 Fast Ethernet driver +-------------------------------- +This driver supports any of the numerous NICs using the DC21140 chipset +including the 100Mb DEC DE-500-XA and SMC 9332. + +Owner: core +Submitted by: Matt Thomas (thomas@lkg.dec.com) +Sources involved: pci/if_de.c pci/dc21040.h + + +DEC FDDI (DEFPA/DEFEA) driver +----------------------------- +Owner: core +Submitted by: Matt Thomas (thomas@lkg.dec.com) +Sources involved: pci/if_pdq.c pci/pdq.c pci/pdq_os.h pci/pdqreg.h + + +3Com 3c505 (Etherlink/+) NIC driver +----------------------------------- +Owner: core +Submitted by: Dean Huxley (dean@fsa.ca) +Obtained from: NetBSD +Sources involved: isa/if_eg.c + + +Fujitsu MB86960A family of NICs driver +------------------------------------- +Owner: core +Submitted by: M.S. (seki@sysrap.cs.fujitsu.co.jp) +Sources involved: isa/if_fe.c + + +Intel EtherExpress driver +------------------------- +Owner: Rodney W. Grimes (rgrimes@FreeBSD.org) +Sources involved: isa/if_ix.c isa/if_ixreg.h + + +3Com 3c589 driver +----------------- +Owner: core +Submitted by: "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp), + Seiji Murata (seiji@mt.cs.keio.ac.jp) and + Noriyuki Takahashi (hor@aecl.ntt.jp) +Sources involved: isa/if_zp.c + + +IBM Credit Card Adapter driver +------------------------------ +Owner: core +Submitted by: "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp), +Sources involved: isa/pcic.c isa/pcic.h + + +EDSS1 and 1TR6 ISDN interface driver +------------------------------------ +Owner: core +Submitted by: Dietmar Friede (dfriede@drnhh.neuhaus.de) and + Juergen Krause (jkr@saarlink.de) +Sources involved: gnu/isdn/* + + + Miscellaneous Drivers + +Joystick driver +--------------- +Owner: Jean-Marc Zucconi (jmz@FreeBSD.org) +Sources involved: isa/joy.c + + +National Instruments "LabPC" driver +----------------------------------- +Owner: Peter Dufault (dufault@hda.com) +Sources involved: isa/labpc.c + + +WD7000 driver +------------- +Owner: Olof Johansson (offe@ludd.luth.se) + + +Pcvt Console driver +------------------- +Owner: Joerg Wunsch (joerg@FreeBSD.org) +Submitted by: Hellmuth Michaelis (hm@altona.hamburg.com) +Sources involved: isa/pcvt/* usr.sbin/pcvt/* + + +BSD-audio emulator for VAT driver +--------------------------------- +Owner: Amancio Hasty (ahasty@FreeBSD.org) and + Paul Traina (pst@FreeBSD.org) +Sources involved: isa/sound/vat_audio.c isa/sound/vat_audioio.h + + +National Instruments AT-GPIB and AT-GPIB/TNT GPIB driver +-------------------------------------------------------- +Owner: core +Submitted by: Fred Cawthorne (fcawth@delphi.umd.edu) +Sources involved: isa/gpib.c isa/gpib.h isa/gpibreg.h + + +Genius GS-4500 hand scanner driver +---------------------------------- +Owner: core +Submitted by: Gunther Schadow (gusw@fub46.zedat.fu-berlin.de) +Sources involved: isa/gsc.c isa/gscreg.h + + +CORTEX-I Frame Grabber +---------------------- +Owner: core +Submitted by: Paul S. LaFollette, Jr. +Sources involved: isa/ctx.c isa/ctxreg.h + + +Video Spigot video capture card +------------------------------- +Owner: Jim Lowe + + + +1.2 Experimental features +------------------------- + +The unionfs and LFS file systems are known to be severely broken in +2.0.5. This is in part due to old bugs that we haven't had time to +resolve yet and the need to update these file systems to deal with the +new VM system. We hope to address these issues in a later release of +FreeBSD. + +FreeBSD now supports running iBCS2 compatible binaries (currently SCO +UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported). The iBCS2 +emulator is in its early stages, but it is functional, we haven't been +able to do exhaustive testing (lack of commercial apps), but almost +all of SCO's 3.2.2 binaries are working, so is an old INFORMIX-2.10 +for SCO. Further testing is nessesary to complete this project. There +is also work under way for ELF & XOUT loaders, and most of the svr4 +syscall wrappers have been written. + +FreeBSD also implements enough of its Linux compatibility that we +can now run Linux DOOM! See the ``xperimnt'' directory (on your local +FTP server or CDROM) for full docs on how to set this up. + +Owner: Soren Schmidt (sos) & Sean Eric Fagan (sef) +Sources involved: sys/i386/ibcs2/* + misc kernel changes. + + +2. Supported Configurations +--------------------------- + +FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus +based PC's, ranging from 386sx to Pentium class machines (though the +386sx is not recommended). Support for generic IDE or ESDI drive +configurations, various SCSI controller, network and serial cards is +also provided. + +Following is a list of all disk controllers and ethernet cards currently +known to work with FreeBSD. Other configurations may very well work, and +we have simply not received any indication of this. + + +2.1. Disk Controllers +--------------------- + +WD1003 (any generic MFM/RLL) +WD1007 (any generic IDE/ESDI) +IDE +ATA + +Adaptec 152x series ISA SCSI controllers +Adaptec 154x series ISA SCSI controllers +Adaptec 174x series EISA SCSI controller in standard and enhanced mode. +Adaptec 274X/284X/2940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI controllers +Adaptec AIC-6260 and AIC-6360 based boards, which includes +the AHA-152x and SoundBlaster SCSI cards. + +** Note: You cannot boot from the SoundBlaster cards as they have no + on-board BIOS, which is necessary for mapping the boot device into the + system BIOS I/O vectors. They're perfectly usable for external tapes, + CDROMs, etc, however. The same goes for any other AIC-6x60 based card + without a boot ROM. Some systems DO have a boot ROM, which is generally + indicated by some sort of message when the system is first powered up + or reset. Check your system/board documentation for more details. + +[Note that Buslogic was formerly known as "Bustec"] +Buslogic 545S & 545c +Buslogic 445S/445c VLB SCSI controller +Buslogic 742A, 747S, 747c EISA SCSI controller. +Buslogic 946c PCI SCSI controller +Buslogic 956c PCI SCSI controller + +NCR 53C810 and 53C825 PCI SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + +DTC 3290 EISA SCSI controller in 1542 emulation mode. + +UltraStor 14F, 24F and 34F SCSI controllers. + +Seagate ST01/02 SCSI controllers. + +Future Domain 8xx/950 series SCSI controllers. + +WD7000 SCSI controller. + +With all supported SCSI controllers, full support is provided for +SCSI-I & SCSI-II peripherals, including Disks, tape drives (including +DAT) and CD ROM drives. + +The following CD-ROM type systems are supported at this time: +(cd) SCSI (also includes ProAudio Spectrum and SoundBlaster SCSI) +(mcd) Mitsumi proprietary interface +(matcd) Matsushita/Panasonic (Creative) proprietary interface +(scd) Sony proprietary interface + +Note: CD-Drives with IDE interfaces are not supported at this time. + +Some controllers have limitations with the way they deal with >16MB of +memory, due to the fact that the ISA bus only has a DMA address space +of 24 bits. If you do your arithmetic, you'll see that this makes it +impossible to do direct DMA to any address >16MB. This limitation is +even true of some EISA controllers (which are normally 32 bit) when +they're configured to emulate an ISA card, which they then do in *all* +respects. This problem is avoided entirely by IDE controllers (which +do not use DMA), true EISA controllers (like the UltraStor, Adaptec +1742A or Adaptec 2742) and most VLB (local bus) controllers. In the +cases where it's necessary, the system will use "bounce buffers" to +talk to the controller so that you can still use more than 16Mb of +memory without difficulty. + + +2.2. Ethernet cards +------------------- + +Allied-Telesis AT1700 and RE2000 cards +SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, +WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT +based clones. SMC Elite Ultra is also supported. + +DEC EtherWORKS III NICs (DE203, DE204, and DE205) +DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) +DEC DC21140 based NICs (SMC???? DE???) +DEC FDDI (DEFPA/DEFEA) NICs + +Fujitsu FMV-181 and FMV-182 + +Intel EtherExpress + +Isolan AT 4141-0 (16 bit) +Isolink 4110 (8 bit) + +Novell NE1000, NE2000, and NE2100 ethernet interface. + +3Com 3C501 cards + +3Com 3C503 Etherlink II + +3Com 3c505 Etherlink/+ + +3Com 3C507 Etherlink 16/TP + +3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III + +Toshiba ethernet cards + +PCMCIA ethernet cards from IBM and National Semiconductor are also +supported. + + +2.3. Misc +--------- + +AST 4 port serial card using shared IRQ. + +ARNET 8 port serial card using shared IRQ. + +BOCA ATIO66 6 port serial card using shared IRQ. + +Cyclades Cyclom-y Serial Board. + +STB 4 port card using shared IRQ. + +Mitsumi (all models) CDROM interface and drive. + +SDL Communications Riscom/8 Serial Board. + +SoundBlaster SCSI and ProAudio Spectrum SCSI CDROM interface and drive. + +Matsushita/Panasonic (Creative SoundBlaster) CDROM interface and drive. + +Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound +and Roland MPU-401 sound cards. + +FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but +support is apparently close to materializing. Details will be posted +as the situation develops. + + +3. Obtaining FreeBSD +-------------------- + +You may obtain FreeBSD in a variety of ways: + +1. FTP/Mail + +You can ftp FreeBSD and any or all of its optional packages from +`ftp.freebsd.org' - the official FreeBSD release site. + +For other locations that mirror the FreeBSD software see the file +MIRROR.SITES. Please ftp the distribution from the nearest site +to you netwise. + +If you do not have access to the internet and electronic mail is your +only recourse, then you may still fetch the files by sending mail to +`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message +to get more information on how to fetch files from ftp.freebsd.org. +Note: This approach will end up sending many *tens of megabytes* +through the mail, and should only be employed as an absolute LAST +resort! + + +2. CDROM + +FreeBSD 2.0.5 may be ordered on CDROM from: + + Walnut Creek CDROM + 4041 Pike Lane, Suite D + Concord CA 94520 + 1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax) + +Or via the internet from orders@cdrom.com or http://www.cdrom.com. +Their current catalog can be obtained via ftp as: + ftp://ftp.cdrom.com/cdrom/catalog. + +Cost per CD is $39.95, or $24.95 with a FreeBSD subscription. With +a subscription, you will automatically receive updates as they +are released. Your credit card will be billed when each disk is shipped +and you may cancel your subscription at any time without further obligation. + +Walnut Creek CDROM also sells a full line of FreeBSD related merchandise such +as T-shirts ($14.95, available in "child", Large and XL sizes), coffee mugs +($9.95), tattoos ($0.25 each) and posters ($3.00). + +Shipping (per order not per disc) is $5 in the US, Canada or +Mexico and $9.00 overseas. They accept Visa, Mastercard, Discover, +American Express or checks in U.S. Dollars and ship COD within the +United States. California residents please add 8.25% sales tax. + +Should you be dissatisfied for any reason, the CD comes with an +unconditional return policy. + + +Reporting problems, making suggestions, submitting code +------------------------------------------------------- + +Your suggestions, bug reports and contributions of code are always +valued - please do not hesitate to report any problems you may find +(preferably with a fix attached if you can!). + +The preferred method to submit bug reports from a machine with +internet mail connectivity is to use the send-pr command. Bug reports +will be dutifully filed by our faithful bugfiler program and you can +be sure that we'll do our best to respond to all reported bugs as soon +as possible. + +If, for some reason, you are unable to use the send-pr command to +submit a bug report, you can try to send it to: + + bugs@FreeBSD.org + + +Otherwise, for any questions or suggestions, please send mail to: + + questions@FreeBSD.org + +Additionally, being a volunteer effort, we are always happy to have +extra hands willing to help - there are already far more enhancements +to be done than we can ever manage to do by ourselves! To contact us +on technical matters, or with offers of help, you may send mail to: + + hackers@FreeBSD.org + +Since these mailing lists can experience significant amounts of +traffic, if you have slow or expensive mail access and you are +only interested in keeping up with significant FreeBSD events, you may +find it preferable to subscribe to: + + announce@FreeBSD.org + + +All but the freebsd-bugs groups can be freely joined by anyone wishing +to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword +`help' on a line by itself somewhere in the body of the message. This +will give you more information on joining the various lists, accessing +archives, etc. There are a number of mailing lists targeted at +special interest groups not mentioned here, so send mail to majordomo +and ask about them! + + +6. Acknowledgements +------------------- + +FreeBSD represents the cumulative work of many dozens, if not +hundreds, of individuals from around the world who have worked very +hard to bring you this release. It would be very difficult, if not +impossible, to enumerate everyone who's contributed to FreeBSD, but +nonetheless we shall try (in alphabetical order, of course). If your +name is not mentioned, please be assured that its omission is entirely +accidental. + + +The Computer Systems Research Group (CSRG), U.C. Berkeley. + +Bill Jolitz, for his initial work with 386BSD. + +The FreeBSD Core Team +(in alphabetical order by first name): + + Andreas Schulz <ats@FreeBSD.org> + Andrey A. Chernov <ache@FreeBSD.org> + Bruce Evans <bde@FreeBSD.org> + David Greenman <davidg@FreeBSD.org> + Garrett A. Wollman <wollman@FreeBSD.org> + Gary Palmer <gpalmer@FreeBSD.org> + Geoff Rehmet <csgr@FreeBSD.org> + Jack Vogel <jackv@FreeBSD.org> + John Dyson <dyson@FreeBSD.org> + Jordan K. Hubbard <jkh@FreeBSD.org> + Justin Gibbs <gibbs@FreeBSD.org> + Paul Richards <paul@FreeBSD.org> + Poul-Henning Kamp <phk@FreeBSD.org> + Rich Murphey <rich@FreeBSD.org> + Rodney W. Grimes <rgrimes@FreeBSD.org> + Satoshi Asami <asami@FreeBSD.org> + Søren Schmidt <sos@FreeBSD.org> + +Special mention to: + + Walnut Creek CDROM, without whose help (and continuing support) + this release would never have been possible. + + Dermot McDonnell for his donation of a Toshiba XM3401B CDROM + drive. + + Additional FreeBSD helpers and beta testers: + + J.T. Conklin Julian Elischer + Frank Durda IV Peter Dufault + Sean Eric Fagan Jeffrey Hsu + Terry Lambert L Jonas Olsson + Chris Provenzano Dave Rivers + Guido van Rooij Steven Wallace + Atsushi Murai Scott Mace + Nate Williams + + And everyone at Montana State University for their initial support. + + +Jordan would also like to give special thanks to Poul-Henning Kamp and +Gary Palmer, both of whom put in long hours helping him to construct +the new installation utility. Poul, being a proud new father, was +especially pressed for time and yet somehow managed to put in +a significant amount of effort anyway. This release could not have +happened without him! Thank you both! + +Thanks also to everyone else who helped, especially those not +mentioned, and we sincerely hope you enjoy this release of FreeBSD! + + + The FreeBSD Core Team + +$Id: RELNOTES,v 1.10 1995/06/10 09:56:30 jkh Exp $ diff --git a/release/sysinstall/help/ru_SU.KOI8-R/README b/release/sysinstall/help/ru_SU.KOI8-R/README new file mode 100644 index 0000000..53d888f --- /dev/null +++ b/release/sysinstall/help/ru_SU.KOI8-R/README @@ -0,0 +1,109 @@ + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Version , , + ----------------------------------------- /( )` + \ \___ / | +äÏÂÒÏ ÐÏÖÁÌÏ×ÁÔØ × ÒÅÌÉÚ 2.0.5 FreeBSD! 2.0.5 - /- _ `-/ ' +ÜÔÏ ÐÒÏÍÅÖÕÔÏÞÎÁÑ ×ÅÒÓÉÑ FreeBSD, ÚÁÐÏÌÎÑÀÝÁÑ (/\/ \ \ /\ +ÎÅÏÂÈÏÄÉÍÙÊ ÐÒÏÍÅÖÕÔÏË ÍÁÖÄÕ ÒÅÌÉÚÁÍÉ 2.0 (ÂÙÌ / / | ` \ +×ÙÐÕÝÅÎ × ÎÏÑÂÒÅ 1994) É 2.1, ËÏÔÏÒÙÊ ÂÕÄÅÔ O O ) / | +×ÙÐÕÝÅÎ × ËÏÎÃÅ ÉÀÌÑ 95-ÇÏ. FreeBSD 2.0.5 `-^--'`< ' +ÓÏÄÅÒÖÉÔ ÍÎÏÖÅÓÔ×Ï ÚÎÁÞÉÔÅÌØÎÙÈ ÕÓÏ×ÅÒÛÅÎÓÔ×Ï×ÁÎÉÊ, (_.) _ ) / +ÎÅ ÐÏÓÌÅÄÎÅÅ ÉÚ ËÏÔÏÒÙÈ - Õ×ÅÌÉÞÅÎÎÁÑ ÓÔÁÂÉÌØÎÏÓÔØ `.___/` / +(ÕÖÅ × ÐÒÉÅÍÌÅÍÙÈ ÐÒÅÄÅÌÁÈ), ÄÅÓÑÔËÉ ÎÏ×ÙÈ `-----' / +×ÏÚÍÏÖÎÏÓÔÅÊ, ÚÎÁÞÉÔÅÌØÎÏ ÕÌÕÞÛÅÎÎÁÑ <----. __ / __ \ +ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ. ÷ ÐÏÄÒÏÂÎÏÓÔÑÈ <----|====O)))==) \) /==== +ÎÏ×ÙÅ ×ÏÚÍÏÖÎÏÓÔÉ FreeBSD 2.0.5 <----' `--' `.__,' \ +ÏÐÉÓÁÎÙ × ÏÐÉÓÁÎÉÉ ÒÅÌÉÚÁ! | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +þÔÏ ÔÁËÏÅ FreeBSD? FreeBSD - ÜÔÏ ÏÐÅÒÁÃÉÏÎÎÁÑ ÓÉÓÔÅÍÁ, ÏÓÎÏ×ÁÎÎÁÑ ÎÁ +4.4 BSD Lite, ÐÒÅÄÎÁÚÎÁÞÅÎÎÁÑ ÄÌÑ ÐÅÒÓÏÎÁÌØÎÙÈ ËÏÍÐØÀÔÅÒÏ×, ÏÓÎÏ×ÁÎÎÙÈ +ÎÁ ÐÒÏÃÅÓÓÏÒÁÈ "x86" ÆÉÒÍ Intel, AMD, Cyrix ÉÌÉ NexGen. ïÎÁ ÐÏÄÄÅÒÖÉ×ÁÅÔ +ÍÎÏÖÅÓÔ×Ï ÒÁÚÌÉÞÎÙÈ ÐÅÒÉÆÅÒÉÊÎÙÈ ÕÓÔÒÏÊÓÔ× É ËÏÎÆÉÇÕÒÁÃÉÊ ðë É ÍÏÖÅÔ ÂÙÔØ +ÉÓÐÏÌØÚÏ×ÁÎÁ ÄÌÑ ÞÅÇÏ ÕÇÏÄÎÏ ÎÁÞÉÎÁÑ ÏÔ ÒÁÚÒÁÂÏÔËÉ ÐÒÏÇÒÁÍÍ É +ÚÁËÁÎÞÉ×ÁÑ ÐÒÅÄÏÓÔÁ×ÌÅÎÉÅÍ ÓÅÒ×ÉÓÁ ÞÅÒÅÚ ÓÅÔØ Internet; ÓÁÍÙÊ +ÚÁÇÒÕÖÅÎÎÙÊ ÓÅÒ×ÅÒ × Internet, ftp.cdrom.com ÒÁÂÏÔÁÅÔ ÐÏÄ FreeBSD! + +÷ ÜÔÏÊ ×ÅÒÓÉÉ FreeBSD ÅÓÔØ ×ÓÅ, ÞÔÏ ×ÁÍ ÎÁÄÏ ÄÌÑ ÒÁÂÏÔÙ ÔÁËÏÊ +ÓÉÓÔÅÍÙ, ÐÌÀÓ ÉÓÈÏÄÎÙÅ ÔÅËÓÔÙ ÄÌÑ ×ÓÅÇÏ ÜÔÏÇÏ. åÓÌÉ Õ ×ÁÓ ÕÓÔÁÎÏ×ÌÅÎÙ +ÉÓÈÏÄÎÙÅ ÔÅËÓÔÙ, ÔÏ ×Ù ÍÏÖÅÔÅ ÚÁÎÏ×Ï ÓËÏÍÐÉÌÉÒÏ×ÁÔØ ×ÓÀ ÓÉÓÔÅÍÕ +Ó ÎÕÌÑ ÂÕË×ÁÌØÎÏ ÏÄÎÏÊ ËÏÍÁÎÄÏÊ, ÞÔÏ ÄÅÌÁÅÔ ÅÅ ÉÄÅÁÌØÎÏÊ ÄÌÑ +ÓÔÕÄÅÎÔÏ×, ÉÓÓÌÅÄÏ×ÁÔÅÌÅÊ, ÉÌÉ ÌÀÄÅÊ, ËÏÔÏÒÙÅ ÐÒÏÓÔÏ ÈÏÔÑÔ ÐÏÓÍÏÔÒÅÔØ, +ÞÔÏ Õ ÎÅÅ ×ÎÕÔÒÉ. + +ëÒÏÍÅ ÔÏÇÏ, ÉÍÅÅÔÓÑ ÂÏÌØÛÁÑ ËÏÌÌÅËÃÉÑ ÎÅÚÁ×ÉÓÉÍÏ ÒÁÚÒÁÂÏÔÁÎÎÏÇÏ +ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ, ÐÅÒÅÎÅÓÅÎÎÏÇÏ ÐÏÄ FreeBSD ("ports +collection"), ÏÂÌÅÇÞÁÀÝÁÑ ÄÌÑ ×ÁÓ ÄÏÂÙ×ÁÎÉÅ É ÕÓÔÁÎÏ×ËÕ ×ÁÛÉÈ +ÌÀÂÉÍÙÈ ÔÒÁÄÉÃÉÏÎÎÙÈ ÕÔÉÌÉÔ UNIX ÄÌÑ FreeBSD. ïÎÁ ÓÏÓÔÏÉÔ ÉÚ ÂÏÌÅÅ 270 +ÐÁËÅÔÏ×, ÏÔ ÔÅËÓÔÏ×ÙÈ ÒÅÄÁËÔÏÒÏ× É ÑÚÙËÏ× ÐÒÏÇÒÁÍÍÉÒÏ×ÁÎÉÑ ÄÏ ÇÒÁÆÉÞÅÓËÉÈ +ÐÁËÅÔÏ×, É ÄÅÌÁÅÔ FreeBSD ÍÏÝÎÏÊ É ×ÓÅÏÈ×ÁÔÙ×ÁÀÝÅÊ ÓÉÓÔÅÍÏÊ, ËÏÔÏÒÁÑ +ÍÏÖÅÔ ÐÏÓÏÒÅ×ÎÏ×ÁÔØÓÑ Ó ÏÐÅÒÁÃÉÏÎÎÙÍÉ ÓÉÓÔÅÍÁÍÉ ÍÏÝÎÙÈ ÒÁÂÏÞÉÈ ÓÔÁÎÃÉÊ +× ÍÏÝÎÏÓÔÉ É ÐÒÅÄÏÓÔÁ×ÌÑÅÍÏÍ ÓÅÒ×ÉÓÅ. + +þÔÏÂÙ ÐÏÌÕÞÉÔØ ÂÏÌÅÅ ÐÏÌÎÕÀ ÄÏËÕÍÅÎÔÁÃÉÀ ÎÁ ÓÉÓÔÅÍÕ, ÍÙ ÓÏ×ÅÔÕÅÍ ×ÁÍ +ÐÒÉÏÂÒÅÓÔÉ ÎÁÂÏÒ ËÎÉÇ ÐÏ BSD 4.4 ÏÔ ÉÚÄÁÔÅÌØÓÔ×Á O'Reilly Associates É +ÁÓÓÏÃÉÁÃÉÉ USENIX, ISBN 1-56592-082-1. íÙ ÎÅ Ó×ÑÚÁÎÙ Ó O'Reilly, ÍÙ +ÌÉÛØ ÕÄÏ×ÌÅÔ×ÏÒÅÎÎÙÅ ÐÏËÕÐÁÔÅÌÉ! (÷ òÏÓÓÉÉ ËÎÉÇÉ O'Reilly ÐÒÏÄÁÅÔ, +ÎÁÐÒÉÍÅÒ, ÆÉÒÍÁ SWD × óÁÎËÔ-ðÅÔÅÒÂÕÒÇÅ - ÐÒÉÍ.ÐÅÒ. - Ñ Ó ÎÉÍÉ ÎÅ +Ó×ÑÚÁÎ, ÐÒÏÓÔÏ Ñ ÚÎÁÀ, ÇÄÅ ÂÙÌÉ ËÕÐÌÅÎÙ ËÎÉÇÉ, ËÏÔÏÒÙÅ Ñ ÞÉÔÁÌ) + +ðÅÒÅÄ ÔÅÍ, ËÁË ÐÒÏÄÏÌÖÉÔØ ÕÓÔÁÎÏ×ËÕ, ×Ù ÍÏÖÅÔÅ ÐÏÞÉÔÁÔØ "òÕËÏ×ÏÄÓÔ×Ï +ÐÏ ÁÐÐÁÒÁÔÕÒÅ" (HARDWARE GUIDE). ëÏÎÆÉÇÕÒÉÒÏ×ÁÎÉÅ ÁÐÐÁÒÁÔÕÒÙ ðë ÄÌÑ +ÞÅÇÏ ÕÇÏÄÎÏ ËÒÏÍÅ DOS/Windows (ËÏÔÏÒÙÅ ÎÁ ÓÁÍÏÍ ÄÅÌÅ ÉÓÐÏÌØÚÕÀÔ ÎÅ ×ÓÅ +×ÏÚÍÏÖÎÏÓÔÉ ÁÐÐÁÒÁÔÕÒÙ) ×ÓÅÇÄÁ ÏËÁÚÙ×ÁÅÔÓÑ ÎÅÓËÏÌØËÏ ÓÌÏÖÎÅÅ, ÞÅÍ ÍÏÖÅÔ +ÐÏËÁÚÁÔØÓÑ ÎÁ ÐÅÒ×ÙÊ ×ÚÇÌÑÄ, É ÅÓÌÉ ×Ù ÄÕÍÁÅÔÅ, ÞÔÏ ÐÏÎÉÍÁÅÔÅ ðë, ÔÏ +ÜÔÏ ÚÎÁÞÉÔ ÌÉÛØ ÔÏ, ÞÔÏ ×Ù ÒÁÂÏÔÁÅÔÅ Ó ÎÉÍ ÎÅÄÏÓÔÁÔÏÞÎÏ ÄÏÌÇÏ! :) üÔÏ +ÒÕËÏ×ÏÄÓÔ×Ï ÄÁÓÔ ×ÁÍ ÎÅËÏÔÏÒÙÅ ÎÁÍÅÔËÉ ÎÁÓÞÅÔ ËÏÎÆÉÇÕÒÉÒÏ×ÁÎÉÑ +ÁÐÐÁÒÁÔÕÒÙ É ÓÉÍÐÔÏÍÏ×, ÚÁ ËÏÔÏÒÙÍÉ ÎÕÖÎÏ ÓÌÅÄÉÔØ ÐÒÉ ×ÏÚÎÉËÎÏ×ÅÎÉÉ +ÐÒÏÂÌÅÍ. ïÎÏ ÄÏÓÔÕÐÎÏ ÞÅÒÅÚ ÍÅÎÀ "Documentation" ÎÁ ÚÁÇÒÕÚÏÞÎÏÊ ÄÉÓËÅÔÅ +FreeBSD. + +ðòåäïóôåòåöåîéå: èÏÔÑ FreeBSD ÄÅÌÁÅÔ ×ÓÅ ÏÔ ÎÅÅ ÚÁ×ÉÓÑÝÅÅ, ÞÔÏÂÙ +ÐÒÅÄÏÔ×ÒÁÔÉÔØ ÓÌÕÞÁÊÎÕÀ ÐÏÔÅÒÀ ÄÁÎÎÙÈ, ×ÓÅ ÒÁ×ÎÏ ×ÐÏÌÎÅ ×ÅÒÏÑÔÎÏ, ÞÔÏ +÷åóø ÷áû äéóë âõäåô óôåòô ×Ï ×ÒÅÍÑ ÜÔÏÊ ÅÅ ÕÓÔÁÎÏ×ËÉ! ðÏÖÁÌÕÊÓÔÁ, ÎÅ +ÐÒÏÄÏÌÖÁÊÔÅ ÕÓÔÁÎÏ×ËÕ, ÐÏËÁ ×Ù ÎÅ ÓÄÅÌÁÅÔÅ ÁÒÈÉ×ÎÕÀ ËÏÐÉÀ ×ÓÅÊ ×ÁÛÅÊ +×ÁÖÎÏÊ ÉÎÆÏÒÍÁÃÉÉ! íÙ ÎÅ ÛÕÔÉÍ! + +ôÅÈÎÉÞÅÓËÉÅ ËÏÍÍÅÎÔÁÒÉÉ ÐÒÏ ÜÔÕ ×ÅÒÓÉÀ ÐÏÓÙÌÁÊÔÅ ÐÏ ÁÄÒÅÓÕ (ÎÁ +ÁÎÇÌÉÊÓËÏÍ ÑÚÙËÅ): + + hackers@FreeBSD.org + +óÏÏÂÝÅÎÉÑ Ï ÏÛÉÂËÁÈ ÓÌÅÄÕÅÔ ÐÏÓÙÌÁÔØ Ó ÐÏÍÏÝØÀ ÐÒÏÇÒÁÍÍÙ `send-pr', +ÅÓÌÉ ×ÁÍ ÕÄÁÌÏÓØ ÕÓÔÁÎÏ×ÉÔØ ÓÉÓÔÅÍÕ, ÉÎÁÞÅ ÐÏ ÁÄÒÅÓÕ (É ÔÏ É ÄÒÕÇÏÅ ÎÁ +ÁÎÇÌÉÊÓËÏÍ ÑÚÙËÅ): + + bugs@FreeBSD.org + +ðÏÖÁÌÕÊÓÔÁ, × ÌÀÂÏÍ ×ÁÛÅÍ ÓÏÏÂÝÅÎÉÉ Ï ÏÛÉÂËÁÈ ÕËÁÚÙ×ÁÊÔÅ, × ëáëïê +÷åòóéé FreeBSD ×Ù ÉÈ ÏÂÎÁÒÕÖÉÌÉ! + +÷ÏÐÒÏÓÙ ÏÂÝÅÇÏ ÈÁÒÁËÔÅÒÁ ÎÁÄÏ ÐÏÓÙÌÁÔØ ÐÏ ÁÄÒÅÓÕ (ÔÏÖÅ ÎÁ ÁÎÇÌÉÊÓËÏÍ): + + questions@FreeBSD.org + +ðÏÖÁÌÕÊÓÔÁ, ÐÒÏÑ×ÉÔÅ ÐÏÎÉÍÁÎÉÅ, ÅÓÌÉ ×ÁÛÉ ×ÏÐÒÏÓÙ ÏÓÔÁÎÕÔÓÑ ÂÅÚ +ÏÔ×ÅÔÁ - ÓÅÊÞÁÓ ÄÌÑ ÎÁÓ ÏÞÅÎØ ÚÁÎÑÔÏÅ ×ÒÅÍÑ, É ÒÅÓÕÒÓÙ ÎÁÛÉÈ +ÄÏÂÒÏ×ÏÌØÃÅ× ÞÁÓÔÏ ÂÙ×ÁÀÔ ÐÏÌÎÏÓÔØÀ ÉÓÞÅÒÐÁÎÙ. óÏÏÂÝÅÎÉÑ Ï ÏÛÉÂËÁÈ, +ÐÏÓÌÁÎÎÙÅ ËÏÍÁÎÄÏÊ send-pr ÚÁÐÉÓÙ×ÁÀÔÓÑ É ÏÔÓÌÅÖÉ×ÁÀÔÓÑ × ÎÁÛÅÊ ÂÁÚÅ +ÄÁÎÎÙÈ ÓÏÏÂÝÅÎÉÊ Ï ÏÛÉÂËÁÈ, É ÍÙ ÂÕÄÅÍ ×ÁÓ ÉÎÆÏÒÍÉÒÏ×ÁÔØ ÏÂÏ ×ÓÅÈ +ÉÚÍÅÎÅÎÉÑÈ × ÔÅËÕÝÅÍ ÓÏÓÔÏÑÎÉÉ ÄÅÌ ÐÏ ÉÓÐÒÁ×ÌÅÎÉÀ ÏÛÉÂËÉ (ÉÌÉ ÐÏ +ÄÏÂÁ×ÌÅÎÉÀ ÚÁÐÒÏÛÅÎÎÙÈ ×ÁÍÉ ×ÏÚÍÏÖÎÏÓÔÅÊ). + +åÝÅ ÏÄÉÎ ÏÞÅÎØ ÈÏÒÏÛÉÊ ÉÓÔÏÞÎÉË ÏÂÎÏ×ÌÅÎÎÏÊ ÉÎÆÏÒÍÁÃÉÉ - ÜÔÏ +ÎÁÛ ÓÅÒ×ÅÒ WWW, http:://www.freebsd.org, ËÏÔÏÒÙÊ ËÒÏÍÅ ÔÏÇÏ ÓÏÄÅÒÖÉÔ +ÄÏÐÏÌÎÉÔÅÌØÎÕÀ ÄÏËÕÍÅÎÔÁÃÉÀ. äÌÑ ÄÏÓÔÕÐÁ Ë WWW ÐÒÑÍÏ ÉÚ FreeBSD ×Ù +ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ×ÅÒÓÉÀ Netscape ÏÔ BSDI. + +äÁÌØÎÅÊÛÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÓÉÓÔÅÍÅ ÓÏÄÅÒÖÉÔÓÑ × ËÁÔÁÌÏÇÁÈ /usr/share/FAQ +(ÞÁÓÔÙÅ ×ÏÐÒÏÓÙ É ÏÔ×ÅÔÙ) É /usr/share/DOC (ÄÏËÕÍÅÎÔÁÃÉÑ). + +óÐÁÓÉÂÏ ×ÁÍ ÚÁ ÔÏ, ÞÔÏ ×Ù ×ÓÅ ÜÔÏ ÐÒÏÞÌÉ, É ÍÙ ÏÞÅÎØ ÎÁÄÅÅÍÓÑ, ÞÔÏ +ÒÁÂÏÔÁ Ó ÜÔÏÊ ×ÅÒÓÉÅÊ FreeBSD ÄÏÓÔÁ×ÉÔ ×ÁÍ ÕÄÏ×ÏÌØÓÔ×ÉÅ! + + Jordan Hubbard, + ÏÔ ÉÍÅÎÉ ÐÒÏÅËÔÁ FreeBSD diff --git a/release/sysinstall/help/ru_SU.KOI8-R/configure.hlp b/release/sysinstall/help/ru_SU.KOI8-R/configure.hlp new file mode 100644 index 0000000..06e2aac --- /dev/null +++ b/release/sysinstall/help/ru_SU.KOI8-R/configure.hlp @@ -0,0 +1,16 @@ +üÔÏ ÍÅÎÀ ÐÏÚ×ÏÌÑÅÔ ×ÁÍ ÓËÏÎÆÉÇÕÒÉÒÏ×ÁÔØ ÓÉÓÔÅÍÕ ×ÓËÏÒÅ ÐÏÓÌÅ ÅÅ +ÕÓÔÁÎÏ×ËÉ. ëÁË ÍÉÎÉÍÕÍ, ×Ù ×ÅÒÏÑÔÎÏ ÄÏÌÖÎÙ ÂÕÄÅÔÅ ÕÓÔÁÎÏ×ÉÔØ ÐÁÒÏÌØ +ÓÉÓÔÅÍÎÏÇÏ ÁÄÍÉÎÉÓÔÒÁÔÏÒÁ É ×ÁÛÕ ×ÒÅÍÅÎÎÕÀ ÚÏÎÕ. + +äÏÐÏÌÎÉÔÅÌØÎÙÅ ÐÁËÅÔÙ, ÔÁËÉÅ ËÁË bash, emacs, pascal É Ô.Ä. ×ÁÍ ÓËÏÒÅÅ +×ÓÅÇÏ ÎÁÄÏ ÂÕÄÅÔ ÐÏÉÓËÁÔØ × ÁÌØÔÅÒÎÁÔÉ×Å "Packages" ÜÔÏÇÏ ÍÅÎÀ. +ðÒÁ×ÄÁ, ÓÅÊÞÁÓ ÏÔ ÜÔÏÇÏ ÎÁÞÉÎÁÎÉÑ ÂÕÄÅÔ ÐÏÌØÚÁ ÔÏÌØËÏ × ÔÏÍ ÓÌÕÞÁÅ, +ÅÓÌÉ Õ ×ÁÓ ÅÓÔØ CD-ROM ÉÌÉ ÇÏÔÏ×ÁÑ ËÏÌÌÅËÃÉÑ ÐÁËÅÔÏ× ÌÅÖÉÔ ÇÄÅ-ÔÏ × +ÆÁÊÌÏ×ÏÊ ÓÉÓÔÅÍÅ, ÔÁË ÞÔÏ ÕÔÉÌÉÔÁ ÕÐÒÁ×ÌÅÎÉÑ ÐÁËÅÔÁÍÉ ÓÍÏÖÅÔ ÉÈ ÎÁÊÔÉ. +á×ÔÏÍÁÔÉÞÅÓËÏÅ ×ÙËÁÞÉ×ÁÎÉÅ ÐÁËÅÔÏ× ÞÅÒÅÚ FTP ÅÝÅ ÎÅ ÐÏÄÄÅÒÖÁÎÏ. + +åÓÌÉ ×Ù ÚÁÈÏÔÉÔÅ ÚÁÐÕÓÔÉÔØ ÕÔÉÌÉÔÕ ÕÓÔÁÎÏ×ËÉ ÐÁËÅÔÏ× ÐÏÓÌÅ ÔÏÇÏ, ËÁË +ÚÁ×ÅÒÛÉÔÅ ÕÓÔÁÎÏ×ËÕ ÓÉÓÔÅÍÙ, ÔÏ ÚÎÁÊÔÅ, ÞÔÏ ÏÎÁ ÎÁÚÙ×ÁÅÔÓÑ +``pkg_manage''. äÌÑ ÎÁÓÔÒÏÊËÉ ×ÒÅÍÅÎÎÏÊ ÚÏÎÙ ÚÁÐÕÓÔÉÔÅ ``tzsetup''. ÷ +ÆÁÊÌÅ ``/etc/sysconfig'' ×Ù ÓÍÏÖÅÔÅ ÎÁÊÔÉ ÄÏÐÏÌÎÉÔÅÌØÎÕÀ ÉÎÆÏÒÍÁÃÉÀ ÐÏ +ÏÂÝÅÊ ËÏÎÆÉÇÕÒÁÃÉÉ ÓÉÓÔÅÍÙ. diff --git a/release/sysinstall/help/ru_SU.KOI8-R/language.hlp b/release/sysinstall/help/ru_SU.KOI8-R/language.hlp new file mode 100644 index 0000000..a6d2e21 --- /dev/null +++ b/release/sysinstall/help/ru_SU.KOI8-R/language.hlp @@ -0,0 +1,15 @@ +ó ÐÏÍÏÝØÀ ÜÔÏÇÏ ÍÅÎÀ ×Ù ÍÏÖÅÔÅ ×ÙÂÒÁÔØ ×ÁÛ ÌÀÂÉÍÙÊ ÑÚÙË. ðÒÁ×ÄÁ, ÐÏËÁ ÞÔÏ ÜÔÏ +ÐÏ×ÌÉÑÅÔ ÔÏÌØËÏ ÎÁ ÔÏ, ÎÁ ËÁËÏÍ ÑÚÙËÅ ×Ù ÐÏÌÕÞÉÔÅ ÜËÒÁÎÙ ÐÏÍÏÝÉ. + +÷ ÂÕÄÕÝÉÈ ×ÅÒÓÉÑÈ ÏÎÏ ÐÏÚ×ÏÌÉÔ ×ÁÍ ÎÁÓÔÒÏÉÔØ É ÒÁÓËÌÁÄËÕ ËÌÁ×ÉÁÔÕÒÙ, +ÜËÒÁÎÎÙÅ ÛÒÉÆÔÙ É ÕÓÔÁÎÏ×ËÉ NLS (National Language Supplement - +ðÏÄÄÅÒÖËÁ îÁÃÉÏÎÁÌØÎÙÈ ñÚÙËÏ×) (ÓÁÍ sysinstall ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ +ÒÁÚÌÉÞÎÙÅ ËÁÔÁÌÏÇÉ ÓÏÏÂÝÅÎÉÊ, ÔÁË ÞÔÏ ÍÅÎÀ ÔÏÖÅ ÂÕÄÕÔ ÎÁ ÒÁÚÌÉÞÎÙÈ +ÑÚÙËÁÈ) É ÒÅÁÌÉÚÏ×ÁÔØ ÄÒÕÇÉÅ ×ÏÚÍÏÖÎÏÓÔÉ ÉÎÔÅÒÎÁÃÉÏÎÁÌÉÚÁÃÉÉ, +ÕÄÏ×ÌÅÔ×ÏÒÑÀÝÉÅ ÒÁÚÌÉÞÎÙÍ ÓÔÁÎÄÁÒÔÁÍ. + +á ÐÏËÁ ÜÔÉ ÕÓÏ×ÅÒÛÅÎÓÔ×Ï×ÁÎÉÑ ÎÅ ÓÄÅÌÁÎÙ, ÄÌÑ ×ÁÓ ÍÏÖÅÔ ÏËÁÚÁÔØÓÑ +ÐÒÏÝÅ ×ÒÕÞÎÕÀ ÏÔÒÅÄÁËÔÉÒÏ×ÁÔØ ÆÁÊÌ /etc/sysconfig ÐÏÓÌÅ ÔÏÇÏ, ËÁË +ÓÉÓÔÅÍÁ ÂÕÄÅÔ ÕÓÔÁÎÏ×ÌÅÎÁ. üÔÏÔ ÆÁÊÌ ÓÏÄÅÒÖÉÔ ÒÑÄ ËÏÍÍÅÎÔÁÒÉÅ× Ï ÔÏÍ, +ÞÔÏ ÉÍÅÎÎÏ ÎÁÄÏ ÍÅÎÑÔØ, Á ÔÁËÖÅ ÎÅÓËÏÌØËÏ ÐÒÉÍÅÒÏ× ÓÕÝÅÓÔ×ÕÀÝÉÈ +ÎÅ-ÁÎÇÌÉÊÓËÉÈ ÎÁÓÔÒÏÅË. diff --git a/release/sysinstall/help/ru_SU.KOI8-R/usage.hlp b/release/sysinstall/help/ru_SU.KOI8-R/usage.hlp new file mode 100644 index 0000000..1b6399b --- /dev/null +++ b/release/sysinstall/help/ru_SU.KOI8-R/usage.hlp @@ -0,0 +1,60 @@ +ëáë ðïìøúï÷áôøóñ üôïê óéóôåíïê +============================== + +ëìá÷éûá äåêóô÷éå +------- -------- +óôòåìëá ÷÷åòè ðÅÒÅÊÔÉ Ë ÐÒÅÄÙÄÕÝÅÊ ÁÌØÔÅÒÎÁÔÉ×Å (ÉÌÉ ××ÅÒÈ × ÔÅËÓÔÅ). +óôòåìëá ÷îéú ðÅÒÅÊÔÉ Ë ÓÌÅÄÕÀÝÅÊ ÁÌØÔÅÒÎÁÔÉ×Å (ÉÌÉ ×ÎÉÚ × ÔÅËÓÔÅ). +TAB ðÅÒÅÊÔÉ Ë ÓÌÅÄÕÀÝÅÊ ÁÌØÔÅÒÎÁÔÉ×Å ÉÌÉ ÇÒÕÐÐÅ. +óôòåìëá ÷ðòá÷ï ðÅÒÅÊÔÉ Ë ÓÌÅÄÕÀÝÅÊ ÁÌØÔÅÒÎÁÔÉ×Å ÉÌÉ ÇÒÕÐÐÅ (ËÁË É TAB). +SHIFT-TAB ðÅÒÅÊÔÉ Ë ÐÒÅÄÙÄÕÝÅÊ ÁÌØÔÅÒÎÁÔÉ×Å ÉÌÉ ÇÒÕÐÐÅ. +óôòåìëá ÷ìå÷ï ðÅÒÅÊÔÉ Ë ÐÒÅÄÙÄÕÝÅÊ ÁÌØÔÅÒÎÁÔÉ×Å ÉÌÉ ÇÒÕÐÐÅ (ËÁË É SHIFT-TAB). +RETURN ÷ÙÂÒÁÔØ [ÜÔÕ ËÌÁ×ÉÛÕ ÔÁËÖÅ ÏÂÏÚÎÁÞÁÀÔ Enter]. +ESC úÁÐÕÓÔÉÔØ shell ÄÌÑ ÄÉÁÇÎÏÓÔÉÞÅÓËÉÈ ÃÅÌÅÊ. ðÒÉ ×ÙÈÏÄÅ + ÉÚ ÛÅÌÌÁ ×Ù ×ÅÒÎÅÔÅÓØ Ë ÔÏÍÕ ÖÅ ÍÅÓÔÕ. +PG UP ÷ ÔÅËÓÔÅ ÐÅÒÅÌÉÓÔÙ×ÁÅÔ ÎÁ ÓÔÒÁÎÉÃÕ ××ÅÒÈ. +PG DN ÷ ÔÅËÓÔÅ ÐÅÒÅÌÉÓÔÙ×ÁÅÔ ÎÁ ÓÔÒÁÎÉÃÕ ×ÎÉÚ. +ðòïâåì ÷ "ÒÁÄÉÏ"-ÍÅÎÀ (ÇÄÅ ÍÏÖÎÏ ×ÙÂÒÁÔØ ÓÒÁÚÕ ÎÅÓËÏÌØËÏ + ÁÌØÔÅÒÎÁÔÉ×) ÐÏÍÅÞÁÅÔ ÉÌÉ ÓÎÉÍÁÅÔ ÐÏÍÅÔËÕ ×ÙÂÏÒÁ Ó + ÔÅËÕÝÅÊ ÁÌØÔÅÒÎÁÔÉ×Ù. +F1 ðÏÍÏÝØ (× ÜËÒÁÎÁÈ, ÇÄÅ ÏÎÁ ÐÒÅÄÕÓÍÏÔÒÅÎÁ). + +åÓÌÉ ×Ù ×ÉÄÉÔÅ × ÕÇÏÌËÁÈ ÍÅÎÀ ÓÉÍ×ÏÌÙ "^(-)" ÉÌÉ "v(+)", ÔÏ ÜÔÏ ÏÚÎÁÞÁÅÔ, +ÞÔÏ ÓÏÏÔ×ÅÔÓÔ×ÅÎÎÏ ×ÙÛÅ ÉÌÉ ÎÉÖÅ ÔÅËÕÝÅÊ ÁÌØÔÅÒÎÁÔÉ×Ù ÅÓÔØ ÅÝÅ +ÁÌØÔÅÒÎÁÔÉ×Ù, ËÏÔÏÒÙÅ ÎÅ ÐÏËÁÚÁÎÙ, ÐÏÔÏÍÕ ÞÔÏ ÎÅ È×ÁÔÉÌÏ ÍÅÓÔÁ ÎÁ ÜËÒÁÎÅ. +ëÌÁ×ÉÛÉ ÓÏ ÓÔÒÅÌËÁÍÉ ××ÅÒÈ/×ÎÉÚ ÐÒÏËÒÕÔÑÔ ÔÁËÏÅ ÍÅÎÀ ÎÁ ÜËÒÁÎÅ. ëÏÇÄÁ +ÓÉÍ×ÏÌ ÉÓÞÅÚÁÅÔ, ÔÏ ÜÔÏ ÚÎÁÞÉÔ, ÞÔÏ ×Ù × ÓÁÍÏÍ ×ÅÒÈÕ (ÉÌÉ ÎÉÚÕ) ÍÅÎÀ. + +÷ ÔÅËÓÔÏ×ÙÈ ÐÏÌÑÈ ËÏÌÉÞÅÓÔ×Ï ÏÓÔÁ×ÛÅÇÏÓÑ ÔÅËÓÔÁ × ÐÒÏÃÅÎÔÁÈ ÐÏËÁÚÙ×ÁÅÔÓÑ × +ÐÒÁ×ÏÍ ÎÉÖÎÅÍ ÕÇÌÕ. 100% ÏÚÎÁÞÁÅÔ, ÞÔÏ ×Ù ÎÁÈÏÄÉÔÅÓØ × ÓÁÍÏÍ ÎÉÚÕ ÐÏÌÑ. + +÷ÙÂÏÒ OK × ÍÅÎÀ ÏÚÎÁÞÁÅÔ ÐÏÄÔ×ÅÒÖÄÅÎÉÅ ÄÅÊÓÔ×ÉÑ, ËÏÔÏÒÏÅ ×Ù ÚÁÐÒÏÓÉÌÉ. +÷ÙÂÏÒ ÁÌØÔÅÒÎÁÔÉ×Ù Cancel ÏÔÍÅÎÉÔ ÚÁÐÒÏÛÅÎÎÕÀ ÏÐÅÒÁÃÉÀ É × ÏÂÝÅÍ ÓÌÕÞÁÅ +×ÅÒÎÅÔ ×ÁÓ × ÐÒÅÄÙÄÕÝÅÅ ÍÅÎÀ. + + +äïðïìîéôåìøîùå ÷ïúíïöîïóôé: +=========================== + +áÌØÔÅÒÎÁÔÉ×Ù ÍÅÎÀ ÍÏÖÎÏ ÔÁËÖÅ ×ÙÂÉÒÁÔØ ÎÁÖÁÔÉÅÍ ÉÈ ÐÅÒ×ÏÊ ÂÕË×Ù (ÅÓÌÉ ÏÎÁ +ÕÎÉËÁÌØÎÁ). ôÁËÉÅ ÓÉÍ×ÏÌÙ-"ÕÓËÏÒÉÔÅÌÉ" (ÉÌÉ "ÁËÓÅÌÅÒÁÔÏÒÙ") ×ÙÄÅÌÑÀÔÓÑ ÄÒÕÇÉÍ +Ã×ÅÔÏÍ × ÎÁÚ×ÁÎÉÉ ÁÌØÔÅÒÎÁÔÉ×Ù. + +÷ ÄÒÁÊ×ÅÒÅ ËÏÎÓÏÌÉ ÔÁËÖÅ ÅÓÔØ ×ÏÚÍÏÖÎÏÓÔØ ÐÒÏËÒÕÔÉÔØ ÎÁÚÁÄ ÉÎÆÏÒÍÁÃÉÀ, +ËÏÔÏÒÁÑ ÕÖÅ "ÕÅÈÁÌÁ" Ó ÜËÒÁÎÁ (ÐÒÏËÒÕÔÉÌÁÓØ ××ÅÒÈ). äÌÑ ÜÔÏÇÏ ÎÁÖÍÉÔÅ +"Scroll Lock" (É ÐÏÔÏÍ ÏÔÐÕÓÔÉÔÅ) É Ó ÐÏÍÏÝØÀ ÓÔÒÅÌÏË É ËÌÁ×ÉÛ PgUp/PgDn ×Ù +ÓÍÏÖÅÔÅ Ä×ÉÇÁÔØ ÓÏÈÒÁÎÅÎÎÙÊ ÔÅËÓÔ (ÏÄÎÁËÏ, ÐÏÍÎÉÔÅ, ÞÔÏ ÂÕÆÅÒ ÎÅ +ÂÅÓËÏÎÅÞÅÎ). þÔÏÂÙ ×ÅÒÎÕÔØÓÑ × ÎÏÒÍÁÌØÎÙÊ ÒÅÖÉÍ, ÓÎÏ×Á ÎÁÖÍÉÔÅ "Scroll +Lock". üÔÁ ×ÏÚÍÏÖÎÏÓÔØ ÏÓÏÂÅÎÎÏ ÐÏÌÅÚÎÁ ÐÒÉ ÒÁÂÏÔÅ × ÛÅÌÌÅ ÉÌÉ ÄÒÕÇÉÈ +"ÒÅÖÉÍÁÈ ÄÌÑ ÚÎÁÔÏËÏ×", ËÏÔÏÒÙÅ ÎÅ ÉÓÐÏÌØÚÕÀÔ ÍÅÎÀ. + +ëÁË ÔÏÌØËÏ ÓÉÓÔÅÍÁ ÂÕÄÅÔ ÐÏÌÎÏÓÔØÀ ÕÓÔÁÎÏ×ÌÅÎÁ É ÚÁÐÕÝÅÎÁ × +"ÍÎÏÇÏÐÏÌØÚÏ×ÁÔÅÌØÓËÏÍ ÒÅÖÉÍÅ", ×Ù ÐÏÌÕÞÉÔÅ ÎÅÓËÏÌØËÏ "×ÉÒÔÕÁÌØÎÙÈ +ËÏÎÓÏÌÅÊ", ËÏÔÏÒÙÅ ×Ù ÓÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÄÌÑ ×ÅÄÅÎÉÑ ÎÅÓËÏÌØËÉÈ ÓÅÁÎÓÏ× +ÒÁÂÏÔÙ ÏÄÎÏ×ÒÅÍÅÎÎÏ. üËÒÁÎÙ ÐÅÒÅËÌÀÞÁÀÔÓÑ Ó ÐÏÍÏÝØÀ ËÌÁ×ÉÛ ALT-F<n>, ÇÄÅ +`F<n>' - ÜÔÏ ÆÕËÎÃÉÏÎÁÌØÎÁÑ ËÌÁ×ÉÛÁ Ó ÎÏÍÅÒÏÍ, ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÍ ÎÏÍÅÒÕ +ÜËÒÁÎÁ, ËÏÔÏÒÙÊ ×Ù ÈÏÔÉÔÅ Õ×ÉÄÅÔØ. ðÏ ÕÍÏÌÞÁÎÉÀ ÓÉÓÔÅÍÁ ÐÏÓÔÁ×ÌÑÅÔÓÑ Ó 4 +×ÉÒÔÕÁÌØÎÙÍÉ ËÏÎÓÏÌÑÍÉ. ÷Ù ÍÏÖÅÔÅ Õ×ÅÌÉÞÉÔØ ÉÈ ÞÉÓÌÏ, ÏÔÒÅÄÁËÔÉÒÏ×Á× ÆÁÊÌ +/etc/ttys ÐÏÓÌÅ ÔÏÇÏ ËÁË ÓÉÓÔÅÍÁ ÂÕÄÅÔ ÕÓÔÁÎÏ×ÌÅÎÁ, ÍÁËÓÉÍÁÌØÎÏÅ ÞÉÓÌÏ +ÒÁ×ÎÏ 12. îÅ Õ×ÌÅËÁÊÔÅÓØ ÂÏÌØÛÉÍ ÞÉÓÌÏÍ ËÏÎÓÏÌÅÊ, ÅÓÌÉ ÎÁ ×ÁÛÅÊ ÍÁÛÉÎÅ ÍÁÌÏ +ÐÁÍÑÔÉ. ðÏÄÈÏÄÑÝÉÍ ÞÉÓÌÏÍ ÄÌÑ 4 ÍÅÇÁÂÁÊÔ ÂÕÄÅÔ 4 ËÏÎÓÏÌÉ (ÉÌÉ ÄÁÖÅ ÍÅÎØÛÅ). diff --git a/release/sysinstall/help/slice.hlp b/release/sysinstall/help/slice.hlp new file mode 100644 index 0000000..e055ca4 --- /dev/null +++ b/release/sysinstall/help/slice.hlp @@ -0,0 +1,28 @@ +This is the Main Partition (or ``Slice'') Editor. + +Possible commands are printed at the bottom, and the Master Boot Record +contents are at the top. You can move up and down with the arrow keys +and can (C)reate a new partition whenever the "bar" is over a partition +whose type is set to "unused". + +The flags field has the following legend: + + '=' -- Partition is properly aligned. + '>' -- The partition doesn't end before cylinder 1024 + 'R' -- Has been marked as containing the root (/) filesystem + 'B' -- Partition employs BAD144 bad-spot handling + 'C' -- This is the FreeBSD 2.0-compatibility partition (default) + 'A' -- This partition is marked active. + +If you select a partition for Bad144 handling, it will be scanned +for bad blocks before any new filesystems are made on it. + +If no partition is marked Active, you will need to either install +a Boot Manager (the option for which will be presented later in the +installation) or set one Active before leaving this screen. + +To leave this screen, type `Q'. + +No actual changes will be made to the disk until you (C)ommit from the +Install menu! You're working with what is essentially a copy of +the disk label(s), both here and in the Label Editor. diff --git a/release/sysinstall/help/sv_SE.ISO8859-1/README b/release/sysinstall/help/sv_SE.ISO8859-1/README new file mode 100644 index 0000000..c6761e8 --- /dev/null +++ b/release/sysinstall/help/sv_SE.ISO8859-1/README @@ -0,0 +1,114 @@ + + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Version , , + ----------------------------------------- /( )` + \ \___ / | +Välkommen till FreeBSD version 2.0.5! Denna version /- _ `-/ ' +är en fyllnadsrelease av FreeBSD som täcker upp det (/\/ \ \ /\ +tomrum som bildats mellan 2.0R (som släpptes i / / | ` \ +November '94) och 2.1R, som kommer att släppas O O ) / | +i slutet av Juli '95. FreeBSD 2.0.5 innehåller `-^--'`< ' +många betydande förbättringar gentemot 2.0R, (_.) _ ) / +bland annat mycket bättre stabilitet, ett `.___/` / +dussintal nya finesser och ett förbättrat `-----' / +installationsprogram. Läs de "release <----. __ / __ \ +notes" som finns för fler detaljer om <----|====O)))==) \) /==== +vad som är nytt i 2.0.5! <----' `--' `.__,' \ + | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +Vad är FreeBSD? FreeBSD är ett operativsystem för Intel, AMD, Cyrix och +NexGen "x86"-baserad PC-hårdvara. FreeBSD är baserat på 4.4 BSD Lite. +Det fungerar med en stor mängd olika tillbehör och konfigurationer och +kan användas för allt från mjukvaruutveckling till att tillhandahålla +Internet-tjänster; det mest använda systemet på Internet, ftp.cdrom.com, är +en FreeBSD-maskin! + +Denna version av FreeBSD innehåller allt du behöver för att köra ett +sådant system. Fullständig källkod till allting ingår också. +Med källkodsdistributionen installerad kan du bokstavligt talat kompilera +om hela systemet från början med ett enda kommando. Detta gör FreeBSD +perfekt för studenter, forskare och de som helt enkelt vill undersöka +hur saker fungerar. + + +En stor samling av programvara anpassad till FreeBSD av olika personer +("the ports collection") följer också med. Mer än 270 programpaket +innehållande allt från editorer till programspråk och grafikverktyg, +detta underlättar för dig att installera alla dina favoritprogram +under unix för FreeBSD. Detta gör FreeBSD till ett kraftfullt och +innehållsrikt operativsystem som utmanar det som många större arbets- +stationer har när det gäller kraftfullhet och allmän användbarhet. + + +För mer information om detta system rekommenderas du att beställa +"4.4BSD Document Set" från O'Reilly Associates och USENIX Association, +ISBN 1-56592-082-1. Vi har inget samarbete med O'Reilly, vi är bara +nöjda kunder! + + +Du kan också vilja läsa den hårdvaruguide som finns *innan* du fortsätter +installationen. Att konfigurera PC-hårdvara för någonting annat än DOS/Windows +(som egentligen inte ställer så höga krav på hårdvaran) är faktiskt svårare +än det ser ut att vara. Om du tror du förstår dig på PC:ar har du uppenbarligen +inte använt dem tillräckligt länge! :) Guiden ger dig en del tips om hur du +skall konfigurera din hårdvara och de symptom du skall vara uppmärksam på +om du får problem. Den finns tillgänglig under menyn "Documentation" som +finns på FreeBSD-startdisketten. + + +OBSERVERA: FreeBSD gör sitt bästa för att du inte skall förlora någon +information, men det är möjligt att RADERA HELA HÅRDDISKEN med denna +installation! Fortsätt inte till sista FreeBSD-installationsmenyn om du +inte har någon säkerhetskopia på all din väsentliga information! Vi menar +det verkligen! + + +Tekniska kommentarer om denna version sänds (på engelska!) till: + + + hackers@FreeBSD.org + + +Felrapporter bör sändas med hjälp av kommandot 'send-pr' om du lyckats +installera systemet, i annat fall till: + + bugs@FreeBSD.org + +Var noga med att uppge VILKEN VERSION av FreeBSD du kör i alla felrapporter! + + +Allmänna frågor bör sändas till: + + questions@FreeBSD.org + + +Var tålmodig om dina frågor inte besvaras omgående - detta är en hektisk +tid för oss, och våra frivilliga tillgångar är ofta belastade till +bristningsgränsen! Felrapporter som skickas med kommandot send-pr +loggas och registreras i vår feldatabas, och du hålls informerad om alla +förändringar som sker under felets livstid (eller, om du kommer med +förslag på förbättringar, hur dessa utvecklas). + + +Vår WEB-server, http://www.freebsd.org, är en bra källa för uppdaterad +information och tillhandahåller ett antal advancerade dokumentations- +finesser. Du kan använda den version av Netscape som finns för BSDI för +att orientera dig runt i World Wide Web direkt under FreeBSD. + + +Du kan även vilja ta en titt i /usr/share/FAQ och /usr/share/doc för mer +information om systemet. + + +Tack för att du tog dig tid för att läsa detta, och vi hoppas verkligen att +du uppskattar denna release av FreeBSD! + + + + Jordan Hubbard, + för The FreeBSD Project diff --git a/release/sysinstall/help/sv_SE.ISO8859-1/configure.hlp b/release/sysinstall/help/sv_SE.ISO8859-1/configure.hlp new file mode 100644 index 0000000..ee64008 --- /dev/null +++ b/release/sysinstall/help/sv_SE.ISO8859-1/configure.hlp @@ -0,0 +1,15 @@ +I denna meny konfigurerar du systemet efter installationen. Du bör +åtminstone sätta ett lösenord för root och ändra till rätt tidszon. + +För extra tillval såsom bash, emacs, pascal med flera vill du nog titta på +valet "Packages" i denna meny. Observera att detta val ännu så länge endast +ger något om du har ett CDROM eller samlingen av programpaket någonstans +på hårddisken där packages-hanteraren kan hitta den. Automatisk hämtning av +packages via FTP stöds ännu så länge inte! + + +Om du vill starta package-installeraren efter systeminstallationen +kan du använda kommandot ``pkg_manage''. För att ändra tidszon +använder du kommandot ``tzsetup''. +För mer information om systemkonfiguration hänvisas du till filen +``/etc/sysconfig''. diff --git a/release/sysinstall/help/sv_SE.ISO8859-1/language.hlp b/release/sysinstall/help/sv_SE.ISO8859-1/language.hlp new file mode 100644 index 0000000..3cadc5f --- /dev/null +++ b/release/sysinstall/help/sv_SE.ISO8859-1/language.hlp @@ -0,0 +1,14 @@ +Använd denna meny för att välja språk. För närvarande ändrar detta +endast det språk som används i hjälptexterna. + +I senare versioner kommer detta även att ändra tangentbordslayouten, +skärmens teckenuppsättning, NLS-inställningarna (själva sysinstall +kommer att använda meddelandekataloger så att alla menyer blir +i det språk du valt) och ändra andra I18N-finesser för att uppfylla +olika konventioner. + + +Innan dessa förbättringar är gjorda kanske du föredrar att ändra i +filen /etc/sysconfig för hand när systemet är installerat. +I filen finns det gott om kommentarer som beskriver vad du skall ändra, +inklusive några exempel på icke-engelska inställningar. diff --git a/release/sysinstall/help/sv_SE.ISO8859-1/usage.hlp b/release/sysinstall/help/sv_SE.ISO8859-1/usage.hlp new file mode 100644 index 0000000..1f544b9 --- /dev/null +++ b/release/sysinstall/help/sv_SE.ISO8859-1/usage.hlp @@ -0,0 +1,49 @@ +HUR DU ANVÄNDER DETTA SYSTEM +============================ + +TANGENT FUNKTION +------- -------- +PIL UPPÅT Flytta till föregående rad (eller uppåt i ett textfält). +PIL NEDÅT Flytta till nästa rad (eller nedåt i ett textfält). +TAB Flytta till nästa fält. +PIL HÖGER Flytta till nästa fält (samma som TAB). +SHIFT-TAB Flytta till föregående fält. +PIL VÄNSTER Flytta till föregående fält (samma som SHIFT-TAB). +RETURN Markera rad eller utför handling. +PAGE UP Flyttar upp texten en sida i textfält. +PAGE DOWN Flyttar ner texten en sida i textfält. +MELLANSLAG Markera/avmarkera gällande val i flervalsmenyer. +F1 Hjälp (på de skärmbilder som tillhandahåller det). + +Om du ser symbolerna "^(-)" eller "v(+)" vid kanten av en meny, betyder +det att det finns fler val ovanför eller under de val du just ser, som inte +visas (på grund av de inte ryms på skärmen). Med hjälp av pil uppåt eller nedåt +kan du rulla fram dessa val. När en symbol försvinner innebär det att du +befinner dig längst upp eller ner på en meny. + +I ett textfält visas storleken av den återstående texten procentuellt +i det nedre högra hörnet. 100% innebär att du är vid slutet av texten. + +Välj "OK" för att bekräfta menyvalen. +"Avbryt" för dig normalt tillbaka till föregående meny. + + +ADVANCERADE FUNKTIONER: +======================= + +Det är möjligt att flytta till ett val genom att skriva dess första tecken +om detta är unikt. Sådana snabbval är markerade i texten. + +Skärmdrivrutinen innehåller ett minne för text som har rullat förbi +på skärmen. För att återse trycker du på "Scroll Lock"-tangenten och +använder piltangenterna och Page Up/Page Down för att förflytta dig i +texten. För att sluta återse trycker du på "Scroll Lock"-tangenten igen. +Denna funktion är till störst nytta när du använder en kommandotolk +eller någon annat "expertläge". + +När systemet är färdiginstallerat och igång kommer du att kunna byta +mellan flera "virtuella skärmar". På så sätt kan du ha flera sessioner +öppna samtidigt. Använd ALT-F<n> för att byta mellan dem. +Från början finns det fyra sessioner att byta mellan. När systemet till +slut är uppe kan du ändra det genom att editera filen /etc/ttys. +Maximalt antal virtuella skärmar är 12. diff --git a/release/sysinstall/help/sv_SE.ISO_8859-1/README b/release/sysinstall/help/sv_SE.ISO_8859-1/README new file mode 100644 index 0000000..c6761e8 --- /dev/null +++ b/release/sysinstall/help/sv_SE.ISO_8859-1/README @@ -0,0 +1,114 @@ + + ----------------------------------------- + FreeBSD 2.0.5 --- RELEASE Version , , + ----------------------------------------- /( )` + \ \___ / | +Välkommen till FreeBSD version 2.0.5! Denna version /- _ `-/ ' +är en fyllnadsrelease av FreeBSD som täcker upp det (/\/ \ \ /\ +tomrum som bildats mellan 2.0R (som släpptes i / / | ` \ +November '94) och 2.1R, som kommer att släppas O O ) / | +i slutet av Juli '95. FreeBSD 2.0.5 innehåller `-^--'`< ' +många betydande förbättringar gentemot 2.0R, (_.) _ ) / +bland annat mycket bättre stabilitet, ett `.___/` / +dussintal nya finesser och ett förbättrat `-----' / +installationsprogram. Läs de "release <----. __ / __ \ +notes" som finns för fler detaljer om <----|====O)))==) \) /==== +vad som är nytt i 2.0.5! <----' `--' `.__,' \ + | | + \ / /\ + ______( (_ / \______/ + ,' ,-----' | + `--{__________) + + +Vad är FreeBSD? FreeBSD är ett operativsystem för Intel, AMD, Cyrix och +NexGen "x86"-baserad PC-hårdvara. FreeBSD är baserat på 4.4 BSD Lite. +Det fungerar med en stor mängd olika tillbehör och konfigurationer och +kan användas för allt från mjukvaruutveckling till att tillhandahålla +Internet-tjänster; det mest använda systemet på Internet, ftp.cdrom.com, är +en FreeBSD-maskin! + +Denna version av FreeBSD innehåller allt du behöver för att köra ett +sådant system. Fullständig källkod till allting ingår också. +Med källkodsdistributionen installerad kan du bokstavligt talat kompilera +om hela systemet från början med ett enda kommando. Detta gör FreeBSD +perfekt för studenter, forskare och de som helt enkelt vill undersöka +hur saker fungerar. + + +En stor samling av programvara anpassad till FreeBSD av olika personer +("the ports collection") följer också med. Mer än 270 programpaket +innehållande allt från editorer till programspråk och grafikverktyg, +detta underlättar för dig att installera alla dina favoritprogram +under unix för FreeBSD. Detta gör FreeBSD till ett kraftfullt och +innehållsrikt operativsystem som utmanar det som många större arbets- +stationer har när det gäller kraftfullhet och allmän användbarhet. + + +För mer information om detta system rekommenderas du att beställa +"4.4BSD Document Set" från O'Reilly Associates och USENIX Association, +ISBN 1-56592-082-1. Vi har inget samarbete med O'Reilly, vi är bara +nöjda kunder! + + +Du kan också vilja läsa den hårdvaruguide som finns *innan* du fortsätter +installationen. Att konfigurera PC-hårdvara för någonting annat än DOS/Windows +(som egentligen inte ställer så höga krav på hårdvaran) är faktiskt svårare +än det ser ut att vara. Om du tror du förstår dig på PC:ar har du uppenbarligen +inte använt dem tillräckligt länge! :) Guiden ger dig en del tips om hur du +skall konfigurera din hårdvara och de symptom du skall vara uppmärksam på +om du får problem. Den finns tillgänglig under menyn "Documentation" som +finns på FreeBSD-startdisketten. + + +OBSERVERA: FreeBSD gör sitt bästa för att du inte skall förlora någon +information, men det är möjligt att RADERA HELA HÅRDDISKEN med denna +installation! Fortsätt inte till sista FreeBSD-installationsmenyn om du +inte har någon säkerhetskopia på all din väsentliga information! Vi menar +det verkligen! + + +Tekniska kommentarer om denna version sänds (på engelska!) till: + + + hackers@FreeBSD.org + + +Felrapporter bör sändas med hjälp av kommandot 'send-pr' om du lyckats +installera systemet, i annat fall till: + + bugs@FreeBSD.org + +Var noga med att uppge VILKEN VERSION av FreeBSD du kör i alla felrapporter! + + +Allmänna frågor bör sändas till: + + questions@FreeBSD.org + + +Var tålmodig om dina frågor inte besvaras omgående - detta är en hektisk +tid för oss, och våra frivilliga tillgångar är ofta belastade till +bristningsgränsen! Felrapporter som skickas med kommandot send-pr +loggas och registreras i vår feldatabas, och du hålls informerad om alla +förändringar som sker under felets livstid (eller, om du kommer med +förslag på förbättringar, hur dessa utvecklas). + + +Vår WEB-server, http://www.freebsd.org, är en bra källa för uppdaterad +information och tillhandahåller ett antal advancerade dokumentations- +finesser. Du kan använda den version av Netscape som finns för BSDI för +att orientera dig runt i World Wide Web direkt under FreeBSD. + + +Du kan även vilja ta en titt i /usr/share/FAQ och /usr/share/doc för mer +information om systemet. + + +Tack för att du tog dig tid för att läsa detta, och vi hoppas verkligen att +du uppskattar denna release av FreeBSD! + + + + Jordan Hubbard, + för The FreeBSD Project diff --git a/release/sysinstall/help/sv_SE.ISO_8859-1/configure.hlp b/release/sysinstall/help/sv_SE.ISO_8859-1/configure.hlp new file mode 100644 index 0000000..ee64008 --- /dev/null +++ b/release/sysinstall/help/sv_SE.ISO_8859-1/configure.hlp @@ -0,0 +1,15 @@ +I denna meny konfigurerar du systemet efter installationen. Du bör +åtminstone sätta ett lösenord för root och ändra till rätt tidszon. + +För extra tillval såsom bash, emacs, pascal med flera vill du nog titta på +valet "Packages" i denna meny. Observera att detta val ännu så länge endast +ger något om du har ett CDROM eller samlingen av programpaket någonstans +på hårddisken där packages-hanteraren kan hitta den. Automatisk hämtning av +packages via FTP stöds ännu så länge inte! + + +Om du vill starta package-installeraren efter systeminstallationen +kan du använda kommandot ``pkg_manage''. För att ändra tidszon +använder du kommandot ``tzsetup''. +För mer information om systemkonfiguration hänvisas du till filen +``/etc/sysconfig''. diff --git a/release/sysinstall/help/sv_SE.ISO_8859-1/language.hlp b/release/sysinstall/help/sv_SE.ISO_8859-1/language.hlp new file mode 100644 index 0000000..3cadc5f --- /dev/null +++ b/release/sysinstall/help/sv_SE.ISO_8859-1/language.hlp @@ -0,0 +1,14 @@ +Använd denna meny för att välja språk. För närvarande ändrar detta +endast det språk som används i hjälptexterna. + +I senare versioner kommer detta även att ändra tangentbordslayouten, +skärmens teckenuppsättning, NLS-inställningarna (själva sysinstall +kommer att använda meddelandekataloger så att alla menyer blir +i det språk du valt) och ändra andra I18N-finesser för att uppfylla +olika konventioner. + + +Innan dessa förbättringar är gjorda kanske du föredrar att ändra i +filen /etc/sysconfig för hand när systemet är installerat. +I filen finns det gott om kommentarer som beskriver vad du skall ändra, +inklusive några exempel på icke-engelska inställningar. diff --git a/release/sysinstall/help/sv_SE.ISO_8859-1/usage.hlp b/release/sysinstall/help/sv_SE.ISO_8859-1/usage.hlp new file mode 100644 index 0000000..1f544b9 --- /dev/null +++ b/release/sysinstall/help/sv_SE.ISO_8859-1/usage.hlp @@ -0,0 +1,49 @@ +HUR DU ANVÄNDER DETTA SYSTEM +============================ + +TANGENT FUNKTION +------- -------- +PIL UPPÅT Flytta till föregående rad (eller uppåt i ett textfält). +PIL NEDÅT Flytta till nästa rad (eller nedåt i ett textfält). +TAB Flytta till nästa fält. +PIL HÖGER Flytta till nästa fält (samma som TAB). +SHIFT-TAB Flytta till föregående fält. +PIL VÄNSTER Flytta till föregående fält (samma som SHIFT-TAB). +RETURN Markera rad eller utför handling. +PAGE UP Flyttar upp texten en sida i textfält. +PAGE DOWN Flyttar ner texten en sida i textfält. +MELLANSLAG Markera/avmarkera gällande val i flervalsmenyer. +F1 Hjälp (på de skärmbilder som tillhandahåller det). + +Om du ser symbolerna "^(-)" eller "v(+)" vid kanten av en meny, betyder +det att det finns fler val ovanför eller under de val du just ser, som inte +visas (på grund av de inte ryms på skärmen). Med hjälp av pil uppåt eller nedåt +kan du rulla fram dessa val. När en symbol försvinner innebär det att du +befinner dig längst upp eller ner på en meny. + +I ett textfält visas storleken av den återstående texten procentuellt +i det nedre högra hörnet. 100% innebär att du är vid slutet av texten. + +Välj "OK" för att bekräfta menyvalen. +"Avbryt" för dig normalt tillbaka till föregående meny. + + +ADVANCERADE FUNKTIONER: +======================= + +Det är möjligt att flytta till ett val genom att skriva dess första tecken +om detta är unikt. Sådana snabbval är markerade i texten. + +Skärmdrivrutinen innehåller ett minne för text som har rullat förbi +på skärmen. För att återse trycker du på "Scroll Lock"-tangenten och +använder piltangenterna och Page Up/Page Down för att förflytta dig i +texten. För att sluta återse trycker du på "Scroll Lock"-tangenten igen. +Denna funktion är till störst nytta när du använder en kommandotolk +eller någon annat "expertläge". + +När systemet är färdiginstallerat och igång kommer du att kunna byta +mellan flera "virtuella skärmar". På så sätt kan du ha flera sessioner +öppna samtidigt. Använd ALT-F<n> för att byta mellan dem. +Från början finns det fyra sessioner att byta mellan. När systemet till +slut är uppe kan du ändra det genom att editera filen /etc/ttys. +Maximalt antal virtuella skärmar är 12. diff --git a/release/sysinstall/help/tcp.hlp b/release/sysinstall/help/tcp.hlp new file mode 100644 index 0000000..3ab5d7c --- /dev/null +++ b/release/sysinstall/help/tcp.hlp @@ -0,0 +1,27 @@ +This screen allows you to set up your general network parameters +(hostname, domain name, DNS server, etc) as well as the settings for a +given interface (which was selected from the menu before this screen). + +You can move through the fields with the TAB, BACK-TAB and RETURN +keys. To edit a field, use DELETE or BACKSPACE. You may also use ^A +(control-A) to go to the beginning of the line, ^E (control-E) to go +to the end, ^F (control-F) to go forward a character, ^B (control-B) +to go backward one character, ^D (control-D) to delete the character +under the cursor and ^K (control-K) to delete to the end of the line. +Basically, the standard EMACS motion sequences. + +The ``Extra options to ifconfig'' is kind of special (read: a hack :-). + +You can use it for specifying the foreign side of a PLIP or SLIP line +(simply type the foreign address in) as well as selecting a given +"link" on an ethernet card that has more than one (e.g. AUI, 10BT, +10B2, etc). The following links are recognised: + + link0 - AUI * highest precedence + link1 - BNC + link2 - UTP * lowest precedence + +That is to say that you can enter one of "link0", "link1" or "link2" +into the `Extra options' field to select a different link. + +When you're done with this form, select OK. diff --git a/release/sysinstall/help/upgrade.hlp b/release/sysinstall/help/upgrade.hlp new file mode 100644 index 0000000..5cba594 --- /dev/null +++ b/release/sysinstall/help/upgrade.hlp @@ -0,0 +1,38 @@ +Welcome to the 2.0.5 -> 2.1 upgrade procedure! + +It must first be said that this upgrade DOES NOT take a particularly +sophisticated approach to the upgrade problem, it being more a question +of providing what seemed "good enough" at the time. A truly polished +upgrade that deals properly with the broad spectrum of installed 2.0.5 +systems would be nice to have, but until that gets written what you get is +this - the brute-force approach! + +What this upgrade will attempt to do is best summarized thusly: + + 1. fsck and mount all file systems chosen in the label editor. + 2. Ask for a location to preserve your /etc directory into and do so. + 3. Extract all selected distributions on top of your existing system. + 4. Copy certain obvious files back from the preserved /etc, leaving the + rest of the /etc file merge up to the user. + 5. Drop user in a shell so that they may perform that merge before + rebooting into the new system. + +And that's it! This "upgrade" is not going to hold your hand in all +major respects, it's simply provided to make one PART of the upgrade +easier. + +IMPORTANT NOTE: What this upgrade procedure may also do, in fact, is +completely destroy your system (though much more quickly than you +would have been able to destroy it yourself). It is simply impossible +to guarantee that this procedure's crude form of upgrade automation +will work in all cases and if you do this upgrade without proper +BACKUPS for any important data then you really must like living life +close to the edge, that's all we can say! + +NOTE to 2.0 users: We're sorry, but the "slice" changes that were +added in FreeBSD 2.0.5 made automated upgrades pretty difficult due to +the fact that a complete reinstall is pretty much called for. Things +may still *work* after a 2.1 upgrade, but you will also no doubt +receive many warnings at boot time about non-aligned slices and such; +we really do recommend a fresh installation for 2.0 systems! (But +back up your user data first :-). diff --git a/release/sysinstall/help/usage.hlp b/release/sysinstall/help/usage.hlp new file mode 100644 index 0000000..b01a94b --- /dev/null +++ b/release/sysinstall/help/usage.hlp @@ -0,0 +1,54 @@ +HOW TO USE THIS SYSTEM +====================== + +KEY ACTION +--- ------ +UP ARROW Move to previous item (or up, in a text field). +DOWN ARROW Move to next item (or down, in a text field). +TAB Move to next item or group. +RIGHT ARROW Move to next item or group (same as TAB). +SHIFT-TAB Move to previous item or group. +LEFT ARROW Move to previous item or group (same as SHIFT-TAB). +RETURN Select item. +PAGE UP In text boxes, scrolls up one page. +PAGE DOWN In text boxes, scrolls down one page. +SPACE In "radio" or multiple choice menus, toggle the current item. +F1 Help (in screens that provide it). + +If you also see small "^(-)" or "v(+)" symbols at the edges of a menu, +it means that there are more items above or below the current one that +aren't being shown (due to insufficient screen space). Using the +up/down arrow keys will cause the menu to scroll. When a symbol +disappears, it means you are at the top (or bottom) of the menu. + +In text fields, the amount of text above the current point will be +displayed as a percentage in the lower right corner. 100% means +you're at the bottom of the field. + +Selecting OK in a menu will confirm whatever action it's controlling. +Selecting Cancel will cancel the operation and generally return you to +the previous menu. + + +SPECIAL FEATURES: +================= + +It is also possible to select a menu item by typing the first +character of its name, if unique. Such "accelerator" characters will +be specially highlighted in the item name. + +The console driver also contains a scroll-back buffer for reviewing +things that may have scrolled off the screen. To use scroll-back, +press the "Scroll Lock" key on your keyboard and use the arrow or +Page Up/Page Down keys to move through the saved text. To leave +scroll-back mode, press the Scroll Lock key again. This feature +is most useful for dealing with sub-shells or other "wizard modes" +that don't use menus. + +Once the system is fully installed and running "multi-user", you will +also find that you have multiple "virtual consoles" and can use them to +have several active sessions at once. Use ALT-F<n> to switch between +them, where `F<n>' is the function key corresponding to the screen you +wish to see. By default, the system comes with 3 virtual consoles enabled. +You can create more by editing the /etc/ttys file, once the system is up, +for a maximum of 12. |
