zfs get canmount zroot/var. If you used the installer then this property will most likely be set to off for at least the root file system. Normally this would only prevent it from auto mounting when you boot from a rescue CD and import the pool there. But I could imagine that this could also occur in other situations. sysrc zfs_enable.
zpool import on the two pools, and then zfs mounted them. I brought the system down at the end of the day (I can't now remember why) and when I rebooted this morning, the zpools weren't mounted, which caused confusion til I discovered that. I don't have them listed in /etc/fstab, but they weren't listed before, either. zfs_enable="YES" in /etc/rc.conf (I just checked again).
# -- sysinstall generated deltas -- # Tue Oct 21 06:59:05 2008
# Created: Tue Oct 21 06:59:05 2008
# Enable network daemons for user convenience.
# Please make all changes to this file, not to /etc/defaults/rc.conf.
# This file now contains just the overrides from /etc/defaults/rc.conf.
hostname="momcat"
ifconfig_igb0="inet 192.168.0.96 netmask 255.255.255.0"
defaultrouter="192.168.0.98"
#
ntpd_enable="YES"
nfs_enable = "YES"
zfs_enable = "YES"
enable_ppp="YES"
samba_server_enable="YES"
# ---------------
lpd_enable="YES"
dbus_enable="YES"
hald_enable="YES"
moused_enable="YES"
# ---------------
#linux_enable="YES"
sshd_enable="YES"
usbd_enable="YES"
# ---------------
mysql_enable="YES"
mysql_dbdir="/MC/mysql_data"
apache24_enable="YES"
#apache24_http_accept_enable="YES"
# ---------------
ftp_enable="YES"
apm_enable="YES"
# -- cups
cupsd_enable="YES"
devfs_system_ruleset="system"
Or do you mean the ones around the "=" in those 2 lines? Is the interpreter really that fragile?
sh, if that's who's doing the interpretation--no existing files would have to be changed, but extra whitespace would no longer prevent interpretation.It's not the number of whitespaces that matters (when you type commands, i.e. to list the contents of a directory,
ls -l ~ls -l ~# echo $TEST
# TEST = 123
sh: TEST: not found
# TEST=123
# echo $TEST
123 TEST, with a couple of arguments (one of which is the = sign)? It can't really, and so to set a variable you have make it clear you are doing an assignment. It's just one of the limitations of trying to write a script using a shell interpreter.The context. The shell should distinguish between the whitespace(s) used, i.e. in setting a variable, and when parsing commands. Unless you quote or escape the equal sign, the interpreter will consider foo=1 as a variable assignement (and declaration, of course), but if you use whitespaces (foo = 1), will not; it'll threat them (foo, the =, and 1) as separate things.
. Thank you for your clear explanation.
The context. The shell should distinguish between the whitespace(s) used, i.e. in setting a variable, and when parsing commands. Unless you quote or escape the equal sign, the interpreter will consider foo=1 as a variable assignement (and declaration, of course), but if you use whitespaces (foo = 1), will not; it'll threat them (foo, the =, and 1) as separate things.
EDIT: Didn't notice your comment usdmatt, sorry
sh language) doesn't have good design skills, or doesn't pay attention, or doesn't care, then the obnoxiousness will affect those who use his work forever. So it's always better for the designer to consume the obnoxiousness before it's generated rather than afflicting everyone after him. command arg1 arg2 format, than to suddenly switch to assignment if an argument happens to be =; A shell doing something different because the first argument to a command is = would be considered a bug by most people. Choosing name=value for assignment is a perfectly reasonable solution for adding variable assignment - without creating any side effects for normal command execution (apart from the fact you can't have an executable called my=program of course).