On Tue, Aug 20, 2002 at 12:00:55PM -0700, Ian Masterson wrote: > Hardlinks work just fine, although being able to use symlinks instead > would be very nice. In fact, hard links _HAVE_ to work, since there is no distinction between original and link. The only scenario I can think of where hard links don't work but symlinks do is if a program removes a file and creates a new file of the same name (intending to replace the original). -Michael > > -Ian > > On 20 Aug 2002, seth vidal wrote: > > > On Tue, 2002-08-20 at 14:51, Andrew Schretter wrote: > > > Seth, > > > You mentioned that I could use a directory containing links to RPMS > > > and run yum-arch on it to create the header info for that directory. > > > > > > However, when I tried it, I got : > > > > > > No rpms to look at. Exiting. > > > > > > The same yum-arch works fine on the directory actually containing all > > > the RPMS. I was just testing to see if I could create a subset of those > > > RPMS in another directory via links. > > > > > > > > > whoops - misremembered: > > > > from serverStuff.py getfilelist() > > > > # get all the files matching the 3 letter extension that is ext in path, > > recursively > > # store them in append them to list > > # return list > > # ignore symlinks > > > > yah - and I think I remember why - b/c the path might be outside of that > > basedir - and the basedir is needed to reach the files if symlink > > following is not supported in the http or ftp server. > > > > > > a problem worth looking into a bit more. If you make them hardlinks what > > happens? > > > > -sv > > > > > > > > > > > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum -- Michael Stenner Office Phone: 919-660-2513 Duke University, Dept. of Physics mstenner@xxxxxxxxxxxx Box 90305, Durham N.C. 27708-0305
