FreeBSDwiki - User contributions [en]

User talk:Light

2005-07-27T15:50:53Z

168.210.90.181:

doesn't ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/5.4/ the bootonly.iso do this?

--[[User:Dave|Dave]] 11:42, 27 Jul 2005 (EDT)

----
----

-bootonly doesn't include the base system, you have to download that for each box you install on if you use that iso unfortunately.

--[[User:168.210.90.181|168.210.90.181]] 11:50, 27 Jul 2005 (EDT)

Sysctl

2005-07-27T15:49:02Z

168.210.90.181:

'''sysctl''' is used to get/set various kernel and kernel module parameters.

To get the value of a kernel parameter:

[root@splat ~]# '''sysctl hw.physmem'''
hw.physmem: 130453504

To set the value of a kernel parameter:

[root@splat ~]# '''sysctl net.link.ether.bridge=0'''
net.link.ether.bridge: 1 -> 0

Please note that some parameters are read-only and cannot be changed.

You can use the '''-a''' parameter to list all '''sysctl''' variables. Coupled with [[grep]] this makes a great way to find the '''sysctl''' variable you're looking for.

[root@splat ~]# '''sysctl -a | grep mem'''
vm.zone_kmem_pages: 182
vm.zone_kmem_kvaspace: 14725120
vfs.ufs.dirhash_maxmem: 2097152
vfs.ufs.dirhash_mem: 292312
hw.physmem: 130453504
hw.usermem: 107544576

[[Category:System Commands]]

Sysctl

2005-07-27T15:43:46Z

168.210.90.181:

'''sysctl''' is used to get/set various kernel and kernel module parameters

[[Category:System Commands]]

Gotchas, Linux

2005-07-27T15:27:46Z

168.210.90.181:

==Things you should know if you're coming to FreeBSD from Linux==
# The kernels are different -- monolithic instead of microkernels, although FreeBSD does allow dynamic loading of modules (see [[kldstat]], [[kldload]], [[kldunload]].)
# No iptables/netfilter: ipfw packet filter takes it's place, but you have to recompile your kernel to include it
# 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.
# 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.
# Java's a tough nut to install. Deal.
# /stand/sysinstall will be quite useful to you at first.
# [[bash]] is not the default shell, [[csh]] or [[tcsh]] is. If you want to change that, see [[chsh]].
# 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 eth0 or whatever. FreeBSD names it's interfaces by the driver they use; you'll see rl0, ed0, hme0, etc.
# /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]].
# [[devinfo]] and [[swapinfo]] will do a lot of [[sysctl]] magic for you.
# Software RAID? See [[vinum]].
# Bandwidth limiting/traffic shaping? See [[dummynet]]
# Disk encryption? [[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-encrypting.html It's in the Handbook]]
# You need to be a member of the wheel group to allow you to su to root.
# Shell scripts do not use '''seq 1 10'''. They use '''jot 10 1''' instead.
# /boot/loader.conf is where you set which kernel modules to load at boot time. /etc/rc.conf is where you set which system daemons to load at boot time.
[[Category : Linux Equivalents]]

Gotchas, Linux

2005-07-27T15:25:27Z

168.210.90.181:

Gotchas, Linux

2005-07-27T15:24:49Z

168.210.90.181:

==Things you should know if you're coming to FreeBSD from Linux==
# The kernels are different -- monolithic instead of microkernels, although FreeBSD does allow dynamic loading of modules (see [[kldstat]], [[kldload]], [[kldunload]].)
# No iptables/netfilter: ipfw packet filter takes it's place, but you have to recompile your kernel to include it
# 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.
# 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.
# Java's a tough nut to install. Deal.
# /stand/sysinstall will be quite useful to you at first.
# [[bash]] is not the default shell, [[csh]] or [[tcsh]] is. If you want to change that, see [[chsh]].
# 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 eth0 or whatever. FreeBSD names it's interfaces by the driver they use; you'll see rl0, ed0, hme0, etc.
# /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]].
# [[devinfo]] and [[swapinfo]] will do a lot of [[sysctl]] magic for you.
# Software RAID? See [[vinum]].
# Bandwidth limiting/traffic shaping? See [[dummynet]]

