similar to: Security issues with SYSLINUX 2.01

Displaying 20 results from an estimated 2000 matches similar to: "Security issues with SYSLINUX 2.01"

2002 Jun 23
1
Using MTOOLS in place of loopback mounting
I am trying to build a distribution without having to be root. The SYSLINUX installer typically needs root to do loopback mounting, but if you have MTOOLS, you can use that instead. This seems to work so far: #!/bin/sh # A minimal replacement for /usr/bin/syslinux; assumes that ldlinux.sys # and ldlinux.bss are available in the current directory. You must # specify locations of mkdosfs and
2002 Jul 04
1
New user problem
Peter, I'm a new user of Linux trying to use the SYSLINUX boot loader to create a Linux system. I'm doing it on a PC with WIN98 installed, and I prefer using a dual boot system. I got through as far as creating a semi-bootable floppy. The problem I'm getting states "could not find kernel image: Linux." However, I do get the "boot:" prompt as well (I just
2002 Jul 17
1
Question on "root pivot" function
Seth, Thank you for your reply. I'm sorry to bother with this, but what is the "root pivot" function and where can I find doc's on it. From what I understand from your email the system would basically boot twice. Once from a stripped kernel on the floppy disk to mount the CD, and then after the CD is mounted it would reboot with the kernel and initial randisk found on the
2003 Mar 14
2
isolinux + cloop
Hi. I am trying to build a bootable linux CD using isolinux and a cloop image. I am a bit lost right now. What I have done is built a custom distro on a seperate partition on my hard drive. I can boot to it with Grub no problem. I've added the ioslinux directory with isolinux.bin, isolinux.cfg, a kernel (with initrd, loopback, iso support), and an initrd file. My next mission is to some
2003 Jan 31
2
isolinux.cfg - DISPLAY command - screen pause?
Hi, is there an option to have the DISPLAY command issue a pause after each screen full of information? I've been searching for a way to have users to agree to (or at least be able to read ) the GPL license. "by issueing a command other than F2 you agree that you are bound to the terms of the GNU Public License that is used on this FreeDOS beta9 cdrom. You can read the license terms by
2015 Jan 06
3
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
On 01/06/2015 08:16 AM, H. Peter Anvin wrote: > On 01/05/2015 04:14 PM, Robert Yang wrote: >> >> On 01/06/2015 08:04 AM, H. Peter Anvin wrote: >>> On 01/01/2015 09:05 PM, Robert Yang wrote: >>>> Hello, >>>> >>>> Happy New Year! >>>> >>>> These patches make syslinux/linux support ext2/3/4, and it doesn't
2015 Nov 10
2
[PATCH] mtools: Remove local xpread/xpwrite, use ones from syslxcom
From: Nicolas Cornu <ncornu at aldebaran.com> --- mtools/Makefile | 1 + mtools/syslinux.c | 59 +------------------------------------------------------ 2 files changed, 2 insertions(+), 58 deletions(-) diff --git a/mtools/Makefile b/mtools/Makefile index 0d0b1b2..c980420 100755 --- a/mtools/Makefile +++ b/mtools/Makefile @@ -9,6 +9,7 @@ SRCS = syslinux.c \
2015 Jan 08
2
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
> On 01/06/2015 02:28 PM, Robert Yang wrote: > > > > > > On 01/07/2015 03:47 AM, H. Peter Anvin wrote: > >> On 01/05/2015 07:20 PM, Robert Yang wrote: > >>> > >>> Hello, > >>> > >>> After more investigations, I'm a little worried about add the extX > >>> support > >>> to mtools/syslinux:
2015 Jan 06
2
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
On 01/07/2015 03:47 AM, H. Peter Anvin wrote: > On 01/05/2015 07:20 PM, Robert Yang wrote: >> >> Hello, >> >> After more investigations, I'm a little worried about add the extX support >> to mtools/syslinux: >> 1) Its name is mtools/syslinux, can't express the libext2fs. > > Renaming it is not a problem. Do you have any suggestion about the new
2015 Jan 06
0
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
On 01/05/2015 07:20 PM, Robert Yang wrote: > > Hello, > > After more investigations, I'm a little worried about add the extX support > to mtools/syslinux: > 1) Its name is mtools/syslinux, can't express the libext2fs. Renaming it is not a problem. > 2) The mtools/syslinux isn't fully functioned, for example, as the code > shows: > if (opt.sectors ||
2015 Jan 06
2
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
On 01/06/2015 08:04 AM, H. Peter Anvin wrote: > On 01/01/2015 09:05 PM, Robert Yang wrote: >> Hello, >> >> Happy New Year! >> >> These patches make syslinux/linux support ext2/3/4, and it doesn't >> require the root privilege, I'd like to add a separate e2fs/syslinux, if >> that is more appropriate, it should be easy to do that. >>
2015 Jan 06
0
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
On 01/05/2015 04:14 PM, Robert Yang wrote: > > On 01/06/2015 08:04 AM, H. Peter Anvin wrote: >> On 01/01/2015 09:05 PM, Robert Yang wrote: >>> Hello, >>> >>> Happy New Year! >>> >>> These patches make syslinux/linux support ext2/3/4, and it doesn't >>> require the root privilege, I'd like to add a separate e2fs/syslinux, if
2014 Apr 16
2
syslinux fails to make a bootable USB stick in Slackware64-14.1 installer
On 16/04/2014 23:46, H. Peter Anvin wrote: > On 04/16/2014 02:15 PM, Didier Spaier wrote: >> Running "syslinux -s /dev/dsb" during installation of Slackware64-14.1 >> (to make a bootable USB stick) fails like this: >> >> Error converting to codepage 850 Invalid argument >> Cannot initialize 'S:' >> Bad target s:/ldlinux.sys >>
2012 Oct 16
3
[PATCH] minor documentation updates (4.06-pre14)
syslinux.txt: syslinux binary is in "linux" directory menu.txt: menu.c32 and vesamenu.c32 are in com32/menu directory --- doc/menu.txt | 2 +- doc/syslinux.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/menu.txt b/doc/menu.txt index 620527e..8a999cd 100644 --- a/doc/menu.txt +++ b/doc/menu.txt @@ -18,7 +18,7 @@ See menu/README for more
2015 Jan 07
0
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
On 01/06/2015 02:28 PM, Robert Yang wrote: > > > On 01/07/2015 03:47 AM, H. Peter Anvin wrote: >> On 01/05/2015 07:20 PM, Robert Yang wrote: >>> >>> Hello, >>> >>> After more investigations, I'm a little worried about add the extX >>> support >>> to mtools/syslinux: >>> 1) Its name is mtools/syslinux, can't
2014 Dec 25
0
[PATCH 0/8] extlinux: support unmounted ext2/3/4 filesystem
> > > On 12/25/2014 04:33 AM, H. Peter Anvin wrote: > > On 12/24/2014 12:16 AM, Robert Yang wrote: > >> Hello syslinux, > >> > >> Merry Christmas! These patches will make extlinux work with umounted > >> ext2/3/4 filesystem, for example: > >> > >> $ extlinux -i /dev/sdXN > >> or > >> $ extlinux -i file_block
2014 Dec 25
2
[PATCH 0/8] extlinux: support unmounted ext2/3/4 filesystem
On 12/25/2014 01:43 PM, Ady wrote: > >> >> >> On 12/25/2014 04:33 AM, H. Peter Anvin wrote: >>> On 12/24/2014 12:16 AM, Robert Yang wrote: >>>> Hello syslinux, >>>> >>>> Merry Christmas! These patches will make extlinux work with umounted >>>> ext2/3/4 filesystem, for example: >>>> >>>> $ extlinux
2010 Jul 27
2
Usage output of Syslinux installers is not consequent
Why doesn't the Windows Syslinux installer show: --offset and --directory too (I know it is not supported)? Because the Linux versions show the Windows/dos specific commands: --mbr --active and --force I didn't check the DOS version. If all options will be displayed unconditionally for all installers, it might be a good idea to add: --offset -t Offset of the file system on the
2015 Jan 06
0
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
On 01/01/2015 09:05 PM, Robert Yang wrote: > Hello, > > Happy New Year! > > These patches make syslinux/linux support ext2/3/4, and it doesn't > require the root privilege, I'd like to add a separate e2fs/syslinux, if > that is more appropriate, it should be easy to do that. > > I put these patches on github so that you can easily get them in case >
2015 Jan 07
1
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
> On 01/05/2015 07:20 PM, Robert Yang wrote: > > > > Hello, > > > > After more investigations, I'm a little worried about add the extX support > > to mtools/syslinux: > > 1) Its name is mtools/syslinux, can't express the libext2fs. > > Renaming it is not a problem. >From users' perspective (starting from documentation, scripts,