82559 information

[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

May 99 Snapshot and -current

[Amancio Hasty]

Got a new disk and I am trying to upgrade from the May 1999 snapshot to today's 
current.

I recompiled the kernel , install  it and reboot afterwards the boot loader fails to 
load
the new kernel so should I upgrade my boot blocks with the latest sources?

Tnks

-- 

 Amancio Hasty
 [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

[The Hermit Hacker]

On Mon, 11 Oct 1999, Jonathan M. Bresler wrote:

>   when the MTA gives up trying to deliver the mail, i call it
> bounced.  so a 500 series error from the other MTA means the email has
> bounced.  

Have you considered  using bouncefilter for this?  I'm using it for the
PostgreSQL mailnig lists, and find its really cut down on my requirement
to intervene on 'dead addresses'... 

Marc G. Fournier   ICQ#7615664   IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: [EMAIL PROTECTED]   secondary: scrappy@{freebsd|postgresql}.org 



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

Re: scsi tape driver wants an update

[Matthew Jacob]

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.

On Sun, 10 Oct 1999, Andy Farkas wrote:

> 
> Just a reminder I guess,
> 
> # uname -v
> FreeBSD 4.0-CURRENT #0: Sun Oct 10 16:16:34 EST 1999
> 
> # mt retension
> 
> console emits (in bright white):
> 
> WARNING: driver sa should register devices with make_dev() (dev_t = "#sa/1")
> 
> 
> 
> --
>  
>  :{ [EMAIL PROTECTED]
>   
> Andy Farkas
> System Administrator
>Speednet Communications
>  http://www.speednet.com.au/
>   
> 
> 
> 
> 
> 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: kernel broken? (pcm)

[Bruce Evans]

> >>Such an errors results from (uncommented) kernel option
 ^^^
> >> 
> >> #makeoptions   CONF_CFLAGS=-fno-builtin
> > 
> > We have enough breakages with the _documented_ kernel options that we 
  
> > don't need to go hunting down oddities. :>

It's well documented.  -fno-builtin is a standard gcc option, and
CONF_FLAGS and its use of -fno-builtin is documented in 4 lines in LINT.

>   Does it mean that I throw away my PR with patches to
> the 'newpcm' files which add 'abs' definition and therefore
> make it possible to make kernel with 
> 
> makeoptions CONF_CFLAGS=-fno-builtin   ?

No, some patches are needed.  I think pcm should use explicit code
like (x < 0 : -x : x).  It only calls abs() twice.

> P.S. It seems to me that this option (or its absent) can
> severely influence kernel run time efficience (not in the 'abs'
> case, of course ;-).

I used to use it for all kernels as a side effect of putting it in
/etc/make.conf so that it gets used for LINT.  Any efficiency effects
seem to be limited to the +-0.1% range.  The only place where it is
likely to make much difference is for bcopy() vs memcpy() on some
machines.  The builtin memcpy() can be pessimal.  This is supposed to
be handled by using bcopy() for large copies and memcpy() (only) for
small, fix-sized copies.  The builtin memcpy() tends to be better for
small copies.  Since using memcpy() in the kernel is correct in some
cases, it is backed up by a function to handle cases where there is
no inline memcpy().

Bruce



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

Re: kernel broken? (pcm)

[Bruce Evans]

On Tue, 12 Oct 1999 [EMAIL PROTECTED] wrote:

> In <[EMAIL PROTECTED]> [EMAIL PROTECTED] wrote:
>   Such an errors results from (uncommented) kernel option
> 
> #makeoptions  CONF_CFLAGS=-fno-builtin

This option is used in LINT to help expose such errors before they are
committed.

>   because there is NO 'abs' function/macro in this files
> (ac97.c, channel.c and mss.c) and they can be only compiled using
> gcc's builtin 'abs'

abs() doesn't exist in the kernel, so it shouldn't be used.

> > linking kernel.debug
> > ac97.o: In function `ac97_setmixer':
> > /usr/src/sys/compile/WORK/../../dev/pcm/ac97.c(.text+0x18d): undefined reference 
>to `abs'
> > channel.o: In function `chn_setblocksize':

Test coverage of pcm in LINT is broken by not configuring pcm because of
conflicts with the old sound drivers.

Bruce



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

Re: fpu_aux.c - new breakage?

[Mike Smith]

> so i went to build yet again to see if i could get the three headed dog to
> walk again, and whammy!

I just fixed some of it, Bruce found some more.  Poul has been committing
without testing again.

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




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

PCM Failure in 4.0-current

[Michael A.Pacheco]

I've been trying to get my sound card to work for some time now. After
reading
quite a few messages from the freebsd-current mailing list I got it to an
almost working condition, but it's still not working...


--In the kernel I have--:

controller pnp0

device pcm0

--dmesg--:

pcm0:  at port
0x220-0x22f,0x388-0x38b,0x100-0x10f irq 5 drq 1,0 on isa0
unknown0:  at port 0x300-0x301 irq 9 on isa0
unknown1:  at port 0x200-0x207 on isa0

--

--sndstat--:

FreeBSD Audio Driver(newpcm) Oct 4 1999 22:09:04
Installed Devices:
pcm0:  at io 0x220 irq 5 drq 1:0 (1/1 channels
duplex)

-

When I try to play any type of sound (i.e.: cat whatever.au > /dev/audio) I
get this error:

start dma, failed to set bit 0xfe 0xff

Do you have any idea what could be causing this? It's also kinda strange how
it detects it as a Terratec Soundsystem when the card's an Analog Devices
AD1816.

Any help would be appreciated, I still lack any freebsd machine with sound
;).

-Thanks in Advance
Michael A. Pacheco




Get free email and a permanent address at http://www.netaddress.com/?N=1


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

fpu_aux.c - new breakage?

[Randy Bush]

so i went to build yet again to see if i could get the three headed dog to
walk again, and whammy!

randy


cc -O -pipe  -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -ansi 
-DKLD_MODULE -nostdinc -I-  -I/usr/obj/usr/src/sys/modules/gnufpu 
-I/usr/obj/usr/src/sys/modules/gnufpu/@ -I/usr/obj/usr/src/tmp/usr/include -c 
/usr/src/sys/modules/gnufpu/../../gnu/i386/fpemul/errors.c
cc -O -pipe  -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -ansi 
-DKLD_MODULE -nostdinc -I-  -I/usr/obj/usr/src/sys/modules/gnufpu 
-I/usr/obj/usr/src/sys/modules/gnufpu/@ -I/usr/obj/usr/src/tmp/usr/include -c 
/usr/src/sys/modules/gnufpu/../../gnu/i386/fpemul/fpu_arith.c
cc -O -pipe  -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -ansi 
-DKLD_MODULE -nostdinc -I-  -I/usr/obj/usr/src/sys/modules/gnufpu 
-I/usr/obj/usr/src/sys/modules/gnufpu/@ -I/usr/obj/usr/src/tmp/usr/include -c 
/usr/src/sys/modules/gnufpu/../../gnu/i386/fpemul/fpu_aux.c
/usr/src/sys/modules/gnufpu/../../gnu/i386/fpemul/fpu_aux.c: In function `fstsw_ax':
/usr/src/sys/modules/gnufpu/../../gnu/i386/fpemul/fpu_aux.c:118: dereferencing pointer 
to incomplete type
*** Error code 1

Stop in /usr/src/sys/modules/gnufpu.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1


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

Re: kernel broken? (pcm)

[Bill Fumerola]

On Tue, 12 Oct 1999 [EMAIL PROTECTED] wrote:

> > We have enough breakages with the _documented_ kernel options that we 
> > don't need to go hunting down oddities. :>
> 
>   Does it mean that I throw away my PR with patches to
> the 'newpcm' files which add 'abs' definition and therefore
> make it possible to make kernel with 
> 
> makeoptions CONF_CFLAGS=-fno-builtin   ?
> 
> P.S. It seems to me that this option (or its absent) can
> severely influence kernel run time efficience (not in the 'abs'
> case, of course ;-).

No. I was merely joking around. We welcome your patches.

-- 
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED]  -






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

Re: kernel broken? (pcm)

[nnd]

In <[EMAIL PROTECTED]> Bill Fumerola 
<[EMAIL PROTECTED]> wrote:
> On Tue, 12 Oct 1999 [EMAIL PROTECTED] wrote:
> 
>> In <[EMAIL PROTECTED]> [EMAIL PROTECTED] wrote:
>>  Such an errors results from (uncommented) kernel option
>> 
>> #makeoptions CONF_CFLAGS=-fno-builtin
> 
> We have enough breakages with the _documented_ kernel options that we 
> don't need to go hunting down oddities. :>

Does it mean that I throw away my PR with patches to
the 'newpcm' files which add 'abs' definition and therefore
make it possible to make kernel with 

makeoptions CONF_CFLAGS=-fno-builtin   ?

P.S. It seems to me that this option (or its absent) can
severely influence kernel run time efficience (not in the 'abs'
case, of course ;-).

N.Dudorov


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

Re: kernel broken? (pcm)

[Bill Fumerola]

On Tue, 12 Oct 1999 [EMAIL PROTECTED] wrote:

> In <[EMAIL PROTECTED]> [EMAIL PROTECTED] wrote:
>   Such an errors results from (uncommented) kernel option
> 
> #makeoptions  CONF_CFLAGS=-fno-builtin

We have enough breakages with the _documented_ kernel options that we 
don't need to go hunting down oddities. :>

-- 
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED]  -






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

Re: kernel broken? (pcm)

[nnd]

In <[EMAIL PROTECTED]> [EMAIL PROTECTED] wrote:
Such an errors results from (uncommented) kernel option

#makeoptionsCONF_CFLAGS=-fno-builtin

because there is NO 'abs' function/macro in this files
(ac97.c, channel.c and mss.c) and they can be only compiled using
gcc's builtin 'abs'

N.Dudorov

> Hi,
> 
> linking kernel.debug
> ac97.o: In function `ac97_setmixer':
> /usr/src/sys/compile/WORK/../../dev/pcm/ac97.c(.text+0x18d): undefined reference to 
>`abs'
> channel.o: In function `chn_setblocksize':
> /usr/src/sys/compile/WORK/../../dev/pcm/channel.c:712: undefined reference to `abs'
> mss.o: In function `mss_speed':
> /usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c(.text+0x182d): undefined reference 
>to `abs'
> /usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c(.text+0x183f): undefined reference 
>to `abs'
> /usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c(.text+0x1869): undefined reference 
>to `abs'
> mss.o(.text+0x187b):/usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c: more 
>undefined references to `abs' follow
> *** Error code 1
> 1 error
> 
> I tried several cvsups since the morning.
> 
> Kernelconfig attached.
> 


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

RE: World fail + resulting cvsup failures

[Mike Heffner]

On 11-Oct-99 FreeBSD mailing list wrote:
> After an attempt to build world failed early this morning after a 
> cvsup, I can neither resolve the world problem, nor can I cvsup.
> 
> World failure:
> 
> ===> usr.bin/kdump
> cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../..
> -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/kdump/kdump.c
> /bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c
> In file included from :45:
> /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE'
> redefined
> /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the
> location of the previous definition
> cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../..
> -I/usr/obj/usr/src/tmp/usr/include -c ioctl.c
> In file included from ioctl.c:65:
> /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE'
> redefined
> /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the
> location of the previous definition
> ioctl.c: In function `ioctlname':
> ioctl.c:353: sizeof applied to an incomplete type
> ioctl.c:617: sizeof applied to an incomplete type
> *** Error code 1
> 
> Stop in /usr/src/usr.bin/kdump.
> *** Error code 1
> 

i just sent a message to the list about this, "make buildworld dies in
usr.bin/kdump (fix)" here's the patch i included in that message:

--- usr.bin/kdump/mkioctls.old  Mon Oct 11 11:41:27 1999
+++ usr.bin/kdump/mkioctls  Mon Oct 11 10:46:17 1999
@@ -35,6 +35,7 @@
print "#include "
print "#include "
print "#include "
+   print "#include "
print "#include "
print "#include "
print ""


the rest of your problems I don't know anything about ;)

-
Mike Heffner <[EMAIL PROTECTED]>
Fredericksburg, VA
ICQ# 882073
Date: 11-Oct-99   Time: 21:38:32
-


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

[Jason K. Fritcher]

On Mon, 11 Oct 1999, Sean Eric Fagan wrote:
> In article <[EMAIL PROTECTED]> you write:
> Whatever method he is using is not working very well, and it has not worked
> very well for a very long time.

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.

Needless to say, I am happy now that my mail server is on a dedicated link.

Great work Jonathan!

--
 Jason K. Fritcher
  [EMAIL PROTECTED]




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

World fail + resulting cvsup failures

[FreeBSD mailing list]

After an attempt to build world failed early this morning after a 
cvsup, I can neither resolve the world problem, nor can I cvsup.

World failure:

===> usr.bin/kdump
cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../..
-I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/kdump/kdump.c
/bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c
In file included from :45:
/usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE'
redefined
/usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the
location of the previous definition
cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../..
-I/usr/obj/usr/src/tmp/usr/include -c ioctl.c
In file included from ioctl.c:65:
/usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE'
redefined
/usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the
location of the previous definition
ioctl.c: In function `ioctlname':
ioctl.c:353: sizeof applied to an incomplete type
ioctl.c:617: sizeof applied to an incomplete type
*** Error code 1

Stop in /usr/src/usr.bin/kdump.
*** Error code 1


Now, certainly this is unrelated to cvsup failing, however something
else in the build must have caused the following:

mrynet# cvsup


***
*** runtime error:
***Segmentation violation - possible attempt to dereference NIL
***pc = 0x2f
***

Abort trap

A reboot has effected no change in this behavior.

An attempt to reinstall modula from ports results in:

 -- building m3core --

 mkdir FreeBSD2
 --- building in FreeBSD2 ---
 m3 -w1 -why -O -times -a libm3core.a -F/var/tmp/qkAK8630 


 ***
 *** runtime error:
 ***Segmentation violation - possible attempt to dereference NIL
 ***pc = 0x2f
 ***

 Abort trap
 *** error code 134 (ignored)


So, the problem lies in Modula 3.

I'm at a total stalemate now.  Has anyone experienced this?  All 
(constructive :P) suggestions hearily welcomed :D

Cheers,
-skots
--
Scott G. Akmentins-Taylor InterNet: [EMAIL PROTECTED]
MRY Systems [EMAIL PROTECTED]
(Skots Gregorijs Akmentins-Teilors -- just call me "Skots")
- Labak miris neka sarkans -


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

Re: MajorDomo Problems

[Poul-Henning Kamp]

In message <[EMAIL PROTECTED]>, Garrett Wollman writes:
>
>We have appointed jmb as postmaster, and so long as he has that job,
>the list management will be done using whatever mechanisms he deems
>appropriate.

Amen!

--
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: MajorDomo Problems

[Garrett Wollman]

< said:

> majordomo is crap it seems, the freebsd mailing lists should switch
> over to ezmlm-idx/qmail... *THAT* works 100% reliable.

Bull$#!^.  I run a couple of fairly large mailing-lists under
majordomo, and nobody ever gets ``accidentally'' unsubscribed.

On the other hand, quite a few people suddenly start bouncing their
mail and get *intentionally* unsubscribed (by me).

We have appointed jmb as postmaster, and so long as he has that job,
the list management will be done using whatever mechanisms he deems
appropriate.

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED]  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick


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

Re: 3dfx Driver?

[Amancio Hasty]

Don't have much time now days to volunteer due to work overload.
If I get a chance one of these nights I will port it.

My focus is to provide decent X video support appropiate for 
h.261 , h.263 , and mpeg -- which basically entails yuv + scaling
hardware assist. In other words 3dfx is a secondary issue.

Cheers


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

Re: ata changes & ATA_16BIT_ONLY

[Soren Schmidt]

It seems Valentin S. Chopov wrote:
> 
> How the ATA_16BIT_ONLY in ata-disk.c and atapi-all.c
> will be defined - kernel option, autodetection or
> device flag?

For now kernel options, later auto for ISA & 486 arch machines..

-Søren



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

[Jonathan M. Bresler]

> 
> Five years of people finding themselves mysteriously removed from lists, with
> no response other than, "Oh, I just remove people automatically without
> warning if I get too many bounces, and, no, I don't have any bounces from you
> but that must have been what happened."

some people have asked for copies of the bounced email.  at
times i have been able to provide these.  more often i have not been
able to because i delete bounced mail after i process it each day or
couple days.

i try to keep an key out for any bounced mail from
"kithrup.com".  no promises, but i will try.

jmb


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

[Jonathan M. Bresler]

Sean,
you are subscribed in different ways to different lists.  

cvs-all:[EMAIL PROTECTED]
freebsd-alpha:[EMAIL PROTECTED]
freebsd-bugs:[EMAIL PROTECTED]
freebsd-chat:[EMAIL PROTECTED]
freebsd-config:[EMAIL PROTECTED]
freebsd-current:[EMAIL PROTECTED]
freebsd-emulation:[EMAIL PROTECTED]
freebsd-fs:[EMAIL PROTECTED]
freebsd-hackers:[EMAIL PROTECTED]
freebsd-hardware:[EMAIL PROTECTED]
freebsd-mobile:[EMAIL PROTECTED]
freebsd-platforms:[EMAIL PROTECTED]
freebsd-ports:[EMAIL PROTECTED]
freebsd-questions:[EMAIL PROTECTED]
freebsd-security:[EMAIL PROTECTED]
freebsd-smp:[EMAIL PROTECTED]
freebsd-stable:[EMAIL PROTECTED]

i dont see any other "kithrup.com" subscriptions.

jmb


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

[Jonathan M. Bresler]

> 
> I know that this is not the place to hype one's own wares, but if your
> lists have fewer than 200 people, why not just use the free version of
> lyris. One of its many features is sophisticated bounce handling. 
> 

no problem.but the lists have thousands of subscribers

jmb


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

[Joe Abley]

On Mon, Oct 11, 1999 at 12:38:51PM -0700, Sean Eric Fagan wrote:
> >To those who _have_ experienced problems, remember this is a volunteer
> >effort. Would you flame someone on a public list if you found a bug
> >in the code they had contributed?
> 
> If, after *FIVE YEARS* it hadn't been fixed, yes.

No. It's a volunteer project. You don't flame people for bugs; you fix
them, submit polite reports or keep quiet.


Joe


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

Re: 3dfx Driver?

[Jeroen Ruigrok/Asmodai]

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

Re: People getting automatically unsub'ed from -arch

[Sean Eric Fagan]

In article <[EMAIL PROTECTED]> you write:
>You have no way of knowing whether inbound mail to you has bounced, or
>not. Why are you so adamant that mail has not bounced?

Becuse I get lots of email, because I check it constantly, because any of a
half dozen sources for it bouncing would result in my being notified on
another system, because my secondary MX server has better network connectivity
than the freebsd systems, because the only one who has ever made any
accusations about bouncing mail has been jmb and he hasn't been able to
provide any proof?

>To those who _have_ experienced problems, remember this is a volunteer
>effort. Would you flame someone on a public list if you found a bug
>in the code they had contributed?

If, after *FIVE YEARS* it hadn't been fixed, yes.

That's how long this has been going on.

Five years of people finding themselves mysteriously removed from lists, with
no response other than, "Oh, I just remove people automatically without
warning if I get too many bounces, and, no, I don't have any bounces from you
but that must have been what happened."

Except for one time when he admitted that he accidentally removed a bunch of
people when editing a file by hand.

Whatever method he is using is not working very well, and it has not worked
very well for a very long time.



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

kernel broken? (pcm)

[A . Leidinger]

Hi,

linking kernel.debug
ac97.o: In function `ac97_setmixer':
/usr/src/sys/compile/WORK/../../dev/pcm/ac97.c(.text+0x18d): undefined reference to 
`abs'
channel.o: In function `chn_setblocksize':
/usr/src/sys/compile/WORK/../../dev/pcm/channel.c:712: undefined reference to `abs'
mss.o: In function `mss_speed':
/usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c(.text+0x182d): undefined reference 
to `abs'
/usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c(.text+0x183f): undefined reference 
to `abs'
/usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c(.text+0x1869): undefined reference 
to `abs'
mss.o(.text+0x187b):/usr/src/sys/compile/WORK/../../dev/pcm/isa/mss.c: more undefined 
references to `abs' follow
*** Error code 1
1 error

I tried several cvsups since the morning.

Kernelconfig attached.

Bye,
Alexander.

-- 
Am I supposed to be impressed?

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


machine i386
ident   WORK
maxusers32

makeoptions DEBUG=-g
#makeoptionsCONF_CFLAGS=-fno-builtin

#
# Allow user-mode programs to manipulate their local descriptor tables.
# This option is required for the WINE Windows(tm) emulator, and is
# not used by anything else (that we know of).
# 
#optionsUSER_LDT#allow user-level control of i386 ldt

# Options for the VM subsystem
#optionsPQ_NOOPT# No coloring
options PQ_LARGECACHE   # color for 512k/16k cache
#optionsPQ_HUGECACHE# color for 1024k/16k cache

#cpuI586_CPU
cpu I686_CPU# aka Pentium Pro(tm)
options CPU_FASTER_5X86_FPU
options CPU_SUSP_HLT
options "NO_F00F_HACK"

options COMPAT_43

options SYSVSHM
options SYSVSEM
options SYSVMSG
options MD5
options DDB
options GDB_REMOTE_CHAT
options KTRACE  #kernel tracing
#optionsPERFMON
options UCONSOLE
options USERCONFIG  #boot -c editor
options VISUAL_USERCONFIG   #visual boot -c editor
options INET#Internet communications protocols
pseudo-device   ether   #Generic Ethernet
pseudo-device   sppp#Generic Synchronous PPP
pseudo-device   loop#Network loopback device
pseudo-device   bpf #Berkeley packet filter
pseudo-device   disc#Discard device
pseudo-device   streams
options PPP_BSDCOMP #PPP BSD-compress support
options PPP_DEFLATE #PPP zlib/deflate/gzip support
options PPP_FILTER  #enable bpf filtering (needs bpfilter)

options MROUTING# Multicast routing
options IPFIREWALL  #firewall
options IPFIREWALL_VERBOSE  #print information about
# dropped packets
options IPFIREWALL_FORWARD  #enable transparent proxy support
options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity
options IPDIVERT#divert sockets
options IPSTEALTH   #support for stealth forwarding
options TCP_RESTRICT_RST#restrict emission of TCP RST
options ICMP_BANDLIM
options FFS #Fast filesystem
options CD9660  #ISO 9660 filesystem
options KERNFS  #Kernel filesystem
options MSDOSFS #MS DOS File System
options PROCFS  #Process filesystem
options MFS #Memory File System
options NFS #Network File System
#optionsNFS_NOSERVER#Disable the NFS-server code.
options FFS_ROOT#FFS usable as root device
options SOFTUPDATES
options P1003_1B
options _KPOSIX_PRIORITY_SCHEDULING
options _KPOSIX_VERSION=199309L

controller  scbus0  #base SCSI code
#device ch0 #SCSI media changers
device  da0 #SCSI direct access devices (aka disks)
#device sa0 #SCSI tapes
device  cd0 #SCSI CD-ROMs
device  pass0   #CAM passthrough driver
device pt0 at scbus?# SCSI processor type
options CAM_MAX_HIGHPOWER=4
options SCSI_DELAY=5000# Be pessimistic about Joe SCSI device

pseudo-device   pty #Pseudo ttys
pseudo-device   speaker #Play IBM BASIC-style noises out your speaker
pseudo-device   gzip#Exec gzipped a.out's
pseudo-device   vn  #Vnode driver (turns a file into a device)
#pseudo-device  snp 3   #Snoop device - to look at pty/vty/etc..

options MSGBUF_SIZE=40960

controller  isa0

# Enable support for the kernel PLL to use an external PPS signal,
# under supervision of [x]ntpd(8)
# More 

Re: People getting automatically unsub'ed from -arch

[Joe Abley]

On Mon, Oct 11, 1999 at 11:21:52AM -0700, Sean Eric Fagan wrote:
> In article <[EMAIL PROTECTED]> you 
>write:
> > 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.
> 
> My mail _has not bounced_.  And yet I have been removed.

You have no way of knowing whether inbound mail to you has bounced, or
not. Why are you so adamant that mail has not bounced?

This discussion is a little one-sided, and is getting personal for some
reason. Jmb: on behalf of the many people who have _not_ experienced
problems (and those who have, but are not blaming you for them), thanks
for your efforts.

To those who _have_ experienced problems, remember this is a volunteer
effort. Would you flame someone on a public list if you found a bug
in the code they had contributed?


Joe


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

[Kip Macy]

I know that this is not the place to hype one's own wares, but if your
lists have fewer than 200 people, why not just use the free version of
lyris. One of its many features is sophisticated bounce handling. 


-Kip

On Mon, 11 Oct 1999, Sean Eric Fagan wrote:

> In article <[EMAIL PROTECTED]> you 
>write:
> > 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.
> 
> My mail _has not bounced_.  And yet I have been removed.
> 
> > several people with recurring email delivery problems have
> >written a script to monitor their subscriptions for them.
> 
> Goody for them.  Since I do not have recurring email delivery problems, there
> is no reason why I should go out of my way.
> 
> And, interestingly enough, I'm not the only person this has happened to, and
> all you can do is blame every single one of them for having "recurring email
> delivery problems."
> 
> When are you going to realize there is a problem and admit it?  When are you
> going to get it _fixed_?
> 
> Or is your life easier if there is nobody on any of the lists?
> 
> 
> 
> 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

[Sean Eric Fagan]

In article <[EMAIL PROTECTED]> you 
write:
>   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.

My mail _has not bounced_.  And yet I have been removed.

>   several people with recurring email delivery problems have
>written a script to monitor their subscriptions for them.  

Goody for them.  Since I do not have recurring email delivery problems, there
is no reason why I should go out of my way.

And, interestingly enough, I'm not the only person this has happened to, and
all you can do is blame every single one of them for having "recurring email
delivery problems."

When are you going to realize there is a problem and admit it?  When are you
going to get it _fixed_?

Or is your life easier if there is nobody on any of the lists?



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

[Jonathan M. Bresler]

> 
> > > 
> > > "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.
> 
> a)  I don't think message count should be considered at all, as the this
> is highly dependent on the list one is on, and the current rate of
> messages going to it.  As Nate pointed out 30 messages could be as
> short as 5 minutes on -hackers.  And in my hay day of being on all
> lists it would have defanitly been in the 5 minute range almost any
> time of the day.


