82559 information

1999-10-12 Thread David Holloway

To David Greenman or.. whoever is maintaining if_fxp.c
I picked up an 82559 card from compusa today...
Guess what?! It's device id was 0x1030 instead of 0x1229.

I adjusted my driver to match and it seems to work fine.

Of course, I haven't tried it yet with FreeBSD.
(I was using vxWorks.)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: kernel broken? (pcm)

1999-10-12 Thread Alexander Leidinger

On 11 Oct, Bill Fumerola wrote:

 #makeoptions CONF_CFLAGS=-fno-builtin
 
 We have enough breakages with the _documented_ kernel options that we

As Bruce Evans already said, It's documented.

 don't need to go hunting down oddities. :

Have you seen the '#' in "#makeoptions"? I assume a '#' in the config
file means: "Hey config, don't look at this!". Please correct me if I'm
wrong.

I've tested both variants with and without '#'. After editing the file I
did a 'config -r CONFIG', 'cd ../../compile/CONFIG', 'make depend',
'make'. I get the error independently of CONF_FLAGS.
Back at home I do it again if you want. 

Bye,
Alexander.

-- 
http://netchild.home.pages.de   A.Leidinger @ WJPServer.CS.Uni-SB.de



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 3dfx Driver?

1999-10-12 Thread Stephen Hocking

Has anyone ported the linux 3DFx Driver to FreeBSD?

Don't think so.

Why?  You volunteering? =)


I made a start on it earlier this year, but the final step (mapping the card 
memory) I got wrong, which then locked up the machine. The box the code is on 
is the other side of the world at the moment unfortunately.


Stephen



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Still waiting for xl driver reports

1999-10-12 Thread Pierre Beyssac

On Sun, Oct 10, 1999 at 04:59:34PM -0400, Bill Paul wrote:
 A while back I posted a message here saying that I'd changed the xl driver
 a bit to hopefully improve performance for 3c90xB and later adapters (i.e.
 the "cyclone," "hurricane" and "tornado" chipsets). I asked for people
 to report if the changes helped, hurt, made no difference or were totally 
 broken.
 
 So far not one person has said so much as a word to me on this subject.

I use the xl device (two cards: xl0 and xl1) in my kernel (compiled
on October 4th) and hadn't realized I was using the new driver. I
only noticed weird things last Sunday when the interface hung while
I was trying a tcpdump on it (I was loggued remotely, which explains
why I saw the problem immediately)... Then there was a "xl1: watchdog
timeout" and things went back to normal.

I compiled today's kernel to see if it made any difference, and I
can confirm I can repeat it easily you wish. The watchdog timeout
seems to happen every time I get out of promiscuous mode, and (very
seldom) at other random moments.

 To reiterate, this only concerns people with the following adapters:

Here's what I have:

xl0: 3Com 3c900-COMBO Etherlink XL irq 11 at device 10.0 on pci2
xl0: Ethernet address: 00:10:5a:bf:13:96
xl0: selecting 10baseT transceiver, half duplex
xl1: 3Com 3c905B-TX Fast Etherlink XL irq 11 at device 17.0 on pci0
xl1: Ethernet address: 00:c0:4f:67:0b:82

It's on xl1 that I have problems, although I'm not sure this wouldn't
happen on xl0 too (xl0 is configured down at the moment).

