Re: Dropping connections without RST

1999-08-16 Thread Rodney W. Grimes
Geoff Rehmet writes: After the discussions regarding the "log_in_vain" sysctls, I was thinking about a feature I would like to implement: Instead of sending a RST (for TCP) or Port Unreachable (for UDP) where the box is not listening on a socket, I would like to implement a

Re: Dropping connections without RST

1999-08-16 Thread Rodney W. Grimes
Brian W. Buchanan writes: Can anyone think of any reason why this feature should not be implemented? I like that idea... net.inet.{tcp,udp}.drop_in_vain ? Why do we need a sysctl knob for this when it can be easily accomplished with IPFW? Not that easily.. how are you

Re: Dropping connections without RST

1999-08-16 Thread Rodney W. Grimes
Rodney W. Grimes writes : Now what would a box with so much security concern such that it needed this knob be doing running an ftp session though your point is valid and acceptable for low security boxes. And I can see the real benifit that having this knob for those boxes

Re: Dropping connections without RST

1999-08-17 Thread Rodney W. Grimes
In message [EMAIL PROTECTED] Archie Cobbs writes: : Not that easily.. how are you going to make ipfw dynamically know : which ports have listeners and which don't? By filtering all RST packets? That would be closer than my set of rules, but has the undesired effect of filtering what may be

Re: Dropping connections without RST

1999-08-17 Thread Rodney W. Grimes
[Charset iso-8859-1 unsupported, filtering to ASCII...] This is an ACK. I like those names, the idea is okay given that the documentation for it reflects what has been discussed here in this thread so folks can understand this is a very simple security measure. Hmm, dumb question

Re: REQ: Test /etc/rc clean-up

1999-08-20 Thread Rodney W. Grimes
Hi folks, I have a diff for src/etc/rc that I'd like to have had used on a few machines before I commit it. I'm pretty sure I haven't made any mistakes with my changes, but you can never be too careful, right? Right... The diff homogenizes the manner in which variables are tested and

Re: The Matrix screensaver, v.0.2

1999-08-22 Thread Rodney W. Grimes
On Sun, 22 Aug 1999, Ollivier Robert wrote: According to Narvi: "Falling letters like in the movie with red bills" Pill :) That very important... The screensaver triggered me to see the movie again. A. I love it. Yeah, it's gotta be the perfect hacker's movie.

Re: Softupdates reliability?

1999-08-24 Thread Rodney W. Grimes
On Tue, 24 Aug 1999, Richard Tobin wrote: Origin = "AuthenticAMD" Id = 0x580 Stepping=0 You have one of the first K6-2s off the line. There were definite problems with these, and as such, they were specially distinguished by having 66 printed on top. I have a 0x580

Re: Softupdates reliability?

1999-08-26 Thread Rodney W. Grimes
On Wed, 25 Aug 1999, Wilko Bulte wrote: The USA... your prices tend to be a lot better than ours. I could can the T2P4 but that would also mean I had to can the SIMMs (everything is DIMMs now), get an AGP videocard and can the perfectly fine Millenium II (I need the extra PCI slot

Re: $FreeBSD tag confusion

1999-08-29 Thread Rodney W. Grimes
John Polstra [EMAIL PROTECTED] writes: The tags are expanding just fine up here in Seattle. :-) I wish you would have included the rest of the output from your cvs status command. It sounds a lot like your source tree was checked out with "-ko". That would show up in the "Sticky

Re: $FreeBSD tag confusion

