[3292] in Kerberos-V5-bugs
pending/1037: krb5-1.2.2 fixes for NetBSD
daemon@ATHENA.MIT.EDU (Ed Ravin [staff])
Tue Jan 8 20:28:05 2002
Resent-From: gnats@rt-11.mit.edu (GNATS Management)
Resent-To: gnats-admin@rt-11.mit.edu
Resent-Reply-To: krb5-bugs@MIT.EDU, "Ed Ravin [staff]" <elr@panix.com>
Message-Id: <200201090127.g091R1q19730@panix1.panix.com>
Date: Tue, 8 Jan 2002 20:27:01 -0500 (EST)
From: "Ed Ravin [staff]" <elr@panix.com>
To: krb5-bugs@mit.edu
>Number: 1037
>Category: pending
>Synopsis: krb5-1.2.2 fixes for NetBSD
>Confidential: yes
>Severity: serious
>Priority: medium
>Responsible: gnats-admin
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Tue Jan 8 20:28:01 EST 2002
>Last-Modified:
>Originator:
>Organization:
>Release:
>Environment:
>Description:
>How-To-Repeat:
>Fix:
>Audit-Trail:
>Unformatted:
NetBSD uses a slightly different PTY scheme than the usual - the letter
"v" (i.e. ttyv[0-9a-f]) is reserved for an archaic virtual console driver,
so the usual way of manually determining the next available PTY doesn't
work when you get to the letter "v". A patch for the problem is below.
We've used this patch on NetBSD 1.4 and 1.5 systems, up to 1.5.2.
I presume there's some generic way to ask the OS for the next available
PTY, but since I don't know how to do it I'd better shut up now. :-)
Thanks,
-- Ed
Ed Ravin
Systems Administrator
PANIX - Public Access Networks Corporation --- http://www.panix.com
(212) 741 4400 "Please state the nature of the network emergency..."
-----------------------------------
diff -u -r1.1 util/pty/getpty.c
--- util/pty/getpty.c 2001/08/02 03:03:57 1.1
+++ util/pty/getpty.c 2001/08/02 03:13:39
@@ -112,7 +112,11 @@
strncpy(slave, slavebuf, slavelength);
return 0;
} else {
- for (cp = "pqrstuvwxyzPQRST";*cp; cp++) {
+#ifdef __NetBSD__
+ for (cp = "pqrstuwxyzPQRST";*cp; cp++) {
+#else
+ for (cp = "pqrstuvwxyzPQRST";*cp; cp++) {
+#endif
sprintf(slavebuf,"/dev/ptyXX");
slavebuf[sizeof("/dev/pty") - 1] = *cp;
slavebuf[sizeof("/dev/ptyp") - 1] = '0';
