I am seriously considering developing for the Fedora Linux Operating System. Also, I have interest in participating in Google Summer of Code 2013 under your organisation.
Also, I have been using Fedora Operating system since 2 Years. So, Please Guide me in the Right Direction and tell me what All I need to learn for the purpose.
UIET, PU, Chandigarh.
Digium released the first release candidate for Asterisk 11 yesterday, with
the final release due hopefully sometime this month. I'm therefore going
to be updating the Asterisk package in Fedora 18 to the release candidate.
Fedora 17 is going to stick with the 10.X series, Fedora 16 is sticking
with the 1.8.X series.
EPEL 6 will stick with the 1.8.X series for the time being as Digium
designates is as a long term support release. Digium plans on ending
support for 1.8.X in 2015 while RHEL 6 support from Red Hat will continue
until 2020 so at some point in 2015 Asterisk in EPEL 6 will need to
switch to a newer version, probably version 13 if Digium's plans hold.
Greetings and salutations!
It is time once again to choose the name for the next release of Fedora.
Suggestions for names will be accepted beginning RIGHT THIS SECOND
(October 9, 2012), and ending promptly at the end of the day on October
16, 2012 (23:59:59 UTC). So mooooooove on over, and help to pick out an
udderly fabulous name for the next release.
The awesome fine print:
You *must* follow the instructions and guidelines at the page listed
above if you want your name to be considered. For instance, there must
be an "is-a" link between the name "Spherical Cow" (from Fedora 18) and
the name you suggest. That link must be different than previous links
for Fedora release names. Names of living people and well-known
trademarks will likely be rejected as well. (Apologies to those wishing
to make links between spherical cows having spots, and Tom Callaway.)
You can also find full schedule details for the release naming process
on the above page. For those of you interested in reviewing the history
of Fedora release names, there is an appropriately named wiki page for
doing so: http://fedoraproject.org/wiki/History_of_Fedora_release_names
I fully expect that, as always, we will have a delightful (and
occasionally wacky) assortment of names to choose from - I look forward
to seeing your suggestions!
devel-announce mailing list
On 10/09/2012 08:47 AM, H. Peter Anvin wrote:
> Yes, I can travel back in time and fix someone else's badly installed
> server that they are asking me to fix or do forensic analysis of.
> Brilliant idea.
Who does not want to travel back in time? =)
On 10/09/2012 08:28 AM, H. Peter Anvin wrote:
> The problem is that they generally get to clean up a system long*after*
> is has been installed by someone else, crashed, and needs to be recovered.
Here you are fighting about libmicrohttpd ( 48KB ) and qrencode-libs (
46.3KB ) while we have rsyslog ( 601KB ) which is totally unnecessary
and should not be a part of the default minimal install since we already
have the journal, an logging solution that comes with systemd and fits
embedded home admins servers and the desktop.
Again there is still nothing preventing them from installing it via .ks
or afterwards if they want need all the bells and whistle that rsyslog
or syslog-ng provide over the journal.
On 10/09/2012 07:50 AM, H. Peter Anvin wrote:
> On 10/09/2012 03:10 PM, "Jóhann B. Guðmundsson" wrote:
>> On 10/09/2012 04:34 AM, Bill Nottingham wrote:
>> Remind me again of the reason why we are still shipping rsyslog by
>> default now that we have the journal?
> An undocumented, acknowledged-experimental binary data format for logs?
> Sysadmins will kill you.
So the so called sysadmin which capable of killing me is not capable of
either adding it manually to his .ks file or at install it afterwards if
he cant learn or like as you put it the "undocumented,
acknowledged-experimental binary data format for logs".
Kudos to those sysadmins...
In order to reduce the size of the F18 Xfce spin, I wanted to edit comps
- but decided to not do so until I fully understand what is going on. I
seem to have missed a lot since since last our discussion at Blacksburg,
so have a lot of questions.
Here we go:
1. How can a package maintainer define a default, but not mandatory
package? Example: The Xfce SIG decided to no longer install
xfce4-icon-theme by default. It just takes space and we don't
use it. Nevertheless we want to enable users to install it
easily. How would we do that? Define an extra group with only
xfce4-icon-theme and make it an option of the Xfce environment?
2. Even if I cannot do it in anacoda any longer, how would I do it
in PackageKit? How can I make something show up in a group there
without making it mandatory?
3. How do the new groups translate into PackageKit groups? Will all
options be listed in the side pane of gpk-applications? Will
they dynamically change? Will all packages of a group be
4. How to define conditionals?
5. Is there more documentation than just