Hi,
i'm the developer of xorriso. (Cc me, please)
Joey Hess wrote:
Assuming debian-cd does
switch to xorriso, so after it supports jidgo
We should begin to write down an exact specification of the jigdo
files which xorriso shall produce during the run by which it
generates an ISO image.
Hi,
Mark Weyer in Bug#420716:
Use case: I bought Debian DVDs from a vendor.
[...] the isos are padded when written to the medium.
How much padding was applied relative to the image ?
Just up to the next full 32 KiB ?
32 KiB alignment is a technical necessity with DVD. With BD it is 64 KiB.
Hi,
But after writing them on the DVD using K3b, Brasero, or GnomeBaker,
when I checked the integrity of the DVD using SHA256SUM they failed
This seems to be a neighbor of Bug#420716.
The advise given by Anne Bezemer should apply here too :
head --bytes=`isosize /dev/cdrom` /dev/cdrom |
Hi,
Dan Serban wrote:
I'd like to make a small change to the netinst iso.
Simply changing the Install menu item to include a few other options passed
to the installer process.
Is there an easy way to achieve this?
Steve McIntyre wrote:
Be aware: to make a working image using xorriso,
Hi,
some technical facts about name lenght in Debian ISO 9660 images:
Raphael Hertzog wrote:
What happens if you try to put too-long filenames on the CD with Joliet
enabled?
libisofs, which produces the Debian i386 and amd64 images, truncates
oversized Joliet names. Collisions get resolved by
Hi,
Alexander Reichle-Schmehl wrote:
xorriso -as mkisofs -o test.iso -J -joliet-long -graft-points \
/012345678901234567890123456789012345678901234567890123456789012345678901234
5678901234567890123456789=/some/file/on/disk
Didn't worked over here with an uptodate Windows XP. It
Hi,
Rui Ribeiro wrote:
I have downloaded the file debian-6.0.1a-i386-DVD-1.iso twice
yesterday. Also have checked the last time the file with md5sum. The
ISO doesnt work, it appears to be corrupted, on one server and my
personal Macbook Pro. However the md5sum is identical to your DVD
Hi,
The error is the following: The following disk image could not be
opened: debian-6.0.1a-i386-DVD-1.iso - no mountable file systems
We're using xorriso to generate hybrid CD
and DVD images for i386, and that may be what's throwing OSX;
One may remove all isohybrid aspects by zeroing
Hi,
I do confirm that after removing the isohybrid of the image, I am
able to mount it.
Whew. So xorriso's ISO 9660 data are not to blame.
Bad news is that obviously the mere presence of a PC-BIOS Master
Boot Record keeps the operating system from mounting the image.
This MBR sits in a region
Hi,
i still ponder about the supposed MBR allergy of the Macs.
Maybe one should make another test by transplanting the first 32 kB of
the i386 image into the first 32 kB of the sparc image.
If the allergy theory is right, then that should not mount any more:
dd if=debian-6.0.1a-i386-DVD-1.iso
Hi,
i wrote:
i still ponder about the supposed MBR allergy of the Macs.
If the allergy theory is right, then that should not mount any more:
dd if=debian-6.0.1a-i386-DVD-1.iso bs=2K count=16 test_mix.iso
dd if=debian-6.0.1a-sparc-CD-1.iso bs=2K skip=16 test_mix.iso
Rui Ribeiro:
I
Hi,
Rui Ribeiro:
It is confirmed debian-live-6.0.1-i386-standard.iso is mountable on my
Macbook.
Oh well. It really seems to be about -partition_offset 16.
Now the producers of isohybrid images have the choice between
mountable on Apple systems or bootable from USB stick on a
Kontron CG2100
Hi,
Steve McIntyre wrote:
Rui: I would suggest you file a bug with Apple about this.
Rui Ribeiro wrote:
I am submitting it at the moment as actually I am registered as an Apple
software developer.
As developer of xorriso i am much interested in helping with this issue.
our tracking number
Hi,
George Danchev wrote:
I guess this would be a nice entry for libburnia FAQ, targeting Apple users.
Done.
http://libburnia-project.org/wiki/FAQ#partition_offset_apple
I also mentioned the problem in wiki page
http://libburnia-project.org/wiki/PartitionOffset
and posted a warning to
Hi,
I got an Invalid or corrupt kernel message, but I don't understand why.
The ISOLINUX boot image /isolinux/isolinux.bin contains a text:
Invalid or corrupt kernel image.
If that appears then initial booting from the ISO image worked.
But obviously the booted loader cannot go on with booting
Hi,
It seems like the issue is the bsdtar command.Bsdtar morphs the
correct vmlinuz image into data.
[...]
After using 7z to extract the iso, all is working fine!
Aha. That would be a problem between libarchive and xorriso.
Maybe you should file a bug for bsdtar resp. libarchive and
cc
Hi,
maybe one should mention the following points in an
expert section:
- The whole isohybrid aspect can be removed by zeroing
the first 32 kB of the image.
Then it is a conventional CD bootable ISO image.
This solved the problem to mount on Snow Leopard systems.
Hi,
on occasion of this thread on debian-bsd list
http://lists.debian.org/debian-bsd/2011/07/msg00237.html
i would like to ask how much effort it is to make ISO images of
Debian GNU/kFreeBSD bootable from memory stick.
---
What i
Hi,
George Danchev wrote:
Thomas Schmitt has developed a new Debian ISO check script
Its main reason of being is that it reads the number of data blocks
from the ISO image and thus can truncate the data stream at the
end of the image when reading it from optical media.
Trailing garbage
Hi,
Luca Capello l...@pca.it wrote:
$ wget [...]/debian-6.0.3-amd64-CD-1.iso
[...]
$ gpg --verify MD5SUMS.sign
[...]
I am not a CD expert, so a simple question: if I burn the verified image
above (debian-6.0.3-amd64-CD-1.iso), do the following commands produces
an image that will match its
Hi,
Andrei Popescu andreimpope...@gmail.com wrote:
[1] I have no idea what checkreading is supposed to mean
With the optical media types DVD-RAM and BD-RE, the drives verify the
readability of the written data before they get overwritten in the drive
buffer. If not properly readable, blocks
Hi,
George Danchev wrote:
a) isosize and dd
b) check_debian_iso script Thomas has developed.
Besides, it doesn't address the checkreading which doesn't seem to be
an English word. Even if it is the technically correct term for what is
going on I doubt FAQ readers actually care and would
Hi,
George Danchev wrote:
Again, with proofreading (i.e. our former checkreading) we address the user
action of deliberate reading of an appropriate amount of bytes from the
burnt media (think 'dd'). This has nothing to do with the Defect Management
mechanism, which DVD-RAM and BD-RE drives
Hi,
i read on http://lists.debian.org/debian-devel/2012/01/msg00168.html
For optical media, I am not really sure: it may use ElTorito or load a
file /efi/boot/bootarch.efi from the ISO-9660 or UDF filesystem, so
this should be checked.
GRUB2 grub-mkrescue can produce (U)EFI bootable ISO 9660
Hi,
Regular El Torito then.
At least grub-mkrescue makes it that way. Better ask a grub-devel for
advise and options.
UEFI booting requires a GPT and a special partition, which would
probably be impossible to implement along with the MBR hack for hybrid
booting.
I am clueless enough to
Hi,
Ryan Braun wrote:
is there some kind of magic that needs to be done to the iso
in order to be able cat squeeze.iso /dev/sdb?
Steve McIntyre wrote:
-isohybrid-mbr syslinux/usr/lib/syslinux/isohdpfx.bin -partition_offset 16
Instead of syslinux/usr/lib/syslinux/isohdpfx.bin one may use
Hi,
Ryan Braun wrote:
Ok guys, having some trouble getting a working iso out of xorriso. It
generates an iso, but there are some warnings.
I do not see this option among your xorriso -as mkisofs arguments:
-boot-info-table
It is necessary for the ISOLINUX boot image to work properly.
The
Hi,
Ryan Braun wrote:
And for reference, here is the command I used to build
the image, as for all my googling I could not find an example of
using xorriso to make an image (outside of .disk/mkisofs that wasn't
working for me :) )
The image production command in .disk/mkisofs consists of a
Hi,
on occasion of april 1st i want to ask the foolish question
how these two lines get into debian-testing-i386-DVD-1.jigdo :
ShortInfo='Debian GNU/Linux testing Wheezy - Official Snapshot i386 DVD
Binary
-1 20120326-05:08 (20120326)'
Info='Generated on Mon, 26 Mar 2012 05:20:12 +'
Hi,
George Danchev wrote:
These data are all known prior to ISO/jigdo creation
and are indeed better to be passed via option parameters to the producer
itself (xorriso, resp. libjte), which is not implemented yet of course.
But this is a low-priority goal, isn't it?
Hi,
The output is huge because of the wget messages on the console, I think.
How can I mute only that ?
http://tldp.org/HOWTO/Debian-Jigdo/faq.html#WGETOPTIONS
you can make wget more quiet by adding --non-verbose to the wgetOpts
switch in your ~/.jigdo-lite file. If you want wget to print no
Hi,
I used the same wrong .iso image debian-testing-i386-DVD-1.iso created
Monday and above checked and I download again
debian-testing-i386-DVD-1.template and debian-testing-i386-DVD-1.jigdo.
So, I discovered that the MD5SUM check error was because missing a file in
.iso file !!!
I rather
Hi,
Successfully created `debian-testing-amd64-DVD-2.iso'
ERROR: Checksums do not match, image might be corrupted!
The first riddle is why the script says successfully created
and then reports a checksum mismatch.
It would be _very_ interesting to see the whole message output
of such a failed
Hi,
It will not boot on any machine.
This might be due to a problem in the ISO image or due to a mismatch of
boot record format and firmware of the machine.
I see that the image is equipped with an El Torito boot record.
No MBR.
The boot catalog begins at block 587 and bears 0 as Platform Id.
Hi,
My linux machine, Debian squeeze, had a catastrophic failure,
i.e. coffee vs. motherboard due to curious feline.
I am not sure whether a Debian Live CD allows to install the
xorriso package.
I know that the sparse rescue system RIPLinux contains xorriso,
as well as the other burn programs
Hi,
Fedora/RH folks recently added more
hacks to isohybrid to support booting on Macs:
http://mjg59.dreamwidth.org/11285.html
This is achieved by applying ISOLINUX program isohybrid from a recent
ISOLINYX version to the already produced ISO images. syslinux-4.05
should probably do.
It is a
Hi,
Steve McIntyre wrote:
(http://www.debian.org/releases/stable/amd64/ch04s03.html.en) but
skipped straight past section 4.3.1. Looks like we could do with a big
clear message DO THIS UNLESS YOU HAVE SPECIAL NEEDS to make it more
obvious. :-)
I am a bit scared by the catastrophic potential
Hi,
Francesco Poli wrote:
I've just read news [1] about the plan to drop business card CD images:
[1] http://www.phoronix.com/scan.php?page=news_itempx=MTEzNzA
Rick Thomas wrote:
Did someone use other than cd1 image?
The image
Hi,
Rick Thomas wrote:
When booting the Debian netinst powerpc installer from a USB flash disk you
may see a mesage
WARNING: Bootstrap partition type is wrong: Apple_HFS
type should be: Apple_Bootstrap
[...]
Any idea what makes it do that? Can if be fixed?
Apple_HFS is
Hi Steve,
i tested bootability of
http://cdimage.debian.org/cdimage/unofficial/efi-development/upload3/debian-wheezy-amd64-efi-test3.iso
on
GIGABYTE GA-MA74GM-S2H AM2
Athlon II X4 620 Quad-Core 4x 2.6GHz
which is probably not UEFI-ready.
At least it does not tell anything about EFI when
Hi,
me:
Further i see that fdisk -lu is once again unhappy with a xorriso
generated partition table. Probably because of -append_partition.
I will have to investigate.
Steve McIntyre:
Hmm, OK.
I investigated further. The ISO image is properly aligned to 1 MiB.
It is the FAT partition which
Hi,
I suppose there is another package containing zlib.h that needs to be
installed, but how to identify it?
Being only a casual booter of Debian, i use queries like this
on my test machine (squeeze 6.0.2):
$ apt-file search zlib.h
...awful.lots.of.matches...
zlib1g-dev:
Hi,
It also seems to have some kind of GPT table, [...]
What tools did you use to get from the file structure on disk to
the hybrid image? Did you use isohybrid --uefi from the syslinux
package, or something else?
The hybrid aspects are generated by xorriso along with the
ISO image. No
Hi,
i did with the current snapshot of xorriso-1.2.9 with version timestamp
2013.05.07.185653 :
xorriso -indev /dvdbuffer/debian-7.0.0-amd64-netinst.iso -toc
to learn
...
Volume id: 'Debian 7.0.0 amd64 1'
...
Boot record : El Torito , ISOLINUX isohybrid MBR pointing to boot image
Hi,
i forgot to mention that gdisks statement
MBR: MBR only
...
GPT: present
is a consequence of the intentional violation of GPT specs
by the presence of a valid MBR partition of type 0xef instead
of a protective MBR partion of type 0xee.
Further, the MBR partiton which describes the
Hi,
i wrote:
[real MBR combined with GPT] [MBR partition type 0x00]
One will have to watch out whether these violations, or the fact
that MBR partition 2 is nested in MBR partition 1, cause any
trouble.
Andreas Heinlein wrote:
Do you think this might cause trouble, i.e. older machines
Hi,
Philip Charles wrote:
When using xorriso 1.2.9 the log file does say 650 Mib 332031 2k blocks
BUT about every 650k or so 'xorriso -as mkisofs ..' tries to run and fails
and the build goes onto the next 650k. This happens 63 times which
squares with the final image size.
With xorriso
Hi,
Philip Charles wrote:
With xorriso 1.2.2 the build stops at 650k.
What happens if you use the same xorriso version as was used
for the Debian release ?
http://www.gnu.org/software/xorriso/xorriso-1.2.6.tar.gz
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to
Hi,
Philip Charles wrote:
Are thes helpful?
libisofs: MISHAP : Cannot patch isolinux boot image
xorriso : FAILURE : Failed to prepare session write run
The message Cannot patch isolinux boot image is issued on
several occasions. Most of them would be accompanied by
messages other than you
Hi,
http://www.gnu.org/software/xorriso/xorriso-1.2.6.tar.gz
Works nicely. Boots off usb stick. Using 1.2.6.
Now this puzzling.
Hope to get onto
'xorriso -abort_on FATAL -report_about ALL -as mkisofs ...'
tomorrow.
Please send me the output of runs with each of the three versions
Hi,
there goes my theory with the missing -b option.
I will have to make experiments. Possibly i will have to ask for
adding image inspection commands after the -as mkisofs options.
Hopefully i have some insight this evening.
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to
Hi,
it is reproducible now. The current release 1.2.8 is affected, too.
1.2.6 indeed works.
Thanks for reporting.
I will give you a note when i found out how i managed to spoil it.
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of
Hi,
the regression was introduced by
http://www.libburnia-project.org/changeset/4985
in xorriso/write_run.c lines 2361 to 2365.
I can get
xorriso-1.2.9 -as mkisofs -print-size -b ... -isohybrid-mbr ...
to work by re-instating the call of Xorriso_genisofs_add_boot()
if -print-size was given:
Hi,
hopefully
http://www.libburnia-project.org/changeset/5039
fixes the problem with xorriso-1.2.[89] and -print-size without
introducing new bugs. The change is small and in theory should
only affect the buggy case. In theory ...
I would appreciate if this could be tested during the next
Hi,
Built wheezy images for i386 and amd64 and they
booted of CDs and flash drives. ;)
Good to know.
To Steve McIntyre:
Is there a chance to get it tested on the Debian ISO production
machine within the next few days ?
Else i would now begin to prepare the next release.
Have a nice day
Hi,
I've been trying to install using the XFCE CD on a zx6000. The boot
rom doesn't recognise the CD as being bootable.The netinst CD does
work.
Google zx6000 ... Itanium CPU ... would that be ia64 ?
http://cdimage.debian.org/debian-cd/7.0.0/ia64/iso-cd/debian-7.0.0-ia64-netinst.iso
Hi,
i see that had a surplus i in the arguments of the xorriso run
for repacking the image:
-b /boot/boot.img -no-emul-boot -boot-load-size i0 \
This should have been
-b /boot/boot.img -no-emul-boot -boot-load-size 0 \
The program run with i0 succeeds but creates El Torito as
with
Hi,
me:
already half on the way to EFI ?
Peter Chubb:
It has always used EFI --- EFI was rolled out first to Itanium.
Shouldn't the El Torito Validation Entry bear a Platform Id of 0xef
then ? (That would be xorriso -as mkisofs option -e rather than -b.)
Id 0xef is not mentioned in El Torito
Hi,
Eugene Paskevich wrote:
dmesg shows the following error:
attempt to access beyond end of device
sr0: rw=0, want=XXX, limit=YYY
where YYY is constant and less than XXX.
If i understand you correctly then the ISO image shows no such
problems when mounted by an already running Linux system.
Hi,
[with] debian-7.2.0-i386-lxde-CD-1.iso /dev/sdb
[...] debian-live-7.2-i386-lxde-desktop+nonfree.iso
I can re-format the free space present on usb
These two images have MBRs with partition 1 beginning at
block 64 (= 32 KB). See e.g. output of
/sbin/fdisk -lu
Hi,
correcting myself:
One may test this theory by setting byte 448 of the isohybrid
result to 1 and byte 454 to 0.
Byte 448 would have to become 65, and byte 454 become 64,
of course. (Currently they are 1 resp. 0)
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to
Hi,
antispammbox-debian wrote:
Then isohybrid does not produce a true hybrid file, because once written,
cannot re-format the space free on usb!
Well, firstly the isohybrid program of ISOLINUX is The Original.
The isohybrid functionality of xorriso was implemented under the
guidance of the
Hi,
i would still like to see confirmation whether a non-zero
partition start indeed makes the USB stick acceptable for
Gparted again, after it was made unacceptable by program
isohybrid.
antispammbox-debian wrote:
Why an iso file is iso file, and a file isohybrid is isohybrid?
What is the
Hi,
since IA64 is said to boot via EFI, you'd probably need a GPT
(with protective MBR).
Do you have a particular system at hand which would boot
via MBR or GPT ?
Are you apt to equip the ISO image with a GPT which contains
an EFI System partition that points to the file /boot/boot.img ?
(First
Hi,
I am also a bit curious to know how the information regarding which
versions of software were used to create the .ISO . It seems this
info. is embedded in the .iso generated
xorriso by default writes its version info into the Preparer Id
field of the ISO Primary Volume Descriptor
Hi,
because debian-cd also records the arguments of its xorriso run,
it should be not too hard to repack it with a newer xorriso,
which produces better GPT. E.g. xorriso-1.3.2 from Debian Sid.
You will need to copy the MBR from the original ISO
dd if=debian-7.3.0-amd64-netinst.iso bs=512
Hi,
while looking for test images with boot sectors for mips and mipsel,
i notice that
http://cdimage.debian.org/debian-cd/7.4.0/mipsel/iso-cd/debian-7.4.0-mipsel-netinst.iso
delivers an ISO image without any boot sector.
The file
.disk/mkisofs
inside the image does not show the option
Hi,
it is embarrassing to see the own bugs mummified since a
full year. You should rather enjoy the fresh and juicy bugs
of version 1.3.6.pl01.
Funnily nobody complains that the wrong GPT header checksum
would prevent booting from USB stick via EFI.
Doesn't (U)EFI check ? Do all tested machines
Hi,
We stopped building d-i for any of the older mipsel hardware that
booted off CD quite a while back, in fact.
I found a boot sector in debian-40r0-mipsel-businesscard.iso
from 2007.
So my collection of Debian ISO examples is complete now.
(When i am done with my new boot sector assessment
Hi,
the bug in question is supposed to have existed in upstream until 1.3.4?
No.
It was introduced by 1.2.4 and fixed by 1.3.0.
So the version in Debian testing should be ok.
It's just that xorriso-1.3.6.pl01 is the newest upstream release,
which i would of course like to see in Debian testing.
Hi,
in january we had a conversation about xorriso and PALO.
I implemented the boot sector as learned from genisoimage:
version number 4 and the short command line at byte 24 to 151.
Further there is the proposed version 5 with long command line at
byte 1024 to 2047, and the yet unexplained
Hi,
Because our discussion stalled, i did not publish the enhancements
of libisofs API and xorriso CLI with the recent release 1.3.6.
That's really sad!
It would have been easier for me, if you would have added them, even
if they were not perfect.
Ah no. It's a tiny bit inconvenient. You
Hi,
looking at your description of ipl_entry computation
- after midnight - makes me search for alternatives.
I would have to duplicate a non-trivial part of PALO
which then would have to be validated against the
original code. From then on, i would have to maintain
it without having much clue.
Hi,
Because of how palo is built, it ensures, that the entry point is always
zero.
That's very convenient for all of us.
I will test your xorriso as soon as possible.
Lemme check whether defining the macro
Libisofs_enable_unreleased_hppa_palO
in libisofs/libisofs.h of the current GNU
Hi,
i am sending this only to debian-cd, as it is not specific to
the bugs 740504 and 743879.
Steve McIntyre:
Please shout if you want me to change to another newer version, e.g. for the
hppa changes that you've been talking about elsewhere.
Well, 1.3.6.pl01 is the current one. I must of
Hi,
uploaded is a new (semi-stable) development snapshot
http://www.gnu.org/software/xorriso/xorriso-1.3.7.tar.gz
with the new features for PALO on HP-PA, which are now promised to
stay compatible in future releases.
MD5: 961939a15cdb2b9893fbe25f453d9ac4
Version timestamp :
Hi,
the proposed patch for the boot sector documentation looks at the
topic from the PALO user perspective. But the perspective of the
file boot_sectors.txt is the one of an ISO 9660 producer.
So i would like to re-arrange the info.
How about this for the command line part ? Would it be
Hi,
How to recognize a PALO that is newer ?
It should be palo 1.92 or higher.
... PALOHDRVERSION ...
I could update it to 5.
I think it is appropriate.
Readers of libisofs docs and of PALO could make a clear connection.
We shouldn't make xorriso more complicated than necessary.
Yeah.
Hi,
the GPT header CRC of
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
looks ok now for me and for gdisk of oldstable (which formerly
complained about amd64 ISOs). Now it says:
GPT fdisk (gdisk) version 0.8.1
Partition
Hi,
my newest bug about gdisk hating an ISO with GPT and MBR is
not affecting debian-cd. (Further it is not GRUB2 specific.)
I can reproduce the user's symptoms with gdisk 0.8.1 and can work
around them by explicitely disabling multi-session emulation when
producing the ISO. This disabling is
Hi,
Chris Bainbridge:
I still can't create a partition, which was the original aim. Is it
supposed to work?
I succeeded with gdisk on my oldstable test machine (help texts and
clueless actions of mine not shown):
--
$ dd
Hi,
the trusty-desktop-amd64+mac.iso which boots on that machine
bears one single El Torito boot image, an isohybrid MBR, and
partition offset 16. Just like Debian i386 ISOs.
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of
Hi,
these programs are usable on
all architectures even if the bootloader isn't available,
Be aware that neither old isohybrid.pl nor new isohybrid.c are
independent of the SYSLINUX version.
I can forward this warning by H. Peter Anvin (hpa), the author
of ISOLINUX, from personal experience a
Hi,
i am watching this bug as upstream developer of xorriso,
which packs up Debian ISOs under control of debian-cd.
So i can mainly comment about early boot stages and mounting
of ISO 9660, not much about Debian installer issues which
arise after or before these steps.
From your initial report
Hi,
There are descriptions in the web for boot media which
contain multiple ISOs.
Yes, but these tools, in theory, won't work perfect with Debian Installer
till #724931 and #759744 are fixed.
Lack of loop mounting is quite some handicap.
Repartition free space to store extra ISO
Hi,
i noticed that the former URL of cdrkit is now squatted
by some (nearly) german language site.
http://www.cdrkit.org
Google does not find any new home of cdrkit upstream.
Is there a place known to which a wiki could point with
a link resp. where a source oriented distro can get its
Hi,
Aurelien Jarno wrote:
Beside that the
default options of genisoimage should be used, there is no need to
specify any strange HFS option like on powerpc
If no option -hfs is needed, then xorriso should be suitable.
The ISO image should be generated with the --chrp-boot argument.
That
Hi,
I've also just added ppc64el to the daily and weekly build config -
let's see how well it works!
If xorriso shall be used, then it must be
-chrp-boot-part
instead of
-chrp-boot
(On the other hand one may omit -cache-inodes, which has no effect.)
Have a nice day :)
Thomas
--
To
Hi,
Steve McIntyre wrote:
I've also just added ppc64el to the daily and weekly build config -
let's see how well it works!
Aurelien Jarno wrote:
It seems the daily build has worked correctly.
If you mean
Hi,
if [ -f CD$N/ppc/bootinfo.txt ] ; then
add_mkisofs_opt $CDDIR/../$N.mkisofs_opts -chrp-boot-part
fi
I've switched to that and added a hard dependency on xorriso too.
Well, let's see how much havock this creates.
I was prepared to give some more reasoning after having read
my
Hi,
the ISO
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/ppc64el/iso-cd/debian-testing-ppc64el-netinst.iso
of 2014-10-04 10:17 (CEST) still has no CHRP partition table
and was not produced with -as mkisofs option -chrp-boot-part.
It contains the data file /ppc/bootinfo.txt
Hi,
debian-testing-ppc64el-netinst.iso of 2014-10-04 18:41 CEST
is equipped with CHRP pseudo-MBR.
Everything should be ok now ... theoretically.
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi,
Aurelien Jarno:
I have just done an install using this image and everything went smoothly.
Was booting done from a CD drive ?
If so, what happens if the ISO is presented on USB stick
or hard disk ?
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to
Hi,
Philip Hands wrote:
https://wiki.debian.org/DebianInstaller/Preseed/EditIso
The paragraph Create new image describes the production
of an El Torito bootable image for BIOS. I.e. no isohybrid for
USB stick on BIOS and no UEFI.
Further, Debian's cdrecord-wodim is fewly suitable for DVD
Hi,
i wrote:
https://wiki.debian.org/DebianInstaller/Modify/CD
[...] Create new image is outdated in the same way.
Lars-Daniel Weber wrote:
I'm using this one:
[...]
-isohybrid-mbr /usr/lib/syslinux/isohdpfx.bin \
[...]
-eltorito-boot isolinux/isolinux.bin \
[...]
So this is for
Hi,
If I specify -c isolinux/boot.cat too, that fixes
it.
That's surprising. Can you surely switch forth and back
between mounatble and unmountable by this option ?
Option -c just gives the El Torito catalog a file name.
The catalog file is not involved in booting from
USB-stick or in the
Hi,
-isohybrid-mbr null.mbr \
-e boot/grub/efi.img -no-emul-boot -isohybrid-gpt-basdat \
This may look valid, but gdisk and other code I've used don't cope
well with the PMBR being broken.
But that's not the fault of the NUL-bytes in null.mbr.
The isohybbrid --gpt layout does not
Hi,
i understand that debian-cd mailing list is in charge
for discussion of amd64 mini.iso and its generating software:
http://anonscm.debian.org/cgit/d-i/debian-installer.git/tree/build/config/x86.cfg
Hi,
Steve McIntyre wrote:
partition 2 seems broken and I can't mount it.
If I specify -c isolinux/boot.cat too, that fixes it.
Is there any new insight in this mystery ?
If it is reproducible, then my understanding of partitions
is in deep trouble. I'd need to investigate and compare an
ISO
Hi,
Summary:
There are two EFI System Partitions in mini.iso.
The one for booting from USB stick or qemu -hdb is indeed empty.
One could try whether it helps to copy the files from the FAT
image /boot/grub/efi.img in the ISO to MBR partition 2:
- Put mini.iso onto a USB stick /dev/sdb or other
1 - 100 of 337 matches
Mail list logo
