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,
Fabian Greffrath wrote:
> Where is 1.4.0-1?
There was a 1.4.0-1.1 on mentors. When i added myself to
Uploaders, i moved on to 1.4.0-2. Same for libisofs and
libisoburn.
Most probably i will have to make libburn-1.4.0-3 to repair
an upstream regression that prevents building on Debian
GNU/kFr
Hi,
Bjørn Mork wrote:
> On a default Debian system you need to be a member of
> the "floppy" group.
Ferenc Wagner wrote:
> What about recommending /dev/disk/by-id/usb-X instead?
I understand that the instructions about creating a Debian installation
medium shall be usable on as many systems as
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 poten
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,
i managed to work around the problem - at least on my system.
There are at least two oddities involved
- If the kernel events happen, then always on open().
But it is quite unpredictable whether they happen at all.
xorriso and program "eject" have a higher probability to trigger
kernel
Hi,
Ben Hutchings:
> I imagine that libburn's commands to the drive cause it to signal a
> status change to the kernel driver, which passes that on to udev.
That's obviously what happens.
udev then loses patience with the drive that is kept internally busy
by a pending SCSI command from libburn,
Hi,
me:
> > What is the recommended way for a library resp. a console program
> > to tell udev, that a CD drive and the media will undergo arbitrary
> > changes and should not be accessed during that time ?
Ben Hutchings:
> There isn't one.
Isn't this a kind of shortcomming ?
I remember that E
Hi,
i am upstream developer of libburn and CD/DVD/BD burn program xorriso.
It seems urgent that i coordinate the activities of libburn with the
activities of udev.
What is the recommended way for a library resp. a console program
to tell udev, that a CD drive and the media will undergo arbitrary
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 X
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 b
Hi,
i am the author of cdrskin and not subscribed here.
Please Cc me.
Michelle Konzack wrote:
> All they are SCSI and not a singel one is working with wodim.
Hm. What are the symptoms ?
William Pitcock wrote:
> > Or look into libburn + cdrskin, which should "just work"
Michelle Konzack wrote:
12 matches
Mail list logo
