Hi,
i would like to learn how GNU xorriso can make
use of GRUB.
Are there any specs available, or an example
of a GRUB enhanced ISO 9660 image that boots
from CD on PC BIOSes ?
I know about ECMA-119 (ISO 9660) and El Torito
CD booting specs, but few about GRUB.
In january 2010 Robert Millan
Hi,
Your question is how to make a cd with grub on it ?
Yes.
GNU xorriso is like cdrtools + growisofs in
one single binary.
My question about GRUB on CD shall improve the
mkisofs-like aspect of xorriso. I am able to
influence ISO image production in any detail.
But i need instructions how to
Hi,
GRUB2 iso generated with grub-mkrescue is a bit special: it can be boot
as either CD, HDD or floppy. For CD boot it follows El Torito no
emulation boot.
Ahum ... grub-1.98/util/grub-mkrescue.in :
iso_uuid=$(date +%Y-%m-%d-%H-%M-%S-00)
grub_mkisofs_arguments=${grub_mkisofs_arguments}
Hi,
Drake Donahue wrote:
Attached is a script I use to make a legacy grub booting cd that
provides an alternate way to boot the system it was built on.
[...]
mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot -boot-load-size 4
-boot-info-table -o grub.iso iso
This resembles a reply of
Hi,
Vladimir '?-coder/phcoder' Serbinenko wrote:
- Is it possible to declare the whole iso for hard-disk emulation for
providing emulating image for buggy BIOSes
libisofs.h describes type ELTORITO_HARD_DISC_EMUL
with API call iso_image_set_boot_image().
Hi,
Drake Donahue wrote:
mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot -boot-load-size 4
-boot-info-table -o grub.iso iso
run the script it generates the image, presuming on a linux system
Regrettably i cannot spot stage2_eltorito on my
SuSE 10.2 (which has such files but not
Hi,
The urge to upgrade might earn you a whining user.
Well, if you develop you have to use current version (IMO).
Sure. As long as i occupy your time i will follow
your proposals.
Nevertheless, at some point i will have to look
at older versions. After all, 1.96 is distributed
with the
Hi,
i have roughly implemented the missing options
of grub-mkisofs in xorriso and am now comparing
the results.
The ISO image by xorriso boots from CD and from
USB stick. Are there other media types which
would impose a further challenge ?
If so: are there testers who would be willing
to try my
Hi,
Are there other media types [...] ?
Floppy. (supported for image sizes smaller than 1.44 MiB)
[...]
We probably need a way to choose a subset of modules for floppies
If i squeeze out the overhead, then xorriso
writes 754 * 2048 bytes rather than 757 * 2048
by grub-mkisofs.
At the end
Hi,
Now it's enough to replace grub-mkisofs with xorrisofs.
What about operating systems other than GNU/Linux
and FreeBSD ?
I have running a version of grub-mkrescue which
can deal with grub-mkisofs, genisoimage, and
xorriso. (genisoimage without
--protective-msdos-label and
Hi,
me:
What about operating systems other than GNU/Linux
and FreeBSD ?
Seth Goldberg:
I agree, selfishly :).
Do you use some of the other OSes ?
If so, would you mind to try what happens if
you do
tar xzf xorriso-0.5.3.tar.gz
cd xorriso-0.5.3
./configure
make
xorriso/xorriso
Hi,
I've tested it on FreeBSD and grub-mkrescue worked fine with xorrisofs
except:
1) you need to use gmake instead of make
What FreeBSD version is this ?
I test building of xorriso on own FreeBSD 8 and
remotely on FreeBSD 6. My own ones are quite
vanilla. Especially the 8-STABLE.
Do you
Hi,
What FreeBSD version is this ?
8.0
./configure gmake
instead of
./configure make
Strange. I run 8-RELEASE and 8-STABLE because
of SATA differences. No problems with make.
What are the negative symptoms on your system ?
I know the [iconv] complaint. It is harmless.
I know, just
Hi,
many thanks for testing xorriso in new
situations.
1) It tries to build even if no iconv is present
The tests in configure.ac resp. acinclude.m4
are too lax, obviously. They aim for finding
out whether one needs -liconv or not. But they
don't assure that iconv() works.
I will have to
Hi,
I think what you should check for is iconv.h since this missing header
caused compilation problem.
I have become quite radical and make a
test compilation and linking of all *.h
in libisofs/util.c and the basic iconv functions.
If that fails, then ./configure aborts after
reporting.
The
Hi,
when i've tried to compile xorriso on MacOSX 10.6.2
i have this error during
the link:
Undefined symbols:
_history_list, referenced from:
_Xorriso_status in xorriso_xorriso-xorriso.o
...
If i add #undef Xorriso_with_readlinE to xorriso.c, i can compile it.
It looks as if the
Hi,
Yves Blusseau wrote:
I have the latest readline library (6.1) installed on my MacOSX
/opt/local/lib/libreadline.a
But i think configure have tried to use the one in the standard path
(/usr/lib):
Perhaps i can use an option of configure or environnement variable to
force the linker ?
Hi,
Vladimir Serbinenko wrote:
You need to add CFLAGS=-I/opt/local/include too.
Good point.
I hope it is already clear that such
manipulations are very experimental.
optimally there should be a configure option for this.
libreadline is not urgently needed.
It is just a convenient capability
Hi,
Yves Blusseau wrote:
http://www.mail-archive.com/autoc...@gnu.org/msg13241.html
there a VL_LIB_READLINE macro
Ahum. A whole family of libraries.
Not only libreadline but also libedit, and
libeditline. This can become as interesting as
the situation with iconv.
But to our luck, libreadline
Hi,
Vladimir Serbinenko:
efi booting [...] it's basically standard no-emul
eltorito except:
platform_id[0] = 0xef;
I assume you mean the Platform ID as of El Torito
specs about the Boot Catalog and its Validation
Entry. (Chapter 2, figure 2)
That should be easy to test.
In
Hi,
I attach the patch I used for dirty checks
Oh. You already tested.
And ? Did it boot ?
Just yesterday i moved that setting from option
-b to option -boot-info-table,
Thanks.
Even better: i now tested that omitting
-boot-info-table really prevents the patcher
function.
Why not to
Hi,
Ok, legacy :(. But --efi-boot would have no legacy.
--efi-boot will be all at your service. :))
The more definite your wishes, the more swift
their implementation.
Maybe we should call it --efi-grub-boot just
to make clear whom it cares for ?
Shall the --efi* option have any influence on
Hi,
i have to correct myself:
The boot catalog of grub-mkrescue has no ISO-path
anyway (no option -c).
There is a boot catalog path in grub-mkrescue.
-c /boot/grub/i386-pc/boot_catalog
Have a nice day :)
Thomas
___
Grub-devel mailing list
Hi,
as this is mainly a GRUB inspired release, i spam
grub-devel by an announcement.
xorriso-0.5.4 offers the grub-mkisofs features
which are used by grub-mkrescue 1.98.
For general info about xorriso see
http://www.gnu.org/software/xorriso/README_xorriso
Hi,
i took a look at grub-mkrescue.in with EFI and
implemented the EFI-only case in xorriso-0.5.5
timestamp 2010.04.20.103448:
--efi-boot FILESet El Torito EFI boot image name and type
Currently -b and --efi-boot override each other.
Who comes last will win.
--efi-boot is not yet
Hi,
i have scruples about the semantics of
Platform ID which is global to the whole boot
catalog.
Section header specifies the platform id of section entry
Oh. Somehow i oversaw that.
[detection of capabilities of xorriso version]
What about checking error status of xorrisofs --foo
Hi,
the fresh development upload of xorriso-0.5.5
with timestamp 2010.04.22.160615 implements the
wish about --efi-boot :
Vladimir Serbinenko wrote 17 Apr 2010:
I would like to have efi+bios cd with 2 eltorito
entries: one with platformid=0 and another one with platformid=0xef.
[...]
I would
Hi,
Seth Goldberg wrote:
BTW, See Fedora's genisoimage for a good example of how they do it.
http://fedoraproject.org/wiki/User:Pjones/BootableCDsForBIOSAndUEFI
Thanks for the hint.
Ahum ...
-eltorito-alt-boot -e images/efiboot.img -no-emul-boot
In man mkisofs of 2.01.01a64 and in
Hi,
Vladimir Serbinenko:
I've tested xorriso version : 0.5.5 Version timestamp :
2010.04.22.221241 and it worked fine.
So my Sector Count unit of 512 bytes is ok
until other info emerges. (The Fedora wiki
gave me doubts.)
I am busily refactoring the xorriso level of
boot options. This
Hi,
i have uploaded
http://www.gnu.org/software/xorriso/xorriso-0.5.5.tar.gz
with version timestamp 2010.04.29.133234.
It can now process up to 32 different boot
images, with all El Torito parameters
adjustable (if anybody finds a use for them).
This is a release candidate as far as boot
Hi,
Colin Watson wrote:
I don't know how well
BIOSes handle MBR partition tables on CD-ROMs.
According to ECMA-119 (aka ISO 9660) the first
32 kB of an image are System Area with
arbitrary custom content.
El Torito specs mention that this area may
contain a bootable disk image. (Figure 1,
case
Hi,
i sent this message 4 hours ago but it did
not show up yet. So i send it again on the risk
to produce a duplicate.
While my local bzr upgrade problems still persist
i can view grub-mkrescue.in at
Hi,
while my local bzr upgrade problems still persist
i can view grub-mkrescue.in at
https://code.launchpad.net/~vcs-imports/grub/grub2-bzr
xorriso -pathspecs on -as mkisofs
I would make this
xorriso -report_about HINT -as mkisofs -graft-points
Option -report_about HINT will reduce
Hi,
- Option --diet saves about 400 kB of image
size without losing much benefit.
If it doesn't lose much,
why would it not be the default?
Maybe one should revert the default and offer
an option
--multi-session-toc
instead ?
Or, put another way, why would
somebody want to turn
Hi,
Isaac Dupree wrote:
What size range are the whole images?
The minimum output of grub-mkrescue 1.98 with
xorriso is 1544192 bytes.
grub-mkisofs: 1550336
genisoimage: 1859584 (-307200 with -no-pad)
One may add lots of other files, of course.
Also I guess no one compresses whole ISOs
It
Hi,
reviewing my grub-mkrescue 1.98 test script
i see these options which will cause the files
in /boot to have low block addresses:
xorriso ... -as mkisofs ... \
--sort-weight 0 / --sort-weight 1 /boot \
...
The boot catalog gets a low LBA by default.
I remember Vladimir mentioned
Hi,
Is MMC-2 subclass of cardreaders?
If you are looking for the SCSI command set used by ATAPI CD-ROM or DVD
devices then you should go to the T10 site and find the MMC or MMC-2
Yes, MMC is the CD/DVD/Blu-ray part of SCSI.
Released is MMC-5 meanwhile. MMC-6 is the current
development
Hi,
Colin Watson wrote:
[...] embedding area [...]
(setup): When embedding the core image in a post-MBR gap, [...]
Aka hidden blocks ?
several people followed up to say that GRUB shouldn't be
using the embedding area because it was never defined to be used for
anything in particular and
Hi,
today i downloaded by:
bzr branch http://bzr.savannah.gnu.org/r/grub/trunk/grub
Building it on a Debian 5.04 GNU/Linux with gcc 4.3.2 failed:
$ make
...
cc1: warnings being treated as errors
disk/mdraid1x_linux.c: In function 'grub_mdraid_detect':
disk/mdraid1x_linux.c:108:
Hi,
Josh Triplett wrote:
Do you know if the approach you use for hybrid images could also work
(with adaptation) for the existing hybrid images bootable via USB or CD
.iso? I'd love to create combination images which can work via all the
methods you mention and also work as a CD .iso.
Hi,
since more than a week, my mail discussion with Vladimir about
https://lists.gnu.org/archive/html/grub-devel/2012-01/msg00061.html
has stalled. (I did not see that mail in January but was pointed to
it by Vladimir a month ago. xorriso is now making progress on the issue.)
One question is
Hi,
Sorry, got busy last times. I've read your mail, just haven't answered
yet. Will try to do so today.
No further need to hurry. I just wanted to prevent a communication stall as
in january.
Vladimir: Can you confirm 0x41 ?
Yes, it is 41. I typoed once in first spec and corrected you
Hi,
i stumbled over a problem in the handling of grub-mkrescue
images on USB stick by Linux in /dev/disk/by-label.
The first MBR partition begins at 512-LBA 1 and thus is
not mountable as ISO image. I understand this is intentional.
ISO filesystems have a label (Volume Id) which gets used
for
Hi,
Noce to hear from you.
I am always watching here for any problems with ISOs.
LBA 0 is not an option.
Thanks for confirming this (once again).
It turned out that /dev/sdb1 is link target in ./by-label
with any partition start LBA. Lack of brains.
So the last hope is the double
Hi,
Isn't this HFS+ catalog sufficient for the problem at hand?
I see the misleading link to /dev/sdb1 with Debian 6
and with a Debian 7 based distro. Dunno which udev rule
first looks at /dev/sdb for an ISO PVD and then links
./by-label to the first partition of that device.
The filesystem
Hi,
So it's bug in Debian, not in xorriso?
xorriso is not at fault. It only follows orders.
It's in our git repo in util/
Yes, i know. But obviously there are older versions around.
For re-tinkering the image it would be helpful to know
the options used.
grub-mkrescue.c is C one.
Oh. I
Hi,
i believe to have found the udev rules in Debian 6 which
govern the population of /dev/disk/by-label.
File
/lib/udev/rules.d/60-persistent-storage.rules
has
# probe filesystem metadata of disks
KERNEL!=sr*, IMPORT{program}=/sbin/blkid -o udev -p $tempnode
...
Hi,
Andrey Borzenkov:
I confirm this. The culprit is this rule in 60-persistent-storage.rules:
# for partitions import parent information
ENV{DEVTYPE}==partition, IMPORT{parent}=ID_*
I'm not really sure how exactly to fix it. [...]
I'm interested in which information actually needs to be
Hi,
Is there an upstream with whom one could discuss this issue
Yes. It was on Cc on my message; you removed it.
Sorry. I did not notice and did not copy it.
I'll subscribe there and post a short version of my previous mail.
Have a nice day :)
Thomas
Hi,
+mkrescue_args=${mkrescue_args} -- -no-pad
This -- is most probably not what you want.
man grub-mkrescue says (and xorriso indeed does it):
Option -- switches to native xorriso command mode.
But -no-pad is not a native xorriso command.
$ xorriso -as mkisofs -- -no-pad
throws
Hi,
mkrescue_args=${mkrescue_args} -no-pad
This doesn't work for me:
./grub-mkrescue: invalid option -- 'n'
So the documentation seems not to match the implementation.
http://git.savannah.gnu.org/cgit/grub.git/tree/docs/grub.texi
All arguments not explicitly listed as
Hi,
xorriso -list_delimiter +xorriso-native+
It comes to me that it would be easier to document that the
first -- brings you out of grub-mkrescue option interpretation
and that the second -- brings you into xorriso native command
mode.
I.e. no change in grub-mkrescue, no -list_delimiter
Hi,
There is no second --. grub-mkrescue --help tries to say, that
everything after -- is simply passed on to xorriso. What is
confusing, is or any of the mkisofs options in previous sentence
which implies that -- is not needed.
It used to work the way which is still in the docs.
See
Hi,
I think it is enough to say that everything after first -- is passed
onto xorriso. The fact that second -- will enter native xorriso is
documented in xorriso manual; anyone who would like to make use of this
feature probably knows it.
This becomes quite confusing by the fact that even
Hi,
Vladimir Serbinenko:
Hm, that's annoying that xorrisofs has single-dash long parameters.
Inherited from mkisofs for the emulation.
(xorriso native commands are recognized with as many dashes
as you want.)
I could make it tolerate double-dash if this is desired.
Perhaps we shouldn't use
Hi,
i recently advertised grub-mkrescue as replacement of
script snippets for creating ISO images with legacy GRUB.
But it is not very appealing to the audience if i have
to mention the different interpretation of argument --
by the shell script of GRUB-2.00 and by the C program
of the git
Hi,
Andrei Borzenkov wrote:
Care to send a patch for both help output and documentation?
First one should decide whether the incompatible CLI change
is really intentional.
If the change is intentional, there should be some assistance
to those people who based their scripts on the old
Hi,
how about this:
-
The C program gets renamed to grub-mkiso.c. The binary gets
installed under two names: grub-mkiso and grub-mkrescue.
If started as grub-mkiso the program implements the change in
the CLI. I.e. -- marks the
Hi,
me:
grub-mkiso.c
Andrei Borzenkov:
What's the point of having to maintain two versions instead of one?
Well, as stated:
This would avoid to bother scripting users of grub-mkrescue
or maintainers of things like
http://www.unix.com/man-page/linux/1/GRUB-MKRESCUE/
Besides
Hi,
to substantiate my proposal of renaming young grub-mkrescue.c to
grub-mkiso.c and to add a built-in emulation of grub-mkrescue(.in),
here the necessary code which i tested standalone with valgrind.
The decision which parser to use would be made in main():
Hi,
Well, below is much more simple patch which is reusing argp
infrastructure. The only problem - it needs small patch for gnulib
otherwise --help does not work. IMHO this is a bug in gnulib. If you
convince them to fix it ...
Me ? I cannot even convince you or Vladimir :))
I understand
Hi,
Vladimir Serbinenko:
I think that old parser is better. The only reason the change happened
is that it's a bug that sneaked in during migration to C. It should be
fixed.
Andrei Borzenkov:
[...] Nor do I actually like pass anything you
do not understand - it has potential to break if
Hi,
Andrei Borzenkov wrote:
Not eltorito, but normal ESP.
That's somewhat appeasing.
returning (hd0,gpt2) would also be wrong here - ESP on CD image is
empty, we need to somehow jump from ESP to full ISO image.
One could allow nested partitions and put whole-ISO partitions
into the various
Hi,
Vladimir wrote:
I think his EFI uses eltorito even from the stick. In that case we end
up in exactly the same scenario as CD-ROM.
This contradicts all my beliefs about El Torito
(and several wikis where i published them).
I would like to see this theory verified:
The first experiment
Hi,
i inspect the image by
xorriso-1.3.8 -indev test-efigrub.iso \
-report_el_torito plain \
-report_system_area plain
and get
Boot record : El Torito , MBR protective-msdos-label cyl-align-off GPT APM
...
Volume id: 'PCBSD_INSTALL'
El Torito
Hi,
(i wonder why the original mail from Dietmar Maurer does
not show up in grub-devel archives or my mailbox)
Dietmar Maurer wrote:
After reverting the following commit everything works again:
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=cf47a2fba5852014bc59959c5e357e8313933414
Hi,
Dietmar Maurer wrote:
It is quite easy to detect if there is a '--' in the argument list.
So you could disable magic code if you find '--'?
It is about an unintended but actually beneficial change
in the syntax of grub-mkrescue arguments.
New grub-mkrescue.c interpreted and consumed the
Hi,
Would it help if you use '---' as separator?
grub-mkrescue could execute xorriso command
-list_delimiter ---
before command -as.
But that would not solve the problem of old ambiguous
and new unambigous CLI which are not compatible.
Further it would make it even more difficult to
Hi,
Vladimir wrote:
In all I kinda like
that grub-mkrescue would be drop-in replacement for xorrisofs/mkisofs
with additional boot semantics. Unfortunately it requires additional
discipline of avoiding option clashes like this one.
You would have to reserve option names within xorriso's
Hi,
We need for compatibility:
-o
--output
This is an intentional interference because grub-mkrescue -o
is supposed to overload mkisofs -o.
--output is not a mkisofs alias of -o, but rather -output.
So in order to keep grub-mkrescue users from circumventing
the overloading, grub-mkrescue
Hi,
Can we have --grub* space?
No hard collision to see in the man pages of xorriso and xorrisofs.
Except the word grub with command -boot_image,
there are only some--grub2-* options of -as mkisofs:
--grub2-boot-info
--grub2-mbr
--grub2-sparc-core
All three are supposed to be under
Hi,
Folks, I really suggest to bite the bullet and switch to argp.
I already gave in to your reasoning for the better CLI. :))
But since Vladimir is not yet annoyed enough by the consequences
of the grub-mkrescue CLI, i provide my part of our cooperation.
(I am with Vladimir that
Hi,
Andrei Borzenkov wrote:
Drive current: -indev '/datastore/iso/openSUSE-13.2-DVD-x86_64.iso'
[...]
You may consider using xorriso to create image, it does quite good job
with hybrid images.
Thanks for the compliment. (The openSUSE ISOs are not made by
xorriso, though, but rather by
Hi,
not that i would want to interfere with GRUB2 development
decisions. Nevertheless, i have some comments from the view
of the specs.
Vladimir Serbinenko wrote:
El torito catalog contains bootable binaries.
UEFI 2.4 9.3.6.2 CD-ROM Media Device Path
The CD-ROM Media Device Path is used to
Hi,
John Lane wrote:
My natural inclination is to reach for -v when I want verbose output
Same for me. -v for version seems odd.
(I am spoiled by archivers and data transfer programs.)
But since it is the old CLI, one would have to declare that
one obsolete and start a new rectified one.
Hi,
Andrei Borzenkov wrote:
> I am not sure we should stretch reproducible builds that far. ISO
> image created by grub-mkrescue is not binary.
I was approached by Debian's reproducible-builds project because
they wanted to be able to create reproducible test ISOs.
Hi,
Alexander E. Patrakov wrote:
> The first thought, though, is related to the fact that the Porteus Kiosk
> image uses partitions aligned to 1 MB. It may be a good idea to force this
> on grub-mkrescue command line and test-boot the result.
That would be xorriso -as mkisofs options
Hi,
sorry, i misposted this answer to bug-grub, rather than grub-devel.
With the wrong subject, too. Internal thread error.
-
Andrei Borzenkov wrote:
> Attempt to mount third GPR partition as HFS+ results in failure.
> Additionally
Hi,
i wrote:
> > The HFS+ failure is due to APM block size 2048.
> > Linux has 512 hardcoded.
Andrei Borzenkov wrote:
> No, it has not.
Seems to fixed meanwhile, indeed.
I patched away MBR partition table and GPT. After that, the partition
/dev/sdb3 does mount. (sdb1 is the APM partition
Hi,
> BTW is xorriso available from single GIT repo?
For historical reasons the software is scattered over a bzr repo
for libisofs and a svn repo for libburn and libisoburn.
bzr branch lp:~libburnia-team/libisofs/scdbackup ./nglibisofs-develop
svn co
Hi,
i hopefully identified the cause of the i/o error with kernel
message
[ 359.020970] hfsplus: walked past end of dir
It seems to be an original mistake by Vladimir (who normally
makes much less mistakes than i do).
Since Andrei is surely more familiar with Vladimir's coding habits
and
Hi,
sorry, i misposted this answer to bug-grub, rather than grub-devel.
With the wrong subject, too. Internal thread error.
-
Andrei Borzenkov wrote:
> Attempt to mount third GPR partition as HFS+ results in failure.
> Additionally
Hi,
i am discussing with Chris Lamb on reproducible-bui...@lists.alioth.debian.org
how to make production of bootable ISOs reproducible. The last (yet known)
obstacle are the pseudo-random GUIDs of the GPT which is produced for EFI
bootability.
Up to this obstacle it turned out that it will
Hi,
after having freshly re-read the specs of UEFI and RFC4122,
here is some nitpicking:
Steve Kenton wrote:
> > 3F2504E0-4F89-41D3-9A0C-0305E82C3301
Andrei Borzenkov wrote:
> Usually GUIDs are displayed in lower case
RFC4122 prescribes to read them independently of case, but to produce
Hi,
Andrei Borzenkov wrote:
> as long as generated GUID has reasonable chance to be different from
> any other GUID on the system where ISO was booted, it should be good.
> For GRUB itself it does not matter anyway - it does not use GUID, so FS
> UUID collision is worse problem.
That's the
Hi,
i riddled over UEFI appendix A:
> > Do you mean that one has to interpret the statement of UEFI 2.4
> > "All EFI GUIDs (Globally Unique Identifiers) have the format described
> >in RFC 4122 [...]
> >It should also be noted that TimeLow, TimeMid, TimeHighAndVersion fields
> >in
Hi,
... still trying to make sense of the specs.
Andrei Borzenkov wrote:
> According to UEFI Appendix A it goes into 7-th byte (starting with 0) of
> binary representation of EFI GUID.
Do you mean that one has to interpret the statement of UEFI 2.4
"All EFI GUIDs (Globally Unique
Hi,
i wrote:
> > i could not reliably determine where to put the version nibble.
Andrei Borzenkov wrote:
> According to UEFI Appendix A it goes into 7-th byte (starting with 0) of
> binary representation of EFI GUID.
And RFC 4122 with its big-endian representation puts it into byte 6.
>
Hi,
Colin Watson wrote:
> https://www.gnu.org/licenses/gpl.html#howto
One should emphasize that the FSF when designing new license versions only
considers compatibility to older FSF licenses if they bear the "or later"
clause.
E.g. it is not possible to combine GPL version 2 software with LGPL
Hi,
Ping.
(Bug or feature ? If bug: what exactly would be the desirable behavior ?)
--
Date: Wed, 14 Jun 2017 11:37:11 +0200
From: Thomas Schmitt <scdbac...@gmx.net>
To: grub-devel@gnu.org
Subject: grub-mkrescue
Hi,
i am discussing with Samuel Thibault two riddling issues of the new
Debian GNU/Hurd ISOs, e.g. this one of about 160 MB:
http://ftp.ports.debian.org/debian-ports-cd/hurd-i386/debian-hurd-2017/debian-hurd-2017-i386-NETINST-1.iso
Those ISOs are among the very few which use GRUB for booting
Hi,
Vladimir 'phcoder' Serbinenko wrote:
> Those are only for floppies with old BIOS. If your image is over 2.88 MiB
> and thus never useful on floppies, it's safe to overwrite.
This explains why it looks like somewhat plausible executable code
and why i386-pc/boot.img of Debian 8 is in the
Hi,
on occasion of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864701
"grub-common: grub-mkrescue does nothing, successfully"
i wonder whether the reaction of grub-mkrescue on xorriso problems
is intended and appropriate. E.g. with:
grub-mkrescue -o output.iso SOURCE
Hi,
SevenBits Tech wrote:
> it is my understanding that, yes, you are required to provide the
> source code used to build the compiled binary.
Agreed. But normally it suffices to point to the place from where one
got the published sources of the free software which one forwards.
E.g. with
Hi,
Tom Davies wrote:
> This might not be the best place to ask about legal issues for edge-case
> scenarios.
At least it would be the place to discuss what should be written in the docs.
The problem is quite specific to grub-mkrescue or people who equip computers
with GRUB and then pass them
Hi,
i read on
http://wiki.osdev.org/Bare_Bones#Building_a_bootable_cdrom_image
a cumbersome interpretation of GRUB's GPL for the case of publishing an ISO
with GRUB boot equipment. (See quote below.)
Is it really necessary to keep and publish the source package of the
binary distro package if
Hi,
i am unhappy about the state of the thread
http://lists.gnu.org/archive/html/bug-grub/2017-12/msg00010.html
"HP ProBook x360 11 G1 EE incompatible with grub"
which is about an EFI implementation which SYSLINUX for EFI can operate
from USB stick whereas GRUB from USB stick ends up with
Hi,
Daniel Kiper wrote:
> > 2) Create EFI System Partition (code EF00) using gdisk. 256.0 MiB will
> > suffice.
> > 3) Format EFI System Partition
> > # mkdosfs /dev/sdb1
> >
> >4) Create GRUB2 EFI bootable image
> > # mount /dev/sdb1 /mnt
> > # mkdir /mnt/efi/boot
> > # grub-mkstandalone
Hi,
I wrote:
> > Does this mean that the decisive trick is to use GPT with EFI partition
> > instead of a MBR partition of type 0xEF ?
Michel Bouissou wrote:
> So might this machine boot only from GPT disks ? Well, then it would'tn
> boot a Knoppix ISO image stick. But it does...
Yes, i
Hi,
Daniel Kiper wrote:
> IIRC you see blank screen after installing some distros. Right?
It also does not work when booting the ISO images which shall install
the systems.
E.g. debian-9.3.0-amd64-netinst.iso :
mount debian-9.3.0-amd64-netinst.iso /mnt/iso
mount /mnt/iso/boot/grub/efi.img
1 - 100 of 213 matches
Mail list logo