Now regarding performance, I haven't made extensives tests. The
closest thing to that that I have in mind is to stretch that
2*100Mbps trunking link we configured this morning between two of
our ethernet switches :-)
-- 
Pierre Beyssac  [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: People getting automatically unsub'ed from -arch

1999-10-12 Thread Jonathan M. Bresler


thanks for the note on bouncefilter.
i'll take a look at it.
may be just what i am looking for..
may be better than what i am using already.
always interested in somethatngthat will help me 
do this better.

jmb


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: kernel broken? (pcm)

1999-10-12 Thread A . Leidinger

On 12 Okt, [EMAIL PROTECTED] wrote:

   You can try the patch in (my) PR 'kern/14278'.

Works.

Bye,
Alexander.

-- 
   What do you mean, my birth certificate expired?

http://netchild.home.pages.de   A.Leidinger+Home @ WJPServer.CS.Uni-SB.de



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Proper Whacking Weeding

1999-10-12 Thread Marc van Woerkom

It took me some fiddling to get a -current system from begin of September 
to build present -current.

To achieve this, among other things, I cleaned up. 
That box is building from source for over two years now, and there were 
quite a lot of old files in the directory hierarchy. 

From rotten headers in /usr/include and strange libs in /usr/lib 
(libtermcap.so.2?) to strange locale stuff in /usr/share/misc 

However I might have whacked a bit too much, as Emacs (both 19 and 20)
display is messed up in textmode. vi and sysinstall however work.
And under X emacs still works. Anyone has an idea what could be wrong?
 

More systematically:
Is there a way to ensure that /usr/include, /usr/share/.. and such
are rebuilt properly? (No files missing, no old files messing things up)


Regards,
Marc



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Request for Flames

1999-10-12 Thread Michael Lucas

Folks,

I'm writing a series of web pages on how to ask for help on the
FreeBSD mailing lists.

From time to time, some innocent newbie wanders in here asking a
question with far too little information.  ("CVSup/pn0/sio.c doesn't
work. Why not?")

On occasion, you folks have taken the time to write detailed notes
describing the exact information you need to solve these problems.
(On other occasions, said newbie is seen around town: a little bit
here, a little bit there... but that's another problem.)

I'me searched the mail archives looking for these messages, and am
having difficulty finding them.  (It's difficult to search for "That
message where Bill Paul told a newbie in excruciating detail what he
needed to fix the problem, and what would happen to the next newbie
who asked this question without providing this information.") Lots of
questions, very few detailed answers.

If any of you have copies of messages that you have previously sent,
describing what information you need to solve a particular problem, I
would appreciate it if you would forward these to me.  I'll use this
information to write another guide.

For an example of what I'm trying to do, take a look at:

http://www.blackhelicopters.org/~dispatch/report/nic.html

My eventual goal is to have something like this for every troublesome
part of the system.  Hopefully newbies will either read these and give
the proper information, or go away and leave us alone.  ;)

Thanks,
==ml


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Linux X Server

1999-10-12 Thread Bill A. K.

Hi,
 Has anyone ever run a Linux X Server under FreeBSD/Linux Emulation? I'm
trying to run the Voodoo Banshee server from Creative Labs. The reason I'm
trying to do this is because when I run XFree86 3.3.5, it screws up my
console display when I exit X. The Linux Server is looking to open /dev/tty9
and it can't. I tried putting a hard link from /dev/tty9 to /dev/ttyv9 but
when i started X it paniced the kernel :)

Is there any way first of all to fix 3.3.5 to work, and if not, to get the
Linux server to work? Is there any way to somehow mimic /dev/tty9 for it?

I'm running 4.0-CURRENT, and the console garble thing also happened on
3.2-RELEASE

Thanks in advance for your help.

Bill
[EMAIL PROTECTED]











To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: People getting automatically unsub'ed from -arch

1999-10-12 Thread Daniel C. Sobral

"Jason K. Fritcher" wrote:
 
 I must say that Jonathan has been more than fair. About a year, maybe a year
 and a half ago, I didn't have a dedicated connection, and was doing smtp on
 demand, with my ISP spooling mail for me when I wasn't online. On average, I
 would get approximate, 20-30 messages during the night while I was offline,
 and twice a night, for each message, my ISP would send a message back to
 freebsd.org saying that the messages were still sitting in a queue waiting
 to be delivered. So for a period of a couple months, he put up with an
 average of ~50/day messages saying that my mail hadn't been delivered yet.
 Personally I was suprised I wasn't killed after the first week.

Interestingly, I used to have problems once. My provider had a
problem in which it's users would stop being recognized at times,
resulting in 5xx messages. It would last only a few minutes (well,
it could last longer at night), but it would happen again and again
throughout the day, which, I guess, generates the pattern that leads
jmb to unsubscribe people.

The funny thing is... the problem happened because of a bug on
FreeBSD's nis. :-)

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"I always feel generous when I'm in the inner circle of a
conspiracy to subvert the world order and, with a small group of
allies, just defeated an alien invasion. Maybe I should value myself
a little more?"




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: scsi tape driver wants an update

1999-10-12 Thread Daniel C. Sobral

Matthew Jacob wrote:
 
 This is a harmless message for the moment. I took a look at the new
 make_dev stuff- it's more than a no-brainer to add because there's a lot
 of stuff about supported device nodes, etc... I'll try and get back to
 this after FreeBSDcon.

Funny, phk's comments led me to believe it's actually easier to use
make_dev() (!= makedev(), btw -- maybe you looked up the wrong
one?).

And, talking about phk, it is also my impression that it is his
intent to push these changes as fast as he can. He gets strange at
this time of the year, y'know... I think Jordan once posted an
interesting explanation for this phenomenum. :-)

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"I always feel generous when I'm in the inner circle of a
conspiracy to subvert the world order and, with a small group of
allies, just defeated an alien invasion. Maybe I should value myself
a little more?"




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 82559 information

1999-10-12 Thread Brooks Davis

On Tue, 12 Oct 1999, David Holloway wrote:

 To David Greenman or.. whoever is maintaining if_fxp.c
 I picked up an 82559 card from compusa today...
 Guess what?! It's device id was 0x1030 instead of 0x1229.
 
 I adjusted my driver to match and it seems to work fine.

Support was added in -current Sept 6.  It appears that no one has back
ported it yet.

-- Brooks



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: scsi tape driver wants an update

1999-10-12 Thread Poul-Henning Kamp

In message [EMAIL PROTECTED], "Daniel C. Sobral" writes:
Matthew Jacob wrote:
 
 This is a harmless message for the moment. I took a look at the new
 make_dev stuff- it's more than a no-brainer to add because there's a lot
 of stuff about supported device nodes, etc... I'll try and get back to
 this after FreeBSDcon.

Funny, phk's comments led me to believe it's actually easier to use
make_dev() (!= makedev(), btw -- maybe you looked up the wrong
one?).

And, talking about phk, it is also my impression that it is his
intent to push these changes as fast as he can. He gets strange at
this time of the year, y'know... I think Jordan once posted an
interesting explanation for this phenomenum. :-)

"This time of the year" == "This time in the release cycle"

If we want to have a somewhat clean line before 4.0 now is the time
to push it through, not after the code freeze.

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: scsi tape driver wants an update