i said "approximately" because i do take into account the
number of lists subscribe and the nature of the lists.  an it gives me
some wiggle room.  


> 
> b)  The 24 hour time period is a bit on the short time, unless the messages
> are bouncing for being in the queue for at least 48 hours.  Many mail
> configuration screw ups happen on a friday night, and may not get
> noticed until monday morning.  Thus a 72 hour window is more reasonable
> for that type of mail problem.

a message may remain in the queue for daysthese are not
bounces...these are queued emails.  i dont count queued emails, but if
i can reach your mail server and it give me back a series 500, thats a
bounce.  YOU, or your isp, controls this.   so if our config if
f*cked, go off the air (not a bounce..at least for several days) and
fix it.  dont leave a f*cked up mail server on the net while that
server gives out series 500 responses.  avoid 500 series unless you
mean ;)   a 500 series means "go away, and dont come back!"

5yz   Permanent Negative Completion reply

   The command was not accepted and the requested action did
   not occur.  The sender-SMTP is discouraged from repeating
   the exact request (in the same sequence).  Even some
   "permanent" error conditions can be corrected, so the
   human user may want to direct the sender-SMTP to
   reinitiate the command sequence by direct action at some
   point in the future (e.g., after the spelling has been
   changed, or the user has altered the account status).



> 
> > 
> > i do NOT send the person mail to inform them that the are
> > being removed from the mailing lists, because their email is bouncing.
> 
> :-).  Though I understand your reasoning, it really depends on for what
> reason they are bouncing.  If it is queue time outs sending a message
> may just get to them, if they happen to get it fixed before the notice
> gets timed out and bounced.  Infact that would be a really good threshold
> for removal due to mail bouncing due to queue timeout.  In the case of
> immediate bounce due to mis configuration your current policy is probably
> the best policy.
> 
> -- 
> Rod Grimes - KD7CAX - (RWG25)[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

[Jonathan M. Bresler]

> Reply-To: [EMAIL PROTECTED] (Nate Williams)
> 
> > > "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.
> 
> How long do you wait to determine 'bounced' email?  I've bounced mail to
> hotmail recently, and it wasn't hotmail accounts problem.  (No comments
> from the peanut gallery, it's an easy way for our folks on the road to
> get email simply.. :)

