You should set up avahi and a vnc server. After that you can connect remotely from another machine and see the virtual desktop. Maybe you don?t need avahi, I don?t know if your home machines are windows, osx or linux. But either you use a monitor or you connect via vnc. A third solution would be using ssh, but I don?t know if your xbmc can be used that way.
There's a whole bunch of ways to control Raspbmc remotely.
As other people have mentioned, ssh. And Google on "ssh without password" to find how to set up authentication keys if you're going to use it often.
Files are best handled via a Samba server, so that you can move files around with your remote machine's usual file-manager. (XBMC has a Samba client, but Raspbmc adds a Samba server too.) Enable it (via the XBMC desktop on your TV, for the moment) as follows:
You then have to Google how to use a Samba server from whatever remote OS you're using. You would mount a "CIFS" share on remote Linux, for example.
Also you can remote-control XBMC itself with the "xbmc-send" program. I can't remember if it's installed by default, or if you have to install the "xbmc-eventclients-xbmc-send" package manually. If so, via ssh:
Then you can control XBMC via ssh. The list of commands is at:
E.g., play a video via ssh with: xbmc-send --action="PlayMedia(/home/pi/vid/vid.mp4)"
Enable remote-control (but I'm not sure if this is necessary) like this: system > services > remote-control > allow other systems to control XBMC
Then if you're using Linux on your remote machine, install the package "xbmc-eventclients-xbmc-send" there (it's in Ubuntu's repository, for example) and you can then control XBMC with remote (not ssh) scripts, e.g.:
Assuming that you have SSH configured to link the two hosts, another way that works rather well is to use gftp but select the SSH2 file transfer protocol. This causes it to connect to the remote sshd server and to operate as a nice, graphical sftp client.
martin@ | Martin Gregorie
gregorie. | Essex, UK
If it's the "uid:gid" issue that you're thinking about; if you've defaulted to 1000:1000 for your own user account on the remote machine, then the "pi" owned files will appear to have your own username, which works OK for file transfer. So on the remote machine:
(pi1 being the pi's hostname assigned to an ip address in /etc/hosts)
If your user account has a different uid:gid (as mine does), it does mean that you need to "sudo" to move files onto the pi. I use the KDE Root Actions Servicemenu to allow me to do it from the filemanager: