daily CVS update output

[NetBSD source update]

Updating src tree:
P src/bin/ksh/Makefile
P src/bin/ksh/c_ksh.c
P src/bin/ksh/c_sh.c
P src/bin/ksh/c_test.c
P src/bin/ksh/c_ulimit.c
P src/bin/ksh/config.h
P src/bin/ksh/edit.c
P src/bin/ksh/edit.h
P src/bin/ksh/emacs.c
P src/bin/ksh/eval.c
P src/bin/ksh/exec.c
P src/bin/ksh/expand.h
P src/bin/ksh/expr.c
P src/bin/ksh/history.c
P src/bin/ksh/io.c
P src/bin/ksh/jobs.c
cvs update: `src/bin/ksh/ksh_stat.h' is no longer in the repository
cvs update: `src/bin/ksh/ksh_time.h' is no longer in the repository
cvs update: `src/bin/ksh/ksh_times.h' is no longer in the repository
P src/bin/ksh/lex.c
P src/bin/ksh/mail.c
P src/bin/ksh/main.c
P src/bin/ksh/misc.c
P src/bin/ksh/path.c
P src/bin/ksh/proto.h
P src/bin/ksh/sh.h
P src/bin/ksh/shf.c
cvs update: `src/bin/ksh/sigact.c' is no longer in the repository
cvs update: `src/bin/ksh/sigact.h' is no longer in the repository
P src/bin/ksh/syn.c
P src/bin/ksh/trap.c
P src/bin/ksh/tty.c
P src/bin/ksh/var.c
P src/bin/ksh/vi.c
P src/bin/sh/Makefile
P src/bin/sh/eval.c
P src/bin/sh/expand.c
P src/bin/sh/input.c
P src/bin/sh/input.h
P src/bin/sh/option.list
P src/bin/sh/parser.c
P src/bin/sh/parser.h
P src/bin/sh/redir.c
P src/bin/sh/redir.h
P src/bin/sh/sh.1
P src/bin/sh/show.c
P src/bin/sh/show.h
P src/bin/sh/var.c
P src/bin/sh/var.h
P src/doc/3RDPARTY
P src/doc/CHANGES
P src/external/bsd/bind/dist/CHANGES
P src/external/bsd/bind/dist/README
U src/external/bsd/bind/dist/srcid
P src/external/bsd/bind/dist/version
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.ch01.html
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.ch02.html
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.ch03.html
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.ch04.html
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.ch05.html
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.ch06.html
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.ch07.html
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.ch08.html
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.ch09.html
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.ch10.html
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.ch11.html
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.ch12.html
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.ch13.html
P src/external/bsd/bind/dist/doc/arm/Bv9ARM.html
U src/external/bsd/bind/dist/doc/arm/Bv9ARM.pdf
P src/external/bsd/bind/dist/doc/arm/man.arpaname.html
P src/external/bsd/bind/dist/doc/arm/man.ddns-confgen.html
P src/external/bsd/bind/dist/doc/arm/man.delv.html
P src/external/bsd/bind/dist/doc/arm/man.dig.html
P src/external/bsd/bind/dist/doc/arm/man.dnssec-checkds.html
P src/external/bsd/bind/dist/doc/arm/man.dnssec-coverage.html
P src/external/bsd/bind/dist/doc/arm/man.dnssec-dsfromkey.html
P src/external/bsd/bind/dist/doc/arm/man.dnssec-importkey.html
P src/external/bsd/bind/dist/doc/arm/man.dnssec-keyfromlabel.html
P src/external/bsd/bind/dist/doc/arm/man.dnssec-keygen.html
P src/external/bsd/bind/dist/doc/arm/man.dnssec-revoke.html
P src/external/bsd/bind/dist/doc/arm/man.dnssec-settime.html
P src/external/bsd/bind/dist/doc/arm/man.dnssec-signzone.html
P src/external/bsd/bind/dist/doc/arm/man.dnssec-verify.html
P src/external/bsd/bind/dist/doc/arm/man.genrandom.html
P src/external/bsd/bind/dist/doc/arm/man.host.html
P src/external/bsd/bind/dist/doc/arm/man.isc-hmac-fixup.html
P src/external/bsd/bind/dist/doc/arm/man.lwresd.html
P src/external/bsd/bind/dist/doc/arm/man.named-checkconf.html
P src/external/bsd/bind/dist/doc/arm/man.named-checkzone.html
P src/external/bsd/bind/dist/doc/arm/man.named-journalprint.html
P src/external/bsd/bind/dist/doc/arm/man.named-rrchecker.html
P src/external/bsd/bind/dist/doc/arm/man.named.conf.html
P src/external/bsd/bind/dist/doc/arm/man.named.html
P src/external/bsd/bind/dist/doc/arm/man.nsec3hash.html
P src/external/bsd/bind/dist/doc/arm/man.nsupdate.html
P src/external/bsd/bind/dist/doc/arm/man.rndc-confgen.html
P src/external/bsd/bind/dist/doc/arm/man.rndc.conf.html
P src/external/bsd/bind/dist/doc/arm/man.rndc.html
P src/external/bsd/bind/dist/doc/arm/notes.html
U src/external/bsd/bind/dist/doc/arm/notes.pdf
P src/external/bsd/bind/dist/doc/arm/notes.xml
P src/external/bsd/bind/dist/lib/dns/api
P src/external/bsd/bind/dist/lib/dns/dnssec.c
P src/external/bsd/bind/dist/lib/dns/message.c
P src/external/bsd/bind/dist/lib/dns/rootns.c
P src/external/bsd/bind/dist/lib/dns/tsig.c
P src/lib/libc/rpc/getnetconfig.c
P src/lib/libedit/Makefile
P src/lib/libedit/literal.c
P src/lib/libedit/literal.h
P src/lib/libedit/refresh.c
P src/lib/libexecinfo/execinfo.h
P src/share/man/man9/wsbell.9
P src/sys/arch/arm/arm32/db_interface.c
P src/sys/arch/arm/sunxi/sunxi_platform.c
P src/sys/arch/arm/vexpress/vexpress_sysreg.c
P src/sys/dev/fdt/fdt_subr.c
P src/sys/dev/fdt/fdtvar.h
P src/sys/dev/ofw/ofw_subr.c
P src/sys/dev/ofw/openfirm.h
P src/sys/net/rtsock.c
P src/tests/net/route/t_flags.sh
P src/tests/net/route/t_flags6.sh

Updating xsrc tree:


Killing core files:


Updating tar files:
src/top-level: collecting... replacing... done
src/bin: collecting... 

Latest shell updates

[Robert Elz]

I have just committed the updates to enable prompt expansion (posix standard
for variable expansion, arithmetic coming, command substitutions possible)
and several new shell variables, many of which are intended for use in
prompts (set in PS1 unexpandsd, as
PS1='${Tod} ${HOSTNAME%%.*} ${PSc} '
rather than pre-expanded as
PS1="${Tod} ${HOSTNAME%%.*} ${PSc} "
which would get you the values of the variables at the time the promot is
set, rather than when it is used as a prompt.

This does mean that you need to be careful with $ (and \ if you happen to
use it) in prompt strings - a simple '$' followed by a space or the end of
the prompt string is not a problem, but a '$' followed by anything which
looks like either a variable name (including '{') or a numeric parameter
(ie: a digit) or a special param (! ? # ...) will now be expanded (perhaps
just to a null string.)

This is the last change of substance that I am hoping will make NetBSD 8,
so please test it - in combination with the PSlit changes (and libedit
upgrades) from the past few days - and test soon is possible, so the
pullup requests can get made.

Testing prompts containing non-ascii characters (encoded according to whatever
your locale expects) would be much appreciated.   Even better if you can
also find a use for non-ascii characters which do not get printed (are
embedded between PSlit characters - one possible use would be to use this
for setting a non-ascii string into an x-xterm title bar .. if xterms support
that.)

None of the recent changes should (or are likely to) make any difference to
the way the shell handles scripts, this is all mostly interactive and prompting
related.

RANDOM is one of the new variables, currently implemented using lrand48(3)
though commenting out one line in the sh Makefile will change it to use
random(3) instead.   I have no idea whether the "random" numbers generated
are in any statistical sense random.

kre

Re: AMD Ryzen and NetBSD?

[Thor Lancelot Simon]

On Fri, Jun 30, 2017 at 04:55:40PM +0100, Patrick Welche wrote:
> On Fri, Jun 30, 2017 at 03:41:39PM +, m...@netbsd.org wrote:
> > On Fri, Jun 30, 2017 at 09:25:19AM +0100, Patrick Welche wrote:
> > > I'm happily running -current on a Ryzen 7 1700 / Asus PRIME X370-PRO.
> > > I wonder about its i/o though: I remember dd'ing zeros over old disks, and
> > > thought "this is slow", so I dd'd over 3 disks at once, with no change
> > > in individual "progress" bit rate, i.e. 3 times the bandwidth...
> > 
> > Are you specifying block size? dd is terribly slow without it.
> 
> I was using 64k - essentially the example in the "progress" man page.

Latency.  You want a double-buffered pipeline.

-- 
  Thor Lancelot Simont...@panix.com

  "We cannot usually in social life pursue a single value or a single moral
   aim, untroubled by the need to compromise with others."  - H.L.A. Hart

Re: AMD Ryzen and NetBSD?

[Martin Husemann]

On Fri, Jun 30, 2017 at 04:55:40PM +0100, Patrick Welche wrote:
> On Fri, Jun 30, 2017 at 03:41:39PM +, m...@netbsd.org wrote:
> > On Fri, Jun 30, 2017 at 09:25:19AM +0100, Patrick Welche wrote:
> > > I'm happily running -current on a Ryzen 7 1700 / Asus PRIME X370-PRO.
> > > I wonder about its i/o though: I remember dd'ing zeros over old disks, and
> > > thought "this is slow", so I dd'd over 3 disks at once, with no change
> > > in individual "progress" bit rate, i.e. 3 times the bandwidth...
> > 
> > Are you specifying block size? dd is terribly slow without it.
> 
> I was using 64k - essentially the example in the "progress" man page.

Any chance file systems/partitions are not properly aligned and the device
is internally using > 1/2k blocks?

Martin

Re: AMD Ryzen and NetBSD?

[Patrick Welche]

On Fri, Jun 30, 2017 at 03:41:39PM +, m...@netbsd.org wrote:
> On Fri, Jun 30, 2017 at 09:25:19AM +0100, Patrick Welche wrote:
> > I'm happily running -current on a Ryzen 7 1700 / Asus PRIME X370-PRO.
> > I wonder about its i/o though: I remember dd'ing zeros over old disks, and
> > thought "this is slow", so I dd'd over 3 disks at once, with no change
> > in individual "progress" bit rate, i.e. 3 times the bandwidth...
> 
> Are you specifying block size? dd is terribly slow without it.

I was using 64k - essentially the example in the "progress" man page.

Cheers,

Patrick

Re: AMD Ryzen and NetBSD?

[maya]

On Fri, Jun 30, 2017 at 09:25:19AM +0100, Patrick Welche wrote:
> I'm happily running -current on a Ryzen 7 1700 / Asus PRIME X370-PRO.
> I wonder about its i/o though: I remember dd'ing zeros over old disks, and
> thought "this is slow", so I dd'd over 3 disks at once, with no change
> in individual "progress" bit rate, i.e. 3 times the bandwidth...

Are you specifying block size? dd is terribly slow without it.

Re: Dark screen with nouveau

[Chavdar Ivanov]

Thanks for the suggestion, but it appears the problem was earlier. I built
an up-to-date kernel with the four files downgraded to the versions prior
to your change, but the result was the same - the system working fine but
with a black screen.  Xorg also starts, judging by the processes present,
but does not alight the screen.  This is with the following versions:
---
➜  conf # head -1 /usr/src/sys/external/bsd/drm2/include/drm/drmfb.h
/*$NetBSD: drmfb.h,v 1.1 2015/03/05 17:50:41 riastradh Exp $  */
➜  conf # strings /netbsd | grep \$NetBSD | egrep
intelfb.c\|nouveaufb.c\|drmfb.c
$NetBSD: drmfb.c,v 1.2 2015/11/09 23:11:18 jmcneill Exp $
$NetBSD: intelfb.c,v 1.12 2015/03/05 17:56:39 riastradh Exp $
$NetBSD: nouveaufb.c,v 1.3 2015/10/17 12:02:44 jmcneill Exp $

Regards,

Chavdar


On Thu, 29 Jun 2017 at 03:36  wrote:

> On Wed, Jun 28, 2017 at 02:34:55PM +, Chavdar Ivanov wrote:
>
> > It would be a bit tedious to do bisecting from 20th of November until
> now,
> > so I hoped someone would remember some change for this.
> >
>
> Most likely I broke it with this change:
> https://v4.freshbsd.org/commit/netbsd/src/dY8Umnn16RPolJxz
>

Re: AMD Ryzen and NetBSD?

[Patrick Welche]

On Fri, Jun 30, 2017 at 10:08:47AM +0200, Frank Kardel wrote:
> has anybody had any experience with -current on the new AMD generation like
> Ryzen 7 1800X? Is there any motherboard that booted up and if so what
> devices were supported?

I'm happily running -current on a Ryzen 7 1700 / Asus PRIME X370-PRO.
The only thing I have noticed as "missing" is "envstat" is empty.

I wonder about its i/o though: I remember dd'ing zeros over old disks, and
thought "this is slow", so I dd'd over 3 disks at once, with no change
in individual "progress" bit rate, i.e. 3 times the bandwidth...

Cheers,

Patrick

AMD Ryzen and NetBSD?

[Frank Kardel]

Hi,

has anybody had any experience with -current on the new AMD generation 
like Ryzen 7 1800X? Is there any motherboard that booted up and if so 
what devices were supported?


Best regards,
  Frank