From: Tiemo Krueger - mycable GmbH <tk@mycable.de>
To: David Kesselring <dkesselr@mmc.atmel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: root login
Date: Wed, 22 Oct 2003 16:15:34 +0200 [thread overview]
Message-ID: <3F969106.5000807@mycable.de> (raw)
In-Reply-To: <Pine.GSO.4.44.0310220952170.15096-100000@ares.mmc.atmel.com>
Hmm, I remember that we had once a similar problem, but I can't remember
the reason
nor the solution. It appeared that we where not able to login as root,
but user login was possible.
Logged in as user I was allowed to 'su' to root.
Perhaps this may be a hint, perhaps not, perhaps Bruno remembers the
solution???
Tiemo
David Kesselring wrote:
>I apologize for the many recent questions but I have another trivia
>question for all of you. :-)
>I have installed the RH7.3 miniport to a harddrive connected to a MIPS
>Malta board. The kernel the comes with the port (2.4.18) works fine. I
>then took the cvs code (2.4.22) for mips and built it for malta. The first
>few builds worked ok (which means I could logon as root). Then I changed
>something in the build process so that now the kernels which I build won't
>allow me to logon as root. I've changed /etc/passwd to eliminate the root
>pw. Does anyone know how a kernel can affect the login like this?
>Thanks,
>
>David Kesselring
>Atmel MMC
>dkesselr@mmc.atmel.com
>919-462-6587
>
>
>
>
>
--
-------------------------------------------------------
Tiemo Krueger Tel: +49 48 73 90 19 86
mycable GmbH Fax: +49 48 73 90 19 76
Boeker Stieg 43
D-24613 Aukrug eMail: tk@mycable.de
Public Kryptographic Key is available on request
-------------------------------------------------------
next prev parent reply other threads:[~2003-10-22 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 13:58 root login David Kesselring
2003-10-22 14:15 ` Tiemo Krueger - mycable GmbH [this message]
2003-10-22 15:12 ` Joerg Ritter
2003-10-23 18:51 ` David Kesselring
2003-10-24 8:57 ` Gleb O. Raiko
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=3F969106.5000807@mycable.de \
--to=tk@mycable.de \
--cc=dkesselr@mmc.atmel.com \
--cc=linux-mips@linux-mips.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