Re: [osol-discuss] SSH - multiple sessions in one command
On Wed, Aug 06, 2008 at 09:39:45PM -0400, Matt Fioravante wrote: > I am trying to write a script to move a zone from one host to another in one > command. > > Is there a way that I can do multiple ssh commands but only have to > authenticate one time? I want to do several commands with ssh, and a couple > file copies with rsync but I don't want to have to enter the password 8 > times. Use authorized_keys approach - ssh(1) - no password, or possibly ssh-agent(1) might be your friend. /j. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris200805 can not boot up after SUNWiwi installation
david, the beadm thingies arent documented there. i recommend to check [0] this too [0] http://mail.opensolaris.org/pipermail/opensolaris-announce/2008-July/001874.html On Thu, Aug 7, 2008 at 5:58 AM, <[EMAIL PROTECTED]> wrote: >> Same for me after installing package SUNWtoo, and the fact that they have >> removed the failsafe from the 05/08 version makes this one hell of a >> disaster. > > Before trying to install SUNWtoo, did you follow the steps documented > at the front of the release notes (labeled "Important Package Update > Instructions for ALL Users") > >http://opensolaris.org/os/project/indiana/resources/rn3/ > > Unfortunately, there was a critical issue in the packaging system as > shipped on the 2008.05 CD which can lead to the wrong version of > packages being installed on the system. Following the three steps > outlined in the release notes will go a long way towards avoiding the > issue that I believe you're seeing. > > dsc > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > -- Andy http://blog.sartek.net ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blastwave.org - any info?
Temporary workaround until (hopefully) genunix.org gets extracated from this mess: add this line to your hosts file: 204.152.191.100 genunix.org www.genunix.org Cheers Andrew. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] configure: error: C preprocessor "/lib/cpp" fails sanity check
check
http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEsed.spec
and http://pkgbuild.sourceforge.net/spec-files-extra/
On Thu, Aug 7, 2008 at 5:37 AM, Krenz von Leiberman
<[EMAIL PROTECTED]> wrote:
> Hello.
> I just tried to run configure on gnu sed.
> I got this output:
>
> [quote]
> /root/bld/sed-4.1.5# /root/src/sed-4.1.5/configure
> checking for a BSD-compatible install... /usr/bin/ginstall -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for gcc... no
> checking for cc... cc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... no
> checking whether cc accepts -g... yes
> checking for cc option to accept ANSI C... none needed
> checking for style of include used by make... GNU
> checking dependency style of cc... none
> checking for ranlib... ranlib
> checking how to run the C preprocessor... /lib/cpp
> configure: error: C preprocessor "/lib/cpp" fails sanity check
> See `config.log' for more details.
> [end]
>
> I installed sunstudio 11. I don't see why this would not work. I thought that
> the C-Preprocesor was included. How do I install/enable it?
> Here is my config.log:
>
> [start]
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
>
> It was created by sed configure 4.1.5, which was
> generated by GNU Autoconf 2.59. Invocation command line was
>
> $ /root/src/sed-4.1.5/configure
>
> ## - ##
> ## Platform. ##
> ## - ##
>
> hostname = ragnarok
> uname -m = i86pc
> uname -r = 5.11
> uname -s = SunOS
> uname -v = BeleniX0.7.1
>
> /usr/bin/uname -p = i386
> /bin/uname -X = System = SunOS
> Node = ragnarok
> Release = 5.11
> KernelID = BeleniX0.7.1
> Machine = i86pc
> BusType =
> Serial =
> Users =
> OEM# = 0
> Origin# = 1
> NumCPU = 1
>
> /bin/arch = i86pc
> /usr/bin/arch -k = i86pc
> /usr/convex/getsysinfo = unknown
> hostinfo = unknown
> /bin/machine = unknown
> /usr/bin/oslevel = unknown
> /bin/universe = unknown
>
> PATH: /usr/gnu/bin
> PATH: /usr/bin
> PATH: /usr/SUNWspro/bin
> PATH: /usr/X11/bin
> PATH: /usr/sbin
> PATH: /sbin
> PATH: /usr/sfw/bin
>
>
> ## --- ##
> ## Core tests. ##
> ## --- ##
>
> configure:1376: checking for a BSD-compatible install
> configure:1431: result: /usr/bin/ginstall -c
> configure:1442: checking whether build environment is sane
> configure:1485: result: yes
> configure:1550: checking for gawk
> configure:1566: found /usr/bin/gawk
> configure:1576: result: gawk
> configure:1586: checking whether make sets $(MAKE)
> configure:1606: result: yes
> configure:1829: checking for gcc
> configure:1858: result: no
> configure:1909: checking for cc
> configure:1925: found /usr/SUNWspro/bin/cc
> configure:1935: result: cc
> configure:2099: checking for C compiler version
> configure:2102: cc --version &5
> cc: Warning: option -- passed to ld
> usage: cc [ options] files. Use 'cc -flags' for details
> configure:2105: $? = 1
> configure:2107: cc -v &5
> usage: cc [ options] files. Use 'cc -flags' for details
> configure:2110: $? = 1
> configure:2112: cc -V &5
> cc: Sun C 5.8 Patch 121016-05 2007/01/10
> usage: cc [ options] files. Use 'cc -flags' for details
> configure:2115: $? = 1
> configure:2138: checking for C compiler default output file name
> configure:2141: ccconftest.c >&5
> configure:2144: $? = 0
> configure:2190: result: a.out
> configure:2195: checking whether the C compiler works
> configure:2201: ./a.out
> configure:2204: $? = 0
> configure:2221: result: yes
> configure:2228: checking whether we are cross compiling
> configure:2230: result: no
> configure:2233: checking for suffix of executables
> configure:2235: cc -o conftestconftest.c >&5
> configure:2238: $? = 0
> configure:2263: result:
> configure:2269: checking for suffix of object files
> configure:2290: cc -c conftest.c >&5
> configure:2293: $? = 0
> configure:2315: result: o
> configure:2319: checking whether we are using the GNU C compiler
> configure:2343: cc -c conftest.c >&5
> "conftest.c", line 17: undefined symbol: choke
> "conftest.c", line 17: syntax error before or at: me
> cc: acomp failed for conftest.c
> configure:2349: $? = 2
> configure: failed program was:
> | /* confdefs.h. */
> |
> | #define PACKAGE_NAME "sed"
> | #define PACKAGE_TARNAME "sed"
> | #define PACKAGE_VERSION "4.1.5"
> | #define PACKAGE_STRING "sed 4.1.5"
> | #define PACKAGE_BUGREPORT "[EMAIL PROTECTED]"
> | #define PACKAGE "sed"
> | #define VERSION "4.1.5"
> | #define SED_FEATURE_VERSION "4.1"
> | /* end confdefs.h. */
> |
> | int
> | main ()
> | {
> | #ifndef __GNUC__
> |c
Re: [osol-discuss] blastwave.org - any info?
On Wed, Aug 6, 2008 at 9:17 PM, andrew <[EMAIL PROTECTED]> wrote: > The phone number referred to in the holding page is for a company called > LiveWire at the following address: > > 80 Galaxy Boulevard, Suite 19 > Toronto, Ontario M9W 4Y8 > Tel : ( 416 ) 798 - 3410 > Fax : ( 416 ) 798 - 3391 > > (from www.livewirecomputer.com, which seems to be the same as livewire.ca. > Dennis's email address is listed on the holding page as dclarke at livewire > dot ca and the toll free number is also for Livewire). > > Is Livewire just his ISP or is there more to it? > > Also, why is the holding page asking for donations with no explanation as > to what has happened, except to say that the companies assets have been > frozen??? > > Here is the whois dump for genunix.org BTW. Note CLIENT TRANSFER > PROHIBITED - is that normal for NSI registered domains or has it been frozen > as well? > > Domain ID:D106563976-LROR > Domain Name:GENUNIX.ORG > Created On:08-Jun-2005 20:10:06 UTC > Last Updated On:06-Aug-2008 22:09:41 UTC > Expiration Date:08-Jun-2013 20:10:06 UTC > Sponsoring Registrar:Network Solutions LLC (R63-LROR) > Status:CLIENT TRANSFER PROHIBITED > Registrant ID:2419290-NSI > Registrant Name:DENNIS CLARKE > Registrant Organization:blastwave.org > > [Address & tel number removed] > > Registrant [EMAIL PROTECTED] > Admin ID:2419290-NSI > Admin Name:DENNIS CLARKE > Admin Organization:blastwave.org > > [Address & tel number removed] > > Admin [EMAIL PROTECTED] > Tech ID:2419290-NSI > Tech Name:DENNIS CLARKE > Tech Organization:blastwave.org > > [Address & tel number removed] > > Tech [EMAIL PROTECTED] > Name Server:NS1.BLASTWAVE.ORG > Name Server:NS2.BLASTWAVE.ORG > > (dumped from www.dnsstuff.com). > > Cheers > > Andrew. > I'm making a huge assumption: the website says: Legal representation for the affairs of Blastwave.org Inc. are handled by Deeth Williams Wall LLP in Toronto Canada. ( DWW.com ) dww.com is a trademark and patent lawyer. I have the feeling that this is what is going on. We need word from dennis as to why he needs money, and I am sure we can get the ball rolling. -- Chris Mahan [EMAIL PROTECTED] cell 818.943.1850 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blastwave.org - any info?
Blastwave mirror list: http://www.canoedissent.org.uk/mirror/status/ Cheers Andrew. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] some command can't be used in chroot,
On Thu, Aug 7, 2008 at 8:07 AM, wan_jm <[EMAIL PROTECTED]> wrote: > thanks. resolved. > > another question: can i use chroot to add driver in the virtual system. Yes you can but what is the point ? Chroot does not run a separate kernel. It is just a filesystem jail within the running OS. Regards, Moinak. > > > This message posted from opensolaris.org > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > -- http://www.belenix.org/ http://moinakg.wordpress.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blastwave.org - any info?
The phone number referred to in the holding page is for a company called LiveWire at the following address: 80 Galaxy Boulevard, Suite 19 Toronto, Ontario M9W 4Y8 Tel : ( 416 ) 798 - 3410 Fax : ( 416 ) 798 - 3391 (from www.livewirecomputer.com, which seems to be the same as livewire.ca. Dennis's email address is listed on the holding page as dclarke at livewire dot ca and the toll free number is also for Livewire). Is Livewire just his ISP or is there more to it? Also, why is the holding page asking for donations with no explanation as to what has happened, except to say that the companies assets have been frozen??? Here is the whois dump for genunix.org BTW. Note CLIENT TRANSFER PROHIBITED - is that normal for NSI registered domains or has it been frozen as well? Domain ID:D106563976-LROR Domain Name:GENUNIX.ORG Created On:08-Jun-2005 20:10:06 UTC Last Updated On:06-Aug-2008 22:09:41 UTC Expiration Date:08-Jun-2013 20:10:06 UTC Sponsoring Registrar:Network Solutions LLC (R63-LROR) Status:CLIENT TRANSFER PROHIBITED Registrant ID:2419290-NSI Registrant Name:DENNIS CLARKE Registrant Organization:blastwave.org [Address & tel number removed] Registrant [EMAIL PROTECTED] Admin ID:2419290-NSI Admin Name:DENNIS CLARKE Admin Organization:blastwave.org [Address & tel number removed] Admin [EMAIL PROTECTED] Tech ID:2419290-NSI Tech Name:DENNIS CLARKE Tech Organization:blastwave.org [Address & tel number removed] Tech [EMAIL PROTECTED] Name Server:NS1.BLASTWAVE.ORG Name Server:NS2.BLASTWAVE.ORG (dumped from www.dnsstuff.com). Cheers Andrew. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with threaded test program
I used dbx as suggested and I was getting (rua) and (rui) messages. I corrected those and the program still hangs in the same place. This is the stack trace from dbx: (dbx) where current thread: [EMAIL PROTECTED] [1] __lwp_park(0x0, 0x0), at 0xb3da3df9 [2] mutex_lock_queue(0xd13b2a00, 0x0, 0x8046b58, 0x0), at 0xb3d9cde3 [3] slow_lock(0xd13b2a00, 0x8046b58, 0x0), at 0xb3d9d6d0 [4] mutex_lock_impl(0x8046b58, 0x0), at 0xb3d9d7c6 [5] _private_mutex_lock(0x8046b58, 0xbf11b078, 0x8046b4c, 0xb8e1ff44, 0x, 0x), at 0xb3d9d8d2 [6] std::basic_ostream >::sentry::sentry(0x8045e24, 0x8046b4c, 0x8047270, 0x804712c, 0xbf12bc14, 0xc5542c3c), at 0xb8d96c16 [7] std::operator<< >(0x8046b4c, 0xbf11b078, 0x8047270, 0x804712c, 0xbf12bc14, 0x8046a18), at 0xb8da5b92 =>[8] lfc1::general::operator<<(arStream = CLASS, arException = CLASS), line 116 in "xexception.cpp" [9] CTestISyncCreateFail::mvTestOutputter(this = 0x8168c58), line 96 in "testsyslib_ctestisynccreatefail.cpp" [10] lfc1::unittest::CTestCaller::CTestCallerFunctor::operator()(this = 0x8046fb0), line 110 in "unittest_ctestcaller.hpp" [11] lfc1::general::CProtector::mvProtect(this = 0x804712c, arFunctor = CLASS, arContext = CLASS), line 54 in "cprotector.cpp" [12] lfc1::unittest::CDefaultProtector::mvProtect(this = 0x8047120, arFunctor = CLASS, arContext = CLASS), line 48 in "cdefaultprotector.cpp" [13] lfc1::unittest::CTestController::mvProtect(this = 0x804710c, arFunctor = CLASS, apTest = 0x816cd10, arPartName = CLASS), line 90 in "ctestcontroller.cpp" [14] lfc1::unittest::CTestCaller::mvRun(this = 0x816cd10, apController = 0x804710c), line 186 in "unittest_ctestcaller.hpp" [15] lfc1::unittest::CTestSuite::mvRun(this = 0x816ccd8, apController = 0x804710c), line 59 in "ctestsuite.cpp" [16] lfc1::unittest::CTestSuite::mvRun(this = 0x814a048, apController = 0x804710c), line 59 in "ctestsuite.cpp" [17] lfc1::unittest::CTextTestRunner::mvRun(this = 0x80470dc, apTest = 0x814a048), line 45 in "ctexttestrunner.cpp" [18] main(), line 168 in "testsyslib.cpp" Can anyone give me a clue what I should be looking out for? Do you think watchmalloc will help in this case? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris200805 can not boot up after SUNWiwi installation
> Same for me after installing package SUNWtoo, and the fact that they have > removed the failsafe from the 05/08 version makes this one hell of a disaster. Before trying to install SUNWtoo, did you follow the steps documented at the front of the release notes (labeled "Important Package Update Instructions for ALL Users") http://opensolaris.org/os/project/indiana/resources/rn3/ Unfortunately, there was a critical issue in the packaging system as shipped on the 2008.05 CD which can lead to the wrong version of packages being installed on the system. Following the three steps outlined in the release notes will go a long way towards avoiding the issue that I believe you're seeing. dsc ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Error when installing OpenSolaris 2008.5 as Xen DomU
> I'm using the GUI guest OS installer in virt-manager. Here is my setup for > the VM: I believe there are changes to virt-manager(1) and/or virt-install(1M) that are required to support 2008.05 as a PV guest. I would suggest sending your question to [EMAIL PROTECTED] as the xVM team know what the necessary changes we made to xVM to support the same thing. dsc ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] ps -p running very slow (1-2 seconds) on Java process
Hi Solaris gurus:
I encountered a issue that running ps -p on java process running very slow, it
took almost 2 seconds to complete.
I issued a truss on the "ps -p " command, the following is part of the
output:
/1: 0.0001 fstat(1, 0x7FFFE1F0)= 0
/1: 0. write(1, " U I D P".., 55) = 55
/1: 0.0002 open("/proc/19299/psinfo", O_RDONLY)= 3
/1: 1.3170 read(3, "02\0\0\0\0\0\011\0\0 K c".., 416) = 416
/1: 1.2401 close(3)= 0
/1: 0.0002 stat("/dev/tty", 0x7FFFE830)= 0
It seems that the read() spent the most time.
Anyone can help?
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] ps -ef running really slow on non-global zone
I encountered the same issue, but the nscd is running:
ps -ef | grep nscd
root 400 1 0 Aug 05 ? 7:47 /usr/sbin/nscd
And the truss output as below:
..
/1: 0.0001 fstat(1, 0x7FFFE1F0)= 0
/1: 0. write(1, " U I D P".., 55) = 55
/1: 0.0002 open("/proc/19299/psinfo", O_RDONLY)= 3
/1: 1.3170 read(3, "02\0\0\0\0\0\011\0\0 K c".., 416) = 416
/1: 1.2401 close(3)= 0
/1: 0.0002 stat("/dev/tty", 0x7FFFE830)= 0
..
It seems that the read() spent the most time.
Anyone can help?
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
[osol-discuss] configure: error: C preprocessor "/lib/cpp" fails sanity check
Hello.
I just tried to run configure on gnu sed.
I got this output:
[quote]
/root/bld/sed-4.1.5# /root/src/sed-4.1.5/configure
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... no
checking for cc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
checking whether cc accepts -g... yes
checking for cc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of cc... none
checking for ranlib... ranlib
checking how to run the C preprocessor... /lib/cpp
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
[end]
I installed sunstudio 11. I don't see why this would not work. I thought that
the C-Preprocesor was included. How do I install/enable it?
Here is my config.log:
[start]
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by sed configure 4.1.5, which was
generated by GNU Autoconf 2.59. Invocation command line was
$ /root/src/sed-4.1.5/configure
## - ##
## Platform. ##
## - ##
hostname = ragnarok
uname -m = i86pc
uname -r = 5.11
uname -s = SunOS
uname -v = BeleniX0.7.1
/usr/bin/uname -p = i386
/bin/uname -X = System = SunOS
Node = ragnarok
Release = 5.11
KernelID = BeleniX0.7.1
Machine = i86pc
BusType =
Serial =
Users =
OEM# = 0
Origin# = 1
NumCPU = 1
/bin/arch = i86pc
/usr/bin/arch -k = i86pc
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/gnu/bin
PATH: /usr/bin
PATH: /usr/SUNWspro/bin
PATH: /usr/X11/bin
PATH: /usr/sbin
PATH: /sbin
PATH: /usr/sfw/bin
## --- ##
## Core tests. ##
## --- ##
configure:1376: checking for a BSD-compatible install
configure:1431: result: /usr/bin/ginstall -c
configure:1442: checking whether build environment is sane
configure:1485: result: yes
configure:1550: checking for gawk
configure:1566: found /usr/bin/gawk
configure:1576: result: gawk
configure:1586: checking whether make sets $(MAKE)
configure:1606: result: yes
configure:1829: checking for gcc
configure:1858: result: no
configure:1909: checking for cc
configure:1925: found /usr/SUNWspro/bin/cc
configure:1935: result: cc
configure:2099: checking for C compiler version
configure:2102: cc --version &5
cc: Warning: option -- passed to ld
usage: cc [ options] files. Use 'cc -flags' for details
configure:2105: $? = 1
configure:2107: cc -v &5
usage: cc [ options] files. Use 'cc -flags' for details
configure:2110: $? = 1
configure:2112: cc -V &5
cc: Sun C 5.8 Patch 121016-05 2007/01/10
usage: cc [ options] files. Use 'cc -flags' for details
configure:2115: $? = 1
configure:2138: checking for C compiler default output file name
configure:2141: ccconftest.c >&5
configure:2144: $? = 0
configure:2190: result: a.out
configure:2195: checking whether the C compiler works
configure:2201: ./a.out
configure:2204: $? = 0
configure:2221: result: yes
configure:2228: checking whether we are cross compiling
configure:2230: result: no
configure:2233: checking for suffix of executables
configure:2235: cc -o conftestconftest.c >&5
configure:2238: $? = 0
configure:2263: result:
configure:2269: checking for suffix of object files
configure:2290: cc -c conftest.c >&5
configure:2293: $? = 0
configure:2315: result: o
configure:2319: checking whether we are using the GNU C compiler
configure:2343: cc -c conftest.c >&5
"conftest.c", line 17: undefined symbol: choke
"conftest.c", line 17: syntax error before or at: me
cc: acomp failed for conftest.c
configure:2349: $? = 2
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME "sed"
| #define PACKAGE_TARNAME "sed"
| #define PACKAGE_VERSION "4.1.5"
| #define PACKAGE_STRING "sed 4.1.5"
| #define PACKAGE_BUGREPORT "[EMAIL PROTECTED]"
| #define PACKAGE "sed"
| #define VERSION "4.1.5"
| #define SED_FEATURE_VERSION "4.1"
| /* end confdefs.h. */
|
| int
| main ()
| {
| #ifndef __GNUC__
|choke me
| #endif
|
| ;
| return 0;
| }
configure:2375: result: no
configure:2381: checking whether cc accepts -g
configure:2402: cc -c -g conftest.c >&5
configure:2408: $? = 0
configure:2412: test -z
|| test ! -s conftest.err
configure:2415: $? = 0
configure:2418: test -s conftest.o
configure:2421: $? = 0
configure:2432: result: yes
configure:2449: checking for cc option to accept ANSI C
configure:2519: cc -c -g conftest.c >&5
"conftest.c", line 12: cannot find include file:
Re: [osol-discuss] some command can't be used in chroot,
thanks. resolved. another question: can i use chroot to add driver in the virtual system. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blastwave.org - any info?
Ian Collins wrote: > Alan Coopersmith wrote: >> http://204.152.191.100/ >> > The wiki's gone :( Clicking through tries to redirect via the DNS name, but going to http://204.152.191.100/wiki/index.php/Main_Page seems to work for me. Perhaps Ben or Al can bring it back online with a new domain name. -- -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc. - X Window System Engineering ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blastwave.org - any info?
Ian Collins wrote: > Matthew Snyder wrote: > >> A little off topic, but I figure you guys use the site and I see Dennis >> around here often, so.. >> >> Anyone know whats up with blastwave.org? the notice sounds legal; >> probably means no official updates right now. Anyone know anything? >> >> I hope all is ok DC >> >> > genunix.org has gone down with it. Not good. > > I thought genunix.org was independent of Blastwave; the mails on the subject form May/June '05 indicate that it is. I know Logical Approach supplied some of the hardware and Al Hopper was involved in commissioning the site. Maybe it's a problem with the domain ownership? Ian ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blastwave.org - any info?
On Wed, Aug 6, 2008 at 7:27 PM, Chris Mahan <[EMAIL PROTECTED]> wrote: > > > On Wed, Aug 6, 2008 at 7:22 PM, Ian Collins <[EMAIL PROTECTED]> wrote: > >> >> > http://204.152.191.100/ >> > >> The wiki's gone :( >> > > It's still there: > > http://204.152.191.100/wiki/index.php/Main_Page > Now the question is: how to suck the content out... Anybody want to write a crawler pronto? or even get a sql dump? somehow? > > > -- > Chris Mahan > [EMAIL PROTECTED] > cell 818.943.1850 > -- Chris Mahan [EMAIL PROTECTED] cell 818.943.1850 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blastwave.org - any info?
On Wed, Aug 6, 2008 at 7:22 PM, Ian Collins <[EMAIL PROTECTED]> wrote: > > > http://204.152.191.100/ > > > The wiki's gone :( > It's still there: http://204.152.191.100/wiki/index.php/Main_Page -- Chris Mahan [EMAIL PROTECTED] cell 818.943.1850 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blastwave.org - any info?
Alan Coopersmith wrote: > Ian Collins wrote: > >> Matthew Snyder wrote: >> >>> A little off topic, but I figure you guys use the site and I see Dennis >>> around here often, so.. >>> >>> Anyone know whats up with blastwave.org? the notice sounds legal; >>> probably means no official updates right now. Anyone know anything? >>> >>> I hope all is ok DC >>> >>> >> genunix.org has gone down with it. Not good. >> > > genunix.org is still available if you use the real IP address, not the > new ones the blastwave nameservers started publishing today. (My DNS > server is fortunate to still have the old ones cached, but I'm sure that > won't last long.) > > http://204.152.191.100/ > The wiki's gone :( Ian ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] VIA PC2500E and opensolaris?
On Mon, Aug 4, 2008 at 10:06 PM, Gil <[EMAIL PROTECTED]> wrote: > Can someone tell me if opensolaris will run on this low power setup? Can I > assume that if it is not listed in the HCL it will not support Opensolaris? Runs just fine; all I had to do was install a third-party network driver. [EMAIL PROTECTED]:~> uname -a SunOS porkproduct 5.11 snv_83 i86pc i386 i86pc Solaris [EMAIL PROTECTED]:~> psrinfo -v Status of virtual processor 0 as of: 08/06/2008 21:17:35 on-line since 04/10/2008 23:34:35. The i386 processor operates at 1500 MHz, and has an i387 compatible floating point processor. [EMAIL PROTECTED]:~> modinfo |grep vfe 146 f970 b9b4 260 1 vfe (via rhine nic driver v2.6.2) [EMAIL PROTECTED]:~> prtdiag -v |more System Configuration: IDOT ID-PCM7E PC2500 BIOS Configuration: Phoenix Technologies, LTD 6.00 PG 09/26/2006 Processor Sockets Version Location Tag -- PC2500 Socket 370 Memory Device Sockets TypeStatus Set Device Locator Bank Locator --- -- --- --- unknown in use 0 A0 Bank0/1 unknown empty 0 A1 Bank2/3 On-Board Devices = Upgradeable Slots ID StatusType Description --- - 1 available PCI PCI0 2 available PCI PCI1 0 in usePCI PCI2 0 in usePCI PCI3 8 in useAGP AGP Bill ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blastwave.org - any info?
Ian Collins wrote: > Matthew Snyder wrote: >> A little off topic, but I figure you guys use the site and I see Dennis >> around here often, so.. >> >> Anyone know whats up with blastwave.org? the notice sounds legal; >> probably means no official updates right now. Anyone know anything? >> >> I hope all is ok DC >> > genunix.org has gone down with it. Not good. genunix.org is still available if you use the real IP address, not the new ones the blastwave nameservers started publishing today. (My DNS server is fortunate to still have the old ones cached, but I'm sure that won't last long.) http://204.152.191.100/ -- -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc. - X Window System Engineering ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blastwave.org - any info?
Matthew Snyder wrote: > A little off topic, but I figure you guys use the site and I see Dennis > around here often, so.. > > Anyone know whats up with blastwave.org? the notice sounds legal; > probably means no official updates right now. Anyone know anything? > > I hope all is ok DC > genunix.org has gone down with it. Not good. Ian ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SSH - multiple sessions in one command
I am trying to write a script to move a zone from one host to another in one command. Is there a way that I can do multiple ssh commands but only have to authenticate one time? I want to do several commands with ssh, and a couple file copies with rsync but I don't want to have to enter the password 8 times. Thanks ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [osol-help] OpenSolaris no longer boots after an update
I think I'm in the same boat. However, I'd like to get a minimal solution--which also includes not installing vast amounts of unneeded stuff in the first place. For example, this is not an AMD64 machine, and I can't imagine any good reason for downloading and installing all of that stuff during the upgrade. Right now I just want to get the security updates without destroying the machine and without having to hack my menu.lst hither and yon. (So far I am not favorably impressed by this OS... For example, right now I evidently can't undo my mistake of touching the CC Forums option below. I have some regard for the technical expertise of someone who recommended studying this OS, but otherwise I'd have already tossed it as not nearly ready for prime time. I understand this is supposed to be a high performance server OS--so the servers have already timed out a couple of times on the responses while attempting to write this reply? My impressions are going down from low...) This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blastwave.org - any info?
well. why not just figure? might be some big company having to do with it, hm? and which one likes to screw up all the time, hm? unless some people take there seats in the near future, i see no good coming. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blastwave.org - any info?
On Wed, Aug 6, 2008 at 5:18 PM, Matthew Snyder <[EMAIL PROTECTED]>wrote: > A little off topic, but I figure you guys use the site and I see Dennis > around here often, so.. > > Anyone know whats up with blastwave.org? the notice sounds legal; > probably means no official updates right now. Anyone know anything? > > I hope all is ok DC > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > Hope all is well also... it has been a great resource for me while learning Solaris. Guess I'll create a local mirror before any of the mirrors remove anything, be terrible to lose that stuff. -- Brent Jones [EMAIL PROTECTED] ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] blastwave.org - any info?
A little off topic, but I figure you guys use the site and I see Dennis around here often, so.. Anyone know whats up with blastwave.org? the notice sounds legal; probably means no official updates right now. Anyone know anything? I hope all is ok DC ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Can Solaris be discussed here?
Glen Gunselman wrote: > Ian, > > I tried usenet a few years back. > > If you ask a question that they feel is too simple - they insult you. > If you ask a question that they feel requires more sys admin experience than > you have - they insult your company. > If you ask a question that's too complex - they insult you. > > It's a great place to be insulted. > > Then I suggest you try again. comp.unix.solaris is a pretty friendly place. Ian. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Can Solaris be discussed here?
James, I do understand that the OpenSolaris Discussions and the Sun Develorper Network (SDN) Sun forums are software development lists and that I am at a real disadvantage because I'm a system admin - not a software developer. I did ask a question some time back about Blastwave but it was about using Blastwave with Solaris 9. The first reply that I received said that these discussions were not for Solaris. I did receive other replies and some help, but that was some time ago. Thanks, Glen >>> James Carlson <[EMAIL PROTECTED]> 8/6/2008 12:04 PM >>> Glen Gunselman writes: > I can't offer any help with reporting Solaris bugs but I will sympathize with > you. I have only been working/supporting Solaris for about 3 1/2 years. I > have not personally experienced the "golden age of Solaris support" but from > searching the forms (over the last 3 years) it appears (to me) that there was > a time when one could expect a question to be expertly answered, but no more. > Many, if not most, of the questions that I posted to the forums go no where. > Sometimes I get a response but only after a few weeks - not very helpful. > (Sometimes I do get/find useful information, but it's not a resource that I > can count on.) That's something to discuss with the owner of the forum, I'd expect. > There was a time when it seemed opensolaris was interested in Solaris but > after reading this thread, I would say that's no longer true. I'm not sure what that comment was intended to mean. I think folks working on OpenSolaris are indeed very interested in Solaris ... otherwise, we wouldn't be here. At a guess, I suspect you mean that Solaris questions aren't "welcome" here. I don't think that's entirely true -- they're just potentially misplaced and confusing. If you're running a commercial release of Solaris, then you should be pursuing support through the vendor. That's what commercial releases are all about: paid support. If you come here, the support you'll get may end up being hit-or-miss, because we don't have access to Sun's customer records, don't know what other issues might be relevant to you, and few have an obligation to reply (i.e., it's a volunteer effort). The folks in support *do* know those things and aren't just volunteers. I think it would be bad for Sun and for customers if those customers came to the opensolaris.org mailing lists expecting the same level of contracted support for which they're paying, end up not getting that support (or worse, a wrong answer from someone with an @sun.com address), and then blame "Sun" for the disconnect. In addition to that, you need to know that S10 and older releases are not the same as the current OpenSolaris code. It's been 3+ years since S10 released, and things have changed. Sure, _some_ things are the same, but talking about problems in an old release can sometimes get confusing, particularly where the bits being discussed have long since been redesigned or outright removed. If you do fully understand that these are software development lists, and that even the @sun.com people here are *NOT* necessarily the support folks paid to do that job (and thus pretty much like all those with [EMAIL PROTECTED] addresses), and the answers might not apply to the release you happen to be running, then go ahead and ask here. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Can Solaris be discussed here?
Sorry - I haven't worked in support since 1995, and don't know what's involved in contracts or service any more. When I was there, anyone answering the phones could create a bug report for any customer who found a legitamate problem - I don't know if/when/why/how that's changed since. Sounds like something you need to escalate to the service manager or whoever sold you the service contract. -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc. - X Window System Engineering Glen Gunselman wrote: > Alan, > > You must be thinking about times past. In the past year to 18 months, using > GOLD support contract, after support could not help me with a problem (this > has happened more the once - I don't remember which time I pushed) I > suggested filing a bug report. I was told that neither they nor I could > create bug reports. Creating bug reports required some one farther up the > chain. > > If there is a support contract level that includes the right to create a > Solaris bug report, please tell us. > > have a good day, > Glen > >> The way to report bugs in Solaris 10 has been the >> same since the >> day it was released, and the same as the way it has >> been for all >> prior releases of Solaris as long as I can remember - >> via your >> support contract by opening a service call either >> directly or via >> sunsolve.sun.com.(If you were to, by mistake, >> file it on >> http://bugs.opensolaris.org/ it would go to the right >> place in the >> end, but without a support contract customer >> reporting & escalating >> it, it's unlikely to be fixed in a patch for an >> existing release.) >> >> As for the forums, like most Sun engineers I suspect, >> I don't have >> time to monitor many different forum sites, and never >> really got >> involved in those forums - and while you may be >> viewing these as >> web forums, they're gatewayed to mailing lists, so >> show up in my >> inbox and are thus much easier to participate in. >> >> -- >> -Alan Coopersmith- >> - [EMAIL PROTECTED] >> Sun Microsystems, Inc. - X Window System >> em Engineering >> >> ___ >> opensolaris-discuss mailing list >> opensolaris-discuss@opensolaris.org > > > This message posted from opensolaris.org > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Minimal Install of OpenSolaris 2008.05
After finding this thread I am somewhat disappointed. The main reason I am looking for a minimal install would be for Xen DomU images, where only CLI access would be needed, and only specific minimal services would be run, such as a web server, db server, or single application. If there is even some way for me to do this myself, that would be great. I am currently just assessing opensolaris, so I wouldn't be sure where to start. I have spent some time looking at documentation for IPS and Caiman projects, but nothing popped out to me on how to accomplish this. Any pointers in the right direction would be greatly appreciated. Thanks, Zak This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Can Solaris be discussed here?
Ian, I tried usenet a few years back. If you ask a question that they feel is too simple - they insult you. If you ask a question that they feel requires more sys admin experience than you have - they insult your company. If you ask a question that's too complex - they insult you. It's a great place to be insulted. I did learn a thing or two from their ancient FAQ (but I had to ask the FAQ maintainer to explain some of the (really old) terms so that I could use it). have a good day, Glen > If you have a Solaris question, use Usenet or your > support channel. > > Ian > > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Can Solaris be discussed here?
Glen Gunselman writes: > I can't offer any help with reporting Solaris bugs but I will sympathize with > you. I have only been working/supporting Solaris for about 3 1/2 years. I > have not personally experienced the "golden age of Solaris support" but from > searching the forms (over the last 3 years) it appears (to me) that there was > a time when one could expect a question to be expertly answered, but no more. > Many, if not most, of the questions that I posted to the forums go no where. > Sometimes I get a response but only after a few weeks - not very helpful. > (Sometimes I do get/find useful information, but it's not a resource that I > can count on.) That's something to discuss with the owner of the forum, I'd expect. > There was a time when it seemed opensolaris was interested in Solaris but > after reading this thread, I would say that's no longer true. I'm not sure what that comment was intended to mean. I think folks working on OpenSolaris are indeed very interested in Solaris ... otherwise, we wouldn't be here. At a guess, I suspect you mean that Solaris questions aren't "welcome" here. I don't think that's entirely true -- they're just potentially misplaced and confusing. If you're running a commercial release of Solaris, then you should be pursuing support through the vendor. That's what commercial releases are all about: paid support. If you come here, the support you'll get may end up being hit-or-miss, because we don't have access to Sun's customer records, don't know what other issues might be relevant to you, and few have an obligation to reply (i.e., it's a volunteer effort). The folks in support *do* know those things and aren't just volunteers. I think it would be bad for Sun and for customers if those customers came to the opensolaris.org mailing lists expecting the same level of contracted support for which they're paying, end up not getting that support (or worse, a wrong answer from someone with an @sun.com address), and then blame "Sun" for the disconnect. In addition to that, you need to know that S10 and older releases are not the same as the current OpenSolaris code. It's been 3+ years since S10 released, and things have changed. Sure, _some_ things are the same, but talking about problems in an old release can sometimes get confusing, particularly where the bits being discussed have long since been redesigned or outright removed. If you do fully understand that these are software development lists, and that even the @sun.com people here are *NOT* necessarily the support folks paid to do that job (and thus pretty much like all those with [EMAIL PROTECTED] addresses), and the answers might not apply to the release you happen to be running, then go ahead and ask here. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Can Solaris be discussed here?
Alan, You must be thinking about times past. In the past year to 18 months, using GOLD support contract, after support could not help me with a problem (this has happened more the once - I don't remember which time I pushed) I suggested filing a bug report. I was told that neither they nor I could create bug reports. Creating bug reports required some one farther up the chain. If there is a support contract level that includes the right to create a Solaris bug report, please tell us. have a good day, Glen > The way to report bugs in Solaris 10 has been the > same since the > day it was released, and the same as the way it has > been for all > prior releases of Solaris as long as I can remember - > via your > support contract by opening a service call either > directly or via > sunsolve.sun.com.(If you were to, by mistake, > file it on > http://bugs.opensolaris.org/ it would go to the right > place in the > end, but without a support contract customer > reporting & escalating > it, it's unlikely to be fixed in a patch for an > existing release.) > > As for the forums, like most Sun engineers I suspect, > I don't have > time to monitor many different forum sites, and never > really got > involved in those forums - and while you may be > viewing these as > web forums, they're gatewayed to mailing lists, so > show up in my > inbox and are thus much easier to participate in. > > -- > -Alan Coopersmith- > - [EMAIL PROTECTED] > Sun Microsystems, Inc. - X Window System > em Engineering > > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Can Solaris be discussed here?
hzmonte, I can't offer any help with reporting Solaris bugs but I will sympathize with you. I have only been working/supporting Solaris for about 3 1/2 years. I have not personally experienced the "golden age of Solaris support" but from searching the forms (over the last 3 years) it appears (to me) that there was a time when one could expect a question to be expertly answered, but no more. Many, if not most, of the questions that I posted to the forums go no where. Sometimes I get a response but only after a few weeks - not very helpful. (Sometimes I do get/find useful information, but it's not a resource that I can count on.) There was a time when it seemed opensolaris was interested in Solaris but after reading this thread, I would say that's no longer true. have a good day, Glen (sysglen on the SDN forums) This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] BIND update?
Milan Jurik wrote: > Hi Kyle, > > V st, 06. 08. 2008 v 17:50, Kyle McDonald píše: > >> Hi all, >> >> Where can I look to be able to tell if NV will be , or has been, updated >> with a version of BIND that has the latest exploit patches installed? >> >> > > To Sun Alert or blogs.sun.com/security > > I didn't realize that Sun's Security Alerts covered NV. Cool. >> While NV policy is "production code all the time", I understand that >> it's still not totally considered production environment, and therefore >> integrating these patches might not be a high priority. >> >> I'm just looking to guage if/when I should go compile it from source - >> Actually I've already started that. >> >> > > Isn't Bind 9.3.5-P1 part of build 95? > 95. That was what I was looking for. Thanks! > If all will go well, I will integrate improved 9.3.5-P2 in the next > days, probably for build 97. > That will be even better! Cool! -Kyle ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] BIND update?
Hi Kyle, V st, 06. 08. 2008 v 17:50, Kyle McDonald píše: > Hi all, > > Where can I look to be able to tell if NV will be , or has been, updated > with a version of BIND that has the latest exploit patches installed? > To Sun Alert or blogs.sun.com/security > While NV policy is "production code all the time", I understand that > it's still not totally considered production environment, and therefore > integrating these patches might not be a high priority. > > I'm just looking to guage if/when I should go compile it from source - > Actually I've already started that. > Isn't Bind 9.3.5-P1 part of build 95? If all will go well, I will integrate improved 9.3.5-P2 in the next days, probably for build 97. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] BIND update?
Hi all, Where can I look to be able to tell if NV will be , or has been, updated with a version of BIND that has the latest exploit patches installed? While NV policy is "production code all the time", I understand that it's still not totally considered production environment, and therefore integrating these patches might not be a high priority. I'm just looking to guage if/when I should go compile it from source - Actually I've already started that. -Kyle ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Marvell Ethernet cards
Rob McMahon writes: > The myk driver starts to work, but appears to give up sending after a > while, around 30Kb :-) I'd like to re-compile for GLDv3, but can't > because of a missing , does anyone know where this might live > ? It's not packaged; it's currently a private part of the implementation because it's not stable enough for anything else to use safely. You can find it in the ON source tree (usr/src/uts/common/sys/mac.h). > `pkg search -r sys/mac.h' (on another machine, already upgraded to > nv94, and with ss-dev installed) comes up with a bunch of packages, but > none of the un-installed ones look relevant. Is it one of the headers > that isn't opened yet ? No, it's definitely open source. It's just not packaged. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Marvell Ethernet cards
frank Che wrote: > Have you tried the 'myk' driver from > http://homepage2.nifty.com/mrym3/taiyodo/eng/index.html ? Thanks for this pointer. In summary, both the yukonx driver and the skge driver crash in the attach routine with a NULL pointer dereference. This is annoyingly difficult to get around with the lack of any failsafe boot mode. (Boot from CD, zpool import, mount, remove driver, ...) The myk driver starts to work, but appears to give up sending after a while, around 30Kb :-) I'd like to re-compile for GLDv3, but can't because of a missing , does anyone know where this might live ? `pkg search -r sys/mac.h' (on another machine, already upgraded to nv94, and with ss-dev installed) comes up with a bunch of packages, but none of the un-installed ones look relevant. Is it one of the headers that isn't opened yet ? Looks like I'm back to wireless for now, I'll try upgrading to nv94 first (failed last time), and retry the myk driver, which looks the most solid. At least it doesn't stop the machine from booting. >> >> I've just got a new laptop, a Toshiba Satellite Pro P300, and I was >> kind of hoping to install OpenSolaris on it dual boot with Windows. >> I've successfully installed OS2008-05 on it, and it's doing pretty >> well, but doesn't recognize the ethernet card. This presents itself >> as a >> >> Marvell Technology Group Ltd >> 0x11ab 0x436c >> >> to scanpci. From the Marvell site, I downloaded and installed the >> yukonx driver, which caused the machine to crash on reboot (NULL >> pointer dereference in the attach routine). I've just tried the skge >> driver from http://www.skd.de/e_en, and the machine has hung solidly >> after doing >> >> update_drv -a -i '"pci11ab,436c"' skge Rob -- E-Mail: [EMAIL PROTECTED] PHONE: +44 24 7652 3037 Rob McMahon, IT Services, Warwick University, Coventry, CV4 7AL, England ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] opensolaris.com : opensolaris.org
john kroll writes: > Thanks for your reply as a geekwanttobe I've been trying to follow Sun's > progression. Could you better explain? Originally the software compiled to > binaries with sun's compilers were incorporated into distro's by another > party belenix,martux_mbe,nexentaos,schillix, of course not in that order but > done just the same. That's still true. There's just now another binary distribution (in addition to the ones you mentioned), that's made by Sun and that calls itself "OpenSolaris" and uses "opensolaris.com" as a web site. > Now 2008.05 is its own distro indiana cross? 2008.05 is one release of that OpenSolaris distribution, and was produced by the Indiana project. > All of this is real confusing to a newbe but to me the core difference lie in > what is compiled with a sun compiler and what is compiled with gnu. No, that never had anything to do with it. The Solaris product has always been built with a number of different compilers, including both Sun's C compiler and GNU's gcc -- even going way back in time to Solaris 10, 9, 8, and earlier. That's still true. The core difference is in distribution rules. The OpenSolaris distribution is (unlike Solaris) freely redistributable. You can give it away yourself if you want. The regular Solaris product (including Solaris Express) includes licensed components that can't be redistributed. They can be given away free, but each copy requires a license to use and distribute. That's why there's a click-through license for downloading Solaris. The OpenSolaris distribution doesn't include those parts. > The subsequent userland of the server and software. >Sun actually gets even more complicated in that it has compiled software > available in separate directory usr/sfw which is not in root path environment > but ties to applications delivered. Could you give any clarity to any of > these points?? I realize my interpretation is not correct. /usr/sfw has nothing to do with any of the above. That was once a place where we installed some software that derived from open source. It's now obsolete. The new rules (for Solaris and OpenSolaris) are to place things where they naturally belong -- which means /usr/bin for most applications. (Obviously, other distributions based on the OpenSolaris source code can do as they see fit, but I'd expect most to follow suit.) Basically, /usr/sfw was a mistake. When we realized that, we fixed it. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] No /etc/X11/xorg.conf
Thanks to all, I solved the problem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] opensolaris.com : opensolaris.org
Dear Mr. Foster, Thanks for your reply as a geekwanttobe I've been trying to follow Sun's progression. Could you better explain? Originally the software compiled to binaries with sun's compilers were incorporated into distro's by another party belenix,martux_mbe,nexentaos,schillix, of course not in that order but done just the same. Now 2008.05 is its own distro indiana cross? All of this is real confusing to a newbe but to me the core difference lie in what is compiled with a sun compiler and what is compiled with gnu. The subsequent userland of the server and software. Sun actually gets even more complicated in that it has compiled software available in separate directory usr/sfw which is not in root path environment but ties to applications delivered. Could you give any clarity to any of these points?? I realize my interpretation is not correct. john This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] No /etc/X11/xorg.conf
[...] > I am not sure whether it will be at all possible > to run multiple > orgs on each VT. > Does the VT design incorporate this kind of a > behavior ? This will be like > providing multiple virtual display framebuffers. Don't know how VT will do this, but IIRC, SCO Unix could do it, years ago. I think their virtual consoles included a mechanism whereby a process (the X server, in this case) could register to be informed (via signals?) when a switch to/from the console was attempted, and/or a process (that caught the key sequences the would switch in console mode) could trigger the switch themselves. The X server would keep enough state for the frame buffer that it could release it and reaquire it later. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] opensolaris.com : opensolaris.org
On 6/08/2008, at 8:47 PM, john kroll wrote: > Can anyone explain differences or need for both?? I'm guessing .com > is 2008.05 only. I already have an account with sun and > opensolaris.org, I'm experimenting with 2008.05 also should I start > a third account with opensolaris.com. opensolaris.com is the website around the binary distribution, OpenSolaris 2008.05. As that website starts to mature, it will develop more and more content related to learning about the technology, and using it (along with a bunch of different media like podcasts, video streams, blogs, etc..). To contribute on the user forums, you'll need to register (or use your existing sun.com account if you have one). opensolaris.org is the website around developing OpenSolaris technology (whether kernel, X, desktop, or otherwise), the processes involved with writing code and contributing it to the various source code repositories. You can contribute on the mailing lists (mailman) without registering, but if you want to use the online forums you'll need to register. Registration is also required to commit code, or edit the web pages. Glynn ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] problem upgrading opensolaris snv93 -> snv_94
well, version dos not really matter here. Simply all the distros I use enable by default root ssh login (and I am used to use it) tom This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] problem upgrading opensolaris snv93 -> snv_94
> but on > all the other (linux) hosts Since there are at least several thousand various Linux distros, I have learned to always specify which distro, and what version number, etc., when mentioning Linux. Otherwise, it can be very confusing. :-) This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] opensolaris.com : opensolaris.org
Can anyone explain differences or need for both?? I'm guessing .com is 2008.05 only. I already have an account with sun and opensolaris.org, I'm experimenting with 2008.05 also should I start a third account with opensolaris.com. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] problem upgrading opensolaris snv93 -> snv_94
it is not just to login, but to allow some automatic scripts running via ssh... I know I could do it also as a normal user, but on all the other (linux) hosts I do as root and I wanted to be consistent. tom This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] some command can't be used in chroot, what is the reason.
Seems like this line is being a problem:
> open("/proc/self/auxv", O_RDONLY) Err#2 ENOENT
Do you have procfs mounted under chroot environment?
Milan Cermak
wan_jm wrote:
> when using chroot, I found that sort, and add_drv can't be used in chroot.
>
> bash-3.00# chroot /secroot /usr/sbin/add_drv
> /usr/sbin/add_drv: getexecname() failed
> bash-3.00# chroot /secroot /usr/bin/sort
> /usr/bin/sort: getexecname() failed
>
> following is the turss message. what is the reason. could someone help me.
> bash-3.00# truss chroot /secroot /usr/bin/sort
> execve("/usr/sbin/chroot", 0xFFBFFE04, 0xFFBFFE14) argc = 3
> resolvepath("/usr/lib/ld.so.1", "/lib/ld.so.1", 1023) = 12
> resolvepath("/usr/sbin/chroot", "/usr/sbin/chroot", 1023) = 16
> stat("/usr/sbin/chroot", 0xFFBFFBE0)= 0
> open("/var/ld/ld.config", O_RDONLY) Err#2 ENOENT
> stat("/lib/libc.so.1", 0xFFBFF698) = 0
> resolvepath("/lib/libc.so.1", "/lib/libc.so.1", 1023) = 14
> open("/lib/libc.so.1", O_RDONLY)= 3
> mmap(0x0001, 32768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_ALIGN, 3, 0) =
> 0xFF3A
> mmap(0x0001, 1015808, PROT_NONE,
> MAP_PRIVATE|MAP_NORESERVE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFF28
> mmap(0xFF28, 905509, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_TEXT,
> 3, 0) = 0xFF28
> mmap(0xFF36E000, 32401, PROT_READ|PROT_WRITE|PROT_EXEC,
> MAP_PRIVATE|MAP_FIXED|MAP_INITDATA, 3, 909312) = 0xFF36E000
> mmap(0xFF376000, 6368, PROT_READ|PROT_WRITE|PROT_EXEC,
> MAP_PRIVATE|MAP_FIXED|MAP_ANON, -1, 0) = 0xFF376000
> munmap(0xFF35E000, 65536) = 0
> memcntl(0xFF28, 144084, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
> close(3)= 0
> mmap(0x0001, 24576, PROT_READ|PROT_WRITE|PROT_EXEC,
> MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFF39
> munmap(0xFF3A, 32768) = 0
> getcontext(0xFFBFF8D0)
> getrlimit(RLIMIT_STACK, 0xFFBFF8B0) = 0
> getpid()= 22824 [22823]
> setustack(0xFF392A88)
> chroot("/secroot") = 0
> chdir("/") = 0
> execve("/usr/bin/sort", 0xFFBFFE0C, 0xFFBFFE14) argc = 1
> resolvepath("/usr/lib/ld.so.1", "/lib/ld.so.1", 1023) = 12
> resolvepath("/usr/bin/sort", "/usr/bin/sort", 1023) = 13
> stat("/usr/bin/sort", 0xFFBFFC00) = 0
> open("/var/ld/ld.config", O_RDONLY) Err#2 ENOENT
> stat("/lib/libc.so.1", 0xFFBFF6B8) = 0
> resolvepath("/lib/libc.so.1", "/lib/libc.so.1", 1023) = 14
> open("/lib/libc.so.1", O_RDONLY)= 3
> mmap(0x0001, 32768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_ALIGN, 3, 0) =
> 0xFF3A
> mmap(0x0001, 1015808, PROT_NONE,
> MAP_PRIVATE|MAP_NORESERVE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFF28
> mmap(0xFF28, 905509, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_TEXT,
> 3, 0) = 0xFF28
> mmap(0xFF36E000, 32401, PROT_READ|PROT_WRITE|PROT_EXEC,
> MAP_PRIVATE|MAP_FIXED|MAP_INITDATA, 3, 909312) = 0xFF36E000
> mmap(0xFF376000, 6368, PROT_READ|PROT_WRITE|PROT_EXEC,
> MAP_PRIVATE|MAP_FIXED|MAP_ANON, -1, 0) = 0xFF376000
> munmap(0xFF35E000, 65536) = 0
> memcntl(0xFF28, 144084, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
> close(3)= 0
> mmap(0x0001, 24576, PROT_READ|PROT_WRITE|PROT_EXEC,
> MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFF39
> munmap(0xFF3A, 32768) = 0
> getcontext(0xFFBFF8F0)
> getrlimit(RLIMIT_STACK, 0xFFBFF8D0) = 0
> getpid()= 22824 [22823]
> setustack(0xFF392A88)
> brk(0x00022340) = 0
> brk(0x00024340) = 0
> stat("/platform/SUNW,Netra-440/lib/libc_psr.so.1", 0xFFBFF5A8) = 0
> resolvepath("/platform/SUNW,Netra-440/lib/libc_psr.so.1",
> "/platform/sun4u-us3/lib/libc_psr.so.1", 1023) = 37
> open("/platform/SUNW,Netra-440/lib/libc_psr.so.1", O_RDONLY) = 3
> mmap(0x0001, 32768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_ALIGN, 3, 0) =
> 0xFF3A
> close(3)= 0
> munmap(0xFF3A, 32768) = 0
> sysinfo(SI_ISALIST, "", 1) = 115
> sysinfo(SI_ISALIST, "sparcv9+vis2 sparcv9+vis sparcv9 sparcv8plus+vis2
> sparcv8plus+vis sparcv8plus sparcv8 sparcv8-fsmuld sparcv7 sparc", 115) = 115
> open("/proc/self/auxv", O_RDONLY) Err#2 ENOENT
> fstat64(2, 0xFFBFEE78) = 0
> /usr/bin/sortwrite(2, " / u s r / b i n / s o r".., 13) = 13
> : getexecname() failed
> write(2, " : g e t e x e c n a m".., 23) = 23
> _exit(1)
>
>
> This message posted from opensolaris.org
> ___
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
--
* There is an ancient curse saying: 'Interesting times on you.' *
__
