Subject: Re: Two bugs in NetBSD-current
To: None <netbsd-bugs@NetBSD.ORG>
From: der Mouse <mouse@Collatz.McRCIM.McGill.EDU>
List: netbsd-bugs
Date: 09/04/1995 21:44:42
> *** exec.c.orig Mon Sep  4 22:04:02 1995
> --- exec.c      Mon Sep  4 22:05:04 1995
[context stripped, line numbers not updated to match -dM]
> ***************
> *** 64,74 ****
> !       static size_t memsize;
> --- 64,73 ----
> !       static size_t memsize = 0;

Aren't these 100% identical?  [Yes, there was another change, which I
deleted - I don't wish to comment on whether _that_ is a correct

> Another (minor) nuisance: I brazenly dared to enable root logins via
> telnet/rlogin, by just putting a 'secure on' after
> ttyp0   none                            network

> But then init really believes in starting a program called 'none' and
> fills the console...

This is not a bug; this is pilot error.  You should remove the "on", or
else change it to "off".  If you want to allow root network logins, you
just need the "secure"; trying to mark the line "on" will do exactly
what it's supposed to - try to run a getty on that line, and you've got
"none" specified as the getty, which will fail, as you saw.

> Ah well, a last one: While I'm used to it, it is still annoying to
> have the wrong xterm entries in /etc/termcap (not to mention
> terminfo...).  'tset' seems to take the 'rows' value from termcap,
> and 66 is certainly not what xterm *normally* has.

This is a bug in tset, then, not termcap, I would say; tset has no
business overriding an already-set explicit size.

					der Mouse