How to set enforcing to 0?

[Paul Smith]

Dear All,

I am experiencing problems with booting F18 after the last updates.
How can I set

enforcing = 0

in boot options?

Thanks in advance,

Paul

[Marcel Hellwig]

Am 26.01.2013 12:16, schrieb Paul Smith:
> Dear All,
>
> I am experiencing problems with booting F18 after the last updates.
> How can I set
>
> enforcing = 0
>
> in boot options?
>
> Thanks in advance,
>
> Paul

Forever or just one time?
Forever:
just adding it to your /etc/default/grub (but without the whitespace
around) and run grub2-mkconfig -O /boot/grub2/grub.cfg
should do the trick ;)
Onetime:
Press e when you are in grub and add enforcing=0 to the line that starts
with linux

Regards

[Junk]

Leon L. Robinson 
Trainer

[phone]
http://uk.linkedin.com/in/leonlrobinson

On 26 Jan 2013, at 11:18, Marcel Hellwig  wrote:
> Am 26.01.2013 12:16, schrieb Paul Smith:
> > Dear All,
> >
> > I am experiencing problems with booting F18 after the last updates.
> > How can I set
> >
> > enforcing = 0
> >
> > in boot options?
> >
> > Thanks in advance,
> >
> > Paul
>
> Forever or just one time?
> Forever:
> just adding it to your /etc/default/grub (but without the whitespace
> around) and run grub2-mkconfig -O /boot/grub2/grub.cfg
> should do the trick ;)
> Onetime:
> Press e when you are in grub and add enforcing=0 to the line that starts
> with linux
>
> Regards
>
> -- 
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

Isn't there a config file in /etc/selinux/ ? Or am I thinking of RHEL6 again?

[Reindl Harald]

Am 26.01.2013 14:24, schrieb Junk:
> Leon L. Robinson 
> Trainer
>
> [phone]
> http://uk.linkedin.com/in/leonlrobinson
>
> On 26 Jan 2013, at 11:18, Marcel Hellwig  wrote:
> > Am 26.01.2013 12:16, schrieb Paul Smith:
> > > Dear All,
> > >
> > > I am experiencing problems with booting F18 after the last updates.
> > > How can I set
> > >
> > > enforcing = 0
> > >
> > > in boot options?
> > >
> > > Thanks in advance,
> > >
> > > Paul
> >
> > Forever or just one time?
> > Forever:
> > just adding it to your /etc/default/grub (but without the whitespace
> > around) and run grub2-mkconfig -O /boot/grub2/grub.cfg
> > should do the trick ;)
> > Onetime:
> > Press e when you are in grub and add enforcing=0 to the line that starts
> > with linux
> >
> > Regards
> >
> > -- 
> > users mailing list
> > [e-mail]
> > To unsubscribe or change subscription options:
> > https://admin.fedoraproject.org/mailman/listinfo/users
> > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> > Have a question? Ask away: http://ask.fedoraproject.org
>
> Isn't there a config file in /etc/selinux/ ? Or am I thinking of RHEL6 again?

would you please strip signatures ON TOP of mails and any sort of
fotters before post to a mailing-list? look abvoe how large is your
message for a one liner and who the fuck has his signature on top?

[Junk]

Leon L. Robinson 
Trainer

[phone]
http://uk.linkedin.com/in/leonlrobinson

On 26 Jan 2013, at 13:28, Reindl Harald  wrote:
> Am 26.01.2013 14:24, schrieb Junk:
> > Leon L. Robinson 
> > Trainer
> >
> > [phone]
> > http://uk.linkedin.com/in/leonlrobinson
> >
> > On 26 Jan 2013, at 11:18, Marcel Hellwig  wrote:
> > > Am 26.01.2013 12:16, schrieb Paul Smith:
> > > > Dear All,
> > > >
> > > > I am experiencing problems with booting F18 after the last updates.
> > > > How can I set
> > > >
> > > > enforcing = 0
> > > >
> > > > in boot options?
> > > >
> > > > Thanks in advance,
> > > >
> > > > Paul
> > >
> > > Forever or just one time?
> > > Forever:
> > > just adding it to your /etc/default/grub (but without the whitespace
> > > around) and run grub2-mkconfig -O /boot/grub2/grub.cfg
> > > should do the trick ;)
> > > Onetime:
> > > Press e when you are in grub and add enforcing=0 to the line that starts
> > > with linux
> > >
> > > Regards
> > >
> > > -- 
> > > users mailing list
> > > [e-mail]
> > > To unsubscribe or change subscription options:
> > > https://admin.fedoraproject.org/mailman/listinfo/users
> > > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> > > Have a question? Ask away: http://ask.fedoraproject.org
> >
> > Isn't there a config file in /etc/selinux/ ? Or am I thinking of RHEL6 again?
>
> would you please strip signatures ON TOP of mails and any sort of
> fotters before post to a mailing-list? look abvoe how large is your
> message for a one liner and who the fuck has his signature on top?
>
> -- 
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