1999-08-30 Thread Rodney W. Grimes
Rodney W. Grimes writes: What verion of the cvs binary are you running (cvs -v)? Concurrent Versions System (CVS) 1.10 `Halibut' (client/server) Are you getting a copy of CVSROOT? yes...as part of src-all, but it's not used as *my* CVSROOT. What is the content of *your

Re: HEADS UP

1999-08-30 Thread Rodney W. Grimes
I've just committed the revised TCP timer code. There are some user visible changes: User visible TCP timers are now in units of the system clock (10ms for the i386), not those of the slowtimeout (500ms). So if you have customized one of these values, (e.g.:

Re: PNP ids missing in sio.c

1999-09-05 Thread Rodney W. Grimes
On Sat, 04 Sep 1999 21:34:09 -0700, Mike Smith [EMAIL PROTECTED] said: The enumerator should assign these resources to a placeholder; I was thinking the nexus was as good an owner as any. If there's an "unknown" device that's probably even better. Some of them should be claimed by

Re: request for review: move of /var/cron/log to /var/log/cron.log

1999-09-05 Thread Rodney W. Grimes
Nick Hibma wrote: Please review the following patch to get all the log files in one place. The commit will be accompanied by a HEADS UP. If no one objects I will commit this in a couple of days. The only thing I don't like about this is that it introduces a point of

Re: optional 'make release' speed-up patch

1999-09-08 Thread Rodney W. Grimes
Hi, The following patch to /usr/src/release/Makefile allows the specification of the variable FASTCLEAN, which instead of doing a recursive rm on CHROOTDIR, simply umounts/newfs/mounts. Of course, this is only useful if your CHROOTDIR location is a separate mount point (which mine is:

Re: more

1999-09-12 Thread Rodney W. Grimes
* Tim Vanderhoek ([EMAIL PROTECTED]) [990912 17:50]: On Sun, Sep 12, 1999 at 03:20:02PM +0200, Jeroen Ruigrok/Asmodai wrote: On this CURRENT of 3-4 weeks old I can do /blah and then use / to find the next occurance of blah in the same file. With the `new' more this behaviour has

Re: An FS question perhaps... non blocking I/O.

1999-09-12 Thread Rodney W. Grimes
In article [EMAIL PROTECTED], Garrett Wollman [EMAIL PROTECTED] wrote: [POLLEXTEND, POLLATTRIB, POLLNLINK, POLLWRITE] It is probably undocumented. I was a bit reluctant to document it since I know that the interface is not correct. One of these days, I (or more likely some

Re: 2xPIIIx450 results NFS results

1999-09-18 Thread Rodney W. Grimes
On Sat, 18 Sep 1999 01:16:52 + (GMT), Adam Strohl [EMAIL PROTECTED] said: I've been getting this too on 4.0-C, just rebuild last night, still there. top displays: CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle On my dual-PPro Intel BB440FX system

Re: 2xPIIIx450 results NFS results

1999-09-18 Thread Rodney W. Grimes
OK, Upgraded my Asus P2B-D machien from BIOS version 1008 to 1010, the problem disappeared. Popped back to my old 1008 BIOS, problem came back. So far about alls I have confirmed is that the problem does not exists with BIOS 1009 when the apm code is not compiled into the kernel. I'll have a

Re: Testers please!

1999-09-22 Thread Rodney W. Grimes
... One question comes to mind: is there a way that the TSCs could become desynchronized somehow? Even though all CPUs run at the same frequency, isn't there a strong possibility for slight frequency deviation since we use crystal oscillation instead of a more accurate atomic breakdown

Re: Automating filesystem check at boot time

1999-09-23 Thread Rodney W. Grimes
[Charset iso-8859-1 unsupported, filtering to ASCII...] I administer a number of remote FreeBSD boxes and starting with 3.x they have been unreliable at rebooting. We all know FreeBSD wants to keep running forever, however it seems to be at the expense of reboot stability. I have found the

Re: On hub.freebsd.org refusing to talk to dialups

1999-09-24 Thread Rodney W. Grimes
From: "Rodney W. Grimes" [EMAIL PROTECTED] Date: Fri, 24 Sep 1999 03:00:55 -0700 (PDT) Another thing that ISP coulds start doing (we are in process with this now, but on a monitoring only basis, instead of a deny we just log them) is to block all outbound from AS tcp 25 set

Re: On hub.freebsd.org refusing to talk to dialups

1999-09-24 Thread Rodney W. Grimes
would immediately unsubscribe to any isp that decided this was acceptable behavior on their part. I agree. Your work also has a serious security concern if it allows this you to directly attatch to it's port 25. No it doesn't, but you do bring up another good point why not to

Re: On hub.freebsd.org refusing to talk to dialups

1999-09-24 Thread Rodney W. Grimes
At 03:00 AM 9/24/1999 -0700, you wrote: Another thing that ISP coulds start doing (we are in process with this now, but on a monitoring only basis, instead of a deny we just log them) is to block all outbound from AS tcp 25 setup packets. Hmm, maybe I'm interpreting this wrong (I hope so),

Re: On hub.freebsd.org refusing to talk to dialups

1999-09-24 Thread Rodney W. Grimes
I agree. Your work also has a serious security concern if it allows this you to directly attatch to it's port 25. No it doesn't, but you do bring up another good point why not to use the ISP's mail server. Security. I don't want email to bounce on your box and

Re: On hub.freebsd.org refusing to talk to dialups

1999-09-26 Thread Rodney W. Grimes
If _we_ don't start to do something about it, big brother _is_ going to do something about it. Trust me on this one, being a member of the USPA I know that we are far better off implementing our own (as ISP's) set of safe gaurds that help eliminate certain undesirable behavior.

Re: Loss of Functionality with newpnp

1999-09-27 Thread Rodney W. Grimes
I'm just suggesting here that it would be nice if the authors of this code would make it _equally functional_ to what was removed. It's not nice to remove functionality unconditionally and then provide no replacement at all... That work is underway, and something to understand about

Re: System crash on vinum start

1999-09-28 Thread Rodney W. Grimes
On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote: Good software shouldn't panic. I wish _I_ could convince some people of this :-(. Most certainly is. Could use the functionality to add to a plex's size for striped or RAID5, but a bit of planning cures that. 8-) It's

Re: Loss of Functionality with newpnp

1999-09-28 Thread Rodney W. Grimes
[Reinsertion of original answer by jkh] That work is underway, and something to understand about -current is that it doesn't have to actually work at all times during the interim periods between releases. Now, should 4.0 be on the horizon and the situation still be one where

Re: System crash on vinum start

1999-09-28 Thread Rodney W. Grimes
As Rodney W. Grimes wrote ... On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote: Good software shouldn't panic. I wish _I_ could convince some people of this :-(. rather than having to recover each logical volume. It would also be nice if you could recover mirrored

Re: HEADS UP: sigset_t changes committed

1999-09-29 Thread Rodney W. Grimes
On Thu, 30 Sep 1999, Harold Gutch wrote: Uhm, that's the way I see it being _right now_ as well. What I was thinking of, was that things would go smoother if you wouldn't upgrade _right now_, but in [insert some time in the near future here], as things would perhaps be "fixed" by then.

Re: new sigset_t and upgrading: a proposal

1999-09-30 Thread Rodney W. Grimes
Hi, In the recent discussion about the breakage of the upgrade path from -stable to -current numerous suggestions and other kinds of remarks have been made. In this light I have the following proposal. Please share your thoughts... NOTE: This proposal only discusses upgrading from

Re: new sigset_t and upgrading: a proposal

1999-09-30 Thread Rodney W. Grimes
"Rodney W. Grimes" wrote: 1. A compiler C running on machine 1 and capable of generating code for machine 2 (the compiler includes headers and libraries), 2. Source code compatible with compiler C, but also with machine 2. And also compatible with

Re: new sigset_t and upgrading: a proposal

1999-09-30 Thread Rodney W. Grimes
Why are the tools being built using new syscalls? What causes this? Mainly historical bugs. Includes are installed too early and they only match the new syscalls. Tools are built using the new includes, so they need new libraries to be consistent. Therefore the new libraries are built

Re: new sigset_t and upgrading: a proposal

1999-09-30 Thread Rodney W. Grimes
On Thu, Sep 30, 1999 at 06:25:56AM -0700, Rodney W. Grimes wrote: Cons o Upgrading from 3.3 and before to -current is only possible after an upgrade to post 3.3. Not good. We recommend that 2.2.x people upgrade to the latest 2.2-STABLE offering before trying to jump

Re: new sigset_t and upgrading: a proposal

1999-10-02 Thread Rodney W. Grimes
[CC: trimmed to -current] But this still doesn't entirely solve the problem. You still have to build and install a new kernel before installing the world. While this is typically what most -current folks do anyways, it still prevents backing up to a previous kernel after the

Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...

