a better way to make XO images

[Scott Douglass]

Hi,

I propose that we use the Fedora virtualization infrastructure to create
Rawhide OS images for the XO.

It should be simple using a kickstart file and the virtualization tools
to create an OS installed on a loopback mounted file that contains a
normal ext3 file system.

Then, we just mount that file, and use it as the source for the rest of
CJB's livecd-iso-to-xo.sh.

No live CD cruft at all. No squashfs. Much much cleaner.

I'm going to give it a try once I come up with a machine that has enough
memory/diskspace for this operation...

[Peter Robinson]

Hi,

>  I propose that we use the Fedora virtualization infrastructure to
> create
>  Rawhide OS images for the XO.
>
>  It should be simple using a kickstart file and the virtualization tools
>  to create an OS installed on a loopback mounted file that contains a
>  normal ext3 file system.
>
>  Then, we just mount that file, and use it as the source for the rest of
>  CJB's livecd-iso-to-xo.sh.
>
>  No live CD cruft at all. No squashfs. Much much cleaner.
>
>  I'm going to give it a try once I come up with a machine that has enough
>  memory/diskspace for this operation... 
I've been trying to use the Fedora appliance-tools to do exactly that
but it seems to have some issues on F-10 at the moment.

Peter

[Bryan Kearney]

Peter Robinson wrote:
>  Hi,
>  
> > I propose that we use the Fedora virtualization infrastructure to create
> > Rawhide OS images for the XO.
> >
> > It should be simple using a kickstart file and the virtualization tools
> > to create an OS installed on a loopback mounted file that contains a
> > normal ext3 file system.
> >
> > Then, we just mount that file, and use it as the source for the rest of
> > CJB's livecd-iso-to-xo.sh.
> >
> > No live CD cruft at all. No squashfs. Much much cleaner.
> >
> > I'm going to give it a try once I come up with a machine that has enough
> > memory/diskspace for this operation...
>  
>  I've been trying to use the Fedora appliance-tools to do exactly that
>  but it seems to have some issues on F-10 at the moment. 
What issues have you been having?

-- bk

[Peter Robinson]

> > I've been trying to use the Fedora appliance-tools to do
> exactly that
> > but it seems to have some issues on F-10 at the moment.
>
>  What issues have you been having? 
I get the following errors, it then seems to go through the montions
OK but I don't seem to get a image.

[root@neo ~]# appliance-creator -n OLPC-rawhide --config
/home/perobinson/fedora/olpc/olpc-4.ks --cache=/home/images/cache
Error: Error informing the kernel about modifications to partition
/dev/loop0p1 -- Invalid argument.  This means Linux won't know about
any changes you made to /dev/loop0p1 until you reboot -- so you
shouldn't mount it or use it in any way before rebooting.
Warning: The kernel was unable to re-read the partition table on
/dev/loop0 (Invalid argument).  This means Linux won't know anything
about the modifications you made until you reboot.  You should reboot
your computer before doing anything with /dev/loop0.
['/']
mke2fs 1.41.4 (27-Jan-2009)
Filesystem label=/
OS type: Linux

Peter

[Bryan Kearney]

Peter Robinson wrote:
> >> I've been trying to use the Fedora appliance-tools to do
> exactly that
> >> but it seems to have some issues on F-10 at the moment.
> > What issues have you been having?
>  
>  I get the following errors, it then seems to go through the montions
>  OK but I don't seem to get a image.
>  
>  [root@neo ~]# appliance-creator -n OLPC-rawhide --config
>  /home/perobinson/fedora/olpc/olpc-4.ks --cache=/home/images/cache
>  Error: Error informing the kernel about modifications to partition
>  /dev/loop0p1 -- Invalid argument.  This means Linux won't know about
>  any changes you made to /dev/loop0p1 until you reboot -- so you
>  shouldn't mount it or use it in any way before rebooting.
>  Warning: The kernel was unable to re-read the partition table on
>  /dev/loop0 (Invalid argument).  This means Linux won't know anything
>  about the modifications you made until you reboot.  You should reboot
>  your computer before doing anything with /dev/loop0.
>  ['/']
>  mke2fs 1.41.4 (27-Jan-2009)
>  Filesystem label=/
>  OS type: Linux
>  
>  Peter 
Could you send me your ks file?

-- bk

[Peter Robinson]

> >>> I've been trying to use the Fedora appliance-tools to
> do exactly that
> >>> but it seems to have some issues on F-10 at the moment.
> >>
> >> What issues have you been having?
> >
> > I get the following errors, it then seems to go through the montions
> > OK but I don't seem to get a image.
> >
> > [root@neo ~]# appliance-creator -n OLPC-rawhide --config
> > /home/perobinson/fedora/olpc/olpc-4.ks --cache=/home/images/cache
> > Error: Error informing the kernel about modifications to partition
> > /dev/loop0p1 -- Invalid argument.  This means Linux won't know about
> > any changes you made to /dev/loop0p1 until you reboot -- so you
> > shouldn't mount it or use it in any way before rebooting.
> > Warning: The kernel was unable to re-read the partition table on
> > /dev/loop0 (Invalid argument).  This means Linux won't know anything
> > about the modifications you made until you reboot.  You should reboot
> > your computer before doing anything with /dev/loop0.
> > ['/']
> > mke2fs 1.41.4 (27-Jan-2009)
> > Filesystem label=/
> > OS type: Linux
> >
> > Peter
>
>  Could you send me your ks file? 
I've tried it with this one that I created a while ago, and with
Chris's adding a diskon bit to it.

http://pbrobinson.fedorapeople.org/olpc/olpc-4.ks

Peter