> -----Original Message----- > From: Dag Nummedal > Subject: Re: error trying to make a new PXE image > > Arne Lovius wrote: > > Hi All, > > > > Having been using unattended for a while I thought I would > take a look at the PXE boot instead of the CD one. Having had > a play and finally got it working I would now like to make > one that has the correct server name, share name and > username and password that fit my environment. I managed to > change the dosboot one by opening up the undis3c.imz with > winimage and changing the appropriate line, but would prefer > to use the linux one so it doesn't need to reboot after > partitioning the disk. Having found the line that needs > changing in linuxboot/misc/master I thought I woud see if I > could build a new PXE boot image > > > > I did a clean debian sarge install, undated the base > install, installed cvs, unzip etc and installed the 2.6.8 > kernel image. I then copied the three 4.6 zips onto the box > into /usr/src and unzipped them into a single folder > structure. I then changed into the linuxboot direcory and did > "make download" which run and eventually completed with no > errors. I then did "make tftpboot" which ran untill it barfed > out with the following > > > > > > make[1]: Leaving directory > `/usr/src/unattended-4.6/linuxboot/linux-2.6.10' > > [ -e linux-2.6.10/arch/i386/boot/bzImage ] > > mkdir -p iso/isolinux/ ; cp -f > linux-2.6.10/arch/i386/boot/bzImage iso/isolinux/bzImage.tmp > ; mv -f iso/isolinux/bzImage.tmp iso/isolinux/bzImage > > mkdir -p tftpboot/ ; ln -f iso/isolinux/bzImage > tftpboot/bzImage.tmp ; mv -f tftpboot/bzImage.tmp tftpboot/bzImage > > tools/mknod-cpio.pl < misc/devices.txt >| devices.cpio.tmp > > /bin/sh: line 1: tools/mknod-cpio.pl: Permission denied > > make: *** [devices.cpio] Error 126 > > > > on running it again it produces this > > > > debian:/usr/src/unattended-4.6/linuxboot# make tftpboot > > tools/mknod-cpio.pl < misc/devices.txt >| devices.cpio.tmp > > /bin/sh: line 1: tools/mknod-cpio.pl: Permission denied > > make: *** [devices.cpio] Error 126 > > > > any suggestions gratefullly received > > Can't help you with the compiling, but unless you're intending to do > some real modifications to the boot image, or help with the > development, > there's no need to do it that way. > > $ file initrd > initrd: ASCII cpio archive (SVR4 with no CRC) > > As you see, the root filesystem is a simple cpio file. Simply unpack > the initrd file (with all permissions and special files), modify > etc/master and make a new initrd file.
Thanks, thats a much neater way of doing what I'm after. I've done [cpio -i -I initrd] to unpack it, modified /etc/master and then done [find . -depth -print | cpio -c -o -O initrd] which re-created initrd, but I get RAMDISK: Couldn't find initial RAM disk image starting at 0. Kernel panic - not synching: VFS: Unable to mount root fs on unknown-block I presume I need a different incantation of cpio to put it back together again > > PS! > > Actually, when I look at the error message, chmod 755 > tools/mknod-cpio.pl might be what's needed. > This had no effect, still barfed... ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ unattended-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unattended-devel