Sorry about that. Fuck.

[Reindl Harald]

WTF - remove your signature on top and do youself a favour
and change your name to something else than "Junk"

rest of the reply at bottom

Am 26.01.2013 14:48, schrieb Junk:
> Leon L. Robinson 
> Trainer
>
> [phone]
> http://uk.linkedin.com/in/leonlrobinson
>
> On 26 Jan 2013, at 13:28, Reindl Harald  wrote:
> > Am 26.01.2013 14:24, schrieb Junk:
> > > Leon L. Robinson 
> > > Trainer
> > >
> > > [phone]
> > > http://uk.linkedin.com/in/leonlrobinson
> > >
> > > On 26 Jan 2013, at 11:18, Marcel Hellwig  wrote:
> > > > -- 
> > > > users mailing list
> > > > [e-mail]
> > > > To unsubscribe or change subscription options:
> > > > https://admin.fedoraproject.org/mailman/listinfo/users
> > > > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> > > > Have a question? Ask away: http://ask.fedoraproject.org
> > >
> > > Isn't there a config file in /etc/selinux/ ? Or am I thinking of RHEL6 again?
> >
> > would you please strip signatures ON TOP of mails and any sort of
> > fotters before post to a mailing-list? look abvoe how large is your
> > message for a one liner and who the fuck has his signature on top?
> >
> > -- 
> > users mailing list
> > [e-mail]
> > To unsubscribe or change subscription options:
> > https://admin.fedoraproject.org/mailman/listinfo/users
> > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> > Have a question? Ask away: http://ask.fedoraproject.org
>
> Sorry about that. Fuck.

and you are doing it again?!

what is so complicated remove lines from "--" to "Have a question?"
and anything looking like a signature/footer from quotes?
_______________

and sorry BUT this signature ON TOP of your messages let you not
look smart! you can guess how much people are thinking "anoter
idiot top-posting and only his signature made it out" not scrolling
down and searching your oneliner reply
> Leon L. Robinson
> Trainer
>
> [phone]
> http://uk.linkedin.com/in/leonlrobinson

[Joe Zeff]

On 01/26/2013 03:16 AM, Paul Smith wrote:
> Dear All,
>
> I am experiencing problems with booting F18 after the last updates.
> How can I set
>
> enforcing = 0
>
> in boot options?

What kind of boot problems are you getting?  Are you getting SELinux 
errors?  Why do you think that this will help?

[Paul Smith]

On Sat, Jan 26, 2013 at 2:15 PM, Joe Zeff  wrote:
> > I am experiencing problems with booting F18 after the last updates.
> > How can I set
> >
> > enforcing = 0
> >
> > in boot options?
>
> What kind of boot problems are you getting?  Are you getting SELinux errors?
> Why do you think that this will help?

Thanks, Joe. It does not help actually, but it was suggested at:

https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=865399

I am getting this sort of message at boot time (I cannot boot my machine):

Welcome to emergency mode. Use "systemctl default" or ^D to enter default mode.
Give root password for maintenance
(or type Control-D to continue)
sulogin: /root: change directory failed: Permission denied

Paul

[Joe Zeff]

On 01/26/2013 06:33 AM, Paul Smith wrote:
> Welcome to emergency mode. Use "systemctl default" or ^D to enter default mode.
> Give root password for maintenance
> (or type Control-D to continue)
> sulogin: /root: change directory failed: Permission denied

