Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
wiki:fileserver [2012/09/10 12:41] – Added some details concerning config files and startup 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 recipe for setting up a NFS server that is available to all machines in a subnet.\\ | ||
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 === | ||
- | /etc/exports\\ | + | The NFS server is configured by 3 files: |
- | /etc/hosts.deny\\ | + | - /etc/hosts.deny\\ |
- | / | + | |
+ | | ||
+ | |||
+ | You can get away with leaving // | ||
+ | please keep in mind that this arrangement is only secure enough within a home network behind a firewall. | ||
+ | |||
+ | Also keep in mind that TinyCore puts its root filesystem "/" | ||
+ | This also applies to the /etc directory. The boot options for persistence do not help for this directory.\\ | ||
+ | If you want to keep some /etc files persistent, you must arrange for them to be copied from some persistent location into /etc at boot time.\\ | ||
+ | The easiest way is to create a /opt/etc directory, and keep persistent copies of your /etc files there.\\ | ||
+ | At boot time, copy everything from /opt/etc into /etc by some command in file / | ||
+ | |||
+ | To share the directory /home/nfs for read-write access, create the file **/ | ||
+ | < | ||
+ | This will make the directory /home/nfs available for any machine in the IP subnet (192.168.2.xxx).\\ | ||
+ | You can also specify exact IP adresses. | ||
=== Starting the NFS server === | === Starting the NFS server === | ||
Line 20: | Line 38: | ||
"/ | "/ | ||
</ | </ | ||
+ | |||
+ | === Approaching the NFS server by a client === | ||
+ | If your TinyCore box with the NFS server has IP address 192.168.2.252 and a / | ||
+ | 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:/ | ||
+ | </ | ||
+ | ( See [[boot option nodhcp]] to obtain a fixed IP address for the server) | ||
See also: | See also: | ||
Line 25: | Line 51: | ||
* [[http:// | * [[http:// | ||
* [[http:// | * [[http:// | ||
- | * | + | * [[http:// |
+ | |||
+ | === Managing the file server === | ||
+ | |||
+ | Occasionally, | ||
+ | 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.\\ | ||
+ | You can use [[OpenSSH]], | ||
+ | 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. | ||