On 04/12/2012 06:41 AM, David Lehman wrote:
> On Wed, 2012-04-11 at 11:08 +0530, Kashyap Chamarthy wrote:
>>>
>>> I'm going give it a try w/ btrfs partitioning. Meanwhile, I wasn't keeping
>>> up. Can someone
>>> confirm, does /boot still need to be ext3/ext4 for btrfs to work?
>>>
>>
>>
>> Ok, I
At today's F17 Beta Go/No-Go meeting, the Fedora 17 Beta release was
declared gold. F17 Beta will be released Tuesday, April 17, 2012.
Thanks to everyone involved for pulling this one together and
participating in the meetings, things came together well this week. :)
For those interested in t
On 04/11/2012 08:52 PM, Michael Hennebry wrote:
On Wed, 11 Apr 2012, Michael Hennebry wrote:
Here is the final grub stanza:
title Install Fedora16 from iso 11 15:34
root (hd0,2)
kernel /isolinux16/vmlinuz repo=hd:LABEL=/home1:/iso16 acpi=off
processor.nocst=1 maxcpus=1 selinux=0
initrd /isolinu
On Wed, 2012-04-11 at 11:08 +0530, Kashyap Chamarthy wrote:
> >
> > I'm going give it a try w/ btrfs partitioning. Meanwhile, I wasn't keeping
> > up. Can someone
> > confirm, does /boot still need to be ext3/ext4 for btrfs to work?
> >
>
>
> Ok, I gave it a try w/ the below command line, and
On Wed, 11 Apr 2012, Michael Hennebry wrote:
On Tue, 10 Apr 2012, mwesten wrote:
If this is the kernel bug you are referring to, perhaps there is a
workaround you could use to get your minimal CD running in order to do
an install.
The description of that patch suggests that passing any one
Minor glitch in gnome-packagekit (gpk-update-viewer) that causes trouble
with subsequent updates.
Bugzilla 811772 has the report about a failure due to "<" character in
input stream
two workarounds really:
1. use yum to install something and let it record the acknowledgement
of the signing
I updated to the latest pan from updates testing, and once it was
installed I could no longer log on to my news provider from pan. I
downgraded, and removed the changes left behind, and was able to do so
again. I'm not sure why, but it asked to create certificates on a non
encrypted connection ev
On Tue, 10 Apr 2012, mwesten wrote:
If this is the kernel bug you are referring to, perhaps there is a
workaround you could use to get your minimal CD running in order to do
an install.
The description of that patch suggests that passing any one of these
kernel parameters will prevent the pr
The following Fedora 15 Security updates need testing:
https://admin.fedoraproject.org/updates/FEDORA-2012-5256/wireshark-1.4.12-1.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-5631/phpMyAdmin-3.5.0-1.fc15
https://admin.fedoraproject.org/updates/FEDORA-2012-4417/mingw-lib
Hi, folks. You may have noticed a 17 Beta RC4.1 directory show up on the
mirror:
http://dl.fedoraproject.org/pub/alt/stage/17-Beta.RC4.1
and been asking yourself what it is. Well, wonder no more. We built the
live images for Beta RC4 with livecd-tools 17.7, in an attempt to fix
this bug:
https:/
On Wed, 2012-04-11 at 00:12 -0700, Dan Mashal wrote:
> You are going to go through some real pain to get btrfs working. I
> don't think an "fsck" utility even exists for btrfs yet. Patience is a
> virtue. There's a reason why it's disabled.
The reason is that the anaconda backend code for dealing
> /etc/grub2.cfg should be a symlink to /boot/grub2/grub.cfg
>
> You should really add your custom menuentry to
> /etc/grub.d/40_custom (careful, you have typo in your
> "menuentry" keyword). Then you should run:
>
> # grub2-mkconfig -o /boot/grub2/grub.cfg
>
> and it should appear in /boot/grub
On Tue, 10 Apr 2012, Antonio Olivares wrote:
but am at the same place. I also want to remove rhgb and quiet from the grub
entry, I did it manually in /boot/grub2/grub.cfg but running the command above
restored it back :(
The default options are under /etc/default/grub, this is somewhat
un
> Dear folks,
>
> I have succeded in installing Fedora 17 nightly build. I have
> successfully added the updates as of yesterday and today. I cannot
> add FreeBSD entry to the grub2 configuration. I have read several
> howto's but only Fedora and two entries for windows show up:
>
> [root@acer
> > The new proposed criterion is this:
> >
> > The installer must be able to boot using kernel+initrd pair (some
> > boot arguments might be needed), e.g. booting a VM or from PXE.
> > Fetching the installer's root image must work using the same
> > access protocols as are required for fetchi
On 11/04/12 08:58, Rob Healey wrote:
> Greetings:
>
> Major crash! Please fix before releasing Fedora 17
>
> Here is what I received on my terminal window regarding this crash...
>
> [Frog@FartingSalmon gep-026]$ pysetup run sdist
> running sdist
> running check
would you mind and provide s
You are going to go through some real pain to get btrfs working. I don't
think an "fsck" utility even exists for btrfs yet. Patience is a virtue.
There's a reason why it's disabled.
Dan
On Wed, Apr 11, 2012 at 12:00 AM, hamidou dia wrote:
> Hi Kashyap,
>
> It was an all-ext4 install, I haven tr
Hi Kashyap,
It was an all-ext4 install, I haven tried yet btrfs. If I have a
moment today, I ll give it a try with / and /boot as btrfs fs type.
I'll keep you posted.
Regards
Hami
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/
18 matches
Mail list logo
