Responses interspersed below. At 05:39 PM 1/12/99 +0000, Paul Rogers wrote [with deletions]: >I'm trying to get the ISC dhcp server up and running on a Red Hat 5.1 >(2.0.36). >I've got it to run and dish out IP addresses. >I'd like to run the daemon on start up. Where would the command go? The usual place for user-added commands is /etc/rc.d/rc.local . This is a bit old fashioned; RH and some other distributions now use a newer rc-file system. But it will work, even on Red Hat. >I also have to issue the following to allow W95 clients to request IP >addresses. > route add -host 255.255.255.255 dev eth0 >Does this need to be issued every time the machine starts and is it >possible to automate this? Yes and yes. Put the line in the same place you put the dhcp daemon startup command. >Finally, I placed the tar file in /usr/src and unpacked it which it has >done to a subdirectoryin /usr/src. I notice that everything ie man >pages executables docs et al have all ended up in this directory. I've >already had to move the configuration files to /etc manually. >Should all the other files go in specific directories such as /sbin etc? >Is there some sort of convention for this? >Is it ok to do this manually? >Is it possible, in future, to get tar to do this automatically. Personally, I dislike the following practice, but it is pretty conventional. Many tarfiles are set up to install everything where it should go if the file is untar'd from the root directory (/). The new files simply overwrite anything that is in the way. This is how you "get tar to do this automatically." The downside is that if whoever made the tarfile did anything wrong (or conceivably something malicious, though anything really bad wouldn't last for long), your system can be nicked or even trashed. A better practice is to include an install script, either a shell script or a call to "make" that does all the installing, a bit more carefully. If done right, these scripts can account for variations among distributions and avoid putting things in the wrong place with a much higher success rate than the simple procedure above. But they are harder for the creator to set up. And if the tarfile doesn't do it this way, a preference for it doesn't help you much. So ... now actually to answer your questions. The other files should probably go where it looks like they should if you read the paths without the leading /usr/src . You can probably move them there safely by hand (though be cautious if you are moving anything to /lib or /usr/lib -- you don't want to overweite a shared library accidentally). If you are the trusting sort, untar'ing the file from / instead of from /usr/src will, in the future, locate things properly, if it is that sort of tarfile, and do something reasonable if it is the other kind I described. ------------------------------------"Never tell me the odds!"--- Ray Olszewski -- Han Solo 762 Garland Drive Palo Alto, CA 94303-3603 650.321.3561 voice 650.322.1209 fax [EMAIL PROTECTED] ----------------------------------------------------------------
