Okay, went through that, when I turned the power to the HD back on, and error message popup stating "Can't mount" appeared with this message "Invalid mount option when attempting to mount the volume 'New Volume'."
Here are my actions in terminal:
[bob@localhost ~]$ mkdir /home/bob/Test
[bob@localhost ~]$ mount /dev/sdb1
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[bob@localhost ~]$ ls -l Test
total 0
[bob@localhost ~]$
Yep, the firewire HD has a switch, it's pretty much identical to a USB HD as well in every other respect, data transfer is a lot faster than USB though (and it was cheap, 20.00 bucks shipping and all off E-bay).
Here's a portion of /var/log/messages that relates to an instance of the system mounting it as it normally does under /media if that helps:
Nov 22 13:41:13 localhost hald: mounted /dev/sdb1 on behalf of uid 500
Nov 22 13:41:13 localhost ntfs-3g[13925]: Version 2010.1.16 external FUSE 28
Nov 22 13:41:13 localhost ntfs-3g[13925]: Mounted /dev/sdb1 (Read-Write, label "New Volume", NTFS 3.1)
Nov 22 13:41:13 localhost ntfs-3g[13925]: Cmdline options: rw,nosuid,nodev,uhelper=hal,locale=en_US.UTF-8
Nov 22 13:41:13 localhost ntfs-3g[13925]: Mount options: rw,nosuid,nodev,uhelper=hal,silent,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096
Nov 22 13:41:13 localhost ntfs-3g[13925]: Ownership and permissions disabled
So hal's doing the mounting I guess, maybe a config file somewhere to edit where it mounts it?