Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| wiki:fileserver [2012/10/03 07:51] – Added explanation on persistence for /etc files kennedywalker | wiki:fileserver [2013/05/09 18:22] (current) – added TFTP under listed alternatives tinypoodle | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| A fileserver is a machine other than your workstation, | A fileserver is a machine other than your workstation, | ||
| Usually, a single fileserver provides filesharing between multiple workstations.\\ | Usually, a single fileserver provides filesharing between multiple workstations.\\ | ||
| + | There are a number of alternatives for sharing files: | ||
| + | * NFS | ||
| + | * Samba | ||
| + | * Rsync | ||
| + | * FTP-SFTP-TFTP | ||
| ==== NFS server ==== | ==== NFS server ==== | ||
| - | The following is a simple | + | The following is a simple |
| To set up a NFS **server** under TinyCore, you need 2 packages. (To setup a NFS **client**, you only need the first package.) | To set up a NFS **server** under TinyCore, you need 2 packages. (To setup a NFS **client**, you only need the first package.) | ||
| - nfs-utils.tcz | - nfs-utils.tcz | ||
| - filesystems-`uname -r`.tcz | - filesystems-`uname -r`.tcz | ||
| - | The appropriate install option for both packages is //OnBoot// | + | The appropriate |
| === NFS server configuration files === | === NFS server configuration files === | ||
| Line 36: | Line 40: | ||
| === Approaching the NFS server by a client === | === Approaching the NFS server by a client === | ||
| - | If your TinyCore box with the NFS server has IP address 192.168.2.252, | + | If your TinyCore box with the NFS server has IP address 192.168.2.252 |
| + | then you can access its files from any machine with an IP address like 192.168.2.xxx ; by entering the following command. | ||
| < | < | ||
| sudo mount 192.168.2.252:/ | sudo mount 192.168.2.252:/ | ||
| </ | </ | ||
| - | ( See [[boot option nodhcp]] to obtain a fixed IP address ) | + | ( See [[boot option nodhcp]] to obtain a fixed IP address |
| See also: | See also: | ||
| Line 46: | Line 51: | ||
| * [[http:// | * [[http:// | ||
| * [[http:// | * [[http:// | ||
| - | * | + | * [[http:// |
| === Managing the file server === | === Managing the file server === | ||
| Line 53: | Line 58: | ||
| On such occasions, command-line access through a remote shell can come in handy.\\ | On such occasions, command-line access through a remote shell can come in handy.\\ | ||
| A solution for this, which is secure as well as reasonably cheap on resources is a Secure Shell.\\ | A solution for this, which is secure as well as reasonably cheap on resources is a Secure Shell.\\ | ||
| - | You can use OpenSSH, or Dropbear. (both being more secure than plain old telnet)\\ | + | You can use [[OpenSSH]], or its light-weight alternative [[Dropbear]]. (both being more secure than plain old telnet)\\ |
| + | If you want to use [[http:// | ||
| + | Dropbear does not come with a SFTP server, but it can borrow the SFTP-server that comes with OpenSSH. | ||
| + | |||
| ==== Samba server ==== | ==== Samba server ==== | ||