1999-10-12 Thread Matthew Jacob

 "This time of the year" == "This time in the release cycle"
 
 If we want to have a somewhat clean line before 4.0 now is the time
 to push it through, not after the code freeze.

And could you mention when the code freeze might be so that some of us
could plan our work? Perhaps I've missed something, but I hadn't heard
when the freeze would be. I have a *lot* of things to consider changing
before it.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: scsi tape driver wants an update

1999-10-12 Thread Poul-Henning Kamp

In message [EMAIL PROTECTED], Matthew Jacob 
writes:
 "This time of the year" == "This time in the release cycle"
 
 If we want to have a somewhat clean line before 4.0 now is the time
 to push it through, not after the code freeze.

And could you mention when the code freeze might be so that some of us
could plan our work? Perhaps I've missed something, but I hadn't heard
when the freeze would be. I have a *lot* of things to consider changing
before it.

I have no idea when the code freeze happens, neither has anybody else.

Looking at my complete collection of FreeBSD CDs on the shelf here
I would put my money (but not too much) on january 2000.

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: scsi tape driver wants an update

1999-10-12 Thread Matthew Jacob



On Tue, 12 Oct 1999, Poul-Henning Kamp wrote:

 In message [EMAIL PROTECTED], Matthew Jacob 
writes:
  "This time of the year" == "This time in the release cycle"
  
  If we want to have a somewhat clean line before 4.0 now is the time
  to push it through, not after the code freeze.
 
 And could you mention when the code freeze might be so that some of us
 could plan our work? Perhaps I've missed something, but I hadn't heard
 when the freeze would be. I have a *lot* of things to consider changing
 before it.
 
 I have no idea when the code freeze happens, neither has anybody else.
 
 Looking at my complete collection of FreeBSD CDs on the shelf here
 I would put my money (but not too much) on january 2000.

Well, you scared me with the "not after the code freeze" statement. I
would like the work I do for FreeBSD 4.0 not to be as incomplete as it was
for FreeBSD 3.0, so making plans as to when new feature freeze is would be
a "good thing (tm)".





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: scsi tape driver wants an update

1999-10-12 Thread Poul-Henning Kamp

In message [EMAIL PROTECTED], Matthew Jacob 
writes:

 And could you mention when the code freeze might be so that some of us
 could plan our work? Perhaps I've missed something, but I hadn't heard
 when the freeze would be. I have a *lot* of things to consider changing
 before it.
 
 I have no idea when the code freeze happens, neither has anybody else.
 
 Looking at my complete collection of FreeBSD CDs on the shelf here
 I would put my money (but not too much) on january 2000.

Well, you scared me with the "not after the code freeze" statement. I
would like the work I do for FreeBSD 4.0 not to be as incomplete as it was
for FreeBSD 3.0, so making plans as to when new feature freeze is would be
a "good thing (tm)".

I'd say try to have the boat rocking done by dec 1st, but that is merely
a guess.

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: People getting automatically unsub'ed from -arch

1999-10-12 Thread Rodney W. Grimes

 "Rodney W. Grimes" wrote:
  
   
"Accidental" removals from the lists are so common that I give up.  I no
longer even try to get back on them -- it's been happening for _years_ now,
and I have made multiple complaints about it, and if it's not a problem for
whoever runs the mailing lists, then I just don't care that much.
  
 only one comment.   i remove people from the lists whenever
   their email bounces.  the threshhold is approximately 30 messages in a
   24 hour period.   mail may bounce due to DNS problems, mail box full,
   MTA misconfiguration.  i also remove people that send vacation
   messages to the list.  oh, and spammers.
  
  Perhaps these threshholds could use some minor adjustments, or perhaps
  my interpretation of the above policy is not quite what really happens.
 
   Having been in a situation similar to Jonathan's (managing a large
 site, many lists, thousands of users) I can only say that it's hard to
 appreciate the difficulty of the task without experiencing it. I think
 he does a fine job, extending people more patience than I used to. :) 

And just who did you think passed the hat onto JMB?  

He is doing an outstanding job of postmaster, but it seems we have a
small problem that perhaps can easily be fixed by some minor adjustments,
perhaps not.

The biggest part of my response was an attempt to more fully
understand his current ``policy'', in that the original statements
about it where lacking in detail.


-- 
Rod Grimes - KD7CAX - (RWG25)[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



SMP stack faults...

1999-10-12 Thread Matthew Jacob


Just a followup question on my question from a week ago or so ther was
indeed a stack overflow I'd guess- I check the code path more carefully
and there was a 2KB stack buffer there (oof)- and removing it seemed to
make the problem go awaySo the question here is "Shouldn't this have
been a more obvious fault"?

-matt




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Linux X Server

1999-10-12 Thread David Scheidt

On Tue, 12 Oct 1999, Bill A. K. wrote:

 Hi,
  Has anyone ever run a Linux X Server under FreeBSD/Linux Emulation? I'm
 trying to run the Voodoo Banshee server from Creative Labs. The reason I'm

Yup.  I run a Voodoo Banshee, with the Creative Labs Linux X server.   This
is on -CURRENT just before newpcm and newpnp, and XFree 3.3.3.  I don't
remember having to do anything too wild to get it working.  The one problem
I do remember is that it doesn't play nicely with /dev/sysmouse.  I have to
use the real mouse device, and can't run moused.  I don't have access to the
machine at the moment, so I cannot tell you much more than that.  I will
take a look at the machine when I get home, and see what else I might have
done.  I don't run xdm, which might be an issue.

David Scheidt



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Request for Flames

1999-10-12 Thread Daniel C. Sobral

Michael Lucas wrote:
 
 If any of you have copies of messages that you have previously sent,
 describing what information you need to solve a particular problem, I
 would appreciate it if you would forward these to me.  I'll use this
 information to write another guide.

I guess I ought to see what you already have, but... well, I'm lazy,
and not connected right now. :-)