when the MTA gives up trying to deliver the mail, i call it
bounced.  so a 500 series error from the other MTA means the email has
bounced.  

> 
> > the threshhold is approximately 30 messages in a
> > 24 hour period. 
> 
> Or 5 minutes worth of emai on -hackers. :)
> 
> > 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.
> 
> How do you cause 'vacation' to not send messages to the list?  Doesn't
> the stock 'vacation' program as shipped in FreeBSD send them to the
> list?

dont know.if i see them, i unsubscribe the person.

[snip][

> Some of the people (who apparently have problems) didn't even know they
> had problems
> 
> Even so, do you have a copy of said scripts?  Given that -arch and
> -security are not allowed to use the 'which' command, do they simply
> re-subscribe themselves on a weekly basis 'just in case'?

no i dontpeople have said that they use thembut its
like my baseball coach said to me when i asked if i could steal second
base: "okay, but dont get caught!"

> 
> Inquiring minds would like to know...
> 
> Even a simple way of finding out (obviously not via email) *IF* I had
> been subscribed would be great.  A 'unsubscribed' mailing list that I
> could run 'which' on that would tell me which lists I'm no longer on,
> however I can imagine that would be a lot of work.

tried thatin majordomo its called the bounces list.
remove people from teh regular list and subscribe them to bounces,
then they get a note every week telling them about it.no one every
unsubscribed from bounces and ressubscribed to teh regular list.  i
ended up having to explain it to people.  excessive overhead.

jmb


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

[Rodney W. Grimes]

> > 
> > "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.

a)  I don't think message count should be considered at all, as the this
is highly dependent on the list one is on, and the current rate of
messages going to it.  As Nate pointed out 30 messages could be as
short as 5 minutes on -hackers.  And in my hay day of being on all
lists it would have defanitly been in the 5 minute range almost any
time of the day.

