Your message dated Sun, 08 Nov 2009 15:33:16 +
with message-id
and subject line Bug#498143: fixed in cdrom-detect 1.32
has caused the Debian Bug report #498143,
regarding Please detect non-ISO block devices masquerading as Debian CDs
to be marked as done.
This means that you claim that the
Frans Pop wrote:
> So I've dropped the documentation patch and committed the others, with a
> few cosmetic changes.
Thank-you.
> Hmmm. If that is really the only use case then maybe that should just be
> documented in the changelog and in comments in appropriate places.
Okay, I'll expand the
tags 498143 pending
thanks
On Tuesday 25 August 2009, Chris Lamb wrote:
> To frame my thoughts here, this is to support d-i when invoked from
> Debian Live USB sticks - as Debian Live knows the target media when
> building the USB image, "try-usb=true" is appended to all generated
> "usb with d-i"
Processing commands for cont...@bugs.debian.org:
> tags 498143 pending
Bug #498143 [cdrom-detect] Please detect non-ISO block devices masquerading as
Debian CDs
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
Frans Pop wrote:
> It would be much nicer if we could somehow display a dialog offering the
> alternative is mounting a CD fails.
To frame my thoughts here, this is to support d-i when invoked from Debian
Live USB sticks - as Debian Live knows the target media when building the
USB image, "try-us
On Thursday 20 August 2009, Frans Pop wrote:
> How are users supposed to know about this option?
>
> I don't know how often this trick is needed, but I doubt users who need
> it will be able to find it. It would be much nicer if we could somehow
> display a dialog offering the alternative is mounti
On Wednesday 19 August 2009, Chris Lamb wrote:
> Updated patch series attached. The previous one did not apply anymore.
I have one fairly big reservation against this patch:
> +Template: cdrom-detect/try-usb
> +Type: boolean
> +Description: for internal use only
> + Preseed this to true to try to
Chris Lamb wrote:
> Attached.
Updated patch series attached. The previous one did not apply anymore.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
From 30c6a69043f56f1616068e9910adbba819a18fb9 Mon Sep 17 00:00:00 2001
From: Chris Lamb
Date: F
Chris Lamb wrote:
> Anyway, if there is no objection to the approach I'll prepare a patch
> and post it back here.
Attached.
- apt-setup is lacking a versioned dependency on cdrom-detect >= 1.32,
but I can't see a way of doing that.
- Templates say stuff like "looking from CD-ROM", "loadin
Chris Lamb wrote:
> However, on [Debian Live] USB/HDD images, cdrom-detect naturally fails
> to locate the partition on which the d-i components reside, as it is
> neither an ISO9660 image nor contained on a block device returned by
> `list-devices cd` or `list-devices maybe-usb-floppy`.
Okay, wh
On Wed, Sep 10, 2008 at 12:49:21PM +0100, Chris Lamb wrote:
> Jérémy Bobbio wrote:
> > How far has this been tested?
>
> I've tested it locally with removal USB keys, both in Qemu and on real
> machines.
Testing if usual CD installations still work is essential before getting
such patch applied a
Jérémy Bobbio wrote:
> How far has this been tested?
I've tested it locally with removal USB keys, both in Qemu and on real
machines.
> Among other questions, how good is this interacting with support for CD
> sets?
I have not tested on a real machine with real CD media yet. Did you have any
pa
On Sun, Sep 07, 2008 at 03:31:13PM +0100, Chris Lamb wrote:
> The attached patch rectifies this by additionally detecting vfat and ext disk
> partitions masquerading as Debian CDs. We only concern ourselves with these
> filesystem types as well as restricting the search to partition
partitions masquerading as Debian CDs. We only concern ourselves with these
filesystem types as well as restricting the search to partitions as live-
helper will only generate images with these combinations.
Regards,
--
Chris Lamb, UK [EMAIL PROTECTED
On Sat, Mar 22, 2003 at 01:56:50PM -0800, Blars Blarson wrote:
> Could it be special-cased for skipping large all-zero blocks at the start
> of files and then check the second 1k block? (Or only use larger blocks
> when these occur)
Something like that, yes... The easiest way I can imagine is to m
In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
>On Fri, Mar 21, 2003 at 07:19:04PM -0700, Chris Tillman wrote:
>jigdo-file first creates a checksum of the first 1k of all files it wants
>to find, then moves a 1k-sized "window" over the image, comparing the image
>checksum of that window
On Fri, Mar 21, 2003 at 07:19:04PM -0700, Chris Tillman wrote:
> Another idea, would be to special case the jigdo code to check the file
> size first, and do something special if it's 1474560 or 2941920 bytes, or
> the other standard floppy sizes.
Well, there's no "something special" that can be d
On Fri, Mar 21, 2003 at 11:09:44AM +0100, Richard Atterer wrote:
> On Thu, Mar 20, 2003 at 08:51:20PM -0700, Chris Tillman wrote:
> > Those seem to be the rescue.bin files. I wouldn't be surprised if the 0's
> > are associated with the boot block, since they are bootable floppies.
>
> Yes, and I w
On Fri, 21 Mar 2003, Richard Atterer wrote:
> On Thu, Mar 20, 2003 at 08:51:20PM -0700, Chris Tillman wrote:
> > Those seem to be the rescue.bin files. I wouldn't be surprised if the 0's
> > are associated with the boot block, since they are bootable floppies.
>
> Yes, and I wouldn't be surprised
On Fri, 21 Mar 2003, Richard Atterer wrote:
> On Fri, Mar 21, 2003 at 11:37:22AM +0800, [EMAIL PROTECTED] wrote:
> > A problem with workarounds is that they lack convenience, and people will
> > forget. May I suggest a bug report against mke2fs and mkfs.minux?.
> > Probably people will still forge
On Thu, Mar 20, 2003 at 08:51:20PM -0700, Chris Tillman wrote:
> Those seem to be the rescue.bin files. I wouldn't be surprised if the 0's
> are associated with the boot block, since they are bootable floppies.
Yes, and I wouldn't be surprised at all if everything continued to work
fine after you
On Fri, Mar 21, 2003 at 11:37:22AM +0800, [EMAIL PROTECTED] wrote:
> A problem with workarounds is that they lack convenience, and people will
> forget. May I suggest a bug report against mke2fs and mkfs.minux?.
> Probably people will still forget (unless it's default behaviour), but
> the docs mig
On Fri, Mar 21, 2003 at 02:31:37AM +0100, Richard Atterer wrote:
> Hello,
>
> many of the floppy images on the FTP server currently start with 1k or more
> of zero bytes. This is bad for jigdo. Would it be possible to write a
> couple of random bytes somewhere in the first 1k of each image?
>
>
On Fri, 21 Mar 2003, Richard Atterer wrote:
> Hello,
>
> many of the floppy images on the FTP server currently start with 1k or more
> of zero bytes. This is bad for jigdo. Would it be possible to write a
> couple of random bytes somewhere in the first 1k of each image?
>
> "Random" can be any
Hello,
many of the floppy images on the FTP server currently start with 1k or more
of zero bytes. This is bad for jigdo. Would it be possible to write a
couple of random bytes somewhere in the first 1k of each image?
"Random" can be anything which makes the images differ from each other in
the
"Holp, John Mr." <[EMAIL PROTECTED]> writes:
> I received the 3 CDs for "official" Debian 2.2.17 last Friday 5
> January 2001. For the past day or two I have been trying to install Debian
> but am not able to effect the installation.
>
> I get all the way through to where I would li
Josip Rodin <[EMAIL PROTECTED]> writes:
> On Mon, Sep 11, 2000 at 04:21:50AM -0400, Adam Di Carlo wrote:
> > > > Do you have the nls_? module in question it is trying to load?
> > >
> > > No. That would be one quite awkwardly named module, too. :)
> >
> > I meant, where you replace '?' with the
On Mon, Sep 11, 2000 at 04:21:50AM -0400, Adam Di Carlo wrote:
> > > Do you have the nls_? module in question it is trying to load?
> >
> > No. That would be one quite awkwardly named module, too. :)
>
> I meant, where you replace '?' with the rest of the module name.
> Are you saying it literal
Josip Rodin <[EMAIL PROTECTED]> writes:
> > Do you have the nls_? module in question it is trying to load?
>
> No. That would be one quite awkwardly named module, too. :)
I meant, where you replace '?' with the rest of the module name.
Are you saying it literally is trying to load 'nls_?' ?
-
On Sat, Sep 02, 2000 at 02:32:49PM -0400, Adam Di Carlo wrote:
> > As the subject says. This happened to me while upgrading slink->potato, on a
> > machine with slink (hmm, perhaps it's potato, this happened even after the
> > upgrade) versions of mount and modutils, and kernel 2.2.16. This is the
Josip Rodin <[EMAIL PROTECTED]> writes:
> As the subject says. This happened to me while upgrading slink->potato, on a
> machine with slink (hmm, perhaps it's potato, this happened even after the
> upgrade) versions of mount and modutils, and kernel 2.2.16. This is the
> fstab entry for the CD:
>
Hi people,
As the subject says. This happened to me while upgrading slink->potato, on a
machine with slink (hmm, perhaps it's potato, this happened even after the
upgrade) versions of mount and modutils, and kernel 2.2.16. This is the
fstab entry for the CD:
/dev/hdd/cdrom iso96
32 matches
Mail list logo
