Steven Walter wrote:
>
> If you're logging in as root, this is probably a result of the VT not
> being named in /etc/securetty. Devfsd mucks up the names, so you can
> either include "1," which would allow root logins from pseudo-terminals
> and other insecure places, or upgrade your util-linux
Steven Walter wrote:
If you're logging in as root, this is probably a result of the VT not
being named in /etc/securetty. Devfsd mucks up the names, so you can
either include "1," which would allow root logins from pseudo-terminals
and other insecure places, or upgrade your util-linux to a
That's not correct .. the latest until-linux does not appear to fix the
problem and there seems to be the same problem with PAM.
Gerhard
On Tue, 12 Sep 2000, Steven Walter wrote:
>
> If you're logging in as root, this is probably a result of the VT not
> being named in
On Tue, Sep 12, 2000 at 03:34:22PM +, Steven Walter wrote:
> If you're logging in as root, this is probably a result of the VT not
> being named in /etc/securetty. Devfsd mucks up the names, so you can
> either include "1," which would allow root logins from pseudo-terminals
> and other
Miles Lane wrote:
On Mon, 11 Sep 2000, David Freedom wrote:
> I tried configuring the kernel to the least amount of
> configured options to almost none and I still cannot
> get the password prompt.
>
> My system hangs and is unable to do anything.
> unfortunetly the only thing I can do is power
If you're logging in as root, this is probably a result of the VT not
being named in /etc/securetty. Devfsd mucks up the names, so you can
either include "1," which would allow root logins from pseudo-terminals
and other insecure places, or upgrade your util-linux to a newer
version; I'm not
If you're logging in as root, this is probably a result of the VT not
being named in /etc/securetty. Devfsd mucks up the names, so you can
either include "1," which would allow root logins from pseudo-terminals
and other insecure places, or upgrade your util-linux to a newer
version; I'm not
On Tue, Sep 12, 2000 at 03:34:22PM +, Steven Walter wrote:
If you're logging in as root, this is probably a result of the VT not
being named in /etc/securetty. Devfsd mucks up the names, so you can
either include "1," which would allow root logins from pseudo-terminals
and other
That's not correct .. the latest until-linux does not appear to fix the
problem and there seems to be the same problem with PAM.
Gerhard
On Tue, 12 Sep 2000, Steven Walter wrote:
If you're logging in as root, this is probably a result of the VT not
being named in /etc/securetty.
On Mon, 11 Sep 2000, David Freedom wrote:
> I tried configuring the kernel to the least amount of
> configured options to almost none and I still cannot
> get the password prompt.
>
> My system hangs and is unable to do anything.
> unfortunetly the only thing I can do is power down my
> PC
I tried configuring the kernel to the least amount of
configured options to almost none and I still cannot
get the password prompt.
My system hangs and is unable to do anything.
unfortunetly the only thing I can do is power down my
PC the incorrect and most unfortunate way leading to
filesys
I tried configuring the kernel to the least amount of
configured options to almost none and I still cannot
get the password prompt.
My system hangs and is unable to do anything.
unfortunetly the only thing I can do is power down my
PC the incorrect and most unfortunate way leading to
filesys
12 matches
Mail list logo
