Well, theoretically, we may need to change the init order so that the server is able to pull a dynamic IP address before it tries to write the configuration files, though I'm not sure what order things should be in, and what side-effects that would have on the server.
I've used e-smith since 3.0, and I have to say it's come a long way, but it's always been good to me unless I try and make it do something that it wasn't intended to do. And since Comcast isn't using a standard DHCP system (after their switch from @Home), using e-smith to serve pages from the cable line is a little tricky.
But as the first rule of computer science says, nothing ever works right the first time.
If anyone has any suggestions as to a preferred order in this scenario, I'd love to hear it. I think my weekend will involve hours cuddled up with a good O'Rielly book or maybe staring at linuxdocs.org until I get this worked out.
