On Wed, 15 Dec 1999, Robert Watson wrote:
On Tue, 14 Dec 1999, Peter Wemm wrote:
The RZ1000 is *dangerous*! We are doing no favours by making it run.. :-/
IMHO It is better to loose the user by not playing ball than to corrupt
their data or run unreliably and make them hate us for it.
On Tue, 14 Dec 1999, Peter Wemm wrote:
The RZ1000 is *dangerous*! We are doing no favours by making it run.. :-/
IMHO It is better to loose the user by not playing ball than to corrupt
their data or run unreliably and make them hate us for it.
It seems Robert Watson wrote:
On Tue, 14 Dec 1999, Peter Wemm wrote:
The RZ1000 is *dangerous*! We are doing no favours by making it run.. :-/
IMHO It is better to loose the user by not playing ball than to corrupt
their data or run unreliably and make them hate us for it.
On Wed, Dec 15, 1999 at 07:01:59PM +0100, Soren Schmidt [EMAIL PROTECTED] wrote:
That particular chip is so broken in so obscure ways, that most of the
"fixes" floating around doesn't. Its just plain broken, and should be
avoided totally and at all cost...
It will be nice to let the user
"Mike" == Mike Smith [EMAIL PROTECTED] writes:
Mike The "right" solution is and has always been to name your
Mike disks and mount them by name. Once devfs is a reality,
Mike we'll be able to do just this. Until then, the problem's
Mike not really as bad as you make it out to
What I didn't like about CAM was that I lost my tape drive. Since I
had all my backups and archives on DAT, it felt like a bad thing.
Which reminds me -- can anyone spare a 2.1 CD? Please send me private
mail, if so: I foolishly neglected to convert to CD, and now I can't
find 2.1 on the web
On Mon, Dec 13, 1999 at 15:45:15 -0600, Anthony Kimball wrote:
What I didn't like about CAM was that I lost my tape drive. Since I
had all my backups and archives on DAT, it felt like a bad thing.
What do you mean you "lost" your tape drive? CAM has included a tape
driver almost from day
On Saturday, 11 December 1999 at 8:52:28 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: You overlook one simple thing here: If we want the ata driver tested,
: we need to make existing kernel configs
On Friday, 10 December 1999 at 19:01:49 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Nate Williams writes:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Given that the ATA driver just went active a few minutes ago, I think a
period of
p
On Saturday, 11 December 1999 at 18:28:42 +0800, Peter Wemm wrote:
Dieter Rothacker wrote:
On Sat, 11 Dec 1999 14:21:25 +0800 (WST), Michael Kennett wrote:
Note that wd1 is not present. This caused a mild hickup when rebooting the
new kernel, since the new ata controller assigned the
On Friday, 10 December 1999 at 19:19:43 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Nate Williams writes:
And your point is? I'm a user, not a developer. If I wanted to be a
developer, I'd have written my own device driver. I want to *USE*
FreeBSD, not develop it.
Then
On Saturday, 11 December 1999 at 15:03:19 +1000, Stephen McKay wrote:
On Friday, 10th December 1999, Mike Smith wrote:
The same mentality that made the CAM cutover a "debacle" is making the
ata cutover a "debacle".
This "mentality" might be an unavoidable part of human nature. I found
my
On Saturday, 11 December 1999 at 12:39:15 +1000, Stephen McKay wrote:
But that shouldn't stop us from moving forward with the ata driver. I
think that a small slowing of the pace, and a bit more understanding toward
those with unusual hardware will help. And I support PHK's hard line
On Saturday, 11 December 1999 at 2:09:48 +0800, Peter Wemm wrote:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Nate Williams writes:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Given that the ATA driver just went active a few minutes ago, I
On Saturday, 11 December 1999 at 0:55:15 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Kris Ken
naway writes:
No-one (as far as I can see) is objecting to making ata the default (which
it already is), and to kill wd in some number of weeks. Why can't you just
do that, and
On Friday, 10 December 1999 at 17:54:14 -0800, Mike Smith wrote:
If half as much energy was spent adding the missing bits of functionality
to the new systems as people have been spending complaining it then we'd be
there ages ago.
Not true. It doesn't take a disk expert to complain about a
On Friday, 10 December 1999 at 17:11:53 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Greg Lehey writes:
We're getting off track again: the real issue is that you shouldn't
completely replace old drivers with new, better written, less buggy
drivers which have significantly
On Friday, 10 December 1999 at 23:32:27 -0800, Mike Smith wrote:
[missing attribution to Greg Childers [EMAIL PROTECTED]]
Except that ATA currently does not work on my system. So I assume I'm not
the only one.
Actually, to quote from your original message:
According to technical product
On Friday, 10 December 1999 at 19:04:33 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Nate Williams writes:
What we need here is a commitment to these new initiatives, not a lot of
fence-sitting and clutching our knitting to our chests.
If all our users were developers I
On Saturday, 11 December 1999 at 0:02:47 +0800, Peter Wemm wrote:
Jeroen Ruigrok/Asmodai wrote:
-On [19991209 16:03], Greg Lehey ([EMAIL PROTECTED]) wrote:
On Wednesday, 8 December 1999 at 20:23:24 +0100, Brad Knowles wrote:
This is -CURRENT. It pains me to say it, but anyone trying to
On Friday, 10 December 1999 at 22:44:36 +0100, Soren Schmidt wrote:
It seems Nate Williams wrote:
If half as much energy was spent adding the missing bits of functionality
to the new systems as people have been spending complaining it then we'd be
there ages ago.
Not true. It doesn't take
Greg Lehey wrote:
On Friday, 10 December 1999 at 23:32:27 -0800, Mike Smith wrote:
[missing attribution to Greg Childers [EMAIL PROTECTED]]
Except that ATA currently does not work on my system. So I assume I'm not
the only one.
Actually, to quote from your original message:
On 1999-Dec-12 05:54:12 +1100, Greg Lehey [EMAIL PROTECTED] wrote:
On Friday, 10 December 1999 at 19:01:49 +0100, Poul-Henning Kamp wrote:
The ata driver has been available for you and other to test for a long
time.
Oh. Somehow I missed this. Sure, I saw commits, but I can't recall a
"HEADS
At 07:40 AM 12/14/99 +0800, Peter Wemm wrote:
Greg Lehey wrote:
On Friday, 10 December 1999 at 23:32:27 -0800, Mike Smith wrote:
[missing attribution to Greg Childers [EMAIL PROTECTED]]
Except that ATA currently does not work on my system. So I assume I'm not
the only one.
3. Get pissed off with FreeBSD and go elsewhere.
don't worry I am sure that quite a few user have left already.
This kind of situation reminds of when I
accidently broke the gus max backwards compatibility.
An old friend of mine sent me a quiet note stating that
he switch OSes cause he
In [EMAIL PROTECTED] Kenneth Wayne Culver
[EMAIL PROTECTED] wrote:
Just a question which I'm not sure is soundcard related. My xmms no longer
starts up anymore, it just hangs in Poll before it actually puts anything
on the display, is that because /dev/dsp isn't working?
Thw
On Fri, Dec 10, 1999 at 07:01:49PM +0100, Poul-Henning Kamp wrote:
The ata driver has been available for you and other to test for a long
time.
That may be the case, but the vast majority of our users don't run
-current, for good reason, and so are in no position to test it. 4.0
will be
In message [EMAIL PROTECTED], Wilko Bulte writes:
On Sat, Dec 11, 1999 at 09:00:52AM -0800, Bob Vaughan wrote:
Subject: Re: HEADSUP: wd driver will be retired!
Date: Fri, 10 Dec 1999 19:19:43 +0100
From: Poul-Henning Kamp [EMAIL PROTECTED]
NOTE TO="SELF"
Maybe we should put
On Sat, Dec 11, 1999 at 12:57:04PM -0800, Doug White [EMAIL PROTECTED] wrote:
I'm getting the "lost disk contact" messages every now and then, but
only on our mp3 machine with PIIX3 controller and IBM UDMA/66 disk. It's
an PPro machine with Intel mobo. Can it be related to newer IBM disks?
In message [EMAIL PROTECTED], Nik Clayton writ
es:
On Fri, Dec 10, 1999 at 07:01:49PM +0100, Poul-Henning Kamp wrote:
The ata driver has been available for you and other to test for a long
time.
That may be the case, but the vast majority of our users don't run
-current, for good reason, and
On Sat, 11 Dec 1999, Marcel Moolenaar wrote:
"Jordan K. Hubbard" wrote:
Actually, I'm sad to say that our shiny new sound system does *not*
work for some of the most popular audio chipsets on the market today
(where the older "luigi" sound system did support them) and this is a
matter
On Sun, Dec 12, 1999 at 11:59:38AM +0100, Poul-Henning Kamp wrote:
Poul, I'd like to know what's wrong with
(1) Putting ata in GENERIC
(2) Keeping wd in LINT, commented out
This will not force CURRENT users to change their configs, a config
with wd in it will still work
Doug Rabson wrote:
The recent commits made existing support even worse. Yes, I'm talking
about the ESS1888. It's more dead than before. I'll have to make the
noise myself these days, and I can tell you it's no opera :-)
In short: Gimme patches! I'll be happy to test and, in a spare
On Sun, 12 Dec 1999, Marcel Moolenaar wrote:
Doug Rabson wrote:
The recent commits made existing support even worse. Yes, I'm talking
about the ESS1888. It's more dead than before. I'll have to make the
noise myself these days, and I can tell you it's no opera :-)
In short:
Leif Neland wrote:
On Sun, 12 Dec 1999, Nik Clayton wrote:
(3) A big notice in UPDATING, saying that ata is the replacement for
wd. Make wd require "options I_WANT_WD" or something similar,
so that people can't simply re-config their existing configuration
It seems Vallo Kallaste wrote:
On Sat, Dec 11, 1999 at 12:57:04PM -0800, Doug White [EMAIL PROTECTED]
wrote:
I'm getting the "lost disk contact" messages every now and then, but
only on our mp3 machine with PIIX3 controller and IBM UDMA/66 disk. It's
an PPro machine with Intel mobo.
In message [EMAIL PROTECTED], Michael Kennett writes:
Finally, I've noticed the following messages:
Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0 retrying
Dec 11 13:54:50 rabbit last message repeated 2 times
Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0
In message [EMAIL PROTECTED], "Jordan K. Hubbard" writes:
The ATA driver went golden now, and to make sure nobody is distracted
from testing it before 4.0-RELEASE is cut, the wd driver will be
removed.
It's really that simple.
Well, I'm not sure that's really true yet and I would honestly
On Sat, 11 Dec 1999 14:21:25 +0800 (WST), Michael Kennett wrote:
Note that wd1 is not present. This caused a mild hickup when rebooting the
new kernel, since the new ata controller assigned the labels ad0 and ad1 to
the drives. It was not possible to boot into multiuser mode without changing
Dieter Rothacker wrote:
On Sat, 11 Dec 1999 14:21:25 +0800 (WST), Michael Kennett wrote:
Note that wd1 is not present. This caused a mild hickup when rebooting the
new kernel, since the new ata controller assigned the labels ad0 and ad1 to
the drives. It was not possible to boot into
On Sat, 11 Dec 1999 18:28:42 +0800, Peter Wemm wrote:
Dieter Rothacker wrote:
You should use the kernel option
"options ATA_STATIC_ID"
for such cases. At least it works for me :-)
I think this should only apply to the /dev/wd* compatability devices. ie:
use the correct numbering for
"Jordan K. Hubbard" wrote:
Actually, I'm sad to say that our shiny new sound system does *not*
work for some of the most popular audio chipsets on the market today
(where the older "luigi" sound system did support them) and this is a
matter of significant concern to some folks, myself
In message [EMAIL PROTECTED], Stephen McKay writes
:
On Friday, 10th December 1999, Mike Smith wrote:
The same mentality that made the CAM cutover a "debacle" is making the
ata cutover a "debacle".
First of all, "core" is not really involved in this per se.
It might be that these things
On Fri, Dec 10, 1999 at 09:31:57PM +0100, Soren Schmidt [EMAIL PROTECTED] wrote:
I've connected the disk back to the UDM33 controller and it works
fine. Now I get the message twice a day:
ata0-master: ad_timeout: lost disk contact - resetting
ata0: resetting devices .. done
I've
If half as much energy was spent adding the missing bits of
functionality to the new systems as people have been spending
complaining it then we'd be there ages ago.
Not true. It doesn't take a disk expert to complain about a policy,
but it takes one to fix bugs/add features to the
On Thu, Dec 09, 1999 at 11:28:20AM +0100, Soren Schmidt wrote:
It seems Soren Schmidt wrote:
It seems Richard Seaman, Jr. wrote:
On Wed, Dec 08, 1999 at 03:02:37PM +0100, Soren Schmidt wrote:
OK, you asked for it, following is a patch to support the
sis 5591 chipset. Remember
On Fri, Dec 10, 1999 at 11:20:19PM -0800, Jordan K. Hubbard wrote:
my strategy on the whole affair at this point has
been to simply make marks on a tally-sheet near my keyboard,
While there is now working support for SiS 5591, and
thus my initial objection to removal of the wd drivers is now
On Sat, Dec 11, 1999 at 09:00:52AM -0800, Bob Vaughan wrote:
Subject: Re: HEADSUP: wd driver will be retired!
Date: Fri, 10 Dec 1999 19:19:43 +0100
From: Poul-Henning Kamp [EMAIL PROTECTED]
NOTE TO="SELF"
Maybe we should put a special marker in -currents sendmail and
On 11-Dec-99 Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: You overlook one simple thing here: If we want the ata driver tested,
: we need to make existing kernel configs break, otherwise people
: will not
The same thing is about to apply to the woxware sound code, we have a
new shiny system that works and is much better designed...
Actually, I'm sad to say that our shiny new sound system does *not*
work for some of the most popular audio chipsets on the market today
(where the older
Just a question which I'm not sure is soundcard related. My xmms no longer
starts up anymore, it just hangs in Poll before it actually puts anything
on the display, is that because /dev/dsp isn't working?
=
| Kenneth Culver
On Fri, Dec 10, 1999 at 09:22:55PM -0700, Kenneth D. Merry wrote:
And as for the device renaming, you didn't have to change anything from
sd-da. The old device names and nodes were supported in most every way.
BUT not any longer. Thus we have no choice but fully make the sd-da
change.
Kenneth Wayne Culver wrote:
The same thing is about to apply to the woxware sound code, we have a
new shiny system that works and is much better designed...
Actually, I'm sad to say that our shiny new sound system does *not*
work for some of the most popular audio chipsets on the
"Dieter" == Dieter Rothacker [EMAIL PROTECTED] writes:
Dieter Why would you want to define "correct" numbering the
Dieter non-spread-out numbering? Or did I misunderstand you? I
Dieter have all my disks as master drives on the channels. Now,
Dieter when I hook up another disk
On Sat, 11 Dec 1999, Lyndon Nerenberg wrote:
"Dieter" == Dieter Rothacker [EMAIL PROTECTED] writes:
Dieter Why would you want to define "correct" numbering the
Dieter non-spread-out numbering? Or did I misunderstand you? I
Dieter have all my disks as master drives on the channels.
On Fri, Dec 10, 1999 at 05:15:29PM +0100, Poul-Henning Kamp wrote:
Please, help Sos fix ATA if you know of a problem.
Please, help fix PCCARD if you know of a problem.
Ok, so now the attitude is I need to spend all my time:
1. Fix ATA to work on my laptop (there are timeout issues)
2. Fix
"Adam" == Adam [EMAIL PROTECTED] writes:
Adam As I understand it, cam or pre-cam or wd or ata it is simply
Adam an issue of defaults. If you plan to use disks that die or
Adam become removed, simply read LINT on how to wire your disk
Adam id's.
I understand. The point is:
Lyndon Nerenberg wrote:
"Adam" == Adam [EMAIL PROTECTED] writes:
Adam As I understand it, cam or pre-cam or wd or ata it is simply
Adam an issue of defaults. If you plan to use disks that die or
Adam become removed, simply read LINT on how to wire your disk
Adam id's.
...
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
phk wrote:
This is *CURRENT* remember ? We want this transistion done and
tested before current becomes 4.0-RELEASE. The time is NOW!
Not quite: this is -current, 4 days before a functionality freeze and
potentially less than one month before 4.0-RELEASE. Replacing critical
parts of the
On Sat, Dec 11, 1999 at 02:48:12PM -0700, Lyndon Nerenberg wrote:
"Dieter" == Dieter Rothacker [EMAIL PROTECTED]
writes:
Dieter Why would you want to define "correct" numbering the
Dieter non-spread-out numbering? Or did I misunderstand you? I
Dieter have all my disks as
Here is a patch for my modem:
--- sio.c.orig Sat Dec 11 19:51:29 1999
+++ sio.c Sat Dec 11 19:51:20 1999
@@ -553,6 +553,7 @@
{0x31307256, NULL}, /* USR3031 */
{0x8020b04e, NULL}, /* SUP2080 */
{0x8024b04e,
I think this should only apply to the /dev/wd* compatability devices. ie:
use the correct numbering for new installs onto ad*, but still support the old
spread-out naming for wd*. This used to be more important as it required
fiddling with $root_disk_unit, but the new mountroot code has
On Sat, 11 Dec 1999, Lyndon Nerenberg wrote:
Or worse, on a file server where you lose a low-numbered disk, not
only does that one go away, but everything higher numbered loses as
well. This "feature" does nothing other than introduce a gratuitous
Amen to this. If the default kernel or
"Dieter" == Dieter Rothacker [EMAIL PROTECTED]
writes:
Dieter Why would you want to define "correct" numbering the
Dieter non-spread-out numbering? Or did I misunderstand you? I
Dieter have all my disks as master drives on the channels. Now,
Dieter when I hook up another
In message [EMAIL PROTECTED] "David O'Brien" writes:
: On Fri, Dec 10, 1999 at 09:22:55PM -0700, Kenneth D. Merry wrote:
: And as for the device renaming, you didn't have to change anything from
: sd-da. The old device names and nodes were supported in most every way.
:
: BUT not any longer.
In message [EMAIL PROTECTED] "David O'Brien" writes:
: 2. Fix PCCARD on my laptop so I can suspend
What's the current issue? I have 0 problems suspending/resuming. I'd
like to know what is still broken, if anything, with the latest
-current.
: OR, I can work on the compiler and close my open
In message [EMAIL PROTECTED] Mike Smith writes:
: This is the usual poorly thought out argument, which fails to note that
: when you lose a disk you're already screwed due by /etc/fstab and the
: need to hard-mount local filesystems.
No. You aren't screwed. I have a system that needs /,
It seems Maxim Sobolev wrote:
Peter Jeremy wrote:
On 1999-Dec-09 10:19:22 +1100, Maxim Sobolev [EMAIL PROTECTED] wrote:
Why do not remove from wd driver support for chipsets
already implemented/tested in ata driver?
This requires additional developer effort - appropriate changes
On Thursday, 9 December 1999 at 8:46:13 -0500, Daniel Eischen wrote:
In message [EMAIL PROTECTED] Christopher Masto writes:
: Right now, I have no sound (not detected), no USB (panic on removal),
: can't use my sio pccard, can't eject my ed pccard, my IDE drives are
: taking hours to dump
In message [EMAIL PROTECTED] Greg Lehey writes:
: This happened some time towards the end of last month.
Try my latest fixes. Towards the end of November, I broke sio, but
spent a couple of hours last night fixing it.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
Jeroen Ruigrok/Asmodai wrote:
-On [19991209 16:03], Greg Lehey ([EMAIL PROTECTED]) wrote:
On Wednesday, 8 December 1999 at 20:23:24 +0100, Brad Knowles wrote:
This is -CURRENT. It pains me to say it, but anyone trying to
run anything "useful" on -CURRENT gets what they deserve. This
In message [EMAIL PROTECTED], Greg Lehey writes:
We're getting off track again: the real issue is that you shouldn't
completely replace old drivers with new, better written, less buggy
drivers which have significantly less than the full functionality of
the old driver.
And while that attitude
In message [EMAIL PROTECTED], Peter Wemm writes
:
I'd say, cut loose the wd driver. (VoxWare removed would be cool too.)
If half as much energy was spent adding the missing bits of functionality
to the new systems as people have been spending complaining it then we'd be
there ages ago. Trying
On Thu, Dec 09, 1999 at 11:01:16PM -0500, Greg Lehey wrote:
pccardd[47]: driver allocation failed for Motorola(MONTANA 33.6 FAX/MODEM): Device
not configured
This closely parallels my experience. I used to get:
Dec 5 11:57:53 mojave /kernel.old: sio1 at port 0x2e8-0x2ef irq 5 slot 1 on
In message [EMAIL PROTECTED] Christopher Masto writes:
: I saw the message about the missing #include "card.h", and that was it
: (along with a broken prototype). Still freezes when I eject, but I'll
: try again after cvsupping Warner's latest.
No. That wasn't it. There are still resource
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Given that the ATA driver just went active a few minutes ago, I think a
period of shakeout time would be called for. I think that time should
be longer than a few days, and should be in 4.0, and then retired in
What we need here is a commitment to these new initiatives, not a lot of
fence-sitting and clutching our knitting to our chests.
If all our users were developers I would agree. But *most* of our users
are not developers.
Again, I say, think of what we're trying to achieve here.
Good
In message [EMAIL PROTECTED], Nate Williams writes:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Given that the ATA driver just went active a few minutes ago, I think a
period of shakeout time would be called for. I think that time should
be longer than a
The sound drivers are fine . What we need are people willing to work
on the sound drivers .
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In message [EMAIL PROTECTED], Nate Williams writes:
What we need here is a commitment to these new initiatives, not a lot of
fence-sitting and clutching our knitting to our chests.
If all our users were developers I would agree. But *most* of our users
are not developers.
-CURRENT should
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Nate Williams writes:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Given that the ATA driver just went active a few minutes ago, I think a
period of shakeout time would be called for. I think
In message [EMAIL PROTECTED], Nate Williams writes:
What we need here is a commitment to these new initiatives, not a lot of
fence-sitting and clutching our knitting to our chests.
If all our users were developers I would agree. But *most* of our users
are not developers.
-CURRENT
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Given that the ATA driver just went active a few minutes ago, I think a
period of shakeout time would be called for. I think that time should
be longer than a few days, and should be in 4.0, and then
What is a killer is if a large number of people on popular hardware can't
even boot, *at all*, in no, way, shape or form. Only that. The only way
to find that out for sure before 4.0 is to push the issue *now*.
I disagree, but I'm not making the decision.
Nate
To Unsubscribe: send mail
In message [EMAIL PROTECTED], Nate Williams writes:
I'm with Warner. If the ATA driver went golden 2-3 months ago, then I'd
say go for it. But not 2-3 days ago. You're only telling your
user-base that they are less important than you are. (Although, this
may be what you believe, so who am I
In message [EMAIL PROTECTED], Nate Williams writes:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Given that the ATA driver just went active a few minutes ago, I think a
period of shakeout time would be called for. I think that time should
be longer
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Given that the ATA driver just went active a few minutes ago, I think a
period of shakeout time would be called for. I think that time should
be longer than a few days, and should be in 4.0, and then
In message [EMAIL PROTECTED], Nate Williams writes:
And your point is? I'm a user, not a developer. If I wanted to be a
developer, I'd have written my own device driver. I want to *USE*
FreeBSD, not develop it.
Then don't run -current.
I don't, but I will be running 4.0, which won't
On 9 Dec, Mike Smith wrote:
There also exist cases where the chipset is supported but a particular
functionality isn´t supported yet (in my case it´s the possibility to
access MS-DOS formated ZIP-disks, harddisk access works well, and I´m
not the only one with this problem (not counting the
In article [EMAIL PROTECTED] PHK writes:
NOTE TO="SELF"
Maybe we should put a special marker in -currents sendmail and
reject all email to the current list if they don't originate
from such a system.
/NOTE
I'll tell you in case you can't figure out the answer to that rather
simple question:
Hi,
I'm new to this list.
I was running the new ATA driver on an IBM UDMA/66
HighPoint HPT366 IDE controller until last week (sometimes after
CTM src-cur-4110). I've recompiled my system and my kernel and
the system was not able to find the partition on my UDM66-Disk,
was not able to
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: Please, help fix PCCARD if you know of a problem.
Yes. I think I've been the only one fixing bugs lately in PCCARD.
:-
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: In message [EMAIL PROTECTED], Nate Williams writes:
:
: I'm with Warner. If the ATA driver went golden 2-3 months ago, then I'd
: say go for it. But not 2-3 days ago. You're only telling your
: user-base that they are less important
If half as much energy was spent adding the missing bits of functionality
to the new systems as people have been spending complaining it then we'd be
there ages ago.
Not true. It doesn't take a disk expert to complain about a policy, but
it takes one to fix bugs/add features to the existing
In message [EMAIL PROTECTED], Warner Losh writes:
: The ATA driver went golden now, and to make sure nobody is distracted
: from testing it before 4.0-RELEASE is cut, the wd driver will be
: removed.
:
: It's really that simple.
Isn't that unprecidented? In the past there has always been a
It seems Nate Williams wrote:
If half as much energy was spent adding the missing bits of functionality
to the new systems as people have been spending complaining it then we'd be
there ages ago.
Not true. It doesn't take a disk expert to complain about a policy, but
it takes one to
Poul-Henning Kamp wrote...
In message [EMAIL PROTECTED], Warner Losh writes:
: The ATA driver went golden now, and to make sure nobody is distracted
: from testing it before 4.0-RELEASE is cut, the wd driver will be
: removed.
:
: It's really that simple.
Isn't that unprecidented? In
At 10:32 PM +0100 1999/12/10, Poul-Henning Kamp wrote:
Well, the only precedent we have is CAM/SCSI, and it was done the
same way.
Given some of the things I've heard about the CAM/SCSI debacle,
I'm not sure that this is a good example to be trotting out right
now. Personally, I
Brad Knowles wrote...
At 10:32 PM +0100 1999/12/10, Poul-Henning Kamp wrote:
Well, the only precedent we have is CAM/SCSI, and it was done the
same way.
Given some of the things I've heard about the CAM/SCSI debacle,
I'm not sure that this is a good example to be trotting out
1 - 100 of 199 matches
Mail list logo
