Re: Building custom images

Chris Gianelloni <[email protected]> Thu, 17 Nov 2005 07:57:11 -0500
Newsgroups gmane.linux.pxes.devel
Organization Gentoo Linux
Message-ID <[email protected]>
--=-dHSIPEDuci4EDIMapTYh
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2005-11-17 at 11:42 +1000, Dan wrote:
> On Thu, November 17, 2005 12:20 am, Chris Gianelloni wrote:
> > On Wed, 2005-11-16 at 17:21 +1000, Dan wrote:
> >
> >> 1) pxesconfig gives "No space left on device" errors when it tries to
> >> make the ram disk.
> >
> > Try increasing the default size of the ramdisk in the kernel's config.
> >
>=20
> OK will do.
>=20
> >
> >> 2) I had to view the source code to pxesconfig to find the appropriate
> >> command line option to increase the ram disk size
> >
> > Perhaps we need a nice --help?
> >
>=20
> That would be nice, but on my system --help results in a stack trace? The=
n
> pxesconfig exits.
>=20
> Thanks for you tip, but i do actually know about --help.

Ehh... No.  I said that perhaps we *need* one.  I wasn't being facetious
or anything.

> >
> >> 3) pxesconfig is forcing me to specify --fssizeinc=3D16384 to get an
> >> image. However, on inspecting the image it appears I have over 17MB of
> >> free space.
> >
> > I would bet this is due to the kernel config, as stated above.
> >
> >
> >> 4) When i boot this image, depmod complains about various files from
> >> /lib/modules/`uname -r`/ (ie modules.ieee1394map, modules.pnpbiosmap
> >> modules.dep (Not ELF file, cannot read ELF header, cannot open for
> >> writing)
> >
> > cd /opt/pxes-1.0/stock/arch/i586/modules/lib/modules/2.6.10-2pxes.2 (or
> > whatever your kernel directory happens to be based on your custom kerne=
l
> > image)
> >
> > I use the following script, called modules-create, from within this
> > directory.
> >
> > #!/bin/bash
> > MODDIR=3D"../../../tmp"
> >
> >
> > for i in modules.dep modules.generic_string modules.ieee1394map
> > modules.isapnpmap modules.parportmap modules.pcimap modules.pnpbiosmap
> > modules.usbmap do rm $i ln -sf $MODDIR/$i $i done
> >
> > The main thing is that these files are symlinks to the /tmp directory o=
n
> > the image, as PXES generates these files at boot.
> >
>=20
> Right. I will give this a shot.
>=20
> Seems like a crucial step.
>=20
> >> 5) Because of errors in 4) networking does not load!
> >>
> >>
> >> After following these instructions:
> >>
> >>
> >> http://www.2x.com/pxes/howtos/Customizingkernelhowto.htm
> >>
> >>
> >> It would appear something needs to be done with at least modules.dep,
> >> but as far as i can tell, there is zero documention describing this pa=
rt
> >> of building a pxes image!
> >>
> >> Can anyone shed any light on what *really* needs to happen during a
> >> pxes build?
> >>
> >> FYI I am using the latest releases of pxesconfig and pxes-base-i586
> >> rpms from the new pxes site.

--=20
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

--=-dHSIPEDuci4EDIMapTYh
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBDfH4nkT4lNIS36YERAicGAJ9OdlUFS3Ot2gpTi5e+eCM0CmMl+wCgu/MT
aIrZg4AMJQvcv3SfZJydIWo=
=bH/w
-----END PGP SIGNATURE-----

--=-dHSIPEDuci4EDIMapTYh--



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click