> This is interesting since they exist on my install. Did you install all of
> the needed opts when you loaded? The only things I had to do on mine was to
> go in and manually add in or edit stuff to make the thing work the way I
> needed it to.
One post already stated this, but I would like to elaborate if I could..
Check out /usr/doc/lilo* and read the lilo documentation if your
interested in knowing how your machine boots up. Essentially - it boots
the kernel, mounts the root device, then executes /sbin/init. That is why
when you do a process list, you'll always see init as the first process -
because it is the mother process.
When init loads it looks for /etc/inittab and runs through that file.
You may have some entries in /etc/inittab that look like:
# Default runlevel.
# System initialization (runs when system boots).
# Runlevel 0 halts the system.
this tells init what runlevel to associate for each state, and which file
to execute when that runlevel starts. As you can see from the example
below, the system initialization state runs the /etc/rc.d/rc.S file. it is
*IMPORTANT* to note that it doesn't have to be /etc/rc.d/rc.S .. it could
be /foobar/foo/foo/foo/startmeup or something :-)
Check out your /etc/inittab and determine what the system initialization
script is. Then locate that script, edit it, and take a look see at it.
If you're not too familiar with shell scripts you may not understand much
- but basically the script starts up daemons - loads modules, starts
network interfaces, etc etc.. the system init script in slackware (for
purpose of simplicity), calls a separate script for each related group of
functions to perform.
On a Redhat system they've got a lot of automatic customization to worry
about. You know, they have an X app or a console app that customizes how
your system boots up - I'm assuming that is why their rc.d files are so
different - mind you i've seen SCO rc.d structures like that as well. But
again, no matter *WHICH* distro you are on, if you check out inittab and
follow through the scripts, you'll understand how it all works.
Now as far as the intranet scripts... An intranet is simply a lan that
uses TCP/IP services. So if you are hooking up a bunch of Linux boxes or
Win95 / Linux boxes - of course you're going to be using TCP/IP -
otherwise it'd be a waste to have the Linux box there... So the term
'intranet' really is trivial for Linux networking.. In simple
'networking' terms - you setup an interface with an IP address, adjust the
routing tables - and voila! away you go.
PS- Of course my explanations are sugar-coated but you can go infinately