Prev: convert CPU load to CPU utilization in %
Next: SunRay with different displays
From: John D Groenveld on 22 Dec 2009 09:28
In article <92c8691f-8442-4fe0-a172-1cb6d2e7389f(a)u7g2000yqm.googlegroups.com>,
ChrisS <chris.scarff(a)gmail.com> wrote:
>not) all upgraded just fine. We primarily use SAMP stuff (minus the
>MySQL), but it's nice to have those little tools at the ready if
>needed.

Have you played with Sun's webstack for Solaris 10?
<URL:http://www.sun.com/software/webstack/>

John
groenveld(a)acm.org
From: phil.googlenews on 23 Dec 2009 13:02
On Dec 21, 11:09 pm, ChrisS <chris.sca...(a)gmail.com> wrote:
>
> As a sidebar (but my objective here) I was wondering when Apache2 will
> be upgraded on OpenCSW.  I see the "Jones" have already update
> theirs.  {:-)  And I'm not mixing the two!  I picked my poison.

:-)

We're working on it!
We first wanted to get an updated, shared libapr out., to build it on
top of.
That particular package is being worked on as we speak. candidate
build had a minor bug in it, so was tossed back to the maintainer to
fix before release.



From: phil.googlenews on 23 Dec 2009 13:07
On Dec 21, 11:09 pm, ChrisS <chris.sca...(a)gmail.com> wrote:

> Well, though Phill is "plugging" his own site here, he is correct in
> one thing; I've used the upgrade option earlier in the year when we
> had to make the decision of who to go with, Blastwave or OpenCSW.  We
> (I), chose to move our platforms to OpenCSW and the upgrade worked
> perfect.  All the old Blastwave software we had installed (too much or
> not) all upgraded just fine.  We primarily use SAMP stuff (minus the
> MySQL), but it's nice to have those little tools at the ready if
> needed.

PS: a little tip, if someone's upgrade gets a little complicated....
or you just want to "clean things up" first:
(or you want to cleanly copy a set of CSW packages from one machine to
another...)

pkg-get -l
will give you a list of your installed packages based on the "software
name".

eg:

$ pkg-get -l
amavisd_new
ap2_modfastcgi
ap2_prefork
ap2_worker
....


You can save that to a file. then loop through pkgrm'ing all CSW
files.
Once the machine is "clean", adjust your pkg-get.conf to use the
appropriate url, and then do

pkg-get -i `cat outputfile`


and it will walk through adding the software, "fresh".

The nice thing about this is that it gives you a chance to review and
edit the outputfile, before adding all the junk back in.

From: ChrisS on 23 Dec 2009 15:29
On Dec 23, 1:07 pm, "phil.googlen...(a)bolthole.com"
<phil.googlen...(a)bolthole.com> wrote:
> On Dec 21, 11:09 pm, ChrisS <chris.sca...(a)gmail.com> wrote:
>
> > Well, though Phill is "plugging" his own site here, he is correct in
> > one thing; I've used the upgrade option earlier in the year when we
> > had to make the decision of who to go with, Blastwave orOpenCSW.  We
> > (I), chose to move our platforms toOpenCSWand the upgrade worked
> > perfect.  All the old Blastwave software we had installed (too much or
> > not) all upgraded just fine.  We primarily use SAMP stuff (minus the
> > MySQL), but it's nice to have those little tools at the ready if
> > needed.
>
> PS: a little tip, if someone's upgrade gets a little complicated....
> or you just want to "clean things up" first:
> (or you want to cleanly copy a set of CSW packages from one machine to
> another...)
>
> pkg-get -l
> will give you a list of your installed packages based on the "software
> name".
>
> eg:
>
> $ pkg-get -l
> amavisd_new
> ap2_modfastcgi
> ap2_prefork
> ap2_worker
>   ....
>
> You can save that to a file. then loop through pkgrm'ing all CSW
> files.
> Once the machine is "clean", adjust your pkg-get.conf to use the
> appropriate url, and then do
>
> pkg-get -i `cat outputfile`
>
> and it will walk through adding the software, "fresh".
>
> The nice thing about this is that it gives you a chance to review and
> edit the outputfile, before adding all the junk back in.

Great tip Phill, thanks! And thanks for the update on the upcoming
apache2 release via OpenCSW.

Chris
From: David Combs on 30 Dec 2009 23:47
In article <hghs9j$7gr$3(a)reader1.panix.com>,
David Combs <dkcombs(a)panix.com> wrote:
>In article <29fc6a86-d97a-4269-ba2e-b233d3d598f0(a)r24g2000prf.googlegroups.com>,
>phil.googlenews(a)bolthole.com <phil.googlenews(a)bolthole.com> wrote:
>>BTW, let's get some attributions and ownerships correct:
>>
>>On Dec 14, 11:18�am, dkco...(a)panix.com (David Combs) wrote:
>>> ....
>>> Note: opencsw uses pkgget (same, different from what blastwave used
>>> *before* the messy "divorce" at Blastwave between Dennis Clarke and
>>> Phillip Brown (went and started opencsw.org),
>>
>>That paragraph has a very misleading implication.
>>
>>Better and more appropriately written as
>>"Philip Brown (started CSW packaging, wrote pkg-get, moved both to
>>opencsw.org)"
>>
>>and...
>>
>>
>>> whereas Clarke-and-team created "pkgutil" (pkg-util?).
>>
>>no, "Clarke-and-team" did NOT create pkgutil. Just like he did not
>>create CSW packaging. I did. he merely hosted it.
>>
>>"Clarke" does not own pkgutil, nor did he have much to do with the
>>creation of it.
>>It was primarily created by (and is still owned and maintained by)
>>Peter Bonivart.
>>Who has contributed effort to both blastwave, and opencsw.org.
>>For those who care, pkgutil works on both repositories, as does pkg-
>>get.
>>
>>
>>
>
>Well, thanks for that last, that each of them work the
>same on each site.
>
>
>David
>
>

Phil -- could you be a bit more specific about the precise changes
one has to make to the current blastwave pkgutil to access opencsw
stuff?

Another question: by playing with a symlink, defining it one
way when wanting to deal with blastwave, and a second way
when dealing with opencsw -- any way something like that
could enable a system to have both available.

I suppose when you wanted to USE a package, or a set of packages,
you would have to use packages from only one or the other --
else internal refs would be to the wrong place?


I really resist the idea that a user must 100% toss one of the
two sites as a source of pre-built software.

I know you two guys are angry at each other, but what you've
done by choosing the csw directory-name seems makes me think
of a High Noon type duel, where one participant never wanted
to be out there in this only-one-will-walk-away-alive situation.

I look at the opencsw site, and am impressed with all that
you have done there, coming out with a rather nice product.

But perhaps you're taking your how-to-succeed-in-business
method from, say, Microsoft (or maybe IBM (of old) or Intel --
heck, for those of a certain age, AT&T!, "you want to
use our system -- you cannot hook any other manufacturer's
equipment than ours -- and if you don't like it, tough!).

(parens wrong, sentence structure too -- but you get the
gist of my point.)


We are all -- at least us users -- better off were, say,
Ford and GM, etc, to make their cars such that a piece
of equipment from one would work on the other.

Disk being cheap enough, maybe two versions, csw and, well,
opencsw.

Or even some kind of a perl or sed filter we can run a
opencsw package through and change every csw to opencsw?

Surely there's SOME way we can take advantage of both efforts!


Hey -- thanks for reading this thing!


David




First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: convert CPU load to CPU utilization in %
Next: SunRay with different displays