From: Alan Cox <alan@redhat.com>
To: msinz@wgate.com (Michael Sinz)
Cc: alan@redhat.com (Alan Cox),
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] kernel 2.5.5 - coredump sysctl
Date: Wed, 27 Feb 2002 09:05:14 -0500 (EST) [thread overview]
Message-ID: <200202271405.g1RE5EK15866@devserv.devel.redhat.com> (raw)
In-Reply-To: <3C7CE025.15DD5CD4@wgate.com> from "Michael Sinz" at Feb 27, 2002 08:33:25 AM
> BTW - are you looking at merging this into your tree (2.5 and/or 2.4)?
> I belive I can continue doing the patching here but it would be nice
> to have this generally available as some people (consulting clients of mine)
> don't want to run kernels that I build but only ones from RedHat...
I still can't decide if its worth the extra complexity.
I don't btw think the '/' is a big problem - only root can set the core
dump path, and current->comm is the "true" name of the program so won't
have a / in it
next prev parent reply other threads:[~2002-02-27 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 14:33 Michael Sinz
2002-02-21 15:12 ` Alan Cox
2002-02-21 15:41 ` Michael Sinz
2002-02-21 15:50 ` Alan Cox
2002-02-27 13:33 ` Michael Sinz
2002-02-27 14:05 ` Alan Cox [this message]
2002-02-27 15:38 ` Michael Sinz
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=200202271405.g1RE5EK15866@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=msinz@wgate.com \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®