From: "Bruce A. Locke" <blocke@shivan.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] lsof with gentoo CFLAGS
Date: Thu Jun 28 22:58:02 2001 [thread overview]
Message-ID: <20010629010019.6645c94f.blocke@shivan.org> (raw)
In-Reply-To: <3B3C08E7.6341648F@fidnet.com>
On Thu, 28 Jun 2001 23:49:43 -0500
"Tod M. Neidt" <tneidt@fidnet.com> wrote:
> One comment. From the documentation, lsof appears to be sensitive to
> the system kernel. It may require some kind of dependency so that if a
> new kernel is merged, lsof gets rebuilt for that kernel. I am not 100%
> sure if that necessary though.
If a kernel dependency needs to be added it might be a good idea to allow
for some way of overriding the dependency in case the end user decides not
to use the gentoo kernel-source packages, etc and uses a linus tree
instead (aka no entries in the db, etc). Or does such a thing exist
already?
---------------------------------------------------------------------
Bruce A. Locke
blocke@shivan.org
next prev parent reply other threads:[~2001-06-29 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 22:48 [gentoo-dev] lsof with gentoo CFLAGS Tod M. Neidt
2001-06-28 22:58 ` Bruce A. Locke [this message]
2001-06-28 23:20 ` Tod M. Neidt
2001-06-28 23:43 ` Daniel Robbins
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=20010629010019.6645c94f.blocke@shivan.org \
--to=blocke@shivan.org \
--cc=gentoo-dev@cvs.gentoo.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