I've just been trying out the new Linux bootdisk with Unattended 4.0b, and
it rocks longer and harder than ever.

My one problem at the moment is trying to make it even more unattended.  I
know I can put the relevant options on the kernel boot command line, but I'd
*love* it if unattended could get the z_path from a DHCP server.  I'm pretty
sure I know to do it, too - or, at least, one part of it.

>From the manpage, it appears that udhcpc will pass the value of the option
'root-path' to the DHCP client script (/etc/udhcpc-script in Unattended) as
$rootpath.  Unfortunately, from my testing I don't think that udhcpc
requests the root-path option, and I've not managed to work out how to tell
udhcpc to ask for it, and dhcpd2 doesn't send it out by default and I can't
work out how to force it to do so.  ARSE!  There's another DHCP client,
dhclient, which I know exactly how to make it ask for root-path, and since
we're creating a CD image anyway I don't think the extra size would be a
problem.  If we can't get udhcpc to do the right thing, switching to
dhclient could be an option.

However, if we can make udhcpc request the root-path option (or force the
DHCP server to send it no matter what), these mods should work to autodetect
the root-path option and make it the default for Z_PATH rather than
//ntinstall/install:

Add the following to /etc/udhcpc-script just after the other echo
statements: 

if [ -n "$rootpath" ]; then
        echo "rootpath=\"$rootpath\"" > $dhcp_out.tmp
fi

Then add these bits to /etc/master:

(after we've gone through the lease getting procedure):

if [ -f /var/run/dhcp.out ]; then
        . /var/run/dhcp.out
fi

(replace Z_PATH=//ntinstall/install with):

if [ -n "$rootpath" ]; then
        Z_PATH="$rootpath"
else
        Z_PATH=//ntinstall/install
fi

(Please excuse the dodgy "patch" format, but I'm hacking on this on another
machine in the ramdisk because I haven't gotten around to setting up a
bootdisk foundry yet).

And that should be all that's needed.  Now, if the defaults don't work for
you, you can still manually edit, which is probably the best thing to do for
usernames and passwords - if you stick those in a DHCP option, you may as
well just make the share guest OK and be done with it.

- Matt

-- 
For once, Microsoft wasn't exaggerating when they named it the "Jet Engine"
-- your data's the seagull.
                -- Chris Adams


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
unattended-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-devel

Reply via email to