similar to: Booting FreeBSD

Displaying 20 results from an estimated 3000 matches similar to: "Booting FreeBSD"

2013 Jul 31
3
Booting FreeBSD
On 01/08/2013, at 24:37, Gene Cumm <gene.cumm at gmail.com> wrote: > On Wed, Jul 31, 2013 at 7:36 AM, Daniel O'Connor <doconnor at gsoft.com.au> wrote: >> Hi, >> I am trying to create a hybrid ISO image for FreeBSD 9.2 using syslinux 6.01 and isohybrid.pl I found at http://www.overclockix.com/sources/isohybrid.pl (I know there is a C version in syslinux but I
2013 Jul 31
0
Booting FreeBSD
Op 2013-07-31 om 21:06 schreef Daniel O'Connor: > Hi, > I am trying to create a hybrid ISO image for FreeBSD > 9.2 using syslinux 6.01 and isohybrid.pl I found at > http://www.overclockix.com/sources/isohybrid.pl (I know there is a > C version in syslinux but I haven't been able to build it yet due to > the UUID library being different to the one in FreeBSD). > >
2013 Jul 31
0
Booting FreeBSD
On Wed, Jul 31, 2013 at 7:36 AM, Daniel O'Connor <doconnor at gsoft.com.au> wrote: > Hi, > I am trying to create a hybrid ISO image for FreeBSD 9.2 using syslinux 6.01 and isohybrid.pl I found at http://www.overclockix.com/sources/isohybrid.pl (I know there is a C version in syslinux but I haven't been able to build it yet due to the UUID library being different to the one in
2013 Aug 01
0
Booting FreeBSD
On Wed, Jul 31, 2013 at 7:40 PM, Daniel O'Connor <doconnor at gsoft.com.au> wrote: > > On 01/08/2013, at 24:37, Gene Cumm <gene.cumm at gmail.com> wrote: >> The Perl version should also be in the source tree >> (utils/isohybrid.in) and built in the archives (util/isohybrid.pl) >> which I'd recommend using everything from the 6.01 binary/source >>
2016 Mar 02
3
Module Versioning
On 02/24/16 20:45, Shao Miller via Syslinux wrote: > On 2/24/2016 22:55, Shao Miller wrote: >> Suppose...: >> - For non-releases: "git" + We take the first 6 chars of git commit >> - For releases: "ver" + major + "." + minor >> - For tar-balls: Something clever, maybe involving the date >> >> ...that we embed such a version in
2009 May 04
2
SYSLINUX 3.80 released
3.80 is a bug fix and internal restructuring release. In particular, the entire shuffler subsystem has been rewritten largely from scratch, as has the Multiboot module. Changes in 3.80: * New shuffler mechanism and API. * Rewritten mboot.c32 module. * The syslinux_boot_linux() function has been simplified. * Don't hang trying to boot a "menu
2014 May 12
2
[PATCH] isohybrid: fix overflow on 32 bit system
On 2014?05?12? 10:49, H. Peter Anvin wrote: > On 05/11/2014 06:56 PM, Kai Kang wrote: >> When call isohybrid with option '-u', it overflows on a 32 bits host. It >> seeks to 512 bytes before the end of the image to install gpt header. If >> the size of image is larger than LONG_MAX, it overflows fseek() and >> cause error: >> >> isohybrid:
2014 May 13
2
[PATCH] isohybrid: fix overflow on 32 bit system
On 2014?05?12? 22:38, H. Peter Anvin wrote: > That is because it needs to use fseeko() and use off_t. Do you mean it does need a patch for isohybrid.c. And the patch looks like: #if _FILE_OFFSET_BITS == 64 fseeko(...) #else fseek(...) Regards, Kai > > On May 11, 2014 11:53:17 PM PDT, Kang Kai <Kai.Kang at windriver.com> wrote: >> On 2014?05?12? 10:49, H. Peter
2014 Feb 01
5
xorriso or genisoimage syntax assistance
Could someone help me get the syntax for `genisoimage' and/or `xorriso' correct? Apparently it is not in many linux distros so below my little HOWTO shows how to compile it. ( which adds tons of crap that can go wrong) mkdir -p ISO_root/isolinux cp /usr/lib/syslinux/[i,m,v]* ISO_root/isolinux cat > ISO_root/isolinux/isolinux.cfg << EOF UI menu.c32 label isolinuxtests EOF # Most
2014 May 12
4
[PATCH] isohybrid: fix overflow on 32 bit system
When call isohybrid with option '-u', it overflows on a 32 bits host. It seeks to 512 bytes before the end of the image to install gpt header. If the size of image is larger than LONG_MAX, it overflows fseek() and cause error: isohybrid: wrlinux-image-x86-64-20140505110100.iso: seek error - 8: Invalid argument Check the offset and call fseek() multi-times if offset is too large.
2015 Oct 13
3
com32/mboot/map.c: removed trailing spaces
On Sat, Oct 10, 2015 at 03:10:26PM +0300, Ady via Syslinux wrote: > From: Geert Stappers <stappers at nero.gpm.stappers.nl> > > > > com32/mboot/map.c: removed trailing spaces > > > > They were introduced by the patch for ELF64 support. > > > IMHO, the trivial trailing-space cleanup could be included in the same > commit too, instead of adding an
2009 Sep 22
1
mboot.c32 and FreeBSD
Hi, I'm trying to get FreeBSD 7.2 booting using mboot module from syslinux 3.82. Unfortunately it doesn't seem to work. Here is my pxelinux config: === 8< === label freebsd72-i386-mboot kernel mboot.c32 append /kernels/freebsd/7.2/i386/boot/kernel/kernel single --- /kernels/freebsd/7.2/i386/boot/mfsroot === 8< === Here is the error message I get on boot: === 8< ===
2007 Apr 30
3
disk image creation, step by step
Hi, I am aware that it is impossible to netboot ISO files through pxelinux/memdisk and that there are multiple reasons for not even attempting it (like the operating system which will try to access a physical optical drive through its own drivers anyway, BIOS issues etc.). When people ask questions regarding ISO support in pxelinux/memdisk, they're mostly told to convert the ISO into a
2007 Jun 27
5
FreeBSD-6.2 and pxelinx
Hi i want to add the FreeBSD 6.2 release to our installserver according to the manual http://syslinux.zytor.com/archives/2007-April/008420.html But if I type FreeBSD-6.2 at the pxelinux boot prompt the created image load but nothing happens. ?boot: FreeBSD-6.2 Loading memdisk.... Loading
2013 Nov 23
4
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
It occured with every BIOS system I tested on (none of them Dell): 1. HP G62 laptop (i3) 2. Samsung RV520 (i3) Don't know what system Philip Muller uses; have copied him in as he has far more technical knowledge than I do. Syslinux tested from Arch and Manjaro (an Arch derivative). Basically found then when creating latest ISO images. I may be missing something as well about the FMs. Just
2013 Aug 07
1
FreeBSD9.2-RC1 bootonly network installation fetch error (snapshots vs releases)
Hello :-) I am installing the 9.2-RC1 bootonly iso which wants to download stuff from snapshots while it is in releases directory: Installer wants to get 9.2-RC1 stuff from here (where it is missing): ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/i386/ While the stuff is at: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/9.2-RC1/ Please fix :-) Best regards :-) Tomek -- CeDeROM,
2013 Dec 16
1
FreeBSD 10.0-RC2 Now Available
The second RC build of the 10.0-RELEASE release cycle is now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and sparc64 architectures. The image checksums follow at the end of this email. ISO images and, for architectures that support it, the memory stick images are available here (or any of the FreeBSD mirror sites):
2011 Nov 09
0
[LLVMdev] LLVM JIT on a Baremetal x86 Machine !!!
Hi James, Thanks again for bearing with me, you have been very helpful. I have got the problem fixed. In fact I needed to override the 'LSeek' implementation of SpecialFile in SpecialModule class as well. The log for the working example is attached, just as a reference. Now one more thing, when the build system creates the ISO9660 CD-ROM Image, it executes the following commands:
2014 Feb 02
2
xorriso or genisoimage syntax assistance
On Sun, Feb 2, 2014 at 6:27 AM, Mattias Schlenker <ms at mattiasschlenker.de>wrote: [...] > Build a recent xorriso - this can be run from the build directory without > installing (thanks, Thomas!): > > ./configure --enable-static > > Thank you for pointing this out, I tried desperately to statically compile `mkisofs' yesterday, to no avail. To hear that xorriso is
2011 Nov 08
2
[LLVMdev] LLVM JIT on a Baremetal x86 Machine !!!
Hi, First question: "/module" is mapped to a special file that reads a kernel module passed in by the bootloader. Much like GRUB, kiwi's bootloader loads a kernel and can load one or more extra files into memory. These are passed to the kernel. The horizon kernel expects one file, which it makes accessible at "/module". This should be set up to be whatever you set