> Dear hackers, thanks for maintaining it on FreeBSD
you are welcome, and happy new year for everybody! :)
why rename killall? what's next? rename init? why not enhance kill? this is the
end of alias? omg...
write shell script and name it, this is not a sin. it can be a crime... but
don
Stephen Montgomery-Smith escribió:
> I would like to introduce a program into the base called
> "screw-the-whole-system." It would do something like this:
>
> while true; do \
> echo "Please wait while your system is being destroyed..."
> sleep 10
> done
>
> ___
Jason A. Spiro wrote:
> On Tue, Dec 22, 2009 at 7:00 PM, Doug Barton wrote:
>
>> And yet there is ZERO interest in changing this in FreeBSD.
>
> As you can see elsewhere in this thread, I am discussing it with Xin.
> So far, both he and the Linux killall maintainer have said "no", but I
> am usi
On 2009/12/22 16:21, Jason Spiro wrote:
Xin LI delphij.net> writes:
killall can be used by scripts which just works in the past, and will
never notice the warnings.
On what scripts will nobody notice the warnings? For example, AFAIK, cron job
output is always mailed to root. The only scri
On Tue, Dec 22, 2009 at 7:00 PM, Doug Barton wrote:
> And yet there is ZERO interest in changing this in FreeBSD.
As you can see elsewhere in this thread, I am discussing it with Xin.
So far, both he and the Linux killall maintainer have said "no", but I
am using rational arguments to try to con
Xin LI delphij.net> writes:
> killall can be used by scripts which just works in the past, and will
> never notice the warnings.
On what scripts will nobody notice the warnings? For example, AFAIK, cron job
output is always mailed to root. The only scripts I can think of are scripts
called by
Jason A. Spiro wrote:
> On Tue, Dec 22, 2009 at 6:44 PM, Doug Barton wrote:
>> There
>> is no hope whatsoever that you're going to get every Unix that has a
>> rational 'killall' command to change, so can we please drop this thread?
>
> It's never too late to change something for the better.
An
On Tue, Dec 22, 2009 at 6:44 PM, Doug Barton wrote:
> Seriously, it's not our problem if solaris did something stupid.
Actually, it looks like the mistake was made by Linux and FreeBSD
developers. SunOS had[1] killall in 1992, and maybe earlier. Craig
said the earliest copyright date on Linux
You forgot to mention that we should wait ten years; and after that
change it's name to "killall"
Stephen Montgomery-Smith schreef:
> I would like to introduce a program into the base called
> "screw-the-whole-system." It would do something like this:
>
> while true; do \
> echo "Please wait whil
On 2009/12/22 14:54, Jason A. Spiro wrote:
Hi Xin,
On Tue, Dec 22, 2009 at 5:34 PM, Xin LI wrote:
I'm afraid that it's too late to change either parties, i.e. there
would be a lot of scripts that rely on the BSD or Linux behavior, etc.
That is why I suggested that you first show a warning m
Jason Spiro wrote:
> Using aliases would help me, but wouldn't help people elsewhere in the world
> who
> don't know what SysV killall does.
Seriously, it's not our problem if solaris did something stupid. There
is no hope whatsoever that you're going to get every Unix that has a
rational 'killa
On Tue, Dec 22, 2009 at 5:03 PM, Jason A. Spiro wrote:
[snip]
> Xin, I'd like to discuss this issue with you by some means other than
> email.
Followup to my earlier message: Thanks for sending me a private mail
with your Jabber address. I added you. But then I saw your most
recent list post,
Hi Xin,
On Tue, Dec 22, 2009 at 5:34 PM, Xin LI wrote:
> I'm afraid that it's too late to change either parties, i.e. there
> would be a lot of scripts that rely on the BSD or Linux behavior, etc.
That is why I suggested that you first show a warning message for five
years, then do the renaming
Hi,
On Tue, Dec 22, 2009 at 2:06 PM, Jason Spiro wrote:
> jhell DataIX.net> writes:
>>
>> This is what shell aliases are for and what a system admins job consist
>> of. If it gives you that much of a problem just alias it out for your self
>> in your .cshrc .shrc .bashrc .bash_profile etc. If yo
jhell DataIX.net> writes:
>
> This is what shell aliases are for and what a system admins job consist
> of. If it gives you that much of a problem just alias it out for your self
> in your .cshrc .shrc .bashrc .bash_profile etc. If you want to change
> something on a more per user basis figure
On Tue, Dec 22, 2009 at 2:18 AM, Xin LI wrote:
>
> No.
>
> killall is not part of standard, and, just because System V choose to
> implement that way, does not warrant that FreeBSD has to. Moreover,
> user can always alias /sbin/killall to 'fkill' and 'kill -15 -1' to
> 'killall' if they really w
Daniel O'Connor gsoft.com.au> writes:
>
> Why not get Sun and HP to change killall to match Linux & *BSD
> behaviour?
>
>
> Although seriously, why not? killall just killing everything is a fairly
> dangerous command with almost no use in the real world.
Because I find that when I send feed
Craig Small enc.com.au> writes:
> On Tue, Dec 22, 2009 at 01:31:02AM -0500, Jason A. Spiro wrote:
>
> Hello Jason (and the FreeBSD folk),
>
> The problem for me is that killall in Linux has been called that for a
> very long time now. psmisc came out 11 years ago and before that killall
> was i
Gary Jennejohn freenet.de> writes:
> I'm wondering why we even need killall when pkill seems to have the same
> basic functionality and is located in /bin (and /rescue) rather than /usr/bin?
I like killall because of its -v (verbose) option. It lets me know what killall
killed. You just inspir
On Tue, 22 Dec 2009 01:31, jasonspiro4@ wrote:
Dear Craig, thanks for maintaining the "killall" command on Linux.
Dear hackers, thanks for maintaining it on FreeBSD.
Naming it the same as System V killall, which just kills all
processes, can wreak havoc. When someone types a standard Linux
kil
I would like to introduce a program into the base called
"screw-the-whole-system." It would do something like this:
while true; do \
echo "Please wait while your system is being destroyed..."
sleep 10
done
___
freebsd-hackers@freebsd.org mailing list
On Tue, 22 Dec 2009, Craig Small wrote:
I also agree with Daniel; why would anyone want to literally kill every
process?
AFAIK, it's a helper program for shutdown(8) (or shutdown(1M) as they call
it) and isn't really intended to be useful otherwise.
--
Nate Eldredge
n...@thatsmathematics.c
On Tue, 22.12.2009 at 11:53:36 +0100, Gary Jennejohn wrote:
> On Mon, 21 Dec 2009 23:18:43 -0800
> Xin LI wrote:
>
> > On Mon, Dec 21, 2009 at 10:31 PM, Jason A. Spiro
> > wrote:
> > > Craig, and hackers, are you both willing to do this?
> >
> > No.
> >
> > killall is not part of standard, an
On Tue, Dec 22, 2009 at 01:31:02AM -0500, Jason A. Spiro wrote:
> Naming it the same as System V killall, which just kills all
> processes, can wreak havoc. When someone types a standard Linux
> killall command line as root on a Solaris or HP-UX server, System V
> killall runs and kills all proces
Am 22.12.2009 11:33, schrieb Dag-Erling Smørgrav:
> man pkill
And that one is also provided on Solaris.
--
Matthias Andree
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any m
On Mon, 21 Dec 2009 23:18:43 -0800
Xin LI wrote:
> On Mon, Dec 21, 2009 at 10:31 PM, Jason A. Spiro
> wrote:
> > Craig, and hackers, are you both willing to do this?
>
> No.
>
> killall is not part of standard, and, just because System V choose to
> implement that way, does not warrant that F
man pkill
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
On Mon, Dec 21, 2009 at 10:31 PM, Jason A. Spiro wrote:
> Craig, and hackers, are you both willing to do this?
No.
killall is not part of standard, and, just because System V choose to
implement that way, does not warrant that FreeBSD has to. Moreover,
user can always alias /sbin/killall to 'fk
On Tue, 22 Dec 2009, Jason A. Spiro wrote:
> Naming it the same as System V killall, which just kills all
> processes, can wreak havoc. When someone types a standard Linux
> killall command line as root on a Solaris or HP-UX server, System V
> killall runs and kills all processes.
>
> It might be
Dear Craig, thanks for maintaining the "killall" command on Linux.
Dear hackers, thanks for maintaining it on FreeBSD.
Naming it the same as System V killall, which just kills all
processes, can wreak havoc. When someone types a standard Linux
killall command line as root on a Solaris or HP-UX se
30 matches
Mail list logo
