Re: People running with LOCALBASE set to something other than /usr/local?
* From: Kris Kennaway <[EMAIL PROTECTED]> * On Wed, 23 Aug 2000, Mike Meyer wrote: * * > How does it decide whether or not a package conforms? * * Probably by looking for files which get installed in /usr/local or * /usr/X11R6 instead of ${LOCALBASE} or ${X11BASE} :-) Actually, it's easier than that -- just do a "make package". If files go to anyplace else than ${PREFIX}, pkg_create will fail. :) However, note that you need to move LOCALBASE and X11BASE for *all* ports, not one. (For instance, you can't expect an emacs-lisp package to install correctly if you just try to move it while emacs is still in /usr/local.) Set LOCALBASE and X11BASE in /etc/make.conf and rebuild everything, including X. Satoshi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: reducing sbsize: lost count, uid = 1001
* Brian Fundakowski Feldman <[EMAIL PROTECTED]> [000823 22:05] wrote: > On Wed, 23 Aug 2000, Alfred Perlstein wrote: > > > * Alfred Perlstein <[EMAIL PROTECTED]> [000823 14:29] wrote: > > > > > > I have a feeling that this is related to missing spl protection around > > > the chgsbsize subsystem, this was probably an issue before I touched it > > > but since I touched it last I'll have a look-see. > > > > > > Brian, does that makes sense? > > [...] > > > > Does it make sense to wrap chgsbsize with spl so callers don't have > > to worry about it? > > > > Yeah, I say to go for it. I was /certain/ that these functions had > the right spl()s before; if the patch fixes jdp's problem, I can't see > a good reason not to change it, other than it would hide what may be > quite problematic for other reasons even if not for that one... Actually with my patches he still has problems, but I just realized that I'm using splnet in my patches, should I be using splimp? patch is here: http://people.freebsd.org/~alfred/sbsize_spl.diff Note that I'm quite sure it's not just sbsize which needs spl, it's the code that modifies the socketbuffer's size fields as well as the chgsbsize() calls otherwise user context may be preempted by a packet closing the connection after sbsize has been adjusted but not before the buffer sizes have been fixed in the socket struture causing the interrupt context to try to chgsbsize again. Or at least that's what I think may be going on. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: reducing sbsize: lost count, uid = 1001
On Wed, 23 Aug 2000, Alfred Perlstein wrote: > * Alfred Perlstein <[EMAIL PROTECTED]> [000823 14:29] wrote: > > > > I have a feeling that this is related to missing spl protection around > > the chgsbsize subsystem, this was probably an issue before I touched it > > but since I touched it last I'll have a look-see. > > > > Brian, does that makes sense? > [...] > > Does it make sense to wrap chgsbsize with spl so callers don't have > to worry about it? > Yeah, I say to go for it. I was /certain/ that these functions had the right spl()s before; if the patch fixes jdp's problem, I can't see a good reason not to change it, other than it would hide what may be quite problematic for other reasons even if not for that one... -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than/usr/local?
On Wed, 23 Aug 2000, Mike Meyer wrote: > How does it decide whether or not a package conforms? Probably by looking for files which get installed in /usr/local or /usr/X11R6 instead of ${LOCALBASE} or ${X11BASE} :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DPT revision....(broken drivers in -STABLE)
On Wed, 23 Aug 2000, Mike Smith wrote: > I would recommend just preserving the relevant files and updating the > rest of the system right now. I think that Matt Dodd is working on > this right now. A quick look at the code doesn't suggest anything > immediately wrong with the new interrupt assignment code; has anything > else in this system been changed? I don't remember seeing a verbose boot log posted so I can't really say whats wrong. There is no difference b/t the -CURRENT and 4-STABLE versions of dpt_pci.c so I'm not sure what could be causing the problem. Of course it may be that the cards don't work in -CURRENT either. Not having a test system with PCI DPT boards somewhat limits my ability to wring these things out. I won't refuse a rackmounted compaq with PCI and EISA slots and a brace of DPT and Smart2 RAID cards if someone sends me one. Who knows? I might even be able to beat a bit on the management tools then. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DPT revision....(broken drivers in -STABLE)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I would recommend just preserving the relevant files and updating the > rest of the system right now. I think that Matt Dodd is working on this > right now. A quick look at the code doesn't suggest anything immediately > wrong with the new interrupt assignment code; has anything else in this > system been changed? No, this system is a regular workstation, and the issue has been tested on a fresh install. Nothin special... Yea, I already did that on at least one machine... (preserving relevent files) Thanks, again, anyway I can help test would be happy to... Visigoth Damieon Stark Sr. Unix Systems Administrator [EMAIL PROTECTED] PGP Public Key: www.telemere.net/~visigoth/visigoth.asc | M$ -Where do you want to go today? | Linux -Where do you want to go tomorrow?| FreeBSD - The POWER to serve Freebsd -Are you guys coming or what? | http://www.freebsd.org | | - -BEGIN PGP SIGNATURE- Version: PGP 6.5.1i iQA/AwUBOaRviDnmC/+RTnGeEQI6hwCglJixNl6ygc5lB1htPYHhHnq/gfgAoPyg PFi6lsLGRVUo9zDr+sC4oPx8 =jmqK -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than /usr/local?
Satoshi - Ports Wraith - Asami writes: > * From: Mike Meyer <[EMAIL PROTECTED]> > * However, I was wondering if there was anyone who could fix things that > * weren't PREFIX clean who would also find them on a regular > * basis. That's not you. > I can help you when the new package building cluster (being put > together by Paul Saab at the moment) comes up for service. I'll run > some builds with LOCALBASE and X11BASE set to someplace other than the > default and flag all ports that don't conform. How does it decide whether or not a package conforms? I'm willing to help if you want to divide this task up. Just let me know what I can do to help.
make buildworld broken in libcrypto.
I got the following error while trying to make builworld with WITH_IDEA=YES and USA_RESIDENT=NO. ===> libcrypto [snip] cc -O -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/secure/lib/libcrypto -DL_ENDIAN -I/usr/obj/usr/src/i386/usr/include -c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c -o e_cbc_i.o /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:7 8: union has no member named `idea_ks' /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c: In function `idea_cbc_init_key': /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:9 7: union has no member named `idea_ks' /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:1 00: syntax error before `tmp' /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:1 02: `tmp' undeclared (first use in this function) /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:1 02: (Each undeclared identifier is reported only once /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:1 02: for each function it appears in.) /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:1 03: union has no member named `idea_ks' /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:1 05: `IDEA_KEY_SCHEDULE' undeclared (first use in this function) /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c: In function `idea_cbc_cipher': /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:1 15: union has no member named `idea_ks' *** Error code 1 Stop in /usr/src/secure/lib/libcrypto. -- Shin-ichi YOSHIMOTO <[EMAIL PROTECTED]> KEK, High Energy Accelerator Research Organization Accelerator Laboratory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld failed with MAKE_IDEA=YES
I don't know this problem is happend only on my box, or not. But I'm using MAKE_IDEA=IES and USA_RESIDENT=NO for buildworld. ===> libcrypto cc -O -mpentiumpro -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/secure/lib/libcrypto -DL_ENDIAN -I/usr/obj/usr/src/i386/usr/include -c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cpt_err.c -o cpt_err.o ... cc -O -mpentiumpro -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/secure/lib/libcrypto -DL_ENDIAN -I/usr/obj/usr/src/i386/usr/include -c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c -o e_cbc_i.o /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:78: union has no member named `idea_ks' /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c: In function `idea_cbc_init_key': /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:97: union has no member named `idea_ks' /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:100: syntax error before `tmp' /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:102: `tmp' undeclared (first use in this function) /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:102: (Each undeclared identifier is reported only once /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:102: for each function it appears in.) /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:103: union has no member named `idea_ks' /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:105: `IDEA_KEY_SCHEDULE' undeclared (first use in this function) /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c: In function `idea_cbc_cipher': /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp/e_cbc_i.c:115: union has no member named `idea_ks' *** Error code 1 Stop in /usr/src/secure/lib/libcrypto. *** Error code 1 Stop in /usr/src/secure/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Jun Kuriyama <[EMAIL PROTECTED]> // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: reducing sbsize: lost count, uid = 1001
In article <[EMAIL PROTECTED]>, Alfred Perlstein <[EMAIL PROTECTED]> wrote: > > more paranioa: > > > Index: uipc_socket.c > === > RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v > retrieving revision 1.80 > diff -u -u -r1.80 uipc_socket.c > --- uipc_socket.c 2000/08/07 17:52:08 1.80 > +++ uipc_socket.c 2000/08/23 23:06:13 > @@ -187,8 +187,10 @@ > sodealloc(so) Nope, still no go. Here's the stack trace: #9 0xc0166894 in panic ( fmt=0xc027fca0 "reducing sbsize: lost count, uid = %d") at /local0/src/sys/kern/kern_shutdown.c:551 #10 0xc0163b67 in chgsbsize (uid=1001, diff=-17520, max=9223372036854775807) at /local0/src/sys/kern/kern_proc.c:202 #11 0xc0186ffa in sbrelease (sb=0xc7c227f4, so=0xc7c22780) at /local0/src/sys/kern/uipc_socket2.c:459 #12 0xc0184343 in sofree (so=0xc7c22780) at /local0/src/sys/kern/uipc_socket.c:264 #13 0xc01b89ae in in_pcbdetach (inp=0xc7c86440) at /local0/src/sys/netinet/in_pcb.c:542 #14 0xc01c2145 in tcp_close (tp=0xc7c86500) at /local0/src/sys/netinet/tcp_subr.c:711 #15 0xc01c010a in tcp_input (m=0xc075cb00, off0=20, proto=6) at /local0/src/sys/netinet/tcp_input.c:2012 #16 0xc01bb0ba in ip_input (m=0xc075cb00) at /local0/src/sys/netinet/ip_input.c:756 #17 0xc01bb117 in ipintr () at /local0/src/sys/netinet/ip_input.c:784 I see that tcp_close() is in the call stack, but that's surprising. It didn't seem like the transfer had gone on nearly long enough for it to be finishing already. Also, from the peer's point of view it was not finished. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DPT revision....(broken drivers in -STABLE)
> > Would it be possible to revert the DPT commits made by peter on > Mon Aug 7 18:48:14 2000 in the RELENG_4 branch? It seems that the > dpt_attatch is failing in bus_alloc_resource(9) for the IRQ, and I have > production machines that need worlds built for some other updates as > well.. I would be happy to install a -CURRENT machine and help debug > until it works, but for right now, there is NO DPT support in -STABLE for > the DPT PM3334UW. I had a pr started, but haven't been able to get any > response from the current maintainer. I would recommend just preserving the relevant files and updating the rest of the system right now. I think that Matt Dodd is working on this right now. A quick look at the code doesn't suggest anything immediately wrong with the new interrupt assignment code; has anything else in this system been changed? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
Alexander Leidinger wrote: > > On 23 Aug, Paul Richards wrote: > > >> > On a vaguely related topic, after much searching I can't seem to see one > >> > way or the other if we can do a complete bit-by-bit copy of a cd with > >> > either cdrecord or burncd, though it's possible I'm looking in the wrong > >> > place. > >> > >> I think cdrecord can burn CDs in disk-at-once mode, and I think cdrdao (in > >> ports/audio) can do it as well. > >> > >> As far as getting an image, you can use dd to dump off an image of a CD if > >> it is a standard ISO9660 CD. (I've used that method to clone CDs before.) > > > > That didn't seem to work when I tried it a couple of days ago. Got a > > "device not configured" error. > > You've done something wrong, it works here. Yep, just tried it again and you're right I was doing something wrong. I was trying to dd from the blank in the CD-RW rather than the master in the CD (blush). > BTW: > If I need a copy of a data cd I use "cdrecord -v speed=4 dev=0,1,0 > -eject -isosize /dev/cd1c" (cd1 is my CD-ROM, cd0 (dev=0,1,0) is my CD > burner). That's what I used in the end. Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: reducing sbsize: lost count, uid = 1001
* John Polstra <[EMAIL PROTECTED]> [000823 15:55] wrote: > In article <[EMAIL PROTECTED]>, > Alfred Perlstein <[EMAIL PROTECTED]> wrote: > > > Nope, that doesn't fix it. I got the same panic on the very first > > > try. > > > > hmm, when does it happen? During the transfer or at the end of the > > transfer? > > The first time I reported the problem it had happened during the > transfer. This time (with your patch) the transfer actually completed > from the peer's point of view before the panic occurred. That's not > many data points, so it could be coincidence. I'll keep you posted > if I can make it happen again. more paranioa: Index: uipc_socket.c === RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v retrieving revision 1.80 diff -u -u -r1.80 uipc_socket.c --- uipc_socket.c 2000/08/07 17:52:08 1.80 +++ uipc_socket.c 2000/08/23 23:06:13 @@ -187,8 +187,10 @@ sodealloc(so) struct socket *so; { + int s; so->so_gencnt = ++so_gencnt; + s = splnet(); /* protect against interrupts messing with sbsize */ if (so->so_rcv.sb_hiwat) (void)chgsbsize(so->so_cred->cr_uid, -(rlim_t)so->so_rcv.sb_hiwat, RLIM_INFINITY); @@ -204,6 +206,7 @@ FREE(so->so_accf->so_accept_filter_str, M_ACCF); FREE(so->so_accf, M_ACCF); } + splx(s); crfree(so->so_cred); zfreei(so->so_zone, so); } -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: reducing sbsize: lost count, uid = 1001
In article <[EMAIL PROTECTED]>, Alfred Perlstein <[EMAIL PROTECTED]> wrote: > > Nope, that doesn't fix it. I got the same panic on the very first > > try. > > hmm, when does it happen? During the transfer or at the end of the > transfer? The first time I reported the problem it had happened during the transfer. This time (with your patch) the transfer actually completed from the peer's point of view before the panic occurred. That's not many data points, so it could be coincidence. I'll keep you posted if I can make it happen again. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: reducing sbsize: lost count, uid = 1001
* John Polstra <[EMAIL PROTECTED]> [000823 15:39] wrote: > In article <[EMAIL PROTECTED]>, > Alfred Perlstein <[EMAIL PROTECTED]> wrote: > > > > Let's take a more paraniod approach (back out my spl in chgsbsize): > > > > > > Index: uipc_socket2.c > > Nope, that doesn't fix it. I got the same panic on the very first > try. hmm, when does it happen? During the transfer or at the end of the transfer? -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: reducing sbsize: lost count, uid = 1001
In article <[EMAIL PROTECTED]>, Alfred Perlstein <[EMAIL PROTECTED]> wrote: > > Let's take a more paraniod approach (back out my spl in chgsbsize): > > > Index: uipc_socket2.c Nope, that doesn't fix it. I got the same panic on the very first try. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: reducing sbsize: lost count, uid = 1001
* John Polstra <[EMAIL PROTECTED]> [000823 15:03] wrote: > In article <[EMAIL PROTECTED]>, > Alfred Perlstein <[EMAIL PROTECTED]> wrote: > > > John can you try this patch and let us know if you still experiance > > crashes? > > Will do. I'll let you know what happens. Let's take a more paraniod approach (back out my spl in chgsbsize): Index: uipc_socket2.c === RCS file: /home/ncvs/src/sys/kern/uipc_socket2.c,v retrieving revision 1.61 diff -u -u -r1.61 uipc_socket2.c --- uipc_socket2.c 2000/07/31 08:23:43 1.61 +++ uipc_socket2.c 2000/08/23 22:23:47 @@ -448,10 +448,17 @@ struct sockbuf *sb; struct socket *so; { + int s; sbflush(sb); + /* +* if we don't spl an interrupt can recurse into us and call chgsbsize +* before we zero sb->sb_hiwat +*/ + s = splnet(); (void)chgsbsize(so->so_cred->cr_uid, -(rlim_t)sb->sb_hiwat, RLIM_INFINITY); sb->sb_hiwat = sb->sb_mbmax = 0; + splx(s); } /* -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than /usr/local?
* From: Mike Meyer <[EMAIL PROTECTED]> * However, I was wondering if there was anyone who could fix things that * weren't PREFIX clean who would also find them on a regular * basis. That's not you. I can help you when the new package building cluster (being put together by Paul Saab at the moment) comes up for service. I'll run some builds with LOCALBASE and X11BASE set to someplace other than the default and flag all ports that don't conform. I couldn't do that for a while since I didn't have enough computing power -- the machines were maxed out just squeezing out the weekly (and sometimes biweekly) set of packages. Satoshi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: reducing sbsize: lost count, uid = 1001
In article <[EMAIL PROTECTED]>, Alfred Perlstein <[EMAIL PROTECTED]> wrote: > John can you try this patch and let us know if you still experiance > crashes? Will do. I'll let you know what happens. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: reducing sbsize: lost count, uid = 1001
* Alfred Perlstein <[EMAIL PROTECTED]> [000823 14:29] wrote: > > I have a feeling that this is related to missing spl protection around > the chgsbsize subsystem, this was probably an issue before I touched it > but since I touched it last I'll have a look-see. > > Brian, does that makes sense? So far, here's functions that look like they call chgsbsize without splnet: socreate (called from socket() and socketpair(), on error calls sofree() which then calls sodealloc() without splnet) sonewconn3 (called from sonewconn which i'm unsure of the spl at this point) I'm sure there's more. Does it make sense to wrap chgsbsize with spl so callers don't have to worry about it? John can you try this patch and let us know if you still experiance crashes? Index: kern_proc.c === RCS file: /home/ncvs/src/sys/kern/kern_proc.c,v retrieving revision 1.69 diff -u -u -r1.69 kern_proc.c --- kern_proc.c 2000/07/04 11:25:22 1.69 +++ kern_proc.c 2000/08/23 21:49:49 @@ -196,6 +196,7 @@ rlim_t max; { struct uidinfo *uip; + int s = splnet(); uip = uifind(uid); if (diff < 0) @@ -205,10 +206,12 @@ /* don't allow them to exceed max, but allow subtraction */ if (diff > 0 && uip->ui_sbsize + diff > max) { (void)uifree(uip); + splx(s); return (0); } uip->ui_sbsize += diff; (void)uifree(uip); + splx(s); return (1); } If this doesn't work then it may be nessesary to spl around examining the socketbuffer's size. thanks, -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: reducing sbsize: lost count, uid = 1001
* John Polstra <[EMAIL PROTECTED]> [000823 13:46] wrote: > I got the above panic in a -current kernel from August 19 with > INVARIANTS and INVARIANT_SUPPORT compiled in. I also saw it once > before on a kernel from a few weeks ago. In both cases the panic > occurred when receiving a 25 MB file with FTP over a gigabit Ethernet > link (wx driver). Here is the relevant portion of the stack trace: > > #16 0xc016689d in panic ( > fmt=0xc027fc80 "reducing sbsize: lost count, uid = %d") > at /local0/src/sys/kern/kern_shutdown.c:553 > #17 0xc0163b67 in chgsbsize (uid=1001, diff=-17520, max=9223372036854775807) > at /local0/src/sys/kern/kern_proc.c:202 > #18 0xc0186fe2 in sbrelease (sb=0xc7c22674, so=0xc7c22600) > at /local0/src/sys/kern/uipc_socket2.c:453 > #19 0xc0184333 in sofree (so=0xc7c22600) > at /local0/src/sys/kern/uipc_socket.c:261 > #20 0xc01b898e in in_pcbdetach (inp=0xc7c86880) > at /local0/src/sys/netinet/in_pcb.c:542 > #21 0xc01c2125 in tcp_close (tp=0xc7c86940) > at /local0/src/sys/netinet/tcp_subr.c:711 > #22 0xc01c00ea in tcp_input (m=0xc075ca00, off0=20, proto=6) > at /local0/src/sys/netinet/tcp_input.c:2012 > #23 0xc01bb09a in ip_input (m=0xc075ca00) > at /local0/src/sys/netinet/ip_input.c:756 > #24 0xc01bb0f7 in ipintr () at /local0/src/sys/netinet/ip_input.c:784 > > Unfortunately, I don't have time to dig into it further any time soon. > I'll append my kernel config file to this mail. The system is a > uniprocessor PII/400. I have a feeling that this is related to missing spl protection around the chgsbsize subsystem, this was probably an issue before I touched it but since I touched it last I'll have a look-see. Brian, does that makes sense? -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic: reducing sbsize: lost count, uid = 1001
I got the above panic in a -current kernel from August 19 with INVARIANTS and INVARIANT_SUPPORT compiled in. I also saw it once before on a kernel from a few weeks ago. In both cases the panic occurred when receiving a 25 MB file with FTP over a gigabit Ethernet link (wx driver). Here is the relevant portion of the stack trace: #16 0xc016689d in panic ( fmt=0xc027fc80 "reducing sbsize: lost count, uid = %d") at /local0/src/sys/kern/kern_shutdown.c:553 #17 0xc0163b67 in chgsbsize (uid=1001, diff=-17520, max=9223372036854775807) at /local0/src/sys/kern/kern_proc.c:202 #18 0xc0186fe2 in sbrelease (sb=0xc7c22674, so=0xc7c22600) at /local0/src/sys/kern/uipc_socket2.c:453 #19 0xc0184333 in sofree (so=0xc7c22600) at /local0/src/sys/kern/uipc_socket.c:261 #20 0xc01b898e in in_pcbdetach (inp=0xc7c86880) at /local0/src/sys/netinet/in_pcb.c:542 #21 0xc01c2125 in tcp_close (tp=0xc7c86940) at /local0/src/sys/netinet/tcp_subr.c:711 #22 0xc01c00ea in tcp_input (m=0xc075ca00, off0=20, proto=6) at /local0/src/sys/netinet/tcp_input.c:2012 #23 0xc01bb09a in ip_input (m=0xc075ca00) at /local0/src/sys/netinet/ip_input.c:756 #24 0xc01bb0f7 in ipintr () at /local0/src/sys/netinet/ip_input.c:784 Unfortunately, I don't have time to dig into it further any time soon. I'll append my kernel config file to this mail. The system is a uniprocessor PII/400. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa # # BLAKE # machine "i386" cpu "I686_CPU" ident BLAKE maxusers32 options SOFTUPDATES options DDB options INVARIANTS options INVARIANT_SUPPORT options "CLK_USE_I8254_CALIBRATION" options CLK_USE_TSC_CALIBRATION options INET#InterNETworking options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options KTRACE #kernel tracing options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660"#ISO 9660 Filesystem options "EXT2FS"#Linux ext2 filesystem options "CD9660_ROOT" #CD-ROM usable as root device options FFS_ROOT#FFS usable as root device [keep this!] options NFS_ROOT#NFS usable as root device options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options RANDOMDEV options SYSVSHM options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options P1003_1B#Posix P1003_1B real-time extentions options _KPOSIX_PRIORITY_SCHEDULING # options _KPOSIX_VERSION=199309L device isa device pci device fdc # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. device ahc options AHC_ALLOW_MEMIO device scbus device da device sa device cd device pass # Keyboard, mouse, display. device atkbdc 1 device atkbd device psm device sc 1 device vga device splash device npx device sio device de device fxp device wx device bpf device ether device gzip device loop device pty device vn # On-board power management controller. device smbus device intpm device smb To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA66 support
It seems j mckitrick wrote: > On Wed, Aug 23, 2000 at 06:14:46PM +0200, Soren Schmidt wrote: > | Well, "work" is exactly the word to use, they work on *some* chipsets > | with *some* drivers, but they have problems there as well. Remember > | that most wintel boxes doesn't even use DMA... > > really? why is that? and why include the feature if it is not used by the > biggest segment of the market? Marketing hype ? > | Besides it seems as if its our much more agressive usage thats the > | real problem, looks like firmware problems too me > > how is bsd more aggressive (other than the obvious buildworld load)? > maybe we should go easier on the hardware for real-world compatibility and > reliability reasons? Running multiple processes, multiple users gives you another use pattern as a wintel box used for gaming -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: patch for mergemaster when /dev is devfs
On Wed, 23 Aug 2000, Ben Smithurst wrote: > Or would you prefer that this be made an option like IGNORE_DEV or > IGNORE_MAKEDEV or something? If you'd prefer that I can probably create > an appropriate patch, but this route seems more sensible to me, since no > config change will be needed if I decide to stop using devfs. I like this approach better, since it doesn't seem that an option is really necessary. However my understanding of devfs is limited to the concept only, so if someone more knoweledgeable and/or preferably someone USING the new devfs stuff wants to comment, I'm open to suggestions. Otherwise, Ben go ahead and commit this after a few days have gone by without opinions to the contrary. Thanks, Doug > Index: mergemaster.sh > === > RCS file: /usr/cvs/src/usr.sbin/mergemaster/mergemaster.sh,v > retrieving revision 1.10 > diff -u -r1.10 mergemaster.sh > --- mergemaster.sh2000/08/13 19:32:19 1.10 > +++ mergemaster.sh2000/08/23 16:17:48 > @@ -10,7 +10,7 @@ > > # $FreeBSD: src/usr.sbin/mergemaster/mergemaster.sh,v 1.10 2000/08/13 19:32:19 >gshapiro Exp $ > > -PATH=/bin:/usr/bin:/usr/sbin > +PATH=/bin:/usr/bin:/usr/sbin:/sbin > > display_usage () { >VERSION_NUMBER=`grep "[$]FreeBSD:" $0 | cut -d ' ' -f 4` > @@ -421,6 +421,11 @@ >*) rm ${TEMPROOT}/etc/motd > ;; >esac > + > + # Avoid trying to update MAKEDEV if /dev is on a devfs > + if mount | grep -q "devfs on /dev "; then > +rm ${TEMPROOT}/dev/MAKEDEV ${TEMPROOT}/dev/MAKEDEV.local > + fi > >;; # End of the "RERUN" test > esac > > -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weirdness with devfs? (time)
In message <[EMAIL PROTECTED]>, Siobhan Patricia Lynch writes: >On Wed, 23 Aug 2000, Poul-Henning Kamp wrote: > >> In message <[EMAIL PROTECTED]>, >> Siobhan Patricia Lynch writes: >> >this is cute: >> >notice the dates, they predate the epoch. >> >> Because of your timezone. >> > >nod, figured that out already, however, is the epoch date intentional? No. I'm working on that issue right now. If you look in sys/ufs/ufs/ufs_vnops.c:ufs_spec{read|write}() you will see that the filesystem "hosting" the device node has to figure out for itself when to update the ACCESS, UPDATE and CHANGE timestamps relative to the access to the dev_t through specfs. Obviously wrong since all device node hosting filesystems (ufs, ext2fs, devfs cd9660 (well, not really but in principle...)) will have to duplicate that code. I'm looking at a patch right now which adds three flag bits to the dev_t and clone this code into sys/miscfs/specfs() where it will maintain these three bits. The hosting filesystem can then examine just those bits to determine when timestamps should be updated. The advantage to this scheme is that the drivers themselves can set these bits when for instance ioctl functions have "updated" or "accessed" the device. The secondary advantage is that we don't have to have this code mutated in multiple filesystems. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
DPT revision....(broken drivers in -STABLE)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry for the cross post but Would it be possible to revert the DPT commits made by peter on Mon Aug 7 18:48:14 2000 in the RELENG_4 branch? It seems that the dpt_attatch is failing in bus_alloc_resource(9) for the IRQ, and I have production machines that need worlds built for some other updates as well.. I would be happy to install a -CURRENT machine and help debug until it works, but for right now, there is NO DPT support in -STABLE for the DPT PM3334UW. I had a pr started, but haven't been able to get any response from the current maintainer. I am going to install a -CURRENT machine with a DPT in it and start the process of working on the issue, but it would be nice if we can keep -STABLE stable... ;) Visigoth Damieon Stark Sr. Unix Systems Administrator [EMAIL PROTECTED] PGP Public Key: www.telemere.net/~visigoth/visigoth.asc | M$ -Where do you want to go today? | Linux -Where do you want to go tomorrow?| FreeBSD - The POWER to serve Freebsd -Are you guys coming or what? | http://www.freebsd.org | | - -BEGIN PGP SIGNATURE- Version: PGP 6.5.1i iQA/AwUBOaQPGDnmC/+RTnGeEQIJmgCfceaKQbQtf6rIw8y7vnKX9yILwzgAoOio qyAuX72v+iICVu5y5n9GQvz/ =TXXY -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weirdness with devfs? (time)
On Wed, 23 Aug 2000, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, > Siobhan Patricia Lynch writes: > >this is cute: > >notice the dates, they predate the epoch. > > Because of your timezone. > nod, figured that out already, however, is the epoch date intentional? __ Trish Lynch FreeBSD - The Power to Serve[EMAIL PROTECTED] Rush Networking [EMAIL PROTECTED] --- "the wood is tired and the wood is old we'll make it fine if the weather holds but if the weather holds we'll have missed the point that's where i need to go" -Indigo Girls, The Wood Song To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA66 support
On Wed, Aug 23, 2000 at 06:14:46PM +0200, Soren Schmidt wrote: | Well, "work" is exactly the word to use, they work on *some* chipsets | with *some* drivers, but they have problems there as well. Remember | that most wintel boxes doesn't even use DMA... really? why is that? and why include the feature if it is not used by the biggest segment of the market? | Besides it seems as if its our much more agressive usage thats the | real problem, looks like firmware problems too me how is bsd more aggressive (other than the obvious buildworld load)? maybe we should go easier on the hardware for real-world compatibility and reliability reasons? jcm -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weirdness with devfs? (time)
In message <[EMAIL PROTECTED]>, Siobhan Patricia Lynch writes: >this is cute: >notice the dates, they predate the epoch. Because of your timezone. >weird huh? anyone else see this or am I just off my rocker? >crw--- 1 root wheel 12, 0 Dec 31 1969 ttyv0 >crw--- 1 root wheel 12, 1 Dec 31 1969 ttyv1 >crw--- 1 root wheel 12, 2 Dec 31 1969 ttyv2 >crw--- 1 root wheel 12, 3 Dec 31 1969 ttyv3 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
patch for mergemaster when /dev is devfs
Just a minor point... Should we add a patch something like this to mergemaster so that it doesn't prompt the user about MAKEDEV if their /dev is a devfs where MAKEDEV can't be created anyway? Or would you prefer that this be made an option like IGNORE_DEV or IGNORE_MAKEDEV or something? If you'd prefer that I can probably create an appropriate patch, but this route seems more sensible to me, since no config change will be needed if I decide to stop using devfs. Index: mergemaster.sh === RCS file: /usr/cvs/src/usr.sbin/mergemaster/mergemaster.sh,v retrieving revision 1.10 diff -u -r1.10 mergemaster.sh --- mergemaster.sh 2000/08/13 19:32:19 1.10 +++ mergemaster.sh 2000/08/23 16:17:48 @@ -10,7 +10,7 @@ # $FreeBSD: src/usr.sbin/mergemaster/mergemaster.sh,v 1.10 2000/08/13 19:32:19 gshapiro Exp $ -PATH=/bin:/usr/bin:/usr/sbin +PATH=/bin:/usr/bin:/usr/sbin:/sbin display_usage () { VERSION_NUMBER=`grep "[$]FreeBSD:" $0 | cut -d ' ' -f 4` @@ -421,6 +421,11 @@ *) rm ${TEMPROOT}/etc/motd ;; esac + + # Avoid trying to update MAKEDEV if /dev is on a devfs + if mount | grep -q "devfs on /dev "; then +rm ${TEMPROOT}/dev/MAKEDEV ${TEMPROOT}/dev/MAKEDEV.local + fi ;; # End of the "RERUN" test esac -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA66 support
It seems Matthew Thyer wrote: > Soren Schmidt wrote: > > It seems Andreas Klemm wrote: > > > ad4: 39082MB [79406/16/63] at ata2-master using UDMA33 > > > > AHA! try swap that with a known good drive (ie non Maxtor/WD) if you can > > Are there plans to try to support this broken hardware ? If possible... > Maxtor seem to be violating ATAPI standards in that FreeBSD and Linux > cannot use many Maxtor drives at rated speed, however. You mean ATA standards, I'm not sure thats the problem... > Maxtor has some extremely fast drives that `work' in WinTel machines > faster than all other competitors using ATA66 (as of a month or so ago) > so it appears they are cutting corners on the standard (cheating) in > order to produce a very fast product. Well, "work" is exactly the word to use, they work on *some* chipsets with *some* drivers, but they have problems there as well. Remember that most wintel boxes doesn't even use DMA... Besides it seems as if its our much more agressive usage thats the real problem, looks like firmware problems too me > Are there plans to accomodate their behavior ? As I've stated before, if somebody get me one of the problematic drives on my desk I'll do what I can > Do you have any contacts in Maxtor to help in this task ? Sortof, but they dont think they have any problems at all :) -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA66 support
Soren Schmidt wrote: > It seems Andreas Klemm wrote: > > ad4: 39082MB [79406/16/63] at ata2-master using UDMA33 > > AHA! try swap that with a known good drive (ie non Maxtor/WD) if you can Are there plans to try to support this broken hardware ? Maxtor seem to be violating ATAPI standards in that FreeBSD and Linux cannot use many Maxtor drives at rated speed, however. Maxtor has some extremely fast drives that `work' in WinTel machines faster than all other competitors using ATA66 (as of a month or so ago) so it appears they are cutting corners on the standard (cheating) in order to produce a very fast product. Are there plans to accomodate their behavior ? Do you have any contacts in Maxtor to help in this task ? > > -Søren > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer (who doesn't send useless test mail to mailing lists) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than /usr/local?
Out of the ether, David O'Brien spewed forth the following bitstream: > On Wed, Aug 23, 2000 at 01:36:56PM +0100, Konstantin Chuguev wrote: > > Do you use /usr/local for anything? > Yes, local stuff. IMHO, the Ports Collection using /usr/local was the > biggest mistake of it. The ports collection should have used /usr/pkg/ > as NetBSD does. I have to create /usr/truely-local on my FreeBSD > machines. Amen. I would strongly recommend that the "/usr/local" use of ports be re-aimed at something else. "/usr/local" should be the pristine ownership of the LOCAL admin. AlanC {BSD/OS uses /usr/contrib, but that ain't the same thing} To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than /usr/local?
Konstantin Chuguev writes: > "Jacques A. Vidrine" wrote: > > On Wed, Aug 23, 2000 at 01:01:59AM -0500, Mike Meyer wrote: > > > Um - why? If you removed the setting of LOCALBASE in that case, you > > > wouldn't change the disk layout at all. > > I prefer installed executables, data files, and man pages to refer to > > /opt. Duh. Ok, that makes sense. I overlooked the man pages. > Just wondering: what is the reason of using /opt instead of /usr/local, > apart from Solaris influence? Do you use /usr/local for anything? I use /usr/opt instead of /opt. I use /usr/local for things that are local additions to the system, as opposed to things that are gotten through freebsd. They have different update & backup policies, which is why they were separated. Ports got moved instead of local because ports has a mechanism for moving them, whereas local things may or may not have that.
I thought I told you not to send a test message
Why have you annoyed many hundreds of people with your test message which I told you was not necessary to send ? I clearly described the simple problem of your organisation using email relay servers which were not registered in the DNS causing many weeks of problems for me. Not only have you annoyed many people but you have sent email using my sending address instead of your own address for a test which was not necessary. I am extremely unimpressed with the performance of your organisation and the incompetant manner that this simple problem has been handled. It would be within my rights to take legal action against your organisation. Please have someone contact me as soon as possible to discuss the way your organisation should repay me for the more than 2 months of inconvienience and suffering I have endured. To the FreeBSD-current list subscribers, I hope you accept that I did not send that stupid test message and also be advised that the Australian operations of UU.net and Access One take about 2 months to even understand a simple DNS problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than /usr/local?
On Wed, Aug 23, 2000 at 01:36:56PM +0100, Konstantin Chuguev wrote: > Do you use /usr/local for anything? Yes, local stuff. IMHO, the Ports Collection using /usr/local was the biggest mistake of it. The ports collection should have used /usr/pkg/ as NetBSD does. I have to create /usr/truely-local on my FreeBSD machines. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weirdness with devfs? (time)
On Wed, 23 Aug 2000, Will Andrews wrote: > On Wed, Aug 23, 2000 at 10:28:00AM -0400, Siobhan Patricia Lynch wrote: >^ > > this is cute: > > notice the dates, they predate the epoch. > > They don't predate the epoch. The epoch starts at 00:00 UTC on January > 1, 1970. Hence, the dates are exactly the epoch (20:00 -0400 UTC on > December 31, 1969). > > But you *DO* have a real bug there.. ;-> > ok I concede, taking into account time zones, yes it is the epoch ;) however it *is* strange. __ Trish Lynch FreeBSD - The Power to Serve[EMAIL PROTECTED] Rush Networking [EMAIL PROTECTED] --- "Can't let them rape me again Your venom's not family here won't let them fill me with fatalistic remedies" -Dream Theater, Scarred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weirdness with devfs? (time)
On Wed, 23 Aug 2000 10:31:45 -0400, Donn Miller wrote: > Maybe your machine was previously owned by a Woodstock-era hippie? LOL. > > I have no such problems with my -current: > > total 42 > -r-xr-xr-x 1 root wheel38814 Aug 19 23:40 MAKEDEV* > -r-xr-xr-x 1 root wheel 2064 Jul 16 07:49 MAKEDEV.local* And you're not using DEVFS, so it doesn't really matter whether you have the problem on your box. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weirdness with devfs? (time)
On Wed, Aug 23, 2000 at 10:28:00AM -0400, Siobhan Patricia Lynch wrote: ^ > this is cute: > notice the dates, they predate the epoch. They don't predate the epoch. The epoch starts at 00:00 UTC on January 1, 1970. Hence, the dates are exactly the epoch (20:00 -0400 UTC on December 31, 1969). But you *DO* have a real bug there.. ;-> -- Will Andrews <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> GCS/E/S @d- s+:+ a--- C++ UB$ P+ L- E--- W+ N-- !o ?K w--- O- M+ V- PS+ PE++ Y+ PGP+>+++ t++ 5 X+ R+ tv+ b++ DI+++ D+ G++ e> h! r- y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weirdness with devfs? (time)
Siobhan Patricia Lynch wrote: > > this is cute: > notice the dates, they predate the epoch. > > weird huh? anyone else see this or am I just off my rocker? > > -Trish > > total 0 > crw-r--r-- 1 root operator 117, 0 Dec 31 1969 acd0a > crw-r--r-- 1 root operator 117, 2 Dec 31 1969 acd0c > crw-r- 1 root operator 15, 0x00010002 Dec 31 1969 cd0 > crw-r- 1 root operator 15, 2 Dec 31 1969 cd0c > crw--- 1 root wheel 0, 0 Dec 31 1969 console Maybe your machine was previously owned by a Woodstock-era hippie? LOL. I have no such problems with my -current: total 42 -r-xr-xr-x 1 root wheel38814 Aug 19 23:40 MAKEDEV* -r-xr-xr-x 1 root wheel 2064 Jul 16 07:49 MAKEDEV.local* crw-r- 2 root operator 117, 0 Jul 17 02:20 acd0a crw-rw-rw- 2 root operator 117, 2 Jul 17 02:20 acd0c crw-r- 2 root operator 117, 8 Jul 17 02:20 acd1a crw-r- 2 root operator 117, 10 Jul 17 02:20 acd1c crw-r- 2 root operator 116, 0x00010002 Jul 17 02:20 ad0 crw-r- 2 root operator 116, 0 Jul 17 02:20 ad0a crw-r- 2 root operator 116, 1 Jul 17 02:20 ad0b [snip] -Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
weirdness with devfs? (time)
this is cute: notice the dates, they predate the epoch. weird huh? anyone else see this or am I just off my rocker? -Trish total 0 crw-r--r-- 1 root operator 117, 0 Dec 31 1969 acd0a crw-r--r-- 1 root operator 117, 2 Dec 31 1969 acd0c crw-r- 1 root operator 15, 0x00010002 Dec 31 1969 cd0 crw-r- 1 root operator 15, 2 Dec 31 1969 cd0c crw--- 1 root wheel 0, 0 Dec 31 1969 console crw--- 1 root wheel 12, 255 Dec 31 1969 consolectl crw-rw 1 uucp dialer 28, 128 Dec 31 1969 cuaa0 crw-rw 1 uucp dialer 28, 129 Dec 31 1969 cuaa1 crw-rw 1 uucp dialer 28, 160 Dec 31 1969 cuaia0 crw-rw 1 uucp dialer 28, 161 Dec 31 1969 cuaia1 crw-rw 1 uucp dialer 28, 192 Dec 31 1969 cuala0 crw-rw 1 uucp dialer 28, 193 Dec 31 1969 cuala1 crw-r- 1 root operator 13, 0x00010002 Dec 31 1969 da0 crw-r- 1 root operator 13, 0x0002 Dec 31 1969 da0s1a crw-r- 1 root operator 13, 0x00020001 Dec 31 1969 da0s1b crw-r- 1 root operator 13, 0x00020004 Dec 31 1969 da0s1e crw-r- 1 root operator 13, 0x0001000a Dec 31 1969 da1 crw-r- 1 root operator 13, 0x0002000c Dec 31 1969 da1s1e crw-r- 1 root operator 13, 0x00010012 Dec 31 1969 da2 crw-r- 1 root operator 13, 0x00020014 Dec 31 1969 da2s1e crw-r- 1 root operator 13, 0x0001001a Dec 31 1969 da3 crw-r- 1 root operator 13, 0x0002001c Dec 31 1969 da3s1e crw-r- 1 root operator9, 0 Dec 31 1969 fd0 crw--- 1 root wheel 2, 14 Dec 31 1969 io crw--- 1 root wheel 79, 3 Dec 31 1969 ipauth crw--- 1 root wheel 79, 0 Dec 31 1969 ipl crw--- 1 root wheel 79, 1 Dec 31 1969 ipnat crw--- 1 root wheel 79, 2 Dec 31 1969 ipstate crw--- 1 root wheel 7, 0 Dec 31 1969 klog crw-r- 1 root kmem2, 1 Dec 31 1969 kmem lrw-r---w- 1 root wheel0 Dec 31 1969 log -> /var/run/log crw--- 1 root wheel 16, 0 Dec 31 1969 lpt0 crw--- 1 root wheel 16, 128 Dec 31 1969 lpt0.ctl crw-r- 1 root kmem2, 0 Dec 31 1969 mem crw-rw-rw- 1 root wheel 2, 2 Dec 31 1969 null crw--- 1 root operator 31, 0 Dec 31 1969 pass0 crw--- 1 root operator 31, 1 Dec 31 1969 pass1 crw--- 1 root operator 31, 2 Dec 31 1969 pass2 crw--- 1 root operator 31, 3 Dec 31 1969 pass3 crw--- 1 root operator 31, 4 Dec 31 1969 pass4 crw-r--r-- 1 root wheel 78, 0 Dec 31 1969 pci crw--- 1 root wheel 82, 0 Dec 31 1969 ppi0 crw-rw-rw- 1 root wheel 6, 0 Dec 31 1969 ptyp0 crw-rw-rw- 1 root wheel 6, 1 Dec 31 1969 ptyp1 crw-rw-rw- 1 root wheel 6, 2 Dec 31 1969 ptyp2 crw-rw-rw- 1 root wheel 2, 3 Dec 31 1969 random crw-rw-rw- 1 root wheel 22, 2 Dec 31 1969 stderr crw-rw-rw- 1 root wheel 22, 0 Dec 31 1969 stdin crw-rw-rw- 1 root wheel 22, 1 Dec 31 1969 stdout crw--- 1 root wheel 12, 128 Dec 31 1969 sysmouse crw-rw-rw- 1 root wheel 1, 0 Dec 31 1969 tty crw--- 1 root wheel 28, 0 Dec 31 1969 ttyd0 crw--- 1 root wheel 28, 1 Dec 31 1969 ttyd1 crw--- 1 root wheel 28, 32 Dec 31 1969 ttyid0 crw--- 1 root wheel 28, 33 Dec 31 1969 ttyid1 crw--- 1 root wheel 28, 64 Dec 31 1969 ttyld0 crw--- 1 root wheel 28, 65 Dec 31 1969 ttyld1 crw--w 1 trish tty 5, 0 Dec 31 1969 ttyp0 crw--w 1 trish tty 5, 1 Dec 31 1969 ttyp1 crw--w 1 trish tty 5, 2 Dec 31 1969 ttyp2 crw--- 1 root wheel 12, 0 Dec 31 1969 ttyv0 crw--- 1 root wheel 12, 1 Dec 31 1969 ttyv1 crw--- 1 root wheel 12, 2 Dec 31 1969 ttyv2 crw--- 1 root wheel 12, 3 Dec 31 1969 ttyv3 crw--- 1 root wheel 12, 4 Dec 31 1969 ttyv4 crw--- 1 root wheel 12, 5 Dec 31 1969 ttyv5 crw--- 1 root wheel 12, 6 Dec 31 1969 ttyv6 crw--- 1 root wheel 12, 7 Dec 31 1969 ttyv7 crw--- 1 root wheel 12, 8 Dec 31 1969 ttyv8 crw--- 1 root wheel 12, 9 Dec 31 1969 ttyv9 crw--- 1 root wheel 12, 10 Dec 31 1969 ttyva crw--- 1 root wheel 12, 11 Dec 31 1969 ttyvb crw--- 1 root wheel 12, 12 Dec 31 1969 ttyvc crw--- 1 root wheel 12, 13 Dec 31 1969 ttyvd crw--- 1 root wheel 12, 14 Dec 31 1969 ttyve crw--- 1 root wheel 12, 15 Dec 31 1969 ttyvf crw-rw-rw- 1 root wheel 2, 4 Dec 31 1969 urandom crw-r--r-- 1 root operator 108, 255 Dec 31 1969 usb crw-r--r-- 1 root operator 108, 0 Dec 31 1969 usb0 lrw-r---w- 1 root wheel0 Dec 31 1969 vga -> /dev/ttyv0 crw--- 1 root operator 104,
Re: Review requested for /dev/random driver improvements!
Mark Murray wrote: > > > So, at least I know the hang is occuring at random: . > > OK; please uncomment the #define DEBUG in yarrow.c and let me know what > the output of that looks like? I get random: Random init and then my machine just locks up tight, right there. -Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Review requested for /dev/random driver improvements!
> So, at least I know the hang is occuring at random: . OK; please uncomment the #define DEBUG in yarrow.c and let me know what the output of that looks like? Thanks! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Review requested for /dev/random driver improvements!
Basically, it is hanging immediately after this message: Preloaded elf kernel "kernel.old" at 0xc0392000. Intel Pentium detected, installing workaround for F00F bug nulldev: I couldn't even drop into the debugger, because my machine was locked solid. The next boot message WOULD'VE been: random: So, at least I know the hang is occuring at random: . -Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
On 23 Aug, Paul Richards wrote: >> > On a vaguely related topic, after much searching I can't seem to see one >> > way or the other if we can do a complete bit-by-bit copy of a cd with >> > either cdrecord or burncd, though it's possible I'm looking in the wrong >> > place. >> >> I think cdrecord can burn CDs in disk-at-once mode, and I think cdrdao (in >> ports/audio) can do it as well. >> >> As far as getting an image, you can use dd to dump off an image of a CD if >> it is a standard ISO9660 CD. (I've used that method to clone CDs before.) > > That didn't seem to work when I tried it a couple of days ago. Got a > "device not configured" error. You've done something wrong, it works here. BTW: If I need a copy of a data cd I use "cdrecord -v speed=4 dev=0,1,0 -eject -isosize /dev/cd1c" (cd1 is my CD-ROM, cd0 (dev=0,1,0) is my CD burner). Bye, Alexander. -- Speak softly and carry a cellular phone. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than /usr/local?
On Wed, Aug 23, 2000 at 01:36:56PM +0100, Konstantin Chuguev wrote: > Just wondering: what is the reason of using /opt instead of /usr/local, > apart from Solaris influence? No Solaris influence, actually. Just strlen("/opt") < strlen("/usr/local"). It looks nicer to me. Secondarily to see if a ports behaves when ${LOCALBASE} != /usr/local. > Do you use /usr/local for anything? Nope. -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than /usr/local?
On Wed, 23 Aug 2000 13:36:56 +0100, Konstantin Chuguev wrote: > Just wondering: what is the reason of using /opt instead of /usr/local, > apart from Solaris influence? Do you use /usr/local for anything? NetBSD uses /usr/opt . It's a matter of taste. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than /usr/local?
"Jacques A. Vidrine" wrote: > On Wed, Aug 23, 2000 at 01:01:59AM -0500, Mike Meyer wrote: > > Um - why? If you removed the setting of LOCALBASE in that case, you > > wouldn't change the disk layout at all. > > I prefer installed executables, data files, and man pages to refer to > /opt. Duh. > Just wondering: what is the reason of using /opt instead of /usr/local, apart from Solaris influence? Do you use /usr/local for anything? -- * *Konstantin Chuguev - Application Engineer * * Francis House, 112 Hills Road * Cambridge CB2 1PQ, United Kingdom D A N T E WWW:http://www.dante.net To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
-On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote: >-=-=- >===> libexec/fingerd >cc -O -pipe -I/usr/obj/src/src/i386/usr/include -c /src/src/libexec/fingerd/fi >ngerd.c >cc -O -pipe -I/usr/obj/src/src/i386/usr/include -o fingerd fingerd.o -lutil >/usr/obj/src/src/i386/usr/lib/libutil.so: undefined reference to `crypt_set_form >at' >*** Error code 1 This should be fixed after my commit. -- Jeroen Ruigrok van der Werven Network- and systemadministrator <[EMAIL PROTECTED]>VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Morpheus in my Heart, your sand in my veins... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than /usr/local?
On Wed, Aug 23, 2000 at 01:01:59AM -0500, Mike Meyer wrote: > Um - why? If you removed the setting of LOCALBASE in that case, you > wouldn't change the disk layout at all. I prefer installed executables, data files, and man pages to refer to /opt. Duh. > However, I was wondering if there was anyone who could fix things that > weren't PREFIX clean who would also find them on a regular basis. > That's not you. Sorry to disappoint you. Patches are welcome. -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Review requested for /dev/random driver improvements!
> > Clean out your tree and reapply the patches; they got applied twice to some > > files :-) > > OK, earlier I had done just that. After re-compiling and rebooting, my > machine hangs at the beginning point of the boot stage, where it says > "Pentium F00F bug detected". The boot just halts right there. There was > no panic, just a dead hang. Please drop into the debugger and see if you can find out what it is doing. (Or just where the hang is happening). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
"Kenneth D. Merry" wrote: > > On Tue, Aug 22, 2000 at 20:43:15 -0400, Laurence Berland wrote: > > On a vaguely related topic, after much searching I can't seem to see one > > way or the other if we can do a complete bit-by-bit copy of a cd with > > either cdrecord or burncd, though it's possible I'm looking in the wrong > > place. > > I think cdrecord can burn CDs in disk-at-once mode, and I think cdrdao (in > ports/audio) can do it as well. > > As far as getting an image, you can use dd to dump off an image of a CD if > it is a standard ISO9660 CD. (I've used that method to clone CDs before.) That didn't seem to work when I tried it a couple of days ago. Got a "device not configured" error. Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: default mount(8) output format changed
Hi folks, Again, this is hardly worth a HEADS UP. The default output format for mount(8) has changed; sync and async read and writes statistics aren't printed unless the -v option is used. This does not apply to the output produced by the -p option, which has never printed these statistics. I've checked that this doesn't break any rc or periodic scripts, but if you use the output of mount(8) (without -p) to feed some specialized parser, make sure you add the -v option to its invocation. Thanks, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Review requested for /dev/random driver improvements!
On Wed, 23 Aug 2000, Mark Murray wrote: > > I just tried the patch, which completed successfully. But now, I'm > > getting these errors (see attached make.log). > > Clean out your tree and reapply the patches; they got applied twice to some > files :-) OK, earlier I had done just that. After re-compiling and rebooting, my machine hangs at the beginning point of the boot stage, where it says "Pentium F00F bug detected". The boot just halts right there. There was no panic, just a dead hang. -Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
-On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote: >Brian, I'm afraid you broke libutil... Every program using libutil now must >depend on libcrypt too. > >-=-=- >===> libexec/fingerd >cc -O -pipe -I/usr/obj/src/src/i386/usr/include -c /src/src/libexec/fingerd/fi >ngerd.c >cc -O -pipe -I/usr/obj/src/src/i386/usr/include -o fingerd fingerd.o -lutil >/usr/obj/src/src/i386/usr/lib/libutil.so: undefined reference to `crypt_set_form >at' >*** Error code 1 > >Stop in /src/src/libexec/fingerd. >*** Error code 1 I get the same thing, even with Brian's latest commit. -- Jeroen Ruigrok van der Werven Network- and systemadministrator <[EMAIL PROTECTED]>VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Haste makes waste... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Review requested for /dev/random driver improvements!
> I just tried the patch, which completed successfully. But now, I'm > getting these errors (see attached make.log). Clean out your tree and reapply the patches; they got applied twice to some files :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
It seems Laurence Berland wrote: > On a vaguely related topic, after much searching I can't seem to see one > way or the other if we can do a complete bit-by-bit copy of a cd with > either cdrecord or burncd, though it's possible I'm looking in the wrong > place. Uhm, I've had some success with changing the READ_CD flags in atapi-cd from 0x10 to 0xf8, that will make the driver read the entire block (2352bytes) no matter what format it is. Then burning it is bitch since DAO mode is not in the official sources yet, but with a bit of enginuity it can be done.. Or use cdrdao on a SCSI burner... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
It seems Mike Meyer wrote: > > I'm planning on implementing all the CDR ioctls for SCSI cds. > > BTW, are those documented somewhere? I mean, I can work out what they > should do, but they still ought to be on a man page. Soren? Uhm, no man page I'm afraid, but I'll answer any questions you might have... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than /usr/local?
Mark Murray writes: > > However, I was wondering if there was anyone who could fix things that > > weren't PREFIX clean who would also find them on a regular > > basis. That's not you. > There is a non-trivial Perl5 LOCALBASE problem that I'm trying to > get my head around. I'm actually discussing one of the PR's related to this now, and had a thought. Is it possible to specify an installation directory in the perl module installation process? If so, then the bsd.port.mk mechanism needs to be tweaked to use that to set things to LOCALBASE (well, PREFIX), and the perl build should add $(LOCALBASE)/lib/5.6.0 to the search path for modules. Thanx,
Re: People running with LOCALBASE set to something other than /usr/local?
Mark Murray writes: > > However, I was wondering if there was anyone who could fix things that > > weren't PREFIX clean who would also find them on a regular > > basis. That's not you. > There is a non-trivial Perl5 LOCALBASE problem that I'm trying to > get my head around. If this is the problem with perl modules installing in /usr/local no matter where LOCALBASE points, I reported it at one point. Non-trivial is an understatement.
Re: Review requested for /dev/random driver improvements!
Mark Murray wrote: > > > I'm getting some errors trying to build this. Attached is my make.log > > that shows the errors. > > The one that's there now should fix this (I forgot to include a 1-line > patch to sys/conf/files). I just tried the patch, which completed successfully. But now, I'm getting these errors (see attached make.log). -Donn cc -c -march=pentium -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/genassym.c sh ../../kern/genassym.sh genassym.o > assym.s rm -f param.c cp ../../conf/param.c . perl5 ../../kern/vnode_if.pl -h ../../kern/vnode_if.src cc -march=pentium -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 -c ../../i386/linux/linux_genassym.c sh ../../kern/genassym.sh linux_genassym.o > linux_assym.h perl5 ../../kern/vnode_if.pl -c ../../kern/vnode_if.src perl5 ../../kern/makeobjops.pl -h ../../kern/device_if.m perl5 ../../kern/makeobjops.pl -h ../../kern/bus_if.m perl5 ../../kern/makeobjops.pl -h ../../kern/linker_if.m perl5 ../../kern/makeobjops.pl -h ../../dev/ppbus/ppbus_if.m perl5 ../../kern/makeobjops.pl -h ../../isa/isa_if.m perl5 ../../kern/makeobjops.pl -h ../../pci/pci_if.m rm -f .newdep mkdep -a -f .newdep -march=pentium -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/ed/if_ed_pci.c ../../dev/md/md.c ../../dev/nulldev/nulldev.c ../../dev/ppbus/if_plip.c ../../dev/ppbus/lpt.c ../../dev/ppbus/ppb_1284.c ../../dev/ppbus/ppb_base.c ../../dev/ppbus/ppb_msq.c ../../dev/ppbus/ppbconf.c ../../dev/ppbus/ppi.c ../../dev/randomdev/harvest.c ../../dev/randomdev/randomdev.c ../../dev/randomdev/yarrow.c ../../dev/randomdev/hash.c ../../crypto/blowfish/bf_cbc.c ../../crypto/blowfish/bf_enc.c ../../crypto/blowfish/bf_skey.c ../../dev/sound/isa/ad1816.c ../../dev/sound/isa/es1888.c ../../dev/sound/isa/ess.c ../../dev/sound/isa/gusc.c ../../dev/sound/isa/mss.c ../../dev/sound/isa/sb.c ../../dev/sound/isa/sbc.c ../../dev/sound/pci/csa.c ../../dev/sound/pci/csapcm.c ../../dev/sound/pci/ds1.c ../../dev/sound/pci/emu10k1.c ../../dev/sound/pci/es137x.c ../../dev/sound/pci/neomagic.c ../../dev/sound/pci/solo.c ../../dev/sound/pci/t4dwave.c ../../dev/sound/pci/via82c686.c ../../dev/sound/pcm/ac97.c ../../dev/sound/pcm/channel.c ../../dev/sound/pcm/dsp.c ../../dev/sound/pcm/fake.c ../../dev/sound/pcm/feeder.c ../../dev/sound/pcm/mixer.c ../../dev/sound/pcm/sound.c ../../gnu/ext2fs/ext2_alloc.c ../../gnu/ext2fs/ext2_balloc.c ../../gnu/ext2fs/ext2_inode.c ../../gnu/ext2fs/ext2_inode_cnv.c ../../gnu/ext2fs/ext2_linux_balloc.c ../../gnu/ext2fs/ext2_linux_ialloc.c ../../gnu/ext2fs/ext2_lookup.c ../../gnu/ext2fs/ext2_subr.c ../../gnu/ext2fs/ext2_vfsops.c ../../gnu/ext2fs/ext2_vnops.c ../../isa/isa_common.c ../../isa/isahint.c ../../isa/pnp.c ../../isa/pnpparse.c ../../isofs/cd9660/cd9660_bmap.c ../../isofs/cd9660/cd9660_lookup.c ../../isofs/cd9660/cd9660_node.c ../../isofs/cd9660/cd9660_rrip.c ../../isofs/cd9660/cd9660_util.c ../../isofs/cd9660/cd9660_vfsops.c ../../isofs/cd9660/cd9660_vnops.c ../../kern/imgact_aout.c ../../kern/imgact_elf.c ../../kern/imgact_shell.c ../../kern/init_main.c ../../kern/init_sysent.c ../../kern/kern_acct.c ../../kern/kern_acl.c ../../kern/kern_cap.c ../../kern/kern_clock.c ../../kern/kern_conf.c ../../kern/kern_descrip.c ../../kern/kern_environment.c ../../kern/kern_event.c ../../kern/kern_exec.c ../../kern/kern_exit.c ../../kern/kern_fork.c ../../kern/kern_intr.c ../../kern/kern_jail.c ../../kern/kern_kthread.c ../../kern/kern_ktrace.c ../../kern/kern_linker.c ../../kern/kern_lock.c ../../kern/kern_lockf.c ../../kern/kern_malloc.c ../../kern/kern_mib.c ../../kern/kern_module.c ../../kern/kern_ntptime.c ../../kern/kern_physio.c ../../kern/kern_proc.c ../../kern/kern_prot.c ../../kern/kern_resource.c ../../kern/kern_shutdown.c ../../kern/kern_sig.c ../../kern/kern_subr.c ../../kern/kern_switch.c ../../kern/kern_synch.c ../../kern/kern_syscalls.c ../../kern/kern_sysctl.c ../../kern/kern_tc.c ../../kern/kern_threads.c ../../kern/kern_time.c ../../kern/kern_timeout.c ../../kern/kern_xxx.c ../../kern/link_aout.c ../../kern/link_elf.c ../../kern/md5c.c ../../kern/subr_autoconf.c ../../kern/subr_blist.c ../../kern/subr_bus.c ../../kern/subr_devstat.c ../../kern/subr_disk.c ../../kern/subr_disklabel.c