From: "Vic Abell" <abe@purdue.edu>
To: <dave@gnu.org>, "'Karel Zak'" <kzak@redhat.com>
Cc: "'util-linux'" <util-linux@vger.kernel.org>
Subject: RE: adopting lslk
Date: Wed, 25 Jan 2012 05:40:24 -0500 [thread overview]
Message-ID: <6091E96C492146DC802B123BAA175195@radio> (raw)
In-Reply-To: <1327445685.3650.4.camel@offbook>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
Davidlohr,
You write:
>
> I just noticed this big fat message from the lslk(8) manpage:
>
> Revision 1.29 represents the end of life for lslk. I don't
> have time to support it. Please don't report bugs to me. I
> will politely
> decline to work on them.
>
> I was thinking util-linux might be a good place to continue
> maintaining this program, it seems worthwhile. I couldn't
> find the _official_ source tarball but I got it through apt.
>
> I could integrate it and send a patch. Any thoughts?
I'm a bit surprised that lslk is still alive anywhere. That
end of life notice is dated July 2001.
If you want to keep it going on Linux, I suggest you adopt
it and rewrite it.
The lslk source was originally organized to work on multiple
UNIX dialects, just like lsof. I never had time to extend
it to many dialects, but the multi-dialect organization is
superfluous for a single one. And, as Karel points out, the
code is terribly old and could stand serious work.
I am attaching a gzipped tar of the last distribution directory
in which lslk was found on my ftp server.
In your adoption process, please observe the simple terms on
the copyright notices that appear in each source file.
Good luck!
Vic
[-- Attachment #2: lslk.tgz --]
[-- Type: application/octet-stream, Size: 452950 bytes --]
prev parent reply other threads:[~2012-01-25 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 22:54 adopting lslk Davidlohr Bueso
2012-01-25 9:37 ` Karel Zak
2012-01-25 10:40 ` Vic Abell [this message]
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=6091E96C492146DC802B123BAA175195@radio \
--to=abe@purdue.edu \
--cc=dave@gnu.org \
--cc=kzak@redhat.com \
--cc=util-linux@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