doc-el commit 1015:5088d006af82 - Replace english text of 'disks...
freebsd-doc-el at lists.hellug.gr
freebsd-doc-el at lists.hellug.gr
Sun Nov 9 06:50:06 EET 2008
changeset: 1015:5088d006af82
user: Manolis Kiagias <sonicy at otenet.gr>
date: 2008-11-06 16:31 +0200
details: http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=5088d006af82
description:
Replace english text of 'disks' chapter with rev. 1.288 (no changes in synopsis)
diffstat:
1 file changed, 59 insertions(+), 67 deletions(-)
el_GR.ISO8859-7/books/handbook/disks/chapter.sgml | 126 +++++++++------------
diffs (truncated from 368 to 300 lines):
diff -r 19b8a6623778 -r 5088d006af82 el_GR.ISO8859-7/books/handbook/disks/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/disks/chapter.sgml Thu Nov 06 16:25:22 2008 +0200
+++ b/el_GR.ISO8859-7/books/handbook/disks/chapter.sgml Thu Nov 06 16:31:29 2008 +0200
@@ -7,7 +7,7 @@
$FreeBSD: doc/el_GR.ISO8859-7/books/handbook/disks/chapter.sgml,v 1.2 2008/01/14 14:19:44 keramida Exp $
%SOURCE% en_US.ISO8859-1/books/handbook/disks/chapter.sgml
- %SRCID% 1.1
+ %SRCID% 1.288
-->
@@ -244,12 +244,12 @@
<step>
<title><application>fdisk</application> Partition Editor</title>
- <para>Once inside <application>fdisk</application>, typing <userinput>A</userinput> will
+ <para>Once inside <application>fdisk</application>, pressing <keycap>A</keycap> will
use the entire disk for FreeBSD. When asked if you want to
<quote>remain cooperative with any future possible operating
systems</quote>, answer <literal>YES</literal>. Write the
- changes to the disk using <userinput>W</userinput>. Now exit the
- FDISK editor by typing <userinput>q</userinput>. Next you will be
+ changes to the disk using <keycap>W</keycap>. Now exit the
+ FDISK editor by pressing <keycap>Q</keycap>. Next you will be
asked about the <quote>Master Boot Record</quote>. Since you are adding a
disk to an already running system, choose
<literal>None</literal>.</para>
@@ -279,8 +279,8 @@
<para><application>sysinstall</application>'s Label editor
favors the <literal>e</literal>
partition for non-root, non-swap partitions. Within the
- Label editor, create a single file system by typing
- <userinput>C</userinput>. When prompted if this will be a FS
+ Label editor, create a single file system by pressing
+ <keycap>C</keycap>. When prompted if this will be a FS
(file system) or swap, choose <literal>FS</literal> and type in a
mount point (e.g, <filename>/mnt</filename>). When adding a
disk in post-install mode, <application>sysinstall</application>
@@ -289,8 +289,8 @@
you specify is not important.</para>
<para>You are now ready to write the new label to the disk and
- create a file system on it. Do this by typing
- <userinput>W</userinput>. Ignore any errors from
+ create a file system on it. Do this by pressing
+ <keycap>W</keycap>. Ignore any errors from
<application>sysinstall</application> that
it could not mount the new partition. Exit the Label Editor
and <application>sysinstall</application> completely.</para>
@@ -321,7 +321,7 @@
<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 bs=1k count=1</userinput>
&prompt.root; <userinput>fdisk -BI da1</userinput> #Initialize your new disk
-&prompt.root; <userinput>bsdlabel -B -w -r da1s1 auto</userinput> #Label it.
+&prompt.root; <userinput>bsdlabel -B -w da1s1 auto</userinput> #Label it.
&prompt.root; <userinput>bsdlabel -e da1s1</userinput> # Edit the bsdlabel just created and add any partitions.
&prompt.root; <userinput>mkdir -p /1</userinput>
&prompt.root; <userinput>newfs /dev/da1s1e</userinput> # Repeat this for every partition you created.
@@ -344,9 +344,9 @@
understand.</para>
<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 bs=1k count=1</userinput>
-&prompt.root; <userinput>bsdlabel -Brw da1 auto</userinput>
+&prompt.root; <userinput>bsdlabel -Bw da1 auto</userinput>
&prompt.root; <userinput>bsdlabel -e da1</userinput> # create the `e' partition
-&prompt.root; <userinput>newfs -d0 /dev/da1e</userinput>
+&prompt.root; <userinput>newfs /dev/da1e</userinput>
&prompt.root; <userinput>mkdir -p /1</userinput>
&prompt.root; <userinput>vi /etc/fstab</userinput> # add an entry for /dev/da1e
&prompt.root; <userinput>mount /1</userinput></screen>
@@ -354,7 +354,7 @@
<para>An alternate method is:</para>
<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 count=2</userinput>
-&prompt.root; <userinput>bsdlabel /dev/da1 | bsdlabel -BrR da1 /dev/stdin</userinput>
+&prompt.root; <userinput>bsdlabel /dev/da1 | bsdlabel -BR da1 /dev/stdin</userinput>
&prompt.root; <userinput>newfs /dev/da1e</userinput>
&prompt.root; <userinput>mkdir -p /1</userinput>
&prompt.root; <userinput>vi /etc/fstab</userinput> # add an entry for /dev/da1e
@@ -467,9 +467,9 @@
<para>To set up &man.ccd.4;, you must first use
&man.bsdlabel.8; to label the disks:</para>
- <programlisting>bsdlabel -r -w ad1 auto
-bsdlabel -r -w ad2 auto
-bsdlabel -r -w ad3 auto</programlisting>
+ <programlisting>bsdlabel -w ad1 auto
+bsdlabel -w ad2 auto
+bsdlabel -w ad3 auto</programlisting>
<para>This creates a bsdlabel for <devicename>ad1c</devicename>, <devicename>ad2c</devicename> and <devicename>ad3c</devicename> that
spans the entire disk.</para>
@@ -837,7 +837,7 @@
these lines to
<filename>/etc/devfs.rules</filename>:</para>
- <programlisting>[localrules=1]
+ <programlisting>[localrules=5]
add path 'da*' mode 0660 group operator</programlisting>
<note>
@@ -875,19 +875,20 @@
the user that is to mount the file system. One way to do that
is for <username>root</username> to create a subdirectory
owned by that user as
- <filename>/mnt/<replaceable>$USER</replaceable></filename>
- (replace <replaceable>$USER</replaceable> by the login name of
- the actual user):</para>
-
- <screen>&prompt.root; <userinput>mkdir /mnt/$USER</userinput>
-&prompt.root; <userinput>chown <replaceable>$USER</replaceable>:<replaceable>$USER</replaceable> /mnt/<replaceable>$USER</replaceable></userinput></screen>
+ <filename>/mnt/<replaceable>username</replaceable></filename>
+ (replace <replaceable>username</replaceable> by the login name of
+ the actual user and <replaceable>usergroup</replaceable> by the
+ user's primary group):</para>
+
+ <screen>&prompt.root; <userinput>mkdir /mnt/<replaceable>username</replaceable></userinput>
+&prompt.root; <userinput>chown <replaceable>username</replaceable>:<replaceable>usergroup</replaceable> /mnt/<replaceable>username</replaceable></userinput></screen>
<para>Suppose a USB thumbdrive is plugged in, and a device
<filename>/dev/da0s1</filename> appears. Since these devices
usually come preformatted with a FAT file system, one can
mount them like this:</para>
- <screen>&prompt.user; <userinput>mount_msdosfs -m 644 -M 755 /dev/da0s1 /mnt/<replaceable>$USER</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>mount -t msdosfs -o -m=644,-M=755 /dev/da0s1 /mnt/<replaceable>username</replaceable></userinput></screen>
<para>If you unplug the device (the disk must be unmounted
before), you should see, in the system message buffer,
@@ -1830,7 +1831,7 @@
before the first use. In the example, the whole
disk space will be used with a standard UFS2 file system:</para>
- <screen>&prompt.root; <userinput>dd if=/dev/zero of=<replaceable>/dev/acd0</replaceable> count=2</userinput>
+ <screen>&prompt.root; <userinput>dd if=/dev/zero of=<replaceable>/dev/acd0</replaceable> bs=2k count=1</userinput>
&prompt.root; <userinput>bsdlabel -Bw <replaceable>acd0</replaceable></userinput>
&prompt.root; <userinput>newfs <replaceable>/dev/acd0</replaceable></userinput></screen>
@@ -1940,7 +1941,7 @@
<para>You can run now &man.bsdlabel.8; like so:</para>
- <screen>&prompt.root; <userinput>/sbin/bsdlabel -B -r -w /dev/fd0 fd1440</userinput></screen>
+ <screen>&prompt.root; <userinput>/sbin/bsdlabel -B -w /dev/fd0 fd1440</userinput></screen>
</sect2>
@@ -2796,27 +2797,12 @@
cp /root/.profile /mnt/root
-cp -f /dev/MAKEDEV /mnt/dev
-chmod 755 /mnt/dev/MAKEDEV
-
chmod 500 /mnt/sbin/init
chmod 555 /mnt/sbin/fsck /mnt/sbin/mount /mnt/sbin/halt
chmod 555 /mnt/bin/sh /mnt/bin/sync
chmod 6555 /mnt/sbin/restore
#
-# create the devices nodes
-#
-cd /mnt/dev
-./MAKEDEV std
-./MAKEDEV da0
-./MAKEDEV da1
-./MAKEDEV da2
-./MAKEDEV sa0
-./MAKEDEV pty0
-cd /
-
-#
# create minimum file system table
#
cat > /mnt/etc/fstab <<EOM
@@ -3465,7 +3451,7 @@
<para>Now restart <command>inetd</command>:</para>
- <screen>&prompt.root; <userinput>kill -HUP `cat /var/run/inetd.pid`</userinput></screen>
+ <screen>&prompt.root; <userinput>/etc/rc.d/inetd restart</userinput></screen>
</sect2>
</sect1>
@@ -3598,7 +3584,7 @@
initialized before it can be used. This initialization needs to
be performed only once:</para>
- <screen>&prompt.root; <userinput>gbde init /dev/ad4s1c -i -L /etc/gbde/ad4s1c</userinput></screen>
+ <screen>&prompt.root; <userinput>gbde init /dev/ad4s1c -i -L /etc/gbde/ad4s1c.lock</userinput></screen>
<para>&man.gbde.8; will open your editor, permitting you to set
various configuration options in a template. For use with UFS1
@@ -3630,7 +3616,11 @@
<para>The <command>gbde init</command> command creates a lock
file for your <application>gbde</application> partition that in
this example is stored as
- <filename>/etc/gbde/ad4s1c</filename>.</para>
+ <filename>/etc/gbde/ad4s1c.lock</filename>.
+ <application>gbde</application> lock files must end in
+ <quote>.lock</quote> in order to be correctly detected by
+ the
+ <filename>/etc/rc.d/gbde</filename> start up script.</para>
<caution>
<para><application>gbde</application> lock files
@@ -3648,7 +3638,7 @@
<step>
<title>Attach the Encrypted Partition to the Kernel</title>
- <screen>&prompt.root; <userinput>gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c</userinput></screen>
+ <screen>&prompt.root; <userinput>gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c.lock</userinput></screen>
<para> You will be asked to provide the passphrase that you
selected during the initialization of the encrypted partition.
@@ -3725,7 +3715,7 @@
<step>
<title>Attach the gbde Partition to the Kernel</title>
- <screen>&prompt.root; <userinput>gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c</userinput></screen>
+ <screen>&prompt.root; <userinput>gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c.lock</userinput></screen>
<para>You will be asked to provide the passphrase that you
selected during initialization of the encrypted
@@ -3765,8 +3755,9 @@
provided. Arguments for this script can be passed via
&man.rc.conf.5;, for example:</para>
- <screen>gbde_autoattach_all="YES"
-gbde_devices="ad4s1c"</screen>
+ <programlisting>gbde_autoattach_all="YES"
+gbde_devices="ad4s1c"
+gbde_lockdir="/etc/gbde"</programlisting>
<para>This will require that the <application>gbde</application>
passphrase be entered at boot time. After typing the correct
@@ -3822,7 +3813,7 @@
<para>A new cryptographic GEOM class is available as of &os; 6.0 -
<command>geli</command>. It is currently being developed by
- &a.pjd;. <command>Geli</command> is different to
+ &a.pjd;. The <command>geli</command> utility is different to
<command>gbde</command>; it offers different features and uses
a different scheme for doing cryptographic work.</para>
@@ -3868,9 +3859,7 @@
<para>The next steps will describe how to enable support for
<command>geli</command> in the &os; kernel and will explain how
- to create a new <command>geli</command> encryption provider. At
- the end it will be demonstrated how to create an encrypted swap
- partition using features provided by <command>geli</command>.</para>
+ to create and use a <command>geli</command> encryption provider.</para>
<para>In order to use <command>geli</command>, you must be running
&os; 6.0-RELEASE or later. Super-user privileges will be
@@ -3878,14 +3867,13 @@
<procedure>
<step>
- <title>Adding <command>geli</command> Support to the Kernel
- Configuration File</title>
+ <title>Adding <command>geli</command> Support to the Kernel</title>
<para>Add the following lines to the kernel configuration
file:</para>
- <screen>options GEOM_ELI
-device crypto</screen>
+ <programlisting>options GEOM_ELI
+device crypto</programlisting>
<para>Rebuild the kernel as described in <xref
linkend="kernelconfig">.</para>
@@ -3894,7 +3882,7 @@
be loaded at boot time. Add the following line to the
<filename>/boot/loader.conf</filename>:</para>
- <para><literal>geom_eli_load="YES"</literal></para>
+ <programlisting>geom_eli_load="YES"</programlisting>
<para>&man.geli.8; should now be supported by the kernel.</para>
</step>
@@ -3905,7 +3893,7 @@
<para>The following example will describe how to generate a
key file, which will be used as part of the Master Key for
the encrypted provider mounted under
- <filename role="directory">/private</filename>. The key
+ <filename class="directory">/private</filename>. The key
file will provide some random data used to encrypt the
Master Key. The Master Key will be protected by a
passphrase as well. Provider's sector size will be 4kB big.
@@ -3960,7 +3948,7 @@
&prompt.root; <userinput>mount /dev/da2.eli /private</userinput></screen>
<para>The encrypted file system should be visible to &man.df.1;
- and be available for use now.</para>
+ and be available for use now:</para>
More information about the Freebsd-doc-el
mailing list