[Cooker] Rolling a Cooker: mkisofs error?
In my quest to roll my own cooker disks, I've got to the point where I can create disks 2 and 3, but the whereabouts of disk 1 remains a mystery. I use the command mkcds /home/ftp/pub/cooker /home/ftp/pub/iso and the log seems to be fine for the first while ... choosing compression method with gzip -9 \ for archive /tmp/.build_hdlist/hdlist1.cz real archive size of /tmp/.build_hdlist/hdlist1.cz is 2615726 repeats for hdlist2 and hdlist3 (any util to dump those lists?) but then things go missing. mkcds reports the following error Mandrake -- . Mandrake -- .. Mandrake -- RPMS Mandrake -- RPMS.cooker Mandrake -- base Mandrake -- mdkinst Mandrake -- share Ignoring file mkcds~ Using RR_MO000 for /rr_moved (rr_moved) mkisofs: Error: (NULL POINTER) and /rr_moved have the same Rock Ridge name mkisofs: Unable to sort directory and that appears to be the end of disk-1 I'm going to probe this a bit by putting some trace statements into mkcd.pl, but does this look familiar to anyone? Any tips or guesses are greatly appreciated. -- Gary Lawrence Murphy [EMAIL PROTECTED] TeleDynamics Communications Inc Business Innovations Through Open Source Systems: http://www.teledyn.com Computers are useless. They can only give you answers.(Pablo Picasso)
Re: [Cooker] Rolling a Cooker: mkisofs error?
Ah ... learned an important lesson today: You can't just start from an old CD set, unpack it to your HD and _migrate_ it to a cooker with add-only rsync. There are generated files that confuse mkisofs into oblivion. From that last posting, I removed root cooker directories rr_moved and a few other files not found on the FTP archive, and it gets much, much farther ... blowing up again with the same error when it encounters /images/boot.cat -- 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
Re: [Cooker] Rolling a Cooker: mkisofs error?
So sprach »Gary Lawrence Murphy« am 2001-07-17 um 17:39:24 -0400 : farther ... blowing up again with the same error when it encounters /images/boot.cat Which you can also remove as it's automatically created by mkisofs. Alexander Skwar -- How to quote: http://learn.to/quote (german) http://quote.6x.to (english) Homepage: http://www.digitalprojects.com | http://www.iso-top.de iso-top.de - Die günstige Art an Linux Distributionen zu kommen Uptime: 15 hours 40 minutes
Re: [Cooker] Rolling a Cooker: mkisofs error?
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
