similar to: 3.52-pre3 vmware 'dopathc'

Hello Peter, The attached patch contains three small (although 2 of them are fundamental :) fixes for pxelinux 1. Alignment error when more than one initramfs are loaded using initrd - the alignment of the last disk is discarded in calculations but is ALWAYS present when the loading procedure is called. As a result - the second image (cpio) is not recognized. 2. On some platforms

Hello, I would like to introduce myself as the new Google Summer of Code student for this year. My name is Andr? Ericson and I'm an undergraduate student of Computer Science in Brazil. I will be, with the help of Paulo Alcantara (pcacjr) my mentor, working on implementing Multidisk Support for the Syslinux. For those that are not familiar with the time-line of GSoC, we (students) have until

Hello, the following patches should get multidisk access working. The syntax accepted is the following: (hdx,y)/path/to/file where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk. the other accepted syntax is using MBR's 32 bits disk signature so for example: (mbr:0x12345678,2)/foo/bar would address

Searching threads back to 2013-07-01 (date of last message on thread), I've come up with the folloowing: -Needs review for inclusion: 12/26 Init cache once 11/27 efi PE header set 11/21 FSUUID for ext2 filesystem 10/15 Upgrade to Lua 5.2.2, add filesystem module and get_key binding (21) 09/23 com32: hdt: fix memory leak 10/3/12-12/16 4k sector support 10/18 MultiFS from MultiDisk 10/07 Lua

Hi, Out of pure curiosity, I was wondering, what would happen if one tries to use a regular 7200RPM (or 10K) drive as slog or L2ARC (or both)? I know these are designed with SSDs in mind, and I know it''s possible to use anything you want as cache. So would ZFS benefit from it? Would it be the same? Would it slow down? I guess it would slow things down, because it would be trying to

My compliments on the release of syslinux-5.0 and happy holidays to the entire Syslinux team.? I have a longer message in me.? Lots of curiousity about the direction of the project, but that will have to wait until I finish my first 5.0 project (*not* my first Syslinux project), which just happens to touch past problems: drive enumeration. This particular effort is on a USB flash drive, with two

Dear R-Users, I'm a master student in Mathematics and Statistics at Carleton University, Ottawa, Canada. I'm studying Clustering methods including different related algorithms. One of them is Support Vector Clustering algorithm. I was wondering whether anybody implemented this algorithm and could help me with the S-Plus or R computer code that I could use in my simulations. I would

MultiFS is a new feature that will turn the task of using multiple disks/partitions possible. By the way, it's not mainstream yet. It will only be available when the patches be released or get merged into the official tree. I'm currently working on the last details, thus it isn't yet available to the public. It was previously called Multidisk. But MultiFS seems to cover better both

On 11/14/16 02:10, SF Markus Elfring via Syslinux wrote: > Hello, > > Various boot parameters can be considered in alternative GRUB 2 configurations. > https://help.ubuntu.com/community/Grub2/ISOBoot/Examples > > I would like to clarify command line parameters like the following a bit more > for the purpose of booting ISO images better. >

Hello, Various boot parameters can be considered in alternative GRUB 2 configurations. https://help.ubuntu.com/community/Grub2/ISOBoot/Examples I would like to clarify command line parameters like the following a bit more for the purpose of booting ISO images better. http://www.syslinux.org/wiki/index.php?title=MEMDISK#-_Passing_ISO_parameter_to_the_kernel 1. bootfrom 2. findiso 3.

The ZFS crew might be better to answer this question. (CC''d here) --jc William Yang wrote: > I am having issues creating a zpool using entire disks with a fibre > channel array. The array is a Dell PowerVault 660F. > When I run "zpool create bottlecap c6t21800080E512C872d14 > c6t21800080E512C872d15", I get the following error: > invalid vdev

Hello List, We just migrated from a PPC Xserve to an Intel Xserve. I used "rsync" to bring everyone's home directories over, and in the back of my mind wondered about how it would handle the binary index files... only one way to find out! :) Once I tried to login to IMAP, I got the following results: May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): Rebuilding index file

Hello everyone, I have just released SYSLINUX 3.52, being functionally identical to 3.52-pre10. Changes in 3.52: * Handle capitalized F-key commands in the menu system. * Fix padding error when loading multiple ramdisks. * Workaround for VMware crashing when trying to print a message during early kernel boot (does not seem to work, consider deleting.)

From: Raphael S. Carvalho <raphael.scarv at gmail.com> This patch finishes the MultiFS support. init_multifs gets called in the main (startup) function of ldlinux.c32, so MultiFS will be initialized automatically. init_multifs calls enable_multifs (lives in the core) to hook get_fs_info. Subsequent accesses will callback the get_fs_info living in ldlinux.c32. Signed-off-by: Raphael S.

Hello, While attempting to build syslinux-3.52-pre6 for testing (my SCSI machine won't boot from CD-ROM with 3.51) I hit this problem: nasm -O99 -f bin -DDATE_STR="'3.52-pre6'" -DHEXDATE="0x46c22b21" \ -DMAP=pxelinux.map -l pxelinux.lsr -o pxelinux.bin pxelinux.asm pxelinux.asm:1206: error: short jump is out of range nasm -version NASM version

Hi I am having problems loading bcdw (http://bootcd.narod.ru) from the isolinux bootloader. I use this to load the acronis programs. It worked fine up till version 3.51 but does not work anymore with 3.52. Here is the code to load the second bootmanager label l kernel /bcdw/bcdwboot.bin Any insights to what might be wrong here? With 3.52 I get Error! Cannot load

Thanks to Dell for sending me a specimen system, and of course, rPath, my employer, for letting me spend the several days it took to chase this one down. There is a memory-overwrite bug where part of the BIOS data area gets overwritten by certain comboot calls, including some used by the simple menu system. Anyone who has had problems where booting from the prompt works but the menu system

I have installed various pc with the version Syslinux 3.31 without particular problems. Trying new 3.52 or 3.36 the PC does not leave more giving the message Returning to the previous version all it resumes to work correctly. What I have mistaken? Thanks. _____________________________________________________ Fabrizio Guerriero EDP Manager C.C.M. Coop.Cartai Modenese Soc.coop. Via F.

I just got the following message on the syslinux mailing list: > 2. On some platforms (vmware for example :), READING from the video memory > in the 32bit mode is impossible (causes an exeption). Taking in to account > that the scroll function in ilinux/arch/i386/boot/compressed/misc.c > works using a memcpy of the video memory, when the linux bootsector is given >

I just got the following message on the syslinux mailing list: > 2. On some platforms (vmware for example :), READING from the video memory > in the 32bit mode is impossible (causes an exeption). Taking in to account > that the scroll function in ilinux/arch/i386/boot/compressed/misc.c > works using a memcpy of the video memory, when the linux bootsector is given >