Rodney | 2 Feb 2010 20:29
Picon

Re: rpcbind isn't starting - a solution

Thanks - forgot about that one!
--

-- 
This message posted from opensolaris.org
mallikarjun | 3 Feb 2010 11:42
Picon

how to make gcc-3.4.6 version workable in cross compilation?

hi experts,

 i need to install gcc-3.4.6 version in solaris 10 x86 machine, which can be useful for cross compilation.
Means gcc-3.4.6 should work for sparc and intel architecture in solaris 10 machine. 
  Any idea . If you provide solution , it is a great help for me.
  Thanks in advance.
--

-- 
This message posted from opensolaris.org
epiq | 3 Feb 2010 14:57
Picon

lm_sensors ??

Hello!
Tell me anybody,which is best way to monitor hardware environment in opensolaris - temperature, SMART and
other parameters?
I'am running this system:
epiq <at> tagra:~# uname -a
SunOS tagra 5.11 snv_130 i86pc i386 i86pc
epiq <at> tagra:~# isainfo -v
32-bit i386 applications
ahf sse fxsr amd_3dnowx amd_3dnow amd_mmx mmx cmov sep cx8 tsc fpu
epiq <at> tagra:~# isalist -v
pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86
epiq <at> tagra:~# psrinfo -pv
The physical processor has 1 virtual processor (0)
x86 (AuthenticAMD 6A0 family 6 model 10 step 0 clock 1100 MHz)
AMD Athlon(tm)

ipmitool - doesn't work =\

epiq <at> tagra:~# ipmitool sensor list
Could not open bmc device: No such file or directory
Get Device ID command failed
Unable to open SDR for reading
--

-- 
This message posted from opensolaris.org
Eric Cartner | 3 Feb 2010 17:22

Re: lm_sensors ??

Ran into this problem the other day. In case you haven't found it, this ipmitool doesn't work because of Bug
ID 6799081: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6799081

There are a couple workarounds listed with the info for 6799081.
--

-- 
This message posted from opensolaris.org
Hejun Xu | 4 Feb 2010 05:29
Picon

Can't restore data to netapp filer with ndmp

Dear all,

I have some NetApp filer, FAS 3140 and 2020.
I have setup one opensolaris box and enable the ndmp service on it.
I can backup and restore data on it successfully with NetBackup 5.0MP5.
But when I tried restore data to my NetApp FAS 3140, it's failure.
The warning is "
cannot restore from filepath /export/home/hjxu, NDMP_HALT_INTERNAL_ERROR occurred
2010-2-4 11:23:27 - end reading"

Please give me some suggestion.

Thanks

-Hejun
--

-- 
This message posted from opensolaris.org
Andre Lue | 4 Feb 2010 06:33
Picon
Favicon

IPS and dependency editing question/help?

After running 
pkg image-create -F -a opensolaris.org=http://pkg.opensolaris.org/dev /ips/

I end up with what I'm guessing is the minimal package list in /var/pkg/pkg (list below). If I start by adding
SUNWcakr, the entire package list below seems to be the base dependency so it will first add all packages
below. Is there anything I can edit before the pkg install of SUNWcakr to change the dependency below? For
example I do not wish to add SUNWfretype2 or SUNWfontconfig, can I edit something before starting the pkg
install to change this dependency?

SUNWPython/                                         SUNWpool/
SUNWPython26/                                       SUNWpr/
SUNWTcl/                                            SUNWsmapi/
SUNWTk/                                             SUNWsqlite3/
SUNWaudd/                                           SUNWtecla/
SUNWbzip/                                           SUNWtls/
SUNWcakr/                                           SUNWtss/
SUNWcar/                                            SUNWusb/
SUNWckr/                                            SUNWusbs/
SUNWcs/                                             SUNWuwb/
SUNWcsl/                                            SUNWwbsup/
SUNWfontconfig/                                     SUNWwsr2/
SUNWfreetype2/                                      SUNWxorg-clientlibs/
SUNWgnu-readline/                                   SUNWxwfsw/
SUNWgrub/                                           SUNWxwice/
SUNWgss/                                            SUNWxwplt/
SUNWinstall-libs/                                   SUNWxwxft/
SUNWlexpt/                                          SUNWzfs/
SUNWlibffi/                                         SUNWzlib/
SUNWlibms/                                          SUNWzone/
SUNWlibsasl/                                        consolidation%2FX%2FX-incorporation/
(Continue reading)

