Quote:
I'm teaching basic system administration. I have a fairly complete course program here: http://www.microlinux.fr/download/fo...istrateurs.pdf Desktops and workstations are explicitly for professionals, e. g. users who consider their computer as a tool to get work done, and not as an extended game console. Before installing a machine or a whole network, I always establish a list of tasks and related apps with the client. And then we both stick to that. I can't say anything about Windows. Last time I used this OS for work was just before I replaced it by Slackware 7.1, around 2001. As for vertical software, I'm slowly but steadily expanding my set of supported professional applications: geophysical software (ProMAX/SeisSpace), school management software (GEPI), public library management (PMB), SMB accounting (Dolibarr), etc. Cheers, Niki |
Quote:
|
I've installed a number of Slacware servers at various small to medium-sized businesses. They all pefform fairly specialized functions:
Most of these Slackware installations are "PAMified". I've created scripts that download, compile and create PAM packages, as well as modified Shadow, OpenSSH and Samba packages with PAM support. That way, I can delegate certain tasks to local admins using sudo and accounts in Active Directory. None of these systems are in any way updated automatically, for the simple reason that one would need to read the changelog and/or the security advisory before applying an update. For instance, upgrading Perl on a mail relay running a SpamAssasin sendmail milter would at the very least require a backout strategy. Well, OK, there's one exception: I do run sa-update as a cron job. |
What's missing?
-Advertising-
A website section dedicated to Slackware in the Enterprise along with testimonials would be a good way to advertise. I'd take some of the one's listed here and put them on the Slackware website. -Cooking Recipes- Impatience is the worst sin in the information technology world. Maybe the addition of some Cookbook articles to SlackDocs website would help. The information is basically out there on the web for things like LAMP stacks and Email. "IT'S A COOKBOOK!" "TO SERVE SLACK" |
Quote:
Here's a link to the first edition, based on CentOS 5.x: http://tinyurl.com/no254g The second edition will be based on Slackware 14.1. |
Quote:
Quote:
Linux with onions: Does that mean Linux is like ogres, which are like onions --- they have layers? :) Actually I envy your entire business. I would enjoy spending a few weeks interning with you. Not to mention enjoying the wonderful weather of southern France this time of year. :) |
Quote:
|
Quote:
PAM is amazingly flexible, and installing PAM on a Slackware system breaks absolutely nothing. In fact, by itself it does nothing, since none of the system components use PAM anyway, which is why I also recompile the Shadow and OpenSSH packages and patch a few configuration files. I mostly combine PAM and Samba4 (or Samba3 + Heimdal on older systems), which makes it possible to authenticate against AD. User profiles are created on the fly by the pam_winbind module. PAM also has modules for LDAP and RADIUS authentication, which come in handy if the system is to be used as a VPN concentrator. I know that in the past, PAM had a significant number of security issues. There were good reasons for not including it in Slackware then, but I don't think that has been true for quite some time. (Not that it really matters all that much whether it's included in Slackware or not, as it can be added quite easily if needed.) |
Quote:
|
Quote:
Oh, and Active Directory does not necessarily imply Windows. You can implement an entire AD infrastructure using nothing but Samba. |
Thank you for the explanations. :)
Would you say that PAM is not critical in small localized networks? |
Ha ha ha ha
1 Attachment(s)
Relax Mr. Slacker
|
1 Attachment(s)
|
Quote:
If you only have a single server then sure, PAM isn't going to do much for you. The second you have users accessing services on multiple servers, and you need authentication and authorization to work across those systems, AND the service daemons can't handle this issue themselves (Samba is an example of a system that does), you're probably going to benefit tremendously from having PAM around. |
Quote:
|
All times are GMT -5. The time now is 07:09 PM. |