I noticed something odd..
(18:25:35:davej@gelk:F-9)$ time make clog
make: `clog' is up to date.
0.22user 0.11system 0:00.33elapsed 98%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+52803minor)pagefaults 0swaps
(18:25:40:davej@gelk:F-9)$ cd ../devel/
(18:25:43:davej@gelk:devel)$ time make clog
make: `clog' is up to date.
0.25user 0.15system 0:02.82elapsed 14%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+76947minor)pagefaults 0swaps
The times are consistent across multiple runs. Same command in devel takes
a lot longer. The spec file differences are irrelevant.
(tested by copying the specfile from f9 to devel)
The clog target is just a simple sed & tee, so I'm confused as to why
it takes longer.
I am quite familiar with connecting arbitrarily complex audio systems. I
have been trying to understand how the sections of the linux audio plug
For sources I have a microphone, audio and video CDs, and MP3s. For
output I have an audio jack, a bluetooth transmitter.
Is there a mux (or preamp equivalent) that allows one to select and
input and output path? Perhaps also set the gain, balance, base, treble
Is there a document that describes haw to turn on, and then access the
various input and and output channels.
Sorry if this is to basic a question. All of my searches have found
pieces, but I am confident there must be an top down design document.
I have read some of the tickets in bugzilla about it, but things seem to
have stalled. What is the status of getting the latest zoneminder into
At one time I read that there were some pieces that were missing, but I
think the last bugzilla entry that I read said that they were submitted
I'm looking for another reviewer for my Coq package - the one
currently assigned (Richard W. M. Jones) is away for a few weeks and
won't be able to look at it further until he returns. I've fixed the
issues cited by him since he looked at the package, as documented on
the bugzilla page:
I still also need a sponsor, as this is my first Fedora package.
For those interested - the description:
Coq is a formal proof management system. It allows for the development
of theorems through first order logic that are mechanically checked by
the machine. Sets of definitions and theorems can be saved as compiled
modules and loaded into the system. Coq is based off of OCaml.
I just read http://www.linuxformat.co.uk/static/suse11.html where is
mentions that OpenSuSe 11 went with a different compression algorithm
for their rpms (LZMA instead of bz2) and have a few questions:
1) While every distro seems to be coming together on a package
management GUI (PackageKit), does this represent a splintering of
package formats? or is rpm compression algorithm agnostic? Is there
any hope that the various rpm development will start pulling in the
2) LZMA appears to have some good characteristics for installation
rpms (tighter compression, 50% decompression time ... at least as
implemented by 7zip ref:
http://www.maximumcompression.com/data/summary_mf4.php ). Is Fedora
planing to follow this switch (or has it already and not advertised it
as a prominent feature) or are there other considerations preventing
that (patent issues?, not suitable for delta rpms?, 200% compression
We're doing something a little special for the next rawhide kernel.
There is an ongoing bug regarding gcc and compiling the kernel, which
leads to ext3 failures.
In order to have a working kernel, but not make gcc go backwards by
untagging it while the gcc folks are working out a fix, I've created a
special buildroot to put the old gcc back into service so that we can
build the kernel and move beyond the ext3 issues. This will be a short
lived buildroot, only used by the kernel, so that we have something
working for the next few days (somewhat critical given FUDCon).
This is not something we normally do, but I wanted to announce it up
front so that everybody knows whats going on.
Fedora -- Freedom² is a feature!
We've changed /bin/mail command source to the new upstream in rawhide
for more info).
The new source was already in Fedora, under an alternative name of
"nail". IOW, we currently have /bin/mail provided by mailx-8.1.1, and
/usr/bin/nail, provided by nail-12.3. Since nail-12.3 supersedes all the
features of the old undeveloped mailx-8.1.1 (and has the same upstream
name of "mailx" now), we've decised to switch to it for /bin/mail as well.
As a result, I've copied the "devel" branch of the "nail" package to the
"devel" branch of the "mailx" package (with some adaptation needed).
The question is: What changelog to preserve?
Both packages have their own history. What changelog preserve in the new
mailx in rawhide -- the old entries from mailx-8.x, the new entries from
nail-12.3, or something else?