> On 07/12/16 13:27, Glen Barber wrote:
> > On Tue, Jul 12, 2016 at 07:17:19AM +0100, Matthew Seaman wrote:
> >> I just upgraded my main machine to 11-STABLE. Things are mostly working
> >> fine -- however I did notice that the new iovctl rc script is apparently
> >> enabled by default. That
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
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
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
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
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
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
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
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
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
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
...
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
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
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
[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
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
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
: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
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
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
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.
...
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
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
[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
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
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,
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
{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
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
:
: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
:
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
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
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
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
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:
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
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
On Thu, 24 Feb 2000 10:21:31 -0700, Chris Wasser [EMAIL PROTECTED] said:
The theoretical maximum for 100BaseT-FDX (which is 200Mbps) is 25MB/s
(megabytes per second), 100BaseT-TX is 12MB/s [FYI: Mbps-MB/s you divide
by 8] I realize my punctuation may be off, but there you are.
On Thu, Feb 24, 2000 at 02:07:40PM -0500, Garrett Wollman wrote:
On Thu, 24 Feb 2000 10:21:31 -0700, Chris Wasser [EMAIL PROTECTED] said:
Assuming you mean ``100BASE-T (half duplex)'' here... This is not
quite right. In a CSMA/CD medium access protocol, like that used by
Ethernet, the
On Fri, Feb 25, 2000 at 01:25:59AM -0800, Rodney W. Grimes wrote:
There was a patch of DC21143 chips it seems that has a very strange
thermal problem. Can you tell me what your hub link lite is doing
when you see this major slow down?
Nope ... as this machine is connected directly
Perhaps this would be of interest in CURRENT issues:
We have several servers that we plan on deploying across the US. Their
purpose in life is network status and monitoring. The hardware profiles
are exactly the same...
Currently, we're using DD to mirror a disk image onto a new
On Fri, 25 Feb 2000 01:13:51 -0800 (PST), "Rodney W. Grimes"
[EMAIL PROTECTED] said:
[I wrote:]
quite right. In a CSMA/CD medium access protocol, like that used by
Ethernet, the actual capacity of the link is always(*) somewhat less than
100%; the exact value depends on t
On Fri, 25 Feb 2000 09:53:37 -0800 (PST), "Rodney W. Grimes"
[EMAIL PROTECTED] said:
I specifically excluded P(coll) by stating point to point or effectively
point to point via switching.
Rod, please bother to READ what people write before spewing nonsense.
I did read i
On Fri, 25 Feb 2000 11:08:24 -0800 (PST), "Rodney W. Grimes"
[EMAIL PROTECTED] said:
The maximum for full-duplex is utterly irrelevant, since the bounds on
performance for half-duplex Ethernet networks come from CSMA/CD.
I will say it one last time, duplex falls out of the
In article [EMAIL PROTECTED], Rodney W. Grimes
[EMAIL PROTECTED] wrote:
A much faster way to do this is to just dd the first few megabytes
of the disk (dd if=foo of=/dev/rXXd bs=32768 count=1024). Then use
dump | restore to populate the disk.
Do you run newfs on the receiving disk
On Tue, 22 Feb 2000 11:06:07 -0800 (PST), "Rodney W. Grimes"
[EMAIL PROTECTED] said:
IBM Hard drives...
If you can actually get them Last time I bought a drive we
weren't able to get IBM in any reasonable timeframe and ended up with
a Seagate instead. (And that Chee
Hmmm. I'm beginning to wonder if openssl shouldn't just be backed-out
at this point. The situation with RSA makes this far more problematic
than I think anyone first thought, and I've seen a lot of breakage so
far for what appears to be comparatively little gain over what we had
before
Giorgos Keramidas writes:
Is there some way to ifconfig up a dummy ethernet interface, one that
will work like the loopback one (lo0) on FreeBSD?
If you want an interface that loops back, you can have more than
one loopback interface (lo0, lo1, lo2, ...).
If you want an interface that
Good analysis deleted...
src/usr.bin/xinstall could probably have been named src/usr.bin/install,
but PROG has to be xinstall regardless. I guess they kept the two as
xinstall for consistancy and in case there were other gotcha's like this.
But you forgot what happens if you have a ``file''
"Rodney W. Grimes" wrote:
Good analysis deleted...
src/usr.bin/xinstall could probably have been named src/usr.bin/install,
but PROG has to be xinstall regardless. I guess they kept the two as
xinstall for consistancy and in case there were other gotcha's like this.
...
Starting an 'fsck' results in:
cage:[/] # fsck /scratch
** /dev/da1s1g
** Last Mounted on /scratch
** Phase 1 - Check Blocks and Sizes
PARTIALLY TRUNCATED INODE I=16
SALVAGE? [yn] ^C
* FILE SYSTEM MARKED DIRTY *
Next step is run the ``save''
On Thu, 27 Jan 2000 00:23:23 PST, "David O'Brien" wrote:
I think what you really want is:
sed 's/^\([^:#@+-]*\):[^:]*:/\1:(password):/'
Eeek, I don't know why I sent you that. It should have been:
sed 's/^\([ +-][^+-][^:]*\):[^:]*:/\1:(password):/'
IMNSO
On Thu, 27 Jan 2000 13:28:10 -0800, "Jordan K. Hubbard" [EMAIL PROTECTED] said:
3. On the first reboot after installing, the keyboard was in a funny
state.
Urk, can't reproduce it. I need a reproducible sequence of operations
before we'll have any hope of tackling this one.
On 27-Jan-00 David O'Brien wrote:
I would appreciate it if those that want things changed would please try
Sheldon's `sed' expression below and report back how it worked for you.
That will expose passwords of users whose entries are commented out,
My awk script does not have that
In message [EMAIL PROTECTED] "David O'Brien" writes:
: BTW, I'm getting numbers that are 2x bigger than before :-(.I had
: makebuildworld down to around 1:20 at one point, but now it is 2:40.
:
: Which compilers for both times?
What ever was on -current as of 2.5 years ago. This
% %It seems Russell L. Carter wrote:
% % %It seems Russell L. Carter wrote:
% % %
% % % I swapped out my motherboard and am seeing this now:
%...
%
%
% )(*$#%$# stupid magazine benchmarkers never actually test
% things like IO... gr
%
%We in the computer hardware business
On Mon, Jan 24, 2000 at 02:17:54PM +0100, Brad Knowles wrote:
At 11:34 PM +1300 2000/1/22, Joe Abley wrote:
This should give you a relative performance metric between the servers
you measured, hopefully with local network performance variations
cancelled out by the fact that all
Hi David,
John can implement a ping echo packet protocol for cvsup whose
response can have "cool" information on the server. Steven's
book on Networking already has the code for doing network latency
calculations . It is more like if John has the time to implement
such scheme
You
Hi David,
John can implement a ping echo packet protocol for cvsup whose
response can have "cool" information on the server. Steven's
book on Networking already has the code for doing network latency
calculations . It is more like if John has the time to implement
such
On Fri, 21 Jan 2000, David O'Brien wrote:
On Fri, Jan 21, 2000 at 07:03:51PM -0500, Chuck Robey wrote:
I don't know ... I think it might be a good idea for the cvsup client to
make a connection to a cvsup master, get redirected from that master to
the actual handler of the
%It seems Russell L. Carter wrote:
% %It seems Russell L. Carter wrote:
% %
% % I swapped out my motherboard and am seeing this now:
...
)(*$#%$# stupid magazine benchmarkers never actually test
things like IO... gr
We in the computer hardware business have a better name for
"Rodney W. Grimes" wrote:
...
Independent of order of export/mounting the dead lock occurs. Cross
mounting via NFS is a verbotten thing in the sysadmin world of production
systems. :-) I have had to fix it at several sites admin'd by newbies...
I'm not sure you
Sorry, I will slow down my reading and stop flipping 2^10 into 10^3.
From: Rodney W. Grimes [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 12, 2000 9:53 PM
[in regards to a previous post preferring base-10 for K and M units...]
I'm sorry but I would find it non-obvious and more
: Sometimes we just want to nfs-mount things on the same
: machine.
:
:Sick, poor in performance and the wrong tool for the job.
:See mount_null(8) for more details on how to do it right.
:
:
: One more example: I don't like /var/news so I mount locally
: /var/news
: to /archive/news
Hi,
I think we should move portmap(8) to /sbin for the following reason:
portmap(8) and therefore mountd(8) should be started before
the nfs filesystems get mounted. But because portmap(8) is in
/usr/sbin , users with a nfs mounted /usr filesystem or with
diskless filesystems will
Hi,
should not have to run either, *even* for diskless boot.
What's all this about loopback mounts in fstab about? What does
that have to do with diskless startup?
Ok. I just rethought everything. It seems that a move is
unnecessary because:
- Sharity light and
On Wed, Jan 12, 2000 at 01:23:14AM -0800, Rodney W. Grimes wrote:
Also moving them to pass1 would bring up nfs exports before we
brought up nfs mounts. syslogd would not be running to catch
Shouldn't nfs exports happen before nfs mounts, so that machines
which have nfs
"Rodney W. Grimes" wrote:
[..]
So no disk, so just what is it that you are exporting???
Just a comment:
I've seen scenarios where a local disk is attached holding a kernel,
bootblocks loader etc, but otherwise booting from a server over NFS. And
it exported the rest of
[Charset iso-8859-1 unsupported, filtering to ASCII...]
I'm sorry but I would find it non-obvious and more confusing. When ls or a
similar disk/memory utility tells me xxxK or xxxM, I would expect it to be
in 2^10 or 2^20 units. To appear otherwise would surprise me.
I guess you get
I'm currently dealing with an increasing set of *very* large files,
most of them in the order of gigabytes. It becomes impossible to
figure the size of a file with ls -l with 9 or more digits displayed.
I would propose a new flag to ls which will together with option -l
change the unit to
[Charset windows-1252 unsupported, skipping...]
Arghh... windblows...
I'm currently dealing with an increasing set of *very* large files,
most of them in the order of gigabytes. It becomes impossible to
figure the size of a file with ls -l with 9 or more digits displayed.
I would
At 2:49 PM -0800 1/11/00, Rodney W. Grimes wrote:
Another thing that ``works for me''. Only make it ki, mi, and gi
to fit with the new binary mode international appreviation standards,
unless of cource you use base 10 divisors.
Why not KB, MB or GB, since that's what you're
In article [EMAIL PROTECTED],
james [EMAIL PROTECTED] wrote:
It's interesting though how i had no ipf rules whatsoever, yet it
introduced so much latency, as Alexander has pointed out in another email.
Why is ipf so slow? I was planning on switching from ipfw/natd to
ipf/ipnat,
...
I strongly suggest to not release 4.0 till the IPv6 import has been finished.
Beside the need for IPv6 it would be wrong to ship a release with a half-
complete implementation.
I expect every person that has made similiar statements here and bore
all the developers with the additional
In message [EMAIL PROTECTED], Luigi Rizzo writes:
One of the things I would do to optimize ipfw is:
- instead of keeping one list with all the rules, split the list (the
internal one) by interface and by direction (one list for ed1 incoming,
one list for ed1 outgoing, etc.).
one
Where do I look for new man pages? I would like to read those for the
new ata driver and for ntpd. They were not created during a build
world some 5 days ago. And I cannot find them in
/usr/src/share/man/man4, where I would expect man ata/ad in any case.
Sos already answered about ata/ad,
In message [EMAIL PROTECTED], Karl Denninger writes:
On Sat, Jan 01, 2000 at 11:11:51AM +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Karl Denninger writes:
This is not a port, its part of the RELEASE!
Its several YEARS old, and doesn't work right - you get lots of
...
I'm pretty sure that the box was getiting receive interrupts because
every time I sent a packet to it from the outside systat -vm showed
a PCI interrupt for the network device. However 'netstat -in 1' did
not show the statistics for the received packets until 64 had
...
(200-300 MHz) clients. That's *with* packet loss (for some reason when
my fxp ethernets pump data out that quickly they tend to cause packet
loss in other parts of my HUBed network, which I find quite annoying).
Interesting you should say that I've been playing with some
On Fri, Dec 17, 1999 at 10:47:59AM +0200, Vallo Kallaste [EMAIL PROTECTED]
wrote:
[snip]
It's very annoying, I have only fair experiences with dump/restore back
to the 2.2.2 days until now.
Sorry for the long post and partially? false alert.
Something in my mind waked up and I
Hm, if correct, Orca would make a good codename for a sysadm tool:
Ordinary Ramblers Can [now] Admin [FreeBSD]
Someone pointed out that Orca was already taken The question NOW
is: Can you come up with a good acronym for "SHAMU"?
Easy...
Some Help for Another Misguided
[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
[.]
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
A person who really knew fsdb could do it /bin/fsdb, infact it's
And for everyone else ;-)
WARNING
Use this tool with extreme caution--you can damage an FFS file system
beyond what fsck(8) can repair.
Yea.. well...
fsdb /dev/rda0s1a
cd /dev/
cd da0s1g
chown root
chgrp
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
...
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
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
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
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
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
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
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
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
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
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
"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
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
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
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
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
301 - 400 of 446 matches
Mail list logo
