From owner-freebsd-hackers Sun Jul 2 1:25:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id EA7C437B6F6; Sun, 2 Jul 2000 01:25:32 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA88447; Sun, 2 Jul 2000 10:25:29 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200007020825.KAA88447@freebsd.dk> Subject: Re: UDF (DVD fs) In-Reply-To: <20000701195547.A12762@cokane.yi.org> from Coleman Kane at "Jul 1, 2000 07:55:47 pm" To: cokane@one.net (Coleman Kane) Date: Sun, 2 Jul 2000 10:25:29 +0200 (CEST) Cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] 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 It seems Coleman Kane wrote: > Hello, is anyone currently working on code to implement the UDF > filesystem? For those not familiar with it, it is the filesystem that > DVDs use. I'd like to look into getting the support under FreeBSD, since > the players already seem to work. If no one is working on this, then I > could probably use some help in writing the code to support this fs. I think Julian Elischer is working on UDF.. However to play/read/use DVD's you dont need UDF, they are also readable as an ISO9660, but that might change in the future... -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 Jul 2 2:52:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 2799D37BA87; Sun, 2 Jul 2000 02:52:08 -0700 (PDT) (envelope-from julian@elischer.org) Received: from kairo-42.budapest.interware.hu ([195.70.50.106] helo=jules.elischer.org) by mail.interware.hu with smtp (Exim 3.12 #1 (Debian)) id 138gfS-00063V-00; Sun, 02 Jul 2000 12:08:02 +0200 Message-ID: <395F10BB.2781E494@elischer.org> Date: Sun, 02 Jul 2000 02:51:55 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Coleman Kane Cc: hackers@FreeBSD.org, multimedia@FreeBSD.org Subject: Re: UDF (DVD fs) References: <20000701195547.A12762@cokane.yi.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am working on UDF support. I have at present a program that reads a udf filesystem and am working (today) on making it into an "mtools" like program that allows access to the contents in a useful manner. I will eventually turn this into a (readonly) filesystem, and it is designed with that in mind (it uses a buffer cache etc, like the kernel. (in other words I'm prototyping). I will at some stage also try make a UDF creation module for mkisofs as well. In the meanwhile you should be able to mount most modern DVDs using the ISO9660 filesystem as they should be "bridge" format, (in which there is metadata for both types of filesystems). Julian Coleman Kane wrote: > > Hello, is anyone currently working on code to implement the UDF > filesystem? For those not familiar with it, it is the filesystem that > DVDs use. I'd like to look into getting the support under FreeBSD, since > the players already seem to work. If no one is working on this, then I > could probably use some help in writing the code to support this fs. > > -- > Coleman Kane > President, > UC Free O.S. Users Group - http://pohl.ececs.uc.edu > > --------------------------------------------------------------- > > Part 1.2 Type: application/pgp-signature -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 )_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 2:55:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (beachbum.freebsd.dk [212.242.127.222]) by hub.freebsd.org (Postfix) with ESMTP id E747C37BA87 for ; Sun, 2 Jul 2000 02:55:15 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id LAA01215; Sun, 2 Jul 2000 11:55:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: hackers@FreeBSD.org Subject: Re: Why do we always create a malloc disk for md? In-reply-to: Your message of "Sat, 01 Jul 2000 17:26:07 PDT." <395E8C1F.675AA7D1@bsdi.com> Date: Sun, 02 Jul 2000 11:55:04 +0200 Message-ID: <1213.962531704@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <395E8C1F.675AA7D1@bsdi.com>, John Baldwin writes: >This ends up registering md1 with disk_create, and thus md1 >is returned as a disk through kern.disks into the list returned >by Disk_Names(), and sysinstall blows up when it tries to open >it. I think the reason it blows up is because /dev/md1 isn't >around, although I think I may be able to fix that by adding >'md' as a disk device in the table in sysinstall/devices.c.\ >However, I'm curious if md1 should be created in this case? Your diagnosis is correct. sysinstall should ignore md* disks. The reason md1 is created is that it is the beginning of an "almost-clone" implementation. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Sun Jul 2 2:57:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (beachbum.freebsd.dk [212.242.127.222]) by hub.freebsd.org (Postfix) with ESMTP id C7E5137BC2C; Sun, 2 Jul 2000 02:57:39 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id LAA01299; Sun, 2 Jul 2000 11:57:36 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: hackers@FreeBSD.ORG, KATO Takenori , Mike Smith Subject: Re: invlpg produces strange sig11 on PentiumPro box In-reply-to: Your message of "Sat, 01 Jul 2000 23:47:05 PDT." <200007020647.XAA33812@john.baldwin.cx> Date: Sun, 02 Jul 2000 11:57:36 +0200 Message-ID: <1297.962531856@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007020647.XAA33812@john.baldwin.cx>, John Baldwin writes: >*ahem* You might want to read the first paragraph as well. It is >for situations where one _can't_ update one's BIOS. I don't see why >making it a tweakable kernel compile time know that is off by >default would be so incredibly bad. We have precedents already for >this type of thing. And yes, in this case, the CPU is not performing >as advertised. So far we have set the limit at hardware being used correctly. Either way, this patch was not the correct way to fix this particular erratum. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Sun Jul 2 3: 9:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id DB83937B596; Sun, 2 Jul 2000 03:09:27 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA17928; Sun, 2 Jul 2000 12:09:22 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200007021009.MAA17928@freebsd.dk> Subject: Re: UDF (DVD fs) In-Reply-To: <395F10BB.2781E494@elischer.org> from Julian Elischer at "Jul 2, 2000 02:51:55 am" To: julian@elischer.org (Julian Elischer) Date: Sun, 2 Jul 2000 12:09:21 +0200 (CEST) Cc: cokane@one.net (Coleman Kane), hackers@FreeBSD.org, multimedia@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] 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 It seems Julian Elischer wrote: > I am working on UDF support. > I have at present a program that reads a udf filesystem > and am working (today) on making it into an "mtools" like > program that allows access to the contents in a useful manner. > > I will eventually turn this into a (readonly) filesystem, and it > is designed with that in mind (it uses a buffer cache etc, like > the kernel. (in other words I'm prototyping). > > I will at some stage also try make a UDF creation module for mkisofs > as well. Uhm, the real value of UDF is that it can be used as a "real" rw filesystem on CDRW/DVDRAM media, if this is not implemented the value of having UDF is very limited IMHO.... > In the meanwhile you should be able to mount most modern DVDs using > the ISO9660 filesystem as they should be "bridge" format, (in which > there is metadata for both types of filesystems). Endeed, makeing a ro UDF filesystem more or less useless :) -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 Jul 2 4:40: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 37A6F37BBFD for ; Sun, 2 Jul 2000 04:40:05 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-195-14-233-140.netcologne.de [195.14.233.140]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id NAA05913 for ; Sun, 2 Jul 2000 13:40:03 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.2/8.10.2) with ESMTP id e62Bdhv10418 for ; Sun, 2 Jul 2000 13:39:43 +0200 (CEST) Date: Sun, 2 Jul 2000 13:39:43 +0200 (CEST) From: Paul Herman To: hackers@FreeBSD.ORG Subject: Re: vmstats for pages that go inactive->active 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 Sat, 1 Jul 2000, I wrote: > vmmeter->cnt.v_reactivated counts the number of cache pages that get > promoted to either active or inactive queues. My read (and I could be > wrong) from vm/vm_page.c is, there is no statistic to count the > inactive pages that get "reclaimed" into the active queue. Another idea would be to simply include the number of reclaimed inactive pages into the original cnt.v_reactivated stats, since they are in this sense basically the same as reclaimed cache pages. Thoughts? -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 6: 7:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palnet.com (mail.palnet.com [192.116.19.220]) by hub.freebsd.org (Postfix) with ESMTP id 9820937BC02; Sun, 2 Jul 2000 06:07:48 -0700 (PDT) (envelope-from mustafa@palnet.com) Received: from nawari (dogbert.palnet.com [192.116.17.51]) by mail.palnet.com (8.9.3/8.9.3) with SMTP id QAA38766; Sun, 2 Jul 2000 16:13:40 +0300 (IDT) From: "Mustafa Deeb" To: Cc: , Subject: RE: Invalidating PACK!!! Date: Sun, 2 Jul 2000 16:06:05 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: <20000701130353.F708@inficad.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG what do you mean by ribbon cables, aren't the cables that came with the motherboard good for it? -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Joey Miller Sent: Sat, July 01, 2000 10:04 PM To: Mustafa Deeb Cc: freebsd-hackers@FreeBSD.ORG; freebsd-isp@FreeBSD.ORG Subject: Re: Invalidating PACK!!! had the same problems. make sure you are using LVD ribbon cables. On Sat, Jul 01, 2000 at 11:11:47AM +0200, Mustafa Deeb wrote: // hi all, // // we build our own servers, we've always used the intel N440BX and the // Barracuda disks.. and we liked it so much, // this time we bought intel's L440GX+ and the chettah disks from seagate // (Ultra2 DIsks) // and I'm getting these errors, // ofcourse the server goes nuts when an error like this happens.. // after looking into the mailling lists, nobody gave a direct reason for this // problem or even a solution, anyways, I want to replace the Hard Drives, // // is there someone who've used the L440GX+ motherboard with 18G disks and he // is happy with it // // Best Regards... // Mustafa N. Deeb // // // // da0 at ahc0 bus 0 target 1 lun 0 // da0: Fixed Direct Access SCSI-3 device // da0: 20.000MB/s transfers (10.000MHz, offset 63, 16bit), Tagged Queueing // Enabled // da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) // da2 at ahc0 bus 0 target 4 lun 0 // da2: Fixed Direct Access SCSI-3 device // da2: 20.000MB/s transfers (10.000MHz, offset 63, 16bit), Tagged Queueing // Enabled // da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) // da1 at ahc0 bus 0 target 2 lun 0 // da1: Fixed Direct Access SCSI-3 device // da1: 20.000MB/s transfers (10.000MHz, offset 63, 16bit), Tagged Queueing // Enabled // da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) // // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): SCB 0x62 - timed out while idle, SEQADDR == 0xb // (da2:ahc0:0:4:0): Queuing a BDR SCB // (da2:ahc0:0:4:0): no longer in timeout, status = 34a // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): Invalidating pack // (da2:ahc0:0:4:0): SCB 0xc - timed out while idle, SEQADDR == 0x9 // (da2:ahc0:0:4:0): Queuing a BDR SCB // (da2:ahc0:0:4:0): no longer in timeout, status = 34a // (da2:ahc0:0:4:0): Invalidating pack // // // // To Unsubscribe: send mail to majordomo@FreeBSD.org // with "unsubscribe freebsd-isp" in the body of the message -- Joey Miller Sr. Systems Engineer iBIZ Technology Corp. 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 Sun Jul 2 8:38:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 76AFB37B575; Sun, 2 Jul 2000 08:38:31 -0700 (PDT) (envelope-from julian@elischer.org) Received: from kampala-40.budapest.interware.hu ([195.70.52.232] helo=jules.elischer.org) by mail.interware.hu with smtp (Exim 3.12 #1 (Debian)) id 138m4c-0006GR-00; Sun, 02 Jul 2000 17:54:22 +0200 Message-ID: <395F61E7.2781E494@elischer.org> Date: Sun, 02 Jul 2000 08:38:15 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Soren Schmidt Cc: Coleman Kane , hackers@FreeBSD.org, multimedia@FreeBSD.org Subject: Re: UDF (DVD fs) References: <200007021009.MAA17928@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > > It seems Julian Elischer wrote: > > Indeed, makeing a ro UDF filesystem more or less useless :) I will be adding read/write later.. One must be able to walk before running! As for RO UDF, it is useful for reading UDF2.0.1 cds that don't have ISO9660 on them (I have one here). The experience of looking at how the other vendors do read/write (especially adaptec) in order to be able to read their disks will be used to make it writable. > > -Søren -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 )_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 11: 6:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from astart2.astart.com (astart2.astart.com [206.71.174.194]) by hub.freebsd.org (Postfix) with ESMTP id B59F337BA49; Sun, 2 Jul 2000 11:06:23 -0700 (PDT) (envelope-from papowell@astart.com) Received: from h4.private (papowell@h4.private [10.0.0.4]) by astart2.astart.com (8.9.3/8.9.3) with ESMTP id LAA23386; Sun, 2 Jul 2000 11:08:11 -0700 (PDT) Received: (from papowell@localhost) by h4.private (8.9.3/8.9.3) id LAA04790; Sun, 2 Jul 2000 11:06:01 -0700 (PDT) Date: Sun, 2 Jul 2000 11:06:01 -0700 (PDT) From: papowell@astart.com Message-Id: <200007021806.LAA04790@h4.private> To: doc@freebsd.org, nik@freebsd.org Subject: Re: Documentation selection in sysinstall Cc: ceren@magnesium.net, dgl@bsdi.com, hackers@freebsd.org, jim@cdrom.com, jkh@freebsd.org, murray@bsdi.com, papowell@astart.com, ryan@ryan.net, wpaul@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 2. We need to find a UI model that allows the user to efficiently > select the language and formats they want to install. > > I'm thinking of initially presenting a dialog box that looks > like this: > > ------------------------------------------------------------ > > Documentation is available in the following languages: > > English > Spanish > French > Japanese > Chinese > > ------------------------------------------------------------ > > with the list extending as necessary, based on what sysinstall > found on the FTP site. After the user has chosen a language, then > present them with a list like this: > > ------------------------------------------------------------ > > Now choose the documentation you would like to install, and > the formats you would like to use. > > HTML HTML Text PS PDF PDB RTF > Split > Books > > Handbook [ ] [X] [ ] [ ] [ ] [ ] [ ] > FAQ [X] [X] [ ] [ ] [ ] [ ] [ ] > Porter's Handbook [ ] [ ] [ ] [X] [ ] [ ] [ ] > > [... and so on ...] You actually have a sparsly populated three dimensional array here. Documentation[ material, language, format ] Exmample: Documentation[ Handbook, EN, HTML ] Documentation[ Handbook, EN, HTMLSplit ] Documentation[ Handbook, JA, HTMLSplit ] ... Suggestion: Use a LIST of preferences for language: ja,de,...,en use the first one that you find in order of preference, default is 'en' ... ??? You specify the language preference Preferred language: en[*] ja[1] de[2] (Don't ask me how you do this with the current sysinstall tools!) Suggestion: Select the set of media/format you want HTML Split HTML Text PS PDF PDB RTF [x] [x] [ ] [ ] [ ] [ ] [ ] This is pretty simple to set up and do, and is similar to how a lot of other documentation packages are structured. Only my opinion of course. Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 11:27:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 9B8AA37B53A for ; Sun, 2 Jul 2000 11:27:16 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustident!@homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id MAA02438; Sun, 2 Jul 2000 12:27:06 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <395F8A01.45A128F9@softweyr.com> Date: Sun, 02 Jul 2000 12:29:21 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Jeroen Ruigrok/Asmodai , freebsd-hackers@FreeBSD.ORG Subject: Re: style(9) References: <20000701212818.G26119@daemon.ninth-circle.org> <20000630114924.A78968@mithrandr.moria.org> <395D8FD7.484D9896@softweyr.com> <200007012029.OAA53865@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <20000701212818.G26119@daemon.ninth-circle.org> Jeroen Ruigrok/Asmodai writes: > : Often the 80 column boundary reminds me not to use > : functions_which_have_crazy_long_names_with_underscores(), but be a > : little more brief, but not too. ;) > > IKnowPeopleThatLikeToHaveParagraphFunctionNamesToo(); > DrivesMeNutsBecauseTheirCodeIsHardToReadAndModify(); > TooMuchVerbosityIsSoMuchWorseThanTooLittleAndRepeitionCanBeBadToo(); stop(THE_INSANITY); -- "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 Sun Jul 2 11:37:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6352537BCB2 for ; Sun, 2 Jul 2000 11:37:34 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA01366; Sun, 2 Jul 2000 12:37:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA59581; Sun, 2 Jul 2000 12:37:23 -0600 (MDT) Message-Id: <200007021837.MAA59581@harmony.village.org> To: Wes Peters Subject: Re: style(9) Cc: Jeroen Ruigrok/Asmodai , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 Jul 2000 12:29:21 MDT." <395F8A01.45A128F9@softweyr.com> References: <395F8A01.45A128F9@softweyr.com> <20000701212818.G26119@daemon.ninth-circle.org> <20000630114924.A78968@mithrandr.moria.org> <395D8FD7.484D9896@softweyr.com> <200007012029.OAA53865@harmony.village.org> Date: Sun, 02 Jul 2000 12:37:23 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <395F8A01.45A128F9@softweyr.com> Wes Peters writes: : Warner Losh wrote: : > : > In message <20000701212818.G26119@daemon.ninth-circle.org> Jeroen Ruigrok/Asmodai writes: : > : Often the 80 column boundary reminds me not to use : > : functions_which_have_crazy_long_names_with_underscores(), but be a : > : little more brief, but not too. ;) : > : > IKnowPeopleThatLikeToHaveParagraphFunctionNamesToo(); : > DrivesMeNutsBecauseTheirCodeIsHardToReadAndModify(); : > TooMuchVerbosityIsSoMuchWorseThanTooLittleAndRepeitionCanBeBadToo(); : : stop(THE_INSANITY); SIGILL. Terminated. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 12:30: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from luzern.cs.rice.edu (luzern.cs.rice.edu [128.42.3.67]) by hub.freebsd.org (Postfix) with ESMTP id A119637BE7A for ; Sun, 2 Jul 2000 12:30:02 -0700 (PDT) (envelope-from ssiyer@luzern.cs.rice.edu) Received: (from ssiyer@localhost) by luzern.cs.rice.edu (8.9.3/8.9.3) id OAA24616 for freebsd-hackers@freebsd.org; Sun, 2 Jul 2000 14:30:02 -0500 (CDT) (envelope-from ssiyer) Date: Sun, 2 Jul 2000 14:30:01 -0500 From: Sitaram Iyer To: freebsd-hackers@freebsd.org Subject: name cache size Message-ID: <20000702143001.B24321@cs.rice.edu> Reply-To: Sitaram Iyer Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-url: http://www.cs.rice.edu/~ssiyer/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, for the purposes of an experiment, how can I increase the size of freebsd's name cache? Currently, find -type f on a tree with more than 40,000 files refuses to cache the results, and increasing desiredvnodes and the size of nchashtbl didn't seem to help. (4.0-RELEASE, with maxusers=512). thanks in advance, (should this have gone to -questions instead? wasn't sure..) -- Sitaram Iyer http://www.cs.rice.edu/~ssiyer/ Phone: (off) 713-348-2265 (rice xBANK), (home) 713-799-8980 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 12:44:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.mail.ru (mx6.mail.ru [194.67.23.42]) by hub.freebsd.org (Postfix) with ESMTP id 0001837BE42 for ; Sun, 2 Jul 2000 12:44:42 -0700 (PDT) (envelope-from andersonfox@mail.ru) Received: from dialup-z6.comint.net ([213.154.192.134] helo=mail.ru) by smtp6.mail.ru with esmtp (Exim 3.14 #4) id 138pfc-000JUF-00 for freebsd-hackers@freebsd.org; Sun, 02 Jul 2000 23:44:51 +0400 Message-ID: <395FC6CB.7080400@mail.ru> Date: Sun, 02 Jul 2000 22:48:43 +0000 From: Fox Anderson User-Agent: Mozilla/5.0 (X11; N; Linux 2.2.12 i386; en-US; m14) Netscape6/6.0b1 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers Subject: dev to name Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. How can i find out the name of device file by device major/minor? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 13: 3:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29]) by hub.freebsd.org (Postfix) with ESMTP id 7E86337BBD8 for ; Sun, 2 Jul 2000 13:03:49 -0700 (PDT) (envelope-from chris@holly.calldei.com) Received: from holly.calldei.com ([208.191.149.190]) by mta5.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FX3003OY6DRM5@mta5.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Sun, 2 Jul 2000 15:03:28 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id PAA82918; Sun, 02 Jul 2000 15:01:17 -0500 (CDT envelope-from chris) Date: Sun, 02 Jul 2000 15:01:16 -0500 From: Chris Costello Subject: Re: dev to name In-reply-to: <395FC6CB.7080400@mail.ru> To: Fox Anderson Cc: freebsd-hackers Reply-To: chris@calldei.com Message-id: <20000702150116.E66762@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <395FC6CB.7080400@mail.ru> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, July 02, 2000, Fox Anderson wrote: > Hi. > How can i find out the name of device file by device major/minor? The devtoname() function. ``man devtoname'' -- |Chris Costello |To define recursion, we must first define recursion. `---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 13:50:33 2000 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 3075A37BE52 for ; Sun, 2 Jul 2000 13:50:29 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e62KoQo28811; Sun, 2 Jul 2000 13:50:26 -0700 (PDT) Date: Sun, 2 Jul 2000 13:50:26 -0700 From: Alfred Perlstein To: Sitaram Iyer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: name cache size Message-ID: <20000702135026.P25571@fw.wintelcom.net> References: <20000702143001.B24321@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000702143001.B24321@cs.rice.edu>; from ssiyer@cs.rice.edu on Sun, Jul 02, 2000 at 02:30:01PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Sitaram Iyer [000702 12:32] wrote: > Hi, > > for the purposes of an experiment, how can I increase the size of freebsd's > name cache? Currently, find -type f on a tree with more than 40,000 files > refuses to cache the results, and increasing desiredvnodes and the size of > nchashtbl didn't seem to help. (4.0-RELEASE, with maxusers=512). > > thanks in advance, > > (should this have gone to -questions instead? wasn't sure..) Try this: sysctl -w vfs.vmiodirenable=1 -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 14:15: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from luzern.cs.rice.edu (luzern.cs.rice.edu [128.42.3.67]) by hub.freebsd.org (Postfix) with ESMTP id 8BE0537B559 for ; Sun, 2 Jul 2000 14:15:03 -0700 (PDT) (envelope-from ssiyer@luzern.cs.rice.edu) Received: (from ssiyer@localhost) by luzern.cs.rice.edu (8.9.3/8.9.3) id QAA25138; Sun, 2 Jul 2000 16:14:58 -0500 (CDT) (envelope-from ssiyer) Date: Sun, 2 Jul 2000 16:14:58 -0500 From: Sitaram Iyer To: Alfred Perlstein Cc: freebsd-hackers@freebsd.org Subject: Re: name cache size Message-ID: <20000702161458.A25129@cs.rice.edu> Reply-To: Sitaram Iyer References: <20000702143001.B24321@cs.rice.edu> <20000702135026.P25571@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000702135026.P25571@fw.wintelcom.net>; from bright@wintelcom.net on Sun, Jul 02, 2000 at 01:50:26PM -0700 X-url: http://www.cs.rice.edu/~ssiyer/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus, Alfred Perlstein wrote... > > how can I increase the size of freebsd's name cache? > sysctl -w vfs.vmiodirenable=1 thanks, that worked. -- Sitaram Iyer http://www.cs.rice.edu/~ssiyer/ Phone: (off) 713-348-2265 (rice xBANK), (home) 713-799-8980 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 15: 1: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 96BDE37BD6B for ; Sun, 2 Jul 2000 15:01:05 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id PAA15746 for ; Sun, 2 Jul 2000 15:01:04 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 02 Jul 2000 15:01:04 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: hackers@freebsd.org Subject: GCC extended asm experts please look at this Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I _thought_ I was an expert in gcc's extended asm feature, but I can't figure out why this won't compile when optmization is disabled: =============================================================================== #define xchgl(v, m) ({ \ int __result; \ __asm __volatile ("xchgl %0, %1" \ : "=r"(__result), "=m"(m) \ : "0"(v), "1"(m)); \ (__result); }) void lock80386_acquire(volatile int *lock) { while (xchgl(1, *lock) != 0) while (*lock != 0) ; } =============================================================================== It compiles and works fine with -O or higher; but without -O gcc says: locktest.c: In function `lock80386_acquire': locktest.c:11: inconsistent operand constraints in an `asm' This happens with both gcc-2.95.2 (the version in -current) and with the much older gcc-2.7.2.3. I believe the code is correct according to the documentation in the gcc info pages. I tried changing several things anyway to make it more conservative, but I haven't been able to make it compile without optimization. Can any of you see an error in the code? John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 15: 5:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.houston.rr.com (sm1.texas.rr.com [24.93.35.54]) by hub.freebsd.org (Postfix) with ESMTP id 19B2C37BE9B for ; Sun, 2 Jul 2000 15:05:21 -0700 (PDT) (envelope-from shocking@houston.rr.com) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.357.35); Sun, 2 Jul 2000 17:06:45 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.9.3/8.9.3) with ESMTP id RAA00525 for ; Sun, 2 Jul 2000 17:02:07 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.9.3/8.9.3) with ESMTP id RAA01238 for ; Sun, 2 Jul 2000 17:02:06 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200007022202.RAA01238@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: VPNs and FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Jul 2000 17:02:06 -0500 From: Stephen Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone done this yet? I've just acquired this shiny new cable modem and would like to have secure access to my place of work (even though they're only 10 minutes walk away!) Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 16:38:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from evil.2y.net (ztown2-2-178.adsl.one.net [216.23.15.178]) by hub.freebsd.org (Postfix) with ESMTP id 45BA437B72E; Sun, 2 Jul 2000 16:38:01 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id TAA12363; Sun, 2 Jul 2000 19:43:30 -0400 (EDT) (envelope-from cokane) Date: Sun, 2 Jul 2000 19:43:30 -0400 From: Coleman Kane To: Soren Schmidt Cc: Julian Elischer , Coleman Kane , hackers@FreeBSD.org, multimedia@FreeBSD.org Subject: Re: UDF (DVD fs) Message-ID: <20000702194330.B12336@cokane.yi.org> References: <395F10BB.2781E494@elischer.org> <200007021009.MAA17928@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1i In-Reply-To: <200007021009.MAA17928@freebsd.dk>; from sos@freebsd.dk on Sun, Jul 02, 2000 at 06:09:24AM -0400 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt had the audacity to say: > > Uhm, the real value of UDF is that it can be used as a "real" rw > filesystem on CDRW/DVDRAM media, if this is not implemented the > value of having UDF is very limited IMHO.... > Not necessarily, since the cd9660 backward compatibility is not a requirement of the standard. I have Pulp Fiction here, and it doesn't work, because it has no 9660 compatibility. > > In the meanwhile you should be able to mount most modern DVDs using > > the ISO9660 filesystem as they should be "bridge" format, (in which > > there is metadata for both types of filesystems). > > Endeed, makeing a ro UDF filesystem more or less useless :) > > -Søren > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 17:10:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns3.khmere.com (d83b56af.dsl.flashcom.net [216.59.86.175]) by hub.freebsd.org (Postfix) with ESMTP id 17A1A37B7BF; Sun, 2 Jul 2000 17:10:30 -0700 (PDT) (envelope-from nathan@khmere.com) Received: from khmere.com (ns2.khmere.com [216.59.86.176]) by ns3.khmere.com (8.9.3/8.8.7) with ESMTP id RAA35602; Sun, 2 Jul 2000 17:13:31 -0700 (PDT) Message-ID: <395FD9F1.84B67DE9@khmere.com> Date: Sun, 02 Jul 2000 17:10:26 -0700 From: nathan@khmere.com X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.15 i586) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-net@FreeBSD.ORG" , "hackers@FreeBSD.ORG" Subject: Re: loader ??? Awwww... come on someone must know !!! References: <395D7D2B.48B90842@khmere.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nathan@khmere.com wrote: > I have FreeBSD 4.0-RELEASE (on i386) > > What I am trying to do is nfs root boot from the loader (?) > I do: > > ok> unload kernel > ok> load diskless_kernel > ok> set kernel=diskless_kernel > ok> boot -r -h > > Now what I understand is the -r flag will tell the kernel to overide the > rootdev and use the "staticly linked device" from when you made the > kernel ? > > Now my kernel (the diskless_kernel ) is a diskless kernel ( with BOOTP, > NFS_ROOT .... etc.. ) compiled in. > But when I boot like this is just tries to mount /dev/ad0s1a ... (normal > device ) even though it gets the proper reply from the bootp server that > its rootfs= it even prints : > > rootfs is > Mounting root from ufs:/dev/ad0s1a > > but still mounts the ufs ! > > How do if force it to boot root fs on nfs ? > > I have tried to do a boot -a then when I prompts me for root fs I enter > the proper nfs mount and it is cool ...... but I need it to do it with > out promting... > > I have tried to : > > ok> set rootdev=nfs: > ok> boot -h > ok> can't determine root device > > I have also passed it kernel flags ? (mybe wrong ones ... ? ) > > Now I have looked at the /usr/src/sys/boot/i386/libi386/bootinfo.c and > I see where it checks the roodev to see if it is proper ..... > but I cannot determine what type of device I can name so that this will > not die on me ??? > set rootdev=??? > > how do I have the kernel to load the nfs root instead of use the currdev > ? > > What does etherboot do when it loads the kernel ? does it pass it > special parameters ?? > > If you are wondering why I just don't boot from etherboot ....etc...(I > do ) but... I want to be able to boot my remote systems without a > floppie and chose how to boot from loader (via serail console ...I don't > have serial access for the bios but I can get serial console with > FreeBSD !! ). Either default (use local drive) or load the diskless > kernel , then boot diskless. > This way I almost the same options ..... and maybe automate it... > > Any help would be great !! > > thank you kindly.... > > nathan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" 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 Jul 2 17:22:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 47D7137BED5; Sun, 2 Jul 2000 17:22:50 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id RAA69166; Sun, 2 Jul 2000 17:22:50 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 2 Jul 2000 17:22:49 -0700 (PDT) From: Kris Kennaway To: Stephen Hocking Cc: hackers@freebsd.org Subject: Re: VPNs and FreeBSD In-Reply-To: <200007022202.RAA01238@bloop.craftncomp.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 Sun, 2 Jul 2000, Stephen Hocking wrote: > Has anyone done this yet? I've just acquired this shiny new cable modem and > would like to have secure access to my place of work (even though they're only > 10 minutes walk away!) Well, yeah..ipsec, SSH tunnel, all sorts of SSL-based stuff in ports, SKIP, ... Go for ipsec is my recommendation. See the handbook. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 17:30:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id 8D73F37B800 for ; Sun, 2 Jul 2000 17:30:09 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA79893 for ; Sun, 2 Jul 2000 17:30:09 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <395FDE90.F2F41F35@gorean.org> Date: Sun, 02 Jul 2000 17:30:08 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0629 i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: ls -G seems to depend on TERM=xterm-color Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The new improved ncurses version of the color ls stuff doesn't display for me if I am in a "normal" xterm. If I set TERM equal to xterm-color I'm back in business. Is this expected behavior? If so, a note to that effect in the man page would help reduce user confusion. I'll be happy to submit a patch if needed. If it isn't expected behavior, where could I be going wrong? I don't do anything unusual with termcap. Thanks, Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 17:35:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (peter1.corp.yahoo.com [208.48.107.4]) by hub.freebsd.org (Postfix) with ESMTP id 10F2737C240 for ; Sun, 2 Jul 2000 17:35:31 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 9B6AB1CD7; Sun, 2 Jul 2000 17:35:30 -0700 (PDT) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: John Polstra Cc: hackers@FreeBSD.ORG Subject: Re: GCC extended asm experts please look at this In-Reply-To: Message from John Polstra of "Sun, 02 Jul 2000 15:01:04 PDT." Date: Sun, 02 Jul 2000 17:35:30 -0700 From: Peter Wemm Message-Id: <20000703003530.9B6AB1CD7@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > I _thought_ I was an expert in gcc's extended asm feature, but I > can't figure out why this won't compile when optmization is > disabled: > > ============================================================================= == > #define xchgl(v, m) ({ \ > int __result; \ > __asm __volatile ("xchgl %0, %1" \ > : "=r"(__result), "=m"(m) \ > : "0"(v), "1"(m)); \ > (__result); }) > > void > lock80386_acquire(volatile int *lock) > { > while (xchgl(1, *lock) != 0) > while (*lock != 0) > ; > } > ============================================================================= == > > It compiles and works fine with -O or higher; but without -O gcc > says: > > locktest.c: In function `lock80386_acquire': > locktest.c:11: inconsistent operand constraints in an `asm' > > This happens with both gcc-2.95.2 (the version in -current) and with > the much older gcc-2.7.2.3. > > I believe the code is correct according to the documentation in the > gcc info pages. I tried changing several things anyway to make it > more conservative, but I haven't been able to make it compile > without optimization. If I change it to use a static inline function, it seems to work and will generate identical code (with -O): static inline int xchgl(int v, volatile int *m) { int __result; __asm __volatile ("xchgl %0, %1" : "=r"(__result), "=m"(*m) : "0"(v), "1"(*m)); return __result; } void lock80386_acquire(volatile int *lock) { while (xchgl(1, lock) != 0) while (*lock != 0) ; } It appears to generate valid code without -O, but I am not 100% sure. It is very inefficient without -O. (Beware the different indirection of "m") Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 18: 5:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.lewman.org (lowrider.lewman.org [209.67.240.52]) by hub.freebsd.org (Postfix) with ESMTP id 8B39937BEB3 for ; Sun, 2 Jul 2000 18:05:08 -0700 (PDT) (envelope-from sean@rentul.net) Received: by mail.lewman.org (Postfix, from userid 1004) id 935E13D32; Sun, 2 Jul 2000 21:05:32 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.lewman.org (Postfix) with ESMTP id 8E9F05BC2; Sun, 2 Jul 2000 21:05:32 -0400 (EDT) Date: Sun, 2 Jul 2000 21:05:32 -0400 (EDT) From: Sean Lutner X-Sender: sean@lowrider.lewman.org To: Doug Barton Cc: hackers@freebsd.org Subject: Re: ls -G seems to depend on TERM=xterm-color In-Reply-To: <395FDE90.F2F41F35@gorean.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 experiencing the same thing. ls --color doesn't seem to work for me unless like Doug, I set TERM=xterm-color. On Sun, 2 Jul 2000, Doug Barton wrote: > The new improved ncurses version of the color ls stuff doesn't display > for me if I am in a "normal" xterm. If I set TERM equal to xterm-color > I'm back in business. Is this expected behavior? If so, a note to that > effect in the man page would help reduce user confusion. I'll be happy > to submit a patch if needed. > > If it isn't expected behavior, where could I be going wrong? I don't do > anything unusual with termcap. > > Thanks, > > Doug > -- > "Live free or die" > - State motto of my ancestral homeland, New Hampshire > > Do YOU Yahoo!? > > > 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 Sun Jul 2 18:25:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D941737B5F8 for ; Sun, 2 Jul 2000 18:25:40 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id SAA16367; Sun, 2 Jul 2000 18:25:39 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA32541; Sun, 2 Jul 2000 18:25:39 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sun, 2 Jul 2000 18:25:39 -0700 (PDT) Message-Id: <200007030125.SAA32541@vashon.polstra.com> To: peter@netplex.com.au Subject: Re: GCC extended asm experts please look at this In-Reply-To: <20000703003530.9B6AB1CD7@overcee.netplex.com.au> References: <20000703003530.9B6AB1CD7@overcee.netplex.com.au> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000703003530.9B6AB1CD7@overcee.netplex.com.au>, Peter Wemm wrote: > If I change it to use a static inline function, it seems to work and > will generate identical code (with -O): Thanks! I'll give that a try in both places where I'm having this problem. > It appears to generate valid code without -O, but I am not 100% > sure. It is very inefficient without -O. OK, I'll look at the code closely and try to convince myself that it's correct. I don't care if it's inefficient without optimization. I'm just trying to avoid having to field problem reports from people who for some reason build world without optimization. (This is for the dynamic linker.) Thanks again for the help! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 19: 3:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from enigma.jaded.net (enigma.jaded.net [216.94.132.9]) by hub.freebsd.org (Postfix) with ESMTP id 3F1CC37BF07; Sun, 2 Jul 2000 19:03:50 -0700 (PDT) (envelope-from pjp@dega.daemonium.com) Received: from dega.dn.toronto.on.ca (unknown [216.94.132.9]) by enigma.jaded.net (Postfix) with ESMTP id D5E3F66B02; Mon, 3 Jul 2000 02:03:47 +0000 (GMT) Received: by dega.dn.toronto.on.ca (Postfix, from userid 1000) id BFFF81518; Sun, 2 Jul 2000 22:02:43 -0400 (EDT) Date: Sun, 2 Jul 2000 22:02:43 -0400 From: Peter Philipp To: "Mustafa N. Deeb" Cc: Jeroen Ruigrok/Asmodai , freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Invalidating PACK!!! Message-ID: <20000702220243.B6510@dn.toronto.on.ca> References: <20000701212545.F26119@daemon.ninth-circle.org> <395E5946.527C8759@palnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <395E5946.527C8759@palnet.com>; from mustafa@palnet.com on Sat, Jul 01, 2000 at 10:49:11PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 01, 2000 at 10:49:11PM +0200, Mustafa N. Deeb wrote: > well I think I've eliminated most of these things, I've the disks out of the > server and made the cooler point the air to it.. > and It does not look like bad cables... > about the BAD hd, I've the problem on 5/5 new drives that I bought.. > I'll try upgrading the firmeware and BIOS.. > and see.. Hi, Where I work we have the same problem we were not however able to get rid of this problem by elimination ie. we replaced scsi cable, scsi adapter and like you we replaced the drive (same specs same seagate) twice with the same results. We also added a fan for the drive noticing it became quite hot with no improvement. da1: Fixed Direct Access Last that remains is probly a swap of the motherboard which seems wrong since the motherboard doesn't touch the drives at all ie. there is a controller inbetween. Power supply we thought may cause it too but swapping the power cables to drives this did not seem a problem. We've sticked this drive into another host of almost the same configuration and ran bonnie continuously on it as so that we would put continuous use on the drive with no errors reported. Sincerely, Peter Philipp (PP2441) Daemonic Networks "We will survive our loss and we will remember" - RFC 2468 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 19: 9:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.houston.rr.com (sm1.texas.rr.com [24.93.35.54]) by hub.freebsd.org (Postfix) with ESMTP id 9C99237BF28 for ; Sun, 2 Jul 2000 19:09:27 -0700 (PDT) (envelope-from shocking@houston.rr.com) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.357.35); Sun, 2 Jul 2000 21:10:49 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.9.3/8.9.3) with ESMTP id VAA00782 for ; Sun, 2 Jul 2000 21:06:11 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.9.3/8.9.3) with ESMTP id VAA41837 for ; Sun, 2 Jul 2000 21:06:05 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200007030206.VAA41837@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: Anyone tried StarOffice 5.2 yet? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Jul 2000 21:06:05 -0500 From: Stephen Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hopefully some industrious soul will update the port... Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 19:32:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 8B35D37B638 for ; Sun, 2 Jul 2000 19:32:29 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id TAA08654; Sun, 2 Jul 2000 19:21:20 -0700 (PDT) Message-Id: <200007030221.TAA08654@implode.root.com> To: Bosko Milekic Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf re-write(s), v 0.1 In-reply-to: Your message of "Thu, 29 Jun 2000 12:01:26 EDT." From: David Greenman Reply-To: dg@root.com Date: Sun, 02 Jul 2000 19:21:19 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Thu, 29 Jun 2000, David Greenman wrote: > >> We used to do this in FreeBSD, but found that it was a bad idea for >> performance reasons. Freeing and reallocating memory from the high-level >> VM system is quite expensive and the trend in NICs these days is towards >> needing the code to be even faster, not slower. Further, if the 'peak' is >> reached often, then you're probably not really gaining much by freeing >> the memory back to the common pool. > > What was previously done at some point was use the kernel malloc() to > allocate mbufs. As you know, this is a general purpose allocator that has > to first determine what algorithm to use and then store the object > correctly according to its size. This allocator is faster than that > one. This allocator knows that it only has to deal with mbufs and knows > that all of these mbufs are of the same size. Yes, malloc is slow for other reasons, but it is especially slow when VM pages are freed back to the general pool. Of course it is possible to introduce hysteresis in the algorithm such that it doesn't free the pages as often, but this (and all the tunables that you proposed) has the negative effect of making the allocator more complex. We've tried very hard not to do this in the current mbuf allocator, making it nearly as efficient as you can get. I guess I just don't see the problem on any of the servers that I manage (ftp.cdrom.com and ftp.freesoftware.com, for example). There are peaks in usage, but they tend to reach the peaks often enough that freeing the pages for short term memory gain is just a waste of CPU cycles. Memory is so cheap these days that throwing memory at the problem seems to be a very reasonable solution, especially when the system clearly needs it during the peaks. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 19:50:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 565C637B7CF for ; Sun, 2 Jul 2000 19:50:49 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id UAA49618; Sun, 2 Jul 2000 20:50:45 -0600 (MDT) Date: Sun, 2 Jul 2000 20:50:45 -0600 (MDT) From: Nick Rogness To: Stephen Hocking Cc: hackers@freebsd.org Subject: Re: VPNs and FreeBSD In-Reply-To: <200007022202.RAA01238@bloop.craftncomp.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 Sun, 2 Jul 2000, Stephen Hocking wrote: > Has anyone done this yet? I've just acquired this shiny new cable modem and > would like to have secure access to my place of work (even though they're only > 10 minutes walk away!) I have done just that with nos-tun and Road Runner service. I have not yet implemented the IPSEC feature for security, but the basic tunneling seems to work. Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 20:42:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dastor.albury.net.au (dastor.albury.NET.AU [203.15.244.203]) by hub.freebsd.org (Postfix) with ESMTP id 6FAA637BF27; Sun, 2 Jul 2000 20:42:22 -0700 (PDT) (envelope-from nicks@dastor.albury.net.au) Received: (from nicks@localhost) by dastor.albury.net.au (8.10.2/8.10.2) id e633fxx63555; Mon, 3 Jul 2000 13:41:59 +1000 (EST) Date: Mon, 3 Jul 2000 13:41:59 +1000 From: Nick Slager To: Peter Philipp Cc: "Mustafa N. Deeb" , Jeroen Ruigrok/Asmodai , freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Invalidating PACK!!! Message-ID: <20000703134159.B61604@albury.net.au> References: <20000701212545.F26119@daemon.ninth-circle.org> <395E5946.527C8759@palnet.com> <20000702220243.B6510@dn.toronto.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000702220243.B6510@dn.toronto.on.ca>; from pjp@dn.toronto.on.ca on Sun, Jul 02, 2000 at 10:02:43PM -0400 X-Homer: Whoohooooooo! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Peter Philipp (pjp@dn.toronto.on.ca): > On Sat, Jul 01, 2000 at 10:49:11PM +0200, Mustafa N. Deeb wrote: > > well I think I've eliminated most of these things, I've the disks out of the > > server and made the cooler point the air to it.. > > and It does not look like bad cables... > > about the BAD hd, I've the problem on 5/5 new drives that I bought.. > > I'll try upgrading the firmeware and BIOS.. > > and see.. > > Where I work we have the same problem we were not however able to get rid > of this problem by elimination ie. we replaced scsi cable, scsi adapter > and like you we replaced the drive (same specs same seagate) twice with the > same results. We also added a fan for the drive noticing it became quite hot > with no improvement. Likewise here. We also changed power supply, to no avail. I had this problem with a 2940UW Pro, with Seagate disks - ST318436LW, and ST318275LW. These are 18Gb Baracuda (7200rpm) units. It was suggested I disable write caching, and this seems to have been the problem. Nick. -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 21:19: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from evil.2y.net (ztown2-2-178.adsl.one.net [216.23.15.178]) by hub.freebsd.org (Postfix) with ESMTP id B75DD37B5E6 for ; Sun, 2 Jul 2000 21:18:48 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id AAA00559; Mon, 3 Jul 2000 00:26:07 -0400 (EDT) (envelope-from cokane) Date: Mon, 3 Jul 2000 00:26:07 -0400 From: Coleman Kane To: Stephen Hocking Cc: hackers@freebsd.org Subject: Re: Anyone tried StarOffice 5.2 yet? Message-ID: <20000703002607.A538@cokane.yi.org> References: <200007030206.VAA41837@bloop.craftncomp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200007030206.VAA41837@bloop.craftncomp.com>; from shocking@houston.rr.com on Sun, Jul 02, 2000 at 10:11:27PM -0400 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I d/l'd from Sun and it installed without a hitch. It is a hell of a lot faster than 5.1 and they've gotten rid of some of the crapisms. Stephen Hocking had the audacity to say: > > Hopefully some industrious soul will update the port... > > > Stephen > -- > The views expressed above are not those of PGS Tensor. > > "We've heard that a million monkeys at a million keyboards could produce > the Complete Works of Shakespeare; now, thanks to the Internet, we know > this is not true." Robert Wilensky, University of California > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 21:21:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id A104337B5E6 for ; Sun, 2 Jul 2000 21:21:34 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id LAA77177 for ; Mon, 3 Jul 2000 11:21:26 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Mon, 3 Jul 2000 11:21:26 +0700 (NSS) From: Max Khon To: hackers@freebsd.org Subject: mbstowcs/wcstombs Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-550152396-962598086=:76752" 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-550152396-962598086=:76752 Content-Type: TEXT/PLAIN; charset=US-ASCII hi, there! sorry for posting here but freebsd-i18n list seems to be dead (is it?) some products (e.g. Xerces for C from XML Apache Project) rely on the following behaviour of mbstowcs/wcstombs: when `dest' param is NULL then `len' parameter is ignored and these functions return required length to store the result. This feature is implemented at least in Solaris' libc and glibc 2.1.2. attached patch implements this behaviour (with updated man page and one minor fix in man 3 multibyte). btw is there ongoing effort to merge Citrus libxpg4 to our base tree? freebsd-i18n archives are empty. searching yields nothing except links to Citrus homepage and NetBSD `whatsnew' pages. /fjoe --0-550152396-962598086=:76752 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="mbstowcs.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="mbstowcs.diff" LS0tIGxpYi9saWJjL2xvY2FsZS9hbnNpLmMub3JpZwlNb24gSnVsICAzIDA5 OjU4OjMyIDIwMDANCisrKyBsaWIvbGliYy9sb2NhbGUvYW5zaS5jCU1vbiBK dWwgIDMgMTA6MDU6MjkgMjAwMA0KQEAgLTEwNSwxNSArMTA1LDIxIEBADQog CWNoYXIgY29uc3QgKmU7DQogCWludCBjbnQgPSAwOw0KIA0KLQlpZiAoIXB3 Y3MgfHwgIXMpDQorCWlmICghcykNCiAJCXJldHVybiAoLTEpOw0KIA0KLQl3 aGlsZSAobi0tID4gMCkgew0KLQkJKnB3Y3MgPSBzZ2V0cnVuZShzLCBNQl9M RU5fTUFYLCAmZSk7DQotCQlpZiAoKnB3Y3MgPT0gX0lOVkFMSURfUlVORSkN CisJd2hpbGUgKCFwd2NzIHx8IG4tLSA+IDApIHsNCisJCXdjaGFyX3Qgd2M7 DQorDQorCQl3YyA9IHNnZXRydW5lKHMsIE1CX0xFTl9NQVgsICZlKTsNCisJ CWlmIChwd2NzKQ0KKwkJCSpwd2NzID0gd2M7DQorCQlpZiAod2MgPT0gX0lO VkFMSURfUlVORSkNCiAJCQlyZXR1cm4gKC0xKTsNCi0JCWlmICgqcHdjcysr ID09IDApDQorCQlpZiAod2MgPT0gMCkNCiAJCQlicmVhazsNCisJCWlmIChw d2NzKQ0KKwkJCXB3Y3MrKzsNCiAJCXMgPSBlOw0KIAkJKytjbnQ7DQogCX0N CkBAIC0xMjksMjMgKzEzNSwzMCBAQA0KIAljaGFyICplOw0KIAlpbnQgY250 LCBuYjsNCiANCi0JaWYgKCFwd2NzIHx8ICFzIHx8IG4gPiBJTlRfTUFYKQ0K KwlpZiAoIXB3Y3MgfHwgKHMgJiYgbiA+IElOVF9NQVgpKQ0KIAkJcmV0dXJu ICgtMSk7DQogDQogCW5iID0gbjsNCiAJY250ID0gMDsNCi0Jd2hpbGUgKG5i ID4gMCkgew0KKwl3aGlsZSAoIXMgfHwgbmIgPiAwKSB7DQorCQljaGFyIGNb TUJfTEVOX01BWCArIDFdOw0KKwkJc2l6ZV90IGNfY250Ow0KKw0KIAkJaWYg KCpwd2NzID09IDApIHsNCi0JCQkqcyA9IDA7DQorCQkJaWYgKHMpDQorCQkJ CSpzID0gMDsNCiAJCQlicmVhazsNCiAJCX0NCi0JCWlmICghc3B1dHJ1bmUo KnB3Y3MrKywgcywgbmIsICZlKSkNCisJCWlmICghc3B1dHJ1bmUoKnB3Y3Mr KywgcyA/IHMgOiBjLCBzID8gbmIgOiBNQl9MRU5fTUFYLCAmZSkpDQogCQkJ cmV0dXJuICgtMSk7CQkvKiBlbmNvZGluZyBlcnJvciAqLw0KIAkJaWYgKCFl KQkJCS8qIHRvbyBsb25nICovDQogCQkJcmV0dXJuIChjbnQpOw0KLQkJY250 ICs9IGUgLSBzOw0KLQkJbmIgLT0gZSAtIHM7DQotCQlzID0gZTsNCisJCWNf Y250ID0gcyA/IGUgLSBzIDogZSAtIGM7DQorCQljbnQgKz0gY19jbnQ7DQor CQlpZiAocykgew0KKwkJCW5iIC09IGNfY250Ow0KKwkJCXMgKz0gY19jbnQ7 DQorCQl9DQogCX0NCiAJcmV0dXJuIChjbnQpOw0KIH0NCi0tLSBsaWIvbGli Yy9sb2NhbGUvbXVsdGlieXRlLjMub3JpZwlNb24gSnVsICAzIDEwOjA4OjAw IDIwMDANCisrKyBsaWIvbGliYy9sb2NhbGUvbXVsdGlieXRlLjMJTW9uIEp1 bCAgMyAxMDoyMDo1MCAyMDAwDQpAQCAtNzcsNyArNzcsNyBAQA0KIGFuZCBj b2RlIGVhY2ggYmFzaWMgZWxlbWVudCBhcyBhIHNlcXVlbmNlIG9mIEMNCiAu VmEgY2hhciBOcyBzIC4NCiBJbmRpdmlkdWFsIGJhc2ljIGVsZW1lbnRzIG1h eSBtYXAgaW50byBvbmUgb3IgbW9yZQ0KLS5QcSB1cCB0byBEdiBNQl9DSEFS X01BWA0KKy5QcSB1cCB0byBEdiBNQl9MRU5fTUFYDQogYnl0ZXMgaW4gYSBt dWx0aWJ5dGUgY2hhcmFjdGVyLg0KIC5QcA0KIFRoZSBjdXJyZW50IGxvY2Fs ZQ0KQEAgLTE3Niw2ICsxNzYsMTQgQEANCiAuRmEgbndjaGFycw0KIHdpZGUg Y2hhcmFjdGVycyBhcmUgc3RvcmVkLg0KIEEgdGVybWluYXRpbmcgbnVsbCB3 aWRlIGNoYXJhY3RlciBpcyBhcHBlbmRlZCBpZiB0aGVyZSBpcyByb29tLg0K K0lmDQorLkZhIHdjc3RyaW5nDQoraXMgYSBudWxsIHBvaW50ZXIsDQorLkZu IG1ic3Rvd2NzDQorcmV0dXJucyB0aGUgbGVuZ3RoIHJlcXVpcmVkIHRvIGNv bnZlcnQgdGhlIGVudGlyZSBhcnJheSByZWdhcmRsZXNzDQorb2YgdGhlIHZh bHVlIG9mDQorLkZhIG53Y2hhcnMgLA0KK2J1dCBubyB2YWx1ZXMgYXJlIHN0 b3JlZC4NCiAuUHANCiBUaGUNCiAuRm4gd2NzdG9tYnMNCkBAIC0xODksNiAr MTk3LDE0IEBADQogLkZhIG1ic3RyaW5nIC4NCiBQYXJ0aWFsIG11bHRpYnl0 ZSBjaGFyYWN0ZXJzIGF0IHRoZSBlbmQgb2YgdGhlIHN0cmluZyBhcmUgbm90 IHN0b3JlZC4NCiBUaGUgbXVsdGlieXRlIGNoYXJhY3RlciBzdHJpbmcgaXMg bnVsbCB0ZXJtaW5hdGVkIGlmIHRoZXJlIGlzIHJvb20uDQorSWYNCisuRmEg bWJzdHJpbmcNCitpcyBhIG51bGwgcG9pbnRlciwNCisuRm4gd2NzdG9tYnMN CityZXR1cm5zIHRoZSBsZW5ndGggcmVxdWlyZWQgdG8gY29udmVydCB0aGUg ZW50aXJlIGFycmF5IHJlZ2FyZGxlc3MNCitvZiB0aGUgdmFsdWUgb2YNCisu RmEgbmJ5dGVzICwNCitidXQgbm8gdmFsdWVzIGFyZSBzdG9yZWQuDQogLlNo ICJSRVRVUk4gVkFMVUVTDQogSWYgbXVsdGlieXRlIGNoYXJhY3RlcnMgYXJl IG5vdCBzdXBwb3J0ZWQgaW4gdGhlIGN1cnJlbnQgbG9jYWxlLA0KIGFsbCBv ZiB0aGVzZSBmdW5jdGlvbnMgd2lsbCByZXR1cm4gXC0xIGlmIGNoYXJhY3Rl cnMgY2FuIGJlIHByb2Nlc3NlZCwNCkBAIC0yMTYsMTEgKzIzMiwxNSBAQA0K IC5QcA0KIFRoZQ0KIC5GbiBtYnN0b3djcw0KLWZ1bmN0aW9uIHJldHVybnMg dGhlIG51bWJlciBvZiB3aWRlIGNoYXJhY3RlcnMgY29udmVydGVkLA0KK2Z1 bmN0aW9uIHJldHVybnMgdGhlIG51bWJlciBvZiB3aWRlIGNoYXJhY3RlcnMg Y29udmVydGVkIChvciByZXF1aXJlZCBpZg0KKy5GYSB3Y3N0cmluZw0KK2lz IE5VTEwpLA0KIG5vdCBjb3VudGluZyBhbnkgdGVybWluYXRpbmcgbnVsbCB3 aWRlIGNoYXJhY3Rlci4NCiBUaGUNCiAuRm4gd2NzdG9tYnMNCi1mdW5jdGlv biByZXR1cm5zIHRoZSBudW1iZXIgb2YgYnl0ZXMgY29udmVydGVkLA0KK2Z1 bmN0aW9uIHJldHVybnMgdGhlIG51bWJlciBvZiBieXRlcyBjb252ZXJ0ZWQg KG9yIHJlcXVpcmVkIGlmDQorLkZhIG1ic3RyaW5nDQoraXMgTlVMTCksDQog bm90IGNvdW50aW5nIGFueSB0ZXJtaW5hdGluZyBudWxsIGJ5dGUuDQogSWYg YW55IGludmFsaWQgbXVsdGlieXRlIGNoYXJhY3RlcnMgYXJlIGVuY291bnRl cmVkLA0KIGJvdGggZnVuY3Rpb25zIHJldHVybiBcLTEuDQo= --0-550152396-962598086=:76752-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 22:12:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 2F4D837BF27 for ; Sun, 2 Jul 2000 22:12:06 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id MAA78932 for ; Mon, 3 Jul 2000 12:11:59 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Mon, 3 Jul 2000 12:11:59 +0700 (NSS) From: Max Khon To: hackers@FreeBSD.ORG Subject: Re: mbstowcs/wcstombs 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 hi, there! On Mon, 3 Jul 2000, Max Khon wrote: > sorry for posting here but freebsd-i18n list seems to be dead (is it?) > > some products (e.g. Xerces for C from XML Apache Project) rely on the > following behaviour of mbstowcs/wcstombs: > > when `dest' param is NULL then `len' parameter is ignored and > these functions return required length to store the result. > This feature is implemented at least in Solaris' libc and glibc 2.1.2. > > attached patch implements this behaviour (with updated man page and > one minor fix in man 3 multibyte). aargh, there is already opened PR for this (bin/17694) anyway the question is open /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 22:27:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B53B237B6D2; Sun, 2 Jul 2000 22:27:49 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Mon, 3 Jul 2000 01:27:48 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Sean Lutner Cc: Doug Barton , hackers@freebsd.org Subject: Re: ls -G seems to depend on TERM=xterm-color 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, 2 Jul 2000, Sean Lutner wrote: > I'm experiencing the same thing. ls --color doesn't seem to work for me > unless like Doug, I set TERM=xterm-color. That's because the "color" escape sequences are defined for xterm-color in termcap; xterm-color is defined as a superset of xterm (see the tc= directive). I have a lot of X resources defined, and here is one that could help you guys: XTerm*termName: xterm-color Happy to help :) -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 2 23:55:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bow.net (bow.net [204.216.230.2]) by hub.freebsd.org (Postfix) with ESMTP id 213C037B5B8 for ; Sun, 2 Jul 2000 23:55:45 -0700 (PDT) (envelope-from bow@bow.net) Received: (from bow@localhost) by bow.net (8.9.3/8.9.2) id AAA87805 for freebsd-hackers@freebsd.org; Mon, 3 Jul 2000 00:12:09 -0700 (PDT) Date: Mon, 3 Jul 2000 00:12:09 -0700 From: bow To: freebsd-hackers@freebsd.org Subject: Monitoring modem for dialing Message-ID: <20000703001208.A87793@bow.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I was wondering if someone could point me in the right direction on how to monitor my modem to capture dialing. Basically I have an extra cordless phone around the house, and I wanted to know if it was possible to hook it into my modem and then have an application monitor the modem for dialing, then do something depending on what was dialed... To give an example, I'm running xmms to listen to music. It'd be cool if I could just pick up the cordless phone, and press the #1 key (on the phone) to jump to the next song, or the #2 key to pause. I haven't a clue where to start! :) Is it even possible? Thanks in advance! -bow To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 0:10:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id 79AFC37C02E; Mon, 3 Jul 2000 00:10:15 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id AAA82554; Mon, 3 Jul 2000 00:10:14 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39603C55.507A2829@gorean.org> Date: Mon, 03 Jul 2000 00:10:13 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0629 i386) X-Accept-Language: en MIME-Version: 1.0 To: Brian Fundakowski Feldman Cc: Sean Lutner , hackers@FreeBSD.org Subject: Re: ls -G seems to depend on TERM=xterm-color References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Fundakowski Feldman wrote: > > On Sun, 2 Jul 2000, Sean Lutner wrote: > > > I'm experiencing the same thing. ls --color doesn't seem to work for me > > unless like Doug, I set TERM=xterm-color. > > That's because the "color" escape sequences are defined for xterm-color > in termcap; xterm-color is defined as a superset of xterm (see the tc= > directive). Right... I am down with all that. I just wanted to confirm that the colorized ls depended on the xterm-color setting. > I have a lot of X resources defined, and here is one that > could help you guys: > > XTerm*termName: xterm-color Ok, that's a good solution, I was just using .bashrc. My point is not so much why, but that it be properly documented. Do you want to handle the update of the ls man page, or do you want me to PR a patch? Thanks, Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 0:22:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 5C06437B7D0 for ; Mon, 3 Jul 2000 00:22:32 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FX30040XY2B6P@field.videotron.net> for freebsd-hackers@FreeBSD.ORG; Mon, 3 Jul 2000 02:01:23 -0400 (EDT) Date: Mon, 03 Jul 2000 02:03:27 -0400 (EDT) From: Bosko Milekic Subject: Re: mbuf re-write(s), v 0.1 In-reply-to: <200007030221.TAA08654@implode.root.com> X-Sender: bmilekic@jehovah.technokratis.com To: David Greenman Cc: freebsd-hackers@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 On Sun, 2 Jul 2000, David Greenman wrote: > Yes, malloc is slow for other reasons, but it is especially slow when VM > pages are freed back to the general pool. Of course it is possible to > introduce hysteresis in the algorithm such that it doesn't free the pages as > often, but this (and all the tunables that you proposed) has the negative > effect of making the allocator more complex. We've tried very hard not to do > this in the current mbuf allocator, making it nearly as efficient as you can > get. * Have you looked at the code I proposed? http://24.201.62.9/code/mbuf/ (I did some simplification recently, but it's not done yet, so you may want to look at it). * Again, I did NOT use malloc()/free() to allocate mbufs. Effectively, I do something similar to NetBSD's "pool" interface, only much SIMPLER. * I only proposed ONE additional tunable, and that's the one I mentionned previously. It has the effect of maintaining speed for those who would prefer to have it done in a similar way to before. * I agree with this: - the present allocator is simple - the present allocator is efficient So is the new one, but since it introduces a new useful feature, which has the effect of freeing physical memory when it isn't needed and when the administrator agrees to do so, it's "simple" and "efficient" in its own class. By the way, I'm very open to comments and optimisation suggestions, so if it's not as efficient as possible right now, then I'd love to hear suggestions pertaining to that, but that would maintain the new functionality. > I guess I just don't see the problem on any of the servers that I manage > (ftp.cdrom.com and ftp.freesoftware.com, for example). There are peaks in > usage, but they tend to reach the peaks often enough that freeing the pages > for short term memory gain is just a waste of CPU cycles. Memory is so cheap > these days that throwing memory at the problem seems to be a very reasonable > solution, especially when the system clearly needs it during the peaks. > > -DG > > David Greenman > Co-founder, The FreeBSD Project - http://www.freebsd.org > Manufacturer of high-performance Internet servers - http://www.terasolutions.com > Pave the road of life with opportunities. I'm getting the unfortunate impression that evolution is being frowned upon here. Are their other people that frown the proposal out there to this extent? (i.e. "don't change it if it works") I'd like to hear some important voices on this issue so that I can decide whether to just drop this entire thing and forget about it. (in other words, what do committers and/or core have to say about this?) Aside from this, I've gotten several other "pro" opinions on this; some people have even sent suggestions. So I know that I am not the only one (not by far, in fact) to see an opportunity to benefit from this. Either way, I know *I* will be using this code in time to come, so I suppose the question is: Would you consider committing this code or should I stop posting any changes I make in the future altogether? -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 0:27:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.mail.ru (mx6.mail.ru [194.67.23.42]) by hub.freebsd.org (Postfix) with ESMTP id 3F33C37BFC3 for ; Mon, 3 Jul 2000 00:27:17 -0700 (PDT) (envelope-from _seal@mail.ru) Received: from [193.220.125.2] (helo=gateway) by smtp6.mail.ru with smtp (Exim 3.14 #4) id 1390dd-000Evx-00 for freebsd-hackers@freebsd.org; Mon, 03 Jul 2000 11:27:30 +0400 Message-ID: <011901bfe4c8$1b35b540$140110ac@int.infocomsc.net> From: "nick" <_seal@mail.ru> To: Subject: Drivers Date: Mon, 3 Jul 2000 10:24:20 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks! I was wondering if someone could point me in the right direction on how to write device drivers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 0:29:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 8DE7F37BFF2 for ; Mon, 3 Jul 2000 00:29:47 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id JAA03771; Mon, 3 Jul 2000 09:29:38 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bosko Milekic Cc: David Greenman , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf re-write(s), v 0.1 In-reply-to: Your message of "Mon, 03 Jul 2000 02:03:27 EDT." Date: Mon, 03 Jul 2000 09:29:37 +0200 Message-ID: <3769.962609377@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Bosko Milekic writes: > I'm getting the unfortunate impression that evolution is being > frowned upon here. Are their other people that frown the proposal out > there to this extent? (i.e. "don't change it if it works") I'd like to > hear some important voices on this issue so that I can decide whether to > just drop this entire thing and forget about it. (in other words, what do > committers and/or core have to say about this?) If you can improve it, and show it to be improved, I think it is a good idea. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Mon Jul 3 1:31:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id B3E6137B895 for ; Mon, 3 Jul 2000 01:31:26 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id BAA09516; Mon, 3 Jul 2000 01:20:15 -0700 (PDT) Message-Id: <200007030820.BAA09516@implode.root.com> To: Bosko Milekic Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf re-write(s), v 0.1 In-reply-to: Your message of "Mon, 03 Jul 2000 02:03:27 EDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 03 Jul 2000 01:20:15 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm getting the unfortunate impression that evolution is being > frowned upon here. Are their other people that frown the proposal out > there to this extent? (i.e. "don't change it if it works") I'd like to > hear some important voices on this issue so that I can decide whether to > just drop this entire thing and forget about it. (in other words, what do > committers and/or core have to say about this?) > > Aside from this, I've gotten several other "pro" opinions on this; > some people have even sent suggestions. So I know that I am not the only > one (not by far, in fact) to see an opportunity to benefit from this. > Either way, I know *I* will be using this code in time to come, so I > suppose the question is: > Would you consider committing this code or should I stop posting any > changes I make in the future altogether? What I'm doing is challenging your assertions that spending CPU cycles to save memory in the networking code is the right thing to do. I'm further saying that I have direct experiance in this area since I'm one of the primary people in FreeBSD's history that have spent major amounts of effort in improving its performance, especially in the networking area. We (actually John Dyson and I) made a conscience decision to waste memory in trade for performance and if we (FreeBSD developers in general) decide to go in the opposite direction, then it sure ought to be well thought out and have solid reasoning behind it. In our discussions so far, I haven't yet seen any real numbers to back up the claims. What is needed is: 1) Some numbers that show that the memory wastage is significant - and I'm talking about multiple megabytes at least. If its not 'significant' by that definition (and in my experiance it isn't), than I'd like to hear why you think much smaller numbers are significant. 2) I'd like to see some more numbers that show that the additional CPU wastage is very minimal (say less than 1% of the total amount of time spent doing the allocs/frees). I'm not trying to 'frown upon evolution', unless the particular form of evolution is to make the software worse than it was. I *can* be convinced that your proposed changes are a good thing and I'm asking you to step up to the plate and prove it. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 1:41:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 4BC3E37B91D for ; Mon, 3 Jul 2000 01:41:24 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id KAA04203; Mon, 3 Jul 2000 10:41:17 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: dg@root.com Cc: Bosko Milekic , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf re-write(s), v 0.1 In-reply-to: Your message of "Mon, 03 Jul 2000 01:20:15 PDT." <200007030820.BAA09516@implode.root.com> Date: Mon, 03 Jul 2000 10:41:17 +0200 Message-ID: <4201.962613677@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007030820.BAA09516@implode.root.com>, David Greenman writes: >> I'm getting the unfortunate impression that evolution is being >> frowned upon here. Are their other people that frown the proposal out >> there to this extent? (i.e. "don't change it if it works") I'd like to >> hear some important voices on this issue so that I can decide whether to >> just drop this entire thing and forget about it. (in other words, what do >> committers and/or core have to say about this?) >> >> Aside from this, I've gotten several other "pro" opinions on this; >> some people have even sent suggestions. So I know that I am not the only >> one (not by far, in fact) to see an opportunity to benefit from this. >> Either way, I know *I* will be using this code in time to come, so I >> suppose the question is: >> Would you consider committing this code or should I stop posting any >> changes I make in the future altogether? > > What I'm doing is challenging your assertions that spending CPU cycles to >save memory in the networking code is the right thing to do. I'm further >saying that I have direct experiance in this area since I'm one of the primary >people in FreeBSD's history that have spent major amounts of effort in >improving its performance, especially in the networking area. David, not all FreeBSD systems come with 128MB ram or more. We have a significant market of very small systems where a different policy might make a lot more sense. I agree that real numbers will have to be used to make any decisions however. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Mon Jul 3 1:50:39 2000 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 002CC37B9CC for ; Mon, 3 Jul 2000 01:50:36 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e638oSx14956; Mon, 3 Jul 2000 01:50:28 -0700 (PDT) Date: Mon, 3 Jul 2000 01:50:28 -0700 From: Alfred Perlstein To: David Greenman Cc: Bosko Milekic , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf re-write(s), v 0.1 Message-ID: <20000703015027.U25571@fw.wintelcom.net> References: <200007030820.BAA09516@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007030820.BAA09516@implode.root.com>; from dg@root.com on Mon, Jul 03, 2000 at 01:20:15AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * David Greenman [000703 01:32] wrote: .. response to mbuf rewrite > I'm not trying to 'frown upon evolution', unless the particular form of > evolution is to make the software worse than it was. I *can* be convinced > that your proposed changes are a good thing and I'm asking you to step up > to the plate and prove it. I agree, we can not afford to sacrifice performance for memory footprint any longer, it's just not realistic. If a subsystem needs X amount of memory at some point in time it will need it again. Sacrificing performance to fix the small occurances where this is not the case is not worth it, the general case will always be there and will be more important. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 2:57:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasi.com (sasi.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 8ACC937B5B1 for ; Mon, 3 Jul 2000 02:57:47 -0700 (PDT) (envelope-from pmk@sasi.com) Received: from samar (sasi.com [164.164.56.2]) by sasi.com (8.9.3/8.9.3) with SMTP id PAA00806 for ; Mon, 3 Jul 2000 15:26:48 +0530 (IST) Received: from pcd134.sasi.com ([10.0.16.134]) by sasi.com; Mon, 03 Jul 2000 15:26:45 +0000 (IST) Received: from localhost (pmk@localhost) by pcd134.sasi.com (8.9.3/8.9.3) with ESMTP id PAA00748; Mon, 3 Jul 2000 15:26:38 +0530 X-Authentication-Warning: pcd134.sasi.com: pmk owned process doing -bs Date: Mon, 3 Jul 2000 15:26:38 +0530 (IST) From: Mohana Krishna Penumetcha To: nick <_seal@mail.ru> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Drivers In-Reply-To: <011901bfe4c8$1b35b540$140110ac@int.infocomsc.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 hi, In an ealier mail some one has sent a list of suggested reading for device drivers(none of them are specific to FreeBSD). i found unix device drivers by george pajari very useful. the methodology i followed is to read a chapter from that book and read the FreeBSD sources for simillar devices. it has been very effective so far.after reading this book you only need to know functions specific to BSD. manuals for deivce driver developement under solaris is available at http://soldc.sun.com/developer/support/driver/docs/pubs.html and the same for HP-UX is available at http://www.docs.hp.com/hpux/os/ incase you don't have the above book, you can use any of the above manuals (i used HP doc and it is good) there is an article on CAM SCSI drivers in the june issue of daemon news(www.daemonnews.org). -Regards mohan Telecom R&D , FAC-D, SAS ph:- 5281461 x3078 On Mon, 3 Jul 2000, nick wrote: > Hi folks! > > I was wondering if someone could point me in the right direction on how to > write device drivers. > > > > > > 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 Jul 3 3:14:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id A0ED037B8C0; Mon, 3 Jul 2000 03:14:48 -0700 (PDT) (envelope-from se@freebsd.org) Received: from [194.97.50.135] (helo=mx2.freenet.de) by mout1.freenet.de with esmtp (Exim 3.14 #3) id 1393FW-0000Da-00; Mon, 03 Jul 2000 12:14:46 +0200 Received: from [213.6.102.199] (helo=StefanEsser.FreeBSD.org) by mx2.freenet.de with esmtp (Exim 3.14 #3) id 1393FV-0004IM-00; Mon, 03 Jul 2000 12:14:45 +0200 Received: by StefanEsser.FreeBSD.org (Postfix, from userid 200) id 7DE6FD4B; Mon, 3 Jul 2000 11:40:31 +0200 (CEST) Date: Mon, 3 Jul 2000 11:40:30 +0200 From: Stefan Esser To: Coleman Kane Cc: Stephen Hocking , hackers@FreeBSD.ORG, Stefan Esser Subject: Re: Anyone tried StarOffice 5.2 yet? Message-ID: <20000703114030.A1816@StefanEsser.FreeBSD.org> Reply-To: Stefan Esser Mail-Followup-To: Stefan Esser , Coleman Kane , Stephen Hocking , hackers@FreeBSD.ORG References: <200007030206.VAA41837@bloop.craftncomp.com> <20000703002607.A538@cokane.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000703002607.A538@cokane.yi.org>; from cokane@one.net on Mon, Jul 03, 2000 at 12:26:07AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-07-03 00:26 -0400, Coleman Kane wrote: > I d/l'd from Sun and it installed without a hitch. It is a hell of a lot > faster than 5.1 and they've gotten rid of some of the crapisms. I didn't try to do any actual work with it, but I noticed that while the direct installation works, the "network installation" seems to succeed, but you can't start SO. This doesn't matter, if you are the only user on your box, but it is not acceptable to require 80MB per SO user on a server, IMHO ;-) I did not have time to work out what's failing, but it should be easy to reproduce (start the installer with an option, hmmm, think it was /net, can't check, since I'm away from that system ...) Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 5:20:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from racine.cybercable.fr (racine.cybercable.fr [212.198.0.201]) by hub.freebsd.org (Postfix) with SMTP id 26A8837B517 for ; Mon, 3 Jul 2000 05:20:16 -0700 (PDT) (envelope-from mhenrion@cybercable.fr) Received: (qmail 4426385 invoked from network); 3 Jul 2000 12:20:08 -0000 Received: from r121m199.cybercable.tm.fr (HELO cybercable.fr) ([195.132.121.199]) (envelope-sender ) by racine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 3 Jul 2000 12:20:08 -0000 Message-ID: <396085C0.15FA5203@cybercable.fr> Date: Mon, 03 Jul 2000 14:23:28 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: why isnt there a ext2fs.ko ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, I was wondering why the kernel module for ext2fs doesnt exist. I think this will be very useful because a lot of linux users come to FreeBSD and want to mount their existing linux partitions, and they have to recompile their kernel. This isn't a hard task, but it's a bit disappointing for new users. - Maxime Henrion To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 5:46: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 8445337C0AA; Mon, 3 Jul 2000 05:46:03 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id IAA34027; Mon, 3 Jul 2000 08:46:01 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200007031246.IAA34027@blackhelicopters.org> Subject: Re: Anyone tried StarOffice 5.2 yet? In-Reply-To: <20000703114030.A1816@StefanEsser.FreeBSD.org> from Stefan Esser at "Jul 3, 2000 11:40:30 am" To: se@FreeBSD.ORG Date: Mon, 3 Jul 2000 08:46:01 -0400 (EDT) Cc: cokane@one.net, shocking@houston.rr.com, hackers@FreeBSD.ORG, se@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] 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 did not have time to work out what's failing, but it should be easy > to reproduce (start the installer with an option, hmmm, think it was > /net, can't check, since I'm away from that system ...) Yep. Run the installer as root with the /net option, and put it under, say, /usr/local/office52. Then: exit root cd /usr/local/office52/program run setup as a regular user. No problem. I'm not sure we should even bother with the port. :) ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 6: 5:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.glue.umd.edu (po3.glue.umd.edu [128.8.10.123]) by hub.freebsd.org (Postfix) with ESMTP id 5089E37B9B9 for ; Mon, 3 Jul 2000 06:05:27 -0700 (PDT) (envelope-from howardjp@glue.umd.edu) Received: from y.glue.umd.edu (root@y.glue.umd.edu [128.8.10.68]) by po3.glue.umd.edu (8.10.1/8.10.1) with ESMTP id e63D5MI03451; Mon, 3 Jul 2000 09:05:23 -0400 (EDT) Received: from y.glue.umd.edu (sendmail@localhost [127.0.0.1]) by y.glue.umd.edu (8.9.3/8.9.3) with SMTP id JAA03955; Mon, 3 Jul 2000 09:05:21 -0400 (EDT) Received: from localhost (howardjp@localhost) by y.glue.umd.edu (8.9.3/8.9.3) with ESMTP id JAA03951; Mon, 3 Jul 2000 09:05:21 -0400 (EDT) X-Authentication-Warning: y.glue.umd.edu: howardjp owned process doing -bs Date: Mon, 3 Jul 2000 09:05:21 -0400 (EDT) From: James Howard To: Maxime Henrion Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: why isnt there a ext2fs.ko ? In-Reply-To: <396085C0.15FA5203@cybercable.fr> 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, 3 Jul 2000, Maxime Henrion wrote: > Hi guys, > > I was wondering why the kernel module for ext2fs doesnt exist. I > think this will be very useful because a lot of linux users come to > FreeBSD and want to mount their existing linux partitions, and they have > to recompile their kernel. This isn't a hard task, but it's a bit > disappointing for new users. http://www.freebsd.org/cgi/query-pr.cgi?pr=14217 But it doesn't seem to compile with FreeBSD-current anymore. Give me a day or so and I will update it work with a newer FreeBSD. On this topic, how would anyone feel about importing NetBSD's GPL-clean ext2fs source? Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 6:22: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id A63BE37B606; Mon, 3 Jul 2000 06:21:54 -0700 (PDT) (envelope-from joe@pavilion.net) Received: from genius.systems.pavilion.net (genesis.tao.org.uk [194.242.131.254]) by florence.pavilion.net (8.9.3/8.8.8) with ESMTP id OAA20877; Mon, 3 Jul 2000 14:21:53 +0100 (BST) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 4801312724; Mon, 3 Jul 2000 14:23:23 +0100 (BST) Date: Mon, 3 Jul 2000 14:23:23 +0100 From: Josef Karthauser To: Doug Barton Cc: Brian Fundakowski Feldman , Sean Lutner , hackers@FreeBSD.ORG Subject: Re: ls -G seems to depend on TERM=xterm-color Message-ID: <20000703142323.I29903@pavilion.net> References: <39603C55.507A2829@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <39603C55.507A2829@gorean.org>; from DougB@gorean.org on Mon, Jul 03, 2000 at 12:10:13AM -0700 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 03, 2000 at 12:10:13AM -0700, Doug Barton wrote: > Brian Fundakowski Feldman wrote: > > > That's because the "color" escape sequences are defined for xterm-color > > in termcap; xterm-color is defined as a superset of xterm (see the tc= > > directive). > > Right... I am down with all that. I just wanted to confirm that the > colorized ls depended on the xterm-color setting. More specifically it is dependant upon a terminal definition that defines colour support, there's not check for xterm-color specifically. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 6:50: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from p2.acadia.net (p2.acadia.net [205.217.210.2]) by hub.freebsd.org (Postfix) with ESMTP id 2098537B6C3 for ; Mon, 3 Jul 2000 06:49:58 -0700 (PDT) (envelope-from tbuswell@acadia.net) Received: from smpbox (ip142167012078.acadia.net [142.167.12.78]) by p2.acadia.net (8.9.3/8.9.3) with ESMTP id JAA17971; Mon, 3 Jul 2000 09:53:31 -0400 (EDT) Received: (from tbuswell@localhost) by smpbox (8.9.3/8.9.3) id JAA00615; Mon, 3 Jul 2000 09:54:52 -0400 (EDT) (envelope-from tbuswell) From: Ted Buswell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 3 Jul 2000 09:53:51 -0400 (EDT) To: bow Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Monitoring modem for dialing In-Reply-To: <20000703001208.A87793@bow.net> References: <20000703001208.A87793@bow.net> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14688.39199.48954.847353@smpbox> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bow writes: > Basically I have an extra cordless phone around the house, and I wanted > to know if it was possible to hook it into my modem and then have an > application monitor the modem for dialing, then do something depending > on what was dialed... To give an example, I'm running xmms to listen to > music. It'd be cool if I could just pick up the cordless phone, and press > the #1 key (on the phone) to jump to the next song, or the #2 key to pause. Modems that support voice operations can probably do this. I know that an old "Hayes Accura 33.6 Voice Modem" can. Basically, you put the modem into voice mode and then it will report local hook state events as well as other things like tone detection. It really depends on your modem, however. -Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 7:56:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.52]) by hub.freebsd.org (Postfix) with ESMTP id 33E3137B953 for ; Mon, 3 Jul 2000 07:56:43 -0700 (PDT) (envelope-from whs @xs4all.nl) Received: from localhost (dc2-modem3207.dial.xs4all.nl [194.109.140.135]) by smtp9.xs4all.nl (8.9.3/8.9.3) with SMTP id QAA01573 for ; Mon, 3 Jul 2000 16:56:40 +0200 (CEST) Message-Id: <200007031456.QAA01573@smtp9.xs4all.nl> Date: Mon, 03 Jul 2000 14:36:07 +0000 From: "W.H.Scholten" <"whs "@xs4all.nl> X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.3-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: uncool MO disk problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG L.S. (the following is on fbsd 3.3 R) I tried use 2048 bytes/sector MO media recently, but it doesn't work. Disklabel complains about /boot/boot2 being to large or something. It seems to have worked (more or less) up until 3.1 as I saw a few posts in the SCSI list, e.g. > From: "Kenneth D. Merry" > Date: Thu, 25 Feb 1999 15:54:01 -0700 (MST) replying to Arnaud Kopp who was using it in fbsd 3.1. (not without problems, but at least disklabel/newfs worked). So, what happened after 3.1? Trying to mount an already formatted 640MB msdos format disk gives the following errors and the mount does not succeed: (da0:sym0:0:3:0): READ(10). CDB: 28 0 70 6f 20 6c 0 0 1 0 (da0:sym0:0:3:0): ILLEGAL REQUEST asc:21,0 (da0:sym0:0:3:0): Logical block address out of range (da0:sym0:0:3:0): READ(10). CDB: 28 0 4f 49 0 1 0 0 1 0 (da0:sym0:0:3:0): ILLEGAL REQUEST asc:21,0 (da0:sym0:0:3:0): Logical block address out of range (da0:sym0:0:3:0): READ(10). CDB: 28 0 20 20 53 50 0 0 1 0 (da0:sym0:0:3:0): ILLEGAL REQUEST asc:21,0 (da0:sym0:0:3:0): Logical block address out of range (da0:sym0:0:3:0): READ(10). CDB: 28 0 e9 e 2 7f 0 0 1 0 (da0:sym0:0:3:0): ILLEGAL REQUEST asc:21,0 (da0:sym0:0:3:0): Logical block address out of range (da0:sym0:0:3:0): READ(10). CDB: 28 0 70 6f 20 6c 0 0 1 0 (da0:sym0:0:3:0): ILLEGAL REQUEST asc:21,0 (da0:sym0:0:3:0): Logical block address out of range (da0:sym0:0:3:0): READ(10). CDB: 28 0 4f 49 0 1 0 0 1 0 (da0:sym0:0:3:0): ILLEGAL REQUEST asc:21,0 (da0:sym0:0:3:0): Logical block address out of range (da0:sym0:0:3:0): READ(10). CDB: 28 0 20 20 53 50 0 0 1 0 (da0:sym0:0:3:0): ILLEGAL REQUEST asc:21,0 (da0:sym0:0:3:0): Logical block address out of range (da0:sym0:0:3:0): READ(10). CDB: 28 0 e9 e 2 7f 0 0 1 0 (da0:sym0:0:3:0): ILLEGAL REQUEST asc:21,0 (da0:sym0:0:3:0): Logical block address out of range dscheck: b_bcount 512 is not on a sector boundary (ssize 2048) FYI, when mounting a dos formmatted 230 MB disk I also get 'Logical block address out of range' errors/warnings but the mount succeeds. [btw, why are the od devices still in /dev if they are not to be used? ] This is not all though. With 512 b/s media there are also problems. 1. ext2fs formatted disks: trying to unmount a write protected disk locks up the machine (i.e. I can't do anything under X, machine is not on a network so can't telnet in, nor read console messages if the kernel is in a loop somewhere, and no, I don't feel like trying it on the console at the moment, I tried a few other things and have been rebooting way to much.) A side note: The ext2fs code in FreeBSD is very unstable: 1a) doing a rm -Rf in a large tree has given me regular panic->halt->reboot 's 1b) files in directories with lots of files (like 900-1000) will cause some files to mysteriously disappear (still in the directory listing, but trying to access the file will fail, I rescued the files by copying the entire tree, adding more files to the directory of the ext2 fs, other files were now inaccessible.., so I could copy the missing ones too..) >From a few posts on usenet I gather the much better Open/Net BSD ext2 code won't be imported as noone cares enough. Well, in that case please label the ext2 code in the config file as dangerous (maybe even a message when mounting an ext2fs fs). 2. msdos formatted MO disks. Mounting /unmounting a write protected disk works unless I (yes, just had to try to see what would happen) you write a file to the write protected disk. There's a message saying the disk is write protected and nothing bad happens at that time, but when trying the unmount the device, the OS tries to write the data to disk anyway, fails, (lots of 5's on screen), panic->reboot. 3. ufs disk formatted on obsd: I cannot use da0a but mounting da0 (with -t ufs) works. After I change the disklabel's '16 partitions:' to '8 partitions:' I can mount da0a (and read/write) but unmounting fails (umount -> unkillable process). 4. Formatting ufs on fbsd: newfs hangs (unkillable). Any ideas on what to change ? patches ? (please CC me as I'm not currently on this list). Wouter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 8:51: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id A1D4337B8B2 for ; Mon, 3 Jul 2000 08:50:54 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id E9EAC6D; Mon, 3 Jul 2000 11:50:51 -0400 (AST) Message-ID: <3960B65B.30DF5DC1@vangelderen.org> Date: Mon, 03 Jul 2000 11:50:51 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: David Greenman , Bosko Milekic , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf re-write(s), v 0.1 References: <200007030820.BAA09516@implode.root.com> <20000703015027.U25571@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: > > * David Greenman [000703 01:32] wrote: > > .. response to mbuf rewrite > > > I'm not trying to 'frown upon evolution', unless the particular form of > > evolution is to make the software worse than it was. I *can* be convinced > > that your proposed changes are a good thing and I'm asking you to step up > > to the plate and prove it. > > I agree, we can not afford to sacrifice performance for memory > footprint any longer, Nobody talks about *sacrificing* performance here if I'm interpreting Bosko's mail correctly. > it's just not realistic. If a subsystem > needs X amount of memory at some point in time it will need it > again. Uh? If the peak is reached only ever so often I'd rather see the memory reclaimed so that it can be used for something else. (If it doesn't affect performance too much that is.) In fact, the whole design of the FreeBSD VM system responds dynamically to the load imposed thereby rendering you claim invalid for at least one subsystems. > Sacrificing performance to fix the small occurances where > this is not the case is not worth it, the general case will always > be there and will be more important. You seem to imply that you have proof that Bosko's patches will negatively affect the general case I assume? Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 9:38: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.49]) by hub.freebsd.org (Postfix) with ESMTP id 8539137B9C5 for ; Mon, 3 Jul 2000 09:38:04 -0700 (PDT) (envelope-from whs@xs4all.nl) Received: from localhost (dc2-modem1387.dial.xs4all.nl [194.109.133.107]) by smtp3.xs4all.nl (8.9.3/8.9.3) with SMTP id SAA22063 for ; Mon, 3 Jul 2000 18:38:01 +0200 (CEST) Message-ID: <3960C18E.41C67EA6@xs4all.nl> Date: Mon, 03 Jul 2000 16:38:38 +0000 From: "W.H.Scholten" X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.3-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: uncool MO disk problems, addendum References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG L.s. small addendum: - it's fbsd 3.3R on i386 as you may have guesssed from the mail headers. - I use the new fbsd symbios/ncr scsi driver (the README says latest revision is sym-0.12.0-19991127). Also my mail address is whs@xs4all.nl, reply on the previous mail will give spaces in the mail address.. Wouter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 9:42:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id 773F537BDF6 for ; Mon, 3 Jul 2000 09:42:17 -0700 (PDT) (envelope-from sam@antinea.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id 6764C191CF; Mon, 3 Jul 2000 18:42:15 +0200 (CEST) Received: by antinea.enst.fr (Postfix, from userid 1000) id 07CBE344; Mon, 3 Jul 2000 18:42:13 +0200 (CEST) To: hackers@freebsd.org Subject: IPsec tunnels with dynamic addresses Mime-Version: 1.0 (generated by tm-edit 1.5) Content-Type: text/plain; charset=US-ASCII Date: 03 Jul 2000 18:42:12 +0200 Lines: 25 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Capitol Reef" From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-07-03-18-42-13+trackit+sam@antinea.enst.fr> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The current situation: I have some machines with static IP addresses, and some other ones with dynamic IP addresses, permanently connected or not. What I would like: establish IPsec tunnels between a machine with a static IP and a machine with a dynamic one. The former solution I used: pipsecd, written by Pierre Beyssac, allows you to configure IPsec tunnels without having an IPsec stack in your kernel. These tunnels can have dynamic addresses: when an IPsec packet enters the machine with a static IP and has the right signature, this changes the tunnel dynamic end to be the machine that sent the packet. That means that sending a single packet from a new IP address was enough to reconfigure the whole tunnel. Is that doable with the current IPsec kernel implementation? Can we dynamically change security policies so that a new tunnel is created when some a packet with the right SPI is received? How can one intercept IPsec packet, since they are not tagged IPsec anymore when they arrive in userland? Sam -- Samuel Tardieu -- sam@inf.enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 9:43:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from evil.2y.net (ztown2-2-178.adsl.one.net [216.23.15.178]) by hub.freebsd.org (Postfix) with ESMTP id 5E00537B9D5; Mon, 3 Jul 2000 09:43:26 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id MAA58225; Mon, 3 Jul 2000 12:50:08 -0400 (EDT) (envelope-from cokane) Date: Mon, 3 Jul 2000 12:50:08 -0400 From: Coleman Kane To: Michael Lucas Cc: se@FreeBSD.ORG, cokane@one.net, shocking@houston.rr.com, hackers@FreeBSD.ORG Subject: Re: Anyone tried StarOffice 5.2 yet? Message-ID: <20000703125008.A58195@cokane.yi.org> References: <20000703114030.A1816@StefanEsser.FreeBSD.org> <200007031246.IAA34027@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200007031246.IAA34027@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Mon, Jul 03, 2000 at 08:46:04AM -0400 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Naw, man. Ports are necessary. Michael Lucas had the audacity to say: > > I did not have time to work out what's failing, but it should be easy > > to reproduce (start the installer with an option, hmmm, think it was > > /net, can't check, since I'm away from that system ...) > > Yep. Run the installer as root with the /net option, and put it > under, say, /usr/local/office52. > > Then: > > exit root > > cd /usr/local/office52/program > > run setup as a regular user. > > No problem. > > I'm not sure we should even bother with the port. :) > > ==ml > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 9:49:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.houston.rr.com (sm2.texas.rr.com [24.93.35.55]) by hub.freebsd.org (Postfix) with ESMTP id D400637B9C8 for ; Mon, 3 Jul 2000 09:49:55 -0700 (PDT) (envelope-from shocking@houston.rr.com) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.357.35); Mon, 3 Jul 2000 11:49:31 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.9.3/8.9.3) with ESMTP id LAA17011; Mon, 3 Jul 2000 11:46:41 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.9.3/8.9.3) with ESMTP id LAA00639; Mon, 3 Jul 2000 11:46:39 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200007031646.LAA00639@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Coleman Kane Cc: hackers@FreeBSD.ORG Subject: Re: Anyone tried StarOffice 5.2 yet? In-Reply-To: Your message of "Mon, 03 Jul 2000 12:50:08 EDT." <20000703125008.A58195@cokane.yi.org> Reply-To: shocking@houston.rr.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Jul 2000 11:46:39 -0500 From: Stephen Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just tried it - seems to work fine, although the soffice script needs one small mod to take account of the fact that test is /bin/test. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 9:54:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id 40C6E37B98C; Mon, 3 Jul 2000 09:54:09 -0700 (PDT) (envelope-from so@server.i-clue.de) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id UAA29485; Mon, 3 Jul 2000 20:56:56 +0200 Message-ID: <3960C542.9A6890D2@i-clue.de> Date: Mon, 03 Jul 2000 18:54:26 +0200 From: Christoph Sold Reply-To: so@server.i-clue.de Organization: i-clue interactive GmbH X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Michael Lucas Cc: se@FreeBSD.ORG, cokane@one.net, shocking@houston.rr.com, hackers@FreeBSD.ORG Subject: Re: Anyone tried StarOffice 5.2 yet? References: <200007031246.IAA34027@blackhelicopters.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Lucas wrote: > > > I did not have time to work out what's failing, but it should be easy > > to reproduce (start the installer with an option, hmmm, think it was > > /net, can't check, since I'm away from that system ...) > > Yep. Run the installer as root with the /net option, and put it > under, say, /usr/local/office52. > > Then: > > exit root > > cd /usr/local/office52/program > > run setup as a regular user. > > No problem. > > I'm not sure we should even bother with the port. :) Just so the doc people can say "cd /usr/ports/whatever; make all install clean; and you're set up." Remember: It's easy to teach rules, but its difficult to teach exceptions. Just my $.05 -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 10: 6:50 2000 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 B08A437B9DC for ; Mon, 3 Jul 2000 10:06:47 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e63H6b125162; Mon, 3 Jul 2000 10:06:37 -0700 (PDT) Date: Mon, 3 Jul 2000 10:06:37 -0700 From: Alfred Perlstein To: "Jeroen C. van Gelderen" Cc: David Greenman , Bosko Milekic , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf re-write(s), v 0.1 Message-ID: <20000703100636.V25571@fw.wintelcom.net> References: <200007030820.BAA09516@implode.root.com> <20000703015027.U25571@fw.wintelcom.net> <3960B65B.30DF5DC1@vangelderen.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3960B65B.30DF5DC1@vangelderen.org>; from jeroen@vangelderen.org on Mon, Jul 03, 2000 at 11:50:51AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jeroen C. van Gelderen [000703 08:52] wrote: > Alfred Perlstein wrote: > > > Sacrificing performance to fix the small occurances where > > this is not the case is not worth it, the general case will always > > be there and will be more important. > > You seem to imply that you have proof that Bosko's patches > will negatively affect the general case I assume? No I don't, I have a lot of faith in Bosko's work but I wanted to make it clear that performance is several orders of magnitude more important than being able to reclaim memory. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 10: 7: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 19E9437B9DC for ; Mon, 3 Jul 2000 10:06:53 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id TAA20236 for hackers@freebsd.org; Mon, 3 Jul 2000 19:06:48 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 9B2FF885B; Mon, 3 Jul 2000 07:38:17 +0200 (CEST) Date: Mon, 3 Jul 2000 07:38:17 +0200 From: Ollivier Robert To: hackers@freebsd.org Subject: Re: Anyone tried StarOffice 5.2 yet? Message-ID: <20000703073817.A77567@keltia.freenix.fr> Mail-Followup-To: hackers@freebsd.org References: <200007030206.VAA41837@bloop.craftncomp.com> <20000703002607.A538@cokane.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000703002607.A538@cokane.yi.org>; from cokane@one.net on Mon, Jul 03, 2000 at 12:26:07AM -0400 X-Operating-System: FreeBSD 5.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Coleman Kane: > I d/l'd from Sun and it installed without a hitch. It is a hell of a lot > faster than 5.1 and they've gotten rid of some of the crapisms. On 5.0-CURRENT or 4-STABLE ? With which linux_lib port ? I tried on my 5.0-CURRENT with the latest linux_lib (from RedHate 6.1) and the setup dies before the end, leaving with a non runnable SO :-( -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 11:22:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web4006.mail.yahoo.com (web4006.mail.yahoo.com [216.115.104.40]) by hub.freebsd.org (Postfix) with SMTP id 431ED37B717 for ; Mon, 3 Jul 2000 11:22:14 -0700 (PDT) (envelope-from dindin2k@yahoo.com) Message-ID: <20000703182212.15750.qmail@web4006.mail.yahoo.com> Received: from [144.60.85.200] by web4006.mail.yahoo.com; Mon, 03 Jul 2000 11:22:12 PDT Date: Mon, 3 Jul 2000 11:22:12 -0700 (PDT) From: Dinesh Nadarajah Subject: Keyboard programming - help! To: 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 Hi: I am new to freeBSD and I would like to get some advice/recommendation regarding keyboard programming. I am trying to port FREEBSD to one of the Indian languages (and could possiblely be used for many of them) and so I would like to find out how to program the keyboard to accept key sequences for that. Here is my problem: The output keycode will not only depend the current key input, but also on th previous one. e.g. if the input sequence is ABCD - then the output sequence may be RGW ( meaning erase the previous code). How can I accomplish this so that all applications (mostly X based ones) can use such a scheme. I was thinking of writing a middle ware application that can be started and stopped at will. Anytime this application runs, it should intercept all keyboard codes, process them and then retransmit it so that what ever application can use it. The program will be able to switch between standard keyboard and also the special keyboard. BTW: This problem is not unique. I have been in contact will several embedded systems manufacturers who also want such implementation for control systems processing. ANy help/advice/opinion/direction/recommendation on this matter will be greatly appreciated. Thanks in advance. -Dinesh __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 11:32:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 3F60737B532 for ; Mon, 3 Jul 2000 11:32:34 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FX4009M6U9XEC@falla.videotron.net> for freebsd-hackers@FreeBSD.ORG; Mon, 3 Jul 2000 13:37:10 -0400 (EDT) Date: Mon, 03 Jul 2000 13:39:13 -0400 (EDT) From: Bosko Milekic Subject: Re: mbuf re-write(s), v 0.1 In-reply-to: <200007030820.BAA09516@implode.root.com> X-Sender: bmilekic@jehovah.technokratis.com To: David Greenman Cc: freebsd-hackers@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 On Mon, 3 Jul 2000, David Greenman wrote: > What I'm doing is challenging your assertions that spending CPU cycles to > save memory in the networking code is the right thing to do. I'm further > saying that I have direct experiance in this area since I'm one of the primary > people in FreeBSD's history that have spent major amounts of effort in > improving its performance, especially in the networking area. We (actually > John Dyson and I) made a conscience decision to waste memory in trade for > performance and if we (FreeBSD developers in general) decide to go in the > opposite direction, then it sure ought to be well thought out and have solid > reasoning behind it. In our discussions so far, I haven't yet seen any real > numbers to back up the claims. What is needed is: > 1) Some numbers that show > that the memory wastage is significant - and I'm talking about multiple > megabytes at least. If its not 'significant' by that definition (and in my > experiance it isn't), than I'd like to hear why you think much smaller numbers > are significant. When I posted the initial diff, I provided such data. I'll repeat: a good example is at: http://24.201.62.9/stats/mbuf.html - specifically, look at the last graph at the bottom. What happened in Weeks 20 and 22 was the result of (simulated) very high web server and NFS activity, combined with a temporary DoS attack that occurred at the same time. On a machine with activity such as that depicted in these statistics, I would set min_on_avail to about 360. This way, the system will allocate at least 360 mbufs from the map and will not free pages back to the map once it hits 360 mbufs on the free lists. Note that during Week 22, the system had allocated around 5.5k mbufs, thus a total of 1408000 bytes (~1.4M). If "normal" activity for this system is ~360 mbufs (it's actually a little less than that), then we're looking at 92160 bytes. 1408000-92160 = 1315840 (~1.3M) of wasted memory, which is around 322 _wired_ pages on my machine. On a machine such as one that is one of my NFS and Samba servers, all that is available are 8M of RAM, and this would leave me with only ~7M to work with. But regardless of the amount of RAM the machine in question has, note that in this case the system is actually _WASTING_ ~1427.78% the memory that it normally would use during "regular high" activity. That's the way I look at it, and obviously -- I agree with you -- if you consider that memory is cheap and that because of that, you are prepared to literally throw some of it away, then why should you even be considering these propositions? Well, if you're looking at designing a system that will scale and give back when it no longer requires, and who's behavior in doing so can be adjusted at runtime, then the present allocator just doesn't suffice. > 2) I'd like to see some more numbers that show that the > additional CPU wastage is very minimal (say less than 1% of the total amount > of time spent doing the allocs/frees). As I also previously mentionned, I had some trouble getting profiling to work for me here (and in fact, I'm still having trouble). I can build a profiling kernel, but it simply won't boot (the system becomes unresponsive when the "/" appears at boot) [this is on -CURRENT] Although I have to post some updated diffs, MGET(), with the modifications, results in the following: * Check if free list is empty, if not (which is usually the case if you adjust min_on_avail properly and have allowed the server to stabilize itself -- e.g. allocate at least min_on_avail from the map), then it will setup a pointer to the new mb_map page descriptor structure at the top of the list and extract the pointer to the chain of free mbufs. It will remove the first mbuf on the chain, while making sure that the others are re-attached properly (this part is essentially what was done with the mmbfree pointer manipulation when removing an mbuf from the chain). Finally, before completing the allocation, it will simply check whether the page descriptor structure entry from which it allocated has now reached zero mbufs, and if it's the case, it will just move that entry to the "empty" list. So the extra CPU cycles are spent in dealing with the two lists that the system must now manage to ensure that it can easily keep track of what mbufs belong to what allocated page, so that it knows when it's time to free the given page -- if necessary. As you know, MGETHDR() is similar. As for MFREE(), here's what it does following the suggested proposition: * If there is external storage, free it (same as always). Place successor into second provided mbuf (same as always). There is a new field in the m_hdr struct in mbufs (pointer) that points to the mbuf's corresponding page descriptor structure, so that pointer is aquired and the free mbuf chain is extracted from the structure to which the freed mbuf is attached (as it always was). I guess the only real addition in CPU cycles here is the following: a simple check was added that just checks if the entry is on the "empty" list and if it is, moves it over to the "free list." If that's not the case, then there is a possibility that the freed mbuf completes a page and the page can be freed, so if that's the case and min_on_avail allows it, then the page is freed back to the map (notice that this behavior is tunable - again - with min_on_avail). > I'm not trying to 'frown upon evolution', unless the particular form of > evolution is to make the software worse than it was. I *can* be convinced > that your proposed changes are a good thing and I'm asking you to step up > to the plate and prove it. That sounds fair. > > -DG > > David Greenman > Co-founder, The FreeBSD Project - http://www.freebsd.org > Manufacturer of high-performance Internet servers - http://www.terasolutions.com > Pave the road of life with opportunities. -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 11:37: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uffdaonline.net (host39.uffdaonline.net [207.109.235.39]) by hub.freebsd.org (Postfix) with ESMTP id 790E337C1AD for ; Mon, 3 Jul 2000 11:37:01 -0700 (PDT) (envelope-from zach@uffdaonline.net) Received: by uffdaonline.net (Postfix, from userid 1000) id D2DA120C9; Mon, 3 Jul 2000 18:38:43 +0000 (GMT) Date: Mon, 3 Jul 2000 13:38:43 -0500 From: "Zach N. Heilig" To: bow Cc: freebsd-hackers@freebsd.org Subject: Re: Monitoring modem for dialing Message-ID: <20000703133843.A27356@murkwood.znh.org> References: <27488F1A121B7A251F29D47B@mail.uffdaonline.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <27488F1A121B7A251F29D47B@mail.uffdaonline.net>; from bow@bow.net on Mon, Jul 03, 2000 at 12:12:09AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 03, 2000 at 12:12:09AM -0700, bow wrote: > Hello, > > I was wondering if someone could point me in the right direction on how > to monitor my modem to capture dialing. > > Basically I have an extra cordless phone around the house, and I wanted > to know if it was possible to hook it into my modem and then have an > application monitor the modem for dialing, then do something depending > on what was dialed... To give an example, I'm running xmms to listen to > music. It'd be cool if I could just pick up the cordless phone, and press > the #1 key (on the phone) to jump to the next song, or the #2 key to pause. > > I haven't a clue where to start! :) > > Is it even possible? Just don't connect this to the phone line if you do this... I would recomend using one of those IR internet remotes that connect to the serial port. It'd be much cheaper (you should be able to pick one up for under US$20). The only problem might be writing a bit of code to make it work. For mine, I just observed the output of the serial port for each of the buttons and wrote the code around that. -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 11:52: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 8615F37C1BD for ; Mon, 3 Jul 2000 11:51:55 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA07943; Mon, 3 Jul 2000 20:51:35 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bosko Milekic Cc: David Greenman , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf re-write(s), v 0.1 In-reply-to: Your message of "Mon, 03 Jul 2000 13:39:13 EDT." Date: Mon, 03 Jul 2000 20:51:35 +0200 Message-ID: <7941.962650295@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , B osko Milekic writes: > When I posted the initial diff, I provided such data. I'll repeat: a > good example is at: http://24.201.62.9/stats/mbuf.html Considering the prominence of DoS attacks and similar, I think it makes a lot of sense to be able to free the memory again, and if the hysteresis you have built in means that there is no measurable performance impact I think you will face no objections. Is it possible to auto-tune min_on_avail somehow ? What if instead you made it free only when more than 50% of the memory allocated from the map was unused ? Could that freeing be done by a timeout routine which runs every N seconds ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Mon Jul 3 12:25:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sn1oexchr01.nextvenue.com (sn1oexchr01.nextvenue.com [63.209.169.9]) by hub.freebsd.org (Postfix) with SMTP id 1864237BD33 for ; Mon, 3 Jul 2000 12:25:11 -0700 (PDT) (envelope-from nevans@nextvenue.com) Received: FROM sn1exchmbx.nextvenue.com BY sn1oexchr01.nextvenue.com ; Mon Jul 03 15:23:27 2000 -0400 Received: by SN1EXCHMBX with Internet Mail Service (5.5.2650.21) id ; Mon, 3 Jul 2000 15:23:21 -0400 Message-ID: <712384017032D411AD7B0001023D799B07C92C@SN1EXCHMBX> From: Nick Evans To: "'freebsd-hackers@freebsd.org'" Subject: BPF and Promiscuous Mode Date: Mon, 3 Jul 2000 15:23:16 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFE524.236D6B20" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFE524.236D6B20 Content-Type: text/plain; charset="iso-8859-1" How do I set an interface in promiscous mode permanently? In Linux it's simply ifconfig PROMISC. Is there something similar in BSD? Is it somekind of sysctl command? thx. ------------------------------------------ nick.evans network.engineering NextVenue, Inc. phone: (212) 909.2988 pager: (888) 642.5541 ------_=_NextPart_001_01BFE524.236D6B20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable BPF and Promiscuous Mode

How do I set an interface in promiscous mode = permanently? In Linux it's simply ifconfig <interface> PROMISC. = Is there something similar in BSD? Is it somekind of sysctl = command?

thx.

------------------------------------------
nick.evans
network.engineering
NextVenue, Inc.
phone: (212) 909.2988
pager: (888) 642.5541

------_=_NextPart_001_01BFE524.236D6B20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 12:26:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 03FA537BF8F for ; Mon, 3 Jul 2000 12:26:33 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FX4001BEYYIMK@falla.videotron.net> for freebsd-hackers@FreeBSD.ORG; Mon, 3 Jul 2000 15:18:18 -0400 (EDT) Date: Mon, 03 Jul 2000 15:20:22 -0400 (EDT) From: Bosko Milekic Subject: Re: mbuf re-write(s), v 0.1 In-reply-to: <7941.962650295@critter.freebsd.dk> X-Sender: bmilekic@jehovah.technokratis.com To: Poul-Henning Kamp Cc: freebsd-hackers@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 On Mon, 3 Jul 2000, Poul-Henning Kamp wrote: > Considering the prominence of DoS attacks and similar, I think it > makes a lot of sense to be able to free the memory again, and if > the hysteresis you have built in means that there is no measurable > performance impact I think you will face no objections. That was one of the reasons of writing. Oh, and there's something I forgot to mention previously. The code I presently have frees memory dedicated to mbufs, so obviously, it's significant, but it's even more significant in the case of mbuf clusters, as they are larger. I still haven't finished writing the cluster stuff though but expect it to be similar in concept and design. > Is it possible to auto-tune min_on_avail somehow ? > > What if instead you made it free only when more than 50% of the > memory allocated from the map was unused ? min_on_avail is presently a sysctl but I do expect to have it optionally autotuned - read below. > Could that freeing be done by a timeout routine which runs every > N seconds ? Ah! Finally, you've read my mind! The design has been made with the idea of the possibility of a "kernel process" running [optionally] periodically which will take care of such issues. * reducing fragmentation by moving page descriptor structure nodes with almost complete free lists to the bottom of the "free" doubly-linked list * possible auto-tuning of min_on_avail; I will be expanding mbstat to include allocator statistics, so that the number of times the VM allocation routine and the VM free routine have been called can be recorded and used for such purposes. * drain routine to free pages back to VM system In other words, the free page back to mb_map routine takes as an argument a node on the free list, so the "timeout" daemon can be made to walk the free list and pick out full available pages from the list and return the space to the map, on the condition that min_on_avail is respected. The issue with doing this however is that it will have to splimp() while walking the lists, so the issue being with whether it's really much of an advantage (as opposed to freeing from MFREE if necessary). On the other hand, what I think would be more of an advantage is having MFREE only call m_mbmapfree() [the new free routine] if (how) == M_WAIT. If (how) == M_NOWAIT, then the mbuf will just be attached to its corresponding page descriptor's free chain. I try to take advantage of (how) being M_WAIT as much as possible. For instance, during allocation, even if the free list is not empty but (how) is M_WAIT, the system will still fetch a new page and allocate from it if the number of free mbufs are less than min_on_avail. This is to minimize the calling to m_mbmapalloc() when allocations are to be done with M_NOWAIT (i.e. from interrupts). > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 12:30:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from maxim.gba.oz.au (gba.tmx.com.au [203.9.155.249]) by hub.freebsd.org (Postfix) with SMTP id 93CF837BA5D for ; Mon, 3 Jul 2000 12:30:33 -0700 (PDT) (envelope-from gjb@acm.org) Received: (qmail 99747 invoked by uid 1001); 3 Jul 2000 16:09:16 +1000 X-Posted-By: GBA-Post 2.02.01 12-Dec-1999 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Mon, 03 Jul 2000 16:09:16 +1000 From: Greg Black To: Wes Peters Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: style(9) References: <20000630114924.A78968@mithrandr.moria.org> <395D8FD7.484D9896@softweyr.com> In-reply-to: <395D8FD7.484D9896@softweyr.com> of Sat, 01 Jul 2000 00:29:43 CST Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters writes: > Or simply get a wider editor. Seriously. Writing code in 80 columns is > an anachronism. No it's not. It's a widely-accepted fact that humans have difficulty reading lines with more than about 70 characters in them -- this difficulty increases with age (and is probably also an issue for people with impaired vision, although I'm no expert on that). It therefore makes sense to limit any textual material, whether it's program source code or not, to less than 80 columns unless it's for personal use or is being displayed by some tool that sets widths according to user preferences -- but that does not apply to program sources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 12:40:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 2A62F37B551 for ; Mon, 3 Jul 2000 12:40:41 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 84F831C6C; Mon, 3 Jul 2000 15:40:40 -0400 (EDT) Date: Mon, 3 Jul 2000 15:40:40 -0400 From: Bill Fumerola To: Bosko Milekic Cc: Poul-Henning Kamp , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf re-write(s), v 0.1 Message-ID: <20000703154040.V18942@jade.chc-chimes.com> References: <7941.962650295@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bmilekic@dsuper.net on Mon, Jul 03, 2000 at 03:20:22PM -0400 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 03, 2000 at 03:20:22PM -0400, Bosko Milekic wrote: > > Considering the prominence of DoS attacks and similar, I think it > > makes a lot of sense to be able to free the memory again, and if > > the hysteresis you have built in means that there is no measurable > > performance impact I think you will face no objections. > > That was one of the reasons of writing. Oh, and there's something I > forgot to mention previously. The code I presently have frees memory > dedicated to mbufs, so obviously, it's significant, but it's even > more significant in the case of mbuf clusters, as they are larger. I > still haven't finished writing the cluster stuff though but expect it > to be similar in concept and design. Just to add a little real worldness here: I'd love to have FreeBSD be able to reclaim memory quicker at the sacrifice of a few cpu cycles. Why? Well, the "add more memory" arguement doesn't work well when I get DoS attacks that will eat any memory available because they can connect quicker then I can reclaim the memory. -- Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES e-mail: billf@chimesnet.com / billf@FreeBSD.org / ircadmin@lsl.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 13: 0:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 5694237BEFC for ; Mon, 3 Jul 2000 13:00:18 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA08461; Mon, 3 Jul 2000 21:59:37 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bill Fumerola Cc: Bosko Milekic , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf re-write(s), v 0.1 In-reply-to: Your message of "Mon, 03 Jul 2000 15:40:40 EDT." <20000703154040.V18942@jade.chc-chimes.com> Date: Mon, 03 Jul 2000 21:59:37 +0200 Message-ID: <8459.962654377@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000703154040.V18942@jade.chc-chimes.com>, Bill Fumerola writes: >I'd love to have FreeBSD be able to reclaim memory quicker at the sacrifice >of a few cpu cycles. Why? Well, the "add more memory" arguement doesn't work >well when I get DoS attacks that will eat any memory available because they >can connect quicker then I can reclaim the memory. I have this dream of a global "VM availability flag": Imagine if the kernel kept a global variable: enum {VM_PLENTY, VM_TIGHT, VM_NONE, VM_PANIC} vm_state; /* VM_PLENTY: No worries */ /* VM_TIGHT: Don't make it any worse if you can avoid it */ /* VM_NONE: Fail if you must, free some if you can */ /* VM_PANIC: "VM, VM, my panic for some VM" */ At least a few pieces of our memory-gobbling code could examine and adjust their caching behaviour from that. Take the vfs name-cache as an example: /* Create a new vfs_name-cache entry */ cache_enter(...) switch (vm_state) { case VM_PLENTY: /* do as today */ break; case VM_TIGHT: /* delete at least as many bytes as we add (LRU wise) */ break; case VM_NONE: /* delete two entries, don't add the new one */ break; case VM_PANIC: /* delete the entire cache */ break; } The mbuf allocator can use this to great effect if the various MGET() calls were labeled according to their importance. Respecting such a flag in the various kernels provide great resistance against DoS. User land processes can benefit from this as well: a sysctl would allow malloc(3) to investigate this state whenever it had was dealing with a full page, and if needed it could release all it's cached pages, possibly even call an optional "GC" callback into the program to force a realloc(3) sequence in long-running daemons. (An alternative scenario is to have a SIGVMSTATE defaulting to ignore which gets sent when the variable changes, but that would have thundering herd issues if a lot of processes was paged out.) If only somebody would add that variable, I don't feel like diving into the VM system right now. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Mon Jul 3 13: 1: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id C243F37BEFC for ; Mon, 3 Jul 2000 13:00:46 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id PAA03183; Mon, 3 Jul 2000 15:00:35 -0500 (CDT) (envelope-from dan) Date: Mon, 3 Jul 2000 15:00:34 -0500 From: Dan Nelson To: Nick Evans Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: BPF and Promiscuous Mode Message-ID: <20000703150034.A2787@dan.emsphone.com> References: <712384017032D411AD7B0001023D799B07C92C@SN1EXCHMBX> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.4i In-Reply-To: <712384017032D411AD7B0001023D799B07C92C@SN1EXCHMBX>; from "Nick Evans" on Mon Jul 3 15:23:16 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jul 03), Nick Evans said: > How do I set an interface in promiscous mode permanently? In Linux > it's simply ifconfig PROMISC. Is there something similar > in BSD? Is it somekind of sysctl command? The only code that fiddles with the promisc bit is bridging and bpf, so the only way to do it now is to start up packet filtering. Why do you need to turn it on? -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 13:40:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 9C19737C1B0 for ; Mon, 3 Jul 2000 13:40:23 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 3 Jul 2000 21:40:21 +0100 (BST) To: freebsd-hackers@freebsd.org Subject: Global variables defined several times. X-Request-Do: Date: Mon, 03 Jul 2000 21:40:21 +0100 From: David Malone Message-ID: <200007032140.aa37554@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just noticed that usr.bin/ftp/ftp_var.h defines a large selection of global variables, and then this header file is included in multiple C source files. I thought this should lead to one copy of the global varible per source file, and then a warning or error at link time due to symbols being defined multiple times. This doesn't seem to be the case with the toolchain - you seem to get one copy of each variable for the final linked unit. I tested this with some different compilers and linkers - SAS/C on the Amiga and CodeWarrior on the Mac seem to complain about the symbols turning up twice. AIX and Digital Unix's compilers seem to have the same behavior as the FreeBSD toolchain. I guess this means it's a traditional Unix feature? I did look at the object files with nm, and it shows these symbols with type "C" - unfortunately this isn't explained in the nm or objdump man pages, and there doesn't seem to be an obvious place to look in the rest of the info pages. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 13:44:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 9B67537B602 for ; Mon, 3 Jul 2000 13:44:07 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id WAA08741; Mon, 3 Jul 2000 22:43:10 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: David Malone Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Global variables defined several times. In-reply-to: Your message of "Mon, 03 Jul 2000 21:40:21 BST." <200007032140.aa37554@salmon.maths.tcd.ie> Date: Mon, 03 Jul 2000 22:43:10 +0200 Message-ID: <8739.962656990@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007032140.aa37554@salmon.maths.tcd.ie>, David Malone writes: >I've just noticed that usr.bin/ftp/ftp_var.h defines a large >selection of global variables, and then this header file is included >in multiple C source files. > >I thought this should lead to one copy of the global varible per >source file, and then a warning or error at link time due to symbols >being defined multiple times. This doesn't seem to be the case with >the toolchain - you seem to get one copy of each variable for the >final linked unit. This is called "common" variables. They're documented with that behaviour in the old and new testament. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Mon Jul 3 13:45:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 1D48B37B8C6 for ; Mon, 3 Jul 2000 13:45:08 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id PAA09565; Mon, 3 Jul 2000 15:45:05 -0500 (CDT) (envelope-from dan) Date: Mon, 3 Jul 2000 15:45:05 -0500 From: Dan Nelson To: Nick Evans , freebsd-hackers@freebsd.org Subject: Re: BPF and Promiscuous Mode Message-ID: <20000703154505.A4860@dan.emsphone.com> References: <712384017032D411AD7B0001023D799B07C931@SN1EXCHMBX> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.4i In-Reply-To: <712384017032D411AD7B0001023D799B07C931@SN1EXCHMBX>; from "Nick Evans" on Mon Jul 3 16:10:42 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jul 03), Nick Evans said: > I'm trying to use IPFilter's copying functions to make a load > balancer, I have traffic being mirrored from a router to one > interface on the BSD box, and for some reason the only time netstat > reports any traffic on that interface is when tcpdump or some other > program that utilizes BPF is running. I have a feeling that this is > why I cannot get the packet copying functionality of IPFilter to > work. I guess there is no similar way as in Linux (ifconfig > PROMISC) to turn BPF on permanently? So you have: [ router ] | | [ BSD box ] | | | | [ web ] [ web ] [server] [server] ? You'll probably want either routing or bridging enabled on the BSD box, to handle any DNS lookups or other activity the web servers will be doing, and with either of those enabled, ipfilter should be able to process the packets. I've never used ipfilter myself, though, so I can't say whether this will definitely work or not. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 14:22:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id E478137BFD1 for ; Mon, 3 Jul 2000 14:22:31 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 3 Jul 2000 22:22:30 +0100 (BST) To: Poul-Henning Kamp Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Global variables defined several times. In-reply-to: Your message of "Mon, 03 Jul 2000 22:43:10 +0200." <8739.962656990@critter.freebsd.dk> X-Request-Do: Date: Mon, 03 Jul 2000 22:22:30 +0100 From: David Malone Message-ID: <200007032222.aa41540@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200007032140.aa37554@salmon.maths.tcd.ie>, David Malone writes: > >I've just noticed that usr.bin/ftp/ftp_var.h defines a large > >selection of global variables, and then this header file is included > >in multiple C source files. > > > >I thought this should lead to one copy of the global varible per > >source file, and then a warning or error at link time due to symbols > >being defined multiple times. This doesn't seem to be the case with > >the toolchain - you seem to get one copy of each variable for the > >final linked unit. > This is called "common" variables. They're documented with that > behaviour in the old and new testament. In the K&R1 I have to hand, the last line of page 76 and top of page 77 say: If the lines int sp; double val[MAXVAL]; apprar outside any function, they \emph{define} the expernal variables sp and val... Further down page 77: There must be only one \emph{definition} of an external variable among all the files that make up the source program; other files may contain extern declarations to access it. I can't find my second edition at the moment. This behavior is commented on in the C FAQ as something the ANSI standard describes as a common extension. (http://www.eskimo.com/~scs/C-faq/q1.7.html) It also seems to suggest it is mostly a Unix thing. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 14:32:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from po4.glue.umd.edu (po4.glue.umd.edu [128.8.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 9B83637C1D0 for ; Mon, 3 Jul 2000 14:32:45 -0700 (PDT) (envelope-from howardjp@glue.umd.edu) Received: from z.glue.umd.edu (root@z.glue.umd.edu [128.8.10.71]) by po4.glue.umd.edu (8.10.1/8.10.1) with ESMTP id e63LWJh23813; Mon, 3 Jul 2000 17:32:19 -0400 (EDT) Received: from z.glue.umd.edu (sendmail@localhost [127.0.0.1]) by z.glue.umd.edu (8.9.3/8.9.3) with SMTP id RAA00507; Mon, 3 Jul 2000 17:32:19 -0400 (EDT) Received: from localhost (howardjp@localhost) by z.glue.umd.edu (8.9.3/8.9.3) with ESMTP id RAA00503; Mon, 3 Jul 2000 17:32:19 -0400 (EDT) X-Authentication-Warning: z.glue.umd.edu: howardjp owned process doing -bs Date: Mon, 3 Jul 2000 17:32:19 -0400 (EDT) From: James Howard To: Ben Smithurst Cc: Brian Somers , freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/security -> /etc/periodic/security ? In-Reply-To: <20000629211028.B48373@strontium.scientia.demon.co.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 On Thu, 29 Jun 2000, Ben Smithurst wrote: > Try the attached. They haven't been thoroughly tested, but that's what > -CURRENT is for, right? :-) I even remembered to update the manual page > this time... This needs to have knobs and stuff located in /etc/defaults/periodic.conf Also, it would be cool if a security option were made to periodic(8). Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 14:40:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id A0EAA37B80E for ; Mon, 3 Jul 2000 14:40:41 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id PAA72333; Mon, 3 Jul 2000 15:40:31 -0600 (MDT) Date: Mon, 3 Jul 2000 15:40:31 -0600 (MDT) From: Nick Rogness To: Dan Nelson Cc: Nick Evans , "'freebsd-hackers@freebsd.org'" Subject: Re: BPF and Promiscuous Mode In-Reply-To: <20000703150034.A2787@dan.emsphone.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, 3 Jul 2000, Dan Nelson wrote: > In the last episode (Jul 03), Nick Evans said: > > How do I set an interface in promiscous mode permanently? In Linux > > it's simply ifconfig PROMISC. Is there something similar > > in BSD? Is it somekind of sysctl command? Stupid Man's Answer: I would just run on bootup: /usr/sbin/tcpdump >> /dev/null & Probaby not the answer you are looking for, but maybe it will help. Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 14:44:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from front7.grolier.fr (front7.grolier.fr [194.158.96.57]) by hub.freebsd.org (Postfix) with ESMTP id 70C4A37B80E for ; Mon, 3 Jul 2000 14:44:37 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from Cergy-2-143.club-internet.fr (Cergy-2-143.club-internet.fr [195.36.197.143]) by front7.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA19121; Mon, 3 Jul 2000 23:44:33 +0200 (MET DST) Date: Mon, 3 Jul 2000 23:22:46 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: "W.H.Scholten" Cc: hackers@FreeBSD.ORG Subject: Re: uncool MO disk problems, addendum In-Reply-To: <3960C18E.41C67EA6@xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Jul 2000, W.H.Scholten wrote: > L.s. >=20 > small addendum: > - it's fbsd 3.3R on i386 as you may have guesssed from the mail headers. > - I use the new fbsd symbios/ncr scsi driver (the README says latest > revision is sym-0.12.0-19991127). The README file hasn't been maintained up to date. It has been useful when the driver was not yet in the repository. It just has been purged of obsolete informations on my latest commit to HEAD. Btw, I donnot think that the driver version has something to do with the MO disk problems you reported in your previous mail. I haven't MFCed a recent `sym' driver version to 3.5R since no problem had been reported to me ('Never change a system that works' applied here :) ). However, given that SYM53C1010 based boards are now available, especially from Tekram, an MFC will be needed to ensure that all SYM53C1010 chip issues I know about are addressed also in RELENG_3. (Latest `sym' driver should still be 3.X compatible at source level thanks to COMPAT code versus NEW BUS one being conditionned according to FreeBSD version. Thus, user can for now move latest driver sources to a 3.X tree and just rebuild the kernel). =20 > Also my mail address is whs@xs4all.nl, reply on the previous mail will > give spaces in the mail address.. >=20 > Wouter G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 15:24:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from evil.2y.net (ztown2-2-178.adsl.one.net [216.23.15.178]) by hub.freebsd.org (Postfix) with ESMTP id DF84037B5FC for ; Mon, 3 Jul 2000 15:24:53 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id SAA59577; Mon, 3 Jul 2000 18:32:04 -0400 (EDT) (envelope-from cokane) Date: Mon, 3 Jul 2000 18:32:04 -0400 From: Coleman Kane To: Ollivier Robert Cc: hackers@freebsd.org Subject: Re: Anyone tried StarOffice 5.2 yet? Message-ID: <20000703183204.A59539@cokane.yi.org> References: <200007030206.VAA41837@bloop.craftncomp.com> <20000703002607.A538@cokane.yi.org> <20000703073817.A77567@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000703073817.A77567@keltia.freenix.fr>; from roberto@keltia.freenix.fr on Mon, Jul 03, 2000 at 01:08:09PM -0400 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You should be using the linux_base package. The linux_lib were removed after rh 5.2. I did this on 5.0-C. Ollivier Robert had the audacity to say: > According to Coleman Kane: > > I d/l'd from Sun and it installed without a hitch. It is a hell of a lot > > faster than 5.1 and they've gotten rid of some of the crapisms. > > On 5.0-CURRENT or 4-STABLE ? With which linux_lib port ? I tried on my > 5.0-CURRENT with the latest linux_lib (from RedHate 6.1) and the setup dies > before the end, leaving with a non runnable SO :-( > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 16:27:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DAB6337B73C for ; Mon, 3 Jul 2000 16:27:06 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA08050; Mon, 3 Jul 2000 17:27:04 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA27427; Mon, 3 Jul 2000 17:26:50 -0600 (MDT) Message-Id: <200007032326.RAA27427@harmony.village.org> To: chris@calldei.com Subject: Re: dev to name Cc: Fox Anderson , freebsd-hackers In-reply-to: Your message of "Sun, 02 Jul 2000 15:01:16 CDT." <20000702150116.E66762@holly.calldei.com> References: <20000702150116.E66762@holly.calldei.com> <395FC6CB.7080400@mail.ru> Date: Mon, 03 Jul 2000 17:26:50 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000702150116.E66762@holly.calldei.com> Chris Costello writes: : On Sunday, July 02, 2000, Fox Anderson wrote: : > Hi. : > How can i find out the name of device file by device major/minor? : : The devtoname() function. ``man devtoname'' This is a kernel only function. The only way to do it in user land is to loop through the /dev/ directory and hope that you can find a match. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 17:43:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 4CEB037B53B; Mon, 3 Jul 2000 17:43:37 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com ([208.187.122.225]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id SAA05806; Mon, 3 Jul 2000 18:43:22 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <396133AB.B30CADBD@softweyr.com> Date: Mon, 03 Jul 2000 18:45:32 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Coleman Kane Cc: Michael Lucas , se@FreeBSD.ORG, shocking@houston.rr.com, hackers@FreeBSD.ORG Subject: Re: Anyone tried StarOffice 5.2 yet? References: <20000703114030.A1816@StefanEsser.FreeBSD.org> <200007031246.IAA34027@blackhelicopters.org> <20000703125008.A58195@cokane.yi.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Coleman Kane wrote: > > Naw, man. Ports are necessary. > > Michael Lucas had the audacity to say: > > > I did not have time to work out what's failing, but it should be easy > > > to reproduce (start the installer with an option, hmmm, think it was > > > /net, can't check, since I'm away from that system ...) > > > > Yep. Run the installer as root with the /net option, and put it > > under, say, /usr/local/office52. > > > > Then: > > > > exit root > > > > cd /usr/local/office52/program > > > > run setup as a regular user. > > > > No problem. > > > > I'm not sure we should even bother with the port. :) They sure are: wes@homer$ /usr/local/office52/program bash: /usr/local/office52/program: is a directory wes@homer$ /usr/local/office52/program/soffice /usr/local/office52/program/soffice: /usr/bin/test: not found Then it continues to run the binary. Perhaps the port could fix this minor bobble? And include a packing list so it can be deleted? Other than that, it seems to work OK. 44 seconds to startup and shutdown; it still isn't exactly a speed daemon. -- "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 Mon Jul 3 18:43:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mg136-135.ricochet.net [204.179.136.135]) by hub.freebsd.org (Postfix) with ESMTP id 25EA037C1B6; Mon, 3 Jul 2000 18:42:21 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id SAA00380; Mon, 3 Jul 2000 18:46:35 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007040146.SAA00380@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nat Lanza Cc: scsi@freebsd.org, hackers@freebsd.org Subject: Re: SCSI HBA device detection? In-reply-to: Your message of "23 Jun 2000 13:10:26 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Jul 2000 18:46:30 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm writing a SCSI HBA driver that simulates a bus with some > ramdisk-backed disks attached to it. I've read through the HBA > tutorial in Daemon News, but I'm still unsure how to tell the system > about my pretend disk devices. I suspect part of the problem is that > I don't actually have real devices or a real IO bus. If this is meant to be an exercise in writing a CAM HBA driver, then you need to teach your disk-emulation code about the basic SCSI commands (INQUIRY, TEST UNIT READY, etc). The SCSI infrastructure will use these commands to automatically detect your drives. If you're writing a generic ramdisk, this is a really masochistic way to go about doing it. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 18:43:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 6B08C37C1B9 for ; Mon, 3 Jul 2000 18:43:27 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 139FSm-0005qN-00; Tue, 04 Jul 2000 00:17:16 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 139FSm-0002pI-00; Tue, 04 Jul 2000 00:17:16 +0100 Date: Tue, 4 Jul 2000 00:17:16 +0100 From: Ben Smithurst To: James Howard Cc: Brian Somers , freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/security -> /etc/periodic/security ? Message-ID: <20000704001716.A13714@strontium.scientia.demon.co.uk> References: <20000629211028.B48373@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="cNdxnHkX5QqsyA0e" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable James Howard wrote: > On Thu, 29 Jun 2000, Ben Smithurst wrote: >=20 >> Try the attached. They haven't been thoroughly tested, but that's what >> -CURRENT is for, right? :-) I even remembered to update the manual page >> this time... >=20 > This needs to have knobs and stuff located in /etc/defaults/periodic.conf Umm, which knobs? I added the only two options the security stuff currently uses, what else does it need? > Also, it would be cool if a security option were made to periodic(8). Well, "periodic security" will work as long as /etc/periodic/security exists, so I guess you just mean the docs need updating? I'll get to that if someone is actually planning on committing this stuff. --=20 Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D --cNdxnHkX5QqsyA0e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: EgjSV3VDV5yjh+NfBeDjBb3F0D4q1WvZ iQCVAwUBOWEe+ysPVtiZOS99AQHvZwQAlqwhmCkYWy5ILaRQ+/22B46kUc5kTuKh 3sn1xp603rn3ZfBca4cWcfIKgyc3s/fJD87h8LIhJdD+pyc4itmtxmAG1gnX/1Il eS9ioMaQkx3wUs7Vf6lglo9BrgDSzhcX2KDjW7jjckk4VZkGNXaRsyfTm1HuhXIP bOwULjKJtXo= =4l6/ -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 18:59:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mg136-135.ricochet.net [204.179.136.135]) by hub.freebsd.org (Postfix) with ESMTP id 08D5D37C1EA for ; Mon, 3 Jul 2000 18:54:45 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id SAA00477; Mon, 3 Jul 2000 18:53:24 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007040153.SAA00477@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: KATO Takenori Cc: hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box In-reply-to: Your message of "Sun, 02 Jul 2000 02:56:09 +0900." <20000702025609D.kato@gneiss.eps.nagoya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Jul 2000 18:53:24 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > If it's something that can be done as eg. a KLD > > we might want to do that instead, or through some other mechanism for > > handling these sort of CPU quirks. > > It sounds good. If binary-format quriks is supported, we can supply > update modules for new CPU and newly found errata like the update > module for AMD K6-2 CPU of Windows 95. Indeed. This won't help us where we need to modify the actual behaviour of a system component, but when we can perform external corrective actions, it will help a lot. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 19: 0: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mg136-135.ricochet.net [204.179.136.135]) by hub.freebsd.org (Postfix) with ESMTP id 3895237C259 for ; Mon, 3 Jul 2000 18:59:53 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id TAA00618; Mon, 3 Jul 2000 19:05:44 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007040205.TAA00618@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: jmt@tbe.net Cc: freebsd-hackers@freebsd.org Subject: Re: APM problems on NEC Versa 2000C In-reply-to: Your message of "24 Jun 2000 14:12:53 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Jul 2000 19:05:43 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have an older 486 laptop which is newly running FreeBSD > 4.0-RELEASE. When I attempted to enable APM and reboot, I got the > following on my screen: > > --begin screen-- > Fatal trap 9: general protection fault while in kernel mode > instruction pointer = 0x58:0x337 > stack pointer = 0x10:0xc334dcdc > frame pointer = 0x10:0xc334dce0 > code segment = base 0xc00ea00, limit 0xffff, type 0x1b > = DPL 0, pres 1, def32 0, gran 0 > processor eflags = resume, IOPL = 0 > current process = 184 (apm) > interrupt mask = none > kernel: type 9 trap, code=0 > Stopped at 0x337: This is inside the APM BIOS - it's probably a BIOS bug that doesn't affect Windows/DOS. With such an old system, you are probably SOL unless you can track down more details (eg. special hacks for this system and Linux). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 19:10: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mg136-135.ricochet.net [204.179.136.135]) by hub.freebsd.org (Postfix) with ESMTP id 669B637C294 for ; Mon, 3 Jul 2000 19:05:00 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id TAA00657; Mon, 3 Jul 2000 19:10:01 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007040210.TAA00657@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Lyndon Nerenberg Cc: freebsd-hackers@freebsd.org Subject: Re: Concurrent access to SMbus In-reply-to: Your message of "Mon, 05 Jun 2000 14:47:04 MDT." <200006052047.e55Kl5X51895@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Jul 2000 19:09:58 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I notice that the /dev/smbX devices are exclusive access. This makes > it impossible to run two (or more) programs concurrently that want > to talk to SMbus devices (in my case, healthd and lmmon, both of which > want to open /dev/smb0 to access the LM78). > > Is this an SMbus restriction, or an artifact of the smb driver? I did a > very quick scan through /sys/dev/smbus/* and nothing jumped out to > indicate why it needs to be exclusive access. Transactions on the bus should be locked, ie. only one client talking at a time, but it should probably be feasible to allow more than one opener. The SMBus code is dearly in need of a maintainer. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 19:10:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hurlame.pdl.cs.cmu.edu (HURLAME.PDL.CS.CMU.EDU [128.2.189.78]) by hub.freebsd.org (Postfix) with SMTP id B4F9637BAAF; Mon, 3 Jul 2000 19:10:11 -0700 (PDT) (envelope-from magus+@hurlame.pdl.cs.cmu.edu) To: Mike Smith Cc: scsi@freebsd.org, hackers@freebsd.org Subject: Re: SCSI HBA device detection? References: <200007040146.SAA00380@mass.osd.bsdi.com> From: Nat Lanza Date: 03 Jul 2000 22:09:36 -0400 In-Reply-To: Mike Smith's message of "Mon, 03 Jul 2000 18:46:30 -0700" Message-ID: Lines: 26 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > If this is meant to be an exercise in writing a CAM HBA driver, then you > need to teach your disk-emulation code about the basic SCSI commands > (INQUIRY, TEST UNIT READY, etc). The SCSI infrastructure will use these > commands to automatically detect your drives. I already have code for handling the basic SCSI commands (I'm really porting a scsi-ramdisk driver from Linux rather than writing from scratch). The bit I'm curious about are which XPT actions I'll need to support other than XPT_PATH_INQ and XPT_SCSI_IO. > If you're writing a generic ramdisk, this is a really masochistic way to > go about doing it. 8) It's really a mix of an exercise in writing a CAM HBA driver and a first step towards a SCSI-over-IP driver. Also, a SCSI ramdisk can be handy for some of the benchmarking and tracing we do. --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 19:11:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from po4.glue.umd.edu (po4.glue.umd.edu [128.8.10.124]) by hub.freebsd.org (Postfix) with ESMTP id C88F537C26C for ; Mon, 3 Jul 2000 19:11:22 -0700 (PDT) (envelope-from howardjp@glue.umd.edu) Received: from y.glue.umd.edu (root@y.glue.umd.edu [128.8.10.68]) by po4.glue.umd.edu (8.10.1/8.10.1) with ESMTP id e642Aol27657; Mon, 3 Jul 2000 22:10:50 -0400 (EDT) Received: from y.glue.umd.edu (sendmail@localhost [127.0.0.1]) by y.glue.umd.edu (8.9.3/8.9.3) with SMTP id WAA17075; Mon, 3 Jul 2000 22:10:50 -0400 (EDT) Received: from localhost (howardjp@localhost) by y.glue.umd.edu (8.9.3/8.9.3) with ESMTP id WAA17071; Mon, 3 Jul 2000 22:10:49 -0400 (EDT) X-Authentication-Warning: y.glue.umd.edu: howardjp owned process doing -bs Date: Mon, 3 Jul 2000 22:10:49 -0400 (EDT) From: James Howard To: Ben Smithurst Cc: Brian Somers , freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/security -> /etc/periodic/security ? In-Reply-To: <20000704001716.A13714@strontium.scientia.demon.co.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 On Tue, 4 Jul 2000, Ben Smithurst wrote: > Umm, which knobs? I added the only two options the security stuff currently > uses, what else does it need? For each script under /etc/periodic/{daily,weekly,monthly}/, there is a knob in /etc/defaults/periodic. This controls whether the script is run and maybe gives it some options. For instance, the daily/440.status-mailq knobs look like this: # 440.status-mailq daily_status_mailq_enable="YES" # Check mail status daily_status_mailq_shorten="NO" # Shorten output There should be equivalent for each of the security scripts. As I mentioned when I first brought this mess up, I am porting the scripts to Red Hat 6.2. I have all of them done except for the security scripts. I am waiting to see if any when a finalized version of these end up in the tree. I plan on making an RPM available of it all when done. Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 20:35:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from evil.2y.net (ztown2-2-178.adsl.one.net [216.23.15.178]) by hub.freebsd.org (Postfix) with ESMTP id 2336737B8EF; Mon, 3 Jul 2000 20:35:26 -0700 (PDT) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id XAA00891; Mon, 3 Jul 2000 23:41:38 -0400 (EDT) (envelope-from cokane) Date: Mon, 3 Jul 2000 23:41:38 -0400 From: Coleman Kane To: Wes Peters Cc: Coleman Kane , Michael Lucas , se@FreeBSD.ORG, shocking@houston.rr.com, hackers@FreeBSD.ORG Subject: Re: Anyone tried StarOffice 5.2 yet? Message-ID: <20000703234138.A874@cokane.yi.org> References: <20000703114030.A1816@StefanEsser.FreeBSD.org> <200007031246.IAA34027@blackhelicopters.org> <20000703125008.A58195@cokane.yi.org> <396133AB.B30CADBD@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <396133AB.B30CADBD@softweyr.com>; from wes@softweyr.com on Mon, Jul 03, 2000 at 08:43:25PM -0400 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeah, change the /usr/bin/test in soffice to /bin/test. BSD has test in /bin. Wes Peters had the audacity to say: > Coleman Kane wrote: > > > > Naw, man. Ports are necessary. > > > > They sure are: > > wes@homer$ /usr/local/office52/program > bash: /usr/local/office52/program: is a directory > > wes@homer$ /usr/local/office52/program/soffice > /usr/local/office52/program/soffice: /usr/bin/test: not found > > Then it continues to run the binary. Perhaps the port could fix this > minor bobble? And include a packing list so it can be deleted? > > Other than that, it seems to work OK. 44 seconds to startup and shutdown; > it still isn't exactly a speed daemon. > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > wes@softweyr.com http://softweyr.com/ > -- Coleman Kane President, UC Free O.S. Users Group - http://pohl.ececs.uc.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 21:19:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sn1oexchr01.nextvenue.com (sn1oexchr01.nextvenue.com [63.209.169.9]) by hub.freebsd.org (Postfix) with SMTP id 7ED9937BA18 for ; Mon, 3 Jul 2000 21:19:31 -0700 (PDT) (envelope-from nevans@nextvenue.com) Received: FROM sn1exchmbx.nextvenue.com BY sn1oexchr01.nextvenue.com ; Tue Jul 04 00:17:48 2000 -0400 Received: by SN1EXCHMBX with Internet Mail Service (5.5.2650.21) id ; Tue, 4 Jul 2000 00:17:42 -0400 Message-ID: <712384017032D411AD7B0001023D799B07C93C@SN1EXCHMBX> From: Nick Evans To: 'Dan Nelson' Cc: "'freebsd-hackers@freebsd.org'" Subject: RE: BPF and Promiscuous Mode Date: Tue, 4 Jul 2000 00:17:34 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFE56E.C75F7B70" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFE56E.C75F7B70 Content-Type: text/plain; charset="iso-8859-1" Exactly, I just tried it and it didn't work :(. Yes you are right on, NFR is a sniffer/ids, but it is based on the OpenBSD kernel and therefore does not support multiple processors. I just tried bridging and it does in fact bridge all interfaces together, but it still does not appear to be mirroring all traffic from one interface to another. Apparently there are issues with IPFilter and FreeBSD... I am going to try OpenBSD and IPFilter tonight. The IPFilter people know that bridging works on OpenBSD, and you can bridge specific interfaces. -----Original Message----- From: Dan Nelson [mailto:dnelson@emsphone.com] Sent: Monday, July 03, 2000 10:34 PM To: Nick Evans Subject: Re: BPF and Promiscuous Mode Is there any reason you're not CC'ing the list? I added it back on my first reply on the assumption you simply forgot, but this email is missing it too. It's good to have exchanges like these in the mailing-list archives, so help other people that might have the same question later. In the last episode (Jul 03), Nick Evans said: > actually it's like this > > --- > | > | <- mirrored port > > | > | > > | | | > | | | > > > the nfr boxes do not have ip's so i just need the traffic duplicated > (so routing is out of the question), but i wanted to use ipfilter to, > get this, filter the traffic so not all the ida's see all the > traffic. the simply cannot handle 600Mbits each... my plan is to put > a gig interface, or two, into the BSD box and several dualport server > adaptors and then segment that traffic down. bridging might work, but > i do not know how to bind certain interfaces together in FreeBSD, > OpenBSD, yes, but not Free... Aahh. An nfr is a sniffer. I assumed that you were load-balancing web servers or something, which was confising me a bit since you don't want to use mirroring for this. For your purposes, mirroring is perfect. I think enabling bridging, and then using ipfilter or ipfw to only allow (say) 1/3 of the Net addresses to each server (assuming you have 3 nfr's), would do what you want. I wonder if NFR will take advantage of multiple CPUs in a single box. That way you don't have to worry about any of this. In the last episode (Jul 03), Nick Evans said: > actually a better question would have been, do you know if you can > bridge multiple interfaces to one other interface lik 4 100mbit nics > to one gigabit nic? I assume so. The bridge manpage mentions the inability to selectively bridge certain interfaces, so the default must be to bridge all ethernet interfaces. You can probably add some filtering rules to make sure you don't re-transmit packets out of your gigabit NICs. -- Dan Nelson dnelson@emsphone.com ------_=_NextPart_001_01BFE56E.C75F7B70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: BPF and Promiscuous Mode

Exactly, I just tried it and it didn't work :(.  = Yes you are right on, NFR is a sniffer/ids, but it is based on the = OpenBSD kernel and therefore does not support multiple processors. I = just tried bridging and it does in fact bridge all interfaces together, = but it still does not appear to be mirroring all traffic from one = interface to another. Apparently there are issues with IPFilter and = FreeBSD... I am going to try OpenBSD and IPFilter tonight. The IPFilter = people know that bridging works on OpenBSD, and you can bridge specific = interfaces.

-----Original Message-----
From: Dan Nelson [mailto:dnelson@emsphone.com]
Sent: Monday, July 03, 2000 10:34 PM
To: Nick Evans
Subject: Re: BPF and Promiscuous Mode



Is there any reason you're not CC'ing the list?  = I added it back on my
first reply on the assumption you simply forgot, but = this email is
missing it too.  It's good to have exchanges = like these in the
mailing-list archives, so help other people that = might have the same
question later.

In the last episode (Jul 03), Nick Evans said:
> actually it's like this
>
> <router> --- <switch>
>       =         =         |
>       =         =         | <- mirrored port
>       =         <freebsdbox>
>       =         =         |
>       =         =         |
>       =      <vlan'd switch>
>       =         = |       = |       |
>       =         = |       = |       |
>       =     <nfr> <nfr> <nfr>
>
> the nfr boxes do not have ip's so i just need = the traffic duplicated
> (so routing is out of the question), but i = wanted to use ipfilter to,
> get this, filter the traffic so not all the = ida's see all the
> traffic. the simply cannot handle 600Mbits = each... my plan is to put
> a gig interface, or two, into the BSD box and = several dualport server
> adaptors and then segment that traffic down. = bridging might work, but
> i do not know how to bind certain interfaces = together in FreeBSD,
> OpenBSD, yes, but not Free...

Aahh.  An nfr is a sniffer.  I assumed that = you were load-balancing web
servers or something, which was confising me a bit = since you don't want
to use mirroring for this.  For your purposes, = mirroring is perfect.

I think enabling bridging, and then using ipfilter or = ipfw to only
allow (say) 1/3 of the Net addresses to each server = (assuming you have
3 nfr's), would do what you want.  I wonder if = NFR will take advantage
of multiple CPUs in a single box.  That way you = don't have to worry
about any of this.

In the last episode (Jul 03), Nick Evans said:
> actually a better question would have been, do = you know if you can
> bridge multiple interfaces to one other = interface lik 4 100mbit nics
> to one gigabit nic?

I assume so.  The bridge manpage mentions the = inability to selectively
bridge certain interfaces, so the default must be to = bridge all
ethernet interfaces.  You can probably add some = filtering rules to make
sure you don't re-transmit packets out of your = gigabit NICs.

--
        Dan = Nelson
        dnelson@emsphone.com

------_=_NextPart_001_01BFE56E.C75F7B70-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 3 22:49:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id E691037C112 for ; Mon, 3 Jul 2000 22:49:28 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 67527 invoked by uid 1000); 4 Jul 2000 05:49:27 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 4 Jul 2000 05:49:27 -0000 Date: Tue, 4 Jul 2000 00:49:27 -0500 (CDT) From: Mike Silbersack To: Mike Smith Cc: KATO Takenori , hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box In-Reply-To: <200007040153.SAA00477@mass.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 On Mon, 3 Jul 2000, Mike Smith wrote: > > Mike Smith wrote: > > > > > If it's something that can be done as eg. a KLD > > > we might want to do that instead, or through some other mechanism for > > > handling these sort of CPU quirks. > > > > It sounds good. If binary-format quriks is supported, we can supply > > update modules for new CPU and newly found errata like the update > > module for AMD K6-2 CPU of Windows 95. > > Indeed. This won't help us where we need to modify the actual behaviour > of a system component, but when we can perform external corrective > actions, it will help a lot. I don't understand the idea here. Are you going to have a KLD that patches the kernel? If so, you'd have to make world before it'd become active, in which case rebuilding the kernel would be quicker. 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 Jul 3 23:40:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 96DF037C149; Mon, 3 Jul 2000 23:40:17 -0700 (PDT) (envelope-from john@baldwin.cx) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id XAA31946; Mon, 3 Jul 2000 23:40:16 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id XAA37730; Mon, 3 Jul 2000 23:41:16 -0700 (PDT) (envelope-from john) Message-Id: <200007040641.XAA37730@john.baldwin.cx> 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: <39603C55.507A2829@gorean.org> Date: Mon, 03 Jul 2000 23:41:16 -0700 (PDT) From: John Baldwin To: Doug Barton Subject: Re: ls -G seems to depend on TERM=xterm-color Cc: hackers@FreeBSD.ORG, Sean Lutner , Brian Fundakowski Feldman Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jul-00 Doug Barton wrote: > Brian Fundakowski Feldman wrote: >> >> On Sun, 2 Jul 2000, Sean Lutner wrote: >> >> > I'm experiencing the same thing. ls --color doesn't seem to work for me >> > unless like Doug, I set TERM=xterm-color. >> >> That's because the "color" escape sequences are defined for xterm-color >> in termcap; xterm-color is defined as a superset of xterm (see the tc= >> directive). > > Right... I am down with all that. I just wanted to confirm that the > colorized ls depended on the xterm-color setting. > >> I have a lot of X resources defined, and here is one that >> could help you guys: >> >> XTerm*termName: xterm-color > > Ok, that's a good solution, I was just using .bashrc. My point is not > so much why, but that it be properly documented. Do you want to handle > the update of the ls man page, or do you want me to PR a patch? Umm, honestly, this shouldn't be all that non-obvious. Do you expect ls -G to work on a monochrome monitor? Of course not. :P The xterm termcap is by default a monochrome terminal. sysinstall doesn't have color in an xterm either w/ term=xterm. > Thanks, > > Doug -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Jul 3 23:42:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id C91DC37BBA1 for ; Mon, 3 Jul 2000 23:42:18 -0700 (PDT) (envelope-from john@baldwin.cx) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id XAA31951; Mon, 3 Jul 2000 23:40:23 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id XAA37734; Mon, 3 Jul 2000 23:41:22 -0700 (PDT) (envelope-from john) Message-Id: <200007040641.XAA37734@john.baldwin.cx> 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: Date: Mon, 03 Jul 2000 23:41:22 -0700 (PDT) From: John Baldwin To: James Howard Subject: Re: why isnt there a ext2fs.ko ? Cc: freebsd-hackers@FreeBSD.ORG, Maxime Henrion Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jul-00 James Howard wrote: > On Mon, 3 Jul 2000, Maxime Henrion wrote: > >> Hi guys, >> >> I was wondering why the kernel module for ext2fs doesnt exist. I >> think this will be very useful because a lot of linux users come to >> FreeBSD and want to mount their existing linux partitions, and they have >> to recompile their kernel. This isn't a hard task, but it's a bit >> disappointing for new users. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=14217 > > But it doesn't seem to compile with FreeBSD-current anymore. Give me a > day or so and I will update it work with a newer FreeBSD. On this topic, > how would anyone feel about importing NetBSD's GPL-clean ext2fs source? Cool! > Jamie -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Tue Jul 4 0: 4:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.lewman.org (lowrider.lewman.org [209.67.240.52]) by hub.freebsd.org (Postfix) with ESMTP id 4D3E837BFE8; Tue, 4 Jul 2000 00:04:29 -0700 (PDT) (envelope-from sean@rentul.net) Received: by mail.lewman.org (Postfix, from userid 1004) id 704733D32; Tue, 4 Jul 2000 03:05:05 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.lewman.org (Postfix) with ESMTP id 6E1C65BC3; Tue, 4 Jul 2000 03:05:05 -0400 (EDT) Date: Tue, 4 Jul 2000 03:05:05 -0400 (EDT) From: Sean Lutner X-Sender: sean@lowrider.lewman.org To: John Baldwin Cc: Doug Barton , hackers@FreeBSD.ORG, Brian Fundakowski Feldman Subject: Re: ls -G seems to depend on TERM=xterm-color In-Reply-To: <200007040641.XAA37730@john.baldwin.cx> 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, 3 Jul 2000, John Baldwin wrote: > > On 03-Jul-00 Doug Barton wrote: > > Brian Fundakowski Feldman wrote: > >> > >> On Sun, 2 Jul 2000, Sean Lutner wrote: > >> > >> > I'm experiencing the same thing. ls --color doesn't seem to work for me > >> > unless like Doug, I set TERM=xterm-color. > >> > >> That's because the "color" escape sequences are defined for xterm-color > >> in termcap; xterm-color is defined as a superset of xterm (see the tc= > >> directive). > > > > Right... I am down with all that. I just wanted to confirm that the > > colorized ls depended on the xterm-color setting. > > > >> I have a lot of X resources defined, and here is one that > >> could help you guys: > >> > >> XTerm*termName: xterm-color > > > > Ok, that's a good solution, I was just using .bashrc. My point is not > > so much why, but that it be properly documented. Do you want to handle > > the update of the ls man page, or do you want me to PR a patch? > > Umm, honestly, this shouldn't be all that non-obvious. Do you expect > ls -G to work on a monochrome monitor? Of course not. :P The xterm > termcap is by default a monochrome terminal. sysinstall doesn't have > color in an xterm either w/ term=xterm. Well, I'm not really using xterm, I use Eterms, and I've NEVER had this problem before, so it was non-obvious to me. I know the Eterms I'm using are capable of displaying color ls output, because it does so when logged into shells. Also, I'm not sure if this is related, but if the xterms aren't capable of displaying color due to it's termcap, how come I can set the fg (text) to any color I choose, and they show up? > > > Thanks, > > > > Doug > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 0:25:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 5A50537B6F2; Tue, 4 Jul 2000 00:25:14 -0700 (PDT) (envelope-from john@baldwin.cx) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id AAA32193; Tue, 4 Jul 2000 00:25:11 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id AAA40370; Tue, 4 Jul 2000 00:26:16 -0700 (PDT) (envelope-from john) Message-Id: <200007040726.AAA40370@john.baldwin.cx> 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: Date: Tue, 04 Jul 2000 00:26:15 -0700 (PDT) From: John Baldwin To: Sean Lutner Subject: Re: ls -G seems to depend on TERM=xterm-color Cc: Brian Fundakowski Feldman , hackers@FreeBSD.ORG, Doug Barton Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jul-00 Sean Lutner wrote: > Well, I'm not really using xterm, I use Eterms, and I've NEVER had this > problem before, so it was non-obvious to me. I know the Eterms I'm using > are capable of displaying color ls output, because it does so when logged > into shells. Also, I'm not sure if this is related, but if the xterms > aren't capable of displaying color due to it's termcap, how come I can set > the fg (text) to any color I choose, and they show up? The terminal can display text, the termcap just doesn't inform the programs how to do so. Termcap is a means of letting programs not have to know the control sequences needed for different terminals. A termcap need not have support for all the abilities of a terminal. Not all xterm's can display color, so the 'xterm' termcap doesn't include color support. As for your remote shells, check the term variable they use, it may be using ansi or somesuch instead of xterm. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Tue Jul 4 1:14:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id B35CF37B51F; Tue, 4 Jul 2000 01:14:34 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id BAA96440; Tue, 4 Jul 2000 01:14:33 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39619CE9.F0D168FA@gorean.org> Date: Tue, 04 Jul 2000 01:14:33 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0702 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: hackers@FreeBSD.ORG, Sean Lutner , Brian Fundakowski Feldman Subject: Re: ls -G seems to depend on TERM=xterm-color References: <200007040641.XAA37730@john.baldwin.cx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > >> XTerm*termName: xterm-color > > > > Ok, that's a good solution, I was just using .bashrc. My point is not > > so much why, but that it be properly documented. Do you want to handle > > the update of the ls man page, or do you want me to PR a patch? > > Umm, honestly, this shouldn't be all that non-obvious. Do you expect > ls -G to work on a monochrome monitor? Of course not. :P The xterm > termcap is by default a monochrome terminal. sysinstall doesn't have > color in an xterm either w/ term=xterm. This is obvious to you and me, but to a newer user it's not going to be obvious at all. There is going to be a bunch of people who write into the mailing lists wondering why they aren't seeing the colorized ls in their xterms. -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 1:40:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 0BC4A37B8C2; Tue, 4 Jul 2000 01:40:13 -0700 (PDT) (envelope-from john@baldwin.cx) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id BAA32418; Tue, 4 Jul 2000 01:40:11 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id BAA40774; Tue, 4 Jul 2000 01:41:16 -0700 (PDT) (envelope-from john) Message-Id: <200007040841.BAA40774@john.baldwin.cx> 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: <39619CE9.F0D168FA@gorean.org> Date: Tue, 04 Jul 2000 01:41:15 -0700 (PDT) From: John Baldwin To: Doug Barton Subject: Re: ls -G seems to depend on TERM=xterm-color Cc: Brian Fundakowski Feldman , Sean Lutner , hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jul-00 Doug Barton wrote: > John Baldwin wrote: > >> >> XTerm*termName: xterm-color >> > >> > Ok, that's a good solution, I was just using .bashrc. My point is not >> > so much why, but that it be properly documented. Do you want to handle >> > the update of the ls man page, or do you want me to PR a patch? >> >> Umm, honestly, this shouldn't be all that non-obvious. Do you expect >> ls -G to work on a monochrome monitor? Of course not. :P The xterm >> termcap is by default a monochrome terminal. sysinstall doesn't have >> color in an xterm either w/ term=xterm. > > This is obvious to you and me, but to a newer user it's not going to be > obvious at all. There is going to be a bunch of people who write into > the mailing lists wondering why they aren't seeing the colorized ls in > their xterms. Well, then you are going to have to document this for every single color program people might want to run in an xterm. :) Seriously, educating the users on termcap will probably be a more productive way of going about this. One way of doing this might be to add a FAQ entry along the lines of "Programs such as ls(1) and sysinstall(8) don't display color in my xterm or other terminal?" -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Tue Jul 4 1:48:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orbitel.bg (ns.orbitel.bg [195.24.32.2]) by hub.freebsd.org (Postfix) with SMTP id 6CFBD37B5F4 for ; Tue, 4 Jul 2000 01:48:51 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 18425 invoked from network); 4 Jul 2000 08:48:49 -0000 Received: from penchev.staff.orbitel.bg (HELO ringwraith.oblivion.bg) (192.168.0.98) by ns.orbitel.bg with SMTP; 4 Jul 2000 08:48:49 -0000 Received: (qmail 71871 invoked by uid 1001); 4 Jul 2000 08:48:45 -0000 Date: Tue, 4 Jul 2000 11:48:45 +0300 From: Peter Pentchev To: Doug Barton Cc: John Baldwin , hackers@FreeBSD.ORG, Sean Lutner , Brian Fundakowski Feldman Subject: Re: ls -G seems to depend on TERM=xterm-color Message-ID: <20000704114845.A829@ringwraith.oblivion.bg> References: <200007040641.XAA37730@john.baldwin.cx> <39619CE9.F0D168FA@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <39619CE9.F0D168FA@gorean.org>; from DougB@gorean.org on Tue, Jul 04, 2000 at 01:14:33AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm.. how about adding this XTerm*termname: xterm-color stuff to a default Xresources file in /usr/share/skel/, or to some default Xresources file in the X directory tree itself? (I haven't messed with X resources too much, guess it shows ;) This would break xterms running on monochrome monitors; tunable via a question in sysinstall? G'luck, Pencheff ---------------------------------------------- Thit sentence is not self-referential because "thit" is not a word. On Tue, Jul 04, 2000 at 01:14:33AM -0700, Doug Barton wrote: > John Baldwin wrote: > > > >> XTerm*termName: xterm-color > > > > > > Ok, that's a good solution, I was just using .bashrc. My point is not > > > so much why, but that it be properly documented. Do you want to handle > > > the update of the ls man page, or do you want me to PR a patch? > > > > Umm, honestly, this shouldn't be all that non-obvious. Do you expect > > ls -G to work on a monochrome monitor? Of course not. :P The xterm > > termcap is by default a monochrome terminal. sysinstall doesn't have > > color in an xterm either w/ term=xterm. > > This is obvious to you and me, but to a newer user it's not going to be > obvious at all. There is going to be a bunch of people who write into > the mailing lists wondering why they aren't seeing the colorized ls in > their xterms. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 2:22:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ywing.creative.net.au (ywing.creative.net.au [203.56.168.34]) by hub.freebsd.org (Postfix) with ESMTP id 6F8CE37B607 for ; Tue, 4 Jul 2000 02:22:36 -0700 (PDT) (envelope-from adrian@ywing.creative.net.au) Received: (from adrian@localhost) by ywing.creative.net.au (8.9.3/8.9.3) id LAA72602; Tue, 4 Jul 2000 11:29:06 +0200 (CEST) (envelope-from adrian) Date: Tue, 4 Jul 2000 11:29:06 +0200 From: Adrian Chadd To: James Howard Cc: Maxime Henrion , freebsd-hackers@FreeBSD.ORG Subject: Re: why isnt there a ext2fs.ko ? Message-ID: <20000704112906.L68833@ywing.creative.net.au> References: <396085C0.15FA5203@cybercable.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from howardjp@glue.umd.edu on Mon, Jul 03, 2000 at 09:05:21AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 03, 2000, James Howard wrote: > On Mon, 3 Jul 2000, Maxime Henrion wrote: > > > Hi guys, > > > > I was wondering why the kernel module for ext2fs doesnt exist. I > > think this will be very useful because a lot of linux users come to > > FreeBSD and want to mount their existing linux partitions, and they have > > to recompile their kernel. This isn't a hard task, but it's a bit > > disappointing for new users. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=14217 > > But it doesn't seem to compile with FreeBSD-current anymore. Give me a > day or so and I will update it work with a newer FreeBSD. On this topic, > how would anyone feel about importing NetBSD's GPL-clean ext2fs source? If noone beats me to it, I'll look at it after I've committed the couple of things in my commit queue. Adrian -- Adrian Chadd Build a man a fire, and he's warm for the rest of the evening. Set a man on fire and he's warm for the rest of his life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 2:42:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 2914C37B60D for ; Tue, 4 Jul 2000 02:42:56 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id SAA00497; Mon, 3 Jul 2000 18:54:22 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007040154.SAA00497@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: KATO Takenori Cc: phk@critter.freebsd.dk, hackers@freebsd.org Subject: Re: invlpg produces strange sig11 on PentiumPro box In-reply-to: Your message of "Sat, 01 Jul 2000 22:30:41 +0900." <20000701223041W.kato@gneiss.eps.nagoya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Jul 2000 18:54:21 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Poul-Henning Kamp wrote: > > > > > If we are talking about errata #34 the correct solution is to not use > > > 4MB pages. > > > > Is FreeBSD #29-safe? > > variable MTTRs are set as follows: > MSR (200): 0000000000000006 > MSR (201): 0000000ffc000800 > MSR (202): 0000000004000006 > MSR (203): 0000000fff000800 > MSR (204): 0000000000f00000 > MSR (205): 0000000ffff00800 * > MSR (206): 0000000000000000 > MSR (207): 0000000000000000 > MSR (208): 0000000000000000 > MSR (209): 0000000000000000 > MSR (20a): 0000000000000000 > MSR (20b): 0000000000000000 > MSR (20c): 0000000000000000 > MSR (20d): 0000000000000000 > MSR (20e): 0000000000000000 > MSR (20f): 0000000000000000 > > One variable MTTR (marked *) has non-4MB aligned mask and errata #29 > affects this system. Can you look at the output of 'memcontrol list' and tell us who 'owns' this MTRR? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 2:46: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 7477C37B699; Tue, 4 Jul 2000 02:45:56 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id KAA70191; Tue, 4 Jul 2000 10:45:53 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA03271; Tue, 4 Jul 2000 09:25:45 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <200007040825.JAA03271@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Ben Smithurst Cc: James Howard , Brian Somers , freebsd-hackers@FreeBSD.org, brian@hak.lan.Awfulhak.org, freebsd-arch@FreeBSD.org Subject: Re: /etc/security -> /etc/periodic/security ? In-Reply-To: Message from Ben Smithurst of "Tue, 04 Jul 2000 00:17:16 BST." <20000704001716.A13714@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Jul 2000 09:25:45 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ x-posted to -arch to fish for complaints ] > James Howard wrote: > > > On Thu, 29 Jun 2000, Ben Smithurst wrote: > >=20 > >> Try the attached. They haven't been thoroughly tested, but that's what > >> -CURRENT is for, right? :-) I even remembered to update the manual page > >> this time... > >=20 > > This needs to have knobs and stuff located in /etc/defaults/periodic.conf > > Umm, which knobs? I added the only two options the security stuff currently > uses, what else does it need? > > > Also, it would be cool if a security option were made to periodic(8). > > Well, "periodic security" will work as long as /etc/periodic/security > exists, so I guess you just mean the docs need updating? I'll get to > that if someone is actually planning on committing this stuff. Perhaps the best option is to do with the inline security option and just run ``periodic security'' from cron ? I can commit the changes. If you send me some diffs, I'll commit them and then look at introducing {daily,weekly,monthly,security}_silence flags that will silence mails that have nothing to say. Assuming there are no objections that is.... > --=20 > Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 3:41:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 492DE37B540; Tue, 4 Jul 2000 03:41:35 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (posh.dmem.strath.ac.uk [130.159.202.3]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id LAA23540 Tue, 4 Jul 2000 11:41:32 +0100 (BST) Message-ID: <3961BF53.E6E5F8A5@cs.strath.ac.uk> Date: Tue, 04 Jul 2000 11:41:23 +0100 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: multimedia@freebsd.org, hackers@freebsd.org Subject: AverMedia TV Card owner - IR Remote Specs obtained. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've got the specs for the AverMedia IR Remote Control. I do not have any AverMedia hardware. So, I need some of you to do some simple programming and testing. And I do mean simple. No kernel drivers needed. FXTV needs a small change. Randall or myself can help. And I'll make the required change to the Bt848 driver. I've got the specs from a linux programmer who just made his code both GPL and BSD licence for us. What a nice guy. ( "Pawel T. Jochym" ) So, anyone interested in helping? Roger -- Roger Hardiman roger@freebsd.org be his sample source code under the BSD licence too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 4: 3:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 78F5337B774 for ; Tue, 4 Jul 2000 04:03:43 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id EAA02396; Tue, 4 Jul 2000 04:10:57 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007041110.EAA02396@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: bow Cc: freebsd-hackers@freebsd.org Subject: Re: Monitoring modem for dialing In-reply-to: Your message of "Mon, 03 Jul 2000 00:12:09 PDT." <20000703001208.A87793@bow.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Jul 2000 04:10:57 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, > > I was wondering if someone could point me in the right direction on how > to monitor my modem to capture dialing. > > Basically I have an extra cordless phone around the house, and I wanted > to know if it was possible to hook it into my modem and then have an > application monitor the modem for dialing, then do something depending > on what was dialed... To give an example, I'm running xmms to listen to > music. It'd be cool if I could just pick up the cordless phone, and press > the #1 key (on the phone) to jump to the next song, or the #2 key to pause. > > I haven't a clue where to start! :) > > Is it even possible? Not if you want to receive incoming calls, no. 8) -- ... 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 taks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 5:36:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 83C8737B82D; Tue, 4 Jul 2000 05:36:35 -0700 (PDT) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id VAA34522; Tue, 4 Jul 2000 21:35:59 +0900 (JST) To: msmith@freebsd.org Cc: kato@ganko.eps.nagoya-u.ac.jp, phk@critter.freebsd.dk, hackers@freebsd.org Subject: Re: invlpg produces strange sig11 on PentiumPro box From: KATO Takenori In-Reply-To: <200007040154.SAA00497@mass.osd.bsdi.com> References: <20000701223041W.kato@gneiss.eps.nagoya-u.ac.jp> <200007040154.SAA00497@mass.osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000704213558K.kato@gneiss.eps.nagoya-u.ac.jp> Date: Tue, 04 Jul 2000 21:35:58 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 105 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > Can you look at the output of 'memcontrol list' and tell us who 'owns' > this MTRR? The `memcontrol list' gives: 0/10000 BIOS write-back fixed-base fixed-length set-by-firmware active 10000/10000 BIOS write-back fixed-base fixed-length set-by-firmware active 20000/10000 BIOS write-back fixed-base fixed-length set-by-firmware active 30000/10000 BIOS write-back fixed-base fixed-length set-by-firmware active 40000/10000 BIOS write-back fixed-base fixed-length set-by-firmware active 50000/10000 BIOS write-back fixed-base fixed-length set-by-firmware active 60000/10000 BIOS write-back fixed-base fixed-length set-by-firmware active 70000/10000 BIOS write-back fixed-base fixed-length set-by-firmware active 80000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active 84000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active 88000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active 8c000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active 90000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active 94000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active 98000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active 9c000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active a0000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active a4000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active a8000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active ac000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active b0000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active b4000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active b8000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active bc000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active c0000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active c1000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active c2000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active c3000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active c4000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active c5000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active c6000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active c7000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active c8000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active c9000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active ca000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active cb000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active cc000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active cd000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active ce000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active cf000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active d0000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active d1000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active d2000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active d3000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active d4000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active d5000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active d6000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active d7000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active d8000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active d9000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active da000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active db000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active dc000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active dd000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active de000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active df000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active e0000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active e1000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active e2000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active e3000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active e4000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active e5000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active e6000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active e7000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active e8000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active e9000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active ea000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active eb000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active ec000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active ed000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active ee000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active ef000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active f0000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active f1000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active f2000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active f3000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active f4000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active f5000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active f6000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active f7000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active f8000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active f9000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fa000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fb000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fc000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fd000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fe000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active ff000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active 0/4000000 BIOS write-back set-by-firmware active 4000000/1000000 BIOS write-back set-by-firmware active f00000/100000 BIOS uncacheable set-by-firmware active -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 4.0R-Rev. 01 available! |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.4R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 7: 3:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail0.u-aizu.ac.jp (mail0.u-aizu.ac.jp [163.143.1.43]) by hub.freebsd.org (Postfix) with ESMTP id DE72D37B5A2; Tue, 4 Jul 2000 07:03:22 -0700 (PDT) (envelope-from sarikaya@u-aizu.ac.jp) Received: from pross114.u-aizu.ac.jp (pross114 [163.143.180.102]) by mail0.u-aizu.ac.jp (8.9.3+3.1W/3.7Winternet-gw) with ESMTP id XAA20556; Tue, 4 Jul 2000 23:03:20 +0900 (JST) Received: from u-aizu.ac.jp (localhost [127.0.0.1]) by pross114.u-aizu.ac.jp (8.9.3+3.1W/3.7Wistcmx+kanji) with ESMTP id XAA20021; Tue, 4 Jul 2000 23:03:19 +0900 (JST) Message-ID: <3961EEA7.6B51D3A9@u-aizu.ac.jp> Date: Tue, 04 Jul 2000 23:03:19 +0900 From: Behcet Sarikaya Organization: University of Aizu X-Mailer: Mozilla 4.7 [en_jp] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: FreeBSD 4 Question : how to get pccardd on a desktop Content-Type: multipart/alternative; boundary="------------F5CF2073766A9D6BC95F9BE0" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------F5CF2073766A9D6BC95F9BE0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, I installed FreeBSD 4.0 on a desktop that has MELCO PCI bus card for PCMCIA cards. I am having some trouble getting pccardd work on this host. MELCO card is recognized as follows (dmesg output): pcic-pci0: irq 0 at device 15.0 on pci0 But when I use rc.pccard to invoke pccardd I get /dev/card0 not defined message and pccardd doesnot start. I used GENERIC.KAME kernel configuration file that is included in kame-20000703-freebsd40-snap.tgz Thanks in advance, -- Behcet Sarikaya Computer Communications Lab. The University of Aizu Tsuruga, Ikki-machi, Aizu-wakamatsu City Fukushima, 965-8580 Japan Tel. +81-242-37-2559 Fax. +81-242-37-2742 Home page: http://www.u-aizu.ac.jp/~sarikaya/ email: sarikaya@u-aizu.ac.jp --------------F5CF2073766A9D6BC95F9BE0 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  
Hello,
    I installed FreeBSD 4.0 on a desktop that has MELCO
PCI bus card for PCMCIA cards. I am having some trouble getting pccardd work on this host.
MELCO card is recognized as follows (dmesg output):
pcic-pci0: <Ricoh RL5C475 PCI-CardBus Bridge> irq 0 at device 15.0 on pci0

But when I use rc.pccard to invoke pccardd
I get /dev/card0 not defined
message and pccardd doesnot start.
  I used GENERIC.KAME kernel configuration file that is included in kame-20000703-freebsd40-snap.tgz

Thanks in advance, 

-- 
Behcet Sarikaya
Computer Communications Lab.
The University of Aizu
Tsuruga, Ikki-machi, Aizu-wakamatsu City
Fukushima, 965-8580 Japan
Tel. +81-242-37-2559 Fax. +81-242-37-2742 
Home page:  http://www.u-aizu.ac.jp/~sarikaya/
email: sarikaya@u-aizu.ac.jp
  --------------F5CF2073766A9D6BC95F9BE0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 8:12:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 7E64037B92C for ; Tue, 4 Jul 2000 08:12:20 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 139RQW-0006ov-00; Tue, 04 Jul 2000 13:03:44 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 139RQW-000IN1-00; Tue, 04 Jul 2000 13:03:44 +0100 Date: Tue, 4 Jul 2000 13:03:43 +0100 From: Ben Smithurst To: James Howard Cc: Brian Somers , freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/security -> /etc/periodic/security ? Message-ID: <20000704130343.C13714@strontium.scientia.demon.co.uk> References: <20000704001716.A13714@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="qtZFehHsKgwS5rPz" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --qtZFehHsKgwS5rPz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable James Howard wrote: > For each script under /etc/periodic/{daily,weekly,monthly}/, there is a > knob in /etc/defaults/periodic. This controls whether the script is run > and maybe gives it some options. For instance, the daily/440.status-mailq > knobs look like this: >=20 > # 440.status-mailq > daily_status_mailq_enable=3D"YES" # Check mail status > daily_status_mailq_shorten=3D"NO" # Shorten output oh, right, ok. That should be simple enough. --=20 Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D --qtZFehHsKgwS5rPz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: 3hGhI1wk9enIERg1z6TCFkFv4KxKKQfi iQCVAwUBOWHSnysPVtiZOS99AQG9dQP/So0ZLIgnhQ8b1nt6fO37c4oqYUOutQyd cC8jqF5nEn2CnPbmM0vAQdH7KepXLAufR05mXJxJxtYzQURjNIM4dXAYIGNIXHoi TUI6RGELJMFyfyrdEFc+xy4bI6XviG5WvVe9A3+dEFJNApHtTrBrreCKP+9kf93G XWQFRRUH8/k= =rFwO -----END PGP SIGNATURE----- --qtZFehHsKgwS5rPz-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 10:16:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f260.law8.hotmail.com [216.33.240.135]) by hub.freebsd.org (Postfix) with SMTP id BE9AC37B9EC for ; Tue, 4 Jul 2000 10:16:39 -0700 (PDT) (envelope-from the_hermit665@hotmail.com) Received: (qmail 51801 invoked by uid 0); 4 Jul 2000 17:16:35 -0000 Message-ID: <20000704171635.51800.qmail@hotmail.com> Received: from 207.246.128.137 by www.hotmail.com with HTTP; Tue, 04 Jul 2000 10:16:35 PDT X-Originating-IP: [207.246.128.137] Reply-To: the_hermit665@hotmail.com From: "Cosmic 665" To: adrian@FreeBSD.ORG, howardjp@glue.umd.edu Cc: mhenrion@cybercable.fr, freebsd-hackers@FreeBSD.ORG Subject: Re: why isnt there a ext2fs.ko ? Date: Tue, 04 Jul 2000 10:16:35 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Statically Compiled modules are much better then the lkd's. Get used to it :P > > > > > Hi guys, > > > > > > I was wondering why the kernel module for ext2fs doesnt exist. I > > > think this will be very useful because a lot of linux users come to > > > FreeBSD and want to mount their existing linux partitions, and they >have > > > to recompile their kernel. This isn't a hard task, but it's a bit > > > disappointing for new users. > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=14217 > > > > But it doesn't seem to compile with FreeBSD-current anymore. Give me a > > day or so and I will update it work with a newer FreeBSD. On this >topic, > > how would anyone feel about importing NetBSD's GPL-clean ext2fs source? > >If noone beats me to it, I'll look at it after I've committed the >couple of things in my commit queue. > > > >Adrian > >-- >Adrian Chadd Build a man a fire, and he's warm for the > rest of the evening. Set a man on fire and > he's warm for the rest of his life. > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message ________________________________________________________________________ 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 Tue Jul 4 10:56: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108]) by hub.freebsd.org (Postfix) with ESMTP id F389137BD23; Tue, 4 Jul 2000 10:55:41 -0700 (PDT) (envelope-from saxonww@ufl.edu) Received: from [10.2.44.33] (gremlin@[10.2.44.33]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id NAA287580; Tue, 4 Jul 2000 13:55:38 -0400 Date: Tue, 4 Jul 2000 13:59:35 -0400 (EDT) From: Will Saxon X-Sender: gremlin@thundarr.dhnet.ufl.edu To: Roger Hardiman Cc: multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: AverMedia TV Card owner - IR Remote Specs obtained. In-Reply-To: <3961BF53.E6E5F8A5@cs.strath.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 I'll be more than happy to help out. Just let me know what I need to do. -Will On Tue, 4 Jul 2000, Roger Hardiman wrote: > Hi, > I've got the specs for the AverMedia IR Remote Control. > > I do not have any AverMedia hardware. > So, I need some of you to do some simple programming > and testing. And I do mean simple. No kernel drivers needed. > > FXTV needs a small change. Randall or myself can help. > And I'll make the required change to the Bt848 driver. > > > I've got the specs from a linux programmer who just > made his code both GPL and BSD licence for us. > What a nice guy. ( "Pawel T. Jochym" ) > > > So, anyone interested in helping? > > Roger > -- > Roger Hardiman > roger@freebsd.org > be his sample source code under the BSD licence too. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-multimedia" 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 Jul 4 12:27:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.comint.net (main.comint.net [213.154.192.70]) by hub.freebsd.org (Postfix) with ESMTP id 3769A37BA3E for ; Tue, 4 Jul 2000 12:27:22 -0700 (PDT) (envelope-from av@ukr.net) Received: from unixbox.anna.com (dialup-z7.comint.net [213.154.192.135]) by relay.comint.net (8.9.1a/8.9.1) with SMTP id WAA19823 for ; Tue, 4 Jul 2000 22:27:25 +0300 From: "Alexey V. Vatchenko" To: freebsd-hackers@freebsd.org Subject: fsck Date: Tue, 4 Jul 2000 22:27:53 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00070422315500.00285@unixbox.anna.com> Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi guys i was experementing with writing kernel modules and my kernel panic and my filesystems too. when i fsck it tells me ** /dev/ad0s2a (NO WRITE) ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 2902 files, 45030 used, 4553 free (41 frags, 564 blocks, 0.1% fragmentation) and fsck -p /dev/ad0s2a: NO WRITE ACCESS /dev/ad0s2a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. what is it? -av To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 13:30:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id C05E837BC8E; Tue, 4 Jul 2000 13:30:28 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 139RUO-0006p8-00; Tue, 04 Jul 2000 13:07:44 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 139RUO-000Jjj-00; Tue, 04 Jul 2000 13:07:44 +0100 Date: Tue, 4 Jul 2000 13:07:44 +0100 From: Ben Smithurst To: Brian Somers Cc: James Howard , freebsd-hackers@FreeBSD.org, brian@hak.lan.Awfulhak.org, freebsd-arch@FreeBSD.org Subject: Re: /etc/security -> /etc/periodic/security ? Message-ID: <20000704130744.D13714@strontium.scientia.demon.co.uk> References: <200007040825.JAA03271@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="pQhZXvAqiZgbeUkD" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007040825.JAA03271@hak.lan.Awfulhak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --pQhZXvAqiZgbeUkD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Brian Somers wrote: >> Well, "periodic security" will work as long as /etc/periodic/security >> exists, so I guess you just mean the docs need updating? I'll get to >> that if someone is actually planning on committing this stuff. >=20 > Perhaps the best option is to do with the inline security option and=20 > just run ``periodic security'' from cron ? I can commit the changes. I don't think there's really a problem with just running security from daily. I can add a note that this is normal practice in the manpage, and that security shouldn't be run separately unless you set daily_security_enable=3DNO or whatever the option is. --=20 Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D --pQhZXvAqiZgbeUkD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: L2wKgXBd+m0yOO7lHvlBgD76Q3qlfpTM iQCVAwUBOWHTkCsPVtiZOS99AQEJZgP+Ly9fbYQFFKE5Qj+2N2L6I3+1SB5YMA9p dCwXX79Cz8sMHmxVqcm/w6dfvZ34RAZK6HkHZwlixnSXHV2BtxbDD7Uv3p09IbT/ t03D4/chMF2i6w2qbHv/ZzN9LgC51vKA1CHhQ3rnwdQH2OAeyO9QKRFO5XP9E/Jh cCloESlI9/E= =yZ+B -----END PGP SIGNATURE----- --pQhZXvAqiZgbeUkD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 13:38:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 801DF37BB0A for ; Tue, 4 Jul 2000 13:38:52 -0700 (PDT) (envelope-from ccristi@rice.edu) Received: from rice.edu (swba-176-228.rice.edu [128.42.176.228]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id PAA22349 for ; Tue, 4 Jul 2000 15:38:41 -0500 (CDT) Message-ID: <39624B26.7D1F98F6@rice.edu> Date: Tue, 04 Jul 2000 15:37:58 -0500 From: Cristian Coarfa X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: profiling tools for Intel Machines Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Are there any tools for FreeBSD on Intel machines for whole system profiling ? kgmon profiles only the kernel, and GPROF does not provide profiling for multiprocess applications (e.g. a multiprocess web server). Thank you, Cristian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 13:48:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id C549C37B849 for ; Tue, 4 Jul 2000 13:48:23 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA05278; Tue, 4 Jul 2000 13:55:41 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007042055.NAA05278@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Silbersack Cc: hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box In-reply-to: Your message of "Tue, 04 Jul 2000 00:49:27 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Jul 2000 13:55:41 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > If it's something that can be done as eg. a KLD > > > > we might want to do that instead, or through some other mechanism for > > > > handling these sort of CPU quirks. > > > > > > It sounds good. If binary-format quriks is supported, we can supply > > > update modules for new CPU and newly found errata like the update > > > module for AMD K6-2 CPU of Windows 95. > > > > Indeed. This won't help us where we need to modify the actual behaviour > > of a system component, but when we can perform external corrective > > actions, it will help a lot. > > I don't understand the idea here. Are you going to have a KLD that > patches the kernel? That's the general idea. > If so, you'd have to make world before it'd become > active, in which case rebuilding the kernel would be quicker. How so? Especially if it's required for the kernel to work at all, it's already built and waiting on the distribution media so that you can just load-and-go. -- ... 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 taks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 13:53:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0E18E37BB2C; Tue, 4 Jul 2000 13:53:36 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA06172; Tue, 4 Jul 2000 13:53:36 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 4 Jul 2000 13:53:35 -0700 (PDT) From: Kris Kennaway To: Nick Rogness Cc: Stephen Hocking , hackers@freebsd.org Subject: Re: VPNs and FreeBSD 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, 2 Jul 2000, Nick Rogness wrote: > On Sun, 2 Jul 2000, Stephen Hocking wrote: > > > Has anyone done this yet? I've just acquired this shiny new cable modem and > > would like to have secure access to my place of work (even though they're only > > 10 minutes walk away!) > > I have done just that with nos-tun and Road Runner service. I That's a Virtual Public Network, then..better not log into your work machines via telnet over that link :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 14:49:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id B1D1737BB37; Tue, 4 Jul 2000 14:49:23 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-117-132.nnj.dialup.bellatlantic.net [151.198.117.132]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id RAA07445; Tue, 4 Jul 2000 17:49:17 -0400 (EDT) Message-ID: <39625C24.5D49AF08@bellatlantic.net> Date: Tue, 04 Jul 2000 17:50:28 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Nat Lanza Cc: Mike Smith , scsi@freebsd.org, hackers@freebsd.org Subject: Re: SCSI HBA device detection? References: <200007040146.SAA00380@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nat Lanza wrote: > > Mike Smith writes: > > > If this is meant to be an exercise in writing a CAM HBA driver, then you > > need to teach your disk-emulation code about the basic SCSI commands > > (INQUIRY, TEST UNIT READY, etc). The SCSI infrastructure will use these > > commands to automatically detect your drives. > > I already have code for handling the basic SCSI commands (I'm really > porting a scsi-ramdisk driver from Linux rather than writing from > scratch). The bit I'm curious about are which XPT actions I'll need to > support other than XPT_PATH_INQ and XPT_SCSI_IO. The tutorial in DaemonNews has this information, as well as information on minimal implementations of the reqired actions. Obviously the actions for SCSI negotiations don't need to be supported because these negotiations make no sense for an emulator or over IP. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 15:11:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E1E3437B938; Tue, 4 Jul 2000 15:11:20 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA05459; Tue, 4 Jul 2000 15:11:07 -0700 Date: Tue, 4 Jul 2000 15:11:07 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Sergey Babkin Cc: Nat Lanza , Mike Smith , scsi@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: SCSI HBA device detection? In-Reply-To: <39625C24.5D49AF08@bellatlantic.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 > > The tutorial in DaemonNews has this information, as well as information > on minimal implementations of the reqired actions. Obviously the actions > for SCSI negotiations don't need to be supported because these > negotiations make no sense for an emulator or over IP. > Or over Fibre Channel (which the DaemonNews article completely missed) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 16:18: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id EF8EB37B5C3; Tue, 4 Jul 2000 16:17:54 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id QAA03672; Tue, 4 Jul 2000 16:17:53 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <396270A1.8DDAC6FE@gorean.org> Date: Tue, 04 Jul 2000 16:17:53 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0702 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: Brian Fundakowski Feldman , Sean Lutner , hackers@FreeBSD.ORG, Sheldon Hearn Subject: Re: ls -G seems to depend on TERM=xterm-color References: <200007040841.BAA40774@john.baldwin.cx> Content-Type: multipart/mixed; boundary="------------E30BF601732EE42E16CCED76" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------E30BF601732EE42E16CCED76 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit John Baldwin wrote: > > On 04-Jul-00 Doug Barton wrote: > > John Baldwin wrote: > > > >> >> XTerm*termName: xterm-color > >> > > >> > Ok, that's a good solution, I was just using .bashrc. My point is not > >> > so much why, but that it be properly documented. Do you want to handle > >> > the update of the ls man page, or do you want me to PR a patch? > >> > >> Umm, honestly, this shouldn't be all that non-obvious. Do you expect > >> ls -G to work on a monochrome monitor? Of course not. :P The xterm > >> termcap is by default a monochrome terminal. sysinstall doesn't have > >> color in an xterm either w/ term=xterm. > > > > This is obvious to you and me, but to a newer user it's not going to be > > obvious at all. There is going to be a bunch of people who write into > > the mailing lists wondering why they aren't seeing the colorized ls in > > their xterms. > > Well, then you are going to have to document this for every single color > program people might want to run in an xterm. :) And the problem with that would be what, exactly? > Seriously, educating the > users on termcap will probably be a more productive way of going about this. > One way of doing this might be to add a FAQ entry along the lines of > "Programs such as ls(1) and sysinstall(8) don't display color in my xterm > or other terminal?" I agree that user education is a noble goal, and if you didn't already realize it, one that I have supported with my own efforts for a long time. However, I can see the "writing on the wall" regarding user confusion over the color ls issue. This _specific_ feature has been often requested by users on -questions, most of whom (dare I say it?) are recent linux converts. Therefore, with this _specific_ feature it will pay off more in both the long and short terms if we put the cookies down a few shelves to start with, and add an enticement for them to eat some meat and potatoes when they are ready. So, I've put my time where my mouth is and produced the attached patch for ls.1. I am 100% open to modifications of both style and content, my only request being that someone commit _something_ before 4.1 goes out the door. Since Andrey MFC'ed the color bits already (a welcome move, don't get me wrong) there is slightly more urgency to this matter then there was previously. John, when your FAQ entry is done, please feel free to add it to the SEE ALSO section of ls.1. :) Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? --------------E30BF601732EE42E16CCED76 Content-Type: text/plain; charset=us-ascii; name="ls.1.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ls.1.diff" Index: ls.1 =================================================================== RCS file: /usr/ncvs/src/bin/ls/ls.1,v retrieving revision 1.38 diff -u -r1.38 ls.1 --- ls.1 2000/06/22 10:07:46 1.38 +++ ls.1 2000/07/04 22:56:57 @@ -100,6 +100,20 @@ In addition to those mentioned above in .Fl F , some extra attributes (setuid bit set, etc.) are also displayed. +The colorization is dependent on a terminal type with the proper +.Xr termcap 5 +capabilities. +The default +.Dq cons25 +console has the proper capabilities, +however if you want to display the colors in an +.Xr xterm 1 +for example, +you need to set your +.Ev TERM +variable to +.Dq xterm-color . +Other terminal types may require similar adjustments. .It Fl H Symbolic links on the command line are followed. This option is assumed if none of the @@ -478,6 +492,10 @@ columns have changeable widths. The fields are, in order: inode, block count, number of links, user name, group name, flags, file size, file name. +.It Ev TERM +The +.Fl G +option depends on a terminal type with color capabilities. .It Ev TZ The timezone to use when displaying dates. See @@ -492,6 +510,8 @@ .Sh SEE ALSO .Xr chflags 1 , .Xr chmod 1 , +.Xr xterm 1 , +.Xr termcap 5 , .Xr symlink 7 , .Xr sticky 8 .Sh HISTORY --------------E30BF601732EE42E16CCED76-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 16:19:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 0327437B7EF; Tue, 4 Jul 2000 16:19:40 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-117-132.nnj.dialup.bellatlantic.net [151.198.117.132]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id TAA09479; Tue, 4 Jul 2000 19:19:27 -0400 (EDT) Message-ID: <39627146.6110151A@bellatlantic.net> Date: Tue, 04 Jul 2000 19:20:38 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: mjacob@feral.com Cc: Nat Lanza , Mike Smith , scsi@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: SCSI HBA device detection? References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > > > > The tutorial in DaemonNews has this information, as well as information > > on minimal implementations of the reqired actions. Obviously the actions > > for SCSI negotiations don't need to be supported because these > > negotiations make no sense for an emulator or over IP. > > > > Or over Fibre Channel (which the DaemonNews article completely missed) Well, I concentrated on the CAM side of interface. The underlying hardware is one of device-dependent parts. BTW, I looked up the list of of absolutely neccessary calls for simulated SCSI: XPT_SCSI_IO XPT_RESET_BUS (at least silently return success) XPT_ABORT (at least return CAM_UA_ABORT) XPT_CALC_GEOMETRY XPT_PATH_INQ -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 16:28: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 807FF37B77E; Tue, 4 Jul 2000 16:27:07 -0700 (PDT) (envelope-from joe@pavilion.net) Received: from genius.systems.pavilion.net (genesis.tao.org.uk [194.242.131.254]) by florence.pavilion.net (8.9.3/8.8.8) with ESMTP id AAA13885; Wed, 5 Jul 2000 00:27:02 +0100 (BST) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id D113312735; Wed, 5 Jul 2000 00:28:55 +0100 (BST) Date: Wed, 5 Jul 2000 00:28:55 +0100 From: Josef Karthauser To: Doug Barton Cc: John Baldwin , Brian Fundakowski Feldman , Sean Lutner , hackers@FreeBSD.ORG, Sheldon Hearn Subject: Re: ls -G seems to depend on TERM=xterm-color Message-ID: <20000705002855.F26614@pavilion.net> References: <200007040841.BAA40774@john.baldwin.cx> <396270A1.8DDAC6FE@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <396270A1.8DDAC6FE@gorean.org>; from DougB@gorean.org on Tue, Jul 04, 2000 at 04:17:53PM -0700 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 04, 2000 at 04:17:53PM -0700, Doug Barton wrote: > > So, I've put my time where my mouth is and produced the attached patch > for ls.1. I am 100% open to modifications of both style and content, my > only request being that someone commit _something_ before 4.1 goes out > the door. Since Andrey MFC'ed the color bits already (a welcome move, > don't get me wrong) there is slightly more urgency to this matter then > there was previously. John, when your FAQ entry is done, please feel > free to add it to the SEE ALSO section of ls.1. :) I agree with the bit about needing proper termcap capablities, I almost added something like this myself earlier today. It's overkill to talk about xterm in the man page though. This should be in an FAQ entry or in the hand book IMO. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 21:40:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from po4.glue.umd.edu (po4.glue.umd.edu [128.8.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 7068D37B5C8; Tue, 4 Jul 2000 21:40:38 -0700 (PDT) (envelope-from howardjp@glue.umd.edu) Received: from z.glue.umd.edu (root@z.glue.umd.edu [128.8.10.71]) by po4.glue.umd.edu (8.10.1/8.10.1) with ESMTP id e654eYW16748; Wed, 5 Jul 2000 00:40:35 -0400 (EDT) Received: from z.glue.umd.edu (sendmail@localhost [127.0.0.1]) by z.glue.umd.edu (8.9.3/8.9.3) with SMTP id AAA25968; Wed, 5 Jul 2000 00:40:34 -0400 (EDT) Received: from localhost (howardjp@localhost) by z.glue.umd.edu (8.9.3/8.9.3) with ESMTP id AAA25964; Wed, 5 Jul 2000 00:40:34 -0400 (EDT) X-Authentication-Warning: z.glue.umd.edu: howardjp owned process doing -bs Date: Wed, 5 Jul 2000 00:40:34 -0400 (EDT) From: James Howard To: Cosmic 665 Cc: adrian@FreeBSD.ORG, mhenrion@cybercable.fr, freebsd-hackers@FreeBSD.ORG Subject: Re: why isnt there a ext2fs.ko ? In-Reply-To: <20000704171635.51800.qmail@hotmail.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, 4 Jul 2000, Cosmic 665 wrote: > > Statically Compiled modules are much better then the lkd's. Get used to it > :P But I only need EXT2FS support once everyone few months. It makes no sense to have it eating kernel memory 100% of the time. Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 4 21:54:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id 5B2DC37B5C8 for ; Tue, 4 Jul 2000 21:54:28 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 70718 invoked by uid 1000); 5 Jul 2000 04:54:26 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Jul 2000 04:54:26 -0000 Date: Tue, 4 Jul 2000 23:54:26 -0500 (CDT) From: Mike Silbersack To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: invlpg produces strange sig11 on PentiumPro box In-Reply-To: <200007042055.NAA05278@mass.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 On Tue, 4 Jul 2000, Mike Smith wrote: > > I don't understand the idea here. Are you going to have a KLD that > > patches the kernel? > > That's the general idea. > > > If so, you'd have to make world before it'd become > > active, in which case rebuilding the kernel would be quicker. > > How so? Especially if it's required for the kernel to work at all, it's > already built and waiting on the distribution media so that you can just > load-and-go. I can't think of a single situation where you wouldn't want your processor directly supported in the kernel w/o external KLDs. I'm of the impression that patching KLDs would just become ignored over time, not being properly updated as needed. 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 Wed Jul 5 6:47:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id DBE4237B8CD; Wed, 5 Jul 2000 06:47:44 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id HAA33009; Wed, 5 Jul 2000 07:47:38 -0600 (MDT) Date: Wed, 5 Jul 2000 07:47:38 -0600 (MDT) From: Nick Rogness To: Kris Kennaway Cc: Stephen Hocking , hackers@freebsd.org Subject: Re: VPNs and FreeBSD 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 Tue, 4 Jul 2000, Kris Kennaway wrote: > On Sun, 2 Jul 2000, Nick Rogness wrote: > > > On Sun, 2 Jul 2000, Stephen Hocking wrote: > > > > > Has anyone done this yet? I've just acquired this shiny new cable modem and > > > would like to have secure access to my place of work (even though they're only > > > 10 minutes walk away!) > > > > I have done just that with nos-tun and Road Runner service. I > > That's a Virtual Public Network, then..better not log into your work > machines via telnet over that link :-) No, I don't. SSH or die ;-) Yes, that is my definition a VPN tunnel. Encryption should be added after the tunnel's are built, IMHO, and are a added functionality of your existing VPN. That's just my opinion...however, Cisco implements it the same way. Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 7:31:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.comint.net (main.comint.net [213.154.192.70]) by hub.freebsd.org (Postfix) with ESMTP id AD09737B578 for ; Wed, 5 Jul 2000 07:31:21 -0700 (PDT) (envelope-from av@ukr.net) Received: from unixbox.anna.com (dialup-z42.comint.net [213.154.192.170]) by relay.comint.net (8.9.1a/8.9.1) with SMTP id RAA00919 for ; Wed, 5 Jul 2000 17:31:09 +0300 From: "Alexey V. Vatchenko" To: freebsd-hackers@freebsd.org Subject: lock in kernel Date: Wed, 5 Jul 2000 17:34:05 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00070517352800.00257@unixbox.anna.com> Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all inside kernel (in my syscall) i need to lock some data sturctures. how can i do it? -av To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 7:45:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id CBBEA37B95F for ; Wed, 5 Jul 2000 07:45:38 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id VAA77583 for ; Wed, 5 Jul 2000 21:45:35 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 5 Jul 2000 21:45:35 +0700 (NSS) From: Max Khon To: hackers@freebsd.org Subject: latest news concerned crypto stuff 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, there! do the latest news concerned crypto stuff mean that we can now always have DES in base system? and what's about a possibility to select Crypt Format (DES/MD5/SHA/whatever) per user or per login class? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 8: 3:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from oskar.dev.nanoteq.co.za (oskar.dev.nanoteq.co.za [196.7.114.5]) by hub.freebsd.org (Postfix) with ESMTP id 3B76237BEAB for ; Wed, 5 Jul 2000 08:03:25 -0700 (PDT) (envelope-from rbezuide@oskar.dev.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id RAA27771 for freebsd-hackers@freebsd.org; Wed, 5 Jul 2000 17:04:59 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <200007051504.RAA27771@oskar.dev.nanoteq.co.za> Subject: NATD errors on 5.0 To: freebsd-hackers@freebsd.org Date: Wed, 5 Jul 2000 17:04:59 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] 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 Hi ... I've started natd on my local machine to translate all packets to the ip of my public interface. If I am on my machine, and I start natd and add the divert rule, (this means I'm trying to connect from my local machine on which I am running the natd to any other machine) I can see the packet leaving my machine, ariving at the destination machine, but NO reply returned, if I ping .. everything seems ok .... Any ideas what is wrong ??? Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 9:22:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 54B9D37B596 for ; Wed, 5 Jul 2000 09:22:30 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id SAA59914; Wed, 5 Jul 2000 18:22:19 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Date: Wed, 5 Jul 2000 18:22:19 +0200 (EET) From: Narvi To: Steve Kargl Cc: Daniel Eischen , freebsd-hackers@FreeBSD.ORG Subject: Re: Default (x86) floating point precision In-Reply-To: <200006271525.IAA59630@troutmask.apl.washington.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 Tue, 27 Jun 2000, Steve Kargl wrote: > Daniel Eischen wrote: > > > > Oddly, this causes problems with GNAT (Ada is a high level language) > > because it wants/expects 64-bit extended precision. It seems as if > > GNAT for linux-i386 also uses 64-bit extended precision. The only > > other GNAT i386 platform that doesn't use 64-bit precision is NT. > > > > So is the above comment still valid? > > > > Does GNAT use the math library in /usr/lib? I've been testing > our math library against UCBTEST, and there appear to be some > pecularities. I need to dig deeper to understand all the info > produced by UCBTEST. The point of this note is that turning on > 64-bit extended precision in GNAT might be compromised by libm.a. > Well, some things can easily depend on there being no double rounding to get the correct results. > -- > Steve > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 11: 1: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id 69E6037BC2D; Wed, 5 Jul 2000 11:01:04 -0700 (PDT) (envelope-from dmiller@search.sparks.net) Received: by search.sparks.net (Postfix, from userid 100) id 2B757DB05; Wed, 5 Jul 2000 13:56:10 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id 2067ADAFE; Wed, 5 Jul 2000 13:56:10 -0400 (EDT) Date: Wed, 5 Jul 2000 13:56:10 -0400 (EDT) From: David Miller To: Soren Schmidt Cc: Julian Elischer , Coleman Kane , hackers@FreeBSD.org, multimedia@FreeBSD.org Subject: Re: UDF (DVD fs) In-Reply-To: <200007021009.MAA17928@freebsd.dk> 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, 2 Jul 2000, Soren Schmidt wrote: > It seems Julian Elischer wrote: > > I am working on UDF support. > > I have at present a program that reads a udf filesystem > > and am working (today) on making it into an "mtools" like > > program that allows access to the contents in a useful manner. > > > > I will eventually turn this into a (readonly) filesystem, and it > > is designed with that in mind (it uses a buffer cache etc, like > > the kernel. (in other words I'm prototyping). > > > > I will at some stage also try make a UDF creation module for mkisofs > > as well. > > Uhm, the real value of UDF is that it can be used as a "real" rw > filesystem on CDRW/DVDRAM media, if this is not implemented the > value of having UDF is very limited IMHO.... Another value of UDF is interoperability with the redmond virii which don't recognize 2.2 GB 9660 file systems. I have to duplicate 4.x GB of mpeg2 files onto 30+ copies of DVD-ram, and being able to do it as UDF instead of having to format UDF on an NT box and copying the files before duping a disk image would save me at least one headache:) --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 11: 4:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fep03-svc.mail.telepac.pt (fep03-svc.mail.telepac.pt [194.65.5.202]) by hub.freebsd.org (Postfix) with ESMTP id E0D0037BB06 for ; Wed, 5 Jul 2000 11:04:31 -0700 (PDT) (envelope-from miltonmoura@mail.telepac.pt) Received: from ekstassy.com ([194.65.187.245]) by fep03-svc.mail.telepac.pt (InterMail vM.4.01.02.27 201-229-119-110) with SMTP id <20000705180826.MWMT18202.fep03-svc.mail.telepac.pt@ekstassy.com> for ; Wed, 5 Jul 2000 19:08:26 +0100 From: milton moura Reply-To: miltonmoura@mail.telepac.pt Organization: universidade dos acores To: freebsd-hackers@freebsd.org Subject: i4b: PCBIT PCI card support Date: Wed, 5 Jul 2000 17:45:23 +0000 X-Mailer: KMail [version 1.0.29] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00070518031400.07491@ekstassy.com> Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there. I have been a Linux user for about 2 years now and I use it mainly at hom= e on my desktop computer to do all the usual stuff Iike programming, office work, whatever comes handy. Until some time ago I had a regular modem dial-up connection to my ISP, w= hich was recently upgraded to a ISDN 64k connection. Along with the ISP ISDN Pack I purchased came a PCBIT PCI TigerJet Tiger3= 00 ISDN card which works perfectly under Linux with ippp and the HiSAX modul= e (loaded with these settings: insmod hisax type=3D20 protocol=3D2 id=3D"Hi= Sax"). Just out of pure curiosity, I ordered FreeBSD-4.0 from freebsdmall a coup= le of weeks ago and it arrived earlier this week. After installing, reading the docs and lots of other stuff, I came to the= sad conclusion that i4b does not support my ISDN card. I have tried to change some of the TELES card settings to see if they wou= ld pick up on my card (since they both rely on the SIEMENS chip) but to no a= vail. Does any one know if there is a "working" patch for i4b with support for = my card? if not, can you point me to some basic procedure to try and write a driver for the card? Any and all help is appreciated :) thanks in advance. - ekstassy^/dev/null (c) Milton Moura @ && IT Student & Gifted Borderline Genius IQ of 135 Homepage:=09http://members.xoom.com/miltonmoura/ GITux Project:=09http://linus.uac.pt/~milton_m/ -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s: a--- C++ UL+++ 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+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 11:16:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id EC2B237B9C6 for ; Wed, 5 Jul 2000 11:16:43 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id LAA72883 for ; Wed, 5 Jul 2000 11:16:38 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id LAA21805 for hackers@freebsd.org; Wed, 5 Jul 2000 11:16:38 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <200007051816.LAA21805@realtime.exit.com> Subject: SB Live! versus -stable. To: hackers@freebsd.org Date: Wed, 5 Jul 2000 11:16:38 -0700 (PDT) Reply-To: frank@exit.com Organization: Exit Consulting X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM962820998-21791-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM962820998-21791-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit I sent this to stable, to a deafening silence. I'm therefore forwarding it to hackers as well. Well, I had three panics from this today (the first was accidental when I went to a webpage with music attached; the other two were me trying to get a good dump). I got some info from the dump. The most relevant bits are that the NMI was at IP 0x280f819a, which isn't in the kernel. I don't know where this might be, a shared library maybe? (I was running the Linux Netscape 4.73, if that might help.) I've attached a disassembly around the faulting instruction, as well as some other info gleaned from the dump. Cameron, et al, if you want any other info, please let me know; I'll hang on to the dump as long as necessary (when you have 36 gig, space isn't a real problem :-). -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://store.exit.com/ --ELM962820998-21791-0_ Content-Type: text/plain; charset=US-ASCII Content-Disposition: attachment; filename=assem Content-Description: assem Content-Transfer-Encoding: 7bit (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:302 #1 0xc01612f5 in panic ( fmt=0xc02a1660 "RAM parity error, likely hardware failure.") at ../../kern/kern_shutdown.c:552 #2 0xc0267e8d in isa_nmi (cd=0) at ../../i386/isa/intr_machdep.c:187 #3 0xc025f42f in trap (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 147577152, tf_esi = 135760192, tf_ebp = -1077937456, tf_isp = -656769068, tf_ebx = 262144, tf_edx = 135729216, tf_ecx = 254400, tf_eax = 11816960, tf_trapno = 19, tf_err = 0, tf_eip = 672104858, tf_cs = 31, tf_eflags = 66054, tf_esp = -1077937560, tf_ss = 47}) at ../../i386/i386/trap.c:379 #4 0x280f819a in ?? () #5 0x8051b67 in ?? () #6 0x8054d3a in ?? () #7 0x8054e09 in ?? () #8 0x804a2cf in ?? () #9 0x80495c5 in ?? () (kgdb) print /x frame $1 = {tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x8cbd940, tf_esi = 0x8178940, tf_ebp = 0xbfbffad0, tf_isp = 0xd8da7fd4, tf_ebx = 0x40000, tf_edx = 0x8171040, tf_ecx = 0x3e1c0, tf_eax = 0xb45000, tf_trapno = 0x13, tf_err = 0x0, tf_eip = 0x280f819a, tf_cs = 0x1f, tf_eflags = 0x10206, tf_esp = 0xbfbffa68, tf_ss = 0x2f} 0x280f8148: andb $0x4e,%al 0x280f814a: je 0x280f818f 0x280f814d: pushl %ebx 0x280f814e: incl %esp 0x280f814f: cmpb (%eax),%ah 0x280f8151: boundl 0x6f(%ebx),%esp 0x280f8154: jo 0x280f81cf 0x280f8156: pushl %ebx 0x280f8158: subb $0x76,%al 0x280f815a: andb %dh,(%ecx) 0x280f815c: andb %dh,%cs:%ss:(%ecx) 0x280f8160: cmpl %edi,(%ecx) 0x280f8162: das 0x280f8164: xorl %esi,(%ecx) 0x280f8166: das 0x280f8167: xorl %esi,(%edx) 0x280f8169: andb %dh,(%eax) 0x280f816b: xorb %bh,(%edx) 0x280f816d: xorl $0x36303a30,%eax 0x280f8172: andb %ch,0x74(%edx) 0x280f8175: arpl %sp,(%eax) 0x280f8177: incl %ebp 0x280f8178: js 0x280f81ea 0x280f817a: andb %ah,(%eax,%eax,1) 0x280f817d: leal 0x0(%esi),%esi 0x280f8180: pushl %esi 0x280f8181: pushl %edi 0x280f8182: movl 0xc(%esp,1),%edi 0x280f8186: movl 0x10(%esp,1),%esi 0x280f818a: movl 0x14(%esp,1),%ecx 0x280f818e: movl %edi,%eax 0x280f8190: subl %esi,%eax 0x280f8192: cmpl %ecx,%eax 0x280f8194: jb 0x280f81ac 0x280f8196: cld 0x280f8197: shrl $0x2,%ecx 0x280f819a: repz movsl %ds:(%esi),%es:(%edi) <-- Faulting instruction. 0x280f819c: movl 0x14(%esp,1),%ecx 0x280f81a0: andl $0x3,%ecx 0x280f81a3: repz movsb %ds:(%esi),%es:(%edi) 0x280f81a5: movl 0xc(%esp,1),%eax 0x280f81a9: popl %edi 0x280f81aa: popl %esi 0x280f81ab: ret (kgdb) proc 373 (kgdb) bt #0 mi_switch () at machine/globals.h:119 #1 0xc0163f91 in tsleep (ident=0xc030206c, priority=280, wmesg=0xc02819e8 "select", timo=8640001) at ../../kern/kern_synch.c:467 #2 0xc016ed28 in select (p=0xd8dd5740, uap=0xd8e18edc) at ../../kern/sys_generic.c:702 #3 0xc22393dc in ?? () #4 0xc22392bb in ?? () #5 0xc0260055 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 146812732, tf_esi = -1077944272, tf_ebp = 1342250056, tf_isp = -656306220, tf_ebx = 1342250064, tf_edx = 1342250600, tf_ecx = 148557768, tf_eax = 82, tf_trapno = 12, tf_err = 2, tf_eip = 143784734, tf_cs = 31, tf_eflags = 582, tf_esp = 1342250052, tf_ss = 47}) at ../../i386/i386/trap.c:1126 #6 0xc024d7fc in Xint0x80_syscall () #7 0x891e5a4 in ?? () #8 0x891e7a8 in ?? () #9 0x891cd68 in ?? () #10 0x891cda7 in ?? () #11 0x891ce14 in ?? () (kgdb) frame 2 #2 0xc016ed28 in select (p=0xd8dd5740, uap=0xd8e18edc) at ../../kern/sys_generic.c:702 702 error = tsleep((caddr_t)&selwait, PSOCK | PCATCH, "select", timo); (kgdb) print /x *p $2 = {p_procq = {tqe_next = 0xd65e9780, tqe_prev = 0xd65e8dc0}, p_list = { le_next = 0xd8dd55a0, le_prev = 0xd8dd5268}, p_cred = 0xc2020ee0, p_fd = 0xc2294400, p_stats = 0xd8e17b78, p_limit = 0xc2297f00, p_upages_obj = 0xd8e0f1e0, p_procsig = 0xc20d1740, p_flag = 0x4086, p_stat = 0x3, p_pad1 = {0x0, 0x0, 0x0}, p_pid = 0x175, p_hash = { le_next = 0x0, le_prev = 0xc1e475d4}, p_pglist = {le_next = 0xd8dd5a80, le_prev = 0xd8dd4dbc}, p_pptr = 0xd8dd55a0, p_sibling = {le_next = 0x0, le_prev = 0xd8dd4dc8}, p_children = {lh_first = 0x0}, p_ithandle = { callout = 0x0}, p_oppid = 0x0, p_dupfd = 0x0, p_vmspace = 0xd8dfba00, p_estcpu = 0x4, p_cpticks = 0x0, p_pctcpu = 0x0, p_wchan = 0xc030206c, p_wmesg = 0xc02819e8, p_swtime = 0xbe, p_slptime = 0x1, p_realtimer = { it_interval = {tv_sec = 0x0, tv_usec = 0x0}, it_value = {tv_sec = 0x0, tv_usec = 0x0}}, p_runtime = 0x1ac26, p_uu = 0x0, p_su = 0x0, p_iu = 0x0, p_uticks = 0x2, p_sticks = 0x6, p_iticks = 0x0, p_traceflag = 0x0, p_tracep = 0x0, p_siglist = {__bits = {0x0, 0x0, 0x0, 0x0}}, p_textvp = 0xd8df27c0, p_lock = 0x0, p_oncpu = 0xff, p_lastcpu = 0x1, p_rqindex = 0x8, p_locks = 0x0, p_simple_locks = 0x0, p_stops = 0x0, p_stype = 0x0, p_step = 0x0, p_pfsflags = 0x0, p_pad3 = {0x0, 0x0}, p_retval = {0x0, 0x50011e68}, p_sigiolst = {slh_first = 0x0}, p_sigparent = 0x14, p_oldsigmask = {__bits = {0x0, 0x0, 0x0, 0x0}}, p_sig = 0x0, p_code = 0x0, p_klist = {slh_first = 0x0}, p_sigmask = { __bits = {0x2000, 0x0, 0x0, 0x0}}, p_sigstk = {ss_sp = 0x0, ss_size = 0x0, ss_flags = 0x4}, p_priority = 0x18, p_usrpri = 0x32, p_nice = 0x0, p_comm = {0x6e, 0x65, 0x74, 0x73, 0x63, 0x61, 0x70, 0x65, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, p_pgrp = 0xc2020980, p_sysent = 0xc223fce0, p_rtprio = {type = 0x1, prio = 0x0}, p_prison = 0x0, p_args = 0xc2020e60, p_addr = 0xd8e17000, p_md = {md_regs = 0xd8e18fa8}, p_xstat = 0x0, p_acflag = 0x0, p_ru = 0x0, p_nthreads = 0x0, p_aioinfo = 0x0, p_wakeup = 0x0, p_peers = 0x0, p_leader = 0xd8dd5740, p_asleep = { as_priority = 0x0, as_timo = 0x0}, p_emuldata = 0x0} --ELM962820998-21791-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 11:37:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id 2537737BFE7 for ; Wed, 5 Jul 2000 11:37:14 -0700 (PDT) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with ESMTP id LAA05568 for ; Wed, 5 Jul 2000 11:36:58 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id LAA13785 for ; Wed, 5 Jul 2000 11:36:58 -0700 (MST) X-Envelope-To: X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id OAA27793; Wed, 5 Jul 2000 14:36:57 -0400 (EDT) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14691.32841.451545.132176@hip186.ch.intel.com> Date: Wed, 5 Jul 2000 11:36:57 -0700 (MST) To: hackers@freebsd.org Subject: OT: thank you to all developers! X-Mailer: VM 6.75 under Emacs 20.6.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last night I finally got around to building up my first "real" 4.0-RELEASE machine (kind "late" since 4.1 is creeping up on us I know ... but ....). I installed 4.0 "fresh" from the CDs, copied my previous machine's /etc files over from a CD backup (with minor edits of course :), cvsup'ed 4-STABLE, rebuilt and installed world and a new kernel, and replaced my 3-STABLE firewall/gateway machine in a matter of hours. All went totally without a hitch in the world and absolutely screams with speed! A huge, giant, chocolate-covered thanks to all developers!!!! -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 11:55:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9A5CA37C33F for ; Wed, 5 Jul 2000 11:55:20 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA17133; Wed, 5 Jul 2000 12:55:18 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA42163; Wed, 5 Jul 2000 12:54:58 -0600 (MDT) Message-Id: <200007051854.MAA42163@harmony.village.org> To: David Malone Subject: Re: Global variables defined several times. Cc: Poul-Henning Kamp , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 Jul 2000 22:22:30 BST." <200007032222.aa41540@salmon.maths.tcd.ie> References: <200007032222.aa41540@salmon.maths.tcd.ie> Date: Wed, 05 Jul 2000 12:54:58 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007032222.aa41540@salmon.maths.tcd.ie> David Malone writes: : I can't find my second edition at the moment. This behavior is : commented on in the C FAQ as something the ANSI standard describes : as a common extension. (http://www.eskimo.com/~scs/C-faq/q1.7.html) : It also seems to suggest it is mostly a Unix thing. VMS's DEC CC does the same thing as our tool chain. At least on the VMS 4.4 system I used in college. It got lots of other things "different" than the unix compilers we were using (pcc derived things for sun3 and sun4), but this it did the same. C++ requires exactly one definition, but can have many declarations (eg only one int foo, but many extern int foo). Actually, conforming C++ compilers may require exactly one definition. This is listed in the appendix of one of the Stroustup books as being a departure from plain old C. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 12: 7:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id E528D37BB78 for ; Wed, 5 Jul 2000 12:07:02 -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 e65J6jf19499; Wed, 5 Jul 2000 12:06:46 -0700 (PDT) Date: Wed, 5 Jul 2000 12:06:45 -0700 (PDT) From: Doug White To: Reinier Bezuidenhout Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NATD errors on 5.0 In-Reply-To: <200007051504.RAA27771@oskar.dev.nanoteq.co.za> 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, 5 Jul 2000, Reinier Bezuidenhout wrote: > Hi ... > > I've started natd on my local machine to translate all packets > to the ip of my public interface. > > If I am on my machine, and I start natd and add the divert rule, > (this means I'm trying to connect from my local machine on which I am > running the natd to any other machine) I can see the packet leaving my > machine, ariving at the destination machine, but NO reply returned, > if I ping .. everything seems ok .... > > Any ideas what is wrong ??? This is a -questions question. Check your rules... try running open to start out with then restrict as needed. 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 Jul 5 13: 8:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 82A4D37BC9D for ; Wed, 5 Jul 2000 13:08:25 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 62E111C64; Wed, 5 Jul 2000 16:08:24 -0400 (EDT) Date: Wed, 5 Jul 2000 16:08:24 -0400 From: Bill Fumerola To: hackers@freebsd.org Subject: data corruption Message-ID: <20000705160824.G4034@jade.chc-chimes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -hackers, This is the most fucked up thing I've ever experienced with FreeBSD: [hawk-billf] /home/billf/helpdesk > ls ./ ../ Makefile hdesk.c [hawk-billf] /home/billf/helpdesk > cd .. [hawk-billf] /home/billf > ls hdesk ls: hdesk: No such file or directory [hawk-billf] /home/billf > cp -pRP helpdesk hdesk [hawk-billf] /home/billf > cd hdesk [hawk-billf] /home/billf/hdesk > ls ./ Makefile hdesk.c ../ hdesk* hdesk.o Note that hdesk and hdesk.o suddenly came back from the dead. It works in reverse, every now and then when running $ echo "test" | ./hdesk it will fail like so: 75203 ktrace CALL execve(0xbfbffb53,0xbfbffa48,0xbfbffa50) 75203 ktrace NAMI "./hdesk" 75203 ktrace RET execve -1 errno 2 No such file or directory but if I run it again, it may work. the files are just appearing and reappearing. Another example: [hawk-billf] /home/billf/helpdesk > make clean rm -f hdesk hdesk.o [hawk-billf] /home/billf/helpdesk > ls ./ Makefile hdesk.c ktrace.out ../ hdesk* hdesk.o hdesk and hdesk.o have been removed, but they are still hanging around. If I copy the directories around (or move) them, I experience the same oddity. If I make a whole new directory structure and $ cat hdesk.c > /tmp/hdesk.c $ cat Makefile /tmp/Makefile $ mkdir notwhacked $ cp /tmp/{hdesk.c,Makefile} notwhacked the behavior goes away. Someone tell me I'm wrong here... -- Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES e-mail: billf@chimesnet.com / billf@FreeBSD.org PS. No, it's not something stupid like file flags or something. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 13:52:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2F02C37B5A0 for ; Wed, 5 Jul 2000 13:52:11 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA17796; Wed, 5 Jul 2000 14:52:09 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA43372; Wed, 5 Jul 2000 14:51:47 -0600 (MDT) Message-Id: <200007052051.OAA43372@harmony.village.org> To: "Alexey V. Vatchenko" Subject: Re: fsck Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 Jul 2000 22:27:53 -0000." <00070422315500.00285@unixbox.anna.com> References: <00070422315500.00285@unixbox.anna.com> Date: Wed, 05 Jul 2000 14:51:47 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <00070422315500.00285@unixbox.anna.com> "Alexey V. Vatchenko" writes: : /dev/ad0s2a: NO WRITE ACCESS : /dev/ad0s2a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. : : what is it? / is likely mounted on /dev/ad0s2a, so you can't get write access to /dev/ad0s2a. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 14:14:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 2447437B529; Wed, 5 Jul 2000 14:14:38 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA79740; Wed, 5 Jul 2000 14:14:38 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 5 Jul 2000 14:14:37 -0700 (PDT) From: Kris Kennaway To: Max Khon Cc: hackers@freebsd.org Subject: Re: latest news concerned crypto stuff 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 Wed, 5 Jul 2000, Max Khon wrote: > do the latest news concerned crypto stuff mean that we can now always have > DES in base system? and what's about a possibility to select Crypt Format > (DES/MD5/SHA/whatever) per user or per login class? No, that code is still not finished. I'm currently sidetracked working on KAME integration in current and trying to get it merged in time for 4.1 Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 15:56:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 24BD637B72A for ; Wed, 5 Jul 2000 15:56:22 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id SAA14253; Wed, 5 Jul 2000 18:57:03 -0400 (EDT) Message-Id: <200007052257.SAA14253@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 05 Jul 2000 19:06:13 -0400 To: Doug White From: Dennis Subject: Re: stray interrupts in 4.0 Cc: hackers@freebsd.org In-Reply-To: References: <200007011919.PAA04481@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:23 PM 7/1/00 -0700, you wrote: >On Sat, 1 Jul 2000, Dennis wrote: > >> We're seeing lots of "stray" interrupts in 4.0 while running 3.4 on the >> same hardware reports nothing. The interrupt its complaining about is IRQ7 >> even though parallel port is disabled and no other device. It happens on >> more than 1 MB. > >This is in the archives and the FAQ at www.freebsd.org. This is normal. thanks for the "pointer", but searching the faq for "stray" returns zilch. To which "archives" are you referring? Why is it "normal" to send hundreds of messages to the console? The term "stray" implies abnormal. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 17: 9:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id 10C6C37B918 for ; Wed, 5 Jul 2000 17:09:35 -0700 (PDT) (envelope-from root@gits.dyndns.org) Received: (qmail 9111121 invoked from network); 6 Jul 2000 00:09:33 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 6 Jul 2000 00:09:33 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id CAA13361; Thu, 6 Jul 2000 02:09:32 +0200 (CEST) (envelope-from root) Posted-Date: Thu, 6 Jul 2000 02:09:32 +0200 (CEST) To: Ben Smithurst Cc: Brian Somers , James Howard , freebsd-hackers@FreeBSD.ORG, brian@hak.lan.Awfulhak.org, freebsd-arch@FreeBSD.ORG Subject: Re: /etc/security -> /etc/periodic/security ? References: <200007040825.JAA03271@hak.lan.Awfulhak.org> <20000704130744.D13714@strontium.scientia.demon.co.uk> Reply-To: clefevre@citeweb.net X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C From: Cyrille Lefevre Date: 06 Jul 2000 02:09:32 +0200 In-Reply-To: Ben Smithurst's message of "Tue, 4 Jul 2000 13:07:44 +0100" Message-ID: Lines: 23 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Canyonlands" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst writes: > Brian Somers wrote: > > >> Well, "periodic security" will work as long as /etc/periodic/security > >> exists, so I guess you just mean the docs need updating? I'll get to > >> that if someone is actually planning on committing this stuff. > >=20 > > Perhaps the best option is to do with the inline security option and=20 > > just run ``periodic security'' from cron ? I can commit the changes. > > I don't think there's really a problem with just running security > from daily. I can add a note that this is normal practice in the > manpage, and that security shouldn't be run separately unless you set > daily_security_enable=3DNO or whatever the option is. why not even something like security_enable=[YES|NO] and security_periode=[daily|weekly|monthly] defaulting to daily? Cyrille. -- home:mailto:clefevre@no-spam.citeweb.net Supprimer "no-spam." pour me repondre. work:mailto:Cyrille.Lefevre@no-spam.edf.fr Remove "no-spam." to answer me back. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 17:37: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 2192537BA74 for ; Wed, 5 Jul 2000 17:36:59 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 42A071C64; Wed, 5 Jul 2000 20:36:58 -0400 (EDT) Date: Wed, 5 Jul 2000 20:36:58 -0400 From: Bill Fumerola To: hackers@freebsd.org Subject: cocaine snorting reported in Michigan, details at 11 (was Re: data corruption) Message-ID: <20000705203658.S4034@jade.chc-chimes.com> References: <20000705160824.G4034@jade.chc-chimes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000705160824.G4034@jade.chc-chimes.com>; from billf@chimesnet.com on Wed, Jul 05, 2000 at 04:08:24PM -0400 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 05, 2000 at 04:08:24PM -0400, Bill Fumerola wrote: > PS. No, it's not something stupid like file flags or something. No, it was something even stupider. Completely ignore this. -- Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES e-mail: billf@chimesnet.com / billf@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 Jul 5 17:47:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (ether.osd.bsdi.com [204.216.28.196]) by hub.freebsd.org (Postfix) with ESMTP id 1207C37BC68 for ; Wed, 5 Jul 2000 17:47:32 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA00500; Wed, 5 Jul 2000 17:54:19 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007060054.RAA00500@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: Doug White , hackers@freebsd.org Subject: Re: stray interrupts in 4.0 In-reply-to: Your message of "Wed, 05 Jul 2000 19:06:13 EDT." <200007052257.SAA14253@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Jul 2000 17:54:19 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 02:23 PM 7/1/00 -0700, you wrote: > >On Sat, 1 Jul 2000, Dennis wrote: > > > >> We're seeing lots of "stray" interrupts in 4.0 while running 3.4 on the > >> same hardware reports nothing. The interrupt its complaining about is IRQ7 > >> even though parallel port is disabled and no other device. It happens on > >> more than 1 MB. > > > >This is in the archives and the FAQ at www.freebsd.org. This is normal. > > thanks for the "pointer", but searching the faq for "stray" returns zilch. > To which "archives" are you referring? The "stray irq7" message has been remarked on countless times. Having said that, our search tools are less than marvellous. 8( > Why is it "normal" to send hundreds of messages to the console? The term > "stray" implies abnormal. It's "normal" insofar as countless PC motherboards generate these spurious interrupts. However, we're anal enough to consider spurious interrupts "abnormal", and we kvetch about them. Generally this message indicates that you have hardware in the system that is not signalling interrupts correctly. -- ... 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] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 17:50:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (ether.osd.bsdi.com [204.216.28.196]) by hub.freebsd.org (Postfix) with ESMTP id 5483C37B772 for ; Wed, 5 Jul 2000 17:50:19 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA00537; Wed, 5 Jul 2000 17:57:47 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007060057.RAA00537@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: clefevre@citeweb.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/security -> /etc/periodic/security ? In-reply-to: Your message of "06 Jul 2000 02:09:32 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Jul 2000 17:57:47 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I don't think there's really a problem with just running security > > from daily. I can add a note that this is normal practice in the > > manpage, and that security shouldn't be run separately unless you set > > daily_security_enable=3DNO or whatever the option is. > > why not even something like security_enable=[YES|NO] and > security_periode=[daily|weekly|monthly] defaulting to daily? That's just what we need - a configuration option that lets the admin turn security off. 8) -- ... 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] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 17:58: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id B369D37BD1B for ; Wed, 5 Jul 2000 17:58:00 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.9.3/8.9.3) with ESMTP id RAA98519; Wed, 5 Jul 2000 17:57:56 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200007060057.RAA98519@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bill Fumerola Cc: hackers@FreeBSD.ORG Subject: Re: cocaine snorting reported in Michigan, details at 11 (was Re: data corruption) In-Reply-To: Message from Bill Fumerola of "Wed, 05 Jul 2000 20:36:58 EDT." <20000705203658.S4034@jade.chc-chimes.com> Date: Wed, 05 Jul 2000 17:57:56 -0700 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: > On Wed, Jul 05, 2000 at 04:08:24PM -0400, Bill Fumerola wrote: > > > PS. No, it's not something stupid like file flags or something. > > No, it was something even stupider. Completely ignore this. Oh, come on now, tell us the details! :-) Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 18: 8:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 50F6437BFE3 for ; Wed, 5 Jul 2000 18:08:27 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id A599E1C64; Wed, 5 Jul 2000 21:08:23 -0400 (EDT) Date: Wed, 5 Jul 2000 21:08:23 -0400 From: Bill Fumerola To: Peter Wemm Cc: hackers@FreeBSD.ORG Subject: Re: cocaine snorting reported in Michigan, details at 11 (was Re: data corruption) Message-ID: <20000705210823.V4034@jade.chc-chimes.com> References: <200007060057.RAA98519@netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200007060057.RAA98519@netplex.com.au>; from peter@netplex.com.au on Wed, Jul 05, 2000 at 05:57:56PM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 05, 2000 at 05:57:56PM -0700, Peter Wemm wrote: > > > PS. No, it's not something stupid like file flags or something. > > > > No, it was something even stupider. Completely ignore this. > > Oh, come on now, tell us the details! :-) It involves this running in another window: [hawk-billf] $ while `true`; do make clean; sleep 5; make; sleep 5; done It was done as a joke before I left last weekend; I opened a bunch of eterms and looped some pings, traceroutes, compiles, etc and the joke was that as long as I did that it looked like I did as much work as other, uhm, less motivated, cow-orkers. I fully expect to be physically assulted by all who I encounter the next time I'm in California for this act of stupidity. -- Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES e-mail: billf@chimesnet.com / billf@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 Jul 5 20:47:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 37FCB37B6D9 for ; Wed, 5 Jul 2000 20:47:46 -0700 (PDT) (envelope-from john@baldwin.cx) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id UAA41344; Wed, 5 Jul 2000 20:47:12 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id UAA44656; Wed, 5 Jul 2000 20:48:24 -0700 (PDT) (envelope-from john) Message-Id: <200007060348.UAA44656@john.baldwin.cx> 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: <20000705210823.V4034@jade.chc-chimes.com> Date: Wed, 05 Jul 2000 20:48:24 -0700 (PDT) From: John Baldwin To: Bill Fumerola Subject: Re: cocaine snorting reported in Michigan, details at 11 (was Re Cc: hackers@FreeBSD.ORG, Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Jul-00 Bill Fumerola wrote: > On Wed, Jul 05, 2000 at 05:57:56PM -0700, Peter Wemm wrote: > >> > > PS. No, it's not something stupid like file flags or something. >> > >> > No, it was something even stupider. Completely ignore this. >> >> Oh, come on now, tell us the details! :-) > > It involves this running in another window: > > [hawk-billf] $ while `true`; do make clean; sleep 5; make; sleep 5; done > > It was done as a joke before I left last weekend; I opened a bunch of > eterms and looped some pings, traceroutes, compiles, etc and the joke > was that as long as I did that it looked like I did as much work > as other, uhm, less motivated, cow-orkers. > > I fully expect to be physically assulted by all who I encounter the > next time I'm in California for this act of stupidity. /me pats the Big Knife and the Damn Thing -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Jul 5 21:10:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C807337C044 for ; Wed, 5 Jul 2000 21:10:28 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id GAA89088 for freebsd-hackers@freebsd.org; Thu, 6 Jul 2000 06:10:26 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id DAA28746 for ; Thu, 6 Jul 2000 03:46:53 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Thu, 6 Jul 2000 03:46:52 +0200 (CEST) From: Leif Neland To: freebsd-hackers@freebsd.org Subject: Make world in "traditional make-mode" 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 Is there an option in make world to work like a traditional make works? i.e. just recompile if the source has changed. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 5 21:15:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 22B1B37C044 for ; Wed, 5 Jul 2000 21:15:43 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id CDC5A1C65; Thu, 6 Jul 2000 00:15:42 -0400 (EDT) Date: Thu, 6 Jul 2000 00:15:42 -0400 From: Bill Fumerola To: Leif Neland Cc: freebsd-hackers@freebsd.org Subject: Re: Make world in "traditional make-mode" Message-ID: <20000706001542.F4034@jade.chc-chimes.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from leifn@neland.dk on Thu, Jul 06, 2000 at 03:46:52AM +0200 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 06, 2000 at 03:46:52AM +0200, Leif Neland wrote: > Is there an option in make world to work like a traditional make works? > i.e. just recompile if the source has changed. -DNOCLEAN is as close as you're going to get, probably. -- Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES e-mail: billf@chimesnet.com / billf@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 Jul 5 22:15:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sn1oexchr01.nextvenue.com (sn1oexchr01.nextvenue.com [63.209.169.9]) by hub.freebsd.org (Postfix) with SMTP id 9F19337B6D9 for ; Wed, 5 Jul 2000 22:15:41 -0700 (PDT) (envelope-from nevans@nextvenue.com) Received: FROM sn1exchmbx.nextvenue.com BY sn1oexchr01.nextvenue.com ; Thu Jul 06 01:13:57 2000 -0400 Received: by SN1EXCHMBX with Internet Mail Service (5.5.2650.21) id ; Thu, 6 Jul 2000 01:13:50 -0400 Message-ID: <712384017032D411AD7B0001023D799B07C963@SN1EXCHMBX> From: Nick Evans To: 'Dan Nelson' Cc: "'freebsd-hackers@freebsd.org'" Subject: RE: BPF and Promiscuous Mode Date: Thu, 6 Jul 2000 01:13:49 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFE708.F8228630" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFE708.F8228630 Content-Type: text/plain; charset="iso-8859-1" Here is how to bridge different interfaces together selectively: Controlling bridging Bridging is almost exclusively controlled by sysctl variables. net.link.ether.bridge_cfg: ed2:1,rl0:1, set of interfaces for which bridging is enabled, and cluster they belong to. net.link.ether.bridge: 0 enable bridging. net.link.ether.bridge_ipfw: 0 enable ipfw for bridging. Thanks to Luigi Rizzo for that information extracted from his site at: http://www.iet.unipi.it/~luigi/ip_dummynet/ This net.link.enther.bridge_cfg is not in the man page and I have read nothing about it anywhere else, is there some resource that has every sysctl variable listed with it's purpose? thx nick -----Original Message----- From: Nick Evans Sent: Tuesday, July 04, 2000 12:18 AM To: 'Dan Nelson' Cc: 'freebsd-hackers@freebsd.org' Subject: RE: BPF and Promiscuous Mode Exactly, I just tried it and it didn't work :(. Yes you are right on, NFR is a sniffer/ids, but it is based on the OpenBSD kernel and therefore does not support multiple processors. I just tried bridging and it does in fact bridge all interfaces together, but it still does not appear to be mirroring all traffic from one interface to another. Apparently there are issues with IPFilter and FreeBSD... I am going to try OpenBSD and IPFilter tonight. The IPFilter people know that bridging works on OpenBSD, and you can bridge specific interfaces. -----Original Message----- From: Dan Nelson [mailto:dnelson@emsphone.com] Sent: Monday, July 03, 2000 10:34 PM To: Nick Evans Subject: Re: BPF and Promiscuous Mode Is there any reason you're not CC'ing the list? I added it back on my first reply on the assumption you simply forgot, but this email is missing it too. It's good to have exchanges like these in the mailing-list archives, so help other people that might have the same question later. In the last episode (Jul 03), Nick Evans said: > actually it's like this > > --- > | > | <- mirrored port > > | > | > > | | | > | | | > > > the nfr boxes do not have ip's so i just need the traffic duplicated > (so routing is out of the question), but i wanted to use ipfilter to, > get this, filter the traffic so not all the ida's see all the > traffic. the simply cannot handle 600Mbits each... my plan is to put > a gig interface, or two, into the BSD box and several dualport server > adaptors and then segment that traffic down. bridging might work, but > i do not know how to bind certain interfaces together in FreeBSD, > OpenBSD, yes, but not Free... Aahh. An nfr is a sniffer. I assumed that you were load-balancing web servers or something, which was confising me a bit since you don't want to use mirroring for this. For your purposes, mirroring is perfect. I think enabling bridging, and then using ipfilter or ipfw to only allow (say) 1/3 of the Net addresses to each server (assuming you have 3 nfr's), would do what you want. I wonder if NFR will take advantage of multiple CPUs in a single box. That way you don't have to worry about any of this. In the last episode (Jul 03), Nick Evans said: > actually a better question would have been, do you know if you can > bridge multiple interfaces to one other interface lik 4 100mbit nics > to one gigabit nic? I assume so. The bridge manpage mentions the inability to selectively bridge certain interfaces, so the default must be to bridge all ethernet interfaces. You can probably add some filtering rules to make sure you don't re-transmit packets out of your gigabit NICs. -- Dan Nelson dnelson@emsphone.com ------_=_NextPart_001_01BFE708.F8228630 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: BPF and Promiscuous Mode

Here is how to bridge different interfaces together = selectively:

Controlling bridging
Bridging is almost exclusively controlled by sysctl = variables.
net.link.ether.bridge_cfg: ed2:1,rl0:1,
        set of = interfaces for which bridging is enabled, and cluster
        they = belong to.

net.link.ether.bridge: 0
        enable = bridging.

net.link.ether.bridge_ipfw: 0
        enable = ipfw for bridging.

Thanks to Luigi Rizzo for that information extracted = from his site at:

http://www.iet.unipi.it/~luigi/ip_dummynet/=

This net.link.enther.bridge_cfg is not in the man = page and I have read nothing about it anywhere else, is there some = resource that has every sysctl variable listed with it's = purpose?

thx
nick
 

-----Original Message-----
From: Nick Evans
Sent: Tuesday, July 04, 2000 12:18 AM
To: 'Dan Nelson'
Cc: 'freebsd-hackers@freebsd.org'
Subject: RE: BPF and Promiscuous Mode


Exactly, I just tried it and it didn't work :(.  = Yes you are right on, NFR is a sniffer/ids, but it is based on the = OpenBSD kernel and therefore does not support multiple processors. I = just tried bridging and it does in fact bridge all interfaces together, = but it still does not appear to be mirroring all traffic from one = interface to another. Apparently there are issues with IPFilter and = FreeBSD... I am going to try OpenBSD and IPFilter tonight. The IPFilter = people know that bridging works on OpenBSD, and you can bridge specific = interfaces.

-----Original Message-----
From: Dan Nelson [mailto:dnelson@emsphone.com]
Sent: Monday, July 03, 2000 10:34 PM
To: Nick Evans
Subject: Re: BPF and Promiscuous Mode



Is there any reason you're not CC'ing the list?  = I added it back on my
first reply on the assumption you simply forgot, but = this email is
missing it too.  It's good to have exchanges = like these in the
mailing-list archives, so help other people that = might have the same
question later.

In the last episode (Jul 03), Nick Evans said:
> actually it's like this
>
> <router> --- <switch>
>       =         =         |
>       =         =         | <- mirrored port
>       =         <freebsdbox>
>       =         =         |
>       =         =         |
>       =      <vlan'd switch>
>       =         = |       = |       |
>       =         = |       = |       |
>       =     <nfr> <nfr> <nfr>
>
> the nfr boxes do not have ip's so i just need = the traffic duplicated
> (so routing is out of the question), but i = wanted to use ipfilter to,
> get this, filter the traffic so not all the = ida's see all the
> traffic. the simply cannot handle 600Mbits = each... my plan is to put
> a gig interface, or two, into the BSD box and = several dualport server
> adaptors and then segment that traffic down. = bridging might work, but
> i do not know how to bind certain interfaces = together in FreeBSD,
> OpenBSD, yes, but not Free...

Aahh.  An nfr is a sniffer.  I assumed that = you were load-balancing web
servers or something, which was confising me a bit = since you don't want
to use mirroring for this.  For your purposes, = mirroring is perfect.

I think enabling bridging, and then using ipfilter or = ipfw to only
allow (say) 1/3 of the Net addresses to each server = (assuming you have
3 nfr's), would do what you want.  I wonder if = NFR will take advantage
of multiple CPUs in a single box.  That way you = don't have to worry
about any of this.

In the last episode (Jul 03), Nick Evans said:
> actually a better question would have been, do = you know if you can
> bridge multiple interfaces to one other = interface lik 4 100mbit nics
> to one gigabit nic?

I assume so.  The bridge manpage mentions the = inability to selectively
bridge certain interfaces, so the default must be to = bridge all
ethernet interfaces.  You can probably add some = filtering rules to make
sure you don't re-transmit packets out of your = gigabit NICs.

--
        Dan = Nelson
        dnelson@emsphone.com

------_=_NextPart_001_01BFE708.F8228630-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 0:55:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id A4C9437C19E for ; Thu, 6 Jul 2000 00:55:33 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (2030 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Thu, 6 Jul 2000 09:55:31 +0200 (CEST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 25254158A; Thu, 6 Jul 2000 09:55:17 +0200 (METDST) Subject: Re: i4b: PCBIT PCI card support In-Reply-To: <00070518031400.07491@ekstassy.com> from milton moura at "Jul 5, 0 05:45:23 pm" To: miltonmoura@mail.telepac.pt Date: Thu, 6 Jul 2000 09:55:17 +0200 (METDST) Cc: freebsd-hackers@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1172 Message-Id: <20000706075517.25254158A@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Until some time ago I had a regular modem dial-up connection to my ISP, which > was recently upgraded to a ISDN 64k connection. > Along with the ISP ISDN Pack I purchased came a PCBIT PCI TigerJet Tiger300 > ISDN card which works perfectly under Linux with ippp and the HiSAX module > (loaded with these settings: insmod hisax type=20 protocol=2 id="HiSax"). > > Just out of pure curiosity, I ordered FreeBSD-4.0 from freebsdmall a couple of > weeks ago and it arrived earlier this week. > After installing, reading the docs and lots of other stuff, I came to the sad > conclusion that i4b does not support my ISDN card. This card is not supported under i4b. Docs for the Tiger300 chip are available on request from the mailaddresses given in http://www.tjnet.com. I'd be happy to include a driver into i4b in case somebody would write one. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 1:11: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 388F237B582 for ; Thu, 6 Jul 2000 01:10:57 -0700 (PDT) (envelope-from kuku@gilberto.physik.rwth-aachen.de) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id KAA43262 for hackers@freebsd.org; Thu, 6 Jul 2000 10:10:59 +0200 (CEST) (envelope-from kuku) Date: Thu, 6 Jul 2000 10:10:59 +0200 (CEST) From: Christoph Kukulies Message-Id: <200007060810.KAA43262@gilberto.physik.rwth-aachen.de> To: hackers@freebsd.org Subject: dutchmen at LinuxTag Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Who of our dutch FreeBSD fellows were present at LinuxTag (LinuxDay in Germany) recently, spreading the word for FreeBSD? I have got a positive response of a Linux addict who said that these guys were very friendly, and he was considering buying a FreeBSD CD and using it in a webserver environment. But 90 Deutsch Marks OTOH was too expensive to him. (I'm feeling to be obligued to send him a complimentary copy of one of my 4.0 FreeBSD CDs). -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 1:17:23 2000 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 292D037B582; Thu, 6 Jul 2000 01:17:16 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id RAA05047; Thu, 6 Jul 2000 17:47:01 +0930 (CST) (envelope-from grog) Date: Thu, 6 Jul 2000 17:47:01 +0930 From: Greg Lehey To: Christoph Kukulies Cc: FreeBSD advocacy list Subject: Re: dutchmen at LinuxTag Message-ID: <20000706174700.C2024@wantadilla.lemis.com> References: <200007060810.KAA43262@gilberto.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200007060810.KAA43262@gilberto.physik.rwth-aachen.de> 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 [moving from -hackers to -advocacy] On Thursday, 6 July 2000 at 10:10:59 +0200, Christoph Kukulies wrote: > > Who of our dutch FreeBSD fellows were present at LinuxTag (LinuxDay in > Germany) recently, spreading the word for FreeBSD? > > I have got a positive response of a Linux addict who said that > these guys were very friendly, and he was considering buying a FreeBSD > CD and using it in a webserver environment. But 90 Deutsch Marks OTOH was > too expensive to him. (I'm feeling to be obligued to send him a > complimentary copy of one of my 4.0 FreeBSD CDs). You should contact Pat Reitz and get her to send you some giveaway CDs for the next Linuxtag. We're having a Linux Installfest here in Adelaide next weekend (15th) (see http://www.linuxsa.org.au/meetings/installfest2000/), and BSDi have contributed 200 giveaways, which should be ample. You'll notice it figures quite prominently in the web page. 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 Thu Jul 6 3:48: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from walrus.xiam.com (walrus.xiam.com [194.125.50.210]) by hub.freebsd.org (Postfix) with ESMTP id 8A2D037B7B1 for ; Thu, 6 Jul 2000 03:47:48 -0700 (PDT) (envelope-from cillian@xiam.com) Received: from xiam.com (REMUS.xiam.com [10.20.3.46]) by walrus.xiam.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id N5HWY98N; Thu, 6 Jul 2000 11:49:33 +0100 Message-ID: <3964638F.9162B7C@xiam.com> Date: Thu, 06 Jul 2000 11:46:39 +0100 From: cillian@xiam.com X-Mailer: Mozilla 4.61 [en]C-CCK-MCD C-UDP; (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: /etc/security -> /etc/periodic/security ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > why not even something like security_enable=[YES|NO] and > > security_periode=[daily|weekly|monthly] defaulting to daily? /etc/security is hard-wired in many respects to be run on a daily basis, i.e. it does lots of 'today/yesterday' diff reports. Anyway, I think security reports are important enough that you'd want to be informed daily, at the very least. > That's just what we need - a configuration option that lets the admin > turn security off. 8) :) While we're on the subject of /etc/security, just a few comments/suggestions.. For 'logfile' reports (login failures, kernel messages, refused connections, etc.), I think we should use the 'logtail' program or something similar. This could be run from cron on a frequent [i.e. hourly] basis, coinciding with newsyslog. This way, you don't have to wait for the daily security report to tell you something's wrong, and it should also eliminate duplicated data in reports as each report only shows the 'bad' messages since last run, as opposed to all the bad messages currently in the respective logfiles. [which is what it certainly does on 3.4, anyway] Also, /var/log/kernel [syslog: kern.*] should be used in preference to dmesg as the source of kernel messages, as there's no risk of losing kernel messages that have disappeared from the system message buffer. Better support for ipfw and ipf/ipmon would be nice, but I'd imagine most people just roll-their-own, when it comes to firewall scripts/status reports. -- Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 5:46:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 335A137B61D for ; Thu, 6 Jul 2000 05:46:17 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id IAA50548; Thu, 6 Jul 2000 08:46:11 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200007061246.IAA50548@blackhelicopters.org> Subject: Re: cocaine snorting reported in Michigan, details at 11 (was Re: data corruption) In-Reply-To: <20000705210823.V4034@jade.chc-chimes.com> from Bill Fumerola at "Jul 5, 2000 9: 8:23 pm" To: billf@chimesnet.com (Bill Fumerola) Date: Thu, 6 Jul 2000 08:46:10 -0400 (EDT) Cc: hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] 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 fully expect to be physically assulted by all who I encounter the > next time I'm in California for this act of stupidity. > Physically assaulted? No, why do that when we can point and laugh? It's legal, and much more devastating. Just noticed you're in Michigan. Are you aware of any Michigan FreeBSD groups? I've been looking around Detroit for a while, and haven't found any. ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 6: 3:33 2000 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 9790E37B553 for ; Thu, 6 Jul 2000 06:03:30 -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, 6 Jul 2000 14:03:25 +0100 Received: from localhost (cmjg@localhost) by mail.ilrt.bris.ac.uk (8.8.7/8.8.8) with ESMTP id OAA03048; Thu, 6 Jul 2000 14:03:24 +0100 (BST) Date: Thu, 6 Jul 2000 14:03:24 +0100 (BST) From: Jan Grant To: Nick Rogness Cc: Dan Nelson , Nick Evans , "'freebsd-hackers@freebsd.org'" Subject: Re: BPF and Promiscuous Mode 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 Mon, 3 Jul 2000, Nick Rogness wrote: > On Mon, 3 Jul 2000, Dan Nelson wrote: > > > In the last episode (Jul 03), Nick Evans said: > > > How do I set an interface in promiscous mode permanently? In Linux > > > it's simply ifconfig PROMISC. Is there something similar > > > in BSD? Is it somekind of sysctl command? > > Stupid Man's Answer: > > I would just run on bootup: > > /usr/sbin/tcpdump >> /dev/null & > > Probaby not the answer you are looking for, but maybe it will > help. You'll notice a lot of DNS traffic from your machine if you do this. Include -n at least! -- 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 Bolstered by my success with vi, I proceeded to learn C with 'learn c'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 7:23: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 98AFC37B6FF for ; Thu, 6 Jul 2000 07:22:54 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id KAA77626; Thu, 6 Jul 2000 10:22:34 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Thu, 6 Jul 2000 10:22:34 -0400 (EDT) From: Adam To: Michael Lucas Cc: Bill Fumerola , hackers@FreeBSD.ORG Subject: Re: cocaine snorting reported in Michigan, details at 11 (was Re: data corruption) In-Reply-To: <200007061246.IAA50548@blackhelicopters.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 On Thu, 6 Jul 2000, Michael Lucas wrote: >> >> I fully expect to be physically assulted by all who I encounter the >> next time I'm in California for this act of stupidity. >> > >Physically assaulted? No, why do that when we can point and laugh? >It's legal, and much more devastating. > >Just noticed you're in Michigan. Are you aware of any Michigan >FreeBSD groups? I've been looking around Detroit for a while, and >haven't found any. > >==ml I keep mentioning to bill and others on irc from michigan that someone should start one :p To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 7:56:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 2F10237BA35 for ; Thu, 6 Jul 2000 07:56:46 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FXA00H1J2CI1Y@falla.videotron.net> for freebsd-hackers@FreeBSD.ORG; Thu, 6 Jul 2000 09:19:31 -0400 (EDT) Date: Thu, 06 Jul 2000 09:21:38 -0400 (EDT) From: Bosko Milekic Subject: Re: mbuf re-write(s), v 0.1 In-reply-to: <8459.962654377@critter.freebsd.dk> X-Sender: bmilekic@jehovah.technokratis.com To: Poul-Henning Kamp Cc: freebsd-hackers@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 On Mon, 3 Jul 2000, Poul-Henning Kamp wrote: > In message <20000703154040.V18942@jade.chc-chimes.com>, Bill Fumerola writes: > > >I'd love to have FreeBSD be able to reclaim memory quicker at the sacrifice > >of a few cpu cycles. Why? Well, the "add more memory" arguement doesn't work > >well when I get DoS attacks that will eat any memory available because they > >can connect quicker then I can reclaim the memory. > > I have this dream of a global "VM availability flag": > > Imagine if the kernel kept a global variable: > > enum {VM_PLENTY, VM_TIGHT, VM_NONE, VM_PANIC} vm_state; > /* VM_PLENTY: No worries */ > /* VM_TIGHT: Don't make it any worse if you can avoid it */ > /* VM_NONE: Fail if you must, free some if you can */ > /* VM_PANIC: "VM, VM, my panic for some VM" */ > > At least a few pieces of our memory-gobbling code could examine > and adjust their caching behaviour from that. Take the vfs > name-cache as an example: > > /* Create a new vfs_name-cache entry */ > cache_enter(...) > switch (vm_state) { > case VM_PLENTY: > /* do as today */ > break; > case VM_TIGHT: > /* delete at least as many bytes as we add (LRU wise) */ > break; > case VM_NONE: > /* delete two entries, don't add the new one */ > break; > case VM_PANIC: > /* delete the entire cache */ > break; > } > > The mbuf allocator can use this to great effect if the various > MGET() calls were labeled according to their importance. > > Respecting such a flag in the various kernels provide great resistance > against DoS. > > User land processes can benefit from this as well: a sysctl would > allow malloc(3) to investigate this state whenever it had was > dealing with a full page, and if needed it could release all it's > cached pages, possibly even call an optional "GC" callback into > the program to force a realloc(3) sequence in long-running daemons. > (An alternative scenario is to have a SIGVMSTATE defaulting to > ignore which gets sent when the variable changes, but that would > have thundering herd issues if a lot of processes was paged out.) > > If only somebody would add that variable, I don't feel like diving > into the VM system right now. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. I've recently had the chance to get some profiling done. I used metrics obtained from gprof, as well as the (basic block length) * (number of executions) metric generated by kernbb. The latter reveals an approximate 30% increase in the new code, but does not necessarily imply that time of execution is increased by that amount. gprof makes a fair estimate on execution time, and reveals that the new code is, worse case scenario 30% slower, and best case scenario, negligeably slower. Of course, I'm leaving out some details here, because I've decided to change things a little, in order to further improve (and significantly, at that) the performance of the new code. Note however that the 30% overall APPROXIMATE increase is not something I would consider significant, especially since the allocator/free routines don't hold much %time, and are not the bottleneck in any of the call graphs. I did decide to make drastic changes, however, in order to maintain with the 0-tolerance policy, even if it involves somewhat getting rid of a cleaner interface and adopting a "kernel process." See below. Following your suggestion for vm_state, which I am not about to implement at this time until I finish this work (so if somebody else wants to take it up, go ahead; just make sure to let all of us know, in case that we decide to do it later). However, the planned changes I am going to make this upcoming weekend to the mbuf code will be aimed at fitting in nicely with the vm_state stuff. Please note, however, that I am not going to dip into net code (yet) and begin inserting "good measure" code that will prevent new PCB allocations depending on vm_state, this is however extremely useful and should be considered in the near future. What I'm planning to do, on the other hand, is have the free routine never explicitly drain pages back to the map. What this means is that there will be a kernel process which can be awoken optionally when number_of_allocated_pages is by far exceeding average_allocated_pages (or, in the future, when vm_state is in a meaningful state). That process will be responsible for walking the "free list" and draining all pages associated with "complete" page descriptor structures until hitting average_allocated_pages once again. Thus, freeing back to the map will never be performed by the m_free or MFREE stuff, in which case performance will be improved. I am tentatively considering this, mainly because of what you mentionned about potential future for vm_state. The other option is of course to have MFREE never free back to the map if (how) == M_DONTWAIT, which will virtually maintain great performance during interrupts. I've actually already done this, but it's difficult to see the nice effects of it as I cannot profile MFREE (since it's a macro) but only m_free, which is typically called at M_WAIT, in which case I don't note the improvement. It's up to you guys. I would like suggestions. Furthermore, if whoever out there has a decent -CURRENT machine that's under heavy network load and would like to help me performance test/tune, please contact me! (e.g. Yahoo! guys, maybe?) Cheers, Bosko. -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 8:51:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from goku.cl.msu.edu (goku.cl.msu.edu [35.8.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 56E3B37C753 for ; Thu, 6 Jul 2000 08:51:51 -0700 (PDT) (envelope-from dervish@goku.cl.msu.edu) Received: (from dervish@localhost) by goku.cl.msu.edu (8.9.3/8.9.3) id LAA74150; Thu, 6 Jul 2000 11:51:29 -0400 (EDT) (envelope-from dervish) Date: Thu, 6 Jul 2000 11:51:29 -0400 From: Bush Doctor To: Adam Cc: Michael Lucas , Bill Fumerola , hackers@FreeBSD.ORG Subject: Re: cocaine snorting reported in Michigan, details at 11 (was Re: data corruption) Message-ID: <20000706115129.B74002@goku.cl.msu.edu> Mail-Followup-To: Adam , Michael Lucas , Bill Fumerola , hackers@FreeBSD.ORG References: <200007061246.IAA50548@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from bsdx@looksharp.net on Thu, Jul 06, 2000 at 10:22:34AM -0400 X-Operating-System: FreeBSD 5.0-CURRENT i386 WWW-Home-Page: http://bantu.cl.msu.edu Organisation: Fraternal Order of Whipped Husbands -- (F.O.O.W.H.) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Adam aka (bsdx@looksharp.net) said: > On Thu, 6 Jul 2000, Michael Lucas wrote: > > >> > >> I fully expect to be physically assulted by all who I encounter the > >> next time I'm in California for this act of stupidity. > >> > > > >Physically assaulted? No, why do that when we can point and laugh? > >It's legal, and much more devastating. > > > >Just noticed you're in Michigan. Are you aware of any Michigan > >FreeBSD groups? I've been looking around Detroit for a while, and > >haven't found any. > > > >==ml > > I keep mentioning to bill and others on irc from michigan that someone > should start one :p Well if anyone is ever down East Lansing way, a couple of co-workers and I have an informal group. Everyone is more than welcome to come here or maybe we could meet somewhere in between ... > > i'khala #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 8:58: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 3CD2137B536 for ; Thu, 6 Jul 2000 08:58:04 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FXA00EVI9CR6G@falla.videotron.net> for freebsd-hackers@FreeBSD.ORG; Thu, 6 Jul 2000 11:50:52 -0400 (EDT) Date: Thu, 06 Jul 2000 11:52:59 -0400 (EDT) From: Bosko Milekic Subject: Re: mbuf re-write(s), v 0.1 In-reply-to: X-Sender: bmilekic@jehovah.technokratis.com To: Poul-Henning Kamp Cc: freebsd-hackers@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 On Thu, 6 Jul 2000, Bosko Milekic wrote: > I've recently had the chance to get some profiling done. > > I used metrics obtained from gprof, as well as the (basic block > length) * (number of executions) metric generated by kernbb. The latter > reveals an approximate 30% increase in the new code, but does not > necessarily imply that time of execution is increased by that amount. > gprof makes a fair estimate on execution time, and reveals that the > new code is, worse case scenario 30% slower, and best case scenario, > negligeably slower. Of course, I'm leaving out some details here, because > I've decided to change things a little, in order to further improve (and > significantly, at that) the performance of the new code. Note however > that the 30% overall APPROXIMATE increase is not something I would > consider significant, especially since the allocator/free routines don't > hold much %time, and are not the bottleneck in any of the call graphs. I > did decide to make drastic changes, however, in order to maintain with > the 0-tolerance policy, even if it involves somewhat getting rid of a > cleaner interface and adopting a "kernel process." See below. You can disregard the above data. I actually found something detrimental (seriously) to performance. During MFREE, the code would free the page in question if at the time the number of mbufs on the free list exceeds (even by a little) min_on_avail. This is fine. The problem was in MGET/MGETHDR where the code would explicitly allocate when how==M_WAIT and number of mbufs on free list < min_on_avail (this was a feeble attempt at making M_NOWAIT allocations even faster). The potential problem is not so obvious: numerous M_WAIT allocs will ALWAYS allocate a page from the map while min_on_avail < mbufs on free lists. And, MFREE would almost ALWAYS have to free back to the map as at this point, the number of mbufs on the free lists fairly quickly reaches min_on_avail. So what would happen is a page would be allocated, freed, allocated, freed, etc. m_get + m_free would be an endless cycle of m_mbmapalloc and m_mbmapfree, which increases overhead significantly. After fixing MGET/MGETHDR, I'm getting more promising results. I'll get some hard data and post it later tonight, hopefully. Oh, and I'm still open to the kernel process idea. I'll need one such beast anyway, because it will help minimize page fragmentation for the allocator, on request. -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 bmilekic@technokratis.com * http://www.technokratis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 9:15:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sn1oexchr01.nextvenue.com (sn1oexchr01.nextvenue.com [63.209.169.9]) by hub.freebsd.org (Postfix) with SMTP id 4D50237C3E6 for ; Thu, 6 Jul 2000 09:15:06 -0700 (PDT) (envelope-from nevans@nextvenue.com) Received: FROM sn1exchmbx.nextvenue.com BY sn1oexchr01.nextvenue.com ; Thu Jul 06 12:13:14 2000 -0400 Received: by SN1EXCHMBX with Internet Mail Service (5.5.2650.21) id ; Thu, 6 Jul 2000 12:13:07 -0400 Message-ID: <712384017032D411AD7B0001023D799B07C96A@SN1EXCHMBX> From: Nick Evans To: "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: bridging Date: Thu, 6 Jul 2000 12:13:07 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFE765.1217DC50" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFE765.1217DC50 Content-Type: text/plain; charset="iso-8859-1" Correct me if I am wrong, but isn't bridging of two interfaces supposed to make a duplicate of the traffic from one onto another? Why is it then that on the second interface I bridge to I only see broadcast and multicast packets? I have fxp0 and fxp1 acting as a bridge, fxp0 sees all kinds of http traffic, napster, IM, etc. but fxp1 sees only multi/broadcast packets. any ideas? ------------------------------------------ nick.evans network.engineering NextVenue, Inc. phone: (212) 909.2988 pager: (888) 642.5541 ------_=_NextPart_001_01BFE765.1217DC50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable bridging

Correct me if I am wrong, but isn't bridging of two = interfaces supposed to make a duplicate of the traffic from one onto = another? Why is it then that on the second interface I bridge to I only = see broadcast and multicast packets? I have fxp0 and fxp1 acting as a = bridge, fxp0 sees all kinds of http traffic, napster, IM, etc. but fxp1 = sees only multi/broadcast packets.

any ideas?


------------------------------------------
nick.evans
network.engineering
NextVenue, Inc.
phone: (212) 909.2988
pager: (888) 642.5541

------_=_NextPart_001_01BFE765.1217DC50-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 9:28:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 2647037BBFA; Thu, 6 Jul 2000 09:28:25 -0700 (PDT) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id DC40A3E4A; Thu, 6 Jul 2000 18:28:20 +0200 (CEST) Date: Thu, 6 Jul 2000 18:28:20 +0200 From: Jesper Skriver To: Nick Evans Cc: "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging Message-ID: <20000706182820.B54678@skriver.dk> References: <712384017032D411AD7B0001023D799B07C96A@SN1EXCHMBX> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <712384017032D411AD7B0001023D799B07C96A@SN1EXCHMBX>; from nevans@nextvenue.com on Thu, Jul 06, 2000 at 12:13:07PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 06, 2000 at 12:13:07PM -0400, Nick Evans wrote: > Correct me if I am wrong, but isn't bridging of two interfaces supposed to > make a duplicate of the traffic from one onto another? Why is it then that > on the second interface I bridge to I only see broadcast and multicast > packets? I have fxp0 and fxp1 acting as a bridge, fxp0 sees all kinds of > http traffic, napster, IM, etc. but fxp1 sees only multi/broadcast packets. Bridging will only bridge unicast packet's who's destination MAC adress is on the other side of the bridge. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 9:34: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 6537437C3F6; Thu, 6 Jul 2000 09:33:54 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id MAA16071; Thu, 6 Jul 2000 12:34:49 -0400 (EDT) Message-Id: <200007061634.MAA16071@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 06 Jul 2000 12:43:51 -0400 To: Mike Smith From: Dennis Subject: Re: stray interrupts in 4.0 Cc: hackers@freebsd.org In-Reply-To: <200007060054.RAA00500@mass.osd.bsdi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> We're seeing lots of "stray" interrupts in 4.0 while running 3.4 on the >> >> same hardware reports nothing. The interrupt its complaining about is IRQ7 >> >> even though parallel port is disabled and no other device. It happens on >> >> more than 1 MB. [snip] > >Generally this message indicates that you have hardware in the system >that is not signalling interrupts correctly. great, so intel doesnt know how to make MBs with their own parts...so how can the message be turned off. Its using more resources printing the message thsn the "stray interrupts" themselves. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 9:44: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 5149237C483; Thu, 6 Jul 2000 09:43:59 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id MAA16116; Thu, 6 Jul 2000 12:44:54 -0400 (EDT) Message-Id: <200007061644.MAA16116@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 06 Jul 2000 12:53:56 -0400 To: Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" From: Dennis Subject: Re: bridging In-Reply-To: <712384017032D411AD7B0001023D799B07C96A@SN1EXCHMBX> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:13 PM 7/6/00 -0400, Nick Evans wrote: > > Correct me if I am wrong, but isn't bridging of two interfaces supposed to > make a duplicate of the traffic from one onto another? Why is it then that on > the second interface I bridge to I only see broadcast and multicast packets? > I have fxp0 and fxp1 acting as a bridge, fxp0 sees all kinds of http traffic, > napster, IM, etc. but fxp1 sees only multi/broadcast packets. Bridges only forward traffic that it thinks it need to...broadcasts, TO known devices and TO unknown devices.It doesnt forward traffic that it knows is destined for the local network. dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 9:46:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id 8B62A37C413 for ; Thu, 6 Jul 2000 09:46:34 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id JAA25850 for ; Thu, 6 Jul 2000 09:46:32 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <3964B7E8.CC0E2E99@gorean.org> Date: Thu, 06 Jul 2000 09:46:32 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0702 i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: [Fwd: Re: Cant build 3.5-stable?] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Reports about this are getting more frequent, FYI. -------- Original Message -------- Subject: Re: Cant build 3.5-stable? Date: Thu, 06 Jul 2000 11:36:16 -0400 From: Daniel Frazier Organization: Magpage Internet Services To: freebsd-stable@freebsd.org References: Adam wrote: > > I am trying to build 3.5-stable on a 3.4-stable system of about two > months old. /usr/src/UPDATING is empty. Can anyone throw a clue or patch > my way? > Sorry Adam, can't help you. CVSupped last night. make buildworld is dying for me at exactly the same point. I hope this gets fixed soon. ===> libfetch compile_et /usr/src/lib/libfetch/fetch_err.et cc -O -pipe -I. -Wall -pedantic -DNDEBUG -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libfetch/fetch.c -o fetch.o In file included from /usr/src/lib/libfetch/fetch.h:34, from /usr/src/lib/libfetch/fetch.c:39: fetch_err.h:6: com_right.h: No such file or directory In file included from /usr/src/lib/libfetch/fetch.h:34, from /usr/src/lib/libfetch/fetch.c:39: fetch_err.h:8: warning: `struct et_list' declared inside parameter list fetch_err.h:8: warning: its scope is only this definition or declaration, fetch_err.h:8: warning: which is probably not what you want. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. ---------------------------------------------------------------------- Daniel Frazier Tel: 302-239-5900 Ext. 231 System Administrator Fax: 302-239-3909 MAGPAGE, We Power the Internet WWW: http://www.magpage.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" 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 Jul 6 10:14:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wiz.plymouth.edu (ness.plymouth.edu [158.136.1.140]) by hub.freebsd.org (Postfix) with ESMTP id 3F07337BBEF; Thu, 6 Jul 2000 10:14:25 -0700 (PDT) (envelope-from ted@wiz.plymouth.edu) Received: (from ted@localhost) by wiz.plymouth.edu (8.10.2/8.10.0) id e66HE6B85065; Thu, 6 Jul 2000 13:14:06 -0400 (EDT) From: Ted Wisniewski Message-Id: <200007061714.e66HE6B85065@wiz.plymouth.edu> Subject: Re: bridging In-Reply-To: <20000706182820.B54678@skriver.dk> from Jesper Skriver at "Jul 6, 2000 06:28:20 pm" To: jesper@skriver.dk (Jesper Skriver) Date: Thu, 6 Jul 2000 13:14:06 -0400 (EDT) Cc: nevans@nextvenue.com (Nick Evans), freebsd-hackers@FreeBSD.ORG ('freebsd-hackers@freebsd.org'), freebsd-net@FreeBSD.ORG ('freebsd-net@freebsd.org') X-Mailer: ELM [version 2.4ME+ PL54 (25)] 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 (* On Thu, Jul 06, 2000 at 12:13:07PM -0400, Nick Evans wrote: (* > Correct me if I am wrong, but isn't bridging of two interfaces supposed to (* > make a duplicate of the traffic from one onto another? Why is it then that (* > on the second interface I bridge to I only see broadcast and multicast (* > packets? I have fxp0 and fxp1 acting as a bridge, fxp0 sees all kinds of (* > http traffic, napster, IM, etc. but fxp1 sees only multi/broadcast packets. (* (* Bridging will only bridge unicast packet's who's destination MAC adress is (* on the other side of the bridge. How about RIP? I recently tried to upgrade my FreeBSD 4.0 bridging-firewall to CURRENT and I could no longer get RIP packets through (reliably) (even with no rules and "DEFAULT_TOACCEPT") and had all kinds of routing problems... Routers could not learn the route out because RIP was not going through. Of course I backed back off to 4.0-RELEASE and life was good again... I sent in a PR but have not heard anything yet. Advice? Thanks -- | Ted Wisniewski INET: ted@oz.plymouth.edu | | Computer Services ted@wiz.plymouth.edu | | Plymouth State College tedw@tigger.plymouth.edu | | Plymouth NH, 03264 HTTP: http://oz.plymouth.edu/~ted/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 10:33:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from athena.lightningone.net (athena.lightningone.net [12.34.104.3]) by hub.freebsd.org (Postfix) with ESMTP id CDC1037B792; Thu, 6 Jul 2000 10:33:33 -0700 (PDT) (envelope-from john@essenz.com) Received: from localhost (john@localhost) by athena.lightningone.net (8.9.3/8.9.3) with ESMTP id NAA53137; Thu, 6 Jul 2000 13:53:41 -0400 (EDT) (envelope-from john@essenz.com) X-Authentication-Warning: athena.lightningone.net: john owned process doing -bs Date: Thu, 6 Jul 2000 13:53:41 -0400 (EDT) From: Essenz Consulting X-Sender: john@athena.lightningone.net To: hardware@freebsd.org, hackers@freebsd.org Subject: UPS Daemons 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 know that APC SmartUPS and BackUPS are supported under FreeBSD but what about the APC PowerStack? I was looking at the APC PowerStack 250 Rackmount UPS. It comes with a RS-232 cables and supports that same kind of emergency shutdown that the SmartUPS systems have. Anybody use a PowerStack? I would only use if I knew that I could tie it in to FreeBSD for automatic shutdown when battery power is used up. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 11: 9:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7C93737C11D for ; Thu, 6 Jul 2000 11:09:15 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA94737; Thu, 6 Jul 2000 11:09:08 -0700 (PDT) (envelope-from dillon) Date: Thu, 6 Jul 2000 11:09:08 -0700 (PDT) From: Matthew Dillon Message-Id: <200007061809.LAA94737@apollo.backplane.com> To: David Greenman Cc: Bosko Milekic , freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf re-write(s), v 0.1 References: <200007030221.TAA08654@implode.root.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :... :> What was previously done at some point was use the kernel malloc() to :> allocate mbufs. As you know, this is a general purpose allocator that has :> to first determine what algorithm to use and then store the object :> correctly according to its size. This allocator is faster than that :> one. This allocator knows that it only has to deal with mbufs and knows :> that all of these mbufs are of the same size. : : Yes, malloc is slow for other reasons, but it is especially slow when VM :pages are freed back to the general pool. Of course it is possible to :introduce hysteresis in the algorithm such that it doesn't free the pages as :often, but this (and all the tunables that you proposed) has the negative :effect of making the allocator more complex. We've tried very hard not to do :this in the current mbuf allocator, making it nearly as efficient as you can :get. : I guess I just don't see the problem on any of the servers that I manage :(ftp.cdrom.com and ftp.freesoftware.com, for example). There are peaks in :usage, but they tend to reach the peaks often enough that freeing the pages :for short term memory gain is just a waste of CPU cycles. Memory is so cheap :these days that throwing memory at the problem seems to be a very reasonable :solution, especially when the system clearly needs it during the peaks. : :-DG : :David Greenman Our userland malloc() has been quite successful using MADV_FREE to 'release' free pages without actually releasing them. The system would reclaim the pages only when it needed them. We might be able to do something similar for our kernelland malloc, though at the moment I don't see much of a point (it seems fast enough to me and I don't see much wasteage either). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 12:16:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id C6D0A37B9B0 for ; Thu, 6 Jul 2000 12:16:35 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 55923 invoked by uid 1000); 6 Jul 2000 19:16:32 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Jul 2000 19:16:32 -0000 Date: Thu, 6 Jul 2000 14:16:32 -0500 (CDT) From: Mike Silbersack To: Dennis Cc: Mike Smith , hackers@freebsd.org Subject: Re: stray interrupts in 4.0 In-Reply-To: <200007061634.MAA16071@etinc.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 Thu, 6 Jul 2000, Dennis wrote: > great, so intel doesnt know how to make MBs with their own parts...so how > can the message be turned off. Its using more resources printing the > message thsn the "stray interrupts" themselves. > > DB Well, it stops after 5 messages or so, just ignore it. Actually, one of my systems stopped doing it a few months back, I have no clue why. Either way, I wouldn't worry about it. 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 Thu Jul 6 12:19:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id D688C37C2D0 for ; Thu, 6 Jul 2000 12:19:08 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id A81FF1C65; Thu, 6 Jul 2000 15:19:07 -0400 (EDT) Date: Thu, 6 Jul 2000 15:19:07 -0400 From: Bill Fumerola To: Michael Lucas Cc: hackers@FreeBSD.org Subject: Re: cocaine snorting reported in Michigan, details at 11 (was Re: data corruption) Message-ID: <20000706151907.K4034@jade.chc-chimes.com> References: <20000705210823.V4034@jade.chc-chimes.com> <200007061246.IAA50548@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200007061246.IAA50548@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Thu, Jul 06, 2000 at 08:46:10AM -0400 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 06, 2000 at 08:46:10AM -0400, Michael Lucas wrote: > > I fully expect to be physically assulted by all who I encounter the > > next time I'm in California for this act of stupidity. > > Physically assaulted? No, why do that when we can point and laugh? > It's legal, and much more devastating. > > Just noticed you're in Michigan. Are you aware of any Michigan > FreeBSD groups? I've been looking around Detroit for a while, and > haven't found any. There was talks of starting a Southeastern Michigan group, but most of us around here are too lazy to actually do it. -- Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES e-mail: billf@chimesnet.com / billf@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 Jul 6 12:30:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id C73EE37C316; Thu, 6 Jul 2000 12:30:14 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id PAA52413; Thu, 6 Jul 2000 15:30:13 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200007061930.PAA52413@blackhelicopters.org> Subject: Southeast MI users' group (was re: cocaine snorting in Michigan) In-Reply-To: <20000706151907.K4034@jade.chc-chimes.com> from Bill Fumerola at "Jul 6, 2000 3:19: 7 pm" To: billf@chimesnet.com (Bill Fumerola) Date: Thu, 6 Jul 2000 15:30:13 -0400 (EDT) Cc: hackers@freebsd.org, advocacy@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] 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 > > There was talks of starting a Southeastern Michigan group, but most > of us around here are too lazy to actually do it. > I'll take on the job of attempting to coordinate a Southeast Michigan users' group. If anyone's interested, email me. Perhaps the Royal Oak or Farmington Hills area? They're somewhat central, with any number of decent restaurants/bars/whatnot for an initial meeting. Followups to, uh, -advocacy, I suppose. ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 12:31:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 6317937B9D0; Thu, 6 Jul 2000 12:31:20 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id A81F81C65; Thu, 6 Jul 2000 15:31:19 -0400 (EDT) Date: Thu, 6 Jul 2000 15:31:19 -0400 From: Bill Fumerola To: Adam , Michael Lucas , advocacy@freebsd.org Subject: Re: cocaine snorting reported in Michigan, details at 11 (was Re: data corruption) Message-ID: <20000706153119.L4034@jade.chc-chimes.com> References: <200007061246.IAA50548@blackhelicopters.org> <20000706115129.B74002@goku.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000706115129.B74002@goku.cl.msu.edu>; from dervish@goku.cl.msu.edu on Thu, Jul 06, 2000 at 11:51:29AM -0400 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ moved to -advocacy from -hackers ] On Thu, Jul 06, 2000 at 11:51:29AM -0400, Bush Doctor wrote: > > I keep mentioning to bill and others on irc from michigan that someone > > should start one :p > Well if anyone is ever down East Lansing way, a couple of co-workers > and I have an informal group. Everyone is more than welcome to come > here or maybe we could meet somewhere in between ... There's also a large OpenBSD assembly of people at UofM. -- Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES e-mail: billf@chimesnet.com / billf@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 Jul 6 12:53:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id A475337C22C for ; Thu, 6 Jul 2000 12:53:38 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id PAA01656 for ; Thu, 6 Jul 2000 15:53:37 -0400 (EDT) Date: Thu, 6 Jul 2000 15:51:34 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Max DMA size 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 Can anyone tell me what factors determine the max DMA size (DMA counter on each controller or PCI bus related)? What is the typical max DMA size for a SCSI disk connected to a PCI bus? It seems to be much larger than MAXPHYS (128K). If so, does it mean we are not using full potential of DMA? So what's the problem if we enlarge MAXPHYS? Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 13: 0:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 25C6737B61A for ; Thu, 6 Jul 2000 13:00:21 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA13756; Thu, 6 Jul 2000 13:00:12 -0700 Date: Thu, 6 Jul 2000 13:00:11 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Max DMA size 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 > > Can anyone tell me what factors determine the max DMA size (DMA counter on > each controller or PCI bus related)? What is the typical max DMA size for > a SCSI disk connected to a PCI bus? It seems to be much larger than > MAXPHYS (128K). If so, does it mean we are not using full potential of > DMA? So what's the problem if we enlarge MAXPHYS? You can enlarge MAXPHYS, but watch out that you don't also then make MAXBSIZE so big that the creation of buffers eats up all of your memory. IMO MAXPHYS is way too small, but there are a number of current VM implementation reasons why making it larger by default is not right. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 13:38: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.weyerhaeuser.com (mail1.weyerhaeuser.com [208.247.148.1]) by hub.freebsd.org (Postfix) with ESMTP id C8AFD37B612 for ; Thu, 6 Jul 2000 13:38:06 -0700 (PDT) (envelope-from comish@weyerhaeuser.com) Received: by mail1.weyerhaeuser.com with Internet Mail Service (5.5.2650.21) id ; Thu, 6 Jul 2000 13:34:37 -0700 Message-ID: <6BDA45469076D1118F7300805F57DDD152F889@emssk1.weyer.com> From: Commissionnaires To: "'freebsd-hackers@freebsd.org'" Subject: Learning Date: Thu, 6 Jul 2000 13:34:35 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am interested in learning about the freebsd operating system, I dont have very much exerience yet but I am motivated to learn. I have poked around other OS but have found them unappealing to my interest, I like the concept of free source systems like linux and have played with SUSE a little but found the limited availability of learning materials in english a hinderance. I have downloaded and printed the manual as of page 34 where I came upon your invitation I decided to reach out and touch someone. I woud like some quick advice as to what version I should install via ftp to begin my learning, and what would be the best path to follow. I am particularily interested in learning to program in an acceptable language and want to concentrate on network protocols and reliable secure communications, as well as network security and firewalls. Thank you for any advice that you can offer. Arnold Murphy amurphy@sk.sympatico.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 13:47:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 5A32737B618 for ; Thu, 6 Jul 2000 13:47:23 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA25569; Thu, 6 Jul 2000 14:47:06 -0600 (MDT) (envelope-from ken) Date: Thu, 6 Jul 2000 14:47:06 -0600 From: "Kenneth D. Merry" To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Max DMA size Message-ID: <20000706144706.A25372@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from zzhang@cs.binghamton.edu on Thu, Jul 06, 2000 at 03:51:34PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 06, 2000 at 15:51:34 -0400, Zhihui Zhang wrote: > > Can anyone tell me what factors determine the max DMA size (DMA counter on > each controller or PCI bus related)? What is the typical max DMA size for > a SCSI disk connected to a PCI bus? It seems to be much larger than > MAXPHYS (128K). If so, does it mean we are not using full potential of > DMA? So what's the problem if we enlarge MAXPHYS? > > Any help is appreciated. MAXPHYS determines the size of struct buf, which at the moment determines the maximum size of a given DMA transaction to a SCSI controller. Typical modern SCSI controllers can handle much more than MAXPHYS data (currently 128K) at a time. An exception is the Adaptec 154x controllers, which can only handle about 64K of data. (Thus the reason I/O through the CAM passthrough interface is limited to 64K instead of the full 128K. We will have that limitation until we implement a way of determining the maximum DMA size allowable for a given controller.) However, as Matt said, you have to be careful about increasing MAXPHYS too much, since you could end up allocating too much memory. I think a better approach to increasing the amount of data that can be sent at one time to a SCSI controller would be to implement some sort of buffer chaining scheme. Most SCSI controllers can do scatter/gather DMA, and CAM has facilities for it, so that would probably be the easiest way to go. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 13:50:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jasper.heartland.ab.ca (jasper.heartland.ab.ca [207.107.228.1]) by hub.freebsd.org (Postfix) with ESMTP id 770BD37B520 for ; Thu, 6 Jul 2000 13:50:40 -0700 (PDT) (envelope-from dkwiebe@hagenhomes.com) Received: from hagenhomes.com (dyn119.heartland.ab.ca [207.107.228.119]) by jasper.heartland.ab.ca (8.9.0/8.9.0) with ESMTP id OAA13698; Thu, 6 Jul 2000 14:49:12 -0600 (MDT) Message-ID: <39649CBB.F9234C1C@hagenhomes.com> Date: Thu, 06 Jul 2000 14:50:35 +0000 From: Darren Wiebe Organization: Hagen Homes Ltd. X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Commissionnaires Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: Learning References: <6BDA45469076D1118F7300805F57DDD152F889@emssk1.weyer.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Congratulations, I wish you much luck. I presume, from your email address, that you work for Weyerhauser? I think that I might know one of the salesmen there, he used to work for Mac Blo and come to our store but got transfered from Edmonton to Saskatoon. Anyway, I would install 4.0 release and play with that for a while then upgrade to -stable or -current. BTW if you would like, I can lend you my 4.0 cd's for a week. I'm in central AB and could mail them to you, that would save a lot of time in downloading, unless you have a really fast connection. Darren Wiebe dkwiebe@hagenhomes.com Commissionnaires wrote: > > I am interested in learning about the freebsd operating system, I dont have > very much exerience yet but I am motivated to learn. I have poked around > other OS but have found them unappealing to my interest, I like the concept > of free source systems like linux and have played with SUSE a little but > found the limited availability of learning materials in english a > hinderance. I have downloaded and printed the manual as of page 34 where I > came upon your invitation I decided to reach out and touch someone. I woud > like some quick advice as to what version I should install via ftp to begin > my learning, and what would be the best path to follow. I am particularily > interested in learning to program in an acceptable language and want to > concentrate on network protocols and reliable secure communications, as well > as network security and firewalls. > > Thank you for any advice that you can offer. > > Arnold Murphy > > amurphy@sk.sympatico.ca > > 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 Jul 6 15:16:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 0B5C237B88A for ; Thu, 6 Jul 2000 15:16:16 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id SAA14468; Thu, 6 Jul 2000 18:16:15 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Thu, 6 Jul 2000 18:16:14 -0400 (EDT) From: Adam To: Bush Doctor Cc: Michael Lucas , Bill Fumerola , hackers@FreeBSD.ORG Subject: Re: cocaine snorting reported in Michigan, details at 11 (was Re: data corruption) In-Reply-To: <20000706115129.B74002@goku.cl.msu.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 Thu, 6 Jul 2000, Bush Doctor wrote: >Out of da blue Adam aka (bsdx@looksharp.net) said: >> On Thu, 6 Jul 2000, Michael Lucas wrote: >> >> >> >> >> I fully expect to be physically assulted by all who I encounter the >> >> next time I'm in California for this act of stupidity. >> >> >> > >> >Physically assaulted? No, why do that when we can point and laugh? >> >It's legal, and much more devastating. >> > >> >Just noticed you're in Michigan. Are you aware of any Michigan >> >FreeBSD groups? I've been looking around Detroit for a while, and >> >haven't found any. >> > >> >==ml >> >> I keep mentioning to bill and others on irc from michigan that someone >> should start one :p >Well if anyone is ever down East Lansing way, a couple of co-workers >and I have an informal group. Everyone is more than welcome to come >here or maybe we could meet somewhere in between ... > >bush doctor > Oh really! Why didnt Ed ever tell me about it! I'd assume he knows because he works at cl ;) (I work at egr) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 17:16:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id DB60837BA82 for ; Thu, 6 Jul 2000 17:16:31 -0700 (PDT) (envelope-from root@gits.dyndns.org) Received: (qmail 9408691 invoked from network); 7 Jul 2000 00:16:29 -0000 Received: from r224m65.cybercable.tm.fr (HELO gits.dyndns.org) ([195.132.224.65]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 7 Jul 2000 00:16:29 -0000 Received: (from root@localhost) by gits.dyndns.org (8.9.3/8.9.3) id CAA24161; Fri, 7 Jul 2000 02:16:28 +0200 (CEST) (envelope-from root) Posted-Date: Fri, 7 Jul 2000 02:16:28 +0200 (CEST) To: Essenz Consulting Cc: hardware@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: UPS Daemons References: Reply-To: clefevre@citeweb.net X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C From: Cyrille Lefevre Date: 07 Jul 2000 02:16:27 +0200 In-Reply-To: Essenz Consulting's message of "Thu, 6 Jul 2000 13:53:41 -0400 (EDT)" Message-ID: Lines: 48 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Canyonlands" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Essenz Consulting writes: > I know that APC SmartUPS and BackUPS are supported under FreeBSD but what > about the APC PowerStack? I was looking at the APC PowerStack 250 > Rackmount UPS. It comes with a RS-232 cables and supports that same kind > of emergency shutdown that the SmartUPS systems have. Anybody use a > PowerStack? I would only use if I knew that I could tie it in to FreeBSD > for automatic shutdown when battery power is used up. I don't have a SmartUPS system but a BackUPS, so I use bkupsd. you should probably use something like : Port: upsd-2.0.1.6 Path: /usr/ports/sysutils/upsd Info: APC Smart UPS Monitoring Daemon Maint: ports@FreeBSD.org Index: sysutils or Port: upsmon-2.1.3 Path: /usr/ports/sysutils/upsmon Info: Basic UPS monitor for the APC SmartUPS devices Maint: ports@FreeBSD.org Index: sysutils as "make search key=ups" in /usr/ports says :) links and descriptions are respectively : MASTER_SITES= ftp://www.ww.net/pub/wildwind/upsd/ \ http://www.cre8tivegroup.com/ \ ftp://ftp.sw.ru/pub/unix/upsd/ upsd is a daemon with flexible configuration which lets you to shutdown your system properly when source power line fails and measure its frequency, voltage etc MASTER_SITES= ftp://newcorridor.com/pub/upsmon/ Designed specifically for the APC SmartUPS devices, the software is dependent on the SmartUPS interface and will only function with SmartUPS devices. Cyrille. -- home:mailto:clefevre@no-spam.citeweb.net Supprimer "no-spam." pour me repondre. work:mailto:Cyrille.Lefevre@no-spam.edf.fr Remove "no-spam." to answer me back. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 17:27:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id E5AFC37B94C for ; Thu, 6 Jul 2000 17:27:54 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id TAA36202; Thu, 6 Jul 2000 19:44:44 -0500 (CDT) From: Joe Greco Message-Id: <200007070044.TAA36202@aurora.sol.net> Subject: Re: cocaine snorting reported in Michigan, details at 11 (was Re: data corruption) To: dervish@goku.cl.msu.edu Date: Thu, 6 Jul 2000 19:44:44 -0500 (CDT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] 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 > Well if anyone is ever down East Lansing way, a couple of co-workers > and I have an informal group. Everyone is more than welcome to come > here or maybe we could meet somewhere in between ... I always wondered why the Voyager Michigan guys were a little screwy :-) (incidentally also located in East Lansing) -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 17:29:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id 0414E37BADC for ; Thu, 6 Jul 2000 17:29:18 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 56868 invoked by uid 1000); 7 Jul 2000 00:29:16 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jul 2000 00:29:16 -0000 Date: Thu, 6 Jul 2000 19:29:16 -0500 (CDT) From: Mike Silbersack To: Doug Barton Cc: hackers@freebsd.org, stable@freebsd.org Subject: Re: [Fwd: Re: Cant build 3.5-stable?] In-Reply-To: <3964B7E8.CC0E2E99@gorean.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 The problem seems to stem from a corrupt /usr/obj/usr/src/lib/libfetch/fetch_err.h If I manually delete it and make from the libfetch directory, it seems to be created properly. So, I have two lingering questions: 1. Did the tools used to create the file change? As far as I can tell, libfetch itself did _not_ change from 3.4 to 3.5. 2. Why isn't the file auto-cleaned? On the other hand, I haven't run a full buildworld yet, so it could be something else in the build process casuing the problem. Details after it finishes. Mike "Silby" Silbersack On Thu, 6 Jul 2000, Doug Barton wrote: > Reports about this are getting more frequent, FYI. > > -------- Original Message -------- > Subject: Re: Cant build 3.5-stable? > Date: Thu, 06 Jul 2000 11:36:16 -0400 > From: Daniel Frazier > Organization: Magpage Internet Services > To: freebsd-stable@freebsd.org > References: > > > Adam wrote: > > > > I am trying to build 3.5-stable on a 3.4-stable system of about two > > months old. /usr/src/UPDATING is empty. Can anyone throw a clue or patch > > my way? > > > > Sorry Adam, can't help you. CVSupped last night. make buildworld is > dying > for me at exactly the same point. I hope this gets fixed soon. > > ===> libfetch > compile_et /usr/src/lib/libfetch/fetch_err.et > cc -O -pipe -I. -Wall -pedantic -DNDEBUG > -I/usr/obj/usr/src/tmp/usr/include -c > /usr/src/lib/libfetch/fetch.c -o fetch.o > In file included from /usr/src/lib/libfetch/fetch.h:34, > from /usr/src/lib/libfetch/fetch.c:39: > fetch_err.h:6: com_right.h: No such file or directory > In file included from /usr/src/lib/libfetch/fetch.h:34, > from /usr/src/lib/libfetch/fetch.c:39: > fetch_err.h:8: warning: `struct et_list' declared inside parameter list > fetch_err.h:8: warning: its scope is only this definition or > declaration, > fetch_err.h:8: warning: which is probably not what you want. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > > ---------------------------------------------------------------------- > Daniel Frazier Tel: 302-239-5900 Ext. 231 > System Administrator Fax: 302-239-3909 > MAGPAGE, We Power the Internet WWW: http://www.magpage.com/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the 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 Jul 6 18:46: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id F32D637BC0F for ; Thu, 6 Jul 2000 18:45:53 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 43891 invoked by uid 1000); 7 Jul 2000 01:45:50 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jul 2000 01:45:50 -0000 Date: Thu, 6 Jul 2000 20:45:50 -0500 (CDT) From: Mike Silbersack To: Doug Barton Cc: hackers@freebsd.org, stable@freebsd.org Subject: Re: [Fwd: Re: Cant build 3.5-stable?] 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 Ok, the problem seems to stem from the fact that if I do a buildworld, I get the following: achilles# vi /usr/obj/usr/src/lib/libfetch/fetch_err.h /* Generated from /usr/src/lib/libfetch/fetch_err.et */ #ifndef __fetch_err_h__ #define __fetch_err_h__ #include void initialize_ftch_error_table_r(struct et_list **); void initialize_ftch_error_table(void); #define init_ftch_err_tbl initialize_ftch_error_table typedef enum ftch_error_number{ ERROR_TABLE_BASE_ftch = -2098765312, ftch_err_base = -2098765312, FETCH_ABORT = -2098765312, FETCH_AUTH = -2098765311, FETCH_DOWN = -2098765310, FETCH_EXISTS = -2098765309, FETCH_FULL = -2098765308, FETCH_INFO = -2098765307, FETCH_MEMORY = -2098765306, (etc) You may note that this differs greatly from what you get if you just go into /usr/src/lib/libfetch and make clean ; make. Anyone with a better knowledge of the buildworld process have any ideas? Mike "Silby" Silbersack On Thu, 6 Jul 2000, Mike Silbersack wrote: > The problem seems to stem from a corrupt > /usr/obj/usr/src/lib/libfetch/fetch_err.h > > If I manually delete it and make from the libfetch directory, it seems > to be created properly. > > So, I have two lingering questions: > > 1. Did the tools used to create the file change? As far as I can tell, > libfetch itself did _not_ change from 3.4 to 3.5. > > 2. Why isn't the file auto-cleaned? > > On the other hand, I haven't run a full buildworld yet, so it could be > something else in the build process casuing the problem. Details after it > finishes. > > 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 Thu Jul 6 19:16: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id 1D23037BE9D for ; Thu, 6 Jul 2000 19:15:54 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 44099 invoked by uid 1000); 7 Jul 2000 02:15:51 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jul 2000 02:15:51 -0000 Date: Thu, 6 Jul 2000 21:15:51 -0500 (CDT) From: Mike Silbersack To: Doug Barton Cc: hackers@freebsd.org, stable@freebsd.org, kris@freebsd.org, markm@freebsd.org, assar@freebsd.org Subject: Re: [Fwd: Re: Cant build 3.5-stable?] 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 Ok, the problem seems to be that the new version of compile_et which was MFC'd is creating broken header files, it just happens that libfetch is the first part of the buildworld that hits it. According to cvs: 1.2.2.2 Tue Jul 4 15:15:12 2000 UTC by assar Branch: RELENG_3 Diffs to 1.2.2.1 FILE REMOVED merge differences from -current and build this from ../../contrib/com_err Reviewed by: kris, markm Go to work, guys! Mike "Silby" Silbersack On Thu, 6 Jul 2000, Mike Silbersack wrote: > Ok, the problem seems to stem from the fact that if I do a buildworld, I > get the following: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 20: 1: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.lewman.org (lowrider.lewman.org [209.67.240.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F55937B612; Thu, 6 Jul 2000 20:00:55 -0700 (PDT) (envelope-from sean@rentul.net) Received: by mail.lewman.org (Postfix, from userid 1004) id 82A0B3D32; Thu, 6 Jul 2000 23:01:58 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.lewman.org (Postfix) with ESMTP id 7DB9F5BC4; Thu, 6 Jul 2000 23:01:58 -0400 (EDT) Date: Thu, 6 Jul 2000 23:01:58 -0400 (EDT) From: Sean Lutner X-Sender: sean@lowrider.lewman.org To: Nick Evans Cc: "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging In-Reply-To: <712384017032D411AD7B0001023D799B07C96A@SN1EXCHMBX> 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 Bridges create a broadcast zone. broadcast packets will cross the bridge unobstructed. On Thu, 6 Jul 2000, Nick Evans wrote: > Correct me if I am wrong, but isn't bridging of two interfaces supposed to > make a duplicate of the traffic from one onto another? Why is it then that > on the second interface I bridge to I only see broadcast and multicast > packets? I have fxp0 and fxp1 acting as a bridge, fxp0 sees all kinds of > http traffic, napster, IM, etc. but fxp1 sees only multi/broadcast packets. > > any ideas? > > > ------------------------------------------ > nick.evans > network.engineering > NextVenue, Inc. > phone: (212) 909.2988 > pager: (888) 642.5541 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 20:36:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 92E2337B5F6; Thu, 6 Jul 2000 20:36:35 -0700 (PDT) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id FAA59616; Fri, 7 Jul 2000 05:36:48 +0200 (CEST) (envelope-from assar) To: Mike Silbersack Cc: Doug Barton , hackers@freebsd.org, stable@freebsd.org, kris@freebsd.org, markm@freebsd.org Subject: Re: [Fwd: Re: Cant build 3.5-stable?] References: From: Assar Westerlund Date: 07 Jul 2000 05:36:47 +0200 In-Reply-To: Mike Silbersack's message of "Thu, 6 Jul 2000 21:15:51 -0500 (CDT)" Message-ID: <5lem561ui8.fsf@assaris.sics.se> Lines: 30 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Silbersack writes: > Ok, the problem seems to be that the new version of compile_et which was > MFC'd is creating broken header files, it just happens that libfetch is > the first part of the buildworld that hits it. Please try the following patch. It will get comitted when my buildworld has completed (successfully). /assar Index: src/lib/libcom_err/Makefile =================================================================== RCS file: /home/ncvs/src/lib/libcom_err/Makefile,v retrieving revision 1.8.2.2 diff -u -w -u -w -r1.8.2.2 Makefile --- src/lib/libcom_err/Makefile 2000/07/04 15:13:05 1.8.2.2 +++ src/lib/libcom_err/Makefile 2000/07/07 03:35:57 @@ -9,6 +9,12 @@ SUBDIR= doc +beforeinstall: + ${INSTALL} -C -o ${BINOWN} -g ${BINGRP} -m 444 \ + ${COM_ERRDIR}/com_err.h ${DESTDIR}/usr/include + ${INSTALL} -C -o ${BINOWN} -g ${BINGRP} -m 444 \ + ${COM_ERRDIR}/com_right.h ${DESTDIR}/usr/include + .include .PATH: ${COM_ERRDIR} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 21: 6:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id A66A437BC8B; Thu, 6 Jul 2000 21:06:11 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id WAA67421; Thu, 6 Jul 2000 22:05:29 -0600 (MDT) Date: Thu, 6 Jul 2000 22:05:29 -0600 (MDT) From: Nick Rogness To: Sean Lutner Cc: Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging 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 Thu, 6 Jul 2000, Sean Lutner wrote: > > Bridges create a broadcast zone. broadcast packets will cross the bridge > unobstructed. OK. So do bridged interfaces fall within the same collision domain?... or are they just members of the same broadcast domain? Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 21:57: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 9A43C37B6AA; Thu, 6 Jul 2000 21:56:58 -0700 (PDT) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id GAA59736; Fri, 7 Jul 2000 06:56:56 +0200 (CEST) (envelope-from assar) To: Mike Silbersack Cc: Doug Barton , hackers@FreeBSD.ORG, stable@FreeBSD.ORG, kris@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: [Fwd: Re: Cant build 3.5-stable?] References: <5lem561ui8.fsf@assaris.sics.se> From: Assar Westerlund Date: 07 Jul 2000 06:56:56 +0200 In-Reply-To: Assar Westerlund's message of "07 Jul 2000 05:36:47 +0200" Message-ID: <5lituizgfb.fsf@assaris.sics.se> Lines: 8 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > Please try the following patch. It will get comitted when my > buildworld has completed (successfully). And my buildworld suceeded so the patch has been comitted as version 1.8.2.3 /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 22: 6:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 9EBF137BD62; Thu, 6 Jul 2000 22:06:05 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id BAA02186; Fri, 7 Jul 2000 01:05:06 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Fri, 7 Jul 2000 01:05:06 -0400 (EDT) From: "Brandon D. Valentine" To: Assar Westerlund Cc: Mike Silbersack , Doug Barton , hackers@FreeBSD.ORG, stable@FreeBSD.ORG, kris@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: [Fwd: Re: Cant build 3.5-stable?] In-Reply-To: <5lituizgfb.fsf@assaris.sics.se> 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 7 Jul 2000, Assar Westerlund wrote: >I wrote: >> Please try the following patch. It will get comitted when my >> buildworld has completed (successfully). > >And my buildworld suceeded so the patch has been comitted as version >1.8.2.3 Thanks for taking care of it so quickly Assar. My buildworld has also gotten past the point it died before with that Makefile patch. Looks good. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 22: 7:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id 61EFB37BC65 for ; Thu, 6 Jul 2000 22:07:17 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 25207 invoked by uid 1000); 7 Jul 2000 05:07:15 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jul 2000 05:07:15 -0000 Date: Fri, 7 Jul 2000 00:07:15 -0500 (CDT) From: Mike Silbersack To: Assar Westerlund Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: [Fwd: Re: Cant build 3.5-stable?] In-Reply-To: <5lituizgfb.fsf@assaris.sics.se> 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 7 Jul 2000, Assar Westerlund wrote: > I wrote: > > Please try the following patch. It will get comitted when my > > buildworld has completed (successfully). > > And my buildworld suceeded so the patch has been comitted as version > 1.8.2.3 > > /assar Thanks for the quick fix. LET THE BUILDING BEGIN! 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 Thu Jul 6 22: 8: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cummings.uol.com.br (cummings.uol.com.br [200.230.198.69]) by hub.freebsd.org (Postfix) with ESMTP id 5805237BA58 for ; Thu, 6 Jul 2000 22:07:52 -0700 (PDT) (envelope-from sergiofr@uol.com.br) Received: from Usuario (PC168.netwaybbs.com.br [200.199.99.168]) by cummings.uol.com.br (8.9.1/8.9.1) with SMTP id CAA23242 for ; Fri, 7 Jul 2000 02:07:39 -0300 (BRT) Message-ID: <001101bfe7d2$d51784e0$a863c7c8@Usuario> From: "Sergio Faustino" To: Subject: driver Date: Fri, 7 Jul 2000 02:18:40 -0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01BFE7B9.AA49EA00" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000E_01BFE7B9.AA49EA00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Sir, To make the QuickCam (grayscale) work with Windows NT machines you must = install an NT driver. I'd like to know as to get this driver. P.S.: I didn't obtain success in the site of Connectix. I thank your attention. ------=_NextPart_000_000E_01BFE7B9.AA49EA00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Dear Sir,
 
To make the QuickCam (grayscale) work = with Windows=20 NT machines you must install an NT driver. I'd like to know as to get = this=20 driver.
 
P.S.: I didn't obtain success in the = site of=20 Connectix.
 
I thank your = attention.
------=_NextPart_000_000E_01BFE7B9.AA49EA00-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 22:36:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4C14B37BC72; Thu, 6 Jul 2000 22:36:07 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA26454; Thu, 6 Jul 2000 23:36:03 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA58718; Thu, 6 Jul 2000 23:35:39 -0600 (MDT) Message-Id: <200007070535.XAA58718@harmony.village.org> To: Dennis Subject: Re: stray interrupts in 4.0 Cc: Mike Smith , hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 Jul 2000 12:43:51 EDT." <200007061634.MAA16071@etinc.com> References: <200007061634.MAA16071@etinc.com> Date: Thu, 06 Jul 2000 23:35:39 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007061634.MAA16071@etinc.com> Dennis writes: : great, so intel doesnt know how to make MBs with their own parts...so how : can the message be turned off. Its using more resources printing the : message thsn the "stray interrupts" themselves. I doubt that. Only about 5 of them are printed then we stop. At least that's what I've seen when I have hardware that is like this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 22:42:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gateway.posi.net (c1096725-a.smateo1.sfba.home.com [24.20.139.104]) by hub.freebsd.org (Postfix) with ESMTP id 575AE37BA6D for ; Thu, 6 Jul 2000 22:42:17 -0700 (PDT) (envelope-from kbyanc@posi.net) Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.9.3/8.9.3) with ESMTP id WAA21858; Thu, 6 Jul 2000 22:45:10 -0700 (PDT) (envelope-from kbyanc@posi.net) Date: Thu, 6 Jul 2000 22:45:09 -0700 (PDT) From: Kelly Yancey To: "Kenneth D. Merry" Cc: Zhihui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: Max DMA size In-Reply-To: <20000706144706.A25372@panzer.kdm.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 On Thu, 6 Jul 2000, Kenneth D. Merry wrote: > On Thu, Jul 06, 2000 at 15:51:34 -0400, Zhihui Zhang wrote: > > > > Can anyone tell me what factors determine the max DMA size (DMA counter on > > each controller or PCI bus related)? What is the typical max DMA size for > > a SCSI disk connected to a PCI bus? It seems to be much larger than > > MAXPHYS (128K). If so, does it mean we are not using full potential of > > DMA? So what's the problem if we enlarge MAXPHYS? > > > > Any help is appreciated. > > MAXPHYS determines the size of struct buf, which at the moment determines > the maximum size of a given DMA transaction to a SCSI controller. > > Typical modern SCSI controllers can handle much more than MAXPHYS data > (currently 128K) at a time. An exception is the Adaptec 154x controllers, > which can only handle about 64K of data. (Thus the reason I/O through the > CAM passthrough interface is limited to 64K instead of the full 128K. We > will have that limitation until we implement a way of determining the > maximum DMA size allowable for a given controller.) > > However, as Matt said, you have to be careful about increasing MAXPHYS too > much, since you could end up allocating too much memory. > > I think a better approach to increasing the amount of data that can be sent > at one time to a SCSI controller would be to implement some sort of buffer > chaining scheme. Most SCSI controllers can do scatter/gather DMA, and CAM > has facilities for it, so that would probably be the easiest way to go. > Hmm. My knowledge may be a bit dated in this matter, but as I recall the 8237 DMA controller standard on PCs only supports DMA requests up to 128k (and then only on the upper 4 DMA channels). The low 4 DMA channels were byte-granular and could only transfer 64k. Am I correct in assuming from this discussion that the state of affairs is somewhat different nowadays? Kelly -- Kelly Yancey - kbyanc@posi.net - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 23:18:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1143637B51E for ; Thu, 6 Jul 2000 23:18:18 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id XAA15769; Thu, 6 Jul 2000 23:18:06 -0700 Date: Thu, 6 Jul 2000 23:18:05 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Kelly Yancey Cc: "Kenneth D. Merry" , Zhihui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: Max DMA size 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 > Hmm. My knowledge may be a bit dated in this matter, but as I recall the > 8237 DMA controller standard on PCs only supports DMA requests up to 128k (and > then only on the upper 4 DMA channels). The low 4 DMA channels were > byte-granular and could only transfer 64k. Am I correct in assuming from this > discussion that the state of affairs is somewhat different nowadays? Uh, yeah. Standard PCI h/w usually has 32 bit dma engines, and a lot have 64 bit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 6 23:55:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gateway.posi.net (c1096725-a.smateo1.sfba.home.com [24.20.139.104]) by hub.freebsd.org (Postfix) with ESMTP id 7676937BD98 for ; Thu, 6 Jul 2000 23:55:41 -0700 (PDT) (envelope-from kbyanc@posi.net) Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.9.3/8.9.3) with ESMTP id XAA22041; Thu, 6 Jul 2000 23:56:43 -0700 (PDT) (envelope-from kbyanc@posi.net) Date: Thu, 6 Jul 2000 23:56:42 -0700 (PDT) From: Kelly Yancey To: Matthew Jacob Cc: "Kenneth D. Merry" , Zhihui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: Max DMA size 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 Thu, 6 Jul 2000, Matthew Jacob wrote: > Uh, yeah. Standard PCI h/w usually has 32 bit dma engines, and a lot have 64 > bit. > Neat, I'll have to go read my books on PCI now. :) Kelly -- Kelly Yancey - kbyanc@posi.net - Belmont, CA System Administrator, eGroups.com http://www.egroups.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 6:21:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uucp.nl.uu.net (uucp.nl.uu.net [193.79.237.146]) by hub.freebsd.org (Postfix) with ESMTP id 25F2237BD79 for ; Fri, 7 Jul 2000 06:21:42 -0700 (PDT) (envelope-from arjan@jak.nl) Received: from jaknl by athos.nl.uu.net with UUCP id ; Fri, 7 Jul 2000 15:21:26 +0200 Received: from jak.nl ([192.168.0.30]) by jak.nl (8.8.8/8.8.8) with ESMTP id PAA24333 for ; Fri, 7 Jul 2000 15:28:52 +0200 (CEST) (envelope-from arjan@jak.nl) Message-ID: <3965D8BA.BDC32313@jak.nl> Date: Fri, 07 Jul 2000 15:18:50 +0200 From: Arjan Knepper Organization: JAK++ Software Development B.V. X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers FreeBSD Subject: Re: stray interrupts in 4.0 Content-Type: multipart/mixed; boundary="------------467F465A0E6E57A4BB74031E" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------467F465A0E6E57A4BB74031E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I had the same problem with a Intel 810 MB. I haven's seen the messages since I upgraded the bios, disabled the lpt port in the bios and rebuilded a kernel with NO parallel driver. Warner Losh wrote: > > In message <200007061634.MAA16071@etinc.com> Dennis writes: > : great, so intel doesnt know how to make MBs with their own parts...so how > : can the message be turned off. Its using more resources printing the > : message thsn the "stray interrupts" themselves. > > I doubt that. Only about 5 of them are printed then we stop. At > least that's what I've seen when I have hardware that is like this. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message --------------467F465A0E6E57A4BB74031E Content-Type: text/x-vcard; charset=us-ascii; name="arjan.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Arjan Knepper Content-Disposition: attachment; filename="arjan.vcf" begin:vcard n:Knepper;Arjan tel;fax:+31-(0)10-243-7314 tel;work:+31-(0)10-243-7362 x-mozilla-html:FALSE url:http://www.jak.nl org:JAK++ Software Development B.V. adr:;;Stoveer 247;Rotterdam;;3032 GB;Netherlands version:2.1 email;internet:arjan@jak.nl x-mozilla-cpt:;-7904 fn:Arjan Knepper end:vcard --------------467F465A0E6E57A4BB74031E-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 7:47:50 2000 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 7313C37BBD9; Fri, 7 Jul 2000 07:47:39 -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.9.3/8.9.3) with SMTP id KAA66448; Fri, 7 Jul 2000 10:47:15 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 7 Jul 2000 10:47:15 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Nick Rogness Cc: Sean Lutner , Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging 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 Thu, 6 Jul 2000, Nick Rogness wrote: > On Thu, 6 Jul 2000, Sean Lutner wrote: > > > > > Bridges create a broadcast zone. broadcast packets will cross the bridge > > unobstructed. > > OK. So do bridged interfaces fall within the same collision > domain?... or are they just members of the same broadcast domain? FreeBSD bridging support places nodes in the same broadcast domain, but different collision domains. As such, you may see reordering of packets between segments, and packets may be lost transitting between segments. FreeBSD's bridging support is not 802.1d-compliant for a variety of reasons, and does not support spanning tree. That said, it is adequate for many uses, including our packet filtering support, which is very useful indeed :-). That said, we might do well to look at the OpenBSD bridging code and see if we can merge the behaviors -- they have some spiffy features (which I heard about at USENIX), including MAC-address based filtering, and some sort of VPN bridged technique (which sounds very useful). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 7:56:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 3F52737BDE5 for ; Fri, 7 Jul 2000 07:56:26 -0700 (PDT) (envelope-from frederik@freddym.org) Received: from server.wes.mee.com (p3E9C0303.dip.t-dialin.net [62.156.3.3]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id QAA04451 for ; Fri, 7 Jul 2000 16:56:19 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by server.wes.mee.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id QAA00356 for ; Fri, 7 Jul 2000 16:49:45 +0200 (CEST) Date: Fri, 7 Jul 2000 16:49:45 +0200 (CEST) From: Frederik Meerwaldt X-Sender: frederik@server.wes.mee.com To: freebsd-hackers@freebsd.org Subject: NATD-Bug??? 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 all, I've configured my Server as a router, so when I'm online, I automatically start natd, to let my other computers use my server as a gateway. But thw problem is, that NATD dies after about 10 Minutes. The process is still there, but I can't route anymore. After flushing all rules and starting Natd again, it works. I route ed0 <--> isp0. Is this a known problem? Any workarounds?? Thanks, Freddy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 10:46:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.mail.yahoo.com (smtp.mail.yahoo.com [128.11.68.32]) by hub.freebsd.org (Postfix) with SMTP id 95E7B37BFF9 for ; Fri, 7 Jul 2000 10:46:50 -0700 (PDT) (envelope-from lgrajales@yahoo.com) Received: from ol46-22.fibertel.com.ar (HELO cero) (24.232.22.46) by smtp.mail.yahoo.com with SMTP; 7 Jul 2000 17:08:16 -0000 X-Apparently-From: Message-ID: <009001bfe835$d42ea280$2e16e818@proxy.fibertel.com.ar> From: "lgrajales" To: Subject: Code Pal VMS Date: Fri, 7 Jul 2000 14:02:33 -0300 Organization: Boixos Nois MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What is a Code Pal for VMS? > thnxs. > __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 11:15:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from facmail.cc.gettysburg.edu (facmail.gettysburg.edu [138.234.4.150]) by hub.freebsd.org (Postfix) with ESMTP id 59DBF37C42E for ; Fri, 7 Jul 2000 11:15:11 -0700 (PDT) (envelope-from s467338@gettysburg.edu) Received: from jupiter2 (jupiter2.cc.gettysburg.edu [138.234.4.6]) by facmail.cc.gettysburg.edu (8.9.3/8.9.3) with SMTP id OAA23507; Fri, 7 Jul 2000 14:15:07 -0400 (EDT) Date: Fri, 7 Jul 2000 14:15:07 -0400 (EDT) From: Andrew Reiter X-Sender: s467338@jupiter2 To: lgrajales Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Code Pal VMS In-Reply-To: <009001bfe835$d42ea280$2e16e818@proxy.fibertel.com.ar> 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 believe we've all hit a real low aftrer this. On Fri, 7 Jul 2000, lgrajales wrote: |> |> What is a Code Pal for VMS? |> thnxs. |> | | | |__________________________________________________ |Do You Yahoo!? |Talk to your friends online with Yahoo! Messenger. |http://im.yahoo.com | | |To Unsubscribe: send mail to majordomo@FreeBSD.org |with "unsubscribe freebsd-hackers" in the body of the message | --------------------------------------------------------- Andrew Reiter Computer Security Engineer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 11:51:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id EB04237B773; Fri, 7 Jul 2000 11:51:29 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id UAA25120; Fri, 7 Jul 2000 20:51:23 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Date: Fri, 7 Jul 2000 20:51:22 +0200 (EET) From: Narvi To: Andrew Reiter Cc: lgrajales , freebsd-hackers@FreeBSD.ORG, freebsd-chat@FreeBSD.ORG Subject: Re: Code Pal VMS 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 No. A real low would be 'what does Visual C++ do or Where do I get cracks for Visual Basic'. And damn it, dare anybody not head over to -chat with this thread! On Fri, 7 Jul 2000, Andrew Reiter wrote: > > I believe we've all hit a real low aftrer this. > > On Fri, 7 Jul 2000, lgrajales wrote: > > |> > |> What is a Code Pal for VMS? > |> thnxs. > |> [snip - sigs] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 12:49: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id B7BF637C886; Fri, 7 Jul 2000 12:49:01 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id VAA25929; Fri, 7 Jul 2000 21:48:51 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Date: Fri, 7 Jul 2000 21:48:50 +0200 (EET) From: Narvi To: Nick Rogness Cc: Sean Lutner , Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging 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 Thu, 6 Jul 2000, Nick Rogness wrote: > On Thu, 6 Jul 2000, Sean Lutner wrote: > > > > > Bridges create a broadcast zone. broadcast packets will cross the bridge > > unobstructed. > > OK. So do bridged interfaces fall within the same collision > domain?... or are they just members of the same broadcast domain? > They can't be in the same collison domain - you'll realise it if you think about it for a second. > > Nick Rogness > - Speak softly and carry a Gigabit switch. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 12:58:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 8743837BE85 for ; Fri, 7 Jul 2000 12:58:46 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id PAA08667; Fri, 7 Jul 2000 15:58:16 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Fri, 7 Jul 2000 15:58:16 -0400 (EDT) From: Adam To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: stray interrupts in 4.0 In-Reply-To: <200007061634.MAA16071@etinc.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 Thu, 6 Jul 2000, Dennis wrote: >>> >> We're seeing lots of "stray" interrupts in 4.0 while running 3.4 on the >>> >> same hardware reports nothing. The interrupt its complaining about is >IRQ7 >>> >> even though parallel port is disabled and no other device. It happens on >>> >> more than 1 MB. >[snip] > >> >>Generally this message indicates that you have hardware in the system >>that is not signalling interrupts correctly. > >great, so intel doesnt know how to make MBs with their own parts...so how >can the message be turned off. Its using more resources printing the >message thsn the "stray interrupts" themselves. > >DB If you *have* an lpt controller and dont need the IRQ you could turn it on and enable the lpt driver in the kernel, that usually seems to take care of it on systems I had this message on. For this reason I usually leave lpt stuff enabled on systems even I'm unlikely to need the parallel port.. The other obvious alternative is to grep for it in the source and comment the printf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 13:31:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 3522137C558; Fri, 7 Jul 2000 13:29:28 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id OAA12959; Fri, 7 Jul 2000 14:29:00 -0600 (MDT) Date: Fri, 7 Jul 2000 14:28:59 -0600 (MDT) From: Nick Rogness To: Narvi Cc: Sean Lutner , Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging 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, 7 Jul 2000, Narvi wrote: > > On Thu, 6 Jul 2000, Sean Lutner wrote: > > > > > > > > Bridges create a broadcast zone. broadcast packets will cross the bridge > > > unobstructed. > > > > OK. So do bridged interfaces fall within the same collision > > domain?... or are they just members of the same broadcast domain? > > > > They can't be in the same collison domain - you'll realise it if you > think about it for a second. It is possible to span 2 collison domains across 1 VLAN...so yes they could be, if it were possible with FreeBSD (?IS it?) to put two ethernet cards in this setup: FreeBSD int1 int2 / \ / \ / \ switch1 switch2 If int1 and int2 were part of the same collision domain, then switch1 and switch2 would also be part of the same collosion domain and visa versa. This would be pretty cool to see happen, essentially making a VLAN switch (with Layer 3 capabilities). Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 14:16:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 983EE37C1D9; Fri, 7 Jul 2000 14:16:42 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id RAA95711; Fri, 7 Jul 2000 17:16:14 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200007072116.RAA95711@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Rogness Cc: Narvi , Sean Lutner , Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: bridging References: In-reply-to: Your message of "Fri, 07 Jul 2000 14:28:59 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Jul 2000 17:16:14 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG They can't be in the same collision domain -- the only way to do that is to have an Ethernet repeater which repeats bit by bit fron one segment to another, and propagating a collision on one segment as a jam on another. On a FreeBSD box, where you interfaces to ethernet segments are NIC cards, you can't get your hands on the ethernet frame until the NIC has received it completely. Thus, you don't have to opportunity to act as a repeater (not that you'd want to anyway) to have a single collision domain. louie > On Fri, 7 Jul 2000, Narvi wrote: > > > > On Thu, 6 Jul 2000, Sean Lutner wrote: > > > > > > > > > > > Bridges create a broadcast zone. broadcast packets will cross the bridge > > > > unobstructed. > > > > > > OK. So do bridged interfaces fall within the same collision > > > domain?... or are they just members of the same broadcast domain? > > > > > > > They can't be in the same collison domain - you'll realise it if you > > think about it for a second. > > It is possible to span 2 collison domains across 1 VLAN...so > yes they could be, if it were possible with FreeBSD (?IS it?) to > put two ethernet cards in this setup: > > FreeBSD > int1 int2 > / \ > / \ > / \ > switch1 switch2 > > If int1 and int2 were part of the same collision domain, then > switch1 and switch2 would also be part of the same collosion > domain and visa versa. This would be pretty cool to see happen, > essentially making a VLAN switch (with Layer 3 capabilities). > > > Nick Rogness > - Speak softly and carry a Gigabit switch. > > > > > > > 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 Jul 7 15: 6:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 0608737B6A7; Fri, 7 Jul 2000 15:06:39 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id QAA67245; Fri, 7 Jul 2000 16:06:23 -0600 (MDT) Date: Fri, 7 Jul 2000 16:06:23 -0600 (MDT) From: Nick Rogness To: "Louis A. Mamakos" Cc: Narvi , Sean Lutner , Nick Evans , "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: bridging In-Reply-To: <200007072116.RAA95711@whizzo.transsys.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, 7 Jul 2000, Louis A. Mamakos wrote: > They can't be in the same collision domain -- the only way to do that > is to have an Ethernet repeater which repeats bit by bit fron one > segment to another, and propagating a collision on one segment as a > jam on another. > > On a FreeBSD box, where you interfaces to ethernet segments are NIC > cards, you can't get your hands on the ethernet frame until the > NIC has received it completely. Thus, you don't have to opportunity > to act as a repeater (not that you'd want to anyway) to have a > single collision domain. You know, you are right...never thought it through completely before I sent my reply. Sorry everyone for the wasted bandwidth. Have 1 more question (has to do with this bridging deal): Anyone working on load-sharing/load-balancing or clustering network solution with FreeBSD? Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 15:28:15 2000 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 EE35837B59C for ; Fri, 7 Jul 2000 15:28:09 -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 e67MRtI55419; Fri, 7 Jul 2000 15:27:55 -0700 (PDT) Date: Fri, 7 Jul 2000 15:27:55 -0700 (PDT) From: Doug White To: Sergio Faustino Cc: hackers@FreeBSD.ORG Subject: Re: driver In-Reply-To: <001101bfe7d2$d51784e0$a863c7c8@Usuario> 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, 7 Jul 2000, Sergio Faustino wrote: > To make the QuickCam (grayscale) work with Windows NT machines you > must install an NT driver. I'd like to know as to get this driver. Ask in a NT forum, then. 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 Fri Jul 7 15:39:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163]) by hub.freebsd.org (Postfix) with ESMTP id 67C3E37B73D; Fri, 7 Jul 2000 15:39:24 -0700 (PDT) (envelope-from gcorcoran@lucent.com) Received: from ihemail2.firewall.lucent.com (localhost [127.0.0.1]) by ihemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id SAA23825; Fri, 7 Jul 2000 18:39:20 -0400 (EDT) Received: from mhmail.mh.lucent.com (h135-3-115-8.lucent.com [135.3.115.8]) by ihemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id SAA23821; Fri, 7 Jul 2000 18:39:20 -0400 (EDT) Received: from lucent.com by mhmail.mh.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id SAA09768; Fri, 7 Jul 2000 18:39:13 -0400 (EDT) Message-ID: <39665C10.9C316392@lucent.com> Date: Fri, 07 Jul 2000 18:39:12 -0400 From: "Gary T. Corcoran" Organization: Lucent Microelectronics - Client Access Broadband Systems X-Mailer: Mozilla 4.73 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: FreeBSD Hackers Subject: Module parameters? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike, A couple of months ago we spoke about my needing the ability to set module parameters during a kldload, and you indicated that you would be working on them for FreeBSD 4.1. I've since progressed my DSL driver to the point where it works in all the modes I need (same as the Linux driver), but I have to recompile my driver to change any options. Therefore, I haven't done any further work on it, and I have been unable to make it available to anyone else for beta testing (since everyone needs to change options for their particular installation)... I was wondering if you (or anyone on this list) has had time to add module parameters to kldload? (and before anyone suggests it, sorry, but I am barely able to squeeze out enough time to even work on this unofficial driver, I can't work on kldload) Thanks, Gary -- ========================================================= Gary Corcoran - Distinguished Member of Technical Staff Lucent Microelectronics - Client Access Broadband Systems Communications Protocol & Driver Development Group "We make the drivers that make communications work" Email: gcorcoran@lucent.com ========================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 16: 0:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 4EDC637B6B7 for ; Fri, 7 Jul 2000 16:00:12 -0700 (PDT) (envelope-from boshea@ricochet.net) Received: from beastie.localdomain ([24.19.158.41]) by mail.rdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000707230007.SGTV13081.mail.rdc1.sfba.home.com@beastie.localdomain>; Fri, 7 Jul 2000 16:00:07 -0700 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id QAA58213; Fri, 7 Jul 2000 16:11:09 -0700 (PDT) (envelope-from brian) Date: Fri, 7 Jul 2000 16:11:09 -0700 From: "Brian O'Shea" To: Narvi Cc: Andrew Reiter , lgrajales , freebsd-hackers@FreeBSD.ORG Subject: Re: Code Pal VMS Message-ID: <20000707161109.L15683@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: Narvi , Andrew Reiter , lgrajales , freebsd-hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Narvi on Fri, Jul 07, 2000 at 08:51:22PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wait a minute guys, this might be a valid (although not very clearly stated) FreeBSD question. After a little digging around, it looks like PALcode is firmware on the DEC Alpha (for which there are versions of VMS, as well as FreeBSD). To the original poster: search for information about the FreeBSD port to the Alpha architecture at . Failing that, post your question to the freebsd-alpha mailing list with a few more details about the context of your question. Good luck, -brian On Fri, Jul 07, 2000 at 08:51:22PM +0200, Narvi wrote: > > No. A real low would be 'what does Visual C++ do or Where do I get cracks > for Visual Basic'. > > And damn it, dare anybody not head over to -chat with this thread! > > On Fri, 7 Jul 2000, Andrew Reiter wrote: > > > > > I believe we've all hit a real low aftrer this. > > > > On Fri, 7 Jul 2000, lgrajales wrote: > > > > |> > > |> What is a Code Pal for VMS? > > |> thnxs. > > |> > > [snip - sigs] > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 17:22:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 24C1737B5AB for ; Fri, 7 Jul 2000 17:22:23 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com ([208.187.122.225]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id SAA16810; Fri, 7 Jul 2000 18:22:16 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <396674B9.CE7F1F97@softweyr.com> Date: Fri, 07 Jul 2000 18:24:25 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Commissionnaires Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: Learning References: <6BDA45469076D1118F7300805F57DDD152F889@emssk1.weyer.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Commissionnaires wrote: > > I am interested in learning about the freebsd operating system, I dont have > very much exerience yet but I am motivated to learn. I have poked around > other OS but have found them unappealing to my interest, I like the concept > of free source systems like linux and have played with SUSE a little but > found the limited availability of learning materials in english a > hinderance. I have downloaded and printed the manual as of page 34 where I > came upon your invitation I decided to reach out and touch someone. I woud > like some quick advice as to what version I should install via ftp to begin > my learning, and what would be the best path to follow. I am particularily > interested in learning to program in an acceptable language and want to > concentrate on network protocols and reliable secure communications, as well > as network security and firewalls. > > Thank you for any advice that you can offer. My best advice for a complete novice would be to buy the book "The Complete FreeBSD", by Greg Lehey, install the version of FreeBSD on the CD-ROM found inside the book, and use the book as a guide to configuring FreeBSD for whatever you need. Once you've gotten that far, then come back and ask questions in the freebsd-hackers mailing list, you'll be ready for us by then. In the meantime, direct questions about how to configure various parts of FreeBSD to the freebsd-questions mailing list, you're much more likely to find willing helpful people there. It's our "support line." Best of luck, and let us know how you do. Better yet, once you've got FreeBSD running to your satisfaction, write an article about it for a magazine, a web site, or your local newspaper and tell us about it. ;^) -- "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 Fri Jul 7 18: 4:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 7EC5937B880 for ; Fri, 7 Jul 2000 18:04:11 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-135-41.nnj.dialup.bellatlantic.net [151.198.135.41]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id VAA29352; Fri, 7 Jul 2000 21:03:54 -0400 (EDT) Message-ID: <39667E45.D8BD4232@bellatlantic.net> Date: Fri, 07 Jul 2000 21:05:09 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Wes Peters Cc: Commissionnaires , "'freebsd-hackers@freebsd.org'" Subject: Re: Learning References: <6BDA45469076D1118F7300805F57DDD152F889@emssk1.weyer.com> <396674B9.CE7F1F97@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > > Commissionnaires wrote: > > > > I am interested in learning about the freebsd operating system, I dont have > My best advice for a complete novice would be to buy the book "The Complete > FreeBSD", by Greg Lehey, install the version of FreeBSD on the CD-ROM found By the way, the new edition of the classic Unix system administration book by Evi Nemeth et. al. includes FreeBSD among the considered systems (others are Solaris, HP-UX and Linux). Judging from previous editions that's a quite good and comprehensive book. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 7 19:29:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 5B1A137B5EC for ; Fri, 7 Jul 2000 19:29:54 -0700 (PDT) (envelope-from steve@virtual-voodoo.com) Received: (from root@localhost) by virtual-voodoo.com (8.11.0.Beta3/8.11.0.Beta3) id e682Trd77135 for freebsd-hackers@freebsd.org; Fri, 7 Jul 2000 21:29:53 -0500 (EST) Date: Fri, 7 Jul 2000 21:29:53 -0500 (EST) From: Steve Ames Message-Id: <200007080229.e682Trd77135@virtual-voodoo.com> To: freebsd-hackers@freebsd.org Subject: OpenSSH 2.X problem with escape chars? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey... just noticed something odd. I just upgrading one of my FBSD boxes to the latest -STABLE and modified /etc/ssh/sshd_config to use version 2 then 1 (Protocol 2,1). After doing this when I connect to that server the escape sequences (~^Z and friends (as per 'man 1 ssh')) no longer work. If I connect version 1 they do. If I connect version 2 they don't. Any thoughts? The client I'm connecting from is a 5.0-CURRENT (7/6/00) system. -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 8 0:34:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from inconnu.isu.edu (inconnu.isu.edu [134.50.8.55]) by hub.freebsd.org (Postfix) with ESMTP id F32C937B5B8; Sat, 8 Jul 2000 00:34:30 -0700 (PDT) (envelope-from galt@inconnu.isu.edu) Received: from localhost (galt@localhost) by inconnu.isu.edu (8.9.3/8.9.3) with ESMTP id BAA15589; Sat, 8 Jul 2000 01:34:22 -0600 Date: Sat, 8 Jul 2000 01:34:22 -0600 (MDT) From: John Galt To: Narvi Cc: Andrew Reiter , lgrajales , freebsd-hackers@FreeBSD.ORG, freebsd-chat@FreeBSD.ORG Subject: Re: Code Pal VMS 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 A friend of mine's making a VB interpreter for TCL/TK... On Fri, 7 Jul 2000, Narvi wrote: > > No. A real low would be 'what does Visual C++ do or Where do I get cracks > for Visual Basic'. > > And damn it, dare anybody not head over to -chat with this thread! > > On Fri, 7 Jul 2000, Andrew Reiter wrote: > > > > > I believe we've all hit a real low aftrer this. > > > > On Fri, 7 Jul 2000, lgrajales wrote: > > > > |> > > |> What is a Code Pal for VMS? > > |> thnxs. > > |> > > [snip - sigs] > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-chat" in the body of the message > -- Who is John Galt? Failure is not an option. It comes bundled with your Microsoft product. -- Ferenc Mantfeld To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 8 0:39:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns3.khmere.com (d83b56af.dsl.flashcom.net [216.59.86.175]) by hub.freebsd.org (Postfix) with ESMTP id 2293237B66D; Sat, 8 Jul 2000 00:39:06 -0700 (PDT) (envelope-from nathan@khmere.com) Received: from khmere.com (ns2.khmere.com [216.59.86.176]) by ns3.khmere.com (8.9.3/8.8.7) with ESMTP id AAA05751; Sat, 8 Jul 2000 00:42:21 -0700 (PDT) Message-ID: <39673C7E.ED9D9D21@khmere.com> Date: Sat, 08 Jul 2000 07:36:46 -0700 From: nathan@khmere.com X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.15 i586) X-Accept-Language: en MIME-Version: 1.0 To: "hackers@FreeBSD.ORG" , "freebsd-net@FreeBSD.ORG" Subject: loader help !! (bug ??) 4.0-STABLE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for the re-post but not reponse !! I have FreeBSD 4.0-STABLE on i386, was -RELEASE ) What I am trying to do is nfs root boot from the loader (?) I do: ok> unload kernel ok> load diskless_kernel ok> set kernel=diskless_kernel ok> boot -r -h Now what I understand is the -r flag will tell the kernel to overide the rootdev and use the "staticly linked device" from when you made the kernel (this would be the BOOTP_NFSROOT option ?) Now my kernel (the diskless_kernel ) is a diskless kernel ( with BOOTP, NFS_ROOT .... etc.. ) compiled in. But when I boot like this is just tries to mount /dev/ad0s1a ... (normal device ) even though it gets the proper reply from the bootp server that its rootfs= it even prints : rootfs is Mounting root from ufs:/dev/ad0s1a but still mounts the ufs ! How do if force it to boot root fs on nfs ? I have tried to do a boot -a then when I prompts me for root fs I enter the proper nfs mount and for RELEASE it would boot diskless but for STABLE is fails !! I have tried to : ok> set rootdev=nfs: ok> boot -h ok> can't determine root device I have also passed it various kernel flags and env options... (mybe wrong ones ... ? ) how do I have the kernel to load the rootfs = nfs root instead of use the currdev ? What does etherboot do when it loads the kernel ? does it pass it special parameters ?? If you are wondering why I just don't boot from etherboot ....etc...(I do ) but... I want to be able to boot my remote systems without a floppie and chose how to boot from loader (via serail console ...I don't have serial access for the bios but I can get serial console with FreeBSD !! ). Either default (use local drive) or load the diskless kernel , then boot diskless. This way I almost the same options ..... and maybe automate it... Any help would be great !! thank you kindly.... nathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 8 8: 0:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vuurwerk.nl (envy.vuurwerk.nl [194.178.232.112]) by hub.freebsd.org (Postfix) with SMTP id 56F1337B60B for ; Sat, 8 Jul 2000 08:00:47 -0700 (PDT) (envelope-from petervd@vuurwerk.nl) Received: (qmail 57357 invoked from network); 8 Jul 2000 15:00:42 -0000 Received: from kesteren.vuurwerk.nl (HELO vuurwerk.nl) (194.178.232.59) by envy.vuurwerk.nl with SMTP; 8 Jul 2000 15:00:42 -0000 Received: (qmail 16299 invoked by uid 11109); 8 Jul 2000 15:00:42 -0000 Mail-Followup-To: freebsd-hackers@FreeBSD.ORG Date: Sat, 8 Jul 2000 17:00:42 +0200 From: Peter van Dijk To: freebsd-hackers@FreeBSD.ORG Subject: Re: Code Pal VMS Message-ID: <20000708170042.E16030@vuurwerk.nl> References: <20000707161109.L15683@beastie.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000707161109.L15683@beastie.localdomain>; from boshea@ricochet.net on Fri, Jul 07, 2000 at 04:11:09PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 07, 2000 at 04:11:09PM -0700, Brian O'Shea wrote: > Wait a minute guys, this might be a valid (although not very > clearly stated) FreeBSD question. After a little digging around, > it looks like PALcode is firmware on the DEC Alpha (for which > there are versions of VMS, as well as FreeBSD). To be exact, there are globally two versions of Alpha firmware - ARC and SRM. One is for booting NT (the Linux loader MILO works with it too, and those are the only two IIRC), the other is for booting VMS and OSF/1 (Digital Unix). You need the second one (which is SRM if I recall correctly, I keep mixing them up) for FreeBSD/OpenBSD and friends too. So, his question is quite valid - he needs the VMS firmware to run FreeBSD on his alpha. Greetz, Peter. -- petervd@vuurwerk.nl - Peter van Dijk [student:developer:ircoper] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 8 8:34:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 92ED537B5DE for ; Sat, 8 Jul 2000 08:34:19 -0700 (PDT) (envelope-from frederik@freddym.org) Received: from server.wes.mee.com (pC19EB39D.dip.t-dialin.net [193.158.179.157]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id RAA24654; Sat, 8 Jul 2000 17:34:18 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by server.wes.mee.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id RAA01732; Sat, 8 Jul 2000 17:04:44 +0200 (CEST) Date: Sat, 8 Jul 2000 17:04:44 +0200 (CEST) From: Frederik Meerwaldt X-Sender: frederik@server.wes.mee.com To: Peter van Dijk Cc: freebsd-hackers@freebsd.org Subject: Re: Code Pal VMS In-Reply-To: <20000708170042.E16030@vuurwerk.nl> 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! > So, his question is quite valid - he needs the VMS firmware to run FreeBSD > on his alpha. And JFI it is downloadable under www.compaq.com/support even for old Alphas AXP150 and so on. Bye, Freddy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 8 9:38:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vuurwerk.nl (envy.vuurwerk.nl [194.178.232.112]) by hub.freebsd.org (Postfix) with SMTP id D902E37BFA2 for ; Sat, 8 Jul 2000 09:38:40 -0700 (PDT) (envelope-from petervd@vuurwerk.nl) Received: (qmail 57828 invoked from network); 8 Jul 2000 16:38:36 -0000 Received: from kesteren.vuurwerk.nl (HELO vuurwerk.nl) (194.178.232.59) by envy.vuurwerk.nl with SMTP; 8 Jul 2000 16:38:36 -0000 Received: (qmail 16409 invoked by uid 11109); 8 Jul 2000 16:38:36 -0000 Mail-Followup-To: freebsd-hackers@FreeBSD.ORG Date: Sat, 8 Jul 2000 18:38:36 +0200 From: Peter van Dijk To: freebsd-hackers@FreeBSD.ORG Subject: Re: Code Pal VMS Message-ID: <20000708183836.I16030@vuurwerk.nl> References: <20000708170042.E16030@vuurwerk.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from frederik@freddym.org on Sat, Jul 08, 2000 at 05:04:44PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 08, 2000 at 05:04:44PM +0200, Frederik Meerwaldt wrote: > Hi! > > > So, his question is quite valid - he needs the VMS firmware to run FreeBSD > > on his alpha. > > And JFI it is downloadable under www.compaq.com/support > even for old Alphas AXP150 and so on. ftp.digital.com has *all* the old stuff, including OEM Design Guides for the AXPpci33 boards (a link to which I recently submitted for the FreeBSD Alpha HARDWARE.TXT). Greetz, Peter. -- petervd@vuurwerk.nl - Peter van Dijk [student:developer:ircoper] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 8 10: 1: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id 2AB9B37B5B7 for ; Sat, 8 Jul 2000 10:01:02 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000708170202.KCRV8575.relay01@chello.nl>; Sat, 8 Jul 2000 19:02:02 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id TAA02084; Sat, 8 Jul 2000 19:00:56 +0200 (CEST) (envelope-from wkb) Date: Sat, 8 Jul 2000 19:00:56 +0200 From: Wilko Bulte To: Peter van Dijk Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Code Pal VMS Message-ID: <20000708190056.B1989@freebie.wbnet> Reply-To: wilko@FreeBSD.ORG References: <20000708170042.E16030@vuurwerk.nl> <20000708183836.I16030@vuurwerk.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000708183836.I16030@vuurwerk.nl>; from petervd@vuurwerk.nl on Sat, Jul 08, 2000 at 06:38:36PM +0200 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 08, 2000 at 06:38:36PM +0200, Peter van Dijk wrote: > On Sat, Jul 08, 2000 at 05:04:44PM +0200, Frederik Meerwaldt wrote: > > Hi! > > > > > So, his question is quite valid - he needs the VMS firmware to run FreeBSD > > > on his alpha. > > > > And JFI it is downloadable under www.compaq.com/support > > even for old Alphas AXP150 and so on. > > ftp.digital.com has *all* the old stuff, including OEM Design Guides for > the AXPpci33 boards (a link to which I recently submitted for the FreeBSD > Alpha HARDWARE.TXT). A link which is even *in* HARDWARE.TXT now ;-) Another good source of Alpha related docs is www.NetBSD.org -- Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try" wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 8 11: 6:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id D36AA37B5B7 for ; Sat, 8 Jul 2000 11:06:31 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000708180735.KMIY8575.relay01@chello.nl> for ; Sat, 8 Jul 2000 20:07:35 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id UAA02586 for FreeBSD-hackers@freebsd.org; Sat, 8 Jul 2000 20:06:29 +0200 (CEST) (envelope-from wkb) Date: Sat, 8 Jul 2000 20:06:29 +0200 From: Wilko Bulte To: FreeBSD hackers list Subject: why the RockRidge message? Message-ID: <20000708200629.A2570@freebie.wbnet> Reply-To: wilko@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I really don't understand why the cd9660 filesystem needs to whine about the RockRidge extensions everytime one mounts a RR cdrom. The code in question is: if (high_sierra) { /* this effectively ignores all the mount flags */ log(LOG_INFO, "cd9660: High Sierra Format\n"); isomp->iso_ftype = ISO_FTYPE_HIGH_SIERRA; } else Comments? -- Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try" wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 8 11:26: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [209.145.74.241]) by hub.freebsd.org (Postfix) with ESMTP id 1BECB37B9E1 for ; Sat, 8 Jul 2000 11:25:56 -0700 (PDT) (envelope-from adrian@ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.9.3/8.8.8) with ESMTP id OAA29787; Sat, 8 Jul 2000 14:24:25 -0400 (EDT) (envelope-from adrian@ubergeeks.com) Date: Sat, 8 Jul 2000 14:24:25 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Steve Ames Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: OpenSSH 2.X problem with escape chars? In-Reply-To: <200007080229.e682Trd77135@virtual-voodoo.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, 7 Jul 2000, Steve Ames wrote: > > Hey... just noticed something odd. I just upgrading one of my FBSD boxes > to the latest -STABLE and modified /etc/ssh/sshd_config to use version > 2 then 1 (Protocol 2,1). After doing this when I connect to that server > the escape sequences (~^Z and friends (as per 'man 1 ssh')) no longer > work. If I connect version 1 they do. If I connect version 2 they don't. > > Any thoughts? The client I'm connecting from is a 5.0-CURRENT (7/6/00) > system. > > -Steve The same problem exists under 4-STABLE from 07/04/00. I haven't had timt to dig into it for real, but running ssh with -v, seemed to make me believe that the client end was pasing along the ~ to the remote end. IIRC, the ~ should be dealt with on the client end. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 8 13:11:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from racine.cybercable.fr (racine.cybercable.fr [212.198.0.201]) by hub.freebsd.org (Postfix) with SMTP id BDAE337B569 for ; Sat, 8 Jul 2000 13:11:10 -0700 (PDT) (envelope-from mhenrion@cybercable.fr) Received: (qmail 7528603 invoked from network); 8 Jul 2000 20:11:04 -0000 Received: from r121m199.cybercable.tm.fr (HELO cybercable.fr) ([195.132.121.199]) (envelope-sender ) by racine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 8 Jul 2000 20:11:04 -0000 Message-ID: <39678B9C.C9166C11@cybercable.fr> Date: Sat, 08 Jul 2000 22:14:20 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: ldconfig behaviour when no parameters are given Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everybody, When ldconfig is invoked without any parameters, the shared library cache is reseted to the contents of /usr/lib only. I think such a behaviour isn't very useful, especially when one knows that a lot of people come to FreeBSD after having used Linux. The first time they get an error message like "foo.so not found", they, nearly automatically, run ldconfig and so screw up their shared library cache. Is there a special reason why ldconfig behaves this way ? And is there any application that rely on that behaviour ? This would at least estonish me. That's why, i wanted to suggest that ldconfig prints a usage screen when invoked without parameters, or else that it performs a default and safe action, like a refresh (ldconfig -R). If it happens that what I say make sense, and that the two requirements above are met (see the two questions), i'll be happy to submit a patch. Waiting for your comments, - Maxiime Henrion To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 8 13:47:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id F194537BB1D; Sat, 8 Jul 2000 13:47:56 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA51439; Sat, 8 Jul 2000 13:47:56 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 8 Jul 2000 13:47:56 -0700 (PDT) From: Kris Kennaway To: Adrian Filipi-Martin Cc: Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: OpenSSH 2.X problem with escape chars? 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 Sat, 8 Jul 2000, Adrian Filipi-Martin wrote: > The same problem exists under 4-STABLE from 07/04/00. I haven't > had timt to dig into it for real, but running ssh with -v, seemed to make > me believe that the client end was pasing along the ~ to the remote end. > IIRC, the ~ should be dealt with on the client end. You should report this to the OpenSSH guys: see www.openssh.com for list of mailing lists. It doesn't sound like a bug we've introduced in our version, and if it's a generic OpenSSH bug then it should be fixed at the source. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 8 17:26:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 1FD6E37B50C; Sat, 8 Jul 2000 17:26:19 -0700 (PDT) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.11.0.Beta3/8.11.0.Beta3) id e690QIQ90971; Sat, 8 Jul 2000 19:26:18 -0500 (EST) Date: Sat, 8 Jul 2000 19:26:17 -0500 From: Steve Ames To: Kris Kennaway Cc: Adrian Filipi-Martin , freebsd-hackers@FreeBSD.org Subject: Re: OpenSSH 2.X problem with escape chars? Message-ID: <20000708192617.A84753@virtual-voodoo.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from kris@FreeBSD.org on Sat, Jul 08, 2000 at 01:47:56PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just forwarded my original message to 'openssh@openssh.com'. -Steve On Sat, Jul 08, 2000 at 01:47:56PM -0700, Kris Kennaway wrote: > On Sat, 8 Jul 2000, Adrian Filipi-Martin wrote: > > > The same problem exists under 4-STABLE from 07/04/00. I haven't > > had timt to dig into it for real, but running ssh with -v, seemed to make > > me believe that the client end was pasing along the ~ to the remote end. > > IIRC, the ~ should be dealt with on the client end. > > You should report this to the OpenSSH guys: see www.openssh.com for list > of mailing lists. It doesn't sound like a bug we've introduced in our > version, and if it's a generic OpenSSH bug then it should be fixed at the > source. > > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 8 21:10:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id 6871837BFF8 for ; Sat, 8 Jul 2000 21:10:47 -0700 (PDT) (envelope-from jim@reptiles.org) Received: from localhost (798 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Sun, 9 Jul 2000 00:10:45 -0400 (EDT) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Sun, 9 Jul 2000 00:10:45 -0400 From: Jim Mercer To: hackers@freebsd.org Subject: cvs-crypto missing from 4.0-stable via cvsup? Message-ID: <20000709001045.A9391@reptiles.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 maybe i just noticed, or maybe something happened recently, but when i cvsup now, i get a message saying cvs-cryto is non-existent. has it been integrated into the standard tree? -- [ Jim Mercer jim@reptiles.org +1 416 410-5633 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 8 21:24:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vicosa.dpi.ufv.br (vicosa.dpi.ufv.br [200.17.74.1]) by hub.freebsd.org (Postfix) with ESMTP id B78F637BFD8 for ; Sat, 8 Jul 2000 21:24:20 -0700 (PDT) (envelope-from kernel@tdnet.com.br) Received: from tdnet.com.br (port59.tdnet.com.br [200.236.148.159]) by vicosa.dpi.ufv.br (AIX4.2/UCB 8.7/8.7) with ESMTP id BAA20578; Sun, 9 Jul 2000 01:22:02 -0200 (GRNLNDDT) Message-ID: <3967D3A3.5B77647C@tdnet.com.br> Date: Sun, 09 Jul 2000 01:21:39 +0000 From: Gustavo Vieira Goncalves Coelho Rios X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jim Mercer Cc: hackers@freebsd.org Subject: Re: cvs-crypto missing from 4.0-stable via cvsup? References: <20000709001045.A9391@reptiles.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Mercer wrote: > > maybe i just noticed, or maybe something happened recently, but when i cvsup > now, i get a message saying cvs-cryto is non-existent. > > has it been integrated into the standard tree? > > -- > [ Jim Mercer jim@reptiles.org +1 416 410-5633 ] > [ Reptilian Research -- Longer Life through Colder Blood ] > [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Yes! cvs-crypto were removed! Now just fetch src-all! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message