...making Linux just a little more fun!
Ben Okopnik [ben at linuxgazette.net]
[ Again, Arild - please remember to CC the list. ]
On Sun, Mar 29, 2009 at 08:16:45PM -0700, deloresh wrote:
> Ben is this what you mean? > I am pretty sure I copied every word correctly then sent it to a > friend's address.Then it got bounced to me in my windows computer. > > ----- Original Message ----- From: <[email protected]> > To: <[email protected]> > Sent: Sunday, March 29, 2009 8:11 PM > Subject: siggen problem > arild@Arildlinux:~$ > arild@Arildlinux:~$ siggen > siggen: Display signature function values. > Tripwire(R) 2.3.1.2 built for > Tripwire 2.3 Portions copyright 2000 Tripwire, Inc. Tripwire is a registered > trademark of Tripwire, Inc. This software comes with ABSOLUTELY NO WARRANTY; > for details use --version. This is free software which may be redistributed > or modified only under certain conditions; see COPYING for details. > All rights reserved. > Use --help to get help. > arild@Arildlinux:~$
Well done, Arild! Yep, exactly what I mean.
What this implies to me is that 1) you have "tripwire" installed (which you don't need), and 2) that you don't have the "siggen" package (as contrasted against the "siggen" program) installed. If you had both, the latter would normally get executed first - because it gets installed in a "higher priority" directory.
ben@Tyr:~$ apt-file search bin/siggen siggen: /usr/bin/siggen tripwire: /usr/sbin/siggen
In the default execution path, "/usr/bin" comes before "/usr/sbin" - so "/usr/bin/siggen" would get executed first. Here's what you need to do to fix it:
sudo dpkg -P tripwire sudo apt-get install siggen
That should take care of it. After you've run the above two commands, you should be able to type "siggen" at the command line and see the sound generator application.
-- * Ben Okopnik * Editor-in-Chief, Linux Gazette * http://LinuxGazette.NET *
[2elnav at netbistro.com]
The machine just stalled out. Why does it keep asking for a password?
arild@Arildlinux:~$ arild@Arildlinux:~$ sudo dpkg-p tripwire [sudo] password for arild: sudo: dpkg-p: command not found arild@Arildlinux:~$ arild@Arildlinux:~$ arild@Arildlinux:~$ sudo dpkg-p tripwire sudo apt-get install siggen sudo: dpkg-p: command not found arild@Arildlinux:~$ arild@Arildlinux:~$ arild@Arildlinux:~$ arild@Arildlinux:~$ "sudo dpkg-P tripwire> sudo apt-get install siggen > > > > > sudo dpkg -P tripwire > sudo apt-get install siggen > > > > sudo dpkg-P tripwire > sudo apt-get install siggen >-------------------------------------------------- No response after 10 minutes.
Kapil Hari Paranjape [kapil at imsc.res.in]
Hello,
On Mon, 30 Mar 2009, [email protected] wrote:
> The machine just stalled out. > Why does it keep asking for a password? > > arild@Arildlinux:~$ > arild@Arildlinux:~$ sudo dpkg-p tripwire
Please read Ben's original response carefully.
Big hint: Spaces are important as are distinctions between uppper and lower case.
Kapil. --
Ben Okopnik [ben at linuxgazette.net]
On Mon, Mar 30, 2009 at 12:23:40AM -0700, [email protected] wrote:
> The machine just stalled out. > Why does it keep asking for a password? > > arild@Arildlinux:~$ sudo dpkg-p tripwire > [sudo] password for arild: > sudo: dpkg-p: command not found
The problem here is that you've used the wrong case for the option (it's supposed to be '-P', not '-p'); you've also missed a space (it's supposed to be 'dpkg -P', not 'dpkg-p'.) Note: it's VERY important to type things exactly as you're told to type them. This literally is as critical as correct diode polarity or the exact IC spec: if you get it wrong in any way, the circuit (or the command) is not going to work, period.
> arild@Arildlinux:~$ sudo dpkg-p tripwire sudo apt-get install siggen > sudo: dpkg-p: command not found
Wrong case, missing space.
> arild@Arildlinux:~$ "sudo dpkg-P tripwire
Missing space.
>> sudo apt-get install siggen
You're no longer typing on the command line. If the line does not begin with 'arild@Arildlinux:~$ ', it's not a command line; in fact, if it begins with '>', it's a "continuation prompt", meaning that the system considers the last command to be unfinished. The reason for that, in this case, is that you started the command line with a double-quote (right in front of the 'sudo' command) - and the shell is waiting for you to "close" that quote. Even then, that wouldn't help you - command names aren't supposed to have quotes in them - but at least you'd have received an error and been returned to the command prompt.
>> sudo dpkg -P tripwire
You're not typing on the command line.
>> sudo apt-get install siggen
You're not typing on the command line.
>> sudo dpkg-P tripwire
You're not typing on the command line.
>> sudo apt-get install siggen
You're not typing on the command line.
> No response after 10 minutes.
Not surprising; you're stuck in the middle of an uncompleted command.
Here's how that's interaction is supposed to go:
1) You type "sudo dpkg <options, etc.>".
2) Depending on how recently you've type "sudo", you may be asked for a password. If you are, then you need to type one in (note that what you type will not appear on the screen; it's a security measure that prevents "shoulder-surfing" - people stealing your password by looking at what you type.)
3) At that point, the "dpkg" command will execute, which will take a while (anywhere from about 15 seconds to a couple of minutes.) You should see informational messages on the screen within a couple of seconds of its execution.
4) Once it's finished, you'll be returned to the standard prompt (e.g, 'arild@Arildlinux:'.)
If you get stuck somewhere in the middle of that - whether via some mistype or whatever the reason - and you see that things aren't moving along the way they should, hit 'Ctrl-C' to break out.
-- * Ben Okopnik * Editor-in-Chief, Linux Gazette * http://LinuxGazette.NET *