>is 'Nevada' likely a more-functional, or at least better-behaved, > option for me?
OpenSolaris has a package management system kind of Ubuntu & Debian have . It has an analog of Synaptic Manager (ubuntu). As far as i know Nevada doesn't have such features in meantime. However, i was always under impression that Solaris 11 is supposed to be developed via Nevada Builds. All the efforts to build Xen 3.3.2 (3.4) Dom0 on Solaris Nevada clearly demonstrate mentioned intend. If i am wrong about that, please, correct me. Boris. --- On Wed, 6/3/09, PGNet Dev <[email protected]> wrote: From: PGNet Dev <[email protected]> Subject: Re: [xen-discuss] runtime panic (vfs_mountroot: cannot mount root) launching 2009.06 DomU on Linux Dom0 To: "John Levon" <[email protected]> Cc: "Boris Derzhavets" <[email protected]>, [email protected] Date: Wednesday, June 3, 2009, 1:30 PM On Wed, Jun 3, 2009 at 10:21 AM, John Levon <[email protected]> wrote: > On Wed, Jun 03, 2009 at 09:48:01AM -0700, PGNet Dev wrote: > I'm confused where you got that message. in part, "I believe OS 2009.06 DomU by default does DHCP request at startup. If it fails you get a problem." > The message is simply that you > have to use the work-around you already are. It's unpleasant but it does > work... as detailed in my prior posts, it's not (yet) working here ... admitting i'm 'new' to this, this install is cumbersome, at best. tbh, a far cry from the "it works" messages from speakers & product_mgmt received at JavaOne "-/ > BTW, if static config is very important for you, you should file an RFE > on defect.opensolaris.org asking for installer and post-install static > config support in OpenSolaris i suppose i'll have to do that, but frankly a bit surprised that that would not have been considered already -- static-ip deployments, of servers in particular, are not particularly uncommon ... > I would try install via DHCP. likely doable ... but, again, DHCP is not going to be an option here at all (eventually) ... > They should have a kind of Network Manager. Network Magic or something > like that. It should be possible to disable this NM. iiuc, i believe that'd be, pfexec svcadm disable network/physical:nwam && \ pfexec svcadm enable network/physical:default pfexec ifconfig xnf0 down pfexec ifconfig xnf0 192.168.1.102 netmask 255.255.255.0 mtu 1492 pfexec ifconfig xnf0 up pfexec route add default 192.168.1.102 which i can/do @ installer time to use static IP assignements. i just can't seem to get them to 'stick' or 'be happy' after reboot and xen, run-time launch. > It's not a problem for Solaris Nevada. Installer it self suggested static IP > configuration. The last build i tried was 106. @ JavaOne i was repeatedly told that SXCE (that's 'Nevada', yes?) is "going away soon" and that I should be using opensolaris _now_. given these experiences, i'm not sure that's the wisest choice, particularly for a server deployment in a static-ip env. given your coment, Boris, and reading, http://whacked.net/2005/06/21/confused-so-was-i/ is 'Nevada' likely a more-functional, or at least better-behaved, option for me?
_______________________________________________ xen-discuss mailing list [email protected]
