Oliver Fromme wrote:
In the case of adding something, what should be added if
nothing is specified? Should the tool invent an arbitrary
IP address and add it? Now that would be nonsensical.
But when removing something without specifying which one,
it makes some sense to simply remove the first
Greg Barniskis wrote:
Karl Denninger wrote:
and every time someone comes in the lists to complain about something
being
broken in -RELEASE, the advice is to go to and track -STABLE!
Maybe splitting hairs, but advising a user with a problem to try using
the -STABLE code that exists at the time
Volker wrote:
This should be documented somewhere clearly then, as my understanding was that -STABLE
meant that anything MFCd back to it *was* tested and deemed stable ... and yes, I do run
stable, and yes, I do expect to hit the occasional 'oopses', but "blantant and
obvious bugs due to insuf
Mike Jakubik wrote:
Jonathan Noack wrote:
The *entire* errata page was from 6.0; it was a mistake. This wasn't
some "put on the rose-colored classes and gloss over major issues"
thing. It was a long release cycle and something was forgotten. C'est
la vie. It's always a good idea to check the
Malcolm Kay wrote:
On Wed, 5 Oct 2005 11:06 am, Jeremy Bogan wrote:
You could try running a caching DNS server locally, DjbDNS is
simple to setup and get going.
Yes, I have thought that maybe a local simple caching dns
server would help; and if I can't otherwise fix the problem
I'll give
Subhro wrote:
Sebastian Holmqvist sat at his 'puter and typed on 10/1/2005 17:45:
Running the latest BIOS version yes. Also running Fail safe options
with the exception on that I've but the cdrom on first boot device.
The cable setup is IDE1 <- HD0 (M) <- Cdrom (S). So yes, they're on
the sam
Scot Hetzel wrote:
The ATA driver was changed in 5.x, and then again in 6-CURRENT. If
you want to run 5.x on that system, your going to need to install FBSD
4.11 first, then do a source upgrade to 5.x. But you'll also need to
replace the 5.x ATAng driver with the 6.x ATA-Mk III driver.
You'll
Jon Dama wrote:
Yes, but only in a configuration <=3GB. But I thought those problems were
ironed out? I've been looking to switch that machine back to
FreeBSD/amd64 but haven't had a chance yet. Would love to know if there
are issues ahead.
-Jon
On Thu, 8 Sep 2005, Mars G. Miro wrote:
Yo
Dan Nelson wrote:
In the last episode (Sep 08), Andriy Gapon said:
on 08.09.2005 19:29 Dan Nelson said the following:
-i uses the magic.mime file instead of the standard magic file, and
there are no entries for RISC executables in there.
Oh I see, completely different database.
Chuck Swiger wrote:
Matthias Buelow wrote:
Chuck Swiger wrote:
PS: Haven't we had this conversation before?
Yes, indeed, and I don't want to reopen that issue since that would
lead to no new insights (and since I don't have the time atm. to
contribute anything I couldn't provide any stuff
Vlad GALU wrote:
On 8/27/05, J. T. Farmer <[EMAIL PROTECTED]> wrote:
[snip]
It did the job for me. jhb commited the patch a couple of weeks
after I submitted the PR. Don't blame either him or me for things
going downhill, I assume that there were at least a few people running
w
Karl Pielorz wrote:
I recently installed FreeBSD 5.4-R onto my Dell laptop, and it worked
fine. I then updated to 5.4-STABLE (as of 26/08/05) - and it broke...
Specifically, with the new sources it fails to mount the root files
system - and instead displays:
"
Mounting root from ufs:/dev/ad
Karl Denninger wrote:
From the online man page for ata.4, which is EXPLICITLY referenced as THE
authoritative list of which disk controllers it supports:
The currently supported ATA/SATA controller chips are:
Acard: ATP850P, ATP860A, ATP860R, ATP865A, ATP865R
ALI:
Chuck Swiger wrote:
Karl Denninger wrote:
On Thu, Aug 11, 2005 at 12:46:04AM +0200, S?ren Schmidt wrote:
[ ... ]
I've already gone WAY out of my way to try to support the sii3112,
and I'm not inclined to waste more of my precious spare time on it.
However, if it really is that important
Scot Hetzel wrote:
On 8/10/05, Søren Schmidt <[EMAIL PROTECTED]> wrote:
Since I came in late in this, I need to know what kind of controller
we are talking about, and if the problem is still present in 6.0.
I plan to backport ATA from 6.0 to 5-stable when it has settled, so
6.0 is the one a
Mike Tancsa wrote:
At 09:31 AM 10/08/2005, Karl Denninger wrote:
Also, I've yet to see a developer commit on the list that they WILL
fix it if
such a controller board is forthcoming (and will return the board
when they're
done) - I've got two of these cards here (choose between Adaptec and
B
Chuck Swiger wrote:
O. Hartmann wrote:
[ ... ]
One of my SATA disks, the SAMSUNG SP2004C seems to show errors
during operation (and also showd under 5.4-RELEASE-p3).
Sometimes I get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still k
Kevin Oberman wrote:
I would suggest that it would have been better to post to current as 6.0
is not yet stable and most of the people who deal with problems are much
more likely to see problems reported there.
Ok, so I'm a bit confused. The answer given for the the DMA_WRITE and
DMA_READ
Andre Oppermann wrote:
First I want to thank everyone for their great support and numerous
donations
to the TCP/IP Cleanup and Optimization[1]! The full funding target
has been
reached today. I want thank especially the many individuals who have
contributed
a significant amount of money alon
J. Porter Clark wrote:
The ATA (definitely not SATA) controller on my Dell Latitude
C840 laptop has READ_DMA, WRITE_DMA problems, maybe 2-3 times
a day unless I turn off DMA. It hangs for 3-4 seconds, logs
errors, then proceeds. It isn't heavily loaded. I tried using
Soren's ATA mkIII patches
Tony Byrne wrote:
Hello Wilko,
Tuesday, July 19, 2005, 7:35:40 PM, you wrote:
WB> On Tue, Jul 19, 2005 at 11:22:01AM -0700, Jon Simola wrote..
What I've recently learned the hard way is that desktop drives have no
place in a server. I've now failed 4 of 10 SATA drives (Maxtor and WD)
in 1
Kevin Oberman wrote:
Don't forget that any "modern" BIOS and HD will be using LBA, not CHS,
for addressing the disk and disks have not had the same number of
sectors per track on all cylinders for a long time, so the numbers are
bogus in any case. CHS does not allow properly addressing any
moder
Uzi wrote:
[...]
super-smack select-key
5.4-RELEASE ~20,000 queries/second
6.0-CURRENT ~24,000 queries/second
CentOS w/async ~36,000 queries/second
CentOS w/sync ~26,000 queries/second
super-smack update-select
5.4-RELEASE
yuval levy wrote:
--- Dick Davies <[EMAIL PROTECTED]> wrote:
* Yuval Levy <[EMAIL PROTECTED]> [0647 15:47]:
Is it possible to fix this issue? from the
description it seems to me
that the issue got worse since freebsd 5.3
(assuming Maxi's root
partition is ufs2
Jim Thompson wrote:
On May 16, 2005, at 10:58 AM, Chris wrote:
Bill Paul wrote:
Ok everyone, PAY ATTENTION! Drop whatevery your doing for the next
five minutes and READ THIS!!
You see that header on this e-mail? You see the "From:" line? Go and
read it to yourself. Read the name. Say it to yourself
Bill Paul wrote:
Ok everyone, PAY ATTENTION! Drop whatevery your doing for the next
five minutes and READ THIS!!
Someone needs to drop back on their caffeine dosage...
Seriously, if that is the worse thing that you have to deal with, then I
really
don't care if you drop me on your personal "do not
Radek Kozlowski wrote:
On Tue, Mar 22, 2005 at 03:28:06PM +0100, Marwan Burelle wrote:
On Tue, Mar 22, 2005 at 02:48:37PM +0100, Radek Kozlowski wrote:
My 5.4-PRERELEASE/i386 as of today panics almost immediately after
plugging in an mp3 usb player (Qware BeatZkey! Pro 512MB). I don't have
27 matches
Mail list logo
