James Carlson <[email protected]> writes: >> I did not find info about where to find any configuration files for >> pkg. > > There aren't any. Should there be?
I'm not telling pkg where to connect to on the command line. Yet it knows. Its getting information somewhere... in some sense that is a configuration. I expected it to be from a file. Apparently that is not the case. Yet it aquires certain information somehow. I guess I'm asksing how to control that. [...] >> How would I tell pkg how to find that and install it. >> `pkg search -r lynx' doesn't find it. > > I think "lynx" integrated as of build 106, which means that it's not > yet on the stable branch. You can pick it up by moving to the "dev" > branch -- by making your authority be this: > > http://pkg.opensolaris.org/dev/ [...] OK, thanks. So will that be integrated into my `image' or will I need to upgrade everything to dev for a new `image'? As you can see, I'm a bit confused by this `image' terminology. `man pkg' is very difficult to read (for me) I admit to having an unusually thick skull and often find things more difficult than others do, but looking up `image-update' in pkg man page. I see `image-update [-fnvq]' And a pretty straight forware description of what it does. So far... good. But then the explanation of -fnvq is somewhere else ... not even clear if it still applies to image-update. In fact I never really did find what each of them meant... finally just guessed that -v was verbose and ran `pkg image-update -v'. So I could watch the action. It installed one pkg (aspell) and told me it was creating a new BE I now have several on the grub menu when I boot, but looking in /boot/grub I don't find anything that resembles what I see at boot time. I guess this is another case of there being no configuration. So If I wanted to remove some of those BE... how would I do that? Just by the `e' edit key at boot time? _______________________________________________ opensolaris-discuss mailing list [email protected]
