From owner-doc-jp@jp.freebsd.org  Tue Oct 28 11:52:22 1997
Received: by jaz.jp.freebsd.org (8.8.8+2.7Wbeta7/8.7.3) id LAA08987
	Tue, 28 Oct 1997 11:52:22 +0900 (JST)
Received: by jaz.jp.freebsd.org (8.8.7+2.7Wbeta7/8.7.3) with ESMTP id LAA08972
	for <doc-jp@jp.FreeBSD.org>; Tue, 28 Oct 1997 11:52:15 +0900 (JST)
Received: from localhost ([202.190.19.56])
	by relay14.jaring.my (8.8.7/8.8.7) with ESMTP id KAA01341;
	Tue, 28 Oct 1997 10:51:33 +0800 (MYT)
Message-Id: <199710280251.KAA01341@relay14.jaring.my>
Received: from localhost (localhost [127.0.0.1]) by localhost (8.8.7/3.4W3) with ESMTP id KAA08830; Tue, 28 Oct 1997 10:59:27 +0800 (MYT)
To: doc-jp@jp.FreeBSD.org, nishika@usa.net
X-Mailer: Mew version 1.06 on Emacs 19.28.1, Mule 2.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-2022-jp
Date: Tue, 28 Oct 1997 10:59:26 +0800
From: Mitsuru IWASAKI <iwasaki@pc.jaring.my>
Reply-To: doc-jp@jp.freebsd.org
Precedence: bulk
X-Distribute: distribute [version 2.1 (Alpha) patchlevel=20]
X-Sequence: doc-jp 3595
Subject: [doc-jp 3595] <FAQ> FAQ-admin.sgml
Errors-To: owner-doc-jp@jp.freebsd.org
Sender: owner-doc-jp@jp.freebsd.org

