|
All, I discovered some strange behavior in solaris express build 160 for sparc. when initialing the install, it doesn't pick the right service. I see this on the console: Downloading install.conf --2011-03-18 21:15:43-- http://10.137.232.30:10101/sparc_160-sparc//install.conf Connecting to 10.137.232.30:10101... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text] Saving to: `/tmp/install.conf' [ <=> ] 79 --.-K/s in 0s 2011-03-18 21:15:43 (1.90 MB/s) - `/tmp/install.conf' saved [79] Cool ! and it contains: root@hazmat:/tmp# cat install.conf install_service=default install_svc_address=10.137.232.30:10101 livessh=enable Even better. But then the install fails, it seems that my manifests are no good. If I look, I see the manifests that are way old, they are even the ones from before build 150 (the opensolaris manifests). Digging a little deeper: root@hazmat:/tmp# cat service_list.1122 10.137.232.49:46503:saeosol-134a-x86 Wow, how did that get there ?? I don't think I ask the install.conf to do that did I ? We have some services on our network on a repo server, but we only use it as such, it's sometimes a install server if the conventional method fails... The install just "picks" the first available service it can find, seems even that it's in port number order. This is what it did: saeosol-134b-sparc (port 46502) After disabling this service... saeosol-134a-x86 (port 46503) And so on .... I really don't want to use the DNS multicast, I just want it to pick the "default": 10.137.232.30:10101:default As I told it to do in the "install.conf" Bug or feature ? Thanks Paul --
|
_______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
