Hi,
i wrote back in february:
> > I am still hunting a bug in the pending changeset to enable
> > production of a UEFI compliant protective MBR plus GPT
> > layout with -append_partition.
> > [...]
> > This proposal will look like
> > xorriso-1.3.9 -as mkisofs \
> > -V 'Debian jessie-DI-b2 ar
Hi,
> OK, I've just built and done a very quick test with an arm64 netinst
> build.
Does it boot ?
Are the partitions mountable ?
>3 313344 313343 0 bytes 0700 Gap1
This looks strange.
What do you get from
xorriso-1.3.9 -indev tmp.iso -report_system_area plain
Hi,
the third, zero sized partition "Gap1" gets indeed
produced by libisofs. xorriso command -report_system_area
does not show it, though.
I am investigating. You may assume that this partition
will not be produced in future xorriso versions.
If the "Gap1" partition entry is suspected to disturb
Hi,
i wrote:
> > The name "Gap1" seems to stem from libisofs.
The cause was found and a fix is being tested meanwhile.
Steve McIntyre wrote:
> The Gap1 partition doesn't seem to cause any problems on the one
> device I've got handy for testing, anyway.
In any case it looks clueless.
(The stupid
Hi,
> Our algorithm is
> failing to discover if this iso[1] is bootable.
I am curious to learn about the expectations of that algorithm.
The ISO looks like being bootable via CHRP.
>From my cheatsheet
http://bazaar.launchpad.net/~libburnia-team/libisofs/scdbackup/view/head:/doc/boot_sectors.t
Hi,
> > debian-8.1.0-ppc64el-CD-1.iso
> debian-7.8.0-powerpc-CD-1.iso
So your algorithm is missing the Apple Partition Map and possibly
the HFS to which it points.
The bootability of debian-8.1.0-ppc64el-CD-1.iso is indicated by
fulfilling the CHRP demands:
- value 0x96 at byte offset 450 (MBR
Hi,
inspection of the ISOs is not needed any more, since we now know
that your algorithm expects "powerpc" bootable ISOs, not those
for "ppc64el".
Nevertheless, as we are at it:
> Here is the output of xorriso:
> ...
> System area summary: MBR CHRP cyl-align-off
> ISO image size/512 : 9162480
> .
Hi,
"myboyfri...@mail.ru" wrote:
> >So maybe type that inf about iso - for stop misunderstanding humanoids?
Steve McIntyre wrote:
> I've just added some text for this, which will appear on the website
> shortly. Thanks for the report!
The Unix-centric part of https://www.debian.org/CD/faq/#write
Hi,
has it been noticed that jigdo-dlbd has exceeded the
size of a single medium ?
http://cdimage.debian.org/debian-cd/8.1.0/amd64/jigdo-dlbd/
http://cdimage.debian.org/debian-cd/8.1.0/i386/jigdo-dlbd/
I dimly remember that it was supposed to also serve as
all-in-one ISO for large USB sticks
Hi,
is it known that these two images do not boot on qemu
of Jessie ?
http://ftp.debian.org/debian/dists/unstable/main/installer-amd64/current/images/netboot/mini.iso
http://ftp.debian.org/debian/dists/unstable/main/installer-i386/current/images/netboot/mini.iso
The BIOS obviously finds iso
Hi,
Ian Campbell wrote:
> I've not heard of it but please check the
> buglist first (reportbug will prompt you do to so anyway).
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796470
I checked
https://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=debian-boot%40lists.debian.org
No "mini.iso"
Hi,
i wrote:
> http://ftp.debian.org/debian/dists/unstable/main/installer-amd64/current/images/netboot/mini.iso
Cyril Brulebois wrote:
> https://lists.debian.org/debian-boot/2015/08/msg00286.html
I am daily looking for a new amd64 mini.iso to show up,
in order to close the bug as soon as it boots
Hi,
Cyril Brulebois wrote:
> Dailies are pushed here:
> http://d-i.debian.org/daily-images/amd64/daily/
I can confirm that
http://d-i.debian.org/daily-images/amd64/daily/netboot/mini.iso
boots in qemu to the graphical screen.
> You'll need a new debian-installer upload to unstable to get an
Hi,
> > > You'll need a new debian-installer upload to unstable
> > Who can make it happen ?
> Usually me. But we don't normally do that outside releases. If you don't
> trust stuff on d-i.d.o (which is entirely reasonable), rebuilding the
> debian-installer source package locally is easy enough
Hi,
Aurelien Jarno wrote:
> I have no idea if they support booting over a
> CD-ROM or USB image. Does someone known if we can do so on a Loongson 3
> or Octeon machine?
Maybe one should ask grub-de...@gnu.org mailing list or
Vladimir Serbinenko directly.
-
Hi,
Steve McIntyre wrote:
> I'm open to making more different-sized image types so long as they
> make sense - ask!
I think an all-in-one ISO image for large USB sticks or
old hard disks in old or new USB boxes is of interest.
Let the target devices grow with Debian's total size. :))
Users of s
Hi,
trying to get in contact with Steve McIntyre about
Debian bug #800130, libjte1:
A few weeks ago i made packages of xorriso-1.4.0 et.al.
which are now in Debian testing, thanks to Dominique
Dumont.
QA complains about libisofs6 having Priority "optional" but
depending on libjte1 with Priority
Hi,
Steve McIntyre wrote:
> Apologies for not responding earlier - swamped with other stuff
I hope i showed the appropriate patience, given the low urgency
of the problem.
> ACK. I'll sort out a dependency change for libjte* shortly. It may
> take a few days to happen, as the priorities of pack
Hi,
> That depends, I guess - what are people going to be building with
> libisofs-dev?
Known to me are two GUI applications:
https://tracker.debian.org/media/packages/x/xfburn/control-0.5.4-1
https://tracker.debian.org/media/packages/b/brasero/control-3.12.1-1
and libisoburn, which also pro
Hi,
Steve McIntyre wrote:
> I'm told
> that Grub can do all the needed stuff to boot CDs as well, so I'm
> curious to test it.
Debian kfreebsd mini.iso already uses GRUB2 for BIOS.
amd64 and i386 have about the same equipment:
Volume id: 'ISOIMAGE'
El Torito catalog : 55 1
El Torito
Hi,
Try asking at mailing list
debian-user-fre...@lists.debian.org
See
https://lists.debian.org/debian-user-french/
Ask for help with
https://www.debian.org/CD/jigdo-cd/#how
As for sarge-amd64-1.jigdo ... was there Jigdo in Debian 3 ten
years ago ?
> la derniere distribution debian po
Hi,
i can only test on Debian GNU/Linux, not on MS-Windows.
I ran
$ jigdo-lite
and was asked for the URL
To start a new download, enter URL of .jigdo file.
...
jigdo:
I gave the one of CD 1 to keep the test small:
http://cdimage.debian.org/debian-cd/8.3.0/amd64/jigdo-cd/debian-8.3.
Hi,
i asked Florent Larose to move the thread over to
debian-u...@lists.debian.org
for now.
Have a nice day :)
Thomas
Hi,
Wouter Verhelst wrote:
> This image however does not support booting on a UEFI-only system.
It does support EFI booting from CDROM. At least with qemu and OVMF
as EFI firmware.
> Is there anyone with the required knowledge who would be willing to
> look into fixing that?
I downloaded
ht
Hi,
Wouter Verhelst wrote:
> http://anonscm.debian.org/cgit/d-i/debian-installer.git/tree/build/util/geniso_hybrid_plus_firmware_partition
> I add a line isohybrid -u "$iso"
This last isohybrid run replaces the partition which was crafted
by the fdisk run.
This is also the reason why fdisk does
Hi,
how much is debian-cd concerned/interested that CDs written by write type
TAO stay readable for e.g. blkid ?
I ask because Archlinux ISOs already do not boot properly from such CDs
as they rely on /dev/disk/by-label/ links to mount the ISO.
https://bugs.archlinux.org/task/48234
The current
Hi,
Steve McIntyre wrote:
> Oh, ugh. :-(
The problem may well be a year old. First report is about Archlinux 2015.04.
> Have you mentioned this on the linux kernel list?
Not yet. I am still looking for allies or even better a mentor.
(Will work for guidance.)
Funny thing is that in october i b
Hi,
Joerg Jaspert wrote:
> > > As of now, InRelease/Release files, Packages and Sources no longer
> > > provide MD5Sum and SHA1sums, only SHA256.
Steve McIntyre wrote:
> > We can't fix this easily in a short
> > timescale - current released jigdo clients (both in Debian and
> > externally) use md
Hi,
> However, it's possible to allow the latter running isohybrid --partok
> iso-name.iso (according to isohybrid's man page), and I have done so, and it
> works.
Interesting result.
How did you make the MBR of the overall device which then hops onto
the code at the start of the partition ?
>
Hi,
Renato Bispo wrote:
> -> I partitioned my USB stick using gparted, setting the boot flag on the
> partition I wanted to put the image.
Now i wonder whether the stick already contained MBR code which
would jump on the marked partition or whether gparted installed such
x86 machine code.
See
Hi,
i wrote
> > dd if=/dev/sdX bs=512 count=1 | od od -t x1
Renato Bispo wrote:
> the command you sent didn't work:
A copy+paste error indeed. A single "od" would have been right.
> 000 b8fa 1000 d08e 00bc b8b0 d88e c08e
A bit pattern widely known to the web.
http://superuser.co
Hi,
i made a mistake, of course. This time when copying the ISO:
Wrong: dd if="$image_path" of="$dev" bs=1M
Right: dd if="$image_path" of="$dev"1 bs=1M
If you perform the wrong command, then the parted MBR gets overwritten
by the isohybrid MBR of the Debian ISO.
Have a nice day :)
Thomas
Hi,
> Does the method described in the manual (copying to /dev/sdX) work under
> UEFI? Or it's basically the same thing as copying to a partition?
The main difference is that copying to /dev/sdX overwrites the MBR and
the partition tables, while copying to /dev/sdXn keeps the partitioning
(and th
Hi,
Renato Bispo wrote:
> * Under BIOS at least
More we cannot expect from this setup.
The next experiment would be to create a new partition of type 0xef
(1MiB, with no filesystem on it, should be ok) and to copy the file
/boot/grub/efi.img, which is actually a FAT filesystem image.
Then one wo
Hi,
Weber wrote:
> I cannot verify the /dev/sr2
> after i tried this there appears a new cdrom /dev/sr3
Looks like the device was abandoned and newly acquired by the
operating system.
Do you see error messages in the system log after this happened ?
Have a nice day :)
Thomas
Hi,
Weber wrote:
> > $ dd if=/dev/cdrom | \
> > head -c `stat --format=%s debian-testing-i386-netinst.iso` | \
> > md5sum
>
> its not working on wheezy.
What are the exact failure symptoms ?
> md5sum with Brasero seems to have an bug(?):
> the "ok" messsage comes up without any testing.
At wha
Hi,
Alexey Eromenko wrote:
> implantisomd5 [...]
> Basically it implants the MD5sum into a secret portion of ISO 9660
> filesystem
Not so secret. At least if it stems from
https://github.com/rhinstaller/isomd5sum/blob/master/libimplantisomd5.c
The MD5 gets written into a field of the ISO 9660
Hi,
do the file timestamps matter in ISOs of debian-cd, debian-live,
or in other Debian ISOs ?
I ask this because xorriso-1.4.6 will obey environment variable
SOURCE_DATE_EPOCH
of reproducible-builds. I then plan to propose to debian ISO producers to
use xorriso-1.4.6 with new original ISOs and
Hi,
i wrote:
> > new program option: --set_all_file_dates [...]
Chris Lamb wrote:
> I believe this option is entirely unnecessary. No need to
> complicate things.
It is architecturally needed, because if SOURCE_DATE_EPOCH sets the
default, there must be some option to set non-default values, es
Hi,
Chris Lamb wrote:
> I just don't see this usecase of being "partly" reproducible being remotely
> useful to anyone, ever. I'm probably misunderstanding something, however.
All three possible behaviors lead to reproducibility if the input trees
of the ISO production runs are sufficiently simil
Hi,
i wrote:
> > All three possible behaviors lead to reproducibility if the
> > input trees of the ISO production runs are sufficiently
> > similar.
Sam Hartman wrote:
> So, are you using a definition of reproducible different than the
> resulting iso will have the same SHA-1 hash?
I mean ident
Hi,
by the narrow margin of one vote, the proposal "set_to_mtime" wins.
Committed as http://libburnia-project.org/changeset/5757
man 1 xorrisofs of the next release will state:
SOURCE_DATE_EPOCH belongs to the specs of reproducible-builds.org. It
is supposed to be either undefined or to co
Hi,
Alexey Eromenko wrote:
> 1. Hybridize ISO images
The amd64 and i386 ISOs are equipped with isohybrid functionality.
In which ISOs are you missing this feature ?
> 2. Please "implantisomd5"
I assume this will meet the same obstacles as the wish for isohybrid
a few years ago: Changing the IS
Hi,
Anders Thulin wrote:
> Looking at debian-8.6.0-arm64-netinst.iso using ISOBuster.
> In the Primary Volume Descriptor file hierarchy, there's a file
> /FIRMWARE/FIRMWARE.DEB;1 (size 0).
That's a symbolic link.
firmware-linux-free_3.3_all.deb ->
../pool/main/f/firmware-free/firmware-linux-fr
Hi,
schatzclan wrote:
> unexpectedly larger
> actual file size (642M) vs reported size (613M) for the “i386 8.x.0 LXDE
> CD#1” iso.
This is explainable from the difference of programmer's MiB and IEC's MB:
642.0 / 1024 / 1024 * 1000 * 1000 = 612.2589111328125
> The “i386 8.5.0 XFCE CD#1” ISO
Hi,
i made a copy + paste error with the repacking command.
Option -apm-block-size lacks its parameter "2048".
Correct would be:
mount debian-8.6.0-i386-DVD-1.iso /mnt/iso
xorriso -as mkisofs \
-o test.iso \
-V 'Debian 8.6.0 i386 1' \
--modification-date='2016091713290100' \
Hi,
(This is about the aspect Mac mountability, not about the aspect of
suitable performance during or after installation..)
Shirish Agarwal wrote:
> Would it be possible to upload the image to someplace where the OP
> could download and use it and see if that works for him.
It is nearly 4 GB o
Hi,
Sam Hartman wrote:
> Why do we care if it mounts on a third mac?
I care in my role as upstream of xorriso.
As for debian-cd, any oddity of installation ISOs should be inspected
and judged whether it demands action.
I see i forgot to Cc: the bug reporter.
Hi ! There are replies to see at:
Hi,
Sam Hartman wrote:
> I'd ask that when interacting with end users, you be more clear about
> what you're trying to do.
I am trying to answer this question from the bug report:
> > Could it be that the hybrid CD/USB iso is causing problems?
The answer is for now:
It might be a problem with M
Hi,
Wolfgang Schindler wrote:
> sorry, mein Englisch ist nicht so gut.
Google translation delivers a quite understandable translation of your
text to english language.
(= Der Google Uebersetzer bringt es einigermassen verstaendlich nach
Englisch.)
There is a german language debian-user mailin
Hi,
> How do I talk to the syslinux developers?
Subscribe on
http://www.zytor.com/mailman/listinfo/syslinux
to
sysli...@zytor.com
and post your report.
Have a nice day :)
Thomas
Hi,
David Christensen wrote:
> http://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-8.7.1-i386-xfce-CD-1.iso
Background info:
This is an isohybrid made by xorriso, equivalent to a run of
isohybrid --uefi
There is a probably useless Apple Partition Map pointing to the UEFI
System Par
Hi,
intermediate report:
We found a bug in isohdpfx.bin which spoils the C/H/S address conversion
for BIOSes which do not support LBA addressing.
http://www.syslinux.org/archives/2017-March/025692.html
It turned out that David Christensen's BIOS does not support INT 13 AH 41
which causes isohd
Hi,
more update for Bug#857597:
Correcting the wrong stack address of sectors/head yielded progress
on David's old BIOS.
The MBR code now correctly addresses and loads the first 4 blocks of
boot image file /isolinux/isolinux.bin .
Nevertheless, the stack interface between MBR and loaded isolinux
Hi,
David Christensen confirmed that above fixed MBR enabled isohybrid
booting on his legacy system.
Time for a summary of findings.
How to reproduce the bug:
Any BIOS which does not announce "Device Access using the packet structure"
Hi,
the following patch has been committed to SYSLINUX to fix the C/H/S
addressing problems in isohybrid MBR and isolinux.bin :
http://git.zytor.com/syslinux/syslinux.git/commit/?id=32c09027423f61c305e2423e52f5f69ecad8e2c0
diff --git a/mbr/isohdpfx.S b/mbr/isohdpfx.S
index 17e1efe..f9e9691 100644
Hi,
Guido Günther wrote:
> > Volume id: Debian stretch-DI-rc2 amd64 1
> > [...]
> > >If the netinst variant would contain netinst or similar
Steve McIntyre wrote:
> I understand, yes. The problem we have is that the volume ID is very
> limited in space available. We've run out... :-/
How about
Hi,
i wrote:
> >> How about replacing the volume number "1" by "n" ?
Guido Günther wrote:
> >That would be great!
Steve McIntyre wrote:
> Date: Thu, 18 May 2017 23:40:40 +0100
> I've just committed code to do that, let's see how it looks on the
> next daily/weekly builds.
Seems not to be in eff
Hi,
Steve McIntyre wrote:
> *Now* fixed... :-)
The latest debian-testing-amd64-netinst.iso has indeed:
Volume Id: Debian testing amd64 n
...
Creation Time: 2017052004084000
(Now we have to brace for protests from people or software relying on
the volume number 1.)
Have a nice day :
Hi,
if we wait much longer then the machines have died out which need the fix.
How about offering the corrected 432 bytes for download and have
an item in CD FAQ which points to the binary and explains how to
put it onto the first 432 bytes of the USB stick or .iso image ?
Have a nice day :)
T
Hi,
Steve McIntyre wrote:
> Do you have suggested text we can use?
Modulo english language, URL of the binary file, and clarity of mind.
$$...$$ means that properties of the download offer have to be inserted.
The answer is intended to be put after
"How do I write a CD/DVD/BD image to a USB fl
Hi,
Jimmy Johnson wrote:
> Tried both installs and they failed on finding the dvd.
Did your BIOS or EFI not notice the presence of a bootable DVD and
instead just does what is usual when no DVD is inserted at boot time ?
If you do not get boot messages from ISOLINUX or GRUB to finally
get to the
Hi,
Jimmy Johnson wrote:
> the dvd boots and runs live to
> desktop, it's when I click to install and it gets to finding the dvd is when
> it loop unable to find the dvd.
Well, that's one or two DVD finds after the one for which my program
would be responsible.
Have a nice day :)
Thomas
Hi,
while comparing a KALI ISO with debian-9.1.0-amd64-netinst.iso i noticed
that debian-cd uses a development snapshot of GNU xorriso:
Preparer Id : XORRISO-1.4.7 2017.06.29.211523, ...
Not that i would deem it bad in any way, but i wonder why not the
Debian package with xorriso-1.4.6 or the
Hi,
good to know that the SYSLINUX/ISOLINUX packages are maintained again.
Please consider to also adopt bug #857597 from package debian-cd:
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
which is actually an old bug in the ISOLINUX isohybrid MBR.
It hits old BIOS wh
Hi,
Lukas Schwaighofer wrote:
> * added patches from upstream to fix:
> - boot problems for pre-2005 BIOS computers, see #857597 [1]
Applause.
I wonder whether the new binary isohdpfx.bin is byte-identical to the
tested MBR with the fix:
http://www.ludd.ltu.se/~ams/tmp/isohdpfx.bin.170324
Hi,
now that a new set of SYSLINUX packages is announced by
https://lists.debian.org/debian-cd/2017/10/msg00025.html
with changelog entry
* Add patch from upstream to fix boot problem for old BIOS firmware from
around 2005 by correcting the C/H/S order (thanks Thomas Schmitt).
what
Hi,
> thanks for pushing this forward :) .
You wrote my name on its item in the changelog.
And somehow i became the drover of this bug, anyway.
> Well, that bug is only solved once we have CD images that are no longer
> affected by this bug.
Given its usual speed of movement i just wanted to g
Hi,
the weekly testing ISOs for i386 and amd64 are now equipped with the
new MBR:
https://cdimage.debian.org/mirror/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-netinst.iso
https://cdimage.debian.org/mirror/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso
Tester
Hi,
David Christensen wrote:
> This will restore Debian (and
> derivatives) as a viable option for many millions of older computers. :-)
At least they can now have some good final years.
(Let's be nice to the elderly. We will join their ranks soon enough.)
Have a nice day :)
Thomas
Hi,
in
https://www.debian.org/CD/jigdo-cd/
the "How to download an image with jigdo" paragraph sends potential
downloaders to http://atterer.org/jigdo/ which then has a semi-obvious
link to
https://packages.debian.org/search?keywords=jigdo-file
How about giving a tangible example for Debian u
Hi,
on occasion of a discussion at debian-user i tried to reproduce the
jigdo-lite problem reported by Nicholas Geovanis in
https://lists.debian.org/debian-user/2017/12/msg00467.html
My attempt yields better results than for him.
Nevertheless using
http://cdimage.debian.org/cdimage/archive/6
Hi,
Brian Potkin wrote:
> That's the link given by Nicholas Geovanis. It works for me for starting
> downloading. I didn't want this image so stopped it after five minutes.
It works for me except 7 or 2 packages in the end.
> I used http://deb.debian.org/debian and got debian-9.3.0-i386-DVD-1.i
Hi,
Philip Hands wrote:
> Ah, right -- you seem to have discovered some corrupt files on my
> server. Thanks :-)
I had a similar suspicion but failed yet to write a reverse function to
decode the MD5s in the .jigdo file. It's a 6-bit format but not base64.
An encoder is in libjte/jte.c as base64
Hi,
after some pondering:
Can it be that these five packages are damaged too on us.cdimage.debian.org ?
gnome-user-share_2.30.1-1_amd64.deb
ipolish_20100612-1_amd64.deb
myspell-en-gb_3.2.1-2_all.deb
debian-keyring_2010.12.29_all.deb
openoffice.org-l10n-en-gb_3.2.1-11+squeeze8_all.deb
Hi,
not graftable into debian-6.0.7-amd64-DVD-2 :
extremetuxracer-data_0.4-4_all.deb
openclipart-png_0.18+dfsg-10_all.deb
ko.tex-extra-hlfont_0.1.0-1_all.deb
lilypond-doc_2.12.3-7_all.deb
libboost1.42-doc_1.42.0-4_all.deb
I used
http://us.cdimage.debian.org/cdimage/snapshot/Debian/
a
Hi,
Cabal Cabal wrote:
> 23:05:19 (103.64 KB/s) -
> `debian-6.0.5-amd64-DVD-1.iso.tmpdir/us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/g/ghostscript/ghostscript-cups_8.71~dfsg2-9_amd64.deb'
> saved [61234/61234]
> ...
> Aaargh - 1 files could not be downloaded. ...
If this is 23:05:19
Hi,
Philip Hands wrote:
> There are four jigdo files that were also corrupt:
Google finds me candidates at ftp.riken.go.jp
but also the ones at cdimage.debian.org/mirror seem to be good.
What i don't find are the expected MD5s of .jigdo files.
Shouldn't they be in files like
http://cdimage.deb
Hi,
i Cc: debian-cd with this follow-up to bug 884526 in the hope to get
some review for the endeavor to detect damaged downloaded package files
during a run of jigdo-lite.
Some disputable aspects remain (plus a possible bug in current jigdo-lite,
which will vanish by my proposal). I put them beh
Hi,
first a correction of my proposal:
The else-case with
echo "WARNING: File not found after download:" >&2
is not good.
It floods the log if one uses a mirror with few matching files.
Not finding a file after the download is a normal situation.
---
Hi,
I wrote:
> > > > sed -e 's/^[hH][tT][tT][pP]:\/\///' \
> > > >... more -e for https, ftp, and file ...
Philip Hands wrote:
> > > sed -e 's,^\(https\?\|ftp\|file\)://,,i'
> > > ...
> > > "$imageTmp/${url#[[:alpha:]]*://}"
> > Are these widely porta
Hi,
i wrote:
> > us.cdimage.debian.org is a quick one.
Nicholas Geovanis wrote:
> From which location? Germany?
Ja.
How about this final message in case that files are missing and that
mismatching downloads were detected ?
(The mismatches shown are fake and recorded twice to get more than 2.)
Hi,
Lars Henrik Jensen wrote:
> Our customers want to buy computer with preinstalled Linux and I wish to
> know how I can do it right and devilery with a recovery DVD/CD or USB stick
> or a recovery partition on harddrive.
With questions about installation of Debian you are probably better off at
Hi,
Luca wrote:
> Windows host=no jigdo
There is a link to
http://atterer.org/sites/atterer/files/2009-08/jigdo/jigdo-win-0.7.2.zip
on
http://atterer.org/jigdo/
Vague alternative ideas:
- Install a small Debian in a virtual machine on some MS-Windows with
network access and use it to assem
Hi,
Luca Biella wrote:
> I thought Jigdo for windows where obsolete.
I have no experience about how fast bit rot invalidates an MS-Windows
binary. It would be interesting to know whether it still works and
whether it can build the BD sized images.
> I will try the Debian live hint on my home P
Hi,
on occasion of a user question on debian-cd
"Blueray Disk image"
https://lists.debian.org/debian-cd/2018/01/msg00010.html
i exercised the whole procedure of Jigdo download by help of Debian LiveCD:
debian-live-9.3.0-amd64-xfce.iso
It is bumpy. (But at least there is a terminal starter
Hi,
i started a wiki page
"Downloading Debian Jigdo ISOs by a Debian Live system"
https://wiki.debian.org/JigdoOnLive
and filled in my experiences about this task.
Help is needed to put some tangible info or examples into
https://wiki.debian.org/JigdoOnLive#Get_access_to_a_writable_disk_fil
Hi,
while working on my JigdoOnLive wiki page i got pointed by Paul Wise
to the fact that the "https:" URLs of cdimage.debian.org files do not
really protect their file content against tampering.
I am quite sure that the .jigdo files get not verified by jigdo-lite
beyond (possibly) the gzip check
Hi,
i looked into jigdo-file about the safety of the final jigdo-lite statement
"OK: Checksums match, image is good!"
The message stems from
src/jigdo-file-cmd.cc
where i read
MD5Sum md; // MD5Sum of image
md.updateFromStream(*image, info->size(), readAmount, *optReporter);
md.finish()
Hi,
Lou Poppler wrote on debian-cd@lists.debian.org:
> I would note that debian-live stable versions are also available via
> bittorrent, which probably has more peers available, and is easier on the
> mirrors.
I myself have no clue of bittorrent. So this part would need an author other
than me.
Hi,
shivgupta wrote:
> > mount: no medium found on /dev/sr0
Steve McIntyre wrote:
> * Did you have a disc in drive sr0?
> * Was it spun up?
The first question was my first thought, too.
But it's not about the drive spinning up, but rather the 10 to 15 seconds
it normally needs to inspect the m
Package: debian-cd
Severity: normal
Tags: upstream
Dear Maintainer,
as described in
https://lists.debian.org/debian-cd/2018/01/msg00019.html
the *.jigdo files are not listed in the checksum files *SUMS.
There is no way provided to check the authenticity of *.jigdo before
downloading by jigdo-li
Hi,
debian-cd muss man auf englisch ansprechen.
Vielleicht kann auch die deutschsprachige Liste
https://lists.debian.org/debian-user-german/
weiterhelfen.
(debian-cd needs to be addressed in english language.
Maybe this german language list can help too:
https://lists.debian.org/debian-user
Hi,
debian-9.3.0-amd64-netinst.iso was made with xorrisofs option -joliet-long,
which enable Joliet names longer than 64 characters.
But production of debian-9.3.0-amd64-DVD-2.iso did not use it.
Whatever setting is finally desirable, it should be the same with all
Debian ISOs which get a Joliet
Hi,
Steve McIntyre wrote:
> Fixing it right now, thanks for the clear report!
I did not want to open a bug without knowing more background.
As you are in fixing mode, could you please look whether
https://bugs.debia
Hi,
Steve McIntyre wrote:
> I think you're the main person who might be using the logs published
> from cdbuilder.
I did not even know that such logs exist.
> https://cdbuilder-logs.debian.org/
Ahum. What's the meaning of the number prefixes of the file names ?
("3sidamd64", "4amd64")
I alway
Hi,
looking at
https://salsa.debian.org/images-team/debian-cd/commit/6112370e0abf29018a5346467aaf27cf7cb8ba91
"Ensure that in all places where we use -J we also use --joliet-long"
i wonder whether it is wise to rely on the undocumented double-dash tolerance
of xorrisofs and genisoimage. Bo
Hi,
Steve McIntyre wrote:
> I've got too used to the relaxed handling in xorriso.
IIRC the tolerance of xorrisofs exists because genisoimage and mkisofs show it.
It's contageous and each adoption possibly widens it.
E.g. i did not check whether genisoimage refuses on some double-dash options
but
Hi,
i wrote:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887830
> > "debian-cd: *.jigdo files should be listed in the *SUMS files"
Steve McIntyre:
> ACK, it's a fairly simple fix to the debian-cd setup. I've pushed the
> changes and if you check today's daily/weekly builds you'll see
Hi,
i wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887831
> "jigdo-file: Jigdo .template file and resulting ISO are only verified
> by MD5"
> [...]
> jigdo-lite could now make automatic use of the *SUMS via the according
> *sum programs.
It comes to me that jigdo-lite would first h
1 - 100 of 355 matches
Mail list logo
