YakShaving: Shawn Ferry's Weblog
v. intr. [MIT AI Lab, after 2000: orig. probably from a Ren & Stimpy episode.] Any seemingly pointless activity which is actually necessary to solve a problem which solves a problem which, several levels of recursion later, solves the real problem you're working on.
Archives
« November 2007 »
SunMonTueWedThuFriSat
    
2
3
4
6
7
8
9
10
11
13
14
15
17
18
19
20
22
23
24
25
28
29
30
 
       
Today

 Subscribe

Search

Links
 

Today's Page Hits: 389

Locations of visitors to this page
« Previous day (Oct 31, 2007) | Main | Next day (Nov 1, 2007) »
20071101 Thursday November 01, 2007
Indiana IPS (Image Packaging System)

Boldly forward with minimal reading of the docs.


I can't obviously find where I would be downloading additional packages from. I feel like I am running in circles. It would seem that nearly the first thing I should be able to find would be download the rest from HERE. The single CD installer rocks, but we are up to 1 DVD for the normal full install.

I want the Firefox default home to prominently show me:
"Now that you have completed the Slim install get the rest of the packages. Use pkg list/status/something someargs"



The Preview includes the Image Packaging System. With IPS, you can select versioned builds of components to manage or create your own custom OpenSolaris distribution.


IPS packages that are not included in the Slim Install installation image, such as developer tools, can be downloaded after the installation. This prototype uses new IPS commands to access packages from the network repositories. Both IPS packages and SVR4 packages are supported.


The OpenSolaris Project: Image Packaging System project page contains man pages for the new IPS commands and a link to the IPS download site.



OK, pkg(5) has some indications of a repository (or authority) pkg://opensolaris.org. No examples, is pkg://opensolaris.org actually a valid and running authority? OK http://opensolaris.org/os/project/pkg/documents/ says pkg.opensolaris.org. Looking at the list of available packages I now see that they are basically ALL installed. (maybe pkg(5) should reference pkg.opensolaris.org)


I can also see that when I pkg uninstall SUNWbind and pkg install SUNWbind the counters on the site increment. When I drop ni0 the install fails and with it enabled and snoop running there is http traffic downloading the package. Clearly I am hitting the remote authority. Somewhere I think I should be able to see what the default authority is or where to find it (without digging in /var/pkg and guessing that cfg_cache should be the source, or looking at snoop to see where my traffic is going)


pkg install/uninstall is fast and also easy (somewhat dependent on network bandwidth I would guess). It wouldn't suffer from the some sort of optional feedback that work is progressing.


Errors from pkg are quite ugly and straight out of python.

At this point I call the install a success simple, easy, fast. The post install experience is still missing something. The packages that are not included on the live CD, how did they get installed on my instance when I had no net during the install.




So we are down to
  1. Is pkg.opensolaris.org the only authority?
  2. are all the packages that are available installed by default?
  3. If pkgadd can't add packages (or is this a bug) how do I add standard SYSV packages now


In the end this was fun and interesting, I have a much better understanding of where we are going but it doesn't look like Indiana is going to be my everyday system for a while yet,

Nov 01 2007, 02:00:27 PM EST Permalink Comments [1]

OpenSolaris/Indiana first thoughts

(See Update 1 for how to get functional networking in Indiana under Parallels)

As ThinGuy just mentioned on twitter, no registration or login to download the image. Woot!

I am running the installer iso on top of Parallels on Mac OS X 10.5 (leopard)


On the down side:



So now as long as I can get a network interface working one way or another I am set. Fingers crossed. I have already nuked my other local install so I had space to play. I would rather not have to recover it.

Update 1:

Networking: It helps if you remember to install the Parallels provided network interface driver.

See the comment about so few steps I must be forgetting something (like installing the driver)

Parallels: Installing the Beta got rid of some VM related network error messages and appears to have fixed shared networking (my default for my simple test instance).

I guess I could have provided a link: http://opensolaris.org/os/project/indiana/resources/getit/

Issues with the base slim install No /usr/ccs/bin/make (or any make as far as I can tell in the default install). To install the required driver the following manual steps are required.


Appendix C: is way out of date although it would have reminded me to install the network driver.




Nov 01 2007, 09:21:01 AM EST Permalink

Blog Information Profile for YakShaving