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
Can yum be setted to delete files from /var/cache/yum*** after upgrading/updateing ?
I dig the man but probablyI miss something or is not possible ?
Life in itself has no meaning.
Life is an opportunity to create meaning.
\|/ ____ \|/
"@'/ .. \`@"
/_| \__/ |_\
I have been having some trouble with gconfd-2 (currently using GConf2-2.4.0
from RawHide PPC) for quite some time. I tried to get some discussion going
on Red Hat's Bugzilla quite a while ago but nothing really came of it. I'd
be willing to work on a patch, but I'd like to come to consensus on the
technique we should use to fix the problem. I thought perhaps I would try
The gconfd-2 daemon is run by many GNOME applications to manage
configurations. Gconfd-2 remains running for some time after the application
which used it quits. This allows other applications to use gconfd-2 without
having to start and stop the daemon too much. This is a good idea.
The problem comes when a system tries to unmount a user's home directory when
the user logs out. For example, pam_mount unmounts an encrypted home
directory then I log out of my system. Other people use NFS or other means
to mount home directories.
Gconfd-2 continues to run even when a user logs out. This causes the
unmounting of the user's home directory to fail because gconfd-2 keeps the
following files open:
In addition, when using GNOME 2.4, there are four new programs that seem to
hang around unwelcome for a second after logging out (at least they are still
around when PAM session closing code is run). This is partially documented
in bug #106826. The four programs are:
bonobo-activation-server (home direcotry remains open as CWD?)
gnome-settings-daemon (home direcotry remains open as CWD?)
xscreensaver -nosplash (home direcotry remains open as CWD?)
mapping-daemon (home direcotry remains open as CWD?)
Red Hat Bugzilla bugs #67605, #75895 and #106826 comment more on this
Some time ago I already asked for a possibility to setup the network
with additional IPs assigned to an eth device without using aliased
devices. As the network scripts now for a long period uses iproute2 to
setup devices instead of the older ifconfig it would be easier to
address further IPs to a device than by aliasing. In addition iptables
can't handle aliased device names.
Did anyone made already efforts to develop scripts to handle this issue?
Otherwise I would start by my own to integrate shell scripts into the
Redhat/Fedora network scripts to assign additional IPs - as a list or as
just a bunch of IPs - to an existing eth device.
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416 14CD E197 6E88 ED69 5653
Ximian just released a new version of Red-Carpet. Would it be an idea
to make RC channels of fedora.us(and Fedora for that matter) ?
RedCarpet does in my opinion make software installation a no brainer
for most people.
Vennlig hilsen/Best Regards
Nils Olav Selåsdal
w w w . u t e l s y s t e m s . c o m
I have seen several posts in the past where someone asks about building
Fedora ISO images. I have yet to see a response.
Surely _someone_ must know how this is done. Why is there never a response?
Is this knowledge a 'secret sauce' that nobody wishes to share?
The new MSN 8: advanced junk mail protection and 2 months FREE*
the Fedora Project will need a buildsystem which features:
it MUST be impossible to kill or ptrace processes of other buildroots
or of the system. Hiding of foreign processes SHOULD be provided.
Direct hardware access through /dev/* entries or modification of
kernel parameters through /proc MUST be impossible. Forbidding the
creation of such special files is one way to reach it, access
restriction another one.
it MUST be impossible for a process in a buildroot to have any kind
of access on objects of the systems (e.g. ssh-keys), or write-access
on other buildroots.
each build MUST happen in an environment which can not be influenced
by previous builds in this environment. This includes both
filesystem-objects, and processes.
excessive resource-usage (memory, diskspace,...) of a build SHOULD
be prevented. Usage of certain resources (e.g. network) MUST be
the buildsystem SHOULD should have only a small or non-existing
impact on the performance.
building of common packages MUST succeed. This requires certain /dev
entries, and a mounted /proc filesystem at least.
the system SHOULD assist the buildmaster and automate the most
tasks, so that the spent time will be reduced to a minimum.
The reasons for these items and how they are solved in the current
fedora.us buildsystem are described in
[PDF, 204 KiB]
The described buildsystem is in use for a short time only, but it
seems to be secure and to work well (it was used in the rh9* -> fc1
mass-rebuild for the most packages). There were some cases which
needed manual intervention (e.g. manual disttags), but these were
A core part is a vserver capable kernel. Unfortunately, it is not
ported to the kernels which are shipped with Fedora yet, and chances are
only low that it comes into the official 2.6 kernel.
Since Red Hat wants a selfhosting buildsystem, alternatives must be
investigated. SELinux offers interesting features, but it is new and
there are lot of open questions:
1. SELinux can protect foreign processes. But is it possible to hide
them in /proc also?
2. Is chroot(2) implemented in a safe manner? Or, can parent directories
of build-roots be protected with SELinux policies? Is a safe chroot(2)
required at all?
3. What is the performance impact of the policy checking?
4. How can disk/memory usage restricted with SELinux? Would CKRM be an
5. Can special mount-operations (e.g. /proc filesystem) be allowed by
the policy, or does this require userspace helper also?
6. Setup of an SELinux policy seems to be very complicated. How possible
are holes in a setup?
It would be nice when an SELinux expert could take a look at this
questions and how it can be used in the buildsystem.
UML might be another option, but its status (chances to come into
official 2.6) and performance impact is not clear.
Due to popular demand on #fedora-devel, I merged the latest libata code to
the FC1 kernel. This is basically identical to 2.4.22-bk53-libata1.patch.gz,
except for two PCI id's added to sata_promise (0x3376 and 0x3378) and
¤t->sigmask_lock -> ¤t->sighand->siglock in libata-core.c.
Pre-built RPMS + the patches I used (linux-2.4.22-libata.patch
and linux-2.4.22-intel-esb-drivers.patch) can be found from
http://www.ee.oulu.fi/~pp/fc1-libata (sorry, no yum support :-) )
Please test it out and if it works like it should, I'll file a RFE in
bugzilla to get this merged.
- Did I break anything? (the amount of changes in header files I merged from
2.4.22-bk to fc1 like scsi.h were a bit worrying...) Promise 376 + athlon
works ok, and it did compile, so I decided to ship it :-)
- Is the Promise 378 PCI id 0x3378 and does the code work on one?
- driver disk or boot.iso that would let people install FC1 on SATA-only
I'm trying to setup an yum repo for AbiWord at
I know I have some directory structure tactical problems, but I'll solve
them when I'm on a faster network, so let's not talk about them right
now, since I'm running into some weird problem, I think totally
unrelated to the dirs.
[root@roque root]# yum install abiword-plugins-impexp
Gathering header information file(s) from server(s)
Server: AbiWord cvsbuilds and releases for Fedora Core 1 - i386
Server: Fedora Core 1 - i386 - Base
Server: Fedora Core 1 - i386 - Released Updates
Finding updated packages
Downloading needed headers
.....identical dependency loop exceeded
package abiword needs libwpd-1.so.2 (not provided)
Now, I have zero matches of libwpd-1.so.2 on the rpms I provide at
savannah. Where's that comming from? Can someone help me?
+ No matter how much you do, you never do enough -- unknown
+ Whatever you do will be insignificant,
| but it is very important that you do it -- Gandhi
+ So let's do it...?
Please AVOID sending me WORD, EXCEL or POWERPOINT attachments.