On 10/7/05, Ché Kristo <[EMAIL PROTECTED]> wrote:
> "Build 23 does not configure network by default", what do you mean ...
I'm running build 22 here and it is sweet :
http://www.blastware.org/images/blastwave/articles/BLS-0039/kde342_snapshot3.jpg
I don't really know what the problem is with build 23 but somehow I
_highly_ doubt we went from "networking working fine" to "does not
configure by default" in one rev.
This is what happens when anyone has to jump from one OS to another.
It doesn't matter if its Linux to Solaris or Windows 2004 to MAC OS X.
There will always be a learning curve in there for something. I
recently had to install Red Hat 9 ( why? go ask the guys at VMware why
) and was really non-thrilled when the eth0 interface was not
configured "by magic". For some silly reason I had to use ifconfig
after the install process was over to get that interface to enable and
come up after boot. After talking with James Dickens ( he rocks by
the way .. see his blog at uadmin.blogspot.com ) he told me about some
silly file in /etc/network-poo-config/eth0-up or some similar
nonesense that needed to be tweaked.
It was an OS leap. Nothing more.
I will tell you that when I tried to format a floppy disk with a
VMware based Windows NT client on Red Hat 9 it fried the whole
machine. Literally. Everything came to a grinding halt and then the
system went down to the bios and rebooted. This is the sort of thing
that some Windows people and Linux people live with I guess. I have
never seen it in the Solaris world ( not true .. back in 96 with Sol
2.5.1 on x86 with Compaq Proliant 6000 and SMART Array controllers and
... some other time ) and would have expect some protection from the
kernel. This is why I prey and wait for the day when VMware
Workstation is released on Solaris 10. Imagine, VMware in a Zone ?
Talk about virtualization maximus rex!
Dennis
_______________________________________________
opensolaris-discuss mailing list
[email protected]