Whatever you do, *please* make a mention of the sections in the
handbook that deal precisely with this kind of stuff! 

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"I always feel generous when I'm in the inner circle of a
conspiracy to subvert the world order and, with a small group of
allies, just defeated an alien invasion. Maybe I should value myself
a little more?"



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: People getting automatically unsub'ed from -arch

1999-10-12 Thread Andre Oppermann

Jonathan M. Bresler wrote:
 
 thanks for the note on bouncefilter.
 i'll take a look at it.
 may be just what i am looking for..
 may be better than what i am using already.
 always interested in somethatngthat will help me
 do this better.

That is what I was talking about. With ezmlm there is no need to deal
with bounces anymore, it does that completly automatically with VERP.
At this time it only runs with qmail, but it might be possible to
teach it to like postfix (should be even easy IMHO). I'll give it a
shot if there is a chance that it will be used eventually.

I know some guys with list's in the three digit k to one digit M range
which don't have to deal with bounces at any time. I know it's hard
to believe but it's true and I can provide you with names where one
can ask for confirmation.

More information about ezmlm can be found on
 ftp://koobera.math.uic.edu/www/ezmlm.html (Authors homepage)
and
 http://www.ezmlm.org (extended version, ezmlm-idx)

more info about VERP is here
 ftp://koobera.math.uic.edu/www/proto/verp.txt (very interesting)

and about how it handles bounces perfectly automatic:
 http://www.ezmlm.org/faq-0.32/FAQ4.html#ss4.9 (ezmlm path for bounces)
plus
 http://www.ezmlm.org/faq-0.32/FAQ4.html#ss4.33 (how bounces are
handled)


-- 
Andre Oppermann

CEO / Geschaeftsfuehrer
Internet Business Solutions Ltd. (AG)
Hardstrasse 235, 8005 Zurich, Switzerland
Fon +41 1 277 75 75 / Fax +41 1 277 75 77
http://www.pipeline.ch[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: People getting automatically unsub'ed from -arch

1999-10-12 Thread Brad Knowles

At 9:23 PM +0200 1999/10/12, Andre Oppermann wrote:

 I know some guys with list's in the three digit k to one digit M range
 which don't have to deal with bounces at any time. I know it's hard
 to believe but it's true and I can provide you with names where one
 can ask for confirmation.

And Bryan Costales  Eric Allman have hacked sendmail to support 
VERPs, and last I heard InfoBeat was handling on the order of several 
million customers per day.  Of course, they're doing an e-mail merge 
operation so that each recipient gets a unique message, but that 
would just put an even heavier load on the system than a mailing list 
the same size.

-- 
   These are my opinions -- not to be taken as official Skynet policy
  
|o| Brad Knowles, [EMAIL PROTECTED]Belgacom Skynet NV/SA |o|
|o| Systems Architect, News  FTP Admin  Rue Col. Bourg, 124   |o|
|o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels   |o|
|o| http://www.skynet.be Belgium   |o|
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
  Unix is like a wigwam -- no Gates, no Windows, and an Apache inside.
   Unix is very user-friendly.  It's just picky who its friends are.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Why Adaptec 1540 bombing?

1999-10-12 Thread Warner Losh

In message [EMAIL PROTECTED] FreeBSD
Bob writes:
: It is a long shot, but I am curious if anyone knows of any problems in
: using the Adaptec 1540A on 3.x or 4.x machines?

The aha 1540 driver (me) didn't have access to the 1540A cards, so I
made changes blind and never tested (nor did those folks that bugged
me to make them).

If you can send me this card, I can see what I can do about making it
work with the aha driver.  There are problems with CAM and this
hardware's use of transfer residuals which might make it hard to get
working.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: People getting automatically unsub'ed from -arch

1999-10-12 Thread Andre Oppermann

Brad Knowles wrote:
 
 At 9:23 PM +0200 1999/10/12, Andre Oppermann wrote:
 
  I know some guys with list's in the three digit k to one digit M range
  which don't have to deal with bounces at any time. I know it's hard
  to believe but it's true and I can provide you with names where one
  can ask for confirmation.
 
 And Bryan Costales  Eric Allman have hacked sendmail to support
 VERPs, and last I heard InfoBeat was handling on the order of several
 million customers per day.  Of course, they're doing an e-mail merge
 operation so that each recipient gets a unique message, but that
 would just put an even heavier load on the system than a mailing list
 the same size.

That is just how VERP works, every email is unique (at least the
return-path). They must be crazy to run a several million recipients
mailing list with sendmail... Do you remember the time when the
FreeBSD lists were driven by sendmail? The lists were lagging several
hours behind. And I don't think we have high two or three digit k
subscribers on a single list. Maybe JMB can shed some light on how
many people are subscribed to the lists (just ranges).

-- 
Andre Oppermann

