On Wed, 29 Mar 2000 09:22:11 +0200, Johan Karlsson wrote:
> I have just submitted a 'follow-up' to the PR with this info.
Are you sure you sent mail to [EMAIL PROTECTED] with
"kern/17536" on the subject line? I can't see any follow-up on the PR.
:-(
Ciao,
Sheldon.
To Unsubscribe: send mail
At Tue, 28 Mar 2000 16:24:17 +0200, Sheldon Hearn wrote:
>
>
>On Thu, 23 Mar 2000 09:21:50 +0100, Johan Karlsson wrote:
>
>> Before this is commited please have a look at the PR kern/17536
>> which addresses a similar thing.
>
>When using the patch you provide on that PR, what does the How-To-Repe
Brian Somers wrote:
>
> If you want to test your results, I'd suggest using pppoed... if you
> can talk to yourself and to ppp(8) then you've probably got it right.
>
> FWIW, my eventual aim is to bring more netgraph stuff into ppp(8)
Nick,
Everything you need to do should be found in
the p
Robert Withrow wrote:
>
> Don't see anything about this on the web page. Is there any
> activity/interest in porting FreeBSD to the PowerPC, and in
> particular to embedded (non-MAC) systems? I've been pinging
> "core" people about this but haven't seem to teak their interrest.
>
> I gather th
On Tue, 28 Mar 2000, Dennis wrote:
OK, personally, I've had enough of reading this. This strikes me as Troll,
and I think Dennis has lost it, but I actaully *want* the following in the
archives...
I have never submitted code to FreeBSD because somebody else has usually
already beaten me to it, n
If you want to test your results, I'd suggest using pppoed... if you
can talk to yourself and to ppp(8) then you've probably got it right.
FWIW, my eventual aim is to bring more netgraph stuff into ppp(8)
> I friend of mine just got Pac$Bell Internet (see the story in
> -questions), and he
On Sat, Mar 25, 2000 at 07:58:50AM +0900, Akinori -Aki- MUSHA wrote:
> Hi, FreeBSD hackers!
Hi knu, fellow zsh user! :)
> I suppose FreeBSD users who use zsh (the Z shell) must have been
> customizing it so well and got some neat definitions for FreeBSD (or
> *BSD rather) environment.
My /etc/z
On Sat, Mar 25, 2000 at 06:34:19PM +0100, Christian Weisgerber wrote:
> MikeM <[EMAIL PROTECTED]> wrote:
>
> > Has anyone thought of Unicode support on FreeBSD?
>
> It has crossed my mind...
>
> > I think that it is inevitable that eventually FreeBSD
> > will *need* to support unicode if it wa
> Don't see anything about this on the web page. Is there any
> activity/interest in porting FreeBSD to the PowerPC, and in
> particular to embedded (non-MAC) systems? I've been pinging
> "core" people about this but haven't seem to teak their interrest.
Yes, there is very real interest. Are y
Don't see anything about this on the web page. Is there any
activity/interest in porting FreeBSD to the PowerPC, and in
particular to embedded (non-MAC) systems? I've been pinging
"core" people about this but haven't seem to teak their interrest.
I gather that BSDI has a powerPC port, but I'd r
>The only thing remaining is that the card is reported as
>Intel EtherExpress Pro 10/100B (which used to have i82557),
>but it's a card with i82559.
>
>This can be detected by reading the revision code of
>integrated PHY (registers 2 and 3) through MDI in CSR space
>(pg. 87 in i82559 datasheet or
David Greenman wrote:
>
> >At the moment I have a spare machine
> >and the NIC available for testing.
> >
> >Please let me know if you are interested
> >in my offer to test your patches to 4.0 driver?
>
>Thanks, Milon. I've attached patches which I believe will fix the problem
> as seen with
On Tue, 28 Mar 2000, Dennis wrote:
>
> If you fellows put as much time into freebsd as you do flaming me we
> wouldnt need this crap. :-)
>
*Plonk!*
Brian Beattie| This email was produced using professional quality,
[EMAIL PROTECTED] | standards based software. Users of Micr
On Tue, Mar 28, 2000 at 07:18:57AM -0800, Ron Rosson wrote:
> On Mon, 27 Mar 2000, Wes Peters was heard blurting out:
>
> > Ron 'The InSaNe One' Rosson wrote:
> > >
> > > Ummm This is getting a little old. I am no programmer but read this
> > > list to get insight on what things may not work
It takes two to flame, really it does.
In message <[EMAIL PROTECTED]>, Dennis writes:
>At 05:04 PM 3/28/00 +0100, you wrote:
>>Dennis wrote:
>>
>>> obviously not the one that has the error. Are you paying attention?
>>
>>DG has just committed a fix for this. Are *YOU* paying attention?
>
>Good, t
At 05:04 PM 3/28/00 +0100, you wrote:
>Dennis wrote:
>
>> obviously not the one that has the error. Are you paying attention?
>
>DG has just committed a fix for this. Are *YOU* paying attention?
Good, then we can end this stupid thread.
If you fellows put as much time into freebsd as you do fla
Saw this on a qmail list. DJB's not got the best bedside manner, but
he's pretty good about preventing loss or damage to mail. What about
supporting his /etc/mta implementation instead?
--Chris (not the poster below)
From: "D. J. Bernstein" <[EMAIL PROTECTED]>
Subject: Re: FYI: FreeB
Dennis wrote:
> obviously not the one that has the error. Are you paying attention?
DG has just committed a fix for this. Are *YOU* paying attention?
> I passed on the info to DG on how to fix it. Work I do belongs to my
> company because they pay me to do it. I know few of you understand that,
:>
:>Have you contributed the fix to FreeBSD? I think I know the answer.
:
:I passed on the info to DG on how to fix it. Work I do belongs to my
:company because they pay me to do it. I know few of you understand that, So
:unless you want to attach the "copyright Emerging Technologies" to the
:dri
In message <[EMAIL PROTECTED]> Dennis writes:
: I passed on the info to DG on how to fix it. Work I do belongs to my
: company because they pay me to do it. I know few of you understand that, So
: unless you want to attach the "copyright Emerging Technologies" to the
: driver you cant use it.
You
On Tue, Mar 28, 2000 at 07:18:57AM -0800, Ron Rosson wrote:
>
> It is the go fix it yourself attitude I guess that gets me sometimes in
> both the mailing lists and IRC. There is some people in the user base
> that can not code but are able to find issues on there systems and would
> like to shar
Hi all,
I've recently run into a panic in tcp_output.c (after Jonathon's
latest commit, it seems), whereby, if I try to open a connection
to a server on my local machine, I get a panic in line 540 of
tcp_output.c.
e.g.: telnet localhost 80
will cause the panic.
I ahev not had much time to invest
> >I run the Intel Etherexpress in full duplex without any problems.
> obviously not the one that has the error. Are you paying attention?
Of course I do, I just wanted to point out that you are generalizing. "The
Intel Etherexpress does not work on FreeBSD" is not true - it works for
me. There a
>> Its an important driver. People get upset when they can't run full-duplex
>> mode. It makes linux MUCH more attractive when you can run your $39. card
>> at twice the speed.
>
>I run the Intel Etherexpress in full duplex without any problems.
obviously not the one that has the error. Are you
On Mon, 27 Mar 2000, Wes Peters was heard blurting out:
> Ron 'The InSaNe One' Rosson wrote:
> >
> > Ummm This is getting a little old. I am no programmer but read this
> > list to get insight on what things may not work or what might work.. It
> > has saved my BACKSIDE many times. I am also
On Thu, 23 Mar 2000 09:21:50 +0100, Johan Karlsson wrote:
> Before this is commited please have a look at the PR kern/17536
> which addresses a similar thing.
When using the patch you provide on that PR, what does the How-To-Repeat
do? The more detail you can give in your answer, the better.
I have an onboard intel chipset fxp0 and an intel management 100 adaptor. I have not
gotten the
error that is being discussed, but I am trying to make it netboot. I would like to
help out with
the problem everyone is having. Do I need to run a particular version and
configuration of
freebsd?
I just started to notice a little hostility. Please feel free to flame me all you
want, but do it
in private. One of the best things that freebsd has is the teamwork. People from all
over the
world working together for a common belief. One day I will be part of a large
software project,
but
In <[EMAIL PROTECTED]>, p_a_r wrote:
>
> Can anyone tell me the differens in FreeBSD and NetBSD. I would like
> to set up 2 internet servers whitch one should i take?
As long as you can't tell by yourself, you are usually better off with
FreeBSD, since it is easier to install and has more reso
David Malone <[EMAIL PROTECTED]> writes:
> I haven't checked carefully, but I expect that the linprocfs code
> has the same problem as the FreeBSD procfs code, in that it can
> expose suid executables which would not usually be run 'cos they
> are in inaccessible directories.
That is indeed corre
On Tue, Mar 28, 2000 at 12:11:28AM -0800, Brooks Davis wrote:
> On Tue, Mar 28, 2000 at 09:39:11AM +0200, Konrad Heuer wrote:
> >
> > The most important strength of NetBSD is its availability on many
> > different hardware platforms. If you plan to set up your servers on Intel
> > or DECalpha sof
It seems David Yeske wrote:
>
> ad0: UDMA ICRC READ ERROR blk# 3500173 retrying
> ad0: UDMA ICRC READ ERROR blk# 3500173 retrying
> ad0: UDMA ICRC READ ERROR blk# 3499709 retrying
> ad0: UDMA ICRC READ ERROR blk# 3499709 retrying
> ad0: UDMA ICRC READ ERROR blk# 3499709 retrying
> ad0: UDMA ICRC
I am getting a nasty error and I would like to resolve it. I know my hard drive is
"ok" according
to a couple of different tests including Western Digital DLT 2.2. Here is the error
and after
that is my dmesg.
ad0: UDMA ICRC READ ERROR blk# 3500173 retrying
ad0: UDMA ICRC READ ERROR blk# 35
On Tue, Mar 28, 2000 at 09:39:11AM +0200, Konrad Heuer wrote:
>
> The most important strength of NetBSD is its availability on many
> different hardware platforms. If you plan to set up your servers on Intel
> or DECalpha software, FreeBSD might do better for you. For example,
> FreeBSD supports
34 matches
Mail list logo
