rpm(8) was difficult for me to use for learning RPM.
This might help for your problem:
# rpm -i --force prog.rpm
___
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
On Mon, 2002-12-16 at 18:24, Joseph D. Wagner wrote:
>
> Do you suggest I re-extract the files from the tar archive and start over?
By the error message you sent, it looks to me that you do not have
software installed that is needed to run xconfig. Try
make menuconfig
or
make config
If menuc
On Fri, 2002-12-13 at 00:21, Jean Francois Martinez wrote:
> > Perhaps Gentoo is more appropriate in this case than Red Hat?>
> <
> Perhaps. But that supposes that compiling with --march=pentium4 makes
> much difference with gcc. I don't doubt it would make a real difference
> with the Intel com
> btw if a dual P4 isn't good enough, try dual Athlon. Apparently Athlons
> eat Pentium IVs; sometimes even Durons outperform them.
Dual P4 = dual Xeon, and a dual Xeon will thump on any dual Athlon
system in any task I can think of.
It used to be the case that uni-Athlon in general outperformed
On Thu, 2002-12-12 at 19:42, John wrote:
> However, if you wish to persist with building everything yourself, the
> the project for you is "Linux from Scratch."
Perhaps Gentoo is more appropriate in this case than Red Hat? It's not
as extreme an approach as LFS, but with Gentoo, one can easily co
On Sat, Nov 10, 2001 at 07:07:57PM -0300, Oliver Schulze L. wrote:
> How about hardware issues?
> Did you check your CPU fan/temperature with lm_sensors?
>
> When Linux freezes, usually is a hardware problem.
I have also seen freezing when devices are sharing IRQs, while their drivers
can't deal
On Wed, Oct 10, 2001 at 09:32:55PM -0400, Matt Wilson wrote:
> I'm unaware of any MMX related bug in the gcc 2.96 errata packages
> released for the Red Hat Linux 7.x series.
My understanding is that GCC 2.x (96 <= x <= 98) ignores MMX routines; one
should use gcc 2.95 or gcc 3.0 in this case (i.
On Tue, Oct 02, 2001 at 09:46:45PM +0300, Matilainen Panu wrote:
> If memory serves in rescue-mode the device files are created in /tmp
> instead of /dev. If not just manually create the necessary device(s).
That's correct -- mknod is present in rescue mode and in the shell that's
available durin
