[09:24] <sekon_> Hello, which command is used to build iso for ubuntu ?? are there any scripts that can act as reference
[09:24] <sekon_> i am using mkisofs, unpatched from upstream
[09:24] <sekon_> be right back .. sorry
[09:28] <sekon_> Hello, I am trying to create a ISO of ubuntu.
[09:28] <sekon_> I take a release of ubuntu CD, mount it on loopback and cp files over to a staging directory
[09:30] <sekon_> i then proceed to use mkisofs (of cdrecord tools)
[09:31] <sekon_> version 3.0 unpatched to build the CDROM
[09:31] <sekon_> the command i used is
[09:32] <sekon_> mkisofs -R -J -hide-rr-moved -v -d -N -no-emul-boot -boot-load-size 32 -boot-info-table -b isolinux/isolinux.bin -c isolinux/boot.cat -o /home/code/fossee/LiveDVD/LP_Test.iso .
[09:36] <sekon_> The DVD does not boot, i get  "unable to open '/dev/zram0" and unable to find medium containg a live file system
[09:36] <sekon_> and i get dropped into busybox shell
[09:37] <sekon_> apart from using an unpatched mkisofs, i dont see any "experimenting", am i doing something fundementally wrong
[09:37] <sekon_> ??
[09:49] <sekon_> The same result when loading the ISO in qemu
[13:28] <superm1> sekon_: it sounds like you might potentially be forgetting to include the .disk directory when copying files over to the staging directory
[14:07] <CIA-16> ubiquity: cjwatson * r5100 trunk/ (d-i/update-control debian/changelog debian/control):
[14:07] <CIA-16> ubiquity: Build-depend/depend on python-gi-cairo/python-gi-dev rather than
[14:07] <CIA-16> ubiquity: python-gobject-cairo/python-gobject-dev.
[14:10] <CarlFK> sekon_: here are the scripts I wrote a few years ago: https://github.com/CarlFK/DVswitchLiveCD
[14:29] <brendand> ev - with the alpha1 candidate iso, if i choose to install from within the live session, i end up with a big space on the 'Choose a picture' screen, where the camera output should be
[14:30] <brendand> ev - i'm about to check if it happens when i choose 'Install Ubuntu' directly
[14:30] <ev> brendand: has this worked for you previously?
[14:30] <brendand> ev - yeah, but i usually don't install from inside the live session
[14:30] <ev> shouldn't make a difference
[14:31] <brendand> ev - if this doesn't work i have to assume a regression. could be hardware specific though
[14:32] <ev> okay
[14:38] <brendand> ev - nah, same thing. you haven't seen/heard about this yet?
[14:38] <brendand> ev - it was working in the last spin
[14:38] <ev> no, I haven't, but I haven't had my ear to ground
[14:39] <ev> what with the crash database and dx team work
[14:39] <ev> please file a bug
[14:40] <brendand> ev - sure
[14:40] <brendand> just gonna check if the camera is working once everything is installed
[16:14] <brendand> ev - it doesn't even work with cheese, so ubiquity is absolved. i'll just raise a kernel bug
[16:21] <ev> yay
[21:32] <kyleN> ev, hi. i'd like to run a type of oem-config in a chroot (at image build time) with no X and use all preseeded values to set things up. possible? oem-config-debconf or oem-config-remaster?
[21:37] <kyleN> ev: nothing too fancy: just want to ensure a default/correct user exists (for an arm system that has no debian-installer, just a root fs) and other bare minimum setups are done correctly