From owner-svn-doc-head@FreeBSD.ORG Tue Feb 4 18:20:56 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D5A24FE2; Tue, 4 Feb 2014 18:20:56 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A611919AF; Tue, 4 Feb 2014 18:20:56 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s14IKuge090633; Tue, 4 Feb 2014 18:20:56 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s14IKu5D090632; Tue, 4 Feb 2014 18:20:56 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201402041820.s14IKu5D090632@svn.freebsd.org> From: Dru Lavigne Date: Tue, 4 Feb 2014 18:20:56 +0000 (UTC) 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 X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Feb 2014 18:20:56 -0000 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 @@ Introduction - This document highlights the technical differences between &os; and + 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;. @@ -55,7 +55,7 @@ In fact, Bash is not even in the default installation. Instead, &os; uses &man.tcsh.1; as the default shell. However, Bash and other - shells are available in &os;'s Packages and Ports Collection. + shells are available for installation using the &os; Packages and Ports Collection. 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 /usr/local/bin is located may not be mounted. In this case, root would not have access to its default - shell, preventing root from logging in. + shell, preventing root from logging in and fixing the problem. @@ -139,7 +139,7 @@ of the &os; Handbook. 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 Apache 2.4 from the Ports Collection: @@ -148,8 +148,8 @@ A benefit of using ports to install software is the ability to customize the installation options. This example - enables mod_ldap by setting - WITH_LDAP: + specifies that the mod_ldap module + should also be installed: &prompt.root; cd /usr/ports/www/apache24 &prompt.root; make WITH_LDAP="YES" install clean @@ -167,8 +167,9 @@ there are no run-levels and /etc/inittab does not exist. Instead, startup is controlled by &man.rc.8; scripts. At system boot, /etc/rc reads - /etc/defaults/rc.conf and - /etc/rc.conf to determine which services are to be + /etc/rc.conf and + /etc/defaults/rc.conf + to determine which services are to be started. The specified services are then started by running the corresponding service initialization scripts located in /etc/rc.d/ and @@ -190,7 +191,7 @@ the base system. User-installed applications are generally installed using Packages or Ports. - In order to keep them separate from the base system, + In order to keep them separate from the base system, user-installed applications are installed under /usr/local/. Therefore, user-installed binaries reside in /usr/local/bin/, @@ -222,7 +223,7 @@ apache24_flags="-DSSL" system: &prompt.root; service sshd start - &prompt.root; service apache24 start +&prompt.root; service apache24 start If a service has not been enabled, it can be started from the command line using : @@ -235,7 +236,7 @@ apache24_flags="-DSSL" Instead of a generic ethX 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 (em0 and em1): @@ -256,14 +257,14 @@ em1: flags=8843<UP,BROADCAST,RUNNING, An IP address can be assigned to an interface using &man.ifconfig.8;. To remain persistent across reboots, the IP configuration must be included in - /etc/rc.conf. The following example - specifies the hostname, IP address, and default gateway: + /etc/rc.conf. The following /etc/rc.conf entries + specify the hostname, IP address, and default gateway: hostname="server1.example.com" ifconfig_em0="inet 10.10.10.100 netmask 255.255.255.0" defaultrouter="10.10.10.1" - Use the following to instead configure an interface for DHCP: + Use the following entries to instead configure an interface for DHCP: hostname="server1.example.com" ifconfig_em0="DHCP" @@ -318,93 +319,65 @@ ifconfig_em0="DHCP" Updating &os; - There are three methods for updating a &os; system: from source, - binary updates, and the installation discs. + There are two methods for updating a &os; system: from source or + binary updates. 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; Subversion 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 - the chapter on updating - in the &os; Handbook. + Once the local source code is up-to-date, a new version of + the kernel and userland can be compiled. Binary updates are similar to using yum or - apt-get to update a &linux; system. The command - &man.freebsd-update.8; will fetch new updates and install them. The + apt-get 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;. - If you do use &man.cron.8; to schedule the updates, please be sure - to use freebsd-update cron in your &man.crontab.1; + When using &man.cron.8; to schedule updates, + use freebsd-update cron in the &man.crontab.1; to reduce the possibility of a large number of machines all pulling - updates at the same time. + updates at the same time: 0 3 * * * root /usr/sbin/freebsd-update cron - 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. + For more information on source and binary updates, refer to + the chapter on updating + in the &os; Handbook. procfs: Gone But Not Forgotten - In &linux;, you may have looked at + In some &linux; distributions, one could look at /proc/sys/net/ipv4/ip_forward 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 - sysctl is available in &linux; as well.) + IP forwarding is enabled. In &os; &man.sysctl.8; is instead used to + view this and other system settings. - In the IP forwarding example, you would use the following to - determine if IP forwarding is enabled on your FreeBSD system: + For example, use the following to + determine if IP forwarding is enabled on a &os; system: &prompt.user; sysctl net.inet.ip.forwarding net.inet.ip.forwarding: 0 - The flag is used to list all the system + Use to list all the system settings: - &prompt.user; sysctl -a -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 -... + &prompt.user; sysctl -a | more - - Some of these sysctl values are - read-only. - - There are occasions where procfs is required, such as running - older software, using &man.truss.1; to trace system calls, and - &linux; Binary Compatibility. - (Although, &linux; Binary Compatibility uses its own procfs, &man.linprocfs.5;.) - If you need to mount procfs you can add the following to + If an application requires procfs, + add the following entry to /etc/fstab: proc /proc procfs rw,noauto 0 0 - - will prevent + Including will prevent /proc from being automatically mounted at - boot. + boot. - And then mount procfs with: + To mount the file system without rebooting: &prompt.root; mount /proc @@ -412,8 +385,7 @@ kern.posix1version: 200112 Common Commands - - Package Management + Some common command equivalents are as follows: @@ -429,46 +401,26 @@ kern.posix1version: 200112 yum install package / apt-get install package - pkg_add -r package - Install package from remote repository + pkg install package + Install package from remote repository rpm -ivh package / dpkg -i package - pkg_add -v package - Install package + pkg add package + Install local package rpm -qa / dpkg -l - pkg_info + pkg info List installed packages - - - - - - - - System Management - - - - - - - &linux; command - &os; equivalent - Purpose - - - lspci pciconf - List PCI devices + List PCI devices @@ -492,15 +444,14 @@ kern.posix1version: 200112 - Conclusion - Hopefully this document has provided you with enough to get - started with &os;. Be sure to take a look at the &os; Handbook - for more in depth coverage of the topics touched on as well as - the many topics not covered in this document. + This document has provided an overview of + &os;. Refer to the &os; Handbook + for more in-depth coverage of these topics as well as + the many topics not covered by this document.