similar to: modifying initrd before high mem load

Displaying 12 results from an estimated 12 matches similar to: "modifying initrd before high mem load"

2003 Dec 27
0
2 disks boot patch
Well, with this simple patch I'm able to load initrd from a different disk. It's not finished, it's just to ask you if I'm going in the right direction... I have also some suggestion/question: - many boot sector I saw use [bp+xx] addressing to gain some bytes. Why don't you use such method? - had syslinux been tested with usb floppy? You test dl however using usb floppy dl ==
2003 Dec 27
0
FW: 2 disks boot patch
Well, with this simple patch I'm able to load initrd from a different disk. It's not finished, it's just to ask you if I'm going in the right direction... I have also some suggestion/question: - many boot sector I saw use [bp+xx] addressing to gain some bytes. Why don't you use such method? - had syslinux been tested with usb floppy? You test dl however using usb floppy dl ==
2005 Jan 10
0
Re: Problems with loading ramdisk under SYSLINUX 3.05
Petr Vandrovec wrote: > Hello, > one of FreeDOS developers pointed out (in > http://www.vmware.com/community/thread.jspa?threadID=11324&messageID=109507&#109507) > that FreeDOS does not work under VMware when using ISOLINUX 3.0x. After > looking at their ISO image I downloaded syslinux-3.05, and there seems > to be bad bug: > > You have this in kernel.inc:
2007 Jun 18
4
pxelinux bug's
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
2006 Jan 08
0
isolinux.cfg location
My point demonstrated from a snippet of isolinux.asm: ; ----------------------------------------------------------------------------- ; Begin data section ; ----------------------------------------------------------------------------- section .data boot_prompt db 'boot: ', 0 wipe_char db BS, ' ', BS, 0 err_notfound db 'Could not find kernel image: ',0 err_notkernel db
2002 Feb 26
0
syslinux timeout
Hi. I've ever wondered how nuch timeis left to timeout while waiting at the boot prompt, so I've writen this small patch to show it. This add a configuration command 'showtimeout'. If you like the patch I could improve it (for example to show the timeout in decimal because now it uses the writehex functions) Regards. -- ______ ________ / / \/ /___ ) I N T E G
2002 Jan 12
0
no echo patch
Hello, pxelinux does not has any password protection, unfortunately my Assembler skills are not that good to extend pxelinux with a global password option. Nevertheless this feature is important, because not every user should have the right to startup an installation of a machine over network. The following patch is only a dirty hack, but other might find it usefull too.(so I post it here) It
2002 Jul 11
1
help with porting patch from 1.62 to 1.75
Hello List, I have below a patch (against Syslinux-1.62), which adds a pseudo-kernel 'swap' which swaps device numbers of the boot device and the first harddisk. It was made for a system equipped with a DiskOnChip (www.msys.com) device which 'steals' the device# of teh first harddisk, This patch is used to enable the syslinux on the DoC to continue booting from the harddisk as if
2009 Jul 27
1
[PATCH] mboot using module path
Hi, We are using pxelinux at my company to test our product. And there are limitations that we have hit in the past w.r.t. the max length of a path, or the max length of a module name (in mboot.c / mboot.c32). We've used workarounds in the past, and reorganized the directory structure, but we face that problem again. Out of the 128 / FILENAME_MAX chars that can be used, 110 - 120 go to the
2006 May 29
2
sip interopability problem
Hi, I have two asterisk machines side by side both running debian sarge, one running sarge's version of asterisk (1.0.7.dfsg.1-2) and the other running the version of asterisk from www.backports.org (1:1.2.1.dfsg-2bpo1). I also have a SIP provider who is routing blocks of DID's to both machines. The sip.conf is nearly identical on both machines (the general section, and the section
2016 Feb 04
1
Bug#813678: blktap-dkms: fails to build with mainline 4.4 based kernels
Package: blktap-dkms Version: 2.0.93-0.5 Severity: important Tags: patch User: apw at ubuntu.com Usertags: origin-ubuntu xenial ubuntu-patch Mainline 4.4 switches how we detect atomicity. Follow that change when compiling against 4.4 based kernels. We are using this in Ubuntu with our latest kernels. Thanks for considering the patch. -apw -- System Information: Debian Release: stretch/sid
2009 May 26
1
Covariance calculation gives different answer than Excel (PR#13720)
Full_Name: Amos Waterland Version: 2.8.1 OS: Ubuntu Linux Submission from: (NULL) (68.175.8.163) I calculated the covariance for a small data set as follows: X <- c(1,2,3,4) Y <- c(3,3,4,3) cov(X,Y) [1] 0.1666667 But when doing the computation with pencil and paper I get: ((-1.5)*(-0.25) + (-0.5)*(-0.25) + (0.5)*(0.75) + (1.5)*(-0.25))/4 [1] 0.125 Microsoft Excel 2003 covar() also