I have the yarrow's iso files on my HD in a RH9 system. Let's say I want
to upgrade selected packages using an "apt-get install" pointing to my
iso-mounted files, how do I do it?
i.e I mount the iso into some /mnt/yarrow1, /mnt/yarrow 2 etc..
Then what is the complete procedure to make my apt look into my own HD to
upgrade packages. Can anybody redirect me to the correct
resource or some literature hanging on the web? Thanks.
Assume also that I do not wish to burn CDs! I do not want to use
With kind regards,
Singapore Synchrotron Light Source (SSLS)
5 Research Link,
Email: slsbdfc at nus dot edu dot sg \or\
didierbe at sps dot nus dot edu dot sg
we use mock for local package build, but it's very slow. now we install
a new host just for mock with 8core, ram disks etc. it seems it still
slow. first of all most of the time mock use only one 1 core of the cpu.
is there any way to speed up different part of the mock build process?
thanks in advance.
ps. anyway is there any better place to discuss it?
Levente "Si vis pacem para bellum!"
Nowadays the jack project has two branches - old jack (1) branch with
version 0.116.2 and new one called jack2 version 1.9.3.
I'd like to gather opinions and suggestions about applying new version for F13.
Please, share your thoughts!
With Best Regards,
early in the F13 cycle, we enabled the bytecode interpreter in our
freetype package, since the patents on that have expired last fall.
Unfortunately, it turned out that many free fonts don't actually benefit
from this, and actually look worse with the bci. The reason for that is
that without the bci, freetype uses its autohinter on all fonts, but
with the bci turned on, it only applies hints to fonts which have them,
and leaves other fonts alone.
Behdad investigated the situation, and we have a plan to fix this, but
doing it properly requires enhancements in multiple places (freetype,
fontconfig, pango), and will not be ready in time for F13.
Therefore, we decided to turn the bci off again until the necessary
changes are in place to use it only on fonts which benefit from it. This
change went into freetype-2.3.11-3.fc13.
If your fonts look subtly different tomorrow, this is why...
I was trying to install i686 variant of F-13 to an Alix board (2D13 with
Geode LX) and got into troubles. The kernel boots fine, but when it
should start initramfs the kernel panics. Everything works well when
using complete F-12 environment and when using F-12 kernel+initramfs
with F-13 rootfs the initramfs stuff runs well, but when I try to
manually chroot into the F-13 from the dracut shell I get an "Invalid
instruction" exception. I though last change in x86 CPU support was in
F-12 (http://fedoraproject.org/wiki/Features/F12X86Support) and it
explicitly talks about Geode LX as still supported. So the question is
whether F-13 should still work on Geode LX?
I'll plan update ImageMagick now -
ABI change follow.
And according it I have some questions. New minor version of IM made
around 1-2 times in week. What policy I should use to handle it? Have it
worth update it in rawhide each time when new version arrived (I hope
no)? For stable releases I though in action
http://fedoraproject.org/wiki/Package_update_guidelines and shortly I
should submit updates only for bugfixes.
Must I notify someone about coming update? How? Is it enough write here?
With best wishes, Pavel Alexeev aka Pahan-Hubbitus.
Has there been any plans to support running custom post-up scripts for each interface, after "ifup <interface>" ?
Debian allows you to specify:
iface eth0 inet static
I'm looking for something similar for rhel/fedora.
Maybe something like POST_UP="/path/script" in /etc/sysconfig/network-scripts/ifcfg-int