b)  The 24 hour time period is a bit on the short time, unless the messages
are bouncing for being in the queue for at least 48 hours.  Many mail
configuration screw ups happen on a friday night, and may not get
noticed until monday morning.  Thus a 72 hour window is more reasonable
for that type of mail problem.

> 
>   i do NOT send the person mail to inform them that the are
> being removed from the mailing lists, because their email is bouncing.

:-).  Though I understand your reasoning, it really depends on for what
reason they are bouncing.  If it is queue time outs sending a message
may just get to them, if they happen to get it fixed before the notice
gets timed out and bounced.  Infact that would be a really good threshold
for removal due to mail bouncing due to queue timeout.  In the case of
immediate bounce due to mis configuration your current policy is probably
the best policy.

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


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

ata changes & ATA_16BIT_ONLY

[Valentin S. Chopov]

How the ATA_16BIT_ONLY in ata-disk.c and atapi-all.c
will be defined - kernel option, autodetection or
device flag?

Thanks,

Val
__
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com


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

make buildworld dies in usr.bin/kdump (fix)

[Mike Heffner]

A cvsup last night (Oct 10) of current dies when I do a make buildworld. It was
dying in usr.bin/kdump with the error "sizeof of incomplete type" or something
like that. It seems there was a header file missing, here's a patch which fixes
it:

