Fedora Core 3 (Linux) Installation: Services [DHCP]
Setting up Fedora Core 3 on the Soekris is relatively easy. Unfortunately, the defaults for the grub.conf make it impossible to use after it reboots for the first time. By default, grub.conf has a splash image set which apparently causes the boot process to hang. I was able to rectify the problem by booting the Soekris via NFS, mounting the fedora boot partition, modifying the /boot/grub/grub.conf file and simply comment out the offending line. That was all it took to fix it. But I still give this distro a BIG THUMBS DOWN for use with the Soekris for that reason alone.
But besides the problem with the grub.conf setting that prevents the box from rebooting, the distro is very bulky and even the ASCII/text based installer is slow to respond. Even if you trim down the installation options as much as possible (without doing individual package selection), it still uses 600MB. You could probably squeeze it down even more if you actually sit and wait 10 to 15 minutes while the installer loads the individual package list so you can trim out the fat, but with so many other distros available that are better suited for the Soekris, why bother?
Never the less, everyone is entitled to their own opinion, so I've gone ahead and documented the process in case someone is bent on running FC3 on their Soekris. And if anyone knows a way to edit the grub.conf file before the installer reboots itself, e-mail me and let me know. Otherwise I think this distro is a complete waste of time for use with the Soekris. NFS booting it just to edit that single file is a huge pain in the neck and most people aren't going to bother.
My notes here are an attempt to condense all the information I have obtained so that people have a simple, single source of information that applies specifically to the Soekris net4801.
You don't have to have an existing Fedora Core 3 installation to install FC3 on your Soekris. Any Linux, FreeBSD, or Solaris box should do just fine. (I imagine you could even use Mac OSX?) In this example, I will be installing FC3 onto my Soekris machine using Gentoo Linux as the host.
The first thing that happens when you boot your Soekris box from the network is that it will look for a DHCP server. That being the case, configuring the DHCP server is the first thing you should set up and get working.
If you don't already have a DHCP server running, you need to install it now. In this document, I am using Gentoo Linux as the host machine for installing FC3. With Gentoo, use emerge to install a DHCP server.
emerge dhcp
Once complete, edit the /etc/dhcp/dhcp.conf file. By default, this file will not exist after a new DHCP install using emerge. There is a /etc/dhcp/dhcp.conf.example file but most likely you can just use my information to setup your config file. Here is my config file.
allow booting;
allow bootp;
option domain-name "example.com";
option domain-name-servers 192.168.1.1 ;
option routers 192.168.1.1;
default-lease-time 600;
max-lease-time 7200;
ddns-update-style none;
log-facility local7;
subnet 192.168.1.0 netmask 255.255.255.0 {
}
host debbox {
hardware ethernet 00:00:00:00:00:00;
fixed-address 192.168.1.4;
next-server 192.168.1.2;
option root-path "/tftpboot";
filename "/soekpxe.0";
}
Obviously you will have to make the necessary MAC and IP address changes to match your particular setup. If you don't know the MAC address of your Eth0 network interface, read the comBIOS section of this document as it explains how to find it.
Make sure the IP address for the next-server directive is the IP address for your TFTP server. This directive is optional, however it is often needed even if your TFTP server is running on the same machine as your DHCP server. And I haven't ran into any problems having the next-server directive in place even it when it wasn't needed.
Now you should start the DHCP server.
/etc/init.d/dhcp start
If you want your dhcp daemon to run all the time, you should make it part of your boot process.
rc-update add dhcp default
This is worth repeating: running daemons (services) is a security risk. Every daemon running on your system is a potential "back door" into your system. I would advise against running the daemon full time unless you absolutely have to. However, if that is the case, I would recommend setting up some IP and port filtering rules to minimize access to the daemon.
STOP NOW: Before you continue with TFTP setup, you should make absolutely certain your DHCP server is working. Until your DHCP server is working properly, everything else is a complete waste of time.
文章整理：西部数码--专业提供域名注册、虚拟主机服务
http://www.west263.com
以上信息与文章正文是不可分割的一部分,如果您要转载本文章,请保留以上信息，谢谢!
