This one time, at band camp, Debian User said: > Ok, I am having a hard time being new to linux and all. Let's go slow then > Basically I am looking for the Standard procedure for setting up an > apache server, and ftp for users on a debian box. > > Someone first tells me not to use FTP, and use some windows util that > none of my clients will have. I am at a loss, isn't FTP what everyone > uses, they sure did on the window servers I use to administrate. This is because FTP sends it's login name and password as cleartext, and if these users also have system accounts, they've just advertised how to break into your machine. You can instruct them to use sftp (there is a windows port of the ssh suite) This encrypts everything sent, so that you don't need to worry about password sniffing and the like. > You have to figure that I am a newbie and I don't know all the different > ways of doing things, but I was hoping that there was a way that the > Average administrator would set up things. > > I looked into this UserDir module, but I am failing to see how that is > going to help me, for all it seems to do is map a web site to a users > directory. I failed to find a page that explained just what it does, I > only found reference in experienced terms. > > What I need to know is what FTP program would be best to use so that I > don't have to instruct users on this. > Also need to know where I should store my HTML files. (/var/www) or > (/home/*user/www) ? Each user has a home directory (/home/whatever), OK. In each of their home directories, they can have a folder called public_html. They use that for their user page. It is owned by them, and accessable to them without your intervention. > I don't know how to use Umask yet, can this set permissions in a Certain > directory so that all new files created in that directory are a certian > permission? Don't worry about it yet, then. Look around, particularly at tldp.org. Their documentation is excellent. > I see much more documentation needed in the Linux world if this is going > to be easyier on newbies, there is plenty of reference, but the system > lacks Layman terms, or terms that explain how something works as a > whole, or how something should be setup for a certain situation. Maybe > I am just looking in the wrong spot, but the apache web site dosen't > seem to help much with how things should be done, they only seem to give > reference for experiance users and I am far from a experienced user. I agree. The problem is, almost everyone struggles through the 'newbie' period somehow, and learns enough of the jargon that they forget how formidable the documentation can be to someone just starting out. A good way to help out, if you're interested, would be to write a howto, in simple terms, of the things you found difficult but solved, and put it online somewhere. There are many such projects out there, and perhaps you could coordinate your efforts with one of them. > Sorry if I sound upset, I am just frustrated spending all day on > something that takes 5 mintues on a windows server. > > -Debuser Once you have it figured out, it'll take a little less time than that on Debian 8^). HTH, Steve -- Be valiant, but not too venturous. Let thy attire be comely, but not costly. -- John Lyly
Attachment:
pgpahyxyI9M2z.pgp
Description: PGP signature