I've been reading some tutorials/guides/etc here and there about Samba and I'm a little confused. I have two Slack boxes (my main box and an old POS I plan to use as a place to practice a little Apache/web serving) and I want to just transfer files between them. Do I have to have something like Samba running to send say an HTML or script file from my main box to my other "test" server? Most of the Samba guides I've found deal with transferring files between Linux and Windows. My computers are already connected to the internet via a router (hence each other) so I guess I'm looking for a quick and easy solution rather than having to straighten out my myriad of questions and confusion with Samba.

1) If you only want to transfer files, have a look at scp. On the server side you only have to run sshd.

2) Samba. On the client side you have to mount your samba share. Look for smbmount (it's equal to: "mount -t smbfs"). It would be the same as mounting a Windows share.

3) NFS. I don't know if Slack's Kernel support nfs, but I think so. Google for the NFS HOWTO.


So it's up to you. In my eyes the easiest solution is the scp one.

(Maybe for the future: There are also projects to mount directories with plain ssh. sshfs or shfs for example. But they didn't work stable enough on my setup)

dont use samba to talk between linux boxes. it's like both slack boxes having a chineese interpretter e.g

slack 1 (english) > chineese 1 (mandarin) > chineese 2 (mandarin) > slack 2 (english)

as you can see it's silly and complicated. using nfs, scp, ftp....

slack 1 (english) > slack 2 (english).

well silly analogy but you get the point. samba is for windows compatibilty.

you could use NFS, but personally i would just use SSH for the odd file transfer (use nfs if you want to copy things all the time). SCP is part of the SSH suite of tools.

i just wrote this mini howto on SSH.

hope it helps....

http://www.linuxquestions.org/questi...d.php?t=419680

If you want to play with Apache, just run it on one box and use its ip in the browser on the other box to connect.

If you want use ssh to connect from one to other to run commands and/or start services use 'ssh ip'. You will be asked pass and then you can run commands as if you were sitting at other box.

Actually it's a great analogy. I'll take a look at that tutorial and see what I can dig up on Google. I just had no idea where to start and now I've got a little better idea of what I need .. I think.

with my howto you should be able to copy files between your boxes very easily.

it may be worth setting up NFS is you require mounted file systems...

I use NFS because I mount drives/tranfer loads of files.

Fairly easy to setup, and Slackware DOES support it straight out of the kernel.(Sorry, dom83. Slackware supports most everything. Recompiles for me are required to get RID of stuff I don't use....lol)

yes, i'm using a NetBSD NFS server and a Slackware NFS client. although it also work's the other way around.

if you want an nfs client in slackware dont forget to chmod +x /etc/rc.d/rc.portmap

Just a quick update. I got my computers talking and I'm able to send files back and forth using scp following satinet's How-To in the other thread. I'm sure I'll be content with this setup for a while until the novelty/convenience wears off and I have time to look into NFS a little more. Thanks again!

scp is great.

Another option is using Konqueror (assuming you use kde) and typing "fish://remote_host" in the url window. You'll be prompted for your user name and password on the remote machine.

Brian

okay i'll do the NFS howto soon, when i get the time

if you like my SSH post, please rate it :-) thanks