$B$$$o$5$-$G$9!#(B
$B9M$($F$_$?$i!";D$j$N?75,K]Lu$,I,MW$J$b$N$O(B
FAQ-admin.sgml $B$@$1$J$s$G$9!#$=$l$b$=$l$[$I(B
$BB?$/$J$$$h$&$J$N$G!"$J$k$Y$/Aa$/JRIU$1$?$$$J!<!"(B
$B$H;W$C$F$$$^$9!#(B
$B$I$J$?$+2<Lu$rDs6!$7$F$$$?$@$1$k4qFC$JJ}$O$$$i$C$7$c$$$^$;$s$+(B?
$B0J2<$K86J8$rE:IU$7$^$9!#$^$?!"85$N%U%!%$%k$O(B
http://www.jp.freebsd.org/~iwasaki/FAQ/FAQ-admin.sgml $B$G$9!#(B

$B!t$d$Y!"$b$&=P$+$1$J$-$c(B!

$B$=$N#1(B:
<!-- NOTYET -->
	  In post-2.2.2 and 3.0, <tt>/etc/sysconfig</tt> was renamed
	  to a more self-describing <tt>rc.conf</tt> file and the syntax
	  cleaned up a bit in the process.  <tt>/etc/netstart</tt> was also
	  renamed to <tt>/etc/rc.network</tt> so that all files could be
	  copied with a <tt>cp /usr/src/etc/rc* /etc</tt> command.

$B$=$N#2(B:
<!-- NOTYET -->
	<p>
	  If you have at least FreeBSD 2.1.5, and you want to dedicate
	  an entire disk to FreeBSD without any care for other
	  systems, you might shorten the steps above to something like:
<verb>
# dd if=/dev/zero of=/dev/rwd0 count=100
# disklabel -Brw wd0 auto
# disklabel -e wd0
</verb>

	  The first <tt/dd/ command ensures there is no old junk at
	  the beginning of the disk that might confuse the disk code
	  in the kernel.  Following is an automatic skeleton label
	  generation using the defaults that have been probed from the
	  disk at boot time.  Editing this label continues as described
	  above.


$B$=$N#3(B:
<!-- NOTYET -->
       <sect1>
         <heading>I have a new removable drive, how do I use it?</heading>

          <p>
	   Whether it's a removable drive like a ZIP or an EZ drive (or
	   even a floppy, if you want to use it that way), or a new hard
	   disk, once it's installed and recognised by the system, and
	   you have your cartridge/floppy/whatever slotted in, things are
	   pretty much the same for all devices.

	   <label id="disklabel">
	   (this section is based on <url
	   url="http://vinyl.quickweb.com/mark/FreeBSD/ZIP-FAQ.html"
	   name="Mark Mayo's ZIP FAQ">)

	   If it's a ZIP drive or a floppy , you've already got a DOS
	   filesystem on it, you can use a command like this:

	   <verb>
		mount -t msdos /dev/fd0c /floppy
	   </verb>

	   if it's a floppy, or this:

	   <verb>
		mount -t msdos /dev/sd2s4 /zip
	   </verb>

	   for a ZIP disk with the factory configuration.

           For other disks, see how they're laid out
	   using <tt/fdisk/ or <tt>/stand/sysinstall</tt>.

           The rest of the
	   examples will be for a ZIP drive on sd2, the third SCSI disk.

	   Unless it's a floppy, or a removable you plan on sharing with
	   other people, it's probably a better idea to stick a BSD file
	   system on it. You'll get long filename support, at least a 2X
	   improvement in performance, and a lot more stability. First, you
	   need to redo the DOS-level partitions/filesystems. You can either
	   use <tt/fdisk/ or <tt>/stand/sysinstall</tt>, or for a small
	   drive that you don't want to bother with multiple operating system
	   support on, just blow away the whole FAT partition table (slices)
	   and just use the BSD partitioning:

	   <verb>
		dd if=/dev/zero of=/dev/rsd2 count=2
		disklabel -Brw sd2 auto
           </verb>

	   You can use disklabel (more info in <ref id="2_1-disklabel-fix"
	   name="this note">) or <tt>/stand/sysinstall</tt> to create multiple
	   BSD partitions. You'll certainly want to do this if you're adding
	   swap space on a fixed disk, but it's probably irrelevant on a
	   removable drive like a ZIP.

	   Finally, create a new file system, this one's on our ZIP drive
	   using the whole disk:

	   <verb>
		newfs /dev/rsd2c
	   </verb>

	   and mount it:

	   <verb>
		mount /dev/sd2c /zip
	   </verb>

	   and it's probably a good idea to add a line like this to
	   <tt>/etc/fstab</tt> so you can just type "mount /zip" in the
	   future:

	   <verb>
                /dev/sd2c      /zip      ffs   rw,noauto   0   0
	   </verb>

$B$=$N#4(B:
<!-- NOTYET -->
      <sect1>
        <heading>How about FreeBSD and Linux? How do I boot FreeBSD from LILO?</heading>
        <p>
          Theoretically you should be able to boot FreeBSD from LILO by
          treating it as a DOS-style operating system, but I haven't been
          able to get it to work. If you put LILO at the start of your Linux
	  boot partition instead of in the MBR, you can boot LILO from the
	  FreeBSD boot manager. This is what I do.

	  If you're running Windows-95 and Linux this is recommended anyway,
	  to make it simpler to get Linux booting again if you should need
	  to reinstall Windows95 (which is a Jealous Operating System, and
	  will bear no other Operating Systems in the Master Boot Record).

      <sect1>
	<heading>Will a ``dangerously dedicated'' disk endanger my health?</heading>
	<p><label id="dedicate">
	  The installation procedure allows you to chose two different
	  modi how to partition your harddisk(s).  The default way makes
	  it compatible with other operating systems on the same machine,
	  by using fdisk table entries (called ``slices'' in FreeBSD),
	  with a FreeBSD slice that employs partitions of its own.
	  Optionally, one can chose to install a boot-selector to switch
	  between the possible operating systems on the disk(s).

	<p>
	  Now, while this is certainly the common case for people
	  coming from a PC background, those people coming more from a
	  Unix background and who are going to setup a machine just to
	  run FreeBSD and only FreeBSD, are more used to the classic
	  Unix way where the operating system owns the entire disks,
	  from the very first sector through the end.  A true fdisk
	  table isn't of any use in this case, the machine is running
	  FreeBSD 24 hours per day, 7 days per week, no other operating
	  system should ever be booted on it.  So, if you select
	  ``A)ll FreeBSD'' in sysinstall's fdisk editor, and answer the
	  next question with ``No'', you'll get this mode.  Note that
	  this means the BSD bootstrap also forms the MBR for this drive,
	  so there's no space left for anything like a boot manager.
	  Don't ever try to install one, or you'll damage the BSD
	  bootstrap.

	<p>
	  So why it is called ``dangerous''?  A disk in this mode
	  doesn't contain what normal PC utilities would consider a
	  valid fdisk table.  Depending on how well they have been
	  designed, they might complain at you once they are getting
	  in contact with such a disk, or even worse, they might
	  damage the BSD bootstrap without even asking or notifying
	  you.  Some kind of operating system that is in rather
	  widespread use on PCs is known for this kind of
	  user-unfriendliness (of course, it does this in the name of
	  ``user-friendliness'').  At least one Award BIOS that is for
	  example used in HP Netservers (but not only there) is known
	  to ignore any harddisk that doesn't have what it believes to
	  be a valid fdisk table.  When it comes to booting, it simply
	  ignores such a disk drive, advances to the floppy drive, and
	  barfs at you with just ``Read error''.  Very impressive, eh?
	  They probably also call this ``user-friendly'', who knows?

	<p>
	  The advantages of this mode are: FreeBSD owns the entire
	  disk, no need to waste several ficticuous `tracks' for just
	  nothing but a 1980-aged simplicistic partitioning model
	  enforcing some artificial and now rather nonsensical
	  constraints on how this partitioning needs to be done.
	  These constraints often lead to what might be the biggest
	  headaches for OS installations on PCs, geometry mismatch
	  hassles resulting out of two different, redundant ways how
	  to store the partitioning information in the fdisk table.
	  See the chapter about <ref id="missing_os" name="Missing
	  Operating System">.  In ``dangerously dedicated'' mode, the
	  BSD bootstrap starts at sector 0, and this one is the only
	  sector that always translates into the same C/H/S values,
	  regardless of which `translation' your BIOS is using for
	  your disk.  Thus, you can also swap disks between
	  systems/controllers that use a different translation scheme,
	  without risking that they won't boot anymore.

	<p>
	  To return a ``dangerously dedicated'' disk for normal PC
	  use, there are basically two options.  The first is, you
	  write enough NULL bytes over the MBR to make any subsequent
	  installation believe this to be a blank disk.  You can do
	  this for example with

	  <verb>
	    dd if=/dev/zero of=/dev/rsd0 count=15
	  </verb>

	  Alternatively, the undocumented DOS command

	  <verb>
	    fdisk /mbr
	  </verb>

	  is supposed to install a new master boot record as well,
	  thus clobbering the BSD bootstrap.