--- usr.bin/kdump/mkioctls.old  Mon Oct 11 11:41:27 1999
+++ usr.bin/kdump/mkioctls  Mon Oct 11 10:46:17 1999
@@ -35,6 +35,7 @@
print "#include "
print "#include "
print "#include "
+   print "#include "
print "#include "
print "#include "
print ""


-
Mike Heffner <[EMAIL PROTECTED]>
Fredericksburg, VA
ICQ# 882073
Date: 11-Oct-99   Time: 11:42:43
-


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

[Nate Williams]

> > "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.

How long do you wait to determine 'bounced' email?  I've bounced mail to
hotmail recently, and it wasn't hotmail accounts problem.  (No comments
from the peanut gallery, it's an easy way for our folks on the road to
get email simply.. :)

> the threshhold is approximately 30 messages in a
> 24 hour period. 

Or 5 minutes worth of emai on -hackers. :)

> 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.

How do you cause 'vacation' to not send messages to the list?  Doesn't
the stock 'vacation' program as shipped in FreeBSD send them to the
list?

>   i do NOT send the person mail to inform them that the are
> being removed from the mailing lists, because their email is bouncing.

Sometimes.:)

> > I have a hard enough time remembering which lists I subscribed to that I do
> > get traffic on to check every day to see which ones have removed me without
> > informing me.
> 
>   several people with recurring email delivery problems have
> written a script to monitor their subscriptions for them. 

Some of the people (who apparently have problems) didn't even know they
had problems

Even so, do you have a copy of said scripts?  Given that -arch and
-security are not allowed to use the 'which' command, do they simply
re-subscribe themselves on a weekly basis 'just in case'?

Inquiring minds would like to know...

Even a simple way of finding out (obviously not via email) *IF* I had
been subscribed would be great.  A 'unsubscribed' mailing list that I
could run 'which' on that would tell me which lists I'm no longer on,
however I can imagine that would be a lot of work.




Nate


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

Re: MajorDomo Problems

[Robert Watson]

Love to know why my freebsd-arch subscription disappeared, although the
rest appeared to stick around.  I just resubscribed, but was subscribed
before (but not sure about until when) as

  [EMAIL PROTECTED]

What is strange is that if that was bouncing, I would have expected, say,
my -current subscription to bounce just as much and be unsubscribed. 

>From the files in the directory, maybe it is the case that a reboot/crash
hit hub as a subscription request was being processed?  (does it rewrite
the file in place, or does it copy the file out with changes, then do a
double rename to put it back in place over the old version?)

Robert

On Mon, 11 Oct 1999, Jonathan M. Bresler wrote:

> 
> yesyou or your provider was bouncing your email.
> 
> i unsubscribed you on Oct 07 05:40:22.
> 
> jmb
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 


  Robert N M Watson 

[EMAIL PROTECTED]  http://www.watson.org/~robert/
PGP key fingerprint: AF B5 5F FF A6 4A 79 37  ED 5F 55 E9 58 04 6A B1
TIS Labs at Network Associates, Safeport Network Services



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

Re: staroffice51 An unrecoverable error has occurred

[Edwin Culp]

Edwin Culp wrote:

> Sean O'Connell wrote:
>
> > On 1999 Oct 11, Edwin Culp (aka [EMAIL PROTECTED]) wrote:
> > > I didn't install it there, to begin with;-)  Still, I can't seem to find the
> > > problem.
> >
> > Ed-
> >
> > I saw this problem with a user on a laptop running 3.2+PAO.  It
> > seems to mostly work under 3.3+PAO (other than the "unable to start
> > plugin manager ... I thought I had that fixed, but now it doesn't
> > work anymore ... sigh).
> >
> > I do my installs in /usr/local/Office51 with a net setup and then
> > have the users do a workstation setup.  StarOffice5.0 worked fine
> > for me.
>
> I've installed in /var/Office51, but I don't think that should make a
> difference.  I'm running current on an ams laptop, that could make a
> difference:-)  I really don't have any problems with it.  I'm going to play with
> setup and see if that changes anything.
>

Sean,

I can't really find that setup has any interesting options:-(  I have played with
ldconfig and LD_LIBRARY_PATH, even PATH with no avail.  I'm getting this in my
/var/log/messages.

Oct 11 07:42:42 local-27 /kernel: pid 28851 (soffice.bin), uid 0: exited on signal
6 (core dumped)
Oct 11 07:46:07 local-27 /kernel: pid 28874 (soffice.bin), uid 0: exited on signal
6 (core dumped)

I'm going to keep looking.

Thanks,

ed



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

Re: staroffice51 An unrecoverable error has occurred

[Edwin Culp]

Johan Karlsson wrote:

> At Sun, 10 Oct 1999 23:40:04 PDT, Edwin Culp wrote:
> >I just installed it out of curiosity.  Everything went well until I try to exe
> >cute
> >it.  It starts as if it were going to work and then it gives me a core dump wi
> >th a
> >message box that says, "An unrecoverable error has occurred.  All modified fil
> >es
> >have been saved and probably can be recovered at reset" .  My Linux emulation
> >is
> >working fine.  I am using linux netscape 4.7 with glibc and many linux plugins
> > with
> >no problems.
> >
> >Anyone else seeing that.
> >
>
> This happend to me, removing the dir Office51 in my home directory solved it.

I didn't install it there, to begin with;-)  Still, I can't seem to find the
problem.

Thanks,

ed



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

Re: MajorDomo Problems

[Jonathan M. Bresler]

yesyou or your provider was bouncing your email.

i unsubscribed you on Oct 07 05:40:22.

jmb


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

[Jonathan M. Bresler]

> 
> "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.

i do NOT send the person mail to inform them that the are
being removed from the mailing lists, because their email is bouncing.

> 
> I have a hard enough time remembering which lists I subscribed to that I do
> get traffic on to check every day to see which ones have removed me without
> informing me.

several people with recurring email delivery problems have
written a script to monitor their subscriptions for them.   

jmb


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

Re: Abit's BP6 and 'lmmon' or 'chm'

