Gotchas, Linux - Revision history

68.189.250.56 at 05:39, 10 November 2009

2009-11-10T05:39:38Z

145.116.5.243: added Arch to notion of linux distro's using bsd-style init. Because it seems the Arch user base is growing fast:)

2008-11-23T01:24:53Z

added Arch to notion of linux distro's using bsd-style init. Because it seems the Arch user base is growing fast:)

63.249.108.162: oops wrong one

2008-07-28T04:25:38Z

oops wrong one

63.249.108.162: typo

2008-07-28T04:25:07Z

typo

Ninereasons: /* Things you should know if you're coming to FreeBSD from Linux */

2006-04-06T19:35:12Z

Things you should know if you're coming to FreeBSD from Linux

Jimbo at 05:22, 25 January 2006

2006-01-25T05:22:42Z

Jimbo: we can hash this back and forth for a while til we're both happy =)

2006-01-25T05:16:21Z

we can hash this back and forth for a while til we're both happy =)

Dave: placement was ugh, but it was relevant to the section it was added to...edited for clarity.

2006-01-24T14:26:29Z

placement was ugh, but it was relevant to the section it was added to...edited for clarity.

Jimbo: info on how Slackware in particular works not really relevant to new FreeBSD users - the Slack users already know, the rest don't need to

2006-01-24T13:41:59Z

info on how Slackware in particular works not really relevant to new FreeBSD users - the Slack users already know, the rest don't need to

209.161.227.206 at 02:47, 24 January 2006

2006-01-24T02:47:54Z

@@ Line 1: / Line 1: @@
 ==Things you should know if you're coming to FreeBSD from Linux==
-# The kernels are both modular, but the commands for loading/viewing/unloading kernel modules are different -- [[kldstat]], [[kldload]], [[kldunload]] instead of Linux' "lsmod", "insmod" and "rmmod".)
+# The kernels are both modular, but the commands for loading/viewing/unloading kernel modules are different -- [[kldstat]], [[kldload]], [[kldunload]] instead of Linux' "lsmod", "insmod/modprobe" and "rmmod/modprobe -r".)
 # You need to be a member of the wheel group in order to su to root - and you NEED to be able to su to root, because by default you can't log in directly as root over ssh.  (and this is a Good Thing, and should not be changed.)
 # No iptables/netfilter: you have your choice of IPFW, PF, or IPFilter (not recommended for SMP systems).  You can either recompile the kernel to include these, or load the kernel modules at runtime.  QoS and bandwidth throttling are handled via either Dummynet (ipfw) or AltQ (pf)

@@ Line 3: / Line 3: @@
 # You need to be a member of the wheel group in order to su to root - and you NEED to be able to su to root, because by default you can't log in directly as root over ssh.  (and this is a Good Thing, and should not be changed.)
 # No iptables/netfilter: you have your choice of IPFW, PF, or IPFilter (not recommended for SMP systems).  You can either recompile the kernel to include these, or load the kernel modules at runtime.  QoS and bandwidth throttling are handled via either Dummynet (ipfw) or AltQ (pf)
-# Init scripts: [[BSD]] style differs from the [[SysV]] style many/most Linux distros (Slackware being one exception) use.  [[runlevels]] mean different things in BSD-style *nixes, and [[init scripts]] are handled differently - in BSD-style init, rc is configured via a single config file (/etc/rc.conf) with the system rc scripts stored under /etc/rc.d, and local daemon startup scripts in /usr/local/etc/rc.d.
+# Init scripts: [[BSD]] style differs from the [[SysV]] style many/most Linux distros (Slackware and Arch being noteable exceptions) use.  [[runlevels]] mean different things in BSD-style *nixes, and [[init scripts]] are handled differently - in BSD-style init, rc is configured via a single config file (/etc/rc.conf) with the system rc scripts stored under /etc/rc.d, and local daemon startup scripts in /usr/local/etc/rc.d.
 # No /[[proc]] tree. If you're used to banging around /proc to find system info, man [[sysctl]]. If you installed linux-compatibility, see /usr/compat/linux/proc
 # You don't '''have''' to compile everything from ports, it's usually better for your particular system if you ''do''. See [[pkg_add]] and the other pkg tools.

@@ Line 5: / Line 5: @@
 # Init scripts: [[BSD]] style differs from the [[SysV]] style many/most Linux distros (Slackware being one exception) use.  [[runlevels]] mean different things in BSD-style *nixes, and [[init scripts]] are handled differently - in BSD-style init, rc is configured via a single config file (/etc/rc.conf) with the system rc scripts stored under /etc/rc.d, and local daemon startup scripts in /usr/local/etc/rc.d.
 # No /[[proc]] tree. If you're used to banging around /proc to find system info, man [[sysctl]]. If you installed linux-compatibility, see /usr/compat/linux/proc
