jejv

I've never seen an actual AMD64 linux system, let alone a Mandrake AMD64 linux system, but I want to build an AMD64 system which runs proprietary 32-bit binaries (Maple, Mathematica, S-Plus. SPSS, etc), which I mostly use at present on 32-bit Mandrake. I would naively suppose that there were two sets of gtk2 libraries, one in . wherever/lib/ and one in . wherever/lib64/ And I would (perhaps naively) expect that all the libraries in an AMD64 distribution would be provided in both 32- and 64-bit versions. How does this work with Mandrake 10.x ? Would I need Two sets of installation disks ? Does rpm/urpmi still get confused ? Regards, John.

Errm. Thankyou. Well, yes I could consider that, and I could consider a lot of other things. I might look at ext3. I can also hack the scripts so that fsck gets run on an ext2 filesystem that wasn't shut down properly. But if I don't have any idea what the rationale is for not running fsck, that would be a hack and not a fix. On the face of it, failing to run fsck on ext2 seems a quite demented decision. But I guess I'm missing something. Can anybody tell me what ? John.

This is on 8.2 upgraded to 9.0 I tried posting this on MandrakeExpert, but it didn't seem to accept the form posting. FSCK not run after unclean shutdown. All my disk partitions are ext2 or swap. After an unclean shutdown: - How is it that the boot scripts ASK if I want to run fsck ? Shouldn't it just do it, without asking ? - If I do hit "Y" in time, it seems that fsck isn't necessarily being run - sometimes boot continues much too quick to be consistent with running fsck, and there's no fsck output on the console. What's going on ? Since I don't trust the boot scripts, I run e2fsck from the boot cd in rescue mode after an unclean shutdown. You might ask what is/are the cause of the "unclean" shutdowns, but I'll ask about that separately. John.