Package: live-build
Version: 5.0~a11-1
Severity: minor
Dear Maintainer,
* What led up to the situation?
I was trying to use @VERSION@ string in splash.svg.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I used @VERSION@ string in splash.svg.
* What was
(E.g. please test it on actual hardware, in your
distro builds, even if you don't use UEFI does the ISO boot as always in
BIOS mode?) And give us feedback on it.
Thank you.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://
El 21/03/16 a las 22:19, Michal Suchanek escribió:
Hello,
On 21 March 2016 at 21:09, adrian15 wrote:
The branch which include specifically the commits I attach here as patches
is:
https://github.com/rescatux/live-build/tree/efi_support_based_on_debian_cd_rebased_5
.
About the variable
El 21/03/16 a las 22:19, Michal Suchanek escribió:
Hello,
On 21 March 2016 at 21:09, adrian15 wrote:
The branch which include specifically the commits I attach here as patches
is:
https://github.com/rescatux/live-build/tree/efi_support_based_on_debian_cd_rebased_5
.
About the variable
ranch
and can be found here:
http://www.supergrubdisk.org/2016/07/31/rescatux-0-40-beta-7-released/ .
As always feedback is welcome.
El 22/03/16 a las 07:18, Michal Suchanek escribió:
On 21 March 2016 at 23:06, adrian15 wrote:
El 21/03/16 a las 22:19, Michal Suchanek escribió:
So please con
ack.
After that time I'll try to request a proper pull / insertion into
Debian's live-build repo and probably into live-build package binaries.
adrian15
El 31/07/16 a las 10:12, Michal Suchanek escribió:
Hello,
On 31 July 2016 at 09:35, adrian15 wrote:
This new update tries to imp
El 04/08/16 a las 14:51, Raphael Hertzog escribió:
Hi,
On Sun, 31 Jul 2016, adrian15 wrote:
Is there anyone else than can provide feedback on this patch / branch?
Either by:
* Installing live-build with this applied patch
* Building your iso and check if it boots in both BIOS and UEFI mode
El 04/08/16 a las 14:51, Raphael Hertzog escribió:
Hi,
On Sun, 31 Jul 2016, adrian15 wrote:
Is there anyone else than can provide feedback on this patch / branch?
Either by:
* Installing live-build with this applied patch
* Building your iso and check if it boots in both BIOS and UEFI mode
El 25/08/16 a las 15:36, Raphael Hertzog escribió:
Hello Adrian,
On Tue, 16 Aug 2016, adrian15 wrote:
Kristian Klausen thinks is a good idea to wait for your tests.
So your feedback is welcome.
I just built a test Kali image with your patch applied. It works:
I can boot the live system in
El 26/08/16 a las 09:52, Raphael Hertzog escribió:
On Thu, 25 Aug 2016, adrian15 wrote:
That's how the grub-pc menu (BIOS) shows currently in live-build.
Well, it sucks compared to the default visual appearance of
isolinux/syslinux in live-build.
I know, but the purpose of my patch
El 26/08/16 a las 13:34, Raphael Hertzog escribió:
On Fri, 26 Aug 2016, adrian15 wrote:
Well, it sucks compared to the default visual appearance of
isolinux/syslinux in live-build.
I know, but the purpose of my patch is to add UEFI support. Not to improve
visual appearance of grub2 so that it
ub.com/rescatux/live-build/tree/efi_support_based_on_debian_cd_rebased_10
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
>From 01a9df8ce325c5df9762f0db86128614b4d3476c Mon Sep 17 00:00:00 2001
Fro
I attach a patch based on your work (which I have not tested so feedback
is welcome).
You can find the specific modifications to your original commit/patch
(which I had to cherry-pick) on branch:
https://github.com/adrian15/live-build/tree/efi_support_based_on_debian_cd
Now I'm goi
an-installer
scripts which let you translate syslinux configuration files into grub
configuration files.
Feedback is welcome!
P.S.: I am going to release soon: Rescatux 0.40b3 which will be based on
these commits so you will be able to see how it would perform the final
product.
adrian15
--
Sup
droms with syslinux-efi.
The quick and dirty branch where I worked on both grub-efi and
syslinux-efi is here:
https://github.com/adrian15/live-build/tree/efi_support_based_on_debian_cd
That branch is handy to understand the changes between Raphael's
original patch and what I present h
ad to
your email program and reply from there) can be found at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731709#153
2) Repo / Branches:
* efi_support_based_on_debian_cd (
https://github.com/adrian15/live-build/tree/efi_support_based_on_debian_cd
) : Original dirty branch where I work
El 18/01/16 a las 07:31, Michal Suchanek escribió:
Hello,
thanks for working on this.
On 18 January 2016 at 05:24, adrian15 wrote:
In my last message I forgot to CC many people who are involved in this bug
so I'm going to refer to my former message, CC some people and finally point
you
fix this situation on:
https://github.com/adrian15/live-build/tree/efi_support_based_on_debian_cd_rebased
and
https://github.com/adrian15/live-build/commits/syslinux-efi-2016
.
(I will probably do another rebase in another branch in the future with
other of your suggestions and these fixes.)
2
https://github.com/adrian15/live-build/tree/efi_support_based_on_debian_cd_rebased
So that part is solved.
(I'll send a proper rebased set of patches in the future).
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
nse if, as I have stated earlier (although I might have missed
something there) they would overwrite their /efi/boot/boot*efi files ?
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
El 18/01/16 a las 13:38, Thomas Schmitt escribió:
Hi,
adrian15 wrote:
* What is it a secondary bootloader?
It's what happens when you request mkisofs that your bootloader to be
boot in second place or as a second partition. I don't know how it
actually works.
An ISO may contain sev
s refering to USB stick then.
adrian15 wrote:
Grub-pc would be the one installed to be boot but syslinux files would be
there for Multi-USB tools to know how to understand the iso and put it into
an USB.
You mean the capability to boot the ISO via BIOS from USB stick ?
(Known with SYSLINUX as
El 21/01/16 a las 12:57, Thomas Schmitt escribió:
adrian15 wrote:
Do you mean if you have:
xorriso bunch-of-options-1 -eltorito-alt-boot bunch-of-options-2
you could just re-arrange them as:
xorriso bunch-of-options-2 -eltorito-alt-boot bunch-of-options-1
and it would be fine?
From the
(based on live-build master
branch) here:
https://github.com/adrian15/live-build/tree/efi_support_based_on_debian_cd_rebased_4
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org
t;Main bootloader"
and
"Alternate bootloader".
Or maybe even better:
"Main eltorito entry"
and
"Alternate eltorito entry"
?
So that we can force a given bootloader to be used only as a "Main
eltorito entry" ?
What do you think about this idea?
functions to binary_bootloader files so
that we have some sort of Object-Oriented / Hook programming when
defining what goes into the mkisofs options.
If you check current: binary_iso file it just relies on existing
binary_bootloaders without having an agnostic bootloader
ining what goes into the mkisofs options.
If you check current: binary_iso file it just relies on existing
binary_bootloaders without having an agnostic bootloader approach.
Here it's what I'm talking about:
https://github.com/adrian15/live-build/blob/5eba3dff5a16a34c3c1eb5d54e3767
El 25/01/16 a las 16:12, Michal Suchanek escribió:
On 25 January 2016 at 03:05, adrian15 wrote:
El 24/01/16 a las 16:51, Michal Suchanek escribió:
What you are describing here is what it's actually implemented in my patch
(Well, actually the first patch version because the curren
erent available binary_bootloaders available.
What's wrong with referencing variables we have so that we know
what's going on in l-b?
Thanks
Michal
Well, basically, my design rationale behind this is that with the
current way of doing things you need to update binary_iso file each
29 matches
Mail list logo
