I don't know, but I've succeeded to build ON b66 with SS12 and it works well
now.
But it's a debug version. And as I've mentioned in the previous email, I
fail to Install the non-debug version.
2007/7/6, Boyd Adamson <[EMAIL PROTECTED]>:
"Tao Jie" <[EMAIL PROTECTED]> writes:
> Hi, Ali
>
> > No
I don't know, but I've succeeded to build ON b66 with SS12 and it works well
now.
But it's a debug version. And as I've mentioned in the previous email, I
fail to Install the non-debug version.
2007/7/6, Boyd Adamson <[EMAIL PROTECTED]>:
"Tao Jie" <[EMAIL PROTECTED]> writes:
> Hi, Ali
>
> > No
"Tao Jie" <[EMAIL PROTECTED]> writes:
> Hi, Ali
>
> > No, you may safely ignore duplicate SUNW_dynsymsort messages. They are
> > more about tidiness than correctness. See here if you are interested
> > in the details:
> > http://www.opensolaris.org/os/community/on/flag-days/pages/2007052202/
> > I
Hi, Ali
2007/7/6, Ali Bahrami <[EMAIL PROTECTED]>:
陶捷 Tao Jie wrote:
>
>
> Check ELF runtime attributes
>
> ./lib/amd64/libelf.so.1: .SUNW_dynsymsort: duplicate 0x00023e38:
> elf32_getehdr, _elf32_getehdr
> ./lib/amd64/libelf.so.1: .SUNW_dynsymsort: duplicate 0x0002
陶捷 Tao Jie wrote:
>
>
> Check ELF runtime attributes
>
> ./lib/amd64/libelf.so.1: .SUNW_dynsymsort: duplicate 0x00023e38:
> elf32_getehdr, _elf32_getehdr
> ./lib/amd64/libelf.so.1: .SUNW_dynsymsort: duplicate 0x000240c8:
> _elf32_getphdr, elf32_getphdr
> ./lib/libe
Nightly distributed build started: Fri Jul 6 09:37:00 CST 2007
Nightly distributed build completed: Fri Jul 6 12:16:34 CST 2007
Total build time
real2:39:34
Nightly argument issues
Warning: the N option (do not run protocmp) is set; it probably s
No apologies necessary, it WAS broken for quite a while :)
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Allen,
Thanks for your quick reply,it's quite clean.
Rgds,
Simon
On 7/6/07, Lu, Baolu <[EMAIL PROTECTED]> wrote:
>
> Gzip drive:
> A high-capacity floppy disk drive developed by Iomega Corporation. Zip disks
> are slightly larger than conventional floppy disks, and about twice as thick.
> They
Carlton <[EMAIL PROTECTED]> writes:
> All I want to do is change the host name on my laptop.
>
> Numerous searches turn up to simply change the /etc/host file, but it is
> read only and won't accept the change.
>
> The man pages say not to use sysidconfig manually, so I don't know if it can
> b
Gzip drive:
A high-capacity floppy disk drive developed by Iomega Corporation. Zip disks
are slightly larger than conventional floppy disks, and about twice as thick.
They can hold 100 or 250 MB of data. Because they're relatively inexpensive and
durable, they have become a popular media for ba
Change these files, i.e hostname of odl server hostname to new hostname of
"test" IP address:
bash-3.00# cd /etc
bash-3.00# ls -altr /etc/host*
lrwxrwxrwx 1 root root 12 Jun 28 20:00 /etc/hosts -> ./inet/hosts
-rw-r--r-- 1 root root 1 Jun 28 20:39 /etc/hostname.nge0
Gurus,
I'm newer to Solaris 10,one question need your help:
what is Jaz drive and Zip drive for Solaris 10?
Thanks.
Rgds,
Simon
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
All I want to do is change the host name on my laptop.
Numerous searches turn up to simply change the /etc/host file, but it is read
only and won't accept the change.
The man pages say not to use sysidconfig manually, so I don't know if it can be
done.
Please advise
This message posted f
prtdiag -v will show the CPU type amd other system info, see the prtdiag man
page.
# prtdiag -v
System Configuration:
BIOS Configuration: Award Software International, Inc. F5 01/30/2007
Processor Sockets
Version Location Tag
Hmm, suddenly it works after posting that message. Apologies folks!
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Title says it all. I'm set to automatically log in, and all I get when I hit
this forum is the page header and footer - no forum content. Logging out of
os.org gives me the beginning of the thread list, but then a java exception in
the middle of the screen, followed by the footer. This obviously
Richard L. Hamilton wrote:
> I've been hearing static-like sounds from my speakers every so often when the
> audio should
> have been inactive; I'm thinking that it's being power-managed somehow. (sun
> blade 2000,
> audiocs device, build 66)
>
> I just added the line
> device-thresholds /
Can anyone give me some userful info aboat JDtace.Such as "How to user",
I just konw First:Consumer.open() Second:Consumer.compile();
Third:Consumer.enable(Programe p) and Last: Consumer.go();
But I didn't know anymore aboat it beacuse of my poor english.
This message posted from opensolaris.o
> Dennis Clarke wrote:
>> Where do we stand on 6576229 ?
>>
>> Is this a show stopper for building snv_68 out here ?
>
> No. onnv_68 was released before the fwflash putback.
Excellent .. thank you. I can proceed here with no worries.
>> If so, can we implement a test phase in which the
Dennis Clarke wrote:
> Where do we stand on 6576229 ?
>
> Is this a show stopper for building snv_68 out here ?
No. onnv_68 was released before the fwflash putback.
> If so, can we implement a test phase in which the open-only build does
> get built before release to the world ?
This o
Where do we stand on 6576229 ?
Is this a show stopper for building snv_68 out here ?
If so, can we implement a test phase in which the open-only build does
get built before release to the world ?
Dennis
___
opensolaris-discuss mailing list
op
Hi Andrew,
* Andrew Watkins ([EMAIL PROTECTED]) wrote:
> Thanks for all the information, but the problem I am having - well not
> a problem - just a general question.
>
> What I have done is boot a Intel Core 2 (running Windows) off the
> latest OpenSolaris B67 x86 and entered the Singe User Shel
Andrew Watkins stated:
< Thanks for all the information, but the problem I am having - well not a
problem - just a general question.
<
< What I have done is boot a Intel Core 2 (running Windows) off the latest
OpenSolaris B67 x86 and entered the Singe User Shell straight away.
Did you enter
https://secure.paymentclearing.com/cgi-bin/mas/buynow.cgi";>
Breitling emergency watches replica omega
speedmaster omega and Jacob & Co. replica watches
Breitling omega jacob & Co. replica watches bape hoodies bape clothing
http://wholesale-distribut
Thanks for all the information, but the problem I am having - well not a
problem - just a general question.
What I have done is boot a Intel Core 2 (running Windows) off the latest
OpenSolaris B67 x86 and entered the Singe User Shell straight away.
# isainfo -v
32-bit i386 applications
Now is
Hi Tao Jie.
While booted, you can check for existence of variables declared only if
DEBUG is set on.
You can use the following command:
/usr/ccs/bin/nm /dev/ksyms | grep
Using mdb, you can also check the value of variables which are different
depending on DEBUG. For example, kmem_flags
btw, How can I determine whether the ON is a debug version or a
non-debug version, if it is not built by myself and I only have the
"Install.i86pc.tar" tarball?
1, Before I bootup this ON, what could I do?
&
2, When this ON is running, what could I do?
Thanks :)
Regards
TJ
2007/7/5, Gavin Malt
Aubrey Li wrote:
> On 7/5/07, Erast Benson <[EMAIL PROTECTED]> wrote:
>> http://www.gnusolaris.org/unstable-iso/ncp_beta1-test3-b68_i386.iso
>
> That's great news. Congratulations!
>> Changes:
>>
>> * ON b68 based
>
> Is ON b68 released? I didn't see it on open-solaris.org
http://dlc.sun.com/oso
Hi,
I've tried to use latest snv67 build with bundled postgres 8.2.4 database and
got the following error when trying to connect to it with psql (initdb goes
fine):
$ psql postgres
LOG: setsockopt(TCP_NODELAY) failed: Option not supported by protocol
psql: server closed the connection unexpect
On 7/5/07, Erast Benson <[EMAIL PROTECTED]> wrote:
> http://www.gnusolaris.org/unstable-iso/ncp_beta1-test3-b68_i386.iso
That's great news. Congratulations!
>
> Changes:
>
> * ON b68 based
Is ON b68 released? I didn't see it on open-solaris.org
> * man pages updated
>
Nexenta is really a great i
I see~ You're all warmhearted, thanks all :)
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Stephen Lau <[EMAIL PROTECTED]> wrote:
> I don't believe all Pentium 4's were 64-bit... but I may be wrong.
Not all were 64 bit and not all were speudo dual core.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED](uni)
[EMAIL
[ opensolaris-code would have been a better place, I've set replys to go
there ]
陶捷 Tao Jie wrote:
> What's the difference?
The debug kernel is built with DEBUG=1 defined so that code behind an
#ifdef DEBUG is enabled.
> When using the debug ON, what messages can I get?
Debug ones :-)
> How
Hi,
On 07/05/07 10:17, ?? Tao Jie wrote:
> What's the difference?
Debug bits are compiled with DEBUG defined (-DDEBUG on cc cmdline etc).
So any code that is bracketed by a #ifdef DEBUG ... #endif becomes
active. This brings additional levels of debug and checking to
life, eg in the sample code:
Hi,
On 07/04/07 21:56, Andrew Watkins wrote:
> I know you may think it is a silly question, but I am unable to find the
> answer.
> OK! We know Sun SPARC chips all run 64 bit OpenSolaris, but which AMD and
> Intel cpu can run it as well:
The OpenSolaris source only supports a 64-bit sparc kerne
What's the difference?
When using the debug ON, what messages can I get?
How can I build a non-debug ON? just use the non-debug on-closed-bins?
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
> I know you may think it is a silly question, but I am
> unable to find the answer.
> OK! We know Sun SPARC chips all run 64 bit
> OpenSolaris, but which AMD and Intel cpu can run it
> as well:
>
> - AMD Opteron run 64bit kernel
> - Intel Xeon run 64bit kernel
>
> but what about:
>
> - AMD At
http://www.gnusolaris.org/unstable-iso/ncp_beta1-test3-b68_i386.iso
Changes:
* ON b68 based
* man pages updated
--
Erast
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
38 matches
Mail list logo
