. Daniel Walsh wrote
>Are you booting with selinux=0 or enforcing=0?
No
[byers@f14 ~]$ cat /etc/selinux/config
...
SELINUX=enforcing
...
SELINUXTYPE=targeted
Dan,
you are responding to my initial response
to you and Lamar Owen, where I was freaking out
over having to deal with selinux.
Sin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/2011 02:41 PM, jackson byers wrote:
> thanks for all of the responses
> to Tim: sticky bits on /tmp are set
> to Ed Greshko: I do not see 'authentication failure', the login screen
> just recycles
>
> to Kam Leo, others: I can't get runle
On 06/29/2011 02:41 AM, jackson byers wrote:
> thanks for all of the responses
> to Tim: sticky bits on /tmp are set
> to Ed Greshko: I do not see 'authentication failure', the login
> screen just recycles
>
> to Kam Leo, others: I can't get runlevel 3 to take effect:
>
>
>From the login scree
per Lamar Owen
from my mainf14, put in .autolabel into my backupf14 /
[root@f14 rootusb2_]# ls -la
...
-rw-r--r--. 1 root root 0 Jun 28 12:14 .autorelabel
then rebooted to backup14
it took its time doing relabel (20min?)
then rebooted automatically, but to mainf14,
so I rebooted manually t
thanks for all of the responses
to Tim: sticky bits on /tmp are set
to Ed Greshko: I do not see 'authentication failure', the login screen just
recycles
to Kam Leo, others: I can't get runlevel 3 to take effect:
Working from my mainf14,
I changed the /etc/inittab in the f14backup,
[root@f14
On Tuesday, June 28, 2011 07:44:32 AM Daniel J Walsh wrote:
> > Either backup with an SELinux context preserving tool (such as star or dump
> > or a disk clone) or run fixfiles ('fixfiles relabel' or 'touch
> > /.autorelabel' and reboot)).
> Easier is to just run
>
> restorecon -R -v /home
If o
Kam Leo wrote:
>On Mon, Jun 27, 2011 at 1:41 PM, jackson byers
>wrote:
>> My backup copy of F14 boots, all looks normal,
>> boot messages all "OK"
>> but then I can't login: after entering my password
>> the screen recycles to the login screen,
>> and continues to do this if I keep trying.
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/2011 07:30 AM, Lamar Owen wrote:
> On Monday, June 27, 2011 04:41:43 PM jackson byers wrote:
>> My backup copy of F14 boots, all looks normal,
>> boot messages all "OK"
>>
>> but then I can't login: after entering my password
>> the screen r
On Monday, June 27, 2011 04:41:43 PM jackson byers wrote:
> My backup copy of F14 boots, all looks normal,
> boot messages all "OK"
>
> but then I can't login: after entering my password
> the screen recycles to the login screen,
> and continues to do this if I keep trying.
Home directories req
On Mon, 2011-06-27 at 13:41 -0700, jackson byers wrote:
> I can't login: after entering my password
> the screen recycles to the login screen,
> and continues to do this if I keep trying.
>
> [byers@f14 ~]$ uname -r
> 2.6.35.13-92.fc14.i686.PAE
>
> hints?, advice?
I've seen this, long ago, wh
On Mon, Jun 27, 2011 at 1:41 PM, jackson byers wrote:
> My backup copy of F14 boots, all looks normal,
> boot messages all "OK"
> but then I can't login: after entering my password
> the screen recycles to the login screen,
> and continues to do this if I keep trying.
> [byers@f14 ~]$ uname -r
>
My backup copy of F14 boots, all looks normal,
boot messages all "OK"
but then I can't login: after entering my password
the screen recycles to the login screen,
and continues to do this if I keep trying.
[byers@f14 ~]$ uname -r
2.6.35.13-92.fc14.i686.PAE
hints?, advice?
Jack
--
users mailin
12 matches
Mail list logo
