Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Brandon Broyles" <netfilter@drbroyles.com>
To: fabrice@netfilter.org
Cc: netfilter@lists.netfilter.org
Subject: Re: Is there something wrong with patch-o-matic?
Date: Wed, 27 Nov 2002 22:14:01 -0500	[thread overview]
Message-ID: <023f01c2968c$33322f70$4545450a@drbroyles.com> (raw)
In-Reply-To: 200211281024.18984.fabrice@netfilter.org


----- Original Message -----
From: "Fabrice MARIE" <fabrice@netfilter.org>
To: "Brandon Broyles" <netfilter@drbroyles.com>; <netfilter@lists.netfilter.org>
Sent: Wednesday, November 27, 2002 9:24 PM
Subject: Re: Is there something wrong with patch-o-matic?


>
> BTW, are you really sure you don't have patch ? :)
> (usually, patch is /usr/bin/patch)
>
> Have a nice day,
>
> Fabrice.
> --
> Fabrice MARIE
>
> "Silly hacker, root is for administrators"
>        -Unknown
>

Nope, I didn't have patch installed.  Based on the message from Alexandros
Papadopoulos
(http://lists.netfilter.org/pipermail/netfilter/2002-November/040283.html) I
discovered that patch was a common command that should be on any Linux system.
I then installed it from my RedHat cd and then the patch-o-matic worked like it
should.  I am now using the time patch which was my goal from all of the
patching.  Thank you and thank you Alexandros.

Brandon Broyles



      reply	other threads:[~2002-11-28  3:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-23 16:34 Am I making a bone-headed mistake with patch-o-matic ? netfilter
2002-11-24  4:43 ` Fabrice MARIE
2002-11-24  5:40   ` electrode
2002-11-24  5:53   ` Brandon Broyles
2002-11-24 17:32     ` Is there something wrong with patch-o-matic? Brandon Broyles
2002-11-24 17:45       ` Alexandros Papadopoulos
2002-11-24 18:10         ` electrode
2002-11-28  2:24       ` Fabrice MARIE
2002-11-28  3:14         ` Brandon Broyles [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='023f01c2968c$33322f70$4545450a@drbroyles.com' \
    --to=netfilter@drbroyles.com \
    --cc=fabrice@netfilter.org \
    --cc=netfilter@lists.netfilter.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