On 14/06/11 11:02, Lucas wrote:
snip
The only possible way to boot is to add selinux=0.
Especially for Daniel J Walsh, the addition of enforcing=0 doesn't make any
difference - boot stops.
Thanks.
Last time I had similar problem, ended up:
rpm -e --nodeps selinux-policy
On 06/14/2011 02:10 PM, Frank Murphy wrote:
On 14/06/11 11:02, Lucas wrote:
snip
The only possible way to boot is to add selinux=0.
Especially for Daniel J Walsh, the addition of enforcing=0 doesn't make
any difference - boot stops.
Thanks.
Last time I had similar problem, ended up:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/14/2011 06:37 AM, Lucas wrote:
On 06/14/2011 02:10 PM, Frank Murphy wrote:
On 14/06/11 11:02, Lucas wrote:
snip
The only possible way to boot is to add selinux=0.
Especially for Daniel J Walsh, the addition of enforcing=0 doesn't make
any
On 06/14/2011 04:38 PM, Daniel J Walsh wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/14/2011 06:37 AM, Lucas wrote:
On 06/14/2011 02:10 PM, Frank Murphy wrote:
On 14/06/11 11:02, Lucas wrote:
snip
The only possible way to boot is to add selinux=0.
Especially for Daniel J
On Tue, 14.06.11 18:48, Lucas (macach...@gmail.com) wrote:
Do you see any errors?
Just checked it. Yum reinstalled selinux-policy-targeted, then relabeling,
then reboot and process
stops on: Starting Remount Root FS. And nothing more, no errors, systemd hung.
Boot with
On Tue, Jun 14, 2011 at 06:48:43PM +0400, Lucas wrote:
Just checked it. Yum reinstalled selinux-policy-targeted, then relabeling,
then reboot and process stops on: Starting Remount Root FS. And nothing
more, no errors, systemd hung.
Are you sure it's not doing an fsck? (There's an open bug for
Le mardi 14 juin 2011 à 22:06 +0400, Lucas a écrit :
May be I know what is going on. May be I did something.
FYI I have the same problem on my box. Was waiting for fixed 3.0 kernel
packages to report a bug. I suspect some kernel/systemd mismatch
--
Nicolas Mailhot
--
devel mailing list
I checked it again - it is not me.
Boot stops at random points - for example last time it stops at:
Configure read-only root support
So it can't even relabel FS, because it happens mush farther.
But option selinux=0 solves this problem.
Thanks.
--
devel mailing list
On Tue, Jun 14, 2011 at 12:25 PM, Matthew Miller mat...@mattdm.org wrote:
Are you sure it's not doing an fsck? (There's an open bug for that.)
I'm having the same problem with an i686 Rawhide virtual machine
(using KVM, on a Fedora 15 x86_64 host). The last few lines I see
before the hang are
On Tue, Jun 14, 2011 at 1:16 PM, Jerry James loganje...@gmail.com wrote:
I'm having the same problem with an i686 Rawhide virtual machine
(using KVM, on a Fedora 15 x86_64 host). The last few lines I see
before the hang are these:
Like Lucas, I can boot with selinux=0. I did so, and upgraded
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/14/2011 04:42 PM, Jerry James wrote:
On Tue, Jun 14, 2011 at 1:16 PM, Jerry James loganje...@gmail.com wrote:
I'm having the same problem with an i686 Rawhide virtual machine
(using KVM, on a Fedora 15 x86_64 host). The last few lines I see
On Tue, Jun 14, 2011 at 3:08 PM, Daniel J Walsh dwa...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/14/2011 04:42 PM, Jerry James wrote:
[snip]
Like Lucas, I can boot with selinux=0. I did so, and upgraded to
today's Rawhide packages. Since reinstalling
12 matches
Mail list logo
