houghi writes:

On Fri, Mar 31, 2006 at 02:04:24PM +0200, Azerion wrote:

...

Seems like makeSUSEdvd is broken in combination with beta9. The md5sums of the iso's are okey. When I wanted to install it reported that it could not found the packages. So I makeSUSEdvd-ed again and tried with y2pmsh.

As Beta9 is not yet out (for me) I can not test it. Could you give me the complete output of makeSUSEdvd?

Is there anything special that has changed in Beta9 that could cause this behaviour?

The problem might come from the fact that we now sign the repository data to gurantee integrity of the complete repository/media and Houghi's script might not do so. The signing should be optional... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

On Fri, Mar 31, 2006 at 07:07:54PM +0200, houghi wrote:

What causes this and how can I get rid of it? At this moment makeSUSEdvd can not add the non-OSS CD to the ISO. Well, it can, but then you can not install. Screenshot at http://houghi.org/shots/susescreen009.jpg

It is worse then I thought. I have tried the following: 1) copy the first ISO to an empty directory 2) mkdir dir 3) touch dir/testing.file 4) makdir -a dir I still get the question to insert CD 1. So it is not possible to add anything to the content of the CD's. So my question is what I can do to correct this. If this is related to the signing, how can I sign it, or what can I do to go around it in the script? Can I remove files or the like? If you are using CD 1-5, all works well. It is only when you want to add CD6 or a directory with RPMs that this happens. Any ideas on insight on how to go about this? It worked well with previous versions. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

David Bolt wrote:

On Fri, 31 Mar 2006, houghi wrote:-

...

On Fri, Mar 31, 2006 at 07:07:54PM +0200, houghi wrote:

...

What causes this and how can I get rid of it? At this moment makeSUSEdvd can not add the non-OSS CD to the ISO. Well, it can, but then you can not install. Screenshot at http://houghi.org/shots/susescreen009.jpg

It is worse then I thought. I have tried the following: 1) copy the first ISO to an empty directory 2) mkdir dir 3) touch dir/testing.file 4) makdir -a dir

I still get the question to insert CD 1. So it is not possible to add anything to the content of the CD's.

So my question is what I can do to correct this. If this is related to the signing, how can I sign it, or what can I do to go around it in the script? Can I remove files or the like?

If you are using CD 1-5, all works well. It is only when you want to add CD6 or a directory with RPMs that this happens. Any ideas on insight on how to go about this? It worked well with previous versions.

There must be a subtle difference between how your script builds the DVD image to how my script does it. I'm installing beta9 now after adding building a DVD with CDs 1-6 and I've not been asked to insert CD1.

If you're interested in making a comparison, a copy of the script I use is here:

URL:http://www.davjam.org/~davjam/linux/make-dvd.sh

Regards, David Bolt

I get the error "mkisofs: Uh oh, I cant find the boot catalog directory 'boot/i386/loader'!" when I run the script with the cd´s for x86_64 platform... /JK

On Sat, Apr 01, 2006 at 08:36:28AM +0200, houghi wrote:

On Sat, Apr 01, 2006 at 12:18:04AM +0100, David Bolt wrote:

...

There must be a subtle difference between how your script builds the DVD image to how my script does it. I'm installing beta9 now after adding building a DVD with CDs 1-6 and I've not been asked to insert CD1.

If you're interested in making a comparison, a copy of the script I use is here:

URL:http://www.davjam.org/~davjam/linux/make-dvd.sh

Somehow I am unable to create a bootable ISO with that. I use just CD1 for speed to do a first testrun:

houghi@penne : ~/tmp/make-dvd.sh --create-data --make-iso --no-clean-up --dest-dir dir/dest --image-dir test/ --temp-dir dir/tmp <snip> Copying contents of CDs test//SUSE-Linux-10.1-beta9-i386-CD1.iso <snip> Recreating MD5SUMS: #This might be the cause. Will try it later <snip> mkisofs 2.01 (i686-suse-linux) mkisofs: No such file or directory. Invalid node - dir/tmp/DVD/.

