Testing4

From PC-BSD Wiki
Revision as of 23:29, 3 May 2012 by Tigersharke (Talk | contribs)

Jump to: navigation, search


PC-BSD is based on BSD Unix, meaning that it is not a Linux distribution. If you have used Linux before, you will find that some features that you are used to have different names on a BSD system and that some commands are different. This section covers some of these differences.

Contents

Filesystems

BSD and Linux use different filesystems during installation. Many Linux distros use EXT2, EXT3, EXT4, or ReiserFS, while PC-BSD uses UFS or ZFS. This means that if you wish to dual-boot with Linux or access data on an external drive that has been formatted with a Linux filesystem, you will want to do a bit of research first to see if the data can be made available on both operating systems.

Table 1.4a summarizes the various filesystems commonly used by desktop systems. Most of the desktop managers available from PC-BSD should automatically mount the following filesystems: FAT16, FAT32, EXT2, EXT3 (without journaling), EXT4 (read-only), NTFS5, NTFS6, and XFS. See Files and File Sharing for more information about available file manager utilities.

Table 1.4a: Filesystem Support Between Linux and PC-BSD

Filesystem Native to Type of non-native support Usage notes


Btrfs


Linux


none


Btrfs[1], when complete, is expected to offer a feature set comparable to ZFS[2]


EXT2


Linux


r/w through ext2fs(5)[3]



EXT3


Linux


r/w through ext2fs(5).


EXT3 journaling is not supported. This means that you won't be able to mount a filesystem requiring a journal replay unless you fsck it using an external utility such as e2fsprogs[4].
EXT4 Linux r/o through ext2fs(5)
r/o through ext4fuse[5]
Journaling is not supported. This means that you won't be able to mount a filesystem requiring a journal replay unless you fsck it using an external utility such as e2fsprogs[4]. EXT3 filesystems converted to EXT4 may be more likely to have better results. May not work. Neither having extended attributes 'enabled' nor inodes greater than 128-bytes are supported.
FAT16 Windows r/w through msdosfs(5)[6]
FAT32 Windows r/w through msdosfs(5)
HFS+ Mac OSX none older Mac versions might work with hfsexplorer[7]
JFS Linux none if you're interested in journaling, choose UFS+J during installation
NTFS5 Windows full r/o, some limitations on r/w, via mount_ntfs(8)[8];
full r/w through ntfs-3g(8)[9]
PC-BSD uses ntfs-3g
NTFS6 Windows r/w through ntfs-3g(8)
ReiserFS Linux r/o through reiserfs(5)[10]
UFS PC-BSD r/o support is included in Linux kernel 2.6.5 onwards;
r/w support on Mac;
UFS Explorer[11] can be used on Windows
changed to r/o support in Mac Lion
UFS+S PC-BSD check if your Linux distro provides ufsutils;
r/w support on Mac;
UFS Explorer[11] can be used on Windows
changed to r/o support in Mac Lion
UFS+J PC-BSD check if your Linux distro provides ufsutils;
r/w support on Mac;
UFS Explorer[11] can be used on Windows
changed to r/o support in Mac Lion
XFS Linux r/o through xfs(5)
ZFS PC-BSD, OpenSolaris Linux port;
Mac support is under development[12]

Device Names

Linux and BSD use different naming conventions for devices. For example:

  • in Linux, Ethernet interfaces begin with eth; in BSD, interface names indicate the name of the driver. For example, an Ethernet interface may be listed as re0, indicating that it uses the Realtek re driver. The advantage of this convention is that you can read the man 4 page for the driver (e.g. type man 4 re) to see which models and features are provided by that driver.
  • BSD disk names differ from Linux. IDE drives begin with ad and SCSI and USB drives begin with da.

Feature Names

Some of the features used by BSD have similar counterparts to Linux, but the name of the feature is different. Table 1.4b provides some common examples:

Figure 1.4b: Names for BSD and Linux Features

PC-BSD Linux Description
PF iptables default firewall
/etc/rc.d/ for operating system and /usr/local/etc/rc.d/ for applications rc0.d/, rc1.d/, etc. in PC-BSD the directories containing the startup scripts do not link to runlevels as there are no runlevels; system startup scripts are separated from third-party application scripts
/etc/ttys and /etc/rc.conf telinit and init.d/ terminals are configured in ttys and rc.conf indicates which services will start at boot time

Commands

If you're comfortable with the command line, you may find that some of the commands that you are used to have different names on BSD. Table 1.4c lists some common commands and their equivalents.

Table 1.4c: Common BSD and Linux Commands

PC-BSD Linux Result
dmesg dmesg
lsdev (Is this used anywhere?)
discover what hardware was detected by the kernel
sysctl dev cat /proc/devices display configured devices
pciconf -l -cv lspci -tv show PCI devices
dmesg | grep usb lsusb -tv show USB devices
kldstat lsmod list all modules loaded in the kernel
kldload <module> modprobe <module> load a kernel module for the current session
pbi_add -r <pbiname> rpm -i <package>.rpm install software from the command line
sysctl hw.realmem cat /proc/meminfo hardware memory
sysctl hw.model cat /proc/cpuinfo CPU model
sysctl hw.machine_arch uname -m CPU Architecture
sysctl hw.ncpu getconf _NPROCESSORS_ONLN number of CPUs
uname -vm lsb_release -a
cat /etc/*release
cat /etc/*version
get release version information
gpart show fdisk -l
parted -l
show device partition information

Additional Resources:


Cite error: <ref> tags exist, but no <references/> tag was found
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox