Tony, As I said, I'm just guessing. I'll assume you compiled intermezzo.o yourself with gcc 3.2, and that there were no ominous warnings. If you run mount with strace (see 'man strace'), do any useful clues appear? Or does the oops kill your system before a trace output appears? --Doc Savage Fairview Heights, IL On Tuesday November 26, 2002 Anthony Joseph Seward wrote: > On Mon, 2002-11-25 at 13:01, Robert Savage wrote: >> Tony, >> >> I'll venture a guess that the root of your difficulty is gcc 3.2. More >> specifically, that the RH8 kernel and glibc binaries were compiled >> with gcc 3.2. Prior releases used gcc 2.96RH or earlier. Binaries for >> RH7.3 very often don't work in RH8.0, and even some source code >> (notably the lt-modem driver) won't compile correctly under the new >> gcc. An unintended consequence of progress, it appears. >> >> --Doc Savage >> Fairview Heights, IL > > I'm skeptical that this is the problem. The reason for this is that all > I have to do to cause the oops is > > modprobe intermezzo > mount -t intermezzo /dev/sda4 /intermezzo/seward > > At this stage I'm only using components that are stock Red Hat. The > user space tools have not yet come into play, though I've recompiled > them with RH 8.0. > > Tony > > -- > Anthony Joseph Seward <anthony.seward@ieee.org> > > > > -- > Psyche-list mailing list > Psyche-list@redhat.com > https://listman.redhat.com/mailman/listinfo/psyche-list -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
