On Wed, 10 Jun 2009 02:53:52 -0500
Dale wrote:
> > That's not quite correct: .py[co] are generated by emerge right after
> > package installaton and these won't come back unless you use these libs
> > as root, since python won't have write access to these paths and will
> > be byte-compiling each
Mike Kazantsev wrote:
> On Mon, 08 Jun 2009 19:27:39 -0500
> Dale wrote:
>
>
>>> Also, be careful when you parse the output of the command. Most of the
>>> .pyc and .pyo files in the python2.5 directories are byte-compiled
>>> version that python generated dynamically the first time they are
>>
On Tuesday 09 June 2009 17:20:49 Etaoin Shrdlu wrote:
> On Tuesday 9 June 2009, 16:36, Neil Bothwick wrote:
> > On Tue, 09 Jun 2009 16:15:21 +0200, Joerg Schilling wrote:
> > > > find -H /usr/lib /lib -type f | xargs -d'\n' qfile --orphans
> > >
> > > No, this is definitely wrong: the right way to
On Tue, 09 Jun 2009 16:59:39 +0200, Joerg Schilling wrote:
> > How does this handle quoted filenames?
>
> correctly.
Are you part Vorlon ;-)
--
Neil Bothwick
The world is a tragedy to those who feel, but a comedy to those who
think.(Horace Walpole)
signature.asc
Description: PGP signatur
On Tue, 9 Jun 2009 17:21:32 +0200, Etaoin Shrdlu wrote:
> > command "file 1 file 2 file 3"
> >
> > or
> >
> > command "file 1" "file 2" "file 3"
>
> The latter.
Thanks, and bye-bye xargs (not that I used it very often).
--
Neil Bothwick
Cross-country skiing is great in small countries.
s
On Tuesday 9 June 2009, 16:52, Neil Bothwick wrote:
> On Tue, 9 Jun 2009 09:42:34 -0500, Paul Hartman wrote:
> > -exec command {} +
> > This variant of the -exec action runs the specified command on the
> > selected files, but the command line is built by appending each
> > selected file name at t
On Tuesday 9 June 2009, 16:36, Neil Bothwick wrote:
> On Tue, 09 Jun 2009 16:15:21 +0200, Joerg Schilling wrote:
> > > find -H /usr/lib /lib -type f | xargs -d'\n' qfile --orphans
> >
> > No, this is definitely wrong: the right way to handle this is
> > execplus (since 19 years).
>
> If it's been a
Neil Bothwick wrote:
> On Tue, 9 Jun 2009 09:42:34 -0500, Paul Hartman wrote:
>
> > -exec command {} +
> > This variant of the -exec action runs the specified command on the
> > selected files, but the command line is built by appending each
> > selected file name at the end; the total number of
On Tue, 9 Jun 2009 09:42:34 -0500, Paul Hartman wrote:
> -exec command {} +
> This variant of the -exec action runs the specified command on the
> selected files, but the command line is built by appending each
> selected file name at the end; the total number of invocations of the
> command will
Neil Bothwick wrote:
> On Tue, 9 Jun 2009 16:04:41 +0200, Volker Armin Hemmann wrote:
>
> > > This is not a zsh limitation but a Linux limitation.
> > > You may have longer arg lists if you use Solaris ;-)
> > >
> > > You may avoid the problem with find . -exec prog args {} +
> >
> > ah, thank
On Tue, 09 Jun 2009 16:15:21 +0200, Joerg Schilling wrote:
> > find -H /usr/lib /lib -type f | xargs -d'\n' qfile --orphans
>
> No, this is definitely wrong: the right way to handle this is execplus
> (since 19 years).
If it's been around 19 years, why doesn't Google know anything about it?
W
2009/6/9 Joerg Schilling
>
> Volker Armin Hemmann wrote:
>
> > On Montag 08 Juni 2009, Neil Bothwick wrote:
> > > qfile --orphans $(find -H /usr/lib /lib -type f)
> >
> > qfile --orphans $(find -H /usr/lib /lib -type f)
> > zsh: argument list too long: qfile
>
> This is not a zsh limitation but a
On Tue, Jun 9, 2009 at 9:36 AM, Neil Bothwick wrote:
> If it's been around 19 years, why doesn't Google know anything about it?
> What is it?
from the manpage of "find", it even compares it to the xargs method:
-exec command {} +
This variant of the -exec action runs the specified command on the
2009/6/9 Joerg Schilling :
> Mickaël Bucas wrote:
>
>
>> > You may avoid the problem with find . -exec prog args {} +
>
>> The right way to handle any size for the list returned by "find", is
>> by using "xargs" :
>>
>> find -H /usr/lib /lib -type f | xargs -d'\n' qfile --orphans
>
> No, this is d
On Tue, 9 Jun 2009 16:04:41 +0200, Volker Armin Hemmann wrote:
> > This is not a zsh limitation but a Linux limitation.
> > You may have longer arg lists if you use Solaris ;-)
> >
> > You may avoid the problem with find . -exec prog args {} +
>
> ah, thank you - I just copied from Neil (and ha
Mickaël Bucas wrote:
> > You may avoid the problem with find . -exec prog args {} +
> The right way to handle any size for the list returned by "find", is
> by using "xargs" :
>
> find -H /usr/lib /lib -type f | xargs -d'\n' qfile --orphans
No, this is definitely wrong: the right way to handle
On Dienstag 09 Juni 2009, Joerg Schilling wrote:
> Volker Armin Hemmann wrote:
> > On Montag 08 Juni 2009, Neil Bothwick wrote:
> > > qfile --orphans $(find -H /usr/lib /lib -type f)
> >
> > qfile --orphans $(find -H /usr/lib /lib -type f)
> > zsh: argument list too long: qfile
>
> This is not a z
Volker Armin Hemmann wrote:
> On Montag 08 Juni 2009, Neil Bothwick wrote:
> > qfile --orphans $(find -H /usr/lib /lib -type f)
>
> qfile --orphans $(find -H /usr/lib /lib -type f)
> zsh: argument list too long: qfile
This is not a zsh limitation but a Linux limitation.
You may have longer arg l
On Montag 08 Juni 2009, Neil Bothwick wrote:
> qfile --orphans $(find -H /usr/lib /lib -type f)
qfile --orphans $(find -H /usr/lib /lib -type f)
zsh: argument list too long: qfile
bash
energy ~ # qfile --orphans $(find -H /usr/lib /lib -type f)
bash: /usr/bin/qfile: Argument list too long
bash -
On Mon, 08 Jun 2009 19:27:39 -0500
Dale wrote:
> > Also, be careful when you parse the output of the command. Most of the
> > .pyc and .pyo files in the python2.5 directories are byte-compiled
> > version that python generated dynamically the first time they are
> > used. For example: /Numeri
On Tue, 09 Jun 2009 12:05:05 +0200, Joerg Schilling wrote:
> > > qfile --orphans $(find -H /usr/lib /lib -type f)
> > >
> > > which avoids checking all the symlinks.
>
> In case that you find implementation works correctly, this will
> not change anything unless either /usr/lib or /lib are sym
Willie Wong wrote:
> > qfile --orphans $(find -H /usr/lib /lib -type f)
> >
> > which avoids checking all the symlinks.
In case that you find implementation works correctly, this will
not change anything unless either /usr/lib or /lib are symlinks.
If you however use find -L, -type f will find
On Tuesday 09 June 2009 02:27:39 Dale wrote:
> That's sort of what I was thinking. It was generated when it was
> started up the first time. I also noticed some things that I installed
> in the Seamonkey directory too. Adblock was one of those.
>
> Tho there was a good many of them, I suspect mo
Willie Wong wrote:
> On Mon, Jun 08, 2009 at 06:52:23PM -0500, Penguin Lover Dale squawked:
>
>> Questions: You knew I subscribed to this list. lol I ran the command:
>>
>> find -H /usr/lib /lib -type f | xargs qfile -o
>>
>> and I got a lot of hits. I'm just going to post snippets of the
>>
On Mon, Jun 08, 2009 at 06:52:23PM -0500, Penguin Lover Dale squawked:
> Questions: You knew I subscribed to this list. lol I ran the command:
>
> find -H /usr/lib /lib -type f | xargs qfile -o
>
> and I got a lot of hits. I'm just going to post snippets of the
> directories here. It is a LO
Neil Bothwick wrote:
> On Mon, 8 Jun 2009 22:44:18 +0200, Alan McKinnon wrote:
>
>
>> Is there an easy way to detect the orphaned libs on and old machine
>> who's install dates back to 2004? The only idea I can come up with is
>>
>> for I in /usr/lib/*.so.* ; do equery belongs $I ; done
>>
On Mon, Jun 08, 2009 at 09:54:08PM +0100, Penguin Lover Neil Bothwick squawked:
> On Mon, 8 Jun 2009 22:44:18 +0200, Alan McKinnon wrote:
>
> > Is there an easy way to detect the orphaned libs on and old machine
> > who's install dates back to 2004? The only idea I can come up with is
> >
> > fo
Alan McKinnon wrote:
> On Monday 08 June 2009 22:54:08 Neil Bothwick wrote:
>
>> On Mon, 8 Jun 2009 22:44:18 +0200, Alan McKinnon wrote:
>>
>>> Is there an easy way to detect the orphaned libs on and old machine
>>> who's install dates back to 2004? The only idea I can come up with is
>>>
>
On Monday 08 June 2009 22:54:08 Neil Bothwick wrote:
> On Mon, 8 Jun 2009 22:44:18 +0200, Alan McKinnon wrote:
> > Is there an easy way to detect the orphaned libs on and old machine
> > who's install dates back to 2004? The only idea I can come up with is
> >
> > for I in /usr/lib/*.so.* ; do eque
On Mon, 8 Jun 2009 22:44:18 +0200, Alan McKinnon wrote:
> Is there an easy way to detect the orphaned libs on and old machine
> who's install dates back to 2004? The only idea I can come up with is
>
> for I in /usr/lib/*.so.* ; do equery belongs $I ; done
qfile --orphans /usr/lib/*.so.*
or, m
Hi,
Is there an easy way to detect the orphaned libs on and old machine who's
install dates back to 2004? The only idea I can come up with is
for I in /usr/lib/*.so.* ; do equery belongs $I ; done
which strikes me as being a tad overkill...
--
alan dot mckinnon at gmail dot com
31 matches
Mail list logo