1999-10-07 Thread Rodney W. Grimes
:Hi again, : : Whoops: a few hours after downgrading to 3.1-STABLE I had a double fault :error (strange, it didn't look like a normal panic screen, just the :message and the content of three registers, then the syncing disks :message). It seems that I might be wrong about hardware not being

Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...

1999-10-08 Thread Rodney W. Grimes
On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote: Intel's ECC implementation is not perfect (1), but it's good enough to catch these sorts of problems. Just as an interesting side note, we had a motherboard which supported ECC ram and had ECC ram in it and which

Re: People getting automatically unsub'ed from -arch

1999-10-11 Thread Rodney W. Grimes
"Accidental" removals from the lists are so common that I give up. I no longer even try to get back on them -- it's been happening for _years_ now, and I have made multiple complaints about it, and if it's not a problem for whoever runs the mailing lists, then I just don't care that

Re: People getting automatically unsub'ed from -arch

1999-10-12 Thread Rodney W. Grimes
"Rodney W. Grimes" wrote: "Accidental" removals from the lists are so common that I give up. I no longer even try to get back on them -- it's been happening for _years_ now, and I have made multiple complaints about it, and if it's not a problem

Re: trek73

1999-10-23 Thread Rodney W. Grimes
No. Make it a port. Policy, remember? 8) I guess the anti-bloatists would have a point on this one... I would not object to a port. It certainly eliminates the bike shed arguments over it. Did anyone bother to look at /usr/src/games/trek/main.c: ** C version by Eric P. Allman

Re: FreeBSD 4.0 SCSI Tape Driver

1999-11-15 Thread Rodney W. Grimes
The design phase for FreeBSD 4.0 is coming to a close. There are a couple of things I'm planning on (belatedly) for the SCSI tape driver. I'd like feedback and suggestions about these and other things, so pass 'em my way. One change I'm thinking about is probably controversial, so I'd like

Re: FreeBSD 4.0 SCSI Tape Driver

1999-11-15 Thread Rodney W. Grimes
Reread/reresponse, sorry- ENOCOFFEE: 1 filemark can not be used for EOT, it is EOF, you can't tell if what you read next is another file or not that may have been left by a previosly longer usage on the tape. Well, read until *BLANK CHECK* seems to be what the driver

Re: FreeBSD 4.0 SCSI Tape Driver

1999-11-15 Thread Rodney W. Grimes
Okay- I hear you both. What do you do with QIC drives which cannnot write 2FM then? Can you give me a model of a QIC drive that has the ``can't write 2 FM's'' and I'll see if I can find one so that I can see this problem first hand and propose a solution to it. I find it extreamly hard to

Re: FreeBSD 4.0 SCSI Tape Driver- Okay, Okay, you win....

1999-11-16 Thread Rodney W. Grimes
On Tuesday, 16 November 1999 at 8:04:05 -0800, Matthew Jacob wrote: Too many people have objected. I didn't make my case clearly enough, but because enough people of have raised issues, the default won't be changed. I think this is the correct decision in the short term. In the

Re: gcc 2.95.2

1999-11-16 Thread Rodney W. Grimes
On Tue, 16 Nov 1999, Manfred Antar wrote: I think this is all related to the compiler update as I did a good build Friday or Saturday before the change. If it is, then some thing wierd is going on. Something weird is going on... I can confirm Manfred's claim, I also just build

Re: dd and gzip'd files

1999-11-21 Thread Rodney W. Grimes
I recently tried using dd to transfer a binary image to floppy. It was the Linux root disk image, color.gz. Basically, dd works ok with non-gzipped files, but with files in gzip format, it chokes: root@lc186 floppies# dd if=color.gz of=/dev/rfd0 dd: /dev/rfd0: Invalid

Re: FreeBSD security auditing project.

