Displaying 20 results from an estimated 500 matches similar to: "[PATCH 0/9] linux/syslinux: support ext2/3/4 device"
2014 Dec 24
14
[PATCH 0/8] extlinux: support unmounted ext2/3/4 filesystem
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
Also it can work with something like:
$ extlinux /dev/sdXN --reset-adv
or
$ extlinux file_block --reset-adv
We don't use a new option (I planed to use "-d" but it is already in
use), it will check whether the
2012 Sep 10
19
Initial support for sector size >512
This set of patches add some support for sector size >512.
Currently it fixes extlinux, MBR for GPT and ext partitions.
Other code is unaffected.
This set of patches has been tested on a read Dell machine running a beta
firmware.
2011 Jul 16
1
crash in extlinux/main
Hi,
I found a bug in extlinux/main.c. Writing a bootloader on a file mounted via
/dev/mapper in Lunix it crashed on me with a segment fault.
The bug is here:
if (!ioctl(devfd, HDIO_GETGEO, &geo)) {
Since we are already called with geo as a pointer the & is wrong as the
pointer itself will be overwritten.
This works:
int get_geometry(int devfd, uint64_t totalbytes, struct
2012 Aug 02
0
[PATCH 1/3] ALPHA: make sector size dynamic in extlinux
This is part of some patches to support sectors > 512.
Currently I'm able to boot a Ubuntu kernel but seems that mboot is not working for some reason.
This patch try to fix first stage of extlinux bootloader but have some problems with ADV
Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com>
---
dos/syslinux.c | 2 +-
extlinux/main.c | 36
2002 Feb 06
2
SFTP Status Bar..
This is the LAST version I plan on doing.. If I hear no feed back good
or bad. Then I'll assume I've wasted my time on a feature that people
whine about but don't care to try. This is against 3.0.2pX so it
should be VERY easy for anyone to test.
- Ben
diff -ur openssh-3.0.2p1/misc.c openssh/misc.c
--- openssh-3.0.2p1/misc.c Tue Jul 3 23:46:58 2001
+++ openssh/misc.c Wed Feb 6
2014 Sep 18
4
[PATCH] remove _BSD_SOURCE definition
The _BSD_SOURCE was deprecated since glibc-2.20. _DEFAULT_SOURCE can be
used instead of _BSD_SOURCE. However, there is no need to include
_BSD_SOURCE because the sources only have inline functions and calls
memcmp/cpy functions.
Signed-off-by: Chanho Park <chanho61.park at samsung.com>
---
dos/getsetsl.c | 1 -
libinstaller/fs.c | 1 -
libinstaller/syslxmod.c | 1 -
3 files
2011 Apr 15
0
[GIT PULL] syslinux command-line
The following changes since commit 868c474546ba68e9e448734e1833f873fd50ec0a:
diskstart: Add a pointer to the syslinux_banner to the EPA (2011-04-04
17:40:59 -0700)
are available in the git repository at:
git://github.com/pcacjr/syslinux.git syslinux-update-for-hpa
Paulo Alcantara (4):
libinstaller: implement syslinux_already_installed
extlinux: use syslinux_already_installed
2017 Mar 03
2
[PATCH 1/2] Use gnulib set_nonblocking_flag function instead of fcntl.
The previous code:
fcntl (fd, F_SETFL, O_NONBLOCK)
was technically incorrect, because it would have reset any
other flags on the file descriptor.
Thanks: Eric Blake
---
bootstrap | 1 +
daemon/inotify.c | 6 ++++--
lib/conn-socket.c | 21 +++++++++++----------
m4/.gitignore | 9 +++++++++
4 files changed, 25 insertions(+), 12 deletions(-)
diff --git a/bootstrap b/bootstrap
2016 Feb 24
2
[PATCH 5/5] installers: fix a MinGW redefinition warning
I get a redefinition warning on _GNU_SOURCE when compiling with MinGW,
and while I could see that this #define was introduced in e4fc44 [1],
but the reason to introduce it is not mentioned, and I can't really see
a good reason to have it, especially as MSVC will happily compile that
source. So far I have found no evidence that _GNU_SOURCE applies to
memset/memmove/memcpy, which are the
2014 Sep 24
0
[PATCH] remove _BSD_SOURCE definition
On Thu, Sep 18, 2014 at 12:34 AM, Chanho Park <chanho61.park at samsung.com> wrote:
> The _BSD_SOURCE was deprecated since glibc-2.20. _DEFAULT_SOURCE can be
> used instead of _BSD_SOURCE. However, there is no need to include
> _BSD_SOURCE because the sources only have inline functions and calls
> memcmp/cpy functions.
Testing this myself on my build boxes, I see no issue. The
2016 Feb 24
6
[PATCH 2/5] ntfs: remove unused variable and have ntfssect use char API calls
The variable 'ok' is never used and generates a warning. Remove it. Also
ntfssect.c is designed to be compiled in non Unicode mode when using
MSVC compilers, so remove all ambiguity about it (LPCTSTR -> LPCSTR, use
of 'A' API calls) so that it doesn't break when compiled in Unicode
mode, which is what Rufus uses with MSVC.
-------------- next part --------------
2013 Jan 04
4
syslinux 5.00 does not build
I am trying to build an RPM starting from the TAR archive. The relevant
error is:
make[1]: Entering directory
`/tmp1/Software/rpmbuild/BUILD/syslinux-5.00/libinstaller'
perl bin2c.pl syslinux_bootsect < ../core/ldlinux.bss > bootsect_bin.c
perl bin2c.pl syslinux_ldlinux 512 < ../core/ldlinux.sys > ldlinux_bin.c
perl bin2c.pl syslinux_mbr < ../mbr/mbr.bin > mbr_bin.c
perl
2014 Dec 24
0
[PATCH 8/8] libinstaller/syslxopt.c: update the help text.
We support both device and directory as the target now.
Signed-off-by: Robert Yang <liezhi.yang at windriver.com>
---
libinstaller/syslxopt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libinstaller/syslxopt.c b/libinstaller/syslxopt.c
index 3fc5519..d06719f 100644
--- a/libinstaller/syslxopt.c
+++ b/libinstaller/syslxopt.c
@@ -88,7 +88,7 @@ void __attribute__
2014 Dec 28
2
raid long option
In Syslinux 6.03 -> libinstaller/syslxopt.c:
#n 50: const struct option long_options[] = {
...
#n 60: {"raid-mode", 0, NULL, 'r'},
...
#n105: fprintf(stderr,
...
#n112: " --raid -r Fall back to the next device on boot failure\n"
Comparing line #60 vs. line #112:
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 28
1
syslinux-4.02-6-ge841d69 build failure
make[1]: Entering directory `/syslinux-4.02-6-ge841d69/dos'
gcc -Wp,-MT,syslxopt.o,-MD,./.syslxopt.o.d -m32 -ffreestanding -fno-stack-protector -fwrapv -freg-struct-return -march=i386
-Os -fomit-frame-pointer -mregparm=3 -DREGPARM=3 -msoft-float -fno-exceptions -fno-asynchronous-unwind-tables -fno-strict-aliasing
-falign-functions=0 -falign-jumps=0 -falign-labels=0 -falign-loops=0
2016 Feb 24
2
[PATCH 3/5] installers: MSVC compatibility fixes
More MSVC compatibility fixes, for packed structures.
NB: In case you are aware of the issues that may come with MS vs GCC
packing, so far, I have not seen evidence of detrimental impact from
using ms_struct packing in MSVC (vs gcc_struct, which is explicitly
specified for MinGW), with regards to the sections of code I am using in
Rufus.
-------------- next part --------------
2014 Dec 25
0
[PATCH 0/8] extlinux: support unmounted ext2/3/4 filesystem
>
> Hi Ady,
>
> Thank you very much, I prefer this one, add the extN support to
> linux/syslinux-nomtools, create a new "e2fs/syslinux" may make things
> more complicated for the user, I will make it as:
>
> 1) If it is a extN device, then root privilege is not required.
> 2) Otherwise work as before.
>
> Any suggestions is appreciated.
>
> //
2014 Dec 28
0
raid long option
Ady <ady-sf at hotmail.com> writes:
> In Syslinux 6.03 -> libinstaller/syslxopt.c:
>
>
> #n 50: const struct option long_options[] = {
> ...
> #n 60: {"raid-mode", 0, NULL, 'r'},
> ...
> #n105: fprintf(stderr,
> ...
> #n112: " --raid -r Fall back to the next device on boot failure\n"
>
>
>
2016 Mar 07
1
[PATCH 4/5] installers: fix a possible buffer overflow when looking for LDLINUX_MAGIC
On 2016.03.07 03:27, Shao Miller via Syslinux wrote:
> - Casting to a uintptr_t is ugly (and not C89, not that Syslinux cares
> about that)
Yeah, I'd have liked to avoid that too, but some compilers will complain
about pointer arithmetic logic, unless you specifically use uintptr_t.
But, considering your other very valid point, let me see if I can work
something better here, that