CEO / Geschaeftsfuehrer
Internet Business Solutions Ltd. (AG)
Hardstrasse 235, 8005 Zurich, Switzerland
Fon +41 1 277 75 75 / Fax +41 1 277 75 77
http://www.pipeline.ch[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: World fail + resulting cvsup failures

1999-10-12 Thread John Polstra

 mrynet# cvsup
 
 
 ***
 *** runtime error:
 ***Segmentation violation - possible attempt to dereference NIL
 ***pc = 0x2f
 ***
 
 Abort trap

I sent a heads up about this to the list a while ago.  There are
people working on the kernel problem that causes it.  For now, add
"@M3novm" to the cvsup command line (anywhere) as a work-around.

And don't try to build a new Modula-3 or CVSup on -current at the
moment.  It won't work.

John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra  Co., Inc.Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."-- Nora Ephron


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Why Adaptec 1540 bombing?

1999-10-12 Thread Darryl Okahata

Warner Losh [EMAIL PROTECTED] wrote:

 If you can send me this card, I can see what I can do about making it
 work with the aha driver.  There are problems with CAM and this
 hardware's use of transfer residuals which might make it hard to get
 working.

 If he can't, I've got a 1540A somewhere (in theory ;-) that I'd be
willing to lend out (if the address is in the US).  It's been years
since I've used it, and so I'm not 100% sure that it still works,
though.

--
Darryl Okahata
[EMAIL PROTECTED]

DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been following him all day.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Why Adaptec 1540 bombing?

1999-10-12 Thread Warner Losh

In message [EMAIL PROTECTED] Darryl Okahata writes:
:  If he can't, I've got a 1540A somewhere (in theory ;-) that I'd be
: willing to lend out (if the address is in the US).  It's been years
: since I've used it, and so I'm not 100% sure that it still works,
: though.

Well, I could install 2.2.x onto a disk and see if that works there.
Once I do that, I can then know if it works or not. :-)

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Proper Whacking Weeding

1999-10-12 Thread Peter Jeremy

On 1999-Oct-13 01:03:54 +1000, Marc van Woerkom wrote:
It took me some fiddling to get a -current system from begin of September 
to build present -current.

It might be useful if you documented exactly what you did.  This is
likely to be a very popular topic for the next few months...

Is there a way to ensure that /usr/include, /usr/share/.. and such
are rebuilt properly? (No files missing, no old files messing things up)

It shouldn't be possible to miss files during an installworld without
the installworld bombing out, though I'm not sure how to actually
confirm this.

I have had a couple of occurrences where my checked-out source tree
got out of step with my CVS tree (I'm not sure how this happened).
My solution here is to occasionally do a checkout into a temporary
tree and compare it with my active tree.  (An alternative would be
to squirrel away my local patches and blow away the active tree).

As for obsolete cruft in the root and /usr filesystems, you could try
"rm -fr /" :-).  Seriously, since installworld installs everything
with the current date, one way is to run "ls -ltr" on all all affected
directories and delete all files older than the installworld.

Peter
-- 
Peter Jeremy (VK2PJ)[EMAIL PROTECTED]
Alcatel Australia Limited
41 Mandible St  Phone: +61 2 9690 5019
ALEXANDRIA  NSW  2015   Fax:   +61 2 9690 5982


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: The eventual fate of BLOCK devices.

1999-10-12 Thread David Scheidt

On Tue, 12 Oct 1999, Kirk McKusick wrote:

 I would like to take a step back from the debate for a moment and
 ask the bigger question: How many real-world applications actually
 use the block device interface? I know of none whatsoever. All the
 filesystem utilities go out of their way to avoid the block device
 and use the raw interface. Does anyone on this list know of any
 programs that need/want the block interface? If there are none, or

It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated
disk devices.  There may be other RDBMSes that do this. 

David Scheidt



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Recent kernel hangs during boot with pnp sio.

1999-10-12 Thread Warner Losh

In message [EMAIL PROTECTED] Doug Rabson 
writes:
: If you find yourself with one of these and pnp is turned off, you can
: download the DOS utility from 3com. I recently had to do this for a friend
: (to turn pnp off). It was harder to find a DOS boot disk :-).

Sometimes these programs work with doscmd with magic command line
options...

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: The eventual fate of BLOCK devices.

1999-10-12 Thread Warner Losh

In message [EMAIL PROTECTED] David 
Scheidt writes:
: It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated
: disk devices.  There may be other RDBMSes that do this. 

EVERY RDBMS that I've ever seen or had to make work with my drivers
has been on the raw partition.  This is because the database writers
DO NOT LIKE OR TRUST the buffer cache due to its non-deterministic
nature of disk writing.  Are you sure that Sybase uses BLOCK devices
and not CHAR devices?

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: The eventual fate of BLOCK devices.

1999-10-12 Thread Julian Elischer


If you are going to respond to this. do it to 'freebsd-arch' only
I've redirected my resonse there..
don't respond to this one..

On Tue, 12 Oct 1999, Kirk McKusick wrote:

 I would like to take a step back from the debate for a moment and
 ask the bigger question: How many real-world applications actually
[...]

julian



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



ESS 1938 Soundcard

1999-10-12 Thread Neal Westfall

