Re: SPAM/virii apparently from freeBSD addresses.
On Sun, 29 Feb 2004, Julian Elischer wrote: > Somewhere out there there is a ?Virus?/?Hacker?/?Spammer? > getting really annoying.. Yeah, I'm getting it too. Worst part is, clamav 0.65 doesn't pick it up. I'm waiting for the 0.67 port to be committed... Mike "Silby" Silbersack ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SPAM/virii apparently from freeBSD addresses.
Oh it was just a rant.. :-( On Sun, 29 Feb 2004, Kris Kennaway wrote: > On Sun, Feb 29, 2004 at 04:50:34PM -0800, Julian Elischer wrote: > > > > Somewhere out there there is a ?Virus?/?Hacker?/?Spammer? > > getting really annoying.. > > Yeah, but what do you expect anyone to do about it? > > Kris > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: em0, polling performance, P4 2.8ghz FSB 800mhz
From: Mike Tancsa [mailto:[EMAIL PROTECTED] > At 08:44 PM 29/02/2004, Don Bowman wrote: > >From: Mike Tancsa [mailto:[EMAIL PROTECTED] > > > > > > On Sat, 28 Feb 2004 23:17:44 -0500, in > sentex.lists.freebsd.hackers > > > > >If you want to spend more time in kernel, perhaps change > > > > > > > >I might have HZ @ 2500 as well. > > > > > > Hi, > > > Just curious as to the reasoning behind that ? > > > >@ high packet rates, you don't have enough DMA > >queues available to the em driver, and will drop. > >increasing the number of dma buffers will cause > >problems with cache occupancy. Increasing the HZ > >doesn't have a huge cost. > > But why that value ? Did you determine it by trial and error > or deduce it > based on some other factors ? Also, is this value optimal > for fxp based boxes. I picked 2500 as the best for my system. Its higher than allowed by rfc1323 and PAWS [kern/61404], but not by so much that i anticipate a problem. For my target packets per second rate, it means that i can use a reasonable number of dma descriptors. I found that bridging performance in particular needs the higher hz to avoid dropping packets, to improve its performance. I'm not sure what affect on fxp. fxp is inherently limited by something internal to it, which prevents achieving high packet rates. bge is the best chip, but doesn't have the best bsd support. The value of HZ needs to be based on your target packet rate, the maximum latency in your system, and the size of your buffers for all steps. more buffers == better ability to handle latency bursts, but worse for cache occupancy. Freebsd is not the best system for trying to guarantee latency through, you can find things like ahd, syncache, arp freeing that will suddenly wake up and munch all kinds of cpu time with spl? taken. freebsd-current is both better and worse: its better with the fine grained locking, but worse since those locks can end up costing you more than you would have spent just taking giant and being done with it: semaphores are expensive, particularly on SMP systems. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: em0, polling performance, P4 2.8ghz FSB 800mhz
At 08:44 PM 29/02/2004, Don Bowman wrote: From: Mike Tancsa [mailto:[EMAIL PROTECTED] > > On Sat, 28 Feb 2004 23:17:44 -0500, in sentex.lists.freebsd.hackers > > >If you want to spend more time in kernel, perhaps change > > > >I might have HZ @ 2500 as well. > > Hi, > Just curious as to the reasoning behind that ? @ high packet rates, you don't have enough DMA queues available to the em driver, and will drop. increasing the number of dma buffers will cause problems with cache occupancy. Increasing the HZ doesn't have a huge cost. But why that value ? Did you determine it by trial and error or deduce it based on some other factors ? Also, is this value optimal for fxp based boxes. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: em0, polling performance, P4 2.8ghz FSB 800mhz
From: Mike Tancsa [mailto:[EMAIL PROTECTED] > > On Sat, 28 Feb 2004 23:17:44 -0500, in sentex.lists.freebsd.hackers > > >If you want to spend more time in kernel, perhaps change > > > >I might have HZ @ 2500 as well. > > Hi, > Just curious as to the reasoning behind that ? @ high packet rates, you don't have enough DMA queues available to the em driver, and will drop. increasing the number of dma buffers will cause problems with cache occupancy. Increasing the HZ doesn't have a huge cost. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Intel wireless NIC on ThinkPad T41
On Monday 01 March 2004 10:08, Julian Elischer wrote: > only in 5.2+ see "project evil" > > On Sun, 29 Feb 2004, Bob Bishop wrote: > > Hi, > > > > Anyone managed to get this working? > > > > [EMAIL PROTECTED]:2:0: class=0x028000 card=0x25518086 chip=0x10438086 rev=0x04 > > hdr=0x00 > > > > vendor = 'Intel Corporation' > > device = 'PRO/Wireless LAN 2100 3B Mini PCI Adapter' > > class= network I have mine working with if_ndis (Project Evil). Let me know if you need a hand. See -> http://www.gsoft.com.au/~doconnor/I8600/ -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP!!! USB MFC committed..
On Sun, 29 Feb 2004, Julian Elischer wrote: > > The USB code in RELENG_4 has been updated to match that in -current. > Please test any USB devices that are critical to you BEFORE we release > 4.10 :-) p.s. there are some more MFCs to come but they are minor (except for what looks like a major rewrite of parts of umass) > > > thanks > > Julian > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
HEADSUP!!! USB MFC committed..
The USB code in RELENG_4 has been updated to match that in -current. Please test any USB devices that are critical to you BEFORE we release 4.10 :-) thanks Julian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SPAM/virii apparently from freeBSD addresses.
Somewhere out there there is a ?Virus?/?Hacker?/?Spammer? getting really annoying.. take this one for example:.. It has a legit FreeBSD from address of someone I'd read, and a subject line that I've seen before on this list, and all sorts of other forgery stuff. >From [EMAIL PROTECTED] Sun Feb 29 16:29:03 2004 -0800 Status: R X-Status: X-Keywords: Return-Path: <[EMAIL PROTECTED]> Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA49824 for <[EMAIL PROTECTED]>; Sun, 29 Feb 2004 16:29:00 -0800 (PST) From: [EMAIL PROTECTED] Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id A83295576A for <[EMAIL PROTECTED]>; Sun, 29 Feb 2004 16:28:59 -0800 (PST) (envelope-from [EMAIL PROTECTED]) Received: by hub.freebsd.org (Postfix) id A421316A4CF; Sun, 29 Feb 2004 16:28:59 -0800 (PST) Delivered-To: [EMAIL PROTECTED] Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A10F516A4CE for <[EMAIL PROTECTED]>; Sun, 29 Feb 2004 16:28:59 -0800 (PST) Received: from freebsd.org (unknown [210.66.161.77]) by mx1.FreeBSD.org (Postfix) with SMTP id 419AB43D39 for <[EMAIL PROTECTED]>; Sun, 29 Feb 2004 16:28:50 -0800 (PST) (envelope-from [EMAIL PROTECTED]) To: [EMAIL PROTECTED] Subject: stolen Date: Mon, 1 Mar 2004 08:29:23 +0800 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="04136376" Message-Id: <[EMAIL PROTECTED]> [...] (spam deleted) This damned thing is obviously using a real mail as a template.. the only thing that it hasn't been able to spoof is the originating IP address.. in taiwan somewhere. [InterJet.elischer.org] 346 traceroute 210.66.161.77 traceroute to 210.66.161.77 (210.66.161.77), 30 hops max, 40 byte packets 1 10.144.192.1 (10.144.192.1) 13.072 ms 10.885 ms 10.212 ms 2 12.244.97.97 (12.244.97.97) 11.357 ms 9.902 ms 11.117 ms 3 12.244.67.86 (12.244.67.86) 13.140 ms 23.507 ms 11.977 ms 4 12.124.35.57 (12.124.35.57) 16.431 ms 25.404 ms 38.147 ms 5 gbr6-p80.sffca.ip.att.net (12.123.13.154) 20.889 ms 16.106 ms 15.797 ms 6 tbr2-p013601.sffca.ip.att.net (12.122.11.93) 26.930 ms 15.280 ms 16.038 m s 7 ggr2-p390.sffca.ip.att.net (12.123.13.194) 14.605 ms 31.905 ms 39.139 ms 8 p16-0-1-1.r20.plalca01.us.bb.verio.net (129.250.9.73) 21.166 ms 36.620 ms 16.578 ms 9 xe-0-2-0.r21.plalca01.us.bb.verio.net (129.250.4.231) 24.247 ms 22.128 ms 22.849 ms 10 p64-0-0-0.r21.mlpsca01.us.bb.verio.net (129.250.5.49) 35.048 ms 27.652 ms 24.794 ms 11 p16-6-0-0.r80.mlpsca01.us.bb.verio.net (129.250.3.24) 17.962 ms 18.794 ms 23.245 ms 12 p16-0-2-0.r20.tokyjp01.jp.bb.verio.net (129.250.4.154) 131.523 ms 131.186 ms 139.967 ms 13 ge-0-0-0.r00.tokyjp01.jp.bb.verio.net (129.250.3.121) 152.421 ms 146.529 m s 145.884 ms 14 p4-0-2-0.r00.taiptw01.tw.bb.verio.net (129.250.4.214) 198.825 ms 190.690 m s 185.596 ms 15 ge-0-0-0.a01.taiptw01.tw.ra.verio.net (61.58.32.35) 182.409 ms 184.256 ms 185.005 ms 16 61.58.33.106 (61.58.33.106) 179.527 ms 175.598 ms 182.063 ms 17 R59-169.seed.net.tw (139.175.59.169) 184.325 ms 177.720 ms 176.060 ms 18 R56-210.seed.net.tw (139.175.56.210) 181.436 ms 177.463 ms 176.991 ms 19 R58-178.seed.net.tw (139.175.58.178) 178.742 ms 183.660 ms 179.474 ms 20 sh38-33.seed.net.tw (139.175.38.33) 183.048 ms 181.770 ms 186.065 ms 21 h170-192-72-33.seed.net.tw (192.72.33.170) 189.714 ms 185.537 ms 196.507 ms 22 *^C [InterJet.elischer.org] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Intel wireless NIC on ThinkPad T41
only in 5.2+ see "project evil" On Sun, 29 Feb 2004, Bob Bishop wrote: > Hi, > > Anyone managed to get this working? > > [EMAIL PROTECTED]:2:0: class=0x028000 card=0x25518086 chip=0x10438086 rev=0x04 > hdr=0x00 > > vendor = 'Intel Corporation' > device = 'PRO/Wireless LAN 2100 3B Mini PCI Adapter' > class= network > > -- > Bob Bishop+44 (0)118 977 4017 > [EMAIL PROTECTED] fax +44 (0)118 989 4254 > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sockets and the owner process
On Saturday, February 28, 2004, at 09:52 AM, grinder wrote: I want to create a small kernel module which logs the socket operations. So in my module i have a socket structure, and i want to know which process (thread) owns it. But the socket structure isn't contains any reference to the process structure. If i walk through the vnode table i can find my socket by the so_gencnt "unique id", but the vnode structure isn't have any variables back to the proc structure. Is it possible to get the owner proc structure for a socket? Not really. Socket descriptors, like other file-descriptors, can be handed off by the fork/exec process, and via local domain sockets to unrelated processes, so by the time that the socket is actually used, there can be no relation to the process that created it (e.g., inetd/xinetd creates it, waits for a connection, accepts the connection, and then passes the descriptor to the service process via fork/exec, and closes its version of that socket). The best you can hope for is to determine processes that are actually using the socket, and that can vary during the socket's lifetime. You would have to scour the file descriptor tables in all process structures to determine which processes had a handle on each socket you have an interest in. There is no real "ownership" of anything accessed via file descriptors. Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics| It's not whether you win or lose... | It's whether *I* win or lose. *--*---* ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Intel wireless NIC on ThinkPad T41
Hi, Anyone managed to get this working? [EMAIL PROTECTED]:2:0: class=0x028000 card=0x25518086 chip=0x10438086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless LAN 2100 3B Mini PCI Adapter' class= network -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 4.9 boot problem on em0 platform.
From: Deepak Jain [mailto:[EMAIL PROTECTED] > > Just a guess, but i think you've bumped nmbclusters or nmbufs up > > too much (or perhaps maxsockets, maxfds, ...) and have run out of > > KVA. > > > > You can tune clusters & mbufs in loader.conf without recompiling > > kernel. You will want to see what vm.zone_kmem_pages, > vm.zone_kmem_kvaspace > > are showing you, vmstat -z, vmstat -m, etc. > > > > You may want to alter VM_KMEM_SIZE_SCALE to e.g. '2' if you are > > trying to put more into the kernel mem space. > > > > The kernel that works from another machine has the same settings > (NMBCLUSTERS=65536, maxusers=512). The machine has 2GB of RAM. > > How do you undo the loader.conf settings when the machine won't boot > because of the settings you made? :| Use 'space' to get to the 'ok' loader prompt. now 'set' the values to a lower #... ok set path.path.path=value man loader will tell you about this. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.9 boot problem on em0 platform.
Just a guess, but i think you've bumped nmbclusters or nmbufs up too much (or perhaps maxsockets, maxfds, ...) and have run out of KVA. You can tune clusters & mbufs in loader.conf without recompiling kernel. You will want to see what vm.zone_kmem_pages, vm.zone_kmem_kvaspace are showing you, vmstat -z, vmstat -m, etc. You may want to alter VM_KMEM_SIZE_SCALE to e.g. '2' if you are trying to put more into the kernel mem space. The kernel that works from another machine has the same settings (NMBCLUSTERS=65536, maxusers=512). The machine has 2GB of RAM. How do you undo the loader.conf settings when the machine won't boot because of the settings you made? :| thanks, Deepak ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 4.9 boot problem on em0 platform.
> From: Deepak Jain [mailto:[EMAIL PROTECTED] > As a part of tracking down a performance issue, I tried building a > custom kernel (with just IPFW, DUMMYNET added, NMBCLUSTERS, > commenting > out MATH_EMULATE, INET6, I386, I486). The system is currently > running a > kernel from a similar machine with the same settings. The > machine does > run on this kernel: 4.9-RELEASE FreeBSD 4.9-RELEASE #8, with > the above > options, but I have not been able to compile a 4.9-RELEASE #2 > (which is > the source tree on the machine) kernel that has an identical > config file. > > So, when it builds itself from -RELEASE sources, it hangs at: > > "pmap_mapdev: Couldn't alloc kernel virtual memory" I couldn't find a > reference to anything recent. Nothing non-default (from a GENERIC > kernel) with respect to ACPI has been touched. I see a reference to > -CURRENT from 9/03, but that's it. Just a guess, but i think you've bumped nmbclusters or nmbufs up too much (or perhaps maxsockets, maxfds, ...) and have run out of KVA. You can tune clusters & mbufs in loader.conf without recompiling kernel. You will want to see what vm.zone_kmem_pages, vm.zone_kmem_kvaspace are showing you, vmstat -z, vmstat -m, etc. You may want to alter VM_KMEM_SIZE_SCALE to e.g. '2' if you are trying to put more into the kernel mem space. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
4.9 boot problem on em0 platform.
As a part of tracking down a performance issue, I tried building a custom kernel (with just IPFW, DUMMYNET added, NMBCLUSTERS, commenting out MATH_EMULATE, INET6, I386, I486). The system is currently running a kernel from a similar machine with the same settings. The machine does run on this kernel: 4.9-RELEASE FreeBSD 4.9-RELEASE #8, with the above options, but I have not been able to compile a 4.9-RELEASE #2 (which is the source tree on the machine) kernel that has an identical config file. So, when it builds itself from -RELEASE sources, it hangs at: "pmap_mapdev: Couldn't alloc kernel virtual memory" I couldn't find a reference to anything recent. Nothing non-default (from a GENERIC kernel) with respect to ACPI has been touched. I see a reference to -CURRENT from 9/03, but that's it. Should I turn off power management? Is there a way to prevent ACPI support from being loaded at the kernel level? Should I just cvsup to 4.9-RELENG and try it again? It would be very nice if this were some how related to my network performance problem, but that might be too much to hope for. :) Thanks in advance, DJ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: em0, polling performance, P4 2.8ghz FSB 800mhz
On Sun, 29 Feb 2004, Mike Silbersack wrote: > On Sat, 28 Feb 2004, Don Bowman wrote: > > > this would only allow 2 concurrent TCP sessions per unique > > source address. Depends on the syn flood you are expecting > > to experience. You could also use dummynet to shape syn > > traffic to a fixed level i suppose. > > Does that really help? If so, we need to optimize the syncache. :( Given that we have syncookie support, the other thing we could consider doing under high syn load is simply to drop the syncache from the loop entirely. The syncache provides us with the ability to "gracefully degrade" as the syn rate goes up, but the FIFO cache bucket overflow handling means we pay the cost of syncache entry allocation even in the high load situation. It might be interesting to measure when syncache overflow is taking place, and simply drop it from the loop under a rate known to exceed the syncache capacity, then re-enable it again once the rate drops. This would remove a memory allocation, queue walking, and in the case of an SMP system, locking, from the syn handling path. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Senior Research Scientist, McAfee Research ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: em0, polling performance, P4 2.8ghz FSB 800mhz
From: Mike Silbersack [mailto:[EMAIL PROTECTED] > On Sat, 28 Feb 2004, Don Bowman wrote: > > > You could use ipfw to limit the damage of a syn flood, e.g. > > a keep-state rule with a limit of ~2-5 per source IP, lower the > > timeouts, increase the hash buckets in ipfw, etc. This would > > use a mask on src-ip of all bits. > > something like: > > allow tcp from any to any setup limit src-addr 2 > > > > this would only allow 2 concurrent TCP sessions per unique > > source address. Depends on the syn flood you are expecting > > to experience. You could also use dummynet to shape syn > > traffic to a fixed level i suppose. > > Does that really help? If so, we need to optimize the syncache. :( In a real-world situation, with some latency from the originating syn-flood attacker, the syncache behaves fine. In a synthetic test situation like this, with probably ~0 latency from the initiator, the syncache gets overwhelmed too. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP.. USB MFC coming..
On Fri, Feb 27, 2004 at 05:54:18PM -0800, Julian Elischer wrote: > > I plan to commit the MFC at http://www.josef-k.net/freebsd/ > (the latest one) in the next couple of days. If you really care about > USB in 4.10 you might do well to test this on your equipment, > ESPECIALLY if you have unusual devices. Let me know of both successes > and failures please.. If I hear nothing I won't know if it's because > no-one tested it or it was just without problems.. Hi Julian, The usb.ko module failed to load with these patches (usb_allocmem undefined). Adding usb_mem.c to SRCS in /sys/modules/usb/Makefile seems to fix this - my USB mouse, flash reader and cheap-ass 'pen drive' all appear to be working as before. One strange thing though - booting from my usual kernel (which loads most things from modules) I get some extra whining when the USB ports are being probed: uhci0: port 0xd800-0xd81f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port error, restarting port 1 uhub0: port error, giving up port 1 umass0: Generic Mass Storage Device, rev 1.10/1.00, addr 2 umass0: Get Max Lun not supported (STALLED) uhub0: port error, restarting port 2 uhub0: port error, giving up port 2 umass1: DMI MultiFlash, rev 1.10/1.00, addr 3 uhci1: port 0xdc00-0xdc1f irq 10 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub1: port error, restarting port 1 uhub1: port error, giving up port 1 ugen0: LEGO Group LEGO USB Tower, rev 1.10/1.00, addr 2 uhub1: port error, restarting port 2 uhub1: port error, giving up port 2 ums0: Logitech USB Receiver, rev 1.10/9.10, addr 3, iclass 3/1 ums0: 5 buttons and Z dir. Booting from a GENERIC built from the same sources, I don't get any of the 'port error' messages: uhci0: port 0xd800-0xd81f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered umass0: Generic Mass Storage Device, rev 1.10/1.00, addr 2 umass0: Get Max Lun not supported (STALLED) umass1: DMI MultiFlash, rev 1.10/1.00, addr 3 uhci1: port 0xdc00-0xdc1f irq 10 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ugen0: LEGO Group LEGO USB Tower, rev 1.10/1.00, addr 2 ums0: Logitech USB Receiver, rev 1.10/9.10, addr 3, iclass 3/1 ums0: 5 buttons and Z dir. This doesn't seems to have any effect on whether things work or not though, other than the umass devices coming up on different SCSI busses if I don't load USB from the module, but I think that has always been the case. Otherwise it looks good. Scott -- === Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" scott at fishballoon.org | 0xAA775B8B | -- Anon ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel options
On Sun, 29 Feb 2004, Kris Kennaway wrote: > On Sun, Feb 29, 2004 at 11:36:56AM +0200, Danny Braniss wrote: > > hi, > > is there a way of knowing with which kernel-options a particular kernel > > was compiled with (appart form the obvious config file)? > > In general, no. I have read about an option to include the configuration file with the kernel. From my 4.9-stable /usr/src/sys/i386/conf/LINT file: # This allows you to actually store this configuration file into # the kernel binary itself, where it may be later read by saying: #strings -n 3 /kernel | sed -n 's/^___//p' > MYKERNEL # options INCLUDE_CONFIG_FILE # Include this file in kernel Not useful unless you've used it, which is not the default case. -- Dan Langille - BSDCan: http://www.bsdcan.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel options
On Sun, Feb 29, 2004 at 11:36:56AM +0200, Danny Braniss wrote: > hi, > is there a way of knowing with which kernel-options a particular kernel > was compiled with (appart form the obvious config file)? In general, no. Kris pgp0.pgp Description: PGP signature
FreeSBIE-1.0-i386 Released
The FreeSBIE project is proud to announce the release of FreeSBIE-1.0-i386.iso FreeSBIE is a bootable CD with the FreeBSD operating system and a collection of software to address the needs of an etherogeneus public. FreeSBIE-1.0 is based on FreeBSD 5.2.1 for the ia32 platform, and has a hardware recognition system which lets it find automagically all the peripherals supported on FreeBSD 5.2.1. FreeSBIE-1.0-i386.iso is the result of the toolkit provided for FreeBSD, and is released to show the power of the operating system and of FreeSBIE itself. FreeSBIE-1.0-i386.iso is addressed to the following categories of users: - System Administrators; - Developers; - Final users; With FreeSBIE-1.0-i386.iso it is possible to satisfy users who: - have the need for multimedia applications; - make deep network analysis; - have problems with damaged or unusable FreeBSD installations; - want to test new FreeBSD functionalities; - need a completely functional FreeBSD system; - want to illustrate and/or release a product based on FreeBSD; - need the power of FreeBSD but don't have the immediate chance to install it/configure it. FreeSBIE-1.0-i386.iso is also designed for day-to-day use through a collection of programs which come with it, thought for a typical workstation use: - Evolution as Personal Information Manager; - Gaim as Instant Messenger; - Pan as newsreader; - XMMS and MPlayer as multimedia players; - XChat as IRC client For a complete list of available applications on FreeSBIE-1.0-i386.iso, check the file FreeSBIE-1.0-pkgs.txt available on our FTP sites (see below). When choosing the applications we tried to address both the needs of the desktop users and console users. In fact we give you the chance to use Mutt, as well as Evolution, and together with Firefox we provide links, while with XChat we offer irssi. Those interested in downloading our software, can find FreeSBIE-1.0-i386.iso on the following FTP sites: ftp://ftp.freesbie.org ftp://ftp2.freesbie.org The main website for the FreeSBIE toolkit is: http://www.FreeSBIE.org where you can also find some more explicative screenshots. Our thanks for the help provided goes to: All the ones who are excluded from this list; All the authors of the included packages; The FreeBSD Team (http://www.FreeBSD.org); The Italian FreeBSD Users Group (http://www.gufi.org); [EMAIL PROTECTED] for the hardware donated; [EMAIL PROTECTED] for the cloop utility FreeBSD port (compressed filesystem) FreeSBIE-1.0-i386.iso will surely not be error-prone, wanted or not, but it's a 1.0 release, and as such please beg our pardon for our mistakes. To contact the members of the FreeSBIE project, we invite you to visit the project's website in the "contacts" section. Some programs included are released under the GPL license. The related sources can be found on the homepages of the rispected projects. The FreeSBIE project remains open to suggestions, developments and observations. Hoping to have created a usable product, efficient and satisfying for your needs, we wish you a great fun with FreeSBIE, The FreeSBIE project signature.asc Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata
Sockets and the owner process
I want to create a small kernel module which logs the socket operations. So in my module i have a socket structure, and i want to know which process (thread) owns it. But the socket structure isn't contains any reference to the process structure. If i walk through the vnode table i can find my socket by the so_gencnt "unique id", but the vnode structure isn't have any variables back to the proc structure. Is it possible to get the owner proc structure for a socket? Thanks, Tibor Kiss ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel options
> On Sun, 29 Feb 2004, 11:36+0200, Danny Braniss wrote: > > > hi, > > is there a way of knowing with which kernel-options a particular kernel > > was compiled with (appart form the obvious config file)? > > Yes, if you use 'options INCLUDE_CONFIG_FILE'. See /sys/conf/NOTES > for details. i knew that im walking in the footsteps of giants :-) thanks, danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel options
On Sun, 29 Feb 2004, 11:36+0200, Danny Braniss wrote: > hi, > is there a way of knowing with which kernel-options a particular kernel > was compiled with (appart form the obvious config file)? Yes, if you use 'options INCLUDE_CONFIG_FILE'. See /sys/conf/NOTES for details. -- Maxim Konovalov ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP.. USB MFC coming..
On Sat, 28 Feb 2004, Julian Elischer wrote: JE> > Well, my main headache (SONY Clie SJ20) is now in a bit different state; before JE> > (at 4.9p1) it failed to attach with JE> > JE> > ucom0: Palm, Inc. Palm Handheld, rev 1.00/1.00, addr 2 JE> > ucom0: Palm, Inc. Palm Handheld, rev 1.00/1.00, addr 2 JE> > ucom0: init failed, STALLED JE> > device_probe_and_attach: ucom0 attach returned 6 JE> > ugen0: Palm, Inc. Palm Handheld, rev 1.00/1.00, addr 2 JE> > JE> > now it is correctly identified (after HotSync activation) as JE> > JE> > ucom0: Palm, Inc. Palm Handheld, rev 1.00/1.00, addr 2 JE> > ucom0: Palm, Inc. Palm Handheld, rev 1.00/1.00, addr 2 JE> > JE> > However, I still can't figure out how to sync, as dlpsh can't attach to JE> > /dev/ucom before activatyng Sync, and never goes to the shell prompt when JE> JE> shouldn't it be /dev/ucom0? JE> (assuming it exists) They both exist and have the same pair (major, minor). JE> > I had I/O errors and hangups with cheap MemoryStick reader before, JE> > but do not have it by hand to quick check. Hope to check tomorrow. JE> JE> I'll go ahead with the MFC but I'll JE> try handle these reports afterwards... Thanks again, I'll post MS reader testing results tonight (I'm at GMT+3 ;-) Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
kernel options
hi, is there a way of knowing with which kernel-options a particular kernel was compiled with (appart form the obvious config file)? danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
