Minimum Install requires discs 1 and ___3___ !!!!!!!
Call it bad luck... Can something be done about this, or at least made
widely clear on the final release announcement?
I'm now waiting for disc 3 of fc2t3 and got disc 2 for nothing :)
Let's say that hypothetically speaking I were to install some packages
from http://rpm.livna.org and then rebuild the gstreamer-plugins src.rpm
except using a source tarball from gnome instead of the red hat one with
And lets this hypothetically resulted in the following plugins:
but after installing and running gst-register, when trying to play a
shoutcast, rhythmbox still pops up a dialog stating:
"There is no element present to handle the stream's mime type
Where would I tell it that it has new gstreamer plugins it can use?
I'm tempted to just build rhythmbox from source (rebuild the rpm) but I
don't think that is the issue, I've had previous installs of rhythmbox
that did simply pick up on the fact that I rebuilt gst-plugins and new
capabilities were there.
Cheap Linux CD's - http://mpeters.us/linux/
It appears as of the 2179 version of the Fedora Core 1 kernel, that the
kernel low-latency patch has been removed. Any ideas as to why? Is
there a replacement for this patch incorporated into the 2179+ releases?
This patch is very important to systems trying to process streaming
data, and I am trying to determine why it has apparently been removed.
Has any work been done to document Anaconda's deep-dark-secrets yet?
My current project:
Given a copy of all the RPMS/SRPMS, and having the anaconda-runtime
package installed, I'd like to build an installable tree using a custom
kernel (for my funky x64_64 laptop) and optionally create CD and DVD
This is probably a stupid question, but anyway...
If I understood correctly, an upgrade from one distro to the next (say, FC1
to FC2) will never be as good with apt or yum as it is with anaconda.
Anaconda knows much more about the process, which packages need to be
removed, which packages need to be installed, and what needs to be done to
the system (ie all the SELinux labelling stuff)
But online upgrade is really extremely useful, especially for a distro with
a 6 months release cycle (I've recently heard Debian users boast --again--
Well, if anaconda can handle the process when it is run from the CDRom,
would it be possible to make it do its job from a running system ? I
suppose it is not possible right now, but would it be possible to just
download the isos, mount them on a loopback device, and launch anaconda
from there ? If needed, it could require a reboot at the end of the
Are there operations which need to be done on an unmounted filesystem ? If
yes, they could be done by a "very-first-start" program after anaconda's
work, or even something loaded in RAM.
I have no idea whether this is possible or not, because I don't know
anaconda's design. If this is the most stupid proposition you've ever
heard, please ignore this. If it is technically impossible, please tell me.
If there are better solutions to upgrade an online system, please tell me
too. But if it is possible (for FC4 or even FC3), this would really rock.
Thanks for your attention.
http://gauret.free.fr ~~~~ Jabber : gauret(a)amessage.info
"Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect." -- Linus Torvalds
In general, what is the frequency that the fedora/redhat kernel folks
grab updates from external source trees? I am mostly interested in how
often it is done for JFFS2, but there are other trees (such as linuxppc)
where development is done outside of the kernel.org tree that has a
value to end users.
Some trees don't push to Linus very often (like JFFS2) for various
reasons, so are users getting whatever is in the vanilla kernels? Or,
do the fedora/redhat people do their own patches?
I am not expecting a schedule or some set update frequency. I am mostly
just asking to see if it is done at all, and if so get a rough estimate
as to how often.
I just submitted three packages -- waproamd, ifplugd, and libdaemon, to
bugzilla.fedora.us. They are bugs # 1534, 1535, and 1536.
Excuse the needless email, but I'm excited about it!
Franklin W. Olin College of Engineering
A few weeks back someone posted some scripts to make a cvs repo of
mostly-current stuff from rawhide. Could you re-point me at those
scripts. I'd like to do some tests to try and do this - to see how much
space it eats up, etc.
Just curious about it. Thanks.