From owner-freebsd-questions@FreeBSD.ORG Sat Jan 9 14:04:21 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CDA2106566C for ; Sat, 9 Jan 2010 14:04:21 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id CAE238FC15 for ; Sat, 9 Jan 2010 14:04:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o09E4Int065759; Sun, 10 Jan 2010 01:04:19 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 10 Jan 2010 01:04:18 +1100 (EST) From: Ian Smith To: Knight Tiger In-Reply-To: <20100109074733.9E5EA106574A@hub.freebsd.org> Message-ID: <20100110000633.G8593@sola.nimnet.asn.au> References: <20100109074733.9E5EA106574A@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-questions@freebsd.org Subject: Re: ISO image size -regarding X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jan 2010 14:04:21 -0000 In freebsd-questions Digest, Vol 292, Issue 14, Message: 12 On Fri, 8 Jan 2010 16:41:24 -0800 Knight Tiger wrote: > Hi, > > I am trying to create a custom ISO image of FreeBSD 6.4. The only > difference between the release ISO and this custom image is a modified > driver (amdsmb.ko). I did not create the new driver. I believe it was > backported from a later release. > > I understand that this is not a backport of the driver but a hack but > the ISO size surprises me. > > The steps I had followed (listed below) resulted in an ISO image of > around 1 GB while the original ISO image is around 600 MB. The new > image work boots fine but I am not sure why it is huge > > Steps: > > // mount the release ISO > # mdconfig -a -t vnode -f 6.4-RELEASE-i386-disc1.iso -u 0 > # mount_cd9660 /dev/acd0 /mnt > > # pwd > /usr/home/scott > > # mkdir custom > # cd custom > > // copy iso files to custom > # rsync -a /mnt . Hi Scott, nearly all in /rescue are hardlinks to one big executable, and there are also hardlinks in /bin and /sbin, hence your size difference. rsync(1): Note that -a does not preserve hardlinks, because finding multi- ply-linked files is expensive. You must separately specify -H. Note also that for compatibility, -a currently does not include --flags (see there) to include preserving change file flags (if supported by the OS). > # scp scott@remote:/boot/kernel/amdsmb.ko boot/kernel/. > > // wrap up in a ISO > # cd .. > #mkisofs -R -b boot/cdboot -no-emul-boot -o custom.iso custom > > The ISO file is created successfully but is huge. I mounted it in > VirtualBox and boots just fine. I was able to install the OS (although > I have not checked the functionality of amdsmb changes yet) > > I looked up information on creating custom ISO images but they had all > involved rebuilding the kernel while I am not sure if I need to do the > same Any leads is appreciated. Yes, running make release might be just a tad over the top for this :) cheers, Ian