diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-October/008665.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-October/008665.html | 126 |
1 files changed, 126 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-October/008665.html b/zarb-ml/mageia-dev/2011-October/008665.html new file mode 100644 index 000000000..422eb3afa --- /dev/null +++ b/zarb-ml/mageia-dev/2011-October/008665.html @@ -0,0 +1,126 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Syslinux integration roadmap + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Syslinux%20integration%20roadmap&In-Reply-To=%3C201110062106.35403.maarten%40rmail.be%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="008663.html"> + <LINK REL="Next" HREF="008668.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Syslinux integration roadmap</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Syslinux%20integration%20roadmap&In-Reply-To=%3C201110062106.35403.maarten%40rmail.be%3E" + TITLE="[Mageia-dev] Syslinux integration roadmap">maarten at rmail.be + </A><BR> + <I>Thu Oct 6 21:06:35 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="008663.html">[Mageia-dev] Syslinux integration roadmap +</A></li> + <LI>Next message: <A HREF="008668.html">[Mageia-dev] Syslinux integration roadmap +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8665">[ date ]</a> + <a href="thread.html#8665">[ thread ]</a> + <a href="subject.html#8665">[ subject ]</a> + <a href="author.html#8665">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op donderdag 06 oktober 2011 20:18:30 schreef Erwan Velu: +><i> Hi fellows, +</I>><i> +</I>><i> I should have started by writting this email, but later is better that +</I>><i> never. +</I>><i> I'd like to share with you the work I started on syslinux : I +</I>><i> registered myself of maintainer of it. +</I>><i> +</I>><i> Under Mandriva, we were running Syslinux 3.8x with the following +</I>><i> configuration +</I>><i> - gfxboot patch (unsupported upstream as very intrusive) +</I>><i> - isohybrid patch from pterjan +</I>><i> - a remplacement of the built-in pnglib +</I>><i> - a packaging with 3 versions of isolinux to load a different +</I>><i> configuration file regarding the processor capabilities (x86/x64) +</I>><i> +</I>><i> I did upgrade to 4.04 for +</I>><i> - using the gfxboot com32 module which is now upsteam +</I>><i> - using a single version of isolinux +</I>><i> - simplifying the integration of upstream releases into mga +</I>><i> - an up to date version of HDT +</I>><i> +</I>><i> Gfxboot module requested an update of the gfxboot tools & theme. This +</I>><i> work is already done and works properly. +</I>><i> +</I>><i> The pnglib patch management is under discussions in another thread. +</I>><i> +</I>><i> The isohybrid patch have to be reworked as isohybrid is now named +</I>><i> isohybrid.pl, a C version of isohybrid now exists also. Rework of this +</I>><i> patch should be quite easy to do once we'll have understood all the +</I>><i> tricks inside ;) That's shouldn't be a big deal though. +</I>><i> +</I>><i> My plan for using a single version of isolinux is the following : +</I>><i> Using syslinux's capability to load various kernel & configuration files +</I>><i> regarding some hw capabilites (the cpu in this case). I'm ending a +</I>><i> prototype that will simulate the loading of different entries regarding +</I>><i> the cpu arch. This will greatly simplify the management of the boot +</I>><i> procedure and especially for the dual arch isos. +</I>><i> +</I>><i> I'm also working for having some specific entries for the virtualized +</I>><i> world like kvm or virtualbox (cf bug 44). +</I>><i> +</I>><i> 4.04 is also now providing a new package called extlinux which provides +</I>><i> extlinux & the mbr file needed to make a very powerful bootloader for +</I>><i> ext* & btrfs filesystems (more to come). +</I>><i> +</I>><i> Switching to this new scheme will ease updates by using upstream's +</I>><i> version of syslinux. +</I>><i> This will also require working on BCD to integrate this new +</I>><i> configuration files. That shouldn't be hard neither. +</I>><i> +</I>><i> I'm part of the upstream project, so if some more features/ideas are +</I>><i> coming, I'll be more than happy to help you. +</I>><i> +</I>><i> Cheers, +</I>><i> Erwan +</I> +nice work! +</PRE> + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="008663.html">[Mageia-dev] Syslinux integration roadmap +</A></li> + <LI>Next message: <A HREF="008668.html">[Mageia-dev] Syslinux integration roadmap +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8665">[ date ]</a> + <a href="thread.html#8665">[ thread ]</a> + <a href="subject.html#8665">[ subject ]</a> + <a href="author.html#8665">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |