My build is x86_64.

I use the ks file in /usr/share/doc/livetools...../.....ks

(I'm sorry for this. I'm home now, and there's no vpn to my office)

I think if I use the standard environment, standard ks, standard command, I can get a useful livecd.

So I choose the ks in /usr/share/doc.

And my command is "livecd-creator -c path-to-that-file -f fd-mini".

So I think whether there are some problems in my environment.

I download the Fedora 18 dvd to install. After that, I yum install that three packages and run that command. I'll check my package version tomorrow.

BTW, what's your livecd-tools version? And ks file....(I want to have a try in my environment, mini ks file is ok)

On Wed, Apr 24, 2013 at 12:03 AM, Scott Dowdle <dowdle@montanalinux.org> wrote:

Greetings,

----- Original Message -----
> The output above is from Centos, so ignore it please.
>
> Several hours ago, I tried it in clean Fedora 18, livecd-tools from
> yum install and no error in whole output (just some warning).
>
> But when I start a machine with that, there's only one option in grub
> (from local drive in troubleshooting).
>
> And I mount my custom image and found that there's little difference
> from Fedora standard live cd:
> 1. grub problems
> 2. no initrd0.img
> 3. no EFI dir
>
> I'm so comfused about this. Did I miss some documents or some key
> steps?

Hmmm. The tboot issue I had was only on the 32-bit builds. tboot being installed seems to have no ill-effect on the 64-bit builds. I don't notice any errors during the build. What I get is a successful .iso that installs, but post-install firstboot only gives the grub prompt. To fix it I had to boot from rescue media, remove the tboot package (running grub2-mkconfig -o /boot/grub2/grub.cfg reveals the error), and the generate the /etc/grub2/grub.cfg file which didn't originally exist. There was a /boot/grub2/grub.cfg.new only. Then after figuring out that tboot was confusing grub, I just excluded that package (that was pulled in for some reason with updates but not needed really) and the problem went away.

Anyway, that does NOT appear to be the same error you are having.

There was an updated to livecd-tools for Fedora 17, 18 (and 19) yesterday... and there were a number of bugs fixed. Have a look at the update details and see if that helps any. Otherwise, search for a bug in bugzilla, add on if you find one, or report a new bug if you don't. I haven't run into the bug you are having and I rebuild F17, F18, (and now F19) usually on a weekly basis. 9 out of 10 times it is a typo in your .ks file. If you file a bug, be sure and submit your .ks file.

Of course if you want to discuss it here for a while longer without filing a bug, go for it, but provide your .ks file.

TYL,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
--
livecd mailing list
livecd@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/livecd

Gareth

Cloud Computing, Openstack, Fitness, Basketball

OpenStack contributor

My promise: if you find any spelling or grammar mistakes in my email from Mar 1 2013, notify me

and I'll donate $1 or ￥1 to an open organization you specify.