Re: [Pkgutil-users] Using pkgutil in JumpStart finish file
Status: Beta
Brought to you by:
bonivart
|
From: Don J. <pkg...@cl...> - 2009-04-19 20:54:22
|
I have gotten pkgutil to work OK in a jumpstart finish script.
There are two tricks:
1) Run every command via "chroot /a"
2) At this point in the boot/installation process, there is no file /a/
mnttab, which causes pkgutil to die, so:
cp /etc/mnttab /a/etc/mnttab
Before you start issuing pkgutil commands.
So, my finish script does a pkgadd of pkgutil from a mounted disk,
then uses pkgutil to fetch the Blastwave catalog, and the packages I
would like to have installed on my new machine.
A couple of enhancement requests for pkgutil:
a) support a command line option that overides the pkgutiil.conf
standard location. When you want to do something different
temporarily, it is a pain to
go change the master file, do what you want, then restore the master
file. It would be far easier to just point that instance of pkgutil
at the config file I want for that invocation.
b) A command line option to eliminate/minimize file transfer status.
In a text log file, these dynamic progress indications take up a lot
of text (see below).
Thanks to Peter and Dennis for their responses!
Don
Example output showing profuse textual output of download status:
Fetching CSWreadline-5.2,REV=2009.01.23...
--13:00:02-- http://blastwave.network.com/csw/unstable/i386/5.10/readline-5.2,REV=2009.01.23-SunOS5.8-i386-CSW.pkg.gz
=> `/var/opt/csw/pkgutil/packages/
readline-5.2,REV=2009.01.23-SunOS5.8-i386-CSW.pkg.gz'
Resolving blastwave.network.com... done.
Connecting to blastwave.network.com[64.79.150.209]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 868,485 [application/x-gzip]
0K .......... .......... .......... .......... .......... 5%
228.31 KB/s
50K .......... .......... .......... .......... .......... 11%
331.13 KB/s
100K .......... .......... .......... .......... .......... 17%
301.20 KB/s
150K .......... .......... .......... .......... .......... 23%
324.68 KB/s
200K .......... .......... .......... .......... .......... 29%
326.80 KB/s
250K .......... .......... .......... .......... .......... 35%
301.20 KB/s
300K .......... .......... .......... .......... .......... 41%
326.80 KB/s
350K .......... .......... .......... .......... .......... 47%
324.68 KB/s
400K .......... .......... .......... .......... .......... 53%
303.03 KB/s
450K .......... .......... .......... .......... .......... 58%
326.80 KB/s
500K .......... .......... .......... .......... .......... 64%
303.03 KB/s
550K .......... .......... .......... .......... .......... 70%
324.68 KB/s
600K .......... .......... .......... .......... .......... 76%
331.13 KB/s
650K .......... .......... .......... .......... .......... 82%
301.20 KB/s
700K .......... .......... .......... .......... .......... 88%
328.95 KB/s
750K .......... .......... .......... .......... .......... 94%
73.42 KB/s
800K .......... .......... .......... .......... ........ 100%
245.56 KB/s
|