This message means that you should specify your device ID when
attaching the driver. Marvell device ID is something like "pci11ab," (
depends on your system). Find out device ID with prtconf and attach it.
# add_drv -i '"pci11ab,"' skge
Alternatively, someone else posted about this h
Hi,
"nightly -i ./opensolaris.sh" do the incremental build.
Also when I change a file, I run the command dmake all, but this only builds
the changed file.
Deepak
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Thomas De
Schampheleire
Sent: Tuesday, Februa
ok. I ended up doing a
yes | /usr/sbin/pkgrm SUNWsogm
\rm -rf /usr/share/nautilus/starthere-link.desktop
So thanks anyways I guess. :)
This message posted from opensolaris.org
___
opensolaris-help mailing list
opensolaris-help@opensolaris.org
My first description of this problem doesn't make any sense to me and
may also mislead others. Well, now I may know the reason.
If I use "shutdown -i 5 -y -g 0" to shutdown the computer, as I always
do, the "numlock" light will be "on" after power-off. So I guess it
means some parts of the compute
I had the exact same problem.
(I could never get the gld3 driver to work, although some others from this same
page have worked for me)
I finally got it working by doing the following:
went to this guy's page here: http://homepage2.nifty.com/mrym3/taiyodo/eng/
There you will find 2 potential d
Hi, Well, I gave the wrong link for the 32-bit driver in my previous post. The
driver in question is "skgesol_x64v8.19.1.3.tar.Z" from
http://www.syskonnect.de.
I was wrong in assuming that the driver installed properly, I repeated the
procedure and ended up with the message (at one point it pr
To answer my own question, I solved the second problem of my question
(See screen shot attached - 2.jpg).
The installation always stalled at exactly that same package set, which when I
dug
further down into the installation menus found was "JDK 6.0 64bit". My VM
was a 32 bit VM, which may be the
Thomas De Schampheleire wrote:
On http://opensolaris.org/os/community/on/devref_toc/devref_4/ I read that it
is possible to compile only parts of the kernel using make/dmake directly. This
would speed up compilation in test phases.
However, when I modify a file, for example uts/common/disp/dis
Hi, Jeremy,
Could you please tell me what to put in a cronjob? I mean the script.
Thanks.
Calvin
On Mon, 2007-02-19 at 20:58 +0800, Jeremy Teo wrote:
> > Something similar was proposed here before and IIRC someone even has a
> > working implementation. I don't know what happened to it.
>
> That
On http://opensolaris.org/os/community/on/devref_toc/devref_4/ I read that it
is possible to compile only parts of the kernel using make/dmake directly. This
would speed up compilation in test phases.
However, when I modify a file, for example uts/common/disp/disp.c, and then run
cd uts
dmake co
I'm trying to configure SMF to manage my Tomcat server and running into a
problem with specifiying multiple startup options. I need to pass Tomcat the
following startup parameters:
CATALINA_OPTS=-Xms256m -Xmx256m
JAVA_OPTS=-Dcom.sun.management.jmxremote
I've tried using svccfg and specifying t
No problems,
printer is working...
Martti
This message posted from opensolaris.org
___
opensolaris-help mailing list
opensolaris-help@opensolaris.org
SXCR have "Solaris-printmgr-wrapper and I can use it.
Nexenta have "gnome-cups-manager" and it is not so easy.
When I try install my Epson Stylus color 600 (parallel) so I don't know in step
2, must I find driver,
the select place "Install Driver..." and how can I find driver.
Martti
This me
Thanks kuhnkem,
here is end of the file netmasks.
Perhaps the last row is wrong.
---
# The term network-number refers to a number obtained from the Internet Network
# Information Center.
#
# Both the network-number and the netmasks are specified in
# "decimal dot" notation, e.g:
#
#
14 matches
Mail list logo
