Jordan K. Hubbard wrote:
Um, can we get back to the subject at hand PLEASE? Who among you is
going to import the new routed? Garrett doesn't have testing
facilities for RIP, so it has to be someone else. Since Chuck also
appears to have boundless energy for this topic, might he be willing?
Sold, to the man in the long black coat! :)
Jordan K. Hubbard wrote:
Um, can we get back to the subject at hand PLEASE? Who among you is
going to import the new routed? Garrett doesn't have testing
facilities for RIP, so it has to be someone else. Since Chuck also
appears to have
On Tue, 27 Apr 1999, Warner Losh wrote:
In message 199904272310.raa06...@mt.sri.com Nate Williams writes:
: Someone submitted a patch that checked to see if the BIOS returned a
: value 64M, and if so to 'accept' it's value for the memory, since it's
: more likely to be correct. I'd like to
This small patch doesn't fix any major bugs (mostly the XXX in the
comment before cache_purge in kern/vfs_cache.c), but should be a step
towards allowing a dynamically sized vnode cache to be used. This is
done by eliminating the reliance on a vnode pointer/v_id pair as a
unique identification
Hello !
Blackbox doesn't work after recent changes in current, it complains:
/usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol
__vt_7filebuf
Unfortunately it doesn't compile also, autoconf(?) complains about
C++ compilator and thinks that it cannot generate executables.
--
auth 9b0472d2 subscribe freebsd-current bjo...@transint.is
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Hi,
In the great new ATA device driver framework (thanks Soren) there seems
to be a problem reported before by Stephen:
Stephen Hocking-Senior Programmer PGS Tensor Perth wrote:
On my machine, a kernel newer than one built on the 22nd will not complete
booting, panicing about not being
Hi,
I have three hosts with -current, all with the new ATA in function.
Booting the same kernel produces different results on all of them wrt
root file system mounting:
- one reports 'changing root device to wd0s3a'
- one reports 'changing root device to wd0s3a' followed by 'changing
root
On Tue, 27 Apr 1999, Jordan K. Hubbard wrote:
Um, can we get back to the subject at hand PLEASE? Who among you is
going to import the new routed? Garrett doesn't have testing
facilities for RIP, so it has to be someone else. Since Chuck also
appears to have boundless energy for this topic,
Is it just me, or is vmstat -m getting very confused in the last few
days?
julian
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Soren Schmidt wrote:
Hmm, could you mail me the output of fdisk disklabel from those tree
machines, with indication of how they behave ??
I'm unable to reproduce those errors here, but this might bring the
details I need to figure it out...
Certainly. First the working machine (reports
GateD is *very* unfriendly. It is user-unfriendly and it is
OSS-unfriendly. ...
... Also, the older, more OSS friendly versions of gated have too
many bugs to be useable as a base. The OSPF implementation in it
wasn't really fixed until late last year.
I can vouch for that... again,
Of all the gin joints in all the towns in all the world, Matthew Dillon
had to walk into mine and say:
(fanfair!)
(Darth Vader's imperial march theme)
NFS Patch #8 for -current is now available. This patch fixes serious bugs
w/ NFS/TCP. Probably not *all* the failure
: Someone submitted a patch that checked to see if the BIOS returned a
: value 64M, and if so to 'accept' it's value for the memory, since it's
: more likely to be correct. I'd like to apply it to -current, but I'm
: not sure of the political ramifications
I think that it would
-Original Message-
From: Bill Paul [mailto:wp...@skynet.ctr.columbia.edu]
Sent: 28 April 1999 14:27
To: dil...@apollo.backplane.com
Cc: hack...@freebsd.org; curr...@freebsd.org
Subject: Re: NFS Patch #8 for current available - new TCP fixes
Of all the gin joints in all the towns
With the current sources, there seems to be a problem with the Adaptec
2940U2W driver when using USB.
Whenever I try to boot a kernel with the USB driver, the boot process
gets to the Waiting 15 seconds for SCSI devices to settle and stops.
If I compile a kernel with an nearly identical config,
On Thu, Apr 29, 1999 at 12:48:58AM +0930, Mark Newton wrote:
Does anyone know what has happened to cvsup.au.freebsd.org?
I think a disk has died. I'm on leave for a couple of weeks, and haven't
had a chance to go into work to check up on it properly.
David
To Unsubscribe: send mail to
Aagh! As of last-night's current (Tuesday), *NO* C++ program that
links against libstdc++ works now. All of them come up with this
error, and recompilation doesn't help :-(
On my machine, this killed the entire KDE system. All of those
programs come up with the error:
/usr/libexec/ld-elf.so.1:
Matthew Dillon dil...@apollo.backplane.com writes:
Given the choice between OSPF and RIP1/2, OSPF is far superior
even on 'simple' networks. It is effectively an open protocol,
like BGP.
Matt, can you clarify what you mean by open here? I know it's
what the O in OSPF stands for, but in what
Hi:
I am seeing the same thing on a ASUS P2B with a Adaptec 2940??
controller.
Rick
- Original Message -
From: e...@habatech.no
To: freebsd-current@FreeBSD.ORG
Sent: Wednesday, April 28, 1999 11:38 AM
Subject: Problems with ahc (2940U2W) and USB
With the current sources, there
I am running 4.0-current SMP of Apr 21 16:51:36 1999.
Time appears to be drifting very fast, ~300 sec in 8 hours. dmesg and config
attached at the end. I am using CLK_USE_I8254_CALIBRATION.
On 27 Apr at about 2000, the system appeared to freeze for several
seconds, while lightly loaded, one
In message 199904272349.taa28...@lor.watermarkgroup.com, Luoqi Chen writes:
I'm about to commit the SMP vmspace sharing patch (the %fs approach). All
kernel modules will need to be recompiled. Recompilation is not neccessary
for user land applications including ps, libkvm and friends.
In
In message 199904281602.jaa17...@ix.netcom.com, Thomas Dean writes:
I am running 4.0-current SMP of Apr 21 16:51:36 1999.
Time appears to be drifting very fast, ~300 sec in 8 hours. dmesg and config
attached at the end. I am using CLK_USE_I8254_CALIBRATION.
Try to remove that option, if your
My 2 x 233MHz PPro has improved make world time by about 100 seconds
out of 5000s = 2 %
Not bad...
Poul-Henning
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Poul-Henning Kamp wrote:
My 2 x 233MHz PPro has improved make world time by about 100 seconds
out of 5000s = 2 %
Not bad...
Poul-Henning
I assume your benchmarking the recent changes Luoqi made to SMP?
--
Steve
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe
Some extra information on tape problems:
FreeBSD neunacht.netgsi.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Apr 22
16:50:33 EDT 1999 root@:/m/src/sys/compile/NEUNACHT i386
This is SMP machine with scsi only.
The tape drive is an EXABYTE-8200.
When doing tape IO that lasts for an extend period
[regarding RTC vs. BIOS selection algorithm]
I don't think this is complete, because I think (don't know) that many
older BIOS's only reported up to 64M of memory, so if you had more than
64M in the box it didn't report it.
The RTC extmem cannot report 64 MB either. In fact, the RTC extmem
is
We had this discussion last September, along with Mike Smith.
We discussed using the calibration stuff in config, and not to use
CLK_CALIBRATION_LOOP.
It was noted the 8254 was unstable and TSC could not be used to
improve it.
As a result of the conversation, I wound up with
My 2 x 233MHz PPro has improved make world time by about 100 seconds
out of 5000s = 2 %
My dual 200MHz PPro worldstone also improved almost 3 minutes
(173 seconds) after Luoqi's SMP change.
I think it's good improvement.
Tammy
To Unsubscribe: send mail to majord...@freebsd.org
with
In message 199904281625.maa05...@lor.watermarkgroup.com, Luoqi Chen writes:
In this %fs approach, per-processor private pages are no longer mapped at
identical virtual address for each cpu, instead a new segment descriptor
(%fs)
is setup to access per-cpu global variables like curproc.
The amber LED on exabytes typically means 'drive needs cleaning'. Exabyte
drives should be cleaned once or twice a week depending on how heavily
you use them. If an exabyte drive is not cleaned on a regular basis, the
transfer rate will drop steadily as the drive is forced to
On Wed, 28 Apr 1999, Poul-Henning Kamp wrote:
In message 199904281625.maa05...@lor.watermarkgroup.com, Luoqi Chen writes:
In this %fs approach, per-processor private pages are no longer mapped at
identical virtual address for each cpu, instead a new segment descriptor
(%fs)
is setup
Fwiw:
The patch below unbreaks -current for me.
[Luoqi Chen's message 199904270645.caa21...@lor.watermarkgroup.com below]
This broke routing, part of the route domain init needs to be done after
all domains are attached. It happened that the new kernel I just made
listed routedomain before
It seems Tamiji Homma wrote:
My 2 x 233MHz PPro has improved make world time by about 100 seconds
out of 5000s = 2 %
My dual 200MHz PPro worldstone also improved almost 3 minutes
(173 seconds) after Luoqi's SMP change.
Yep, I see the same here, good job!!
-Søren
To Unsubscribe: send
I know this is a little late ... but I don't suppose there might be a
way to lock a TLB entry in place? That would solve the problem too.
Baring that, %fs is the way to go.
I am happily compiling up a new SMP kernel as we speak :-).
-Matt
Are these changes going to be committed to -stable?
Tx
-Original Message-
From: owner-freebsd-curr...@freebsd.org
[mailto:owner-freebsd-curr...@freebsd.org]on Behalf Of Tamiji Homma
Sent: Wednesday, April 28, 1999 1:16 PM
To: p...@critter.freebsd.dk
Cc: curr...@freebsd.org
Matthew,
Thanks I should have been more clear.
The amber LED on 8205s and 8505s and any of the half hight drives blink when
they need cleaning. This is the original 8200 full hight drives. They
have no cleaning indicator.
The drive is cleaned every monday before the amflush. We use exabyte
:Matthew Dillon dil...@apollo.backplane.com writes:
:
: Given the choice between OSPF and RIP1/2, OSPF is far superior
: even on 'simple' networks. It is effectively an open protocol,
: like BGP.
:
:Matt, can you clarify what you mean by open here? I know it's
:what the O in OSPF stands for,
On Wed, 28 Apr 1999, Nate Williams wrote:
: Someone submitted a patch that checked to see if the BIOS returned a
: value 64M, and if so to 'accept' it's value for the memory, since it's
: more likely to be correct. I'd like to apply it to -current, but I'm
: not sure of the
Hi
Just wondering if the new swatch clock has its way into the date command...
_
Lauri Laupmaa
...speaking for myself only...
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
On Wed, 28 Apr 1999, Matthew Dillon wrote:
:Matthew Dillon dil...@apollo.backplane.com writes:
:
: Given the choice between OSPF and RIP1/2, OSPF is far superior
: even on 'simple' networks. It is effectively an open protocol,
: like BGP.
:
:Matt, can you clarify what you mean by open
On Wed, 28 Apr 1999, Bill Paul wrote:
Of all the gin joints in all the towns in all the world, Matthew Dillon
had to walk into mine and say:
(fanfair!)
(Darth Vader's imperial march theme)
NFS Patch #8 for -current is now available. This patch fixes serious
bugs
Hello ...
The burn* scripts in /usr/share/examples/atapi try to use wormcontrol for
some reason, which obviously doesn't work. Should we just dump them, or
does someone have one that uses mkisofs/cdrecord that would be
appropriate?
Doug White
Internet:
It seems Doug White wrote:
Hello ...
The burn* scripts in /usr/share/examples/atapi try to use wormcontrol for
some reason, which obviously doesn't work. Should we just dump them, or
does someone have one that uses mkisofs/cdrecord that would be
appropriate?
What planet are you from ??
:couldn't possibly be more open than RIP.
:
:
: OSPF has been around for a long time.
:
:But RIP is older, and was the first routing scheme.
Which means nothing. RIP was designed for a time when networks
were simple. It has no multipath capabilities, it can *barely*
handle
I can't quite figure why they stuck the word open in there, because it
couldn't possibly be more open than RIP.
Probably because it was (at the time) in heavy competition with the OSI
IS-IS routing protocol. Those standards were *not* openly available. (I
believe they are now.)
Steinar Haug,
: I can't quite figure why they stuck the word open in there, because it
: couldn't possibly be more open than RIP.
:
:Probably because it was (at the time) in heavy competition with the OSI
:IS-IS routing protocol. Those standards were *not* openly available. (I
:believe they are now.)
:
Umm ... OK, I thought you were saying that OSPF and BGP are open,
whereas RIP v1 and v2 are not. In that context, I wasn't sure what
you meant by open. If open means freely downloadable spec, then
presumably all of the above are open. So never mind :-).
Jim Shankland
NLynx Systems, Inc.
To
On Wed, Apr 28, 1999 at 12:14:03PM -0700, Matthew Dillon wrote:
:Probably because it was (at the time) in heavy competition with the OSI
:IS-IS routing protocol. Those standards were *not* openly available. (I
:believe they are now.)
:
:Steinar Haug, Nethelp consulting, sth...@nethelp.no
In message 199904281914.maa08...@apollo.backplane.com, Matthew Dillon writes:
: I can't quite figure why they stuck the word open in there, because it
: couldn't possibly be more open than RIP.
:
:Probably because it was (at the time) in heavy competition with the OSI
:IS-IS routing protocol.
I consider ISIS dead these days, though I'm sure there are people who
still swear by it.
As far as I know, there is *active* development of IS-IS these days, see
for instance:
IS-IS Optimized Multipath (ISIS-OMP), Tony Li, Curtis Villamizar,
02/23/1999,
On Wed, 28 Apr 1999 sth...@nethelp.no wrote:
I can't quite figure why they stuck the word open in there, because it
couldn't possibly be more open than RIP.
Probably because it was (at the time) in heavy competition with the OSI
IS-IS routing protocol. Those standards were *not* openly
As Christopher T. Johnson wrote ...
Some extra information on tape problems:
FreeBSD neunacht.netgsi.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Apr 22
16:50:33 EDT 1999 root@:/m/src/sys/compile/NEUNACHT i386
This is SMP machine with scsi only.
The tape drive is an EXABYTE-8200.
When
Hi,
At 11:42 am -0700 28/4/99, Doug White wrote:
The burn* scripts in /usr/share/examples/atapi try to use wormcontrol for
some reason, which obviously doesn't work.[etc]
Er, I think it does. It's SCSI/CAM which has lost the worm device, not ATAPI.
See also misc/10351.
--
Bob Bishop
After doing a make world today and compiling a new kernel, the Linux
netscape 4.51 does not work anymore. It immediately core dumps:
/home/blaz netscape
Illegal instruction (core dumped)
/home/blaz gdb /usr/local/netscape-4.51/communicator-4.51.bin
communicator-4.5.
core
GDB is free software and
: I can't quite figure why they stuck the word open in there, because it
: couldn't possibly be more open than RIP.
:
:Probably because it was (at the time) in heavy competition with the OSI
:IS-IS routing protocol. Those standards were *not* openly available. (I
:believe they are now.)
:
On Wed, 28 Apr 1999, Blaz Zupan wrote:
After doing a make world today and compiling a new kernel, the Linux
netscape 4.51 does not work anymore. It immediately core dumps:
Sigh. Ignore my mail. I failed to follow the first rule of posting: think
before you post. I cvsupped between make world
On Wed, Apr 28, 1999 at 11:19:17AM -0700, Matthew Dillon wrote:
I know this is a little late ... but I don't suppose there might be a
way to lock a TLB entry in place? That would solve the problem too.
Baring that, %fs is the way to go.
Unfortunately, on the x86, the answer is
As Christopher T. Johnson wrote ...
REGARDLESS!
The drive is reporting an error condition and that error is NOT
getting back to user land. I've verified the problem with amdump
Oh? Where/what is the error, does the console tell you?
amflush and dd. In ALL cases once the
As Matthew Dillon wrote ...
The amber LED on exabytes typically means 'drive needs cleaning'. Exabyte
drives should be cleaned once or twice a week depending on how heavily
you use them. If an exabyte drive is not cleaned on a regular basis, the
transfer rate will drop
In article 199904271932.naa01...@zen.alb.khoral.com,
Steve Jorgensen st...@khoral.com wrote:
I cvsup'ed and installed yesterday morning it's the third
cvsup I've done since egcs went in, so I know it's working
ok. Anyway, I decided to update my XFree86 installation,
and
As Christopher T. Johnson wrote ...
REGARDLESS!
The drive is reporting an error condition and that error is NOT
getting back to user land. I've verified the problem with amdump
Oh? Where/what is the error, does the console tell you?
Sorry, no error reported, just the lights.
That sounds like a bug. But it could be CAM not understanding that the
8200 firmware went to Nowhere-land. If I got a dime for each Exabyte
lockup..
Yep, been there done that. But these drives have been rock solid. It is
not the case of putting in a new, unknown drive and finding
On Wed, 28 Apr 1999 14:34:51 -0400 (EDT), Chuck Robey chu...@picnic.mat.net
said:
I can't quite figure why they stuck the word open in there, because it
couldn't possibly be more open than RIP.
Because a previous link-state (aka shortest-path-first) routing
protocol had been deployed which
In reply:
Hi
Just wondering if the new swatch clock has its way into the date command...
I'd rather that it wouldn't. Swatch is pulling a marketing stunt,
plain and simple. Something to toss in the closet with the pet rock a
year from now.
jim
--
All opinions expressed are mine, if you
:On Wed, Apr 28, 1999 at 11:19:17AM -0700, Matthew Dillon wrote:
: I know this is a little late ... but I don't suppose there might be a
: way to lock a TLB entry in place? That would solve the problem too.
: Baring that, %fs is the way to go.
:
:
:Unfortunately, on the x86, the
With the current sources, there seems to be a problem with the Adaptec
2940U2W driver when using USB.
This isn't likely to be related to the 2940 per se.
Check your BIOS settings related to USB; make sure you have it properly
turned on and have an interrupt allocated to the USB port. Try
I'm sorry- I missed the front end of this. I've had pretty good luck with
getting the 8200 to work. What f/w level are you at for the 8200?
-matt
Matt, it isn't a tape drive problem. Nor is it directly and exabyte problem.
It is a problem where an error from the tape drive is
:Umm ... OK, I thought you were saying that OSPF and BGP are open,
:whereas RIP v1 and v2 are not. In that context, I wasn't sure what
:you meant by open. If open means freely downloadable spec, then
:presumably all of the above are open. So never mind :-).
:
:Jim Shankland
:NLynx Systems, Inc.
I cvsupped from 3.1-RELEASE today to 4.0-CURRENT and since then PCM sound
has been screwed. Im using a crystal sound card, anyone having similar
problems?
Cheers
Andrew
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
:For parts that don't support arbitrary alignment, you have to copy.
:Now, in some of the drivers that I ported to the alpha, I only copied
:the first small section of the packet in order to get the IP header
:aligned (since failing to do this causes an unaligned access trap in
:the IP code). This
I get no pcm devices configured; this happened after cvsupping a week or
so. (I cvsup every night).
The soundcard gets probed as a AudioPCI ESS1370
dmesg:
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of
Btw, why does boot write [*UTP*] ?
The card is working nicely with bnc.
ep0 at port 0x300-0x30f irq 11 on isa0
ep0: utp/bnc[*UTP*] address 00:60:08:09:c8:d9
ep0: interrupting at irq 11
device ep0 at isa? port 0x300 irq 11
Leif
To Unsubscribe: send mail to majord...@freebsd.org
with
On Wed, 28 Apr 1999, Garrett Wollman wrote:
On Wed, 28 Apr 1999 14:34:51 -0400 (EDT), Chuck Robey
chu...@picnic.mat.net said:
I can't quite figure why they stuck the word open in there, because it
couldn't possibly be more open than RIP.
Because a previous link-state (aka
As Christopher T. Johnson wrote ...
As Christopher T. Johnson wrote ...
REGARDLESS!
The drive is reporting an error condition and that error is NOT
getting back to user land. I've verified the problem with amdump
Oh? Where/what is the error, does the console tell you?
Aagh! As of last-night's current (Tuesday), *NO* C++ program that
links against libstdc++ works now. All of them come up with this
error, and recompilation doesn't help :-(
You have done a *FULL* CVSup and `make world'? You have then recopiled
any C++ libs from ports or private sources?
--
Open (according to Lenny Kleinrock) meant available; thus OSPF
was supposed to mean Available, shortest path first. But, then again,
these meanings get changed with time. Open is now a codeword for
GNU/GPL/intellectual rights unencumbtered software. For OSPF, it was
simply a description of an
On Wed, Apr 28, 1999 at 02:48:56PM -0700, Matthew Dillon wrote:
...
There might be less confusion with %fs if we simply use it as a
'cpu number' index and then make all the cpu-dependant variables
standard arrays. i.e. instead if 'struct proc *curproc' we would
have
On Wed, Apr 28, 1999 at 02:34:51PM -0400, Chuck Robey wrote:
And you didn't know that the RIP spec is even older, and was publicly
available via an RFC (the same as OSPF?)
But, of course, RIP sucks in many well-known ways.
I can't quite figure why they stuck the word open in there, because it
:I don't think the current approach with %fs is that confusing. :-) You
:can view it as an optimization of
:
: struct per processor data {
: struct proc *curproc;
: ...
: } ppd[NCPUS];
:
: some_func()
: {
: ... ppd[MYCPU]-curproc
At 03:39 PM 4/28/99 -0700, David O'Brien wrote:
Aagh! As of last-night's current (Tuesday), *NO* C++ program that
links against libstdc++ works now. All of them come up with this
error, and recompilation doesn't help :-(
You have done a *FULL* CVSup and `make world'? You have then recopiled
Add me to the list of people seeing this problem. I have an ASUS P2B-S with
onboard Adaptec 7890. I have been seeing the problem on and off since December
of last year. One time it boots and the next time it doesn't. Once the disk is
hung, the reset switch or power cycling are the only ways to
I just encountered this:
=== gnu/usr.bin/cc/doc
makeinfo -I /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc -I
/u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/cp --no-split -I
/u3/src/gnu/usr.bin/cc/doc -I /u3/src/gnu/usr.bin/cc/doc
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
On Thu, Apr 29, 1999 at 03:19:37AM +0200, Jean-Marc Zucconi wrote:
I just encountered this:
=== gnu/usr.bin/cc/doc
makeinfo -I /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc -I
/u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/cp --no-split -I
/u3/src/gnu/usr.bin/cc/doc -I
/usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined
symbol __vt_7filebuf
I'm rather tied up until Sunday. So it will be few days unti I can
really take a look at this. Until then, patches gladly accepted.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe:
On Wed, 28 Apr 1999, David O'Brien wrote:
# /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined
# symbol __vt_7filebuf
#
# I'm rather tied up until Sunday. So it will be few days unti I can
# really take a look at this. Until then, patches gladly accepted.
Remember you asked. :-)
On Wed, 28 Apr 1999, Soren Schmidt wrote:
Hi,
I have three hosts with -current, all with the new ATA in function.
Booting the same kernel produces different results on all of them wrt
root file system mounting:
- one reports 'changing root device to wd0s3a'
- one reports 'changing
Here is the dmesg output from a boot -v on my machine. I don't believe
that I have ever had the USB ports configured in my kernel. They do
have an IRQ allocated in the BIOS though.
Jim Bloom
bl...@acm.org
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
In reply:
Btw, why does boot write [*UTP*] ?
The card is working nicely with bnc.
ep0 at port 0x300-0x30f irq 11 on isa0
ep0: utp/bnc[*UTP*] address 00:60:08:09:c8:d9
ep0: interrupting at irq 11
device ep0 at isa? port 0x300 irq 11
Leif
good question. when were your sources built?
This is with the latest cvs tree checked out. For -current. At a guess
I would say that it's related to Luoqi's recent checkin.
/FreeBSD/FreeBSD-4.x/src/gnu/usr.bin/gdb/gdb/freebsd-nat.c: In function
`fetch_core_registers':
On Wed, 28 Apr 1999, Matthew Dillon wrote:
:couldn't possibly be more open than RIP.
:
:
: OSPF has been around for a long time.
:
:But RIP is older, and was the first routing scheme.
Which means nothing. RIP was designed for a time when networks
were simple. It has
On Wed, 28 Apr 1999, Chris Dillon wrote:
On Wed, 28 Apr 1999 sth...@nethelp.no wrote:
I can't quite figure why they stuck the word open in there, because it
couldn't possibly be more open than RIP.
Probably because it was (at the time) in heavy competition with the OSI
IS-IS
Oops. I take it back. It worked just fine. I was looking at the
wrong xterm!
-Matt
Matthew Dillon
dil...@backplane.com
:
:This is with the latest cvs tree
On Wed, 28 Apr 1999, Jim Bryant wrote:
good question. when were your sources built? i'm running a kernel
from Thu Apr 8 10:40:17 CDT 1999.
ep0 at 0x210-0x21f irq 10 on isa
ep0: aui/bnc[*BNC*] address 00:20:af:d2:e4:ae
Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still
I get a thoroughtly reproducible (in fact, utterly non-un-reproducible)
panic on boot of recent -CURRENTs. It did this on a cvsup from maybe 2,
3 days ago, and again with one done ~4pm CDT today.
Note: all these messages are hand-copied, this machine isn't in a
situation where it's easy to put a
In reply:
On Wed, 28 Apr 1999, Jim Bryant wrote:
good question. when were your sources built? i'm running a kernel
from Thu Apr 8 10:40:17 CDT 1999.
ep0 at 0x210-0x21f irq 10 on isa
ep0: aui/bnc[*BNC*] address 00:20:af:d2:e4:ae
Well, I'd chalk it up to buggy 3com h/w myself.
In message 199904282134.qaa37...@argus.tfs.net, Jim Bryant writes:
In reply:
Hi
Just wondering if the new swatch clock has its way into the date command...
I'd rather that it wouldn't. Swatch is pulling a marketing stunt,
plain and simple. Something to toss in the closet with the pet rock a
98 matches
Mail list logo