[sthaug]

> > Does anybody successfully use ports/sysutils/{lmmon|chm}
> > with the Abit's BP6 motherboard ?
> 
> > II only receive:
> > IOCTL: device not configured
> > from lmmon and chm.
> 
> I have the same problem with the 'wmhm' port. I also have Abit BP6 with two
> 450 Mhz Celerons. 

Ditto. BP6 with 2xCeleron 366, no overclocking. FreeBSD-current as of
a couple of days ago.

Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]


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

Re: Abit's BP6 and 'lmmon' or 'chm'

[Chris D. Faulhaber]

On Mon, 11 Oct 1999, Nickolay Dudorov wrote:

>   Does anybody successfully use ports/sysutils/{lmmon|chm}
> with the Abit's BP6 motherboard ?
> 
>   After 'make install'-ing ports and adding
> 
> controller smbus0
> controller iicbus0
> controller iicbb0
> controller intpm0
> device smb0 at smbus?
> 
> to kernel config file (and config, make depend, make, make install,
> reboot the new kernel) I only receive:
> 
> IOCTL: device not configured
> 
> from lmmon and chm.
> 

This is due to the intpm controller not configuring the motherboards PM
controller, not because the software.

I emailed Takanori Watanabe a while back concerning this MB.  His thoughts
were that: 1) He hadn't heard of the driver working in an SMP environment;
2) It may be due to the controller using an unconfigured ISA interface.

Anyone else wish to comment?

-
Chris D. Faulhaber <[EMAIL PROTECTED]>  |  All the true gurus I've met never
System/Network Administrator,|  claimed they were one, and always
Reality Check Information, Inc.  |  pointed to someone better.




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

Re: Abit's BP6 and 'lmmon' or 'chm'

[Dave J. Boers]

On Mon, Oct 11, 1999 at 06:44:50PM +0700, Nickolay Dudorov wrote:
>   Does anybody successfully use ports/sysutils/{lmmon|chm}
> with the Abit's BP6 motherboard ?

> II only receive:
> IOCTL: device not configured
> from lmmon and chm.

I have the same problem with the 'wmhm' port. I also have Abit BP6 with two
450 Mhz Celerons. 

Dave. 

-- 

  Dave J. Boers
  [EMAIL PROTECTED]  I will *NOT* read email sent to 
  Graduate student of Theoretical Physics   [EMAIL PROTECTED]
  -> FreeBSD: The Power to Serve .http://www.freebsd.org 


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

Abit's BP6 and 'lmmon' or 'chm'

[Nickolay Dudorov]

Does anybody successfully use ports/sysutils/{lmmon|chm}
with the Abit's BP6 motherboard ?

After 'make install'-ing ports and adding

controller smbus0
controller iicbus0
controller iicbb0
controller intpm0
device smb0 at smbus?

to kernel config file (and config, make depend, make, make install,
reboot the new kernel) I only receive:

IOCTL: device not configured

from lmmon and chm.

N.Dudorov


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

Re: ATA related panic

[Soren Schmidt]

It seems Maxim Sobolev wrote:
[Charset koi8-r unsupported, filtering to ASCII...]
> Soren Schmidt wrote:
> 
> > It seems Maxim Sobolev wrote:
> > > It seems that ATA is broken - it paniced when kernel is booting. Following is
> > > diagnostic output:
> > > Fatal trap 12: page fault while in kernel mode
> > > fault virtual address= 0xc
> > > fault code  = supervisor read, page not present
> > > instruction pointer  = 0x8:0xc01ca927
> > Oops, try this patch:
> 
> Yes, it works!

Roger, I'll commit it right away...

-Soren


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

Re: ATA related panic

[Maxim Sobolev]

Soren Schmidt wrote:

> It seems Maxim Sobolev wrote:
> > It seems that ATA is broken - it paniced when kernel is booting. Following is
> > diagnostic output:
> > Fatal trap 12: page fault while in kernel mode
> > fault virtual address= 0xc
> > fault code  = supervisor read, page not present
> > instruction pointer  = 0x8:0xc01ca927
> Oops, try this patch:

Yes, it works!

-Maxim




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

Re: ATA related panic

[Soren Schmidt]

It seems Maxim Sobolev wrote:
> It seems that ATA is broken - it paniced when kernel is booting. Following is
> diagnostic output:
> 
> isa0:  on motherboard
> pccard0:  on motherboard
> 
> Fatal trap 12: page fault while in kernel mode
> fault virtual address= 0xc
> fault code  = supervisor read, page not present
> instruction pointer  = 0x8:0xc01ca927
> stack pointer  = 0x10:0xc032fe14
> frame pointer  = 0x10:0xc032fe28
> code segment = base 0x0, limit 0xf, type 0x1b
>   = DPL 0, pres 1, def32 1, gran 1
> processor eflags  = interrupt enabled, resume, IOPL = 0
> current process   = 0 (swapper)
> interrupt mask= net tty bio cam
> trap number= 12
> panic: page fault

Oops, try this patch:

