svn commit: r253513 - head/release

[Teske, Devin]

On Jul 21, 2013, at 9:55 AM, Hiroki Sato wrote:

> "Teske, Devin" <Devin.Teske at fisglobal.com> wrote
>  in <13CA24D6AB415D428143D44749F57D7201FD2BF2 at ltcfiswmsgmb21>:
> 
> De>
> De> On Jul 21, 2013, at 6:39 AM, Alexey Dokuchaev wrote:
> De>
> De> > On Sun, Jul 21, 2013 at 05:23:34AM +0000, Glen Barber wrote:
> De> >> New Revision: 253513
> De> >> URL: https://urldefense.proofpoint.com/v1/url?u=http://svnweb.freebsd.org/changeset/base/253513&k=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=Mrjs6vR4%2Faj2Ns9%2FssHJjg%3D%3D%0A&m=ICzrrPRprsUfeSXmW22PbvhR4zFtb5xxNHgyzQmaW38%3D%0A&s=ab088fdca0bfa1bc85c9bae0aaa04a30f6c37b8815a87d255b1e026794ecbccf
> De> >>
> De> >> Log:
> De> >>  Create memstick images with the '.img' filename extension.
> De> >>
> De> >>  Requested by:	many
> De> >>  [...]
> De> >
> De> > Is there any work being done to merge the .iso and .img into single,
> De> > hybrid bootable image (c.g. Haiku)?  I've asked this question before,
> De> > but I cannot recall now what was the outcome if it...
> De> >
> De>
> De> I have been doing this for years @ $work with sysinstall. Since the
> De> death of sysinstall, I've been working on the replacement. However,
> De> you can download Hybrid ISO/IMG images here:
> 
> It is possible to create a hybrid image of ISO9660 and USB memory
> image because ISO images for sparc64 have a similar structure and we
> can reuse the build procedure.  I have a patch to create such images,
> but there is a concern that recent memory images become >700MB.  Is
> it still useful?
> 

Yes. Because we can burn them to DVD for read-only optical and we can use 2GB, 4GB, or greater-sized USB Thumbs.

@ $work we've been able to keep the size of the ISOs down by using sysinstall from an mfsroot.

===

ASIDE: I recently analyzed what we would need to put bsdinstall+bsdconfig into an mfsroot to do similar things as sysinstall...

(sorted alphabetically)
/bin/sh /usr/sbin/pkg_add* awk bsdlabel** cat cdcontrol chmod chown cksum cmp cp 
date df dhclient dialog dumpfs ee fdisk fetch find ftp grep host hostname id 
ifconfig kill ldconfig ln ls md5 mkdir mktemp mount mount_cd9660 mount_msdosfs 
mount_nfs moused mv nc pkg_delete* pw rm route rtsol sed sleep sort stat stty 
sysctl tail tr umount uname vidcontrol

(optional functionality requirements; not required in mfsroot)
Xdialog logger su sudo touch xauth xterm

* bsdconfig(8) yet to be updated for pkg (for configPackages)
** bsdconfig(8) yet to be updated to use gpart to probe for disks (for mediaSet*)

===

Despite the fact that what we've only published builds under 600MB, in-house @ $work, I've made so-called "super discs" that contain multiple arches + multiple releases. For example, I once made a multi-GB DVD that contained 4.11, 8.1-32, 8.1-64, 8.3-32, 8.3-64, 9.0-32, and 9.0-64 (plus several utilities like memtest86, memtest86+, memtest86+SMP, windiag, Derik's Boot-And-Nuke, TuffTest Pro, SpinRite, WD Velociraptor FW updates, Seagate SeaTools (both GUI and Txt version), and yet even more. I think the resulting ISO was about 2.7GB. It fit nicely on a 3GB thumb-drive I had and it burned well to DVD. It was very nice being able to walk around with one disc or one thumb drive and be prepared for anything/everything.

(I carry one one me at all times in my coat pocket ^_^)

So yeah... >700MB shouldn't be a problem.
-- 
Devin

_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.