|
While your goal is laudable, please don't dive into the deep end of the pool before you know how to swim.
I would **highly** suggest that, before you take on any paying clients, get *at least* a year of running your own server under your belt, perhaps more even. Ideally, you should get a job with a firm that is doing what you want to do. There you can apprentice under a seasoned administrator, who can help guide you through how things should be done.
I'm not trying to imply that it is impossible to learn these things on your own, but it is very time-consuming, and when you have paying clients, frequent data loss, outages, etc., are unacceptable. Your customers, even if they're not technologically savvy, will be able to tell you don't know what you're doing and will take their business elsewhere.
Moving on, giving out vpn, shell, etc. accounts is *very* risky, especially so if you don't know what the risks are, how to detect nefarious behavior, and how to properly deal with it. I've been watching over large linux server installations for over 12 years. By all accounts, I'm a seasoned linux greybeard, and even I am reticent to give out shell accounts on my machines. I know what is possible when one has a shell account, and I will not give out an account unless I *completely* trust that user. Same for VPN or proxy accounts - are you ready and willing to research the legalities of providing such a service? How much do you know about the DCMA?
I'm not trying to discourage you, but rather just give you a taste of the reality of professional systems administration. It's not rocket science, but there are a million and one ways to shoot yourself (or your customers) in the foot, and believe me, you *will* shoot yourself in the foot. Many times. Find someone to help you learn, so that you can minimize your foot shootings.
_________________ 
|