Teaching standard init config...
 

I'm having a problem. I'm planning for a college course in Apache web
server, and have opted to teach the standard way of compiling and
installing the software from source. The problem is to configure the
machine to start Apache at boot.

It seems one of the rules of creating your own Linux dist is to make
sure your init config doesn't look like anyone else's. It's not just a
matter of a layer of config tools on top of the standard files, etc.
The hierarchy of scripts is really different from Red Hat to Slackware
to Ubuntu.

So I'm at a loss. If I can't teach how to make Apache start at boot, I
can't really teach them how to compile and install from source. Since
the students choose whatever dist they like, I can't really teach
installing Apache at all. To me, that is an essential part of the
course.

I'm basically just looking for some feedback on this. Have you been
taught some standard way of dealing with rc scripts? Any great ideas in
general?

Thanks!

Re: Teaching standard init config...
 

I may be misinterpreting your post, but init scripts and compiling are two totally seperate, unrelated things. Configuring and compiling source code depends on the instructions included with the source code. Starting services at boot depends on the type of init a particular distro uses, which you have already discovered. The two basic types of init systems are System V and BSD. Read up on those and that may help you explain that to your students.

There is no standardization between distros - it is up to the particular distro developers which init system they use. Configuring and installing software is pretty standard across distros though.

Re: Re: Teaching standard init config...
 

Thanks for the response.

Well, they are not unrelated when the task is to install and configure a web site. I know what both are, it's just that teaching my students to configure, compile, and install the standard distribution, and not telling them how to set the box up so Apache starts at boot feels pointless. On the other hand, while I can teach the standard way of working with Apache, I can't teach a standard way of working with the init configuration on any Linux box (because there is none). That is my dilemma. Should I make it a half Apache For Linux course, or a full Apache For Ubuntu course? In fact, I don't really expect anyone here to solve this, I was just hoping for someone more creative and inspired than me. :)

EDIT:

I suspect this was the confusing sentence in my OP:
"If I can't teach how to make Apache start at boot, I
can't really teach them how to compile and install from source."
I failed to make clear that the alternative is to teach how to install using your local package manager, which will normally set up rc scripts for you. That would also mean it becomes an Apache For Dist-X course, which is not what I have in mind.

Re: Re: Re: Teaching standard init config...
 

I understand - you are looking at the task as a whole. Yes, the lack of init standardization is an issue, but perhaps you can simply tell them each distro has different ways of starting services, and they should look at their distro's documentation for an explaination on how to do this. You could explain how to install Apache from source, then show an example of how to start it on Ubuntu. Keep in mind Apache does not have to be installed from source, but I think you know that already. Are you doing this because installing from source is more standard than dealing with a specific distro's package management system?

Re: Re: Re: Re: Teaching standard init config...
 

Yes. Apparently my students mostly run Ubuntu, I run Slackware. But more importantly, I have worked with Apache for many years, and chances are very good that these kids will end up on a job in front of some unknown installation which doesn't just not run Ubuntu (a somewhat unlikely choice for a server anyway I think) but perhaps something they've never encountered before. So, I just want to make the course as complete and as meaningful as possible, and to me teaching them to use Ubuntu's package manager is not the best choice. Neither is not showing them how to start Apache at boot.

However, I just realized that maybe I can use KSysV, at least as an example and a model for how to show them the steps. I might still figure something out...

Re: Re: Re: Re: Re: Teaching standard init config...
 

I was just thinking (dangerous!) you could perhaps show the installation and configuration of Apache, and maybe seperate the init issue into another session? That creates a disconnect though, because you still have to teach them how to start the Apache server. I agree with Ubuntu not being your average server distro. When I think of Linux servers, I think of Redhat, Gentoo or BSD, even though BSD is not Linux. Good luck on your course, it sounds interesting, and I'm sure you will come up with a good solution.

I only have about 15x45 minutes in toto for the course, so will have to stay pretty focused.

Thanks for the feedback Sargek, it always helps!

Feedback
 

You are welcome! I am a "guest" lecturer at a local community college, and talk about Free/Open Source software vs. Proprietary software. I also end up talking about GNU/Linux, because that's the platform the majority of Free/Open Source software is built for. I always try to think about the lecture beforehand and see if I am putting it together in a way that makes sense, and is complete. Point here being, I understand your dilemma!