This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: RE: As86 missing from RHL 6.1? From: "Steven W. Orr" <steveo@world.std.com> Date: Sun, 28 Nov 1999 21:16:26 -0500 (EST) =>> On Sun, 28 Nov 1999, Juha Saarinen wrote: =>> =>> =>Noticed that the as86 assembler isn't there with RHL6.1 when I tried to =>> =>compile the 2.2.13 source. It's included with the 6.0 RPMs but =>> not the 6.1. =>> =>Is this intentional? =>> From: Steven W. Orr [mailto:steveo@world.std.com] =>> Sent: Sunday, 28 November 1999 18:40 =>> To: Juha Saarinen =>> Cc: Redhat-List@Redhat. Com =>> Subject: Re: As86 missing from RHL 6.1? =>> =>> =>> Give a man fish and he'll smell funny. Teach him how to fish and =>> he'll teach =>> others to smell funny. =>> =>> Mount your install cd and go to the RPMS directory. =>> =>> for i in *.rpm =>> do =>> echo $i =>> rpm -qpl $i | grep as86 =>> done | less =>> On Sun, 28 Nov 1999, Juha Saarinen wrote: =>Hmmm... thanks, but I'm not sure if that scriptlet works quite as you =>intended. It lists all the files in the RPMS directory. It did exactly what I intended. It lists every rpm file that it processes, but it prints the grep output after the rpm file that it works on so you know which rpm the found file came from. Another variant would be something like: for i in *.rpm do rpm -qpl $i | grep -l as86 done | less === Subject: Re: A couple of source code questions From: Hal Burgiss <hburgiss@bellsouth.net> Date: Fri, 10 Dec 1999 18:15:48 -0500 On Sat, Dec 11, 1999 at 06:53:34AM +0800, John Summerfield wrote: > At this point, I will leave Red Hat to explain where the current > documentation for RPM may be found; the book at www.rpm.org is > seriously out of date; RPM 3 has significant changes that are not > reflected in any documentation I've been able to find. There is an updated HOWTO: http://www.rpm.org/RPM-HOWTO/index.html === Subject: Re: directory permission From: Jan Carlson <janc@iname.com> Date: Sun, 19 Sep 1999 17:48:02 +0000 "Gatesway Online, Inc." wrote: > > hi, can anyone tell me what should > be the directory permission of > /var/spool/mail ??? rpm can tell you that, for anything that was installed from an rpm: rpm -qlvf /var/spool/mail | grep /var/spool/mail === Subject: Re: Fed up persons guide to glibc? From: Gordon Messmer <yinyang@eburg.com> Date: Fri, 10 Dec 1999 10:27:45 -0800 Timothy Reaves wrote: > issues. Some RPM's un-install (or screw up) some compat glibc stuff, > other apps need version x and others version y. > If anyone could point me in the correct direction I would appreciate > it. Often, the easiest solution is simply to get the src.rpm instead of the binary, and rpm --rebuild it. === Subject: Re: A couple of source code questions From: Alan Cox <alan@lxorguk.ukuu.org.uk> Date: Fri, 10 Dec 1999 18:03:15 +0000 (GMT) > My question is, how would I extract the source code and patches from > the Apache RPM supplied on the Redhat cd's into a directory like > /usr/src/apache-1.3.9? I was able to install stock apache source > code, no problem, but I am coming up short trying to find the Redhat > patches. > > Sorry to sound so ignorant. You don't. The RPM stuff is more than just a package archive. rpm --install apache-1.3.9.src.rpm will unpack the specification file, some patches and some tar files. Then you can use rpm -ba to build it all, and various other rpm commands to do stuff like partial builds. The spec file is basically the build command list, a list of the archives and the patches. The idea of this is that you can easily swap the base package (eg when apache 1.3.10 appears), or add patch files to the list and rebuild a new RPM. There is a book 'Maximum RPM' which I believe is also online somewhere on www.rpm.org for download. === Subject: RE: upgrading with rpm From: Mike Owen <Mike.Owen@aptissoftware.com> Date: Tue, 21 Dec 1999 09:52:06 -0600 > I have read the rpm docs, and can't seem to find the option I need... > > I want to have a directory of all the Red Hat updates, and > issue a single > command to have rpm upgrade *only* those rpm's which are already > installed. ( I personally think -U should do this instead of > defaulting to use rpm -Fvh * to update (Freshen) only installed packages. === Subject: Re: upgrading with rpm From: Bernhard Rosenkraenzer <bero@redhat.de> Date: Tue, 21 Dec 1999 17:17:05 +0100 (CET) On Tue, 21 Dec 1999, Randy Carpenter wrote: > > Wouldn't rpm -Uvh * be enough? > > No. -U will install a package even if it isn't already installed. rpm -Fvh * should do, though. The only problem with rpm -F is that it can't deal with packages that obsolete others (e.g. if you try upgrading 6.1 to rawhide, rpm -F won't install gcc over egcs). === Subject: Re: Re: upgrading with rpm From: rpjday@mindspring.com Date: Tue, 21 Dec 1999 11:33:27 -0500 Bernhard Rosenkraenzer <bero@redhat.de> wrote: > > On Tue, 21 Dec 1999, Randy Carpenter wrote: > > > > Wouldn't rpm -Uvh * be enough? > > > > No. -U will install a package even if it isn't already installed. > > rpm -Fvh * should do, though. The only problem with rpm -F is that it > can't deal with packages that obsolete others (e.g. if you try upgrading > 6.1 to rawhide, rpm -F won't install gcc over egcs). another caution with freshen is that newer versions of some packages have new dependencies they never had before. i recall doing a freshen with a set of new RPMS, and having one of the freshens choke since it depended on (from memory) libpopt.a, or something like that, a dependency the older version of the package never had. and i had never installed libpopt.a. other than fairly obvious cautions like these, does freshen actually work, since i've heard ugly stories about it from more than one source. thanks. ===