search for: petitboot

...ay (in this case, without requiring the DHCP server to send out different lease parameters in response to the client's DHCP architecture ID). For this to be useful, my aim is that different pxe loader implementations to follow the arch-xxxx convention too; I'm proposing a similar change in petitboot: http://git.ozlabs.org/?p=petitboot;a=commitdiff;h=3bc86f99 I have a patch in development for u-boot too. In the petitboot & u-boot cases, the pxe loader code is already present on the machine, so we don't have the "which loader binary to serve" issue, only the "which con...

Am 27.02.2014 20:49, schrieb H. Peter Anvin: > I2C can be provided through an almost infinite number of controllers, > and building an I2C subsystem in Syslinux would be a good step toward > making it a fullblown operating system. Why not use linux as bootloader? Booting a (rather small) linux kernel with I?C support and either shutting down or kexecing another linux kernel (plus

...quiring the >DHCP >server to send out different lease parameters in response to the >client's DHCP architecture ID). > >For this to be useful, my aim is that different pxe loader >implementations to follow the arch-xxxx convention too; I'm proposing a >similar change in petitboot: > > http://git.ozlabs.org/?p=petitboot;a=commitdiff;h=3bc86f99 > >I have a patch in development for u-boot too. > >In the petitboot & u-boot cases, the pxe loader code is already present >on the machine, so we don't have the "which loader binary to serve" &gt...

In other words, the dhcp server has to start the client on the correct binary for it's arch and by virtue of running different bins, we can determine the most appropriate config file for the client? On Monday, February 24, 2014 9:13 AM, Gene Cumm <gene.cumm at gmail.com> wrote: On Mon, Feb 24, 2014 at 3:14 AM, Jeremy Kerr <jk at ozlabs.org> wrote: > When serving PXE config

Am 28.02.2014 12:11, schrieb Jo?o Henrique Freitas: > Based on the above I will get the Mattias idea. > > Thanks a lot. > > [1] > https://www.kernel.org/pub/linux/kernel/people/geoff/petitboot/petitboot.html Petitboot seems to "Grand" for this purpose. kexec is so simple if you put the kernel and initramfs you want to boot into the initramfs used to test your environment. Of course you also can also add some scripts, modules and binaries to the original initramfs to test y...

...machines of separate architectures (x86 PC-BIOS and PowerPC OPAL) booting from the same directory of pxe configuration files: /pxelinux.cfg/arch-0000 /pxelinux.cfg/arch-000e The arch-0000 file is being used by for the x86 machines running pxelinux, and arch-000e for the powerpc machines running petitboot. Cheers, Jeremy

...html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8a65b7fef64f6cf48889b896f6a47c0ed4503b0ec7aeed2b2515972ededcd1b7 busybox-1.15.1-21.el6_6.i686.rpm c01c8f78c58ebe47136902d76f959f2ccb5da9414e72511445711ef8983cc33d busybox-petitboot-1.15.1-21.el6_6.i686.rpm x86_64: 68189894c6f04cc2862e4c37f03d191e7eee3c2a72e412203e1b8ee93e0e9599 busybox-1.15.1-21.el6_6.x86_64.rpm 2acdc4229d7fa197fea79c072129e1b9e200694d9d08db9e3fea054f0f244eb9 busybox-petitboot-1.15.1-21.el6_6.x86_64.rpm Source: 68a8fe0335f9ba1fc6905cd66259bd9b953e5b0c8655...

....html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a0d9ecd33900791bf3c5395ebe3e80fabacddb28d41fc967955e2aa6eb1b22c4 busybox-1.15.1-15.el6.i686.rpm 3470523a6bd3559843b761857adf3557a8ce9b5147bfc62436c2109443ee7411 busybox-petitboot-1.15.1-15.el6.i686.rpm x86_64: 44ce051a279ef4d22d1cfee3a1434867f513f4a02258dace0ae6344ecd437a75 busybox-1.15.1-15.el6.x86_64.rpm 483caa0897753d352a14c3bcbc77ca7c5d3ef960994e3a9180e656de40232623 busybox-petitboot-1.15.1-15.el6.x86_64.rpm Source: 3b645023d3013390145fc09094fdf7c8cee4f811e31cf74e39...

...html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5cd60c4b0f49064e475e7600805b0b013ef08fc0037941b2bcc2d2fe76c36e59 busybox-1.15.1-16.el6_4.i686.rpm 9ca78349ef72a172300a116fabc1bf6f0ddf7ee1e0dfc72845b80ed167e5616d busybox-petitboot-1.15.1-16.el6_4.i686.rpm x86_64: 790438c19ef4228c9e1e259cae7052afdb17e007b4abd78326a0b5a095a0cd59 busybox-1.15.1-16.el6_4.x86_64.rpm f8732a07438648dadd1162137c03c3b19dee190173f1beff6ed391c6c37ca345 busybox-petitboot-1.15.1-16.el6_4.x86_64.rpm Source: 580e9713a754a2599ea0c3836f270c6e635148a1e30c...

...o it. Even thought I will need i2c to read what kind of hardware I am and then use the correct device tree to Linux do the job. So I think this job is out of scope of syslinux. Based on the above I will get the Mattias idea. Thanks a lot. [1] https://www.kernel.org/pub/linux/kernel/people/geoff/petitboot/petitboot.html On Fri, Feb 28, 2014 at 5:17 AM, Mattias Schlenker <ms at mattiasschlenker.de>wrote: > Am 27.02.2014 20:49, schrieb H. Peter Anvin: > > I2C can be provided through an almost infinite number of controllers, >> and building an I2C subsystem in Syslinux would be...

On 07/03/2014 08:44 PM, Gene Cumm wrote: > On Thu, Jul 3, 2014 at 9:13 PM, Alexander Perlis wrote: > >> I suppose we could try making an ISOLINUX CD for the local boot, which then >> uses pxechn.c32 to connect to our PXE server? > > pxechn.c32 requires a functional PXELINUX. If I understand the issue correctly, is it that pxelinux.0 does not have a network stack and

...6 > PC-BIOS and PowerPC OPAL) booting from the same directory of pxe > configuration files: > >? /pxelinux.cfg/arch-0000 >? /pxelinux.cfg/arch-000e > > The arch-0000 file is being used by for the x86 machines running > pxelinux, and arch-000e for the powerpc machines running petitboot. No, what string is used for a file name in the TFTP request for the boot binaries (ie pxelinux.0 bootia32.efi bootx64.efi)?? How do you manipulate the DHCP offer to evoke this behavior (ie a BIOS machine receiving "pxelinux.0" in the DHCP/BOOTP field "file") http://tools.ietf...

...html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5cd60c4b0f49064e475e7600805b0b013ef08fc0037941b2bcc2d2fe76c36e59 busybox-1.15.1-16.el6_4.i686.rpm 9ca78349ef72a172300a116fabc1bf6f0ddf7ee1e0dfc72845b80ed167e5616d busybox-petitboot-1.15.1-16.el6_4.i686.rpm x86_64: 790438c19ef4228c9e1e259cae7052afdb17e007b4abd78326a0b5a095a0cd59 busybox-1.15.1-16.el6_4.x86_64.rpm f8732a07438648dadd1162137c03c3b19dee190173f1beff6ed391c6c37ca345 busybox-petitboot-1.15.1-16.el6_4.x86_64.rpm Source: 580e9713a754a2599ea0c3836f270c6e635148a1e30c...

...html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8a65b7fef64f6cf48889b896f6a47c0ed4503b0ec7aeed2b2515972ededcd1b7 busybox-1.15.1-21.el6_6.i686.rpm c01c8f78c58ebe47136902d76f959f2ccb5da9414e72511445711ef8983cc33d busybox-petitboot-1.15.1-21.el6_6.i686.rpm x86_64: 68189894c6f04cc2862e4c37f03d191e7eee3c2a72e412203e1b8ee93e0e9599 busybox-1.15.1-21.el6_6.x86_64.rpm 2acdc4229d7fa197fea79c072129e1b9e200694d9d08db9e3fea054f0f244eb9 busybox-petitboot-1.15.1-21.el6_6.x86_64.rpm Source: 68a8fe0335f9ba1fc6905cd66259bd9b953e5b0c8655...

...6 > PC-BIOS and PowerPC OPAL) booting from the same directory of pxe > configuration files: > > /pxelinux.cfg/arch-0000 > /pxelinux.cfg/arch-000e > > The arch-0000 file is being used by for the x86 machines running > pxelinux, and arch-000e for the powerpc machines running petitboot. No, what string is used for a file name in the TFTP request for the boot binaries (ie pxelinux.0 bootia32.efi bootx64.efi)? How do you manipulate the DHCP offer to evoke this behavior (ie a BIOS machine receiving "pxelinux.0" in the DHCP/BOOTP field "file") http://tools.ietf...

