Originally Posted by lumak
Samba - very complicated details for security, takes at least a day for a newbie to figure out a simple file share where the linux box is the host.
Not really. Just install samba, and add something like this into /etc/samba/smb.conf
;My first Samba Config file
server string = my_linux_server
workgroup = homenetwork
encrypt passwords = yes
log file = /var/log/samba/log.%m
security = share
path = /samba
read only = no
guest ok = yes
It could hardly be easier. Then you fire up samba, and if there's no firewalling doing weird things, you should be able to reach your /samba dir from windows. Then it's a matter of reading, learning, adding and changing stuff and tightening the security a bit. Of course you need to make sure that both computers IPs and subnets are in the same range and that the work groups are the same in the case of windows. Ping comes in handy to check if a given computer can see the ip of another computer in the same net.
About 2 and 3, all you need is a cron job, and a tool to do backups. rsync is probably the best for incremental backups. But you can use whatever you want. I advise using standard tools, because that's what you will have in your livecd if something really bad happens.
I can't imagine why would I use ghost for windows or dos, when there are around 12 trillions of ways to do backup (at file level and at image level) in linux natively. However, I don't recommend at all doing image backups while the fs's are mounted with write enabled. You are going to end with a corrupted image because you can't guarantee that the fs is not gonna change while the image is being created. There's really no point in using disk images are backups... Do backups at file level, and use incremental tools when possible like rsync. That will take care of about everything that the OP wanted. That, and cron.
you would need to open up a port on your router, have the linux box listen to the port for an ftp server, have the files shared under the ftp server (symbolic links are usually defaulted to off... I think...), and have one of those auto updating dns things for your dynamic ip (for convenience)
You can use ddclient in linux to take care of autoupdating your ip in dyndns when needed. For the rest, you just need to run the correct server for whatever service you want to access remotely, and make sure your firewall is not locking it. This is a very wide topic, and we can't explain you how to setup every existing server on a simple post.
To the original poster
, I recommend you to rethink the strategy for everything, and then open one thread for every problem. It's more likely that the thread will be of any use if you solve one problem at a time.