On Fri, 10 Dec 1999, Brian Fundakowski Feldman wrote:
Why don't you want libssl, too? If we don't have that, then we'll
end up having to install the port for using SSL and there will be
redundancy (wasted space) and two copies of OpenSSL to maintain,
still.
Since it wasn't going to be used
On Thu, 9 Dec 1999, Archie Cobbs wrote:
Andrzej Bialecki writes:
I'd like to know whether we reached some conclusions concerning the naming
of sysctl variables created (or related to) KLDs. I know that Linux
emulator creates "compat.linux". I don't know if any other module creates
Make release in a -current cvsuped just now broke. It looks like the aout
directory is not there.
Fixed. Thanks. I'm testing as well, so if anything comes up, let me
know.
Ok, It got a little further. It now dies with during the "Rebuilding
dependencies" phase with:
--
mkdep
Hi ..
Under current the flash plugin works with the linux version of
Netscape and the linuxelator ... Sound etc, everything works ok ...
except for the odd crash of netscape which is normal :)
Hmmm. The developers of mozilla are dying to get bug reports
http://www.mozilla.org 8)
Someone
Hi,
On Thu, Dec 09, 1999 at 11:16:58PM +0300, Dmitrij Tejblum wrote:
Good luck using it under current.
First site you hit quits netscape without reasons...
... yes. I built the port for the first time just yesterday and made
the same experience.
...until you drop out of X and see a
On Fri, 10 Dec 1999, Andre Albsmeier wrote:
On Thu, 09-Dec-1999 at 15:02:41 -0800, Alfred Perlstein wrote:
On Thu, 9 Dec 1999, Andre Albsmeier wrote:
...
For better reference, here is the current patch:
I don't have too much time to think about this, argue me this:
Sure,
John Hay wrote:
The reason is that in Makefile.inc1 BMAKE sets -DNO_OBJC (and a lot of
others). BMAKE is used to do the cleanup and make the obj dirs, so the
/usr/obj/usr/src/gnu/usr.bin/cc/cc1obj dir is never created. To make
the dependencies and the rest XMAKE is used and then -DNO_OBJC
At 12:17 AM +0100 1999/12/10, Brad Knowles wrote:
In -CURRENT, I would say that this could probably be committed,
if John feels safe. I am not yet convinced that it should be
committed to -STABLE, although things do look good so far.
Well, things continue to look good:
Fri
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
It seems Donn Miller wrote:
I rebuilt my kernel on Tuesday or thereabouts with the new ata
controller. It worked perfectly with my SiS 5591. But, with the latest
cvsup, now the boot hangs and the hard drive is on solid when it gets to
the part mounting root on /dev/ad0s1a. Also, my UDMA/33
On Fri, 10 Dec 1999, Soren Schmidt wrote:
Erhm, there is NO support for the SIS5591 in the official sources, so
I dont see how you should have gotten UDMA33 with that, are you sure
you havn't applied the experimental patches I posted here to the
older kernel ??
Yes, come to think of it, I
Chuck Robey wrote:
This isn't taking the execution of aout binaries out, just stopping a
world build. This is only going to stop 3rd party developers from making
a 4.0 aout platform to create *more* aout binaries. They'll probably hang
on for dear life on 2.2, just as long as they can.
Kris Kennaway [EMAIL PROTECTED] wrote:
I have it building fine, although compiling without RSA seems
broken in openssl 0.9.4.
Well, it works fine in the OpenBSD tree. You might want to take a
look at what's been done there.
--
Christian "naddy" Weisgerber [EMAIL PROTECTED]
On Thu, 9 Dec 1999, Rodney W. Grimes wrote:
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
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
[EMAIL PROTECTED] wrote:
Managed to get the sound stuff working on this thinkpad 600e, for anyone
who cares...
Had to update to the most recent bios, and made sure "quick boot" was
disabled (hold down F1 while powering on to get into bios). I removed the
"csa0" device from the kernel
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
At 2:33 AM -0800 12/10/99, Alfred Perlstein wrote:
Can someone take a look at this?
Basically, it makes the link to the file, if it can unlink the original
it will then chown the spool file if it can't delete or read the original
then the user didn't have permission and it backs out.
I'm
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
On Fri, 10 Dec 1999, Garance A Drosihn wrote:
At 2:33 AM -0800 12/10/99, Alfred Perlstein wrote:
Can someone take a look at this?
Basically, it makes the link to the file, if it can unlink the original
it will then chown the spool file if it can't delete or read the original
then the user
I have checked the mailing list archives and havn't been able to find
anything on this so here goes:
I have a SoundBlaster ViBRA16X, and a Diamond SupraExpress 56i modem. The
SoundBlaster worked fine with PnP OS turned off in Bios, as did the
modem. They were detected as non PnP devices by
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
In message [EMAIL PROTECTED], Luoqi Chen writes:
This discussion is not going anywhere. Why can't everyone calm down and
find a comprise? Here's my proposal:
1. leave the the code and config option in the source tree for now
2. remove all traces of wd in documentation/GENERIC/LINT/MAKEDEV
that
I think there has been enough objections to the idea of just removing wd.c
for it to stay for a few months.
It doesn't hurt to keep it. Especially if it's not on by default.
I think this argument can go away for a while.
On Fri, 10 Dec 1999, Poul-Henning Kamp wrote:
In message [EMAIL
What's the status on the newpcm? is it still broken?
When I use newpcm, these problems occur:
1. when I use waveplay to play a file, even after it completely plays the
file (and return to the shell prompt), I still hear about 1-2 seconds of
sound playing repeatedly.
2. when I use xmms or mpg123,
At 3:05 PM -0700 1999/12/10, Kenneth D. Merry wrote:
I agree that the CAM integration shouldn't be used as a precedent here. I
don't agree with your characterization of it as a "debacle", though.
On the whole, we gained a whole lot and lost very little.
Long-term, yes I believe
At 11:22 PM 12/10/99 +0100, Poul-Henning Kamp wrote:
This discussion is not going anywhere. Why can't everyone calm down and
find a comprise? Here's my proposal:
1. leave the the code and config option in the source tree for now
2. remove all traces of wd in
On Fri, 10 Dec 1999, Poul-Henning Kamp wrote:
Listen guys, this is a tempest in a tea-cup, we are not loosing any
functionality here, we are gaining functionality.
Poul-Henning, what I'm seeing here is a LOT of voices raised against this
idea, both from key developers and other citizens of
Brad Knowles wrote...
At 3:05 PM -0700 1999/12/10, Kenneth D. Merry wrote:
I agree that the CAM integration shouldn't be used as a precedent here. I
don't agree with your characterization of it as a "debacle", though.
On the whole, we gained a whole lot and lost very little.
On Fri, 10 Dec 1999, Poul-Henning Kamp wrote:
This fails the most important criteria for the transistion to ATA:
it doesn't break existing kernel configs.
Listen guys, this is a tempest in a tea-cup, we are not loosing any
functionality here, we are gaining functionality.
The wd
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 put and end to this discussion happily? Will a few weeks
really harm the
Poul-Henning Kamp [EMAIL PROTECTED] wrote:
Once we have established that the new driver doesn't leave a large
number of people stranded it will be killed for good.
I think this is a key issue, if not *THE* key issue.
Please correct me if I'm wrong, but PHK and others are basically
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 change them to use ata. We know this from bitter experience.
If all you are talking about
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
Hi all,
I am using -current as of December 9 (CTM:src-cur.4130.gz), and
got following weird ATA related messages while 'make -j4 buildworld'.
I never had this kind of message when using wd drivers.
ata0-master: ad_timeout: lost disk contact - resetting
ata0: resetting devices ..
On Fri, 10 Dec 1999, Daniel C. Sobral wrote:
What Motoyuki-san is complaining about is that applications that
depend on a.out libraries will suffer. Alas, I don't think that's
the case, since all these libraries are (or ought to be, anyway) in
compat.
Looking at copious examples from
On Friday, 10th December 1999, "Kenneth D. Merry" wrote:
Brad Knowles wrote...
At 3:05 PM -0700 1999/12/10, Kenneth D. Merry wrote:
I agree that the CAM integration shouldn't be used as a precedent here.
I don't agree with your characterization of it as a "debacle", though.
On the
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
Stephen McKay wrote...
On Friday, 10th December 1999, "Kenneth D. Merry" wrote:
Brad Knowles wrote...
At 3:05 PM -0700 1999/12/10, Kenneth D. Merry wrote:
I agree that the CAM integration shouldn't be used as a precedent here.
I don't agree with your characterization of it as a
On Fri, 10 Dec 1999, 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.
There were a lot of mis-informed people on the lists who claimed that you
had to change your device
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.
There were a lot of mis-informed people on the lists who claimed that you
had to change your device names. That was completely untrue, and I
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
That was my musing in the next paragraph.
my first reaction was
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 "luigi"
Mike Smith 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.
There were a lot of mis-informed people on the lists who claimed that you
had to change your device names. That was
I am not sure the timecounters are being detected properly on my home
computer. A while back (around August) -CURRENT's kernel detected 2
timecounters, and using systat -vm, I could see clk generating 100
interrupts (I'm assuming per second) and rtc0 generating about 128 per
second. Around the
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 prefer
it if you wouldn't make "conclusive statements"
On 11 Dec, Munehiro Matsuda wrote:
Hi all,
I am using -current as of December 9 (CTM:src-cur.4130.gz), and
got following weird ATA related messages while 'make -j4 buildworld'.
I never had this kind of message when using wd drivers.
ata0-master: ad_timeout: lost disk contact -
I've just tried installing the last current snapshot (4.0-19991208-CURRENT)
onto an IBM laptop (365, type 2625-2E9) with a Xircom networking card
(CE3B-100BTX). It failed -- the pccard was not recognized.
I mention this because the floppies/pccard/README.TXT mentioned the systems
that have been
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 summary, the primary IDE interface, on
] which both my drives reside, is a PCTech RZ1000 on the PCI local bus.
Nobody in
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 change them to use ata. We know this from
The rtc is not a timecounter, and I doubt the the problem is related
to timecounters at all.
The RTC is always detected, because we know it is there, but it may
be that you don't get any interrupts from it, I don't know why that
might be.
Poul-Henning
In message [EMAIL PROTECTED], Ke
nneth
78 matches
Mail list logo
