From owner-freebsd-hackers Sun Apr 29 0: 3: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bryden.apana.org.au (bryden.apana.org.au [203.3.126.129]) by hub.freebsd.org (Postfix) with ESMTP id 07C4237B422; Sun, 29 Apr 2001 00:02:56 -0700 (PDT) (envelope-from dougy@bryden.apana.org.au) Received: from oracle (CPE-61-9-143-80.vic.bigpond.net.au [61.9.143.80]) by bryden.apana.org.au (8.9.3/8.9.3) with SMTP id RAA26968; Sun, 29 Apr 2001 17:01:44 +1000 (EST) (envelope-from dougy@bryden.apana.org.au) Message-ID: <068701c0d07a$5f051510$0400a8c0@oracle> From: "Doug Young" To: "Jim Durham" , =?iso-8859-1?Q?Jes=FAs_Arn=E1iz?= Cc: , References: Subject: Re: RV: VPN Date: Sun, 29 Apr 2001 17:02:31 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2462.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG vtund is fairly well documented, so I won't include a config file example, but I can supply one if asked. I would really appreciate any links etc you have to vtund documentation. After searching high & low for over a week I'd come to the conclusion that apart from one solitary (& very basic) HOWTO there wasn't anything of consequence. I did try for several days to get vtund working before putting it aside for a later day. Obviously doing was somethig wrong because every attempt to start vtund caused broken routing on the local machine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 0:14:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bryden.apana.org.au (bryden.apana.org.au [203.3.126.129]) by hub.freebsd.org (Postfix) with ESMTP id 1D09737B42C; Sun, 29 Apr 2001 00:14:11 -0700 (PDT) (envelope-from dougy@bryden.apana.org.au) Received: from oracle (CPE-61-9-143-80.vic.bigpond.net.au [61.9.143.80]) by bryden.apana.org.au (8.9.3/8.9.3) with SMTP id RAA27011; Sun, 29 Apr 2001 17:12:59 +1000 (EST) (envelope-from dougy@bryden.apana.org.au) Message-ID: <069301c0d07b$f23861b0$0400a8c0@oracle> From: "Doug Young" To: "Wes Peters" Cc: =?iso-8859-1?Q?Jes=FAs_Arn=E1iz?= , , References: <039501c0ce26$fccdaab0$0400a8c0@oracle> <3AE84A97.AFC183EB@softweyr.com> Subject: Re: VPN Date: Sun, 29 Apr 2001 17:13:46 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2462.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually I've published my own notes as part of the Pedantic FreeBSD rather than get involved with the official documentation project. I was subscribed to the docs list for a while but found the level of conversation so far over my head it was pointless being subscribed. I'll have another look there after the next update of Pedantic FreeBSD in a week or two in the hope that someone is speaking english (rather than martian or whatever). ----- Original Message ----- From: "Wes Peters" To: "Doug Young" Cc: "Jesús Arnáiz" ; ; Sent: Friday, April 27, 2001 2:19 AM Subject: Re: VPN > Doug Young wrote: > > > > I've just been going through this stuff for the past week. > > None of the things come with adequate documentation > > so you need to rely heavily on mailing list support. > > Thankfully a few people have been giving me > > some assistance but looks like at least few days more > > messing around will be involved before its working.. > > I certainly hope you're keeping careful notes, preparing to write that > FreeBSD Handbook section once you're done. Hint hint. > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > wes@softweyr.com http://softweyr.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 6:31:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailin1.bigpond.com (juicer13.bigpond.com [139.134.6.21]) by hub.freebsd.org (Postfix) with ESMTP id EDCDA37B424; Sun, 29 Apr 2001 06:31:26 -0700 (PDT) (envelope-from sldwyer@bigpond.com) Received: from bigpond.com ([139.134.4.50]) by mailin1.bigpond.com (Netscape Messaging Server 4.15) with SMTP id GCK34800.8D2; Sun, 29 Apr 2001 23:36:08 +1000 Received: from WEBH-T-009-p-253-68.tmns.net.au ([203.54.253.68]) by mail8.bigpond.com (Claudes-Tidy-MailRouter V2.9c 17/1492416); 29 Apr 2001 23:31:18 Message-ID: <3AEC1868.13FA5F62@bigpond.com> Date: Sun, 29 Apr 2001 21:34:32 +0800 From: Shaun Dwyer X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Patrick S. Gardella" Cc: tdwyer@bigpond.com, freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: LCD driver port (Linux -> FreeBSD) needed for car-mp3 player References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Patrick, I didn't really explain much about the LCD+Driver... Basically its a parallel port display that uses the generic Hitachi HD44780 chipset. What the driver for linux does is provide a /dev/lcd that you can address the same as you would /dev/cuaaX for a serial matrix orbital display. The reason I am using the parallel port LCD, is that it cost $80, as opposed to $400+ for the matrix orbital serial display (I am in Australia). Shaun "Patrick S. Gardella" wrote: > > Shaun, > > I looked at the Cajun pages. Very nice little box! > > As far as the LCD, you don't need a "driver" for it, since it uses either a > serial port interface or and i2c interface. For the serial port, you can use > whatever language you want to connect to it and talk to it. (Assuming you are > referring to the Matrix Orbital LCDs mentioned on that page.) > > Patrick > > On 26-Apr-01 Shaun Dwyer wrote: > > Hi everyone.. > > > > I have a PC in the boot of my car running Linux (yuck!!!!) to play mp3s. > > I would love to use FreeBSD instead of Linux for many reasons. > > The only thing stopping me using FreeBSD is the lack of a driver in the > > style > > implemented for Linux (provides a /dev/lcd that u just throw data at). > > > > The reason I need this driver to be ported is so I can use Cajun > > (cajun.sourceforge.net) > > with little or no modifications on FreeBSD. > > > > If I knew C, i would port the driver myself, and If i knew perl, I would > > mod > > cajun to use /usr/share/examples/ppi/ppilcd.c's stuff. > > > > The linux driver is available at: > > http://www4.infi.net/~cpinkham/cajun/code/lcd-0.2c.tar.gz > > > > If you want to see some photos and a bit of a description of my mp3 > > player, goto > > http://members.nbci.com/mp3zeus/ > > > > BTW, please email me directly, as I am not subscribed to the mailing > > list. > > > > Thanks in advance, > > > > Shaun > > > > > > -- > > ---------------------- > > Shaun Dwyer > > sldwyer@bigpond.com > > ---------------------- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > Patrick > ---------- > Patrick Gardella patrick@freebsd.org > The Power to Serve shall not be infringed. -- ---------------------- Shaun Dwyer sldwyer@bigpond.com ---------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 6:48:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id 974A737B424 for ; Sun, 29 Apr 2001 06:48:55 -0700 (PDT) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f3TDmrN12637 for ; Sun, 29 Apr 2001 08:48:54 -0500 (CDT) Message-Id: <200104291348.f3TDmrN12637@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: freebsd-hackers@freebsd.org Subject: Re: Port-related C++ question In-reply-to: Your message of "Sat, 28 Apr 2001 23:18:07 PDT." <20010428231807.G6731@lizzy.bugworks.com> Date: Sun, 29 Apr 2001 08:48:53 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010428231807.G6731@lizzy.bugworks.com>, Jos Backus writes: >Yeah, I am just puzzled as to how this can build at all on other platforms >(Linux?), unless they don't define this variable. Many of them probably have it as an external object, not a #define. I'm still not sure the code makes any sense. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 7:58:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 940AD37B43E for ; Sun, 29 Apr 2001 07:58:36 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f3TEwRR31360; Sun, 29 Apr 2001 08:58:29 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200104291458.f3TEwRR31360@harmony.village.org> To: seebs@plethora.net (Peter Seebach) Subject: Re: Port-related C++ question Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 29 Apr 2001 08:48:53 CDT." <200104291348.f3TDmrN12637@guild.plethora.net> References: <200104291348.f3TDmrN12637@guild.plethora.net> Date: Sun, 29 Apr 2001 08:58:27 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200104291348.f3TDmrN12637@guild.plethora.net> Peter Seebach writes: : In message <20010428231807.G6731@lizzy.bugworks.com>, Jos Backus writes: : >Yeah, I am just puzzled as to how this can build at all on other platforms : >(Linux?), unless they don't define this variable. : : Many of them probably have it as an external object, not a #define. I'm : still not sure the code makes any sense. The standards allow for it to be a #define (just like they allow errno to be a #define), so code that uses like the code that was posted earlier is not strictly conforming. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 10:41:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from webmail.netcom.no (webmail.netcom.no [212.45.188.36]) by hub.freebsd.org (Postfix) with ESMTP id 6CBCC37B424 for ; Sun, 29 Apr 2001 10:41:31 -0700 (PDT) (envelope-from sgt@netcom.no) Received: from hal ([212.45.183.80]) by webmail.netcom.no (Netscape Messaging Server 4.15) with ESMTP id GCKEHC00.HPW for ; Sun, 29 Apr 2001 19:41:36 +0200 Date: Sun, 29 Apr 2001 19:40:31 +0200 (CEST) From: Torbjorn Kristoffersen X-Sender: To: FreeBSD-Hackers Subject: Trouble with HPT366 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having trouble with my HighPoint 366 controller. Both the chip and cable works fine in Linux or Windows, but I get an error message from FreeBSD 4.3-RC2 that says "DMA limited to UDMA33, Non-ATA66 compliant cable." Here is my dmesg output with a kernel verbosely booted. I have carefully erased a few unimportant lines, to make it shorter and more readable. I'd appreciate help/advice on this. I've been reading a bit through /sys/dev/ata/* and what causes the error _message_ is that "ATA_PARAM(scp, device)->cblid" returns zero (ata-dma.c:105). cblid lies in struct ata_params. But I'm not sure what to do with this. Torbjorn Kristoffersen sgt@netcom.no PS: I've had this problem with the predecessors of FreeBSD as well. ====== Start of dmesg output ====== Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-RC2 #2: Tue Apr 10 00:32:38 CEST 2001 sgt@hal.netforce.no:/usr/src/sys/compile/HAL Calibrating clock(s) ... TSC clock: 701682801 Hz, i8254 clock: 1193338 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 701593899 Hz CPU: Pentium III/Pentium III Xeon/Celeron (701.59-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 268435456 (262144K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00382000 - 0x0fff7fff, 264724480 bytes (64630 pages) avail memory = 257200128 (251172K bytes) bios32: Found BIOS32 Service Directory header at 0xc00faf90 bios32: Entry = 0xfb410 (c00fb410) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb440 pnpbios: Found PnP BIOS data at 0xc00fc010 pnpbios: Entry = f0000:c038 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc035c000. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard found-> vendor=0x8086, dev=0x7190, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base e4000000, size 25 found-> vendor=0x8086, dev=0x7191, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000f000, size 4 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=255 map[20]: type 1, range 32, base 0000d000, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 00005000, size 4 found-> vendor=0x10ec, dev=0x8029, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 0000d400, size 5 found-> vendor=0x1103, dev=0x0004, revid=0x01 class=01-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 0000d800, size 3 map[14]: type 1, range 32, base 0000dc00, size 2 map[20]: type 1, range 32, base 0000e000, size 8 found-> vendor=0x1103, dev=0x0004, revid=0x01 class=01-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=11 map[10]: type 1, range 32, base 0000e400, size 3 map[14]: type 1, range 32, base 0000e800, size 2 map[20]: type 1, range 32, base 0000ec00, size 8 pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x102b, dev=0x0525, revid=0x04 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base e6000000, size 25 map[14]: type 1, range 32, base e0000000, size 14 map[18]: type 1, range 32, base e1000000, size 23 pci1: on pcib1 pci1: (vendor=0x102b, dev=0x0525) at 0.0 irq 9 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000 ata0: mask=03 status0=50 status1=50 ata0: mask=03 ostat0=50 ostat2=50 ata0-master: ATAPI probe a=00 b=00 ata0-slave: ATAPI probe a=00 b=00 ata0: mask=03 status0=50 status1=50 ata0-master: ATA probe a=01 b=a5 ata0-slave: ATA probe a=01 b=a5 ata0: devices=03 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xf008 ata1: mask=02 status0=ff status1=50 ata1: mask=02 ostat0=ff ostat2=50 ata1-slave: ATAPI probe a=14 b=eb ata1: mask=02 status0=ff status1=00 ata1: devices=08 ata1: at 0x170 irq 15 on atapci0 pci0: (vendor=0x8086, dev=0x7112) at 7.2 chip1: port 0x5000-0x500f at device 7.3 on pci0 ed0: port 0xd400-0xd41f irq 10 at device 13.0 on pci0 bpf: ed0 attached ed0: address 00:50:bf:03:ad:a2, type NE2000 (16 bit) atapci1: port 0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 11 at device 19.0 on pci0 ata2: iobase=0xd800 altiobase=0xdc02 bmaddr=0xe000 ata2: mask=03 status0=50 status1=30 ata2: mask=03 ostat0=50 ostat2=30 ata2-master: ATAPI probe a=00 b=00 ata2-slave: ATAPI probe a=30 b=30 ata2: mask=03 status0=50 status1=30 ata2-master: ATA probe a=01 b=a5 ata2-slave: ATA probe a=a5 b=25 ata2: devices=01 ata2: at 0xd800 on atapci1 atapci2: port 0xec00-0xecff,0xe800-0xe803,0xe400-0xe407 irq 11 at device 19.1 on pci0 ata-: ata2 exists, using next available unit number ata3: iobase=0xe400 altiobase=0xe802 bmaddr=0xec00 ata3: mask=03 status0=20 status1=30 ata3: mask=03 ostat0=20 ostat2=30 ata3-master: ATAPI probe a=20 b=20 ata3-slave: ATAPI probe a=30 b=30 ata3: mask=03 status0=20 status1=30 ata3-master: ATA probe a=25 b=25 ata3-slave: ATA probe a=25 b=25 ata3: devices=00 ata3: at 0xe400 on atapci2 using shared irq11. ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number Trying Read_Port at 203 Trying Read_Port at 243 CTL0045: start dependant CTL0045: adding irq mask 0x20 CTL0045: adding dma mask 0x2 CTL0045: adding dma mask 0x20 CTL0045: adding io range 0x220-0x22f, size=0x10, align=0x1 CTL0045: adding io range 0x330-0x331, size=0x2, align=0x1 CTL0045: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0045: start dependant CTL0045: adding irq mask 0x6a0 CTL0045: adding dma mask 0xb CTL0045: adding dma mask 0xe0 CTL0045: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0045: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0045: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0045: start dependant CTL0045: adding irq mask 0x6a0 CTL0045: adding dma mask 0xb CTL0045: adding dma mask 0xe0 CTL0045: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0045: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0045: start dependant CTL0045: adding irq mask 0x6a0 CTL0045: adding dma mask 0xb CTL0045: adding dma mask 0xe0 CTL0045: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0045: start dependant CTL0045: adding irq mask 0x6a0 CTL0045: adding dma mask 0xb CTL0045: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0045: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0045: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0045: start dependant CTL0045: adding irq mask 0x6a0 CTL0045: adding dma mask 0xb CTL0045: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0045: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0045: start dependant CTL0045: adding irq mask 0x6a0 CTL0045: adding dma mask 0xb CTL0045: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0045: start dependant isa0: too many dependant configs (8) CTL7002: start dependant CTL7002: adding io range 0x200-0x207, size=0x8, align=0x1 CTL7002: start dependant CTL7002: adding io range 0x200-0x20f, size=0x8, align=0x8 CTL7002: end dependant CTL0022: start dependant CTL0022: adding io range 0x620-0x623, size=0x4, align=0x1 CTL0022: start dependant CTL0022: adding io range 0x620-0x683, size=0x4, align=0x20 CTL0022: end dependant isa0: unexpected small tag 14 ex_isa_identify() isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata4 failed to probe at port 0x1f0 irq 14 flags 0xb0ffb0ff on isa0 ata5 failed to probe at port 0x170 irq 15 flags 0xb0ffb0ff on isa0 sbc0 failed to probe at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 isa_probe_children: probing PnP devices BIOS Geometries: 0:030ffe3f 0..783=784 cylinders, 0..254=255 heads, 1..63=63 sectors 1:03fe3f3f 0..1022=1023 cylinders, 0..63=64 heads, 1..63=63 sectors 2:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: lo0 attached bpf: ppp0 attached new masks: bio 68c840, tty 6310ba, net 6714ba ata0-master: success setting UDMA2 on PIIX4 chip Creating DISK ad0 Creating DISK wd0 ad0: ATA-4 disk at ata0-master ad0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 ad0: 6149MB [13328/15/63] at ata0-master UDMA33 ata0-slave: success setting UDMA2 on PIIX4 chip Creating DISK ad1 Creating DISK wd1 ad1: ATA-2 disk at ata0-slave ad1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 ad1: piomode=4 dmamode=2 udmamode=2 cblid=0 ad1: 2014MB [4092/16/63] at ata0-slave UDMA33 ata2-master: DMA limited to UDMA33, non-ATA66 compliant cable ata2-master: success setting UDMA2 on HighPoint chip Creating DISK ad4 Creating DISK wd4 ad4: ATA-4 disk at ata2-master ad4: 19574MB (40088160 sectors), 39770 cyls, 16 heads, 63 S/T, 512 B/S ad4: 16 secs/int, 1 depth queue, UDMA33 ad4: piomode=4 dmamode=2 udmamode=4 cblid=0 HighPoint check1 failed ad4: 19574MB [39770/16/63] at ata2-master UDMA33 ata1-slave: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata1-slave: success setting PIO4 on generic chip acd0: CDROM drive at ata1 as slave acd0: read 5512KB/s (5512KB/s), 256KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm photo disc loaded, unlocked Mounting root from ufs:/dev/ad4s1a ad4s1: type 0xa5, start 63, end = 40082174, size 40082112 : OK start_init: trying /sbin/init ad0s1: type 0x6, start 63, end = 4192964, size 4192902 : OK ad0s2: type 0x5, start 4192965, end = 12594959, size 8401995 : OK ad0s5: type 0xb, start 4193028, end = 12594959, size 8401932 : OK ====== End of dmesg output ====== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 10:48:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (adam042-060.resnet.wisc.edu [146.151.42.60]) by hub.freebsd.org (Postfix) with ESMTP id 6755537B42C for ; Sun, 29 Apr 2001 10:48:10 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 18523 invoked by uid 1000); 29 Apr 2001 17:48:03 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 29 Apr 2001 17:48:03 -0000 Date: Sun, 29 Apr 2001 12:48:03 -0500 (CDT) From: Mike Silbersack To: Torbjorn Kristoffersen Cc: FreeBSD-Hackers Subject: Re: Trouble with HPT366 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Apr 2001, Torbjorn Kristoffersen wrote: > I'm having trouble with my HighPoint 366 controller. Both the chip and > cable works fine in Linux or Windows, but I get an error message from > FreeBSD 4.3-RC2 that says "DMA limited to UDMA33, Non-ATA66 compliant > cable." Well, are you using one of the 80-conductor cables? Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 11:20:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from totem.fix.no (totem.fix.no [213.142.66.130]) by hub.freebsd.org (Postfix) with ESMTP id 2F0C437B423; Sun, 29 Apr 2001 11:20:24 -0700 (PDT) (envelope-from anders@totem.fix.no) Received: by totem.fix.no (Postfix, from userid 1000) id F34253CCF; Sun, 29 Apr 2001 20:20:22 +0200 (CEST) Date: Sun, 29 Apr 2001 20:20:22 +0200 From: Anders Nordby To: Martin Blapp Cc: iedowse@freebsd.org, rwatson@freebsd.org, tmm@freebsd.org, alfred@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Recent RPC changes to -current Message-ID: <20010429202022.A51006@totem.fix.no> References: <20010413145645.P976@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mb@imp.ch on Sat, Apr 14, 2001 at 02:48:36PM +0200 X-Operating-System: FreeBSD 4.1.1-STABLE X-PGP-Key: http://anders.fix.no/pgp/ X-PGP-Key-FingerPrint: 1E0F C53C D8DF 6A8F EAAD 19C5 D12A BC9F 0083 5956 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Sat, Apr 14, 2001 at 02:48:36PM +0200, Martin Blapp wrote: > Can you check if this solves the drac problem in CURRENT ? > Does drac work the way it should ? There were some flags > actived in rpcgen, which shouldn't have been. I also modified > your port a bit to use tirpc code and to not include netdir.h > > http://home.teleport.ch/freebsd/rpcgen.diff DRAC works both as it should both with and without this. The only practical difference I could spot is that the rpc.dracd daemon actually detaches (!) when using a rpcgen program with these patches applied to generate its RPC code. Tested in: FreeBSD current.localnet 5.0-20010420-CURRENT FreeBSD 5.0-20010420-CURRENT #0: Fri Apr 20 15:56:14 GMT 2001 root@usw2.freebsd.org:/usr/src/sys/compile/GENERIC i386 (kern.osreldate: 500018) > http://home.teleport.ch/freebsd/drac.diff I'll use this to make a TI_RPC patch for drac in -current then, instead of using rpcgen -b as the pathces I sent in PR ports/26545 do. Thanks. Cheers, -- Anders. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 12: 1: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 3983137B50C; Sun, 29 Apr 2001 12:00:54 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f3TJ5j800935; Sun, 29 Apr 2001 12:05:46 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104291905.f3TJ5j800935@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Shaun Dwyer Cc: "Patrick S. Gardella" , tdwyer@bigpond.com, freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: LCD driver port (Linux -> FreeBSD) needed for car-mp3 player In-reply-to: Your message of "Sun, 29 Apr 2001 21:34:32 +0800." <3AEC1868.13FA5F62@bigpond.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Apr 2001 12:05:45 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi Patrick, > > > I didn't really explain much about the LCD+Driver... > Basically its a parallel port display that uses the generic Hitachi > HD44780 > chipset. What the driver for linux does is provide a /dev/lcd > that you can address the same as you would /dev/cuaaX for a serial > matrix orbital display. > > The reason I am using the parallel port LCD, is that it cost $80, > as opposed to $400+ for the matrix orbital serial display (I am in > Australia). Look at /usr/share/examples/ppi; you don't need (or want) a kernel driver for this sort of thing. I wrote the ppilcd app to talk to exactly that LCD controller; the electronics involved should be the same as for the Linux interface. If you have any questions, let me know. The code's a bit old, but the ppi interface hasn't changed in the last four years. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 15: 9: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from webmail.netcom.no (webmail.netcom.no [212.45.188.36]) by hub.freebsd.org (Postfix) with ESMTP id 41A3B37B423 for ; Sun, 29 Apr 2001 15:09:02 -0700 (PDT) (envelope-from sgt@netcom.no) Received: from hal ([212.45.183.182]) by webmail.netcom.no (Netscape Messaging Server 4.15) with ESMTP id GCKQUW00.BJH for ; Mon, 30 Apr 2001 00:08:56 +0200 Date: Mon, 30 Apr 2001 00:08:47 +0200 (CEST) From: Torbjorn Kristoffersen X-Sender: To: FreeBSD-Hackers Subject: Re: Trouble with HPT366 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Apr 2001, Mike Silbersack wrote: > > On Sun, 29 Apr 2001, Torbjorn Kristoffersen wrote: > > > I'm having trouble with my HighPoint 366 controller. Both the chip and > > cable works fine in Linux or Windows, but I get an error message from > > FreeBSD 4.3-RC2 that says "DMA limited to UDMA33, Non-ATA66 compliant > > cable." > > Well, are you using one of the 80-conductor cables? > Yes, I'm using the 80-conductor cable I got with the motherboard (ABIT BE6 with HPT366 onboard). Torbjorn Kristoffersen sgt@netcom.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 23:26:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 522BA37B422 for ; Sun, 29 Apr 2001 23:26:07 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.11.3/8.11.3) id f3U6Q5A52505; Mon, 30 Apr 2001 08:26:05 +0200 (CEST) (envelope-from sos) From: Søren Schmidt Message-Id: <200104300626.f3U6Q5A52505@freebsd.dk> Subject: Re: Trouble with HPT366 In-Reply-To: "from Torbjorn Kristoffersen at Apr 30, 2001 00:08:47 am" To: Torbjorn Kristoffersen Date: Mon, 30 Apr 2001 08:26:05 +0200 (CEST) Cc: FreeBSD-Hackers X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Torbjorn Kristoffersen wrote: > On Sun, 29 Apr 2001, Mike Silbersack wrote: > > On Sun, 29 Apr 2001, Torbjorn Kristoffersen wrote: > > > I'm having trouble with my HighPoint 366 controller. Both the chip and > > > cable works fine in Linux or Windows, but I get an error message from > > > FreeBSD 4.3-RC2 that says "DMA limited to UDMA33, Non-ATA66 compliant > > > cable." > > Well, are you using one of the 80-conductor cables? > Yes, I'm using the 80-conductor cable I got with the motherboard > (ABIT BE6 with HPT366 onboard). Since the disk claims clbid to be zero, the disk doesn't see the cable as being a valid 80pin one, have you tried another cable ? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 23:30: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (adam042-060.resnet.wisc.edu [146.151.42.60]) by hub.freebsd.org (Postfix) with ESMTP id 43A7837B422 for ; Sun, 29 Apr 2001 23:29:58 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 19265 invoked by uid 1000); 30 Apr 2001 06:29:56 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Apr 2001 06:29:56 -0000 Date: Mon, 30 Apr 2001 01:29:56 -0500 (CDT) From: Mike Silbersack To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: Torbjorn Kristoffersen , FreeBSD-Hackers Subject: Re: Trouble with HPT366 In-Reply-To: <200104300626.f3U6Q5A52505@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Apr 2001, S=F8ren Schmidt wrote: > It seems Torbjorn Kristoffersen wrote: > > On Sun, 29 Apr 2001, Mike Silbersack wrote: > > > On Sun, 29 Apr 2001, Torbjorn Kristoffersen wrote: > > > > I'm having trouble with my HighPoint 366 controller. Both the chip = and > > > > cable works fine in Linux or Windows, but I get an error message fr= om > > > > FreeBSD 4.3-RC2 that says "DMA limited to UDMA33, Non-ATA66 complia= nt > > > > cable." > > > Well, are you using one of the 80-conductor cables? > > Yes, I'm using the 80-conductor cable I got with the motherboard > > (ABIT BE6 with HPT366 onboard). > > Since the disk claims clbid to be zero, the disk doesn't see the cable > as being a valid 80pin one, have you tried another cable ? > > -S=F8ren I've had a further thought on this. How does the drive recognize the cable? Is it due to a notch cut out of one of the wires? I mention this because I seem to recall seeing some 80-pin cables with the notch, and some without. (I don't have time to pull apart any boxes and look right now, though.) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 23:30:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta7.pltn13.pbi.net (mta7.pltn13.pbi.net [64.164.98.8]) by hub.freebsd.org (Postfix) with ESMTP id 52AD837B42C for ; Sun, 29 Apr 2001 23:30:14 -0700 (PDT) (envelope-from jazepeda@pacbell.net) Received: from zippy.mybox.zip ([207.214.149.192]) by mta7.pltn13.pbi.net (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0GCL00JL3E211D@mta7.pltn13.pbi.net> for hackers@freebsd.org; Sun, 29 Apr 2001 23:30:04 -0700 (PDT) Received: by zippy.mybox.zip (Postfix, from userid 1000) id 8FB08182C; Sun, 29 Apr 2001 23:30:00 -0700 (PDT) Date: Sun, 29 Apr 2001 23:30:00 -0700 From: Alex Zepeda Subject: Re: Trouble with HPT366 In-reply-to: ; from sgt@netcom.no on Mon, Apr 30, 2001 at 12:08:47AM +0200 To: Torbjorn Kristoffersen Cc: hackers@freebsd.org Message-id: <20010429233000.A87067@zippy.mybox.zip> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 30, 2001 at 12:08:47AM +0200, Torbjorn Kristoffersen wrote: > Yes, I'm using the 80-conductor cable I got with the motherboard > (ABIT BE6 with HPT366 onboard). Is the cable connected properly? The blue connector must be on the motherboard end.. Are you sure Leenuchs is using ATA66 speeds? Anyhow, I'd be careful with the HPT366, I've had nothing but trouble with my HPT366 based card. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 23:33:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 66EB537B422 for ; Sun, 29 Apr 2001 23:33:23 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.11.3/8.11.3) id f3U6XIb54203; Mon, 30 Apr 2001 08:33:18 +0200 (CEST) (envelope-from sos) From: Søren Schmidt Message-Id: <200104300633.f3U6XIb54203@freebsd.dk> Subject: Re: Trouble with HPT366 In-Reply-To: <20010429233000.A87067@zippy.mybox.zip> "from Alex Zepeda at Apr 29, 2001 11:30:00 pm" To: Alex Zepeda Date: Mon, 30 Apr 2001 08:33:18 +0200 (CEST) Cc: Torbjorn Kristoffersen , hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alex Zepeda wrote: > On Mon, Apr 30, 2001 at 12:08:47AM +0200, Torbjorn Kristoffersen wrote: > > > Yes, I'm using the 80-conductor cable I got with the motherboard > > (ABIT BE6 with HPT366 onboard). > > Is the cable connected properly? The blue connector must be on the > motherboard end.. Are you sure Leenuchs is using ATA66 speeds? Anyhow, > I'd be careful with the HPT366, I've had nothing but trouble with my > HPT366 based card. Yup, orientation is important :) And Yes, the HPT366 has issues with fast disks, and I havn't been able to find a workaround for that yet, sadly.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Apr 29 23:48:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailin5.bigpond.com (juicer02.bigpond.com [139.134.6.78]) by hub.freebsd.org (Postfix) with ESMTP id D4DE337B424; Sun, 29 Apr 2001 23:48:04 -0700 (PDT) (envelope-from sldwyer@bigpond.com) Received: from bigpond.com ([139.134.4.52]) by mailin5.bigpond.com (Netscape Messaging Server 4.15) with SMTP id GCLF3Y00.1K1; Mon, 30 Apr 2001 16:52:46 +1000 Received: from WEBH-T-008-p-156-167.tmns.net.au ([203.54.156.167]) by mail5.bigpond.com (Claudes-Zippy-MailRouter V2.9c 9/3458137); 30 Apr 2001 16:48:08 Message-ID: <3AED0B5F.CF181D5F@bigpond.com> Date: Mon, 30 Apr 2001 14:51:11 +0800 From: Shaun Dwyer X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: "Patrick S. Gardella" , tdwyer@bigpond.com, freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: LCD driver port (Linux -> FreeBSD) needed for car-mp3 player References: <200104291905.f3TJ5j800935@mass.dis.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Mike, The software I am using in Linux (cajun - cajun.sourceforge.net) requires a serial display to work. What the linux driver does is emulate the serial display, and provides a /dev/lcd. As I am not a perl coder, I cannot modify Cajun to use the app you wrote, And as I am not a C coder, I cannot modify what you wrote to behave like the linux driver. Unless there is something already around that can take input in the way /dev/cuaaX does, and then pump the data into what you wrote, I think that the easiest way to do this is to make a driver for FreeBSD that behaves exactly the way that the Linux driver does. Shaun Mike Smith wrote: > > > Hi Patrick, > > > > > > I didn't really explain much about the LCD+Driver... > > Basically its a parallel port display that uses the generic Hitachi > > HD44780 > > chipset. What the driver for linux does is provide a /dev/lcd > > that you can address the same as you would /dev/cuaaX for a serial > > matrix orbital display. > > > > The reason I am using the parallel port LCD, is that it cost $80, > > as opposed to $400+ for the matrix orbital serial display (I am in > > Australia). > > Look at /usr/share/examples/ppi; you don't need (or want) a kernel driver > for this sort of thing. I wrote the ppilcd app to talk to exactly that > LCD controller; the electronics involved should be the same as for the > Linux interface. > > If you have any questions, let me know. The code's a bit old, but the > ppi interface hasn't changed in the last four years. > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E -- ---------------------- Shaun Dwyer sldwyer@bigpond.com ---------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 0:23:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from db.wireless.net (adsl-gte-la-216-86-194-70.mminternet.com [216.86.194.70]) by hub.freebsd.org (Postfix) with ESMTP id CA64737B422; Mon, 30 Apr 2001 00:23:29 -0700 (PDT) (envelope-from dbutter@wireless.net) Received: from dbm.wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with SMTP id AAA70411; Mon, 30 Apr 2001 00:22:34 -0700 (PDT) (envelope-from dbutter@wireless.net) Content-Type: text/plain; charset="iso-8859-15" From: Devin Butterfield To: Shaun Dwyer , Mike Smith Subject: Re: LCD driver port (Linux -> FreeBSD) needed for car-mp3 player Date: Mon, 30 Apr 2001 00:24:40 -0700 X-Mailer: KMail [version 1.2] Cc: "Patrick S. Gardella" , tdwyer@bigpond.com, freebsd-hackers@FreeBSD.ORG References: <200104291905.f3TJ5j800935@mass.dis.org> <3AED0B5F.CF181D5F@bigpond.com> In-Reply-To: <3AED0B5F.CF181D5F@bigpond.com> MIME-Version: 1.0 Message-Id: <01043000244000.01065@dbm.wireless.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday 29 April 2001 11:51, Shaun Dwyer wrote: > Hi Mike, > > The software I am using in Linux (cajun - cajun.sourceforge.net) > requires > a serial display to work. What the linux driver does is emulate the > serial > display, and provides a /dev/lcd. > > As I am not a perl coder, I cannot modify Cajun to use the app you > wrote, > And as I am not a C coder, I cannot modify what you wrote to behave like > the linux driver. > > > Unless there is something already around that can take input in the way > /dev/cuaaX > does, and then pump the data into what you wrote, I think that the > easiest way > to do this is to make a driver for FreeBSD that behaves exactly the way > that the Linux driver does. Writing a driver is not the easiest way to go and if you don't know C then you can't write the driver. I think what your getting at (IIRC from your original post) is that you are asking someone to volunteer to write it for you. This is not a small request as writing kernel drivers is not a trivial task, can be very time consuming, and most people don't have time. Anyway, this looks like a pretty cool project and hopefully someone with some extra time on their hands will take up the task. Alternatively, you could learn C, learn how to write FreeBSD device drivers by reading the source code of existing drivers, and then write it yourself. :) I'm sure folks on this list (including myself) would be willing to answer any questions you had. Good luck! -- Regards, Devin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 2:12:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id A680737B424; Mon, 30 Apr 2001 02:12:27 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f3U9HL808411; Mon, 30 Apr 2001 02:17:22 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104300917.f3U9HL808411@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Shaun Dwyer Cc: "Patrick S. Gardella" , tdwyer@bigpond.com, freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: LCD driver port (Linux -> FreeBSD) needed for car-mp3 player In-reply-to: Your message of "Mon, 30 Apr 2001 14:51:11 +0800." <3AED0B5F.CF181D5F@bigpond.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Apr 2001 02:17:21 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The software I am using in Linux (cajun - cajun.sourceforge.net) > requires a serial display to work. What the linux driver does is emulate > the serial display, and provides a /dev/lcd. > > As I am not a perl coder, I cannot modify Cajun to use the app you > wrote, And as I am not a C coder, I cannot modify what you wrote to behave > like the linux driver. > > Unless there is something already around that can take input in the way > /dev/cuaaX does, and then pump the data into what you wrote, I think that > the easiest way to do this is to make a driver for FreeBSD that behaves > exactly the way that the Linux driver does. Er, you're no great shakes at logic, either. "I can't fix the app, so someone else should write a driver" is what you've just said. I'll give you the benefit of the doubt, and simply tell you that fixing the app will be a damn sight easier than writing this driver you're talking about. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 2:21:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rafiu.psi-domain.co.uk (rafiu.psi-domain.co.uk [212.87.84.199]) by hub.freebsd.org (Postfix) with ESMTP id 061EE37B424 for ; Mon, 30 Apr 2001 02:21:08 -0700 (PDT) (envelope-from heckfordj@psi-domain.co.uk) Received: from smtp.psi-domain.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by rafiu.psi-domain.co.uk (8.11.3/8.11.3) with SMTP id f3U9HEX48059 for ; Mon, 30 Apr 2001 10:17:14 +0100 (BST) Date: Mon, 30 Apr 2001 11:19:29 +0100 From: Jamie Heckford To: freebsd-hackers@freebsd.org Subject: Re: LCD driver port (Linux -> FreeBSD) needed for car-mp3 player Message-ID: <20010430111929.M44631@storm.psi-domain.co.uk> Reply-To: heckfordj@psi-domain.co.uk References: <3AED0B5F.CF181D5F@bigpond.com> <200104300917.f3U9HL808411@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: <200104300917.f3U9HL808411@mass.dis.org>; from msmith@FreeBSD.ORG on Mon, Apr 30, 2001 at 10:17:21 +0100 X-Mailer: Balsa 1.1.1 Lines: 79 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Been following this thread, and thought I would poke my nose in. We are in the process of writing a driver (heavily based on LCDProc - http://lcdproc.omnipotent.net) and the source for this seems to be pretty easy to work with. The panel and driver board we are using hooks into a serial port, I take it this is what you are looking for? We will of course be releasing the driver BSD style license when its finished :) Just letting you know, check the LCDproc code, it is pretty solid. Jamie On 2001.04.30 10:17 Mike Smith wrote: > > > > The software I am using in Linux (cajun - cajun.sourceforge.net) > > requires a serial display to work. What the linux driver does is > emulate > > the serial display, and provides a /dev/lcd. > > > > As I am not a perl coder, I cannot modify Cajun to use the app you > > wrote, And as I am not a C coder, I cannot modify what you wrote to > behave > > like the linux driver. > > > > Unless there is something already around that can take input in the way > > /dev/cuaaX does, and then pump the data into what you wrote, I think > that > > the easiest way to do this is to make a driver for FreeBSD that behaves > > exactly the way that the Linux driver does. > > Er, you're no great shakes at logic, either. > > "I can't fix the app, so someone else should write a driver" is what > you've just said. > > I'll give you the benefit of the doubt, and simply tell you that fixing > the app will be a damn sight easier than writing this driver you're > talking about. > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > -- Jamie Heckford Network Operations Manager Psi-Domain - Innovative Linux Solutions. Ask Us How. FreeBSD - The power to serve Join our mailing list and stay informed by emailing majordomo@psi-domain.co.uk with the line: subscribe collective ===================================== email: heckfordj@psi-domain.co.uk web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile: +44 (0)7866 724 224 ===================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 6:16:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cslab.csie.ntu.edu.tw (cslab.csie.ntu.edu.tw [140.112.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 0BF6637B422 for ; Mon, 30 Apr 2001 06:16:47 -0700 (PDT) (envelope-from r88074@csie.ntu.edu.tw) Received: from hornets (hornets.csie.ntu.edu.tw [140.112.30.134]) by cslab.csie.ntu.edu.tw (8.9.3/8.9.3) with SMTP id VAA24962 for ; Mon, 30 Apr 2001 21:16:33 +0800 (CST) Message-Id: <200104301316.VAA24962@cslab.csie.ntu.edu.tw> From: "ªL­^¶W" To: "Freebsd-Hackers" Subject: write() vs aio_write() Date: Mon, 30 Apr 2001 21:15:25 +0800 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear all: Because write() use buffer cache, I want to know whether aio_write() is better than write() in FreeBSD 4.1 . Is aio_write() outperform write() ? Or any related performance comparison between the two system call ???? Thanks in advance Richard_Lin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 6:32: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 7C1FD37B43C for ; Mon, 30 Apr 2001 06:32:01 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3UDV1p11018; Mon, 30 Apr 2001 06:31:01 -0700 (PDT) Date: Mon, 30 Apr 2001 06:31:01 -0700 From: Alfred Perlstein To: =?iso-8859-1?Q?=AAL=AD^=B6W?= Cc: Freebsd-Hackers Subject: Re: write() vs aio_write() Message-ID: <20010430063101.Z18676@fw.wintelcom.net> References: <200104301316.VAA24962@cslab.csie.ntu.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200104301316.VAA24962@cslab.csie.ntu.edu.tw>; from r88074@csie.ntu.edu.tw on Mon, Apr 30, 2001 at 09:15:25PM +0800 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * ªL­^¶W [010430 06:17] wrote: > Dear all: > > Because write() use buffer cache, I want to know whether aio_write() is > better than write() in FreeBSD 4.1 . Is aio_write() > > outperform write() ? Or any related performance comparison between the two > system call ???? aio_write is for doing async aio. meaning you can ask the kernel to move data for you from a memory location to a file descriptor while you proceed on with doing other work. if you don't have any other work to do then aio is probably just going to slow you down. -- -Alfred Perlstein - [alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 6:47:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cslab.csie.ntu.edu.tw (cslab.csie.ntu.edu.tw [140.112.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 1842637B422 for ; Mon, 30 Apr 2001 06:46:59 -0700 (PDT) (envelope-from r88074@csie.ntu.edu.tw) Received: from hornets (hornets.csie.ntu.edu.tw [140.112.30.134]) by cslab.csie.ntu.edu.tw (8.9.3/8.9.3) with SMTP id VAA25665; Mon, 30 Apr 2001 21:40:53 +0800 (CST) Message-Id: <200104301340.VAA25665@cslab.csie.ntu.edu.tw> From: "ªL­^¶W" To: "Alfred Perlstein" Cc: "Freebsd-Hackers" Subject: RE: write() vs aio_write() Date: Mon, 30 Apr 2001 21:39:43 +0800 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20010430063101.Z18676@fw.wintelcom.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Alfred Perlstein Sent: Monday, April 30, 2001 9:31 PM To: ªL­^¶W Cc: Freebsd-Hackers Subject: Re: write() vs aio_write() * ªL­^¶W [010430 06:17] wrote: > Dear all: > > Because write() use buffer cache, I want to know whether aio_write() is > better than write() in FreeBSD 4.1 . Is aio_write() > > outperform write() ? Or any related performance comparison between the two > system call ???? aio_write is for doing async aio. meaning you can ask the kernel to move data for you from a memory location to a file descriptor while you proceed on with doing other work. if you don't have any other work to do then aio is probably just going to slow you down. Now I am trying to implement a Proxy Server. I want to use asynchrounos I/O so that the Proxy Server can do other things than blocking on I/O operation. Is it a good idea to use aio_write or aio_read on Proxy Server ??? Thanks a lot Richard_Lin -- -Alfred Perlstein - [alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 6:49:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E93FB37B422 for ; Mon, 30 Apr 2001 06:49:19 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3UDn3311496; Mon, 30 Apr 2001 06:49:03 -0700 (PDT) Date: Mon, 30 Apr 2001 06:49:03 -0700 From: Alfred Perlstein To: =?iso-8859-1?Q?=AAL=AD^=B6W?= Cc: Freebsd-Hackers Subject: Re: write() vs aio_write() Message-ID: <20010430064903.B18676@fw.wintelcom.net> References: <20010430063101.Z18676@fw.wintelcom.net> <200104301340.VAA25665@cslab.csie.ntu.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200104301340.VAA25665@cslab.csie.ntu.edu.tw>; from r88074@csie.ntu.edu.tw on Mon, Apr 30, 2001 at 09:39:43PM +0800 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * ªL­^¶W [010430 06:47] wrote: > > * ªL­^¶W [010430 06:17] wrote: > > Dear all: > > > > Because write() use buffer cache, I want to know whether aio_write() > is > > better than write() in FreeBSD 4.1 . Is aio_write() > > > > outperform write() ? Or any related performance comparison between the > two > > system call ???? > > aio_write is for doing async aio. meaning you can ask the kernel to > move data for you from a memory location to a file descriptor while > you proceed on with doing other work. if you don't have any other > work to do then aio is probably just going to slow you down. > > > Now I am trying to implement a Proxy Server. I want to use asynchrounos I/O > so that > the Proxy Server can do other things than blocking on I/O operation. Is it a > good idea to > use aio_write or aio_read on Proxy Server ??? It's a good idea to use it for disk IO, probably not a good idea for network IO. -- -Alfred Perlstein - [alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 8: 0:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ewey.excite.com (ewey-rwcmta.excite.com [198.3.99.191]) by hub.freebsd.org (Postfix) with ESMTP id 1AA4537B423 for ; Mon, 30 Apr 2001 08:00:20 -0700 (PDT) (envelope-from john_wilson100@excite.com) Received: from almond.excite.com ([199.172.148.82]) by ewey.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20010430150019.YTAR20552.ewey.excite.com@almond.excite.com> for ; Mon, 30 Apr 2001 08:00:19 -0700 Message-ID: <12354766.988642819102.JavaMail.imail@almond.excite.com> Date: Mon, 30 Apr 2001 08:00:18 -0700 (PDT) From: John Wilson To: freebsd-hackers@freebsd.org Subject: ipfw routing/netmask problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 192.116.157.233 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to set up a FreeBSD firewall for ~100 PCs and ~10 servers, and I'm having some trouble with routing/netmasks. I have 30 IP addresses assigned to me by my ISP, for the sake of this example let's say I've got 90.91.92.0/27. The FreeBSD box has 2 interface cards, fxp0 and fxp1, fxp0 connected to the router, fxp1 to the ethernet switch. The router is 90.91.92.1, fxp0 is 90.91.92.2, netmask 255.255.255.252 (broadcast 90.91.92.3) fxp1 is bound to several IPs, 192.168.1.254 and 192.168.2.254 for two different types of NAT clients, and 90.91.92.4 for the DMZ. The intention is that NAT clients use 192.168.1.254 (or 192.168.2.254) as their default gateway, and DMZ clients use 90.91.92.4. The question is how to choose a netmask for fxp1 that would exclude the default gateway (90.91.92.1), so the machine would route via fxp0. Unfortunately, when I choose a netmask such as 255.255.255.227 (11100011), I'm left with only 6 IPs for the DMZ: 90.91.92.8 (binary 1000) 90.91.92.12 (binary 1100) 90.91.92.16 (binary 10000) 90.91.92.20 (binary 10100) 90.91.92.24 (binary 11000) 90.91.92.28 (binary 11100) This seems like a huge waste of IPs. If I choose any other mask, the machine refuses to route via fxp0, because it thinks the default gateway is accessible via fxp1. Is there a way to save IPs (I need at least 12 DMZ IPs), while achieving the same goal? Thanks John Wilson _______________________________________________________ Send a cool gift with your E-Card http://www.bluemountain.com/giftcenter/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 8:21:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cody.jharris.com (cody.jharris.com [205.238.128.83]) by hub.freebsd.org (Postfix) with ESMTP id DD96F37B43C for ; Mon, 30 Apr 2001 08:21:31 -0700 (PDT) (envelope-from nick@rogness.net) Received: from localhost (nick@localhost) by cody.jharris.com (8.11.1/8.9.3) with ESMTP id f3UGVF278087; Mon, 30 Apr 2001 11:31:15 -0500 (CDT) (envelope-from nick@rogness.net) Date: Mon, 30 Apr 2001 11:31:15 -0500 (CDT) From: Nick Rogness X-Sender: nick@cody.jharris.com To: John Wilson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ipfw routing/netmask problem In-Reply-To: <12354766.988642819102.JavaMail.imail@almond.excite.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Apr 2001, John Wilson wrote: This probably belongs on freebsd-net or freebsd-questions. > > I have 30 IP addresses assigned to me by my ISP, for the sake of this > example let's say I've got 90.91.92.0/27. The FreeBSD box has 2 > interface cards, fxp0 and fxp1, fxp0 connected to the router, fxp1 to > the ethernet switch. OK. > > The router is 90.91.92.1, fxp0 is 90.91.92.2, netmask 255.255.255.252 > (broadcast 90.91.92.3) > Is the netmask on the router set as a /30 as well? > fxp1 is bound to several IPs, 192.168.1.254 and 192.168.2.254 for two > different types of NAT clients, and 90.91.92.4 for the DMZ. Define "2 different types of NAT clients". Your DMZ is not on a seperate network of your private network? By doing that you are getting rid of the whole concept of having a DMZ. ALso, run private address space on the DMZ OR Set the address of the DMZ to be 90.91.92.17/28...see below for more details. > > The intention is that NAT clients use 192.168.1.254 (or 192.168.2.254) > as their default gateway, and DMZ clients use 90.91.92.4. > > The question is how to choose a netmask for fxp1 that would exclude > the default gateway (90.91.92.1), so the machine would route via fxp0. > > Is there a way to save IPs (I need at least 12 DMZ IPs), while > achieving the same goal? You have 2 options here. 1) Setup proxy arp on your outside interface. Binding the whole /27 address range (with exception of the router's IP) to your BSD machine. Make natd translations accordingly. 2) Setup your DMZ using 90.91.92.16/28 IP range which gives you enough IP's to play with, and leaves the 90.91.92.4/30 and 90.91.92.8/29 subnet's to play with. Add the routes in the router to route the subnets to your BSD machine's IP. Make natd translations accordingly if you decide to run private address space for your DMZ, if not no additional work needs to be done. Nick Rogness - Keep on Routing in a Free World... "FreeBSD: The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 9: 4:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id ABC0D37B422 for ; Mon, 30 Apr 2001 09:04:14 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 56249 invoked by uid 1001); 30 Apr 2001 16:04:12 +0000 (GMT) To: john_wilson100@excite.com Cc: freebsd-hackers@freebsd.org Subject: Re: ipfw routing/netmask problem From: sthaug@nethelp.no In-Reply-To: Your message of "Mon, 30 Apr 2001 08:00:18 -0700 (PDT)" References: <12354766.988642819102.JavaMail.imail@almond.excite.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 30 Apr 2001 18:04:12 +0200 Message-ID: <56247.988646652@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Unfortunately, when I choose a netmask such as 255.255.255.227 (11100011), > I'm > left with only 6 IPs for the DMZ: Netmasks must be contiguous, which means that 255.255.255.227 is an invalid netmask. (This is a CIDR requirement.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 9:24:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from webmail.netcom.no (webmail.netcom.no [212.45.188.36]) by hub.freebsd.org (Postfix) with ESMTP id B315A37B509 for ; Mon, 30 Apr 2001 09:24:37 -0700 (PDT) (envelope-from sgt@netcom.no) Received: from hal ([212.45.183.23]) by webmail.netcom.no (Netscape Messaging Server 4.15) with ESMTP id GCM5LD00.5ZA; Mon, 30 Apr 2001 18:24:49 +0200 Date: Mon, 30 Apr 2001 18:24:35 +0200 (CEST) From: Torbjorn Kristoffersen X-Sender: To: Alex Zepeda Cc: Subject: Re: Trouble with HPT366 In-Reply-To: <20010429233000.A87067@zippy.mybox.zip> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Apr 2001, Alex Zepeda wrote: > On Mon, Apr 30, 2001 at 12:08:47AM +0200, Torbjorn Kristoffersen wrote: > > > Yes, I'm using the 80-conductor cable I got with the motherboard > > (ABIT BE6 with HPT366 onboard). > > Is the cable connected properly? The blue connector must be on the > motherboard end.. Are you sure Leenuchs is using ATA66 speeds? Anyhow, > I'd be careful with the HPT366, I've had nothing but trouble with my > HPT366 based card. I think Leenuchs used ATA66 speeds, although I'm not sure, since it's a long time since I had it installed on my computer. Yeah, the cable is connected properly. But I'll try to get another cable (w/ or without the "notch"?) and test it further. Did you only have problems with the HPT366 using ATA66 or even when using ATA33 drives? It works perfectly here in ATA33 mode, except for the speed. Cheers, Torbjorn Kristoffersen sgt@netcom.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 10: 5: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id D06B837B422 for ; Mon, 30 Apr 2001 10:04:57 -0700 (PDT) (envelope-from nsouch@alcove.fr) Received: from koka.alcove-fr ([10.16.110.26] helo=koka.alcove-int ident=mail) by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian)) id 14uH6V-0007MR-00; Mon, 30 Apr 2001 19:04:55 +0200 Received: from nsouch by koka.alcove-int with local (Exim 3.12 #1 (Debian)) id 14uH6U-0000Sk-00; Mon, 30 Apr 2001 19:04:54 +0200 Date: Mon, 30 Apr 2001 19:04:54 +0200 From: Nicolas Souchu To: Alex Cc: freebsd-hackers@freebsd.org Subject: Re: Is it ok to compile a device driver as a module though no load_function is declared in DRIVER_MODULE()? Message-ID: <20010430190454.A1750@koka.alcove-fr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i In-Reply-To: ; from d_f0rce@gmx.de on Mon, Apr 16, 2001 at 03:42:34PM +0200 Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Ecom?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 16, 2001 at 03:42:34PM +0200, Alex wrote: > Hi, > > i've got a little question about device drivers for FreeBSD. > > I'm testing my device driver by compiling it as a module and > kldloading it. But as I don't want to use it as a module in the > future I declared DRIVER_MODULE(..) as follows: > > DRIVER_MODULE( ir, isa, ir_isa_driver, ir_devclass, 0, 0); > > As I read on deamonnews that one has to declare a load_function > to use a driver as a KLD I'm not sure if the above DRIVER_MODULE() > is valid for testing. You don't need the load_function with the DRIVER_MODULE declaration. The entry points for you module are probe and identify then attach and detach. That's all. -- Nicolas.Souchu@fr.alcove.com Alcôve - Open Source Software Engineer - http://www.alcove.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 10: 5:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ewey.excite.com (ewey-rwcmta.excite.com [198.3.99.191]) by hub.freebsd.org (Postfix) with ESMTP id 52F2537B422 for ; Mon, 30 Apr 2001 10:05:53 -0700 (PDT) (envelope-from john_wilson100@excite.com) Received: from almond.excite.com ([199.172.148.82]) by ewey.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20010430170552.ZSXT20552.ewey.excite.com@almond.excite.com>; Mon, 30 Apr 2001 10:05:52 -0700 Message-ID: <17607983.988650352302.JavaMail.imail@almond.excite.com> Date: Mon, 30 Apr 2001 10:05:51 -0700 (PDT) From: John Wilson To: Nick Rogness Subject: Re: ipfw routing/netmask problem Cc: freebsd-hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 192.116.157.233 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Nick, Thanks for your prompt reply. > On Mon, 30 Apr 2001, John Wilson wrote: > > > I have 30 IP addresses assigned to me by my ISP, for the sake of this > > example let's say I've got 90.91.92.0/27. The FreeBSD box has 2 > > interface cards, fxp0 and fxp1, fxp0 connected to the router, fxp1 to > > the ethernet switch. > > OK. > > > > > The router is 90.91.92.1, fxp0 is 90.91.92.2, netmask 255.255.255.252 > > (broadcast 90.91.92.3) > > > > Is the netmask on the router set as a /30 as well? No, the router routes everything from 90.91.92.0/27 to the machine's exposed interface (90.91.92.2). > > fxp1 is bound to several IPs, 192.168.1.254 and 192.168.2.254 for two > > different types of NAT clients, and 90.91.92.4 for the DMZ. > > Define "2 different types of NAT clients". Your DMZ is not on a > seperate network of your private network? By doing that you are > getting rid of the whole concept of having a DMZ. Two different companies sharing the line. It's easier to use two different unregistered subnets for NAT clients (bandwidth accounting, etc.), although both are aliased to appear from the exposed interface (90.91.92.2) I don't see a problem with DMZ being on the same network with everyone else, other than that people can steal routable IPs, but then the firewall is configured to block all incoming traffic to 62.90.91.2 (except for established connections), and has specific rules for each allowed DMZ server (allow incoming 25 for mail, 80 for http, etc.), so even if someone steals an extra IP, the firewall will reject them. > ALso, run private address space on the DMZ OR Set the address of > the DMZ to be 90.91.92.17/28...see below for more details. > > > > > The intention is that NAT clients use 192.168.1.254 (or 192.168.2.254) > > as their default gateway, and DMZ clients use 90.91.92.4. > > > > The question is how to choose a netmask for fxp1 that would exclude > > the default gateway (90.91.92.1), so the machine would route via fxp0. > > > > Is there a way to save IPs (I need at least 12 DMZ IPs), while > > achieving the same goal? > > > You have 2 options here. > > 1) Setup proxy arp on your outside interface. Binding the whole > /27 address range (with exception of the router's IP) to your BSD > machine. Make natd translations accordingly. Which option is better? How do I set up proxy arp? > 2) Setup your DMZ using 90.91.92.16/28 IP range which gives you > enough IP's to play with, and leaves the 90.91.92.4/30 and > 90.91.92.8/29 subnet's to play with. Add the routes in the router > to route the subnets to your BSD machine's IP. Make natd > translations accordingly if you decide to run private address > space for your DMZ, if not no additional work needs to be done. This seems like a good solution. Please help me figure out the subnets/routes I need to use. So far, I have this: /---------------------\ | router 90.91.92.1 | \---------------------/ | | /---------------------\ /---------------------\ | fxp0 90.91.92.2/30 |---| fxp1 90.91.92.?/? | \---------------------/ \---------------------/ -| | |----------- | | | /-------\ /-------\ /-------\ | NAT 1 | | NAT 2 | | DMZ | \-------/ \-------/ \-------/ All I gotta do is fill in the missing blanks :) Thanks a lot for your help John Wilson > > > Nick Rogness > - Keep on Routing in a Free World... > "FreeBSD: The Power to Serve!" > > > _______________________________________________________ Send a cool gift with your E-Card http://www.bluemountain.com/giftcenter/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 10:26: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bdr-xcon.matchlogic.com (mail.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 2458A37B423 for ; Mon, 30 Apr 2001 10:26:01 -0700 (PDT) (envelope-from crandall@matchlogic.com) Received: by mail.matchlogic.com with Internet Mail Service (5.5.2653.19) id ; Mon, 30 Apr 2001 11:24:44 -0600 Message-ID: <5FE9B713CCCDD311A03400508B8B30130828EC88@bdr-xcln.corp.matchlogic.com> From: Charles Randall To: 'Alfred Perlstein' , =?iso-8859-1?Q?=AAL=AD=5E?= =?iso-8859-1?Q?=B6W?= Cc: Freebsd-Hackers Subject: RE: write() vs aio_write() Date: Mon, 30 Apr 2001 11:24:42 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Regarding aio_*, Alfred Perlstein writes: >It's a good idea to use it for disk IO, probably not a good >idea for network IO. Could you elaborate? -Charles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 10:36:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cody.jharris.com (cody.jharris.com [205.238.128.83]) by hub.freebsd.org (Postfix) with ESMTP id E195E37B43C for ; Mon, 30 Apr 2001 10:36:24 -0700 (PDT) (envelope-from nick@rogness.net) Received: from localhost (nick@localhost) by cody.jharris.com (8.11.1/8.9.3) with ESMTP id f3UIjPH78708; Mon, 30 Apr 2001 13:45:25 -0500 (CDT) (envelope-from nick@rogness.net) Date: Mon, 30 Apr 2001 13:45:25 -0500 (CDT) From: Nick Rogness X-Sender: nick@cody.jharris.com To: John Wilson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ipfw routing/netmask problem In-Reply-To: <17607983.988650352302.JavaMail.imail@almond.excite.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Apr 2001, John Wilson wrote: Moved to -net. Nick Rogness - Keep on Routing in a Free World... "FreeBSD: The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 11:11:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (adam042-060.resnet.wisc.edu [146.151.42.60]) by hub.freebsd.org (Postfix) with ESMTP id 0795A37B424 for ; Mon, 30 Apr 2001 11:11:10 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 20571 invoked by uid 1000); 30 Apr 2001 18:11:03 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Apr 2001 18:11:03 -0000 Date: Mon, 30 Apr 2001 13:11:03 -0500 (CDT) From: Mike Silbersack To: Charles Randall Cc: 'Alfred Perlstein' , =?iso-8859-1?Q?=AAL=AD=5E?= =?iso-8859-1?Q?=B6W?= , Freebsd-Hackers Subject: RE: write() vs aio_write() In-Reply-To: <5FE9B713CCCDD311A03400508B8B30130828EC88@bdr-xcln.corp.matchlogic.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Apr 2001, Charles Randall wrote: > Regarding aio_*, Alfred Perlstein writes: > >It's a good idea to use it for disk IO, probably not a good > >idea for network IO. > > Could you elaborate? > > -Charles Sockets already support non-blocking IO, and have for a long while. Hence, the socket code is probably more optimized for non-blocking operation than AIO operation. As a plus, using non-blocking socket operations will allow your code to run on any platform; aio isn't as portable. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 11:31:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.coastsight.com (ns1.coastsight.com [208.46.230.17]) by hub.freebsd.org (Postfix) with ESMTP id 3F8CF37B424 for ; Mon, 30 Apr 2001 11:31:23 -0700 (PDT) (envelope-from maillist@coastsight.com) Received: from ns1.coastsight.com ([208.46.230.17]) by ns1.coastsight.com with esmtp (Exim 2.05 #1) id 14uISA-000IPz-00 for freebsd-hackers@freebsd.org; Mon, 30 Apr 2001 11:31:22 -0700 Date: Mon, 30 Apr 2001 11:31:22 -0700 (PDT) From: Rick Duvall To: freebsd-hackers@freebsd.org Subject: Set up loader to boot cd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to make a custom boot CD for FreeBSD. I got it to the point to where the CD will boot, load the kernel, but that's as far as it get's. It does when it get's to the part where it wants to mount the root devicd. It tried to access the floppy drive. So, do I need to vnconfig the boot.flp and put my own custom loader in it or what? I don't want to be puting -C in every time I boot. Also, when I put in -C, the kernel will load, but then can't find the CD device.... Any ideas would be appreciated. Maybe step by step instructions on making a custom bootable live cd would be nice. Thanks. Sincerely, Rick Duvall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 16:41:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 4F17A37B424 for ; Mon, 30 Apr 2001 16:41:15 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3UNf1G82366 for ; Mon, 30 Apr 2001 16:41:01 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 30 Apr 2001 16:40:24 -0700 (PDT) From: John Baldwin To: hackers@FreeBSD.org Subject: Patch to lock LDT and TSS's Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a little patch to try to make accesses to the LDT and TSS of processes on the x86 thread safe. It relies partially on the fact that a TSS or LDT is only modified by the process it is attached to (with the exception of the LDT reference count for LDT's shared among processes). The patch can be found at http://www.FreeBSD.org/~jhb/patches/ldt.patch Please test and review. Thanks. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 16:58:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nero.transactionsite.com (nero.transactionsite.com [203.14.245.6]) by hub.freebsd.org (Postfix) with SMTP id 954CD37B423 for ; Mon, 30 Apr 2001 16:58:46 -0700 (PDT) (envelope-from janm@transactionware.com) Received: (qmail 32811 invoked from network); 30 Apr 2001 23:52:01 -0000 Received: from unknown (HELO haym) (192.168.1.9) by 192.168.1.6 with SMTP; 30 Apr 2001 23:52:01 -0000 Message-ID: <00bd01c0d1d1$106ccdf0$0901a8c0@haym.transactionsite.com> From: "Jan Mikkelsen" To: "Freebsd-Hackers" Subject: Re: write() vs aio_write() Date: Tue, 1 May 2001 09:55:41 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3612.1700 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Silbersack wrote: [ On using aio on disks vs. sockets ] >Sockets already support non-blocking IO, and have for a long while. >Hence, the socket code is probably more optimized for non-blocking >operation than AIO operation. As a plus, using non-blocking socket >operations will allow your code to run on any platform; aio isn't as >portable. I recall reading about possible zero copy I/O using the aio interface. Is anyone thinking about this? And on a related note, how about something like IRIX's O_DIRECT mode for files? I'm sure there are lots of issues, but I'm curious. Jan Mikkelsen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 17:36:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 387EF37B43C for ; Mon, 30 Apr 2001 17:36:30 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f410Zu827779; Mon, 30 Apr 2001 17:35:56 -0700 (PDT) Date: Mon, 30 Apr 2001 17:35:56 -0700 From: "'Alfred Perlstein'" To: Charles Randall Cc: =?iso-8859-1?Q?=AAL=AD^=B6W?= , Freebsd-Hackers Subject: Re: write() vs aio_write() Message-ID: <20010430173555.H18676@fw.wintelcom.net> References: <5FE9B713CCCDD311A03400508B8B30130828EC88@bdr-xcln.corp.matchlogic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5FE9B713CCCDD311A03400508B8B30130828EC88@bdr-xcln.corp.matchlogic.com>; from crandall@matchlogic.com on Mon, Apr 30, 2001 at 11:24:42AM -0600 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Charles Randall [010430 10:26] wrote: > Regarding aio_*, Alfred Perlstein writes: > >It's a good idea to use it for disk IO, probably not a good > >idea for network IO. > > Could you elaborate? Sure. Network IO can be done without blocking (unless you take a fault on the source address of your data). Hence the additional context switching required by aio is not needed. Disk IO probably stands a good chance of blocking your application, if you can offload that blocking to a kernel thread you should be able to continue serving content. -- -Alfred Perlstein - [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 18: 8:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from primo.verat.net (primo.verat.net [217.26.64.130]) by hub.freebsd.org (Postfix) with ESMTP id 687D537B422 for ; Mon, 30 Apr 2001 18:08:21 -0700 (PDT) (envelope-from milunovic@sendmail.ru) Received: from scorpion.cosmos.all.net (ppp65-019.verat.net [217.26.65.19]) by primo.verat.net (x.y.z/1.1.1) with ESMTP id DAA13056 for ; Tue, 1 May 2001 03:08:08 +0200 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by scorpion.cosmos.all.net (8.11.3/8.11.3) with ESMTP id f411Egs00426 for ; Tue, 1 May 2001 03:14:43 +0200 (CEST) Date: Tue, 1 May 2001 03:14:38 +0200 (CEST) From: milunovic X-Sender: milunovic@scorpion.cosmos.all.net To: hackers@freebsd.org Subject: Problem with device rl Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Maybe this isn't right mailing list to send this problem but here it is: I have D-Link DFE-530TX+ and in LINT I read that I should use device rl for this Network card but kernel don't want to find it only output off kernel is : pci0: (vendor=0x1186, dev=0x1300) at 13.0 irq 11 This should be that card.I read all posts from docs.freebsd.org and I couldn't find how to solve this problem. Version of FreeBSD is 4.2 and line in kernel is : device miibus device rl I don't know what should I do.Please help. Vojislav Milunovic milunovic@sendmail.ru -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQEVAwUBOu4OAS3gPLld8IkLAQFgqggAiL0WcP7FDTTYyNI1fqeMS7ozn219wuTF gnGQtAo7g9B/dWf2MIsol9C0Aj+i9TyGX833q/me9GynSkZIwT7Pi8CVoHWfrd6k wFzUKIMI8o7Bta4518FIgrlrLpMSB0q5lioxhwo5irsRaYDTfv1g3JZEegxPyyLD D2A+j9oO90SNNXqcIqCVZ6J9DPrHzxFPhMzQGSdEg2KuYX1XU5lz5JqNUB7lLJIC 99Z6KNSYYFzv+vfDEQnnq0pVpkwIyAMxVJ7DH7tkJ9rYMRRnAnfdjbMQBBq/07tG k/CAc1kAS07Chl5tCUvkiPrOdM2Wfnu37Ai/9IZsN/cBLkItLR4ZvA== =bQV2 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 18:23:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from embryo.jamboa.com (lsanca1-ar7-115-043.biz.dsl.gtei.net [4.35.115.43]) by hub.freebsd.org (Postfix) with ESMTP id 84A7037B422 for ; Mon, 30 Apr 2001 18:23:13 -0700 (PDT) (envelope-from drakFB@drak.com) Received: from [192.168.0.204] (h204.jamboa.org [192.168.0.204]) by embryo.jamboa.com (8.9.3/8.9.3) with ESMTP id SAA58848; Mon, 30 Apr 2001 18:15:21 -0700 (PDT) (envelope-from drakFB@drak.com) Mime-Version: 1.0 X-Sender: (Unverified) Message-Id: In-Reply-To: References: Date: Mon, 30 Apr 2001 18:22:14 -0700 To: milunovic , hackers@FreeBSD.ORG From: Andrew Matheson Subject: Re: Problem with device rl Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vojislav, I had the same problem with FreeBSD 4.3 and a D-Link DFE-530TX+ on a Dell PowerEdge 1400sc. I spent a couple of days on and off fighting with it and couldn't make it work. After going as far as explicitly loading the rl driver in loader.conf (I don't know how I ended up in there, but I was desperate), I finally punted. I returned the D-Link and purchased an Intel InBusiness 10/100 card. It was $49 bucks, but worked right out of the box with the fxp driver--I didn't have to monkey with anything. $30 wouldn't have been worth two days even if in the end the card had worked. It was particularly frustrating because everything I've read in the mailing list archives indicated that it should work. Good Luck, Andrew >-----BEGIN PGP SIGNED MESSAGE----- > >Maybe this isn't right mailing list to send this problem but here it is: >I have D-Link DFE-530TX+ and in LINT I read that I should use device rl >for this Network card but kernel don't want to find it only output off >kernel is : >pci0: (vendor=0x1186, dev=0x1300) at 13.0 irq 11 > >This should be that card.I read all posts from docs.freebsd.org and I >couldn't find how to solve this problem. >Version of FreeBSD is 4.2 and line in kernel is : >device miibus >device rl > >I don't know what should I do.Please help. > >Vojislav Milunovic >milunovic@sendmail.ru > >-----BEGIN PGP SIGNATURE----- >Version: PGPfreeware 5.0i for non-commercial use >Charset: noconv > >iQEVAwUBOu4OAS3gPLld8IkLAQFgqggAiL0WcP7FDTTYyNI1fqeMS7ozn219wuTF >gnGQtAo7g9B/dWf2MIsol9C0Aj+i9TyGX833q/me9GynSkZIwT7Pi8CVoHWfrd6k >wFzUKIMI8o7Bta4518FIgrlrLpMSB0q5lioxhwo5irsRaYDTfv1g3JZEegxPyyLD >D2A+j9oO90SNNXqcIqCVZ6J9DPrHzxFPhMzQGSdEg2KuYX1XU5lz5JqNUB7lLJIC >99Z6KNSYYFzv+vfDEQnnq0pVpkwIyAMxVJ7DH7tkJ9rYMRRnAnfdjbMQBBq/07tG >k/CAc1kAS07Chl5tCUvkiPrOdM2Wfnu37Ai/9IZsN/cBLkItLR4ZvA== >=bQV2 >-----END PGP SIGNATURE----- > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 18:28: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from skippyii.compar.com (mail.compar.com [216.208.38.130]) by hub.freebsd.org (Postfix) with ESMTP id C567237B422 for ; Mon, 30 Apr 2001 18:27:56 -0700 (PDT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (515.POOLDEF.TOR3.enoreo.on.ca [216.26.99.135]) by skippyii.compar.com (8.11.3/8.11.3) with SMTP id f411Wi004088; Mon, 30 Apr 2001 21:32:44 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <00bc01c0d1dd$2241a940$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "milunovic" , References: Subject: Re: Problem with device rl Date: Mon, 30 Apr 2001 21:22:02 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----BEGIN PGP SIGNED MESSAGE----- > > Maybe this isn't right mailing list to send this problem but here it is: > I have D-Link DFE-530TX+ and in LINT I read that I should use device rl > for this Network card but kernel don't want to find it only output off > kernel is : > pci0: (vendor=0x1186, dev=0x1300) at 13.0 irq 11 > > This should be that card.I read all posts from docs.freebsd.org and I > couldn't find how to solve this problem. > Version of FreeBSD is 4.2 and line in kernel is : > device miibus > device rl You're doing the right thing, but sadly the driver hasn't been updated to support the DFE-530TX+ and the DFE-538TX/R cards. If you feel comfortable patching kernel source code, the following patches will add support for the DFE-530TX+ card. [ Thanks to Bill Paul for posting these patches on the -net mailing list last month. ] -- Matt Emmerton *** if_rl.c.orig Sun Mar 25 19:08:34 2001 --- if_rl.c Sun Mar 25 23:14:00 2001 *************** *** 149,154 **** --- 149,156 ---- "Delta Electronics 8139 10/100BaseTX" }, { ADDTRON_VENDORID, ADDTRON_DEVICEID_8139, "Addtron Technolgy 8139 10/100BaseTX" }, + { DLINK_VENDORID, DLINK_DEVICEID_530TXPLUS, + "D-Link DFE-530TX+ 10/100BaseTX" }, { 0, 0, NULL } }; *************** *** 898,904 **** rl_read_eeprom(sc, (caddr_t)&rl_did, RL_EE_PCI_DID, 1, 0); if (rl_did == RT_DEVICEID_8139 || rl_did == ACCTON_DEVICEID_5030 || ! rl_did == DELTA_DEVICEID_8139 || rl_did == ADDTRON_DEVICEID_8139) sc->rl_type = RL_8139; else if (rl_did == RT_DEVICEID_8129) sc->rl_type = RL_8129; --- 903,910 ---- rl_read_eeprom(sc, (caddr_t)&rl_did, RL_EE_PCI_DID, 1, 0); if (rl_did == RT_DEVICEID_8139 || rl_did == ACCTON_DEVICEID_5030 || ! rl_did == DELTA_DEVICEID_8139 || rl_did == ADDTRON_DEVICEID_8139 || ! rl_did == DLINK_DEVICEID_530TXPLUS) sc->rl_type = RL_8139; else if (rl_did == RT_DEVICEID_8129) sc->rl_type = RL_8129; *** if_rlreg.h.orig Sun Mar 25 19:08:34 2001 --- if_rlreg.h Sun Mar 25 19:10:12 2001 *************** *** 433,438 **** --- 433,448 ---- #define ADDTRON_DEVICEID_8139 0x1360 /* + * D-Link vendor ID. + */ + #define DLINK_VENDORID 0x1186 + + /* + * D-Link DFE-530TX+ device ID + */ + #define DLINK_DEVICEID_530TXPLUS 0x1300 + + /* * PCI low memory base and low I/O base register, and * other PCI registers. */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Apr 30 21:18: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (adam042-060.resnet.wisc.edu [146.151.42.60]) by hub.freebsd.org (Postfix) with ESMTP id A38C537B61A for ; Mon, 30 Apr 2001 21:17:59 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 21325 invoked by uid 1000); 1 May 2001 04:17:58 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 May 2001 04:17:58 -0000 Date: Mon, 30 Apr 2001 23:17:58 -0500 (CDT) From: Mike Silbersack To: Jan Mikkelsen Cc: Freebsd-Hackers Subject: Re: write() vs aio_write() In-Reply-To: <00bd01c0d1d1$106ccdf0$0901a8c0@haym.transactionsite.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 May 2001, Jan Mikkelsen wrote: > Mike Silbersack wrote: > [ On using aio on disks vs. sockets ] > >Sockets already support non-blocking IO, and have for a long while. > >Hence, the socket code is probably more optimized for non-blocking > >operation than AIO operation. As a plus, using non-blocking socket > >operations will allow your code to run on any platform; aio isn't as > >portable. > > I recall reading about possible zero copy I/O using the aio interface. Is > anyone thinking about this? And on a related note, how about something like > IRIX's O_DIRECT mode for files? > > I'm sure there are lots of issues, but I'm curious. > > Jan Mikkelsen I think the zero-copy patch for FreeBSD sets the page of the written COW and can thereby work with the standard write call. (Assuming that you don't re-write the page soon after doing the write.) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 0: 6:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 85C1137B422 for ; Tue, 1 May 2001 00:06:49 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0731.cvx21-bradley.dialup.earthlink.net [209.179.194.221]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id DAA22603; Tue, 1 May 2001 03:06:46 -0400 (EDT) Message-ID: <3AEE6099.3137138F@mindspring.com> Date: Tue, 01 May 2001 00:07:05 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Tom Cc: hackers@FreeBSD.ORG Subject: Re: cdr and cdrw with 4.3 release References: <20010413000032.12100.qmail@web12505.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom wrote: > > Does anyone know if it is possible to use a cdr/cdrw > with 4.3 release? I want to use it with my sony vaio > f580 (notebook). I have the option of usb or pcmcia. > Can you tell me which models are known to work? Thanks > for your help. Please mail all responses to > captonline@yahoo.com. Thanks again.. Tom I use the internal CDRW with my Vaio PCG-XG29. I believe that it is the same model which is used in the F580 and similar F-series notebooks. I don't use an external CDRW off a USB or PCMCIA dongle. A person I used to work with has a PCG-XG28; they use a PCMCIA based CDRW with success, but the card has to be there, and the drive on, at boot time. Personally, I prefer the internal version. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 1:18: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 5DCE237B423; Tue, 1 May 2001 01:17:58 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0731.cvx21-bradley.dialup.earthlink.net [209.179.194.221]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id EAA02208; Tue, 1 May 2001 04:17:46 -0400 (EDT) Message-ID: <3AEE713D.C0A35C82@mindspring.com> Date: Tue, 01 May 2001 01:18:05 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kirk McKusick Cc: Robert Watson , Julian Elischer , Rik van Riel , freebsd-hackers@FreeBSD.ORG, Matt Dillon , David Xu Subject: Re: vm balance References: <200104180540.WAA58303@beastie.mckusick.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ ... merging vnode and vm_object_t ... ] Kirk McKusick wrote: > Every vnode in the system has an associated object. Every object > backed by a file (e.g., everything but anonymous objects) has an > associated vnode. So, the performance of one is pretty tied to the > performance of the other. Matt is right that the VM does locking > on a page level, but then has to get a lock on the associated > vnode to do a read or a write, so really is pretty tied to the > vnode lock performance. Merging the two data structures is not > likely to change the performance characteristics of the system for > either better or worse. But it will save a lot of headaches having > to do with lock ordering that we have to deal with at the moment. I really, really dislike the idea of a merge of these objects, still, and not just because it will be nearly impossible to macke object coherency work in a stack of two or more VFS layers if this change ever goes through. When John Dyson originally wrote the FreeBSD unified VM and buffer cache code under contract for Oracle for use in their Oracle 8i and FreeBSD based NC server platform, he did so in such a way to allow anonymous objects, which did not have backing store associated with them. This was the memory pulled off of /dev/zero, and the memory in SYSVSHM. The main benefit of doing this is that it saves an incredible amount of write-through, which would otherwise be necessary to maintain coherency with the backing object (vnode). I think we need to remember that we do not always have a backing object, nor is a backing object always desirable. The performance of an mmap'ed file, or swap-backed anonymous region is _significantly_ below that of unbacked objects. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 1:23:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cslab.csie.ntu.edu.tw (cslab.csie.ntu.edu.tw [140.112.30.25]) by hub.freebsd.org (Postfix) with ESMTP id A1ED537B422 for ; Tue, 1 May 2001 01:22:53 -0700 (PDT) (envelope-from r88074@csie.ntu.edu.tw) Received: from hornets (hornets.csie.ntu.edu.tw [140.112.30.134]) by cslab.csie.ntu.edu.tw (8.9.3/8.9.3) with SMTP id QAA17927 for ; Tue, 1 May 2001 16:22:36 +0800 (CST) Message-Id: <200105010822.QAA17927@cslab.csie.ntu.edu.tw> From: "ªL­^¶W" To: "Freebsd-Hackers" Subject: RE: write() vs aio_write() Date: Tue, 1 May 2001 16:21:21 +0800 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <20010430173555.H18676@fw.wintelcom.net> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of 'Alfred Perlstein' Sent: Tuesday, May 01, 2001 8:36 AM To: Charles Randall Cc: ªL­^¶W; Freebsd-Hackers Subject: Re: write() vs aio_write() * Charles Randall [010430 10:26] wrote: > Regarding aio_*, Alfred Perlstein writes: > >It's a good idea to use it for disk IO, probably not a good > >idea for network IO. > > Could you elaborate? Sure. Network IO can be done without blocking (unless you take a fault on the source address of your data). Hence the additional context switching required by aio is not needed. Disk IO probably stands a good chance of blocking your application, if you can offload that blocking to a kernel thread you should be able to continue serving content. By the way..... I think synchonous I/O include blocking and non-blocking I/O and asynchonous I/O is non-blocking I/O, but it is signal-driven......... Am I right ???? -- -Alfred Perlstein - [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 1:28: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 0D04C37B422; Tue, 1 May 2001 01:27:58 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0731.cvx21-bradley.dialup.earthlink.net [209.179.194.221]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id EAA23348; Tue, 1 May 2001 04:27:51 -0400 (EDT) Message-ID: <3AEE739A.A69A52FE@mindspring.com> Date: Tue, 01 May 2001 01:28:10 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: Kirk McKusick , Robert Watson , Julian Elischer , Rik van Riel , freebsd-hackers@FreeBSD.ORG, Matt Dillon , David Xu Subject: Re: vm balance References: <33029.987575619@critter> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <200104180540.WAA58303@beastie.mckusick.com>, Kirk > McKusick writes: > > >Every vnode in the system has an associated object. > > No: device vnodes dont... > > I think the correct solution to that is to move devices away from > vnodes and into the fdesc layer, just like fifo's and sockets. This is really, likewise, a bad idea. The "struct fileops" has been a problem from day one. It exists for devices because we still have "specfs", and have not moved over to a "devfs" that uses vnodes instead of using strategy routines invoked from a "struct fileops *" dereference. The code was smeared into the FIFO/socket/IPC code as a poor man's integration to get something working. When that happened, the ability to do normal things like set ownership, permissions, etc., on things like FIFOs disappeared. FreeBSD is much poorer with regard to full compliance with POSIX semantics on things like F_ fcntl() arguments and the like when applied to sockets. Linux, Solaris, AIX, and other POSIX and Single UNIX Specification compliant OSs don't suffer these same problems. Perhaps one of the most annoying things about FreeBSD is the inability to perform advisory locking on anything by true vnode objects... and then only if the underlying VFS has an advisory lock chain hung off of some private structure, which can't be rescued except through the evils of POSIX locking semantics. Many applications use advisory lock chains off of devices to communicate region protection information not directly related to really protecting the resource. Similarly, "struct fileops" is the main culprit, to my mind, behind the inability of FreeBSD to support cloning devices, such as that needed for multiple virtual machine instances in vmware to work as it does in Linux and other first-class host OSs. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 1:42:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id DCC8F37B422 for ; Tue, 1 May 2001 01:42:14 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0731.cvx21-bradley.dialup.earthlink.net [209.179.194.221]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id EAA11157; Tue, 1 May 2001 04:42:04 -0400 (EDT) Message-ID: <3AEE76EF.BEF4FF98@mindspring.com> Date: Tue, 01 May 2001 01:42:23 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Michael C . Wu" Cc: Andrew Hesford , "Michael C . Wu" , Remy Nonnenmacher , jgowdy@home.com, freebsd-hackers@FreeBSD.ORG Subject: Re: x86-64 Hammer and IA64 Itainium References: <20010417205711.C64757@cec.wustl.edu> <200104181422.f3IELwC11439@luxren2.boostworks.com> <20010426180836.C88522@peorth.iteration.net> <20010426192352.A2341@cec.wustl.edu> <20010427102622.D88522@peorth.iteration.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Michael C . Wu" wrote: > I have been hearing about GaAs since the beginning of my college > career. One chemistry professor put it rather well, "Gallium > Arsenide based semiconductors are considered the future of > semiconductors, and always will be the future of semiconductors." Hitachi has a GaAs SPARC chip; it is used in Satellites. The CRAY-3 was GaAs based, if I'm not mistaken. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 1:47: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 4F96C37B423 for ; Tue, 1 May 2001 01:47:00 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0731.cvx21-bradley.dialup.earthlink.net [209.179.194.221]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id EAA30886; Tue, 1 May 2001 04:46:55 -0400 (EDT) Message-ID: <3AEE7812.FCA97395@mindspring.com> Date: Tue, 01 May 2001 01:47:14 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jeremiah Gowdy Cc: remy@boostworks.com, ajh3@chmod.ath.cx, freebsd-hackers@FreeBSD.ORG Subject: Re: x86-64 Hammer and IA64 Itainium References: <200104181422.f3IELwC11439@luxren2.boostworks.com> <000701c0c8e1$e3016490$015778d8@sherline.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeremiah Gowdy wrote: > Now think about this. Microsoft Visual C++ will be *the* > industry compiler for Itainium. Their compiler is already > working and has ILP support. Plus Intel makes its own > compiler which plugs into Visual Studio. Both the Microsoft > and Intel compilers for ILP are going to kick the crap out > of gcc and I think we all know it. So then what, you're > going to have FreeBSD and Linux compiled with an inferior > compiler compared to Windows with their compilers ? The > first thing that will happen is Microsoft will pay for a > benchmark showing Windows beating the living crap out of > Linux and BSD. And this time they won't have to fake it. > Not having proper ILP support is like intentionally stalling > pipes constantly. The whole design of this new cpu is the > ILP. Without it, the GNU compiled programs aren't going to > have much to show for. FWIW, I have been hearing increasing rumors about Intel donating their compiler to the FSF in order to ensure that benchmarks compiled with GCC run best on Intel. We have seen similar motions from Compaq, in their making Alpha compiler technology available without charge. These people sell hardware, not compilers; compilers are marketing tools for hardware, and have been, ever since free tools became "good enough" for most uses... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 1:47:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 4FEE937B422 for ; Tue, 1 May 2001 01:47:37 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f418lBX01954; Tue, 1 May 2001 10:47:11 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: tlambert2@mindspring.com Cc: "Michael C . Wu" , Andrew Hesford , "Michael C . Wu" , Remy Nonnenmacher , jgowdy@home.com, freebsd-hackers@FreeBSD.ORG Subject: Re: x86-64 Hammer and IA64 Itainium In-Reply-To: Your message of "Tue, 01 May 2001 01:42:23 PDT." <3AEE76EF.BEF4FF98@mindspring.com> Date: Tue, 01 May 2001 10:47:11 +0200 Message-ID: <1952.988706831@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3AEE76EF.BEF4FF98@mindspring.com>, Terry Lambert writes: >"Michael C . Wu" wrote: >> I have been hearing about GaAs since the beginning of my college >> career. One chemistry professor put it rather well, "Gallium >> Arsenide based semiconductors are considered the future of >> semiconductors, and always will be the future of semiconductors." > >Hitachi has a GaAs SPARC chip; it is used in Satellites. > >The CRAY-3 was GaAs based, if I'm not mistaken. And Convex made a GaAs based supercomputer, the 3800 I belive. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 2:10:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id E159237B423 for ; Tue, 1 May 2001 02:10:27 -0700 (PDT) (envelope-from langd@informatik.tu-muenchen.de) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.24.91] HELO atrbg11.informatik.tu-muenchen.de ident: IDENT-NONSENSE [port 1071]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <112000-237>; Tue, 1 May 2001 11:10:23 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 6315A13660; Tue, 1 May 2001 11:10:19 +0200 (CEST) Date: Tue, 1 May 2001 00:04:15 +0200 From: Daniel Lang To: Michael Jon Vigodda Cc: freebsd-hackers@leo.org Subject: Re: arp_rtrequest error Message-ID: <20010501000414.A665@atrbg11.informatik.tu-muenchen.de> References: <008301c0d1ab$d7e38980$7a493ad8@lee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <008301c0d1ab$d7e38980$7a493ad8@lee>; from vigodda@etherworx.com on Mon, Apr 30, 2001 at 03:29:13PM -0400 X-Geek: GCS d-- s: a- C++ UB++++$ P+++$ L- E W+++(--) N+ o K w--- O? M- V@ PS+(++) PE--(+) Y+ PGP+ t++ 5@ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Michael Jon Vigodda wrote on Mon, Apr 30, 2001 at 03:29:13PM -0400: > Hello. I saw your post on the FreeBSD-hackers mailing list and have the same problem. I was wondering what fix you came up with for this as, months later, I am scouring the mail lists to see if there is a fix and also cannot find one. > > I, too, have many aliases with the 0xfffffff netmask and am running routed. > > Any help or insights you can offer are greatly appreciated. Since I'm not familiar with the routing code, I switched over to gated, which did not cause these problems. Just a workaround, no real solution, but at least something. Best regards, Daniel -- IRCnet: Mr-Spock - signs of absurd developments in the net community: #42: - "Wurstbrot gehoert m.E. zum Fruehstuecks-botnet von Cartoon" - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 2:18:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from primo.verat.net (primo.verat.net [217.26.64.130]) by hub.freebsd.org (Postfix) with ESMTP id 7E27E37B424 for ; Tue, 1 May 2001 02:18:11 -0700 (PDT) (envelope-from milunovic@sendmail.ru) Received: from scorpion.cosmos.all.net (ppp65-114.verat.net [217.26.65.114]) by primo.verat.net (x.y.z/1.1.1) with ESMTP id LAA08785 for ; Tue, 1 May 2001 11:18:07 +0200 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by scorpion.cosmos.all.net (8.11.3/8.11.3) with ESMTP id f419OdH00645 for ; Tue, 1 May 2001 11:24:40 +0200 (CEST) Date: Tue, 1 May 2001 11:24:34 +0200 (CEST) From: milunovic X-Sender: milunovic@scorpion.cosmos.all.net Cc: hackers@FreeBSD.ORG Subject: Re: Problem with device rl In-Reply-To: <00bc01c0d1dd$2241a940$1200a8c0@gsicomp.on.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On Mon, 30 Apr 2001, Matthew Emmerton wrote: Thank you,this patch is working > *** if_rl.c.orig Sun Mar 25 19:08:34 2001 > --- if_rl.c Sun Mar 25 23:14:00 2001 > *************** > *** 149,154 **** > --- 149,156 ---- > "Delta Electronics 8139 10/100BaseTX" }, > { ADDTRON_VENDORID, ADDTRON_DEVICEID_8139, > "Addtron Technolgy 8139 10/100BaseTX" }, > + { DLINK_VENDORID, DLINK_DEVICEID_530TXPLUS, > + "D-Link DFE-530TX+ 10/100BaseTX" }, > { 0, 0, NULL } > }; > *************** > *** 898,904 **** > rl_read_eeprom(sc, (caddr_t)&rl_did, RL_EE_PCI_DID, 1, 0); > > if (rl_did == RT_DEVICEID_8139 || rl_did == ACCTON_DEVICEID_5030 || > ! rl_did == DELTA_DEVICEID_8139 || rl_did == ADDTRON_DEVICEID_8139) > sc->rl_type = RL_8139; > else if (rl_did == RT_DEVICEID_8129) > sc->rl_type = RL_8129; > --- 903,910 ---- > rl_read_eeprom(sc, (caddr_t)&rl_did, RL_EE_PCI_DID, 1, 0); > > if (rl_did == RT_DEVICEID_8139 || rl_did == ACCTON_DEVICEID_5030 || > ! rl_did == DELTA_DEVICEID_8139 || rl_did == ADDTRON_DEVICEID_8139 || > ! rl_did == DLINK_DEVICEID_530TXPLUS) > sc->rl_type = RL_8139; > else if (rl_did == RT_DEVICEID_8129) > sc->rl_type = RL_8129; > > *** if_rlreg.h.orig Sun Mar 25 19:08:34 2001 > --- if_rlreg.h Sun Mar 25 19:10:12 2001 > *************** > *** 433,438 **** > --- 433,448 ---- > #define ADDTRON_DEVICEID_8139 0x1360 > > /* > + * D-Link vendor ID. > + */ > + #define DLINK_VENDORID 0x1186 > + > + /* > + * D-Link DFE-530TX+ device ID > + */ > + #define DLINK_DEVICEID_530TXPLUS 0x1300 > + > + /* > * PCI low memory base and low I/O base register, and > * other PCI registers. > */ > > > > Vojislav Milunovic milunovic@sendmail.ru -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQEVAwUBOu6A1i3gPLld8IkLAQH6Vgf9GKRPN5J2Wt6ty/I/dLyTmYkrUDU+TlLK eS+o+dpvaDGKAGRDx+5yuxYfoxb40ZFar/mu29JSfCZ4SzLm8NJGWMi6Fshkt7Hn ECdtZfZHOxVey51jobD1h+ipr33taj+8Wz8RMLMigE8wID3eQ/bY4TveXxYkal/B aMOhHXy0SWIGLHp0AzyWomxByW0m8ye8BwiEktOx2Z7pAlBAl9FVd8TfgHzs+hJd LVc2Goi4VCZ7vhhCpB097ier46tgcAH9eGavR4BPfT/RYOrmgOwsROW4B8bn7NI/ 2CpHNGn7tY7gt1/kUSk+SYFr5Ot49Z1Ua7TrLV4o3hVXGNuPE+bcsQ== =TdYO -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 2:51:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id 97C5B37B422; Tue, 1 May 2001 02:51:41 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (pool0731.cvx21-bradley.dialup.earthlink.net [209.179.194.221]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id FAA11270; Tue, 1 May 2001 05:51:32 -0400 (EDT) Message-ID: <3AEE8736.17582DA3@mindspring.com> Date: Tue, 01 May 2001 02:51:50 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matt Dillon Cc: Poul-Henning Kamp , Julian Elischer , Robert Watson , Kirk McKusick , Rik van Riel , freebsd-hackers@FreeBSD.ORG, David Xu Subject: Re: Proposed struct file (was Re: vm balance) References: <42007.987619504@critter> <200104181903.f3IJ3Bw40186@earth.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > > This is all preliminary. The question is whether we can > cover enough bases for this to be viable. > > Here is a proposed struct file. Make f_data opaque (or > more opaque), add f_object, extend fileops (see next > structure), Added f_vopflags to indicate the presence > of a vnode in f_data, allowing extended filesystem ops > (e.g. rename, remove, fchown, etc etc etc). 1) struct fileops is evil; adding to it contributes to its inherent evil-ness. 2) The new structure is too large. 3) The old structure is too large; I have a need for 1,000,000 open files for a particular application, and I'm not willing to give up that much memory. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 2:56:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.tgd.net (rand.tgd.net [64.81.67.117]) by hub.freebsd.org (Postfix) with SMTP id DE84037B422 for ; Tue, 1 May 2001 02:56:31 -0700 (PDT) (envelope-from sean@mailhost.tgd.net) Received: (qmail 15993 invoked by uid 1001); 1 May 2001 09:56:29 -0000 Date: Tue, 1 May 2001 02:56:29 -0700 From: Sean Chittenden To: freebsd-hackers@freebsd.org Subject: Fetching an index of an FTP site using fetch... Message-ID: <20010501025629.E15203@rand.tgd.net> References: <20010501022832.C15203@rand.tgd.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mR8QP4gmHujQHb1c" Content-Disposition: inline In-Reply-To: <20010501022832.C15203@rand.tgd.net>; from "sean@chittenden.org" on Tue, May 01, 2001 at = 02:28:32AM X-PGP-Key: 0x1EDDFAAD X-PGP-Fingerprint: C665 A17F 9A56 286C 5CFB 1DEA 9F4F 5CEF 1EDD FAAD X-Web-Homepage: http://sean.chittenden.org/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --mR8QP4gmHujQHb1c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Does anyone have any ideas as far as a way in which it'd be possible to fetch a directory index using fetch? If I try to toss it into mirror mode (-m|-M), it returns the following error: fetch: fetch.out: Syntax error, command unrecognized Anyone have any ideas? The full command that I was trying is: fetch -p -m ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/ fetch -m ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/ fetch ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/ No dice on any of them. It seems like it should be possible to get an INDEX file of sorts out of fetch, but aparently not. ::sigh:: -sc PS I've looked through the source of fetch and libfetch, and it seems like there's some stub code that hasn't been flushed out completely. Anyone know of any plans to finish this up? /* * List a directory */ extern void warnx(char *, ...); struct url_ent * fetchListFTP(struct url *url, char *flags) { warnx("fetchListFTP(): not implemented"); return NULL; } --=20 Sean Chittenden --mR8QP4gmHujQHb1c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: Sean Chittenden iEYEARECAAYFAjruiEwACgkQn09c7x7d+q1vGACgh14aVnMuYO9A1gUVsT7wl6mp 86MAoNcHYpYSt6gaAYWDuBVRgSkRlXZX =FVMA -----END PGP SIGNATURE----- --mR8QP4gmHujQHb1c-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 7:56:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 0A67237B422 for ; Tue, 1 May 2001 07:56:35 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f41EuV840426 for ; Tue, 1 May 2001 23:56:31 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: References: X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.5 (alfalfa) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 10 From: Makoto MATSUSHITA To: hackers@freebsd.org Subject: Re: Set up loader to boot cd Date: Tue, 01 May 2001 23:56:05 +0900 Message-Id: <20010501235605M.matusita@jp.FreeBSD.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG maillist> So, do I need to vnconfig the boot.flp and put my own custom maillist> loader in it or what? I don't want to be puting -C in every maillist> time I boot. Also, when I put in -C, the kernel will load, maillist> but then can't find the CD device.... Which FreeBSD version you are using, 5-current or [43]-stable ? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 9:18:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.coastsight.com (ns1.coastsight.com [208.46.230.17]) by hub.freebsd.org (Postfix) with ESMTP id ADE7337B422 for ; Tue, 1 May 2001 09:18:21 -0700 (PDT) (envelope-from maillist@coastsight.com) Received: from ns1.coastsight.com ([208.46.230.17]) by ns1.coastsight.com with esmtp (Exim 2.05 #1) id 14ucqz-0001CG-00; Tue, 1 May 2001 09:18:21 -0700 Date: Tue, 1 May 2001 09:18:21 -0700 (PDT) From: Rick Duvall To: Makoto MATSUSHITA Cc: hackers@freebsd.org Subject: Re: Set up loader to boot cd In-Reply-To: <20010501235605M.matusita@jp.FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 4.2-20010119-STABLE On Tue, 1 May 2001, Makoto MATSUSHITA wrote: > > maillist> So, do I need to vnconfig the boot.flp and put my own custom > maillist> loader in it or what? I don't want to be puting -C in every > maillist> time I boot. Also, when I put in -C, the kernel will load, > maillist> but then can't find the CD device.... > > Which FreeBSD version you are using, 5-current or [43]-stable ? > > -- - > Makoto `MAR' MATSUSHITA > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 10: 3:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 118BE37B423 for ; Tue, 1 May 2001 10:03:34 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f41H3T848032 for ; Wed, 2 May 2001 02:03:30 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: References: <20010501235605M.matusita@jp.FreeBSD.org> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.5 (alfalfa) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 18 From: Makoto MATSUSHITA To: hackers@FreeBSD.ORG Subject: Re: Set up loader to boot cd Date: Wed, 02 May 2001 02:03:12 +0900 Message-Id: <20010502020312K.matusita@jp.FreeBSD.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG maillist> 4.2-20010119-STABLE My sample ISO image (using latest 4-stable) works very fine, booting from CD and mount CD as root partition. It works pretty well. If you have enough bandwidth to fetch 160MB ISO image file, try: Also, I've tried to do with 5-current, kernel *can't* mount CD as a root partition. If you wanna try how it goes to fail, try: I've sent a email before to current@freebsd.org, does anybody know why 5-current kernel can't mount my CD-ROM as a root partition? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 10:15:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.coastsight.com (ns1.coastsight.com [208.46.230.17]) by hub.freebsd.org (Postfix) with ESMTP id C5D8C37B422 for ; Tue, 1 May 2001 10:15:22 -0700 (PDT) (envelope-from maillist@coastsight.com) Received: from ns1.coastsight.com ([208.46.230.17]) by ns1.coastsight.com with esmtp (Exim 2.05 #1) id 14udk9-0001HY-00; Tue, 1 May 2001 10:15:21 -0700 Date: Tue, 1 May 2001 10:15:21 -0700 (PDT) From: Rick Duvall To: Makoto MATSUSHITA Cc: hackers@FreeBSD.ORG Subject: Re: Set up loader to boot cd In-Reply-To: <20010502020312K.matusita@jp.FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What about creating a mfsroot.gz as part of that boot floppy image, and mounting that as root, then mounting the cd as /usr on top of that? Let me know if you think that will work.... I don't quite understand how loader works, though.... Handbook doesn't tell me enough. Thanks. Sincerely, Rick Duvall On Wed, 2 May 2001, Makoto MATSUSHITA wrote: > > maillist> 4.2-20010119-STABLE > > My sample ISO image (using latest 4-stable) works very fine, booting > from CD and mount CD as root partition. It works pretty well. > > If you have enough bandwidth to fetch 160MB ISO image file, try: > > > Also, I've tried to do with 5-current, kernel *can't* mount CD as a > root partition. If you wanna try how it goes to fail, try: > > > I've sent a email before to current@freebsd.org, does anybody know why > 5-current kernel can't mount my CD-ROM as a root partition? > > -- - > Makoto `MAR' MATSUSHITA > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 10:20:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 47CBE37B639; Tue, 1 May 2001 10:20:47 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f41HKb268250; Tue, 1 May 2001 10:20:37 -0700 (PDT) (envelope-from dillon) Date: Tue, 1 May 2001 10:20:37 -0700 (PDT) From: Matt Dillon Message-Id: <200105011720.f41HKb268250@earth.backplane.com> To: Terry Lambert Cc: Kirk McKusick , Robert Watson , Julian Elischer , Rik van Riel , freebsd-hackers@FreeBSD.ORG, David Xu Subject: Re: vm balance References: <200104180540.WAA58303@beastie.mckusick.com> <3AEE713D.C0A35C82@mindspring.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I think we need to remember that we do not always have a :backing object, nor is a backing object always desirable. : :The performance of an mmap'ed file, or swap-backed anonymous :region is _significantly_ below that of unbacked objects. : :-- Terry This is not true, Terry. There is no performance degredation with swap verses unbacked storage, and no performance degredation with file-backed storage if you use MAP_NOSYNC to adjust the write flushing characteristics of the map. Additionally, there is no 'write through' in the VM layer per-say -- the filesystem syncer has to come along and actually look for dirty pages to sync to the backing store (and with MAP_NOSYNC it doesn't bother). The VM layers do not touch the backing store at all until they absolutely have to. For example, swap is not allocated until the pagedaemon actually decides to page something out. This leaves only the pageout daemon which operates as it always has... if you are not squeezed for memory, it won't try to page anything out. And you can always use madvise(), msync(), and mlock() on top of everything else to adjust the VM characteristics of a section of memory (though personally speaking I don't think mlock() is necessary with 4.x's VM system unless you need realtime). In short, mmap()'s backing store is not an issue in 4.x. Read the manual page for mmap for more information, I fleshed it out a long time ago to explain all of this. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 10:51:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 46D7737B422 for ; Tue, 1 May 2001 10:51:18 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f41HpE850264 for ; Wed, 2 May 2001 02:51:15 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: References: <20010502020312K.matusita@jp.FreeBSD.org> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.5 (alfalfa) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 16 From: Makoto MATSUSHITA To: hackers@FreeBSD.ORG Subject: Re: Set up loader to boot cd Date: Wed, 02 May 2001 02:51:01 +0900 Message-Id: <20010502025101M.matusita@jp.FreeBSD.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG maillist> What about creating a mfsroot.gz as part of that boot floppy maillist> image, and mounting that as root, then mounting the cd as maillist> /usr on top of that? Simply 'mount -t cd9660 /dev/cd0a /usr' (or whatever CD device) after booting a kernel is not enough for you? I've not tried yet, but there is no reason to fail (if it fails, it means that you cannot install FreeBSD from your CD drive.) maillist> I don't quite understand how loader works, though.... Obviously, mounting a filesystem is not a loader(8)'s job :-) -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 11:31: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by hub.freebsd.org (Postfix) with ESMTP id BD68D37B424 for ; Tue, 1 May 2001 11:30:57 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.11.3/8.11.2) id f41ITnS04475; Tue, 1 May 2001 11:29:49 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200105011829.f41ITnS04475@ambrisko.com> Subject: Re: cdr and cdrw with 4.3 release In-Reply-To: <3AEE6099.3137138F@mindspring.com> "from Terry Lambert at May 1, 2001 00:07:05 am" To: tlambert2@mindspring.com Date: Tue, 1 May 2001 11:29:49 -0700 (PDT) Cc: Tom , hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: | Tom wrote: | > | > Does anyone know if it is possible to use a cdr/cdrw | > with 4.3 release? I want to use it with my sony vaio | > f580 (notebook). I have the option of usb or pcmcia. | > Can you tell me which models are known to work? Thanks | > for your help. Please mail all responses to | > captonline@yahoo.com. Thanks again.. Tom | | I use the internal CDRW with my Vaio PCG-XG29. I believe | that it is the same model which is used in the F580 and | similar F-series notebooks. | | I don't use an external CDRW off a USB or PCMCIA dongle. | | A person I used to work with has a PCG-XG28; they use a | PCMCIA based CDRW with success, but the card has to be | there, and the drive on, at boot time. That is strange. I definitely don't see such problems. I do such thing several times. I try to avoid booting my laptop and just suspend and resume it. So I have several cards come and go over one boot cycle. Any generic PCMCIA IDE based thing should work. I might stop using an external CDRW things once combo DVD & CDRW become more available/cheaper. Also internal bits are harder to share. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 12: 3:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.coastsight.com (ns1.coastsight.com [208.46.230.17]) by hub.freebsd.org (Postfix) with ESMTP id C37B437B422; Tue, 1 May 2001 12:03:22 -0700 (PDT) (envelope-from maillist@coastsight.com) Received: from ns1.coastsight.com ([208.46.230.17]) by ns1.coastsight.com with esmtp (Exim 2.05 #1) id 14ufQf-0001Qm-00; Tue, 1 May 2001 12:03:21 -0700 Date: Tue, 1 May 2001 12:03:21 -0700 (PDT) From: Rick Duvall To: freebsd-questions@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Bootable CD IV Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So, let me get this straight: To make a bootable CD, you need to: 1. compile a kernel (generic will work) 2. gzip the kernel to kernel.gz 3. vnconfig -s labels -c vn0 boot.flp (from /cdrom/floppies/boot.flp) 4. mount /dev/vn0a /mnt 5. cp kernel.gz /mnt/kernel.gz 6. cp /boot/boot0 /mnt/boot/boot0;cp /boot/loader.4th /mnt/boot/loader.4th 7. umount /dev/vn0a;vnconfig -u vn0 8. mkdir /usr/cd;cp boot.flp /usr/cd 9. cp -R /bin /usr/cd;cp -R /etc /usr/cd;cp -R /sbin /usr/cd 10. pico -w /usr/cd/etc/fstab to mount acd0 as root. 11. mkisofs -o burnthis.iso -b boot.flp cd 12. Burn the ISO to a CD. 13. boot the CD. Okay, got that far. But, it will load the kernel, then hang and say that it cannot mount root device /dev/fd0. This doesn't make any sense to me becuase I specifically told fstab on the cd to use the cdrom as root. Am I stupid or something? Thanks. Sincerely, Rick Duvall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 14:54: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 755F837B423 for ; Tue, 1 May 2001 14:54:03 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id XAA21612; Tue, 1 May 2001 23:53:59 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Sean Chittenden Cc: freebsd-hackers@freebsd.org Subject: Re: Fetching an index of an FTP site using fetch... References: <20010501022832.C15203@rand.tgd.net> <20010501025629.E15203@rand.tgd.net> From: Dag-Erling Smorgrav Date: 01 May 2001 23:53:58 +0200 In-Reply-To: <20010501025629.E15203@rand.tgd.net> Message-ID: Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean Chittenden writes: > Does anyone have any ideas as far as a way in which it'd be > possible to fetch a directory index using fetch? No. It's not intended for that purpose, though it would be a nice addition. > PS I've looked through the source of fetch and libfetch, and > it seems like there's some stub code that hasn't been flushed out > completely. Anyone know of any plans to finish this up? Feel free to send patches :) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 15:49:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.coastsight.com (ns1.coastsight.com [208.46.230.17]) by hub.freebsd.org (Postfix) with ESMTP id EED8B37B422; Tue, 1 May 2001 15:49:19 -0700 (PDT) (envelope-from maillist@coastsight.com) Received: from ns1.coastsight.com ([208.46.230.17]) by ns1.coastsight.com with esmtp (Exim 2.05 #1) id 14uixL-0001lt-00; Tue, 1 May 2001 15:49:19 -0700 Date: Tue, 1 May 2001 15:49:19 -0700 (PDT) From: Rick Duvall To: Sven Huster Cc: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Bootable CD IV In-Reply-To: <3.0.6.32.20010502004207.0107d530@mx.mailsurf.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So, you mean I need to create that rootmfs.gz thing that is on the second floppy of the freebsd install, then mount cdrom as something other than root? I do actually have a copy of my / on my cd, so, I don't see why it's failing to mount root. The only thing I can see is if I create the mfsroot.gz and get it compressed with kernel.gz like it is in the 2.88M boot.flp image. I just wish I knew what files to put in the root image, and how to get it to merge with kernel.gz. Thanks... Sincerely, Rick Duvall On Wed, 2 May 2001, Sven Huster wrote: > *This message was transferred with a trial version of CommuniGate(tm) Pro* > Hi > > i think it tries to mount root before it reads fstab, which is > on root. > > the problem i see, is that boot from cdrom simulates a floppy. > so the system will try to use the simulated floppy for the root device. > > i think you will need at least a minmal root fs on this bootable image, > you use to create the cdrom. > > regards > Sven > > At 12:03 01.05.01 -0700, you wrote: > >*This message was transferred with a trial version of CommuniGate(tm) Pro* > >So, let me get this straight: To make a bootable CD, you need to: > > > >1. compile a kernel (generic will work) > >2. gzip the kernel to kernel.gz > >3. vnconfig -s labels -c vn0 boot.flp (from /cdrom/floppies/boot.flp) > >4. mount /dev/vn0a /mnt > >5. cp kernel.gz /mnt/kernel.gz > >6. cp /boot/boot0 /mnt/boot/boot0;cp /boot/loader.4th > >/mnt/boot/loader.4th > >7. umount /dev/vn0a;vnconfig -u vn0 > >8. mkdir /usr/cd;cp boot.flp /usr/cd > >9. cp -R /bin /usr/cd;cp -R /etc /usr/cd;cp -R /sbin /usr/cd > >10. pico -w /usr/cd/etc/fstab to mount acd0 as root. > >11. mkisofs -o burnthis.iso -b boot.flp cd > >12. Burn the ISO to a CD. > >13. boot the CD. > > > >Okay, got that far. But, it will load the kernel, then hang and say that > >it cannot mount root device /dev/fd0. This doesn't make any sense to me > >becuase I specifically told fstab on the cd to use the cdrom as root. Am > >I stupid or something? > > > >Thanks. > > > >Sincerely, > > > >Rick Duvall > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-questions" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 15:57:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from out-mta3.plasa.com (out-mta3.plasa.com [202.134.0.195]) by hub.freebsd.org (Postfix) with ESMTP id 08B1437B424 for ; Tue, 1 May 2001 15:57:22 -0700 (PDT) (envelope-from q2001@plasa.com) Received: out-mta3.plasa.com; Wed, 02 May 2001 05:51:27 +0700 Received: out-mta2.plasa.com; Wed, 02 May 2001 05:52:40 +0700 Received: from [192.168.19.55] (account ) by mail.plasa.com (CommuniGate Pro WebUser 3.4.4) with HTTP id 3518011 for ; Wed, 02 May 2001 05:57:19 +0700 From: "q" Subject: cy0: port not found To: freebsd-hackers@freebsd.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.4 Date: Wed, 02 May 2001 05:57:19 +0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I need some advice to build dial-in server. I've Cyclades Cyclom 32 YeP and FreeBSD 4.3. This is first time for me to Install multiport Serial. I'm trying to look at FreeBSD 4.3 manual : # man cy and I follow to add the lines to my kernel options, recompile it, and restart the computer. But reported : cy0: port not found What should I do ??? Thank's. Q ------------------------------------------------------------------ Email ini dikirim oleh PlasaCom : http://www.plasa.com Cepat di-download via TelkomNet Instan http://www.plasa.com/instan Rindukah Anda bertemu dengan ex teman-teman satu sekolah dulu ? Kunjungilah mereka (47.033 anggota) di KSI : http://ksi.plasa.com ------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 17:19:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id D8AA137B422; Tue, 1 May 2001 17:19:29 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f420JJ334064; Tue, 1 May 2001 17:19:20 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: maillist@coastsight.com Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Bootable CD IV In-Reply-To: References: X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010501171919L.jkh@osd.bsdi.com> Date: Tue, 01 May 2001 17:19:19 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 25 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Rick Duvall Subject: Bootable CD IV Date: Tue, 1 May 2001 12:03:21 -0700 (PDT) > So, let me get this straight: To make a bootable CD, you need to: > [steps alided] That will essentially work, yes, though I've never seen someone use /usr directly as a scratch directory before. :-) > Okay, got that far. But, it will load the kernel, then hang and say that > it cannot mount root device /dev/fd0. This doesn't make any sense to me > becuase I specifically told fstab on the cd to use the cdrom as root. Am > I stupid or something? Not stupid, just not thinking this all the way through. The root mounting code runs well ahead of anything which looks into /etc/fstab; how indeed could it even find fstab if it didn't know where the root partition was? You need to change the kernel's mind about where to find its root partition, something which can be accomplished in a variety of ways. In the case of the boot floppy, we don't even try; we just use MFS for the root partition and mount the CD elsewhere. Of all the options, this is in fact the simplest. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 18:13:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from areilly.bpc-users.org (CPE-144-132-234-126.nsw.bigpond.net.au [144.132.234.126]) by hub.freebsd.org (Postfix) with SMTP id 4913C37B422 for ; Tue, 1 May 2001 18:13:18 -0700 (PDT) (envelope-from areilly@bigpond.net.au) Received: (qmail 1553 invoked by uid 1000); 2 May 2001 01:13:17 -0000 From: "Andrew Reilly" Date: Wed, 2 May 2001 11:13:17 +1000 To: Leif Neland Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: x86-64 Hammer and IA64 Itainium Message-ID: <20010502111317.A1059@gurney.reilly.home> References: <200104171836.LAA06378@akira.lanfear.com> <000001c0c777$f9529b30$215778d8@cx443070b> <20010426175906.B88522@peorth.iteration.net> <3AE8D4DC.E0E35042@bellatlantic.net> <00d701c0cedc$1ee190c0$6405a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00d701c0cedc$1ee190c0$6405a8c0@neland.dk>; from leifn@neland.dk on Fri, Apr 27, 2001 at 07:37:15AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 27, 2001 at 07:37:15AM +0200, Leif Neland wrote: > From: "Sergey Babkin" > > Anothing interesting point is that the optimisation for IA-64 > > seems to be highly processor-specific: the code optimized for > > Itanium won't be optimal for McKinley and vice versa. I've heard > > an estimation of about 1.5 times speed increase due to the > > model-specific optimisation. > > > Perhaps commercial software will need to come in (encrypted) > source and be compiled to the the current processor... What else is .NET? (OK, it's a bunch of other stuff too, but processors like the Itanium that introduce serious system specific performance issues (like memory and cache latencies) are a very good reason to persue dynamic recompilation technologies like HotSpot, Dynamo, FX-86, Transmetta and .NET.) -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 20:56:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 9ED7C37B422 for ; Tue, 1 May 2001 20:56:48 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f423uTM08248; Tue, 1 May 2001 21:56:29 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200105020356.f423uTM08248@harmony.village.org> To: Doug Ambrisko Subject: Re: cdr and cdrw with 4.3 release Cc: tlambert2@mindspring.com, Tom , hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 01 May 2001 11:29:49 PDT." <200105011829.f41ITnS04475@ambrisko.com> References: <200105011829.f41ITnS04475@ambrisko.com> Date: Tue, 01 May 2001 21:56:29 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200105011829.f41ITnS04475@ambrisko.com> Doug Ambrisko writes: : Any generic PCMCIA IDE based thing should work. I might stop using an Other than flash, I have 5 different PCMCIA IDE based things, and they all work. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 21:49: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout1-hme0.midsouth.rr.com (mailout1-100bt.midsouth.rr.com [24.92.68.6]) by hub.freebsd.org (Postfix) with ESMTP id E441337B423 for ; Tue, 1 May 2001 21:48:59 -0700 (PDT) (envelope-from dchance@midsouth.rr.com) Received: from satan (HubS-mcr-24-165-213-219.midsouth.rr.com [24.165.213.219]) by mailout1-hme0.midsouth.rr.com (8.11.2/8.11.2) with SMTP id f424mqb25571 for ; Tue, 1 May 2001 23:48:52 -0500 (CDT) Message-ID: <024d01c0d2c3$56626ac0$0200000a@satan> From: "Daryl Chance" To: Subject: Mini Config. Date: Tue, 1 May 2001 23:49:51 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2465.0003 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2465.0003 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm working on creating the smallest config I can get to compile as an "experiment" and to basically move to KLM's overall (once I get this working properly, I'll send-pr it to see if anyone wants it in the next release possibly). I have a question about how I would get some of the options into the kernel, wether it be sysctl or they would need to be in the kernel config. Things like: options NFS_ROOT options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=10 etc etc. If I kldload nfs.ko, will the NFS_ROOT option be available if I don't specify it in the kernel or do I need to specify it in the kernel if I want it to be usable as root when the NFS module is loaded? Can I do this via sysctls? Same goes for IPFIREWALL_* Thanks, Daryl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 1 22:50: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.guildsoftware.com (guild.guildsoftware.com [207.67.51.35]) by hub.freebsd.org (Postfix) with ESMTP id C677937B424 for ; Tue, 1 May 2001 22:50:06 -0700 (PDT) (envelope-from andude@guild.guildsoftware.com) Received: (from andude@localhost) by guild.guildsoftware.com (8.9.3/8.9.3) id AAA24582 for freebsd-hackers@FreeBSD.org; Wed, 2 May 2001 00:50:00 -0500 Date: Wed, 2 May 2001 00:50:00 -0500 From: Andy Sloane To: freebsd-hackers@FreeBSD.org Subject: new syscons screensaver Message-ID: <20010502005000.B19547@guild.guildsoftware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I just wrote a new syscons screensaver which I think is much more interesting than the other ones, while still being relatively easy on the CPU (much less CPU intensive than "fire", anyway). Please review it and let me know what you think. It's the bsd daemon logo (with much editing, thanks to my coworker Waylon) floating (with a realtime shadow!) above a bunch of tiled spheres which move around and morph. It's only one palette change per frame, until the bsd daemon moves. http://fear.incarnate.net/~andude/balls.tar.gz I'm not on this list, so please reply directly to me. Thanks. -Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 0:17:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from chmod.ath.cx (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id D7ECD37B423 for ; Wed, 2 May 2001 00:17:07 -0700 (PDT) (envelope-from ajh3@chmod.ath.cx) Received: by chmod.ath.cx (Postfix, from userid 1001) id 6EFAAA876; Wed, 2 May 2001 02:16:00 -0500 (CDT) Date: Wed, 2 May 2001 02:16:00 -0500 From: Andrew Hesford To: Andy Sloane Cc: freebsd-hackers@FreeBSD.org Subject: Re: new syscons screensaver Message-ID: <20010502021600.A34130@cec.wustl.edu> References: <20010502005000.B19547@guild.guildsoftware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010502005000.B19547@guild.guildsoftware.com>; from andy@guildsoftware.com on Wed, May 02, 2001 at 12:50:00AM -0500 X-Loop: Andrew Hesford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 02, 2001 at 12:50:00AM -0500, Andy Sloane wrote: > Hello, > > I just wrote a new syscons screensaver which I think is much more > interesting than the other ones, while still being relatively easy on the > CPU (much less CPU intensive than "fire", anyway). Please review it and > let me know what you think. > > It's the bsd daemon logo (with much editing, thanks to my coworker Waylon) > floating (with a realtime shadow!) above a bunch of tiled spheres which > move around and morph. It's only one palette change per frame, until the > bsd daemon moves. > > http://fear.incarnate.net/~andude/balls.tar.gz > > I'm not on this list, so please reply directly to me. Thanks. > > -Andy First, you should know that I absolutely love your first name. :) The screensaver isn't bad, and it gets pretty trippy when you focus at infinity and let the 3D-Illusions (TM) effect set in. If I were to make one suggestion, it would be to animate Beastie, so that he walks around the screen rather than teleporting everywhere. However, I'm quite fond of the green_saver module, which shuts down my monitor after 15 minutes. Other screensavers are really just for entertainment; I think green_saver is the only one that serves a really good purpose. -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 3:19:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from discus.nl.uu.net (discus.nl.uu.net [193.67.79.178]) by hub.freebsd.org (Postfix) with ESMTP id 856B337B422 for ; Wed, 2 May 2001 03:19:56 -0700 (PDT) (envelope-from arjan@jak.nl) Received: from 1Cust226.tnt34.rtm1.nl.uu.net ([213.116.162.226]:1059 "EHLO jak.nl") by discus.nl.uu.net with ESMTP id ; Wed, 2 May 2001 12:19:33 +0200 Message-ID: <3AEFDF61.8CAF40BF@jak.nl> Date: Wed, 02 May 2001 12:20:17 +0200 From: Arjan Knepper Organization: JAK++ Software Development B.V. X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: q Cc: freebsd-hackers@freebsd.org Subject: Re: cy0: port not found References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG q wrote: > Hi, I need some advice to build dial-in server. > I've Cyclades Cyclom 32 YeP and FreeBSD 4.3. > This is first time for me to Install multiport Serial. > I'm trying to look at FreeBSD 4.3 manual : > > # man cy > > and I follow to add the lines to my kernel options, > recompile it, and restart the computer. > But reported : > > cy0: port not found > > What should I do ??? > Thank's. Maybe you forgot to make the devices cuac00 - cuac0v with # sh /dev/MAKEDEV cuac0. And you also want to to al look in /etc/rc.serial at the cyclades section I guess. Success, Arjan Knepper > > > Q > ------------------------------------------------------------------ > Email ini dikirim oleh PlasaCom : http://www.plasa.com > Cepat di-download via TelkomNet Instan http://www.plasa.com/instan > Rindukah Anda bertemu dengan ex teman-teman satu sekolah dulu ? > Kunjungilah mereka (47.033 anggota) di KSI : http://ksi.plasa.com > ------------------------------------------------------------------ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 5: 4:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id AC7BF37B422; Wed, 2 May 2001 05:04:36 -0700 (PDT) (envelope-from langd@informatik.tu-muenchen.de) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.24.91] HELO atrbg11.informatik.tu-muenchen.de ident: IDENT-NONSENSE [port 1358]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <113116-237>; Wed, 2 May 2001 14:04:33 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id D668C13667; Wed, 2 May 2001 14:04:23 +0200 (CEST) Date: Wed, 2 May 2001 14:04:23 +0200 From: Daniel Lang To: freebsd-hackers@freebsd.org, freebsd-quetions@freebsd.org Subject: Kernel Console speed Message-ID: <20010502140423.B91287@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Geek: GCS d-- s: a- C++ UB++++$ P+++$ L- E W+++(--) N+ o K w--- O? M- V@ PS+(++) PE--(+) Y+ PGP+ t++ 5@ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear People, I have configured a couple of machines to use the serial console. Now with some machines, the console speed cannot be set correctly. I have read the appropriate chapters in the handbook, and I getting the serial console working at all, is not a problem. Just the speed setting does not work at _some_ machines. As far as I understand it, there are several components that interact as (serial) console: - boot2 - loader - the kernel - the getty (if a getty is configured at the console device) My problems only apply to the kernel, not to the bootstrap, and the getty intially uses, what the kernel used. What I did: set BOOT_COMCONSOLE_SPEED=38400 in /etc/make.conf set options CONSPEED=38400 in KERNEL compiled and installed kernel and new bootstrap (with disklabel). changed /etc/ttys to use std.38400 as argument to getty. further: set machdep.conspeed=38400 in /boot/loader.conf I've checked with kgdb the constants in the debugging kernel, that in /sys/isa/sio.c:sysctl_machdep_comdefaultrate() comdefaultrate is indeed 38400. The bootstraps works with 38400, (both boot2 and loader), but as soon as the kernel boots, it switches back to 9600. If the system is up, I can change the sysctl parameter: sysctl -w machdep.conspeed=38400 back to 38400, which works then (it also worked automaticalle if I place this in /etc/sysctl.conf). But I seem to have no chance to make it actually boot with that speed, so that the booting messages of the kernel can be viewed from the console-server. I run 4.3-STABLE on the box. The strange things is, that it works on another machine, but not on two other ones. All run the same release, all are i386 PCs with 16550A UARTs. The hardware is of course capable of running at different speeds than 9600, since the bootstrap runs at 38400 and a running system can be set to it, too. The hardware is very different though: Working boxes: Athlon 700 on Asus A7V Not working ones: Dell PowerEdge 4/200: 4xPPro 200 SMP, (with chipset info) Intel 82454KX/GX (Orion) host to PCI bridge Intel 82375EB PCI-EISA bridge Thanks and Best regards, Daniel -- IRCnet: Mr-Spock - Agartim billiard bumba m'abdul in papejim twista - rumba rock n rolla. Leik'ab mai. Spirzon Heroin se'osit gaula. - - Marijuana esit gaula. Haschisch. Opis. - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 9:16:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.coastsight.com (ns1.coastsight.com [208.46.230.17]) by hub.freebsd.org (Postfix) with ESMTP id EE84037B423; Wed, 2 May 2001 09:16:13 -0700 (PDT) (envelope-from maillist@coastsight.com) Received: from ns1.coastsight.com ([208.46.230.17]) by ns1.coastsight.com with esmtp (Exim 2.05 #1) id 14uzIT-0003G4-00; Wed, 2 May 2001 09:16:13 -0700 Date: Wed, 2 May 2001 09:16:13 -0700 (PDT) From: Rick Duvall To: Jordan Hubbard Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Bootable CD IV In-Reply-To: <20010501171919L.jkh@osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So, I guess my next questions is: How do create the 2.88M boot floppy image with the MFS stuff on it? I guess it merges somehow inside the kernel? Am I right? If so, how do i compile my mfs into the kernel, and what do I put in the MFS? Also, what files do I need to put on the boot floppy and what configuration files do I need to edit? If I cannot mount the cd as /, and only the MFS can be /, then can I at lease mount it as /usr? I am assuming I would edit /etc/rc.local on the mfs root. What I am wanting is a bootable cd that will take the user into an automatic restore script, that will ask them to put the last tape in the drive, and do a fdisk, disklabel, and newfs the hard drive, then restore from tape. Basicly, it's a foolproof method for disaster recovery is what i am trying to get at. Thanks. Sincerely, Rick Duvall On Tue, 1 May 2001, Jordan Hubbard wrote: > From: Rick Duvall > Subject: Bootable CD IV > Date: Tue, 1 May 2001 12:03:21 -0700 (PDT) > > > So, let me get this straight: To make a bootable CD, you need to: > > [steps alided] > > That will essentially work, yes, though I've never seen someone use > /usr directly as a scratch directory before. :-) > > > Okay, got that far. But, it will load the kernel, then hang and say that > > it cannot mount root device /dev/fd0. This doesn't make any sense to me > > becuase I specifically told fstab on the cd to use the cdrom as root. Am > > I stupid or something? > > Not stupid, just not thinking this all the way through. The root > mounting code runs well ahead of anything which looks into /etc/fstab; > how indeed could it even find fstab if it didn't know where the root > partition was? You need to change the kernel's mind about where to > find its root partition, something which can be accomplished in a > variety of ways. In the case of the boot floppy, we don't even try; > we just use MFS for the root partition and mount the CD elsewhere. > Of all the options, this is in fact the simplest. > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 9:17:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id CFF4437B423 for ; Wed, 2 May 2001 09:17:14 -0700 (PDT) (envelope-from krepel@fokus.gmd.de) Received: from fokus.gmd.de (quant [193.175.133.183]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id SAA27477; Wed, 2 May 2001 18:17:02 +0200 (MET DST) Message-ID: <3AF032FE.A0CBFB34@fokus.gmd.de> Date: Wed, 02 May 2001 18:17:02 +0200 From: Falco Krepel Organization: GMD FOKUS - CATS Group X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en, de-DE MIME-Version: 1.0 To: Arjan Knepper Cc: q , freebsd-hackers@FreeBSD.ORG Subject: Re: cy0: port not found References: <3AEFDF61.8CAF40BF@jak.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Arjan Knepper wrote: > > q wrote: > > > Hi, I need some advice to build dial-in server. > > Maybe you forgot to make the devices cuac00 - cuac0v with # sh > /dev/MAKEDEV cuac0. Is this also necessary when you use the kernel option DEVFS? -- Falco Krepel Phone: +49-(0)30 - 34 63 - 7 276 GMD-FOKUS Fax: +49-(0)30 - 34 63 - 8 276 Kaiserin-Augusta-Allee 31 e-mail: krepel@fokus.gmd.de 10589 Berlin WWW: http://www.fokus.gmd.de/usr/krepel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 9:42: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.guildsoftware.com (guild.guildsoftware.com [207.67.51.35]) by hub.freebsd.org (Postfix) with ESMTP id A4C2D37B422 for ; Wed, 2 May 2001 09:42:05 -0700 (PDT) (envelope-from andude@guild.guildsoftware.com) Received: (from andude@localhost) by guild.guildsoftware.com (8.9.3/8.9.3) id LAA26014; Wed, 2 May 2001 11:42:00 -0500 Date: Wed, 2 May 2001 11:41:59 -0500 From: Andy Sloane To: Andrew Hesford Cc: freebsd-hackers@FreeBSD.org Subject: Re: new syscons screensaver Message-ID: <20010502114159.C19547@guild.guildsoftware.com> References: <20010502005000.B19547@guild.guildsoftware.com> <20010502021600.A34130@cec.wustl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: <20010502021600.A34130@cec.wustl.edu>; from Andrew Hesford on Wed, May 02, 2001 at 02:16:00AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 02, 2001 at 02:16:00AM -0500, Andrew Hesford wrote: > The screensaver isn't bad, and it gets pretty trippy when you focus at > infinity and let the 3D-Illusions (TM) effect set in. If I were to make > one suggestion, it would be to animate Beastie, so that he walks around > the screen rather than teleporting everywhere. Heh. My main aim was to make it as low-overhead as possible for my poor old firewall box, but animating him wouldn't add much, especially on modern computers. :) > However, I'm quite fond of the green_saver module, which shuts down my > monitor after 15 minutes. Other screensavers are really just for > entertainment; I think green_saver is the only one that serves a really > good purpose. I agree; however I'm running FreeBSD on my firewall box, which has an old vga monitor which isn't DPMS-capable, so it doesn't really ever shut down unless I turn it off. For all I know I may be the only one who actually uses these screensavers. So I thought I'd try maximize my entertainment value. -Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 9:59:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 6683437B43C; Wed, 2 May 2001 09:59:37 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f42GxQ341227; Wed, 2 May 2001 09:59:26 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: maillist@coastsight.com Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Bootable CD IV In-Reply-To: References: <20010501171919L.jkh@osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010502095926S.jkh@osd.bsdi.com> Date: Wed, 02 May 2001 09:59:26 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 18 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Rick Duvall Subject: Re: Bootable CD IV Date: Wed, 2 May 2001 09:16:13 -0700 (PDT) > So, I guess my next questions is: > > How do create the 2.88M boot floppy image with the MFS stuff on it? I > guess it merges somehow inside the kernel? Am I right? If so, how do i > compile my mfs into the kernel, and what do I put in the MFS? In the interests of sparing my fingers, I'll simply direct you to /usr/src/release/Makefile at this point; you can see how it builds the mfsroot.flp bits and how it also stuffs them into a "big kernel" for the boot.flp bits. Don't be surprised if you have to read it about 11 times to really get the gist, but it will eventually make sense if you have the patience. :) Good luck! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 11: 8:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 78A9F37B423; Wed, 2 May 2001 11:08:25 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.22 #1) id 14v131-0001yN-00; Wed, 02 May 2001 18:08:23 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f42IClT01353; Wed, 2 May 2001 20:12:47 +0200 (CEST) (envelope-from wkb) Date: Wed, 2 May 2001 20:12:47 +0200 From: Wilko Bulte To: Jordan Hubbard Cc: maillist@coastsight.com, freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Bootable CD IV Message-ID: <20010502201247.A1339@freebie.demon.nl> References: <20010501171919L.jkh@osd.bsdi.com> <20010502095926S.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010502095926S.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Wed, May 02, 2001 at 09:59:26AM -0700 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 02, 2001 at 09:59:26AM -0700, Jordan Hubbard wrote: > From: Rick Duvall > Subject: Re: Bootable CD IV > Date: Wed, 2 May 2001 09:16:13 -0700 (PDT) > > > So, I guess my next questions is: > > > > How do create the 2.88M boot floppy image with the MFS stuff on it? I > > guess it merges somehow inside the kernel? Am I right? If so, how do i > > compile my mfs into the kernel, and what do I put in the MFS? > > In the interests of sparing my fingers, I'll simply direct you to > /usr/src/release/Makefile at this point; you can see how it builds the > mfsroot.flp bits and how it also stuffs them into a "big kernel" > for the boot.flp bits. Don't be surprised if you have to read > it about 11 times to really get the gist, but it will eventually > make sense if you have the patience. :) Good luck! Beer helps too.. -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte Powered by FreeBSD/alpha http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 11:28:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 8B70C37B424 for ; Wed, 2 May 2001 11:28:46 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f42ISVG41758; Wed, 2 May 2001 11:28:35 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010502005000.B19547@guild.guildsoftware.com> Date: Wed, 02 May 2001 11:27:46 -0700 (PDT) From: John Baldwin To: Andy Sloane Subject: RE: new syscons screensaver Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-May-01 Andy Sloane wrote: > Hello, > > I just wrote a new syscons screensaver which I think is much more > interesting than the other ones, while still being relatively easy on the > CPU (much less CPU intensive than "fire", anyway). Please review it and > let me know what you think. > > It's the bsd daemon logo (with much editing, thanks to my coworker Waylon) > floating (with a realtime shadow!) above a bunch of tiled spheres which > move around and morph. It's only one palette change per frame, until the > bsd daemon moves. > > http://fear.incarnate.net/~andude/balls.tar.gz > > I'm not on this list, so please reply directly to me. Thanks. Looks cool. I think it would be kind of cool to have the daemon walking around as well, but other than that it is neat. If you are looking for another idea for a scresn saver, a really cool one to have would be the 'swarm' or 'bees' saver either as a text or graphical one. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 11:42:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from webmail.netcom.no (webmail.netcom.no [212.45.188.36]) by hub.freebsd.org (Postfix) with ESMTP id 6F4B537B422 for ; Wed, 2 May 2001 11:42:07 -0700 (PDT) (envelope-from sgt@netcom.no) Received: from hal ([212.45.183.18]) by webmail.netcom.no (Netscape Messaging Server 4.15) with ESMTP id GCQ1AG00.DND; Wed, 2 May 2001 20:42:16 +0200 Date: Wed, 2 May 2001 20:42:01 +0200 (CEST) From: Torbjorn Kristoffersen X-Sender: To: Andy Sloane , Andrew Hesford Cc: Subject: Re: new syscons screensaver In-Reply-To: <20010502021600.A34130@cec.wustl.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > However, I'm quite fond of the green_saver module, which shuts down my > monitor after 15 minutes. Other screensavers are really just for > entertainment; I think green_saver is the only one that serves a really > good purpose. > What about implementing some code from green_saver into his saver to enable DPMS support? And have a sysctl value to set the delay after the green saver will begin :) Maybe there's a better way, to let his beastie_saver.ko load green_saver.ko (and possibly unload itself) after a specified delay? G`luck, Torbjorn Kristoffersen sgt@netcom.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 12: 8:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from chmod.ath.cx (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id 862AE37B423 for ; Wed, 2 May 2001 12:08:30 -0700 (PDT) (envelope-from ajh3@chmod.ath.cx) Received: by chmod.ath.cx (Postfix, from userid 1001) id B519FA876; Wed, 2 May 2001 14:07:30 -0500 (CDT) Date: Wed, 2 May 2001 14:07:30 -0500 From: Andrew Hesford To: Torbjorn Kristoffersen Cc: Andy Sloane , freebsd-hackers@FreeBSD.ORG Subject: Re: new syscons screensaver Message-ID: <20010502140730.A35961@cec.wustl.edu> References: <20010502021600.A34130@cec.wustl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from sgt@netcom.no on Wed, May 02, 2001 at 08:42:01PM +0200 X-Loop: Andrew Hesford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 02, 2001 at 08:42:01PM +0200, Torbjorn Kristoffersen wrote: > > > > However, I'm quite fond of the green_saver module, which shuts down my > > monitor after 15 minutes. Other screensavers are really just for > > entertainment; I think green_saver is the only one that serves a really > > good purpose. > > > > What about implementing some code from green_saver into his saver to > enable DPMS support? And have a sysctl value to set the delay after the > green saver will begin :) Maybe there's a better way, to let his > beastie_saver.ko load green_saver.ko (and possibly unload itself) after a > specified delay? > > G`luck, > Torbjorn Kristoffersen > sgt@netcom.no > > THAT'S an idea. I would love to see some fancy screensaver put to good use, as long as I know that it will eventually turn off my monitor. -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 12:16:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from discus.nl.uu.net (discus.nl.uu.net [193.67.79.178]) by hub.freebsd.org (Postfix) with ESMTP id A3B0637B423 for ; Wed, 2 May 2001 12:16:31 -0700 (PDT) (envelope-from arjan@jak.nl) Received: from 1Cust55.tnt18.rtm1.nl.uu.net ([213.116.130.55]:1871 "EHLO jak.nl") by discus.nl.uu.net with ESMTP id ; Wed, 2 May 2001 21:16:29 +0200 Message-ID: <3AF05D38.46739D4B@jak.nl> Date: Wed, 02 May 2001 21:17:12 +0200 From: Arjan Knepper Organization: JAK++ Software Development B.V. X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Falco Krepel Cc: q , freebsd-hackers@FreeBSD.ORG Subject: Re: cy0: port not found References: <3AEFDF61.8CAF40BF@jak.nl> <3AF032FE.A0CBFB34@fokus.gmd.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Falco Krepel wrote: > Arjan Knepper wrote: > > > > q wrote: > > > > > Hi, I need some advice to build dial-in server. > > > > Maybe you forgot to make the devices cuac00 - cuac0v with # sh > > /dev/MAKEDEV cuac0. > > Is this also necessary when you use the kernel option DEVFS? I don't know, I think it is needed as long as you want to use the /dev/cuac0* entries to access to cyclades serial ports. Arjan Knepper To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 12:29:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.guildsoftware.com (guild.guildsoftware.com [207.67.51.35]) by hub.freebsd.org (Postfix) with ESMTP id C198837B422 for ; Wed, 2 May 2001 12:29:34 -0700 (PDT) (envelope-from andude@guild.guildsoftware.com) Received: (from andude@localhost) by guild.guildsoftware.com (8.9.3/8.9.3) id OAA26582; Wed, 2 May 2001 14:29:31 -0500 Date: Wed, 2 May 2001 14:29:31 -0500 From: Andy Sloane To: Torbjorn Kristoffersen Cc: freebsd-hackers@FreeBSD.org Subject: Re: new syscons screensaver Message-ID: <20010502142931.D19547@guild.guildsoftware.com> References: <20010502021600.A34130@cec.wustl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: ; from Torbjorn Kristoffersen on Wed, May 02, 2001 at 08:42:01PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 02, 2001 at 08:42:01PM +0200, Torbjorn Kristoffersen wrote: > What about implementing some code from green_saver into his saver to > enable DPMS support? And have a sysctl value to set the delay after the > green saver will begin :) Maybe there's a better way, to let his > beastie_saver.ko load green_saver.ko (and possibly unload itself) after a > specified delay? Actually, looking at the code, it would be very easy to do so. The only issue is how does one set the delay... sysctl would work, I suppose, and one could introduce a general sysctl variable for screensaver standby mode timeout or something, and then all the other screensavers could be updated. Or it could be handled by the underlying screensaver driver, which seems to make more sense to me, although I don't know much about it. (i.e. after the timeout expires, stop calling the scrn_saver_t "saver" function and perform a blank_display(V_DISPLAY_STAND_BY)...) -Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 12:45:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 5106637B424; Wed, 2 May 2001 12:45:20 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f42Jn4E14900; Wed, 2 May 2001 12:49:04 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200105021949.f42Jn4E14900@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Daniel Lang Cc: freebsd-hackers@freebsd.org, freebsd-quetions@freebsd.org Subject: Re: Kernel Console speed In-reply-to: Your message of "Wed, 02 May 2001 14:04:23 +0200." <20010502140423.B91287@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 May 2001 12:49:04 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The bootstraps works with 38400, (both boot2 and loader), > but as soon as the kernel boots, it switches back to 9600. You forgot to edit /etc/ttys to set the getty that runs on your console port to 38400 as well. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 13:26:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id 99FF637B422; Wed, 2 May 2001 13:26:32 -0700 (PDT) (envelope-from langd@informatik.tu-muenchen.de) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.24.91] HELO atrbg11.informatik.tu-muenchen.de ident: IDENT-NONSENSE [port 1715]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <113305-235>; Wed, 2 May 2001 22:26:25 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 274CC13667; Wed, 2 May 2001 22:26:18 +0200 (CEST) Date: Wed, 2 May 2001 22:26:18 +0200 From: Daniel Lang To: Mike Smith Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Kernel Console speed Message-ID: <20010502222618.A93572@atrbg11.informatik.tu-muenchen.de> References: <20010502140423.B91287@atrbg11.informatik.tu-muenchen.de> <200105021949.f42Jn4E14900@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105021949.f42Jn4E14900@mass.dis.org>; from msmith@freebsd.org on Wed, May 02, 2001 at 12:49:04PM -0700 X-Geek: GCS d-- s: a- C++ UB++++$ P+++$ L- E W+++(--) N+ o K w--- O? M- V@ PS+(++) PE--(+) Y+ PGP+ t++ 5@ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Mike, Mike Smith wrote on Wed, May 02, 2001 at 12:49:04PM -0700: > > The bootstraps works with 38400, (both boot2 and loader), > > but as soon as the kernel boots, it switches back to 9600. > > You forgot to edit /etc/ttys to set the getty that runs on your console > port to 38400 as well. No, I didn't, I even mentioned it: [..] > > What I did: > > set BOOT_COMCONSOLE_SPEED=38400 in /etc/make.conf > > set options CONSPEED=38400 in KERNEL > > compiled and installed kernel and new bootstrap (with disklabel). > > changed /etc/ttys to use std.38400 as argument to getty. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ And additionally, if it would have been the getty, the kernel boot messages would have been printed at the right speed. Thanks anyway, Daniel -- IRCnet: Mr-Spock - Eddie would go! - Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 13:58:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dargo.talarian.com (dargo.talarian.com [207.5.33.3]) by hub.freebsd.org (Postfix) with ESMTP id A85DF37B423 for ; Wed, 2 May 2001 13:58:20 -0700 (PDT) (envelope-from nsayer@talarian.com) Received: from moya.talarian.com (moya.talarian.com [10.4.10.8]) by dargo.talarian.com (Postfix) with ESMTP id DAE6222B15; Wed, 2 May 2001 13:56:13 -0700 (PDT) Received: from beast.talarian.com (beast.talarian.com [10.4.10.6]) by moya.talarian.com (Postfix) with ESMTP id E0DE56E; Wed, 2 May 2001 13:58:06 -0700 (PDT) Received: from talarian.com (localhost [127.0.0.1]) by beast.talarian.com (8.11.3/8.11.3) with ESMTP id f42Kw6795102; Wed, 2 May 2001 13:58:06 -0700 (PDT) (envelope-from nsayer@talarian.com) Message-ID: <3AF074DE.4D95E6B8@talarian.com> Date: Wed, 02 May 2001 13:58:06 -0700 From: Nick Sayer X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Hesford Cc: Andy Sloane , freebsd-hackers@FreeBSD.ORG Subject: Re: new syscons screensaver References: <20010502005000.B19547@guild.guildsoftware.com> <20010502021600.A34130@cec.wustl.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Hesford wrote: > However, I'm quite fond of the green_saver module, which shuts down my > monitor after 15 minutes. Other screensavers are really just for > entertainment; I think green_saver is the only one that serves a really > good purpose. You might consider trying the apm_saver module instead, especially on laptops. I have found instances in the past of monitor/BIOS/video combinations where green didn't do the right thing but that the APM got right. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 14:20:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beastie.saturn-tech.com (beastie.saturn-tech.com [207.229.19.136]) by hub.freebsd.org (Postfix) with ESMTP id 675A937B505 for ; Wed, 2 May 2001 14:20:45 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by beastie.saturn-tech.com (8.11.1/8.11.0) with ESMTP id f43DOo786159; Thu, 3 May 2001 07:24:50 -0600 (MDT) (envelope-from drussell@saturn-tech.com) X-Authentication-Warning: beastie.saturn-tech.com: drussell owned process doing -bs Date: Thu, 3 May 2001 07:24:50 -0600 (MDT) From: Doug Russell To: Andrew Hesford Cc: Andy Sloane , freebsd-hackers@FreeBSD.ORG Subject: Re: new syscons screensaver In-Reply-To: <20010502021600.A34130@cec.wustl.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 May 2001, Andrew Hesford wrote: > However, I'm quite fond of the green_saver module, which shuts down my > monitor after 15 minutes. Other screensavers are really just for > entertainment; I think green_saver is the only one that serves a really > good purpose. Perhaps we should make it so the green_saver can kick in after x minutes of the regular screensaver? Users would be used to this type of control. later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 14:24:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f45.law8.hotmail.com [216.33.241.45]) by hub.freebsd.org (Postfix) with ESMTP id 852A737B440 for ; Wed, 2 May 2001 14:24:42 -0700 (PDT) (envelope-from dominic_marks@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 2 May 2001 14:24:42 -0700 Received: from 194.72.9.37 by lw8fd.law8.hotmail.msn.com with HTTP; Wed, 02 May 2001 21:24:42 GMT X-Originating-IP: [194.72.9.37] From: "Dominic Marks" To: freebsd-hackers@freebsd.org Subject: KEvent doesnt return and KEvent sample troubles Date: Wed, 02 May 2001 21:24:42 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 02 May 2001 21:24:42.0455 (UTC) FILETIME=[4D52B670:01C0D34E] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been looking to start using the KEvent system and I've been experimenting with it. However I've been having several problems, with my own code as well as samples from http://www.flugsvamp.org. It appears I am able to create the correct structure's and register the events. However the event never returns and never responds to any action. For example if I use a sample which monitors the actions on a file I can read from, and write to the file and it shows no sign of noticing. I was wondering if it's simply a mistake of my own, however the failure for the samples I've found has puzzled my further. I'm working on a 4.3-STABLE machine using GCC version 2.95.3. Here is an example of code that I am using which doesn't seem to catch any events. Its a slightly modified version of read_test.c from flugsvamp.com which I edit so it would compile happily. It doesn't seem to work however. > #include #include #include #include #include #include #include #include #include #include #include main(int argc, char **argv) { int fd, kq, n; struct kevent event[1]; struct kevent *evp[1]; char buffer[128]; struct stat st; struct aiocb iocb; struct timespec ts = {0, 0}; if (argc != 2) errx(1, "Usage: %s file\n", argv[0]); fd = open(argv[1], O_RDONLY); if (fd < 0) err(1, "open: %s\n", argv[1]); lseek(fd, 0, SEEK_END); kq = syscall(SYS_kqueue); if (kq < 0) err(1, "kqueue"); event[0].ident = fd; event[0].filter = EVFILT_READ; event[0].flags = EV_ADD | EV_ENABLE; evp[0] = &event[0]; n = syscall(SYS_kevent, kq, 1, evp, 0, NULL, 0); for (;;) { n = syscall(SYS_kevent, kq, 0, NULL, 1, event, ts); if (n < 0) err(1, "kevent"); printf("kevent flags: 0x%x, data: 0x%x\n", event[0].flags, event[0].data); n = read(fd, buffer, 128); buffer[n] = '\0'; printf("%s", buffer); } } < I'd appreciate any feedback very much. Thank you Dominic Marks _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 14:33:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8721737B422 for ; Wed, 2 May 2001 14:33:41 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f42LXf813533; Wed, 2 May 2001 14:33:41 -0700 (PDT) Date: Wed, 2 May 2001 14:33:41 -0700 From: Alfred Perlstein To: Dominic Marks Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: KEvent doesnt return and KEvent sample troubles Message-ID: <20010502143340.U18676@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dominic_marks@hotmail.com on Wed, May 02, 2001 at 09:24:42PM -0000 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dominic Marks [010502 14:29] wrote: > I've been looking to start using the KEvent system and I've been > experimenting with it. However I've been having several problems, with my > own code as well as samples from http://www.flugsvamp.org. www.flugsvamp.org doesn't seem to resolve. > > It appears I am able to create the correct structure's and register the > events. However the event never returns and never responds to any action. > For example if I use a sample which monitors the actions on a file I can > read from, and write to the file and it shows no sign of noticing. > > I was wondering if it's simply a mistake of my own, however the failure for > the samples I've found has puzzled my further. I'm working on a 4.3-STABLE > machine using GCC version 2.95.3. > > Here is an example of code that I am using which doesn't seem to catch any > events. Its a slightly modified version of read_test.c from flugsvamp.com > which I edit so it would compile happily. > > It doesn't seem to work however. > [snip..] > kq = syscall(SYS_kqueue); > if (kq < 0) > err(1, "kqueue"); > > event[0].ident = fd; > event[0].filter = EVFILT_READ; > event[0].flags = EV_ADD | EV_ENABLE; > evp[0] = &event[0]; > n = syscall(SYS_kevent, kq, 1, evp, 0, NULL, 0); uh, what the heck? Why not just use the kqueue call directly like the manpage explains? I think you have the arguments to kevent() wrong. -- -Alfred Perlstein - [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 14:40: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-26.dsl.lsan03.pacbell.net [63.207.60.26]) by hub.freebsd.org (Postfix) with ESMTP id BF1C637B423; Wed, 2 May 2001 14:40:04 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0CFEA678A1; Wed, 2 May 2001 14:40:04 -0700 (PDT) Date: Wed, 2 May 2001 14:40:03 -0700 From: Kris Kennaway To: John Baldwin Cc: Andy Sloane , freebsd-hackers@FreeBSD.org Subject: Re: new syscons screensaver Message-ID: <20010502144003.A86801@xor.obsecurity.org> References: <20010502005000.B19547@guild.guildsoftware.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Wed, May 02, 2001 at 11:27:46AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 02, 2001 at 11:27:46AM -0700, John Baldwin wrote: >=20 > On 02-May-01 Andy Sloane wrote: > > Hello, > >=20 > > I just wrote a new syscons screensaver which I think is much more > > interesting than the other ones, while still being relatively easy on t= he > > CPU (much less CPU intensive than "fire", anyway). Please review it and > > let me know what you think. > >=20 > > It's the bsd daemon logo (with much editing, thanks to my coworker Wayl= on) > > floating (with a realtime shadow!) above a bunch of tiled spheres which > > move around and morph. It's only one palette change per frame, until t= he > > bsd daemon moves. > >=20 > > http://fear.incarnate.net/~andude/balls.tar.gz > >=20 > > I'm not on this list, so please reply directly to me. Thanks. Looks great; please submit this as a PR. Kris --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE68H6zWry0BWjoQKURAtovAJ9Kp5Iyu3rqo5sZL3k6FgSbrYwzzwCgzPOD lyhhPTRV8xzFbF4UVIvi1Vk= =/esO -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 14:47:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from temphost.dragondata.com (temphost.dragondata.com [63.167.131.128]) by hub.freebsd.org (Postfix) with ESMTP id 658B637B422 for ; Wed, 2 May 2001 14:47:17 -0700 (PDT) (envelope-from toasty@temphost.dragondata.com) Received: (from toasty@localhost) by temphost.dragondata.com (8.9.3/8.9.3) id QAA00364; Wed, 2 May 2001 16:49:32 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200105022149.QAA00364@temphost.dragondata.com> Subject: NMI during procfs mem reads (#2) To: hackers@freebsd.org Date: Wed, 2 May 2001 16:49:27 -0500 (CDT) Cc: kevind@ikadega.com X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried sending this from my work account, but our new exchange server isn't exactly sending mail correctly... Excuse the duplicate post if you see it. :) -- Kevin -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We're working on a custom PCI card, that on occasion requires several retries to complete a read (talking to a very slow device). We had a small bug that would cause it to retry forever, if the device never responded. It seems that our PCI chipset generates an NMI if the PCI retry limit is hit. That's OK with us, except that if the read is going through procfs_rwmem, we get a kernel trap. If we run a test that attempts to do a read from a PCI mmap()ed memory register that will retry forever, without using GDB, we get: NMI ISA b0, EISA ff RAM parity error, likely hardware failure. Followed by a bus error. This is exactly what we'd expect to happen, and I'm happy with that. If we run the exact same code through gdb (which seems to use procfs somehow) we get: Fatal trap 19: non-maskable interrupt trap while in kernel mode instruction pointer = 0x8:0xc0306860 stack pointer = 0x10:0xede2ce28 frame pointer = 0x10:0xede2ce54 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 211 (gdb) interrupt mask = none Program received signal SIGEMT, Emulation trap. 0xc0306860 in generic_bcopy () (kgdb) bt #0 0xc0306860 in generic_bcopy () #1 0xede2cf0c in ?? () #2 0xc01dbe55 in procfs_rwmem (curp=0xeca5b560, p=0xeca5b3c0, uio=0xede2cf0c) at ../../miscfs/procfs/procfs_mem.c:208 #3 0xc01dbf48 in procfs_domem (curp=0xeca5b560, p=0xeca5b3c0, pfs=0x0, uio=0xede2cf0c) at ../../miscfs/procfs/procfs_mem.c:264 #4 0xc01b83b9 in ptrace (curp=0xeca5b560, uap=0xede2cf80) at ../../kern/sys_process.c:399 #5 0xc0307f29 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 675283088, tf_esi = 0, tf_ebp = -1077938072, tf_isp = -303902764, tf_ebx = 675283088, tf_edx = 673855764, tf_ecx = 1, tf_eax = 26, tf_trapno = 7, tf_err = 2, tf_eip = 673315836, tf_cs = 31, tf_eflags = 518, tf_esp = - -1077938148, tf_ss = 47}) at machine/smp.h:190 #6 0xc02fc3b5 in Xint0x80_syscall () Is it supposed to work this way? pcib0: on motherboard pci0: on pcib0 pcib1: at device 8.0 on pci0 pci1: on pcib1 ikapci0: mem 0xb4000000-0xb7ffffff,0xc0000000-0xdfffffff irq 11 at device 9.0 on pci1 -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.5.3 iQA/AwUBOvBFHc0YFqTZRQvqEQKjaQCeM/oZScd+FkHMV63ia0rgC5LAcfQAoKIx +1YDufmdbiTBK+J8/IIl46sj =LbQh -----END PGP SIGNATURE----- -- Kevin Day toasty@dragondata.com - kevin@stileproject.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 14:48: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.guildsoftware.com (guild.guildsoftware.com [207.67.51.35]) by hub.freebsd.org (Postfix) with ESMTP id 5059E37B422 for ; Wed, 2 May 2001 14:48:01 -0700 (PDT) (envelope-from andude@guild.guildsoftware.com) Received: (from andude@localhost) by guild.guildsoftware.com (8.9.3/8.9.3) id QAA27210; Wed, 2 May 2001 16:47:49 -0500 Date: Wed, 2 May 2001 16:47:49 -0500 From: Andy Sloane To: Nick Sayer Cc: Andrew Hesford , freebsd-hackers@FreeBSD.org Subject: Re: new syscons screensaver Message-ID: <20010502164749.E19547@guild.guildsoftware.com> References: <20010502005000.B19547@guild.guildsoftware.com> <20010502021600.A34130@cec.wustl.edu> <3AF074DE.4D95E6B8@talarian.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: <3AF074DE.4D95E6B8@talarian.com>; from Nick Sayer on Wed, May 02, 2001 at 01:58:06PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 02, 2001 at 01:58:06PM -0700, Nick Sayer wrote: > You might consider trying the apm_saver module instead, especially on > laptops. I have found instances in the past of monitor/BIOS/video > combinations where green didn't do the right thing but that the APM got > right. Both apm_saver and green_saver are essentially (once you get past all the screensaver setup code) one-line routines to turn off the display. I think it would make sense to both tell the VGA chip to blank (green_saver) and tell APM to shut down (apm_saver) with proper #ifdeffing around the APM stuff. I also think it would make sense to do this inside dev/fb/splash.c (or perhaps dev/syscons/syscons.c) instead of inside each screensaver, so that it's automatically handled. And maybe a new 'vidcontrol' option to set the blanking delay (as opposed to the screensaver delay) would be necessary. There may be an even better place to put this, but I am mostly unfamiliar with the kernel source tree and as such I won't attempt to write a patch for this yet. -Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 14:57:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f135.law8.hotmail.com [216.33.241.135]) by hub.freebsd.org (Postfix) with ESMTP id 0D4C037B43C for ; Wed, 2 May 2001 14:57:31 -0700 (PDT) (envelope-from dominic_marks@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 2 May 2001 14:57:31 -0700 Received: from 194.72.9.37 by lw8fd.law8.hotmail.msn.com with HTTP; Wed, 02 May 2001 21:57:30 GMT X-Originating-IP: [194.72.9.37] From: "Dominic Marks" To: bright@wintelcom.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: KEvent doesnt return and KEvent sample troubles Date: Wed, 02 May 2001 21:57:30 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 02 May 2001 21:57:31.0014 (UTC) FILETIME=[E2ACFA60:01C0D352] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >* Dominic Marks [010502 14:29] wrote: > > I've been looking to start using the KEvent system and I've been > > experimenting with it. However I've been having several problems, with >my > > own code as well as samples from http://www.flugsvamp.org. > >www.flugsvamp.org doesn't seem to resolve. Yes, a mistake on my part. It should have been flugsvamp.com. > > > > > It appears I am able to create the correct structure's and register the > > events. However the event never returns and never responds to any >action. > > For example if I use a sample which monitors the actions on a file I can > > read from, and write to the file and it shows no sign of noticing. > > > > I was wondering if it's simply a mistake of my own, however the failure >for > > the samples I've found has puzzled my further. I'm working on a >4.3-STABLE > > machine using GCC version 2.95.3. > > > > Here is an example of code that I am using which doesn't seem to catch >any > > events. Its a slightly modified version of read_test.c from >flugsvamp.com > > which I edit so it would compile happily. > > > > It doesn't seem to work however. > > > >[snip..] > > > kq = syscall(SYS_kqueue); > > if (kq < 0) > > err(1, "kqueue"); > > > > event[0].ident = fd; > > event[0].filter = EVFILT_READ; > > event[0].flags = EV_ADD | EV_ENABLE; > > evp[0] = &event[0]; > > n = syscall(SYS_kevent, kq, 1, evp, 0, NULL, 0); > >uh, what the heck? Why not just use the kqueue call directly like >the manpage explains? I think you have the arguments to kevent() >wrong. > I just copied the example directly here so I couldn't comment absolute on the decisions here. Having browsed through the man page I've edited the original sample, moving some of the arguments around - where these ever moved one way and since changed perhaps? However what I believe to be correct now equally refuses to respond. Updated: > #include #include #include #include #include #include #include #include #include #include #include main(int argc, char **argv) { int fd, kq, n; struct kevent event[1]; struct kevent *evp[1]; char buffer[128]; struct stat st; struct aiocb iocb; struct timespec ts = {0, 0}; if (argc != 2) errx(1, "Usage: %s file\n", argv[0]); fd = open(argv[1], O_RDONLY); if (fd < 0) err(1, "open: %s\n", argv[1]); lseek(fd, 0, SEEK_END); kq = kqueue(); if (kq < 0) err(1, "kqueue"); event[0].ident = fd; event[0].filter = EVFILT_READ; event[0].flags = EV_ADD | EV_ENABLE; evp[0] = &event[0]; n = kevent(kq, *evp, 1, NULL, 0, &ts); for (;;) { n = kevent(kq, 0, NULL, event, 1, NULL); if (n < 0) err(1, "kevent"); printf("kevent flags: 0x%x, data: 0x%x\n", event[0].flags, event[0].data); n = read(fd, buffer, 128); buffer[n] = '\0'; printf("%s", buffer); } } < >-- >-Alfred Perlstein - [alfred@freebsd.org] >Instead of asking why a piece of software is using "1970s technology," >start asking why software is ignoring 30 years of accumulated wisdom. Thanks again Dominic Marks _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 15:13:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 158F237B422 for ; Wed, 2 May 2001 15:13:35 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f42MCkG47845; Wed, 2 May 2001 15:13:16 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010502164749.E19547@guild.guildsoftware.com> Date: Wed, 02 May 2001 15:12:04 -0700 (PDT) From: John Baldwin To: Andy Sloane Subject: Re: new syscons screensaver Cc: freebsd-hackers@FreeBSD.org, Andrew Hesford , Nick Sayer Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-May-01 Andy Sloane wrote: > On Wed, May 02, 2001 at 01:58:06PM -0700, Nick Sayer wrote: >> You might consider trying the apm_saver module instead, especially on >> laptops. I have found instances in the past of monitor/BIOS/video >> combinations where green didn't do the right thing but that the APM got >> right. > > Both apm_saver and green_saver are essentially (once you get past all the > screensaver setup code) one-line routines to turn off the display. I think > it would make sense to both tell the VGA chip to blank (green_saver) and > tell APM to shut down (apm_saver) with proper #ifdeffing around the APM > stuff. > > I also think it would make sense to do this inside dev/fb/splash.c (or > perhaps dev/syscons/syscons.c) instead of inside each screensaver, so that > it's automatically handled. And maybe a new 'vidcontrol' option to set the > blanking delay (as opposed to the screensaver delay) would be necessary. > There may be an even better place to put this, but I am mostly unfamiliar > with the kernel source tree and as such I won't attempt to write a patch > for this yet. You could just add new ioctl's to do this the same way that vidcontrol does settings now. This approach does sound the most sensible to me, FWIW, as it avoids duplicating code all over the place. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 15:52:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from karon.dynas.se (karon.dynas.se [192.71.43.4]) by hub.freebsd.org (Postfix) with SMTP id 2685837B423 for ; Wed, 2 May 2001 15:52:55 -0700 (PDT) (envelope-from mikko@dynas.se) Received: (qmail 41469 invoked from network); 2 May 2001 22:51:54 -0000 Received: from spirit.sto.dynas.se (HELO spirit.dynas.se) (172.16.1.10) by 172.16.1.1 with SMTP; 2 May 2001 22:51:54 -0000 Received: (qmail 1867 invoked from network); 2 May 2001 22:52:57 -0000 Received: from explorer.rsa.com (10.81.217.59) by spirit.dynas.se with SMTP; 2 May 2001 22:52:57 -0000 Received: (from mikko@localhost) by explorer.rsa.com (8.11.3/8.11.1) id f42MpsH64241; Wed, 2 May 2001 15:51:54 -0700 (PDT) (envelope-from mikko) Date: Wed, 2 May 2001 15:51:54 -0700 (PDT) From: Mikko Tyolajarvi Message-Id: <200105022251.f42MpsH64241@explorer.rsa.com> To: dominic_marks@hotmail.com Cc: hackers@freebsd.org Subject: Re: KEvent doesnt return and KEvent sample troubles Newsgroups: local.freebsd.hackers References: X-Newsreader: NN version 6.5.6 (NOV) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In local.freebsd.hackers you write: >>* Dominic Marks [010502 14:29] wrote: >> > I've been looking to start using the KEvent system and I've been >> > experimenting with it. However I've been having several problems, with >>my >> > own code as well as samples from http://www.flugsvamp.org. >> >>www.flugsvamp.org doesn't seem to resolve. >Yes, a mistake on my part. It should have been flugsvamp.com. [...] >I just copied the example directly here so I couldn't comment absolute on >the decisions here. Having browsed through the man page I've edited the >original sample, moving some of the arguments around - where these ever >moved one way and since changed perhaps? However what I believe to be >correct now equally refuses to respond. Works here (4.3-RC, Apr 19), provided that you append to the file. If you just overwrite it with the same amount of data, read() will return zero, and you get no output. Check out the source for tail(1) for a more complete example (in /usr/src/usr.bin/tail/forward.c) $.02, /Mikko -- Mikko Työläjärvi_______________________________________mikko@rsasecurity.com RSA Security To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 16: 0:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 19A2137B423; Wed, 2 May 2001 16:00:21 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f42MuoV01721; Wed, 2 May 2001 15:56:50 -0700 (PDT) Message-ID: <3AF090AF.31215A1C@isi.edu> Date: Wed, 02 May 2001 15:56:47 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: Daniel Lang Cc: Mike Smith , freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Kernel Console speed References: <20010502140423.B91287@atrbg11.informatik.tu-muenchen.de> <200105021949.f42Jn4E14900@mass.dis.org> <20010502222618.A93572@atrbg11.informatik.tu-muenchen.de> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms39411D44F8AD59C61007E6E0" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms39411D44F8AD59C61007E6E0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Daniel Lang wrote: > > > What I did: > > > set BOOT_COMCONSOLE_SPEED=38400 in /etc/make.conf > > > set options CONSPEED=38400 in KERNEL > > > compiled and installed kernel and new bootstrap (with disklabel). > > > changed /etc/ttys to use std.38400 as argument to getty. "Me, too." Same thing, just with 115200 instead of 38400, and on 4.2-RELEASE. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------ms39411D44F8AD59C61007E6E0 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAxMDUwMjIyNTY0OVowIwYJKoZIhvcNAQkEMRYE FI8s039VVCDr8OCisoMVkXcqn4d1MFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGAcLq5ZnjQhXihf2RYRWKF77OasPjNTDr2T8D5bK38CppaXnrwvvqm k8lccjmoDxmULXgel/8iNi/wuyEZkVaBMgIuCitgCS9ewNMflctTO70nQospBEkSNVEN+sp7 rwClR7lR4yJGY72Z2jTI6LFyGz8ClbiOevHUNP1XcWJpee0= --------------ms39411D44F8AD59C61007E6E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 16:49:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from softweyr.com (mail.dobox.com [208.187.122.44]) by hub.freebsd.org (Postfix) with ESMTP id 3BA1937B423 for ; Wed, 2 May 2001 16:49:25 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=2d30ffc1ee241b6ab4b50c9e48679bcd) by softweyr.com with esmtp (Exim 3.16 #1) id 14uyAi-00005t-00; Wed, 02 May 2001 09:04:08 -0600 Message-ID: <3AF021E8.F2F58D2F@softweyr.com> Date: Wed, 02 May 2001 09:04:08 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Nick Rogness Cc: John Wilson , freebsd-hackers@FreeBSD.ORG Subject: Re: ipfw routing/netmask problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Rogness wrote: > > On Mon, 30 Apr 2001, John Wilson wrote: > > This probably belongs on freebsd-net or freebsd-questions. -questions, please. -net is for discussing FreeBSD networking code, not for configuration problems. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 16:49:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from softweyr.com (mail.dobox.com [208.187.122.44]) by hub.freebsd.org (Postfix) with ESMTP id 6574537B424; Wed, 2 May 2001 16:49:26 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=ada25448f5bb7769debaedab93916bea) by softweyr.com with esmtp (Exim 3.16 #1) id 14uTvy-0000AT-00; Tue, 01 May 2001 00:46:54 -0600 Message-ID: <3AEE5BDE.ACB3F3A5@softweyr.com> Date: Tue, 01 May 2001 00:46:54 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matt Dillon Cc: =?iso-8859-1?Q?Jes=FAs=20Arn=E1iz?= , questions@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: NAT and IPFiltering References: <200104262321.f3QNLpx61257@earth.backplane.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > > :Hi! > : > :I'm configuring a server able to do NAT and IP FILTERING (IPF). > : > :What are the required options that I should set to the kernel? > : > :I have this: > :... > :Jesús Arnáiz > > I think all you need is: > > options IPFIREWALL > options IPDIVERT Those are for ipfw/natd. For ipfilter, you need: > I usually also have (because it is useful): > > options IPFILTER If you want to use ipmon to log ipf actions, you'll need: options IPFILTER_LOG The default state in ipf is open, you can change it to block with: options IPFILTER_DEFAULT_BLOCK That's it. ipnat uses ipfilter in the kernel and requires only the IPFILTER option. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 16:49:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from softweyr.com (mail.dobox.com [208.187.122.44]) by hub.freebsd.org (Postfix) with ESMTP id C248537B43C for ; Wed, 2 May 2001 16:49:26 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=624d138e1d0485dff1774b5ecca87d95) by softweyr.com with esmtp (Exim 3.16 #1) id 14uT4u-000071-00; Mon, 30 Apr 2001 23:52:04 -0600 Message-ID: <3AEE4F04.B1CDDAE8@softweyr.com> Date: Mon, 30 Apr 2001 23:52:04 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Michael C . Wu" Cc: Remy Nonnenmacher , keichii@iteration.net, ajh3@chmod.ath.cx, jgowdy@home.com, freebsd-hackers@FreeBSD.ORG Subject: Re: x86-64 Hammer and IA64 Itainium References: <20010426180836.C88522@peorth.iteration.net> <200104271108.f3RB81C63528@luxren2.boostworks.com> <20010427104703.G88522@peorth.iteration.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Michael C . Wu" wrote: > > .... > You've just ruined any real reason for me to continue my education > as a computer architecture student.... :P > "Let all the computer scientists design the CPU and hope that > they take into account the electromagnetic effects!!" Er, turn this around to: design the system so the software will actually run quickly on it. This was the design goal of RISC, and it moved a giant leap towards that goal, as long as memory was as fast as the processor. Now that processors outpace their memory subsystems by many times, it's probably time to start going the other direction again. This time hopefully we'll do it intelligently. There's your reason for sticking around. > | Now imagine you get a fully programmable add-on card. If something get > | wrong, the device driver writer can fix it and not just put hacks to > | handle this or this revision of a chip. Even further, computation part > | of the DD can be pushed onto the card. Imagine a NIC pushing you mbufs, > | pcb entries, etc... You will also not have to wait for the good willing > | of XYZ company to release documentation or seeing a version of a chip > | being phased out in favor of the new super-one released only with an > | opaque Windows driver. > > Can you picture the difficulty of writing drivers for these > devices that do so many specific things? I am sure Bill Paul, > Mike Smith, et al. will be so thrilled to read thousands of pages > of documentation to write one driver..... > Engineering is about K.I.S.S., not making it very complicated for > everyone involved. Snort. You should look inside a layer 3 (or higher) switch. Queueing engines with 16K - 64K queues, multiple queues per port, with programmable priorities per-queue/per-port, programmable thresholds per queue, auto- magic buffer management, etc., etc., all in the hardware. If you think that's exotic, wait'll the next generation of hardware firewalls enters the field. That'll be a heyday. Engineering: building something that customers want to buy, that can be produced profitably. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 16:49:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 430E637B43F for ; Wed, 2 May 2001 16:49:35 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id f42NnVP84816; Wed, 2 May 2001 16:49:31 -0700 (PDT) Date: Wed, 2 May 2001 16:49:30 -0700 (PDT) From: Doug White To: Dominic Marks Cc: Subject: Re: KEvent doesnt return and KEvent sample troubles In-Reply-To: Message-ID: X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 May 2001, Dominic Marks wrote: > I've been looking to start using the KEvent system and I've been > experimenting with it. However I've been having several problems, with my > own code as well as samples from http://www.flugsvamp.org. > > It appears I am able to create the correct structure's and register the > events. However the event never returns and never responds to any action. > For example if I use a sample which monitors the actions on a file I can > read from, and write to the file and it shows no sign of noticing. For that you want status change notifications. You've registerted just a simple read() notification a la select(), which will trigger until you've read the entire file then stop. You might find this more interesting if you point it at a named pipe then use something to stuff data down it. Take a look at the EVFILT_VNODE type in the kqueue(2) manpage. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 17: 8:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by hub.freebsd.org (Postfix) with ESMTP id 666AB37B422 for ; Wed, 2 May 2001 17:08:37 -0700 (PDT) (envelope-from jwd@bsdwins.com) Received: (from jwd@localhost) by bsdone.bsdwins.com (8.11.3/8.11.0) id f4308Ud11401; Wed, 2 May 2001 20:08:30 -0400 (EDT) (envelope-from jwd) Date: Wed, 2 May 2001 20:08:30 -0400 From: John To: Andy Sloane Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: new syscons screensaver Message-ID: <20010502200830.A11324@bsdwins.com> References: <20010502005000.B19547@guild.guildsoftware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010502005000.B19547@guild.guildsoftware.com>; from andy@guildsoftware.com on Wed, May 02, 2001 at 12:50:00AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This looks pretty good, and it seems to be getting good comments. It seems that you either need to file a PR or have a committer volunteer to get it in the tree. Any takers? I may have some spare time later this weekend. -john ----- Andy Sloane's Original Message ----- > Hello, > > I just wrote a new syscons screensaver which I think is much more > interesting than the other ones, while still being relatively easy on the > CPU (much less CPU intensive than "fire", anyway). Please review it and > let me know what you think. > > It's the bsd daemon logo (with much editing, thanks to my coworker Waylon) > floating (with a realtime shadow!) above a bunch of tiled spheres which > move around and morph. It's only one palette change per frame, until the > bsd daemon moves. > > http://fear.incarnate.net/~andude/balls.tar.gz > > I'm not on this list, so please reply directly to me. Thanks. > > -Andy > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 19:14: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 0C4F437B424 for ; Wed, 2 May 2001 19:14:05 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f432Drf74664; Wed, 2 May 2001 21:13:53 -0500 (CDT) (envelope-from jlemon) Date: Wed, 2 May 2001 21:13:53 -0500 (CDT) From: Jonathan Lemon Message-Id: <200105030213.f432Drf74664@prism.flugsvamp.com> To: dominic_marks@hotmail.com, hackers@freebsd.org Subject: Re: KEvent doesnt return and KEvent sample troubles X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >I've been looking to start using the KEvent system and I've been >experimenting with it. However I've been having several problems, with my >own code as well as samples from http://www.flugsvamp.org. AAARGH. /me hastily goes and removes that example directory. Sorry about that; those examples were correct during the initial kqueue development, and haven't been updated to reflect reality. I'll put the examples back up after I've corrected them to work with the current version of FreeBSD. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 21:20: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 588FD37B423; Wed, 2 May 2001 21:19:59 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f42N8Pl00912; Wed, 2 May 2001 16:08:41 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200105022308.f42N8Pl00912@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Lars Eggert Cc: Daniel Lang , Mike Smith , freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Kernel Console speed In-reply-to: Your message of "Wed, 02 May 2001 15:56:47 PDT." <3AF090AF.31215A1C@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 May 2001 16:08:25 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Daniel Lang wrote: > > > > What I did: > > > > set BOOT_COMCONSOLE_SPEED=38400 in /etc/make.conf > > > > set options CONSPEED=38400 in KERNEL > > > > compiled and installed kernel and new bootstrap (with disklabel). > > > > changed /etc/ttys to use std.38400 as argument to getty. > > "Me, too." > > Same thing, just with 115200 instead of 38400, and on 4.2-RELEASE. You don't want to set CONSPEED in the kernel config, or change the loader configuration. Just build/install boot1/boot2 with a new BOOT_COMCONSOLE_SPEED, and ensure that /etc/ttys is correctly set for your desired console rate. This works. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 2 22:19:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cslab.csie.ntu.edu.tw (cslab.csie.ntu.edu.tw [140.112.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 21F7D37B423 for ; Wed, 2 May 2001 22:19:23 -0700 (PDT) (envelope-from r88074@csie.ntu.edu.tw) Received: from hornets (hornets.csie.ntu.edu.tw [140.112.30.134]) by cslab.csie.ntu.edu.tw (8.9.3/8.9.3) with SMTP id NAA17179 for ; Thu, 3 May 2001 13:18:57 +0800 (CST) Message-Id: <200105030518.NAA17179@cslab.csie.ntu.edu.tw> From: "ªL­^¶W" To: "Freebsd-Hackers" Subject: Command like "sar" on solaris ???? Date: Thu, 3 May 2001 13:17:37 +0800 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear all: I want to know buffer cache hit ratio on Freebsd , I know the command "sar" on solaris has the fuction, But It doesn't appear on FreeBSD. Is there the same function command on FreeBSD . Please tell me , Thanks Richard_Lin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 1: 2:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f57.law8.hotmail.com [216.33.241.57]) by hub.freebsd.org (Postfix) with ESMTP id BB24C37B43C for ; Thu, 3 May 2001 01:02:18 -0700 (PDT) (envelope-from dominic_marks@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 3 May 2001 01:02:18 -0700 Received: from 194.72.9.37 by lw8fd.law8.hotmail.msn.com with HTTP; Thu, 03 May 2001 08:02:18 GMT X-Originating-IP: [194.72.9.37] From: "Dominic Marks" To: freebsd-hackers@freebsd.org Subject: Re: KEvent doesnt return and KEvent sample tr...  Date: Thu, 03 May 2001 08:02:18 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 03 May 2001 08:02:18.0714 (UTC) FILETIME=[5FD493A0:01C0D3A7] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Many thanks. I see where I was going wrong now. Dominic Marks _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 1:20:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.kebne.se (mail.kebne.se [212.209.134.151]) by hub.freebsd.org (Postfix) with ESMTP id 1A92937B422; Thu, 3 May 2001 01:20:53 -0700 (PDT) (envelope-from gunnar.olsson@xelerated.com) Received: by mail.kebne.se with Internet Mail Service (5.5.2653.19) id ; Thu, 3 May 2001 10:20:49 +0200 Message-ID: <31A473DBB655D21180850008C71E251A031AAF3A@mail.kebne.se> From: Gunnar Olsson To: "Freebsd Net (E-mail)" , "Freebsd Hackers (E-mail)" Subject: how to use netgraph? Date: Thu, 3 May 2001 10:20:45 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I have a process in user space, that wants to send a packet direct on the ethernet, not encapsulate the packet in IP. When I read about netgraph, it looks like it possible to do, or? When I hook to a upper or a lower hook, does the kernel create the ethernet header, or do I have to create the ethernet header in the user process myself before sending down? If the kernal is adding the ethernet header, what is actually sent out on the wire? Usaully an ARPLOOKUP is done and maps the IP dst to a MAC dst, but now I do not have the IP header. How to get the MAC dst field filled in? If someone has an example how to write a small program that using the netgragh to sent a packet down via an hook, I would be so happy if you could send that to me:-) Best Regards Gunnar ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Gunnar Olsson Phone: +46 8 5062 5762 Xelerated Packet Devices AB Fax: +46 8 5455 3211 Regeringsgatan 67 Mobile: +46 73 3279765 SE-10386 Stockholm Web: http://www.xelerated.com Email: mailto:gunnar.olsson@xelerated.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 2:35: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay01.putra.net.my (relay01.putra.net.my [202.9.64.92]) by hub.freebsd.org (Postfix) with ESMTP id 4789937B424 for ; Thu, 3 May 2001 02:34:57 -0700 (PDT) (envelope-from crystal_243@trans-usa.com) Received: from mailsvr.klhchem.com.my (pop.suncorp.com.my [202.9.67.14]) by relay01.putra.net.my (8.11.0/8.11.0) with ESMTP id f438our10131; Thu, 3 May 2001 16:50:56 +0800 Received: from trans-usa.com ([192.168.0.4]) by mailsvr.klhchem.com.my (Lotus Domino Release 5.0.4) with SMTP id 2001050218013118:2440 ; Wed, 2 May 2001 18:01:31 +0800 Message-ID: <00002a1428b7$00004786$00001a2c@trans-usa.com> To: From: crystal_243@trans-usa.com Subject: RE: inquiry 6700 Date: Wed, 02 May 2001 03:06:51 -0700 MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MIMETrack: Itemize by SMTP Server on mailsvr/klhchem/my(Release 5.0.4 |June 8, 2000) at 05/02/2001 06:01:33 PM, Serialize by Router on mailsvr/klhchem/my(Release 5.0.4 |June 8, 2000) at 05/03/2001 04:39:07 PM, Serialize complete at 05/03/2001 04:39:07 PM Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Take Control Of Your Conference Calls

