:
:
: In message [EMAIL PROTECTED], Matthew Dillon writes:
:
: :NFS uses the kernel 'boottime' structure to generate its version id.
: :Now normally you might believe that this structure, once set, will
: :never change. The authors of NFS certainly make that assumption!
: :
: :Is
It seems Dave J. Boers wrote:
I am still having "disc contact lost messages" regularly too. I've been
posting about them on several occasions some time ago. I haven't been able
to pinn it down, however. IF they occur, they occur somewhere between 9:15
and 9:20 a.m. OR p.m. But they don't
It seems Soren Schmidt wrote:
It seems Dave J. Boers wrote:
I am still having "disc contact lost messages" regularly too. I've been
posting about them on several occasions some time ago. I haven't been able
to pinn it down, however. IF they occur, they occur somewhere between 9:15
In message [EMAIL PROTECTED], Kevin Day writes:
Ack, I was using this very same thing for several devices in an isolated
peer-to-peer network to decide who the 'master' was. (Whoever had been up
longest knew more about the state of the network) Having this change could
cause weirdness for me
On 15-Dec-99 Oliver Fromme wrote:
Alexander Langer wrote in list.freebsd-current:
gunzip has approx 106 kb, but you save about 50% per executeable.
-r-xr-xr-x 1 root wheel 4648 Jan 28 1999 /usr/bin/minigzip
It requires the 50Kb libz.so.2 though and some of libc.
On Thu, Dec 16, 1999 at 09:36:42AM +0100, Soren Schmidt wrote:
One more thing, do you have SMART enabled in your BIOS ??, if so
turn it off, and see if that changes anything...
I don't recall having it enabled; but I will check to make sure as soon as
I get home from work (which is still some
It seems Devin Butterfield wrote:
That's interesting...In my case it is quite easily reproduced (very
predictable). All I have to do is reboot and then run sysinstall and
when it probes the devices the disks time out. So far I have not been
able to get this behavior at any other time.
I
On Thu, Dec 16, 1999 at 03:29:30PM +0600, Max Khon wrote:
hi, there!
same here, dmesg output:
SNIP
ata_command: timeout waiting for interrupt
Mounting root from ufs:/dev/ad0s2a
ata0-master: ad_timeout: lost disk contact - resetting
ata0: resetting devices .. done
ata0-master: ad_timeout:
Hi Soren/group,
After spending a little time sniffing around in my BIOS I realized that
my BIOS (Award BIOS) defaults to disabling UDMA for both master and
slave and for some reason I never thought to check thisduh. Anyway
after setting this to "auto" for both master and slave the problem
hi, there!
On Thu, 16 Dec 1999, Dave J. Boers wrote:
Could you tell met the exact time on which these messages occurred?
Anywhere near 10:15 or 9:15 ?
nope. the time is unpredictable.
sometimes it can work more than a day without spilling out those messages
/fjoe
To Unsubscribe: send
It seems Devin Butterfield wrote:
Hi Soren/group,
After spending a little time sniffing around in my BIOS I realized that
my BIOS (Award BIOS) defaults to disabling UDMA for both master and
slave and for some reason I never thought to check thisduh. Anyway
after setting this to "auto"
Hi Soren,
No unfortunately it still fails with the patch and the UDMA disabled in
the BIOS.
I'd be happy to try anything else you can think of. :)
Thanks.
--
Regards, Devin.
Soren Schmidt wrote:
It seems Devin Butterfield wrote:
Hi Soren/group,
After spending a little time sniffing
This is a HEADSUP message to warn all current users that tha following is
being done:
- disable xntpd build
- enable ntp build
- removal of old xntpd/xntpdc binaries as they've been renamed
- modifications in /etc/defaults/rc.conf to take the new daemon into
account.
xntpd will be "cvs
On Thu, Dec 16, 1999 at 09:25:11AM +0100, Soren Schmidt wrote:
It seems Dave J. Boers wrote:
I am still having "disc contact lost messages" regularly too. I've been
posting about them on several occasions some time ago. I haven't been able
to pinn it down, however. IF they occur, they
On Thu, Dec 16, 1999 at 07:10:46AM -0600, Richard Seaman, Jr. wrote:
Dec 15 19:01:02 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting
Dec 15 19:01:02 test /kernel: ata0: resetting devices .. done
snipsnip
Dec 16 07:01:24 test /kernel: ata0-master: ad_timeout: lost disk
It seems Dave J. Boers wrote:
On Thu, Dec 16, 1999 at 07:10:46AM -0600, Richard Seaman, Jr. wrote:
Dec 15 19:01:02 test /kernel: ata0-master: ad_timeout: lost disk contact -
resetting
Dec 15 19:01:02 test /kernel: ata0: resetting devices .. done
snipsnip
Dec 16 07:01:24 test /kernel:
On Thu, Dec 16, 1999 at 03:02:24PM +0100, Soren Schmidt wrote:
Uhm, that wont be new WD drives, as they are exactly the same as
IBM drives give or take the label :)
Huh? That I didn't know. So you're saying that WD and IBM 18 Gb disks are
the same hardware?
My disk:
ad0: WDC
It seems Dave J. Boers wrote:
On Thu, Dec 16, 1999 at 03:02:24PM +0100, Soren Schmidt wrote:
Uhm, that wont be new WD drives, as they are exactly the same as
IBM drives give or take the label :)
Huh? That I didn't know. So you're saying that WD and IBM 18 Gb disks are
the same hardware?
You can also fool sh into running the *wrong* binary if if you have
two in showdowed paths:
#! /bin/sh
test -d foo1 || mkdir foo1
test -d foo2 || mkdir foo2
test -d foo2 || mkdir foo3
echo 'echo :one' foo1/run
echo 'echo :two' foo2/run
echo 'echo :three' foo2/run3
chmod a+x */run*
hash -r
Matthew Dillon writes:
And so Andrews bug report comes into the light! His poor client
(and mine once I reproduced the bug) got into a state, due to the
server returning a different version id for virtually every packet,
where it resent the same write data over the
I have the Enterprise 1400 Megaraid adapter with (currently 16M) on
it. I have tested the various modes of operation (different raid
levels and striping) and find it to be working well. My LVD array
consists of 8 18G Quamtum IV's.
Now... using vinum and either the 2940U2W (Adaptec LVD) or the
At 10:52 AM -0500 1999/12/16, David Gilbert wrote:
Now... using vinum and either the 2940U2W (Adaptec LVD) or the TekRAM
(NCR) LVD (using the sym0 device) gives 30 to 35 M/s under RAID-5.
That's really interesting, because there are at least two or
three outstanding bugs in the
"Brad" == Brad Knowles [EMAIL PROTECTED] writes:
This is impressive and subject to the bug that I mentioned in
-STABLE which still hasn't been found.
Brad Which one is this?
It's a really long thread. I'm not going to repeat it here.
Basically, under "enough" load, vinum trashes the
On Thu, Dec 16, 1999 at 03:40:20PM +0100, Martin Cracauer wrote:
You can also fool sh into running the *wrong* binary if if you have
two in showdowed paths:
pdksh does not suffer from either this problem or the problem that
started this thread (and does not coredump). We've shown in the past
In message [EMAIL PROTECTED], Kevin Day writes:
Ack, I was using this very same thing for several devices in an isolated
peer-to-peer network to decide who the 'master' was. (Whoever had been up
longest knew more about the state of the network) Having this change could
cause weirdness for
Huh? What about the impact on all ntp.conf files? Or is this seamless?
On Thu, 16 Dec 1999, Ollivier Robert wrote:
This is a HEADSUP message to warn all current users that tha following is
being done:
- disable xntpd build
- enable ntp build
- removal of old xntpd/xntpdc binaries as
fyi
-- Forwarded message --
Date: Thu, 16 Dec 1999 12:15:48 -0500 (EST)
From: Paul B. Brown [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Linux vs. OpenBSD vs. FreeBSD vs. NetBSD
Resent-Date: 16 Dec 1999 17:15:54 -
Resent-From: [EMAIL
In message [EMAIL PROTECTED], Matthew
Jacob writes:
Huh? What about the impact on all ntp.conf files? Or is this seamless?
I was just about to start to compose an email with some info on this
one when you email arrived.
/etc/ntp.conf is the same unless you have a refclock. If you have
a
Matt, you are a tenacious, fearsome bug hunter!
Matt
Matthew Dillon wrote:
Here's a general update on this bug report to -current. It took all day
but I was finally able to reproduce Andrew's bug.
You guys are going to *love* this.
NFS uses the kernel 'boottime'
All,
This might be a linux ABI question, or it might be an `ld.so' question,
so arguably I could have sent this to emulation, questions or since I run
-current, current, or perhaps hackers, at any rate here goes -
I've got `framemaker for linux' and am getting -
# maker5X.exe
maker5X.exe:
Between the two of us Dave Mills and I have managed to get the
"nanokernel" to act sensibly in the domain inside +/- 1usec which
the old one didn't. (See http://gps.freebsd.dk for what kind of
performance this can result in, given appropriate hardware).
You may not know the answer to this,
In message [EMAIL PROTECTED], Kevin Day writes:
Ack, I was using this very same thing for several devices in an isolated
peer-to-peer network to decide who the 'master' was. (Whoever had been up
longest knew more about the state of the network) Having this change could
cause
Yeah, uptime is moving which makes it difficult for me too. When new
machines enter the network, they need to announce a number which is used to
decice who will become the master if the current master disappears. I could
just announce currenttime-uptime, but that's got a slightly different
The only point I would like to argue is that this is not a comparison of
Apples to Apples.
Linux is just a kernel. There are Linux only utilities however
(i.e. util-linux). Each of the BSDs that you mentioned are full operating
systems. The closest comparison you can get is to compare a Linux
At 11:48 AM -0500 1999/12/16, David Gilbert wrote:
It's a really long thread. I'm not going to repeat it here.
Basically, under "enough" load, vinum trashes the kernel stack in such
a way that debugging is very tough.
It sounds like the second RAID-5 bug listed on the page I
"Brad" == Brad Knowles [EMAIL PROTECTED] writes:
Brad It sounds like the second RAID-5 bug listed on the page I
Brad mentioned:
28 September 1999: We have seen hangs when perform heavy I/O to
RAID-5 plexes. The symptoms are that processes hang waiting on
vrlock and flswai. Use ps lax to
:
:
:Yeah, uptime is moving which makes it difficult for me too. When new
:machines enter the network, they need to announce a number which is used to
:decice who will become the master if the current master disappears. I could
:just announce currenttime-uptime, but that's got a slightly
In message [EMAIL PROTECTED] Matthew Jacob
writes:
: Huh? What about the impact on all ntp.conf files? Or is this seamless?
Except for additional clocks, I've had no problems using old ntp.conf
files with the new ntpd.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: If people do a "settimeofday" we change the boot time since the
: amount of time we've been up *IS* known for sure, whereas the boottime
: is only an estimate.
There is one problem with this. The amount of uptime isn't the same
as the
In message [EMAIL PROTECTED] Nate Williams writes:
: You may not know the answer to this, but it's worth a shot. Wht kind of
: accuracy can we expect using 'cheap' off-the-shelf GPS receivers?
We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap
gps receiver + atomic clock on a
In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: If people do a "settimeofday" we change the boot time since the
: amount of time we've been up *IS* known for sure, whereas the boottime
: is only an estimate.
There is one problem with
Steve O'Hara-Smith wrote in list.freebsd-current:
On 15-Dec-99 Oliver Fromme wrote:
Alexander Langer wrote in list.freebsd-current:
gunzip has approx 106 kb, but you save about 50% per executeable.
-r-xr-xr-x 1 root wheel 4648 Jan 28 1999 /usr/bin/minigzip
It
: You may not know the answer to this, but it's worth a shot. Wht kind of
: accuracy can we expect using 'cheap' off-the-shelf GPS receivers?
We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap
gps receiver + atomic clock on a i486 class machine.
I've got the cheap gps
: If people do a "settimeofday" we change the boot time since the
: amount of time we've been up *IS* known for sure, whereas the boottime
: is only an estimate.
There is one problem with this. The amount of uptime isn't the same
as the amount of time since the machine booted. How can
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: Well, I don't think anybody has seriously thought about what the right
: semantics for APM is, and consequently the code we have is rather evil.
Don't know if I'd go so far as to say evil, but there are some pola
issues.
: What to do is a
In message [EMAIL PROTECTED] Nate Williams writes:
: : You may not know the answer to this, but it's worth a shot. Wht kind of
: : accuracy can we expect using 'cheap' off-the-shelf GPS receivers?
:
: We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap
: gps receiver +
Also sprach Oliver Fromme ([EMAIL PROTECTED]):
gunzip has approx 106 kb, but you save about 50% per executeable.
-r-xr-xr-x 1 root wheel 4648 Jan 28 1999 /usr/bin/minigzip
ok, even better :-)
Alex
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in
: : You may not know the answer to this, but it's worth a shot. Wht kind of
: : accuracy can we expect using 'cheap' off-the-shelf GPS receivers?
:
: We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap
: gps receiver + atomic clock on a i486 class machine.
:
:
In message [EMAIL PROTECTED], Nate Williams writes:
Between the two of us Dave Mills and I have managed to get the
"nanokernel" to act sensibly in the domain inside +/- 1usec which
the old one didn't. (See http://gps.freebsd.dk for what kind of
performance this can result in, given
In message [EMAIL PROTECTED] Nate Williams writes:
: Cool. I was under the impression that the cheap NMEA signals only gave
: 2-5sec accuracy given the 2400 baud speed issues.
If you have a PPS signal, then you can get fairly close even if the
inforation about the PPS signal comes in at 2400
: Cool. I was under the impression that the cheap NMEA signals only gave
: 2-5sec accuracy given the 2400 baud speed issues.
If you have a PPS signal, then you can get fairly close even if the
inforation about the PPS signal comes in at 2400 baud.
Hmm, how do I find out how good it is?
On Thu, 16 Dec 1999, Warner Losh wrote:
In message [EMAIL PROTECTED] Tom Bartol
writes:
: IIRC it does update uptime properly after a suspend in 2.2.8 but does not
: do so in 3.X and -current on my ThinkPad 770.
define correctly. Eg, if I suspend for an hour it adds an hour?
Warner
In message [EMAIL PROTECTED] Nate Williams writes:
: : Cool. I was under the impression that the cheap NMEA signals only gave
: : 2-5sec accuracy given the 2400 baud speed issues.
:
: If you have a PPS signal, then you can get fairly close even if the
: inforation about the PPS signal
In message [EMAIL PROTECTED] Tom Bartol
writes:
: I tried 3.0-current after this merge, suspend and resume worked fine on my
: 770 with the exception of uptime.
I can confirm that uptime, at least as reported by uptime(1), isn't
increased in the latest -current.
Warner
To Unsubscribe: send
In message [EMAIL PROTECTED], Nate Williams writes:
: You may not know the answer to this, but it's worth a shot. Wht kind of
: accuracy can we expect using 'cheap' off-the-shelf GPS receivers?
We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap
gps receiver + atomic
In message [EMAIL PROTECTED], Nate Williams writes:
"What is a PPS signal ?"
Typically handheld/boat naviation stuff. The NMEA or other
serial timecodes are at best in the 1msec class.
Again, for me this is acceptable. It would be nice to have it better
than this, but the
On Thu, 16 Dec 1999, Warner Losh wrote:
In message [EMAIL PROTECTED] Tom Bartol
writes:
: I tried 3.0-current after this merge, suspend and resume worked fine on my
: 770 with the exception of uptime.
I can confirm that uptime, at least as reported by uptime(1), isn't
increased in the
On 1999-Dec-16 19:55:35 +1100, Steve O'Hara-Smith [EMAIL PROTECTED] wrote:
On 15-Dec-99 Oliver Fromme wrote:
Alexander Langer wrote in list.freebsd-current:
gunzip has approx 106 kb, but you save about 50% per executeable.
-r-xr-xr-x 1 root wheel 4648 Jan 28 1999 /usr/bin/minigzip
Hi Julian,
the kernel code for appletalk is 'out of date' but it is also
somewhat modified..
If you want to work with it, let me know and I can help as I did the
original integration into our tree,
Well I would definitelly appreciate a quick summary of the changes that you
did to
Hi,
I can only assume that I'm doing something strange locally, but I've
now got two machines that do this, and my third -current machine
hasn't been installworld'd in a while
The problem is that I can't ``make install'' any info files... I get
something like:
$ make clean make depend
cd /usr/src/gnu/usr.bin/cc/f771; make build-tools
cc -O -pipe -march=pentium -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_T
ARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/us
r/src/gnu/usr.bin/cc/f771/../cc_tools -I/usr/src/gnu/usr.bin/cc/f771/../cc_tools
David Scheidt wrote:
What's wrong with run with system V runlevels? Other than it's system V and
everything AT^HUSL did is evil, of course.
They try to map graphs into a line.
--
Daniel C. Sobral(8-DCS)
who is as social as a wampas
[EMAIL PROTECTED]
[EMAIL
On Thu, Dec 16, 1999 at 09:25:11AM +0100, Soren Schmidt wrote:
There is this thing with the IBM's doing some headcleaning stuff once
a day/week, but I've never seen any of my IBM's do that (I got plenty
of them). I'll try to get more info on that from IBM...
Check
Patrick Bihan-Faou wrote:
[Charset iso-8859-1 unsupported, filtering to ASCII...]
Hi Julian,
the kernel code for appletalk is 'out of date' but it is also
somewhat modified..
If you want to work with it, let me know and I can help as I did the
original integration into our tree,
On Thu, Dec 16, 1999 at 04:50:55PM -0600, Richard Seaman, Jr. wrote:
Check http://www.storage.ibm.com/techsup/hddtech/prodspec/djna_spw.pdf
snip
If a command is received during spin down of ADM, the drive quits the spin down
and tries to complete the command as soon as possible.
In case the
Jos Backus wrote:
I just built the world from sources about 3-4 hours ago. It was all
great.
Darren Wiebe
[EMAIL PROTECTED]
cd /usr/src/gnu/usr.bin/cc/f771; make build-tools
cc -O -pipe -march=pentium -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_T
ARGET_VERSION=\"2.95.2\"
+[ Warner Losh ]-
|
| There is one problem with this. The amount of uptime isn't the same
| as the amount of time since the machine booted. How can this happen?
| When a laptop suspends, it doesn't update the update while it is
| asleep, nor does
I have the Enterprise 1400 Megaraid adapter with (currently 16M) on
it. I have tested the various modes of operation (different raid
levels and striping) and find it to be working well. My LVD array
consists of 8 18G Quamtum IV's.
Now... using vinum and either the 2940U2W (Adaptec LVD)
On Thu, 16 Dec 1999, Warner Losh wrote:
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: If people do a "settimeofday" we change the boot time since the
: amount of time we've been up *IS* known for sure, whereas the boottime
: is only an estimate.
There is one problem
Matthew Dillon writes:
We're already testing a patch.
Thanks again Matt!
The latest rev of nfs_serv.c has fixed it.
I'm now seeing FreeBSD UDP client read bandwidth of 9.2MB/sec write
bandwidth of 10.9MB/sec. Solaris clients are writing over TCP at
10.1MB/sec (and that is across a
On Wed, 15 Dec 1999 15:00:34 -0800 (PST),
Julian Elischer [EMAIL PROTECTED] said:
Julian however LINT doesn't help because it still has comments refering
Julian to 'enable pnp'. Are these old? and if not, how do I now do this?
Yes. Also, pcm(4) no longer needs to mention pnp(4). Could anyone
Julian Elischer writes:
might I suggest that we make a decision to allow procfs to be mounted with
a -linux flag and act more like the linux programs expect.?
(particularly we could mount it at /compat/linux/proc with the -linux
flag).
That would be wonderful.
I'd also like to
On Thu, 16 Dec 1999, Andrew Gallatin wrote:
Julian Elischer writes:
might I suggest that we make a decision to allow procfs to be mounted with
a -linux flag and act more like the linux programs expect.?
(particularly we could mount it at /compat/linux/proc with the -linux
:Matthew Dillon writes:
:
: We're already testing a patch.
:
:Thanks again Matt!
:
:The latest rev of nfs_serv.c has fixed it.
:
:I'm now seeing FreeBSD UDP client read bandwidth of 9.2MB/sec write
:bandwidth of 10.9MB/sec. Solaris clients are writing over TCP at
:10.1MB/sec (and that
On Thu, Dec 16, 1999 at 19:28:34 -0800, Matthew Dillon wrote:
:Matthew Dillon writes:
:
: We're already testing a patch.
:
:Thanks again Matt!
:
:The latest rev of nfs_serv.c has fixed it.
:
:I'm now seeing FreeBSD UDP client read bandwidth of 9.2MB/sec write
:bandwidth of
A few days back my Avance Asound stopped working. The probe would
fail (sorry, this is from memory):
sbc0: probe_and_attach returned 6
I found a slight error in sbc.c and here's a working patch:
--- /sys/dev/sound/isa/sbc.cSat Dec 11 21:30:19 1999
+++ sbc.c Thu Dec 16 23:42:43 1999
Seigo Tanimura wrote:
On Wed, 15 Dec 1999 15:00:34 -0800 (PST),
Julian Elischer [EMAIL PROTECTED] said:
Julian however LINT doesn't help because it still has comments refering
Julian to 'enable pnp'. Are these old? and if not, how do I now do this?
Yes. Also, pcm(4) no longer needs to
It seems Richard Seaman, Jr. wrote:
Yup, sounds like the problem some are seing, now I wonder why I
havn't seen it on any of the IBM disks I've access to, hmm...
It apparantly can't be disabled, but I'll try to figure out if
I can detect when the drive is in this mode, or put it in
standby mode
On Wed, Dec 15, 1999 at 05:31:13PM -0600, Chris Costello wrote:
On Wed, Dec 15, 1999, Wilko Bulte wrote:
Click-click, hosed up beyond repair. What I mean to say is that
GUI != easy to administer. M$ has plenty of examples available.
There's a difference between useful GUI design and
Hi,
I was looking at the netatalk package and the appletalk support in the
kernel source code and I realized that they are based on the same code
originally (the code from netatalk).
The kernel code however is quite out of date from what can be found in the
netatalk-asun package. I was
the kernel code for appletalk is 'out of date' but it is also
somewhat modified..
If you want to work with it, let me know and I can help as I did the
original integration into our tree,
Julian
On Thu, 16 Dec 1999, Patrick Bihan-Faou wrote:
Hi,
I was looking at the netatalk package
81 matches
Mail list logo
