On 11/27/2011 06:13 AM, Sam Varshavchik wrote:
>
> Again, I'd suggest uninstalling the most recent kernel, and reinstalling
> it, in order to regenerate the initrd, and the grub menu item for it,
> afresh.
I haven't quite done that, but I have something new to report. The
following is quoted fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2011 09:53 AM, JB wrote:
> Daniel J Walsh redhat.com> writes:
>
>>
>>
>> On 12/07/2011 03:14 AM, JB wrote:
>>> JB gmail.com> writes:
>>>
...
>>>
>>> To make my point clear.
>>>
>>> In general, the resuce mode turns all services of
Daniel J Walsh redhat.com> writes:
>
>
> On 12/07/2011 03:14 AM, JB wrote:
> > JB gmail.com> writes:
> >
> >> ...
> >
> > To make my point clear.
> >
> > In general, the resuce mode turns all services off for the purpose
> > of preserving the original troubled environment (machine state) an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2011 03:14 AM, JB wrote:
> JB gmail.com> writes:
>
>> ...
>
> To make my point clear.
>
> In general, the resuce mode turns all services off for the purpose
> of preserving the original troubled environment (machine state) and
> preventing
JB gmail.com> writes:
> ...
To make my point clear.
In general, the resuce mode turns all services off for the purpose of preserving
the original troubled environment (machine state) and preventing any worsening
of it until it can be investigated or fixed.
So it seems a rescue mode should not
Marko Vojinovic gmail.com> writes:
> ...
> >
> > Case:
> > - I disable selinux
> > # cat /etc/sysconfig/selinux ...
> > SELINUX=disabled
> > - I reboot the system,
> > - /.autorelabel created by sys init,
> > - I enable selinux again,
> > - I reboot with intention to boot rescue mode kernel
On Tuesday 06 December 2011 22:16:40 JB wrote:
> Daniel J Walsh redhat.com> writes:
> > ...
> > SELinux relabeling is caused by booting a rescue mode kernel. As soon
> > as you boot a system with SELinux disabled, the init system creates
> > the /.autorelabel file, so the next time it boots with
Daniel J Walsh redhat.com> writes:
> ...
> SELinux relabeling is caused by booting a rescue mode kernel. As soon
> as you boot a system with SELinux disabled, the init system creates
> the /.autorelabel file, so the next time it boots with SELinux it will
> relabel.
>
Question:
Are you not se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/06/2011 02:44 PM, Joe Zeff wrote:
> On 12/06/2011 11:31 AM, Terry Polzin wrote:
>> Is there an error is /etc/sysconfig/selinux?
>
> No.
SELinux relabeling is caused by booting a rescue mode kernel. As soon
as you boot a system with SELinux disa
On 12/06/2011 11:31 AM, Terry Polzin wrote:
> Is there an error is /etc/sysconfig/selinux?
No.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailin
On Tue, 2011-12-06 at 10:52 -0800, Joe Zeff wrote:
> On 12/06/2011 06:13 AM, JB wrote:
> > To remove an unneeded kernel:
> > # yum list installed "*kernel*"
> > ...
> > kernel.i686 3.1.1-1.fc16
> > @updates
> > ...
> > # yum remove "*kernel*3.1.1-1.fc1
On 12/06/2011 06:13 AM, JB wrote:
> To remove an unneeded kernel:
> # yum list installed "*kernel*"
> ...
> kernel.i686 3.1.1-1.fc16
> @updates
> ...
> # yum remove "*kernel*3.1.1-1.fc16*"
>
> Now, reboot your system to your latest F16 kernel and see w
On Mon, 2011-12-05 at 13:37 -0800, Joe Zeff wrote:
> Currently, the laptop goes into emergency mode and hangs two out of
> three times if I use the newest kernel. The third time it continues
> until it says that SELinux needs to relabel things and that it might
> take a while. Then it just sit
Joe Zeff zeff.us> writes:
>
> Currently, the laptop goes into emergency mode and hangs two out of
> three times if I use the newest kernel. The third time it continues
> until it says that SELinux needs to relabel things and that it might
> take a while.
Change selinux config to this (for t
On 12/05/2011 05:57 PM, Craig White wrote:
> I am under the impression that you can change the 'installonly_limit'
> value in /etc/yum.conf (of which kernel is definitely one of those) but
> to be honest, I've never tinkered with it.
I've also heard that, but wasn't sure just where it was. I wond
Currently, the laptop goes into emergency mode and hangs two out of
three times if I use the newest kernel. The third time it continues
until it says that SELinux needs to relabel things and that it might
take a while. Then it just sits with no disk activity until I power
cycle it. If I try
On 11/27/2011 06:13 AM, Sam Varshavchik wrote:
> Again, I'd suggest uninstalling the most recent kernel, and reinstalling
> it, in order to regenerate the initrd, and the grub menu item for it,
> afresh.
I used yumex to do a full update on my laptop, having it remove the most
recent kernel as wel
On 11/27/2011 06:13 AM, Sam Varshavchik wrote:
> Again, I'd suggest uninstalling the most recent kernel, and reinstalling
> it, in order to regenerate the initrd, and the grub menu item for it,
> afresh.
More info, now that I've had the time to play with my laptop. First,
the kernel in question
On 12/01/2011 02:15 PM, Sam Varshavchik wrote:
> It's not clear if your grubby warnings are due to the old grub 1 config,
> or the current grub 2 config. If it's grub 1, deleting grub.cfg will
> shut grubby up. If it's grub 2, I found that rerunning grub2-mkconfig
> generates a new grub 2 config fi
Joe Zeff writes:
On 12/01/2011 04:02 AM, Sam Varshavchik wrote:
> As log as grubby did its job with grub2, there is no issue.
>
> If grubby is having a problem with grub2, using grub2-mkconfig should
> fix it.
More thoughts. Remember, Sam, that I can't boot into the new kernel so
there might b
On 12/01/2011 12:38 PM, Terry Polzin wrote:
> Can you boot into rescue mode from install media (don't forget to enable
> the network) and mount the filesystems?
>
> chroot /mnt/sysimage ; then try another yum update see if a newer kernel
> yet will fix things.
Why? I can, and do boot into the las
On Thu, 2011-12-01 at 12:17 -0800, Joe Zeff wrote:
> On 12/01/2011 04:02 AM, Sam Varshavchik wrote:
> > As log as grubby did its job with grub2, there is no issue.
> >
> > If grubby is having a problem with grub2, using grub2-mkconfig should
> > fix it.
>
> More thoughts. Remember, Sam, that I ca
On 12/01/2011 04:02 AM, Sam Varshavchik wrote:
> As log as grubby did its job with grub2, there is no issue.
>
> If grubby is having a problem with grub2, using grub2-mkconfig should
> fix it.
More thoughts. Remember, Sam, that I can't boot into the new kernel so
there might be an issue. (I jus
On 12/01/2011 04:02 AM, Sam Varshavchik wrote:
>
> If you upgraded from F15, grubby is complaining about the old grub.cfg.
> This is harmless. rm /etc/grub.cfg to make this complaint go away.
No, from F14, but the point's still good. As to the other, I'll try it
as soon as I have time, then repo
Joe Zeff writes:
On 11/27/2011 06:13 AM, Sam Varshavchik wrote:
> Again, I'd suggest uninstalling the most recent kernel, and reinstalling
> it, in order to regenerate the initrd, and the grub menu item for it,
> afresh.
More information, now that I'm home again and have time to dig into
this.
On 11/27/2011 06:13 AM, Sam Varshavchik wrote:
> Again, I'd suggest uninstalling the most recent kernel, and reinstalling
> it, in order to regenerate the initrd, and the grub menu item for it,
> afresh.
More information, now that I'm home again and have time to dig into
this. I went back into t
On 11/27/2011 05:05 PM, Mikkel L. Ellertson wrote:
> You may want to run "yum reinstall" instead. I am
> not 100% sure, but it should generate a new initrd.
I've just gotten home and haven't had time to bring in everything (too
tired) let alone set up my laptop. However, man yum has this to say
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/27/2011 10:19 AM, Joe Zeff wrote:
> On 11/27/2011 06:13 AM, Sam Varshavchik wrote:
>>
>> Again, I'd suggest uninstalling the most recent kernel, and reinstalling
>> it, in order to regenerate the initrd, and the grub menu item for it,
>> afresh.
On 11/27/2011 06:13 AM, Sam Varshavchik wrote:
>
> Again, I'd suggest uninstalling the most recent kernel, and reinstalling
> it, in order to regenerate the initrd, and the grub menu item for it,
> afresh.
That's probably the best idea of all. I don't remember your mentioning
it before and don't
On 11/27/2011 04:09 AM, JB wrote:
> From there you can run all you can, e.g.
> # fsck
> # package-cleanup --dupes
> # package-cleanup --problems
> # rpm -V -a --quiet
> and whatever else you wish
I suspect that things aren't quite as bad as you think; I'm using the
"badly corrupted" computer rig
Joe Zeff writes:
On 11/26/2011 09:27 PM, Sam Varshavchik wrote:
> No, you most certainly do. Everyone who installs Fedora ends up
> encrypting something. I'll bet that all your passwords in /etc/shadow
> are encrypted, for example. Because that's the kind of things
> libgcrypt.so.1 is responsibl
Joe Zeff zeff.us> writes:
>
> On 11/26/2011 09:10 PM, Sam Varshavchik wrote:
> > Furthermore, if you have a corrupted libcrypt.so.1, it wouldn't matter
> > which kernel you're booting
>
> The specific message is that /sbin/sulogin failed because it coulden't
> find libcrypt.so.1.
>
> I touche
On 11/26/2011 09:27 PM, Sam Varshavchik wrote:
> No, you most certainly do. Everyone who installs Fedora ends up
> encrypting something. I'll bet that all your passwords in /etc/shadow
> are encrypted, for example. Because that's the kind of things
> libgcrypt.so.1 is responsible for.
I sit correc
Joe Zeff writes:
On 11/26/2011 09:10 PM, Sam Varshavchik wrote:
> Furthermore, if you have a corrupted libcrypt.so.1, it wouldn't matter
> which kernel you're booting. You wouldn't be able to boot anything. No
> matter which kernel you boot, you're running the same userspace, and the
> same set
On 11/26/2011 09:10 PM, Sam Varshavchik wrote:
> Furthermore, if you have a corrupted libcrypt.so.1, it wouldn't matter
> which kernel you're booting
The specific message is that /sbin/sulogin failed because it coulden't
find libcrypt.so.1.
I touched /forcefsck and rebooted into the F16 kernel a
On 11/26/2011 09:10 PM, Sam Varshavchik wrote:
> Furthermore, if you have a corrupted libcrypt.so.1, it wouldn't matter
> which kernel you're booting. You wouldn't be able to boot anything. No
> matter which kernel you boot, you're running the same userspace, and the
> same set of userspace librari
Joe Zeff writes:
Recently I upgraded my laptop to F16 using preupgrade. This morning, at
a convention, I did a system update that included (I thought) a new
kernel. The next time I booted, the system hung, with no output. I had
to power-cycle to try again, this time getting error messages: it
Recently I upgraded my laptop to F16 using preupgrade. This morning, at
a convention, I did a system update that included (I thought) a new
kernel. The next time I booted, the system hung, with no output. I had
to power-cycle to try again, this time getting error messages: it
couldn't find l
38 matches
Mail list logo