Long Distance Conferencing
Only 18 Cents Per Minute

Connects Up To 100 Participants!<= /FONT>

<= /TABLE>

  • No setup fees
  • No contracts or monthly fees
  • Call anytime, from anywhere, to anywhere
  • International Dial In 18 cents per minute
  • Simplicity in set up and administration
  • Operator Help available 24/7
    • G= et the best quality, the easiest to use, and lowest rate in the industry.

    If you like saving m= oney, fill out the form below and one of our consultants will contact you.

    Required Input Field*

    Name*
    Web Address*
    Company Name*
    Web Address*
    Business Phone*
    Home Phone
    Email Address*
    Type of Business

    This email is to those persons that have contacted Conferen= ce Calls for Less regarding available services or product information. If thi= s email is reaching you in error and you feel that you have not contac= ted us, C= lick here. We will gladly remove you from our mailing list.

    To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 2:41:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id 8163E37B423 for ; Thu, 3 May 2001 02:41:15 -0700 (PDT) (envelope-from Jan.Grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Thu, 3 May 2001 10:40:56 +0100 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 14vFax-0005b9-00; Thu, 03 May 2001 10:40:23 +0100 Date: Thu, 3 May 2001 10:40:23 +0100 (BST) From: Jan Grant To: Andrew Hesford Cc: Andy Sloane , freebsd-hackers Subject: Re: new syscons screensaver In-Reply-To: <20010502021600.A34130@cec.wustl.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Very neat. [forgive flippancy] On Wed, 2 May 2001, Andrew Hesford wrote: > The screensaver isn't bad, and it gets pretty trippy when you focus at > infinity and let the 3D-Illusions (TM) effect set in. Argh! I've just gone blind. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287163 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk YKYBPTMRogueW... you try to move diagonally in vi. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 3:15:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dnull.com (dnull.com [209.133.53.79]) by hub.freebsd.org (Postfix) with ESMTP id 90BC037B43F for ; Thu, 3 May 2001 03:14:57 -0700 (PDT) (envelope-from jessem@jigsaw.svbug.com) Received: from jigsaw.svbug.com ([198.79.110.2]) by dnull.com (8.8.8/8.8.8) with ESMTP id DAA08946; Thu, 3 May 2001 03:15:25 -0700 (PDT) Message-Id: <200105031015.DAA08946@dnull.com> Date: Thu, 3 May 2001 03:14:44 -0700 (PDT) From: jessem@livecam.com Reply-To: jessemonroy@email.com Subject: Re: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com] To: jkh@osd.bsdi.com Cc: hackers@freebsd.org In-Reply-To: <20010502220847.A84247@mooseriver.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan, I don't buy this story for a moment. You should expect SVBUG not to either. This can only be classified as: A) A poor excuse for a coverup (for some unknown reason) B) Major incompetence (in which someone should resign) C) Aliens have landed If as you say, it has been known since the 20th of April, 2001, then the world (and FreeBSD) has plenty of channels for communications. Windriver has a website, it is un-affected by FreeBSD traffic. BSDi has a website, it is un-affected by FreeBSD traffic. Daemonnews has a website.... Do I need continue? Best Regards, Jessem. > To: announce@FreeBSD.ORG > Subject: ANNOUNCE: Status update on ftp.freebsd.org AKA ftp.freesoftware.com > X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) > Date: Wed, 02 May 2001 20:58:09 -0700 > From: Jordan Hubbard > > Hi folks, > > This is just a short note to discuss the current state of affairs with > our master FTP site, explain what we're doing about it and combat some > of the FUD floating around which has everyone from space aliens to > Wind River Systems (who supply the space aliens with navigational > software, of course) intentionally killing the site off. > > On April 20th, 2001, the day that FreeBSD 4.3 was due to be released, > we lost access to our main FTP site, ftp.freesoftware.com, without any > advance warning. Further investigation revealed that the problem was > due to an unforeseen network outage which caused the hosting ISP to > have to block access to the site. With one of their major links down, > it was overloading the ISPs backup links and denying bandwidth to > their other customers. > > It was also not clear to us, then or now, just how long the outage > would last and whether this was to be a short-term or a long-term > problem. With the release date for 4.3 already well publicized in > advance and many people asking me for it, I decided to use one of our > backup sites, the usw[1-6].freebsd.org cluster, and at least get the > current releases bits up somewhere on an interim basis. > > Unfortunately, I really underestimated both the extent of the demand > and the degree to which our big, fat Gigabit pipe at ftp.freesoftware.com > has made distributing the bits to our mirrors look comparatively easy. > Even with the login limits set *significantly* greater in favor of the > registered mirror sites, and with multiple machines pulling the load, > it quickly overwhelmed the new hosting infrastructure and resulted in > significant bandwidth limiting on FTP traffic being instituted by the > ISP. Even delaying the official announcement by 24 hours had no > measurable effect on the overload since word of mouth and anticipation > had already built demand beyond the saturation point. > > In short, what many of us have suspected for years turned out to be > proven rather abruptly true: The FreeBSD.org services infrastructure > has become overly reliant on resources which constitute single points > of failure and lacks both sufficient tiering and redundancy in the > face of such failure. We lost a key FTP resource and our entire > distribution service essentially collapsed. The same may be true for > CVSup, mail and WWW services and that's something we definitely need > to look at. > > For now, the most critical item is to finish implementing the > discussed-but-not-implemented ftp-master site scheme. A machine to > serve as the project's "master FTP host" has been procured will > shortly be available for FTP access. ONLY mirror sites will be > allowed to connect to it, and it will always be pre-loaded with > release bits, CERT advisories and anything else which requires the > mirrors to have a head-start in advance of any public announcement. > Announcements will only be made after a hand-inspection of the mirror > sites reveals that a significant degree of propagation has taken place > from the master site and not beforehand. > > What people currently regard as "ftp.freebsd.org" will become another > tier of sites, probably served in round-robin DNS fashion, which have > all agreed to meet the minimum requirements for being "full and > complete mirrors" of the bits offered from ftp-master.freebsd.org. > Existing mirror sites which wish to maintain only a subset of the > master bits will become clients of these second-tier sites and subject > to whatever distribution policies they institute. It would be my > expectation that certain 2nd-tier sites will also have mirror access > lists which favor the 3rd-tier sites over end-users, but that's a > detail to be worked out over time. > > It's also not clear what, if anything, needs to be done to make sites > like www.freebsd.org and hub.freebsd.org more reliable in the face of > failure, but people can certainly expect that a good deal of thought > will be going into answering those questions over the next few weeks. > > It certainly would have been nice to have had all of this been fixed > before the release of 4.3, of course, and it's somewhat ironic that > discussions about these very problems were occurring right around the > same time, but it sometimes requires a truly painful experience to > actually force an organization (or an individual for that matter) to > both recognize and act on its shortcomings. > > The failure of the FTP site, the timing of FreeBSD 4.3 RELEASE and > Wind River's acquisition of BSDi's BSD assets were simply unfortunate > coincidences which had no causal link and I'd also be happy if people > would stop inferring as much. Wind River has, in fact, indicated some > interest in keeping the ftp.freesoftware.com site alive and we simply > need to figure out the best way of doing so. As one might expect, a > Gigabit connection and collocation facilities for a full 19" rack's > worth of equipment doesn't come cheap! > > I will be releasing more information as the situation develops, > both here and to the hubs@freebsd.org mailing list. Thanks, > > - Jordan > > This is the moderated mailing list freebsd-announce. > The list contains announcements of new FreeBSD capabilities, > important events and project milestones. > See also the FreeBSD Web pages at http://www.freebsd.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-announce" in the body of the message > > > ----- End forwarded message ----- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 3:46: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by hub.freebsd.org (Postfix) with ESMTP id A9D3337B423 for ; Thu, 3 May 2001 03:46:00 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Thu, 3 May 2001 12:45:59 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FD9BA4@l04.research.kpn.com> From: "Koster, K.J." To: "'jessemonroy@email.com'" Cc: hackers@FreeBSD.ORG, jkh@osd.bsdi.com Subject: RE: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com] Date: Thu, 3 May 2001 12:45:58 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Jessem, > > A) A poor excuse for a coverup (for some unknown reason) > Need a reason? See item C. > > B) Major incompetence (in which someone should resign) > Does this mean you're volunteering? In case you don't: I hereby resign from the position of Major Incompetence. I have proudly held this position for the past eigthteen seconds. However, in honest and open talk with General Protection Failure we have come to the conclusion that it's best for me to let the younger generation move up and fill my shoes in this department. I have learned a lot from working with you in this position and it hurts me to make this decision. Still, my life goes on, and so does yours. > > C) Aliens have landed > Ah. All is explained. Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 3:53:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tepid.osl.fast.no (tepid.osl.fast.no [213.188.9.130]) by hub.freebsd.org (Postfix) with ESMTP id 0D3B937B422 for ; Thu, 3 May 2001 03:53:17 -0700 (PDT) (envelope-from Raymond.Wiker@fast.no) Received: from raw.grenland.fast.no.fast.no (fw-oslo.fast.no [213.188.9.129]) by tepid.osl.fast.no (8.9.3/8.9.1) with ESMTP id KAA05862; Thu, 3 May 2001 10:53:07 GMT (envelope-from Raymond.Wiker@fast.no) From: Raymond Wiker MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15089.14479.941452.818699@raw.grenland.fast.no> Date: Thu, 3 May 2001 12:53:03 +0200 To: hackers@FreeBSD.ORG Subject: RE: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com] In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FD9BA4@l04.research.kpn.com> References: <59063B5B4D98D311BC0D0001FA7E452205FD9BA4@l04.research.kpn.com> X-Mailer: VM 6.89 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Koster, K.J. writes: > Dear Jessem, > > > C) Aliens have landed > > > Ah. All is explained. Note that "jessem" appears to be Jesus Monroy Jr, who about 6 or 7 years ago conducted various experiments on PC hardware. Among other things, he proved that >>> if you turn off DRAM refresh, the PC crashes <<< Ignore him. //Raymond. -- Raymond Wiker Raymond.Wiker@fast.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 7:53:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mpehp1.mpe-garching.mpg.de (mpehp1.mpe-garching.mpg.de [130.183.70.10]) by hub.freebsd.org (Postfix) with ESMTP id DA6FD37B423 for ; Thu, 3 May 2001 07:53:16 -0700 (PDT) (envelope-from sutter@robert2.mpe-garching.mpg.de) Received: from robert2.mpe-garching.mpg.de (robert2.mpe-garching.mpg.de [130.183.136.59]) by mpehp1.mpe-garching.mpg.de (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id QAA27185 for ; Thu, 3 May 2001 16:53:16 +0200 (METDST) Received: from robert2.mpe-garching.mpg.de (localhost.mpe-garching.mpg.de [127.0.0.1]) by robert2.mpe-garching.mpg.de (8.11.3/8.11.3) with ESMTP id f43ErXS31356 for ; Thu, 3 May 2001 16:53:33 +0200 (CEST) (envelope-from sutter@robert2.mpe-garching.mpg.de) Message-Id: <200105031453.f43ErXS31356@robert2.mpe-garching.mpg.de> Reply-To: robert@mpe.mpg.de To: freebsd-hackers@freebsd.org Subject: Q: porting a driver from linux to freebsd. Date: Thu, 03 May 2001 16:53:33 +0200 From: Robert Suetterlin Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I asked this already on freebsd-questions and was suggested to ask on this list, too. I have a linux driver for a video grabber card (dfg/bw1 from 'the imaging source'). This card does not use a well bt848 or similar chip. I would like to transfer this driver to freebsd. I do understand how the driver works under linux and I will explain below. I have also read articles on newbus, some netbsd docs, several freebsd manpages and the sources of meteor.c. I know in principle how to do a driver under freebsd. But I never did it before and wanted to get some expertise on how to do it best. Under Linux the driver is just an empty shell that links into the kernel, then allocates some memory and provides rather general access to the pci-bus and the allocated memory using ioctl and mmap. There is a 'lowlevel' library that translates the ioctl and mmap calls to a struct based API. This API is then used by a binary only library to do all the work. I.e. find the hardware on the pci-bus. Read and write the device memory. Transfer data to main memory. Set grabbing specifics, etc. The reasons for this implementation are not mine to discuss, but in pricipal I do understand the idea, as it separates the OS/hardware specific part from a more general library. And it allows to distribute the library in binary format and evade some copyright problems. A driver as described above would not really be a PCI-device-driver as it would not allocate (attach to) a pci-device during configuration. My feeling is, that this is some kind of PCI-interface, or PCI-bus abstraction, more like an API, not like a real device. I think it is more like a new system call then a real device. My question: If you (as very experienced driver / kernel programmer) would face this task. And if You were not allowed to question /sidestep the task itself. Haw would You implement this under Freebsd? I even do not know enough keywords to ask more specific. I could ask: Would You do a pseudo device? But I do not know if this could be done by a pseudeo device. Etc. ... Sincerely, Robert S. Haw would You implement this under Freebsd? I even do not know enough keywords to ask more specific. I could ask: Would You do a pseudo device? But I do not know if this could be done by a pseudeo device. Etc. ... Sincerely, Robert S. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 8:46:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 39C2637B43F for ; Thu, 3 May 2001 08:46:28 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.2/8.11.0) with ESMTP id f43Fjxj41435; Thu, 3 May 2001 09:46:04 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.2/8.8.3) with ESMTP id f43Fjql38865; Thu, 3 May 2001 09:45:56 -0600 (MDT) Message-Id: <200105031545.f43Fjql38865@billy-club.village.org> To: Kevin Day Subject: Re: NMI during procfs mem reads (#2) Cc: hackers@FreeBSD.ORG, kevind@ikadega.com In-reply-to: Your message of "Wed, 02 May 2001 16:49:27 CDT." <200105022149.QAA00364@temphost.dragondata.com> References: <200105022149.QAA00364@temphost.dragondata.com> Date: Thu, 03 May 2001 09:45:52 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200105022149.QAA00364@temphost.dragondata.com> Kevin Day writes: : I tried sending this from my work account, but our new exchange server isn't : exactly sending mail correctly... Excuse the duplicate post if you see it. : :) It sounds like the PCI card that you are trying to read from is generating the pci fault cycles to cause the bridge to generate an nmi. Either that, or you have one of those handy nmi switches that you used to break into the debugger. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 8:49:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from temphost.dragondata.com (temphost.dragondata.com [63.167.131.128]) by hub.freebsd.org (Postfix) with ESMTP id A931137B422 for ; Thu, 3 May 2001 08:49:14 -0700 (PDT) (envelope-from toasty@temphost.dragondata.com) Received: (from toasty@localhost) by temphost.dragondata.com (8.9.3/8.9.3) id KAA74358; Thu, 3 May 2001 10:51:32 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200105031551.KAA74358@temphost.dragondata.com> Subject: Re: NMI during procfs mem reads (#2) To: imp@village.org (Warner Losh) Date: Thu, 3 May 2001 10:51:32 -0500 (CDT) Cc: hackers@FreeBSD.ORG, kevind@ikadega.com In-Reply-To: from "Warner Losh" at May 03, 2001 09:45:52 AM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In message <200105022149.QAA00364@temphost.dragondata.com> Kevin Day writes: > : I tried sending this from my work account, but our new exchange server isn't > : exactly sending mail correctly... Excuse the duplicate post if you see it. > : :) > > It sounds like the PCI card that you are trying to read from is > generating the pci fault cycles to cause the bridge to generate an > nmi. Either that, or you have one of those handy nmi switches that > you used to break into the debugger. > > Warner > The PCI target itself isn't doing anything like that, but it's possible that the PCI-PCI bridge we're going through might be. In any case, getting the NMI isn't really all that bad, it's stopping the chipset from getting hung on a infinite retry. My only concern is the NMI handler while in the kernel may be too aggressive in causing a panic. -- Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 8:57:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 1CCBD37B422 for ; Thu, 3 May 2001 08:57:19 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f43FuQ345916; Thu, 3 May 2001 08:56:27 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: jessemonroy@email.com, jessem@livecam.com Cc: hackers@FreeBSD.ORG Subject: Re: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com] In-Reply-To: <200105031015.DAA08946@dnull.com> References: <20010502220847.A84247@mooseriver.com> <200105031015.DAA08946@dnull.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010503085626S.jkh@osd.bsdi.com> Date: Thu, 03 May 2001 08:56:26 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 162 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, given that it's you I'm speaking with, I think we can just settle for the Aliens explanation and leave it at that. In the real world, shit happens and people do their best to deal with it, often with inadequate information and a lack of alternative resources. I suppose I could also ascribe your own failure to ever come up with a QIC tape driver or a floppy driver (despite months of "newsletters" and apparent effort) as a coverup or major incompetence in action, but that would be another case of reading too much into a sitution where simple human frailty was a more than adequate explanation. If you wish to turn SVBUG into your own personal pulpit for conspiracy theories and other wild-ass politicking then you're also free to do so, but SVBUG should not then be surprised if the rest of us avoid it like the plague. I've already made our position plain and this is the last communication we need to have on the matter since I can easily see that we're going squarely down the path of serious non-productivity with this whole exchange. I also don't see where the -hackers mailing list needs to be involved since this has NOTHING to do with FreeBSD hacking. Have a nice day. - Jordan From: jessem@livecam.com Subject: Re: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com] Date: Thu, 3 May 2001 03:14:44 -0700 (PDT) > Jordan, > I don't buy this story for a moment. You should expect > SVBUG not to either. This can only be classified as: > > A) A poor excuse for a coverup (for some unknown reason) > B) Major incompetence (in which someone should resign) > C) Aliens have landed > > If as you say, it has been known since the 20th of > April, 2001, then the world (and FreeBSD) has plenty > of channels for communications. Windriver has a website, > it is un-affected by FreeBSD traffic. BSDi has a website, > it is un-affected by FreeBSD traffic. Daemonnews has > a website.... Do I need continue? > > Best Regards, > Jessem. > > > > > > To: announce@FreeBSD.ORG > > Subject: ANNOUNCE: Status update on ftp.freebsd.org AKA ftp.freesoftware.com > > X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) > > Date: Wed, 02 May 2001 20:58:09 -0700 > > From: Jordan Hubbard > > > > Hi folks, > > > > This is just a short note to discuss the current state of affairs with > > our master FTP site, explain what we're doing about it and combat some > > of the FUD floating around which has everyone from space aliens to > > Wind River Systems (who supply the space aliens with navigational > > software, of course) intentionally killing the site off. > > > > On April 20th, 2001, the day that FreeBSD 4.3 was due to be released, > > we lost access to our main FTP site, ftp.freesoftware.com, without any > > advance warning. Further investigation revealed that the problem was > > due to an unforeseen network outage which caused the hosting ISP to > > have to block access to the site. With one of their major links down, > > it was overloading the ISPs backup links and denying bandwidth to > > their other customers. > > > > It was also not clear to us, then or now, just how long the outage > > would last and whether this was to be a short-term or a long-term > > problem. With the release date for 4.3 already well publicized in > > advance and many people asking me for it, I decided to use one of our > > backup sites, the usw[1-6].freebsd.org cluster, and at least get the > > current releases bits up somewhere on an interim basis. > > > > Unfortunately, I really underestimated both the extent of the demand > > and the degree to which our big, fat Gigabit pipe at ftp.freesoftware.com > > has made distributing the bits to our mirrors look comparatively easy. > > Even with the login limits set *significantly* greater in favor of the > > registered mirror sites, and with multiple machines pulling the load, > > it quickly overwhelmed the new hosting infrastructure and resulted in > > significant bandwidth limiting on FTP traffic being instituted by the > > ISP. Even delaying the official announcement by 24 hours had no > > measurable effect on the overload since word of mouth and anticipation > > had already built demand beyond the saturation point. > > > > In short, what many of us have suspected for years turned out to be > > proven rather abruptly true: The FreeBSD.org services infrastructure > > has become overly reliant on resources which constitute single points > > of failure and lacks both sufficient tiering and redundancy in the > > face of such failure. We lost a key FTP resource and our entire > > distribution service essentially collapsed. The same may be true for > > CVSup, mail and WWW services and that's something we definitely need > > to look at. > > > > For now, the most critical item is to finish implementing the > > discussed-but-not-implemented ftp-master site scheme. A machine to > > serve as the project's "master FTP host" has been procured will > > shortly be available for FTP access. ONLY mirror sites will be > > allowed to connect to it, and it will always be pre-loaded with > > release bits, CERT advisories and anything else which requires the > > mirrors to have a head-start in advance of any public announcement. > > Announcements will only be made after a hand-inspection of the mirror > > sites reveals that a significant degree of propagation has taken place > > from the master site and not beforehand. > > > > What people currently regard as "ftp.freebsd.org" will become another > > tier of sites, probably served in round-robin DNS fashion, which have > > all agreed to meet the minimum requirements for being "full and > > complete mirrors" of the bits offered from ftp-master.freebsd.org. > > Existing mirror sites which wish to maintain only a subset of the > > master bits will become clients of these second-tier sites and subject > > to whatever distribution policies they institute. It would be my > > expectation that certain 2nd-tier sites will also have mirror access > > lists which favor the 3rd-tier sites over end-users, but that's a > > detail to be worked out over time. > > > > It's also not clear what, if anything, needs to be done to make sites > > like www.freebsd.org and hub.freebsd.org more reliable in the face of > > failure, but people can certainly expect that a good deal of thought > > will be going into answering those questions over the next few weeks. > > > > It certainly would have been nice to have had all of this been fixed > > before the release of 4.3, of course, and it's somewhat ironic that > > discussions about these very problems were occurring right around the > > same time, but it sometimes requires a truly painful experience to > > actually force an organization (or an individual for that matter) to > > both recognize and act on its shortcomings. > > > > The failure of the FTP site, the timing of FreeBSD 4.3 RELEASE and > > Wind River's acquisition of BSDi's BSD assets were simply unfortunate > > coincidences which had no causal link and I'd also be happy if people > > would stop inferring as much. Wind River has, in fact, indicated some > > interest in keeping the ftp.freesoftware.com site alive and we simply > > need to figure out the best way of doing so. As one might expect, a > > Gigabit connection and collocation facilities for a full 19" rack's > > worth of equipment doesn't come cheap! > > > > I will be releasing more information as the situation develops, > > both here and to the hubs@freebsd.org mailing list. Thanks, > > > > - Jordan > > > > This is the moderated mailing list freebsd-announce. > > The list contains announcements of new FreeBSD capabilities, > > important events and project milestones. > > See also the FreeBSD Web pages at http://www.freebsd.org > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-announce" in the body of the message > > > > > > ----- End forwarded message ----- > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 9:11:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 6C16F37B424 for ; Thu, 3 May 2001 09:11:06 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f43GB0b64926; Thu, 3 May 2001 10:11:01 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200105031611.f43GB0b64926@harmony.village.org> To: Kevin Day Subject: Re: NMI during procfs mem reads (#2) Cc: hackers@FreeBSD.ORG, kevind@ikadega.com In-reply-to: Your message of "Thu, 03 May 2001 10:51:32 CDT." <200105031551.KAA74358@temphost.dragondata.com> References: <200105031551.KAA74358@temphost.dragondata.com> Date: Thu, 03 May 2001 10:11:00 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200105031551.KAA74358@temphost.dragondata.com> Kevin Day writes: : The PCI target itself isn't doing anything like that, but it's possible that : the PCI-PCI bridge we're going through might be. In any case, getting the : NMI isn't really all that bad, it's stopping the chipset from getting hung : on a infinite retry. My only concern is the NMI handler while in the kernel : may be too aggressive in causing a panic. Yes. The NMI handler is a little too agressive about panicing. Also, current has problems where sometimes it will panic when the nmi happens with GIANT held. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 9:45:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout00.sul.t-online.com (mailout00.sul.t-online.com [194.25.134.16]) by hub.freebsd.org (Postfix) with ESMTP id 6678037B422 for ; Thu, 3 May 2001 09:45:18 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from fwd07.sul.t-online.com by mailout00.sul.t-online.com with smtp id 14vME9-0004wF-06; Thu, 03 May 2001 18:45:17 +0200 Received: from peedub.muc.de (320038014727-0001@[62.155.144.121]) by fmrl07.sul.t-online.com with esmtp id 14vME2-0KGwYSC; Thu, 3 May 2001 18:45:10 +0200 Received: (from garyj@localhost) by peedub.muc.de (8.11.3/8.11.1) id f43GjIe43262; Thu, 3 May 2001 18:45:18 +0200 (CEST) (envelope-from garyj) Content-Type: text/plain; charset="iso-8859-1" From: Gary Jennejohn Reply-To: garyj@jennejohn.org To: robert@mpe.mpg.de, Robert Suetterlin , freebsd-hackers@freebsd.org Subject: Re: Q: porting a driver from linux to freebsd. Date: Thu, 3 May 2001 18:45:18 +0200 X-Mailer: KMail [version 1.2] References: <200105031453.f43ErXS31356@robert2.mpe-garching.mpg.de> In-Reply-To: <200105031453.f43ErXS31356@robert2.mpe-garching.mpg.de> MIME-Version: 1.0 Message-Id: <01050318451803.00815@peedub.muc.de> Content-Transfer-Encoding: 8bit X-Sender: 320038014727-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday 03 May 2001 16:53, Robert Suetterlin wrote: > Hello! > > I asked this already on freebsd-questions and was suggested to ask on this > list, too. > > I have a linux driver for a video grabber card (dfg/bw1 from 'the imaging > source'). This card does not use a well bt848 or similar chip. I would > like to transfer this driver to freebsd. > [snip] > Under Linux the driver is just an empty shell that links into the kernel, > then allocates some memory and provides rather general access to the > pci-bus and the allocated memory using ioctl and mmap. There is a > 'lowlevel' library that translates the ioctl and mmap calls to a struct > based API. This API is then used by a binary only library to do all the > work. I.e. find the hardware on the pci-bus. Read and write the device > memory. Transfer data to main memory. Set grabbing specifics, etc. > [snip] > My question: If you (as very experienced driver / kernel programmer) would > face this task. And if You were not allowed to question /sidestep the task > itself. Haw would You implement this under Freebsd? I even do not know > enough keywords to ask more specific. I could ask: Would You do a pseudo > device? But I do not know if this could be done by a pseudeo device. Etc. > ... I suspect that this thing uses libpci under Linux, which allows one to do all the nasty stuff in userland which is normally done in the probe and attach routines in the kernel. AFAIK libpci is very general und should work under FreeBSD too. However, if libpci does not work (I've never tried to use it with FreeBSD), then there's probably no way around writing a driver which at least does the basic probe/attach stuff to get the card mapped into the kernel. Beyond that you can probably get away with just providing mmap/ioctl support a la Linux. I personally would write a full-fledged driver. I don't think that this is something for which a pseudo-device is appropriate. I see that you're in Garching. I live in Munich and could maybe give you some help. Look me up in the phonebook, my name is unique. -- Gary Jennejohn garyj@jennejohn.org gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 9:53:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D1A1E37B43F for ; Thu, 3 May 2001 09:53:19 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f43GpSG71881; Thu, 3 May 2001 09:51:28 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200105031611.f43GB0b64926@harmony.village.org> Date: Thu, 03 May 2001 09:50:43 -0700 (PDT) From: John Baldwin To: Warner Losh Subject: Re: NMI during procfs mem reads (#2) Cc: kevind@ikadega.com, hackers@FreeBSD.org, Kevin Day Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-May-01 Warner Losh wrote: > In message <200105031551.KAA74358@temphost.dragondata.com> Kevin Day writes: >: The PCI target itself isn't doing anything like that, but it's possible that >: the PCI-PCI bridge we're going through might be. In any case, getting the >: NMI isn't really all that bad, it's stopping the chipset from getting hung >: on a infinite retry. My only concern is the NMI handler while in the kernel >: may be too aggressive in causing a panic. > > Yes. The NMI handler is a little too agressive about panicing. Also, > current has problems where sometimes it will panic when the nmi > happens with GIANT held. Correction, with a spin lock held. It may try to acquire Giant (not sure _why_ it acquires Giant) and then it pukes. Getting a traceback would be most helpful. :) Also, the output of 'show locks' from ddb could help, too. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 9:55:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id F39D937B422; Thu, 3 May 2001 09:55:20 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f43GtIq11742; Thu, 3 May 2001 09:55:18 -0700 Date: Thu, 3 May 2001 09:55:18 -0700 From: Brooks Davis To: Gunnar Olsson Cc: "Freebsd Net (E-mail)" , "Freebsd Hackers (E-mail)" Subject: Re: how to use netgraph? Message-ID: <20010503095518.A10093@Odin.AC.HMC.Edu> References: <31A473DBB655D21180850008C71E251A031AAF3A@mail.kebne.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <31A473DBB655D21180850008C71E251A031AAF3A@mail.kebne.se>; from gunnar.olsson@xelerated.com on Thu, May 03, 2001 at 10:20:45AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 03, 2001 at 10:20:45AM +0200, Gunnar Olsson wrote: > I have a process in user space, that wants to send a packet > direct on the ethernet, not encapsulate the packet in IP. > When I read about netgraph, it looks like it possible to do, or? > When I hook to a upper or a lower hook, does the kernel create > the ethernet header, or do I have to create the ethernet header > in the user process myself before sending down? >=20 > If the kernal is adding the ethernet header, > what is actually sent out on the wire? Usaully an ARPLOOKUP > is done and maps the IP dst to a MAC dst, but now I do not > have the IP header. How to get the MAC dst field filled in? It's rather unnecessicary to use netgraph for this purpose. Instead you can use the well hidden feature of the bpf device that it can write as well as read. If you want to send packets with arbitrary sender addresses, you will want to use the BIOCGHDRCMPLT ioctl to enable that (not all cards support this, for instance wireless cards do not.) You might also look at libnet which provides wrappers for this, but I seem to recall that it doesn't support BIOCGHDRCMPLT. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE68Y11XY6L6fI4GtQRAidiAKCbcfyGhEl2P4klZv4zVqsjm6qG5QCg16p9 RjsEWw6j0QN78Xoiuh0fD2w= =ucdh -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 10:33:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dnull.com (dnull.com [209.133.53.79]) by hub.freebsd.org (Postfix) with ESMTP id 3BFA537B423 for ; Thu, 3 May 2001 10:33:32 -0700 (PDT) (envelope-from jessem@jigsaw.svbug.com) Received: from jigsaw.svbug.com ([198.79.110.2]) by dnull.com (8.8.8/8.8.8) with ESMTP id KAA11858; Thu, 3 May 2001 10:33:12 -0700 (PDT) Message-Id: <200105031733.KAA11858@dnull.com> Date: Thu, 3 May 2001 10:32:32 -0700 (PDT) From: jessem@livecam.com Reply-To: jessemonroy@email.com Subject: Re: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com] To: jkh@osd.bsdi.com Cc: jessemonroy@email.com, hackers@FreeBSD.ORG In-Reply-To: <20010503085626S.jkh@osd.bsdi.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 3 May, Jordan Hubbard wrote: > Well, given that it's you I'm speaking with, I think we can just > settle for the Aliens explanation and leave it at that. In the real > world, shit happens and people do their best to deal with it, often > with inadequate information and a lack of alternative resources. > > I suppose I could also ascribe your own failure to ever come up with a > QIC tape driver or a floppy driver (despite months of "newsletters" > and apparent effort) as a coverup or major incompetence in action, but > that would be another case of reading too much into a sitution where > simple human frailty was a more than adequate explanation. > > If you wish to turn SVBUG into your own personal pulpit for conspiracy > theories and other wild-ass politicking then you're also free to do > so, but SVBUG should not then be surprised if the rest of us avoid it > like the plague. I've already made our position plain and this is the > last communication we need to have on the matter since I can easily > see that we're going squarely down the path of serious > non-productivity with this whole exchange. I also don't see where the > -hackers mailing list needs to be involved since this has NOTHING to > do with FreeBSD hacking. Have a nice day. > Mr. Hubbard, It's more than apparent I've found the right point at which to discuss this issue. If flame bait had to be labeled, in this case it would be 'aliens'. We both have bitten into that apple now. I hoped you would answer the question. However, given the past nature of your responses, my guess that you would take the 'aliens' route proved correct (at least to me). Conspiracy, that's your label. It has implications, I don't see any that apply; perhaps you do. As for the nature of SVBUG, perhaps you might consider that my 'wild-ass politicking' might be the response of the club as a whole. To which, a bunch of OS-X newbies might be the least of your issues for years to come. Lastly, as an SVBUG club member remarked last might, "perhaps FreeBSD will now become familiar with how the Jolitz felt, when they were accused of coverups." Best Regards, Jessem. > - Jordan > > From: jessem@livecam.com > Subject: Re: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com] > Date: Thu, 3 May 2001 03:14:44 -0700 (PDT) > >> Jordan, >> I don't buy this story for a moment. You should expect >> SVBUG not to either. This can only be classified as: >> >> A) A poor excuse for a coverup (for some unknown reason) >> B) Major incompetence (in which someone should resign) >> C) Aliens have landed >> >> If as you say, it has been known since the 20th of >> April, 2001, then the world (and FreeBSD) has plenty >> of channels for communications. Windriver has a website, >> it is un-affected by FreeBSD traffic. BSDi has a website, >> it is un-affected by FreeBSD traffic. Daemonnews has >> a website.... Do I need continue? >> >> Best Regards, >> Jessem. >> >> >> >> >> > To: announce@FreeBSD.ORG >> > Subject: ANNOUNCE: Status update on ftp.freebsd.org AKA ftp.freesoftware.com >> > X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) >> > Date: Wed, 02 May 2001 20:58:09 -0700 >> > From: Jordan Hubbard >> > >> > Hi folks, >> > >> > This is just a short note to discuss the current state of affairs with >> > our master FTP site, explain what we're doing about it and combat some >> > of the FUD floating around which has everyone from space aliens to >> > Wind River Systems (who supply the space aliens with navigational >> > software, of course) intentionally killing the site off. >> > >> > On April 20th, 2001, the day that FreeBSD 4.3 was due to be released, >> > we lost access to our main FTP site, ftp.freesoftware.com, without any >> > advance warning. Further investigation revealed that the problem was >> > due to an unforeseen network outage which caused the hosting ISP to >> > have to block access to the site. With one of their major links down, >> > it was overloading the ISPs backup links and denying bandwidth to >> > their other customers. >> > >> > It was also not clear to us, then or now, just how long the outage >> > would last and whether this was to be a short-term or a long-term >> > problem. With the release date for 4.3 already well publicized in >> > advance and many people asking me for it, I decided to use one of our >> > backup sites, the usw[1-6].freebsd.org cluster, and at least get the >> > current releases bits up somewhere on an interim basis. >> > >> > Unfortunately, I really underestimated both the extent of the demand >> > and the degree to which our big, fat Gigabit pipe at ftp.freesoftware.com >> > has made distributing the bits to our mirrors look comparatively easy. >> > Even with the login limits set *significantly* greater in favor of the >> > registered mirror sites, and with multiple machines pulling the load, >> > it quickly overwhelmed the new hosting infrastructure and resulted in >> > significant bandwidth limiting on FTP traffic being instituted by the >> > ISP. Even delaying the official announcement by 24 hours had no >> > measurable effect on the overload since word of mouth and anticipation >> > had already built demand beyond the saturation point. >> > >> > In short, what many of us have suspected for years turned out to be >> > proven rather abruptly true: The FreeBSD.org services infrastructure >> > has become overly reliant on resources which constitute single points >> > of failure and lacks both sufficient tiering and redundancy in the >> > face of such failure. We lost a key FTP resource and our entire >> > distribution service essentially collapsed. The same may be true for >> > CVSup, mail and WWW services and that's something we definitely need >> > to look at. >> > >> > For now, the most critical item is to finish implementing the >> > discussed-but-not-implemented ftp-master site scheme. A machine to >> > serve as the project's "master FTP host" has been procured will >> > shortly be available for FTP access. ONLY mirror sites will be >> > allowed to connect to it, and it will always be pre-loaded with >> > release bits, CERT advisories and anything else which requires the >> > mirrors to have a head-start in advance of any public announcement. >> > Announcements will only be made after a hand-inspection of the mirror >> > sites reveals that a significant degree of propagation has taken place >> > from the master site and not beforehand. >> > >> > What people currently regard as "ftp.freebsd.org" will become another >> > tier of sites, probably served in round-robin DNS fashion, which have >> > all agreed to meet the minimum requirements for being "full and >> > complete mirrors" of the bits offered from ftp-master.freebsd.org. >> > Existing mirror sites which wish to maintain only a subset of the >> > master bits will become clients of these second-tier sites and subject >> > to whatever distribution policies they institute. It would be my >> > expectation that certain 2nd-tier sites will also have mirror access >> > lists which favor the 3rd-tier sites over end-users, but that's a >> > detail to be worked out over time. >> > >> > It's also not clear what, if anything, needs to be done to make sites >> > like www.freebsd.org and hub.freebsd.org more reliable in the face of >> > failure, but people can certainly expect that a good deal of thought >> > will be going into answering those questions over the next few weeks. >> > >> > It certainly would have been nice to have had all of this been fixed >> > before the release of 4.3, of course, and it's somewhat ironic that >> > discussions about these very problems were occurring right around the >> > same time, but it sometimes requires a truly painful experience to >> > actually force an organization (or an individual for that matter) to >> > both recognize and act on its shortcomings. >> > >> > The failure of the FTP site, the timing of FreeBSD 4.3 RELEASE and >> > Wind River's acquisition of BSDi's BSD assets were simply unfortunate >> > coincidences which had no causal link and I'd also be happy if people >> > would stop inferring as much. Wind River has, in fact, indicated some >> > interest in keeping the ftp.freesoftware.com site alive and we simply >> > need to figure out the best way of doing so. As one might expect, a >> > Gigabit connection and collocation facilities for a full 19" rack's >> > worth of equipment doesn't come cheap! >> > >> > I will be releasing more information as the situation develops, >> > both here and to the hubs@freebsd.org mailing list. Thanks, >> > >> > - Jordan >> > >> > This is the moderated mailing list freebsd-announce. >> > The list contains announcements of new FreeBSD capabilities, >> > important events and project milestones. >> > See also the FreeBSD Web pages at http://www.freebsd.org >> > >> > >> > To Unsubscribe: send mail to majordomo@FreeBSD.org >> > with "unsubscribe freebsd-announce" in the body of the message >> > >> > >> > ----- End forwarded message ----- >> > >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 10:41:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dnull.com (dnull.com [209.133.53.79]) by hub.freebsd.org (Postfix) with ESMTP id E57AE37B424 for ; Thu, 3 May 2001 10:41:25 -0700 (PDT) (envelope-from jessem@jigsaw.svbug.com) Received: from jigsaw.svbug.com ([198.79.110.2]) by dnull.com (8.8.8/8.8.8) with ESMTP id KAA11934; Thu, 3 May 2001 10:40:17 -0700 (PDT) Message-Id: <200105031740.KAA11934@dnull.com> Date: Thu, 3 May 2001 10:38:33 -0700 (PDT) From: jessem@livecam.com Reply-To: jessemonroy@email.com Subject: RE: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com] To: K.J.Koster@kpn.com Cc: hackers@FreeBSD.ORG, jkh@osd.bsdi.com In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FD9BA4@l04.research.kpn.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG K.J. thanks for your comments. I'll make sure to pass them on to the club. :-) Best Regards, Jessem. On 3 May, Koster, K.J. wrote: > Dear Jessem, > >> >> A) A poor excuse for a coverup (for some unknown reason) >> > Need a reason? See item C. > >> >> B) Major incompetence (in which someone should resign) >> > Does this mean you're volunteering? > > In case you don't: I hereby resign from the position of Major Incompetence. > I have proudly held this position for the past eigthteen seconds. However, > in honest and open talk with General Protection Failure we have come to the > conclusion that it's best for me to let the younger generation move up and > fill my shoes in this department. I have learned a lot from working with you > in this position and it hurts me to make this decision. Still, my life goes > on, and so does yours. > >> >> C) Aliens have landed >> > Ah. All is explained. > > Kees Jan > > ================================================ > You are only young once, > but you can stay immature all your life. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 10:46:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id CE2F837B422 for ; Thu, 3 May 2001 10:46:33 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f43Hk6346316; Thu, 3 May 2001 10:46:06 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: jessemonroy@email.com, jessem@livecam.com Cc: hackers@FreeBSD.ORG Subject: Re: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com] In-Reply-To: <200105031733.KAA11858@dnull.com> References: <20010503085626S.jkh@osd.bsdi.com> <200105031733.KAA11858@dnull.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010503104606M.jkh@osd.bsdi.com> Date: Thu, 03 May 2001 10:46:06 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 32 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know what part of "this has nothing to do with hacking FreeBSD" you did not understand before, but this list has a very clear and well-stated CHARTER which is posted here: http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/eresources.html#ERESOURCES-MAIL and this discussion clearly does not fall under it. As the charter very explicitly states: "Ongoing irrelevant chatter or flaming only detracts from the value of the mailing list for everyone on it and will not be tolerated" You may therefore consider this your second official warning that you are not in compliance with the charter for this mailing list and need only one more offense to warrant a ban. Since this will also not be the first time you have managed to ban yourself from this list, I suspect that a ban on this occasion may prove permanent, so take heed! I have already communicated the true situation with ftp.freebsd.org as best I could using the appropriate channels and whatever you or SVBUG may choose to say about it is purely your own business, simply keep it off this mailing list. A perfectly good mailing list, chat@freebsd.org, also exists for just this kind of thing and you are more than encouraged to take this "discussion" there. This is your second and final warning and if you choose to reply to this message, either make it personal to me only or cc it to freebsd-chat. I've only cc'd hackers twice myself to show that the issue is being dealt with and to ensure that the warnings are properly on record. Anything further you send to -hackers, unless on a more appropriate topic, will constitute a banning offense. Thank you. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 10:51:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 2BEB337B43C for ; Thu, 3 May 2001 10:51:38 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f43HpLX31184; Thu, 3 May 2001 19:51:21 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: jessemonroy@email.com Cc: jkh@osd.bsdi.com, hackers@FreeBSD.ORG Subject: Re: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com] In-Reply-To: Your message of "Thu, 03 May 2001 10:32:32 PDT." <200105031733.KAA11858@dnull.com> Date: Thu, 03 May 2001 19:51:21 +0200 Message-ID: <31182.988912281@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan, As far as I can see the ECHELON is still doing a good job of filtering his messages out, I have seen no traces of this thread anywhere else than on the encrypted monitor VPN. But I guess he is on to our plan, so we really have no choice but to kill him. Is it your turn or my turn to call the squad ? Ohh, btw: great cover story you got going there, I wonder if anybody else will catch the subtle irony of the first space tourist having the same name as a former eastern block dictator, TSGM were all howling from laughter when they heard it, you certainly scored some brownie points with that. And how's your new helicopter ? Black is always beautiful as they say :-) Poul-Henning In message <200105031733.KAA11858@dnull.com>, jessem@livecam.com writes: >On 3 May, Jordan Hubbard wrote: >> Well, given that it's you I'm speaking with, I think we can just >> settle for the Aliens explanation and leave it at that. In the real >> world, shit happens and people do their best to deal with it, often >> with inadequate information and a lack of alternative resources. >> >> I suppose I could also ascribe your own failure to ever come up with a >> QIC tape driver or a floppy driver (despite months of "newsletters" >> and apparent effort) as a coverup or major incompetence in action, but >> that would be another case of reading too much into a sitution where >> simple human frailty was a more than adequate explanation. >> >> If you wish to turn SVBUG into your own personal pulpit for conspiracy >> theories and other wild-ass politicking then you're also free to do >> so, but SVBUG should not then be surprised if the rest of us avoid it >> like the plague. I've already made our position plain and this is the >> last communication we need to have on the matter since I can easily >> see that we're going squarely down the path of serious >> non-productivity with this whole exchange. I also don't see where the >> -hackers mailing list needs to be involved since this has NOTHING to >> do with FreeBSD hacking. Have a nice day. >> >Mr. Hubbard, > It's more than apparent I've found the right point at which to >discuss this issue. If flame bait had to be labeled, in this case >it would be 'aliens'. We both have bitten into that apple now. > > I hoped you would answer the question. However, given the past >nature of your responses, my guess that you would take the 'aliens' >route proved correct (at least to me). Conspiracy, that's your label. >It has implications, I don't see any that apply; perhaps you do. > > As for the nature of SVBUG, perhaps you might consider >that my 'wild-ass politicking' might be the response of the >club as a whole. To which, a bunch of OS-X newbies might >be the least of your issues for years to come. > > Lastly, as an SVBUG club member remarked last might, "perhaps >FreeBSD will now become familiar with how the Jolitz felt, when >they were accused of coverups." > > Best Regards, > Jessem. > > > > >> - Jordan >> >> From: jessem@livecam.com >> Subject: Re: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com] >> Date: Thu, 3 May 2001 03:14:44 -0700 (PDT) >> >>> Jordan, >>> I don't buy this story for a moment. You should expect >>> SVBUG not to either. This can only be classified as: >>> >>> A) A poor excuse for a coverup (for some unknown reason) >>> B) Major incompetence (in which someone should resign) >>> C) Aliens have landed >>> >>> If as you say, it has been known since the 20th of >>> April, 2001, then the world (and FreeBSD) has plenty >>> of channels for communications. Windriver has a website, >>> it is un-affected by FreeBSD traffic. BSDi has a website, >>> it is un-affected by FreeBSD traffic. Daemonnews has >>> a website.... Do I need continue? >>> >>> Best Regards, >>> Jessem. >>> >>> >>> >>> >>> > To: announce@FreeBSD.ORG >>> > Subject: ANNOUNCE: Status update on ftp.freebsd.org AKA ftp.freesoftware.com >>> > X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) >>> > Date: Wed, 02 May 2001 20:58:09 -0700 >>> > From: Jordan Hubbard >>> > >>> > Hi folks, >>> > >>> > This is just a short note to discuss the current state of affairs with >>> > our master FTP site, explain what we're doing about it and combat some >>> > of the FUD floating around which has everyone from space aliens to >>> > Wind River Systems (who supply the space aliens with navigational >>> > software, of course) intentionally killing the site off. >>> > >>> > On April 20th, 2001, the day that FreeBSD 4.3 was due to be released, >>> > we lost access to our main FTP site, ftp.freesoftware.com, without any >>> > advance warning. Further investigation revealed that the problem was >>> > due to an unforeseen network outage which caused the hosting ISP to >>> > have to block access to the site. With one of their major links down, >>> > it was overloading the ISPs backup links and denying bandwidth to >>> > their other customers. >>> > >>> > It was also not clear to us, then or now, just how long the outage >>> > would last and whether this was to be a short-term or a long-term >>> > problem. With the release date for 4.3 already well publicized in >>> > advance and many people asking me for it, I decided to use one of our >>> > backup sites, the usw[1-6].freebsd.org cluster, and at least get the >>> > current releases bits up somewhere on an interim basis. >>> > >>> > Unfortunately, I really underestimated both the extent of the demand >>> > and the degree to which our big, fat Gigabit pipe at ftp.freesoftware.com >>> > has made distributing the bits to our mirrors look comparatively easy. >>> > Even with the login limits set *significantly* greater in favor of the >>> > registered mirror sites, and with multiple machines pulling the load, >>> > it quickly overwhelmed the new hosting infrastructure and resulted in >>> > significant bandwidth limiting on FTP traffic being instituted by the >>> > ISP. Even delaying the official announcement by 24 hours had no >>> > measurable effect on the overload since word of mouth and anticipation >>> > had already built demand beyond the saturation point. >>> > >>> > In short, what many of us have suspected for years turned out to be >>> > proven rather abruptly true: The FreeBSD.org services infrastructure >>> > has become overly reliant on resources which constitute single points >>> > of failure and lacks both sufficient tiering and redundancy in the >>> > face of such failure. We lost a key FTP resource and our entire >>> > distribution service essentially collapsed. The same may be true for >>> > CVSup, mail and WWW services and that's something we definitely need >>> > to look at. >>> > >>> > For now, the most critical item is to finish implementing the >>> > discussed-but-not-implemented ftp-master site scheme. A machine to >>> > serve as the project's "master FTP host" has been procured will >>> > shortly be available for FTP access. ONLY mirror sites will be >>> > allowed to connect to it, and it will always be pre-loaded with >>> > release bits, CERT advisories and anything else which requires the >>> > mirrors to have a head-start in advance of any public announcement. >>> > Announcements will only be made after a hand-inspection of the mirror >>> > sites reveals that a significant degree of propagation has taken place >>> > from the master site and not beforehand. >>> > >>> > What people currently regard as "ftp.freebsd.org" will become another >>> > tier of sites, probably served in round-robin DNS fashion, which have >>> > all agreed to meet the minimum requirements for being "full and >>> > complete mirrors" of the bits offered from ftp-master.freebsd.org. >>> > Existing mirror sites which wish to maintain only a subset of the >>> > master bits will become clients of these second-tier sites and subject >>> > to whatever distribution policies they institute. It would be my >>> > expectation that certain 2nd-tier sites will also have mirror access >>> > lists which favor the 3rd-tier sites over end-users, but that's a >>> > detail to be worked out over time. >>> > >>> > It's also not clear what, if anything, needs to be done to make sites >>> > like www.freebsd.org and hub.freebsd.org more reliable in the face of >>> > failure, but people can certainly expect that a good deal of thought >>> > will be going into answering those questions over the next few weeks. >>> > >>> > It certainly would have been nice to have had all of this been fixed >>> > before the release of 4.3, of course, and it's somewhat ironic that >>> > discussions about these very problems were occurring right around the >>> > same time, but it sometimes requires a truly painful experience to >>> > actually force an organization (or an individual for that matter) to >>> > both recognize and act on its shortcomings. >>> > >>> > The failure of the FTP site, the timing of FreeBSD 4.3 RELEASE and >>> > Wind River's acquisition of BSDi's BSD assets were simply unfortunate >>> > coincidences which had no causal link and I'd also be happy if people >>> > would stop inferring as much. Wind River has, in fact, indicated some >>> > interest in keeping the ftp.freesoftware.com site alive and we simply >>> > need to figure out the best way of doing so. As one might expect, a >>> > Gigabit connection and collocation facilities for a full 19" rack's >>> > worth of equipment doesn't come cheap! >>> > >>> > I will be releasing more information as the situation develops, >>> > both here and to the hubs@freebsd.org mailing list. Thanks, >>> > >>> > - Jordan >>> > >>> > This is the moderated mailing list freebsd-announce. >>> > The list contains announcements of new FreeBSD capabilities, >>> > important events and project milestones. >>> > See also the FreeBSD Web pages at http://www.freebsd.org >>> > >>> > >>> > To Unsubscribe: send mail to majordomo@FreeBSD.org >>> > with "unsubscribe freebsd-announce" in the body of the message >>> > >>> > >>> > ----- End forwarded message ----- >>> > >>> >>> >>> >>> To Unsubscribe: send mail to majordomo@FreeBSD.org >>> with "unsubscribe freebsd-hackers" in the body of the message >> >> > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 10:58:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rottweiler.esbrasil.com (www.esbrasil.com [200.188.18.227]) by hub.freebsd.org (Postfix) with ESMTP id 7872B37B422; Thu, 3 May 2001 10:58:33 -0700 (PDT) (envelope-from jcarlos@esbrasil.com) Received: from WKSNOP03 (ld-facs0234.ba.psinet.com.br [200.188.18.234] (may be forged)) by rottweiler.esbrasil.com (8.11.3/8.11.0) with SMTP id f43Eubc64070; Thu, 3 May 2001 14:56:38 GMT Message-ID: <015701c0d3fa$ab253140$830a14ac@ESOLUTIONS.esbrasil.com> From: "Joao Carlos" To: Cc: Subject: real time Date: Thu, 3 May 2001 14:58:32 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does FreeBSD has any related work about it as an real time operating system? Where can i find information about that ?? --- Joao Carlos jcarlos@esbrasil.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 11:11:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id AEC1737B424 for ; Thu, 3 May 2001 11:11:51 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f43IBXL12739; Thu, 3 May 2001 11:11:33 -0700 (PDT) (envelope-from dillon) Date: Thu, 3 May 2001 11:11:33 -0700 (PDT) From: Matt Dillon Message-Id: <200105031811.f43IBXL12739@earth.backplane.com> To: Poul-Henning Kamp Cc: jessemonroy@email.com, jkh@osd.bsdi.com, hackers@FreeBSD.ORG Subject: Re: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com] References: <31182.988912281@critter> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :And how's your new helicopter ? Black is always beautiful as they say :-) : :Poul-Henning Helicopter? Pah! I know for a fact that Jordan was bribed with a brand spanking new hovermobile by the afformentioned aliens! (which, oddly enough looks somewhat like a DeLorean with a MrCoffee bolted to the back, hrmmmmm). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 11:44:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail3.intermedia.net (mail3.intermedia.net [206.40.48.153]) by hub.freebsd.org (Postfix) with ESMTP id DFDBA37B50D for ; Thu, 3 May 2001 11:43:44 -0700 (PDT) (envelope-from tonyg@crazynickels.com) Received: from mail.crazynickels.com (unverified [64.78.44.128]) by mail3.intermedia.net (Rockliffe SMTPRA 4.2.4) with ESMTP id for ; Thu, 3 May 2001 11:37:28 -0700 Message-ID: Content-type: text/plain Date: Thu, 03 May 2001 11:42:31 -0700 From: tonyg@crazynickels.com Subject: Web Development To: freebsd-hackers@FreeBSD.org X-mailer: CrazyNickels.Com Email Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Hi, I do web development and database work out of Las Vegas. I was wondering if you needed any development done. I have been doing web work for 6 years. I know Cold Fusion, ASP, Oracle, SQL and Flash. Tony Grijalva 702.951.3051 Here's some the sites I've worked on: http://www.crazynickels.com - Complete site. Turned out in 3 days. http://www.woodtrim.com - Complete sites along with www.brushed aluminum.com as a content manager, shopping cart, FAQ, Referral Program. http://www.SchoolCity.com - Pre-IPO Company I did the Complete site. I can send you a complete document about this site. http://www.codernet.com - My own site with a bunch of guys here. I did the graphics. http://www.antennas.com - The graphics were given to me in PhotoShop format. I have to make them web ready and add functions. http://www.momentisgroup.com - Backend Cold Fusion work. http://www.isecinc.com - Their print company in Arizona sent me the project and related functions. I can walk you through a back door process. http://www.reoinc.com - Working on Now. http://www.arraybiopharma.com - Needed the site before they went public... I didn't do the flash but everything else and some cgi. http://www.linworth.com - Got PhotoShop files. Added Cold Fusion functions. Please let me know if you need any help...... Thank You for your time and consideration, Tony Grijalva 702.951.3051 tonyg@codernet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 11:56:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 7093D37B424 for ; Thu, 3 May 2001 11:56:08 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from zerogravity.kawo2.rwth-aachen.de ([134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.6.9) with ESMTP id UAA03840; Thu, 3 May 2001 20:55:55 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id AA6D314BE6; Thu, 3 May 2001 20:55:55 +0200 (CEST) Date: Thu, 3 May 2001 20:55:55 +0200 From: Alexander Langer To: Matt Dillon Cc: Poul-Henning Kamp , jessemonroy@email.com, jkh@osd.bsdi.com, hackers@FreeBSD.ORG Subject: Re: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com] Message-ID: <20010503205555.A2125@zerogravity.kawo2.rwth-aachen.d> References: <31182.988912281@critter> <200105031811.f43IBXL12739@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105031811.f43IBXL12739@earth.backplane.com>; from dillon@earth.backplane.com on Thu, May 03, 2001 at 11:11:33AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Matt Dillon (dillon@earth.backplane.com): > Helicopter? Pah! I know for a fact that Jordan was bribed with > a brand spanking new hovermobile by the afformentioned aliens! > (which, oddly enough looks somewhat like a DeLorean with a MrCoffee > bolted to the back, hrmmmmm). I always thought sheep drive Vespas. :) Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 12:14:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id F00E637B423; Thu, 3 May 2001 12:14:04 -0700 (PDT) (envelope-from langd@informatik.tu-muenchen.de) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.24.91] HELO atrbg11.informatik.tu-muenchen.de ident: IDENT-NONSENSE [port 2039]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <114336-237>; Thu, 3 May 2001 21:13:59 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 652A613667; Thu, 3 May 2001 21:13:52 +0200 (CEST) Date: Thu, 3 May 2001 21:13:52 +0200 From: Daniel Lang To: Mike Smith Cc: Lars Eggert , freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Kernel Console speed Message-ID: <20010503211352.A96026@atrbg11.informatik.tu-muenchen.de> References: <3AF090AF.31215A1C@isi.edu> <200105022308.f42N8Pl00912@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200105022308.f42N8Pl00912@mass.dis.org>; from msmith@freebsd.org on Wed, May 02, 2001 at 04:08:25PM -0700 X-Geek: GCS d-- s: a- C++ UB++++$ P+++$ L- E W+++(--) N+ o K w--- O? M- V@ PS+(++) PE--(+) Y+ PGP+ t++ 5@ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Mike, Mike Smith wrote on Wed, May 02, 2001 at 04:08:25PM -0700: [..] > You don't want to set CONSPEED in the kernel config, or change the loader > configuration. Just build/install boot1/boot2 with a new > BOOT_COMCONSOLE_SPEED, and ensure that /etc/ttys is correctly set for > your desired console rate. This works. I tried this. Rebuilt the kernel without any CONSPEED option, bootstrap untouched (did already work with 38400), still the same problem. To illustrate it a bit, here cut & paste from the console server, which is permanently set at 38400: [..] Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS drive E: is disk3 BIOS 639kB/523264kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 (root@atleo1.leo.org, Tue Apr 24 09:16:22 CEST 2001) Loading /boot/defaults/loader.conf /kernel text=0x20ec4e data=0x27cd4+0x301a4 syms=[0x4+0x2d3e0+0x4+0x32f1e] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... øøøøøøàøøÀøøøøøøøøÀ... [.. from here on, the kernel boot messages should appear starting with: Copyright (c) 1992-2001 The FreeBSD Project. but its not readable on the console-server, because of the wrong speed. This stays until /etc/rc.sysctl resets machdep.conspeed=38400 Then the system startup / rc continues (then readable) until the getty is started (which of course is also running at 38400) ..] øàøøøøþøÀøàüüxachdep.conspeed: 9600 -> 38400 Doing initial network setup: hostname. fxp0: flags=8843 mtu 1500 inet 131.159.72.9 netmask 0xfffffe00 broadcast 131.159.73.255 inet6 fe80::2a0:c9ff:fe99:504e%fxp0 prefixlen 64 tentative scopeid 0x1 inet 131.159.72.28 netmask 0xffffffff broadcast 131.159.72.28 ether 00:a0:c9:99:50:4e media: autoselect (100baseTX ) status: active [ remaining startup output omitted ] Additional TCP options:. Thu May 3 21:02:16 CEST 2001 FreeBSD/i386 (atleo1.leo.org) (ttyd0) login: [..] So far... Thanks, Daniel -- IRCnet: Mr-Spock - Eddie would go! - Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 14: 6:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cody.jharris.com (cody.jharris.com [205.238.128.83]) by hub.freebsd.org (Postfix) with ESMTP id EBC6B37B422 for ; Thu, 3 May 2001 14:06:49 -0700 (PDT) (envelope-from nick@rogness.net) Received: from localhost (nick@localhost) by cody.jharris.com (8.11.1/8.9.3) with ESMTP id f43MHIF15074 for ; Thu, 3 May 2001 17:17:18 -0500 (CDT) (envelope-from nick@rogness.net) Date: Thu, 3 May 2001 17:17:17 -0500 (CDT) From: Nick Rogness X-Sender: nick@cody.jharris.com To: freebsd-hackers@freebsd.org Subject: /etc/rc.network and natd_enable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In 4.2-STABLE, /etc/rc.network has entries to turn on natd. However, natd does not get enabled if you don't specify natd_interface. WHat if you you have setup stored in a configuration file and do not wish to supply an interface flag in /etc/rc.conf? Well, natd does not turn on! Would it make more sense to do something like (psuedo-ish code): if (natd_enable = YES) if (natd_interface defined) natd -n $natd_interface $natd_flags elif (natd_flags defined) natd $natd_flags fi fi It would allow for people to not specify a natd_interface but still be able to run natd out of rc.conf. What does everyone think of this? I guess you pay the penalty if someone doesn't setup the flags properly but I guess you could write that off as a config error anyways. Nick Rogness - Keep on Routing in a Free World... "FreeBSD: The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 14:35:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from no-spam.it.helsinki.fi (NO-SPAM.it.helsinki.fi [128.214.205.34]) by hub.freebsd.org (Postfix) with ESMTP id 9414137B423; Thu, 3 May 2001 14:35:47 -0700 (PDT) (envelope-from reissell@cc.helsinki.fi) Received: from mursu.pesa.fi (root@sirppi.helsinki.fi [128.214.205.27]) by no-spam.it.helsinki.fi (8.11.3/8.11.3-SPAMmers-sod-off) with ESMTP id f43LWtn17253; Fri, 4 May 2001 00:32:55 +0300 (EEST) Received: (from poku@localhost) by mursu.pesa.fi (8.11.2/8.11.1) id f43Laih54434; Fri, 4 May 2001 00:36:44 +0300 (EEST) (envelope-from poku@mursu.pesa.fi) To: Rick Duvall Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Bootable CD IV References: X-No-Archive: yes From: Jussi Reissell Date: 04 May 2001 00:36:44 +0300 In-Reply-To: Rick Duvall's message of "Tue, 1 May 2001 12:03:21 -0700 (PDT)" Message-ID: <87itjiw1w3.fsf@mursu.pesa.fi> Lines: 37 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rick Duvall writes: > So, let me get this straight: To make a bootable CD, you need to: > > [ snipped ] /usr/src/release/Makefile has this nice picture of the setup: # +------------------------------------------------------------------------+ # |boot.flp | # +-----+-----+------------------------------------------------------------+ # |boot1|boot2|floppy filesystem "bootfd" | # +-----+-----+-+--------------------------------------------------------+-+ # |kernel | # +------------+-----------------------------------------+-+ # |mfs filesystem "mfsfd" | # +-----------------------------------------+ What you need is to make the kernel be able to both incorporate the mfs filesystem and then make it /. Grep LINT for MFS. Or MD or malloc disk ... Then craft the mfsfd - you already have some of the correct steps - and zot it into the kernel. There's a write_mfs_in_kernel.c in /usr/src/release for this purpose. Check also the .../release/scripts directory. You have to go through the vnconfig routine twice: once for the boot.flp and then to create the mfsfd. What you put in your "mfsfd" and how you link that with the contents of the rest of your CD is up to you. There's probably several approaches you can take ... I chose to craft links from the "mfsfd" to the rest of the ISO at /etc/rc-time. I'll do some experimenting with this some time ... Sorry, can't be much more specific than that, I have the stuff on a SCSI disk and my controller has been on it's way to the manufacturer for quite some time now :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 3 15:21:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 8573E37B422 for ; Thu, 3 May 2001 15:21:45 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id RAA03852; Thu, 3 May 2001 17:21:30 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 3 May 2001 17:21:30 -0500 (CDT) From: Chris Dillon To: Nick Rogness Cc: Subject: Re: /etc/rc.network and natd_enable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1924726952-988928490=:3479" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1924726952-988928490=:3479 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 3 May 2001, Nick Rogness wrote: > In 4.2-STABLE, /etc/rc.network has entries to turn on natd. > However, natd does not get enabled if you don't specify > natd_interface. WHat if you you have setup stored in a > configuration file and do not wish to supply an interface flag in > /etc/rc.conf? Well, natd does not turn on! I've attached a very simple, but untested patch that will DTRT. Anyone care to commit this if Nick says it works as expected? Just in case the attachment doesn't make it, here it is inline (be careful of cut'n'paste tab-to-space conversions). --- rc.network.orig Thu May 3 17:04:05 2001 +++ rc.network Thu May 3 17:18:52 2001 @@ -269,7 +269,9 @@ else natd_ifarg="-n ${natd_interface}" fi + fi + if [ -n "${natd_interface}" -o -n "${natd_flags}" ]; then echo -n ' natd'; ${natd_program:-/sbin/natd} ${natd_flags} ${natd_ifarg} fi ;; -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org --0-1924726952-988928490=:3479 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="rc.network.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="rc.network.patch" LS0tIHJjLm5ldHdvcmsub3JpZwlUaHUgTWF5ICAzIDE3OjA0OjA1IDIwMDEN CisrKyByYy5uZXR3b3JrCVRodSBNYXkgIDMgMTc6MTg6NTIgMjAwMQ0KQEAg LTI2OSw3ICsyNjksOSBAQA0KIAkJCQkJCWVsc2UNCiAJCQkJCQkJbmF0ZF9p ZmFyZz0iLW4gJHtuYXRkX2ludGVyZmFjZX0iDQogCQkJCQkJZmkNCisJCQkJ CWZpDQogDQorCQkJCQlpZiBbIC1uICIke25hdGRfaW50ZXJmYWNlfSIgLW8g LW4gIiR7bmF0ZF9mbGFnc30iIF07IHRoZW4NCiAJCQkJCQllY2hvIC1uICcg bmF0ZCc7ICR7bmF0ZF9wcm9ncmFtOi0vc2Jpbi9uYXRkfSAke25hdGRfZmxh Z3N9ICR7bmF0ZF9pZmFyZ30NCiAJCQkJCWZpDQogCQkJCQk7Ow0K --0-1924726952-988928490=:3479-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 0:13:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id A464F37B422 for ; Fri, 4 May 2001 00:13:18 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f447CxE59513; Fri, 4 May 2001 10:12:59 +0300 (EEST) (envelope-from ru) Date: Fri, 4 May 2001 10:12:59 +0300 From: Ruslan Ermilov To: Nick Rogness Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/rc.network and natd_enable Message-ID: <20010504101259.A58642@sunbay.com> Mail-Followup-To: Nick Rogness , freebsd-hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from nick@rogness.net on Thu, May 03, 2001 at 05:17:17PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 03, 2001 at 05:17:17PM -0500, Nick Rogness wrote: > > In 4.2-STABLE, /etc/rc.network has entries to turn on natd. However, natd > does not get enabled if you don't specify natd_interface. WHat if you you > have setup stored in a configuration file and do not wish to supply an > interface flag in /etc/rc.conf? Well, natd does not turn on! > > Would it make more sense to do something like (psuedo-ish code): > > if (natd_enable = YES) > > if (natd_interface defined) > natd -n $natd_interface $natd_flags > elif (natd_flags defined) > natd $natd_flags > fi > fi > > > It would allow for people to not specify a natd_interface but still be > able to run natd out of rc.conf. What does everyone think of this? > > I guess you pay the penalty if someone doesn't setup the flags properly > but I guess you could write that off as a config error anyways. > ${natd_interface} is required to set up the ``divert natd'' rule from /etc/rc.firewall. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 8:48:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bsdhome.dyndns.org (unknown [24.25.2.193]) by hub.freebsd.org (Postfix) with ESMTP id 076C737B422 for ; Fri, 4 May 2001 08:48:53 -0700 (PDT) (envelope-from bsd@bsdhome.com) Received: from vger.bsdhome.com (vger [192.168.220.2]) by bsdhome.dyndns.org (8.11.3/8.11.3) with ESMTP id f44FmoJ89541; Fri, 4 May 2001 11:48:51 -0400 (EDT) (envelope-from bsd@bsdhome.com) Received: (from bsd@localhost) by vger.bsdhome.com (8.11.3/8.11.1) id f44Fmor18661; Fri, 4 May 2001 11:48:50 -0400 (EDT) (envelope-from bsd) Date: Fri, 4 May 2001 11:48:50 -0400 From: Brian Dean To: Rick Duvall Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Set up loader to boot cd Message-ID: <20010504114850.A18459@vger.bsdhome.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from maillist@coastsight.com on Mon, Apr 30, 2001 at 11:31:22AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 30, 2001 at 11:31:22AM -0700, Rick Duvall wrote: > I am trying to make a custom boot CD for FreeBSD. I got it to the point > to where the CD will boot, load the kernel, but that's as far as it > get's. It does when it get's to the part where it wants to mount the root > devicd. It tried to access the floppy drive. > > So, do I need to vnconfig the boot.flp and put my own custom loader in it > or what? I don't want to be puting -C in every time I boot. Also, when I > put in -C, the kernel will load, but then can't find the CD device.... > > Any ideas would be appreciated. Maybe step by step instructions on making > a custom bootable live cd would be nice. I've had good success with the following which is a /bin/sh shell function. Use it as follows: % dofdboot /scratch/cdroot where /scratch/cdroot could be produced by: % make installkernel installworld DESTDIR=/scratch/cdroot After all that, specify boot/boot.fd as your ISO eltorito boot image file. Enjoy! -Brian -- Brian Dean bsd@FreeBSD.org bsd@bsdhome.com dofdboot () { DESTDIR="$1" echo "DOFDBOOT: DESTDIR=$DESTDIR" echo "Generating 2.88 MB boot floppy image" KERNELIMG=${DESTDIR}/kernel umount /mnt > /dev/null 2>&1 vnconfig -u /dev/vn0 > /dev/null 2>&1 echo "Initialize boot floppy image" dd if=/dev/zero of=${DESTDIR}/boot/boot.fd bs=1024 count=2880 vnconfig -s labels -c /dev/vn0 ${DESTDIR}/boot/boot.fd disklabel -Brw /dev/vn0c minimum2 newfs -o space -T minimum2 /dev/vn0c mount /dev/vn0c /mnt echo "Copy kernel from ${KERNELIMG} to the boot floppy" cp -p ${KERNELIMG} /mnt mkdir /mnt/boot echo "Copy boot1, boot2, and loader to boot floppy" (cd ${DESTDIR}/boot && cp -p boot1 boot2 loader /mnt/boot) echo "Create boot.config" echo "-P" > /mnt/boot.config echo "Create loader.rc" cat < /mnt/boot/loader.rc echo "BSD CDROM ROOT IMAGE" echo "LOADING KERNEL" load /kernel boot -C EOF umount /mnt } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 9:59: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by hub.freebsd.org (Postfix) with ESMTP id 7600737B422 for ; Fri, 4 May 2001 09:58:59 -0700 (PDT) (envelope-from blc@bsdwins.com) Received: (from blc@localhost) by bsdone.bsdwins.com (8.11.3/8.11.0) id f44GwwQ26481 for freebsd-hackers@FreeBSD.org; Fri, 4 May 2001 12:58:58 -0400 (EDT) (envelope-from blc) Date: Fri, 4 May 2001 12:58:58 -0400 From: "Brad L. Chisholm" To: freebsd-hackers@FreeBSD.org Subject: Optimal setup for large raid? Message-ID: <20010504125858.C18876@bsdone.bsdwins.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I sent this to -questions a few days ago, but never received any response, so I thought I'd try here. My apologies if you've seen this more than once. I'm also interested in what might be appropriate filesystem settings (newfs) for a large volume like this which will contain relatively few, large files. ------------- We are planning to create a large software raid volume, and I am interested in input about what might make the best configuration. We have 52 identical 9Gb drives (Seagate ST19171W) spread across 4 SCSI controllers (Adaptec AHA 2944UW), with 13 drives per controller. We want fault-tolerance, but cannot afford to "waste" 50% of our space for a mirrored (raid1) configuration. Thus, we are considering some sort of raid5 setup using vinum (possibly in combination with ccd). We are running FreeBSD 4.3-RELEASE, on a 550Mz P3 with 384Mb of memory. Possible configurations: Configuration #1: A single raid5 vinum volume consisting of all 52 drives. Questions: A) Is there a performance penalty for this many drives in a raid5 array? B) Should the plex be configured with sequential drives on different controllers? (i.e. if drives 1-13 are on controller 1, 14-27 on controller 2, 27-39 on controller 3, and 40-52 on controller 4, should the drive ordering be: 1,14,27,40,2,15,28,41,... or 1,2,3,4,5,6,7,8,... Configuration #2: Multiple raid5 vinum volumes (perhaps 1 per controller), combined into a single volume by striping the raid5 volumes. (Basically a "raid50" setup.) Questions: A) Is this possible with vinum? From the documentation, it didn't appear to be, so we were considering using 'ccd' to stripe the raid5 volumes together. B) Would this perform better, worse, or about the same as #1? Any other configurations that might prove superior? The final volume will be used as an online backup area, and will contain a relatively few, large tar files. Write performance will likely be more important that read, although I realize using raid5 will impact write performance. Any suggestions on what might be the best stripe size to use? Thanks in advance for any suggestions you might have. -Brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 10:10:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bdr-xcon.matchlogic.com (mail.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 259EA37B422; Fri, 4 May 2001 10:10:12 -0700 (PDT) (envelope-from crandall@matchlogic.com) Received: by mail.matchlogic.com with Internet Mail Service (5.5.2653.19) id ; Fri, 4 May 2001 11:10:08 -0600 Message-ID: <5FE9B713CCCDD311A03400508B8B30130828ECB6@bdr-xcln.corp.matchlogic.com> From: Charles Randall To: 'Joao Carlos' , hackers@freebsd.org Cc: questions@freebsd.org Subject: RE: real time Date: Fri, 4 May 2001 11:10:05 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's one starting point, http://www.rtmx.com/ They offer extensions to OpenBSD. Charles -----Original Message----- From: Joao Carlos [mailto:jcarlos@esbrasil.com] Sent: Thursday, May 03, 2001 11:59 AM To: hackers@freebsd.org Cc: questions@freebsd.org Subject: real time Does FreeBSD has any related work about it as an real time operating system? Where can i find information about that ?? --- Joao Carlos jcarlos@esbrasil.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 13: 6:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bsdconspiracy.net (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 53C4B37B423; Fri, 4 May 2001 13:06:42 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from wes by bsdconspiracy.net with local (Exim 3.14 #1) id 14vlpX-0008Nr-00; Fri, 04 May 2001 14:05:35 -0600 Subject: Re: real time In-Reply-To: <5FE9B713CCCDD311A03400508B8B30130828ECB6@bdr-xcln.corp.matchlogic.com> from Charles Randall at "May 4, 2001 11:10:05 am" To: Charles Randall Date: Fri, 4 May 2001 14:05:35 -0600 (MDT) Cc: "'Joao Carlos'" , hackers@freebsd.org, questions@freebsd.org X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: From: Wes Peters Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charles: > > -----Original Message----- > > Joao Carlos asked: > > > > Does FreeBSD has any related work about it as an real time operating > > system? > > Where can i find information about that ?? > > Here's one starting point, > > http://www.rtmx.com/ > > They offer extensions to OpenBSD. Used to. RTMX contributed the RTMX code base to OpenBSD and stopped distributing it themselves over a year ago. Since then, it has disappeared, with no mention of it on the OpenBSD web site. Neither OpenBSD.org, rtmx.com, nor rtmx.net has a "search" feature, so looking for it is nearly impossible. There is nothing in the OpenBSD change logs mentioning RTMX, either. You might want to ask Theo what happened to the RTMX code. -- Wes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 13:12: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.147.224.201]) by hub.freebsd.org (Postfix) with ESMTP id 7ED3B37B422; Fri, 4 May 2001 13:11:55 -0700 (PDT) (envelope-from jim@thehousleys.net) Received: (from root@localhost) by thehousleys.net (8.11.3/8.11.2) id f44KBcc38148; Fri, 4 May 2001 16:11:38 -0400 (EDT) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (baby.int.thehousleys.net [192.168.0.24]) (authenticated) by thehousleys.net (8.11.3/8.11.3) with ESMTP id f44KBam38140; Fri, 4 May 2001 16:11:36 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <3AF30CF8.FC28EDA1@thehousleys.net> Date: Fri, 04 May 2001 16:11:36 -0400 From: James Housley X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Wes Peters Cc: Charles Randall , "'Joao Carlos'" , hackers@freebsd.org, questions@freebsd.org, Joel Sherrill Subject: Re: real time References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > > Charles: > > > > -----Original Message----- > > > Joao Carlos asked: > > > > > > Does FreeBSD has any related work about it as an real time operating > > > system? > > > Where can i find information about that ?? > > > > Here's one starting point, > > > > http://www.rtmx.com/ > > > > They offer extensions to OpenBSD. > > Used to. RTMX contributed the RTMX code base to OpenBSD and stopped > distributing it themselves over a year ago. Since then, it has > disappeared, with no mention of it on the OpenBSD web site. Neither > OpenBSD.org, rtmx.com, nor rtmx.net has a "search" feature, so > looking for it is nearly impossible. There is nothing in the OpenBSD > change logs mentioning RTMX, either. > RTEMS, http://www.oarcorp.com, does compile and run on FreeBSD. I have been contacted/contacting one of their main people about closer ties. The tools are in the ports tree. Jim -- /"\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ ----------------------------------------------------------------- jeh@FreeBSD.org http://www.FreeBSD.org The Power to Serve jim@TheHousleys.Net http://www.TheHousleys.net --------------------------------------------------------------------- microsoft: "where do you want to go today?" linux: "where do you want to go tomorrow?" BSD: "are you guys coming, or what?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 13:50: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 0F56037B422; Fri, 4 May 2001 13:50:04 -0700 (PDT) (envelope-from hosokawa@itc.keio.ac.jp) Received: from mail2.rim.or.jp by serio.al.rim.or.jp (3.7W/HMX-13) id FAA09882; Sat, 5 May 2001 05:49:25 +0900 (JST) Received: from bougainvillea.FromTo.Cc (shell [202.247.191.98]) by mail2.rim.or.jp (8.9.3/3.7W) id FAA28108; Sat, 5 May 2001 05:49:24 +0900 (JST) Date: Sat, 05 May 2001 05:49:24 +0900 Message-ID: <86lmocdeln.wl@bougainvillea.FromTo.Cc> From: Tatsumi Hosokawa To: hackers@FreeBSD.org Cc: cjh@FreeBSD.org, statue@mail.elife.idv.tw, zhecka@klondike.ru, hosokawa@FreeBSD.org Subject: multilingual boot.flp for 4.3-RELEASE User-Agent: Wanderlust/2.4.1 (Stand By Me) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I've ported multilingual boot.flp to 4.3-RELEASE. Currently, almost all documents are translated to Japanese by me and doc-jp project. I put the source tarball (release-*.tar.gz), compiled binaries (*/*.flp, currently English and Japanese support only) and translation kit (tranlation-kit-*.tar.gz) at ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/I18N-flp/4.3-RELEASE/ This mail is cc'ed to the translator of Korean, Chinese, and Russian translators of 4.2 multilinugual boot.flp. If you can update the translation to 4.3, please tell me about it. Thank you very much. (Sorry for being away from FreeBSD community for months. That's because I've been hospitalized on January, and it made my daytime business terribly busy from February to April) -- Tatsumi Hosokawa http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 16: 5:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 5A62737B423 for ; Fri, 4 May 2001 16:05:40 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id 00BEE3E0B for ; Fri, 4 May 2001 16:05:39 -0700 (PDT) To: hackers@freebsd.org Subject: Getting peer credentials on a unix domain socket Date: Fri, 04 May 2001 16:05:39 -0700 From: Dima Dorfman Message-Id: <20010504230540.00BEE3E0B@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a reliable method of obtaining the credentials (uid/gid) of a peer (SOCK_STREAM sockets only, obviously) on a unix domain socket? All the Stevens books I have suggest that there isn't, but I'm wondering if something has been developed since those books were published. Note that a BSD/OS-like LOCAL_CREDS socket opt is not sufficient because using the latter the process must wait until the peer sends something before they can learn its credentials. If this process intends to drop the connection if it's not from an authorized source, this may lead to a DoS attack. Timers don't help, either; think of TCP SYN flood-like attacks. Thanks, Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 17: 7:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id EFCE737B424 for ; Fri, 4 May 2001 17:07:43 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f4507cW04458; Fri, 4 May 2001 17:07:38 -0700 (PDT) Date: Fri, 4 May 2001 17:07:38 -0700 From: Alfred Perlstein To: Dima Dorfman Cc: hackers@FreeBSD.ORG Subject: Re: Getting peer credentials on a unix domain socket Message-ID: <20010504170738.U18676@fw.wintelcom.net> References: <20010504230540.00BEE3E0B@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010504230540.00BEE3E0B@bazooka.unixfreak.org>; from dima@unixfreak.org on Fri, May 04, 2001 at 04:05:39PM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dima Dorfman [010504 16:06] wrote: > Is there a reliable method of obtaining the credentials (uid/gid) of a > peer (SOCK_STREAM sockets only, obviously) on a unix domain socket? > All the Stevens books I have suggest that there isn't, but I'm > wondering if something has been developed since those books were > published. Note that a BSD/OS-like LOCAL_CREDS socket opt is not > sufficient because using the latter the process must wait until the > peer sends something before they can learn its credentials. If this > process intends to drop the connection if it's not from an authorized > source, this may lead to a DoS attack. Timers don't help, either; > think of TCP SYN flood-like attacks. Someone had some patches for a getpeercreds() syscall, but I wasn't happy with it considering we already have the sendmsg() stuff to pass credentials along with the fact that the initial creator of a socket may be long gone before it's used to connect to something. -- -Alfred Perlstein - [alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 18:47:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from zeus.superscript.com (zeus.superscript.com [206.234.89.16]) by hub.freebsd.org (Postfix) with SMTP id 4616937B422 for ; Fri, 4 May 2001 18:47:08 -0700 (PDT) (envelope-from web@superscript.com) Received: (qmail 30237 invoked by uid 1008); 5 May 2001 01:47:02 -0000 Date: Fri, 4 May 2001 21:47:02 -0400 From: "William E. Baxter" To: hackers@freebsd.org Subject: Re: Getting peer credentials on a unix domain socket Message-ID: <20010504214702.A29392@zeus.superscript.com> References: <20010504230540.00BEE3E0B@bazooka.unixfreak.org> <20010504170738.U18676@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010504170738.U18676@fw.wintelcom.net>; from bright@wintelcom.net on Fri, May 04, 2001 at 05:07:38PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 04, 2001 at 05:07:38PM -0700, Alfred Perlstein wrote: > * Dima Dorfman [010504 16:06] wrote: > > Is there a reliable method of obtaining the credentials (uid/gid) of a > > peer (SOCK_STREAM sockets only, obviously) on a unix domain socket? > > All the Stevens books I have suggest that there isn't, but I'm > > wondering if something has been developed since those books were > > published. Note that a BSD/OS-like LOCAL_CREDS socket opt is not > > sufficient because using the latter the process must wait until the > > peer sends something before they can learn its credentials. If this > > process intends to drop the connection if it's not from an authorized > > source, this may lead to a DoS attack. Timers don't help, either; > > think of TCP SYN flood-like attacks. > > Someone had some patches for a getpeercreds() syscall, but I wasn't > happy with it considering we already have the sendmsg() stuff to pass > credentials along with the fact that the initial creator of a socket > may be long gone before it's used to connect to something. I wrote that patch. Links to my patches appear at http://www.superscript.com/patches/intro.html Explanatory material and links to the same appear at http://www.superscript.com/ucspi-ipc/getpeereid.html My patch is designed to satisfy these conditions: 1. Server can obtain credentials of connect() caller (effective uid and gid suffice). 2. Server can obtain credentials without depending on client to send data. Having met these conditions, it is nearly trivial to create privileged servers that run behind a unix socket, in an environment under their own control. In many instances one can replace setuid programs with such servers. How does one meet these two conditions with vanilla FreeBSD, NetBSD, or OpenBSD? So far as I know, the answer is "One cannot." Unfortunately, sendmsg() mechanisms fail to satisfy condition (2). As Dima pointed out, this means a local user can launch DoS attacks anonymously. The server operates at the mercy of the client. And as Alfred points out, perhaps unintentionally, the information should be passed at connect(), because the client process may exit before accept() returns. Many simple servers require credentials and nothing more. In such cases, there is no reason for the client to wait until accept() returns. My ucspi-ipc package provides a framework for turning filters into servers based on getpeereid(): http://www.superscript.com/ucspi-ipc/intro.html A collection of simple servers, some of which perform operations normally delegated to setuid programs, is available at: http://www.superscript.com/ipctools/intro.html Linux already has sufficient basis for implementing getpeereid(), with getsockopt() and SO_PEERCRED, and my ucspi-ipc package uses them to satisfy the two conditions stated above. I created patches for NetBSD, FreeBSD, and OpenBSD, hoping to contribute better facilities to these projects. None of the implementors displayed any enthusiasm. Nor did they demonstrate how to satisfy the two conditions stated above with existing system features. Too bad. If you think that getpeereid(), or sufficient basis for it, should appear in future versions of *BSD, please tell the implementors. My implementation remains theirs for the asking. W. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 19:32:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id BD29437B424 for ; Fri, 4 May 2001 19:32:46 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 37E136ACBA; Sat, 5 May 2001 12:02:44 +0930 (CST) Date: Sat, 5 May 2001 12:02:44 +0930 From: Greg Lehey To: "Brad L. Chisholm" Cc: freebsd-hackers@FreeBSD.org Subject: Re: Optimal setup for large raid? Message-ID: <20010505120243.F67787@wantadilla.lemis.com> References: <20010504125858.C18876@bsdone.bsdwins.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010504125858.C18876@bsdone.bsdwins.com>; from blc@bsdwins.com on Fri, May 04, 2001 at 12:58:58PM -0400 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 4 May 2001 at 12:58:58 -0400, Brad L. Chisholm wrote: > I sent this to -questions a few days ago, but never received > any response, so I thought I'd try here. My apologies if you've > seen this more than once. > > I'm also interested in what might be appropriate filesystem > settings (newfs) for a large volume like this which will contain > relatively few, large files. > > ------------- > > We are planning to create a large software raid volume, > and I am interested in input about what might make the > best configuration. > > We have 52 identical 9Gb drives (Seagate ST19171W) spread > across 4 SCSI controllers (Adaptec AHA 2944UW), with 13 > drives per controller. We want fault-tolerance, but cannot > afford to "waste" 50% of our space for a mirrored (raid1) > configuration. Thus, we are considering some sort of > raid5 setup using vinum (possibly in combination with ccd). I can't see any advantage in using ccd here. It doesn't do RAID-5 itself, and Vinum does everything that ccd does. > We are running FreeBSD 4.3-RELEASE, on a 550Mz P3 with > 384Mb of memory. > > Possible configurations: > > Configuration #1: A single raid5 vinum volume consisting of all > 52 drives. > > Questions: > > A) Is there a performance penalty for this many drives in a > raid5 array? Not in normal operation. In degraded operation, where one drive is down, you have to read from *all* the drives to reconstruct a block on the dead drive. On the other hand, this would happen less often (every 51 accesses), so maybe it wouldn't be such a hit after all. In addition, you'd have a greater chance of a drive failing, and also a greater chance of two drives failing (which is unrecoverable). > B) Should the plex be configured with sequential drives on > different controllers? (i.e. if drives 1-13 are on controller 1, > 14-27 on controller 2, 27-39 on controller 3, and 40-52 on > controller 4, should the drive ordering be: > > 1,14,27,40,2,15,28,41,... > or 1,2,3,4,5,6,7,8,... Good question. I suppose the hopping would give marginally better performance for single accesses, and since your files are big, this might be a better way to go. > > Configuration #2: Multiple raid5 vinum volumes (perhaps 1 per controller), > combined into a single volume by striping the raid5 > volumes. (Basically a "raid50" setup.) > > Questions: > > A) Is this possible with vinum? No. > From the documentation, it didn't appear to be, so we were > considering using 'ccd' to stripe the raid5 volumes > together. Ah, that was the reason. I still don't think this is a good idea. > B) Would this perform better, worse, or about the same as #1? Under normal circumstances there shouldn't be any difference. > Any other configurations that might prove superior? If you really need a single volume of that size, you're probably better off with scenario #1. > The final volume will be used as an online backup area, and will > contain a relatively few, large tar files. Write performance will > likely be more important that read, although I realize using raid5 > will impact write performance. To put it more clearly: write performance on RAID-5 is terrible, about 25% of read performance. > Any suggestions on what might be the best stripe size to use? Not a power of 2, between 256 and 512 kB. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 20:14:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cody.jharris.com (cody.jharris.com [205.238.128.83]) by hub.freebsd.org (Postfix) with ESMTP id 6B0D537B422; Fri, 4 May 2001 20:14:36 -0700 (PDT) (envelope-from nick@rogness.net) Received: from localhost (nick@localhost) by cody.jharris.com (8.11.1/8.9.3) with ESMTP id f454PSH23695; Fri, 4 May 2001 23:25:28 -0500 (CDT) (envelope-from nick@rogness.net) Date: Fri, 4 May 2001 23:25:28 -0500 (CDT) From: Nick Rogness X-Sender: nick@cody.jharris.com To: Ruslan Ermilov Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/rc.network and natd_enable In-Reply-To: <20010504101259.A58642@sunbay.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 May 2001, Ruslan Ermilov wrote: > On Thu, May 03, 2001 at 05:17:17PM -0500, Nick Rogness wrote: > > In > 4.2-STABLE, /etc/rc.network has entries to turn on natd. However, > natd > does not get enabled if you don't specify natd_interface. > WHat if you you > have setup stored in a configuration file and do not > wish to supply an > > interface flag in /etc/rc.conf? Well, natd does not turn on! > > > > Would it make more sense to do something like (psuedo-ish code): > > > > if (natd_enable = YES) > > > > if (natd_interface defined) > > natd -n $natd_interface $natd_flags > > elif (natd_flags defined) > > natd $natd_flags > > fi > > fi > > > > > > It would allow for people to not specify a natd_interface but still > be > able to run natd out of rc.conf. What does everyone think of > this? > > > I guess you pay the penalty if someone doesn't setup the flags > properly > but I guess you could write that off as a config error > anyways. > > > ${natd_interface} is required to set up the ``divert natd'' rule > from /etc/rc.firewall. > Damn! And if someone enters an IP as natd_interface...does the firewall rules error out? (haven't tried it but looks as if it would) I would suspect that if the user doesn't specify natd_interface in rc.conf that he would have to be aware that the firewall rule for nat did not get added. I don't necessarily think that's a bad thing...but maybe it is. Nick Rogness - Keep on Routing in a Free World... "FreeBSD: The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 20:17:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cody.jharris.com (cody.jharris.com [205.238.128.83]) by hub.freebsd.org (Postfix) with ESMTP id 6433B37B423; Fri, 4 May 2001 20:17:16 -0700 (PDT) (envelope-from nick@rogness.net) Received: from localhost (nick@localhost) by cody.jharris.com (8.11.1/8.9.3) with ESMTP id f454S8G23732; Fri, 4 May 2001 23:28:08 -0500 (CDT) (envelope-from nick@rogness.net) Date: Fri, 4 May 2001 23:28:08 -0500 (CDT) From: Nick Rogness X-Sender: nick@cody.jharris.com To: Ruslan Ermilov Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/rc.network and natd_enable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 May 2001, Nick Rogness wrote: > On Fri, 4 May 2001, Ruslan Ermilov wrote: > > > > > Damn! And if someone enters an IP as natd_interface...does the > firewall rules error out? (haven't tried it but looks as if it > would) I take that back...it should work ok...sorry for the slip up. > > I would suspect that if the user doesn't specify natd_interface in > rc.conf that he would have to be aware that the firewall rule for > nat did not get added. I don't necessarily think that's a bad > thing...but maybe it is. Nick Rogness - Keep on Routing in a Free World... "FreeBSD: The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 20:22:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 9211D37B423; Fri, 4 May 2001 20:22:13 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id 3FD923E0B; Fri, 4 May 2001 20:22:13 -0700 (PDT) To: "William E. Baxter" Cc: hackers@freebsd.org, alfred@freebsd.org Subject: Re: Getting peer credentials on a unix domain socket In-Reply-To: <20010504214702.A29392@zeus.superscript.com>; from web@superscript.com on "Fri, 4 May 2001 21:47:02 -0400" Date: Fri, 04 May 2001 20:22:13 -0700 From: Dima Dorfman Message-Id: <20010505032213.3FD923E0B@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "William E. Baxter" writes: > On Fri, May 04, 2001 at 05:07:38PM -0700, Alfred Perlstein wrote: > > * Dima Dorfman [010504 16:06] wrote: > > > Is there a reliable method of obtaining the credentials (uid/gid) of a > > > peer (SOCK_STREAM sockets only, obviously) on a unix domain socket? > > > All the Stevens books I have suggest that there isn't, but I'm > > > wondering if something has been developed since those books were > > > published. Note that a BSD/OS-like LOCAL_CREDS socket opt is not > > > sufficient because using the latter the process must wait until the > > > peer sends something before they can learn its credentials. If this > > > process intends to drop the connection if it's not from an authorized > > > source, this may lead to a DoS attack. Timers don't help, either; > > > think of TCP SYN flood-like attacks. > > > > Someone had some patches for a getpeercreds() syscall, but I wasn't > > happy with it considering we already have the sendmsg() stuff to pass > > credentials along with the fact that the initial creator of a socket > > may be long gone before it's used to connect to something. > > > I wrote that patch. Links to my patches appear at > > http://www.superscript.com/patches/intro.html Cool! Actually, I wrote a patch[1] to implement something simlar before sending my original e-mail. I looked at your patches, and it seems the main difference is that mine uses the getsockopt interface instead of a system call, and mine uses struct xucred which, I believe, is the correct way of passing user credentials to the userland (this structure didn't exist in FreeBSD 4.0, which is what it looks like your patch is against). Other than that they do pretty much the same thing :-). > Explanatory material and links to the same appear at > > http://www.superscript.com/ucspi-ipc/getpeereid.html > > My patch is designed to satisfy these conditions: > > 1. Server can obtain credentials of connect() caller (effective uid and gid suffice). > 2. Server can obtain credentials without depending on client to send data. > > Having met these conditions, it is nearly trivial to create privileged servers > that run behind a unix socket, in an environment under their own control. In > many instances one can replace setuid programs with such servers. Just to expand on that a little more (for others on the list), consider crontab(1). It's setuid root right now. Obviously that's not good. One way of getting rid of that setuid bit is to have cron(8) (or another daemon) listen on a world-writable unix domain socket, and have crontab(1) just be a user interface which sends the information via that socket. With some mechanism to get the credentials of the user that connected, this would be possible. Regards, Dima Dorfman dima@unixfreak.org [1] http://www.unixfreak.org/~dima/home/peercred.diff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 20:35: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E742237B422 for ; Fri, 4 May 2001 20:35:00 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f453YvC05837; Fri, 4 May 2001 20:34:57 -0700 (PDT) Date: Fri, 4 May 2001 20:34:57 -0700 From: Alfred Perlstein To: Dima Dorfman Cc: "William E. Baxter" , hackers@freebsd.org Subject: Re: Getting peer credentials on a unix domain socket Message-ID: <20010504203457.V18676@fw.wintelcom.net> References: <20010504214702.A29392@zeus.superscript.com> <20010505032213.3FD923E0B@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010505032213.3FD923E0B@bazooka.unixfreak.org>; from dima@unixfreak.org on Fri, May 04, 2001 at 08:22:13PM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dima Dorfman [010504 20:22] wrote: > > Just to expand on that a little more (for others on the list), > consider crontab(1). It's setuid root right now. Obviously that's > not good. One way of getting rid of that setuid bit is to have > cron(8) (or another daemon) listen on a world-writable unix domain > socket, and have crontab(1) just be a user interface which sends the > information via that socket. With some mechanism to get the > credentials of the user that connected, this would be possible. The silly part of it is that the socket's initial credentials might be different than the holder's credentials. What makes a lot more sense is packaging the messages with the credentials using the existing interface rather than trusting possibly stale credential information. -- -Alfred Perlstein - [alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 20:56: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 6AADC37B423; Fri, 4 May 2001 20:56:05 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id B504E3E0B; Fri, 4 May 2001 20:56:04 -0700 (PDT) To: Alfred Perlstein Cc: "William E. Baxter" , hackers@freebsd.org Subject: Re: Getting peer credentials on a unix domain socket In-Reply-To: <20010504203457.V18676@fw.wintelcom.net>; from alfred@freebsd.org on "Fri, 4 May 2001 20:34:57 -0700" Date: Fri, 04 May 2001 20:56:04 -0700 From: Dima Dorfman Message-Id: <20010505035604.B504E3E0B@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > * Dima Dorfman [010504 20:22] wrote: > > > > Just to expand on that a little more (for others on the list), > > consider crontab(1). It's setuid root right now. Obviously that's > > not good. One way of getting rid of that setuid bit is to have > > cron(8) (or another daemon) listen on a world-writable unix domain > > socket, and have crontab(1) just be a user interface which sends the > > information via that socket. With some mechanism to get the > > credentials of the user that connected, this would be possible. > > The silly part of it is that the socket's initial credentials > might be different than the holder's credentials. Perhaps it is silly to a human, but I don't see how it makes much of a difference. I'm assuming you're talking about either fork()/exec() or descriptor passing. I don't mean to sound rude, but if a user is silly enough to forget to close that descriptor before exec'ing an untrusted program, or he passes it to a program that has no business using it, there are bigger problems. OTOH, the user may legitmately want to do that. If the server is concerned about that, it can always use both techniques (this and SCM_CREDS) together. Without using this, however, the server may be vulnerable to a DoS attack. In cron's case, this attack may be in the form of opening lots of connections and not writing anything. It can't refuse duplicate connections from the same user because it doesn't know who's connected until they send something. BTW, I hope I made it clear that this is for *stream sockets*. It's horribly useless on datagram sockets. Just making sure in case that's what you were thinking about. Thanks, Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 4 21:12:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from zeus.superscript.com (zeus.superscript.com [206.234.89.16]) by hub.freebsd.org (Postfix) with SMTP id 9501337B424 for ; Fri, 4 May 2001 21:12:07 -0700 (PDT) (envelope-from web@superscript.com) Received: (qmail 30751 invoked by uid 1008); 5 May 2001 04:12:11 -0000 Date: Sat, 5 May 2001 00:12:11 -0400 From: "William E. Baxter" To: Alfred Perlstein Cc: hackers@freebsd.org, dima@unixfreak.org Subject: Re: Getting peer credentials on a unix domain socket Message-ID: <20010505001211.A27676@zeus.superscript.com> References: <20010504214702.A29392@zeus.superscript.com> <20010505032213.3FD923E0B@bazooka.unixfreak.org> <20010504203457.V18676@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010504203457.V18676@fw.wintelcom.net>; from alfred@freebsd.org on Fri, May 04, 2001 at 08:34:57PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 04, 2001 at 08:34:57PM -0700, Alfred Perlstein wrote: > The silly part of it is that the socket's initial credentials > might be different than the holder's credentials. A user calls connect() with one set of credentials, subsequently changes credentials, and writes to the socket. Alternatively, the same user first changes credentials, then calls connect() and writes to the socket. So what? > What makes a lot more sense is packaging the messages with the > credentials using the existing interface rather than trusting > possibly stale credential information. My conditions are: 1. Server can obtain credentials of connect() caller (effective uid and gid suffice). 2. Server can obtain credentials without depending on client to send data. Condition (2) prevents local users from launching an anonymous DoS attack by calling connect() and sending no data. How does your approach satisfy condition (2)? W. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 3:33:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web12204.mail.yahoo.com (web12204.mail.yahoo.com [216.136.173.88]) by hub.freebsd.org (Postfix) with SMTP id CE95237B423 for ; Sat, 5 May 2001 03:33:49 -0700 (PDT) (envelope-from nadiach_4@yahoo.com) Message-ID: <20010505103349.16398.qmail@web12204.mail.yahoo.com> Received: from [203.135.3.98] by web12204.mail.yahoo.com; Sat, 05 May 2001 03:33:49 PDT Date: Sat, 5 May 2001 03:33:49 -0700 (PDT) From: Nadia chaudhary Subject: minimum size bsd requird To: freebsd-hackers@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm the student of BCS final year. Our project is to make an embedded system providing the faciltiy of email. and for that purpose we need small size OS. i heard about BSD and therefore we need a small size BSD .If you can help us to provide us wirh at least 1 MB os that will be of great help. bye nadia __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 3:43:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2B64E37B422 for ; Sat, 5 May 2001 03:43:31 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f45AhUM09983; Sat, 5 May 2001 03:43:30 -0700 (PDT) Date: Sat, 5 May 2001 03:43:29 -0700 From: Alfred Perlstein To: Nadia chaudhary Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: minimum size bsd requird Message-ID: <20010505034329.D18676@fw.wintelcom.net> References: <20010505103349.16398.qmail@web12204.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010505103349.16398.qmail@web12204.mail.yahoo.com>; from nadiach_4@yahoo.com on Sat, May 05, 2001 at 03:33:49AM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Nadia chaudhary [010505 03:34] wrote: > Hello, > I'm the student of BCS final year. Our project is to > make an embedded system providing the faciltiy of > email. and for that purpose we need small size OS. i > heard about BSD and therefore we need a small size BSD > .If you can help us to provide us wirh at least 1 MB > os that will be of great help. You should take a look at http://people.freebsd.org/~picobsd/ -- -Alfred Perlstein - [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 3:45:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from webmail.netcom.no (webmail.netcom.no [212.45.188.36]) by hub.freebsd.org (Postfix) with ESMTP id 2F98E37B422 for ; Sat, 5 May 2001 03:45:47 -0700 (PDT) (envelope-from sgt@netcom.no) Received: from hal ([212.45.183.80]) by webmail.netcom.no (Netscape Messaging Server 4.15) with ESMTP id GCUZ8L00.MND; Sat, 5 May 2001 12:45:57 +0200 Date: Sat, 5 May 2001 12:45:41 +0200 (CEST) From: Torbjorn Kristoffersen X-Sender: To: Nadia chaudhary Cc: Subject: Re: minimum size bsd requird In-Reply-To: <20010505103349.16398.qmail@web12204.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 May 2001, Nadia chaudhary wrote: > Hello, > I'm the student of BCS final year. Our project is to > make an embedded system providing the faciltiy of > email. and for that purpose we need small size OS. i > heard about BSD and therefore we need a small size BSD > .If you can help us to provide us wirh at least 1 MB > os that will be of great help. > bye > nadia All I can think of is PicoBSD. See homepage at http://people.freebsd.org/~picobsd/ and the source code at /usr/src/release/picobsd and a mailing-list: freebsd-small@freebsd.org Regards, Torbjorn Kristoffersen sgt@netcom.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 9: 2:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from chmod.ath.cx (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id CF32C37B422 for ; Sat, 5 May 2001 09:02:40 -0700 (PDT) (envelope-from ajh3@chmod.ath.cx) Received: by chmod.ath.cx (Postfix, from userid 1001) id 5D6ADA876; Sat, 5 May 2001 11:01:41 -0500 (CDT) Date: Sat, 5 May 2001 11:01:41 -0500 From: Andrew Hesford To: Nadia chaudhary Cc: freebsd-hackers@FreeBSD.org Subject: Re: minimum size bsd requird Message-ID: <20010505110141.A43798@cec.wustl.edu> References: <20010505103349.16398.qmail@web12204.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010505103349.16398.qmail@web12204.mail.yahoo.com>; from nadiach_4@yahoo.com on Sat, May 05, 2001 at 03:33:49AM -0700 X-Loop: Andrew Hesford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 05, 2001 at 03:33:49AM -0700, Nadia chaudhary wrote: > Hello, > I'm the student of BCS final year. Our project is to > make an embedded system providing the faciltiy of > email. and for that purpose we need small size OS. i > heard about BSD and therefore we need a small size BSD > .If you can help us to provide us wirh at least 1 MB > os that will be of great help. > bye > nadia What do you mean, "the facility of email"? A client, or a server? If you're talking about a client, I can get PicoBSD on a single floppy, and mutt is 1/2 MB; I'm not sure if this will compress onto a single floppy, but it sure gets close. Mutt provides SMTP, POP3 and IMAP support; you can't get better than that. Of course, you can always implement your own lightweight client, or try to strip mutt of IMAP to make it more lightweight. As one who enjoys cramming firewalls on single diskettes, I can tell you that PicoBSD will indeed get smaller than Linux. The reason is the ability to crunch binaries, which I haven't seen on a linux system. The only other small UNIX-like system I can think of is QNX, which can fit on a single floppy, and has a windowing system and at least a web browser. -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 10:31:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from waste.silverserver.co.at (waste.silverserver.co.at [194.152.178.7]) by hub.freebsd.org (Postfix) with ESMTP id 8ABA237B423 for ; Sat, 5 May 2001 10:31:07 -0700 (PDT) (envelope-from if@sil.at) Received: from ikarus (ikarus.sil.at [194.152.178.41]) by waste.silverserver.co.at (8.11.2/8.11.2) with ESMTP id f45HPmr05041 for ; Sat, 5 May 2001 19:25:48 +0200 Date: Sat, 5 May 2001 19:36:07 +0200 (MEST) From: Ingo Flaschberger X-Sender: chaoztc@ikarus To: freebsd-hackers@FreeBSD.ORG Subject: no keyboard Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi i'm not sure if that is the right list, but i hope u could help me. i'm working at an iap, and we are using freebsd (4.2) boxes as routers. normally no keyboard or monitor is attached to the box. the problem is, when i connect after the boot a keyboard at the box, it is not recognized. at the colocations we often need access to this boxes (not remote access). is there a solution for this problem? bye, Ingo SILVER SERVER \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\ \\ \ if@sil.at www.sil.at Backbone Team bbt@vbs.at keep your backbone tidy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 10:35:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id 5FB5437B422 for ; Sat, 5 May 2001 10:35:22 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by peitho.fxp.org (Postfix, from userid 1501) id 0E1D513614; Sat, 5 May 2001 13:35:10 -0400 (EDT) Date: Sat, 5 May 2001 13:35:10 -0400 From: Chris Faulhaber To: Ingo Flaschberger Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: no keyboard Message-ID: <20010505133510.A94399@peitho.fxp.org> Mail-Followup-To: Chris Faulhaber , Ingo Flaschberger , freebsd-hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from if@sil.at on Sat, May 05, 2001 at 07:36:07PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 05, 2001 at 07:36:07PM +0200, Ingo Flaschberger wrote: > Hi >=20 > i'm not sure if that is the right list, but i hope u could help me. >=20 > i'm working at an iap, and we are using freebsd (4.2) boxes as routers. > normally no keyboard or monitor is attached to the box. > the problem is, when i connect after the boot a keyboard at the box, it is > not recognized. at the colocations we often need access to this boxes (not > remote access).=20 > is there a solution for this problem? >=20 See atkbd(4)... (remove 'flags 0x1' from the atkbd0 line) --=20 Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: FreeBSD: The Power To Serve iEYEARECAAYFAjr0Oc0ACgkQObaG4P6BelAxWACgmgn1OLU4mNBJOy62SxK5419f rXcAn3t8pHRbMAPBS+CMMx4GGWmfRDls =nGl6 -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 11:27:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from waste.silverserver.co.at (waste.silverserver.co.at [194.152.178.7]) by hub.freebsd.org (Postfix) with ESMTP id 8660E37B43C for ; Sat, 5 May 2001 11:27:10 -0700 (PDT) (envelope-from if@sil.at) Received: from ikarus (ikarus.sil.at [194.152.178.41]) by waste.silverserver.co.at (8.11.2/8.11.2) with ESMTP id f45ILlX06097; Sat, 5 May 2001 20:21:47 +0200 Date: Sat, 5 May 2001 20:32:06 +0200 (MEST) From: Ingo Flaschberger X-Sender: chaoztc@ikarus To: Chris Faulhaber Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: no keyboard In-Reply-To: <20010505133510.A94399@peitho.fxp.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > i'm working at an iap, and we are using freebsd (4.2) boxes as routers. > > normally no keyboard or monitor is attached to the box. > > the problem is, when i connect after the boot a keyboard at the box, it is > > not recognized. at the colocations we often need access to this boxes (not > > remote access). > > is there a solution for this problem? > > > > See atkbd(4)... (remove 'flags 0x1' from the atkbd0 line) i don't have set the flags 0x1 at the kernel config. at the box the keyboard driver is installed at boot time: ---- snip --- atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 --- snap --- but if i connect a keyboard later to the box, it doesn't work. bye, Ingo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 11:40:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (s108.dhcp212-28.cybercable.fr [212.198.28.108]) by hub.freebsd.org (Postfix) with ESMTP id D19A337B423 for ; Sat, 5 May 2001 11:40:27 -0700 (PDT) (envelope-from thierry@herbelot.com) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id UAA53685; Sat, 5 May 2001 20:52:00 +0200 (CEST) (envelope-from thierry@herbelot.com) Message-ID: <3AF44907.D1DC4C89@herbelot.com> Date: Sat, 05 May 2001 20:40:07 +0200 From: Thierry Herbelot X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Chris Faulhaber Cc: Ingo Flaschberger , freebsd-hackers@FreeBSD.ORG Subject: Re: no keyboard References: <20010505133510.A94399@peitho.fxp.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Faulhaber wrote: > > On Sat, May 05, 2001 at 07:36:07PM +0200, Ingo Flaschberger wrote: > > Hi > > > > i'm not sure if that is the right list, but i hope u could help me. > > > > i'm working at an iap, and we are using freebsd (4.2) boxes as routers. > > normally no keyboard or monitor is attached to the box. > > the problem is, when i connect after the boot a keyboard at the box, it is > > not recognized. at the colocations we often need access to this boxes (not > > remote access). > > is there a solution for this problem? Note : this is a way to kill your keyboard : an AT keyboard is not hot-plug compatible two better solutions : - a KVM (keyboard video mouse) switch (for example, from Blackbox) - a serial console (via console="comconsole" in /boot/loader.conf + the right conf in /etc/ttys -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 11:49:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from waste.silverserver.co.at (waste.silverserver.co.at [194.152.178.7]) by hub.freebsd.org (Postfix) with ESMTP id 82BBA37B422 for ; Sat, 5 May 2001 11:49:18 -0700 (PDT) (envelope-from if@sil.at) Received: from ikarus (ikarus.sil.at [194.152.178.41]) by waste.silverserver.co.at (8.11.2/8.11.2) with ESMTP id f45IhxX06647 for ; Sat, 5 May 2001 20:43:59 +0200 Date: Sat, 5 May 2001 20:54:18 +0200 (MEST) From: Ingo Flaschberger X-Sender: chaoztc@ikarus To: freebsd-hackers@FreeBSD.ORG Subject: Re: no keyboard In-Reply-To: <3AF44907.D1DC4C89@herbelot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > the problem is, when i connect after the boot a keyboard at the box, it is > > > not recognized. at the colocations we often need access to this boxes (not > > > remote access). > > > is there a solution for this problem? > > Note : this is a way to kill your keyboard : an AT keyboard is not > hot-plug compatible i have never killed a keyboard with un / plugging. at linux it works. > > two better solutions : > - a KVM (keyboard video mouse) switch (for example, from Blackbox) cannt do that, to much boxes. > - a serial console (via console="comconsole" in /boot/loader.conf + the we already have serial console at the boxes, but u can't use it if u have no laptop with u. the keyboard an the monitor at the locations are always used at other boxes..( bye, Ingo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 11:59: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cloudburst.umist.ac.uk (cloudburst.umist.ac.uk [130.88.119.66]) by hub.freebsd.org (Postfix) with ESMTP id F223337B422 for ; Sat, 5 May 2001 11:58:57 -0700 (PDT) (envelope-from cez@cds220.halls.umist.ac.uk) Received: from cds220.halls.umist.ac.uk ([130.88.161.220]) by cloudburst.umist.ac.uk with esmtp (Exim 3.22 #1) id 14w7Ga-0008KI-00; Sat, 05 May 2001 19:58:56 +0100 Received: (from cez@localhost) by cds220.halls.umist.ac.uk (8.11.3/8.11.2) id f45Ix0U26957; Sat, 5 May 2001 19:59:00 +0100 (BST) (envelope-from cez) Date: Sat, 5 May 2001 19:58:59 +0100 From: Ceri Storey To: Ingo Flaschberger Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: no keyboard Message-ID: <20010505195859.A383@cds220.halls.umist.ac.uk> References: <3AF44907.D1DC4C89@herbelot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from if@sil.at on Sat, May 05, 2001 at 08:54:18PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote: > > Note : this is a way to kill your keyboard : an AT keyboard is not > > hot-plug compatible > > i have never killed a keyboard with un / plugging. > at linux it works. Well, it works, until your keyboard does actually break :) -- Ceri Storey http://pkl.net/~cez/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 12:10:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id DB98437B422 for ; Sat, 5 May 2001 12:10:14 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f45JA8N11887; Sat, 5 May 2001 12:10:08 -0700 (PDT) Date: Sat, 5 May 2001 12:10:08 -0700 From: Alfred Perlstein To: Ceri Storey Cc: Ingo Flaschberger , freebsd-hackers@FreeBSD.ORG Subject: Re: no keyboard Message-ID: <20010505121008.E18676@fw.wintelcom.net> References: <3AF44907.D1DC4C89@herbelot.com> <20010505195859.A383@cds220.halls.umist.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010505195859.A383@cds220.halls.umist.ac.uk>; from c.storey@student.umist.ac.uk on Sat, May 05, 2001 at 07:58:59PM +0100 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Ceri Storey [010505 11:59] wrote: > On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote: > > > Note : this is a way to kill your keyboard : an AT keyboard is not > > > hot-plug compatible > > > > i have never killed a keyboard with un / plugging. > > at linux it works. > Well, it works, until your keyboard does actually break :) It can actually fry the entire motherboard. I doubt linux can prevent that. FreeBSD 4.3 allows hotswap again. -- -Alfred Perlstein - [alfred@freebsd.org] http://www.egr.unlv.edu/~slumos/on-netbsd.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 12:13:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.cs.umn.edu (mail.cs.umn.edu [128.101.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 96F4B37B423 for ; Sat, 5 May 2001 12:13:51 -0700 (PDT) (envelope-from rakshe@cs.umn.edu) Received: from mercury.cs.umn.edu (rakshe@mercury.cs.umn.edu [128.101.34.120]) by mail.cs.umn.edu (8.11.3/8.11.3) with ESMTP id f45JDns07031 for ; Sat, 5 May 2001 14:13:49 -0500 (CDT) Received: from localhost (rakshe@localhost) by mercury.cs.umn.edu (8.9.3/8.9.0) with ESMTP id OAA16648 for ; Sat, 5 May 2001 14:13:24 -0500 (CDT) X-Authentication-Warning: mercury.cs.umn.edu: rakshe owned process doing -bs Date: Sat, 5 May 2001 14:13:24 -0500 (CDT) From: Rohit Rakshe To: Subject: FPU exception, kernel panic In-Reply-To: <20010505195859.A383@cds220.halls.umist.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! I modified some TCP and UDP code in FreeBSD 4.1 and suddenly started getting (almost repeatable) kernel panics. This is how it looks like from remote gdb: (kgdb) bt #0 0xc0192e58 in panic (fmt=0xc035c076 "npxintr from nowhere") at ../../kern/kern_shutdown.c:550 #1 0xc0303c6c in npx_intr (dummy=0x0) at ../../i386/isa/npx.c:721 #2 0xc02e1052 in Xfpu () #3 0xc019824d in softclock () at ../../kern/kern_timeout.c:131 . . . (kgdb) list 126 } else { 127 c->c_flags = 128 (c->c_flags & ~CALLOUT_PENDING); 129 } 130 splx(s); 131 c_func(c_arg); 132 s = splhigh(); 133 steps = 0; 134 c = nextsoftcheck; 135 } . . . (kgdb) #1 0xc0303c6c in npx_intr (dummy=0x0) at ../../i386/isa/npx.c:721 721 panic("npxintr from nowhere"); (kgdb) p npxproc $5 = 0 (kgdb) p npx_exists $6 = 1 '\001' . . . (kgdb) info all-registers eax 0x12 18 ecx 0xc03a60a0 -1069916000 edx 0x400000 4194304 ebx 0xcbc56540 -876255936 esp 0xc0361354 0xc0361354 ebp 0xc0361410 0xc0361410 esi 0x400000 4194304 edi 0x400000 4194304 eip 0xc019824d 0xc019824d eflags 0x346 838 cs 0x8 8 ss 0x10 16 ds 0x400010 4194320 es 0x10 16 fs 0x0 0 gs 0x0 0 (kgdb) info float status 0xc8f5: exceptions: INVALID DIVZ UNDERF LOS FPSTACK; flags: 1000; top 1 control 0x6620: compute to 53 bits; round DOWN; mask: LOS; warning: reserved bits on: 0x6000 last instruction: opcode 0x2825; pc 0x71a4:0x2824c316; operand 0xf800:0x8176640 regno tag msb lsb value %st(7) valid 0000000008179a802825 Denormal (0 as a double) %st(6) valid 71a42824c31600000000 Unnormal (NaN) %st(5) valid 08176640282571a42824 Unnormal (NaN) %st(4) valid c8910818f9380818f800 Unnormal (NaN) %st(3) valid 282571a42824c316bfbf Unnormal (NaN) %st(2) valid e82808176620089c3000 Unnormal (NaN) %st(1) valid 00000032000000010001 Denormal (0 as a double) %st(0) => valid 0000000000240818f800 Denormal (0 as a double) So, this means that there was a FPU exception in kernel, right ? 1. The code which I added in kernel does not use any floats. So I am wondering why this problem should happen at all. 2. pc register in FPU should give address of the instruction which caused this exception, right ? 3. If yes, how do I translate this 48 bit address in a linear address which gdb can understand ? Thanks for help ! - Rohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 12:44:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from chmod.ath.cx (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id 9DA0E37B422 for ; Sat, 5 May 2001 12:44:34 -0700 (PDT) (envelope-from ajh3@chmod.ath.cx) Received: by chmod.ath.cx (Postfix, from userid 1001) id 9E643A876; Sat, 5 May 2001 14:43:34 -0500 (CDT) Date: Sat, 5 May 2001 14:43:34 -0500 From: Andrew Hesford To: Ingo Flaschberger Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: no keyboard Message-ID: <20010505144334.A52167@cec.wustl.edu> References: <3AF44907.D1DC4C89@herbelot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from if@sil.at on Sat, May 05, 2001 at 08:54:18PM +0200 X-Loop: Andrew Hesford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote: > i have never killed a keyboard with un / plugging. > at linux it works. Of course it works with linux. It has nothing to do with the operating system. I hotswap my stuff keyboard and mouse all the time; you just have to remember that there IS a chance you will toast things. -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 13:42:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tango.entreri.com (tango.entreri.com [205.219.158.250]) by hub.freebsd.org (Postfix) with ESMTP id 5C42437B422 for ; Sat, 5 May 2001 13:42:39 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org (Toronto-ppp220788.sympatico.ca [64.228.103.113]) by tango.entreri.com (8.10.2/8.9.1) with ESMTP id f45Kfjx05189; Sat, 5 May 2001 15:41:46 -0500 Message-ID: <3AF46881.67D34B9D@penix.org> Date: Sat, 05 May 2001 16:54:25 -0400 From: Paul Halliday X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Ceri Storey , Ingo Flaschberger , freebsd-hackers@FreeBSD.ORG Subject: Re: no keyboard References: <3AF44907.D1DC4C89@herbelot.com> <20010505195859.A383@cds220.halls.umist.ac.uk> <20010505121008.E18676@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > * Ceri Storey [010505 11:59] wrote: > > On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote: > > > > Note : this is a way to kill your keyboard : an AT keyboard is not > > > > hot-plug compatible > > > > > > i have never killed a keyboard with un / plugging. > > > at linux it works. > > Well, it works, until your keyboard does actually break :) > > It can actually fry the entire motherboard. I doubt linux can > prevent that. > it would blow the inline fuse before it fries the mother board. > FreeBSD 4.3 allows hotswap again. > > -- > -Alfred Perlstein - [alfred@freebsd.org] > http://www.egr.unlv.edu/~slumos/on-netbsd.html > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Paul Halliday. http://dp.penix.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 15:41:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2F96A37B422 for ; Sat, 5 May 2001 15:41:21 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f45MfE413092; Sat, 5 May 2001 15:41:14 -0700 (PDT) Date: Sat, 5 May 2001 15:41:14 -0700 From: Alfred Perlstein To: Paul Halliday Cc: Ceri Storey , Ingo Flaschberger , freebsd-hackers@FreeBSD.ORG Subject: Re: no keyboard Message-ID: <20010505154114.F18676@fw.wintelcom.net> References: <3AF44907.D1DC4C89@herbelot.com> <20010505195859.A383@cds220.halls.umist.ac.uk> <20010505121008.E18676@fw.wintelcom.net> <3AF46881.67D34B9D@penix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AF46881.67D34B9D@penix.org>; from dp@penix.org on Sat, May 05, 2001 at 04:54:25PM -0400 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Paul Halliday [010505 13:41] wrote: > Alfred Perlstein wrote: > > > > * Ceri Storey [010505 11:59] wrote: > > > On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote: > > > > > Note : this is a way to kill your keyboard : an AT keyboard is not > > > > > hot-plug compatible > > > > > > > > i have never killed a keyboard with un / plugging. > > > > at linux it works. > > > Well, it works, until your keyboard does actually break :) > > > > It can actually fry the entire motherboard. I doubt linux can > > prevent that. > > > > it would blow the inline fuse before it fries the mother board. Anything is possible, and I have heard of it happening at least once. One of the other fun things about hot swapping keyboards is that you can actually damage the connector which can cause a short on the motherboard if the poor thing detaches then proceeds to relocate itself across some contacts. -- -Alfred Perlstein - [alfred@freebsd.org] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 16:47:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beastie.saturn-tech.com (beastie.saturn-tech.com [207.229.19.136]) by hub.freebsd.org (Postfix) with ESMTP id 74DE637B42C for ; Sat, 5 May 2001 16:47:37 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by beastie.saturn-tech.com (8.11.1/8.11.0) with ESMTP id f46085U96018 for ; Sat, 5 May 2001 18:08:05 -0600 (MDT) (envelope-from drussell@saturn-tech.com) X-Authentication-Warning: beastie.saturn-tech.com: drussell owned process doing -bs Date: Sat, 5 May 2001 18:08:05 -0600 (MDT) From: Doug Russell To: freebsd-hackers@FreeBSD.ORG Subject: Re: no keyboard In-Reply-To: <20010505121008.E18676@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 May 2001, Alfred Perlstein wrote: > > > i have never killed a keyboard with un / plugging. > > > at linux it works. > > Well, it works, until your keyboard does actually break :) > > It can actually fry the entire motherboard. I doubt linux can > prevent that. > > FreeBSD 4.3 allows hotswap again. Hehe... I've never burned a MB or keyboard in the > 1000 times I've done it, although I've had to reboot a few because the keyboard controller didn't wake up properly. :) I've had dead-ish keyboards that won't allow a machine to boot if plugged in when booting, but work fine if plugged in afterwards. (I've got a nice rackmount Netframe keyboard/trackball that does this. What a pain. I'd like to be able to use that keyboard!) It could be handy sometimes to have a widget to run that would totally re-initialize the keyboard controller. Most often I'd find this handy to re-enable a PS/2 mouse after inadvertantly disconnecting it. I hate to reboot server machines that have been up for hundreds of days because I can't use the KB or mouse. (Not that I often use a KB or mouse on any server machines... but it has happened more than once.) Besides... It's not as bad as hot-swapping ISA cards. When I first got my Microsoft InPort Bus Mouse (with Windows 286) years and years ago, I used to often move it between my BBS machine and my development machine every few minutes when I was building some of the ANSI screens, etc. Occasionally I had to go to DOS and re-enable the mouse driver, but it actually worked because the card was so simple. :) Not recommended. Yes, I am crazy. Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 17: 4:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beastie.saturn-tech.com (beastie.saturn-tech.com [207.229.19.136]) by hub.freebsd.org (Postfix) with ESMTP id CCD9937B422 for ; Sat, 5 May 2001 17:04:26 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by beastie.saturn-tech.com (8.11.1/8.11.0) with ESMTP id f460PKu96071 for ; Sat, 5 May 2001 18:25:25 -0600 (MDT) (envelope-from drussell@saturn-tech.com) X-Authentication-Warning: beastie.saturn-tech.com: drussell owned process doing -bs Date: Sat, 5 May 2001 18:25:20 -0600 (MDT) From: Doug Russell To: freebsd-hackers@FreeBSD.ORG Subject: Re: no keyboard In-Reply-To: <20010505154114.F18676@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 May 2001, Alfred Perlstein wrote: > Anything is possible, and I have heard of it happening at least > once. One of the other fun things about hot swapping keyboards > is that you can actually damage the connector which can cause a > short on the motherboard if the poor thing detaches then proceeds > to relocate itself across some contacts. Ahh yes... Be very careful plugging in those little PS/2 connectors. That's probably the cause of most burned hot-swapped keyboards. :) If you bend the pins by twisting, then get the wrong pin into the +5.... ZZzzzzzap.. Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 17:12:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 8546D37B42C for ; Sat, 5 May 2001 17:12:07 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id 3A4903E0B for ; Sat, 5 May 2001 17:12:07 -0700 (PDT) To: hackers@freebsd.org Subject: Man page for struct ucred/xucred Date: Sat, 05 May 2001 17:12:07 -0700 From: Dima Dorfman Message-Id: <20010506001207.3A4903E0B@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote a rather short manual page about struct ucred, struct xucred, and the routines used to manipulate the former. There really isn't all that much to write about, but I thought it'd be useful to have something that describes the cr* functions even though the code isn't hard to find or particularly difficult to understand. In addition it mentions that struct ucred shouldn't be exported to the userland; it may seem obvious, but implicit traditions are rarely a good thing. While writing this I also noticed that there's no routine to make a struct xucred from a struct ucred. Should there be one? I think so. Perhaps something with an API of void crxucred(struct ucred *cr, struct xucred *xcr); would be useful. Diff against /dev/null for the man page attached. Comments? Suggestions? Thanks, Dima Dorfman dima@unixfreak.org --- /dev/null Sat May 5 16:12:17 2001 +++ ucred.9 Sat May 5 16:49:03 2001 @@ -0,0 +1,108 @@ +.\" +.\" Copyright (c) 2001 Dima Dorfman +.\" All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" $FreeBSD$ +.\" +.Dd May 5, 2001 +.Dt UCRED 9 +.Os +.Sh NAME +.Nm ucred , +.Nm xucred +.Nd structures to describe user credentials in the kernel and userland +.Sh SYNOPSIS +.Fd #include +.Fd #include +.Ft struct ucred * +.Fn crget "void" +.Ft void +.Fn crhold "struct ucred *cr" +.Ft void +.Fn crfree "struct ucred *cr" +.Ft struct ucred * +.Fn crcopy "struct ucred *cr" +.Ft struct ucred * +.Fn crdup "struct ucred *cr" +.Sh DESCRIPTION +The +.Ft ucred +structure describes the user credentials within the kernel. +The +.Ft xucred +structure describes the same user credentials in the userland. +A +.Ft struct ucred +should never be exported to the userland; +instead, it should be converted into a +.Ft struct xucred . +.Pp +The following kernel functions exist to facilitate the maintenance of +user credentials structures within the kernel. +.Pp +.Bl -tag -width crcopy +.It Fn crget +Allocate the memory for and return a zeroed structure. +The reference count is set to 1. +.It Fn crhold +Increment the reference count of +.Fa cr . +.It Fn crfree +Decrement the reference count of +.Fa cr . +If the reference count drops to 0, +the memory for the structure is deallocated. +.It Fn crcopy +Make a copy and subsequently free +.Fa cr . +If the reference count was 1, +this is equivilent to just assigning the address of +.Fa cr +to the new variable. +Otherwise, it is equivilent to calling +.Fn crdup +and +.Fn crfree . +.It Fn crdup +Allocate memory for a new structure and populate its contents with +those from +.Fa cr . +The reference count of the new structure is set to 1. +.El +.Sh NOTES +The +.Dv cr_uid +member of +.Ft struct ucred +should never be inspected directly to determine whether the user +associated with this credentials structure should have superuser +privileges. +Instead, one of the +.Xr suser 9 +functions should be used. +.Sh BUGS +There is no routine to convert a +.Ft struct ucred +into a +.Ft struct xucred . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 17:22:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id A59BD37B424 for ; Sat, 5 May 2001 17:22:31 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f460MNf27541; Sat, 5 May 2001 20:22:27 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sat, 5 May 2001 20:22:22 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Dima Dorfman Cc: hackers@freebsd.org Subject: Re: Man page for struct ucred/xucred In-Reply-To: <20010506001207.3A4903E0B@bazooka.unixfreak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One of the things still under some amount of consideration is the locking and reference counting behavior of the ucred-related code. I have a fairly significant revision of the ucred code in the works, which combines pcred and ucred, as well as cleaning up all the change_*() calls. There are also a number of races in code such as exec(), set*id(), ptrace(), et al, that have substantial races that need to be correct. The pcred->ucred changes are implemented, and build, but I have not booted test boxes yet. Once we have established the desired semantics, we'll probably want to be careful to document their behavior. One thing you should note in the man page is that that function requires that the passed ucred reference be a shared or exclusive reference for the duration of the call. I hope to post the pcred patches to -arch in the near future. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Sat, 5 May 2001, Dima Dorfman wrote: > I wrote a rather short manual page about struct ucred, struct xucred, > and the routines used to manipulate the former. There really isn't > all that much to write about, but I thought it'd be useful to have > something that describes the cr* functions even though the code isn't > hard to find or particularly difficult to understand. In addition it > mentions that struct ucred shouldn't be exported to the userland; it > may seem obvious, but implicit traditions are rarely a good thing. > > While writing this I also noticed that there's no routine to make a > struct xucred from a struct ucred. Should there be one? I think so. > Perhaps something with an API of > > void crxucred(struct ucred *cr, struct xucred *xcr); > > would be useful. > > Diff against /dev/null for the man page attached. Comments? Suggestions? > > Thanks, > > Dima Dorfman > dima@unixfreak.org > > > --- /dev/null Sat May 5 16:12:17 2001 > +++ ucred.9 Sat May 5 16:49:03 2001 > @@ -0,0 +1,108 @@ > +.\" > +.\" Copyright (c) 2001 Dima Dorfman > +.\" All rights reserved. > +.\" > +.\" Redistribution and use in source and binary forms, with or without > +.\" modification, are permitted provided that the following conditions > +.\" are met: > +.\" 1. Redistributions of source code must retain the above copyright > +.\" notice, this list of conditions and the following disclaimer. > +.\" 2. Redistributions in binary form must reproduce the above copyright > +.\" notice, this list of conditions and the following disclaimer in the > +.\" documentation and/or other materials provided with the distribution. > +.\" > +.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND > +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE > +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE > +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE > +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL > +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS > +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) > +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT > +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY > +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF > +.\" SUCH DAMAGE. > +.\" > +.\" $FreeBSD$ > +.\" > +.Dd May 5, 2001 > +.Dt UCRED 9 > +.Os > +.Sh NAME > +.Nm ucred , > +.Nm xucred > +.Nd structures to describe user credentials in the kernel and userland > +.Sh SYNOPSIS > +.Fd #include > +.Fd #include > +.Ft struct ucred * > +.Fn crget "void" > +.Ft void > +.Fn crhold "struct ucred *cr" > +.Ft void > +.Fn crfree "struct ucred *cr" > +.Ft struct ucred * > +.Fn crcopy "struct ucred *cr" > +.Ft struct ucred * > +.Fn crdup "struct ucred *cr" > +.Sh DESCRIPTION > +The > +.Ft ucred > +structure describes the user credentials within the kernel. > +The > +.Ft xucred > +structure describes the same user credentials in the userland. > +A > +.Ft struct ucred > +should never be exported to the userland; > +instead, it should be converted into a > +.Ft struct xucred . > +.Pp > +The following kernel functions exist to facilitate the maintenance of > +user credentials structures within the kernel. > +.Pp > +.Bl -tag -width crcopy > +.It Fn crget > +Allocate the memory for and return a zeroed structure. > +The reference count is set to 1. > +.It Fn crhold > +Increment the reference count of > +.Fa cr . > +.It Fn crfree > +Decrement the reference count of > +.Fa cr . > +If the reference count drops to 0, > +the memory for the structure is deallocated. > +.It Fn crcopy > +Make a copy and subsequently free > +.Fa cr . > +If the reference count was 1, > +this is equivilent to just assigning the address of > +.Fa cr > +to the new variable. > +Otherwise, it is equivilent to calling > +.Fn crdup > +and > +.Fn crfree . > +.It Fn crdup > +Allocate memory for a new structure and populate its contents with > +those from > +.Fa cr . > +The reference count of the new structure is set to 1. > +.El > +.Sh NOTES > +The > +.Dv cr_uid > +member of > +.Ft struct ucred > +should never be inspected directly to determine whether the user > +associated with this credentials structure should have superuser > +privileges. > +Instead, one of the > +.Xr suser 9 > +functions should be used. > +.Sh BUGS > +There is no routine to convert a > +.Ft struct ucred > +into a > +.Ft struct xucred . > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 5 23:24:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 110D337B423 for ; Sat, 5 May 2001 23:24:47 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by falcon.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id XAA19369 for ; Sat, 5 May 2001 23:24:41 -0700 (PDT) Received: (from adsharma@localhost) by sharmas.dhs.org (8.9.3/8.9.3) id XAA12896 for freebsd-hackers@freebsd.org; Sat, 5 May 2001 23:21:03 -0700 Date: Sat, 5 May 2001 23:21:03 -0700 From: Arun Sharma To: freebsd-hackers@freebsd.org Subject: http://www.freebsd.org/send-pr.html Message-ID: <20010505232103.A12889@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doesn't allow me to attach a diff. The attached diff adds that capability to the HTML, but more changes will be needed to the CGI script that handles the form. If someone can point me to the CGI source, I can change that too. -Arun --- send-pr.html.orig Sat May 5 23:11:00 2001 +++ send-pr.html Sat May 5 23:13:33 2001 @@ -93,12 +93,14 @@ Fix to the problem if known:

    + Attachments:
    +
    + + -

    Note: copy/paste will destroy TABs and spacing, and this web - form should not be used to submit code as plain text.

    freebsd-questions@FreeBSD.ORG
    To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message