* mkinitrd: binary operator expacted
From: plachninka @ 2002-12-17 8:52 UTC (permalink / raw)
To: linux-kernel
Hi
Can anyone tell me what means following message:
[root@tilda plachnina]# /sbin/mkinitrd initrd-2.4.18-18.7.xsmp.img
2.4.18-18.7.xsmp
/sbin/mkinitrd: [:
/lib/modules/2.4.18-18.7.xsmp/./kernel/drivers/scsi/aic7xxx/aic7xxx.o:
binary operator expected
I fight with aic7xxx module since 1 month...
regards
Mariusz Bozewicz
^ permalink raw reply
* Re: writing new BBRAM driver
From: Jörn Engel @ 2002-12-17 9:12 UTC (permalink / raw)
To: Alex Pavloff; +Cc: 'Tobias Otto-Adamczak', linux-mtd
In-Reply-To: <D3AF5F134D627243993F2F2FC32EE4D229C4B0@mailman.eason.com>
On Mon, 16 December 2002 14:33:41 -0800, Alex Pavloff wrote:
>
> Alright, one more question: What should the erasesize be for BBRAM?
> Obviously I'm not worried about wear, so should it be zero or one or
> something else?
Depends. :-)
For jffs2, you need 5 free blocks for operation. But every used block
eats up ~150Byte roughly, depending on data and compression. Bigger
blocks eat memory, more blocks eat memory, minimum is somewhere in the
middle, you do the math.
For minix, fat, ext2/3 etc., this doesn't really matter. I'd pick 4k,
as that is pagesize on most machines, but even 1byte might work - with
lots of overhead.
Jörn
--
But this is not to say that the main benefit of Linux and other GPL
software is lower-cost. Control is the main benefit--cost is secondary.
-- Bruce Perens
^ permalink raw reply
* .reginfo and .mdebug section
From: Long Li @ 2002-12-17 8:43 UTC (permalink / raw)
To: linux-mips
Hi,
I have some problems after building a linux-mips cross
compiler on Red Hat7.1.
1. I tried to compile some c code targetting mips4k,
which is 32-bit ISA. However, the map file tells me
that the compiled code are 64-bit, since the address
are 64-bit.
2. When I compiled the c code, I found in the mapfile
that there are some sections called .reginfo and
.mdebug. What are those sections? I would like to get
rid of them. However, they still exists even if I
deleted the '-g' option for gcc. Is there a way I can
avoid the .reginfo and .mdebug sections?
Thanks a lot!
Long
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
^ permalink raw reply
* Re: i845PE chipset and 20276 Promise Controller boot failure with 2.4.20-ac2
From: Andre Hedrick @ 2002-12-17 8:52 UTC (permalink / raw)
To: Denis Vlasenko; +Cc: edward.kuns, linux-kernel
In-Reply-To: <200212170646.gBH6kCs16053@Port.imtp.ilyichevsk.odessa.ua>
On Tue, 17 Dec 2002, Denis Vlasenko wrote:
> On 16 December 2002 21:09, edward.kuns@rockwellfirstpoint.com wrote:
> > acted exactly the same. So then I added a bunch of printk's to see
> > if I could localize where it was hanging and it died immediately
> > after displaying info about the PIIX driver.
>
> Way to go man! This will save tons of time for IDE folks if everyone
> who has problems go that far in debugging.
> If you'll play with printk a bit more, you will find it.
Really I am now curious as to when it first showed up.
This i845 has been a royal pain!
Andre Hedrick
LAD Storage Consulting Group
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: Andi Kleen @ 2002-12-17 8:56 UTC (permalink / raw)
To: Linus Torvalds; +Cc: mingo, linux-kernel, davej
In-Reply-To: <Pine.LNX.4.44.0212161639310.1623-100000@penguin.transmeta.com.suse.lists.linux.kernel>
Linus Torvalds <torvalds@transmeta.com> writes:
>
> That NMI problem is pretty fundamentally unfixable due to the stupid
> sysenter semantics, but we could just make the NMI handlers be real
> careful about it and fix it up if it happens.
You just have to make the NMI a task gate with an own TSS, then the
microcode will set up an own stack for you.
The only issue afterwards is that "current" does not work, but that
can be worked around by being a bit careful in the handler.
It has to run with interrupts off too to avoid a race with an
timer interrupt which uses current (or alternatively the timer
interrupt could check for the "in nmi condition" - I don't think
any other interrupts access current except when they crash)
[in theory it would be also possible to align the NMI stacks to
8K and put a "pseudo" task into that stack, but it would look
a bit inelegant for me]
Using a task gate would be a good idea for kernel stack faults and
double faults too, then it would be at least possible to get an oops
for them, not the usual double fault.
[x86-64 does it similarly, except that it uses ISTs instead of task
gates and avoids the current problem by using an explicit base register]
I cannot implement SYSENTER for x86-64/32bit emulation, but I think
I can change the vsyscall code to use SYSCALL, not SYSENTER. The only
issue is that I cannot easily use a fixmap to map into 32bit processes,
because the kernel fixmap are way up into the 48bit address space
and not reachable from compatibility mode.
I suspect a similar trick as with the lazy vmallocs - map it in the
page fault handler on demand will work. I hope there won't be much
more of these special cases though, do_page_fault is getting
awfully complicated.
-Andi
^ permalink raw reply
* Re: i845PE chipset and 20276 Promise Controller boot failure with 2.4.20-ac2
From: Andre Hedrick @ 2002-12-17 8:55 UTC (permalink / raw)
To: edward.kuns; +Cc: linux-kernel
In-Reply-To: <OF4D4BDDD2.8FD534AB-ON86256C91.007B9286-86256C91.007EE995@rockwellfirstpoint.com>
00:1f.1 IDE interface: Intel Corp. 82801DB ICH4 IDE (rev 02) (prog-if 8a
[Master SecP PriP])
Subsystem: Giga-byte Technology: Unknown device 24c2
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at 01f0
Region 1: I/O ports at 03f4
Region 2: I/O ports at 0170
Region 3: I/O ports at 0374
Region 4: I/O ports at cc00 [size=16]
Region 5: Memory at 20000000 (32-bit, non-prefetchable) [size=1K]
What needs to happen now that Intel has BAR5 is to switch the capablities
to MMIO away from bars 0-4!
Andre Hedrick
LAD Storage Consulting Group
^ permalink raw reply
* Re: Notification hooks
From: David Woodhouse @ 2002-12-17 9:05 UTC (permalink / raw)
To: Ben Collins
Cc: Arjan van de Ven, Larry McVoy, Linus Torvalds, linux-kernel,
Larry McVoy
In-Reply-To: <20021216174426.GB504@hopper.phunnypharm.org>
bcollins@debian.org said:
> Problem is that my changeset isn't even listed there. Not a very
> dependable way to get that info.
Isn't it? Why not? What changeset was it?
--
dwmw2
^ permalink raw reply
* Re: [PATCH] Hop Limit match/target for IPv6
From: Maciej Soltysiak @ 2002-12-17 9:01 UTC (permalink / raw)
To: netfilter-devel
In-Reply-To: <Pine.LNX.4.44.0212161859460.15942-200000@dns.toxicfilms.tv>
I forgot to attach a plain/text version, here it is:
diff -Nru netfilter.orig/patch-o-matic/base/HL.patch.ipv6 netfilter/patch-o-matic/base/HL.patch.ipv6
--- netfilter.orig/patch-o-matic/base/HL.patch.ipv6 1970-01-01 01:00:00.000000000 +0100
+++ netfilter/patch-o-matic/base/HL.patch.ipv6 2002-12-16 18:05:55.000000000 +0100
@@ -0,0 +1,135 @@
+diff -Nru linux-2.4.20/include/linux/netfilter_ipv6/ip6t_HL.h linux.new/include/linux/netfilter_ipv6/ip6t_HL.h
+--- linux-2.4.20/include/linux/netfilter_ipv6/ip6t_HL.h 1970-01-01 01:00:00.000000000 +0100
++++ linux.new/include/linux/netfilter_ipv6/ip6t_HL.h 2002-12-16 17:12:29.000000000 +0100
+@@ -0,0 +1,22 @@
++/* Hop Limit modification module for ip6tables
++ * Maciej Soltysiak <solt@dns.toxicfilms.tv> */
++ * Based on HW's TTL module */
++
++#ifndef _IP6T_HL_H
++#define _IP6T_HL_H
++
++enum {
++ IP6T_HL_SET = 0,
++ IP6T_HL_INC,
++ IP6T_HL_DEC
++};
++
++#define IP6T_HL_MAXMODE IP6T_HL_DEC
++
++struct ip6t_HL_info {
++ u_int8_t mode;
++ u_int8_t hop_limit;
++};
++
++
++#endif
+diff -Nru linux-2.4.20/net/ipv6/netfilter/ip6t_HL.c linux.new/net/ipv6/netfilter/ip6t_HL.c
+--- linux-2.4.20/net/ipv6/netfilter/ip6t_HL.c 1970-01-01 01:00:00.000000000 +0100
++++ linux.new/net/ipv6/netfilter/ip6t_HL.c 2002-12-16 17:08:23.000000000 +0100
+@@ -0,0 +1,105 @@
++/*
++ * Hop Limit modification target for ip6tables
++ * Maciej Soltysiak <solt@dns.toxicfilms.tv>
++ * Based on HW's TTL module
++ *
++ * This software is distributed under the terms of GNU GPL
++ */
++
++#include <linux/module.h>
++#include <linux/skbuff.h>
++#include <linux/ip.h>
++
++#include <linux/netfilter_ipv6/ip6_tables.h>
++#include <linux/netfilter_ipv6/ip6t_HL.h>
++
++MODULE_AUTHOR("Maciej Soltysiak <solt@dns.toxicfilms.tv>");
++MODULE_DESCRIPTION("IP tables Hop Limit modification module");
++MODULE_LICENSE("GPL");
++
++static unsigned int ip6t_hl_target(struct sk_buff **pskb, unsigned int hooknum,
++ const struct net_device *in, const struct net_device *out,
++ const void *targinfo, void *userinfo)
++{
++ struct ipv6hdr *ip6h = (*pskb)->nh.ipv6h;
++ const struct ip6t_HL_info *info = targinfo;
++ u_int16_t diffs[2];
++ int new_hl;
++
++ switch (info->mode) {
++ case IP6T_HL_SET:
++ new_hl = info->hop_limit;
++ break;
++ case IP6T_HL_INC:
++ new_hl = ip6h->hop_limit + info->hop_limit;
++ if (new_hl > 255)
++ new_hl = 255;
++ break;
++ case IP6T_HL_DEC:
++ new_hl = ip6h->hop_limit + info->hop_limit;
++ if (new_hl < 0)
++ new_hl = 0;
++ break;
++ default:
++ new_hl = ip6h->hop_limit;
++ break;
++ }
++
++ if (new_hl != ip6h->hop_limit) {
++ diffs[0] = htons(((unsigned)ip6h->hop_limit) << 8) ^ 0xFFFF;
++ ip6h->hop_limit = new_hl;
++ diffs[1] = htons(((unsigned)ip6h->hop_limit) << 8);
++ }
++
++ return IP6T_CONTINUE;
++}
++
++static int ip6t_hl_checkentry(const char *tablename,
++ const struct ip6t_entry *e,
++ void *targinfo,
++ unsigned int targinfosize,
++ unsigned int hook_mask)
++{
++ struct ip6t_HL_info *info = targinfo;
++
++ if (targinfosize != IP6T_ALIGN(sizeof(struct ip6t_HL_info))) {
++ printk(KERN_WARNING "HL: targinfosize %u != %Zu\n",
++ targinfosize,
++ IP6T_ALIGN(sizeof(struct ip6t_HL_info)));
++ return 0;
++ }
++
++ if (strcmp(tablename, "mangle")) {
++ printk(KERN_WARNING "HL: can only be called from \"mangle\" table, not \"%s\"\n", tablename);
++ return 0;
++ }
++
++ if (info->mode > IP6T_HL_MAXMODE) {
++ printk(KERN_WARNING "HL: invalid or unknown Mode %u\n",
++ info->mode);
++ return 0;
++ }
++
++ if ((info->mode != IP6T_HL_SET) && (info->hop_limit == 0)) {
++ printk(KERN_WARNING "HL: increment/decrement doesn't make sense with value 0\n");
++ return 0;
++ }
++
++ return 1;
++}
++
++static struct ip6t_target ip6t_HL = { { NULL, NULL }, "HL",
++ ip6t_hl_target, ip6t_hl_checkentry, NULL, THIS_MODULE };
++
++static int __init init(void)
++{
++ return ip6t_register_target(&ip6t_HL);
++}
++
++static void __exit fini(void)
++{
++ ip6t_unregister_target(&ip6t_HL);
++}
++
++module_init(init);
++module_exit(fini);
diff -Nru netfilter.orig/patch-o-matic/base/HL.patch.ipv6.config.in netfilter/patch-o-matic/base/HL.patch.ipv6.config.in
--- netfilter.orig/patch-o-matic/base/HL.patch.ipv6.config.in 1970-01-01 01:00:00.000000000 +0100
+++ netfilter/patch-o-matic/base/HL.patch.ipv6.config.in 2002-12-16 18:32:27.000000000 +0100
@@ -0,0 +1,4 @@
+ dep_tristate ' Packet filtering' CONFIG_IP6_NF_FILTER $CONFIG_IP6_NF_IPTABLES
+ if [ "$CONFIG_IP6_NF_FILTER" != "n" ]; then
+ dep_tristate ' HL target support' CONFIG_IP6_NF_TARGET_HL $CONFIG_IP6_NF_FILTER
+ fi
diff -Nru netfilter.orig/patch-o-matic/base/HL.patch.ipv6.configure.help netfilter/patch-o-matic/base/HL.patch.ipv6.configure.help
--- netfilter.orig/patch-o-matic/base/HL.patch.ipv6.configure.help 1970-01-01 01:00:00.000000000 +0100
+++ netfilter/patch-o-matic/base/HL.patch.ipv6.configure.help 2002-12-16 18:02:32.000000000 +0100
@@ -0,0 +1,8 @@
+CONFIG_IP6_NF_TARGET_LOG
+HL target support
+CONFIG_IP6_NF_TARGET_HL
+ This option adds a `HL' target, which allows you to modify the value of
+ IPv6 Hop Limit field.
+
+ If you want to compile it as a module, say M here and read
+ <file:Documentation/modules.txt>. If unsure, say `N'.
diff -Nru netfilter.orig/patch-o-matic/base/HL.patch.ipv6.help netfilter/patch-o-matic/base/HL.patch.ipv6.help
--- netfilter.orig/patch-o-matic/base/HL.patch.ipv6.help 1970-01-01 01:00:00.000000000 +0100
+++ netfilter/patch-o-matic/base/HL.patch.ipv6.help 2002-12-16 18:23:09.000000000 +0100
@@ -0,0 +1,10 @@
+Author: Maciej Soltysiak <solt@dns.toxicfilms.tv>
+Status: Works for me.
+
+This allows the user to set the IPv6 Hop Limit value on a packet or
+to increment or decrement it by a given value.
+
+Example:
+# ip6tables -t mangle -A OUTPUT -j HL --hl-inc 1
+# ip6tables -t mangle -A INPUT -j HL --hl-eq 64
+# ip6tables -t mangle -A OUTPUT -j HL --hl-dec 2
diff -Nru netfilter.orig/patch-o-matic/base/HL.patch.ipv6.makefile netfilter/patch-o-matic/base/HL.patch.ipv6.makefile
--- netfilter.orig/patch-o-matic/base/HL.patch.ipv6.makefile 1970-01-01 01:00:00.000000000 +0100
+++ netfilter/patch-o-matic/base/HL.patch.ipv6.makefile 2002-12-16 18:10:45.000000000 +0100
@@ -0,0 +1,2 @@
+obj-$(CONFIG_IP6_NF_TARGET_LOG) += ip6t_LOG.o
+obj-$(CONFIG_IP_NF_TARGET_HL) += ipt_HL.o
diff -Nru netfilter.orig/patch-o-matic/base/hl.patch.ipv6 netfilter/patch-o-matic/base/hl.patch.ipv6
--- netfilter.orig/patch-o-matic/base/hl.patch.ipv6 1970-01-01 01:00:00.000000000 +0100
+++ netfilter/patch-o-matic/base/hl.patch.ipv6 2002-12-16 18:05:19.000000000 +0100
@@ -0,0 +1,104 @@
+diff -Nru linux-2.4.20/include/linux/netfilter_ipv6/ip6t_hl.h linux.new/include/linux/netfilter_ipv6/ip6t_hl.h
+--- linux-2.4.20/include/linux/netfilter_ipv6/ip6t_hl.h 1970-01-01 01:00:00.000000000 +0100
++++ linux.new/include/linux/netfilter_ipv6/ip6t_hl.h 2002-12-16 17:11:56.000000000 +0100
+@@ -0,0 +1,22 @@
++/* ip6tables module for matching the Hop Limit value
++ * Maciej Soltysiak <solt@dns.toxicfilms.tv>
++ * Based on HW's ttl module */
++
++#ifndef _IP6T_HL_H
++#define _IP6T_HL_H
++
++enum {
++ IP6T_HL_EQ = 0, /* equals */
++ IP6T_HL_NE, /* not equals */
++ IP6T_HL_LT, /* less than */
++ IP6T_HL_GT, /* greater than */
++};
++
++
++struct ip6t_hl_info {
++ u_int8_t mode;
++ u_int8_t hop_limit;
++};
++
++
++#endif
+diff -Nru linux-2.4.20/net/ipv6/netfilter/ip6t_hl.c linux.new/net/ipv6/netfilter/ip6t_hl.c
+--- linux-2.4.20/net/ipv6/netfilter/ip6t_hl.c 1970-01-01 01:00:00.000000000 +0100
++++ linux.new/net/ipv6/netfilter/ip6t_hl.c 2002-12-16 17:09:53.000000000 +0100
+@@ -0,0 +1,74 @@
++/*
++ * Hop Limit matching module
++ * Maciej Soltysiak <solt@dns.toxicfilms.tv>
++ * Based on HW's ttl module
++ *
++ * This software is distributed under the terms GNU GPL
++ */
++
++#include <linux/module.h>
++#include <linux/skbuff.h>
++
++#include <linux/netfilter_ipv6/ip6t_hl.h>
++#include <linux/netfilter_ipv6/ip6_tables.h>
++
++MODULE_AUTHOR("Maciej Soltysiak <solt@dns.toxicfilms.tv>");
++MODULE_DESCRIPTION("IP tables Hop Limit matching module");
++MODULE_LICENSE("GPL");
++
++static int match(const struct sk_buff *skb, const struct net_device *in,
++ const struct net_device *out, const void *matchinfo,
++ int offset, const void *hdr, u_int16_t datalen,
++ int *hotdrop)
++{
++ const struct ip6t_hl_info *info = matchinfo;
++ const struct ipv6hdr *ip6h = skb->nh.ipv6h;
++
++ switch (info->mode) {
++ case IP6T_HL_EQ:
++ return (ip6h->hop_limit == info->hop_limit);
++ break;
++ case IP6T_HL_NE:
++ return (!(ip6h->hop_limit == info->hop_limit));
++ break;
++ case IP6T_HL_LT:
++ return (ip6h->hop_limit < info->hop_limit);
++ break;
++ case IP6T_HL_GT:
++ return (ip6h->hop_limit > info->hop_limit);
++ break;
++ default:
++ printk(KERN_WARNING "ip6t_hl: unknown mode %d\n",
++ info->mode);
++ return 0;
++ }
++
++ return 0;
++}
++
++static int checkentry(const char *tablename, const struct ip6t_ip *ip,
++ void *matchinfo, unsigned int matchsize,
++ unsigned int hook_mask)
++{
++ if (matchsize != IP6T_ALIGN(sizeof(struct ip6t_hl_info)))
++ return 0;
++
++ return 1;
++}
++
++static struct ip6t_match hl_match = { { NULL, NULL }, "hl", &match,
++ &checkentry, NULL, THIS_MODULE };
++
++static int __init init(void)
++{
++ return ip6t_register_match(&hl_match);
++}
++
++static void __exit fini(void)
++{
++ ip6t_unregister_match(&hl_match);
++
++}
++
++module_init(init);
++module_exit(fini);
diff -Nru netfilter.orig/patch-o-matic/base/hl.patch.ipv6.config.in netfilter/patch-o-matic/base/hl.patch.ipv6.config.in
--- netfilter.orig/patch-o-matic/base/hl.patch.ipv6.config.in 1970-01-01 01:00:00.000000000 +0100
+++ netfilter/patch-o-matic/base/hl.patch.ipv6.config.in 2002-12-16 18:08:55.000000000 +0100
@@ -0,0 +1,2 @@
+ dep_tristate ' MAC address match support' CONFIG_IP6_NF_MATCH_MAC $CONFIG_IP6_NF_IPTABLES
+ dep_tristate ' HL match support' CONFIG_IP6_NF_MATCH_HL $CONFIG_IP6_NF_IPTABLES
diff -Nru netfilter.orig/patch-o-matic/base/hl.patch.ipv6.configure.help netfilter/patch-o-matic/base/hl.patch.ipv6.configure.help
--- netfilter.orig/patch-o-matic/base/hl.patch.ipv6.configure.help 1970-01-01 01:00:00.000000000 +0100
+++ netfilter/patch-o-matic/base/hl.patch.ipv6.configure.help 2002-12-16 18:04:01.000000000 +0100
@@ -0,0 +1,8 @@
+CONFIG_IP6_NF_TARGET_LOG
+HL match support
+CONFIG_IP6_NF_MATCH_HL
+ This option adds a `hl' match, which allows you match the value of
+ the IPv6 Hop Limit field.
+
+ If you want to compile it as a module, say M here and read
+ <file:Documentation/modules.txt>. If unsure, say `N'.
diff -Nru netfilter.orig/patch-o-matic/base/hl.patch.ipv6.help netfilter/patch-o-matic/base/hl.patch.ipv6.help
--- netfilter.orig/patch-o-matic/base/hl.patch.ipv6.help 1970-01-01 01:00:00.000000000 +0100
+++ netfilter/patch-o-matic/base/hl.patch.ipv6.help 2002-12-16 18:22:25.000000000 +0100
@@ -0,0 +1,9 @@
+Author: Maciej Soltysiak <solt@dns.toxicfilms.tv>
+Status: Works for me.
+
+This allows the user to match the IPv6 Hop Limit value on a packet.
+
+Examples:
+# ip6tables -A INPUT -m hl --hl-eq 63 -j LOG --log-prefix "Blah: "
+# ip6tables -A FORWARD -m hl --hl-gt 64 -j DROP
+# ip6tables -A OUTPUT -m hl --hl-lt 64 -j ACCEPT
diff -Nru netfilter.orig/patch-o-matic/base/hl.patch.ipv6.makefile netfilter/patch-o-matic/base/hl.patch.ipv6.makefile
--- netfilter.orig/patch-o-matic/base/hl.patch.ipv6.makefile 1970-01-01 01:00:00.000000000 +0100
+++ netfilter/patch-o-matic/base/hl.patch.ipv6.makefile 2002-12-16 18:11:03.000000000 +0100
@@ -0,0 +1,2 @@
+obj-$(CONFIG_IP6_NF_TARGET_LOG) += ip6t_LOG.o
+obj-$(CONFIG_IP_NF_MATCH_HL) += ipt_hl.o
diff -Nru netfilter.orig/userspace/extensions/Makefile netfilter/userspace/extensions/Makefile
--- netfilter.orig/userspace/extensions/Makefile 2002-12-09 10:31:23.000000000 +0100
+++ netfilter/userspace/extensions/Makefile 2002-12-16 16:57:44.000000000 +0100
@@ -1,7 +1,7 @@
#! /usr/bin/make
PF_EXT_SLIB:=ah conntrack dscp ecn esp helper icmp length limit mac mark multiport owner pkttype standard state tcp tcpmss tos ttl udp unclean DNAT DSCP ECN LOG MARK MASQUERADE MIRROR REDIRECT REJECT SAME SNAT TARPIT TCPMSS TOS ULOG
-PF6_EXT_SLIB:=eui64 icmpv6 length limit mac mark multiport owner standard tcp udp LOG MARK
+PF6_EXT_SLIB:=eui64 icmpv6 length limit mac mark multiport owner standard tcp udp LOG MARK hl HL
# The following may not be present, but compile them anyway.
PF_EXT_SLIB+=TTL iplimit
diff -Nru netfilter.orig/userspace/extensions/libip6t_HL.c netfilter/userspace/extensions/libip6t_HL.c
--- netfilter.orig/userspace/extensions/libip6t_HL.c 1970-01-01 01:00:00.000000000 +0100
+++ netfilter/userspace/extensions/libip6t_HL.c 2002-12-16 17:05:57.000000000 +0100
@@ -0,0 +1,164 @@
+/*
+ * IPv6 Hop Limit Target module
+ * Maciej Soltysiak <solt@dns.toxicfilms.tv>
+ * Based on HW's ttl target
+ * This program is distributed under the terms of GNU GPL
+ */
+
+#include <stdio.h>
+#include <string.h>
+#include <stdlib.h>
+#include <getopt.h>
+#include <ip6tables.h>
+
+#include <linux/netfilter_ipv6/ip6_tables.h>
+#include <linux/netfilter_ipv6/ip6t_HL.h>
+
+#define IP6T_HL_USED 1
+
+static void init(struct ip6t_entry_target *t, unsigned int *nfcache)
+{
+}
+
+static void help(void)
+{
+ printf(
+"HL target v%s options\n"
+" --hl-set value Set HL to <value>\n"
+" --hl-dec value Decrement HL by <value>\n"
+" --hl-inc value Increment HL by <value>\n"
+, IPTABLES_VERSION);
+}
+
+static int parse(int c, char **argv, int invert, unsigned int *flags,
+ const struct ip6t_entry *entry,
+ struct ip6t_entry_target **target)
+{
+ struct ip6t_HL_info *info = (struct ip6t_HL_info *) (*target)->data;
+ u_int8_t value;
+
+ if (*flags & IP6T_HL_USED) {
+ exit_error(PARAMETER_PROBLEM,
+ "Can't specify HL option twice");
+ }
+
+ if (!optarg)
+ exit_error(PARAMETER_PROBLEM,
+ "HL: You must specify a value");
+
+ if (check_inverse(optarg, &invert, NULL, 0))
+ exit_error(PARAMETER_PROBLEM,
+ "HL: unexpected `!'");
+
+ value = atoi(optarg);
+
+ switch (c) {
+
+ case '1':
+ info->mode = IP6T_HL_SET;
+ break;
+
+ case '2':
+ if (value == 0) {
+ exit_error(PARAMETER_PROBLEM,
+ "HL: decreasing by 0?");
+ }
+
+ info->mode = IP6T_HL_DEC;
+ break;
+
+ case '3':
+ if (value == 0) {
+ exit_error(PARAMETER_PROBLEM,
+ "HL: increasing by 0?");
+ }
+
+ info->mode = IP6T_HL_INC;
+ break;
+
+ default:
+ return 0;
+
+ }
+
+ info->hop_limit = value;
+ *flags |= IP6T_HL_USED;
+
+ return 1;
+}
+
+static void final_check(unsigned int flags)
+{
+ if (!(flags & IP6T_HL_USED))
+ exit_error(PARAMETER_PROBLEM,
+ "HL: You must specify an action");
+}
+
+static void save(const struct ip6t_ip6 *ip,
+ const struct ip6t_entry_target *target)
+{
+ const struct ip6t_HL_info *info =
+ (struct ip6t_HL_info *) target->data;
+
+ switch (info->mode) {
+ case IP6T_HL_SET:
+ printf("--hl-set ");
+ break;
+ case IP6T_HL_DEC:
+ printf("--hl-dec ");
+ break;
+
+ case IP6T_HL_INC:
+ printf("--hl-inc ");
+ break;
+ }
+ printf("%u ", info->hop_limit);
+}
+
+static void print(const struct ip6t_ip6 *ip,
+ const struct ip6t_entry_target *target, int numeric)
+{
+ const struct ip6t_HL_info *info =
+ (struct ip6t_HL_info *) target->data;
+
+ printf("HL ");
+ switch (info->mode) {
+ case IP6T_HL_SET:
+ printf("set to ");
+ break;
+ case IP6T_HL_DEC:
+ printf("decrement by ");
+ break;
+ case IP6T_HL_INC:
+ printf("increment by ");
+ break;
+ }
+ printf("%u ", info->hop_limit);
+}
+
+static struct option opts[] = {
+ { "hl-set", 1, 0, '1' },
+ { "hl-dec", 1, 0, '2' },
+ { "hl-inc", 1, 0, '3' },
+ { 0 }
+};
+
+static
+struct ip6tables_target HL = { NULL,
+ "HL",
+ IPTABLES_VERSION,
+ IP6T_ALIGN(sizeof(struct ip6t_HL_info)),
+ IP6T_ALIGN(sizeof(struct ip6t_HL_info)),
+ &help,
+ &init,
+ &parse,
+ &final_check,
+ &print,
+ &save,
+ opts
+};
+
+void _init(void)
+{
+ register_target6(&HL);
+}
diff -Nru netfilter.orig/userspace/extensions/libip6t_hl.c netfilter/userspace/extensions/libip6t_hl.c
--- netfilter.orig/userspace/extensions/libip6t_hl.c 1970-01-01 01:00:00.000000000 +0100
+++ netfilter/userspace/extensions/libip6t_hl.c 2002-12-16 17:05:14.000000000 +0100
@@ -0,0 +1,177 @@
+/*
+ * IPv6 Hop Limit matching module
+ * Maciej Soltysiak <solt@dns.toxicfilms.tv>
+ * Based on HW's ttl match
+ * This program is released under the terms of GNU GPL
+ */
+
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+#include <getopt.h>
+#include <ip6tables.h>
+
+#include <linux/netfilter_ipv6/ip6_tables.h>
+#include <linux/netfilter_ipv6/ip6t_hl.h>
+
+static void help(void)
+{
+ printf(
+"HL match v%s options:\n"
+" --hl-eq value Match hop limit value\n"
+" --hl-lt value Match HL < value\n"
+" --hl-gt value Match HL > value\n"
+, IPTABLES_VERSION);
+}
+
+static void init(struct ip6t_entry_match *m, unsigned int *nfcache)
+{
+ /* caching not yet implemented */
+ *nfcache |= NFC_UNKNOWN;
+}
+
+static int parse(int c, char **argv, int invert, unsigned int *flags,
+ const struct ip6t_entry *entry, unsigned int *nfcache,
+ struct ip6t_entry_match **match)
+{
+ struct ip6t_hl_info *info = (struct ip6t_hl_info *) (*match)->data;
+ u_int8_t value;
+
+ check_inverse(optarg, &invert, &optind, 0);
+ value = atoi(argv[optind-1]);
+
+ if (*flags)
+ exit_error(PARAMETER_PROBLEM,
+ "Can't specify HL option twice");
+
+ if (!optarg)
+ exit_error(PARAMETER_PROBLEM,
+ "hl: You must specify a value");
+ switch (c) {
+ case '2':
+ if (invert)
+ info->mode = IP6T_HL_NE;
+ else
+ info->mode = IP6T_HL_EQ;
+
+ /* is 0 allowed? */
+ info->hop_limit = value;
+ *flags = 1;
+
+ break;
+ case '3':
+ if (invert)
+ exit_error(PARAMETER_PROBLEM,
+ "hl: unexpected `!'");
+
+ info->mode = IP6T_HL_LT;
+ info->hop_limit = value;
+ *flags = 1;
+
+ break;
+ case '4':
+ if (invert)
+ exit_error(PARAMETER_PROBLEM,
+ "hl: unexpected `!'");
+
+ info->mode = IP6T_HL_GT;
+ info->hop_limit = value;
+ *flags = 1;
+
+ break;
+ default:
+ return 0;
+
+ }
+
+ return 1;
+}
+
+static void final_check(unsigned int flags)
+{
+ if (!flags)
+ exit_error(PARAMETER_PROBLEM,
+ "HL match: You must specify one of "
+ "`--hl-eq', `--hl-lt', `--hl-gt");
+}
+
+static void print(const struct ip6t_ip6 *ip,
+ const struct ip6t_entry_match *match,
+ int numeric)
+{
+ const struct ip6t_hl_info *info =
+ (struct ip6t_hl_info *) match->data;
+
+ printf("HL match ");
+ switch (info->mode) {
+ case IP6T_HL_EQ:
+ printf("HL == ");
+ break;
+ case IP6T_HL_NE:
+ printf("HL != ");
+ break;
+ case IP6T_HL_LT:
+ printf("HL < ");
+ break;
+ case IP6T_HL_GT:
+ printf("HL > ");
+ break;
+ }
+ printf("%u ", info->hop_limit);
+}
+
+static void save(const struct ip6t_ip6 *ip,
+ const struct ip6t_entry_match *match)
+{
+ const struct ip6t_hl_info *info =
+ (struct ip6t_hl_info *) match->data;
+
+ switch (info->mode) {
+ case IP6T_HL_EQ:
+ printf("--hl-eq ");
+ break;
+ case IP6T_HL_NE:
+ printf("! --hl-eq ");
+ break;
+ case IP6T_HL_LT:
+ printf("--hl-lt ");
+ break;
+ case IP6T_HL_GT:
+ printf("--hl-gt ");
+ break;
+ default:
+ /* error */
+ break;
+ }
+ printf("%u ", info->hop_limit);
+}
+
+static struct option opts[] = {
+ { "hl", 1, 0, '2' },
+ { "hl-eq", 1, 0, '2'},
+ { "hl-lt", 1, 0, '3'},
+ { "hl-gt", 1, 0, '4'},
+ { 0 }
+};
+
+static
+struct ip6tables_match hl = {
+ NULL,
+ "hl",
+ IPTABLES_VERSION,
+ IP6T_ALIGN(sizeof(struct ip6t_hl_info)),
+ IP6T_ALIGN(sizeof(struct ip6t_hl_info)),
+ &help,
+ &init,
+ &parse,
+ &final_check,
+ &print,
+ &save,
+ opts
+};
+
+
+void _init(void)
+{
+ register_match6(&hl);
+}
^ permalink raw reply
* Re: My cpu fuzzy problem was due to XMMS
From: Denis Vlasenko @ 2002-12-17 13:54 UTC (permalink / raw)
To: Xavier LaRue, linux-kernel
In-Reply-To: <20021217011600.08f8cd81.paxl@videotron.ca>
On 17 December 2002 04:16, Xavier LaRue wrote:
> :).. I just found it out :)
>
> But now my real problem.. That probably slow down considerably my
> box, How to make my L2 cache reconized
> my dmesg is hosted here http://paxl.no-ip.org/~paxl/dmesg.txt
It does *NOT* slow down your box if kernel cannot parse
CPIUD cache size info. Cache does not need any help from kernel to function.
It is typically enabled by BIOS at boot, that's all.
If you can prove otherwise (that is, your cache is disabled),
that is a problem. Problem in BIOS.
Cache size *reporting* is a minor issue. You can track it yourself.
You have the code, right?
--
vda
^ permalink raw reply
* [U-Boot-Users] booting linux from u-boot - help!
From: Murray Jensen @ 2002-12-17 9:05 UTC (permalink / raw)
To: u-boot
In-Reply-To: <sdff7591.074@au.thalesgroup.com>
On Tue, 17 Dec 2002 19:04:41 +1100, My-Hong Vuong <My-Hong.Vuong@au.thalesgroup.com> writes:
>with the cache, i've disabled MSR_DR in head_8xx.S
You mustn't do this - virtual memory will not work if you do this.
>which then seems to
>get to start_here fine.
This is giving you false hope - you must leave the virtual memory on.
>but inserting the same code just before
>early_init doesn't seem to work...
One problem that you need to look out for is that you only have 0x100 bytes
available to you at that point. This is executing the reset exception handler
at 0x...100 and the next exception handler must start at 0x...200. Don't insert
too much code (you should get an error from the assembler - saying that you
are trying to set the location backwards or something like that).
>the assembly I'm using is :
>lis r25, 0xaaaa
>ori r25, r25, 0xaaaa
>lis r26, 0x8100
>ori r26,r26,0x0000
>stw r25, 0(r26)
>
>where r25 is the pattern I want to write into address 0x81000000. I've
>used r25 and r26 because I can't see them being used anywhere in the
>code...
r25 and r26 (and others) are used to save the arguments passed to kernel from
the boot loader (in r3, r4, ..., r7) - it's like the first few instructions
ever executed by Linux - you mustn't clobber these registers.
Besides this, if you leave virtual memory on, this will not do what you
think it will - you must first set up a temporary translation in the TLB before
you can access that physical location, as is done for the Internal Memory
Mapped Registers (IMMR) area.
Of course, the appropriate BRx/ORx for the LEDs must have been set up by the
boot loader so that the physical address 0x81000000 really does access the
LED hardware (I assume this is the case - since you say this code works
elsewhere).
>I'm not sure how do do it otherwise (i.e. restoring the original
>register values)
Use some other registers (if you're careful) - e.g. r3, r4, r5 - these will be
restored later when required (see call to identify_machine - or some name like
that).
>any other ideas would be muchly appreciated,
I just got my BDI2000 - it's great. Other than that - pull out all code you
have inserted and go back to the original Linux code - after carefully
examining all the config options. If your hardware is correct and your
linux config matches it properly, it should "just work" :-) Good luck.
Cheers!
Murray...
--
Murray Jensen, CSIRO Manufacturing & Infra. Tech. Phone: +61 3 9662 7763
Locked Bag No. 9, Preston, Vic, 3072, Australia. Fax: +61 3 9662 7853
Internet: Murray.Jensen at csiro.au
Hymod project: http://www.msa.cmst.csiro.au/projects/Hymod/
To the extent permitted by law, CSIRO does not represent, warrant and/or
guarantee that the integrity of this communication has been maintained or
that the communication is free of errors, virus, interception or interference.
The information contained in this e-mail may be confidential or privileged.
Any unauthorised use or disclosure is prohibited. If you have received this
e-mail in error, please delete it immediately and notify Murray Jensen on
+61 3 9662 7763. Thank you.
^ permalink raw reply
* AW: Possible problem in asm/bitops.h
From: Georg Klug @ 2002-12-17 9:10 UTC (permalink / raw)
To: Tom Rini; +Cc: linuxppc-embedded
In-Reply-To: <20021212152851.GE19456@opus.bloom.county>
Hi Tom,
> On Wed, Dec 11, 2002 at 04:31:14PM +0100, Georg Klug wrote:
>
> > Q: Is the ffz() function desgined to work in a user space
> application, too? If
> > yes, the file asm-ppc/bitops.h would need a change.
> > Q: Does it make any sense to define one single macro (PPC405_ERR77()) in
> > different
> > ways in different include files?
>
> The problem here is that userland programs are _not_ allowed to use
> kernel headers, iirc, even programs which are tied to the kernel in some
> way. They _must_ make a local copy of the include file which they
> actually need.
Oops, I thought, that the directories /usr/include/linux as well as
/usr/include/asm should come directly from the kernel (either as a copy
or symbolically linked). In that case those include files should always
be prepared to be included in a userland application. Am I right with this?
I also thought, that the asm-ppc/bitops.h should provide the same
functionality as its pendant in asm-i386/ which lets userland applications
use some static inline functions like set_bit() clear_bit() and change_bit().
I actually don't know whether those functions are needed outside the kernel,
so I cannot tell whether it is correct or not. But IMO it should be done
the same way on all plattforms. Would you agree?
> I suspect the actual problem is that iproute2 only needs
> a very small amount of what is in include/linux/inetdev.h
That might be true. But would the solution be to copy the linux/inetdev.h
to a local directory and change that file until it doesn't need the file
asm/bitops.h anymore?
Sorry for asking a little bit pedantic, but I want to set-up a complete
environment for building a kernel as well as all the needed userland
applications for our custom ppc_405 (walnut based) boards.
Thanks in advance for answering my questions,
Georg Klug
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* Who's doing the SIBO port?
From: Richard Wallman @ 2002-12-17 9:17 UTC (permalink / raw)
To: Linux 8086
After successfully wiping the Internal ramdisk on my 3c (DOH! Where's
that backup...) I thought it might be easier to ask the maintainer.
So...
Who's the current maintainer of the SIBO port, and is there any work
being done on it? I think at very least putting a bloody big warning in
the FAQ along the lines of: "If you don't know exactly what you're
doing, you're likely to wipe everything, so backup NOW!" rather than
the kinda weak "It's not worth installing" message in /INSTALLATION
--
Richard Wallman
http://www.murkygoth.uklinux.net/elks
^ permalink raw reply
* Re: Domain transition
From: Russell Coker @ 2002-12-17 9:19 UTC (permalink / raw)
To: Brian May; +Cc: SELinux
In-Reply-To: <20021216231110.GF15678@snoopy.apana.org.au>
On Tue, 17 Dec 2002 00:11, Brian May wrote:
> On Mon, Dec 16, 2002 at 11:07:52PM +0100, Russell Coker wrote:
> > (*) /bin/login has had a good history in terms of security for almost 10
> > years now, unlike sshd. Also /bin/login can't be accessed anywhere
> > nearly as
>
> Assuming you are not using telnet...
Telnet causes login to be run as remote_login_t which is distinguished from
the main local_login_t domain for this reason.
Actually we should probably have ifdef(`rlogin.te',` around the definition of
remote_login_t in login.te, and have a similar ifdef(`login.te', ` in
rlogin.te.
> (and yes, you can use Kerberos Telnet or SSL-Telnet too, so telnet
> doesn't always have to mean insecure; with these protocols you need to
> be authenticated though before login is run).
SSL-Telnet would be OK apart from it's history of security holes.
Kerberos still isn't safe, proxying the telnet protocol and hijacking it is
not overly difficult...
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
^ permalink raw reply
* RE: writing new BBRAM driver
From: Tobias Otto-Adamczak @ 2002-12-17 9:49 UTC (permalink / raw)
To: linux-mtd; +Cc: Alex Pavloff
In-Reply-To: <D3AF5F134D627243993F2F2FC32EE4D229C4B0@mailman.eason.com>
Alex Pavloff, 2002-12-16, 14:33h:
> Does the minix fs have a small overhead like FAT12? Could I use FAT12 if I
> was willing to stick with 8.3? (Which wouldn't be a bad idea anyway, for
> other reasons in my project).
Of course you can use FAT12 if that suits your needs.
> Alright, one more question: What should the erasesize be for BBRAM?
I set it to 0 for my project. I read in other messages here that
blocksize=erasesize but for erasesize=0 this is definitely not the case
:-) I did no modifications to the slram code and the sizes are:
erasesize=0 byte
sectorsize=512 byte
blocksize=1024 byte
Be careful to use fresh mtd code when you try this (in the latest
slram.c, it is predefined with 0 anyway). I run into problems with old
releases.
Tobias
^ permalink raw reply
* Re: [PATCH] updated scheduler tunables
From: Marc-Christian Petersen @ 2002-12-17 9:33 UTC (permalink / raw)
To: Hanna Linder, Robert Love, linux-kernel; +Cc: anton, hannal
In-Reply-To: <69970000.1040093092@w-hlinder>
On Tuesday 17 December 2002 03:44, Hanna Linder wrote:
Hi Robert,
> One vote for including this in 2.5. (as if this were a democracy... ;)
another vote.
ciao, Marc
^ permalink raw reply
* Re: [PATCH] move LOG_BUF_SIZE to header file
From: Christoph Hellwig @ 2002-12-17 9:41 UTC (permalink / raw)
To: Randy.Dunlap; +Cc: Andrew Morton, linux-kernel
In-Reply-To: <Pine.LNX.4.33L2.0212121517300.19827-100000@dragon.pdx.osdl.net>
On Mon, Dec 16, 2002 at 10:11:42PM -0800, Randy.Dunlap wrote:
> --- ./arch/i386/Kconfig%LOGBUF Sun Dec 15 18:07:47 2002
> +++ ./arch/i386/Kconfig Sun Dec 15 20:45:09 2002
> @@ -1573,6 +1573,43 @@
> If you don't debug the kernel, you can say N, but we may not be able
> to solve problems without frame pointers.
>
> +choice
> + prompt "Kernel log buffer size"
> + default LOG_BUF_128KB if ARCH_S390
> + default LOG_BUF_64KB if X86_NUMAQ || IA64
> + default LOG_BUF_32KB if SMP
> + default LOG_BUF_16KB
yuck. Why don't you just add and integer LOG_BUG_SHIFT symbol that can
be freely choosen?
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: Andre Hedrick @ 2002-12-17 9:45 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Dave Jones, Ingo Molnar, linux-kernel, hpa
In-Reply-To: <Pine.LNX.4.44.0212162140500.1644-100000@home.transmeta.com>
Linus,
Are you serious about moving of the banging we currently do on 0x80?
If so, I have a P4 development board with leds to monitor all the lower io
ports and can decode for you.
On Mon, 16 Dec 2002, Linus Torvalds wrote:
>
> On Mon, 16 Dec 2002, Linus Torvalds wrote:
> >
> > (Modulo the missing syscall page I already mentioned and potential bugs
> > in the code itself, of course ;)
>
> Ok, I did the vsyscall page too, and tried to make it do the right thing
> (but I didn't bother to test it on a non-SEP machine).
>
> I'm pushing the changes out right now, but basically it boils down to the
> fact that with these changes, user space can instead of doing an
>
> int $0x80
>
> instruction for a system call just do a
>
> call 0xfffff000
>
> instead. The vsyscall page will be set up to use sysenter if the CPU
> supports it, and if it doesn't, it will just do the old "int $0x80"
> instead (and it could use the AMD syscall instruction if it wants to).
> User mode shouldn't know or care, the calling convention is the same as it
> ever was.
>
> On my P4 machine, a "getppid()" is 641 cycles with sysenter/sysexit, and
> something like 1761 cycles with the old "int 0x80/iret" approach. That's a
> noticeable improvement, but I have to say that I'm a bit disappointed in
> the P4 still, it shouldn't be even that much.
>
> As a comparison, an Athlon will do a full int/iret faster than a P4 does a
> sysenter/sysexit. Pathetic. But it's better than it used to be.
>
> Whatever. The code is extremely simple, and while I'm sure there are
> things I've missed I'd love to hear if this works for anybody else. I'm
> appending the (extremely stupid) test-program I used to test it.
>
> The way I did this, things like system call restarting etc _should_ all
> work fine even with "sysenter", simply by virtue of both sysenter and "int
> 0x80" being two-byte opcodes. But it might be interesting to verify that a
> recompiled glibc (or even just a preload) really works with this on a
> "whole system" testbed rather than just testing one system call (and not
> even caring about the return value) a million times.
>
> The good news is that the kernel part really looks pretty clean.
>
> Linus
>
> ---
> #include <time.h>
> #include <sys/time.h>
> #include <asm/unistd.h>
> #include <sys/stat.h>
> #include <stdio.h>
>
> #define rdtsc() ({ unsigned long a,d; asm volatile("rdtsc":"=a" (a), "=d" (d)); a; })
>
> int main()
> {
> int i, ret;
> unsigned long start, end;
>
> start = rdtsc();
> for (i = 0; i < 1000000; i++) {
> asm volatile("call 0xfffff000"
> :"=a" (ret)
> :"0" (__NR_getppid));
> }
> end = rdtsc();
> printf("%f cycles\n", (end - start) / 1000000.0);
>
> start = rdtsc();
> for (i = 0; i < 1000000; i++) {
> asm volatile("int $0x80"
> :"=a" (ret)
> :"0" (__NR_getppid));
> }
> end = rdtsc();
> printf("%f cycles\n", (end - start) / 1000000.0);
> }
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Andre Hedrick
LAD Storage Consulting Group
^ permalink raw reply
* RE: Redhat 7.3 and IPTables 1.2.7a (was ICMP Destination Unreacha ble)
From: Rob Sterenborg @ 2002-12-17 9:41 UTC (permalink / raw)
To: 'netfilter@lists.netfilter.org'
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
> Is it possible to use IPTables version 1.2.7a with Redhat
> 7.3? RH 7.3 comes with a different version by default and I
> wanted to upgrade to 1.2.7a. Is it possible?
Yes, you can compile a brand new version for your own system.
It's not that hard...
> Also, do you know if any RPMs exist for IPTables version
> 1.2.7a and RH 7.3?
A Google search on "iptables 1.2.7a redhat rpm" returns results like
http://www.haoli.org/rpm/redhat-7.x/RPMS/i386/.
But I still think you'd better compile your own.
Rob
[-- Attachment #2: Type: text/html, Size: 1245 bytes --]
^ permalink raw reply
* Re: USB PCI
From: Korosi Akos @ 2002-12-17 9:41 UTC (permalink / raw)
To: dashielljt; +Cc: Newbie
In-Reply-To: <Pine.LNX.4.50.0212162100570.217-100000@athame.gmpexpress.net>
Hi!
dashielljt <dashielljt@gmpexpress.net> wrote:
>Here's your problem. You must have a bios on that computer that has a
> date on or after July 1, 1989.
...
> Jude <dashielljt(at)gmpexpress-dot-net>
Thanks! And if the bios is newer, than this date
(I could check this only in weekend), then
there are no other problems?
Akos
________________________________________________
http://mailbox.hu - Már SMS értesítéssel is!
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply
* Unexpected IO-APIC (Athlon MP 2100+ / VIA KT400)
From: Colin Bayer @ 2002-12-17 9:45 UTC (permalink / raw)
To: linux-smp
[-- Attachment #1.1: Type: text/plain, Size: 141 bytes --]
Kernel version: 2.4.20-ac2
Hardware:
1 Athlon MP 2100+
Albatron KX400-8X (KT400)
/var/log/dmesg is attached.
-- Colin <vogon@icculus.org>
[-- Attachment #1.2: dmesg --]
[-- Type: text/plain, Size: 10987 bytes --]
Linux version 2.4.20-ac2 (root@fortytwo.homeip.net) (gcc version 2.95.4 20011002 (Debian prerelease)) #4 Sat Dec 14 09:54:20 PST 2002
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000005fff0000 (usable)
BIOS-e820: 000000005fff0000 - 000000005fff3000 (ACPI NVS)
BIOS-e820: 000000005fff3000 - 0000000060000000 (ACPI data)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
639MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000f5350
hm, page 000f5000 reserved twice.
hm, page 000f6000 reserved twice.
hm, page 000f1000 reserved twice.
hm, page 000f2000 reserved twice.
On node 0 totalpages: 393200
zone(0): 4096 pages.
zone(1): 225280 pages.
zone(2): 163824 pages.
Intel MultiProcessor Specification v1.4
Virtual Wire compatibility mode.
OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
Processor #0 Pentium(tm) Pro APIC version 17
I/O APIC #2 Version 17 at 0xFEC00000.
Enabling APIC mode: Flat. Using 1 I/O APICs
Processors: 1
Kernel command line: BOOT_IMAGE=2-4-20-ac2 ro root=342 hdc=ide-scsi
ide_setup: hdc=ide-scsi
Initializing CPU#0
Detected 1729.348 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 3447.19 BogoMIPS
Memory: 1544588k/1572800k available (1186k kernel code, 23604k reserved, 506k data, 80k init, 655296k highmem)
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode cache hash table entries: 131072 (order: 8, 1048576 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
ramfs: mounted with options: <defaults>
ramfs: max_pages=193601 max_file_pages=0 max_inodes=0 max_dentries=193601
Buffer cache hash table entries: 131072 (order: 7, 524288 bytes)
Page-cache hash table entries: 524288 (order: 9, 2097152 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After generic, caps: 0383fbff c1cbfbff 00000000 00000000
CPU: Common caps: 0383fbff c1cbfbff 00000000 00000000
CPU: AMD Athlon(tm) XP 2100+ stepping 02
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
ENABLING IO-APIC IRQs
Setting 2 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 2 ... ok.
init IO_APIC IRQs
IO-APIC (apicid-pin) 2-0, 2-10, 2-11, 2-12, 2-18, 2-20, 2-23 not connected.
..TIMER: vector=0x31 pin1=2 pin2=0
number of MP IRQ sources: 22.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................
IO APIC #2......
.... register #00: 02000000
....... : physical APIC id: 02
.... register #01: 00178003
....... : max redirection entries: 0017
....... : PRQ implemented: 1
....... : IO APIC version: 0003
An unexpected IO-APIC was found. If this kernel release is less than
three months old please report this to linux-smp@vger.kernel.org
.... IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 000 00 1 0 0 0 0 0 0 00
01 001 01 0 0 0 0 0 1 1 39
02 001 01 0 0 0 0 0 1 1 31
03 001 01 0 0 0 0 0 1 1 41
04 001 01 0 0 0 0 0 1 1 49
05 001 01 0 0 0 0 0 1 1 51
06 001 01 0 0 0 0 0 1 1 59
07 001 01 0 0 0 0 0 1 1 61
08 001 01 0 0 0 0 0 1 1 69
09 001 01 0 0 0 0 0 1 1 71
0a 000 00 1 0 0 0 0 0 0 00
0b 000 00 1 0 0 0 0 0 0 00
0c 000 00 1 0 0 0 0 0 0 00
0d 001 01 0 0 0 0 0 1 1 79
0e 001 01 0 0 0 0 0 1 1 81
0f 001 01 0 0 0 0 0 1 1 89
10 001 01 1 1 0 1 0 1 1 91
11 001 01 1 1 0 1 0 1 1 99
12 000 00 1 0 0 0 0 0 0 00
13 001 01 1 1 0 1 0 1 1 A1
14 000 00 1 0 0 0 0 0 0 00
15 001 01 1 1 0 1 0 1 1 A9
16 001 01 1 1 0 1 0 1 1 B1
17 000 00 1 0 0 0 0 0 0 00
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:5
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
IRQ16 -> 0:16
IRQ17 -> 0:17
IRQ19 -> 0:19
IRQ21 -> 0:21
IRQ22 -> 0:22
.................................... done.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1729.2371 MHz.
..... host bus clock speed is 266.0364 MHz.
cpu: 0, clocks: 2660364, slice: 1330182
CPU0<T0:2660352,T1:1330160,D:10,S:1330182,C:2660364>
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfb3d0, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router VIA [1106/3177] at 00:11.0
PCI->APIC IRQ transform: (B0,I12,P0) -> 16
PCI->APIC IRQ transform: (B0,I13,P0) -> 17
PCI->APIC IRQ transform: (B0,I16,P0) -> 21
PCI->APIC IRQ transform: (B0,I16,P1) -> 21
PCI->APIC IRQ transform: (B0,I16,P2) -> 21
PCI->APIC IRQ transform: (B0,I16,P3) -> 19
PCI->APIC IRQ transform: (B0,I17,P0) -> 22
PCI->APIC IRQ transform: (B0,I17,P2) -> 22
PCI->APIC IRQ transform: (B1,I0,P0) -> 16
PCI: Via IRQ fixup for 00:10.0, from 11 to 5
PCI: Via IRQ fixup for 00:10.1, from 10 to 5
PCI: Via IRQ fixup for 00:10.2, from 12 to 5
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
allocated 32 pages and 32 bhs reserved for the highmem bounces
Journalled Block Device driver loaded
ACPI: Core Subsystem version [20011018]
ACPI: Subsystem enabled
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Redundant entry in serial pci_table. Please send the output of
lspci -vv, this message (12b9,1008,12b9,baba)
and the manufacturer and name of serial board or modem board
to serial-pci-info@lists.sourceforge.net.
ttyS04 at port 0xd000 (irq = 16) is a 16550A
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 1430M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: AGP aperture is 128M @ 0xd0000000
Uniform Multi-Platform E-IDE driver Revision: 7.00beta-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci00:11.1
ide0: BM-DMA at 0xe400-0xe407, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xe408-0xe40f, BIOS settings: hdc:DMA, hdd:pio
hda: ST320413A, ATA DISK drive
hdb: Maxtor 31536U2, ATA DISK drive
hda: DMA disabled
blk: queue c02ed700, I/O limit 4095Mb (mask 0xffffffff)
hdb: DMA disabled
blk: queue c02ed84c, I/O limit 4095Mb (mask 0xffffffff)
hdc: CD-W54E, ATAPI CD/DVD-ROM drive
hdc: DMA disabled
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: host protected area => 1
hda: 39102336 sectors (20020 MB) w/512KiB Cache, CHS=2434/255/63, UDMA(100)
hdb: host protected area => 1
hdb: 30015216 sectors (15368 MB) w/512KiB Cache, CHS=1868/255/63, UDMA(66)
Partition check:
hda: hda1 hda2 hda4 < hda5 hda6 >
hdb: hdb1 hdb2 hdb3 < hdb5 hdb6 >
usb.c: registered new driver hub
hcd.c: ehci-hcd @ 00:10.3, VIA Technologies, Inc. USB 2.0
hcd.c: irq 19, pci mem f8840000
usb.c: new USB bus registered, assigned bus number 1
hcd/ehci-hcd.c: USB 2.0 support enabled, EHCI rev 1.00, ehci-hcd 2002-Sep-23
hub.c: USB hub found
hub.c: 6 ports detected
usb-uhci.c: $Revision: 1.275 $ time 00:36:21 Dec 14 2002
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: USB UHCI at I/O 0xd800, IRQ 21
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: USB UHCI at I/O 0xdc00, IRQ 21
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: USB UHCI at I/O 0xe000, IRQ 21
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 4
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 16384 buckets, 128Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 80k freed
hub.c: new USB device 00:10.0-1, assigned address 2
input0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb2:2.0
Adding Swap: 88316k swap-space (priority -1)
Adding Swap: 411640k swap-space (priority -2)
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,66), internal journal
hub.c: new USB device 00:10.0-2, assigned address 3
hub.c: USB hub found
hub.c: 4 ports detected
Real Time Clock Driver v1.10e
hub.c: new USB device 00:10.0-2.2, assigned address 4
usb.c: USB device 4 (vend/prod 0x545/0x8002) is not claimed by any active driver.
Linux video capture interface: v1.00
usb.c: registered new driver ibmcam
ibmcam.c: IBM NetCamera USB camera found (model 4, rev. 0x030a)
usbvideo.c: ibmcam on /dev/video0: canvas=352x288 videosize=352x288
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,70), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,2), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,5), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3415 bytes --]
^ permalink raw reply
* Re: MSN helper module
From: Carlos Fernandez Sanz @ 2002-12-17 9:51 UTC (permalink / raw)
To: Patrick Schaaf; +Cc: netfilter-devel
In-Reply-To: <20021217075448.GA24766@oknodo.bof.de>
Patrick,
MSN is (other than a ISP), an instant messaging service like ICQ.
Unfortunately, one of the most used these days (because it's the Microsoft
supported one). The helper module would have to do the same thing the other
modules do - keep track of children connection, rewrite some packets to
change IPs, etc.
Carlos.
----- Original Message -----
From: "Patrick Schaaf" <bof@bof.de>
To: "Carlos Fernandez Sanz" <cfs-netfilter@nisupu.com>
Cc: <netfilter-devel@lists.netfilter.org>
Sent: Tuesday, December 17, 2002 08:54
Subject: Re: MSN helper module
> On Tue, Dec 17, 2002 at 12:57:35AM +0100, Carlos Fernandez Sanz wrote:
> >
> > Is there a helper module for MSN? If not, is it being developed and can
I
> > join the effort?
> >
> > If nothing is being done I'll just write the module myself before not
having
> > full MSN support becomes a serious issue and starts going up...
>
> Ahem - what would such a helper module have to do? As far as I know,
> MSN is an Internet Service Provider, and there is no network protocol
> called MSN. Did that change? Do they do the AOL, 10 years later?
>
> I sure hope so, it would be their final death.
>
> Sorry for off-topic; my first question, above, is what should be
discussed.
>
> best regards
> Patrick
>
^ permalink raw reply
* Re: rmap and nvidia?
From: Andrew McGregor @ 2002-12-17 9:58 UTC (permalink / raw)
To: O.Sezer, linux-kernel
In-Reply-To: <3DFE522A.6010803@superonline.com>
The bit calling pte_unmap in nv-linux.h is the only difference from the
current minion.de patch, but it works, doesn't oops any more, nor does it
leak memory any more :-)
Great! X on 2.5 on my laptop!
Andrew
--On Tuesday, December 17, 2002 00:22:34 +0200 "O.Sezer"
<sezero@superonline.com> wrote:
> Is this patch correct in any way?
> (Ripped out of the 2.5 patch and modified some).
>
> Thanks.
>
^ permalink raw reply
* Re: "iptables: Invalid argument" with kernel 2.4.20
From: cees-bart @ 2002-12-17 9:55 UTC (permalink / raw)
To: netfilter
In-Reply-To: <200212161435.06101.netfilter@newkirk.us>
On Mon, 16 Dec 2002, Joel Newkirk wrote:
> On Monday 16 December 2002 11:25 am, cees-bart wrote:
> > hi all,
>
> > -A OUTPUT -d MYMACHINE -p udp -m udp --dport 27960 -j DNAT \
> > --to-destination OTHERMACHINE:30000
>
> > this setup works fine on kernel 2.4.19 with iptables 1.2.6a.
> >
> > BUT, the last rule (OUTPUT) fails with message "iptables: Invalid
> > argument" when running under 2.4.20.
>
> Have you tried manually creating the rule, or are you restoring from a
> save made with the earlier version?
i tried both, and i found my mistake:
i forgot to enable CONFIG_IP_NF_NAT_LOCAL in the kernel.
sorry for the trouble.
bye,
cees-bart
^ permalink raw reply
* Re: Alcatel speedtouch USB driver and SMP.
From: Andrew McGregor @ 2002-12-17 10:02 UTC (permalink / raw)
To: Greg KH, Colin Paul Adams; +Cc: linux-kernel
In-Reply-To: <3880000.1040039852@localhost.localdomain>
The 2.5 tree one works for me *with PPPoATM*, which I gather is kind of a
rare setup.
Andrew
--On Tuesday, December 17, 2002 00:57:32 +1300 Andrew McGregor
<andrew@indranet.co.nz> wrote:
> There's a binary only one from Alcatel themselves, which only works on
> one 2.2 kernel and one (old) 2.4 kernel, the other is on SourceForge, and
> is also GPL.
>
> Andrew, who's just set up one himself on 2.4 and will try 2.5 when enough
> else behaves.
>
> --On Sunday, December 15, 2002 21:13:00 -0800 Greg KH <greg@kroah.com>
> wrote:
>
>> On Sun, Dec 15, 2002 at 08:58:14AM +0000, Colin Paul Adams wrote:
>>> >>>>> "Greg" == Greg KH <greg@kroah.com> writes:
>>>
>>> Greg> On Sun, Dec 15, 2002 at 07:10:33AM +0000, Colin Paul Adams
>>> Greg> wrote:
>>> >> Can anyone tell me if the speedtouch driver is SMP safe yet?
>>>
>>> Greg> Which driver? I know of at least 3 different ones :(
>>>
>>> drivers/usb/misc/speedtouch.c
>>
>> Ah good, you're using one that the source is available for :)
>> I think the developer has said it will work on SMP machines, but what
>> problems are you having, and have you asked the author of the code?
>>
>>> Where are the others?
>>
>> I don't know, but I know they are out there...
>>
>> thanks,
>>
>> greg k-h
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
>> in the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
^ permalink raw reply
* Re: Redhat 7.3 and IPTables 1.2.7a (was ICMP Destination Unreachable)
From: Marcello Scacchetti @ 2002-12-17 10:01 UTC (permalink / raw)
To: hare ram; +Cc: freedom, netfilter
In-Reply-To: <025b01c2a5b8$e2e7c200$13fcc5cb@nextto>
Try check here: http://www.haoli.org/rpm/redhat-7.x/RPMS/i386/
Marcello
Il mar, 2002-12-17 alle 11:41, hare ram ha scritto:
> hi
>
> yes you can patch up the kernel with new version
> but there is no Latest rpm availbale for 1.2.7a
>
> you need to use only 1.2.6a latest RPM with Redhat 8.0
> ----- Original Message -----
> From: "freedom" <freedom10@idemation.com>
> To: "'Marcello Scacchetti'" <marcello.scacchetti@nextrem.it>;
> <netfilter@lists.netfilter.org>
> Sent: Tuesday, December 17, 2002 9:23 AM
> Subject: RE: Redhat 7.3 and IPTables 1.2.7a (was ICMP Destination
> Unreachable)
>
>
> > Marcello,
> >
> > Sure...
> >
> > Is it possible to use IPTables version 1.2.7a with Redhat 7.3? RH 7.3
> > comes with a different version by default and I wanted to upgrade to
> > 1.2.7a. Is it possible?
> >
> > Also, do you know if any RPMs exist for IPTables version 1.2.7a and RH
> > 7.3?
> >
> > Thanks!
> > Kameron
> >
> > > -----Original Message-----
> > > From: netfilter-admin@lists.netfilter.org [mailto:netfilter-
> > > admin@lists.netfilter.org] On Behalf Of Marcello Scacchetti
> > > Sent: Monday, December 16, 2002 7:18 AM
> > > To: netfilter@lists.netfilter.org
> > > Subject: Re: ICMP Destination Unreachable
> > >
> > > Hi Kameron,
> > > can you be a little more verbose?
> > > What does "run" means? Unable to set rules? Unable to run iptables
> > > command? Unable to make rules work?
> > >
> > > Marcello
> > >
> > > Il ven, 2002-12-06 alle 16:09, Kameron ha scritto:
> > > > Hello Gurus,
> > > >
> > > > I have a couple of quick questions...
> > > >
> > > > 1) Does anybody know of any reason why I couldn't run IPTables
> > 1.2.7a
> > > > with RH7.3.
> > > >
> > > > 2) Are there any .rpm's for IPTables 1.2.7.a available? I attempted
> > to
> > > > compile my own, but didn't have any luck.
> > > >
> > > > Thanks!
> > > > Kameron
> > > --
> > > Marcello Scacchetti <marcello.scacchetti@nextrem.it>
> > >
> >
> >
> >
> >
--
Marcello Scacchetti <marcello.scacchetti@nextrem.it>
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
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.