# Disk encryption? [[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-encrypting.html It's in the Handbook]]
# You need to be a member of the wheel group to allow you to su to root.
# Shell scripts do not use '''seq 1 10'''. They use '''jot 10 1''' instead.
[[Category : Linux Equivalents]]

Gotchas, Linux

2005-07-27T15:24:18Z

168.210.90.181:

==Things you should know if you're coming to FreeBSD from Linux==
# The kernels are different -- monolithic instead of microkernels, although FreeBSD does allow dynamic loading of modules (see [[kldstat]], [[kldload]], [[kldunload]].)
# No iptables/netfilter: ipfw packet filter takes it's place, but you have to recompile your kernel to include it
# 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.
# 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.
# Java's a tough nut to install. Deal.
# /stand/sysinstall will be quite useful to you at first.
# [[bash]] is not the default shell, [[csh]] or [[tcsh]] is. If you want to change that, see [[chsh]].
# 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 eth0 or whatever. FreeBSD names it's interfaces by the driver they use; you'll see rl0, ed0, hme0, etc.
# /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]].
# [[devinfo]] and [[swapinfo]] will do a lot of [[sysctl]] magic for you.
# Software RAID? See [[vinum]].
# Bandwidth limiting/traffic shaping? See [[dummynet]]
# Shell scripts do not use '''seq 1 10''. They use '''jot 10 1''' instead.
# Disk encryption? [[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-encrypting.html It's in the Handbook]]
# You need to be a member of the wheel group to allow you to su to root.
[[Category : Linux Equivalents]]

Gotchas, Linux

2005-07-27T15:19:05Z

168.210.90.181:

Gotchas, Linux

2005-07-27T15:16:30Z

168.210.90.181:

==Things you should know if you're coming to FreeBSD from Linux==
# The kernels are different -- monolithic instead of microkernels, although FreeBSD does allow dynamic loading of modules (see [[kldstat]], [[kldload]], [[kldunload]].)
# No iptables/netfilter: ipfw packet filter takes it's place, but you have to recompile your kernel to include it
# 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.
# 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.
# Java's a tough nut to install. Deal.
# /stand/sysinstall will be quite useful to you at first.
# [[bash]] is not the default shell, [[csh]] or [[tcsh]] is. If you want to change that, see [[chsh]].
# 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 eth0 or whatever. FreeBSD names it's interfaces by the driver they use; you'll see rl0, ed0, hme0, etc.
# /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]].
# [[devinfo]] and [[swapinfo]] will do a lot of [[sysctl]] magic for you.
# Software RAID? See [[vinum]].
# Bandwidth limiting/traffic shaping? See [[dummynet]]
# Disk encryption? [[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-encrypting.html It's in the Handbook]]
# You need to be a member of the wheel group to allow you to su to root.
[[Category : Linux Equivalents]]

Gotchas, Linux

2005-07-27T15:13:11Z

168.210.90.181:

==Things you should know if you're coming to FreeBSD from Linux==
# The kernels are different -- monolithic instead of microkernels, although FreeBSD does allow dynamic loading of modules (see [[kldstat]], [[kldload]], [[kldunload]].)
# No iptables/netfilter: ipfw packet filter takes it's place, but you have to recompile your kernel to include it
# 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.
# If in doubt, read the Handbook (or ask here).
# Different filesystems: linux uses ext2/ext3/reiserfs by default (usually) and FreeBSD uses UFS. Yes, it does journaling.
# Java's a tough nut to install. Deal.
# /stand/sysinstall will be quite useful to you at first.
# [[bash]] is not the default shell, [[csh]] or [[tcsh]] is. If you want to change that, see [[chsh]].
# 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 eth0 or whatever. FreeBSD names it's interfaces by the driver they use; you'll see rl0, ed0, hme0, etc.
# /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]].
# [[devinfo]] and [[swapinfo]] will do a lot of [[sysctl]] magic for you.
# Software RAID? See [[vinum]].
# Bandwidth limiting/traffic shaping? See [[dummynet]]
# Disk encryption? [[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-encrypting.html It's in the Handbook]]
# You need to be a member of the wheel group to allow you to su to root.
[[Category : Linux Equivalents]]

