Re: Why does fsck try to fsck a CDROM?

2001-06-07 Thread David O'Brien -Hackers
On Thu, Jun 07, 2001 at 03:32:19PM -0700, Dave Hayes wrote: > Alfred Perlstein <[EMAIL PROTECTED]> writes: > > The sixth field, (fs_passno), is used by the fsck(8) program to > > determine the order in which filesystem checks are done at > > reboot time. > > Yep, good that you ask

Re: free() and const warnings

2001-06-07 Thread Warner Losh
In message <[EMAIL PROTECTED]> John Baldwin writes: : Of course, this begs the question of why you are free'ing a const. :) Sometimes that's the only handle that you have on the object :-). I sometimes think that changing free to be const void * is the right answer, but that has its own set prob

Re: Why does fsck try to fsck a CDROM?

2001-06-07 Thread Dave Hayes
David O'Brien -Hackers <[EMAIL PROTECTED]> writes: > You mentioned though that your CDROM is /. How about posting the real > /etc/fstab from your root partition for us to have a look at? There is none. No default fstab exists. -- Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED

Re: newbussifying drivers

2001-06-07 Thread j mckitrick
| > > : How would you recommending fixing this, taken from the ex driver? | > > | > > By deleting it. | > | > Uh, what? | > | > Non PnP devices that can be autodetected should be autodetected. | > | > Relying on the user to wire down hints is silly. | | Probably they should provide an identify m

Re: newbussifying drivers

2001-06-07 Thread Warner Losh
In message <[EMAIL PROTECTED]> j mckitrick writes: : Okay, there is something i'm not understanding here. In the ed driver, : there are many possible cards, which each have different i/o ports, correct? Not really. The ed driver is the most twisted driver in the tree when it comes to probe. :

Re: Why does fsck try to fsck a CDROM?

2001-06-07 Thread Alfred Perlstein
* Dave Hayes <[EMAIL PROTECTED]> [010607 18:02] wrote: > If I boot from a CDROM (of my own creation admittedly), fsck -p > wants to fsck the CD partition, /dev/ad0c. It is mounted as root. from fstab(5): The sixth field, (fs_passno), is used by the fsck(8) program to determine the orde

Re: cloning network interfaces

2001-06-07 Thread Brooks Davis
On Thu, Jun 07, 2001 at 12:19:53PM +0100, Brian Somers wrote: > > The quick and dirty way: > > > > Make a clone handler despite the fact that there is no /dev > > entry needed. You don't actually have to create a dev entry > > in the clone handler, you could just create the gif_inter

Why does fsck try to fsck a CDROM?

