Ok, I found it. It is just in the LiveMedia-framework - derived (originally by Moinak Ghosh, now AI-adopted) /lib/svc/method/live-fs-root SMF script after line 184 or after 253, according to grep. If it is a bug, I respond later with a solution. Maybe it was simply a user error by myself (during installadm create-service).
On Tue, Apr 28, 2009 at 12:56 PM, Martin Bochnig <martin at martux.org> wrote: > On Tue, Apr 28, 2009 at 12:24 PM, Martin Bochnig <martin at martux.org> wrote: >> Now I can look into the next issue, now of course everything should be >> way less dramatic, as the boot does work now. On all sun4u workstation >> models (except U1), which I all just tested. >> >> The next problem is simply, that the booted 111 AI image complains on >> all machines: >> >> "Couldn't determine automated install image. > > > Err, damn laptop keyboard and touchscreen, two words got missing. > I do not want to report incomplete error messages. > The precise error message is. > > "Couldn't determine source of automated install image > Requesting System Maintenance mode ..." > > > I guess this one is not difficult to fix (properly). > Also a workaround should be possible after I log in into System > Maintenance milestone. > Which command must I call? > > TIA. > > -- > %martin > > >> Requesting maintenance mode." >> It looks like wanboot may not provide enough parameters to the booted >> client install environment. >> >> Now I must check if I get the same on a Blade 100 with OBP 4.17.1 when >> I boot directly via OBP's wanboot, rather than off-media's >> /platform/sun4u/wanboot. >
