Been a while since I've been here; I have my iMac and MBpro connected via firewire, and they can see each other when I open the finder windows.
But I'd like to be able to 'see' each computer on the other via the terminal application; and I can't see them right now. I can transfer files via the finder windows, etc; but since I'd like to get under the hood, I want to do it from terminal just in case.
I used to be able to do this, but I forgot; can anyone help me out?
Why are the MAC addresses duplicated in the "seastat" command output for all the LPARs? I can't figure out why one stanza has the LPAR information (hostname and IP) while the other stanza does not? Why the two separate sections and two separate sets of usage information (Bytes and Packets)?... (1 Reply)
I have my iMac and MB pro connected by firewire. I can see the connection in the finderwindow, but can't locate the machines in terminal. Can someone help me? I do most of my work in Terminal and would like to move/copy files from one machine to another like that -- I could have sworn I was able... (4 Replies)
FIREWIRE(4) BSD Kernel Interfaces Manual FIREWIRE(4)NAME
firewire -- IEEE1394 High-performance Serial Bus
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device firewire
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
firewire_load="YES"
DESCRIPTION
FreeBSD provides machine-independent bus support and raw drivers for firewire interfaces.
The firewire driver consists of two layers: the controller and the bus layer. The controller attaches to a physical bus (like pci(4)). The
firewire bus attaches to the controller. Additional drivers can be attached to the bus.
Up to 63 devices, including the host itself, can be attached to a firewire bus. The root node is dynamically assigned with a PHY device
function. Also, the other firewire bus specific parameters, e.g., node ID, cycle master, isochronous resource manager and bus manager, are
dynamically assigned, after bus reset is initiated. On the firewire bus, every device is identified by an EUI 64 address.
FILES
/dev/fw0.0
/dev/fwmem0.0
SEE ALSO fwe(4), fwip(4), fwohci(4), pci(4), sbp(4), eui64(5), fwcontrol(8), kldload(8), sysctl(8)HISTORY
The firewire driver first appeared in FreeBSD 5.0.
AUTHORS
The firewire driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa for the FreeBSD project.
BUGS
See fwohci(4) for security notes.
BSD April 1, 2006 BSD