From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] u32 and fw coexistance
Date: Sun, 03 Feb 2002 10:32:04 +0000 [thread overview]
Message-ID: <marc-lartc-101273238411399@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101255514731508@msgid-missing>
On Fri, Feb 01, 2002 at 02:51:04PM +0530, Sumit Pandya wrote:
> Hi,
> Bert, I's replied by only you for my problem under subject "Two u32
> problems: module count and fw" in LARTC
> List(http://mailman.ds9a.nl/mailman/listinfo/lartc). But I think you felt
> bad from the way I responced and you stopped communication. Here by this
> mail I apologies for any unwanted mistakes and request you to go through the
> thread of mentioned subject in arcieves "2001q4".
> So don't you feel that is seems like some bug, and it must no longer exist
> in our favriote Linux. What is 'exploit script'? I can post that if in
> addition of those mentioned commands sequence, you require that script.
Well - if you find a problem, you should make it easy to reproduce for
others, so they can help.
See: http://www.tuxedo.org/~esr/faqs/smart-questions.html
And: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
That's what an exploit script does - it shows anybody the problem.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2002-02-03 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 9:33 [LARTC] u32 and fw coexistance Sumit Pandya
2002-02-03 10:32 ` bert hubert [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=marc-lartc-101273238411399@msgid-missing \
--to=ahu@ds9a.nl \
--cc=lartc@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