SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The wall command in Slackware (at least in Slackware Current) is from util-linux-ng 2.18 and doesn't appear to support the -n option. Perhaps the gentoo one is from a different origin or version.
There's plenty of ways of doing this though,
msmi10 has since modified his code example above to something that should work (though it'd be better with quotes) so I'm not sure why there was a need to resurrect this thread once again. Resurrecting long dead threads wastes everyone's time and is annoying when you don't spot it is a zombie. Reading back I was clearly overly harsh with him, I guess I wasn't in a very tolerant mood that day (Everyone has bad days).
In the hopes of finally laying this one to rest, I'll just finish with another couple of possibilities.
In recent bash versions, you can use the syntax
Code:
wall <<< "Never argue with an idiot. They drag you down to their level and then beat you with experience."
More portably, you can use a here-document, which also has the advantage of allowing you to do a few other fancy things like pre-formatting, or include variables
and command substitutions
Code:
wall <<_EOF
Some text here
and here's some indented
and today's date is $(date)
and so on.
_EOF
or, as has already been mentioned you can just take the input from the output of another command in the more usual pipe syntax, as per the now corrected example msmi10 posted.
The wall command in Slackware (at least in Slackware Current) is from util-linux-ng 2.18 and doesn't appear to support the -n option. Perhaps the gentoo one is from a different origin or version.
Here, it works even without the -n option. On Gentoo, that command is part of sysvinit-2.88-r1. So, there is no telling what sort of differences there is between Gentoo and Slackware.
Here, it works even without the -n option. On Gentoo, that command is part of sysvinit-2.88-r1. So, there is no telling what sort of differences there is between Gentoo and Slackware.
There are one or two commands that seem to be differ between distros: 'rename' is another one that I find differs.
Having said that, basic 'wall' usage is that simple I'm surprised anyone could manage to have a problem using it.
Anyway, old thread and really not worth labouring over. Thanks for posting dalek.
There are one or two commands that seem to be differ between distros: 'rename' is another one that I find differs.
Having said that, basic 'wall' usage is that simple I'm surprised anyone could manage to have a problem using it.
Anyway, old thread and really not worth labouring over. Thanks for posting dalek.
Yea but it did remind me to update my sig with the new and improved rig.
ah-ha.... i did a "man wall" and the manpage says:
Code:
WALL(1) BSD General Commands Manual WALL(1)
NAME
wall -- write a message to users
SYNOPSIS
wall [file]
DESCRIPTION
Wall displays the contents of file or, by default, its standard input, on
the terminals of all currently logged in users.
Only the super-user can write on the terminals of users who have chosen
to deny messages or are using a program which automatically denies mes-
sages.
Reading from a file is refused when the invoker is not superuser and the
program is suid or sgid.
SEE ALSO
mesg(1), talk(1), write(1), shutdown(8)
HISTORY
A wall command appeared in Version 7 AT&T UNIX.
AVAILABILITY
The wall command is part of the util-linux-ng package and is available
from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/.
Linux 0.99 March 8, 1993 Linux 0.99
~
so yes, Slack uses the BSD wall, but the manpage really doesn't go into the details of the stdin input usage.
gee... from looking at the manpage for talk, it looks like talk could be used as a basic IM on a local network... i'll have to play with it a bit
Last edited by unclejed613; 01-13-2011 at 05:44 PM.
Mine says it was written by Miquel van Smoorenburg and at the top says "Linux User's Manual". It appears that Gentoo uses something entirely different. Sort of wonder why they didn't name it something different too. Maybe gwall or something if it is only used on Gentoo.
maybe that's why this topic is in the Slackware forum, not the Ubuntu one.
if you have questions/reports about the usage of wall on Ubuntu, open a topic on the dedicated forum, don't revive an old thread on random ones (if you had read all this one you could have seen this -the awkward reviving- already happened in this same thread).
I joined just to say I use your site all the time and finding threads even as old as 2003 and having users still replying to them in 2015 and beyond shouldn't upset people because they're 'old'. This information is still useful, even today. Isn't that the point of a forum like this?
ANYWAY, I found the information on wall <<< "text here" useful, so thanks!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.