On Fri, 2011-01-21 at 17:24 -0500, Martin Langhoff wrote:
On Thu, Jan 20, 2011 at 3:45 PM, Martin Langhoff
martin.langh...@gmail.com wrote:
While not as modular and elegant as olpc-os-builder, we do have a
collection of tools and configs that, operated correctly, build XS
isos for installation. This can be useful to prepare a custom
auto-intalling iso with preconfigured settings.
http://dev.laptop.org/git/projects/olpc-xs-builder
The current scripts (just committed) are based on pungi and a comps
file. This is _trivial_ compared to the overcomplicated mess we had
before.
It wasn't that bad.
Perhaps it's experience in wrestling with revisor and earlier versions
of pungi. Maybe it's Jerry's better-way-to-do-it recommendations that
have finally reached an active neuron in my skull.
Yea, the comps file is far easier to play with.
The key trick is splitting the Pungi process; stop it before it makes
the ISO -- edit/overwrite the bits we want, and then make the ISO. See
http://dev.laptop.org/git/projects/olpc-xs-builder/commit/?id=9093a4c380d0394c957f547c593a28db68f5b512
Better take upgradeany out of the install part of the isolinux.cfg file.
The package definition on both ks files is going to get slimmed down
to @OLPC-XS methinks.
Jerry,
- is there anything else we should whack before ISOing the ISO? I
just reviewed the mkslim script but it's unclear to me what was
getting cut out.
I was just using stage2/install.img file and leaving the rest.
- is there anything we want to include so that turning that ISO into
a bootable/installable USB is easier?
I was using --driveorder=sda,sdb with F9, that seemed to fix the issue,
there might of been some confusion on which mbr to write to. It can't be
the boot drive that started the install. When playing with F11 I left
the auto partitioning out.
cheers,
m
I'll give it a spin on the weekend,
Jerry
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel
