On 06/14/2011 11:43 AM, Somebody in the thread at some point said:
>> For what's left, eg ARM9+ that you can run normal Linux and Fedora on,
>> ipv6 is going to be workable if the memory allows. Looking a year or
>> two ahead, where "Embedded" will extend to Cortex A15 quad core, and
>> IPv6 will
On 06/14/2011 11:17 AM, Somebody in the thread at some point said:
Hi -
>> Dude, systemd requires the functionality of the three modules it loads
>> explicitly.
>
> systemd requires ipv6.
> And you pitch systemd to be used by embedded devices.
>
> Do you really think all embedded devices will be
On 06/14/2011 05:57 AM, Somebody in the thread at some point said:
> Fedora could well benefit from switching to a rolling release model
> as well (no not rawhide - a controlled rolling release much as the
> kernel development follows).
I've been living from rawhide on my main laptop for a f
Hi -
Maybe it's common knowledge already but the 3.0 / 3.0.0 thing has led to
the uname -r of the kernel not matching the packaged module path.
Your boot will be a "bit minimal" until you stick a symlink in along the
lines of -->
ln -sf /lib/modules/3.0-0.rc1.git0.1.fc16.x86_64
/lib/modules/3
On 04/23/2011 08:46 PM, Somebody in the thread at some point said:
Hi -
> I've setup FC15 beta for my 76-year old uncle. The major issues
> encountered:
> * wake up from suspend didn't work on his laptop; on another one does
I thought my suspend was broken on this laptop. But it turned out it
Hi -
Building on the work of Lennert Buytenhek and David Woodhouse I recently
uplevelled the spec files for gcc and binutils they did for gcc-4.1.2
and binutils-2.17.50.0.18 to work with recent rawhide gcc and binutils.
The goal of the spec changes is to allow rpmbuild to also build cross
gcc
On 09/01/10 16:29, Somebody in the thread at some point said:
Hi -
> What are the use cases for the cross-compilers?
>
> If these are to compliment the Fedora secondary archs, then compiling
> kernels is probably the main use of cross-compilers -- for example, on
> ARM, devices often need a custo
On 03/13/10 11:46, Somebody in the thread at some point said:
> On 03/13/2010 11:52 AM, Ville-Pekka Vainio wrote:
>> pe, 2010-03-12 kello 15:20 -0800, Jesse Keating kirjoitti:
>
>> As Fedora is the distribution I'm most familiar with, I've also
>> installed it on some of my family members' systems
On 03/12/10 18:06, Somebody in the thread at some point said:
>>> In this context, if you're writing homegrown apps, you're a
>>> "developer", not a "user", so the above sentence obviously does not
>>> apply. Instead, my original point does (you'll be compiling your
>>> own software very often any
On 03/12/10 15:11, Somebody in the thread at some point said:
> Andy Green wrote:
>
>> On 03/12/10 00:45, Somebody in the thread at some point said:
>>
>>> If you are the user, then you should not be compiling software. :-) You
>>> should be using some repositor
On 03/12/10 14:01, Somebody in the thread at some point said:
> On Fri, Mar 12, 2010 at 12:23:58PM +0000, Andy Green wrote:
>
>> However I agree this isn't a real issue, the packages with the homegrown
>> apps should choke the yum update because they see the lib versions the
On 03/12/10 00:45, Somebody in the thread at some point said:
> If you are the user, then you should not be compiling software. :-) You
> should be using some repository and that repository is responsible for
> rebuilding the package.
I tend to agree with what you have been writing but this seems
On 08/14/2009 10:20 AM, Somebody in the thread at some point said:
> It's been pretty common since forever for various scriptlets to redirect
> output of stderr/stdout to /dev/null, so I think it'd be a bit of an
> ugly mess if there was a mandatory packaging rule you couldn't use at
> least /dev/
13 matches
Mail list logo
