Ken Moffat wrote:
> On Thu, Feb 28, 2013 at 05:51:30PM -0600, Bruce Dubbs wrote:
>>
>> I'm not sure. The base code has:
>>
>> set pmap "${topdir}pmap"
>> set pmap_initname "1:\\s+\\S+\[^\\r\]+\\s+"
>> ...
>> set test "pmap X with unreachable process"
>> spawn $pmap -X 1
>> expect_pass $test "$pmap
On Thu, Feb 28, 2013 at 05:51:30PM -0600, Bruce Dubbs wrote:
>
> I'm not sure. The base code has:
>
> set pmap "${topdir}pmap"
> set pmap_initname "1:\\s+\\S+\[^\\r\]+\\s+"
> ...
> set test "pmap X with unreachable process"
> spawn $pmap -X 1
> expect_pass $test "$pmap_initname\$"
>
> The sed r
Ken Moffat wrote:
> On Wed, Feb 27, 2013 at 08:51:37PM -0600, Bruce Dubbs wrote:
>> Ken Moffat wrote:
>>>The interesting part of the log is:
>>>
>>> Running ./pgrep.test/pgrep.exp ...
>>> ERROR: tcl error sourcing ./pgrep.test/pgrep.exp.
>>> ERROR: can't read "tty": no such variable
>>
>> I've
On Wed, Feb 27, 2013 at 08:51:37PM -0600, Bruce Dubbs wrote:
> Ken Moffat wrote:
> > The interesting part of the log is:
> >
> > Running ./pgrep.test/pgrep.exp ...
> > ERROR: tcl error sourcing ./pgrep.test/pgrep.exp.
> > ERROR: can't read "tty": no such variable
>
> I've seen this if trying in
On Thu, Feb 28, 2013 at 03:08:18AM +, Ken Moffat wrote:
>
> - not my main problem at the moment - I'm now running it, but nfs
> (with updates) isn't working. Adding an /etc/netconfig (!) sort of
> helps, but rpcbind still isn't working. I'm seeing
> rpcinfo: can't contact portmapper: RPC: U
On Wed, Feb 27, 2013 at 08:51:37PM -0600, Bruce Dubbs wrote:
> Ken Moffat wrote:
> > On my build of approximately 7.3 I got 4 failures in the procps
> > tests. Pierre has fixed two of them (slabtop), but now that I've
> > finished a minimal desktop I wanted to try to understand the other
> > two
Ken Moffat wrote:
> On my build of approximately 7.3 I got 4 failures in the procps
> tests. Pierre has fixed two of them (slabtop), but now that I've
> finished a minimal desktop I wanted to try to understand the other
> two before I try to prove it can build itself [ _without_ analyzing
> if i
On my build of approximately 7.3 I got 4 failures in the procps
tests. Pierre has fixed two of them (slabtop), but now that I've
finished a minimal desktop I wanted to try to understand the other
two before I try to prove it can build itself [ _without_ analyzing
if it is bitwise the same, I've l
