Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a 70GB drive RAID1'd that I need to install Red Hat on, then configure as an FTP server. You guys have helped me understand how to load the FTP server once I get the server loaded, but what sizes to use to properly partition the server as I load it, I always have a hard time with since I'm new to Linux. Does anyone have any advice?
Looking at other servers, they have a
But not sure what's best with only 70GB for an FTP only server.
You won't need to break it down into that many partitions for something like that. At a minimum I would suggest putting whatever directory you are exposing over FTP to be on it's own partition, the rest could go onto
1 or 2 primary partitions, plus swap.
What exactly is the role of this FTP server? Is it going to be a download-only anonymous like a software mirror, or will there be individual user accounts/directories and uploads?
The FTP server will be used for a few clients to send and grab files from with their own specific accounts. They can all dump into the ftp root since nothing is highly sensitive, or create a subfolder if they want.
Well, if there are going to be multiple users, presumably you are going to be serving files out of /home, so you would want to put that on it's own partition.
If you were doing a big anonymous FTP server like a distribution mirror or something, you could potentially change the default FTP directory to something like /mnt/ftp and mount a second partition on that.
This is my first FTP server, so I'm not really sure where vsftpd makes the root at, or if it can (or should be for security sake) changed.
By default, it going to be the home directory of whatever user connects, so /home/username. So putting /home on it's own partition would separate all the user's FTP directories from the OS.
But for example on my server the OS is stored on an 8 GB CF card, and all remote-accessible files are held on a 1 TB HDD. I want to keep local user accounts on CF and only the publicly accessible data on the HDD, so in my case I don't want to put all of /home on the HDD. So I only allow the user "ftp", and have the FTP root set as /mnt/pub_ftp (where the 1 TB drive is mounted).
There are a lot of ways you could set the server up, and it is hard to argue for any one "right" way. In your case, I would probably just do three partitions. One for the root filesystem (/), one for /home (where the FTP accounts will be), and the third for a small swap space.
Keep in mind once you have your ftp server up and running every time you add a user the user has the ability to view all all system files normally read only. If you don't want that then use chroot to set their home directory for example /home/username