[BACK]Return to netbsd-en.txt CVS log [TXT][DIR] Up to [cvs.NetBSD.org] / htdocs / docs / guide / download

Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files.

Diff for /htdocs/docs/guide/download/netbsd-en.txt between version 1.2 and 1.3

version 1.2, 2018/07/31 23:53:44 version 1.3, 2018/08/23 18:43:32
Line 1297  The NetBSD install program sysinst allow
Line 1297  The NetBSD install program sysinst allow
 during the installation. If for some reason this does not work for you, you can  during the installation. If for some reason this does not work for you, you can
 use the map in the following table.  use the map in the following table.
   
 +-----------+  +-------------+
 |US|IT|DE|FR|  |US| IT |DE|FR|
 |--+--+--+--|  |--+----+--+--|
 |- |' |  |) |  |- | '  |ss|) |
 |--+--+--+--|  |--+----+--+--|
 |/ |- |- |! |  |/ | -  |- |! |
 |--+--+--+--|  |--+----+--+--|
 |= |  |' |- |  |= | i` |' |- |
 |--+--+--+--|  |--+----+--+--|
 |: |  |  |M |  |: | c, |O:|M |
 |--+--+--+--|  |--+----+--+--|
 |; |  |  |m |  |; | o` |o:|m |
 |--+--+--+--|  |--+----+--+--|
 |# |  |  |3 |  |# |-L- |S:|3 |
 |--+--+--+--|  |--+----+--+--|
 |" |  |  |% |  |" |DEG |A:|% |
 |--+--+--+--|  |--+----+--+--|
 |* |( |( |8 |  |* | (  |( |8 |
 |--+--+--+--|  |--+----+--+--|
 |( |) |) |9 |  |( | )  |) |9 |
 |--+--+--+--|  |--+----+--+--|
 |) |= |= |0 |  |) | =  |= |0 |
 |--+--+--+--|  |--+----+--+--|
 |' |  |  |  |  |' | a` |a:|u`|
 |--+--+--+--|  |--+----+--+--|
 |` |\ |^ |@ |  |` | \  |^ |@ |
 |--+--+--+--|  |--+----+--+--|
 |\ |  |# |` |  |\ | u` |# |` |
 +-----------+  +-------------+
   
 3.4. Starting the installation  3.4. Starting the installation
   
Line 4028  Table of Contents
Line 4028  Table of Contents
   
 9.1. What is X?  9.1. What is X?
   
 NetBSD uses the X Window System to provide a graphical interface. In NetBSD  NetBSD uses the X Window System (from X.Org) to provide a graphical interface.
 5.0, the amd64, i386, macppc, shark, sgimips, and sparc64 ports use X.Org and  
 the rest use XFree86.  
   
 Please note that the X Window System is a rather bare bones framework. It acts  Please note that the X Window System is a rather bare bones framework. It acts
 as a base for modern desktop environments like GNOME or KDE, but they are not  as a base for modern desktop environments like GNOME or KDE, but they are not
Line 4044  at first. The basic elements are:
Line 4042  at first. The basic elements are:
   
   * An X server running on top of the hardware. The X server provides a    * An X server running on top of the hardware. The X server provides a
     standard way to display graphics (including fonts for text display) and get      standard way to display graphics (including fonts for text display) and get
     mouse/keyboard/other input. X is network-transparent, which means that you      mouse/keyboard/other input.
     can run X clients on one machine, and the X server (i.e., the display, with  
     video hardware) on another machine.  
   
   * X clients. These are the programs you directly interact with. They run on    * X clients. These are the programs you directly interact with. They run on
     top of the X server. A web browser like Firefox is an example of an X      top of the X server. A web browser like Firefox is an example of an X
     client.      client. X is network-transparent, which means that you can run X clients on
       one machine, and the X server (i.e., the display, with video hardware) on
       another machine.
   
   * A window manager running on top of the X server. The window manager is a    * A window manager running on top of the X server. The window manager is a
     special X client that is allowed to control the placement of windows. It      special X client that is allowed to control the placement of windows. It
