I am hoping I can find a way to pass non-standard custom text options to some PC-104 systems that I am doing ARM development on.
I was editing an LTSP initrd.img file last week and found that I could set custom non-standard text messages to be used as boot arguments. I think the initrd.img is not using a full blown dhclient but some how the kernel boots with the right arguments. I just could not find how the values where getting into the initrd script. I was hoping there was a /proc file I could just cat. On Wed, Oct 8, 2008 at 11:53 AM, Gustin Johnson <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Royce Souther wrote: > > My DHCP server gives options for LTSP terminals about what server on the > > network is the root server. LTSP terminals some how are able to read > > this info at boot time. I would like to find a way to read that > > information after a system has booted. The info is global in the DHCP > > settings so ever system gets it. Is there any way I can cat some file in > > proc to find it? > > > I am not sure if this information is stored after the fact (other than > in places like the routing table, /etc/resolv.conf etc.). On my system > I have dhclient overwrite and insert data that it receives from the dhcp > server. > > To see what is actually being sent, I would use tcpdump to pull the data > off the wire. Of course, I am always looking for excuses to pull out > tcpdump, so there is probable a more elegant solution out there. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFI7POKwRXgH3rKGfMRAkKnAJ424vXe+Zx71/VZPjFxJcntY9pGIACeJWLK > TTOuiRD7VVJJvltZAADQHyA= > =EL2c > -----END PGP SIGNATURE----- > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying > -- http://www.Radados.org
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying

