From owner-freebsd-hackers Sun Nov 5 0:53:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 2542C37B479; Sun, 5 Nov 2000 00:53:10 -0800 (PST) Received: from newsguy.com (p04-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.133]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id RAA17918; Sun, 5 Nov 2000 17:53:01 +0900 (JST) Message-ID: <3A051B10.3E43D0C9@newsguy.com> Date: Sun, 05 Nov 2000 17:32:16 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: Mike Smith , Poul-Henning Kamp , hackers@FreeBSD.ORG Subject: Re: user-space resource information... References: <3248.973365649@critter> <200011041952.eA4JqZF11774@mass.osd.bsdi.com> <20001104221812.A14843@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > > I think vmstat(8) might be a better fit than iostat. vmstat already > displays kernel memory usage (-m), interrupt usage (-i), paging stats (-s), > and zone allocator stats (-z). That's vmstat's problem, not a feature. :-) That kind of thinking is what led to Linux /proc. > Since vmstat already has "kitchen sink" type functionality (i.e. a wide > variety of uses), I think it would probably work better to put this new > functionality there. If it's not vm-related, it shouldn't be listed by vmstat. > iostat is also designed primarily for continuous output use -- displaying a > line of stats every N seconds. vmstat is also designed for that in its That's the objection I raised to Mike. :-) I suggested systat, though that has it's problems too. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@world.wide.bsdconspiracy.net He has been convicted of criminal possession of a clue with intent to distribute. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 1:13:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from public.ndh.com (public.ndh.net [195.94.90.21]) by hub.freebsd.org (Postfix) with ESMTP id 59BD837B4D7 for ; Sun, 5 Nov 2000 01:13:16 -0800 (PST) Received: from elan.firekeys.org (port2135.duesseldorf.ndh.net [195.227.37.135]) by public.ndh.com (8.9.3/8.8.0) with ESMTP id KAA02068 for ; Sun, 5 Nov 2000 10:13:13 +0100 (MET) Date: Sun, 5 Nov 2000 10:13:12 +0100 (CET) Message-Id: <200011050913.eA59DCM02249@elan.firekeys.org> From: Stefan Moeding To: freebsd-hackers@freebsd.org Subject: Bogus filename error with pkg_add Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Reply-To: s.moeding@ndh.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm working on a port which tries to install some files containing a "'" character in the filename. The ports system works well but when I create the package and try to install it with pkg_add it bombs with a "Bogus filename" message. The code in /usr/src/usr.sbin/pkg_install/add/extract.c looks like this: if (strrchr(p->name,'\'')) { cleanup(0); errx(2, __FUNCTION__ ": Bogus filename \"%s\"", p->name); } I know that "'" might not be the best character for filenames but what exactly is the reason for pkg_add not allowing those characters? After all the installation as a port works fine. Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 2:46: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from minerva.springer.cx (cgmd77002.chello.nl [212.83.77.2]) by hub.freebsd.org (Postfix) with ESMTP id E2A2737B4C5 for ; Sun, 5 Nov 2000 02:45:58 -0800 (PST) Received: from springer.cx (aurum.rinkspringer.com [172.16.0.2]) by minerva.springer.cx (8.9.3/8.9.3) with ESMTP id KAA31636; Sun, 5 Nov 2000 10:56:04 -0500 Message-ID: <3A055656.30605@springer.cx> Date: Sun, 05 Nov 2000 12:45:10 +0000 From: Rink Springer User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.1-RELEASE i386; en-US; m15) X-Accept-Language: en MIME-Version: 1.0 To: Sergey Babkin Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: KLD's on ISA bus: how? References: <3A04A8CD.6BDBB8CD@bellatlantic.net> <3A044899.9020508@springer.cx> <200011042344.QAA37170@harmony.village.org> <200011050035.RAA37476@harmony.village.org> <3A04C46A.24DF7BA6@bellatlantic.net> Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sergey Babkin wrote: Hi, I've got a probe, attach and a dummy identify procedure for my driver now. When I load the KLD, my identify procedure gets triggered, but the probe procedure doesn't! Why? Can someone help me? I've tightly used aha_isa.c as a help... for some reason, FreeBSD doesn't appear even to CALL the probe thing! Please help me! Thanks! --Rink > > Warner Losh wrote: > > > > > > In message <3A04A8CD.6BDBB8CD@bellatlantic.net> Sergey Babkin writes: > > > > > : In 4.x if you say in config file > > > : > > > : foo at isa > > > : > > > : and provide the identify routine in the driver the result should be > > > : the same. The "ep" driver does that using a proprietary probe > > > : procedure. > > > > > > Most cards don't have that backdoor. They are either full plug and > > > play, or they are rock stupid. Come to think of it, there are some > > > that are both :-). The foo at isa might not work even in 4.x. It > > > will attach a child with no hints at all, so the probe routine won't > > > know where to look. The identify routine is the only way to deal. In > > > 4.x, you say > > > device ep > > > not > > > device ep at isa > > > iirc. > > > > Ah, right. I confused it with another case, where the probe routine > > tries to look for all possible ports. If I remember correctly, > > "aha" is an example of such device. > > > > -SB > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 3: 9: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 9A1C337B4CF; Sun, 5 Nov 2000 03:08:53 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 5 Nov 2000 11:08:40 +0000 (GMT) To: Doug Ambrisko Cc: John Hay , Mike Smith , Danny Braniss , freebsd-hackers@FreeBSD.ORG Subject: Re: dhcp boot was: Re: diskless workstation In-Reply-To: Your message of "Sat, 04 Nov 2000 12:37:16 PST." <200011042037.MAA63521@whistle.com> Date: Sun, 05 Nov 2000 11:08:38 +0000 From: Ian Dowse Message-ID: <200011051108.aa63419@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011042037.MAA63521@whistle.com>, Doug Ambrisko writes: >| to the kernel's output. I had a look at the pxe code in >| /sys/boot/i386/libi386/pxe.c where pxeboot is built from and in >| /sys/i386/i386/autoconf.c which is the kernel side and it looks like >| they don't do anything about swap. There is a /* XXX set up swap? */ >| placeholder though. :-) > >Yep looks like you're right, I just tried it on 4.2-BETA it worked in >4.1.1. Swap is now broken ... sigh this is going to be a problem. I >guess the only thing you might be able to do in the interim is to do a >vnconfig of a file and then mount that as swap. I think the vnconfig >man pages describes this. Hopefully it works over NFS. The diskless setup we use here is based on a compiled-in MFS root rather than an NFS root, so we couldn't use the bootp code to enable NFS swap. Our solution was a modification to swapon() to enable direct swapping to NFS regular files. This results in the same swaponvp() call that the bootp code would use (at the time we implemented this, swapping over NFS via vnconfig was extremely unreliable; I think things are much better now). The patch we use is below. Ian Index: vm_swap.c =================================================================== RCS file: /FreeBSD/FreeBSD-CVS/src/sys/vm/vm_swap.c,v retrieving revision 1.96 diff -u -r1.96 vm_swap.c --- vm_swap.c 2000/01/25 17:49:12 1.96 +++ vm_swap.c 2000/11/05 11:04:34 @@ -202,10 +202,14 @@ NDFREE(&nd, NDF_ONLY_PNBUF); vp = nd.ni_vp; - vn_isdisk(vp, &error); - - if (!error) + if (vn_isdisk(vp, &error)) error = swaponvp(p, vp, vp->v_rdev, 0); + else if (vp->v_type == VREG && vp->v_tag == VT_NFS) { + struct vattr attr; + error = VOP_GETATTR(vp, &attr, p->p_ucred, p); + if (!error) + error = swaponvp(p, vp, NODEV, attr.va_size/DEV_BSIZE); + } if (error) vrele(vp); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 3:40:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from minerva.springer.cx (cgmd77002.chello.nl [212.83.77.2]) by hub.freebsd.org (Postfix) with ESMTP id 6072A37B4CF for ; Sun, 5 Nov 2000 03:40:06 -0800 (PST) Received: from springer.cx (aurum.rinkspringer.com [172.16.0.2]) by minerva.springer.cx (8.9.3/8.9.3) with ESMTP id MAA31952; Sun, 5 Nov 2000 12:40:16 -0500 Message-ID: <3A056311.8030807@springer.cx> Date: Sun, 05 Nov 2000 13:39:29 +0000 From: Rink Springer User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.1-RELEASE i386; en-US; m15) X-Accept-Language: en MIME-Version: 1.0 To: Sergey Babkin Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: KLD's on ISA bus: how? References: <3A04A8CD.6BDBB8CD@bellatlantic.net> <3A044899.9020508@springer.cx> <200011042344.QAA37170@harmony.village.org> <200011050035.RAA37476@harmony.village.org> <3A04C46A.24DF7BA6@bellatlantic.net> Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'd like to point out that I'm writing a KLD driver, so the problem shouldn't be in the kernel, correct? For some reason, FreeBSD refuses to call my probe() thing. It does identify() it, though. Why is this? Aha.c does an ISA auto-detect, which I want to do too... why does it work for AHA and not for me? Help! PS. I couldn't find a hints file or something, as someone pointed out... Thanks! --Rink > > Warner Losh wrote: > > > > > > In message <3A04A8CD.6BDBB8CD@bellatlantic.net> Sergey Babkin writes: > > > > > : In 4.x if you say in config file > > > : > > > : foo at isa > > > : > > > : and provide the identify routine in the driver the result should be > > > : the same. The "ep" driver does that using a proprietary probe > > > : procedure. > > > > > > Most cards don't have that backdoor. They are either full plug and > > > play, or they are rock stupid. Come to think of it, there are some > > > that are both :-). The foo at isa might not work even in 4.x. It > > > will attach a child with no hints at all, so the probe routine won't > > > know where to look. The identify routine is the only way to deal. In > > > 4.x, you say > > > device ep > > > not > > > device ep at isa > > > iirc. > > > > Ah, right. I confused it with another case, where the probe routine > > tries to look for all possible ports. If I remember correctly, > > "aha" is an example of such device. > > > > -SB > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 6: 0:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 0C8EF37B479; Sun, 5 Nov 2000 05:59:31 -0800 (PST) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13sQJy-00034q-00; Sun, 05 Nov 2000 15:58:54 +0200 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13sQJx-00041A-00; Sun, 05 Nov 2000 15:58:53 +0200 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Alfred Perlstein Cc: Paul Saab , John Baldwin , freebsd-hackers@FreeBSD.ORG Subject: pxe Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Nov 2000 15:58:53 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, I'm trying to figure out why in pxe.c (sys/boot/i386/libi386) the ip in ip:path is quietly ignored. there must be a reason, but it escapes me. the problem im having, is that since my nfs-root server is not the dhcpd-server, the only way to give it the root nfs ip, is via the option swap-server. tia, danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 6: 5:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurum.springer.cx (cgmd77002.chello.nl [212.83.77.2]) by hub.freebsd.org (Postfix) with ESMTP id 8358637B4CF for ; Sun, 5 Nov 2000 06:05:28 -0800 (PST) Received: by aurum.springer.cx (8.9.3/8.9.3) id QAA91853; Sun, 5 Nov 2000 16:04:52 GMT (envelope-from rink) From: Rink Springer VII To: Takanori Watanabe Subject: Re: KLD's on ISA bus: how? Date: Sun, 5 Nov 2000 16:04:10 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: hackers@FreeBSD.ORG References: <200011041548.AAA39517@shidahara1.planet.sci.kobe-u.ac.jp> In-Reply-To: <200011041548.AAA39517@shidahara1.planet.sci.kobe-u.ac.jp> MIME-Version: 1.0 Message-Id: <00110516045101.91668@aurum.springer.cx> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [snip] > There is two way. > > 1.Write device_identify method and put auto-probe scheme to this.and ,if found, > use BUS_ADD_CHILD to add your driver as ISA driver and > use BUS_SET_RESOURCE to set resource you found. What are the prototypes of these? Can't find them... vpo.c has it for BUS_ADD_CHILD, which FINALLY causes FreeBSD to probe my neat device (yay!), but the SET_RESOURCE thing, what's the syntax? Thanks! --Rink To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 6:50:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 1020037B4CF for ; Sun, 5 Nov 2000 06:50:34 -0800 (PST) Received: from localnet.cwnt.co.il (ras7-171.hfa.netvision.net.il [62.0.191.175]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id QAA18821 for ; Sun, 5 Nov 2000 16:50:32 +0200 (IST) Received: from 192.168.0.146 ([192.168.0.146]) by localnet.cwnt.co.il (WinRoute 3.04g) with SMTP; Sun, 5 Nov 2000 12:45:45 +0200 Message-ID: <001c01c04716$7c710c50$9200a8c0@ido> From: "Ido Barnea" To: Subject: sppp driver bug? Date: Sun, 5 Nov 2000 12:52:26 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_01C04727.3FF3C1D0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0019_01C04727.3FF3C1D0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Hi I am trying to use the sppp driver of the 4.1FreeBSD to establish ip = connection over ppp between two pc's. It usually works, but in a small percentage of the cases one of the = interfaces gets stack in the following state: lcp is in state closed and ipcp is in state closed (I know that for sure = from debug prints I added). The real problem is that nothing seems to get the interface out of its = "problematic" state. (I tried putting it down and up, transferring it to = hdlc and back and more...) I think the following change in sppp_lcp_tld will enable the interface = to recover using ifconfig down and up. original lines: for (i =3D 0, mask =3D 1; i < IDX_COUNT; i++, mask <<=3D 1) if (sp->lcp.protos & mask && ((cps[i])->flags & CP_LCP) =3D=3D 0) { My suggested lines: for (i =3D 0; i < IDX_COUNT; i++) if (((cps[i])->flags & CP_LCP) =3D=3D 0) { The idea here is that since the ipcp is in closed state, its bit in the = lcp.protos is not set, so it never receives the down and close event (inside the if). It also does not put the bit on = when getting open event (since it is in the stopped state), so it never = receives up event in sppp_lcp_tlu. If anyone has an idea why the interface gets stack in the first place, = I'll be very glad to hear. I also want to know if my code change seems reasonable. Thanks, Ido ------=_NextPart_000_0019_01C04727.3FF3C1D0 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable
Hi
 I am trying to use the sppp = driver of the=20 4.1FreeBSD to establish ip connection over ppp between two=20 pc's.
 It usually works, but = in a small=20 percentage of the cases one of the interfaces gets stack in the = following=20 state:
lcp is in state closed and = ipcp is in=20 state closed (I know that for sure from debug prints I = added).
 
The real problem is that = nothing seems=20 to get the interface out of its "problematic" state. (I = tried putting it=20 down and up, transferring it to hdlc and back and more...)
 
I think the following change = in=20 sppp_lcp_tld will enable the interface to recover using ifconfig down = and=20 up.
original lines:
  for (i =3D 0,=20 mask =3D 1; i < IDX_COUNT; i++, mask <<=3D 1)
  if = (sp->lcp.protos & mask && ((cps[i])->flags & = CP_LCP) =3D=3D 0)=20 {
 
My suggested = lines:
 for (i =3D 0; i < IDX_COUNT;=20 i++)
      if (((cps[i])->flags & = CP_LCP) =3D=3D=20 0) {
 
The idea here is that since = the ipcp is=20 in closed state, its bit in the lcp.protos is not set, so it never = receives=20 the
down and close event (inside = the if). It=20 also does not put the bit on when getting open event (since it is in the = stopped=20 state), so it never receives up event in sppp_lcp_tlu.
 
If anyone has an idea why = the interface=20 gets stack in the first place, I'll be very glad to hear.
I also want to know if = my code=20 change seems reasonable.
 
Thanks, Ido
 
 
------=_NextPart_000_0019_01C04727.3FF3C1D0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 6:54:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurum.springer.cx (cgmd77002.chello.nl [212.83.77.2]) by hub.freebsd.org (Postfix) with ESMTP id 3366637B479 for ; Sun, 5 Nov 2000 06:54:23 -0800 (PST) Received: by aurum.springer.cx (8.9.3/8.9.3) id QAA91961; Sun, 5 Nov 2000 16:52:47 GMT (envelope-from rink) From: Rink Springer VII To: Warner Losh Subject: KLD's on ISA: another problem Date: Sun, 5 Nov 2000 16:37:57 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: hackers@FreeBSD.ORG References: <3A044899.9020508@springer.cx> <200011042344.QAA37170@harmony.village.org> In-Reply-To: <200011042344.QAA37170@harmony.village.org> MIME-Version: 1.0 Message-Id: <00110516524700.91928@aurum.springer.cx> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, It works nicer now... the IDENTIFY code will now happily tell FreeBSD the device is at 0x378, IRQ 7. The code I used for this is: static void dl_identify (driver_t* driver,device_t parent) { device_t t; printf ("DL: IDENTIFY\n"); t = BUS_ADD_CHILD (parent, 0, "dl", 0); bus_set_resource (t, SYS_RES_IOPORT, 0, 0x378, 3); bus_set_resource (t, SYS_RES_IRQ, 0, 7, 1); } static int dl_probe (device_t dev) { struct dl_softc* sc = device_get_softc (dev); int rid = 0; sc->ioaddr = bus_get_resource_start (dev, SYS_RES_IOPORT, 0); sc->iobase = bus_alloc_resource (dev, SYS_RES_IOPORT, &rid, 0ul, ~0ul, 3, RF_ACTIVE); /* [error check code] */ sc->ioaddr = rman_get_start (sc->iobase); /* [probe stuff] */ return 0; } static int dl_attach (device_t dev) { int rid; struct dl_softc* sc = device_getr_softc(dev); void *ih; printf ("dl0: grab IRQ\n"); sc->irqbase = bus_alloc_resource (dev, SYS_RES_IRQ, &rid, 0ul, ~0ul, 1, RF_ACTIVE); /* [ error check ] */ printf ("dl0: set IRQ handkler\n"); if (bus_setup_intr (dev, sc->irqbase, INTR_TYPE_NET, dl_intr, (void*)sc, &ih)) { /* [error check] */ } printf ("dl0: DONE!\n"); } But upon loading, it *CRASHES* (!) FreeBSD after the dl0: DONE thing... HELP! Anyone know how I can fix this? Sorry for all those messages lately, but I really want this to work! Thanks! --Rink To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 7:33:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 06D0E37B4CF for ; Sun, 5 Nov 2000 07:33:24 -0800 (PST) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id D4DB3A82B; Mon, 6 Nov 2000 02:33:21 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id CE5655464 for ; Mon, 6 Nov 2000 01:33:21 +1000 (EST) Date: Mon, 6 Nov 2000 01:33:21 +1000 (EST) From: andrew@ugh.net.au To: freebsd-hackers@freebsd.org Subject: gdb & threaded application Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a program compiled with -pthread and I'm trying to use gdb to debug it. I run the program in one window and then try to attach to it from another. I have put a sleep 10 in the program so I can catch it before it enters the section I want to debug. This is what I get: Attaching to program: /usr/home/andrew/work/msgs2/msgs, process 10063 Reading symbols from /usr/lib/libc_r.so.4...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. 0x280b7368 in _thread_sys_poll () from /usr/lib/libc_r.so.4 (gdb) n Single stepping until exit from function _thread_sys_poll, which has no line number information. 0x280b674f in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.4 (gdb) n Single stepping until exit from function _thread_kern_sched_state_unlock, which has no line number information. 0x280b5f99 in _thread_kern_sched () from /usr/lib/libc_r.so.4 (gdb) n Single stepping until exit from function _thread_kern_sched, which has no line number information. 0x28078a70 in _init () from /usr/lib/libc_r.so.4 (gdb) n Single stepping until exit from function _init, which has no line number information. Error accessing memory address 0x158: Bad address. (gdb) n Single stepping until exit from function _thread_kern_sched, which has no line number information. Program received signal SIGSEGV, Segmentation fault. 0x280b591f in _thread_kern_sched () from /usr/lib/libc_r.so.4 (gdb) q The program is running. Quit anyway (and detach it)? (y or n) y Detaching from program: /usr/home/andrew/work/msgs2/msgs, process 10063, thread 1 ptrace: No such process. (gdb) To get out of gdb I need to suspend and kill it. Now this certainly isn't the behaviour I get when running it without the debuger. I haven't spawned any threads at this point. Any ideas what I'm doing wrong? Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 9:49:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 4B67037B479 for ; Sun, 5 Nov 2000 09:49:53 -0800 (PST) Received: from bellatlantic.net (client-151-198-117-206.nnj.dialup.bellatlantic.net [151.198.117.206]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id MAA13673; Sun, 5 Nov 2000 12:41:14 -0500 (EST) Message-ID: <3A059BB9.1487DA3D@bellatlantic.net> Date: Sun, 05 Nov 2000 12:41:13 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Rink Springer Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: KLD's on ISA bus: how? References: <3A04A8CD.6BDBB8CD@bellatlantic.net> <3A044899.9020508@springer.cx> <200011042344.QAA37170@harmony.village.org> <200011050035.RAA37476@harmony.village.org> <3A04C46A.24DF7BA6@bellatlantic.net> <3A055656.30605@springer.cx> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rink Springer wrote: > > Sergey Babkin wrote: > > Hi, > > I've got a probe, attach and a dummy identify procedure for my driver > now. When I load the KLD, my identify procedure gets triggered, but the > probe procedure doesn't! Why? Can someone help me? I've tightly used > aha_isa.c as a help... for some reason, FreeBSD doesn't appear even to > CALL the probe thing! Does your identify() routine add the devices to be probed ? BTW, did you look at my article in DaemonNews from June 2000 (www.daemonnnews.org) ? It has a general description of how these things work in 4.x. Though it does not consider specifically the KLD drivers, things should be the same for them. I think this article should be somewhere in the Handbook too or at least the guys from the docs project were going to include it. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 9:50:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 9178237B479 for ; Sun, 5 Nov 2000 09:50:13 -0800 (PST) Received: from bellatlantic.net (client-151-198-117-206.nnj.dialup.bellatlantic.net [151.198.117.206]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id MAA13689; Sun, 5 Nov 2000 12:43:26 -0500 (EST) Message-ID: <3A059C3E.283BA628@bellatlantic.net> Date: Sun, 05 Nov 2000 12:43:26 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Rink Springer Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: KLD's on ISA bus: how? References: <3A04A8CD.6BDBB8CD@bellatlantic.net> <3A044899.9020508@springer.cx> <200011042344.QAA37170@harmony.village.org> <200011050035.RAA37476@harmony.village.org> <3A04C46A.24DF7BA6@bellatlantic.net> <3A056311.8030807@springer.cx> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rink Springer wrote: > > PS. I couldn't find a hints file or something, as someone pointed out... Hints file is only in -current (AKA 5.0). In 4.x the kernel config file contains this information (which I guess is of no use for KLD drivers). Probably you can do a likewise thing in 4.x with sysctl variables. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 13:12:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 9715A37B4CF; Sun, 5 Nov 2000 13:12:49 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA19245; Sun, 5 Nov 2000 14:12:41 -0700 (MST) (envelope-from ken) Date: Sun, 5 Nov 2000 14:12:41 -0700 From: "Kenneth D. Merry" To: "Daniel C. Sobral" Cc: Mike Smith , Poul-Henning Kamp , hackers@FreeBSD.ORG Subject: Re: user-space resource information... Message-ID: <20001105141241.A19227@panzer.kdm.org> References: <3248.973365649@critter> <200011041952.eA4JqZF11774@mass.osd.bsdi.com> <20001104221812.A14843@panzer.kdm.org> <3A051B10.3E43D0C9@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A051B10.3E43D0C9@newsguy.com>; from dcs@newsguy.com on Sun, Nov 05, 2000 at 05:32:16PM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 05, 2000 at 17:32:16 +0900, Daniel C. Sobral wrote: > "Kenneth D. Merry" wrote: > > > > I think vmstat(8) might be a better fit than iostat. vmstat already > > displays kernel memory usage (-m), interrupt usage (-i), paging stats (-s), > > and zone allocator stats (-z). > > That's vmstat's problem, not a feature. :-) > > That kind of thinking is what led to Linux /proc. > > > Since vmstat already has "kitchen sink" type functionality (i.e. a wide > > variety of uses), I think it would probably work better to put this new > > functionality there. > > If it's not vm-related, it shouldn't be listed by vmstat. Interrupts aren't vm-related either, yet vmstat displays them. > > iostat is also designed primarily for continuous output use -- displaying a > > line of stats every N seconds. vmstat is also designed for that in its > > That's the objection I raised to Mike. :-) I suggested systat, though > that has it's problems too. Well, perhaps this stuff should go in its own utility, since it doesn't really seem to fit anywhere else. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 13:31:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by hub.freebsd.org (Postfix) with ESMTP id 252B537B4C5 for ; Sun, 5 Nov 2000 13:31:38 -0800 (PST) Received: from fwd07.sul.t-online.com by mailout02.sul.t-online.com with smtp id 13sXO4-0003uk-0A; Sun, 05 Nov 2000 22:31:36 +0100 Received: from venus.system7.de (320051988339-0001@[62.224.113.12]) by fwd07.sul.t-online.com with esmtp id 13sXNr-1HkBM0C; Sun, 5 Nov 2000 22:31:23 +0100 Received: by venus.system7.de (Postfix, from userid 1001) id 50590543B; Sun, 5 Nov 2000 22:31:22 +0100 (CET) Date: Sun, 5 Nov 2000 22:31:21 +0100 From: Sven.Huster@t-online.de (Sven Huster) To: freebsd-hackers@freebsd.org Subject: isp1100 serial console problem Message-ID: <20001105223121.A58010@venus.system7.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Sender: 320051988339-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi there, i just got a intel isp1100 server, which supports redirection of the console to serial ports. the doc mentions that using hypertermial on win you can access the bios via F2, but if i use kermit on freebsd, this does not work. can i setup kermit that it submit function keys to the device the same way hyerterminal does, if it is set to ansi mode. by the way, does anybody know anything about the console redirection to lan, which is also supported by the server? thanks sven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 14:47:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (unknown [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1ABFD37B4C5 for ; Sun, 5 Nov 2000 14:47:44 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eA5Mlgn59501; Sun, 5 Nov 2000 15:47:43 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA04001; Sun, 5 Nov 2000 15:47:42 -0700 (MST) Message-Id: <200011052247.PAA04001@harmony.village.org> To: Rink Springer Subject: Re: KLD's on ISA bus: how? Cc: Sergey Babkin , hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 05 Nov 2000 12:45:10 GMT." <3A055656.30605@springer.cx> References: <3A055656.30605@springer.cx> <3A04A8CD.6BDBB8CD@bellatlantic.net> <3A044899.9020508@springer.cx> <200011042344.QAA37170@harmony.village.org> <200011050035.RAA37476@harmony.village.org> <3A04C46A.24DF7BA6@bellatlantic.net> Date: Sun, 05 Nov 2000 15:47:42 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A055656.30605@springer.cx> Rink Springer writes: : I've got a probe, attach and a dummy identify procedure for my driver : now. When I load the KLD, my identify procedure gets triggered, but the : probe procedure doesn't! Why? Can someone help me? I've tightly used : aha_isa.c as a help... for some reason, FreeBSD doesn't appear even to : CALL the probe thing! Are you actually adding a child device in the identify routine? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 14:48:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (unknown [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3676337B4CF for ; Sun, 5 Nov 2000 14:48:46 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eA5Mmjn59513; Sun, 5 Nov 2000 15:48:45 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA04028; Sun, 5 Nov 2000 15:48:44 -0700 (MST) Message-Id: <200011052248.PAA04028@harmony.village.org> To: Rink Springer Subject: Re: KLD's on ISA bus: how? Cc: Sergey Babkin , hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 05 Nov 2000 13:39:29 GMT." <3A056311.8030807@springer.cx> References: <3A056311.8030807@springer.cx> <3A04A8CD.6BDBB8CD@bellatlantic.net> <3A044899.9020508@springer.cx> <200011042344.QAA37170@harmony.village.org> <200011050035.RAA37476@harmony.village.org> <3A04C46A.24DF7BA6@bellatlantic.net> Date: Sun, 05 Nov 2000 15:48:44 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A056311.8030807@springer.cx> Rink Springer writes: : I'd like to point out that I'm writing a KLD driver, so the problem : shouldn't be in the kernel, correct? Yes : Why is this? Aha.c does an ISA auto-detect, which I want to do too... : why does it work for AHA and not for me? I'll need some code to look at. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 14:52:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (unknown [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D0F3C37B479 for ; Sun, 5 Nov 2000 14:52:11 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eA5Mq6n59532; Sun, 5 Nov 2000 15:52:06 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA04067; Sun, 5 Nov 2000 15:52:05 -0700 (MST) Message-Id: <200011052252.PAA04067@harmony.village.org> To: Rink Springer VII Subject: Re: KLD's on ISA: another problem Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 05 Nov 2000 16:37:57 GMT." <00110516524700.91928@aurum.springer.cx> References: <00110516524700.91928@aurum.springer.cx> <3A044899.9020508@springer.cx> <200011042344.QAA37170@harmony.village.org> Date: Sun, 05 Nov 2000 15:52:05 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <00110516524700.91928@aurum.springer.cx> Rink Springer VII writes: : static void : dl_identify (driver_t* driver,device_t parent) { : device_t t; : : printf ("DL: IDENTIFY\n"); : t = BUS_ADD_CHILD (parent, 0, "dl", 0); : bus_set_resource (t, SYS_RES_IOPORT, 0, 0x378, 3); : bus_set_resource (t, SYS_RES_IRQ, 0, 7, 1); : } You need to check to see if the child is already there or not before adding it. : But upon loading, it *CRASHES* (!) FreeBSD after the dl0: DONE thing... You shouldn't hold any resources after your probe routine. You must free them. It is also generally a bad idea to store things in softc in probe as the device framework is free to destroy the softc iirc. Make sure that your softc size is specified properly, otherwise you may crash. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 14:54:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (unknown [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2A2A437B479 for ; Sun, 5 Nov 2000 14:54:22 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eA5Ms7n59548; Sun, 5 Nov 2000 15:54:08 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA04101; Sun, 5 Nov 2000 15:54:07 -0700 (MST) Message-Id: <200011052254.PAA04101@harmony.village.org> To: Sergey Babkin Subject: Re: KLD's on ISA bus: how? Cc: Rink Springer , hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 05 Nov 2000 12:43:26 EST." <3A059C3E.283BA628@bellatlantic.net> References: <3A059C3E.283BA628@bellatlantic.net> <3A04A8CD.6BDBB8CD@bellatlantic.net> <3A044899.9020508@springer.cx> <200011042344.QAA37170@harmony.village.org> <200011050035.RAA37476@harmony.village.org> <3A04C46A.24DF7BA6@bellatlantic.net> <3A056311.8030807@springer.cx> Date: Sun, 05 Nov 2000 15:54:07 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A059C3E.283BA628@bellatlantic.net> Sergey Babkin writes: : Hints file is only in -current (AKA 5.0). In 4.x the kernel config : file contains this information (which I guess is of no use for : KLD drivers). Probably you can do a likewise thing in 4.x with : sysctl variables. I've ported the meat of the 5.x hints stuff to 4.x for Timing Solution's embedded products. It works great there so I sometimes forget that it isn't in stable. Maybe I should MFC after 4.2 release. All that I merge does is if there are hints in the boot environment, it sets them. It doesn't do all the rest of the stuff Peter did to -current. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 15:54:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurum.springer.cx (cgmd77002.chello.nl [212.83.77.2]) by hub.freebsd.org (Postfix) with ESMTP id BBBAC37B4CF for ; Sun, 5 Nov 2000 15:54:29 -0800 (PST) Received: by aurum.springer.cx (8.9.3/8.9.3) id BAA10087; Mon, 6 Nov 2000 01:53:54 GMT (envelope-from rink) From: Rink Springer VII To: Warner Losh Subject: Re: KLD's on ISA bus: how? Date: Mon, 6 Nov 2000 01:51:21 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: Sergey Babkin , hackers@FreeBSD.ORG References: <3A055656.30605@springer.cx> <3A04C46A.24DF7BA6@bellatlantic.net> <200011052247.PAA04001@harmony.village.org> In-Reply-To: <200011052247.PAA04001@harmony.village.org> MIME-Version: 1.0 Message-Id: <00110601535400.09767@aurum.springer.cx> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 05 Nov 2000, Warner Losh wrote: > In message <3A055656.30605@springer.cx> Rink Springer writes: > : I've got a probe, attach and a dummy identify procedure for my driver > : now. When I load the KLD, my identify procedure gets triggered, but the > : probe procedure doesn't! Why? Can someone help me? I've tightly used > : aha_isa.c as a help... for some reason, FreeBSD doesn't appear even to > : CALL the probe thing! > > Are you actually adding a child device in the identify routine? > > Warner Yes... is that bad? It was the only way to get BSD to probe it. I'll make the source availabletomorrow. too late now. On the sidenote, my BSD box totally CRASHES after I attach the device using the ether_attach call... any idea why? Thanks! --Rink > > > 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 Nov 5 16: 0: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (unknown [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A95D237B4C5 for ; Sun, 5 Nov 2000 15:59:59 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eA5Nxwn59838; Sun, 5 Nov 2000 16:59:58 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA04971; Sun, 5 Nov 2000 16:59:58 -0700 (MST) Message-Id: <200011052359.QAA04971@harmony.village.org> To: Rink Springer VII Subject: Re: KLD's on ISA bus: how? Cc: Sergey Babkin , hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 06 Nov 2000 01:51:21 GMT." <00110601535400.09767@aurum.springer.cx> References: <00110601535400.09767@aurum.springer.cx> <3A055656.30605@springer.cx> <3A04C46A.24DF7BA6@bellatlantic.net> <200011052247.PAA04001@harmony.village.org> Date: Sun, 05 Nov 2000 16:59:58 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <00110601535400.09767@aurum.springer.cx> Rink Springer VII writes: : Yes... is that bad? It was the only way to get BSD to probe it. You should do this only if you haven't done it already. : On the sidenote, my BSD box totally CRASHES after I attach the device using the : ether_attach call... any idea why? I've had this problem in the past. Usually it is due to not giving the softc the right size in the device declaration because I copied it from somewhere that didn't use a softc and specified a '1'. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 16:54:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-14.dsl.snfc21.pacbell.net [63.202.178.14]) by hub.freebsd.org (Postfix) with ESMTP id 68ECF37B479 for ; Sun, 5 Nov 2000 16:54:39 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eA60xaF16031; Sun, 5 Nov 2000 16:59:37 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011060059.eA60xaF16031@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Sven.Huster@t-online.de (Sven Huster) Cc: freebsd-hackers@freebsd.org Subject: Re: isp1100 serial console problem In-reply-to: Your message of "Sun, 05 Nov 2000 22:31:21 +0100." <20001105223121.A58010@venus.system7.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Nov 2000 16:59:36 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > the doc mentions that using hypertermial on win you can access the bios > via F2, but if i use kermit on freebsd, this does not work. Use an xterm and cu. It's expecting ansi function key codes. > can i setup kermit that it submit function keys to the device the same way > hyerterminal does, if it is set to ansi mode. Probably, but I wouldn't be able to tell you how. > by the way, does anybody know anything about the console redirection to > lan, which is also supported by the server? Yes. It's broken and doesn't work as of the latest BIOS from Intel. In fact, enabling it will cause the machine to lock up so hard you need to default the CMOS to get it back. -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 20: 0:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id C15D537B4D7 for ; Sun, 5 Nov 2000 20:00:12 -0800 (PST) Received: (qmail 7004 invoked by uid 1142); 6 Nov 2000 04:00:11 -0000 Date: 5 Nov 2000 20:00:11 -0800 Date: Sun, 5 Nov 2000 20:00:04 -0800 From: Jason Evans To: andrew@ugh.net.au Cc: freebsd-hackers@freebsd.org Subject: Re: gdb & threaded application Message-ID: <20001105200004.O4044@canonware.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from andrew@ugh.net.au on Mon, Nov 06, 2000 at 01:33:21AM +1000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 06, 2000 at 01:33:21AM +1000, andrew@ugh.net.au wrote: > Hi, > > I have a program compiled with -pthread and I'm trying to use gdb to debug > it. I run the program in one window and then try to attach to it from > another. I have put a sleep 10 in the program so I can catch it before it > enters the section I want to debug. This is what I get: > > Attaching to program: /usr/home/andrew/work/msgs2/msgs, process 10063 > Reading symbols from /usr/lib/libc_r.so.4...done. > Reading symbols from /usr/libexec/ld-elf.so.1...done. > 0x280b7368 in _thread_sys_poll () from /usr/lib/libc_r.so.4 ^^^^^^^^^^^ For reasons that I don't entirely understand, using gdb with dynamically linked applications usually produces very undesireable (often totally incorrect) results on FreeBSD. I don't know that this is the problem, but the first thing I'd do if I were you would be to link statically. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 20: 9:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id AA30D37B4E5 for ; Sun, 5 Nov 2000 20:09:34 -0800 (PST) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id D86F3A82B; Mon, 6 Nov 2000 15:09:33 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id D54115464; Mon, 6 Nov 2000 14:09:33 +1000 (EST) Date: Mon, 6 Nov 2000 14:09:33 +1000 (EST) From: andrew@ugh.net.au To: Jason Evans Cc: freebsd-hackers@freebsd.org Subject: Re: gdb & threaded application In-Reply-To: <20001105200004.O4044@canonware.com> Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 5 Nov 2000, Jason Evans wrote: > the first thing I'd do if I were you would be to link statically. Yep that fixed it. Thanks for your time, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 5 23:10:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 34F3537B4C5; Sun, 5 Nov 2000 23:10:31 -0800 (PST) Received: from newsguy.com (p41-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.42]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id QAA20692; Mon, 6 Nov 2000 16:10:25 +0900 (JST) Message-ID: <3A065901.91BBAB7D@newsguy.com> Date: Mon, 06 Nov 2000 16:08:49 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: Mike Smith , Poul-Henning Kamp , hackers@FreeBSD.ORG Subject: Re: user-space resource information... References: <3248.973365649@critter> <200011041952.eA4JqZF11774@mass.osd.bsdi.com> <20001104221812.A14843@panzer.kdm.org> <3A051B10.3E43D0C9@newsguy.com> <20001105141241.A19227@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > ... > > That's vmstat's problem, not a feature. :-) ... > > If it's not vm-related, it shouldn't be listed by vmstat. > > Interrupts aren't vm-related either, yet vmstat displays them. And it shouldn't do so. See my first comment. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@world.wide.bsdconspiracy.net He has been convicted of criminal possession of a clue with intent to distribute. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 2:59:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web3507.mail.yahoo.com (web3507.mail.yahoo.com [204.71.203.74]) by hub.freebsd.org (Postfix) with SMTP id 5E24A37B479 for ; Mon, 6 Nov 2000 02:59:24 -0800 (PST) Message-ID: <20001106105924.9983.qmail@web3507.mail.yahoo.com> Received: from [196.7.146.6] by web3507.mail.yahoo.com; Mon, 06 Nov 2000 02:59:24 PST Date: Mon, 6 Nov 2000 02:59:24 -0800 (PST) From: Jacques Fourie Subject: Debugging KLD's To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I am using the following method to debug a KLD on 4.1 using gdb remote debugging: - Add makeoptions DEBUG=-g to the kernel config - Compile the KLD with -ggdb - Use objdump -h to get the offset of .text in the KLD. - Add this value to the value reported by kldstat and use this as offset for the gdb add-symbol-file command. The problem is that variable values reported by gdb seems to be total garbage. If I add explicit printf's in the C code, the value printed on the console is correct but the values given by gdb are totally different. Everything else seems to be working - I can do a break and the breakpoint will be set correctly. Any help will be greatly appreciated. jacques __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one Place. http://shopping.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 3:44:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.oblivion.bg (pool66-tch-1.Sofia.0rbitel.net [212.95.170.66]) by hub.freebsd.org (Postfix) with SMTP id 4266837B479 for ; Mon, 6 Nov 2000 03:44:51 -0800 (PST) Received: (qmail 1807 invoked by uid 1000); 6 Nov 2000 11:44:37 -0000 Date: Mon, 6 Nov 2000 13:44:37 +0200 From: Peter Pentchev To: hackers@freebsd.org Subject: New mergemaster behavior - comparing CVS $Id too Message-ID: <20001106134437.A556@ringworld.oblivion.bg> Mail-Followup-To: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a way to make mergemaster revert to its old behavior - only comparing $FreeBSD tags on files which have those? I keep some of my /etc files in a CVS repository of my own, and in the last mergemaster runs it detects that the file in /etc has an $Id, while the file in /var/tmp/temproot does not, and reports a difference. (Well, yes, I guess I could remove the $Id tags from my own files, but.. is there another way? :) G'luck, Peter PS. And yes, I know RELENG_4 is frozen now, but.. still.. :) -- I am not the subject of this sentence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 7:38:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id A557937B479 for ; Mon, 6 Nov 2000 07:38:29 -0800 (PST) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id RAA15776 for ; Mon, 6 Nov 2000 17:38:20 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 15675; Mon Nov 6 17:37:22 2000 Message-ID: <3A06B7A7.7665C46A@cequrux.com> Date: Mon, 06 Nov 2000 15:52:39 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Help writing a screen saver module Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all I am trying to write a screen saver module that, when it kicks in, will switch to the first console, and then, if a key is pressed, will switch back to the one that was previously active. The idea is that the first console has something useful running on it, typically a tail -f of the logs. The code that I have at the moment is based on other simple saver modules, and the VT_ACTIVATE ioctl code in syscons.c. However, it just causes a reboot. This isn't a very important piece of code, but before I give up on trying to get it to work, I thought I'd throw it out here and see if anyone has any ideas. Here are the two externally visible routines I've added to syscons.c: ---------------------------------------------------------------------- extern int ActivateConsole(int n); extern int GetActiveConsole(void); int ActivateConsole(int n) { int s = spltty(); sc_clean_up(cur_console); splx(s); return switch_scr(cur_console, n); } int GetActiveConsole(void) { return get_scr_num(); } ---------------------------------------------------------------------- Here is the module code: ---------------------------------------------------------------------- #include #include #include #include #include #include #include #include static int last_active, blanked; extern int ActivateConsole(int); extern int GetActiveConsole(); static int switch_saver(video_adapter_t *adp, int blank) { if (adp->va_info.vi_flags & V_INFO_GRAPHICS) return EAGAIN; if (blank) { if (!blanked) { blanked = 1; last_active = GetActiveConsole(); ActivateConsole(0); } } else { if (blanked) { blanked = 0; ActivateConsole(last_active); } } return 0; } static int switch_init(video_adapter_t *adp) { (void)adp; last_active = blanked = 0; return 0; } static int switch_term(video_adapter_t *adp) { (void)adp; return 0; } static scrn_saver_t switch_module = { "switch_saver", switch_init, switch_term, switch_saver, NULL, }; SAVER_MODULE(switch_saver, switch_module); -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 8:29: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id EBD7237B4CF for ; Mon, 6 Nov 2000 08:29:01 -0800 (PST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id RAA08913; Mon, 6 Nov 2000 17:28:54 +0100 (MET) Date: Mon, 6 Nov 2000 17:28:54 +0100 (CET) From: Harti Brandt To: m_yevmenkin@yahoo.com Cc: hackers@freebsd.org Subject: if_tap and devfs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I recently moved to using devfs and now if_tap seems unusable. Although the module is loaded, it doesn't show up in /dev or as an interface. From a quick comparison with if_tun it seems that this is 'expected' behaviour although I'm not a specialist with devfs. Is this so? If yes, is there somebody working to make if_tap devfs-ready? Or I'm doing something wrong? harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org, lhbrandt@mail.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 10: 8:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.161.193]) by hub.freebsd.org (Postfix) with ESMTP id 02DB737B4CF for ; Mon, 6 Nov 2000 10:08:52 -0800 (PST) Received: from mail.vt.edu (gkar.cc.vt.edu [198.82.161.190]) by lennier.cc.vt.edu (8.11.0/8.11.0) with ESMTP id eA6I8pt397314 for ; Mon, 6 Nov 2000 13:08:51 -0500 (EST) Received: from flaw.vt.edu ([198.82.82.148]) by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0G3M00GBD7QP6I@gkar.cc.vt.edu> for freebsd-hackers@FreeBSD.ORG; Mon, 6 Nov 2000 13:08:50 -0500 (EST) Date: Mon, 06 Nov 2000 13:16:51 -0500 From: Raymond Law Subject: system call and SYSCALL macro X-Sender: flaw@mail.vt.edu To: freebsd-hackers@FreeBSD.ORG Message-id: <4.3.0.20001106131527.00df0cc0@mail.vt.edu> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Content-type: text/plain; format=flowed; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: I am trying to implement a system call. I used the syscalls.master already. I know I have to modify libc, but this requires makeworld and all the binaries must be compiled again. If I don't want to modify libc, I know I have to use the SYSCALL macro or something like that. But I don't know how to use it. Also, I tried the syscall() function but are not getting good results. I just try to add a simple system call for testing: int my_call(int x, int y) { return (x + y); } In my user program: int main(int argc, char ** argv) { int x = 3; int y = 8; int z = 0; z = syscall(SYS_my_call, x, y); printf("%i + %i = %i\n", x, y, z); return 0; } But it prints: 3 + 8 = -1 Can you give me some idea what I did wrong and what I should do? Also, can you tell me how to use the SYSCALL macro because I am not familiar with macros at all? Thanks in advance. Thanks. Ray, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 10:20:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id B2EF337B4E5; Mon, 6 Nov 2000 10:19:54 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.0/8.11.0) id eA6IJNl33880; Mon, 6 Nov 2000 20:19:23 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200011061819.eA6IJNl33880@zibbi.icomtek.csir.co.za> Subject: Re: dhcp boot was: Re: diskless workstation In-Reply-To: <200011051108.aa63419@salmon.maths.tcd.ie> from Ian Dowse at "Nov 5, 2000 11:08:38 am" To: iedowse@maths.tcd.ie (Ian Dowse) Date: Mon, 6 Nov 2000 20:19:23 +0200 (SAT) Cc: ambrisko@whistle.com (Doug Ambrisko), jhay@icomtek.csir.co.za (John Hay), msmith@FreeBSD.ORG (Mike Smith), danny@cs.huji.ac.il (Danny Braniss), freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200011042037.MAA63521@whistle.com>, Doug Ambrisko writes: > >| to the kernel's output. I had a look at the pxe code in > >| /sys/boot/i386/libi386/pxe.c where pxeboot is built from and in > >| /sys/i386/i386/autoconf.c which is the kernel side and it looks like > >| they don't do anything about swap. There is a /* XXX set up swap? */ > >| placeholder though. :-) > > > >Yep looks like you're right, I just tried it on 4.2-BETA it worked in > >4.1.1. Swap is now broken ... sigh this is going to be a problem. I > >guess the only thing you might be able to do in the interim is to do a > >vnconfig of a file and then mount that as swap. I think the vnconfig > >man pages describes this. Hopefully it works over NFS. > > The diskless setup we use here is based on a compiled-in MFS root > rather than an NFS root, so we couldn't use the bootp code to enable > NFS swap. Our solution was a modification to swapon() to enable > direct swapping to NFS regular files. > > This results in the same swaponvp() call that the bootp code would > use (at the time we implemented this, swapping over NFS via vnconfig > was extremely unreliable; I think things are much better now). Thanks for the patch. I was able to make a swapfile with vnconfig on -stable, but on -current I just get a device not configured error. Your patch work just fine on -current. John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 10:36:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whalers.digisle.com (whalers.digisle.com [167.216.128.32]) by hub.freebsd.org (Postfix) with ESMTP id 2618C37B479; Mon, 6 Nov 2000 10:36:35 -0800 (PST) Received: from guinness.digisle.net (guinness.digisle.net [167.216.152.33]) by whalers.digisle.com (8.9.3/8.9.3/mx) with ESMTP id SAA18176; Mon, 6 Nov 2000 18:37:33 GMT Received: from digisle.com (comanche.digisle.com [206.220.227.145]) by guinness.digisle.net (8.9.3/8.9.3/digisle) with ESMTP id SAA05764; Mon, 6 Nov 2000 18:36:33 GMT Message-ID: <3A06FA30.CF5F720F@digisle.com> Date: Mon, 06 Nov 2000 10:36:32 -0800 From: Maksim Yevmenkin Organization: Digital Island X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Harti Brandt Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: [PATCH] Re: if_tap and devfs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, > I recently moved to using devfs and now if_tap seems unusable. Although > the module is loaded, it doesn't show up in /dev or as an interface. > >From a quick comparison with if_tun it seems that this is 'expected' > behaviour although I'm not a specialist with devfs. Is this so? If yes, > is there somebody working to make if_tap devfs-ready? Or I'm doing > something wrong? please try the following patch. it is not tested, sorry i dont have FreeBSD box available right now :( please let me know the results. thanks, emax ---- *** if_tap.c.orig Mon Nov 6 09:24:08 2000 --- if_tap.c Mon Nov 6 10:26:35 2000 *************** *** 79,84 **** --- 79,85 ---- static int tapmodevent __P((module_t, int, void *)); /* device */ + static void tapclone __P((void *, char *, int, dev_t *)); static void tapcreate __P((dev_t)); /* network interface */ *************** *** 131,157 **** int type; void *data; { ! static int attached = 0; ! struct ifnet *ifp = NULL; ! int unit, s; switch (type) { case MOD_LOAD: if (attached) return (EEXIST); cdevsw_add(&tap_cdevsw); attached = 1; break; ! case MOD_UNLOAD: if (taprefcnt > 0) return (EBUSY); cdevsw_remove(&tap_cdevsw); unit = 0; while (unit <= taplastunit) { s = splimp(); TAILQ_FOREACH(ifp, &ifnet, if_link) if ((strcmp(ifp->if_name, TAP) == 0) || --- 132,164 ---- int type; void *data; { ! static int attached = 0; ! static eventhandler_tag eh_tag = NULL; switch (type) { case MOD_LOAD: if (attached) return (EEXIST); + eh_tag = EVENTHANDLER_REGISTER(dev_clone, tapclone, 0, 1000); cdevsw_add(&tap_cdevsw); attached = 1; break; ! case MOD_UNLOAD: { ! int unit; ! if (taprefcnt > 0) return (EBUSY); + EVENTHANDLER_DEREGISTER(dev_clone, eh_tag); cdevsw_remove(&tap_cdevsw); unit = 0; while (unit <= taplastunit) { + int s; + struct ifnet *ifp = NULL; + s = splimp(); TAILQ_FOREACH(ifp, &ifnet, if_link) if ((strcmp(ifp->if_name, TAP) == 0) || *************** *** 179,185 **** } attached = 0; ! break; default: return (EOPNOTSUPP); --- 186,192 ---- } attached = 0; ! } break; default: return (EOPNOTSUPP); *************** *** 187,192 **** --- 194,234 ---- return (0); } /* tapmodevent */ + + + /* + * DEVFS handler + * + * We need to support two kind of devices - tap and vmnet + */ + static void + tapclone(arg, name, namlen, dev) + void *arg; + char *name; + int namelen; + dev_t *dev; + { + int unit, minor; + char *device_name = NULL; + + if (*dev != NODEV) + return; + + device_name = TAP; + if (dev_stdclone(name, NULL, device_name, &unit) != 1) { + device_name = VMNET; + + if (dev_stdclone(name, NULL, device_name, &unit) != 1) + return; + + minor = (unit | VMNET_DEV_MASK); + } + else + minor = unit; + + *dev = make_dev(&tap_cdevsw, minor, UID_ROOT, GID_WHEEL, 0600, "%s%d", + device_name, unit); + } /* tapclone */ /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 10:39:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from access.sanet.ge (access.sanet.ge [212.72.130.51]) by hub.freebsd.org (Postfix) with ESMTP id 9831137B479 for ; Mon, 6 Nov 2000 10:39:23 -0800 (PST) Received: from ppp76-tc3.sanet.ge (ppp76-tc3.sanet.ge [212.72.129.76]) by access.sanet.ge (8.9.3/8.9.3) with ESMTP id WAA85406 for ; Mon, 6 Nov 2000 22:38:42 +0500 (GET) Date: Mon, 6 Nov 2000 22:41:46 +0400 From: Zurab Chaya X-Mailer: The Bat! (v1.46d) Educational X-Priority: 3 (Normal) Message-ID: <1624384220.20001106224146@access.sanet.ge> To: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 13:21:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id DC07237B479 for ; Mon, 6 Nov 2000 13:21:20 -0800 (PST) Received: from portonovo-52.budapest.interware.hu ([195.70.60.116] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13sthT-00019l-00; Mon, 06 Nov 2000 22:21:08 +0100 Message-ID: <3A071A27.894ED4FC@elischer.org> Date: Mon, 06 Nov 2000 12:52:55 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Riaz Khan Cc: hackers@FreeBSD.org Subject: Re: Streams support. References: <3A02B286.38CDA896@hclt.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Riaz Khan wrote: > > Hello, > I just need a clarification regarding streams support. Does FreeBSD > provides support for streams programming. - i don't think so. > I need info regarding how the network stack is implemented in FreeBSD. > hope its very similar to linux architecture. > > If possible please do specify probable links > which speak about internals of networking stack > in FreeBSD. there is some streams supprt as part of the SYSV emulation. I have no idea how complete it is or if it can be used natively. > > clarify. > riaz. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 13:55:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurum.springer.cx (cgmd77002.chello.nl [212.83.77.2]) by hub.freebsd.org (Postfix) with ESMTP id 74D4D37B4D7 for ; Mon, 6 Nov 2000 13:55:49 -0800 (PST) Received: by aurum.springer.cx (8.9.3/8.9.3) id XAA36583; Mon, 6 Nov 2000 23:54:57 GMT (envelope-from rink) From: Rink Springer VII To: Warner Losh Subject: My driver source. Date: Mon, 6 Nov 2000 23:53:20 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: Sergey Babkin , hackers@FreeBSD.ORG References: <00110601535400.09767@aurum.springer.cx> <200011052247.PAA04001@harmony.village.org> <200011052359.QAA04971@harmony.village.org> In-Reply-To: <200011052359.QAA04971@harmony.village.org> MIME-Version: 1.0 Message-Id: <00110623545600.36558@aurum.springer.cx> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, My driver's source can be grabbed from: http://www.rink.springer.cx/driver/if_dl.c and http://www.rink.springer.cx/driver/if_dlvar.h Please help me... it crashes for some reason. Thanks! --Rink To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 14: 7:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 420AE37B4C5 for ; Mon, 6 Nov 2000 14:07:28 -0800 (PST) Received: (from newton@localhost) by gizmo.internode.com.au (8.11.0/8.9.3) id eA6M2SY10686; Tue, 7 Nov 2000 08:32:28 +1030 (CST) (envelope-from newton) Date: Tue, 7 Nov 2000 08:32:28 +1030 From: Mark Newton To: Julian Elischer Cc: Riaz Khan , hackers@FreeBSD.ORG Subject: Re: Streams support. Message-ID: <20001107083228.C8866@internode.com.au> References: <3A02B286.38CDA896@hclt.com> <3A071A27.894ED4FC@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <3A071A27.894ED4FC@elischer.org> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 06, 2000 at 12:52:55PM -0800, Julian Elischer wrote: > Riaz Khan wrote: > > I just need a clarification regarding streams support. Does FreeBSD > > provides support for streams programming. - i don't think so. > > I need info regarding how the network stack is implemented in FreeBSD. > > hope its very similar to linux architecture. > > there is some streams supprt as part of the SYSV emulation. > I have no idea how complete it is or if it can be > used natively. Don't even think about it :-) It's an evil hack. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 14:44: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (mail.dobox.com [208.187.122.44]) by hub.freebsd.org (Postfix) with ESMTP id E55ED37B479; Mon, 6 Nov 2000 14:43:59 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13sv07-0000Bo-00; Mon, 06 Nov 2000 15:44:27 -0700 Message-ID: <3A07344B.95C98FD5@softweyr.com> Date: Mon, 06 Nov 2000 15:44:27 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: mb@imp.ch Cc: hackers@freebsd.org, stable@freebsd.org Subject: StarOffice 5.2 port for FreeBSD. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been trying to install the StarOffice port for FreeBSD. It appears the checksum for the StarOffice binary from Sun has changed but the port has not. It also appears to have tripped a bug (or limitation) in ld.so. This system is a recent -STABLE: FreeBSD star 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Wed Oct 25 15:55:27 MDT 2000 rootb@star:/usr/obj/usr/src/sys/STAR i386 'make' in the staroffice port yeilds: >> Checksum mismatch for staroffice52/so-5_2-ga-bin-linux-en.bin. Running make with NO_CHECKSUM=yes yeilds: ===> staroffice-4.2 depends on file: /compat/linux/lib/libc.so.6 - found BUG IN DYNAMIC LINKER ld.so: dynamic-link.h: 57: elft_get_dynamic_info: Assertion `! "bad dynamic tag"' failed! *** Error code 127 Has anyone else seen this, or a similar problem? Do I just need to cvsup the system again? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 14:51: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gelrevision.nl (mail.gelrevision.nl [195.86.58.10]) by hub.freebsd.org (Postfix) with ESMTP id BC8D637B479; Mon, 6 Nov 2000 14:50:58 -0800 (PST) Received: from localhost [195.86.231.176] by mail.gelrevision.nl with ESMTP (SMTPD32-6.00) id A558114F01C6; Mon, 06 Nov 2000 23:48:56 +0100 Date: Mon, 6 Nov 2000 23:49:58 +0100 (CET) From: Maarten van Schie To: Wes Peters Cc: mb@imp.ch, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: StarOffice 5.2 port for FreeBSD. In-Reply-To: <3A07344B.95C98FD5@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I installed SO it didn't spitt out any complaints about the checksum. Did you install the Linux Emulator from /usr/ports/emulators/linux_base ? You need it since the SO port uses the Linux version. Maarten. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 15: 3: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from neimail.networkengines.com (unknown [64.55.6.7]) by hub.freebsd.org (Postfix) with ESMTP id 4793137B4F9 for ; Mon, 6 Nov 2000 15:02:59 -0800 (PST) Received: by neimail.networkengines.com with Internet Mail Service (5.5.2650.21) id ; Mon, 6 Nov 2000 18:00:05 -0500 Message-ID: <8D18C4F9CBA1D311900F00A0C990C97F67CB44@neimail.networkengines.com> From: Andrew Sporner To: "'freebsd-hackers@freebsd.org'" Subject: High-availability failover software available. Date: Mon, 6 Nov 2000 17:59:57 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Please allow me to introduce myself. I am Andrew Sporner and I have authored a H/A Failover system that happens to work with BSD. I would like to contribute this to the FreeBSD project or at a minimum make it available to those who want it. What it includes is: - Multi-path heartbeat based node failure detection. - Application failover. - Applications can be assigned to two or many nodes in the cluster. If the current node that the application runs on fails, the next successor picks up the application. - Drag&Drop administration interface (X-11 tcl/tk based The current state is alpha and is being tested by several people now. Beta will occur in about a week or so. The current source is located at http://www.sporner.com/bsdclusters Please let me know what I should do... Thanks very much in advance. Respectfully, Andy Sporner PS. I am not sure how many of you were at BSDCon 2000, but that was some very good talks--especially the BIO talk. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 15:12:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id D4E9637B479 for ; Mon, 6 Nov 2000 15:12:48 -0800 (PST) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id RAA88126; Mon, 6 Nov 2000 17:12:43 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Mon, 6 Nov 2000 17:12:43 -0600 (CST) From: David Scheidt To: Andrew Sporner Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: High-availability failover software available. In-Reply-To: <8D18C4F9CBA1D311900F00A0C990C97F67CB44@neimail.networkengines.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Nov 2000, Andrew Sporner wrote: :Hi, : :Please allow me to introduce myself. I am Andrew Sporner and I have :authored :a H/A Failover system that happens to work with BSD. I would like to Very cool! :The current source is located at http://www.sporner.com/bsdclusters Your webpages seem to be b0rked. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 15:28:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from neimail.networkengines.com (unknown [64.55.6.7]) by hub.freebsd.org (Postfix) with ESMTP id CCF6137B4CF for ; Mon, 6 Nov 2000 15:28:52 -0800 (PST) Received: by neimail.networkengines.com with Internet Mail Service (5.5.2650.21) id ; Mon, 6 Nov 2000 18:26:05 -0500 Message-ID: <8D18C4F9CBA1D311900F00A0C990C97F67CB46@neimail.networkengines.com> From: Andrew Sporner To: 'David Scheidt' , Andrew Sporner Cc: "'freebsd-hackers@freebsd.org'" Subject: RE: High-availability failover software available. Date: Mon, 6 Nov 2000 18:26:04 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Here is the direct link http://www.sporner.com/bsdclusters/download Remember! this is alpha-ware :-) I will be doing some more fixes/updates this evening... Look for fresh stuff tommorrow morning... Thanks in advance for all your support! Andy -----Original Message----- From: David Scheidt [mailto:dscheidt@enteract.com] Sent: Monday, November 06, 2000 6:13 PM To: Andrew Sporner Cc: 'freebsd-hackers@freebsd.org' Subject: Re: High-availability failover software available. On Mon, 6 Nov 2000, Andrew Sporner wrote: :Hi, : :Please allow me to introduce myself. I am Andrew Sporner and I have :authored :a H/A Failover system that happens to work with BSD. I would like to Very cool! :The current source is located at http://www.sporner.com/bsdclusters Your webpages seem to be b0rked. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 18:17:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.getrelevant.com (mail.getrelevant.com [63.211.149.12]) by hub.freebsd.org (Postfix) with ESMTP id 3CB0237B4C5 for ; Mon, 6 Nov 2000 18:17:29 -0800 (PST) Received: from khmere.com ([63.211.149.44]) by mail.getrelevant.com (Lotus Domino Release 5.0.5) with ESMTP id 2000110618151121:207819 ; Mon, 6 Nov 2000 18:15:11 -0800 Message-ID: <3A076622.A12C5979@khmere.com> Date: Mon, 06 Nov 2000 18:17:06 -0800 From: Nathan Boeger Organization: Getrelevant X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-hackers@FreeBSD.ORG" Subject: Digi Xem help! X-MIMETrack: Itemize by SMTP Server on notes/GetRelevant(Release 5.0.5 |September 22, 2000) at 11/06/2000 06:15:11 PM, Serialize by Router on notes/GetRelevant(Release 5.0.5 |September 22, 2000) at 11/06/2000 06:15:14 PM, Serialize complete at 11/06/2000 06:15:14 PM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry if this is the wrong list !! Anyway I have a Digi / Xem eisa adapter on 4.1-RELEASE. I have made the kernel and it see's the card. I have also remade the /dev/ttyD* entries. Problem, when I try to access any of the ports I get : cu: open (/dev/ttyD00): Device not configured cu: /dev/ttyD00: Line in use Here is the boot output: dgm0: PC/Xem (type 245) dgm0 at port 0x104-0x107 iomem 0xd0000-0xd7fff on isa0 dgm0: DigiBIOS loaded, initializing, DigiBIOS running dgm0: FEP/OS loaded, initializing, FEP/OS running dgm0: 16 ports dgm0: driver is using old-style compatability shims Now what do I have to do ? I have played with permissions (cu is setuid, setgid) I have also tried to use stty and comcontrol but they say the same. Any help would be great !! thank you nathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 19: 0:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lavender.sanpei.org (lavender.yy.ics.keio.ac.jp [131.113.47.22]) by hub.freebsd.org (Postfix) with ESMTP id 1DED737B4C5 for ; Mon, 6 Nov 2000 19:00:32 -0800 (PST) Received: (from sanpei@localhost) by lavender.sanpei.org (8.11.0/3.7W) id eA72xmb04618; Tue, 7 Nov 2000 11:59:48 +0900 (JST) Message-Id: <200011070259.eA72xmb04618@lavender.sanpei.org> To: freebsd-hackers@FreeBSD.ORG From: sanpei@FreeBSD.org Subject: ftp.FreeBSD.org/pub/FreeBSD/branches/4.0-stable was not updated from 2000/April/25. X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 07 Nov 2000 11:59:48 +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. In ftp.FreeBSD.org, below files were not updated from 2000/April/25.... Why..... ftp://ftp.FreeBSD.org/pub/FreeBSD/branches/4.0-stable/ I hope to sync latest 4-stable FreeBSD tree. ----- ftp connection to ftp.FreeBSD.org ---- > cd /pub/FreeBSD/branches/4.0-stable/src > dir total 102 -rw-rw-r-- 1 2035 207 4735 Sep 5 1999 COPYRIGHT drwxrwxr-x 2 2035 207 512 Apr 24 2000 CVS -rw-rw-r-- 1 2035 207 7205 Feb 24 2000 Makefile -rw-rw-r-- 1 2035 207 23892 Mar 9 2000 Makefile.inc1 -rw-rw-r-- 1 2035 207 9761 Aug 28 1999 Makefile.upgrade -rw-rw-r-- 1 2035 207 2351 Aug 28 1999 README -rw-rw-r-- 1 2035 207 24016 Mar 9 2000 UPDATING drwxrwxr-x 33 2035 207 512 Apr 24 2000 bin drwxrwxr-x 39 2035 207 1024 Apr 24 2000 contrib ~~~~~~~~~~~~ <> --------------------------------------------- Cheers. --- MIHIRA, Sanpei Yoshiro Yokohama, Japan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 19:18:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id ADD0C37B4C5; Mon, 6 Nov 2000 19:18:14 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eA73JL206643; Mon, 6 Nov 2000 19:19:21 -0800 (PST) (envelope-from kris) Date: Mon, 6 Nov 2000 19:19:21 -0800 From: Kris Kennaway To: sanpei@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ftp.FreeBSD.org/pub/FreeBSD/branches/4.0-stable was not updated from 2000/April/25. Message-ID: <20001106191921.B6581@citusc17.usc.edu> References: <200011070259.eA72xmb04618@lavender.sanpei.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="pvezYHf7grwyp3Bc" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011070259.eA72xmb04618@lavender.sanpei.org>; from sanpei@FreeBSD.ORG on Tue, Nov 07, 2000 at 11:59:48AM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --pvezYHf7grwyp3Bc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 07, 2000 at 11:59:48AM +0900, sanpei@FreeBSD.ORG wrote: > Hi. >=20 > In ftp.FreeBSD.org, below files were not updated from > 2000/April/25.... Why..... >=20 > ftp://ftp.FreeBSD.org/pub/FreeBSD/branches/4.0-stable/ >=20 > I hope to sync latest 4-stable FreeBSD tree. Use cvsup, it's much more efficient at syncing, since the majority of the code does not change from one release to another. Kris --pvezYHf7grwyp3Bc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoHdLgACgkQWry0BWjoQKVwUgCfbQwVlO/0jQ+C71REZzJV1O0w n4kAoMtH9jGM3X5o/DHPORgYaKT7brQ6 =fZzv -----END PGP SIGNATURE----- --pvezYHf7grwyp3Bc-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 19:22:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.khmere.com (sdsl-216-36-70-194.dsl.sjc.megapath.net [216.36.70.194]) by hub.freebsd.org (Postfix) with ESMTP id EABD337B4CF for ; Mon, 6 Nov 2000 19:22:46 -0800 (PST) Received: from khmere.com (ns2.khmere.com [216.36.70.196]) by ns1.khmere.com (8.11.0/8.8.7) with ESMTP id eA73MSO18559; Mon, 6 Nov 2000 19:22:29 -0800 (PST) Message-ID: <3A07757D.2F865232@khmere.com> Date: Mon, 06 Nov 2000 19:22:37 -0800 From: nathan@khmere.com X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.17 i586) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Sporner Cc: "'David Scheidt'" , "'freebsd-hackers@freebsd.org'" Subject: Re: High-availability failover software available. References: <8D18C4F9CBA1D311900F00A0C990C97F67CB46@neimail.networkengines.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Sporner wrote: > Hi, > > Here is the direct link http://www.sporner.com/bsdclusters/download > > Remember! this is alpha-ware :-) > > I will be doing some more fixes/updates this evening... Look for fresh > stuff tommorrow morning... > > Thanks in advance for all your support! > > Andy > > -----Original Message----- > From: David Scheidt [mailto:dscheidt@enteract.com] > Sent: Monday, November 06, 2000 6:13 PM > To: Andrew Sporner > Cc: 'freebsd-hackers@freebsd.org' > Subject: Re: High-availability failover software available. > > On Mon, 6 Nov 2000, Andrew Sporner wrote: > > :Hi, > : > :Please allow me to introduce myself. I am Andrew Sporner and I have > :authored > :a H/A Failover system that happens to work with BSD. I would like to > > Very cool! > > :The current source is located at http://www.sporner.com/bsdclusters > > Your webpages seem to be b0rked. > > David > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message I have been doing something very simular at work. I was wondering if you need some help ? nathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 19:24:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lavender.sanpei.org (lavender.yy.ics.keio.ac.jp [131.113.47.22]) by hub.freebsd.org (Postfix) with ESMTP id 1833E37B4C5; Mon, 6 Nov 2000 19:24:47 -0800 (PST) Received: (from sanpei@localhost) by lavender.sanpei.org (8.11.0/3.7W) id eA73OGM04758; Tue, 7 Nov 2000 12:24:16 +0900 (JST) Message-Id: <200011070324.eA73OGM04758@lavender.sanpei.org> To: kris@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG From: sanpei@FreeBSD.ORG Subject: Re: ftp.FreeBSD.org/pub/FreeBSD/branches/4.0-stable was not updated from 2000/April/25. In-Reply-To: Your message of "Mon, 6 Nov 2000 19:19:21 -0800" References: <20001106191921.B6581@citusc17.usc.edu> X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 07 Nov 2000 12:24:15 +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I know cvsup and personally I use cvsup. But that direcotry would confused novice user. If no one update these directory, I hope to remove that ``branches/4.0-stable'' directory from ftp.FreeBSD.org. >On Tue, Nov 07, 2000 at 11:59:48AM +0900, sanpei@FreeBSD.ORG wrote: >> Hi. >> >> In ftp.FreeBSD.org, below files were not updated from >> 2000/April/25.... Why..... >> >> ftp://ftp.FreeBSD.org/pub/FreeBSD/branches/4.0-stable/ >> >> I hope to sync latest 4-stable FreeBSD tree. > >Use cvsup, it's much more efficient at syncing, since the majority of >the code does not change from one release to another. Cheers. --- MIHIRA, Sanpei Yoshiro Yokohama, Japan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 21:44:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id E565537B479 for ; Mon, 6 Nov 2000 21:44:14 -0800 (PST) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13t1YL-0000YR-00; Tue, 07 Nov 2000 05:44:13 +0000 Date: Tue, 7 Nov 2000 05:44:13 +0000 To: hackers@freebsd.org Subject: "iowait" CPU state Message-ID: <20001107054413.A1983@firedrake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i From: void Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been using Solaris a lot lately, and I've noticed that in e.g. top's output, it has a distinct CPU state called "iowait", which seems to be a pretty good indicator of how I/O-bound a system is. Is there any reason that FreeBSD doesn't have such a state? "iostat" also seems a lot less informative than Sun's. What should I be using to measure I/O utilization on FreeBSD? -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 22:45:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 55CEF37B4C5 for ; Mon, 6 Nov 2000 22:45:34 -0800 (PST) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id PAA55278; Tue, 7 Nov 2000 15:44:35 +0900 (JST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Message-Id: <200011070644.PAA55278@shidahara1.planet.sci.kobe-u.ac.jp> To: Rink Springer VII Cc: hackers@FreeBSD.ORG Subject: Re: My driver source. In-reply-to: Your message of "Mon, 06 Nov 2000 23:53:20 GMT." <00110623545600.36558@aurum.springer.cx> Date: Tue, 07 Nov 2000 15:44:34 +0900 From: Takanori Watanabe Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <00110623545600.36558@aurum.springer.cx>, Rink Springer VII $B$5$s$$$o(B $B$/(B: >Hi guys, > >My driver's source can be grabbed from: > >http://www.rink.springer.cx/driver/if_dl.c >and >http://www.rink.springer.cx/driver/if_dlvar.h > >Please help me... it crashes for some reason. I don't know why it crashes.But I suggest you to use ppbus code. ppbus provides low level register access ,like command register on printer port. See sys/dev/ppbus/ppbio.h . Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 23:22:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 7155A37B4C5; Mon, 6 Nov 2000 23:22:25 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id A5F7F5730D; Tue, 7 Nov 2000 01:22:26 -0600 (CST) Date: Tue, 7 Nov 2000 01:22:26 -0600 From: "Michael C . Wu" To: Andrew Sporner Cc: freebsd-net@freebsd.org, "'freebsd-hackers@freebsd.org'" Subject: Re: High-availability failover software available. Message-ID: <20001107012226.A61671@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , Andrew Sporner , freebsd-net@freebsd.org, "'freebsd-hackers@freebsd.org'" References: <8D18C4F9CBA1D311900F00A0C990C97F67CB44@neimail.networkengines.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8D18C4F9CBA1D311900F00A0C990C97F67CB44@neimail.networkengines.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >; from andy.sporner@networkengines.com on Mon, Nov 06, 2000 at 05:59:57PM -0500 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 [Moving to -net, please remove -hackers cc when replying] On Mon, Nov 06, 2000 at 05:59:57PM -0500, Andrew Sporner scribbled: | Hi, | | Please allow me to introduce myself. I am Andrew Sporner and I have Hi, :) | a H/A Failover system that happens to work with BSD. I would like to | contribute | this to the FreeBSD project or at a minimum make it available to those who | What it includes is: | - Multi-path heartbeat based node failure detection. How do you determine that a machine/service is "failing"? Have you considered that the distributed nodes might be very far away from each other, even across the globe? Lag time can lead to daemon falsely thinking that a node is down. Example: condition, Cross pacific link being slow Node A,B in Lake Tahoe, USA. Node C,D in Maldive Islands, South Pacific Node C and D have gigabit LAN between each other, and so does A and B Lake Tahoe Pacific Ocean Maldive Islands (A+B) <-------connected via T1-------> (C+D) Upon lag and/or service requests to (C+D) in India, while the T1 is slow, (C+D) should take over. Upon service request in America, B is down, C+D still alive, A is under high load, no matter how light the load of C+D, the service request should be routed to A. bla bla bla..... (I want to buy houses in these two places one day... 8-P ) Reading your code, I don't think broadcasting over all interfaces is a good idea. A safer way would be requiring two physical interfaces on all nodes, building two seperate physical networks. The nodes communicate information on one network, and do the actual "work" on the other, more powerful, network. The daemons on the nodes should broadcast over these two interfaces. In addition, a comparison between the connectivity of the two physical networks can provide lots of valuable info. There is another bad thing about broadcasting over all interfaces, several types of attacks can be made: A. spoofing node packets, making controlling daemon believe some machinese are down. B. network internal information acquired by people that shouldn't have them. A great thing to do with this code would be using kqueue. | - Application failover. | - Applications can be assigned to two or many nodes in the | cluster. If the current node that the application runs on | fails, the next successor picks up the application. I think there should be a daemon that "routes" service queries, say a http request, to different nodes as the requests come in. | - Drag&Drop administration interface (X-11 tcl/tk based I think this should also include a console-type controller. Real-life work involves admining remotely, and GUI apps are not that great remotely. | The current state is alpha and is being tested by several people now. Beta | The current source is located at http://www.sporner.com/bsdclusters Please document what you have done, so we can learn more about the engineering thinking behind your implementation. | Please let me know what I should do... Will this be BSDL or will it be another license? Also, please include man pages. | Andy Sporner | PS. I am not sure how many of you were at BSDCon 2000, but that was some | very good talks--especially the BIO talk. I think we missed a great chance to talk to each other, since my research interest is the same field as your project. Or we may have met, I'm the Chinese guy that had the shortest hair. P.S. Please keep lines shorter than 80 characters. :) -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 6 23:57:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from femail8.sdc1.sfba.home.com (femail8.sdc1.sfba.home.com [24.0.95.88]) by hub.freebsd.org (Postfix) with ESMTP id 054DA37B4D7 for ; Mon, 6 Nov 2000 23:57:31 -0800 (PST) Received: from beastie.localdomain ([24.19.158.41]) by femail8.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20001107075730.FLZF2160.femail8.sdc1.sfba.home.com@beastie.localdomain>; Mon, 6 Nov 2000 23:57:30 -0800 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id AAA93675; Tue, 7 Nov 2000 00:00:22 -0800 (PST) (envelope-from brian) Date: Tue, 7 Nov 2000 00:00:22 -0800 From: "Brian O'Shea" To: void Cc: hackers@FreeBSD.ORG Subject: Re: "iowait" CPU state Message-ID: <20001107000022.M622@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: void , hackers@FreeBSD.ORG References: <20001107054413.A1983@firedrake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20001107054413.A1983@firedrake.org>; from void on Tue, Nov 07, 2000 at 05:44:13AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 07, 2000 at 05:44:13AM +0000, void wrote: > I've been using Solaris a lot lately, and I've noticed that in e.g. > top's output, it has a distinct CPU state called "iowait", which seems > to be a pretty good indicator of how I/O-bound a system is. Is there > any reason that FreeBSD doesn't have such a state? "iostat" also seems > a lot less informative than Sun's. What should I be using to measure > I/O utilization on FreeBSD? From the iostat(8) man page: SEE ALSO fstat(1), netstat(1), nfsstat(1), ps(1), systat(1), pstat(8), vmstat(8) What information are you looking for specifically? Have a look at systat(1). It presents the activity on your system nicely, breaking it down into several descriptive categories which are documented in the man page. Try this: $ systat -io Hope that helps, -brian -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 0:15:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 749B137B479 for ; Tue, 7 Nov 2000 00:15:19 -0800 (PST) Received: from FreeBSD.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id AAA03020; Tue, 7 Nov 2000 00:15:14 -0800 (PST) (envelope-from DougB@FreeBSD.org) Message-ID: <3A07BA12.A3CD8C88@FreeBSD.org> Date: Tue, 07 Nov 2000 00:15:14 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Peter Pentchev Cc: hackers@FreeBSD.org Subject: Re: New mergemaster behavior - comparing CVS $Id too References: <20001106134437.A556@ringworld.oblivion.bg> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Pentchev wrote: > > Is there a way to make mergemaster revert to its old behavior - only > comparing $FreeBSD tags on files which have those? Of course there is a way, the question is how likely it is to happen. :) You've stated the solution, just take the local tags out for now. They don't tell you anything that 'cvs status' doesn't already tell you. I struggled with this change, because I myself use a CVS repo to store local mods to config files. One of the goals of the current round of mergemaster mods is to make the thing more palatable across *BSD platforms. There were already too many if it's one $Id tag or another definitions in the old code, and it was going to get bigger. If there is a great hue and cry over this problem, I'll look at changing it back, but frankly my inclination is that using 'ident' is going to be the best solution long term. Doug -- Life is an essay test. Long form. Spelling counts. Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 0:31: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.oblivion.bg (pool153-tch-1.Sofia.0rbitel.net [212.95.170.153]) by hub.freebsd.org (Postfix) with SMTP id 5955437B4D7 for ; Tue, 7 Nov 2000 00:30:59 -0800 (PST) Received: (qmail 2090 invoked by uid 1000); 7 Nov 2000 08:30:48 -0000 Date: Tue, 7 Nov 2000 10:30:48 +0200 From: Peter Pentchev To: Doug Barton Cc: hackers@FreeBSD.org Subject: Re: New mergemaster behavior - comparing CVS $Id too Message-ID: <20001107103048.B314@ringworld.oblivion.bg> Mail-Followup-To: Doug Barton , hackers@FreeBSD.org References: <20001106134437.A556@ringworld.oblivion.bg> <3A07BA12.A3CD8C88@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A07BA12.A3CD8C88@FreeBSD.org>; from DougB@FreeBSD.org on Tue, Nov 07, 2000 at 12:15:14AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 07, 2000 at 12:15:14AM -0800, Doug Barton wrote: > Peter Pentchev wrote: > > > > Is there a way to make mergemaster revert to its old behavior - only > > comparing $FreeBSD tags on files which have those? > > Of course there is a way, the question is how likely it is to happen. > :) You've stated the solution, just take the local tags out for now. > They don't tell you anything that 'cvs status' doesn't already tell you. Ahhhhhh... well I guess I should read my manuals a bit more :) I *thought* I'd read the parts about tags and such, and yet I've managed to miss all the info about 'cvs status'. But hey, it isn't included in the 'CVS commands' section :P (although yes, it is in the 'cvs --help-commands' output..) > I struggled with this change, because I myself use a CVS repo to store > local mods to config files. One of the goals of the current round of > mergemaster mods is to make the thing more palatable across *BSD > platforms. There were already too many if it's one $Id tag or another > definitions in the old code, and it was going to get bigger. If there is > a great hue and cry over this problem, I'll look at changing it back, > but frankly my inclination is that using 'ident' is going to be the best > solution long term. Hmmm alright, I'll buy the *BSD compatibility one. Thanks for the answer :) G'luck, Peter -- Thit sentence is not self-referential because "thit" is not a word. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 1:58:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from memogw1.sbb.ch (memogw1.sbb.ch [147.78.29.212]) by hub.freebsd.org (Postfix) with ESMTP id 1BF3237B4C5 for ; Tue, 7 Nov 2000 01:58:44 -0800 (PST) Received: from aeschbacher.com (I28405.sbb.ch [147.78.31.196]) by memogw1.sbb.ch (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with ESMTP id KAA02823 for ; Tue, 07 Nov 2000 10:58:28 +0100 Message-ID: <3A07D2F1.E169FC96@aeschbacher.com> Date: Tue, 07 Nov 2000 11:01:21 +0100 From: Stefan Aeschbacher X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: hardware problem? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I have a machine which behaves very weird. It runs 4.0-stable built in June. Recently i made a cvsupdate followed by a buildworld. Both worked. Due to lack of time (and access to the machine for installing in single user mode), I did not install anything. Today I tried to compile something and the compiler crashes with the following message: cc: Internal compiler error: program ld got fatal signal 11 this error happens during each compilation but it does not happen at the same location in the source code each run. furthermore, some daemons tend to segfault extremely often. I had the same problems some time ago and thought it is caused by kernel and world being out of sinc (I was not very careful when updating at this time) but this should not be the case now. Any propositions on how to debug this thing? Could it be a hardware problem? Stefan Aeschbacher To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 2: 5:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gray.westgate.gr (gray.westgate.gr [212.205.119.66]) by hub.freebsd.org (Postfix) with ESMTP id F058337B4CF for ; Tue, 7 Nov 2000 02:05:51 -0800 (PST) Received: (from charon@localhost) by gray.westgate.gr (8.11.1/8.11.1) id eA7A5B198116 for hackers@freebsd.org; Tue, 7 Nov 2000 12:05:11 +0200 (EET) Date: Tue, 7 Nov 2000 12:05:11 +0200 From: Giorgos Keramidas To: hackers@freebsd.org Subject: umask(2) and -Wconversion Message-ID: <20001107120511.A98074@gray.westgate.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 3A 75 52 EB F1 58 56 0D - C5 B8 21 B6 1B 5E 4A C2 X-URL: http://students.ceid.upatras.gr/~keramida/index.html Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While trying to compile libskey with various warnings enabled, I discovered the following funny thing about -Wconversion and umask(2), which caused libskey to fail to compile, because it compiles by default with -Werror which makes every warning fatal. I found that the warning is caused when a program that calls umask(2) is compiled with -Wconversion. The info page of gcc says about -Wconversion: `-Wconversion' Warn if a prototype causes a type conversion that is different from what would happen to the same argument in the absence of a prototype. This includes conversions of fixed point to floating and vice versa, and conversions changing the width or signedness of a fixed point argument except when the same as the default promotion. Also, warn if a negative integer constant expression is implicitly converted to an unsigned type. For example, warn about the assignment `x = -1' if `x' is unsigned. But do not warn about explicit casts like `(unsigned) -1'. The following test program when compiled with -Wconversion shown below will always give a warning, even if I explicitly try to cast the argument of umask() to mode_t. 1 #include 2 #include 3 4 int main (void) 5 { 6 mode_t oldmask; 7 8 oldmask = umask(0); 9 printf("The umask has changed\n"); 10 umask(oldmask); 11 return 0; 12 } The output given when I compile this with -Wconversion is: gray-charon:/home/charon/test% gcc -Wconversion test.c -o test test.c: In function `main': test.c:8: warning: passing arg 1 of `umask' with different width due to prototype test.c:10: warning: passing arg 1 of `umask' with different width due to prototype The problem is that even if I change line 8 to read: 8 oldmask = umask((mode_t) 0); the warning is still there. Am I being a bit too strict with all these warnings here? If not, does anyone else have any idea why umask(2) will always cause such a warning, and how I can go about correcting it? Casting obviously fails, so something else needs to be done. -- Giorgos Keramidas, For my public pgp2 key: finger -l keramida@diogenis.ceid.upatras.gr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 2:17:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.oblivion.bg (pool153-tch-1.Sofia.0rbitel.net [212.95.170.153]) by hub.freebsd.org (Postfix) with SMTP id 9B83D37B4C5 for ; Tue, 7 Nov 2000 02:17:45 -0800 (PST) Received: (qmail 2489 invoked by uid 1000); 7 Nov 2000 10:17:34 -0000 Date: Tue, 7 Nov 2000 12:17:34 +0200 From: Peter Pentchev To: Giorgos Keramidas Cc: hackers@freebsd.org Subject: Re: umask(2) and -Wconversion Message-ID: <20001107121734.D314@ringworld.oblivion.bg> Mail-Followup-To: Giorgos Keramidas , hackers@freebsd.org References: <20001107120511.A98074@gray.westgate.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001107120511.A98074@gray.westgate.gr>; from keramida@ceid.upatras.gr on Tue, Nov 07, 2000 at 12:05:11PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In my experience, the problem is not only with umask(2) - GCC *is* a bit stubborn about -Wconversion; I wonder if this is really a GCC bug :( I'm having the same problems with many other functions when passing integer constants - even if I explicitly cast them to a long or unsigned long or plain unsigned int or whatever the particular function needs, GCC seems to ignore the cast and whines about the conversion nonetheless :( Can anybody else confirm this? I can't dig out a code snippet right now, but ISTR a recurring case of this when compiling with BDECFLAGS a program which includes ncurses.h, then passes integer constants to init_pair() or something similar. G'luck, Peter -- If there were no counterfactuals, this sentence would not have been paradoxical. On Tue, Nov 07, 2000 at 12:05:11PM +0200, Giorgos Keramidas wrote: > While trying to compile libskey with various warnings enabled, I > discovered the following funny thing about -Wconversion and umask(2), > which caused libskey to fail to compile, because it compiles by default > with -Werror which makes every warning fatal. > > I found that the warning is caused when a program that calls umask(2) is > compiled with -Wconversion. The info page of gcc says about -Wconversion: > > `-Wconversion' > Warn if a prototype causes a type conversion that is different > from what would happen to the same argument in the absence of a > prototype. This includes conversions of fixed point to floating > and vice versa, and conversions changing the width or signedness > of a fixed point argument except when the same as the default > promotion. > > Also, warn if a negative integer constant expression is implicitly > converted to an unsigned type. For example, warn about the > assignment `x = -1' if `x' is unsigned. But do not warn about > explicit casts like `(unsigned) -1'. > > The following test program when compiled with -Wconversion shown below > will always give a warning, even if I explicitly try to cast the > argument of umask() to mode_t. > > 1 #include > 2 #include > 3 > 4 int main (void) > 5 { > 6 mode_t oldmask; > 7 > 8 oldmask = umask(0); > 9 printf("The umask has changed\n"); > 10 umask(oldmask); > 11 return 0; > 12 } > > The output given when I compile this with -Wconversion is: > > gray-charon:/home/charon/test% gcc -Wconversion test.c -o test > test.c: In function `main': > test.c:8: warning: passing arg 1 of `umask' with different width due to prototype > test.c:10: warning: passing arg 1 of `umask' with different width due to prototype > > The problem is that even if I change line 8 to read: > > 8 oldmask = umask((mode_t) 0); > > the warning is still there. Am I being a bit too strict with all these > warnings here? If not, does anyone else have any idea why umask(2) will > always cause such a warning, and how I can go about correcting it? > Casting obviously fails, so something else needs to be done. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 2:57:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gray.westgate.gr (gray.westgate.gr [212.205.119.66]) by hub.freebsd.org (Postfix) with ESMTP id A897F37B4C5 for ; Tue, 7 Nov 2000 02:57:21 -0800 (PST) Received: (from charon@localhost) by gray.westgate.gr (8.11.1/8.11.1) id eA7AueA47506; Tue, 7 Nov 2000 12:56:40 +0200 (EET) Date: Tue, 7 Nov 2000 12:56:39 +0200 From: Giorgos Keramidas To: Peter Pentchev Cc: hackers@FreeBSD.ORG Subject: Re: umask(2) and -Wconversion Message-ID: <20001107125639.A47446@gray.westgate.gr> References: <20001107120511.A98074@gray.westgate.gr> <20001107121734.D314@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001107121734.D314@ringworld.oblivion.bg>; from roam@orbitel.bg on Tue, Nov 07, 2000 at 12:17:34PM +0200 X-PGP-Fingerprint: 3A 75 52 EB F1 58 56 0D - C5 B8 21 B6 1B 5E 4A C2 X-URL: http://students.ceid.upatras.gr/~keramida/index.html Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 07, 2000 at 12:17:34PM +0200, Peter Pentchev wrote: > In my experience, the problem is not only with umask(2) - GCC *is* > a bit stubborn about -Wconversion; I wonder if this is really a GCC bug :( > > I'm having the same problems with many other functions when passing > integer constants - even if I explicitly cast them to a long or unsigned > long or plain unsigned int or whatever the particular function needs, > GCC seems to ignore the cast and whines about the conversion nonetheless :( > > Can anybody else confirm this? I can't dig out a code snippet right now, > but ISTR a recurring case of this when compiling with BDECFLAGS a program > which includes ncurses.h, then passes integer constants to init_pair() > or something similar. Yes, that is what I was trying to do. I wanted to buildworld with BDECFLAGS in a 4.2-BETA installation and libskey among other things just bombed when compiling. I tracked the problem to -Wconversion being too strict about the arguments passed to umask, but this seems to be a GCC problem not a problem with umask() :/// I tried compiling the following little program with -Wconversion and it causes the same warning: 1 #include 2 3 int func (short x); 4 5 int main (void) 6 { 7 int var = 10; 8 9 func((short) var); 10 return 0; 11 } 12 13 int func (short var) 14 { 15 printf("var: %d\n", var); 16 return 0; 17 } The cast to (short) in line 9 does not inhibit the warning when the -Wconversion option of gcc is used as shown below: gray% gcc -Wconversion test2.c test2.c: In function `main': test2.c:9: warning: passing arg 1 of `func' with different width due to prototype I think that I will remove -Wconversion from my BDECFLAGS and move on with compiling my world. On a side-note, the -ansi and -pedantic flags also caused a few problems, and I deleted them from my BDECFLAGS last night. Moving on with my quest to remove as many warnings from /usr/src as possible... - giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 3:53:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 6826837B479; Tue, 7 Nov 2000 03:53:29 -0800 (PST) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13t7Je-0002yF-00; Tue, 07 Nov 2000 13:53:26 +0200 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13t7Jd-0005X6-00; Tue, 07 Nov 2000 13:53:25 +0200 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Paul Saab Cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: diskless/routing Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Nov 2000 13:53:25 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, Some more WLP (wee-little-problem :-) 1- not setting a gateway in dhcp panics the kernel. I've been down this road road before, but can't remember the fix - yet :-(. 2- somewhere - and it's not bootp.c - there must be a htonl ntohl problem. example: client-ip: 132.65.80.251 mask: 255.255.0.0 root-server: 132.65.16.6 if I set the gateway (only needed because of 1), to 132.65.32.1 it works - only because the router is sending icmp redirects! - the packets are sent out with the mac address of the router. if set to 132.65.16.1 all is fine. btw, the first stage, tftp is ok, the problem is in the nfs loading of the kernel. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 4:39:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 6A4A137B479 for ; Tue, 7 Nov 2000 04:39:33 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id SAA27864 for ; Tue, 7 Nov 2000 18:39:17 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 7 Nov 2000 18:39:16 +0600 (NS) From: Max Khon To: hackers@freebsd.org Subject: daemon() Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! --- cut here --- #include #include main() { if (daemon(1, 1) < 0) { perror("daemon"); } for (;;) sleep(1); } --- cut here --- lark:~$ps ax | grep foo3 26102 ?? Ss 0:00.00 ./foo3 26104 p8 S+ 0:00.01 grep foo3 lark:~$fstat -p 26102 USER CMD PID FD MOUNT INUM MODE SZ|DV R/W fjoe foo3 26102 root / 2 drwxr-xr-x 512 r fjoe foo3 26102 wd /usr 16007 drwxr-xr-x 8192 r fjoe foo3 26102 text /usr 16071 -rwxrwxr-x 4574 r fjoe foo3 26102 0 / 5542 crw--w---- ttyp8 rw fjoe foo3 26102 1 / 5542 crw--w---- ttyp8 rw fjoe foo3 26102 2 / 5542 crw--w---- ttyp8 rw fjoe foo3 26102 4* pipe c9f1cde0 <-> 0 0 rw lark:~$ what is FD 4? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 4:50:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id E193237B4CF for ; Tue, 7 Nov 2000 04:50:09 -0800 (PST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id NAA28852; Tue, 7 Nov 2000 13:50:05 +0100 (MET) Date: Tue, 7 Nov 2000 13:50:05 +0100 (CET) From: Harti Brandt To: Maksim Yevmenkin Cc: hackers@freebsd.org Subject: Re: if_tap and devfs In-Reply-To: <3A06E7D4.A103EE92@digisle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Nov 2000, Maksim Yevmenkin wrote: Hi Maksim, > > is there somebody working to make if_tap devfs-ready? Or I'm doing > > something wrong? > > [SNIP] > it seems to me that it did not get commited. i will look into it again > today and re-send patch to the list. Great! It works. (Minus a spelling error: the parameter in tapclone() should spell 'namelen'). Would nice if it get's committed. thanks, harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org, lhbrandt@mail.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 4:56:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gwdu60.gwdg.de (gwdu60.gwdg.de [134.76.98.60]) by hub.freebsd.org (Postfix) with ESMTP id 982E237B4D7; Tue, 7 Nov 2000 04:56:28 -0800 (PST) Received: from localhost (kheuer@localhost) by gwdu60.gwdg.de (8.9.3/8.9.3) with ESMTP id NAA01058; Tue, 7 Nov 2000 13:56:21 +0100 (CET) (envelope-from kheuer@gwdu60.gwdg.de) Date: Tue, 7 Nov 2000 13:56:21 +0100 (CET) From: Konrad Heuer To: freebsd-hackers@freebsd.org, freebsd-security@freebsd.org Subject: TCPDUMP patch v1.1 and AppleTalk Message-ID: 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 X-Loop: FreeBSD.ORG This morning I applied the tcpdump v1.1 patch for 4.x-R on a 4.1-R system with following configuration: ti0=09Gigabit-Link=09IPv4 interface xl0=09Fast Ethernet=09AppleTalk interface options NETATALK is included in the kernel config since the host uses the netatalk package exports the home directories for MAC users (the system does a good job since August). After patching and installing, tcpdump can't be used anymore since it puts very heavy load onto the network via xl0 and AppleTalk broadcast messages (one message each 0.2 ms). Sorry, in the moment I don't know more details =2E.. Konrad Heuer Personal Bookmarks: Gesellschaft f=FCr wissenschaftliche Datenverarbeitung mbH G=D6ttingen http://www.freebsd.org Am Fa=DFberg, D-37077 G=D6ttingen http://www.daemonnews.o= rg Deutschland (Germany) kheuer@gwdu60.gwdg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 5:20:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web3504.mail.yahoo.com (web3504.mail.yahoo.com [204.71.203.71]) by hub.freebsd.org (Postfix) with SMTP id 238A937B4D7 for ; Tue, 7 Nov 2000 05:20:13 -0800 (PST) Message-ID: <20001107132009.23436.qmail@web3504.mail.yahoo.com> Received: from [196.7.146.6] by web3504.mail.yahoo.com; Tue, 07 Nov 2000 05:20:09 PST Date: Tue, 7 Nov 2000 05:20:09 -0800 (PST) From: Jacques Fourie Subject: kernel stack size? To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Please excuse any silly questions, but I am stuck with a problem that I can't find the answer for. I wrote a KLD module that performs encryption on network packets in the kernel. Packets are intercepted for encryption on a ethernet level (in ether_input() and ether_output_frame() respectively). This module is implemented on 4.1.1-RELEASE. For input packets I added my own NETISR as well as interrupt queue. In the ether_input() routine the packets are queued and a software interrupt scheduled. Further processing on the packet then happens at a priority of splnet(). If I do bulk data transfers (encrypted) everything works fine until I run a shell script that does a 'ls -lR' in an infinite loop. A few "virtual time alarm" messages appear and then a kernel panic. Looking at the DDB output, it seems a lot like a kernel stack overflow has resulted. Very strange values for ebp and page faults on stack accesses is making me think along these lines. Does anyone know where I can find more information about the kernel stack at interrupt time (such as the maximum size)? I'm also not quite sure what the "virtual time alarm" messages mean, can anyone help me out? jacques __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one Place. http://shopping.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 5:30: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 1648137B4D7 for ; Tue, 7 Nov 2000 05:30:07 -0800 (PST) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 878B2A82B; Wed, 8 Nov 2000 00:30:05 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 813AC5465; Tue, 7 Nov 2000 23:30:05 +1000 (EST) Date: Tue, 7 Nov 2000 23:30:05 +1000 (EST) From: andrew@ugh.net.au To: Giorgos Keramidas Cc: hackers@freebsd.org Subject: Re: umask(2) and -Wconversion In-Reply-To: <20001107120511.A98074@gray.westgate.gr> Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Nov 2000, Giorgos Keramidas wrote: > discovered the following funny thing about -Wconversion and umask(2), I spent quite a while trying to silence that warning in one of my programs the otherday but I decided it was probably harmless and left it. > and vice versa, and conversions changing the width or signedness > of a fixed point argument except when the same as the default > promotion. I think this is what we are hitting. From memory mode_t is a u_int16_t. When you pass 0 (a 32 bit number) it gets cast to a 16 bit number (change of width) and so produces the warning. I think the reason that the cast doesn't help (or passing a u_int16_t) is that when the 16 bit number gets passed it has to be placed on the 32 bit stack which promotes it so you will always end up with a demotion when the number is taken from the stack and given to umaks as a 16 bit int. OTH I could be wrong :-) I haven't looked at the gcc source. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 5:41:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id C939737B4C5 for ; Tue, 7 Nov 2000 05:41:19 -0800 (PST) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 02619A82B; Wed, 8 Nov 2000 00:41:19 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id EF3625465; Tue, 7 Nov 2000 23:41:19 +1000 (EST) Date: Tue, 7 Nov 2000 23:41:19 +1000 (EST) From: andrew@ugh.net.au To: Max Khon Cc: hackers@freebsd.org Subject: Re: daemon() In-Reply-To: Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Nov 2000, Max Khon wrote: > what is FD 4? I can't reproduce this? Does it always happen? Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 5:45:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 4FB6637B657 for ; Tue, 7 Nov 2000 05:45:25 -0800 (PST) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id FAA27768; Tue, 7 Nov 2000 05:43:18 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id FAA81876; Tue, 7 Nov 2000 05:43:17 -0800 (PST) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id FAA10397; Tue, 7 Nov 2000 05:43:17 -0800 (PST) From: Don Lewis Message-Id: <200011071343.FAA10397@salsa.gv.tsc.tdk.com> Date: Tue, 7 Nov 2000 05:43:17 -0800 In-Reply-To: References: X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: andrew@ugh.net.au, Max Khon Subject: Re: daemon() Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov 7, 11:41pm, andrew@ugh.net.au wrote: } Subject: Re: daemon() } } } On Tue, 7 Nov 2000, Max Khon wrote: } } > what is FD 4? } } I can't reproduce this? Does it always happen? It might be something that the shell forgets to close, so it will be dependent on which shell you use. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 5:51:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.oblivion.bg (pool153-tch-1.Sofia.0rbitel.net [212.95.170.153]) by hub.freebsd.org (Postfix) with SMTP id 2DF8337B4CF for ; Tue, 7 Nov 2000 05:51:44 -0800 (PST) Received: (qmail 5595 invoked by uid 1000); 7 Nov 2000 13:51:32 -0000 Date: Tue, 7 Nov 2000 15:51:32 +0200 From: Peter Pentchev To: andrew@ugh.net.au Cc: Max Khon , hackers@freebsd.org Subject: Re: daemon() Message-ID: <20001107155132.A4407@ringworld.oblivion.bg> Mail-Followup-To: andrew@ugh.net.au, Max Khon , hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from andrew@ugh.net.au on Tue, Nov 07, 2000 at 11:41:19PM +1000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 07, 2000 at 11:41:19PM +1000, andrew@ugh.net.au wrote: > > > On Tue, 7 Nov 2000, Max Khon wrote: > > > what is FD 4? > > I can't reproduce this? Does it always happen? Me neither.. RELENG_4 here, but daemon() seems to be exactly the same across (supported) releases. All fd's I can see on a fstat -p are 0, 1 and 2. G'luck, Peter -- If there were no counterfactuals, this sentence would not have been paradoxical. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 6:24:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id B8AD937B479 for ; Tue, 7 Nov 2000 06:24:38 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id UAA37712; Tue, 7 Nov 2000 20:24:20 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 7 Nov 2000 20:24:19 +0600 (NS) From: Max Khon To: andrew@ugh.net.au Cc: hackers@freebsd.org Subject: Re: daemon() In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Tue, 7 Nov 2000 andrew@ugh.net.au wrote: > > what is FD 4? > > I can't reproduce this? Does it always happen? yes. I am running sample program under FreeBSD 4.2-BETA (31 Oct 2000) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 6:29:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from genius.systems.pavilion.net (genesis.tao.org.uk [194.242.131.254]) by hub.freebsd.org (Postfix) with ESMTP id 55A3937B4C5 for ; Tue, 7 Nov 2000 06:29:10 -0800 (PST) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id D6A339B2D; Tue, 7 Nov 2000 14:32:44 +0000 (GMT) Date: Tue, 7 Nov 2000 14:32:44 +0000 From: Josef Karthauser To: hackers@freebsd.org Subject: Mounting a md as a root filesystem. Message-ID: <20001107143244.B56873@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having trouble mounting an MD as a root filesystem from 5.0. Can anyone tell me what I'm doing wrong please? /boot/loader: # load /kernel # load -t md /filesystemfile # boot PROBES,etc. Manual root filesystem specification: : Mount using filesystem etc... Yes, I do have MD_ROOT compiled into my kernel. Any help would be very much appreciated. Thanks, Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 6:30:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 792BC37B4C5 for ; Tue, 7 Nov 2000 06:30:07 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id UAA37875; Tue, 7 Nov 2000 20:29:37 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 7 Nov 2000 20:29:37 +0600 (NS) From: Max Khon To: Don Lewis Cc: andrew@ugh.net.au, hackers@FreeBSD.ORG Subject: Re: daemon() In-Reply-To: <200011071343.FAA10397@salsa.gv.tsc.tdk.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Tue, 7 Nov 2000, Don Lewis wrote: > } > what is FD 4? > } > } I can't reproduce this? Does it always happen? > > It might be something that the shell forgets to close, so it will be > dependent on which shell you use. exactly. this does not happen if I run this program from tcsh (but does if I run from bash 1.14.7(1) built from ports thanks! /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 6:32:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.oblivion.bg (pool153-tch-1.Sofia.0rbitel.net [212.95.170.153]) by hub.freebsd.org (Postfix) with SMTP id 293AA37B479 for ; Tue, 7 Nov 2000 06:32:47 -0800 (PST) Received: (qmail 6153 invoked by uid 1000); 7 Nov 2000 14:32:35 -0000 Date: Tue, 7 Nov 2000 16:32:34 +0200 From: Peter Pentchev To: Max Khon Cc: andrew@ugh.net.au, hackers@freebsd.org Subject: Re: daemon() Message-ID: <20001107163234.B4407@ringworld.oblivion.bg> Mail-Followup-To: Max Khon , andrew@ugh.net.au, hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from fjoe@iclub.nsu.ru on Tue, Nov 07, 2000 at 08:24:19PM +0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 07, 2000 at 08:24:19PM +0600, Max Khon wrote: > hi, there! > > On Tue, 7 Nov 2000 andrew@ugh.net.au wrote: > > > > what is FD 4? > > > > I can't reproduce this? Does it always happen? > > yes. I am running sample program under FreeBSD 4.2-BETA (31 Oct 2000) As was already mentioned, this most probably has something to do with the shell. Which shell are you using? I tried that program under /bin/sh, /bin/csh, /bin/tcsh and bash 2.04, and fd 4 never did show up. G'luck, Peter -- I had to translate this sentence into English because I could not read the original Sanskrit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 6:51: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from neimail.networkengines.com (unknown [64.55.6.7]) by hub.freebsd.org (Postfix) with ESMTP id E238537B4C5; Tue, 7 Nov 2000 06:50:55 -0800 (PST) Received: by neimail.networkengines.com with Internet Mail Service (5.5.2650.21) id ; Tue, 7 Nov 2000 09:48:08 -0500 Message-ID: <8D18C4F9CBA1D311900F00A0C990C97F67CB4A@neimail.networkengines.com> From: Andrew Sporner To: "'Michael C . Wu'" , Andrew Sporner Cc: freebsd-net@freebsd.org, "'freebsd-hackers@freebsd.org'" Subject: RE: High-availability failover software available. Date: Tue, 7 Nov 2000 09:48:07 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! > | a H/A Failover system that happens to work with BSD. I > would like to > | contribute > | this to the FreeBSD project or at a minimum make it > available to those who > | What it includes is: > | - Multi-path heartbeat based node failure detection. > > How do you determine that a machine/service is "failing"? > Have you considered that the distributed nodes might be very far > away from each other, even across the globe? Lag time can > lead to daemon falsely thinking that a node is down. This is for local area clusters. This is really foundation work for another project I have in mind, involving process swapping. I needed a way of finding when a node died to do some garbage collection. As it turned out, it didn't take much to make it work for doing application failover. So I thought, "Well since there doesn't appear to be anything free this way--why not!? and so here it is." In short I am not trying to solve geographical failover because it isn't really germaine to my goal. But, if the architecture lends itself to it, there is no reason not to include it. Any takers? But to answer your question. A heart beat message is sent on the broadcast address of the networks that the machine lives on. Currently it will use all of them. I think a necessary feature would be to allow for a subset of interfaces. :-) But I wanted to solve the bigger problems first. When a peer node recieves the packet, it updates a timestamp for it's peer interface. Periodically these are checked and if one of the links is out of bounds, it is marked offline. When the last live interface is marked offline, the node is marked offline and then the recovery procedure starts. There may be a need to start recovery if only one interface fails, but again this is outside the mission I have embarked on. Mainly because the architecture I am pursing requires that the heartbeat lans (which will also be used to transfer pages between machines) be private and not used for user applications. In this way I get link recovery through redundancy and the cluster software knows how to handle it--where an application might (actually probably) won't know how to handle it. But to stop a potential argument--let's leave it strictly the case of keeping these particular lans private. > > Reading your code, I don't think broadcasting over all > interfaces is a good idea. A safer way would be requiring two > physical interfaces on all nodes, building two seperate physical > networks. The nodes communicate information on one network, and > do the actual "work" on the other, more powerful, network. The > daemons on the nodes should broadcast over these two interfaces. > In addition, a comparison between the connectivity of the two physical > networks can provide lots of valuable info. I agree! I am answering this email serially and am reading as I reply and it looks like we are in sync. I will in the next few releases privide a delete option on the GUI to take away an autodiscovered interface. I think the autodiscovery is important, but it should be allowed to be updated. The interface will remain in the configuration (so it doesn't get autodiscovered again! :-)) but marked with a special flag so it isn't used. An upcoming feature is the ability to drag a lan interface over to the right of the GUI to monitor LAN perforamce. I also plan to have several metrics tied to each resource and by right-clicking on the guages that are there you can change them. Right now The applications or nodes can be monitored and it is only CPU, MEMORY and one other--been too long since I saw it. At one point I even thougth about putting TOP functionality in the GUI so that by expanding a node, one can also see the processes and drag a process over to the right side to monitor it. > A great thing to do with this code would be using kqueue. Can you give me more specifics? or better--would you be willing to try it and give me the patch? > > I think there should be a daemon that "routes" service queries, say > a http request, to different nodes as the requests come in. Like a load balancer? :-) I had one once and unfortunately two things. First it won't scale (reverse proxy) and second some people I worked on this for would have a fit. I went to a great mini-tutorial at BSDcon about IP filter. Guido mentioned something about having a kernel filter rule that calls a kernel address for each packet. A good way to do this would be to put a router inside the kernel and then leverage the IP filter. > > | - Drag&Drop administration interface (X-11 tcl/tk based > > I think this should also include a console-type controller. > Real-life work involves admining remotely, and GUI apps are not > that great remotely. :-) OK, next release! :-) > > | The current state is alpha and is being tested by several > people now. Beta > | The current source is located at http://www.sporner.com/bsdclusters > > Please document what you have done, so we can learn more about > the engineering thinking behind your implementation. In progress, maybe some of my answers here would help. I also have heavily commented the cluster.c code. But I will write a document detailing how and why in the near future. > Will this be BSDL or will it be another license? Also, please > include man pages. Yes, and yes :-) > I think we missed a great chance to talk to each other, since my > research interest is the same field as your project. Or we may have > met, I'm the Chinese guy that had the shortest hair. > > P.S. Please keep lines shorter than 80 characters. :) Ahhh! A terminal guy :-) I will try to, but since I kind of whored myself to microsoft for email it is hard to think about this :-) Thanks for all of your feedback! Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 7: 2:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 661D637B4CF for ; Tue, 7 Nov 2000 07:02:23 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id QAA49380; Tue, 7 Nov 2000 16:02:19 +0100 (CET) (envelope-from des@ofug.org) 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: Josef Karthauser Cc: hackers@FreeBSD.ORG Subject: Re: Mounting a md as a root filesystem. References: <20001107143244.B56873@pavilion.net> From: Dag-Erling Smorgrav Date: 07 Nov 2000 16:02:19 +0100 In-Reply-To: Josef Karthauser's message of "Tue, 7 Nov 2000 14:32:44 +0000" Message-ID: Lines: 9 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser writes: > # load -t md /filesystemfile Shouldn't that be 'load -t md_root'? 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 Tue Nov 7 7:13:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 85BC437B479 for ; Tue, 7 Nov 2000 07:13:37 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id QAA49454; Tue, 7 Nov 2000 16:13:31 +0100 (CET) (envelope-from des@ofug.org) 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: void Cc: hackers@FreeBSD.ORG Subject: Re: "iowait" CPU state References: <20001107054413.A1983@firedrake.org> From: Dag-Erling Smorgrav Date: 07 Nov 2000 16:13:30 +0100 In-Reply-To: void's message of "Tue, 7 Nov 2000 05:44:13 +0000" Message-ID: Lines: 14 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG void writes: > I've been using Solaris a lot lately, and I've noticed that in e.g. > top's output, it has a distinct CPU state called "iowait", which seems > to be a pretty good indicator of how I/O-bound a system is. Is there > any reason that FreeBSD doesn't have such a state? It has several, depending on the type of I/O the process is waiting for: biord (waiting for a read operation to complete), biowr (waiting for a write operation to complete), select (waiting for descriptors to become readable / writable), etc. 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 Tue Nov 7 7:30:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (unknown [213.162.128.50]) by hub.freebsd.org (Postfix) with ESMTP id E7F1F37B4D7 for ; Tue, 7 Nov 2000 07:30:07 -0800 (PST) Received: by mimer.webgiro.com (Postfix, from userid 66) id A82B82DC0B; Tue, 7 Nov 2000 16:32:48 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 762387817; Tue, 7 Nov 2000 16:28:26 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 68E1810E1A; Tue, 7 Nov 2000 16:28:26 +0100 (CET) Date: Tue, 7 Nov 2000 16:28:26 +0100 (CET) From: Andrzej Bialecki To: Dag-Erling Smorgrav Cc: Josef Karthauser , hackers@FreeBSD.ORG Subject: Re: Mounting a md as a root filesystem. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 7 Nov 2000, Dag-Erling Smorgrav wrote: > Josef Karthauser writes: > > # load -t md /filesystemfile > > Shouldn't that be 'load -t md_root'? Actually, it's md_image or mfs_root (see /sys/dev/md/md.c:446). Both of these are mentioned in md(4). Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 7:53:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.sereb.net (ip50-246.dialup.wplus.net [195.131.50.246]) by hub.freebsd.org (Postfix) with ESMTP id 4F6E537B4D7 for ; Tue, 7 Nov 2000 07:53:37 -0800 (PST) Received: from lev.sereb.net (lev.sereb.net [192.168.1.1]) by freebsd.sereb.net (8.9.3/8.9.3) with ESMTP id SAA00874 for ; Tue, 7 Nov 2000 18:53:28 +0300 (MSK) (envelope-from lev@serebryakov.spb.ru) Date: Tue, 7 Nov 2000 18:53:58 +0300 From: Lev Serebryakov X-Mailer: The Bat! (v1.41) Reply-To: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <7787.001107@serebryakov.spb.ru> To: All Subject: SIGALARM is loosing when time are shifted. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, All! How are you? One my program use alarm() to interrupt some blocking system calls. I use alarm(1) (one second). Everything works Ok, except cases, when ntpdate shift time more than 1 second forward. If time is shifted when alarm are set already, but not generated yet, SIGALARM doesn't occur at all :( Is it normal? Lev Serebryakov /-----------------------------------------------\ | FIDONet: 2:5030/661.0 | | E-Mail: lev@serebryakov.spb.ru | | Page: http://lev.serebyrakov.spb.ru/ | | ICQ UIN: 3670018 | | Phone: You know, if you have world nodelist | \===============================================/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 8:19: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gray.westgate.gr (gray.westgate.gr [212.205.119.66]) by hub.freebsd.org (Postfix) with ESMTP id 2845837B479 for ; Tue, 7 Nov 2000 08:18:55 -0800 (PST) Received: (from charon@localhost) by gray.westgate.gr (8.11.1/8.11.1) id eA7GHvI49458; Tue, 7 Nov 2000 18:17:57 +0200 (EET) Date: Tue, 7 Nov 2000 18:17:57 +0200 From: Giorgos Keramidas To: andrew@ugh.net.au Cc: hackers@freebsd.org Subject: Re: umask(2) and -Wconversion Message-ID: <20001107181757.A49354@gray.westgate.gr> References: <20001107120511.A98074@gray.westgate.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from andrew@ugh.net.au on Tue, Nov 07, 2000 at 11:30:05PM +1000 X-PGP-Fingerprint: 3A 75 52 EB F1 58 56 0D - C5 B8 21 B6 1B 5E 4A C2 X-URL: http://students.ceid.upatras.gr/~keramida/index.html Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 07, 2000 at 11:30:05PM +1000, andrew@ugh.net.au wrote: > > On Tue, 7 Nov 2000, Giorgos Keramidas wrote: > > > discovered the following funny thing about -Wconversion and umask(2), > > I spent quite a while trying to silence that warning in one of my programs > the otherday but I decided it was probably harmless and left it. The warning in itself is rather harmless, since it does not cause much trouble. However some parts of a FreeBSD world are compiled with -Werror, and every warning is considered an error that causes compilation to abort :> Anyway, this is getting more and more off-topic, since it's obviously something caused by GCC's strictness when -Wconversion is used. > I think the reason that the cast doesn't help (or passing a u_int16_t) > is that when the 16 bit number gets passed it has to be placed on > the 32 bit stack which promotes it so you will always end up with a > demotion when the number is taken from the stack and given to umaks as > a 16 bit int. I thought that the cast would help because the size of (mode_t) is known in compile time, and I expected the compiler to place the result of an expression like `(mode_t) 0' in a properly sized integer type. I mean, one would expect that ((short) 0) would be different than ((int) 0); isn't the compiler supposed to know the diference, if both types have sizes that are known at compile time? Whatever... I will also remove -Wconversion from my make.conf CFLAGS and move on. This is probably discussed with the GCC fellows. I will sum up what this thread was all about, and post a mail to their lists tomorrow. I'm too tired to write to them right now. - giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 8:32:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-99.zoominternet.net [24.154.28.99]) by hub.freebsd.org (Postfix) with ESMTP id 6B0D737B479 for ; Tue, 7 Nov 2000 08:32:19 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by topperwein.dyndns.org (8.11.1/8.11.1) with ESMTP id eA7GWBo07975; Tue, 7 Nov 2000 11:32:11 -0500 (EST) (envelope-from behanna@zbzoom.net) Date: Tue, 7 Nov 2000 11:32:11 -0500 (EST) From: Chris BeHanna Reply-To: behanna@zbzoom.net To: Peter Pentchev Cc: Giorgos Keramidas , hackers@FreeBSD.ORG Subject: Re: umask(2) and -Wconversion In-Reply-To: <20001107121734.D314@ringworld.oblivion.bg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Nov 2000, Peter Pentchev wrote: > In my experience, the problem is not only with umask(2) - GCC *is* > a bit stubborn about -Wconversion; I wonder if this is really a GCC bug :( > > I'm having the same problems with many other functions when passing > integer constants - even if I explicitly cast them to a long or unsigned > long or plain unsigned int or whatever the particular function needs, > GCC seems to ignore the cast and whines about the conversion nonetheless :( > > Can anybody else confirm this? I can't dig out a code snippet right now, > but ISTR a recurring case of this when compiling with BDECFLAGS a program > which includes ncurses.h, then passes integer constants to init_pair() > or something similar. What happens if you pass an explicit long or unsigned long literal instead of casting an integer literal? Like this: void myfunc( unsigned long); int main( int argc, char* argv[]) { myfunc( 12UL); return 0; } I realize, of course, that going through and changing every array subscript, for example, is a PITA. I'm just curious about whether or not this makes gcc behave nicely. -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 8:43:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.oblivion.bg (pool153-tch-1.Sofia.0rbitel.net [212.95.170.153]) by hub.freebsd.org (Postfix) with SMTP id F3C6137B479 for ; Tue, 7 Nov 2000 08:43:09 -0800 (PST) Received: (qmail 14283 invoked by uid 1000); 7 Nov 2000 16:42:53 -0000 Date: Tue, 7 Nov 2000 18:42:53 +0200 From: Peter Pentchev To: Chris BeHanna Cc: Giorgos Keramidas , hackers@FreeBSD.ORG Subject: Re: umask(2) and -Wconversion Message-ID: <20001107184253.D4407@ringworld.oblivion.bg> Mail-Followup-To: Chris BeHanna , Giorgos Keramidas , hackers@FreeBSD.ORG References: <20001107121734.D314@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from behanna@zbzoom.net on Tue, Nov 07, 2000 at 11:32:11AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 07, 2000 at 11:32:11AM -0500, Chris BeHanna wrote: > On Tue, 7 Nov 2000, Peter Pentchev wrote: > > > In my experience, the problem is not only with umask(2) - GCC *is* > > a bit stubborn about -Wconversion; I wonder if this is really a GCC bug :( > > > > I'm having the same problems with many other functions when passing > > integer constants - even if I explicitly cast them to a long or unsigned > > long or plain unsigned int or whatever the particular function needs, > > GCC seems to ignore the cast and whines about the conversion nonetheless :( > > > > Can anybody else confirm this? I can't dig out a code snippet right now, > > but ISTR a recurring case of this when compiling with BDECFLAGS a program > > which includes ncurses.h, then passes integer constants to init_pair() > > or something similar. > > What happens if you pass an explicit long or unsigned long > literal instead of casting an integer literal? Like this: > > void myfunc( unsigned long); > > int > main( int argc, char* argv[]) > { > myfunc( 12UL); > return 0; > } > > I realize, of course, that going through and changing every array > subscript, for example, is a PITA. I'm just curious about whether or > not this makes gcc behave nicely. Actually, I just got hold of a code snippet - the problem is not only with passing constants. A prime example is the init_pair() that I already mentioned. In ncurses.h: extern int init_pair(short,short,short); I have: typedef enum { RS_CLR_NULL, RS_CLR_MENU, RS_CLR_DLG, RS_CLR_LAST } rs_clr_t; typedef struct { short f, b; } rs_clrpair_t; static rs_clrpair_t rs_pairs[RS_CLR_LAST] = { {COLOR_BLACK, COLOR_BLACK}, {COLOR_WHITE, COLOR_BLACK}, {COLOR_YELLOW, COLOR_BLUE} }; rs_err_t rs_color_init(void) { short i; start_color(); for(i = 0; i < RS_CLR_LAST; i++) init_pair(i, rs_pairs[i].f, rs_pairs[i].b); return RS_ERR_NONE; } As you can see, I'm passing a short i as a first arg, a short f as second, and a short b as third; and yet, gcc with BDECFLAGS complains about ALL the arguments! G'luck, Peter -- This sentence every third, but it still comprehensible. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 9: 3:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 2BFD537B479 for ; Tue, 7 Nov 2000 09:03:52 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA50361; Tue, 7 Nov 2000 18:03:40 +0100 (CET) (envelope-from des@ofug.org) 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: Graham Wheeler Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Help writing a screen saver module References: <3A06B7A7.7665C46A@cequrux.com> From: Dag-Erling Smorgrav Date: 07 Nov 2000 18:03:39 +0100 In-Reply-To: Graham Wheeler's message of "Mon, 06 Nov 2000 15:52:39 +0200" Message-ID: Lines: 15 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Graham Wheeler writes: > I am trying to write a screen saver module that, when it kicks in, will > switch to the first console, and then, if a key is pressed, will switch > back to the one that was previously active. The idea is that the first > console has something useful running on it, typically a tail -f of the > logs. Switching consoles causes syscons to stop the screensaver, which causes your code to try to switch back to the original console, which causes syscons to stop the screensaver since seems to be running. In other words, Don't Do That. Sorry. 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 Tue Nov 7 9:28:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ruby.digisle.com (ruby.digisle.net [167.216.192.43]) by hub.freebsd.org (Postfix) with ESMTP id 2BE3437B4CF; Tue, 7 Nov 2000 09:27:58 -0800 (PST) Received: from guinness.digisle.net (guinness.digisle.net [167.216.152.33]) by ruby.digisle.com (8.9.3/8.9.3/mx) with ESMTP id RAA17890; Tue, 7 Nov 2000 17:27:56 GMT Received: from digisle.com (comanche.digisle.com [206.220.227.145]) by guinness.digisle.net (8.9.3/8.9.3/digisle) with ESMTP id RAA21536; Tue, 7 Nov 2000 17:27:55 GMT Message-ID: <3A083B9A.4C1DDD82@digisle.com> Date: Tue, 07 Nov 2000 09:27:54 -0800 From: Maksim Yevmenkin Organization: Digital Island X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Harti Brandt Cc: current@freebsd.org, hackers@freebsd.org Subject: [PATCH] Please review and commit (Re: if_tap and devfs) References: Content-Type: multipart/mixed; boundary="------------367164509B202DD0CF71424B" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------367164509B202DD0CF71424B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Harti, > > > is there somebody working to make if_tap devfs-ready? Or I'm doing > > > something wrong? > > > > [SNIP] > > it seems to me that it did not get commited. i will look into it again > > today and re-send patch to the list. > > Great! It works. (Minus a spelling error: the parameter in > tapclone() should spell 'namelen'). Would nice if it get's committed. ooops :) sorry about that. unfortunately, i can not commit it. we have to ask one of the commiters. To ALL: anyone wants to review and commit the attached patch? thanks, emax --------------367164509B202DD0CF71424B Content-Type: text/plain; charset=us-ascii; name="if_tap.c.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="if_tap.c.diff" *** if_tap.c.orig Mon Nov 6 09:24:08 2000 --- if_tap.c Mon Nov 6 10:26:35 2000 *************** *** 79,84 **** --- 79,85 ---- static int tapmodevent __P((module_t, int, void *)); /* device */ + static void tapclone __P((void *, char *, int, dev_t *)); static void tapcreate __P((dev_t)); /* network interface */ *************** *** 131,157 **** int type; void *data; { ! static int attached = 0; ! struct ifnet *ifp = NULL; ! int unit, s; switch (type) { case MOD_LOAD: if (attached) return (EEXIST); cdevsw_add(&tap_cdevsw); attached = 1; break; ! case MOD_UNLOAD: if (taprefcnt > 0) return (EBUSY); cdevsw_remove(&tap_cdevsw); unit = 0; while (unit <= taplastunit) { s = splimp(); TAILQ_FOREACH(ifp, &ifnet, if_link) if ((strcmp(ifp->if_name, TAP) == 0) || --- 132,164 ---- int type; void *data; { ! static int attached = 0; ! static eventhandler_tag eh_tag = NULL; switch (type) { case MOD_LOAD: if (attached) return (EEXIST); + eh_tag = EVENTHANDLER_REGISTER(dev_clone, tapclone, 0, 1000); cdevsw_add(&tap_cdevsw); attached = 1; break; ! case MOD_UNLOAD: { ! int unit; ! if (taprefcnt > 0) return (EBUSY); + EVENTHANDLER_DEREGISTER(dev_clone, eh_tag); cdevsw_remove(&tap_cdevsw); unit = 0; while (unit <= taplastunit) { + int s; + struct ifnet *ifp = NULL; + s = splimp(); TAILQ_FOREACH(ifp, &ifnet, if_link) if ((strcmp(ifp->if_name, TAP) == 0) || *************** *** 179,185 **** } attached = 0; ! break; default: return (EOPNOTSUPP); --- 186,192 ---- } attached = 0; ! } break; default: return (EOPNOTSUPP); *************** *** 187,192 **** --- 194,234 ---- return (0); } /* tapmodevent */ + + + /* + * DEVFS handler + * + * We need to support two kind of devices - tap and vmnet + */ + static void + tapclone(arg, name, namelen, dev) + void *arg; + char *name; + int namelen; + dev_t *dev; + { + int unit, minor; + char *device_name = NULL; + + if (*dev != NODEV) + return; + + device_name = TAP; + if (dev_stdclone(name, NULL, device_name, &unit) != 1) { + device_name = VMNET; + + if (dev_stdclone(name, NULL, device_name, &unit) != 1) + return; + + minor = (unit | VMNET_DEV_MASK); + } + else + minor = unit; + + *dev = make_dev(&tap_cdevsw, minor, UID_ROOT, GID_WHEEL, 0600, "%s%d", + device_name, unit); + } /* tapclone */ /* --------------367164509B202DD0CF71424B-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 9:33: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 978C537B4C5 for ; Tue, 7 Nov 2000 09:33:05 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA50486; Tue, 7 Nov 2000 18:33:01 +0100 (CET) (envelope-from des@ofug.org) 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: Andrzej Bialecki Cc: Josef Karthauser , hackers@FreeBSD.ORG Subject: Re: Mounting a md as a root filesystem. References: From: Dag-Erling Smorgrav Date: 07 Nov 2000 18:33:00 +0100 In-Reply-To: Andrzej Bialecki's message of "Tue, 7 Nov 2000 16:28:26 +0100 (CET)" Message-ID: Lines: 17 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki writes: > On 7 Nov 2000, Dag-Erling Smorgrav wrote: > > Josef Karthauser writes: > > > # load -t md /filesystemfile > > Shouldn't that be 'load -t md_root'? > Actually, it's md_image or mfs_root (see /sys/dev/md/md.c:446). Both of > these are mentioned in md(4). In that case, md(4) is wrong: des@aes ~% current md_root src/sys/dev/md/md.c: SYSINIT(md_root, SI_SUB_MOUNT_ROOT, SI_ORDER_FIRST, md_takeroot, NULL); src/sys/i386/conf/NOTES: # images of type mfs_root or md_root. 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 Tue Nov 7 10:14:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 1EAB937B479 for ; Tue, 7 Nov 2000 10:14:42 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13tDGZ-0002On-00; Tue, 07 Nov 2000 18:14:39 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id eA7HI5I01235; Tue, 7 Nov 2000 18:18:05 +0100 (CET) (envelope-from wkb) Date: Tue, 7 Nov 2000 18:18:05 +0100 From: Wilko Bulte To: Stefan Aeschbacher Cc: hackers@freebsd.org Subject: Re: hardware problem? Message-ID: <20001107181805.A735@freebie.demon.nl> References: <3A07D2F1.E169FC96@aeschbacher.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A07D2F1.E169FC96@aeschbacher.com>; from stefan@aeschbacher.com on Tue, Nov 07, 2000 at 11:01:21AM +0100 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 07, 2000 at 11:01:21AM +0100, Stefan Aeschbacher wrote: > cc: Internal compiler error: program ld got fatal signal 11 > > this error happens during each compilation but it does not > happen at the same location in the source code each run. > furthermore, some daemons tend to segfault extremely often. > > I had the same problems some time ago and thought it is > caused by kernel and world being out of sinc (I was not > very careful when updating at this time) but this should > not be the case now. > Any propositions on how to debug this thing? > Could it be a hardware problem? Definitely yes. Check memory, CPU cooling, overclocking, powersupply. -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 10:40:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (mail.dobox.com [208.187.122.44]) by hub.freebsd.org (Postfix) with ESMTP id 617EE37B479; Tue, 7 Nov 2000 10:40:53 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13tDgV-0000Ke-00; Tue, 07 Nov 2000 11:41:27 -0700 Message-ID: <3A084CD7.D8023C33@softweyr.com> Date: Tue, 07 Nov 2000 11:41:27 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Maarten van Schie Cc: mb@imp.ch, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: StarOffice 5.2 port for FreeBSD. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maarten van Schie wrote: > > When I installed SO it didn't spitt out any complaints about the checksum. > > Did you install the Linux Emulator from /usr/ports/emulators/linux_base ? > You need it since the SO port uses the Linux version. Yes, and linux-netscape and wordperfect both install and run without any problems. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 10:47:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 45CAA37B479 for ; Tue, 7 Nov 2000 10:47:51 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eA7Ij4d81283; Tue, 7 Nov 2000 10:45:04 -0800 (PST) (envelope-from dillon) Date: Tue, 7 Nov 2000 10:45:04 -0800 (PST) From: Matt Dillon Message-Id: <200011071845.eA7Ij4d81283@earth.backplane.com> To: Jacques Fourie Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: kernel stack size? References: <20001107132009.23436.qmail@web3504.mail.yahoo.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi : :Please excuse any silly questions, but I am stuck with :a problem that I can't find the answer for. : :I wrote a KLD module that performs encryption on :network packets in the kernel. Packets are intercepted :for encryption on a ethernet level (in ether_input() :and ether_output_frame() respectively). This module is :implemented on 4.1.1-RELEASE. : :For input packets I added my own NETISR as well as :interrupt queue. In the ether_input() routine the :packets are queued and a software interrupt scheduled. :Further processing on the packet then happens at a :priority of splnet(). : :If I do bulk data transfers (encrypted) everything :works fine until I run a shell script that does a :'ls -lR' in an infinite loop. A few "virtual time :alarm" messages appear and then a kernel panic. :Looking at the DDB output, it seems a lot like a :kernel stack overflow has resulted. Very strange :values for ebp and page faults on stack accesses is :making me think along these lines. : :Does anyone know where I can find more information :about the kernel stack at interrupt time (such as the :maximum size)? :I'm also not quite sure what the "virtual time alarm" :messages mean, can anyone help me out? : :jacques The stack is very small. You cannot safely allocate large structures on the stack -- I would limit your stack utilization to 256 bytes total to be safe. If you need to allocate large structures or arrays you need to do it at device-open and then save a reference that your interrupt can then use. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 12:42:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 0932F37B479 for ; Tue, 7 Nov 2000 12:42:32 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.11.1) id eA7Kg3w16327; Tue, 7 Nov 2000 14:42:03 -0600 (CST) (envelope-from dan) Date: Tue, 7 Nov 2000 14:42:02 -0600 From: Dan Nelson To: Dag-Erling Smorgrav Cc: Graham Wheeler , freebsd-hackers@FreeBSD.ORG Subject: Re: Help writing a screen saver module Message-ID: <20001107144202.B4569@dan.emsphone.com> References: <3A06B7A7.7665C46A@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from "Dag-Erling Smorgrav" on Tue Nov 7 18:03:39 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 07), Dag-Erling Smorgrav said: > Graham Wheeler writes: > > I am trying to write a screen saver module that, when it kicks in, > > will switch to the first console, and then, if a key is pressed, > > will switch back to the one that was previously active. The idea is > > that the first console has something useful running on it, > > typically a tail -f of the logs. > > Switching consoles causes syscons to stop the screensaver, which > causes your code to try to switch back to the original console, which > causes syscons to stop the screensaver since seems to be running. In > other words, Don't Do That. Sorry. You can make it look like you're switched to vty 0, by making your screen_saver() function simply copy the contents of vty 0 to screen memory on every update. Just make sure both vtys are the same size first... -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 14:12:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout01.sul.t-online.com (mailout01.sul.t-online.com [194.25.134.80]) by hub.freebsd.org (Postfix) with ESMTP id 9482F37B479 for ; Tue, 7 Nov 2000 14:12:21 -0800 (PST) Received: from fwd03.sul.t-online.com by mailout01.sul.t-online.com with smtp id 13tGya-0003XM-03; Tue, 07 Nov 2000 23:12:20 +0100 Received: from venus.system7.de (320051988339-0001@[62.224.116.153]) by fwd03.sul.t-online.com with esmtp id 13tGyP-0O1IsiC; Tue, 7 Nov 2000 23:12:09 +0100 Received: by venus.system7.de (Postfix, from userid 1001) id 61C0B543C; Tue, 7 Nov 2000 23:12:08 +0100 (CET) Date: Tue, 7 Nov 2000 23:12:08 +0100 From: Sven.Huster@t-online.de (Sven Huster) To: freebsd-hackers@freebsd.org Subject: problem with sysinstall and serial console Message-ID: <20001107231207.A26779@venus.system7.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Sender: 320051988339-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi everyone, i want to install serveral intel isp1100 servers with serial console attached. the problem is that is want install them automatically without any user interaction. but sysinstall asks me for the terminal type on serial console. everything else work real fine (pxe boot, package install and so on). thanks sven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 14:58: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2F5F437B4C5; Tue, 7 Nov 2000 14:58:04 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eA7Mw3E12510; Tue, 7 Nov 2000 14:58:03 -0800 (PST) Date: Tue, 7 Nov 2000 14:58:03 -0800 From: Alfred Perlstein To: jkh@freebsd.org Cc: hackers@freebsd.org Subject: Documenting sysV IPC tunables. Message-ID: <20001107145803.G5112@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a patch here that I'd like to get into LINT for 4.2, it _finally_ documents the sysV IPC tunables. I'll also be applying this patch to NOTES for -current. Index: LINT =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/Attic/LINT,v retrieving revision 1.749.2.35 diff -u -u -r1.749.2.35 LINT --- LINT 2000/10/31 23:16:07 1.749.2.35 +++ LINT 2000/11/07 22:57:59 @@ -272,9 +272,33 @@ # Definition-style interprocess communication, in the form of shared # memory, semaphores, and message queues, respectively. # -options SYSVSHM -options SYSVSEM -options SYSVMSG +# System V shared memory and tunable parameters +options SYSVSHM # include support for shared memory +options SHMMAXPGS=1025 # max amount of shared memory pages (4k on i386) +options SHMALL=1025 # max amount of shared memory (bytes) +options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" + # max shared memory segment size (bytes) +options SHMMIN=2 # min shared memory segment size (bytes) +options SHMMNI=33 # max number of shared memory identifiers +options SHMSEG=9 # max shared memory segments per process + +# System V semaphores and tunable parameters +options SYSVSEM # include support for semaphores +options SEMMAP=31 # amount of entries in semaphore map +options SEMMNI=11 # number of semaphore identifiers in the system +options SEMMNS=61 # number of semaphores in the system +options SEMMNU=31 # number of undo structures in the system +options SEMMSL=61 # max number of semaphores per id +options SEMOPM=101 # max number of operations per semop call +options SEMUME=11 # max number of undo entries per process + +# System V message queues and tunable parameters +options SYSVMSG # include support for message queues +options MSGMNB=2049 # max characters per message +options MSGMNI=41 # max number of message queue identifiers +options MSGSEG=2049 # max number of message segments in the system +options MSGSSZ=16 # size of a message segment MUST be power of 2 +options MSGTQL=41 # max amount of messages in the system ##################################################################### @@ -2415,11 +2439,6 @@ options KEY options LOCKF_DEBUG options LOUTB -options MSGMNB=2049 -options MSGMNI=41 -options MSGSEG=2049 -options MSGSSZ=16 -options MSGTQL=41 options NBUF=512 options NETATALKDEBUG options NMBCLUSTERS=1024 @@ -2435,19 +2454,6 @@ options SCSI_NCR_MYADDR=7 options SC_DEBUG_LEVEL options SC_RENDER_DEBUG -options SEMMAP=31 -options SEMMNI=11 -options SEMMNS=61 -options SEMMNU=31 -options SEMMSL=61 -options SEMOPM=101 -options SEMUME=11 -options SHMALL=1025 -options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" -options SHMMAXPGS=1025 -options SHMMIN=2 -options SHMMNI=33 -options SHMSEG=9 options SHOW_BUSYBUFS # List buffers that prevent root unmount options SIMPLELOCK_DEBUG options SI_DEBUG -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 15:27:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id A65B637B479; Tue, 7 Nov 2000 15:27:11 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eA7NRB513683; Tue, 7 Nov 2000 15:27:11 -0800 (PST) Date: Tue, 7 Nov 2000 15:27:11 -0800 From: Alfred Perlstein To: jkh@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Documenting sysV IPC tunables. Message-ID: <20001107152711.H5112@fw.wintelcom.net> References: <20001107145803.G5112@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001107145803.G5112@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Nov 07, 2000 at 02:58:03PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Alfred Perlstein [001107 14:58] wrote: > I have a patch here that I'd like to get into LINT for 4.2, > it _finally_ documents the sysV IPC tunables. > > I'll also be applying this patch to NOTES for -current. Bah, someone beat me for -current, but I like my patch better because it groups the options together with the "include support for" options. I'd like to change NOTES to look like my patch and i'd like to apply it to LINT in 4.x. Any objections? > > Index: LINT > =================================================================== > RCS file: /home/ncvs/src/sys/i386/conf/Attic/LINT,v > retrieving revision 1.749.2.35 > diff -u -u -r1.749.2.35 LINT > --- LINT 2000/10/31 23:16:07 1.749.2.35 > +++ LINT 2000/11/07 22:57:59 > @@ -272,9 +272,33 @@ > # Definition-style interprocess communication, in the form of shared > # memory, semaphores, and message queues, respectively. > # > -options SYSVSHM > -options SYSVSEM > -options SYSVMSG > +# System V shared memory and tunable parameters > +options SYSVSHM # include support for shared memory > +options SHMMAXPGS=1025 # max amount of shared memory pages (4k on i386) > +options SHMALL=1025 # max amount of shared memory (bytes) > +options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" > + # max shared memory segment size (bytes) > +options SHMMIN=2 # min shared memory segment size (bytes) > +options SHMMNI=33 # max number of shared memory identifiers > +options SHMSEG=9 # max shared memory segments per process > + > +# System V semaphores and tunable parameters > +options SYSVSEM # include support for semaphores > +options SEMMAP=31 # amount of entries in semaphore map > +options SEMMNI=11 # number of semaphore identifiers in the system > +options SEMMNS=61 # number of semaphores in the system > +options SEMMNU=31 # number of undo structures in the system > +options SEMMSL=61 # max number of semaphores per id > +options SEMOPM=101 # max number of operations per semop call > +options SEMUME=11 # max number of undo entries per process > + > +# System V message queues and tunable parameters > +options SYSVMSG # include support for message queues > +options MSGMNB=2049 # max characters per message > +options MSGMNI=41 # max number of message queue identifiers > +options MSGSEG=2049 # max number of message segments in the system > +options MSGSSZ=16 # size of a message segment MUST be power of 2 > +options MSGTQL=41 # max amount of messages in the system > > > ##################################################################### > @@ -2415,11 +2439,6 @@ > options KEY > options LOCKF_DEBUG > options LOUTB > -options MSGMNB=2049 > -options MSGMNI=41 > -options MSGSEG=2049 > -options MSGSSZ=16 > -options MSGTQL=41 > options NBUF=512 > options NETATALKDEBUG > options NMBCLUSTERS=1024 > @@ -2435,19 +2454,6 @@ > options SCSI_NCR_MYADDR=7 > options SC_DEBUG_LEVEL > options SC_RENDER_DEBUG > -options SEMMAP=31 > -options SEMMNI=11 > -options SEMMNS=61 > -options SEMMNU=31 > -options SEMMSL=61 > -options SEMOPM=101 > -options SEMUME=11 > -options SHMALL=1025 > -options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" > -options SHMMAXPGS=1025 > -options SHMMIN=2 > -options SHMMNI=33 > -options SHMSEG=9 > options SHOW_BUSYBUFS # List buffers that prevent root unmount > options SIMPLELOCK_DEBUG > options SI_DEBUG > -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 15:32:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 0A5BE37B479; Tue, 7 Nov 2000 15:32:34 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp241.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eA7NWNH69131; Tue, 7 Nov 2000 15:32:23 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001107152711.H5112@fw.wintelcom.net> Date: Tue, 07 Nov 2000 15:32:48 -0800 (PST) From: John Baldwin To: Alfred Perlstein Subject: Re: Documenting sysV IPC tunables. Cc: hackers@FreeBSD.org, jkh@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Nov-00 Alfred Perlstein wrote: > * Alfred Perlstein [001107 14:58] wrote: >> I have a patch here that I'd like to get into LINT for 4.2, >> it _finally_ documents the sysV IPC tunables. >> >> I'll also be applying this patch to NOTES for -current. > > Bah, someone beat me for -current, but I like my patch better > because it groups the options together with the "include support for" > options. Why not reorder what is already in NOTES then rather than cutting out most of the comments? The existing comments in -current are more verbose and helpful to people trying to read it to learn. I don't think this really qualifies as a bug fix, but it is up to Jordan if he'll let you MFC it. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "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 Nov 7 15:35:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9CBB737B4C5; Tue, 7 Nov 2000 15:35:28 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eA7NZSP14249; Tue, 7 Nov 2000 15:35:28 -0800 (PST) Date: Tue, 7 Nov 2000 15:35:27 -0800 From: Alfred Perlstein To: John Baldwin Cc: hackers@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Documenting sysV IPC tunables. Message-ID: <20001107153527.J5112@fw.wintelcom.net> References: <20001107152711.H5112@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from jhb@FreeBSD.ORG on Tue, Nov 07, 2000 at 03:32:48PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * John Baldwin [001107 15:33] wrote: > > On 07-Nov-00 Alfred Perlstein wrote: > > * Alfred Perlstein [001107 14:58] wrote: > >> I have a patch here that I'd like to get into LINT for 4.2, > >> it _finally_ documents the sysV IPC tunables. > >> > >> I'll also be applying this patch to NOTES for -current. > > > > Bah, someone beat me for -current, but I like my patch better > > because it groups the options together with the "include support for" > > options. > > Why not reorder what is already in NOTES then rather than cutting out most of > the comments? The existing comments in -current are more verbose and helpful > to people trying to read it to learn. I don't think this really qualifies as a > bug fix, but it is up to Jordan if he'll let you MFC it. Actually, I'm up for MFC'ing the current set of documentation or applying my patch directly to LINT (and leaving NOTES alone). I'll let Jordan make the call on what he'd like to see in 4.x. I'd really like to see this get done because of what I see on the postrgresql lists and my own experiances not having fun trying to tune for semaphores and shared memory by having to grovel through the kernel source to get a clue as to what each tunable does. It would be a really nice 'feature' to be in 4.2 and not having these things documented almost qualifies as a bug. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 17:16:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 3C75B37B479 for ; Tue, 7 Nov 2000 17:16:23 -0800 (PST) Received: from bellatlantic.net (client-151-198-117-26.nnj.dialup.bellatlantic.net [151.198.117.26]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA22007; Tue, 7 Nov 2000 20:16:02 -0500 (EST) Message-ID: <3A08A951.B9536B7F@bellatlantic.net> Date: Tue, 07 Nov 2000 20:16:01 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Nathan Boeger Cc: "freebsd-hackers@FreeBSD.ORG" Subject: Re: Digi Xem help! References: <3A076622.A12C5979@khmere.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nathan Boeger wrote: > > Sorry if this is the wrong list !! > > Anyway I have a Digi / Xem eisa adapter on 4.1-RELEASE. I have made the > kernel and it see's the card. I have also remade the /dev/ttyD* entries. > > Problem, when I try to access any of the ports I get : > > cu: open (/dev/ttyD00): Device not configured > cu: /dev/ttyD00: Line in use Try to use cua* devices instead of tty*. The tty* devices are for incoming connections, cua* are for outgoing connections. The idea is that if you have a getty listening on tty*, you can still open this port for outgoing connection as cua* and for duration of this connection the tty* port will be transparently locked out. It might be that you have carrier present at this port, so the driver considers it a potentially established outgoing connection and locks out the incoming port. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 17:30:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from linus.dvart.com (linus.dvart.com [64.79.2.3]) by hub.freebsd.org (Postfix) with ESMTP id CB0C437B479 for ; Tue, 7 Nov 2000 17:30:30 -0800 (PST) Received: from dvart.com ([192.168.100.141]) by linus.dvart.com (8.9.3/8.9.3) with ESMTP id RAA28809 for ; Tue, 7 Nov 2000 17:30:29 -0800 Message-ID: <3A08ACB5.FD22CE8@dvart.com> Date: Tue, 07 Nov 2000 17:30:29 -0800 From: bruno schwander X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: close call in a device ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everybody, I am writing a pseudo-device driver (as a kernel module) that needs to be opened in write mode by several processes. The problem I am having is that I do get all the "open" calls when a process opens the device, and I am able to process data written, etc. on a per-process basis; however, when a process closes the device, I do not get a "close" call for each process closing the device. I instead get a close only on the last process closing the device. This is a problem since I need to allocate/free resources for each process accessing the device, at the time a process closes the device. Is there a way to make sure my driver gets all "close" calls ? I could possibly get around this by using timeouts, but the unpredictability of the accessing processes may make this very difficult and suboptimal, so getting the "close" calls would be way better Thank you all for any information on this bruno -- ########################################################################### Bruno Schwander Senior Software Engineer Worldgate Communications, Inc email: bschwand@dvart.com ############################################################################ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 17:57:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 78F2E37B479 for ; Tue, 7 Nov 2000 17:57:09 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.9.3/8.9.3) id RAA00555; Tue, 7 Nov 2000 17:57:02 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200011080157.RAA00555@iguana.aciri.org> Subject: Re: close call in a device ? In-Reply-To: <3A08ACB5.FD22CE8@dvart.com> from bruno schwander at "Nov 7, 2000 5:30:29 pm" To: bschwand@dvart.com (bruno schwander) Date: Tue, 7 Nov 2000 17:57:02 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > when a process closes the device, I do not get a "close" call for each > process closing the device. I instead get a close only on the last > process closing the device. the reason for this is that you might have a process fork() after it has opened the device, and you do not want to get to the device all close calls from all processes generated by the original one, but really only the last instance. The thing is, i think your model (allocating per-user resources on open) is wrong. It cannot protect you from a process forking and then having two instances using the same device. If you want multiple instances of the device, one option could be to use the minor number and really create multiple instances of the device, and open them in exclusive way so you know that there can be only one open per device (you should scan available devices in a similar way as the one is used for scanning pty's). cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- > This is a problem since I need to allocate/free resources for each > process accessing the device, at the time a process closes the device. > > Is there a way to make sure my driver gets all "close" calls ? > > I could possibly get around this by using timeouts, but the > unpredictability of the accessing processes may make this very difficult > and suboptimal, so getting the "close" calls would be way better > > Thank you all for any information on this > > bruno > > -- > > ########################################################################### > > Bruno Schwander > Senior Software Engineer > > Worldgate Communications, Inc > email: bschwand@dvart.com > > ############################################################################ > > > > > > 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 Nov 7 18:24:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from saturn.cs.uml.edu (saturn.cs.uml.edu [129.63.8.2]) by hub.freebsd.org (Postfix) with ESMTP id 5750F37B479 for ; Tue, 7 Nov 2000 18:24:50 -0800 (PST) Received: (from acahalan@localhost) by saturn.cs.uml.edu (8.11.0/8.10.0) id eA82Nxf392522; Tue, 7 Nov 2000 21:23:59 -0500 (EST) Date: Tue, 7 Nov 2000 21:23:59 -0500 (EST) Message-Id: <200011080223.eA82Nxf392522@saturn.cs.uml.edu> From: "Albert D. Cahalan" To: hackers@FreeBSD.ORG, roam@orbitel.bg, keramida@ceid.upatras.gr Subject: Re: umask(2) and -Wconversion Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Pentchev writes: > As you can see, I'm passing a short i as a first arg, a short f > as second, and a short b as third; and yet, gcc with BDECFLAGS > complains about ALL the arguments! Yes, no kidding. That's what you asked gcc to do. `-Wconversion' Warn if a prototype causes a type conversion that is different from what would happen to the same argument in the absence of a prototype. This includes conversions of fixed point to floating and vice versa, and conversions changing the width or signedness of a fixed point argument except when the same as the default promotion. The C language is crufty. In the absense of a prototype, "short" is promoted to "int". You wanted to be warned about that; you got it! To avoid the warning, avoid passing anything but "int" and "double". Maybe "long" is OK too, I forget. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 18:43:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from linus.dvart.com (linus.dvart.com [64.79.2.3]) by hub.freebsd.org (Postfix) with ESMTP id 2866A37B479 for ; Tue, 7 Nov 2000 18:43:10 -0800 (PST) Received: from dvart.com ([192.168.100.141]) by linus.dvart.com (8.9.3/8.9.3) with ESMTP id SAA29215 for ; Tue, 7 Nov 2000 18:43:09 -0800 Message-ID: <3A08BDBD.575A6AA4@dvart.com> Date: Tue, 07 Nov 2000 18:43:09 -0800 From: bruno schwander X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Re: close call in a device ? References: <200011080157.RAA00555@iguana.aciri.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The reason I am doing this, is precisely because I need to virtualize accesses from several processes to _one_ _predefined_ device. I have no control over that device name from the client process point of view, so I can not have multiple devices. I pretty much need to be able to lie to the process, telling it that it has full control of the device it wants, and actually allow other processes to open and use the device in the same way at the same time. Did I miss something in your suggestion ? Or were you suggesting that I can create same name device entries, differing only by their minor number ? But then I still hit the problem that the processes are maybe not going to open the device in exclusive mode ? > the reason for this is that you might have a process fork() after > it has opened the device, and you do not want to get to the > device all close calls from all processes generated by the original > one, but really only the last instance. > > The thing is, i think your model (allocating per-user resources on > open) is wrong. It cannot protect you from a process forking > and then having two instances using the same device. > I can walk the process tree to figure whose parent process allocated the resource and thus use the same resource for the child, so this is not a problem (I think...). Besides, in my context, I doubt the process will fork after opening the device. > If you want multiple instances of the device, one option could be > to use the minor number and really create multiple instances > of the device, and open them in exclusive way so you know that > there can be only one open per device (you should scan available > devices in a similar way as the one is used for scanning pty's). > > cheers > luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 19: 1: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77]) by hub.freebsd.org (Postfix) with ESMTP id 80EE037B479 for ; Tue, 7 Nov 2000 19:01:01 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eA835rF34155; Tue, 7 Nov 2000 19:05:56 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011080305.eA835rF34155@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: bruno schwander Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: close call in a device ? In-reply-to: Your message of "Tue, 07 Nov 2000 18:43:09 PST." <3A08BDBD.575A6AA4@dvart.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Nov 2000 19:05:53 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The reason I am doing this, is precisely because I need to virtualize > accesses from several processes to _one_ _predefined_ device. I have no > control over that device name from the client process point of view, so I > can not have multiple devices. I pretty much need to be able to lie to > the process, telling it that it has full control of the device it wants, > and actually allow other processes to open and use the device in the same > way at the same time. If I understand you correctly, you have multiple processes all of which are going to try to open /dev/foo, and you want them to behave as though they have each opened a unique device? You can't do this with FreeBSD, or with many other Unixes. Arguably, this is a defect with the device model. If you are trying to fake up concurrent access to a device, and the client processes are only going to read and write (no ioctls) to this device, then you can use a fifo and a multiplexor process. Alternatively, and this would be recommended; fix the client program. -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 19: 5:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id D0E7737B479 for ; Tue, 7 Nov 2000 19:05:27 -0800 (PST) Received: (qmail 64784 invoked by uid 1001); 8 Nov 2000 13:05:19 +1000 X-Posted-By: GBA-Post 2.06 15-Sep-2000 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Wed, 08 Nov 2000 13:05:19 +1000 From: Greg Black To: "Albert D. Cahalan" Cc: hackers@FreeBSD.ORG, roam@orbitel.bg, keramida@ceid.upatras.gr Subject: Re: umask(2) and -Wconversion References: <200011080223.eA82Nxf392522@saturn.cs.uml.edu> In-reply-to: <200011080223.eA82Nxf392522@saturn.cs.uml.edu> of Tue, 07 Nov 2000 21:23:59 EST Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Albert D. Cahalan" writes: > The C language is crufty. In the absense of a prototype, "short" is > promoted to "int". You wanted to be warned about that; you got it! > > To avoid the warning, avoid passing anything but "int" and "double". > Maybe "long" is OK too, I forget. I'm not sure which C language you're talking about here, but I'll assume it's C89. In that language, in the absence of a prototype, (and in K&R C), `int', `long', `double' and pointer types are not promoted; but signed or unsigned `char', `short', and `int' bit-fields are promoted; `float' is promoted. -- Greg Black To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 20:42: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id A9FD237B4C5 for ; Tue, 7 Nov 2000 20:41:59 -0800 (PST) Received: from FreeBSD.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id UAA58626; Tue, 7 Nov 2000 20:40:26 -0800 (PST) (envelope-from DougB@FreeBSD.org) Message-ID: <3A08D939.4998F9E1@FreeBSD.org> Date: Tue, 07 Nov 2000 20:40:25 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Max Khon Cc: Don Lewis , andrew@ugh.net.au, hackers@FreeBSD.org Subject: Re: daemon() References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Max Khon wrote: > > hi, there! > > On Tue, 7 Nov 2000, Don Lewis wrote: > > > } > what is FD 4? > > } > > } I can't reproduce this? Does it always happen? > > > > It might be something that the shell forgets to close, so it will be > > dependent on which shell you use. > > exactly. this does not happen if I run this program from tcsh > (but does if I run from bash 1.14.7(1) built from ports > thanks! No one with any brains uses bash 1 for anything anymore. If you're interested in testing whether or not a version of bash has a given bug, use the latest bash 2. Doug -- Life is an essay test. Long form. Spelling counts. Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 20:47:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id EB34F37B479 for ; Tue, 7 Nov 2000 20:47:46 -0800 (PST) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 70A42A82B; Wed, 8 Nov 2000 15:47:40 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 6CF6F5465; Wed, 8 Nov 2000 14:47:40 +1000 (EST) Date: Wed, 8 Nov 2000 14:47:40 +1000 (EST) From: andrew@ugh.net.au To: "Albert D. Cahalan" Cc: hackers@FreeBSD.ORG, roam@orbitel.bg, keramida@ceid.upatras.gr Subject: Re: umask(2) and -Wconversion In-Reply-To: <200011080223.eA82Nxf392522@saturn.cs.uml.edu> Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Nov 2000, Albert D. Cahalan wrote: > of a fixed point argument except when the same as the default > promotion. > The C language is crufty. In the absense of a prototype, "short" is > promoted to "int". You wanted to be warned about that; you got it! short going to int would be a default promotion and so shouldn't produce a warning. > To avoid the warning, avoid passing anything but "int" and "double". > Maybe "long" is OK too, I forget. No the secret is not to have any function arguments that aren't ints, doubles etc. Its the cast from the default type on the stack to the non default type to get in the function that produces the warning I think. Take this example code: void foo(int i); void bar(short i); int main() { short s; foo(s); bar(s); return(0); } void foo(int i) { } void bar(short i) { } When compiled with -Wconversion you get: test10.c: In function `main': test10.c:10: warning: passing arg 1 of `bar' with different width due to prototype Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 21:28: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gray.westgate.gr (gray.westgate.gr [212.205.119.66]) by hub.freebsd.org (Postfix) with ESMTP id 2B21037B479 for ; Tue, 7 Nov 2000 21:28:02 -0800 (PST) Received: (from charon@localhost) by gray.westgate.gr (8.11.1/8.11.1) id eA85QUi58657; Wed, 8 Nov 2000 07:26:30 +0200 (EET) Date: Wed, 8 Nov 2000 07:26:30 +0200 From: Giorgos Keramidas To: andrew@ugh.net.au Cc: "Albert D. Cahalan" , hackers@FreeBSD.ORG, roam@orbitel.bg Subject: Re: umask(2) and -Wconversion Message-ID: <20001108072630.A58596@gray.westgate.gr> References: <200011080223.eA82Nxf392522@saturn.cs.uml.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from andrew@ugh.net.au on Wed, Nov 08, 2000 at 02:47:40PM +1000 X-PGP-Fingerprint: 3A 75 52 EB F1 58 56 0D - C5 B8 21 B6 1B 5E 4A C2 X-URL: http://students.ceid.upatras.gr/~keramida/index.html Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 08, 2000 at 02:47:40PM +1000, andrew@ugh.net.au wrote: > > On Tue, 7 Nov 2000, Albert D. Cahalan wrote: >> >> The C language is crufty. In the absense of a prototype, "short" is >> promoted to "int". You wanted to be warned about that; you got it! > > short going to int would be a default promotion and so shouldn't produce a > warning. Agreed. But, obviously, this is not what happens when I compile my test program posted earlier in this thread: 1 #include 2 3 #define VALUE 0 4 5 int func (short x); 6 7 int main (void) 8 { 9 int var = 10; 10 11 func(VALUE); 12 return 0; 13 } 14 15 int func (short var) 16 { 17 printf("var: %d\n", var); 18 return 0; 19 } Even though I have a cast at line 9 that one would expect to inhibit such a warning, the warning remains. This is what happens when one tries to compile programs that use umask(2) with -Wconversion. Macros defined in header, much like VALUE above are passed to a function that expects a `short', and the warning is issued. My original question was if this is not behavior that should be considered buggy, since the size of VALUE has not been determined to be equal to sizeof(int) when the #define occurs, or has it? - giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 22:39: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 64A9737B479; Tue, 7 Nov 2000 22:39:00 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eA86e0P41395; Tue, 7 Nov 2000 22:40:00 -0800 (PST) (envelope-from kris) Date: Tue, 7 Nov 2000 22:39:59 -0800 From: Kris Kennaway To: Konrad Heuer Cc: freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: TCPDUMP patch v1.1 and AppleTalk Message-ID: <20001107223959.B41350@citusc17.usc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="24zk1gE8NUlDmwG9" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from kheuer@gwdu60.gwdg.de on Tue, Nov 07, 2000 at 01:56:21PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --24zk1gE8NUlDmwG9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Nov 07, 2000 at 01:56:21PM +0100, Konrad Heuer wrote: > After patching and installing, tcpdump can't be used anymore since it puts > very heavy load onto the network via xl0 and AppleTalk broadcast messages > (one message each 0.2 ms). Sorry, in the moment I don't know more details > ... tcpdump shouldn't be sending any appletalk packets, I thought (I may be wrong, never used it on an appletalk network). Are you sure this is the problem? Kris --24zk1gE8NUlDmwG9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoI9T8ACgkQWry0BWjoQKUG8QCcD+cR/YwWPe+eDTTsUZfv0ldu yJQAoLDxYY4xSxE04sbvoH8V6GPWHL5R =CSXv -----END PGP SIGNATURE----- --24zk1gE8NUlDmwG9-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 23:37: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id DC6D937B4C5 for ; Tue, 7 Nov 2000 23:36:56 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.9.3/8.9.3) id XAA02080; Tue, 7 Nov 2000 23:36:55 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200011080736.XAA02080@iguana.aciri.org> Subject: Re: close call in a device ? In-Reply-To: <3A08BDBD.575A6AA4@dvart.com> from bruno schwander at "Nov 7, 2000 6:43: 9 pm" To: bschwand@dvart.com (bruno schwander) Date: Tue, 7 Nov 2000 23:36:55 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > The reason I am doing this, is precisely because I need to virtualize accesses > from several processes to _one_ _predefined_ device. I have no control over that > device name from the client process point of view, so I can not have multiple > devices. I pretty much need to be able to lie to the process, telling it that it > has full control of the device it wants, and actually allow other processes to > open and use the device in the same way at the same time. you could do something like this: + open allocates a descriptor which stores the PID of the process requesting access to the "device" + each I/O operation uses the descriptor matching the PID passed to the read/write/ioctl + you could implement an ioctl() to dispose the storage, a "well behaved" process would have to invoke this ioctl before terminating; + and a timeout as you suggested could be used to purge entries that have been idle for some time, or you could also purge them basing on usage patterns assumning there are clearly identifiable ones. > Did I miss something in your suggestion ? Or were you suggesting that I can > create same name device entries, differing only by their minor number ? But then you cannot use the same name unless the entries are in different directories. My suggestion was to use /dev/foo.00 /dev/foo.01 /dev/foo.02 and so on. cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 7 23:43:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web3502.mail.yahoo.com (web3502.mail.yahoo.com [204.71.203.69]) by hub.freebsd.org (Postfix) with SMTP id C578537B479 for ; Tue, 7 Nov 2000 23:43:27 -0800 (PST) Message-ID: <20001108074327.28774.qmail@web3502.mail.yahoo.com> Received: from [196.7.146.6] by web3502.mail.yahoo.com; Tue, 07 Nov 2000 23:43:27 PST Date: Tue, 7 Nov 2000 23:43:27 -0800 (PST) From: Jacques Fourie Subject: Re: kernel stack size? To: Matt Dillon Cc: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Thanks for your reply. I have two other questions regarding this matter. Would it be possible to extend the kernel stack? The reason is that some of the crypto and hashing algorithms use relatively large contexts which for performance reasons are currently allocated on the stack. If this is not a good idea, would it be possible to somehow allocate a block of memory on the heap and use this as a stack in my interrupt routine? regards, jacques __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one Place. http://shopping.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 0: 9:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 20F5C37B4C5 for ; Wed, 8 Nov 2000 00:09:23 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eA886Ju97762; Wed, 8 Nov 2000 00:06:19 -0800 (PST) (envelope-from dillon) Date: Wed, 8 Nov 2000 00:06:19 -0800 (PST) From: Matt Dillon Message-Id: <200011080806.eA886Ju97762@earth.backplane.com> To: Jacques Fourie Cc: freebsd-hackers@freebsd.org Subject: Re: kernel stack size? References: <20001108074327.28774.qmail@web3502.mail.yahoo.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Hi : :Thanks for your reply. I have two other questions :regarding this matter. : :Would it be possible to extend the kernel stack? :The reason is that some of the crypto and hashing :algorithms use relatively large contexts which for :performance reasons are currently allocated on the :stack. : :If this is not a good idea, would it be possible to :somehow allocate a block of memory on the heap and use :this as a stack in my interrupt routine? : :regards, :jacques The simple answer is, no, it is not possible to extend the kernel stack. You have to preallocate a block of memory in the device open routine and associate it with your softc structure. Your interrupt can reference the memory that way. If the memory requirements are dynamic in nature, the interrupt is the wrong place to be trying to allocate and free memory. Preallocation will not perform any worse then declaring an array on the stack in terms of performance. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 0:21:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web3504.mail.yahoo.com (web3504.mail.yahoo.com [204.71.203.71]) by hub.freebsd.org (Postfix) with SMTP id 3867D37B479 for ; Wed, 8 Nov 2000 00:21:36 -0800 (PST) Message-ID: <20001108082135.21027.qmail@web3504.mail.yahoo.com> Received: from [196.7.146.6] by web3504.mail.yahoo.com; Wed, 08 Nov 2000 00:21:35 PST Date: Wed, 8 Nov 2000 00:21:35 -0800 (PST) From: Jacques Fourie Subject: Re: kernel stack size? To: Matt Dillon Cc: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would it be possible to pre-allocate a block of memory and then "switch" stacks in my interrupt routine? This may be far off, but my only other option is going through ~10000 lines of code and examining all places where local variables are declared. If I could somehow do this in a different way, it would really help a lot. regards, jacques __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one Place. http://shopping.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 0:27:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id CF0F937B479 for ; Wed, 8 Nov 2000 00:27:09 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eA88R8g12715; Wed, 8 Nov 2000 01:27:08 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA27696; Wed, 8 Nov 2000 01:27:08 -0700 (MST) Message-Id: <200011080827.BAA27696@harmony.village.org> To: Jacques Fourie Subject: Re: kernel stack size? Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 08 Nov 2000 00:21:35 PST." <20001108082135.21027.qmail@web3504.mail.yahoo.com> References: <20001108082135.21027.qmail@web3504.mail.yahoo.com> Date: Wed, 08 Nov 2000 01:27:08 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001108082135.21027.qmail@web3504.mail.yahoo.com> Jacques Fourie writes: : Would it be possible to pre-allocate a block of memory : and then "switch" stacks in my interrupt routine? This : may be far off, but my only other option is going : through ~10000 lines of code and examining all places : where local variables are declared. If I could somehow : do this in a different way, it would really help a : lot. 10k lines in an interrupt routine sounds to be way more work than you want to do in an interrupt routine. Maybe you could use a work queue and deal with it that way. There isn't much I can do to help you with the local variable issue, since it sounds like this code is just flat ill suited for the kernel. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 0:35:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web3506.mail.yahoo.com (web3506.mail.yahoo.com [204.71.203.73]) by hub.freebsd.org (Postfix) with SMTP id 3ADBE37B479 for ; Wed, 8 Nov 2000 00:35:16 -0800 (PST) Message-ID: <20001108083511.25177.qmail@web3506.mail.yahoo.com> Received: from [196.7.146.6] by web3506.mail.yahoo.com; Wed, 08 Nov 2000 00:35:11 PST Date: Wed, 8 Nov 2000 00:35:11 -0800 (PST) From: Jacques Fourie Subject: Re: kernel stack size? To: Warner Losh Cc: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Warner Losh wrote: > 10k lines in an interrupt routine sounds to be way > more work than you > want to do in an interrupt routine. Maybe you could > use a work queue > and deal with it that way. There isn't much I can The ~10k lines of code is in a software interrupt (netisr) routine. In the hardware interrupt (ether_input() ) the packets are queued and the software interrupt scheduled. All the work is done in the software interrupt routine. Sorry if I did not explain this clearly before. Does everything discussed so far still apply? If so, I can't see any way to do this differently right now. Back to the drawing boards, I guess. jacques __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one Place. http://shopping.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 0:41: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77]) by hub.freebsd.org (Postfix) with ESMTP id 86E8B37B479 for ; Wed, 8 Nov 2000 00:41:04 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eA88kNF00891; Wed, 8 Nov 2000 00:46:24 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011080846.eA88kNF00891@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jacques Fourie Cc: Warner Losh , freebsd-hackers@freebsd.org Subject: Re: kernel stack size? In-reply-to: Your message of "Wed, 08 Nov 2000 00:35:11 PST." <20001108083511.25177.qmail@web3506.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Nov 2000 00:46:23 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > --- Warner Losh wrote: > > > 10k lines in an interrupt routine sounds to be way > > more work than you > > want to do in an interrupt routine. Maybe you could > > use a work queue > > and deal with it that way. There isn't much I can > > The ~10k lines of code is in a software interrupt > (netisr) routine. In the hardware interrupt > (ether_input() ) the packets are queued and the > software interrupt scheduled. All the work is done in > the software interrupt routine. Sorry if I did not > explain this clearly before. Does everything discussed > so far still apply? If so, I can't see any way to do > this differently right now. Back to the drawing > boards, I guess. Basically, large stack variables are just wrong, and particularly wrong in anything called from interrupt context (that applies to netisrs as well). It should be pretty straightforward to move your large variables elsewhere though, and a salutory lesson to you for next time. 8) Note also that it's OK to call malloc if your storage is relatively persistent. Without knowing why you need so much space, it's hard to offer you more constructive suggestions though. Feel free to discuss at more length; many of us have been down this path already and can probably save you a lot of headscratching. -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 0:45: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 64B3337B479; Wed, 8 Nov 2000 00:45:05 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id C9E8F5730D; Wed, 8 Nov 2000 02:45:07 -0600 (CST) Date: Wed, 8 Nov 2000 02:45:07 -0600 From: "Michael C . Wu" To: hackers@freebsd.org Cc: obrien@freebsd.org, asmodai@freebsd.org Subject: import of CITRUS code Message-ID: <20001108024507.A71687@peorth.iteration.net> Reply-To: "Michael C . Wu" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello guys, I have been working on merging the CITRUS locale/wchar/iconv patches into -current. Here is the patch, please test and comment. http://iteration.net/~keichii/src.diff.keichii.citrus.20001108.bz2 Thanks, -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 1:18:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web3504.mail.yahoo.com (web3504.mail.yahoo.com [204.71.203.71]) by hub.freebsd.org (Postfix) with SMTP id 5003237B4C5 for ; Wed, 8 Nov 2000 01:18:30 -0800 (PST) Message-ID: <20001108091829.24085.qmail@web3504.mail.yahoo.com> Received: from [196.7.146.6] by web3504.mail.yahoo.com; Wed, 08 Nov 2000 01:18:29 PST Date: Wed, 8 Nov 2000 01:18:29 -0800 (PST) From: Jacques Fourie Subject: Re: kernel stack size? To: Mike Smith Cc: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First of all, I would like to say a big thanks for all of the replies I got so far. I really appreciate it. Here is a more detailed description of what the code does. It is for a commercial IPsec product. I know that IPsec is available in FreeBSD, but this started long before KAME was available. Using KAME is not an option for me, so I'm stuck with this. The basic idea is to modify the ether_input() and ether_output_frame() routines to add hooks for IPsec processing. In ether_input() mbufs are placed on a queue in a similar way to that done in ether_demux(). The reason that it is done here is that we want to operate in a "bump-in-the-wire" mode. This basically boils down to bridging + IPsec. After queuing the mbuf a netisr is scheduled. Inside this interrupt routine the mbuf is passed on to the IPsec processing code. The IPsec processing code performs all the transforms required on the packet (crypto + hashing etc.) Inside this code some of the routines use large local variables (contexts for the crypto and hashing etc.) I can malloc these variables and live with the performance loss or pre-alloc as previouslu discussed. Once the IPsec processing is finished, another function is called to send packets out on the interface in question. This is where another problem pitches up. The function called to begin IPsec processing on the packet only returns once the packet has been sent out on the wire eventually. This leads to a deeply recursed call stack which I think is part of the problem. In routine operation this is about 20 function calls long which leaves very little space for local variables, if at all. Any ideas (except for re-writes :) )? regards, jacques __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one Place. http://shopping.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 1:22:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id D3B5637B479 for ; Wed, 8 Nov 2000 01:22:31 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eA89MMQ98018; Wed, 8 Nov 2000 01:22:22 -0800 (PST) (envelope-from dillon) Date: Wed, 8 Nov 2000 01:22:22 -0800 (PST) From: Matt Dillon Message-Id: <200011080922.eA89MMQ98018@earth.backplane.com> To: Jacques Fourie Cc: freebsd-hackers@freebsd.org Subject: Re: kernel stack size? References: <20001108082135.21027.qmail@web3504.mail.yahoo.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : :Would it be possible to pre-allocate a block of memory :and then "switch" stacks in my interrupt routine? This :may be far off, but my only other option is going :through ~10000 lines of code and examining all places :where local variables are declared. If I could somehow :do this in a different way, it would really help a :lot. : :regards, :jacques I think you are stuck. I would transplant most of the code into a user level process and have the interrupt and device driver just deal with getting the data to and from the user process. You can theoretically increase UPAGES in /usr/src/sys/i386/include/param.h but I dunno if that would work, and it would increase the size of every kernel stack for every process in the system. I get the feeling that your code eats more then just a few kilobytes of stack. It doesn't sound like something that belongs in the kernel. The only other choice would be to rewrite the code into a form suitable for the kernel's smaller stack. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 1:26:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id E86FF37B479 for ; Wed, 8 Nov 2000 01:26:11 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eA89QBl98066; Wed, 8 Nov 2000 01:26:11 -0800 (PST) (envelope-from dillon) Date: Wed, 8 Nov 2000 01:26:11 -0800 (PST) From: Matt Dillon Message-Id: <200011080926.eA89QBl98066@earth.backplane.com> To: hackers@freebsd.org Subject: VXLOCK Deadlock against self ? Anyone have any ideas? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is quite odd. Anybody have any ideas? (kgdb) back #0 mi_switch () at machine/globals.h:119 #1 0xc0167711 in tsleep (ident=0xe19418c0, priority=8, wmesg=0xc0291cfd "vget", timo=0) at ../../kern/kern_synch.c:467 #2 0xc0190193 in vget (vp=0xe19418c0, flags=393216, p=0xdca87780) at ../../kern/vfs_subr.c:1368 #3 0xc023c2ba in vm_object_reference (object=0xe1974960) at ../../vm/vm_object.c:251 #4 0xc022ccbc in ffs_write (ap=0xdca95c00) at ../../ufs/ufs/ufs_readwrite.c:399 #5 0xc0242a33 in vnode_pager_generic_putpages (vp=0xe19418c0, m=0xdca95d10, bytecount=65536, flags=1, rtvals=0xdca95ca4) at vnode_if.h:363 #6 0xc022d5ca in ffs_putpages (ap=0xdca95c68) at ../../ufs/ufs/ufs_readwrite.c:686 #7 0xc024288e in vnode_pager_putpages (object=0xe1974960, m=0xdca95d10, count=16, sync=1, rtvals=0xdca95ca4) at vnode_if.h:1126 #8 0xc023f8b3 in vm_pageout_flush (mc=0xdca95d10, count=16, flags=1) at ../../vm/vm_pager.h:145 #9 0xc023c997 in vm_object_page_clean (object=0xe1974960, start=0, end=0, flags=1) at ../../vm/vm_object.c:655 #10 0xc023c53b in vm_object_terminate (object=0xe1974960) at ../../vm/vm_object.c:425 #11 0xc019060e in vclean (vp=0xe19418c0, flags=8, p=0xdca87780) at ../../kern/vfs_subr.c:1669 ---Type to continue, or q to quit--- #12 0xc019088b in vgonel (vp=0xe19418c0, p=0xdca87780) at ../../kern/vfs_subr.c:1840 #13 0xc0190810 in vrecycle (vp=0xe19418c0, inter_lkp=0x0, p=0xdca87780) at ../../kern/vfs_subr.c:1795 #14 0xc022f061 in ufs_inactive (ap=0xdca95f04) at ../../ufs/ufs/ufs_inode.c:100 #15 0xc02341a9 in ufs_vnoperate (ap=0xdca95f04) at ../../ufs/ufs/ufs_vnops.c:2285 #16 0xc01903a9 in vput (vp=0xe19418c0) at vnode_if.h:794 #17 0xc0227e64 in handle_workitem_remove (dirrem=0xc1c42020) at ../../ufs/ffs/ffs_softdep.c:2670 #18 0xc022554d in softdep_process_worklist (matchmnt=0x0) at ../../ufs/ffs/ffs_softdep.c:559 #19 0xc018fc4f in sched_sync () at ../../kern/vfs_subr.c:1034 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 1:35:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id C9B2A37B479 for ; Wed, 8 Nov 2000 01:35:48 -0800 (PST) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 7615EA82B; Wed, 8 Nov 2000 20:35:48 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 6F47E5465; Wed, 8 Nov 2000 19:35:48 +1000 (EST) Date: Wed, 8 Nov 2000 19:35:48 +1000 (EST) From: andrew@ugh.net.au To: Giorgos Keramidas Cc: "Albert D. Cahalan" , hackers@FreeBSD.ORG, roam@orbitel.bg Subject: Re: umask(2) and -Wconversion In-Reply-To: <20001108072630.A58596@gray.westgate.gr> Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The #defines dont matter as cc never sees them so line 11 is seen as func(0) 0 will be an int by default. When this call is made a 32 bit int with a value of 0 will be pushed onto the stack. When func is executed this 32 bit value is cast to a 16 bit short and this causes a warning to be emitted. Even if line 11 was func((short)0) then the 16 bit 0 would be promoted to a 32 bit 0 as its pushed on the stack and the same problem would occur. I think anyway...as I said earlier I haven't actually loooked at the gcc source. Andrew On Wed, 8 Nov 2000, Giorgos Keramidas wrote: > Agreed. But, obviously, this is not what happens when I compile my test > program posted earlier in this thread: > > 1 #include > 2 > 3 #define VALUE 0 > 4 > 5 int func (short x); > 6 > 7 int main (void) > 8 { > 9 int var = 10; > 10 > 11 func(VALUE); > 12 return 0; > 13 } > 14 > 15 int func (short var) > 16 { > 17 printf("var: %d\n", var); > 18 return 0; > 19 } > > Even though I have a cast at line 9 that one would expect to inhibit There is? > such a warning, the warning remains. This is what happens when one > tries to compile programs that use umask(2) with -Wconversion. Macros umask is taking a 16 bit number off a 32 bit stack... > My original question was if this is not behavior that should be > considered buggy, since the size of VALUE has not been determined to be > equal to sizeof(int) when the #define occurs, or has it? No it has. It is compiled in as a 32bit int unless you qualify it. None the less I dont think a warning should be emitted in these cases, that is when it leaves one function as 16bit and arrives at another as 16bit. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 1:39:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 42B2937B479; Wed, 8 Nov 2000 01:39:18 -0800 (PST) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JWAM5CI760000YLB@research.kpn.com>; Wed, 8 Nov 2000 10:39:15 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Wed, 08 Nov 2000 10:39:14 +0100 Content-return: allowed Date: Wed, 08 Nov 2000 10:39:13 +0100 From: "Koster, K.J." Subject: RE: daemon() To: 'Doug Barton' Cc: 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D79C7@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > No one with any brains uses bash 1 for anything > anymore. > Then why is it there? To help up the port count? If it's not good, it should be nuked, IMHO. Kees Jan PS. Interesting to use the words "nuke" and "humble" in the same sentence. I should go into politics. ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 2: 3:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.kyx.net (cr95838-b.crdva1.bc.wave.home.com [24.113.50.147]) by hub.freebsd.org (Postfix) with ESMTP id E909437B479; Wed, 8 Nov 2000 02:03:55 -0800 (PST) Received: from smp.kyx.net (unknown [10.22.22.45]) by mail.kyx.net (Postfix) with SMTP id 479291DC03; Wed, 8 Nov 2000 02:06:25 -0800 (PST) From: Dragos Ruiu Organization: kyx.net To: Kris Kennaway , Konrad Heuer Subject: Re: TCPDUMP patch v1.1 and AppleTalk Date: Wed, 8 Nov 2000 02:00:40 -0800 X-Mailer: KYX-CP/M [version core00-mail-92] Content-Type: text/plain Cc: freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG References: <20001107223959.B41350@citusc17.usc.edu> In-Reply-To: <20001107223959.B41350@citusc17.usc.edu> MIME-Version: 1.0 Message-Id: <0011080203080F.00551@smp.kyx.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 07 Nov 2000, Kris Kennaway wrote: > > On Tue, Nov 07, 2000 at 01:56:21PM +0100, Konrad Heuer wrote: > > > After patching and installing, tcpdump can't be used anymore since it puts > > very heavy load onto the network via xl0 and AppleTalk broadcast messages > > (one message each 0.2 ms). Sorry, in the moment I don't know more details > > ... > > tcpdump shouldn't be sending any appletalk packets, I thought (I may > be wrong, never used it on an appletalk network). Are you sure this is > the problem? I've never run this kind of a scenario here so I'm speaking from a vacuum of knowledge and pure conjecture... ;-) but could it be generating packets through name resolutions.... ??? Does it still generate the packets with -n ? cheers, --dr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 2: 4:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gwdu60.gwdg.de (gwdu60.gwdg.de [134.76.98.60]) by hub.freebsd.org (Postfix) with ESMTP id 7EECB37B479; Wed, 8 Nov 2000 02:04:44 -0800 (PST) Received: from localhost (kheuer@localhost) by gwdu60.gwdg.de (8.9.3/8.9.3) with ESMTP id LAA05953; Wed, 8 Nov 2000 11:04:42 +0100 (CET) (envelope-from kheuer@gwdu60.gwdg.de) Date: Wed, 8 Nov 2000 11:04:42 +0100 (CET) From: Konrad Heuer To: Kris Kennaway Cc: freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: TCPDUMP patch v1.1 and AppleTalk In-Reply-To: <20001107223959.B41350@citusc17.usc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Nov 2000, Kris Kennaway wrote: > On Tue, Nov 07, 2000 at 01:56:21PM +0100, Konrad Heuer wrote: > > > After patching and installing, tcpdump can't be used anymore since it puts > > very heavy load onto the network via xl0 and AppleTalk broadcast messages > > (one message each 0.2 ms). Sorry, in the moment I don't know more details > > ... > > tcpdump shouldn't be sending any appletalk packets, I thought (I may > be wrong, never used it on an appletalk network). Are you sure this is > the problem? > > Kris > Well, I don't know exactly what happens but I seems to be more complex than I thought first. It doesn't happen each time I start tcpdump but when some circumstances meet which I don't know my FreeBSD host begins to flood the network with AppelTalk broadcast requests as long as tcpdump keeps running. Killing tcpdump kills this flooding, too. I've never observed such a situation before I applied the last patch, and I use tcpdump frequently to analyze the one or other problem. On the other hand, our network environment isn't static, of course, and I can't be sure about other things that may have been changed from day to day. Konrad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 2:42:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id BC38137B479 for ; Wed, 8 Nov 2000 02:42:19 -0800 (PST) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id MAA20108; Wed, 8 Nov 2000 12:41:43 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 20002; Wed Nov 8 12:41:16 2000 Message-ID: <3A091543.4F917C51@cequrux.com> Date: Wed, 08 Nov 2000 10:56:35 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dan Nelson Cc: Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: Help writing a screen saver module References: <3A06B7A7.7665C46A@cequrux.com> <20001107144202.B4569@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Nelson wrote: > > You can make it look like you're switched to vty 0, by making your > screen_saver() function simply copy the contents of vty 0 to screen > memory on every update. Just make sure both vtys are the same size > first... Ok, I'll try that approach and see if I can get it to work. Thanks for the help guys! gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 3: 7:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id F18BD37B4C5; Wed, 8 Nov 2000 03:07:10 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id RAA63472; Wed, 8 Nov 2000 17:06:42 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 8 Nov 2000 17:06:42 +0600 (NS) From: Max Khon To: "Koster, K.J." Cc: "'Doug Barton'" , "'FreeBSD Hackers mailing list'" Subject: RE: daemon() In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D79C7@l04.research.kpn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Wed, 8 Nov 2000, Koster, K.J. wrote: > > No one with any brains uses bash 1 for anything > > anymore. > Then why is it there? To help up the port count? If it's not good, it should > be nuked, IMHO. people still use it because it is smaller obrien has already tried to remove it once (in Mar 1999) as for me -- I do not try to hunt bugs in bash1 and do not blame it. my question was about unclosed pipe /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 3:20: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 27E2C37B479 for ; Wed, 8 Nov 2000 03:19:58 -0800 (PST) Received: from newsguy.com (p14-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.79]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id UAA15323; Wed, 8 Nov 2000 20:19:32 +0900 (JST) Message-ID: <3A093663.23578211@newsguy.com> Date: Wed, 08 Nov 2000 20:17:55 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Jacques Fourie Cc: Matt Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: kernel stack size? References: <20001108082135.21027.qmail@web3504.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jacques Fourie wrote: > > Would it be possible to pre-allocate a block of memory > and then "switch" stacks in my interrupt routine? This > may be far off, but my only other option is going > through ~10000 lines of code and examining all places > where local variables are declared. If I could somehow > do this in a different way, it would really help a > lot. Don't do that during interrupt. Queue the data to be processed by a kernel thread later. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@world.wide.bsdconspiracy.net He has been convicted of criminal possession of a clue with intent to distribute. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 6: 7:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 804CF37B479 for ; Wed, 8 Nov 2000 06:07:23 -0800 (PST) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.1/8.11.0) id eA8E7MI85808 for hackers@freebsd.org; Wed, 8 Nov 2000 15:07:22 +0100 (CET) (envelope-from asmodai) Date: Wed, 8 Nov 2000 15:07:22 +0100 From: Jeroen Ruigrok van der Werven To: hackers@freebsd.org Subject: PSE/PAE support Message-ID: <20001108150722.L80971@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Reading some documents and sources I came to the following conclusion: We support 4 Kbyte pages and 4 Mbyte pages, but we do not support 2 Mbyte pages. On IA-32 at least. Is there a reason to? I could understand that some people would prefer 2 Mbyte pages in some situations. But looking at pmap.c I see we only test CPUID_PSE and don't use CPUID_PAE anywhere. Since pmap.c is in a MD location it wouldn't be hard to extend the code to do this. Would this needlessly complicate a lot of things in our code? i could envision that our VM and related code should be usable no matter what the page size is. This will certainly improve future ports to new architectures with different page sizes. Are there even more arguments in favor or against? I'd like to hear some thoughts. :) -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Wisdom is the difference between knowledge and experience... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 6:41:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.o-yo.com (unknown [202.109.110.102]) by hub.freebsd.org (Postfix) with SMTP id E386B37B4C5 for ; Wed, 8 Nov 2000 06:41:30 -0800 (PST) Received: (qmail 988 invoked from network); 9 Nov 2000 06:40:43 -0000 Received: from unknown (HELO oneflower) (202.109.110.101) by 202.109.110.102 with SMTP; 9 Nov 2000 06:40:43 -0000 Message-ID: <001701c04991$87ea03c0$656e6dca@oneflower> From: "oneflower" To: , Subject: a problem about install freebsd 4.1.1 on HP Lpr? Date: Wed, 8 Nov 2000 22:38:16 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG SGVsbG8sZXZlcnkgb25lOg0KDQogIEkgaGF2ZSBtZWV0IGEgcHJvYmxlbSB3aGVuIEkgYW0gaW5z dGFsbGluZyBGcmVlQlNEIDQuMS4xIG9uIEhQIExQUi4NCg0KSFAgTFBSOg0KDQpjcHU6IFBJSUkg NjUwTUhaICoyDQptZW1vcnk6Mzg0TUINCkRpc2sgOiA5RyBzY3NpLTIgKjINClNjc2kgY2FyZDog IEhQIE5ldFJhaWQgMXNpDQogICAgICAgICAgICBzY3NpIGNhcmQgd2l0aG91dCByYWlkIChIUCkN Cg0KUGhvZW5peEJJT1MgNC4wNi4zNCBQUg0KU3ltYmlvcyxJbmMuU0RNUyAoVE0pIHY0LjAgUENJ IFNDU0kgQklPUyxQQ0kgUmV2LiAyLjAgLDIuMQ0KQ29weXJpZ2h0IDE5OTUgLDE5OTggU3ltYmlv cyxJbmMuDQpQQ0ktNC4xNC4wNA0KDQpTeW1iaW9zLEluYy5QY2kgYm9vdCBSb20gLG5vIHN1cHBv cnRlZCBkZXZpY2VzIGZvdW5kLg0KDQpIUCBOZXRSQUlEIEFkYXB0ZXIgQklPUyBWRVIgQi4wMi4w MiBBcHIgMDMsMjAwMA0KQ29weXJpZ2h0KGMpIEFtZXJpY2FuIE1lZ2FUcmVuZHMsSW5jLg0KDQoN Cg0KdGhlIGluc3RhbGwgcHJvY2VzcyBzdG9wIGF0IHRoaXMgc2NyZWVuOg0KDQoiLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uDQpmeHAwOjxJbnRlciBwcm8gMTAvMTAw Qi8xMDArIEV0aGVybmV0PiBwb3J0IDB4OTQwMC0weDk0M2YgbWVtIDB4ZmExMDAwMDAtMHhmYTFm ZmZmZiwNCjB4ZmEyMDAwMDAtMHhmYTJmZmZmZiAgaXJxIDExIGF0IGRldmljZSAzLjAgb24gcGNp MQ0KZnhwMDogRXRoZXJuZXQgYWRkcmVzcyAwMDpkMDpiNzo5MToyMDpkMg0Kc3ltMDogPDg5NT4g cG9ydCAweDkwMDAtMHg5MGZmIG1lbSAweGZhMjAxMDAwLTB4ZmEyMDFmZmYsMHhmYTIwMjAwMC0w eGZhMjAyMGZmIA0KaXJxIDE1IGF0IGRldmljZSA0LjAgb24gcGNpMSINCiAgDQoNCmFmdGVyIGEg bG9uZyB0aW1lICxpdCByZXBlYXRlZCBtZXNzYWdlcyBvbiBzY3JlZW4gbGlrZSA6DQoNCiIuLi4u Li4uDQoobm9wZXJpcGg6IHN5bTA6MDotMTotMSk6IFNDU0kgQlVTIG1vZGUgY2hhbmdlIGZyb20g U0UgdG8gU0UNCnN5bTA6MDppcGg6c3ltIE9VVCBwaGFzZSBhZnRlci4uLi4uLi4uLi4uIg0KDQoN Cg0KV2hhdCBwcm9ibGVtPyBXaG8gY2FuIGhlbHAgbWU/DQoNClRoZSBMcHIgY2FuIGJlIGluc3Rh bGxlZCB3aXRoIHdpbmRvd3MgMjAwMCBBZHYgU2VydmVyLHJ1biB3ZWxsIGJ1dCBib290IHdpbmRv d3MNCiBuZWVkcyBhIGxvdCBvZiB0aW1lLg0KSSBjYW4ndCBpbnN0YWxsICBSZWRoYXQgNy4wIG9u IGl0ICx0b28uDQpJdCBzdG9wZWQgYXQgbG9hZCBzY3NpIGRyaXZlci4NCg0KDQpCZXN0IFJlZ2Fy ZHMsDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBGbG93ZXIN Cg== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 7: 4:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from css-1.cs.iastate.edu (css-1.cs.iastate.edu [129.186.3.24]) by hub.freebsd.org (Postfix) with ESMTP id F01E137B4C5; Wed, 8 Nov 2000 07:04:44 -0800 (PST) Received: from popeye.cs.iastate.edu (ghelmer@popeye.cs.iastate.edu [129.186.3.4]) by css-1.cs.iastate.edu (8.9.0/8.9.0) with ESMTP id JAA12259; Wed, 8 Nov 2000 09:04:44 -0600 (CST) Received: from localhost (ghelmer@localhost) by popeye.cs.iastate.edu (8.9.0/8.9.0) with ESMTP id JAA06305; Wed, 8 Nov 2000 09:04:41 -0600 (CST) X-Authentication-Warning: popeye.cs.iastate.edu: ghelmer owned process doing -bs Date: Wed, 8 Nov 2000 09:04:41 -0600 (CST) From: Guy Helmer To: Konrad Heuer Cc: Kris Kennaway , freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: TCPDUMP patch v1.1 and AppleTalk In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Nov 2000, Konrad Heuer wrote: > > On Tue, 7 Nov 2000, Kris Kennaway wrote: > > > On Tue, Nov 07, 2000 at 01:56:21PM +0100, Konrad Heuer wrote: > > > > > After patching and installing, tcpdump can't be used anymore since it puts > > > very heavy load onto the network via xl0 and AppleTalk broadcast messages > > > (one message each 0.2 ms). Sorry, in the moment I don't know more details > > > ... > > > > tcpdump shouldn't be sending any appletalk packets, I thought (I may > > be wrong, never used it on an appletalk network). Are you sure this is > > the problem? > > > > Kris > > Well, I don't know exactly what happens but I seems to be more complex > than I thought first. It doesn't happen each time I start tcpdump but when > some circumstances meet which I don't know my FreeBSD host begins to flood > the network with AppelTalk broadcast requests as long as tcpdump keeps > running. Killing tcpdump kills this flooding, too. I've never observed > such a situation before I applied the last patch, and I use tcpdump > frequently to analyze the one or other problem. On the other hand, our > network environment isn't static, of course, and I can't be sure about > other things that may have been changed from day to day. If you are running the daemon that supports Appletalk (is it netatalk?), perhaps the Appletalk daemon becomes confused when tcpdump puts the Ethernet interface into promiscuous mode. It may be that the daemon expects to see only the Appletalk traffic directed to it, and seeing *all* Appletalk traffic on the wire makes it go nuts. Guy Helmer, Ph.D. Candidate, Iowa State University Dept. of Computer Science Research Assistant, Dept. of Computer Science --- ghelmer@cs.iastate.edu http://www.cs.iastate.edu/~ghelmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 7:35:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id C69CF37B479; Wed, 8 Nov 2000 07:35:09 -0800 (PST) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id HAA20486; Wed, 8 Nov 2000 07:32:44 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id HAA91370; Wed, 8 Nov 2000 07:32:43 -0800 (PST) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id HAA14728; Wed, 8 Nov 2000 07:32:42 -0800 (PST) From: Don Lewis Message-Id: <200011081532.HAA14728@salsa.gv.tsc.tdk.com> Date: Wed, 8 Nov 2000 07:32:42 -0800 In-Reply-To: References: X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Max Khon , "Koster, K.J." Subject: RE: daemon() Cc: "'Doug Barton'" , "'FreeBSD Hackers mailing list'" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov 8, 5:06pm, Max Khon wrote: } Subject: RE: daemon() } hi, there! } } On Wed, 8 Nov 2000, Koster, K.J. wrote: } } > > No one with any brains uses bash 1 for anything } > > anymore. } } > Then why is it there? To help up the port count? If it's not good, it should } > be nuked, IMHO. } } people still use it because it is smaller } obrien has already tried to remove it once (in Mar 1999) } } as for me -- I do not try to hunt bugs in bash1 and do not blame it. } my question was about unclosed pipe It appears to be a descriptor that your shell failed to close before execing your test program. Unless you do something out of the ordinary like run program 27>somefile the shell should only leave three descriptors (0, 1, and 2 for stdin, stdout, and stderr) open when it execs another program. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 7:35:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 9C51437B4FE; Wed, 8 Nov 2000 07:35:13 -0800 (PST) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.1/8.11.0) id eA8FWUV87045; Wed, 8 Nov 2000 16:32:30 +0100 (CET) (envelope-from asmodai) Date: Wed, 8 Nov 2000 16:32:30 +0100 From: Jeroen Ruigrok van der Werven To: Max Khon Cc: "Koster, K.J." , "'Doug Barton'" , "'FreeBSD Hackers mailing list'" Subject: Re: daemon() Message-ID: <20001108163230.Q80971@lucifer.bart.nl> References: <59063B5B4D98D311BC0D0001FA7E4522026D79C7@l04.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from fjoe@iclub.nsu.ru on Wed, Nov 08, 2000 at 05:06:42PM +0600 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20001108 12:10], Max Khon (fjoe@iclub.nsu.ru) wrote: [snip spurious fd problem] >as for me -- I do not try to hunt bugs in bash1 and do not blame it. >my question was about unclosed pipe Which seems to me, after X people tested the same program under a host of different shells, including bash 2.x, that the problem lies with bash 1.x. And people _did_ answer the question by pointing that out. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Things do not change, we change... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 7:56: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kaon.intercom.com (kaon.intercom.com [198.143.3.30]) by hub.freebsd.org (Postfix) with ESMTP id 3EE6037B4C5; Wed, 8 Nov 2000 07:55:56 -0800 (PST) Received: from [198.143.3.26] (helo=intercom.com) by kaon.intercom.com with esmtp (Exim 3.16 #1) id 13tXZg-000HYP-00; Wed, 08 Nov 2000 10:55:44 -0500 Date: Wed, 8 Nov 2000 10:55:44 -0500 (EST) From: "Jason J. Horton" X-Sender: mail@kaon.intercom.com To: oneflower Cc: freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org Subject: Re: a problem about install freebsd 4.1.1 on HP Lpr? In-Reply-To: <001701c04991$87ea03c0$656e6dca@oneflower> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had no problems with my LPrs during installs, I have almost the same config as you (the diff being faster CPUs). Are you sure you properly terminated the built-in SCSI card when you installed the RAID card? The instructions that came with the RAID card are pretty detailed in what needs to be done. Also, if you dont have any drives attached to the built-in SCSI card, you may want to concider disabling it in the BIOS. > Hello,every one: > > I have meet a problem when I am installing FreeBSD 4.1.1 on HP LPR. > > HP LPR: > > cpu: PIII 650MHZ *2 > memory:384MB > Disk : 9G scsi-2 *2 > Scsi card: HP NetRaid 1si > scsi card without raid (HP) > > PhoenixBIOS 4.06.34 PR > Symbios,Inc.SDMS (TM) v4.0 PCI SCSI BIOS,PCI Rev. 2.0 ,2.1 > Copyright 1995 ,1998 Symbios,Inc. > PCI-4.14.04 > > Symbios,Inc.Pci boot Rom ,no supported devices found. > > HP NetRAID Adapter BIOS VER B.02.02 Apr 03,2000 > Copyright(c) American MegaTrends,Inc. > > > > the install process stop at this screen: > > ".......................................... > fxp0: port 0x9400-0x943f mem 0xfa100000-0xfa1fffff, > 0xfa200000-0xfa2fffff irq 11 at device 3.0 on pci1 > fxp0: Ethernet address 00:d0:b7:91:20:d2 > sym0: <895> port 0x9000-0x90ff mem 0xfa201000-0xfa201fff,0xfa202000-0xfa2020ff > irq 15 at device 4.0 on pci1" > > > after a long time ,it repeated messages on screen like : > > "....... > (noperiph: sym0:0:-1:-1): SCSI BUS mode change from SE to SE > sym0:0:iph:sym OUT phase after..........." > > > > What problem? Who can help me? > > The Lpr can be installed with windows 2000 Adv Server,run well but > boot windows needs a lot of time. > I can't install Redhat 7.0 on it ,too. > It stoped at load scsi driver. > > > Best Regards, > > Flower To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 8:24:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 128FD37B4CF; Wed, 8 Nov 2000 08:24:41 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.11.1/8.11.1) with ESMTP id eA8GMxj33122; Wed, 8 Nov 2000 22:22:59 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 8 Nov 2000 22:22:58 +0600 (NS) From: Max Khon To: Don Lewis Cc: "Koster, K.J." , "'Doug Barton'" , "'FreeBSD Hackers mailing list'" Subject: RE: daemon() In-Reply-To: <200011081532.HAA14728@salsa.gv.tsc.tdk.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Wed, 8 Nov 2000, Don Lewis wrote: > } > > No one with any brains uses bash 1 for anything > } > > anymore. > } > } > Then why is it there? To help up the port count? If it's not good, it should > } > be nuked, IMHO. > } > } people still use it because it is smaller > } obrien has already tried to remove it once (in Mar 1999) > } > } as for me -- I do not try to hunt bugs in bash1 and do not blame it. > } my question was about unclosed pipe > > It appears to be a descriptor that your shell failed to close before > execing your test program. Unless you do something out of the ordinary > like run > program 27>somefile > the shell should only leave three descriptors (0, 1, and 2 for stdin, stdout, > and stderr) open when it execs another program. yes, I understand that. My point is that bash1 is still used and comments about braindead people who use it should be redirected to /dev/null. I think we should stop this thread. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 9:23:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whalers.digisle.com (whalers.digisle.com [167.216.128.32]) by hub.freebsd.org (Postfix) with ESMTP id 24E4E37B4C5 for ; Wed, 8 Nov 2000 09:23:30 -0800 (PST) Received: from guinness.digisle.net (guinness.digisle.net [167.216.152.33]) by whalers.digisle.com (8.9.3/8.9.3/mx) with ESMTP id RAA17691 for ; Wed, 8 Nov 2000 17:24:30 GMT Received: from digisle.com (comanche.digisle.com [206.220.227.145]) by guinness.digisle.net (8.9.3/8.9.3/digisle) with ESMTP id RAA22683 for ; Wed, 8 Nov 2000 17:23:28 GMT Message-ID: <3A098C0F.C06701EC@digisle.com> Date: Wed, 08 Nov 2000 09:23:27 -0800 From: Maksim Yevmenkin Organization: Digital Island X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: list problem? (Re: Undelivered Mail Returned to Sender) References: <20001108053210.C07DD37B4CF@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'm sorry for posting it here, but... Mail Delivery System wrote: > > This is the Postfix program at host hub.freebsd.org. > > I'm sorry to have to inform you that the message returned > below could not be delivered to one or more destinations. > > For further assistance, please contact > > If you do so, please include this problem report. You can > delete your own text from the message returned below. > > The Postfix program > > : mail forwarding loop for > freebsd-hackers@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 Nov 8 9:29: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 8AA1737B4C5; Wed, 8 Nov 2000 09:27:56 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13tYsG-0000I5-00; Wed, 08 Nov 2000 10:19:00 -0700 Message-ID: <3A098B04.EA631BB5@softweyr.com> Date: Wed, 08 Nov 2000 10:19:00 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Maarten van Schie , mb@imp.ch, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: StarOffice 5.2 port for FreeBSD. References: <3A084CD7.D8023C33@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > > Maarten van Schie wrote: > > > > When I installed SO it didn't spitt out any complaints about the checksum. > > > > Did you install the Linux Emulator from /usr/ports/emulators/linux_base ? > > You need it since the SO port uses the Linux version. > > Yes, and linux-netscape and wordperfect both install and run without any > problems. This turned out to be a flawed download file. I downloaded the so-* file directly from the Sun web page and it installed without a problem. Perhaps somebody should inform the mirror sites? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 9:31: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web122.yahoomail.com (web122.mail.yahoo.com [205.180.60.57]) by hub.freebsd.org (Postfix) with SMTP id 5191037B479 for ; Wed, 8 Nov 2000 09:31:01 -0800 (PST) Received: (qmail 11469 invoked by uid 60001); 8 Nov 2000 17:31:00 -0000 Message-ID: <20001108173100.11468.qmail@web122.yahoomail.com> Received: from [167.216.163.116] by web122.yahoomail.com; Wed, 08 Nov 2000 09:31:00 PST Date: Wed, 8 Nov 2000 09:31:00 -0800 (PST) From: Maksim Yevmenkin Subject: [PATCH] Please review and commit (Re: if_tap and devfs) To: freebsd-hackers@freebsd.org Cc: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-783368690-973704660=:11219" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-783368690-973704660=:11219 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello All, anyone wants to review and commit the following patch. thanks, emax __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one Place. http://shopping.yahoo.com/ --0-783368690-973704660=:11219 Content-Type: application/x-unknown; name="if_tap.c.diff" Content-Transfer-Encoding: base64 Content-Description: if_tap.c.diff Content-Disposition: attachment; filename="if_tap.c.diff" KioqIGlmX3RhcC5jLm9yaWcJTW9uIE5vdiAgNiAwOToyNDowOCAyMDAwCi0t LSBpZl90YXAuYwlNb24gTm92ICA2IDEwOjI2OjM1IDIwMDAKKioqKioqKioq KioqKioqCioqKiA3OSw4NCAqKioqCi0tLSA3OSw4NSAtLS0tCiAgc3RhdGlj IGludCAJCXRhcG1vZGV2ZW50CV9fUCgobW9kdWxlX3QsIGludCwgdm9pZCAq KSk7CiAgCiAgLyogZGV2aWNlICovCisgc3RhdGljIHZvaWQJCXRhcGNsb25l CV9fUCgodm9pZCAqLCBjaGFyICosIGludCwgZGV2X3QgKikpOwogIHN0YXRp YyB2b2lkCQl0YXBjcmVhdGUJX19QKChkZXZfdCkpOwogIAogIC8qIG5ldHdv cmsgaW50ZXJmYWNlICovCioqKioqKioqKioqKioqKgoqKiogMTMxLDE1NyAq KioqCiAgCWludAkJIHR5cGU7CiAgCXZvaWQJCSpkYXRhOwogIHsKISAJc3Rh dGljIGludAkJIGF0dGFjaGVkID0gMDsKISAJc3RydWN0IGlmbmV0CQkqaWZw ID0gTlVMTDsKISAJaW50CQkJIHVuaXQsIHM7CiAgCiAgCXN3aXRjaCAodHlw ZSkgewogIAljYXNlIE1PRF9MT0FEOgogIAkJaWYgKGF0dGFjaGVkKQogIAkJ CXJldHVybiAoRUVYSVNUKTsKICAKICAJCWNkZXZzd19hZGQoJnRhcF9jZGV2 c3cpOwogIAkJYXR0YWNoZWQgPSAxOwogIAlicmVhazsKICAKISAJY2FzZSBN T0RfVU5MT0FEOgogIAkJaWYgKHRhcHJlZmNudCA+IDApCiAgCQkJcmV0dXJu IChFQlVTWSk7CiAgCiAgCQljZGV2c3dfcmVtb3ZlKCZ0YXBfY2RldnN3KTsK ICAKICAJCXVuaXQgPSAwOwogIAkJd2hpbGUgKHVuaXQgPD0gdGFwbGFzdHVu aXQpIHsKICAJCQlzID0gc3BsaW1wKCk7CiAgCQkJVEFJTFFfRk9SRUFDSChp ZnAsICZpZm5ldCwgaWZfbGluaykKICAJCQkJaWYgKChzdHJjbXAoaWZwLT5p Zl9uYW1lLCBUQVApID09IDApIHx8Ci0tLSAxMzIsMTY0IC0tLS0KICAJaW50 CQkgdHlwZTsKICAJdm9pZAkJKmRhdGE7CiAgewohIAlzdGF0aWMgaW50CQlh dHRhY2hlZCA9IDA7CiEgCXN0YXRpYyBldmVudGhhbmRsZXJfdGFnCWVoX3Rh ZyA9IE5VTEw7CiAgCiAgCXN3aXRjaCAodHlwZSkgewogIAljYXNlIE1PRF9M T0FEOgogIAkJaWYgKGF0dGFjaGVkKQogIAkJCXJldHVybiAoRUVYSVNUKTsK ICAKKyAJCWVoX3RhZyA9IEVWRU5USEFORExFUl9SRUdJU1RFUihkZXZfY2xv bmUsIHRhcGNsb25lLCAwLCAxMDAwKTsKICAJCWNkZXZzd19hZGQoJnRhcF9j ZGV2c3cpOwogIAkJYXR0YWNoZWQgPSAxOwogIAlicmVhazsKICAKISAJY2Fz ZSBNT0RfVU5MT0FEOiB7CiEgCQlpbnQJdW5pdDsKISAKICAJCWlmICh0YXBy ZWZjbnQgPiAwKQogIAkJCXJldHVybiAoRUJVU1kpOwogIAorIAkJRVZFTlRI QU5ETEVSX0RFUkVHSVNURVIoZGV2X2Nsb25lLCBlaF90YWcpOwogIAkJY2Rl dnN3X3JlbW92ZSgmdGFwX2NkZXZzdyk7CiAgCiAgCQl1bml0ID0gMDsKICAJ CXdoaWxlICh1bml0IDw9IHRhcGxhc3R1bml0KSB7CisgCQkJaW50CQkgczsK KyAJCQlzdHJ1Y3QgaWZuZXQJKmlmcCA9IE5VTEw7CisgCiAgCQkJcyA9IHNw bGltcCgpOwogIAkJCVRBSUxRX0ZPUkVBQ0goaWZwLCAmaWZuZXQsIGlmX2xp bmspCiAgCQkJCWlmICgoc3RyY21wKGlmcC0+aWZfbmFtZSwgVEFQKSA9PSAw KSB8fAoqKioqKioqKioqKioqKioKKioqIDE3OSwxODUgKioqKgogIAkJfQog IAogIAkJYXR0YWNoZWQgPSAwOwohIAlicmVhazsKICAKICAJZGVmYXVsdDoK ICAJCXJldHVybiAoRU9QTk9UU1VQUCk7Ci0tLSAxODYsMTkyIC0tLS0KICAJ CX0KICAKICAJCWF0dGFjaGVkID0gMDsKISAJfSBicmVhazsKICAKICAJZGVm YXVsdDoKICAJCXJldHVybiAoRU9QTk9UU1VQUCk7CioqKioqKioqKioqKioq KgoqKiogMTg3LDE5MiAqKioqCi0tLSAxOTQsMjM0IC0tLS0KICAKICAJcmV0 dXJuICgwKTsKICB9IC8qIHRhcG1vZGV2ZW50ICovCisgCisgCisgLyoKKyAg KiBERVZGUyBoYW5kbGVyCisgICoKKyAgKiBXZSBuZWVkIHRvIHN1cHBvcnQg dHdvIGtpbmQgb2YgZGV2aWNlcyAtIHRhcCBhbmQgdm1uZXQKKyAgKi8KKyBz dGF0aWMgdm9pZAorIHRhcGNsb25lKGFyZywgbmFtZSwgbmFtZWxlbiwgZGV2 KQorIAl2b2lkCSphcmc7CisgCWNoYXIJKm5hbWU7CisgCWludAkgbmFtZWxl bjsKKyAJZGV2X3QJKmRldjsKKyB7CisgCWludAkgdW5pdCwgbWlub3I7Cisg CWNoYXIJKmRldmljZV9uYW1lID0gTlVMTDsKKyAKKyAJaWYgKCpkZXYgIT0g Tk9ERVYpCisgCQlyZXR1cm47CisgCisgCWRldmljZV9uYW1lID0gVEFQOwor IAlpZiAoZGV2X3N0ZGNsb25lKG5hbWUsIE5VTEwsIGRldmljZV9uYW1lLCAm dW5pdCkgIT0gMSkgeworIAkJZGV2aWNlX25hbWUgPSBWTU5FVDsKKyAKKyAJ CWlmIChkZXZfc3RkY2xvbmUobmFtZSwgTlVMTCwgZGV2aWNlX25hbWUsICZ1 bml0KSAhPSAxKQorIAkJCXJldHVybjsKKyAKKyAJCW1pbm9yID0gKHVuaXQg fCAgVk1ORVRfREVWX01BU0spOworIAl9CisgCWVsc2UKKyAJCW1pbm9yID0g dW5pdDsKKyAKKyAJKmRldiA9IG1ha2VfZGV2KCZ0YXBfY2RldnN3LCBtaW5v ciwgVUlEX1JPT1QsIEdJRF9XSEVFTCwgMDYwMCwgIiVzJWQiLAorIAkJCWRl dmljZV9uYW1lLCB1bml0KTsKKyB9IC8qIHRhcGNsb25lICovCiAgCiAgCiAg LyoK --0-783368690-973704660=:11219-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 9:36:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id CE27B37B479; Wed, 8 Nov 2000 09:35:59 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.9.3) with ESMTP id eA8HZKm04780; Wed, 8 Nov 2000 18:35:20 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Maksim Yevmenkin Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: [PATCH] Please review and commit (Re: if_tap and devfs) In-Reply-To: Your message of "Wed, 08 Nov 2000 09:31:00 PST." <20001108173100.11468.qmail@web122.yahoomail.com> Date: Wed, 08 Nov 2000 18:35:20 +0100 Message-ID: <4778.973704920@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just glanced at it and see no major mistakes. Sorry I don't have time for a real review. Poul-Henning In message <20001108173100.11468.qmail@web122.yahoomail.com>, Maksim Yevmenkin writes: >--0-783368690-973704660=:11219 >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline > >Hello All, > >anyone wants to review and commit the following patch. > >thanks, >emax > > >__________________________________________________ >Do You Yahoo!? >Thousands of Stores. Millions of Products. All in one Place. >http://shopping.yahoo.com/ >--0-783368690-973704660=:11219 >Content-Type: application/x-unknown; name="if_tap.c.diff" >Content-Transfer-Encoding: base64 >Content-Description: if_tap.c.diff >Content-Disposition: attachment; filename="if_tap.c.diff" > >KioqIGlmX3RhcC5jLm9yaWcJTW9uIE5vdiAgNiAwOToyNDowOCAyMDAwCi0t >LSBpZl90YXAuYwlNb24gTm92ICA2IDEwOjI2OjM1IDIwMDAKKioqKioqKioq >KioqKioqCioqKiA3OSw4NCAqKioqCi0tLSA3OSw4NSAtLS0tCiAgc3RhdGlj >IGludCAJCXRhcG1vZGV2ZW50CV9fUCgobW9kdWxlX3QsIGludCwgdm9pZCAq >KSk7CiAgCiAgLyogZGV2aWNlICovCisgc3RhdGljIHZvaWQJCXRhcGNsb25l >CV9fUCgodm9pZCAqLCBjaGFyICosIGludCwgZGV2X3QgKikpOwogIHN0YXRp >YyB2b2lkCQl0YXBjcmVhdGUJX19QKChkZXZfdCkpOwogIAogIC8qIG5ldHdv >cmsgaW50ZXJmYWNlICovCioqKioqKioqKioqKioqKgoqKiogMTMxLDE1NyAq >KioqCiAgCWludAkJIHR5cGU7CiAgCXZvaWQJCSpkYXRhOwogIHsKISAJc3Rh >dGljIGludAkJIGF0dGFjaGVkID0gMDsKISAJc3RydWN0IGlmbmV0CQkqaWZw >ID0gTlVMTDsKISAJaW50CQkJIHVuaXQsIHM7CiAgCiAgCXN3aXRjaCAodHlw >ZSkgewogIAljYXNlIE1PRF9MT0FEOgogIAkJaWYgKGF0dGFjaGVkKQogIAkJ >CXJldHVybiAoRUVYSVNUKTsKICAKICAJCWNkZXZzd19hZGQoJnRhcF9jZGV2 >c3cpOwogIAkJYXR0YWNoZWQgPSAxOwogIAlicmVhazsKICAKISAJY2FzZSBN >T0RfVU5MT0FEOgogIAkJaWYgKHRhcHJlZmNudCA+IDApCiAgCQkJcmV0dXJu >IChFQlVTWSk7CiAgCiAgCQljZGV2c3dfcmVtb3ZlKCZ0YXBfY2RldnN3KTsK >ICAKICAJCXVuaXQgPSAwOwogIAkJd2hpbGUgKHVuaXQgPD0gdGFwbGFzdHVu >aXQpIHsKICAJCQlzID0gc3BsaW1wKCk7CiAgCQkJVEFJTFFfRk9SRUFDSChp >ZnAsICZpZm5ldCwgaWZfbGluaykKICAJCQkJaWYgKChzdHJjbXAoaWZwLT5p >Zl9uYW1lLCBUQVApID09IDApIHx8Ci0tLSAxMzIsMTY0IC0tLS0KICAJaW50 >CQkgdHlwZTsKICAJdm9pZAkJKmRhdGE7CiAgewohIAlzdGF0aWMgaW50CQlh >dHRhY2hlZCA9IDA7CiEgCXN0YXRpYyBldmVudGhhbmRsZXJfdGFnCWVoX3Rh >ZyA9IE5VTEw7CiAgCiAgCXN3aXRjaCAodHlwZSkgewogIAljYXNlIE1PRF9M >T0FEOgogIAkJaWYgKGF0dGFjaGVkKQogIAkJCXJldHVybiAoRUVYSVNUKTsK >ICAKKyAJCWVoX3RhZyA9IEVWRU5USEFORExFUl9SRUdJU1RFUihkZXZfY2xv >bmUsIHRhcGNsb25lLCAwLCAxMDAwKTsKICAJCWNkZXZzd19hZGQoJnRhcF9j >ZGV2c3cpOwogIAkJYXR0YWNoZWQgPSAxOwogIAlicmVhazsKICAKISAJY2Fz >ZSBNT0RfVU5MT0FEOiB7CiEgCQlpbnQJdW5pdDsKISAKICAJCWlmICh0YXBy >ZWZjbnQgPiAwKQogIAkJCXJldHVybiAoRUJVU1kpOwogIAorIAkJRVZFTlRI >QU5ETEVSX0RFUkVHSVNURVIoZGV2X2Nsb25lLCBlaF90YWcpOwogIAkJY2Rl >dnN3X3JlbW92ZSgmdGFwX2NkZXZzdyk7CiAgCiAgCQl1bml0ID0gMDsKICAJ >CXdoaWxlICh1bml0IDw9IHRhcGxhc3R1bml0KSB7CisgCQkJaW50CQkgczsK >KyAJCQlzdHJ1Y3QgaWZuZXQJKmlmcCA9IE5VTEw7CisgCiAgCQkJcyA9IHNw >bGltcCgpOwogIAkJCVRBSUxRX0ZPUkVBQ0goaWZwLCAmaWZuZXQsIGlmX2xp >bmspCiAgCQkJCWlmICgoc3RyY21wKGlmcC0+aWZfbmFtZSwgVEFQKSA9PSAw >KSB8fAoqKioqKioqKioqKioqKioKKioqIDE3OSwxODUgKioqKgogIAkJfQog >IAogIAkJYXR0YWNoZWQgPSAwOwohIAlicmVhazsKICAKICAJZGVmYXVsdDoK >ICAJCXJldHVybiAoRU9QTk9UU1VQUCk7Ci0tLSAxODYsMTkyIC0tLS0KICAJ >CX0KICAKICAJCWF0dGFjaGVkID0gMDsKISAJfSBicmVhazsKICAKICAJZGVm >YXVsdDoKICAJCXJldHVybiAoRU9QTk9UU1VQUCk7CioqKioqKioqKioqKioq >KgoqKiogMTg3LDE5MiAqKioqCi0tLSAxOTQsMjM0IC0tLS0KICAKICAJcmV0 >dXJuICgwKTsKICB9IC8qIHRhcG1vZGV2ZW50ICovCisgCisgCisgLyoKKyAg >KiBERVZGUyBoYW5kbGVyCisgICoKKyAgKiBXZSBuZWVkIHRvIHN1cHBvcnQg >dHdvIGtpbmQgb2YgZGV2aWNlcyAtIHRhcCBhbmQgdm1uZXQKKyAgKi8KKyBz >dGF0aWMgdm9pZAorIHRhcGNsb25lKGFyZywgbmFtZSwgbmFtZWxlbiwgZGV2 >KQorIAl2b2lkCSphcmc7CisgCWNoYXIJKm5hbWU7CisgCWludAkgbmFtZWxl >bjsKKyAJZGV2X3QJKmRldjsKKyB7CisgCWludAkgdW5pdCwgbWlub3I7Cisg >CWNoYXIJKmRldmljZV9uYW1lID0gTlVMTDsKKyAKKyAJaWYgKCpkZXYgIT0g >Tk9ERVYpCisgCQlyZXR1cm47CisgCisgCWRldmljZV9uYW1lID0gVEFQOwor >IAlpZiAoZGV2X3N0ZGNsb25lKG5hbWUsIE5VTEwsIGRldmljZV9uYW1lLCAm >dW5pdCkgIT0gMSkgeworIAkJZGV2aWNlX25hbWUgPSBWTU5FVDsKKyAKKyAJ >CWlmIChkZXZfc3RkY2xvbmUobmFtZSwgTlVMTCwgZGV2aWNlX25hbWUsICZ1 >bml0KSAhPSAxKQorIAkJCXJldHVybjsKKyAKKyAJCW1pbm9yID0gKHVuaXQg >fCAgVk1ORVRfREVWX01BU0spOworIAl9CisgCWVsc2UKKyAJCW1pbm9yID0g >dW5pdDsKKyAKKyAJKmRldiA9IG1ha2VfZGV2KCZ0YXBfY2RldnN3LCBtaW5v >ciwgVUlEX1JPT1QsIEdJRF9XSEVFTCwgMDYwMCwgIiVzJWQiLAorIAkJCWRl >dmljZV9uYW1lLCB1bml0KTsKKyB9IC8qIHRhcGNsb25lICovCiAgCiAgCiAg >LyoK > >--0-783368690-973704660=:11219-- > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- 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 Wed Nov 8 10: 5:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from linus.dvart.com (linus.dvart.com [64.79.2.3]) by hub.freebsd.org (Postfix) with ESMTP id AE9B937B4D7 for ; Wed, 8 Nov 2000 10:05:14 -0800 (PST) Received: from dvart.com ([192.168.100.141]) by linus.dvart.com (8.9.3/8.9.3) with ESMTP id KAA02791; Wed, 8 Nov 2000 10:05:13 -0800 Message-ID: <3A0995D9.61AD357F@dvart.com> Date: Wed, 08 Nov 2000 10:05:13 -0800 From: bruno schwander X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Luigi Rizzo Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: close call in a device ? References: <200011080736.XAA02080@iguana.aciri.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Luigi Rizzo wrote: > you could do something like this: > + open allocates a descriptor which stores the PID of the process requesting > access to the "device" > doing that now > + each I/O operation uses the descriptor matching the PID passed to the > read/write/ioctl that too > > + you could implement an ioctl() to dispose the storage, a "well behaved" > process would have to invoke this ioctl before terminating; I could, but my problem is that the process is not under my control. I can't modify the program to have it do something more. Maybe I can have a module that captures the close call and make it issue my special cleanup ioctl ? Or maybe that call won't be intercepted precisely because of the so far observed behavior ? back to studying the kernel module stuff.... > > + and a timeout as you suggested could be used to purge entries that have > been idle for some time, or you could also purge them basing on usage > patterns assumning there are clearly identifiable ones. > yes, but that is the problem again, there may not be clearly identifiable patterns. At least, in the worst case, I could just check the process table and when a process goes away, I clean its associated resources. And I have to hope that a given process does not reopen and close the device several times. > > > Did I miss something in your suggestion ? Or were you suggesting that I can > > create same name device entries, differing only by their minor number ? But then > > you cannot use the same name unless the entries are in different > directories. My suggestion was to use /dev/foo.00 /dev/foo.01 /dev/foo.02 > and so on. > yep, I tried and tested that now :-) well there may not be a simple solution, but I think the idea of trapping "close" calls may work if I can trap the actual call before the kernel does its job of deciding where to route the call (which driver) and if the driver "close" should be called. Thanks for the idea. Any comments anyone ? bruno ########################################################################### Bruno Schwander Senior Software Engineer Worldgate Communications, Inc email: bschwand@dvart.com ############################################################################ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 10:31:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id CD45637B479; Wed, 8 Nov 2000 10:31:36 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id eA8ISUj13784; Wed, 8 Nov 2000 12:28:30 -0600 (CST) (envelope-from jlemon) Date: Wed, 8 Nov 2000 12:28:30 -0600 (CST) From: Jonathan Lemon Message-Id: <200011081828.eA8ISUj13784@prism.flugsvamp.com> To: asmodai@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: PSE/PAE support X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Reading some documents and sources I came to the following conclusion: > >We support 4 Kbyte pages and 4 Mbyte pages, but we do not support 2 >Mbyte pages. On IA-32 at least. > >Is there a reason to? > >I could understand that some people would prefer 2 Mbyte pages in some >situations. But looking at pmap.c I see we only test CPUID_PSE and >don't use CPUID_PAE anywhere. My initial feeling is that it wouldn't win us anything. We use a two-level page table, with the first level covering a 4MB page, and the second level containing 1024 pte's, each covering 4K. Since each pte takes up 4 bytes, by using a 4MB page, we eliminate an entire page of pte's at the second level. With a 2M page, we would still need a second level page entry, plus some code to differentiate between 4K entries and a "half-page" 2M entry. But I'm by no means a vm hacker, so I may be wrong here. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 11:47:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id 3824E37B479 for ; Wed, 8 Nov 2000 11:47:48 -0800 (PST) Received: (qmail 6694 invoked by uid 1001); 9 Nov 2000 05:47:44 +1000 X-Posted-By: GBA-Post 2.06 15-Sep-2000 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Thu, 09 Nov 2000 05:47:44 +1000 From: Greg Black To: Giorgos Keramidas Cc: andrew@ugh.net.au, "Albert D. Cahalan" , hackers@FreeBSD.ORG, roam@orbitel.bg Subject: Re: umask(2) and -Wconversion References: <200011080223.eA82Nxf392522@saturn.cs.uml.edu> <20001108072630.A58596@gray.westgate.gr> In-reply-to: <20001108072630.A58596@gray.westgate.gr> of Wed, 08 Nov 2000 07:26:30 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Giorgos Keramidas writes: > 3 #define VALUE 0 > My original question was if this is not behavior that should be > considered buggy, since the size of VALUE has not been determined to be > equal to sizeof(int) when the #define occurs, or has it? The size of VALUE is not the issue; the type is `int' in the line quoted above. If you want VALUE to be a `short', you need to say: #define VALUE ((short) 0) -- Greg Black To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 11:56:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id 6AAED37B479 for ; Wed, 8 Nov 2000 11:56:44 -0800 (PST) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id MAA26705; Wed, 8 Nov 2000 12:52:51 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpdAAAx2aalZ; Wed Nov 8 12:51:32 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id MAA24247; Wed, 8 Nov 2000 12:55:21 -0700 (MST) From: Terry Lambert Message-Id: <200011081955.MAA24247@usr08.primenet.com> Subject: Re: gdb & threaded application To: andrew@ugh.net.au Date: Wed, 8 Nov 2000 19:55:20 +0000 (GMT) Cc: jasone@canonware.com (Jason Evans), freebsd-hackers@FreeBSD.ORG In-Reply-To: from "andrew@ugh.net.au" at Nov 06, 2000 02:09:33 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > the first thing I'd do if I were you would be to link statically. > > Yep that fixed it. In my experience, which include trying to get the JNI stuff working with promiscuous libraries, this is generally the result of a bug in the FreeBSD linker. What it usually means is that you have a program linked against a shared library that uses a function from a different shared library, like: prog: main() { lib_1_function(); } lib1: lib_1_function() { lib_2_function(); } And then no references to any other lib2 stuff from prog. The linker appaers to treat this as an RTLD_LAZY rather than an RTLD_NOW for the purposes of dependent symbol resoloution (ELF supports linking a shared library against another shared library, which is supposed to cause the library linked against to come in when you link programs against the first library). It appears that because of the RTLD_LAZY behaviou, there is no recursion on the load, and the second order dependency blows up, rather than getting resolved. I tried to fix this in the rtld stuff in FreeBSD 3.x, but it turned out that fixing the linker introduced a lot of references that then blew up, and what looked like it might take only an hour or so to fix blew up into something that would take a couple of weeks to fix (and I didn't have them). The easiest thing would be to explicitly link against the second order dependent library, or to link the first order dependent library statically, which will cause the symbols to be undefined unless the second order link is forced by the reference (this latter is what I think saved you, in this case, FWIW). I have also seen this (rarely), when ldconfig does not include the library where the shared libraries are being installed, for user supplied shared libraries. I think this is a bug, since ldconfig is only supposed to cache hints; you would think that it would look to the original link location to try to find the library, but it doesn't. I've seen this most often when doing builds of code off the net (like OpenSSL + Cyrus SASL) into my own build environment, rather than using /usr/local/lib, like ports wants you to. The link succeeds, but at runtime, the library fails to load. You can see this by doing an "ldd" on your binary, and seeing that it can't find some of the libraries (ldd and ld.so use the same ldconfig hints, and both use the same lookup function, which fails to do the correct thing when looking for "not found" libraries). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 12: 5:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id A9B9137B479 for ; Wed, 8 Nov 2000 12:05:37 -0800 (PST) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id NAA14215; Wed, 8 Nov 2000 13:02:10 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpdAAAdZaiGB; Wed Nov 8 13:01:54 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id NAA24535; Wed, 8 Nov 2000 13:05:12 -0700 (MST) From: Terry Lambert Message-Id: <200011082005.NAA24535@usr08.primenet.com> Subject: Re: system call and SYSCALL macro To: rlaw@vt.edu (Raymond Law) Date: Wed, 8 Nov 2000 20:05:12 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <4.3.0.20001106131527.00df0cc0@mail.vt.edu> from "Raymond Law" at Nov 06, 2000 01:16:51 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just try to add a simple system call for testing: > > int my_call(int x, int y) { > return (x + y); > } > > In my user program: > > int main(int argc, char ** argv) { > int x = 3; > int y = 8; > int z = 0; > z = syscall(SYS_my_call, x, y); > printf("%i + %i = %i\n", x, y, z); > return 0; > } > > But it prints: > > 3 + 8 = -1 > > Can you give me some idea what I did wrong and what I should do? Also, can > you tell me how to use the SYSCALL macro because I am not familiar with > macros at all? Thanks in advance. Change this to: int my_call(int x, int y, int *result) { *result = x + y; return( 0); } int main( int ac, char **av) { int x = 3; int y = 8; int z = 0; if( syscall(SYS_my_call, x, y, &z) != 0) { perror("system call failed!"); exit( 1); } printf("%i + %i = %i\n", x, y, z); return 0; } --- Since you aren't checking for failure of your system call, you are confusing a failure of the call with an incorrect result. I suspect you will see the error "ENOENT", meaning that your system call has not been loaded into the kernel, and had its function pointer inserted into sysent[ SYS_my_call]. Look at the KLD documentation and examples on how to load system calls into the kernel. see also "kldstat", which should tell you where your system call was loaded (i.e. it will give you the value you need to pass as "SYS_my_call" to syscall(2) for things to work). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 12: 8:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 1E71837B479; Wed, 8 Nov 2000 12:08:53 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp241.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eA8K8gH99005; Wed, 8 Nov 2000 12:08:42 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001108150722.L80971@lucifer.bart.nl> Date: Wed, 08 Nov 2000 12:09:10 -0800 (PST) From: John Baldwin To: Jeroen Ruigrok van der Werven Subject: RE: PSE/PAE support Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Nov-00 Jeroen Ruigrok van der Werven wrote: > Reading some documents and sources I came to the following conclusion: > > We support 4 Kbyte pages and 4 Mbyte pages, but we do not support 2 > Mbyte pages. On IA-32 at least. > > Is there a reason to? Heh, PSE and PAE are two different things. PSE allows you to specify that the pointer to the final layer page table should map a large contiguous page insetad of pointing to a page table that maps several 4k pages. A page table on IA-32 is 4096 bytes long. Under normal paging without PAE, each entry in a page table is 4 bytes long, so that each leaf page table can map 1024 4k pages, or 4 Meg. If you turn PSE on, then a "large" page mapsa contiguous 4mb page. PAE changes the paging a bit to allow for 36-bit physical addresses. It still uses 32-bit virtual addresses, however. To accomodate the larger number of bits for physical addresses, each page table entry becomes 8 bytes long instead of 4 bytes. Thus, each leaf page table can only map 512 4k pages, or 2 Mb. As a result, when PSE is turned on, a "large" page maps a contiuous 2mb page. Since each level of page tables with PAE only uses 9 bits intead of 8 (512 entries instead of 1024), an additional layer of page tables is added at the top with a small 16-entry table that points to the page directories. Without PAE, you normall have one page directory that is pointed to be %cr3. Here's a diagram that might help: Page Size Table: | Small Pages | Large Pages --------------------------------------- Normal | 4k | 4k PSE | 4k | 4m PAE | 4k | 4k PAE + PSE | 4k | 2m The benefits of PAE are that you can support a machine that has more than 4gb of phyiscal ram, up to 64gb. However, the virtual address space is still 4gb, so a process (and kernel with the current way we do our virtual address mapping) must still fit into a 4gb space. > I could understand that some people would prefer 2 Mbyte pages in some > situations. But looking at pmap.c I see we only test CPUID_PSE and > don't use CPUID_PAE anywhere. Actually, the 2mb pages really don't buy us anything. We only use large pages now to map the kernel, AFAIK. > Since pmap.c is in a MD location it wouldn't be hard to extend the code > to do this. > > Would this needlessly complicate a lot of things in our code? i could > envision that our VM and related code should be usable no matter what > the page size is. This will certainly improve future ports to new > architectures with different page sizes. Adding in PAE support is not an easy task. Many places in the x86 pmap code assume that a page table entry is an int. This is not true in the case of PAE. There are also other problems that Peter Wemm could scare you with. :) There is some desire to do this, but it won't be easy. > Are there even more arguments in favor or against? > > I'd like to hear some thoughts. :) I'm sure Peter can correct this and fill in any holes as well as offer guidance to anyone who is masochistic enough^W^Wwilling to work on this. > -- > Jeroen Ruigrok van der Werven Network- and systemadministrator > VIA Net.Works The Netherlands > BSD: Technical excellence at its best http://www.via-net-works.nl > Wisdom is the difference between knowledge and experience... -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "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 Nov 8 12:12: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.161.193]) by hub.freebsd.org (Postfix) with ESMTP id 63B1337B479 for ; Wed, 8 Nov 2000 12:11:55 -0800 (PST) Received: from mail.vt.edu (gkar.cc.vt.edu [198.82.161.190]) by lennier.cc.vt.edu (8.11.0/8.11.0) with ESMTP id eA8KBst22086; Wed, 8 Nov 2000 15:11:54 -0500 (EST) Received: from zathras.cc.vt.edu ([198.82.162.117]) by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0G3Q0013I2RR8H@gkar.cc.vt.edu>; Wed, 8 Nov 2000 15:11:51 -0500 (EST) Date: Wed, 08 Nov 2000 15:10:56 -0500 From: flaw Subject: RE: system call and SYSCALL macro To: Raymond Law , Terry Lambert Cc: freebsd-hackers Message-id: <3A13684F@zathras.cc.vt.edu> MIME-version: 1.0 X-Mailer: WebMail (Hydra) SMTP v3.61 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-WebMail-UserID: flaw X-EXP32-SerialNo: 00002964 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am not using kld to implement my system call. I am just using the old way. But I tried using pointers also. But I am not getting the correct returned values either... >===== Original Message From Terry Lambert ===== >> I just try to add a simple system call for testing: >> >> int my_call(int x, int y) { >> return (x + y); >> } >> >> In my user program: >> >> int main(int argc, char ** argv) { >> int x = 3; >> int y = 8; >> int z = 0; >> z = syscall(SYS_my_call, x, y); >> printf("%i + %i = %i\n", x, y, z); >> return 0; >> } >> >> But it prints: >> >> 3 + 8 = -1 >> >> Can you give me some idea what I did wrong and what I should do? Also, can >> you tell me how to use the SYSCALL macro because I am not familiar with >> macros at all? Thanks in advance. > >Change this to: > >int >my_call(int x, int y, int *result) >{ > *result = x + y; > return( 0); >} > >int >main( int ac, char **av) >{ > int x = 3; > int y = 8; > int z = 0; > if( syscall(SYS_my_call, x, y, &z) != 0) { > perror("system call failed!"); > exit( 1); > } > printf("%i + %i = %i\n", x, y, z); > return 0; >} > >--- > >Since you aren't checking for failure of your system call, you >are confusing a failure of the call with an incorrect result. > >I suspect you will see the error "ENOENT", meaning that your >system call has not been loaded into the kernel, and had its >function pointer inserted into sysent[ SYS_my_call]. > >Look at the KLD documentation and examples on how to load >system calls into the kernel. see also "kldstat", which >should tell you where your system call was loaded (i.e. it >will give you the value you need to pass as "SYS_my_call" >to syscall(2) for things to work). > > > Terry Lambert > terry@lambert.org >--- >Any opinions in this posting are my own and not those of my present >or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 12:17:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id 4730537B479 for ; Wed, 8 Nov 2000 12:17:22 -0800 (PST) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id NAA03316; Wed, 8 Nov 2000 13:13:26 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpdAAA3vaqCg; Wed Nov 8 13:13:20 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id NAA25041; Wed, 8 Nov 2000 13:17:10 -0700 (MST) From: Terry Lambert Message-Id: <200011082017.NAA25041@usr08.primenet.com> Subject: Re: daemon() To: fjoe@iclub.nsu.ru (Max Khon) Date: Wed, 8 Nov 2000 20:17:09 +0000 (GMT) Cc: Don.Lewis@tsc.tdk.com (Don Lewis), andrew@ugh.net.au, hackers@FreeBSD.ORG In-Reply-To: from "Max Khon" at Nov 07, 2000 08:29:37 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > } > what is FD 4? > > } > > } I can't reproduce this? Does it always happen? > > > > It might be something that the shell forgets to close, so it will be > > dependent on which shell you use. > > exactly. this does not happen if I run this program from tcsh > (but does if I run from bash 1.14.7(1) built from ports > thanks! It appears to be a bash bug, with not setting close on exec on the fd it uses for its tty, in order to hide from shell scripts. The problem is that if you redirect input, bash has no tty on which to do reads, etc.. Feel lucky: it used to be worse. It uses to go out and try to get the highest posible fd for doing this crap, which meant waiting for it to eat up all of kernel memory chasing fd's until there was no more memory available for the per process open file table. All in all, bash is pretty buggy. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 12:19:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id 2506037B4C5 for ; Wed, 8 Nov 2000 12:19:39 -0800 (PST) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id NAA18682; Wed, 8 Nov 2000 13:18:38 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpdAAA5vaqAK; Wed Nov 8 13:18:27 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id NAA25082; Wed, 8 Nov 2000 13:19:07 -0700 (MST) From: Terry Lambert Message-Id: <200011082019.NAA25082@usr08.primenet.com> Subject: Re: SIGALARM is loosing when time are shifted. To: lev@serebryakov.spb.ru Date: Wed, 8 Nov 2000 20:19:07 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG (All) In-Reply-To: <7787.001107@serebryakov.spb.ru> from "Lev Serebryakov" at Nov 07, 2000 06:53:58 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > One my program use alarm() to interrupt some blocking system calls. > I use alarm(1) (one second). Everything works Ok, except cases, when > ntpdate shift time more than 1 second forward. If time is shifted > when alarm are set already, but not generated yet, SIGALARM doesn't > occur at all :( > Is it normal? No. This looks like a bug. When advancing the clock past timed events which are outstanding, it is supposed to trigger those events that would have occurred in the interim. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 12:29:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 922E937B479 for ; Wed, 8 Nov 2000 12:29:34 -0800 (PST) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 8CF436A901 for ; Wed, 8 Nov 2000 21:29:24 +0100 (CET) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id A91199F0226; Wed, 08 Nov 2000 21:35:29 +0100 Message-Id: <5.0.0.25.0.20001108211845.04d2d0a0@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 08 Nov 2000 21:29:03 +0100 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: post-install of kernal sources, maxusers max? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry to bother you hackers, but -questions isn't responding, and the handbook and Complete/Lehey don't, afaics, cover this situation explicitly. I can't really afford to screw up this production machine and start over from fresh disk, nor futz around for hours guessing what magik combo of post-install choices will do the trick. ========== I'm working, remotely, on a 4.1 system with only a binary install from cdrom. Now I need to do a custom kernal. Can the /stand/systinstall post-config option be used to put on all the developer source pkg without bothering the current config? which choice (I don't want X, just enough to build a custom kernal) It's in production as 200 K msgs/day mail hub. All I need to change, I think, is maxusers since we're getting this error from postfix: Nov 8 04:59:41 postfix/qmgr[16383]: fatal: socket: No buffer space available Nov 8 04:59:41 postfix/smtp[16872]: fatal: socket: No buffer space available Nov 8 05:00:58 postfix/qmgr[16876]: fatal: socket: No buffer space available The machine can get up 200 SMTP processes and 50 SMTPD processes simulatenously, 256 meg RAM. Increasing maxusers will fix this pb? afaic, maxusers can't be fixed with sysctl. Also, having been over /stand/systinstall a few times in last hour, there is no post-install choice that corresponds to an initial install "developer's sources less X and games", which is what I do when I install (this customer didn't follow my instructions for the initial insall). Also: On the postfix list, it seems someone has heard from several FreeBSD "experts" that FreeBSD should not be run at above maxusers = 128, while somebody else said they were running with 256 happily. Comments, please? Len http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 & 8.2.3 T6B for NT4 & W2K http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 12:33:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 3C39137B479 for ; Wed, 8 Nov 2000 12:33:55 -0800 (PST) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id NAA27119; Wed, 8 Nov 2000 13:30:25 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpdAAAshaW10; Wed Nov 8 13:30:15 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id NAA25455; Wed, 8 Nov 2000 13:33:33 -0700 (MST) From: Terry Lambert Message-Id: <200011082033.NAA25455@usr08.primenet.com> Subject: Re: close call in a device ? To: rizzo@aciri.org (Luigi Rizzo) Date: Wed, 8 Nov 2000 20:33:33 +0000 (GMT) Cc: bschwand@dvart.com (bruno schwander), freebsd-hackers@FreeBSD.ORG In-Reply-To: <200011080157.RAA00555@iguana.aciri.org> from "Luigi Rizzo" at Nov 07, 2000 05:57:02 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > when a process closes the device, I do not get a "close" call for each > > process closing the device. I instead get a close only on the last > > process closing the device. > > the reason for this is that you might have a process fork() after > it has opened the device, and you do not want to get to the > device all close calls from all processes generated by the original > one, but really only the last instance. > > The thing is, i think your model (allocating per-user resources on > open) is wrong. It cannot protect you from a process forking > and then having two instances using the same device. > > If you want multiple instances of the device, one option could be > to use the minor number and really create multiple instances > of the device, and open them in exclusive way so you know that > there can be only one open per device (you should scan available > devices in a similar way as the one is used for scanning pty's). To add to this, the close calls can be forces; there is a flag in the device structure wich can force notification. I'm not sure what it does over a fork(), though: I think you really want open notification. The main problem with per process resources is that the VFS that implements devices, specfs, doesn't own its own vnodes. This is actually the primary reason that VMWARE can only run one instance at a time of a virtual machine: there is no way to have per open instance resources, which are not shared. If you were to use the TFS flag (grep for TFS in the headers, that's a substring), you could make specfs own its own vnodes. The way you would handle your problem then is by returning a different instance of the device, with a different instance of per process attached storage. It's pretty simple to do this: just return a different vnode for the next open of the same device, instead of the same vnode with an additional reference. You will have to worry about close tracking in this case, as well. Other potential pitfalls are the directory name lookup cache returning a cached reference to the vnode from the last open (you will need to disable it), and the fork() and decriptor passing (using UNIX domain sockets) mechanisms, since what they return is a reference to the same reference, instead of a reference to a seperate, new reference (look at the per process open file table code to understand this). NB: If you are trying to do this for VMWARE or some other binary code, there's no way that the pty opening soloution suggested in the previous posting will be able to work for you, since the code will expect a particular behaviour. Right now, FreeBSD doesn't support this behaviour (cloning devices), but as pointed out above, it's not hard to implement, it's mostly just labor intensive. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 12:35:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 62A8837B479; Wed, 8 Nov 2000 12:35:49 -0800 (PST) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id NAA08515; Wed, 8 Nov 2000 13:33:53 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpdAAANbaiyq; Wed Nov 8 13:33:23 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id NAA25463; Wed, 8 Nov 2000 13:35:15 -0700 (MST) From: Terry Lambert Message-Id: <200011082035.NAA25463@usr08.primenet.com> Subject: Re: close call in a device ? To: msmith@FreeBSD.ORG (Mike Smith) Date: Wed, 8 Nov 2000 20:35:14 +0000 (GMT) Cc: bschwand@dvart.com (bruno schwander), freebsd-hackers@FreeBSD.ORG In-Reply-To: <200011080305.eA835rF34155@mass.osd.bsdi.com> from "Mike Smith" at Nov 07, 2000 07:05:53 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If I understand you correctly, you have multiple processes all of which > are going to try to open /dev/foo, and you want them to behave as though > they have each opened a unique device? > > You can't do this with FreeBSD, or with many other Unixes. Any SVR4 system can support this. So can AIX. > Arguably, this is a defect with the device model. If you are trying to > fake up concurrent access to a device, and the client processes are only > going to read and write (no ioctls) to this device, then you can use a > fifo and a multiplexor process. > > Alternatively, and this would be recommended; fix the client program. Or fix the device model. You can't have multiple VMWARE sessions in FreeBSD today because of this defect in the device model. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 12:39:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 776CD37B4D7; Wed, 8 Nov 2000 12:39:12 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp241.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eA8Kd4H00604; Wed, 8 Nov 2000 12:39:04 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 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, 08 Nov 2000 12:39:32 -0800 (PST) From: John Baldwin To: John Baldwin Subject: RE: PSE/PAE support Cc: hackers@FreeBSD.org, Jeroen Ruigrok van der Werven Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Nov-00 John Baldwin wrote: > I'm sure Peter can correct this and fill in any holes as well as offer > guidance to anyone who is masochistic enough^W^Wwilling to work on this. Well, I didn't get all the facts quite right *sigh*. The page directory pointer table actually contains 4 entries which are indexed by the upper 2 bits of the virtual linear address. Also, one thing I failed to mention is that the choice between small and large pages is made via the PS bit in the page directory table entry that points to either a large page or a page table. And my table of page-sizes was a little off, it looks like this: Page Size Table: | Small Pages | Large Pages --------------------------------------- Normal | 4k | 4k PSE | 4k | 4m PAE | 4k | 2m PAE + PSE | 4k | 4m Now, if we look at how the virtual address is split up when using PAE for a large page: 31 30 29 21 20 0 ----------------------------------------------- | | | | ----------------------------------------------- ^ ^ ^ | | `----------------- offset within the page | `------------------------------------- index into the page directory `--------------------------------------------- index into the page directory pointer table This means that large pages with PAE have a 21-bit offset. That only allows for a 2mb offset, so I'm not sure how one goes about addressing the upper 2mb of a 4mb page then. *scratches head* -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "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 Nov 8 12:58:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 921FA37B479 for ; Wed, 8 Nov 2000 12:58:22 -0800 (PST) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id NAA08954; Wed, 8 Nov 2000 13:54:55 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpdAAA7baGir; Wed Nov 8 13:54:41 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id NAA26096; Wed, 8 Nov 2000 13:57:57 -0700 (MST) From: Terry Lambert Message-Id: <200011082057.NAA26096@usr08.primenet.com> Subject: Re: system call and SYSCALL macro To: flaw@vt.edu (flaw) Date: Wed, 8 Nov 2000 20:57:57 +0000 (GMT) Cc: rlaw@vt.edu (Raymond Law), tlambert@primenet.com (Terry Lambert), freebsd-hackers@FreeBSD.ORG (freebsd-hackers) In-Reply-To: <3A13684F@zathras.cc.vt.edu> from "flaw" at Nov 08, 2000 03:10:56 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am not using kld to implement my system call. I am just using > the old way. > > But I tried using pointers also. But I am not getting the correct > returned values either... The correct return value is probably "-1", with the value of 'z' being undefined, for what you have now. If you are not KLD'in your system call, how are you informing the kernel of its existance? The normal way this is done is to modify /sys/kern/syscalls.master, e.g.: 180 STD NOHIDE { int my_call(int x, int y, int *z); } And building a new kernel, after making sure that syscalls.c is regenerated from syscalls.master, and that your .c file that implements "my_call" is included in the kernel compilation. Examine the sysent[] array created from syscalls.master during the build process (down in your kernel compile directory) to make sure that it was put in there; if it wasn't go back and try again until it is. Once you have built a kernel that has your entry in it, you will need to install it and boot off it (I suggest using the name "kernel.test" as the installed kernel name, so that if you screw up, your default kernel will still boot, and so you can ignore it at boot time, when you switch to KLDs). Really, you want to use KLDs for this. If you are adamant about not using KLDs, remember: don't bother even trying to boot your new kernel, if there isn't a "my_call" listed in syscalls.c or its function pointer is not in the sysent[] array. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 13: 4:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id 0A4FA37B479 for ; Wed, 8 Nov 2000 13:04:38 -0800 (PST) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id OAA06749; Wed, 8 Nov 2000 14:03:40 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpdAAATeaqan; Wed Nov 8 14:03:26 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA26181; Wed, 8 Nov 2000 14:04:19 -0700 (MST) From: Terry Lambert Message-Id: <200011082104.OAA26181@usr08.primenet.com> Subject: Re: bsd.prog.mk and /usr/local/include To: andrew@ugh.net.au Date: Wed, 8 Nov 2000 21:04:19 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "andrew@ugh.net.au" at Nov 04, 2000 12:00:50 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What is the proper way to get the C compiler to look in ${PREFIX}/include > for header files and ${PREFIX}/lib for libraries when using bsd.prog.mk? > > I can just use CFLAGS+= -I${PREFIX}/include -L${PREFIX}/lib but I suspect > there may be a better way. grepping for -I in bsd.prog.mk didn't show up > much however. Depends on why you are doing it. If you are using a compiler that is not the default compiler, and setting DESTDIR, you will have to set it by doctoring the CC line itself, since DESTDIR will cause your include path and library path to be overridden in this case (I saw this while using a newer g++ for exception handling and RTTI). If you are doing it for any other reason, setting CFLAGS for the include path and LDFLAGS for the library path is probably the right way to do it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 13:16:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id F201237B479 for ; Wed, 8 Nov 2000 13:16:37 -0800 (PST) Received: from casablanca-51.budapest.interware.hu ([195.70.53.51] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13tca6-0005DI-00; Wed, 08 Nov 2000 22:16:31 +0100 Message-ID: <3A094107.624361F4@elischer.org> Date: Wed, 08 Nov 2000 04:03:19 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Jacques Fourie Cc: freebsd-hackers@freebsd.org Subject: Re: kernel stack size? References: <20001107132009.23436.qmail@web3504.mail.yahoo.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jacques Fourie wrote: > > Hi > > Please excuse any silly questions, but I am stuck with > a problem that I can't find the answer for. > > I wrote a KLD module that performs encryption on > network packets in the kernel. Packets are intercepted > for encryption on a ethernet level (in ether_input() > and ether_output_frame() respectively). This module is > implemented on 4.1.1-RELEASE. > > For input packets I added my own NETISR as well as > interrupt queue. In the ether_input() routine the > packets are queued and a software interrupt scheduled. > Further processing on the packet then happens at a > priority of splnet(). Why are you not using the netgraph system, which was specifically designed for this? it allows you to divert eherne packets through your own arbitrary processing modules and to even pass then to userland for processing if you want. you can do this without editing any other file in the kernel, since netgraph modules can be loaded, and there is already a netgraph tap point in the ethernet system. Netgraph will also aoutomatically do all the queueing you require. > > If I do bulk data transfers (encrypted) everything > works fine until I run a shell script that does a > 'ls -lR' in an infinite loop. A few "virtual time > alarm" messages appear and then a kernel panic. > Looking at the DDB output, it seems a lot like a > kernel stack overflow has resulted. Very strange > values for ebp and page faults on stack accesses is > making me think along these lines. Generally you have very little kernel stack. you should use MALLOC'd regions for workspace if you need it. in 4.x and earlier, the NETISR code will run on whatever stack is presently in use so if you are running something that uses a lot of stack already, it may find that there is not enough left. > > Does anyone know where I can find more information > about the kernel stack at interrupt time (such as the > maximum size)? > I'm also not quite sure what the "virtual time alarm" > messages mean, can anyone help me out? > > jacques > > __________________________________________________ > Do You Yahoo!? > Thousands of Stores. Millions of Products. All in one Place. > http://shopping.yahoo.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 13:16:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 0D79837B4D7; Wed, 8 Nov 2000 13:16:42 -0800 (PST) Received: from casablanca-51.budapest.interware.hu ([195.70.53.51] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13tca0-0005D1-00; Wed, 08 Nov 2000 22:16:25 +0100 Message-ID: <3A09C290.DC5F0E3A@elischer.org> Date: Wed, 08 Nov 2000 13:16:00 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Terry Lambert Cc: Mike Smith , bruno schwander , freebsd-hackers@FreeBSD.ORG Subject: Re: close call in a device ? References: <200011082035.NAA25463@usr08.primenet.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > If I understand you correctly, you have multiple processes all of which > > are going to try to open /dev/foo, and you want them to behave as though > > they have each opened a unique device? > > > > You can't do this with FreeBSD, or with many other Unixes. > > Any SVR4 system can support this. So can AIX. > > > Arguably, this is a defect with the device model. If you are trying to > > fake up concurrent access to a device, and the client processes are only > > going to read and write (no ioctls) to this device, then you can use a > > fifo and a multiplexor process. > > > > Alternatively, and this would be recommended; fix the client program. > > Or fix the device model. You can't have multiple VMWARE sessions > in FreeBSD today because of this defect in the device model. I believe that this is not the reason.. it's another resource that we only have globally.. (i.e. once) but I forget what it is.. the problem here can be solved by using Poul's 'cloning device' interface in the driver. I don't think he has it quite completed but it is partly there.. maybe enough.. only in -current at the moment and you need to have devfs turned on. each time you open it, you actually get a different device and vnode.. > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 13:22:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id 4F6C837B479 for ; Wed, 8 Nov 2000 13:22:35 -0800 (PST) Received: (qmail 45888 invoked by uid 1000); 8 Nov 2000 21:22:34 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 Nov 2000 21:22:34 -0000 Date: Wed, 8 Nov 2000 15:22:34 -0600 (CST) From: Mike Silbersack To: Len Conrad Cc: freebsd-hackers@freebsd.org Subject: Re: post-install of kernal sources, maxusers max? In-Reply-To: <5.0.0.25.0.20001108211845.04d2d0a0@mail.Go2France.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Nov 2000, Len Conrad wrote: > All I need to change, I think, is maxusers since we're getting this > error from postfix: > > Nov 8 04:59:41 postfix/qmgr[16383]: fatal: socket: No buffer space available > Nov 8 04:59:41 postfix/smtp[16872]: fatal: socket: No buffer space available > Nov 8 05:00:58 postfix/qmgr[16876]: fatal: socket: No buffer space available > > The machine can get up 200 SMTP processes and 50 SMTPD processes > simulatenously, 256 meg RAM. > > Increasing maxusers will fix this pb? afaic, maxusers can't be fixed > with sysctl. I think you can up the mbuf related settings while the system is running. Give it a try. The two sysctls you'll want to fiddle with are: kern.ipc.nmbclusters kern.ipc.nmbufs You can determine which is needed more through a quick netstat -m. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 13:31:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from front3m.grolier.fr (front3m.grolier.fr [195.36.216.53]) by hub.freebsd.org (Postfix) with ESMTP id AB71E37B479; Wed, 8 Nov 2000 13:31:40 -0800 (PST) Received: from nas7-126.vlt.club-internet.fr (nas7-126.vlt.club-internet.fr [194.158.109.126]) by front3m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA02471; Wed, 8 Nov 2000 22:31:30 +0100 (MET) Date: Wed, 8 Nov 2000 21:31:58 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: oneflower Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG, Pam Delaney Subject: Re: a problem about install freebsd 4.1.1 on HP Lpr? In-Reply-To: <001701c04991$87ea03c0$656e6dca@oneflower> Message-ID: 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 X-Loop: FreeBSD.ORG Looks like both the NetRaid firmware and the `sym' driver are in love with the 895. If I am right, such an evil competition obviously disallows both of them to succeed their aim. :-) Given this message, > Symbios,Inc.Pci boot Rom ,no supported devices found. The Symbios BIOS seems to detect the situation just fine and discard the 895. For now, I donnot know how it does, but may-be Pamela knows. G=E9rard. On Wed, 8 Nov 2000, oneflower wrote: > Hello,every one: >=20 > I have meet a problem when I am installing FreeBSD 4.1.1 on HP LPR. >=20 > HP LPR: >=20 > cpu: PIII 650MHZ *2 > memory:384MB > Disk : 9G scsi-2 *2 > Scsi card: HP NetRaid 1si > scsi card without raid (HP) >=20 > PhoenixBIOS 4.06.34 PR > Symbios,Inc.SDMS (TM) v4.0 PCI SCSI BIOS,PCI Rev. 2.0 ,2.1 > Copyright 1995 ,1998 Symbios,Inc. > PCI-4.14.04 >=20 > Symbios,Inc.Pci boot Rom ,no supported devices found. >=20 > HP NetRAID Adapter BIOS VER B.02.02 Apr 03,2000 > Copyright(c) American MegaTrends,Inc. >=20 >=20 >=20 > the install process stop at this screen: >=20 > ".......................................... > fxp0: port 0x9400-0x943f mem 0xfa100000-= 0xfa1fffff, > 0xfa200000-0xfa2fffff irq 11 at device 3.0 on pci1 > fxp0: Ethernet address 00:d0:b7:91:20:d2 > sym0: <895> port 0x9000-0x90ff mem 0xfa201000-0xfa201fff,0xfa202000-0xfa2= 020ff=20 > irq 15 at device 4.0 on pci1" > =20 >=20 > after a long time ,it repeated messages on screen like : >=20 > "....... > (noperiph: sym0:0:-1:-1): SCSI BUS mode change from SE to SE > sym0:0:iph:sym OUT phase after..........." >=20 >=20 >=20 > What problem? Who can help me? >=20 > The Lpr can be installed with windows 2000 Adv Server,run well but boot w= indows > needs a lot of time. > I can't install Redhat 7.0 on it ,too. > It stoped at load scsi driver. >=20 >=20 > Best Regards, >=20 > Flower > N=85'=B2=E6=ECr=B8=9B{=FB=1E=9D=D9=9A=8A[h=99=A8=E8=AD=DA&=A3=F1ky=E0R=0F= =FA+=83=08=AD=87=FB=A7=B2=E6=ECr=B8=9By=FA=DEy=BB=1D=FE=16=9C=91=EA=EC=FE)= =ED=85=E6=E8w*=1F=B6=17=A6z=CB=1A >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 13:33: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 3009C37B4C5 for ; Wed, 8 Nov 2000 13:33:01 -0800 (PST) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id CBD396A901; Wed, 8 Nov 2000 22:32:58 +0100 (CET) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id A7F6A92023E; Wed, 08 Nov 2000 22:39:02 +0100 Message-Id: <5.0.0.25.0.20001108222155.0252ceb0@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 08 Nov 2000 22:32:55 +0100 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: Re: post-install of kernal sources, maxusers max? Cc: Ian Dowse In-Reply-To: <200011082116.aa66725@salmon.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In message <5.0.0.25.0.20001108211845.04d2d0a0@mail.Go2France.com>,=20 >Len Conrad >writes: > > >All I need to change, I think, is maxusers since we're getting this > >error from postfix: > >You may be able to increase these limits without recompiling the >kernel, by using kernel environment variables set in /boot/loader.rc. > >First of all you need to find out exactly what resource is getting >exhausted. I suspect it is the socket space memory zone, but you can >verify this with the commands: > > vmstat -z |grep ^socket # vmstat -z ZONE used total mem-use PIPE 36 102 5/15K SWAPMETA 8 50 1/7K tcpcb 179 350 95/185K unpcb 418 896 26/56K ripcb 0 42 0/7K tcpcb 0 0 0/0K udpcb 10 168 1/31K socket 607 1050 113/196K KNOTE 6 256 0/16K NFSNODE 0 0 0/0K NFSMOUNT 0 0 0/0K VNODE 4006 4028 751/755K NAMEI 0 40 0/40K VMSPACE 260 384 48/72K PROC 264 343 107/139K DP fakepg 0 0 0/0K PV ENTRY 53272 79979 1456/2186K MAP ENTRY 3117 3953 146/185K KMAP ENTRY 804 978 37/45K MAP 7 10 0/1K VM OBJECT 4907 5464 460/512K ------------------------------------------ TOTAL 3252/4455K Do you see anything else up there that looks bad or =FCber limit? > sysctl kern.ipc.maxsockets # sysctl kern.ipc.maxsockets kern.ipc.maxsockets: 1064 >If the 'max' column in the vmstat output matches the number returned >by sysctl, then the kernel has hit this limit at some stage. doesn't look like it to me. >To increase the limit, pick a new larger value, and add a line to >/boot/loader.rc e.g. > > set kern.ipc.maxsockets=3D5000 > >You will need to reboot for this setting to take effect, and it is not >possible to dynamically increase the limit in a running kernel. > >Other settings worth investigating are nmbclusters and nmbufs. These >are viewable via 'netstat -m', and can be set as above. # netstat -m 358/960/4096 mbufs in use (current/peak/max): 198 mbufs allocated to data 160 mbufs allocated to packet headers 185/504/1024 mbuf clusters in use (current/peak/max) 1248 Kbytes allocated to network (36% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines So what do you think postfix is complaining about, more precisely,=20 how to fix it: Fatal Errors (postfix) ------------ bounce 1 socket: No buffer space available qmgr 7 socket: No buffer space available script 1 usage: postfix start (or stop, reload, abort, flush, or check) smtp 5 socket: No buffer space available 3 inet_addr_local: socket: No buffer space available smtpd 6 socket: No buffer space available Thanks, Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 13:40:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 707D337B4C5 for ; Wed, 8 Nov 2000 13:40:26 -0800 (PST) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id QAA81436; Wed, 8 Nov 2000 16:40:18 -0500 (EST) Date: Wed, 8 Nov 2000 16:40:18 -0500 (EST) From: To: Mike Silbersack Cc: Len Conrad , freebsd-hackers@FreeBSD.ORG Subject: Re: post-install of kernal sources, maxusers max? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Nov 2000, Mike Silbersack wrote: > > The machine can get up 200 SMTP processes and 50 SMTPD processes > > simulatenously, 256 meg RAM. > > > > Increasing maxusers will fix this pb? afaic, maxusers can't be fixed > > with sysctl. > > I think you can up the mbuf related settings while the system is > running. Give it a try. The two sysctls you'll want to fiddle with are: > > kern.ipc.nmbclusters > kern.ipc.nmbufs Nope. Those are read only at least on my 4.2-BETA kernel. I am running into the same problem during my benchmarking. I also thought that a change in the past made the mbuf cluters tuneable on a running machine. Hmm maybe I am wrong. However Im not sure that is the problem. I have: [open-systems]:/home/chris> netstat -m 5/2000/6144 mbufs in use (current/peak/max): 1 mbufs allocated to data 4 mbufs allocated to packet headers 0/1096/1536 mbuf clusters in use (current/peak/max) I still have free mbuf's yet get the same error trying to make postfix bleed to death: [open-systems]:/home/chris> /usr/bin/time -p smtp-source -s 10000 -l 100000 -m 1000 -c -f chris@localhost -t null@localhost localhost smtp-source: fatal: socket: No buffer space available I also get: [open-systems]:/home/chris> /usr/bin/time -p smtp-source -s 10000 -l 100000 -m 1000 -c -f chris@localhost -t null@localhost localhost smtp-source: fatal: lost connection while sending sender I am working on figuring out what the magic combo is to get postfix to really doll out connections on FreeBSD. ============================================================================= -Chris Watson (316) 326-3862 | FreeBSD Consultant, FreeBSD Geek Work: scanner@jurai.net | Open Systems Inc., Wellington, Kansas Home: scanner@deceptively.shady.org | http://open-systems.net ============================================================================= WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tommorow?" BSD: "Are you guys coming or what?" ============================================================================= irc.openprojects.net #FreeBSD -Join the revolution! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 13:46:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 019CC37B479 for ; Wed, 8 Nov 2000 13:46:38 -0800 (PST) Received: from boole.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Nov 2000 21:46:34 +0000 (GMT) To: Len Conrad Cc: freebsd-hackers@freebsd.org, Ian Dowse Subject: Re: post-install of kernal sources, maxusers max? In-Reply-To: Your message of "Wed, 08 Nov 2000 22:32:55 +0100." <5.0.0.25.0.20001108222155.0252ceb0@mail.Go2France.com> Date: Wed, 08 Nov 2000 21:46:34 +0000 From: Ian Dowse Message-ID: <200011082146.aa69533@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5.0.0.25.0.20001108222155.0252ceb0@mail.Go2France.com>, Len Conrad writes: ># vmstat -z ... >socket 607 1050 113/196K ... >kern.ipc.maxsockets: 1064 >doesn't look like it to me. I think a few slots are reserved, so you can consider 1050 as being equal to 1064. Try putting set kern.ipc.maxsockets=4000 in /boot/loader.rc and rebooting. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 13:47:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 3334437B479 for ; Wed, 8 Nov 2000 13:47:54 -0800 (PST) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 826FA6A901; Wed, 8 Nov 2000 22:47:53 +0100 (CET) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id AB75A010226; Wed, 08 Nov 2000 22:53:57 +0100 Message-Id: <5.0.0.25.0.20001108224536.02526a20@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 08 Nov 2000 22:47:50 +0100 To: Mike Silbersack From: Len Conrad Subject: Re: post-install of kernal sources, maxusers max? Cc: freebsd-hackers@freebsd.org In-Reply-To: References: <5.0.0.25.0.20001108211845.04d2d0a0@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >kern.ipc.nmbclusters >kern.ipc.nmbufs # sysctl -w kern.ipc.nmbclusters=2048 sysctl: oid 'kern.ipc.nmbclusters' is read only # sysctl -w kern.ipc.nmbufs=8192 sysctl: oid 'kern.ipc.nmbufs' is read only I'll have to reboot, >You can determine which is needed more through a quick netstat -m. # netstat -m 367/960/4096 mbufs in use (current/peak/max): 189 mbufs allocated to data 178 mbufs allocated to packet headers 150/504/1024 mbuf clusters in use (current/peak/max) 1248 Kbytes allocated to network (31% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines question still is what postfix is missing. I guess I better try to postfix list again. Thanks, Silby Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 13:54:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id C742737B4C5 for ; Wed, 8 Nov 2000 13:54:30 -0800 (PST) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id E8C7D6A901; Wed, 8 Nov 2000 22:54:29 +0100 (CET) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id AD02B7D028A; Wed, 08 Nov 2000 23:00:34 +0100 Message-Id: <5.0.0.25.0.20001108225200.02526630@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 08 Nov 2000 22:54:27 +0100 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: Re: post-install of kernal sources, maxusers max? Cc: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > kern.ipc.nmbclusters > > kern.ipc.nmbufs > > Nope. Those are read only at least on my 4.2-BETA kernel. read-only also in 4.1 # sysctl -w kern.ipc.nmbclusters=2048 sysctl: oid 'kern.ipc.nmbclusters' is read only # sysctl -w kern.ipc.nmbufs=8192 sysctl: oid 'kern.ipc.nmbufs' is read only >I am running into the same problem during my benchmarking. I also thought >that a change in the past made the mbuf cluters tuneable on a running >machine. Hmm maybe I am wrong. However Im not sure that is the problem. I >have: > >[open-systems]:/home/chris> netstat -m >5/2000/6144 mbufs in use (current/peak/max): > 1 mbufs allocated to data > 4 mbufs allocated to packet headers >0/1096/1536 mbuf clusters in use (current/peak/max) > >I still have free mbuf's yet get the same error trying to make postfix >bleed to death: > >[open-systems]:/home/chris> /usr/bin/time -p smtp-source -s 10000 -l >100000 -m 1000 -c -f chris@localhost -t null@localhost localhost >smtp-source: fatal: socket: No buffer space available yep, me, too, can't see exactly what postfix is bitching about: # netstat -m 367/960/4096 mbufs in use (current/peak/max): 189 mbufs allocated to data 178 mbufs allocated to packet headers 150/504/1024 mbuf clusters in use (current/peak/max) 1248 Kbytes allocated to network (31% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines If you learn something, let me know, please. Thanks Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 14: 6:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id A6C2337B479 for ; Wed, 8 Nov 2000 14:06:51 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eA8M6iZ26117; Wed, 8 Nov 2000 14:06:44 -0800 (PST) Date: Wed, 8 Nov 2000 14:06:44 -0800 From: Alfred Perlstein To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: post-install of kernal sources, maxusers max? Message-ID: <20001108140644.Y5112@fw.wintelcom.net> References: <5.0.0.25.0.20001108211845.04d2d0a0@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <5.0.0.25.0.20001108211845.04d2d0a0@mail.Go2France.com>; from lconrad@Go2France.com on Wed, Nov 08, 2000 at 09:29:03PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Len Conrad [001108 12:29] wrote: > Sorry to bother you hackers, but -questions isn't responding, and the > handbook and Complete/Lehey don't, afaics, cover this situation > explicitly. I can't really afford to screw up this production > machine and start over from fresh disk, nor futz around for hours > guessing what magik combo of post-install choices will do the trick. > > ========== > > I'm working, remotely, on a 4.1 system with only a binary install from cdrom. > > Now I need to do a custom kernal. Can the /stand/systinstall kernel! :) > post-config option be used to put on all the developer source pkg > without bothering the current config? which choice (I don't want X, > just enough to build a custom kernal) > > It's in production as 200 K msgs/day mail hub. > > All I need to change, I think, is maxusers since we're getting this > error from postfix: > > Nov 8 04:59:41 postfix/qmgr[16383]: fatal: socket: No buffer space available > Nov 8 04:59:41 postfix/smtp[16872]: fatal: socket: No buffer space available > Nov 8 05:00:58 postfix/qmgr[16876]: fatal: socket: No buffer space available > > The machine can get up 200 SMTP processes and 50 SMTPD processes > simulatenously, 256 meg RAM. > > Increasing maxusers will fix this pb? afaic, maxusers can't be fixed > with sysctl. Yes, but nmbclusters can, see the loader(8) manpage for the tunables to raise kern.ipc.nmbclusters, you might have better luck setting it to 32768. > Also: > > On the postfix list, it seems someone has heard from several FreeBSD > "experts" that FreeBSD should not be run at above maxusers = 128, > while somebody else said they were running with 256 happily. There was a very short period where FreeBSD 3.x wouldn't work properly when maxusers was above 256, but that hasn't been an issue for quite some time. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 14:22:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 8762B37B479 for ; Wed, 8 Nov 2000 14:22:23 -0800 (PST) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id RAA82254; Wed, 8 Nov 2000 17:22:19 -0500 (EST) Date: Wed, 8 Nov 2000 17:22:18 -0500 (EST) From: To: Alfred Perlstein Cc: Len Conrad , freebsd-hackers@FreeBSD.ORG Subject: Re: post-install of kernal sources, maxusers max? In-Reply-To: <20001108140644.Y5112@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Nov 2000, Alfred Perlstein wrote: > Yes, but nmbclusters can, see the loader(8) manpage for the tunables > to raise kern.ipc.nmbclusters, you might have better luck setting > it to 32768. Is it possible to make the tuning of nmbclusters available after the kenrel is loaded. So that you don't have to reboot a server to get loader's changes to take effect? > when maxusers was above 256, but that hasn't been an issue for quite > some time. So one could go as high as.. 512? 1024? There has to still be drawbacks at some number where your wasting resources that you dont need just to get more mbuf's. I think that is why they are saying dont just jack up MAXUSERS. Use the NMBCLUSTERS=XXXX instead. Because that is usually the variable you want increased not the other parameters MAXUSERS increases. ============================================================================= -Chris Watson (316) 326-3862 | FreeBSD Consultant, FreeBSD Geek Work: scanner@jurai.net | Open Systems Inc., Wellington, Kansas Home: scanner@deceptively.shady.org | http://open-systems.net ============================================================================= WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tommorow?" BSD: "Are you guys coming or what?" ============================================================================= irc.openprojects.net #FreeBSD -Join the revolution! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 14:23: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id 29A0737B479 for ; Wed, 8 Nov 2000 14:23:08 -0800 (PST) Received: from yoda.sftw.com (yoda.sftw.com [209.157.37.211]) by guardian.sftw.com (8.11.0/8.11.0) with ESMTP id eA8MMtq19261 for ; Wed, 8 Nov 2000 14:22:55 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.11.0/8.11.0) with ESMTP id eA8MMsq41799 for ; Wed, 8 Nov 2000 14:22:55 -0800 (PST) (envelope-from nsayer@sftw.com) Message-ID: <3A09D23E.6EA4390D@sftw.com> Date: Wed, 08 Nov 2000 14:22:54 -0800 From: Nick Sayer X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: RPC not taking the same service twice: a bug or a security measure? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A coworker seems to have found an issue with portmap on FreeBSD. Aparently, if you try and register the same service twice, but with different protocols (UDP vs TCP), it doesn't work. I'm not entirely sure I believe this, and I am digging for more details, but I am writing to see if anyone can tell me anything that will save me having to do the investigative work. :-) I'll follow up with more details as I can. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 14:55:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 965A337B479 for ; Wed, 8 Nov 2000 14:55:15 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eA8Mt7C27915; Wed, 8 Nov 2000 14:55:07 -0800 (PST) Date: Wed, 8 Nov 2000 14:55:06 -0800 From: Alfred Perlstein To: scanner@jurai.net Cc: Len Conrad , freebsd-hackers@FreeBSD.ORG Subject: Re: post-install of kernal sources, maxusers max? Message-ID: <20001108145506.Z5112@fw.wintelcom.net> References: <20001108140644.Y5112@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from scanner@jurai.net on Wed, Nov 08, 2000 at 05:22:18PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * scanner@jurai.net [001108 14:22] wrote: > On Wed, 8 Nov 2000, Alfred Perlstein wrote: > > > Yes, but nmbclusters can, see the loader(8) manpage for the tunables > > to raise kern.ipc.nmbclusters, you might have better luck setting > > it to 32768. > > Is it possible to make the tuning of nmbclusters available after > the kenrel is loaded. So that you don't have to reboot a server to get > loader's changes to take effect? Nope. > > > when maxusers was above 256, but that hasn't been an issue for quite > > some time. > > So one could go as high as.. 512? 1024? There has to still be > drawbacks at some number where your wasting resources that you dont need > just to get more mbuf's. I think that is why they are saying dont just > jack up MAXUSERS. Use the NMBCLUSTERS=XXXX instead. Because that is > usually the variable you want increased not the other parameters MAXUSERS > increases. I've never had to set maxusers higher than 512 and 256 would have probably been fine. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 15: 3:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 1262D37B479 for ; Wed, 8 Nov 2000 15:03:39 -0800 (PST) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.11.0/8.11.1) with ESMTP id eA8N3cf21878 for ; Wed, 8 Nov 2000 15:03:38 -0800 (PST) (envelope-from nsayer@medusa.kfu.com) Received: (from nsayer@localhost) by medusa.kfu.com (8.11.0/8.11.0) id eA8N3c193540 for freebsd-hackers@freebsd.org; Wed, 8 Nov 2000 15:03:38 -0800 (PST) (envelope-from nsayer) Date: Wed, 8 Nov 2000 15:03:38 -0800 (PST) From: Nick Sayer Message-Id: <200011082303.eA8N3c193540@medusa.kfu.com> To: freebsd-hackers@freebsd.org Subject: KDE2, konsole_grantpty and FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG KDE2 uses a utility called "konsole_grantpty". This is an suid program. Its job is to chown the master side (/dev/pty??) of the pty pair for konsole, which is KDE's "xterm" sort of thing. By isolating this action in a child, konsole itself does not require suid. konsole_grantpty does its job by performing the actions called for on ttyname(3) (that is, it is passed a file descriptor on fd 3 of the device it needs to fiddle). The problem is that ttyname() fails on all /dev/pty?? devices. This is because the first thing ttyname does is perform a tcgetattr() to see if it's really a terminal or not. This fails. So something has to give. Either konsole_grantpty has to find some other way of turning a file descriptor into a /dev entry in a way that can't be exploited by someone else redirecting stuff into it, or ttyname() has to be made a bit more lax, or pty's have to look like tty's to ttyname(). Anyone have any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 15:18:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orthanc.ab.ca (207-167-15-66.dsl.worldgate.ca [207.167.15.66]) by hub.freebsd.org (Postfix) with ESMTP id B3E4237B479 for ; Wed, 8 Nov 2000 15:18:44 -0800 (PST) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.11.0/8.11.0.Beta3) with ESMTP id eA8NIHN25708; Wed, 8 Nov 2000 16:18:17 -0700 (MST) Message-Id: <200011082318.eA8NIHN25708@orthanc.ab.ca> To: scanner@jurai.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: post-install of kernal sources, maxusers max? In-reply-to: Your message of "Wed, 08 Nov 2000 17:22:18 EST." Date: Wed, 08 Nov 2000 16:18:16 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "scanner" == writes: scanner> So one could go as high as.. 512? 1024? There has to scanner> still be drawbacks at some number where your wasting scanner> resources that you dont need just to get more mbuf's. I scanner> think that is why they are saying dont just jack up scanner> MAXUSERS. Use the NMBCLUSTERS=XXXX instead. Because that scanner> is usually the variable you want increased not the other scanner> parameters MAXUSERS increases. FWIW I run our NFS server with NMBCLUSTERS=10000. It doesn't burn that much additional memory. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 15:54:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (dhcp244.osd.bsdi.com [204.216.28.244]) by hub.freebsd.org (Postfix) with ESMTP id 7DD5237B479 for ; Wed, 8 Nov 2000 15:54:36 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eA900F311423 for ; Wed, 8 Nov 2000 16:00:15 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011090000.eA900F311423@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: PCI interrupt routing across PCI:PCI bridges Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_14741562390" Date: Wed, 08 Nov 2000 16:00:15 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_14741562390 Content-Type: text/plain; charset=us-ascii Following is a patch to route interrupts for devices on the child side of a PCI:PCI bridge. I don't have any easy way to test this, unfortunately. If anyone would care to eyeball it before I commit it, I'd greatly appreciate that. --==_Exmh_14741562390 Content-Type: text/plain ; name="pcisupport.diff"; charset=us-ascii Content-Description: pcisupport.diff Content-Disposition: attachment; filename="pcisupport.diff" Index: pcisupport.c =================================================================== RCS file: /local0/src/src/sys/pci/pcisupport.c,v retrieving revision 1.177 diff -u -r1.177 pcisupport.c --- pcisupport.c 2000/10/29 16:27:40 1.177 +++ pcisupport.c 2000/11/08 23:36:33 @@ -831,6 +831,42 @@ b, s, f, reg, val, width); } +/* + * Route an interrupt across a PCI bridge. + */ +static int +pcib_route_interrupt(device_t dev, int device, int pin) +{ + device_t bridge, bus; + int parent_intpin; + int intnum; + + /* + * + * The PCI standard defines a swizzle of the child-side device/intpin to + * the parent-side intpin as follows. + * + * device = device on child bus + * child_intpin = intpin on child bus slot (0-3) + * parent_intpin = intpin on parent bus slot (0-3) + * + * parent_intpin = (device + child_intpin) % 4 + */ + parent_intpin = (pci_get_slot(dev) + (pin - 1)) % 4; + + /* + * Our parent is a PCI bus. Its parent must export the pcib interface + * which includes the ability to route interrupts. + */ + bridge = device_get_parent(dev); + bus = device_get_parent(bridge); + intnum = PCIB_ROUTE_INTERRUPT(device_get_parent(bus), + pci_get_slot(bridge), parent_intpin + 1); + device_printf(bridge, "routed slot %d INT%c to irq %d\n", pci_get_slot(dev), + 'A' + pin - 1, intnum); + return(intnum); +} + static device_method_t pcib_methods[] = { /* Device interface */ DEVMETHOD(device_probe, pcib_probe), @@ -854,6 +890,7 @@ DEVMETHOD(pcib_maxslots, pcib_maxslots), DEVMETHOD(pcib_read_config, pcib_read_config), DEVMETHOD(pcib_write_config, pcib_write_config), + DEVMETHOD(pcib_route_interrupt, pcib_route_interrupt), { 0, 0 } }; --==_Exmh_14741562390 Content-Type: text/plain; charset=us-ascii ... 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] V I C T O R Y N O T V E N G E A N C E --==_Exmh_14741562390-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 15:59:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 83C6D37B479 for ; Wed, 8 Nov 2000 15:59:28 -0800 (PST) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G3Q0025NDAXO0@falla.videotron.net> for freebsd-hackers@FreeBSD.ORG; Wed, 8 Nov 2000 18:59:21 -0500 (EST) Date: Wed, 08 Nov 2000 19:04:15 -0500 (EST) From: Bosko Milekic Subject: Re: post-install of kernal sources, maxusers max? In-reply-to: X-Sender: bmilekic@jehovah.technokratis.com To: Mike Silbersack Cc: Len Conrad , freebsd-hackers@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Nov 2000, Mike Silbersack wrote: > I think you can up the mbuf related settings while the system is > running. Give it a try. The two sysctls you'll want to fiddle with are: > > kern.ipc.nmbclusters > kern.ipc.nmbufs Nope. These are read-only but can be tuned from loader. > You can determine which is needed more through a quick netstat -m. > > Mike "Silby" Silbersack Cheers, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 16:33:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id D973837B4C5 for ; Wed, 8 Nov 2000 16:33:18 -0800 (PST) Received: (qmail 8002 invoked by uid 1001); 9 Nov 2000 10:33:15 +1000 X-Posted-By: GBA-Post 2.06 15-Sep-2000 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Thu, 09 Nov 2000 10:33:15 +1000 From: Greg Black To: Lyndon Nerenberg Cc: scanner@jurai.net, freebsd-hackers@FreeBSD.ORG Subject: Re: post-install of kernal sources, maxusers max? References: <200011082318.eA8NIHN25708@orthanc.ab.ca> In-reply-to: <200011082318.eA8NIHN25708@orthanc.ab.ca> of Wed, 08 Nov 2000 16:18:16 MST Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lyndon Nerenberg writes: > FWIW I run our NFS server with NMBCLUSTERS=10000. It doesn't burn that > much additional memory. As an additional data point, I had an NFS server that regularly crashed when it ran out; logs showed that it needed up to 1700 (against the default of 1024). I bumped it to 4096 about a year ago to give myself a bit of headroom and have no problems since; and I have noticed no waste of resources that mattered. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 16:46: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from linus.dvart.com (linus.dvart.com [64.79.2.3]) by hub.freebsd.org (Postfix) with ESMTP id 9AA1A37B4C5 for ; Wed, 8 Nov 2000 16:46:01 -0800 (PST) Received: from dvart.com ([192.168.100.141]) by linus.dvart.com (8.9.3/8.9.3) with ESMTP id QAA09273; Wed, 8 Nov 2000 16:45:57 -0800 Message-ID: <3A09F3BF.B028E0F8@dvart.com> Date: Wed, 08 Nov 2000 16:45:51 -0800 From: bruno schwander X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: close call in a device ? References: <200011082033.NAA25455@usr08.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > when a process closes the device, I do not get a "close" call for each > > > process closing the device. I instead get a close only on the last > > > process closing the device. > > > > devices in a similar way as the one is used for scanning pty's). > > To add to this, the close calls can be forces; there is a flag > in the device structure wich can force notification. I'm not > sure what it does over a fork(), though: I think you really want > open notification. > You mean that when I register my device/kernel module, I can explicitely request that all close calls will notify my module ? That is exactly what I need. What do you mean by open notification ? I do get all "open" calls to my device, just not all the "close" > The main problem with per process resources is that the VFS that > implements devices, specfs, doesn't own its own vnodes. Could you develop a little ? I don't know about VFS, specfs and vnodes... What I did is make a module that defines a struct cdevsw with the open/read/ etc callbacks, then I register my calls for various devices entries with make_dev(), and at the end used the DEV_MODULE() macro to declare it to the system. I modeled that after the example in /usr/src/share/examples/kld of FreeBSD 4 Is there a different driver/module architecture ? > This is actually the primary reason that VMWARE can only run > one instance at a time of a virtual machine: there is no way > to have per open instance resources, which are not shared. > > If you were to use the TFS flag (grep for TFS in the headers, > that's a substring), you could make specfs own its own vnodes. > Where should I look for this ? I looked into /usr/src/ and only some references to NTFS and TFS filesystems turned up ? Would I have to roll out a custom filesystem to have this running ? > The way you would handle your problem then is by returning a > different instance of the device, with a different instance of > per process attached storage. It's pretty simple to do this: > just return a different vnode for the next open of the same > device, instead of the same vnode with an additional reference. this is really confusing me... in the example I had, the only thing I return from my open routine is an int telling success or errors happened... any pointers for the vnode stuff ? if it could apply to what I am trying to do ? Am I basing my driver on the wrong stuff ? > NB: If you are trying to do this for VMWARE or some other binary > code, there's no way that the pty opening soloution suggested in > the previous posting will be able to work for you, since the code Yes, I came to that conclusion too. > will expect a particular behaviour. Right now, FreeBSD doesn't > support this behaviour (cloning devices), but as pointed out > above, it's not hard to implement, it's mostly just labor > intensive. > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. -- ########################################################################### Bruno Schwander Senior Software Engineer Worldgate Communications, Inc email: bschwand@dvart.com ############################################################################ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 17: 6:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 3790A37B479 for ; Wed, 8 Nov 2000 17:06:44 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id eA916Ov60507; Wed, 8 Nov 2000 17:06:24 -0800 (PST) Date: Wed, 8 Nov 2000 17:06:24 -0800 (PST) From: Doug White To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: post-install of kernal sources, maxusers max? In-Reply-To: <5.0.0.25.0.20001108211845.04d2d0a0@mail.Go2France.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Nov 2000, Len Conrad wrote: > All I need to change, I think, is maxusers since we're getting this > error from postfix: > > Nov 8 04:59:41 postfix/qmgr[16383]: fatal: socket: No buffer space available > Nov 8 04:59:41 postfix/smtp[16872]: fatal: socket: No buffer space available > Nov 8 05:00:58 postfix/qmgr[16876]: fatal: socket: No buffer space available You're running out of send/recvspace or your ethernet is maxed out. net.inet.tcp.sendspace: 16384 net.inet.tcp.recvspace: 16384 Try tweaking these values. You should also bump maxusers/nmbcluters/nmbufs so you're using about 20-30% nominally. Also make sure you're using full duplex links and you're not seeing excessive errors/collisions. I'd have to watch 'systat -vm' to check for some of the more remote problems ... > The machine can get up 200 SMTP processes and 50 SMTPD processes > simulatenously, 256 meg RAM. Small processes. > On the postfix list, it seems someone has heard from several FreeBSD > "experts" that FreeBSD should not be run at above maxusers = 128, > while somebody else said they were running with 256 happily. Depends on the release... I would not go above 256. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | 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 Nov 8 17:18:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 1930E37B479; Wed, 8 Nov 2000 17:18:45 -0800 (PST) Subject: Re: RPC not taking the same service twice: a bug or a security measure? In-Reply-To: <3A09D23E.6EA4390D@sftw.com> from Nick Sayer at "Nov 8, 2000 02:22:54 pm" To: nsayer@sftw.com (Nick Sayer) Date: Wed, 8 Nov 2000 17:18:45 -0800 (PST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20001109011845.1930E37B479@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A coworker seems to have found an issue with portmap on FreeBSD. > Aparently, if you try and register the same service twice, but with > different protocols (UDP vs TCP), it doesn't work. I'm not entirely sure > I believe this, and I am digging for more details, but I am writing to > see if anyone can tell me anything that will save me having to do the > investigative work. :-) I'll follow up with more details as I can. No you won't, because both you and your cow-orker are smoking entirely too much crack. (Him for hallucinating this problem in the first place, and you for believing him enough to post this query here.) Do rpcinfo -p on a FreeBSD host running NFS, NIS, AMD, or whatever, and you'll see both UDP and TCP entries for each service. If it didn't work, somebody would have screamed bloody murder about it long before now. You don't explain how your cow-orker is trying to register these services (it's probably a custom RPC application, but he could be using a hammer and chisel for all we know), nor do you go into any detail at all about what "doesn't work" means. The correct procedure here is to take away his crack pipe and pump him for more details, *then* post here only after you're sure he's not imagining things. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 17:36:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from linus.dvart.com (linus.dvart.com [64.79.2.3]) by hub.freebsd.org (Postfix) with ESMTP id E6FC137B4C5 for ; Wed, 8 Nov 2000 17:36:05 -0800 (PST) Received: from dvart.com ([192.168.100.141]) by linus.dvart.com (8.9.3/8.9.3) with ESMTP id RAA14000; Wed, 8 Nov 2000 17:35:29 -0800 Message-ID: <3A09FF60.ACF33F8D@dvart.com> Date: Wed, 08 Nov 2000 17:35:28 -0800 From: bruno schwander X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: close call in a device ? References: <200011082035.NAA25463@usr08.primenet.com> <3A09C290.DC5F0E3A@elischer.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > the problem here can be solved by using Poul's 'cloning device' > interface in the driver. > I don't think he has it quite completed but it is partly there.. maybe > enough.. > this seems very promising. Any pointers toward more info on this ? Thanks bruno > > only in -current at the moment and you need to have devfs turned on. > > each time you open it, you actually get a different device and vnode.. > > > > Terry Lambert > > terry@lambert.org > > --- > > Any opinions in this posting are my own and not those of my present > > or previous employers. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000 > ---> X_.---._/ presently in: Budapest > v -- ########################################################################### Bruno Schwander Senior Software Engineer Worldgate Communications, Inc tel: (408) 378-7800 x116 fax: (408) 378-8018 email: bschwand@dvart.com ############################################################################ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 17:54:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id 2BFB537B479 for ; Wed, 8 Nov 2000 17:54:47 -0800 (PST) Received: from yoda.sftw.com (yoda.sftw.com [209.157.37.211]) by guardian.sftw.com (8.11.0/8.11.0) with ESMTP id eA91shq22046 for ; Wed, 8 Nov 2000 17:54:44 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.11.0/8.11.0) with ESMTP id eA91shR53204 for ; Wed, 8 Nov 2000 17:54:43 -0800 (PST) (envelope-from nsayer@sftw.com) Message-ID: <3A0A03E3.BA0C7A9E@sftw.com> Date: Wed, 08 Nov 2000 17:54:43 -0800 From: Nick Sayer Reply-To: Nick Sayer X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Re: KDE2, konsole_grantpty and FreeBSD References: <200011082303.eA8N3c193540@medusa.kfu.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have cobbled together a solution with fstat() and devname(). Interestingly enough, elsewhere in konsole, a call to ttyname() with an FD on the master side appears to actually work, so I don't know what the hell is up with that. :-/ Nick Sayer wrote: > [...] > > The problem is that ttyname() fails on all /dev/pty?? devices. This is because > the first thing ttyname does is perform a tcgetattr() to see if it's really a > terminal or not. This fails. > [...] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 19:52:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.iadfw.net (mail2.iadfw.net [206.66.12.234]) by hub.freebsd.org (Postfix) with SMTP id 3F81037B479 for ; Wed, 8 Nov 2000 19:52:23 -0800 (PST) Received: from jason from [64.31.200.230] by mail2.iadfw.net (/\##/\ Smail3.1.30.16 #30.11) with smtp for sender: id ; Wed, 8 Nov 2000 21:52:31 -0600 (CST) Message-ID: <01a001c04a01$06548900$e6c81f40@pdq.net> From: "Jason" Cc: References: Subject: Re: PSE/PAE support Date: Wed, 8 Nov 2000 21:56:22 -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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "John Baldwin" > On 08-Nov-00 Jeroen Ruigrok van der Werven wrote: > > We support 4 Kbyte pages and 4 Mbyte pages, but we do not support 2 > > Mbyte pages. On IA-32 at least. > > > > Is there a reason to? If you have the time to burn, want to squeeze out that small amount of possible performace from reduced TLB misses, or want to support that small nich of server hardware that can use more then 4GB of memory. > The benefits of PAE are that you can support a machine that has more than 4gb > of phyiscal ram, up to 64gb. However, the virtual address space is still 4gb, > so a process (and kernel with the current way we do our virtual address > mapping) must still fit into a 4gb space. > > I could understand that some people would prefer 2 Mbyte pages in some > > situations. But looking at pmap.c I see we only test CPUID_PSE and > > don't use CPUID_PAE anywhere. > > Actually, the 2mb pages really don't buy us anything. We only use large pages > now to map the kernel, AFAIK. > On IA-32 the 4MB/2MB entries pose two benifits. First they allow the support of a larger physical memory space and second they reduce the entries used in the TLB. Currently FreeBSD/i386 uses a 4MB entry for the first 4MB of memory because it can assume that this area of memory containing various BIOS data, IO mappings, and kernel text, bss, and data will never be swapped out. This condenses a somewhat constant 1024 entries to one. I'd have to look at the way things are mapped again, but this may save a 4KB page of memory or most likly the page is left unrefernced because it is a magic page allocated for the PTD of the first 4MB of memory. > > Since pmap.c is in a MD location it wouldn't be hard to extend the code > > to do this. Say that again after you've done it ... -Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 20:18:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hkgmss11.cwhkt.com (unknown [202.84.162.93]) by hub.freebsd.org (Postfix) with SMTP id DF7AF37B479; Wed, 8 Nov 2000 20:18:34 -0800 (PST) Received: by mail.cwhkt.com with Internet Mail Service (5.5.2650.21) id ; Thu, 9 Nov 2000 12:20:52 +0800 From: "Tsang, Victor YF" To: "'questions@freebsd.org'" , "'hackers@freebsd.org'" Subject: programming: how to send signal to other program Date: Thu, 9 Nov 2000 11:31:10 +0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="big5" Message-Id: <20001109041834.DF7AF37B479@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, How can I send a signal (say, SIGUSR1) to another program with known pid? I used to do so in Solaris using sigsend() but this call seems not available in FreeBSD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 20:21: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id 9212C37B479 for ; Wed, 8 Nov 2000 20:21:02 -0800 (PST) Received: (qmail 9036 invoked by uid 1001); 9 Nov 2000 14:21:00 +1000 X-Posted-By: GBA-Post 2.06 15-Sep-2000 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Thu, 09 Nov 2000 14:20:59 +1000 From: Greg Black To: "Tsang, Victor YF" Cc: "'questions@freebsd.org'" , "'hackers@freebsd.org'" Subject: Re: programming: how to send signal to other program References: <20001109041834.DF7AF37B479@hub.freebsd.org> In-reply-to: <20001109041834.DF7AF37B479@hub.freebsd.org> of Thu, 09 Nov 2000 11:31:10 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How can I send a signal (say, SIGUSR1) to another program with known pid? I > used to do so in Solaris using sigsend() but this call seems not available > in FreeBSD. Use kill(2), and don't send learner questions to -hackers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 23: 9:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 9A13E37B479 for ; Wed, 8 Nov 2000 23:09:18 -0800 (PST) Received: from newsguy.com (p47-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.48]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id QAA00570; Thu, 9 Nov 2000 16:08:48 +0900 (JST) Message-ID: <3A0A4D19.7FCD3678@newsguy.com> Date: Thu, 09 Nov 2000 16:07:05 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Ian Dowse Cc: Len Conrad , freebsd-hackers@FreeBSD.ORG Subject: Re: post-install of kernal sources, maxusers max? References: <200011082146.aa69533@salmon.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ian Dowse wrote: > > I think a few slots are reserved, so you can consider 1050 as being > equal to 1064. Try putting > > set kern.ipc.maxsockets=4000 > > in /boot/loader.rc and rebooting. Eeeewwww! kern.ipc.maxsockets="4000" in /boot/loader.conf instead, please! -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@world.wide.bsdconspiracy.net He has been convicted of criminal possession of a clue with intent to distribute. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 23:33:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web3503.mail.yahoo.com (web3503.mail.yahoo.com [204.71.203.70]) by hub.freebsd.org (Postfix) with SMTP id D6D1037B479 for ; Wed, 8 Nov 2000 23:33:34 -0800 (PST) Message-ID: <20001109073328.16200.qmail@web3503.mail.yahoo.com> Received: from [196.7.146.6] by web3503.mail.yahoo.com; Wed, 08 Nov 2000 23:33:28 PST Date: Wed, 8 Nov 2000 23:33:28 -0800 (PST) From: Jacques Fourie Subject: Re: kernel stack size? To: Julian Elischer Cc: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Julian Elischer wrote: > Why are you not using the netgraph system, which was > specifically > designed > for this? it allows you to divert eherne packets When we started on this, (~2years ago) I was not aware of the netgraph functionality. I agree that it would be better to re-implement using netgraph. As always, time is the problem... regards, jacques __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one Place. http://shopping.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 8 23:38: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web3503.mail.yahoo.com (web3503.mail.yahoo.com [204.71.203.70]) by hub.freebsd.org (Postfix) with SMTP id 890B937B4CF for ; Wed, 8 Nov 2000 23:38:05 -0800 (PST) Message-ID: <20001109073805.16423.qmail@web3503.mail.yahoo.com> Received: from [196.7.146.6] by web3503.mail.yahoo.com; Wed, 08 Nov 2000 23:38:05 PST Date: Wed, 8 Nov 2000 23:38:05 -0800 (PST) From: Jacques Fourie Subject: Re: kernel stack size? To: Matt Dillon Cc: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Matt Dillon wrote: > You can theoretically increase UPAGES in > /usr/src/sys/i386/include/param.h I increased UPAGES from 2 to 8 and everything seems to be working as it should. The device in question will very much be a dedicated IPsec device and will not be running that many user processes. A waste of memory is not such a big issue - not nice but given the choice I will rather have it working. thanks for your advice, jacques __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one Place. http://shopping.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 0: 3:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 52B9F37B479; Thu, 9 Nov 2000 00:03:41 -0800 (PST) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 61A02A85B; Thu, 9 Nov 2000 19:03:35 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 5F76F545E; Thu, 9 Nov 2000 18:03:35 +1000 (EST) Date: Thu, 9 Nov 2000 18:03:35 +1000 (EST) From: andrew@ugh.net.au To: "Tsang, Victor YF" Cc: "'questions@freebsd.org'" , "'hackers@freebsd.org'" Subject: Re: programming: how to send signal to other program In-Reply-To: <20001109041834.DF7AF37B479@hub.freebsd.org> Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Nov 2000, Tsang, Victor YF wrote: > How can I send a signal (say, SIGUSR1) to another program with known pid? I > used to do so in Solaris using sigsend() but this call seems not available > in FreeBSD. kill(2) Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 0:24:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.klondike.ru (unknown [195.170.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 7975B37B4C5; Thu, 9 Nov 2000 00:24:12 -0800 (PST) Received: from freebsd.klondike.ru (freebsd [195.170.237.64]) by ns.klondike.ru (8.9.3/8.9.3) with SMTP id LAA10460; Thu, 9 Nov 2000 11:24:09 +0300 (MSK) Message-Id: <200011090824.LAA10460@ns.klondike.ru> Date: Thu, 9 Nov 2000 11:23:27 +0000 From: Kaltashkin Eugene To: hackers@freebsd.org Cc: stable@freebsd.org Subject: mbuf allocation error X-Mailer: stuphead version 0.4.5 (GTK+ 1.2.8; FreeBSD 4.2-BETA; i386) Organization: Klondike Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ppls Today i get message looutput: mbuf allocation error #netstat -m 567/2176/4096 mbufs in use (current/peak/max): 317 mbufs allocated to data 250 mbufs allocated to packet headers 296/1024/1024 mbuf clusters in use (current/peak/max) where i can increase amount of mbuf ? sysctl say what this variables is readonly :( Best Regards. Zhecka PS: system use Postgresql with many many records. Everynight base has been repacked. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 0:26:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id BF03837B479; Thu, 9 Nov 2000 00:26:34 -0800 (PST) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 5E6831C6B; Thu, 9 Nov 2000 03:26:34 -0500 (EST) Date: Thu, 9 Nov 2000 03:26:34 -0500 From: Bill Fumerola To: Kaltashkin Eugene Cc: hackers@freebsd.org Subject: Re: mbuf allocation error Message-ID: <20001109032634.K37870@jade.chc-chimes.com> References: <200011090824.LAA10460@ns.klondike.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200011090824.LAA10460@ns.klondike.ru>; from zhecka@klondike.ru on Thu, Nov 09, 2000 at 11:23:27AM +0000 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ don't cross post, followups to hackers (was on stable) ] On Thu, Nov 09, 2000 at 11:23:27AM +0000, Kaltashkin Eugene wrote: > #netstat -m > 567/2176/4096 mbufs in use (current/peak/max): > 317 mbufs allocated to data > 250 mbufs allocated to packet headers > 296/1024/1024 mbuf clusters in use (current/peak/max) > > where i can increase amount of mbuf ? > sysctl say what this variables is readonly :( options NMBCLUSTERS=8192 or whatever in your kernel. or kern.ipc.nmbclusters="8192" # Set the number of mbuf clusters in /boot/loader.conf -- Bill Fumerola - Lame Duck, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 0:40:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id C58EB37B479 for ; Thu, 9 Nov 2000 00:40:49 -0800 (PST) Received: from gorean.org (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id AAA73498; Thu, 9 Nov 2000 00:38:58 -0800 (PST) (envelope-from DougB@gorean.org) Message-ID: <3A0A62A2.193D3406@gorean.org> Date: Thu, 09 Nov 2000 00:38:58 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Terry Lambert Cc: Max Khon , Don Lewis , andrew@ugh.net.au, hackers@FreeBSD.ORG Subject: Re: daemon() References: <200011082017.NAA25041@usr08.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: [snippage] > > exactly. this does not happen if I run this program from tcsh > > (but does if I run from bash 1.14.7(1) built from ports > > thanks! > All in all, bash is pretty buggy. The originator already stated that the bug doesn't appear in bash 2. Using bash 1 as an example of anything is just (pardon the pun) bash-bash'ing. I stand by my statement that no one with any sense still uses bash 1 for anything. It's documented to be broken lots of ways, and all known bugs are fixed in bash 2. If there are real bugs (not style disagreements) in bash 2, they should be reported to the maintainer, who actively responds to and fixes reported problems. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 5:21:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C5EFF37B479 for ; Thu, 9 Nov 2000 05:21:51 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id eA9DLld53062; Thu, 9 Nov 2000 14:21:47 +0100 (CET) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.0/8.11.0) with ESMTP id eA9DLWp05037; Thu, 9 Nov 2000 14:21:37 +0100 (CET) (envelope-from leifn@neland.dk) Date: Thu, 9 Nov 2000 14:21:32 +0100 (CET) From: Leif Neland To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: post-install of kernal sources, maxusers max? In-Reply-To: <5.0.0.25.0.20001108211845.04d2d0a0@mail.Go2France.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Nov 2000, Len Conrad wrote: > Sorry to bother you hackers, but -questions isn't responding, and the > handbook and Complete/Lehey don't, afaics, cover this situation > explicitly. I can't really afford to screw up this production > machine and start over from fresh disk, nor futz around for hours > guessing what magik combo of post-install choices will do the trick. > > ========== > > I'm working, remotely, on a 4.1 system with only a binary install from cdrom. > > Now I need to do a custom kernal. Can the /stand/systinstall > post-config option be used to put on all the developer source pkg > without bothering the current config? which choice (I don't want X, > just enough to build a custom kernal) > Install cvsup-binary from ports, and cvsup the sources. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 5:27: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spammie.svbug.com (mg136-010.ricochet.net [204.179.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 078D237B479; Thu, 9 Nov 2000 05:26:58 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id FAA14148; Thu, 9 Nov 2000 05:29:10 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200011091329.FAA14148@spammie.svbug.com> Date: Thu, 9 Nov 2000 05:29:08 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: RPC not taking the same service twice: a bug or a security meas ure? To: wpaul@FreeBSD.ORG Cc: nsayer@sftw.com, hackers@FreeBSD.ORG In-Reply-To: <20001109011845.1930E37B479@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8 Nov, Bill Paul wrote: >> A coworker seems to have found an issue with portmap on FreeBSD. >> Aparently, if you try and register the same service twice, but with >> different protocols (UDP vs TCP), it doesn't work. I'm not entirely sure >> I believe this, and I am digging for more details, but I am writing to >> see if anyone can tell me anything that will save me having to do the >> investigative work. :-) I'll follow up with more details as I can. > > No you won't, because both you and your cow-orker are smoking entirely > too much crack. (Him for hallucinating this problem in the first place, > and you for believing him enough to post this query here.) > Hey!! There is no need for this type of response. It's obvious the person writing has good intentions, but has not read a TCP/IP book, that's worth a damm. I would consider it a personal favor, if this might be responded to in a less attacking manner. best regards, Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 7:15:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id 098C337B4C5 for ; Thu, 9 Nov 2000 07:15:21 -0800 (PST) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id RAA26768; Thu, 9 Nov 2000 17:19:44 +0100 Message-ID: <3A0ABFB7.B269FAFD@i-clue.de> Date: Thu, 09 Nov 2000 16:16:07 +0100 From: Christoph Sold X-Mailer: Mozilla 4.75 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: Jimmy Olgeni Cc: hackers@FreeBSD.ORG Subject: Re: What about rc.shutdown.local? References: <3A0AAB5E.C6B1C53@uli.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Redirected from stable@FreeBSD.org to hackers@FreeBSD.org ] Jimmy Olgeni schrieb: > > It would be nice to have a /etc/rc.shutdown.local called by > /etc/rc.shutdown, > to implement custom shutdown procedures. This is currently done by > editing rc.shutdown, but you have to remember about it when you run > mergemaster. > > Just a thought :) Better still would be /usr/local/etc/rc.d/*.sh called automatically with parameter stop. To do so, insert for dir in ${local_startup}; do if [ -d "${dir}" ]; then for script in ${dir}/*.sh; do if [ -x "${script}" ]; then (set -T trap 'exit 1' 2 ${script} stop) fi done fi done echo . into /etc/rc.shutdown. (Script shamelessly copied from /etc/rc), changed "start" to "stop". HTH -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 7:24: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 40BF337B4C5 for ; Thu, 9 Nov 2000 07:24:06 -0800 (PST) Received: (from root@localhost) by virtual-voodoo.com (8.11.1/8.11.1) id eA9FNbI72342; Thu, 9 Nov 2000 10:23:37 -0500 (EST) (envelope-from steve) Date: Thu, 9 Nov 2000 10:23:37 -0500 From: Charlie & To: Christoph Sold Cc: Jimmy Olgeni , hackers@FreeBSD.ORG Subject: Re: What about rc.shutdown.local? Message-ID: <20001109102337.A64659@virtual-voodoo.com> References: <3A0AAB5E.C6B1C53@uli.it> <3A0ABFB7.B269FAFD@i-clue.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A0ABFB7.B269FAFD@i-clue.de>; from so@server.i-clue.de on Thu, Nov 09, 2000 at 04:16:07PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This already happens... at least in rc.shutdown v1.15: # $FreeBSD: src/etc/rc.shutdown,v 1.15 2000/10/20 20:26:05 ache Exp $ -Steve On Thu, Nov 09, 2000 at 04:16:07PM +0100, Christoph Sold wrote: > [ Redirected from stable@FreeBSD.org to hackers@FreeBSD.org ] > > Jimmy Olgeni schrieb: > > > > It would be nice to have a /etc/rc.shutdown.local called by > > /etc/rc.shutdown, > > to implement custom shutdown procedures. This is currently done by > > editing rc.shutdown, but you have to remember about it when you run > > mergemaster. > > > > Just a thought :) > > Better still would be /usr/local/etc/rc.d/*.sh called automatically > with parameter stop. To do so, insert > > for dir in ${local_startup}; do > if [ -d "${dir}" ]; then > for script in ${dir}/*.sh; do > if [ -x "${script}" ]; then > (set -T > trap 'exit 1' 2 > ${script} stop) > fi > done > fi > done > echo . > > into /etc/rc.shutdown. (Script shamelessly copied from /etc/rc), changed > "start" to "stop". > > HTH > -Christoph Sold > > > 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 Nov 9 7:26:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 98F9A37B479 for ; Thu, 9 Nov 2000 07:26:12 -0800 (PST) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id RAA22231; Thu, 9 Nov 2000 17:25:47 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 22216; Thu Nov 9 17:25:36 2000 Message-ID: <3A0AA96B.3F1365D@cequrux.com> Date: Thu, 09 Nov 2000 15:40:59 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dan Nelson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Help writing a screen saver module References: <3A06B7A7.7665C46A@cequrux.com> <20001107144202.B4569@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Nelson wrote: > > In the last episode (Nov 07), Dag-Erling Smorgrav said: > > Graham Wheeler writes: > > > I am trying to write a screen saver module that, when it kicks in, > > > will switch to the first console, and then, if a key is pressed, > > > will switch back to the one that was previously active. The idea is > > > that the first console has something useful running on it, > > > typically a tail -f of the logs. > > > > Switching consoles causes syscons to stop the screensaver, which > > causes your code to try to switch back to the original console, which > > causes syscons to stop the screensaver since seems to be running. In > > other words, Don't Do That. Sorry. > > You can make it look like you're switched to vty 0, by making your > screen_saver() function simply copy the contents of vty 0 to screen > memory on every update. Just make sure both vtys are the same size > first... I've made some progress here. I have a function in syscons.c that should (I thought) work. It only works partially. When the saver kicks in it changes the contents of the screen with something that looks half-like garbage, and half like it should. In some places every second character is right, and these are interspersed with whitespace which shouldn't be there, but in others this breaks down, and I might have a few consecutive ones right or a whole sequence of garbage. (On closer inspection, the `garbage' seems to be remnants of the original contents). On the other hand, if I press a key, the original contents are restored perfectly (or perhaps only the characters that were being copied are being restored, which together with the `garbage' makes the screen look like it used to?). I'm quite confused about why this is so. Any ideas anyone? Here is my additional function added to syscons.c: /* Copy the contents of one console to another. The original contents of the copyee are saved in a buffer, a pointer to which is returned, iff backup==0. If backup is non-zero, and from < 0, then backup should point to the original contents, and they will be restored, and the memory used will be freed. So the use is something like: First Copy: char *backup = CopyConsoleContents(from, to, 0); Refresh (subsequent copies): backup = CopyConsoleContents(from, to, backup); or: (void)CopyConsoleContents(from, to, backup); Restore: CopyConsoleContents(-1, to, backup); If to<0 then the current console will be used */ u_short *CopyConsoleContents(int from, int to, u_short *backup); u_short *CopyConsoleContents(int from, int to, u_short *backup) { if (to < 0) /* if to < 0 we want the current console */ to = get_scr_num(); if (to != from) /* don't waste time if source == dest */ { scr_stat *fc, *tc = console[to]; int s = spltty(), pos, len; /* is this a restore? */ if (from < 0 && backup) { /* restore from the backup and free allocated memory */ bcopy((char*)backup, (char*)tc->scr_buf, tc->xsize*tc->ysize*sizeof(u_short)); free((char*)backup, M_DEVBUF); backup = 0; } /* else this is a copy */ else if (from>=0 && from < MAXSONS) /* is the source index sane? */ { fc = console[from]; /* first do some more sanity checks: non-NULL pointers and equal console sizes */ if (fc && tc && fc->xsize == tc->xsize && fc->ysize == tc->ysize && fc->scr_buf && tc->scr_buf) { /* is this a first copy? if so, backup original contents */ if (backup == 0) { backup = (u_short*)malloc( tc->xsize*tc->ysize*sizeof(u_short), M_DEVBUF, M_NOWAIT); if (backup) bcopy((const char*)tc->scr_buf, (char*)backup, tc->xsize*tc->ysize*sizeof(u_short)); } /* copy the from console to the to console bcopy((const char*)fc->scr_buf, (char*)tc->scr_buf, fc->xsize*fc->ysize*sizeof(u_short)); } } /* update the video memory if to==current console */ if (to == get_scr_num() && tc->adp && tc->adp->va_window) { len = tc->ysize * tc->xsize; for (pos = 0; pos < len; pos +=2) writew(tc->adp->va_window + pos*2, tc->scr_buf[pos]); } splx(s); } return backup; } ==================================================================== Here is what the switch_saver.c looks like now: ==================================================================== #include #include #include #include #include #include #include #include u_short *backup; extern u_short *CopyConsoleContents(int from, int to, u_short *backup); static int switch_saver(video_adapter_t *adp, int blank) { if (adp->va_info.vi_flags & V_INFO_GRAPHICS) return EAGAIN; if (blank) { backup = CopyConsoleContents(0, -1, backup); } else if (backup) /* restore old contents */ backup = CopyConsoleContents(-1, -1, backup); return 0; } static int switch_init(video_adapter_t *adp) { (void)adp; backup = 0; return 0; } static int switch_term(video_adapter_t *adp) { (void)adp; return 0; } static scrn_saver_t switch_module = { "switch_saver", switch_init, switch_term, switch_saver, NULL, }; SAVER_MODULE(switch_saver, switch_module); ==================================================================== regards gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 7:31:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 12B1137B479 for ; Thu, 9 Nov 2000 07:31:52 -0800 (PST) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.11.0/8.11.1) with ESMTP id eA9FVkf38933 for ; Thu, 9 Nov 2000 07:31:46 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from icarus.kfu.com (ssmail@localhost) by medusa.kfu.com (8.11.0/8.11.0) with ESMTP id eA9FVjF00300 for ; Thu, 9 Nov 2000 07:31:45 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com by icarus.kfu.com with ESMTP (8.11.0//ident-1.0) id eA9EDix58383; Thu, 9 Nov 2000 06:13:44 -0800 (PST) Message-ID: <3A0AB117.6FCBD79F@quack.kfu.com> Date: Thu, 09 Nov 2000 06:13:43 -0800 From: Nick Sayer X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: opentrax@email.com Cc: wpaul@FreeBSD.ORG, nsayer@sftw.com, hackers@FreeBSD.ORG Subject: Re: RPC not taking the same service twice: a bug or a security measure? References: <200011091329.FAA14148@spammie.svbug.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG opentrax@email.com wrote: > > On 8 Nov, Bill Paul wrote: > >> A coworker seems to have found an issue with portmap on FreeBSD. > >> Aparently, if you try and register the same service twice, but with > >> different protocols (UDP vs TCP), it doesn't work. I'm not entirely sure > >> I believe this, and I am digging for more details, but I am writing to > >> see if anyone can tell me anything that will save me having to do the > >> investigative work. :-) I'll follow up with more details as I can. > > > > No you won't, because both you and your cow-orker are smoking entirely > > too much crack. (Him for hallucinating this problem in the first place, > > and you for believing him enough to post this query here.) > > > Hey!! There is no need for this type of response. > It's obvious the person writing has good intentions, > but has not read a TCP/IP book, that's worth a damm. > I would consider it a personal favor, if this might be > responded to in a less attacking manner. No, no. He's right. We were smoking too much crack. :-) The problem turns out that we try to unregister the service before we register it. On solaris we use rpcb_unset(), which is protocol specific. On Freebsd, we use pmap_unset() which does not consider protocol. It would unregister the one we registered on the other protocol moments ago. I guess on FreeBSD there is no way to unregister selectively such as with rpcb_unset(), so we will just have to be a little more careful. :-) In my own defense, I'd like to point out that I've read lots of good TCP/IP books. It's RPC that I know very little about. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 9:50:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id 6E11F37B65F for ; Thu, 9 Nov 2000 09:50:11 -0800 (PST) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13tvpa-0005gC-00; Thu, 09 Nov 2000 17:49:46 +0000 Date: Thu, 9 Nov 2000 17:49:46 +0000 From: void To: Brian O'Shea Cc: hackers@FreeBSD.ORG Subject: Re: "iowait" CPU state Message-ID: <20001109174946.B21468@firedrake.org> References: <20001107054413.A1983@firedrake.org> <20001107000022.M622@beastie.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001107000022.M622@beastie.localdomain>; from boshea@ricochet.net on Tue, Nov 07, 2000 at 12:00:22AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 07, 2000 at 12:00:22AM -0800, Brian O'Shea wrote: > > What information are you looking for specifically? %busy figures for disks, %iowait figures for processors. > $ systat -io > > Hope that helps, Like iostat, this tells me how much data is being transferred, but not how busy the disks are. I want relative data, not absolute. Thanks though. -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 9:51: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id 44D4A37B479 for ; Thu, 9 Nov 2000 09:50:57 -0800 (PST) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13tvqc-0005gu-00; Thu, 09 Nov 2000 17:50:50 +0000 Date: Thu, 9 Nov 2000 17:50:50 +0000 From: void To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: "iowait" CPU state Message-ID: <20001109175050.C21468@firedrake.org> References: <20001107054413.A1983@firedrake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Tue, Nov 07, 2000 at 04:13:30PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 07, 2000 at 04:13:30PM +0100, Dag-Erling Smorgrav wrote: > void writes: > > I've been using Solaris a lot lately, and I've noticed that in e.g. > > top's output, it has a distinct CPU state called "iowait", which seems > > to be a pretty good indicator of how I/O-bound a system is. Is there > > any reason that FreeBSD doesn't have such a state? > > It has several, depending on the type of I/O the process is waiting > for: biord (waiting for a read operation to complete), biowr (waiting > for a write operation to complete), select (waiting for descriptors to > become readable / writable), etc. Is there any reason top couldn't add these up and report a %iowait like Solaris'? -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 9:57:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id 7F84E37B479 for ; Thu, 9 Nov 2000 09:57:05 -0800 (PST) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id TAA52996 for ; Thu, 9 Nov 2000 19:56:56 +0200 (EET) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id TAA25320 for ; Thu, 9 Nov 2000 19:56:59 +0200 (EET) (envelope-from petro@She.wertep.com) Date: Thu, 9 Nov 2000 19:56:59 +0200 (EET) From: petro To: FreeBSD-hackers@FreeBSD.ORG Subject: PPPD! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I try to start pppd but always receive such message when start pppd Device cuaa0 is busy... What I must do, I try to kill all pppd and then start again, but again receive such message, before rebbot everything works fine.... Thank you... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 10: 3:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from amsmta03-svc.chello.nl (mail-out.chello.nl [213.46.240.7]) by hub.freebsd.org (Postfix) with ESMTP id 219BE37B479 for ; Thu, 9 Nov 2000 10:03:40 -0800 (PST) Received: from chello ([213.93.11.73]) by amsmta03-svc.chello.nl (InterMail vK.4.02.00.10 201-232-116-110 license 1753790c58305fd3f286395c4a42fdc7) with ESMTP id <20001109180324.RGJO13713.amsmta03-svc@chello>; Thu, 9 Nov 2000 19:03:24 +0100 From: "Leonard den Ottolander" To: redhat-list@redhat.com Date: Thu, 9 Nov 2000 19:03:41 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: [OT] serial protocol analyzer Cc: freebsd-hackers@freebsd.org Message-ID: <3A0AF50D.16530.974B26@localhost> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everybody, I was wondering if somebody could point me out a serial protocol analyzer. Maybe analyzer is too big a word for what I am looking for (I could be the analyzer :) ). What I am thinking of is a piece of software that listens on two serial devices, and mimics input from either to the other, in the mean time dumping and/or analyzing the traffic. To be concrete: I want to put a box with this piece of software between another box and its modem to analyze the traffic. Thanks in advance, Ciao, Leonard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 10:28:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 72EFF37B479 for ; Thu, 9 Nov 2000 10:28:15 -0800 (PST) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id LAA28847; Thu, 9 Nov 2000 11:28:42 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp05.primenet.com, id smtpdAAA80aaq4; Thu Nov 9 11:28:32 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id LAA22910; Thu, 9 Nov 2000 11:27:56 -0700 (MST) From: Terry Lambert Message-Id: <200011091827.LAA22910@usr08.primenet.com> Subject: Re: close call in a device ? To: bschwand@dvart.com (bruno schwander) Date: Thu, 9 Nov 2000 18:27:56 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), freebsd-hackers@FreeBSD.ORG In-Reply-To: <3A09F3BF.B028E0F8@dvart.com> from "bruno schwander" at Nov 08, 2000 04:45:51 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > To add to this, the close calls can be forces; there is a flag > > in the device structure wich can force notification. I'm not > > sure what it does over a fork(), though: I think you really want > > open notification. > > You mean that when I register my device/kernel module, I can > explicitely request that all close calls will notify my module? > That is exactly what I need. Add D_TRACKCLOSE to d_flags for your device. When the d_close() of your device is call, the first arg is the dev. Unfortunately, vcount() is used to see if the close is really a final close, or not, and the vp is not passed into the close itself. You will have to track closes yourself. One kludge to get around having to so this is to modify spec_close() to do: } else if (devsw(dev)->d_flags & D_TRACKCLOSE) { /* Keep device updated on status */ if (vcount(vp) > 1) { /* clear flag to signal driver of last close*/ devsw(dev)->d_flags &= ~D_TRACKCLOSE; } } else if (vcount(vp) > 1) { and then as the _first_ thing in your close code: if( !(devsw(dev)->d_flags & D_TRACKCLOSE)) { /* magic: final close: add flag back in to keep sane*/ devsw(dev)->d_flags |= D_TRACKCLOSE; ... } You can find spec_close() in /sys/miscfs/specfs/spec_vnops.c. You really probably ought to just add the flag back in in the first open. The thing that makes this a kludge is that it very evilly unsets a flag it shouldn't unset, and it makes it the job of the device to fix up the damage (the interface isn't reflexive). A secondary nit is that this is not really reentrant, while the flag is clear, so you have to be careful. Really, since you will be doing per-open instance housekeeping anyway, you ought to just add a list pointer to the per-open instance data, and keep the open instances on a linked list; you will have tolook up the per-open instance data somehow, anyway, and it might as well be a list traversal. When list membership goes from 1->0, you'll know it's the last close, and you can free global (non per-open instance) resources. Traditionally, this is done using a minor number, but you can't just naievely allocate an unused one, since you might not get called. > What do you mean by open notification ? I do get all "open" calls to my > device, just not all the "close" For each open, d_open() gets called. This is where you will be creating your per open instance data. You should look at how fd's are handled over a fork() or other call. Without a look at this code in depth, I can't tell you today whether or not your d_open() code will get called again for each open fd, or not. If it doesn't, this could be a problem for you. It used to get called, FWIW. > > The main problem with per process resources is that the VFS that > > implements devices, specfs, doesn't own its own vnodes. > > Could you develop a little ? I don't know about VFS, specfs and vnodes... When you perform an operation on an open file, the vnode pointer is dereferenced out of the per process open file table. The kernel internally doesn't know from file handles (architectural bug, IMO), and so not only is it hard to do file I/O in the kernel, but you have this opaque handle called a vnode. When you do an ioctl() or something else, then because this is a special device, there is a dereference into a function table pointed to by the vnode. This table is called "struct fileops", and the table for special devices is spec_fileops. So you give it a vnode, it dereferences the fcntl() function pointer out of this table to make the call, and passes the vnode pointer as an argument. In the spec_fileops version of fcntl(), the device specific data is derefenced out of the vnode; it can do this, because it knows that any vnode of type VCHR will have one of these structures on it. This is used by specfs to locate the correct device entry point to call: your device. Your device driver function is then called, with the device private data pointer from the vnode, called "dev". It's a pointer to your device private data. Because the specfs does not own its own vnodes, each time you open a device, you get the same vnode back from specfs. It can't give you a different one, because you asked for the same one: by the time it gets to the open, all it has is the vnode of the parent directory, a major number, and a minor number. So there's no way for the open to return a unique instance of the device each time you open it, because it can only return one vnode. This gets worse, because of fork() and other fd managemetn behaviour. The kernel likes to give back the same vnode to a user space process as often as possible. If one of these calls to do this returns another reference to an existing open isntance (say you open the same device twice from the same program, or you call dup() or dup2()), then you may not get to call all the way down to the open, like you expect. This code is pretty convoluted, and I haven't traced it so I can give you an exact answer, and I'm probably not running the exact same version of the code as you, so even if I did the work and gave you the right answer for me, it might not be the same answer for you. So all I'm saying is "here there be dragons", and you should be very, very cautious. If you do give back a different vnode, then you will have to be careful about vcount(), which will always return "1" for your vnodes, and so it will always close them (this could be a benefit, actually: you could ignore D_TRACKCLOSE entirely). In any case, the vnodes are not the specfs or devices to give, they belong to the system. Because of that, there are two consequences: 1) You can have cache effects, like those I talked about for fork(), dup(), dup2(), and so on. 2) You won't necessarily get notified all the way to your device driver when a new fd references an existing vp, so relying on the open/close notification might not work. 3) The way a device driver is "supposed" to tell which device is which is by using the minor number out of the "dev" structure (the major number is what got you to your device driver through specfs in the first place), and... your device, if it acts this way, will have the same minor number for each time it is called, which means you will have to differentiate based on making up a new minor number for each open, and returning that as a different vnode. Only the vnode allocation is done above the device driver control, so this is hard (you _must_ modify specfs to get this behaviour; in particular, you _must_ modify the code that calls the spec_open() call, since that's where the vnode gets allocated for the open -- and that's two layers up from your device, so you will probably have to ad your own D_ flag, and teach the upper layer about it). It is not all that complicated, once you understand the code, but there are a lot of places that you have to be careful so that you don't get bitten. I think the biggest problem is actually going to be #1, above, since I expect that what is going to happen is that the VFS on which the special device is located will look in its little name cache, given the directory vp of the parent directory for the device, and the name of the device, and then just return a new reference on a cached copy of the vp that it gets back from this cache. The problem's going to be that no matter how you got there, the upper level VFS that has the device on it will probably get in your way. Really, the vnode cache wants to be in common upper level code, and let you set a falg on the vnode in the lowest level code that's still a VFS (in this case, specfs) to say "don't cache this thing, please, I want each open to call my device open, because each open is different". > What I did is make a module that defines a struct cdevsw with the open/read/ > etc callbacks, then I register my calls for various devices entries with > make_dev(), and at the end used the DEV_MODULE() macro to declare it to the > system. I modeled that after the example in /usr/src/share/examples/kld of > FreeBSD 4 This is the way to do it. > Is there a different driver/module architecture ? You will need to change the existing architecture to be able to do what you want, without having to have a different device name be used for each open (in order to get cloning devices). The actual "clone" event is when the upper level VFS where the device lives calls down to the specfs to the device to get a vnode with a device with a different minor number, and a different vnode to point to it, so that the per process open file table won't get confused. > > This is actually the primary reason that VMWARE can only run > > one instance at a time of a virtual machine: there is no way > > to have per open instance resources, which are not shared. > > > > If you were to use the TFS flag (grep for TFS in the headers, > > that's a substring), you could make specfs own its own vnodes. > > Where should I look for this ? I looked into /usr/src/ and only some > references to NTFS and TFS filesystems turned up ? vfs.h. You aren't going to see an FS, only the flag that lets an FS own its own vnodes (and it's a kludge). The documentation above is much more thorough (and I expect it will be corrected here and there by people reading this, or by you, when you dive into the code and find somewhere where I've given you old information). > Would I have to roll out a custom filesystem to have this running ? No. You just have to change the way the specfs is treated by the system. Mostly, I run systems without a specfs, since I think that struct fileops is a terrible, terrible kludge, but my code has diverged significantly since 1995, and continues to diverge even more radically as time goes on (so it won't be much use to you, since I haven't pulled a [Linux] Alan Cox and don't maintain an FTP distribution point for my changes, or sync them with the source tree more thanonce a month or so -- sorry). > > The way you would handle your problem then is by returning a > > different instance of the device, with a different instance of > > per process attached storage. It's pretty simple to do this: > > just return a different vnode for the next open of the same > > device, instead of the same vnode with an additional reference. > > this is really confusing me... in the example I had, the only thing I return > from my open routine is an int telling success or errors happened... any > pointers for the vnode stuff ? if it could apply to what I am trying to do ? > > Am I basing my driver on the wrong stuff ? No. You are basing your driver on the current FreeBSD state of the art. If you don't push for a higher state of the art, you will not be able to do what you want, and you will need to not use a clone device to do what you want. If you want to go this route, look at the library code for openpty(), and look at the pty driver. Basically, you will need to: 1) Create a bunch of minor devices off the same major 2) Open each minor device only once, and make your code iterate through all possible minor devices, before giving up. > > NB: If you are trying to do this for VMWARE or some other binary > > code, there's no way that the pty opening soloution suggested in > > the previous posting will be able to work for you, since the code > > Yes, I came to that conclusion too. So I can assume that this is a binary interface issue? If it's a kernel space issue, and _never_ a user space issue, you might be able to kludge this by calling your clone interface internally, once per minor number. The resource tracking for doing this right will be a pain, but should work. If it's a user space issue, then you will need to make cloning devices work. Unfortunately, many of the things I have described above will be a problem for you, or I'd just say "use a portal, and make it map to multiple real devices, one for each time you open the portal". The caching issues and notification issues noted above would still kill you with a portal, though, and a portal will look like a different special file type, instead of looking like a device, so you would not be able to ioctl() or otherwise treat the thing as a device. The problem is that there will be great resistance to these changes, since they will have to be broken up into pieces to get past reviewers. Since you have to have the directory cache in common code up front, this is going to be the hardest sell, since people will see no difference in functionality, until other code is written (it will look like a gratuitous change to the unenlightened). I had similar problems when I wanted to make unrelated VFS changes which would eventually have led to working stacking, since they were unwilling to take such a large chunk at one time, and they were unwilling to take what they considered gratuitous changes, once it was broken up into pieces that were small enough that they would accept them. As you can see above, the required changes are a little bit larger in scope than I recently led Jordan Hubbard to believe (if you followed that discussion). But I think they are necessary to permit progress in research in the area where you are doing your work (I did a similar thing back in 1997, which is part of my source base, in order to get true cloning pty drivers). If you can get even partial buy-in from a core team member, you will be much better off. Poul-Henning has shown some interest in this are, with some of his recent work on his own cloning implementation requiring devfs, but I think his code is far from complete (unless he has uncommitted patches he is willing to share). I can advise you on implementation, and even give you some code bits that aren't too far out of sync with how FreeBSD works, but for some things, you will be on your own (e.g. in my system, vnodes are already owned by each VFS, and have been for years, so I don't have the TFS issue to deal with to kludge around the system owning the things, etc.). Good luck, and I hope this has at least given you more insight into what's involved, and where to look in the source for more answers. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 10:39:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6E55237B4E5 for ; Thu, 9 Nov 2000 10:39:46 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA24611; Thu, 9 Nov 2000 10:39:43 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id eA9IdgH30450; Thu, 9 Nov 2000 10:39:42 -0800 (PST) (envelope-from jdp) Date: Thu, 9 Nov 2000 10:39:42 -0800 (PST) Message-Id: <200011091839.eA9IdgH30450@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Reply-To: hackers@freebsd.org Cc: leonardjo@hetnet.nl Subject: Re: [OT] serial protocol analyzer In-Reply-To: <3A0AF50D.16530.974B26@localhost> References: <3A0AF50D.16530.974B26@localhost> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3A0AF50D.16530.974B26@localhost>, Leonard den Ottolander wrote: > I was wondering if somebody could point me out a serial protocol > analyzer. Maybe analyzer is too big a word for what I am looking > for (I could be the analyzer :) ). What I am thinking of is a piece > of software that listens on two serial devices, and mimics input > from either to the other, in the mean time dumping and/or analyzing > the traffic. To be concrete: I want to put a box with this piece of > software between another box and its modem to analyze the traffic. Try the "comms/snooper" port. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 11:44:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tor3.targetnet.com (smtp.tor3.targetnet.com [207.176.132.71]) by hub.freebsd.org (Postfix) with ESMTP id 9118737B4CF; Thu, 9 Nov 2000 11:44:42 -0800 (PST) Received: from james by smtp.tor3.targetnet.com with local (Exim 3.16 #1) id 13txcn-000AKQ-00; Thu, 09 Nov 2000 14:44:41 -0500 Date: Thu, 9 Nov 2000 14:44:41 -0500 From: James FitzGibbon To: hackers@freebsd.org Cc: scsi@freebsd.org Subject: USB-to-SCSI converter Message-ID: <20001109144441.A39548@targetnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Targetnet.com Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a Microtech USB to SCSI converter (see http://www.microtechint.com/qs-usbscsi.html for details). Under Windows (having installed the driver that comes with), everything works without issue. Under BSD, I get this on boot: umass0: Microtech International, Inc. USB-SCSI-HD50, rev 1.00/1.00, addr 3 umass0: Get Max Lun not supported (STALLED) Are there any known workarounds for this problem ? In my particular application I won't be using multi-lun devices, but I don't think that making a "maxlun=0" assumption is a good thing to do. Are there any known workarounds for this problem ? Thanks. -- j. James FitzGibbon james@targetnet.com Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 11:52:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from henny.webweaving.org (unknown [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 0A9EB37B479; Thu, 9 Nov 2000 11:52:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id TAA40253; Thu, 9 Nov 2000 19:51:03 GMT (envelope-from n_hibma@qubesoft.com) Date: Thu, 9 Nov 2000 19:51:03 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: James FitzGibbon Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter In-Reply-To: <20001109144441.A39548@targetnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is not a problem as the thing works although it displays the message. Because it does not support the call it gives an indication that multi LUN devices are not supported. I have one of these cables and managed to newfs a 4Gb SCSI drive. Was anything connected to the cable when you connected it? Nick > I have a Microtech USB to SCSI converter (see > http://www.microtechint.com/qs-usbscsi.html for details). > > Under Windows (having installed the driver that comes with), everything > works without issue. Under BSD, I get this on boot: > > umass0: Microtech International, Inc. USB-SCSI-HD50, rev 1.00/1.00, addr 3 > umass0: Get Max Lun not supported (STALLED) > > Are there any known workarounds for this problem ? In my particular > application I won't be using multi-lun devices, but I don't think that > making a "maxlun=0" assumption is a good thing to do. > > Are there any known workarounds for this problem ? > > Thanks. > > -- > j. > > James FitzGibbon james@targetnet.com > Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 12: 0:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 0D1E937B479; Thu, 9 Nov 2000 12:00:06 -0800 (PST) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id NAA01854; Thu, 9 Nov 2000 13:59:36 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 9 Nov 2000 13:59:36 -0600 (CST) From: Chris Dillon To: Nick Hibma Cc: James FitzGibbon , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Nov 2000, Nick Hibma wrote: > This is not a problem as the thing works although it displays the > message. Because it does not support the call it gives an > indication that multi LUN devices are not supported. > > I have one of these cables and managed to newfs a 4Gb SCSI drive. > > Was anything connected to the cable when you connected it? I'm looking for a USB to SCSI converter myself... are there any that are a little more well-behaved and work great with FreeBSD and Windows (preferably one that Win98+ will see without having to carry around a driver disk)? I doubt I'll ever attach multi-lun devices to it either, but I don't like my options limited. :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64 and PowerPC under development. 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 Thu Nov 9 12: 7: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tor3.targetnet.com (smtp.tor3.targetnet.com [207.176.132.71]) by hub.freebsd.org (Postfix) with ESMTP id B7A8E37B479; Thu, 9 Nov 2000 12:06:59 -0800 (PST) Received: from james by smtp.tor3.targetnet.com with local (Exim 3.16 #1) id 13txyA-000Afw-00; Thu, 09 Nov 2000 15:06:46 -0500 Date: Thu, 9 Nov 2000 15:06:46 -0500 From: James FitzGibbon To: Nick Hibma Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter Message-ID: <20001109150646.B39548@targetnet.com> References: <20001109144441.A39548@targetnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from n_hibma@qubesoft.com on Thu, Nov 09, 2000 at 07:51:03PM +0000 Organization: Targetnet.com Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Nick Hibma (n_hibma@qubesoft.com) [001109 14:52]: > > This is not a problem as the thing works although it displays the > message. Because it does not support the call it gives an indication > that multi LUN devices are not supported. > > I have one of these cables and managed to newfs a 4Gb SCSI drive. > > Was anything connected to the cable when you connected it? Yes, I've tried with a Yahama external CDR and a Syquest Syjet drive. In neither case did the device show up on the probe. I do have "SCSI over USB" working on the box, since I regularly use a USB zip drive on the same machine and it comes up as device da0 right after the 'umass-sim0' probe. Can you share your kernel config and/or dmesg for that 4gb drive you mention ? Thanks. -- j. James FitzGibbon james@targetnet.com Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 12: 8:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from linus.dvart.com (linus.dvart.com [64.79.2.3]) by hub.freebsd.org (Postfix) with ESMTP id 0B55337B479 for ; Thu, 9 Nov 2000 12:08:15 -0800 (PST) Received: from dvart.com ([192.168.100.141]) by linus.dvart.com (8.9.3/8.9.3) with ESMTP id MAA23812; Thu, 9 Nov 2000 12:08:11 -0800 Message-ID: <3A0B042B.BAABCBDE@dvart.com> Date: Thu, 09 Nov 2000 12:08:11 -0800 From: bruno schwander X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: close call in a device ? References: <200011091827.LAA22910@usr08.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you infinitely for all this information. It will take me a while to absorb and poke around in the right places but this is definitely extremely useful, thank you. I will most probably come back to you with more questions, in a near future time... bruno Terry Lambert wrote: > > > To add to this, the close calls can be forces; there is a flag > > > in the device structure wich can force notification. I'm not > > > sure what it does over a fork(), though: I think you really want > > > open notification. > > > > You mean that when I register my device/kernel module, I can > > explicitely request that all close calls will notify my module? > > That is exactly what I need. > > Add D_TRACKCLOSE to d_flags for your device. When the d_close() > of your device is call, the first arg is the dev. > snip ... much much more .... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 12:23:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from planet.gaumina.lt (unknown [193.219.211.17]) by hub.freebsd.org (Postfix) with SMTP id DECAC37B479 for ; Thu, 9 Nov 2000 12:23:27 -0800 (PST) Received: (qmail 22765 invoked from network); 9 Nov 2000 21:16:56 -0000 Received: from unknown (HELO daemon) (205.244.197.148) by mail.centras.lt with SMTP; 9 Nov 2000 21:16:56 -0000 Message-ID: <000901c01f53$26932ce0$f9ecfea9@daemon> From: "Edvard Gess" To: Subject: Date: Fri, 15 Sep 2000 22:25:26 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C01F63.D90CEC20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C01F63.D90CEC20 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Hello, dear friends!!! Sorry for mistakes I am from Lithuania = :-) I'm 16 years old and I can't live without FreeBSD ! I want to = develope it, but I think that I have not enougth knowledge :-( In my = country I can't get FreeBSD :-( And my connection speed is 16k(I can't = get FreeBSD from the Internet) Would you tell me what I must to do to develope FreeBSD, and where I = can get it? I haven't a lot of money, but I want to work for FREE, I = want learning!!! And I want to help you!!! Please tell me what I must to = know to write own OS parts? Please trust me, my life in Lithuania is very hard! And I wanna get = better life! I wanna start! ------=_NextPart_000_0006_01C01F63.D90CEC20 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
        = Hello, dear=20 friends!!! Sorry for mistakes I am from Lithuania :-)
 
    I'm 16 years old and = I can't=20 live without FreeBSD ! I want to develope it, but I think that I = have not=20 enougth knowledge :-( In my country I can't get FreeBSD :-( And my = connection=20 speed is 16k(I can't get FreeBSD from the Internet)
 
    Would you tell me = what I must to=20 do to develope FreeBSD, and where I can get it? I haven't a lot of = money, but I=20 want to work for FREE, I want learning!!! And I want to help you!!! = Please tell=20 me what I must to know to write own OS parts?
 
    Please trust me, my = life in=20 Lithuania is very hard! And I wanna get better life!
I wanna = start!
------=_NextPart_000_0006_01C01F63.D90CEC20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 12:27: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 3C70B37B479 for ; Thu, 9 Nov 2000 12:27:04 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eA9KR3a92709 for ; Thu, 9 Nov 2000 13:27:03 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200011092027.eA9KR3a92709@aslan.scsiguy.com> To: current@FreeBSD.org Subject: FreeBSD Foundation: Examples of FreeBSD as teaching aid/research plat Date: Thu, 09 Nov 2000 13:26:09 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As some of you may know, I'm working on a 501(c)3 (tax exempt/non-profit) determination for the FreeBSD Foundation. The IRS seems to be a little confused about the nature of FreeBSD and we're currenlty working on a response to an initial determination from the IRS that was not favorable. One thing that would help us to explain the nature of FreeBSD and how it is used by the public is to enumerate some specific examples of how FreeBSD is used as either a teaching aid or a research platform by educational institutions. If possible, please include a contact name, email, or phone number so we can ask additional questions if necessary. Thanks in advance for your help! Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 13: 5:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.hitbase.com (ns.hitbase.com [64.65.2.58]) by hub.freebsd.org (Postfix) with ESMTP id 5372337B479 for ; Thu, 9 Nov 2000 13:05:08 -0800 (PST) Received: from dima ([212.48.199.30]) by ns.hitbase.com (8.9.3/8.9.3) with SMTP id RAA27396 for ; Thu, 9 Nov 2000 17:01:46 -0500 Message-ID: <002001c04a91$10f0be20$1ec730d4@dima> From: "Dmitry Sychov" To: Subject: aio_read() broken functionality. Date: Fri, 10 Nov 2000 00:07:24 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001B_01C04AAA.33FBA740" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_001B_01C04AAA.33FBA740 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Greetings. According to manual the aio_offset field of the "aiocb" structure is ignored in the aio_read() call. So one can read the file only from beginning. Very bad for me. :-( Will this bug be fixed in FreeBSD 5.0? Thank you! Dmitry ------=_NextPart_000_001B_01C04AAA.33FBA740 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
Greetings.
 
According to = manual the=20 aio_offset field of the "aiocb" structure
is ignored in the = aio_read()=20 call. So one can read the file only from
beginning. Very bad for me. :-(
 
Will this bug be fixed in FreeBSD = 5.0?
 
Thank you!
Dmitry
 
 
------=_NextPart_000_001B_01C04AAA.33FBA740-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 13:10:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tor3.targetnet.com (smtp.tor3.targetnet.com [207.176.132.71]) by hub.freebsd.org (Postfix) with ESMTP id E816337B4C5 for ; Thu, 9 Nov 2000 13:10:45 -0800 (PST) Received: from james by smtp.tor3.targetnet.com with local (Exim 3.16 #1) id 13tyy5-000BPX-00 for hackers@freebsd.org; Thu, 09 Nov 2000 16:10:45 -0500 Date: Thu, 9 Nov 2000 16:10:45 -0500 From: James FitzGibbon To: hackers@freebsd.org Subject: Repeatable STL core with -pthread Message-ID: <20001109161045.D39548@targetnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Targetnet.com Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We're having a problem with threaded programs that use the STL. Given the following program: --START-- #include #include typedef map mymap_t; #ifdef GLOBLOCK pthread_mutex_t glob_mut; #endif void *run(void *) { while (1) { string f(""); #ifdef GLOBLOCK pthread_mutex_lock(&glob_mut); #endif f += "adsasd"; f += "adsasd"; f += "adsasd"; #ifdef GLOBLOCK pthread_mutex_unlock(&glob_mut); #endif } } int main () { #define FOO 50 pthread_t thread[FOO]; for(int x =0;x; Thu, 9 Nov 2000 13:23:44 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eA9LNdu05745; Thu, 9 Nov 2000 13:23:39 -0800 (PST) Date: Thu, 9 Nov 2000 13:23:39 -0800 From: Alfred Perlstein To: Dmitry Sychov Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read() broken functionality. Message-ID: <20001109132339.B5112@fw.wintelcom.net> References: <002001c04a91$10f0be20$1ec730d4@dima> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <002001c04a91$10f0be20$1ec730d4@dima>; from accelware@accelware.com on Fri, Nov 10, 2000 at 12:07:24AM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dmitry Sychov [001109 13:06] wrote: > Greetings. > > According to manual the aio_offset field of the "aiocb" structure > is ignored in the aio_read() call. So one can read the file only from > beginning. Very bad for me. :-( > > Will this bug be fixed in FreeBSD 5.0? Hrm, parsing through the kernel code it looks like this is just a bug in the manpage, basically aio_offset doesn't look like it's ignored, can you try to use aio_offset and report if it works or not. Please submit some test code if it doesn't. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 13:36:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.west.se (unknown [194.52.130.37]) by hub.freebsd.org (Postfix) with ESMTP id 94E3437B4C5 for ; Thu, 9 Nov 2000 13:36:40 -0800 (PST) Received: from west.se (bashful [192.168.0.14]) by mail.west.se (8.11.0/8.9.3) with ESMTP id eA9FbxH71867 for ; Thu, 9 Nov 2000 16:37:59 +0100 (CET) (envelope-from bjorn.tornqvist@west.se) Message-ID: <3A0AC4FB.DEE94ED9@west.se> Date: Thu, 09 Nov 2000 16:38:35 +0100 From: Bjorn Tornqvist Organization: West AB X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.2-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Modifying msgrcv() and msgsnd() Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm going to add 2 functioncalls to the kernel; msgrcv_t() msgsnd_t() ("t" as in timeout) where the user will be able to specify a maximum amount of time they are prepared to wait for a message to be sent or become available. I just wonder if the rest of the freebsd community is interested in these kinds of additions to the kernel? I'm pretty certain there is alot more people out there who'd like this functionality. Should I bother posting them to the list? As a sidenote: The main reason I need this is since I can't use longjmp()/setjmp() with alarm() between pthread contexts; with FreeBSD 5.0 this fix probably won't be necessary (but still nice to have though). And besides, I'd get paid to contribute to the project! =) Greetings, Bjorn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 13:42:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8D5CE37B479 for ; Thu, 9 Nov 2000 13:42:29 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eA9LgRa06784; Thu, 9 Nov 2000 13:42:27 -0800 (PST) Date: Thu, 9 Nov 2000 13:42:27 -0800 From: Alfred Perlstein To: Bjorn Tornqvist Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Modifying msgrcv() and msgsnd() Message-ID: <20001109134226.C5112@fw.wintelcom.net> References: <3A0AC4FB.DEE94ED9@west.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <3A0AC4FB.DEE94ED9@west.se>; from bjorn.tornqvist@west.se on Thu, Nov 09, 2000 at 04:38:35PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Bjorn Tornqvist [001109 13:38] wrote: > > Hi! > > I'm going to add 2 functioncalls to the kernel; msgrcv_t() msgsnd_t() > ("t" > as in timeout) where the user will be able to specify a maximum amount > of > time they are prepared to wait for a message to be sent or become > available. > > I just wonder if the rest of the freebsd community is interested in > these > kinds of additions to the kernel? I'm pretty certain there is alot more > people out there who'd like this functionality. Should I bother posting > them to the list? > > As a sidenote: The main reason I need this is since I can't use > longjmp()/setjmp() with alarm() between pthread contexts; with FreeBSD > 5.0 > this fix probably won't be necessary (but still nice to have though). > > And besides, I'd get paid to contribute to the project! =) Actually, what i'd like to see is kqueue filters able to attach to sysVipc. I'm pretty sure something like msgrcv_t()/msgsnd_t() won't make it into the kernel, however I'd take a personal interest in having kqueue'able sysV message queues and would be happy to assist you in getting that into the kernel. I'm also unsure why you'd want a "timeout", although it'd be less effecient you could effectively poll by using IPC_NOWAIT and usleep(3) or nanosleep(2). -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 13:47:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 733AF37B479 for ; Thu, 9 Nov 2000 13:47:50 -0800 (PST) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id C36B5193DF; Thu, 9 Nov 2000 15:47:49 -0600 (CST) Received: (from nectar@localhost) by hamlet.nectar.com (8.11.1/8.9.3) id eA9Llni25732; Thu, 9 Nov 2000 15:47:49 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Date: Thu, 9 Nov 2000 15:47:49 -0600 From: "Jacques A. Vidrine" To: Bjorn Tornqvist Cc: freebsd-hackers@freebsd.org Subject: Re: Modifying msgrcv() and msgsnd() Message-ID: <20001109154749.A25637@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , Bjorn Tornqvist , freebsd-hackers@freebsd.org References: <3A0AC4FB.DEE94ED9@west.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A0AC4FB.DEE94ED9@west.se>; from bjorn.tornqvist@west.se on Thu, Nov 09, 2000 at 04:38:35PM +0100 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 09, 2000 at 04:38:35PM +0100, Bjorn Tornqvist wrote: > I'm going to add 2 functioncalls to the kernel; msgrcv_t() msgsnd_t() > ("t" as in timeout) where the user will be able to specify a maximum > amount of time they are prepared to wait for a message to be sent or > become available. > > I just wonder if the rest of the freebsd community is interested in > these kinds of additions to the kernel? I'm pretty certain there is > alot more people out there who'd like this functionality. Should I > bother posting them to the list? > > As a sidenote: The main reason I need this is since I can't use > longjmp()/setjmp() with alarm() between pthread contexts; with FreeBSD > 5.0 this fix probably won't be necessary (but still nice to have > though). > > And besides, I'd get paid to contribute to the project! =) I think this might be better handled by a kevent filter for message queues, if you are going to hack something in the kernel for your application. At least then it might find some general use. -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 14:31:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from henny.webweaving.org (unknown [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 36D8737B479; Thu, 9 Nov 2000 14:31:23 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id UAA40361; Thu, 9 Nov 2000 20:17:57 GMT (envelope-from n_hibma@qubesoft.com) Date: Thu, 9 Nov 2000 20:17:57 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: James FitzGibbon Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter In-Reply-To: <20001109150646.B39548@targetnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Which version of the OS? Please update to a recent release of 4-STABLE if you are not there. Did you do a camcontrol rescan 0? What does that produce? All you will need is kldload usb kldload cam kldload umass or compile with the following options (I am not sure whether the CAM module is available in stable) device scbus device da device usb device umass Hope this helps. Nick On Thu, 9 Nov 2000, James FitzGibbon wrote: > * Nick Hibma (n_hibma@qubesoft.com) [001109 14:52]: > > > > > This is not a problem as the thing works although it displays the > > message. Because it does not support the call it gives an indication > > that multi LUN devices are not supported. > > > > I have one of these cables and managed to newfs a 4Gb SCSI drive. > > > > Was anything connected to the cable when you connected it? > > Yes, I've tried with a Yahama external CDR and a Syquest Syjet drive. In > neither case did the device show up on the probe. I do have "SCSI over USB" > working on the box, since I regularly use a USB zip drive on the same > machine and it comes up as device da0 right after the 'umass-sim0' probe. > > Can you share your kernel config and/or dmesg for that 4gb drive you mention > ? > > Thanks. > > -- > j. > > James FitzGibbon james@targetnet.com > Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 14:31:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from henny.webweaving.org (unknown [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 4064637B4C5; Thu, 9 Nov 2000 14:31:25 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id UAA40368; Thu, 9 Nov 2000 20:20:42 GMT (envelope-from n_hibma@qubesoft.com) Date: Thu, 9 Nov 2000 20:20:42 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: James FitzGibbon Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter In-Reply-To: <20001109150646.B39548@targetnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hm, I missed the zip story. You seem to have all the bits that are necessary in your kernel. Could you compile your kernel/module with UMASS_DEBUG defined and send me the output after an attach? The 'GetMAXLUN not supported' thing does not make the driver fail, it makes it just assume that the LUN is always 0. Nick On Thu, 9 Nov 2000, James FitzGibbon wrote: > * Nick Hibma (n_hibma@qubesoft.com) [001109 14:52]: > > > > > This is not a problem as the thing works although it displays the > > message. Because it does not support the call it gives an indication > > that multi LUN devices are not supported. > > > > I have one of these cables and managed to newfs a 4Gb SCSI drive. > > > > Was anything connected to the cable when you connected it? > > Yes, I've tried with a Yahama external CDR and a Syquest Syjet drive. In > neither case did the device show up on the probe. I do have "SCSI over USB" > working on the box, since I regularly use a USB zip drive on the same > machine and it comes up as device da0 right after the 'umass-sim0' probe. > > Can you share your kernel config and/or dmesg for that 4gb drive you mention > ? > > Thanks. > > -- > j. > > James FitzGibbon james@targetnet.com > Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 14:31:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from henny.webweaving.org (unknown [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id DFC4D37B661; Thu, 9 Nov 2000 14:31:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id UAA40350; Thu, 9 Nov 2000 20:01:51 GMT (envelope-from n_hibma@qubesoft.com) Date: Thu, 9 Nov 2000 20:01:50 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: Chris Dillon Cc: James FitzGibbon , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The cable is pretty decent and the fact that it does not support the call is not a problem. Nick On Thu, 9 Nov 2000, Chris Dillon wrote: > On Thu, 9 Nov 2000, Nick Hibma wrote: > > > This is not a problem as the thing works although it displays the > > message. Because it does not support the call it gives an > > indication that multi LUN devices are not supported. > > > > I have one of these cables and managed to newfs a 4Gb SCSI drive. > > > > Was anything connected to the cable when you connected it? > > I'm looking for a USB to SCSI converter myself... are there any that > are a little more well-behaved and work great with FreeBSD and Windows > (preferably one that Win98+ will see without having to carry around a > driver disk)? I doubt I'll ever attach multi-lun devices to it > either, but I don't like my options limited. :-) > > > -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net > FreeBSD: The fastest and most stable server OS on the planet. > For IA32 and Alpha architectures. IA64 and PowerPC under development. > http://www.freebsd.org > > > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 15: 9:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.integratus.com (unknown [63.209.2.83]) by hub.freebsd.org (Postfix) with SMTP id 604AE37B479 for ; Thu, 9 Nov 2000 15:09:04 -0800 (PST) Received: (qmail 6677 invoked from network); 9 Nov 2000 23:08:55 -0000 Received: from kungfu.integratus.com (HELO integratus.com) (172.20.5.168) by tortuga1.integratus.com with SMTP; 9 Nov 2000 23:08:55 -0000 Message-ID: <3A0B2E87.3B49887B@integratus.com> Date: Thu, 09 Nov 2000 15:08:55 -0800 From: Jack Rusher Organization: http://www.integratus.com/ X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: James FitzGibbon Cc: hackers@freebsd.org Subject: Re: Repeatable STL core with -pthread References: <20001109161045.D39548@targetnet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James FitzGibbon wrote: > > The program will core after about 10 seconds, every time. > It would appear that there is an issue with some low-level allocator in the > STL as shipped in 4.x. Dude. The STL implementation that ships with g++ isn't thread safe. In fact, if you read the STL portion of the C++ specification, you will notice that threads are not mentioned at all. The only guarantees made by the STL are that operations will complete within certain performance guidelines. As a safety tip, the string implementation in the g++ implementation isn't thread safe either. It uses a shared buffer scheme ("char* string->rep") to reduce memory consumption & improve performance. This is in opposition to "deep copy" style libraries, like the SGI STL, that work in threaded environments. Because of the way the C++ standard is written, commercial STL implementations, such as the Rogue Wave library that comes with the Sun C++ compiler, suffer from the same threading problems. -- Jack Rusher, Senior Engineer | mailto:jar@integratus.com Integratus, Inc. | http://www.integratus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 16:23:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rye.elite.net (rye.elite.net [205.199.220.6]) by hub.freebsd.org (Postfix) with ESMTP id 0D25437B479 for ; Thu, 9 Nov 2000 16:23:53 -0800 (PST) Received: from localhost (bangel@peach.elite.net [205.199.220.25]) by rye.elite.net (8.9.3/8.9.3) with SMTP id QAA18028 for ; Thu, 9 Nov 2000 16:23:52 -0800 (PST) Date: Thu, 9 Nov 2000 16:24:12 -0800 (PST) From: Keith Simonsen X-Sender: bangel@localhost To: hackers@freebsd.org Subject: bad hardware? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, Just curious if anyone has come across this error before, because I haven't... Nov 9 16:05:00 peach sshd[9275]: Disconnecting: Corrupted check bytes on input. Does anyone think it could be bad ram? I'm going to cvsup and run a buildworld and see how that goes... Thanks Keith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 21: 8:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id B223337B479 for ; Thu, 9 Nov 2000 21:08:24 -0800 (PST) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13u6QJ-0002ep-00; Fri, 10 Nov 2000 05:08:23 +0000 Date: Fri, 10 Nov 2000 05:08:23 +0000 From: void To: hackers@freebsd.org Subject: Re: "iowait" CPU state Message-ID: <20001110050823.A10063@firedrake.org> References: <20001109174946.B21468@firedrake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from andrew@ugh.net.au on Fri, Nov 10, 2000 at 12:33:31PM +1000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 10, 2000 at 12:33:31PM +1000, andrew@ugh.net.au wrote: > On Thu, 9 Nov 2000, void wrote: > > > not how busy the disks are. I want relative data, not absolute. > > systat -vmstat? Thank you! This gets the me disk %busy, which is one of the things I was looking for. Now, can anyone tell me how to tell what percentage of processor time is being spent waiting for disk I/O to complete? -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 21: 8:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.cs.umn.edu (mail.cs.umn.edu [128.101.35.200]) by hub.freebsd.org (Postfix) with ESMTP id AF7B337B479 for ; Thu, 9 Nov 2000 21:08:51 -0800 (PST) Received: from barber.cs.umn.edu (IDENT:root@barber.cs.umn.edu [128.101.35.60]) by mail.cs.umn.edu (8.9.3/8.9.3) with ESMTP id XAA19369 for ; Thu, 9 Nov 2000 23:08:47 -0600 (CST) Received: from localhost (duan@localhost) by barber.cs.umn.edu (8.9.3/8.9.0) with ESMTP id XAA24986 for ; Thu, 9 Nov 2000 23:08:46 -0600 X-Authentication-Warning: barber.cs.umn.edu: duan owned process doing -bs Date: Thu, 9 Nov 2000 23:08:46 -0600 (CST) From: Zhenhai Duan To: freebsd-hackers@FreeBSD.ORG Subject: printf() Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A simple question: Does the kernel function printf() flushes the output immediately, or it is possible some data is buffered somewhere and gets lost without printing to the console? like the corresponding funtion in the c library. Thanks. --Zhenhai To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 21:44: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 97FF037B479 for ; Thu, 9 Nov 2000 21:44:05 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAA5i4Y23049; Thu, 9 Nov 2000 21:44:04 -0800 (PST) Date: Thu, 9 Nov 2000 21:44:04 -0800 From: Alfred Perlstein To: Zhenhai Duan Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: printf() Message-ID: <20001109214403.V11449@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from duan@cs.umn.edu on Thu, Nov 09, 2000 at 11:08:46PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Zhenhai Duan [001109 21:09] wrote: > A simple question: > > Does the kernel function printf() flushes the output immediately, or it is > possible some data is buffered somewhere and gets lost without printing > to the console? like the corresponding funtion in the c library. It's not buffered afaik. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 9 22:31:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 75DD637B479 for ; Thu, 9 Nov 2000 22:31:20 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13u7jN-0000TD-00; Thu, 09 Nov 2000 23:32:09 -0700 Message-ID: <3A0B9669.B9FCCF94@softweyr.com> Date: Thu, 09 Nov 2000 23:32:09 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Dmitry Sychov , freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read() broken functionality. References: <002001c04a91$10f0be20$1ec730d4@dima> <20001109132339.B5112@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > * Dmitry Sychov [001109 13:06] wrote: > > Greetings. > > > > According to manual the aio_offset field of the "aiocb" structure > > is ignored in the aio_read() call. So one can read the file only from > > beginning. Very bad for me. :-( > > > > Will this bug be fixed in FreeBSD 5.0? > > Hrm, parsing through the kernel code it looks like this is just a > bug in the manpage, basically aio_offset doesn't look like it's > ignored, can you try to use aio_offset and report if it works or > not. It was probably correct when the manpage was written. This seems to be yet another bit of doco that has not been updated along with the system. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 0:49:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 9992637B479 for ; Fri, 10 Nov 2000 00:49:37 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id JAA68090; Fri, 10 Nov 2000 09:49:35 +0100 (CET) (envelope-from des@ofug.org) 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: void Cc: hackers@FreeBSD.ORG Subject: Re: "iowait" CPU state References: <20001107054413.A1983@firedrake.org> <20001109175050.C21468@firedrake.org> From: Dag-Erling Smorgrav Date: 10 Nov 2000 09:49:34 +0100 In-Reply-To: void's message of "Thu, 9 Nov 2000 17:50:50 +0000" Message-ID: Lines: 10 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG void writes: > Is there any reason top couldn't add these up and report a %iowait > like Solaris'? Yes. It would conceal valuable information. Do the adding up in your head. 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 Fri Nov 10 1:26:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 8C14437B479 for ; Fri, 10 Nov 2000 01:26:12 -0800 (PST) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id LAA01096; Fri, 10 Nov 2000 11:25:56 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 991; Fri Nov 10 11:25:14 2000 Message-ID: <3A0BA675.474EA77B@cequrux.com> Date: Fri, 10 Nov 2000 09:40:37 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dan Nelson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Help writing a screen saver module References: <3A06B7A7.7665C46A@cequrux.com> <20001107144202.B4569@dan.emsphone.com> Content-Type: multipart/mixed; boundary="------------9A44061129438E75E5872412" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------9A44061129438E75E5872412 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Dan Nelson wrote: > > In the last episode (Nov 07), Dag-Erling Smorgrav said: > > Graham Wheeler writes: > > > I am trying to write a screen saver module that, when it kicks in, > > > will switch to the first console, and then, if a key is pressed, > > > will switch back to the one that was previously active. The idea is > > > that the first console has something useful running on it, > > > typically a tail -f of the logs. > > > You can make it look like you're switched to vty 0, by making your > screen_saver() function simply copy the contents of vty 0 to screen > memory on every update. Just make sure both vtys are the same size > first... Okay, got it working. I've attached my code if anyone is interested. Thanks for all the help Dan. I have another question now - it would be great if I could put a message on the top or bottom line of /dev/ttyv0, in inverse video, and have the output of the `tail -f' go to a scrolling region in the rest of the screen. The idea here is, on /dev/ttyv0, to have a message "Press Alt-Fn (n=1,2,..) for Login Consoles". The screen saver would replace this with "Press any key to stop watching logs and return to login console", or something like that. It would be nice, but its not too important... gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 --------------9A44061129438E75E5872412 Content-Type: text/plain; charset=us-ascii; name="switch_saver.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="switch_saver.c" #include #include #include #include #include #include #include #include #include #ifndef SC_STAT #define SC_STAT sc_get_scr_stat #endif #ifndef MAXCONS #define MAXCONS 16 #endif void CopyConsoleContents(video_adapter_t *adp, int from) { if (from>=0 && fromscr_buf && adp->va_window && fc->ysize == adp->va_info.vi_height && fc->xsize == adp->va_info.vi_width) { int len = fc->ysize * fc->xsize, pos; for (pos = 0; pos < len; ++pos) writew(adp->va_window+pos*2, fc->scr_buf[pos]); } splx(s); } } static int switch_saver(video_adapter_t *adp, int blank) { if (adp->va_info.vi_flags & V_INFO_GRAPHICS) return EAGAIN; if (blank) CopyConsoleContents(adp, 0); return 0; } static int switch_init(video_adapter_t *adp) { (void)adp; return 0; } static int switch_term(video_adapter_t *adp) { (void)adp; return 0; } static scrn_saver_t switch_module = { "switch_saver", switch_init, switch_term, switch_saver, NULL, }; SAVER_MODULE(switch_saver, switch_module); --------------9A44061129438E75E5872412-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 2:15:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spammie.svbug.com (mg136-070.ricochet.net [204.179.136.70]) by hub.freebsd.org (Postfix) with ESMTP id AD05237B479 for ; Fri, 10 Nov 2000 02:15:35 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id CAA01227; Fri, 10 Nov 2000 02:13:01 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200011101013.CAA01227@spammie.svbug.com> Date: Fri, 10 Nov 2000 02:12:59 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: printf() To: bright@wintelcom.net Cc: duan@cs.umn.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <20001109214403.V11449@fw.wintelcom.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Nov, Alfred Perlstein wrote: > * Zhenhai Duan [001109 21:09] wrote: >> A simple question: >> >> Does the kernel function printf() flushes the output immediately, or it is >> possible some data is buffered somewhere and gets lost without printing >> to the console? like the corresponding funtion in the c library. > > It's not buffered afaik. > Actually my experince in writing drivers (for 386bsd) showed (me) that the kernel printf() was buffered. Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 2:29:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77]) by hub.freebsd.org (Postfix) with ESMTP id 9437537B479 for ; Fri, 10 Nov 2000 02:29:11 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAAAYk906022; Fri, 10 Nov 2000 02:34:47 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011101034.eAAAYk906022@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: opentrax@email.com Cc: bright@wintelcom.net, duan@cs.umn.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: printf() In-reply-to: Your message of "Fri, 10 Nov 2000 02:12:59 PST." <200011101013.CAA01227@spammie.svbug.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Nov 2000 02:34:46 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Does the kernel function printf() flushes the output immediately, or it is > >> possible some data is buffered somewhere and gets lost without printing > >> to the console? like the corresponding funtion in the c library. > > > > It's not buffered afaik. > > > Actually my experince in writing drivers (for 386bsd) showed (me) > that the kernel printf() was buffered. Considerable (ie. shitloads) of experience using the kernel printf with FreeBSD (not to mention reading the code line by line as I ported it for libstand) allows me to tell you that it isn't. And you're welcome to go read the code yourself, should you choose to take issue with that. 8) -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 3:17:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spammie.svbug.com (mg136-070.ricochet.net [204.179.136.70]) by hub.freebsd.org (Postfix) with ESMTP id 1E2FC37B479; Fri, 10 Nov 2000 03:17:34 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id DAA01311; Fri, 10 Nov 2000 03:17:32 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200011101117.DAA01311@spammie.svbug.com> Date: Fri, 10 Nov 2000 03:17:31 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: printf() To: msmith@FreeBSD.ORG Cc: bright@wintelcom.net, duan@cs.umn.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <200011101034.eAAAYk906022@mass.osd.bsdi.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10 Nov, Mike Smith wrote: >> >> Does the kernel function printf() flushes the output immediately, or it is >> >> possible some data is buffered somewhere and gets lost without printing >> >> to the console? like the corresponding funtion in the c library. >> > >> > It's not buffered afaik. >> > >> Actually my experince in writing drivers (for 386bsd) showed (me) >> that the kernel printf() was buffered. > > Considerable (ie. shitloads) of experience using the kernel printf with > FreeBSD (not to mention reading the code line by line as I ported it for > libstand) allows me to tell you that it isn't. > > And you're welcome to go read the code yourself, should you choose to > take issue with that. 8) > Sir, with regards to your experience and reading of the code, I should say that as you have read it, that would appear to be the situation. Better judgement - and testing to see how it might be buffered - would seem to be a challange. However, before we quest into what might be a futile battle on the definition of a word. Let's first agree that taken the code at face value you are correct. I will certainly not deny - code taken on face value to be code taken on value. Let us also agree that "buffering" might be defined in different ways. For instance, we could say, "buffering implies an actual level of intermediate storage that might (for some unknown reason) be delaying the output of a printf()" Show that be the case, then it would stem that our differences are minor, and could simply be a difference in interpetation or meaning of the word "buffered". As such, let me NOT blather on with meaningless dribble. Let us say, if we might, that there could be a delay in output two (2) seperate kernel printf() statements. Or said an other way, Is it possible for two (2) printf() statements NOT to be outputed in a linear fashinon? Ie. the first printf() statement get printed first, the second - second. If we differ on this point, then perhaps a example might be needed. As such, my example would only work under 386BSD, as I stated. Being your stated experience with FreeBSD, it is quite possible that I am incorrect. Should that be the case, then I stand correct. However, I see no evidence to such. Further my understanding or *BSD kernels, could be skewed, but past experience tells me otherwise. Is there is way that I could perhaps demonstrate my reasoning, such that it might be satisfactory to you? best regards, Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 3:26:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77]) by hub.freebsd.org (Postfix) with ESMTP id C1BAD37B479 for ; Fri, 10 Nov 2000 03:26:48 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAABWP906200; Fri, 10 Nov 2000 03:32:25 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011101132.eAABWP906200@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: opentrax@email.com Cc: bright@wintelcom.net, duan@cs.umn.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: printf() In-reply-to: Your message of "Fri, 10 Nov 2000 03:17:31 PST." <200011101117.DAA01311@spammie.svbug.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Nov 2000 03:32:25 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is there is way that I could perhaps demonstrate my reasoning, > such that it might be satisfactory to you? No. -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 3:31:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 6D96D37B479 for ; Fri, 10 Nov 2000 03:31:31 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA68819; Fri, 10 Nov 2000 12:31:27 +0100 (CET) (envelope-from des@ofug.org) 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: opentrax@email.com Cc: bright@wintelcom.net, duan@cs.umn.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: printf() References: <200011101013.CAA01227@spammie.svbug.com> From: Dag-Erling Smorgrav Date: 10 Nov 2000 12:31:26 +0100 In-Reply-To: opentrax@email.com's message of "Fri, 10 Nov 2000 02:12:59 -0800 (PST)" Message-ID: Lines: 9 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG opentrax@email.com writes: > [...] > Jessem. Amazing what people will do to evade killfiles. Plonk. 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 Fri Nov 10 5:10:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from transport.itb.ac.id (transport.itb.ac.id [167.205.9.60]) by hub.freebsd.org (Postfix) with SMTP id 1149C37B479 for ; Fri, 10 Nov 2000 05:10:33 -0800 (PST) Received: (qmail 5725 invoked by uid 1020); 10 Nov 2000 13:09:02 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 10 Nov 2000 13:09:02 -0000 Date: Fri, 10 Nov 2000 20:09:02 +0700 (JAVT) From: Fadli Syarid X-Sender: fadli@transport.itb.ac.id To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk 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 Fri Nov 10 5:27:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 00C4037B479 for ; Fri, 10 Nov 2000 05:27:44 -0800 (PST) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JWDMP9IT5Y00108Q@research.kpn.com> for freebsd-hackers@freebsd.org; Fri, 10 Nov 2000 14:27:41 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Fri, 10 Nov 2000 14:27:40 +0100 Content-return: allowed Date: Fri, 10 Nov 2000 14:27:31 +0100 From: "Koster, K.J." Subject: Legacy ethernet cards in FreeBSD To: 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D79E3@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear All, Last night I cvsupped my trusty old Compaq Deskpro XL 6200 from 4.0-release to 4.2-beta. As part of that process, I seem to have lost support for the on-board NIC (lnc0: PCNet/PCI Ethernet Adapter, PC-net-32 VL-Bus). What is the newest version of FreeBSD that will propely support that card? If there are people who are cleaning up the support for older network cards in FreeBSD I'd like to help out by sending you my old NICs. It's not like they're any good to me without OS support. Please contact me off-list for any of the following cards: 3Com 3c503 ISA DEC Etherworks ISA DEC DE205 ISA SMC EtherEZ ISA RealTek "TP-Link" PCI As far as I've been able to determine, none of these work properly. In particular, the RealTek card gets detected and pretends to work, but loses the link after a bit (The link status LED goes out, and I need to reboot the box.) I'll be happy to try out patches for the lnc driver to fix the problem of the Deskpro, or to give remote access to it if you want to work on it. Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 5:31:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spammie.svbug.com (mg136-070.ricochet.net [204.179.136.70]) by hub.freebsd.org (Postfix) with ESMTP id E61BC37B479; Fri, 10 Nov 2000 05:31:22 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id FAA01525; Fri, 10 Nov 2000 05:31:22 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200011101331.FAA01525@spammie.svbug.com> Date: Fri, 10 Nov 2000 05:31:18 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: printf() To: msmith@FreeBSD.ORG Cc: bright@wintelcom.net, duan@cs.umn.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <200011101132.eAABWP906200@mass.osd.bsdi.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10 Nov, Mike Smith wrote: >> >> Is there is way that I could perhaps demonstrate my reasoning, >> such that it might be satisfactory to you? > > No. > Then, should I take it you concede the point? Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 5:35:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77]) by hub.freebsd.org (Postfix) with ESMTP id 757B137B479; Fri, 10 Nov 2000 05:35:35 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAADfF906762; Fri, 10 Nov 2000 05:41:15 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011101341.eAADfF906762@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: opentrax@email.com Cc: msmith@FreeBSD.ORG, bright@wintelcom.net, duan@cs.umn.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: printf() In-reply-to: Your message of "Fri, 10 Nov 2000 05:31:18 PST." <200011101331.FAA01525@spammie.svbug.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Nov 2000 05:41:14 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 10 Nov, Mike Smith wrote: > >> > >> Is there is way that I could perhaps demonstrate my reasoning, > >> such that it might be satisfactory to you? > > > > No. > > > Then, should I take it you concede the point? No. -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 8: 6:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.outerlink.com (mail.outerlink.com [4.19.252.11]) by hub.freebsd.org (Postfix) with ESMTP id C026237B479 for ; Fri, 10 Nov 2000 08:06:52 -0800 (PST) Received: from geostar [4.19.252.5] by mail.outerlink.com (SMTPD32-6.05) id AC421CC0132; Fri, 10 Nov 2000 11:03:14 -0500 From: "Robert A. Wheeler" To: Cc: Subject: RE: [OT] serial protocol analyzer Date: Fri, 10 Nov 2000 11:14:47 -0500 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 IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3A0AF50D.16530.974B26@localhost> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a need for something like this - I modified a serial cable such that it had four connectors: DB9#1 goes to device A DB9#2 goes to device B DB9#3 and DB9#4 goes to a "monitoring" system on COM1 and COM2 #1 TX is connected to #2 RX AND #3 RX #1 RX is connected to #2 TX #2 TX is connected to #1 RX AND #4 RX #2 RX is connected to #1 TX #3 RX is tapped to #1 TX #3 TX is not connected #4 RX is tapped to #2 TX #4 TX is not connected Connect signal ground on each to each and monitor using a terminal emulator - Most terminal emulators have the ability to display rather than interpret control characters and escape sequences. You can see what is passing in both directions on the serial cable without affecting it, while not affecting the data stream. What you do not get is timestamp data. Or you can buy serial line monitors that do all this and more. Hope this helps. > -----Original Message----- > From: redhat-list-admin@redhat.com > [mailto:redhat-list-admin@redhat.com]On Behalf Of Leonard den Ottolander > Sent: Thursday, November 09, 2000 1:04 PM > To: redhat-list@redhat.com > Cc: freebsd-hackers@freebsd.org > Subject: [OT] serial protocol analyzer > > > Hello everybody, > > I was wondering if somebody could point me out a serial protocol > analyzer. > Maybe analyzer is too big a word for what I am looking for (I > could be the > analyzer:) ). What I am thinking of is a piece of software that > listens on > two serial devices, and mimics input from either to the other, in > the mean > time dumping and/or analyzing the traffic. To be concrete: I want > to put a box > with this piece of software between another box and its modem to > analyze the > traffic. > Thanks in advance, > > Ciao, > > Leonard. > > > > > > _______________________________________________ > Redhat-list mailing list > Redhat-list@redhat.com > https://listman.redhat.com/mailman/listinfo/redhat-list > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 8:41:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.cs.umn.edu (mail.cs.umn.edu [128.101.36.200]) by hub.freebsd.org (Postfix) with ESMTP id CC96E37B479; Fri, 10 Nov 2000 08:41:07 -0800 (PST) Received: from kepler.cs.umn.edu (duan@kepler.cs.umn.edu [128.101.34.78]) by mail.cs.umn.edu (8.9.3/8.9.3) with ESMTP id KAA20197; Fri, 10 Nov 2000 10:41:06 -0600 (CST) Received: from localhost (duan@localhost) by kepler.cs.umn.edu (8.9.1/8.9.0) with ESMTP id KAA08897; Fri, 10 Nov 2000 10:41:05 -0600 (CST) X-Authentication-Warning: kepler.cs.umn.edu: duan owned process doing -bs Date: Fri, 10 Nov 2000 10:41:05 -0600 (CST) From: Zhenhai Duan To: Mike Smith Cc: , , Subject: Re: printf() In-Reply-To: <200011101341.eAADfF906762@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for all of your replies. The reason I asked this question is that I really saw some incomplete print out on FreeBSD 3.3. My intuition is that the printout is buffered some where, otherwise, I would expect either there is a complete printout, or no printout at all. --Zhenhai On Fri, 10 Nov 2000, Mike Smith wrote: > > On 10 Nov, Mike Smith wrote: > > >> > > >> Is there is way that I could perhaps demonstrate my reasoning, > > >> such that it might be satisfactory to you? > > > > > > No. > > > > > Then, should I take it you concede the point? > > No. > > -- > ... 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] > V I C T O R Y N O T V E N G E A N C E > > > > > 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 Fri Nov 10 8:43:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id B8F4837B479 for ; Fri, 10 Nov 2000 08:43:26 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.11.1) id eAAGgNw15899; Fri, 10 Nov 2000 10:42:23 -0600 (CST) (envelope-from dan) Date: Fri, 10 Nov 2000 10:42:23 -0600 From: Dan Nelson To: Dag-Erling Smorgrav Cc: void , hackers@FreeBSD.ORG Subject: Re: "iowait" CPU state Message-ID: <20001110104223.B21494@dan.emsphone.com> References: <20001107054413.A1983@firedrake.org> <20001109175050.C21468@firedrake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from "Dag-Erling Smorgrav" on Fri Nov 10 09:49:34 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 10), Dag-Erling Smorgrav said: > void writes: > > Is there any reason top couldn't add these up and report a %iowait > > like Solaris'? > > Yes. It would conceal valuable information. Do the adding up in your > head. I can't see how it would conceal information, since it would simply change "90% idle" to "10% idle 80% iowait". -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 8:58: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id 0DBC537B479 for ; Fri, 10 Nov 2000 08:57:58 -0800 (PST) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Fri, 10 Nov 2000 16:57:40 +0000 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 13uHUJ-0005l1-00; Fri, 10 Nov 2000 16:57:15 +0000 Date: Fri, 10 Nov 2000 16:57:15 +0000 (GMT) From: Jan Grant To: Christoph Sold Cc: Jimmy Olgeni , hackers@FreeBSD.ORG Subject: Re: What about rc.shutdown.local? In-Reply-To: <3A0ABFB7.B269FAFD@i-clue.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Nov 2000, Christoph Sold wrote: > Better still would be /usr/local/etc/rc.d/*.sh called automatically > with parameter stop. To do so, insert This is all nice (BTDT) although I find the *.sh pattern quite annoying, due to the alphabetisation issue. When I make these mods I tend to use the SysV-style S* and K* patterns - that means you get to control the order of startup _and_ shutdown (which might need a different sequence). jan PS. Yeah, an all-singing, all-dancing subsystem mechanism would make all of this moot, but this method is cheap and simple, and already here. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287163 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk Bolstered by my success with vi, I proceeded to learn C with 'learn c'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 9:56:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tor3.targetnet.com (smtp.tor3.targetnet.com [207.176.132.71]) by hub.freebsd.org (Postfix) with ESMTP id B297537B479; Fri, 10 Nov 2000 09:56:45 -0800 (PST) Received: from james by smtp.tor3.targetnet.com with local (Exim 3.16 #1) id 13uIPl-000MX5-00; Fri, 10 Nov 2000 12:56:37 -0500 Date: Fri, 10 Nov 2000 12:56:37 -0500 From: James FitzGibbon To: Nick Hibma Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter Message-ID: <20001110125637.E78538@targetnet.com> References: <20001109150646.B39548@targetnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from n_hibma@qubesoft.com on Thu, Nov 09, 2000 at 08:20:42PM +0000 Organization: Targetnet.com Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Nick Hibma (n_hibma@qubesoft.com) [001109 17:31]: > Hm, I missed the zip story. You seem to have all the bits that are > necessary in your kernel. > > Could you compile your kernel/module with UMASS_DEBUG defined and send > me the output after an attach? As it turns out, I got it working, but only when the device is on SCSI ID 0. Any other SCSI id and the device is not found when I run 'camcontrol rescan 0' The output is rather large, so I put it on a web server: http://people.targetnet.com/~james/dmesg.plugin http://people.targetnet.com/~james/dmesg.rescan (plugin is the dmesg output when I plugged it into the USB port, and rescan is the additional output when I ran camcontrol rescan 0). Thanks. -- j. James FitzGibbon james@targetnet.com Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 10: 3:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 8071F37B479; Fri, 10 Nov 2000 10:03:38 -0800 (PST) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id LAA11629; Fri, 10 Nov 2000 11:00:10 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpdAAAVMayyw; Fri Nov 10 10:59:56 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id LAA22849; Fri, 10 Nov 2000 11:03:16 -0700 (MST) From: Terry Lambert Message-Id: <200011101803.LAA22849@usr08.primenet.com> Subject: Re: PCI interrupt routing across PCI:PCI bridges To: msmith@FreeBSD.ORG (Mike Smith) Date: Fri, 10 Nov 2000 18:03:16 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <200011090000.eA900F311423@mass.osd.bsdi.com> from "Mike Smith" at Nov 08, 2000 04:00:15 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Following is a patch to route interrupts for devices on the child side of > a PCI:PCI bridge. I don't have any easy way to test this, unfortunately. > > If anyone would care to eyeball it before I commit it, I'd greatly > appreciate that. FWIW, this matches my reading of my paper copy of the spec., but I can't test it either. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 10:28:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id 82B8737B479 for ; Fri, 10 Nov 2000 10:28:29 -0800 (PST) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id LAA13846; Fri, 10 Nov 2000 11:24:31 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpdAAAyTaOpA; Fri Nov 10 11:23:33 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id LAA23635; Fri, 10 Nov 2000 11:27:25 -0700 (MST) From: Terry Lambert Message-Id: <200011101827.LAA23635@usr08.primenet.com> Subject: Re: aio_read() broken functionality. To: accelware@accelware.com (Dmitry Sychov) Date: Fri, 10 Nov 2000 18:27:25 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <002001c04a91$10f0be20$1ec730d4@dima> from "Dmitry Sychov" at Nov 10, 2000 12:07:24 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to manual the aio_offset field of the "aiocb" structure > is ignored in the aio_read() call. So one can read the file only from > beginning. Very bad for me. :-( > > Will this bug be fixed in FreeBSD 5.0? The bug was fixed a long time ago, but the man page was never updated. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 10:31:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from henny.webweaving.org (unknown [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 4D08937B479; Fri, 10 Nov 2000 10:31:13 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id SAA43008; Fri, 10 Nov 2000 18:07:13 GMT (envelope-from n_hibma@qubesoft.com) Date: Fri, 10 Nov 2000 18:07:13 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: James FitzGibbon Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter In-Reply-To: <20001110125637.E78538@targetnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This makes sense as the adapter is not a ful controller, just a cheapo interface. You cannot select the SCSI id from the USB driver. Nick On Fri, 10 Nov 2000, James FitzGibbon wrote: > * Nick Hibma (n_hibma@qubesoft.com) [001109 17:31]: > > > Hm, I missed the zip story. You seem to have all the bits that are > > necessary in your kernel. > > > > Could you compile your kernel/module with UMASS_DEBUG defined and send > > me the output after an attach? > > As it turns out, I got it working, but only when the device is on SCSI ID 0. > Any other SCSI id and the device is not found when I run 'camcontrol rescan > 0' > > The output is rather large, so I put it on a web server: > > http://people.targetnet.com/~james/dmesg.plugin > http://people.targetnet.com/~james/dmesg.rescan > > (plugin is the dmesg output when I plugged it into the USB port, and rescan > is the additional output when I ran camcontrol rescan 0). > > Thanks. > > -- > j. > > James FitzGibbon james@targetnet.com > Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 10:31:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (s014.dhcp212-24.cybercable.fr [212.198.24.14]) by hub.freebsd.org (Postfix) with ESMTP id 8DBED37B4C5 for ; Fri, 10 Nov 2000 10:31:39 -0800 (PST) Received: from cybercable.fr (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id TAA42919; Fri, 10 Nov 2000 19:31:28 +0100 (CET) (envelope-from herbelot@cybercable.fr) Message-ID: <3A0C3EFF.FC473FD0@cybercable.fr> Date: Fri, 10 Nov 2000 19:31:27 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Koster, K.J." Cc: "'FreeBSD Hackers mailing list'" Subject: Re: Legacy ethernet cards in FreeBSD References: <59063B5B4D98D311BC0D0001FA7E4522026D79E3@l04.research.kpn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Koster, K.J." wrote: > > Dear All, > > Last night I cvsupped my trusty old Compaq Deskpro XL 6200 from 4.0-release > to 4.2-beta. As part of that process, I seem to have lost support for the > on-board NIC (lnc0: PCNet/PCI Ethernet Adapter, PC-net-32 VL-Bus). > > What is the newest version of FreeBSD that will propely support that card? > > If there are people who are cleaning up the support for older network cards > in FreeBSD I'd like to help out by sending you my old NICs. It's not like > they're any good to me without OS support. > > Please contact me off-list for any of the following cards: > > 3Com 3c503 ISA should be ok with the ed driver, for correct values of irq and io range > DEC Etherworks ISA > DEC DE205 ISA > SMC EtherEZ ISA ditto > RealTek "TP-Link" PCI > > As far as I've been able to determine, none of these work properly. In > particular, the RealTek card gets detected and pretends to work, but loses > the link after a bit (The link status LED goes out, and I need to reboot the > box.) > > I'll be happy to try out patches for the lnc driver to fix the problem of > the Deskpro, or to give remote access to it if you want to work on it. > > Kees Jan -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 10:59:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 4F09C37B4CF; Fri, 10 Nov 2000 10:59:22 -0800 (PST) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id MAA17538; Fri, 10 Nov 2000 12:59:16 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 10 Nov 2000 12:59:15 -0600 (CST) From: Chris Dillon To: Nick Hibma Cc: James FitzGibbon , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: USB-to-SCSI converter In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Nov 2000, Nick Hibma wrote: > This makes sense as the adapter is not a ful controller, just a > cheapo interface. > > You cannot select the SCSI id from the USB driver. Hmm.. Since I was looking for a "true" USB-SCSI controller, obviously this thing won't work. If it only works with devices set to ID 0, it will never work with a SCSI ZIP drive which only has settings for ID 5 or 6 (which is one thing I would use it with). Do the Shuttle-based USB-SCSI adapters have the same limitation? -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64 and PowerPC under development. 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 Fri Nov 10 11:15:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id E60ED37B4C5 for ; Fri, 10 Nov 2000 11:15:31 -0800 (PST) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id MAA03409; Fri, 10 Nov 2000 12:15:47 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp05.primenet.com, id smtpdAAAEna4H6; Fri Nov 10 11:58:22 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id LAA24569; Fri, 10 Nov 2000 11:57:44 -0700 (MST) From: Terry Lambert Message-Id: <200011101857.LAA24569@usr08.primenet.com> Subject: Re: printf() To: duan@cs.umn.edu (Zhenhai Duan) Date: Fri, 10 Nov 2000 18:57:36 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Zhenhai Duan" at Nov 09, 2000 11:08:46 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A simple question: > > Does the kernel function printf() flushes the output immediately, or it is > possible some data is buffered somewhere and gets lost without printing > to the console? like the corresponding funtion in the c library. There is no buffering comparable to that of the stdio package; in other words, there is no such thing as an fflush() or setbuf() call. There has been some discussion of bufering of console output, with the buffer list to be used as a synchronization point, so that SMP systems, kernel threads, and interrupt handlers can't stomp on each other when one is in the middle of console I/O; should that work be done and incorporated, the console I/O will definitely be buffered, in the stdio sense, and a "spin until queue drains, yielding to the console output routine" may find its way in, as an aid to debugging kernel problems, which could otherwise be hidden by the queueing: a kernel fflush(). As things currently sit, it's possible to take an interrupt in the middle of output, and truncate it, if the interrupt handler has a bug that forces it into a tight loop, or otherwise locks up the machine. Similarly, output in an interrupt handler might (rarely) stomp in the middle of output in progress from elsewhere; console output at interrupt level is discouraged. Depending on the console output you are talking about, if it's coming from user space, all bets are off: user space console I/O may be buffered by whatever program doing the output, and some programs which output to the console have very long latencies, which you might also see (e.g. syslogd). Console messages that are sent from the kernel are usually sent to the diagnostic log. This is the log reported by dmesg, and is implemented using a buffer in memory, which is expected to survive over a boot. Some BIOS RAM test methods used to prevent this; I am unsure of how this is stored over reboots in the current code, and whether it is reliable or not on particular hardware. This is the information that is reported by the "dmesg" command. Finally, if you are talking about the console log, those outputs are inddeed buffered, through syslog. In addition, the commits of this data to the log file are not entirely synchronous. This means that you can not really depend on the console log contents to be 100% accurate at any given instance. So if what you are trying to do is diagnose a system crash from the console log in /var/messages (for example), then you will be out of luck. If dmesg data survives reboots for you, then you will be much happier using that instead of the console log (default: /var/log/messages). I hope this was useful; there really is very little documentation that is accurate about this type of area of FreeBSD internals, so it was probably OK for you to post your question here rather than questions, even though you are probably asking about what you suspect is your problem, instead of asking your real question. Hope this helps, and hope anyone who has any corrections to this wil provide them, since this type of documentation needs to be collected somewhere, and the mailing list archives seem to be the most appropriate place. Maybe we can set up an arch-doc list, which we can cross-post these responses to via Bcc:, without incurring the wrath of the mailing list manager? An archive of such things (my contributions in this area are minor, trust me) would be a good thing; PHK posted a nice internals description the other day that I would not mind having archived for eternity, without it taking up space in my email archive. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 11:26:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id 40A3F37B4C5 for ; Fri, 10 Nov 2000 11:26:54 -0800 (PST) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id MAA04194; Fri, 10 Nov 2000 12:22:56 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpdAAA2waOTh; Fri Nov 10 12:22:14 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id MAA25495; Fri, 10 Nov 2000 12:26:06 -0700 (MST) From: Terry Lambert Message-Id: <200011101926.MAA25495@usr08.primenet.com> Subject: Re: What about rc.shutdown.local? To: root@virtual-voodoo.com (Charlie &) Date: Fri, 10 Nov 2000 19:26:05 +0000 (GMT) Cc: so@server.i-clue.de (Christoph Sold), olgeni@uli.it (Jimmy Olgeni), hackers@FreeBSD.ORG In-Reply-To: <20001109102337.A64659@virtual-voodoo.com> from "Charlie &" at Nov 09, 2000 10:23:37 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > It would be nice to have a /etc/rc.shutdown.local called by > > > /etc/rc.shutdown, > > > to implement custom shutdown procedures. This is currently done by > > > editing rc.shutdown, but you have to remember about it when you run > > > mergemaster. > > > > Better still would be /usr/local/etc/rc.d/*.sh called automatically > > with parameter stop. To do so, insert > > This already happens... at least in rc.shutdown v1.15: > > # $FreeBSD: src/etc/rc.shutdown,v 1.15 2000/10/20 20:26:05 ache Exp $ I was looking for a similar thing yesterday, and had to roll my own. The problem with the /usr/local crap is that it assumes that anything I'm going to install will be put into the /usr/local. The basic problem with this assumption (and of the runtime linker not seeing shared libraries in directories that are not in ldconfig, but were used in the build process to link successfully, and have their paths therefore stored in the binary) is that it assumes that I will never have a conflict with the system. Unfortunately, the ports system likes to use /usr/local to dump ports in, so this makes for a certain amount of developement confusion. When I want to develop a program on a FreeBSD system to deploy on a FreeBSD system, I will install all sorts of ports on my developement machine, but I will install nothing but the code I wish to deploy on my deployment machine. This means that the deployment code may infact use some of the same libraries and other binaries and data and so on that result from the ports system installing packages and ports, BUT it can NOT depend on these libraries being present in the deployment environment. This means that my deployment code my target a different directory hierarchy. The "ldconfig" issue aside (it's a can of worms, including that I could end up linking system components against my developement components because of ldconfig, even though I will later move or delete the build product), this is a real problem. For the startup stuff, at least you can wedge it with a /etc/rc.local; I know that it's "preferred" that I put my code and the ports code into the same namespace, but it is not "preferred" by me, nor is it really practical to do an extreme audit of every bit of code to make sure that I'm not getting a header file or something "accidently" by way of /usr/local. Worse, what if my deployment system is not FreeBSD? I know, I can hear the cries of "Heresy!" from here. I need to ensure that I can build out my source tree without dependency on the host system at all, at least as far as things in addition to POSIX interfaces and the libraries that implement them, let alone crap that some port happens to import "behind my back" to satisfy some third or fourth order dependency. So for FreeBSD, it would be useful to have an rc.shutdown.local which corresponds to rc.local, and the "preference" of the style police be damned. It seems to me that FreeBSD is setting itself up to be a system on which all working software needs to be integrated into the ports system, and this won't work at all for commercial or role modularized code. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 11:49:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1C91937B4C5 for ; Fri, 10 Nov 2000 11:49:49 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAAJnlg26639; Fri, 10 Nov 2000 12:49:48 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA50988; Fri, 10 Nov 2000 12:49:47 -0700 (MST) Message-Id: <200011101949.MAA50988@harmony.village.org> To: Zhenhai Duan Subject: Re: printf() Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 09 Nov 2000 23:08:46 CST." References: Date: Fri, 10 Nov 2000 12:49:47 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Zhenhai Duan writes: : Does the kernel function printf() flushes the output immediately, or it is : possible some data is buffered somewhere and gets lost without printing : to the console? like the corresponding funtion in the c library. Yes. It can be buffered, but that's a driver level thing. I've seen serial consoles where things crashed after a printf I put in and never saw. I've not seen anything similar on video consoles. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 11:53:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 67F2037B4C5 for ; Fri, 10 Nov 2000 11:53:21 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAAJrKg26663; Fri, 10 Nov 2000 12:53:20 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA51160; Fri, 10 Nov 2000 12:53:19 -0700 (MST) Message-Id: <200011101953.MAA51160@harmony.village.org> To: "Koster, K.J." Subject: Re: Legacy ethernet cards in FreeBSD Cc: "'FreeBSD Hackers mailing list'" In-reply-to: Your message of "Fri, 10 Nov 2000 14:27:31 +0100." <59063B5B4D98D311BC0D0001FA7E4522026D79E3@l04.research.kpn.com> References: <59063B5B4D98D311BC0D0001FA7E4522026D79E3@l04.research.kpn.com> Date: Fri, 10 Nov 2000 12:53:19 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <59063B5B4D98D311BC0D0001FA7E4522026D79E3@l04.research.kpn.com> "Koster, K.J." writes: : 3Com 3c503 ISA I think so. The ed driver supports this : DEC Etherworks ISA : DEC DE205 ISA don't know about these. lnc driver supports them maybe ? : SMC EtherEZ ISA ed driver. : RealTek "TP-Link" PCI Don't know about this one. : As far as I've been able to determine, none of these work properly. In : particular, the RealTek card gets detected and pretends to work, but loses : the link after a bit (The link status LED goes out, and I need to reboot the : box.) Read Bill Paul's glowing reviews of the realtek hardware in the rl driver :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 12:19:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id CF0D537B479; Fri, 10 Nov 2000 12:19:40 -0800 (PST) Subject: Re: Legacy ethernet cards in FreeBSD In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D79E3@l04.research.kpn.com> from "Koster, K.J." at "Nov 10, 2000 02:27:31 pm" To: K.J.Koster@kpn.com (Koster K.J.) Date: Fri, 10 Nov 2000 12:19:40 -0800 (PST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20001110201940.CF0D537B479@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Charset iso-8859-1 unsupported, filtering to ASCII...] > Dear All, > > Last night I cvsupped my trusty old Compaq Deskpro XL 6200 from 4.0-release > to 4.2-beta. As part of that process, I seem to have lost support for the > on-board NIC (lnc0: PCNet/PCI Ethernet Adapter, PC-net-32 VL-Bus). Ok, "seem to have lost support" is about the vaguest thing you could have said. I've killed people for less. Please explain in detail how you arrived at the conclusion that the card was no longer supported. Show us the dmesg output from your machine. Explain what you tried to do and what results you observed. Don't just say "it doesn't work." You've not going to help anyone that way. FreeBSD 4.2 has a new driver for AMD PCnet/PCI devices, in particular the 10/100 cards, because the lnc driver runs these cards in 16-bit LANCE compatibility mode which really impairs their performance. Did you check to see if a pcn0 device was detected? Did you attempt to use it? If not, why not? If so, what happened? > What is the newest version of FreeBSD that will propely support that card? You're soaking in it. > If there are people who are cleaning up the support for older network cards > in FreeBSD I'd like to help out by sending you my old NICs. It's not like > they're any good to me without OS support. > > Please contact me off-list for any of the following cards: > > 3Com 3c503 ISA Should work with the ed driver, *provided* you get its I/O address set correctly so that the ed driver will detect it. I haven't used one of these since FreeBSD 2.x though. > DEC Etherworks ISA > DEC DE205 ISA Don't know about these. > SMC EtherEZ ISA Should also work with the ed driver, though you may have to turn off plug and play mode using the SMC EZSetup utility. > RealTek "TP-Link" PCI If this is a 10mbps card, it should be an NE2000 clone, and will work with the ed driver. If it's a 100Mbps card, it should work with the rl driver. > I'll be happy to try out patches for the lnc driver to fix the problem of > the Deskpro, or to give remote access to it if you want to work on it. I'd be happier if you told me whether the pcn driver works or not. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 12:23: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 297C337B479 for ; Fri, 10 Nov 2000 12:22:57 -0800 (PST) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id NAA00159; Fri, 10 Nov 2000 13:22:34 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id NAA28017; Fri, 10 Nov 2000 13:22:32 -0700 (MST) (envelope-from nate) Date: Fri, 10 Nov 2000 13:22:32 -0700 (MST) Message-Id: <200011102022.NAA28017@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: "Koster, K.J." , "'FreeBSD Hackers mailing list'" Subject: Re: Legacy ethernet cards in FreeBSD In-Reply-To: <200011101953.MAA51160@harmony.village.org> References: <59063B5B4D98D311BC0D0001FA7E4522026D79E3@l04.research.kpn.com> <200011101953.MAA51160@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : 3Com 3c503 ISA > > I think so. The ed driver supports this I'm pretty sure the ed driver doesn't support the 503. I think we dropped support for the 503 a *REALLY* long time ago (2.1 days...) > : DEC Etherworks ISA > : DEC DE205 ISA > > don't know about these. lnc driver supports them maybe ? Use to be the le driver supported them, but apparently it's broken now. 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 10 12:36:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77]) by hub.freebsd.org (Postfix) with ESMTP id E58AE37B479 for ; Fri, 10 Nov 2000 12:36:17 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAAKfc908044; Fri, 10 Nov 2000 12:41:41 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011102041.eAAKfc908044@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nate@yogotech.com (Nate Williams) Cc: Warner Losh , "Koster, K.J." , "'FreeBSD Hackers mailing list'" Subject: Re: Legacy ethernet cards in FreeBSD In-reply-to: Your message of "Fri, 10 Nov 2000 13:22:32 MST." <200011102022.NAA28017@nomad.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Nov 2000 12:41:38 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : 3Com 3c503 ISA > > > > I think so. The ed driver supports this > > I'm pretty sure the ed driver doesn't support the 503. I think we > dropped support for the 503 a *REALLY* long time ago (2.1 days...) You are probably confusing it with the 501 or 505. The 503 is basically an NE1000 (with a better probe routine). -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 12:38: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 6776D37B479; Fri, 10 Nov 2000 12:38:01 -0800 (PST) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id NAA00428; Fri, 10 Nov 2000 13:37:55 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id NAA28108; Fri, 10 Nov 2000 13:37:54 -0700 (MST) (envelope-from nate) Date: Fri, 10 Nov 2000 13:37:54 -0700 (MST) Message-Id: <200011102037.NAA28108@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: nate@yogotech.com (Nate Williams), Warner Losh , "Koster, K.J." , "'FreeBSD Hackers mailing list'" Subject: Re: Legacy ethernet cards in FreeBSD In-Reply-To: <200011102041.eAAKfc908044@mass.osd.bsdi.com> References: <200011102022.NAA28017@nomad.yogotech.com> <200011102041.eAAKfc908044@mass.osd.bsdi.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > : 3Com 3c503 ISA > > > > > > I think so. The ed driver supports this > > > > I'm pretty sure the ed driver doesn't support the 503. I think we > > dropped support for the 503 a *REALLY* long time ago (2.1 days...) > > You are probably confusing it with the 501 or 505. The 503 is basically > an NE1000 (with a better probe routine). You're indeed correct. It was the 501 that we dropped support for, sorry for the false information. 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 10 12:50:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 0418D37B479 for ; Fri, 10 Nov 2000 12:50:17 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id PAA33722; Fri, 10 Nov 2000 15:50:07 -0500 (EST) Date: Fri, 10 Nov 2000 15:50:06 -0500 (EST) From: "Matthew N. Dodd" To: Nate Williams Cc: Warner Losh , "Koster, K.J." , "'FreeBSD Hackers mailing list'" Subject: Re: Legacy ethernet cards in FreeBSD In-Reply-To: <200011102022.NAA28017@nomad.yogotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Nov 2000, Nate Williams wrote: > > : 3Com 3c503 ISA > > > > I think so. The ed driver supports this > > I'm pretty sure the ed driver doesn't support the 503. I think we > dropped support for the 503 a *REALLY* long time ago (2.1 days...) How difficult is it to check the source? The 3c503 is supported. You're thinking of the 3c501 and the 3c505. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 13:55:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from news.IAEhv.nl (news.IAE.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id 33DFA37B479 for ; Fri, 10 Nov 2000 13:55:50 -0800 (PST) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id WAA19119; Fri, 10 Nov 2000 22:55:40 +0100 (MET) Received: by adv.devet.org (Postfix, from userid 100) id E628F411B; Fri, 10 Nov 2000 22:55:29 +0100 (CET) To: float@firedrake.org Subject: Re: "iowait" CPU state X-Newsgroups: list.freebsd.hackers In-Reply-To: <20001110050823.A10063@firedrake.org> References: <20001109174946.B21468@firedrake.org> Organization: Eindhoven, the Netherlands Cc: hackers@freebsd.org Message-Id: <20001110215529.E628F411B@adv.devet.org> Date: Fri, 10 Nov 2000 22:55:29 +0100 (CET) From: Arjan.deVet@adv.iae.nl (Arjan de Vet) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20001110050823.A10063@firedrake.org> you write: >> > not how busy the disks are. I want relative data, not absolute. >> >> systat -vmstat? > >Thank you! This gets the me disk %busy, which is one of the things I >was looking for. Now, can anyone tell me how to tell what percentage of That was something I was looking for some time ago as well, so I wrote and submitted the patch for %busy :-). It's not 100% accurate, see the systat source for the details. This patch will add an extra row 'queue' displaying the amount of commands queued for the disk: Index: vmstat.c =================================================================== RCS file: /home/freebsd/CVS/src/usr.bin/systat/vmstat.c,v retrieving revision 1.38.2.2 diff -u -r1.38.2.2 vmstat.c --- vmstat.c 2000/07/02 10:03:17 1.38.2.2 +++ vmstat.c 2000/07/06 22:07:57 @@ -335,6 +335,7 @@ mvprintw(DISKROW + 2, DISKCOL, "tps"); mvprintw(DISKROW + 3, DISKCOL, "MB/s"); mvprintw(DISKROW + 4, DISKCOL, "%% busy"); + mvprintw(DISKROW + 5, DISKCOL, "queue"); /* * For now, we don't support a fourth disk statistic. So there's * no point in providing a label for it. If someone can think of a @@ -841,4 +842,5 @@ putlongdouble(transfers_per_second, DISKROW + 2, c, 5, 0, 0); putlongdouble(mb_per_second, DISKROW + 3, c, 5, 2, 0); putlongdouble(device_busy * 100 / elapsed_time, DISKROW + 4, c, 5, 0, 0); + putlongdouble(now->dinfo->devices[di].busy_count, DISKROW + 5, c, 5, 0, 0); } >processor time is being spent waiting for disk I/O to complete? Hmm, I thought the CPU never spends time waiting for disk I/O, it just schedules another process? How should iowait% be calculated then? Is the percentage of time the CPU was idle and one or more processes were blocked on disk I/O? Arjan -- Arjan de Vet, Eindhoven, The Netherlands URL: http://www.iae.nl/users/devet/ for PGP key: finger devet@iae.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 14:13:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id 5FB4237B4C5 for ; Fri, 10 Nov 2000 14:13:41 -0800 (PST) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id PAA07207; Fri, 10 Nov 2000 15:12:42 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpdAAAmHaORp; Fri Nov 10 11:24:22 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id LAA23555; Fri, 10 Nov 2000 11:25:08 -0700 (MST) From: Terry Lambert Message-Id: <200011101825.LAA23555@usr08.primenet.com> Subject: Re: Repeatable STL core with -pthread To: jar@integratus.com (Jack Rusher) Date: Fri, 10 Nov 2000 18:25:08 +0000 (GMT) Cc: james@targetnet.com (James FitzGibbon), hackers@FreeBSD.ORG In-Reply-To: <3A0B2E87.3B49887B@integratus.com> from "Jack Rusher" at Nov 09, 2000 03:08:55 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The program will core after about 10 seconds, every time. > > It would appear that there is an issue with some low-level allocator in the > > STL as shipped in 4.x. > > Dude. The STL implementation that ships with g++ isn't thread safe. > In fact, if you read the STL portion of the C++ specification, you will > notice that threads are not mentioned at all. The only guarantees made > by the STL are that operations will complete within certain performance > guidelines. > > As a safety tip, the string implementation in the g++ implementation > isn't thread safe either. It uses a shared buffer scheme ("char* > string->rep") to reduce memory consumption & improve performance. This > is in opposition to "deep copy" style libraries, like the SGI STL, that > work in threaded environments. > > Because of the way the C++ standard is written, commercial STL > implementations, such as the Rogue Wave library that comes with the Sun > C++ compiler, suffer from the same threading problems. Use the STL that is used by the Cyrus ACAP server, which is the one from the Moscow Center for Supercomputing Activities. There is an issue in GNU C++ with an assumption by the ACAP code about dynamic virtual base class construction order at load time, but it can be handled by ensureing that the link order ensures that classes are linked lowest level to highest level, in reverse dependency order. The Moscow STL also has a large number of bug fixes; Jeremy Allison (of Samba) and myself spent a fair amount of time adding in support for Draft 4 pthreads, and making it work on FreeBSD at the time (which included patches to FreeBSD of the time to bring it into compliance with Draft 4). Without these, you will probably have a hard time making the STL code work on both modern FreeBSD, and on, say, IRIX, which is still Draft 4. But if this is not a portability issue for you, I would suggest using that STL instead. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 14:15:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id C993937B479 for ; Fri, 10 Nov 2000 14:15:45 -0800 (PST) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id PAA08122; Fri, 10 Nov 2000 15:14:45 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpdAAA1iaq0q; Fri Nov 10 11:25:43 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id LAA23595; Fri, 10 Nov 2000 11:26:31 -0700 (MST) From: Terry Lambert Message-Id: <200011101826.LAA23595@usr08.primenet.com> Subject: Re: aio_read() broken functionality. To: bright@wintelcom.net (Alfred Perlstein) Date: Fri, 10 Nov 2000 18:26:31 +0000 (GMT) Cc: accelware@accelware.com (Dmitry Sychov), freebsd-hackers@FreeBSD.ORG In-Reply-To: <20001109132339.B5112@fw.wintelcom.net> from "Alfred Perlstein" at Nov 09, 2000 01:23:39 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > * Dmitry Sychov [001109 13:06] wrote: > > Greetings. > > > > According to manual the aio_offset field of the "aiocb" structure > > is ignored in the aio_read() call. So one can read the file only from > > beginning. Very bad for me. :-( > > > > Will this bug be fixed in FreeBSD 5.0? > > Hrm, parsing through the kernel code it looks like this is just a > bug in the manpage, basically aio_offset doesn't look like it's > ignored, can you try to use aio_offset and report if it works or > not. > > Please submit some test code if it doesn't. > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." > > > 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 Fri Nov 10 14:28:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id D9CA737B479 for ; Fri, 10 Nov 2000 14:28:45 -0800 (PST) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id PAA13181; Fri, 10 Nov 2000 15:27:43 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpdAAA8caO0w; Fri Nov 10 11:32:16 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id LAA23780; Fri, 10 Nov 2000 11:33:03 -0700 (MST) From: Terry Lambert Message-Id: <200011101833.LAA23780@usr08.primenet.com> Subject: Re: "iowait" CPU state To: float@firedrake.org (void) Date: Fri, 10 Nov 2000 18:33:03 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <20001110050823.A10063@firedrake.org> from "void" at Nov 10, 2000 05:08:23 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thank you! This gets the me disk %busy, which is one of the things I > was looking for. Now, can anyone tell me how to tell what percentage of > processor time is being spent waiting for disk I/O to complete? Uh, none? If there is disk I/O pending, the processor just runs a different process... am I missing your question? Are you maybe asking what percentage of time a given process spends waiting on disk I/O, thather than doing processing? A rough approximation of this would be (system time/(user time + system time))*100. Using the wall time would not take other processes use of the CPU into account, but you might consider using that anyway, depending on why you want the statistic. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 10 16:35: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id 09DE937B479 for ; Fri, 10 Nov 2000 16:34:57 -0800 (PST) Received: (qmail 25000 invoked by uid 1001); 11 Nov 2000 10:34:48 +1000 X-Posted-By: GBA-Post 2.06 15-Sep-2000 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Sat, 11 Nov 2000 10:34:47 +1000 From: Greg Black To: Jan Grant Cc: Christoph Sold , Jimmy Olgeni , hackers@FreeBSD.ORG Subject: Re: What about rc.shutdown.local? References: In-reply-to: of Fri, 10 Nov 2000 16:57:15 GMT Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jan Grant writes: > > Better still would be /usr/local/etc/rc.d/*.sh called automatically > > with parameter stop. To do so, insert > > This is all nice (BTDT) although I find the *.sh pattern quite annoying, > due to the alphabetisation issue. When I make these mods I tend to use > the SysV-style S* and K* patterns - that means you get to control the > order of startup _and_ shutdown (which might need a different sequence). This seems trivial. I name the scripts with two-digit prefixes and an underscore so that I can have meaningful names and an easy way to control the sequence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 0:43:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wpk-smtp-relay.cwci.net (wpk-smtp-relay2.cwci.net [195.44.63.19]) by hub.freebsd.org (Postfix) with ESMTP id 6758737B479 for ; Sat, 11 Nov 2000 00:43:09 -0800 (PST) Received: from o7i1i1 ([195.44.147.200]) by wpk-smtp-relay.cwci.net with Microsoft SMTPSVC(5.5.1877.387.38); Sat, 11 Nov 2000 08:42:47 +0000 Message-ID: <000801c04bbb$96f0b9a0$c8932cc3@o7i1i1> From: "Katya.Hazelden" To: Subject: CD ROM Date: Sat, 11 Nov 2000 08:44:19 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C04BBB.952B8A00" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C04BBB.952B8A00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I've got a problem with my CD ROM. The drawer keeps sliding open every = time I try to put a CD into it, it just won't stay shut. Have you got = any ideas? ------=_NextPart_000_0005_01C04BBB.952B8A00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I've got a problem with my CD ROM. The = drawer keeps=20 sliding open every time I try to put a CD into it, it just won't stay = shut. Have=20 you got any ideas?
------=_NextPart_000_0005_01C04BBB.952B8A00-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 1: 2:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B32F837B479 for ; Sat, 11 Nov 2000 01:02:32 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA42449; Sat, 11 Nov 2000 10:03:28 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200011110903.KAA42449@freebsd.dk> Subject: Re: CD ROM In-Reply-To: <000801c04bbb$96f0b9a0$c8932cc3@o7i1i1> from "Katya.Hazelden" at "Nov 11, 2000 08:44:19 am" To: Katya.Hazelden@ic24.net (Katya.Hazelden) Date: Sat, 11 Nov 2000 10:03:27 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Katya.Hazelden wrote: > I've got a problem with my CD ROM. The drawer keeps sliding open every time I try to put a CD into it, it just won't stay shut. Have you got any ideas? Your drive is broken, or something is obstructing the drawer... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 1:19:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 7481737B479 for ; Sat, 11 Nov 2000 01:19:10 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eAB9J2I28473; Sat, 11 Nov 2000 01:19:02 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: "Katya.Hazelden" Cc: hackers@FreeBSD.ORG Subject: Re: CD ROM In-Reply-To: Message from "Katya.Hazelden" of "Sat, 11 Nov 2000 08:44:19 GMT." <000801c04bbb$96f0b9a0$c8932cc3@o7i1i1> Date: Sat, 11 Nov 2000 01:19:02 -0800 Message-ID: <28470.973934342@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've got a problem with my CD ROM. The drawer keeps sliding open every = > time I try to put a CD into it, it just won't stay shut. Have you got = > any ideas? Duct tape? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 2:36:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.attica.net.nz (mail.attica.net.nz [202.180.64.33]) by hub.freebsd.org (Postfix) with SMTP id 900FD37B479 for ; Sat, 11 Nov 2000 02:36:29 -0800 (PST) Received: (qmail 20750 invoked from network); 11 Nov 2000 10:36:26 -0000 Received: from 202-180-75-118.iff0.attica.net.nz (HELO davep200.afterswish.com) (202.180.75.118) by mail.attica.net.nz with SMTP; 11 Nov 2000 10:36:26 -0000 Message-Id: <5.0.0.25.1.20001111232849.00a5e8e0@mail.afterswish.com> X-Sender: davep@mail.afterswish.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 11 Nov 2000 23:32:06 +1300 To: "Katya.Hazelden" From: David Preece Subject: Re: CD ROM Cc: freebsd-hackers@freebsd.org In-Reply-To: <000801c04bbb$96f0b9a0$c8932cc3@o7i1i1> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:44 11/11/00 +0000, you wrote: >I've got a problem with my CD ROM. The drawer keeps sliding open every >time I try to put a CD into it, it just won't stay shut. Have you got any >ideas? I have one CD ROM that used to do the same thing some of the time. Then more often. Now, nearly 100% of the time. Under Windows it merely fails to mount the disk. The drive now has "F**KED" written across it in indelible felt tip, I have yet to work out why I've not thrown it away. Borrow another drive. Dave :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 2:39:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id DAB8F37B479 for ; Sat, 11 Nov 2000 02:39:33 -0800 (PST) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Sat, 11 Nov 2000 10:35:59 +0000 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 13uY0j-0000WR-00; Sat, 11 Nov 2000 10:35:49 +0000 Date: Sat, 11 Nov 2000 10:35:49 +0000 (GMT) From: Jan Grant To: Greg Black Cc: Jan Grant , Christoph Sold , Jimmy Olgeni , hackers@FreeBSD.ORG Subject: Re: What about rc.shutdown.local? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 11 Nov 2000, Greg Black wrote: > Jan Grant writes: > > > > Better still would be /usr/local/etc/rc.d/*.sh called automatically > > > with parameter stop. To do so, insert > > > > This is all nice (BTDT) although I find the *.sh pattern quite annoying, > > due to the alphabetisation issue. When I make these mods I tend to use > > the SysV-style S* and K* patterns - that means you get to control the > > order of startup _and_ shutdown (which might need a different sequence). > > This seems trivial. I name the scripts with two-digit prefixes > and an underscore so that I can have meaningful names and an > easy way to control the sequence. It _is_ trivial, but you miss my point: I run several things at startup that rely on a database service (which needs to be launched first). When they shut down, the DB must still be running (it's taken down last). So using a *.sh pattern for startup and shutdown scripts doesn't satisfy my requirements. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287163 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk The Java disclaimer: values of 'anywhere' may vary between regions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 2:49:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id 1F67C37B479 for ; Sat, 11 Nov 2000 02:49:40 -0800 (PST) Received: (qmail 28590 invoked by uid 1001); 11 Nov 2000 20:49:36 +1000 X-Posted-By: GBA-Post 2.06 15-Sep-2000 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Sat, 11 Nov 2000 20:49:36 +1000 From: Greg Black To: Jan Grant Cc: Christoph Sold , Jimmy Olgeni , hackers@FreeBSD.ORG Subject: Re: What about rc.shutdown.local? References: In-reply-to: of Sat, 11 Nov 2000 10:35:49 GMT Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jan Grant writes: > It _is_ trivial, but you miss my point: I run several things at startup > that rely on a database service (which needs to be launched first). When > they shut down, the DB must still be running (it's taken down last). So > using a *.sh pattern for startup and shutdown scripts doesn't satisfy my > requirements. It's easy to miss a pont that isn't well made. Never mind. The task is still trivial. Three obvious solutions spring to mind: 1. Put a sleep in the stop case that gives enough time for the other scripts to run. 2. Make the last script that has to run /before/ this one create a sentinel file when it finishes; let this script wait until the sentinel appears, then it removes the sentinel and does its stuff. 3. Give this script two links. On startup, it runs if it's running under the startup name; on shutdown, it runs if it's running under the other name. If none of these does the trick, they should at least point the way. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 7:25:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spammie.svbug.com (mg136-070.ricochet.net [204.179.136.70]) by hub.freebsd.org (Postfix) with ESMTP id 1BA8E37B479 for ; Sat, 11 Nov 2000 07:25:46 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id HAA02970; Sat, 11 Nov 2000 07:26:15 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200011111526.HAA02970@spammie.svbug.com> Date: Sat, 11 Nov 2000 07:26:14 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: printf() To: tlambert@primenet.com Cc: duan@cs.umn.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <200011101857.LAA24569@usr08.primenet.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10 Nov, Terry Lambert wrote: >> A simple question: >> >> Does the kernel function printf() flushes the output immediately, or it is >> possible some data is buffered somewhere and gets lost without printing >> to the console? like the corresponding funtion in the c library. > > There is no buffering comparable to that of the stdio package; > in other words, there is no such thing as an fflush() or setbuf() > call. > >>...[Trimmed]... > > Hope this helps, and hope anyone who has any corrections to this > wil provide them, since this type of documentation needs to be > collected somewhere, and the mailing list archives seem to be the > most appropriate place. > Yes, Thanks Terry. Your explaination is much clearer than mine and it certainly covers the material in a much more concise manner than I know I could in a single writing. > Maybe we can set up an arch-doc list, which we can cross-post > these responses to via Bcc:, without incurring the wrath of the > mailing list manager? An archive of such things (my contributions > in this area are minor, trust me) would be a good thing; PHK > posted a nice internals description the other day that I would > not mind having archived for eternity, without it taking up space > in my email archive. > I agree. Additionally, such a idea could be extended with some simple scripts, if the write wrote a few key phrases at the head of such a message. For instance in this case: Scope: kernel internals Lifetime: Eternal Overrides: None However, that might just be wishful thinking on my part. :-) Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 7:30:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spammie.svbug.com (mg136-070.ricochet.net [204.179.136.70]) by hub.freebsd.org (Postfix) with ESMTP id 2DCE837B479 for ; Sat, 11 Nov 2000 07:30:24 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id HAA02982; Sat, 11 Nov 2000 07:30:54 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200011111530.HAA02982@spammie.svbug.com> Date: Sat, 11 Nov 2000 07:30:53 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: printf() To: imp@village.org Cc: duan@cs.umn.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <200011101949.MAA50988@harmony.village.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10 Nov, Warner Losh wrote: > In message Zhenhai Duan writes: > : Does the kernel function printf() flushes the output immediately, or it is > : possible some data is buffered somewhere and gets lost without printing > : to the console? like the corresponding funtion in the c library. > > Yes. It can be buffered, but that's a driver level thing. I've seen > serial consoles where things crashed after a printf I put in and never > saw. > > I've not seen anything similar on video consoles. > I want to be clear on what you're saying Warner. Are you saying that you put a printf() after your crash point, but never saw your printf(). So in your code it might have looked like: printf("foo do foo\n"); crash_here(); printf("after the crash\n"); And never see the statement "foo do foo\n"; Is that correct? Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 8:35:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id D9B4E37B479 for ; Sat, 11 Nov 2000 08:35:50 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13udXm-0000IU-00; Sat, 11 Nov 2000 09:30:18 -0700 Message-ID: <3A0D741A.5D50F8CF@softweyr.com> Date: Sat, 11 Nov 2000 09:30:18 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Jan Grant Cc: Greg Black , Christoph Sold , Jimmy Olgeni , hackers@FreeBSD.ORG Subject: Re: What about rc.shutdown.local? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jan Grant wrote: > > On Sat, 11 Nov 2000, Greg Black wrote: > > > Jan Grant writes: > > > > > > Better still would be /usr/local/etc/rc.d/*.sh called automatically > > > > with parameter stop. To do so, insert > > > > > > This is all nice (BTDT) although I find the *.sh pattern quite annoying, > > > due to the alphabetisation issue. When I make these mods I tend to use > > > the SysV-style S* and K* patterns - that means you get to control the > > > order of startup _and_ shutdown (which might need a different sequence). > > > > This seems trivial. I name the scripts with two-digit prefixes > > and an underscore so that I can have meaningful names and an > > easy way to control the sequence. > > It _is_ trivial, but you miss my point: I run several things at startup > that rely on a database service (which needs to be launched first). When > they shut down, the DB must still be running (it's taken down last). So > using a *.sh pattern for startup and shutdown scripts doesn't satisfy my > requirements. make? tsort? This was discussed ad nauseum in the last round of discussions about replacing /etc/rc*, search the archives if you're interested. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 9:39:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id CDA8C37B479 for ; Sat, 11 Nov 2000 09:39:07 -0800 (PST) Received: (qmail 31320 invoked by uid 0); 11 Nov 2000 17:39:05 -0000 Received: from p3e9bc17d.dip.t-dialin.net (HELO forge.local) (62.155.193.125) by mail.gmx.net (mail09) with SMTP; 11 Nov 2000 17:39:05 -0000 Received: from thomas by forge.local with local (Exim 3.12 #1 (Debian)) id 13uecD-0002YH-00 for ; Sat, 11 Nov 2000 18:38:57 +0100 Date: Sat, 11 Nov 2000 18:38:57 +0100 To: freebsd-hackers@freebsd.org Subject: [PATCH] per-packet UDP source address selection for sendmsg Message-ID: <20001111183857.A9781@forge.local> Mail-Followup-To: tmoestl@gmx.net, freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline User-Agent: Mutt/1.2.5i From: Thomas Moestl Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, recently, I have written a kernel patch that makes sendmsg(2) honor IP_RECVDSTADDR ancillary data on UDP sockets, so that the source address can be set on a per-packet basis. This is very useful for servers that need to use UDP and want to answer with the same source address a query went to. This is not always the case with vanilla sendto(2) in certain routing layouts. As this is my first kernel patch, could someone please give it a quick look before I submit it, so that I can be sure that it contains no stupid glitches? Unfortunately, I had no chance to test this on -current (I'm just building a -current box). Thanks, Thomas --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="recvdstaddr-current.diff" *** netinet/udp_usrreq.c.old Thu Nov 9 19:05:13 2000 --- netinet/udp_usrreq.c Thu Nov 9 19:23:54 2000 *************** *** 642,680 **** { register struct udpiphdr *ui; register int len = m->m_pkthdr.len; struct in_addr laddr; struct sockaddr_in *sin; ! int s = 0, error = 0; ! ! if (control) ! m_freem(control); /* XXX */ ! if (len + sizeof(struct udpiphdr) > IP_MAXPACKET) { error = EMSGSIZE; goto release; } if (addr) { sin = (struct sockaddr_in *)addr; prison_remote_ip(p, 0, &sin->sin_addr.s_addr); ! laddr = inp->inp_laddr; if (inp->inp_faddr.s_addr != INADDR_ANY) { error = EISCONN; ! goto release; } /* * Must block input while temporarily connected. */ ! s = splnet(); error = in_pcbconnect(inp, addr, p); ! if (error) { ! splx(s); ! goto release; ! } } else { if (inp->inp_faddr.s_addr == INADDR_ANY) { error = ENOTCONN; ! goto release; } } /* --- 642,741 ---- { register struct udpiphdr *ui; register int len = m->m_pkthdr.len; + register struct cmsghdr *cm = 0; struct in_addr laddr; struct sockaddr_in *sin; ! struct sockaddr_in src; ! int s = 0, error = 0, bound = 0, addrset = 0, fmbuf = 0; ! if (len + sizeof(struct udpiphdr) > IP_MAXPACKET) { error = EMSGSIZE; + if (control) + m_freem(control); goto release; } + if (control) { + /* + * XXX: Currently, we assume all the optional information is stored + * in a single mbuf. + */ + if (control->m_next) + error = EINVAL; + else { + for (; control->m_len; control->m_data += ALIGN(cm->cmsg_len), + control->m_len -= ALIGN(cm->cmsg_len)) { + cm = mtod(control, struct cmsghdr *); + if (cm->cmsg_len == 0 || cm->cmsg_len > control->m_len) { + error = EINVAL; + break; + } + if (cm->cmsg_level != IPPROTO_IP) + continue; + + switch(cm->cmsg_type) { + case IP_RECVDSTADDR: + if (cm->cmsg_len != CMSG_LEN(sizeof(struct in_addr))) { + error = EINVAL; + break; + } + laddr = inp->inp_laddr; + bzero(&src, sizeof(src)); + src.sin_family = AF_INET; + src.sin_port = inp->inp_lport; + src.sin_addr = *(struct in_addr *)CMSG_DATA(cm); + bound = 1; + s = splnet(); + if (inp->inp_laddr.s_addr == INADDR_ANY && inp->inp_lport == 0) { + /* This will check the address */ + error = in_pcbbind(inp, (struct sockaddr *)&src, p); + } else { + if (prison_ip(p, 0, &src.sin_addr.s_addr)) { + error = EINVAL; + break; + } + if (ifa_ifwithaddr((struct sockaddr *)&src) == 0) { + error = EADDRNOTAVAIL; + break; + } + inp->inp_laddr = src.sin_addr; + in_pcbrehash(inp); + } + break; + default: + error = ENOPROTOOPT; + } + if (error) + break; + } + } + m_freem(control); /* XXX */ + if (error) + goto unbind; + } + if (addr) { sin = (struct sockaddr_in *)addr; prison_remote_ip(p, 0, &sin->sin_addr.s_addr); ! if (!bound) ! laddr = inp->inp_laddr; if (inp->inp_faddr.s_addr != INADDR_ANY) { error = EISCONN; ! goto unbind; } /* * Must block input while temporarily connected. */ ! addrset=1; ! if (!bound) ! s = splnet(); error = in_pcbconnect(inp, addr, p); ! if (error) ! goto unbind; } else { if (inp->inp_faddr.s_addr == INADDR_ANY) { error = ENOTCONN; ! goto unbind; } } /* *************** *** 684,692 **** M_PREPEND(m, sizeof(struct udpiphdr), M_DONTWAIT); if (m == 0) { error = ENOBUFS; ! if (addr) ! splx(s); ! goto release; } /* --- 745,752 ---- M_PREPEND(m, sizeof(struct udpiphdr), M_DONTWAIT); if (m == 0) { error = ENOBUFS; ! /* XXX we did _not_ disconnect here before. Was that correct? Then back out! */ ! goto disconnect; } /* *************** *** 721,739 **** #ifdef IPSEC ipsec_setsocket(m, inp->inp_socket); #endif /*IPSEC*/ error = ip_output(m, inp->inp_options, &inp->inp_route, (inp->inp_socket->so_options & (SO_DONTROUTE | SO_BROADCAST)), inp->inp_moptions); ! if (addr) { in_pcbdisconnect(inp); inp->inp_laddr = laddr; /* XXX rehash? */ - splx(s); } ! return (error); ! release: ! m_freem(m); return (error); } --- 781,807 ---- #ifdef IPSEC ipsec_setsocket(m, inp->inp_socket); #endif /*IPSEC*/ + fmbuf = 1; error = ip_output(m, inp->inp_options, &inp->inp_route, (inp->inp_socket->so_options & (SO_DONTROUTE | SO_BROADCAST)), inp->inp_moptions); ! disconnect: ! if (addrset) { in_pcbdisconnect(inp); inp->inp_laddr = laddr; /* XXX rehash? */ } ! unbind: ! if (bound) { ! /* restore old state */ ! inp->inp_laddr = laddr; ! in_pcbrehash(inp); ! } ! if (addrset || bound) ! splx(s); release: ! if (!fmbuf) ! m_freem(m); return (error); } --gBBFr7Ir9EOA20Yy-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 10:50:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from intel.cleveland.lug.net (intel.cleveland.lug.net [207.166.193.101]) by hub.freebsd.org (Postfix) with ESMTP id 8683F37B479 for ; Sat, 11 Nov 2000 10:50:24 -0800 (PST) Received: from localhost (ken@localhost) by intel.cleveland.lug.net (8.9.3/8.9.3) with SMTP id NAA03707; Sat, 11 Nov 2000 13:47:42 -0500 Date: Sat, 11 Nov 2000 13:47:42 -0500 (EST) From: kf To: redhat-list@redhat.com Cc: freebsd-hackers@freebsd.org Subject: Re: [OT] serial protocol analyzer In-Reply-To: <3A0AF50D.16530.974B26@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't remember the url anymore, but I do remember that there was a Japanese guy who wrote drivers for digital cameras, cameras which connected to the serial port of a PC to download the pictures. On his site he mentioned a (free?) package which he used to analyze the "conversation" between the camera and the PC. So do a search for "digital cameras and Linux" at your favorite search engine and look for a site in Japan. hth, kf -- "If George W. Bush spoke his mind, he'd be speechless." On Thu, 9 Nov 2000, Leonard den Ottolander wrote: = Hello everybody, = = I was wondering if somebody could point me out a serial protocol analyzer. = Maybe analyzer is too big a word for what I am looking for (I could be the = analyzer:) ). What I am thinking of is a piece of software that listens on = two serial devices, and mimics input from either to the other, in the mean = time dumping and/or analyzing the traffic. To be concrete: I want to put a box = with this piece of software between another box and its modem to analyze the = traffic. = Thanks in advance, = = Ciao, = = Leonard. = = = = = = _______________________________________________ = Redhat-list mailing list = Redhat-list@redhat.com = https://listman.redhat.com/mailman/listinfo/redhat-list = To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 10:59:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id AE54037B479 for ; Sat, 11 Nov 2000 10:59:33 -0800 (PST) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eABIxWg32184; Sat, 11 Nov 2000 11:59:32 -0700 (MST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.1/8.8.3) with ESMTP id eABJ0iG31667; Sat, 11 Nov 2000 12:00:44 -0700 (MST) Message-Id: <200011111900.eABJ0iG31667@billy-club.village.org> To: opentrax@email.com Subject: Re: printf() Cc: duan@cs.umn.edu, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 11 Nov 2000 07:30:53 PST." <200011111530.HAA02982@spammie.svbug.com> References: <200011111530.HAA02982@spammie.svbug.com> Date: Sat, 11 Nov 2000 12:00:44 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011111530.HAA02982@spammie.svbug.com> opentrax@email.com writes: : printf("foo do foo\n"); : crash_here(); : printf("after the crash\n"); : : And never see the statement "foo do foo\n"; : Is that correct? Yes. But I had a lot of printfs in the code that I was debugging and the last few wouldn't be printed before the crash. But this was on a serial console where I had printed >> transmit fifo size. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 16:47:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id D6F3137B479 for ; Sat, 11 Nov 2000 16:47:03 -0800 (PST) Received: (qmail 22322 invoked by uid 0); 12 Nov 2000 00:47:00 -0000 Received: from p3ee21428.dip.t-dialin.net (HELO forge.local) (62.226.20.40) by mail.gmx.net (mail02) with SMTP; 12 Nov 2000 00:47:00 -0000 Received: from thomas by forge.local with local (Exim 3.12 #1 (Debian)) id 13ulIK-0003Iu-00 for ; Sun, 12 Nov 2000 01:46:52 +0100 Date: Sun, 12 Nov 2000 01:46:52 +0100 From: Thomas Moestl To: freebsd-hackers@freebsd.org Subject: Re: [PATCH] per-packet UDP source address selection for sendmsg Message-ID: <20001112014652.A12685@forge.local> Mail-Followup-To: Thomas Moestl , freebsd-hackers@freebsd.org References: <20001111183857.A9781@forge.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001111183857.A9781@forge.local>; from tmoestl@gmx.net on Sat, Nov 11, 2000 at 06:38:57PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As this is my first kernel patch, could someone please give it a quick > look before I submit it, so that I can be sure that it contains no stupid > glitches? > [...] > + bzero(&src, sizeof(src)); > + src.sin_family = AF_INET; > + src.sin_port = inp->inp_lport; > + src.sin_addr = *(struct in_addr *)CMSG_DATA(cm); > + bound = 1; Except of course forgetting to set src.sin_len :( Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 19:13:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id ED4BB37B479; Sat, 11 Nov 2000 19:13:39 -0800 (PST) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id WAA02111; Sat, 11 Nov 2000 22:13:36 -0500 (EST) Date: Sat, 11 Nov 2000 22:12:35 -0500 (EST) From: Zhiui Zhang X-Sender: zzhang@opal To: freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org Subject: simple lock and the lost wakeup problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am new to SMP subject and have some questions to ask: Is the simplelock() really needed since FreeBSD is using the big giant lock and the kernel is non preemptive? Or has FreeBSD changed the big giant lock and made kernel thread preemptive? Uresha Vahalia talks about Lost Wakeup Problem (page 196), the test of the resource and sleep() has to be done atomically. Which correct mechanism should I use on FreeBSD to achieve this (avoid the lost-wakeup problem)? Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 11 21:43:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1B3B437B479 for ; Sat, 11 Nov 2000 21:43:17 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAC5hAC01002; Sat, 11 Nov 2000 22:43:11 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA01462; Sat, 11 Nov 2000 22:43:01 -0700 (MST) Message-Id: <200011120543.WAA01462@harmony.village.org> To: Jan Grant Subject: Re: What about rc.shutdown.local? Cc: Greg Black , Christoph Sold , Jimmy Olgeni , hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 11 Nov 2000 10:35:49 GMT." References: Date: Sat, 11 Nov 2000 22:43:01 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Jan Grant writes: : It _is_ trivial, but you miss my point: I run several things at startup : that rely on a database service (which needs to be launched first). When : they shut down, the DB must still be running (it's taken down last). So : using a *.sh pattern for startup and shutdown scripts doesn't satisfy my : requirements. Right, that's why there's someone doing an evaluation of the NetBSD startup code to see how well it will work for exactly this sort of situation. Until that evaluation/proof of concept is complete, it would be premature to talk about changes to the FreeBSD system since the NetBSD one already copes with exactly this sort of situation. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message