Your message dated Sun, 30 Jan 2011 16:10:40 -0400
with message-id <20110130201040.gc20...@gnu.kitenet.net>
and subject line Re: Bug#590568: hd-media boot.img.gz's installer cannot find 
squeeze RC2 iso file
has caused the Debian Bug report #590568,
regarding debian-installer: hd-media boot.img.gz's installer cannot find 
mini.iso
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
590568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Severity: normal

Hi.

I've tried to follow instructions in 
http://www.debian.org/releases/testing/i386/ch04s03.html.en to create a 
bootable USB disk.

What I've done is reuse the files from : 
http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/current/images/hd-media/boot.img.gz
 and just use a basic syslinux config :
  default linux
  append initrd=initrd.gz
to get a bootable USB disk of maximum size that indeed will boot an installer.

However, whenever inside the installer, the netinst .iso file cannot be found 
when it searches the disks to find an installable iso image.

The iso is named mini.iso (just as downloaded from 
http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/current/images/netboot/)
 and sits inside the USB key's first (and only) VFAT partition (which mounts 
fine from /dev/sdb1 to /hd-media from a shell started inside the installer).

Is there a requirement on a special name for iso image files ?

Thanks in advance


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
anataka wrote:
> Then upon further inspection, I found out I've been using the wrong 
> boot.img.gz
> all along, I only thought I had the one linked above but in fact I was using
> the i386 one. I had several web pages open and click one thinking i was in
> another.
> 
> I started over and it worked.
> 
> I fixed my own stupidity but still automated scan is nice but imho it could be
> useful to offer an option to manually enter the path to the iso.

I don't think that further complicating the installer with prompts for
paths that most users will not find it easy to manually figure out is
the right approach.

iso-scan already does a 2-pass scan, so unless the user has hidden away the
iso very deep on the disk, they can avoid having it recursively scan
deeply through all their drives.

Anyway, all this is deprecated by hybrid isos that can be written
directly to USB disks to make a bootable image, avoiding every single
pain point that users have encountered with the piggyback iso and
iso-scan. So I expect that iso-scan will soon only be used by users in
highly unusual situations (either users who need to boot the installer
from an existing partition with no removable media at all, or users who
cannot afford a dedicated cheap USB stick).

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to