On 2011-11-07, Bubba <nick...@banelli.biz.invalid> wrote:
> DoN. Nichols's log on stardate 07 stu 2011
>
>>> Is that correct, for example, in respect of gcc, web performance and
>>> simmilar things?
>> Well ... I tend to prefer the compiler in Sun's "Studio 12"
>> development package -- if you can still get it along with Solaris 10
>> since the Oracle takeover, but there are some programs which really
>> need gcc to compile. My experience is that one takes longer to
>> compile, but produces somewhat faster code. (And I forget which is
>> which at the moment.)
>
> Hehe, well, I'd sacrifice longer compile time (that is, after all, "one
> time job") for faster run time.
With the tradeoff that if you are doing a lot of compiles in
debugging, the faster compile is a benefit until you are ready for
production. (So write your code so it will compile on both. :-)
Here is the comparison (using the old dhrystone benchmark) with
the two compilers on a Sun Blade 2000 with dual 1.2 GHz CPUs:
======================================================================
* MACHINE MICROPROCESSOR OPERATING COMPILER DHRYSTONES/SEC.
* TYPE SYSTEM NO REG REGS
* -------------------------- ------------ ----------- ---------------
* SB-2K US-III dual 1.2 GHZ Solaris 10 cc 3086419 3086419
* SB-2K US-III dual 1.2 GHZ Solaris 10 gcc 3355704 3355704
======================================================================
So -- since gcc produced the faster run time (in this one very
limited benchmark), then the cc with Studio 12 must have been the faster
compile time.
with lots of other machine results snipped out.
> Either way, I need CLI tool, so I believe "Studio 12" or whatever is IDE,
> so it is probably not worth installing just for compiler.
There are a bunch of CLI compilers in the Studio 12 package, and
NetBeans is the accompanying IDE, which I have never used.
======================================================================
/opt/SUNWspro/bin:
analyzer@ cxref@ fbe@ rtc_patch_area@ tcov@
b2m@ dbx@ fdumpmod@ rxm@ tha@
bcheck@ dem@ fpp@ rxs@ uil2xd@
bil2xd@ dmake@ fpr@ sbcleanup@ uninstaller@
binopt@ dumpstabs@ fpversion@ sbenter@ version-5.0@
c++filt@ dwarfdump@ fsplit@ sbquery@ version@
c89@ ellcc@ gil2xd@ sbtags@ visu@
c99@ er_archive@ gnuattach@ smallxd@ visuroot@
cb@ er_cp@ gnuclient@ smctl@ whatdir@
cc-5.0@ er_export@ gnudoit@ sparcv9/ xdcapture@
cc@ er_kernel@ gvim@ ss_attach@ xdconfig@
CC@ er_mv@ indent@ sunas@ xdesigner@
CCadmin@ er_print@ libsunperf_check@ sunc89@ xdhelp@
cflow@ er_rm@ lint@ sunc99@ xdrecord@
checkjava@ er_src@ lock_lint@ suncc@ xdreplay@
collect@ etags@ ootags@ sunCC@ xdroot@
cscope@ f77@ prepare_system@ sunf77@ xdtosj@
ctc@ f90@ ptclean@ sunf90@ xemacs-mule@
ctcr@ f95@ rcs-checkin@ sunf95@ xemacs@
ctrace@ fbe-4.0@ rdtimgr@ sunstudio@
======================================================================
These are all duplicated by more links in /usr/bin. So lots of CLI
compilers, including several flavors of C, and several versions of
FORTRAN as well as tools like indent, cflow, cscope, and dbx (the
debugger).
BTW Also beware that some programs may not absolutely require gcc
to compile, but will look like it, because they require a gnu
(or similar) version of make.
BTW Also notice several gnu programs are in the above list.
> In any case, I'll check it out, thanks.
Enjoy.
>>> I was afraid there might be something important in ALOM that would
>>> prevent me from accessing OS or something like that.
>> Only if you are trying to control it remotely (via ALOM). If
>> the V440 is like the Sun Fire 280R, you can even pull out the card
>> which implements ALOM or RSC (mine had RSC, not ALOM). However, the
>> Sun Fire V120 has the LOM chip on the system board, so you can't do
>> that, though you can change a jumper and power it up to flush the
>> current settings (including passwords) in the LOM.
>
> I saw some jumpers, yes, and I thought they might be for something like
> clearing settings. However, I couldn't find any sane documentation
> regarding that card per se, so I'll have to give it a try a bit more...
Is the ALOM on the V440 a separate card, like the RCS on the Sun
Fire 280R? If so, you can simply pull the card and get it all out of
the way until you have an installed OS, and then can reinstall the ALOM
card and clean the user list and associated passwords in there.
>> If you select "initial install" (I think that is the term, not
>> "initialize"), you will newfs all the disk partitions, and if you
>> re-partition (select the "custom" option when it gets to asking about
>> disk partitions), that will pretty much force a newfs on each changed
>> partition. But really, an "initial install" will clear away anything
>> on the disk anyway -- though not as thoroughly as it would with the
>> format "analyze" options set for one of the modes to "destroy
>> existing data" -- but I hope that you have plenty of time to twiddle
>> your thumbs while it does this.
>
> Oh, that's great news.
>
> Well, I'll just keep it rollin' during the night...
O.K. The initial install does not take that long, even with
manual repartitioning, but if you go into format and ask for a
destructive surface check, that will take forever with 72 GB or larger
disks. But for your purposes, just letting the initial install do its
newfs on each partition should be fine.
>> Freshly scrubbed disks with a new install of Solaris -- I would
>> *hope*. :-) Maybe spare disks which they kept around fully loaded
>> with the OS for emergencies, and which they swapped in to send away a
>> "clean" system.
>
> I don't really care, I just want to wipe them clean, even if they had
> human readable text files with PIN's. :)
If you really fear that such is there (and are worried about it
being there), then the format with the surface check option. O.K. Here
is the first menu in format:
======================================================================
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format>
======================================================================
And the choice which I was trying to remember is "analyze". And its
sub-menu is:
======================================================================
ANALYZE MENU:
read - read only test (doesn't harm SunOS)
refresh - read then write (doesn't harm data)
test - pattern testing (doesn't harm data)
write - write then read (corrupts data)
compare - write, read, compare (corrupts data)
purge - write, read, write (corrupts data)
verify - write entire disk, then verify (corrupts data)
print - display data buffer
setup - set analysis parameters
config - show analysis parameters
!<cmd> - execute <cmd> , then return
quit
analyze>
======================================================================
The "purge" choice would probably be the best one, and it will take (by
default) two passes, each with bit patterns which are the compliment of
the previous one. A third pass with yet another bit pattern would be
even better, if you have the time to spare. After this, nobody except
perhaps the intelligence agencies would be able to show what was on
there before. You can tune the bit patterns among othe things with the
"setup" menu entry.
>> O.K. Looks like UK power cords. Nice Fluke meters.
>
> Nope, two times. :) It's Croatia (Schuko -
O.K. Certainly not US ones -- including based on the voltage
shown.
That is what matters. The voltmeter is a Fluke, though, is it
not? I've lost the URL so I can't go back and check.
Good Luck,