Sigh. Still the same error even after making new MD5SUMS. It still asks to insert a CD when I add something. :-( So what has changed please? How can I add extra stuff to the CD? houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

_____ From: houghi [mailto:houghi@houghi.org] To: opensuse-factory@opensuse.org Sent: Sat, 01 Apr 2006 15:10:40 +0200 Subject: Re: [opensuse-factory] makeSUSEdvd broken for beta9 On Sat, Apr 01, 2006 at 11:08:20AM +0200, houghi wrote:

Sigh. Still the same error even after making new MD5SUMS. It still asks to insert a CD when I add something. :-(

So what has changed please? How can I add extra stuff to the CD?

There must have been a party in Nurnberg, because normaly people are awake and reacting. ;-) I have tried removing $CD_DIR/content.* and $CD_DIR/media.1/products.* and that gave me again the same result. Next I removed all lines that started with KEY and META in $CD_DIR/content. Still nothing. Does really nobody know what is going on or how to solve it? As it is not really a SUSE issue, I can't file a big report. :-( houghi -- Seems we're alone here today! ;-) I tried the script posted here earlier, and I successfully created a DVD with custom RPMs included. Had to change the boot/i386 to accommodate for x86_64 version. /Jan K.

On Sat, 1 Apr 2006, houghi wrote:-

On Sat, Apr 01, 2006 at 03:40:29PM +0200, Jan Karjalainen wrote:

...

I tried the script posted here earlier, and I successfully created a DVD with custom RPMs included. Had to change the boot/i386 to accommodate for x86_64 version.

I was not able to work with it.

Did it give any errors? I might be able to get it to work for you.

Also the script does not do that much differently, as far as I can see.

Comparing them, there doesn't seem to be much difference although there must be some since, after some tweaking to get it working with multiple different directories, the DVD your script created was about 13Mb smaller than the one mine made. I've yet to actually test it out by trying an install and will let you know how it works out.

Darn, this reverse enginering is hard.

And a distinct lack of comments won't help the process either. :-/ Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11 AMD2400(32) 768Mb SUSE 10.0 | Falcon 14Mb TOS 4.02 | A4000 4Mb RISCOS 3.11 AMD2600(64) 512Mb SUSE 10.0 | | RPC600 129Mb RISCOS 3.6

On Sat, 1 Apr 2006, houghi wrote:-

On Sat, Apr 01, 2006 at 03:39:03PM +0100, David Bolt wrote:

...

Did it give any errors? I might be able to get it to work for you.

As posted earlier: Somehow I am unable to create a bootable ISO with that. I use just CD1 for speed to do a first testrun:

houghi@penne : ~/tmp/make-dvd.sh --create-data --make-iso --no-clean-up --dest-dir dir/dest --image-dir test/ --temp-dir dir/tmp <snip> Copying contents of CDs test//SUSE-Linux-10.1-beta9-i386-CD1.iso <snip> Recreating MD5SUMS: #This might be the cause. Will try it later <snip> mkisofs 2.01 (i686-suse-linux) mkisofs: No such file or directory. Invalid node - dir/tmp/DVD/.

Interesting. I'll have a good look to see why it came up with that error. In theory, it shouldn't since mkisofs is passed the same directory that create_package_descr uses. Try re-running it without specifying either --temp-dir or --dest-dir. They're not strictly needed as, if they aren't specified, the script will pick present directory by default.

...

Comparing them, there doesn't seem to be much difference although there must be some since, after some tweaking to get it working with multiple different directories, the DVD your script created was about 13Mb smaller than the one mine made.

13MB? Wow. I edit some things, but not much.

Well, it's not really that great a difference

...

And a distinct lack of comments won't help the process either. :-/

It is half the fun. :-) I asume the difference is that I CD's in reversed order.

I'm guessing that that is the cause of the problem. See below.

I have a working version, I think. http://houghi.org/script/makeSUSEdvd

Grabbed.

It would be nice if some people could verify that it works, or not.

I've downloaded it and just finished building the ISO.

I test in a VM manager, otherwise I would have burned abut 20-40 DVD's already. :-)

You too :)

After verification, I will put 0.27 online at SF and remove the one above.

The 0.27 script failed again. I guess that I've just compared the ./content files on the one produced by my script, and that produced by yours and your script has the add-on CD content file whereas mine has the file from the last CD image processed, which would be CD5 when using the full set. I've edited the 0.27 script so it doesn't work in reverse order[0], built another DVD image, tested it and it seems to have worked. [0] Along with a couple of other minor tweaks. The diff file is here: URL:http://www.davjam.org/~davjam/linux/makeSUSEdvd.diff Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11 AMD2400(32) 768Mb SUSE 10.0 | Falcon 14Mb TOS 4.02 | A4000 4Mb RISCOS 3.11 AMD2600(64) 512Mb SUSE 10.0 | | RPC600 129Mb RISCOS 3.6

