From: "Pádraig Brady" <P@draigBrady.com>
To: Karel Zak <kzak@redhat.com>
Cc: Albert Cahalan <acahalan@gmail.com>,
List util-linux-ng <util-linux-ng@vger.kernel.org>,
"Alfred M. Szmidt" <ams@gnu.org>, Evan Hunt <ethanol@armory.com>
Subject: Re: kill
Date: Wed, 20 Dec 2006 10:03:36 +0000 [thread overview]
Message-ID: <45890A78.1030105@draigBrady.com> (raw)
In-Reply-To: <20061220085706.GH5971@petra.dvoda.cz>
Karel Zak wrote:
> On Wed, Dec 20, 2006 at 01:42:13AM -0500, Albert Cahalan wrote:
>> Karel Zak writes:
>>
>>> I've originally thought about util-linux upstream fork,
>>> but as usually an fork is bad step. So.. I'd like to start
>>> some discussion before this step.
>> ...
>>> after few weeks I'm pleased to announce a new "util-linux-ng"
>>> project. This project is a fork of the original util-linux (2.13-pre7).
>> Well, how about giving me a chunk of it? I'd like /bin/kill please.
We definitely need less version of kill:
ubuntu: $ dpkg -S `which kill`
procps: /bin/kill
fedora: $ rpm -qf `which kill`
util-linux-2.12p-9.3
fedora: $ type kill
kill is a shell builtin
$ tar tzf coreutils-6.2.tar.gz | grep kill
coreutils-6.2/src/kill.c
coreutils-6.2/man/kill.1
coreutils-6.2/man/kill.x
> We can think about it. I'm not sure with this kind of changes in the
> next 2.13 release. That release should be more about bug fixes and
> code stabilisation.
agreed.
>
> I'd like to do some consolidation in 2.14. I also need explore why
> RHEL/FC uses the kill command from util-linux rather that from
> procps. And Suse and Debian?
On a similar note, there are utils in util-linux[-ng] that are
not specific to linux (like look, cal etc.)
There has been the proposal for a new miscutils project
on the coreutils list: http://lists.gnu.org/archive/html/bug-coreutils/2006-11/msg00086.html
for which I am the proposed maintainer of.
Possibly some of these non specific linux utils could be moved there?
cheers,
Pádraig.
next prev parent reply other threads:[~2006-12-20 10:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <787b0d920612192242x3788f4bfh3be846d4188e3767@mail.gmail.com>
2006-12-20 8:57 ` kill (was: Re: util-linux: orphan) Karel Zak
2006-12-20 10:03 ` Pádraig Brady [this message]
2006-12-20 10:45 ` kill Karel Zak
2006-12-20 21:45 ` kill Alfred M. Szmidt
2006-12-20 23:55 ` kill Karel Zak
2006-12-21 4:10 ` kill Evan Hunt
2006-12-21 16:34 ` splitting util-linux (was: kill) Bryan Henderson
2006-12-21 21:53 ` Karel Zak
2006-12-22 6:12 ` Albert Cahalan
2006-12-22 7:13 ` Bryan Henderson
2006-12-22 9:06 ` Albert Cahalan
2006-12-22 7:23 ` Bryan Henderson
2006-12-22 7:45 ` Evan Hunt
2006-12-22 8:07 ` Karel Zak
2006-12-22 8:45 ` Evan Hunt
2006-12-22 11:03 ` Karel Zak
2006-12-22 16:52 ` Evan Hunt
2006-12-22 12:32 ` Ian Kent
2006-12-22 10:24 ` Karel Zak
2006-12-22 14:50 ` Mark Rosenstand
2006-12-22 17:38 ` Albert Cahalan
2006-12-25 20:03 ` Albert Cahalan
2006-12-25 22:50 ` Bryan Henderson
2006-12-22 6:44 ` Bryan Henderson
2006-12-22 7:52 ` Karel Zak
2006-12-21 10:51 ` kill Alfred M. Szmidt
2006-12-21 11:39 ` kill Martin Mares
2006-12-21 15:30 ` kill Karel Zak
2006-12-21 16:50 ` kill Alfred M. Szmidt
2006-12-21 17:38 ` kill Albert Cahalan
2006-12-22 1:37 ` kill Ian Kent
2006-12-20 15:00 ` kill Ian Kent
2006-12-20 16:58 ` kill Albert Cahalan
2006-12-20 16:33 ` kill (was: Re: util-linux: orphan) Albert Cahalan
2006-12-20 21:12 ` Karel Zak
2006-12-21 2:32 ` Albert Cahalan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45890A78.1030105@draigBrady.com \
--to=p@draigbrady.com \
--cc=acahalan@gmail.com \
--cc=ams@gnu.org \
--cc=ethanol@armory.com \
--cc=kzak@redhat.com \
--cc=util-linux-ng@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox