On Jo, 29 iul 10, 08:41:57, Andrei Popescu wrote:
On Mi, 28 iul 10, 16:10:38, Jordon Bedwell wrote:
On 7/28/10 4:03 PM, Jordan Metzmeier wrote:
On 07/28/2010 04:11 PM, Jordon Bedwell wrote:
find / |grep libraptor
Perhaps you wanted find's -name option? find / -name 'libraptor*'
On Thu, Jul 29, 2010 at 08:41:57AM +0300, Andrei Popescu wrote:
On Mi, 28 iul 10, 16:10:38, Jordon Bedwell wrote:
On 7/28/10 4:03 PM, Jordan Metzmeier wrote:
On 07/28/2010 04:11 PM, Jordon Bedwell wrote:
find / |grep libraptor
Perhaps you wanted find's -name option? find / -name
On Jo, 29 iul 10, 09:50:32, Tzafrir Cohen wrote:
If you stop it with ctrl-C, both find and grep get interrupted and stop,
right?
Actually I don't know how shell pipes work here. Is the output of find
piped to grep only when find finishes or as soon as there is some
output?
Regards,
Andrei
On 7/29/10 4:57 AM, Andrei Popescu wrote:
On Jo, 29 iul 10, 09:50:32, Tzafrir Cohen wrote:
If you stop it with ctrl-C, both find and grep get interrupted and stop,
right?
Actually I don't know how shell pipes work here. Is the output of find
piped to grep only when find finishes or as soon
On Jo, 29 iul 10, 05:08:27, Jordon Bedwell wrote:
[snip]
Thanks, learned some new stuff.
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
signature.asc
Description: Digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/29/2010 06:08 AM, Jordon Bedwell wrote:
I opt to pipe to grep because I usually do a lot more complicated things
with find and over time, I just kept using grep, it's a personal
preference really. Just like using locate is far faster
On Thursday 29 July 2010 07:38:00 Jordan Metzmeier wrote:
For me it something that I just cringe to see. I realize that in
practice, it is not bad. I just cannot get over feeling uneasy when
seeing things like:
find | grep
cat | grep
ls -l | grep
for i in $(ls -l foo/)
sudo su
I
On Qui, 29 Jul 2010, Boyd Stephen Smith Jr. wrote:
I understand your issues with all but the last one. A user may need to sudo
su due to configuration outside of their control. A system that
requires you
to sudo su for some task is likely misconfigured, but it is a
useful tool to
have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/29/2010 12:22 PM, Boyd Stephen Smith Jr. wrote:
I understand your issues with all but the last one. A user may need
to sudo su due to configuration outside of their control. A system
that requires you to sudo su for some task is likely
On Thursday 29 July 2010 11:25:51 Eduardo M KALINOWSKI wrote:
On Qui, 29 Jul 2010, Boyd Stephen Smith Jr. wrote:
I understand your issues with all but the last one. A user may need to
sudo su due to configuration outside of their control. A system that
requires you
to sudo su for some
On Thursday 29 July 2010 11:31:05 Jordan Metzmeier wrote:
On 07/29/2010 12:22 PM, Boyd Stephen Smith Jr. wrote:
I understand your issues with all but the last one. A user may need
to sudo su due to configuration outside of their control. A system
that requires you to sudo su for some task
On 7/29/10 11:31 AM, Jordan Metzmeier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/29/2010 12:22 PM, Boyd Stephen Smith Jr. wrote:
I understand your issues with all but the last one. A user may need
to sudo su due to configuration outside of their control. A system
that
On Jo, 29 iul 10, 08:38:00, Jordan Metzmeier wrote:
For me it something that I just cringe to see. I realize that in
practice, it is not bad. I just cannot get over feeling uneasy when
seeing things like:
find | grep
cat | grep
ls -l | grep
for i in $(ls -l foo/)
sudo su
add
dpkg -l
On 7/29/10 11:51 AM, Boyd Stephen Smith Jr. wrote:
On Thursday 29 July 2010 11:31:05 Jordan Metzmeier wrote:
On 07/29/2010 12:22 PM, Boyd Stephen Smith Jr. wrote:
I understand your issues with all but the last one. A user may need
to sudo su due to configuration outside of their control. A
On Qui, 29 Jul 2010, Boyd Stephen Smith Jr. wrote:
See my reply to Eduardo. In short, having (sudo su) available does not mean
that (sudo -i) will work.
Well, if you wanna give a full root shell to someone, then do it in
the correct way (allowing sudo -i to work), instead of allowing su
On Qui, 29 Jul 2010, Andrei Popescu wrote:
add
dpkg -l | grep packagename
At least here (a somewhat old 8.04 Ubuntu), dpkg -l still requires grep:
$ dpkg -l gnome
No packages found matching gnome.
$ dpkg -l | grep gnome
$ LANG=C dpkg -l | grep gnome
ii bluez-gnome
On Thursday 29 July 2010 11:56:45 Eduardo M KALINOWSKI wrote:
On Qui, 29 Jul 2010, Boyd Stephen Smith Jr. wrote:
See my reply to Eduardo. In short, having (sudo su) available does not
mean that (sudo -i) will work.
Well, if you wanna give a full root shell to someone, then do it in
the
On Thursday 29 July 2010 11:51:55 Jordon Bedwell wrote:
On 7/29/10 11:31 AM, Jordan Metzmeier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/29/2010 12:22 PM, Boyd Stephen Smith Jr. wrote:
I understand your issues with all but the last one. A user may need
to sudo su
On Jo, 29 iul 10, 13:59:29, Eduardo M KALINOWSKI wrote:
On Qui, 29 Jul 2010, Andrei Popescu wrote:
add
dpkg -l | grep packagename
At least here (a somewhat old 8.04 Ubuntu), dpkg -l still requires grep:
$ dpkg -l gnome
No packages found matching gnome.
Of course, there is no package
Is is possible to get amaya_wx-11.3.1-1_amd64.deb to run on sid?
I've installed it with dpkg but get the following error message:
~$ amaya
/usr/lib/Amaya/wx/bin/amaya_bin: error while loading shared libraries:
libraptor.so.1: cannot open shared object file: No such file or directory to
I
On 7/28/10 2:46 PM, Charles Kroeger wrote:
Is is possible to get amaya_wx-11.3.1-1_amd64.deb to run on sid?
I've installed it with dpkg but get the following error message:
~$ amaya
/usr/lib/Amaya/wx/bin/amaya_bin: error while loading shared libraries:
libraptor.so.1: cannot open shared object
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/28/2010 04:11 PM, Jordon Bedwell wrote:
find / |grep libraptor
if you don't come up with it in lib then which ever one is there that
says 1 symlink libraptor.so.1 to it. Then go on about your way, or
you can download the source to
On 7/28/10 4:03 PM, Jordan Metzmeier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/28/2010 04:11 PM, Jordon Bedwell wrote:
find / |grep libraptor
if you don't come up with it in lib then which ever one is there that
says 1 symlink libraptor.so.1 to it. Then go on about your
On 2010-07-28 21:46 +0200, Charles Kroeger wrote:
Is is possible to get amaya_wx-11.3.1-1_amd64.deb to run on sid?
If you're using the amd64 architecture, most probably yes. Your
X-Newsreader header suggests that you run i386, however.
I've installed it with dpkg but get the following error
svenj...@gmx.de
Date: Wed, 28 Jul 2010 23:31:05
To: debian-user@lists.debian.org
Subject: Re: Amaya W3C Web browser and sid
On 2010-07-28 21:46 +0200, Charles Kroeger wrote:
Is is possible to get amaya_wx-11.3.1-1_amd64.deb to run on sid?
If you're using the amd64 architecture, most probably yes
Jordon Bedwell said:
you can download the source to amaya and compile it against your
libraptor install (which is what I recommend personally).
Thanks for this suggestion. Would you mind describing the steps in detail. If
it solves my problem I would add these commands to my personal growing
On Mi, 28 iul 10, 16:10:38, Jordon Bedwell wrote:
On 7/28/10 4:03 PM, Jordan Metzmeier wrote:
On 07/28/2010 04:11 PM, Jordon Bedwell wrote:
find / |grep libraptor
Perhaps you wanted find's -name option? find / -name 'libraptor*'
I personally prefer to grep over find, but to each their
27 matches
Mail list logo
