On 2/27/11 5:54 PM, Fernando Cassia wrote:
> On Sun, Feb 27, 2011 at 9:37 PM, James McKenzie
> wrote:
>
>>> Thanks to everyone!. Btw. this box had Fedora 10... not 12... :) I now
>>> realize
>> Time for an upgrade to the lastest version of Fedora?
>>
>> Definitely time to clean up the drive and
On Sun, Feb 27, 2011 at 9:37 PM, James McKenzie wrote:
>> Thanks to everyone!. Btw. this box had Fedora 10... not 12... :) I now
>> realize
> Time for an upgrade to the lastest version of Fedora?
>
> Definitely time to clean up the drive and rid it of all unnecessary baggage.
>
> James McKenzie
On 2/27/11 4:01 PM, Fernando Cassia wrote:
> On Sun, Feb 27, 2011 at 7:43 PM, JB wrote:
>> So it would be:
>> selinux=0 enforcing=0 1
>>
>> Try it and report back.
> Worked like a charm. The combination of first booting to runlevel 1,
> erasing some stuff to bring disk usage down from 100% to 98%
Fernando Cassia gmail.com> writes:
> ...
> Ok, runlevel 1 I went and erased some VirtualBox VM vdis taking a
> couple gigs. Now space free is 98% according to "df". I hope SELinux
> stops panicking now.
>
> BTW: Is it "working as designed" to have an OS become comatose and
> unable to boot when
Please don´t fight, don´t need to. The problem was solved, thanks to you all.
A little manners goes a long way. No need to point fingers and accuse
others of being "wrong". :)
FC
On Sun, Feb 27, 2011 at 8:25 PM, compdoc wrote:
>> Wrong. Runlevel 1 is single-user mode.
>
> Naw, I wasn't wrong -
> Wrong. Runlevel 1 is single-user mode.
Naw, I wasn't wrong - I was just explaining in a way anyone can understand.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fe
On 02/27/2011 02:43 PM, compdoc wrote:
> As Kevin J. Cummings said, you want to boot to runlevel 1, which is text mode.
> Boot to the command line, in other words.
Wrong. Runlevel 1 is single-user mode. You aren't connected to the net
by default and only the root partition (and, if needed, /boo
On Sun, Feb 27, 2011 at 7:43 PM, JB wrote:
>
> So it would be:
> selinux=0 enforcing=0 1
>
> Try it and report back.
Worked like a charm. The combination of first booting to runlevel 1,
erasing some stuff to bring disk usage down from 100% to 98% and then
disabling SELinux did the trick.
Thanks
On Sun, Feb 27, 2011 at 7:17 PM, Fernando Cassia wrote:
> Thanks, will try that.
>
> Confirms my suspicion: SELinux´ best feature is to disable it. ;) (JOKE, JOKE)
> FC
Ok, runlevel 1 I went and erased some VirtualBox VM vdis taking a
couple gigs. Now space free is 98% according to "df". I hope S
Fernando Cassia gmail.com> writes:
>
> On Sun, Feb 27, 2011 at 7:12 PM, JB gmail.com> wrote:
> > Fernando Cassia gmail.com> writes:
> >
> >> ...
> >> The issue is that I get the normal Fedora boot screen , then the
> >> hourglass, then the log-in screen,then I get
> >>
> >> Oops, sealert hit a
As Kevin J. Cummings said, you want to boot to runlevel 1, which is text mode.
Boot to the command line, in other words.
Google: fedora 12 runlevel 1
And if you are able to log in as root, you need to look at all of your
partitions and see which one is full. If you aren't sure what to delete,
On Sun, Feb 27, 2011 at 7:12 PM, JB wrote:
> Fernando Cassia gmail.com> writes:
>
>> ...
>> The issue is that I get the normal Fedora boot screen , then the
>> hourglass, then the log-in screen,then I get
>>
>> Oops, sealert hit an error!
>>
>> Traceback (most recent call last):
>> ...
>
> Stop b
On Sun, Feb 27, 2011 at 7:12 PM, JB wrote:
> Stop boot loader, edit kernel boot line, and disable selinux for now.
> kernel /boot/vmlinuz-... ... selinux=0
>
> This may get you thru ...
>
> JB
Thanks, will try that.
Confirms my suspicion: SELinux´ best feature is to disable it. ;) (JOKE, JOKE)
Fernando Cassia gmail.com> writes:
> ...
> The issue is that I get the normal Fedora boot screen , then the
> hourglass, then the log-in screen,then I get
>
> Oops, sealert hit an error!
>
> Traceback (most recent call last):
> ...
Stop boot loader, edit kernel boot line, and disable selinux
On 02/27/2011 05:01 PM, Fernando Cassia wrote:
> I have one old machine running Fedora 12, kernel 2.6.27.
> Suddenly one day after doing system updates (and it was downloading
> some torrents in the background) the system would no longer boot
> properly, and the system says the disk is full (probab
I have one old machine running Fedora 12, kernel 2.6.27.
Suddenly one day after doing system updates (and it was downloading
some torrents in the background) the system would no longer boot
properly, and the system says the disk is full (probably is).
The issue is that I get the normal Fedora boot
16 matches
Mail list logo
