On Thu, 2 Aug 2007, Andrew Clapp wrote:
> nbmake: don't know how to make mkidr. Stop
^
Pilot error. :-)
- Hubert
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping throug
OK. Here goes. Error is at the bottom.
g4u-build failed with this first,
BUILD_FLAGS="${UPDATE_FLAGS} ${ALL_FLAGS}"
so just to make sure I tried this,
BUILD_FLAGS="${FROMSCRACH_FLAGS} ${ALL_FLAGS}"
and this pasted error is from the latter
I'm trying to wrap my head around the layout of
On Thu, 2 Aug 2007, Andrew Clapp wrote:
> 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.
That sounds ok. Can you paste the exact error with some (5-50) lines of
context?
- Hubert
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
Don't let those floppies go... I run the local network labs at my uni
and floppy is the only way to go when dealing with clusters composed by
aging hardware. I also use systemimager for systems only requiring
linux, but g4u is a heavenside when dealing with BSD/Solaris. Keep it up.
João.
-
