From: "Нижник Денис" <denis@bibirevo.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: LARTC digest, Vol 1 #1385 - 4 msgs
Date: Sun, 28 Sep 2003 09:19:59 +0000 [thread overview]
Message-ID: <marc-lartc-106474091631194@msgid-missing> (raw)
Здравствуйте lartc-request,
Sunday, September 28, 2003, 8:45:03 AM, you wrote:
lrmdn> Send LARTC mailing list submissions to
lrmdn> lartc@mailman.ds9a.nl
lrmdn> To subscribe or unsubscribe via the World Wide Web, visit
lrmdn> http://mailman.ds9a.nl/mailman/listinfo/lartc
lrmdn> or, via email, send a message with subject or body 'help' to
lrmdn> lartc-request@mailman.ds9a.nl
lrmdn> You can reach the person managing the list at
lrmdn> lartc-admin@mailman.ds9a.nl
lrmdn> When replying, please edit your Subject line so it is more specific
lrmdn> than "Re: Contents of LARTC digest..."
lrmdn> Today's Topics:
lrmdn> 1. Re: compile errors (Jacek Bilski)
lrmdn> 2. Re: compile errors (Andrew Carson)
lrmdn> 3. frontend for tcc ? (Steve Wright)
lrmdn> 4. Re: Simulated latency (sufcrusher)
lrmdn> --__--__--
lrmdn> Message: 1
lrmdn> Subject: Re: [LARTC] compile errors
lrmdn> From: Jacek Bilski <dino@camelot.homedns.org>
lrmdn> To: LARTC <lartc@mailman.ds9a.nl>
lrmdn> Date: Sat, 27 Sep 2003 10:30:40 +0200
lrmdn> --=-Vt76b8g4rzsiQwlx1fs7
lrmdn> Content-Type: text/plain
lrmdn> Content-Transfer-Encoding: quoted-printable
lrmdn> Hello!
lrmdn> On sob, 2003-09-27 at 05:11, Andrew Carson wrote:
>> I've noticed a few people have had probs compiling iproute2 on the 2.4.22
>> kernel.. has anyone found a fix yet? I'm having the same problem:
lrmdn> Workaround: make your /usr/src/linux point to /usr/src/linux-2.4.21
lrmdn> rather than /usr/src/linux-2.4.22, it works_for_me (TM). I didn't
lrmdn> investigate where from are those errors.
lrmdn> Greetings!
lrmdn> --
lrmdn> Jacek Bilski <dino@camelot.homedns.org>
lrmdn> --=-Vt76b8g4rzsiQwlx1fs7
lrmdn> Content-Type: application/pgp-signature; name=signature.asc
lrmdn> Content-Description: This is a digitally signed message part
lrmdn> -----BEGIN PGP SIGNATURE-----
lrmdn> Version: GnuPG v1.2.3 (GNU/Linux)
lrmdn> iD8DBQA/dUqwx3yucFtEz74RAmeNAJ9nSW2Qqo/DLTb/gEeUUGO3c++hwACfYmxA
lrmdn> sqo6GMcRcaiNdzcqlLOQjZQlrmdn> fV3
lrmdn> -----END PGP SIGNATURE-----
lrmdn> --=-Vt76b8g4rzsiQwlx1fs7--
lrmdn> --__--__--
lrmdn> Message: 2
lrmdn> From: "Andrew Carson" <acarson@iinet.net.au>
lrmdn> To: <lartc@mailman.ds9a.nl>
lrmdn> Subject: Re: [LARTC] compile errors
lrmdn> Date: Sat, 27 Sep 2003 16:55:51 +0800
lrmdn> Jacek,
lrmdn> Yep, that's what I ended up doing too... Oh well, it's a fix for now :^)
lrmdn> Andrew.
lrmdn> --__--__--
lrmdn> Message: 3
lrmdn> From: Steve Wright <paua@quicksilver.net.nz>
lrmdn> To: lartc@mailman.ds9a.nl
lrmdn> Organization:
lrmdn> Date: 28 Sep 2003 07:46:14 +1200
lrmdn> Subject: [LARTC] frontend for tcc ?
lrmdn> --=-f9TrBrbE2+a4vppFhaJ2
lrmdn> Content-Type: text/plain
lrmdn> Content-Transfer-Encoding: 7bit
lrmdn> Hey All,
lrmdn> Does anyone know of a web/other front-end for tcc ?
lrmdn> TIA,
lrmdn> Steve
lrmdn> --=-f9TrBrbE2+a4vppFhaJ2
lrmdn> Content-Type: text/html; charset=utf-8
lrmdn> Content-Transfer-Encoding: 7bit
lrmdn> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
lrmdn> <HTML>
lrmdn> <HEAD>
lrmdn> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
lrmdn> <META NAME="GENERATOR" CONTENT="GtkHTML/1.1.9">
lrmdn> </HEAD>
lrmdn> <BODY>
lrmdn> Hey All,<BR>
lrmdn> <BR>
lrmdn> Does anyone know of a web/other front-end for tcc ?<BR>
lrmdn> <BR>
lrmdn> <BR>
lrmdn> TIA,<BR>
lrmdn> Steve<BR>
lrmdn> <BR>
lrmdn> </BODY>
lrmdn> </HTML>
lrmdn> --=-f9TrBrbE2+a4vppFhaJ2--
lrmdn> --__--__--
lrmdn> Message: 4
lrmdn> From: "sufcrusher" <sufcrusher@zonnet.nl>
lrmdn> To: "Morey ixipetl" <mixipetl@comcast.net>
lrmdn> Cc: <lartc@mailman.ds9a.nl>
lrmdn> Subject: Re: [LARTC] Simulated latency
lrmdn> Date: Sun, 28 Sep 2003 02:21:55 +0200
lrmdn> You could use the iptables QUEUE target. It allows you to "catch" packets in
lrmdn> a user space program (e.g. perl), do stuff with it (or nothing: sleep) and
lrmdn> then ACCEPT the packet (or DROP).
lrmdn> It's a pretty crude method, but it works.
lrmdn> ----- Original Message -----
lrmdn> From: "Morey ixipetl" <mixipetl@comcast.net>
lrmdn> Cc: <lartc@mailman.ds9a.nl>
lrmdn> Sent: Thursday, September 25, 2003 5:27 PM
lrmdn> Subject: [LARTC] Simulated latency
>> This seems like it ought to be simple, but so far, no joy. I need to
>> simulate latency in a network connection, e.g. a sattelite link, but
>> can't figure out how to do that. I don't need to drop packets or
>> otherwise limit rates, just introduce certain fixed amounts of latency.
>> I know about NIST Net, but would rather use iptables, ip, tc, etc. Any
>> ideas?
lrmdn> --__--__--
lrmdn> _______________________________________________
lrmdn> LARTC mailing list
lrmdn> LARTC@mailman.ds9a.nl
lrmdn> http://mailman.ds9a.nl/mailman/listinfo/lartc
lrmdn> End of LARTC Digest
--
С наилучшими пожеланиями,
Денис mailto:denis@bibirevo.net
Powered by The Bat! 1.53d
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-09-28 9:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-106474091631194@msgid-missing \
--to=denis@bibirevo.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.