<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Punky Tse wrote:
<blockquote cite="mid1a49df600508141924132cc3dc@mail.gmail.com"
type="cite">
<pre wrap="">Beat,
Of course, I has no problem to apply the IMQ patch to the voyage
kernel series. But the IMQ patch requires iptables patch to make it
fully functional? This is the problem...
I don't know, but can you tell me what the benefit of using IMQ but
not htq and cbq which should be natively supported by voyage kernel
and the built in iptables?
</pre>
</blockquote>
This works fine for outgoing shaping BUT for incoming shapping you
cannot use this<br>
If you want to limit bandwith of input AND output you MUST use imq.<br>
<br>
I have built the following packages for pebble:<br>
iproute2-2.6.11-050330<br>
iptables-1.3.2<br>
kismet-2005-06-R1<br>
madwifi-bsd-20050702<br>
openssh-4.0p1<br>
openssl-0.9.7g<br>
wavemon-0.0.4b<br>
wireless-tiils-28.pre8<br>
wpa_supplicant-0.4.3<br>
<br>
I think it's imported that someone can upgrade some stuff if there are
security patches new version<br>
like hostapd, wpa_supplicant.<br>
For that you cannot rely on the system openssl because it could be that
you should upgrade ssl.<br>
The problem is that some packges rely on ssl. If you stay in the same
version i.e. 0.9.7<br>
I think (and I didn't have) there should no problems to upgrade ssl.<br>
If you upgrade to 0.9.8 or what ever there maybe could be a problem.<br>
<br>
Greetings<br>
<br>
Beat<br>
<blockquote cite="mid1a49df600508141924132cc3dc@mail.gmail.com"
type="cite">
<pre wrap="">On 8/14/05, Beat Meier <a class="moz-txt-link-rfc2396E" href="mailto:bmeier@infovia.com.ar"><bmeier@infovia.com.ar></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Punky Tse wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Beat,
pebble is based on Debian woody while voyage is based on sarge. So
almost all packages used by them are mostly different. You can find
the package list used by voyage in /voyage.dpkg-l.
</pre>
</blockquote>
<pre wrap="">Ok missunderstanding: I have use until yet a modified pebble version.
Now I've installed voyage ...
</pre>
<blockquote type="cite">
<pre wrap="">kernel patch : I keep all patches for every kernel built. They are
all available at <a class="moz-txt-link-freetext" href="http://www.voyage.hk/download/kernel_patch/2.6/">http://www.voyage.hk/download/kernel_patch/2.6/</a>. And
yes, they diff against the corresponding debian kernel. But I heard
that someone were able to apply these patches against the stock kernel
as well.
</pre>
</blockquote>
<pre wrap="">Yes thats what I do now.
What I see is that you have not applied IMQ patch for example which is
almost a must
for traffic shapping.
Ok will have a look at the patches in
<a class="moz-txt-link-freetext" href="http://www.voyage.hk/download/kernel_patch/2.6/">http://www.voyage.hk/download/kernel_patch/2.6/</a>
Thanks
Beat
</pre>
<blockquote type="cite">
<pre wrap="">Punky
Beat Meier wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello
I've just upgrade from pebble to voyage.
Nice!
What I realy miss by all distros is what packages were modified from
the original distro.
It woult be nice to document in Wiki which packages are created or
modified from
the original version. Also which kernel patches were applied.
For example gcc- was modified because of dependencies i..e. almost
everything
in this package wad deleted ...
I think it's not much work (only the author knows (hopefully) which
packages
were modified but the help is realy great for developers/contributors.
The problem comes for example if you want to install kernels form
kernerl.org
You cannot diff the sources because the use kernel sources from
voyage base
on the debian kernel which have already modifed the sources.
So if the author say: I have aplied the IMQ patch from XXX we can
do the same with the stock kernel from kernerl.org.
More imported even which modules do you have to recompile if you want
use your own
kernel like for example madwifi -> hostapd, wpa_supplicant etc.
So peopple can use the distro and upgrade or use the kernel they MUST
use
for some constraints.
BTW: Is there any docu from debian which packages are incompatible with
using kernel 2.6 instead of 2.4?
In the future I will send some stuff (Skripts/changes) about wrap
which could be intgrated
if you have interess.
Greetings and thanks
Beat
_______________________________________________
Voyage-linux mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a>
<a class="moz-txt-link-freetext" href="http://list.voyage.hk/mailman/listinfo/voyage-linux">http://list.voyage.hk/mailman/listinfo/voyage-linux</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Voyage-linux mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a>
<a class="moz-txt-link-freetext" href="http://list.voyage.hk/mailman/listinfo/voyage-linux">http://list.voyage.hk/mailman/listinfo/voyage-linux</a>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>