Gotchas, Linux

2005-07-27T15:03:17Z

168.210.90.181:

==Things you should know if you're coming to FreeBSD from Linux==
# The kernels are different -- monolithic instead of microkernels, although FreeBSD does allow dynamic loading of modules (see [[kldstat]], [[kldload]], [[kldunload]].)
# No iptables/netfilter: ipfw packet filter takes it's place, but you have to recompile your kernel to include it
# 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.
# If in doubt, read the Handbook (or ask here).
# Different filesystems: linux uses ext2/ext3/reiserfs by default (usually) and FreeBSD uses UFS. Yes, it does journaling.
# Java's a tough nut to install. Deal.
# /stand/sysinstall will be quite useful to you at first.
# [[bash]] is not the default shell, [[csh]] or [[tcsh]] is. If you want to change that, see [[chsh]].
# 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 eth0 or whatever. FreeBSD names it's interfaces by the driver they use; you'll see rl0, ed0, hme0, etc.
# /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]].
# [[devinfo]] and [[swapinfo]] will do a lot of [[sysctl]] magic for you.
# Software RAID? See [[vinum]].
# Bandwidth limiting/traffic shaping? See [[dummynet]]
# Disk encryption? [[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-encrypting.html It's in the Handbook]]

[[Category : Linux Equivalents]]

User:Light

2005-07-27T14:55:28Z

168.210.90.181:

FreeBSD fanatic, wiki lurker and occasional contributor.

I miss the -miniinst ISO. When I install I generally:
#Install all the base system binaries, source and ports.
#Install cvsup-without-gui.
#Update to the latest system sources and ports.
#Build and install world.
#pkg_delete -a.

So quite frankly, the full disc ISOs are a waste of time to download and the -bootonly disc is not re-usable.

I'm just wondering if anyone else out there does the same?

- Light

P.S. I come from South Africa where bandwidth is both scarce and expensive, so downloading a full disc ISO is an issue.

Talk:Df

2005-07-27T14:40:41Z

168.210.90.181:

I'd like to see a link here to "Memory free". Does anybody know of a quick and simply was to get a [[df]]-style memory listing (something like the '''free''' command under Linux or the '''mem''' command under DOS)?

I know I can use [[top]], but that shows me a whole lot of stuff I don't wanna see, and not everything I want to see (for instance the total amount of physical memory).

I know I can type
[light@splat ~]$ '''sysctl -n hw.physmem'''
to get the amount of physical memory. I can also get a whole bunch of info from [[vmstat]].

If I have the Linux emulation layer installed and the Linux proc system mounted I can type

[light@splat ~]$ '''cat /usr/compat/linux/proc/meminfo'''

This gives me almost exactly what I, or in fact what any person first logging into a server and worrying about memory usage, would want to know.

So, is there a '''simple''' answer, one that doesn't require anything installed except the basic system? ;)

- [[User:Light|Light]]

----
Have you looked at '''muse'''?

http://www.freebsdsoftware.org/ports.php?c=sysutils&n=muse

--[[User:Jimbo|Jimbo]] 04:08, 11 Sep 2004 (GMT)

----
only thing i can think of is to make a script that runs those commands and maybe pull them together and output 'em to STOUT. Ideally, a bourne shell script so you could port it to other unixes. I did find that annoying the first time I tried "free" on a BSD CLI.

--[[User:Dave|Dave]]

although looking at muse in action, it's pretty nice.

-d.

Cd

2004-09-06T13:36:11Z

168.210.90.181:

Under FreeBSD and other unixlike OSes, '''cd''' means just what it does under Windows - "change directory."

The notable differences being that under unixlike OSes a space is required between '''cd''' and the name of the directory to change to and a forward slash '''/''' is used instead of a backward slash '''\'''

eg.

cd\stuff (windows)
cd /stuff (unixlike)

cd.. (windows)
cd .. (unixlike)

[[Category:Windows Equivalents]]