On Sat, 1 Apr 2006, houghi wrote:- <snip>

The reverse order is just a gimmick, so you see CD5, CD4, ... However a different order should not be the the cause of the problem.

Apparently, at present, it does but only when there is the add-on CD present.

So for me it is not a real solution to the problem. Next version might be that the naming is such that the extra ISO is again last. e.g. now it is: SUSE-Linux-10.1-beta9-Addon-BiArch.iso SUSE-Linux-10.1-beta9-i386-CD1.iso ... SUSE-Linux-10.1-beta9-i386-CD5.iso What if the next CD is called SUSE-Linux-10.1-beta9-non-oss.iso ( or SUSE-Linux-10.1-beta9-NON-OSS.iso) then you have a different order. Or what if they renamed their CD's, or use real CD's and put them in in random order (with the -c option).

Without coding around the problem, it's going to happen again.

Also it could be that a person wants to use his own CD that he made and gave it whatever name.

At present, it would probably fail. If it appears after the last SUSE CD, the contents file will overwrite the previous one and we're back to square one.

That is the difference with your script and mine. You only have to work for you, mine has to work for the rest of the world. ;-)

Well, as I said, I wasn't expecting mine to be released into the wild.

So many reasons that it is not a real solution.

I know, but there are a few possible solutions. One would be to check each CD as it's mounted, and the contents copied, to see if it's the first SUSE CD. If it is, make a temporary copy of both ./content and ./media.1/products. Once all the CDs are copied, write the temporary copies back to the correct places in the DVD structure and this should get around the problem. To really make sure that you've got the right ones, you could parse the ./content file and compare it to known good values, only making the copies if they match. Another possible solution would be to build your own ./content and ./media.1/products files. Looking at the i386 version, the ./media.1/products file have a very simple format: / SUSE-Linux-CD-OSS-i386 10.1 The ./content is a little more complex but, if you're making an online repository, you're already going to be making a basic one for that. A few minor additions and you could have a quite customised DVD[0].

Still thanks and if anybody from SUSE can give some feedback, that would also be great.

houghi

[0] like changing the default language and time-zone. Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11 AMD2400(32) 768Mb SUSE 10.0 | Falcon 14Mb TOS 4.02 | A4000 4Mb RISCOS 3.11 AMD2600(64) 512Mb SUSE 10.0 | | RPC600 129Mb RISCOS 3.6

On Sat, Apr 01, 2006 at 05:55:25PM +0100, David Bolt wrote:

...

After verification, I will put 0.27 online at SF and remove the one above.

The 0.27 script failed again.

This is getting weird. I have tried it and it worked. One other person emailed me that 0.27 worked. So why did it not work with you? Just to get the obvious out of the way, you ran ./makeSUSEdvd and not just makeSUSEdvd? The second could run a previous installed version. Sorry to ask this, but I would hate to look for solutions if there not is a real problem. That said, I previously tried to run it without the META an KEY lines and firt it did not work. Now it did. I have tried 3 times yesterday and again today and it worked, so I am really curious why it did work with me and the other person and not with you. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

On Sun, 2 Apr 2006, houghi wrote:-

On Sat, Apr 01, 2006 at 05:55:25PM +0100, David Bolt wrote:

...

...

After verification, I will put 0.27 online at SF and remove the one above.

The 0.27 script failed again.

This is getting weird. I have tried it and it worked. One other person emailed me that 0.27 worked. So why did it not work with you? Just to get the obvious out of the way, you ran ./makeSUSEdvd and not just makeSUSEdvd? The second could run a previous installed version.

Since I don't have it installed, and I don't have . in my path, I have to use ./makeSUSEdvd.

Sorry to ask this, but I would hate to look for solutions if there not is a real problem.

That I can understand.

That said, I previously tried to run it without the META an KEY lines and firt it did not work. Now it did.

I have tried 3 times yesterday and again today and it worked, so I am really curious why it did work with me and the other person and not with you.

I don't know. Removing the 'r' from here: # MOUNT_ISO : mount the ISOs and copy them to one directory MOUNT_ISO () { for DIR in `ls $HERE/*.iso -Ar` # remove this letter # ------------^ do test ! -d TEMP_DIR && mkdir TEMP_DIR and then rebuilding the DVD made an image that booted correctly. With it there, it failed. Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11 AMD2400(32) 768Mb SUSE 10.0 | Falcon 14Mb TOS 4.02 | A4000 4Mb RISCOS 3.11 AMD2600(64) 512Mb SUSE 10.0 | | RPC600 129Mb RISCOS 3.6

