Date: Sat, 4 Sep 2010 18:53:24 -0400 (EDT) From: Garrett Wollman <wollman@hergotha.csail.mit.edu> To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/150290: xterm -C no longer grabs console Message-ID: <201009042253.o84MrOio003147@hergotha.csail.mit.edu> Resent-Message-ID: <201009042300.o84N0Avb089257@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 150290 >Category: ports >Synopsis: xterm -C no longer grabs console >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Sep 04 23:00:10 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Garrett Wollman >Release: FreeBSD 8.1-RELEASE amd64 >Organization: >Environment: System: FreeBSD hergotha.csail.mit.edu 8.1-RELEASE FreeBSD 8.1-RELEASE #0 r212140M: Sat Sep 4 00:16:21 EDT 2010 wollman@hergotha.csail.mit.edu:/usr/obj/usr/src/sys/HERGOTHA amd64 xterm package: xterm-261 >Description: xterm -C is supposed to grab kernel console output (using the TIOCCONS ioctl). Now it doesn't (as demonstrated by running "xterm -C" and causing the kernel to generate some debugging messages). wollman@hergotha(9)$ xterm -C xterm: cannot open console: Operation not permitted wollman@hergotha(10)$ ls -l /dev/console crw------- 1 wollman wheel 0, 4 Sep 4 18:47 /dev/console Running "xterm -C" as root doesn't generate the error message, but also doesn't capture console output. I don't know if this is a bug in xterm or in the new tty layer, so filing it under ports-bugs as the most proximally involved code is a port. >How-To-Repeat: xterm -C camcontrol debug -c 0:0:0 lsdvd /dev/cd0 # wonder where all the debugging output went... >Fix: unknown >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201009042253.o84MrOio003147>