I will schedule a relabel and take a look at my box. ssd relabel is
pretty quick.
On 12/16/2014 06:07 PM, Tom Horsley wrote:
> On Tue, 16 Dec 2014 16:58:41 -0500
> Daniel J Walsh wrote:
>
>> What version of Fedora was this?
> A brand new fedora 21 workstation install.
>
On Tue, 16 Dec 2014 16:58:41 -0500
Daniel J Walsh wrote:
> What version of Fedora was this?
A brand new fedora 21 workstation install.
> restorecon -p -R /
> 7.4%^C
>
> Shows Percent done now.
I'm not sure the actual percentage makes it through
systemd though to the messages I was looking at du
What version of Fedora was this?
restorecon -p -R /
7.4%^C
Shows Percent done now.
On 12/16/2014 02:03 PM, Tom Horsley wrote:
> On Tue, 16 Dec 2014 13:36:08 -0500
> Daniel J Walsh wrote:
>
>> There should be an indicator on the screen telling you the progress of
>> t
On Tue, 16 Dec 2014 13:36:08 -0500
Daniel J Walsh wrote:
> There should be an indicator on the screen telling you the progress of
> the relabel.
I don't remember for sure, but I think there was just a cylon eyeball
bouncing asterisks, not anything telling me about progress.
> DI
al image.
>>
>> When it booted, it said "I've got to relabel everything,
>> this may take a while."
>>
>> So I figured I'd just wait for it, then a few minutes
>> later a message came up about a watchdog expiring
>> and it rebooted the s
On Sat, 13 Dec 2014 09:52:35 -0500
Tom Horsley wrote:
> Just a note for someone who might care about this:
>
> I foolishly forgot to disable selinux in a system
> I created by copying all the files from a virtual image.
>
> When it booted, it said "I've got to re
Just a note for someone who might care about this:
I foolishly forgot to disable selinux in a system
I created by copying all the files from a virtual image.
When it booted, it said "I've got to relabel everything,
this may take a while."
So I figured I'd just wait for it
On Tue, 2014-04-29 at 12:03 -0700, Dan Thurman wrote:
> You are top-posting!
IIRC he's using a severely broken webmail system which doesn't even do
threading correctly.
poc
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedorapro
On 04/29/2014 11:58 AM, Patrick Dupre wrote:
Thank,
I know, but I guess that there is an option from grub2
by setting something!!
On 04/29/2014 11:46 AM, Patrick Dupre wrote:
Hello,
I guess that I can force the relabel of a disk or partition at boot
by using grub2, but I cannnot rememeber
Thank,
I know, but I guess that there is an option from grub2
by setting something!!
> On 04/29/2014 11:46 AM, Patrick Dupre wrote:
> > Hello,
> >
> > I guess that I can force the relabel of a disk or partition at boot
> > by using grub2, but I cannnot rememeber how t
On Tue, Apr 29, 2014 at 1:46 PM, Patrick Dupre wrote:
> Hello,
>
> I guess that I can force the relabel of a disk or partition at boot
> by using grub2, but I cannnot rememeber how to do it!!
You can use Dan's method or this link has a grub option:
http://fedoraproject.
On 04/29/2014 11:46 AM, Patrick Dupre wrote:
Hello,
I guess that I can force the relabel of a disk or partition at boot
by using grub2, but I cannnot rememeber how to do it!!
Thank for your help.
===
Patrick DUPRÉ
Hello,
I guess that I can force the relabel of a disk or partition at boot
by using grub2, but I cannnot rememeber how to do it!!
Thank for your help.
===
Patrick DUPRÉ | | email: pdu
Hello Chris,
> >
> > I am back with you.
> > Thinking about your suggestion.
>
> How did you clone it? Did you use cp? Did you use rsync? What was the exact
> command?
>
>
> > I generate a file: /boot/grub2/grub.cfg
>
> Did you use chroot at all?
Yes I did
That is, did you mount the clone's
On Dec 27, 2013, at 6:45 PM, "Patrick Dupre" wrote:
> Hello Chris,
>
> I am back with you.
> Thinking about your suggestion.
How did you clone it? Did you use cp? Did you use rsync? What was the exact
command?
> I generate a file: /boot/grub2/grub.cfg
Did you use chroot at all? That is, di
Hello Chris,
I am back with you.
Thinking about your suggestion.
I generate a file: /boot/grub2/grub.cfg
and
a file initramfs
but these files are on the clone.
If I understand (I guess) the point in generating a new initramfs, I do not
see the point in generating a new grub.cfg file since it is no
On Thu, Dec 26, 2013 at 12:18 PM, Patrick Dupre wrote:
>
> I try to uncompress the new img, but it does not work
> cpio -i -d -H newc -F ../initramfs-3.12.5-200.fc19.i686.PAE.img
> --no-absolute-filenames
>
> cpio: premature end of file
It's gzipped too.
gzip -dc ../initramfs-3.12.5-200.fc19.i6
Hello Chris,
Thank for your help.
I did exactly like you said, but the result is the same as before.
I am sure that the issue is with the initramfs.
According to the tests that I made. it is probably due to the /boot
which is not found
However, how can I know exactly what is going on?
I try to u
On Dec 25, 2013, at 5:48 PM, Patrick Dupre wrote:
> Hello,
>
> I wanted to clone my distribution fedora 19, I used to do it with
> previous release but I failed with fedora 19.
>
> I copy (-a) the partition / (lvm2) and /boot (ext4)
You probably need to remake the initramfs. The easiest way t
Hello,
I wanted to clone my distribution fedora 19, I used to do it with
previous release but I failed with fedora 19.
I copy (-a) the partition / (lvm2) and /boot (ext4)
I ran:
grub2-mkconfig -o /boot/grub2/grub.cfg
fixfiles relabel (the new partitions)
the file grub.cfg seems OK.
To try to
On Wed, 25 Dec 2013 18:46:35 +0100
"Patrick Dupre" wrote:
> Hello,
>
> I dupliqued a distribution.
> I propably need to relabel the partitions.
> and/or run restorecon
> How I do it in fedora19 ?
>
> Thank.
>
sudo fixfiles onboot # then reboot
Hello,
I dupliqued a distribution.
I propably need to relabel the partitions.
and/or run restorecon
How I do it in fedora19 ?
Thank.
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire
on the file /etc/X11/xinit/Xsession
>
> I can boot single user okay.
>
> I ran 'fixfiles restore' to relabel again and rebooted, and it made no
> difference.
>
> By comparing with a similar but un-upgraded (ie F13) working host, I
>
ker from entrypoint
> > access on the file /usr/bin/gnome-keyring/daemon
> > SELinux is preventing /usr/libexec/gdm-session-worker from entrypoint
> > access on the file /etc/X11/xinit/Xsession
> >
> > I can boot single user okay.
> >
> > I ran 'fixf
on the file /etc/X11/xinit/Xsession
>
> I can boot single user okay.
>
> I ran 'fixfiles restore' to relabel again and rebooted, and it made no
> difference.
>
> By comparing with a similar but un-upgraded (ie F13) working host, I
>
access on
the file /usr/bin/gnome-keyring/daemon
SELinux is preventing /usr/libexec/gdm-session-worker from entrypoint access on
the file /etc/X11/xinit/Xsession
I can boot single user okay.
I ran 'fixfiles restore' to relabel again and rebooted, and it made no
difference.
By comparing
26 matches
Mail list logo