-# You don't '''have''' to compile everything from ports, its usually better for your particular system if you ''do''. See [[pkg_add]] and the other pkg tools.
+# You don't '''have''' to compile everything from ports, it's usually better for your particular system if you ''do''. See [[pkg_add]] and the other pkg tools.
 # If in doubt, read the Handbook (or ask here).
 # Different filesystems: linux uses ext2/ext3/reiserfs by default (usually) and FreeBSD uses UFS. It does not do journaling, but instead uses a system called soft-updates. Have a look [[http://www.usenix.org/publications/library/proceedings/usenix2000/general/seltzer.html here]] if you would like to know what this means. It seems that [[http://www.freebsd.org/projects/summerofcode.html Google]] might be helping to change this though.
@@ Line 12: / Line 12: @@
 # [[bash]] is not the default shell. [[csh]] (actually [[tcsh]]) is the default for root, sh is the default for normal users. Every other shell under the sun can be installed via the ports tree, and you can use  [[chsh]] to change it for a specific user. Users seeking a decent shell (both [[sh]]-compatible and friendly for interactive use) should consider [[ksh]] or [[pdksh]] as well as bash.
 # Most linux distros use [[vim]], FreeBSD uses [[nvi]] by default. You can change this if it matters to you. Use /usr/ports/editors/vim-lite if you do not want to install the [[X windowing system]] else use /usr/ports/editors/vim.
-# Your NIC is no longer eth0 or eth1 or whatever. FreeBSD names it's interfaces by the driver they use; you'll see rl0, ed0, hme0, etc.  FreeBSD 6.x includes interface renaming, so those that like generic names can use them.
+# Your NIC is no longer eth0 or eth1 or whatever. FreeBSD names its interfaces by the driver they use; you'll see rl0, ed0, hme0, etc.  FreeBSD 6.x includes interface renaming, so those that like generic names can use them.
 # /etc/mtab doesn't show you mounts. [[mount]] and [[df]] do.
 # Your hard disks are no longer /dev/hda or /dev/sda. Now they are /dev/ad0s1a. See [[partitions]].

@@ Line 5: / Line 5: @@
 # Init scripts: [[BSD]] style differs from the [[SysV]] style many/most Linux distros (Slackware being one exception) use.  [[runlevels]] mean different things in BSD-style *nixes, and [[init scripts]] are handled differently - in BSD-style init, rc is configured via a single config file (/etc/rc.conf) with the system rc scripts stored under /etc/rc.d, and local daemon startup scripts in /usr/local/etc/rc.d.
 # No /[[proc]] tree. If you're used to banging around /proc to find system info, man [[sysctl]]. If you installed linux-compatibility, see /usr/compat/linux/proc
-# You don't '''have''' to compile everything from ports, it's usually better for your particular system if you ''do''. See [[pkg_add]] and the other pkg tools.
+# You don't '''have''' to compile everything from ports, its usually better for your particular system if you ''do''. See [[pkg_add]] and the other pkg tools.
 # If in doubt, read the Handbook (or ask here).
 # Different filesystems: linux uses ext2/ext3/reiserfs by default (usually) and FreeBSD uses UFS. It does not do journaling, but instead uses a system called soft-updates. Have a look [[http://www.usenix.org/publications/library/proceedings/usenix2000/general/seltzer.html here]] if you would like to know what this means. It seems that [[http://www.freebsd.org/projects/summerofcode.html Google]] might be helping to change this though.

@@ Line 16: / Line 16: @@
 # Your hard disks are no longer /dev/hda or /dev/sda. Now they are /dev/ad0s1a. See [[partitions]].
 # [[devinfo]] and [[swapinfo]] will do a lot of [[sysctl]] magic for you.
-# Software RAID? See [[vinum]] and [[RAID1, Software, How to setup]].  (Note:  vinum is dead in 5.x, use gvinum, gmirror, or graid)
+# Software RAID? See [[vinum]] and [[RAID1, Software, How to setup]].  (Note:  vinum is dead since 5.3; use [[gvinum]], gmirror, or graid)
 # Disk encryption? [[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-encrypting.html It's in the Handbook]]
 # Shell scripts do not use '''seq 1 10'''. They use '''jot 10 1''' instead.