Thank you.  Whenever I see a question like that with no explanation I 
get suspicious that somebody's trying to be a cargo cult sysadmin, 
trying a drastic "solution" that they don't understand because "it 
worked ten years ago."

You might try booting from a LiveCD, chrooting and running restorecon on 
/root.  And, while I'm thinking about it, why does your boot process 
need to log in as root?  Is this something normal that I've never 
noticed, or something odd?

[Paul Smith]

On Sat, Jan 26, 2013 at 2:51 PM, Joe Zeff  wrote:
> > Welcome to emergency mode. Use "systemctl default" or ^D to enter default
> > mode.
> > Give root password for maintenance
> > (or type Control-D to continue)
> > sulogin: /root: change directory failed: Permission denied
>
> Thank you.  Whenever I see a question like that with no explanation I get
> suspicious that somebody's trying to be a cargo cult sysadmin, trying a
> drastic "solution" that they don't understand because "it worked ten years
> ago."
>
> You might try booting from a LiveCD, chrooting and running restorecon on
> /root.  And, while I'm thinking about it, why does your boot process need to
> log in as root?  Is this something normal that I've never noticed, or
> something odd?

Thanks, Joe. I do not know why it tries to login as root -- my
installation is merely a F18 clean installation. I strongly believe
that the problem I am experiencing is being caused by the new selinux
update.

Is there some way of disabling selinux in the emergency mode and
getting the machine booting without selinux active?

Paul

Paul

[Paul Smith]

On Sun, Jan 27, 2013 at 11:07 AM, Paul Smith  wrote:
> > > Welcome to emergency mode. Use "systemctl default" or ^D to enter default
> > > mode.
> > > Give root password for maintenance
> > > (or type Control-D to continue)
> > > sulogin: /root: change directory failed: Permission denied
> >
> > Thank you.  Whenever I see a question like that with no explanation I get
> > suspicious that somebody's trying to be a cargo cult sysadmin, trying a
> > drastic "solution" that they don't understand because "it worked ten years
> > ago."
> >
> > You might try booting from a LiveCD, chrooting and running restorecon on
> > /root.  And, while I'm thinking about it, why does your boot process need to
> > log in as root?  Is this something normal that I've never noticed, or
> > something odd?
>
> Thanks, Joe. I do not know why it tries to login as root -- my
> installation is merely a F18 clean installation. I strongly believe
> that the problem I am experiencing is being caused by the new selinux
> update.
>
> Is there some way of disabling selinux in the emergency mode and
> getting the machine booting without selinux active?

By running journalctl, I got the following:

kernel: ata1.00 exception emask 0x0 SAct 0x0 action 0x0
kernel: ata1.00: BMDMA stat 0x24
kernel: ata1.00: failed command: READ DMA EXT

Any ideas?

Paul

[Reindl Harald]

Am 27.01.2013 12:54, schrieb Paul Smith:
> > Is there some way of disabling selinux in the emergency mode and
> > getting the machine booting without selinux active?
>
> By running journalctl, I got the following:
>
> kernel: ata1.00 exception emask 0x0 SAct 0x0 action 0x0
> kernel: ata1.00: BMDMA stat 0x24
> kernel: ata1.00: failed command: READ DMA EXT

ata1.00 is your first hard disk

[Paul Smith]

On Sun, Jan 27, 2013 at 11:56 AM, Reindl Harald  wrote:
> > By running journalctl, I got the following:
> >
> > kernel: ata1.00 exception emask 0x0 SAct 0x0 action 0x0
> > kernel: ata1.00: BMDMA stat 0x24
> > kernel: ata1.00: failed command: READ DMA EXT
>
> ata1.00 is your first hard disk

Thanks, Reindl. I only have one hard disk in my computer, which runs
only Fedora 18.

Paul

[Reindl Harald]

Am 27.01.2013 13:12, schrieb Paul Smith:
> On Sun, Jan 27, 2013 at 11:56 AM, Reindl Harald  wrote:
> > > By running journalctl, I got the following:
> > >
> > > kernel: ata1.00 exception emask 0x0 SAct 0x0 action 0x0
> > > kernel: ata1.00: BMDMA stat 0x24
> > > kernel: ata1.00: failed command: READ DMA EXT
> >
> > ata1.00 is your first hard disk
>
> Thanks, Reindl. I only have one hard disk in my computer, which runs
> only Fedora 18.

