similar to: [PATCH] Correct outdated and incomplete mailing list info

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> --- syslinux accepts a --directory (or -d) option. As far as I can see this option only affects the installation location of the ldlinux.sys file. (It also affects the boot sector that syslinux generates, but that is not something user visible.) Currently man/syslinux.1 talks about the "SYSLINUX control files". That is not entirely

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

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

Hi, I just noticed that the keytab-lilo utility included with SYSLINUX isn't up to date. It *is* a problem since the old version isn't compatible with current distributions like Debian ou Ubuntu (for example). Two options are offered to those who would like to use keytab-lilo in order to generate a file compatible with the KBDMAP directive : - use an up to date version of keytab-lilo

Hi, Round(0.55,1)=0.5 Round(2.55,1)=2.6 Can this be right? Thanks, Ed [[alternative HTML version deleted]]

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

On 01/31/2015 11:28 PM, Ferenc Wagner wrote: > I for one don't expect insults after such a start. Please share your > thoughts, constructive feedback is always useful. Even if there may be > good reasons for some things being as they are. Ok Feri, of course there is no reason for insults, but still, some groups take offense at any criticism. If I sound bitchy it is only as

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

Do you guys like feedback from people who just gavesyslinux a first try? I have a few bitches if you do ;-)

https://bugzilla.mindrot.org/show_bug.cgi?id=2216 Bug ID: 2216 Summary: allow forwarding a different socket than SSH_AUTH_SOCK Product: Portable OpenSSH Version: 6.5p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs

Hello, there seems to be an odd behaviour regarding the CD-Rom drives in wine depending on whether you run a precompiled version (in my case a Debian package) or compile wine for yourself (same version). Background is that there seems to be a regression in wine which I wanted to debug. The regression is in a game which checks for the CD first and then shows an intro and a menu (which has

Hello We have a problem with our Windows 10 Clients. Installed on a SLES12 Server is samba v4.4 I can bind the clients to the domain without any problem. Afterwards I want to login in the domain, I get the error, no logonserver available I can change in the smb conf max protocol to NT1 -> now it is possible to login with user xxx in the domain We don't want to use our samba server