Ȼ/12

Top / Ȼ / 12

FreeBSD ΥС󥢥å

ơFreeBSD 6.3R 2008.01.18 ˤǤ꡼줿.
ǡޤݤäμΥϥ*1Ȥä,ߤγΥޥ 6.2R 6.3R ˤ upgrade 褦.

꤫񤤤ƤޤäƤϤʤˤ⳧ΰ٤ˤʤΤǡϼϤǤä㤪.

Ūˤϡhttp://www.jp.freebsd.org/www.FreeBSD.org/releases/6.3R/announce.html ɤǡ˽äƺȤƤߤ衤ȤȤǤ.

ʤ켡ɤ߹෱ͤơС󥢥åפ˴ؤƤϾλʳߤƤϤʤʤΤȤ.

եݥ

դ٤ݥȤϽ񤤤Ƥ.

OS ΥС󥢥åפȤʤȡƥΥեȥ¿С󥢥åפ. ˤϡưѤΤ䡤եΰ٤(ǽ)ưʤΤ⤢뤫⤷ʤ. ΤäƤ⺤ʤ褦ˡ֥ХååפȤäס֤Ǥľʥƥ๽ľƤץС󥢥åפԤ褦ˤ褦.

϶Ūˤϡ㤨мΤ褦ʤΤ. ¾ˤͤʤηäʤäƤߤ.

  1. եθǤޤǤ /etc ǥ쥯ȥǰΰ ޤ뤴ȥХååפäƤ.
    ŪˤϡС󥢥å׺
     cd /
     cd -Rp /etc /etc.old-20080201
    ʤɤȤФ褤.

  2. /etc/resolv.conf ϡ BIND ǤϤʤơǤгΥ꥾ФľƤ.
    פˤξϥС󥢥å׺
     nameserver 192.168.125.14
    ˤäᤷƤȤȤ.

  3. ƥ˴ؤȤϾ˺ȥʤĤ褦. portupgrade Τ褦˼ưǺȥϤ褤ϤǤϤʤΤǡsrcipt ޥɤѤƺȥ褦ˤ褦.

  4. ˡǥåץ졼ɤ硤ǥեΡפå̤ФƤ. ǤϡFreeBSD Security Officer<security-officer@FreeBSD.org>ɤ̾ Ȥ̤ޤǤʤȤƤĥ뤳! gpg: ̾򸡺Ǥޤ: No public key ȸƤ뤦ϥǤ롥ˤĤƤ gpg λȤΤʤȤʤ. äơgpg λȤˤĤĴ٤뤳ȤϾ¤Ȥ̤ OK Ȥ.

  5. ¾㤨Сͥե뤬ʤȵưʤʤ뤫⤷ʤ. ǤϥͥեХååפˤ?

ºݤκȥ