it this sounds like it would make problems not to say
is dying - if there are unbackuped data i would take
a live-cd and start to backup them!

[Paul Smith]

On Sun, Jan 27, 2013 at 12:12 PM, Paul Smith  wrote:
> > > By running journalctl, I got the following:
> > >
> > > kernel: ata1.00 exception emask 0x0 SAct 0x0 action 0x0
> > > kernel: ata1.00: BMDMA stat 0x24
> > > kernel: ata1.00: failed command: READ DMA EXT
> >
> > ata1.00 is your first hard disk
>
> Thanks, Reindl. I only have one hard disk in my computer, which runs
> only Fedora 18.

As a consequence of this problem, I cannot boot my computer. This
problem occurred after the last updates, which included
selinux-policy.

Paul

[Reindl Harald]

Am 27.01.2013 13:17, schrieb Paul Smith:
> On Sun, Jan 27, 2013 at 12:12 PM, Paul Smith  wrote:
> > > > By running journalctl, I got the following:
> > > >
> > > > kernel: ata1.00 exception emask 0x0 SAct 0x0 action 0x0
> > > > kernel: ata1.00: BMDMA stat 0x24
> > > > kernel: ata1.00: failed command: READ DMA EXT
> > >
> > > ata1.00 is your first hard disk
> >
> > Thanks, Reindl. I only have one hard disk in my computer, which runs
> > only Fedora 18.
>
> As a consequence of this problem, I cannot boot my computer. This
> problem occurred after the last updates, which included
> selinux-policy.

i doubt that HARDWARE errors have anything to do with selinux-policy

[Paul Smith]

On Sun, Jan 27, 2013 at 12:31 PM, Reindl Harald  wrote:
> > > > > By running journalctl, I got the following:
> > > > >
> > > > > kernel: ata1.00 exception emask 0x0 SAct 0x0 action 0x0
> > > > > kernel: ata1.00: BMDMA stat 0x24
> > > > > kernel: ata1.00: failed command: READ DMA EXT
> > > >
> > > > ata1.00 is your first hard disk
> > >
> > > Thanks, Reindl. I only have one hard disk in my computer, which runs
> > > only Fedora 18.
> >
> > As a consequence of this problem, I cannot boot my computer. This
> > problem occurred after the last updates, which included
> > selinux-policy.
>
> i doubt that HARDWARE errors have anything to do with selinux-policy

Thanks again, Reindl. By using smartctl, I get a message similar to
the one below:

Error 18 occurred at disk power-on lifetime: 12126 hours (505 days + 6 hours)
  When the command that caused the error occurred, the device was
active or idle.

Paul

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/27/2013 07:44 AM, Paul Smith wrote:
> On Sun, Jan 27, 2013 at 12:31 PM, Reindl Harald 
> wrote:
> > > > > > By running journalctl, I got the following:
> > > > > >
> > > > > > kernel: ata1.00 exception emask 0x0 SAct 0x0 action 0x0 kernel:
> > > > > > ata1.00: BMDMA stat 0x24 kernel: ata1.00: failed command: READ
> > > > > > DMA EXT
> > > > >
> > > > > ata1.00 is your first hard disk
> > > >
> > > > Thanks, Reindl. I only have one hard disk in my computer, which runs 
> > > > only Fedora 18.
> > >
> > > As a consequence of this problem, I cannot boot my computer. This 
> > > problem occurred after the last updates, which included 
> > > selinux-policy.
> >
> > i doubt that HARDWARE errors have anything to do with selinux-policy
>
> Thanks again, Reindl. By using smartctl, I get a message similar to the one
> below:
>
> Error 18 occurred at disk power-on lifetime: 12126 hours (505 days + 6
> hours) When the command that caused the error occurred, the device was 
> active or idle.
>
> Paul

Boot your machine with enforcing=0 on the kernel line.  If you still have the
problem, then it is probably not SELinux.  If it works, then I would try to
relabel.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.13 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlEGkyAACgkQrlYvE4MpobM1TgCeIzLEEhfE3zMa7EEURiQLLyZf
> QwcAnA3d0maQLHmbXjMNfP9bVHlY9XYf
> =XMkS
> -----END PGP SIGNATURE-----