Line 4067  at first. The basic elements are:
Line 4065  at first. The basic elements are:
   
 9.2. Configuration  9.2. Configuration
   
 In some cases, you may be able to start using X without any configuration at  In most cases, you will be able to start using X without any configuration at
 all, and startx will work just fine. In many cases, however, some configuration  all, and startx will work just fine. In rare cases, however, configuration of
 of the X server is required. Depending on the port you use, this configuration  the X server is required. This configuration file is located at /etc/X11/
 file will be either /etc/X11/xorg.conf or /etc/X11/XF86Config. The structure of  xorg.conf. The structure of the configuration file is described formally in
 the configuration file is described formally in xorg.conf(5) or XF86Config(5).  xorg.conf(5).
   
 To generate an initial configuration file for your X server, run the command  To generate an initial configuration file for your X server, run the command
   
Line 4084  directory. To test the generated configu
Line 4082  directory. To test the generated configu
   
 If this succeeds, you should see a crosshatched background and a cursor in the  If this succeeds, you should see a crosshatched background and a cursor in the
 shape of an X. Try moving the cursor around to verify that the mouse is  shape of an X. Try moving the cursor around to verify that the mouse is
 functional. To quit, press Ctrl-Alt-Backspace.  functional. You can then switch to another virtual terminal (Ctrl-Alt-F#) or
   log in remotely and kill the X process.
   
 If the above test was successful, move the file into place (as either /etc/X11/  If the above test was successful, move the file into place as /etc/X11/
 xorg.conf or /etc/X11/XF86Config) and you are ready to go. The following  xorg.conf and you are ready to go.
 sections may be of interest or use, but are not required reading.  
   
 9.3. The mouse  9.3. The mouse
   
Line 4103  Section "InputDevice"
Line 4101  Section "InputDevice"
         Option      "ZAxisMapping" "4 5 6 7"          Option      "ZAxisMapping" "4 5 6 7"
 EndSection  EndSection
   
 For a serial mouse on the first serial port, try something like:  
   
 Section "InputDevice"  
         Identifier  "Mouse0"  
         Driver      "mouse"  
         Option      "Protocol" "auto"  
         Option      "Device" "/dev/tty00"  
 EndSection  
   
 In this example. /dev/tty00 is the first serial port. Use /dev/tty01 for the  
 second, and so on. Protocol "auto" will try to automatically detect the  
 protocol of your serial mouse. If this doesn't work, try values like  
 "Microsoft", "IntelliMouse" or "Logitech". See mousedrv(4) for more  
 information.  
   
 9.4. The keyboard  9.4. The keyboard
   
 Even if you have already configured your keyboard for wscons (See Section 8.1,  Even if you have already configured your keyboard for wscons (See Section 8.1,
Line 4165  listed in that command's output, you can
Line 4148  listed in that command's output, you can
   
 $ xrandr -s 1680x1050  $ xrandr -s 1680x1050
   
 If your preferred resolution is not listed, or you have issues with flickering,  
 you may need to manually specify your monitor's horizontal and vertical  
 frequencies. These can be set with the "HorizSync" and "VertRefresh" directives  
 in the "Monitor" section. An example is provided below.  
   
 Section "Monitor"  
         Identifier   "Monitor0"  
         VendorName   "Monitor Vendor"  
         ModelName    "Monitor Model"  
         HorizSync    30-83  
         VertRefresh  56-75  
 EndSection  
   
 9.6. The video card  9.6. The video card
   
 Normally, your video card will be automatically detected. In the event that  Normally, your video card will be automatically detected. In the event that
 this autodetection fails, all available drivers can be found in /usr/X11R7/lib/  this autodetection fails, all available drivers can be found in /usr/X11R7/lib/
 modules/drivers. (Replace "X11R7" with "X11R6" if you use a port that has not  modules/drivers. The driver can be set with the "Driver" directive in the "
 yet switched to X.Org.) The driver can be set with the "Driver" directive in  Device" section, as shown below.
 the "Device" section, as shown below.  
   
 Section "Device"  Section "Device"
         Identifier  "Card0"          Identifier  "Card0"
Line 4218  instance of the xclock and xterm program
Line 4187  instance of the xclock and xterm program
 to "bisque4", which is defined in /usr/X11R7/lib/X11/rgb.txt.  to "bisque4", which is defined in /usr/X11R7/lib/X11/rgb.txt.
   
 ...  ...
 # start some nice programs  # start some programs
 xclock -geometry 50x50-1-1 &  xclock -geometry 50x50-1-1 &
 xsetroot -solid bisque4 &  xsetroot -solid bisque4 &
 xterm -geometry 80x34-1+1 -bg OldLace &  xterm -geometry 80x34-1+1 -bg OldLace &
Line 4260  xclock -geometry 50x50-1-1 &
Line 4229  xclock -geometry 50x50-1-1 &
 exec openbox   # no '&' here  exec openbox   # no '&' here
   
 The startx command will start the X11 session with Openbox. As configured in  The startx command will start the X11 session with Openbox. As configured in
 the example .xinitrc file above, choosing "Exit" or similar from the window  the example .xinitrc file above, choosing "Log Out" from Openbox's menu will
 manager's menu will quit the window manager and end the X11 session.  end the X11 session.
   
 Installing a desktop environment is almost as easy. The following example shows  Installing a desktop environment is almost as easy. The following example shows
 how to use the Xfce desktop environment.  how to use the Xfce desktop environment.
Line 4309  different virtual console, change vt05 a
Line 4278  different virtual console, change vt05 a
 contention between getty and xdm, be sure to start xdm on a virtual terminal  contention between getty and xdm, be sure to start xdm on a virtual terminal
 where getty is disabled. For example, if in Xservers you have:  where getty is disabled. For example, if in Xservers you have:
   
 :0 local /usr/X11R6/bin/X :0 vt04  :0 local /usr/X11R7/bin/X :0 vt04
   
 then in /etc/ttys you should have  then in /etc/ttys you should have
   
 ttyE3   "/usr/libexec/getty Pc"         vt220   off secure  ttyE3   "/usr/libexec/getty Pc"         wsvt25   off secure
   
 (Please note that vt04 corresponds to ttyE3; In /etc/X11/xdm/Xservers,  (Please note that vt04 corresponds to ttyE3; In /etc/X11/xdm/Xservers,
 numbering starts at 1, but in /etc/ttys, numbering starts at 0).  numbering starts at 1, but in /etc/ttys, numbering starts at 0).
Line 6869  candidates for use in RAID and should be
Line 6838  candidates for use in RAID and should be
   
 Perform a very generic installation onto your Disk0/wd0. Follow the INSTALL  Perform a very generic installation onto your Disk0/wd0. Follow the INSTALL
 instructions for your platform. Install all the sets but do not bother  instructions for your platform. Install all the sets but do not bother
 customizing anything other than the kernel as it will be overwritten.  customizing anything other than the kernel as it will be overwritten. See also
   Chapter 2, Installing NetBSD: Preliminary considerations and preparations.
   
 Tip  Tip
   
 On x86, during the sysinst install, when prompted if you want to "use the  On x86, during the sysinst install, when prompted if you want to "use the
 entire disk for NetBSD", answer "yes".  entire disk for NetBSD", answer "yes".
   
   * Chapter 2, Installing NetBSD: Preliminary considerations and preparations  
   
   * NetBSD/i386 pre-6.x Install Directions  
   
   * NetBSD/i386 6.x Install Directions  
   
   * NetBSD/amd64 6.x Install Directions  
   
   * NetBSD/sparc64 Install Directions  
   
 Once the installation is complete, you should examine the disklabel(8) and  Once the installation is complete, you should examine the disklabel(8) and
 fdisk(8) / sunlabel(8) outputs on the system:  fdisk(8) / sunlabel(8) outputs on the system:
   
Line 8598  password
Line 8558  password
 Modules are a very central concept in PAM; after all, they are the "M" in "PAM"  Modules are a very central concept in PAM; after all, they are the "M" in "PAM"
 . A PAM module is a self-contained piece of program code that implements the  . A PAM module is a self-contained piece of program code that implements the
 primitives in one or more facilities for one particular mechanism; possible  primitives in one or more facilities for one particular mechanism; possible
 mechanisms for the authentication facility, for instance, include the UNIX  mechanisms for the authentication facility, for instance, include the UNIX(R)
 password database, NIS, LDAP and Radius.  password database, NIS, LDAP and Radius.
   
 18.4.2.1. Module Naming  18.4.2.1. Module Naming
   
 FreeBSD and NetBSD implement each mechanism in a single module, named pam_  FreeBSD and NetBSD implement each mechanism in a single module, named pam_
 mechanism.so (for instance, pam_unix.so for the UNIX  mechanism.) Other  mechanism.so (for instance, pam_unix.so for the UNIX(R) mechanism.) Other
 implementations sometimes have separate modules for separate facilities, and  implementations sometimes have separate modules for separate facilities, and
 include the facility name as well as the mechanism name in the module name. To  include the facility name as well as the mechanism name in the module name. To
 name one example, Solaris? has a pam_dial_auth.so.1 module which is commonly  name one example, Solaris? has a pam_dial_auth.so.1 module which is commonly
Line 9034  system to security risks.
Line 8994  system to security risks.
   
 18.6.1.19. pam_unix(8)  18.6.1.19. pam_unix(8)
   
 The pam_unix(8) module implements traditional UNIX  password authentication,  The pam_unix(8) module implements traditional UNIX(R) password authentication,
 using getpwnam(3) under FreeBSD or getpwnam_r(3) under NetBSD to obtain the  using getpwnam(3) under FreeBSD or getpwnam_r(3) under NetBSD to obtain the
 target account's password and compare it with the one provided by the  target account's password and compare it with the one provided by the
 applicant. It also provides account management services (enforcing account and  applicant. It also provides account management services (enforcing account and
Line 9455  User Manuals
Line 9415  User Manuals
   
 Related Web pages  Related Web pages
   
 [openpam-website] OpenPAM homepage. Dag-Erling Sm rgrav. ThinkSec AS.  [openpam-website] OpenPAM homepage. Dag-Erling Smo/rgrav. ThinkSec AS.
   
 [linuxpam-website] Linux-PAM homepage. Andrew G. Morgan.  [linuxpam-website] Linux-PAM homepage. Andrew G. Morgan.
   
Line 19547  addition, special thanks go to (in alpha
Line 19507  addition, special thanks go to (in alpha
   * Lubomir Sedlacik, for some details on using CGD for swap in Section 14.5,    * Lubomir Sedlacik, for some details on using CGD for swap in Section 14.5,
     "Suggestions and Warnings".      "Suggestions and Warnings".
   
   * Dag-Erling Sm rgrav, for the article on Chapter 18, Pluggable    * Dag-Erling Smo/rgrav, for the article on Chapter 18, Pluggable
     Authentication Modules (PAM). See Section D.3.2, "Networks Associates      Authentication Modules (PAM). See Section D.3.2, "Networks Associates
     Technology's license on the PAM article" for the accompanying license.      Technology's license on the PAM article" for the accompanying license.
   
   * Florian St hr, for Section 14.4, "Example: encrypted CDs/DVDs".    * Florian Sto:hr, for Section 14.4, "Example: encrypted CDs/DVDs".
   
 D.3. Licenses  D.3. Licenses
   

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3

CVSweb <webmaster@jp.NetBSD.org>