Package: grub-efi-amd64-bin
Version: 1+2.02+dfsg1+20
Severity: wishlist
Dear Maintainer,
I'm trying to use Debian-signed secure boot grub binaries
with Super Grub2 Disk scripts.
Many of the Super Grub2 Disk scripts make use of the probe
command. It makes possible to identify partition uuid
Package: shim-unsigned
Version: 15+1533136590.3beb971-7
Severity: normal
Dear Maintainer,
I want to be able to build a live cd that has both ia32 and x64 Secure
Boot UEFI support.
So I need both shim-signed:amd64 and shim-signed:i386 installed.
Those two packages depend on shim-unsigned:amd64
Package: pcmanfm-qt
Severity: important
Dear Maintainer,
It does not start - without a meaningful message
* Expected Behavior
it should start as root
* Current Behavior
It does not start at all as root
* Possible Solution
Use:
lxsudo dbus-launch pcmanfm-qt
instead which requires dbus-x11
Package: grub-efi-amd64-signed
Version: 1+2.02+dfsg1+16
Severity: wishlist
Dear Maintainer,
live-build generated grub.cfg uses grub's cpuid command when
there are two or more kernel flavours.
The final user thanks to the add auto option can choose either
the amd64 kernel or 686 kernel in an
Package: shim-signed
Version: 1.30+15+1533136590.3beb971-5
Severity: normal
Dear Maintainer,
I want to be able to build a live cd that has both ia32 and x64 Secure
Boot UEFI support.
So I need both shim-signed:amd64 and shim-signed:i386 installed.
After adding and apt amd64 architecture to an
Package: debian-live
Severity: wishlist
Dear Maintainer,
As official Debian Live images are going to be signed
by MS keys that will mean that they can be booted
in MS Secure Boot enabled hardware.
Some people might want to be able to use mokutil
binaries from their live cds to enrol new
I haven't checked every possible combination you put there I guess it's ok.
So, once again looks good to me.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
art should be improved to have something better than:
https://salsa.debian.org/live-team/live-build/blob/00eab3a77f3da176f3f0aa807b886206f8f0f0f1/scripts/build/binary_hdd#L60-86
All of this above is trying to improve multi bootloader support in the
binary_hdd part of live-build. Not sure if you should deal with this
prior to adding your code.
But if you want to take a look and tell us if binary_hdd should be
updated or not (in the end the efi installation is handled by
binary_syslinux-efi or binary_grub-efi in the filesystem level and not
by binary_hdd).
Having to deal with separate bootloaders, what they add or contribute
that's another reason why I prefer binary_syslinux and
binary_syslinux-efi being in different files.
6.3) Many of your commits seem to need a rebase into the current master
branch. Well, that's to be expected.
>
> Gr.
>
> Matthijs
>
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
id you ever check buxy's work just in case it has something
that you can recycle?
I'll try to comment on "Improve bootloader configuration checks
(5fb9ab31)" on the next days. I need to be focused on this one :) .
Waiting for your feedback on the rest of the points. Hopefu
t commit should be in its own pull request and not
the current one.
That way it can opt to be applied inmediately while the rest of your
commits is being studied.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
https://salsa.debian.org/live-team/live-build/merge_requests/19
1) What is the rationale behind removing the --templates option
explanation on manpage?
Do you remove it in any of your commits? Which one?
Or someone else did remove it?
Thank you.
Note: I will make more comments about this bug lat
El 18/03/19 a las 00:39, adrian15 escribió:
> El 09/03/19 a las 18:06, Thomas Schmitt escribió:>> What I'm saying with
> all of this is that I'm going to propose a fix that
>>> involves not using any earmark (which involves too much work) but just
>>> sea
distributions discuss with each other and
another place where remaster tool developers discuss with each other.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
El 13/03/19 a las 09:01, Raphael Hertzog escribió:
> On Tue, 12 Mar 2019, adrian15 wrote:
>> Is it ok for merging in Debian GIT or is there anything that I can improve?
>
> I think it's OK if this was tested and if it doesn't break anything.
Yeah, I tested it in various commits fro
autodetection is already present in
binary_loopback_cfg. So I only want isolinux support to be added.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
>From 13730f7f8db6eb9bdd82a06b5c38148c56b2278d Mon Sep
"686 amd64:amd64"
in a buster i386 chroot and it works flawlessly.
If you want to avoid the grub> prompt with Secure Boot you should apply
patch from #924053 bug too.
Is it ok for merging in Debian GIT or is there anything that I can improve?
Thank you very much!
adrian15
--
s, as long as we only support binary_iso it's fine for now to
rely on /disk/.info (only generated by xorriso) till we find a better
method (like the one suggested by Thomas).
Thank you.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub
El 09/03/19 a las 15:03, Thomas Schmitt escribió:
> Hi,
>
> adrian15 wrote:
>> Well, guess what happened... my obvious patch:
>> if ! search --set=root --file /live/vmlinuz ; then
>search --set=root --file /live/vmlinuz1
>> does not boot in my compu
El 09/03/19 a las 16:35, Thomas Schmitt escribió:
> Hi,
>
> adrian15 wrote:
>> replace:
>> search --set=root --file /live/vmlinuz
>> with:
>> search --set=root --label \"${LB_ISO_VOLUME}\"
>
> This looks ok for me, as far as GRUB2's work is
"${LB_ISO_VOLUME}"
.
As I said I'll work on the /live/id/12345678.ABC approach later.
adrian15
El 09/03/19 a las 15:18, adrian15 escribió:
> I am currently building and testing a label search approach.
> It works manually on both UEFI USB boot and TianaCore UEFI CDROM boot.
>
El 09/03/19 a las 15:03, Thomas Schmitt escribió:
> Hi,
>
> adrian15 wrote:
>> Well, guess what happened... my obvious patch:
>> if ! search --set=root --file /live/vmlinuz ; then
>search --set=root --file /live/vmlinuz1
>> does not boot in my compu
El 09/03/19 a las 15:03, Thomas Schmitt escribió:
> Hi,
>
> adrian15 wrote:
>> Well, guess what happened... my obvious patch:
>> if ! search --set=root --file /live/vmlinuz ; then
>search --set=root --file /live/vmlinuz1
>> does not boot in my compu
/ devices being detected with
Secure Boot enabled and Secure Boot disabled.
So that we can conclude if this fallback to minimal grub.cfg is
inevitable and attached to Secure Boot or if it's a Secure Boot bug itself.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el so
ts. Maybe renaming /live/vmlinuz in the
internal hard disk partition to mimic non HP250G6 systems but I already
know what's going to happen. I'll get the grub> prompt too because it
will have no useful grub.cfg to configfile into.
4) And, well, I might try an obvious patch that searches with regex b
8a8301629d84c/scripts/build/efi-image
Can anyone more experienced than me take a look at the 'signed packages'
'source package' and check how the EFI are actually built?
I guess they use a different script than efi-image or an update one that
changes some paths.
As always, any feedback is
I/BOOT # This might be an additional EFI
partition because it only has 'efi' and 'boot' directories.
prefix=(hd0)/boot/grub # USB ( boot/ , efi/, efi.img, isolinux/, live/ y
md5sum.txt )
root=hd0 # USB ( boot/ , efi/, efi.img, isolinux/, live/ y md5sum.txt )
adrian15
El 08/03/19 a las 23:21, ad
any feedback that can speed up my
testing is welcomed.
Thank you very much!
adrian15
Here there is the bisect just in case you need me to test more commits:
( grub> ) f242323fa246840ba9581586ad78a8301629d84c We should add buster
for release
( N/A ) 2fa258cca25d834f7896b7adc64892dc583010
El 20/11/18 a las 14:19, Raphael Hertzog escribió:
Sorry for the delay in answering but I have been busy.
> Hi,
>
> On Sun, 18 Nov 2018, adrian15 wrote:
>> After testing this change the Grub menu which should have two kernel
>> entries has only one. It might be other of m
El 23/02/18 a las 17:43, Raphael Hertzog escribió:
> Hi,
>
> On Sat, 23 Dec 2017, adrian15 wrote:
>> 3) So I dropped that implementation of the patch and searched for
>> something more elegant. A patch that modified the least possible lines
>> of the live-build code
El 21/12/17 a las 14:32, Raphael Hertzog escribió:
> On Sun, 17 Dec 2017, adrian15 wrote:
>>* What led up to the situation?
>
> The reportbug templates are not always very appropriate when you
> just want to submit a patch... just go straight to the explanation
>
El 21/12/17 a las 14:11, Raphael Hertzog escribió:
> Hi,
>
> On Sat, 16 Dec 2017, adrian15 wrote:
>> Now using:
>>
>> --linux-flavours="amd64:amd64 686"
>>
>> in a i386 system does install amd64 kernel from amd64 architecture in a
>> transp
Package: live-build
Version: 1:20171207
Severity: normal
Control: tags -1 + patch
Dear Maintainer,
* What led up to the situation?
I was trying to build a live cd that has both two kernels: 686 and amd64
and at the same time which would be any hybrid disk so that I can boot
in a BIOS-only
Package: live-build
Version: 1:20171207
Severity: normal
Control: tags -1 + patch
Dear Maintainer,
* What led up to the situation?
I was trying to build a live cd that has both two kernels: 686 and amd64
and at the same time which would be any hybrid disk so that I can boot
in a BIOS-only
Package: live-build
Version: 1:20171207
Severity: normal
Control: tags -1 + patch
Dear Maintainer,
* What led up to the situation?
I was trying to build a live cd that has both two kernels: 686 and amd64
and at the same time which would be any hybrid disk so that I can boot
in a BIOS-only
Control: tags -1 + patch
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
he current git head ( d33943ea7a71ba5d874eb20f47bb898da485c77d )
* Can also be found at:
** Repo: https://github.com/rescatux/live-build.git
** Branch: foreign-architecture-support-quicktest3
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super
Package: live-build
Version: 1:20171207
Severity: normal
Dear Maintainer,
* Introduction
Jessie had linux-amd64 package in its own i386 section.
Stretch has linux-amd64 package not in i386 section but in amd64 section
only.
When using live-build with Jessie you could use in an i386 Jessie
Control: tags -1 + patch
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
Control: tags -1 + patch
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
Control: tags -1 + patch
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
Control: tags -1 + patch
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
-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
From: Adrian Gibanel Lo
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
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 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
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
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 <adrian15...@gmail.com> wrote:
This new update tries to imp
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 <adrian15...@gmail.com> wrote:
El 21/03/16 a las 22:19, Michal Suchanek es
u
can check our tour "Installing Debian".
CSA. 6. Enjoy your Debian
As per your technical role we recommend you to discover the
different blends of Debian which can be applied to normal Debian
installation thanks to its metapackages.
CSA. 7. Become a Debianer!
El 21/03/16 a las 22:19, Michal Suchanek escribió:
Hello,
On 21 March 2016 at 21:09, adrian15 <adrian15...@gmail.com> 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_reb
El 21/03/16 a las 22:19, Michal Suchanek escribió:
Hello,
On 21 March 2016 at 21:09, adrian15 <adrian15...@gmail.com> 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_reb
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://www.supergrubdisk.org/donate/
>F
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
ng 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 time
a new bootloader is added.
With what I'm proposing you you wouldn't have to u
El 25/01/16 a las 16:12, Michal Suchanek escribió:
On 25 January 2016 at 03:05, adrian15 <adrian15...@gmail.com> 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 v
fs 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/5eba3dff5a16a34c3c1eb5d54e3767339654e2d0/scripts/build/binary_iso#L111
_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 approach.
Here it'
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
was graphical oriented and that I
left out some cli tools from it. Some sysadmins might consider using
grml instead of Rescatux for cli purposes just for that.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http
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
ot;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?
ad
ed 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/dona
/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/
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 several lures
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/
to 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
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 <adrian15...@gmail.com> 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
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 worked
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 here.
adrian15
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
--
Support free software. Donate to Super
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 going
issue can be found at:
https://github.com/adrian15/chntpw/commit/684d32504e4875fcb647544cb83903b375f22505
Additional note: I already contacted upstream author but received no
answer for
about half a year, so I guess it's fine pushing this to Debian.
-- System Information:
Debian Release: 8.
binary to do such task.
* What outcome did you expect instead?
To have a binary that allows me to unlock a windows user from the
command line.
The two patches that allows the new samunlock binary are:
https://github.com/adrian15/chntpw/commit/b24f36061493ae674dbbcf815e314c6c90103311
https
_USER}" ${SAM_FILE};
* What was the outcome of this action?
The windows user password was not changed.
* What outcome did you expect instead?
I expected the user password to be changed.
You can find the patch that solves this problem in upstream here:
https://github.com/adrian15/chn
olves this issue can be found at:
https://github.com/adrian15/chntpw/commit/dc1c6edf135d9d628ab4230605bd778efd7c5dba
Additional note: I already contacted upstream author but received no
answer for
about half a year, so I guess it's fine pushing this to Debian.
-- System Information:
Debian Releas
El 18/08/15 a las 19:28, Andreas Cadhalpun escribió:
Hi adrian15,
On 18.08.2015 10:47, adrian15 wrote:
Can you please explain why you are using: get_fstype () function which it's
based
on blkid instead of just using the old method of relying in auto function from
the kernel itself
-detect.patch and mountmedia.patch.
Please, be aware, that I'm not telling you your approach is incorrect.
It seems we are lacking the explanation or rationale on why you made
that decision in order to evaluate that change in a fair manner.
Thank you very much!
adrian15
--
Support free software
Right. Grub does not need to be inside the iso.
Your example is right is the filename is loopback.cfg and not
looback.cfg which I think it's a typo.
El 14/08/15 a las 08:41, Daniel Baumann escribió:
Hi,
just to be sure: loopback.cfg support means that the iso doesn't
necessarily has to have
about this templates directory. Thank you very much. I
guess the difference is that the grub2 package has some template files
by default while the syslinux has not these templates by default so the
bootloaders directory needed to be used. But, well, I'm just wild guessing.
adrian15
--
Support
El 17/01/15 a las 02:21, jnqnfe escribió:
On 15/01/2015 14:52, adrian15 wrote:
I just write down here that I will have to review your mentioned: #1,
#2, #3, #4, #5, #6, #7, #8 and #9 in my (#757883) (support for
loopback.cfg file) so that it matches your improvements and fixes.
No problem, I
.
As of this moment I have written patches for 11 of these issues, some of
which have already been posted separately. More to follow soon.
Thank you again for your hard work.
adrian15
[1]:
http://git.grml.org/?p=grml-live.git;a=blobdiff;f=templates/boot/grub/grub.cfg;h
El 22/12/14 a las 01:19, Michal Suchanek escribió:
Hello,
On 10 August 2014 at 18:31, Adrian Gibanel Lopez adrian15...@gmail.com wrote:
Source: live-config
Severity: wishlist
Dear Maintainer,
If one has configured its Debian Live to have more than one architecture
kernel this is what I am
Package: grub-common
Version: 2.02~beta2-20
Severity: normal
Dear Maintainer,
* Summary
grub-common not being dependent on mtools package breaks the build of
EFI based
ISOs (thanks to grub-mkrescue) for those of us who did not have mtools
package
installed in first place.
* What led
El 15/08/14 a las 13:04, Daniel Baumann escribió:
On 08/15/2014 07:12 AM, adrian15 wrote:
I attach a patch for Isolinux / Syslinux implementation for cpu detection.
nice, thanks.
from a quick look, sounds good. will check, test, and apply next week.
As suggested (by another bug) I attach
the binary_syslinux renaming the kernel
filenames or is it ok the way I'm doing it?
Thank you.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
filenames.
Just in case you want the detailed commits from debian-old-3.0 to
debian-next they can be found here:
https://github.com/adrian15/live-build/commit/b907d5ca4cfac5407e4231a202b5b84cfcf8c56c
https://github.com/adrian15/live-build/commit/5c7636f8848b3d1d058bb2ed7fd69e01ad05270d
https
Just in case it's easier for you to accept my patch you can also find it
in this git repo commit based on live-build git repo:
https://github.com/adrian15/live-build/commit/c6da5ff61bb46cb66b23fcb66daa83e23fc8a36b
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
I have these same patches available for live-build package on my
live-build git repo here:
Isolinux:
https://github.com/adrian15/live-build/commit/4419638ab9cdfb1bacd98593e31d7f700b15a2dc
Grub2 :
https://github.com/adrian15/live-build/commit/a06085381ba346b576064ee84b325de54a81e33d
Just
I know that:
git push --force
is kind of forbidden when working in public with other people.
As this is my kind of personal repo I did it.
So the replaced commit (which only fixes file permissions) is found at:
https://github.com/adrian15/live-build/commit
4 GB hard disk test
after dding the ~ 500 GB image would have been detected as a 500 GB size
only hard disk.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
--
To UNSUBSCRIBE, email to debian
to make depend this bug on #724931 if that it makes sense (not
very experienced on BTS and Debian policies).
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
--
To UNSUBSCRIBE, email to debian
needed actually works or if it would need hacks on how Gnu/Linux
kernel reads devices bigger than its partition table suggested size.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate
).
9) You should boot into your Debian Live without problems (thanks to
findiso boot parametre).
If you ever wanted to test from your grub2 installation instead from
Super Grub2 Disk check: http://www.supergrubdisk.org/wiki/Loopback.cfg
for an example.
adrian15
--
Support free software. Donate
I attach a patch for CPU detection when Debian Live uses grub2 as its
bootloader.
Please advise how to improve it so that it gets included upstream.
Thank you.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http
=deb15c765e2b34fe587c96ca590981a59a278922
Upstream documentation: http://www.syslinux.org/wiki/index.php/Ifcpu64.c32
Thank you!
I attach a patch for Isolinux / Syslinux implementation for cpu detection.
Please advise how to improve the implementation so that it can be
accepted upstream.
Thank you.
adrian15
Package: live-boot
Version: 3.0~b2-1
Severity: important
When building an Squeeze debian live cd inside an Squeeze system and
trying to use live-boot* packages from unstable seems to be broken.
When I boot I get:
Loading, please wait..., run-init: nuking initramfs contents: Directory
not
First of all I've managed to fix the problem on the fly inspired from
the related bug.
So you boot with break=init and I run:
mkdir -p live
mount -t tmpfs tmpfs /live
exit
and the system seems to boot ok.
El 09/09/12 19:14, Daniel Baumann escribió:
On 2012-09-09 18:55, adrian15 wrote
doesn't work on stable make
easier your work.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
)
as background.
That fits into Case A.
Not sure what causes this bug yet.
El 20/01/12 00:28, adrian15 escribió:
I have done more tests and this is what I have found:
Case A: When I get a black background:
==
/home/user/.config/pcmanfm/LXDE.conf has lxde_blue.jpg
1 - 100 of 125 matches
Mail list logo