[Paul Smith]

On Mon, Jan 28, 2013 at 3:02 PM, Daniel J Walsh  wrote:
> > > > > > > By running journalctl, I got the following:
> > > > > > >
> > > > > > > kernel: ata1.00 exception emask 0x0 SAct 0x0 action 0x0 kernel:
> > > > > > > ata1.00: BMDMA stat 0x24 kernel: ata1.00: failed command: READ
> > > > > > > DMA EXT
> > > > > >
> > > > > > ata1.00 is your first hard disk
> > > > >
> > > > > Thanks, Reindl. I only have one hard disk in my computer, which runs
> > > > > only Fedora 18.
> > > >
> > > > As a consequence of this problem, I cannot boot my computer. This
> > > > problem occurred after the last updates, which included
> > > > selinux-policy.
> > >
> > > i doubt that HARDWARE errors have anything to do with selinux-policy
> >
> > Thanks again, Reindl. By using smartctl, I get a message similar to the one
> > below:
> >
> > Error 18 occurred at disk power-on lifetime: 12126 hours (505 days + 6
> > hours) When the command that caused the error occurred, the device was
> > active or idle.
>
> Boot your machine with enforcing=0 on the kernel line.  If you still have the
> problem, then it is probably not SELinux.  If it works, then I would try to
> relabel.

Thanks, Daniel. I have meanwhile overcome the problem by re-installing
Fedora. Now, everything seems to be working perfectly.

By the way,

enforcing=0

was to be placed in the line that starts with the word

'linux',

right?

How can one do the relabeling?

Paul

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/28/2013 03:20 PM, Paul Smith wrote:
> On Mon, Jan 28, 2013 at 3:02 PM, Daniel J Walsh  wrote:
> > > > > > >> By running journalctl, I got the following:
> > > > > > >> 
> > > > > > >> kernel: ata1.00 exception emask 0x0 SAct 0x0 action 0x0
> > > > > > >> kernel: ata1.00: BMDMA stat 0x24 kernel: ata1.00: failed
> > > > > > >> command: READ DMA EXT
> > > > > > > 
> > > > > > > ata1.00 is your first hard disk
> > > > > >
> > > > > > Thanks, Reindl. I only have one hard disk in my computer, which
> > > > > > runs only Fedora 18.
> > > > >
> > > > > As a consequence of this problem, I cannot boot my computer. This 
> > > > > problem occurred after the last updates, which included 
> > > > > selinux-policy.
> > > >
> > > > i doubt that HARDWARE errors have anything to do with selinux-policy
> > >
> > > Thanks again, Reindl. By using smartctl, I get a message similar to the
> > > one below:
> > >
> > > Error 18 occurred at disk power-on lifetime: 12126 hours (505 days + 6 
> > > hours) When the command that caused the error occurred, the device was 
> > > active or idle.
> >
> > Boot your machine with enforcing=0 on the kernel line.  If you still have
> > the problem, then it is probably not SELinux.  If it works, then I would
> > try to relabel.
>
> Thanks, Daniel. I have meanwhile overcome the problem by re-installing 
> Fedora. Now, everything seems to be working perfectly.
>
> By the way,
>
> enforcing=0
>
> was to be placed in the line that starts with the word
>
> 'linux',
>
> right?
>
> How can one do the relabeling?
>
> Paul

touch /.autorelabel; reboot

Will cause a relabel at boot, although not necessary now.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.13 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlEG3toACgkQrlYvE4MpobP2wwCeOsvnnkXjwF4WWzN2QYDWR7B+
> Wc0AoK9lmmCpd5po4rI4MQqY54CjkfQD
> =d241
> -----END PGP SIGNATURE-----

[Paul Smith]

On Mon, Jan 28, 2013 at 8:26 PM, Daniel J Walsh  wrote:
> > > Boot your machine with enforcing=0 on the kernel line.  If you still have
> > > the problem, then it is probably not SELinux.  If it works, then I would
> > > try to relabel.
> >
> > Thanks, Daniel. I have meanwhile overcome the problem by re-installing
> > Fedora. Now, everything seems to be working perfectly.
> >
> > By the way,
> >
> > enforcing=0
> >
> > was to be placed in the line that starts with the word
> >
> > 'linux',
> >
> > right?
> >
> > How can one do the relabeling?
>
> touch /.autorelabel; reboot

