You should be able to fire up two video cards were one them can not
be mapped to the vga registers -- your mileage will vary here pending
upon the vga card implementation for instance the old matrox millenium
had a feature to disable the vga register mapping .
Can speak much about syscons I would
:
:I'm nothing like an NFS expert, so I may be talking through my hat,
:but... I presume NFS correctly supports O_APPEND semantics for
:multiple clients (as seen from the server). In this case, the
:optimization only works when there's only one client machine (though
:possibly multiple processes
> I was just wondering -- does the new EGCS imply that things like
> apps2go Motif won't link properly against a 4.x-CURRENT world now?
My Apps2go Motif works just file post-EGCS.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: send mail to majord...@freebsd.org
with
> >:Just wondering if these changes also have the side effect of fixing the
> >:nmap problem that crashes 3.x boxes ? i.e. as you wrote back on 3/4/99
> >:
> >:>The problem is a deadlock caused by the fgrep. The fgrep is mmap()ing
> >:>the file, but then it does some really weird crap wh
Matthew Dillon wrote:
> :> > work! :-)
> :>
> :> Clearly, that goes to show Luigi must have no life... :-)
> :>
> :
> :"Luigi" is an interesting spelling of "Louqi".
Whoops! Luoqi ;-)
> :The bug was actually in libalias.
> :
>
> Luoqi found a bug in the compiler's optimizer. I presume so
:> > work! :-)
:>
:> Clearly, that goes to show Luigi must have no life... :-)
:>
:
:"Luigi" is an interesting spelling of "Louqi".
:
:The bug was actually in libalias.
:
:--
:Steve
Luoqi found a bug in the compiler's optimizer. I presume someone
has/will commit a change to libalias to
:> Speaking of, when can we expect to see this wonderfull _stability_
:> improvement in -stable? I'm setting up a server here, and would
:
:Usually when we're sure it's not a pessimization in other ways. I
:think people are getting just a bit prematurely excited here, not to
:knock Matt's good wor
> "Luigi" is an interesting spelling of "Louqi".
Or even "Luoqi", as his name is actually spelled. :-)
Sorry, Mr. Chen, for the transposition of you and Luigi. Temporary
brain fade! :)
> The bug was actually in libalias.
Yes, also correct.
- Jordan
To Unsubscribe: send mail to majord...@fre
what is this shit? damn, i need to tell my uncle, he used to be an
assemblies of god preacher, and he has enough choice words on those
racists to fill a book...
this shit doesn't belong here.
In reply:
> CALL TODAY TO ORDER THIS BOOK - (800) 305-1458 [24hrs.]
> --
Daniel C. Sobral wrote:
> "Jordan K. Hubbard" wrote:
> >
> > > Funny you should mention it. I've heard this from a number of people over
> > > the last week.. One has even suggested using a particular known-good 4.0
> > > snapshot in preference to a 3.1-stable for a production system..
> >
"Jordan K. Hubbard" wrote:
>
> > Funny you should mention it. I've heard this from a number of people over
> > the last week.. One has even suggested using a particular known-good 4.0
> > snapshot in preference to a 3.1-stable for a production system..
>
> That's a little foolish since we'v
Viren R. Shah once stated:
=Amancio and Nick helped me get my system with only a USB keyboard and
=USB mouse up and running. Right now I'm pretty happy with the way it is
=now. My only concern is that the FreeBSD bootloader does not appear to
=see keystrokes from the USB keyboard (which kinda make
On 22-Apr-99 Amancio Hasty wrote:
> The problem was not really a bios problem not sure what the guys
> did to fix the boot loader probably switch to using a dos int function
> to access the keyboard from the boot loader.
Hmm.. what does it do now? Just talk to the keyboard controller directly?
The problem was not really a bios problem not sure what the guys
did to fix the boot loader probably switch to using a dos int function
to access the keyboard from the boot loader.
--
Amancio Hasty
ha...@star-gate.com
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe fr
CALL TODAY TO ORDER THIS BOOK - (800) 305-1458 [24hrs.]
--
"What nobody had the nerve to tell you until now."
"Real evidence of what you only suspected."
"The Black Church as you've never known it before."
Pulpit Confessions:
Exposing The Black Chur
Can newbus resource manager manage discontinuouse I/O port?
Many PC-98 devices use discontinuous I/O port like:
0x00d0, 0x10d0, 0x20d0, 0x30d0, 0x40d0, ..., 0xf0d0
Current API seems to assume contiguity and not to be able to manage
such I/O port addresses.
-
On 21-Apr-99 Viren R. Shah wrote:
> Kazu> be able to "detach" the ukbd driver while the system is running.
> Amancio and Nick helped me get my system with only a USB keyboard and
> USB mouse up and running. Right now I'm pretty happy with the way it
> is now. My only concern is that the FreeB
> All I'm saying (I think) is that we shouldn't allow the 4.0 release cycle
> to stretch out to 2 years like the 3.0 cycle did (discounting 3.0 as a
> beta release).
No argument there - the current schedule is 12 months for 4.0. 2
years far too long and merely the result of unforseen delays and m
> I'm curious, is there any plan to backport egcs to -stable or no? Also, as a
There are no plans at this time to merge egcs over. This will only
happen if time and hindsight prove egcs to be of low enough
impact that it's suitable -stable material.
- Jordan
To Unsubscribe: send mail to major
> I wonder if it would be too radical to suggest that the release cycle for
> 4.0 be *much* shorter than the 3.0 cycle. Maintaining two branches gets
> worse and worse as time goes on and it just becomes a waste of programmer
> time. If we are reasonably careful with the 4.0 tree, I think a 4.0
Wh
> Speaking of, when can we expect to see this wonderfull _stability_
> improvement in -stable? I'm setting up a server here, and would
Usually when we're sure it's not a pessimization in other ways. I
think people are getting just a bit prematurely excited here, not to
knock Matt's good work or a
> Funny you should mention it. I've heard this from a number of people over
> the last week.. One has even suggested using a particular known-good 4.0
> snapshot in preference to a 3.1-stable for a production system..
That's a little foolish since we've still not found all the egcs
optimizer
> I'm curious, is there any plan to backport egcs to -stable or no?
No.
> Also, as a side note: good thing we went with egcs, as it was just
> announced that egcs is now the official gcc.
Yep, I had some inside info that this was probably going to happen.
--
-- David(obr...@nuxi.com -or
I am running 4.0-current SMP, cvsup today and built an hour ago.
Everything seems OK.
Great work.
tomdean
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
I'm only subscribed to freebsd-stable, so I missed the original thread,
but reading the lines below, a question arises:
On Wed, 21 Apr 1999, Matthew Dillon wrote:
> Well, you already see a lot of the pure bug fixes being backported.
> What you don't see in -stable are the bug fixes that also depen
Hi,
At 4:34 pm -0700 20/4/99, Matthew Dillon wrote:
>NFS patch #6 is now available for -current.[etc]
Looks real good here. Been running two servers continuously building the
world with their /usr/obj cross-mounted on each other. Oh, and one of them
is SMP running -j8.
Great job!
--
Bob Bi
Matthew Dillon wrote:
[Partial writes]
> I finally gave up on it. What NFS does now is optimize only two
> write situations: ... And (2) piecemeal writes in the write-append
> case.
I'm nothing like an NFS expert, so I may be talking through my hat,
but... I presume NFS correctly supports O_A
> "Amancio" == Amancio Hasty writes:
Amancio> Hi,
>> is now. My only concern is that the FreeBSD bootloader does not appear
Amancio> If you are running -current as of at least last nite you
Amancio> will not have any problems with the bootloader and your USB
Amancio> keyboard in fact I
Hi,
>is now. My only concern is that the FreeBSD bootloader does not appear
If you are running -current as of at least last nite you will not have
any problems with the bootloader and your USB keyboard in fact
I just rebooted my test system and was able to select the kernel
to boot; previously, y
At 01:29 PM 4/21/99 -0700, Matthew Dillon wrote:
>
>:Hi,
>:Just wondering if these changes also have the side effect of fixing the
>:nmap problem that crashes 3.x boxes ? i.e. as you wrote back on 3/4/99
>:
>:
>:>The problem is a deadlock caused by the fgrep. The fgrep is mmap()ing
>:>the
Speaking of upgrading to -current from 3.x-STABLE, I was just wondering --
does the new EGCS imply that things like apps2go Motif won't link properly
against a 4.x-CURRENT world now? It's things like this that will hold me
back, if they indeedy are a problem.
Brian
To Unsubscribe: send mail
> "Kazu" == Kazutaka YOKOTA writes:
Kazu> You need to be running usbd.
Kazu> In any case, we need some more work in the usb and ukbd driver code to
Kazu> be able to "detach" the ukbd driver while the system is running.
Amancio and Nick helped me get my system with only a USB keyboard and
:Hi,
:Just wondering if these changes also have the side effect of fixing the
:nmap problem that crashes 3.x boxes ? i.e. as you wrote back on 3/4/99
:
:
:>The problem is a deadlock caused by the fgrep. The fgrep is mmap()ing
:>the file, but then it does some really weird crap when deali
When running dhclient with the kernel fxp driver I get a kernel panic in
ifconfig. Might be some other things I enabled in the kernel, but I haven't
double-checked yet.
--
Eric Hodel
hodel...@seattleu.edu
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in
At 01:09 PM 4/21/99 -0700, Matthew Dillon wrote:
>:Speaking of, when can we expect to see this wonderfull _stability_
>:improvement in -stable? I'm setting up a server here, and would
>:rather have fixed NFS code in it... Yet, jumping to -current is
>:officially wrong... Thanks!
>:
>: -mi
>
>
:Speaking of, when can we expect to see this wonderfull _stability_
:improvement in -stable? I'm setting up a server here, and would
:rather have fixed NFS code in it... Yet, jumping to -current is
:officially wrong... Thanks!
:
: -mi
Well, you already see a lot of the pure bug fixes bei
Don't worry quite a few fixes went into syscons so it is no
longer isa centric.
>
> >While playing over here with the USB stuff, I rebooted the system and
> >disconnected the USB keyboard waited till the system was fully up
> >and re-connected the USB keyboard which resulted in the system
> >
On Wed, 21 Apr 1999, Matthew Dillon wrote:
> :I wonder if it would be too radical to suggest that the release cycle for
> :4.0 be *much* shorter than the 3.0 cycle. Maintaining two branches gets
> :worse and worse as time goes on and it just becomes a waste of programmer
> :time. If we are reasona
>While playing over here with the USB stuff, I rebooted the system and
>disconnected the USB keyboard waited till the system was fully up
>and re-connected the USB keyboard which resulted in the system
>not attaching the USB keyboard.
You need to be running usbd.
In any case, we need some more
On 21-Apr-99 Matthew Dillon wrote:
> Most of the bug fixes have been backported to -stable. Getting the new
> VM system into -stable ( which I want to do just after the 3.2 release )
> is going to require brute force, though. Unfortunately, the most recent
> fixes to NFS fall int
:I wonder if it would be too radical to suggest that the release cycle for
:4.0 be *much* shorter than the 3.0 cycle. Maintaining two branches gets
:worse and worse as time goes on and it just becomes a waste of programmer
:time. If we are reasonably careful with the 4.0 tree, I think a 4.0
:releas
On Wed, 21 Apr 1999, Matthew Dillon wrote:
> :Matthew Reimer wrote:
> :> Great work guys! It almost seems that -current is more stable than
> :> -stable!
> :>
> :> Matt
> :
> :Funny you should mention it. I've heard this from a number of people over
> :the last week.. One has even suggested usi
While playing over here with the USB stuff, I rebooted the system and
disconnected the USB keyboard waited till the system was fully up
and re-connected the USB keyboard which resulted in the system
not attaching the USB keyboard.
A side note, someone fixed syscons so it no longer panics if
the
> Matthew Reimer wrote:
> > Great work guys! It almost seems that -current is more stable than
> > -stable!
> > Matt
>
> Funny you should mention it. I've heard this from a number of people over
> the last week.. One has even suggested using a particular known-good 4.0
> snapshot in preference t
On Thu, 22 Apr 1999, Peter Wemm wrote:
> Matthew Reimer wrote:
> > Great work guys! It almost seems that -current is more stable than
> > -stable!
> >
> > Matt
>
> Funny you should mention it. I've heard this from a number of people over
> the last week.. One has even suggested using a parti
:Matthew Reimer wrote:
:> Great work guys! It almost seems that -current is more stable than
:> -stable!
:>
:> Matt
:
:Funny you should mention it. I've heard this from a number of people over
:the last week.. One has even suggested using a particular known-good 4.0
:snapshot in preference to a
Peter Wemm once wrote:
> > Great work guys! It almost seems that -current is more stable than
> > -stable!
> Funny you should mention it. I've heard this from a number of people
> over the last week.. One has even suggested using a particular
> known-good 4.0 snapshot in preference to a 3.1-stab
On Wed, 21 Apr 1999, Matthew Dillon wrote:
> :2 questions I had:
> :
> :2) at BAFUG 2 or 3 months ago I, *cough* attempted to keep up with you
> :an Julian talking about VM issues. :) Something you guys brought up
> :was problems with mmap() + read()/write() no staying in sync and requireing
> :a
On Wed, 21 Apr 1999, Matthew Dillon wrote:
> :
> :I would just like to say, that unlike certain zealots of other operating
> :systems I've always been a bit hesitant to recommend FreeBSD over
> :solaris because of this one factor (NFS).
> :
> :It now seems I can't think of a single reason, (I'm
Matthew Reimer wrote:
> Great work guys! It almost seems that -current is more stable than
> -stable!
>
> Matt
Funny you should mention it. I've heard this from a number of people over
the last week.. One has even suggested using a particular known-good 4.0
snapshot in preference to a 3.1-stabl
On Wed, 21 Apr 1999, Matthew Dillon wrote:
> :
> :With a full duplex setup collisions don't exist. In a switched setup the
> :latency should be very consistent and extremely low. Something else must
> :be wrong here.
>
>I should explain this more: It isn't actually the ethernet latency
>
:> We all owe Matt big for this. :)
:>
:>
:> > I'm using the default mount operations, as far as NFS server
:> > not responding messages, i have no clue, but the server is still
:> > up and i've seen that message happen when a lot of pressure is
:> > being put on an NFS server even though everyth
:
:I would just like to say, that unlike certain zealots of other operating
:systems I've always been a bit hesitant to recommend FreeBSD over
:solaris because of this one factor (NFS).
:
:It now seems I can't think of a single reason, (I'm much more a
:cluster fan than an SMP fan) SMP just doe
:2 questions I had:
:
:1) you said you disabled partial writes that were causing these
:mmap() problems, they were causing problems because NFS had to
:muck with the structures directly in order to do zero copy?
: so if our NFS impelementation didn't do that it wouldn't be
:an issue probably. I
On Wed, 21 Apr 1999, Alfred Perlstein wrote:
> On Wed, 21 Apr 1999, Kevin Day wrote:
>
> >
> > Try mounting with -d... Can I make a guess that the NFS mount is going over
> > 100MB ethernet? I have a strong theory that the dynamic retransmit timer
> > needs rework for low latency connections, wi
Great work guys! It almost seems that -current is more stable than
-stable!
Matt
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
On Wed, 21 Apr 1999, Kevin Day wrote:
> > yeah the clocks are not setup properly :) but otherwise i'm just
> > gonna say HOLY SH*T you fixed NFS! :)
>
>
> We all owe Matt big for this. :)
>
>
> > I'm using the default mount operations, as far as NFS server
> > not responding messages, i have n
> yeah the clocks are not setup properly :) but otherwise i'm just
> gonna say HOLY SH*T you fixed NFS! :)
We all owe Matt big for this. :)
> I'm using the default mount operations, as far as NFS server
> not responding messages, i have no clue, but the server is still
> up and i've seen that m
This PR is no longer validate now that g77 has enter
the base distribution.
--
Steve
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
SMP on -current would lose the WCPU and CPU times after a while in top's
output, this seems to be fixed on my machine/mobo with the latest source.
Asus PD2 afaik dual 400mhz.
thanks guys, great work!
-Alfred
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-curren
On Tue, 20 Apr 1999, Matthew Dillon wrote:
> NFS patch #6 is now available for -current. This patch has been
> extensively tested with NFS and with FFS+softupdates and has not
> screwed up yet, so I'm reasonably confident that it will not
> scrap whole filesystems :-)
>
> h
> > > P.S.: USBDI as in, our version of it. The people from the consortium
> > > kicked us out.
>
>
> > Can you elaborate on the reason that USBDI does not FreeBSD
> > to be involved with the consortium?
>
> Money. We cannot pay the fee (>1000 US $) to join the kindergarten aka
> consortium
> > P.S.: USBDI as in, our version of it. The people from the consortium
> > kicked us out.
> Can you elaborate on the reason that USBDI does not FreeBSD
> to be involved with the consortium?
Money. We cannot pay the fee (>1000 US $) to join the kindergarten aka
consortium. No company was w
On 21-Apr-99 Martin Blapp wrote:
>
> Hi,
>
> Recently I bought a new laptop and my ed0-pccard stopped working. This
> happened before the newconfig stuff came in. I first thought there were
> some irq-related problems, but I wasn't able to figure out where the
> problems are. The pccard-controll
On Wed, 21 Apr 1999 p...@originative.co.uk wrote:
> > -Original Message-
> > From: Peter Wemm [mailto:pe...@netplex.com.au]
> > Sent: 20 April 1999 21:20
> > To: Doug Rabson
> > Cc: Takanori Watanabe; freebsd-current@freebsd.org
> > Subject: Re: newbus and modem(s)
> >
> >
> > Doug Rabs
An egcs optimizer bug caused incorrect tcp checksum recalculation in libalias
for the rewritten PORT command packet and the server subsequently discard the
packet.
The following piece of C code (from TcpChecksum() in alias_util.c)
u_short *ptr;
int sum, oddbyte;
oddbyte =
66 matches
Mail list logo
