subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[.]
tun0: Command: ip-telecom: set dial ABORT BUSY ABORT NO\sCARRIER ABORT
NO\sDIAL\sTONE TIMEOUT 5 "" AT OK-AT-OK ATF OK
AT#F0$R1%E0S20=8E2S48=16 OK \dATDP\T TIMEOUT 40 CONNECT
[.]
ppp was treating everything from the # to the end of line as a
comment. It should be fixed now.
--
On Mon, 27 Dec 1999 03:39:56 -0500,
Donn Miller [EMAIL PROTECTED] said:
http://people.FreeBSD.org/~tanimura/patches/newmidi/2ndbuf-19991227.diff.gz
Donn Hmmm... this seems to have broken the probe at boot time.
Donn Here's a sample of my dmesg:
(snip)
Donn unknown1: ESS ES1868 Plug
, the patch broke Rollemup, so I fixed just now. The URI is the same.
Seigo http://people.FreeBSD.org/~tanimura/patches/newmidi/2ndbuf-19991227.diff.gz
--
Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
At 8:55 AM -0500 12/24/99, Robert Watson wrote:
... keep in mind that this optimization does not produce behavior
behavior in some cases. For example, imagine that the user has a
number of hard links to the file in question. If the file is copied and
then deleted, then the link count is
Did a test install against the latest snapshot.
The network configuration comes up with "dc0" (we have de0), this "works" in that we
were able to perform the network install (so it must be a typo somewhere).
However, it results in multiple entries in /etc/rc.conf (three, total), which have
The 'de' driver has been obsoleted for the 21143 part by the 'dc' driver.
You should be using 'dc' for those devices that it supports.
Did a test install against the latest snapshot.
The network configuration comes up with "dc0" (we have de0), this "works" in that we
were able to
On Mon, Dec 27, 1999 at 02:14:29PM -0500, Forrest Aldrich wrote:
Did a test install against the latest snapshot.
The network configuration comes up with "dc0" (we have de0),
this "works" in that we were able to perform the network
install (so it must be a typo somewhere).
If you had
In message [EMAIL PROTECTED], Forrest Aldrich writes
:
Did a test install against the latest snapshot.
The network configuration comes up with "dc0" (we have de0), this
"works" in that we were able to perform the network install (so it
must be a typo somewhere).
No, dc0 is the new and
Hi,
I apologize if this question is not appropriate for this list but...
I just installed FreeBSD 4.0-CURRENT (19991226) on a box. I also recompiled
the kernel so it would support SMP. All I basicly did is change two lines
concerning SMP in the GENERIC kernel (I followed the handbook). The
On Mon, 27 Dec 1999, Emre wrote:
Hi,
I apologize if this question is not appropriate for this list but...
I just installed FreeBSD 4.0-CURRENT (19991226) on a box. I also recompiled
the kernel so it would support SMP. All I basicly did is change two lines
concerning SMP in the GENERIC
On Mon, Dec 27, 1999 at 01:06:52PM -0800, Brian W. Buchanan wrote:
Add the line:
options IPFIREWALL
to your kernel config and recompile. See LINT for documentation and other
options you may wish to consider. IP Firewalling is not enabled by
default in GENERIC.
Oh Thanks for the quick
I've had my share of problems with this drive's DMA abilities. I'm
convinced that it has none... even though it probes as such.
ad0: NEC Coporation DSE2550A/5DE0314 ATA-0 disk at ata0 as master
ad0: ...
ad0: 16 secs/int, 1 depth queue, DMA
now... when I boot -v, I don't have a chance to write
The problem with the PCI128 rev 7 and ASUS boards seem to be solved
with a simple patch.
Anybody with such a combination please try this patch
ftp://ftp.thebarn.com/FreeBSD/es1371/es1371-src4-PCI128rev7.patch
Once it is verified to work, I'm sure somebody will want to commit it.
dunno
At 8:55 AM -0500 12/24/99, Robert Watson wrote:
For example, imagine that the user has a
number of hard links to the file in question.
Okay, here's my newer version of the code, which takes into
account multiple hard links, and also makes it so the spooled
data file is owned by daemon instead of
Randy Bush wrote:
The problem with the PCI128 rev 7 and ASUS boards seem to be solved
with a simple patch.
Anybody with such a combination please try this patch
ftp://ftp.thebarn.com/FreeBSD/es1371/es1371-src4-PCI128rev7.patch
Once it is verified to work, I'm sure somebody will
On Mon, Dec 27, 1999 at 10:02:29PM +0100, Wilko Bulte wrote:
Is there any reason for you to run -current? Because if there isn't you'd
be better off using a -stable version of FreeBSD.
Not really. All my other boxes (NetBSD/OpenBSD) run -current so I'm
used to be on the "bleeding edge" I
dunno what's solved by what, but current is not blasting sound for me.
reading the lists, suggestions for adding
controller pnp0
The pnp stuff shouldn't have anything to do with this card, it's pi.
^c
unnerstand. but
any clue how i can find out what this puppy is
Hauppauge WinCast/TV, Philips NTSC tuner, msp3400c stereo.
- pci0: unknown card (vendor=0x109e, dev=0x0878) at 10.1 irq 18
pcm0: AudioPCI ES1371 irq 17 at device 11.0 on pci0
i think everything in the box is working.
randy
To
On Mon, 27 Dec 1999, Randy Bush wrote:
any clue how i can find out what this puppy is
Hauppauge WinCast/TV, Philips NTSC tuner, msp3400c stereo.
- pci0: unknown card (vendor=0x109e, dev=0x0878) at 10.1 irq 18
Go to
http://www.pcisig.com/membership/vendors/sorted.html
to look up
hehe oops.. follow up to my own message this is for -stable :)
--
Eric Futch New York Connect.Net, Ltd.
[EMAIL PROTECTED] Technical Support Staff
http://www.nyct.net (212) 293-2620
"Bringing New York The Internet Access It Deserves"
On Mon, 27 Dec 1999, Eric D. Futch
Sigh. Ok, I've fixed the VN device. Again. It looks like the removal of
/dev/drum removed a little too much. We need the device infrastructure
to support the VN device's use of swap backing store.
This patch below is a commit candidate. It could use a review, then I'll
so, to go for 3.4 to -current i had to
o comment kerberos4 and perl from /etc/make.conf
o build
o build and install perl right in the directory
o the usual cruft
it works. and it fixed
o wl0
o my dlt free bus error
still working on kerberos, but i have learned to care less and less
In message [EMAIL PROTECTED], Matthew Dillon writes:
Sigh. Ok, I've fixed the VN device. Again. It looks like the removal of
/dev/drum removed a little too much. We need the device infrastructure
to support the VN device's use of swap backing store.
This patch below is a
:
:In message [EMAIL PROTECTED], Matthew Dillon writes:
:
:Sigh. Ok, I've fixed the VN device. Again. It looks like the removal of
:/dev/drum removed a little too much. We need the device infrastructure
:to support the VN device's use of swap backing store.
:
:This patch
Hi all,
I just rebooted my -current box for the first time in a long
time. Everything on this box is freshly compiled (including
X) as of only a couple of hours ago. I even mergemaster'd
for good measure.
For some reason now I can't startx(1) as either myself or root.
I type startx and the
Hi.
I have been following the thread(s) about getting the SoundBlaster
Vibra 16 sound-cards working in -current, and it appears that if
you have a PnP card, it seems to be working.
I do not have a PnP version of this card, and the last time I was
able to get the sound card recognised was
In message [EMAIL PROTECTED], Matthew Dillon writes:
VN calls vm_pager_strategy() which collects I/O in filesystem buffers
(bp)'s in order to cluster the I/O, and you cannot initiate I/O on
filesystem buffers without a valid b_dev.
So, the jist of the problem is that in order
:In message [EMAIL PROTECTED], Matthew Dillon writes:
:
:VN calls vm_pager_strategy() which collects I/O in filesystem buffers
:(bp)'s in order to cluster the I/O, and you cannot initiate I/O on
:filesystem buffers without a valid b_dev.
:
:So, the jist of the problem is that in
In message [EMAIL PROTECTED], Matthew Dillon writes:
First, you are confusing the underlying swap devices that we swapon on
with the parent swap device that controls them. The parent swap device
needs to have a dev_t - it does not currently have one, and this is
the entry point
:In message [EMAIL PROTECTED], Matthew Dillon writes:
:
:First, you are confusing the underlying swap devices that we swapon on
:with the parent swap device that controls them. The parent swap device
:needs to have a dev_t - it does not currently have one, and this is
:the entry
Ahh, I see the mistake.
All you need to fix this is to add a new function:
void
flushswchainbuf(struct buf *nbp)
{
if (nbp-b_bcount) {
nbp-b_bufsize = nbp-b_bcount;
if ((nbp-b_flags B_READ) == 0)
:
:
:Ahh, I see the mistake.
:
:All you need to fix this is to add a new function:
:
: void
: flushswchainbuf(struct buf *nbp)
: {
: if (nbp-b_bcount) {
: nbp-b_bufsize = nbp-b_bcount;
: if ((nbp-b_flags B_READ) == 0)
:
In message [EMAIL PROTECTED], Matthew Dillon writes:
:
:Ahh, I see the mistake.
:
:All you need to fix this is to add a new function:
:
: void
: flushswchainbuf(struct buf *nbp)
: {
: if (nbp-b_bcount) {
: nbp-b_bufsize = nbp-b_bcount;
:
::--
::Poul-Henning Kamp FreeBSD coreteam member
::[EMAIL PROTECTED] "Real hackers run -current on their laptop."
:
:Uh... no. The chain buffer routines are supposed to be generic. In fact,
:all the filesystem buffer cache I/O routines are supposed to be
In message [EMAIL PROTECTED], Matthew Dillon writes:
Huh? Look Poul, I don't know what your problem is but I'm through
playing around with you. You aren't making any sense and, frankly my
dear sir, the buffer cache, vm_pager interface, VN device, and
vm_pager_strategy
:
:In message [EMAIL PROTECTED], Matthew Dillon writes:
:
:Huh? Look Poul, I don't know what your problem is but I'm through
:playing around with you. You aren't making any sense and, frankly my
:dear sir, the buffer cache, vm_pager interface, VN device, and
:vm_pager_strategy
In message [EMAIL PROTECTED], Matthew Dillon writes:
Sorry Poul, but you have no authority in this matter. All the statements
you have made in the last hour simply point out, in very clear terms,
that you don't know what you are talking about. Instead of simply
admiting a
I've heard from both of you that you think the other is wrong. This isn't
very helpful, however, in finding the correct solution. What I'd like to hear
from both of you is the reasons why swap is better as a device, or not. There
seems to be some unstated architectural philosophy that needs to
Very INET6 specific patches are already prepared and under the
review. getaddrinfo() and getaddrname() is not yet, but I'll
also prepare them.
And after those libraries are prepared, porting KAME tools
onto current won't be difficult.
Getaddrinfo(), getaddrname(), etc support is
Matthew Dillon wrote:
[..]
And, in anycase, I am not going to spend hours putting together a long
involved patch when a simple short patch suffices. If you want to
spend the time to come up with your own patch (that doesn't screw the
pooch in regards to cluster
David Greenman wrote:
I've heard from both of you that you think the other is wrong. This isn't
very helpful, however, in finding the correct solution. What I'd like to hear
from both of you is the reasons why swap is better as a device, or not. There
seems to be some unstated
In message [EMAIL PROTECTED] Peter Wemm writes:
: Just as a BTW, dfr and sos are exchanging patches right now (and have been
: for quite a few days) that happen to fix the inthand_add() stuff.
This may also help the pccard code cases which I have floating around.
Warner
To Unsubscribe: send
:
: I've heard from both of you that you think the other is wrong. This isn't
:very helpful, however, in finding the correct solution. What I'd like to hear
:from both of you is the reasons why swap is better as a device, or not. There
:seems to be some unstated architectural philosophy that
In message [EMAIL PROTECTED], David Greenman writes:
There
seems to be some unstated architectural philosophy that needs to be stated
before any informed decision can be made about what is the right direction to
go in.
The underlying problem is of course that struct buf is a conglomerate
of
Frankly, Poul, I strongly, *STRONGLY* recommend that you simply not
reply to any of my postings. Not a single one, because I am wholely
sick and tired of your superiority complex. This thread was not meant
This is unwontedly personal and has no place in a public mailing list.
It makes no sense whatsoever to spend hours or days reworking a major
subsystem *just* so the swap device can do without a dev_t. I don't
really give a damn about /dev/drum -- I said before and I will say again
that we can leave it out. But we need to give the swap device its's
Peter Wemm wrote:
David Greenman wrote:
I've heard from both of you that you think the other is wrong. This isn'
t
very helpful, however, in finding the correct solution. What I'd like to he
ar
from both of you is the reasons why swap is better as a device, or not. The
re
:
:Matthew Dillon wrote:
:[..]
: And, in anycase, I am not going to spend hours putting together a long
: involved patch when a simple short patch suffices. If you want to
: spend the time to come up with your own patch (that doesn't screw the
: pooch in regards to cluster
This is unwontedly personal and has no place in a public mailing list.
Please keep your replies confined to technical content (or your
concerns about the lack thereof) and keep always in mind that getting
emotional serves only to generate heat when what's needed is light.
- Jordan
And it
I noticed recently (10 minutes ago) that FreeBSD will mount a DVD and I
can even look around on it as if it were a regular CD (on -CURRENT). I was
wondering if there was any mpeg2 decoder that would play DVD movies. I
don't have a hardware decoder the software one looks fine but I'd like to
know
Hello,
I just got my box up and running
Current 12-27. ATA works great for both drives now. However, I
compiled XFree86 from the port and I chose the options for RPC, Wraphelp.c, PAM
and threads. When I start x (using startkde), I get many many password
prompts. I can only assume that the
Hello,
I just got my box up and running Current 12-27. ATA works great for
both drives now. However, I compiled XFree86 from the port and I chose the
options for RPC, Wraphelp.c, PAM and threads. When I start x (using
startkde), I get many many password prompts. I can only assume that
Recently someone posted a url that provided a quick run through on some
important extra steps to take while doing a make world from -STABLE to
-CURRENT, unfortunatly I lost the URL. I was wondering if someone could
post it again? I did check the archives, but I wasn't able to find it.
Thanks.
On Mon, Dec 27, 1999 at 11:23:21PM -0600, Kevin Entringer wrote:
Recently someone posted a url that provided a quick run through on some
important extra steps to take while doing a make world from -STABLE to
-CURRENT, unfortunatly I lost the URL. I was wondering if someone could
post it
On 27-Dec-99 Emre wrote:
Actually I haven't tried -release or -stable...I'm willing
to take the chance.
I think you will find that you are taking much more of a chance with
-current than with -stable. After all -current is allowed to break sometimes,
-stable only does it by accident.
On Mon, Dec 27, 1999 at 11:01:50PM -0600, Thomas T. Veldhouse wrote:
Hello,
I just got my box up and running Current 12-27. ATA works great for both drives
now. However, I compiled XFree86 from the port and I chose the options for RPC,
Wraphelp.c, PAM and threads. When I start x
I just got my box up and running Current 12-27. ATA works great for =
both drives now. However, I compiled XFree86 from the port and I chose =
the options for RPC, Wraphelp.c, PAM and threads. When I start x (using =
startkde), I get many many password prompts. I can only assume that
Quoth Kenneth Wayne Culver on Mon, 27 December:
: I don't have a hardware decoder the software one looks fine but I'd like to
: know if anyone has tried to make a software decoder for FreeBSD. Thanks..
(I'll redirect to multimedia.)
I've been trying to build the nist mpeg2player on current
Seigo Tanimura wrote:
Another fix was made on feeding and sucking pcm data. Now chn_wrfeed()
and the other functions do not attempt excessive feeding during DMA
transfer to eat up the whole processor. The patch is at:
http://people.FreeBSD.org/~tanimura/patches/newmidi/2ndbuf-19991227
60 matches
Mail list logo