Thanks, Daniel. But what is the kernel line? The one that starts with
the word 'linux' when one at the booting time presses the key 'e'?

Paul

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/28/2013 03:40 PM, Paul Smith wrote:
> On Mon, Jan 28, 2013 at 8:26 PM, Daniel J Walsh  wrote:
> > > > Boot your machine with enforcing=0 on the kernel line.  If you still
> > > > have the problem, then it is probably not SELinux.  If it works, then
> > > > I would try to relabel.
> > >
> > > Thanks, Daniel. I have meanwhile overcome the problem by re-installing 
> > > Fedora. Now, everything seems to be working perfectly.
> > >
> > > By the way,
> > >
> > > enforcing=0
> > >
> > > was to be placed in the line that starts with the word
> > >
> > > 'linux',
> > >
> > > right?
> > >
> > > How can one do the relabeling?
> >
> > touch /.autorelabel; reboot
>
> Thanks, Daniel. But what is the kernel line? The one that starts with the
> word 'linux' when one at the booting time presses the key 'e'?
>
> Paul

Yes, something like:

linux   /vmlinuz-3.8.0-0.rc4.git1.1.fc19.x86_64
root=UUID=43a08079-a288-4e6f-8767-404eb56b8df3 ro rd.md=0 rd.lvm=0 rd.dm=0
SYSFONT=True  KEYTABLE=us
rd.luks.uuid=luks-d78a7fd8-3aba-4152-82c6-e9000fb2ca83
rd.luks.uuid=luks-f1cc16a9-e403-4eeb-b5c7-5a6aa567f7c6 LANG=en_US.UTF-8 rhgb quiet
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.13 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlEG43QACgkQrlYvE4MpobOPBQCgtfyu8iMp5MJFMeP0bzoU5nl0
> pWMAoLX6wECSXCNfvCb3BusDSaF0rxpV
> =A0oT
> -----END PGP SIGNATURE-----

[Paul Smith]

On Mon, Jan 28, 2013 at 8:45 PM, Daniel J Walsh  wrote:
> > > > > Boot your machine with enforcing=0 on the kernel line.  If you still
> > > > > have the problem, then it is probably not SELinux.  If it works, then
> > > > > I would try to relabel.
> > > >
> > > > Thanks, Daniel. I have meanwhile overcome the problem by re-installing
> > > > Fedora. Now, everything seems to be working perfectly.
> > > >
> > > > By the way,
> > > >
> > > > enforcing=0
> > > >
> > > > was to be placed in the line that starts with the word
> > > >
> > > > 'linux',
> > > >
> > > > right?
> > > >
> > > > How can one do the relabeling?
> > >
> > > touch /.autorelabel; reboot
> >
> > Thanks, Daniel. But what is the kernel line? The one that starts with the
> > word 'linux' when one at the booting time presses the key 'e'?
> >
> > Paul
>
> Yes, something like:
>     linux   /vmlinuz-3.8.0-0.rc4.git1.1.fc19.x86_64
>
> root=UUID=43a08079-a288-4e6f-8767-404eb56b8df3 ro rd.md=0 rd.lvm=0 rd.dm=0
> SYSFONT=True  KEYTABLE=us
> rd.luks.uuid=luks-d78a7fd8-3aba-4152-82c6-e9000fb2ca83
> rd.luks.uuid=luks-f1cc16a9-e403-4eeb-b5c7-5a6aa567f7c6 LANG=en_US.UTF-8 rhgb quiet

Thanks, Daniel. I had done that but with no success. However, I did
not do any relabeling, unfortunately. Anyway, the problem seems to be
overcome now.

Paul

[Wolfgang S. Rupprecht]

Daniel J Walsh  writes:
> touch /.autorelabel; reboot
>
> Will cause a relabel at boot, although not necessary now.

One thing that has always bothered me about the first "restorecon -rv /"
run after a fresh install is how many files are relabeled because the
restorecon database and the rpm that the file came from disagree on the
context.  Should we put in a bug report for these?  Are these things
benign enough to ignore?

-wolfgang