Well, after some of the usual trial and error (mostly error) I have
made g4u do things it was not supposed to do, which have helped us do
remote installs. I am letting our to-be-installed machines come up
via dhcp and pxe boot a g4u with a modified .profile for root.
Instead of seeing the g4u menu, you ftp a file from some server and
run it.
My version grabs the mac addr from ifconfig (which a netowrk has it
because of dhcp)
and ftp's a file with the mac addr in the name. Then the file is sourced.
Inside the file I can then do a slurpdisk. After that I mount the
filesystem and can ftp for more files or do other configurations.
To make this more useful for system configuration, I'd like to add
mkdir to the ramdisk, since I'm not depending on the size of the image
fitting on a floppy.
I tried adding bin/mkdir to the file:
/usr/src/distrib/i386/ramdisks/ramdisk-g4u/list
but that complains about not being able to know how to make mkdir.
Can anyone help me understand the proper way to add this (and
extensibly other) functionality?
-ASC
--
"Yes, could I please have half an order of magnitude and a side of PI?"
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
g4u-help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/g4u-help
