SCIENTIFIC-LINUX-USERS Archives

March 2017

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Stodola <[log in to unmask]>
Reply To:
Mark Stodola <[log in to unmask]>
Date:
Tue, 21 Mar 2017 08:01:39 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
On 03/21/2017 06:49 AM, Lars Behrens wrote:
> Hi there,
>
> After copying a system like I have done a million times before (but only
> with debianic, suse or arch systems) by
>
> * starting a live system on the target
> * copy the origin to mounted target device
> * chroot afterwards
> * adapt /etc/fstab and hosts/hostname files
> * install and config grub.
>
> after reboot I cannot log in to the resulting system neither as root nor
> as user.
>
> When I set selinux to permissive it works. So I am missing some basic thing.
>
> Internet search didn't help me and in the selinux docs I don't know what
> to search for.
>
> Maybe someone, here could help me?
>
> TIA!
>
> Cheerz,
> Lars
>
>

There may be clues in your log files if you can access them from live media.

You could also try using restorecon to reset the selinux policies.  I 
believe doing a 'touch /.autorelabel' will cause selinux to do it on 
reboot as well.

ATOM RSS1 RSS2