Project Proposal: Device Detection Tool
I propose a project on opensolaris.org for the creation of Device Detection
Tool. This tool is a handy tool to check devices against a database. It
provides a web-accessible method for Linux, Windows and Solaris users to
check their device driver availabili
James McPherson wrote On 03/11/06 12:18 PM,:
On 11/3/06, Hema Huchegowda <[EMAIL PROTECTED]> wrote:
Is there a way in mdb to specify the library path (similar to
pathmap in dbx) so I can open the application core on target
systems that doesn't have to be running at the same patch
level as th
> > Sorry, I don't have wiki to offer. But I hope you get
> > involved anyway.
>
> I'm confused - the OpenSolaris site is already a wiki right
> now? - only it has more restricted access rights than your
> typical wiki environment.
True. It does allow you to edit pages from within the browser.
That first link got me to a page with no information. The second had a little
more. I guess my feeling that this particular thing was not all that well
documented was correct. :-)
This message posted from opensolaris.org
___
opensolaris-discuss mail
The following documentation provides some information.
I'm searching for more, but this might help:
- "x86:Partitioning Recommendations" at
http://docs.sun.com/app/docs/doc/819-5778/6n7rbgt5e?q=partition&a=viewx86:
- Or, "partitioning Profile Keyword" at
http://docs.sun.com/app/docs/doc/819-5778
On 11/3/06, Hema Huchegowda <[EMAIL PROTECTED]> wrote:
Is there a way in mdb to specify the library path (similar to
pathmap in dbx) so I can open the application core on target
systems that doesn't have to be running at the same patch
level as the system where the application core dumped..
Hi
Is there a way in mdb to specify the library path (similar to pathmap in dbx)
so I can open the application core on target systems that doesn't have to be
running at the same patch level as the system where the application core
dumped..
This message posted from opensolaris.org
__
>> Things missing are:
>> - global setting of mount options
> ^
> This would make it unusable :-(
I'm not sure what this remark means? THat you require global mount
option setting or tat you cannot have global mount option setting?
Unusable would perhaps be somewh
I just wanted to drop a note to mention how the projects/repositories
are being listed, since it's not clear from the static HTML page you see
at http://src.opensolaris.org/source
If you go to the Cross Reference page:
http://src.opensolaris.org/source/xref/
You can see the listing here of con
I want to be able to install a flash archive via the DVD Installation method
for Solaris. It turns out that once I have recreated slice 0 containing my
flash archive, it exceeds the capacity of the original slice 0. I therefore
changed the approriate bytes within the VTOC. I compiled a iso image
Just on a guess, it's probably based on your IP address. If your IP block is
listed as being in the US, even if you aren't, it may well show you as being in
the US.
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opens
[EMAIL PROTECTED] wrote:
>
> >Does that mean it is going to work in Build 51? And does it substitute vold
> >by then?
>
>
> Yes, but not the complete replacement:
>
> - vold gone
> - dbus/hal/rmvolmgr take over
>
> Things missing are:
> - global setting of mount options
Hi,
The page: http://opensolaris.org/jive/online.jspa lists the users who are
currently logged in. It also lists the country of each user.
My country is apparently "United States".
But it's not, and the profile form doesn't even ask you for your country!
How do I change this?! Have I missed so
This project is currently in the works. A new release of b.o.o. will be
out next month, stay tuned for a long awaited release.
Thanks for your patience :)
Linda
Bob Palowoda wrote On 10/30/06 03:18,:
The subject about says it all. I remember some discussion about
resources being added b
On Wed, 1 Nov 2006, David Van Couvering wrote:
I would like to propose the formation of a new Open Solaris community
focused on databases within Solaris...
Excellent! +1
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Here is the October issue of the OpenSolaris Community Newsletter.
http://opensolaris.org/os/project/content/newsletter/oct06/
Feel free to send your contributions to [EMAIL PROTECTED]
-Linda
___
opensolaris-discuss mailing list
opensolaris-discuss@
Yo he usado hasta los momentos Nexenta, en mi laptop, una Toshiba Tecra A6, solo me dio problemas con la tarjeta de red.Hasta lo momentos, por lo visto en las diferentes distros, yo usaria Nexenta por la facilidad del repositorio de aplicaciones que se pueden instalara a traves del apt-get.De momen
> The former hasn't crystalized yet, the latter is
> going to be present,
> settable on a per-user basis when GNOME 2.16
> integrates.
And when is GNOME 2.16 scheduled (roughly) to integrate?
Furthermore, does anybody know when the battery/power management for laptops
will become available?
> Maybe. Perhaps I'm in the minority, but I think
> there's a lot more
> that can be wrung out of more conventional power
> management mechanisms
> before resorting to "magic packets" and the like.
Agreed. Just replacing conventional hard disk(s) inside of systems with solid
state disks, or ripp
> Sorry, I don't have wiki to offer. But I hope you get
> involved anyway.
I'm confused - the OpenSolaris site is already a wiki right now? - only it has
more restricted access rights than your typical wiki environment.
~mm
> Having the site in multiple language could change the
> dynamic of
宋林健 wrote:
I usually used the "killall xxx" command to kill the process named xxx. But the killall
in solaris is not able to support this function. It is troublesome to always check the xxx.pid and
use "kill pid_number". Is there any idea to solve the problem? Or how to use the killall
[signa
宋林健 wrote:
I usually used the "killall xxx" command to kill the process named xxx. But the killall
in solaris is not able to support this function. It is troublesome to always check the xxx.pid and
use "kill pid_number". Is there any idea to solve the problem? Or how to use the killall
[signa
宋林健 wrote:
I usually used the "killall xxx" command to kill the process named xxx. But the killall
in solaris is not able to support this function. It is troublesome to always check the xxx.pid and
use "kill pid_number". Is there any idea to solve the problem? Or how to use the killall
[signa
You can do a pkill process_name.
pgrep, pkill - find or signal processes by name and other attributesOn 11/2/06, 宋林健 <[EMAIL PROTECTED]
> wrote:I
usually used the "killall xxx" command to kill the process named xxx.
But the killall in solaris is not able to support this function. It is
trouble
I usually used the "killall xxx" command to kill the process named xxx. But the
killall in solaris is not able to support this function. It is troublesome to
always check the xxx.pid and use "kill pid_number". Is there any idea to solve
the problem? Or how to use the killall [signal] command.
25 matches
Mail list logo