Index: ata-all.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v
retrieving revision 1.25
diff -u -r1.25 ata-all.c
--- ata-all.c   1999/10/10 18:08:36 1.25
+++ ata-all.c   1999/10/11 10:42:36
@@ -115,7 +115,7 @@
 
 /* check if allready in use by a PCI device */
 for (ctlr = 0; ctlr < atanlun; ctlr++) {
-   if (atadevices[ctlr]->ioaddr == rman_get_start(port)) {
+   if (atadevices[ctlr] && atadevices[ctlr]->ioaddr==rman_get_start(port)){
printf("ata-isa%d: already registered as ata%d\n", 
   device_get_unit(dev), ctlr);
bus_release_resource(dev, SYS_RES_IOPORT, 0, port);

-Soren


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

ATA related panic

[Maxim Sobolev]

It seems that ATA is broken - it paniced when kernel is booting. Following is
diagnostic output:

isa0:  on motherboard
pccard0:  on motherboard

Fatal trap 12: page fault while in kernel mode
fault virtual address= 0xc
fault code  = supervisor read, page not present
instruction pointer  = 0x8:0xc01ca927
stack pointer  = 0x10:0xc032fe14
frame pointer  = 0x10:0xc032fe28
code segment = base 0x0, limit 0xf, type 0x1b
  = DPL 0, pres 1, def32 1, gran 1
processor eflags  = interrupt enabled, resume, IOPL = 0
current process   = 0 (swapper)
interrupt mask= net tty bio cam
trap number= 12
panic: page fault

First I think that this is pccard breakage, but look into "nm /kernel" gave me
following symbols around 0xc01ca927:

c01ca8b4 t ata_isaprobe
c01ca8b4 t gcc2_compiled.
c01ca9c0 t ata_isaattach
c01caa58 t ata_pcimatch
c01cabe0 t ata_pciprobe
c01cac0c t ata_pciattach
c01cb0a0 t ata_probe
c01cb3a0 t ataintr
c01cb42c T ata_start
c01cb570 T ata_reset
c01cb6b0 T ata_reinit
c01cb79c T ata_wait

So, I've recommpiled my kernel with wd0 instead and its working now.

-Maxim



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

Re: MajorDomo Problems

[Andre Oppermann]

Brad Knowles wrote:
> 
> At 11:01 AM +0200 1999/10/11, Andre Oppermann wrote:
> 
> > majordomo is crap it seems, the freebsd mailing lists should switch
> > over to ezmlm-idx/qmail... *THAT* works 100% reliable.
> 
> I think we can separate MLA issues from MTA issues.  Myself, I've
> had no problems with Majordomo on the various lists I manage, but I
> confess that on the larger mailing lists I prefer to use tools more
> suited for the jobs (such as Listserv).  MLA issues I would be
> willing to discuss relatively dispassionately.

Well, ezmlm works only with qmail because of it's superior VERP
bounce system... otherwise I don't care as long as it is not sendmail.

> However, if you're going to get into MTA religious discussions, I
> would suggest that people take a long hard look at Postfix instead.

And at qmail. But yes, that doesn't belong here.

> Of course, none of these sorts of discussions are really relevant
> to -current, or for that matter, relevant to any other
> FreeBSD-related mailing list of which I am aware.

-- 
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: MajorDomo Problems

[Brad Knowles]

At 11:01 AM +0200 1999/10/11, Andre Oppermann wrote:

> majordomo is crap it seems, the freebsd mailing lists should switch
> over to ezmlm-idx/qmail... *THAT* works 100% reliable.

I think we can separate MLA issues from MTA issues.  Myself, I've 
had no problems with Majordomo on the various lists I manage, but I 
confess that on the larger mailing lists I prefer to use tools more 
suited for the jobs (such as Listserv).  MLA issues I would be 
willing to discuss relatively dispassionately.

However, if you're going to get into MTA religious discussions, I 
would suggest that people take a long hard look at Postfix instead.


Of course, none of these sorts of discussions are really relevant 
to -current, or for that matter, relevant to any other 
FreeBSD-related mailing list of which I am aware.

-- 
   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: MajorDomo Problems

[Andre Oppermann]

Alex wrote:
> 
> Tom Embt wrote:
> >
> > I've been mysteriously unsubscribed from -questions sometime between Oct
> > 7th and Oct 10th.  My guess puts it at late morning/early afternoon EDT on
> > the 7th.
> >
> > It would seem something is up...  good thing somebody mentioned the 'which'
> > command (I'd never heard of it), I was wondering why noone was responding
> > to an earlier post ;)
> 
> Hey - I was unsubscribed from -cvs-all, -advocacy, -emulation, -hackers,
> -mobile, -multimedia, -new-bus, -announce and -stable!  In other words,
> ALL mailing lists I was subscribed to except -current.
> 
> This happened twice!  The first time was a couple of weeks ago - I just
> ignored it and resubscribed - but having to do it again is just too
> much!  Please do something about it, sort it out!  It really sucks
> having to acknowledge every subscribe request and then receive a whole
> bunch of confirmation messages.

majordomo is crap it seems, the freebsd mailing lists should switch
over to ezmlm-idx/qmail... *THAT* works 100% reliable.

-- 
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: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org

[Matthew N. Dodd]

On Mon, 11 Oct 1999, Doug Rabson wrote:
> I was looking at the Linux driver and I don't think it would be hard to
> use their algorithm to set the memory resource appropriately. 

Looks pretty simple.

I'll take a crack at it tomorrow.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



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

[Doug Rabson]

On Sun, 10 Oct 1999, Matthew N. Dodd wrote:

> On Sun, 10 Oct 1999, Matthew N. Dodd wrote:
> > On Sun, 10 Oct 1999, Doug Rabson wrote:
> > > Your card is an SMC EtherEZ (8416). I think that needs some special
> > > extra tricks to get it supported. Matt Dodd <[EMAIL PROTECTED]> was
> > > working on this recently but I don't know if he has it working yet.
> > 
> > I've got uncommitted patches that fix this I believe.  I need to go back
> > and test them before I commit but they should work.
> 
> Ok, I've tested my patches and remembered why I didn't ever do anything
> with them.
> 
> *** ISA_GET_RESOURCE(,,SYS_RES_MEMORY,...) failed (2)
> unknown0:  at port 0x240-0x25f irq 9 on isa0
> 
> ed_probe_WD80x3() doesn't understand boards that have no shared memory.
> 
> While these cards work just fine in softset mode, turning on their PnP
> features seems to disable the use of shared memory.

I was looking at the Linux driver and I don't think it would be hard to
use their algorithm to set the memory resource appropriately. 

--
Doug Rabson Mail:  [EMAIL PROTECTED]
Nonlinear Systems Ltd.  Phone: +44 181 442 9037




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

3dfx Driver?

[Amancio Hasty]

Has anyone ported the linux 3DFx Driver to FreeBSD?

Tnks!
-- 

 Amancio Hasty
 [EMAIL PROTECTED]




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

People getting automatically unsub'ed from -arch

[Brian Somers]

> > I Can't believe this email only produced TWO responses!
> > I would have thought that this wouldhav brought out the chainsaws!
> > Maybe no-one is listenning on 'arch' any more, or maybe 'arch' doesn't
> > work? (the only responders got it via 'core')
> 
> Interesting.  It appears that somehow I got 'unsubscribed' from arch.
> Not sure why, but in May I was subscribed, but I'm no longer subscribed.
> 
> Did everyone get unsubscribed when it went idle?

I believe I did more than once.  I've re-subscribed several times and 
got a ``you'll have to be approved manually'' message back.  When I 
tried again a few days ago, it seemed to stick.

Like you, I was subscribed at one point

> Nate

-- 
Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]>
     <[EMAIL PROTECTED]>
Don't _EVER_ lose your sense of humour !  <[EMAIL PROTECTED]>




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