Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] "Bug" in howto 4.2.1 Split access and other advice
Date: Fri, 05 Jul 2002 19:27:52 +0000	[thread overview]
Message-ID: <marc-lartc-102589730306034@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102589034132084@msgid-missing>

On Friday 05 July 2002 21:05, Arthur van Leeuwen wrote:
> On Fri, 5 Jul 2002, Stef Coene wrote:
> > On Friday 05 July 2002 20:47, Arthur van Leeuwen wrote:
> > > On Fri, 5 Jul 2002, Stef Coene wrote:
> > > > Hi,
> > > >
> > > > I was rereading the pages in the howto about multiple ISP's and I
> > > > also found some strange stuff in it.  Maybe you can create a patch
> > > > for Bert to update the howto ?
> > >
> > > Could you be more precies? :)
> >
> > export CVSROOT=:pserver:anon@outpost.ds9a.nl:/var/cvsroot
> > cvs login
> > CVS password: [enter 'cvs' (without 's)]
> > cvs co 2.4routing
> >    password = cvs
> > vi 2.4routing/2.4routing.sgml
> >
> >   :wq
> >
> > cvs diff -u > patch
> > uuencode patch patch | mail -s "HOWTO update"  HOWTO@ds9a.nl
>
> On what stuff you found strange, I meant... not on the process of sending
> in a patch for the HOWTO...
quoted from my post above :
> > > > I was rereading the pages in the howto about multiple ISP's and I
quoted from the subject
Re: [LARTC] "Bug" in howto 4.2.1 Split access and other advice

So I was talking about chapter 4.2 :
http://www.lartc.org/HOWTO//cvs/2.4routing/html/lartc.rpdb.multiple-links.html

> Doei, Arthur. (Jeez, nerds... :))
A real nerd takes a plane to Canada to talk about traffic shaping :)

Yesterday a colleague had a problem.  He had a redhat based firewall and 
installed NT4 on it.  After first reboot, lilo was still booting a linux 
kernel even after fdisk'ing the disk.  He couldn't remove the tux-virus :)

Stef

-- 
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-07-05 19:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-05 17:31 [LARTC] "Bug" in howto 4.2.1 Split access and other advice Ard van Breemen
2002-07-05 18:13 ` Arthur van Leeuwen
2002-07-05 18:25 ` Laurens van Alphen
2002-07-05 18:39 ` Stef Coene
2002-07-05 18:45 ` Arthur van Leeuwen
2002-07-05 18:47 ` Arthur van Leeuwen
2002-07-05 18:58 ` Stef Coene
2002-07-05 19:05 ` Arthur van Leeuwen
2002-07-05 19:27 ` Stef Coene [this message]
2002-07-05 19:39 ` Arthur van Leeuwen
2002-07-05 20:31 ` Julian Anastasov
2002-07-05 21:43 ` Stef Coene
2002-07-08 11:22 ` Ard van Breemen
2002-07-08 11:54 ` Ard van Breemen
2002-07-08 12:15 ` Julian Anastasov
2002-07-08 12:28 ` S Mohan
2002-07-08 13:50 ` 'Ard van Breemen'

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-102589730306034@msgid-missing \
    --to=stef.coene@docum.org \
    --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