From: "M.H.VanLeeuwen" <vanl@megsinet.net>
To: David Ford <david@linux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: run level 1, login takes too long, 2.4.X vs. 2.2.X
Date: Sun, 19 Nov 2000 23:20:56 -0600 [thread overview]
Message-ID: <3A18B4B8.37508FA0@megsinet.net> (raw)
In-Reply-To: <3A18573B.E65CA88A@megsinet.net> <3A18AA1F.FAC00978@linux.com>
Hi David,
Yup, I know rpc.portmap isn't running, the point is that it wasn't running on either
2.2.17 or 2.4.X. Isn't run level 1 supposed to only be the bare minimum of running
processes, a few kernel processes, init and getty. No network services...
What's changed in the kernel to elicit this behavior?
Is there a better "faster" way to get root access at run level 1 w/o login & passwd
on 2.4.X?
No it's not an everyday occurance, but I was impatiently thinking the sytem had
locked up and rebooted a couple of times, so it got me wondering why 2.2.X and
2.4.X differ in this basic behavior.
Martin
David Ford wrote:
>
> rpc.portmap isn't running, your login configuration/nss requires yp or something provided ans an RPC.
>
> -d
>
> "M.H.VanLeeuwen" wrote:
>
> > I had occasion to "telinit 1" today and found that it took a long time
> > to login after root passwd was entered. this doesn't happen with 2.2.X
> > kernels.
> >
> > Is this to be expected with the 2.4 series kernels? or a bug?
> >
> > Martin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-20 5:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-19 22:42 run level 1, login takes too long, 2.4.X vs. 2.2.X M.H.VanLeeuwen
2000-11-20 2:51 ` Jeff Epler
2000-11-20 4:35 ` David Ford
2000-11-20 5:20 ` M.H.VanLeeuwen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A18B4B8.37508FA0@megsinet.net \
--to=vanl@megsinet.net \
--cc=david@linux.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox