As part of the F21 "Modular Kernel Packaging for Cloud" Feature,
I've committed and pushed the kernel packaging split up into
kernel-core and kernel-drivers subpackages. For those of you running
rawhide, this really shouldn't be a major impact at all. When you do
a yum update, you will see "kernel", "kernel-core", and
"kernel-drivers" packages being installed. The end result should be
in line with today's rawhide kernels.
Note: Unless you're using a typical VM or Cloud image, don't uninstall
the kernel or kernel-drivers packages. The machine may boot with just
kernel-core, but it will lack drivers for a significant portion of
bare-metal hardware without kernel-drivers installed.
Despite best efforts in testing, it's always possible a bug or two
snuck through. In the event that you do have an issue with this,
please file a bug against the kernel package.
On Sat, 2014-04-19 at 15:33 +0000, updates(a)fedoraproject.org wrote:
> The following comment has been added to the mesa-10.1-6.20140305.fc20,pure-0.58-3.fc20,python-llvmpy-0.12.4-1.fc20,pocl-0.9-4.fc20.1,OpenGTL-0.9.18-9.fc20,gedit-code-assistance-0.2.0-5.fc20,gambas3-3.5.3-1.fc20.1,dragonegg-3.4-0.3.rc0.fc20,llvm-3.4-6.fc20 update:
> bodhi - 2014-04-19 15:33:49 (karma: 0)
> This update has been submitted for stable by ignatenkobrain.
Can you please not just decide to push things to updates that I'd
already promised fesco I'd leave in testing for a long soak period?
That be great.
= Proposed Self Contained Change: The Shogun Machine Learning Toolbox =
Change owner(s): Björn Esser <besser82(a)fedoraproject.org>
SHOGUN is a large Scale Machine Learning Toolbox, being implemented in C++ and
offering interfaces to C#, Java, Lua, Octave, Perl, Python, R and Ruby.
== Detailed Description ==
* Homepage: The SHOGUN Machine Learning Toolbox 
* SCM-repo: on GitHub 
* Documentation: is available here 
* further Information: on Wikipedia 
The machine learning toolbox's focus is on large scale kernel methods and
especially on Support Vector Machines (SVM). It provides a generic SVM object
interfacing to several different SVM implementations, among them the state of
the art LibSVM. Each of the SVMs can be combined with a variety of kernels.
The toolbox not only provides efficient implementations of the most common
kernels, like the Linear, Polynomial, Gaussian and Sigmoid Kernel but also
comes with a number of recent string kernels as e.g. the Locality Improved,
Fischer, TOP, Spectrum, Weighted Degree Kernel (with shifts). For the latter
the efficient LINADD optimizations are implemented. Also SHOGUN offers the
freedom of working with custom pre-computed kernels. One of its key features
is the "combined kernel" which can be constructed by a weighted linear
combination of a number of sub-kernels, each of which not necessarily working
on the same domain. An optimal sub-kernel weighting can be learned using
Multiple Kernel Learning. Currently SVM 2-class classification and regression
problems can be dealt with. However SHOGUN also implements a number of linear
methods like Linear Discriminant Analysis (LDA), Linear Programming Machine
(LPM), (Kernel) Perceptrons and features algorithms to train hidden Markov-
models. The input feature-objects can be dense, sparse or strings and of type
int/short/double/char and can be converted into different feature types.
Chains of "pre-processors" (e.g. subtracting the mean) can be attached to each
feature object allowing for on-the-fly pre-processing.
== Scope ==
* Proposal owners: Create the rpm-spec and file a review bug. Have the package
build after review was granted.
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
devel-announce mailing list
= Proposed System Wide Change: Default Local DNS Resolver =
Change owner(s): P J P <pjp(a)fedoraproject.org>, Pavel Šimerda
<pavlix(a)pavlix.net>, Tomas Hozza <thozza(a)redhat.com>
To install a local DNS resolver trusted for the DNSSEC validation running on
127.0.0.1:53. This must be the only name server entry in /etc/resolv.conf.
The automatic name server entries received via dhcp/vpn/wireless
configurations should be stored separately, as transitory name servers to be
used by the trusted local resolver. In all cases, DNSSEC validation will be
This change was submitted after the Submission deadline.
== Detailed Description ==
There are growing instances of discussions and debates about the need for a
trusted DNSSEC validating local resolver running on 127.0.0.1:53. There are
multiple reasons for having such a resolver, importantly security & usability.
Security & protection of user's privacy becomes paramount with the backdrop of
the increasingly snooping governments and service providers world wide.
People use Fedora on portable/mobile devices which are connected to diverse
networks as and when required. The automatic DNS configurations provided by
these networks are never trustworthy for DNSSEC validation. As currently there
is no way to establish such trust.
Apart from trust, these name servers are often known to be flaky and
unreliable. Which only adds to the overall bad and at times even frustrating
user experience. In such a situation, having a trusted local DNS resolver not
only makes sense but is in fact badly needed. It has become a need of the
hour. (See: , , )
Going forward, as DNSSEC and IPv6 networks become more and more ubiquitous,
having a trusted local DNS resolver will not only be imperative but be
unavoidable. Because it will perform the most important operation of
establishing trust between two parties.
All DNS literature strongly recommends it. And amongst all discussions and
debates about issues involved in establishing such trust, it is unanimously
agreed upon and accepted that having a trusted local DNS resolver is the best
solution possible. It'll simplify and facilitate lot of other design decisions
and application development in future. (See: , , )
* Petr Spacek
* Paul Wouters
* Simo Sorce
* Dmitri Pal
* Carlos O'Donell
== Scope ==
* Proposal owners: Proposal owners shall have to
** define the syntax and semantics for new configuration parameters/files.
** persuade and coordinate with the other package owners to incorporate new
changes/workflow in their applications.
* Other developers: (especially NetworkManager and the likes)
** would have to implement the new features/workflow for their applications
adhering to the new configurations and assuming the availability of the
'''trusted''' local DNS resolver.
** NetworkManager already has features & capability to support local DNS
resolvers. Though few details are still under development, but are expected to
realize in near future. Please see 
* Release engineering:
** would have to ensure that trusted local DNS resolver is available
throughout the installation stage and the same is installed on all
installations including LiveCDs etc.
* Policies and guidelines:
** the chosen trusted DNS resolver package(ex dnsmasq or dnssec-trigger etc.)
would have to ensure that their DNS resolver starts at boot time and works out
of the box without any user intervention.
** NetworkManager and others would have to be told to not tamper with the
local nameserver entries in '/etc/resolv.conf' and save the dynamic nameserver
entries in a separate configuration file.
devel-announce mailing list
looks like https://fedoraproject.org/wiki/Features/DracutHostOnly over
the long has the opposite effect and more and more modules are included
in the hostonly-initrd because regressions right and left
people who used hostonly before the feature on machines where
it is fine where down below 5 MB, with F19 around 6 MB and
on a completly stripped down F21/Rahide we reahc 9 MB
5,9M 2014-04-27 11:47 initramfs-3.13.11-100.fc19.x86_64.img
8,9M 2014-04-30 21:47 initramfs-3.15.0-0.rc3.git1.10.fc21.x86_64.img
finally nobody won and the ones with stripped down systems lost
-----BEGIN PGP SIGNED MESSAGE-----
Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 17:00UTC in #fedora-meeting on irc.freenode.net.
To convert UTC to your local time, take a look at
date -d '2014-04-30 17:00 UTC'
Links to all tickets below can be found at:
= Followups =
#topic #1221 Product working group activity reports
#topic #1244 F21 System Wide Change: cron to systemd time units -
#topic #1250 F21 Self Contained Changes
#topic #1291 F21 System Wide Change: BerkeleyDB 6 -
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
-----END PGP SIGNATURE-----