View previous topic :: View next topic |
Author |
Message |
clauchiorean n00b
Joined: 19 Feb 2006 Posts: 18
|
Posted: Fri Nov 24, 2006 10:41 pm Post subject: Login error |
|
|
At every login I receive this:
configuration error - unknown item "GETPASS _ASTERISKS"
I don't know how to get rid of it.
Help |
|
Back to top |
|
|
grunthus Apprentice
Joined: 21 Apr 2005 Posts: 194 Location: Shetland UK
|
Posted: Sat Nov 25, 2006 12:00 am Post subject: |
|
|
This happened to me (similar errors at any rate) on a box after a 'big' set of emerges. I must have messed up a config file update.
Try running etc-update or dispatch-conf. If that doesn't do the job, comment out the offending line in /etc/login.defs, first making a backup:
Code: | cp /etc/login.defs /etc/login.defs.bak
nano -w /etc/login.defs
|
Think you need then to do this:
Code: | etc-update
source /etc/profile |
_________________ Read 'Free Software - Free Society' by RM Stallman |
|
Back to top |
|
|
Theophile Apprentice
Joined: 31 Mar 2004 Posts: 285
|
Posted: Wed Dec 20, 2006 5:12 am Post subject: |
|
|
I have this same problem, but I cannot even login to my system. All logins and password are rejected. What can I do? _________________ Monopedilos |
|
Back to top |
|
|
moesasji Apprentice
Joined: 10 May 2005 Posts: 263
|
Posted: Wed Dec 20, 2006 5:52 am Post subject: |
|
|
@Theophile: You have a higher chance to get an answer if you start your own topic.
Now your question was completely hidden.
Anyway: To get access to your system you do the following. (change the hda3 & hda2) to correspond to your root and boot-partition.
Code: |
Boot from the Install CD and wait until you receive a prompt
We first mount all partitions:
# mount /dev/hda3 /mnt/gentoo
# mount /dev/hda1 /mnt/gentoo/boot
# swapon /dev/hda2
# mount -t proc none /mnt/gentoo/proc
Then we chroot into our Gentoo environment and configure the kernel:
# chroot /mnt/gentoo /bin/bash
# env-update && source /etc/profile
|
With this you chrooted into your installation and can do any fixes necessary.
What exactly you need to do once in the chroot I do not know exactly.
Seeing this bugreport I guess that re-emerge shadow with emerge --oneshot shadow would solve it. |
|
Back to top |
|
|
|