Hi there,
i guess that not only me can see today, that pca is unable to work now.
regards, daniel
--
Best Regards / S Pozdravem
Daniel Pecka
--
SunOS Specialist, IT Administrator
www.techniservit.cz
dpecka wrote:
i guess that not only me can see today, that pca is unable to work now.
Same here. SunSolve is unresponsive, access to e.g.
https://sunsolve.sun.com/pdownload.do?target=patchdiag.xref
via the browser or wget hangs as well ..
Martin.
It is working here ok,
tb
Am 31.05.2010 um 09:20 schrieb Martin Paul:
> dpecka wrote:
>> i guess that not only me can see today, that pca is unable to work now.
>
> Same here. SunSolve is unresponsive, access to e.g.
>
> https://sunsolve.sun.com/pdownload.do?target=patchdiag.xref
>
> via the
2010/5/31 Martin Paul :
> dpecka wrote:
>>
>> i guess that not only me can see today, that pca is unable to work now.
>
> Same here. SunSolve is unresponsive, access to e.g.
>
> https://sunsolve.sun.com/pdownload.do?target=patchdiag.xref
>
> via the browser or wget hangs as well ..
For me, it's w
Alexander Skwar wrote:
2010/5/31 Martin Paul :
dpecka wrote:
i guess that not only me can see today, that pca is unable to work now.
Same here. SunSolve is unresponsive, access to e.g.
https://sunsolve.sun.com/pdownload.do?target=patchdiag.xref
via the browser or wget hangs as well ..
For
On Mon, 2010-05-31 at 09:29 +0200, Martin Paul wrote:
>
> Yes, seems to be OK again.
>
> Martin.
>
not for me, but no worry, i suppose that it will be working soon since i
can't even download patchdiag.xref by hand, so problem is not evidently
in pca.pl itself ..
btw, i investigated a bit beca
dpecka wrote:
btw, i investigated a bit because i have found, that in .xref file is in
position #7 and #8 (indexed from zero) architecture or so ..
at http://sunsolve.sun.com/patchfinder/ you can check and find wanted
patches by using several more filters which pca.pl doesn't know like
above men
On Mon, 2010-05-31 at 10:24 +0200, Martin Paul wrote:
> Keep in mind that pca's main intention is to identify those patches
> which apply to a certain system, not to show patches which match a
> certain criteria in the patchdiag.xref file.
ok, i keep, but honestly, i guess, that the very lot of
dpecka wrote:
pca does not use column #7 to match patches to the installed OS release,
as this information has proven to be unreliable in the past. Some
patches have been described as "Unbundled" although they applied to e.g.
Solaris 10. Therefore, pca uses the information about the included
p
On Mon, 2010-05-31 at 15:39 +0200, Martin Paul wrote:
> Anyway, what kind of queries are you (or is everybody) using patchfinder
> for, that pca doesn't support? Maybe I'm just missing something which is
> extremely useful.
>
> Martin.
>
no, you're not missing something "extremely useful" .. i
dpecka wrote:
On Mon, 2010-05-31 at 15:39 +0200, Martin Paul wrote:
Anyway, what kind of queries are you (or is everybody) using patchfinder
for, that pca doesn't support? Maybe I'm just missing something which is
extremely useful.
no, you're not missing something "extremely useful" .. i only
Hi.
2010/6/1 Martin Paul
> The problem with some fields is that the possible values are of very
> different length. As I want to keep a fixed format (column X always is Y
> chars wide) for easier post-processing, I have to use the maximum width.
> This would make output for the "architecture" co
Alexander Skwar wrote:
With fixed width, post processing isn't easier (but also not harder,
of course *G*). It just LOOKS nicer, but if you're after post processing,
the looks aren't that important, I'd say.
You're right.
Right now the options to control pca's output are not very great, and my
On Tue, 2010-06-01 at 15:22 +0200, Martin Paul wrote:
> Ok, now that's not too complicated. For a start, I've added support for
> a new specifier "%o" for --format to the current development release.
>
> Martin.
>
excellent martin :) .. i'd like to suggest yet another must-to-have
feature ..
On Wed, 2010-06-02 at 11:19 +0200, dpecka wrote:
> the usage could be as follows:
>
> --asort %{key} :ascending sort by key
> --dsort %{key} :descending sort by key
> --esort "{$sort_expression},%{key}" :perl sort() expressions including
> brackets {} and coma separated %{key}
>
> example:
>
>
dpecka wrote:
i think, that for -l|--list operation would be very useful a possibility
of sorting by --format %{keys} ..
Ok, I've put it on the ToDo list. As I just noticed how ugly the code
around --format (and creating the output in general) is, I will probably
do the necessary changes at t
Hi.
2010/6/2 dpecka :
> On Tue, 2010-06-01 at 15:22 +0200, Martin Paul wrote:
>> Ok, now that's not too complicated. For a start, I've added support for
>> a new specifier "%o" for --format to the current development release.
>>
>> Martin.
>>
>
> excellent martin :) .. i'd like to suggest yet anot
On Wed, 2010-06-02 at 12:26 +0200, Martin Paul wrote:
> OTOH this is a good example to explain my reluctancy to add every new
> idea to pca. In the good old tradition of Unix, there are small
> utilities which usually do one thing, but that very good. All these are
> supposed to work hand in han
18 matches
Mail list logo
