comps file not version 0??? sig 11???

comps file not version 0??? sig 11???

Post by Tommy Dag-L?ngstr? » Sat, 10 Apr 1999 04:00:00



I have an iMac rev B with 96Mb ram, and i'm trying to install linuxppc r4.
The installer boots fine, but when it's searching the rpm database i get a
"comps file not version 0 as expected" message. When i click OK and install
continues, but just before it's starting to install the rpms i get a "sig
11"
and install quits. Why?
 
 
 

comps file not version 0??? sig 11???

Post by Jack Howar » Sat, 10 Apr 1999 04:00:00




> I have an iMac rev B with 96Mb ram, and i'm trying to install linuxppc r4.
> The installer boots fine, but when it's searching the rpm database i get a
> "comps file not version 0 as expected" message. When i click OK and install
> continues, but just before it's starting to install the rpms i get a "sig
> 11"
> and install quits. Why?

This sounds like you might have allowed the comps file to be converted to
Mac text format. If you have the comps on your MacOS HFS partition open it
with BBEdit Lite and save it down with Unix line breaks set in the Options.
                                 Jack

 
 
 

comps file not version 0??? sig 11???

Post by Ansgar Eszterman » Tue, 13 Apr 1999 04:00:00



> I have an iMac rev B with 96Mb ram, and i'm trying to install linuxppc r4.
> The installer boots fine, but when it's searching the rpm database i get a
> "comps file not version 0 as expected" message. When i click OK and install
> continues, but just before it's starting to install the rpms i get a "sig
> 11"
> and install quits. Why?

Your comps.pmac file probably is not a Unix text file. There are several
utilities that allow you to change this, e.g. CodeWarrior our StuffIt.

Ansgar

 
 
 

1. Memory Fault (11) (sig 11)

     I have a program coded in C that will not run.  The code compiles
without problem, but when I attempt a run I receive a memory fault and
a core dump.  I tried using the symbolic debugger and received the line
'Memory Fault (11) (sig 11) at address'.  I did look up the signal and
discovered 11 is a segmentation violation, but I am not exactly sure what
that means.  

     If someone could point me to the proper manual or attempt an explanation
I would greatly appreciate the effort.  Please respond by mail.  Thanks in
advance.

Steven Kilby
--    
--
Steven M. Kilby    Univ. of Cincinnati, College of Business Administration


2. Sparcstation into telephone

3. K6, Sig 11, not RAM or Cache related!?

4. mt and taper don't recognize /dev/rft0

5. Very weird gtar errors between Version 1.11.1 and 1.11.8

6. caldera Lite, XF86Config and Millenium

7. Sig 11 problem

8. Save over 50%

9. minicom - killed with sig 11!

10. 4.0.1, NV, and daily sig 11's

11. Hardware Problems causing Sig 11....

12. compiling dilemma(gcc 2.7.x) /sig 11

13. Sig 11 problem