WAN Boot questsions

[Bernd.Schemmer]

Hi,

we're just testing WAN Boot with Solaris 9 and 10 and in the official
documentation (man page, docs.sun.com) I can not find the answer of the
following questsions:

1. Doing a WAN Boot from CDROM I can not explicitly specify the LAN
interface to use.
I assume from our tests that in this case WAN Boot always uses the LAN
interface at which the devalias net points to. Is this assumption correct?

2. WAN Boot only copies the "official" files from the profile directory
on the installation server to the local profile directory on the machine
to install.

In our environment we have additional files in the profile directory
that are necessary for our installation scripts.
At this time I copy them in the begin_script to the profile directory of
the client but I wonder if there is a better method to do this?

2a. Can i use geziped tar files for the profile while doing WAN Boot?
I did not find a working solution for this

3. If I use WAN Boot from CDROM and the network interface information
used is invalid (e.g. the router IP is wrong) it takes a very logng time
until the WAN Boot interpreter detects the error and fail back to the
prompt.

Is there a method other than sending a break available to stop the WAN
Boot? Or can I tune the timeout used by the WAN Boot program?

4. Is there any good WAN Boot documentation available other than the man
page and docs.sun.com

And, last

5. It seems to me that man page of the boot command does not contain
all possible values for the parameter of this command. Am I right? And,
if yes, where can I find a complete documentation of the parameter for
the boot command (SPARC and x86)

regards

Bernd

--
Bernd Schemmer http://home.arcor.de/bnsmb/index.html

[Darren Dunham]

Bernd.Schemmer <bn...@online.de> wrote:

> 5. It seems to me that man page of the boot command does not contain
> all possible values for the parameter of this command. Am I right? And,
> if yes, where can I find a complete documentation of the parameter for
> the boot command (SPARC and x86)

Is there something in particular you're thinking of?

In general you can add things to the 'boot' command and it passes them
down. The program that's run (ufsboot/inetboot/wanboot) then parses and
removes some parameters relevant to it. It probably then passes any
arguments it doesn't understand to the next program (unix kernel).

So for instance kernel options (like -s and -m ) are discussed on the
kernel man page, not the boot man page. But you enter them on the boot
line.

Is that what you're thinking of, or did you have something else in mind?

--
Darren Dunham ddu...@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >

[Bernd.Schemmer]

Darren Dunham wrote:
>
> Is there something in particular you're thinking of?

A complete list of parameter for reference.

> In general you can add things to the 'boot' command and it passes them
> down. The program that's run (ufsboot/inetboot/wanboot) then parses and
> removes some parameters relevant to it. It probably then passes any
> arguments it doesn't understand to the next program (unix kernel).
>
> So for instance kernel options (like -s and -m ) are discussed on the
> kernel man page, not the boot man page. But you enter them on the boot
> line.
>
> Is that what you're thinking of, or did you have something else in mind?

Yes, that make sense; I'll read the man pages for ufsboot, inetboot, etc
and put it all together

Thanks