[6031] in Athena Bugs
why does xlogin touch the kernel?
daemon@ATHENA.MIT.EDU (John Carr)
Fri Sep 14 01:49:26 1990
To: bugs@ATHENA.MIT.EDU
Date: Fri, 14 Sep 90 01:49:15 EDT
From: John Carr <jfc@ATHENA.MIT.EDU>
I ran xlogin manually and this message was printed:
Unable find all the symbols in /vmunix.
Invoking xlogin should not require that vmunix be readable, writeable, or the
boot kernel. This looks like a message printed by the 6.4->7.0 update kernel
patcher. Xlogin should not touch the configuration or kernel except when run
from init or toehold on a public workstation which needs an update
(/srvd/auto_update should exit immediately on finding $PUBLIC or $AUTOUPDATE
false).