From owner-freebsd-hackers Sun Nov 28 1:20:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 8B7D5155DA; Sun, 28 Nov 1999 01:20:13 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7DDB41CD733; Sun, 28 Nov 1999 01:20:13 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 28 Nov 1999 01:20:13 -0800 (PST) From: Kris Kennaway To: "Brian J. McGovern" Cc: hackers@freebsd.org Subject: Re: Test code... In-Reply-To: <199911280159.UAA07223@spoon.beta.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 27 Nov 1999, Brian J. McGovern wrote: > Anyone have any suggestions (or feel like writing) code to exercise the > following subsystems? > > - Virtual Memory > > - The threads library > > - mmap() and friends > > We want to try to bang on them a little more for 3.4 than we have in the past. Search the PR database and the mailing list archives for regression tests (things which at one time used to break things, but which are claimed to have been fixed). There are quite a few of these, although some bugs have only been fixed in -current because of the intrusive nature of the required changes. Kris ---- Just remember, as you celebrate Thanksgiving with your family feasts of turkey, cranberries, stuffing, gravy, mashed potatoes, squash, corn, cornbread, apples, pickles, dumplings, fish, orangutans, fruitbats, breakfast cereals, and so forth, to keep in mind the true reason for the season: The birth of Santa. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 28 12: 8:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eth0-gw.poli.hu (eth0-gw.poli.hu [195.199.8.27]) by hub.freebsd.org (Postfix) with ESMTP id 7B78014C88 for ; Sun, 28 Nov 1999 12:08:27 -0800 (PST) (envelope-from mauzi@faber.poli.hu) Received: from faber.poli.hu ([195.199.8.29]) by eth0-gw.poli.hu with esmtp (Exim 3.03 #1 (Debian)) id 11sAcX-0003fU-00 for ; Sun, 28 Nov 1999 21:08:29 +0100 Received: from mauzi (helo=localhost) by faber.poli.hu with local-esmtp (Exim 3.03 #1 (Debian)) id 11sAcO-0001Xj-00 for ; Sun, 28 Nov 1999 21:08:20 +0100 Date: Sun, 28 Nov 1999 21:08:20 +0100 (CET) From: Egervary Gergely To: freebsd-hackers@freebsd.org Subject: cdrom speed adjustment ioctl 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 hello, I've just hacked a new ioctl into the ATAPI cdrom driver, which lets the user to specify (pronounce: ``slow down'' :) the speed of todays' extremely high speed drives. It's a documented ATAPI feature, and is very easy to implement, and I've found it very useful :) first, you need to add the ioctl into sys/cdio.h: struct ioc_spdsel { int rate; } #define CDIOCSPDSEL _IOW('c',32,struct ioc_spdsel) second, need to add this into i386/isa/atapi.h #define ATAPI_SPEED_SELECT 0xbb and finally need to add this case into the function ``acdioctl'' in i386/isa/atapi-cd.c case CDIOCSPDSEL: { struct ioc_spdsel *arg = (struct ioc_spdsel *)addr; return acd_request_wait(cdp, ATAPI_SPEED_SELECT, 0, arg->rate>>8 & 0xff, arg->rate & 0xff, 0, 0, 0, 0, 0, 0, 0, 0); } of course unified diff's are available. i'm not an experienced kernel hacker, please feel free to correct me and drop me a mail about this thingy... thanks in advance -- mauzi Gergely EGERVARY mauzi@lkg.rulez.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 28 13:59:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from styx.astrom.net (astrom.net [193.15.98.30]) by hub.freebsd.org (Postfix) with ESMTP id 6497A14BEE for ; Sun, 28 Nov 1999 13:59:34 -0800 (PST) (envelope-from patrik@astrom.net) Received: from localhost (astrom@localhost) by styx.astrom.net (8.9.3/8.9.3) with ESMTP id WAA56387 for ; Sun, 28 Nov 1999 22:59:30 +0100 (CET) Date: Sun, 28 Nov 1999 22:59:29 +0100 (CET) From: patrik@astrom.net X-Sender: astrom@styx.astrom.net To: freebsd-hackers@freebsd.org Subject: Error compiling.. 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 everyone... First of all I would like to state that IM not a programmer. Im trying to compile a program and IM getting a errormessage, I have included the error message bellow. viking# cc emsg1.c emsg1.c: In function `main': emsg1.c:197: warning: passing arg 2 of `connect' from incompatible pointer type /var/tmp/ccRu22801.o: In function `main': /var/tmp/ccRu22801.o(.text+0x5bb): undefined reference to `cuserid' viking# The software IM trying to compile is a network monitoring tool named "EMU", I've found it at "http://www.jarrix.com.au". At line 197 it looks like this... if( connect(s, &sin, sizeof(sin)) < 0) { close(s); sleep(rand[count]); count++; } else { send(s, msg, strlen(msg), 0); if(q_option) { fp = fdopen(s, "r"); while ((c = fgetc(fp)) != EOF) { putchar(c); } close(s); exit(0); } close(s); exit(0); } And where it complains about the "cuserid" bit it looks like this... /* get my user name */ if (u_flag == 0) { cuserid(myuser); } As stated above IM not a programmer and I would be most grateful for any hints or suggestions. Im attaching the emsg1.c file to if someone should get intressted. Regards Patrik Astrom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 28 14: 2: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from styx.astrom.net (astrom.net [193.15.98.30]) by hub.freebsd.org (Postfix) with ESMTP id AA236153B3 for ; Sun, 28 Nov 1999 14:01:56 -0800 (PST) (envelope-from patrik@astrom.net) Received: from localhost (astrom@localhost) by styx.astrom.net (8.9.3/8.9.3) with ESMTP id XAA56409 for ; Sun, 28 Nov 1999 23:01:57 +0100 (CET) Date: Sun, 28 Nov 1999 23:01:56 +0100 (CET) From: patrik@astrom.net X-Sender: astrom@styx.astrom.net To: freebsd-hackers@freebsd.org Subject: Error compiling.. (Again, forgot the attachment) Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1007746717-943826516=:56372" 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-1007746717-943826516=:56372 Content-Type: TEXT/PLAIN; charset=US-ASCII Sorry for the double posting... Regards Patrik Astrom ---------- Forwarded message ---------- Date: Sun, 28 Nov 1999 22:59:29 +0100 (CET) From: patrik@astrom.net To: freebsd-hackers@freebsd.org Subject: Error compiling.. Hi everyone... First of all I would like to state that IM not a programmer. Im trying to compile a program and IM getting a errormessage, I have included the error message bellow. viking# cc emsg1.c emsg1.c: In function `main': emsg1.c:197: warning: passing arg 2 of `connect' from incompatible pointer type /var/tmp/ccRu22801.o: In function `main': /var/tmp/ccRu22801.o(.text+0x5bb): undefined reference to `cuserid' viking# The software IM trying to compile is a network monitoring tool named "EMU", I've found it at "http://www.jarrix.com.au". At line 197 it looks like this... if( connect(s, &sin, sizeof(sin)) < 0) { close(s); sleep(rand[count]); count++; } else { send(s, msg, strlen(msg), 0); if(q_option) { fp = fdopen(s, "r"); while ((c = fgetc(fp)) != EOF) { putchar(c); } close(s); exit(0); } close(s); exit(0); } And where it complains about the "cuserid" bit it looks like this... /* get my user name */ if (u_flag == 0) { cuserid(myuser); } As stated above IM not a programmer and I would be most grateful for any hints or suggestions. Im attaching the emsg1.c file to if someone should get intressted. Regards Patrik Astrom --0-1007746717-943826516=:56372 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="emsg1.c" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="emsg1.c" LyogZW1zZy5jIC0gc2VuZCBsb2cgbWVzc2FnZXMgdG8gdGhlIEVNVSBldmVu dCBtYW5hZ2VyDQogICBWRVJTSU9OIDEuMQ0KIyAgQ29weXJpZ2h0IDE5OTkN CiMgIGJ5IEphcnJpeCBTeXN0ZW1zIFB0eSBMdGQuICBBbGwgcmlnaHRzIHJl c2VydmVkLiAgU29tZSBpbmRpdmlkdWFsDQojICBmaWxlcyBpbiB0aGlzIGRp c3RyaWJ1dGlvbiBtYXkgYmUgY292ZXJlZA0KIyAgYnkgb3RoZXIgY29weXJp Z2h0cywgYXMgbm90ZWQgaW4gdGhlaXIgZW1iZWRkZWQgY29tbWVudHMuDQoj DQojICBSZWRpc3RyaWJ1dGlvbiBhbmQgdXNlIGluIHNvdXJjZSBhbmQgYmlu YXJ5IGZvcm1zIGFyZSBwZXJtaXR0ZWQNCiMgIHByb3ZpZGVkIHRoYXQgdGhp cyBlbnRpcmUgY29weXJpZ2h0IG5vdGljZSBpcyBkdXBsaWNhdGVkIGluIGFs bCBzdWNoDQojICBjb3BpZXMsIGFuZCB0aGF0IGFueSBkb2N1bWVudGF0aW9u LCBhbm5vdW5jZW1lbnRzLCBhbmQgb3RoZXINCiMgIG1hdGVyaWFscyByZWxh dGVkIHRvIHN1Y2ggZGlzdHJpYnV0aW9uIGFuZCB1c2UgYWNrbm93bGVkZ2Ug dGhhdCB0aGUNCiMgIHNvZnR3YXJlIHdhcyBkZXZlbG9wZWQgYXQgSmFycml4 IFN5c3RlbXMgUHR5IEx0ZCBieSBKYXJyYSBhbmQgQW5uYQ0KIyAgVm9sZXlu aWsuDQojDQojICBObyBjaGFyZ2UsIG90aGVyIHRoYW4gYW4gImF0LWNvc3Qi IGRpc3RyaWJ1dGlvbiBmZWUsIG1heSBiZSBjaGFyZ2VkDQojICBmb3IgY29w aWVzLCBkZXJpdmF0aW9ucywgb3IgZGlzdHJpYnV0aW9ucyBvZiB0aGlzIG1h dGVyaWFsIHdpdGhvdXQNCiMgIHRoZSBleHByZXNzIHdyaXR0ZW4gY29uc2Vu dCBvZiB0aGUgY29weXJpZ2h0IGhvbGRlci4NCiMNCiMgIFRISVMgU09GVFdB UkUgSVMgUFJPVklERUQgYGBBUyBJUycnIEFORCBXSVRIT1VUIEFOWQ0KIyAg RVhQUkVTUyBPUiBJTVBMSUVEIFdBUlJBTlRJRVMsIElOQ0xVRElORywgV0lU SE9VVCBMSU1JVEFUSU9OLCBUSEUNCiMgIElNUExJRUQgV0FSUkFOVElFUyBP RiBNRVJDSEFOVEFCSUxJVFkgQU5EIEZJVE5FU1MgRk9SIEFOWSBQQVJUSUNV TEFSDQojICBQVVJQT1NFLg0KDQoNCiAqLw0KDQojaW5jbHVkZSA8c3lzL3R5 cGVzLmg+DQojaW5jbHVkZSA8c3lzL3NvY2tldC5oPg0KI2luY2x1ZGUgPG5l dGluZXQvaW4uaD4NCiNpbmNsdWRlIDxuZXRkYi5oPg0KI2luY2x1ZGUgPHN0 ZGlvLmg+DQojaW5jbHVkZSA8c3RyaW5nLmg+DQojaW5jbHVkZSA8dW5pc3Rk Lmg+DQojaW5jbHVkZSA8dGltZS5oPg0KDQpleHRlcm4gaW50IGVycm5vOw0K DQojZGVmaW5lIEFSR1MgIm86aDp1Om46cDptOnQ6dzpzOmM6Ig0KDQptYWlu KGFyZ2MsYXJndikNCmludCBhcmdjOw0KY2hhciAqKmFyZ3Y7DQp7DQoJaW50 IGM7DQoJRklMRSAqZnA7DQoJY2hhciBob3N0bmFtZVs2NV07DQoJY2hhciBt eWhvc3RbNjVdOw0KCWNoYXIgbXl1c2VyWzI1XTsNCgljaGFyIHR5cGVbMjVd Ow0KCWNoYXIgdHRsWzEzXT0ibm9uZSI7DQoJaW50IHBvcnQ7DQoJaW50IHM7 DQoJaW50IHJldDsNCgl0aW1lX3QgdDsNCgljaGFyIG10aW1lWzEzXTsNCglj aGFyIHNldmVyaXR5WzEzXT0ibm9uZSI7DQoJY2hhciBjbGFzc1sxMjldPSJu b25lIjsNCgljaGFyIHBhc3N3b3JkWzI1XTsNCgljaGFyIG1lc3NhZ2VbMjU3 XTsNCgljaGFyIG1zZ1sxMDI0XTsNCglpbnQgcmFuZFs3XT17Myw2LDksMTIs MTUsMTgsMjF9Ow0KCXN0cnVjdCBob3N0ZW50ICpocDsNCglzdHJ1Y3Qgc29j a2FkZHJfaW4gc2luOw0KCWV4dGVybiBjaGFyICpvcHRhcmc7DQoJZXh0ZXJu IGludCBvcHRpbmQ7DQoJaW50IGVycmZsZz0wOw0KCWludCBjb3VudD0wOw0K CWludCBoX2ZsYWc9MDsNCglpbnQgdV9mbGFnPTA7DQoJaW50IG9fZmxhZz0w Ow0KCWludCBuX2ZsYWc9MDsNCglpbnQgcF9mbGFnPTA7DQoJaW50IHRfZmxh Zz0wOw0KCWludCB3X2ZsYWc9MDsNCglpbnQgc19mbGFnPTA7DQoJaW50IG1f ZmxhZz0wOw0KCWludCBjX2ZsYWc9MDsNCglpbnQgcV9vcHRpb249MDsNCglz dHJ1Y3QgdG0gKm15dGltZTsNCg0KDQoJb3B0YXJnID0gTlVMTDsNCgkJDQoJ d2hpbGUgKCFlcnJmbGcgJiYgKGMgPSBnZXRvcHQoYXJnYywgYXJndiwgQVJH UykpICE9IEVPRikNCiAgICAgICAgICAgICAgICAgICAgICAgc3dpdGNoIChj KSB7DQogICAgICAgICAgICAgICAgICAgICAgIGNhc2UgJ24nICAgICAgICA6 DQoJCQkJCQluX2ZsYWcgPSAxOw0KICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgIHN0cmNweShob3N0bmFtZSxvcHRhcmcpOw0KICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgIGJyZWFrOw0KICAgICAgICAgICAgICAgICAg ICAgICBjYXNlICdwJyAgICAgICAgOg0KCQkJCQkJcF9mbGFnID0gMTsNCiAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBwb3J0ID0gYXRvaShvcHRh cmcpOw0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIGJyZWFrOw0K ICAgICAgICAgICAgICAgICAgICAgICBjYXNlICd0JyAgICAgICAgOg0KCQkJ CQkJdF9mbGFnID0gMTsNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICBzdHJjcHkodHRsLG9wdGFyZyk7DQogICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgYnJlYWs7DQogICAgICAgICAgICAgICAgICAgICAgIGNhc2Ug J3cnICAgICAgICA6DQoJCQkJCQl3X2ZsYWcgPSAxOw0KICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgIHN0cmNweShwYXNzd29yZCxvcHRhcmcpOw0K ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIGJyZWFrOw0KICAgICAg ICAgICAgICAgICAgICAgICBjYXNlICdtJyAgICAgICAgOg0KCQkJCQkJbV9m bGFnID0gMTsNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBzdHJj cHkobWVzc2FnZSxvcHRhcmcpOw0KICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgIGJyZWFrOw0KICAgICAgICAgICAgICAgICAgICAgICBjYXNlICdz JyAgICAgICAgOg0KCQkJCQkJc19mbGFnID0gMTsNCiAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICBzdHJjcHkoc2V2ZXJpdHksb3B0YXJnKTsNCiAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBicmVhazsNCiAgICAgICAg ICAgICAgICAgICAgICAgY2FzZSAnYycgICAgICAgIDoNCgkJCQkJCWNfZmxh ZyA9IDE7DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgc3RyY3B5 KGNsYXNzLG9wdGFyZyk7DQogICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgYnJlYWs7DQogICAgICAgICAgICAgICAgICAgICAgIGNhc2UgJ28nICAg ICAgICA6DQoJCQkJCQlvX2ZsYWcgPSAxOw0KICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgIHN0cmNweSh0eXBlLG9wdGFyZyk7DQogICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgYnJlYWs7DQoJCQkJCWNhc2UgJ2gnCToN CgkJCQkJCWhfZmxhZyA9IDE7DQoJCQkJCQlzdHJjcHkobXlob3N0LG9wdGFy Zyk7DQoJCQkJCQlicmVhazsNCgkJCQkJY2FzZSAndScJOg0KCQkJCQkJdV9m bGFnID0gMTsNCgkJCQkJCXN0cmNweShteXVzZXIsb3B0YXJnKTsNCgkJCQkJ CWJyZWFrOw0KICAgICAgICAgICAgICAgICAgICAgICBkZWZhdWx0IDoNCiAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBlcnJmbGcrKzsNCgkJCQkJ CSBzeW50YXgoKTsNCgkJCQkJCSBleGl0KDIpOw0KICAgICAgICAgICAgICAg ICAgICAgICB9DQoNCgkvKiBpZiAtbyBub3Qgc3BlY2lmaWVkLCBhc3N1bWUg dHlwZSBub3JtYWwgKi8NCglpZiAob19mbGFnID09IDApIHsNCgkJc3RyY3B5 KHR5cGUsIm5vcm1hbCIpOw0KCX0NCglpZiAoIXN0cmNtcCgicXVlcnkiLHR5 cGUpIHx8ICFzdHJjbXAoInN1c3BlbmQiLHR5cGUpIHx8ICFzdHJjbXAoImRl bGV0ZSIsdHlwZSkgfHwgIXN0cmNtcCgiY29tbWVudCIsdHlwZSkgfHwgIXN0 cmNtcCgid2FrZXVwIix0eXBlKSkgew0KCQlpZihuX2ZsYWcgPT0gMCB8fCBw X2ZsYWcgPT0gMCB8fCB3X2ZsYWcgPT0gMCB8fCBtX2ZsYWcgPT0gMCkgew0K CQkJc3ludGF4KCk7DQoJCQlleGl0KDIpOw0KCQl9DQoJfQ0KCWVsc2UgaWYg KCFzdHJuY21wKCJjb3VudCIsdHlwZSw1KSB8fCAhc3RyY21wKCJub3JtYWwi LHR5cGUpIHx8ICFzdHJjbXAoInNsZWVwIix0eXBlKSB8fCAhc3RyY21wKCJt YXNrIix0eXBlKSB8fCAhc3RyY21wKCJldmVudCIsdHlwZSkpIHsNCgkJCWlm KG5fZmxhZyA9PSAwIHx8IHBfZmxhZyA9PSAwIHx8IHdfZmxhZyA9PSAwIHx8 IG1fZmxhZyA9PSAwIHx8IHRfZmxhZyA9PSAwIHx8IHNfZmxhZyA9PSAwIHx8 IGNfZmxhZyA9PSAwKSB7DQoJCQkJc3ludGF4KCk7DQoJCQkJZXhpdCgyKTsN CgkJCX0NCgl9DQoJZWxzZSBpZihuX2ZsYWcgPT0gMCB8fCBwX2ZsYWcgPT0g MCB8fCB3X2ZsYWcgPT0gMCB8fCBtX2ZsYWcgPT0gMCB8fCB0X2ZsYWcgPT0g MCB8fCBzX2ZsYWcgPT0gMCB8fCBjX2ZsYWcgPT0gMCkgew0KCQkJc3ludGF4 KCk7DQogICAgICAgICAgICAgICBleGl0KDIpOyANCgl9DQoNCglpZiAoIXN0 cmNtcCgicXVlcnkiLHR5cGUpKSB7DQoJCQlxX29wdGlvbiA9IDE7DQoJfQ0K DQoJLyogZ2V0IG15IGhvc3QgbmFtZSAqLw0KCWlmIChoX2ZsYWcgPT0gMCkg ew0KCQlnZXRob3N0bmFtZShteWhvc3Qsc2l6ZW9mKG15aG9zdCkpOw0KCX0N Cg0KCS8qIGdldCBteSB1c2VyIG5hbWUgKi8NCglpZiAodV9mbGFnID09IDAp IHsNCgkJY3VzZXJpZChteXVzZXIpOw0KCX0NCgkJDQoNCgkvKiBnZXQgbXkg dGltZSAqLw0KCXRpbWUoJnQpOw0KCW15dGltZT1sb2NhbHRpbWUoJnQpOw0K DQoJaWYoKGhwID0gZ2V0aG9zdGJ5bmFtZShob3N0bmFtZSkpID09IE5VTEwp IHsNCgkJZnByaW50ZihzdGRlcnIsICIlczogdW5rbm93biBob3N0LlxuIiwg aG9zdG5hbWUpOw0KCQlleGl0KDEpOw0KCX0NCg0KCXNwcmludGYobXRpbWUs IiUwMmQvJTAyZCAlMDJkOiUwMmQiLG15dGltZS0+dG1fbWRheSxteXRpbWUt PnRtX21vbisxLG15dGltZS0+dG1faG91cixteXRpbWUtPnRtX21pbik7DQoJ c3ByaW50Zihtc2csIiUtMTJzJS02NHMlLTI0cyUtMTJzJS0xMnMlLTI0cyUt MTI4cyUtMjU2cyUtMjRzXG4iLG10aW1lLG15aG9zdCxteXVzZXIsdHRsLHNl dmVyaXR5LHBhc3N3b3JkLGNsYXNzLG1lc3NhZ2UsdHlwZSk7DQoJLyoNCglw cmludGYoIm1zZz0lc1xuIixtc2cpOw0KCWV4aXQoMSk7DQoJKi8NCg0KCS8q IGluIGNhc2UgdGhlIHNlcnZlciBpcyBzaW5nbGUtdGhyZWFkZWQsIGJhY2sg b2ZmIGlmIHRoZSBjb25uZWN0aW9uDQoJZmFpbHMgYW5kIHRyeSBsYXRlciAt IHVwIHRvIDcgdGltZXMgKi8NCg0KCWNvdW50PTA7DQoJd2hpbGUoY291bnQg PCA3KSB7DQoJCWlmKChzID0gc29ja2V0KEFGX0lORVQsIFNPQ0tfU1RSRUFN LCAwKSkgPCAwKSB7DQoJCQlwZXJyb3IoImNsaWVudDogc29ja2V0Iik7DQoJ CQlleGl0KDEpOw0KCQl9DQoJCXNpbi5zaW5fZmFtaWx5ID0gQUZfSU5FVDsN CgkJc2luLnNpbl9wb3J0ID0gaHRvbnMocG9ydCk7DQoJCWJjb3B5KGhwLT5o X2FkZHIsICZzaW4uc2luX2FkZHIsIGhwLT5oX2xlbmd0aCk7DQoNCgkJaWYo IGNvbm5lY3QocywgJnNpbiwgc2l6ZW9mKHNpbikpIDwgMCkgew0KCQkJY2xv c2Uocyk7DQoJCQlzbGVlcChyYW5kW2NvdW50XSk7DQoJCQljb3VudCsrOw0K CQl9DQoJCWVsc2Ugew0KCQkJc2VuZChzLCBtc2csIHN0cmxlbihtc2cpLCAw KTsNCgkJCWlmKHFfb3B0aW9uKSB7DQoJCQkJZnAgPSBmZG9wZW4ocywgInIi KTsNCgkJCQl3aGlsZSAoKGMgPSBmZ2V0YyhmcCkpICE9IEVPRikgew0KCQkJ CQlwdXRjaGFyKGMpOw0KCQkJCX0NCgkJCQljbG9zZShzKTsNCgkJCQlleGl0 KDApOw0KCQkJfQ0KCQkJY2xvc2Uocyk7DQoJCQlleGl0KDApOw0KCQl9DQoJ CS8qIGNsb3NlKHMpOyAqLw0KCX0NCglleGl0KDEpOw0KfQ0KDQpzeW50YXgo KQ0Kew0KCXB1dHMoIkNvcHlyaWdodCAoQykgMTk5OSBKYXJyaXggU3lzdGVt cyB2MS4xIik7DQoJcHV0cygiICIpOw0KCXB1dHMoImVtc2cxIFstaCA8aG9z dG5hbWU+XSBbLXUgPHVzZXI+XSBbLW8gPG5vcm1hbHxzbGVlcHxtYXNrfGNv dW50fGV2ZW50Pl0gLW48aG9zdD4gLXA8cG9ydD4gLXQ8dGltZS10by1saXZl PiAtczxzZXZlcml0eT4gLXc8cGFzc3dvcmQ+IC1jIDxjbGFzcz4gLW08bWVz c2FnZT5cbiIpOw0KCXB1dHMoImVtc2cxIFstaCA8aG9zdG5hbWU+XSBbLXUg PHVzZXI+XSBbLW8gPHdha2V1cHxxdWVyeXxjb21tZW50fGRlbGV0ZXxzdXNw ZW5kPl0gLW48aG9zdD4gLXA8cG9ydD4gIC13PHBhc3N3b3JkPiAgLW08aG9z dG5hbWU6b2JqZWN0IC4uLi4uLi4uPlxuIik7DQp9DQo= --0-1007746717-943826516=:56372-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 28 14:50:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 24B7514BF3 for ; Sun, 28 Nov 1999 14:50:48 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id OAA75087; Sun, 28 Nov 1999 14:50:38 -0800 (PST) To: patrik@astrom.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Error compiling.. (Again, forgot the attachment) In-reply-to: Your message of Sun, 28 Nov 1999 23:01:56 +0100. Date: Sun, 28 Nov 1999 14:50:38 -0800 Message-ID: <75085.943829438@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , you wrot e: >Hi everyone... > >First of all I would like to state that IM not a programmer. Then you're probably not a `hacker' either. >Im trying to compile a program and IM getting a errormessage, I have >included the error message bellow. > >viking# cc emsg1.c >emsg1.c: In function `main': >emsg1.c:197: warning: passing arg 2 of `connect' from incompatible pointer >type >/var/tmp/ccRu22801.o: In function `main': >/var/tmp/ccRu22801.o(.text+0x5bb): undefined reference to `cuserid' >viking# > >The software IM trying to compile is a network monitoring tool named >"EMU", I've found it at "http://www.jarrix.com.au". > >At line 197 it looks like this... > >if( connect(s, &sin, sizeof(sin)) < 0) { Try replacing that line with: if( connect(s, (struct sockaddr *) &sin, sizeof(sin)) < 0) { That should fix your `incompatable pointer' warning. As regards to your link-time error (missing `cuserid') I'm afraid I can't be of any help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 28 15: 9:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id E28EE14A2A for ; Sun, 28 Nov 1999 15:09:39 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id PAA11298; Sun, 28 Nov 1999 15:09:15 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Sun, 28 Nov 1999 15:09:15 -0800 Date: Sun, 28 Nov 1999 15:09:15 -0800 (PST) From: Kip Macy X-Sender: kip@luna To: "Ronald F. Guilmette" Cc: patrik@astrom.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Error compiling.. (Again, forgot the attachment) In-Reply-To: <75085.943829438@monkeys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: rfg@monkeys.com,patrik@astrom.net,freebsd-hackers@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cuserid is in the compatibility library, from the man page: CUSERID(3) FreeBSD Library Functions Manual CUSERID(3) NAME cuserid - get user name associated with effective UID SYNOPSIS #include char * cuserid(char *s) DESCRIPTION The cuserid function is made obsolete by getpwuid. It is available from the compatibility library, libcompat. To get the program to link just add: -lcompat On Sun, 28 Nov 1999, Ronald F. Guilmette wrote: > > In message , you wrot > e: > > >Hi everyone... > > > >First of all I would like to state that IM not a programmer. > > Then you're probably not a `hacker' either. > > >Im trying to compile a program and IM getting a errormessage, I have > >included the error message bellow. > > > >viking# cc emsg1.c > >emsg1.c: In function `main': > >emsg1.c:197: warning: passing arg 2 of `connect' from incompatible pointer > >type > >/var/tmp/ccRu22801.o: In function `main': > >/var/tmp/ccRu22801.o(.text+0x5bb): undefined reference to `cuserid' > >viking# > > > >The software IM trying to compile is a network monitoring tool named > >"EMU", I've found it at "http://www.jarrix.com.au". > > > >At line 197 it looks like this... > > > >if( connect(s, &sin, sizeof(sin)) < 0) { > > Try replacing that line with: > > if( connect(s, (struct sockaddr *) &sin, sizeof(sin)) < 0) { > > That should fix your `incompatable pointer' warning. > > As regards to your link-time error (missing `cuserid') I'm afraid I > can't be of any help. > > > 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 Nov 28 15:38:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles501.castles.com [208.214.165.65]) by hub.freebsd.org (Postfix) with ESMTP id F3DAC15322 for ; Sun, 28 Nov 1999 15:38:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA01055; Sun, 28 Nov 1999 15:38:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199911282338.PAA01055@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ronald F. Guilmette" Cc: patrik@astrom.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Error compiling.. (Again, forgot the attachment) In-reply-to: Your message of "Sun, 28 Nov 1999 14:50:38 PST." <75085.943829438@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Nov 1999 15:38:28 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As regards to your link-time error (missing `cuserid') I'm afraid I > can't be of any help. You could read the cuserid(3) manpage, which should tell you enough to get yourself sorted out. -- \\ 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 Sun Nov 28 16:44: 3 1999 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 97FEE14A00 for ; Sun, 28 Nov 1999 16:43:48 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.0.4] ident=ben) by scientia.demon.co.uk with smtp (Exim 3.092 #1) id 11sDPg-00042L-00; Sun, 28 Nov 1999 23:07:24 +0000 Date: Sun, 28 Nov 1999 23:07:24 +0000 From: Ben Smithurst To: patrik@astrom.net Cc: freebsd-hackers@freebsd.org Subject: Re: Error compiling.. Message-ID: <19991128230724.A926@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG patrik@astrom.net wrote: > Im trying to compile a program and IM getting a errormessage, I have > included the error message bellow. > > viking# cc emsg1.c > emsg1.c: In function `main': > emsg1.c:197: warning: passing arg 2 of `connect' from incompatible pointer > type > /var/tmp/ccRu22801.o: In function `main': > /var/tmp/ccRu22801.o(.text+0x5bb): undefined reference to `cuserid' > viking# > > The software IM trying to compile is a network monitoring tool named > "EMU", I've found it at "http://www.jarrix.com.au". > > At line 197 it looks like this... > > if( connect(s, &sin, sizeof(sin)) < 0) { Cast the second argument to (struct sockaddr *). i.e. if (connect(s, (struct sockaddr *)&sin, sizeof sin) < 0) { ... > And where it complains about the "cuserid" bit it looks like this... > > /* get my user name */ > if (u_flag == 0) { > cuserid(myuser); > } RTFM. "man cuserid" says: DESCRIPTION The cuserid function is made obsolete by getpwuid. It is available from the compatibility library, libcompat. So you need to add -lcompat to the command line, or take the manual page's advice and use getpwuid (with an argument of geteuid()) instead, and copy the pw_name member of the returned structure to myuser. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 28 21: 5:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from c62443-a.frmt1.sfba.home.com (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 973601512B for ; Sun, 28 Nov 1999 21:05:14 -0800 (PST) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id VAA01931; Sun, 28 Nov 1999 21:05:14 -0800 Date: Sun, 28 Nov 1999 21:05:14 -0800 From: Arun Sharma Message-Id: <199911290505.VAA01931@c62443-a.frmt1.sfba.home.com> To: freebsd-hackers@freebsd.org Subject: Fwd: Re: kstat - an API for gathering kernel stats Reply-To: adsharma@sharmas.dhs.org (Arun Sharma) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ For some reason, this post through muc.lists.freebsd.hackers gateway didn't show up on the mailing list. Forwarding it to the mailing list.. ] On Thu, 04 Nov 1999 20:38:50 -0800, Mike Smith wrote: > > I don't see any examples in sys/modules. The SYSCTL_INT macros eventually > > expands to DATA_SET which puts certain data in a different ELF section. > > You don't do anything magic at all; it's handled invisibly by the > kernel linker. I was thinking about implementing SMP cpu stats using sysctl today and I have a question - can I create sysctl nodes dynamically ? i.e. for (cpu = 0; cpu < get_num_cpus(); cpu++) { /* create sysctl node here ? */ } Also, one simple solution to maintaining per cpu stats is to put the whole thing in struct globaldata. All existing code remains unchanged and automagically updates the per cpu stats. I may need to add some additional variables, which reflect system wide data. Now, if I put stuff in globaldata and try to export it using sysctl, things get a little more complex. One solution to the above problem is to use SMPpt relative addresses in the sysctl declarations. But given that the number of CPUs is known only at runtime, we come back to the first question in this mail. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 28 23:17:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from 24-25-220-29.san.rr.com (24-25-220-29.san.rr.com [24.25.220.29]) by hub.freebsd.org (Postfix) with ESMTP id C4CCF15343 for ; Sun, 28 Nov 1999 23:17:18 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by 24-25-220-29.san.rr.com (8.9.3/8.8.8) with ESMTP id XAA23882; Sun, 28 Nov 1999 23:16:54 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38422866.6779B268@gorean.org> Date: Sun, 28 Nov 1999 23:16:54 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) References: 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: > > On Mon, 22 Nov 1999, David E. Cross wrote: > > > Ok... I have *had* it with the meta, but not really, lockd. Are there any > > kernel issues with correctly implimenting rpc.lockd? I can't help with the code, but put me down as both very interested, and willing to help test. We have a mixed sun, netapp and freebsd nfs environment, and I have some freebsd machines that I can sacrifice to the cause. We are pretty desperate for working NFS file locking at work as well. FWIW, we tried the linux version of lockd on linux and not only did it suck potatoes, it was frequently the cause of that server crashing. I would stay completely away from it. Thanks, Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 0: 3:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by hub.freebsd.org (Postfix) with ESMTP id 45C0214F41 for ; Mon, 29 Nov 1999 00:03:14 -0800 (PST) (envelope-from conrad@apple.com) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.9.3/8.9.3) with ESMTP id AAA19385 for ; Mon, 29 Nov 1999 00:03:13 -0800 (PST) Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com (mailgate1.apple.com- SMTPRS 2.0.15) with ESMTP id ; Mon, 29 Nov 1999 00:03:04 -0800 Received: from [17.202.43.185] (wa.apple.com [17.202.43.185]) by scv3.apple.com (8.9.3/8.9.3) with ESMTP id AAA19943; Mon, 29 Nov 1999 00:02:53 -0800 (PST) X-Sender: conrad@mail.apple.com Message-Id: In-Reply-To: <19991125163613.A2147@dustdevil.waterspout.com> References: <199911222138.QAA76632@cs.rpi.edu> MIME-Version: 1.0 Date: Mon, 29 Nov 1999 00:02:42 -0800 To: "C. Stephen Gunn" , hackers@freebsd.org From: Conrad Minshall Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) Cc: rick@snowhite.cis.uoguelph.ca Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:36 PM -0800 11/25/99, C. Stephen Gunn wrote: >On Mon, Nov 22, 1999 at 02:07:58PM -0800, Alfred Perlstein wrote: >> > Does NetBSD have a working rpc.lockd... that would make this much easier. >> >> at a glance at http://cvsweb.netbsd.org/... no. >I'm fairly certain that rpc.lockd is included with Darwin from Apple, >I've not closely compared it to what we have in -STABLE or -CURRENT >to see if it actually works. It doesn't, sorry... if someone gets a *BSD version of NFS locking operating I'd help see it into Darwin. BTW, is anyone working on NFS Version 4 for BSD? Rick? -- Conrad Minshall ... conrad@apple.com ... 408 974-2749 Apple Computer ... Mac OS X Core Operating Systems ... NFS/UDF/etc Alternative email address: rad@acm.org. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 0:18: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 7182014C1D for ; Mon, 29 Nov 1999 00:17:59 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id DAA96450; Mon, 29 Nov 1999 03:17:54 -0500 (EST) Message-Id: <199911290817.DAA96450@cs.rpi.edu> To: Doug Barton Cc: Alfred Perlstein , "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) In-Reply-To: Message from Doug Barton of "Sun, 28 Nov 1999 23:16:54 PST." <38422866.6779B268@gorean.org> Date: Mon, 29 Nov 1999 03:17:54 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I am starting to get pretty seriously involved. It looks pretty easy, just a lot of small details (this is the kind of coding I like :) A couple of issues need to be worked out. First I need to backport the FH open/stat/etc. calls to -STABLE. The main reason for this is that I am developing rpc.lockd for out main servers, which for obvious reasons run -STABLE. Second I need some input and advice. Looking at Solaris' lockd, they use NLM version 2 as a method of IPC between lockd and statd this is an undocumented interface. I would suggest a unix domain socket as an alternate method (any objections). This I feel has a number of advantages, such as providing an easier Kernel interface to the user-land lock manager (it is my reading that rpc.lockd should perform the tasks of maintaining local locks on remote servers as well as managing locks on local filesystems from remote servers.) Thank you to the person who provided the Open-Group Spec. I had read that it was available from them in the NFS3 RFC, I just figured I would need to pay much $$$ to actually get it :) -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 1: 8:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 7285914E19 for ; Mon, 29 Nov 1999 01:08:47 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 273981927; Mon, 29 Nov 1999 10:09:35 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 263C249EC; Mon, 29 Nov 1999 10:09:35 +0100 (CET) Date: Mon, 29 Nov 1999 10:09:35 +0100 (CET) From: Andrzej Bialecki To: Arun Sharma Cc: freebsd-hackers@freebsd.org Subject: Re: Fwd: Re: kstat - an API for gathering kernel stats In-Reply-To: <199911290505.VAA01931@c62443-a.frmt1.sfba.home.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, 28 Nov 1999, Arun Sharma wrote: > > [ For some reason, this post through muc.lists.freebsd.hackers gateway didn't > show up on the mailing list. Forwarding it to the mailing list.. ] > > On Thu, 04 Nov 1999 20:38:50 -0800, Mike Smith wrote: > > > I don't see any examples in sys/modules. The SYSCTL_INT macros eventually > > > expands to DATA_SET which puts certain data in a different ELF section. > > > > You don't do anything magic at all; it's handled invisibly by the > > kernel linker. > > I was thinking about implementing SMP cpu stats using sysctl today and > I have a question - can I create sysctl nodes dynamically ? > > i.e. > > for (cpu = 0; cpu < get_num_cpus(); cpu++) { > /* create sysctl node here ? */ > } Yes. See for example linux emulator or my SPY module: http://www.freebsd.org/~abial/spy You can also create whole new branches, as the second example shows. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 2:26:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 826DD14C1F for ; Mon, 29 Nov 1999 02:26:38 -0800 (PST) (envelope-from K.J.Koster@research.kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #35196) with ESMTP id <01JIWP8YDRP000025R@research.kpn.com> for freebsd-hackers@freebsd.org; Mon, 29 Nov 1999 11:26:37 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Mon, 29 Nov 1999 11:26:37 +0100 Content-return: allowed Date: Mon, 29 Nov 1999 11:26:33 +0100 From: "Koster, K.J." Subject: RE: cdrom speed adjustment ioctl To: "'freebsd-hackers@freebsd.org'" Message-id: <59063B5B4D98D311BC0D0001FA7E45220FD062@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've just hacked a new ioctl into the ATAPI cdrom driver, which > lets the user to specify (pronounce: ``slow down'' :) the speed > of todays' extremely high speed drives. > There would not be such a thing for SCSI cdrom's too? It would probably squeeze a few extra months out of my cdrom player. On some cd's (mainly ones you get with magazines and books) it's making gut-wrenching noises and spinning up and down all the time. Interesting fact: the FreeBSD cdrom are never a problem. Does cdrom.com balance them before shipping them? Kees Jan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 2:52: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id A0A2114FE4 for ; Mon, 29 Nov 1999 02:52:00 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn53.imasy.or.jp [202.227.24.245]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id TAA24550; Mon, 29 Nov 1999 19:51:56 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199911291051.TAA24550@tasogare.imasy.or.jp> To: Bryan Collins Cc: hackers@FreeBSD.ORG Subject: Re: more softpower/apm.. X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 29 Nov 1999 19:51:49 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 26 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Bryan. > Does anyone know if its possible for FreeBSD to execute a halt from > the powerswitch? > > >From reading the apmd doco, this is what apmd is suppose to do, handle > events from the APM bios and execute according to apmd.conf > > If an ATX powersupply/motherboard is setup to suspend on power button, > (i.e hold down for 5 seconds to turn off) > can FreeBSD pick up this button press and do clean shutdown? > I tried running apmd -dv, but I cant seem to see any events from the power > button pressing. Apmd was developed for you :-) You can reject suspend request on power button and execute shutdown -p instead. For example, My box was setup to suspend on power button and issues USERSUSPENDREQ, so my apmd.conf is like this; apm_event USERSUSPENDREQ { reject; exec "shutdown -p now"; } Have fun! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 3: 8:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay4.mail.uk.psi.net (relay4.mail.uk.psi.net [154.32.111.6]) by hub.freebsd.org (Postfix) with ESMTP id D675A14FE4 for ; Mon, 29 Nov 1999 03:08:21 -0800 (PST) (envelope-from amobbs@allstor-sw.co.uk) Received: from mail.plasmon.co.uk ([193.115.5.217]) by relay4.mail.uk.psi.net with smtp (Exim 2.12 #2) id 11sOdO-00059a-00; Mon, 29 Nov 1999 11:06:18 +0000 Received: by mail.plasmon.co.uk(Lotus SMTP MTA v4.6.4 (830.2 3-23-1999)) id 80256838.003D0F6D ; Mon, 29 Nov 1999 11:06:56 +0000 X-Lotus-FromDomain: PLASNOTES From: amobbs@allstor-sw.co.uk To: "Koster, K.J." Cc: freebsd-hackers@freebsd.org Message-ID: <80256838.003D0E73.00@mail.plasmon.co.uk> Date: Mon, 29 Nov 1999 11:06:53 +0000 Subject: RE: cdrom speed adjustment ioctl Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >There would not be such a thing for SCSI cdrom's too? It would probably >squeeze a few extra months out of my cdrom player. On some cd's (mainly ones >you get with magazines and books) it's making gut-wrenching noises and >spinning up and down all the time. No idea if there's an ioctl, but you should be able to do this with camcontrol, e.g. if your drive supports the MMC Set CD Speed command: camcontrol -n cd -u -c "BB 00 XX XX 00 00 00 00 00 00 00 00" Where is the number of the CD device you want to set the speed of, and XX XX is the hex of the desired speed in kbps. Andrew. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 3:21:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lindt.urgle.com (lindt.urgle.com [195.173.172.169]) by hub.freebsd.org (Postfix) with ESMTP id 83E9114E40 for ; Mon, 29 Nov 1999 03:21:50 -0800 (PST) (envelope-from mike@urgle.com) Received: from mike by lindt.urgle.com with local (Exim 3.03 #1) id 11sOsC-000ALf-00; Mon, 29 Nov 1999 11:21:36 +0000 Date: Mon, 29 Nov 1999 11:21:36 +0000 From: Mike Bristow To: amobbs@allstor-sw.co.uk Cc: "Koster, K.J." , freebsd-hackers@freebsd.org Subject: Re: cdrom speed adjustment ioctl Message-ID: <19991129112136.A39768@lindt.urgle.com> References: <80256838.003D0E73.00@mail.plasmon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <80256838.003D0E73.00@mail.plasmon.co.uk> X-Rated: Noriega, militia Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 29, 1999 at 11:06:53AM +0000, amobbs@allstor-sw.co.uk wrote: > >There would not be such a thing for SCSI cdrom's too? It would probably > >squeeze a few extra months out of my cdrom player. On some cd's (mainly ones > >you get with magazines and books) it's making gut-wrenching noises and > >spinning up and down all the time. > > No idea if there's an ioctl, but you should be able to do this with camcontrol, > e.g. if your drive supports the MMC Set CD Speed command: > > camcontrol -n cd -u -c "BB 00 XX XX 00 00 00 00 00 00 00 00" > > Where is the number of the CD device you want to set the speed of, and XX XX > is the hex of the desired speed in kbps. Is this a project for a rainy day I see before me? cdspeed(1) Imaginary Man Page cdspeed(1) NAME cdspeed - control (slow down!) the speed that a cdrom will operate at. SYOPSIS cdspeed YADDA yadda yadda yadda FreeBSD 3.3 November 29 1999 1 -- Mike Bristow, Geek At Large ``Beware of Invisible Cows'' GK/RT0011 - Essential reading for train-spotters. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 4:59:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 5E46114E40; Mon, 29 Nov 1999 04:59:29 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id NAA95132; Mon, 29 Nov 1999 13:59:05 +0100 (CET) (envelope-from des) To: Tony Landells Cc: hackers@FreeBSD.ORG Subject: Re: new IPFW References: <199911242152.IAA26077@tungsten.austclear.com.au> From: Dag-Erling Smorgrav Date: 29 Nov 1999 13:59:05 +0100 In-Reply-To: Tony Landells's message of "Thu, 25 Nov 1999 08:52:28 +1100" Message-ID: Lines: 36 User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moving from -ipfw and -arch to -hackers] Tony Landells writes: > One concern I would have with that is that there are a lot of tools > built on BPF that I would prefer to not be able to run on the firewall. Don't confuse BPF with promiscuous mode. BPF is simply a programmable packet filter and does not in and of itself represent a security risk. Promiscuous mode allows a host to capture packets not destined to itself, and may represent a security risk on shared media networks (e.g. 10Base2, unswitched 10BaseT). The attached patch prevents switching into promiscuous mode when running in "Network secure mode" (securelevel 3 or higher). DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no Index: if.c =================================================================== RCS file: /home/ncvs/src/sys/net/if.c,v retrieving revision 1.77 diff -u -r1.77 if.c --- if.c 1999/11/22 02:44:51 1.77 +++ if.c 1999/11/29 12:52:07 @@ -908,6 +908,8 @@ int error; if (pswitch) { + if (securelevel >= 3) + return (EPERM); /* * If the device is not configured up, we cannot put it in * promiscuous mode. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 5: 7:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id BF98D14A20 for ; Mon, 29 Nov 1999 05:07:26 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id NAA11271; Mon, 29 Nov 1999 13:47:31 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <199911291247.NAA11271@info.iet.unipi.it> Subject: Re: new IPFW In-Reply-To: from Dag-Erling Smorgrav at "Nov 29, 1999 01:59:05 pm" To: Dag-Erling Smorgrav Date: Mon, 29 Nov 1999 13:47:31 +0100 (CET) Cc: Tony Landells , hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 > The attached patch prevents switching into promiscuous mode when > running in "Network secure mode" (securelevel 3 or higher). What happens with yout patch if i need to run an mrouted on such a machine ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 5:21:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 933341510B for ; Mon, 29 Nov 1999 05:21:10 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id OAA95218; Mon, 29 Nov 1999 14:21:07 +0100 (CET) (envelope-from des) To: Luigi Rizzo Cc: Tony Landells , hackers@FreeBSD.ORG Subject: Re: new IPFW References: <199911291247.NAA11271@info.iet.unipi.it> From: Dag-Erling Smorgrav Date: 29 Nov 1999 14:21:07 +0100 In-Reply-To: Luigi Rizzo's message of "Mon, 29 Nov 1999 13:47:31 +0100 (CET)" Message-ID: Lines: 12 User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo writes: > > The attached patch prevents switching into promiscuous mode when > > running in "Network secure mode" (securelevel 3 or higher). > What happens with yout patch if i need to run an mrouted on such a > machine ? It'll crash and burn, which demonstrates the inadequacy of the secure level mechanism. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 9:31:55 1999 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 A15EC14FB9 for ; Mon, 29 Nov 1999 09:31:53 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA06859; Mon, 29 Nov 1999 09:31:43 -0800 (PST) (envelope-from dillon) Date: Mon, 29 Nov 1999 09:31:43 -0800 (PST) From: Matthew Dillon Message-Id: <199911291731.JAA06859@apollo.backplane.com> To: "David E. Cross" Cc: Doug Barton , Alfred Perlstein , "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) References: <199911290817.DAA96450@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Well, I am starting to get pretty seriously involved. It looks pretty :easy, just a lot of small details (this is the kind of coding I like :) : :A couple of issues need to be worked out. First I need to backport :the FH open/stat/etc. calls to -STABLE. The main reason for this is that :... I can't help with the code either - what little time I have available is going towards the SMP project. I will be shorting beginning work work on another startup and consulting on a second (but that won't stop me from continuing to badger core to remove the idiotic extra restrictions they still have on my commit privs). But I do I have time to test patchsets as your work progresses. My test boxes are currently split into a -stable test box and a -current test box so I can test under both. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 9:37:42 1999 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 879CF1522E for ; Mon, 29 Nov 1999 09:37:41 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA06933; Mon, 29 Nov 1999 09:37:39 -0800 (PST) (envelope-from dillon) Date: Mon, 29 Nov 1999 09:37:39 -0800 (PST) From: Matthew Dillon Message-Id: <199911291737.JAA06933@apollo.backplane.com> To: "David E. Cross" , Doug Barton , Alfred Perlstein , "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) References: <199911290817.DAA96450@cs.rpi.edu> <199911291731.JAA06859@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : I can't help with the code either - what little time I have available : is going towards the SMP project. I will be shorting beginning work ^^^^^ shortly. Bleh. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 10: 2:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14]) by hub.freebsd.org (Postfix) with ESMTP id 1F2CE15282 for ; Mon, 29 Nov 1999 10:02:37 -0800 (PST) (envelope-from mda@discerning.com) Received: from MDAXKE (cm-24-142-61-115.cableco-op.ispchannel.com [24.142.61.115]) by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id JAA22882 for ; Mon, 29 Nov 1999 09:59:03 -0800 (PST) Date: Mon, 29 Nov 1999 09:58:20 -0800 From: "Mark D. Anderson" To: freebsd-hackers@freebsd.org Subject: SYN flood and freebsd? Message-ID: <3271662348.943869500@MDAXKE> X-Mailer: Mulberry (Win32) [2.0.0a6, s/n U-301276] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (I've struck out now on freebsd-security and freebsd-net, now trying freebsd-hackers....) i've searched around deja and freebsd.org and come up wanting (email archives show rarely show resolutions...). what is the current status in stable and latest regarding defense against SYN flood, and how is it implemented? i found some discussion regarding the inadequacy of the "SYN cookie" defense added to linux -- i couldn't make out whether that fix has actually been withdrawn from linux or not. i also didn't find an explanation of exactly what was bad about it -- something about firewalls or NAT. see for example: http://x41.deja.com/getdoc.xp?AN=491586304&CONTEXT=942635225.1891434518&hitnum=26 and openbsd has apparently settled on a random dropping of old half-open connections. appreciate some clarification on this, as well as pointers to where answers to things like this might be found, for those of us who don't want to run grep through kernel sources. -mda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message ---------- End Forwarded Message ---------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 10:10:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 2382615402 for ; Mon, 29 Nov 1999 10:10:26 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id MAA50933 for hackers@freebsd.org; Mon, 29 Nov 1999 12:12:23 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <199911291812.MAA50933@celery.dragondata.com> Subject: Getting structures from kernelspace to userspace To: hackers@freebsd.org Date: Mon, 29 Nov 1999 12:12:23 -0600 (CST) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the embedded system I'm working on, I have a need to get detailed hard drive information in a userland process. Specifically, I need the contents of all the values in wddrives[]. While I've made it work, I've run into a few difficulties. If someone thinks this is useful enough, I'll clean it up to make it more presentable for inclusion, as well as a port to the ATA driver. I added the following routine to sys/i386/isa/wd.c : static intsysctl_hw_wddrives SYSCTL_HANDLER_ARGS{ int error=0; int i; for (i=0;i #include static struct disk wddrives[NWD]; /* table of units */ void foo(void) { unsigned int len; int i; len = sizeof(struct disk) * NWD; for (i=0;i; Mon, 29 Nov 1999 11:01:27 -0800 (PST) (envelope-from ghelmer@scl.ameslab.gov) Received: from demios.ether.scl.ameslab.gov ([147.155.137.54]) by mailhub.scl.ameslab.gov with esmtp (Exim 3.02 #1) id 11sW2x-000GZ8-00; Mon, 29 Nov 1999 13:01:11 -0600 Date: Mon, 29 Nov 1999 13:01:08 -0600 From: Guy Helmer To: "Mark D. Anderson" Cc: freebsd-hackers@freebsd.org Subject: Re: SYN flood and freebsd? In-Reply-To: <3271662348.943869500@MDAXKE> 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, 29 Nov 1999, Mark D. Anderson wrote: > i've searched around deja and freebsd.org and come up wanting > (email archives show rarely show resolutions...). > > what is the current status in stable and latest regarding > defense against SYN flood, and how is it implemented? > > i found some discussion regarding the inadequacy of the "SYN cookie" > defense added to linux -- i couldn't make out whether that > fix has actually been withdrawn from linux or not. > i also didn't find an explanation of exactly what was bad about > it -- something about firewalls or NAT. > see for example: > http://x41.deja.com/getdoc.xp?AN=491586304&CONTEXT=942635225.1891434518&hitnum=26 I can't comment about the SYN-cookie approach, since I haven't heard about its pitfalls. > and openbsd has apparently settled on a random dropping of > old half-open connections. > > appreciate some clarification on this, as well as pointers > to where answers to things like this might be found, for > those of us who don't want to run grep through kernel sources. There was some discussion about this on freebsd-net or freebsd-hackers in September 1996 which can be reviewed by using the mail list search page at http://www.freebsd.org/search/search.html. Anyway, the CVS history gives the definitive answer for which you are looking. The pages at http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_input.c and http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/uipc_socket2.c shows that random drop was implemented (see tcp_input.c versions 1.54 & 1.55 and uipc_socket2.c versions 1.15 & 1.16). Guy Guy Helmer, Ph.D. Candidate, Iowa State University Dept. of Computer Science Research Assistant, Ames Laboratory --- ghelmer@scl.ameslab.gov Research Assistant, Dept. of Computer Science --- ghelmer@cs.iastate.edu Teaching Assistant, ComS 652 Distributed Operating Systems http://www.cs.iastate.edu/~ghelmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 11:34:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wit401310.student.utwente.nl (wit401310.student.utwente.nl [130.89.236.150]) by hub.freebsd.org (Postfix) with ESMTP id 3917514F62 for ; Mon, 29 Nov 1999 11:34:29 -0800 (PST) (envelope-from dalroi@wit401310.student.utwente.nl) Received: from wit401310.student.utwente.nl (localhost [127.0.0.1]) by wit401310.student.utwente.nl (Postfix) with ESMTP id E6A051EC0 for ; Mon, 29 Nov 1999 20:34:41 +0100 (CET) Date: Mon, 29 Nov 1999 20:34:40 +0100 (CET) From: Alban Hertroys Subject: random (6) To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <19991129193441.E6A051EC0@wit401310.student.utwente.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a small patch that adds an option (-s) to the random command. It prints one random line out of every _denominator_ lines to stdout. For example, if you feed it an ls of /bin (32 files) to stdin, with "random -s 4" you will get series of 8 (=32/4) random filenames from /bin. dalroi * cd /bin dalroi * ls|random -s 4 chio dd domainname hostname mv red rmail test If anybody is interested I'll send it, according to the guidelines (But then I'll have to read up a bit on them first, this is my first FreeBSD patch). -- Alban Hertroys http://wit401310.student.utwente.nl - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Install a BSD and become religious. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 12:50:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id 9B33F153A5 for ; Mon, 29 Nov 1999 12:50:15 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id PAA03408; Mon, 29 Nov 1999 15:52:17 -0500 (EST) Date: Mon, 29 Nov 1999 15:52:17 -0500 From: Dan Moschuk To: Conrad Minshall Cc: "C. Stephen Gunn" , hackers@FreeBSD.ORG, rick@snowhite.cis.uoguelph.ca Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) Message-ID: <19991129155217.C2999@spirit.jaded.net> References: <199911222138.QAA76632@cs.rpi.edu> <19991125163613.A2147@dustdevil.waterspout.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from conrad@apple.com on Mon, Nov 29, 1999 at 12:02:42AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | >I'm fairly certain that rpc.lockd is included with Darwin from Apple, | >I've not closely compared it to what we have in -STABLE or -CURRENT | >to see if it actually works. | | It doesn't, sorry... if someone gets a *BSD version of NFS locking operating | I'd help see it into Darwin. | | BTW, is anyone working on NFS Version 4 for BSD? Rick? A few of us talked about this on IRC a few weeks ago and it was decided that when/if we implement NFSv4 it would have to be from scratch. A pretty big task. -- Dan Moschuk (TFreak!dan@freebsd.org) "Cure for global warming: One giant heatsink and dual fans!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 13:28:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 93C9C15082 for ; Mon, 29 Nov 1999 13:28:22 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id NAA12198; Mon, 29 Nov 1999 13:26:35 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id NAA01584; Mon, 29 Nov 1999 13:26:34 -0800 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA16757; Mon, 29 Nov 99 13:26:30 PST Message-Id: <3842EF84.68C78E5A@softweyr.com> Date: Mon, 29 Nov 1999 14:26:28 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Dag-Erling Smorgrav Cc: Luigi Rizzo , Tony Landells , hackers@FreeBSD.ORG Subject: Re: new IPFW References: <199911291247.NAA11271@info.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > Luigi Rizzo writes: > > > The attached patch prevents switching into promiscuous mode when > > > running in "Network secure mode" (securelevel 3 or higher). > > > > What happens with yout patch if i need to run an mrouted on such a > > machine ? > > It'll crash and burn, which demonstrates the inadequacy of the secure > level mechanism. Or you start mrouted before going to securelevel 3. -- "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 Nov 29 16:59: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lobster.baynetworks.com (ns3.BayNetworks.COM [192.32.253.3]) by hub.freebsd.org (Postfix) with ESMTP id CD92415623 for ; Mon, 29 Nov 1999 16:59:01 -0800 (PST) (envelope-from bwithrow@engeast.BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by lobster.baynetworks.com (8.9.1/8.9.1) with ESMTP id UAA16682; Mon, 29 Nov 1999 20:02:03 -0500 (EST) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id TAA18650; Mon, 29 Nov 1999 19:54:09 -0500 (EST) Received: from tuva.engeast.baynetworks.com (tuva [192.32.150.102]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id TAA09574; Mon, 29 Nov 1999 19:58:28 -0500 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.9.3/8.9.3) with ESMTP id TAA42935; Mon, 29 Nov 1999 19:58:17 -0500 (EST) (envelope-from bwithrow@tuva.engeast.baynetworks.com) Message-Id: <199911300058.TAA42935@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@freebsd.org Cc: bwithrow@engeast.BayNetworks.COM, tim@franklin.matlink.demon.co.uk Subject: Linking causes sendmail gas Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Nov 1999 19:58:17 -0500 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had this problem across the last two or three releases of FreeBSD. Currently I'm running: bash-2.03$ uname -sr FreeBSD 3.2-RELEASE And whenever I *link* a particular program, sendmail starts complaining! Nov 29 18:55:53 tuva sendmail[36003]: NOQUEUE: SYSERR: putoutmsg (NO-HOST): error on output channel sending "451 fill_fd: before readcf: fd 1 not open: Bad file descriptor": Input/output error Nov 29 18:55:53 tuva sendmail[36003]: NOQUEUE: SYSERR(bwithrow): fill_fd: before readcf: fd 1 not open: Bad file descriptor Nov 29 18:55:57 tuva sendmail[36003]: NOQUEUE: SYSERR(bwithrow): fill_fd: before readcf: fd 2 not open: Bad file descriptor Nov 29 19:23:59 tuva sendmail[40563]: NOQUEUE: SYSERR: putoutmsg (NO-HOST): error on output channel sending "451 fill_fd: before main() initmaps: fd 1 not open: Bad file descriptor": Input/output error Nov 29 19:23:59 tuva sendmail[40563]: NOQUEUE: SYSERR(bwithrow): fill_fd: before main() initmaps: fd 1 not open: Bad file descriptor Nov 29 19:24:02 tuva sendmail[40563]: NOQUEUE: SYSERR(bwithrow): fill_fd: before main() initmaps: fd 2 not open: Bad file descriptor Nov 29 19:24:47 tuva sendmail[42779]: NOQUEUE: SYSERR: putoutmsg (NO-HOST): error on output channel sending "451 fill_fd: before readcf: fd 1 not open: Bad file descriptor": Input/output error Nov 29 19:24:47 tuva sendmail[42779]: NOQUEUE: SYSERR(bwithrow): fill_fd: before readcf: fd 1 not open: Bad file descriptor Nov 29 19:25:01 tuva sendmail[42779]: NOQUEUE: SYSERR(bwithrow): fill_fd: before readcf: fd 2 not open: Bad file descriptor The link line looks like this (with the names changed to protect the innocent): gcc -o /someplace/thing /someplace/thingMain.o /someplace/os_host.o /someplace/host_stubs.o /someplace/os_host_stubs.o -L/someplace -lsystem -lcommands -lshow -lnewshow -lndm -lscripts -lndmmql -lsystem -lmql -lmib -lmibdb -ltype -ltcllite -lutil -ledit -lcompat Why would linking a program cause sendmail to complain? I'm suspicious that it isn't *entirely* a sendmail problem, since it is triggered by normal system activity unrelated to mail processing. If nothing else it suggest a possible denial-of-service attack doesn't it? Suggestions? Comments? Searching through the archives shows that at least one other person has this problem besides me, and I haven't found a solution posted. Reference follow: http://www.freebsd.org/cgi/getmsg.cgi?fetch=1894326+1897263+/usr/local/www/db/text/1999/freebsd-questions/19990509.freebsd-questions -- Robert Withrow -- (+1 978 288 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 20: 4:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from turing.csis.gvsu.edu (turing.csis.gvsu.edu [148.61.162.181]) by hub.freebsd.org (Postfix) with SMTP id 1E82A156BB for ; Mon, 29 Nov 1999 20:04:25 -0800 (PST) (envelope-from matt@csis.gvsu.edu) Received: (qmail 12170 invoked by uid 0); 30 Nov 1999 04:04:22 -0000 Received: from pm628-14.dialip.mich.net (HELO 198.110.189.168) (198.110.189.168) by csis.gvsu.edu with SMTP; 30 Nov 1999 04:04:22 -0000 Received: (qmail 6541 invoked by uid 500); 30 Nov 1999 04:04:36 -0000 From: matt@csis.gvsu.edu Date: Mon, 29 Nov 1999 23:04:36 -0500 To: freebsd-hackers@freebsd.org Subject: Human readable df Message-ID: <19991129230436.A6501@badmofo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-my-OS-is-better-than-your-OS: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure if -hackers is the place for this, but here goes. Here's a patch to add -h flag to df to produce human readable output. This makes it easier to read if the disk is big. Example: [badmofo@/home/matt] df -h Filesystem Size Used Avail Capacity Mounted on /dev/wd0s1a 722M 20M 644M 3% / /dev/wd0s2h 9.9G 4.4G 4.8G 48% /usr procfs 4.0K 4.0K 0B 100% /proc .... Code merged from OpenBSD and added to FreeBSD-STABLE. [badmofo@/usr/src/bin/df] diff -u df df~ diff -u df/df.1 df~/df.1 --- df/df.1 Sun Aug 29 10:12:14 1999 +++ df~/df.1 Mon Nov 29 22:57:01 1999 @@ -40,7 +40,7 @@ .Nd display free disk space .Sh SYNOPSIS .Nm df -.Op Fl ikn +.Op Fl hikn .Op Fl t Ar type .Op Ar file | Ar filesystem ... .Sh DESCRIPTION @@ -59,6 +59,10 @@ .Pp The following options are available: .Bl -tag -width Ds +.It Fl h +"Human-readable" output. Use unit suffixes: Byte, Kilobyte, Megabyte, +Gigabyte, Terabyte, Petabyte, Exabyte in order to reduce the number of +digits to four or less. .It Fl i Include statistics on the number of free inodes. .It Fl k diff -u df/df.c df~/df.c --- df/df.c Sun Aug 29 10:12:15 1999 +++ df~/df.c Mon Nov 29 22:57:01 1999 @@ -59,11 +59,14 @@ #include #include #include +#include #include #include #include #include +typedef enum { NONE = 0, KILO, MEGA, GIGA, TERA, PETA /* , EXA */ } unit_t; + int checkvfsname __P((const char *, char **)); char **makevfslist __P((char *)); long regetmntinfo __P((struct statfs **, long, char **)); @@ -71,9 +74,12 @@ char *getmntpt __P((char *)); void prtstat __P((struct statfs *, int)); int ufs_df __P((char *, int)); +unit_t unit_adjust __P((double *)); +void prthumanval __P((double)); +void prthuman __P((struct statfs *, long)); void usage __P((void)); -int iflag, nflag; +int iflag, nflag, hflag; struct ufs_args mdev; int @@ -88,8 +94,11 @@ char *mntpt, *mntpath, **vfslist; vfslist = NULL; - while ((ch = getopt(argc, argv, "iknt:")) != -1) + while ((ch = getopt(argc, argv, "hiknt:")) != -1) switch (ch) { + case 'h': + hflag = 1; + break; case 'i': iflag = 1; break; @@ -267,20 +276,26 @@ if (maxwidth < 11) maxwidth = 11; if (++timesthrough == 1) { - header = getbsize(&headerlen, &blocksize); - (void)printf("%-*.*s %s Used Avail Capacity", + if(hflag) + header = " Size"; + else + header = getbsize(&headerlen, &blocksize); + (void)printf("%-*.*s %s Used Avail Capacity", maxwidth, maxwidth, "Filesystem", header); if (iflag) (void)printf(" iused ifree %%iused"); - (void)printf(" Mounted on\n"); + (void)printf(" Mounted on\n"); } (void)printf("%-*.*s", maxwidth, maxwidth, sfsp->f_mntfromname); used = sfsp->f_blocks - sfsp->f_bfree; availblks = sfsp->f_bavail + used; - (void)printf(" %*ld %8ld %8ld", headerlen, - fsbtoblk(sfsp->f_blocks, sfsp->f_bsize, blocksize), - fsbtoblk(used, sfsp->f_bsize, blocksize), - fsbtoblk(sfsp->f_bavail, sfsp->f_bsize, blocksize)); + if(hflag) + prthuman(sfsp, used); + else + (void)printf(" %*ld %8ld %8ld", headerlen, + fsbtoblk(sfsp->f_blocks, sfsp->f_bsize, blocksize), + fsbtoblk(used, sfsp->f_bsize, blocksize), + fsbtoblk(sfsp->f_bavail, sfsp->f_bsize, blocksize)); (void)printf(" %5.0f%%", availblks == 0 ? 100.0 : (double)used / (double)availblks * 100.0); if (iflag) { @@ -290,7 +305,67 @@ inodes == 0 ? 100.0 : (double)used / (double)inodes * 100.0); } else (void)printf(" "); - (void)printf(" %s\n", sfsp->f_mntonname); + (void)printf(" %s\n", sfsp->f_mntonname); +} + +/* + * "human-readable" output: use 3 digits max.--put unit suffixes at + * the end. Makes output compact and easy-to-read esp. on huge disks. + */ + +unit_t +unit_adjust(val) + double *val; +{ + double abval; + unit_t unit; + + abval = fabs(*val); + if (abval < 1024) + unit = NONE; + else if (abval < 1048576ULL) { + unit = KILO; + *val /= 1024; + } else if (abval < 1073741824ULL) { + unit = MEGA; + *val /= 1048576; + } else if (abval < 1099511627776ULL) { + unit = GIGA; + *val /= 1073741824ULL; + } else if (abval < 1125899906842624ULL) { + unit = TERA; + *val /= 1099511627776ULL; + } else if (abval < 1152921504606846976ULL) { + unit = PETA; + *val /= 1125899906842624ULL; + } + return (unit); +} + +void +prthumanval(bytes) + double bytes; +{ + unit_t unit; + + unit = unit_adjust(&bytes); + + if (bytes == 0) + (void)printf(" 0B"); + else if (bytes > 10) + (void)printf(" %5.0f%c", bytes, "BKMGTPE"[unit]); + else + (void)printf(" %5.1f%c", bytes, "BKMGTPE"[unit]); +} + +void +prthuman(sfsp, used) + struct statfs *sfsp; + long used; +{ + prthumanval((double)(sfsp->f_blocks) * (double)(sfsp->f_bsize)); + prthumanval((double)(used) * (double)(sfsp->f_bsize)); + prthumanval((double)(sfsp->f_bavail) * (double)(sfsp->f_bsize)); } /* @@ -377,6 +452,6 @@ usage() { (void)fprintf(stderr, - "usage: df [-ikn] [-t type] [file | filesystem ...]\n"); + "usage: df [-hikn] [-t type] [file | filesystem ...]\n"); exit(1); } Only in df~: extern.h Only in df~: vfslist.c -- http://www.csis.gvsu.edu/matt 03 F8 23 C5 43 A2 F7 5A 24 49 F7 B0 3A F9 B1 7F Try to understand everything, but believe nothing To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 21:39:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 3AF0C156D7 for ; Mon, 29 Nov 1999 21:39:53 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 7148A1DA; Mon, 29 Nov 1999 21:39:53 -0800 (PST) Date: Mon, 29 Nov 1999 21:39:53 -0800 From: Chris Piazza To: matt@csis.gvsu.edu Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Human readable df Message-ID: <19991129213953.D16943@norn.ca.eu.org> References: <19991129230436.A6501@badmofo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991129230436.A6501@badmofo>; from matt@csis.gvsu.edu on Mon, Nov 29, 1999 at 11:04:36PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 29, 1999 at 11:04:36PM -0500, matt@csis.gvsu.edu wrote: > Not sure if -hackers is the place for this, but here goes. > > Here's a patch to add -h flag to df to produce human readable > output. This makes it easier to read if the disk is big. > Example: > > [badmofo@/home/matt] df -h > Filesystem Size Used Avail Capacity Mounted on > /dev/wd0s1a 722M 20M 644M 3% / > /dev/wd0s2h 9.9G 4.4G 4.8G 48% /usr > procfs 4.0K 4.0K 0B 100% /proc > .... > > Code merged from OpenBSD and added to FreeBSD-STABLE. [patch snipped] For what it's worth, I'd ported this a few months back (file dated Aug 28), but forgot about it :-). Here's the patch updated for -current, anyway. Index: df.1 =================================================================== RCS file: /home/ncvs/src/bin/df/df.1,v retrieving revision 1.17 diff -u -r1.17 df.1 --- df.1 1999/11/01 04:57:42 1.17 +++ df.1 1999/11/30 05:38:47 @@ -40,7 +40,7 @@ .Nd display free disk space .Sh SYNOPSIS .Nm df -.Op Fl aikn +.Op Fl ahikmn .Op Fl t Ar type .Op Ar file | Ar filesystem ... .Sh DESCRIPTION @@ -62,6 +62,10 @@ .It Fl a Show all mount points, including those that were mounted with the MNT_IGNORE flag. +.It Fl h +"Human-readable" output. Use unit suffixes: Byte, Kilobyte, Megabyte, +Gigabyte, Terabyte, Petabyte, Exabyte in order to reduce the number of +digits to four or less. .It Fl i Include statistics on the number of free inodes. .It Fl k Index: df.c =================================================================== RCS file: /home/ncvs/src/bin/df/df.c,v retrieving revision 1.22 diff -u -r1.22 df.c --- df.c 1999/11/01 04:57:43 1.22 +++ df.c 1999/11/30 05:38:47 @@ -59,21 +59,27 @@ #include #include #include +#include #include #include #include #include +typedef enum { NONE = 0, KILO, MEGA, GIGA, TERA, PETA /* , EXA */ } unit_t; + int checkvfsname __P((const char *, char **)); char **makevfslist __P((char *)); long regetmntinfo __P((struct statfs **, long, char **)); int bread __P((off_t, void *, int)); char *getmntpt __P((char *)); +void prthuman __P((struct statfs *, long)); +void prthumanval __P((double)); void prtstat __P((struct statfs *, int)); int ufs_df __P((char *, int)); +unit_t unit_adjust __P((double *)); void usage __P((void)); -int aflag = 0, iflag, nflag; +int aflag = 0, hflag, iflag, nflag; struct ufs_args mdev; int @@ -88,11 +94,14 @@ char *mntpt, *mntpath, **vfslist; vfslist = NULL; - while ((ch = getopt(argc, argv, "aiknt:")) != -1) + while ((ch = getopt(argc, argv, "ahiknt:")) != -1) switch (ch) { case 'a': aflag = 1; break; + case 'h': + hflag = 1; + break; case 'i': iflag = 1; break; @@ -249,6 +258,68 @@ } /* + * Output in "human-readable" format. Uses 3 digits max and puts + * unit suffixes at the end. Makes output compact and easy to read, + * especially on huge disks. + * + */ + +unit_t +unit_adjust(val) + double *val; +{ + double abval; + unit_t unit; + + abval = fabs(*val); + if (abval < 1024) + unit = NONE; + else if (abval < 1048576ULL) { + unit = KILO; + *val /= 1024; + } else if (abval < 1073741824ULL) { + unit = MEGA; + *val /= 1048576; + } else if (abval < 1099511627776ULL) { + unit = GIGA; + *val /= 1073741824ULL; + } else if (abval < 1125899906842624ULL) { + unit = TERA; + *val /= 1099511627776ULL; + } else if (abval < 1152921504606846976ULL) { + unit = PETA; + *val /= 1125899906842624ULL; + } + return (unit); +} + +void +prthuman(sfsp, used) + struct statfs *sfsp; + long used; +{ + prthumanval((double)(sfsp->f_blocks) * (double)(sfsp->f_bsize)); + prthumanval((double)(used) * (double)(sfsp->f_bsize)); + prthumanval((double)(sfsp->f_bavail) * (double)(sfsp->f_bsize)); +} + +void +prthumanval(bytes) + double bytes; +{ + unit_t unit; + + unit = unit_adjust(&bytes); + + if (bytes == 0) + (void)printf(" 0B"); + else if (bytes > 10) + (void)printf(" %5.0f%c", bytes, "BKMGTPE"[unit]); + else + (void)printf(" %5.1f%c", bytes, "BKMGTPE"[unit]); +} + +/* * Convert statfs returned filesystem size into BLOCKSIZE units. * Attempts to avoid overflow for large filesystems. */ @@ -272,9 +343,16 @@ if (maxwidth < 11) maxwidth = 11; if (++timesthrough == 1) { - header = getbsize(&headerlen, &blocksize); - (void)printf("%-*.*s %s Used Avail Capacity", - maxwidth, maxwidth, "Filesystem", header); + if (hflag) { + header = " Size"; + headerlen = strlen(header); + (void)printf("%-*.*s %s Used Avail Capacity", + maxwidth, maxwidth, "Filesystem", header); + } else { + header = getbsize(&headerlen, &blocksize); + (void)printf("%-*.*s %s Used Avail Capacity", + maxwidth, maxwidth, "Filesystem", header); + } if (iflag) (void)printf(" iused ifree %%iused"); (void)printf(" Mounted on\n"); @@ -282,10 +360,13 @@ (void)printf("%-*.*s", maxwidth, maxwidth, sfsp->f_mntfromname); used = sfsp->f_blocks - sfsp->f_bfree; availblks = sfsp->f_bavail + used; - (void)printf(" %*ld %8ld %8ld", headerlen, - fsbtoblk(sfsp->f_blocks, sfsp->f_bsize, blocksize), - fsbtoblk(used, sfsp->f_bsize, blocksize), - fsbtoblk(sfsp->f_bavail, sfsp->f_bsize, blocksize)); + if (hflag) + prthuman(sfsp, used); + else + (void)printf(" %*ld %8ld %8ld", headerlen, + fsbtoblk(sfsp->f_blocks, sfsp->f_bsize, blocksize), + fsbtoblk(used, sfsp->f_bsize, blocksize), + fsbtoblk(sfsp->f_bavail, sfsp->f_bsize, blocksize)); (void)printf(" %5.0f%%", availblks == 0 ? 100.0 : (double)used / (double)availblks * 100.0); if (iflag) { -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 21:45: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id B1B071575F for ; Mon, 29 Nov 1999 21:45:06 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 4061A153; Mon, 29 Nov 1999 21:45:06 -0800 (PST) Date: Mon, 29 Nov 1999 21:45:06 -0800 From: Chris Piazza To: Chris Piazza Cc: matt@csis.gvsu.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: Human readable df Message-ID: <19991129214506.E16943@norn.ca.eu.org> References: <19991129230436.A6501@badmofo> <19991129213953.D16943@norn.ca.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991129213953.D16943@norn.ca.eu.org>; from cpiazza@jaxon.net on Mon, Nov 29, 1999 at 09:39:53PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 29, 1999 at 09:39:53PM -0800, Chris Piazza wrote: Oops, plus the usage change which I forgot (of course). @@ -382,6 +463,6 @@ usage() { (void)fprintf(stderr, - "usage: df [-aikn] [-t type] [file | filesystem ...]\n"); + "usage: df [-ahikn] [-t type] [file | filesystem ...]\n"); exit(1); } -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 22:37:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 3C8BE15872; Mon, 29 Nov 1999 22:37:11 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 65F581CD737; Mon, 29 Nov 1999 22:37:09 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 29 Nov 1999 22:37:08 -0800 (PST) From: Kris Kennaway To: matt@csis.gvsu.edu Cc: freebsd-hackers@freebsd.org Subject: Re: Human readable df In-Reply-To: <19991129230436.A6501@badmofo> 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, 29 Nov 1999 matt@csis.gvsu.edu wrote: > Not sure if -hackers is the place for this, but here goes. > > Here's a patch to add -h flag to df to produce human readable > output. This makes it easier to read if the disk is big. You should submit this as a PR so it doesn't fall through the cracks (although it looks like Chris might take care of it, he seems to like adding options to commands :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 22:57:22 1999 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 3DCFE14A08 for ; Mon, 29 Nov 1999 22:57:19 -0800 (PST) (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 XAA07452; Mon, 29 Nov 1999 23:57:17 -0700 (MST) (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 XAA99880; Mon, 29 Nov 1999 23:57:48 -0700 (MST) Message-Id: <199911300657.XAA99880@harmony.village.org> To: matt@csis.gvsu.edu Subject: Re: Human readable df Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 29 Nov 1999 23:04:36 EST." <19991129230436.A6501@badmofo> References: <19991129230436.A6501@badmofo> Date: Mon, 29 Nov 1999 23:57:48 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991129230436.A6501@badmofo> matt@csis.gvsu.edu writes: : [badmofo@/home/matt] df -h : Filesystem Size Used Avail Capacity Mounted on : /dev/wd0s1a 722M 20M 644M 3% / : /dev/wd0s2h 9.9G 4.4G 4.8G 48% /usr : procfs 4.0K 4.0K 0B 100% /proc Note, this uses the "traditional computer science SI extention" units. Where M == 1 << 20, G == 1 << 30, etc. Disk drive manufacturers use the real SI units where M == 10 ^ 6, G == 10 ^ 9, etc. There are new Si units for the old traditional CS SI units, but I don't like them :-) It also appears that this patch ignores blocksize, but maybe that's something that I've missed somehow... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 23:27:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5EA54155C6; Mon, 29 Nov 1999 23:27:27 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id XAA21798; Mon, 29 Nov 1999 23:27:26 -0800 (PST) (envelope-from obrien) Date: Mon, 29 Nov 1999 23:27:26 -0800 From: "David O'Brien" To: Kris Kennaway Cc: matt@csis.gvsu.edu, freebsd-hackers@FreeBSD.ORG, mharo@FreeBSD.ORG Subject: Re: Human readable df Message-ID: <19991129232726.A21771@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19991129230436.A6501@badmofo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 3.3-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 29, 1999 at 10:37:08PM -0800, Kris Kennaway wrote: > > Here's a patch to add -h flag to df to produce human readable > > output. This makes it easier to read if the disk is big. > > You should submit this as a PR so it doesn't fall through the cracks > (although it looks like Chris might take care of it, he seems to like > adding options to commands :-) Mike Haro has this ready to commit in -CURRENT for quite some time. I've been pushing him to get it in 4.0-R. Please send any patches etc, to mharo@freebsd.org so he can merge all the good ideas into one commit. -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 23:29:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E916514D07; Mon, 29 Nov 1999 23:29:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id XAA21828; Mon, 29 Nov 1999 23:29:11 -0800 (PST) (envelope-from obrien) Date: Mon, 29 Nov 1999 23:29:11 -0800 From: "David O'Brien" To: Warner Losh Cc: matt@csis.gvsu.edu, freebsd-hackers@FreeBSD.ORG, mharo@FreeBSD.ORG Subject: Re: Human readable df Message-ID: <19991129232911.B21771@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19991129230436.A6501@badmofo> <199911300657.XAA99880@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <199911300657.XAA99880@harmony.village.org> X-Operating-System: FreeBSD 3.3-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 29, 1999 at 11:57:48PM -0700, Warner Losh wrote: > Note, this uses the "traditional computer science SI extention" > units. Where M == 1 << 20, G == 1 << 30, etc. Disk drive > manufacturers use the real SI units where M == 10 ^ 6, G == 10 ^ 9, Some implimentations of ``df -h'' use "-h" for base 2, and "-H" for SI units. I believe Mike Haro's additions supports both. Same for ``du'' of course. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 23:30:22 1999 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 6416814D07 for ; Mon, 29 Nov 1999 23:30:15 -0800 (PST) (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 AAA07567; Tue, 30 Nov 1999 00:30:15 -0700 (MST) (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 AAA00409; Tue, 30 Nov 1999 00:30:46 -0700 (MST) Message-Id: <199911300730.AAA00409@harmony.village.org> Subject: Re: Human readable df To: matt@csis.gvsu.edu, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 29 Nov 1999 23:57:48 MST." <199911300657.XAA99880@harmony.village.org> References: <199911300657.XAA99880@harmony.village.org> <19991129230436.A6501@badmofo> Date: Tue, 30 Nov 1999 00:30:45 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a slightly better patch. It tries harder to fill up the 5 digit field with as many sig figs as possible (always up to 3). It uses better constants for things than the magic numbers of the first patch. I've not tried to patch the man page yet. Also patched where the gross use of "BKMGTP"[unit], the disorder in the prototypes. I also fixed it so that disk larger then 1000Pbytes are displayed in petabytes rather than bytes like the old code. I think this looks a little better than the orignial patch singe it now gives the same resolution of data for each file system. I experimented with setting the throttle from 1000.00 the previous unit to 2000.00 the previous unit to give it a more multi-meter look and to give higher resolution around 1 which would give you a more linear amount of data (taken as the log of the rounding error), but that didn't look as good, so I left it on the cutting room floor. I also experimented with a format that looked like /dev/da0s1e 192.M 167.M 9.22M 95% /usr but that too didn't look good to my eye, even though it was more pedantically correct from a sigfig point of view (since 200M means there is one sig fig, while 200.M means two, at least in the sig fig system I learned in high school). Here's the output Filesystem Size Used Avail Capacity Mounted on /dev/da0s1a 62.0M 31.0M 26.1M 54% / /dev/da0s1e 192M 167M 9.22M 95% /usr /dev/da0s1d 61.4M 11.3M 45.2M 20% /var /dev/da0s1f 288M 247M 18.4M 93% /usr/local /dev/da0s1g 2.17G 1.88G 122M 94% /home procfs 4.00K 4.00K 0B 100% /proc /dev/sd1a 990M 376M 534M 41% /jaz /dev/da2s4c 1.94G 1.72G 68.0M 96% /hawk /dev/da3s4a 3.93G 1.95G 1.67G 54% /u Warner P.S. I thought of doing a -H as well that used real SI units rather than the traditional CS si-ish units, but thought better of it. I also didn't use the new ki, Mi, et al either since that would just make the display look wrong to my eye (I was also unsure of their exact spelling :-). Index: df.c =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/bin/df/df.c,v retrieving revision 1.22 diff -u -r1.22 df.c --- df.c 1999/11/01 04:57:43 1.22 +++ df.c 1999/11/30 07:19:07 @@ -59,21 +59,28 @@ #include #include #include +#include #include #include #include #include -int checkvfsname __P((const char *, char **)); -char **makevfslist __P((char *)); -long regetmntinfo __P((struct statfs **, long, char **)); +typedef enum { NONE = 0, KILO, MEGA, GIGA, TERA, PETA /* , EXA */ } unit_t; +const char *unit_string = "BKMGTP"; + int bread __P((off_t, void *, int)); +int checkvfsname __P((const char *, char **)); char *getmntpt __P((char *)); +char **makevfslist __P((char *)); +void prthuman __P((struct statfs *, long)); +void prthumanval __P((double)); void prtstat __P((struct statfs *, int)); +long regetmntinfo __P((struct statfs **, long, char **)); int ufs_df __P((char *, int)); +unit_t unit_adjust __P((double *)); void usage __P((void)); -int aflag = 0, iflag, nflag; +int aflag = 0, iflag, nflag, hflag; struct ufs_args mdev; int @@ -88,11 +95,14 @@ char *mntpt, *mntpath, **vfslist; vfslist = NULL; - while ((ch = getopt(argc, argv, "aiknt:")) != -1) + while ((ch = getopt(argc, argv, "ahiknt:")) != -1) switch (ch) { case 'a': aflag = 1; break; + case 'h': + hflag = 1; + break; case 'i': iflag = 1; break; @@ -272,20 +282,26 @@ if (maxwidth < 11) maxwidth = 11; if (++timesthrough == 1) { - header = getbsize(&headerlen, &blocksize); - (void)printf("%-*.*s %s Used Avail Capacity", + if(hflag) + header = " Size"; + else + header = getbsize(&headerlen, &blocksize); + (void)printf("%-*.*s %s Used Avail Capacity", maxwidth, maxwidth, "Filesystem", header); if (iflag) (void)printf(" iused ifree %%iused"); - (void)printf(" Mounted on\n"); + (void)printf(" Mounted on\n"); } (void)printf("%-*.*s", maxwidth, maxwidth, sfsp->f_mntfromname); used = sfsp->f_blocks - sfsp->f_bfree; availblks = sfsp->f_bavail + used; - (void)printf(" %*ld %8ld %8ld", headerlen, - fsbtoblk(sfsp->f_blocks, sfsp->f_bsize, blocksize), - fsbtoblk(used, sfsp->f_bsize, blocksize), - fsbtoblk(sfsp->f_bavail, sfsp->f_bsize, blocksize)); + if(hflag) + prthuman(sfsp, used); + else + (void)printf(" %*ld %8ld %8ld", headerlen, + fsbtoblk(sfsp->f_blocks, sfsp->f_bsize, blocksize), + fsbtoblk(used, sfsp->f_bsize, blocksize), + fsbtoblk(sfsp->f_bavail, sfsp->f_bsize, blocksize)); (void)printf(" %5.0f%%", availblks == 0 ? 100.0 : (double)used / (double)availblks * 100.0); if (iflag) { @@ -295,7 +311,74 @@ inodes == 0 ? 100.0 : (double)used / (double)inodes * 100.0); } else (void)printf(" "); - (void)printf(" %s\n", sfsp->f_mntonname); + (void)printf(" %s\n", sfsp->f_mntonname); +} + +/* + * "human-readable" output: use 3 digits max.--put unit suffixes at + * the end. Makes output compact and easy-to-read esp. on huge disks. + */ + +unit_t +unit_adjust(val) + double *val; +{ +#define K(a) ((a) * (1ULL<< 10)) +#define M(a) ((a) * (1ULL<< 20)) +#define G(a) ((a) * (1ULL<< 30)) +#define T(a) ((a) * (1ULL<< 40)) +#define P(a) ((a) * (1ULL<< 50)) + double abval; + unit_t unit; + + abval = fabs(*val); + if (abval < K(1)) + unit = NONE; + else if (abval < K(1000.0)) { + unit = KILO; + *val /= K(1); + } else if (abval < M(1000.0)) { + unit = MEGA; + *val /= M(1); + } else if (abval < G(1000.0)) { + unit = GIGA; + *val /= G(1.0); + } else if (abval < T(1000.0)) { + unit = TERA; + *val /= T(1.0); + } else { + unit = PETA; + *val /= P(1.0); + } + return (unit); +} + +void +prthumanval(bytes) + double bytes; +{ + unit_t unit; + + unit = unit_adjust(&bytes); + + if (bytes == 0) + (void)printf(" 0B"); + else if (bytes > 100) + (void)printf(" %5.0f%c", bytes, unit_string[unit]); + else if (bytes > 10) + (void)printf(" %5.1f%c", bytes, unit_string[unit]); + else + (void)printf(" %5.2f%c", bytes, unit_string[unit]); +} + +void +prthuman(sfsp, used) + struct statfs *sfsp; + long used; +{ + prthumanval((double)(sfsp->f_blocks) * (double)(sfsp->f_bsize)); + prthumanval((double)(used) * (double)(sfsp->f_bsize)); + prthumanval((double)(sfsp->f_bavail) * (double)(sfsp->f_bsize)); } /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 29 23:30:38 1999 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 D944E14D07 for ; Mon, 29 Nov 1999 23:30:34 -0800 (PST) (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 AAA07572; Tue, 30 Nov 1999 00:30:33 -0700 (MST) (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 AAA00426; Tue, 30 Nov 1999 00:31:04 -0700 (MST) Message-Id: <199911300731.AAA00426@harmony.village.org> Subject: Re: Human readable df Cc: matt@csis.gvsu.edu, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 29 Nov 1999 23:57:48 MST." <199911300657.XAA99880@harmony.village.org> References: <199911300657.XAA99880@harmony.village.org> <19991129230436.A6501@badmofo> Date: Tue, 30 Nov 1999 00:31:04 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911300657.XAA99880@harmony.village.org> Warner Losh writes: : It also appears that this patch ignores blocksize, but maybe that's : something that I've missed somehow... Never mind this comment. It was my mistake. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 0:40:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id 875F414C8F; Tue, 30 Nov 1999 00:40:40 -0800 (PST) (envelope-from puga@mauibuilt.com) Received: from mauibuilt.com (puga@puga.mauibuilt.com [205.166.10.2]) by mauibuilt.com (8.9.3/8.9.3) with ESMTP id WAA10401; Mon, 29 Nov 1999 22:46:18 -1000 (HST) (envelope-from puga@mauibuilt.com) Message-ID: <38438D16.2ABC1907@mauibuilt.com> Date: Mon, 29 Nov 1999 22:38:46 -1000 From: Richard Puga X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Subject: Databook Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have some PCMCIA to ISA adapters which use the Data Book DB86082 chipset. I would be happy to donate a card or 2 to anyone who would write a driver for it. Thank you Richard Puga puga@mauibuilt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 1:24:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id AFFE714D28; Tue, 30 Nov 1999 01:23:44 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA78091; Tue, 30 Nov 1999 09:29:54 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 30 Nov 1999 09:29:54 +0000 (GMT) From: Doug Rabson To: Dan Moschuk Cc: Conrad Minshall , "C. Stephen Gunn" , hackers@freebsd.org, rick@snowhite.cis.uoguelph.ca Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) In-Reply-To: <19991129155217.C2999@spirit.jaded.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 29 Nov 1999, Dan Moschuk wrote: > > | >I'm fairly certain that rpc.lockd is included with Darwin from Apple, > | >I've not closely compared it to what we have in -STABLE or -CURRENT > | >to see if it actually works. > | > | It doesn't, sorry... if someone gets a *BSD version of NFS locking operating > | I'd help see it into Darwin. > | > | BTW, is anyone working on NFS Version 4 for BSD? Rick? > > A few of us talked about this on IRC a few weeks ago and it was decided that > when/if we implement NFSv4 it would have to be from scratch. A pretty big > task. I reviewed the NFSv4 specs recently and came to the same conclusion. To do it right will be quite a bit of work and would include a decent kernel side implementation of rpc and gssapi. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 2: 0:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id A05051593D for ; Tue, 30 Nov 1999 02:00:22 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id TAA08042; Tue, 30 Nov 1999 19:59:26 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpd008033; Tue Nov 30 19:59:21 1999 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id TAA17607; Tue, 30 Nov 1999 19:58:56 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id TAA03216; Tue, 30 Nov 1999 19:58:55 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id TAA16931; Tue, 30 Nov 1999 19:58:54 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199911300958.TAA16931@nymph.detir.qld.gov.au> To: Warner Losh Cc: freebsd-hackers@freebsd.org, matt@csis.gvsu.edu, syssgm@detir.qld.gov.au Subject: Re: Human readable df References: <199911300657.XAA99880@harmony.village.org> <19991129230436.A6501@badmofo> <199911300730.AAA00409@harmony.village.org> In-Reply-To: <199911300730.AAA00409@harmony.village.org> from Warner Losh at "Tue, 30 Nov 1999 00:30:45 -0700" Date: Tue, 30 Nov 1999 19:58:54 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 30th November 1999, Warner Losh wrote: > Filesystem Size Used Avail Capacity Mounted on > /dev/da0s1a 62.0M 31.0M 26.1M 54% / > /dev/da0s1e 192M 167M 9.22M 95% /usr > /dev/da0s1d 61.4M 11.3M 45.2M 20% /var > /dev/da0s1f 288M 247M 18.4M 93% /usr/local > /dev/da0s1g 2.17G 1.88G 122M 94% /home > procfs 4.00K 4.00K 0B 100% /proc > /dev/sd1a 990M 376M 534M 41% /jaz > /dev/da2s4c 1.94G 1.72G 68.0M 96% /hawk > /dev/da3s4a 3.93G 1.95G 1.67G 54% /u Add a 'df -h' if you like, but to me this looks like an unreadable jumble of letters and digits. For the same reason, I don't like graphs with dynamic scaling. If anything, I want a 'df -m' option that does this: Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/da0s1a 62 31 26 54% / /dev/da0s1e 192 167 9 95% /usr /dev/da0s1d 61 11 45 20% /var /dev/da0s1f 288 247 18 93% /usr/local /dev/da0s1g 2170 1880 122 94% /home procfs 0 0 0 100% /proc /dev/sd1a 990 376 534 41% /jaz /dev/da2s4c 1940 1720 68 96% /hawk /dev/da3s4a 3930 1950 1670 54% /u When it comes time, I'll want 'df -g' too. Pity 'df -t' is already taken. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 2:32:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id EDB171514C for ; Tue, 30 Nov 1999 02:32:18 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id LAA01715 for freebsd-hackers@FreeBSD.ORG; Tue, 30 Nov 1999 11:32:17 +0100 (CET) (envelope-from olli) Date: Tue, 30 Nov 1999 11:32:17 +0100 (CET) From: Oliver Fromme Message-Id: <199911301032.LAA01715@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Human readable df Organization: Administration TU Clausthal Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen McKay wrote in list.freebsd-hackers: > On Tuesday, 30th November 1999, Warner Losh wrote: > > Filesystem Size Used Avail Capacity Mounted on > > /dev/da0s1a 62.0M 31.0M 26.1M 54% / > > /dev/da0s1e 192M 167M 9.22M 95% /usr > > /dev/da0s1d 61.4M 11.3M 45.2M 20% /var > > /dev/da0s1f 288M 247M 18.4M 93% /usr/local > > /dev/da0s1g 2.17G 1.88G 122M 94% /home > > procfs 4.00K 4.00K 0B 100% /proc > > /dev/sd1a 990M 376M 534M 41% /jaz > > /dev/da2s4c 1.94G 1.72G 68.0M 96% /hawk > > /dev/da3s4a 3.93G 1.95G 1.67G 54% /u > > Add a 'df -h' if you like, but to me this looks like an unreadable jumble > of letters and digits. FWIW, I agree whole-heartedly. I think -k output is much more readable than the above, because you have an immediate "visual" overview of the sizes. What I'd like to have would be an option that inserts thousands separators ("," or whatever your locale settings say) into the default display: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 105,893 5,117 97,600 5% /foo /dev/da0s1e 139,172 261 138,911 1% /bar /dev/da0s1d 17,641,178 15,931,150 1,710,028 91% /bar/baz /dev/da0s1f 262,133 167,310 86,960 66% /mumble /dev/da0s1g 17,641,178 16,462,303 1,178,875 94% /laber /dev/da0s1h 8,782,097 4,605,191 4,176,906 53% /fasel mfs:33 297,663 2 297,661 0% /tmp procfs 4 4 0 100% /proc This would be esay to implement and improves readability a lot, IMO. I'd send-pr a patch, if there's a chance that it will be comitted (I'd suggest "-s" for "separators"). Or does this start to get feeping creaturism...? Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 3:30: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 576C414CFC for ; Tue, 30 Nov 1999 03:30:03 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id GAA11593; Tue, 30 Nov 1999 06:29:59 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id GAA25526; Tue, 30 Nov 1999 06:29:58 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id GAA69411; Tue, 30 Nov 1999 06:29:57 -0500 (EST) Date: Tue, 30 Nov 1999 06:29:57 -0500 (EST) From: Thomas David Rivers Message-Id: <199911301129.GAA69411@lakes.dignus.com> To: imp@village.org, matt@csis.gvsu.edu Subject: Re: Human readable df Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199911300657.XAA99880@harmony.village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991129230436.A6501@badmofo> matt@csis.gvsu.edu writes: : [badmofo@/home/matt] df -h : Filesystem Size Used Avail Capacity Mounted on : /dev/wd0s1a 722M 20M 644M 3% / : /dev/wd0s2h 9.9G 4.4G 4.8G 48% /usr : procfs 4.0K 4.0K 0B 100% /proc This also looks a lot like what the SVR4 dfspace program produced. dfspace was simply an awk script that prettied up the output of df. Not that I'm against the patch - would such prettying up better be done outside of df itself (to follow the UNIX tools-built-on-tools philosophy...) maybe? maybe not?.... Just a thought - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 3:39:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 8D7F514CFC for ; Tue, 30 Nov 1999 03:39:53 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id GAA06248; Tue, 30 Nov 1999 06:39:33 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id GAA25539; Tue, 30 Nov 1999 06:39:32 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id GAA69471; Tue, 30 Nov 1999 06:39:32 -0500 (EST) Date: Tue, 30 Nov 1999 06:39:32 -0500 (EST) From: Thomas David Rivers Message-Id: <199911301139.GAA69471@lakes.dignus.com> To: imp@village.org, syssgm@detir.qld.gov.au Subject: Re: Human readable df Cc: freebsd-hackers@FreeBSD.ORG, matt@csis.gvsu.edu In-Reply-To: <199911300958.TAA16931@nymph.detir.qld.gov.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen McKay write > > On Tuesday, 30th November 1999, Warner Losh wrote: > > > Filesystem Size Used Avail Capacity Mounted on > > /dev/da0s1a 62.0M 31.0M 26.1M 54% / > > /dev/da0s1e 192M 167M 9.22M 95% /usr > > /dev/da0s1d 61.4M 11.3M 45.2M 20% /var > > /dev/da0s1f 288M 247M 18.4M 93% /usr/local > > /dev/da0s1g 2.17G 1.88G 122M 94% /home > > procfs 4.00K 4.00K 0B 100% /proc > > /dev/sd1a 990M 376M 534M 41% /jaz > > /dev/da2s4c 1.94G 1.72G 68.0M 96% /hawk > > /dev/da3s4a 3.93G 1.95G 1.67G 54% /u > > Add a 'df -h' if you like, but to me this looks like an unreadable jumble > of letters and digits. Which adds to my logic of not putting this in df itself, there will always be someone (for many valid reasons) that wants something else. I'd suggest going the dfspace route - then users have an example of something that parses the df output & they can choose for themselves. I just checked on the Solaris box here, /etc/dfspace isn't there... I know it was there on my old ISC 3.2 box; and I recall making it work on FreeBSD. But, it was copyright AT&T, so I simply can't post it. The way it works is to (honoring the block size correctly) skip the first few lines of df (the normal heading) and then grab all the following `table' if you will. With that information in hand, it can format things anyway it needed. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 7:18:54 1999 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 DE67D15909; Tue, 30 Nov 1999 07:18:45 -0800 (PST) (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 IAA08867; Tue, 30 Nov 1999 08:18:44 -0700 (MST) (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 IAA02355; Tue, 30 Nov 1999 08:19:18 -0700 (MST) Message-Id: <199911301519.IAA02355@harmony.village.org> To: Richard Puga Subject: Re: Databook Cc: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 29 Nov 1999 22:38:46 -1000." <38438D16.2ABC1907@mauibuilt.com> References: <38438D16.2ABC1907@mauibuilt.com> Date: Tue, 30 Nov 1999 08:19:18 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38438D16.2ABC1907@mauibuilt.com> Richard Puga writes: : I have some PCMCIA to ISA adapters which use the Data Book DB86082 : chipset. : : I would be happy to donate a card or 2 to anyone who would write a : driver for it. If you can get a databook/user manual for these things, I'd consider it after the newcard stuff stabilizes. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 7:50:39 1999 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 1877015936; Tue, 30 Nov 1999 07:50:36 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 3A6781C5D; Tue, 30 Nov 1999 09:51:40 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 36EE7381B; Tue, 30 Nov 1999 09:51:40 -0500 (EST) Date: Tue, 30 Nov 1999 09:51:40 -0500 (EST) From: Bill Fumerola To: Warner Losh Cc: matt@csis.gvsu.edu, freebsd-hackers@FreeBSD.ORG, mharo@FreeBSD.org Subject: Re: Human readable df In-Reply-To: <199911300730.AAA00409@harmony.village.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 Tue, 30 Nov 1999, Warner Losh wrote: > Filesystem Size Used Avail Capacity Mounted on > /dev/da0s1a 62.0M 31.0M 26.1M 54% / Previously the three size column were right-aligned with the headers, and the percentiage was centered under 'Capacity', I hope we can keep that consistant. Thanks, -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Tue Nov 30 7:55:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 35FE115930 for ; Tue, 30 Nov 1999 07:55:04 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 3.03 #1) id 11spcN-0007ld-00 for freebsd-hackers@FreeBSD.ORG; Tue, 30 Nov 1999 08:55:04 -0700 Message-ID: <3843F357.DF857C60@softweyr.com> Date: Tue, 30 Nov 1999 08:55:03 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Re: Human readable df References: <199911301032.LAA01715@dorifer.heim3.tu-clausthal.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme wrote: > > What I'd like to have would be an option that inserts thousands > separators ("," or whatever your locale settings say) into the > default display: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 105,893 5,117 97,600 5% /foo > /dev/da0s1e 139,172 261 138,911 1% /bar > > I'd send-pr a patch, if there's a chance that it will be > comitted (I'd suggest "-s" for "separators"). Or does this > start to get feeping creaturism...? Don't forget to correctly i18n the separators. Talk about feeping creaturism. -- "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 Tue Nov 30 8:17:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id 175C01594A; Tue, 30 Nov 1999 08:17:29 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id LAA02510; Tue, 30 Nov 1999 11:19:17 -0500 (EST) Date: Tue, 30 Nov 1999 11:19:17 -0500 From: Dan Moschuk To: Doug Rabson Cc: Dan Moschuk , Conrad Minshall , "C. Stephen Gunn" , hackers@FreeBSD.ORG, rick@snowhite.cis.uoguelph.ca Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) Message-ID: <19991130111917.A2308@spirit.jaded.net> References: <19991129155217.C2999@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dfr@nlsystems.com on Tue, Nov 30, 1999 at 09:29:54AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | I reviewed the NFSv4 specs recently and came to the same conclusion. To do | it right will be quite a bit of work and would include a decent kernel | side implementation of rpc and gssapi. Cool! I can take that "I volunteer" ? :-) -- Dan Moschuk (TFreak!dan@freebsd.org) "Cure for global warming: One giant heatsink and dual fans!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 8:43:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 18A9B15950; Tue, 30 Nov 1999 08:43:48 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id LAA17177; Tue, 30 Nov 1999 11:43:35 -0500 (EST) Date: Tue, 30 Nov 1999 11:39:57 -0500 (EST) From: "Matthew N. Dodd" To: Richard Puga Cc: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Databook In-Reply-To: <38438D16.2ABC1907@mauibuilt.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, 29 Nov 1999, Richard Puga wrote: > I have some PCMCIA to ISA adapters which use the Data Book DB86082 > chipset. > > I would be happy to donate a card or 2 to anyone who would write a > driver for it. tcic0: at port 0x380 iomem 0xd0000 irq 5 on isa0 I'm working on it... Once Warner has the newbus PCMCIA code in -CURRENT beaten into shape I'll finish the port of the 'tcic' driver from NetBSD. I'm really looking for any sort of 3com Etherlink III PCMCIA card if you've got any. :) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 9: 4:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 0FCEB14CD2; Tue, 30 Nov 1999 09:04:10 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id MAA17655; Tue, 30 Nov 1999 12:04:03 -0500 (EST) Date: Tue, 30 Nov 1999 12:03:02 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: Richard Puga , freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Databook In-Reply-To: <199911301519.IAA02355@harmony.village.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 Tue, 30 Nov 1999, Warner Losh wrote: > If you can get a databook/user manual for these things, I'd consider > it after the newcard stuff stabilizes. It doesn't seem likely that we'll be able to get the manuals for them. :/ -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 10: 1:59 1999 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 4D468159C3; Tue, 30 Nov 1999 10:01:54 -0800 (PST) (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 LAA09566; Tue, 30 Nov 1999 11:01:52 -0700 (MST) (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 LAA03438; Tue, 30 Nov 1999 11:02:28 -0700 (MST) Message-Id: <199911301802.LAA03438@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: Databook Cc: Richard Puga , freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 30 Nov 1999 12:03:02 EST." References: Date: Tue, 30 Nov 1999 11:02:27 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : On Tue, 30 Nov 1999, Warner Losh wrote: : > If you can get a databook/user manual for these things, I'd consider : > it after the newcard stuff stabilizes. : : It doesn't seem likely that we'll be able to get the manuals for them. :/ That would significantly dampen my enthusiasm for doing a driver :-< Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 10:44:22 1999 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 B5C6B14E9B for ; Tue, 30 Nov 1999 10:44:20 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id MAA60641; Tue, 30 Nov 1999 12:44:00 -0600 (CST) (envelope-from dan) Date: Tue, 30 Nov 1999 12:44:00 -0600 From: Dan Nelson To: Stephen McKay Cc: Warner Losh , freebsd-hackers@FreeBSD.ORG, matt@csis.gvsu.edu Subject: Re: Human readable df Message-ID: <19991130124400.A59749@dan.emsphone.com> References: <199911300657.XAA99880@harmony.village.org> <19991129230436.A6501@badmofo> <199911300730.AAA00409@harmony.village.org> <199911300958.TAA16931@nymph.detir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911300958.TAA16931@nymph.detir.qld.gov.au>; from "Stephen McKay" on Tue Nov 30 19:58:54 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 30), Stephen McKay said: > If anything, I want a 'df -m' option that does this: > > Filesystem 1M-blocks Used Avail Capacity Mounted on > /dev/da0s1a 62 31 26 54% / > /dev/da0s1e 192 167 9 95% /usr > /dev/da0s1d 61 11 45 20% /var > /dev/da0s1f 288 247 18 93% /usr/local > /dev/da0s1g 2170 1880 122 94% /home > procfs 0 0 0 100% /proc > /dev/sd1a 990 376 534 41% /jaz > /dev/da2s4c 1940 1720 68 96% /hawk > /dev/da3s4a 3930 1950 1670 54% /u Just set BLOCKSIZE to your preferred unit. $ BLOCKSIZE=1M df Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/da2s2a 7893 759 6502 10% / /dev/da0s1e 51161 40922 6146 87% /io3 /dev/da1s1e 43997 32111 8366 79% /io4 procfs 0 0 0 100% /proc ( / is 7.8 gig, /io3 is 51 gig ) -- 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 Tue Nov 30 12:17:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 08861155B6 for ; Tue, 30 Nov 1999 12:17:16 -0800 (PST) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id PAA04232; Tue, 30 Nov 1999 15:15:44 -0500 (EST) Reply-To: Randell Jesup To: Robert Watson , freebsd-hackers@freebsd.org Subject: Re: Portable way to compare struct stat's? From: Randell Jesup Date: 30 Nov 1999 15:18:16 -0500 In-Reply-To: Robert Watson's message of "Tue, 16 Nov 1999 10:38:42 -0500 (EST)" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Watson writes: >> On a single system, if st_dev and st_ino are equal, you must be referring >> to the same object. If not, I'd like to hear about it. > >This assumption has always caused lots of pain and suffering for >distributed file system people -- in a distributed file system, the >requirement that you can generate a unique 32 bit number for each file or >directory visible in the FS is a fairly arduous one. Either the number is Quite true, and a real performance problem for some FS designs. Read some SigOS papers for examples (or below). Allowing the application to decide if something is the same or not directly is not a Good Idea. Allowing the OS/FS to determine that for the application is a Good Idea. Witness the SameLock(lock1,lock2) call in some OS's (AmigaOS in particular - SameFileHandle(fh1,fh2) or SameFile(filename1,filename2) are simple derivatives of SameLock()). re: AFS, CODA >each file/directory, only it's 96-bit, which in my book doesn't guarantee >unique mapping onto the 16 bit dev number and 32 bit inode. This means a >hash is required, and collisions are possibly. When a collision occurs on >the hash under Linux, all hell breaks loose :-). Hell breaking loose can be a real pain >Rant rant rant. And a darn good rant at that. Too bad that the "that's the way it's always been done"/"inodes were handed down by God" arguments are so hard to overcome. 1/2 :-) -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 13:11:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1-ext.email.verio.net [129.250.36.41]) by hub.freebsd.org (Postfix) with ESMTP id 70764155EC; Tue, 30 Nov 1999 13:11:27 -0800 (PST) (envelope-from matthew@netsol.net) Received: from dfw-mmp3.email.verio.net ([129.250.38.63]) by dfw-smtpout1.email.verio.net (Netscape Messaging Server 4.05) with ESMTP id FM147300.LX6; Tue, 30 Nov 1999 21:11:27 +0000 Received: from exchange-server.styleclick.net ([207.199.66.93]) by dfw-mmp3.email.verio.net (Netscape Messaging Server 4.05) with ESMTP id FM146200.00Q; Tue, 30 Nov 1999 21:10:50 +0000 Received: from mattl (mattl.styleclick.net [172.20.30.111]) by exchange-server.styleclick.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id X66QQLD8; Tue, 30 Nov 1999 13:12:06 -0800 Message-ID: <000101bf3b77$7e7495e0$6f1e14ac@mattl.styleclick.net> From: "Matt" To: , Subject: stack overflow and security Date: Tue, 30 Nov 1999 13:11:39 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG can any one help to explain how stack over security exploit. does anyone know how to fix it? How it happens? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 13:29: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id AAC7814C98; Tue, 30 Nov 1999 13:28:50 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA74960; Tue, 30 Nov 1999 21:35:16 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 30 Nov 1999 21:35:16 +0000 (GMT) From: Doug Rabson To: Dan Moschuk Cc: Conrad Minshall , "C. Stephen Gunn" , hackers@FreeBSD.ORG, rick@snowhite.cis.uoguelph.ca Subject: Re: Ok, that's it, enough is enough! (rpc.lockd) In-Reply-To: <19991130111917.A2308@spirit.jaded.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 30 Nov 1999, Dan Moschuk wrote: > > | I reviewed the NFSv4 specs recently and came to the same conclusion. To do > | it right will be quite a bit of work and would include a decent kernel > | side implementation of rpc and gssapi. > > Cool! I can take that "I volunteer" ? :-) Not with my current workload :-(. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 13:52:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 1126A14DBB for ; Tue, 30 Nov 1999 13:52:35 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA22391 for FreeBSD-hackers@freebsd.org; Tue, 30 Nov 1999 22:18:22 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA25129 for FreeBSD-hackers@freebsd.org; Tue, 30 Nov 1999 22:18:10 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911302118.WAA25129@yedi.iaf.nl> Subject: Linux ioctl not implemented error To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Tue, 30 Nov 1999 22:18:10 +0100 (CET) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.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 get " LINUX: 'ioctl' fd=0, typ=0x53(S), num=0x13 not implemented " when attempting to configure a IDE cdrom under VMware (really coold BTW!! thanks for the port development). Somebody close to a Linux box have an idea what this ioctl is supposed to do? Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Nov 30 14:20:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 1C96E14EFE for ; Tue, 30 Nov 1999 14:20:00 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac7.wam.umd.edu (root@rac7.wam.umd.edu [128.8.10.147]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA00410; Tue, 30 Nov 1999 17:19:43 -0500 (EST) Received: from rac7.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.3/8.9.3) with SMTP id RAA05578; Tue, 30 Nov 1999 17:19:38 -0500 (EST) Received: from localhost (culverk@localhost) by rac7.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA05574; Tue, 30 Nov 1999 17:19:37 -0500 (EST) X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs Date: Tue, 30 Nov 1999 17:19:37 -0500 (EST) From: Kenneth Wayne Culver To: Wilko Bulte Cc: FreeBSD hackers list Subject: Re: Linux ioctl not implemented error In-Reply-To: <199911302118.WAA25129@yedi.iaf.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 Wait... vmware for linux works under FreeBSD now??? or it just runs freebsd??? ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Tue, 30 Nov 1999, Wilko Bulte wrote: > I get " LINUX: 'ioctl' fd=0, typ=0x53(S), num=0x13 not implemented " > when attempting to configure a IDE cdrom under VMware (really coold BTW!! > thanks for the port development). > > Somebody close to a Linux box have an idea what this ioctl is supposed > to do? > > Wilko > -- > | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - > |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Nov 30 14:22:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id AEF2D14CFF for ; Tue, 30 Nov 1999 14:22:50 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FM100C9Q7H6AG@mta4.rcsntx.swbell.net> for FreeBSD-hackers@FreeBSD.ORG; Tue, 30 Nov 1999 16:22:19 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id QAA09288; Tue, 30 Nov 1999 16:24:08 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Tue, 30 Nov 1999 16:24:07 -0600 From: Chris Costello Subject: Re: Linux ioctl not implemented error In-reply-to: To: Kenneth Wayne Culver Cc: Wilko Bulte , FreeBSD hackers list Reply-To: chris@calldei.com Message-id: <19991130162407.Q2233@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <199911302118.WAA25129@yedi.iaf.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 30, 1999, Kenneth Wayne Culver wrote: > Wait... vmware for linux works under FreeBSD now??? or it just runs > freebsd??? It runs on FreeBSD. -- |Chris Costello |What do computer engineers use for birth control? Their personalities. `----------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 14:30: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 3FB37157B9 for ; Tue, 30 Nov 1999 14:30:01 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac7.wam.umd.edu (root@rac7.wam.umd.edu [128.8.10.147]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA01264; Tue, 30 Nov 1999 17:29:45 -0500 (EST) Received: from rac7.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.3/8.9.3) with SMTP id RAA07090; Tue, 30 Nov 1999 17:29:43 -0500 (EST) Received: from localhost (culverk@localhost) by rac7.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA07086; Tue, 30 Nov 1999 17:29:43 -0500 (EST) X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs Date: Tue, 30 Nov 1999 17:29:43 -0500 (EST) From: Kenneth Wayne Culver To: Chris Costello Cc: Wilko Bulte , FreeBSD hackers list Subject: Re: Linux ioctl not implemented error In-Reply-To: <19991130162407.Q2233@holly.calldei.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 Any wierd things I should do to get it running? ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Tue, 30 Nov 1999, Chris Costello wrote: > On Tue, Nov 30, 1999, Kenneth Wayne Culver wrote: > > Wait... vmware for linux works under FreeBSD now??? or it just runs > > freebsd??? > > It runs on FreeBSD. > > -- > |Chris Costello > |What do computer engineers use for birth control? Their personalities. > `----------------------------------------------------------------------- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 14:54:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from front2.grolier.fr (front2.grolier.fr [194.158.96.52]) by hub.freebsd.org (Postfix) with ESMTP id B026314F27 for ; Tue, 30 Nov 1999 14:54:34 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-169-11.villette.club-internet.fr [195.36.169.11]) by front2.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id XAA02675; Tue, 30 Nov 1999 23:54:28 +0100 (MET) Date: Wed, 1 Dec 1999 01:19:29 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: Wilko Bulte Cc: FreeBSD hackers list Subject: Re: Linux ioctl not implemented error In-Reply-To: <199911302118.WAA25129@yedi.iaf.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 Tue, 30 Nov 1999, Wilko Bulte wrote: > I get " LINUX: 'ioctl' fd=3D0, typ=3D0x53(S), num=3D0x13 not implemented = " > when attempting to configure a IDE cdrom under VMware (really coold BTW!! > thanks for the port development). >=20 > Somebody close to a Linux box have an idea what this ioctl is supposed > to do? CDROMVOLREAD that you want to map to CDIOGETVOL. IMO, you should download a recent Linux stable tree (2.2.13 should fit) which is a single gzipped tar file. Then you will be able to quickly add emulation of all missing IOCTL as needed (you also may have to look into the Linux code).=20 G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 15:45:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E6D5D14F3E for ; Tue, 30 Nov 1999 15:45:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA92050; Tue, 30 Nov 1999 15:45:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kenneth Wayne Culver Cc: FreeBSD hackers list Subject: Re: Linux ioctl not implemented error In-reply-to: Your message of "Tue, 30 Nov 1999 17:19:37 EST." Date: Tue, 30 Nov 1999 15:45:14 -0800 Message-ID: <92046.944005514@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Wait... vmware for linux works under FreeBSD now??? or it just runs > freebsd??? You really need to go search the mailing list archives for the discussion which has just occurred on this topic. Everything from what it does to how to grab the port and apply the appropriate patches to your kernel have been discussed in the freebsd-emulation mailing list and it would be kind of silly to reprise the whole thing all over again in -hackers. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 15:53:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 44ECF159EE for ; Tue, 30 Nov 1999 15:53:10 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA29648; Wed, 1 Dec 1999 00:29:47 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA66873; Wed, 1 Dec 1999 00:29:20 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911302329.AAA66873@yedi.iaf.nl> Subject: Re: Linux ioctl not implemented error In-Reply-To: from Kenneth Wayne Culver at "Nov 30, 1999 5:19:37 pm" To: culverk@wam.umd.edu (Kenneth Wayne Culver) Date: Wed, 1 Dec 1999 00:29:20 +0100 (CET) Cc: FreeBSD-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.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 As Kenneth Wayne Culver wrote ... > Wait... vmware for linux works under FreeBSD now??? or it just runs > freebsd??? Vladimir has created a port of the Linux version that, although highly experimental, works with -current as the host operating system. > On Tue, 30 Nov 1999, Wilko Bulte wrote: > > > I get " LINUX: 'ioctl' fd=0, typ=0x53(S), num=0x13 not implemented " > > when attempting to configure a IDE cdrom under VMware (really coold BTW!! > > thanks for the port development). > > > > Somebody close to a Linux box have an idea what this ioctl is supposed > > to do? -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Nov 30 15:54: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 00794158B7 for ; Tue, 30 Nov 1999 15:53:10 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA29638; Wed, 1 Dec 1999 00:29:31 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA66863; Wed, 1 Dec 1999 00:27:05 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199911302327.AAA66863@yedi.iaf.nl> Subject: Re: Linux ioctl not implemented error In-Reply-To: <19991130162407.Q2233@holly.calldei.com> from Chris Costello at "Nov 30, 1999 4:24: 7 pm" To: chris@calldei.com Date: Wed, 1 Dec 1999 00:27:05 +0100 (CET) Cc: culverk@wam.umd.edu, FreeBSD-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.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 As Chris Costello wrote ... > On Tue, Nov 30, 1999, Kenneth Wayne Culver wrote: > > Wait... vmware for linux works under FreeBSD now??? or it just runs > > freebsd??? > > It runs on FreeBSD. More precisely: on -current. In the meantime I also gave it a shot on my dual-P100 SMP box. This gave me a "VMWare internal monitor error, NullGate on IRQ. gate=0x52" Along with a suggestion to report a bug to the VMware development team ;-) For obvious reasons I'll refrain from the latter Question: how do you people get a guest O/S installed without a CD drive working? Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Nov 30 15:55:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id E9ECD15910 for ; Tue, 30 Nov 1999 15:55:26 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id PAA25579 for hackers@Freebsd.org; Tue, 30 Nov 1999 15:55:55 -0800 (PST) (envelope-from ulf) Date: Tue, 30 Nov 1999 15:55:55 -0800 From: Ulf Zimmermann To: hackers@Freebsd.org Subject: Digi AccelePort-USB 2, 4 or 8 port serial terminal server ? Message-ID: <19991130155555.B91042@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nice serial server, anyone working for serial support on USB ? Have an 8 port and could help getting support for it or testing drivers. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 15:55:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 3AAAD1591B for ; Tue, 30 Nov 1999 15:55:36 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac4.wam.umd.edu (root@rac4.wam.umd.edu [128.8.10.144]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA07449; Tue, 30 Nov 1999 18:55:16 -0500 (EST) Received: from rac4.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id SAA27651; Tue, 30 Nov 1999 18:55:14 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA27644; Tue, 30 Nov 1999 18:55:14 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Tue, 30 Nov 1999 18:55:14 -0500 (EST) From: Kenneth Wayne Culver To: "Jordan K. Hubbard" Cc: FreeBSD hackers list Subject: Re: Linux ioctl not implemented error In-Reply-To: <92046.944005514@zippy.cdrom.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 Oops... not a member of that one... I'll go look then... :-) sorry to have cross posted... ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Tue, 30 Nov 1999, Jordan K. Hubbard wrote: > > Wait... vmware for linux works under FreeBSD now??? or it just runs > > freebsd??? > > You really need to go search the mailing list archives for the > discussion which has just occurred on this topic. Everything from > what it does to how to grab the port and apply the appropriate patches > to your kernel have been discussed in the freebsd-emulation mailing > list and it would be kind of silly to reprise the whole thing all over > again in -hackers. > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 15:56:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 8338A14F28 for ; Tue, 30 Nov 1999 15:56:22 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac4.wam.umd.edu (root@rac4.wam.umd.edu [128.8.10.144]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA21452; Tue, 30 Nov 1999 18:56:11 -0500 (EST) Received: from rac4.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id SAA28155; Tue, 30 Nov 1999 18:56:13 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA28151; Tue, 30 Nov 1999 18:56:12 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Tue, 30 Nov 1999 18:56:12 -0500 (EST) From: Kenneth Wayne Culver To: Wilko Bulte Cc: chris@calldei.com, FreeBSD-hackers@FreeBSD.ORG Subject: Re: Linux ioctl not implemented error In-Reply-To: <199911302327.AAA66863@yedi.iaf.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 Well, I personally was gonna try to get my already installed windows working... :-) ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Wed, 1 Dec 1999, Wilko Bulte wrote: > As Chris Costello wrote ... > > On Tue, Nov 30, 1999, Kenneth Wayne Culver wrote: > > > Wait... vmware for linux works under FreeBSD now??? or it just runs > > > freebsd??? > > > > It runs on FreeBSD. > > More precisely: on -current. > > In the meantime I also gave it a shot on my dual-P100 SMP box. > > This gave me a "VMWare internal monitor error, NullGate on IRQ. gate=0x52" > Along with a suggestion to report a bug to the VMware development team ;-) > > For obvious reasons I'll refrain from the latter > > Question: how do you people get a guest O/S installed without a CD > drive working? > > Wilko > -- > | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - > |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Nov 30 16: 2:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 784BD159D0 for ; Tue, 30 Nov 1999 16:01:43 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03114; Tue, 30 Nov 1999 16:01:37 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912010001.QAA03114@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kenneth Wayne Culver Cc: Wilko Bulte , chris@calldei.com, FreeBSD-hackers@FreeBSD.ORG Subject: Re: Linux ioctl not implemented error In-reply-to: Your message of "Tue, 30 Nov 1999 18:56:12 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Nov 1999 16:01:37 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I personally was gonna try to get my already installed windows > working... :-) That's a really bad idea; the moment you run Windows under VMware it will try to reconfigure itself for the new "hardware", and you'll screw your old configuration. -- \\ 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 Nov 30 16:40: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pebkac.owp.csus.edu (pebkac.owp.csus.edu [130.86.232.245]) by hub.freebsd.org (Postfix) with ESMTP id 2808814D70 for ; Tue, 30 Nov 1999 16:39:56 -0800 (PST) (envelope-from joseph.scott@owp.csus.edu) Received: from owp.csus.edu (mail.owp.csus.edu [130.86.232.247]) by pebkac.owp.csus.edu (8.9.3/8.9.3) with ESMTP id QAA37126; Tue, 30 Nov 1999 16:39:17 -0800 (PST) (envelope-from joseph.scott@owp.csus.edu) Message-ID: <38446E2E.5EEBD4EC@owp.csus.edu> Date: Wed, 01 Dec 1999 00:39:10 +0000 From: Joseph Scott X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kenneth Wayne Culver Cc: Chris Costello , Wilko Bulte , FreeBSD hackers list Subject: Re: Linux ioctl not implemented error References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote: > > Any wierd things I should do to get it running? > > > On Tue, Nov 30, 1999, Kenneth Wayne Culver wrote: > > > Wait... vmware for linux works under FreeBSD now??? or it just runs > > > freebsd??? > > > > It runs on FreeBSD. Here's pointer to the announcement on -hackers and to the web page for the port on Daily Damon News : http://daily.daemonnews.org/view_story.php3?story_id=270 -- Joseph Scott joseph.scott@owp.csus.edu Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 18:29:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id EF40C14CD1 for ; Tue, 30 Nov 1999 18:29:34 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id MAA25270; Wed, 1 Dec 1999 12:28:53 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpd025249; Wed Dec 1 12:28:44 1999 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id MAA10078; Wed, 1 Dec 1999 12:20:25 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id MAA00085; Wed, 1 Dec 1999 12:20:24 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id MAA06369; Wed, 1 Dec 1999 12:20:23 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199912010220.MAA06369@nymph.detir.qld.gov.au> To: Dan Nelson Cc: freebsd-hackers@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Human readable df References: <199911300657.XAA99880@harmony.village.org> <19991129230436.A6501@badmofo> <199911300730.AAA00409@harmony.village.org> <199911300958.TAA16931@nymph.detir.qld.gov.au> <19991130124400.A59749@dan.emsphone.com> In-Reply-To: <19991130124400.A59749@dan.emsphone.com> from Dan Nelson at "Tue, 30 Nov 1999 12:44:00 -0600" Date: Wed, 01 Dec 1999 12:20:23 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 30th November 1999, Dan Nelson wrote: >In the last episode (Nov 30), Stephen McKay said: >> If anything, I want a 'df -m' option that does this: >> >>[snip] >Just set BLOCKSIZE to your preferred unit. > >$ BLOCKSIZE=1M df > >Filesystem 1M-blocks Used Avail Capacity Mounted on >/dev/da2s2a 7893 759 6502 10% / >/dev/da0s1e 51161 40922 6146 87% /io3 >/dev/da1s1e 43997 32111 8366 79% /io4 >procfs 0 0 0 100% /proc I knew this; I just assumed it was well known. In the same way you could use "BLOCKSIZE=1K df" instead of "df -k". But you don't because there's a convenient command option. Similarly, I'd rather use "df -m". I think it's a low impact solution that will scale to "df -g" in the future. Personally, I think "df -h" as proposed is not useful, but I've given up arguing against additional options that other people like. And to Thomas: I've used dfspace before on ISC Unix, but never really liked it. I prefer df to do what I want. Am I greedy? :-) Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 20:44:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id 6012D14E4C for ; Tue, 30 Nov 1999 20:44:32 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id XAA17911 for ; Tue, 30 Nov 1999 23:44:31 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <199912010444.XAA17911@spoon.beta.com> To: hackers@freebsd.org Subject: writing to an mmap()'ed region requires read access? Date: Tue, 30 Nov 1999 23:44:31 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was just playing with mmap() really for the first time, and I noticed something a bit odd. When you mmap() a file for writing, it also appears to require that you give it read permissions, else it dies on a signal 10. Any reason for this? (I'm using 3.3-STABLE (11/30/99) with the following program) -Brian #include #include #include #include #include void main(int argc, char *argv[]) { int f1 = 0, /* File descriptor for source */ f2 = 0; /* File descriptor for target */ off_t size = 0, /* Size of source/mmap'ed regions */ len = 0; /* Size of destination (for test) */ unsigned char *b1 = NULL, /* MMAP of source */ *b2 = NULL; /* MMAP of destination */ if (argc < 3) /* Too few arguments? */ { printf("Usage: mcopy \n"); exit(1); } f1 = open(argv[1],O_RDWR); /* Open src */ f2 = open(argv[2],O_RDWR | O_CREAT);/* Open dst */ if (f1 < 0) /* Error in src? */ { printf("Couldn't open file %s\n",argv[1]); exit(2); } if (f2 < 0) /* Error in dst? */ { printf("Couldn't open file %s\n",argv[2]); exit(3); } printf("Both files opened\n"); size = lseek(f1,0,SEEK_END); /* How big is src? */ printf("Size is %d\n",size); if (lseek(f2,size - 1,SEEK_SET) != (size - 1)) /* Make dst 1 byte shorter */ { printf("Couldn't seek in output file to location %d\n",size - 1); exit(4); } write(f2,"\0",1); /* Write single byte, thereby creating a "hole" in the file. This allows u to mmap the entire region by only writing 1 byte */ len = lseek(f2,0,SEEK_END); /* Make sure our destination is now as big as our source. This is not required */ printf("output file should now by %d bytes long\n",len); /* MMAP the source */ b1 = (unsigned char *)mmap((void *)NULL, (size_t)size, PROT_READ, MAP_SHARED, f1, 0); if (b1 == MAP_FAILED) { perror("mmap input file"); exit(5); } printf("mmap of file 1 complete. Address is %p.\n",b1); /* MMAP the destination. Is read access really required? */ b2 = (unsigned char *)mmap((void *)NULL, (size_t)size, PROT_READ | PROT_WRITE, MAP_SHARED, f2, 0); if (b2 == MAP_FAILED) { perror("mmap input file"); exit(5); } printf("mmap of file 2 complete. Address is %p.\n",b2); printf("Performing bcopy\n"); /* Copy the files */ memcpy(b2,b1,size); printf("Unmapping files\n"); /* Unmap/close them */ munmap(b1,(size_t)size); munmap(b2,(size_t)size); printf("Closing descriptors\n"); close(f1); close(f2); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 21:54:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 9FF7414CE6 for ; Tue, 30 Nov 1999 21:54:11 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id AAA28605; Wed, 1 Dec 1999 00:54:02 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id AAA27151; Wed, 1 Dec 1999 00:53:53 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id AAA89439; Wed, 1 Dec 1999 00:53:52 -0500 (EST) Date: Wed, 1 Dec 1999 00:53:52 -0500 (EST) From: Thomas David Rivers Message-Id: <199912010553.AAA89439@lakes.dignus.com> To: dnelson@emsphone.com, syssgm@detir.qld.gov.au Subject: Re: Human readable df Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199912010220.MAA06369@nymph.detir.qld.gov.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen McKay wrote: > > And to Thomas: I've used dfspace before on ISC Unix, but never really > liked it. I prefer df to do what I want. Am I greedy? :-) Not at all - it just seems to me the question should be asked, that's all. Since not a single person agreed - it seems it has been answered as well :-) - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 30 23:28:50 1999 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 B3EFE14E90 for ; Tue, 30 Nov 1999 23:28:48 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA29886; Tue, 30 Nov 1999 23:28:44 -0800 (PST) (envelope-from dillon) Date: Tue, 30 Nov 1999 23:28:44 -0800 (PST) From: Matthew Dillon Message-Id: <199912010728.XAA29886@apollo.backplane.com> To: "Brian J. McGovern" Cc: hackers@FreeBSD.ORG Subject: Re: writing to an mmap()'ed region requires read access? References: <199912010444.XAA17911@spoon.beta.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I was just playing with mmap() really for the first time, and I noticed :something a bit odd. When you mmap() a file for writing, it also appears :to require that you give it read permissions, else it dies on a signal 10. :Any reason for this? (I'm using 3.3-STABLE (11/30/99) with the following :program) : -Brian I've got a few hundred terrabytes of WOM to sell ya! This is just a byproduct of the MMU implementation. Most MMU's do not support write-only maps because most do not implement separate read and write bits. You get a valid and a write-enable bit instead, or you just get a valid bit and have to use the dirty bit to make the page writable (no write-enable bit at all). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 1 7:35: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from loki.intrepid.net (intrepid.net [204.71.127.3]) by hub.freebsd.org (Postfix) with ESMTP id 5061814CC5 for ; Wed, 1 Dec 1999 07:35:00 -0800 (PST) (envelope-from mark@loki.intrepid.net) Received: (from mark@localhost) by loki.intrepid.net (8.8.5/8.8.5) id KAA14148; Wed, 1 Dec 1999 10:34:39 -0500 Date: Wed, 1 Dec 1999 10:34:39 -0500 From: Mark Conway Wirt To: matthew@netsol.net Cc: freebsd-hackers@freebsd.org Subject: Re: stack overflow and security Message-ID: <19991201103439.D25021@intrepid.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > can any one help to explain how stack over security exploit. does > anyone know how to fix it? How it happens? http://www.cse.ogi.edu/DISC/projects/immunix/StackGuard/usenixsc98_html/paper.html The above USENIX paper talks about them, and two ways of protecting against them. --Mark -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 1 11: 7:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 5E84E15308 for ; Wed, 1 Dec 1999 11:07:33 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id LAA18911; Wed, 1 Dec 1999 11:04:16 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id LAA12764; Wed, 1 Dec 1999 11:04:15 -0800 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA16340; Wed, 1 Dec 99 11:04:09 PST Message-Id: <3845712D.F4D51A70@softweyr.com> Date: Wed, 01 Dec 1999 12:04:13 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Randell Jesup Cc: Robert Watson , freebsd-hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randell Jesup wrote: > > Robert Watson writes: > >> On a single system, if st_dev and st_ino are equal, you must be referring > >> to the same object. If not, I'd like to hear about it. > > > >This assumption has always caused lots of pain and suffering for > >distributed file system people -- in a distributed file system, the > >requirement that you can generate a unique 32 bit number for each file or > >directory visible in the FS is a fairly arduous one. Either the number is > > Too bad that the "that's the way it's always been done"/"inodes > were handed down by God" arguments are so hard to overcome. 1/2 :-) Perhaps we simply need to expand the size of ino_t and carefully convert smaller types to it in the stat call? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 1 11:23: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 29D1E150B1 for ; Wed, 1 Dec 1999 11:23:00 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA23280; Wed, 1 Dec 1999 19:57:25 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA00469; Wed, 1 Dec 1999 19:49:52 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912011849.TAA00469@yedi.iaf.nl> Subject: Re: Linux ioctl not implemented error In-Reply-To: from Gerard Roudier at "Dec 1, 1999 1:19:29 am" To: groudier@club-internet.fr (Gerard Roudier) Date: Wed, 1 Dec 1999 19:49:52 +0100 (CET) Cc: FreeBSD-hackers@freebsd.org X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.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 As Gerard Roudier wrote ... > > > On Tue, 30 Nov 1999, Wilko Bulte wrote: > > > I get " LINUX: 'ioctl' fd=0, typ=0x53(S), num=0x13 not implemented " > > when attempting to configure a IDE cdrom under VMware (really coold BTW!! > > thanks for the port development). > > > > Somebody close to a Linux box have an idea what this ioctl is supposed > > to do? > > CDROMVOLREAD that you want to map to CDIOGETVOL. > > IMO, you should download a recent Linux stable tree (2.2.13 should fit) Sounds like fair idea. > which is a single gzipped tar file. Then you will be able to quickly add Do you have a pointer to such a tgz at hand maybe? TNX, Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Dec 1 11:40:35 1999 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 1D89C14DF6 for ; Wed, 1 Dec 1999 11:40:32 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id MAA22109; Wed, 1 Dec 1999 12:08:42 -0800 (PST) Date: Wed, 1 Dec 1999 12:08:41 -0800 (PST) From: Alfred Perlstein To: Wilko Bulte Cc: Gerard Roudier , FreeBSD-hackers@FreeBSD.ORG Subject: Re: Linux ioctl not implemented error In-Reply-To: <199912011849.TAA00469@yedi.iaf.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 On Wed, 1 Dec 1999, Wilko Bulte wrote: > As Gerard Roudier wrote ... > > > > > > On Tue, 30 Nov 1999, Wilko Bulte wrote: > > > > > I get " LINUX: 'ioctl' fd=0, typ=0x53(S), num=0x13 not implemented " > > > when attempting to configure a IDE cdrom under VMware (really coold BTW!! > > > thanks for the port development). > > > > > > Somebody close to a Linux box have an idea what this ioctl is supposed > > > to do? > > > > CDROMVOLREAD that you want to map to CDIOGETVOL. > > > > IMO, you should download a recent Linux stable tree (2.2.13 should fit) > > Sounds like fair idea. > > > which is a single gzipped tar file. Then you will be able to quickly add > > Do you have a pointer to such a tgz at hand maybe? try this: Index: linux_ioctl.c =================================================================== RCS file: /home/ncvs/src/sys/i386/linux/linux_ioctl.c,v retrieving revision 1.47 diff -u -u -r1.47 linux_ioctl.c --- linux_ioctl.c 1999/11/29 23:03:34 1.47 +++ linux_ioctl.c 1999/12/01 23:46:22 @@ -1273,6 +1273,11 @@ return error; } + case LINUX_CDROMVOLREAD: { + args->arg = CDIOGETVOL; + return (ioctl(p, (struct ioctl_args *)args)); + } + case LINUX_OSS_GETVERSION: { int version; -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 1 12:54:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 280C715187 for ; Wed, 1 Dec 1999 12:54:17 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA28801; Wed, 1 Dec 1999 21:38:03 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA11365; Wed, 1 Dec 1999 21:32:35 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912012032.VAA11365@yedi.iaf.nl> Subject: Re: Linux ioctl not implemented error In-Reply-To: from Alfred Perlstein at "Dec 1, 1999 12: 8:41 pm" To: bright@wintelcom.net (Alfred Perlstein) Date: Wed, 1 Dec 1999 21:32:35 +0100 (CET) Cc: groudier@club-internet.fr, FreeBSD-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.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 As Alfred Perlstein wrote ... > On Wed, 1 Dec 1999, Wilko Bulte wrote: > > > CDROMVOLREAD that you want to map to CDIOGETVOL. > > > > > > IMO, you should download a recent Linux stable tree (2.2.13 should fit) > > > > Sounds like fair idea. > > > > > which is a single gzipped tar file. Then you will be able to quickly add > > > > Do you have a pointer to such a tgz at hand maybe? Never mind, I got one in the meantime. > try this: > > Index: linux_ioctl.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/linux/linux_ioctl.c,v > retrieving revision 1.47 > diff -u -u -r1.47 linux_ioctl.c > --- linux_ioctl.c 1999/11/29 23:03:34 1.47 > +++ linux_ioctl.c 1999/12/01 23:46:22 > @@ -1273,6 +1273,11 @@ > return error; > } > > + case LINUX_CDROMVOLREAD: { > + args->arg = CDIOGETVOL; CDIOCGETVOL I think as CDIOGETVOL does not exist. The console complaints about the ioctl are gone now. Unfortunately VMware still complains. I'll try to findout why. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Dec 1 13:23:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from 24-25-220-29.san.rr.com (24-25-220-29.san.rr.com [24.25.220.29]) by hub.freebsd.org (Postfix) with ESMTP id 0FAD914C26 for ; Wed, 1 Dec 1999 13:23:48 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gateway.gorean.org (gateway.gorean.org [10.0.0.1]) by 24-25-220-29.san.rr.com (8.9.3/8.8.8) with ESMTP id NAA52719 for ; Wed, 1 Dec 1999 13:21:38 -0800 (PST) (envelope-from Doug@gorean.org) Date: Wed, 1 Dec 1999 13:21:08 -0800 (PST) From: Doug Barton X-Sender: doug@24-25-220-29.san.rr.com To: freebsd-hackers@freebsd.org Subject: Weird cvs co problem with src/tools/regression/README 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 Before I forget, major kudos to whomever implemented the whole tools/regression idea. It's something that is long overdue, and very much a cool thing. I am doing some regression testing of my own on some new hardware that we're evaluating at work, and so I checked out a new -Stable src tree on that box from the cvs repo on my machine. When I did the original co (using 'cvs co -r RELENG_3 src') I got an "permission denied" error for src/tools/regression/README. When I consequently did a cvs update for that same machine it told me that the file had been lost, and correctly checked it out. I'm not sure that this is terribly significant, but I have noticed at different times in the past that when doing an initial co with a -r or -D flag that sometimes one or two little files will be left out. The cvs log for the README file seems to have all the proper tags and such, so I'm not sure where the error is coming from, but hopefully this will be of use to someone. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 1 13:49:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from 24-25-220-29.san.rr.com (24-25-220-29.san.rr.com [24.25.220.29]) by hub.freebsd.org (Postfix) with ESMTP id 79A3E14DBC for ; Wed, 1 Dec 1999 13:49:24 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gateway.gorean.org (gateway.gorean.org [10.0.0.1]) by 24-25-220-29.san.rr.com (8.9.3/8.8.8) with ESMTP id NAA52816 for ; Wed, 1 Dec 1999 13:49:10 -0800 (PST) (envelope-from Doug@gorean.org) Date: Wed, 1 Dec 1999 13:48:39 -0800 (PST) From: Doug Barton X-Sender: doug@24-25-220-29.san.rr.com To: freebsd-hackers@freebsd.org Subject: Basic question about threads and SMP 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 You know, a stray thought just occured to me, which hopefully won't sound to silly to people who know about this stuff. :) If I have an SMP box (using -Current specifically) do I want to be compiling things with -lc_r? I'm thinking specifically of mission critical things like apache, but in general will other ports and such take advantage of libc_r if they are compiled with it, or would a program that _can_ take advantage of it already have that built in, say into autoconf or some such? What about other parts of the base system? I'm assuming that the kernel is covered by virtue of the fact that I've enabled the SMP options, yes? I'm trying to learn more about SMP, threads, and such like in general. The recent conversations about those topics on the lists have been very educational. I'm still wading through them, but I appreciate being able to sit on the sidelines and glean bits here and there. Thanks, Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 1 14:10:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from 24-25-220-29.san.rr.com (24-25-220-29.san.rr.com [24.25.220.29]) by hub.freebsd.org (Postfix) with ESMTP id ACCC115067 for ; Wed, 1 Dec 1999 14:10:30 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gateway.gorean.org (gateway.gorean.org [10.0.0.1]) by 24-25-220-29.san.rr.com (8.9.3/8.8.8) with ESMTP id OAA52970; Wed, 1 Dec 1999 14:09:36 -0800 (PST) (envelope-from Doug@gorean.org) Date: Wed, 1 Dec 1999 14:09:06 -0800 (PST) From: Doug Barton X-Sender: doug@24-25-220-29.san.rr.com To: Chris Piazza Cc: matt@csis.gvsu.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: Human readable df In-Reply-To: <19991129213953.D16943@norn.ca.eu.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, 29 Nov 1999, Chris Piazza wrote: > For what it's worth, I'd ported this a few months back (file dated > Aug 28), but forgot about it :-). Here's the patch updated for > -current, anyway. If a "me too" will help get this committed, here 'tis. I can do the math in my head, but I'd rather save the neurons for something more useful. I wouldn't even mind seeing this as the default, but someone would probably gripe... Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 1 14:38:49 1999 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 02A08151AC for ; Wed, 1 Dec 1999 14:38:43 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id RAA16859 for ; Wed, 1 Dec 1999 17:38:15 -0500 (EST) Date: Wed, 1 Dec 1999 16:25:22 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: memory-to-memory copy 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 used to know that memory to memory copy is done by the DMA controller in the I/O bridge (Actually, this knowledge confues me because DMA controller normally does not store the data that pass through it. Now the source and destination are both memory, how can it achieve this at the same time with one memory bus?). I was also told that the function bcopy() is used to setup DMA. Now I look at the bcopy() function in i386/support.s, I only see instructions like "rep movsb". So how is the memory-to-memory copy done in FreeBSD? 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 Wed Dec 1 17:41: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from news.curriculo.com.br (resolver.alphanet.com.br [200.246.167.12]) by hub.freebsd.org (Postfix) with ESMTP id 0B1AA14C87; Wed, 1 Dec 1999 17:40:54 -0800 (PST) (envelope-from news-owner@news.curriculo.com.br) Received: from curriculum.com.br [200.246.167.45] by smtp.alphanet.com.br with ESMTP (SMTPD32-5.05) id AC034400E8; Tue, 30 Nov 1999 23:46:27 -0300 Received: from marcelo [200.246.167.77] by curriculum.com.br (SMTPD32-5.05) id AB643550108; Tue, 30 Nov 1999 23:43:48 -0300 Message-ID: <001d01bf3ba5$dffe70a0$4da7f6c8@alphanet.com.br> Reply-To: "Administracao" From: "Administracao" To: Subject: A Maior Vitrine de Profissionais do Brasil Date: Wed, 1 Dec 1999 00:43:39 -0200 Organization: www.curriculum.com.br MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Você ainda não faz parte da maior vitrine de profissionais do Brasil? Deixe www.curriculum.com.br trabalhar por você! Cadastre-se gratuitamente e faça como inúmeros outros profissionais. Independente se está ou não empregado, coloque-se a disposição do mercado de trabalho. Este é o futuro. Deixe as portas abertas para novas oportunidades e utilize a força da Internet para trabalhar por você. www.curriculum.com.br sempre trabalhando por você hoje e sempre! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 1 17:59:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp5.mindspring.com (smtp5.mindspring.com [207.69.200.82]) by hub.freebsd.org (Postfix) with ESMTP id 4E18A14CF3 for ; Wed, 1 Dec 1999 17:59:44 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2iveb0u.dialup.mindspring.com [165.247.44.30]) by smtp5.mindspring.com (8.8.5/8.8.5) with ESMTP id UAA05832; Wed, 1 Dec 1999 20:59:40 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id UAA00598; Wed, 1 Dec 1999 20:59:38 -0500 (EST) (envelope-from vsilyaev) Date: Wed, 1 Dec 1999 20:59:38 -0500 From: "Vladimir N. Silyaev" To: FreeBSD-hackers@FreeBSD.ORG Cc: groudier@club-internet.fr Subject: Re: Linux ioctl not implemented error Message-ID: <19991201205938.B559@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The console complaints about the ioctl are gone now. Unfortunately VMware >still complains. I'll try to findout why. Try to load new vmware port from: http://www.mindspring.com/~vsilyaev/vmware/files/vmware.tar.gz And reinstall it. I think this may fix the problem. -- Vladimir Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 1 18:55:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from neptune.1webpage.net (neptune.1webpage.net [208.244.164.17]) by hub.freebsd.org (Postfix) with SMTP id DDC61153A1 for ; Wed, 1 Dec 1999 18:55:15 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: (qmail 17617 invoked from network); 2 Dec 1999 02:53:41 -0000 Received: from harlan.fred.net (HELO pcpsj.pfcs.com) (?sVFaSstLoA5qmZZEIDd+QK2Mg1LteWMI?@208.238.64.78) by neptune.1webpage.net with SMTP; 2 Dec 1999 02:53:41 -0000 Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id for ; Wed, 1 Dec 1999 21:53:34 -0500 (EST) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Wed, 1 Dec 1999 18:53:30 -0800 (PST) Received: from localhost.pfcs.com [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Wed, 1 Dec 1999 21:53:30 -0500 (EST) To: hackers@freebsd.org Subject: Bitkeeper license review X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d User-Agent: EMH/1.10.0 SEMI/1.13.3 (Komaiko) FLIM/1.12.7 (=?ISO-8859-1?Q?Y?= =?ISO-8859-1?Q?=1B=2ED=8E=FEzaki?=) XEmacs/21.1 (20 Minutes to Nikko) (i386-unknown-freebsd2.2.8) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Date: Wed, 01 Dec 1999 21:53:29 -0500 Message-ID: <12389.944103209@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anybody here have the time/inclination/ability to review a *draft* of the proposed BitKeeper license to see if it would be acceptable for use by FreeBSD? H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 1 19:32: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from atdot.dotat.org (atdot.dotat.org [150.101.89.3]) by hub.freebsd.org (Postfix) with ESMTP id BF2A814F4C for ; Wed, 1 Dec 1999 19:32:00 -0800 (PST) (envelope-from newton@atdot.dotat.org) Received: (from newton@localhost) by atdot.dotat.org (8.9.3/8.7) id NAA07910; Thu, 2 Dec 1999 13:55:56 +1030 (CST) Date: Thu, 2 Dec 1999 13:55:55 +1030 From: Mark Newton To: PinkSmurf Mushroom Cc: hackers@freebsd.org Subject: Re: syncflood attack Message-ID: <19991202135555.B7796@atdot.dotat.org> References: <19991202032458.34136.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991202032458.34136.qmail@hotmail.com>; from smurfclanz@hotmail.com on Wed, Dec 01, 1999 at 07:24:58PM -0800 X-PGP-Key: http://slash.dotat.org/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 01, 1999 at 07:24:58PM -0800, PinkSmurf Mushroom wrote: > AS I discovered today that my box was brought down by a heavy syncflood > attack, connecting to multiple ports. In addition to that, the attacker even > attack the ftpd with spoofed IPs, opening tons of connection. > In result I've limited the total connection allowed at anyone time but I > couldnt figure out how to stop syncflood. One usually stops it by staying away from the 3l33t hax0rz channels in IRC. - mark -------------------------------------------------------------------- I tried an internal modem, newton@atdot.dotat.org but it hurt when I walked. Mark Newton ----- Voice: +61-4-1620-2223 ------------- Fax: +61-8-82231777 ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 1 20:22: 4 1999 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 3217F14EF1 for ; Wed, 1 Dec 1999 20:22:01 -0800 (PST) (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 XAA52619; Wed, 1 Dec 1999 23:22:14 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199912020422.XAA52619@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Vladimir N. Silyaev" Cc: FreeBSD-hackers@FreeBSD.ORG, groudier@club-internet.fr From: "Louis A. Mamakos" Subject: Re: Linux ioctl not implemented error References: <19991201205938.B559@jupiter.delta.ny.us> In-reply-to: Your message of "Wed, 01 Dec 1999 20:59:38 EST." <19991201205938.B559@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Dec 1999 23:22:13 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >The console complaints about the ioctl are gone now. Unfortunately VMware > >still complains. I'll try to findout why. > > Try to load new vmware port from: > http://www.mindspring.com/~vsilyaev/vmware/files/vmware.tar.gz > > And reinstall it. I think this may fix the problem. > I'm trying the new port now. I seem to have a problem with the vmware emulator program dying due to some panic caused by an uncaught signal whenever I try to save a configuration. Right now, I opted to not save the configuration, and have proceeded on to booting a FreeBSD-3.3 release CDROM, and installing it in a VMware virtual machine. This is great. I dunno if it's just me, but this seems to provoke manical laughter from time to time. Next up: how long to do a 'make world' of the 3.3 system inside the emulator. So, is there a working network interface for the virtual machine? That would be very nifty, indeed. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 1 21:25:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 199DD14A08 for ; Wed, 1 Dec 1999 21:25:42 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA00818; Wed, 1 Dec 1999 21:26:43 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912020526.VAA00818@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: memory-to-memory copy In-reply-to: Your message of "Wed, 01 Dec 1999 16:25:22 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Dec 1999 21:26:43 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I used to know that memory to memory copy is done by the DMA controller in > the I/O bridge (Actually, this knowledge confues me because DMA controller > normally does not store the data that pass through it. Now the source and > destination are both memory, how can it achieve this at the same time with > one memory bus?). Almost nobody does memory-to-memory copy with DMA controllers. You certainly don't do it on the PC. > I was also told that the function bcopy() is used to > setup DMA. No, bcopy is used to move data from one place to another using the CPU. > Now I look at the bcopy() function in i386/support.s, I only > see instructions like "rep movsb". So how is the memory-to-memory copy > done in FreeBSD? With bcopy(). -- \\ 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 Wed Dec 1 21:57:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B529114C45 for ; Wed, 1 Dec 1999 21:57:23 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id VAA00767; Wed, 1 Dec 1999 21:58:09 -0800 Date: Wed, 1 Dec 1999 21:58:09 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Harlan Stenn Cc: hackers@FreeBSD.ORG Subject: Re: Bitkeeper license review In-Reply-To: <12389.944103209@brown.pfcs.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 Since Larry's a neighbor and buddy of mine, I can look at it, but not until next week (poke me if to do so if it hasn't been done already). I already offered to him to do the port for *BSD, but he's a new dad and busy and didn't really get back to me... On Wed, 1 Dec 1999, Harlan Stenn wrote: > Anybody here have the time/inclination/ability to review a *draft* of the > proposed BitKeeper license to see if it would be acceptable for use by > FreeBSD? > > H > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 1 23:23: 1 1999 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 9171714C81; Wed, 1 Dec 1999 23:22:29 -0800 (PST) (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 JAA02892; Thu, 2 Dec 1999 09:19:13 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199912020719.JAA02892@oskar.dev.nanoteq.co.za> Subject: Re: Linux ioctl not implemented error In-Reply-To: from Alfred Perlstein at "Dec 1, 99 12:08:41 pm" To: bright@wintelcom.net (Alfred Perlstein) Date: Thu, 2 Dec 1999 09:19:13 +0200 (SAT) Cc: wilko@yedi.iaf.nl, groudier@club-internet.fr, FreeBSD-hackers@FreeBSD.ORG, marcel@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 ... > > > > to do? > > > > > > CDROMVOLREAD that you want to map to CDIOGETVOL. That should read CDIOCGETVOL :) > try this: > > Index: linux_ioctl.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/linux/linux_ioctl.c,v > retrieving revision 1.47 > diff -u -u -r1.47 linux_ioctl.c > --- linux_ioctl.c 1999/11/29 23:03:34 1.47 > +++ linux_ioctl.c 1999/12/01 23:46:22 > @@ -1273,6 +1273,11 @@ > return error; > } > > + case LINUX_CDROMVOLREAD: { > + args->arg = CDIOGETVOL; > + return (ioctl(p, (struct ioctl_args *)args)); > + } > + > case LINUX_OSS_GETVERSION: { > int version; > > I've made a change that removed the complaint from vmware before Vladimar fixed it in the kernel module. It is the implementation of LINUX_CDROMVOLREAD to fit in with CDIOCGETVOL which has two different structures. Marcel please review this :) Index: linux_ioctl.c =================================================================== RCS file: /home/freebsd-cvs/src/sys/i386/linux/linux_ioctl.c,v retrieving revision 1.47 diff -c -r1.47 linux_ioctl.c *** linux_ioctl.c 1999/11/29 23:03:34 1.47 --- linux_ioctl.c 1999/12/02 07:15:29 *************** *** 473,478 **** --- 473,486 ---- u_char cdte_datamode; }; + struct linux_cdrom_volctrl + { + u_char channel0; + u_char channel1; + u_char channel2; + u_char channel3; + }; + struct linux_cdrom_subchnl { u_char cdsc_format; *************** *** 1232,1237 **** --- 1240,1261 ---- bsd_to_linux_msf_lba(irtse.address_format, &irtse.entry.addr, <e.cdte_addr); copyout((caddr_t)<e, (caddr_t)args->arg, sizeof(lte)); + } + return error; + } + + case LINUX_CDROMVOLREAD: { + struct linux_cdrom_volctrl lvol, *lvolp = + (struct linux_cdrom_volctrl *)args->arg; + struct ioc_vol bsd_vol; + error = fo_ioctl(fp, CDIOCGETVOL, (caddr_t)&bsd_vol, p); + if (!error) { + lvol = *lvolp; + lvol.channel0 = bsd_vol.vol[0]; + lvol.channel1 = bsd_vol.vol[1]; + lvol.channel2 = bsd_vol.vol[2]; + lvol.channel3 = bsd_vol.vol[3]; + copyout((caddr_t)&lvol, (caddr_t)args->arg, sizeof(lvol)); } return error; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 0:18: 4 1999 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 5F7F214DF2; Thu, 2 Dec 1999 00:17:58 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id AAA11247; Thu, 2 Dec 1999 00:45:57 -0800 (PST) Date: Thu, 2 Dec 1999 00:45:57 -0800 (PST) From: Alfred Perlstein To: Reinier Bezuidenhout Cc: wilko@yedi.iaf.nl, groudier@club-internet.fr, FreeBSD-hackers@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: Linux ioctl not implemented error In-Reply-To: <199912020719.JAA02892@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 Thu, 2 Dec 1999, Reinier Bezuidenhout wrote: > > @@ -1273,6 +1273,11 @@ > > return error; > > } > > > > + case LINUX_CDROMVOLREAD: { > > + args->arg = CDIOGETVOL; > > + return (ioctl(p, (struct ioctl_args *)args)); > > + } > > + > > case LINUX_OSS_GETVERSION: { > > int version; > > > > > > I've made a change that removed the complaint from vmware before Vladimar > fixed it in the kernel module. It is the implementation of LINUX_CDROMVOLREAD > to fit in with CDIOCGETVOL which has two different structures. > > Marcel please review this :) > > > Index: linux_ioctl.c > =================================================================== > RCS file: /home/freebsd-cvs/src/sys/i386/linux/linux_ioctl.c,v > retrieving revision 1.47 > diff -c -r1.47 linux_ioctl.c > *** linux_ioctl.c 1999/11/29 23:03:34 1.47 > --- linux_ioctl.c 1999/12/02 07:15:29 > *************** > *** 473,478 **** > --- 473,486 ---- > u_char cdte_datamode; > }; > > + struct linux_cdrom_volctrl > + { > + u_char channel0; > + u_char channel1; > + u_char channel2; > + u_char channel3; > + }; > + > struct linux_cdrom_subchnl > { > u_char cdsc_format; > *************** > *** 1232,1237 **** > --- 1240,1261 ---- > bsd_to_linux_msf_lba(irtse.address_format, > &irtse.entry.addr, <e.cdte_addr); > copyout((caddr_t)<e, (caddr_t)args->arg, sizeof(lte)); > + } > + return error; > + } > + > + case LINUX_CDROMVOLREAD: { > + struct linux_cdrom_volctrl lvol, *lvolp = > + (struct linux_cdrom_volctrl *)args->arg; > + struct ioc_vol bsd_vol; > + error = fo_ioctl(fp, CDIOCGETVOL, (caddr_t)&bsd_vol, p); > + if (!error) { > + lvol = *lvolp; > + lvol.channel0 = bsd_vol.vol[0]; > + lvol.channel1 = bsd_vol.vol[1]; > + lvol.channel2 = bsd_vol.vol[2]; > + lvol.channel3 = bsd_vol.vol[3]; > + copyout((caddr_t)&lvol, (caddr_t)args->arg, sizeof(lvol)); > } > return error; > } > FYI the kernel structures are completely identical, you don't really gain anything by doing this convertion. Should this be put in for clarity? I'm not sure. Marcel? -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 1: 0:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (law-f300.hotmail.com [209.185.130.89]) by hub.freebsd.org (Postfix) with SMTP id 3EBAB14C1C for ; Thu, 2 Dec 1999 01:00:41 -0800 (PST) (envelope-from manny8383@hotmail.com) Received: (qmail 78854 invoked by uid 0); 2 Dec 1999 09:00:16 -0000 Message-ID: <19991202090016.78853.qmail@hotmail.com> Received: from 129.2.9.131 by www.hotmail.com with HTTP; Thu, 02 Dec 1999 01:00:16 PST X-Originating-IP: [129.2.9.131] From: "Manny Obrey" To: freebsd-hackers@freebsd.org Subject: error Date: Thu, 02 Dec 1999 01:00:16 PST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, This may be a simple error on my part but I've narrowed my prob to the snippet below. When trying to compile: #include #include int main () { return 0;} I get error messages which state parse errors in /usr/include/sys/socket.h my compiler =gcc 2.7 ( also tried gcc 2.95.1 ) my os = FreeBSD 3.3-RELEASE, enough RAM , processor speed, etc socket.h = $FreeBSD: src/sys/sys/socket.h,v 1.27.2.1 1999/08/29 16:32:44 peter Exp $ Any suggestions would be appreciated. - Manny Long error outout follows: In file included from ./main.c:1: /usr/include/sys/socket.h:139: parse error before `u_char' /usr/include/sys/socket.h:139: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:140: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:142: parse error before `}' /usr/include/sys/socket.h:150: parse error before `u_short' /usr/include/sys/socket.h:150: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:151: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:266: parse error before `caddr_t' /usr/include/sys/socket.h:266: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:267: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:269: parse error before `msg_iovlen' /usr/include/sys/socket.h:269: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:270: parse error before `msg_control' /usr/include/sys/socket.h:270: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:271: parse error before `msg_controllen' /usr/include/sys/socket.h:271: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:273: parse error before `}' /usr/include/sys/socket.h:293: parse error before `u_int' /usr/include/sys/socket.h:293: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:297: parse error before `}' /usr/include/sys/socket.h:314: parse error before `pid_t' /usr/include/sys/socket.h:314: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:315: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:316: parse error before `cmcred_euid' /usr/include/sys/socket.h:316: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:317: parse error before `cmcred_gid' /usr/include/sys/socket.h:317: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:319: parse error before `cmcred_groups' /usr/include/sys/socket.h:319: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:320: parse error before `}' /usr/include/sys/socket.h:343: parse error before `u_short' /usr/include/sys/socket.h:343: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:345: parse error before `}' /usr/include/sys/socket.h:351: parse error before `caddr_t' /usr/include/sys/socket.h:351: warning: no semicolon at end of struct or union /usr/include/sys/socket.h:355: parse error before `msg_accrights' /usr/include/sys/socket.h:355: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:357: parse error before `}' In file included from ./main.c:1: /usr/include/sys/socket.h:388: parse error before `recv' /usr/include/sys/socket.h:388: parse error before `size_t' /usr/include/sys/socket.h:388: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:389: parse error before `recvfrom' /usr/include/sys/socket.h:389: parse error before `size_t' /usr/include/sys/socket.h:389: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:390: parse error before `recvmsg' /usr/include/sys/socket.h:390: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:391: parse error before `send' /usr/include/sys/socket.h:391: parse error before `size_t' /usr/include/sys/socket.h:391: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:392: parse error before `sendto' /usr/include/sys/socket.h:393: parse error before `size_t' /usr/include/sys/socket.h:393: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:394: parse error before `sendmsg' /usr/include/sys/socket.h:394: warning: data definition has no type or storage c lass /usr/include/sys/socket.h:395: parse error before `off_t' ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 1: 2:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 98B5514C1C for ; Thu, 2 Dec 1999 01:02:49 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11tS7l-0000ns-00; Thu, 2 Dec 1999 09:02:02 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id KAA33965; Thu, 2 Dec 1999 10:02:02 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <3846358A.B040411@scc.nl> Date: Thu, 02 Dec 1999 10:02:02 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Reinier Bezuidenhout Cc: Alfred Perlstein , wilko@yedi.iaf.nl, groudier@club-internet.fr, FreeBSD-hackers@FreeBSD.ORG Subject: Re: Linux ioctl not implemented error References: <199912020719.JAA02892@oskar.dev.nanoteq.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Reinier Bezuidenhout wrote: > I've made a change that removed the complaint from vmware before Vladimar > fixed it in the kernel module. It is the implementation of LINUX_CDROMVOLREAD > to fit in with CDIOCGETVOL which has two different structures. > > Marcel please review this :) Please hold your horses. I have a completely rewritten linux_ioctl.c waiting to be committed. I'm already working on the ioctl stuff with Vladimir as to synchronize the change. As soon as Vladimir has updated his port to use the new interface everything is committed and announced. From that moment on I'll happily accept any patches and diffs! Please, send patches that specificly apply to the VMware port to Vladimir and any patches that apply to the Linuxulator to me. That way we have this port up and running in notime. I unfortunately don't have time to read the mailinglists very closely, so I may have missed a couple of patches already... Thanks, -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@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 Dec 2 1: 9:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 2FBD314C1C for ; Thu, 2 Dec 1999 01:09:45 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11tSCz-0000tf-00; Thu, 2 Dec 1999 09:07:25 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id KAA34002; Thu, 2 Dec 1999 10:07:24 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <384636CC.A184B6D0@scc.nl> Date: Thu, 02 Dec 1999 10:07:24 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Reinier Bezuidenhout , wilko@yedi.iaf.nl, groudier@club-internet.fr, FreeBSD-hackers@FreeBSD.ORG Subject: Re: Linux ioctl not implemented error References: 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: > > > + if (!error) { > > + lvol = *lvolp; > > + lvol.channel0 = bsd_vol.vol[0]; > > + lvol.channel1 = bsd_vol.vol[1]; > > + lvol.channel2 = bsd_vol.vol[2]; > > + lvol.channel3 = bsd_vol.vol[3]; > > FYI the kernel structures are completely identical, you don't really > gain anything by doing this convertion. Should this be put in for > clarity? I'm not sure. No. When it's there, you automaticly assume it's there for a reason. Since the structures are identical, there's no reason for the code to be there. Very confusing :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@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 Dec 2 1:10: 8 1999 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 7AF1B150FE; Thu, 2 Dec 1999 01:09:49 -0800 (PST) (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 LAA05726; Thu, 2 Dec 1999 11:04:37 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199912020904.LAA05726@oskar.dev.nanoteq.co.za> Subject: Re: Linux ioctl not implemented error In-Reply-To: from Alfred Perlstein at "Dec 2, 99 00:45:57 am" To: bright@wintelcom.net (Alfred Perlstein) Date: Thu, 2 Dec 1999 11:04:37 +0200 (SAT) Cc: wilko@yedi.iaf.nl, groudier@club-internet.fr, FreeBSD-hackers@FreeBSD.ORG, marcel@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 > > + { > > + u_char channel0; > > + u_char channel1; > > + u_char channel2; > > + u_char channel3; > > + }; > > + > > struct linux_cdrom_subchnl > > { > > u_char cdsc_format; > > *************** > > *** 1232,1237 **** > > --- 1240,1261 ---- > > FYI the kernel structures are completely identical, you don't really > gain anything by doing this convertion. Should this be put in for > clarity? I'm not sure. > Ok ... I guess it should not be a problem the FreeBSD structure is struct ioc_vol { u_char vol[4]; /* one for each channel */ }; which I guess should look the same in memory than the linux one ... The confersion is then not necessary ... ?? Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 1:10:54 1999 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 433DD15003 for ; Thu, 2 Dec 1999 01:10:44 -0800 (PST) (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 LAA05790; Thu, 2 Dec 1999 11:06:19 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199912020906.LAA05790@oskar.dev.nanoteq.co.za> Subject: Re: Linux ioctl not implemented error In-Reply-To: <3846358A.B040411@scc.nl> from Marcel Moolenaar at "Dec 2, 99 10:02:02 am" To: marcel@scc.nl (Marcel Moolenaar) Date: Thu, 2 Dec 1999 11:06:19 +0200 (SAT) Cc: bright@wintelcom.net, wilko@yedi.iaf.nl, groudier@club-internet.fr, FreeBSD-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 ... > > to fit in with CDIOCGETVOL which has two different structures. > > > > Marcel please review this :) > > Please hold your horses. I have a completely rewritten linux_ioctl.c > waiting to be committed. I'm already working on the ioctl stuff with > Vladimir as to synchronize the change. As soon as Vladimir has updated > his port to use the new interface everything is committed and announced. > From that moment on I'll happily accept any patches and diffs! > > Please, send patches that specificly apply to the VMware port to > Vladimir and any patches that apply to the Linuxulator to me. That way > we have this port up and running in notime. I unfortunately don't have > time to read the mailinglists very closely, so I may have missed a > couple of patches already... > Ok ... I'm holding my horses ... my previous e-mail was just before I received this one ... please ignore it then ... Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 1:12:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 81AD014C1C for ; Thu, 2 Dec 1999 01:12:42 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 1F389163; Thu, 2 Dec 1999 01:12:25 -0800 (PST) Date: Thu, 2 Dec 1999 01:12:25 -0800 From: Chris Piazza To: Manny Obrey Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: error Message-ID: <19991202011224.B7287@norn.ca.eu.org> References: <19991202090016.78853.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991202090016.78853.qmail@hotmail.com>; from manny8383@hotmail.com on Thu, Dec 02, 1999 at 01:00:16AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 02, 1999 at 01:00:16AM -0800, Manny Obrey wrote: > Hello, > This may be a simple error on my part but I've narrowed my prob to > the snippet below. > > When trying to compile: > > #include > #include > > int main () { return 0;} > > I get error messages which state parse errors in > /usr/include/sys/socket.h > > Any suggestions would be appreciated. man socket: SYNOPSIS #include #include enough said. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 1:16:59 1999 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 041F8151AA for ; Thu, 2 Dec 1999 01:16:45 -0800 (PST) (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 LAA05956; Thu, 2 Dec 1999 11:12:43 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199912020912.LAA05956@oskar.dev.nanoteq.co.za> Subject: Re: Linux ioctl not implemented error In-Reply-To: <384636CC.A184B6D0@scc.nl> from Marcel Moolenaar at "Dec 2, 99 10:07:24 am" To: marcel@scc.nl (Marcel Moolenaar) Date: Thu, 2 Dec 1999 11:12:42 +0200 (SAT) Cc: bright@wintelcom.net, wilko@yedi.iaf.nl, groudier@club-internet.fr, FreeBSD-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 > Alfred Perlstein wrote: > > > > > + if (!error) { > > > + lvol = *lvolp; > > > + lvol.channel0 = bsd_vol.vol[0]; > > > + lvol.channel1 = bsd_vol.vol[1]; > > > + lvol.channel2 = bsd_vol.vol[2]; > > > + lvol.channel3 = bsd_vol.vol[3]; > > > > FYI the kernel structures are completely identical, you don't really > > gain anything by doing this convertion. Should this be put in for > > clarity? I'm not sure. > > No. When it's there, you automaticly assume it's there for a reason. > Since the structures are identical, there's no reason for the code to be > there. Very confusing :-) I stand corrected then :) thanx Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 1:25:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 03EFB14D63; Thu, 2 Dec 1999 01:25:38 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id BAA47348; Thu, 2 Dec 1999 01:24:08 -0800 (PST) Date: Thu, 2 Dec 1999 01:24:07 -0800 (PST) From: Julian Elischer To: Alfred Perlstein Cc: Reinier Bezuidenhout , wilko@yedi.iaf.nl, groudier@club-internet.fr, FreeBSD-hackers@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: Linux ioctl not implemented error 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 The structures are identical because they are what the SCSI spec specifies that's what they look like.. On Thu, 2 Dec 1999, Alfred Perlstein wrote: > On Thu, 2 Dec 1999, Reinier Bezuidenhout wrote: > > > > @@ -1273,6 +1273,11 @@ > > > return error; > > > } > > > > > > + case LINUX_CDROMVOLREAD: { > > > + args->arg = CDIOGETVOL; > > > + return (ioctl(p, (struct ioctl_args *)args)); > > > + } > > > + > > > case LINUX_OSS_GETVERSION: { > > > int version; > > > > > > > > > > I've made a change that removed the complaint from vmware before Vladimar > > fixed it in the kernel module. It is the implementation of LINUX_CDROMVOLREAD > > to fit in with CDIOCGETVOL which has two different structures. > > > > Marcel please review this :) > > > > > > Index: linux_ioctl.c > > =================================================================== > > RCS file: /home/freebsd-cvs/src/sys/i386/linux/linux_ioctl.c,v > > retrieving revision 1.47 > > diff -c -r1.47 linux_ioctl.c > > *** linux_ioctl.c 1999/11/29 23:03:34 1.47 > > --- linux_ioctl.c 1999/12/02 07:15:29 > > *************** > > *** 473,478 **** > > --- 473,486 ---- > > u_char cdte_datamode; > > }; > > > > + struct linux_cdrom_volctrl > > + { > > + u_char channel0; > > + u_char channel1; > > + u_char channel2; > > + u_char channel3; > > + }; > > + > > struct linux_cdrom_subchnl > > { > > u_char cdsc_format; > > *************** > > *** 1232,1237 **** > > --- 1240,1261 ---- > > bsd_to_linux_msf_lba(irtse.address_format, > > &irtse.entry.addr, <e.cdte_addr); > > copyout((caddr_t)<e, (caddr_t)args->arg, sizeof(lte)); > > + } > > + return error; > > + } > > + > > + case LINUX_CDROMVOLREAD: { > > + struct linux_cdrom_volctrl lvol, *lvolp = > > + (struct linux_cdrom_volctrl *)args->arg; > > + struct ioc_vol bsd_vol; > > + error = fo_ioctl(fp, CDIOCGETVOL, (caddr_t)&bsd_vol, p); > > + if (!error) { > > + lvol = *lvolp; > > + lvol.channel0 = bsd_vol.vol[0]; > > + lvol.channel1 = bsd_vol.vol[1]; > > + lvol.channel2 = bsd_vol.vol[2]; > > + lvol.channel3 = bsd_vol.vol[3]; > > + copyout((caddr_t)&lvol, (caddr_t)args->arg, sizeof(lvol)); > > } > > return error; > > } > > > > FYI the kernel structures are completely identical, you don't really > gain anything by doing this convertion. Should this be put in for > clarity? I'm not sure. > > Marcel? > > -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] > Wintelcom systems administrator and programmer > - http://www.wintelcom.net/ [bright@wintelcom.net] > > > > > 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 Dec 2 3:44: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id DD97414F44 for ; Thu, 2 Dec 1999 03:44:00 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id GAA08232; Thu, 2 Dec 1999 06:43:52 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id GAA30025; Thu, 2 Dec 1999 06:43:51 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id GAA58619; Thu, 2 Dec 1999 06:43:50 -0500 (EST) Date: Thu, 2 Dec 1999 06:43:50 -0500 (EST) From: Thomas David Rivers Message-Id: <199912021143.GAA58619@lakes.dignus.com> To: freebsd-hackers@FreeBSD.ORG, manny8383@hotmail.com Subject: Re: error In-Reply-To: <19991202090016.78853.qmail@hotmail.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Include before - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 5: 0:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id B25B514CC2; Thu, 2 Dec 1999 05:00:15 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id NAA19161; Thu, 2 Dec 1999 13:57:57 +0100 (CET) (envelope-from asmodai) Date: Thu, 2 Dec 1999 13:57:57 +0100 From: Jeroen Ruigrok van der Werven To: Matthew Jacob Cc: Harlan Stenn , hackers@FreeBSD.ORG, eivind@FreeBSD.ORG Subject: Re: Bitkeeper license review Message-ID: <19991202135757.D18855@lucifer.bart.nl> References: <12389.944103209@brown.pfcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mjacob@feral.com on Wed, Dec 01, 1999 at 09:58:09PM -0800 Organisation: bART Internet Services B.V. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Wed, 1 Dec 1999, Harlan Stenn wrote: -On [19991202 07:00], Matthew Jacob (mjacob@feral.com) wrote: >> Anybody here have the time/inclination/ability to review a *draft* of the >> proposed BitKeeper license to see if it would be acceptable for use by >> FreeBSD? >Since Larry's a neighbor and buddy of mine, I can look at it, but not >until next week (poke me if to do so if it hasn't been done already). I >already offered to him to do the port for *BSD, but he's a new dad and >busy and didn't really get back to me... Sorry to say, but BitKeeper is severely braindead. They chose to built on top of SCCS, which in itself is nearly useless. Also he has some weird ideas about versioning which I certainly don't agree on. We use CVS at this moment, stepping towards BitKeeper from CVS is a step backwards. Eivind and me are trying to get a new version control system of the ground which will kick arse on several accounts. Unfortunately work draws us in. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / Tel: +31 - (0) 10 - 240 39 70 VIA NET.WORKS Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 6:37:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 8A18E14BE9 for ; Thu, 2 Dec 1999 06:37:49 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id PAA15396; Thu, 2 Dec 1999 15:37:42 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA82701; Thu, 2 Dec 1999 15:37:42 +0100 (MET) Date: Thu, 2 Dec 1999 15:37:42 +0100 From: Eivind Eklund To: Jeroen Ruigrok van der Werven Cc: Matthew Jacob , Harlan Stenn , hackers@FreeBSD.ORG Subject: Re: Bitkeeper license review Message-ID: <19991202153742.L76366@bitbox.follo.net> References: <12389.944103209@brown.pfcs.com> <19991202135757.D18855@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991202135757.D18855@lucifer.bart.nl>; from asmodai@bart.nl on Thu, Dec 02, 1999 at 01:57:57PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 02, 1999 at 01:57:57PM +0100, Jeroen Ruigrok van der Werven wrote: > >On Wed, 1 Dec 1999, Harlan Stenn wrote: > -On [19991202 07:00], Matthew Jacob (mjacob@feral.com) wrote: > > >> Anybody here have the time/inclination/ability to review a *draft* of the > >> proposed BitKeeper license to see if it would be acceptable for use by > >> FreeBSD? > > >Since Larry's a neighbor and buddy of mine, I can look at it, but not > >until next week (poke me if to do so if it hasn't been done already). I > >already offered to him to do the port for *BSD, but he's a new dad and > >busy and didn't really get back to me... > > Sorry to say, but BitKeeper is severely braindead. They chose to built > on top of SCCS, which in itself is nearly useless. Also he has some > weird ideas about versioning which I certainly don't agree on. > > We use CVS at this moment, stepping towards BitKeeper from CVS is a step > backwards. I can not back these statements. Yes, I think there are some design flaws in BitKeeper, but certainly not enough to make it useless. I do not believe they are strong enough for it to be worse than CVS in any area I can think of, and contains improvements for a number of areas. I have, however, not tried using it in practice, so there may be problems I do not know about. > Eivind and me are trying to get a new version control system of the > ground which will kick arse on several accounts. Unfortunately work > draws us in. Yes, I am working on a new version control system, and Jeroen is helping. This system has at least one severe disadvantage compared to BitKeeper: It is not available as of right now. This work has deliberately been kept low-key, as I see it as harmful to hype prior to actually delivering. I also hope this to be a project that can cooperate with other version control projects (giving a very solid baseline, to which other projects can deliver 'value add'). As a such, it is extremely counter-productive to go off with active flamethrowers when another product is mentioned, and I want to totally distance me from it. This is NOT the official line of the OVCS project, and Larry is on the list of people to contact to look at possibilites for cooperation once OVCS has core code in place. My apologies on behalf of the OVCS project, Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 6:49: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.url.com.tw (alpha.url.com.tw [210.59.228.107]) by hub.freebsd.org (Postfix) with SMTP id 02B1C14C8D for ; Thu, 2 Dec 1999 06:48:48 -0800 (PST) (envelope-from allanchou@ms2.url.com.tw) Received: from ms2.url.com.tw ([210.59.228.10]) by AccSMTP/NT 2.5 (210.59.228.110) [210.59.228.110]; Thu, 2 Dec 1999 19:15:54 +0800 Received: from ms2.url.com.tw ([203.75.14.11]) by AccSMTP/NT 2.5 (210.59.228.35) [210.59.228.35]; Thu, 2 Dec 1999 16:05:21 +0800 Message-ID: <38462888.1A7E465@ms2.url.com.tw> Date: Thu, 02 Dec 1999 16:06:33 +0800 From: Allan Chou X-Mailer: Mozilla 4.5 [zhtw]C-CCK-MCD (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: About FreeBSD LAN driver development Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sir, I am DAVICOM Semiconductor, Inc. software engineer, our company want to develop the FreeBSD driver for our DM9102 LAN chip, and I have found some LAN cards FreeBSD driver code at web site http://www.freebsd.org/~wpaul. The following are my problems, can you reply them for me? 1. Can I use the LAN cards FreeBSD driver code at web site http://www.freebsd.org/~wpaul to develop our device driver ? 2. How can I upload our FreeBSD driver to the web site http://www.freebsd.org/~wpaul after our FreeBSd driver is ready? I look forward to receiving your response. Thanks a lot. Best regards, Allan Chou 1999.12.02 DAVICOM Semiconductor, Inc. allan_chou@davicom.com.tw or allanchou@ms2.url.com.tw To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 7:15:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id B6DE014BF6 for ; Thu, 2 Dec 1999 07:15:14 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id JAA26651; Thu, 2 Dec 1999 09:14:05 -0600 (CST) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id JAA24802; Thu, 2 Dec 1999 09:14:04 -0600 (CST) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id JAA04293; Thu, 2 Dec 1999 09:14:03 -0600 (CST) Date: Thu, 2 Dec 1999 09:14:03 -0600 (CST) From: Jonathan Lemon Message-Id: <199912021514.JAA04293@free.pcs> To: allanchou@ms2.url.com.tw, hackers@freebsd.org Subject: Re: About FreeBSD LAN driver development X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >I am DAVICOM Semiconductor, Inc. software engineer, >our company want to develop the FreeBSD driver for >our DM9102 LAN chip, and I have found some LAN cards >FreeBSD driver code at web site http://www.freebsd.org/~wpaul. > >The following are my problems, can you reply them for me? > >1. Can I use the LAN cards FreeBSD driver code at web site > http://www.freebsd.org/~wpaul to develop our device driver ? Yes. You can take all the code there and use it as a base to develop your own driver. >2. How can I upload our FreeBSD driver to the web site > http://www.freebsd.org/~wpaul after our FreeBSd driver > is ready? After your driver is done, you can either: 1. put it up on your own website, and announce it here, or 2. submit the code for inclusion in FreeBSD. You do this either by submitting a PR, or sending the code to a FreeBSD committer for review. For assistance with the driver, you may want to contact Bill Paul, . As a matter of fact, I believe that he has already written a driver for the Davicom DM9102 chip already, but only for -current. . -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 7:35: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id B87E014D06 for ; Thu, 2 Dec 1999 07:35:01 -0800 (PST) (envelope-from rminnich@lanl.gov) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id IAA348128 for ; Thu, 2 Dec 1999 08:33:57 -0700 (MST) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id IAA05514 for ; Thu, 2 Dec 1999 08:33:57 -0700 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Thu, 2 Dec 1999 08:33:57 -0700 (MST) From: "Ronald G. Minnich" X-Sender: rminnich@mini.acl.lanl.gov To: freebsd-hackers@FreeBSD.ORG Subject: Re: memory-to-memory copy 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, 1 Dec 1999, Zhihui Zhang wrote: > I used to know that memory to memory copy is done by the DMA controller in > the I/O bridge (Actually, this knowledge confues me because DMA controller Now, that brings back memories :-) check out the original dma chip design, ca. infinite years ago. Wow, did freebsd ever use this for bcopy? Hard to see that it would pay ... I know that early 8086 code did use it though. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 8:14:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D45D214BD7; Thu, 2 Dec 1999 08:14:34 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id IAA02057; Thu, 2 Dec 1999 08:15:24 -0800 Date: Thu, 2 Dec 1999 08:15:24 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Eivind Eklund Cc: Jeroen Ruigrok van der Werven , Harlan Stenn , hackers@FreeBSD.ORG Subject: Re: Bitkeeper license review In-Reply-To: <19991202153742.L76366@bitbox.follo.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 Well, I only wanted to help see whether the BitKeeper licence is somehow usable for *BSD. The comments about SCCS are ill considered and not on point. This isn't a discussion as to whether CVS will be deepsixed. This is only a discussion about broadening tool support for *BSD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 9: 3:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 1CFCC14CA6 for ; Thu, 2 Dec 1999 09:03:26 -0800 (PST) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id MAA22150; Thu, 2 Dec 1999 12:02:03 -0500 (EST) Reply-To: Randell Jesup To: Matthew Dillon , freebsd-hackers@freebsd.org Subject: Re: writing to an mmap()'ed region requires read access? From: Randell Jesup Date: 02 Dec 1999 12:04:31 -0500 In-Reply-To: Matthew Dillon's message of "Tue, 30 Nov 1999 23:28:44 -0800 (PST)" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: >:I was just playing with mmap() really for the first time, and I noticed >:something a bit odd. When you mmap() a file for writing, it also appears >:to require that you give it read permissions, else it dies on a signal 10. > > I've got a few hundred terrabytes of WOM to sell ya! I'll sell you a few petabytes! > This is just a byproduct of the MMU implementation. Most MMU's do > not support write-only maps because most do not implement separate > read and write bits. You get a valid and a write-enable bit instead, > or you just get a valid bit and have to use the dirty bit to make the > page writable (no write-enable bit at all). Makes sense. Shouldn't the mmap() return MAP_FAILED, probably with EACCES, instead of causing a signal 10? -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 9:25:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 042CC14E00 for ; Thu, 2 Dec 1999 09:25:26 -0800 (PST) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id MAA23121; Thu, 2 Dec 1999 12:23:16 -0500 (EST) Reply-To: Randell Jesup To: Wes Peters , freebsd-hackers@freebsd.org Subject: Re: Portable way to compare struct stat's? From: Randell Jesup Date: 02 Dec 1999 12:25:43 -0500 In-Reply-To: Wes Peters's message of "Wed, 01 Dec 1999 12:04:13 -0700" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters writes: >Randell Jesup wrote: >> >> On a single system, if st_dev and st_ino are equal, you must be referring >> >> to the same object. If not, I'd like to hear about it. >> > >> >This assumption has always caused lots of pain and suffering for >> >distributed file system people -- in a distributed file system, the >> >requirement that you can generate a unique 32 bit number for each file or >> >directory visible in the FS is a fairly arduous one. Either the number is >> >> Too bad that the "that's the way it's always been done"/"inodes >> were handed down by God" arguments are so hard to overcome. 1/2 :-) > >Perhaps we simply need to expand the size of ino_t and carefully convert >smaller types to it in the stat call? It's the paradigm that's the problem here, not the implementation, IMHO. While expanding ino_t might allow us to kludge around the problem, the real issue is that not all filesystems have an easy way to associate a (semi)permanent, unique number of any size with a specific file. If it were long enough to store a path, that might solve some FS's problems, except that directories in the path might get renamed. Quite honestly, the application should not be determining whether two files are the same directly. The OS/FS should do that. ino_t in stat() should be deprecated and and alternative system call created. Programs that reference the inode field should be modified to use the new interface. Of course, if I were to believe this would happen just because it's the right design, I'd also believe in the tooth fairy. :-( There's lots of ancient cruft in the design of *nix systems that's very hard to get people to consider even touching, let alone deprecating or removing. Sigh. -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 11:52:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 50FD9150EA for ; Thu, 2 Dec 1999 11:52:15 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA32635; Thu, 2 Dec 1999 20:27:05 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01613; Thu, 2 Dec 1999 20:34:05 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912021934.UAA01613@yedi.iaf.nl> Subject: Re: Linux ioctl not implemented error In-Reply-To: <199912020422.XAA52619@whizzo.transsys.com> from "Louis A. Mamakos" at "Dec 1, 1999 11:22:13 pm" To: louie@TransSys.COM (Louis A. Mamakos) Date: Thu, 2 Dec 1999 20:34:04 +0100 (CET) Cc: vsilyaev@mindspring.com, FreeBSD-hackers@FreeBSD.ORG, groudier@club-internet.fr X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.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 As Louis A. Mamakos wrote ... > > >The console complaints about the ioctl are gone now. Unfortunately VMware > > >still complains. I'll try to findout why. > > > > Try to load new vmware port from: > > http://www.mindspring.com/~vsilyaev/vmware/files/vmware.tar.gz > > > > And reinstall it. I think this may fix the problem. > > > > I'm trying the new port now. I seem to have a problem with the > vmware emulator program dying due to some panic caused by an > uncaught signal whenever I try to save a configuration. Same here. But that also happened with the pre-Dec 1, 1999 version. Does not happen always, sometimes it works. I have not yet found a pattern. > Right now, I opted to not save the configuration, and have proceeded > on to booting a FreeBSD-3.3 release CDROM, and installing it in a > VMware virtual machine. This is great. I dunno if it's just me, > but this seems to provoke manical laughter from time to time. Well, no manical laughter here yet. I still get "does not appear to be a cdrom device". Looks like I have some kind of config mistake here. What do people use for the /dev entry? /dev/wcd0a ? > Next up: how long to do a 'make world' of the 3.3 system inside the > emulator. Blurk.. ;-) > So, is there a working network interface for the virtual machine? That > would be very nifty, indeed. Vladimir's web page they don't work: " - All networking This require FreeBSD version of vmnet driver " Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 14:37:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 9757014FAC; Thu, 2 Dec 1999 14:37:09 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id OAA67848; Thu, 2 Dec 1999 14:37:01 -0800 (PST) Date: Thu, 2 Dec 1999 14:37:01 -0800 (PST) From: Julian Elischer To: hackers@freebsd.org Cc: jkh@freebsd.org Subject: Hardware list idea 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 Might it be an idea to allow the setup program to have an option "Send word back to FreeBSD.org that this model of machine works". or maybe, just a version of send-pr that does that, and uses a different template: Laptop: {yes/No} Manufacturer: Model: #If you don't have a model number fill in the following details: CPU: SPeed: BUS bridges: ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 14:44:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id A9A7214C5A; Thu, 2 Dec 1999 14:44:09 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 136A09B36; Thu, 2 Dec 1999 17:44:00 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 03774BA21; Thu, 2 Dec 1999 17:44:00 -0500 (EST) Date: Thu, 2 Dec 1999 17:43:59 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Julian Elischer Cc: hackers@freebsd.org, jkh@freebsd.org Subject: Re: Hardware list idea 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, 2 Dec 1999, Julian Elischer wrote: > > Might it be an idea to allow the setup program to have an option > "Send word back to FreeBSD.org that this model of machine works". > > or maybe, just a version of send-pr that does that, and uses a different > template: > > Laptop: {yes/No} > Manufacturer: > Model: > #If you don't have a model number fill in the following details: > CPU: > SPeed: > BUS bridges: > > ... > ...along with the output of dmesg for better correlation between drivers and models? ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 15:31: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id A144A15035; Thu, 2 Dec 1999 15:30:59 -0800 (PST) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2650.21) id ; Thu, 2 Dec 1999 16:28:01 -0700 Message-ID: <64003B21ECCAD11185C500805F31EC03046222B6@houston.matchlogic.com> From: Charles Randall To: "Chris D. Faulhaber" , Julian Elischer , hackers@freebsd.org Cc: jkh@freebsd.org Subject: RE: Hardware list idea Date: Thu, 2 Dec 1999 16:28:00 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "perlbug -ok" does the same thing for Perl. I added the first version of this a few years ago. Perhaps "send-pr -ok"? Charles -----Original Message----- From: Chris D. Faulhaber [mailto:jedgar@fxp.org] Sent: Thursday, December 02, 1999 3:44 PM To: Julian Elischer Cc: hackers@freebsd.org; jkh@freebsd.org Subject: Re: Hardware list idea On Thu, 2 Dec 1999, Julian Elischer wrote: > > Might it be an idea to allow the setup program to have an option > "Send word back to FreeBSD.org that this model of machine works". > > or maybe, just a version of send-pr that does that, and uses a different > template: > > Laptop: {yes/No} > Manufacturer: > Model: > #If you don't have a model number fill in the following details: > CPU: > SPeed: > BUS bridges: > > ... > ...along with the output of dmesg for better correlation between drivers and models? ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. 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 Dec 2 15:40:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id BA1C514C9D; Thu, 2 Dec 1999 15:40:32 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id SAA118588; Thu, 2 Dec 1999 18:39:38 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Thu, 2 Dec 1999 18:45:19 -0500 To: Julian Elischer , hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Hardware list idea Cc: jkh@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:37 PM -0800 12/2/99, Julian Elischer wrote: >Might it be an idea to allow the setup program to have an option >"Send word back to FreeBSD.org that this model of machine works". > >or maybe, just a version of send-pr that does that, and uses a >different template: I think openbsd asks users to email them the output of 'dmesg', so they can tell which drivers are really of interest to the greatest number of their users. Seems like a reasonable idea. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 15:57:56 1999 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 A4B8F14C2B for ; Thu, 2 Dec 1999 15:57:46 -0800 (PST) (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 QAA19860 for ; Thu, 2 Dec 1999 16:55:38 -0700 (MST) (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 QAA06352 for ; Thu, 2 Dec 1999 16:55:38 -0700 (MST) Message-Id: <199912022355.QAA06352@harmony.village.org> To: hackers@freebsd.org Subject: tty level buffer overflows Date: Thu, 02 Dec 1999 16:55:38 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dec 2 11:08:56 bifrost /kernel: sio0: 208 more tty-level buffer overflows (total 3356) is appearing on our ppp machine. What are tty-level buffer overflows? How can I fix this? What resource is running out? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 16:14: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 0B6C314FDA for ; Thu, 2 Dec 1999 16:13:57 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id QAA18009; Thu, 2 Dec 1999 16:10:18 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA25272; Thu, 2 Dec 1999 16:10:17 -0800 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA22790; Thu, 2 Dec 99 16:10:15 PST Message-Id: <38470A6F.D5962E5E@softweyr.com> Date: Thu, 02 Dec 1999 17:10:23 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Harlan Stenn Cc: hackers@FreeBSD.ORG Subject: Re: Bitkeeper license review References: <12389.944103209@brown.pfcs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Harlan Stenn wrote: > > Anybody here have the time/inclination/ability to review a *draft* of the > proposed BitKeeper license to see if it would be acceptable for use by > FreeBSD? I'm not sure what you mean by "acceptable for use by FreeBSD". If you mean, could we include BitKeeper as a port in FreeBSD, the answer is certainly yes. Doing so would be a good idea, too, we want FreeBSD to be a splendiferous software development system, with as many tools as possible. If you mean, would the FreeBSD Project be willing to have their change logs sent to a public server somewhere, we already do. Our CVS server is open to public scrutiny, of both the code and commit logs. If you mean developing FreeBSD-related projects using BitKeeper as a source store, I doubt anyone would complain at all. Please contribute your FreeBSD port of it before you set off, and I'll lead the cheering. ;^) If you mean moving the FreeBSD CVS repository to BitKeeper, you probably don't understand how much work you are asking for even if BitKeeper provided some compelling features over what we have now. I my opinion, it does not. I've read through Larry's explanation of the theory of operation for BitKeeper, and it seems quite good as a tool for enabling Linus to pore over every patch flowing into Linux Central, and less useful for just about anything else. But I certainly don't see anything in the license WE would find objectionable. Quite the opposite, I expect he will get a LOT more licensing flak from the Linux crowd. -- "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 Thu Dec 2 17: 1:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 0566C14D47 for ; Thu, 2 Dec 1999 17:01:42 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2iniikt.dialup.mindspring.com [165.121.74.157]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id UAA29290; Thu, 2 Dec 1999 20:01:37 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id QAA00626; Thu, 2 Dec 1999 16:05:16 -0500 (EST) (envelope-from vsilyaev) Date: Thu, 2 Dec 1999 16:05:16 -0500 From: "Vladimir N. Silyaev" To: Wilko Bulte Cc: "Louis A. Mamakos" , vsilyaev@mindspring.com, FreeBSD-hackers@FreeBSD.ORG, groudier@club-internet.fr Subject: Re: Linux ioctl not implemented error Message-ID: <19991202160515.C536@jupiter.delta.ny.us> References: <199912020422.XAA52619@whizzo.transsys.com> <199912021934.UAA01613@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912021934.UAA01613@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Thu, Dec 02, 1999 at 08:34:04PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 02, 1999 at 08:34:04PM +0100, Wilko Bulte wrote: > > > > I'm trying the new port now. I seem to have a problem with the > > vmware emulator program dying due to some panic caused by an > > uncaught signal whenever I try to save a configuration. > > Same here. But that also happened with the pre-Dec 1, 1999 version. > Does not happen always, sometimes it works. I have not yet found > a pattern. Every time, when you save new configuration, VMware complained about unexpected signal (before that it save first line from configuration file). But if you load configuration and change it, or save it with same or another name, all be working well. > > > Right now, I opted to not save the configuration, and have proceeded > > on to booting a FreeBSD-3.3 release CDROM, and installing it in a > > VMware virtual machine. This is great. I dunno if it's just me, > > but this seems to provoke manical laughter from time to time. > > Well, no manical laughter here yet. I still get "does not > appear to be a cdrom device". Looks like I have some kind of config > mistake here. What do people use for the /dev entry? /dev/wcd0a ? Lines from my configuration file: ---------------- ide0:1.present = TRUE ide0:1.deviceType = "atapi-cdrom" ide0:1.fileName = "/dev/rwcd0c" ---------------- > > So, is there a working network interface for the virtual machine? That > > would be very nifty, indeed. > > Vladimir's web page they don't work: > > " > - All networking > This require FreeBSD version of vmnet driver > " Exactly, and vmware distribution have the sources of this driver. But this module consisted from one source file, in this file implemented three devices, and one file node in the linux procfs. Of course this file _very_ linux specific. -- Vladimir Silyaev. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 17:50:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 02C8C14F8B for ; Thu, 2 Dec 1999 17:50:07 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id TAA41173; Thu, 2 Dec 1999 19:49:52 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Thu, 2 Dec 1999 19:49:52 -0600 (CST) From: David Scheidt To: Warner Losh Cc: hackers@freebsd.org Subject: Re: tty level buffer overflows In-Reply-To: <199912022355.QAA06352@harmony.village.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, 2 Dec 1999, Warner Losh wrote: > > Dec 2 11:08:56 bifrost /kernel: sio0: 208 more tty-level buffer overflows (total 3356) > > is appearing on our ppp machine. What are tty-level buffer overflows? > How can I fix this? What resource is running out? If I remember properly, it is a receive buffer filling up. There were some hacks in 2.x kernels to get around it, so you might want t o go look through the archives. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 17:54:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 2E93A14F8B for ; Thu, 2 Dec 1999 17:54:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA02824; Thu, 2 Dec 1999 17:55:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912030155.RAA02824@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: David Scheidt Cc: Warner Losh , hackers@freebsd.org Subject: Re: tty level buffer overflows In-reply-to: Your message of "Thu, 02 Dec 1999 19:49:52 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Dec 1999 17:55:18 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 2 Dec 1999, Warner Losh wrote: > > > > > Dec 2 11:08:56 bifrost /kernel: sio0: 208 more tty-level buffer overflows (total 3356) > > > > is appearing on our ppp machine. What are tty-level buffer overflows? > > How can I fix this? What resource is running out? > > If I remember properly, it is a receive buffer filling up. There were some > hacks in 2.x kernels to get around it, so you might want t o go look through > the archives. It's documented in the sio(4) manpage, which is always worth reading. -- \\ 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 Thu Dec 2 18: 7: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id 2EDB814CF4 for ; Thu, 2 Dec 1999 18:06:59 -0800 (PST) (envelope-from akm@mail.theinternet.com.au) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id MAA84653; Fri, 3 Dec 1999 12:16:00 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <199912030216.MAA84653@mail.theinternet.com.au> Subject: Re: Linux ioctl not implemented error In-Reply-To: <19991202160515.C536@jupiter.delta.ny.us> from "Vladimir N. Silyaev" at "Dec 2, 1999 4: 5:16 pm" To: vsilyaev@mindspring.com (Vladimir N. Silyaev) Date: Fri, 3 Dec 1999 12:16:00 +1000 (EST) Cc: wilko@yedi.iaf.nl, louie@TransSys.COM, vsilyaev@mindspring.com, FreeBSD-hackers@FreeBSD.ORG, groudier@club-internet.fr 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 +----[ Vladimir N. Silyaev ]--------------------------------------------- | | > Vladimir's web page they don't work: | > | > " | > - All networking | > This require FreeBSD version of vmnet driver | > " | | Exactly, and vmware distribution have the sources of this driver. | But this module consisted from one source file, in this file | implemented three devices, and one file node in the linux procfs. | Of course this file _very_ linux specific. The bochs port implements a pseudo-ne2000 using BPF under FreeBSD, is this approach a possibility? The freebsd ether stuff from bochs has Peter Grehan (grehan@iprg.nokia.com) on the copyright so he'd be the one to contact about the availability of (parts of) his code to use in a port I suppose. It does have some limitations (can't send packets to the host/os) but I don't know how complete the code is either. Kevin Lawton (the bochs author) is working on his own vmware type system as well, they're still in an experimental mode though. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 18: 9:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id EFE0114CF4 for ; Thu, 2 Dec 1999 18:09:10 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id VAA34700; Thu, 2 Dec 1999 21:08:14 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <3845712D.F4D51A70@softweyr.com> References: <3845712D.F4D51A70@softweyr.com> Date: Thu, 2 Dec 1999 21:13:56 -0500 To: Wes Peters , Randell Jesup From: Garance A Drosihn Subject: Re: Portable way to compare struct stat's? Cc: Robert Watson , freebsd-hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:04 PM -0700 12/1/99, Wes Peters wrote: > > >> On a single system, if st_dev and st_ino are equal, you must be > > >> referring to the same object. If not, I'd like to hear about it. > > > > > >This assumption has always caused lots of pain and suffering for > > >distributed file system people -- in a distributed file system, the > > >requirement that you can generate a unique 32 bit number for each file > > >or directory visible in the FS is a fairly arduous one. Either... > >Perhaps we simply need to expand the size of ino_t and carefully convert >smaller types to it in the stat call? In the case of AFS, I think you'd want to expand the size of st_dev. All files in an AFS volume are "one device", I would think. If the "device" is gone (ie, the volume is not mounted), then all files in that "device" (volume) will not be available. I don't know what would be best for other distributed file systems, though. Maybe both variables would have to increase in size. Maybe we should start by creating an "fcompare()" routine, which you'd pass two file descriptors to and it would say if they're the same file. Initially that routine could just do two fstat()'s, and compare st_dev and st_ino. We could then expand it to do better comparisons for other file-systems. That's only a partial solution, of course, but I imagine it would be pretty tricky to change the field-sizes for st_dev and st_ino in the stat structure without breaking lots of things... --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 19:33: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by hub.freebsd.org (Postfix) with ESMTP id 4313014BC8 for ; Thu, 2 Dec 1999 19:32:57 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id WAA66379; Thu, 2 Dec 1999 22:32:44 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14407.14812.812358.220983@trooper.velocet.net> Date: Thu, 2 Dec 1999 22:32:44 -0500 (EST) To: freebsd-hackers@freebsd.org Subject: Inverting a gdb -k mapping? X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can grep through the vmcore.x file and find the offset of the string I put on the stack by strings -t x ; Thu, 2 Dec 1999 19:36:39 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2iniikt.dialup.mindspring.com [165.121.74.157]) by fb01.eng00.mindspring.net (8.9.3/8.8.5) with ESMTP id WAA20651; Thu, 2 Dec 1999 22:36:08 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id WAA05490; Thu, 2 Dec 1999 22:36:05 -0500 (EST) (envelope-from vsilyaev) Date: Thu, 2 Dec 1999 22:36:04 -0500 From: "Vladimir N. Silyaev" To: Andrew Kenneth Milton Cc: "Vladimir N. Silyaev" , wilko@yedi.iaf.nl, louie@TransSys.COM, FreeBSD-hackers@FreeBSD.ORG, groudier@club-internet.fr Subject: vmnet (was: Linux ioctl not implemented error) Message-ID: <19991202223604.B5379@jupiter.delta.ny.us> References: <19991202160515.C536@jupiter.delta.ny.us> <199912030216.MAA84653@mail.theinternet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912030216.MAA84653@mail.theinternet.com.au>; from akm@mail.theinternet.com.au on Fri, Dec 03, 1999 at 12:16:00PM +1000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 03, 1999 at 12:16:00PM +1000, Andrew Kenneth Milton wrote: > The bochs port implements a pseudo-ne2000 using BPF under FreeBSD, is > this approach a possibility? The freebsd ether stuff from bochs has > Peter Grehan (grehan@iprg.nokia.com) on the copyright so he'd be the > one to contact about the availability of (parts of) his code to use in > a port I suppose. I don't know. At any case we are need provide the same API as linux vmnet provide, so we are need to implement it in the kernel module. But bochs use user level implementation. > It does have some limitations (can't send packets to the host/os) but > I don't know how complete the code is either. At this time I found the next message (it was posted more than 3 years ago at the freebsd-hackers mailing list): http://www.freebsd.org/cgi/getmsg.cgi?fetch=661424+0+/usr/local/www/db/text/1996/freebsd-hackers/19961020.freebsd-hackers It's a very long URL but I hope that it's possible to retrieve it. At least you can search via its subject: Networking in PCEMU (1/2) I don't study this code, but it looking not so bad. > > Kevin Lawton (the bochs author) is working on his own vmware type system > as well, they're still in an experimental mode though. Yes. I looking to this project, named as freemware. Their URL: http://www.freemware.org/ But this code very experimental. And to develop such kind of software are need to have steal nerves. I fill that, at the time when I was porting vmware. I have too much hours of very interested work - load driver, launch vmware and then looking into the DDB double fault screen. Reload box, and then again. -- Vladimir Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 20: 3: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 8E4D514CCE for ; Thu, 2 Dec 1999 20:03:02 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id UAA76181; Thu, 2 Dec 1999 20:02:37 -0800 (PST) Date: Thu, 2 Dec 1999 20:02:37 -0800 (PST) From: Julian Elischer To: "Vladimir N. Silyaev" Cc: Andrew Kenneth Milton , wilko@yedi.iaf.nl, louie@TransSys.COM, FreeBSD-hackers@FreeBSD.ORG, groudier@club-internet.fr Subject: Re: vmnet (was: Linux ioctl not implemented error) In-Reply-To: <19991202223604.B5379@jupiter.delta.ny.us> 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, 2 Dec 1999, Vladimir N. Silyaev wrote: > On Fri, Dec 03, 1999 at 12:16:00PM +1000, Andrew Kenneth Milton wrote: > > The bochs port implements a pseudo-ne2000 using BPF under FreeBSD, is > > this approach a possibility? The freebsd ether stuff from bochs has > > Peter Grehan (grehan@iprg.nokia.com) on the copyright so he'd be the > > one to contact about the availability of (parts of) his code to use in > > a port I suppose. > I don't know. At any case we are need provide the same API as linux > vmnet provide, so we are need to implement it in the kernel module. > But bochs use user level implementation. > > > It does have some limitations (can't send packets to the host/os) but > > I don't know how complete the code is either. > At this time I found the next message (it was posted more than 3 years > ago at the freebsd-hackers mailing list): > http://www.freebsd.org/cgi/getmsg.cgi?fetch=661424+0+/usr/local/www/db/text/1996/freebsd-hackers/19961020.freebsd-hackers > > It's a very long URL but I hope that it's possible to retrieve it. At least > you can search via its subject: Networking in PCEMU (1/2) > > I don't study this code, but it looking not so bad. check if you might not be able to use a netgraph module for this. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 20: 9:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by hub.freebsd.org (Postfix) with ESMTP id 77B4D14BD0 for ; Thu, 2 Dec 1999 20:09:40 -0800 (PST) (envelope-from cyouse@paradox.nexuslabs.com) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id XAA57381 for ; Thu, 2 Dec 1999 23:07:12 -0500 (EST) (envelope-from cyouse@paradox.nexuslabs.com) Date: Thu, 2 Dec 1999 23:07:12 -0500 (EST) From: Chuck Youse To: freebsd-hackers@freebsd.org Subject: tmpfs .. ? 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 Has anyone toyed with the idea of implementing a swap-based filesystem similar to Sun's tmpfs? Chuck Youse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 2 20:13:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 56C1215039 for ; Thu, 2 Dec 1999 20:13:35 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA04264; Thu, 2 Dec 1999 20:13:42 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912030413.UAA04264@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Chuck Youse Cc: freebsd-hackers@freebsd.org Subject: Re: tmpfs .. ? In-reply-to: Your message of "Thu, 02 Dec 1999 23:07:12 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Dec 1999 20:13:42 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Has anyone toyed with the idea of implementing a swap-based filesystem > similar to Sun's tmpfs? Like, oh, MFS maybe? Try 'man -k mfs'. -- \\ 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 Fri Dec 3 2:20:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 7054314C84 for ; Fri, 3 Dec 1999 02:18:08 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id MAA12877; Fri, 3 Dec 1999 12:16:03 +0200 (EET) (envelope-from ru) Date: Fri, 3 Dec 1999 12:16:03 +0200 From: Ruslan Ermilov To: hackers@FreeBSD.org Subject: Understanding ``stray irq 7'' Message-ID: <19991203121603.A11424@relay.ucb.crimea.ua> Mail-Followup-To: hackers@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Could someone please comment on the following info from the Intel: : 8259/82C59 : Spurious IRQ7 : : In some applications, problem with a spurious IRQ7 might exist. : For example, a spurios IRQ7 will occur under the following condition: : : While the device is performing extensive I/O operations : (IN AL, DX; OUT DX, AL), an external signal triggers IRQ3. : Spurious enabling of IRQ7 and occassional losing of IRQ3 will be : the outcome of this condition. : : Design Consideration: : : - A spurious IRQ7 occurs, in the 8259, if any interrupt request : duration is too short or hasn't met the setup time required by : the 8259A. : : - This is a standard 8259 behavior under specific conditions. : IRQ7 is triggered when IRQ7 is enabled and is requested : OR : when an interrupt request clears (by itself) before the CPU : services the request. A software solution would be to write : an IRQ7 handler that checks the various possible requesters : and to handle any "missed" interrupts from any of those : requesters. (http://support.intel.com/support/controllers/peripheral/7507.htm) -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 5:58:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 98A9414D88 for ; Fri, 3 Dec 1999 05:58:52 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id HAA15157; Fri, 3 Dec 1999 07:58:05 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Fri, 3 Dec 1999 07:58:05 -0600 (CST) From: David Scheidt To: David Gilbert Cc: freebsd-hackers@freebsd.org Subject: Re: Inverting a gdb -k mapping? In-Reply-To: <14407.14812.812358.220983@trooper.velocet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 2 Dec 1999, David Gilbert wrote: > I can grep through the vmcore.x file and find the offset of the string > I put on the stack by > > strings -t x > ... but how do I associate that back with an address inside gdb -k? > > My problem is that vinum (or something related to it) is trashing the > stack and trying to return to 0x0 is panic'ing the kernel (of course). Have you looked a t Greg Lehey's how to debug vinum pages at http://www.lemis.com/vinum/how-to-debug.html ? David Scheidt > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 6:13:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by hub.freebsd.org (Postfix) with ESMTP id DC97A14E9B for ; Fri, 3 Dec 1999 06:13:13 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id JAA88969; Fri, 3 Dec 1999 09:12:47 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14407.53214.998956.352922@trooper.velocet.net> Date: Fri, 3 Dec 1999 09:12:46 -0500 (EST) To: David Scheidt Cc: David Gilbert , freebsd-hackers@freebsd.org Subject: Re: Inverting a gdb -k mapping? In-Reply-To: References: <14407.14812.812358.220983@trooper.velocet.net> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "David" == David Scheidt writes: [...] David> Have you looked a t Greg Lehey's how to debug vinum pages at David> http://www.lemis.com/vinum/how-to-debug.html ? Very much so. The issue is that the whole stack trace (which I have posted in stable before) looks like this: #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 #1 0xc0152f68 in at_shutdown ( function=0xc0237fc6 <__set_sysinit_set_sym_memdev_sys_init+1050>, arg=0x0, queue=12) at ../../kern/kern_shutdown.c:446 #2 0xc0209c15 in trap_fatal (frame=0xc0241260, eva=0) at ../../i386/i386/trap.c:942 #3 0xc02098f3 in trap_pfault (frame=0xc0241260, usermode=0, eva=0) at ../../i386/i386/trap.c:835 #4 0xc0209596 in trap (frame={tf_es = 1835991056, tf_ds = 1701904400, tf_edi = -1073215488, tf_esi = -1058170880, tf_ebp = -1071377704, tf_isp = -1071377784, tf_ebx = -1057735652, tf_edx = 0, tf_ecx = -1057735652, tf_eax = -1073215488, tf_trapno = 12, tf_err = 0, tf_eip = 0, tf_cs = 8, tf_eflags = 66054, tf_esp = -1072233935, tf_ss = -1057735652}) at ../../i386/i386/trap.c:437 #5 0x0 in ?? () Now... some very helpful people have pointed out that the value of tf_esp (the stack pointer) does not make sense --- it is not byte aligned. The best guess at analysis currently is that stack corruption is occuring and some function is returning to a NULL value on the stack. Now... this is very hard to debug. I need to find the stack or find information about the stack. It would be really cool to know what function is causing corruption on the stack. But nosing around a large corefile looking for the kernel stack is a long process that tends to make me sleepy. Does the kernel stack start at the same place each boot? Is there a way of finding the stack that caused this call to trap() Help? I'm willing to do quite a lot of grunt work here (it's worth about $4000 to me to solve this problem), but I need some help. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 9:23: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82]) by hub.freebsd.org (Postfix) with ESMTP id E4EB315025 for ; Fri, 3 Dec 1999 09:22:54 -0800 (PST) (envelope-from jin@george.lbl.gov) Received: from SpamWall.lbl.gov (localhost [127.0.0.1]) by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id JAA02868 for ; Fri, 3 Dec 1999 09:22:36 -0800 (PST) From: jin@george.lbl.gov Received: from george.lbl.gov (george.lbl.gov [131.243.2.12]) by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id JAA02862 for ; Fri, 3 Dec 1999 09:22:36 -0800 (PST) Received: (from jin@localhost) by george.lbl.gov (8.9.1b+Sun/8.9.1) id JAA20387 for hackers@freebsd.org; Fri, 3 Dec 1999 09:22:34 -0800 (PST) Date: Fri, 3 Dec 1999 09:22:34 -0800 (PST) Message-Id: <199912031722.JAA20387@george.lbl.gov> To: hackers@freebsd.org Subject: question on lkm / kld in 3.3-RELEASE or later Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that lkm is no longer working after 3.3, it complains regardless the mod is compiled in aout or elf (setenv OBJFORMAT before doing compiling): # modload -ezatm_mod /lkm/znatmdrv.o ld: /kernel: malformed input file (not rel or archive) modload: /usr/bin/ld: return code 1 So, it looks like that kld is the way to go. However, there is no miscellaneous module under kld (/usr/share/examples/kld/{cdev, syscall}). Below is some comment in kld/cdev/module/cdevmod.c, It says that cdev module is "a miscellaneous module". Will kld provide a miscellaneous module in the future? or miscellaneous module is merged with cdev module? Thanks for any information, -Jin ... #include "cdev.h" static int cdev_load(module_t, modeventtype_t, void *); /* * This function is called each time the module is loaded or unloaded. * Since we are a miscellaneous module, we have to provide whatever * code is necessary to patch ourselves into the area we are being * loaded to change. * * The stat information is basically common to all modules, so there * is no real issue involved with stat; we will leave it lkm_nullcmd(), * since we don't have to do anything about it. */ static int cdev_load(mod, cmd, arg) module_t mod; modeventtype_t cmd; void * arg; { int err = 0; cdevmod.c: unmodified, readonly: line 79 of 122 [64%] ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 10: 9:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ckmso1.proxy.att.com (ckmso1.att.com [12.20.58.69]) by hub.freebsd.org (Postfix) with ESMTP id F1BFA15216 for ; Fri, 3 Dec 1999 10:09:22 -0800 (PST) (envelope-from myevmenkin@att.com) Received: from njb140r1.ems.att.com ([135.65.202.58]) by ckmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id NAA01528 for ; Fri, 3 Dec 1999 13:08:28 -0500 (EST) Received: from njb140bh1.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id NAA00520; Fri, 3 Dec 1999 13:07:57 -0500 (EST) Received: by njb140bh1.ems.att.com with Internet Mail Service (5.5.2448.0) id ; Fri, 3 Dec 1999 13:08:28 -0500 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'freebsd-hackers@freebsd.org'" Subject: How to get Ethernet MAC address Date: Fri, 3 Dec 1999 13:08:21 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="koi8-r" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, Is there any ioctl command to get Ethernet MAC address from specific interface? I've checked netstat and ifconfig source code and mail archive. It seems to me all use different methods to do the same thing. I'm using FreeBSD 3.3-Release. May be SIOGHWADDR (as in Linux) is a good idea? :) Thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 10:15:23 1999 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 94B8A14E82; Fri, 3 Dec 1999 10:15:17 -0800 (PST) (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 LAA23177; Fri, 3 Dec 1999 11:14:48 -0700 (MST) (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 LAA11849; Fri, 3 Dec 1999 11:14:47 -0700 (MST) Message-Id: <199912031814.LAA11849@harmony.village.org> To: Mike Smith Subject: Re: tty level buffer overflows Cc: David Scheidt , hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 02 Dec 1999 17:55:18 PST." <199912030155.RAA02824@mass.cdrom.com> References: <199912030155.RAA02824@mass.cdrom.com> Date: Fri, 03 Dec 1999 11:14:47 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912030155.RAA02824@mass.cdrom.com> Mike Smith writes: : It's documented in the sio(4) manpage, which is always worth reading. Even reading the sio manpage is unclear. All it says is that things are too slow. Steady state I don't get these, just every now and again it happens. No apparent correlation to the time of day, cron jobs running, etc. What I was wondering is if there is a way to, say, double the buffer size. Also, what is the number of overflows mean? Is that bytes? clists? 16byte chunks? The overflow seems to happen just once and it is always a number less than 1000. I'd gladly spend an extra 1-2k of memory to help my poor ppp machine over the humps. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 12: 9:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 9F59B1523F for ; Fri, 3 Dec 1999 12:09:10 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id NAA00539; Fri, 3 Dec 1999 13:08:34 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA12138; Fri, 3 Dec 1999 13:08:33 -0700 Date: Fri, 3 Dec 1999 13:08:33 -0700 Message-Id: <199912032008.NAA12138@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: tty level buffer overflows In-Reply-To: <199912022355.QAA06352@harmony.village.org> References: <199912022355.QAA06352@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Dec 2 11:08:56 bifrost /kernel: sio0: 208 more tty-level buffer overflows (total 3356) > > is appearing on our ppp machine. What are tty-level buffer overflows? > How can I fix this? What resource is running out? Is it safe to assume that this isn't happening on a laptop? At least with the old code (I don't know about the new code), sio isn't using fast interrupts when used by the laptop code. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 12:40:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 08EC7152EC for ; Fri, 3 Dec 1999 12:39:54 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA09506; Fri, 3 Dec 1999 21:26:27 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA05126; Fri, 3 Dec 1999 21:37:03 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912032037.VAA05126@yedi.iaf.nl> Subject: Re: Linux ioctl not implemented error In-Reply-To: <19991202160515.C536@jupiter.delta.ny.us> from "Vladimir N. Silyaev" at "Dec 2, 1999 4: 5:16 pm" To: vsilyaev@mindspring.com (Vladimir N. Silyaev) Date: Fri, 3 Dec 1999 21:37:03 +0100 (CET) Cc: louie@TransSys.COM, vsilyaev@mindspring.com, FreeBSD-hackers@FreeBSD.ORG, groudier@club-internet.fr X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.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 As Vladimir N. Silyaev wrote ... Hello Vladimir, > On Thu, Dec 02, 1999 at 08:34:04PM +0100, Wilko Bulte wrote: > > Same here. But that also happened with the pre-Dec 1, 1999 version. > > Does not happen always, sometimes it works. I have not yet found > > a pattern. > Every time, when you save new configuration, VMware complained about > unexpected signal (before that it save first line from configuration > file). But if you load configuration and change it, or save it with Right, you get a file with only: #!/usr/local/lib/vmware/bin/vmware in it. > same or another name, all be working well. Hm, I think I also saw it fallover when I did this (sometimes, not always). Anyway, I'm more concerned with the CDrom drive right now. > > Well, no manical laughter here yet. I still get "does not > > appear to be a cdrom device". Looks like I have some kind of config > > mistake here. What do people use for the /dev entry? /dev/wcd0a ? > Lines from my configuration file: > ---------------- > ide0:1.present = TRUE > ide0:1.deviceType = "atapi-cdrom" > ide0:1.fileName = "/dev/rwcd0c" > ---------------- Tried that. No luck :-( See also seperate posting. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Fri Dec 3 13:30:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 8B0AE14D25 for ; Fri, 3 Dec 1999 13:30:15 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id PAA30168; Fri, 3 Dec 1999 15:29:28 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Fri, 3 Dec 1999 15:29:28 -0600 (CST) From: David Scheidt To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: tty level buffer overflows In-Reply-To: <199912031814.LAA11849@harmony.village.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 Fri, 3 Dec 1999, Warner Losh wrote: > What I was wondering is if there is a way to, say, double the buffer > size. Also, what is the number of overflows mean? Is that bytes? > clists? 16byte chunks? The overflow seems to happen just once and it It's the return from b_to_q, so it is the number of characters that it failed to be copied from the linear buffer to clist chain. It should be possible to increase the size of the buffer a bit, but I haven't figured it out yet. sio.c has changed a lot since the last time I hacked at it. david scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 13:57:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by hub.freebsd.org (Postfix) with ESMTP id 9EF9014BEF for ; Fri, 3 Dec 1999 13:57:51 -0800 (PST) (envelope-from justin@rhapture.apple.com) Received: from mailgate2.apple.com ([17.129.100.225]) by mail-out2.apple.com (8.9.3/8.9.3) with ESMTP id NAA25999 for ; Fri, 3 Dec 1999 13:56:53 -0800 (PST) Received: from scv1.apple.com (scv1.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Fri, 03 Dec 1999 13:49:37 -0800 Received: from rhapture.apple.com (rhapture.apple.com [17.202.40.59]) by scv1.apple.com (8.9.3/8.9.3) with ESMTP id NAA12722; Fri, 3 Dec 1999 13:49:36 -0800 (PST) Received: (from justin@localhost) by rhapture.apple.com (8.9.1/8.9.1) id NAA00781; Fri, 3 Dec 1999 13:49:36 -0800 (PST) Message-Id: <199912032149.NAA00781@rhapture.apple.com> To: "Yevmenkin, Maksim N, CSCIO" Subject: Re: How to get Ethernet MAC address Cc: "'freebsd-hackers@freebsd.org'" Date: Fri, 3 Dec 1999 13:49:35 -0800 From: "Justin C. Walker" Reply-To: justin@apple.com X-Mailer: by Apple MailViewer (2.105.dev) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: "Yevmenkin, Maksim N, CSCIO" > Date: 1999-12-03 10:11:49 -0800 > To: "'freebsd-hackers@freebsd.org'" > Subject: How to get Ethernet MAC address > Delivered-to: freebsd-hackers@freebsd.org > X-Mailer: Internet Mail Service (5.5.2448.0) > X-Loop: FreeBSD.ORG > > Hello All, > > Is there any ioctl command to get Ethernet MAC address from specific > interface? > > I've checked netstat and ifconfig source code and mail archive. > It seems to me all use different methods to do the same thing. > > I'm using FreeBSD 3.3-Release. May be SIOGHWADDR (as in Linux) > is a good idea? Try SIOCGIFCONF, and search through the list of returned structures for one with address family AF_LINK. The sockaddr for this one will be a sockaddr_dl, with the MAC address enclosed. See the code, e.g., for netstat, or for ifconfig. There's also a sysctl() request that works. Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Manager, CoreOS Networking | Men are from Earth. Apple Computer, Inc. | Women are from Earth. 2 Infinite Loop | Deal with it. Cupertino, CA 95014 | *-------------------------------------*-------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 15:20: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 89603152EC for ; Fri, 3 Dec 1999 15:20:02 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id XAA58538; Fri, 3 Dec 1999 23:26:53 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 3 Dec 1999 23:26:53 +0000 (GMT) From: Doug Rabson To: jin@george.lbl.gov Cc: hackers@freebsd.org Subject: Re: question on lkm / kld in 3.3-RELEASE or later In-Reply-To: <199912031722.JAA20387@george.lbl.gov> 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, 3 Dec 1999 jin@george.lbl.gov wrote: > It seems that lkm is no longer working after 3.3, it complains regardless > the mod is compiled in aout or elf (setenv OBJFORMAT before doing compiling): > > # modload -ezatm_mod /lkm/znatmdrv.o > ld: /kernel: malformed input file (not rel or archive) > modload: /usr/bin/ld: return code 1 > > So, it looks like that kld is the way to go. However, there is no > miscellaneous module under kld (/usr/share/examples/kld/{cdev, syscall}). > Below is some comment in kld/cdev/module/cdevmod.c, It says that cdev > module is "a miscellaneous module". > > Will kld provide a miscellaneous module in the future? or miscellaneous > module is merged with cdev module? > > Thanks for any information, There aren't any specific module types for KLD. Basically, we just run all the SYSINITs in the code which is loaded. Virtually anything can be built from that and we have provided hooks for registering filesystems, devices, syscalls, etc. To do something else, just use a SYSINIT to call a custom initialisation function of your own. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 16: 0:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 9A27B14C34 for ; Fri, 3 Dec 1999 16:00:28 -0800 (PST) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id TAA11611 for ; Fri, 3 Dec 1999 19:00:11 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA00342; Fri, 3 Dec 1999 18:59:40 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.3) id SAA58078; Fri, 3 Dec 1999 18:59:40 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <199912032359.SAA58078@dean.pc.sas.com> Subject: natd is jumpy To: freebsd-hackers@freebsd.org Date: Fri, 3 Dec 1999 18:59:40 -0500 (EST) 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 Hi, I posted this on -questions about five days ago and haven't received any hints or suggestions. Does anyone here have any ideas? I use natd and a 56k phone connection to my ISP so that all my computers can share one line. This all works fine, but I experience very noticeable jumpiness when typing over a telnet connection to a remote system. Delays of 7-10 seconds between typing characters and them appearing on my screen are not uncommon. If I rebuild my kernel without IPFIREWALL and IPDIVERT, and disable natd and the firewall code, these delays go away so I am assuming that it is natd/firewall/divert that is responsible for this delay. Is there a parameter or anything that I can tune to eliminate or reduce this affect? I looked in the lists and did not see anything specific to my situation. I am running FreeBSD -current as of 11/21 and my firewall is set up as "open". Any suggestions are appreciated. Thanks, -Brian -- Brian Dean brdean@unx.sas.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 16:10:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vitoria.ddsecurity.com.br (vitoria.ddsecurity.com.br [200.18.130.93]) by hub.freebsd.org (Postfix) with SMTP id E358014D7B for ; Fri, 3 Dec 1999 16:10:04 -0800 (PST) (envelope-from grios@ddsecurity.com.br) Received: (qmail 62551 invoked from network); 4 Dec 1999 00:08:00 -0000 Received: from modem26.tdnet.com.br (HELO ddsecurity.com.br) (200.236.148.126) by vitoria.ddsecurity.com.br with SMTP; 4 Dec 1999 00:08:00 -0000 Message-ID: <384868AC.C6D1CF2A@ddsecurity.com.br> Date: Fri, 03 Dec 1999 23:04:44 -0200 From: Gustavo V G C Rios X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: reboots 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 am sending this message, in order to get a help from you wizards. Just after turn power on, i get into FreeBSD boot manager, it is given me three choices: F1: DOS F2: FreeBSD F3: Linux Then, i select FreeBSD (F2)! Now, after BTX delay time to boot i time ESC, what brings me into the following prompt: disk2s2a:> I issue the reboot command, what cause some register values to be printed into the screen, and the message: System Halted. After the system halted message i come into the OS menu again: F1: DOS F2: FreeBSD F3: Linux I choose FreeBSD (F2), and this is what a get: Fatal Trap 22: FPU device not available while in kernel mode Instruction Pointer = 0x8:0c01a86fd Stack Pointer = 0x10:0xc024ff0c Frame Pointer = 0x10:0xc024ff1c Code Segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def 32, gran 1 Processor eflags = interrupt enabled, resume, IOPL=0 Current process = 0 () interrupt mask = net tty bio cam trap number = 22 panic: FPU device not available Automatic reboot in 15 seconds - ...... Do you wizard know what is happening ? PS: my uname -a output: FreeBSD etosha 3.3-STABLE FreeBSD 3.3-STABLE #1: Sun Nov 28 02:16:33 EDT 1999 root@etosha:/usr/src/sys/compile/ETOSHA i386 This is the only situation that causes FBSD to crash, on other way, nothing wrong happens, my system runs like a rock. Thanks a lot for your time and cooperation. -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 17:10:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 5DDD714C0F for ; Fri, 3 Dec 1999 17:10:26 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2iveard.dialup.mindspring.com [165.247.43.109]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id UAA21117; Fri, 3 Dec 1999 20:08:54 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id UAA00738; Fri, 3 Dec 1999 20:07:56 -0500 (EST) (envelope-from vsilyaev) Date: Fri, 3 Dec 1999 20:07:55 -0500 From: "Vladimir N. Silyaev" To: Julian Elischer Cc: "Vladimir N. Silyaev" , Andrew Kenneth Milton , wilko@yedi.iaf.nl, louie@TransSys.COM, FreeBSD-hackers@FreeBSD.ORG, groudier@club-internet.fr Subject: Re: vmnet (was: Linux ioctl not implemented error) Message-ID: <19991203200755.B578@jupiter.delta.ny.us> References: <19991202223604.B5379@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from julian@whistle.com on Thu, Dec 02, 1999 at 08:02:37PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 02, 1999 at 08:02:37PM -0800, Julian Elischer wrote: > > I don't know. At any case we are need provide the same API as linux > > vmnet provide, so we are need to implement it in the kernel module. > > But bochs use user level implementation. > > > > > It does have some limitations (can't send packets to the host/os) but > > > I don't know how complete the code is either. > > At this time I found the next message (it was posted more than 3 years > > ago at the freebsd-hackers mailing list): > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=661424+0+/usr/local/www/db/text/1996/freebsd-hackers/19961020.freebsd-hackers > > > > It's a very long URL but I hope that it's possible to retrieve it. At least > > you can search via its subject: Networking in PCEMU (1/2) > > > > I don't study this code, but it looking not so bad. > > check if you might not be able to use a netgraph module for this. My first think was about netgraph, but loopback ethernet driver, much closer to current linux vmnet implementation. I wrote to Serge Babkin (author of original posting), and he pointed to more fresh version of the driver: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/6668 -- Vladimir Silyaev. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 17:28:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id EDFB514A2D for ; Fri, 3 Dec 1999 17:28:09 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id UAA86340 for ; Fri, 3 Dec 1999 20:27:25 -0500 (EST) Date: Fri, 3 Dec 1999 20:27:24 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: freebsd-hackers@freebsd.org Subject: timespecmul() has no implemention? 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 my 3.3 system, defines timespecmul() (only if KERNEL is defined). However, 'grep -R timespecmul /usr/src/*' reveals absolutely no references to the symbol, not even an implementation. I must be missing something, because that is definately odd. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.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 Dec 3 17:39:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id D59E314C2E for ; Fri, 3 Dec 1999 17:39:22 -0800 (PST) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id SAA10544; Fri, 3 Dec 1999 18:38:36 -0700 (MST) Date: Fri, 3 Dec 1999 18:38:36 -0700 (MST) From: Nick Rogness To: Brian Dean Cc: freebsd-hackers@freebsd.org Subject: Re: natd is jumpy In-Reply-To: <199912032359.SAA58078@dean.pc.sas.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, 3 Dec 1999, Brian Dean wrote: > I use natd and a 56k phone connection to my ISP so that all my > computers can share one line. Is this an internal/external modem or a router connection to the outside? > > This all works fine, but I experience very noticeable jumpiness when > typing over a telnet connection to a remote system. Delays of 7-10 How many machines are on this setup and use it at the same time? > seconds between typing characters and them appearing on my screen are > not uncommon. If I rebuild my kernel without IPFIREWALL and IPDIVERT, > and disable natd and the firewall code, these delays go away so I am > assuming that it is natd/firewall/divert that is responsible for this > delay. Was there anyone sharing the bandwidth WHILE natd was configured and running? If so, try running NAT with noone else on sharing bandwidth and see if you get the same delays. Could it be possibly that when you rebooted, after the kernel rebuild, no other machines were able to use the same bandwidth because nat was turned off? Those delays could be normal if the other machines were surfing or using the majority of your bandwidth. Try turning natd on unplugging the 'inside' interface from the network and then run your tests. How 'far' away is the machine you are telneting to? 1,2,3 hops? Ping the host and see what times you are getting, both with NAT turned on and without. I run this setup with ISDN at home and never see delays on either diverted range (192.168.0.0/24) or my routeable subnet. Of course, I am running stable though. ******************************************************** Nick Rogness File not found... System Administrator Should I fake it (Y/N)? RapidNet, INC ******************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 17:42:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 5B1EF14C2E for ; Fri, 3 Dec 1999 17:42:51 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2iveard.dialup.mindspring.com [165.247.43.109]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id UAA27109; Fri, 3 Dec 1999 20:42:43 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id UAA28603; Fri, 3 Dec 1999 20:42:39 -0500 (EST) (envelope-from vsilyaev) Date: Fri, 3 Dec 1999 20:42:37 -0500 From: "Vladimir N. Silyaev" To: Wilko Bulte Cc: "Vladimir N. Silyaev" , louie@TransSys.COM, FreeBSD-hackers@FreeBSD.ORG, groudier@club-internet.fr Subject: Re: Linux ioctl not implemented error Message-ID: <19991203204236.B868@jupiter.delta.ny.us> References: <19991202160515.C536@jupiter.delta.ny.us> <199912032037.VAA05126@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912032037.VAA05126@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Fri, Dec 03, 1999 at 09:37:03PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 03, 1999 at 09:37:03PM +0100, Wilko Bulte wrote: > Hm, I think I also saw it fallover when I did this (sometimes, not always). I really don't have suggestion, what vmware doing, when it save configuration file. > Anyway, I'm more concerned with the CDrom drive right now. > [skipped] > Tried that. No luck :-( Try to run vmware from xterm, did you see messages about 'ioctl xxx not implemented' ? And dumb question, what version of port are you used, say something like ID from Makefile, or the value of VMMON_FREEBSD_VERSION, from the same Makefile. -- Vladimir Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 3 20:22:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 8DA2C152F8 for ; Fri, 3 Dec 1999 20:22:14 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id XAA89324 for ; Fri, 3 Dec 1999 23:19:00 -0500 (EST) Date: Fri, 3 Dec 1999 23:19:00 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: freebsd-hackers@freebsd.org Subject: oddities in sysctl -a 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've got a box running 3.2 dated Tue May 18 18:39:26 EDT 1999 (I'de upgrade but the 117 days uptime is putting the linux boxen in-house to shame :) ). Anyway, here are some excerpts from sysctl -a that caught my eye: kern.dumpdev: { major = 255, minor = -65281 } kern.ps_strings: -1077944336 kern.usrstack: -1077944320 vm.stats.sys.v_intr: -1837017521 vfs.cache.numchecks: -1447532299 Now, getting my hands dirty, I noticed that the entire vfs.cache sysctl tree is registered in sys/kern/vfs_cache.c using SYSCTL_INT, even though the variables are all declared as u_longs. However, being that I'm running on i386 and ints and longs are the same size, I don't think that accounts for what I'm seeing. The problem seems to be that values registered with the kernel sysctl interface cannot specify whether the values are signed or unsigned. Then when sysctl reads the oid_fmt specifier back out, it assumes integers are unsigned. My immediate inclination it to add new format identifiers (maybe "LU" and "IU" for the unsigned versions of long and integer respectively) and update sysctl to understand the new formats. But the source tells me that get-the-oid_fmt code should be axed. So the question is, should I bother fixing it? If so, I'll submit patches adding unsigned integer support along with ones fixing the int/long bug in vfs_cache when I get home. I'm looking forward to your input, Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.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 Dec 3 20:44:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by hub.freebsd.org (Postfix) with ESMTP id B80D615279; Fri, 3 Dec 1999 20:44:49 -0800 (PST) (envelope-from cyouse@paradox.nexuslabs.com) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id XAA83514; Fri, 3 Dec 1999 23:42:33 -0500 (EST) (envelope-from cyouse@paradox.nexuslabs.com) Date: Fri, 3 Dec 1999 23:42:32 -0500 (EST) From: Chuck Youse To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: tmpfs .. ? In-Reply-To: <199912030413.UAA04264@mass.cdrom.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 tmpfs may or may not be a UFS image stored in swap. I have a strong suspicion that it's not. MFS *is* a UFS image in memory (backed by swap, of course). As such, it is not nearly as efficient as it could be for /tmp purposes. Chuck On Thu, 2 Dec 1999, Mike Smith wrote: > > > > Has anyone toyed with the idea of implementing a swap-based filesystem > > similar to Sun's tmpfs? > > Like, oh, MFS maybe? > > Try 'man -k mfs'. > > -- > \\ 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 Fri Dec 3 21:32:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 7F74E14BDB for ; Fri, 3 Dec 1999 21:32:54 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id AAA90299 for ; Sat, 4 Dec 1999 00:31:11 -0500 (EST) Date: Sat, 4 Dec 1999 00:31:11 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: freebsd-hackers@FreeBSD.ORG Subject: Re: oddities in sysctl -a 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 > The problem seems to be that values registered with the kernel sysctl > interface cannot specify whether the values are signed or unsigned. Then > when sysctl reads the oid_fmt specifier back out, it assumes integers are > unsigned. ^^^^^^^^ Oops, I meant signed. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.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 Dec 3 23:57:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles530.castles.com [208.214.165.94]) by hub.freebsd.org (Postfix) with ESMTP id 75C6F15347 for ; Fri, 3 Dec 1999 23:57:48 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA00511; Fri, 3 Dec 1999 23:58:42 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912040758.XAA00511@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nate@mt.sri.com (Nate Williams) Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: tty level buffer overflows In-reply-to: Your message of "Fri, 03 Dec 1999 13:08:33 MST." <199912032008.NAA12138@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Dec 1999 23:58:42 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Dec 2 11:08:56 bifrost /kernel: sio0: 208 more tty-level buffer overflows (total 3356) > > > > is appearing on our ppp machine. What are tty-level buffer overflows? > > How can I fix this? What resource is running out? > > Is it safe to assume that this isn't happening on a laptop? At least > with the old code (I don't know about the new code), sio isn't using > fast interrupts when used by the laptop code. Er, you should read the sio(4) manpage too. tty-level buffer overflows have nothing to do with interrupt latency/execution time. -- \\ 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 Sat Dec 4 0:15:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 9607C1509D for ; Sat, 4 Dec 1999 00:15:42 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id DAA92597 for ; Sat, 4 Dec 1999 03:14:13 -0500 (EST) Date: Sat, 4 Dec 1999 03:14:13 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: freebsd-hackers@FreeBSD.ORG Subject: Re: oddities in sysctl -a 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 > > My immediate inclination it to add new format identifiers (maybe "LU" > and "IU" for the unsigned versions of long and integer respectively) and > update sysctl to understand the new formats. But the source tells me that > get-the-oid_fmt code should be axed. So the question is, should I bother > fixing it? > > If so, I'll submit patches adding unsigned integer support along with > ones fixing the int/long bug in vfs_cache when I get home. I'm looking > forward to your input, > > Kelly Replying to myself (it's lonely at 3:16am EST :) ). I've submitted patches to address the unsigned issue with sysctl: PR kern/15251. The PR details what all is affected. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.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 Sat Dec 4 1: 9: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 9177E1537B for ; Sat, 4 Dec 1999 01:08:50 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id JAA04241; Sat, 4 Dec 1999 09:46:00 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id JAA55819; Sat, 4 Dec 1999 09:42:17 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912040842.JAA55819@yedi.iaf.nl> Subject: Re: Linux ioctl not implemented error In-Reply-To: <19991203204236.B868@jupiter.delta.ny.us> from "Vladimir N. Silyaev" at "Dec 3, 1999 8:42:37 pm" To: vsilyaev@mindspring.com (Vladimir N. Silyaev) Date: Sat, 4 Dec 1999 09:42:17 +0100 (CET) Cc: vsilyaev@mindspring.com, louie@TransSys.COM, FreeBSD-hackers@FreeBSD.ORG, groudier@club-internet.fr X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.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 As Vladimir N. Silyaev wrote ... > On Fri, Dec 03, 1999 at 09:37:03PM +0100, Wilko Bulte wrote: > > Anyway, I'm more concerned with the CDrom drive right now. > > > [skipped] > > Tried that. No luck :-( > Try to run vmware from xterm, did you see messages about > 'ioctl xxx not implemented' ? No, what I get is: FreeBSD 4.0-CURRENT (P100) #3: Fri Dec 3 23:14:46 CET 1999 You have new mail. bash-2.03# vmware Dec 4 11:35:13 p100 /kernel: deb: /dev/vmmon: Module vmmon: registered with major=10 minor=165 tag=$Name: build-364 $ Dec 4 11:35:13 p100 /kernel: deb: /dev/vmmon: Module vmmon: registered with major=10 minor=165 tag=$Name: build-364 $ Dec 4 11:35:13 p100 /kernel: deb: /dev/vmmon: Module vmmon: initialized Dec 4 11:35:13 p100 /kernel: deb: /dev/vmmon: Module vmmon: initialized Warning: Name: scale Class: XmScale The specified scale value is greater than the maximum scale value. > And dumb question, what version of port are you used, say something > like ID from Makefile, or the value of VMMON_FREEBSD_VERSION, from > the same Makefile. # $vmFreeBSD: vmware/vmmon-only/freebsd/port/Makefile,v 1.5 1999/12/01 06:51:50 vsilyaev Exp $ # VERSION= 1.1.2 BUILD= 364 VMMON_FREEBSD_VERSION = 0.92 I hope this is the latest one (?). Thanks for all your help, Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Sat Dec 4 8:25:20 1999 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 438E4150ED for ; Sat, 4 Dec 1999 08:25:12 -0800 (PST) (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 LAA16468; Sat, 4 Dec 1999 11:25:16 -0500 (EST) Message-Id: Message-Id: X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 04 Dec 1999 11:20:49 -0500 To: Bill Fumerola From: Dennis Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) Cc: hackers@freebsd.org In-Reply-To: References: <199911220127.UAA28430@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 07:49 PM 11/21/99 -0500, you wrote: >On Mon, 22 Nov 1999, Dennis wrote: > >> The nightmare of instability of 3.x continues whilst the braintrust flogs >> away at 4.x. Its really a damn shame. And why is 3.x so much slower than >> 2.2.8? Will 4.0 be slower yet? > >Your vagueness and lack of evidence is astounding. The "evidence" is that 3.x chokes in conditions that 2.2.8 and LINUX dont on the exact same hardware. Sorry I dont have time to present a case to you. The number of customer i have that still run 2.2.8 is perhaps "circumstantial" evidence, but significant. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 8:37:15 1999 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 B99FB14BDD; Sat, 4 Dec 1999 08:37:07 -0800 (PST) (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 LAA16504; Sat, 4 Dec 1999 11:39:06 -0500 (EST) Message-Id: Message-Id: X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 04 Dec 1999 11:34:39 -0500 To: Mike Smith , Kris Kennaway From: Dennis Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199911220720.XAA06603@dingo.cdrom.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 At 11:20 PM 11/21/99 -0800, Mike Smith wrote: >> > His point was not a claim about performance, rather he was bringing into >> > question whether performance was improving with successive releases. >> >> Sounded very much to me like he was just vaguely griping about how slow >> and unstable newer versions of FreeBSD are compared to the good old days. >> Dennis will be able to clarify this for us all when he posts his benchmark >> specs. > >Dennis has been whining and griping about just about everything since >day one. You can't realistically consider that sort of activity on his >part as any sort of metric at all. There was a time that when someone reported a problem there was interest in finding out what it might be. Now you mock the person reporting it. I guess thats why everyone in the world is using linux. Its disheartening to realize that things apparently wont be getting much better. DB Emerging Technologies, Inc. http://www.etinc.com ISA and PCI T1/T3/V35/HSSI Cards for FreeBSD and LINUX Multiport T1 and HSSI/T3 UNIX-based Routers Bandwidth Management Standalone Systems Bandwidth Management software for LINUX and FreeBSD DSL Frame Relay Bridging over T1 and T3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 9:27:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 08F2714D3F for ; Sat, 4 Dec 1999 09:27:25 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id JAA11936; Sat, 4 Dec 1999 09:26:22 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id JAA22688; Sat, 4 Dec 1999 09:26:22 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA22238; Sat, 4 Dec 99 09:26:16 PST Message-Id: <38494EC8.296BB7C1@softweyr.com> Date: Sat, 04 Dec 1999 10:26:32 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Dennis Cc: hackers@freebsd.org Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: <199911220127.UAA28430@etinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > > At 07:49 PM 11/21/99 -0500, you wrote: > >On Mon, 22 Nov 1999, Dennis wrote: > > > >> The nightmare of instability of 3.x continues whilst the braintrust flogs > >> away at 4.x. Its really a damn shame. And why is 3.x so much slower than > >> 2.2.8? Will 4.0 be slower yet? > > > >Your vagueness and lack of evidence is astounding. > > The "evidence" is that 3.x chokes in conditions that 2.2.8 and LINUX dont > on the exact same hardware. Sorry I dont have time to present a case to > you. Exactly WHAT did you think you would accomplish with this message? Let me summarize what you've said to clarify: "FreeBSD 3.x sucks but I don't have time tell you where and how it sucks." My 3.3 machines run until I make world and reboot. They're not heavily loaded, just doing Gigabit ethernet testing and spidering the entire WWW. Did you come here asking for help, or just to throw bricks? -- "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 Sat Dec 4 9:30:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 76BB614D3F; Sat, 4 Dec 1999 09:30:34 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id JAA11956; Sat, 4 Dec 1999 09:28:34 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id JAA27922; Sat, 4 Dec 1999 09:28:33 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA22276; Sat, 4 Dec 99 09:28:30 PST Message-Id: <38494F52.3732AFF7@softweyr.com> Date: Sat, 04 Dec 1999 10:28:50 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Dennis Cc: Mike Smith , Kris Kennaway , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > > There was a time that when someone reported a problem there was interest in > finding out what it might be. Now you mock the person reporting it. I guess > thats why everyone in the world is using linux. Its disheartening to > realize that things apparently wont be getting much better. If you're insinuating that Linux is more stable and reliable than FreeBSD, you're absolutely and unequivocally wrong. Unless they're running your drivers. I'm perfectly willing to accept YOUR DRIVERS might be less unstable on Linux than FreeBSD. -- "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 Sat Dec 4 9:37:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CF0CF14D3F; Sat, 4 Dec 1999 09:37:08 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA10192; Sat, 4 Dec 1999 09:36:30 -0800 Date: Sat, 4 Dec 1999 09:36:30 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: tty level buffer overflows In-Reply-To: <199912040758.XAA00511@mass.cdrom.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 > Er, you should read the sio(4) manpage too. tty-level buffer overflows > have nothing to do with interrupt latency/execution time. You mean this: sio%d: tty-level buffer overflow. Problem in the application. Input has arrived faster than the given module could process it and some has been lost. Normally I might agree with this, but I use a tty line on a 150Mhz i386 to be a serial console for another freebsd box. This is a NS16550A with a 16 byte fifo. This systems is effectively idle except for this task. So, I'm running tip and I get constant tty-level buffer overflows at 9600 baud. I also have a 8 (well, 6 now since I moved and one of the system boards blew a backplane interface chip) 50 Mhz processor SS1000 running Solaris 2.6. It has 5 Zilog (2 byte fifo) 8530 chips running constant console sessions with regular large amounts of output (debugging and panicing other solaris systems for Fibre Channel work) via tip. There has never been a lost character that I can see except due to power outage. I am convinced to a moral certainty and beyond a reasonable doubt that if I had a single 50Mhz processor I'd have the same experience. Since the Solaris tip and the FreeBSD tip are essentially identical (both derive from BSD 4.X tip), I'd like to try and understand how this is an application problem :-). -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 9:55:16 1999 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 8850B14C37; Sat, 4 Dec 1999 09:55:05 -0800 (PST) (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 KAA28862; Sat, 4 Dec 1999 10:52:45 -0700 (MST) (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 KAA21366; Sat, 4 Dec 1999 10:52:45 -0700 (MST) Message-Id: <199912041752.KAA21366@harmony.village.org> To: mjacob@feral.com Subject: Re: tty level buffer overflows Cc: Mike Smith , hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 04 Dec 1999 09:36:30 PST." References: Date: Sat, 04 Dec 1999 10:52:45 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Matthew Jacob writes: : Normally I might agree with this, but I use a tty line on a 150Mhz i386 to : be a serial console for another freebsd box. This is a NS16550A with a 16 : byte fifo. This systems is effectively idle except for this task. So, I'm : running tip and I get constant tty-level buffer overflows at 9600 baud. In the past, something like TTYHOG has been used to arbitrate this, but I can't seem to find the right magic bits here. Pointers? I am seeing this at 115200 on my 486DX2-66 for my ISDN line. NS16550A uarts. Everything else seems cool. I am suspecting a subtle bug because it only happens now and again, not all the time, or only when large xfers are happening. I'd like to know more about this resource shortage so I might do something about it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 9:58:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0168314C28 for ; Sat, 4 Dec 1999 09:58:51 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA10272; Sat, 4 Dec 1999 09:59:35 -0800 Date: Sat, 4 Dec 1999 09:59:35 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: tty level buffer overflows In-Reply-To: <199912041752.KAA21366@harmony.village.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 > In message Matthew Jacob writes: > : Normally I might agree with this, but I use a tty line on a 150Mhz i386 to > : be a serial console for another freebsd box. This is a NS16550A with a 16 > : byte fifo. This systems is effectively idle except for this task. So, I'm > : running tip and I get constant tty-level buffer overflows at 9600 baud. > > In the past, something like TTYHOG has been used to arbitrate this, > but I can't seem to find the right magic bits here. Pointers? Err, umm, *cough*... it's been over ten years since I did any tty line discipline work, so I don't remember... :-(. > I am seeing this at 115200 on my 486DX2-66 for my ISDN line. NS16550A > uarts. Everything else seems cool. I am suspecting a subtle bug > because it only happens now and again, not all the time, or only when > large xfers are happening. I'd like to know more about this resource > shortage so I might do something about it. That's one I'd like to know as well. Sigh- I think somebody (I'm booked) will have to go looksee. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 10:26:52 1999 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 BFA2915118; Sat, 4 Dec 1999 10:26:48 -0800 (PST) (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 NAA16812; Sat, 4 Dec 1999 13:29:21 -0500 (EST) Message-Id: <199912041829.NAA16812@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 04 Dec 1999 13:24:53 -0500 To: Wes Peters From: Dennis Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) Cc: Mike Smith , Kris Kennaway , freebsd-hackers@FreeBSD.ORG In-Reply-To: <38494F52.3732AFF7@softweyr.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 At 10:28 AM 12/4/99 -0700, Wes Peters wrote: >Dennis wrote: >> >> There was a time that when someone reported a problem there was interest in >> finding out what it might be. Now you mock the person reporting it. I guess >> thats why everyone in the world is using linux. Its disheartening to >> realize that things apparently wont be getting much better. > >If you're insinuating that Linux is more stable and reliable than FreeBSD, >you're absolutely and unequivocally wrong. All Im saying is that more people use linux because its getting better and they are responsive to their community. Im comparing Freebsd 2.2.8 to 3.3 and citing that there are more problems with 3.3 than 2.2.8 Linux 2.2 was a vast improvement over 2.0 whilst that clearly isnt the case here. > Unless they're running your drivers. I'm perfectly willing to accept YOUR DRIVERS might be less unstable on Linux than FreeBSD. "less unstable". Is that a technical term? If you are going to make totally ignorant statements at least try to get the semantics right. DB Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 11:43:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foo.sics.se (foo.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id F268015062 for ; Sat, 4 Dec 1999 11:43:38 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id UAA39818; Sat, 4 Dec 1999 20:42:37 +0100 (CET) (envelope-from assar) To: Garance A Drosihn Cc: Wes Peters , Randell Jesup , Robert Watson , freebsd-hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3845712D.F4D51A70@softweyr.com> From: Assar Westerlund Date: 04 Dec 1999 20:42:37 +0100 In-Reply-To: Garance A Drosihn's message of "Thu, 2 Dec 1999 21:13:56 -0500" Message-ID: <5lwvqu7as2.fsf@foo.sics.se> Lines: 21 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garance A Drosihn writes: > In the case of AFS, I think you'd want to expand the size of st_dev. > All files in an AFS volume are "one device", I would think. If the > "device" is gone (ie, the volume is not mounted), then all files in > that "device" (volume) will not be available. I'm confused. Did you mean `st_ino' there? I agree that you want to see the whole AFS space as a single device. > I don't know what would be best for other distributed file systems, > though. Maybe both variables would have to increase in size. Maybe > we should start by creating an "fcompare()" routine, which you'd > pass two file descriptors to and it would say if they're the same > file. Initially that routine could just do two fstat()'s, and > compare st_dev and st_ino. We could then expand it to do better > comparisons for other file-systems. In solaris there's a vnode operation vop_cmp that does exactly that. But it's not exported to userland in any way. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 12:18:35 1999 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 A070715163 for ; Sat, 4 Dec 1999 12:18:27 -0800 (PST) (envelope-from robert@cyrus.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 PAA02056; Sat, 4 Dec 1999 15:17:30 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Sat, 4 Dec 1999 15:17:29 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Assar Westerlund Cc: Garance A Drosihn , Wes Peters , Randell Jesup , freebsd-hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? In-Reply-To: <5lwvqu7as2.fsf@foo.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 4 Dec 1999, Assar Westerlund wrote: > Garance A Drosihn writes: > > In the case of AFS, I think you'd want to expand the size of st_dev. > > All files in an AFS volume are "one device", I would think. If the > > "device" is gone (ie, the volume is not mounted), then all files in > > that "device" (volume) will not be available. > > I'm confused. Did you mean `st_ino' there? I agree that you want to > see the whole AFS space as a single device. I agree. > > I don't know what would be best for other distributed file systems, > > though. Maybe both variables would have to increase in size. Maybe > > we should start by creating an "fcompare()" routine, which you'd > > pass two file descriptors to and it would say if they're the same > > file. Initially that routine could just do two fstat()'s, and > > compare st_dev and st_ino. We could then expand it to do better > > comparisons for other file-systems. > > In solaris there's a vnode operation vop_cmp that does exactly that. > But it's not exported to userland in any way. The suggested fcompare() would be a much better way for tar (and other programs with a "samefile" requirement) to identify objects that are the same, rather than relying on the device and inode numbers, which are fairly artificial constructions on a number of file systems--backing it with a vop_cmp(struct vnode *vp1, struct vnode *vp2, ...) would probably be the way to go--you'd probably ask the first vnode (and hence its supporting file system) if it was the same as the second vnode, so as to try and avoid aliasing issues (?). This places responsibility for maintaining information about file system objects back in the hands of the file system, where it probably should have been in the first place. The inode number in stat + posix semantics requirements essentially consist of requiring an unlimited size cache with no callback mechanism :-). They also resemble requiring an entire second namespace for each file system -- the vnode-happy namei() lookup namespace, and also an inode namespace. It's arguable that only the string-based namespace is broadly used, and consistent with the generalized VFS file system concept. The inode-number in stat is a hanger-on from the days of only UFS/NFS, and inappropriate in a VFS. That isn't to say that there should be a vop_get_fsspecific(struct *vp, struct something *something) to retrieve this for processes interested, just that it's not supposed to have cross-fs guarantees. 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 Sat Dec 4 12:31: 8 1999 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 F066C14C34 for ; Sat, 4 Dec 1999 12:31:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA56701; Sat, 4 Dec 1999 12:29:37 -0800 (PST) (envelope-from dillon) Date: Sat, 4 Dec 1999 12:29:37 -0800 (PST) From: Matthew Dillon Message-Id: <199912042029.MAA56701@apollo.backplane.com> To: Chuck Youse Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: tmpfs .. ? References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Has anyone toyed with the idea of implementing a swap-based filesystem :similar to Sun's tmpfs? : :Chuck Youse I did it a couple of months ago. You simply use the VN device and tell it to use swap as backing store, then newfs up a UFS filesystem on it. You have the option to have it dynamically allocate and deallocate swap, or you can force it to pre-reserve swap. See the 'vnconfig' man page and the -S option and the '-s reserve' option. This is for -CURRENT only. Generally speaking this isn't going to be as efficient as a real tmpfs due to the update daemon syncing all filesystems every so often. But if you pre-reserve the swap it *will* be just as efficient as a normal filesystem. In fact, if you have multiple swap partitions your tmpfs will wind up being interleaved and will have even better performance. pre-reservation also gives you the ability to recover the filesystem after a crash though for obvious reasons it can be problematic to depend on this ability. The big difference between MFS and VN is that MFS simulates a 'disk' by using a special processes VM space, which means that disk blocks tend to end up in memory twice - in the VM cache, and in the VM space. The VN device implements the disk directly on a file or swap and does not have the double-caching problem. MFS will tend to overload the VM system if you use it to accomodate large files. VN operates more like a normal disk, especially (in performance terms) when you use pre-reserved swap as backing store. vnconfig -e -s labels,reserve -S 100m /dev/vn0 disklabel -r -w vn0 auto newfs -i 4096 /dev/rvn0c tunefs -n enable /dev/rvn0c mount /dev/vn0c /usr/obj -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 Sat Dec 4 12:31:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 77C7D15295; Sat, 4 Dec 1999 12:31:07 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id OAA86770; Sat, 4 Dec 1999 14:29:42 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Sat, 4 Dec 1999 14:29:42 -0600 (CST) From: David Scheidt To: Dennis Cc: Wes Peters , Mike Smith , Kris Kennaway , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) In-Reply-To: <199912041829.NAA16812@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 Sat, 4 Dec 1999, Dennis wrote: > At 10:28 AM 12/4/99 -0700, Wes Peters wrote: > > > Unless they're running your drivers. I'm perfectly willing to accept YOUR > DRIVERS might be less unstable on Linux than FreeBSD. > > "less unstable". Is that a technical term? With a large number of the systems I have dealt with this is the perfectly correct way to describe them. If you are going to make totally > ignorant statements at least try to get the semantics right. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 12:49:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 6A21E14A2A for ; Sat, 4 Dec 1999 12:49:42 -0800 (PST) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id PAA05671 for ; Sat, 4 Dec 1999 15:47:39 -0500 (EST) Reply-To: Randell Jesup To: freebsd-hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3845712D.F4D51A70@softweyr.com> <5lwvqu7as2.fsf@foo.sics.se> From: Randell Jesup Date: 04 Dec 1999 15:49:59 -0500 In-Reply-To: Assar Westerlund's message of "04 Dec 1999 20:42:37 +0100" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Assar Westerlund writes: >> we should start by creating an "fcompare()" routine, which you'd >> pass two file descriptors to and it would say if they're the same >> file. Initially that routine could just do two fstat()'s, and >> compare st_dev and st_ino. We could then expand it to do better >> comparisons for other file-systems. > >In solaris there's a vnode operation vop_cmp that does exactly that. >But it's not exported to userland in any way. Sounds like what we'd want to build it upon. If the FS doesn't support it, use st_dev/st_ino. The real problem is getting people to switch. -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 13:22: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 9D20A151A7; Sat, 4 Dec 1999 13:21:59 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA41268; Sat, 4 Dec 1999 13:21:13 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Dennis Cc: Mike Smith , Kris Kennaway , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) In-reply-to: Your message of "Sat, 04 Dec 1999 11:34:39 EST." Date: Sat, 04 Dec 1999 13:21:13 -0800 Message-ID: <41264.944342473@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There was a time that when someone reported a problem there was interest in > finding out what it might be. Bah, this is a shameless attempt to inflame emotions as a substitute for having an actual logical point and you know it. Save it for the presidential debates! There is ALWAYS interest in finding out what a problem is when it's reported in such a way that the effort is worth the potential reward. Having someone walk up and say, in effect, "Dudes, your system is broken. Fix it!" is a content-free statement and does not qualify as reasonable reporting by any stretch of the imagination, so it's not worth any effort at all. There are plenty of more substantive bug reports that require our attention. What's more, you know this full well yourself having been on the sticky end of tech support more than once and you're just being deliberately annoying and difficult now for reasons best known to yourself. It's disheartening to realize that even people who know better can still behave as Dennis has been behaving in this sad excuse for constructive feedback so far. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 13:46:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles545.castles.com [208.214.165.109]) by hub.freebsd.org (Postfix) with ESMTP id 9D77C15157; Sat, 4 Dec 1999 13:46:44 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA04790; Sat, 4 Dec 1999 13:48:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912042148.NAA04790@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: Mike Smith , Kris Kennaway , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) In-reply-to: Your message of "Sat, 04 Dec 1999 11:34:39 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Dec 1999 13:48:08 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 11:20 PM 11/21/99 -0800, Mike Smith wrote: > >> > His point was not a claim about performance, rather he was bringing into > >> > question whether performance was improving with successive releases. > >> > >> Sounded very much to me like he was just vaguely griping about how slow > >> and unstable newer versions of FreeBSD are compared to the good old days. > >> Dennis will be able to clarify this for us all when he posts his benchmark > >> specs. > > > >Dennis has been whining and griping about just about everything since > >day one. You can't realistically consider that sort of activity on his > >part as any sort of metric at all. > > There was a time that when someone reported a problem there was interest in > finding out what it might be. Now you mock the person reporting it. I guess > thats why everyone in the world is using linux. Its disheartening to > realize that things apparently wont be getting much better. Actually, you may recall that when you first brought this up this time around, I (and others) _did_ try to find out what you were actually unhappy about. Spectators will note that you haven't actually given us anything useful to work with; no PR numbers, no code fragments, in fact nothing whatsoever of any substance. Thus, I feel quite comfortable in reassuring other developers that your hysterical complaints shouldn't be taken as a cause for alarm. If and when you have something that actually looks like it might be enough evidence for us to work with, we'll take you seriously. -- \\ 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 Sat Dec 4 13:51:31 1999 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 A42AF14C1F; Sat, 4 Dec 1999 13:51:27 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA57545; Sat, 4 Dec 1999 13:49:53 -0800 (PST) (envelope-from dillon) Date: Sat, 4 Dec 1999 13:49:53 -0800 (PST) From: Matthew Dillon Message-Id: <199912042149.NAA57545@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: Dennis , Mike Smith , Kris Kennaway , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: <41264.944342473@zippy.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> There was a time that when someone reported a problem there was interest in :> finding out what it might be. : :Bah, this is a shameless attempt to inflame emotions as a substitute :for having an actual logical point and you know it. Save it for the :presidential debates! : :There is ALWAYS interest in finding out what a problem is when it's :reported in such a way that the effort is worth the potential reward. :Having someone walk up and say, in effect, "Dudes, your system is :broken. Fix it!" is a content-free statement and does not qualify as This is complete bullshit. Read through the thread from day 1... starting around Nov 20th. Dennis started out posting a bug report. A very reasonable bug report whos only fault might be that it was lacking in detail. The very first response was a snide, unhelpful "Not enough information" which did not even explain what type of information was needed, so Dennis's second response, again a very reasonable "what kind of information is needed?" was obvious. The later responses, mainly by existing FreeBSD people, was to essentially roast him over the coals. By the third message the thread turned into an emotional mush, and *NONE* of it was Dennis's doing. Dennis is fully within his rights to become annoyed at that. You people (though not mainly Jordan) essentially roasted him over the coals unrelentingly until he got angry enough to post something a tad over the top and then you people (including Jordan) roasted him for that as well. If you want an example of the *PROPER* way to deal with a bug report containing insufficient information, look at some of my past responses to bug reports related to VM or NFS that contained insufficient information. The proper way to go about it is to say "Well, I can't figure out anything from that, perhaps if you do A, B, and C it may give us enough information to work on". --- Now, with all that said, going back to Dennis's original bug report posted Nov 20th, I would like to note that I had a similar problem with PCI overloading for a few days what, a month ago? When one of the Adaptec drivers was temporarily changed to turn off a special PCI DMA mode which the author had no documentation on, causing the Adaptec to blow up when the 100BaseTX ethernet was loaded down. That particular bug was fixed within a few days, but the author noted that the special PCI mode required to avoid the lockup seemed only to exist in a few adaptec cards and he wasn't sure what the other cards did. But it points to a possible line of direction in regards to locating the current bug. It's possible that another similar bug has been found, and if the conversation had not degraded into a flame war perhaps it would be fixed by now. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 13:53: 3 1999 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 EEEA615394; Sat, 4 Dec 1999 13:52:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA57575; Sat, 4 Dec 1999 13:52:58 -0800 (PST) (envelope-from dillon) Date: Sat, 4 Dec 1999 13:52:58 -0800 (PST) From: Matthew Dillon Message-Id: <199912042152.NAA57575@apollo.backplane.com> To: Mike Smith Cc: Dennis , Mike Smith , Kris Kennaway , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: <199912042148.NAA04790@mass.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Actually, you may recall that when you first brought this up this time :around, I (and others) _did_ try to find out what you were actually :unhappy about. : :Spectators will note that you haven't actually given us anything useful :to work with; no PR numbers, no code fragments, in fact nothing :whatsoever of any substance. : :Thus, I feel quite comfortable in reassuring other developers that your :hysterical complaints shouldn't be taken as a cause for alarm. If and :when you have something that actually looks like it might be enough :evidence for us to work with, we'll take you seriously. It wasn't hysterical until other people (not the original poster) made it that way. Frankly, Mike, your initial response to Dennis's initial posting left a hellofalot to be desired. Simply stating, in a snide way, that there was not nearly enough information is not helpful if you do not describe the type of information you think would be useful. Presumably the original poster (Dennis) did not know exactly what kind of information was needed (that he could also supply, since he is (and said he was) not a kernel hacker). Dennis made this quite clear in his initial posting and got nothing but hell from you. -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 Sat Dec 4 14:47:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles545.castles.com [208.214.165.109]) by hub.freebsd.org (Postfix) with ESMTP id E83C01534F for ; Sat, 4 Dec 1999 14:47:29 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA05083; Sat, 4 Dec 1999 14:47:32 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912042247.OAA05083@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: hackers@freebsd.org Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) In-reply-to: Your message of "Sat, 04 Dec 1999 13:52:58 PST." <199912042152.NAA57575@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Dec 1999 14:47:32 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :Actually, you may recall that when you first brought this up this time > :around, I (and others) _did_ try to find out what you were actually > :unhappy about. > : > :Spectators will note that you haven't actually given us anything useful > :to work with; no PR numbers, no code fragments, in fact nothing > :whatsoever of any substance. > : > :Thus, I feel quite comfortable in reassuring other developers that your > :hysterical complaints shouldn't be taken as a cause for alarm. If and > :when you have something that actually looks like it might be enough > :evidence for us to work with, we'll take you seriously. > > It wasn't hysterical until other people (not the original poster) made it > that way. Frankly, Mike, your initial response to Dennis's initial > posting left a hellofalot to be desired. Simply stating, in a snide way, > that there was not nearly enough information is not helpful if you do not > describe the type of information you think would be useful. Presumably > the original poster (Dennis) did not know exactly what kind of information > was needed (that he could also supply, since he is (and said he was) not > a kernel hacker). Dennis made this quite clear in his initial posting > and got nothing but hell from you. Since you're going to attack me in public over this, I'm going to state my position on this once and then let it rest. - You're welcome to project what you like into you personal interpretation of my response to Dennis. It's unreasonable to expect that what you think I meant is what was actually meant (this is basic communications theory). You also lack most of the context for this interaction, some of which I attempted to convey in the message you've quoted above. - Dennis is a principal in a company which manufactures communications peripherals and writes driver software for them. It's not unreasonable to expect him to have some sort of idea, or access to an in-house idea, about how to go about diagnosing a problem like this. It's also not unreasonable to expect that, being involved in a development environment, that he would have some experience in reporting problems in a fashion that would allow action to be taken to resolve them. - We have been dealing with Dennis for many years. He has persisted in his defective communications style despite many well-meaning attempts to encourage him to improve. At this point in time, he has worn out his welcome with many of us and if anything it's a credit to our stamina that we still even listen to him anymore. - Irregardless of your initial presumptions concerning Dennis' ability, the fact remains that he failed to follow through on the encouragement to provide more information, and thus (again) we were unable to actually provide him with any more assistance. Now he comes back a few weeks later to complain again, still not providing any more information. Which side is falling down in this relationship? -- \\ 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 Sat Dec 4 14:48: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 247F415019 for ; Sat, 4 Dec 1999 14:47:48 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id OAA17507; Sat, 4 Dec 1999 14:47:08 -0800 (PST) To: Brian Dean Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: natd is jumpy In-reply-to: Your message of Fri, 03 Dec 1999 18:59:40 -0500. <199912032359.SAA58078@dean.pc.sas.com> Date: Sat, 04 Dec 1999 14:47:08 -0800 Message-ID: <17505.944347628@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912032359.SAA58078@dean.pc.sas.com>, you wrote: >Hi, > >I posted this on -questions about five days ago and haven't received >any hints or suggestions. Does anyone here have any ideas? > >I use natd and a 56k phone connection to my ISP so that all my >computers can share one line. > >This all works fine, but I experience very noticeable jumpiness when >typing over a telnet connection to a remote system. Delays of 7-10 >seconds between typing characters and them appearing on my screen are >not uncommon. If I rebuild my kernel without IPFIREWALL and IPDIVERT, >and disable natd and the firewall code, these delays go away so I am >assuming that it is natd/firewall/divert that is responsible for this >delay. I think that is a bad assumption. I'm running FreeBSD 3.3 with IPFIREWALL, IPDIVERT, and natd also over a 56k modem, and I _never_ have seen the kind of slow echo effect you are speaking of, except on very rare occasions when _somebody_ between me and whichever machine I'm talking to happens to be dropping a lot of packets. And obviously, in those cases, it ain't the fault of my FreeBSD box. >Is there a parameter or anything that I can tune to eliminate or >reduce this affect? Maybe change your ISP (?) But seriously, next time it happens, try doing some pings to the remote system that you are telnetting to. Look for dropped packets. Doing a couple of traceroutes to the remote system from your location might pro- vide some useful info also. >I am running FreeBSD -current as of 11/21 and my firewall is set up as >"open". That just means that you have minimal filtering rules in place. I have a *lot* of filtering rules in place on my system, but the kernel- level divert and firewall stuff still seems to run like a bat outta hell. At least that's my general impression. I really didn't notice any response degradation whatsoever when I when from an old kernel that was built without IPFIREWALL and IPDIVERT to a new one that was built with these things enabled. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 15:41:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foo.sics.se (assail.s3.kth.se [130.237.43.29]) by hub.freebsd.org (Postfix) with ESMTP id E09FF154D1 for ; Sat, 4 Dec 1999 15:41:27 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id AAA40156; Sun, 5 Dec 1999 00:40:16 +0100 (CET) (envelope-from assar) To: Randell Jesup Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3845712D.F4D51A70@softweyr.com> <5lwvqu7as2.fsf@foo.sics.se> From: Assar Westerlund Date: 05 Dec 1999 00:40:14 +0100 In-Reply-To: Randell Jesup's message of "04 Dec 1999 15:49:59 -0500" Message-ID: <5laenqz34x.fsf@foo.sics.se> Lines: 39 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randell Jesup writes: > Sounds like what we'd want to build it upon. If the FS doesn't > support it, use st_dev/st_ino. Actually, since it's in the kernel, the default implementation of the vnode operation might be: int vop_default_cmp (struct vnode *v1, struct vnode *v2) { return v1 == v2; } Or did you mean a fallback in the library function for when the kernel doesn't provide the fdcmp (or whatever) system call? That could be something like: /* * 1 if fd1 and fd2 point to the same file. * 0 if they are not * -1 if we can't compare them */ int fdcmp (int fd1, int fd2) { struct stat sb1, sb2; if(fstat(fd1, &sb1) < 0 || fstat(fd2, &sb2) < 0) return -1; return sb1.st_dev == sb2.st_dev && sb1.st_ino == sb2.st_ino; } > The real problem is getting people to switch. You mean application programs? Sure, but the only thing we can do about that is implementing support for it, right? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 15:47:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 8443714C2E for ; Sat, 4 Dec 1999 15:47:21 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id PAA18064 for ; Sat, 4 Dec 1999 15:44:49 -0800 (PST) To: freebsd-hackers@FreeBSD.ORG Subject: Re: tmpfs .. ? In-reply-to: Your message of Sat, 04 Dec 1999 12:29:37 -0800. <199912042029.MAA56701@apollo.backplane.com> Date: Sat, 04 Dec 1999 15:44:49 -0800 Message-ID: <18062.944351089@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912042029.MAA56701@apollo.backplane.com>, Matthew Dillon wrote: > >:Has anyone toyed with the idea of implementing a swap-based filesystem >:similar to Sun's tmpfs? >: >:Chuck Youse > > I did it a couple of months ago. You simply use the VN device and > tell it to use swap as backing store, then newfs up a UFS filesystem > on it. You have the option to have it dynamically allocate and > deallocate swap, or you can force it to pre-reserve swap. See the > 'vnconfig' man page and the -S option and the '-s reserve' option. > > This is for -CURRENT only. > > Generally speaking this isn't going to be as efficient as a real tmpfs Please excuse my ignorance, but what is it, exactly, that you are defining as a ``real tmpfs'' here? > due to the update daemon syncing all filesystems every so often. > But if you pre-reserve the swap it *will* be just as efficient as a > normal filesystem. In fact, if you have multiple swap partitions > your tmpfs will wind up being interleaved and will have even better > performance. pre-reservation also gives you the ability to recover > the filesystem after a crash though for obvious reasons it can be > problematic to depend on this ability. Again, please excuse my ignorance, but what ``obvious reasons'' are those? P.S. I have a definite interest in this sort of thing, especially if the data stored was made to be persistant across reboots and/or crashes. Specifically, I'm planning a large mail server... which will use Sendmail... and I'd really like to allocate the Sendmail queue files... which typically have a rather short lifespan... on/in some sort of filesystem (e.g. an mfs or else this VN thing you are talking about) that would tend to give petter performance than just using an ordinary disk-based filesystem. But of course, in this sort of an application, it would be Really Nice if the filesystem in question would persist across most rebbots and crashes. (I asked about MFS persistance awhile back on -questions, but I don't think that anybody groked _why_ I might want that. Now perhaps I have made my intentions more clear.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 15:53: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id BF48015303; Sat, 4 Dec 1999 15:52:56 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id PAA72350; Sat, 4 Dec 1999 15:51:30 -0800 (PST) From: Archie Cobbs Message-Id: <199912042351.PAA72350@bubba.whistle.com> Subject: Patch for 'ipfw tee' In-Reply-To: <199912042306.PAA74389@freefall.freebsd.org> from Chris Piazza at "Dec 4, 1999 03:06:48 pm" To: cvs-committers@FreeBSD.org, freebsd-hackers@FreeBSD.org Date: Sat, 4 Dec 1999 15:51:30 -0800 (PST) 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 Anyone particularly interested in kernel ipfw and/or divert, please review this patch, which implements 'ipfw tee' and cleans up a few things: ftp://ftp.whistle.com/pub/archie/misc/tee.patch If there are no objections I'll commit this in a couple of days. Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 17:19:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 5216414E9D; Sat, 4 Dec 1999 17:19:50 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id RAA12760; Sat, 4 Dec 1999 17:18:18 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id RAA05180; Sat, 4 Dec 1999 17:18:17 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA29563; Sat, 4 Dec 99 17:18:14 PST Message-Id: <3849BD69.275BA9D6@softweyr.com> Date: Sat, 04 Dec 1999 18:18:33 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Dennis Cc: Mike Smith , Kris Kennaway , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: <199912041829.NAA16812@etinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > > At 10:28 AM 12/4/99 -0700, Wes Peters wrote: > > > >If you're insinuating that Linux is more stable and reliable than FreeBSD, > >you're absolutely and unequivocally wrong. > > All Im saying is that more people use linux because its getting better and > they are responsive to their community. Im comparing Freebsd 2.2.8 to 3.3 > and citing that there are more problems with 3.3 than 2.2.8 Linux 2.2 was a > vast improvement over 2.0 whilst that clearly isnt the case here. But it clearly is the case to the vast majority of FreeBSD users, and your snotty remarks aren't helping. > > Unless they're running your drivers. I'm perfectly willing to accept YOUR > > DRIVERS might be less unstable on Linux than FreeBSD. > > "less unstable". Is that a technical term? If you are going to make totally > ignorant statements at least try to get the semantics right. I was politely mealy-mouthing my way around an insinuation that it is your driver and not FreeBSD 3.x that sucks. -- "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 Sat Dec 4 17:24:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 458461535C; Sat, 4 Dec 1999 17:24:08 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id RAA12764; Sat, 4 Dec 1999 17:21:58 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id RAA05205; Sat, 4 Dec 1999 17:21:57 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA29611; Sat, 4 Dec 99 17:21:54 PST Message-Id: <3849BE44.EF52448C@softweyr.com> Date: Sat, 04 Dec 1999 18:22:12 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Matthew Dillon Cc: "Jordan K. Hubbard" , Dennis , Mike Smith , Kris Kennaway , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: <41264.944342473@zippy.cdrom.com> <199912042149.NAA57545@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > : > :> There was a time that when someone reported a problem there was interest in > :> finding out what it might be. > : > :There is ALWAYS interest in finding out what a problem is when it's > :reported in such a way that the effort is worth the potential reward. > :Having someone walk up and say, in effect, "Dudes, your system is > :broken. Fix it!" is a content-free statement and does not qualify as > > This is complete bullshit. Read through the thread from day 1... > starting around Nov 20th. Matt, this thread is a LOT older than Nov 20th, it runs for YEARS. Dennis said the same things about 2.2 vs. 2.1.5 at the very least. A few years later when he finally got his driver sorted out for 2.2, it became the best thing since sliced bread and now 3.x is nothing but crap. -- "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 Sat Dec 4 18:33:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id A96F1153AB; Sat, 4 Dec 1999 18:33:49 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 9ADFE1CD473; Sat, 4 Dec 1999 18:33:49 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 4 Dec 1999 18:33:49 -0800 (PST) From: Kris Kennaway To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) In-Reply-To: <199912042149.NAA57545@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 4 Dec 1999, Matthew Dillon wrote: > The later responses, mainly by existing FreeBSD people, was to > essentially roast him over the coals. By the third message the thread > turned into an emotional mush, and *NONE* of it was Dennis's doing. Since I'm one of the existing FreeBSD people you're probably referring to here, let me remind you of the actual content: Dennis said the following: > The nightmare of instability of 3.x continues whilst the braintrust > flogs away at 4.x. Its really a damn shame. And why is 3.x so much > slower than 2.2.8? Will 4.0 be slower yet? Note the apparently belligerent tone, including use of emotionally charged language and sudden change of topic. Now, when someone makes a wild, authoritative yet unsupported statement like this, I think it's only reasonable to ask for some evidence. If I sounded facetious when I said: > Dennis will be able to clarify this for us all when he posts his > benchmark specs. it's because I hardly expected him to do so (so far, I've been correct). However, if Dennis, or anyone else, can provide some hard data about the relative speed of 2.x vs 3.x (I haven't seen any comparisons like this) then there'll at least be something to work with. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 19:58:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 28A17153C1; Sat, 4 Dec 1999 19:58:07 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id WAA00567; Sat, 4 Dec 1999 22:57:52 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Sat, 4 Dec 1999 22:57:51 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Archie Cobbs Cc: cvs-committers@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: Patch for 'ipfw tee' In-Reply-To: <199912042351.PAA72350@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 4 Dec 1999, Archie Cobbs wrote: > Anyone particularly interested in kernel ipfw and/or divert, please review > this patch, which implements 'ipfw tee' and cleans up a few things: > > ftp://ftp.whistle.com/pub/archie/misc/tee.patch > > If there are no objections I'll commit this in a couple of days. I saw it when you mailed it to me, and I do not object at all :) Sorry for not saying anything sooner, but I have pretty big connectivity problems. > > Thanks, > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com -- 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 Sat Dec 4 20:11:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 77FED153C7 for ; Sat, 4 Dec 1999 20:11:36 -0800 (PST) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id XAA20346; Sat, 4 Dec 1999 23:10:35 -0500 (EST) Reply-To: Randell Jesup To: Assar Westerlund Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3845712D.F4D51A70@softweyr.com> <5lwvqu7as2.fsf@foo.sics.se> <5laenqz34x.fsf@foo.sics.se> From: Randell Jesup Date: 04 Dec 1999 23:12:54 -0500 In-Reply-To: Assar Westerlund's message of "05 Dec 1999 00:40:14 +0100" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Assar Westerlund writes: >Randell Jesup writes: >> Sounds like what we'd want to build it upon. If the FS doesn't >> support it, use st_dev/st_ino. > >Actually, since it's in the kernel, the default implementation of the >vnode operation might be: > >int >vop_default_cmp (struct vnode *v1, struct vnode *v2) >{ > return v1 == v2; >} Sure, depending on what's in a vnode (I haven't looked). I was really thinking of the kernel; I don't know how much of the interior filesystem structure is exposed to the kernel; I was assuming that vnodes are something that's opaque (or mostly so) to the kernel, and are interpreted by the filesystem that created them. >Or did you mean a fallback in the library function for when the kernel >doesn't provide the fdcmp (or whatever) system call? That could be >something like: That's what I was thinking of, partially. It makes binaries more transportable, and source if we can get Linux/etc to add it to their libraries. >> The real problem is getting people to switch. > >You mean application programs? Sure, but the only thing we can do >about that is implementing support for it, right? Right; that's where to start. -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 20:22:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foo.sics.se (assail.s3.kth.se [130.237.43.29]) by hub.freebsd.org (Postfix) with ESMTP id E137515237 for ; Sat, 4 Dec 1999 20:22:44 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id FAA54986; Sun, 5 Dec 1999 05:21:38 +0100 (CET) (envelope-from assar) To: Randell Jesup Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? References: <3845712D.F4D51A70@softweyr.com> <5lwvqu7as2.fsf@foo.sics.se> <5laenqz34x.fsf@foo.sics.se> From: Assar Westerlund Date: 05 Dec 1999 05:21:37 +0100 In-Reply-To: Randell Jesup's message of "04 Dec 1999 23:12:54 -0500" Message-ID: <5l1z92m2zy.fsf@foo.sics.se> Lines: 16 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randell Jesup writes: > Sure, depending on what's in a vnode (I haven't looked). Note that I was comparing the `pointers' and not the contents. The way the VFS works you only keep one vnode for every file. > That's what I was thinking of, partially. It makes binaries > more transportable, and source if we can get Linux/etc to add it to > their libraries. So write patches for Linux as well and get it installed there as well. Having it in *BSD and Linux is the best you can hope for in a short time scale. Getting it into commercial Unixes takes a few more years... /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 20:47:19 1999 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 5B4A514C4C for ; Sat, 4 Dec 1999 20:47:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA58828; Sat, 4 Dec 1999 20:47:11 -0800 (PST) (envelope-from dillon) Date: Sat, 4 Dec 1999 20:47:11 -0800 (PST) From: Matthew Dillon Message-Id: <199912050447.UAA58828@apollo.backplane.com> To: "Ronald F. Guilmette" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: tmpfs .. ? References: <18062.944351089@monkeys.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> deallocate swap, or you can force it to pre-reserve swap. See the :> 'vnconfig' man page and the -S option and the '-s reserve' option. :> :> This is for -CURRENT only. :> :> Generally speaking this isn't going to be as efficient as a real tmpfs : :Please excuse my ignorance, but what is it, exactly, that you are defining :as a ``real tmpfs'' here? I would define a real tmpfs as: * one that keeps all the inodes and directory structure in memory (not swap backed) * one that is able to recover all swap space used to back processes and such, rather then just some of it. We can get close now, but eventually using UFS on top of a swap filesystem will lead to swap being allocated for virtually the entire bitmap and inode space, and partially allocated for file fragments. This would be true even with swap pre-reserved, because the system will still attempt to read a partially used disk block prior to writing it. If no swap is assigned to that block then the read is essentially a nop (well, zero-fill). * one that does not unnecessarily sync files to backing store. MFS actually doesn't, but MFS has the double-caching problem which makes it unsuitable to hold large amounts of data without stressing the system. Currently :> your tmpfs will wind up being interleaved and will have even better :> performance. pre-reservation also gives you the ability to recover :> the filesystem after a crash though for obvious reasons it can be :> problematic to depend on this ability. : :Again, please excuse my ignorance, but what ``obvious reasons'' are those? : :P.S. I have a definite interest in this sort of thing, especially if the :data stored was made to be persistant across reboots and/or crashes. If you pre-reserve swap then the physical disk locations of the swap you have reserved depends on the order in which you reserve it. So, for example, if your system needs to use some swap before the boot process gets to the point where you create the swap-backed filesystems then it will not reliably reserve the same area of swap when you create those filesystems and they will not survive the reboot. :Specifically, I'm planning a large mail server... which will use Sendmail... :and I'd really like to allocate the Sendmail queue files... which typically :have a rather short lifespan... on/in some sort of filesystem (e.g. an :mfs or else this VN thing you are talking about) that would tend to give :petter performance than just using an ordinary disk-based filesystem. But :of course, in this sort of an application, it would be Really Nice if the :filesystem in question would persist across most rebbots and crashes. : :(I asked about MFS persistance awhile back on -questions, but I don't :think that anybody groked _why_ I might want that. Now perhaps I have :made my intentions more clear.) You can also use a file as backing store for VN. You can use a file to back an MFS filesystem but you will *NOT* get persistance unless you manage to unmount the filesystem prior to rebooting. Mail queue files are persistant enough (upwards of 5 days if a destination is down) that you run a real risk of losing something important if you crash and wipe. I would not use MFS at all and I would only use VN with persistant store, but the performance is going to be similar to using a normal filesystem so it may not be worth doing. Normal filesystems with softupdates turned on make pretty good mail spools though, of course, we still have the problem of large queue directories with sendmail. -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 Sat Dec 4 20:53:20 1999 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 5F7521538D; Sat, 4 Dec 1999 20:53:16 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA58889; Sat, 4 Dec 1999 20:53:11 -0800 (PST) (envelope-from dillon) Date: Sat, 4 Dec 1999 20:53:11 -0800 (PST) From: Matthew Dillon Message-Id: <199912050453.UAA58889@apollo.backplane.com> To: Wes Peters Cc: "Jordan K. Hubbard" , Dennis , Mike Smith , Kris Kennaway , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: <41264.944342473@zippy.cdrom.com> <199912042149.NAA57545@apollo.backplane.com> <3849BE44.EF52448C@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :There is ALWAYS interest in finding out what a problem is when it's :> :reported in such a way that the effort is worth the potential reward. :> :Having someone walk up and say, in effect, "Dudes, your system is :> :broken. Fix it!" is a content-free statement and does not qualify as :> :> This is complete bullshit. Read through the thread from day 1... :> starting around Nov 20th. : :Matt, this thread is a LOT older than Nov 20th, it runs for YEARS. Dennis :said the same things about 2.2 vs. 2.1.5 at the very least. A few years :later when he finally got his driver sorted out for 2.2, it became the :best thing since sliced bread and now 3.x is nothing but crap. : :Wes Peters Softweyr LLC If you base your opinion on something a person has done years ago then absolutely *nothing* he can do will change your opinion. If you then perpetuate the problem by using that as the basis for a continuing opinion, and use that to color your every reply, then you create a self-fullfilling prophesy. The only person you have to blame in that type of situation is yourself, since you are the only one who can change it. -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 Sat Dec 4 21:15:35 1999 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 77954153CF; Sat, 4 Dec 1999 21:15:27 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA58998; Sat, 4 Dec 1999 21:14:41 -0800 (PST) (envelope-from dillon) Date: Sat, 4 Dec 1999 21:14:41 -0800 (PST) From: Matthew Dillon Message-Id: <199912050514.VAA58998@apollo.backplane.com> To: Kris Kennaway Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Since I'm one of the existing FreeBSD people you're probably referring to :here, let me remind you of the actual content: : :Dennis said the following: : :> The nightmare of instability of 3.x continues whilst the braintrust :> flogs away at 4.x. Its really a damn shame. And why is 3.x so much :> slower than 2.2.8? Will 4.0 be slower yet? : :Note the apparently belligerent tone, including use of emotionally charged :language and sudden change of topic. Now, when someone makes a wild, :authoritative yet unsupported statement like this, I think it's only :reasonable to ask for some evidence. If I sounded facetious when I said: He didn't say this until after the situation had started to degrade. Besides, he's right. 3.x has serious problems. For a while I had good hopes for 4.x but so many things have been changed gratuitously (and not by me!) that I'm beginning to worry about 4.x as well. I think the problem is that we split the tree too early and everyone moved to developing on 4.x. In regards to the speed issue - some things are faster, some things are slower. It depends on the subsystem. The remark seems to be one of frustration rather then belligerence. I would be frustrated too if I didn't have commit privs to fix the problems that effect me. Fortunately I am a good programmer and can fix things :-). But I've had to deal with a number of nightmare situations by commercial entities deploying FreeBSD and at least three (including one very recently) where commercial entities have refused to upgrade past 2.2.x due to perceived stability problems. Perhaps this time around we should not split out the 5.x tree until we've gotten past the 4.1 release. It's something to think about. -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 Sat Dec 4 21:16:56 1999 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 22746153CF for ; Sat, 4 Dec 1999 21:16:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA59052; Sat, 4 Dec 1999 21:16:48 -0800 (PST) (envelope-from dillon) Date: Sat, 4 Dec 1999 21:16:48 -0800 (PST) From: Matthew Dillon Message-Id: <199912050516.VAA59052@apollo.backplane.com> To: Matthew Dillon Cc: "Ronald F. Guilmette" , freebsd-hackers@FreeBSD.ORG Subject: Re: tmpfs .. ? References: <18062.944351089@monkeys.com> <199912050447.UAA58828@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : * one that is able to recover all swap space used to back processes : and such, rather then just some of it. We can get close now, processes? I meant files. Just SMP and filesystem code mixing in my brain! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 4 21:38:36 1999 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 4681614EE3; Sat, 4 Dec 1999 21:38:33 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA59166; Sat, 4 Dec 1999 21:37:57 -0800 (PST) (envelope-from dillon) Date: Sat, 4 Dec 1999 21:37:57 -0800 (PST) From: Matthew Dillon Message-Id: <199912050537.VAA59166@apollo.backplane.com> To: Mike Smith Cc: hackers@freebsd.org Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: <199912042247.OAA05083@mass.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : - Dennis is a principal in a company which manufactures communications : peripherals and writes driver software for them. It's not : unreasonable to expect him to have some sort of idea, or access to an : in-house idea, about how to go about diagnosing a problem like this. : It's also not unreasonable to expect that, being involved in a : development environment, that he would have some experience in : reporting problems in a fashion that would allow action to be taken to : resolve them. : : - We have been dealing with Dennis for many years. He has persisted in : his defective communications style despite many well-meaning attempts : to encourage him to improve. At this point in time, he has worn out : his welcome with many of us and if anything it's a credit to our : stamina that we still even listen to him anymore. : : - Irregardless of your initial presumptions concerning Dennis' ability, : the fact remains that he failed to follow through on the encouragement : to provide more information, and thus (again) we were unable to : actually provide him with any more assistance. Now he comes back a : few weeks later to complain again, still not providing any more : information. Which side is falling down in this relationship? Mike, if your idea of encouragement is an attitude of superiority, it's no wonder you aren't getting results. Has it ever occured to you that perhaps the fault for having to deal with this situation 'for years' might be partially attributed to the way your attitude colors your postings? It is perfectly possible that when this all began the person was in the wrong, but at this point the manner in which you respond to his bug reports only perpetuates the problem. I answer a lot of newbie questions on these lists, and if you read them you will note that I try to be helpful - if I'm going to answer someone's question or bug report, I don't give one line answers, I don't make assumptions as to a person's experience or abilities, and I don't put people who ask questions or post simple (or simplistic) bug reports down. I give suggestions only and I usually back up those suggestions with examples. If those people take the time to even ask a question or post a bug report in this list that appears to be reasonable, whether simplistic or not, then they deserve the best answer that can be given to them - one that does not automatically make assumptions as to abilities, intelligence, or character. That is the goal you (and a number of others) need to strive for. I fully realize that some developers have become frustated in the last few years -- I have especially noticed that with Jordan (sorry Jordan!) in the coloring of their answers to others. But putting someone down who has made a reasonable posting to the list based on past presence only perpetuates the problem (and here I am talking about other posters and not taking issue with myself, I've made plenty of bad postings but they tend to not be 'sticky' unless there's an ongoing problem. Hmm. Only one person is on my list that fits that bill at the moment if you don't count my general distate for core's mis-execution of their polcies and continuing 'extra' restrictions on my commit privs for no good reason). -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 Sat Dec 4 21:47: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 023EA14EE3 for ; Sat, 4 Dec 1999 21:47:03 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id VAA13178; Sat, 4 Dec 1999 21:45:36 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id VAA15974; Sat, 4 Dec 1999 21:45:36 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA03743; Sat, 4 Dec 99 21:45:32 PST Message-Id: <3849FC0D.E29DF371@softweyr.com> Date: Sat, 04 Dec 1999 22:45:49 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Matthew Dillon Cc: hackers@freebsd.org Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: <41264.944342473@zippy.cdrom.com> <199912042149.NAA57545@apollo.backplane.com> <3849BE44.EF52448C@softweyr.com> <199912050453.UAA58889@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > :Matt, this thread is a LOT older than Nov 20th, it runs for YEARS. Dennis > :said the same things about 2.2 vs. 2.1.5 at the very least. A few years > :later when he finally got his driver sorted out for 2.2, it became the > :best thing since sliced bread and now 3.x is nothing but crap. > : > :Wes Peters Softweyr LLC > > If you base your opinion on something a person has done years ago then > absolutely *nothing* he can do will change your opinion. If you then > perpetuate the problem by using that as the basis for a continuing opinion, > and use that to color your every reply, then you create a self-fullfilling > prophesy. The only person you have to blame in that type of situation is > yourself, since you are the only one who can change it. Oh hell, how did I manage to fall into alt.philosophy.est? Wait a minute, this *is* freebsd-hackers. It's *you* who is off topic, and off base. As penance, you get to go read everything ever posted to a freebsd mailing list by JMJr. People do change, and I continually await improvement from the lot of 'em. I'm rarely pleasantly surprised. -- "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 Sat Dec 4 21:53:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id A142B14EE3; Sat, 4 Dec 1999 21:53:11 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id VAA13186; Sat, 4 Dec 1999 21:52:13 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id VAA16014; Sat, 4 Dec 1999 21:52:12 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA03842; Sat, 4 Dec 99 21:52:09 PST Message-Id: <3849FD95.F0434263@softweyr.com> Date: Sat, 04 Dec 1999 22:52:21 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Matthew Dillon Cc: Kris Kennaway , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: <199912050514.VAA58998@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > : > :Since I'm one of the existing FreeBSD people you're probably referring to > :here, let me remind you of the actual content: > : > :Dennis said the following: > : > :> The nightmare of instability of 3.x continues whilst the braintrust > :> flogs away at 4.x. Its really a damn shame. And why is 3.x so much > :> slower than 2.2.8? Will 4.0 be slower yet? > : > :Note the apparently belligerent tone, including use of emotionally charged > :language and sudden change of topic. Now, when someone makes a wild, > :authoritative yet unsupported statement like this, I think it's only > :reasonable to ask for some evidence. If I sounded facetious when I said: > > He didn't say this until after the situation had started to degrade. > > Besides, he's right. 3.x has serious problems. All running software has serious problems, that's why it is never considered done. Taking the time to enumerate specific problems that are currently plaguing an installation is the only way anyone can possibly hope to help. Problems reports of "It don't work" are helpful to absolutely noone. > For a while I had > good hopes for 4.x but so many things have been changed gratuitously > (and not by me!) that I'm beginning to worry about 4.x as well. I think > the problem is that we split the tree too early and everyone moved to > developing on 4.x. > > Perhaps this time around we should not split out the 5.x tree until we've > gotten past the 4.1 release. It's something to think about. Finally, a well-thought-out message in this thread. I'd say rather than rubber-stamping it at 4.1, perhaps stretch it to "a 4.x that we'd recommend to Yahoo!" Of course, 4.1 *should* be that stable. -- "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 Sat Dec 4 22:10: 3 1999 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 B6ACB14EE3 for ; Sat, 4 Dec 1999 22:09:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA59355; Sat, 4 Dec 1999 22:09:17 -0800 (PST) (envelope-from dillon) Date: Sat, 4 Dec 1999 22:09:17 -0800 (PST) From: Matthew Dillon Message-Id: <199912050609.WAA59355@apollo.backplane.com> To: Wes Peters Cc: hackers@freebsd.org Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: <41264.944342473@zippy.cdrom.com> <199912042149.NAA57545@apollo.backplane.com> <3849BE44.EF52448C@softweyr.com> <199912050453.UAA58889@apollo.backplane.com> <3849FC0D.E29DF371@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Oh hell, how did I manage to fall into alt.philosophy.est? Wait a minute, :this *is* freebsd-hackers. It's *you* who is off topic, and off base. : :As penance, you get to go read everything ever posted to a freebsd mailing :list by JMJr. : :People do change, and I continually await improvement from the lot of 'em. :I'm rarely pleasantly surprised. : :-- : "Where am I, and what am I doing in this handbasket?" : :Wes Peters Softweyr LLC It's not really philosophy, just common sense. If you want to affect a change then, believe me, the way you are going about it isn't helping. If you post responses that only perpetuate the problem, then you are going to be waiting a *long* time. Now, this probably seems a bit jaded coming from me since my dealings with core have spilled over into the lists, but that's a different situation. Core has been holding an axe over my head for 11 months with arbitrary commit restrictions and can't come up with a straight answer for why they are still doing it. Perhaps if they take away the axe or state in a clear and concise and non-vague manner why the axe is there and what I can do to have it taken away, they might be pleasantly surprised. Until that happens though nothing will change. The self perpetuation of the problem in my case is that axe and since I don't control the axe core has created a self fullfilling prophesy for as long as they continue to hold it over me. In this case there is no axe, so there is no real reason why the problem should continue to perpetuate, yet it does and you have to consider the possibility that you are partially to blame and fix that part before you can expect to see any change realized by the other party. -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 Sat Dec 4 22:47:20 1999 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 897A515147; Sat, 4 Dec 1999 22:47:11 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA59445; Sat, 4 Dec 1999 22:46:01 -0800 (PST) (envelope-from dillon) Date: Sat, 4 Dec 1999 22:46:01 -0800 (PST) From: Matthew Dillon Message-Id: <199912050646.WAA59445@apollo.backplane.com> To: Wes Peters Cc: Kris Kennaway , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: <199912050514.VAA58998@apollo.backplane.com> <3849FD95.F0434263@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> He didn't say this until after the situation had started to degrade. :> :> Besides, he's right. 3.x has serious problems. : :All running software has serious problems, that's why it is never considered :done. Taking the time to enumerate specific problems that are currently :plaguing an installation is the only way anyone can possibly hope to help. :Problems reports of "It don't work" are helpful to absolutely noone. This simply isn't true. I have written plenty of software (large projects) that do not have serious problems and, in fact, some do not have any known problems at all. I have written several operating systems and one of them is least as complex as the FreeBSD core (but not as complex if you count drivers) which are bug-free (that is, there have been no recorded crashes and except for feature updates have never been rebooted). FreeBSD can become 'bug free' insofar as it is possible to become bug free. You have to believe that it can happen or it won't. I believe it can -- my personal goal for the project is to make the core bug free and uncrashable (and here I mean only with a network and disk driver, and not all the other drivers out there which would be an impossible task). Since I've actually *written* bug-free and uncrashable OS cores I am confident that it is possible to do with FreeBSD. Many of the issues relating to FreeBSD's instability and the many bugs in the core have nothing to do with continuing development work per-say, but instead has to do with an attitude that allows major pollution to be introduced into the code to optimize very specific cases (which destabilizes the source at the same time), and the lack of proper documention within the source code. It is precisely these two things which I have concentrated on the most - by rewriting where necessary, generalizing optimizations (and ripping quite a few out of the VM system entirely), and documenting the hell out of any procedure I modify with succinct comments. There are two good examples of code pollution and, needless to say, they have been responsible for a huge number of bugs over the years. Hundreds of bugs at least. The first example is all the VM hacking that was done to accomodate partial cache instantiation and, most noteably, partial byte-range writes for NFS. So far this year I have managed to rip about half of those hacks out at relatively little cost (a few esoteric NFS write cases will be slower is all and buffer cache writing is slightly slower due to the extra system process, but hopefully made up by the move to an O(1) algorithm (previously an O(N^2) algorithm). The second example is the VFS layer implemenation and, most especially, VOP_LOOKUP(). VOP_LOOKUP() has caused no end of trouble but the VFS layer implementation with all of its locking assumptions and return requirements has made filesystem design problematic at best. There is enormous complexity in the lookup, directory scanning, VFS cache code that hides bugs and that could be removed with a rewrite. In general, it is possible to fix these problems but some of those fixes require significant rewriting. You have to be willing to rewrite and take your lumps up front or you may be faced with a situation where new problems are found with a subsystem for years to come. The best example of this in my case is the getnewbuf() code. The code was originally optimized with so many 'hacks' that it created at least half a dozen serious bugs in the system. When I first rewrote it I encountered a huge amount of resistance from certain people who believed (wrongly) that rewriting would create more bugs then it fixed. While a few bugs were introduced (that's the 'taking your lumps part), the generalization of the code made finding and fixing them much, much easier and this will ultimately lead to a better track record down the road. I applaud the removal of dead code that has been going on, though I have major problems with the way some of it has been gone about. Compared to what some committers have been doing recently, the dead code removal that Alan and I had done to the VM system earlier in the year was a walk in the part. I am dead set against 'hiding' bugs by trying to cache around them instead of fixing them, which is essentially the category in which I put most of the recent changes to procfs and /bin/ps. It may seem counter-productive, but in order to fix bugs and make the system stable we actually need to cause the bugs to come to light more quickly and in a manner that is so blazingly obvious that we can fix them more quickly. Hence the reason for putting KASSERT()'s all throughout the VM system (which led to the discovery that VM pages were being put on the cache queue while still dirty and led to a fix for a serious filesystem corruption bug, amoung other things). When I did that some people screamed at me because they thought it would make the system unstable, but how many panics have we ever seen from it? I am happy to see other people start to do the same thing. So, I think it *IS* possible to make FreeBSD sufficiently bug-free that people become 'surprised' when they are able to crash a box running it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message