I just picked up a cheap PCI soundcard at Fry's for $17.99.  The box
has a picture of a card using the Trident 4DWAVE chip, but the card
in the box had an ESS 1938S chip on it.  Now I know there is no
support for this card yet, but was wondering if there is any support
planned for it in the near future?  Anyone heard of this PCI sound
chip?  Didn't see anything on the OSS webpage about it either.

Neal



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Linux X Server

1999-10-12 Thread Francis Jordan

"Bill A. K." wrote:

  Has anyone ever run a Linux X Server under FreeBSD/Linux Emulation? I'm
 trying to run the Voodoo Banshee server from Creative Labs. The reason I'm
 trying to do this is because when I run XFree86 3.3.5, it screws up my
 console display when I exit X. The Linux Server is looking to open /dev/tty9
 and it can't. I tried putting a hard link from /dev/tty9 to /dev/ttyv9 but
 when i started X it paniced the kernel :)
 
 Is there any way first of all to fix 3.3.5 to work, and if not, to get the
 Linux server to work? Is there any way to somehow mimic /dev/tty9 for it?


The Banshee only seems to have this problem when switching from a
graphical mode to the _standard_ text mode (80x25).   Adding the
following line to /etc/rc.conf

allscreens_flags="80x30"

fixed it for me.

Frank


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: The eventual fate of BLOCK devices.

1999-10-12 Thread Jonathan M. Bresler


 Sybase can use either block devices or raw disk.   We run all our
databases, Sybase, Oracle, etc. on raw disk.  the database engineers
here would kill me if i were to ask them to use a block device rather
than raw disk.

jmb


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



non-512 msdosfs patch

1999-10-12 Thread Chiharu Shibata

This is Chiharu Shibata, who sent the PR(misc/12992) before.
That PR's patch is to support non-512bytes/sector media for msdosfs.

I have been checking the CVS repository, but the patch is not committed yet.
I was hoping to be committed, before the patch is not available by another
modification of msdosfs.

The MO is very popular media in Japan, and 640MB/1.3GB MO are both
2048bytes/sector media.
So, It is a FAQ that "How can I use DOS/Windows formatted 640MB MO?".
In addition, NEC PC-98 uses non-512bytes/sector media generally.
It is useless for PC-98 without the patch, not too much to say.

I have reports that the patch works well, not only NEC PC-98, but also
PC/AT's FreeBSD3.2-RELEASE.

PS.
I don't subscribe freebsd-current ML.
About this theme, please send to me via freebsd98-hackers ML with Cc:.
(See Cc: of this mail)
-- 
Chiharu Shibata[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org

1999-10-12 Thread Warner Losh

In message [EMAIL PROTECTED] Doug Rabson 
writes:
: Due to the nature of the pnp code, it might be probed as ed1 instead of
: ed0.

I have a SBC here that has an onboard PNP ne2000 chip on it.  It comes
up as ed1 because I have ed0 at a wired address.  I don't see ed0 at
all, and it just works, so I just hacked my rc.conf to use ed1 rather
than ed0 like I did when it ran 3.3R.

Now for the obligitory tangent:
Does FreeBSD have the ability to reassign IRQs for PNP devices?  I
have one that is coming up at IRQ 5, but I have a non-PNP device that
is at 5, but many other IRQs free.  There is no way in the BIOS to set
which IRQs are used for PNP and which ones are designated for legacy
devices.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: How do I get a PCCARD modem to work?

1999-10-12 Thread Warner Losh

In message [EMAIL PROTECTED] "Justin T. Gibbs" writes:
: The pccard brokenness is not sio's fault.  If I were following where
: our PCCARD support was going, I might take a stab at fixing this myself...

Yes.  Pccard brokennes *IS* sio's fault.  It was written to only deal
with ISA busses and cannot attach to other busses (yet).  That's the
issue.  I did noticed that Doug submitted some changes that might
change this...  I'll have to look tonight after doing some
consulting..

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 3dfx Driver?

1999-10-12 Thread i think

there was a walkthrough on how to get the linux drivers running through the
linux emulation.  this is specifically for the quake3 test, i dont know how
it will fare on any other programs  ( havent tried) but q3test does work.
if you want, check it out

http://www.cybernet.com/~mtaylor/q3ahowto.html

Andrew
- Original Message -
From: "Jeroen Ruigrok/Asmodai" [EMAIL PROTECTED]
To: "Amancio Hasty" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, October 11, 1999 15:48
Subject: Re: 3dfx Driver?


 On [19991011 12:00], Amancio Hasty ([EMAIL PROTECTED]) wrote:
 
 Has anyone ported the linux 3DFx Driver to FreeBSD?

 Don't think so.

 Why?  You volunteering? =)

 --
 Jeroen Ruigrok van der Werven/Asmodai  asmodai(at)wxs.nl
 The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai
 Network/Security SpecialistBSD: Technical excellence at its best
 One from many.


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



How to report problems (was: Request for Flames)

1999-10-12 Thread Greg Lehey

