[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Re: [SOLVED] Some issues with live-build 2.0.7-1 in ubuntu mode



Hi Robert,

 Your help in testing the Ubuntu support is greatly appreciated.

On Tue, Dec 14, 2010 at 8:39 AM, Robert Key <rob54321@mighty.co.za> wrote:
Hi and thanks Cody, you doing the patch is fine.

There are other important issues all be it simple:

1. For the udebs there must be a soft link to maverick and lucid ( or any other ubuntu distributions)
in the directory:   /usr/share/live/build/data/debian-cd that points to squeeze.

Without the link the installer will fail.

Daniel has added the actual data directories from Ubuntu's debian-cd branch so this won't be needed anymore.
 
2. I also had to disable the gtk installer as vmlinuz and initrd.gz do not appear under current/images/cdrom/gtk for the debian installer in the ubuntu archives.

Yes. I was hoping Colin Watson would re-enable the GTK d-i build.

Daniel: Feel free to update the default for Ubuntu to just have this disabled by default for Ubuntu for all releases. I'll send in a patch if you don't get around to it.
 
3. I also disabled the win32loader as this is kept in a different place in the ubuntu archive.

I'll look into this further. I thought this was already disabled by default though for Ubuntu.
 
4.  As far as the cd images are concerned they were simply accessed from the ubuntu archive and appear in the binary image.  When I installed the install worked perfectly (in text mode, normal vga)
and was quite fast.

I assume you mean d-i images and not cd images here?
 
5. Oh one other thing the boot parameter cdrom-detect/try-usb=true is vital or else you will receive the message "could not load cd image.

If you're using usb-hdd then live-build should add that boot parameter automatically. If you're running into cases where it doesn't, please let file a bug.
 
Some notes for the install to work.
The partition on which the image is installed must be fat32 not ext4, ext3 or else the cd is not found.

Thats interesting. The next time I'm looking at cdrom-detect I'll see about fixing that.
 
The partition does not have to be first on the disk but must be the first one with a cd image on it as the search for cd images starts from 1 , 2, 3  etc and stops as soon as one is found. If the wrong one is found the message "no kernel modules found".

Please remember the link 1. above.
Thanks for all your help.
 Rob Key

Thanks again!

Cheers,

--
Cody A.W. Somerville
Release Engineer
Foundations Team
Custom Engineering Solutions Group
Canonical OEM Services
Phone: +1 781 850 2087
Cell: +1 613 401 5141
Fax: +1 613 687 7368
Email: cody.somerville@canonical.com

Reply to: