Brian Cameron wrote:
The JDS team is working to provide the CBE and the Sun patches needed to
build the desktop, so is it similarly straightforward for someone to
build the Xserver for Solaris? Does the Xserver team apply patches,
use nondefault build options, or otherwise modify the Xserver
On Tue, 2005-07-19 at 14:56 -0500, Eric Boutilier wrote:
So what I should have said is, Blastwave's GNOME build (set of custom
patches) is
the leading community-based build.
Agreed :)
Cheeri,
Calum.
--
CALUM BENSON, Usability Engineer Sun Microsystems Ireland
mailto:[EMAIL
Gavin Maltby [EMAIL PROTECTED] wrote:
On 07/14/05 20:11, Joerg Schilling wrote:
Every second free software packet comes with illegal Makefiles that only
work
usually because they depend on bugs in Sun Make or GNU make. Note that
OpenSolaris does not come with Sun Make, I use smake for
Paul Gress [EMAIL PROTECTED] wrote:
On my Solaris 10 GA, W2100z (Dual Opteron):
$ /opt/csw/bin/cdrecord -scanbus
Cdrecord-ProDVD-Clone 2.01b35 (i386-pc-solaris2.8) Copyright (C)
1995-2004 J�rg Schilling
Unlocked features: ProDVD Clone
Limited features:
This copy of cdrecord is licensed
Hi,
when trying to boot SchilliX on this notebook, I get:
panic: failed to boot kernel/unix
Now unfortunately we don't have all sources for multiboot
so I am unable to even find out how to set the variable
verbosemode to get better messages.
How may I set verbosemode to a value != 0 and when
On 7/20/05, Joerg Schilling [EMAIL PROTECTED] wrote:
How may I set verbosemode to a value != 0 and when will
we have full sources for multiboot?
I'm pretty sure verbosemode is activated by doing -v to the kernel...
Just like one does -kdv...
--
Shawn Walker, Software and Systems Analyst
Hi all,
===
Yesterday I spent a few hours at night thinking and talking with
friends about OpenSolaris and more specifically trying to answer the
question of Why I don't use OpenSolaris on my personal laptop?.
I started to think about it because yesterday I saw Chris Hanna - the
new
On Wed, 20 Jul 2005, Alvaro Lopez Ortega wrote:
In the meanwhile, I thought: «I'm sure he would prefer to type
apt-get install anjuta rather than spending all that time trying to
compile just a dependency of what he really wants to use».
A fine idea. Have you looked at Blastwave.org? Their
On Wed, 20 Jul 2005, David J. Orman wrote:
On Wed, Jul 20, 2005 at 10:37:21AM -0700, Rich Teer wrote:
Just out of curiosity, why do you say that (for Blastwave at least)?
I would assume due to the specific mentioning of the package
count/size, because blastwave has nowhere near the amount of
On Wed, 2005-07-20 at 13:45, Jasse Jansson wrote:
On Jul 20, 2005, at 10:26 PM, UNIX admin wrote:
1. you patch the source code if necessary
Is there a 'recommended' format for patches in the Solaris environment?
patches to what ?
If you are talking about Solaris the binary product then
On Tue, 19 Jul 2005, Glenn Lagasse wrote:
Now, if you packaged up your custom built software into Solaris
packages, your maintenance for 100+ machines goes down. You have a
build machine, that runs whatever version of Solaris that is running
on the rest of your machines, you build your
`pkg-get -i anjuta`
and that would have been the end of that.
and your sanity as well because it will duplicate many of packages already part
of /usr or /usr/sfw, under /opt/csw.
This message posted from opensolaris.org
___
opensolaris-discuss
On Jul 20, 2005, at 10:53 PM, Darren J Moffat wrote:
On Wed, 2005-07-20 at 13:45, Jasse Jansson wrote:
On Jul 20, 2005, at 10:26 PM, UNIX admin wrote:
1. you patch the source code if necessary
Is there a 'recommended' format for patches in the Solaris
environment?
patches to
Jasse Jansson wrote:
and to apply the patch:
patch -i patch_file file_to_be_patched
or is there some other tricks that I should be aware of?
I usually use gpatch (included in Solaris) instead of patch, because
patch follows some obscure standard that breaks in subtle ways on some
Sunil wrote:
`pkg-get -i anjuta`
and that would have been the end of that.
and your sanity as well because it will duplicate many of packages already part
of /usr or /usr/sfw, under /opt/csw.
Which is a bad thing why? (Please don't say space.)
On Wed, 2005-07-20 at 14:04, Chris Ricker wrote:
creating a mysql-4.1 pkg from scratch. Or what if you want the same
version that Sun shipped, but just need it compiled with different
options? That's trivial on Linux distros, not so trivial on Solaris
Thats what the SUNWmysqlS package is
Thanks, Takaaki. I think I'll include these links in the new user group
community we are opening up. I have one user group listed on the links
page, and I'll move that one over, too.
Jim
Takaaki Higuchi wrote:
Hi, Jim,
Could you add these links ?
NSUG(Nihon Sun User Group)
Dragan Cvetkovic wrote:
But, I still don't understand why the newest CSWsudo installs
something like 15 or 20 additional packages. Previous versions of
CSWsudo were much more reasonable in that sense. This is a bug in my
opinion.
http://www.blastwave.org/bugtrack/
Which is a bad thing why? (Please don't say space.)
if you can prove duplication is a good thing, I will be happy.
anyway, its bad because it:
1. wastes network bandwidth for downloading packages which are already
installed, working, used, tested.
2. wastes time re-installing the packages
Hi David -
I'm a tech writer at Sun. I'm going to review this information and get
back to you about adding this procedure to the docs.sun.com documentation.
Thanks,
Ginnie
David J. Orman wrote:
That feedback was excellent, that was extremely helpful. I'm sure it
would help a lot of other
On Jul 21, 2005, at 12:33 AM, Shawn Walker wrote:
On 7/20/05, Torrey McMahon [EMAIL PROTECTED] wrote:
and your sanity as well because it will duplicate many of
packages already part of /usr or /usr/sfw, under /opt/csw.
Which is a bad thing why? (Please don't say space.)
Ok, I'll
On 7/20/05, Jasse Jansson [EMAIL PROTECTED] wrote:
2) Some people have limits on their bandwidth usage, or even heaven
forbid have to pay for usage based on time or bandwidth. This means
duplicate software is not only wasteful, it's costly...
You just updated the old saying from
One of the core values of Solaris is that sharable things really
should be shared.
This begs the related questions of
What constraints does this place on the shared component, and
What do you do when the shared thing evolves
Sun has a proactive development methodology that looks
Without this ability to manage the evolution of
shared components,
it becomes extremely difficult to reuse them, because
asynchronous
development almost guarantees that a change to the
shared component
will break a consumer, and that multiple consumers
rarely depend on
the same version.
As BIll said, iowait as reported by mpstat et al is zero on Solaris 10; iowait
is only a useful metric on a uniprocessor machine, its value is not useful when
there is more than one processor in the system. Since it's been the center of
much confusion, it's been removed.
A better way would be
Interesting as I'm seeing this in the kde 3.4.1 from
m blastwave.
Multiple copies of different versions of libstdc++
compiled
into some of the daemon process. I wonder if this is
what is causing
it to crash.
if 'ldd' shows both .5 and .6 referenced, it will lead to trouble sooner than
Thats what the SUNWmysqlS package is for, it is
is there a rationale behind such names? I mean why not 'mysql', which is a nice
name given by the writer of the source of pkg? what is this company ticker
concept useful for?
This message posted from opensolaris.org
Sunil wrote:
Thats what the SUNWmysqlS package is for, it is
is there a rationale behind such names? I mean why not 'mysql', which is a nice
name given by the writer of the source of pkg? what is this company ticker
concept useful for?
They key thing is not to get two packages w/ the same
This is Tian Siyuan from OPG ERI.
I propose to set up a community specifically for users in China especially
those in Chinese universities. As China is a fastest growing market for Sun,
there should be a lot of opportunites for Sun in general and Opensolaris in
particular. We have OPG in ERI
On Wed, 2005-07-20 at 20:19, Sunil wrote:
Thats what the SUNWmysqlS package is for, it is
is there a rationale behind such names? I mean why not 'mysql', which is a
nice name
given by the writer of the source of pkg? what is this company ticker concept
useful for?
there is no central
Hi John,
On Wed, 2005-07-20 at 19:31, John Plocher wrote:
Without this ability to manage the evolution of shared components,
it becomes extremely difficult to reuse them, because asynchronous
development almost guarantees that a change to the shared component
will break a consumer, and that
--- Bob Palowoda [EMAIL PROTECTED] wrote:
On Wed, 2005-07-20 at 15:17, Torrey McMahon
wrote:
This is a real problem when multiple copies of
the
same interface
get dragged into a single processes.
Interesting as I'm seeing this in the kde 3.4.1
from blastwave.
Sunil wrote:
Sunil wrote:
Thats what the SUNWmysqlS package is for, it is
is there a rationale behind such names? I mean why
not 'mysql', which is a nice name given by the writer
of the source of pkg? what is this company ticker
concept useful for?
They key thing is not to get two
Sunil wrote:
I don't get it. you mean somebody actually wants to install SUNWmysql,
REDHmysql, IMYmysql, YOUmysql at the same time on the same box?
It's not uncommon to have multiple vendor versions of gcc, perl, named,
and many others installed on the same box. But besides that, seeing
Sunil wrote:
I don't get it. you mean somebody actually wants to install SUNWmysql,
REDHmysql, IMYmysql, YOUmysql at the same time on the same box?
Probably not, but not all package names are unique, especially
when the system was started and SVR4 package names were limited
to 9 characters,
On 7/20/05, Bart Smaalders [EMAIL PROTECTED] wrote:
They key thing is not to get two packages w/ the same name... and
using the ticker symbol of the originating company helps prevent that.
It's just a way of partitioning the name space that lines up well w/
organizational boundaries...
Is
Anyone interested in getting winex from tansgaming and helping me do a port?
Shouldn't be too divergent.
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
You might want (made up names for example) VRTSvm and
EMCvm
installed if you used both Veritas Volume Manager and
VMWare.
two disparate packages ending up with same two letter short name is not a good
logic to prefix names with stock ticker symbols.
now that 8 character limit is not there,
Sunil wrote:
now that 8 character limit is not there, what stops us from having some
meaningful unique names for packages, which are really unique across csw/sunw,
so in future I install just one copy of a package and csw doesn't go around
downloading and installing it but just checks if it
Dan Mick wrote:
and for the record, /dev/xsvc is coming. I'm working on it personally now.
BTW, examining the source for aperture, it looks very much like programs
designed to use /dev/xsvc (like the afore-argued-about iasl) would work
fine if /dev/xsvc were a link to /dev/fbs/aperture.
I
Sunil wrote:
now that 8 character limit is not there, what stops us from having some
meaningful unique names for packages, which are really unique across csw/sunw,
so in future I install just one copy of a package and csw doesn't go around
downloading and installing it but just checks if it
41 matches
Mail list logo