ʲˡץȤƺȥ򼨤Ƥ.
Τޤ޿ˤʤäƤޤäƤϤʤˤʤʤΤǡȤޤǸʤ褦ˤƤ(^-^).

 > fetch http:people.freebsd.org/~cperciva/freebsd-update-upgrade.tgz
 > fetch http:people.freebsd.org/~cperciva/freebsd-update-upgrade.tgz.asc
 > gpg --verify freebsd-update-upgrade.tgz.asc freebsd-update-upgrade.tgz
  
 gpg:  11/16 23:01:38 2007 JSTDSAID CA6CDFB2ǻܤ줿̾
 gpg: ̾򸡺Ǥޤ: No public key
  
 > gpg --keyserver pgp.nic.ad.jp --recv-key CA6CDFB2
  
 gpg: ء/root/.gnupg/secring.gpgפǤޤ
 gpg: CA6CDFB2hkp饵Сpgp.nic.ad.jp׵
 gpg: CA6CDFB2: ʣ桼IDθ - ʻ
 gpg: /root/.gnupg/trustdb.gpg: ѥǡ١Ǥޤ
 gpg: CA6CDFB2: FreeBSD Security Officer <security-officer@FreeBSD.org>ɤɤ߹ߤޤ
 gpg: Ū˿Ѥ븰Ĥޤ
 gpg:     ι: 1
 gpg:           ɹ: 1
  
  
 > gpg --verify freebsd-update-upgrade.tgz.asc freebsd-update-upgrade.tgz
 gpg:  11/16 23:01:38 2007 JSTDSAID CA6CDFB2ǻܤ줿̾
 gpg: FreeBSD Security Officer <security-officer@FreeBSD.org>ɤ̾
 gpg: ٹ: θϿѤǤ̾ǾƤޤ!
 gpg:       ν̾ͭԤΤΤɤθڼʤޤ
 縰λ: C374 0FC5 69A6 FBB1 4AED  B131 15D6 8804 CA6C DFB2
  
 > tar xfv freebsd-update-upgrade.tgz
 x freebsd-update.sh
 x freebsd-update.conf
  
 > sh ./freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade
 Looking up update.FreeBSD.org mirrors... 1 mirrors found.
 Fetching metadata signature for 6.2-RELEASE from update1.FreeBSD.org... done.
 Fetching metadata index... done.
 Fetching 1 metadata files... done.
 Inspecting system... done.
  
 The following components of FreeBSD seem to be installed:
 kernel/generic src/base src/sys world/base world/dict world/doc
 world/games world/info world/manpages world/proflibs
  
 The following components of FreeBSD do not seem to be installed:
 kernel/smp src/bin src/contrib src/crypto src/etc src/games src/gnu
 src/include src/krb5 src/lib src/libexec src/release src/rescue src/sbin
 src/secure src/share src/tools src/ubin src/usbin world/catpages
  
 Does this look reasonable (y/n)? y
  
 Fetching metadata signature for 6.3-RELEASE from update1.FreeBSD.org... done.
 Fetching metadata index... done.
 Fetching 1 metadata patches. done.
 Applying metadata patches... done.
 Fetching 1 metadata files... done.
 Inspecting system... done.
 Fetching files from 6.2-RELEASE for merging... done.
 Preparing to download files...7322 patches.....10....20....30....(ά)...7300....7310....7320. done.
 Applying patches... done.
 Fetching 1260 files... done.
 Attempting to automatically merge changes in files... done.
  
 The following file could not be merged automatically: /var/named/etc/namedb/named.conf
 Press Enter to edit this file in emacs and resolve the conflicts
 manually...
 (ŬڤԽ. ʬǽ­ľꤷʬͭǤ³褦դФ褤. ˤƤ named.conf ɤѤäää.)
  
 The following changes, which occurred between FreeBSD 6.2-RELEASE and
 FreeBSD 6.3-RELEASE have been merged into /etc/hosts.allow:
 --- current version
 +++ new version
 @@ -1,8 +1,8 @@
  #
  # hosts.allow access control file for "tcp wrapped" applications.
 -# $FreeBSD: src/etc/hosts.allow,v 1.19.8.1 2006/02/19 14:57:01 ume Exp $
 +# $FreeBSD: src/etc/hosts.allow,v 1.19.8.2 2007/01/20 02:19:57 csjp Exp $
  #
  # NOTE: The hosts.deny file is deprecated.
  #       Place both 'allow' and 'deny' rules in the hosts.allow file.
  #      See hosts_options(5) for the format of this file.
  #      hosts_access(5) no longer fully applies.
 @@ -67,10 +67,11 @@
  rpcbind : 192.0.2.32/255.255.255.224 : allow
  rpcbind : 192.0.2.96/255.255.255.224 : allow
  rpcbind : ALL : deny
  
  # NIS master server. Only local nets should have access
 +# (Since this is an RPC service, rpcbind needs to be considered)
  ypserv : localhost : allow
  ypserv : .unsafe.my.net.example.com : deny
  ypserv : .my.net.example.com : allow
  ypserv : ALL : deny
  
 Does this look reasonable (y/n)? y
  
 The following changes, which occurred between FreeBSD 6.2-RELEASE and
 FreeBSD 6.3-RELEASE have been merged into /var/named/etc/namedb/named.conf:
 --- current version
 +++ new version
 @@ -1,16 +1,17 @@
 - $FreeBSD: src/etc/namedb/named.conf,v 1.21.2.1 2005/09/10 08:27:27 dougb Exp $
 + $FreeBSD: src/etc/namedb/named.conf,v 1.21.2.6.2.1 2008/01/13 20:51:09 dougb Exp $
  
   Refer to the named.conf(5) and named(8) man pages, and the documentation
   in /usr/share/doc/bind9 for more details.
  
   If you are going to set up an authoritative server, make sure you
   understand the hairy details of how DNS works.  Even with
   simple mistakes, you can break connectivity for affected parties,
   or cause huge amounts of useless Internet traffic.
  
  options {
 +        Relative to the chroot directory, if any
         directory       "/etc/namedb";
         pid-file        "/var/run/named/pid";
         dump-file       "/var/dump/named_dump.db";
         statistics-file "/var/stats/named.stats";
  
 @@ -25,15 +26,23 @@
   If you have IPv6 enabled on this system, uncomment this option for
   use as a local resolver.  To give access to the network, specify
   an IPv6 address, or the keyword "any".
       listen-on-v6    { ::1; };
  
 +/*     These options are available for BIND 9.4.x
 + These zones are already covered by the empty zones listed below.
 + If you remove the related empty zones below, comment these lines out.
 +       disable-empty-zone "255.255.255.255.IN-ADDR.ARPA";
 +       disable-empty-zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA";
 +       disable-empty-zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA";
 +*/
 +
   In addition to the "forwarders" clause, you can force your name
   server to never initiate queries of its own, but always ask its
   forwarders only, by enabling the following line:
  
 -      forward only;
 +     forward only;
  
   If you've got a DNS server around at your upstream provider, enter
   its IP address here, and enable the line below.  This will make you
   benefit from its cache, thus reduce overall DNS traffic in the Internet.
  /*
 @@ -53,26 +62,178 @@
  
   If you enable a local name server, don't forget to enter 127.0.0.1
   first in your /etc/resolv.conf so this server will be queried.
   Also, make sure to enable it in /etc/rc.conf.
  
 + The traditional root hints mechanism. Use this, OR the slave zones below.
 +zone "." { type hint; file "named.root"; };
 +
 +/*     Slaving the following zones from the root name servers has some
 +       significant advantages:
 +       1. Faster local resolution for your users
 +       2. No spurious traffic will be sent from your network to the roots
 +       3. Greater resilience to any potential root server failure/DDoS
 +
 +       On the other hand, this method requires more monitoring than the
 +       hints file to be sure that an unexpected failure mode has not
 +       incapacitated your server.  Name servers that are serving a lot
 +       of clients will benefit more from this approach than individual
 +       hosts.  Use with caution.
 +
 +       To use this mechanism, uncomment the entries below, and comment
 +       the hint zone above.
 +*/
 +/*
  zone "." {
 -       type hint;
 -       file "named.root";
 +       type slave;
 +       file "slave/root.slave";
 +       masters {
 +               192.5.5.241;     F.ROOT-SERVERS.NET.
 +       };
 +       notify no;
  };
 -
 -zone "0.0.127.IN-ADDR.ARPA" {
 -       type master;
 -       file "master/localhost.rev";
 +zone "arpa" {
 +       type slave;
 +       file "slave/arpa.slave";
 +       masters {
 +               192.5.5.241;     F.ROOT-SERVERS.NET.
 +       };
 +       notify no;
  };
 -
 - RFC 3152
 -zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA" {
 -       type master;
 -       file "master/localhost-v6.rev";
 +zone "in-addr.arpa" {
 +       type slave;
 +       file "slave/in-addr.arpa.slave";
 +       masters {
 +               192.5.5.241;     F.ROOT-SERVERS.NET.
 +       };
 +       notify no;
  };
  
 +
 +=======
 +*/
 +
 +/*     Serving the following zones locally will prevent any queries
 +       for these zones leaving your network and going to the root
 +       name servers.  This has two significant advantages:
 +       1. Faster local resolution for your users
 +       2. No spurious traffic will be sent from your network to the roots
 +*/
 + RFC 1912
 +zone "localhost"       { type master; file "master/localhost-forward.db"; };
 +zone "127.in-addr.arpa" { type master; file "master/localhost-reverse.db"; };
 +zone "255.in-addr.arpa"        { type master; file "master/empty.db"; };
 +
 + RFC 1912-style zone for IPv6 localhost address
 +zone "0.ip6.arpa"      { type master; file "master/localhost-reverse.db"; };
 +
 + "This" Network (RFCs 1912 and 3330)
 +zone "0.in-addr.arpa"          { type master; file "master/empty.db"; };
 +
 + Private Use Networks (RFC 1918)
 +zone "10.in-addr.arpa"         { type master; file "master/empty.db"; };
 +zone "16.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "17.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "18.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "19.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "20.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "21.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "22.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "23.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "24.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "25.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "26.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "27.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "28.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "29.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "30.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "31.172.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "168.192.in-addr.arpa"    { type master; file "master/empty.db"; };
 +
 + Link-local/APIPA (RFCs 3330 and 3927)
 +zone "254.169.in-addr.arpa"    { type master; file "master/empty.db"; };
 +
 + TEST-NET for Documentation (RFC 3330)
 +zone "2.0.192.in-addr.arpa"    { type master; file "master/empty.db"; };
 +
 + Router Benchmark Testing (RFC 3330)
 +zone "18.198.in-addr.arpa"     { type master; file "master/empty.db"; };
 +zone "19.198.in-addr.arpa"     { type master; file "master/empty.db"; };
 +
 + IANA Reserved - Old Class E Space
 +zone "240.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "241.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "242.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "243.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "244.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "245.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "246.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "247.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "248.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "249.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "250.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "251.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "252.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "253.in-addr.arpa"                { type master; file "master/empty.db"; };
 +zone "254.in-addr.arpa"                { type master; file "master/empty.db"; };
 +
 + IPv6 Unassigned Addresses (RFC 4291)
 +zone "1.ip6.arpa"              { type master; file "master/empty.db"; };
 +zone "3.ip6.arpa"              { type master; file "master/empty.db"; };
 +zone "4.ip6.arpa"              { type master; file "master/empty.db"; };
 +zone "5.ip6.arpa"              { type master; file "master/empty.db"; };
 +zone "6.ip6.arpa"              { type master; file "master/empty.db"; };
 +zone "7.ip6.arpa"              { type master; file "master/empty.db"; };
 +zone "8.ip6.arpa"              { type master; file "master/empty.db"; };
 +zone "9.ip6.arpa"              { type master; file "master/empty.db"; };
 +zone "a.ip6.arpa"              { type master; file "master/empty.db"; };
 +zone "b.ip6.arpa"              { type master; file "master/empty.db"; };
 +zone "c.ip6.arpa"              { type master; file "master/empty.db"; };
 +zone "d.ip6.arpa"              { type master; file "master/empty.db"; };
 +zone "e.ip6.arpa"              { type master; file "master/empty.db"; };
 +zone "0.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +zone "1.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +zone "2.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +zone "3.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +zone "4.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +zone "5.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +zone "6.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +zone "7.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +zone "8.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +zone "9.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +zone "a.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +zone "b.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +zone "0.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +zone "1.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +zone "2.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +zone "3.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +zone "4.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +zone "5.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +zone "6.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +zone "7.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +
 + IPv6 ULA (RFC 4193)
 +zone "c.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +zone "d.f.ip6.arpa"            { type master; file "master/empty.db"; };
 +
 + IPv6 Link Local (RFC 4291)
 +zone "8.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +zone "9.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +zone "a.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +zone "b.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +
 + IPv6 Deprecated Site-Local Addresses (RFC 3879)
 +zone "c.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +zone "d.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +zone "e.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +zone "f.e.f.ip6.arpa"          { type master; file "master/empty.db"; };
 +
 + IP6.INT is Deprecated (RFC 4159)
 +zone "ip6.int"                 { type master; file "master/empty.db"; };
 +
 +
 +
  zone "sub17.cl.math.sci.osaka-u.ac.jp" {
         type master;
         file "master/sub17.zone";
  };
  
 @@ -81,52 +242,38 @@
   serve demonstration/documentation purposes!
  
   Example slave zone config entries.  It can be convenient to become
   a slave at least for the zone your own domain is in.  Ask
   your network administrator for the IP address of the responsible
 - primary.
 + master name server.
  
 - Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
 - (This is named after the first bytes of the IP address, in reverse
 - order, with ".IN-ADDR.ARPA" appended.)
 -
 - Before starting to set up a primary zone, make sure you fully
 - understand how DNS and BIND works.  There are sometimes
 - non-obvious pitfalls.  Setting up a slave zone is simpler.
 + Do not forget to include the reverse lookup zone!
 + This is named after the first bytes of the IP address, in reverse
 + order, with ".IN-ADDR.ARPA" appended, or ".IP6.ARPA" for IPv6.
 +
 + Before starting to set up a master zone, make sure you fully
 + understand how DNS and BIND work.  There are sometimes
 + non-obvious pitfalls.  Setting up a slave zone is usually simpler.
  
   NB: Don't blindly enable the examples below. :-)  Use actual names
   and addresses instead.
  
 -/* An example master zone
 -zone "example.net" {
 -       type master;
 -       file "master/example.net";
 -};
 -*/
 -
  /* An example dynamic zone
  key "exampleorgkey" {
 -        algorithm hmac-md5;
 -        secret "sf87HJqjkqh8ac87a02lla==";
 +       algorithm hmac-md5;
 +       secret "sf87HJqjkqh8ac87a02lla==";
  };
  zone "example.org" {
         type master;
         allow-update {
                 key "exampleorgkey";
         };
         file "dynamic/example.org";
  };
  */
  
 -/* Examples of forward and reverse slave zones
 -zone "example.com" {
 -       type slave;
 -       file "slave/example.com";
 -       masters {
 -               192.168.1.1;
 -       };
 -};
 +/* Example of a slave reverse zone
  zone "1.168.192.in-addr.arpa" {
         type slave;
         file "slave/1.168.192.in-addr.arpa";
         masters {
                 192.168.1.1;
 Does this look reasonable (y/n)? y
  
 The following files will be removed as part of updating to 6.3-RELEASE-p0:
 /boot/kernel/hptmv.ko
 /usr/share/doc/de_DE.ISO8859-1/books/handbook/install-supported-hardware.html
 ...
  
 The following files will be added as part of updating to 6.3-RELEASE-p0:
 /boot/kernel/acpi_dock.ko
 /boot/kernel/coretemp.ko
 ...
  
 The following files will be updated as part of updating to 6.3-RELEASE-p0:
 /COPYRIGHT
 /bin/[
 ...
  
 >  sh ./freebsd-update.sh -f freebsd-update.conf install
 Installing updates...
 Kernel updates have been installed.  Please reboot and run
 "./freebsd-update.sh install" again to finish installing updates.
  
 > shutdown -r now
  
 FreeBSD 6.3-RELEASE (GENERIC) #0: Wed Jan 16 04:18:52 UTC 2008
 (ʤߤˡƵưΥˤϡ)
  
 (Ƶư)
 > sh ./freebsd-update.sh -f freebsd-update.conf install
 Installing updates... done.
  
 > shutdown -r now

;͵С

port ʤɤǤƤ. ꤳޤ˺ȤƤС

 > portaudit -Fad
 auditfile.tbz                                 100% of   47 kB   48 kBps
 New database installed.
 Database created: 2008ǯ 127  0810ʬ01 JST
 0 problem(s) in your installed packages found.
 > portsnap fetch
 Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
 Fetching snapshot tag from portsnap2.FreeBSD.org... done.
 Latest snapshot on server matches what we already have.
 No updates needed.
 > portupgrade -na -x 'emacs*'
 --->  Reading default options: -v -L /var/log/ports/%s::%s.log
 --->  Session started at: Sun, 27 Jan 2008 08:16:08 +0900
 ά
 --->  Packages processed: 0 done, 639 ignored, 0 skipped and 1 failed   fail ϼȤ줿ܸޥ˥奢 package ΤʤΤʤ
 --->  Session ended at: Sun, 27 Jan 2008 08:18:57 +0900 (consumed 00:02:48)  

Ȥ褦ʴ, ۤܺǿξݤĤȤǤ.

ݡ

ºݤ˥С󥢥åפԤ

 uname -v 

Ȥ

 FreeBSD 6.3-RELEASE #0: Wed Jan 16 04:18:52 UTC 2008     root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC

ȤϤ褦ˤ.

ޤθ塤

 dig @127.0.0.1 www.osaka-u.ac.jp

Ȥơ BIND ưƤ뤳ȤǧƤ顤/etc/resolv.conf ʬᤷ dig ŬԤä DNS 䤤碌ʤȤǧ.

ޤΥ꡼web Dedication Ȥʬ򤭤ɤߡܸơݡȤĥդ.
ޤ˽ФƤʪˤĤĴη̤ˤĤƽҤ٤.

ޤFreeBSD 6.3R ϤĤޤǥݡȤͽ꤫ˤĤƤҤ٤.


*1 ΤʤȤ򶵤㤦ޤԤĤǤʤȯŪˤĴ٤Ȥ.