Comments on: Bash fun

By: Florin

Florin — Fri, 21 May 2010 19:14:59 +0000

Having fun on windows: here’s how: http://forum.codecall.net/classes-code-snippets/13036-cowsay-c-version.html

By: cowcant root

cowcant root — Mon, 27 Jul 2009 04:14:25 +0000

I solved it. Thank you again Radu for your time and help. Please feel free to delete my non helpful post lol. I wouldn’t be offended.

By: cowcant root

cowcant root — Sun, 26 Jul 2009 10:22:40 +0000

sorry, didn’t post that one as it brought me back to original post:
sudo su
[sudo] password for myname:
*****:/home/myname# cowsay -f tux I see you > /dev/pts/1
bash: cowsay: command not found

Sorry, can’t send you money, but can send Thank Yous’ here
(I know not the same

By: Radu

Radu — Sun, 26 Jul 2009 09:01:36 +0000

Yeah… I’ve got two ideas. First issue who in a terminal to see who is logged in and where. Then do what Tudor has shown you. Afterwards maybe you can send me some money for support.

By: cowcant root

cowcant root — Sun, 26 Jul 2009 04:09:10 +0000

I’m back with a working sudo
sudo /etc/init.d/apache2 reload
[sudo] password for myname:
Reloading web server config: apache2.

But cowsay still can’t speak to another user. I’ve tried a variety of cmds:
sudo su cowsay -f moose I see you > /dev/pts/2
-bash: /dev/pts/2: Permission denied

sudo su cowsay -f moose I see you > sudo /dev/pts/2
su: invalid option — f
Usage: su [options] [LOGIN]

sudo su cowsay -f moose I see you > sudo su /dev/pts/2
su: invalid option — f
Usage: su [options] [LOGIN]

sudo cowsay -f moose I see you > /dev/pts/2
-bash: /dev/pts/2: Permission denied

sudo cowsay -f moose I see you > sudo /dev/pts/2
sudo: cowsay: command not found

cowsay -f moose I see you > sudo su /dev/pts/2
(no reply, and it didn’t say to user 2)

Any ideas? Thank you

By: cowcant root

cowcant root — Sat, 25 Jul 2009 02:03:53 +0000

Sorry Radu; stuck and very frustrated.
This is what I have done and the edited replies. I posted here: http://pastebin.com/m45312224
as worried too long for here and felt like it was ruining your nice cosway post
I’m also very nervous that I’m messing with the host files. Since I only have remote access to this box it would be impossible to fix it if it went off line because I mess something up real good.

Thank you very much!

PS. I didn’t mean to come here to have you fix all of this for me, sorry…if you want me to take it to a forum to fix, I understand Thank you again Radu!

By: cowcant root

cowcant root — Fri, 24 Jul 2009 06:14:18 +0000

Thank you Radu. I didn’t know that. All along I thought su & sudo were thee same thing just different cmd’s for different OS’s. Wow ok from cowsay to fixing this lol…

After some digging I found that I didn’t have ‘sudo’ (http://www.binbash.eu/linux/58-debian-etch-notes) so I did:

aptitude install sudo 
No /etc/sudoers found... creating one for you.

Ok so now I try (as a user and as root) sudo
reply same for both:

sudo: unable to resolve host PTy990499a.servername.com

(*PTy990499a.servername.com I have changed, it’s not the real server name, just similar)

cat /etc/hostname

simply has PTy990499a.servername.com and this hostname can not be resolved (Dns unable to resolve..). Where as the servername.com part can be resolved, correctly. And the PTy990499a part is what I see on the console on each line, for example:

PTy990499a:~# cat /etc/hostname
PTy990499a.servername.com
PTy990499a:~# cat /etc/hosts
127.0.0.1       localhost
200/66.123.66   PTy990499a.servername.com.servername.com  PTy990499a
 
# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

(*200/66.123.66 also not the real IP)

So I’m going to try to fix this myself, please don’t give away any clues and see if I can do this myself. Just a crazy busy day here. Will post when done or stuck
Thank you again Radu!

By: Radu

Radu — Thu, 23 Jul 2009 12:03:16 +0000

Try man sudo and see the difference between those options. If you try to use sudo as root, well that's not possible. sudo is meant only for users other than root, but they must be in the sudoers list. If you have tried sudo as a regular user and found that "error", you either are in the case mentioned in the previous phrase, either you have broken your hostname by not keeping consistency between /etc/hostname and /etc/hosts.

By: cowcant root

cowcant root — Thu, 23 Jul 2009 11:16:20 +0000

Radu thank you again.
Yes re sudo su:
sudo su
-bash: sudo: command not found

For my Debian its su which I believe is the same thing, yes?
So for su can’t cowsay
and for user can’t /dev/pts/1

Maybe I am misunderstanding the ‘sudo su’ thing?

Re the e-mail, to be honest, just a habit when registering isn’t required. Sorry I didn’t realize you had to approve each time so I have put my email this time

By: Radu

Radu — Thu, 23 Jul 2009 11:04:13 +0000

Tudor said sudo su. If you use sudo -i, as I used, it won’t work. For you to send that message with the exclamation mark, you just need to remove the quotes:

root@tux:/home/radu# cowsay -f sodomized I see you behind this cow! > /dev/pts/0
 ____________________________
< I see you behind this cow! >
 ----------------------------
                      _
                     (_)
           ^__^       / 
           (oo)_____/_ 
            (__)       ) /
                ||----w ((
                ||     ||>>

The first output of the sodomized cow was from BusyBox, on my router, which does not interpret the quotes like Ubuntu does.

P.S. Why are you afraid to use your email? If you use it, I wouldn’t have to approve every comment you make, only the first one registered with it. I’m not gonna sell it for spam…