NetBSD Problem Report #44265

From www@NetBSD.org  Wed Dec 22 23:56:21 2010
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id EEB1E63BB73
	for <gnats-bugs@gnats.NetBSD.org>; Wed, 22 Dec 2010 23:56:20 +0000 (UTC)
Message-Id: <20101222235620.D1E5563BAC9@www.NetBSD.org>
Date: Wed, 22 Dec 2010 23:56:20 +0000 (UTC)
From: darrenandrewgould@gmail.com
Reply-To: darrenandrewgould@gmail.com
To: gnats-bugs@NetBSD.org
Subject: Creation of boot image for i386
X-Send-Pr-Version: www-1.0

>Number:         44265
>Category:       misc
>Synopsis:       Creation of boot image for i386
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    www
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Thu Dec 23 00:00:00 +0000 2010
>Closed-Date:    
>Last-Modified:  Mon Apr 30 22:21:57 +0000 2012
>Originator:     Darren Gould
>Release:        NetBSD 5.1
>Organization:
none
>Environment:
Non-applicable, applies to documentation.
>Description:
Hi, 

I'm one of those users that like to build my own iso rather than use the pre-built one offered. In doing so, I realized that the "-no-emul-boot" is needed to create the bootable image.  Otherwise, the mkisofs will render a: "Size of boot image is 7200 sectors --> Error - boot image is not the an allowable size" error.

The current documentation at:
http://netbsd.org/docs/bootcd.html#i386image
does not reflect that requirement, so I thought I'd throw you a "heads-up" to let you know.

Regards,

D. Gould
>How-To-Repeat:
N/A
>Fix:
N/A

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->feedback
State-Changed-By: riz@NetBSD.org
State-Changed-When: Fri, 24 Dec 2010 01:29:44 +0000
State-Changed-Why:
Requested feedback from submitter.


From: Jeff Rizzo <riz@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-i386/44265: Creation of boot image for i386
Date: Thu, 23 Dec 2010 17:26:57 -0800

 On 12/22/10 4:00 PM, darrenandrewgould@gmail.com wrote:
 > Hi,
 >
 > I'm one of those users that like to build my own iso rather than use the pre-built one offered. In doing so, I realized that the "-no-emul-boot" is needed to create the bootable image.  Otherwise, the mkisofs will render a: "Size of boot image is 7200 sectors -->  Error - boot image is not the an allowable size" error.
 >
 > The current documentation at:
 > http://netbsd.org/docs/bootcd.html#i386image
 > does not reflect that requirement, so I thought I'd throw you a "heads-up" to let you know.

 I assume the instructions as posted merely create a boot image that does 
 not have installation sets, and so you install via the network?

 I wonder if these instructions should be supplanted with information 
 about the fact that bootable .iso images are created by default in a 
 release build these days, and are by default put in 
 i386/installation/cdrom .  For example, from the latest autobuilds:

 http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201012230600Z/i386/installation/cdrom/boot.iso

 ... these images are actually build with makefs, which is part of NetBSD 
 these days.

 Thanks for the report - can you check if these images work for you and 
 do what you want?

 +j

From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
To: riz@netbsd.org
Cc: gnats-bugs@netbsd.org, tsutsui@ceres.dti.ne.jp
Subject: Re: port-i386/44265: Creation of boot image for i386
Date: Fri, 24 Dec 2010 19:33:48 +0900

 >  I assume the instructions as posted merely create a boot image that does 
 >  not have installation sets, and so you install via the network?
  :
 >  ... these images are actually build with makefs, which is part of NetBSD 
 >  these days.

 I guess certain users want to know how to create bootable CD
 and it isn't relevant to installation.

 We also have to clarify the definition of "bootable"
 (make BIOS/firmware load a binary, load a kernel from CD, or
  get single user prompt with working file system?),
 but probably it's enough to mention the following command
 that uses the ElTorito specification without old floppy emulation:

 % makefs -t cd9660 -o rockridge,bootimage=i386\;/PATH/TO/bootxx_cd9660,no-emul-boot,allow-mutidot output.iso /PATH/TO/cdsoureces_dir

 It might be worth to mention the following topics:
 - how to fetch sources and build tools to get makefs(8)
   (mention guide pages?)
 - how to prepare root file system
   (extract base/etc/kern sets, or
    put miniroot.kmod with "load" command in boot.cfg(5)?)
 - how to set permissions properly in output iso (by makefs(8) -F spec)
 but I'm not sure if it's in the scope of the document.

 ---
 Izumi Tsutsui