On Tuesday, 12 October 1999 at 11:08:50 -0400, Michael Lucas wrote:
 Folks,

 I'm writing a series of web pages on how to ask for help on the
 FreeBSD mailing lists.

 From time to time, some innocent newbie wanders in here asking a
 question with far too little information.  ("CVSup/pn0/sio.c doesn't
 work. Why not?")

That's a *good* one.  Take a look at
http://www.lemis.com/questions.html for some alternatives.

 On occasion, you folks have taken the time to write detailed notes
 describing the exact information you need to solve these problems.
 (On other occasions, said newbie is seen around town: a little bit
 here, a little bit there... but that's another problem.)

 I'me searched the mail archives looking for these messages, and am
 having difficulty finding them.  (It's difficult to search for "That
 message where Bill Paul told a newbie in excruciating detail what he
 needed to fix the problem, and what would happen to the next newbie
 who asked this question without providing this information.") Lots of
 questions, very few detailed answers.

 If any of you have copies of messages that you have previously sent,
 describing what information you need to solve a particular problem, I
 would appreciate it if you would forward these to me.  I'll use this
 information to write another guide.

 For an example of what I'm trying to do, take a look at:

 http://www.blackhelicopters.org/~dispatch/report/nic.html

Looks good.  You probably need to structure it differently (for
example, have a link to things like OS revision and kernel config,
which will be needed in most cases).

Greg
--
See complete headers for address, home page and phone numbers
finger [EMAIL PROTECTED] for PGP public key


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Proper Whacking Weeding

1999-10-12 Thread Marc van Woerkom

 It might be useful if you documented exactly what you did.  This is
 likely to be a very popular topic for the next few months...

Not quite possible, because when things started to look foobar I was 
not cool enough to keep logging. :)

But I know some highlights of my tour:

o My Last successful -current build was

Sun Sep 19 19:18:42 CEST 1999


o Then I tried to rebuild on

Tue Oct  5 17:49:53 CEST 1999

  and got this one:

=== f77doc
/usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc
cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO 
-DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend;  /usr/obj/usr/src/tmp/usr/bin/make 
-DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all;  
/usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE 
-DNOSHARED -B install;  /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN 
-DNOPROFILE -DNOSHARED -B cleandir obj
rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH 
/usr/obj/usr/src/gnu/lib/libgcc/GRTAGS  /usr/obj/usr/src/gnu/lib/libgcc/GSYMS 
/usr/obj/usr/src/gnu/lib/libgcc/GTAGS
echo '#include i386/xm-i386.h'  config.h
echo '#include xm-freebsd.h'  config.h
echo '#include "i386/xm-i386.h"'  tconfig.h
echo '#include "i386/i386.h"'  tm.h
echo '#include "i386/att.h"'  tm.h
echo '#include "i386/freebsd.h"'  tm.h
echo '#include "i386/perform.h"'  tm.h
cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config 
-I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC 
-I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o 
/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c
*** Signal 12
Stop in /usr/src/gnu/lib/libgcc.

  So I decided to wait some times, in case this was related to
  changes to gcc.


o Next try was 

Sun Oct 10 12:55:50 CEST 1999

  This time I had a look into freebsd-current and src/UPDATING before 
  and noticed that I had to build a new kernel before.
  No problems. Kernel compiled, installed and booted.


o Later,

Sun Oct 10 13:38:40 CEST 1999

  during make buildworld, I got this one:

cc -O -pipe -I/usr/src/usr.bin/make-I/usr/obj/usr/src/tmp/usr/include -c 
/usr/src/usr.bin/make/arch.c
In file included from /usr/include/sys/stat.h:50,
 from /usr/src/usr.bin/make/arch.c:97:
/usr/include/sys/time.h:289: time.h: No such file or directory
/usr/src/usr.bin/make/arch.c:100: ctype.h: No such file or directory
/usr/src/usr.bin/make/arch.c:101: ar.h: No such file or directory
/usr/src/usr.bin/make/arch.c:102: utime.h: No such file or directory
/usr/src/usr.bin/make/arch.c:104: stdlib.h: No such file or directory
In file included from /usr/src/usr.bin/make/arch.c:105:
/usr/src/usr.bin/make/make.h:53: ctype.h: No such file or directory
/usr/src/usr.bin/make/make.h:76: stdlib.h: No such file or directory
In file included from /usr/src/usr.bin/make/make.h:80,
 from /usr/src/usr.bin/make/arch.c:105:
/usr/src/usr.bin/make/lst.h:51: stdlib.h: No such file or directory
/usr/src/usr.bin/make/arch.c: In function `ArchStatMember':
/usr/src/usr.bin/make/arch.c:464: `SARMAG' undeclared (first use in this function)
/usr/src/usr.bin/make/arch.c:464: (Each undeclared identifier is reported only once
/usr/src/usr.bin/make/arch.c:464: for each function it appears in.)
/usr/src/usr.bin/make/arch.c:468: storage size of `arh' isn't known
/usr/src/usr.bin/make/arch.c:514: storage size of `sarh' isn't known
/usr/src/usr.bin/make/arch.c:540: `ARMAG' undeclared (first use in this function)
/usr/src/usr.bin/make/arch.c:552: sizeof applied to an incomplete type
/usr/src/usr.bin/make/arch.c:553: `ARFMAG' undeclared (first use in this function)
/usr/src/usr.bin/make/arch.c:621: sizeof applied to an incomplete type
/usr/src/usr.bin/make/arch.c:623: sizeof applied to an incomplete type
/usr/src/usr.bin/make/arch.c: In function `ArchFindMember':
/usr/src/usr.bin/make/arch.c:785: `SARMAG' undeclared (first use in this function)
/usr/src/usr.bin/make/arch.c:798: `ARMAG' undeclared (first use in this function)
/usr/src/usr.bin/make/arch.c:814: dereferencing pointer to incomplete type
/usr/src/usr.bin/make/arch.c:815: dereferencing pointer to incomplete type
/usr/src/usr.bin/make/arch.c:818: sizeof applied to an incomplete type
/usr/src/usr.bin/make/arch.c:819: dereferencing pointer to incomplete type
/usr/src/usr.bin/make/arch.c:819: `ARFMAG' undeclared (first use in this function)
/usr/src/usr.bin/make/arch.c:819: dereferencing pointer to incomplete type
/usr/src/usr.bin/make/arch.c:826: dereferencing pointer to incomplete type
/usr/src/usr.bin/make/arch.c:834: dereferencing pointer to incomplete type
/usr/src/usr.bin/make/arch.c:834: dereferencing pointer to incomplete type

Re: The eventual fate of BLOCK devices.

1999-10-12 Thread Peter Wemm

Warner Losh wrote:
 In message [EMAIL PROTECTED] Da
vid Scheidt writes:
 : It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated
 : disk devices.  There may be other RDBMSes that do this. 
 
 EVERY RDBMS that I've ever seen or had to make work with my drivers
 has been on the raw partition.  This is because the database writers
 DO NOT LIKE OR TRUST the buffer cache due to its non-deterministic
 nature of disk writing.  Are you sure that Sybase uses BLOCK devices
 and not CHAR devices?

Sybase is supposed to be run on char devices.  The Linux sybase release
notes refer to "Unfortunately Linux does not have raw (char) disk devices so
we have to make do".

Cheers,
-Peter



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Still waiting for xl driver reports

1999-10-12 Thread Jim Bloom

I keep seeing a watchdog timeout with my 3c905B-TX every time the machine
boots.  It seems to occur after everything has been probed and /etc/rc has
completed; around the time I get my login banner. I am running the dhcp client
to get my IP address.  I don't pound on the network very much so I can't tell
you how performance is.

Jim Bloom

Pierre Beyssac wrote:
 
 On Sun, Oct 10, 1999 at 04:59:34PM -0400, Bill Paul wrote:
  A while back I posted a message here saying that I'd changed the xl driver
  a bit to hopefully improve performance for 3c90xB and later adapters (i.e.
  the "cyclone," "hurricane" and "tornado" chipsets). I asked for people
  to report if the changes helped, hurt, made no difference or were totally
  broken.
 
  So far not one person has said so much as a word to me on this subject.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



COMMAND_SET ?

1999-10-12 Thread Chuck Robey

I'm looking at sys/boot/common/pnp.c so I can find out how pnp is handled,
and I found something called a COMMAND_SET, and I can't figure out what it
means.  Any takers?


Chuck Robey| Interests include C programming, Electronics,
213 Lakeside Dr. Apt. T-1  | communications, and signal processing.
Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and
(301) 220-2114 |   jaunt.mat.net : FreeBSD-current(Alpha)




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: COMMAND_SET ?

1999-10-12 Thread Donald J . Maddox

It's defined in sys/boot/common/bootstrap.h.  I think all you want to know
is in that file.

On Tue, Oct 12, 1999 at 09:46:12PM -0400, Chuck Robey wrote:
 I'm looking at sys/boot/common/pnp.c so I can find out how pnp is handled,
 and I found something called a COMMAND_SET, and I can't figure out what it
 means.  Any takers?
 
 
 Chuck Robey| Interests include C programming, Electronics,
 213 Lakeside Dr. Apt. T-1  | communications, and signal processing.
 Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and
 (301) 220-2114 |   jaunt.mat.net : FreeBSD-current(Alpha)
 
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: People getting automatically unsub'ed from -arch

1999-10-12 Thread Kenneth D. Merry

Ben Smithurst wrote...
 Jonathan M. Bresler wrote:
 
  i do NOT send the person mail to inform them that the are
  being removed from the mailing lists, because their email is bouncing.
 
 How about sending a message to them once every 24 hours for, say,
 a week? I imagine some of those bounces are due to temporary
 mis-configurations which will soon be fixed.

I dunno what jmb's general experience is, but my experience from the 15 or
so lists that I manage is that most bounces are from people who switch
ISPs, etc., and don't unsubscribe.  (Quota violations are another popular
cause nowadays.)

It generally isn't worth the effort to send mail informing them of the fact
that they've been unsubscribed, since it'll almost always keep bouncing.
They'll figure it out when they stop getting mail, if they care about the
list.

Things might be different, of course, for the FreeBSD lists since people
on these lists are generally much more clueful.

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Freebsd 4.0 and Linux

1999-10-12 Thread mariusz

Hi 
   
   What depth of FreeBSD's support for Linux applications under 
   FreeBSD 4.0?  I can't seem to find adequate information online.  
   Does the support comply with our current requirements for Linux?:
   
   minimum kernel version: 2.0.34
   minimum glibc version: 2.0.7-19
   
Mariusz



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...

1999-10-12 Thread Warner Losh

In message [EMAIL PROTECTED] Matthew Dillon writes:
: Forget the drilling!  Blood conducts electricity... simply *installing*
: a motherboard in those fraggin sharp-edged sheet metal chassis is enough!

I've had one or two cheapo mo-bos that haven't worked at 100MHz after
spattering human blood on it from said sharp-edged sheet metal
corners...

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message