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] [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) ...
Hi!
2009-08-22: ksh93-integration update 2 tarballs for Solaris 11
Nevada+OpenSolaris/Indiana
These tarballs ([2]) are intended to be installed over an existing
Solaris Nevada/Indiana/OpenSolaris >= B110 i386 or SPARC installation
and provide ksh93t+_20090505 and the content described in PSARC/2009/248
("ksh93 update to 2009-03-10") and PSARC/2009/249 ("more ksh93 command
conversions").
Note that the binaries are provided for testing and evaluation purposes
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).
Quick links:
- Download&&install instructions:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/2009-08-22/
- Webrev:
http://cr.opensolaris.org/~gisburn/ksh93_integration_update2_20090822_webrev/
Differences to the previous test release (2009-07-02)
The only difference to the previous test release
(http://www.opensolaris.org/os/project/ksh93-integration/downloads/2009-07-02/)
is the fix for the /usr/bin/tail, /usr/xpg4/bin/tail and "tail"
utilities to handle FIFOs correctly (see
http://bugs.grommit.com/show_bug.cgi?id=630 ('AST "tail" fails to handle
FIFOs correctly' ; the patch (including a testcase) can be found at
http://bugs.grommit.com/attachment.cgi?id=331)).
The fixed "tail" utility can be identified based on it's version number
which should now print "2009-08-15":
-- snip --
$ tail
--version
version tail (AT&T Research) 2009-08-15
-- snip --
Highlights of this release:
- Many bugfixes to ksh93, it's infrastructure and other
commands, primarily focussing on stability, improved error
checking, performance and fixing support for large, complex
variable trees.
- The several commands have been updated (or added) and now
include common GNU+BSD+AST features, including:
/usr/bin/cksum
/usr/bin/cmp
/usr/bin/comm
/usr/bin/cut
/usr/bin/head
/usr/bin/join
/usr/bin/kill
/usr/bin/logname
/usr/bin/mkfifo
/usr/bin/paste
/usr/bin/print
/usr/bin/rev
/usr/bin/sleep
/usr/bin/sum
/usr/bin/tail
/usr/bin/tee
/usr/bin/test
/usr/bin/uniq
/usr/bin/wait
/usr/bin/wc
/usr/xpg4/bin/tail
(the full list of updated commands can be found below)
- The following bugs/RFEs will be fixed by this putback:
+--+
|BugID |Title |
|---+--|
|4701104|*tail* tail -r has limitations on un-mmappable files |
| |(/etc/mnttab) |
|---+--|
|6605478|ksh93 profile shell option does not work |
|---+--|
|6705126|first call to read does not honor new setting of |
| |HISTFILE |
|---+--|
|6764665|*libpp* Array overrun in libpp|
|---+--|
|6765756|*libast* Array overruns in libast |
|---+--|
|6769332|Recursive function+command substitutions terminate|
| |shell after 257 iterations|
|---+--|
|6778077|*ksh93* does not understand "THAW" as a signal for use|
| |with trap |
|---+--|
|6789247|[ku1] libast/ksh93 1-digit hexfloat base |
| |conversion rounds incorrectly |
|---+--|
|6790507|RFE: Update /usr/bin/tail and /usr/xpg4/bin/tail to |
| |AT&T AST "tail" |
|---+--|
|6791838|*ksh93* unset of a variable which is not set |
| |should return 0 |
|---+--|
|6793714|RFE: Update /usr/bin/comm to AT&T AST "comm" |
|---+--|
|6793719|RFE: Update /usr/bin/cut to AT&T AST "cut"|
|---+--|
|6793721|RFE: Update /usr/bin/paste to AT&T AST "paste"|
|---+--|
|6793722|RFE: Update /usr/bin/cmp to AT&T AST "cmp"|
|---+--|
|6793726|RFE: Update /usr/bin/uniq to AT&T AST "uniq"
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
[osol-discuss] [Annoucement] ksh93-integration update2 2009-07-02 binaries available for download (for Solaris 11 Nevada >= B110+OpenSolaris/Indiana) ...
Hi!
2009-07-02: ksh93-integration update 2 tarballs for Solaris 11
Nevada+OpenSolaris/Indiana
These tarballs ([2]) are intended to be installed over an existing
Solaris Nevada/Indiana/OpenSolaris >= B110 i386 or SPARC installation
and provide ksh93t+_20090505 and the content described in PSARC/2009/248
("ksh93 update to 2009-03-10") and PSARC/2009/249 ("more ksh93 command
conversions").
Note that the binaries are provided for testing and evaluation purposes
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).
Quick links:
- Download&&install instructions:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/2009-07-02/
- Webrev:
http://cr.opensolaris.org/~gisburn/ksh93_integration_update2_20090702_webrev/
Highlights of this release:
- Many bugfixes to ksh93, it's infrastructure and other
commands, primarily focussing on stability, improved error
checking, performance and fixing support for large, complex
variable trees.
- The several commands have been updated (or added) and now
include common GNU+BSD+AST features, including:
/usr/bin/cksum
/usr/bin/cmp
/usr/bin/comm
/usr/bin/cut
/usr/bin/head
/usr/bin/join
/usr/bin/kill
/usr/bin/logname
/usr/bin/mkfifo
/usr/bin/paste
/usr/bin/print
/usr/bin/rev
/usr/bin/sleep
/usr/bin/sum
/usr/bin/tail
/usr/bin/tee
/usr/bin/test
/usr/bin/uniq
/usr/bin/wait
/usr/bin/wc
/usr/xpg4/bin/tail
(the full list of updated commands can be found below)
- The following bugs/RFEs will be fixed by this putback:
+--+
|BugID |Title |
|---+--|
|4701104|*tail* tail -r has limitations on un-mmappable files |
| |(/etc/mnttab) |
|---+--|
|6605478|ksh93 profile shell option does not work |
|---+--|
|6705126|first call to read does not honor new setting of |
| |HISTFILE |
|---+--|
|6764665|*libpp* Array overrun in libpp|
|---+--|
|6765756|*libast* Array overruns in libast |
|---+--|
|6769332|Recursive function+command substitutions terminate|
| |shell after 257 iterations|
|---+--|
|6778077|*ksh93* does not understand "THAW" as a signal for use|
| |with trap |
|---+--|
|6789247|[ku1] libast/ksh93 1-digit hexfloat base |
| |conversion rounds incorrectly |
|---+--|
|6790507|RFE: Update /usr/bin/tail and /usr/xpg4/bin/tail to |
| |AT&T AST "tail" |
|---+--|
|6791838|*ksh93* unset of a variable which is not set |
| |should return 0 |
|---+--|
|6793714|RFE: Update /usr/bin/comm to AT&T AST "comm" |
|---+--|
|6793719|RFE: Update /usr/bin/cut to AT&T AST "cut"|
|---+--|
|6793721|RFE: Update /usr/bin/paste to AT&T AST "paste"|
|---+--|
|6793722|RFE: Update /usr/bin/cmp to AT&T AST "cmp"|
|---+--|
|6793726|RFE: Update /usr/bin/uniq to AT&T AST "uniq" |
|---+--|
|6793735|RFE: Update /usr/bin/wc to AT&T AST "wc" |
|---+--|
|6793744|RFE: Add /usr/share/doc/ksh/ for ksh93 documentation |
|---+--|
|6793747|RFE: Provide "print" builtin as /usr/bin/ |
||print for external applications |
|---+--|
|6793763|RFE: Update /usr/bin/ksh93 to ast-ksh.2009-05-05 |
|---+--|
|6794952|RFE: Enable "globstar" option in /etc/ksh.kshrc |
|---+--|
|6805792|[ Movin
[osol-discuss] [Annoucement] ksh93-integration update2 2009-05-11 binaries available for download (for Solaris 11 Nevada >= B110+OpenSolaris/Indiana) ...
Hi!
2009-05-11: ksh93-integration update 2 tarballs for Solaris 11
Nevada+OpenSolaris/Indiana
These tarballs ([2]) are intended to be installed over an existing
Solaris Nevada/Indiana/OpenSolaris >= B110 i386 or SPARC
installation and provide ksh93t+_20090505 and the content
described in PSARC/2009/248 ("ksh93 update to 2009-03-10")
and PSARC/2009/249 ("more ksh93 command conversions")
Note that the binaries are provided for testing and evaluation
purposes 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).
Highlights of this release:
- Many bugfixes to ksh93, it's infrastructure and other
commands, primarily focussing on stability, improved error
checking, performance and fixing support for large, complex
variable trees.
- The several commands have been updated (or added) and now
include common GNU+BSD+AST features, including:
/usr/bin/cksum
/usr/bin/cmp
/usr/bin/comm
/usr/bin/cut
/usr/bin/head
/usr/bin/join
/usr/bin/kill
/usr/bin/logname
/usr/bin/mkfifo
/usr/bin/paste
/usr/bin/print
/usr/bin/rev
/usr/bin/sleep
/usr/bin/sum
/usr/bin/tail
/usr/bin/tee
/usr/bin/test
/usr/bin/uniq
/usr/bin/wait
/usr/bin/wc
/usr/xpg4/bin/tail
(the full list of updated commands can be found below)
- The following bugs/RFEs will be fixed by this putback:
+---+
|BugID |Title |
|---+---|
|6605478|ksh93 profile shell option does not work |
|---+---|
|6705126|first call to read does not honor new setting |
| |of HISTFILE|
|---+---|
|6764665|*libpp* Array overrun in libpp |
|---+---|
|6765756|*libast* Array overruns in libast |
|---+---|
|6769332|Recursive function+command substitutions |
| |terminate shell after 257 iterations |
|---+---|
|6778077|*ksh93* does not understand "THAW" as a signal |
| |for use with trap |
|---+---|
|6789247|[ku1] libast/ksh93 1-digit hexfloat base conversion|
| |rounds incorrectly |
|---+---|
|6790507|RFE: Update /usr/bin/tail and /usr/xpg4/bin/tail |
| |to AT&T AST "tail" |
|---+---|
|6791838|*ksh93* unset of a variable which is not set |
| |should return 0|
|---+---|
|6793714|RFE: Update /usr/bin/comm to AT&T AST "comm" |
|---+---|
|6793719|RFE: Update /usr/bin/cut to AT&T AST "cut" |
|---+---|
|6793721|RFE: Update /usr/bin/paste to AT&T AST "paste" |
|---+---|
|6793722|RFE: Update /usr/bin/cmp to AT&T AST "cmp" |
|---+---|
|6793726|RFE: Update /usr/bin/uniq to AT&T AST "uniq" |
|---+---|
|6793735|RFE: Update /usr/bin/wc to AT&T AST "wc" |
|---+---|
|6793744|RFE: Add /usr/share/doc/ksh/ for ksh93 documentation |
|---+---|
|6793747|RFE: Provide "print" builtin as /usr/bin/ |
| |print for external applications|
|---+---|
|6793763|RFE: Update /usr/bin/ksh93 to ast-ksh.2009-05-05 |
|---+---|
|6794952|RFE: Enable "globstar" option in /etc/ksh.kshrc|
|---+---|
|6805792|[ku1] Moving local compound var into array does not|
| |work |
|---+---|
|6805794|[ku1] printf returns "invalid character constant" for |
| |$ printf "%dn" "'" |
|---+-
[osol-discuss] [Annoucement] ksh93-integration update2 2009-04-20 binaries available for download (for Solaris 11 Nevada >= B110+OpenSolaris/Indiana) ...
Hi!
2009-04-20: ksh93-integration update 2 tarballs for Solaris 11
Nevada+OpenSolaris/Indiana
These tarballs ([2]) are intended to be installed over an existing
Solaris Nevada/Indiana/OpenSolaris >= B110 i386 or SPARC
installation and provide ksh93t+_20090310 and the content
described in PSARC/2009/248 ("ksh93 update to 2009-03-10")
and PSARC/2009/249 ("more ksh93 command conversions")
Note that the binaries are provided for testing and evaluation
purposes 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).
Highlights of this release:
- Many bugfixes to ksh93, it's infrastructure and other
commands, primarily focussing on stability, improved error
checking, performance and fixing support for large, complex
variable trees.
- The several commands have been updated (or added) and now
include common GNU+BSD+AST features, including:
/usr/bin/cksum
/usr/bin/cmp
/usr/bin/comm
/usr/bin/cut
/usr/bin/head
/usr/bin/join
/usr/bin/kill
/usr/bin/logname
/usr/bin/mkfifo
/usr/bin/paste
/usr/bin/print
/usr/bin/rev
/usr/bin/sleep
/usr/bin/sum
/usr/bin/tail
/usr/bin/tee
/usr/bin/test
/usr/bin/uniq
/usr/bin/wait
/usr/bin/wc
/usr/xpg4/bin/tail
(the full list of updated commands can be found below)
Install instructions:
*** Basic installation:
1. Download the tarball:
+ i386/AMD64:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20090420_snapshot_i386.tar.bz2
+ SPARC:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20090420_snapshot_sparc.tar.bz2
2. Verify the MD5 checksum:
+ i386/AMD64: MD5
(ksh93_integration_20090420_snapshot_i386.tar.bz2)=
c5697c5bc5f14bfa6a2c5708ed25e4f2
+ SPARC: MD5
(ksh93_integration_20090420_snapshot_sparc.tar.bz2)=
e0cc96c747f87094388abd62c4694816
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
$ /usr/sfw/bin/wget \
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20090420_snapshot_i386.tar.bz2
$ sum -x md5 ksh93_integration_20090420_snapshot_i386.tar.bz2
c5697c5bc5f14bfa6a2c5708ed25e4f2
ksh93_integration_20090420_snapshot_i386.tar.bz2
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20090420_snapshot_sparc.tar.bz2
$ sum -x md5 ksh93_integration_20090420_snapshot_sparc.tar.bz2
e0cc96c747f87094388abd62c4694816
ksh93_integration_20090420_snapshot_sparc.tar.bz2
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/svn_genunix_org_on_branches_ksh93_gisburn_prototype021_rev_1446_1483.diff.txt
, 1.82MB, MD5 checksum is afbc63ce43d9f416d2500941bb92c0d1).
* "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 1483 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 ..
[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) ...
Hi!
2008-11-14: ksh93 update tarballs for Solaris Nevada+Indiana
These tarballs are intended to be installed over an existing OpenSolaris
>= B84 i386 or SPARC installation and provide ast-ksh.2008-11-04
>(ksh93t_20081104) and match PSARC/2008/094 ("ksh93 Update 1" ;
>http://www.opensolaris.org/os/community/arc/caselog/2008/094)/ +
>PSARC/2008/344 ("ksh93 Integration Update 1 Amendments 1" ;
>http://www.opensolaris.org/os/community/arc/caselog/2008/344/)
Note that the binaries are provided for testing and evaluation purposes
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).
Highlights of this release:
- /etc/ksh.kshrc now sets a default prompt (PS1) for interactive
sessions (see NOTES below)
- Many bugfixes, primarily focussing on stability, improved error
checking, performance and fixing support for large, complex
variable trees.
- Many closed-source binaries are replaced with opensource versions
- The shell script compiler "shcomp" is now included
- Many new demos including:
- "shircbot" (IRC bot demo)
- "crawlsrccomments" (two-phased source code comment+license
extrator which uses serialised variable trees for
storage+caching)
- "filemutexdemo1" (demo to show ksh93's new type system and
an implementation of filesystem-based read/write locks)
- "multifollow" (poll(1) demo which run multiple "tail -f")
- "shnote" (utility to read/write pastebin.ca)
- "shtwitter" (access twitter.com service and push blog
entries)
- "shcalc" (command-line ISO C99 floating-point calculator)
- "shpiano" (audio demo)
- "shtinyurl" (tool to generate short tinyurl.com URLs)
- "svcproptree1" (SMF demo)
- "test_net_sctp" (SCTP protocol demo)
- "shman" (early prototype of a /usr/bin/man rewrite)
- "xmldocumenttree1" (XML parser demo)
... and much more...
Install instructions:
*** Basic installation:
1. Download the tarball:
+ i386/AMD64:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20081114_snapshot_i386.tar.bz2
+ SPARC:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20081114_snapshot_sparc.tar.bz2
2. Verify the MD5 checksum:
+ i386/AMD64: MD5
(ksh93_integration_20081114_snapshot_i386.tar.bz2)=
2a757c0e9476962d55fda9210e14c512
+ SPARC: MD5
(ksh93_integration_20081114_snapshot_sparc.tar.bz2)=
c9fe186651073fd84e974bd4f77667cc
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
$ /usr/sfw/bin/wget
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20081114_snapshot_i386.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20081114_snapshot_i386.tar.bz2
MD5(ksh93_integration_20081114_snapshot_i386.tar.bz2)=
2a757c0e9476962d55fda9210e14c512
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20081114_snapshot_sparc.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20081114_snapshot_sparc.tar.bz2
MD5(ksh93_integration_20081114_snapshot_sparc.tar.bz2)=
c9fe186651073fd84e974bd4f77667cc
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/svn_genunix_org_on_branches_ksh93_gisburn_prototype012_rev_1175_1285.diff.txt
, 4.5MB, MD5 checksum is 8df042b6f4768158883348dba1628c19).
* "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 ~~32
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 usr/-directory of the 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
[osol-discuss] [Annoucement] ksh93-integration update1 2008-08-10 binaries available for download (for Solaris Nevada >= B84+Indiana) ...
Hi!
2008-08-10: ksh93 update tarballs for Solaris Nevada+Indiana
These tarballs are intended to be installed over an existing OpenSolaris
>= B84 i386 or SPARC installation and provide ast-ksh.2008-07-25
>(ksh93t_20080725) and match PSARC/2008/094 ("ksh93 Update 1" ;
>http://www.opensolaris.org/os/community/arc/caselog/2008/094)/ +
>PSARC/2008/344 ("ksh93 Integration Update 1 Amendments 1" ;
>http://www.opensolaris.org/os/community/arc/caselog/2008/344/)
Note that the binaries are provided for testing and evaluation purposes
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).
Highlights of this release:
- /etc/ksh.kshrc now sets a default prompt for interactive sessions
(see NOTES below)
- Many bugfixes, primarily focussing on stability, improved error
checking, performance and fixing support for large, complex
variable trees.
- Many closed-source binaries are replaced with opensource versions
- The shell script compiler "shcomp" is now included
- Many new demos including:
- "crawlsrccomments" (two-phased source code comment+license
extrator which uses serialised variable trees for
storage+caching)
- "filemutexdemo1" (demo to show ksh93's new type system and
an implementation of filesystem-based read/write locks)
- "multifollow" (poll(1) demo which run multiple "tail -f")
- "shnote" (utility to read/write pastebin.ca)
- "shtwitter" (access twitter.com service and push blog
entries)
- "shpiano" (audio demo)
- "shtinyurl" (tool to generate short tinyurl.com URLs)
- "svcproptree1" (SMF demo)
- "test_net_sctp" (SCTP protocol demo)
- "shman" (early prototype of a /usr/bin/man rewrite)
- "xmldocumenttree1" (XML parser demo)
... and much more...
Install instructions:
*** Basic installation:
1. Download the tarball:
+ i386/AMD64:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20080810_snapshot_i386.tar.bz2
+ SPARC:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20080810_snapshot_sparc.tar.bz2
2. Verify the MD5 checksum:
+ i386/AMD64: MD5
(ksh93_integration_20080810_snapshot_i386.tar.bz2)=
5c381f9341207843dbfd41636a6d0a9b
+ SPARC: MD5
(ksh93_integration_20080810_snapshot_sparc.tar.bz2)=
fde870ae2dad69fbd9c54f5b3939e9f9
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
$ /usr/sfw/bin/wget
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20080810_snapshot_i386.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20080810_snapshot_i386.tar.bz2
MD5(ksh93_integration_20080810_snapshot_i386.tar.bz2)=
5c381f9341207843dbfd41636a6d0a9b
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20080810_snapshot_sparc.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20080810_snapshot_sparc.tar.bz2
MD5(ksh93_integration_20080810_snapshot_sparc.tar.bz2)=
fde870ae2dad69fbd9c54f5b3939e9f9
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/svn_genunix_org_on_branches_ksh93_gisburn_prototype011_rev_974_1163.diff.txt
(4.5MB, MD5 checksum is de8bc41480f7cdb0fc4cd7ec837dd62f).
* /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 ~~20
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 usr/-directory of the prototype011 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+ [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 ca
[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) ...
Hi!
2008-06-24: ksh93 update tarballs for Solaris Nevada >= B84+Indiana
These tarballs are intended to be installed over an existing
OpenSolaris >= B84 i386 or SPARC installation and provide
ksh93t-_20080614 and match PSARC/2008/094 ("ksh93 Update 1" ;
http://www.opensolaris.org/os/community/arc/caselog/2008/094)/ +
PSARC/2008/344 ("ksh93 Integration Update 1 Amendments 1" ;
http://www.opensolaris.org/os/community/arc/caselog/2008/344/)
Note that the binaries are provided for testing and evaluation
purposes 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).
** Highlights of this release:
- /etc/ksh.kshrc now sets a default prompt for interactive sessions
(see NOTES below) and enables the "multiline" input mode.
- Many bugfixes, primarily focussing on stability, improved error
checking, performance and fixing support for large, complex
variable trees.
- Many closed-source binaries are replaced with opensource versions
- The shell script compiler "shcomp" is now included
- Many new demos including:
- "crawlsrccomments" (two-phased source code comment+license
extrator which uses serialised variable trees for
storage+caching)
- "filemutexdemo1" (demo to show ksh93's new type system and
an implementation of filesystem-based read/write locks)
- "multifollow" (poll(1) demo which run multiple "tail -f")
- "shnote" (utility to read/write pastebin.ca)
- "shtwitter" (access twitter.com service and push blog
entries)
- "shpiano" (audio demo)
- "shtinyurl" (tool to generate short tinyurl.com URLs)
- "svcproptree1" (SMF demo)
- "test_net_sctp" (SCTP demo)
- "shman" (early prototype of a /usr/bin/man rewrite)
- "xmldocumenttree1" (XML parser demo)
... and much more...
** Major changes since the 2008-06-17 release:
- Fixed and re-enabled the "multiline" input mode
per community requests
- Updated demo code (mainly the /usr/bin/man-rewrite
proof-of-concept demo "shman.sh")
** Install instructions:
1. Download the tarball:
+ i386/AMD64:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20080624_snapshot_i386.tar.bz2
+ SPARC:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20080624_snapshot_sparc.tar.bz2
2. Verify the MD5 checksum:
+ i386/AMD64: MD5
(ksh93_integration_20080624_snapshot_i386.tar.bz2)=
e8d8a25ae9121a087a9a1ee9840bff40
+ SPARC: MD5
(ksh93_integration_20080624_snapshot_sparc.tar.bz2)=
7903cfdfb3ec2f43b355aab1cbc18123
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_20080624_snapshot_i386.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20080624_snapshot_i386.tar.bz2
MD5(ksh93_integration_20080624_snapshot_i386.tar.bz2)=
e8d8a25ae9121a087a9a1ee9840bff40
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20080624_snapshot_sparc.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20080624_snapshot_sparc.tar.bz2
MD5(ksh93_integration_20080624_snapshot_sparc.tar.bz2)=
7903cfdfb3ec2f43b355aab1cbc18123
# cd /
# sync ; sync
# bzcat @:$ for normal
users and @:# for
user "root"; the prompt length itself is limited to ~~20
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 usr/-directory of the prototype011 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
[osol-discuss] ksh93-integration 2008-06-17 update binaries available for download (for Solaris Nevada >= B84+Indiana) ...
Hi!
2008-06-17: ksh93 update tarballs for Solaris Nevada+Indiana
These tarballs are intended to be installed over an existing OpenSolaris
>= B84 i386 or SPARC installation and provide ksh93t-_20080614 and match
>PSARC/2008/094 ("ksh93 Update 1" ;
>http://www.opensolaris.org/os/community/arc/caselog/2008/094)/ +
>PSARC/2008/344 ("ksh93 Integration Update 1 Amendments 1" ;
>http://www.opensolaris.org/os/community/arc/caselog/2008/344/)
Note that the binaries are provided for testing and evaluation purposes
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).
** Highlights of this release:
- /etc/ksh.kshrc now sets a default prompt for interactive sessions
(see NOTES below)
- Many bugfixes, primarily focussing on stability, improved error
checking, performance and fixing support for large, complex
variable trees.
- Many closed-source binaries are replaced with opensource versions
- The shell script compiler "shcomp" is now included
- Many new demos including:
- "crawlsrccomments" (two-phased source code comment+license
extrator which uses serialised variable trees for
storage+caching)
- "filemutexdemo1" (demo to show ksh93's new type system and
an implementation of filesystem-based read/write locks)
- "multifollow" (poll(1) demo which run multiple "tail -f")
- "shnote" (utility to read/write pastebin.ca)
- "shtwitter" (access twitter.com service and push blog
entries)
- "shpiano" (audio demo)
- "shtinyurl" (tool to generate short tinyurl.com URLs)
- "svcproptree1" (SMF demo)
- "test_net_sctp" (SCTP demo)
- "shman" (early prototype of a /usr/bin/man rewrite)
- "xmldocumenttree1" (XML parser demo)
... and much more...
** Install instructions:
1. Download the tarball:
+ i386/AMD64:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20080617_snapshot_i386.tar.bz2
+ SPARC:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20080617_snapshot_sparc.tar.bz2
2. Verify the MD5 checksum:
+ i386/AMD64: MD5
(ksh93_integration_20080617_snapshot_i386.tar.bz2)=
efce5d0f4417b7d5579370c4c14280b7
+ SPARC: MD5
(ksh93_integration_20080617_snapshot_sparc.tar.bz2)=
247ecbcfd962e24d115b033c97437ab3
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_20080617_snapshot_i386.tar.bz2
$ /usr/sfw/bin/openssl md5 \
ksh93_integration_20080617_snapshot_i386.tar.bz2
MD5(ksh93_integration_20080617_snapshot_i386.tar.bz2)=
efce5d0f4417b7d5579370c4c14280b7
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20080617_snapshot_sparc.tar.bz2
$ /usr/sfw/bin/openssl md5 \
ksh93_integration_20080617_snapshot_sparc.tar.bz2
MD5(ksh93_integration_20080617_snapshot_sparc.tar.bz2)=
247ecbcfd962e24d115b033c97437ab3
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/svn_genunix_org_on_branches_ksh93_gisburn_prototype011_rev_974_1122.diff.txt
; 4.5MB, MD5 checksum is
2bfe00f5552bd0ef97d4f19feb7d5727).
* /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 ~~20
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 usr/-directory of the prototype011 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+ [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.
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) ...
Hi!
2008-02-29: ksh93 update tarballs for OpenSolaris
These tarballs are intended to be installed over an existing OpenSolaris
>= B72 + Indiana distribution i386 or SPARC installation and provide
>ksh93s+_20080202 (the content matches PSARC/2008/094
>(http://www.opensolaris.org/os/community/arc/caselog/2008/094/)).
Note that the binaries are provided for testing and evaluation purpose
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).
** Highlights of this release:
- "multiline" editor mode allows to edit lines in a similar fashion
as "readline"-based applications like "bash"
- /etc/ksh.kshrc now sets a default prompt for interactive sessions
(see NOTES below)
- Many bugfixes
- Many closed-source binaries are replaced with opensource versions
- The shell script compiler "shcomp" is now included
- Many new demos including:
- "shnote" (utilty to read/write pastebin.ca)
- "shtwitter" (access twitter.com service and push blog entries)
- "shpiano" (audio demo)
- "shtinyurl" (tool to generate short tinyurl.com URLs)
- "shman" (early prototype of a /usr/bin/man rewrite)
- "svcproptree1" (SMF demo)
- "xmldocumenttree1" (XML parser demo)
- "test_net_sctp" (SCTP demo)
- "multifollow" (poll(1) demo which run multiple "tail -f")
... and much more...
** Install instructions:
1. Download the tarball:
+ i386/AMD64:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20080229_snapshot_i386.tar.bz2
+ SPARC:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20080229_snapshot_sparc.tar.bz2
2. Verify the MD5 checksum:
+ i386/AMD64: MD5
(ksh93_integration_20080229_snapshot_i386.tar.bz2)=
7a1bae17aeeccd62df31a1c5d8295554
+ SPARC: MD5
(ksh93_integration_20080229_snapshot_sparc.tar.bz2)=
45c11e457118232f7fd1d07b0f178b1b
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_20080229_snapshot_i386.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20080229_snapshot_i386.tar.bz2
MD5(ksh93_integration_20080229_snapshot_i386.tar.bz2)=
7a1bae17aeeccd62df31a1c5d8295554
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20080229_snapshot_sparc.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20080229_snapshot_sparc.tar.bz2
MD5(ksh93_integration_20080229_snapshot_sparc.tar.bz2)=
45c11e457118232f7fd1d07b0f178b1b
# cd /
# sync ; sync
# bzcat @:$ for normal
users and @:# for
user "root"; the prompt length itself is limited to ~~20
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.
* Users of B72, B73, B74 and B75 (anything ?B75 has already been
fixed) which like to use ksh93 as login shell must create the
/etc/shells (see shells(4) manual page) to include it in the
list of "allowed" system login shells (otherwise dtlogin will
refuse graphical login):
Example /etc/shells file (created using
$ cat usr/src/lib/libc/port/gen/getusershell.c |
egrep '.*".*/(bin|sbin)/.*".*' | sed 's/[",]//g' | sort -u #):
/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
* 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.
* The ksh93 binaries can be build from source like this:
(Instruction
[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) ...
Hi!
2007-11-05: ksh93 _update tarballs_ for OpenSolaris >= B72
These tarballs are intended to be installed over an existing OpenSolaris
i386 or SPARC installation (>= Nevada B72) to update the provided ksh93
installation to ksh93sü_20071101.
Note that the binaries are provided 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].
** Highlights of this release:
- "multiline" editor mode allows to edit lines in a similar fashion as
"readline"-based applications like "bash"
- /etc/ksh.kshrc now sets a default prompt for interactive sessions (see
NOTES below)
- Many bugfixes
- Many closed-source binaries are replaced with opensource versions
- The shell script compiler "shcomp" is now included
- Many new demos including:
- "shnote" (utilty to read/write pastebin.ca)
- "shtwitter" (access twitter.com service and push blog entries)
- "shpiano" (audio demo)
- "shtinyurl" (tool to generate short tinyurl.com URLs)
- "shman" (early prototype of a /usr/bin/man rewrite)
- "svcproptree1" (SMF demo)
- "xmldocumenttree1" (XML parser demo)
- "test_net_sctp" (SCTP demo)
- "multifollow" (poll(1) demo which run multiple "tail -f")
... and much more...
** Install instructions:
1. Download the tarball:
+ i386/AMD64:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20071105_snapshot_i386.tar.bz2
+ SPARC:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20071105_snapshot_sparc.tar.bz2
2. Verify the MD5 checksum:
+ i386/AMD64: MD5
(ksh93_integration_20071105_snapshot_i386.tar.bz2)=
86820df14a8931706a7d6200dc41a889
+ SPARC: MD5
(ksh93_integration_20071105_snapshot_sparc.tar.bz2)=
396b9e135789c6c5c206547242dca842
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_20071105_snapshot_i386.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20071105_snapshot_i386.tar.bz2
MD5(ksh93_integration_20071105_snapshot_i386.tar.bz2)=
86820df14a8931706a7d6200dc41a889
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20071105_snapshot_sparc.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20071105_snapshot_sparc.tar.bz2
MD5(ksh93_integration_20071105_snapshot_sparc.tar.bz2)=
396b9e135789c6c5c206547242dca842
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/svn_genunix_org_on_branches_ksh93_gisburn_prototype010_rev_866_894.diff.txt
;
3MB, MD5 checksum is c6590f068ff81cb08a7d7d3fbbac4756).
* "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 ~~20
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.
* Users of B72, B73, B74 and B75 (anything >=B75 has already been
fixed) which like to use ksh93 as login shell must create the
/etc/shells (see shells(4) manual page) to include it in the
list of "allowed" system login shells (otherwise dtlogin will
refuse graphical login):
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 --
* 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 s
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) ...
Hi!
[If you run Solaris 11 >= B72 please ignore this]
A new set of tarballs containing an OS/Net version of ksh93 [1] (based
on ksh93s+_beta_20070418 [2]) is now available from
http://www.opensolaris.org/os/project/ksh93-integration/downloads/2007-10-31/
These tarballs are intended to be installed over an existing OpenSolaris
i386 or SPARC installation (>= Nevada B61 and < Nevada B72 ; this
tarball is no longer neccesary if you run Nevada B72 or higher!!) and
provide ksh93s+_beta_20070418 [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].
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
WARNING: These tarballs are NOT needed if you run Solaris 11/B72 or
higher (ksh93 was integrated in B72 [6]) - these tarballs are only
intended as a quick way to add ksh93 to existing pre-B72 machines (such
as the Sun OS/Net buildfarm machines).
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
** Install instructions:
1. Download the tarball:
+ i386/AMD64:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20071031_snapshot_i386.tar.bz2
+ SPARC:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20071031_snapshot_sparc.tar.bz2
2. Verify the MD5 checksum:
+ i386/AMD64: MD5
(ksh93_integration_20071031_snapshot_i386.tar.bz2)=
3dce7c8cf3cfef92224d9da54589bfe6
+ SPARC: MD5
(ksh93_integration_20071031_snapshot_sparc.tar.bz2)=
9265f2aa0957427a394f44084d85268e
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_20071031_snapshot_i386.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20071031_snapshot_i386.tar.bz2
MD5(ksh93_integration_20071031_snapshot_i386.tar.bz2)=
3dce7c8cf3cfef92224d9da54589bfe6
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20071031_snapshot_sparc.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20071031_snapshot_sparc.tar.bz2
MD5(ksh93_integration_20071031_snapshot_sparc.tar.bz2)=
9265f2aa0957427a394f44084d85268e
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/docs/ksh93s/
** Notes:
* This tarball matches ksh93s+ (=ast-ksh.2007-04-18) with many
many changes since the last version. Please test the binaries
extensively.
* The binaries now are build from a B61-based tree and require
SXCR B61 or higher
* Sources/diffs:
+ The diffs between Solaris Nevada B61 and the current
ksh93-integration tree can be obtained via
svn diff -r 676:885
svn://svn.genunix.org/on/branches/ksh93/gisburn/prototype005/usr
or as unified diff from
http://www.opensolaris.org/os/project/ksh93-integration/downloads/svn_genunix_org_on_branches_ksh93_gisburn_prototype005_rev_676_885.diff.txt
(12MB, MD5 checksum is bf01ae796575aa72137c9cd54315a74d).
* 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/.
* Starting with ksh93s+ multibyte characters can be used for
variable/function/etc.-names. Please test this functionality
extensively.
* was added to emacs/gmacs mode to clear the screen
(per community requests and to be in sync with bash)
* 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 #):
/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
* 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 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 pag
[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...
http post
{
print -- "${request}"
print -- "${content}"
} >&${netfd}
# process reply
parse_http_response httpresponse <&${netfd}
response="$(cat <&${netfd})"
# close connection
exec {netfd}<&-
if [[ "${response}" = ~(E).*SUCCESS.* ]] ; then
typeset response_token="${response/~(E).*SUCCESS:/}"
print "SUCCESS: http://opensolaris.pastebin.ca/${response_token}";
# write history entry
typeset histrec=(
title="${mimeform.form[0].data}"
description="${mimeform.form[3].data}"
providertoken="${response_token}"
provider="opensolaris.pastebin.ca"
url="http://opensolaris.pastebin.ca/${response_token}";
)
history_write_record histrec
else
print "ERROR: ${response}"
return 1
fi
return 0
}
function get_note_pastebin_ca
{
typeset recordname="$1"
integer netfd # http stream number
case "${recordname}" in
~(Elr)[0-9][0-9]*)
# pass-through
;;
~(Elr)http://opensolaris.pastebin.ca/raw/[0-9]*)
recordname="${recordname/~(El)http:\/\/opensolaris.pastebin.ca\/raw\//}"
;;
~(Elr)http://opensolaris.pastebin.ca/[0-9]*)
recordname="${recordname/~(El)http:\/\/opensolaris.pastebin.ca\//}"
;;
*)
fatal_error "Unsupported record name ${recordname}."
esac
print -u2 -f "# Record name is '%s'\n" "${recordname}"
typeset url_host="opensolaris.pastebin.ca"
typeset url_path="/raw/${recordname}"
typeset url="http://${url_host}${url_path}";
# I hereby curse Solaris for not having an entry for "http" in /etc/services
# open TCP channel
exec {netfd}<>"/dev/tcp/${url_host}/80"
(( $? != 0 )) && { print -u2 "Couldn't open connection to ${url_host}." ;
return 1 ; }
# send HTTP request
request="GET ${url_path} HTTP/1.1\n"
request+="Host: ${url_host}\n"
request+="User-Agent: ${http_user_agent}\n"
request+="Connection: close\n"
print -u${netfd} -- "${request}\n"
# collect response and send it to stdout
parse_http_response httpresponse <&${netfd}
cat <&${netfd}
# close connection
exec {netfd}<&-
print # add newline
return 0
}
function usage
{
OPTIND=0
getopts -a "${progname}" "${USAGE}" OPT '-?'
exit 2
}
# program start
builtin basename
builtin cat
builtin date
builtin uname
typeset progname="$(basename "${0}")"
# HTTP protocol client identifer
typeset -r http_user_agent="shnote/ksh93 (2007-09-18; $(uname -s -r -p)"
# name of history log (the number after "history" is some kind of version
# counter to handle incompatible changes to the history file format)
typeset -r history_file="${HOME}/.shnote/history0.txt"
USAGE=$'
[-?\n@(#)\$Id: shnote (Roland Mainz) 2007-09-18 \$\n]
[-author?Roland Mainz <[EMAIL PROTECTED]
[+NAME?shnote - read/write text data to internet clipboards]
[+DESCRIPTION?\bshnote\b is a small utilty which can read and write text
data to internet "clipboards" such as opensolaris.pastebin.ca.]
[+?The first arg \bmethod\b describes one of the methods, "put" saves a string
to the internet clipboard, returning an identifer and the full URL
where the data are stored. The method "get" retrives the raw
information using the identifer from the previous "put" action.]
[+?The second arg \bstring\b contains either the string data which should be
stored on the clipboard using the "put" method, the "get" method uses
this information as identifer to retrive the raw data from the
clipboard.]
method [ string ]
[+SEE ALSO?\bksh93\b(1), \brssread\b(1), http://opensolaris.pastebin.ca]
'
while getopts -a "${progname}" "${USAGE}" OPT ; do
#printmsg "## OPT=|${OPT}|, OPTARG=|${OPTARG}|"
case ${OPT} in
*)usage ;;
esac
done
shift $((OPTIND-1))
typeset method="$1"
shift
# todo: "history" mode
case "${method}" in
put) put_note_pastebin_ca "$@" ; exit $? ;;
get) get_note_pastebin_ca "$@" ; exit $? ;;
hist) print_history "$@"; exit $? ;;
*) usage ;;
esac
fatal_error "not reached."
# EOF.
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
[osol-discuss] Small experiment with "twitter.com" and /var/adm/messages ...
ode, cookies etc.
function parse_http_response
{
nameref response=$1
typeset h c i
IFS=$' \t' read -r h c # read HTTP/1.[01]
[[ "$h" != ~(Eil)HTTP/.* ]] && { print -u2 "$0: HTTP/ header missing" ;
return 1 ; }
response.httpcode="$c"
# skip remaining headers
while IFS='' read -r i ; do
[[ "$i" = $'\r' ]] && break
done
return 0
}
function encode_http_basic_auth
{
typeset user="$1"
typeset passwd="$2"
typeset s
integer s_len
typeset -b base64var
# ksh93 binary variables use base64 encoding, the same as the
# HTTP basic authentification. We only have to read the
# plaintext user:passwd string into the binary variable "base64var"
# and then print this variable as ASCII.
s="${user}:${passwd}"
s_len="${#s}"
print -n "${s}" | read -N${s_len} base64var
print -- "${base64var}"
return 0
}
function put_twitter_message
{
#set -o xtrace
[[ "$SHTWITTER_USER" = "" ]] && fatal_error "SHTWITTER_USER not set."
[[ "$SHTWITTER_PASSWD" = "" ]] && fatal_error "SHTWITTER_PASSWD not set."
# site setup
typeset url_host="twitter.com"
typeset url_path="/statuses/update.xml"
typeset url="http://${url_host}${url_path}";
integer netfd # http stream number
typeset msgtext="$1"
# argument for "encode_x_www_form_urlencoded"
typeset urlform=(
# input
typeset -a form
# output
typeset content
integer content_length
)
typeset request=""
typeset content=""
# ToDo: Use "urlform.form+=(" once ksh93 has been fixed.
urlform.form[0]=( name="status" data="${msgtext}" )
encode_x_www_form_urlencoded urlform
content="${urlform.content}"
request="POST ${url_path} HTTP/1.1\n"
request+="Host: ${url_host}\n"
request+="Authorization: Basic $(encode_http_basic_auth "${SHTWITTER_USER}"
"${SHTWITTER_PASSWD}")=\n"
request+="User-Agent: ${http_user_agent}\n"
request+="Connection: close\n"
request+="Content-Type: application/x-www-form-urlencoded\n"
request+="Content-Length: $(( ${urlform.content_length} ))\n"
#exit 0
exec {netfd}<>"/dev/tcp/${url_host}/80"
(( $? != 0 )) && { print -u2 "Couldn't open connection to ${url_host}." ;
return 1 ; }
# send http post
{
print -- "${request}"
print -- "${content}"
} >&${netfd}
# process reply
parse_http_response httpresponse <&${netfd}
response="$(cat <&${netfd})"
# close connection
exec {netfd}<&-
print "twitter response was: ${response}"
return 0
}
function usage
{
OPTIND=0
getopts -a "${progname}" "${USAGE}" OPT '-?'
exit 2
}
# program start
builtin basename
builtin cat
builtin date
builtin uname
typeset progname="$(basename "${0}")"
# HTTP protocol client identifer
typeset -r http_user_agent="shtwitter/ksh93 (2007-09-14; $(uname -s -r -p)"
USAGE=$'
[-?\n@(#)\$Id: shtwitter (Roland Mainz) 2007-09-14 \$\n]
[-author?Roland Mainz <[EMAIL PROTECTED]
[+NAME?shtwitter - read/write text data to internet clipboards]
[+DESCRIPTION?\bshtwitter\b is a small utility which can read and write text
to the twitter.com microblogging site.]
[+?The first arg \bmethod\b describes one of the methods, "update" posts a
text message to the users twitter blog, returning the raw response
message from the twitter server.]
[+?The second arg \bstring\b contains the string data which should be
stored on twitter.com.]
method [ string ]
[+SEE ALSO?\bksh93\b(1), \brssread\b(1), http://www.twitter.com]
'
while getopts -a "${progname}" "${USAGE}" OPT ; do
#printmsg "## OPT=|${OPT}|, OPTARG=|${OPTARG}|"
case ${OPT} in
*)usage ;;
esac
done
shift $((OPTIND-1))
typeset method="$1"
shift
case "${method}" in
update|blog) put_twitter_message "$@" ; exit $? ;;
*) usage ;;
esac
fatal_error "not reached."
# EOF.
___
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...
Hi!
A new set of tarballs containing an OS/Net version of ksh93 [1] (based
on ksh93s+_beta_20070418 [2]) is now available from
http://www.opensolaris.org/os/project/ksh93-integration/downloads/2007-07-14/
These tarballs are intended to be installed over an existing OpenSolaris
i386 or SPARC installation (>= Nevada B61) and provide
ksh93s+_beta_20070418 [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].
** Install instructions:
1. Download the tarball:
+ i386/AMD64:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20070714_snapshot_i386.tar.bz2
+ SPARC:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20070714_snapshot_sparc.tar.bz2
2. Verify the MD5 checksum:
+ i386/AMD64: MD5
(ksh93_integration_20070714_snapshot_i386.tar.bz2)=
cab10e4b10eebcf753da462a79bb69c9
+ SPARC: MD5(ksh93_integration_20070714_snapshot_sparc.tar.bz2)
= 003e62591c137cdd46e022baa6bc8f9c
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_20070714_snapshot_i386.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20070714_snapshot_i386.tar.bz2
MD5(ksh93_integration_20070714_snapshot_i386.tar.bz2)=
cab10e4b10eebcf753da462a79bb69c9
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20070714_snapshot_sparc.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20070714_snapshot_sparc.tar.bz2
MD5(ksh93_integration_20070714_snapshot_sparc.tar.bz2)=
003e62591c137cdd46e022baa6bc8f9c
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/svn_genunix_org_on_branches_ksh93_gisburn_prototype005_rev_676_740.diff.txt
(12MB, MD5 checksum is b17d17508b056ccb5698847258ad9d74).
+ Alternatively webrev pages (for final code review) can be found
at
http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/2007-July/005545.html
* 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/.
* Starting with ksh93s+ multibyte characters can be used for
variable/function/etc.-names. Please test this functionality
extensively.
* was added to emacs/gmacs mode to clear the screen
(per community requests and to be in sync with bash)
* 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 #):
/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
* 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 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 740
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):
--- ./test1_x86/usr/src/tools/env/opensolaris.shThu Sep
1
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
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...
Hi!
[Sorry for the repost but the original annoucement had a few dates/etc.
wrong... ;-( ]
A new set of tarballs containing an OS/Net version of ksh93 [1] (based
on ksh93s+_beta_20070418 [2]) is now available from
http://www.opensolaris.org/os/project/ksh93-integration/downloads/2007-04-19/
These tarballs are intended to be installed over an existing OpenSolaris
i386 or SPARC installation (>= B61) and provide ksh93s_final_20070418
[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_20070419_snapshot_i386.tar.bz2
+ SPARC:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20070419_snapshot_sparc.tar.bz2
2. Verify the MD5 checksum:
+ i386/AMD64: MD5
(ksh93_integration_20070419_snapshot_i386.tar.bz2)=
16c2788ade60e2f7fb27c555248e722a
+ SPARC: MD5
(ksh93_integration_20070419_snapshot_sparc.tar.bz2)
= 45dd265978f8f40d62ebcb2600568a67
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_20070419_snapshot_i386.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20070419_snapshot_i386.tar.bz2
MD5(ksh93_integration_20070419_snapshot_i386.tar.bz2)=
16c2788ade60e2f7fb27c555248e722a
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20070419_snapshot_sparc.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20070419_snapshot_sparc.tar.bz2
MD5(ksh93_integration_20070419_snapshot_sparc.tar.bz2)=
45dd265978f8f40d62ebcb2600568a67
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/2007-04-19/
for updates):
* This tarball matches ksh93s+ (=ast-ksh.2007-04-18) with
many many changes since the last version. Please test
the binaries extensively.
* The binaries now are build from a B61-based tree and
require SXCR B61 or higher
* Sources/diffs/webrevs:
+ The diffs between Solaris Nevada B61 and the
current ksh93-integration tree can be obtained via
svn diff -r 676:694 svn://svn.genunix.org/on/
branches/ksh93/gisburn/prototype005/usr
or as unified diff (12MB, MD5 checksum is
1332a3ce792e02e90099daa81d7f26af).
+ Alternatively webrev pages (for code review) are
available in various flavors:
o All changes+diffs+sources:
http://www.nrubsig.org/people/gisburn/work/solaris/ksh93_integration/ksh93_integration_prototype005_webrev_20070419/allfiles/webrev/
o Only Makefile changes+diffs+sources:
http://www.nrubsig.org/people/gisburn/work/solaris/ksh93_integration/ksh93_integration_prototype005_webrev_20070419/makefile_files/webrev/
o Only non-AST/ksh93 changes+diffs+sources:
http://www.nrubsig.org/people/gisburn/work/solaris/ksh93_integration/ksh93_integration_prototype005_webrev_20070419/non_ast_files/webrev/
o Only AST/ksh93-specific changes+diffs+sources:
http://www.nrubsig.org/people/gisburn/work/solaris/ksh93_integration/ksh93_integration_prototype005_webrev_20070419/non_files/webrev/
* 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/.
* Starting with ksh93s+ multibyte characters can be used
for variable/function/etc.-names. Please test this
functionality extensively.
* was added to emacs/gmacs mode to clear
the screen (per community requests and to be in sync
with bash)
* 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 #):
/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
* libcmd.so is replaced with a version which includes
both the ksh93 builtin commands and the private Solaris
API of previous libcmd version
[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+_beta_20070418 [2]) is now available from
http://www.opensolaris.org/os/project/ksh93-integration/downloads/2007-04-19/
These tarballs are intended to be installed over an existing OpenSolaris
i386 or SPARC installation (>= B61) and provide ksh93s_final_20070418
[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_20070419_snapshot_i386.tar.bz2
+ SPARC:
http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20070419_snapshot_sparc.tar.bz2
2. Verify the MD5 checksum:
+ i386/AMD64: MD5
(ksh93_integration_20070419_snapshot_i386.tar.bz2)=
16c2788ade60e2f7fb27c555248e722a
+ SPARC: MD5
(ksh93_integration_20070419_snapshot_sparc.tar.bz2)
= 45dd265978f8f40d62ebcb2600568a67
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_20070419_snapshot_i386.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20070419_snapshot_i386.tar.bz2
MD5(ksh93_integration_20070419_snapshot_i386.tar.bz2)=
16c2788ade60e2f7fb27c555248e722a
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/ksh93_integration_20070419_snapshot_sparc.tar.bz2
$ /usr/sfw/bin/openssl md5
ksh93_integration_20070419_snapshot_sparc.tar.bz2
MD5(ksh93_integration_20070419_snapshot_sparc.tar.bz2)=
45dd265978f8f40d62ebcb2600568a67
# cd /
# sync ; sync
# bzcat http://www.opensolaris.org/os/project/ksh93-integration/downloads/2007-04-19/
for updates):
* This tarball matches ksh93s+ (=ast-ksh.2007-04-18) with
many many changes since the last version. Please test
the binaries extensively.
* The binaries now are build from a B61-based tree and
require SXCR B61 or higher
* Sources/diffs/webrevs:
+ The diffs between Solaris Nevada B61 and the
current ksh93-integration tree can be obtained via
svn diff -r 676:694 svn://svn.genunix.org/on/
branches/ksh93/gisburn/prototype005/usr
or as unified diff (12MB, MD5 checksum is
1332a3ce792e02e90099daa81d7f26af).
+ Alternatively webrev pages (for code review) are
available in various flavors:
o All changes+diffs+sources:
http://www.nrubsig.org/people/gisburn/work/solaris/ksh93_integration/ksh93_integration_prototype005_webrev_20070419/allfiles/webrev/
o Only Makefile changes+diffs+sources:
http://www.nrubsig.org/people/gisburn/work/solaris/ksh93_integration/ksh93_integration_prototype005_webrev_20070419/makefile_files/webrev/
o Only non-AST/ksh93 changes+diffs+sources:
http://www.nrubsig.org/people/gisburn/work/solaris/ksh93_integration/ksh93_integration_prototype005_webrev_20070419/non_ast_files/webrev/
o Only AST/ksh93-specific changes+diffs+sources:
http://www.nrubsig.org/people/gisburn/work/solaris/ksh93_integration/ksh93_integration_prototype005_webrev_20070419/non_files/webrev/
* 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/.
* Starting with ksh93s+ multibyte characters can be used
for variable/function/etc.-names. Please test this
functionality extensively.
* was added to emacs/gmacs mode to clear
the screen (per community requests and to be in sync
with bash)
* 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 #):
/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
* 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 B61 proto
/ subdir via collect
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] 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
Re: [osol-discuss] Status of Power PC port?
Dennis Clarke wrote: > > ken mays wrote: [snip] > >> 5. Support for PowerPC G4 to G5 (PPC750GX) > > > > Will Apple G3 machines still be supported ? > > probably not for a lng time Why (I still have the chance to get an older Apple G3-based IMac... question is whether it makes sense to buy it...) ? 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: 3K man pages available
Eric Enright wrote: > On 1/29/07, Roland Mainz <[EMAIL PROTECTED]> wrote: > > Michelle Olson wrote: > > > Thanks for this message, really good to hear from you. > > > I will ask the gatekeeper to make this change if there > > > are more folks who prefer gzip to bzip2--you are the first to ask. > > > > What about providing both gzip and bzip2 tarballs ? > > This is an ideal solution, IMO. Many source repositories also do that. Ok... (please please no *.tar.Z (tarballs packed with /usr/bin/compress) ... that would be an overkill (mhhh, does anyone remeber pack(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] Re: 3K man pages available
Bruno Jargot wrote: > On 1/29/07, Michelle Olson <[EMAIL PROTECTED]> wrote: > > Thanks for this message, really good to hear from you. I will ask the > > gatekeeper to make this change if there are more folks who prefer gzip to > > bzip2--you are the first to ask. > > I think it's better to stick with bzip2 archives. They need less > bandwidth and less room on disks. Using gzip again would be a step > backwards. Really. +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
Sun Studio 11 tarball for OS/Net compressed with /usr/bin/compress / was: Re: [osol-discuss] Re: 3K man pages available
Stephen Lau wrote: > Michelle Olson wrote: > > Thanks for this message, really good to hear from you. > > I will ask the gatekeeper to make this change if there > > are more folks who prefer gzip to bzip2--you are the > > first to ask. > > My personal preference is for bzip2 - but that's just cause I deliver ON > as bz2 files. There doesn't seem to be a convention - some > consolidations/projects deliver .gz, most deliver .bz2 though. BTW: Did someone filed a bug that the Sun Studio 11 tarball for OS/Net is compressed with /usr/bin/compress ? 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: 3K man pages available
Michelle Olson wrote: > Thanks for this message, really good to hear from you. > I will ask the gatekeeper to make this change if there > are more folks who prefer gzip to bzip2--you are the first to ask. What about providing both gzip and bzip2 tarballs ? Bye, Roland P.S.: Would it be possible to add MD5 checksums to the download page and/or the annoucements, please ? -- __ . . __ (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: 3K man pages available
Martin Bochnig wrote: > Roland Mainz wrote: > >I vote to use bzip2 to compress all the developer sources... usually the > >disks are slower than uncompressing the tarball anyway... > > Not if the uncompressed archives are bigger than, say, 100MB. > Try it out on a U60 with 1x300MHz and let's see if your opinion has changed. My primary development machine is an Ultra5 with 333MHz which is MUCH worse than an Ultra60. I still think bzip2 is a better choice... (BTW: Take a look at my comment about bzip2 performance on SPARC, AFAIK there should be various ways to improve the performance, ranging from compiler tweaks, largepage usage and/or locking the buffers in memory...). 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] Status of Power PC port?
ken mays wrote: > > What is the status of the Opensolaris Power PC port? > Is the project > still active? There were not any status reports or > updates in the last > months. > > Bruno > - > > Cyril, PPC for Solaris community lead, can best answer > that question over in the PowerPC discussions group. > Last I checked, a few things were going on: > > 1. Updating of GCC toolkit (GCC 4.1.1,binutils 2.17) > 2. Updating of ON build to a recent version (offline > b54+?). > 3. Retirement of the Genesi Pegasos 1/2 hardware. > 4. Movement to the the new Genesi EFIKA 5200B and > Pegasos 8641D hardware. > 5. Support for PowerPC G4 to G5 (PPC750GX) Will Apple G3 machines still be supported ? 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
bzip2 performance on SPARC / was: Re: [osol-discuss] Re: 3K man pages available
Eric Enright wrote: > On 1/29/07, Bruno Jargot <[EMAIL PROTECTED]> wrote: > > On 1/29/07, Michelle Olson <[EMAIL PROTECTED]> wrote: > > > Hi Rich, [snip] > Waiting a little extra time to receive the archive is far better than > waiting a lot of extra time to unpack it. Offtopic: Both gzip and bzip2 run much faster on SPARC, either via using large pages (e.g. 64k or 4M; 512k pages will not work on Niagara1 machines... ;-( ) for the source and destination buffers and/or using profile feedback compilation (and/or, XIPO (=interprocedural optimizer)). In theory it may even be "nice" to provide gzip and bzip2 as optimized libraries to avoid that less-optimal versions are used by the various applications (it would even allow to use some of the gzip-accerlator cards out there (by replacing the libraries with versions which use this hardware)). Bye, Roland P.S:: Reply-To: set to OpenSolaris Performance/HPC discussions -- __ . . __ (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: 3K man pages available
Martin Bochnig wrote:
> Rich Teer wrote:
> >On Mon, 29 Jan 2007, Bruno Jargot wrote:
> >
> >>I think it's better to stick with bzip2 archives. They need less
> >>bandwidth and less room on disks. Using gzip again would be a step
> >>backwards. Really.
> >
> >I resepctfully disagree. Casper and I discussed this ages ago (I
> >forget exactly when); apparently the use of bzip archives is one
> >reasons why installing Solaris takes so long.
>
> I agree.
> Very much, in fact.
>
> Algo used by gzip(and its implementation) is the most practical
> compromise {compression_ratio_achieved <<--vs.-->> cpu_time_required}.
And I disagree... the manual page archive has AFAIK nothing ToDo with
package installation, right ? AFAIK these are developer sources and less
space is AFAIK better in such cases...
... I'll vote to keep bz2 ...
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: 3K man pages available
Rich Teer wrote: > On Mon, 29 Jan 2007, Bruno Jargot wrote: > > I think it's better to stick with bzip2 archives. They need less > > bandwidth and less room on disks. Using gzip again would be a step > > backwards. Really. > > I resepctfully disagree. Casper and I discussed this ages ago (I > forget exactly when); apparently the use of bzip archives is one > reasons why installing Solaris takes so long. Correct me if I am wrong... the 3K manual page archive for developers has nothing todo with Solaris install... right ? (And bzip2 on SPARC could be tweaked to run a little bit faster anyway). I vote to use bzip2 to compress all the developer sources... usually the disks are slower than uncompressing the tarball anyway... 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
Transparent codeset conversion in filesystems ? / was: Re: [osol-discuss] Suggestion: PCFS Open Development Project
Ienup Sung wrote: > > Yes, we have numerous locales with different codesets. Solaris 10, > as an example, we have 165 locales with 23 different codesets. > In many cases, codesets use quite similar representation forms and yet > the mappings between the code point values and actual characters/glyphs > are quite different. > > Underlying file systems also have various ways of depositing characters > althought many new file systems are converging to Unicode. (Even then, among > those rather new file systems that use Unicode, they use sometimes > different Unicode encodings not entirely compatible with others byte by > byte.) > > To solve the problem of not correctly showing non-ASCII characters and yet > keeping the maximum compatibility with existing applications and also > numerous locales and codesets it appears that either we tag codeset for > each file or adopt Unicode, in particular, UTF-8, as the file system codeset > as the one thing and then add/doing transparent codeset conversion as > the other. These two could go together or separately supported too. ... The various LC_* variables can point to different locales+encodings (for example ja_JP.UTF-8 vs. ja_JP.PCK) ... isn't there some risk that transparent translations somehow cause havoc ? I assume it's not the case (assuming that only filenames are converted transparently) but did anyone thought this detail (different LC_* variables pointing to different locales/encodings) to the end (I can't think anymore in a straight line after ~~48h brain_uptime, please excuse me if I start asking silly things...) ? Another (likely more real-world) problem is: How would such a "transparent conversion" handle characters which cannot be represented in the current locale - for example how should the "C"/"POSIX" locale handle german umlauts (e.g. "öäü") ? Just replace them via '?', use transliteration (e.g. 'ü' = "ue", 'ö' == "oe" etc.), encode them URLencoding-like (another, (more portable ?) style of transliteration) or invent some all-new solution for the problem ? Final thought: I guess if Solaris wants to use Unicode (locales) more widespread some of tools in /usr/bin/ need to be replaced with the versions from /usr/xpg4/bin/ since the /usr/bin/ tools suffer from the widespread "I don't care about multibyte locales"-disease (question is whether this is considered a "bug" or "feature"... ;-/ ) ... how should this be handled if the "bugfix" (e.g. handle multibyte characters correctly) collides with something like "backwards compatibility" ? 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] Release of OS/Net B56 source ?
Hi! Does anyone know when the B56 sources will be released ? Seems that this may be the version we'll pick for final code review of the ksh93-integration tree... 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: Refined OpenSolaris KDE proposal / Re: Proposal to create an OpenSolaris KDE project
Holger Berger wrote: > > On 1/17/07, Eric Boutilier <[EMAIL PROTECTED]> wrote: > > Need clarification please. Are John Sonnenschein and Roland Mainz > > co-owners of the KDE proposal now? > > I remember the day when it was considered 'impossible' to convince Sun > to introduce ksh93 to Solaris and somehow Roland Mainz managed to get > ksh93 into Solaris. Uhm... the ksh93-integration project is a group effort... IMHO people like April Chin, Glenn Fowler, David Korn and Mike Kupfer did much more work than I did... I am just the one who is plugging the code together, finds more bugs, attempts to be stubborn to get some features working from the beginning (that's why we'll get things like a 64it version of the shell, a default editor/input mode and some other nice goodies with the first putback) and then runs around doing some further tweaking. There is no magic behind 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
Refined OpenSolaris KDE proposal / Re: [osol-discuss] Proposal to create an OpenSolaris KDE project
John Sonnenschein wrote: > > Following the official proposal guidelines, I'd like to take this opportunity > to propose that we collaborate with the KDE e.V. and kde-core-devel in order > to integrate KDE as an OpenSolaris project Ok, lets refine this proposal: 1. Deliver KDE3 to /usr/kde3/ and reserve /usr/kde4/ for KDE version 4. No /opt/blabal or /usr/sfw/junkblabla 2. Ship a Sun/Solaris-branded KDE which uses the default SuSE Linux 10 configuration as default (e.g. things like emacs-like input/edtor modes for widgets, enable the klipper clipboard tool by default etc.) to increase interoperability+productivity. 3. The package should be named SUNWkde* (where '*' means the suffix for the packages) and targets delivery into Solaris 11. 4. The KDE should focus on a lightwheight default configuration with a upper limit of 128MB per user (better would be 64MB if possible ; this excludes larger applications like OpenOffice, Konqueror, Mozilla/Seamonkey (see below)) and a strong focus on office usage 5. Focus on a compact and stable distribution which matches more or less the pieces shipped in SuSE Linux (for interoperability) 6. The distribution should be compiled with the Sun Studio compilers (as a mandatory requirement for the project). No gcc junk. 7. Consider using Mozilla/Seakmoney instead of Thunderbird/FireFox (for the simple reason that the Gecko engine is very memory hungry and running it twice, one for time FireFox and a 2nd time for ThunderBird is IMHO excessive squandering of memory resources). 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] Offtopic: Blogging engine with DocBook support ?
Hi! [Ok... this may be horrible offtopic for OpenSolaris... but maybe there are some people who played around with "Roller" (which runs http://bugs.sun.com) and other Blog engines and may be able to help] Does anyone have a recommendation for a blogging engine which accepts DocBook/XML as input ? 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] Obtaining nameservice-independent "user_attr" and"publickey" data from a shell script ?
Darren J Moffat wrote: > Roland Mainz wrote: > > Is there a nameservice-independent way to obtain the values for > > "user_attr" and "publickey" from a shell script (if not I would propose > > to add a extension to "getent") ? > > publickey no there isn't. > > For user_attr it depends which values you want. I want the "raw" values as returned by |getuserattr()|, |getprofattr()|, |getprofattr()| etc. ... /usr/bin/getent should just return the matching values, either for the admins, users or shell script to use. > user_attr is a little problematic because in some cases it isn't just > user_attr you need to look at but you might then need to look at > prof_attr, auth_attr and exec_attr as well as policy.conf. > > There are a couple of shell tools for some of the user_attr data. > > auths(1) will tell you all the authorisations a user has from user_attr, > all included profiles and defaults from policy.conf. > > profiles(1) will tell you all the profiles a user has assigned to them > from user_attr, and policy.conf and any profiles included in a profile. > > roles(1) will tell you the roles a user has - currently you can only > assign a role directly in user_attr(4) but we want to change that so you > can do it as part of a profile in prof_attr(4) as well. Ok, but all these tools only return mangled versions of the data and not the "raw" (or better: unchanged) values as returned by the native library calls, right ? > That still leaves: > > project, defaultpriv, limitpriv, lock_after_retries, > idletime, idlecmd, labelview, clearance, min_label, type. > > For the user_attr(4) database what exactly is it you are trying to do > from shell script ? Possible usage would be a system admin to figure out whether the system "sees" the changed attributes in a way he/she would expect it (e.g. change/modification verification) ... I could imagine futher usage but right now the primary problem is that there is no direct access to these data except looking at /etc/nsswitch.conf and then implement hand-crafted code for each possible backend type - and that's not really usefull... ;-( A better example would be our script which changes the X11 authentification from MIT-MAGIC-COOKIE-1 to SUN-DES-1 if the user has propper DES/DH credentials. If you have access to NIS+ it's no problem - but obtaining the data from other types of directory backends can be a serious pain for shell scripts (and if we add "publickey" to /usr/bin/getent IMO we should add the other items in /etc/nsswitch.conf in one step (with the limitation that the changes should be easy and obvious), too - just to avoid that someone falls in the same pit as I did long ago... ;-( ). Bye, Roland P.S.: Reply-To: set to OpenSolaris Shell discussions <[EMAIL PROTECTED]> -- __ . . __ (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] Obtaining nameservice-independent "user_attr"and"publickey" data from a shell script ?
James Carlson wrote: > Peter C. Norton writes: > > I think he wants to be able to add a flag, i.e. -nssvc nis, -nssvc > > dns, -nssvc 'ldap', etc. to getent that will dlopen the appropriate > > nss_blah library instead of following the lookup in nsswitch.conf so > > that the lookup to a particular database can be scripted. > > Better yet, being able to specify the search order explicitly from the > command line would be extremely helpful in answering "what if?" sorts > of questions. > > It sounds like part of a decent RFE to me. Ouch... and how would the implementation look like ? The idea was to get simple access to the data independent of the backend nameservice details, e.g. a script should not need to implement support for YP, NIS+, LDAP etc. seperately. Adding those switches would make this MUCH more painfull to implement since we could no longer use any library functions and instead have to do our own lookup code in /usr/bin/getent ... and that's AFAIK an overkill... 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] Obtaining nameservice-independent "user_attr"and"publickey" data from a shell script ?
Martin Bochnig wrote: > Roland Mainz wrote: [snip] > "Normal" users with limited privileges may naturally have no - or > limited - access. > Didn't you find any help in the man pages for NIS, NIS+ and LDAP? That was not the goal. The matching scripts should be able to operate regardless how the backend looks like... 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] Obtaining nameservice-independent "user_attr"and"publickey" data from a shell script ?
Martin Bochnig wrote: > Martin Bochnig wrote: > >Peter C. Norton wrote: > >>On Fri, Jan 05, 2007 at 02:59:55AM +0100, Martin Bochnig wrote: [snip] > >>How does nisinit get names from dns even if your system is set to > >>resolve via NIS+? > > Maybe you mean, Roland would want to clone the methods in which > /usr/sbin/nisinit accesses those data? > But we are talking about C-functions then, not a pure shell script. I was thinking about something like $ /usr/bin/getent user_attr username # to return the values of |getuserattr()| or $ /usr/bin/getent publickey username # to do the same for the "publickey" database, regardless how the backend looks like (e.g. files, nisplus, yp, LDAP etc.) etc., e.g. /usr/bin/getent should return the values which the matching library functions would return... 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] Obtaining nameservice-independent "user_attr"and "publickey" data from a shell script ?
Martin Bochnig wrote: > Martin Bochnig wrote: > >Martin Bochnig wrote: > >>>Maybe getuserattr() or getauthattr() ? > > > >Plus getpublickey() > > > >Or don't those work with "files" as NS ?? > > > >*shrug* > > Exclusively from a shell script, no C? Yes... > Can't you analyse the files in /etc directly then? No, because in the case that the matching entries in /etc/nsswitch.conf contain more than "files" you need nameservice-specific calls, one for YP, one for NIS, one for NIS+, one for LDAP etc. - and you would have to care about the lookup order and fallback behaviour if a nameservice is down etc. etc. ... ... that's why I was thinking to extend /usr/bin/getent to include these items if they are not available via other ways. > Which other tools can be expected to be present Just the shell... > Under which user or role will the script run (root) ? It should work with any user... 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] Obtaining nameservice-independent "user_attr"and "publickey" data from a shell script ?
Martin Bochnig wrote: > Martin Bochnig wrote: > >Roland Mainz wrote: > >>Is there a nameservice-independent way to obtain the values for > >>"user_attr" and "publickey" from a shell script (if not I would propose > >>to add a extension to "getent") ? > > > >Maybe getuserattr() or getauthattr() ? > > Plus getpublickey() > > Or don't those work with "files" as NS ?? The problem is to make these items accessible to the shell (and not binary code). The "publickey" was very annoying since it forced me to create horrible stunts in our script which switches the X11 authentification from MIT-MAGIC-COOKIE-1 to SUN-DES-1 (the hacks will case blindness at the moment you're looking at them). 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] Obtaining nameservice-independent "user_attr" and "publickey" data from a shell script ?
Hi! Is there a nameservice-independent way to obtain the values for "user_attr" and "publickey" from a shell script (if not I would propose to add a extension to "getent") ? 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
Shipping "lsof" with Solaris ? / was: Re: [osol-discuss] problem with /tmp FS still up
Peter Tribble wrote: > On 1/1/07, wb <[EMAIL PROTECTED]> wrote: > > I have a /tmp FS for swap, and a really big file crout* > > inside. The /tmp was 95% up. > > I decided to remove the crout file. > > The problem, is the /tmp is not decreasing, but still > > growing. > > > > How could I make it decrease? > > Find and kill the process that's writing to that file. Somehow I am wondering why Solaris doesn't ship "lsof" in /usr/sbin/ ... is this just "noone had time yet" or something else ? 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] Recent putback of PSARC 2006/356 Reliable DatagramSockets
Cyril Plisko wrote: [snip] > 26 * Copyright (c) 2005 SilverStorm Technologies, Inc. All rights reserved. > 27 * > 28 * This software is available to you under a choice of one of two > 29 * licenses. You may choose to be licensed under the terms of the GNU > 30 * General Public License (GPL) Version 2, available from the file > 31 * COPYING in the main directory of this source tree, or the > 32 * OpenIB.org BSD license below: > > [BSD license text yanked] > > 57 /* > 58 * Sun elects to include this software in Sun product > 59 * under the OpenIB BSD license. [snip] > So is it a sign of Sun isn't taking it [OpenSolaris] seriously, or > a trivial ignorance of most of the Sun' developers ? I guess the project and/or this choice predates OpenSolaris.org or the engineers were not aware that someone may want to see their head(s) on a stick in front of the building for this choice... :-) 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
Trouble with ASCII art in gmail + "Jive" / was: Re: [osol-discuss] What's the status of virtual consoles?
Ignacio Marambio Catán wrote: > > . * * . * .* . > > . * . .* > > President, * . . /\ ( . . * > > Rite Online Inc. . . / .\ . * . > > .*. / * \ . . > > . /* o \ . > > Voice: +1 (250) 979-1638* '''||''' . > > URL: http://www.rite-group.com/rich ** > > sorry, the question is killing me, why is it that roland's butterfly > always shows right and your xmas tree is aways bad? :P Both "GMail" and "Jive" use proportional fonts instead of fixed-width ones. For GMail the fix would be easy: Use HTML "" tags after "-- " (e.g. rexex '^-- $') was found in an email body (seaching from the bottom to make sure we catch only the footer) to render all email footers in a fixed-width font. For "Jive" all hope is lost (just based on the fact that it still screws-up the In-Reply-To:/References: mail headers after many many people complained here about 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
Re: [osol-discuss] Re: vfork issues
Felix Schulte wrote: > On 12/19/06, Richard L. Hamilton <[EMAIL PROTECTED]> wrote: > > That's not something one is supposed to take advantage of! > > > > >From vfork(2) (albeit admittedly the SX version of the man page): > > The vfork() function is deprecated. Its sole legitimate use as a prelude to > > an immediate call to a function from the exec family can be achieved safely > > by posix_spawn(3C) or posix_spawnp(3C). > Read > http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/2006-October/001587.html > and following posts > posix_spawn(3C) is broken in Solaris 11/10 and I would not use it to > use until Sun fixes this and ports the fix back to older Solaris > versions That is not correct. |posix_spawn()| just has a tiny glitch which may hurt you under rare conditions (the ksh93-interation list has more details (the archive is offline right now but I can provide the links once it's online again) ; in general ksh93 is affected but still works with the "buggy" |posix_spawn()| under normal conditions). 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: [website-discuss] Mailman list archives gone ?
Stephen Lau wrote: > Roland Mainz wrote: > > It seems all the list archives are gone from mail.opensolaris.org - for > > example http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/ > > only shows an empty directory instead of the archived messages... ;-(( > > Can anyone please check what is going wrong there ? > > Two hours after Sun US went on holiday, our mail machine ran out of > inodes on its file-system. We're planning to rebuild the mail machine > sometime after we get back from holiday; but in the interm, I took the > existing archives offline (I've archived them so we can restore them in > the future) as a short-term (easy) workaround. Ok... thanks! :-) ... I'll just queue-up all the important postings in my Drafts/ folder until the archives are back... ;-( > Please use the Jive > forums for archives/searching in the meantime.. I just wish we could replace the "Jive" stuff with something more usefull... ;-/ 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
