On Wed, Jan 02, 2008 at 03:35:43PM +0100, Julio M. Merino Vidal wrote:
> On 02/01/2008, at 14:58, Manuel Bouyer wrote:
> 
> >On Wed, Jan 02, 2008 at 11:39:05AM +0000, matthew green wrote:
> >>
> >>Module Name:	src
> >>Committed By:	mrg
> >>Date:		Wed Jan  2 11:39:05 UTC 2008
> >>
> >>Modified Files:
> >>	src/distrib/ofppc: Makefile
> >>	src/distrib/ofppc/cdroms/installcd: Makefile
> >>Added Files:
> >>	src/distrib/ofppc/instkernel: Makefile
> >>	src/distrib/ofppc/ramdisks: Makefile
> >>	src/distrib/ofppc/ramdisks/common: Makefile.ramdisk dot.profile
> >>	    list.ramdisk list.sysinst mtree.ramdisk termcap.mini
> >>	src/distrib/ofppc/ramdisks/ramdisk: Makefile list list.inet6
> >>
> >>Log Message:
> >>- put netbsd.ofppc and ofwboot.ofppc in the root of ofppciso.cd.
> >>
> >>- create a mostly working sysinst/ramdisk environment.  i was
> >>able to successfully run sysinst, but the screen displays many
> >>"bad format `p'" errors i am yet to track down entirely that
> >>make it somewhat difficult to see.
> >
> >Hi,
> >I've seen these bad format `p' in other boot media as well. I  
> >suspect it's
> >a curses issue.
> 
> I'm seeing this also on a NetBSD/amd64 installation when I use, for  
> example, man under a screen session.  It is very hard to read any  
> manual page this way.  And this happens both on the console and  
> through ssh (but always inside screen).

Now that you're saying it ... I think I've seen it when running sysinst
from a Xen INSTALL kernel, with xm console running inside a screen
session. I tested it, and I see it when running xm console in screen on a
-current amd64 system (no problems with a i386 system). 

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
     NetBSD: 26 ans d'experience feront toujours la difference
--