From owner-freebsd-current Mon Aug 28 8:24: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id BD22437B43C for ; Mon, 28 Aug 2000 08:24:04 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e7SFNtN11144; Mon, 28 Aug 2000 17:23:55 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: devname(3) broken for DEFVS In-Reply-To: Your message of "Mon, 28 Aug 2000 17:14:01 +0200." <80966.967475641@axl.fw.uunet.co.za> Date: Mon, 28 Aug 2000 17:23:55 +0200 Message-ID: <11142.967476235@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hi Poul-Henning, > >I've been having trouble with ps(1) printing invalid controlling >terminal names for processes connected to psuedo-terminals. > >This only seems to be a problem for DEVFS-enabled systems. Yes, devname(3) need to learn a few things. It's actually always been a problem if you added device nodes after boot where dev_mkdb was run. I think the DTRT solution is a sysctl where kern_conf.c can answer the question. It's on my list. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message