That sounds like a real winner. I started playing with udhcpd last night and found that the scripting is pretty straightforward. One question I have, after combining the scripts (cut & paste), it occurred to me that you shouldn't really need the script files, but rather a configure file that can be user modified, and have the inittab actually run the program based on the conf file. Anyway .. I made a little progress last night, but not a whole lot. I'll let you know more this evening...
The other question I am still working on is this damn serial terminal problem. I am still able to get the echo out, and the login says (so on and so on) ttyS0, so I know that it is at least allowing a login from the terminal, but I still cannot transmit data. This is really starting to bother me... Joey -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of guitarlynn Sent: Thursday, February 14, 2002 11:29 PM To: Joey Officer Cc: [EMAIL PROTECTED] Subject: Re: [Leaf-user] 1680K Dachstein-IPSec floppy Ok, I did a little more stripping of the system and came up with a image with dhclient, dhcpd, and 37K blocks of free room to actually configure it on a 1680K disk. This image should now fully replace the other two images I made using the same space. Here is the image: http://leaf.sourceforge.net/devel/guitarlynn/images \ /dachstein-v1.0.2-ipsec-full-1680.bin To get modules that aren't on the disk, get them here: http://lrp.steinkuehler.net/files/kernels/Dachstein-small/modules/ The big loser this time was local.lrp (which isn't used on the floppy anyway) and all NIC modules except pci-scan, tulip, and 3c509. Aside from the stripped modules, everything should be fully functional. The tulip module happens to be one of the larger (and most used) modules, so many people will have to load the modules they need and get rid of the ones they don't that exist on the disk. I have left the most commonly used ip_masq modules on the disk, so the same space requirements apply for these modules as well. I did this for a safe default space figure, for instance you can pretty much load the entire "8390.o" modules (8390, ne.0, ne2k-pci, etc...) in the same space as the tulip module alone. You'll have to gauge for yourself if real audio, ICQ, and serial.o are possible with this image. I'm also looking at implementing udhcp as Charles thought it might make a sizable replacement for dhclient and dhcpd. It appears that 50-60k might be gained if it works acceptably. This extra space would make it possible to make a custom ppp/pppoe image, which will not be possible IMHO on a 1680-ipsec image at this time. We'll see how it goes .... I hope this pretty much fits the bill for this experiment, for now! Enjoy! -- ~Lynn Avants aka Guitarlynn guitarlynn at users.sourceforge.net http://leaf.sourceforge.net If linux isn't the answer, you've probably got the wrong question! _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user