Re: [osol-discuss] Problem with /bin/sh: pipe discards empty lines.
On Thu, Dec 9, 2010 at 10:37 AM, Karel Gardas wrote: > Hello, > thanks for your reply. I'm trying to reproduce the same error on vanilla > 2010.11 installation and to my surprise I'm not able to. What I need to do is: > > export PATH=/usr/xpg4/bin:$PATH > > and then I'm able to reproduce this error with our testsuite, but I'm not yet > able to simplify it to the simple shell test. Yes, because it's a buffering issue. It will not happen if the application pushes all three lines in one step but it will happen if each line is send+|fflush()|'ed individually. I had fun with that the whole right. > Anyway, one important thing is that if I replace grep with ggrep and so I > don't use grep from /usr/xpg4/bin/grep, but usual GNU grep. The issue is > fixed. The same happen if I use grep from /usr/bin then there is no issue. It > looks like just grep from xpg4 causes this empty line discarding... I can reproduce the issue... fix is under testing, together with the Illumos work for "grep -r" ... Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] AST/ksh93/busybox standard conformance and interface stability... / was: Re: community driven distro...
On Sun, May 23, 2010 at 10:25 AM, Richard L. Hamilton wrote: [snip] > My impression is that a number of the AST tools have picked up the > major options previously unique to the GNU tools, while trying to retain > better standards compliance. Assuming that to be true, I think they'd > be the way to go. The goal for the AST utilities is to conform _strictly_ to the POSIX/SUS standards (now quickly moving towards SUSv4) and add those BSD and GNU extensions which are 1) usefull and 2) do not conflict with the POSIX/SUS standards (e.g. we won't add BSD/GNU options which will cause the utilities to break the POSIX/SUS test suite or specification [1]). >From an ARC point of view the POSIX/SUS APIs (and options) are "Commited" while the non-standard options remain uncommited unless there are more than one (or better: two) implementations out there which implement it identically and the "upgrade" of the interface stability makes sense. [1]=OK, I am lying a tiny bit... we have support for multiple defaults for the utilities which can be toggled via a "secret" switch. This allows (if needed) that one utilitiy can act as replacement for Solaris, GNU and BSD utilties at the same time with one implementation (this saves code space, too (which is one of the major design considerations behind the project, e.g. to be one of the fastest implementations but one of the smallest, too (without sacrifying conformance))). But the default should _ALWAYS_ be "standard conformance by default". Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Slap the troll... / was: Re: This is how Oracle treats open communities and projects. Will OGB intervene?
On Mon, May 10, 2010 at 3:15 PM, Dave Johnson wrote: [snip] > Here is the evidence: > > Evidence 1: > - Project cooperation with ksh project withdrawn > - GNU commands as replacements are the future > > -- Forwarded message -- > From: John Sonnenschein > Date: Fri, Dec 4, 2009 at 6:01 PM > Subject: Re: Removal of some redundant GNU utilities [PSARC/2009/660 > FastTrack timeout 12/10/2009] > To: psarc-...@sun.com > > > After discussions with the OpenSolaris architect and lead, I withdraw > this case. It was premature and will be revised as part of a bigger > project to provide Solaris modernization using GNU utilities for /usr/bin. Nice attempt, unfortunately (for you) the ARC emails are being archived. John Sonnenschein's original posting can be found at http://mail.opensolaris.org/pipermail/opensolaris-arc/2009-December/019530.html (and I and many others archive the emails at home, too) and differs a lot from the "proof" you've posted. The diff between his and your email looks like this: -- snip -- @@ -6,8 +6,8 @@ After discussions with the OpenSolaris architect and lead, I withdraw -this case. It was premature and will be considered as part of a bigger -project to provide Solaris moderization. +this case. It was premature and will be revised as part of a bigger +project to provide Solaris modernization using GNU utilities for /usr/bin. -JohnS -- snip -- Please troll somewhere else. Bye, Roland P.S.: Wearing my hat as ksh93-integration project lead: No, neither the ksh93-integration project nor the POSIX modernisation project are dead (neither am I, I am just trying to get rid of some bacteria and Olga Kryzhanovska is currently leading (and in charge) of the projects). -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] how to use SUNWnetcat to capture network traffic?
>i need to capture traffic between two apps. so you want some network sniffer. not sure if ngrep is available for solaris. >I started with snoop, but as i'm only interested by ascii messages (the apps >use >telnet to communicate), snoop don't do the job well. why not? it probably depends on the commandline switches... >Somebody suggests me to use netcat, something like: >nc -l -p PORT -e PROGRAM >and PROGRAM is: that does not capture traffic BETWEEN two apps. It replaces one of the apps and play the role as a dummy server with no intelligence. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] solaris 32bit broken - so when will it get discontinued ?
>What makes you think a company would necessarily >_have_ a policy on something like that they make it available and i don`t read from sun something like "please don`t use, we don`t support it as good as 64bit" if i would read"made just for your convenience, use at your own risk" somewhere that would be something different. it`s just that i like to know it solaris 32bit is a dead child for sun or not and if it`s having really severe issues or if this is just FUD from single individuals... -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] solaris 32bit broken - so when will it get discontinued ?
thanks for your feedback. actually, it`s also this mail which scares me to use opensolaris 32bit: http://opensolaris.org/jive/message.jspa?messageID=266248 especially this post: - bhorn Posts: 75 From: Menlo Park, CA Registered: 9/5/06 Re: ZFS on 32bit. Posted: Aug 6, 2008 10:59 PM in response to: Thomas Garner To: Communities » zfs » discuss In the most recent code base (both OpenSolaris/Nevada and S10Ux with patches) all the known marvell88sx problems have long ago been dealt with. However, I've said this before. Solaris on 32-bit platforms has problems and is not to be trusted. There are far, far too many places in the source code where a 64-bit object is either loaded or stored without any atomic locking occurring which could result in any number of wrong and bad behaviors. ZFS has some problems of this sort, but so does some of the low level 32-bit x86 code. The problem was reported long ago, but to the best of my knowledge the issues have not been addressed. Looking below it appears that nothing has been done for about 9 months. - furthermore, i have read several times, that 64bit solaris should preferred under all circumstances. that is a user`s opinion, but how does SUN think about that ? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] solaris 32bit broken - so when will it get discontinued ?
Hello, i always wondered about the details why using 32bit solaris is not adviced - i now came across this one: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6634371 Solaris ON is broken w.r.t. 64-bit operations on 32-bit processors as this bugreport is nearly 2 yrs old and in status "dispatched", i`d wonder if issues like this will ever be fixed. so, what about the support status of 32bit solaris then and when is it going to be discontinued? i always thought the problems are "theoretical" or "rare", but looking at issues like this, i won`t spend any minute on trying solaris on 32bit anymore. what i´m wondering a little bit is why it`s still running fine here on two systems. no zfs errors/problems or crashes or whatever -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Broadcom support?
Hi, I was wondering if I would be able to run openSolaris on my Gateway MX6441 AMD Turion 64 Mobile Technology, 798MHz, 448MB DDR laptop with a Broadcom wireless card and ATI graphics. I'm not very technical, but I have been using Ubuntu on my laptop for about 6 months. I would like to put openSolaris on a partition and see if it is for me. However, If I won't be able to get the wireless to work then I really need not try. I mainly use my laptop for just web browsing, OpenOffice applications, and personal e-mail. Cheers! -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [zfs-discuss] Which kind of ACLs does tmpfssupport?
Robert Thurlow wrote: > Roland Mainz wrote: > > > Ok... does that mean that I have to create a ZFS filesystem to actually > > test ([1]) an application which modifies ZFS/NFSv4 ACLs or are there any > > other options ? > > By all means, test with ZFS. But it's easy to do that: > > # mkfile 64m /zpool.file > # zpool create test /zpool.file > # zfs list > test 67.5K 27.4M18K /test I know... but AFAIK this requires "root" priviledges which the test suite won't have... Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [zfs-discuss] Which kind of ACLs does tmpfssupport?
Ian Collins wrote: > Roland Mainz wrote: > > Norm Jacobs wrote: > >> Roland Mainz wrote: > >>> Does anyone know out-of-the-head whether tmpfs supports ACLs - and if > >>> "yes" - which type(s) of ACLs (e.g. NFSv4/ZFS, old POSIX draft ACLs > >>> etc.) are supported by tmpfs ? > >>> > >> I have some vague recollection that tmpfs doesn't support ACLs snd it > >> appears to be so... > > > > Is there any RFE which requests the implementation of NFSv4-like ACLs > > for tmpfs yet ? > > > >> ZFS > >> > >> opensolaris% touch /var/tmp/bar > >> opensolaris% chmod A=user:lp:r:deny /var/tmp/bar > >> opensolaris% > >> > >> TMPFS > >> > >> opensolaris% touch /tmp/bar > >> opensolaris% chmod A=user:lp:r:deny /tmp/bar > >> chmod: ERROR: Failed to set ACL: Operation not supported > >> opensolaris% > >> > > > > Ok... does that mean that I have to create a ZFS filesystem to actually > > test ([1]) an application which modifies ZFS/NFSv4 ACLs or are there any > > other options ? > Use function interposition. Umpf... the matching code is linked with -Bdirect ... AFAIK I can't interpose library functions linked with this option, right ? Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Which kind of ACLs does tmpfs support ?
Norm Jacobs wrote: > Roland Mainz wrote: > > Does anyone know out-of-the-head whether tmpfs supports ACLs - and if > > "yes" - which type(s) of ACLs (e.g. NFSv4/ZFS, old POSIX draft ACLs > > etc.) are supported by tmpfs ? > > I have some vague recollection that tmpfs doesn't support ACLs snd it > appears to be so... Is there any RFE which requests the implementation of NFSv4-like ACLs for tmpfs yet ? > ZFS > > opensolaris% touch /var/tmp/bar > opensolaris% chmod A=user:lp:r:deny /var/tmp/bar > opensolaris% > > TMPFS > > opensolaris% touch /tmp/bar > opensolaris% chmod A=user:lp:r:deny /tmp/bar > chmod: ERROR: Failed to set ACL: Operation not supported > opensolaris% Ok... does that mean that I have to create a ZFS filesystem to actually test ([1]) an application which modifies ZFS/NFSv4 ACLs or are there any other options ? [1]=The idea is to have a test module which checks whether ACL operations work correctly, however the testing framework must only run as normal, unpriviledged user... Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Which kind of ACLs does tmpfs support ?
Hi! Does anyone know out-of-the-head whether tmpfs supports ACLs - and if "yes" - which type(s) of ACLs (e.g. NFSv4/ZFS, old POSIX draft ACLs etc.) are supported by tmpfs ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] [Annoucement] ksh93-integration update2 2009-08-22 binaries available for download (for Solaris 11 Nevada >= B110+OpenSolaris/Indiana) ...
nstall >buildlog.log 2>&1 Finally: Please check http://www.opensolaris.org/os/project/ksh93-integration/downloads/2009-08-22/ for any updates or additional comments... Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=2009-08-22 ksh93-integration update2 test binaries: http://www.opensolaris.org/os/project/ksh93-integration/downloads/2009-08-22/ [3]=ksh93s+ manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93s/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=ksh93-integration project bugzilla: http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration Bye, Roland P.S.: Reply-To: is set to ksh93-integration-disc...@opensolaris.org -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_120 on a laptop - no keyboard? (more info)
>The call to drive_present never returns. that sounds like edd - i know sysstems where you need to pass "edd=off" to correctly boot linux. (http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e479c8306f898fcdb9b36179071eae6338a17364) dobiosdev=0 sounds like the solaris equivalent for that. is that correct ? i`m wondering that solaris can get past this bios call, while linux hangs endlessly in those routines and needs "edd=off" to work around that. does someone know details about the difference? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fault tolerance in OpenSolaris xVM
>I am looking for a way to run a fault tolerant virtual machine using >OpenSolaris xVM. you mean "fault tolerance" lilke "VMWare Fault Tolerance" ? >If it is possible, I would like to do it, without a >separate, shared storage. i think xVM cannot do that and especially without shared storage you should forget about that idea entirely -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] (www|hg|svn|wiki).genunix.org down ?
Al Hopper wrote: > On Sat, Jul 11, 2009 at 1:16 AM, Al Hopper > wrote: > > On Sat, Jul 11, 2009 at 12:38 AM, Al Hopper > > wrote: > > > On Fri, Jul 10, 2009 at 7:58 PM, Roland Mainz > > > wrote: > > > > Does anyone know what's wrong with > > > > (www|hg|svn|wiki).genunix.org ? I > > > > can't reach any of these sites since > > > > some time... ;-( [snip] > > It may be tomorrow AM Pacific time before the folks at the > > ISC NOC can resolve this issue. > > Problem resolved around 6:10 AM Pacific. Thanks! :-) > A typo in the (ISC) router > took away our default route. They don't have monitoring scripts which scream "ALARM!" when something breaks ? > Murphys law is alive and well! ;-( Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Any idea why Solaris snv 117 x86 wont see a 1, 5 TB SATA drive
>Before complaining and trashing against the wall, do some research >about the VTOC problematic behind it. thanks. i read about the vtoc problem, but i believe that "there is some way" to work around this or to solve it somehow. not easy ,sure - but i think it`s not ok to say "this is impossible with 32bit solaris kernel" and will never be done. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Any idea why Solaris snv 117 x86 wont see a 1, 5 TB SATA drive
so, we need to trash a working system and replace it just because of the need of adding bigger disks and because inability of software to handle that ? if other 32bit operating systems can handle those without problems, it`s mostly a matter of "good will" to change 32bit solaris apropriately. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Any idea why Solaris snv 117 x86 wont see a 1, 5 TB SATA drive
>The 32-bit Solaris kernel does not support disks > 1TB which is a major annoyance. let 1 or 2 years go by, and disks >1TB will be standard. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Adaptec SAS 2405 - anyone ?
Hello, is anybody using this controller with opensolaris/snv ? http://www.adaptec.com/de-DE/products/Controllers/Hardware/sas/entry/SAS-2405/ does it run out of the box ? how does it perform with zfs? (especially when using it for zfs/nfs esx setup) the driver from adaptec is for solaris 10 u4. If it does not work out of the box, can i use that driver with opensolaris/snv ? thanks roland -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] [Annoucement] ksh93-integration update2 2009-07-02 binaries available for download (for Solaris 11 Nevada >= B110+OpenSolaris/Indiana) ...
.bz2 $ sum -x md5 ksh93_integration_20090702_snapshot_sparc.tar.bz2 7949f49e4f422d6b1490c1b0dfb1789e ksh93_integration_20090702_snapshot_sparc.tar.bz2 # cd / # sync ; sync # bzcat svn_genunix_org_on_branches_ksh93_gisburn_prototype021_rev_b111_1610.diff.txt o ... unified diff (http://www.opensolaris.org/os/project/ksh93-integration/downloads/svn_genunix_org_on_branches_ksh93_gisburn_prototype021_rev_b111_1610.diff.txt , 2.25MB, MD5 checksum is6e33ae16efbeced80ff1beb52afa445b). o ... Mercurial/HG export bundle (http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_update2_20090702_hg_export_001.hgexport.bz2 , 212KB, MD5 checksum is 2a977e5be3b2eaa57d76c9aa8cd9d5c5) + Alternatively webrev pages are available at http://cr.opensolaris.org/~gisburn/ksh93_integration_update2_20090702_webrev/ * "multiline" input mode is now enabled by default in /etc/ksh.kshrc to match input/editor behaviour of bash. * /etc/ksh.kshrc now sets a default prompt (PS1) which contains @:$ for normal users and @:# for user "root"; the prompt length itself is limited to ~~30 characters to ensure it only occupies ~~1/4 of a standard 80x24 terminal window. * was added to emacs/gmacs mode to clear the screen (per community requests and to be in sync with bash) * 64bit binaries and libraries are now included (and used by default if the hardware is 64bit capable) * "shcomp", the shell script compiler is now included as /usr/bin /shcomp. * AST l10n utilities are stored in /usr/ast/bin/. * Starting with ksh93s+ multibyte characters can be used for variable/function/etc.-names. Please test this functionality extensively. * The tarball was created using the build_ksh93_standalone_tarball.sh script which is available in the base directory of the prototype021 tree. Note: The script can only be used after a successfull $ cd usr/ src ; (cd tools ; make install) ; make setup ; \ dmake install #-sequence, otherwise the resulting tarball will be incomplete. * The tarballs do not provide a manual page for ksh93. Please use the manual page for ksh93s+ in the meantime. * The ksh93 binaries can be build from source like this: (Instructions are for Solaris i386/AMD64; SPARC requires minor adjustments) 1. Pull sources and extract closed bin stuff (files can be obtained from opensolaris.org): $ mkdir test_x86 ; cd test_x86 $ svn checkout -r 1610 \ svn://svn.genunix.org/on/branches/ksh93/gisburn/prototype021/usr $ bzcat <../download/on-closed-bins-nd.i386.tar.bz2 | \ tar -xf - $ bzcat <../download/on-closed-bins.i386.tar.bz2 | \ tar -xf - $ cd .. 2. Create opensolaris.sh. This is the usual opensolaris.sh with the paths adjusted to match your location of the sources. Example for the changes applies to opensolaris.sh (for my workspace): --- ./test1_x86/usr/src/tools/env/opensolaris.sh +++ ./opensolaris.sh @@ -43,10 +43,10 @@ # This is a variable for the rest of the script - GATE doesn't # matter to nightly itself -GATE=testws; export GATE +GATE=prototype021; export GATE +# workaround for B111 build issue +export NOT_UNDER_SCM=true # CODEMGR_WS - where is your workspace at (or what should # nightly name it) -CODEMGR_WS="/export/$GATE";export CODEMGR_WS +CODEMGR_WS="/home/test001/ksh93/on_build1/$GATE";export CODEMGR_WS # Location of encumbered binaries. ON_CLOSED_BINS="$CODEMGR_WS/closed"; export ON_CLOSED_BINS 3. Run "bldenv": $ env - SHELL=$SHELL TERM=$TERM HOME=$HOME LOGNAME=$LOGNAME \ DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY LANG=C LC_ALL=C \ PAGER=less MANPATH=$MANPATH /opt/onbld/bin/bldenv \ opensolaris.sh # 4. Build it (the quick way): $ cd prototype021/usr/src $ export CW_NO_SHADOW=1 $ time nice make setup 2>&1 | tee -a buildlog_setup.log $ time nice dmake install >buildlog.log 2>&1 Finally: Please check http://www.opensolaris.org/os/project/ksh93-integration/downloads/2009-07-02/ for any updates or additional comments... Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=2009-07-02 ksh93-integration update2 test binaries: http://www.opensolaris.org/os/project/ksh93-integration/downloads/2009-07-02/ [3]=ksh93s+ manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93s/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=ksh93-integration project bugzilla: http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration Bye, Roland P.S.: Reply-To: is set to ksh93-integration-disc...@opensolaris.org -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] no keyboard with snv_112
I`m trying to install snv_112 on an older FSC Server (RX200), but the keyboard (ps/2) does not work. it works in the bios and at the boot screen, but when solaris kernel starts, i have no keyboard - so i cannot even install. (no install type selection etc.) what can i do to debug this ? regards roland -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] OpenSolaris 0609 srss 4.1
I would like to know how to install SRSS 4.1 on OpenSolaris 2009.06 june 1 2009. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] [Annoucement] ksh93-integration update2 2009-05-11 binaries available for download (for Solaris 11 Nevada >= B110+OpenSolaris/Indiana) ...
d used by default if the hardware is 64bit capable) * "shcomp", the shell script compiler is now included as /usr/bin/shcomp. * AST l10n utilities are stored in /usr/ast/bin/. * Starting with ksh93s+ multibyte characters can be used for variable/function/etc.-names. Please test this functionality extensively. * The tarball was created using the build_ksh93_standalone_tarball.sh script which is available in the base directory of the prototype021 tree. Note: The script can only be used after a successfull $ cd usr/src ; (cd tools ; make install) ; make setup ; dmake install #-sequence, otherwise the resulting tarball will be incomplete. * The tarballs do not provide a manual page for ksh93. Please use the manual page for ksh93s+ in the meantime. * The ksh93 binaries can be build from source like this: (Instructions are for Solaris i386/AMD64; SPARC requires minor adjustments) 1. Pull sources and extract closed bin stuff (files can be obtained from opensolaris.org): $ mkdir test_x86 ; cd test_x86 $ svn checkout -r 1532 \ svn://svn.genunix.org/on/branches/ksh93/gisburn/prototype021/usr $ bzcat <../download/on-closed-bins-nd.i386.tar.bz2 | \ tar -xf - $ bzcat <../download/on-closed-bins.i386.tar.bz2 | \ tar -xf - $ cd .. 2. Create opensolaris.sh. This is the usual opensolaris.sh with the paths adjusted to match your location of the sources. Example for the changes applies to opensolaris.sh (for my workspace): --- ./test1_x86/usr/src/tools/env/opensolaris.shThu Sep 14 13:17:59 2006 +++ ./opensolaris.shSun Jul 30 00:50:08 2006 @@ -43,10 +43,10 @@ # This is a variable for the rest of the script - GATE doesn't matter # to nightly itself -GATE=testws; export GATE +GATE=prototype021; export GATE +# workaround for B111 build issue +export NOT_UNDER_SCM=true # CODEMGR_WS - where is your workspace at (or what should nightly # name it) -CODEMGR_WS="/export/$GATE";export CODEMGR_WS +CODEMGR_WS="/home/test001/ksh93/on_build1/$GATE";export CODEMGR_WS # Location of encumbered binaries. ON_CLOSED_BINS="$CODEMGR_WS/closed"; export ON_CLOSED_BINS 3. Run "bldenv": $ env - SHELL=$SHELL TERM=$TERM HOME=$HOME LOGNAME=$LOGNAME DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY LANG=C LC_ALL=C PAGER=less MANPATH=$MANPATH /opt/onbld/bin/bldenv opensolaris.sh # 4. Build it (the quick way): $ cd prototype021/usr/src $ export CW_NO_SHADOW=1 $ time nice make setup 2>&1 | tee -a buildlog_setup.log $ time nice dmake install >buildlog.log 2>&1 Finally: Please check http://www.opensolaris.org/os/project/ksh93-integration/downloads/2009-05-11/ for any updates or additional comments... Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=2009-05-11 ksh93-integration update2 test binaries: http://www.opensolaris.org/os/project/ksh93-integration/downloads/2009-05-11/ [3]=ksh93s+ manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93s/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=ksh93-integration project bugzilla: http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration Bye, Roland P.S.: Reply-To: is set to ksh93-integration-disc...@opensolaris.org -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] [Annoucement] ksh93-integration update2 2009-04-20 binaries available for download (for Solaris 11 Nevada >= B110+OpenSolaris/Indiana) ...
r -xf - $ bzcat <../download/on-closed-bins.i386.tar.bz2 | \ tar -xf - $ cd .. 2. Create opensolaris.sh. This is the usual opensolaris.sh with the paths adjusted to match your location of the sources. Example for the changes applies to opensolaris.sh (for my workspace): --- ./test1_x86/usr/src/tools/env/opensolaris.sh +++ ./opensolaris.shSun Jul 30 00:50:08 2006 @@ -43,10 +43,10 @@ # This is a variable for the rest of the script - GATE # doesn't matter to nightly itself -GATE=testws; export GATE +GATE=prototype021; export GATE +# workaround for B111 build issue +export NOT_UNDER_SCM=true # CODEMGR_WS - where is your workspace at #(or what should nightly name it) -CODEMGR_WS="/export/$GATE"; export CODEMGR_WS +CODEMGR_WS="/home/test001/ksh93/on_build1/$GATE"; export CODEMGR_WS # Location of encumbered binaries. ON_CLOSED_BINS="$CODEMGR_WS/closed";export ON_CLOSED_BINS 3. Run "bldenv": $ env - SHELL=$SHELL TERM=$TERM HOME=$HOME LOGNAME=$LOGNAME DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY LANG=C LC_ALL=C PAGER=less MANPATH=$MANPATH /opt/onbld/bin/bldenv opensolaris.sh # 4. Build it (the quick way): $ cd prototype021/usr/src $ export CW_NO_SHADOW=1 $ time nice make setup 2>&1 | tee -a buildlog_setup.log $ time nice dmake install >buildlog.log 2>&1 Finally: Please check http://www.opensolaris.org/os/project/ksh93-integration/downloads/2009-04-20/ for any updates or additional comments... Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=2009-04-20 ksh93-integration update2 test binaries: http://www.opensolaris.org/os/project/ksh93-integration/downloads/2009-04-20/ [3]=ksh93s+ manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93s/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=ksh93-integration project bugzilla: http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration Bye, Roland P.S.: Reply-To: is set to ksh93-integration-disc...@opensolaris.org -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] how to configure solari express to execute 'rsh' by root ?
it`s not the rsh client which cannot be executed by root, it`s the remote system not letting you do ls as root. you may need to uncomment "CONSOLE=/dev/console" in /etc/default/login on the remote machine. hth roland -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How can i forbid sftp users to change their home directory
have a look at "scponly" ( http://www.sublimation.org/scponly/ ) -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] disconnecting hdd from zfs mirror hangs whole system
thanks - i can "see" it now and finding it by the search phrase, where i got no hit before. seems i was a little bit too impatient. i should better read what`s on screen. sorry for have taken your time ! -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] disconnecting hdd from zfs mirror hangs whole system
i added a bugreport to bugster for this yesterday. unfortunately, i dumped the response mail with the bug-id and now i cannot find my own bugreport anymore. (did somebody delete that?) as this thread is linked from the bugster bugreport, whoever is reading this thread please post the bug id here. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] check io bandwidth
maybe there is a 64 version of bonnie around? anyway - do we really need 64bit fs benchmarking tool? wouldn`t 32bit be ok for that? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] disconnecting hdd from zfs mirror hangs whole system
>Unless you have a chassis that's made for hot plugging, and have a sliding >caddy with physical latch on the front, and a red blinking light to identify >which is the failed disk, and unless you bought a name brand product like >Sun or Dell or HP ... I think you can count on *not* supporting hot plugging >disks. if the specs for a controller chip tell, that it supports hotplugging and if it works with other operating systems, then i count on that. I tested the same system with linux. cd to /some/dir/on/that/disk , unplugged the disk, waited some time for the kernel to set the device faulty and it continued to run without a problem. sure, i`m getting errors on read/writes in that dir (as it`s on a disk which does not exist anymore), but i could cd to another place and the system was useable and responsive for the whole time. no hangs, no stalls. when i reattached the disk, linux was able to detect it and i could re-use it without a reboot. now with solaris - if i unplug the disk (as part of a zfs mirror), the whole system stalls/hangs forever. so, it appears it`s not a hardware problem but a solaris problem. this is from another terminal: vmstat 1 |while read a ;do echo -n `date`;echo $a;done Donnerstag, 2. April 2009, 16:57:38 Uhr CEST0 0 0 3708564 2527308 18 187 0 0 0 0 0 0 0 0 0 360 362 280 0 1 99 Donnerstag, 2. April 2009, 16:57:39 Uhr CEST0 1 0 3707968 2526712 78 461 0 0 0 0 0 1 0 0 0 360 598 283 1 2 97 Donnerstag, 2. April 2009, 16:57:40 Uhr CEST0 1 0 3707944 2526688 18 187 0 0 0 0 0 0 0 0 0 336 286 226 0 1 99 Donnerstag, 2. April 2009, 16:57:41 Uhr CEST0 1 0 3707944 2526688 18 189 0 0 0 0 0 25 0 0 0 443 287 340 0 1 99 Donnerstag, 2. April 2009, 16:57:42 Uhr CEST0 1 0 3707944 2526688 18 185 0 0 0 0 0 0 0 0 0 342 293 237 1 1 98 Donnerstag, 2. April 2009, 16:57:43 Uhr CEST0 1 0 3707944 2526688 18 187 0 0 0 0 0 0 0 0 0 329 350 213 0 1 99 Donnerstag, 2. April 2009, 16:57:44 Uhr CESTkthr memory page disk faults cpu Donnerstag, 2. April 2009, 16:57:44 Uhr CESTr b w swap free re mf pi po fr de sr cd cd cd f0 in sy cs us sy id Donnerstag, 2. April 2009, 16:57:44 Uhr CEST0 1 0 3707944 2526688 18 187 0 0 0 0 0 0 0 0 0 360 283 262 0 1 99 Donnerstag, 2. April 2009, 16:57:45 Uhr CEST0 1 0 3707944 2526688 42 547 0 0 0 0 0 0 0 0 0 350 669 249 1 2 99 ---unplug ---hang. while hanging, cpu usage seems to go up as i hear the cpu fan starts blowing- ---reconnect Donnerstag, 2. April 2009, 17:05:18 Uhr CEST3 1 0 3707944 2526688 0 3 0 0 0 0 0 0 0 0 0 201 5 2 0 99 1 Donnerstag, 2. April 2009, 17:05:18 Uhr CEST4 1 0 3707868 2526612 1 1 0 0 0 0 0 0 0 0 0 201 36 5 0 100 0 Donnerstag, 2. April 2009, 17:05:18 Uhr CEST36 0 0 3707468 2526420 0 0 0 0 0 0 0 0 0 0 0 181 1 1 0 100 0 Donnerstag, 2. April 2009, 17:05:19 Uhr CEST2 0 0 3707312 2526184 49 907 0 0 0 0 0 178 125 138 0 1212 1737 1479 2 60 38 Donnerstag, 2. April 2009, 17:05:20 Uhr CEST0 0 0 3707200 2526080 18 192 0 0 0 0 0 235 102 102 0 1118 882 1712 1 9 90 Donnerstag, 2. April 2009, 17:05:21 Uhr CEST0 0 0 3707736 2526524 18 185 0 0 0 0 0 240 0 0 0 629 552 709 1 4 95 Donnerstag, 2. April 2009, 17:05:22 Uhr CEST0 0 0 3707712 2526500 18 187 0 0 0 0 0 0 0 0 0 330 287 191 0 1 99 Donnerstag, 2. April 2009, 17:05:23 Uhr CEST0 0 0 3707712 2526500 18 187 0 0 0 0 0 0 0 0 0 324 280 181 0 1 99 Donnerstag, 2. April 2009, 17:05:24 Uhr CEST0 0 0 3707712 2526500 18 189 0 0 0 0 0 0 0 0 0 343 345 220 0 1 99 output from demsg: Donnerstag, 2. April 2009, 17:12:56 Uhr CEST Apr 2 16:51:10 zetta pseudo: [ID 129642 kern.info] pseudo-device: profile0 Apr 2 16:51:10 zetta genunix: [ID 936769 kern.info] profile0 is /pseudo/prof...@0 Apr 2 16:51:10 zetta pseudo: [ID 129642 kern.info] pseudo-device: systrace0 Apr 2 16:51:10 zetta genunix: [ID 936769 kern.info] systrace0 is /pseudo/systr...@0 Apr 2 16:51:10 zetta pseudo: [ID 129642 kern.info] pseudo-device: fbt0 Apr 2 16:51:10 zetta genunix: [ID 936769 kern.info] fbt0 is /pseudo/f...@0 Apr 2 16:51:10 zetta pseudo: [ID 129642 kern.info] pseudo-device: sdt0 Apr 2 16:51:10 zetta genunix: [ID 936769 kern.info] sdt0 is /pseudo/s...@0 Apr 2 16:51:10 zetta pseudo: [ID 129642 kern.info] pseudo-device: dcpc0 Apr 2 16:51:10 zetta genunix: [ID 936769 kern.info] dcpc0 is /pseudo/d...@0 Apr 2 16:51:10 zetta pseudo: [ID 129642 kern.info] pseudo-device: ucode0 Apr 2 16:51:10 zetta genunix: [ID 936769 kern.info] ucode0 is /pseudo/uc...@0 Apr 2 16:51:10 zetta pseudo: [ID 129642 kern.info] pseudo-device: fcp0 Apr 2 16:51:10 zetta genunix: [ID 936769 kern.info] fcp0 is /pseudo/f...@0 Apr 2 16:51:10 zetta pseudo: [ID 129642 kern.info] pseudo-device: fcsm0 Apr 2 16:51:10 zetta genunix: [ID 936769 kern.info] fcsm0 is /pseudo/f...@0 Apr 2 16:51:10 zetta pseudo: [ID 129642 kern.info] pseudo-device: ncall0 Apr 2 16:51:10 zetta genunix: [ID 936769 kern.info] ncall0 is /pseudo/nc...@0 Apr 2 16:51:10 zetta pseudo: [ID 129642 kern.info] pseudo-device: nsctl0 Apr 2 16:51:10 zetta genunix: [ID 936769 kern.info]
Re: [osol-discuss] disconnecting hdd from zfs mirror hangs whole system
>Original Poster: can you please take a look at cfgadm? Seems like sil >believes disk is still there or gone mad, maybe it cam be solved by >switching it off or marking unconfigured. i can take a look at the end of the week and will report. anyway - how can this be solved by switching it of or marking unconfigured? i want to run a raidz with this controller with 4 disks and unplugging one disk for testing it for reliability. if this simple test doesn`t even work, the whole thing will never go into production, as a raid which stalls the system on unpluggig a single disk is completely crap and useless -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] VMware Tools on ESXi for OpenSolaris
check out http://open-vm-tools.sourceforge.net/ if you have problems installing the tools that come with esxi -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] disconnecting hdd from zfs mirror hangs whole system
thanks for the hint - i thought sata would be always hot-pluggable. i checked the specs for 3114 and they tell it supports hot-plug: http://www.siliconimage.com/products/product.aspx?pid=28 i think i will try how a raid mirror behaves with linux, just to see if there is a difference. roland -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] disconnecting hdd from zfs mirror hangs whole system
hello, i`m using a sil3114 sata controller with a zfs configured as mirror. if i disconnect one of the drives, the whole system stalls until i reconnect the drive. i cannot even login via network anymore. this lasts at least for some minutes (don`t know if it cures itself after a while), but if i reconnect the drive, all is well again at once. that`s not the expected behaviour from a raid configuration, imho. hints ? regards roland ps: can post some information from the logs very soon. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Emancipation vs. "POSIX commands community" vs. closed-bin stuff.. / was: Re: [on-discuss] Emergency project to rescueOpensolaris fr
Miles Nordin wrote: > > You wish to talk to Roland Mainz, Glenn Fowler and > > Jennifer Pioch > > then. They have opensource replacements for > > /usr/bin/sed, > > /usr/xpg4/bin/sed, /usr/bin/tail, /usr/xpg4/bin/tail, > > /usr/bin/tr and > > /usr/xpg4/bin/tr. > > is this a joke? No, this is no joke. I am in the process of updating my bulid machines and then I make a Subversion tree which includes code for getting an opensource replacement for "tail" (both /usr/bin/tail and /usr/xpg4/bin/tail) and later "sed" (both /usr/bin/tail and /usr/xpg4/bin/tail), (/usr/bin/|/usr/xpg4/bin/|/usr/xpg6/bin/)tr and /usr/bin/pax. Basically we're now quickly getting rid of all closed-source POSIX commands (as part of the upcoming "POSIX commands community"). > Wherever could they find such precious and novel work? > maybe, from the GNU project, fifteen years ago? No, the work is based on the AT&T AST codebase - the same stuff where ksh93 comes from. > oh, o sorry my mistake they want *XPG4* versions. seriously, WHO CARES? We > are talking about this source: > > http://opensolaris.org/os/about/no_source/ Right... as said I try to push the matching source code as fast as possible... Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Please stop this flamewar... / was: Re: [ksh93-integration-discuss] General THANKLESS- and RESPECTLESSnesstowards Joerg Schilling (and others, which I leave out of this msg.) __/__ Was:
Martin Bochnig wrote: > On Wed, Mar 25, 2009 at 5:25 PM, Josh Hurst wrote: > > On 3/25/09, Dennis Clarke wrote: [snip] > Flame wars should be fought privately, if at all. * First: I would _STRONGLY_ prefer to keep all non-technical issues (including politics, license discussions, personal issues with other people+their opinions or flamewars) out of the... 1) ksh93-integration-disc...@opensolaris.org 2) shell-disc...@opensolaris.org 3) busybox-...@opensolaris.org ... mailinglists (and (not speaking for John Beck) I guess the same applies to "on-disc...@opensolaris.org", too). These three lists are technical lists _ONLY_ and the current discussion is IMO completely out-of-control, completely off-topic and offensive in several ways. * Second: I request that all involved parties check the use of their language and avoid the use of "vulgar" vocabulary (German users: If you are unsure check http://dict.leo.org/ , they mark matching vocables with a "[vulg.]"-tag). The next person caught here using such vocabular will get a more definite email. Bye, Roland P.S.: Setting reply-to: opensolaris-discuss@opensolaris.org -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Using |mmap()| for Xorg pixmap allocations... / was: Re: [desktop-discuss] Poor interactive performanceunder heavy system load
Alan Coopersmith wrote: > Joerg Schilling wrote: > > Another issue: Xsun did use mmap() to allocate bigger parts of memory in the > > X server. If big memory leaking program like netscape died in former times, > > Xsun did shrink. Today, we have firefox that itself allocates less memory > > than > > before but rather forxes X to allocate more memory and Xorg is malloc() > > based > > and this does not shrink when fireforx dies... > > We had to turn down Xsun's use of mmap() because it caused performance > problems > when programs like Netscape or the GNOME desktop had allocated hundreds of > pixmaps per session, and you had dozens of sessions running on a Sun Ray > server > leading to TLB thrashing for all those new page mapping entries, especially on > the UltraSPARC CPU's with small TLBs. Right - but that was a problem of not limiting the minimum amount for |mmap()|'ed pixmaps. AFAIK later this was changed to 1MB which is far too large to be usefull (as suggested in the original thread I suggested AFAIK a size of 8*pagesize as minimum threshhold to get a good balance between extra overhead, TLB usage (on UltraSPARC-2 CPUs) and pixmap create/destroy performance) except for large double-buffer pixmaps as used by Mozilla/FireFox/Seamonkey/etc. > There were also performance issues with > pixmap allocation & deallocation becoming much more expensive, since > mmap/mmunmap are far more expensive calls than malloc/free. (See for > instance, > the GNOME stock ticker issue described in the original DTrace Usenix paper, > and http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=4757131 ) > > Even so, we've looked at porting those changes to Xorg before, and I released > the Xsun code to Roland at one point when he volunteered to port it, but have > never gotten it done. If I recall it correctly the code was working except if something starts to use MIT-SHM - AFAIK this turned the simple patch into a compliciated mess which required to change the Xorg ABI and that was a "no go" during that time. BTW: A simpler and faster solution may be to let Xorg use the libast allocator using the |mmap()| backend since it "bundles" smaller allocation into larger |mmap()| ones (again 8*pagesize but this is a tuneable) and avoids long-term memory fragmentation (better than the libc code) which helps a _lot_ with Xorg. Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [ksh93-integration-discuss] [tools-discuss] ksh93 sleep
Hi! Irek: I'm setting the Reply-To: to opensolaris-discuss@opensolaris.org ... I would be really nice to keep the "stone throwing" out of the ksh93-integration-disc...@opensolars.org list - we're trying to get technical stuff done in this list and not rant about the history of Solaris or throw slime around (or do flamewars, license discussions (like "CDDL/CPL are evil, GPL is the only true choice" etc.) etc.). "I. Szczesniak" wrote: > On 2/18/09, Peter Memishian wrote: > > > > > Reverse course and restore Sun's innovation-unfriendly attitude? Sun > > > really has become what I consider the executor of the System V legacy, > > > leaving the implementation of innovations to the competition. > > > > > > This has nothing to with System V legacy. > > This has something to do with Suns inability to innovate. Sun failed > to innovate the command line utilities for 17 years. Now Roland came > up with innovations and as soon as the first reports about fixable > bugs appear you demand a pull-out. > > > This has to do with putting our > > energy into our most important problems. > > Tell me, what was the last innovation Sun introduced to the command > line utilities? Which energy did Sun invest into these commands in the > past? Please stop this generalised "stone throwing". Many many people at Sun helped with the project - remeber that without the help from people like April Chin this project wouldn't even exist, others helped with the ARC cases, tesing and the code and people like Peter provided very valueable input and bug reports. And Sun did invest lots of time and money getting the POSIX commands in Solaris maintained, updated to conform to the POSIX standard, keeping a very high quality standard (which is not easy to match with a new codebase - even getting the AST tools (which were very good from the beginning) to the same level took many many months) and finally getting ksh93 integrated into OS/Net. [snip] > > He who is innocent shall throw the first stone. I don't know whether the following is a quote from the bible... but: Could we please continue to cooperate and not try to tear each other into pieces ? Thanks! Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Memory requirements of Solaris/OpenSolaris... /was: Re: [tools-discuss] Project Proposal -- Port toMIPSarchitecture
ken mays wrote: [snip] > > Mark Martin wrote: [snip] > > Assuming you only use UFS and cut-down some system > > tuneables Solaris can > > run on a 64MB machine (my Ultra5 only has 128MB now after > > one of the > > DIMMs failed and it still works fine with CDE). The > > problems start if > > you want to run some of the memory-hogs, e.g. ZFS, JAVA or > > a X11 server > > - then you either need a swap device or much more memory. > > You should take to the 32MB of RAM level. How about playback of MPEG-2 > streams or MP3 audio using OpenSolaris in a 32 MB RAM embedded environment > solution. Booting plain OpenSolaris with a 32MB machine may be possible (remember original versions of Solaris 2.x had no problems with that) ... but MPEG-2 video stream playback will itself consume lots of memory since you have to do buffering, including I frames, data for the P/B frames etc. ... and system stream playback (system stream == interleaved video+audio streams) will require even more memory. I don't know whether this is possible... Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Memory requirements of Solaris/OpenSolaris... / was: Re: [tools-discuss] Project Proposal -- Port to MIPSarchitecture
Mark Martin wrote: > > [Resent for Reply-all] > > On Sat, Oct 18, 2008 at 6:03 PM, Martin Bochnig > wrote: > > +1 > > Except that it would be nice if somebody would make the > Polaris port functional, before starting a new port. > Also, why MIPS, not ARM? Isn't MIPS dead a bit? > > Thanks for the vote and the feedback. > > I believe the PowerPC is either lacking consensus on a platform or > lacking other resources (or both). I agree that the PowerPC has some > attractive features, but lack of a valid, available platform and > resources I think is contributing to its dormancy. I believe that > interest continues for that platform, but once Sun Labs discontinued > development support, the project seems to have gone into hibernation. > > Someone mentioned interest in an ARM a short while ago, but in my > research, I could not find a solid, available platform that provided > enough physical resources -- namely 256MB to 512MB RAM, Assuming you only use UFS and cut-down some system tuneables Solaris can run on a 64MB machine (my Ultra5 only has 128MB now after one of the DIMMs failed and it still works fine with CDE). The problems start if you want to run some of the memory-hogs, e.g. ZFS, JAVA or a X11 server - then you either need a swap device or much more memory. Beyond that I think we need a project which works on lowering the memory footprint of Solaris - for example as I already wrote in http://mail.opensolaris.org/pipermail/opensolaris-code/2007-March/004430.html -- snip -- > Another issue is the way how applications in Solaris allocate temporary > memory (this applies to the kernel but a "solution" is much more tricky > because the kernel's stack can't grow which limits it to 4k on i86 and > 8k on UltraSPARC (UltraSPARC may be in a better position since it could > map the stack with 64k pages (which runs into other problems since lots > of code doesn't expect a "custom" page size for kernel stacks... ;-(( > ))) - IMO in many places the usage of |malloc()| should be replaced with > |alloca()| or C99's variable length arrays assuming the size does not > exceed a given size (some sample code can be found in > http://mail.opensolaris.org/pipermail/perf-discuss/2007-February/001589.html). > This solution would have lots of advantages, for example: > - Multithreaded applications would not go through the heap each time, > e.g. avoid locking/syscall overhead in the worst case > - Better locality of data - the thread's stack is assumed to be closer > to the running CPU than a "random" page in the heap > - It is "easier" (the explanation of this is little bit beyond the scope > of this email, basically some UltraSPARC CPUs seems to have trouble > handling more than two different pagsizes at the same time except the > number of pages for a 3rd/4th size is very small) to map the stack with > largepages than the whole heap of an application > - Avoid taxing the heap with lots of small temporary allocations -- snip -- If we could fix the way how these allocations are done many issues with memory wasting and kernel allocator scalability (or better: Many temporary allocations will done in the per-thread memory "stack" and no longer go through the SLAB code) will simply go away. Bye, Roland P.S.: Setting Reply-To: to on-disc...@opensolaris.org -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Weired "at" job with "*.ctrl: No such file or directory" ...
Hi! Does anyone remeber a component of Solaris (OS/Netm SFWNV, Studio or punchin) which produces the following kind of "at" jobs: -- snip -- >From r...@terror.alquiekquak.org Tue Dec 16 00:00:55 2008 Date: Tue, 16 Dec 2008 00:00:53 +0100 (CET) From: Super-User To: r...@terror.alquiekquak.org Subject: Output from "at" job MIME-Version: 1.0 Your "at" job on terror "/var/spool/cron/atjobs/1229382046.a" produced the following output: *.ctrl: No such file or directory -- snip -- Does that ring a bell anywhere ? Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] genunix.org experiencing tech difficulties
Cyril Plisko wrote: > On Wed, Dec 3, 2008 at 1:28 PM, Roland Mainz <[EMAIL PROTECTED]> wrote: > > Al Hopper wrote: > >> > >> PS: belenix.org runs on genunix.org infrastructure but is running on > >> other hardware and is unaffected by this outage. > > > > Was svn.genunix.org somehow be affected, too ? > > Its a zone on the main machine, so I'd say whatever is true for > www.genunix.org is also true for svn.genunix.org > > Wait a sec, Roland, didn't you switched to mercurial long time ago ? The development tree (the current one is "prototype012") will move to mercurial after the ksh93-integration update1 putback (code review should end aroound 5.12.2008, then followed by RTI and immediate putback on monday) ... but the documentation, testcases, work logs, demo code etc. and development trees for some sub-projects (e.g. shxml, compound_var(4), /etc/env.d/ etc.) will likely remain in the Subversion repository. > Sorry, couldn't help it :) :-) Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] genunix.org experiencing tech difficulties
Al Hopper wrote: > > Please bear with us as we find/fix the hardware issues currently > causing "constipation" at www.genunix.org. Wiki users - don't worry - > we have current backups. But please allow at least 12 hours for the > site to be restored to normal operation. > > I guess our uptime record of 1267 days had to end at some point in time :) > > Sorry - no unusual images to display like they do at twitter.com etc > under these circumstances :) > On the other hand, we have twitter.com beaten in terms of reliability/uptime. > > Thanks for your patience... > > PS: belenix.org runs on genunix.org infrastructure but is running on > other hardware and is unaffected by this outage. Was svn.genunix.org somehow be affected, too ? Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] [Annoucement] ksh93-integration update1 2008-11-14 binaries available for download (for Solaris Nevada >= B84+OpenSolaris/Indiana) ...
prototype012 tree. Note: The script can only be used after a successfull $ make setup ; dmake install #-sequence, otherwise the resulting tarball will be incomplete. * The tarballs do not provide a manual page for ksh93. Please use the manual page for ksh93s+ in the meantime. * The ksh93 binaries can be build from source like this: (Instructions are for Solaris i386/AMD64; SPARC requires minor adjustments) 1. Pull sources and extract closed bin stuff (files can be obtained from opensolaris.org): $ mkdir test_x86 ; cd test_x86 $ svn checkout -r 1285 svn://svn.genunix.org/on/branches/ksh93/gisburn/prototype012/usr $ bzcat <../download/ on-closed-bins-nd-b97_pre1.i386.tar.bz2 | tar -xf - $ cd .. 2. Create opensolaris.sh. This is the usual opensolaris.sh with the paths adjusted to match your location of the sources. Example for the changes applies to opensolaris.sh (for my workspace): --- ./test1_x86/usr/src/tools/env/opensolaris.sh +++ ./opensolaris.sh @@ -43,10 +43,10 @@ # This is a variable for the rest of the script - # GATE doesn't matter to nightly itself -GATE=testws; export GATE +GATE=test1_x86;export GATE # CODEMGR_WS - where is your workspace at (or what should # nightly name it) -CODEMGR_WS="/export/$GATE"; export CODEMGR_WS +CODEMGR_WS="/home/test001/ksh93/on_build1/$GATE" +export CODEMGR_WS # Location of encumbered binaries. ON_CLOSED_BINS="$CODEMGR_WS/closed" export ON_CLOSED_BINS 3. Run "bldenv": $ env - SHELL=$SHELL TERM=$TERM HOME=$HOME LOGNAME=$LOGNAME DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY LANG=C LC_ALL=C PAGER=less MANPATH=$MANPATH /opt/onbld/bin/bldenv opensolaris.sh # 4. Build it (the quick way): $ cd test_x86/usr/src $ export CW_NO_SHADOW=1 $ time nice make setup 2>&1 | tee -a buildlog_setup.log $ time nice dmake install >buildlog.log 2>&1 Finally: Please check http://www.opensolaris.org/os/project/ksh93-integration/downloads/2008-11-14/ for any updates or additional comments... Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=http://www.opensolaris.org/os/project/ksh93-integration/downloads/2008-11-14/ [3]=ksh93s+ manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93s/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=ksh93-integration project bugzilla: http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration [6]=Heads-up message for "ksh93 integrated into Solaris 11/B72": http://www.opensolaris.org/os/community/on/flag-days/pages/2007081701/ Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] [Annoucement] ksh93-integration update1 2008-08-10 binaries available for download (for Solaris Nevada >= B84+Indiana) ...
r ksh93s+ [3] in the meantime. * The ksh93 binaries can be build from source like this: (Instructions are for Solaris i386/AMD64; SPARC requires minor adjustments) 1. Pull sources and extract closed bin stuff (files can be obtained from opensolaris.org): $ mkdir test_x86 ; cd test_x86 $ svn checkout -r 1163 svn://svn.genunix.org/on/branches/ ksh93/gisburn/prototype011/usr $ bzcat <../download/on-closed-bins-nd-b84.i386.tar.bz2 | tar -xf - $ cd .. 2. Create opensolaris.sh. This is the usual opensolaris.sh with the paths adjusted to match your location of the sources. Example for the changes applies to opensolaris.sh (for my workspace): --- ./test1_x86/usr/src/tools/env/opensolaris.sh Thu Sep 14 13:17:59 2666 +++ ./opensolaris.shSun Jul 30 00:50:08 2006 @@ -43,10 +43,10 @@ # This is a variable for the rest of the script - # GATE doesn't matter to nightly itself -GATE=testws; export GATE +GATE=test1_x86;export GATE # CODEMGR_WS - where is your workspace at (or what should # nightly name it) -CODEMGR_WS="/export/$GATE"; export CODEMGR_WS +CODEMGR_WS="/home/test001/ksh93/on_build1/$GATE"; export CODEMGR_WS # Location of encumbered binaries. ON_CLOSED_BINS="$CODEMGR_WS/closed" export ON_CLOSED_BINS 3. Run "bldenv": $ env - SHELL=$SHELL TERM=$TERM HOME=$HOME LOGNAME=$LOGNAME DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY LANG=C LC_ALL=C PAGER=less MANPATH=$MANPATH /opt/onbld/bin/bldenv opensolaris.sh # 4. Build it (the quick way): $ cd test_x86/usr/src $ export CW_NO_SHADOW=1 $ time nice make setup 2>&1 | tee -a buildlog_setup.log $ time nice dmake install >buildlog.log 2>&1 Finally: Please check http://www.opensolaris.org/os/project/ksh93-integration/downloads/2008-08-10/ for any updates or additional comments... ** Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=http://www.opensolaris.org/os/project/ksh93-integration/downloads/2008-08-10/ [3]=ksh93s+ manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93s/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=ksh93-integration project bugzilla: http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration [6]=Heads-up message for "ksh93 integrated into Solaris 11/B72": http://www.opensolaris.org/os/community/on/flag-days/pages/2007081701/ Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SXCE download area... / was: Re: sxce b95 download sucks
Ian Collins wrote: > Herschel Krustofsky writes: > > I agree completely with Bruno, getting the distribution out there properly > > is a showstopper. > > > This subject comes up over and over (and has for years) and the answer > remains the same. > > Why do you think Indiana was created? AFAIK this issue is not related to Indiana - originally the download system did work properly until it was replaced with a new one which broke "wget" and now depends on features (https, javascript) which aren't supported by anything except a web browser. IMO it would be nice to fix two things: 1. Get "wget" support working again, including the feature to resume downloads after an IP address change on the client side 2. Post MD5/SHA256 checksums to the _mailinglist_ (e.g. an independet information source - right now the ISOs and hash sums are located on the same set of servers which is IMO bad for security) Bye, Roland P.S.: Setting Reply-To: to [EMAIL PROTECTED] ... -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Multithreaded browsers... / was: Re: The end of Sparc desktops?
"Richard L. Hamilton" wrote: [snip] > > Hmmm... that'd be a close shave. Having worked with > > UltraSPARC T2s quite a bit, I'd say that the T2 is > > still pretty weak for the desktop workloads, > > precisely because of his single-thread performance. > > You'd have to have software that was highly optimized > > for either threading, or that was designed around > > spawning child processes ala Apache httpd or ISC's > > named. > > Java and browsers are already multithreaded, [snip] Small correction: AFAIK the only browser which is fully threaded (e.g. layout engine, plugins, networking etc.) is "Opera" (AFAIK "Konqueror" is fully threaded too... but I am not sure...). The Mozilla family of browsers+applications (e.g. FireFox, Mozilla/SeaMonkey, ThunderBird) only uses helper threads for stuff like networking while the layout engine+plugins all run in the same thread (threading in the layout engine+plugins was discussed long ago and rejected because it requires more or less a rewrite from scratch of the layout engine or having tons of locks in the code... and many years ago we simply thought that no system will get so many CPUs/cores that something like this makes sense (in the meantime the world has changed... ;-/ )) and AFAIK the remaining browsers (e.g. "w3m", "lynx" etc.) are completely single-threaded. Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] REVIEW System Admin. Guide for the Back toSchool Kit
Kathy Slattery wrote: > > > Currently, I'm using a customized version of Epic > > to author the > > > book. The source isn't available yet, but I plan to > > move it into > > > mercurial after the August 8th release. > > > > May I ask for any links to that soft, google search > > does not give my any reasonable results. > > I believe the plan is for me to transition the contents to XML Which kind of XML ? XML is basically only the "raw" syntax... > and then > you can use XMLMind or whatever XML editor you want to edit > the files. Does that help? It would help a lot if it's DocBook/XML since there are many editors/viewers for this kind of XML format... Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] "hexfloat" format not supported by |strtod()| in C99/SUSv3 mode ? / was: Re: Can Solaris be discussed here?
Dennis Clarke wrote: > On Fri, Aug 1, 2008 at 11:27 PM, Ming Kin Lai <[EMAIL PROTECTED]> wrote: > > I have a feeling that Sun has abandoned maintaining Solaris, and shifted > > its resources to OpenSolaris. Well, that's good news to people here, I > > guess. > > So, can I discuss things about Solaris 10 here? How about something about > > Solaris 10's C library? Can I ask a question why a certain library > > function does not work properly? Can I report a bug here? Currently there > > does not appear to be a way to report Solaris' bugs in Sun's website > > anymore. > > > > just a guess, are you referring to an issue with strtod(3C) in > C99/SUSv3 mode NOT being able to handle hexadecimal strings ? Erm... the hexfloat format, e.g. ... -- snip -- $ printf "%a\n" 0.1 0x1.999ap-04 -- snip -- ... is AFAIK part of C99 standard and should work on Solaris. If it does not work then this is a bug... Bye, Roland P.S.: Seting Reply-To: to OpenSolaris Code mailing list <[EMAIL PROTECTED]> -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] ksh93-integration 2008-06-24 update binaries available for download (for Solaris Nevada >= B84+Indiana) ...
n be build from source like this: (Instructions are for Solaris i386/AMD64; SPARC requires minor adjustments) 1. Pull sources and extract closed bin stuff (files can be obtained from opensolaris.org): $ mkdir test_x86 ; cd test_x86 $ svn checkout -r 1134 svn://svn.genunix.org/on/branches/ksh93/gisburn/prototype011/usr $ bzcat <../download/on-closed-bins-nd-b84.i386.tar.bz2 | tar -xf - $ cd .. 2. Create opensolaris.sh. This is the usual opensolaris.sh with the paths adjusted to match your location of the sources. Example for the changes applies to opensolaris.sh (for my workspace): -- snip -- --- ./test_x86/usr/src/tools/env/opensolaris.sh Thu Sep 1 0:0:0 2666 +++ ./opensolaris.shSun Jul 1 0:0:0 2006 @@ -43,10 +43,10 @@ # This is a variable for the rest of the script - GATE # doesn't matter to nightly itself -GATE=testws; export GATE +GATE=test_x86; export GATE # CODEMGR_WS - where is your workspace at # (or what should nightly name it) -CODEMGR_WS="/work/$GATE";export CODEMGR_WS +CODEMGR_WS="/home/test001/ksh93/on_build1/$GATE";export CODEMGR_WS # Location of encumbered binaries. ON_CLOSED_BINS="$CODEMGR_WS/closed"; export ON_CLOSED_BINS -- snip -- 3. Run "bldenv": $ env - SHELL=$SHELL TERM=$TERM HOME=$HOME LOGNAME=$LOGNAME DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY LANG=C LC_ALL=C PAGER=less MANPATH=$MANPATH /opt/onbld/bin/bldenv opensolaris.sh # 4. Build it (the quick way): $ cd test_x86/usr/src $ export CW_NO_SHADOW=1 $ time nice make setup 2>&1 | tee -a buildlog_setup.log $ time nice dmake install >buildlog.log 2>&1 Finally: Please check http://www.opensolaris.org/os/project/ksh93-integration/downloads/2008-06-24/ for any updates or additional comments... ** Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=http://www.opensolaris.org/os/project/ksh93-integration/downloads/2008-06-24/ [3]=ksh93s+ manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93s/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=ksh93-integration project bugzilla: http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] ksh93-integration 2008-06-17 update binaries available for download (for Solaris Nevada >= B84+Indiana) ...
. * The ksh93 binaries can be build from source like this: (Instructions are for Solaris i386/AMD64; SPARC requires minor adjustments) 1. Pull sources and extract closed bin stuff (files can be obtained from opensolaris.org): $ mkdir test_x86 ; cd test_x86 $ svn checkout -r 1122 svn://svn.genunix.org/on/branches/ ksh93/gisburn/prototype011/usr $ bzcat <../download/on-closed-bins-nd-b84.i386.tar.bz2 | tar -xf - $ cd .. 2. Create opensolaris.sh. This is the usual opensolaris.sh with the paths adjusted to match your location of the sources. Example for the changes applies to opensolaris.sh (for my workspace): --- ./test1_x86/usr/src/tools/env/opensolaris.sh Thu Sep 14 13:17:59 2666 +++ ./opensolaris.shSun Jul 30 00:50:08 2006 @@ -43,10 +43,10 @@ # This is a variable for the rest of the script - # GATE doesn't matter to nightly itself -GATE=testws; export GATE +GATE=test1_x86;export GATE # CODEMGR_WS - where is your workspace at (or what should # nightly name it) -CODEMGR_WS="/export/$GATE";export CODEMGR_WS +CODEMGR_WS="/home/test001/ksh93/on_build1/$GATE"; export CODEMGR_WS # Location of encumbered binaries. ON_CLOSED_BINS="$CODEMGR_WS/closed" export ON_CLOSED_BINS 3. Run "bldenv": $ env - SHELL=$SHELL TERM=$TERM HOME=$HOME LOGNAME=$LOGNAME DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY LANG=C LC_ALL=C PAGER=less MANPATH=$MANPATH /opt/onbld/bin/bldenv opensolaris.sh # 4. Build it (the quick way): $ cd test_x86/usr/src $ export CW_NO_SHADOW=1 $ time nice make setup 2>&1 | tee -a buildlog_setup.log $ time nice dmake install >buildlog.log 2>&1 Finally: Please check http://www.opensolaris.org/os/project/ksh93-integration/downloads/2008-06-17/ for any updates or additional comments... ** Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=http://www.opensolaris.org/os/project/ksh93-integration/downloads/2008-06-17/ [3]=ksh93s+ manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93s/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=ksh93-integration project bugzilla: http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration [6]=Heads-up message for "ksh93 integrated into Solaris 11/B72": http://www.opensolaris.org/os/community/on/flag-days/pages/2007081701/ Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [blog post] Terminal with colors in OpenSolaris 2008.5
On 5/8/08, Silveira Neto <[EMAIL PROTECTED]> wrote: > Put colors for bash: > http://silveiraneto.net/2008/05/07/terminal-with-colors-in-opensolaris/ > Edit ~/.bashrc and insert in the end: > > alias ls='ls –color=auto' > reopen your terminal and you got colors. > > I could not find the global bashrc for root and others users, where is it? /etc/bash.bashrc is not supported _yet_ (we're working on that). For ksh there is now /etc/ksh.kshrc with the same functionality. Bye, Roland P.S.: Please use [EMAIL PROTECTED] for shell-related questions (please subscribe before posting...). -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] ${HOME} of "root" is now "/root" ... / was: Re: [security-discuss]$HOME of root
Gary Winiger wrote: > > -- > X-Sun-Data-Type: text > X-Sun-Data-Description: text > X-Sun-Data-Name: text > X-Sun-Charset: us-ascii > X-Sun-Content-Lines: 8 > > > It's done! :-) > > > > See attached commit notification email. "Flag day" notification is > > http://www.opensolaris.org/os/community/on/flag-days/pages/2008031801/ > > FYI, the Nevada Heads Up that I sent to internal aliases is attached. Thanks! ... :-) ... and I forgot something in my previous email: Thank you very much for doing this... :-) Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] ${HOME} of "root" is now "/root" ... / was: Re: [security-discuss] $HOME of root
Dirk Wetter wrote: > Am 10.03.2008 09:51, Joep Vesseur schrieb: > > On 03/10/08 01:41, Roland Mainz wrote: > >> Is there any status update ? Did you hit any major problems ? > > > > On the list for integration any time now (I can't say which build since I'm > > not the one who will put it in, but it is planned RSN). > > RSN? Since this is an ongoing matter for quite some time: in which > build? If you can't answer it, maybe somebody else can? It's done! :-) See attached commit notification email. "Flag day" notification is http://www.opensolaris.org/os/community/on/flag-days/pages/2008031801/ Bye, Roland P.S.: Setting Reply-To: to "[EMAIL PROTECTED]" ... -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)--- Begin Message --- Author: gww Repository: /hg/onnv/onnv-gate Latest revision: c4e3ce4e0c929acf768a14fb1045a4292fc75da7 Total changesets: 1 Log message: PSARC/2003/039 Alternate home directory for root user 4960338 want to change root's home directory Files: update: usr/src/Targetdirs update: usr/src/cmd/Adm/sun/passwd update: usr/src/pkgdefs/SUNWcsr/prototype_com ___ onnv-notify mailing list [EMAIL PROTECTED] http://mail.opensolaris.org/mailman/listinfo/onnv-notify --- End Message --- ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] VMware tools don't rock the clock in B83a/B84 ...
Hi! More or less an update to my original "VMware's rock around the clock..."-posting (http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-March/013848.html): 1. In Solaris 11 B83a and B84 the VMware tools no longer sync the time with the host OS (I'm not using "ntpdate" to slew the VM's clock each 15mins to get a more or less accurate time) 2. In Solaris 11/B72 (where the VMware tools were still properly working) the VMware tools cause sub-second "time jumps". This isn't a big issue for nornmal applications but things like test suites which compare filesystem timestamps (which support sub-second granulation) blow-up (which renders VMware currently more or less useless for development in my case). IMO the suggested fix would be to teach the VMware tools to "slew" the clock if the time difference is smaller than 5mins and only "set" the time when the differenfec is greater (maybe this should be a tuneable). Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] ksh93-integration 2008-02-29 update binaries available for download (for Nevada >= B72+Indiana) ...
ake install #-sequence, otherwise the resulting tarball will be incomplete. * The tarballs do not provide a manual page for ksh93. Please use the manual page for ksh93s+ in the meantime. * The ksh93 binaries can be build from source like this: (Instructions are for Solaris i386/AMD64; SPARC requires minor adjustments) 1. Pull sources and extract closed bin stuff (files can be obtained from opensolaris.org): $ mkdir test_x86 ; cd test_x86 $ svn checkout -r 957 svn://svn.genunix.org/on/branches/ ksh93/gisburn/prototype010/usr $ bzcat <../download/on-closed-bins-nd-b72.i386.tar.bz2 | tar -xf - $ cd .. 2. Create opensolaris.sh. This is the usual opensolaris.sh with the paths adjusted to match your location of the sources. Example for the changes applies to opensolaris.sh (for my workspace): --- ./test1_x86/usr/src/tools/env/opensolaris.sh Thu Jan 666 13:17:59 2666 +++ ./opensolaris.shSun Jul 30 00:50:08 2666 @@ -43,10 +43,10 @@ # This is a variable for the rest of the script - GATE doesn't matter to # nightly itself -GATE=testws; export GATE +GATE=test1_x86; export GATE # CODEMGR_WS - where is your workspace at (or what should nightly name it) -CODEMGR_WS="/export/$GATE"; export CODEMGR_WS +CODEMGR_WS="/home/test001/ksh93/on_build1/$GATE"; export CODEMGR_WS # Location of encumbered binaries. ON_CLOSED_BINS="$CODEMGR_WS/closed"; export ON_CLOSED_BINS 3. Run "bldenv": $ env - SHELL=$SHELL TERM=$TERM HOME=$HOME LOGNAME=$LOGNAME DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY LANG=C LC_ALL=C PAGER=less MANPATH=$MANPATH /opt/onbld/bin/bldenv opensolaris.sh # 4. Build it (the quick way): $ cd test_x86/usr/src $ export CW_NO_SHADOW=1 $ time nice make setup 2>&1 | tee -a buildlog_setup.log $ time nice dmake install >buildlog.log 2>&1 Finally: Please check http://www.opensolaris.org/os/project/ksh93-integration/downloads/2008-02-29/ for any updates or additional comments... ** Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=http://www.opensolaris.org/os/project/ksh93-integration/downloads/2008-02-29/ [3]=ksh93s+ manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93s/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=ksh93-integration project bugzilla: http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration [6]=Heads-up message for "ksh93 integrated into Solaris 11/B72": http://www.opensolaris.org/os/community/on/flag-days/pages/2007081701/ Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] The impossible SDLC download... / was: Re: [osol-announce] SXCE Build 81 available
Moritz Willers wrote: > On 29 Jan 2008, at 22:59, Derek Cicero wrote: > > Please find the links to SXCE Build 81 at > > > > http://www.opensolaris.org/os/downloads/on/ > > > > /IMPORTANT:/ > > > > The SDLC has changed how the downloads works. > > > > Now you choose the Platform first and then see a list of all > > the downloads (CD and DVD). > > > > I believe I fixed all the old links so they now point to the right > > place, but if you have trouble please send a note to website-discuss > > and > > I'll make any corrections. > > > > Also, for anyone using the old > > > > /os/downloads/sol_ex_dvd/ > > > > shortcut on your blogs, it will still work for a while but I will > > remove > > it after Build 85. The new shortcut is > > > > /os/downloads/sol_ex/ > > Thanks a lot for posting. I find that new technology on the SDLC > quite annoying. > > It used to be possible to copy/paste the URLs from the laptop (non > Solaris) to the server (Solaris) and then wget the files straight onto > the server where I needed the iso image (I do the Live Upgrade > straight from the iso, never burn to DVD (save the trees or something > like that)). The URL used to contain all authentication information > necessary, now all that gets hidden away into cookies that I cannot > easily copy over. > > I always found this obsession to have to use to web browser to get to > the updates annoying, oh that damned click do accept the license ..., > but I suffered it. I so wish everyone within Sun would have to go > through that same web page to get to the iso and I bet it would be > changed to lend itself more easily to automation! Erm... if that's true then this needs to be escalated within Sun immediately. 1. Lots of FireFox versions shipped with Solaris have the annyoing bug to eat memory for large downloads and crash when the system runs out of memory - which means a simple 512MB machine (assuming no swap) will be _unable_ to download the 1GB DVD segments. 2. IMO it should be allowed to use "wget" for download and not force users to rely on either a memory-hungry browser which needs to stay open the whole night or some "fancy" java-based download helper tool which consumes similar insane amounts of memory BTW: What is the justification for changing the authentification from URL sessions to HTTP cookies ? Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [pkg-discuss] 142 Replace /sbin/sh with ksh93
[EMAIL PROTECTED] wrote: > > The ksh93/bash holy war is off-topic for pkg-discuss. > > This list is for the discussion of the development of the packaging system. > > Indiana-discuss, or perhaps alt.fetish on USENET, would be a better > forum for this thread. Or just "remind" people (either via email or cudgel) to keep no-technical bickering&&whining and all "political" issues out of the technical lists (like ksh93-integration-disucss@, pkg-discuss@) etc. Bye, Roland P.S.: Setting Reply-To: to opensolaris-discuss@opensolaris.org -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] ksh93-integration 2007-11-05 update binaries available for download (for Nevada >= B72) ...
in/tcsh /usr/bin/zsh /usr/sfw/bin/zsh /usr/xpg4/bin/sh -- snip -- * The tarball was created using the "build_ksh93_standalone_tarball.sh" script which is available in the usr/-directory of the prototype010 tree. Note: The script can only be used after a successfull $ make setup ; dmake install #-sequence, otherwise the resulting tarball will be incomplete. * The tarballs do not provide a manual page for ksh93. Please use the manual page for ksh93s+ in the meantime (see [3]). * The ksh93 binaries can be build from source like this: (Instructions are for Solaris i386/AMD64; SPARC requires minor adjustments) 1. Pull sources and extract closed bin stuff (files can be obtained from opensolaris.org): $ mkdir test_x86 ; cd test_x86 $ svn checkout -r 894 svn://svn.genunix.org/on/branches/ksh93/gisburn/prototype010/usr $ bzcat &1 | tee -a buildlog_setup.log $ time nice dmake install >buildlog.log 2>&1 Finally: Please check http://www.opensolaris.org/os/project/ksh93-integration/downloads/2007-11-05/ for any updates or additional comments... ** Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=http://www.opensolaris.org/os/project/ksh93-integration/downloads/2007-11-05/ [3]=ksh93s+ manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93s/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=ksh93-integration project bugzilla: http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration [6]=Heads-up message for "ksh93 integrated into Solaris 11/B72": http://www.opensolaris.org/os/community/on/flag-days/pages/2007081701/ Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Indiana milestone reached!
Glynn Foster wrote:
>
> I'm very pleased to announce that the first milestone of Project Indiana is
> now
> available - called OpenSolaris Developer Preview.
>
> It's available for download at
>
> http://dlc.sun.com/osol/indiana/downloads/current/in-preview.iso
[snip]
Congrats to all! :-)
I only did a quick look:
- Many locales are missing. IMO it may be nice to ship (limited to one
per country to restrict disk space requirements):
"C"
"en_US.UTF-8" (as default, following the default for SuSE Linux and
RedHat)
"ja_JP.UTF-8" (for japan)
"zh_CN.UTF-8" (for china)
etc.
- The manual page subsystem should be adjusted to be a bit more
enduser-friendly (I have a rewrite of /usr/bin/man queued, please ask
either me or Michelle Olson)
- The default interactive shell environment needs some adjustments
(better defaults for prompt, PAGER, MANPATH etc.)
- Please allow localised manual pages to be installed on demand (e.g.
Solaris comes with a huge list of japanese and chinese manual pages)
- It may be nice to think about shipping the VMware tools by default or
as an installable package (currently the system clock has problems which
causes other issues over time)
- Where are the "traditional" X11 tools like "xclock" or "xeyes" ? ;-(
- The network autodetection assumes that the local network has DHCP
(which is not always available)
- If network is available and the system is not running VMware tools
"xntpd" should be enabled and sync the time against an external source
(e.g. some kind of "time autodetection" ... :-) )
- Why was the automounter for /home/ removed ? I liked my traditional
"/home/${LOGNAME}" directory...
that's all what I found in a 5min look...
Bye,
Roland
P.S.: Setting Reply-To: to [EMAIL PROTECTED] to handle the
technical stuff listed above there...
--
__ . . __
(o.\ \/ /.o) [EMAIL PROTECTED]
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
[osol-discuss] ksh93-integration 2007-10-31 test binaries available for download (for Nevada B61-B71) ...
|pp)|/(ksh|rksh|pfksh)|include/ast|usr/ast/" | egrep -v cmdutils | sort #. * The tarballs do not provide a manual page for ksh93. Please use the manual page for ksh93s+ in the meantime [3]. * "multiline" input mode was temporary disabled in the default configuration due small issues. * The ksh93 binaries can be build from source like this: (Instructions are for Solaris i386/AMD64; SPARC requires minor adjustments) 1. Pull sources and extract closed bin stuff (files can be obtained from opensolaris.org): $ mkdir test_x86 ; cd test_x86 $ svn checkout -r 885 svn://svn.genunix.org/on/branches/ksh93/gisburn/prototype005/usr $ bzcat <../download/on-closed-bins-nd-b61.i386.tar.bz2 | tar -xf - $ cd .. 2. Create opensolaris.sh. This is the usual opensolaris.sh with the paths adjusted to match your location of the sources. Example for the changes applies to opensolaris.sh (for my workspace): -- snip -- --- ./test1_x86/usr/src/tools/env/opensolaris.shThu Sep 14 13:17:59 2006 +++ ./opensolaris.shSun Jul 30 00:50:08 2006 @@ -43,10 +43,10 @@ # This is a variable for the rest of the script - GATE # doesn't matter to nightly itself -GATE=testws; export GATE +GATE=test1_x86;export GATE # CODEMGR_WS - where is your workspace at # (or what should nightly name it) -CODEMGR_WS="/export/$GATE";export CODEMGR_WS +CODEMGR_WS="/home/test001/ksh93/on_build1/$GATE"; export CODEMGR_WS # Location of encumbered binaries. ON_CLOSED_BINS="$CODEMGR_WS/closed"; export ON_CLOSED_BINS -- snip -- 3. Run "bldenv": $ env - SHELL=$SHELL TERM=$TERM HOME=$HOME LOGNAME=$LOGNAME DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY LANG=C LC_ALL=C PAGER=less MANPATH=$MANPATH /opt/onbld/bin/bldenv opensolaris.sh # 4. Build it (the quick way): $ cd test_x86/usr/src $ export ON_BUILD_AST_L10N_CATALOGS=1 CW_NO_SHADOW=1 $ time nice make setup 2>&1 | tee -a buildlog_setup.log $ time nice dmake install >buildlog.log 2>&1 Finally: Please check http://www.opensolaris.org/os/project/ksh93-integration/downloads/2007-10-31/ for any updates or additional comments... ** Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=ksh93s+_beta release annoucement: http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/2007-April/002483.html [3]=ksh93s+ manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93s/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=ksh93-integration project bugzilla: http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration [6]=Heads-up message for "ksh93 integrated into Solaris 11/B72": http://www.opensolaris.org/os/community/on/flag-days/pages/2007081701/ Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] sendmail project at opensolaris.org ?
Hi! Just curious: Would be there any interest to create a sendmail and/or mail-related community or project which bundles all the sendmail&&mail tool activities (e.g. sendmail maintaince, updates, mailx things, building a "managing sendmail on Solaris (+SMF)" FAQ etc. (the idea came up today when someone asked on IRC "... how do I prevent user root and only user root from receiving spam from outside...")) ? Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Porting OpenSolaris To OLPC XO AMD Geode Laptops
Brandorr wrote:
> On 9/28/07, nospam <[EMAIL PROTECTED]> wrote:
> > OLPC (One Laptop Per Child) project had released XO Laptops for the public
> > using G1G1 ("Buy 2 Get 1").
> > One laptop will be sent to the buyer, another laptop will be sent to a
> > child in developing country.
> >
> > Unfortunately the XO AMD Geode LX laptops is different from other laptops:
> > 1. There is no BIOS inside the laptop.
> > 2. There is no VGA/EGA/CGA mode.
> > 3. Non standard boot procedure.
> > 4. Nobody knows if it is possible to boot the laptop from external CD-Drive.
> > 5. Ordinary / off-the-shelf OpenSolaris can't run on this laptop. Linux run
> > on XO with patched/modified kernel.
> >
> > Is it possible to port OpenSolaris to XO laptops?
> > Who can do this project?
> > Thank you.
>
> Not happening. You only have 1G of storage. Solaris would need some
> serious trimming to fit. (And maybe compression). With 256M of RAM it
> would be crazy..
Why ? I only have 256MB in my Ultra5 and crafted most of the
ksh93-integration stuff on that machine. And disk space shouldn't be a
big problem since much stuff can be trimmed, redundant stuff removed
(e.g. the extra libc, 64bit stuff, includes etc.), Xserver linked
statically etc.
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) [EMAIL PROTECTED]
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Running Solaris 11/Nevada B72 on a M4000 ...
Roland Mainz wrote: > Does anyone here run Solaris 11/Nevada B72 on a M4000 ? I need some > feedback whether it runs (more or less) stable on that type of > machine... ... does anyone have a M4000 or M5000 around to test this, please ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Running Solaris 11/Nevada B72 on a M4000 ...
Hi! Does anyone here run Solaris 11/Nevada B72 on a M4000 ? I need some feedback whether it runs (more or less) stable on that type of machine... Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Sun + Microsoft cooperation = codecs forSiolaris, finally?
Alan Coopersmith wrote: > UNIX admin wrote: > > In fact, Sun, under this agreement has access to all and > > any Microsoft technology, and is free to implement that > > technology in Solaris in any way Sun pleases! > > I've never seen the agreement, and I'm sure anyone who has will not > be commenting on it here, but for the one product I know of that came > out of that agreement, it certainly has restrictions and Sun is not > free to do whatever it damn well pleases, so I think you just read a > poorly informed news article and not the actual agreement. Another issue is: Someone has to write the code... you can't just grab some windows codec sources and compile them 1:1 on Solaris... Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Where are my bug reports (season 6, episode 66) ?
Roland Mainz wrote: > Does anyone know whether bugs.opensolaris.org is "sick" again ? I'm > missing two bug reports: > 1. DTrace causes system hang > > and > > 2. DTrace ksh scripts > > Can anyone please check what happened to these bugs ? Erm... did anyone see these bug reports somewhere or should I just assume they're "MIA" (="missing in action") and need to be resubmitted ? Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Where are my bug reports (season 6, episode 66) ?
Hi! Does anyone know whether bugs.opensolaris.org is "sick" again ? I'm missing two bug reports: 1. DTrace causes system hang and 2. DTrace ksh scripts Can anyone please check what happened to these bugs ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Internet clipboard "opensolaris.pastebin.ca" set up...
Hi!
[The users in irc://irc.freenode.org/#opensolaris already know it but
AFAIK it was never announced to the general public]
I've set-up an OpenSolaris-specific version of the pastebin.ca internet
clipboard, e.g. a public place to paste larger texts via browser (or the
command-line tool below) which couldn't be transfered easily via other
methods (except email) - this is AFAIK quite usefull during IRC
conversations, phone meetings and maybe things like the upcoming
opensolaris summit (e.g. genereal-purpose scripts/drafts/etc. dumping
ground).
For those who don't have a browser around to paste things like logs and
other stuff to opensolaris.pastebin.ca I wrote a small script (attached
as "shnote.ksh.txt" ; note that this script needs Solaris 11/Nevada B72
or higher) which does this without requiring a browser, e.g. install the
script with...
-- snip --
# cp shnote.ksh.txt /usr/bin/shnote
# chmod a+rx,a-w /usr/bin/shnote
-- snip --
...and then use it like this:
-- snip --
$ shnote put "demo #8932001"
SUCCESS: http://opensolaris.pastebin.ca/702814
-- snip --
... will write the string "demo #8932001" to
http://opensolaris.pastebin.ca and returns the URL where the text can be
accessed from a browser.
Sending command output works similary, e.g.
-- snip --
$ shnote put "$(ls -l)"
SUCCESS: http://opensolaris.pastebin.ca/702822
-- snip --
... will send the output of "ls -l" to http://opensolaris.pastebin.ca
and return the access URL.
Additionally the script maintains a small history containing the access
URL, title (usually the users name) and the date, e.g.
-- snip --
$ shnote hist
#
...
...
http://opensolaris.pastebin.ca/702814 gisburn Sep 19 04:51:21 CET 2007
...
http://opensolaris.pastebin.ca/702822 gisburn Sep 19 05:02:52 CET 2007
-- snip --
Finally you can get strings/data/text/etc. from
http://opensolaris.pastebin.ca using...
-- snip --
$ shnote get http://opensolaris.pastebin.ca/702814
# Record name is '702814'
demo #8932001
-- snip --
...or just short:
-- snip --
$ shnote get 702814
# Record name is '702814'
demo #8932001
-- snip --
Suggestions/comments/rants/etc. welcome... :-)
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) [EMAIL PROTECTED]
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)#!/bin/ksh93
#
# CDDL HEADER START
#
# The contents of this file are subject to the terms of the
# Common Development and Distribution License (the "License").
# You may not use this file except in compliance with the License.
#
# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
# or http://www.opensolaris.org/os/licensing.
# See the License for the specific language governing permissions
# and limitations under the License.
#
# When distributing Covered Code, include this CDDL HEADER in each
# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
# If applicable, add the following below this CDDL HEADER, with the
# fields enclosed by brackets "[]" replaced with your own identifying
# information: Portions Copyright [] [name of copyright owner]
#
# CDDL HEADER END
#
#
# Copyright 2007 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
# ident "%Z%%M% %I% %E% SMI"
#
# Solaris needs /usr/xpg4/bin/ because the tools in /usr/bin are not
POSIX-conformant
export PATH=/usr/xpg4/bin:/bin:/usr/bin
# Make sure all math stuff runs in the "C" locale to avoid problems with
alternative
# radix point representations (e.g. ',' instead of '.' in de_DE.*-locales). This
# needs to be set _before_ any floating-point constants are defined in this
script)
if [[ "${LC_ALL}" != "" ]] ; then
export \
LC_MONETARY="${LC_ALL}" \
LC_MESSAGES="${LC_ALL}" \
LC_COLLATE="${LC_ALL}" \
LC_CTYPE="${LC_ALL}"
unset LC_ALL
fi
export LC_NUMERIC=C
function fatal_error
{
print -u 2 "${progname}: $@"
exit 1
}
# fixme: use "stat" builtin instead of "ls"
function get_filesize
{
typeset filename="$1"
typeset dummy # dummy string
integer filesize=-1
if [[ -f "${filename}" ]] ; then
ls -lb "${filename}" | read dummy dummy dummy dummy filesize dummy
fi
print -- ${filesize}
return 0
}
function encode_multipart_form_data
{
#set -o xtrace
nameref formdata=$1
nameref content="${1}.content" # ToDO: should be
|content="formdata.content"|
integer numformelements=${#formdata.form[*]}
integer i
content=""
# todo: add support to upload files
for (( i=0 ; i < numformelements ; i++ )) ; do
nameref element="${1}.form[$
[osol-discuss] Small experiment with "twitter.com" and /var/adm/messages ...
Hi!
Based on Glynn Foster's IRC request I hacked-up a small experiment/toy
(see attached script "shtwitter.ksh", the file needs Solaris 11 >= B72
since it depends on the networking capabilities of the new korn shell)
which allows to post messages to a twitter.com blog. "twitter" is some
kind of microblogging site, e.g. you can post one-liners up to 140
characters to a page, similar to a syslog.
The similarity with a syslog quickly leads to a simple usage idea - send
the contents of /var/adm/messages to a twitter blog like (see
http://twitter.com/syslog_sxb72x86 for an example (WARNING: This is not
recommended since the log may contain passwords by accident))
$ (export SHTWITTER_USER=""
SHTWITTER_PASSWD="" ; tail -f /var/adm/messages |
while read i ; do ksh93 shtwitter.ksh blog "$i" ; done)
Does anyone have better ideas how such a thing could be utilised (maybe
to monitor SMF state changes ?) ?
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) [EMAIL PROTECTED]
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)#!/bin/ksh93
#
# CDDL HEADER START
#
# The contents of this file are subject to the terms of the
# Common Development and Distribution License (the "License").
# You may not use this file except in compliance with the License.
#
# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
# or http://www.opensolaris.org/os/licensing.
# See the License for the specific language governing permissions
# and limitations under the License.
#
# When distributing Covered Code, include this CDDL HEADER in each
# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
# If applicable, add the following below this CDDL HEADER, with the
# fields enclosed by brackets "[]" replaced with your own identifying
# information: Portions Copyright [] [name of copyright owner]
#
# CDDL HEADER END
#
#
# Copyright 2007 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
# ident "%Z%%M% %I% %E% SMI"
#
# Solaris needs /usr/xpg4/bin/ because the tools in /usr/bin are not
POSIX-conformant
export PATH=/usr/xpg4/bin:/bin:/usr/bin
# Make sure all math stuff runs in the "C" locale to avoid problems with
alternative
# radix point representations (e.g. ',' instead of '.' in de_DE.*-locales). This
# needs to be set _before_ any floating-point constants are defined in this
script)
if [[ "${LC_ALL}" != "" ]] ; then
export \
LC_MONETARY="${LC_ALL}" \
LC_MESSAGES="${LC_ALL}" \
LC_COLLATE="${LC_ALL}" \
LC_CTYPE="${LC_ALL}"
unset LC_ALL
fi
export LC_NUMERIC=C
function fatal_error
{
print -u 2 "${progname}: $@"
exit 1
}
function encode_x_www_form_urlencoded
{
#set -o xtrace
nameref formdata=$1
nameref content="${1}.content" # ToDO: should be
|content="formdata.content"|
integer numformelements=${#formdata.form[*]}
integer i j
content=""
for (( i=0 ; i < numformelements ; i++ )) ; do
nameref element="${1}.form[${i}]" # ToDo: should be
|element="formdata.form[${i}]"|
typeset data="${element.data}"
integer datalen="${#data}"
typeset c
[[ "$content" != "" ]] && content+="&"
content+="${element.name}="
for ((j=0 ; j < datalen ; j++)) ; do
c="${data:j:1}"
case "$c" in
' ') c="+" ;;
'!') c="%21" ;;
'*') c="%2A" ;;
"'") c="%27" ;;
'(') c="%28" ;;
')') c="%29" ;;
';') c="%3B" ;;
':') c="%3A" ;;
'@') c="%40" ;;
'&') c="%26" ;;
'=') c="%3D" ;;
'+') c="%2B" ;;
'$') c="%24" ;;
',') c="%2C" ;;
'/') c="%2F" ;;
'?') c="%3F" ;;
'%') c="%25" ;;
'#') c="%23" ;;
'[') c="%5B" ;;
']') c="%5D" ;;
*) ;;
esac
content+="$c"
done
done
formdata.content_length=${#content}
return 0
}
# parse return c
Re: [osol-discuss] VMware's rock around the clock...
you may try one of the following: http://wotho2.ethz.ch/vmware/tools/ or "vmw" from http://chitchat.at.infoseek.co.jp/vmware/vmtools.html#top regards roland (too) This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libshell/common/ appears... disappears... appears... disappears... appears... disappears... appears... disappears...
Hi! Does anyone know what may currently be wrong with http://src.opensolaris.org/ ? New sources like http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libshell/common/ are sometimes available, sometimes they disappear, then they appear again and then they disappear again (and putting links to these sources a home page or blog entry then causes "broken link" reports... ;-( ) ... ;-( ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [osol-announce] New OpenSolaris Xen drop available
John Levon wrote: > > New binaries and sources are available for the OpenSolaris on Xen project. For > more details: > > http://blogs.sun.com/levon/entry/solaris_xen_update Is there anywhere a webrev for the changes ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] ksh93-integration 2007-07-14 test binaries available for download...
nges applies to opensolaris.sh (for my workspace): --- ./test1_x86/usr/src/tools/env/opensolaris.shThu Sep 14 13:17:59 2006 +++ ./opensolaris.shSun Jul 30 00:50:08 2006 @@ -43,10 +43,10 @@ # This is a variable for the rest of the script - GATE doesn't matter to # nightly itself -GATE=testws; export GATE +GATE=test1_x86;export GATE # CODEMGR_WS - where is your workspace at (or what should nightly name it) -CODEMGR_WS="/export/$GATE";export CODEMGR_WS +CODEMGR_WS="/home/test001/ksh93/on_build1/$GATE"; export CODEMGR_WS # Location of encumbered binaries. ON_CLOSED_BINS="$CODEMGR_WS/closed"; export ON_CLOSED_BINS 3. Run "bldenv": $ env - SHELL=$SHELL TERM=$TERM HOME=$HOME LOGNAME=$LOGNAME DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY LANG=C LC_ALL=C PAGER =less MANPATH=$MANPATH /opt/onbld/bin/bldenv opensolaris.sh # 4. Build it (the quick way): $ cd test_x86/usr/src $ export ON_BUILD_AST_L10N_CATALOGS=1 CW_NO_SHADOW=1 $ time nice make setup 2>&1 | tee -a buildlog_setup.log $ time nice dmake install >buildlog.log 2>&1 Finally: Please check http://www.opensolaris.org/os/project/ksh93-integration/downloads/2007-07-14/ for any updates or additional comments... ** Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=ksh93s+_beta release annoucement: http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/2007-April/002483.html [3]=ksh93r manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93r/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] VMware's rock around the clock...
Andy Tucker wrote: > > On 3/6/06, Roland Mainz <[EMAIL PROTECTED]> wrote: > > I'm hitting some problems with Solaris guest installations in VMware > > (e.g. Solaris being the guest in a VMware VM): > > Sometimes the clock is going out-of-sync. I configured "xntpd" to > > counteract these issues - but suddenly at one point all hell breaks > > loose: > ... > > Generally configuring ntp in a guest doesn't work well due since ntpd > gets confused by the unstable nature of time in a VM (particularly if > the host is busy) and gives up. The better solution is to run ntp on > the host and configure the guest tools to keep time in sync with the > host. Unfortunately guest tools aren't available for Solaris - but > that should be getting fixed soon. Is there any "VMware-tools for Solaris" package which works with Solaris 11/B61 ? Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Announcing NexentaCP(b65) with ZFS/Boot integrated
this doesn`t boot inside vmware (5.x or server 1.x) the VM crashes if you use virtual scsi disk. looks like a vmware issue This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: Open Sound System
Dev Mazumdar wrote: > The rumors are true, we're planning on open sourcing Open Sound (on June > 14th). We will be offering the source code under CDDL to Solaris and GPLv2 > for Linux BSD, OpenServer etc. > > At this time, we'd like to propose that Open Sound be started as a project > under the Desktop Community and should things start getting more interesting, > we'll spin off as our own community. Glynn Foster has agreed to be our > sponsor. > > More details and source code will be made available on June 14th. +1 Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Compiler mailing list?
Alan Coopersmith wrote: > William James wrote: > > No one from Sun's compiler team did bother to respond to my emails. > > They may not care about good customer support but I do. I think the > > best way is now to move forward and create a mailing list at > > opensolaris.org > > The most logical place to do that would be in the Tools community. > To do it there, you'ld just need to convince them to ask for it - try > discussing it on tools-discuss. I have a better idea. Since there appears to be demand in such a list (well, I have a bunch of generic (non-OpenSolaris) compiler questions, too... :-) ) I propose to simply create such a list (just a list (title: "Compiler (Sun Studio&&gcc) mailing list"), not a project) and make me the list admin - I already maintain three lists and a 4th won't hurt me much. Problem solved, customers satisfied (hopefully), rants gone... :-) Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blogs.sun.com invaded by marketing ?
Artem Kachitchkine wrote:
>
> > somehow this feels not good that "products" start to have blogs
>
> It can be interesting to meet real people behind a product share their
> views from the other side of the fence.
Right... and I don't disagree with that... but somehow the idea that
"products" start to have their own "blogs" ... sounds... uhm... weired.
Until now I always associated blogs with real living people and not
something like a "product" which starts writing it's blog ("Cyc" may be
an execption but AFAIK noone tried such an experiment yet... ;-/ ).
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) [EMAIL PROTECTED]
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: blogs.sun.com invaded by marketing ?
"W. Wayne Liauh" wrote: > > Today I stumbled over http://blogs.sun.com/olympus/ > > and > > http://blogs.sun.com/samqfs/ (erm, this is not > > thought as offense > > against the QFS or Olympus people but AFAIK > > group/project blogs should > > be in the project-specific blogging areas at > > opensolaris.org and not at > > blogs.sun.com) ... somehow this feels not good that > > "products" start to > > have blogs (except they start to run and think > > without human > > assistance... :-) ), e.g. people could think that the > > whole > > blogs.sun.com is just a marketing thing and not > > really a personal > > blogging site with real people... ;-( > > I have a very different opinion. I don't really see > anything wrong about Sun's people talking about their own > products. Erm, I don't have problems with Sun people talking abou Sun products. My point was that http://blogs.sun.com/olympus/ looks like a blog for the "olympus" product and http://blogs.sun.com/samqfs/ a blog for the "SamQFS" product. Both products are certainly not alive (anyone who disagrees please do the turing test for AI and post the results... :-) ) and do not match "one blog == one living person" ... Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] blogs.sun.com invaded by marketing ?
Hi! Today I stumbled over http://blogs.sun.com/olympus/ and http://blogs.sun.com/samqfs/ (erm, this is not thought as offense against the QFS or Olympus people but AFAIK group/project blogs should be in the project-specific blogging areas at opensolaris.org and not at blogs.sun.com) ... somehow this feels not good that "products" start to have blogs (except they start to run and think without human assistance... :-) ), e.g. people could think that the whole blogs.sun.com is just a marketing thing and not really a personal blogging site with real people... ;-( ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: SAM-QFS
Ted Pogue wrote: > > Project Overview: > > I propose the creation of a project on opensolaris.org, to bring to the > community Solaris host-based data services; namely the Storage Archive > Manager or SAM and the Solaris shared file system QFS. These data > services exist today and are distributed commercially by Sun as the Sun > StorageTek Storage Archive Manager and Sun StorageTek QFS shared file > system. The software is delivered unbundled commercially for Solaris 9 > and 10, but also is compiled for and runs on Open Solaris. [snip] +1 Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] ksh93-integration 2007-04-19 test binaries available for download...
s both the ksh93 builtin commands and the private Solaris API of previous libcmd versions. * The tarball was simply created from an OS/Net B61 proto / subdir via collecting the files listed by $ find $ROOT '!' -type d | sed 's/.*\/root_sparc\///' | egrep "/(lib|llib-l)(cmd|ast|shell|dll|pp)|/(ksh|rksh|pfksh)| include/ast|usr/ast/" | egrep -v cmdutils | sort #. * The tarballs do not provide a manual page for ksh93. Please use the manual page for ksh93r in the meantime. * "multiline" input mode was temporary disabled in the default configuration due small issues. * The ksh93 binaries can be build from source like this: (Instructions are for Solaris i386/AMD64; SPARC requires minor adjustments) 1. Pull sources and extract closed bin stuff (files can be obtained from opensolaris.org): $ mkdir test_x86 ; cd test_x86 $ svn checkout -r 694 svn://svn.genunix.org/on/ branches/ksh93/gisburn/prototype004/usr $ bzcat <../download/ on-closed-bins-nd-b61.i386.tar.bz2 | tar -xf - $ cd .. 2. Create opensolaris.sh. This is the usual opensolaris.sh with the paths adjusted to match your location of the sources. Example for the changes applies to opensolaris.sh (for my workspace): --- ./test1_x86/usr/src/tools/env/opensolaris.shThu Sep 14 13:17:59 2006 +++ ./opensolaris.shSun Jul 30 00:50:08 2006 @@ -43,10 +43,10 @@ # This is a variable for the rest of the script - GATE doesn't matter to # nightly itself -GATE=testws; export GATE +GATE=test1_x86;export GATE # CODEMGR_WS - where is your workspace at (or what should nightly name it) -CODEMGR_WS="/export/$GATE";export CODEMGR_WS +CODEMGR_WS="/home/test001/ksh93/on_build1/$GATE"; export CODEMGR_WS # Location of encumbered binaries. ON_CLOSED_BINS="$CODEMGR_WS/closed"; export ON_CLOSED_BINS 3. Run "bldenv": $ env - SHELL=$SHELL TERM=$TERM HOME=$HOME LOGNAME= $LOGNAME DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY LANG=C LC_ALL=C PAGER=less MANPATH=$MANPATH /opt/ onbld/bin/bldenv opensolaris.sh # 4. Build it (the quick way): $ cd test_x86/usr/src $ export ON_BUILD_AST_L10N_CATALOGS=1 CW_NO_SHADOW=1 $ time nice make setup 2>&1 | tee -a buildlog_setup.log $ time nice dmake install >buildlog.log 2>&1 ** Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=ksh93s+_beta release annoucement: http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/2007-April/002483.html [3]=ksh93r manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93r/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] ksh93-integration 2007-03-18 test binaries available for download
versions. * The tarball was simply created from an OS/Net B61 proto / subdir via collecting the files listed by $ find $ROOT '!' -type d | sed 's/.*\/root_sparc\///' | egrep "/(lib|llib-l)(cmd|ast|shell|dll|pp)|/(ksh|rksh|pfksh)| include/ast|usr/ast/" | egrep -v cmdutils | sort #. * The tarballs do not provide a manual page for ksh93. Please use the manual page for ksh93r in the meantime. * "multiline" input mode was temporary disabled in the default configuration due small issues. * The ksh93 binaries can be build from source like this: (Instructions are for Solaris i386/AMD64; SPARC requires minor adjustments) 1. Pull sources and extract closed bin stuff (files can be obtained from opensolaris.org): $ mkdir test_x86 ; cd test_x86 $ svn checkout -r 694 svn://svn.genunix.org/on/ branches/ksh93/gisburn/prototype004/usr $ bzcat <../download/ on-closed-bins-nd-b61.i386.tar.bz2 | tar -xf - $ cd .. 2. Create opensolaris.sh. This is the usual opensolaris.sh with the paths adjusted to match your location of the sources. Example for the changes applies to opensolaris.sh (for my workspace): --- ./test1_x86/usr/src/tools/env/opensolaris.shThu Sep 14 13:17:59 2006 +++ ./opensolaris.shSun Jul 30 00:50:08 2006 @@ -43,10 +43,10 @@ # This is a variable for the rest of the script - GATE doesn't matter to # nightly itself -GATE=testws; export GATE +GATE=test1_x86;export GATE # CODEMGR_WS - where is your workspace at (or what should nightly name it) -CODEMGR_WS="/export/$GATE";export CODEMGR_WS +CODEMGR_WS="/home/test001/ksh93/on_build1/$GATE"; export CODEMGR_WS # Location of encumbered binaries. ON_CLOSED_BINS="$CODEMGR_WS/closed"; export ON_CLOSED_BINS 3. Run "bldenv": $ env - SHELL=$SHELL TERM=$TERM HOME=$HOME LOGNAME= $LOGNAME DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY LANG=C LC_ALL=C PAGER=less MANPATH=$MANPATH /opt/ onbld/bin/bldenv opensolaris.sh # 4. Build it (the quick way): $ cd test_x86/usr/src $ export ON_BUILD_AST_L10N_CATALOGS=1 CW_NO_SHADOW=1 $ time nice make setup 2>&1 | tee -a buildlog_setup.log $ time nice dmake install >buildlog.log 2>&1 ** Links/References: [1]=ksh93-integration/migration project home page: http://www.opensolaris.org/os/project/ksh93-integration/ [2]=ksh93s+_beta release annoucement: http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/2007-April/002483.html [3]=ksh93r manual page: http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93r/man/man1/sh/ [4]=ksh93-integration mailinglist: http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/ ; please subscribe before posting (and please avoid flamewars) !! [5]=http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Virtual Console new release available NOW!
LingBo Tang wrote:
>
> This mail has been posted in virtual console discussion alias. The
> broadcasting is for those who may be interested in this feature on solaris.
>
> The new release for "Virtual Console" is available now, you can download
> and try for fun:
> http://opensolaris.org/os/project/vconsole/Downloads/
>
> There is a brief changes list for your reference:
>
> 1. Add many secure feature, like secure switch via vtdaemon, which
> require password during switching. Follow SMF policy for vtdaemon and
> console-login service etc.
>
> 2. Virtual terminal names are changed as "/dev/vt/#", and the 1st
> virtual terminal uses "/dev/console", which can be accessed via
> "Alt-F1". The second one uses "/dev/vt/2" accordingly.
One small request: Could you please rename /dev/vt/ to something longer,
e.g. /dev/vtconsole/ (the idea is to make the name more descriptive and
avoid possible "fun" with name collisions à la libcmd (see
http://www.opensolaris.org/os/community/arc/caselog/2006/561/onepager/))
?
> 3. You can keep pressing "Alt" key during switching between several
> virtual consoles.
Random ideas/thoughs:
- What about adding a capabilty to cycle through virtual terminals, e.g.
using the <+>/<-> keys and/or / ?
- A small tool would be nice to switch between virtual consoles from
scripts, add/remove consoles, enumerate consoles, dump current console
view to a file/stdout and set/get attributes, e.g. window title
- What about adding an option ("on" by default) to use the first line of
the virtual console to hold the "window title" ?
- Is there any plan for supporting an input method (e.g. to input
japanese/chinese/etc. (CC:'ing Ienup Sung <[EMAIL PROTECTED]> for
that...)) ?
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) [EMAIL PROTECTED]
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
[osol-discuss] bugs.opensolaris.org loosing bugs again ?!
Hi!
Is it possible that bugs.opensolaris.org is loosing bugs (again) ?
I am missing two bug reports:
1. "usr/src/cmd/perl/ build installs Subversion directories (.svn) in
the proto area" (note that this is not the exact title). That one was
filed seveal days ago and since noone from Sun could find the bug I
filed it again (now known as CR #6546677 ("usr/src/cmd/perl/ build
installs Subversion directories (.svn) in the proto area").
2. Today I filed a bug that the number of realtime signals is
insufficient, again noone can find the bug report in the triage queue or
elsewhere while my browser says:
-- snip --
Report a Bug
The bug has been reported.
-- snip --
Erm... I guess something is going horribly wrong here and needs some
immediate action. We may be loosing bug reports... ;-(
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) [EMAIL PROTECTED]
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
[osol-discuss] The "shell" project now open...
Hi! Just a quick announcement that the "shell" project is now open. What are we are doing ? The "shell project" should investigate and execute improvements related to shells and the shell environment in (Open-)Solaris: * Improve usuablity for plain users, including beginners and admins * Maintain/update various shells in Solaris (including bash, csh, ksh93, tcsh, zsh, /usr/bin/sh, /usr/xpg4/bin/sh, etc.) * Implement /etc/env.d/ to provide a way to add plugable shell scriptfragments for startup/shutdown of user sessions (login, interactive) * Improve the default shell environment, including: + Manual-page subsystem, e.g. the defaults of MANPATH, PAGER, etc., the related tools and their default configuration + Per-user temporary directories (TMPDIR), e.g. /tmp/ instead of putting everything into /tmp + More ideas welcome * Implement tools like /usr/sbin/chsh (change user shell) and /usr/bin/chfn (change finger/GCOS information) * Improve internationalisation (=i18n) and localisation (=l10n) support in the shell environment * Followup of the ksh93-integration project, including: + ksh93 busybox project + ksh93 Dtrace project + "shcomp" - shell script compiler and shbinexec kernel module * Start the work on a future POSIX shell standard which may include some of the newer ksh93/bash features. Why are we doing this ? * Improve the user-friendliness of the Solaris shell environment, via enhancements of the default setup, history, builtins etc Further information can be found on the project home page at http://www.opensolaris.org/os/project/shell/ or in the project mailinglist (see http://mail.opensolaris.org/mailman/listinfo/shell-discuss/ for instructions how to subscribe and/or access the list archives (please _subscribe_ before posting...)). Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Problems with "uata: [ID 464412 kern.warning] WARNING: timeout: reset target chno = 0 targ = 0" ...
Hi! My Solaris 11/B48 Ultra5 sometimes (while doing lots of disk I/O) hangs for a few seconds and then recovers while logging the following lines to /var/adm/messages -- snip -- $ tail /var/adm/messages Apr 2 02:50:37 jupiterb48 uata: [ID 464412 kern.warning] WARNING: timeout: reset target chno = 0 targ = 0 Apr 2 02:50:37 jupiterb48 uata: [ID 606412 kern.warning] WARNING: timeout: reset bus chno = 0 targ = 0 -- snip -- Does anyone know whether there is a bugid for this problem ? If "yes" - how serious is this issue ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Kconfig in Solaris?
thanks for your replies so far >This is not needed on Solaris, Solaris is fully modular since ~ 1992. >All drivers are loaded on demand. despite being modular or not - what i´m more interested in is to determine, which drivers and kernel features are inside solaris. is there a detailed list providing this besides solaris hcl ? in linux, i usually do "make menuconfig" and can have a detailed look into the kernel features and device drivers. i could also browse through the Kconfig files to know about "what`s inside". i have often come across linux features i never would have tried or would even know about if i had not taken a look into kernel configuration. so any help on getting some more transparency here is highly appreciated. regards roland ps: it`s absolutely _NOT_ my intention to blame solaris here (i like solaris as i like linux), but at them moment, solaris being less transparent for me. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Kconfig in Solaris?
Hello ! Is there something similar to Kconfig/Linux in Solaris - to make it possible to search through all the features a Solaris kernel provides ? or maybe thre is some comprehensive list of features and drivers a solaris kernel provides ? For example, for every Linux component, there is a modular Kconfig entry, with description: config EXT2_FS tristate "Second extended fs support" help Ext2 is a standard Linux file system for hard disks. To compile this file system support as a module, choose M here: the module will be called ext2. Be aware however that the file system of your root partition (the one containing the directory /) cannot be compiled as a module, and so this could be dangerous. If unsure, say Y. is there something similar in Solaris ? i have taken a quick look into uts at http://src.opensolaris.org bout couldn`t find appropriate information. regards roland This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] ksh93-integration 2007-03-18 test binaries available for download
Hi!
A new set of tarballs containing an OS/Net version of ksh93 [1] (based
on ksh93s_final_20070111 [2]) is now available from
http://www.opensolaris.org/os/project/ksh93-integration/downloads/2007-03-18/
These tarballs are intended to be installed over an existing OpenSolaris
i386 or SPARC installation and provide ksh93s_final_20070111 [2] for
testing and evaluation purposed ONLY.
Please report any problems/errors/bugs/comments to the ksh93-integration
project bugzilla [5] or the ksh93-integration mailinglist ([4]; please
subscribe before posting).
** Install instructions:
1. Download the tarball:
+ i386/AMD64:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20070318_snapshot_i386.tar.bz2
+ SPARC:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20070318_snapshot_sparc.tar.bz2
2. Verify the MD5 checksum:
+ i386/AMD64: MD5
(ksh93_integration_20070318_snapshot_i386.tar.bz2)=
1df38f1ade798a3fbff4f1250a8a211b
+ SPARC: MD5
(ksh93_integration_20070318_snapshot_sparc.tar.bz2)=
2a594b17b2283aef2154a164d020
3. Login as user "root":
4. Change directory to / and unpack the tarball with /usr/bin/tar
using the "xvof" option ("o" is very important to set the file
ownership to "root")
Example for i386/AMD64:
$ cd /tmp
$ wget
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20070318_snapshot_i386.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20070318_snapshot_i386.tar.bz2
MD5(ksh93_integration_20070318_snapshot_i386.tar.bz2)=
1df38f1ade798a3fbff4f1250a8a211b
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20070318_snapshot_sparc.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20070318_snapshot_sparc.tar.bz2
MD5(ksh93_integration_20070318_snapshot_sparc.tar.bz2)=
2a594b17b2283aef2154a164d020
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/svn_genunix_org_on_branches_ksh93_gisburn_prototype004_rev_500_647.diff.txt
(12MB, MD5 checksum is 0ea00a2f410f742ed8c99321f26d2842).
* 64bit binaries and libraries are now included (and used by
default if the hardware is 64bit capable)
* AST l10n utilities are stored in /usr/ast/bin/.
* If you wish to use ksh93 as login shell you have to create the
file /etc/shells (see shells(4) manual page) to include it in
the list of "allowed" system login shells:
Example /etc/shells file (created using $ cat
usr/src/lib/libc/port/gen/getusershell.c | egrep
'.*".*/(bin|sbin)/.*".*' | sed 's/[",]//g' | sort -u #):
-- snip --
/bin/bash
/bin/csh
/bin/jsh
/bin/ksh
/bin/ksh93
/bin/pfcsh
/bin/pfksh
/bin/pfsh
/bin/sh
/bin/tcsh
/bin/zsh
/sbin/jsh
/sbin/pfsh
/sbin/sh
/usr/bin/bash
/usr/bin/csh
/usr/bin/jsh
/usr/bin/ksh
/usr/bin/ksh93
/usr/bin/pfcsh
/usr/bin/pfksh
/usr/bin/pfsh
/usr/bin/sh
/usr/bin/tcsh
/usr/bin/zsh
/usr/sfw/bin/zsh
/usr/xpg4/bin/sh
-- snip --
* libcmd.so is replaced with a version which includes both the
ksh93 builtin commands and the private Solaris API of previous
libcmd versions.
* The tarball was simply created from an OS/Net B51 proto/ subdir
via collecting the files listed by $ find $ROOT '!' -type d |
sed 's/.*\/root_sparc\///' | egrep "/(lib|llib-l)(cmd|ast|shell
|dll|pp)|/(ksh|rksh|pfksh)|include/ast|usr/ast/" | egrep -v
cmdutils | sort #.
* The tarballs do not provide a manual page for ksh93. Please use
the manual page for ksh93r [3] in the meantime.
* "multiline" input mode was temporary disabled in the default
configuration due small issues.
* Build instructions and further notes can be found at
http://www.opensolaris.org/os/project/ksh93-integration/downloads/2007-03-18/
** Links/References:
[1]=ksh93-integration/migration project home page:
http://www.opensolaris.org/os/project/ksh93-integration/
[2]=ksh93s_final_20070111 release annoucement:
https://mailman.research.att.com/pipermail/ast-users/2007q1/001546.html
[3]=ksh93r manual page:
http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93r/man/man1/sh/
[4]=ksh93-integration mailinglist:
http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss/
; please subscribe before posting (and please avoid flamewars) !!
[5]=http://bugs.grommit.com/enter_bug.cgi?product=ksh93-integration
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) [EMAIL PROTECTED]
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
dtksh status / was: Re: [osol-discuss] About CDE bugs, errors
Hi! General note: The email below contains some of the old history of dtksh in Solaris and some background why the ksh93-integration project was created. I would prefer to take this as a page in a history book and _not_ as opportunity to come up with the old flamewars about dtksh, support or any of the other related issues. We're now working on getting ksh93 integrated into (Open-)Solaris and trying to leave the old problems behind us. Thanks! :-) John Plocher wrote: > Josh Hurst wrote: > > WIll Sun FIX dtksh? Both experts in this field - David Korn and Roland > > Mainz have complained about dtksh being utterly broken because Sun > > used an unofficial alpha code as ksh basis. > > It depends on how you define broken. Trying to be precise, several > potential definitions of /broken/ come to mind: > > o Isn't the latest version > o Doesn't have the features I wish it had > o Doesn't work as documented > o Corrupts my data > o Panic()s or dumps core > > In this case, dtksh faithfully delivers the functionality found > in the version it was based upon (M-12/28/93d). Yes and no. AFAIK it's not based on the final ksh93 version 'd' code. And I think based on the version used that this code should have never been shiped with a production system (see below ; AFAIK some of the CDE vendors took action and either fixed the problems or just upgraded the ksh93 basis to a newer version to leave the issues of ksh93d alpha simply behind...). > Inasmuch as it > reflects that old codebase, it isn't broken just because it has > not been updated or because it doesn't have modern features. > Will Sun FIX dtksh? Yes, if it is broken. The problem for dtksh is a little bit more compliciated. We have a larger set of dtksh applications created by our lab staff to get a "simple" GUI interface (erm... my fault... I teached them shell scripting and then showed them dtksh and over all the years this has evolved into a multi-megabyte colletion of scripts (last time I checked this the CVS contained around 12MB of script code) ... and sometimes I wish I would be able to understand what half the stuff does (at least the situation improved a little bit since they read the "Amiga User Interface Style Guide" (which stopped them from putting buttons and other GUI elements into places where you would not expect them...) ... :-) ) and based on this experience I think that the version of dtksh in other CDE versions like those in AIX+HP/UX is usually much more stable than the Solaris version (but I am not sure how it was done... the rumor ranges from manual bugfixing up to a simple update of the ksh93 basis). Solaris dtksh currently suffer from several weired "instablities" (e.g. scripts acting "randomly" or causing crashes) which are coming from the ksh93 version being used and some items are problems in the libDtWidget/Motif codebase. For example during the development of the init.d startup script for Xprt (Xprint server) we tried to use dtksh - it worked without problems on our side but many users complained about weired script failures. It turned out the problem was related to the many "hits" reported by "dbx -check access" and Rational Purity... and finally it was decided to use /usr/bin/ksh instead since dtksh was not reliable and any attempt to get this problem to the attention of Sun simply failed or was "ignored" (and "yes"... I've collected some amount of anger about that (and my preference would be to avoid the resurrection of this theme unless someone wants to see me exploding...) ... ;-( ). Another unfortunate issue is (or was) that Sun's customer support recommended dtksh to customers who wanted to use ksh93 in Solaris... which I think was very very "unfortunate" (which is an understatement...) ... some customers like Irek's company took a closer look at the problem, realised that the instabilites appeared to be known within Sun and then thought that Sun support was taking the mickey out of them and started deploying their own ksh93 binaries with their products instead. The same problems and rants had at least one good thing... the issue was resurrected a year ago (with much tears, anger and _lots_ of wrath about the situation) and resulted in the proposal which became the ksh93-integration project (going after dtksh was considered useless given the support status of CDE in Solaris). > Will Sun upgrade > dtksh to some /new/ set of specifications and features? Probably > not. I don't think it's possible to "fix" the ksh93d base of dtksh - the code is too old (it predates the day when ksh93 was opensourced and misses lots of bugfixes) and futher modifications will make the situation only much worse than it. I think the only workable option is to u
Re: [osol-discuss] Reading/posting via threaded web interface andNNTP (Was: SPAM-Attack via Jive..)
Mike Kupfer wrote:
>
> >>>>> "Eric" == Eric Boutilier <[EMAIL PROTECTED]> writes:
>
> Eric> ... In fact Gmane already is carrying some opensolaris lists (I
> Eric> don't know the who/when/why)...
>
> There should be some discussion of this in the opensolaris-discuss
> archives for July 2005 ("gmane and OpenSolaris").
>
> My understanding is that they are happy to gateway specific lists that
> people ask for. They were unenthusiastic about gatewaying "all the
> OpenSolaris lists" because of the sheer number.
Usual approach: Send them a Niagara machine... :-)
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) [EMAIL PROTECTED]
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
"Shells&&Utilities" community ? / was: Re: [osol-discuss] /usr/gnu project?
"Laszlo (Laca) Peter" wrote: > So the /usr/gnu proposal[1] was approved by PSARC. Obviously, the > reason for defining /usr/gnu wasn't theoretical -- it allows moving > GNU packages from /usr/sfw to /usr or /usr/gnu and it helps us > integrating more GNU packages into Solaris. We have already seen > the first few putbacks (m4, bison). [snip] What about creating a "Shells&&Utilities" community as umbrella for the ksh93-integration, shells and the /usr/gnu/ project (with [EMAIL PROTECTED] being the main list for now) ? That would cover most of the recent proposal, including this one, the cron thing etc. Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] What keeps "6414874 Revive le(7D) driver" frombeing done?
James Carlson wrote: > Tom Haynes writes: > > Are there any legal ramifications in open sourcing the le(7D) driver? [snip] > - whether the code itself was based on either code or information > (such as hardware manufacturer documentation) that is itself > encumbered. > > As well as potentially other things, such as the people who worked on > it, depending on the situation. It's no small matter, and the older > the code in question, the more difficult the effort. (And the deader > the hardware, the less reason to bother spending Sun's money that way. > 10Mb-only Ethernet? Who cares?) At least I and many other students would care since Ultra1 machines are still very widespread and they've become quite cheap (at least we have around 50-60 rotting in the cellar and I guess most german universities have similar stockpiles around). Problem is that OpenSolaris no longer supports this kind of machine which more or less ruines this opportunity to get more developers to work with OpenSolaris on SPARC machines... ;-( Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [website-discuss] Re: [osol-discuss] SPAM-Attack via Jive (AGAIN)... / was: [Fwd: [ksh93-integration-discuss] For sale:Nokian95:$300, Nokian93:$230]
Alan Burlison wrote: > Stephen Hahn wrote: > > Not easily, no. I'll look at the moderation idea, but the > > "subscribers only" request contradicts the aims of most legitimate > > forum posters. > > Another alternative would be to moderate the first few posts from new > registrants. This should stop the spammers who register a throwaway > email address, post spam and then disappear. What about adding an option for list admins that all emails from unsubscribed people (including Jive) are queued for moderation ? The current problem is triggered by the issue that Jive bypasses the whole mailman moderation/filter system... ;-( Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SPAM-Attack via Jive (AGAIN) ... / was: [Fwd: [ksh93-integration-discuss] For sale:Nokia n95:$300, Nokia n93:$230]
Stephen Hahn wrote: > > * Roland Mainz <[EMAIL PROTECTED]> [2007-02-18 15:10]: > > Is there a way to prevent things like the posting below ? For example is > > it possibe to reconfigure Jive to allow postings only for people who are > > subscribed to that list or make sure that such postings are queued for > > moderation by the list admins automatically ? > > Not easily, no. I'll look at the moderation idea, but the > "subscribers only" request contradicts the aims of most legitimate > forum posters. IMO the current concept is half-broken anyway since they don't get emails for the replies anyway. IMO people should use the list via normal email clients and not via the Jive add-on. To be honestly IKO the whole Jive software sucks whole galaxies - for example it breaks (by messing up the References:/In-Reply-To: headers) the threading in my email client (and normal Mozilla) which causes threads split up into tiny chunks that it has become difficult to follow the replies. At least I no longer read opensolaris-discuss@opensolaris.org on regular basis because there are too many threads broken into pieces by people posting via Jive, making it difficult to follow long discussions with many sub-topics. (And that is not the only problem with Jive - it messes up the email encoding, doesn't handle attachments properly and many other "little" details are broken etc. etc.). Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SPAM-Attack via Jive (AGAIN) ... / was: [Fwd: [ksh93-integration-discuss] For sale:Nokia n95:$300, Nokia n93:$230]
Hi! Is there a way to prevent things like the posting below ? For example is it possibe to reconfigure Jive to allow postings only for people who are subscribed to that list or make sure that such postings are queued for moderation by the list admins automatically ? Original Message Subject: [ksh93-integration-discuss] For sale:Nokia n95:$300, Nokia n93:$230 Date: Sun, 18 Feb 2007 12:52:35 PST From: Anna Kelly <[EMAIL PROTECTED]> Reply-To: Korn Shell 93 integration/migration project discussion <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] [b]International Industrial Limited is a professional supplier of mobile phones and their peripheral accessories. Through tremendous effort and extensive experience, our company expanded into the international distribution ma â?¦ wehave all brands of Mobile Phones,Ipods,xbox 360, Sidekicks,Nextels phone,Laptops for sell at cheap and affordable price this are original sealed box, With 1 year international warranty from the manufacturer, English & Spanish manual, Finland made. we delivery our customer item within 48hrs via UPS,DHL,FEDEX!! E-MAILS : [EMAIL PROTECTED] Motorola productâ?¦ Motorola v8 for $180usd Motorola v600 for $90usd Motorola v3 for $150usd Motorola rokr e1 for $160usd Motorola v3c for $180usd Motorola slvr l7 for $180usd Motorola q for $250usd Pamtero 600 for $155usd Nokia productâ?¦. Nokia n95 for $400usd Nokia n93 for $245usd Nokia n92 for $230usd Nokia n91 for $220usd Nokia n90 for $200usd Nokia n73 for $180usd Nokia n80 fof $190usd- Nokia n70 for $150usd Nokia n71 for $165usd Nokia neo for $260usd Nokia e60 for $180usd Nokia e61 for $190usd Nokia 6060 $200usd Nokia 6270 for $200usd Nokia neo for $250usd Nokia 6230i for $150usd Nokia 6630 for $120usd Nokia 6680 for $150usd Nokia 7610 for $120usd Nokia 7290 for $180usd Nokia 3250 for $200usd Nokia 7390 for $230usd Nokia 7380 for $200usd Nokia 7370 for $170usd Nokia 7360 for $100usd Nokia 6102 for $200usd Nokia e70 for $280usd Nokia e61 for $260usd Nokia 3250 for $250usd Nokia 6280 for $220usd Nokia 6270 for $200usd Nokia 6600 for $100usd Samsung productâ?¦. sSmsung serene for $200usd Samsung x810 for $185usd Samsung z700 for $190usd Samsung p860 for $170usd Samsung p850 for $200usd Samsung d500 for $160usd Samsung d600 for $180usd Samsung scgh i3000 $160usd Samsung e800 $110usd Sony ericsson product .. Sony ericsson z1010 for $185usd Sony ericsson w950i for $170usd Sony ericcson p990 for $150usd Sony ericsson w900 for $150usd Sony ericsson w600 for $135usd Sony ericsson p910i for $170usd Sony ericsson p900 for $150usd sony ericsson v600i for $140usd Sony ericssson w800i for $150usd Sony ericssson k800i for $250usd Sony ericssson k790i for $200usd Sony ericcson k500i for $120usd Sony ericsson w850 for $180 Sony ericsson j220 for $150 Sony ericsson j230 for $100 Sony ericsson p800 for $190 OTHERS LIKEâ?¦ i-mate jas jar for $150usd i-mate jam for $200usd i-mate k jam for $250usd i-mate jaq3 for $270usd Qtek 9600 for $260usd Sick kick for $130usd Side kick ii for $145usd Side kick iii for $180usd Nextel i930 for $130usd Nextel i860 for $112usd Nextel i870 for $140usd Pamtero 600 for $145usd Pamtero 650 for $170usd Treo 650 for $150usd Treo 700 for $210usd Treo 750 for $250usd Eten m 500 for $140usd Eten m 600 for $200usd Eten m700 glofish for $250usd Dvx-pod for $40usd Premium xbox 360 for $160 ps3 for $240usd Apple iPod nano Media Player 2GB for $100 Apple iPod nano Media Player 4GB for $130 Apple iPod nano Media Player 6GB for $190 Ipod video 30GB for $170USD Ipod video 60GB for $210USD Thereâ??s 1 year warranty for every phone sold out to Our company,We also give discount for large purchases, and our products are guaranteed brand new, with complete accessories. So Please feel free to contact us with your Quotation and Location SALES DIRECTOR: Anna E-MAILS : [EMAIL PROTECTED]/b] This message posted from opensolaris.org ___ ksh93-integration-discuss mailing list [EMAIL PROTECTED] http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Xorg memory allocation / was: Re: [osol-discuss] Re: Re: Re: Community participation (was GPLv3ravings)
Alan Coopersmith wrote: > Doug Scott wrote: > > Thanks for the explanation. This explains what is happening to > > firefox. Is Xorg > > looking into the problem, as it can be a real pain having to restart X > > every so often. > > I don't know of anyone at X.Org looking into the problem since it's pretty > universally believed to be a Firefox problem, not an Xorg one. Erm, no. It's a problem of the Gecko[1] engine (which tries to "upload" all pictures to the Xserver, including all frames of an animation (AFAIK timeless had a patch to limit this but the patch was ignored by Mozilla.org)) - but part of the problem is memory fragmentation in the Xserver itself (using |mmap()| partially defeats fragmentation because heap and |mmap()|'ed memory are coming from seperate areas in the address space). Please ping me when the first ksh93-integration putback is done... I had a patch for Xorg which fixed at least the fragmentation problem via using |mmap()| for larger allocations (>= 2*largepagesize with exception of scratch surfaces; current Xsun uses 1MB which is far too high) and switched the code to use larger pages on SPARC (64k) for heap and stack which resulted in a impressive performance boost, mainly thanks to better offscreen pixmap rendering performance and a faster freetype2 font rasterizer (and we may want to revisit the usage of temporary allocations in the Xserver, much could be saved here and it would solve fragmentation problems coming from asymetric allocation/deallocation of heap). [1]=The engine which is he basis for FireFox, Thunderbird, Mozilla etc. Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