From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: port-i386-maintainer@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org, darrenandrewgould@gmail.com
Subject: Re: port-i386/44265: Creation of boot image for i386
Date: Fri, 24 Dec 2010 12:21:08 +0100

 On Fri, Dec 24, 2010 at 10:35:02AM +0000, Izumi Tsutsui wrote:
 >  - how to set permissions properly in output iso (by makefs(8) -F spec)
 >  but I'm not sure if it's in the scope of the document.

 It's all fine to document "somewhere" (bootable-iso.8 or something or
 some special file under src/doc/ paralell to "building"),
 but let's please remove all of it from the guide and just point to
 "build.sh iso-image".

 Martin

From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
To: martin@duskware.de
Cc: gnats-bugs@NetBSD.org, tsutsui@ceres.dti.ne.jp
Subject: Re: port-i386/44265: Creation of boot image for i386
Date: Fri, 24 Dec 2010 20:29:36 +0900

 > but let's please remove all of it from the guide and just point to
 > "build.sh iso-image".

 The page mentioned in this PR is not the guide but
 "Creating a bootable NetBSD CD-ROM"
 http://www.NetBSD.org/docs/bootcd.html

 I have no idea if we have such technical info on www.
 ---
 Izumi Tsutsui

From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: port-i386-maintainer@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org, darrenandrewgould@gmail.com
Subject: Re: port-i386/44265: Creation of boot image for i386
Date: Fri, 24 Dec 2010 12:34:55 +0100

 On Fri, Dec 24, 2010 at 11:30:05AM +0000, Izumi Tsutsui wrote:
 >  The page mentioned in this PR is not the guide but
 >  "Creating a bootable NetBSD CD-ROM"
 >  http://www.NetBSD.org/docs/bootcd.html

 Yeah, sorry for confusion.

 >  I have no idea if we have such technical info on www.

 Legacy from days when creating a bootfloppy was a hard and manual step.

 Martin

From: Darren Gould <darrenandrewgould@gmail.com>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-i386/44265: Creation of boot image for i386
Date: Fri, 24 Dec 2010 10:02:24 -0500

 Hello again,

 I guess my earlier report has proven premature.  I was not aware until
 after my filing that NetBSD 5.x uses its own native tools to create
 the boot image.  So, even though "-no-emul-boot" will get one through
 the iso creation, it will not boot into installation.

 Sorry for the oversight.  A side note about the change in 5.x would
 have been a better suggestion.  But, I just checked the Problem
 Report, and it looks like you guys really dove into it!

 Many Thanks,

 Darren A. Gould


 On 12/22/10, gnats-admin@netbsd.org <gnats-admin@netbsd.org> wrote:
 > Thank you very much for your problem report.
 > It has the internal identification `port-i386/44265'.
 > The individual assigned to look at your
 > report is: port-i386-maintainer.
 >
 >>Category:       port-i386
 >>Responsible:    port-i386-maintainer
 >>Synopsis:       Creation of boot image for i386
 >>Arrival-Date:   Thu Dec 23 00:00:00 +0000 2010
 >
 >

From: Alan Barrett <apb@cequrux.com>
To: Darren Gould <darrenandrewgould@gmail.com>
Cc: gnats-bugs@NetBSD.org
Subject: Re: port-i386/44265: Creation of boot image for i386
Date: Mon, 27 Dec 2010 07:59:35 +0200

 On Sun, 26 Dec 2010, Darren Gould wrote:
 > I thought I'd follow with an update.  Being that 'makefs' is a tool
 > native to NetBSD, and I didn't have NetBSD installed, sort of thrust
 > me in a Catch-22.

 NetBSD is intended to be cross-buildable on almost any unix-like
 platform.  You'll need the source tree, of course, but then the
 "build.sh" script should be able to build everything, and "build.sh
 tools" will build just the tools.

 --apb (Alan Barrett)

Responsible-Changed-From-To: port-i386-maintainer->www
Responsible-Changed-By: dholland@NetBSD.org
Responsible-Changed-When: Mon, 30 Apr 2012 22:21:57 +0000
Responsible-Changed-Why:
The problem here is that the docs on the web site are outdated.


State-Changed-From-To: feedback->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 30 Apr 2012 22:21:57 +0000
State-Changed-Why:
Submitter wrote back in 2010; I must have missed it at the
time.


>Unformatted:

Home	PR Database Search