Re: Patch #3 (TCP / Linux / Performance)
this is what i get, it's between a dell 2540 (dual PIII/900) and an Intel Sl2 (dual PIII/1g). both are using intel's em driver. majadara ./tbench 1 bagel Throughput 12.4785 MB/sec (NB=15.5981 MB/sec 124.785 MBit/sec) majadara ./tbench 2 bagel Throughput 18.1598 MB/sec (NB=22.6998 MB/sec 181.598 MBit/sec) majadara ./tbench 4 bagel Throughput 26.966 MB/sec (NB=33.7076 MB/sec 269.66 MBit/sec) majadara ./tbench 6 bagel Throughput 31.4915 MB/sec (NB=39.3644 MB/sec 314.915 MBit/sec) majadara ./tbench 8 bagel Throughput 33.6752 MB/sec (NB=42.0939 MB/sec 336.752 MBit/sec) ./tbench 10 bagel Throughput 34.8712 MB/sec (NB=43.589 MB/sec 348.712 MBit/sec) ./tbench 15 bagel Throughput 37.002 MB/sec (NB=46.2526 MB/sec 370.02 MBit/sec) ./tbench 20 bagel Throughput 37.0574 MB/sec (NB=46.3217 MB/sec 370.574 MBit/sec) it starts very nice, but maxes out at about 37MB/sec. btw, before the patch tbench was moving bits (not bytes :-) at turtle speed (i thought that it was hung, but tcpdump showed some trafffic :-) good work! now lets see if nfs/tcp is ok again. danny To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Patch #3 (TCP / Linux / Performance)
:this is what i get, it's between a dell 2540 (dual PIII/900) and an Intel Sl2 :(dual PIII/1g). both are using intel's em driver. : :majadara ./tbench 1 bagel :Throughput 12.4785 MB/sec (NB=15.5981 MB/sec 124.785 MBit/sec) :... :Throughput 37.002 MB/sec (NB=46.2526 MB/sec 370.02 MBit/sec) : ./tbench 20 bagel :Throughput 37.0574 MB/sec (NB=46.3217 MB/sec 370.574 MBit/sec) : :it starts very nice, but maxes out at about 37MB/sec. Yah. Anything running over GigE is going to be extremely finicky about the cpu/hardware/motherboard design. The best tbench results I got was 47 MB/sec between two DELL2550's(1.1GHz). It was definitely cpu-saturated. 37 MB/sec sounds about right for a 900 MHz box (with everything else being equal). This is actually fairly good performance considering the Big Giant Lock issue with SMP. :btw, before the patch tbench was moving bits (not bytes :-) at turtle speed :(i thought that it was hung, but tcpdump showed some trafffic :-) : :good work! now lets see if nfs/tcp is ok again. : :danny It should be. I now get 7.8 MBytes/sec with a TCP mount and *no* nfsiod's running where before I got buckus. And with nfsiod's I get 12.3 MBytes/sec over 100BaseTX (100% saturation). On the GigE I get 16 MBytes/sec without nfsiod and around 22 MBytes/sec with nfsiod running. That's doing NFS reads... a 'dd' to read a large file over NFS, and very good for a TCP mount. UDP mounts over the GigE get 19 MB/s and 31 MB/s reading, which is also very good for a single-file read. I wish we'd gone after these problems earlier. If we had our ducks lined up in a row we could have had these (trivial) fixes in as early as FreeBSD-4.3 and would have got much more favorable numbers in the several Linux-FreeBSD comparison articles that have come out in the last six months. Oh well. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
AUTOBOOT!!!
Hi, sorry by the english... but... how can i fix the AUTOBOOT??? my FreeBSD 4.2 (mail server) are booting when it wants! is it normal? default??? The implemantation for AUTOBOOT is for what??? i don't believe it! The uptime of that box is one day... three days... and REBOOT... help, how can i fix it?? thanks!!! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: AUTOBOOT!!!
Odd... Have you checked the syslog (messages) to see if you are not actually experiencing a kernel panic? FreeBSD would autoboot on kernel panic. Also, if this is a public machine, it's possible (altho unlikely) you have some kind of Trojan/Virus and someone is either manually doing it remotely, or it's a malicious virus set to do it automatically. FreeBSD is not meant to reboot all by itself, unless you have a Watchdog timer on it (which I doubt you have!)... Thanks S. On Mon, 3 Dec 2001, Marcelo Leal wrote: Hi, sorry by the english... but... how can i fix the AUTOBOOT??? my FreeBSD 4.2 (mail server) are booting when it wants! is it normal? default??? The implemantation for AUTOBOOT is for what??? i don't believe it! The uptime of that box is one day... three days... and REBOOT... help, how can i fix it?? thanks!!! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message -- Mr Shashi Dookhee Head of IT Infrastructure Tel: (020) 7298 8222 Fax: (020) 7298 1050 Mob: (07803) 760 315 Email: [EMAIL PROTECTED] === Traffic Proximity Limited 191 Old Marylebone Road London NW1 5DW United Kingdom Registered number: 3164767 Registered in England Tel:+44 (0) 20 7298 8200 Fax:+44 (0) 20 7298 8201 This email its contents and any files or images with it are intended solely for the addressee(s) and are confidential. If you have received this email in error you may not copy or use the contents, attachments or information in any way. Please destroy it and contact the sender on the number printed above, via the Traffic Proximity switchboard or via email return. DISCLAIMER Material contained in this email may be copyright material of Traffic Proximity or protected by other intellectual property rights. It may only be reproduced with the express permission of Traffic Proximity. Traffic Proxmity does not accept responsibility for any changes made to this email by unauthorised parties after it was sent. Whilst Traffic Proximity runs antivirus software on all Internet emails it is not liable for any loss or damage caused by an infected email. The recipient is advised to run their own antivirus software. All information contained in this email has been prepared using information believed by the author to be reliable and accurate, but Traffic Proximity makes no warranty as to accuracy and completeness. Any opinions expressed in this email are those of the author and do not necessarily reflect the opinions of Traffic Proximity or its affiliates. === To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
RE: AUTOBOOT!!!
Marcelo Leal, How about checking your machine was rebooted by kernel panic (because of fs problem, ... etc)? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Shashi Dookhee Sent: Monday, December 03, 2001 9:05 PM To: Marcelo Leal Cc: John Capo; Bruce A. Mah; [EMAIL PROTECTED] Subject: Re: AUTOBOOT!!! Odd... Have you checked the syslog (messages) to see if you are not actually experiencing a kernel panic? FreeBSD would autoboot on kernel panic. Also, if this is a public machine, it's possible (altho unlikely) you have some kind of Trojan/Virus and someone is either manually doing it remotely, or it's a malicious virus set to do it automatically. FreeBSD is not meant to reboot all by itself, unless you have a Watchdog timer on it (which I doubt you have!)... Thanks S. On Mon, 3 Dec 2001, Marcelo Leal wrote: Hi, sorry by the english... but... how can i fix the AUTOBOOT??? my FreeBSD 4.2 (mail server) are booting when it wants! is it normal? default??? The implemantation for AUTOBOOT is for what??? i don't believe it! The uptime of that box is one day... three days... and REBOOT... help, how can i fix it?? thanks!!! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message -- Mr Shashi Dookhee Head of IT Infrastructure Tel: (020) 7298 8222 Fax: (020) 7298 1050 Mob: (07803) 760 315 Email: [EMAIL PROTECTED] === Traffic Proximity Limited 191 Old Marylebone Road London NW1 5DW United Kingdom Registered number: 3164767 Registered in England Tel:+44 (0) 20 7298 8200 Fax:+44 (0) 20 7298 8201 This email its contents and any files or images with it are intended solely for the addressee(s) and are confidential. If you have received this email in error you may not copy or use the contents, attachments or information in any way. Please destroy it and contact the sender on the number printed above, via the Traffic Proximity switchboard or via email return. DISCLAIMER Material contained in this email may be copyright material of Traffic Proximity or protected by other intellectual property rights. It may only be reproduced with the express permission of Traffic Proximity. Traffic Proxmity does not accept responsibility for any changes made to this email by unauthorised parties after it was sent. Whilst Traffic Proximity runs antivirus software on all Internet emails it is not liable for any loss or damage caused by an infected email. The recipient is advised to run their own antivirus software. All information contained in this email has been prepared using information believed by the author to be reliable and accurate, but Traffic Proximity makes no warranty as to accuracy and completeness. Any opinions expressed in this email are those of the author and do not necessarily reflect the opinions of Traffic Proximity or its affiliates. === To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: AUTOBOOT!!!
Thanks!!! how can i do that??? if the system reboot because a kernel panic, this is good, and i wanna know why??? How can i start this debug job??? thanks, sorry by the english! On Monday 03 December 2001 10:29, CESTLAVIE wrote: Marcelo Leal, How about checking your machine was rebooted by kernel panic (because of fs problem, ... etc)? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Shashi Dookhee Sent: Monday, December 03, 2001 9:05 PM To: Marcelo Leal Cc: John Capo; Bruce A. Mah; [EMAIL PROTECTED] Subject: Re: AUTOBOOT!!! Odd... Have you checked the syslog (messages) to see if you are not actually experiencing a kernel panic? FreeBSD would autoboot on kernel panic. Also, if this is a public machine, it's possible (altho unlikely) you have some kind of Trojan/Virus and someone is either manually doing it remotely, or it's a malicious virus set to do it automatically. FreeBSD is not meant to reboot all by itself, unless you have a Watchdog timer on it (which I doubt you have!)... Thanks S. On Mon, 3 Dec 2001, Marcelo Leal wrote: Hi, sorry by the english... but... how can i fix the AUTOBOOT??? my FreeBSD 4.2 (mail server) are booting when it wants! is it normal? default??? The implemantation for AUTOBOOT is for what??? i don't believe it! The uptime of that box is one day... three days... and REBOOT... help, how can i fix it?? thanks!!! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
wctype.h
Hi! Why widechar functions is not implemented? Is there real difficulty? And can I get it somwhere from a external lib? I need towupper, towlower and iswspace. Thank you. Sem. --- Sergey Matveychuk | System Administrator E-Mail: [EMAIL PROTECTED] | Institute Of Aviation Motors Tel: +7(095)362-56-58 | Moscow, Russia Pager: +7(095)918-19-19 ab.2244 | ICQ UIN: 3317990 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Make RELEASE broken?
There is not a /usr/release/usr/src/contrib/nvi/docs/USD.doc/vi.ref/ref.so? in the directory. and i modified the usr/src/release/Makefile to use the 4.4-stable tag. Would you please check that your buildbox has a file /usr/release/usr/src/contrib/nvi/docs/USD.doc/vi.ref/ref.so? And, you apprantly don't specify RELEASETAG variable that means you are trying to build 5-current. Is it OK for you? -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
cvsup core dumped with
id Thr ead.T closure rootA* waiting for 11 0x84ca8d4 0x8435d20 Apply *ready* 10 0x8434020 0x8435ce8 Apply A condition 0x8435480 9 0x8435ee0 0x8435cc0 Apply *ready * 8 0x8435db8 0x8436090 DispatcherRun A I/O 7 0x84334a4 0x84 33354 SndrApply A *ready* 6 0x843337c 0x8433344 RecvApply A I/O 5 0x844dc44 0x844dc08 Apply A timer 4 0x8 when updating src-base src-sys and the ports collection. it happened in the cvsupit dialog text style window. seems to be running fine now when i do /usr/local/bin/cvsup -g -L 2 /etc/cvsupfile after the core dump. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: wctype.h
what is great in that? I need them to port some application. May be exist some external libs? why don't u write ur own release to everyone? I'v got no enough time. But if I would have time may be exist some troubles with it if FreeBSD don't have this function yet. Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Application using getmntinfo and statfs
Hi all, I've written an application that uses getmntinfo which creates an array of statfs structs and stores information about mounted filesystems there. The issue that I am having is detecting valid filesystems to do further checks on. I am only interested in checking local filesystems such as UFS. Originally I was checking to see if f_type in the created struct was a certain number. The man page described this as being int f_type; /* type of filesystem */ I have now had to revert to checking f_fstypename against a string (ufs only for now) because f_type seems to contain different numbers for the same f_fstypename on different machines. Eg on three different machines running FreeBSD 4.4-STABLE I got 1, 3 and 5 for f_type where the f_fstypename was ufs. Is the f_type supposed to be consistent? If so, where is this normally defined? If the f_type is not supposed to be consistent, is there any way to check a the filesystem in the current statfs struct against a list of values without having to do if ( (strcmp(mounted_fs[count].f_fstypename, ufs) != 0) || (strcmp(mounted_fs[count].f_fstypename, hfs) !=0) ) ? Thanks -- - Wayne Pascoe | What we need is either less corruption, [EMAIL PROTECTED] | or more chance to participate in it. http://www.molemanarmy.com | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Make RELEASE broken?
kerberus There is not a kerberus /usr/release/usr/src/contrib/nvi/docs/USD.doc/vi.ref/ref.so? kerberus in the directory. That file should be there. It's your local problem if it is not extracted from your CVS repository copy. kerberus i modified the usr/src/release/Makefile to use the kerberus 4.4-stable tag. You don't have to modify Makefile. See the comment of src/release/Makefile. *** You may also want to read http://www.freebsd.org/internal/releng.html, the document of FreeBSD release engineering process written by murray. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: tar and nodump flag
Jim Bryant wrote: fergus wrote: - It doesn't support incremental backups. That isn't a problem in itself, but it's a feature our GNU tar currently has and people probably don't want to lose. I dunno... The entire incremental thing in tar is dependant on NOT using compression, which IMHO makes it pretty useless, especially if you prefer the much tighter software compression you get from gzip. You must be thinking of something different than what I was thinking of. GNU tar has an option --incremental file (or --listed-incremental) that is unaffected by the use of gzip AFAIK. -- \ |_ _|__ __|_ \ __| Jason Andresen[EMAIL PROTECTED] |\/ | ||/ _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
umass ATAPI
Hi, is anyone working on extending umass.c for ATAPI devices? My new digital camera identifies itself as an ATAPI device, but the corresponding code is commented out in umass.c, because it isn't complete and/or tested. (I'm running 4.4-RELEASE, but it doesn't look like -current is any different.) I've enabled the disabled code, and the camera probes and attaches correctly as da0. However, mounting it fails, because the ATAPI code in umass.c does not translate some commands that the mount tries to execute (cache sync, and some read_6 command - from memory, may be wrong). I'm kinda at loss on how to add the missing command translations (I poke around in the network stack normally), but I'd give it a shot if I had a little more background info on how to translate from ATAPI to SCSI. Any pointers? And I'd of course happily test whatever patches more qualified hackers come up with... :-) Lars -- Lars Eggert [EMAIL PROTECTED] Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Found the problem, w/patch (was Re: FreeBSD performing worse than Linux?)
Nate Williams [EMAIL PROTECTED] wrote: Unfortunately, I'm unable to run tcpdump on the client, since it's running NT and we're not allowed to install any 3rd party apps on it (such as the WinDump package). NT??? You wouldn't happen to be seeing performance problems with Samba, I hope? There are some known Samba/FreeBSD issues that can cause abysmal performance (~30-40KB/sec -- yes, kilobytes/sec), even with 100BT cards. No hangs or aborts, though. I've only seen this problem with DOS network stacks, but it wouldn't surprise me if it also affected some version of NT. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Found the problem, w/patch (was Re: FreeBSD performing worse than Linux?)
Unfortunately, I'm unable to run tcpdump on the client, since it's running NT and we're not allowed to install any 3rd party apps on it (such as the WinDump package). NT??? You wouldn't happen to be seeing performance problems with Samba, I hope? We're not using Samba over 100's of miles. :) There are some known Samba/FreeBSD issues that can cause abysmal performance (~30-40KB/sec -- yes, kilobytes/sec), even with 100BT cards. This may be due to problems that Matt Dillon just recently fixed this weekend in FreeBSD's TCP/IP stack. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: tar and nodump flag
On Thu, Nov 29, 2001 at 03:50:00PM -0500, Brandon D. Valentine wrote: On Thu, 29 Nov 2001, Christian Weisgerber wrote: - It doesn't support incremental backups. That isn't a problem in itself, but it's a feature our GNU tar currently has and people probably don't want to lose. It's a feature that is essential that FreeBSD doesn't lose IMO. Those of us who use tar w/ amanda to backup FreeBSD boxes know how crucial the ability to make incremental backups of filesystems can be. GNUtar would always be available as a port. So that takes care of the amanda requirement. Even my IRIX boxes come with GNUtar 1.13 in the freeware distribution. Our base system having 1.11.2 is unfortunate. If I make a test FreeBSD latest-GNUtar version, are you willing to test it out and tell me if it could go live? -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: tar and nodump flag (fwd)
On Thu, Nov 29, 2001 at 09:07:03PM +0100, Joerg Schilling wrote: - An idiosyncratic build system. This is really funny Please don't waste time on this issue. I can bmake and shoe-horn anything into our build system. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: multi-disk file systems on FreeBSD?
On Wed, Nov 28, 2001 at 12:50:21PM -0500, Michael Lucas wrote: man 8 vinum Feh. Too many problems. Remember the KISS principle and man 8 ccd -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: umass ATAPI
On Mon, Dec 03, 2001 at 10:24:36AM -0800, Lars Eggert wrote: Hi, is anyone working on extending umass.c for ATAPI devices? My new digital camera identifies itself as an ATAPI device, but the corresponding code is commented out in umass.c, because it isn't complete and/or tested. (I'm running 4.4-RELEASE, but it doesn't look like -current is any different.) I've enabled the disabled code, and the camera probes and attaches correctly as da0. However, mounting it fails, because the ATAPI code in umass.c does not translate some commands that the mount tries to execute (cache sync, and some read_6 command - from memory, may be wrong). I'm kinda at loss on how to add the missing command translations (I poke around in the network stack normally), but I'd give it a shot if I had a little more background info on how to translate from ATAPI to SCSI. Any pointers? src/sys/cam/scsi/scsi_da.c has the quirk table for such things. There are also some cameras in there. A bunch of entries have been MFS'ed shortly so if you had named your device we would know better if it's already special handled. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: umass ATAPI
Bernd Walter wrote: src/sys/cam/scsi/scsi_da.c has the quirk table for such things. There are also some cameras in there. Ian Dowse has suggested the same thing, I'll try the quirks. There's also a patch at http://groups.yahoo.com/group/usb-bsd/message/1233 that looks promising. A bunch of entries have been MFS'ed shortly so if you had named your device we would know better if it's already special handled. Ooops, sorry - it's a Pentax Optio 430. Lars -- Lars Eggert [EMAIL PROTECTED] Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: wctype.h
* Sergey Matveychuk [EMAIL PROTECTED] [011203 07:55] wrote: Hi! Why widechar functions is not implemented? Is there real difficulty? And can I get it somwhere from a external lib? I need towupper, towlower and iswspace. If you can provide sample code to verify the correctness of an implementation then i may be able to integrate it from netbsd. -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: umass ATAPI
On Mon, Dec 03, 2001 at 12:43:19PM -0800, Lars Eggert wrote: Bernd Walter wrote: src/sys/cam/scsi/scsi_da.c has the quirk table for such things. There are also some cameras in there. Ian Dowse has suggested the same thing, I'll try the quirks. There's also a patch at http://groups.yahoo.com/group/usb-bsd/message/1233 that looks promising. A bunch of entries have been MFS'ed shortly so if you had named your ^^^ Ops - should be MFC'ed device we would know better if it's already special handled. Ooops, sorry - it's a Pentax Optio 430. Usually the dmesg line fro da0 probing is more acurate. But from memory it sounds like a new device for the quirk table. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: tar and nodump flag
On Mon, 3 Dec 2001, David O'Brien wrote: On Thu, Nov 29, 2001 at 03:50:00PM -0500, Brandon D. Valentine wrote: On Thu, 29 Nov 2001, Christian Weisgerber wrote: - It doesn't support incremental backups. That isn't a problem in itself, but it's a feature our GNU tar currently has and people probably don't want to lose. It's a feature that is essential that FreeBSD doesn't lose IMO. Those of us who use tar w/ amanda to backup FreeBSD boxes know how crucial the ability to make incremental backups of filesystems can be. GNUtar would always be available as a port. So that takes care of the amanda requirement. Indeed it does. In fact, the ports/archivers/gtar port provides the latest GNUtar (1.13.25) which is on the list of things I install upon first booting a freshly installed FreeBSD box. It's the only way to make amanda play nicely. Even my IRIX boxes come with GNUtar 1.13 in the freeware distribution. Our base system having 1.11.2 is unfortunate. If I make a test FreeBSD latest-GNUtar version, are you willing to test it out and tell me if it could go live? Not on production boxes obviously but I'll put it through its paces at home for you if you like. I should think it would be pretty straightforward seeing as there is already a port which has taken care of any potential build problems. It looks like you've Cc'd the port maintainer for the gtar port on this so perhaps he's interested in helping out? Let me know if you need testing assistance. Brandon D. Valentine -- Iam mens praetrepidans avet vagari. - G. Valerius Catullus, Carmina, XLVI To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: tar and nodump flag
On Mon, Dec 03, 2001 at 04:12:28PM -0500, Brandon D. Valentine wrote: I should think it would be pretty straightforward seeing as there is already a port which has taken care of any potential build problems. Why do you think that?? The port builds using gmake and autoconf. Any in-FreeBSD-tree bits build with Bmake and w/o autoconf. Also the port has none of the FreeBSD specific changes. If the ports was in the perfect shape, why do you think the in-tree gnu tar hasn't been upgraded yet? Please look at the diffs in /usr/src/gnu/usr.bin/tar -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: wctype.h
At 2:54 PM -0600 12/3/01, Alfred Perlstein wrote: * Sergey Matveychuk [EMAIL PROTECTED] [011203 07:55] wrote: Hi! Why widechar functions is not implemented? Is there real difficulty? And can I get it somwhere from a external lib? I need towupper, towlower and iswspace. If you can provide sample code to verify the correctness of an implementation then i may be able to integrate it from netbsd. I thought we had some project which brought in the wide-character stuff, or at least was working on it. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: tar and nodump flag
On Mon, 3 Dec 2001, David O'Brien wrote: Why do you think that?? The port builds using gmake and autoconf. Any in-FreeBSD-tree bits build with Bmake and w/o autoconf. Also the port has none of the FreeBSD specific changes. If the ports was in the perfect shape, why do you think the in-tree gnu tar hasn't been upgraded yet? Please look at the diffs in /usr/src/gnu/usr.bin/tar Ah. Early Monday morning does not an astute observer make. Mea culpa. Brandon D. Valentine -- Iam mens praetrepidans avet vagari. - G. Valerius Catullus, Carmina, XLVI To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: TCP Performance Graphs
Leo Bicknell wrote: On Fri, Nov 30, 2001 at 10:29:28AM -0800, Luigi Rizzo wrote: It is not a big deal to move the default to 32 or 64k, and I'd vote for that, but if a sysadmin is unable to have a look at this, then the problem is in the sysadmin, not in FreeBSD! I disagree, on two points: * Many people use FreeBSD as a desktop OS. Think the same people who use Win98, but only slightly smarter. These people are 'sysadmins' only in the sense that they have a root password. When FreeBSD can't fill their DSL line and Linux can, they will switch to Linux never knowing what the real problem was. It's not a good idea for very large servers, either. When you doube the size, you quarter the maximum number of simultaneous slow connections which you are able to have without overcommit (you double both the input and output buffers for the sickets, meaning you have 1/4 as many mbufs per socket available. Normally, you overcommit, but, for example, if you were serving HTTP content to multiple users on slow links from a FreeBSD box in a data center, then the output buffers are commited after the first buffer full, until all of the data has been sent. For images, MP3's, etc., this means that the buffer is committed per connection for the remainder of the connection until the data is completely transferred. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Jul 30 changes to ppp break my Telstra ADSL PPPoE connection
G'day all, I have a problem with PPPoE over Telstra ADSL (Australia). A full description of the problem can be found in freebsd-questions (see [EMAIL PROTECTED] dated Nov 30) with the subject: ADSL PPPoE (Telstra Aust.) began to hang between 4.3- and 4.4-RELEASE The short of it is that at some point during my cvsup history certain types of traffic would hang, specifically most web traffic and certain types of ssh (e.g. ls -l of a long directory). This was reminiscent of the MTU/MRU problems at the beginning of the year. I backdated to 4.3-RELEASE which worked and I forgot about it until recently when I decided to change my gateway machine. I have now chased it up in earnest by going back through various dated cvsup's and making the world. On July 30th there were some changes to src/usr.sbin/ppp that break ppp and cause this problem. Strangely enough the changes were related to MRU's :- !! I can reliably make my DSL connection work on three different machines using four different network cards (ed, de, vr, rl) with source dated Jul 30 12:01am, and reliably break it with anything after Jul 31 12:01am. The changes made to ppp on that day were to: src/usr.sbin/ppp/command.c src/usr.sbin/ppp/lpc.c src/usr.sbin/ppp/nat_cmd.c src/usr.sbin/ppp/nat_cmd.h src/usr.sbin/ppp/ppp.8 The most likely problem is lpc.c because 1) it looks the most complicated(!!) and 2) it is supposed to: MFC: Handle peer REQ/NAKs of 1500 byte MRUs when we have no preference The other diffs were small and were to implement two issues: MFC: If the peer REJects our MRU REQ, stop REQing it -- *EVEN* if we're doing PPPoE and the default MRU is therefore too big. MFC: Actually add the ``nat proto'' command I'm afraid my lack of knowledge stops me going on from here. My ppp.conf is below and I start ppp with ppp -ddial -nat -quiet bigpond Can anyone see the problem and suggest further detective work I can perform or even better, a fix or workaround? Cheers, Greg P.S. I have cross-posted to questions since the thread started there and hackers since I believe I have narrowed down the problem and it is technical. I hope this is OK. Please confine your reply to whatever list you feel is appropriate, I am subscribed to both. --- default: #Only enable logging for troubleshooting #set log CBCP CCP Chat Connect Command IPCP tun Phase Warning Debug LCP sync set device PPPoE:rl0:bigpond set speed sync set mru 1454 set mtu 1454 set ctsrts off enable lqr add default HISADDR set timeout 0 set redial 7 0 set socket /var/run/pppsocket * #Network Address Translation (NAT) nat enable yes nat log yes #nat same_ports yes nat unregistered_only yes #enable dns # this disabled since the box now runs its own dns bigpond: set authname *** set authkey *** --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Success! [with patch] (was Re: umass ATAPI)
On Mon, Dec 03, 2001 at 03:19:03PM -0800, Lars Eggert wrote: Bernd Walter wrote: But from memory it sounds like a new device for the quirk table. Yes, adding quirks to scsi_da.c and enabling ATAPI in umass.c made the camera attach and mount correctly. Copying also works fine. Patches attached, if someone would like to commit them. Thanks for the help! That was quite painless... Are you shure you need to change the #if 0? Especialy the first should only have an effect on different devices. Can you please try with both to default and if that failed with the first on default. -- These quirk entries in scsi_da are a mess because all non-scsi proto umass devices need this. And unfortunatley some ide/usb converters put the ide identification on the bus, which increases the possible quirk list to every ide disk out there. Does anyone know if it is possible to put a da quirk for cam from within umass.c? umass_cam_action() or umass_*_trans/case INQUIRY comes into mind. Otherwise I will try to write some umass_*_transform routines conerting R/W_6 into _10 calls. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Success! [with patch] (was Re: umass ATAPI)
Bernd Walter wrote: Are you shure you need to change the #if 0? Especialy the first should only have an effect on different devices. Can you please try with both to default and if that failed with the first on default. Sure! With both = 0, I get: umass0: Unsupported command protocol 5 ugen0: ASAHI PENTAX OPTIO 430, rev 1.00/10.00, addr 2 With the first = 0 and the second = 1, everything works as before, so I agree that the first block probably doesn't matter. (I simply enabled everything that said ATAPI when I made the change.) However: I found that I sometimes get kernel crashes when attaching the camera, after these messages (copied by hand, may have typos): umass0: ASAHI PENTAX PENTAX OPTIO 430, rev. 1.00/10.00, addr 2, 8070i (ATAPI) over CBI umass-sim:0:-1:-1:XPT_PATH_INQ:. umass0:0:0:-1: Attached to scbus0 as device 0 scbus0: scanning for umass0:0:0:-1 umass-sim:0:-1:-1:XPT_PATH_INQ:. umass0:0:0:0::XPT_PATH_INQ:. umass0:0:0:0::XPT_PATH_INQ:. umass0:0:0:0::XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/36b data/18b sense umass-sim:0:1:0:func_code 0x0004: Invalid target (no wildcard) umass0: Handling CBI state 10 (CBI Command), xfer=0xc3eb6800, NORMAL_COMPLETION These crashes happen only one the first attach (subsequent ones are fine *if* the first one succeeded), and not always on the first one. The strange thing is that they *only* seem to happen when I attach right after bootup *before* anyone logs in. After someone logs in, it never crashed (yet). It also doesn't crash if the camera was attached *during* boot. Any clues? (Can't produce a crashdump, kernel doesn't enter DDB when crashing). Lars -- Lars Eggert [EMAIL PROTECTED] Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Jul 30 changes to ppp break my Telstra ADSL PPPoE connection
Greg Lane wrote: G'day all, I have a problem with PPPoE over Telstra ADSL (Australia). A full description of the problem can be found in freebsd-questions (see [EMAIL PROTECTED] dated Nov 30) with the subject: ADSL PPPoE (Telstra Aust.) began to hang between 4.3- and 4.4-RELEASE The short of it is that at some point during my cvsup history certain types of traffic would hang, specifically most web traffic and certain types of ssh (e.g. ls -l of a long directory). This was reminiscent of the MTU/MRU problems at the beginning of the year. I backdated to 4.3-RELEASE which worked and I forgot about it until recently when I decided to change my gateway machine. I have now chased it up in earnest by going back through various dated cvsup's and making the world. On July 30th there were some changes to src/usr.sbin/ppp that break ppp and cause this problem. Strangely enough the changes were related to MRU's :- !! I can reliably make my DSL connection work on three different machines using four different network cards (ed, de, vr, rl) with source dated Jul 30 12:01am, and reliably break it with anything after Jul 31 12:01am. The changes made to ppp on that day were to: src/usr.sbin/ppp/command.c src/usr.sbin/ppp/lpc.c src/usr.sbin/ppp/nat_cmd.c src/usr.sbin/ppp/nat_cmd.h src/usr.sbin/ppp/ppp.8 The most likely problem is lpc.c because 1) it looks the most complicated(!!) and 2) it is supposed to: MFC: Handle peer REQ/NAKs of 1500 byte MRUs when we have no preference The other diffs were small and were to implement two issues: MFC: If the peer REJects our MRU REQ, stop REQing it -- *EVEN* if we're doing PPPoE and the default MRU is therefore too big. MFC: Actually add the ``nat proto'' command I'm afraid my lack of knowledge stops me going on from here. My ppp.conf is below and I start ppp with ppp -ddial -nat -quiet bigpond Can anyone see the problem and suggest further detective work I can perform or even better, a fix or workaround? Cheers, Greg P.S. I have cross-posted to questions since the thread started there and hackers since I believe I have narrowed down the problem and it is technical. I hope this is OK. Please confine your reply to whatever list you feel is appropriate, I am subscribed to both. --- default: #Only enable logging for troubleshooting #set log CBCP CCP Chat Connect Command IPCP tun Phase Warning Debug LCP sync set device PPPoE:rl0:bigpond set speed sync set mru 1454 set mtu 1454 I had a similar problem, but haven't been able to fully track it down. I did file a PR http://www.freebsd.org/cgi/query-pr.cgi?pr=32040 . A LCP log of both versions was requested. Also if you read the new man page there is set mtu max x and set mru max x options, the I might have mistyped when I tried. Jim -- /\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ - [EMAIL PROTECTED] http://www.FreeBSD.org The Power to Serve [EMAIL PROTECTED] http://www.TheHousleys.net [EMAIL PROTECTED] http://www.SimTel.Net - If it happens once, it's a bug. If it happens twice, it's a feature. If it happens more than twice, it's windows. -- Luiz de Barros To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
RE: Success! [with patch] (was Re: umass ATAPI)
Hi, Bernd and me have mailed privately, and there's another solution besides adding a quirk to scsi_da.c. It's based on a patch posted by Gerd Knops to the usb-bsd list (http://groups.yahoo.com/group/usb-bsd/message/1233). It adds 6-to-10 conversion for SCSI commands, which makes many devices work that needed quirks before. I've verified that this (also) enables attaching, mounting and accessing a Pentax Optio 430 digital camera, which identifies itself as an ATAPI device. I've put the patch into a PR (http://www.freebsd.org/cgi/query-pr.cgi?pr=32490) in case someone would like to clean it up and commit it. Lars -- Lars Eggert [EMAIL PROTECTED] Information Sciences Institute http://www.isi.edu/larse/ University of Southern California smime.p7s Description: application/pkcs7-signature
Re: token ring cards always PROMISC
At 07/11/2001, Gary Jennejohn wrote: On Wednesday 07 November 2001 13:29, Len Conrad wrote: Sorry to bother you here. No answers from -questions or -tokenring. We didn't turn it on, we can't get PROMISC mode off. The card otherwise works fine. Is it a problem to leave in that mode? - forwarded from the other lists: Hi list, When we bring up the 3137 (or 3140), it´s always in PROMISC mode. This didn´t occur on a 4.2R machine where we DL'ed the driver ourselves (rather than use the kernel driver of 4.4R or ourselves) and has been running +one year error free. The driver turns it on by default in the init routine. If you don't want it then you'll have to modify the driver yourself. I don't know _why_ the driver does that, so modify it at your own risk. oltr0: Olicom PCI/II 16/4 Adapter (OC-3137) port 0xd000-0xd03f irq 10 at device 10.0 on pci0 oltr0: MAC address 00:00:83:2b:63:db ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xb800-0xb81f irq 11 at device 12.0 on pci0 ed0: address 00:50:ba:ee:48:38, type NE2000 (16 bit) orm0: Option ROM at iomem 0xc-0xc9fff on isa0 [...] freebsd:/home/gmarco ifconfig -a oltr0: flags=143UP,BROADCAST,RUNNING,PROMISC mtu 1500 [...] ed0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 [...] Here I have the same situation. Even if the card seems to works smoothly. I had also a lot of problems with ipfw ... Do you use any kind of firewall ? If yes can you tell me your experiences ? Best Regards, Gianmarco Giovannelli , Unix expert since yesterday http://www.gufi.org/~gmarco To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