2001-06-07 Thread Dave Hayes
If I boot from a CDROM (of my own creation admittedly), fsck -p wants to fsck the CD partition, /dev/ad0c. It is mounted as root. I look at the source and in preen.c I'm not able to see any way for fsck to do that. Granted I've never looked at fsck source before (I looked in /usr/src/sbin/fsck fo

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Matt Dillon
: :On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote: :> :> : :> :Thanks, I will try setting errno, but I don't think it is signals. :> :I have been running truss on the process. The relevant part is :> : :> :gettimeofday(0xbfbffa54,0x0) = 0 (0x0) :> :select(0x50,0x

Re: libc_r, signal handler ucontext modification

2001-06-07 Thread Daniel Eischen
On Thu, 7 Jun 2001, Stefan Hoffmeister wrote: > : On Thu, 7 Jun 2001 12:07:50 -0400 (EDT), Daniel Eischen wrote: > > >On Thu, 7 Jun 2001, Stefan Hoffmeister wrote: > > >> [copy context back into thread] > > >You can't do that. There is no requirement that the interrupted thread > >is the one t

Re: Why does fsck try to fsck a CDROM?

2001-06-07 Thread Dave Hayes
Alfred Perlstein <[EMAIL PROTECTED]> writes: > The sixth field, (fs_passno), is used by the fsck(8) program to > determine the order in which filesystem checks are done at > reboot time. Yep, good that you asked this, but not the problem. I not only set this field to zero *I delet

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Graham Barr
While this does sound very plausable,... The server does not do any writes, data only travels from the clients to the server. The clients and the server are connected to the same switch. The other server which is similar is on the same network and is connected to by the same machines as clients

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Ian Dowse
In message <[EMAIL PROTECTED]>, Graham Barr writes: >Also why does this happen only every few hours ? There is a lot of >data going through these connections maybe the timer for SO_RCVTIMEO >is not being reset. > >But then we have another server, with a similar number of clients and >data through

Re: FreeBSD

2001-06-07 Thread Chris Costello
On Thursday, June 07, 2001, tywain.griffen wrote: > To whom this concern, > Please send me a FreeBSD. My address is: > > > 110 Juniper Dr. > Ozark, Al 36360 If anything, this should've gone to [EMAIL PROTECTED], but it really doesn't belong there, either.

Re: FreeBSD

2001-06-07 Thread Steve B.
Below is the URL on where you can download FreeBSD.    http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/mirrors-ftp.html   IF you want it on CD-ROM below is the URL to places that sell it.   http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/mirrors.html   All this info and

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Graham Barr
On Thu, Jun 07, 2001 at 03:09:17PM -0400, Alfred Perlstein wrote: > * Graham Barr <[EMAIL PROTECTED]> [010607 12:17] wrote: > > Since people seem to be helping you in other ways, I'll just > answer this one: > > > So, here is my question. Does anyone know under what circumstance > > ETIMEDOUT ma

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Alfred Perlstein
* Graham Barr <[EMAIL PROTECTED]> [010607 12:17] wrote: Since people seem to be helping you in other ways, I'll just answer this one: > So, here is my question. Does anyone know under what circumstance > ETIMEDOUT may be returned from read(2) or is this a potential bug > somewhere ? I'm quite s

Re: read(2) and ETIMEDOUT

2001-06-07 Thread rick norman
I've seen this behavior in the past. My impression is that it is load related. If you do a grep on ETIMEDOUT in /usr/src/sys/netinet, you will see where the tcp stack may return this message. There may be some sysctl params relating to timers that you can muck with. Rick Graham Barr wrote: >

FreeBSD

2001-06-07 Thread tywain.griffen
To whom this concern,   Please send me a FreeBSD. My address is:     110 Juniper Dr.  Ozark, Al 36360   Tywain Griffen

Re: free() and const warnings

2001-06-07 Thread Jacques A. Vidrine
On Thu, Jun 07, 2001 at 10:20:51AM -0700, John Baldwin wrote: > > On 07-Jun-01 Peter Pentchev wrote: > > On Thu, Jun 07, 2001 at 07:07:22PM +0300, Peter Pentchev wrote: > >> Hi, > >> > >> Is free((void *) (size_t) ptr) the only way to free a const whatever *ptr > >> with WARNS=2? (or more speci

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Graham Barr
On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote: > > : > :Thanks, I will try setting errno, but I don't think it is signals. > :I have been running truss on the process. The relevant part is > : > :gettimeofday(0xbfbffa54,0x0) = 0 (0x0) > :select(0x50,0x93f8c90,0x0

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Matt Dillon
: :Thanks, I will try setting errno, but I don't think it is signals. :I have been running truss on the process. The relevant part is : :gettimeofday(0xbfbffa54,0x0) = 0 (0x0) :select(0x50,0x93f8c90,0x0,0x0,0xbfbffa74)= 3 (0x3) :read(0x16,0xa2da000,0x8000)

Re: free() and const warnings

2001-06-07 Thread John Baldwin
On 07-Jun-01 Peter Pentchev wrote: > On Thu, Jun 07, 2001 at 07:07:22PM +0300, Peter Pentchev wrote: >> Hi, >> >> Is free((void *) (size_t) ptr) the only way to free a const whatever *ptr >> with WARNS=2? (or more specifically, with -Wcast-qual) > > Uhm. OK. So size_t may not be enough to ho

Re: libc_r, signal handler ucontext modification

2001-06-07 Thread Stefan Hoffmeister
: On Thu, 7 Jun 2001 12:07:50 -0400 (EDT), Daniel Eischen wrote: >On Thu, 7 Jun 2001, Stefan Hoffmeister wrote: >> [copy context back into thread] >You can't do that. There is no requirement that the interrupted thread >is the one that handles the signal. If you copy the context back to >the

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Graham Barr
Thanks, I will try setting errno, but I don't think it is signals. I have been running truss on the process. The relevant part is gettimeofday(0xbfbffa54,0x0) = 0 (0x0) select(0x50,0x93f8c90,0x0,0x0,0xbfbffa74)= 3 (0x3) read(0x16,0xa2da000,0x8000)

Re: free() and const warnings

2001-06-07 Thread Peter Pentchev
On Thu, Jun 07, 2001 at 07:07:22PM +0300, Peter Pentchev wrote: > Hi, > > Is free((void *) (size_t) ptr) the only way to free a const whatever *ptr > with WARNS=2? (or more specifically, with -Wcast-qual) Uhm. OK. So size_t may not be enough to hold a pointer. What is it then - caddr_t? G'l

Re: read(2) and ETIMEDOUT

2001-06-07 Thread Matt Dillon
:A while ago our systems were upgraded from 4.2 to 4.3-RC, and at :this time we started seeing problems that I am having a difficult :time tracking down. : :We have a server process which is connected to by many other :machines, each of them streams data in via tcp/ip. These connections :are prett

read(2) and ETIMEDOUT

2001-06-07 Thread Graham Barr
A while ago our systems were upgraded from 4.2 to 4.3-RC, and at this time we started seeing problems that I am having a difficult time tracking down. We have a server process which is connected to by many other machines, each of them streams data in via tcp/ip. These connections are pretty much

Re: libc_r, signal handler ucontext modification

2001-06-07 Thread Daniel Eischen
On Thu, 7 Jun 2001, Stefan Hoffmeister wrote: > : On Thu, 07 Jun 2001 15:21:31 +0200, Stefan Hoffmeister wrote: > > >I admit that all this is somewhat anecdotal, but I haven't looked in > >detail yet at what happens after the signal handler has returned to > > > > uthread/uthread_sig.c -> _threa

free() and const warnings

2001-06-07 Thread Peter Pentchev
Hi, Is free((void *) (size_t) ptr) the only way to free a const whatever *ptr with WARNS=2? (or more specifically, with -Wcast-qual) G'luck, Peter -- I've heard that this sentence is a rumor. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the

Re: How to disable software TCP checksumming?

2001-06-07 Thread Bsdguru
This thread is baffling. The bottom line is that you cant trust data coming into your machine, and you have to checksum it. The link level check only verifies that what was sent by the last forwarding point is the same as what you got, but in NO WAY implies that all of the data is valid. A li

Re: XFree86 4.1.0 and i810

2001-06-07 Thread Andrew Hesford
On Thu, Jun 07, 2001 at 07:15:00AM -0700, Jean-Marc Zucconi wrote: > I will commit it. Please send it to [EMAIL PROTECTED] too. > > Jean-Marc Thanks a lot, I have just submitted the patch to [EMAIL PROTECTED] -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED]

Re: libc_r, signal handler ucontext modification

2001-06-07 Thread Stefan Hoffmeister
: On Thu, 07 Jun 2001 15:21:31 +0200, Stefan Hoffmeister wrote: >I admit that all this is somewhat anecdotal, but I haven't looked in >detail yet at what happens after the signal handler has returned to > > uthread/uthread_sig.c -> _thread_sig_wrapper Looking at code in question, I wonder wheth

Re: XFree86 4.1.0 and i810

2001-06-07 Thread Jean-Marc Zucconi
> Andrew Hesford writes: > On Thu, Jun 07, 2001 at 08:35:06AM -0500, Andrew Hesford wrote: >> The solution is to comment out the calls to I810BindGARTMemory() and >> I810UnbindGARTMemory() in the VT-switching functions. The end result is >> that I810EnterVT() and I810LeaveVT() are now ide

Re: XFree86 4.1.0 and i810

2001-06-07 Thread Andrew Hesford
On Thu, Jun 07, 2001 at 02:15:02PM +0200, Stijn Hoop wrote: > BTW, Andrew, I really hope you do succeed (esp. with the recent > 4.1.0 troubles). Thanks for investigating this! > > --Stijn The problem is incredibly simple. I explain it and offer a patch in my response to Will's messages. As many

Re: XFree86 4.1.0 and i810

2001-06-07 Thread Andrew Hesford
On Thu, Jun 07, 2001 at 08:35:06AM -0500, Andrew Hesford wrote: > The solution is to comment out the calls to I810BindGARTMemory() and > I810UnbindGARTMemory() in the VT-switching functions. The end result is > that I810EnterVT() and I810LeaveVT() are now identical in 4.1.0 to the > ones in 4.0.1,

Re: XFree86 4.1.0 and i810

2001-06-07 Thread Andrew Hesford
On Thu, Jun 07, 2001 at 06:59:15AM -0500, Will Andrews wrote: > On Thu, Jun 07, 2001 at 12:32:50AM -0500, Andrew Hesford ([EMAIL PROTECTED]) wrote: > > The XFree86 4.0.1 sources *did* offer a helpful hint. I have posted > > another email which includes a patch to fix the buggy i810 driver. > > Ar

libc_r, signal handler ucontext modification

2001-06-07 Thread Stefan Hoffmeister
Hi, given the following * FreeBSD 4.3 Release (i386) * an application linked against libc_r * and a signal handler installed with the SA_SIGINFO flag which implies that the signal handler will be called with int Signal, int SomethingBoring, uncontext_t* ucontext ow should th

Re: [Patch?] signal(SIGCHLD, SIG_IGN) is against SUSv2

2001-06-07 Thread Cejka Rudolf
Oops, kid's bugs. Thanks to David Malone ;-) Cejka Rudolf wrote (2001/06/07): > "if (ps->ps_sigact[_SIG_IDX(SIGCHLD)] = SIG_IGN)" is unnecessary. ^ == > --- sys/kern/kern_sig.c.orig Wed Jun 6 11:52:37 2001 > +++ sy

[Patch?] signal(SIGCHLD, SIG_IGN) is against SUSv2

2001-06-07 Thread Cejka Rudolf
There is following paragraph in SUSv2: If a process sets the action for the SIGCHLD signal to SIG_IGN, the behaviour is unspecified, except as specified below. If the action for the SIGCHLD signal is set to SIG_IGN, child processes of the calling processes will not be transformed into zo

Re: XFree86 4.1.0 and i810

2001-06-07 Thread Stijn Hoop
On Thu, Jun 07, 2001 at 06:59:15AM -0500, Will Andrews wrote: > On Thu, Jun 07, 2001 at 12:32:50AM -0500, Andrew Hesford ([EMAIL PROTECTED]) wrote: > > The XFree86 4.0.1 sources *did* offer a helpful hint. I have posted > > another email which includes a patch to fix the buggy i810 driver. > > Ar

Re: XFree86 4.1.0 and i810

2001-06-07 Thread Will Andrews
On Thu, Jun 07, 2001 at 12:32:50AM -0500, Andrew Hesford ([EMAIL PROTECTED]) wrote: > The XFree86 4.0.1 sources *did* offer a helpful hint. I have posted > another email which includes a patch to fix the buggy i810 driver. Are you people talking about XFree86 4.1.0 or 4.0.1? Because 4.0.1 is >WA

Re: newbussifying drivers

2001-06-07 Thread Doug Rabson
On Thu, 7 Jun 2001, Matthew N. Dodd wrote: > On Wed, 6 Jun 2001, Warner Losh wrote: > > In message <[EMAIL PROTECTED]> j mckitrick writes: > > : How would you recommending fixing this, taken from the ex driver? > > > > By deleting it. > > Uh, what? > > Non PnP devices that can be autodetected sho

Re: cloning network interfaces

2001-06-07 Thread Brian Somers
> In message <[EMAIL PROTECTED]>, Brooks Davis writes: > > >With network devices that are also normal devices the way tun is, > >you do this by just implementing a dev_clone event handler so when the > >user attempts to open a non-existent instance it's created. The problem > >with gif is that t