On 2012-07-24 02:03, Christopher Svanefalk wrote:
> Can you still log into the normal tty:s? Try ctrl-alt-f6 for example.
No, I can just not login on the machine
When I boot from another installation and mount the volume, the
permission seems right.
> Not sure exactly what is broken here...but running "ls -l /usr/bin |
> grep login" and see what it says. Possibly some permissions were not
> set properly because of the failed update.
I cannot login, so, I cannot make a ls command.
I use to log in text mode.
> Best,
>
> Christopher Svanefalk
>
> On Tue, Jul 24, 2012 at 12:42 AM, Patrick Dupre <pdupre(a)kegtux.org
> [6]> wrote:
>
>> Hello,
>>
>> I tried to update a fedora 16 to 17. Unfortunately, the update
>> failed
>> very soon after the starting.
>> Then, no way to try again to update, the distribution was not
>> recognized.
>> Anyway, I was able to boot the distribution, but at the login,
>> after I
>> give a login name I get:
>> tty1: cant exec /bin/login permission denied
>>
>> What are your recommendations?
>>
>> Thank.
>>
>> --
>>
>
> ======================================================================
>> Patrick DUPRÉ | | email:
>> pdupre(a)kegtux.org [1]
>>
>
> ======================================================================
>> --
>> users mailing list
>> users(a)lists.fedoraproject.org [2]
>> To unsubscribe or change subscription options:
>>
https://admin.fedoraproject.org/mailman/listinfo/users [3]
>> Guidelines:
http://fedoraproject.org/wiki/Mailing_list_guidelines
>> [4]
>> Have a question? Ask away:
http://ask.fedoraproject.org [5]
>
>
>
> Links:
> ------
> [1] mailto:pdupre@kegtux.org
> [2] mailto:users@lists.fedoraproject.org
> [3]
https://admin.fedoraproject.org/mailman/listinfo/users
> [4]
http://fedoraproject.org/wiki/Mailing_list_guidelines
> [5]
http://ask.fedoraproject.org
> [6] mailto:pdupre@kegtux.org
If it's a selinux problem, boot the distribution, mount the partition,
and edit /etc/selinux/config. Change to
SELINUX=permissive
then reboot. Hopefully that will get you logged in so you can find the
problem. I suggest a re-label.
Bill