Eric Sproul | 4 Feb 2010 20:10
Favicon
Gravatar

Best SPARC CPU for building C programs?

Hi,
This is mostly idle curiosity... if I've got a decent amount of C compiling to
do for the SPARC platform, what would be the best CPU to use in the build
system?  "Best" here means "compiles the fastest", as the typical scenario would
be cranking through a large number of build scripts to create a set of packages.
 We target very generically, so I'm not concerned about much optimization, just
the time it takes to build a particular program.

It seems to me that because we're mostly talking about 'make', that
single-threaded performance is king here.  This makes me think the current line
of CoolThreads processors aren't necessarily best.  Would it then be UltraSPARC
IV/IV+?  I see that those have topped 2 GHz.

Thanks,
Eric
Alan Coopersmith | 4 Feb 2010 20:14
Picon

Re: Best SPARC CPU for building C programs?

Eric Sproul wrote:
> It seems to me that because we're mostly talking about 'make', that
> single-threaded performance is king here. 

If your software is so small and simple that you only compile a single
file, who cares?    In the much more complex software I work on, I got
it to compile about 25% of the time by getting dmake setup to have
multiple *.c files compiled in parallel on a 8-thread CPU.   Unfortunately
I haven't had a chance to see how well it does on a CoolThreads CPU.

--

-- 
	-Alan Coopersmith-           alan.coopersmith@...
	 Sun Microsystems, Inc. - X Window System Engineering
Eric Sproul | 4 Feb 2010 20:40
Favicon
Gravatar

Re: Best SPARC CPU for building C programs?

On 02/ 4/10 02:14 PM, Alan Coopersmith wrote:
> If your software is so small and simple that you only compile a single
> file, who cares?

I should have been clearer-- I'm talking about building open source software,
like Apache and PHP.  We build both 32- and 64-bit versions, and in the case of
PHP, we end up building *4* times (32/64-bit for Apache 1.3, 32/64-bit for
Apache 2.2).  It gets tedious when building on a V210 with 1.0GHz US-IIIi.  :)

> In the much more complex software I work on, I got
> it to compile about 25% of the time by getting dmake setup to have
> multiple *.c files compiled in parallel on a 8-thread CPU.   Unfortunately
> I haven't had a chance to see how well it does on a CoolThreads CPU.

That would be an ideal case for using a highly parallel CPU like the T2.  I've
not used dmake before, so I'll check it out.

Thanks,
Eric
William Yang | 4 Feb 2010 20:54
Favicon

Re: Best SPARC CPU for building C programs?

gmake can also thread using the -j option.  Most open source distributions
of software will build properly in parallel using either gmake or dmake, but
there are a handful I've run into that sometimes have trouble with it,
probably due to incompletely declared dependencies in the Makefile or
something.  I seem to remember that a few years ago, a T2 was once cited as
being able to build the Solaris kernel faster than an 8 core AMD.  We
currently have an M4000 (8 cores SPARC64-VI 2.1 GHz, 2 threads per core)
that we do our compiles on, and that's been able to compile almost as fast
as the identical software on an 8 core Intel X5460. 

William Yang

> -----Original Message-----
> From: sysadmin-discuss-bounces@... [mailto:sysadmin-discuss-
> bounces@...] On Behalf Of Eric Sproul
> Sent: Thursday, February 04, 2010 2:41 PM
> To: Alan Coopersmith
> Cc: sysadmin-discuss@...
> Subject: Re: [sysadmin-discuss] Best SPARC CPU for building C programs?
> 
> On 02/ 4/10 02:14 PM, Alan Coopersmith wrote:
> > If your software is so small and simple that you only compile a single
> > file, who cares?
> 
> I should have been clearer-- I'm talking about building open source
> software,
> like Apache and PHP.  We build both 32- and 64-bit versions, and in the
> case of
> PHP, we end up building *4* times (32/64-bit for Apache 1.3, 32/64-bit for
> Apache 2.2).  It gets tedious when building on a V210 with 1.0GHz US-
(Continue reading)


Gmane