Hi!
I'm not sure if I do it correctly, but I can't get Xvnc to work at build 117.
When VNC session is opened and the gnome window is asking me for user and
password, the hole window turns into "white screen" after that I have logged in.
--
This message posted from opensolaris.org
__
Paul Theodoropoulos wrote:
thanks for the replies, gentlemen. yes, the 'outlier' issue is really the crux of it. while this isn't bad motherboard, neither is it enterprise-grade. i'm reasonably happy with the performance, so i really should just buy a spare of the mobo, and for the most part that
thanks for the replies, gentlemen. yes, the 'outlier' issue is really the crux
of it. while this isn't bad motherboard, neither is it enterprise-grade. i'm
reasonably happy with the performance, so i really should just buy a spare of
the mobo, and for the most part that covers me. sure - it's po
I've had bad RAM in some of my OpenSolaris boxes before and the bad RAM has
caused ZFS to detect "phantom disk errors" when I do zpool scrubbing (i.e. ZFS
detects that there's an error somewhere in the process of reading data from the
disk and checksumming it).
I recommend try testing the RAM w
YukonX for the win.
Been using it ever since I got rid of the broken skge driver I had before and
haven't had any problems since. Good job to whoever the engineer was who wrote
yukonx. Solaris is way ahead of the NIC device driver pack now considering all
the problems I've had with these Marvel
do i have to get ahold of an exactly identical mobo, or will osol tolerate a
mobo by a different manufacturer, but with the same chipset... or would it
refuse to even boot? should i just bear the pain of buying an identical spare
mobo, cpu, ram, psu, so that i'm ready should the worst happen?
Carl Mascott wrote:
You have probably found by now that rebooting makes the update notification go
away.
When you update 'entire' you create a new boot environment in which the update
gets installed, but there is no automatic switch to this new boot environment.
You have to reboot the machin
Paul Theodoropoulos wrote:
background: my vocation and avocation since 1994 has been unix systems administrator.
i've been running solaris on SPARC hardware all this time. my home server, which does
email, webhosting, etc for a bunch of friends and family, has until recently been a Netra
T1 10
You have probably found by now that rebooting makes the update notification go
away.
When you update 'entire' you create a new boot environment in which the update
gets installed, but there is no automatic switch to this new boot environment.
You have to reboot the machine and select the newly
Hi,
After exploring OSOL2010.02-b117 yesterday, I noticed a weird error in my
mouse clicks and scrolling while working with the gnome panels. This was
something that didn't happen in the previous releases. I figured this might
be one of the bugs in GNOME 2.26.1.
Well, I figured rather than wait
Filled a bug with the thing:
http://defect.opensolaris.org/bz/show_bug.cgi?id=9730
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Surprise for me.
I have the error too.
I have 2 pools on 1 disk, each on one partition.
Showing the error only on one of the pools.
The afected file is a VBox machine file I use every day without problems.
I my opinion it does't mean that the disk is defective, and error reading a
disk can hap
Hello:
I installed a new Seagate 1.5T hard drive and installed OpenSolaris2009.06.
Everything runs fine. But after I installed sun-cc development suite and gcc
and VirtualBox, I checked "zpool status," I was surprised to find out that
there were "permanent" errors "ZFS-8000-8A" in the file
rp
Tried twice today. Both times happened the same.
There are some messages and little space left (about 900m) during install.
(upgrading from 111b)
Other than that all goes well. Then when reboot, on console login
I can write in correct script (latin, what you are reading now),
wait until GUI login
14 matches
Mail list logo
