Some years ago the FSF advised against using Copyright YEAR1-YEAR-4.
They said it was better to have:
Copyright YEAR4
Copyright YEAR3
Copyright YEAR2
Copyright YEAR1
.
I don't remember what their reasoning was but it was some legal stuff.
Not sure if it's valid nowadays.
El mié., 11 mar. 2020
I coded that part and some basic test seems to imply its wrong as you have
noticed.
It should be in binary_iso which it's the one that I use.
Here there is:
https://salsa.debian.org/live-team/live-build/-/blob/d6096622f9f7f9e2e1c8b01b4769c9d08487688e/scripts/build/binary_iso#L109-171
So I suggest
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 key
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/
)
--bootloaders grub-pc,syslinux-efi
in a hdd target and 'syslinux' installation should be only triggered if
it's the first bootloader.
Well, that's exactly how binary_hdd works right now... although the
multi bootloader part 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/
to live-build because of reasons? Because grub-efi
enabled Secure Boot to work?
Anyways... Did 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
mmit 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 bu
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
>&g
Unless you know a place where 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 c
pport arch 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 13730f7f8db6eb9bdd82a06b5c38148c56b227
"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
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 i
"${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
n I want to compare grub hard disks / 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
ends and the user is presented:
grub> .
3) I'll try to do more tests. 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
42323fa246840ba9581586ad78a8301629d84c/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
chan
path=(hd0,msdos2)/EFI/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 )
. Anyways 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 ) 2fa258cca25d834f7896b7adc648
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
to discard graphical programs because rescapp needs an UI.
I know that rescapp does not fit into a rescue task rescue because it
needs and UI but if you happen to take a look and you find somehow
rescapp interesting you can take a look at:
https://www.supergrubdisk.org/other-stuff/rescatux-package-repository/
.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
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
> of
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 ma
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 ma
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 ma
It uses the 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. Do
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/
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 sys
--linux-flavours 'amd64 686-pae'
now should be replaced by:
--linux-flavours 'amd64:amd64 686-pae'
Enjoy!
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
Well,
I don't care too much about the approach or if you apply it to
live-wrapper (current Debian Live) or live-build (former Debian Live).
In any case make sure you implement it for both UEFI and BIOS boot. UEFI
uses GRUB2 menues and thus it's slightly different to the current proposed
isolinux
t. It only caches the packages that you actually
download.
I have not tested apt-offline myself so I cannot comment on it.
According to other repliers say it might be more suitable for your needs.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
I just found this new MX Workbench respin iso based on Mepis.
Here's the current list of packages that they use:
https://github.com/AdrianTM/workbench-defaults/blob/master/workbench-tools.list
Just in case it can help you.
adrian15
2016-01-28 17:47 GMT+01:00 Donald Raikes :
> --
>
h syslinux.
Is that correct, or have I overlooked something?
My build system is jessie, the target live-system too.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
ge for using
the software.But, yes, it should work if you build it and install it.
thanks,
Machu
Waiting for your feedback on the recently UEFI boot support added.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
h GPL requirements that
happens to have additional repos then you should help me on fixing this
issue or find a workaround.
Finally, should I fill a bug or am I missing something obvious?
Thank you.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el softw
able to submit an updated patch for almost
three weeks.
As Bern Armstrong says we are sometimes more busy with personal lives
and other projects. :).
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
plies greatly appreciated.
Cheers.
Michael.
For EFI support please check:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731709 . Hopefully I
will be able to upload another version of my patch (hopefully a
definitive one) in seven days.
adrian15
--
Support free software. Donate to Super
catux 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.
e to set a 'distribution name' variable so that a
common string could be replaced on:
* Bootloader entries
* Login screen (I will need this in the future for adapting tails-greeter)
* Possibly in another places
2) Hopefully this RFE can improve the current live-wrapper design.
adrian15
--
S
on the available architecture.
I already did this work for live-build and the commits can be found here:
https://github.com/adrian15/live-build/commit/5852a69976da36abd7bcbbce95807a7a2451a7a6
https://github.com/adrian15/live-build/commit/36f781c4dc55e9a0d14cc74df5ff36f9eac2e33f
3) I don't
tools *
Memtest
Super Grub2 Disk
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
des can be found at:
* Repo: https://github.com/adrian15/live-build/
* Tag: rescatux-0.40b1
* Commit: 42a8f50690be1153285dc8841ec532ac2281e27d
What it's missing from the implementation is:
* Choosing to enable it or not (It's enabled by default)
* Choose between permissive or enforce m
es:
Jessie branch: http://sourceforge.net/p/rescatux/git/ci/jessie/tree/
Commit: 9f74111d7c5222a739054af1900784481f6496c3
8) Annex B. Debian Live update:
tmp-selinux branch: https://github.com/adrian15/live-build/tree/tmp-selinux
Commit: 42a8f50690be1153285dc8841ec532ac2281e27d
adrian15
--
Support
es inside live-build code where we implicitly suppose that it's
going to have
its default value.
El 21/08/15 a las 20:08, adrian15 escribió:
This is a patch for adding Multi bootloaders support to Debian Live.
(Based on current git master).
This is the first step I need to b
This is a patch for adding Multi bootloaders support to Debian Live.
(Based on current git master).
This is the first step I need to be able to add loopback.cfg support to
Debian Live.
It's currently not working. Any help on debugging it it's needed.
Thank you !
adrian15
--
Su
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
ck_templates
function in functions/templates.sh, this looks for a local config
template directory and sets the location in the TEMPLATE variable, which
is used later in binary_grub2.
I don't really see the point in grub/grub2 stuff being treated
differently in this way though...
I did not know
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
ily replace Debian to e.g. Kali from a config file
without too much effort.
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.
adrian
three or more than three
different kernels?
I prefer not to implement i486 vs i686-pae.
I think it's better the patch to be accepted as-is and later to be
improved if someone finds out a reasonable way of improving it for
enabling i486 vs i686-pae.
Thanks
Michal
adrian15
--
Support
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 kernel 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/5c7636f8848b3d1d058bb2ed7fd69e01ad05
enames. That's what it's currently implemented.
Any thoughts on how to approach 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 S
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
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 sof
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 in
El 23/11/14 a las 18:04, intrigeri escribió:
Hi,
I suggest to send the questions aimed at Tails developers to... Tails
developers => tails-...@boum.org.
Ok, I will do.
adrian15 wrote (23 Nov 2014 15:42:11 GMT) :
1) I did a search in tails repository packages (apt-file) and there was
So, I have a fork for tails-greeter at:
https://github.com/adrian15/tails-greeter
branch master: Upstream's master which happens to be: 0.8.5 version.
branch debian-live: Enforces as much as possible not to enable specific
Tails bits. Kind of a workaround.
branch rescatux_0.32: debian
s not strictly needed if you know how to replace the default
lightdm greeter.
Thank you for having read till this point. I know it was a long message.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.or
he TODO list
is this one. Then there's the rescue article, so many things. So, you
can bet I will implement it one day or another.
Intrigeri: Your feedback on my blind assumptions on what tails DM
does is welcomed.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el
El 25/10/14 11:53, intrigeri escribió:
Hi,
(please don't Cc me, I read the list.)
adrian15 wrote (25 Oct 2014 09:25:19 GMT) :
I don't discard modifying and improving your greeter (Language, keyboard, and
keyboard options should be bigger and in the center of the screen)
FYI,
h we can compare manually?
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-live-requ...@lists.debian.org
with a subject of "unsubscr
El 20/10/14 14:03, intrigeri escribió:
Hi,
adrian15 wrote (20 Oct 2014 07:03:06 GMT) :
5) Are you already doing this in your Debian Live based project ? How do you do
it?
We at Tails use a custom GDM greeter:
https://git-tails.immerda.ch/greeter
I suspect it wouldn't be s ha
ds and its variants so that I
can use syslinux without using variables? Or is it ok with you?
5) Are you already doing this in your Debian Live based project ? How do
you do it?
Thank you for your feedback!
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Do
El 23/08/14 18:23, Daniel Baumann escribió:
On 08/23/2014 06:20 PM, adrian15 wrote:
Ok, I'll try to do my best. I have been impressed because there are way
many more rescue packages on these two lists than what I had thought of
originally.
that would be great, thank you very much.
g
directly to the kernel.
Does it make any sense to anyone of you?
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-live-requ...@lists.deb
#656135.
Feel free 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 UNSUBSCR
El 23/08/14 07:57, Daniel Baumann escribió:
On 08/23/2014 02:16 AM, adrian15 wrote:
A rescue task for tasksel means having a metapackage like:
task-lxde-desktop
but being named as: task-rescue ?
yes (or whatever the tasksel maintainers would name it).
Great.
If my assumption is right, do
in that task-rescue
metapackage.
Is there any other mailing list in Debian where other people might be
interested on the task-rescue package contents so that we ask there too?
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supe
l for lb_config so that it has
another manpage than I can finally check and issue a bug if grub2 is not
mentioned as an available bootloader?
Thank you.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/d
El 17/08/14 15:11, Daniel Baumann escribió:
On 08/17/2014 02:51 AM, adrian15 wrote:
which I suppose should be renamed to be:
# Checking stage file
Check_stagefile .build/binary_grub2
# Creating stage file
Create_stagefile .build/binary_grub2
no; iirc it used to be that we needed
El 17/08/14 15:07, Daniel Baumann escribió:
On 08/17/2014 02:55 AM, adrian15 wrote:
* Are ok
yes.
Interesting. So, probably, there are people using syslinux by default
and enabling installation but not seeing those entries at boot time.
* Should not be in grub2
they should.
Ok. So, that
El 17/08/14 15:06, Daniel Baumann escribió:
On 08/17/2014 03:37 AM, adrian15 wrote:
In one hand I want to be able to rename Debian Live distro into
Something distro by just changing one variable. And at the same time I
want that multi-live usb tools detect the iso as a Debian live so that
they
ll of these embedded code because Progress Linux
no longer uses it but only official Debian Live customisation procedures?
5) Is there (much?) more Progress Linux stuff ? (I have only checked in
live-build package. /usr/lib/live/build directory).
Thank you.
adrian15
--
Support free software.
usb tools detect the iso as a Debian live so that
they don't have to implement their code for each and everyone of the
Debian derivatives.
In the other hand I want a define a final way of setting up bootloaders
config in an bootloader-agnostic way.
Thank you.
adrian15
--
Supp
=true
priority=critical ${APPEND_GI}"
But I have also noticed that:
/usr/lib/live/build/binary_syslinux
does not seem to have these installation boot entries.
So the question is if these installation boot entries:
* Are ok
* Should not be in grub2
* Should also be in syslinux
?
So
to be:
# Checking stage file
Check_stagefile .build/binary_grub2
# Creating stage file
Create_stagefile .build/binary_grub2
As grub2 is not grub2 but grub version 2 I was asking myself if that
TYPO was made on purpose or if I should file a bug for it.
Thank you.
adrian15
--
Support free sof
ourse).
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. D
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
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
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 emp
El 15/04/12 12:00, intrigeri escribió:
Hi,
adrian15 wrote (15 Apr 2012 09:22:03 GMT) :
El 10/04/12 11:59, intrigeri escribió:
Shall we consider this action item (fromiso rewriting based on
findiso structure) as done, and close this bug?
If the fromiso option still works I think so too
Package: live-boot
Version: 3.0~a26-1
Severity: minor
Dear Maintainer,
Current findiso implementation should be improved.
What needs to be removed (and checked that it does not induces any
regression) is the part where:
/live/findiso is mount-moved to /root/live/findiso.
I'll try from
El 10/04/12 11:59, intrigeri escribió:
Hi,
adrian15 wrote (09 Apr 2012 18:43:54 GMT) :
I attach the splitted patches.
Thanks!
I've merged:
* fromiso_001_renaming.patch
* fromiso_002_use_live_fromiso.patch
* fromiso_004_fromiso_uses_is_mountpoint_function.patch *but*
tested after removing it just
to be sure that we aren't breaking anything.
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-live-requ...@lists.debian.org
live/image and /root/live/image that do
not seem to be used (just rgreped for /live/image). I might open a new
bug for this but I'm not sure.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donat
t it in the first place so that you can access the
iso contents and copy them to RAM.
Once the content is copied to the RAM the iso is unmounted so, as its
explained in a comment in the code, you can fsck the underlying device
(Which I suppose gets umounted later, haven't checked that)
El 09/04/12 09:46, intrigeri escribió:
Hi,
adrian15 wrote (08 Apr 2012 20:54:39 GMT) :
But according to current fromiso implementation it would seem that
you have to check exactly the same directory as the one
you're umounting.
I'm not very sure about this reasoning so please tak
It seems I made a mistake when submitting the patch.
I attach the correct patch which only patches what I had originally
described.
Sorry for that.
adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org
Package: live-boot
Version: 3.0~a26-1
Severity: minor
Dear Maintainer,
I am trying to improve fromiso boot parametre current code.
I attach a patch that:
a) Rewrites it to its code structure is as close as findiso one. This
implies that the /live/fromiso (previously called /isofrom) folde
El 08/04/12 20:33, intrigeri escribió:
tags 656135 + fixed-upstream
thanks
Daniel Baumann wrote (08 Apr 2012 11:29:28 GMT) :
intrigeri, ack for applying it?
Applied in Git, with a few improvements as follow-up commits.
Thanks adrian15!
Cheers,
While trying to improve fromiso/isofrom
El 08/04/12 20:33, intrigeri escribió:
tags 656135 + fixed-upstream
thanks
Daniel Baumann wrote (08 Apr 2012 11:29:28 GMT) :
intrigeri, ack for applying it?
Applied in Git, with a few improvements as follow-up commits.
Thanks adrian15!
Cheers,
The changes seem fine to me.
Thank you
1 - 100 of 108 matches
Mail list logo
