This case was approved at PSARC today.
- Garrett
On 03/10/10 07:28 PM, Garrett D'Amore - sun microsystems wrote:
> Provide an opensource version of /usr/bin/sed and /usr/xpg4/bin/sed
>
+1
-Seb
ksh93 (the shell) passes the majority of the VSC sh tests.
The only VSC failures are described in
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6901715 and
happen in vi mode. I like to fix them but without test cases it is
near impossible to figure out what fails and how the expected c
Yes, it has been tested two times in 2009.
First time resulted in numerous failures which have been fixed as Glenn said.
The 2nd run was clean except one failure which is considered a bug in
the VSC test suite.
I am not sure whether I can post the VSC log here since it was passed
as private mail a
On 13/03/2010 00:43, Don Cragun wrote:
> I realize that. I was just trying to reassure Alan and Garrett that
> the project team that has been replacing "closed", "standard" utilities
> with AST code (whether stand-alone or built into ksh93 has always made
> sure that the code passes the VSC tests
On 13/03/2010 00:22, ? wrote:
> ksh93 (the shell) passes the majority of the VSC sh tests.
> The only VSC failures are described in
> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6901715 and
> happen in vi mode. I like to fix them but without test cases it is
> near
On 13/03/2010 00:15, ? wrote:
> Yes, it has been tested two times in 2009.
> First time resulted in numerous failures which have been fixed as Glenn said.
> The 2nd run was clean except one failure which is considered a bug in
> the VSC test suite.
OK, thanks for the info.
> I a
On 12/03/2010 21:05, ? wrote:
> VSC testing covers POSIX.
Yes, I know that, I'm asking if it has been done, and what the result was.
--
Alan Burlison
--
On 12/03/2010 18:39, Garrett D'Amore wrote:
> I don't think there was any indication anywhere that the bits would
> *not* pass POSIX conformance tests. Obviously a change of this nature
> (specifically to /usr/xpg4/bin/sed) requires such conformance testing to
> be done. Such testing, however, is
On 12/03/2010 18:32, Don Cragun wrote:
> While it is nice (and correct) to say that ksh93 passes the VSC tests
> for sh, that is not an indication that the sed functionality built
> into ksh93 will pass the VSC tests for sed.
I am led to believe that VSC doesn't run *at all* under ksh93.
--
Ala
VSC testing covers POSIX.
Olga
2010/3/12 Alan Burlison :
> On 12/03/2010 13:49, ? wrote:
>
>> AT&T AST sed from the ast-open package. It is a direct descendant of
>> the AT&T sed in UNIX. The same package contains ksh93, has the same
>> license (CPL 1.0) as ksh93 and passes VSC.
To clarify Glenn's email:
All utilities have been tested with VSC and all issues found have been
addressed.
This includes AST sed.
Olga
On Fri, Mar 12, 2010 at 9:22 PM, Glenn Fowler wrote:
>
> here are some (possibly off-list) message subjects from late 2009
>
> for -lcmd builtins
>
>VSC
Don, we do not intend to make all closed utilities we replace builtins
in ksh93. Making AST sed a builtin was just an easy thing because the
code is well designed and easy to make re-entrant.
Olga
On Fri, Mar 12, 2010 at 8:21 PM, Don Cragun wrote:
>
> On Mar 12, 2010, at 10:39 AM, Garrett D'Amor
Don, sorry for being ambiguous.
I tried to explain where this version of sed comes from, that ksh93 is
part of the same source repository and that sed passes the VSC test
suite.
Olga
On Fri, Mar 12, 2010 at 7:32 PM, Don Cragun wrote:
> On Mar 12, 2010, at 14:49:39 +0100, olga.kryzhanovska at gma
On Fri, Mar 12, 2010 at 08:46:01AM -0600, Mike Gerdts wrote:
> 2010/3/12 ? :
> > This one, right?
> > ? ? ? -i[SUFFIX], --in-place[=SUFFIX]
> > ? ? ? ? ? ? ?edit files in place (makes backup if extension supplied)
> >
> > -i copies the content to a temporary backup file, truncates
On 12/03/2010 13:49, ? wrote:
> AT&T AST sed from the ast-open package. It is a direct descendant of
> the AT&T sed in UNIX. The same package contains ksh93, has the same
> license (CPL 1.0) as ksh93 and passes VSC.
And what about the POSIX conformance testing?
>
> Olga
>
> On F
For the record, these problems surrounding conformance are the reason
that I am generally unwilling to sponsor integration of these projects
-- I don't know anything about the test suites or how to run them, and I
really don't have the time to learn unless they were shown to be really
straight-
Note that I have removed PSARC-ext from the distribution list and
removed the case number from the subject line. I don't believe
PSARC is interested in this side discussion.
On Mar 12, 2010, 22:01:50 +0100, olga.kryzhanovska at gmail.com wrote:
> Don, we do not intend to make all closed utilitie
truss says it does not use O_NOFOLLOW.
Olga
2010/3/12 James Carlson :
> ? wrote:
>> 2010/3/12 Christine Tran :
>>> 2010/3/12 ? :
This one, right?
-i[SUFFIX], --in-place[=SUFFIX]
edit files in place (makes backup if extension supp
2010/3/12 Mike Gerdts :
> 2010/3/12 ? :
>> This one, right?
>> -i[SUFFIX], --in-place[=SUFFIX]
>> edit files in place (makes backup if extension supplied)
>>
>> -i copies the content to a temporary backup file, truncates the
>> original (keeping permissions, ACL
Subject: Re: Re: [shell-discuss] open source sed [PSARC/2010/086 FastTrack
timeout 03/17/2010]
> >
> > Where do you see the race?
>
> TOCTTOU. Root does this:
>
> find /tmp -type f -print | xargs sed -i 's/this/that/'
>
> Bad guy does som
On Fri, Mar 12, 2010 at 07:56:00PM +, Ceri Davies wrote:
> On Fri, Mar 12, 2010 at 08:46:01AM -0600, Mike Gerdts wrote:
> > [...] A better approach would be the equivalent of:
> >
> > 1. ln $file $file.$suffix
> > 2. newfile=$(mktemp $(dirname $file)/$(basename $file).XX
2010/3/12 Christine Tran :
> 2010/3/12 ? :
>> This one, right?
>> -i[SUFFIX], --in-place[=SUFFIX]
>> edit files in place (makes backup if extension supplied)
>>
>> -i copies the content to a temporary backup file, truncates the
>> original (keeping permissions, A
On 03/12/10 03:18 PM, Alan Burlison wrote:
> On 12/03/2010 18:32, Don Cragun wrote:
>
>> While it is nice (and correct) to say that ksh93 passes the VSC tests
>> for sh, that is not an indication that the sed functionality built
>> into ksh93 will pass the VSC tests for sed.
>
> I am led to believe
This one, right?
-i[SUFFIX], --in-place[=SUFFIX]
edit files in place (makes backup if extension supplied)
-i copies the content to a temporary backup file, truncates the
original (keeping permissions, ACL flags etc) and starts processing
from backup to original file, right?
here are some (possibly off-list) message subjects from late 2009
for -lcmd builtins
VSC test results for { "comm", "join", "tail" }
VSC test failures for "cmp" builtin
VSC test suite failures when testing the "mkfifo" builtin
for ast standalone cmds
VSC test re
Yes, there is. Just because I have to rework the formal proposal
doesn't mean we don't exist and don't write code.
The open source replacements for sed, tr, printf and other utilities
are ready sans testing since 2006 and I believe its time to get the
code into ON, regardless of the formal paperwor
AT&T AST sed from the ast-open package. It is a direct descendant of
the AT&T sed in UNIX. The same package contains ksh93, has the same
license (CPL 1.0) as ksh93 and passes VSC.
Olga
On Fri, Mar 12, 2010 at 2:27 PM, Alan Burlison wrote:
> On 11/03/2010 00:28, Garrett D'Amore - sun microsystems
Can I suggest, that while this topic is interesting, and should be
pursued, the question of how to implement in-place editing is not
relevant to *this* case, since it doesn't propose to offer it at this
time. Note that this case does not replace /usr/gnu/bin/sed.
(The idea to do so at a future
On Thu, Mar 11, 2010 at 12:28 AM, Garrett D'Amore - sun microsystems
wrote:
>
> Template Version: @(#)sac_nextcase 1.69 02/15/10 SMI
> This information is Copyright 2010 Sun Microsystems
> 1. Introduction
> ? ?1.1. Project/Component Working Name:
> ? ? ? ? open source sed
> ? ?1.2. Name of Documen
On 11/03/2010 00:28, Garrett D'Amore - sun microsystems wrote:
> Provide an opensource version of /usr/bin/sed and /usr/xpg4/bin/sed
Can you provide some information on which opensource implementation you
are intending to use? Have you confirmed that it passes the VSC test suite?
Thanks,
--
Christine: Which options and features do you need/want?
Garrett: I used Roland's phrase "[...]so out of order and partial
putbacks at this granularity should have no adverse impact on the
functionality and behavior of the system as a whole[...]". Does this
phrase even apply to individual options?
On Mar 12, 2010, at 10:39 AM, Garrett D'Amore wrote:
> On 03/12/10 10:32 AM, Don Cragun wrote:
>> On Mar 12, 2010, at 14:49:39 +0100, olga.kryzhanovska at gmail.com wrote:
>>
>>
>>> AT&T AST sed from the ast-open package. It is a direct descendant of
>>> the AT&T sed in UNIX. The same package
Subject: Re: Re: [shell-discuss] open source sed [PSARC/2010/086 FastTrack
timeout 03/17/2010]
> Hi, in-place replacement, the -i switch. It allows sed to modify the
> file directly, instead of redirecting the output and then copying it
> back over. This is very useful whe
On 03/12/10 10:32 AM, Don Cragun wrote:
> On Mar 12, 2010, at 14:49:39 +0100, olga.kryzhanovska at gmail.com wrote:
>
>
>> AT&T AST sed from the ast-open package. It is a direct descendant of
>> the AT&T sed in UNIX. The same package contains ksh93, has the same
>> license (CPL 1.0) as ksh93 an
On Mar 12, 2010, at 14:49:39 +0100, olga.kryzhanovska at gmail.com wrote:
> AT&T AST sed from the ast-open package. It is a direct descendant of
> the AT&T sed in UNIX. The same package contains ksh93, has the same
> license (CPL 1.0) as ksh93 and passes VSC.
While it is nice (and correct) to say
? wrote:
> truss says it does not use O_NOFOLLOW.
Bug?
--
James Carlson 42.703N 71.076W
? wrote:
> 2010/3/12 Mike Gerdts :
>> 2010/3/12 ? :
>>> This one, right?
>>> -i[SUFFIX], --in-place[=SUFFIX]
>>> edit files in place (makes backup if extension supplied)
>>>
>>> -i copies the content to a temporary backup file, truncates the
>>>
? wrote:
> 2010/3/12 Christine Tran :
>> 2010/3/12 ? :
>>> This one, right?
>>> -i[SUFFIX], --in-place[=SUFFIX]
>>> edit files in place (makes backup if extension supplied)
>>>
>>> -i copies the content to a temporary backup file, truncates the
>
2010/3/12 ? :
> This one, right?
> ? ? ? -i[SUFFIX], --in-place[=SUFFIX]
> ? ? ? ? ? ? ?edit files in place (makes backup if extension supplied)
>
> -i copies the content to a temporary backup file, truncates the
> original (keeping permissions, ACL flags etc) and starts processing
2010/3/12 ? :
> 2010/3/12 Mike Gerdts :
>> 2010/3/12 ? :
>>> This one, right?
>>> ? ? ? -i[SUFFIX], --in-place[=SUFFIX]
>>> ? ? ? ? ? ? ?edit files in place (makes backup if extension supplied)
>>>
>>> -i copies the content to a temporary backup file, truncates the
2010/3/12 ? :
> Christine: Which options and features do you need/want?
>
Hi, in-place replacement, the -i switch. It allows sed to modify the
file directly, instead of redirecting the output and then copying it
back over. This is very useful when you use sed for text processin
2010/3/12 ? :
> This one, right?
> ? ? ? -i[SUFFIX], --in-place[=SUFFIX]
> ? ? ? ? ? ? ?edit files in place (makes backup if extension supplied)
>
> -i copies the content to a temporary backup file, truncates the
> original (keeping permissions, ACL flags etc) and starts processing
? wrote:
> Which purpose has this option (I can't look at the GPL code without
> getting tainted by the GPL):
The "viral" nature of the GPL only applies to copying code, it
can't "infect" humans (unless you have a perfect memory and are
likely to retype the code you saw directly i
Peter Tribble wrote:
> On Thu, Mar 11, 2010 at 12:28 AM, Garrett D'Amore - sun microsystems
> wrote:
>> Template Version: @(#)sac_nextcase 1.69 02/15/10 SMI
>> This information is Copyright 2010 Sun Microsystems
>> 1. Introduction
>>1.1. Project/Component Working Name:
>> open source
On 03/12/10 04:13 AM, ? wrote:
> Christine: Which options and features do you need/want?
>
> Garrett: I used Roland's phrase "[...]so out of order and partial
> putbacks at this granularity should have no adverse impact on the
> functionality and behavior of the system as a whole[.
> 6687656 RFE: Provide an opensource version of /usr/bin/sed and
> /usr/xpg4/bin/sed
>
>
>
> Interface ? ? ? ? ? ? ? ? ? ? ? ? Stability ? ? ? ?Description
> - ? ? ? ? ? ? ? ? ? ? ? ? - ? ? ? ?---
> /usr/bin/sed ? ? ? ? ? ? ? ? ? ? ?See man page ? ? sed command
> /usr/xpg4/
Casper.Dik at Sun.COM wrote:
> >Well, I asked many times for a documentation of the ON Buildsystem.
> >
> >I mentioned already, that the buildsystem looks like the only real problem.
>
> There is not a whole lot of documentation; clearly people have been able to
> integrate ksh93 into Solaris Ne
>Casper.Dik at sun.com wrote:
>
>> >The integration with ON isn't done, as far as I'm aware.
>>
>> Indeed; you will need to have a completely finished workspace were all you
>> need to type is "hg push". Then most of the work is done and you ask for
>> a sponsor.
>
>Well, I asked many times for
Casper.Dik at sun.com wrote:
> >The integration with ON isn't done, as far as I'm aware.
>
> Indeed; you will need to have a completely finished workspace were all you
> need to type is "hg push". Then most of the work is done and you ask for
> a sponsor.
Well, I asked many times for a documen
>The integration with ON isn't done, as far as I'm aware.
Indeed; you will need to have a completely finished workspace were all you
need to type is "hg push". Then most of the work is done and you ask for
a sponsor.
Casper
On Thu, Mar 11, 2010 at 1:32 AM, James C. McPherson
wrote:
> On 11/03/10 10:28 AM, Garrett D'Amore - sun microsystems wrote:
>>
>> Template Version: @(#)sac_nextcase 1.69 02/15/10 SMI
>> This information is Copyright 2010 Sun Microsystems
>> 1. Introduction
>> 1.1. Project/Component Working Na
Ceri Davies wrote:
> > It first requires a sign of will from people inside Sun/Oracle as we the
> > Community currently cannot directly influence/control the software that
> > comes
> > with Solaris.
>
> I disagree.
Why?
> > > If replacing pax is very important, I'd be willing to port FreeB
? wrote:
> pax is already covered, too. We only have to do the ARC case.
???
How?
J?rg
--
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
js at cs.tu-berlin.de(uni)
joerg.schilling at fokus.fraunhofer.de (work)
Ceri Davies wrote:
> On Thu, Mar 11, 2010 at 10:13:10AM +0100, Joerg Schilling wrote:
> > "Garrett D'Amore" wrote:
> >
> > > It would be interesting to survey the closed-bins and find out how many
> > > of those were still required to build open source ON. I wonder how much
> > > closer this
pax is already covered, too. We only have to do the ARC case.
Olga
On Thu, Mar 11, 2010 at 12:12 PM, Ceri Davies wrote:
> On Thu, Mar 11, 2010 at 10:13:10AM +0100, Joerg Schilling wrote:
>> "Garrett D'Amore" wrote:
>>
>> > It would be interesting to survey the closed-bins and find out how many
On Thu, Mar 11, 2010 at 12:36:45PM +0100, Joerg Schilling wrote:
> Ceri Davies wrote:
>
> > > It first requires a sign of will from people inside Sun/Oracle as we the
> > > Community currently cannot directly influence/control the software that
> > > comes
> > > with Solaris.
> >
> > I disagre
On Thu, Mar 11, 2010 at 12:26:33PM +0100, Joerg Schilling wrote:
> Ceri Davies wrote:
>
> > On Thu, Mar 11, 2010 at 10:13:10AM +0100, Joerg Schilling wrote:
> > > "Garrett D'Amore" wrote:
> > >
> > > > It would be interesting to survey the closed-bins and find out how many
> > > > of those wer
On Thu, Mar 11, 2010 at 10:13:10AM +0100, Joerg Schilling wrote:
> "Garrett D'Amore" wrote:
>
> > It would be interesting to survey the closed-bins and find out how many
> > of those were still required to build open source ON. I wonder how much
> > closer this case will bring us? It certainl
On 11/03/10 10:28 AM, Garrett D'Amore - sun microsystems wrote:
>
> Template Version: @(#)sac_nextcase 1.69 02/15/10 SMI
> This information is Copyright 2010 Sun Microsystems
> 1. Introduction
> 1.1. Project/Component Working Name:
>open source sed
> 1.2. Name of Document Author/S
"Garrett D'Amore" wrote:
> It would be interesting to survey the closed-bins and find out how many
> of those were still required to build open source ON. I wonder how much
> closer this case will bring us? It certainly can't *hurt*. :-)
I am still wondering why some cases are considered an
On 03/11/10 08:47, Joerg Schilling wrote:
> Casper.Dik at Sun.COM wrote:
>
>>> Well, I asked many times for a documentation of the ON Buildsystem.
>>>
>>> I mentioned already, that the buildsystem looks like the only real problem.
>>
>> There is not a whole lot of documentation; clearly people have
Joerg Schilling wrote:
> Casper.Dik at Sun.COM wrote:
>
>>> Well, I asked many times for a documentation of the ON Buildsystem.
>>>
>>> I mentioned already, that the buildsystem looks like the only real problem.
>> There is not a whole lot of documentation; clearly people have been able to
>> in
We have code to tackle all closed POSIX utilities and add BSD and GNU
options, too. We only have to write ARC cases, get them approved
without getting torn into pieces and integrate the code.
Olga
On Thu, Mar 11, 2010 at 1:36 AM, Garrett D'Amore wrote:
> It would be interesting to survey the clo
It would be interesting to survey the closed-bins and find out how many
of those were still required to build open source ON. I wonder how much
closer this case will bring us? It certainly can't *hurt*. :-)
- Garrett
On 03/10/10 04:32 PM, James C. McPherson wrote:
> On 11/03/10 10:28 A
Template Version: @(#)sac_nextcase 1.69 02/15/10 SMI
This information is Copyright 2010 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
open source sed
1.2. Name of Document Author/Supplier:
Author: Olga Kryzhanovska
1.3 Date of This Document:
66 matches
Mail list logo