1999-11-23 Thread Rodney W. Grimes
2) I propose that WE diff(1) FreeBSD with {Open|Net}BSD, This is not the easiest thing to do (I've tried). Rather one should look at what changes OpenBSD has done to a piece of code since they imported it from NetBSD and compare with FreeBSD code to see if the OpenBSD change is

Re: FreeBSD security auditing project.

1999-11-24 Thread Rodney W. Grimes
"Rodney W. Grimes" [EMAIL PROTECTED] writes: It's not so much that they where ``allowed'' to do it, it is more the matter that they where never directly served with legal papers from USL/Novell to cease all use of Net/2. Nor did they ever enter into any agreement, that

Re: patches for test / review

2000-03-21 Thread Rodney W. Grimes
On Tue, Mar 21, 2000 at 09:29:56AM -0800, Matthew Dillon wrote: : : I would think that track-caches and intelligent drives would gain : much if not more of what clustering was designed to do gain. : :Hm. But I'd think that even with modern drives a smaller number of bigger :I/Os is

Re: patches for test / review

2000-03-21 Thread Rodney W. Grimes
On Tue, Mar 21, 2000 at 01:14:45PM -0800, Rodney W. Grimes wrote: On Tue, Mar 21, 2000 at 09:29:56AM -0800, Matthew Dillon wrote: : : I would think that track-caches and intelligent drives would gain : much if not more of what clustering was designed to do gain. : :Hm

Re: Experts only please! (was Re: Preliminary SMP/BGL patch)

2000-03-24 Thread Rodney W. Grimes
At 2:57 PM -0500 2000/3/24, Garance A Drosihn wrote: At 10:01 AM -0800 3/24/00, Matthew Dillon wrote: This is not a 'normal Matt patch' that 'just works'. Ok, it seems to just work, but it's not a normal Matt patch. If there were a designation before 'early alpha' this

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Rodney W. Grimes
The message in question can be extremely useful in case there is IP address clash on the local network. I suggest we just change the code in question to ignore clashes over 0.0.0.0 address only. No, don't do that, anyone arping 0.0.0.0 on any network around here I sure as heck want to know

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Rodney W. Grimes
to be disabled? On 07-Apr-00 Rodney W. Grimes wrote: The message in question can be extremely useful in case there is IP address clash on the local network. I suggest we just change the code in question to ignore clashes over 0.0.0.0 address only. No, don't do that, anyone arping

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Rodney W. Grimes
The message in question can be extremely useful in case there is IP address clash on the local network. I suggest we just change the code in question to ignore clashes over 0.0.0.0 address only. No, don't do that, anyone arping 0.0.0.0 on any network around here I sure as heck

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Rodney W. Grimes
No... Yes... that is just the type of thing the link local RFC reserved address space is for. In message [EMAIL PROTECTED], Mathew Kanner writes: On Apr 07, Donn Miller wrote: Since I started using a cable modem and dhclient, my system has been literally overwhelmed with messages like:

Re: missing functionality

2000-04-22 Thread Rodney W. Grimes
On Sat, 22 Apr 2000 01:45:20 -0400 (EDT), "Brandon D. Valentine" [EMAIL PROTECTED] said: to include support for the MCA bus. The vast majority of MCA bus machines in existence utilize ESDI because they predate the UDMA and AFAIK, the only MCA disk controller supported does SCSI. The

Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday

2000-04-23 Thread Rodney W. Grimes
There's another good reason to MFC the linux patch on wednesday... that is, to do it at the same time the SMP cleanup is MFC'd, and that is because both patch sets require the linux kernel module to be recompiled and I'd rather not force people to do that twice. The

Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday

2000-04-23 Thread Rodney W. Grimes
: :In message [EMAIL PROTECTED], Matthew Dillon writes: : :There's another good reason to MFC the linux patch on wednesday... :that is, to do it at the same time the SMP cleanup is MFC'd, and that :is because both patch sets require the linux kernel module to be :

Re: SMP changes and breaking kld object module compatibility

2000-04-24 Thread Rodney W. Grimes
On Mon, Apr 24, 2000 at 09:27:04AM -0500, Richard Wackerbarth wrote: On a released system, I may not have the sources to recompile the module. It might be a proprietary module that I got with the hardware, for example. How real is this? What modules are we talking about? The last time

Re: SMP changes and breaking kld object module compatibility

2000-04-24 Thread Rodney W. Grimes
Gee, is that perhaps because FreeBSD keeps breaking the ABI to modules so every vendor that has ever tried to use them has been bitten by the fact that they have to maintain N version for each branch of FreeBSD??? Can you list some specific examples? I'm not trying to be a wise-ass,

Re: SMP changes and breaking kld object module compatibility

2000-04-24 Thread Rodney W. Grimes
On Mon, Apr 24, 2000 at 02:02:28PM -0500, Richard Wackerbarth wrote: That is also partly why you are also lacking the respect and support of a wider audience. If you act like FreeBSD is just a "developer's sandbox", that's what it will be. If you want it to be something greater than

Re: SMP changes and breaking kld object module compatibility

2000-04-24 Thread Rodney W. Grimes
{First one bounced by hub with ``out of memory'' error... second attempt} Are there any 3rd party NIC klds yet? NTMK. It's not quite a kld, but ET Inc's modules are distributed as a .o. Also I know of work underway to support some of the fancier SDL WanNic cards that would have to be kld's

Re: Abit BP6 - UDMA66 and non IBM disks

2000-05-08 Thread Rodney W. Grimes
[Charset ISO-8859-1 unsupported, filtering to ASCII...] It seems Arun Sharma wrote: I have the following disk: ad4: 9787MB WDC AC310200R [19885/16/63] at ata2-master using UDMA33 and am experiencing hangs when I run it with UDMA66. That exact disk model cant do UDMA66 reliably, even

Re: /sys hierarchy

2000-07-02 Thread Rodney W. Grimes
On Sunday, July 02, 2000, John Baldwin wrote: Sounds good to me actually. Although, should it be ${MACHINE_ARCH}/compile instead in keeping with the mentioned goal of keeping all MD stuff under ${MACHINE_ARCH}? I think that compile/${MACHINE_ARCH} is the proper way to do this.

Re: /sys hierarchy

2000-07-02 Thread Rodney W. Grimes
... I feel masochistic at the moment, so here's a suggestion. Feel free to rip it all up to pieces, ya'll. And to start off: I like green bikesheds. (I.e. let's settle on something sensible and not get I prefer blue ones :-) ... Ok (/me dons the asbestos suit, climbs into the concrete

Re: /sys hierarchy

2000-07-02 Thread Rodney W. Grimes
On Sunday, July 02, 2000, Rodney W. Grimes wrote: Actually the whole src/sys/compile thing should go away, it is one of the last things that has to be dealt with for a totally read-only mounted /usr/src. IMHO it should be moved to /usr/obj, and /usr/obj should, if it hasn't already

Re: cvs-crypto unknown

2000-07-07 Thread Rodney W. Grimes
cvsup4.freebsd.org does not know about cvs-crypto. What is the correct collection? src-crypto -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: cvs-crypto unknown

2000-07-07 Thread Rodney W. Grimes
cvsup4.freebsd.org does not know about cvs-crypto. What is the correct collection? src-crypto Oopsss... never mind. I think this has all been folded into the baseline cvs target. *-crypto is no more. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To

Re: if_de as a module...

2000-07-10 Thread Rodney W. Grimes
Umm- started okay: : and then died: rplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt arplookup

Re: if_de as a module...

2000-07-10 Thread Rodney W. Grimes
:f0'' to create a ``permanant'' entry and IT gets replaced!!! ARGHHH On Mon, 10 Jul 2000, Rodney W. Grimes wrote: Umm- started okay: : and then died: rplookup 192.67.166.155 failed: could not allocate llinfo arpresolve: can't allocate llinfo for 192.67.166.155rt

Re: dc driver and underruns (was: Strangeness with 4.0-S)

2000-07-13 Thread Rodney W. Grimes
On Thu, 13 Jul 2000, Stephen McKay wrote: Guess it will show up if you measure latencies (or your application is doing lots of RPCs). But as soon as there is a cheap 100baseT switch in the path to the destination, there will be store-and-forward at work ;-) Does anyone here actually

Re: dc driver and underruns (was: Strangeness with 4.0-S)

2000-07-14 Thread Rodney W. Grimes
[cc: trimmed to -current] Does anyone here actually measure these latencies? I know for a fact that nothing I've ever done would or could be affected by extra latencies that are as small as the ones we are discussing. Does anybody at all depend on the

Re: dc driver and underruns (was: Strangeness with 4.0-S)

2000-07-16 Thread Rodney W. Grimes
On Friday, 14th July 2000, "Rodney W. Grimes" wrote: I suspect an interaction between the ATA driver and VIA chipsets, because other than the network, that's all that is operating when I see the underruns. And my Celeron with a ZX chipset is immune. I've seen them on

Re: dc driver and underruns (was: Strangeness with 4.0-S)

2000-07-16 Thread Rodney W. Grimes
On Sun, 16 Jul 2000 11:41:37 -0700 (PDT), "Rodney W. Grimes" [EMAIL PROTECTED] said: Ohh... and a finally note, DEC blew the chip design by only including a 160byte threshold point given that PCI 2.0 spec says it should have been 500bytes!! It wouldn't be the first thi

Re: dc driver and underruns (was: Strangeness with 4.0-S)

2000-07-17 Thread Rodney W. Grimes
... As far as I can tell the fxp driver doesn't even use the tx_fifo in the 825xxx chips :-) The 82557-9 have a 2KB internal buffer for transmits. They don't start transmitting until a programmed threshold is reached - this is to insure that PCI bus latency doesn't result in the

Re: randomdev entropy gathering is really weak

2000-07-22 Thread Rodney W. Grimes
On Fri, 21 Jul 2000, Mark Murray wrote: Section 2.1, last paragraph: "If a system is shut down, and restarted, it is desirable to store some high-entropy data (such as the key) in non-volatile memory. This allows the PRNG to be restarted in an unguessable state at the next restart. We

Re: Core dumps on Current Make World this morning

2001-01-02 Thread Rodney W. Grimes
In message [EMAIL PROTECTED] Matthew Jacob writes: : Same with me. This sounds like a job for Captain UPDATING: Don't you just need to rebuild vi/ex? Ie would not: cd /usr/src/usr.bin/vi; make cleandir make obj make depend make all install fix the problem? Two

Re: Core dumps on Current Make World this morning

2001-01-02 Thread Rodney W. Grimes
In message [EMAIL PROTECTED], "Rodney W. Grimes" writes : In message [EMAIL PROTECTED] Matthew Jacob writes: : Same with me. This sounds like a job for Captain UPDATING: Don't you just need to rebuild vi/ex? Ie would not: cd /usr/src/usr.bin/vi; make cleandir

Re: tape device names and devfs

2001-03-06 Thread Rodney W. Grimes
Christian Weisgerber wrote: Steve Kargl [EMAIL PROTECTED] wrote: I haven't heard any screaming yet. Besides, this is -CURRENT. devfs has also abandoned symlinks for 'r' disk devices. The "r" in tape device names has traditionally meant "r"ewind. The "r" in disk names (such as

Re: ** HEADS UP ** portmap daemon renamed to rpcbind

2001-04-09 Thread Rodney W. Grimes
Ok guys. I just had to fix a problem with portmap in -stable related to binding to specific IP addresses so replies to UDP packets come 'from' the proper IP address (for multi-homed hosts). This has been a problem with portmap for as long as I can remember (back to the SunOS 3.5

Re: cp -d dir patch for review (or 'xargs'?)

2001-04-20 Thread Rodney W. Grimes
Folks, although there was much rejoicing, I think there's no need for a new option to cp. Just use the toolbox, it's not too hard: (cat bigfilelist; echo destdir) | xargs cp I like this version of the patch!! It's much much cleaner than hacking up cp or xargs, it even follows the unix

Re: cp -d dir patch for review (or 'xargs'?)

2001-04-20 Thread Rodney W. Grimes
On Fri, Apr 20, 2001 at 07:26:18PM -0700, Rodney W. Grimes wrote: (cat bigfilelist; echo destdir) | xargs cp I like this version of the patch!! It's much much cleaner than hacking up cp or xargs, it even follows the unix principle of using simple tools and glueing them togeather

Re: cp -d dir patch for review (or 'xargs'?)

2001-04-22 Thread Rodney W. Grimes
I don't see a problem with adding an option to cp to treat the first argument as the target instead of the last argument. It's a simple solution, the code change is simple, and it produces the exact desired result. What's the problem? It's yet another non-portable option. I

Re: 'make includes' ownership patch

2001-05-28 Thread Rodney W. Grimes
On Sat, May 26, 2001 at 03:06:00PM -0700, Kris Kennaway wrote: On Sat, May 26, 2001 at 02:59:22PM -0700, Kris Kennaway wrote: Shouldn't the includes/Makefile be installing headers using INCOWN/INCGRP instead of BINOWN/BINGRP? I ran into this when trying to do a 'make includes' as a

Re: 'make includes' ownership patch

2001-05-28 Thread Rodney W. Grimes
On Mon, May 28, 2001 at 10:22:33AM -0700, Rodney W. Grimes wrote: This was on my TODO. The only problem with INCOWN/INCGRP not being used here is that they were introduced long after include/Makefile. And perhaps one should go read the commit message that introduced them

Re: 'make includes' ownership patch

2001-05-28 Thread Rodney W. Grimes
On Mon, May 28, 2001 at 10:31:58AM -0700, Rodney W. Grimes wrote: On Mon, May 28, 2001 at 10:22:33AM -0700, Rodney W. Grimes wrote: This was on my TODO. The only problem with INCOWN/INCGRP not being used here is that they were introduced long after include/Makefile

Re: modules/netgraph/bpf breaks world

1999-12-03 Thread Rodney W. Grimes
thanks, committed. For thise wondering this is a netgraph node that can do arbitrary filtering using the existing bpf engine. And just when is ipfw going to become a netgraph node 0.5 * :-) God I wish I had some free time to go play with this code!! On Fri, 3 Dec 1999, Steven G. Kargl

Re: Sv: mount(2) broken?

1999-12-05 Thread Rodney W. Grimes
In message 003001bf3f5d$1ff01780$[EMAIL PROTECTED], "Leif Neland" writes: Why isn't MAKEDEV installed by make (install)world? I'm actually starting to wonder about that too... Because the source is buried in src/etc, and src/etc is not run as a SUBDIR target. It had always been my intent

Re: Intel 810?

1999-12-06 Thread Rodney W. Grimes
I recently got a quote from a hardware vendor which made the following claim: All Socket 370PGA Motherboards use either the 810 or [the] 810c chip ^^ I can say with certain that statement is false, you can run a Socket 370

Re: Route table leaks

1999-12-08 Thread Rodney W. Grimes
Hell, I've been seeing this for well over a year. The last time I mentioned it, everybody seemed to think I was nuts. :-) FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 routetbl289178 40961K 40961K 40960K 4357410 0 16,32,64,128,256 Well, I havent seen

Re: Route table leaks

1999-12-08 Thread Rodney W. Grimes
Have any of you been seeing route table leaks in -current? I noticed this week that cvsup-master.freebsd.org is suffering from them. I actually had to reboot it because it couldn't allocate any more. From the "vmstat -m" output: Memory statistics by type

Re: Route table leaks

1999-12-08 Thread Rodney W. Grimes
Please use 'netstat -rna' to get a listing of *all* the routes, including the temporary ones, not just the non-temporary routes. FWIW, another datapoint: set$ netstat -ran | wc -l 15 set$ vmstat -m | grep routetbl|grep K Type InUse MemUse

Re: MCA support

1999-12-09 Thread Rodney W. Grimes
My m77 has weird problems reading the floppy drive. I'm fairly sure this has everything to do with code in the loader/bootstrap that doesn't like the 2.88M drive. I used the 1.2M drive and it works great. I suspect a normal 1.44M drive would be good too. The loader just uses the

Re: MCA support

1999-12-09 Thread Rodney W. Grimes
My m77 has weird problems reading the floppy drive. I'm fairly sure this has everything to do with code in the loader/bootstrap that doesn't like the 2.88M drive. I used the 1.2M drive and it works great. I suspect a normal 1.44M drive would be good too. The loader just uses the

Re: HEADSUP: wd driver will be retired!

1999-12-10 Thread Rodney W. Grimes
We've been telling people for a long time that the wd driver would remain around even after ata went golden to support the ESDI systems still in service. That sounds like it is changing now. Real support for ESDI died with bad144... Error free ESDI disks are very rare, even the best in my

Re: HEADSUP: wd driver will be retired!

1999-12-11 Thread Rodney W. Grimes
... The scsi system has always been dynamic with a wiring *option* right from as far back as 2.0. CAM didn't change this. as far back as 386BSD and the patchkit. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: make world broken building fortunes

1999-12-13 Thread Rodney W. Grimes
On Mon, 13 Dec 1999 10:42:36 +0100, Marcel Moolenaar wrote: I think the easiest solution would be (instead of your patches of course): -STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin +STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games Only if you

Re: Speaking of moving files

1999-12-14 Thread Rodney W. Grimes
[Charset ISO-8859-1 unsupported, filtering to ASCII...] Ben Rosengart wrote in list.freebsd-current: On Tue, 14 Dec 1999, Matthew Dillon wrote: I think at one time or another all of us have missed *something* in /usr that wasn't in /. For example, disklabel -e doesn't

Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-14 Thread Rodney W. Grimes
[.] On a related subject: don't you think it's high time to end up this madness with MAKEDEV being a shell script, and reimplement it in C? Today, [.] *cough*DEVFS*cough* Yea... been hearing that for 4 years... one of it's big short comings is that it needs a persistent backing

  1   2   3   >