On 02/24/2012 07:34 PM, Tom H wrote:
On Fri, Feb 24, 2012 at 8:41 PM, Chuck Forsberg WA7KGX N2469R
wrote:
On 02/23/2012 08:50 PM, Tom H wrote:
On Thu, Feb 23, 2012 at 4:55 AM, Chuck Forsberg WA7KGX N2469R
wrote:
Here is the relevant /etc/exports entry in my server:
/ 192.168.1.1/255.2
On Fri, Feb 24, 2012 at 8:41 PM, Chuck Forsberg WA7KGX N2469R
wrote:
> On 02/23/2012 08:50 PM, Tom H wrote:
>> On Thu, Feb 23, 2012 at 4:55 AM, Chuck Forsberg WA7KGX N2469R
>> wrote:
>>>
>>> Here is the relevant /etc/exports entry in my server:
>>> / 192.168.1.1/255.255.255.0(rw,async)
>>>
>>>
modprobe nfs complains about failed memory allocation.
This was on the 32 bit, will try 64 bit later.
NFS mounts worked fine on 64 bit RC3 on another machine.
On 02/23/2012 08:50 PM, Tom H wrote:
On Thu, Feb 23, 2012 at 4:55 AM, Chuck Forsberg WA7KGX N2469R
wrote:
Here is the relevant /etc/e
Message: 6
Date: Fri, 24 Feb 2012 17:25:24 -0500
From: Claude Jones
To: For testing and quality assurance of Fedora releases
Subject: Re: VirtualBox and test releases
Message-ID:<4f480e54.50...@tehogeeservices.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 2/24/2012 4:23
On 2/24/2012 4:23 PM, Richard Shaw wrote:
Although the interface is slow, I haven't had the same multi-minute
delays you speak of. Also, I've found that to build guest additions
all you need is:
$ yum install gcc kernel-headers kernel-devel make dkms
> this is pretty useless
I hope you figur
On Fri, Feb 24, 2012 at 3:20 PM, Claude Jones
wrote:
> ...
> Then I followed Andre's suggestion and after a lot of fiddling and having to
> install gcc and its dependencies and other stuff, I finally got the GL
> module to build successfully; that's where I'm rebooting from now...so,
> let's see w
On 2/24/2012 11:03 AM, Claude Jones wrote:
On 2/24/2012 1:34 AM, Adam Williamson wrote:
As ajax says, check if you're getting software rendering of GNOME Shell,
which is likely to be slow: if so you can force fallback mode from a VT,
much faster than trying to get through the control center, wit
On Fri, 2012-02-24 at 08:11 -0500, Josh Boyer wrote:
> On Fri, Feb 24, 2012 at 5:55 AM, Kamil Paral wrote:
> >> Almost all FC17 kernels are debug kernels. A quick way to tell if
> >> you're
> >> using one is:
> >>
> >> grep -i CONFIG_ACPI_DEBUG /boot/config-`uname -r`
> >>
> >> 'not set' = release
On 02/24/2012 10:03 AM, Rawhide Report wrote:
> [coccinella]
> coccinella-0.96.20-3.fc17.noarch requires memchan
I've put memchan up for a new review to revive it and resolve this
broken dep. If anyone would be so kind as to help me out here, I would
appreciate it. :)
https://bugzilla.redha
On 2/24/2012 1:34 AM, Adam Williamson wrote:
As ajax says, check if you're getting software rendering of GNOME Shell,
which is likely to be slow: if so you can force fallback mode from a VT,
much faster than trying to get through the control center, with this
command:
gsettings set org.gnome.des
On Fri, Feb 24, 2012 at 10:25:02 -0500,
"Clyde E. Kunkel" wrote:
> Is this program still viable? Are applicants being accepted?
Yes applicants are still accepted.
We aren't sure how we are going to use this group going forward, but having
people test updates and report feedback is still good
Is this program still viable? Are applicants being accepted?
TIA
--
Regards,
OldFart
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
On Fri, Feb 24, 2012 at 5:55 AM, Kamil Paral wrote:
>> Almost all FC17 kernels are debug kernels. A quick way to tell if
>> you're
>> using one is:
>>
>> grep -i CONFIG_ACPI_DEBUG /boot/config-`uname -r`
>>
>> 'not set' = release kernel. 'Y' = debug kernel.
>>
>> The kernel team is building one ke
> Almost all FC17 kernels are debug kernels. A quick way to tell if
> you're
> using one is:
>
> grep -i CONFIG_ACPI_DEBUG /boot/config-`uname -r`
>
> 'not set' = release kernel. 'Y' = debug kernel.
>
> The kernel team is building one kernel per upstream kernel release (I
> think that's it) as '
Compose started at Fri Feb 24 08:15:17 UTC 2012
Broken deps for x86_64
--
[HippoDraw]
HippoDraw-devel-1.21.3-2.fc17.i686 requires python-numarray
HippoDraw-devel-1.21.3-2.fc17.x86_64 requires python-numarray
HippoDraw-
I've noticed that, as with previous versions of GNOME 3, bluetooth and
network on/off settings do not survive a reboot. If I disable bluetooth
by toggling the switch to off, next reboot it is on again. Is this
as-designed?
Some other experiences with F17 alpha-RC4:
- ipv6 addressing is now working
16 matches
Mail list logo