...PAL) booting from the same directory of pxe >> configuration files: >> >> /pxelinux.cfg/arch-0000 >> /pxelinux.cfg/arch-000e >> >> The arch-0000 file is being used by for the x86 machines running >> pxelinux, and arch-000e for the powerpc machines running petitboot. > > No, what string is used for a file name in the TFTP request for the > boot binaries (ie pxelinux.0 bootia32.efi bootx64.efi)? How do you > manipulate the DHCP offer to evoke this behavior (ie a BIOS machine > receiving "pxelinux.0" in the DHCP/BOOTP field "file&q...

...2.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 9d7f52f3419db47128d6768450db38f611a4dd9c740ee7963767a890553dcd65 busybox-1.15.1-20.el6.i686.rpm 533db6f5b948e5301e5c30855b00173ee99dabf0d23db30ce36965290333ae25 busybox-petitboot-1.15.1-20.el6.i686.rpm x86_64: 9ad9350136dac8955805a0a03bed08e3d228af909dfc1d5709eebe8e263947d5 busybox-1.15.1-20.el6.x86_64.rpm 9941ce3bd9201c5eeda1d15a664d0b5a846bf2e30e16aab209809fad43718da6 busybox-petitboot-1.15.1-20.el6.x86_64.rpm Source: 0242d5834679713b91771930284c809c57cae2ddd19874065e...