<div dir="ltr"><br><br><div class="gmail_quote">On Sat, Oct 11, 2008 at 9:38 AM, Karl Kleinpaste <span dir="ltr"><<a href="mailto:karl@kleinpaste.org" target="_blank">karl@kleinpaste.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>"Greg Hellings" <<a href="mailto:greg.hellings@gmail.com" target="_blank">greg.hellings@gmail.com</a>> writes:<br>
</div><div>> My guess is that the update to -0.98 came with the image-upgrade that I ran<br>
> from the command-line<br>
<br>
</div>If you mean the directions for immediate update specified here...<br>
<a href="http://www.opensolaris.org/os/project/indiana/resources/rn3/#Update_Inst" target="_blank">http://www.opensolaris.org/os/project/indiana/resources/rn3/#Update_Inst</a><br>
...I did that as directed when I first booted, which is why I knew there<br>
was a problem with /etc/nsswitch.conf.</blockquote><div><br>Ah, I see - that's not at all the steps I followed. I found documentation exceedingly difficult to locate. The steps I followed were:<br>make entries in /etc/hosts for <a href="http://www.opensolaris.org" target="_blank">www.opensolaris.org</a> and <a href="http://pkg.opensolaris.org" target="_blank">pkg.opensolaris.org</a><br>
# pkg refresh --full<br># pkg image-update -v (died with error telling me to update SUNWipkg)<br># (issue the command here that the previous command asked for)<br># pkg image-update -v<br># reboot<br><br>It's possible that image-update is similar to dist-upgrade with Debian based systems... but I'm not certain.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div><br>
> or from syncing against the repository.<br>
<br>
</div>Is there some sense of "syncing" other than "start package manager and<br>
wait for it to display available packages"? (That's a serious question.)</blockquote><div><br>The gui Package Manager was broken upon initial install, so the command pkg refresh --full from the command line did what I was looking for. However, since you updated the system with the commands from the above URL, clicking the "Refresh" button will probably do the trick. But if I'm actually running some sort of beta 2008.11 version or whatever, then you might not have the same packages as me, without doing the image-update step.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
You seem to have a very different view of what was installed than I do,<br>
yet all I did was install the 2008.05 ISO, do the initial update per<br>
above, and go looking for needed stuff in the package manager. I cannot<br>
begin to understand why you have additional support that seems to be<br>
missing for me.</blockquote><div><br>I might be in beta for the next upcoming release? I'm not entirely certain. When I ran the image-update, it updated about 512 of the 527 packages, or something to that effect, I know that it was very nearly all of them.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div><br>
> I'm not completely certain - when you look in Package Manager, you can<br>
</div>> see a list of files that come with a package. ... So my only guess is<br>
<div>> that either the information in Package Manager is wrong, or some<br>
> hidden dependency pulled it in.<br>
<br>
</div>If the package manager is failing to properly identify files used in a<br>
package, then the authors of that package manager should give up and go<br>
home.<br>
<br>
Of course, as I mess around with this a bit more, I've just been pointed<br>
to pkgchk, whose man page provides the example "pkgchk -l -p /usr/bin/ls",<br>
for which it should "display package installation information"...and yet<br>
which produces empty output. So maybe they should go home after all.</blockquote><div><br>Ditto on that opinion and on getting null output from pkgchk. However, I have gotten somewhere with the pkg search xrender.pc command. It appears that xorg-headers is not the requisite package after all. I suppose installing xorg-headers must have pulled in xwinc, which is listed as the package owning xrender.pc. I'm not having any luck copying out of the VM with openSolaris in it, but pkg search is listing SUNWxwinc-0.5.11-0.98 as the owner of xrender.pc.<br>
<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
If I can't get any farther than this pretty soon, I'll just give up on<br>
Solaris as yet another lost cause. I get tired of pushing on really<br>
fundamental, basic, "just get the system going, ok?" kinds of questions<br>
that can't be answered.</blockquote><div><br></div></div>For an operating system supposedly in its 11th version and sporting approximately a 20-year history, openSolaris is pathetically impractical, incapable and extremely frustrating. To be flawed to the point of being unable to update itself and unable to access DNS on default install point to major issues with the entire system. I wouldn't blame you at all for taking your ball and going home at this point. OpenSolaris also seems to bear almost no resemblance to the commercial Solaris 10 that we're using at school/work. If I were Sun, I'd either get on the task of greatly improving openSolaris or stop calling it by the same name as its flagship operating system. I would certainly never move to commercial Solaris if I thought openSolaris represented the nature of the commercial product.<br>
<br>--Greg<br></div>