To install Apache by using Mandrake RPMs, you will have to find the rpm and use a command like (check syntax, I don't use rpms):
rpm --install httpd_blah.rpm blah will probably be replaced by the version.
Here are instructions by source. The version is WAY behind now:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apache 2.0.43 installation:
You will need to unzip and untar the downloaded file (httpd-2.0.43.tar.gz in this case) into a temporary area with enough space (50mB recommended). Download
the latest version of Apache (1.3 or 2.0) from
http://httpd.apache.org.
Current latest versions (20.12.2002):
1.3.27
2.0.43
$
cd /tmp
$
gunzip httpd-2.0.43.tar.gz
$
tar -xvf httpd-2.0.43.tar
$
cd httpd-2.0.43
For this installation we will be configuring apache to install in the /web directory. No other non-default configurations will be made at this time in this
example. Information on further configuration will be provided in another how-to (will place link here when done).
$
./configure --prefix="/web"
checking for chosen layout...
. . . bunch of configure options and tests
include/ap_config_auto.hconfig.status: executing default commands
$
PATH="$PATH:/usr/ccs/bin"$ export PATH
We need both make and gmake in the $PATH, not sure why at this time
$
gmake
Making all in srclibgmake[1]:
Entering directory `/tmp/httpd-2.0.43/srclib'
Making all in aprgmake[2]:
. . . More make information
socket -lnsl -lresolv -ldlgmake[1]:
Leaving directory `/tmp/httpd-2.0.43'
$
su -
We need to be root to install the software.
Password:
Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001 # gmake install We will need to have our $PATH set very similar to the previous $PATH
#
gmake install
Making install in srclibgmake[1]:
Entering directory `/tmp/httpd-2.0.43/srclib'
. . .more make install stuff
/web/manualInstalling build system filesgmake[1]:
Leaving directory `/tmp/httpd-2.0.43'
#
cd /web
#
ls -l
total 56
drwxr-xr-x 2 root other 512 Dec 19 10:11 bin
drwxr-xr-x 2 root other 512 Dec 19 10:11 build
drwxr-xr-x 2 root other 512 Dec 19 10:11 cgi-bin
drwxr-xr-x 2 root other 512 Dec 19 10:11 conf
drwxr-xr-x 3 root other 1024 Dec 19 10:11 error
drwxr-xr-x 2 root other 1024 Dec 19 10:11 htdocs
drwxr-xr-x 3 root other 3584 Dec 19 10:11 icons
drwxr-xr-x 2 root other 2560 Dec 19 10:11 include
drwxr-xr-x 2 root other 512 Dec 19 10:10 lib
drwxr-xr-x 2 root other 512 Dec 19 10:11 logs
drwx------ 2 root root 8192 Dec 18 09:37 lost+found
drwxr-xr-x 4 root other 512 Dec 19 10:11 man
drwxr-xr-x 14 root other 3072 Dec 19 10:11 manual
drwxr-xr-x 2 root other 512 Dec 19 10:11 modules
Everything is now installed into /web.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Cleaning up dhcpd docs, but here it is so far. This doesn't cover MANY of the options, and probably doesn't cover all of the options you will need/want. I'm going to try and add more information, but I don't have any way to test anything I type here.
😉 But the
man pages are quite good:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
dhcpd.conf example:
shared-network netboot-network {
option domain-name "netboot-network";
option domain-name-servers 192.168.131.1;
allow bootp;
deny unknown-clients;
subnet 192.168.131.0 netmask 255.255.255.0 {
option routers 192.168.131.1;
host client.netboot-network{
hardware ethernet 8:0:20:1b:1:e3;
fixed-address 192.168.131.10;
allow booting;
}
}
}
Ok, to try and explain each option:
shared-network netboot-network { This is basically a quick description of the stuff that follows. You can see in my example that this is a netboot network.
option domain-name "netboot-network"; This is the domain that the clients use. ie. example.com
option domain-name-servers 192.168.131.1; This is the DNS server the clients will be configured to use.
allow bootp; This is required for netboot networks utilizing bootp, don't use this option if you do not need it.
deny unknown-clients; This will not allow you to just put a new machine on the network and have it work, some manual configuration will be necessary.
subnet 192.168.131.0 netmask 255.255.255.0 { This declares the subnet that will be utilizing this part of the configuration.
option routers 192.168.131.1; This configures the default route (gateway) for the clients.
host client.netboot-network{ This sets the name for the particular machine being configured by dhcpd.
hardware ethernet 8:0:20:1b:1:e3; This identifies that particular client.
fixed-address 192.168.131.10; This gives the client an ip address.
allow booting; I believe this again allows the netboot stuff to work. You probably won't need this.
😉
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BIND is a little too big for me to be able to do something tonight. Plus, I haven't tried v9. Last version I used was v4.
😛
Please post questions, as they can improve any documentation I play around with.
😉