From owner-freebsd-hackers Sun Oct 27 0:50:56 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D873737B401; Sun, 27 Oct 2002 00:50:52 -0700 (PDT) Received: from baraca.united.net.ua (ns.united.net.ua [193.111.8.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7CDE43E3B; Sun, 27 Oct 2002 00:50:50 -0700 (PDT) (envelope-from max@vega.com) Received: from vega.vega.com (xDSL-2-2.united.net.ua [193.111.9.226]) by baraca.united.net.ua (8.12.6/8.11.6) with ESMTP id g9R7oih4090317; Sun, 27 Oct 2002 09:50:46 +0200 (EET) (envelope-from max@vega.com) Received: from vega.vega.com (max@localhost [127.0.0.1]) by vega.vega.com (8.12.6/8.12.5) with ESMTP id g9R7onaJ036558; Sun, 27 Oct 2002 09:50:49 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: (from max@localhost) by vega.vega.com (8.12.6/8.12.5/Submit) id g9R7ohAE036557; Sun, 27 Oct 2002 09:50:43 +0200 (EET) Date: Sun, 27 Oct 2002 09:50:43 +0200 From: Maxim Sobolev To: Nate Lawson Cc: jlemon@FreeBSD.ORG, hackers@FreeBSD.ORG, audit@FreeBSD.ORG Subject: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC Message-ID: <20021027075043.GA36533@vega.vega.com> References: <3DB79DFA.FA719B8F@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Oct 26, 2002 at 06:09:31PM -0700, Nate Lawson wrote: > On Thu, 24 Oct 2002, Maxim Sobolev wrote: > > Please review the patch, which adds two new types of events - > > NOTE_STARTEXEC and NOTE_STOPEXEC, that could be used to get > > notification when the image starts or stops executing. For example, it > > could be used to monitor that a daemon is up and running and notify > > administrator when for some reason in exits. I am running this code > > for more than a year now without any problems. > > > > Any comments and suggestions are welcome. > > Couldn't this just be done by init(8) and /etc/ttys? Or inetd? If you > want to write your own, couldn't you use waitpid()? Or a kevent() of > EVFILT_PROC with NOTE_EXIT/NOTE_FORK? I'm not sure I see the need for > this. EVFILT_PROC operates on pids, while NOTE_{START,STOP}EXEC operate on vnodes - it is the main difference. Currently, you can't reliably get a notification when kernes started executing some arbitrary executable from your fs. > Comments below. > > > +.It NOTE_STOPEXEC > > +Execution of the file referenced by the descriptor ended. Triggered > > when > > +the process associated with the file exited or was replaced with anoter > > +image using > > +.Xr execve 2 > > +or simial syscall. The PID of the process is returned in > ^^^^^ > typo OK, fixed. > > Index: src/sys/sys/event.h > > =================================================================== > > RCS file: /home/ncvs/src/sys/sys/event.h,v > > retrieving revision 1.21 > > diff -d -u -r1.21 event.h > > --- src/sys/sys/event.h 29 Jun 2002 19:14:52 -0000 1.21 > > +++ src/sys/sys/event.h 24 Oct 2002 06:57:41 -0000 > > @@ -83,13 +83,15 @@ > > /* > > * data/hint flags for EVFILT_VNODE, shared with userspace > > */ > > -#define NOTE_DELETE 0x0001 /* vnode was removed */ > > -#define NOTE_WRITE 0x0002 /* data contents changed */ > > -#define NOTE_EXTEND 0x0004 /* size increased */ > > -#define NOTE_ATTRIB 0x0008 /* attributes changed */ > > -#define NOTE_LINK 0x0010 /* link count changed */ > > -#define NOTE_RENAME 0x0020 /* vnode was renamed */ > > -#define NOTE_REVOKE 0x0040 /* vnode access was revoked */ > > +#define NOTE_DELETE 0x00100000 /* vnode was removed */ > > +#define NOTE_WRITE 0x00200000 /* data contents changed */ > > +#define NOTE_EXTEND 0x00400000 /* size increased */ > > +#define NOTE_ATTRIB 0x00800000 /* attributes changed */ > > +#define NOTE_LINK 0x01000000 /* link count changed */ > > +#define NOTE_RENAME 0x02000000 /* vnode was renamed */ > > +#define NOTE_REVOKE 0x04000000 /* vnode access was revoked */ > > +#define NOTE_STARTEXEC 0x08000000 /* vnode was executed */ > > +#define NOTE_STOPEXEC 0x10000000 /* vnode execution stopped */ > > +/* Applies both to EVFILT_VNODE and EVFILT_PROC */ > > #define NOTE_PDATAMASK 0x000fffff /* mask for pid */ > > I don't think we should burn our 32 bits on this. Since pids are 32 bits, > this interface will fail unpredictably. This is no different from the current situation and doesn't add any new breakage. All EVFILT_PROC are currently limited to 16-bit pids only. Of course this misbehaviour should be fixed eventually, but it wasn't the purpose of this patch. > > /* additional flags for EVFILT_PROC */ > > Index: src/sys/kern/kern_exec.c > > =================================================================== > > RCS file: /home/ncvs/src/sys/kern/kern_exec.c,v > > retrieving revision 1.193 > > diff -d -u -r1.193 kern_exec.c > > --- src/sys/kern/kern_exec.c 11 Oct 2002 21:04:01 -0000 1.193 > > +++ src/sys/kern/kern_exec.c 24 Oct 2002 06:57:41 -0000 > > @@ -518,6 +518,8 @@ > > * to locking the proc lock. > > */ > > textvp = p->p_textvp; > > + if (textvp) > > + VN_KNOTE(textvp, NOTE_STOPEXEC | p->p_pid); > > p->p_textvp = ndp->ni_vp; > > Do these always stay an int or are there casts that could result in endian > problems? > > >Index: src/sys/kern/kern_fork.c > >=================================================================== > >RCS file: /home/ncvs/src/sys/kern/kern_fork.c,v > >retrieving revision 1.172 > >diff -d -u -r1.172 kern_fork.c > >--- src/sys/kern/kern_fork.c 18 Oct 2002 17:45:41 -0000 1.172 > >+++ src/sys/kern/kern_fork.c 24 Oct 2002 06:58:03 -0000 > >@@ -724,6 +724,8 @@ > > * tell any interested parties about the new process > > */ > > KNOTE(&p1->p_klist, NOTE_FORK | p2->p_pid); > >+ if (p2->p_textvp != NULL) > >+ VN_KNOTE(p2->p_textvp, NOTE_STARTEXEC | p2->p_pid); > > PROC_UNLOCK(p1); > > > > /* > > This shows my doubt for the need for this since the NOTE_FORK is immediately > before your duplicate NOTE_STARTEXEC. Again, they apply to a different types of objects - NOTE_FORK is for pids, while NOTE_STARTEXEC is for vnodes. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 1: 4:30 2002 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 2AAB037B401; Sun, 27 Oct 2002 01:04:29 -0700 (PDT) Date: Sun, 27 Oct 2002 01:04:29 -0700 From: Juli Mallett To: Maxim Sobolev Cc: Nate Lawson , jlemon@FreeBSD.ORG, hackers@FreeBSD.ORG, audit@FreeBSD.ORG Subject: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC Message-ID: <20021027010429.A90908@FreeBSD.org> References: <3DB79DFA.FA719B8F@FreeBSD.org> <20021027075043.GA36533@vega.vega.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20021027075043.GA36533@vega.vega.com>; from sobomax@FreeBSD.ORG on Sun, Oct 27, 2002 at 09:50:43AM +0200 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-LiveJournal: flata, jmallett X-Negacore: Yes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * De: Maxim Sobolev [ Data: 2002-10-27 ] [ Subjecte: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC ] > On Sat, Oct 26, 2002 at 06:09:31PM -0700, Nate Lawson wrote: > > On Thu, 24 Oct 2002, Maxim Sobolev wrote: > > > Please review the patch, which adds two new types of events - > > > NOTE_STARTEXEC and NOTE_STOPEXEC, that could be used to get > > > notification when the image starts or stops executing. For example, it > > > could be used to monitor that a daemon is up and running and notify > > > administrator when for some reason in exits. I am running this code > > > for more than a year now without any problems. > > > > > > Any comments and suggestions are welcome. > > > > Couldn't this just be done by init(8) and /etc/ttys? Or inetd? If you > > want to write your own, couldn't you use waitpid()? Or a kevent() of > > EVFILT_PROC with NOTE_EXIT/NOTE_FORK? I'm not sure I see the need for > > this. > > EVFILT_PROC operates on pids, while NOTE_{START,STOP}EXEC operate on > vnodes - it is the main difference. Currently, you can't reliably > get a notification when kernes started executing some arbitrary > executable from your fs. This is not a job for the kernel, I don't think. Implement it in userland in terms of having the daemon write to a pidfile at startup, and have SIGUSR1 make it tell the sender it's alive (using my sigq stuff this is trivial, just send SIGUSR2 back), and periodically read the pidfile and try to communciate with the daemon, and respawn it if it fails. This could be racey if done poorly. However if you want this for *any* executable, rather than just "some arbitrary executable" rather than some specific job, then while I wonder how useful it is in a generic concept, the kq solution might be more reasonable. Juli Mallett | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger jmallett@FreeBSD.org http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 1:23: 9 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54E0437B401; Sun, 27 Oct 2002 01:23:08 -0700 (PDT) Received: from baraca.united.net.ua (ns.united.net.ua [193.111.8.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FE1F43E3B; Sun, 27 Oct 2002 01:23:07 -0700 (PDT) (envelope-from max@vega.com) Received: from vega.vega.com (xDSL-2-2.united.net.ua [193.111.9.226]) by baraca.united.net.ua (8.12.6/8.11.6) with ESMTP id g9R8N4h4091536; Sun, 27 Oct 2002 10:23:05 +0200 (EET) (envelope-from max@vega.com) Received: from vega.vega.com (max@localhost [127.0.0.1]) by vega.vega.com (8.12.6/8.12.5) with ESMTP id g9R8NAaJ036678; Sun, 27 Oct 2002 10:23:10 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: (from max@localhost) by vega.vega.com (8.12.6/8.12.5/Submit) id g9R8N9JJ036677; Sun, 27 Oct 2002 10:23:09 +0200 (EET) Date: Sun, 27 Oct 2002 10:23:09 +0200 From: Maxim Sobolev To: Juli Mallett Cc: Nate Lawson , jlemon@FreeBSD.ORG, hackers@FreeBSD.ORG, audit@FreeBSD.ORG Subject: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC Message-ID: <20021027082309.GC36533@vega.vega.com> References: <3DB79DFA.FA719B8F@FreeBSD.org> <20021027075043.GA36533@vega.vega.com> <20021027010429.A90908@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20021027010429.A90908@FreeBSD.org> User-Agent: Mutt/1.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Oct 27, 2002 at 01:04:29AM -0700, Juli Mallett wrote: > * De: Maxim Sobolev [ Data: 2002-10-27 ] > [ Subjecte: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC ] > > On Sat, Oct 26, 2002 at 06:09:31PM -0700, Nate Lawson wrote: > > > On Thu, 24 Oct 2002, Maxim Sobolev wrote: > > > > Please review the patch, which adds two new types of events - > > > > NOTE_STARTEXEC and NOTE_STOPEXEC, that could be used to get > > > > notification when the image starts or stops executing. For example, it > > > > could be used to monitor that a daemon is up and running and notify > > > > administrator when for some reason in exits. I am running this code > > > > for more than a year now without any problems. > > > > > > > > Any comments and suggestions are welcome. > > > > > > Couldn't this just be done by init(8) and /etc/ttys? Or inetd? If you > > > want to write your own, couldn't you use waitpid()? Or a kevent() of > > > EVFILT_PROC with NOTE_EXIT/NOTE_FORK? I'm not sure I see the need for > > > this. > > > > EVFILT_PROC operates on pids, while NOTE_{START,STOP}EXEC operate on > > vnodes - it is the main difference. Currently, you can't reliably > > get a notification when kernes started executing some arbitrary > > executable from your fs. > > This is not a job for the kernel, I don't think. Why not? Kernel now reports number of internal events via kqueue(2) interface, there is nothing wrong in adding yet another one. BTW, linux and irix already have similar functionality provided by /dev/imon. > Implement it in userland > in terms of having the daemon write to a pidfile at startup, and have SIGUSR1 > make it tell the sender it's alive (using my sigq stuff this is trivial, just > send SIGUSR2 back), and periodically read the pidfile and try to communciate > with the daemon, and respawn it if it fails. This could be racey if done > poorly. However if you want this for *any* executable, rather than just > "some arbitrary executable" rather than some specific job, then while I wonder > how useful it is in a generic concept, the kq solution might be more > reasonable. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 1:24:21 2002 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 5D90C37B401; Sun, 27 Oct 2002 01:24:19 -0700 (PDT) Date: Sun, 27 Oct 2002 01:24:19 -0700 From: Juli Mallett To: Maxim Sobolev Cc: Nate Lawson , jlemon@FreeBSD.ORG, hackers@FreeBSD.ORG, audit@FreeBSD.ORG Subject: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC Message-ID: <20021027012419.A94775@FreeBSD.org> References: <3DB79DFA.FA719B8F@FreeBSD.org> <20021027075043.GA36533@vega.vega.com> <20021027010429.A90908@FreeBSD.org> <20021027082309.GC36533@vega.vega.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20021027082309.GC36533@vega.vega.com>; from sobomax@FreeBSD.ORG on Sun, Oct 27, 2002 at 10:23:09AM +0200 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-LiveJournal: flata, jmallett X-Negacore: Yes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * De: Maxim Sobolev [ Data: 2002-10-27 ] [ Subjecte: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC ] > On Sun, Oct 27, 2002 at 01:04:29AM -0700, Juli Mallett wrote: > > * De: Maxim Sobolev [ Data: 2002-10-27 ] > > [ Subjecte: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC ] > > > On Sat, Oct 26, 2002 at 06:09:31PM -0700, Nate Lawson wrote: > > > > On Thu, 24 Oct 2002, Maxim Sobolev wrote: > > > > > Please review the patch, which adds two new types of events - > > > > > NOTE_STARTEXEC and NOTE_STOPEXEC, that could be used to get > > > > > notification when the image starts or stops executing. For example, it > > > > > could be used to monitor that a daemon is up and running and notify > > > > > administrator when for some reason in exits. I am running this code > > > > > for more than a year now without any problems. > > > > > > > > > > Any comments and suggestions are welcome. > > > > > > > > Couldn't this just be done by init(8) and /etc/ttys? Or inetd? If you > > > > want to write your own, couldn't you use waitpid()? Or a kevent() of > > > > EVFILT_PROC with NOTE_EXIT/NOTE_FORK? I'm not sure I see the need for > > > > this. > > > > > > EVFILT_PROC operates on pids, while NOTE_{START,STOP}EXEC operate on > > > vnodes - it is the main difference. Currently, you can't reliably > > > get a notification when kernes started executing some arbitrary > > > executable from your fs. > > > > This is not a job for the kernel, I don't think. > > Why not? Kernel now reports number of internal events via kqueue(2) interface, > there is nothing wrong in adding yet another one. BTW, linux and irix already > have similar functionality provided by /dev/imon. If you implemented a kq interface, and an imon wrapper, I'd be much more impressed. A less-divergant interface to do this would be nice, even if kq is the backing. In fact, especially if kq is the backing, kq is strong, kq will make us smart. -- Juli Mallett | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger jmallett@FreeBSD.org http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 1:51:47 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 196A037B401; Sun, 27 Oct 2002 01:51:44 -0800 (PST) Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FD8F43E65; Sun, 27 Oct 2002 01:51:38 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0011.cvx40-bradley.dialup.earthlink.net ([216.244.42.11] helo=mindspring.com) by harrier.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 185k50-00044x-00; Sun, 27 Oct 2002 01:51:34 -0800 Message-ID: <3DBBB6D9.F369A5CD@mindspring.com> Date: Sun, 27 Oct 2002 01:50:17 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Juli Mallett Cc: Maxim Sobolev , Nate Lawson , jlemon@FreeBSD.ORG, hackers@FreeBSD.ORG, audit@FreeBSD.ORG Subject: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC References: <3DB79DFA.FA719B8F@FreeBSD.org> <20021027075043.GA36533@vega.vega.com> <20021027010429.A90908@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Juli Mallett wrote: > > EVFILT_PROC operates on pids, while NOTE_{START,STOP}EXEC operate on > > vnodes - it is the main difference. Currently, you can't reliably > > get a notification when kernes started executing some arbitrary > > executable from your fs. > > This is not a job for the kernel, I don't think. Implement it in userland > in terms of having the daemon write to a pidfile at startup, and have SIGUSR1 > make it tell the sender it's alive (using my sigq stuff this is trivial, just > send SIGUSR2 back), and periodically read the pidfile and try to communciate > with the daemon, and respawn it if it fails. This could be racey if done > poorly. However if you want this for *any* executable, rather than just > "some arbitrary executable" rather than some specific job, then while I wonder > how useful it is in a generic concept, the kq solution might be more > reasonable. The problem with daemon's is that they are not children of a process other than "init". It's only useful to use SIGCHLD as the termination notification if it's a parent process being notified. For most daemons, this would mean relacing "init". It's useful to replace "init", and "syslog", both, to be able to track state for services; however, the notification on termination is significantly better if anyone who cares can monitor for it. The main problem with this approach is that it's not the service identity that's communicated, but the name of a file, and the file name is for a path that's probably relative to the current directory in most cases (or could be), and so isn't globally unique. It is also not useful to poll, since your daemon could be down for an entire poll interval; also, it means you have to trust the poll interval itself will be maintained... and if your failure is a failure of the process doing the polling itself, that's broken. In terms of most services, actually gross notification is the minmal level of assurance: just because a program that's supposed to offer a service is caught in an endless loop, so that there has not been an exit, doesn't mean that it's actually offering the service that it was intended to offer. The best check is to actually attach to, and utilize the service. There is also an intermediate level... which is probably best served by kevents, actually. For network services, when a listen on a socket occurs, it occurs on a socket specific to a service: a well known port. One obvious thing to do is to cause events to occur when a listen is issued, and when a listen socket is closed. One might also do an implicit listen in the case of an outstanding listen socket, for which no listen was executed (default listen queue depth)... basically a blocking accept vs. a connect and/or a select for readability on an outstanding socket. So there are various levels of service availability notification: 0) A "ping" of the system offering the service indicates that the interrupt code and network stack are active, but nothing else. 1) The program is running/stopped, with a notification latency (this is your suggested scenario, having to do with pid files). 2) The program is running/stopped, with no notification latency (this is the NOTE_STARTEXEC/NOTE_STOPEXEC scenario). 3) A server is listening on a well known port/has stopped listening on a well known port (this is my suggested scenario, and has the benefit of accounting for configuration and other latencies that #1 and #2 can miss -- it closes race windows). 4) Active status monitoring, through attempts to actually use a service offered by a server (e.g. making a DNS request to a DNS server, doing a "HEAD /" on an HTTP server, saying "EHLO" to an SMTP server, etc.). Obviously, #4 is the best approach. Barring that, #3 provides much better identification of services, but onl works on netwqork services. #2 provides information about services by (potentially relative or non-matching) path name. Actually, the best approach for this would be to return a "stat" buffer for the file that was exec'ed or stopped, so that the caller could use the name information for logging, but could verify that the "sendmail" being run was, say, /usr/local/bin/sendmail, instead of /usr/sbin/sendmail: the way this would work is to have the program which cared stat the executable that it expected to run, and then compare the "stat" information (dev_t and ino_t) to verify that the uniquely identified executable was in fact what was running. This is *much* better than a (partial) path comparison by (nonunique) file name (consider also: hard links with different names). So, in general: o NOTE_STARTEXEC/NOTE_STOPEXEC are a good idea; they close a latency window, and they close a race window, and the eliminate a single-point-of-failure that would come from having one monitoring program ("who monitors the monitors?"). o The name information being returned is insufficient to uniquely identify the executable to an interested program o Minimally, the information the interested program really wants is the dev_t/ino_t pair o It's OK to offer the exec path name information, at least as much of it as is known, but that's additional information, and is not sufficient for the application for which the interface was intended. At best, it may be useful for logging purposes o Another event set for NOTE_STARTLISTEN/NOTE_STOPLISTEN would be significantly more useful for most purposes for which the NOTE_STARTEXEC/NOTE_STOPEXEC events are being introduced -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 1:58:11 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05BE537B401; Sun, 27 Oct 2002 01:58:10 -0800 (PST) Received: from baraca.united.net.ua (ns.united.net.ua [193.111.8.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E58D43E42; Sun, 27 Oct 2002 01:58:08 -0800 (PST) (envelope-from max@vega.com) Received: from vega.vega.com (xDSL-2-2.united.net.ua [193.111.9.226]) by baraca.united.net.ua (8.12.6/8.11.6) with ESMTP id g9R9w5h4095172; Sun, 27 Oct 2002 11:58:06 +0200 (EET) (envelope-from max@vega.com) Received: from vega.vega.com (max@localhost [127.0.0.1]) by vega.vega.com (8.12.6/8.12.5) with ESMTP id g9R9w9aJ036811; Sun, 27 Oct 2002 11:58:09 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: (from max@localhost) by vega.vega.com (8.12.6/8.12.5/Submit) id g9R9w8qs036810; Sun, 27 Oct 2002 11:58:08 +0200 (EET) Date: Sun, 27 Oct 2002 11:58:08 +0200 From: Maxim Sobolev To: Juli Mallett Cc: Nate Lawson , jlemon@FreeBSD.ORG, hackers@FreeBSD.ORG, audit@FreeBSD.ORG Subject: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC Message-ID: <20021027095808.GA36796@vega.vega.com> References: <3DB79DFA.FA719B8F@FreeBSD.org> <20021027075043.GA36533@vega.vega.com> <20021027010429.A90908@FreeBSD.org> <20021027082309.GC36533@vega.vega.com> <20021027012419.A94775@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20021027012419.A94775@FreeBSD.org> User-Agent: Mutt/1.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Oct 27, 2002 at 01:24:19AM -0700, Juli Mallett wrote: > * De: Maxim Sobolev [ Data: 2002-10-27 ] > [ Subjecte: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC ] > > On Sun, Oct 27, 2002 at 01:04:29AM -0700, Juli Mallett wrote: > > > * De: Maxim Sobolev [ Data: 2002-10-27 ] > > > [ Subjecte: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC ] > > > > On Sat, Oct 26, 2002 at 06:09:31PM -0700, Nate Lawson wrote: > > > > > On Thu, 24 Oct 2002, Maxim Sobolev wrote: > > > > > > Please review the patch, which adds two new types of events - > > > > > > NOTE_STARTEXEC and NOTE_STOPEXEC, that could be used to get > > > > > > notification when the image starts or stops executing. For example, it > > > > > > could be used to monitor that a daemon is up and running and notify > > > > > > administrator when for some reason in exits. I am running this code > > > > > > for more than a year now without any problems. > > > > > > > > > > > > Any comments and suggestions are welcome. > > > > > > > > > > Couldn't this just be done by init(8) and /etc/ttys? Or inetd? If you > > > > > want to write your own, couldn't you use waitpid()? Or a kevent() of > > > > > EVFILT_PROC with NOTE_EXIT/NOTE_FORK? I'm not sure I see the need for > > > > > this. > > > > > > > > EVFILT_PROC operates on pids, while NOTE_{START,STOP}EXEC operate on > > > > vnodes - it is the main difference. Currently, you can't reliably > > > > get a notification when kernes started executing some arbitrary > > > > executable from your fs. > > > > > > This is not a job for the kernel, I don't think. > > > > Why not? Kernel now reports number of internal events via kqueue(2) interface, > > there is nothing wrong in adding yet another one. BTW, linux and irix already > > have similar functionality provided by /dev/imon. > > If you implemented a kq interface, and an imon wrapper, I'd be much more > impressed. A less-divergant interface to do this would be nice, even if > kq is the backing. In fact, especially if kq is the backing, kq is strong, > kq will make us smart. Actually, the only user of /dev/imon I am aware of is SGI's fam package (file alteration monitor). I've already implemented subset of it using BSD kqueue as a backend instead of imon. Check bsdfam project on sourceforge for details. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 9:18:50 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A54FD37B401 for ; Sun, 27 Oct 2002 09:18:48 -0800 (PST) Received: from blackbox.yayproductions.com (h-66-166-17-53.SNVACAID.covad.net [66.166.17.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C4F443E4A for ; Sun, 27 Oct 2002 09:18:48 -0800 (PST) (envelope-from davek@saturn5.com) Received: from localhost (davek@localhost) by blackbox.yayproductions.com (8.11.6/8.11.3) with ESMTP id g9RHCXs00342 for ; Sun, 27 Oct 2002 09:12:33 -0800 (PST) (envelope-from davek@saturn5.com) X-Authentication-Warning: blackbox.yayproductions.com: davek owned process doing -bs Date: Sun, 27 Oct 2002 09:12:33 -0800 (PST) From: David Nicholas Kayal X-X-Sender: davek@blackbox.yayproductions.com To: freebsd-hackers@FreeBSD.ORG Subject: i am looking for a 5 volt signal Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm looking for a 5 volt signal. I have wires plugged into pins 2 and 25 of the parallel port. I have written a small program: #include #include #include int main() { int fd; while(1) { ioctl(fd, PPISDATA, 255); } } and have it executing... I have a multi-meter with the positive lead touching the pin 2 wire and the negative lead touching pin 25 wire, but i am not registering any voltage. =( I am sad. I have recompiled my kernel to disable plip and enable ppi. The following is a snipet of my kernel configuration: # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer # # 2002 oct 27 - removed plip and added ppi. # #device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da any help would be very much appreciated To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 9:28:19 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E477037B401 for ; Sun, 27 Oct 2002 09:28:16 -0800 (PST) Received: from blackbox.yayproductions.com (h-66-166-17-53.SNVACAID.covad.net [66.166.17.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F1A743E3B for ; Sun, 27 Oct 2002 09:28:16 -0800 (PST) (envelope-from davek@saturn5.com) Received: from localhost (davek@localhost) by blackbox.yayproductions.com (8.11.6/8.11.3) with ESMTP id g9RHM1L00370; Sun, 27 Oct 2002 09:22:01 -0800 (PST) (envelope-from davek@saturn5.com) X-Authentication-Warning: blackbox.yayproductions.com: davek owned process doing -bs Date: Sun, 27 Oct 2002 09:22:01 -0800 (PST) From: David Nicholas Kayal X-X-Sender: davek@blackbox.yayproductions.com To: nbari@unixmexico.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: i am looking for a 5 volt signal In-Reply-To: <24109.148.243.211.1.1035739351.squirrel@mail.unixmexico.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Shouldn't the fact that the signal is in a while loop keep the 5 volt signal going? Isn't the parallel port being blasted with the value 255 over and over again? The serial port will not fulfill what i am ultimately trying to achive. I am trying to have the parallel port to control 8 relays each turing on/off based upon which bit i send out to the port. On Sun, 27 Oct 2002 nbari@unixmexico.com wrote: > try using also the serial port and a logical buffer > > the 5 volt signal is very fast and your multimeter is maybe not to fast > > > I'm looking for a 5 volt signal. > > > > I have wires plugged into pins 2 and 25 of the parallel port. > > > > I have written a small program: > > > > #include > > #include > > #include > > > > int main() > > { > > int fd; > > while(1) > > { > > ioctl(fd, PPISDATA, 255); > > } > > } > > > > and have it executing... > > > > I have a multi-meter with the positive lead touching the pin 2 wire and > > the negative lead touching pin 25 wire, but i am not registering any > > voltage. > > > > =3D( > > > > I am sad. > > > > I have recompiled my kernel to disable plip and enable ppi. The > > following is a snipet of my kernel configuration: > > > > # Parallel port > > device=09=09ppc0=09at isa? irq 7 > > device=09=09ppbus=09=09# Parallel port bus (required) > > device=09=09lpt=09=09# Printer > > # > > # 2002 oct 27 - removed plip and added ppi. > > # > > #device=09=09plip=09=09# TCP/IP over parallel > > device=09=09ppi=09=09# Parallel port interface device > > #device=09=09vpo=09=09# Requires scbus and da > > > > any help would be very much appreciated > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ----------------------------------------- > "UNIXMEXICO la comunidad *nix en todo M=E9xico!" > http://www.unixmexico.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 9:43:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C36CC37B401 for ; Sun, 27 Oct 2002 09:43:38 -0800 (PST) Received: from blackbox.yayproductions.com (h-66-166-17-53.SNVACAID.covad.net [66.166.17.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FD1143E6E for ; Sun, 27 Oct 2002 09:43:38 -0800 (PST) (envelope-from davek@saturn5.com) Received: from localhost (davek@localhost) by blackbox.yayproductions.com (8.11.6/8.11.3) with ESMTP id g9RHbNG00406; Sun, 27 Oct 2002 09:37:23 -0800 (PST) (envelope-from davek@saturn5.com) X-Authentication-Warning: blackbox.yayproductions.com: davek owned process doing -bs Date: Sun, 27 Oct 2002 09:37:23 -0800 (PST) From: David Nicholas Kayal X-X-Sender: davek@blackbox.yayproductions.com To: nbari@unixmexico.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: i am looking for a 5 volt signal In-Reply-To: <34470.148.243.211.1.1035740270.squirrel@mail.unixmexico.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm having problems just using 1 bit fromt he parallel port at this time. On Sun, 27 Oct 2002 nbari@unixmexico.com wrote: > the parallel port then is ok > now you can use a logical multiplexer > > and from the paralel port you can use just 3 bits > > take a look to the data sheets ot this multiplexer > > http://www.cs.utah.edu/classes/cs3700/handouts/pdf/MM74C150.pdf > > the input of the multiplexer will be > > 000 > 001 > 010 > 011 > 100 > 101 > 110 > 111 > > and at the ouput you will have a leched 1 or 0 ( 5volts or 0 volts) the > ones you can aply to your relays > > > > Shouldn't the fact that the signal is in a while loop keep the 5 volt > > signal going? Isn't the parallel port being blasted with the > > value 255 over and over again? > > > > The serial port will not fulfill what i am ultimately trying to achive. > > I am trying to have the parallel port to control 8 relays each turing > > on/off based upon which bit i send out to the port. > > > > On Sun, 27 Oct 2002 nbari@unixmexico.com wrote: > > > >> try using also the serial port and a logical buffer > >> > >> the 5 volt signal is very fast and your multimeter is maybe not to > >> fast > >> > >> > I'm looking for a 5 volt signal. > >> > > >> > I have wires plugged into pins 2 and 25 of the parallel port. > >> > > >> > I have written a small program: > >> > > >> > #include > >> > #include > >> > #include > >> > > >> > int main() > >> > { > >> > int fd; > >> > while(1) > >> > { > >> > ioctl(fd, PPISDATA, 255); > >> > } > >> > } > >> > > >> > and have it executing... > >> > > >> > I have a multi-meter with the positive lead touching the pin 2 wire > >> and the negative lead touching pin 25 wire, but i am not registering > >> any voltage. > >> > > >> > =3D( > >> > > >> > I am sad. > >> > > >> > I have recompiled my kernel to disable plip and enable ppi. The > >> following is a snipet of my kernel configuration: > >> > > >> > # Parallel port > >> > device=09=09ppc0=09at isa? irq 7 > >> > device=09=09ppbus=09=09# Parallel port bus (required) > >> > device=09=09lpt=09=09# Printer > >> > # > >> > # 2002 oct 27 - removed plip and added ppi. > >> > # > >> > #device=09=09plip=09=09# TCP/IP over parallel > >> > device=09=09ppi=09=09# Parallel port interface device > >> > #device=09=09vpo=09=09# Requires scbus and da > >> > > >> > any help would be very much appreciated > >> > > >> > > >> > To Unsubscribe: send mail to majordomo@FreeBSD.org > >> > with "unsubscribe freebsd-hackers" in the body of the message > >> > >> > >> > >> ----------------------------------------- > >> "UNIXMEXICO la comunidad *nix en todo M=E9xico!" > >> http://www.unixmexico.org/ > >> > >> > >> > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ----------------------------------------- > "UNIXMEXICO la comunidad *nix en todo M=E9xico!" > http://www.unixmexico.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 11:19:17 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 878BB37B401 for ; Sun, 27 Oct 2002 11:19:16 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36A2243E4A for ; Sun, 27 Oct 2002 11:19:16 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.5/8.12.5) with ESMTP id g9RJJFFC091314; Sun, 27 Oct 2002 11:19:15 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.5/8.12.5/Submit) id g9RJJFEm091313; Sun, 27 Oct 2002 11:19:15 -0800 (PST) (envelope-from dillon) Date: Sun, 27 Oct 2002 11:19:15 -0800 (PST) From: Matthew Dillon Message-Id: <200210271919.g9RJJFEm091313@apollo.backplane.com> To: David Nicholas Kayal Cc: nbari@unixmexico.com, freebsd-hackers@FreeBSD.ORG Subject: Re: i am looking for a 5 volt signal References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :Shouldn't the fact that the signal is in a while loop keep the 5 volt :signal going? Isn't the parallel port being blasted with the :value 255 over and over again? : :The serial port will not fulfill what i am ultimately trying to achive. I :am trying to have the parallel port to control 8 relays each turing :on/off based upon which bit i send out to the port. : :.. :> try using also the serial port and a logical buffer :> :> the 5 volt signal is very fast and your multimeter is maybe not to fast :> :> > I'm looking for a 5 volt signal. Uh guys. Parallel port digital outputs do not generally have a whole lot of drive. I really doubt a parallel port output could drive a relay. And it's probably TTL level equivalents, not CMOS. Even if you ganged the output bits together I doubt you would get enough drive out of them. A serial port output (+/-12 but you may see +/-10 or -5 and +12 or other out-of-spec combinations) is far more likely to be useful in driving a relay, though again there will not be much drive. It would be far better to supply the power you need from another source, like a +5V power supply. Or just get a wallwart with DC output and run it through a linear regulator. At least then you aren't likely to burn the house down :-) -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 11:33:26 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF7DE37B401 for ; Sun, 27 Oct 2002 11:33:25 -0800 (PST) Received: from ns1.rwwa.com (ns1.rwwa.com [66.92.67.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4625D43E7B for ; Sun, 27 Oct 2002 11:33:25 -0800 (PST) (envelope-from witr@rwwa.com) Received: from rwwa.com (harvey.rwwa.com [192.124.97.11]) by ns1.rwwa.com (Postfix) with ESMTP id C76EA32B3 for ; Sun, 27 Oct 2002 14:33:23 -0500 (EST) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 X-Exmh-Isig-CompType: comp X-Exmh-Isig-Folder: inbox To: freebsd-hackers@freebsd.org Subject: Suggestion: usbd.conf uses rc.conf for options Mime-Version: 1.0 Content-Type: text/plain Date: Sun, 27 Oct 2002 14:33:23 -0500 From: Robert Withrow Message-Id: <20021027193323.C76EA32B3@ns1.rwwa.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi: I notice that usbd.conf has this for the mouse device: device "Mouse" devname "ums[0-9]+" attach "/usr/sbin/moused -p /dev/${DEVNAME} -I /var/run/moused.${DEVNAME}.pid" If usbd.conf could use rc.conf, this could be modified to attach "/usr/sbin/moused ${moused_flags} -p /dev/${DEVNAME} -I /var/run/moused.${DEVNAME}.pid" That way the user wouldn't loose his moused_flags (like accelerator settings). YMMV To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 11:47:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B81BF37B401 for ; Sun, 27 Oct 2002 11:47:12 -0800 (PST) Received: from tesla.foo.is (tesla.reverse-bias.org [217.151.166.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4163D43E4A for ; Sun, 27 Oct 2002 11:47:12 -0800 (PST) (envelope-from baldur@foo.is) Received: from there (eniac.foo.is [192.168.1.25]) by tesla.foo.is (Postfix) with SMTP id 6AA69AB93; Sun, 27 Oct 2002 19:47:10 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" From: Baldur Gislason To: Robert Withrow Subject: Re: Suggestion: usbd.conf uses rc.conf for options Date: Sun, 27 Oct 2002 19:47:10 +0000 X-Mailer: KMail [version 1.3.2] References: <20021027193323.C76EA32B3@ns1.rwwa.com> In-Reply-To: <20021027193323.C76EA32B3@ns1.rwwa.com> Cc: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20021027194710.6AA69AB93@tesla.foo.is> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I agree, that would be a nice feature in usbd, but a workaround to gain the same functionality would be: attach "/usr/sbin/moused `/usr/bin/perl -e 'while(<>) { $foo = $_ . $foo; } if($foo =~ /^moused_flags="(.*?)"$/im) { print $1; }' < /etc/rc.conf` -p /dev/${DEVNAME} -I /var/run/moused.${DEVNAME}.pid" Baldur On Sunday 27 October 2002 19:33, you wrote: > Hi: > > I notice that usbd.conf has this for the mouse device: > > device "Mouse" > devname "ums[0-9]+" > attach "/usr/sbin/moused -p /dev/${DEVNAME} -I > /var/run/moused.${DEVNAME}.pid" > > If usbd.conf could use rc.conf, this could be modified to > > attach "/usr/sbin/moused ${moused_flags} -p /dev/${DEVNAME} -I > /var/run/moused.${DEVNAME}.pid" > > That way the user wouldn't loose his moused_flags (like accelerator > settings). > > YMMV > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 11:48:16 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 116E537B401 for ; Sun, 27 Oct 2002 11:48:15 -0800 (PST) Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9821843E4A for ; Sun, 27 Oct 2002 11:48:14 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0177.cvx22-bradley.dialup.earthlink.net ([209.179.198.177] helo=mindspring.com) by scaup.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 185tON-0005OU-00; Sun, 27 Oct 2002 11:48:12 -0800 Message-ID: <3DBC42AF.C68F31B0@mindspring.com> Date: Sun, 27 Oct 2002 11:46:55 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: David Nicholas Kayal , nbari@unixmexico.com, freebsd-hackers@FreeBSD.ORG Subject: Re: i am looking for a 5 volt signal References: <200210271919.g9RJJFEm091313@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: > Uh guys. Parallel port digital outputs do not generally have a whole > lot of drive. I really doubt a parallel port output could drive a > relay. Depends on the amperage the relay draws. 8-). I used to use the paralell port output to drive a pulse dialer and "off hook" for a modem that didn't have the capability itself (a 300 baud accoustic couple modem). One of the reasons I laugh when I see the "war dialer" scene in War Games. That said, you damn well better not draw any real current from the parallel port, if you want to avoid cooking it. In other words, do *not* use it to power something external, and if you are using it for a 1/0 signal to something that wangts to switch a lot of volts and amps from a real power supply, consider using an SCR, instead. > > And it's probably TTL level equivalents, not CMOS. Even if you ganged > the output bits together I doubt you would get enough drive out of > them. > > A serial port output (+/-12 but you may see +/-10 or -5 and +12 or other > out-of-spec combinations) is far more likely to be useful in driving > a relay, though again there will not be much drive. It would be far > better to supply the power you need from another source, like a +5V > power supply. Or just get a wallwart with DC output and run it through > a linear regulator. At least then you aren't likely to burn the house > down :-) Get a brick and use an SCR to switch the brick. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 11:51:17 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B002337B401 for ; Sun, 27 Oct 2002 11:51:15 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BC7743E3B for ; Sun, 27 Oct 2002 11:51:14 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.6/8.12.6) with ESMTP id g9RJp6Nb000840; Sun, 27 Oct 2002 20:51:06 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.6/8.12.6/Submit) id g9RJp6sT000839; Sun, 27 Oct 2002 20:51:06 +0100 (CET) Date: Sun, 27 Oct 2002 20:51:05 +0100 From: Wilko Bulte To: Matthew Dillon Cc: David Nicholas Kayal , nbari@unixmexico.com, freebsd-hackers@FreeBSD.ORG Subject: Re: i am looking for a 5 volt signal Message-ID: <20021027205105.A822@freebie.xs4all.nl> References: <200210271919.g9RJJFEm091313@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200210271919.g9RJJFEm091313@apollo.backplane.com>; from dillon@apollo.backplane.com on Sun, Oct 27, 2002 at 11:19:15AM -0800 X-OS: FreeBSD 4.7-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Oct 27, 2002 at 11:19:15AM -0800, Matthew Dillon wrote: > > : > :Shouldn't the fact that the signal is in a while loop keep the 5 volt > :signal going? Isn't the parallel port being blasted with the > :value 255 over and over again? > : > :The serial port will not fulfill what i am ultimately trying to achive. I > :am trying to have the parallel port to control 8 relays each turing > :on/off based upon which bit i send out to the port. > : > :.. > :> try using also the serial port and a logical buffer > :> > :> the 5 volt signal is very fast and your multimeter is maybe not to fast > :> > :> > I'm looking for a 5 volt signal. > > Uh guys. Parallel port digital outputs do not generally have a whole > lot of drive. I really doubt a parallel port output could drive a > relay. Get a solid state relay. Parallel ports used to be build with TTL chips, but these days drive power is probably much less. > And it's probably TTL level equivalents, not CMOS. Even if you ganged > the output bits together I doubt you would get enough drive out of > them. Yup. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 12: 6:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1A3A37B401 for ; Sun, 27 Oct 2002 12:06:49 -0800 (PST) Received: from primus.vsservices.com (primus.vsservices.com [63.66.136.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3748643E4A for ; Sun, 27 Oct 2002 12:06:49 -0800 (PST) (envelope-from gclarkii@vsservices.com) Received: from prime.vsservices.com (conr-adsl-dhcp-26-247.txucom.net [209.34.26.247]) by primus.vsservices.com (8.12.6/8.12.5) with SMTP id g9RK6Z30095894; Sun, 27 Oct 2002 14:06:35 -0600 (CST) (envelope-from gclarkii@vsservices.com) Date: Sun, 27 Oct 2002 14:05:13 -0600 From: GB Clark To: Matthew Dillon Cc: davek@saturn5.com, nbari@unixmexico.com, freebsd-hackers@FreeBSD.ORG, opn5vmf@yahoo.com Subject: Re: i am looking for a 5 volt signal Message-Id: <20021027140513.3a608671.gclarkii@vsservices.com> In-Reply-To: <200210271919.g9RJJFEm091313@apollo.backplane.com> References: <200210271919.g9RJJFEm091313@apollo.backplane.com> X-Mailer: Sylpheed version 0.8.2 (GTK+ 1.2.10; i386-portbld-freebsd4.6) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 27 Oct 2002 11:19:15 -0800 (PST) Matthew Dillon wrote: > > : > :Shouldn't the fact that the signal is in a while loop keep the 5 volt > :signal going? Isn't the parallel port being blasted with the > :value 255 over and over again? > : > :The serial port will not fulfill what i am ultimately trying to achive. I > :am trying to have the parallel port to control 8 relays each turing > :on/off based upon which bit i send out to the port. > : > :.. > :> try using also the serial port and a logical buffer > :> > :> the 5 volt signal is very fast and your multimeter is maybe not to fast > :> > :> > I'm looking for a 5 volt signal. > > Uh guys. Parallel port digital outputs do not generally have a whole > lot of drive. I really doubt a parallel port output could drive a > relay. > > And it's probably TTL level equivalents, not CMOS. Even if you ganged > the output bits together I doubt you would get enough drive out of > them. > > A serial port output (+/-12 but you may see +/-10 or -5 and +12 or other > out-of-spec combinations) is far more likely to be useful in driving > a relay, though again there will not be much drive. It would be far > better to supply the power you need from another source, like a +5V > power supply. Or just get a wallwart with DC output and run it through > a linear regulator. At least then you aren't likely to burn the house > down :-) > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Two things here... One, most multimeters do not have the senistivity to monitor a pulse like this, they will just see 0 volts. You really need a scope or a probe to see this. Second, you'll can't drive an analog relay off of Pport without a latch or something. A transistor setup would work just fine. Check out http://www.circuitcellar.com/ for stuff that would work... GB -- GB Clark II | Roaming FreeBSD Admin gclarkii@VSServices.COM | General Geek CTHULU for President - Why choose the lesser of two evils? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 12:22:37 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4808137B401 for ; Sun, 27 Oct 2002 12:22:35 -0800 (PST) Received: from primus.vsservices.com (primus.vsservices.com [63.66.136.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id C49A843E77 for ; Sun, 27 Oct 2002 12:22:34 -0800 (PST) (envelope-from gclarkii@vsservices.com) Received: from prime.vsservices.com (conr-adsl-dhcp-26-247.txucom.net [209.34.26.247]) by primus.vsservices.com (8.12.6/8.12.5) with SMTP id g9RKMX30096015 for ; Sun, 27 Oct 2002 14:22:34 -0600 (CST) (envelope-from gclarkii@vsservices.com) Date: Sun, 27 Oct 2002 14:21:12 -0600 From: GB Clark To: hackers@freebsd.org Subject: Fw: Anyone got time for a quick fix commit in the libc/db? Patch included Message-Id: <20021027142112.1d774e2c.gclarkii@vsservices.com> X-Mailer: Sylpheed version 0.8.2 (GTK+ 1.2.10; i386-portbld-freebsd4.6) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, There are two seperate bugs in libc/db. The first is the in libc/db/hash/hash.c in hash_action. If hash_action is called with HASH_DELETE and the key is not found it will return -1 (error) instead of 1 (key not found) as documented in the man page. This bug is mentioned in PR misc/42429. The second is in libc/db/hash/ndbm.c. dbm_delete needs to be changed to return the status from the db call directly. As it stands now it just checks for a non-zero and returns -1 if this is so. If it returned the status directly then it would work as documented. This is the bug mentioned in PR misc/42422. Attached are two patch files relative to lib/libc/db/hash. Should have done more research before I sent the first PR...:) GB -PATCH1- *** hash.c Wed Sep 4 17:13:22 2002 --- hash.c.patched Wed Sep 4 17:11:03 2002 *************** *** 685,692 **** save_bufp->flags &= ~BUF_PIN; return (SUCCESS); } - case HASH_GET: case HASH_DELETE: default: save_bufp->flags &= ~BUF_PIN; return (ABNORMAL); --- 685,693 ---- save_bufp->flags &= ~BUF_PIN; return (SUCCESS); } case HASH_DELETE: + return 1; + case HASH_GET: default: save_bufp->flags &= ~BUF_PIN; return (ABNORMAL); -PATCH2- *** ndbm.c Wed Sep 4 17:14:44 2002 --- ndbm.c.patched Wed Sep 4 17:15:06 2002 *************** *** 171,181 **** dbtkey.data = key.dptr; dbtkey.size = key.dsize; ! status = (db->del)(db, &dbtkey, 0); ! if (status) ! return (-1); ! else ! return (0); } /* --- 171,178 ---- dbtkey.data = key.dptr; dbtkey.size = key.dsize; ! return (db->del)(db, &dbtkey, 0); ! } /* -CUT- GB -- GB Clark II | Roaming FreeBSD Admin gclarkii@VSServices.COM | General Geek CTHULU for President - Why choose the lesser of two evils? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 13:10:56 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E210C37B401; Sun, 27 Oct 2002 13:10:54 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 211D343E4A; Sun, 27 Oct 2002 13:10:52 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.6/8.12.6) with ESMTP id g9RLAmNb001205; Sun, 27 Oct 2002 22:10:49 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.6/8.12.6/Submit) id g9RLAmhD001204; Sun, 27 Oct 2002 22:10:48 +0100 (CET) Date: Sun, 27 Oct 2002 22:10:48 +0100 From: Wilko Bulte To: John Baldwin Cc: hackers@FreeBSD.ORG Subject: Re: Getting ACPI to work on -stable Message-ID: <20021027221048.A1187@freebie.xs4all.nl> References: <20021024223256.A5488@freebie.xs4all.nl> <20021024231118.A5705@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20021024231118.A5705@freebie.xs4all.nl>; from wkb@freebie.xs4all.nl on Thu, Oct 24, 2002 at 11:11:18PM +0200 X-OS: FreeBSD 4.7-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Oct 24, 2002 at 11:11:18PM +0200, Wilko Bulte wrote: > On Thu, Oct 24, 2002 at 04:36:50PM -0400, John Baldwin wrote: > > > > On 24-Oct-2002 Wilko Bulte wrote: > > > On Thu, Oct 24, 2002 at 04:29:20PM -0400, John Baldwin wrote: > > >> > > >> On 24-Oct-2002 Wilko Bulte wrote: > > >> > On Thu, Oct 24, 2002 at 03:22:19PM -0400, John Baldwin wrote: > > >> >> > > >> >> On 24-Oct-2002 Wilko Bulte wrote: > > >> >> > On Thu, Oct 24, 2002 at 02:25:57PM -0400, John Baldwin wrote: > > >> >> >> > > >> >> >> On 24-Oct-2002 Wilko Bulte wrote: > > >> >> >> > On Wed, Oct 23, 2002 at 04:20:17PM -0400, John Baldwin wrote: > > >> >> >> >> Ok, here are the instructions on getting ACPI going on 4-stable for > > >> >> >> >> those of you who are foolish^H^H^H^H^H^H^Hbrave: > > >> >> >> >> > > >> > > > >> >> > - pressing the lid switch results in an immediate reboot > > >> >> > - apm gives me: > > > Hmm, what does 'l *0xc01a5084' and 'l *0xc0160fe5' show? > > I did not trust this kernel.debug, built a new one and crashed it giving me: > > #0 dumpsys () at ../../kern/kern_shutdown.c:487 > #1 0xc015a5dd in db_fncall (dummy1=0, dummy2=0, dummy3=0, While playing with the laptop it proved that roughly all power events lead to the panic. Like running the battery flat for example :) It panics just before it gets killed because of lack of power. Wilko -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 13:26:55 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27CAF37B401 for ; Sun, 27 Oct 2002 13:26:54 -0800 (PST) Received: from blackbox.yayproductions.com (h-66-166-17-53.SNVACAID.covad.net [66.166.17.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41A8443E42 for ; Sun, 27 Oct 2002 13:26:53 -0800 (PST) (envelope-from davek@saturn5.com) Received: from localhost (davek@localhost) by blackbox.yayproductions.com (8.11.6/8.11.3) with ESMTP id g9RLKdB00715 for ; Sun, 27 Oct 2002 13:20:39 -0800 (PST) (envelope-from davek@saturn5.com) X-Authentication-Warning: blackbox.yayproductions.com: davek owned process doing -bs Date: Sun, 27 Oct 2002 13:20:39 -0800 (PST) From: David Nicholas Kayal X-X-Sender: davek@blackbox.yayproductions.com To: freebsd-hackers@freebsd.org Subject: Show me the light Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I got a LED and touched it to the positive and negative ends of two 1.5v AA batteries in a serial configuration. The LED lit up. I then crimped on pins to the end of the LED wires and again tested it with the batteries. Again, I saw the light. I plugged said tinned pins into the 2nd and 25th pinout of a 25 pin port (the parallel port): positive lead to the 2 pin, and negative pin to\ the the 25 pin. I then executed the following program: I have written a small program: #include #include #include int main() { int fd; while(1) { ioctl(fd, PPISDATA, 255); } } I am expecting to see that LED light up, flashing if not creating a solid light. However, I am not. any help would be very much appreciated Sincerely, David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 14: 7:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37D3A37B404 for ; Sun, 27 Oct 2002 14:07:07 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id C697A43E3B for ; Sun, 27 Oct 2002 14:07:06 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.5/8.12.5) with ESMTP id g9RM76FC091840; Sun, 27 Oct 2002 14:07:06 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.5/8.12.5/Submit) id g9RM76sX091839; Sun, 27 Oct 2002 14:07:06 -0800 (PST) (envelope-from dillon) Date: Sun, 27 Oct 2002 14:07:06 -0800 (PST) From: Matthew Dillon Message-Id: <200210272207.g9RM76sX091839@apollo.backplane.com> To: Terry Lambert Cc: David Nicholas Kayal , nbari@unixmexico.com, freebsd-hackers@FreeBSD.ORG Subject: Re: i am looking for a 5 volt signal References: <200210271919.g9RJJFEm091313@apollo.backplane.com> <3DBC42AF.C68F31B0@mindspring.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :Matthew Dillon wrote: :> Uh guys. Parallel port digital outputs do not generally have a whole :> lot of drive. I really doubt a parallel port output could drive a :> relay. : :Depends on the amperage the relay draws. 8-). : :I used to use the paralell port output to drive a pulse dialer and :"off hook" for a modem that didn't have the capability itself (a :300 baud accoustic couple modem). One of the reasons I laugh when :I see the "war dialer" scene in War Games. : :That said, you damn well better not draw any real current from the :parallel port, if you want to avoid cooking it. In other words, do :*not* use it to power something external, and if you are using it :for a 1/0 signal to something that wangts to switch a lot of volts :and amps from a real power supply, consider using an SCR, instead. : :-- Terry Huh. I would have expected you to use the current loop on the phone line to power the dialer. There's a significant amount of power available there, though you would have to isolate the circuit since the common mode could be upwards of one or two hundred volts. In anycase, I can only concur on the danger of ganging the parallel power output bits. A single chip is driving those outputs and is almost certainly not rated to deal with a maximal current draw from all of them at once for long periods of time. It could fry. Though if it's a TTL output there isn't much current there anyway (TTL can sink a lot of current but it can't source it, the equivalent resistance to VCC is fairly high). Serial port pins are a much better bet. Serial port outputs can handle shorts far better then parallel port outputs and since the voltages are higher you can draw a good chunk of current out of them. Use diodes to rectify the serial port outputs (be sure to orient them properly, BAR side is positive. Flip the orientation for the negative supply). -o--------------o---- positive supply to circuit | (bar) | (around +10V) DIODE DIODE | | serial-pin serial-pin | | DIODE DIODE (OPTIONAL IF YOU NEED A NEGATIVE | (bar) | SUPPLY) -o--------------o---- negative supply to circuit (around -10V) Then: positive supply to circuit -----[LINREG]---- +5V to circuit Use a 100uF (or more), a 10uF, and 0.1uF capacitor on the input side of the regulator and a 0.1uF capacitor on the output side of the regulator. The 0.1's should be as close to the linear regulator as possible. i.e.: -------supply--------o-----o----o----[LINREG]------o---- +5V supply | | | 5V | CAP CAP CAP CAP | | | | gnd gnd gnd gnd 100 10 0.1 0.1 You can gang the serial outputs (by wire-dioding them together). The driver chips are far better able to handle that sort of thing, and since the output is +12V (well, usually +9 to +12) you can pull more current before it drops down to < 5V, so you can power 5V circuitry from it (up to a point). I expect you can get at least 20mA @ 5V out of ganged serial port outputs, possibly more. You could use an SCR but linear regulators are far, far better (a little 3-pin TO92 package linear regulator). And linear regulators have overcurrent protection as well (for themselves, not for whatever is powering them). It's fairly difficult to blow one up. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 14: 7:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78DE737B401 for ; Sun, 27 Oct 2002 14:07:50 -0800 (PST) Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BC0B43E4A for ; Sun, 27 Oct 2002 14:07:49 -0800 (PST) (envelope-from babolo@aaz.links.ru) Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by aaz.links.ru (8.12.6/8.12.6) with ESMTP id g9RM8PDh096716; Mon, 28 Oct 2002 01:08:25 +0300 (MSK) (envelope-from babolo@aaz.links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.12.6/8.12.6/Submit) id g9RM8PNX096715; Mon, 28 Oct 2002 01:08:25 +0300 (MSK) Message-Id: <200210272208.g9RM8PNX096715@aaz.links.ru> Subject: Re: Show me the light X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: To: David Nicholas Kayal Date: Mon, 28 Oct 2002 01:08:25 +0300 (MSK) From: "."@babolo.ru Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I got a LED and touched it to the positive and negative ends of two 1.5v > AA batteries in a serial configuration. > The LED lit up. I then crimped on pins to the end of the LED wires and > again tested it with the batteries. Again, I saw the light. > > I plugged said tinned pins into the 2nd and 25th pinout of a 25 pin port > (the parallel port): positive lead to the 2 pin, and negative pin to\ > the the 25 pin. As far as I remember, there is open collector output on parallel port, so your wish impossible %-) Try "-" batteryes to ground, "+" batteries to "+" LED and "-" LED to data. And remember - you probably blow up your port, if not use current restrictor, usually resistor. I advice to replace LED with voltmeter in parallel with 2..5 Kohm resistor instead. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 14: 9:50 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A390B37B401 for ; Sun, 27 Oct 2002 14:09:49 -0800 (PST) Received: from vorbis.noc.easynet.net (vorbis.noc.easynet.net [195.40.1.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B94C43E6E for ; Sun, 27 Oct 2002 14:09:49 -0800 (PST) (envelope-from chrisy@vorbis.noc.easynet.net) Received: from chrisy by vorbis.noc.easynet.net with local (Exim 3.36 #1) id 185vbE-000EDO-00; Sun, 27 Oct 2002 22:09:36 +0000 Date: Sun, 27 Oct 2002 22:09:36 +0000 From: Chrisy Luke To: David Nicholas Kayal Cc: freebsd-hackers@freebsd.org Subject: Re: Show me the light Message-ID: <20021027220936.GA41450@flix.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Organization: The Flirble Internet Exchange X-URL: http://www.flix.net/ X-FTP: ftp://ftp.flirble.org/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Nicholas Kayal wrote (on Oct 27): > int main() > { > int fd; > while(1) > { > ioctl(fd, PPISDATA, 255); > } > } Doesn't "fd" normally need to have a value, such as that of a valid descriptor before you ioctl() it? Like: fd = open("/dev/ppi0", O_RDWR); Chris. -- == chrisy@flix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 14:24:43 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F99E37B401 for ; Sun, 27 Oct 2002 14:24:42 -0800 (PST) Received: from mailbox.univie.ac.at (mailbox.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2DEA43E7B for ; Sun, 27 Oct 2002 14:24:40 -0800 (PST) (envelope-from l.ertl@univie.ac.at) Received: from adslle.cc.univie.ac.at (adslle.cc.univie.ac.at [131.130.102.11]) by mailbox.univie.ac.at (8.12.2/8.12.2) with ESMTP id g9RMOXYs053324; Sun, 27 Oct 2002 23:24:35 +0100 Date: Sun, 27 Oct 2002 23:24:32 +0100 (CET) From: Lukas Ertl X-X-Sender: le@leelou.in.tern To: Wilko Bulte Cc: hackers@FreeBSD.ORG Subject: Re: Getting ACPI to work on -stable In-Reply-To: <20021027221048.A1187@freebie.xs4all.nl> Message-ID: <20021027232216.S374-100000@leelou.in.tern> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 27 Oct 2002, Wilko Bulte wrote: > > I did not trust this kernel.debug, built a new one and crashed it givin= g me: > > > > #0 dumpsys () at ../../kern/kern_shutdown.c:487 > > #1 0xc015a5dd in db_fncall (dummy1=3D0, dummy2=3D0, dummy3=3D0, > > While playing with the laptop it proved that roughly all power events > lead to the panic. Like running the battery flat for example :) > It panics just before it gets killed because of lack of power. The other way round it's the same: when you load the battery and it's getting 100% full -> boom. I already have three different coredumps :-) regards, le --=20 Lukas Ertl eMail: l.ertl@univie.ac.at UNIX-Systemadministrator Tel.: (+43 1) 4277-14073 Zentraler Informatikdienst (ZID) Fax.: (+43 1) 4277-9140 der Universit=E4t Wien http://mailbox.univie.ac.at/~le/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 14:28:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9425437B4B9 for ; Sun, 27 Oct 2002 14:28:49 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9403443E6E for ; Sun, 27 Oct 2002 14:28:48 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.6/8.12.6) with ESMTP id g9RMSlNb001786; Sun, 27 Oct 2002 23:28:47 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.6/8.12.6/Submit) id g9RMSjP1001781; Sun, 27 Oct 2002 23:28:45 +0100 (CET) Date: Sun, 27 Oct 2002 23:28:45 +0100 From: Wilko Bulte To: Lukas Ertl Cc: hackers@FreeBSD.ORG Subject: Re: Getting ACPI to work on -stable Message-ID: <20021027232845.A1767@freebie.xs4all.nl> References: <20021027221048.A1187@freebie.xs4all.nl> <20021027232216.S374-100000@leelou.in.tern> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20021027232216.S374-100000@leelou.in.tern>; from l.ertl@univie.ac.at on Sun, Oct 27, 2002 at 11:24:32PM +0100 X-OS: FreeBSD 4.7-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Oct 27, 2002 at 11:24:32PM +0100, Lukas Ertl wrote: > On Sun, 27 Oct 2002, Wilko Bulte wrote: > > > > I did not trust this kernel.debug, built a new one and crashed it giving me: > > > > > > #0 dumpsys () at ../../kern/kern_shutdown.c:487 > > > #1 0xc015a5dd in db_fncall (dummy1=0, dummy2=0, dummy3=0, > > > > While playing with the laptop it proved that roughly all power events > > lead to the panic. Like running the battery flat for example :) > > It panics just before it gets killed because of lack of power. > > The other way round it's the same: when you load the battery and it's > getting 100% full -> boom. I already have three different coredumps :-) Sounds logical ;) I have not tried that yet. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 14:46:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E960337B401 for ; Sun, 27 Oct 2002 14:46:41 -0800 (PST) Received: from mailrelay1.lanl.gov (mailrelay1.lanl.gov [128.165.4.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 278C943E4A for ; Sun, 27 Oct 2002 14:46:41 -0800 (PST) (envelope-from rminnich@lanl.gov) Received: from acl.lanl.gov (localhost.localdomain [127.0.0.1]) by mailrelay1.lanl.gov (8.12.3/8.12.3/(ccn-5)) with SMTP id g9RMk1x1025981 for ; Sun, 27 Oct 2002 15:46:01 -0700 Received: (qmail 474163 invoked from network); 27 Oct 2002 15:46:39 -0700 Received: from xed.acl.lanl.gov (128.165.147.191) by acl.lanl.gov with SMTP; 27 Oct 2002 15:46:39 -0700 Received: (qmail 30489 invoked by uid 3499); 27 Oct 2002 15:46:39 -0700 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 27 Oct 2002 15:46:39 -0700 Date: Sun, 27 Oct 2002 15:46:39 -0700 (MST) From: Ronald G Minnich X-X-Sender: To: David Nicholas Kayal Cc: Subject: Re: Show me the light In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Put a voltmeter on the PP port. Measure voltage. put am ammeter on the PP port. measure current. (start at 10 amps to be safe, trust me, you're not going to cause the ammeter any trouble). See if Voc and Isc are in a usable range. If not, go get yerself a little reed relay or solid state relay. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 14:48: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B41BF37B401 for ; Sun, 27 Oct 2002 14:48:02 -0800 (PST) Received: from mailrelay2.lanl.gov (mailrelay2.lanl.gov [128.165.4.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0924F43E3B for ; Sun, 27 Oct 2002 14:48:02 -0800 (PST) (envelope-from rminnich@lanl.gov) Received: from acl.lanl.gov (localhost.localdomain [127.0.0.1]) by mailrelay2.lanl.gov (8.12.3/8.12.3/(ccn-5)) with SMTP id g9RMm1H4017544 for ; Sun, 27 Oct 2002 15:48:01 -0700 Received: (qmail 471004 invoked from network); 27 Oct 2002 15:48:01 -0700 Received: from xed.acl.lanl.gov (128.165.147.191) by acl.lanl.gov with SMTP; 27 Oct 2002 15:48:01 -0700 Received: (qmail 30493 invoked by uid 3499); 27 Oct 2002 15:48:00 -0700 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 27 Oct 2002 15:48:00 -0700 Date: Sun, 27 Oct 2002 15:48:00 -0700 (MST) From: Ronald G Minnich X-X-Sender: To: <"."@babolo.ru> Cc: David Nicholas Kayal , Subject: Re: Show me the light In-Reply-To: <200210272208.g9RM8PNX096715@aaz.links.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 28 Oct 2002 .@babolo.ru wrote: > As far as I remember, there is open collector output > on parallel port, so your wish impossible %-) oops, I forgot that little deal. Yup, you need a pullup. you can get PP relay modules for not much. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 14:54:24 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FB6437B401 for ; Sun, 27 Oct 2002 14:54:23 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1618943E3B for ; Sun, 27 Oct 2002 14:54:12 -0800 (PST) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.5/8.12.6) id g9RMrs2G024315; Sun, 27 Oct 2002 23:53:54 +0100 (CET) (envelope-from sos) From: Soeren Schmidt Message-Id: <200210272253.g9RMrs2G024315@spider.deepcore.dk> Subject: Re: Show me the light In-Reply-To: To: Ronald G Minnich Date: Sun, 27 Oct 2002 23:53:54 +0100 (CET) Cc: "."@babolo.ru, David Nicholas Kayal , freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Ronald G Minnich wrote: > On Mon, 28 Oct 2002 .@babolo.ru wrote: > > > As far as I remember, there is open collector output > > on parallel port, so your wish impossible %-) > > oops, I forgot that little deal. Yup, you need a pullup. Only the control signals are OC, the databits are tri state. Actually, depending on how many databits one needs, the rest can be used to provide a usable powersupply when they are set to '1'. I use that for an 8chan AD converter that then fit into the parport plug housing and no need for an external power supply. But beware the current you can get this way is very limitted... -Sren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 15: 1: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EAFD37B401 for ; Sun, 27 Oct 2002 15:01:02 -0800 (PST) Received: from tesla.foo.is (tesla.reverse-bias.org [217.151.166.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78F6E43E3B for ; Sun, 27 Oct 2002 15:01:01 -0800 (PST) (envelope-from baldur@foo.is) Received: from there (eniac.foo.is [192.168.1.25]) by tesla.foo.is (Postfix) with SMTP id 3BD9DAB93; Sun, 27 Oct 2002 23:00:49 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" From: Baldur Gislason To: Ronald G Minnich Subject: Re: Show me the light Date: Sun, 27 Oct 2002 23:00:48 +0000 X-Mailer: KMail [version 1.3.2] References: In-Reply-To: Cc: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20021027230049.3BD9DAB93@tesla.foo.is> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have powered leds from the parallel port, there's about 10mA of current available on each data pin without destroying anything. so I wired 8 leds, each with a 330 ohm series resistor, no external power supply. Baldur On Sunday 27 October 2002 22:48, you wrote: > On Mon, 28 Oct 2002 .@babolo.ru wrote: > > As far as I remember, there is open collector output > > on parallel port, so your wish impossible %-) > > oops, I forgot that little deal. Yup, you need a pullup. > > you can get PP relay modules for not much. > > ron > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 15:23:20 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 622B337B401; Sun, 27 Oct 2002 15:23:19 -0800 (PST) Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 053B843E42; Sun, 27 Oct 2002 15:23:19 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0347.cvx22-bradley.dialup.earthlink.net ([209.179.199.92] helo=mindspring.com) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 185wkX-0002RP-00; Sun, 27 Oct 2002 15:23:17 -0800 Message-ID: <3DBC7519.251B5C99@mindspring.com> Date: Sun, 27 Oct 2002 15:22:01 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Wilko Bulte Cc: John Baldwin , hackers@FreeBSD.ORG Subject: Re: Getting ACPI to work on -stable References: <20021024223256.A5488@freebie.xs4all.nl> <20021024231118.A5705@freebie.xs4all.nl> <20021027221048.A1187@freebie.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > > > #0 dumpsys () at ../../kern/kern_shutdown.c:487 > > #1 0xc015a5dd in db_fncall (dummy1=0, dummy2=0, dummy3=0, > > While playing with the laptop it proved that roughly all power events > lead to the panic. Like running the battery flat for example :) > It panics just before it gets killed because of lack of power. Most likely, there is a BIOS data area that is inaccessible to the BIOS code that gets invoked as a result of the interrupt, since most of the control stuff is implemented as BIOS traps, especially for the cheap-o processors, but also because you have to make the BIOS match the hardware implementation, and those vary widely. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 15:51:29 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C592B37B401 for ; Sun, 27 Oct 2002 15:51:27 -0800 (PST) Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F89343E88 for ; Sun, 27 Oct 2002 15:51:27 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0347.cvx22-bradley.dialup.earthlink.net ([209.179.199.92] helo=mindspring.com) by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 185xBk-0001ZY-00; Sun, 27 Oct 2002 15:51:24 -0800 Message-ID: <3DBC7BAD.BCB59AD7@mindspring.com> Date: Sun, 27 Oct 2002 15:50:05 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: David Nicholas Kayal , nbari@unixmexico.com, freebsd-hackers@FreeBSD.ORG Subject: Re: i am looking for a 5 volt signal References: <200210271919.g9RJJFEm091313@apollo.backplane.com> <3DBC42AF.C68F31B0@mindspring.com> <200210272207.g9RM76sX091839@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: > Huh. I would have expected you to use the current loop on the > phone line to power the dialer. There's a significant amount > of power available there, though you would have to isolate the > circuit since the common mode could be upwards of one or two > hundred volts. Telephone is 24 volts DC, which generally falls off to 18v at the customer permises. Ring is AC line voltage, to support mechanical ringers (e.g. 120v AC between ring, 24v DC between tip and ring). I worked as a lineman on private phone systems starting around age 14. 8-). > You could use an SCR but linear regulators are far, far better > (a little 3-pin TO92 package linear regulator). And linear regulators > have overcurrent protection as well (for themselves, not for whatever > is powering them). It's fairly difficult to blow one up. My SCR suggestion was based on the idea that you wanted to switch lots of volts/amps using Vcc chip levels to do it. THere are actually two threads here now: doing that, and lighting up a small number of LEDs (mention hardware projects, and the EE hobbiest wannabes come out of teh woodwork to ask for circuits... 8-)). Here is a good beginning parallel port project site: LED: http://www.free-hosting.lt/stech/lights/lights.htm Relay: http://www.armory.com/~rstevew/Public/Tutor/SolidStateRelaysDIY.txt Or a kit you can buy, with schematics: http://www.u-net.com/epr/electron/issue2/feat0302.htm Or more serious prebuilt stuff: http://www.lptek.com/io.htm And here is a wider selection, that has parallel port and serial port projects: http://ourworld.compuserve.com/homepages/Bill_Bowden/ ...and I'm disclaiming any responsibility, if you cook something with any of this... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 15:54:55 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F56B37B401 for ; Sun, 27 Oct 2002 15:54:54 -0800 (PST) Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B94B43E6E for ; Sun, 27 Oct 2002 15:54:54 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0347.cvx22-bradley.dialup.earthlink.net ([209.179.199.92] helo=mindspring.com) by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 185xEu-0005YG-00; Sun, 27 Oct 2002 15:54:40 -0800 Message-ID: <3DBC7C71.CCD4FE35@mindspring.com> Date: Sun, 27 Oct 2002 15:53:21 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Baldur Gislason Cc: Ronald G Minnich , freebsd-hackers@freebsd.org Subject: Re: Show me the light References: <20021027230049.3BD9DAB93@tesla.foo.is> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Baldur Gislason wrote: > I have powered leds from the parallel port, there's about 10mA of current > available on each data pin without destroying anything. so I wired 8 leds, > each with a 330 ohm series resistor, no external power supply. Use 470 ohm; your chip will last longer with all bits lit. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 16:38: 2 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D49937B401 for ; Sun, 27 Oct 2002 16:38:01 -0800 (PST) Received: from blackbox.yayproductions.com (h-66-166-17-53.SNVACAID.covad.net [66.166.17.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00D9943E8A for ; Sun, 27 Oct 2002 16:37:59 -0800 (PST) (envelope-from davek@saturn5.com) Received: from localhost (davek@localhost) by blackbox.yayproductions.com (8.11.6/8.11.3) with ESMTP id g9S0VkG01095 for ; Sun, 27 Oct 2002 16:31:46 -0800 (PST) (envelope-from davek@saturn5.com) X-Authentication-Warning: blackbox.yayproductions.com: davek owned process doing -bs Date: Sun, 27 Oct 2002 16:31:46 -0800 (PST) From: David Nicholas Kayal X-X-Sender: davek@blackbox.yayproductions.com To: freebsd-hackers@freebsd.org Subject: Programming the Parallel Port using ppi. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've updated the program to read as thus: #include #include #include #include int main() { int fd; u_int8_t val; fd = open("/dev/ppi0", O_RDWR); val = 0xff; while(1) { ioctl(fd, PPISDATA, &val); ioctl(fd, PPIGCTRL, &val); val |= STROBE; ioctl(fd, PPISCTRL, &val); val &= ~STROBE; ioctl(fd, PPISCTRL, &val); } } I have tried to test the output of pins 2 through 9, with a voltmeter, using pin 25 as the ground pin. Nothing registered. I tried again to use the LED, but that did not register anything as well. I am thinking of putting a 1k ohm resister on the positive side of the LED. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 18: 0: 2 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80D5237B401 for ; Sun, 27 Oct 2002 18:00:01 -0800 (PST) Received: from bogslab.ucdavis.edu (bogslab.ucdavis.edu [169.237.68.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11D7543E6E for ; Sun, 27 Oct 2002 18:00:01 -0800 (PST) (envelope-from greg@bogslab.ucdavis.edu) Received: from thistle.bogs.org (thistle.bogs.org [198.137.203.61]) by bogslab.ucdavis.edu (8.9.3/8.9.3) with ESMTP id RAA35581 for ; Sun, 27 Oct 2002 17:59:49 -0800 (PST) (envelope-from greg@bogslab.ucdavis.edu) Received: from thistle.bogs.org (localhost [127.0.0.1]) by thistle.bogs.org (8.11.3/8.11.3) with ESMTP id g9S1tiQ69311 for ; Sun, 27 Oct 2002 17:55:45 -0800 (PST) (envelope-from greg@thistle.bogs.org) Message-Id: <200210280155.g9S1tiQ69311@thistle.bogs.org> To: hackers@FreeBSD.ORG X-To: David Nicholas Kayal X-Sender: owner-freebsd-hackers@FreeBSD.ORG Subject: Re: Programming the Parallel Port using ppi. In-reply-to: Your message of "Sun, 27 Oct 2002 16:31:46 PST." Reply-To: gkshenaut@ucdavis.edu Date: Sun, 27 Oct 2002 17:55:44 -0800 From: Greg Shenaut Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , David Nicholas Kayal cleopede: > val = 0xff; For this kind of testing, it is sometimes useful to use a value like 0xaa or 0x55, and probe the adjacent lines--don't forget that if there is inversion going on, 0xff will produce all 0v outputs. Just a random thought, it may not help here, but aa/ff are generally more useful than all 1's or all 0's. Greg Shenaut To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 19: 9:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A2AB37B401 for ; Sun, 27 Oct 2002 19:09:50 -0800 (PST) Received: from blackbox.yayproductions.com (h-66-166-17-53.SNVACAID.covad.net [66.166.17.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AD8B43E77 for ; Sun, 27 Oct 2002 19:09:50 -0800 (PST) (envelope-from davek@saturn5.com) Received: from localhost (davek@localhost) by blackbox.yayproductions.com (8.11.6/8.11.3) with ESMTP id g9S33Yk01236; Sun, 27 Oct 2002 19:03:34 -0800 (PST) (envelope-from davek@saturn5.com) X-Authentication-Warning: blackbox.yayproductions.com: davek owned process doing -bs Date: Sun, 27 Oct 2002 19:03:34 -0800 (PST) From: David Nicholas Kayal X-X-Sender: davek@blackbox.yayproductions.com To: gkshenaut@ucdavis.edu Cc: hackers@FreeBSD.ORG Subject: Re: Programming the Parallel Port using ppi. In-Reply-To: <200210280155.g9S1tiQ69311@thistle.bogs.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Shouldn't 0xff result in 5v outputs? On Sun, 27 Oct 2002, Greg Shenaut wrote: > In message , David Nicholas Kayal cleopede: > > val = 0xff; > > For this kind of testing, it is sometimes useful to use a value > like 0xaa or 0x55, and probe the adjacent lines--don't forget that > if there is inversion going on, 0xff will produce all 0v outputs. > Just a random thought, it may not help here, but aa/ff are generally > more useful than all 1's or all 0's. > > Greg Shenaut > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 19:35:25 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7724737B401 for ; Sun, 27 Oct 2002 19:35:24 -0800 (PST) Received: from 002.216-123-229-0.interbaun.com (002.216-123-229-0.interbaun.com [216.123.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B738843E3B for ; Sun, 27 Oct 2002 19:35:22 -0800 (PST) (envelope-from soralx@cydem.zp.ua) Received: from 254.216-123-229-0.interbaun.com ([192.168.0.3]) by 002.216-123-229-0.interbaun.com (8.11.6/8.11.6) with ESMTP id g9S3ZKi00214 for ; Sun, 27 Oct 2002 20:35:21 -0700 (MST) (envelope-from soralx@cydem.zp.ua) Content-Type: text/plain; charset="iso-8859-1" From: To: freebsd-hackers@FreeBSD.ORG Subject: Re: i am looking for a 5 volt signal Date: Sun, 27 Oct 2002 19:35:12 -0700 X-Mailer: KMail [version 1.4] References: <3DBC42AF.C68F31B0@mindspring.com> <200210272207.g9RM76sX091839@apollo.backplane.com> In-Reply-To: <200210272207.g9RM76sX091839@apollo.backplane.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200210271935.12396.soralx@cydem.zp.ua> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > In anycase, I can only concur on the danger of ganging the parallel > power output bits. A single chip is driving those outputs and is > almost certainly not rated to deal with a maximal current draw from > all of them at once for long periods of time. It could fry. The output signals don't go straight from the chip - do they? I've seen few KOhms resistors on most boards for each output pin. 27.10.2002; 19:32:00 [SorAlx] http://cydem.zp.ua/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 19:41:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFC0B37B401 for ; Sun, 27 Oct 2002 19:41:41 -0800 (PST) Received: from bogslab.ucdavis.edu (bogslab.ucdavis.edu [169.237.68.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6229443E4A for ; Sun, 27 Oct 2002 19:41:41 -0800 (PST) (envelope-from greg@bogslab.ucdavis.edu) Received: from thistle.bogs.org (thistle.bogs.org [198.137.203.61]) by bogslab.ucdavis.edu (8.9.3/8.9.3) with ESMTP id TAA35863 for ; Sun, 27 Oct 2002 19:41:39 -0800 (PST) (envelope-from greg@bogslab.ucdavis.edu) Received: from thistle.bogs.org (localhost [127.0.0.1]) by thistle.bogs.org (8.11.3/8.11.3) with ESMTP id g9S3bYQ69540 for ; Sun, 27 Oct 2002 19:37:35 -0800 (PST) (envelope-from greg@thistle.bogs.org) Message-Id: <200210280337.g9S3bYQ69540@thistle.bogs.org> To: hackers@FreeBSD.ORG X-To: David Nicholas Kayal X-Sender: owner-freebsd-hackers@FreeBSD.ORG Subject: Re: Programming the Parallel Port using ppi. In-reply-to: Your message of "Sun, 27 Oct 2002 19:03:34 PST." Reply-To: gkshenaut@ucdavis.edu Date: Sun, 27 Oct 2002 19:37:34 -0800 From: Greg Shenaut Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , David Nicholas Kayal cleopede: >Shouldn't 0xff result in 5v outputs? Sure, but in general you may get more information by using an alternating bit pattern (aa/55), that's all. Can you print from this port? Greg Shenaut To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 19:44:57 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4C0537B401 for ; Sun, 27 Oct 2002 19:44:56 -0800 (PST) Received: from blackbox.yayproductions.com (h-66-166-17-53.SNVACAID.covad.net [66.166.17.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19E9843E77 for ; Sun, 27 Oct 2002 19:44:56 -0800 (PST) (envelope-from davek@saturn5.com) Received: from localhost (davek@localhost) by blackbox.yayproductions.com (8.11.6/8.11.3) with ESMTP id g9S3cf601282; Sun, 27 Oct 2002 19:38:41 -0800 (PST) (envelope-from davek@saturn5.com) X-Authentication-Warning: blackbox.yayproductions.com: davek owned process doing -bs Date: Sun, 27 Oct 2002 19:38:41 -0800 (PST) From: David Nicholas Kayal X-X-Sender: davek@blackbox.yayproductions.com To: gkshenaut@ucdavis.edu Cc: hackers@FreeBSD.ORG Subject: Re: Programming the Parallel Port using ppi. In-Reply-To: <200210280337.g9S3bYQ69540@thistle.bogs.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I don't have a printer, so I am not sure. On Sun, 27 Oct 2002, Greg Shenaut wrote: > In message , David Nicholas Kayal cleopede: > >Shouldn't 0xff result in 5v outputs? > > Sure, but in general you may get more information by using an > alternating bit pattern (aa/55), that's all. > > Can you print from this port? > > Greg Shenaut > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 20: 2:21 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8342D37B401 for ; Sun, 27 Oct 2002 20:02:20 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA8D443E3B for ; Sun, 27 Oct 2002 20:02:19 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.3/8.12.3) with ESMTP id g9S42Ipk026143; Sun, 27 Oct 2002 21:02:18 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 27 Oct 2002 21:01:25 -0700 (MST) Message-Id: <20021027.210125.27780229.imp@bsdimp.com> To: davek@saturn5.com Cc: gkshenaut@ucdavis.edu, hackers@FreeBSD.ORG Subject: Re: Programming the Parallel Port using ppi. From: "M. Warner Losh" In-Reply-To: References: <200210280155.g9S1tiQ69311@thistle.bogs.org> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: David Nicholas Kayal writes: : Shouldn't 0xff result in 5v outputs? Depends on of the pins are negative logic, now doesn't it :-) And most Parallel ports I've measured clock in at about 3.3V. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 21:22:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C96137B401 for ; Sun, 27 Oct 2002 21:22:12 -0800 (PST) Received: from simmts1-srv.bellnexxia.net (simmts1.bellnexxia.net [206.47.199.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A133443E6E for ; Sun, 27 Oct 2002 21:22:11 -0800 (PST) (envelope-from ian@damnit.org) Received: from damnit.org ([142.177.49.14]) by simmts1-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20021028052159.VCTB27043.simmts1-srv.bellnexxia.net@damnit.org> for ; Mon, 28 Oct 2002 00:21:59 -0500 Message-ID: <3DBCC9EE.8000505@damnit.org> Date: Mon, 28 Oct 2002 01:23:58 -0400 From: Ian Campbell User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4.1) Gecko/20020314 Netscape6/6.2.2 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Increasing KVM Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG How exactly would I go about increasing KVM? I tried bumping up KVA_PAGES from 256 to 260, but all that did was cause page faults whenever apache (or fatboy, like in this case) was started... here's the error from /var/log/messages Oct 24 14:51:12 qt20 /kernel: Oct 24 14:51:12 qt20 /kernel: Oct 24 14:51:12 qt20 /kernel: Fatal trap 12: page fault while in kernel mode Oct 24 14:51:12 qt20 /kernel: mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 Oct 24 14:51:12 qt20 /kernel: fault virtual address = 0xafcaae5c Oct 24 14:51:12 qt20 /kernel: fault code = supervisor write, page not present Oct 24 14:51:12 qt20 /kernel: instruction pointer = 0x8:0xb0257d11 Oct 24 14:51:12 qt20 /kernel: stack pointer = 0x10:0xe590ee40 Oct 24 14:51:12 qt20 /kernel: frame pointer = 0x10:0xe590ee4c Oct 24 14:51:12 qt20 /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Oct 24 14:51:12 qt20 /kernel: = DPL 0, pres 1, def32 1, gran 1 Oct 24 14:51:12 qt20 /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Oct 24 14:51:12 qt20 /kernel: current process = 250 (fatboy) Oct 24 14:51:12 qt20 /kernel: interrupt mask = none <- SMP: XXX Oct 24 14:51:12 qt20 /kernel: trap number = 12 Oct 24 14:51:12 qt20 /kernel: panic: page fault Oct 24 14:51:12 qt20 /kernel: mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 Oct 24 14:51:12 qt20 /kernel: boot() called on cpu#0 Oct 24 14:51:12 qt20 /kernel: Oct 24 14:51:12 qt20 /kernel: syncing disks... 15 3 I remember reading somewhere that NKPT should also be increased if you're going to fiddle with KVA_PAGES, is that true? Clearly there's something I'm not doing, I remember reading about people cranking KVA_PAGES up to 768. --Ian. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 21:39:20 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F3B637B401 for ; Sun, 27 Oct 2002 21:39:19 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B12F643E42 for ; Sun, 27 Oct 2002 21:39:18 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.5/8.12.5) with ESMTP id g9S5dFFC093584; Sun, 27 Oct 2002 21:39:15 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.5/8.12.5/Submit) id g9S5dFAR093583; Sun, 27 Oct 2002 21:39:15 -0800 (PST) (envelope-from dillon) Date: Sun, 27 Oct 2002 21:39:15 -0800 (PST) From: Matthew Dillon Message-Id: <200210280539.g9S5dFAR093583@apollo.backplane.com> To: "M. Warner Losh" Cc: davek@saturn5.com, gkshenaut@ucdavis.edu, hackers@FreeBSD.ORG Subject: Re: Programming the Parallel Port using ppi. References: <200210280155.g9S1tiQ69311@thistle.bogs.org> <20021027.210125.27780229.imp@bsdimp.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Depends on of the pins are negative logic, now doesn't it :-) : :And most Parallel ports I've measured clock in at about 3.3V. : :Warner That sounds about right. I found a web page with the circuit for a TTL output. http://www.play-hookey.com/digital/electronics/ttl_gates.html If you go down to the bottom you'll see the circuit. A TTL 'high' is +5V through a 130 ohm resistor through a transitor (0.7V drop), through a diode (another 0.7V drop) = 5 - 1.4 = 3.6V, but it's actually less because there is current through the transistor, causing an additional drop through the 130ohm resistor. The real problem is the 130 ohm resistor. Each 1 mA you pull on the output will drop the voltage another 0.13V, which means you can't pull much current out of the output (and also that the output is nowhere near 5 volts even if you don't pull any current out of it). A TTL output is much better pulling to ground (sinking current rather then sourcing it). As you can see, when the output is a zero the bottom transistor is turned on and that is basically a direct connection to ground through a 0.7V drop, with no resistor (though there is an equivalent resistance due to the transitor), so TTL can pull down to 0.7V or so, usually at least 20mA. - Now, if this were a CMOS output you basically have two symmetrical FETs: http://www.play-hookey.com/digital/electronics/cmos_gates.html Which have an equivalent resistance of 50 ohms typically (well, the web page says 200 ohms but I think it's more around 50 for HCMOS). So a CMOS 1 is essentially 50 ohms to +V and a CMOS 0 is essentially 50 ohms to ground. This is the nice thing about CMOS... the lowest voltage is basically ground (not 0.7V), and the highest output voltage is basically +V (e.g. 5V rather then 3.3-3.6V). But a parallel port output is not a [H]CMOS output, it's a TTL output, which makes it a very poor power source. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 22:10:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7847E37B401 for ; Sun, 27 Oct 2002 22:10:41 -0800 (PST) Received: from saturn.bsdhome.com (rdu25-2-113.nc.rr.com [24.25.2.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id C202843E3B for ; Sun, 27 Oct 2002 22:10:40 -0800 (PST) (envelope-from bsd@bsdhome.com) Received: from neutrino.bsdhome.com (jupiter [192.168.220.13]) by saturn.bsdhome.com (8.12.6/8.12.6) with ESMTP id g9S6Adg0013625; Mon, 28 Oct 2002 01:10:39 -0500 (EST) (envelope-from bsd@bsdhome.com) Received: from neutrino.bsdhome.com (localhost [127.0.0.1]) by neutrino.bsdhome.com (8.12.6/8.12.6) with ESMTP id g9S6AYcP072158; Mon, 28 Oct 2002 01:10:34 -0500 (EST) (envelope-from bsd@neutrino.bsdhome.com) Received: (from bsd@localhost) by neutrino.bsdhome.com (8.12.6/8.12.6/Submit) id g9S6AXk0072157; Mon, 28 Oct 2002 01:10:33 -0500 (EST) Date: Mon, 28 Oct 2002 01:10:33 -0500 From: Brian Dean To: David Nicholas Kayal Cc: freebsd-hackers@FreeBSD.org Subject: Re: Programming the Parallel Port using ppi. Message-ID: <20021028061033.GA65546@neutrino.bsdhome.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Oct 27, 2002 at 04:31:46PM -0800, David Nicholas Kayal wrote: > #include > #include > #include > #include > > int main() > { > int fd; > u_int8_t val; > > fd = open("/dev/ppi0", O_RDWR); > val = 0xff; > while(1) > { > ioctl(fd, PPISDATA, &val); > ioctl(fd, PPIGCTRL, &val); > val |= STROBE; > ioctl(fd, PPISCTRL, &val); > val &= ~STROBE; > ioctl(fd, PPISCTRL, &val); > } > } You should really check your return values. The parallel port is not writeable by default, so unless you've changed it, or are running as root, your program is most likely failing to even open it, but you're not noticing because you aren't checking your return codes. -Brian -- Brian Dean bsd@FreeBSD.org bsd@bsdhome.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 27 23:48:52 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B70F437B401 for ; Sun, 27 Oct 2002 23:48:50 -0800 (PST) Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E54D43E3B for ; Sun, 27 Oct 2002 23:48:50 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0035.cvx40-bradley.dialup.earthlink.net ([216.244.42.35] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1864dk-0005Gc-00; Sun, 27 Oct 2002 23:48:48 -0800 Message-ID: <3DBCEB91.660A44FC@mindspring.com> Date: Sun, 27 Oct 2002 23:47:29 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ian Campbell Cc: freebsd-hackers@freebsd.org Subject: Re: Increasing KVM References: <3DBCC9EE.8000505@damnit.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ian Campbell wrote: > How exactly would I go about increasing KVM? I tried bumping up > KVA_PAGES from 256 to 260, but all that did was cause page faults > whenever apache (or fatboy, like in this case) was started... here's the > error from /var/log/messages [ ... ] > I remember reading somewhere that NKPT should also be increased if > you're going to fiddle with KVA_PAGES, is that true? Clearly there's > something I'm not doing, I remember reading about people cranking > KVA_PAGES up to 768. You only need to make additional changes if you are running a version of FreeBSD prior to 4.5; otherwise, just changing the KVA_PAGES should be enough. If you have a kernel where changing NKPT is relevent, then you are running a version before 4.5-RELEASE, and, and KVA_PAGES should have no effect whatsoever on the KVA size (it will be ignored, much as if you had used: option FRITZ_THE_CAT=260 (i.e. you can set any variable you want, and if no one looks at it, no one cares what you set it to). Prior to 4.6, Matt Dillon's autosizing patches had not yet been committed for KVA usage. On systems with large amounts of RAM, this meant that the amount of KVA space for page tables grew too large too quickly. Subsequent to the 4.6 release, there were additional changes for autotuning. Therefore you should be running at least 4.7-RELEASE, if you are messing with this at all. You haven't said whether you were running -current; everyone will assume that you are not, since you posted to the wrong mailing list for -current kernel issues (-hackers). One thing that would help is a traceback of why the fault was happening, which you haven't provided, since you only provided the fact that you were having a fault, and a meaningless address and other information, which is useless without the kernel and source code you are using. So first thing, you should get a system dump, run the debugger against a debug kernel image, and get a traceback. It will give you information which you will need to have for anyone to answer your question. My guess is that you are using up all available physical memory for backing KVA, and then crashing in a page fault attempting to trap to allocate physical backing pages for KVA space you've allocated for some reason, but have not yet used. This happens a lot these days in -current, because the wrong map is being used for preallocation of space with the new allocator (see -current list archived for recent patches for this, if you are running -current). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 3:49:34 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A23737B401 for ; Mon, 28 Oct 2002 03:49:33 -0800 (PST) Received: from semantico.com (choke.semantico.com [212.74.15.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F7A443E3B for ; Mon, 28 Oct 2002 03:49:32 -0800 (PST) (envelope-from dom@semantico.com) Received: from semantico.com (cassia.dyn.rp.lan [192.168.1.236]) by semantico.com (Postfix) with ESMTP id C0BFD32006A; Mon, 28 Oct 2002 11:49:22 +0000 (GMT) Message-ID: <3DBD2442.5050602@semantico.com> Date: Mon, 28 Oct 2002 11:49:22 +0000 From: Dominic Mitchell Organization: Semantico User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-gb, sv, en MIME-Version: 1.0 To: Baldur Gislason Cc: Robert Withrow , freebsd-hackers@FreeBSD.ORG Subject: Re: Suggestion: usbd.conf uses rc.conf for options References: <20021027193323.C76EA32B3@ns1.rwwa.com> <20021027194710.6AA69AB93@tesla.foo.is> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Baldur Gislason wrote: > I agree, that would be a nice feature in usbd, but a workaround to gain the same functionality would be: > > attach "/usr/sbin/moused `/usr/bin/perl -e 'while(<>) { $foo = $_ . $foo; } if($foo =~ /^moused_flags="(.*?)"$/im) { print $1; }' < /etc/rc.conf` -p /dev/${DEVNAME} -I /var/run/moused.${DEVNAME}.pid" Why not just: attach ". /etc/rc.conf; /usr/bin/moused ${moused_flags} -p /dev/${DEVNAME} -I /var/run/moused.${DEVNAME}.pid" (untested) -Dom -- | Semantico: creators of major online resources | | URL: http://www.semantico.com/ | | Tel: +44 (1273) 722222 | | Address: 33 Bond St., Brighton, Sussex, BN1 1RD, UK. | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 3:58: 5 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E84C437B401 for ; Mon, 28 Oct 2002 03:58:03 -0800 (PST) Received: from straylight.ringlet.net (office.sbnd.net [217.75.140.130]) by mx1.FreeBSD.org (Postfix) with SMTP id 432C643E7B for ; Mon, 28 Oct 2002 03:58:00 -0800 (PST) (envelope-from roam@ringlet.net) Received: (qmail 25542 invoked by uid 1000); 28 Oct 2002 11:57:22 -0000 Date: Mon, 28 Oct 2002 13:57:22 +0200 From: Peter Pentchev To: Dominic Mitchell Cc: Baldur Gislason , Robert Withrow , freebsd-hackers@FreeBSD.ORG Subject: Re: Suggestion: usbd.conf uses rc.conf for options Message-ID: <20021028115722.GB17000@straylight.oblivion.bg> Mail-Followup-To: Dominic Mitchell , Baldur Gislason , Robert Withrow , freebsd-hackers@FreeBSD.ORG References: <20021027193323.C76EA32B3@ns1.rwwa.com> <20021027194710.6AA69AB93@tesla.foo.is> <3DBD2442.5050602@semantico.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CUfgB8w4ZwR/yMy5" Content-Disposition: inline In-Reply-To: <3DBD2442.5050602@semantico.com> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --CUfgB8w4ZwR/yMy5 Content-Type: text/plain; charset=windows-1251 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 28, 2002 at 11:49:22AM +0000, Dominic Mitchell wrote: > Baldur Gislason wrote: > >I agree, that would be a nice feature in usbd, but a workaround to gain= =20 > >the same functionality would be: > > > >attach "/usr/sbin/moused `/usr/bin/perl -e 'while(<>) { $foo =3D $_ . $f= oo;=20 > >} if($foo =3D~ /^moused_flags=3D"(.*?)"$/im) { print $1; }' < /etc/rc.co= nf` -p=20 > >/dev/${DEVNAME} -I /var/run/moused.${DEVNAME}.pid" >=20 > Why not just: >=20 > attach ". /etc/rc.conf; /usr/bin/moused ${moused_flags} -p=20 > /dev/${DEVNAME} -I /var/run/moused.${DEVNAME}.pid" >=20 > (untested) This had better be ". /etc/defaults/rc.conf; source_rc_confs; ..." :) I have been thinking for quite some time of writing a little utility that parses various configuration file mechanisms and allows the administrator to specify which config mechanism to use for which program. I have a simple design in mind, which would allow direct variable setting, use of /etc/rc.conf, use of other configuration files, use of daemontools-style envdirs, and a couple of others, but so far, there has been no time to actually start writing a simple proof-of-concept thing. Funny now, the timing; I was thinking of writing up a simple rcenv(1) today or tomorrow, and then I saw this thread :) G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 No language can express every thought unambiguously, least of all this one. --CUfgB8w4ZwR/yMy5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE9vSYi7Ri2jRYZRVMRApvpAKC5xbu+5HtAbtbOJBgk4uhAnzyOFgCfVOjM cAVCpBuMRSIAoo5rpWYKZL8= =yELm -----END PGP SIGNATURE----- --CUfgB8w4ZwR/yMy5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 4: 4:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C2C237B401; Mon, 28 Oct 2002 04:04:58 -0800 (PST) Received: from hotmail.com (f31.pav2.hotmail.com [64.4.37.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5773943E77; Mon, 28 Oct 2002 04:04:58 -0800 (PST) (envelope-from sepehr_soh@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 28 Oct 2002 04:04:58 -0800 Received: from 213.217.52.210 by pv2fd.pav2.hotmail.msn.com with HTTP; Mon, 28 Oct 2002 12:04:58 GMT X-Originating-IP: [213.217.52.210] From: "sepehr sohrabi" To: freebsd-net@freebsd.org Subject: spoofing source code in kernel Date: Mon, 28 Oct 2002 15:34:58 +0330 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 28 Oct 2002 12:04:58.0290 (UTC) FILETIME=[3C51D120:01C27E7A] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi list Anyone has source code for spoofing (in kernel) for all input Tcp/IP packets .For any TCP/IP packet recieve it creates an ACK for it . someThing like spoofing GW CLIENT <-----> GW <-------> server connections are spoofed THANX _________________________________________________________________ Broadband?Dial-up? Get reliable MSN Internet Access. http://resourcecenter.msn.com/access/plans/default.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 4: 9:22 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A858D37B401 for ; Mon, 28 Oct 2002 04:09:20 -0800 (PST) Received: from infinitive.futureperfectcorporation.com (infinitive.futureperfectcorporation.com [196.25.137.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id F239D43E4A for ; Mon, 28 Oct 2002 04:09:17 -0800 (PST) (envelope-from nbm@gerund.futureperfectcorporation.com) Received: (qmail 41181 invoked by uid 0); 28 Oct 2002 12:08:56 -0000 Received: from gerund.futureperfectcorporation.com (196.25.137.65) by infinitive.futureperfectcorporation.com with DES-CBC3-SHA encrypted SMTP; 28 Oct 2002 12:08:56 -0000 Received: (qmail 51244 invoked by uid 1001); 28 Oct 2002 12:11:36 -0000 Date: Mon, 28 Oct 2002 14:11:36 +0200 From: Neil Blakey-Milner To: Peter Pentchev Cc: Dominic Mitchell , Baldur Gislason , Robert Withrow , freebsd-hackers@FreeBSD.ORG Subject: Re: Suggestion: usbd.conf uses rc.conf for options Message-ID: <20021028121136.GA51141@mithrandr.moria.org> References: <20021027193323.C76EA32B3@ns1.rwwa.com> <20021027194710.6AA69AB93@tesla.foo.is> <3DBD2442.5050602@semantico.com> <20021028115722.GB17000@straylight.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021028115722.GB17000@straylight.oblivion.bg> User-Agent: Mutt/1.3.27i Organization: iTouch Technology and Architectural Services X-Operating-System: FreeBSD 4.3-RELEASE i386 X-URL: http://mithrandr.moria.org/nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon 2002-10-28 (13:57), Peter Pentchev wrote: > This had better be ". /etc/defaults/rc.conf; source_rc_confs; ..." :) > > I have been thinking for quite some time of writing a little utility > that parses various configuration file mechanisms and allows the > administrator to specify which config mechanism to use for which > program. I have a simple design in mind, which would allow direct > variable setting, use of /etc/rc.conf, use of other configuration files, > use of daemontools-style envdirs, and a couple of others, but so far, > there has been no time to actually start writing a simple > proof-of-concept thing. Funny now, the timing; I was thinking of > writing up a simple rcenv(1) today or tomorrow, and then I saw this > thread :) Go for it (please!). Check out: Subject: non-variables in rc.conf (Re: proposed code: automatic setting of hostname from MAC address) Message-ID: <20020410091703.GA47576@mithrandr.moria.org> On arch mailing list: <<<=== Abstracting the configuration away from "shell scripts and functions" would allow us to pull the configuration in from other locations in the "backend". The one basic example I did perform was in the order of (replace \ns with real enters): eval `echo 'g/^[:space:]*$/d\ng/^#/d\ng/$/s//;/\ng/./' | ed -s \!'cat /etc/rc.alternate.conf'` Anyway, assume that we can get our network configured beforehand, and we can then use ldap, NIS, or whatever (netinfo?) to get our configuration. ===>>> When we can finally get rid of non-variables in the configuration system we no longer rely on 'sh', and we can read configuration using any programming language, and/or (even better) back the configuration up with LDAP or whatever. Neil -- Neil Blakey-Milner nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 5:10:27 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3270937B401 for ; Mon, 28 Oct 2002 05:10:26 -0800 (PST) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4951743E42 for ; Mon, 28 Oct 2002 05:10:24 -0800 (PST) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 6DE91534E; Mon, 28 Oct 2002 14:10:16 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Ian Campbell Cc: freebsd-hackers@freebsd.org Subject: Re: Increasing KVM References: <3DBCC9EE.8000505@damnit.org> From: Dag-Erling Smorgrav Date: Mon, 28 Oct 2002 14:10:16 +0100 In-Reply-To: <3DBCC9EE.8000505@damnit.org> (Ian Campbell's message of "Mon, 28 Oct 2002 01:23:58 -0400") Message-ID: Lines: 8 User-Agent: Gnus/5.090007 (Oort Gnus v0.07) Emacs/21.2 (i386--freebsd) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ian Campbell writes: > How exactly would I go about increasing KVM? Read the FAQ. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 5:47:12 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E9B137B401 for ; Mon, 28 Oct 2002 05:47:10 -0800 (PST) Received: from firehouse.net (dsl-64-130-18-61.telocity.com [64.130.18.61]) by mx1.FreeBSD.org (Postfix) with SMTP id 8982243E4A for ; Mon, 28 Oct 2002 05:47:09 -0800 (PST) (envelope-from alan@clegg.com) Received: (qmail 7487 invoked by uid 85); 28 Oct 2002 13:47:01 -0000 Date: Mon, 28 Oct 2002 08:46:58 -0500 To: freebsd-hackers@freebsd.org Subject: Re: Suggestion: usbd.conf uses rc.conf for options Message-ID: <20021028134658.GB6821@shazam.wetworks.org> References: <20021027193323.C76EA32B3@ns1.rwwa.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gatW/ieO32f1wygP" Content-Disposition: inline In-Reply-To: <20021027193323.C76EA32B3@ns1.rwwa.com> User-Agent: Mutt/1.4i From: "Alan B. Clegg" Mail-Followup-To: alan-dated-1036244818.c7ce83@clegg.com, freebsd-hackers@freebsd.org X-Delivery-Agent: TMDA/0.52 (Python 2.2 on FreeBSD/i386) X-TMDA-Fingerprint: 8m8/uIs5mLAG+5pFdzK/QiJgoVc X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --gatW/ieO32f1wygP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Unless the network is lying to me again, Robert Withrow said:=20 > I notice that usbd.conf has this for the mouse device: [..] I have a laptop that uses different moused_flags depending on the mouse being built-in or USB. I hate to say it, but perhaps introducing=20 usb_moused_flags into rc.conf? AlanC --=20 | Alan Clegg | Networks | Security | UNIX | 802.11 |=20 "you just have to be smarter than what you're working on." - Scott Lauren --gatW/ieO32f1wygP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE9vT/SyJP8xSfQVdsRAnp7AJ9vnT24TgH9GFpwO1nUgM4blXAD0ACfePh0 uOLUHhGxrz2oUfTpTd7U2R4= =vl7e -----END PGP SIGNATURE----- --gatW/ieO32f1wygP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 5:56:45 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98B2E37B401 for ; Mon, 28 Oct 2002 05:56:43 -0800 (PST) Received: from littleboy.csh.rit.edu (littleboy.csh.rit.edu [129.21.60.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5AFF43E42 for ; Mon, 28 Oct 2002 05:56:42 -0800 (PST) (envelope-from sunday@csh.rit.edu) Received: from fury.csh.rit.edu (fury.csh.rit.edu [129.21.60.5]) by littleboy.csh.rit.edu (Postfix) with ESMTP id B7469866A; Mon, 28 Oct 2002 08:56:36 -0500 (EST) Received: by fury.csh.rit.edu (Postfix, from userid 38501) id 13AAE2E384; Mon, 28 Oct 2002 08:56:35 -0500 (EST) Date: Mon, 28 Oct 2002 08:56:35 -0500 From: Joe Sunday To: David Nicholas Kayal Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: i am looking for a 5 volt signal Message-ID: <20021028135635.GA28293@csh.rit.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Operating-System: SunOS 5.8 (sun4u) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Oct 27, 2002 at 09:12:33AM -0800, David Nicholas Kayal wrote: > I'm looking for a 5 volt signal. > > I have wires plugged into pins 2 and 25 of the parallel port. > > I have written a small program: > > #include > #include > #include > > int main() > { > int fd; > while(1) > { > ioctl(fd, PPISDATA, 255); > } > } PPISDATA actually takes an int* argument. (The man page may be a tad confusing here.) Try int main() { int fd; int d = 255; fd = open( "/dev/ppi0", O_RDWR ); ioctl( fd, PPISDATA, &d ); return 0; } The port should hold the last value you send to it, there's no need to continually refresh it. --Joe -- Joe Sunday http://www.csh.rit.edu/~sunday/ Computer Science House, Rochester Inst. Of Technology To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 7:31:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A55137B401; Mon, 28 Oct 2002 07:31:49 -0800 (PST) Received: from mail.ubergeeks.com (lorax.ubergeeks.com [209.145.65.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92F6743E3B; Mon, 28 Oct 2002 07:31:48 -0800 (PST) (envelope-from adrian+freebsd-audit@ubergeeks.com) Received: from mail.ubergeeks.com (localhost [127.0.0.1]) by mail.ubergeeks.com (8.12.5/8.12.5) with ESMTP id g9SFVgel064168; Mon, 28 Oct 2002 10:31:42 -0500 (EST) (envelope-from adrian+freebsd-audit@ubergeeks.com) Received: from localhost (adrian@localhost) by mail.ubergeeks.com (8.12.5/8.12.5/Submit) with ESMTP id g9SFVfCq064165; Mon, 28 Oct 2002 10:31:42 -0500 (EST) (envelope-from adrian+freebsd-audit@ubergeeks.com) X-Authentication-Warning: lorax.ubergeeks.com: adrian owned process doing -bs Date: Mon, 28 Oct 2002 10:31:41 -0500 (EST) From: Adrian Filipi-Martin To: Juli Mallett Cc: Maxim Sobolev , Nate Lawson , , , Subject: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC In-Reply-To: <20021027010429.A90908@FreeBSD.org> Message-ID: <20021028102544.O64046-100000@lorax.ubergeeks.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 27 Oct 2002, Juli Mallett wrote: > * De: Maxim Sobolev [ Data: 2002-10-27 ] > [ Subjecte: Re: New kevent types: NOTE_STARTEXEC and NOTE_STOPEXEC ] > > On Sat, Oct 26, 2002 at 06:09:31PM -0700, Nate Lawson wrote: > > > On Thu, 24 Oct 2002, Maxim Sobolev wrote: > > > > Please review the patch, which adds two new types of events - > > > > NOTE_STARTEXEC and NOTE_STOPEXEC, that could be used to get > > > > notification when the image starts or stops executing. For example, it > > > > could be used to monitor that a daemon is up and running and notify > > > > administrator when for some reason in exits. I am running this code > > > > for more than a year now without any problems. > > > > > > > > Any comments and suggestions are welcome. > > > > > > Couldn't this just be done by init(8) and /etc/ttys? Or inetd? If you > > > want to write your own, couldn't you use waitpid()? Or a kevent() of > > > EVFILT_PROC with NOTE_EXIT/NOTE_FORK? I'm not sure I see the need for > > > this. > > > > EVFILT_PROC operates on pids, while NOTE_{START,STOP}EXEC operate on > > vnodes - it is the main difference. Currently, you can't reliably > > get a notification when kernes started executing some arbitrary > > executable from your fs. > > This is not a job for the kernel, I don't think. Implement it in userland > in terms of having the daemon write to a pidfile at startup, and have SIGUSR1 > make it tell the sender it's alive (using my sigq stuff this is trivial, just > send SIGUSR2 back), and periodically read the pidfile and try to communciate > with the daemon, and respawn it if it fails. This could be racey if done > poorly. However if you want this for *any* executable, rather than just > "some arbitrary executable" rather than some specific job, then while I wonder > how useful it is in a generic concept, the kq solution might be more > reasonable. > > Juli Mallett | FreeBSD: The Power To Serve Monitoring process health isn't nearly as intersting as being able to track system statistics for IDS purposes. STOP/START_EXEC tracking would make it much easier to profile a running system and then generate a statistical profile of what should normally be running. This cannot be accurately done outside the kernel. Adrian -- [ adrian@ubergeeks.com ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 9:59:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5CAC37B4BC; Mon, 28 Oct 2002 09:59:48 -0800 (PST) Received: from mta6.srv.hcvlny.cv.net (mta6.srv.hcvlny.cv.net [167.206.5.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4406143E8A; Mon, 28 Oct 2002 09:59:48 -0800 (PST) (envelope-from d9999@optonline.net) Received: from optonline.net (ool-18bd986b.dyn.optonline.net [24.189.152.107]) by mta6.srv.hcvlny.cv.net (iPlanet Messaging Server 5.2 HotFix 0.9 (built Jul 29 2002)) with SMTP id <0H4P00DMHDXKSD@mta6.srv.hcvlny.cv.net>; Mon, 28 Oct 2002 12:58:58 -0500 (EST) Date: Mon, 28 Oct 2002 12:59:00 +0000 (PM) From: lana Subject: info<<< To: awal@tworld.com Message-id: <0H4P00DYPDY9SD@mta6.srv.hcvlny.cv.net> X-Mailer: L.C. Enterprises - Email Extractor 2002 Content-transfer-encoding: 7BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi ,,your home based business opportunity sounds interesting .. got few questions pleasecall me 614-837-8112 thank..you LANA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 12:35:47 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E29937B401; Mon, 28 Oct 2002 12:35:46 -0800 (PST) Received: from nebula.wanadoo.fr (ca-sqy-5-142.abo.wanadoo.fr [80.8.58.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDC0243E3B; Mon, 28 Oct 2002 12:35:43 -0800 (PST) (envelope-from dak@wanadoo.fr) Received: from nebula.wanadoo.fr (localhost [127.0.0.1]) by nebula.wanadoo.fr (8.12.6/8.12.5) with ESMTP id g9SKauqk000342; Mon, 28 Oct 2002 21:36:56 +0100 (CET) (envelope-from dak@nebula.wanadoo.fr) Received: (from dak@localhost) by nebula.wanadoo.fr (8.12.6/8.12.6/Submit) id g9SKatUr000341; Mon, 28 Oct 2002 21:36:55 +0100 (CET) Date: Mon, 28 Oct 2002 21:36:54 +0100 From: =?iso-8859-15?Q?Aur=E9lien?= Nephtali To: Wilko Bulte Cc: John Baldwin , hackers@FreeBSD.ORG Subject: Re: Getting ACPI to work on -stable Message-ID: <20021028203654.GA264@nebula.wanadoo.fr> References: <20021024210829.B4981@freebie.xs4all.nl> <20021024214702.A5209@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <20021024214702.A5209@freebie.xs4all.nl> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I've got a panic too while playing with the battery (when I insert it, some= time later *BOOM* panic). It seems to be the same as Wilko so I don't attach the traceback (but if you really want it, I'll do :p). Someone is already investigating on this problem ? -- Aur=E9lien --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE9vZ/mDNsbHbt8ok8RApTKAJ99IwKf0wmDsaY57/xBY969tK7wnACglnTU AWAx+/vyzegVmtvz6uV/9rk= =Not2 -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 15:45: 2 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E91AE37B401 for ; Mon, 28 Oct 2002 15:45:00 -0800 (PST) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3308243E4A for ; Mon, 28 Oct 2002 15:44:59 -0800 (PST) (envelope-from Alex.Wilkinson@dsto.defence.gov.au) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.10.1/8.10.1) with ESMTP id g9SNhDe19774 for ; Tue, 29 Oct 2002 10:13:13 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by dsto-ms2.dsto.defence.gov.au (Content Technologies SMTPRS 4.2.10) with ESMTP id for ; Tue, 29 Oct 2002 10:12:59 +1030 Received: from salex001.dsto.defence.gov.au (salex001.dsto.defence.gov.au [131.185.2.9]) by muttley.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id KAA18539 for ; Tue, 29 Oct 2002 10:09:44 +1030 (CST) Received: from squirm.dsto.defence.gov.au ([131.185.75.211]) by salex001.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id VW7LLLNW; Tue, 29 Oct 2002 10:10:58 +1030 Date: Tue, 29 Oct 2002 09:56:30 +1030 (CST) From: "Wilkinson,Alex" X-X-Sender: wilkinsa@squirm.dsto.defence.gov.au Reply-To: Alex.Wilkinson@dsto.defence.gov.au To: hackers@freebsd.org Subject: [hardware] Tagged Command Queuing or Larger Cache ? Message-ID: <20021029095553.N91719-100000@squirm.dsto.defence.gov.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Howdy Crew, I am about to buy a new hard disk for my FreeBSD work station. Since FreeBSD's ATA drivers implement Tagged Command Queuing and IBM make the only ATA disks that implement tagged command queuing ( ie since the 60GXP family ), an IBM 40GB 120GXP "looks like" the best solution. However, my question is: Do the benifits from a having a larger disk cache such as the "WD 40GB 7200RPM w/8MB Cache" has, outweigh the benefits of Tagged Command Queuing ? Thanks - aW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 15:47:45 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7BDC37B401; Mon, 28 Oct 2002 15:47:27 -0800 (PST) Received: from isp.sputnikmedia.net (bigmir.mirotel.net [194.125.225.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B6C943E3B; Mon, 28 Oct 2002 15:47:25 -0800 (PST) (envelope-from russiaseminar@mail.ru) Received: from spam (ppp11.BM.mirotel.net [194.125.224.11]) by isp.sputnikmedia.net (8.12.6/8.11.6) with SMTP id g9SNAd9q068294; Tue, 29 Oct 2002 01:10:40 +0200 (EET) (envelope-from russiaseminar@mail.ru) Message-Id: <200210282310.g9SNAd9q068294@isp.sputnikmedia.net> From: To: 10@isp.sputnikmedia.net Organization: X-Priority: 3 X-MSMail-Priority: Normal Subject: ﾑ褌竟瑩 碣 Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Date: Tue, 29 Oct 2002 01:36:11 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ﾌ褂蔘瑩蓖鬆竟璋韶 琿竟胛糺 ﾖ褊 ﾏ鞳璧瑯 粽蒻褄裨 裝韜, 竟瑙糺 蒻裲, 粽蒻褄裨 瑙粽-顆褥頷 趁, 褻鞨頌 珞褊 竟瑙瑟, 瑕趺 瑰 頽 竟 瑰韃 褌竟瑩瑾-瑕韭瑾, 粽蒻 碣 2002 胛萵 ﾊ韃粢: ﾎ褄 ｫﾑ瑙-ﾏ褪褞碯羹 . ﾊ韃, 碯籵 ﾒ. ﾘ裘褊, 4 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ﾏﾐﾎﾁﾋﾅﾌﾛ ﾈﾑﾏﾎﾋﾍﾅﾍﾈﾟ ﾑﾓﾄﾅﾁﾍﾛﾕ ﾐﾅﾘﾅﾍﾈﾉ. ﾏ瑕顆褥韃 瑰裲. 5 碣 ﾏ硴褌 頌褊韃 蒟硼 褸褊韜 - "胛粹 碚" 蓁 肛 琲頷 裝韜. ﾄ琥 琿顆韋 褸褊 鴦粢胛 萵 粡瑙韋 蒡聰 裝 裙 粽鈔瑣 趺 鈞 蓁頸褄 . ﾊ 赳褊, "粨" 蒡跫韭 蒟褂 裝 韲褥籵, 砒鈕褄 蒟硼 頌頸褄裨, 瑕趺 鈕瑙韃 襃粨 褥 粱瑰, 襃糒 磊 頌褊 蒟硼 褸褊韜. ﾎ碚 粹韲瑙韃 碯蒟 蒟褊 粢褊 硴褌 粽 韈 瑕韭 頌頸褄胛 韈粽蓴籵. ﾑ褌竟瑩 韃頏籵 瑕韭, 鈞韲頷 粽瑟 粽鈔瑣 蒡胛 頸 胚碚 瑕顆褥韜 瑩瑕褞. ﾂ裝ｸ 褌竟瑩: 鈞褥頸褄 蒻裲 ﾄ襃瑩瑟褊 ﾃ萵粢 頌頸褄 趁 ﾌ竟頌褞籵 ﾞ頽韋 ﾓ琲: ﾊﾓﾇﾜ ﾀ.ﾐ. ﾑﾒﾎﾈﾌﾎﾑﾒﾜ ﾓﾗﾀﾑﾒﾈﾟ: 350 胙. 砒 ﾍﾄﾑ (裝竟 琿) - 鈞 蓖胛 瑰韭 褥 1-2 蔘 - V.I.P. 蕘 310 胙. 砒 ﾍﾄﾑ (裝竟 琿) - 鈞 蓖胛 瑰韭 褥 3-5 蔘. ﾄ 糘胛 褪裙 瑰韭 鞴 - 5% 7% 粢粢. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ﾑﾈﾑﾒﾅﾌﾀ ﾑﾁﾛﾒﾀ ﾄﾈﾋﾅﾐﾑﾊﾀﾟ ﾑﾅﾒﾜ: 瑙粲, 珸粨韃, . 12 碣 ﾝ裲鞣 珮 趁 磊 瑙粨 蓖韲 韈 裘 粨 褸胛 珸粨 礪鈿褥. ﾊ瑕 珞齏 聰韈籵 珮 趁 磊? ﾊ瑕 瑙頏籵 磊? ﾊ瑕 珸珮瑣 裲鞣 瑣裙 磊 褊 裝 韲褊 蓁 ﾂ璧裨 瑙韋? C瑣褄 褌竟瑩 碯蒟 裝趺 頌褌 蔟 褊 蒻褞 褪, 萵 裲褊萵韋 褊 蒡胛 褊韜 褞裲鞣 蒻褞瑟 裲褊萵韋 褸褊 琲碚裹 韵顆 硴褌 褥瑙萵 頸璋韜. ﾏ竟 瑰韃 褌竟瑩, 瑣褄 胚 褸 褸瑣 肛 蓿肛 鈞萵 珞褊 磊. ﾂ裝ｸ 褌竟瑩: ﾊﾀﾋﾌﾛﾊﾎﾂ ﾀ.ﾑ. - 礪鈿褥-瑙 胛粱. ﾏ褄 碯褊韃 竟頸 裲 褊裝趺 AGIT, ﾃ褞瑙. ﾑ琥頏籵 粢蔘裨 裘裨 胛粽 瑙韋 METRO, ﾃ褞瑙. ﾀ糘 裲 蓁 瑙韜 EUROMART, UNITRADE, METRO, ﾃﾀﾌﾌﾀ, PUMA, ﾝﾍﾐﾀﾍ, MEZOKRED, ﾍﾜﾞ ﾂﾈﾍﾄ ﾋﾅﾍﾒﾀ, FOZZY, ﾈﾍﾒﾅﾐﾒﾅﾕﾍﾈﾊﾀ 蓿. ﾑﾒﾎﾈﾌﾎﾑﾒﾜ ﾓﾗﾀﾑﾒﾈﾟ: 333 胙. 砒 ﾍﾄﾑ (裝竟 琿) - 鈞 蓖胛 瑰韭 褥 1-2 蔘 - V.I.P. 蕘 299 胙. 砒 ﾍﾄﾑ (裝竟 琿) - 鈞 蓖胛 瑰韭 褥 3-5 蔘. ﾄ 糘胛 褪裙 瑰韭 鞴 - 5% 7% 粢粢. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ﾏﾎﾑﾒﾀﾍﾎﾂﾊﾀ ﾑﾈﾑﾒﾅﾌﾛ ﾁﾞﾄﾆﾅﾒﾈﾐﾎﾂﾀﾍﾈﾟ. 14 碣 ﾏ褥 瑙粲 蓙褪頏籵 裔褪 琥褊 珮 糂襄 蓿珸蒟褊韜 瑙韜 粽 肭珞 竟瑙粽 趁. ﾍ 褌竟瑩-瑕韭 瑰瑣鞣瑯 裝籵褄 蒟鴦粨, 褓磆蒻 蓁 瑙粲 頌褌 蓙褪胛 珞褊, 璞竟 裝籵頸褄 珞褊褥 竟瑙粽 蒻璢韭 瑙韋 鈞瑙鞣 珸珮 瑕褪 粹褊頷 珞褊褥頷 蒡褊 蓙褪頏籵. ﾓ瑰韃 褌竟瑩, 胙瑟 胛 褊 粢 碚碼褊 瑕顆褥胛 , 鈔頸 瑣褄 瑟褄 頏籵 蓁 粽裨 瑙韋 襄肛 粹裝褊 蓙褪頏籵, 瑕趺 頌褌 褊 裼瑣 珸珮瑙 蒟 蓙褪胛 珞褊. ﾂ裝ｸ 褌竟瑩: ﾋ礪 ﾃ褞瑰韲褊 - 竟瑙糺 褞 (financial controller) 瑙韋 ﾔ齏韵 ﾌ頌 ﾓ琲. ﾑ褞頡頽頏籵 褂蔘瑩蓖 碯聰褞-瑪蒻 ACCA. ﾏ褄 碯褊韃 ﾓ鞣褞頸褪 ﾏ鴦 (ﾑﾘﾀ). ﾀ糘 韭琿 珸珮 褪蒻 蓙褪頏籵. ﾏ瑩褞 褌竟瑩: ﾊ璋 ﾃ琿瑕韭 (ﾐﾔ) - 蒻 韈 裨頷 ﾑﾍﾃ 珸珮韭 裲 褸褊韜 硴瑰 珞瑣韈璋韋 珞褊 韈粽蓴粢-鴦粢 竟瑙粽 蒟褄 裝. ﾑﾒﾎﾈﾌﾎﾑﾒﾜ ﾓﾗﾀﾑﾒﾈﾟ: 350 胙. 砒 ﾍﾄﾑ (裝竟 琿) - 鈞 蓖胛 瑰韭 褥 1-2 蔘 - V.I.P. 蕘 310 胙. 砒 ﾍﾄﾑ (裝竟 琿) - 鈞 蓖胛 瑰韭 褥 3-5 蔘. ﾄ 糘胛 褪裙 瑰韭 鞴 - 5% 7% 粢粢. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ﾂﾝﾄ 瑕: 瑟趺 . ﾍﾎﾂﾛﾅ ﾒﾀﾌﾎﾆﾅﾍﾍﾛﾅ ﾏﾐﾀﾂﾈﾋﾀ. 16 碣 ﾍ褞裝 鈞褊韋 粹褸顆褥胛 瑕 琲 裝瑣 粹韲瑙 蒟褪 珞褊 粨 瑕 - 粨 蓐 趾褊 瑟趺 裝. ﾏ裝粨: "胛粹 碚", 蒡頸褄 鈞瑣 糅褌褊 蒟褂 裝. ﾓ瑰韭 褌竟瑩 碯蔘 砒褶褊 瑟 粢趺 瑟 瑕琿 竟璋韃 粽瑟 瑟趺胛 裙頏籵, 鈿瑕 褪 矜 褸褊 硴褌 竟韲韈璋韋 鈞瑣 頌 褞褌襌褊韋 籵 褞裼 瑟趺 胙瑙頽 ﾓ琲 !!! ﾂ裝ｸ 褌竟瑩: ﾂ.ﾏ. ﾍ瑪褊 - 鈞. 蒻裲 瑙韋 ﾍﾒﾔ "ﾈ褥", 粢蔘韜 褻鞨頌 硴瑰 蒟瑩頏籵 瑟趺胛 褊 籵. ﾀ糘 胙瑶韜 "ﾎ糺 瑟趺胛 鈞萵褄籵 ﾓ琲", "ﾂ 瑟趺 褊韋 胙鉋". ﾏﾀﾐﾒﾍﾅﾐ ﾑﾅﾌﾈﾍﾀﾐﾀ: ﾊ瑙 "ﾈﾍﾒﾅﾑ", 珸珮韭 胙瑟胛 砒褶褊 蓁 珮 瑟跫裨. QD Professional - 砒蒻褄 ﾂ褫琲胛 韈粽蒻褄裨 胙瑟胛 砒褶褊 SoftRegatta-2001 330 胙. 砒 ﾍﾄﾑ (裝竟 琿) - 鈞 蓖胛 瑰韭 褥 1-2 蔘 - V.I.P. 蕘 299 胙. 砒 ﾍﾄﾑ (裝竟 琿) - 鈞 蓖胛 瑰韭 褥 3-5 蔘. ﾄ 糘胛 褪裙 瑰韭 鞴 - 3% 5% 粢粢. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ﾂ 韲 粲褊: 竟璋韶-璋韶 碵跖籵韃 褌竟瑩, 琿碚 瑣褞鞨, 褪, 碵趾褊韃 蒡琅 碆褊 褊 裲. ﾎ瑣 鈞 瑰韃 褌竟瑩 頸 珞 籵糺 鈞瑣 (. 5 ﾇ瑕 ﾓ琲 ﾎ 琿胛硴趺韋 鞦 裝韜) ﾐ裙瑟褊: 9-00 9-30 - 裙頌璋 (褊韃 碯聰褞胛 裲, 碚韭 瑣褞鞨, 鈞褊韃 瑙褪). 9-30 17-30 - 璋韋 褌竟瑩. ﾏ褞褞 褪 -碣裨. ﾑ褌竟瑩 粽蒻 糅褌褊 褞褊-鈞 頌鉋籵韃 璢蓖 裼褊璋韜 韲裝韜胛 裲. ﾄ瑙 粨 粢蒟 褌竟瑩 糺 裲鞣 糺褊, 硴裙 韲瑙韃, 蒟 糺褊韃 鈞竟韲, 鈔褪 鈞 韜 頸 瑕韲 裼 竟璋韋. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ﾐ裙頌璋 瑰韭 韈粽蒻 褞 : +38 (044) 459-02-82 ﾏ蓿硼 竟璋 褌竟瑩瑾 瑾蒻 琺 www.consulting.home.ro ﾈﾍﾔﾎﾐﾌﾀﾖﾈﾟ ﾎ ﾃﾎﾒﾅﾋﾅ: ﾀ蓿褥: 碯籵 ﾘ裘褊, 4 ﾐ瑰趺韃: 褊 (ﾁ褥瑩珮 琅) ﾏ韲褶瑙韃: ﾓ蒡硼 瑰趺韃 胛竟頽 褊 胛萵. ﾐ珸顆 瑣裙韋 褞. ﾁ頏籵韃 褞:(044) 229-73-64, 229-74-72 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 17:38:57 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E45937B401 for ; Mon, 28 Oct 2002 17:38:56 -0800 (PST) Received: from april.chuckr.org (april.chuckr.org [66.92.147.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id E159043E6E for ; Mon, 28 Oct 2002 17:38:54 -0800 (PST) (envelope-from chuckr@chuckr.org) Received: from april.chuckr.org (localhost [127.0.0.1]) by april.chuckr.org (8.12.6/8.12.5) with ESMTP id g9T1ZEli092499; Mon, 28 Oct 2002 20:35:14 -0500 (EST) (envelope-from chuckr@chuckr.org) Received: from localhost (chuckr@localhost) by april.chuckr.org (8.12.6/8.12.5/Submit) with ESMTP id g9T1ZCDa092496; Mon, 28 Oct 2002 20:35:13 -0500 (EST) X-Authentication-Warning: april.chuckr.org: chuckr owned process doing -bs Date: Mon, 28 Oct 2002 20:35:12 -0500 (EST) From: Chuck Robey To: "Wilkinson,Alex" Cc: Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? In-Reply-To: <20021029095553.N91719-100000@squirm.dsto.defence.gov.au> Message-ID: <20021028202933.Q59710-100000@april.chuckr.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 29 Oct 2002, Wilkinson,Alex wrote: > Howdy Crew, > > I am about to buy a new hard disk for my FreeBSD work station. > Since FreeBSD's ATA drivers implement Tagged Command Queuing and IBM make > the only ATA disks that implement tagged command queuing ( ie since the 60GXP family ), > an IBM 40GB 120GXP "looks like" the best solution. > > However, my question is: > > Do the benifits from a having a larger disk cache such as the "WD 40GB 7200RPM w/8MB Cache" > has, outweigh the benefits of Tagged Command Queuing ? You might want to give that a bit of thought. IBM, while producing OK scsi disks, has had a really terrible headache getting reliability into their IDE products. Additionally, IBM just sold their entire hard disk product line to some other company. I don't know if that had anything to do with their well-publicized IDE reliability problems or not, but I'd fight shy of any IBM IDE disks, in any app which requires any kind of stability. If you don't care about reliability, tho, there are some good deals I've seen on those disks, tho ... being dumped in mass cheaply. Again, this has nothing to do with their scsi disks, which are just fine. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 17:45:20 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C1AD37B401 for ; Mon, 28 Oct 2002 17:45:16 -0800 (PST) Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6547143E3B for ; Mon, 28 Oct 2002 17:45:15 -0800 (PST) (envelope-from culverk@yumyumyum.org) Received: from alpha.yumyumyum.org (localhost [127.0.0.1]) by alpha.yumyumyum.org (8.12.6/8.12.5) with ESMTP id g9T1gxDF061003; Mon, 28 Oct 2002 20:42:59 -0500 (EST) (envelope-from culverk@yumyumyum.org) Received: from localhost (culverk@localhost) by alpha.yumyumyum.org (8.12.6/8.12.5/Submit) with ESMTP id g9T1gvXF061000; Mon, 28 Oct 2002 20:42:58 -0500 (EST) (envelope-from culverk@yumyumyum.org) X-Authentication-Warning: alpha.yumyumyum.org: culverk owned process doing -bs Date: Mon, 28 Oct 2002 20:42:57 -0500 (EST) From: Kenneth Culver To: Chuck Robey Cc: "Wilkinson,Alex" , Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? In-Reply-To: <20021028202933.Q59710-100000@april.chuckr.org> Message-ID: <20021028204130.D59907-100000@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-2.0 required=5.0 tests=IN_REP_TO,X_AUTH_WARNING,SUBJ_ENDS_IN_Q_MARK, NO_MX_FOR_FROM,AWL version=2.31 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > You might want to give that a bit of thought. IBM, while producing OK > scsi disks, has had a really terrible headache getting reliability into > their IDE products. Additionally, IBM just sold their entire hard disk > product line to some other company. I don't know if that had anything to > do with their well-publicized IDE reliability problems or not, but I'd > fight shy of any IBM IDE disks, in any app which requires any kind of > stability. > > If you don't care about reliability, tho, there are some good deals I've > seen on those disks, tho ... being dumped in mass cheaply. Again, this > has nothing to do with their scsi disks, which are just fine. > I'd probably steer clear of the western digital drives as well. Yes the 8MB cache that some of them have DOES make a difference, but from personal experience, the drives themselves don't last that long. So in short, what good is a fast hard-drive if it's just going to break faster too? Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 17:48: 4 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3A5A37B401 for ; Mon, 28 Oct 2002 17:48:03 -0800 (PST) Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E0AB43E3B for ; Mon, 28 Oct 2002 17:48:03 -0800 (PST) (envelope-from culverk@yumyumyum.org) Received: from alpha.yumyumyum.org (localhost [127.0.0.1]) by alpha.yumyumyum.org (8.12.6/8.12.5) with ESMTP id g9T1klDF061046; Mon, 28 Oct 2002 20:46:48 -0500 (EST) (envelope-from culverk@yumyumyum.org) Received: from localhost (culverk@localhost) by alpha.yumyumyum.org (8.12.6/8.12.5/Submit) with ESMTP id g9T1kkRT061043; Mon, 28 Oct 2002 20:46:46 -0500 (EST) (envelope-from culverk@yumyumyum.org) X-Authentication-Warning: alpha.yumyumyum.org: culverk owned process doing -bs Date: Mon, 28 Oct 2002 20:46:46 -0500 (EST) From: Kenneth Culver To: Chuck Robey Cc: "Wilkinson,Alex" , Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? In-Reply-To: <20021028204130.D59907-100000@alpha.yumyumyum.org> Message-ID: <20021028204631.S61008-100000@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-2.0 required=5.0 tests=IN_REP_TO,X_AUTH_WARNING,SUBJ_ENDS_IN_Q_MARK, NO_MX_FOR_FROM,AWL version=2.31 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I'd probably steer clear of the western digital drives as well. Yes the make that "stear" clear. > 8MB cache that some of them have DOES make a difference, but from personal > experience, the drives themselves don't last that long. So in short, what > good is a fast hard-drive if it's just going to break faster too? > > Ken > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 17:52:15 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4829B37B401 for ; Mon, 28 Oct 2002 17:52:14 -0800 (PST) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7037D43E3B for ; Mon, 28 Oct 2002 17:52:11 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from localhost (localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.4/8.12.3) with ESMTP id g9T1pxbT000781; Tue, 29 Oct 2002 12:21:59 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? From: "Daniel O'Connor" To: Kenneth Culver Cc: Chuck Robey , "Wilkinson,Alex" , hackers@FreeBSD.ORG In-Reply-To: <20021028204130.D59907-100000@alpha.yumyumyum.org> References: <20021028204130.D59907-100000@alpha.yumyumyum.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 29 Oct 2002 01:51:59 +0000 Message-Id: <1035856320.77698.49.camel@chowder.localdomain> Mime-Version: 1.0 X-Spam-Score: -2.9 () IN_REP_TO,SUBJ_ENDS_IN_Q_MARK,PORN_10 X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 2002-10-29 at 01:42, Kenneth Culver wrote: > I'd probably steer clear of the western digital drives as well. Yes the > 8MB cache that some of them have DOES make a difference, but from personal > experience, the drives themselves don't last that long. So in short, what > good is a fast hard-drive if it's just going to break faster too? I haven't had any trouble with the WDxxxBB drives - the WDxxxAA drives are pretty unreliable though. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 17:55:26 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1DFA37B401 for ; Mon, 28 Oct 2002 17:55:25 -0800 (PST) Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBF7D43E42 for ; Mon, 28 Oct 2002 17:55:24 -0800 (PST) (envelope-from culverk@yumyumyum.org) Received: from alpha.yumyumyum.org (localhost [127.0.0.1]) by alpha.yumyumyum.org (8.12.6/8.12.5) with ESMTP id g9T1s9DF061085; Mon, 28 Oct 2002 20:54:09 -0500 (EST) (envelope-from culverk@yumyumyum.org) Received: from localhost (culverk@localhost) by alpha.yumyumyum.org (8.12.6/8.12.5/Submit) with ESMTP id g9T1s75v061082; Mon, 28 Oct 2002 20:54:07 -0500 (EST) (envelope-from culverk@yumyumyum.org) X-Authentication-Warning: alpha.yumyumyum.org: culverk owned process doing -bs Date: Mon, 28 Oct 2002 20:54:07 -0500 (EST) From: Kenneth Culver To: "Daniel O'Connor" Cc: Chuck Robey , "Wilkinson,Alex" , Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? In-Reply-To: <1035856320.77698.49.camel@chowder.localdomain> Message-ID: <20021028205222.G61008-100000@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-1.7 required=5.0 tests=IN_REP_TO,X_AUTH_WARNING,SUBJ_ENDS_IN_Q_MARK,PORN_10, NO_MX_FOR_FROM,AWL version=2.31 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I haven't had any trouble with the WDxxxBB drives - the WDxxxAA drives > are pretty unreliable though. > Hrmm, I havn't tried those, but just about every WD drive I've used has ended up with problems which were of course handled by the warranty, but even then, I still had to reinstall the os and pull a bunch of stuff from my backups which was a pain to do for each failure. Like I said, just my personal experience. I don't think the new 8MB cache drives have been out long enough to actually develop the problems I've seen on WD drives though. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 18: 4: 4 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BE7637B401 for ; Mon, 28 Oct 2002 18:04:03 -0800 (PST) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93DF143E3B for ; Mon, 28 Oct 2002 18:04:01 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from localhost (localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.4/8.12.3) with ESMTP id g9T23obT001010; Tue, 29 Oct 2002 12:33:50 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? From: "Daniel O'Connor" To: Kenneth Culver Cc: Chuck Robey , "Wilkinson,Alex" , hackers@FreeBSD.ORG In-Reply-To: <20021028205222.G61008-100000@alpha.yumyumyum.org> References: <20021028205222.G61008-100000@alpha.yumyumyum.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 29 Oct 2002 02:03:50 +0000 Message-Id: <1035857031.77698.57.camel@chowder.localdomain> Mime-Version: 1.0 X-Spam-Score: -2.9 () IN_REP_TO,SUBJ_ENDS_IN_Q_MARK,PORN_10 X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 2002-10-29 at 01:54, Kenneth Culver wrote: > > I haven't had any trouble with the WDxxxBB drives - the WDxxxAA drives > > are pretty unreliable though. > > > Hrmm, I havn't tried those, but just about every WD drive I've used has > ended up with problems which were of course handled by the warranty, but > even then, I still had to reinstall the os and pull a bunch of stuff from > my backups which was a pain to do for each failure. Like I said, just my > personal experience. I don't think the new 8MB cache drives have been out > long enough to actually develop the problems I've seen on WD drives > though. Yes, but my point is that the AA drives are bad, but the BB drives seem good. I have been using them for a while (~1 year) without trouble. I believe the JB drives are much more closely related to the BB drives (ie effectively identical but with a bigger cache). Personally I find that no HD manufacturer has a good reputation - they have all made trashy drives at one point. Give the general time it takes for problems to surface vs product lifetimes makes deciding what to buy a PITA :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 18: 4:36 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 811F637B401 for ; Mon, 28 Oct 2002 18:04:35 -0800 (PST) Received: from 12-234-90-219.client.attbi.com (12-234-90-219.client.attbi.com [12.234.90.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE00843E4A for ; Mon, 28 Oct 2002 18:04:34 -0800 (PST) (envelope-from DougB@FreeBSD.org) Received: from master.gorean.org (master.gorean.org [10.0.0.2]) by 12-234-90-219.client.attbi.com (8.12.6/8.12.6) with ESMTP id g9T24LmX010133; Mon, 28 Oct 2002 18:04:22 -0800 (PST) (envelope-from DougB@FreeBSD.org) Received: from localhost (doug@localhost) by master.gorean.org (8.12.6/8.12.6/Submit) with ESMTP id g9T243pn003920; Mon, 28 Oct 2002 18:04:11 -0800 (PST) Date: Mon, 28 Oct 2002 18:04:03 -0800 (PST) From: Doug Barton To: Kenneth Culver Cc: Chuck Robey , "Wilkinson,Alex" , Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? In-Reply-To: <20021028204631.S61008-100000@alpha.yumyumyum.org> Message-ID: <20021028180337.H3316-100000@master.gorean.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 28 Oct 2002, Kenneth Culver wrote: > > I'd probably steer clear of the western digital drives as well. Yes the > > make that "stear" clear. Ummm... why? "steer" is a word with multiple meanings. I can't find "stear" anywhere. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 18: 8:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25B3A37B401 for ; Mon, 28 Oct 2002 18:08:41 -0800 (PST) Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E52743E4A for ; Mon, 28 Oct 2002 18:08:40 -0800 (PST) (envelope-from culverk@yumyumyum.org) Received: from alpha.yumyumyum.org (localhost [127.0.0.1]) by alpha.yumyumyum.org (8.12.6/8.12.5) with ESMTP id g9T27ODF061171; Mon, 28 Oct 2002 21:07:24 -0500 (EST) (envelope-from culverk@yumyumyum.org) Received: from localhost (culverk@localhost) by alpha.yumyumyum.org (8.12.6/8.12.5/Submit) with ESMTP id g9T27NgG061168; Mon, 28 Oct 2002 21:07:23 -0500 (EST) (envelope-from culverk@yumyumyum.org) X-Authentication-Warning: alpha.yumyumyum.org: culverk owned process doing -bs Date: Mon, 28 Oct 2002 21:07:23 -0500 (EST) From: Kenneth Culver To: "Daniel O'Connor" Cc: Chuck Robey , "Wilkinson,Alex" , Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? In-Reply-To: <1035857031.77698.57.camel@chowder.localdomain> Message-ID: <20021028210709.L61008-100000@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-2.0 required=5.0 tests=IN_REP_TO,X_AUTH_WARNING,SUBJ_ENDS_IN_Q_MARK, NO_MX_FOR_FROM,AWL version=2.31 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Yes, but my point is that the AA drives are bad, but the BB drives seem > good. I have been using them for a while (~1 year) without trouble. > > I believe the JB drives are much more closely related to the BB drives > (ie effectively identical but with a bigger cache). > > Personally I find that no HD manufacturer has a good reputation - they > have all made trashy drives at one point. Give the general time it takes > for problems to surface vs product lifetimes makes deciding what to buy > a PITA :( > I'll agree with that :-) Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 18: 9:25 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1B9337B401; Mon, 28 Oct 2002 18:09:24 -0800 (PST) Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AD7843E77; Mon, 28 Oct 2002 18:09:24 -0800 (PST) (envelope-from culverk@yumyumyum.org) Received: from alpha.yumyumyum.org (localhost [127.0.0.1]) by alpha.yumyumyum.org (8.12.6/8.12.5) with ESMTP id g9T288DF061185; Mon, 28 Oct 2002 21:08:09 -0500 (EST) (envelope-from culverk@yumyumyum.org) Received: from localhost (culverk@localhost) by alpha.yumyumyum.org (8.12.6/8.12.5/Submit) with ESMTP id g9T287UJ061182; Mon, 28 Oct 2002 21:08:07 -0500 (EST) (envelope-from culverk@yumyumyum.org) X-Authentication-Warning: alpha.yumyumyum.org: culverk owned process doing -bs Date: Mon, 28 Oct 2002 21:08:07 -0500 (EST) From: Kenneth Culver To: Doug Barton Cc: Chuck Robey , "Wilkinson,Alex" , Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? In-Reply-To: <20021028180337.H3316-100000@master.gorean.org> Message-ID: <20021028210733.I61008-100000@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-2.0 required=5.0 tests=IN_REP_TO,X_AUTH_WARNING,SUBJ_ENDS_IN_Q_MARK, NO_MX_FOR_FROM,AWL version=2.31 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Ummm... why? "steer" is a word with multiple meanings. I can't find > "stear" anywhere. > > well, lets just say that my brain is fried b/c of midterms. OK? :-P Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 18:31: 1 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88D7937B401 for ; Mon, 28 Oct 2002 18:31:00 -0800 (PST) Received: from 12-234-90-219.client.attbi.com (12-234-90-219.client.attbi.com [12.234.90.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 800BA43E42 for ; Mon, 28 Oct 2002 18:30:59 -0800 (PST) (envelope-from DougB@FreeBSD.org) Received: from master.gorean.org (master.gorean.org [10.0.0.2]) by 12-234-90-219.client.attbi.com (8.12.6/8.12.6) with ESMTP id g9T2UjmX010267; Mon, 28 Oct 2002 18:30:47 -0800 (PST) (envelope-from DougB@FreeBSD.org) Received: from localhost (doug@localhost) by master.gorean.org (8.12.6/8.12.6/Submit) with ESMTP id g9T2UjHT003975; Mon, 28 Oct 2002 18:30:45 -0800 (PST) Date: Mon, 28 Oct 2002 18:30:45 -0800 (PST) From: Doug Barton To: Kenneth Culver Cc: Chuck Robey , "Wilkinson,Alex" , Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? In-Reply-To: <20021028210733.I61008-100000@alpha.yumyumyum.org> Message-ID: <20021028183024.A3316-100000@master.gorean.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 28 Oct 2002, Kenneth Culver wrote: > > Ummm... why? "steer" is a word with multiple meanings. I can't find > > "stear" anywhere. > > > > > well, lets just say that my brain is fried b/c of midterms. OK? :-P Ah, you are forgiven then... go and sin no more. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 18:32:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFF7C37B401 for ; Mon, 28 Oct 2002 18:32:41 -0800 (PST) Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA97243E7B for ; Mon, 28 Oct 2002 18:32:40 -0800 (PST) (envelope-from babolo@aaz.links.ru) Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by aaz.links.ru (8.12.6/8.12.6) with ESMTP id g9T2XDDh033712; Tue, 29 Oct 2002 05:33:13 +0300 (MSK) (envelope-from babolo@aaz.links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.12.6/8.12.6/Submit) id g9T2XDDw033711; Tue, 29 Oct 2002 05:33:13 +0300 (MSK) Message-Id: <200210290233.g9T2XDDw033711@aaz.links.ru> Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: <20021029095553.N91719-100000@squirm.dsto.defence.gov.au> To: Alex.Wilkinson@dsto.defence.gov.au Date: Tue, 29 Oct 2002 05:33:11 +0300 (MSK) From: "."@babolo.ru Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Howdy Crew, > > I am about to buy a new hard disk for my FreeBSD work station. > Since FreeBSD's ATA drivers implement Tagged Command Queuing and IBM make > the only ATA disks that implement tagged command queuing ( ie since the 60GXP family ), > an IBM 40GB 120GXP "looks like" the best solution. > > However, my question is: > > Do the benifits from a having a larger disk cache such as the "WD 40GB 7200RPM w/8MB Cache" > has, outweigh the benefits of Tagged Command Queuing ? As far as I know big cashe helps for one I/O thread, and Tagged Queuing helps more in multiple I/O threads. The first series of Tagged Queuing drive was far before 60GXP - it was DPTA. Then DLTA (I used this hardly, some of them was slightly buggy) -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 18:43:43 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D7D537B401 for ; Mon, 28 Oct 2002 18:43:42 -0800 (PST) Received: from april.chuckr.org (april.chuckr.org [66.92.147.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id C019343E3B for ; Mon, 28 Oct 2002 18:43:40 -0800 (PST) (envelope-from chuckr@chuckr.org) Received: from april.chuckr.org (localhost [127.0.0.1]) by april.chuckr.org (8.12.6/8.12.5) with ESMTP id g9T2eVff045737; Mon, 28 Oct 2002 21:40:31 -0500 (EST) (envelope-from chuckr@chuckr.org) Received: from localhost (chuckr@localhost) by april.chuckr.org (8.12.6/8.12.5/Submit) with ESMTP id g9T2eTcP045734; Mon, 28 Oct 2002 21:40:29 -0500 (EST) X-Authentication-Warning: april.chuckr.org: chuckr owned process doing -bs Date: Mon, 28 Oct 2002 21:40:28 -0500 (EST) From: Chuck Robey To: "Daniel O'Connor" Cc: Kenneth Culver , "Wilkinson,Alex" , Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? In-Reply-To: <1035857031.77698.57.camel@chowder.localdomain> Message-ID: <20021028213317.Y45658-100000@april.chuckr.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 29 Oct 2002, Daniel O'Connor wrote: > On Tue, 2002-10-29 at 01:54, Kenneth Culver wrote: > > > I haven't had any trouble with the WDxxxBB drives - the WDxxxAA drives > > > are pretty unreliable though. > > > > > Hrmm, I havn't tried those, but just about every WD drive I've used has > > ended up with problems which were of course handled by the warranty, but > > even then, I still had to reinstall the os and pull a bunch of stuff from > > my backups which was a pain to do for each failure. Like I said, just my > > personal experience. I don't think the new 8MB cache drives have been out > > long enough to actually develop the problems I've seen on WD drives > > though. > > Yes, but my point is that the AA drives are bad, but the BB drives seem > good. I have been using them for a while (~1 year) without trouble. > > I believe the JB drives are much more closely related to the BB drives > (ie effectively identical but with a bigger cache). > > Personally I find that no HD manufacturer has a good reputation - they > have all made trashy drives at one point. Give the general time it takes > for problems to surface vs product lifetimes makes deciding what to buy > a PITA :( No, I'd take issue with that, hitting on all HD mfrs in general, it has more to do with the technology, and the focus of the market it's aimed at. In general, SCSI drives have a far better rep than the IDE drives. That probably has to do with the market sector they focus on. With one exception (a heat problem I probably must blame on myself doing some learning) I've had no problems with scsi drives, and I beat hell out of them. I guess if you *must* run IDE, then run raid arrays. If you don't run either, then you can't complain if you buy the cheapest and don't get the best reliability. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 19:26:18 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E20FF37B401 for ; Mon, 28 Oct 2002 19:26:16 -0800 (PST) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id C28B243E3B for ; Mon, 28 Oct 2002 19:26:14 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from localhost (localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.4/8.12.3) with ESMTP id g9T3PxbT002409; Tue, 29 Oct 2002 13:56:01 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? From: "Daniel O'Connor" To: Chuck Robey Cc: Kenneth Culver , "Wilkinson,Alex" , hackers@FreeBSD.ORG In-Reply-To: <20021028213317.Y45658-100000@april.chuckr.org> References: <20021028213317.Y45658-100000@april.chuckr.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 29 Oct 2002 03:25:59 +0000 Message-Id: <1035861964.77698.83.camel@chowder.localdomain> Mime-Version: 1.0 X-Spam-Score: -3.5 () IN_REP_TO,SUBJ_ENDS_IN_Q_MARK X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 2002-10-29 at 02:40, Chuck Robey wrote: > > Personally I find that no HD manufacturer has a good reputation - they > > have all made trashy drives at one point. Give the general time it takes > > for problems to surface vs product lifetimes makes deciding what to buy > > a PITA :( > > No, I'd take issue with that, hitting on all HD mfrs in general, it has > more to do with the technology, and the focus of the market it's aimed at. > In general, SCSI drives have a far better rep than the IDE drives. That > probably has to do with the market sector they focus on. With one > exception (a heat problem I probably must blame on myself doing some > learning) I've had no problems with scsi drives, and I beat hell out of > them. They sure do have a better rep. but they DO cost 4x as much :) (Not including a controller) > I guess if you *must* run IDE, then run raid arrays. If you don't run > either, then you can't complain if you buy the cheapest and don't get the > best reliability. Indeed, though in general I find it pretty hard to justify SCSI prices in the particular application we have. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 20:24:22 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06A2937B401 for ; Mon, 28 Oct 2002 20:24:20 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6343743E6E for ; Mon, 28 Oct 2002 20:24:19 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id 967662A88D; Mon, 28 Oct 2002 20:24:15 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "Daniel O'Connor" Cc: Chuck Robey , Kenneth Culver , "Wilkinson, Alex" , hackers@FreeBSD.ORG Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? In-Reply-To: <1035861964.77698.83.camel@chowder.localdomain> Date: Mon, 28 Oct 2002 20:24:15 -0800 From: Peter Wemm Message-Id: <20021029042415.967662A88D@canning.wemm.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Daniel O'Connor" wrote: > On Tue, 2002-10-29 at 02:40, Chuck Robey wrote: > > > Personally I find that no HD manufacturer has a good reputation - they > > > have all made trashy drives at one point. Give the general time it takes > > > for problems to surface vs product lifetimes makes deciding what to buy > > > a PITA :( > > > > No, I'd take issue with that, hitting on all HD mfrs in general, it has > > more to do with the technology, and the focus of the market it's aimed at. > > In general, SCSI drives have a far better rep than the IDE drives. That > > probably has to do with the market sector they focus on. With one > > exception (a heat problem I probably must blame on myself doing some > > learning) I've had no problems with scsi drives, and I beat hell out of > > them. > > They sure do have a better rep. but they DO cost 4x as much :) > (Not including a controller) > > > I guess if you *must* run IDE, then run raid arrays. If you don't run > > either, then you can't complain if you buy the cheapest and don't get the > > best reliability. > > Indeed, though in general I find it pretty hard to justify SCSI prices > in the particular application we have. A seperate parallel thread is running on -alpha (bad!), where the question of whether tagged queueing on IDE was safe or not. === (I wrote:) Peter Jeremy wrote: > The safe states are: tagging & caching or no-caching (which is slow). Actually, not even then. Modern IDE drives only write entire tracks at a time. If you modify a single sector, then the drive has to read the entire track into the buffer, in-place edit the sector, and then rewrite the entire track. As you can imagine, this violates the basic assumptions of FFS and softdep. They assume that only sectors that are written to are at risk, and do all their ordering based on that assumption. But the assumption is completely bogus. Even with no-caching it doesn't work because if the drive loses power after only having written half of the track, then you risk losing the rest - the track is written from "wherever", and not any index marks. ie: the track is just as likely to overwrite the second half of the sectors first, and when you lose power, you have two copies of the first half of the sectors. Basically you have to assume that the entire track and all of the nearby sectors could get lost or trashed. And that completely blows FFS's assumptions out of the water. And what is sad is that many SCSI disks are similar these days. But not all of them (I'm told). Basically if you get a power failure, you are totally screwed. softdep will save you from a hard OS level lockup/reset though. === Personally, I find that the sub-5ms seek time on scsi drives contributes a fair bit to the percieved speed of the box under load. Without serious load though, it is very hard to tell the difference between scsi and ide. Most of the recent scsi drives I've used are between about 4.1ms through 4.5ms seek vs ide drives at between 8ms and 12ms seek time. What IDE calls 'tagged queueing' seems to be little more than allowing ide drives to release the bus while they go and do something. It dramatically improves the bus contention when you have a pair of drives on a single ide channel.. almost to the point that there is little or no degradation when you are hammering both drives at once. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 21:41:49 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7969237B401 for ; Mon, 28 Oct 2002 21:41:48 -0800 (PST) Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93C5B43E4A for ; Mon, 28 Oct 2002 21:41:47 -0800 (PST) (envelope-from babolo@aaz.links.ru) Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by aaz.links.ru (8.12.6/8.12.6) with ESMTP id g9T5gJDh036717; Tue, 29 Oct 2002 08:42:19 +0300 (MSK) (envelope-from babolo@aaz.links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.12.6/8.12.6/Submit) id g9T5g6PV036712; Tue, 29 Oct 2002 08:42:06 +0300 (MSK) Message-Id: <200210290542.g9T5g6PV036712@aaz.links.ru> Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: <20021029042415.967662A88D@canning.wemm.org> To: Peter Wemm Date: Tue, 29 Oct 2002 08:42:05 +0300 (MSK) From: "."@babolo.ru Cc: "Daniel O'Connor" , Chuck Robey , Kenneth Culver , "Wilkinson, Alex" , hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > "Daniel O'Connor" wrote: > As you can imagine, this violates the basic assumptions of FFS and softdep. > They assume that only sectors that are written to are at risk, and do all > their ordering based on that assumption. But the assumption is completely > bogus. Even with no-caching it doesn't work because if the drive loses > power after only having written half of the track, then you risk losing the > rest - the track is written from "wherever", and not any index marks. ie: > the track is just as likely to overwrite the second half of the sectors > first, and when you lose power, you have two copies of the first half of > the sectors. Basically you have to assume that the entire track and > all of the nearby sectors could get lost or trashed. I usually lose 4..8 sectors cluster on fast power down on IBM IDE drives. Repairable. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 28 21:44:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A7CE37B401 for ; Mon, 28 Oct 2002 21:44:58 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC33C43E4A for ; Mon, 28 Oct 2002 21:44:57 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id A905A2A88D; Mon, 28 Oct 2002 21:44:57 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "."@babolo.ru Cc: "Daniel O'Connor" , Chuck Robey , Kenneth Culver , "Wilkinson, Alex" , hackers@FreeBSD.ORG Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? In-Reply-To: <200210290542.g9T5g6PV036712@aaz.links.ru> Date: Mon, 28 Oct 2002 21:44:57 -0800 From: Peter Wemm Message-Id: <20021029054457.A905A2A88D@canning.wemm.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "."@babolo.ru wrote: > > "Daniel O'Connor" wrote: > > As you can imagine, this violates the basic assumptions of FFS and softdep. > > They assume that only sectors that are written to are at risk, and do all > > their ordering based on that assumption. But the assumption is completely > > bogus. Even with no-caching it doesn't work because if the drive loses > > power after only having written half of the track, then you risk losing the > > rest - the track is written from "wherever", and not any index marks. ie: > > the track is just as likely to overwrite the second half of the sectors > > first, and when you lose power, you have two copies of the first half of > > the sectors. Basically you have to assume that the entire track and > > all of the nearby sectors could get lost or trashed. > I usually lose 4..8 sectors cluster on fast power down > on IBM IDE drives. > Repairable. Maybe so, but FFS is written with the assumption that only the sector being written is at risk. Even losing 4-8 sectors blows that out the window if it happens to be metadata. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 2:31:53 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFE2237B401 for ; Tue, 29 Oct 2002 02:31:52 -0800 (PST) Received: from HAL9000.homeunix.com (12-232-220-15.client.attbi.com [12.232.220.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D68643E6E for ; Tue, 29 Oct 2002 02:31:51 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id g9TAVhTx018890; Tue, 29 Oct 2002 02:31:43 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id g9TAVXvk018889; Tue, 29 Oct 2002 02:31:33 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Tue, 29 Oct 2002 02:31:33 -0800 From: David Schultz To: Peter Wemm Cc: "Daniel O'Connor" , Chuck Robey , Kenneth Culver , "Wilkinson, Alex" , hackers@FreeBSD.ORG Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? Message-ID: <20021029103133.GA18812@HAL9000.homeunix.com> Mail-Followup-To: Peter Wemm , Daniel O'Connor , Chuck Robey , Kenneth Culver , "Wilkinson, Alex" , hackers@FreeBSD.ORG References: <1035861964.77698.83.camel@chowder.localdomain> <20021029042415.967662A88D@canning.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021029042415.967662A88D@canning.wemm.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Peter Wemm : > Actually, not even then. Modern IDE drives only write entire tracks at a > time. If you modify a single sector, then the drive has to read the entire > track into the buffer, in-place edit the sector, and then rewrite the entire > track. [...] > And that completely blows FFS's assumptions out of the water. And what > is sad is that many SCSI disks are similar these days. But not all of > them (I'm told). I've heard this before. It would be very useful to have information about which drives have this misfeature, but I guess it isn't the sort of thing that hard drive manufacturers like to advertise. Does anyone have any data on track-writing drives? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 8: 3:11 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CB6637B401 for ; Tue, 29 Oct 2002 08:03:10 -0800 (PST) Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCECE43E88 for ; Tue, 29 Oct 2002 08:03:09 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from onyx ([128.226.182.171]) by bingnet2.cc.binghamton.edu (8.11.6/8.11.6) with ESMTP id g9TG35o03631 for ; Tue, 29 Oct 2002 11:03:05 -0500 (EST) Date: Tue, 29 Oct 2002 11:03:04 -0500 (EST) From: Zhihui Zhang X-Sender: zzhang@onyx To: freebsd-hackers@freebsd.org Subject: Command used to trace the stack of a process Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I remember there is a command in either gdb or ddb which enable you to display the stack of a particular process. Can anyone tell me if there is such a command and what the command is? Thanks! -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 8: 9:16 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52F5C37B401 for ; Tue, 29 Oct 2002 08:09:14 -0800 (PST) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00C8C43E7B for ; Tue, 29 Oct 2002 08:09:13 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) by srv1.cosmo-project.de (8.12.5/8.12.5) with ESMTP id g9TG8qWQ072230 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Tue, 29 Oct 2002 17:08:55 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.1.10]) by cicely5.cicely.de (8.12.6/8.12.6) with ESMTP id g9TG8pCu028006 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 29 Oct 2002 17:08:51 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (localhost [127.0.0.1]) by cicely8.cicely.de (8.12.6/8.12.6) with ESMTP id g9TG8ol8017178; Tue, 29 Oct 2002 17:08:50 +0100 (CET) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.12.6/8.12.6/Submit) id g9TG8k0j017177; Tue, 29 Oct 2002 17:08:46 +0100 (CET) Date: Tue, 29 Oct 2002 17:08:45 +0100 From: Bernd Walter To: Joe Sunday Cc: David Nicholas Kayal , freebsd-hackers@FreeBSD.ORG Subject: Re: i am looking for a 5 volt signal Message-ID: <20021029160844.GA16922@cicely8.cicely.de> Reply-To: ticso@cicely.de References: <20021028135635.GA28293@csh.rit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021028135635.GA28293@csh.rit.edu> X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 User-Agent: Mutt/1.5.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Oct 28, 2002 at 08:56:35AM -0500, Joe Sunday wrote: > On Sun, Oct 27, 2002 at 09:12:33AM -0800, David Nicholas Kayal wrote: > > > I'm looking for a 5 volt signal. > > > > I have wires plugged into pins 2 and 25 of the parallel port. > > > > I have written a small program: > > > > #include > > #include > > #include > > > > int main() > > { > > int fd; > > while(1) > > { > > ioctl(fd, PPISDATA, 255); > > } > > } > > PPISDATA actually takes an int* argument. (The man page may be a tad > confusing here.) No it takes an u_int8_t* exactly as written in the manpage. Using an int doesn't work in all cases. I have no idea what part of the manpage is confusing. > Try > int main() { > int fd; > int d = 255; u_int8_t d = 255; > fd = open( "/dev/ppi0", O_RDWR ); > > ioctl( fd, PPISDATA, &d ); > > return 0; > } -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 8:17:29 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 810D337B401 for ; Tue, 29 Oct 2002 08:17:27 -0800 (PST) Received: from littleboy.csh.rit.edu (littleboy.csh.rit.edu [129.21.60.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A5DF43E3B for ; Tue, 29 Oct 2002 08:17:23 -0800 (PST) (envelope-from sunday@csh.rit.edu) Received: from fury.csh.rit.edu (fury.csh.rit.edu [129.21.60.5]) by littleboy.csh.rit.edu (Postfix) with ESMTP id ED3B28674; Tue, 29 Oct 2002 11:17:16 -0500 (EST) Received: by fury.csh.rit.edu (Postfix, from userid 38501) id 513592E384; Tue, 29 Oct 2002 11:17:16 -0500 (EST) Date: Tue, 29 Oct 2002 11:17:16 -0500 From: Joe Sunday To: ticso@cicely.de Cc: David Nicholas Kayal , freebsd-hackers@FreeBSD.ORG Subject: Re: i am looking for a 5 volt signal Message-ID: <20021029161715.GB11104@csh.rit.edu> References: <20021028135635.GA28293@csh.rit.edu> <20021029160844.GA16922@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021029160844.GA16922@cicely8.cicely.de> User-Agent: Mutt/1.4i X-Operating-System: SunOS 5.8 (sun4u) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Oct 29, 2002 at 05:08:45PM +0100, Bernd Walter wrote: > On Mon, Oct 28, 2002 at 08:56:35AM -0500, Joe Sunday wrote: > > On Sun, Oct 27, 2002 at 09:12:33AM -0800, David Nicholas Kayal wrote: > > > > > I'm looking for a 5 volt signal. > > > > > > I have wires plugged into pins 2 and 25 of the parallel port. > > > > > > I have written a small program: > > > > > > #include > > > #include > > > #include > > > > > > int main() > > > { > > > int fd; > > > while(1) > > > { > > > ioctl(fd, PPISDATA, 255); > > > } > > > } > > > > PPISDATA actually takes an int* argument. (The man page may be a tad > > confusing here.) > > No it takes an u_int8_t* exactly as written in the manpage. > Using an int doesn't work in all cases. > I have no idea what part of the manpage is confusing. > > > Try > > int main() { > > int fd; > > int d = 255; > u_int8_t d = 255; > > > fd = open( "/dev/ppi0", O_RDWR ); > > > > ioctl( fd, PPISDATA, &d ); > > > > return 0; > > } My bad. Yeah, it takes a u_int8_t* argument, not an int* (Serves me right for doing it off the top of my head instead of looking at my code). However, the original poster had it simply taking some integer value rather than a pointer. The man page says this: Each command takes a single u_int8_t argument, transferring one byte of data. Which, to me at first glance, can read as a u_int8_t argument, rather than a u_int8_t* argument if you're new to using ioctls. The example further down the man page has it properly taking an pointer. --Joe -- Joe Sunday http://www.csh.rit.edu/~sunday/ Computer Science House, Rochester Inst. Of Technology To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 8:48:50 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E53A37B401 for ; Tue, 29 Oct 2002 08:48:49 -0800 (PST) Received: from mail04.svc.cra.dublin.eircom.net (mail04.svc.cra.dublin.eircom.net [159.134.118.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 64D6243E75 for ; Tue, 29 Oct 2002 08:48:48 -0800 (PST) (envelope-from pmedwards@eircom.net) Received: (qmail 86436 messnum 1108018 invoked from network[159.134.237.77/kearney.eircom.net]); 29 Oct 2002 16:48:46 -0000 Received: from kearney.eircom.net (HELO webmail.eircom.net) (159.134.237.77) by mail04.svc.cra.dublin.eircom.net (qp 86436) with SMTP; 29 Oct 2002 16:48:46 -0000 From: "Peter Edwards" To: zzhang@cs.binghamton.edu Cc: freebsd-hackers@freebsd.org Subject: Re: Command used to trace the stack of a process Date: Tue, 29 Oct 2002 16:46:04 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-Originating-IP: 62.17.151.61 X-Mailer: Eircom Net CRC Webmail (http://www.eircom.net/) Organization: Eircom Net (http://www.eircom.net/) Message-Id: <20021029164848.64D6243E75@mx1.FreeBSD.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is /usr/ports/sysutils/pstack what you're looking for? -- Peter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 9: 1:53 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C98337B401 for ; Tue, 29 Oct 2002 09:01:52 -0800 (PST) Received: from mail.speakeasy.net (mail17.speakeasy.net [216.254.0.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07A5843E42 for ; Tue, 29 Oct 2002 09:01:52 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 6948 invoked from network); 29 Oct 2002 17:01:54 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail17.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 29 Oct 2002 17:01:54 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id g9TH1gn5091804; Tue, 29 Oct 2002 12:01:43 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 29 Oct 2002 12:01:41 -0500 (EST) From: John Baldwin To: Zhihui Zhang Subject: RE: Command used to trace the stack of a process Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 29-Oct-2002 Zhihui Zhang wrote: > > I remember there is a command in either gdb or ddb which enable you to > display the stack of a particular process. Can anyone tell me if there is > such a command and what the command is? Thanks! In ddb you can do 'tr ' where is the PID of the process. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 9:27:22 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7590C37B401 for ; Tue, 29 Oct 2002 09:27:21 -0800 (PST) Received: from gicco.homeip.net (dclient80-218-75-109.hispeed.ch [80.218.75.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1F4843E75 for ; Tue, 29 Oct 2002 09:27:14 -0800 (PST) (envelope-from hampi@rootshell.be) Received: (from idefix@localhost) by gicco.homeip.net (8.11.6/8.11.6) id g9THRCh01520 for hackers@FreeBSD.org; Tue, 29 Oct 2002 18:27:12 +0100 (CET) (envelope-from hampi@rootshell.be) Date: Tue, 29 Oct 2002 18:27:12 +0100 From: Hanspeter Roth To: hackers@FreeBSD.org Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer Message-ID: <20021029182712.A1479@gicco.homeip.net> Reply-To: freebsd-hackers@FreeBSD.org Mail-Followup-To: hackers@FreeBSD.org References: <3DB048B5.21097613@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3DB048B5.21097613@FreeBSD.org>; from sobomax@FreeBSD.org on Fri, Oct 18, 2002 at 08:45:25PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Oct 18 at 20:45, Maxim Sobolev spoke: > again, then again ad infinitum. The same effect if you'll mount > write-protected floppy in read/write mode. As of a write-protected floppy, why is it allowd to be mounted as writeable? The mount should be degraded to readonly or rejected. -Hanspeter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 9:34:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D661337B401; Tue, 29 Oct 2002 09:34:50 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71AEB43E6E; Tue, 29 Oct 2002 09:34:48 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id g9THYarF094461; Tue, 29 Oct 2002 18:34:37 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: freebsd-hackers@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer In-Reply-To: Your message of "Tue, 29 Oct 2002 18:27:12 +0100." <20021029182712.A1479@gicco.homeip.net> Date: Tue, 29 Oct 2002 18:34:36 +0100 Message-ID: <94460.1035912876@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20021029182712.A1479@gicco.homeip.net>, Hanspeter Roth writes: > On Oct 18 at 20:45, Maxim Sobolev spoke: > >> again, then again ad infinitum. The same effect if you'll mount >> write-protected floppy in read/write mode. This is just lame, but I'm not willing to to take a shouting match with the person who committed this brain-damage. >As of a write-protected floppy, why is it allowd to be mounted as >writeable? >The mount should be degraded to readonly or rejected. That's a slightly more involved issue because you would have to actually try to write to it before you find out that you can't. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 9:34:55 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D661337B401; Tue, 29 Oct 2002 09:34:50 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71AEB43E6E; Tue, 29 Oct 2002 09:34:48 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id g9THYarF094461; Tue, 29 Oct 2002 18:34:37 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: freebsd-hackers@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer In-Reply-To: Your message of "Tue, 29 Oct 2002 18:27:12 +0100." <20021029182712.A1479@gicco.homeip.net> Date: Tue, 29 Oct 2002 18:34:36 +0100 Message-ID: <94460.1035912876@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20021029182712.A1479@gicco.homeip.net>, Hanspeter Roth writes: > On Oct 18 at 20:45, Maxim Sobolev spoke: > >> again, then again ad infinitum. The same effect if you'll mount >> write-protected floppy in read/write mode. This is just lame, but I'm not willing to to take a shouting match with the person who committed this brain-damage. >As of a write-protected floppy, why is it allowd to be mounted as >writeable? >The mount should be degraded to readonly or rejected. That's a slightly more involved issue because you would have to actually try to write to it before you find out that you can't. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 9:47:26 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2823737B401 for ; Tue, 29 Oct 2002 09:47:26 -0800 (PST) Received: from gicco.homeip.net (dclient80-218-75-109.hispeed.ch [80.218.75.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0832643E7B for ; Tue, 29 Oct 2002 09:47:25 -0800 (PST) (envelope-from hampi@rootshell.be) Received: (from idefix@localhost) by gicco.homeip.net (8.11.6/8.11.6) id g9THlOG01710 for freebsd-hackers@FreeBSD.ORG; Tue, 29 Oct 2002 18:47:24 +0100 (CET) (envelope-from hampi@rootshell.be) Date: Tue, 29 Oct 2002 18:47:24 +0100 From: Hanspeter Roth To: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer Message-ID: <20021029184724.A1682@gicco.homeip.net> Reply-To: freebsd-hackers@FreeBSD.ORG Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <20021029182712.A1479@gicco.homeip.net> <94460.1035912876@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <94460.1035912876@critter.freebsd.dk>; from phk@critter.freebsd.dk on Tue, Oct 29, 2002 at 06:34:36PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Oct 29 at 18:34, Poul-Henning Kamp spoke: > That's a slightly more involved issue because you would have to > actually try to write to it before you find out that you can't. Isn't there a means to determine the state of the protection before the mount is attempted? -Hanspeter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 10: 2: 2 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F104537B401 for ; Tue, 29 Oct 2002 10:02:01 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A4EE43E77 for ; Tue, 29 Oct 2002 10:01:58 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id g9TI1mrF094803 for ; Tue, 29 Oct 2002 19:01:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer In-Reply-To: Your message of "Tue, 29 Oct 2002 18:47:24 +0100." <20021029184724.A1682@gicco.homeip.net> Date: Tue, 29 Oct 2002 19:01:48 +0100 Message-ID: <94802.1035914508@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20021029184724.A1682@gicco.homeip.net>, Hanspeter Roth writes: > On Oct 29 at 18:34, Poul-Henning Kamp spoke: > >> That's a slightly more involved issue because you would have to >> actually try to write to it before you find out that you can't. > >Isn't there a means to determine the state of the protection before >the mount is attempted? As far as I know there isn't. I'm not sure if it is a device driver (morituri te salutem!) or hardware issue. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 10: 2:44 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 665F437B401 for ; Tue, 29 Oct 2002 10:02:43 -0800 (PST) Received: from mail1.qc.uunet.ca (mail1.qc.uunet.ca [198.168.54.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8921B43E6E for ; Tue, 29 Oct 2002 10:02:41 -0800 (PST) (envelope-from anarcat@espresso-com.com) Received: from xtanbul.espresso-com.com ([216.94.147.57]) by mail1.qc.uunet.ca (8.10.2/8.10.2) with ESMTP id g9TI2XZ15656 for ; Tue, 29 Oct 2002 13:02:33 -0500 Received: from anarcat by xtanbul.espresso-com.com with local (Exim 3.36 #1 (Debian)) id 186ah9-0004NC-00 for ; Tue, 29 Oct 2002 13:02:27 -0500 Date: Tue, 29 Oct 2002 13:02:27 -0500 From: The Anarcat To: freebsd-hackers@freebsd.org Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer Message-ID: <20021029180227.GA16435@xtanbul.espresso-com.com> References: <20021029182712.A1479@gicco.homeip.net> <94460.1035912876@critter.freebsd.dk> <20021029184724.A1682@gicco.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021029184724.A1682@gicco.homeip.net> User-Agent: Mutt/1.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue Oct 29, 2002 at 06:47:24PM +0100, Hanspeter Roth wrote: > > Isn't there a means to determine the state of the protection before > the mount is attempted? No. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 10:53:43 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2C6B37B404 for ; Tue, 29 Oct 2002 10:53:41 -0800 (PST) Received: from HAL9000.homeunix.com (12-232-220-15.client.attbi.com [12.232.220.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27E3643E42 for ; Tue, 29 Oct 2002 10:53:41 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id g9TIrbTx021161; Tue, 29 Oct 2002 10:53:37 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id g9TIrbSK021160; Tue, 29 Oct 2002 10:53:37 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Tue, 29 Oct 2002 10:53:37 -0800 From: David Schultz To: Poul-Henning Kamp Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer Message-ID: <20021029185337.GA21064@HAL9000.homeunix.com> Mail-Followup-To: Poul-Henning Kamp , freebsd-hackers@FreeBSD.ORG References: <20021029184724.A1682@gicco.homeip.net> <94802.1035914508@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <94802.1035914508@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Poul-Henning Kamp : > >Isn't there a means to determine the state of the protection before > >the mount is attempted? > > As far as I know there isn't. I'm not sure if it is a device driver > (morituri te salutem!) or hardware issue. I believe most floppy drives can be queried for both their write-protect status and whether the inserted disk has been changed. If someone cared enough, these bits could be used to protect users from themselves. IMO, the retry-forever bug is the real problem, but I'm a bit skeptical that it's easy to solve safely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 10:55:22 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 826B937B401 for ; Tue, 29 Oct 2002 10:55:21 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B34543E4A for ; Tue, 29 Oct 2002 10:55:19 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id g9TIt8rF095857; Tue, 29 Oct 2002 19:55:08 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: David Schultz Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer In-Reply-To: Your message of "Tue, 29 Oct 2002 10:53:37 PST." <20021029185337.GA21064@HAL9000.homeunix.com> Date: Tue, 29 Oct 2002 19:55:08 +0100 Message-ID: <95856.1035917708@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20021029185337.GA21064@HAL9000.homeunix.com>, David Schultz writes: >IMO, the retry-forever bug is the >real problem, but I'm a bit skeptical that it's easy to solve >safely. Just revert the commit which added it recently. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 10:55:32 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B07437B408 for ; Tue, 29 Oct 2002 10:55:31 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DC5343E8A for ; Tue, 29 Oct 2002 10:55:31 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.5/8.12.5) with ESMTP id g9TItLFC009948; Tue, 29 Oct 2002 10:55:21 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.5/8.12.5/Submit) id g9TItHsq009943; Tue, 29 Oct 2002 10:55:17 -0800 (PST) (envelope-from dillon) Date: Tue, 29 Oct 2002 10:55:17 -0800 (PST) From: Matthew Dillon Message-Id: <200210291855.g9TItHsq009943@apollo.backplane.com> To: Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: i am looking for a 5 volt signal References: <3DBC42AF.C68F31B0@mindspring.com> <200210272207.g9RM76sX091839@apollo.backplane.com> <200210271935.12396.soralx@cydem.zp.ua> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :The output signals don't go straight from the chip - do they? :I've seen few KOhms resistors on most boards for each output pin. : :27.10.2002; 19:32:00 :[SorAlx] http://cydem.zp.ua/ It depends on the chip. Most modern serial driver chips have series resistors on the outputs, inside the chip, and do not need any external current limiting (which is what the resistor does in effect). Parallel port chips typically do not have output resistors and instead depend on beefy TTL output stages, and a good motherboard manufacturer will put series resistors on those pins. All modern chips have diode protection on their outputs but you can still zap them (static shock it to death). Serial pins tend to be far, far more robust then parallel port pins due to having to go through level converters to get the right voltages on outputs and to be able to handle +/-12V on inputs. For example, most serial driver chips can handle up to +/-25V on their inputs before they blow up. Try putting even +12V on a parallel port pin and you will likely fry the chip, even with an external series resistor, and an external series resistor alone will not stop a big static shock, only a Zener diode is fast enough to do that. An external series resistor is there strictly for current limiting purposes. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 11: 2:29 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B4BC37B401 for ; Tue, 29 Oct 2002 11:02:28 -0800 (PST) Received: from smtp.melim.com.br (aririba.melim.com.br [200.215.110.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 049A143E6E for ; Tue, 29 Oct 2002 11:02:27 -0800 (PST) (envelope-from ivan@melim.com.br) Received: from saoroque2 (ressacada.melim.com.br [200.215.110.4]) by smtp.melim.com.br (Postfix) with ESMTP id D916AFCFD for ; Tue, 29 Oct 2002 16:01:15 -0300 (EST) Message-ID: <034c01c27f76$23494cb0$27a8a8c0@melim.com.br> Reply-To: "Ivan Marquetti Ostermann" From: "Ivan Marquetti Ostermann" To: References: <94802.1035914508@critter.freebsd.dk> Subject: Date: Tue, 29 Oct 2002 16:08:09 -0200 Organization: Ivan Marquetti Ostermann MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 12:31: 2 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D117F37B401 for ; Tue, 29 Oct 2002 12:31:01 -0800 (PST) Received: from HAL9000.homeunix.com (12-232-220-15.client.attbi.com [12.232.220.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id C28AC43E42 for ; Tue, 29 Oct 2002 12:31:00 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id g9TKUrTx021423; Tue, 29 Oct 2002 12:30:53 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id g9TKUrdC021422; Tue, 29 Oct 2002 12:30:53 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Tue, 29 Oct 2002 12:30:53 -0800 From: David Schultz To: Poul-Henning Kamp Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer Message-ID: <20021029203053.GA21387@HAL9000.homeunix.com> Mail-Followup-To: Poul-Henning Kamp , freebsd-hackers@FreeBSD.ORG References: <20021029185337.GA21064@HAL9000.homeunix.com> <95856.1035917708@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <95856.1035917708@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Poul-Henning Kamp : > In message <20021029185337.GA21064@HAL9000.homeunix.com>, David Schultz writes: > > >IMO, the retry-forever bug is the > >real problem, but I'm a bit skeptical that it's easy to solve > >safely. > > Just revert the commit which added it recently. Recently? I know that the bug was present at least six months ago, and probably earlier as well. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 12:32:25 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 328D437B401 for ; Tue, 29 Oct 2002 12:32:24 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35A0143E77 for ; Tue, 29 Oct 2002 12:32:23 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id g9TKWDrF097532; Tue, 29 Oct 2002 21:32:13 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: David Schultz Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer In-Reply-To: Your message of "Tue, 29 Oct 2002 12:30:53 PST." <20021029203053.GA21387@HAL9000.homeunix.com> Date: Tue, 29 Oct 2002 21:32:13 +0100 Message-ID: <97531.1035923533@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20021029203053.GA21387@HAL9000.homeunix.com>, David Schultz writes: >Thus spake Poul-Henning Kamp : >> In message <20021029185337.GA21064@HAL9000.homeunix.com>, David Schultz writes: >> >> >IMO, the retry-forever bug is the >> >real problem, but I'm a bit skeptical that it's easy to solve >> >safely. >> >> Just revert the commit which added it recently. > >Recently? I know that the bug was present at least six months >ago, and probably earlier as well. That's "recently" enough for me :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 13: 8:36 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DF9637B401 for ; Tue, 29 Oct 2002 13:08:36 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 2F8A943E6E for ; Tue, 29 Oct 2002 13:08:35 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 88052 invoked by uid 1000); 29 Oct 2002 21:08:35 -0000 Date: Tue, 29 Oct 2002 13:08:35 -0800 (PST) From: Nate Lawson To: Doug Barton Cc: Kenneth Culver , Chuck Robey , "Wilkinson,Alex" , hackers@FreeBSD.org Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? In-Reply-To: <20021028180337.H3316-100000@master.gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 28 Oct 2002, Doug Barton wrote: > On Mon, 28 Oct 2002, Kenneth Culver wrote: > > > > I'd probably steer clear of the western digital drives as well. Yes the > > > > make that "stear" clear. > > Ummm... why? "steer" is a word with multiple meanings. I can't find > "stear" anywhere. Mu. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 13:11:19 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48BE937B401 for ; Tue, 29 Oct 2002 13:11:18 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id DA5CE43E3B for ; Tue, 29 Oct 2002 13:11:17 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 88067 invoked by uid 1000); 29 Oct 2002 21:11:18 -0000 Date: Tue, 29 Oct 2002 13:11:18 -0800 (PST) From: Nate Lawson To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: RE: Command used to trace the stack of a process In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 29 Oct 2002, John Baldwin wrote: > On 29-Oct-2002 Zhihui Zhang wrote: > > > > I remember there is a command in either gdb or ddb which enable you to > > display the stack of a particular process. Can anyone tell me if there is > > such a command and what the command is? Thanks! > > In ddb you can do 'tr ' where is the PID of the process. In gdb, it's bt. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 13:25: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD78D37B401 for ; Tue, 29 Oct 2002 13:25:01 -0800 (PST) Received: from flamingo.mail.pas.earthlink.net (flamingo.mail.pas.earthlink.net [207.217.120.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CE0343E88 for ; Tue, 29 Oct 2002 13:25:01 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0057.cvx22-bradley.dialup.earthlink.net ([209.179.198.57] helo=mindspring.com) by flamingo.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 186drA-0001wm-00 for freebsd-hackers@FreeBSD.ORG; Tue, 29 Oct 2002 13:25:00 -0800 Message-ID: <3DBEFC5A.5468CADD@mindspring.com> Date: Tue, 29 Oct 2002 13:23:38 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer References: <20021029182712.A1479@gicco.homeip.net> <94460.1035912876@critter.freebsd.dk> <20021029184724.A1682@gicco.homeip.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hanspeter Roth wrote: > On Oct 29 at 18:34, Poul-Henning Kamp spoke: > > That's a slightly more involved issue because you would have to > > actually try to write to it before you find out that you can't. > > Isn't there a means to determine the state of the protection before > the mount is attempted? You can write 0x04ss (sense drive status on standard parameter for drive and head select 'ss') to port 0x03F5; then read disk status register 3 for one byte: bit meaning --- ------------ 7 No drive fault 6 Write protected (1 = protected) 5 Drive ready (1 = ready) 4 Head is on track zero (1 = on track 0) 3 Two sided (1 = two sided, 0 = one sided) 2 Head select (0 = side 0, 1 = side 1) 1 | 0 | bit 1 bit 0 meaning ----- ----- ------------ 0 0 drive 0 selected 0 1 drive 1 selected 1 0 drive 2 selected 1 1 drive 3 selected You can detect "disk change" by selecting a sidk, and then reading 0x03F7 (this works on all PC hardware on or after the IBM PC AT). The byte you read is only interesting for bit 7, unless you can verify that specific controller being used. If bit 7 is zero, then there is a disk present, and it has not been changed. If bit 7 is set, then there is no diskette present, or the disk has not been changed. Therefore, by repeating this operation twice, and seeing a 1 -> 0 transition for bit 7, you can tell a disk is present, or seeing a 1 -> 1 persistance, you can tell there is no disk present (e.g. you will need to save "one behind" on status for this to be useful in detecting both changes and missing disks). Note that this works on 3.5" disks, but only works on 5.25" disks that are 1.2M or larger. In addition, many systems fail to wire up the "disk change" or "disk present" lines from the floppy drive to the controller, hard wiring the disk as being present and unchanged at all times. So "disk change" is unreliable. "If all else fails, read the documentation..." -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 14:13:19 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1AE3A37B401 for ; Tue, 29 Oct 2002 14:13:18 -0800 (PST) Received: from HAL9000.homeunix.com (12-232-220-15.client.attbi.com [12.232.220.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94FEC43E4A for ; Tue, 29 Oct 2002 14:13:17 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id g9TMDETx021672; Tue, 29 Oct 2002 14:13:14 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id g9TMDE50021671; Tue, 29 Oct 2002 14:13:14 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Tue, 29 Oct 2002 14:13:14 -0800 From: David Schultz To: Poul-Henning Kamp Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer Message-ID: <20021029221314.GA21640@HAL9000.homeunix.com> Mail-Followup-To: Poul-Henning Kamp , freebsd-hackers@FreeBSD.ORG References: <20021029203053.GA21387@HAL9000.homeunix.com> <97531.1035923533@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <97531.1035923533@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Poul-Henning Kamp : > >Recently? I know that the bug was present at least six months > >ago, and probably earlier as well. > > That's "recently" enough for me :-) > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe ^^^^^^^^^^^^^^^^^^ Ah yes, I should have guessed. Do you happen to know at what point it was non-broken? The problem seems nontrivial to fix, given that you have to be able to propagate the failure up to the filesystem and cancel all dependent metadata updates in order to maintain correctness. That's why it seems easier to me to just destory the failed buffers on unmount, but maybe I'm missing something. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 15:20:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 624FC37B404 for ; Tue, 29 Oct 2002 15:20:58 -0800 (PST) Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1785A43E3B for ; Tue, 29 Oct 2002 15:20:57 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from onyx ([128.226.182.171]) by bingnet2.cc.binghamton.edu (8.11.6/8.11.6) with ESMTP id g9TNKro12123; Tue, 29 Oct 2002 18:20:53 -0500 (EST) Date: Tue, 29 Oct 2002 18:20:52 -0500 (EST) From: Zhihui Zhang X-Sender: zzhang@onyx To: Nate Lawson Cc: freebsd-hackers@freebsd.org Subject: RE: Command used to trace the stack of a process In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks. The backtrace often gives something like: + 0x350 Is there a way to quickly determine the correponding source code line? -Zhihui On Tue, 29 Oct 2002, Nate Lawson wrote: > On Tue, 29 Oct 2002, John Baldwin wrote: > > On 29-Oct-2002 Zhihui Zhang wrote: > > > > > > I remember there is a command in either gdb or ddb which enable you to > > > display the stack of a particular process. Can anyone tell me if there is > > > such a command and what the command is? Thanks! > > > > In ddb you can do 'tr ' where is the PID of the process. > > In gdb, it's bt. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 15:40:44 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 981C837B401 for ; Tue, 29 Oct 2002 15:40:43 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id AAB0043E75 for ; Tue, 29 Oct 2002 15:40:42 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 88415 invoked by uid 1000); 29 Oct 2002 23:40:42 -0000 Date: Tue, 29 Oct 2002 15:40:42 -0800 (PST) From: Nate Lawson To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: RE: Command used to trace the stack of a process In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG l *routine + 0x350 or if you use a core file with symbols (-g), gdb will do it automatically. Please read the gdb docs for better info. On Tue, 29 Oct 2002, Zhihui Zhang wrote: > > Thanks. The backtrace often gives something like: > > + 0x350 > > Is there a way to quickly determine the correponding source code line? > > -Zhihui > > On Tue, 29 Oct 2002, Nate Lawson wrote: > > > On Tue, 29 Oct 2002, John Baldwin wrote: > > > On 29-Oct-2002 Zhihui Zhang wrote: > > > > > > > > I remember there is a command in either gdb or ddb which enable you to > > > > display the stack of a particular process. Can anyone tell me if there is > > > > such a command and what the command is? Thanks! > > > > > > In ddb you can do 'tr ' where is the PID of the process. > > > > In gdb, it's bt. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 16:29:27 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99C0637B401 for ; Tue, 29 Oct 2002 16:29:26 -0800 (PST) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B2B343E4A for ; Tue, 29 Oct 2002 16:29:24 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id BA03053C4F; Wed, 30 Oct 2002 10:59:12 +1030 (CST) Date: Wed, 30 Oct 2002 10:59:12 +1030 From: Greg 'groggy' Lehey To: Daniel O'Connor Cc: Kenneth Culver , Chuck Robey , "Wilkinson,Alex" , hackers@FreeBSD.ORG Subject: Disk reliability (was: Tagged Command Queuing or Larger Cache ?) Message-ID: <20021030002912.GB74811@wantadilla.lemis.com> References: <20021028205222.G61008-100000@alpha.yumyumyum.org> <1035857031.77698.57.camel@chowder.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1035857031.77698.57.camel@chowder.localdomain> User-Agent: Mutt/1.4i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday, 29 October 2002 at 2:03:50 +0000, Daniel O'Connor wrote: > On Tue, 2002-10-29 at 01:54, Kenneth Culver wrote: >>> I haven't had any trouble with the WDxxxBB drives - the WDxxxAA drives >>> are pretty unreliable though. >>> >> Hrmm, I havn't tried those, but just about every WD drive I've used has >> ended up with problems which were of course handled by the warranty, but >> even then, I still had to reinstall the os and pull a bunch of stuff from >> my backups which was a pain to do for each failure. Like I said, just my >> personal experience. I don't think the new 8MB cache drives have been out >> long enough to actually develop the problems I've seen on WD drives >> though. > > Yes, but my point is that the AA drives are bad, but the BB drives seem > good. I have been using them for a while (~1 year) without trouble. I've had trouble with BB drives. Given that they have (or had) a 3 year warranty, 1 year of experience isn't very much to go by. > Personally I find that no HD manufacturer has a good reputation - > they have all made trashy drives at one point. Give the general time > it takes for problems to surface vs product lifetimes makes deciding > what to buy a PITA :( That's a more valid point. Note that WD and Seagate have dropped their warranty on IDE drives from 3 years to 1 year. What does this say to you? Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 16:36:27 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B37C637B401; Tue, 29 Oct 2002 16:36:25 -0800 (PST) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id D769643E77; Tue, 29 Oct 2002 16:36:22 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from localhost (localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.4/8.12.3) with ESMTP id g9U0aBbT021479; Wed, 30 Oct 2002 11:06:11 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Subject: Re: Disk reliability (was: Tagged Command Queuing or Larger Cache ?) From: "Daniel O'Connor" To: "Greg 'groggy' Lehey" Cc: Kenneth Culver , Chuck Robey , "Wilkinson,Alex" , hackers@FreeBSD.org In-Reply-To: <20021030002912.GB74811@wantadilla.lemis.com> References: <20021028205222.G61008-100000@alpha.yumyumyum.org> <1035857031.77698.57.camel@chowder.localdomain> <20021030002912.GB74811@wantadilla.lemis.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 30 Oct 2002 11:06:11 +1030 Message-Id: <1035938171.435.2.camel@chowder.gsoft.com.au> Mime-Version: 1.0 X-Spam-Score: -3.4 () IN_REP_TO X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 2002-10-30 at 10:59, Greg 'groggy' Lehey wrote: > I've had trouble with BB drives. Given that they have (or had) a 3 What trouble? > year warranty, 1 year of experience isn't very much to go by. Hah, well not anymore.. I agree with your assessment about 1 vs 3 years, but as I said below it is basically impossible to know in advance. > > Personally I find that no HD manufacturer has a good reputation - > > they have all made trashy drives at one point. Give the general time > > it takes for problems to surface vs product lifetimes makes deciding > > what to buy a PITA :( > > That's a more valid point. > > Note that WD and Seagate have dropped their warranty on IDE drives > from 3 years to 1 year. What does this say to you? You can buy JB drives which have both a larger cache and a longer warranty. You can also purchase an extended warranty (but it costs about the same as the price difference between the BB and JB drives) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 16:42:36 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D993337B401; Tue, 29 Oct 2002 16:42:34 -0800 (PST) Received: from ns.aus.com (adsl-66-127-242-2.dsl.sntc01.pacbell.net [66.127.242.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CBEB43E77; Tue, 29 Oct 2002 16:42:24 -0800 (PST) (envelope-from rsharpe@ns.aus.com) Received: from localhost (rsharpe@localhost) by ns.aus.com (8.11.6/8.11.6) with ESMTP id g9U13Y205269; Wed, 30 Oct 2002 11:33:34 +1030 Date: Wed, 30 Oct 2002 11:33:34 +1030 (CST) From: Richard Sharpe To: "Greg 'groggy' Lehey" Cc: "Daniel O'Connor" , Kenneth Culver , Chuck Robey , "Wilkinson,Alex" , Subject: Re: Disk reliability (was: Tagged Command Queuing or Larger Cache ?) In-Reply-To: <20021030002912.GB74811@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 30 Oct 2002, Greg 'groggy' Lehey wrote: > On Tuesday, 29 October 2002 at 2:03:50 +0000, Daniel O'Connor wrote: > > On Tue, 2002-10-29 at 01:54, Kenneth Culver wrote: > >>> I haven't had any trouble with the WDxxxBB drives - the WDxxxAA drives > >>> are pretty unreliable though. > >>> > >> Hrmm, I havn't tried those, but just about every WD drive I've used has > >> ended up with problems which were of course handled by the warranty, but > >> even then, I still had to reinstall the os and pull a bunch of stuff from > >> my backups which was a pain to do for each failure. Like I said, just my > >> personal experience. I don't think the new 8MB cache drives have been out > >> long enough to actually develop the problems I've seen on WD drives > >> though. > > > > Yes, but my point is that the AA drives are bad, but the BB drives seem > > good. I have been using them for a while (~1 year) without trouble. > > I've had trouble with BB drives. Given that they have (or had) a 3 > year warranty, 1 year of experience isn't very much to go by. > > > Personally I find that no HD manufacturer has a good reputation - > > they have all made trashy drives at one point. Give the general time > > it takes for problems to surface vs product lifetimes makes deciding > > what to buy a PITA :( > > That's a more valid point. > > Note that WD and Seagate have dropped their warranty on IDE drives > from 3 years to 1 year. What does this say to you? Hmmm, from what I remember, they did that for the 5400RPM drives, not the 7200RPM drives! Regards ----- Richard Sharpe, rsharpe@ns.aus.com, rsharpe@samba.org, sharpe@ethereal.com, http://www.richardsharpe.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 17:28:26 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE57437B401 for ; Tue, 29 Oct 2002 17:28:24 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8AEC43E75 for ; Tue, 29 Oct 2002 17:28:24 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id 8E54B2A88D; Tue, 29 Oct 2002 17:28:24 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Daniel O'Connor , Chuck Robey , Kenneth Culver , "Wilkinson, Alex" , hackers@FreeBSD.ORG Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? In-Reply-To: <20021029103133.GA18812@HAL9000.homeunix.com> Date: Tue, 29 Oct 2002 17:28:24 -0800 From: Peter Wemm Message-Id: <20021030012824.8E54B2A88D@canning.wemm.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Schultz wrote: > Thus spake Peter Wemm : > > Actually, not even then. Modern IDE drives only write entire tracks at a > > time. If you modify a single sector, then the drive has to read the entire > > track into the buffer, in-place edit the sector, and then rewrite the entir e > > track. > [...] > > And that completely blows FFS's assumptions out of the water. And what > > is sad is that many SCSI disks are similar these days. But not all of > > them (I'm told). > > I've heard this before. It would be very useful to have > information about which drives have this misfeature, but I guess > it isn't the sort of thing that hard drive manufacturers like to > advertise. Does anyone have any data on track-writing drives? IBM used to claim it as a feature and have patents on it. As best as I can tell, all IDE disks have it since about 1999 or so. Quantum and IBM certainly did, as it was a way of getting the drive capacity up and reducing the cost. One way that you can tell is by seeing how big the slowdown is when write caching is turned off and whether you see the same slowdown slowdown regardless of any sector interleaving. ie: if writing to every 10th or 20th (or whatever) sector is just as slow as writing to every sector with write caching turned off, then you have a track-write drive. This is because every single sector write causes the entire track to be written. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 18:14:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D32237B401 for ; Tue, 29 Oct 2002 18:14:09 -0800 (PST) Received: from 002.216-123-229-0.interbaun.com (002.216-123-229-0.interbaun.com [216.123.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AA3C43E6E for ; Tue, 29 Oct 2002 18:14:07 -0800 (PST) (envelope-from soralx@cydem.zp.ua) Received: from 254.216-123-229-0.interbaun.com ([192.168.0.3]) by 002.216-123-229-0.interbaun.com (8.11.6/8.11.6) with ESMTP id g9U2E5i03339 for ; Tue, 29 Oct 2002 19:14:06 -0700 (MST) (envelope-from soralx@cydem.zp.ua) Content-Type: text/plain; charset="iso-8859-1" From: To: freebsd-hackers@FreeBSD.ORG Subject: Re: i am looking for a 5 volt signal Date: Mon, 28 Oct 2002 18:13:59 -0700 X-Mailer: KMail [version 1.4] References: <200210271935.12396.soralx@cydem.zp.ua> <200210291855.g9TItHsq009943@apollo.backplane.com> In-Reply-To: <200210291855.g9TItHsq009943@apollo.backplane.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200210281813.59491.soralx@cydem.zp.ua> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > :The output signals don't go straight from the chip - do they? > :I've seen few KOhms resistors on most boards for each output pin. > An external series resistor is there strictly for current > limiting purposes. Yep, that's why I asked if manufacturers usually put external resistors. I tried to short all the wires together and on the ground :) from an old ISA paraller port controller card - it didn't blow up. So the message to the author of this thread: check for resistors on your mboard, if it's the old one, in series with the outputs, so that you can be sure that you won't kill the controller during experiments... 28.10.2002; 18:05:15 [SorAlx] http://cydem.zp.ua/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 29 18:16:35 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7545637B401 for ; Tue, 29 Oct 2002 18:16:34 -0800 (PST) Received: from 002.216-123-229-0.interbaun.com (002.216-123-229-0.interbaun.com [216.123.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id C71AE43E97 for ; Tue, 29 Oct 2002 18:16:33 -0800 (PST) (envelope-from soralx@cydem.zp.ua) Received: from 254.216-123-229-0.interbaun.com ([192.168.0.3]) by 002.216-123-229-0.interbaun.com (8.11.6/8.11.6) with ESMTP id g9U2GVi03343 for ; Tue, 29 Oct 2002 19:16:32 -0700 (MST) (envelope-from soralx@cydem.zp.ua) Content-Type: text/plain; charset="iso-8859-1" From: To: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer Date: Mon, 28 Oct 2002 18:16:25 -0700 X-Mailer: KMail [version 1.4] References: <94460.1035912876@critter.freebsd.dk> In-Reply-To: <94460.1035912876@critter.freebsd.dk> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200210281816.25889.soralx@cydem.zp.ua> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > >As of a write-protected floppy, why is it allowd to be mounted as > >writeable? > >The mount should be degraded to readonly or rejected. This would not be very convenient - a person may want to remove the write protection without remounting the floppy. 28.10.2002; 18:14:52 [SorAlx] http://cydem.zp.ua/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 30 4: 8:15 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94D3F37B404 for ; Wed, 30 Oct 2002 04:08:14 -0800 (PST) Received: from gicco.homeip.net (dclient80-218-75-109.hispeed.ch [80.218.75.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C45243E7B for ; Wed, 30 Oct 2002 04:08:13 -0800 (PST) (envelope-from hampi@rootshell.be) Received: (from idefix@localhost) by gicco.homeip.net (8.11.6/8.11.6) id g9UC8AC01482 for freebsd-hackers@freebsd.org; Wed, 30 Oct 2002 13:08:10 +0100 (CET) (envelope-from hampi@rootshell.be) Date: Wed, 30 Oct 2002 13:08:10 +0100 From: Hanspeter Roth To: freebsd-hackers@freebsd.org Subject: removing slice chair from a running system Message-ID: <20021030130810.A1412@gicco.homeip.net> Reply-To: freebsd-hackers@freebsd.org Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, diskspace is getting cheaper nowadays and the number of primary slices (partitions) proportionally stays the same and several OS' love primary slices. So far I have a `master' OS which permanently occupies a slice and which remaps slice entries of `slave' OS'. But when I have slave1 OS running and want to reboot to slave2 OS I first reboot the master OS and do the remapping before I reboot slave2 OS. What happens with FreeBSD if it's slice entry is removed in the MBR before it is shutdown? Can it safely shutdown and unmount like this? The slice entries in the MBR are probably needed by the boot selector, by fdisk, by disklabel and when mounting foreign filesystems and maybe by fsck. Is a valid slice entry required by FreeBSD before/during shutdown? -Hanspeter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 30 5:14: 1 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F0EC37B401 for ; Wed, 30 Oct 2002 05:13:59 -0800 (PST) Received: from boadicea.adminhell.org (boadicea.adminhell.org [213.9.30.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id B327C43E42 for ; Wed, 30 Oct 2002 05:13:50 -0800 (PST) (envelope-from kai@adminhell.org) Received: from adminhell.org (gw.adesso.de [195.138.52.2]) by boadicea.adminhell.org (Postfix) with ESMTP id 3759714664; Wed, 30 Oct 2002 14:13:37 +0100 (CET) Date: Wed, 30 Oct 2002 14:13:35 +0100 Subject: FYI: FreeBSD and Intel/ICP Vortex Raid-Controllers Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v546) Cc: achim.leubner@intel.com To: freebsd-hackers@freebsd.org From: Kai Gallasch Content-Transfer-Encoding: 7bit Message-Id: <65ADD54D-EC09-11D6-A13F-0050E425E67E@adminhell.org> X-Mailer: Apple Mail (2.546) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, a few days ago I looked through the LINT file of the stable kernel sources and wondered if the "iir" RAID device would also support the ICP vortex line of RAID controllers (INTEL recently bought the manufacturer ICP and with it its whole productline of controllers) So I asked one of the contacts for the "iir" named in the LINT - achim.leubner@intel.com - if ICP Vortex controllers are also supported.. Achim had this to say.. ---snip--- Hello Kai, the "iir" driver supports the ICP vortex controller line AND the intel controller line. You must not use another ICP specific driver. Regards, Achim ----------------------------------------------------- Achim Leubner Research & Development ICP vortex Computersysteme GmbH, an Intel company Gostritzer Str. 61-63 D-01217 Dresden, Germany Phone: +49-351-871-8291 Fax: +49-351-871-8448 Mail: achim.leubner@intel.com Url: www.icp-vortex.com -----Original Message----- From: Kai Gallasch [mailto:kai@adminhell.org] Sent: Wednesday, October 30, 2002 11:08 AM To: Leubner, Achim Subject: FreeBSD and Intel/ICP Vortex Raid-Controllers Hello, does the device "iir" in the kernel sources of FreeBSD stable also support the ICP Vortex Raid-Controller line, or do I still have to use the FreeBSD driver delivered by ICP Vortex? I found the following in the LINT file of the freebsd kernel sources.. --snip-- # # Intel Integrated RAID controllers. # This driver was developed and is maintained by Intel. Contacts # at Intel for this driver are # "Kannanthanam, Boji T" and # "Leubner, Achim" . # device iir --snip-- Proposal: The "iir" comment section of the LINT file in stable should mention that ICP vortex controllers are also supported by the "iir" driver. Cheers, Kai. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 30 7:37:33 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 799D937B502 for ; Wed, 30 Oct 2002 07:37:24 -0800 (PST) Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0958843E3B for ; Wed, 30 Oct 2002 07:37:24 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 743 invoked from network); 30 Oct 2002 15:37:26 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail16.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 30 Oct 2002 15:37:26 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id g9UFbMn5025682; Wed, 30 Oct 2002 10:37:22 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 30 Oct 2002 10:37:22 -0500 (EST) From: John Baldwin To: Nate Lawson Subject: RE: Command used to trace the stack of a process Cc: freebsd-hackers@freebsd.org, Zhihui Zhang Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 29-Oct-2002 Nate Lawson wrote: > l *routine + 0x350 or if you use a core file with symbols (-g), gdb will > do it automatically. Please read the gdb docs for better info. You can also use 'nm' with grep to find routine's start address. Then add the offset to that and use 'addr2line' to find the line number. This might be easier to throw into a shell script than firing up gdb for example (not to mention quicker). > On Tue, 29 Oct 2002, Zhihui Zhang wrote: > >> >> Thanks. The backtrace often gives something like: >> >> + 0x350 >> >> Is there a way to quickly determine the correponding source code line? >> >> -Zhihui >> >> On Tue, 29 Oct 2002, Nate Lawson wrote: >> >> > On Tue, 29 Oct 2002, John Baldwin wrote: >> > > On 29-Oct-2002 Zhihui Zhang wrote: >> > > > >> > > > I remember there is a command in either gdb or ddb which enable you to >> > > > display the stack of a particular process. Can anyone tell me if there is >> > > > such a command and what the command is? Thanks! >> > > >> > > In ddb you can do 'tr ' where is the PID of the process. >> > >> > In gdb, it's bt. >> > >> > >> > To Unsubscribe: send mail to majordomo@FreeBSD.org >> > with "unsubscribe freebsd-hackers" in the body of the message >> > >> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 30 8:52:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6C9B37B401; Wed, 30 Oct 2002 08:52:40 -0800 (PST) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A5AD43E97; Wed, 30 Oct 2002 08:52:39 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (localhost [127.0.0.1]) by haldjas.folklore.ee (8.12.3/8.11.3) with ESMTP id g9UGqGOs013654; Wed, 30 Oct 2002 18:52:16 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.12.3/8.12.3/Submit) with ESMTP id g9UGqC0o013651; Wed, 30 Oct 2002 18:52:12 +0200 (EET) Date: Wed, 30 Oct 2002 18:52:12 +0200 (EET) From: Narvi To: "Greg 'groggy' Lehey" Cc: "Daniel O'Connor" , Kenneth Culver , Chuck Robey , "Wilkinson,Alex" , Subject: Re: Disk reliability (was: Tagged Command Queuing or Larger Cache ?) In-Reply-To: <20021030002912.GB74811@wantadilla.lemis.com> Message-ID: <20021030184732.U9982-100000@haldjas.folklore.ee> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 30 Oct 2002, Greg 'groggy' Lehey wrote: > On Tuesday, 29 October 2002 at 2:03:50 +0000, Daniel O'Connor wrote: > > On Tue, 2002-10-29 at 01:54, Kenneth Culver wrote: > >>> I haven't had any trouble with the WDxxxBB drives - the WDxxxAA drives > >>> are pretty unreliable though. > >>> > >> Hrmm, I havn't tried those, but just about every WD drive I've used has > >> ended up with problems which were of course handled by the warranty, but > >> even then, I still had to reinstall the os and pull a bunch of stuff from > >> my backups which was a pain to do for each failure. Like I said, just my > >> personal experience. I don't think the new 8MB cache drives have been out > >> long enough to actually develop the problems I've seen on WD drives > >> though. > > > > Yes, but my point is that the AA drives are bad, but the BB drives seem > > good. I have been using them for a while (~1 year) without trouble. > > I've had trouble with BB drives. Given that they have (or had) a 3 > year warranty, 1 year of experience isn't very much to go by. > > > Personally I find that no HD manufacturer has a good reputation - > > they have all made trashy drives at one point. Give the general time > > it takes for problems to surface vs product lifetimes makes deciding > > what to buy a PITA :( > > That's a more valid point. > > Note that WD and Seagate have dropped their warranty on IDE drives > from 3 years to 1 year. What does this say to you? That the cost cutting and pricewars on IDE drives are close to the point where the drives are essentially disposables - buy it, use until fails, throw away and buy a new(er) model. > > Greg > -- > See complete headers for address and phone numbers > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 30 13:54:38 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0E3D37B404 for ; Wed, 30 Oct 2002 13:54:32 -0800 (PST) Received: from dclient217-162-112-2.hispeed.ch (dclient80-218-56-43.hispeed.ch [80.218.56.43]) by mx1.FreeBSD.org (Postfix) with SMTP id 1EFAD43E3B for ; Wed, 30 Oct 2002 13:54:31 -0800 (PST) (envelope-from philipp.stutz@gmx.ch) Received: (qmail 670 invoked from network); 30 Oct 2002 21:54:30 -0000 Received: from goofy.home (HELO gmx.ch) (192.168.1.10) by obelix.home with SMTP; 30 Oct 2002 21:54:30 -0000 Message-ID: <3DC05516.5000603@gmx.ch> Date: Wed, 30 Oct 2002 22:54:30 +0100 From: Philipp Stutz User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org Subject: core dump from ffs_write - i think Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG in the last few days i had three core dumps. the machine was up for a few month without a problem. this is the backtrace of the third core dump (haven't got vmcore.X of the others): IdlePTD at phsyical address 0x00354000 initial pcb at physical address 0x002c5dc0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0257d0a stack pointer = 0x10:0xc4ce0c04 frame pointer = 0x10:0xc4ce0c30 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 5 (syncer) interrupt mask = none trap number = 12 panic: page fault syncing disks... 30 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 done Uptime: 3h9m34s dumping to dev #ad/0x20002, offset 117160068 dump ata0: resetting devices .. done 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 1 5 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 487 if (dumping++) { (kgdb) where #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 #1 0xc0169084 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:316 #2 0xc01694d1 in panic (fmt=0xc0298aac "%s") at /usr/src/sys/kern/kern_shutdown.c:595 #3 0xc0259570 in trap_fatal (frame=0xc4ce0bc4, eva=0) at /usr/src/sys/i386/i386/trap.c:974 #4 0xc025920d in trap_pfault (frame=0xc4ce0bc4, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:867 #5 0xc0258d7f in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = -1042837504, tf_esi = 0, tf_ebp = -993129424, tf_isp = -993129488, tf_ebx = 4096, tf_edx = -1042837504, tf_ecx = 1024, tf_eax = -1042837504, tf_trapno = 12, tf_err = 0, tf_eip = -1071284982, tf_cs = 8, tf_eflags = 66070, tf_esp = -993129180, tf_ss = -993129208}) at /usr/src/sys/i386/i386/trap.c:466 #6 0xc0257d0a in generic_bcopy () #7 0xc021aabd in ffs_write (ap=0xc4ce0ccc) at /usr/src/sys/ufs/ufs/ufs_readwrite.c:531 #8 0xc09b8e6f in ?? () #9 0xc02328d6 in vnode_pager_generic_putpages (vp=0xc5074b00, m=0xc4ce0de4, bytecount=4096, flags=0, rtvals=0xc4ce0db4) at vnode_if.h:363 #10 0xc09b8cab in ?? () #11 0xc02326fa in vnode_pager_putpages (object=0xc505ea20, m=0xc4ce0de4, count=1, sync=0, rtvals=0xc4ce0db4) at vnode_if.h:1147 #12 0xc022f5e5 in vm_pageout_flush (mc=0xc4ce0de4, count=1, flags=0) at /usr/src/sys/vm/vm_pager.h:145 #13 0xc022c4d2 in vm_object_page_collect_flush (object=0xc505ea20, p=0xc04b4708, curgeneration=11141, pagerflags=0) at /usr/src/sys/vm/vm_object.c:800 #14 0xc022c0d5 in vm_object_page_clean (object=0xc505ea20, start=0, end=0, flags=4) at /usr/src/sys/vm/vm_object.c:602 #15 0xc01992ba in vfs_msync (mp=0xc091c000, flags=2) at /usr/src/sys/kern/vfs_subr.c:2710 #16 0xc01995cb in sync_fsync (ap=0xc4ce0f7c) at /usr/src/sys/kern/vfs_subr.c:2971 #17 0xc0197b47 in sched_sync () at vnode_if.h:558 $ uname -a FreeBSD obelix.home 4.7-STABLE FreeBSD 4.7-STABLE #0: Wed Oct 30 02:04:53 CET 2002 phil@asterix. home:/usr/obj/usr/src/sys/OBELIX i386 i had to run fsck manualy. all drives use softupdates. the kernel was cvsuped yesterday. phil i'm not (yet) subscribed to this list so please cc and excuse a non-native speaker... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 30 14:17:49 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFED337B401; Wed, 30 Oct 2002 14:17:48 -0800 (PST) Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1E5C43E6E; Wed, 30 Oct 2002 14:17:47 -0800 (PST) (envelope-from keramida@freebsd.org) Received: from gray.sea.gr (patr530-b196.otenet.gr [212.205.244.204]) by mailsrv.otenet.gr (8.12.6/8.12.6) with ESMTP id g9UMHiun027062; Thu, 31 Oct 2002 00:17:46 +0200 (EET) Received: from gray.sea.gr (gray [127.0.0.1]) by gray.sea.gr (8.12.6/8.12.6) with ESMTP id g9UMHBW1016658; Thu, 31 Oct 2002 00:18:05 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by gray.sea.gr (8.12.6/8.12.6/Submit) id g9UKQL4m008698; Wed, 30 Oct 2002 22:26:21 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Wed, 30 Oct 2002 22:26:20 +0200 From: Giorgos Keramidas To: "Greg 'groggy' Lehey" Cc: hackers@freebsd.org Subject: Re: Disk reliability (was: Tagged Command Queuing or Larger Cache ?) Message-ID: <20021030202620.GD1882@gray.sea.gr> References: <20021028205222.G61008-100000@alpha.yumyumyum.org> <1035857031.77698.57.camel@chowder.localdomain> <20021030002912.GB74811@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021030002912.GB74811@wantadilla.lemis.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-10-30 10:59, Greg 'groggy' Lehey wrote: > That's a more valid point. > > Note that WD and Seagate have dropped their warranty on IDE drives > from 3 years to 1 year. What does this say to you? That I am a terribly lucky man to have bought my WD disk one year ago. The warranty that came with it explicitly mentions 3 years :-) I'll have to find another disk manufacturer in about 1.5 year or so, but looking for the "currently best thing" is part of the plan anyway, so no big worries until then. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 30 14:40:36 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8450337B412 for ; Wed, 30 Oct 2002 14:40:30 -0800 (PST) Received: from dclient217-162-112-2.hispeed.ch (dclient80-218-56-43.hispeed.ch [80.218.56.43]) by mx1.FreeBSD.org (Postfix) with SMTP id F027F43E42 for ; Wed, 30 Oct 2002 14:40:28 -0800 (PST) (envelope-from philipp.stutz@gmx.ch) Received: (qmail 360 invoked from network); 30 Oct 2002 22:40:27 -0000 Received: from goofy.home (HELO gmx.ch) (192.168.1.10) by obelix.home with SMTP; 30 Oct 2002 22:40:27 -0000 Message-ID: <3DC05FDB.1020607@gmx.ch> Date: Wed, 30 Oct 2002 23:40:27 +0100 From: Philipp Stutz User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: core dump from ffs_write - i think References: <3DC05516.5000603@gmx.ch> In-Reply-To: <3DC05516.5000603@gmx.ch> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG had an other core dump (looks almost the same): IdlePTD at phsyical address 0x00354000 initial pcb at physical address 0x002c5dc0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0257d0a stack pointer = 0x10:0xc4ce0c04 frame pointer = 0x10:0xc4ce0c30 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 5 (syncer) interrupt mask = none trap number = 12 panic: page fault syncing disks... 30 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 done Uptime: 3h9m34s dumping to dev #ad/0x20002, offset 117160068 dump ata0: resetting devices .. done 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 1 5 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 487 if (dumping++) { (kgdb) where #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 #1 0xc0169084 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:316 #2 0xc01694d1 in panic (fmt=0xc0298aac "%s") at /usr/src/sys/kern/kern_shutdown.c:595 #3 0xc0259570 in trap_fatal (frame=0xc4ce0bc4, eva=0) at /usr/src/sys/i386/i386/trap.c:974 #4 0xc025920d in trap_pfault (frame=0xc4ce0bc4, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:867 #5 0xc0258d7f in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = -1042837504, tf_esi = 0, tf_ebp = -993129424, tf_isp = -993129488, tf_ebx = 4096, tf_edx = -1042837504, tf_ecx = 1024, tf_eax = -1042837504, tf_trapno = 12, tf_err = 0, tf_eip = -1071284982, tf_cs = 8, tf_eflags = 66070, tf_esp = -993129180, tf_ss = -993129208}) at /usr/src/sys/i386/i386/trap.c:466 #6 0xc0257d0a in generic_bcopy () #7 0xc021aabd in ffs_write (ap=0xc4ce0ccc) at /usr/src/sys/ufs/ufs/ufs_readwrite.c:531 #8 0xc09b8e6f in ?? () #9 0xc02328d6 in vnode_pager_generic_putpages (vp=0xc5074b00, m=0xc4ce0de4, bytecount=4096, flags=0, rtvals=0xc4ce0db4) at vnode_if.h:363 #10 0xc09b8cab in ?? () #11 0xc02326fa in vnode_pager_putpages (object=0xc505ea20, m=0xc4ce0de4, count=1, sync=0, rtvals=0xc4ce0db4) at vnode_if.h:1147 #12 0xc022f5e5 in vm_pageout_flush (mc=0xc4ce0de4, count=1, flags=0) at /usr/src/sys/vm/vm_pager.h:145 #13 0xc022c4d2 in vm_object_page_collect_flush (object=0xc505ea20, p=0xc04b4708, curgeneration=11141, pagerflags=0) at /usr/src/sys/vm/vm_object.c:800 #14 0xc022c0d5 in vm_object_page_clean (object=0xc505ea20, start=0, end=0, flags=4) at /usr/src/sys/vm/vm_object.c:602 #15 0xc01992ba in vfs_msync (mp=0xc091c000, flags=2) at /usr/src/sys/kern/vfs_subr.c:2710 #16 0xc01995cb in sync_fsync (ap=0xc4ce0f7c) at /usr/src/sys/kern/vfs_subr.c:2971 #17 0xc0197b47 in sched_sync () at vnode_if.h:558 Philipp Stutz wrote: > in the last few days i had three core dumps. the machine was up for a > few month without a problem. this is the backtrace of the third core > dump (haven't got vmcore.X of the others): > > IdlePTD at phsyical address 0x00354000 > initial pcb at physical address 0x002c5dc0 > panicstr: page fault > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0257d0a > stack pointer = 0x10:0xc4ce0c04 > frame pointer = 0x10:0xc4ce0c30 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 5 (syncer) > interrupt mask = none > trap number = 12 > panic: page fault > > syncing disks... 30 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 > done > Uptime: 3h9m34s > > dumping to dev #ad/0x20002, offset 117160068 > dump ata0: resetting devices .. done > 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 > 24 23 22 21 20 19 18 17 16 1 > 5 14 13 12 11 10 9 8 7 6 5 4 3 2 1 > --- > #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 > 487 if (dumping++) { > (kgdb) where > #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 > #1 0xc0169084 in boot (howto=256) at > /usr/src/sys/kern/kern_shutdown.c:316 > #2 0xc01694d1 in panic (fmt=0xc0298aac "%s") at > /usr/src/sys/kern/kern_shutdown.c:595 > #3 0xc0259570 in trap_fatal (frame=0xc4ce0bc4, eva=0) at > /usr/src/sys/i386/i386/trap.c:974 > #4 0xc025920d in trap_pfault (frame=0xc4ce0bc4, usermode=0, eva=0) > at /usr/src/sys/i386/i386/trap.c:867 > #5 0xc0258d7f in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, > tf_edi = -1042837504, > tf_esi = 0, tf_ebp = -993129424, tf_isp = -993129488, tf_ebx = > 4096, tf_edx = -1042837504, > tf_ecx = 1024, tf_eax = -1042837504, tf_trapno = 12, tf_err = 0, > tf_eip = -1071284982, > tf_cs = 8, tf_eflags = 66070, tf_esp = -993129180, tf_ss = > -993129208}) > at /usr/src/sys/i386/i386/trap.c:466 > #6 0xc0257d0a in generic_bcopy () > #7 0xc021aabd in ffs_write (ap=0xc4ce0ccc) at > /usr/src/sys/ufs/ufs/ufs_readwrite.c:531 > #8 0xc09b8e6f in ?? () > #9 0xc02328d6 in vnode_pager_generic_putpages (vp=0xc5074b00, > m=0xc4ce0de4, bytecount=4096, > flags=0, rtvals=0xc4ce0db4) at vnode_if.h:363 > #10 0xc09b8cab in ?? () > #11 0xc02326fa in vnode_pager_putpages (object=0xc505ea20, m=0xc4ce0de4, > count=1, sync=0, > rtvals=0xc4ce0db4) at vnode_if.h:1147 > #12 0xc022f5e5 in vm_pageout_flush (mc=0xc4ce0de4, count=1, flags=0) > at /usr/src/sys/vm/vm_pager.h:145 > #13 0xc022c4d2 in vm_object_page_collect_flush (object=0xc505ea20, > p=0xc04b4708, > curgeneration=11141, pagerflags=0) at /usr/src/sys/vm/vm_object.c:800 > #14 0xc022c0d5 in vm_object_page_clean (object=0xc505ea20, start=0, > end=0, flags=4) > at /usr/src/sys/vm/vm_object.c:602 > #15 0xc01992ba in vfs_msync (mp=0xc091c000, flags=2) at > /usr/src/sys/kern/vfs_subr.c:2710 > #16 0xc01995cb in sync_fsync (ap=0xc4ce0f7c) at > /usr/src/sys/kern/vfs_subr.c:2971 > #17 0xc0197b47 in sched_sync () at vnode_if.h:558 > > $ uname -a > FreeBSD obelix.home 4.7-STABLE FreeBSD 4.7-STABLE #0: Wed Oct 30 > 02:04:53 CET 2002 phil@asterix. > home:/usr/obj/usr/src/sys/OBELIX i386 > > i had to run fsck manualy. all drives use softupdates. the kernel was > cvsuped yesterday. > > phil > > i'm not (yet) subscribed to this list so please cc and excuse a > non-native speaker... > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 30 14:47: 9 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D02B37B401 for ; Wed, 30 Oct 2002 14:47:05 -0800 (PST) Received: from dclient217-162-112-2.hispeed.ch (dclient80-218-56-43.hispeed.ch [80.218.56.43]) by mx1.FreeBSD.org (Postfix) with SMTP id D5FA543E3B for ; Wed, 30 Oct 2002 14:47:03 -0800 (PST) (envelope-from philipp.stutz@gmx.ch) Received: (qmail 450 invoked from network); 30 Oct 2002 22:47:03 -0000 Received: from goofy.home (HELO gmx.ch) (192.168.1.10) by obelix.home with SMTP; 30 Oct 2002 22:47:03 -0000 Message-ID: <3DC06166.3090503@gmx.ch> Date: Wed, 30 Oct 2002 23:47:02 +0100 From: Philipp Stutz User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: core dump from ffs_write - i think References: <3DC05516.5000603@gmx.ch> <3DC05FDB.1020607@gmx.ch> In-Reply-To: <3DC05516.5000603@gmx.ch> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Philipp Stutz wrote: > had an other core dump (looks almost the same): this one was wrong... here the correct one: IdlePTD at phsyical address 0x00354000 initial pcb at physical address 0x002c5dc0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0257d0a stack pointer = 0x10:0xc4ce0c04 frame pointer = 0x10:0xc4ce0c30 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 5 (syncer) interrupt mask = none trap number = 12 panic: page fault syncing disks... 32 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 done Uptime: 1h33m20s dumping to dev #ad/0x20002, offset 117160068 dump ata0: resetting devices .. done 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 1 5 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 487 if (dumping++) { (kgdb) where #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 #1 0xc0169084 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:316 #2 0xc01694d1 in panic (fmt=0xc0298aac "%s") at /usr/src/sys/kern/kern_shutdown.c:595 #3 0xc0259570 in trap_fatal (frame=0xc4ce0bc4, eva=0) at /usr/src/sys/i386/i386/trap.c:974 #4 0xc025920d in trap_pfault (frame=0xc4ce0bc4, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:867 #5 0xc0258d7f in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = -1039855616, tf_esi = 0, tf_ebp = -993129424, tf_isp = -993129488, tf_ebx = 4096, tf_edx = -1039855616, tf_ecx = 1024, tf_eax = -1039855616, tf_trapno = 12, tf_err = 0, tf_eip = -1071284982, tf_cs = 8, tf_eflags = 66070, tf_esp = -993129180, tf_ss = -993129208}) at /usr/src/sys/i386/i386/trap.c:466 #6 0xc0257d0a in generic_bcopy () #7 0xc021aabd in ffs_write (ap=0xc4ce0ccc) at /usr/src/sys/ufs/ufs/ufs_readwrite.c:531 #8 0xc09d5e6f in ?? () #9 0xc02328d6 in vnode_pager_generic_putpages (vp=0xc4de8380, m=0xc4ce0de4, bytecount=4096, flags=0, rtvals=0xc4ce0db4) at vnode_if.h:363 #10 0xc09d5cab in ?? () #11 0xc02326fa in vnode_pager_putpages (object=0xc502c8a0, m=0xc4ce0de4, count=1, sync=0, rtvals=0xc4ce0db4) at vnode_if.h:1147 #12 0xc022f5e5 in vm_pageout_flush (mc=0xc4ce0de4, count=1, flags=0) at /usr/src/sys/vm/vm_pager.h:145 #13 0xc022c4d2 in vm_object_page_collect_flush (object=0xc502c8a0, p=0xc0465f7c, curgeneration=4141, pagerflags=0) at /usr/src/sys/vm/vm_object.c:800 #14 0xc022c0d5 in vm_object_page_clean (object=0xc502c8a0, start=0, end=0, flags=4) at /usr/src/sys/vm/vm_object.c:602 #15 0xc01992ba in vfs_msync (mp=0xc09a9600, flags=2) at /usr/src/sys/kern/vfs_subr.c:2710 #16 0xc01995cb in sync_fsync (ap=0xc4ce0f7c) at /usr/src/sys/kern/vfs_subr.c:2971 #17 0xc0197b47 in sched_sync () at vnode_if.h:558 try to reproduce this again with something other than configuring samba. > Philipp Stutz wrote: > > > in the last few days i had three core dumps. the machine was up for a > > few month without a problem. this is the backtrace of the third core > > dump (haven't got vmcore.X of the others): > > > > IdlePTD at phsyical address 0x00354000 > > initial pcb at physical address 0x002c5dc0 > > panicstr: page fault > > panic messages: > > --- > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0x0 > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xc0257d0a > > stack pointer = 0x10:0xc4ce0c04 > > frame pointer = 0x10:0xc4ce0c30 > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags = interrupt enabled, resume, IOPL = 0 > > current process = 5 (syncer) > > interrupt mask = none > > trap number = 12 > > panic: page fault > > > > syncing disks... 30 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 > > done > > Uptime: 3h9m34s > > > > dumping to dev #ad/0x20002, offset 117160068 > > dump ata0: resetting devices .. done > > 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 > > 24 23 22 21 20 19 18 17 16 1 > > 5 14 13 12 11 10 9 8 7 6 5 4 3 2 1 > > --- > > #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 > > 487 if (dumping++) { > > (kgdb) where > > #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 > > #1 0xc0169084 in boot (howto=256) at > > /usr/src/sys/kern/kern_shutdown.c:316 > > #2 0xc01694d1 in panic (fmt=0xc0298aac "%s") at > > /usr/src/sys/kern/kern_shutdown.c:595 > > #3 0xc0259570 in trap_fatal (frame=0xc4ce0bc4, eva=0) at > > /usr/src/sys/i386/i386/trap.c:974 > > #4 0xc025920d in trap_pfault (frame=0xc4ce0bc4, usermode=0, eva=0) > > at /usr/src/sys/i386/i386/trap.c:867 > > #5 0xc0258d7f in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, > > tf_edi = -1042837504, > > tf_esi = 0, tf_ebp = -993129424, tf_isp = -993129488, tf_ebx = > > 4096, tf_edx = -1042837504, > > tf_ecx = 1024, tf_eax = -1042837504, tf_trapno = 12, tf_err = 0, > > tf_eip = -1071284982, > > tf_cs = 8, tf_eflags = 66070, tf_esp = -993129180, tf_ss = > > -993129208}) > > at /usr/src/sys/i386/i386/trap.c:466 > > #6 0xc0257d0a in generic_bcopy () > > #7 0xc021aabd in ffs_write (ap=0xc4ce0ccc) at > > /usr/src/sys/ufs/ufs/ufs_readwrite.c:531 > > #8 0xc09b8e6f in ?? () > > #9 0xc02328d6 in vnode_pager_generic_putpages (vp=0xc5074b00, > > m=0xc4ce0de4, bytecount=4096, > > flags=0, rtvals=0xc4ce0db4) at vnode_if.h:363 > > #10 0xc09b8cab in ?? () > > #11 0xc02326fa in vnode_pager_putpages (object=0xc505ea20, m=0xc4ce0de4, > > count=1, sync=0, > > rtvals=0xc4ce0db4) at vnode_if.h:1147 > > #12 0xc022f5e5 in vm_pageout_flush (mc=0xc4ce0de4, count=1, flags=0) > > at /usr/src/sys/vm/vm_pager.h:145 > > #13 0xc022c4d2 in vm_object_page_collect_flush (object=0xc505ea20, > > p=0xc04b4708, > > curgeneration=11141, pagerflags=0) at > /usr/src/sys/vm/vm_object.c:800 > > #14 0xc022c0d5 in vm_object_page_clean (object=0xc505ea20, start=0, > > end=0, flags=4) > > at /usr/src/sys/vm/vm_object.c:602 > > #15 0xc01992ba in vfs_msync (mp=0xc091c000, flags=2) at > > /usr/src/sys/kern/vfs_subr.c:2710 > > #16 0xc01995cb in sync_fsync (ap=0xc4ce0f7c) at > > /usr/src/sys/kern/vfs_subr.c:2971 > > #17 0xc0197b47 in sched_sync () at vnode_if.h:558 > > > > $ uname -a > > FreeBSD obelix.home 4.7-STABLE FreeBSD 4.7-STABLE #0: Wed Oct 30 > > 02:04:53 CET 2002 phil@asterix. > > home:/usr/obj/usr/src/sys/OBELIX i386 > > > > i had to run fsck manualy. all drives use softupdates. the kernel was > > cvsuped yesterday. > > > > phil > > > > i'm not (yet) subscribed to this list so please cc and excuse a > > non-native speaker... > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 30 15:40:50 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 793A337B401 for ; Wed, 30 Oct 2002 15:40:49 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 40AEC43E77 for ; Wed, 30 Oct 2002 15:40:49 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 92227 invoked by uid 1000); 30 Oct 2002 23:40:50 -0000 Date: Wed, 30 Oct 2002 15:40:50 -0800 (PST) From: Nate Lawson To: Philipp Stutz Cc: hackers@freebsd.org Subject: Re: core dump from ffs_write - i think In-Reply-To: <3DC06166.3090503@gmx.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Try to figure out where it was in frames 8 and 10 (probably a module). -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 30 16:53:35 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F1BD37B401 for ; Wed, 30 Oct 2002 16:53:34 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94EBC43E7B for ; Wed, 30 Oct 2002 16:53:33 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id TAA27410; Wed, 30 Oct 2002 19:53:33 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g9V0r3824184; Wed, 30 Oct 2002 19:53:03 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15808.32495.60682.290812@grasshopper.cs.duke.edu> Date: Wed, 30 Oct 2002 19:53:03 -0500 (EST) To: Philipp Stutz Cc: hackers@freebsd.org Subject: Re: core dump from ffs_write - i think In-Reply-To: References: <3DC06166.3090503@gmx.ch> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Nate Lawson writes: > Try to figure out where it was in frames 8 and 10 (probably a module). > Try the gdbmods port (/usr/ports/devel/gdbmods) Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 30 21:53:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EE0137B401 for ; Wed, 30 Oct 2002 21:53:09 -0800 (PST) Received: from HAL9000.homeunix.com (12-232-220-15.client.attbi.com [12.232.220.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED5C043E4A for ; Wed, 30 Oct 2002 21:53:08 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id g9V5r5Tx026802; Wed, 30 Oct 2002 21:53:05 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id g9V5qqWF026801; Wed, 30 Oct 2002 21:52:52 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Wed, 30 Oct 2002 21:52:52 -0800 From: David Schultz To: Peter Wemm Cc: "Daniel O'Connor" , Chuck Robey , Kenneth Culver , "Wilkinson, Alex" , hackers@FreeBSD.ORG Subject: Re: [hardware] Tagged Command Queuing or Larger Cache ? Message-ID: <20021031055252.GB26692@HAL9000.homeunix.com> Mail-Followup-To: Peter Wemm , Daniel O'Connor , Chuck Robey , Kenneth Culver , "Wilkinson, Alex" , hackers@FreeBSD.ORG References: <20021029103133.GA18812@HAL9000.homeunix.com> <20021030012824.8E54B2A88D@canning.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021030012824.8E54B2A88D@canning.wemm.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Peter Wemm : > > > Actually, not even then. Modern IDE drives only write entire tracks at a > > > time. If you modify a single sector, then the drive has to read the entire > > > track into the buffer, in-place edit the sector, and then rewrite the entir > e > > > track. [...] > ie: if writing to every 10th or 20th (or whatever) sector is just as slow > as writing to every sector with write caching turned off, then you have a > track-write drive. This is because every single sector write causes the > entire track to be written. I remember you mentioning this trick the last time this topic came up. I was hoping someone had the results of running this test on some actual drives. ;-) Another strategy, I suppose, would be to look at which patents the drives claim to use. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 31 6: 0:22 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B60437B404 for ; Thu, 31 Oct 2002 06:00:20 -0800 (PST) Received: from smtp.www-service.de (smtp.www-service.de [212.77.161.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1C2843E4A for ; Thu, 31 Oct 2002 06:00:18 -0800 (PST) (envelope-from thz@Lennartz-electronic.de) Received: from swd2.tue.le (pD90065DE.dip.t-dialin.net [217.0.101.222]) by smtp.www-service.de (8.11.6/8.11.6) with ESMTP id g9VFHBX10723; Thu, 31 Oct 2002 16:17:12 +0100 Received: from mezcal.tue.le (mezcal.tue.le [192.168.201.20]) by swd2.tue.le (8.12.6/8.12.6) with ESMTP id g9VDxsdt051016; Thu, 31 Oct 2002 14:59:54 +0100 (CET) (envelope-from thz@mezcal.tue.le) Received: from mezcal.tue.le (localhost [127.0.0.1]) by mezcal.tue.le (8.12.6/8.12.3) with ESMTP id g9VDxs1D000512; Thu, 31 Oct 2002 14:59:54 +0100 (CET) (envelope-from thz@mezcal.tue.le) Received: (from thz@localhost) by mezcal.tue.le (8.12.6/8.12.6/Submit) id g9VDxqeP000511; Thu, 31 Oct 2002 14:59:52 +0100 (CET) Date: Thu, 31 Oct 2002 14:59:52 +0100 From: Thomas Zenker To: Poul-Henning Kamp Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer Message-ID: <20021031145952.A457@mezcal.tue.le> Mail-Followup-To: Poul-Henning Kamp , freebsd-hackers@FreeBSD.ORG References: <20021029182712.A1479@gicco.homeip.net> <94460.1035912876@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <94460.1035912876@critter.freebsd.dk>; from phk@critter.freebsd.dk on Tue, Oct 29, 2002 at 06:34:36PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Oct 29, 2002 at 06:34:36PM +0100, Poul-Henning Kamp wrote: > In message <20021029182712.A1479@gicco.homeip.net>, Hanspeter Roth writes: > > On Oct 18 at 20:45, Maxim Sobolev spoke: > > > >> again, then again ad infinitum. The same effect if you'll mount > >> write-protected floppy in read/write mode. > > This is just lame, but I'm not willing to to take a shouting match > with the person who committed this brain-damage. > > >As of a write-protected floppy, why is it allowd to be mounted as > >writeable? > >The mount should be degraded to readonly or rejected. > > That's a slightly more involved issue because you would have to > actually try to write to it before you find out that you can't. for stable I have a patch, which checks during open for write protection of the floppy if FWRITE bit is set and fails with EPERM if this is the case. This works reliably for me. The reason I haven't sent this patch in is, there is a possible conflict with accesses to a second floppy disk drive at the same time. Anyway, better than panic'ing the machine... Actually all accesses to the controller hardware are serialized thru a state machine "fdstate". The Bad Thing is, that this state machine is bound too tight to the strategy (i.e. you get some job done via a buffer or nothing). Best example is the interfacing of formatting via the B_FORMAT/B_XXX kludge. The Right Thing would be to redesign the interface to the state machine to get jobs done from any source (with or without buffer) and maintaining state of write protection. Index: sys/isa/fd.c =================================================================== RCS file: /usr/cvs/FreeBSD/src/sys/isa/fd.c,v retrieving revision 1.176.2.8 diff -u -r1.176.2.8 fd.c --- sys/isa/fd.c 15 May 2002 21:56:14 -0000 1.176.2.8 +++ sys/isa/fd.c 31 Oct 2002 13:06:05 -0000 @@ -1448,6 +1448,21 @@ } } fd->ft = fd_types + type - 1; + if (flags & FWRITE) { /* check for write protection */ + int r, s, st3; + s = splbio(); + set_motor(fdc, fd->fdsu, TURNON); /* select drive */ + r = fd_sense_drive_status(fdc, &st3); + set_motor(fdc, fd->fdsu, TURNOFF); + fdc->state = RESETCTLR; + splx(s); + if(r != 0) + return(ENXIO); + if (st3 & NE7_ST3_WP) { + device_printf(fd->dev, "write protected\n"); + return(EPERM); + } + } fd->flags |= FD_OPEN; /* * Clearing the DMA overrun counter at open time is a bit messy. Cheers, -- Thomas Zenker c/o Lennartz electronic GmbH Bismarckstrasse 136, D-72072 Tuebingen, Germany Phone: +49-(0)7071-93550 Email: thz@lennartz-electronic.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 31 8:23: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 054EA37B401; Thu, 31 Oct 2002 08:23:01 -0800 (PST) Received: from mail2.caramail.com (mail2.caramail.com [213.193.13.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0207C43E3B; Thu, 31 Oct 2002 08:23:00 -0800 (PST) (envelope-from aku.aku@caramail.com) Received: from caramail.com (www57.caramail.com [213.193.13.67]) by mail2.caramail.com (Postfix) with SMTP id 6C6AFC96D; Thu, 31 Oct 2002 17:22:46 +0100 (MET) From: aku aku To: aku.aku@caramail.com Message-ID: <1036081363031381@caramail.com> X-Mailer: Caramail - www.caramail.com X-Originating-IP: [193.251.159.163] Mime-Version: 1.0 Subject: REQUEST FOR INVESTMENT ASSISTANCE. Date: Thu, 31 Oct 2002 17:22:43 GMT+1 Content-Type: multipart/mixed; boundary="=_NextPart_Caramail_0313811036081363_ID" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --=_NextPart_Caramail_0313811036081363_ID Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable From.MR.AKU WILLISON DUKE. Lot 140 Petit Marche, 10 Bp. Abidjan 10,Koumassi, Cote d' Ivoire,West Africa. Dear, REQUEST FOR INVESTMENT ASSISTANCE. Permit me to inform you of my desire of going into business relationship with you. Introducing myself , I am MR.AKU WILLISON DUKE the only son of the late Mr and Mrs Barnabas DUKE , my father was a gold and cocoa merchant based in Accra, Ghana and Abidjan (Ivory Coast ),he was poisoned to death by his business associates on one of their business trips. Before the death of my father on 29th June 2001 in a private hospital here in Abidjan. He secretly called me on his bedside and told me that he has a sum of USD$12.5M Twelve Million five hundred thousand U.S), deposited in Bank in Abidjan Cote D' Ivoire, that he used my name as his only son for the next of kin in depositing of the fund. He also explained to me that it was because of this wealth that he was poisoned by his business associates, that I should seek for a foreign partner in a country of my choice where I will transfer this money and use it for investment purpose such as expansion of his existing cocoa business and real estate management overseas. Please, I am humbly seeking your assistance in the following ways. 1- To assist me in providing an account of yours where this fund can quietly transferred. 2-To serve as the guardian of this fund since I am still in the secondary school. 3) To make arrangement for me to come over to your country to further my education and to help secure a residential permit in your country. 4.TO come down to abidjan in three working visit Moreover, I am willing to offer you 15% of the total sum as compensation for your effort/ Input after the successful transfer of this fund to your nominated account overseas, while 5% will be set aside to offset any expenses we may incure Furthermore, you can indicate your option towards assisting me as I believe that this transaction would be concluded within the shortest possible time if you signify interest to assist me. NB: Please call /contact me immediately you receive this message through the above contact if you are interested. Best Regards MR.AKU W DUKE _________________________________________________________ Gagne une PS2 ! Envoie un SMS avec le code PS au 61166 (0,35 Hors co=FBt du SMS) --=_NextPart_Caramail_0313811036081363_ID-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 31 9: 4:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8804F37B401 for ; Thu, 31 Oct 2002 09:04:58 -0800 (PST) Received: from asgard.ecci.ucr.ac.cr (asgard.ecci.ucr.ac.cr [163.178.104.110]) by mx1.FreeBSD.org (Postfix) with SMTP id B2D5743E7B for ; Thu, 31 Oct 2002 09:04:49 -0800 (PST) (envelope-from braulio@bsolano.com) Received: (qmail 248 invoked from network); 31 Oct 2002 17:10:19 -0000 Received: from unknown (HELO azul) (208.165.58.177) by asgard.ecci.ucr.ac.cr with SMTP; 31 Oct 2002 17:10:19 -0000 Message-ID: <00a201c280ff$8ee519b0$b13aa5d0@azul> From: =?iso-8859-1?Q?Braulio_Jos=E9_Solano_Rojas?= To: Cc: , Subject: Intel PCI Modem Date: Thu, 31 Oct 2002 11:04:18 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello! I have an "Intel V92 HaM Data Fax Voice" Modem. It is a hardware based modem. Mi pnpbios recognizes it as "Simple COMM. controler IRQ12". I would like to hack sio.c in order to get it working. Therefore I think I should add an entry to pci_ids[] like: {hex x, "Intel V92 HaM Data Fax Voice", hex y} But I do not know what are hex x and hex y, or if it is going to work. With dmesg I can see this: pci0 (vendor=0x1813, dev=0x4000) at 9.0 irq 12 And if I do pciconf -l: none0@pci0:9:0: class=0x078000 card=0x00000000 chip=0x40001813 rev=0x02 hdr=0x00 My questions are: * What are hex x and hex y? * If I hack sio.c like I intend to, is my modem going to work? * If so, would be the following line correct in my kernel configuration file: device sio2 at isa? port IO_COM3 irq 12 ? Please, I will appreciate very much your help. I would like very much to connect to Internet so I can build ports, ftp, telnet, :-) Best regards, Braulio Solano To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 31 9: 7:18 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63DBE37B401 for ; Thu, 31 Oct 2002 09:07:16 -0800 (PST) Received: from asgard.ecci.ucr.ac.cr (asgard.ecci.ucr.ac.cr [163.178.104.110]) by mx1.FreeBSD.org (Postfix) with SMTP id 199E843E77 for ; Thu, 31 Oct 2002 09:07:13 -0800 (PST) (envelope-from braulio@bsolano.com) Received: (qmail 300 invoked from network); 31 Oct 2002 17:12:58 -0000 Received: from unknown (HELO azul) (208.165.58.177) by asgard.ecci.ucr.ac.cr with SMTP; 31 Oct 2002 17:12:58 -0000 Message-ID: <00aa01c280ff$ed4d30f0$b13aa5d0@azul> From: =?iso-8859-1?Q?Braulio_Jos=E9_Solano_Rojas?= To: Cc: , Subject: Re: Intel PCI Modem Date: Thu, 31 Oct 2002 11:06:55 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! About this: > I have an "Intel V92 HaM Data Fax Voice" Modem. It is a hardware based > modem. Mi pnpbios recognizes it as "Simple COMM. controler IRQ12". > > I would like to hack sio.c in order to get it working. Therefore I think I > should add an entry to pci_ids[] like: > {hex x, "Intel V92 HaM Data Fax Voice", hex y} > > But I do not know what are hex x and hex y, or if it is going to work. > > With dmesg I can see this: > pci0 (vendor=0x1813, dev=0x4000) at 9.0 irq 12 > > And if I do pciconf -l: > none0@pci0:9:0: class=0x078000 card=0x00000000 chip=0x40001813 rev=0x02 > hdr=0x00 I have found that my modem is in /usr/share/misc/pci_vendors, and if I do a pciconf -lv, I get: none0@pci0:9:0: class=0x078000 card=0x00000000 chip=0x40001813 rev=0x02 hdr=0x00 vendor = 'Ambient Technologies Inc' device = 'Creatix V.90 HaM Modem' class = simple comms It does not have a subclass, is this why I don't see it at boot? > My questions are: > * What are hex x and hex y? > * If I hack sio.c like I intend to, is my modem going to work? > * If so, would be the following line correct in my kernel configuration > file: > device sio2 at isa? port IO_COM3 irq 12 > ? Or do I need a special driver? If this is needed maybe I can try to program one, even if I have to learn lots of technical stuff. Please be gentle, I am not used to technical discussions of FreeBSD. I would like very much to see my modem working, therefore I will appreciate very much your help. Best regards, Braulio Solano Developer - Costa Rica To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 31 10:37:24 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2FD637B401 for ; Thu, 31 Oct 2002 10:37:21 -0800 (PST) Received: from gicco.homeip.net (dclient80-218-72-234.hispeed.ch [80.218.72.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48A2143E7B for ; Thu, 31 Oct 2002 10:37:20 -0800 (PST) (envelope-from hampi@rootshell.be) Received: (from hampi@localhost) by gicco.homeip.net (8.11.6/8.11.6) id g9VIbJH00982 for freebsd-hackers@FreeBSD.ORG; Thu, 31 Oct 2002 19:37:19 +0100 (CET) (envelope-from hampi@rootshell.be) Date: Thu, 31 Oct 2002 19:37:19 +0100 From: Hanspeter Roth To: freebsd-hackers@FreeBSD.ORG Subject: Patch to prevent write-protected floppy from being mounted writable Message-ID: <20021031193719.A940@gicco.homeip.net> Reply-To: freebsd-hackers@FreeBSD.ORG Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <20021029182712.A1479@gicco.homeip.net> <94460.1035912876@critter.freebsd.dk> <20021031145952.A457@mezcal.tue.le> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20021031145952.A457@mezcal.tue.le>; from thz@Lennartz-electronic.de on Thu, Oct 31, 2002 at 02:59:52PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Oct 31 at 14:59, Thomas Zenker spoke: > On Tue, Oct 29, 2002 at 06:34:36PM +0100, Poul-Henning Kamp wrote: > > That's a slightly more involved issue because you would have to > > actually try to write to it before you find out that you can't. > > for stable I have a patch, which checks during open for write > protection of the floppy if FWRITE bit is set and fails with EPERM > if this is the case. This works reliably for me. The reason I haven't > sent this patch in is, there is a possible conflict with accesses > to a second floppy disk drive at the same time. Anyway, better than > panic'ing the machine... > > Actually all accesses to the controller hardware are serialized > thru a state machine "fdstate". The Bad Thing is, that this state > machine is bound too tight to the strategy (i.e. you get some job > done via a buffer or nothing). Best example is the interfacing of > formatting via the B_FORMAT/B_XXX kludge. The Right Thing would > be to redesign the interface to the state machine to get jobs done > from any source (with or without buffer) and maintaining state of > write protection. > > Index: sys/isa/fd.c > =================================================================== > RCS file: /usr/cvs/FreeBSD/src/sys/isa/fd.c,v > retrieving revision 1.176.2.8 > diff -u -r1.176.2.8 fd.c > --- sys/isa/fd.c 15 May 2002 21:56:14 -0000 1.176.2.8 > +++ sys/isa/fd.c 31 Oct 2002 13:06:05 -0000 > @@ -1448,6 +1448,21 @@ > } > } > fd->ft = fd_types + type - 1; > + if (flags & FWRITE) { /* check for write protection */ > + int r, s, st3; > + s = splbio(); > + set_motor(fdc, fd->fdsu, TURNON); /* select drive */ > + r = fd_sense_drive_status(fdc, &st3); > + set_motor(fdc, fd->fdsu, TURNOFF); > + fdc->state = RESETCTLR; > + splx(s); > + if(r != 0) > + return(ENXIO); > + if (st3 & NE7_ST3_WP) { > + device_printf(fd->dev, "write protected\n"); > + return(EPERM); > + } > + } > fd->flags |= FD_OPEN; > /* > * Clearing the DMA overrun counter at open time is a bit messy. > > > Cheers, > > -- Thomas Zenker Hey, exactly! Thank you! Could the core team consider this patch to get merged into 4.8? -Hanspeter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 31 11:15:34 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C802237B401 for ; Thu, 31 Oct 2002 11:15:33 -0800 (PST) Received: from smarthost2.mail.easynet.fr (smarthost2.mail.easynet.fr [212.180.1.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6488A43E6E for ; Thu, 31 Oct 2002 11:15:28 -0800 (PST) (envelope-from richard2@netcourrier.com) Received: from [212.11.34.74] (helo=netcourrier.com) by smarthost2.mail.easynet.fr with esmtp (Exim 3.35 #1 (Debian)) id 187Kms-00058B-00; Thu, 31 Oct 2002 20:15:27 +0100 Message-ID: <3DC165C3.87D0712F@netcourrier.com> Date: Thu, 31 Oct 2002 18:17:55 +0100 From: Richard X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.8-26mdk i586) X-Accept-Language: fr, en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: subscribe freebsd-hackers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 31 13:12:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DBD937B404 for ; Thu, 31 Oct 2002 13:12:41 -0800 (PST) Received: from ella.slis.indiana.edu (ella.slis.indiana.edu [129.79.36.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A66543E8A for ; Thu, 31 Oct 2002 13:12:37 -0800 (PST) (envelope-from jfieber@slis.indiana.edu) Received: from slis.indiana.edu (d-1-1.dhcp-149-159.indiana.edu [149.159.1.1]) by ella.slis.indiana.edu (8.12.2+Sun/8.12.2) with ESMTP id g9VLCaor010293 for ; Thu, 31 Oct 2002 16:12:36 -0500 (EST) Date: Thu, 31 Oct 2002 16:12:36 -0500 Mime-Version: 1.0 (Apple Message framework v546) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Formatting a large (1.3TB) SCSI disk From: John Fieber To: freebsd-hackers@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <7ABB1A10-ED15-11D6-BA17-00039349B214@slis.indiana.edu> X-Mailer: Apple Mail (2.546) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm a bit stumped on this. I have a roughly 1.3 terabyte disk array attached via an Adaptec 39166 controller (on the motherboard of a Dell 2650). I understand there is a gap between the theoretical filesystem size limits and the actual limits which I gather hover around 1TB. Okay, so I can partition the disk and make a couple smaller filesystems. But I can't even get the thing sliced (fdisk) or partitioned (disklabel). sysinstall fdisk & disklabel complain about the geometry and claim to be selecting a more reasonable geometry, and then complain about the more reasonable geometry they selected. Using disklabel to try and set up the disk in "dangerously" dedicated mode (eg, no fdisk stuff) gives me wierd errors when I try to add partitions. If I try and newfs the default c partition, I get console message about block count discrepancies, etc... So obviously disk larger than a terabyte are not exactly plug-n-play (with 4.7 at least) so does anyone who has dealt with this situation have any sage advice? The person using the machine would prefer a single giant filesystem if possible. -john (returning to FreeBSD after a several year diversion in Solaris administration) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 31 19:20: 4 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C2ED37B401 for ; Thu, 31 Oct 2002 19:20:01 -0800 (PST) Received: from marla.namshub.net (marla.namshub.net [66.220.23.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB88343E4A for ; Thu, 31 Oct 2002 19:20:00 -0800 (PST) (envelope-from jwood@joelwood.com) Received: from marla.namshub.net (localhost [127.0.0.1]) by marla.namshub.net (8.12.3/8.12.3) with ESMTP id gA13IDoE024430; Thu, 31 Oct 2002 19:18:13 -0800 (PST) (envelope-from jwood@joelwood.com) Received: from localhost (jwood@localhost) by marla.namshub.net (8.12.3/8.12.3/Submit) with ESMTP id gA13ICe8024427; Thu, 31 Oct 2002 19:18:13 -0800 (PST) X-Authentication-Warning: marla.namshub.net: jwood owned process doing -bs Date: Thu, 31 Oct 2002 19:18:12 -0800 (PST) From: Joel Wood X-X-Sender: jwood@marla.namshub.net To: Kai Gallasch Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FYI: FreeBSD and Intel/ICP Vortex Raid-Controllers In-Reply-To: <65ADD54D-EC09-11D6-A13F-0050E425E67E@adminhell.org> Message-ID: <20021031190211.W24366-100000@marla.namshub.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Also, incase your intrested, you can also use icpcon with the iir driver incase you want to fool with the raid from userland. icpcon looks alot like the interface you get when booting. You can look for failures, rebuild the raid, and get statistics. To use icpcon, you just need to: mknod /dev/iir c 164 0 ln -s /dev/iir /dev/icp You can get icpcon as part of the icp freebsd driver zip from icp-vortex.com. -Joel On Wed, 30 Oct 2002, Kai Gallasch wrote: > Hi, > > a few days ago I looked through the LINT file of the stable kernel > sources and > wondered if the "iir" RAID device would also support the ICP vortex line > of RAID controllers (INTEL recently bought the manufacturer ICP and > with it its whole > productline of controllers) > > So I asked one of the contacts for the "iir" named in the LINT - > achim.leubner@intel.com - > if ICP Vortex controllers are also supported.. > > Achim had this to say.. > > ---snip--- > > Hello Kai, > > the "iir" driver supports the ICP vortex controller line AND the intel > controller line. > You must not use another ICP specific driver. > > Regards, > Achim > > ----------------------------------------------------- > Achim Leubner > Research & Development > ICP vortex Computersysteme GmbH, an Intel company > Gostritzer Str. 61-63 > D-01217 Dresden, Germany > Phone: +49-351-871-8291 > Fax: +49-351-871-8448 > Mail: achim.leubner@intel.com > Url: www.icp-vortex.com > > > -----Original Message----- > From: Kai Gallasch [mailto:kai@adminhell.org] > Sent: Wednesday, October 30, 2002 11:08 AM > To: Leubner, Achim > Subject: FreeBSD and Intel/ICP Vortex Raid-Controllers > > > Hello, > > does the device "iir" in the kernel sources of FreeBSD stable also > support > the ICP Vortex Raid-Controller line, or do I still have to use the > FreeBSD > driver delivered by ICP Vortex? > > I found the following in the LINT file of the freebsd kernel sources.. > > --snip-- > # > # Intel Integrated RAID controllers. > # This driver was developed and is maintained by Intel. Contacts > # at Intel for this driver are > # "Kannanthanam, Boji T" and > # "Leubner, Achim" . > # > device iir > --snip-- > > Proposal: > The "iir" comment section of the LINT file in stable should mention that > ICP vortex controllers are also supported by the "iir" driver. > > Cheers, > Kai. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 31 20:13:20 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 700D737B401 for ; Thu, 31 Oct 2002 20:13:19 -0800 (PST) Received: from server4.hostpoint.ch (server4.hostpoint.ch [62.50.74.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D46743E6E for ; Thu, 31 Oct 2002 20:13:18 -0800 (PST) (envelope-from jukebox-admin@diejukebox.ch) Received: from localhost ([127.0.0.1] helo=server4.hostpoint.ch) by server4.hostpoint.ch with esmtp (Exim 3.36 #1) id 187TBR-00062A-00 for freebsd-hackers@freebsd.org; Fri, 01 Nov 2002 05:13:21 +0100 Date: Fri, 01 Nov 2002 05:13:21 +0100 Message-ID: <20021101041321.7552.76307.Mailman@server4.hostpoint.ch> Subject: blackmusic.ch mailing list memberships reminder From: mailman-owner@server4.hostpoint.ch To: freebsd-hackers@freebsd.org X-No-Archive: yes X-BeenThere: Jukebox@diejukebox.ch X-Mailman-Version: 2.0.13 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server4.hostpoint.ch X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0] X-AntiAbuse: Sender Address Domain - diejukebox.ch Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a reminder, sent out once a month, about your blackmusic.ch mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, Newsletter-request@blackmusic.ch) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@server4.hostpoint.ch. Thanks! Passwords for freebsd-hackers@freebsd.org: List Password // URL ---- -------- Newsletter@blackmusic.ch boxoko http://server4.hostpoint.ch/mailman/options/newsletter_blackmusic.ch/freebsd-hackers%40freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 1 4:24: 1 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9CED37B401 for ; Fri, 1 Nov 2002 04:23:58 -0800 (PST) Received: from MX1.wgate.com (mx1.wgate.com [66.150.46.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 21DF743E88 for ; Fri, 1 Nov 2002 04:23:58 -0800 (PST) (envelope-from msinz@wgate.com) Received: FROM mail.tvol.net BY MX1.wgate.com ; Fri Nov 01 07:18:00 2002 -0500 Received: from sinz.eng.tvol.net ([10.32.2.99]) by mail.tvol.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 41A6MVWR; Fri, 1 Nov 2002 07:23:44 -0500 Received: from wgate.com (localhost [127.0.0.1]) by sinz.eng.tvol.net (8.11.6/8.11.6) with ESMTP id gA1CNZM57841; Fri, 1 Nov 2002 07:23:35 -0500 (EST) (envelope-from msinz@wgate.com) Message-ID: <3DC27247.5040100@wgate.com> Date: Fri, 01 Nov 2002 07:23:35 -0500 From: Michael Sinz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1b) Gecko/20020813 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matt Dillon , freebsd-hackers@freebsd.org Subject: Socket so_linger setting Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG During some parameter limit checking work, I ran into what I believe to be an error in FreeBSD. (Albeit unlikely to be hit) A setsockopt of the SO_LINGER field will cause strange results if the value is set above 32767. This is due to the fact that in struct socket, the so_linger field is a signed short and the parameter passed to setsockopt for linger is a signed long. What happens is that any value between 32768 and 65535 will cause so_linger to be negative. And then getsockopt will return a sign extended negative value in the signed long field for linger. The "trivial" fix is to do the following: ------------------------------------------------------ --- uipc_socket.c Wed May 1 01:13:02 2002 +++ /tmp/uipc_socket.c Fri Nov 1 06:55:10 2002 @@ -1139,7 +1139,8 @@ if (error) goto bad; - so->so_linger = l.l_linger; + /* Limit the value to what fits in so_linger */ + so->so_linger = (l.l_linger > SHRT_MAX ? SHRT_MAX : l.linger); if (l.l_onoff) so->so_options |= SO_LINGER; else ------------------------------------------------------ What this does is limit the value to no more than 32767 (SHRT_MAX) However, I believe the more correct answer is that so_linger should not be a signed value to begin with. The reasoning is that what does a negative so_linger mean? To close the socket before the user does ;^)? It is somewhat obvious that so_linger does not need to be a long. It is not possible to change the API to make the input a short. Limiting the value to 32767 is reasonable (and that is a *vary* long linger time) However, given that negative linger values really don't exist (logically) it would be reasonable to not that field be signed. That would naturally limit the values to being within a valid range and prevent some strange results, specifically when looking at the tsleep() call where the so_linger field is just blindly multiplied by the hz of the system. (around line 312 of uipc_socket.c) A segative so_linger will get sign extended into a negative int (32-bit) (times hz) and then passed to tsleep which just checks for zero, passed on to timeout which then passes it to callout_reset. It turns out that callout_reset will take negative values and make them a single tick... (whew! lucky thing that was there :-) The question I have is: should put together a patch that changes so_linger (and xso_linger) to unsigned? (And make sure there are no bad side effects) or is the trivial fix above what is wanted? [ My personal feeling is that since so_linger has no valid negative value that the field should be unsigned. Not that it matters about improving the range as 32767 is over 9 hours. It is more a matter of "correctness" in the code/representation since the code assumes the value is not negative already. ] -- Michael Sinz -- Director, Systems Engineering -- Worldgate Communications A master's secrets are only as good as the master's ability to explain them to others. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 1 10: 0: 8 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3673737B404 for ; Fri, 1 Nov 2002 10:00:04 -0800 (PST) Received: from neuhaus.s-s-a.com (neuhaus.s-s-a.com [210.163.70.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AB3843E3B for ; Fri, 1 Nov 2002 10:00:01 -0800 (PST) (envelope-from rayinri4do@aol.com) Received: from mx1.mail.yahoo.com (mailhost.mht.co.uk [194.203.204.1]) by neuhaus.s-s-a.com (8.9.3/3.6Wbeta7) with ESMTP id CAA14800; Sat, 2 Nov 2002 02:58:29 +0900 (JST) From: rayinri4do@aol.com Message-ID: <00003f4d5461$0000139f$000045d9@mailin-01.mx.aol.com> To: , , , Cc: , , , Subject: Seek and Find KGKQSUUQSI Date: Fri, 01 Nov 2002 12:00:32 -1800 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG READY TO KNOW? REALLY? CONFIDENTIAL! The SOFTWARE They Want BANNED In all 50 STATES. Why??? Because these secrets were never intended to reach your eyes... Get the facts on anyone Locate Missing Persons, find Lost Relatives, obtain Addresses and Phone Numbers of old school friends, even Skip Trace Dead Beat Spouses. Very Valuable when doing Genealogy projects! In Fact this software is a "Must Have" You'll save 100's of hours... This is not a Private Investigator, but a sophisticated SOFTWARE program DESIGNED to automatically CRACK YOUR CASE with links to thousands of Public Record databases. Find out SECRETS about your relatives,friends, enemies, and everyone else! Even your spouse! With the New,INTERNET SPY AND YOU! It's absolutely astounding! Here's what you can learn. License plate number Get anyone's name and address with just a license plate number Find that girl you met in traffic! Driving record!Get anyone's driving record! Social security number! Trace anyone by social security number! Address!Get anyone's address with just a name! Unlisted phone numbers!!! Get anyone's phone number with just a name even unlisted numbers! Locate! Long lost friends, relatives, a past lover who broke your heart! E-mailSend anonymous e-mail completely untraceable! Dirty secrets! Discover dirty secrets your in-laws don't want you to know! Investigate anyone! Use the sources that private investigators use (all on the Internet)secretly! Ex-spouse! Learn how to get information on an ex-spouse that will help you win in court! (Dig up old skeletons) Criminal search Background check! Find out about your daughter's boyfriend! Find out!If you are being investigated! Neighbors!Learn all about your mysterious neighbors! Find out what they have to hide! People you work with! Be astonished by what you'll learn about people you work with! Education verification! Did he really graduate college? Find out! Internet Spy and You! Software will help you discover ANYTHING about anyone, with clickable hyperlinks and no typing in Internet addresses! Just insert the floppy disk and Go! You will be shocked and amazed by the secrets that can be discovered about absolutely everyone! Find out the secrets they don't want you to know! About others, about yourself! It's INCREDIBLE what you can find out using Internet Spy and You and the Internet! You'll be riveted to your computer screen! Get the software they're trying to ban! Before it's too late! ACT NOW!! ONLY $18.95!! REGULAR PRICE $49.95 ONLY for those who A*C*T within the next 7 days! ORDER NOW AND RECEIVE THE SPY SOFTWARE FOR $18.95! THAT'S RIGHT ONLY $18.95 a $30 savings... ;-)) This offer Can be withdrawn at any time, act within 7 days for the special price. Your price is.......$18.95 add ONLY ............$1.05 Shipping/Handling ...................______ Your Total is only..$20.00 We will SEND YOU the Internet Spy and SOFTWARE so you can begin discovering all the secrets you ever wanted to know! You can Know EVERYTHING about ANYONE with our Internet Spy and Software. Works with all browsers and all versions of AOL! US FUNDS ONLY, MONEY ORDER, CHECKS Foreign money orders must be payable from a US BANK AND IN US FUNDS NO EXCEPTIONS! DON'T WAIT TO GET STARTED... It's as easy as 1, 2, 3. STEP 1 - Print the form below. Or put the requested info neatly printed on any paper. We need this to fill your order!!! STEP 2 - Type or print your order information into the order form section. STEP 3 - Mail order form and payment to the address below. ....ONLY...$20.00 including the SHIPPING/HANDLING! Netsense PO BOX 2033 Columbus, NE 68602-2033 Name: _______________________________________________ Address: _____________________________________________ City/State/Zip: ______________________________________ E-Mail _______________________________________________ DISCLAIMER: The seller of this powerful software resource will not be held responsible for how the purchaser chooses to use it's resources. To be removed from our list alloff1@btamail.net.cn and put Remove in the subject. Thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 1 10:30:32 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DED8437B401; Fri, 1 Nov 2002 10:30:30 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A79E143E3B; Fri, 1 Nov 2002 10:30:29 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id gA1ITtOo091661; Fri, 1 Nov 2002 13:29:55 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 1 Nov 2002 13:29:54 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: hackers@FreeBSD.org Subject: Request for submissions: FreeBSD Bi-Monthly Development Status Report Sept-Oct 2002 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a solicitation for submissions for the September 2002 - October 2002 FreeBSD Bi-Monthly Development Status Report. All submissions are due by October 10, 2002. Submissions should be made by filling out the template found at: http://www.FreeBSD.org/news/status/report-sample.xml Submissions must then be e-mailed to the following address for automated processing (IT HAS CHANGED): monthly@FreeBSD.org Reports must be submitted in the XML format described, or they will be silently dropped. Submissions made to other e-mail addresses will be ignored. If more than one report is submitted for a project, the latest instance will be used. Status reports should be submitted once per project, although project developers may choose to submit additional reports on specific sub-projects of substantial size. Status reports are typically one or two short paragraphs, but the text may be up to 20 lines in length. Submissions are welcome on a variety of topics relating to FreeBSD, including development, documentation, advocacy, and development processes. Submitting developer status reports help maintain an important link between FreeBSD developers, as well as a link to the user and sponsor communities. By submitting a report, you help share information about the rapid progress made by the project, making it easier for advocates to point at the excellent work that's being done! Prior status reports may be viewed at: http://www.FreeBSD.org/news/status/ Of particular interest, rolling up to the 5.0 release, are reports relating to the major architectural projects with results in 5.0, including SMPng, KSE, GEOM, TrustedBSD, UFS2, newcard, firewire, ACPI, IPsec acceleration, and new hardware ports including sparc64 and ia64. Including reports on the status approaching the release, and identifying areas where "must be done" requirements are present for the release will help consumers of FreeBSD get a sense of what they can expect in 5.0, as well as what other developers need to work on in order to make it happen. Robert Watson, Scott Long FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 1 10:33:45 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64D1E37B401; Fri, 1 Nov 2002 10:33:44 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E94443E42; Fri, 1 Nov 2002 10:33:43 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id gA1IX7Oo092656; Fri, 1 Nov 2002 13:33:07 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 1 Nov 2002 13:33:06 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: hackers@FreeBSD.org Subject: Re: Request for submissions: FreeBSD Bi-Monthly Development Status Report Sept-Oct 2002 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 1 Nov 2002, Robert Watson wrote: > All submissions are due by October 10, 2002. Needless to say, the deadline is actually November 10, 2002. Rather than thinking of this as an "off the hook" scenario, think of it as an extra month to submit the status report, starting about a month ago :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 1 10:54:30 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0B8737B401 for ; Fri, 1 Nov 2002 10:54:26 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C88D43E77 for ; Fri, 1 Nov 2002 10:54:26 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.3/8.12.3) with ESMTP id gA1IsNs7012059 for ; Fri, 1 Nov 2002 10:54:24 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.3/8.12.3/Submit) id gA1IsNHl012057 for hackers@freebsd.org; Fri, 1 Nov 2002 10:54:23 -0800 Date: Fri, 1 Nov 2002 10:54:23 -0800 From: Brooks Davis To: hackers@freebsd.org Subject: [brooks@one-eyed-alien.net: [PATCH] switching to if_xname] Message-ID: <20021101105423.A9676@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm trying to get some review for the following patch. I realize it's quite large, but most it is is trivial. The ipfw code is the only thing that worries me significantly. I have promised Kris that I will fix ports that break with this change so you don't need to worry about that issue. I'd like to commit this prior to 5.0-R pending RE approval (post DP2 would be fine if that would help get it out the door). Thanks, Brooks ----- Forwarded message from Brooks Davis ----- From: Brooks Davis Date: Wed, 23 Oct 2002 20:50:38 -0700 To: net@FreeBSD.ORG Subject: [PATCH] switching to if_xname As previously discussed, I've created a patch to replace if_unit and if_name with if_xname in struct ifnet following the example of NetBSD and OpenBSD. I've tried to place the more intresting parts of the diff near the top. This patch will break ports which use libkvm to read interface statistics. This effects at least wmnet and wmnet2 (though both segfault on current without this patch). The patches to fix this should be trivial since most of those applications probably support NetBSD or OpenBSD and I plan to bump __FreeBSD_version. Other then those issues and a generalization of interface globing in IPFW, this patch should be a giant no-op from the user perspective. Real features will come later, but the API/ABI change needs to happen soon or it's going to be a 6.0 feature. I'm running this patch on my laptop with a GENERIC kernel without any problems so far. For all it's size, most of the changes are log() or printf() calls plus a fairly consistant change to each network driver's attach function so this should be generally low impact. The patch is available at the URL below. I tried to send a copy to the list, but it looks like it got silently tossed as too large. If you want a copy e-mailed to you, feel free to ask me for one. http://people.freebsd.org/~brooks/patches/if_xname.diff Please review. Thanks, Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 ----- End forwarded message ----- --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9ws3bXY6L6fI4GtQRAhSAAKC20rlugr41WvZ3kFxjyrehr/Po5wCgzQxG e5UryWvCkKbCFduDjPayARc= =spD5 -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 1 12: 7: 6 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC07E37B401 for ; Fri, 1 Nov 2002 12:07:04 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 9136943E8A for ; Fri, 1 Nov 2002 12:07:04 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 97421 invoked by uid 1000); 1 Nov 2002 20:07:05 -0000 Date: Fri, 1 Nov 2002 12:07:05 -0800 (PST) From: Nate Lawson To: Brooks Davis Cc: hackers@freebsd.org Subject: Re: [PATCH] switching to if_xname In-Reply-To: <20021101105423.A9676@Odin.AC.HMC.Edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You might also try -net or -arch. On Fri, 1 Nov 2002, Brooks Davis wrote: > I'm trying to get some review for the following patch. I realize it's > quite large, but most it is is trivial. The ipfw code is the only thing > that worries me significantly. I have promised Kris that I will fix > ports that break with this change so you don't need to worry about that > issue. > > I'd like to commit this prior to 5.0-R pending RE approval (post DP2 > would be fine if that would help get it out the door). > > Thanks, > Brooks > > http://people.freebsd.org/~brooks/patches/if_xname.diff > > Please review. Couple comments. * You interchangeably use strlcpy and snprintf(... "%s", ...) and even strncpy/strcpy(!). You probably want to go with just strlcpy. * There may be some cases where a string compare is too slow and it needs a unit compare. I'm not familiar with the code that does this but please comment. * Some places seem to still be using a unit number as a local loop counter. Just curious if this has any side effects. * Do the ipfw glob changes break ABI? Overall, I like it. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 1 12: 8:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98FA637B401 for ; Fri, 1 Nov 2002 12:08:56 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E54743E8A for ; Fri, 1 Nov 2002 12:08:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.5/8.12.5) with ESMTP id gA1K8rFC034486; Fri, 1 Nov 2002 12:08:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.5/8.12.5/Submit) id gA1K8rOa034485; Fri, 1 Nov 2002 12:08:53 -0800 (PST) (envelope-from dillon) Date: Fri, 1 Nov 2002 12:08:53 -0800 (PST) From: Matthew Dillon Message-Id: <200211012008.gA1K8rOa034485@apollo.backplane.com> To: Michael Sinz Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Socket so_linger setting References: <3DC27247.5040100@wgate.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I think your patch is fine as is, Mike! Good find! Even though so_linger cannot be negative, it is often convenient to use a signed integer to store the value to avoid unexpected arithmatic results when mixing with signed operations. My quick perusal does not show any cases of this for so_linger, so we could make it unsigned, but I don't see any pressing need to do so. The range check would need to be in there in either case. Can I go ahead and commit it? -Matt Matthew Dillon :During some parameter limit checking work, I ran into what I believe to :be an error in FreeBSD. (Albeit unlikely to be hit) : :A setsockopt of the SO_LINGER field will cause strange results if :the value is set above 32767. : :This is due to the fact that in struct socket, the so_linger field :is a signed short and the parameter passed to setsockopt for linger :is a signed long. : :What happens is that any value between 32768 and 65535 will cause :so_linger to be negative. And then getsockopt will return a sign :extended negative value in the signed long field for linger. : :The "trivial" fix is to do the following: : :------------------------------------------------------ :--- uipc_socket.c Wed May 1 01:13:02 2002 :+++ /tmp/uipc_socket.c Fri Nov 1 06:55:10 2002 :@@ -1139,7 +1139,8 @@ : if (error) : goto bad; : :- so->so_linger = l.l_linger; :+ /* Limit the value to what fits in so_linger */ :+ so->so_linger = (l.l_linger > SHRT_MAX ? SHRT_MAX : l.linger); : if (l.l_onoff) : so->so_options |= SO_LINGER; : else :------------------------------------------------------ : :What this does is limit the value to no more than 32767 (SHRT_MAX) :However, I believe the more correct answer is that so_linger should :not be a signed value to begin with. : :The reasoning is that what does a negative so_linger mean? To :close the socket before the user does ;^)? : :It is somewhat obvious that so_linger does not need to be a long. : :It is not possible to change the API to make the input a short. : :Limiting the value to 32767 is reasonable (and that is a *vary* :long linger time) : :However, given that negative linger values really don't exist :(logically) it would be reasonable to not that field be signed. :That would naturally limit the values to being within a valid :range and prevent some strange results, specifically when :looking at the tsleep() call where the so_linger field is :just blindly multiplied by the hz of the system. (around line :312 of uipc_socket.c) A segative so_linger will get sign extended :into a negative int (32-bit) (times hz) and then passed to tsleep :which just checks for zero, passed on to timeout which then :passes it to callout_reset. It turns out that callout_reset will :take negative values and make them a single tick... (whew! lucky :thing that was there :-) : :The question I have is: should put together a patch that changes :so_linger (and xso_linger) to unsigned? (And make sure there are :no bad side effects) or is the trivial fix above what is wanted? : :[ My personal feeling is that since so_linger has no valid negative : value that the field should be unsigned. Not that it matters : about improving the range as 32767 is over 9 hours. It is more : a matter of "correctness" in the code/representation since the : code assumes the value is not negative already. ] : :-- :Michael Sinz -- Director, Systems Engineering -- Worldgate Communications :A master's secrets are only as good as : the master's ability to explain them to others. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 1 12:23:18 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F2EB37B401 for ; Fri, 1 Nov 2002 12:23:16 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12D4B43E4A for ; Fri, 1 Nov 2002 12:23:16 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.3/8.12.3) with ESMTP id gA1KN5s7029390; Fri, 1 Nov 2002 12:23:05 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.3/8.12.3/Submit) id gA1KN5ZK029385; Fri, 1 Nov 2002 12:23:05 -0800 Date: Fri, 1 Nov 2002 12:23:04 -0800 From: Brooks Davis To: Nate Lawson Cc: Brooks Davis , hackers@FreeBSD.ORG Subject: Re: [PATCH] switching to if_xname Message-ID: <20021101122304.A27263@Odin.AC.HMC.Edu> References: <20021101105423.A9676@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from nate@root.org on Fri, Nov 01, 2002 at 12:07:05PM -0800 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 01, 2002 at 12:07:05PM -0800, Nate Lawson wrote: > Couple comments. >=20 > * You interchangeably use strlcpy and snprintf(... "%s", ...) and even > strncpy/strcpy(!). You probably want to go with just strlcpy. I forgot to sweep for those again. I'll do another pass shortly. > * There may be some cases where a string compare is too slow and it needs > a unit compare. I'm not familiar with the code that does this but please > comment. The only case I recall where unit compare was really in the fast path was in ipfw. In my change, globing is now a bit more expensive since it uses fnmatch instead of ignoring the unit, but the non-globing case should be pretty much the same if not slightly faster (it no longer has to check the unit and the median length of the compared string will only rise by 1 for every one except tunnel servers). > * Some places seem to still be using a unit number as a local loop > counter. Just curious if this has any side effects. We've got a number of devices that really like to know thier unit number. In those cases, I've generally stuffed it into the softc if it wasn't there already. > * Do the ipfw glob changes break ABI? Yes, but I don't think that's a hugh deal. The bigger deal is breaking the network interface API and ABI which in turn breaks a few user land programs that use libkvm ("netstat -r" for exmaple). That's why this is a .0 feature. Thanks, Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9wuKmXY6L6fI4GtQRAi3oAKDLtmcDLS5sdEEtMU15+c+abT4hHACfW1BV IOOp1isEKfnTYOSYqrFTWzs= =8phh -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 1 12:49:58 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87BA037B433 for ; Fri, 1 Nov 2002 12:49:57 -0800 (PST) Received: from MX1.wgate.com (mx1.wgate.com [66.150.46.4]) by mx1.FreeBSD.org (Postfix) with SMTP id A7ED943E75 for ; Fri, 1 Nov 2002 12:49:56 -0800 (PST) (envelope-from msinz@wgate.com) Received: FROM mail.tvol.net BY MX1.wgate.com ; Fri Nov 01 15:38:29 2002 -0500 Received: from sinz.eng.tvol.net ([10.32.2.99]) by mail.tvol.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 41A6M58N; Fri, 1 Nov 2002 15:44:14 -0500 Received: from wgate.com (localhost [127.0.0.1]) by sinz.eng.tvol.net (8.11.6/8.11.6) with ESMTP id gA1Ki5M59536; Fri, 1 Nov 2002 15:44:05 -0500 (EST) (envelope-from msinz@wgate.com) Message-ID: <3DC2E794.5060702@wgate.com> Date: Fri, 01 Nov 2002 15:44:04 -0500 From: Michael Sinz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1b) Gecko/20020813 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Socket so_linger setting References: <3DC27247.5040100@wgate.com> <200211012008.gA1K8rOa034485@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: > I think your patch is fine as is, Mike! Good find! Even though > so_linger cannot be negative, it is often convenient to use a signed > integer to store the value to avoid unexpected arithmatic results > when mixing with signed operations. My quick perusal does not show > any cases of this for so_linger, so we could make it unsigned, but I > don't see any pressing need to do so. The range check would need > to be in there in either case. > > Can I go ahead and commit it? I would at least commit it as a range check... Maybe we should look at changing so_linger to unsigned too. (As I stated before, it "documents" the value range a bit more correctly and, with better compilers, the "math errors" would be warnings if you assumed signed-ness of the value :-) -- Michael Sinz -- Director, Systems Engineering -- Worldgate Communications A master's secrets are only as good as the master's ability to explain them to others. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 1 13: 4:39 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7625F37B401 for ; Fri, 1 Nov 2002 13:04:38 -0800 (PST) Received: from ahmler3.mail.eds.com (ahmler3.mail.eds.com [192.85.154.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8154243E42 for ; Fri, 1 Nov 2002 13:04:37 -0800 (PST) (envelope-from jeff.ward@eds.com) Received: from ahmlir5.mail.eds.com (ahmlir5-2.mail.eds.com [192.85.154.135]) by ahmler3.mail.eds.com (8.11.6/8.11.6) with ESMTP id gA1L4VZ03329 for ; Fri, 1 Nov 2002 16:04:31 -0500 Received: from ahmlir5.mail.eds.com (localhost [127.0.0.1]) by ahmlir5.mail.eds.com (8.11.6/8.11.6) with ESMTP id gA1L4UX29696 for ; Fri, 1 Nov 2002 16:04:30 -0500 (EST) Received: from usahm102.exmi01.exch.eds.com (usahm102.exmi01.exch.eds.com [207.37.138.190]) by ahmlir5.mail.eds.com (8.11.6/8.11.6) with ESMTP id gA1L4Tg29686 for ; Fri, 1 Nov 2002 16:04:29 -0500 (EST) Received: by usahm102.exmi01.exch.eds.com with Internet Mail Service (5.5.2655.51) id <4K5PQAN1>; Fri, 1 Nov 2002 16:04:34 -0500 Message-ID: From: "Ward, Jeff" To: "'FreeBSD-hackers@FreeBSD.org'" Subject: Subscribe Date: Fri, 1 Nov 2002 16:04:25 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.51) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Please subscribe me to the mailing list! Thanks! Jeffrey A. Ward EDS Information Analyst To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 1 13:15:49 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 703DE37B401 for ; Fri, 1 Nov 2002 13:15:48 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id BA3E043E6E for ; Fri, 1 Nov 2002 13:15:44 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 97687 invoked by uid 1000); 1 Nov 2002 21:15:45 -0000 Date: Fri, 1 Nov 2002 13:15:45 -0800 (PST) From: Nate Lawson To: Brooks Davis Cc: hackers@FreeBSD.ORG Subject: Re: [PATCH] switching to if_xname In-Reply-To: <20021101122304.A27263@Odin.AC.HMC.Edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 1 Nov 2002, Brooks Davis wrote: > The bigger deal is breaking > the network interface API and ABI which in turn breaks a few user land > programs that use libkvm ("netstat -r" for exmaple). That's why this is > a .0 feature. > > Thanks, > Brooks Please check the libdnet port and possibly libpcap. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 1 13:41:47 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7084637B401 for ; Fri, 1 Nov 2002 13:41:45 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 072B643E42 for ; Fri, 1 Nov 2002 13:41:45 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.3/8.12.3) with ESMTP id gA1Lfhs7012588; Fri, 1 Nov 2002 13:41:43 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.3/8.12.3/Submit) id gA1LfgxY012587; Fri, 1 Nov 2002 13:41:42 -0800 Date: Fri, 1 Nov 2002 13:41:42 -0800 From: Brooks Davis To: Nate Lawson Cc: Brooks Davis , hackers@FreeBSD.ORG Subject: Re: [PATCH] switching to if_xname Message-ID: <20021101134142.B27263@Odin.AC.HMC.Edu> References: <20021101122304.A27263@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="dTy3Mrz/UPE2dbVg" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from nate@root.org on Fri, Nov 01, 2002 at 01:15:45PM -0800 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --dTy3Mrz/UPE2dbVg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 01, 2002 at 01:15:45PM -0800, Nate Lawson wrote: > On Fri, 1 Nov 2002, Brooks Davis wrote: > > The bigger deal is breaking > > the network interface API and ABI which in turn breaks a few user land > > programs that use libkvm ("netstat -r" for exmaple). That's why this is > > a .0 feature. >=20 > Please check the libdnet port and possibly libpcap. libdnet was already broken by a different change (visability conditionals on IFNAMSIZ), but this change would break it more. It's a pretty simple fix (replace fr_to_ipfw_device with strlcpy). It should be noted that libdnet's ipfw support is already broken because it doesn't handle wildcards. libpcap doesn't require any patches. I've already told kris I'd provide fixes for the ports this change breaks. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --dTy3Mrz/UPE2dbVg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9wvUWXY6L6fI4GtQRAsySAKCcWRhfvbjODbeplNKE4sP9207F+wCeOun5 NQzKu0ARE1lovbajKOJ6eGs= =LlfO -----END PGP SIGNATURE----- --dTy3Mrz/UPE2dbVg-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 2 1:38:31 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E936137B401 for ; Sat, 2 Nov 2002 01:38:29 -0800 (PST) Received: from sage.globe.net.nz (mx.globe.net.nz [203.96.128.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97FEB43E75 for ; Sat, 2 Nov 2002 01:38:28 -0800 (PST) (envelope-from barak@globe.net.nz) Received: from globe.net.nz (ip-210-48-25-203.asiaonline.net.nz [210.48.25.203]) by sage.globe.net.nz (Postfix) with ESMTP id 9E8024B723 for ; Sat, 2 Nov 2002 22:38:09 +1300 (NZDT) Message-ID: <3DC453E9.5040500@globe.net.nz> Date: Sun, 03 Nov 2002 11:38:33 +1300 From: Dave & Julia Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc3) Gecko/20020811 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Hi folk, needing basic help with shared mem Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi folk, I appoligize in advance if I am emailing to the wrong group as I just got this group from an EFNet question response. What I am trying to do is create a simple message parser library for applications to access, NOT using any of the main BSD components like pipes and sockets. The coding of the message system should not be a problem, my problem lies in creating a library that can hold and parse information between calling applications. i.e my library has for example a func PostMessage(int app, word msg); and SendMessage(int app, word msg); for argument sake.. All this is fine, however, I am finding, that even though I have created my library as a shared lib, each time the lib is called by an app the lib knows nothing about the previous calls. I am assuming this is in the memory handling technique, and this is where I am falling down, thus far I have played with shm_open() and mmap() but still, it's like the lib can't find anything from a previous call to itself by another app. (I HOPE I make sense here). Just incase I am not making myself clear, this is the flow of how my app works... MainApp (which runs continuously in an infinte loop loads the Lib at time of init and calls SetUpMapping, since this app is always in memory, then the lib is not unloaded.) bool SetUpMapping() { int dis_mem = shm_open("Physical", O_RDWR | O_CREAT, 00777 ); if (dis_mem==-1) { printf("Failed to mmap()\n"); return false; } dis_buff=(char*)mmap(0, 1048576, PROT_READ | PROT_WRITE, MAP_SHARED , dis_mem, 0); return true; } Calling Applications call the Libs GetMessage and SendMessage functions which work with dis_buff to determine messages etc. Part of my problem here is probably sdue to the fact that I have just come over from the Win32 platform and grasping some of the POSIX compliance coding is a tad different to WinAPI and Direct3D ;) I appreciate any help I can get on this, Thanks in advance, Dave Smith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 2 1:52:46 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94FCC37B401 for ; Sat, 2 Nov 2002 01:52:45 -0800 (PST) Received: from flamingo.mail.pas.earthlink.net (flamingo.mail.pas.earthlink.net [207.217.120.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1239743E75 for ; Sat, 2 Nov 2002 01:52:45 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0019.cvx21-bradley.dialup.earthlink.net ([209.179.192.19] helo=mindspring.com) by flamingo.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 187uxL-0003PE-00; Sat, 02 Nov 2002 01:52:39 -0800 Message-ID: <3DC39FFF.8C35192B@mindspring.com> Date: Sat, 02 Nov 2002 01:50:55 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dave & Julia Smith Cc: freebsd-hackers@freebsd.org Subject: Re: Hi folk, needing basic help with shared mem References: <3DC453E9.5040500@globe.net.nz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wrong list... try -questions, next time. Dave & Julia Smith wrote: > i.e my library has for example a func PostMessage(int app, word msg); > and SendMessage(int app, word msg); > for argument sake.. man msgsnd man msgrcv -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 2 6:11:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC74637B401; Sat, 2 Nov 2002 06:11:36 -0800 (PST) Received: from ooo.no (fb171157.ot.FreeBit.NE.JP [61.203.171.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id B63E943E3B; Sat, 2 Nov 2002 06:11:34 -0800 (PST) (envelope-from cmail11jp@yahoo.co.jp) Received: from 5-A ([192.168.0.3]) by ooo.no (8.9.3+3.2W/3.7W) with SMTP id XAA26378; Sat, 2 Nov 2002 23:10:58 +0900 Message-Id: <200211021410.XAA26378@ooo.no> From: =?iso-2022-jp?B?Y21haWwxMWpw?= To: =?iso-2022-jp?B?am9ueQ==?=@ooo.no Reply-To: cmail11jp@yahoo.co.jp Date: Sat, 02 Nov 2002 23:06:51 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoRUU7UiVhITwlazktOXAbKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG <送信者> 電子メール広告社 今後、広告をご希望しない方はここへ (必ず本文にあなたのメールアドレスのみをお書き下さい） king11@vesta.dti.ne.jp メールアドレスをご記入してください。 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　03-3544-6222 FAX　03-3544-6218 =============================================================== 問題商品ばかり集めましたので、消される恐れがありますので お申込みはお早めに！ =============================================================== ■　会員制ロリータクラブ　■ ＤＶＤ・ビデオ2500円から ハイクオリティ画質での販売マニアックな映像の数々 まずはカタログ請求お待ちしております（局留めでの請求可能） お手元にお届く封筒には、お客様のお名前のみ！当社名は一切入りません。 カタログをお見て、お申し込みください。 無料カタログ http://www.allround.sib.ru/roriclub/ http://magazine.japanesebabies.com/roriclub/ 　　　　　　　　　　　　　　　　　　　　　会員制ロリータクラブ ＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿ ■SEXフレンド募集■ 真剣にSEXフレンドを探している人だけ集合！ 全国どこでも近くの人をプロフィール付ですぐ紹介。 若い人から熟年までいっぱいいるよ! ダンナに内緒のHを楽しもう！ http://www.allround.sib.ru/sex/ http://magazine.japanesebabies.com/sex/ レモンクラブ ＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿ ■ももがはじけてぶどうがゆれる■ しじみともものコラボレーション ロリータビデオ（ＤＶＤ）専門 いつまで営業できるかわかりません ご注文はお早めに！ http://www.allround.sib.ru/roridvd/rori/ http://magazine.japanesebabies.com/roridvd/rori/ 作品例 少女伝説　名古屋団地9　少女の道草 などなど132作品。好評発売中！ 　(^-^)/~ロリ炉利ムトー ＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿ ■　ＳＭパートナー紹介即日　■ ＳＭパートナー即日紹介。 援助やSMクラブとは違い、ＳＭ愛好者だけが集う会。 全国でご紹介できます。 あなたのプレイにあわせて即日紹介。 プレイ代金は一切かかりません。 年齢は20歳以上。 http://www.allround.sib.ru/sm/ http://magazine.japanesebabies.com/sm/ 　　　　　　　　　　　　　　　　　　　　　　　　　ＳＭクラブ ――――――――――――――――――――――――――――――― ■　人形師が作った傑作品　■ 抱きしめたくなるようなお人形さんが作れました。 爆発的大ヒット商品！ 数に制限があるため、お申し込みはお早めに！ ☆局部まで本物そっくりに制作したため、店頭販売できません。 http://www.allround.sib.ru/dachi/dollc/ http://magazine.japanesebabies.com/dachi/dollc/ 　　　　　　　　　　　　　　　　　　　　　人形師宮川デザイン ――――――――――――――――――――――――――――――― ■　逆援助交際くらぶ　■ 素敵な男性と朝まで二人・・・。 素敵な男性を今すぐ貴女の元へ向かわせます。 全国ネットワークですぐに紹介ＯＫ。 若い女性も遠慮しないで遊びまくろう！ １回限り、長期、何でもあり。 ♪女性に優しくできる男性スタッフも同時募集中♪ http://www.allround.sib.ru/enjyo/ http://magazine.japanesebabies.com/enjyo/ 　　　　　　　　　　　　　　　　　　　　　　　　　逆援助会 ――――――――――――――――――――――――――――――― ■　マリファナの種　■ マリファナがたまらなく好きな人、どうぞ、ここへ。 あぶないくすりの情報も手に入るよ！ 「絶対に悪用しないでください。」 http://www.allround.sib.ru/mari/ http://magazine.japanesebabies.com/mari/ 　　　　　　　　　　　　　　　　　　　　　　　　　森　正男 ――――――――――――――――――――――――――――――― ■　新装開店！激安セール　■ AV.DVD激安セール 他店では手に入らないものばかし･･････ 以前のように、よろしくお願いします。 他店に負けず激安料金！ http://www.allround.sib.ru/pink/ http://magazine.japanesebabies.com/pink/ 　　　 　　　　　　　　　　　　　　　　　　　　　　　　　美少女クラブ ――――――――――――――――――――――――――――――― To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 2 13:36:36 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06EF537B48F for ; Sat, 2 Nov 2002 13:36:33 -0800 (PST) Received: from fed1mtao03.cox.net (fed1mtao03.cox.net [68.6.19.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 902CA43E42 for ; Sat, 2 Nov 2002 13:36:32 -0800 (PST) (envelope-from dchrist@cox.net) Received: from linus ([68.4.176.221]) by fed1mtao03.cox.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP id <20021102213633.GWKR21998.fed1mtao03.cox.net@linus> for ; Sat, 2 Nov 2002 16:36:33 -0500 From: "David Christensen" To: Subject: Receiving EROFS error creating a new file system Date: Sat, 2 Nov 2002 13:36:26 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm working on a disk driver and it seems to be working for random data read/write operations when I use dd, so now I'm trying to create a filesystem on the drive. I've partitioned the drive and created a slice to format, but when I lay down a filesystem I get the following error: diablo# newfs /dev/xyzd0s1e Warning: Block size restricts cylinders per group to 398. /dev/xyzd0s1e: 2097152 sectors in 512 cylinders of 1 tracks, 4096 sectors 1024.0MB in 2 cyl groups (398 c/g, 796.00MB/g, 8192 i/g) super-block backups (for fsck -b #) at: 32, 1630240 write error: 0 newfs: wtfs: Read-only file system The disk driver never receives the request to write data to block 0, so the write() call returns EROFS error from somewhere else. Why might I be receiving this error? If I partition another drive and create an identical slice, I don't get the error. David Christensen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message