>>>>> "A" == Alexander Skwar <[EMAIL PROTECTED]> writes:
A> So sprach �Gary Lawrence Murphy� am 2001-07-17 um 17:39:24
A> -0400 :
>> farther ... blowing up again with the same error when it
>> encounters /images/boot.cat
A> Which you can also remove as it's automatically created by
A> mkisofs.
Not only _can_ I remove it, I _must_ remove it or mkisofs will blow
a gasket ;)
That out of the way, I can now generate beautiful shiny disks that
actually boot my computer and initiate the new graphical install
process (nice work people!), but I am left now with one small
tactical question:
Is there a utility to verify that all my RPMs are consistent, that
there are no missing dependencies?
I may be out of luck since my pressing motivation to create this CD
set is because my RPM kit is out of commission, but some functions
appear to work, and the rpm kit within the cooker itself will work,
the only hurdle appears to be when things try to use my local rpm
database and keel over with errors like
cannot open Depends index using db3: Cannot allocate memory (12)
rpmdb: Unable to allocate 8347 bytes rom mpool shared region
This leads to another question about the Mandrake install process. My
guess is that I cannot save my old rpm db; it correctly reports all
the packages installed, but does not allow any other queries (file lists,
or package info) and does not allow updates. Thus, I fear I will have to
choose "Install" instead of "Update" in the installer.
What will "Install" kill? Does it (must it) reformat the HD, or will it
just overwrite the rpmdb leaving everything already installed? If it
does reformat, is there some way to prevent/bypass that step and go
straight to package installations?
--
Gary Lawrence Murphy <[EMAIL PROTECTED]>: office voice/fax: 01 519 4222723
T(C)Inc Business Innovations through Open Source http://www.teledyn.com
KernelWiki Community Linux Docs: http://kernelbook.sourceforge.net/wiki
