similar to: [PATCH] Describe the --directory option more precisely

LDLINUX.SYS uses a working directory. The documentation seems to improve if that fact is made explicit. So the working directory is added to the documentation (with a bit of vagueness and possibly not entirely correct, to keep it readable). Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- This is a result of today's discussion of a previous patch ("Describe the --directory

ldlinux.sys uses a working directory. The documentation seems to improve if that fact is made explicit. So the working directory is added to the documentation (with a bit of vagueness and possibly not entirely correct, to keep it readable). While we're at it, also convert the name ldlinus.sys to lowercase everywhere, even if it's clear its name is used in a DOS context. Signed-off-by:

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- man/extlinux.1 | 6 +++--- man/syslinux.1 | 10 +++------- 2 files changed, 6 insertions(+), 10 deletions(-) diff --git a/man/extlinux.1 b/man/extlinux.1 index 3192122..62bf3b1 100644 --- a/man/extlinux.1 +++ b/man/extlinux.1 @@ -57,8 +57,8 @@ about your system and your BIOS; the vast majority of all problems reported turn out to

virtio_balloon.h exports "u16" and "u64" to userspace. Use "__u16" and "__u64" instead. Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) Tested with a kernel build. 1) Both types are used in this header for quite some time now. So is my patch flawed or doesn't userspace actually use virtio_balloon.h? include/uapi/linux/virtio_balloon.h

virtio_balloon.h exports "u16" and "u64" to userspace. Use "__u16" and "__u64" instead. Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) Tested with a kernel build. 1) Both types are used in this header for quite some time now. So is my patch flawed or doesn't userspace actually use virtio_balloon.h? include/uapi/linux/virtio_balloon.h

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- doc/comboot.txt | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/comboot.txt b/doc/comboot.txt index 4b4b880..04d5deb 100644 --- a/doc/comboot.txt +++ b/doc/comboot.txt @@ -986,27 +986,27 @@ AX=0024h [3.80] Cleanup, shuffle and boot, raw version ++++ 32-BIT ONLY API CALLS ++++ -void

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- doc/comboot.txt | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/comboot.txt b/doc/comboot.txt index 4b4b880..04d5deb 100644 --- a/doc/comboot.txt +++ b/doc/comboot.txt @@ -986,27 +986,27 @@ AX=0024h [3.80] Cleanup, shuffle and boot, raw version ++++ 32-BIT ONLY API CALLS ++++ -void

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) If I build syslinux on a system without mingw a (successful) build will end with: ls: cannot access win32/syslinux.exe: No such file or directory ls: cannot access win64/syslinux64.exe: No such file or directory [...] make: [all] Error 2 (ignored) Ie, it ends with an ignored error. That's confusing (and a bit

Compiling xenbus_xs.o triggers this GCC warning: drivers/xen/xenbus/xenbus_xs.c:628:13: warning: function declaration isn?t a prototype [-Wstrict-prototypes] Add the obvious and trivial fix. While we're touching this function add some equally obvious and trivial whitespace fixes. Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) Triggered by compiling v3.7-rc1 using

Compiling xenbus_xs.o triggers this GCC warning: drivers/xen/xenbus/xenbus_xs.c:628:13: warning: function declaration isn?t a prototype [-Wstrict-prototypes] Add the obvious and trivial fix. While we're touching this function add some equally obvious and trivial whitespace fixes. Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) Triggered by compiling v3.7-rc1 using

Dear Syslinux bootloader list, I'm running into a few issues concerning Syslinux modules here, hoping you can answer one or more of the following questions: * Where's "ifmemdsk.c32" ? 4.05, 4.06pre1 and latest 4.10pre seem to lack it. Only the "ifmemdsk.c" file, which is likely sourcecode. Not seeing any "ifmemdsk.cbt" legacy comboot module. * Do COM32

Allow the grub loader to (optionally) support using a GRUB menu file. For example chain fs grub=stage2,grub.conf will load GRUB's stage2 and pass the (absolute) path to the file "grub.conf" in the Syslinux filesystem to GRUB's stage2. The path is passed to stage2 in GRUB's device/partition syntax (eg, "(hd0,1)/foo"). Note that we don't check whether the

virtio_console.h exports "u32" to userspace. Use "__u32" instead. Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) Tested with a kernel build. 1) Again. I'm guessing userspace doesn't use VIRTIO_CONSOLE_BAD_ID. include/uapi/linux/virtio_console.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/uapi/linux/virtio_console.h

virtio_console.h exports "u32" to userspace. Use "__u32" instead. Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) Tested with a kernel build. 1) Again. I'm guessing userspace doesn't use VIRTIO_CONSOLE_BAD_ID. include/uapi/linux/virtio_console.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/uapi/linux/virtio_console.h

This adds (basic) support for GRUB stage2 image files. Loading a stage2 image will probably give you a GRUB prompt, with GRUB's "root" set at "(hd0)" (ie, entire first disk). Maybe the "root" will differ in less common setups. (One can of course select another disk and/or partition with GRUB's "root" command.) This has only been tested with version

On Mon, 2014-12-22 at 14:37 +0100, Paul Bolle wrote: > On Mon, 2014-12-22 at 13:01 +0000, Sid Boyce wrote: > > CHK kernel/config_data.h > > CC [M] drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o > > drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c: In function > > ‘nvd0_dmaobj_bind’: > > drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: error:

0) The Kconfig symbol XEN_PRIVILEGED_GUEST got added to the mainline Linux repository in v2.6.37. It has never been used. It has always been a nop. 1) Its Kconfig entry is preceded with this comment: # Dummy symbol since people have come to rely on the PRIVILEGED_GUEST # name in tools. What does that mean? 2) On a related note: can anyone please explain commit

0) The Kconfig symbol XEN_PRIVILEGED_GUEST got added to the mainline Linux repository in v2.6.37. It has never been used. It has always been a nop. 1) Its Kconfig entry is preceded with this comment: # Dummy symbol since people have come to rely on the PRIVILEGED_GUEST # name in tools. What does that mean? 2) On a related note: can anyone please explain commit

Add man/mkfs.btrfs.8.in Kept the name with the name in, so that further processing such as BUILD_DATE BUILD_VERSION etc. could be included later. All man pages included in the man directory to avoid file cluttering. Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.de> --- man/mkfs.btrfs.8.in | 63 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 63 insertions(+), 0

On 22/12/14 13:54, Paul Bolle wrote: > On Mon, 2014-12-22 at 14:37 +0100, Paul Bolle wrote: >> On Mon, 2014-12-22 at 13:01 +0000, Sid Boyce wrote: >>> CHK kernel/config_data.h >>> CC [M] drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o >>> drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c: In function >>> ‘nvd0_dmaobj_bind’: