Hi,
I'm getting a puzzling problem when building a .ks file that worked
two days ago:
Traceback (most recent call last):
File /usr/bin/livecd-creator, line 140, in module
sys.exit(main())
File /usr/bin/livecd-creator, line 124, in main
creator.configure()
File
On Tue, Jul 14, 2009 at 09:37:33PM -0400, Jeremy Katz wrote:
On Tuesday, July 14 2009, Martin Dengler said:
On Tue, Jul 14, 2009 at 11:02:25AM -0400, Jeremy Katz wrote:
On Tuesday, July 14 2009, Martin Dengler said:
I'm getting a .ISO without a /home despite the filesystem rpm being
Hi,
I'm getting a .ISO without a /home despite the filesystem rpm being
installed, and I'd really appreciate any tips on debugging this or
hints as to how this might happen.
This is with the example .ks and I can get livecd-creator to work on a
number of other machines. If I chroot and install
On Tue, Jul 14, 2009 at 11:02:25AM -0400, Jeremy Katz wrote:
On Tuesday, July 14 2009, Martin Dengler said:
I'm getting a .ISO without a /home despite the filesystem rpm being
installed, and I'd really appreciate any tips on debugging this or
hints as to how this might happen.
Any
livecd-iso-to-disk.sh doesn't do the right thing w.r.t. loop devices
and MBR detection. I don't think this is intentional, but it
currently requires loop devices to start with an MBR, by virtue of
getdisk() being a NOOP for loop devices and checkMBR assuming that the
disk must need an MBR.
