Displaying 20 results from an estimated 400 matches similar to: "[PATCH] extlinux: code cleanup and simplification"
2015 Nov 12
1
[PATCH] Unification of ext_(write/read)_adv
Signed-off-by: Nicolas Cornu <nicolac76 at yahoo.fr>
---
extlinux/main.c | 44 ++++++++++++++++++++++----------------------
1 file changed, 22 insertions(+), 22 deletions(-)
diff --git a/extlinux/main.c b/extlinux/main.c
index 6871fb1..385b364 100644
--- a/extlinux/main.c
+++ b/extlinux/main.c
@@ -1415,21 +1415,12 @@ static int open_device(const char *path, struct stat *st, char
2015 Nov 18
0
[PATCH] extlinux: code cleanup and simplification
2015-11-13 20:35 UTC+01:00, Nicolas Cornu via Syslinux <syslinux at zytor.com>:
> Merge btrfs_read_adv and xfs_read_adv into a single generic function
> ext_read_adv and split ext_write_adv_offset out of ext_write_adv.
>
> Use those new functions in rewrite_boot_image and btrfs_install_file
> where it is actually hardcoded.
>
> Signed-off-by: Nicolas Cornu <nicolac76
2015 Nov 26
0
[syslinux:master] extlinux: code cleanup and simplification
Commit-ID: 82c0ec7b39acb87175ea588f2fa11b21331503c4
Gitweb: http://www.syslinux.org/commit/82c0ec7b39acb87175ea588f2fa11b21331503c4
Author: Nicolas Cornu via Syslinux <syslinux at zytor.com>
AuthorDate: Fri, 13 Nov 2015 20:35:29 +0100
Committer: Paulo Alcantara <pcacjr at zytor.com>
CommitDate: Wed, 25 Nov 2015 21:58:23 -0200
extlinux: code cleanup and simplification
Merge
2015 Nov 18
1
[PATCH] extlinux: code cleanup and simplification
Right sorry for that ;)
Le Mercredi 18 novembre 2015 7h31, Celelibi <celelibi at gmail.com> a ?crit :
2015-11-13 20:35 UTC+01:00, Nicolas Cornu via Syslinux <syslinux at zytor.com>:
> Merge btrfs_read_adv and xfs_read_adv into a single generic function
> ext_read_adv and split ext_write_adv_offset out of ext_write_adv.
>
> Use those new functions in
2013 May 30
0
Possible bug in ext_read_adv
Hi,
looking at ext_read_adv code (extlinux/main.c)
static int ext_read_adv(const char *path, int devfd, const char **namep)
{
int err;
const char *name;
if (fs_type == BTRFS) {
/* btrfs "ldlinux.sys" is in 64k blank area */
return btrfs_read_adv(devfd);
} else if (fs_type == XFS) {
/* XFS "ldlinux.sys" is in the first 2048 bytes of
2015 Nov 26
1
[PATCH] extlinux: code cleanup and simplification
> On Fri, 13 Nov 2015 20:35:29 +0100
> Nicolas Cornu via Syslinux <syslinux at zytor.com> wrote:
>
> > Merge btrfs_read_adv and xfs_read_adv into a single generic function
> > ext_read_adv and split ext_write_adv_offset out of ext_write_adv.
> >
> > Use those new functions in rewrite_boot_image and btrfs_install_file
> > where it is actually
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
2015 Jan 02
13
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
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
you'd like to test them. (The repo's name is sys_tmp, which avoids
confusing others, I will
2013 Jul 12
2
[PATCH 001/001] Add UFS1/2 support to Extlinux installer.
It's needed to enumerate both UFS1/2 since they have different magic numbers
and super block offsets.
Besides, UFS2 can be installed in the 0-64k range like BTRFS, whereas
UFS1 can't.
Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com>
---
extlinux/main.c | 71 +++++++++---
extlinux/ufs.h | 26 ++++
extlinux/ufs_fs.h | 307
2013 Jul 26
2
[PATCH 1/1] core: Add a check at ldlinux.sys build time.
On 07/26/2013 01:36 PM, Raphael S Carvalho wrote:
>
> Bootsector is installed into the 0-512 range, whereas 2 copies of ADV
> into (65536 - 2 * ADV_SIZE).
> Then basically ldlinux.sys must fit between the bootsector and two
> copies of ADV whose size may vary.
>
> The range 0-64k is laid out something like this, right?!
> [0](bootsector)[512](ldlinux.sys)[65536 - 2 *
2013 Sep 30
2
[PATCH v2] core: Check size of ldlinux.sys at building time.
From: Raphael S. Carvalho <raphael.scarv at gmail.com>
v2: Extract ADV_SIZE automatically from libinstaller/setadv.h.
Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit.
ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary.
Thus, the size of ldlinux.sys can be at most: 65536 - 2 * ADV_SIZE - 512 (limit).
Certain file systems
2012 Aug 02
0
[PATCH 2/3] ALPHA: first try to fix adv problem
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 ADV size problem.
Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com>
---
extlinux/main.c | 40 +++++++++++++++++++++++++++++++++++-----
1 files changed, 35 insertions(+), 5 deletions(-)
diff
2013 Aug 31
4
[PATCH 1/1] core: Check if ldlinux.sys exceeds the limit at its building time.
Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit.
ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary.
Thus, the size of ldlinux.sys (limit) can be at most: 65536 - 2 * ADV_SIZE - 512.
Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys being installed on the 0-64k range,
thus it can't exceed the limit,
2014 May 21
0
[syslinux:master] btrfs: fix typo in definition of BTRFS_ADV_OFFSET
Op 2014-05-20 om 16:57 schreef syslinux-bot for H. Peter Anvin:
> Commit-ID: 93f89ce6697adffcb3b40d758445ff9adf18b6d4
> Gitweb: http://www.syslinux.org/commit/93f89ce6697adffcb3b40d758445ff9adf18b6d4
That yields 'Bad commit reference: 93f89ce6697adffcb3b40d758445ff9adf18b6d4'
What can I do to fix it?
> Author: H. Peter Anvin <hpa at linux.intel.com>
>
2013 Sep 16
2
[PATCH 1/1] core: Check if ldlinux.sys exceeds the limit at its building time.
On Mon, Sep 16, 2013 at 11:08 AM, Matt Fleming <matt at console-pimps.org> wrote:
> Peter, does this look OK to you?
>
> Raphael, I can't work out why ADV_SIZE is a constant in this file?
Matt, ADV_SIZE is currently a constant value, but it may change in the future.
So it would need some care.
Regards,
Raphael S. Carvalho
2014 May 27
2
[PATCH 1/1] core: Check if ldlinux.sys exceeds the limit at its building time.
> On May 25, 2014 3:39 AM, "Geert Stappers" <stappers at stappers.nl> wrote:
> >
> >
> > While going throug old posts found:
> >
> > Op 2013-08-31 om 17:01 schreef Raphael S.Carvalho:
> > > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds
> the limit.
> > > ldlinux.sys must fit between the bootsector and
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.
2013 Jul 22
1
[PATCH 1/1 v2] Add UFS1/2 support to Extlinux installer.
It's needed to enumerate both UFS1/2 since they have different magic numbers
and super block offsets.
Besides, UFS2 can be installed in the 0-64k range like BTRFS, whereas
UFS1 can't. UFS2 has no cow feature unlike BTRFS.
Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com>
---
extlinux/main.c | 79 ++++++++++---
extlinux/ufs.h | 26 ++++
2013 Sep 16
1
[PATCH 1/1] core: Check if ldlinux.sys exceeds the limit at its building time.
On Mon, 16 Sep, at 09:49:01AM, H. Peter Anvin wrote:
> We probably will need to increase out to 4K because of newer drives.
Raphael, is there any way we could extract the ADV_SIZE value from
libinstaller/setadv.h and pass it to ldlinux_limit.pl? That would allow
things to keep working in future when we do upgrade to 4K.
--
Matt Fleming, Intel Open Source Technology Center
2013 Oct 15
1
Using *Syslinux 6.02* on *BTRFS* volumes corrupts the superblock.
BTRFS file systems will be corrupted on 6.02 (mainstream) and some
previous versions.
DYNAMIC_DEBUG makes the core larger than the allowed.
Even before its introduction, building Syslinux with DEBUG_PORT
enabled would probably corrupt BTRFS images (IIRC) *if* ldlinux.sys
surpasses the maximum allowed size.
Besides, the installer isn't safe at all... The check could be easily
made there to