Date: Tue, 12 Jan 2010 11:56:38 -0800 From: Knight Tiger <caugar@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: ISO image size -regarding Message-ID: <69fec4521001121156m2f85f06eqc530547cbb6b3479@mail.gmail.com> In-Reply-To: <20100110000633.G8593@sola.nimnet.asn.au> References: <20100109074733.9E5EA106574A@hub.freebsd.org> <20100110000633.G8593@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, To update all, I followed Roland's suggestion and installed isomaster and just opened the iso file (1GB) and saved it again and it 'magically' shrank to 570 MB. The new ISO was burned and tested on a physical machine and it works fine. Thanks Roland ! I tried Ian's suggestion and copied from the ISO file and can confirm that his recommended changes did the trick and the ripped files only measure 570 MB making it easier to use mkisofs . Thanks Ian ! Cheers Scott On Sat, Jan 9, 2010 at 6:04 AM, Ian Smith <smithi@nimnet.asn.au> wrote: > In freebsd-questions Digest, Vol 292, Issue 14, Message: 12 > On Fri, 8 Jan 2010 16:41:24 -0800 Knight Tiger <caugar@gmail.com> wrote: > =A0> Hi, > =A0> > =A0> I am trying to create a custom ISO image of FreeBSD 6.4. The only > =A0> difference between the release ISO and this custom image is a modifi= ed > =A0> driver (amdsmb.ko). I did not create the new driver. I believe it wa= s > =A0> backported from a later release. > =A0> > =A0> I understand that this is not a backport of the driver =A0but a hack= but > =A0> the ISO size surprises me. > =A0> > =A0> The steps I had followed (listed below) resulted in an ISO image of > =A0> around 1 GB while the original ISO image is around 600 MB. The new > =A0> image work boots fine but I am not sure why it is huge > =A0> > =A0> Steps: > =A0> > =A0> // mount the release ISO > =A0> # mdconfig -a -t vnode -f 6.4-RELEASE-i386-disc1.iso -u 0 > =A0> # mount_cd9660 /dev/acd0 /mnt > =A0> > =A0> # pwd > =A0> /usr/home/scott > =A0> > =A0> # mkdir custom > =A0> # cd custom > =A0> > =A0> // copy iso files to custom > =A0> # rsync =A0-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. =A0rsync(1)= : > > =A0 =A0 =A0 =A0 =A0 =A0 =A0Note that -a does not preserve hardlinks, beca= use finding multi- > =A0 =A0 =A0 =A0 =A0 =A0 =A0ply-linked =A0files is expensive. =A0You must = separately specify -H. > =A0 =A0 =A0 =A0 =A0 =A0 =A0Note also that for compatibility, -a currently= does not =A0include > =A0 =A0 =A0 =A0 =A0 =A0 =A0--flags =A0(see there) to include preserving c= hange file flags (if > =A0 =A0 =A0 =A0 =A0 =A0 =A0supported by the OS). > > =A0> # scp scott@remote:/boot/kernel/amdsmb.ko boot/kernel/. > =A0> > =A0> // wrap up in a ISO > =A0> # cd .. > =A0> #mkisofs -R -b boot/cdboot -no-emul-boot -o custom.iso custom > =A0> > =A0> The ISO file is created successfully but is huge. I mounted it in > =A0> VirtualBox and boots just fine. I was able to install the OS (althou= gh > =A0> I have not checked the functionality of amdsmb changes yet) > =A0> > =A0> I looked up information on creating custom ISO images but they had a= ll > =A0> involved rebuilding the kernel while I am not sure if I need to do t= he > =A0> same Any leads is appreciated. > > Yes, running make release might be just a tad over the top for this :) > > cheers, Ian >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?69fec4521001121156m2f85f06eqc530547cbb6b3479>