Date: Tue, 4 Feb 2014 18:20:56 +0000 (UTC) From: Dru Lavigne <dru@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43766 - head/en_US.ISO8859-1/articles/linux-users Message-ID: <201402041820.s14IKu5D090632@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Tue Feb 4 18:20:56 2014 New Revision: 43766 URL: http://svnweb.freebsd.org/changeset/doc/43766 Log: Last pass through this article. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/articles/linux-users/article.xml Modified: head/en_US.ISO8859-1/articles/linux-users/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/linux-users/article.xml Tue Feb 4 17:15:33 2014 (r43765) +++ head/en_US.ISO8859-1/articles/linux-users/article.xml Tue Feb 4 18:20:56 2014 (r43766) @@ -36,7 +36,7 @@ <sect1 xml:id="intro"> <title>Introduction</title> - <para>This document highlights the technical differences between &os; and + <para>This document highlights some of the technical differences between &os; and &linux; so that intermediate to advanced &linux; users can quickly familiarize themselves with the basics of &os;.</para> @@ -55,7 +55,7 @@ In fact, <application>Bash</application> is not even in the default installation. Instead, &os; uses &man.tcsh.1; as the default shell. However, <application>Bash</application> and other - shells are available in &os;'s <link xlink:href="&url.base;/doc/en_US.ISO8859-1/books/handbook/ports.html">Packages and Ports Collection</link>.</para> + shells are available for installation using the &os; <link xlink:href="&url.base;/doc/en_US.ISO8859-1/books/handbook/ports.html">Packages and Ports Collection</link>.</para> <para>After installing another shell, use &man.chsh.1; to change a user's default shell. It is recommended that the @@ -66,7 +66,7 @@ system where <filename>/usr/local/bin</filename> is located may not be mounted. In this case, <systemitem class="username">root</systemitem> would not have access to its default - shell, preventing <systemitem class="username">root</systemitem> from logging in.</para> + shell, preventing <systemitem class="username">root</systemitem> from logging in and fixing the problem.</para> </sect1> <sect1 xml:id="software"> @@ -139,7 +139,7 @@ of the &os; Handbook.</para> <para>To compile a port, change to the - port's directory and starting the build process. The following example + port's directory and start the build process. The following example installs <application>Apache 2.4</application> from the Ports Collection:</para> @@ -148,8 +148,8 @@ <para>A benefit of using ports to install software is the ability to customize the installation options. This example - enables <application>mod_ldap</application> by setting - <varname>WITH_LDAP</varname>:</para> + specifies that the <application>mod_ldap</application> module + should also be installed:</para> <screen>&prompt.root; <userinput>cd /usr/ports/www/apache24</userinput> &prompt.root; <userinput>make WITH_LDAP="YES" install clean</userinput></screen> @@ -167,8 +167,9 @@ there are no run-levels and <filename>/etc/inittab</filename> does not exist. Instead, startup is controlled by &man.rc.8; scripts. At system boot, <filename>/etc/rc</filename> reads - <filename>/etc/defaults/rc.conf</filename> and - <filename>/etc/rc.conf</filename> to determine which services are to be + <filename>/etc/rc.conf</filename> and + <filename>/etc/defaults/rc.conf</filename> + to determine which services are to be started. The specified services are then started by running the corresponding service initialization scripts located in <filename>/etc/rc.d/</filename> and @@ -190,7 +191,7 @@ the <quote>base</quote> system. User-installed applications are generally installed using <link xlink:href="&url.base;/doc/en_US.ISO8859-1/books/handbook/ports-using.html">Packages or Ports</link>. - In order to keep them separate from the <quote>base</quote> system, + In order to keep them separate from the base system, user-installed applications are installed under <filename>/usr/local/</filename>. Therefore, user-installed binaries reside in <filename>/usr/local/bin/</filename>, @@ -222,7 +223,7 @@ apache24_flags="-DSSL"</programlisting> system:</para> <screen>&prompt.root; <userinput>service sshd start</userinput> - &prompt.root; <userinput>service apache24 start</userinput></screen> +&prompt.root; <userinput>service apache24 start</userinput></screen> <para>If a service has not been enabled, it can be started from the command line using <option>onestart</option>:</para> @@ -235,7 +236,7 @@ apache24_flags="-DSSL"</programlisting> <para>Instead of a generic <emphasis>ethX</emphasis> identifier that &linux; uses to identify a network interface, &os; uses the driver - name followed by a number as the identifier. The following output + name followed by a number. The following output from &man.ifconfig.8; shows two &intel; Pro 1000 network interfaces (<filename>em0</filename> and <filename>em1</filename>):</para> @@ -256,14 +257,14 @@ em1: flags=8843<UP,BROADCAST,RUNNING, <para>An <acronym>IP</acronym> address can be assigned to an interface using &man.ifconfig.8;. To remain persistent across reboots, the <acronym>IP</acronym> configuration must be included in - <filename>/etc/rc.conf</filename>. The following example - specifies the hostname, <acronym>IP</acronym> address, and default gateway:</para> + <filename>/etc/rc.conf</filename>. The following <filename>/etc/rc.conf</filename> entries + specify the hostname, <acronym>IP</acronym> address, and default gateway:</para> <programlisting>hostname="server1.example.com" ifconfig_em0="inet 10.10.10.100 netmask 255.255.255.0" defaultrouter="10.10.10.1"</programlisting> - <para>Use the following to instead configure an interface for <acronym>DHCP</acronym>:</para> + <para>Use the following entries to instead configure an interface for <acronym>DHCP</acronym>:</para> <programlisting>hostname="server1.example.com" ifconfig_em0="DHCP"</programlisting> @@ -318,93 +319,65 @@ ifconfig_em0="DHCP"</programlisting> <sect1 xml:id="updates"> <title>Updating &os;</title> - <para>There are three methods for updating a &os; system: from source, - binary updates, and the installation discs.</para> + <para>There are two methods for updating a &os; system: from source or + binary updates.</para> <para>Updating from source is the most involved update method, but offers the greatest amount of flexibility. The process involves synchronizing a - local copy of the FreeBSD source code with the &os; + local copy of the &os; source code with the &os; <application>Subversion</application> servers. - Once the local source code is up to date you can build new versions of - the kernel and userland. For more information on source updates see - <link xlink:href="&url.base;/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html">the chapter on updating</link> - in the &os; Handbook.</para> + Once the local source code is up-to-date, a new version of + the kernel and userland can be compiled.</para> <para>Binary updates are similar to using <command>yum</command> or - <command>apt-get</command> to update a &linux; system. The command - &man.freebsd-update.8; will fetch new updates and install them. The + <command>apt-get</command> to update a &linux; system. In &os;, + &man.freebsd-update.8; can be used fetch new binary updates and install them. These updates can be scheduled using &man.cron.8;.</para> <note> - <para>If you do use &man.cron.8; to schedule the updates, please be sure - to use <command>freebsd-update cron</command> in your &man.crontab.1; + <para>When using &man.cron.8; to schedule updates, + use <command>freebsd-update cron</command> in the &man.crontab.1; to reduce the possibility of a large number of machines all pulling - updates at the same time.</para> + updates at the same time:</para> <programlisting>0 3 * * * root /usr/sbin/freebsd-update cron</programlisting> </note> - <para>The last update method, updating from the installation discs, is a - straight-forward process. Boot from the installation discs and select - the option to upgrade.</para> + <para>For more information on source and binary updates, refer to + <link xlink:href="&url.base;/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html">the chapter on updating</link> + in the &os; Handbook.</para> </sect1> <sect1 xml:id="procfs"> <title>procfs: Gone But Not Forgotten</title> - <para>In &linux;, you may have looked at + <para>In some &linux; distributions, one could look at <filename>/proc/sys/net/ipv4/ip_forward</filename> to determine if - IP forwarding was enabled. Under &os; you should use &man.sysctl.8; to - view this and other system settings, as &man.procfs.5; has been - deprecated in current versions of &os;. (Although - <command>sysctl</command> is available in &linux; as well.)</para> + <acronym>IP</acronym> forwarding is enabled. In &os; &man.sysctl.8; is instead used to + view this and other system settings.</para> - <para>In the IP forwarding example, you would use the following to - determine if IP forwarding is enabled on your FreeBSD system:</para> + <para>For example, use the following to + determine if <acronym>IP</acronym> forwarding is enabled on a &os; system:</para> <screen>&prompt.user; <userinput>sysctl net.inet.ip.forwarding</userinput> net.inet.ip.forwarding: 0</screen> - <para>The <option>-a</option> flag is used to list all the system + <para>Use <option>-a</option> to list all the system settings:</para> - <screen>&prompt.user; <userinput>sysctl -a</userinput> -kern.ostype: FreeBSD -kern.osrelease: 6.2-RELEASE-p9 -kern.osrevision: 199506 -kern.version: FreeBSD 6.2-RELEASE-p9 #0: Thu Nov 29 04:07:33 UTC 2007 - root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC - -kern.maxvnodes: 17517 -kern.maxproc: 1988 -kern.maxfiles: 3976 -kern.argmax: 262144 -kern.securelevel: -1 -kern.hostname: server1 -kern.hostid: 0 -kern.clockrate: { hz = 1000, tick = 1000, profhz = 666, stathz = 133 } -kern.posix1version: 200112 -...</screen> + <screen>&prompt.user; <userinput>sysctl -a | more</userinput></screen> - <note> - <para>Some of these <command>sysctl</command> values are - read-only.</para></note> - - <para>There are occasions where procfs is required, such as running - older software, using &man.truss.1; to trace system calls, and - <link xlink:href="&url.base;/doc/en_US.ISO8859-1/books/handbook/linuxemu.html">&linux; Binary Compatibility</link>. - (Although, &linux; Binary Compatibility uses its own procfs, &man.linprocfs.5;.) - If you need to mount procfs you can add the following to + <para>If an application requires procfs, + add the following entry to <filename>/etc/fstab</filename>:</para> <screen>proc /proc procfs rw,noauto 0 0</screen> - <note> - <para><option>noauto</option> will prevent + <para>Including <option>noauto</option> will prevent <filename>/proc</filename> from being automatically mounted at - boot.</para></note> + boot.</para> - <para>And then mount procfs with:</para> + <para>To mount the file system without rebooting:</para> <screen>&prompt.root; <userinput>mount /proc</userinput></screen> </sect1> @@ -412,8 +385,7 @@ kern.posix1version: 200112 <sect1 xml:id="commands"> <title>Common Commands</title> - <sect2 xml:id="packageCommands"> - <title>Package Management</title> + <para>Some common command equivalents are as follows:</para> <para> <informaltable frame="none" pgwide="1"> @@ -429,46 +401,26 @@ kern.posix1version: 200112 <tbody> <row> <entry><command>yum install package</command> / <command>apt-get install package</command></entry> - <entry><command>pkg_add -r package</command></entry> - <entry>Install <replaceable>package</replaceable> from remote repository</entry> + <entry><command>pkg install package</command></entry> + <entry>Install package from remote repository</entry> </row> <row> <entry><command>rpm -ivh package</command> / <command>dpkg -i package</command></entry> - <entry><command>pkg_add -v package</command></entry> - <entry>Install package</entry> + <entry><command>pkg add package</command></entry> + <entry>Install local package</entry> </row> <row> <entry><command>rpm -qa</command> / <command>dpkg -l</command></entry> - <entry><command>pkg_info</command></entry> + <entry><command>pkg info</command></entry> <entry>List installed packages</entry> </row> - </tbody> - </tgroup> - </informaltable> - </para> - </sect2> - - <sect2 xml:id="systemCommands"> - <title>System Management</title> - - <para> - <informaltable frame="none" pgwide="1"> - <tgroup cols="3"> - <thead> - <row> - <entry>&linux; command</entry> - <entry>&os; equivalent</entry> - <entry>Purpose</entry> - </row> - </thead> - <tbody> <row> <entry><command>lspci</command></entry> <entry><command>pciconf</command></entry> - <entry>List PCI devices</entry> + <entry>List <acronym>PCI</acronym> devices</entry> </row> <row> @@ -492,15 +444,14 @@ kern.posix1version: 200112 </tgroup> </informaltable> </para> - </sect2> </sect1> <sect1 xml:id="conclusion"> <title>Conclusion</title> - <para>Hopefully this document has provided you with enough to get - started with &os;. Be sure to take a look at the <link xlink:href="&url.base;/doc/en_US.ISO8859-1/books/handbook/index.html">&os; Handbook</link> - for more in depth coverage of the topics touched on as well as - the many topics not covered in this document.</para> + <para>This document has provided an overview of + &os;. Refer to the <link xlink:href="&url.base;/doc/en_US.ISO8859-1/books/handbook/index.html">&os; Handbook</link> + for more in-depth coverage of these topics as well as + the many topics not covered by this document.</para> </sect1> </article>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201402041820.s14IKu5D090632>