Date: Tue, 26 Sep 2000 22:28:57 +1100 (EST) From: Stanley Hopcroft <Stanley.Hopcroft@IPAustralia.Gov.AU> To: Odhiambo Washington <wash@iconnect.co.ke> Cc: Stanley Hopcroft <Stanley.Hopcroft@IPAustralia.Gov.AU>, freebsd-questions@freebsd.org Subject: Re: telnetd: All network ports in use. After new 4.1-R kernel; Ok with GENERIC. Message-ID: <Pine.BSF.4.21.0009262212570.310-100000@stan> In-Reply-To: <20000926122202.B18238@poeza.iconnect.co.ke>
next in thread | previous in thread | raw e-mail | index | archive | help
Dar Sir, I am writing to thank you for your patience in this matter, and say that if I have anything worth troubling the list about, it is that the GENERIC kernel configuration file (/usr/src/sys/i386/conf/GENERIC) has an incorrect pty statement in it stan# cd /usr/src/sys/i386/conf/ stan# uname -a FreeBSD stan.aipo.gov.au 4.1-RELEASE FreeBSD 4.1-RELEASE #0: Fri Sep 1 13:27:48 EST 2000 root@stan.aipo.gov.au:/usr/src/sys/compile/STAN2 i386 stan# grep -2 pty GENERIC pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device gif 4 # IPv6 and IPv4 tunneling stan# grep GENERIC GENERIC # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.8 2000/07/20 02:51:02 msmith Exp $ ident So, when the innocent turkey creates a custom kernel by copying and editing the GENERIC file, unless he or she shows your sapience in correcting the pty statement (and sh MAKEDEV accordingly), he or she will be disappointed. Here by contrast is the GENERIC definition file for 3.4-RELEASE, showing a different pty statement. > uname -a FreeBSD stan 3.4-RELEASE FreeBSD 3.4-RELEASE #7: Fri Feb 4 20:49:06 EST 2000 root@:/usr/src/sys/compile/STAN i386 > grep GENERIC GENERIC # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.143.2.24 1999/12/05 01:56:42 luoqi Exp $ ident GENERIC > grep pty GENERIC pseudo-device pty 16 # Pseudo-ttys (telnet etc) > So to sum up, 1 As you say, if the pty statement in your custom kernel does not have some digits after it, the kernel it generates will reject telnet connections with telnetd: All network ports in use 2 The GENERIC kernel configuration file in 4.1-RELEASE is in error because it has no digits after the pty statement; this is not stated as error on http://www.FreeBSD.org/releases/4.1R/errata.html. so maybe it isn't .. 3 OTOH, maybe this needs a PR. Unfortunately, I don't know how to do this. Thank you, Yours sincerely. S Hopcroft Network Specialist IP Australia +61 2 6283 3189 +61 2 6281 1353 FAX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0009262212570.310-100000>