Date: Mon, 24 Sep 2001 04:54:01 -0700 (PDT) From: <murray@FreeBSD.org> To: alex.neyman@auriga.ru, murray@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/30739: changing terminal type in sysinstall causes abortion Message-ID: <200109241154.f8OBs1S54868@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
Synopsis: changing terminal type in sysinstall causes abortion State-Changed-From-To: open->analyzed State-Changed-By: murray State-Changed-When: Mon Sep 24 04:47:45 PDT 2001 State-Changed-Why: This bug exists in -STABLE and -CURRENT and should be fixed ASAP. I don't believe the problem is with the actual xterm entry since I don't think that termcap.small is even put onto the MFSROOT floppy. The panic comes from setterm call. lib_setup.c:grab_entry seems to be the culprit, although I'm not sure how this function returning error turns into a 0 signal (undefined signal in FreeBSD) which then causes init (sysinstall) to die. Olgeni added this functionality a few months ago. If I don't hear back from him soon I think we should just backout this whole set termcap option. It's clearly not implemented properly. In fact, I haven't been able to use it without panicing sysinstall a single time. It would help to boot into sysinstall, get far enough along so that you've got the holographic shell, and then use commands to examine the environment variables. I'm curious if there is a termcap entry setup for xterm properly. termpcap.c (sysinstall src) tries to setup the termcap environment variables properly so that the termcap database file is never consulted. I believe this is where the problem lies. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=30739 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109241154.f8OBs1S54868>