On Mon, 3 Apr 2006, houghi wrote:-

On Sun, Apr 02, 2006 at 04:31:59PM +0100, David Bolt wrote:

...

and then rebuilding the DVD made an image that booted correctly. With it there, it failed.

Failed to boot? That is another problem and should be unrelated to the checking of the media issue.

No, it booted just fine. Once YaST started getting all the relevant data, it failed by asking for the add-on disc without allowing me to cancel. Once that happens, it's stuck. Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11 AMD2400(32) 768Mb SUSE 10.0 | Falcon 14Mb TOS 4.02 | A4000 4Mb RISCOS 3.11 AMD2600(64) 512Mb SUSE 10.0 | | RPC600 129Mb RISCOS 3.6

On Mon, 3 Apr 2006, houghi wrote:-

On Mon, Apr 03, 2006 at 01:27:50PM +0100, David Bolt wrote:

...

No, it booted just fine. Once YaST started getting all the relevant data, it failed by asking for the add-on disc without allowing me to cancel. Once that happens, it's stuck.

Till now you are the only one that has this behaviour. Other people have had positive results. So no idea why it would happen to you.

And, after another test it worked. Very weird.

Still awfully silent from SUSE. :-(

Indeed :-| Now, the bad news. I think I've found a bug in the script. If I don't have the ISOs in the current directory, and pass the path to them using -d the script can't find them. If I copy them to the current directory, it works just fine, as you can see from below: ===== start snippet ===== davjam@playing:/shared-partitions/playing-hdb2> clear && ./makeSUSEdvd.0.27.orig -s /shared-partitions/playing-hdc5/test -o $(pwd)/dvd/ -d $(pwd)/beta9/ Working with /shared-partitions/playing-hdb2/beta9/ as source of the ISO files. Putting the DVD ISO in /shared-partitions/playing-hdb2/dvd/ . Putting directory structure in /shared-partitions/playing-hdc5/test . If used with -i, this is where your sources are. SUSE-Linux-10.1-beta9-Addon-BiArch.iso: No such file or directory You do not know the root password or typed it wrong. This program will now stop. Please start again and enter the correct password, or ask the systemadministrator to give it to you. davjam@playing:/shared-partitions/playing-hdb2> ls -l /shared-partitions/playing-hdb2/beta9/ total 3662220 drwxr-xr-x 2 davjam users 4096 2006-04-03 22:02 makeSUSEdvd.9542 -rw-r--r-- 1 davjam users 312975360 2006-03-31 21:14 SUSE-Linux-10.1-beta9-Addon-BiArch.iso -rw-r--r-- 1 davjam users 680611840 2006-03-31 19:17 SUSE-Linux-10.1-Beta9-i386-CD1.iso -rw-r--r-- 1 davjam users 677060608 2006-03-31 18:38 SUSE-Linux-10.1-Beta9-i386-CD2.iso -rw-r--r-- 1 davjam users 688134144 2006-03-31 19:46 SUSE-Linux-10.1-Beta9-i386-CD3.iso -rw-r--r-- 1 davjam users 701747200 2006-03-31 20:23 SUSE-Linux-10.1-Beta9-i386-CD4.iso -rw-r--r-- 1 davjam users 685877248 2006-03-31 19:54 SUSE-Linux-10.1-Beta9-i386-CD5.iso d davjam@playing:/shared-partitions/playing-hdb2> clear && ./makeSUSEdvd.0.27.orig -s /shared-partitions/playing-hdc5/test -o $(pwd)/dvd/ Putting the DVD ISO in /shared-partitions/playing-hdb2/dvd/ . Putting directory structure in /shared-partitions/playing-hdc5/test . If used with -i, this is where your sources are. /shared-partitions/playing-hdc5/test already exists. Using /shared-partitions/playing-hdc5/test.CD.9542 instead /shared-partitions/playing-hdb2/dvd already exists. Using /shared-partitions/playing-hdb2/dvd.DVD.9542 instead Making a DVD of several CD's The root password is needed. If you know how to do this without, please tell me Here we go. /shared-partitions/playing-hdb2/SUSE-Linux-10.1-Beta9-i386-CD5.iso is being mounted and copied on TEMP_DIR. /shared-partitions/playing-hdb2/SUSE-Linux-10.1-Beta9-i386-CD4.iso is being mounted and copied on TEMP_DIR. /shared-partitions/playing-hdb2/SUSE-Linux-10.1-Beta9-i386-CD3.iso is being mounted and copied on TEMP_DIR. /shared-partitions/playing-hdb2/SUSE-Linux-10.1-Beta9-i386-CD2.iso is being mounted and copied on TEMP_DIR. /shared-partitions/playing-hdb2/SUSE-Linux-10.1-Beta9-i386-CD1.iso is being mounted and copied on TEMP_DIR. /shared-partitions/playing-hdb2/SUSE-Linux-10.1-beta9-Addon-BiArch.iso is being mounted and copied on TEMP_DIR. ===== end snippet ===== Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11 AMD2400(32) 768Mb SUSE 10.0 | Falcon 14Mb TOS 4.02 | A4000 4Mb RISCOS 3.11 AMD2600(64) 512Mb SUSE 10.0 | | RPC600 129Mb RISCOS 3.6

On Tue, 4 Apr 2006, houghi wrote:-

On Mon, Apr 03, 2006 at 11:21:29PM +0100, David Bolt wrote:

<Snip>

...

Now, the bad news. I think I've found a bug in the script. If I don't have the ISOs in the current directory, and pass the path to them using -d the script can't find them. If I copy them to the current directory, it works just fine, as you can see from below:

Thanks for finding this. Will be fixed in the next version. In ISO_TEST you just change the line: sudo mount -o loop $CD $HERE/makeSUSEdvd.$PPID || ROOT_CHECK to sudo mount -o loop $HERE/$CD $HERE/makeSUSEdvd.$PPID || ROOT_CHECK

Will look into it and test it some more before I put it online.

Applying that change made it work fine here. I'm still wondering just why I didn't see that simple fix.

It is there for a LONG time now and I did not get any complaints, so I doubt it is extremely urgent

I only noticed it because of the way I store the images. I use the deltas to build the full images and keep both the deltas and the full images in separate directories. You'll probably find that most (all?) of the users are calling it from inside the directory containing the CD images. It was only because I called it from the directory above that I noticed the failure.

and I would hate to see it breaking other things.

That I can understand. The good news is that I don't see where this change would break anything, especially since it's effect is limited to a tiny section of the script. Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11 AMD2400(32) 768Mb SUSE 10.0 | Falcon 14Mb TOS 4.02 | A4000 4Mb RISCOS 3.11 AMD2600(64) 512Mb SUSE 10.0 | | RPC600 129Mb RISCOS 3.6

On Sat, 1 Apr 2006, Jan Karjalainen wrote:- <snip>

-- Seems we're alone here today! ;-)

It's that annoying thing known as Real Life (TM). Sometimes it doesn't half get in the way of doing things.

I tried the script posted here earlier, and I successfully created a DVD with custom RPMs included.

Which does beg the question as to what the difference is between my script and Houghis. Well, apart from the fact that mine was written just for myself and Houghi wrote his to share.

Had to change the boot/i386 to accommodate for x86_64 version.

I was going to reply to your earlier post saying about the i386 loader not being found by suggesting that change but you didn't need it. Regards, David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11 AMD2400(32) 768Mb SUSE 10.0 | Falcon 14Mb TOS 4.02 | A4000 4Mb RISCOS 3.11 AMD2600(64) 512Mb SUSE 10.0 | | RPC600 129Mb RISCOS 3.6

houghi writes:

On Fri, Mar 31, 2006 at 07:07:54PM +0200, houghi wrote:

...

What causes this and how can I get rid of it? At this moment makeSUSEdvd can not add the non-OSS CD to the ISO. Well, it can, but then you can not install. Screenshot at http://houghi.org/shots/susescreen009.jpg

It is worse then I thought. I have tried the following: 1) copy the first ISO to an empty directory 2) mkdir dir 3) touch dir/testing.file 4) makdir -a dir

I still get the question to insert CD 1. So it is not possible to add anything to the content of the CD's.

So my question is what I can do to correct this. If this is related to the signing, how can I sign it, or what can I do to go around it in the script? Can I remove files or the like?

Please open a bugreport and CC me on it. I'll assign it to the developers so that we find a solution for this, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126