From owner-freebsd-hackers Sun Dec 6 02:19:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08052 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 02:19:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lab321.ru (anonymous1.omsk.net.ru [62.76.128.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA08047 for ; Sun, 6 Dec 1998 02:18:31 -0800 (PST) (envelope-from kev@lab321.ru) Received: from www.lab321.ru (kev@www.lab321.ru [62.76.129.65]) by lab321.ru (8.9.1a/8.9.1a) with SMTP id QAA04596; Sun, 6 Dec 1998 16:16:55 +0600 (OS) Date: Sun, 6 Dec 1998 16:16:55 +0600 (OS) From: Eugeny Kuzakov To: Darren Reed cc: hackers@FreeBSD.ORG, darrenr@pobox.com Subject: Re: 2.2.8&ipfilter 3.2.10 panics In-Reply-To: <199812060544.QAA09692@avalon.reed.wattle.id.au> 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 Sun, 6 Dec 1998, Darren Reed wrote: > There's a patch recently posted to the IP Filter mailling list which uses > in_cksum() inside of fr_tcpsum() and solves this problem. I booted kernel with ipfilter 3.2.7. There are 3 traps at last night. Some time crashes when initializing ipnat. I can send you debug info, if you interesting.:( -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru ICQ#: 5885106 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 02:28:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08565 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 02:28:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lab321.ru (anonymous1.omsk.net.ru [62.76.128.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA08558 for ; Sun, 6 Dec 1998 02:28:36 -0800 (PST) (envelope-from kev@lab321.ru) Received: from www.lab321.ru (kev@www.lab321.ru [62.76.129.65]) by lab321.ru (8.9.1a/8.9.1a) with SMTP id QAA05475; Sun, 6 Dec 1998 16:20:06 +0600 (OS) Date: Sun, 6 Dec 1998 16:20:06 +0600 (OS) From: Eugeny Kuzakov To: Darren Reed cc: hackers@FreeBSD.ORG, darrenr@pobox.com Subject: Re: 2.2.8&ipfilter 3.2.10 panics In-Reply-To: <199812060544.QAA09692@avalon.reed.wattle.id.au> 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 Sun, 6 Dec 1998, Darren Reed wrote: > There's a patch recently posted to the IP Filter mailling list which uses > in_cksum() inside of fr_tcpsum() and solves this problem. Can anyone say me mailing list archive location or this patch ? 10tx. -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru ICQ#: 5885106 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 04:08:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20380 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 04:08:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from firewall.reed.wattle.id.au (darren2.lnk.telstra.net [139.130.53.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA20375 for ; Sun, 6 Dec 1998 04:08:38 -0800 (PST) (envelope-from darrenr@reed.wattle.id.au) Received: (from root@localhost) by firewall.reed.wattle.id.au (8.9.1/8.8.7) id MAA17680; Sun, 6 Dec 1998 12:08:32 GMT Received: from avalon.reed.wattle.id.au(192.168.1.1) by firewall.reed.wattle.id.au via smap (V1.3) id sma017678; Sun Dec 6 12:08:15 1998 Received: from percival.reed.wattle.id.au. (percival.reed.wattle.id.au [192.168.1.5]) by avalon.reed.wattle.id.au (8.9.0.Beta3/8.9.0.Beta3) with SMTP id XAA10143; Sun, 6 Dec 1998 23:08:15 +1100 (EST) From: Darren Reed Message-Id: <199812061208.XAA10143@avalon.reed.wattle.id.au> Subject: Re: 2.2.8&ipfilter 3.2.10 panics To: kev@lab321.ru (Eugeny Kuzakov) Date: Sun, 6 Dec 1998 23:08:14 +1100 (EST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Eugeny Kuzakov" at Dec 6, 98 04:20:06 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some email I received from Eugeny Kuzakov, sie wrote: > > On Sun, 6 Dec 1998, Darren Reed wrote: > > > There's a patch recently posted to the IP Filter mailling list which uses > > in_cksum() inside of fr_tcpsum() and solves this problem. > Can anyone say me mailing list archive location or this patch ? > 10tx. The web page version is `messy'...and I can't update the ftp site right now so see below. darren Index: fil.c =================================================================== RCS file: /devel/CVS/IP-Filter/fil.c,v retrieving revision 2.0.2.41.2.27 retrieving revision 2.0.2.41.2.29 diff -c fil.c.orig fil.c *** /tmp/T00GMcpW Sun Dec 6 23:06:48 1998 --- /tmp/T10Iie8o Sun Dec 6 23:06:48 1998 *************** *** 7,13 **** */ #if !defined(lint) static const char sccsid[] = "@(#)fil.c 1.36 6/5/96 (C) 1993-1996 Darren Reed"; ! static const char rcsid[] = "@(#)$Id: fil.c,v 2.0.2.41.2.27 1998/11/22 01:50:15 darrenr Exp $"; #endif #include --- 7,13 ---- */ #if !defined(lint) static const char sccsid[] = "@(#)fil.c 1.36 6/5/96 (C) 1993-1996 Darren Reed"; ! static const char rcsid[] = "@(#)$Id: fil.c,v 2.0.2.41.2.29 1998/11/28 02:25:25 darrenr Exp $"; #endif #include *************** *** 949,955 **** --- 949,1028 ---- ip_t *ip; tcphdr_t *tcp; int len; + #if SOLARIS || defined(KERNEL) && ((defined(BSD) || defined(sun))) + # if SOLARIS { + struct ip ipd, *ipp = &ipd; + mblk_t mb, *mp = &mb; + struct datab db, *dp = &db; + u_short sum; + int hlen; + + bzero((char *)dp, sizeof(*dp)); + bzero((char *)mp, sizeof(*mp)); + dp->db_type = M_DATA; + dp->db_base = (u_char *)ipp; + mp->b_rptr = dp->db_base; + mp->b_wptr = dp->db_base + sizeof(*ipp); + mp->b_datap = dp; + + hlen = ip->ip_hl << 2; + + ipp->ip_src = ip->ip_src; + ipp->ip_dst = ip->ip_dst; + ipp->ip_p = ip->ip_p; + ipp->ip_len = htons(ip->ip_len); + m->b_rptr += hlen; + #ifdef _KERNEL + sum = IP_CSUM(mp, len, 0); + #else + sum = 0; + #endif + m->b_rptr -= hlen; + return sum; + } + # else + # if (defined(BSD) || defined(sun)) + { + struct ip *ipp; + struct mbuf mb, *mp = &mb; + u_short sum; + int hlen; + + bzero((char *)mp, sizeof(*mp)); + hlen = ip->ip_hl << 2; + mp->m_next = m; + mp->m_len = hlen; + mp->m_type = MT_DATA; + # if BSD >= 199306 + mp->m_data = mp->m_dat; + # else + mp->m_off = MMINOFF; + # endif + ipp = mtod(mp, struct ip *); + ipp->ip_src = ip->ip_src; + ipp->ip_dst = ip->ip_dst; + ipp->ip_p = ip->ip_p; + ipp->ip_len = htons(ip->ip_len); + m->m_len -= hlen; + # if BSD >= 199306 + m->m_data += hlen; + # else + m->m_off += hlen; + # endif + sum = in_cksum(mp, len); + m->m_len += hlen; + # if BSD >= 199306 + m->m_data -= hlen; + # else + m->m_off -= hlen; + # endif + return sum; + } + # endif /* BSD || sun */ + # endif /* SOLARIS */ + #else /* KERNEL */ + { union { u_char c[2]; u_short s; *************** *** 956,962 **** } bytes; u_32_t sum; u_short *sp, slen; ! # if SOLARIS || defined(__sgi) int add, hlen; # endif --- 1029,1035 ---- } bytes; u_32_t sum; u_short *sp, slen; ! # if defined(__sgi) int add, hlen; # endif *************** *** 985,1015 **** sp += 2; /* Skip over checksum */ sum += *sp++; /* urp */ ! #if SOLARIS /* - * In case we had to copy the IP & TCP header out of mblks, - * skip over the mblk bits which are the header - */ - if ((caddr_t)ip != (caddr_t)m->b_rptr) { - hlen = (caddr_t)sp - (caddr_t)ip; - while (hlen) { - add = MIN(hlen, m->b_wptr - m->b_rptr); - sp = (u_short *)((caddr_t)m->b_rptr + add); - hlen -= add; - if ((caddr_t)sp >= (caddr_t)m->b_wptr) { - m = m->b_cont; - if (!hlen) { - if (!m) - break; - sp = (u_short *)m->b_rptr; - } - PANIC((!m),("fr_tcpsum(1): not enough data")); - } - } - } - #endif - #ifdef __sgi - /* * In case we had to copy the IP & TCP header out of mbufs, * skip over the mbuf bits which are the header */ --- 1058,1065 ---- sp += 2; /* Skip over checksum */ sum += *sp++; /* urp */ ! # ifdef __sgi /* * In case we had to copy the IP & TCP header out of mbufs, * skip over the mbuf bits which are the header */ *************** *** 1030,1056 **** } } } ! #endif if (!(len -= sizeof(*tcp))) goto nodata; while (len > 1) { - #if SOLARIS - if ((caddr_t)sp >= (caddr_t)m->b_wptr) { - m = m->b_cont; - PANIC((!m),("fr_tcpsum(2): not enough data")); - sp = (u_short *)m->b_rptr; - } - if ((caddr_t)(sp + 1) > (caddr_t)m->b_wptr) { - bytes.c[0] = *(u_char *)sp; - m = m->b_cont; - PANIC((!m),("fr_tcpsum(3): not enough data")); - sp = (u_short *)m->b_rptr; - bytes.c[1] = *(u_char *)sp; - sum += bytes.s; - sp = (u_short *)((u_char *)sp + 1); - } - #else if (((caddr_t)sp - mtod(m, caddr_t)) >= m->m_len) { m = m->m_next; PANIC((!m),("fr_tcpsum(2): not enough data")); --- 1080,1090 ---- } } } ! # endif if (!(len -= sizeof(*tcp))) goto nodata; while (len > 1) { if (((caddr_t)sp - mtod(m, caddr_t)) >= m->m_len) { m = m->m_next; PANIC((!m),("fr_tcpsum(2): not enough data")); *************** *** 1065,1071 **** sum += bytes.s; sp = (u_short *)((u_char *)sp + 1); } - #endif /* SOLARIS */ if ((u_long)sp & 1) { bcopy((char *)sp++, (char *)&bytes.s, sizeof(bytes.s)); sum += bytes.s; --- 1099,1104 ---- *************** *** 1081,1086 **** --- 1114,1120 ---- sum = (u_short)(~sum & 0xffff); return sum; } + #endif /* KERNEL */ #if defined(_KERNEL) && ( ((BSD < 199306) && !SOLARIS) || defined(__sgi) ) *************** *** 1117,1123 **** * SUCH DAMAGE. * * @(#)uipc_mbuf.c 8.2 (Berkeley) 1/4/94 ! * $Id: fil.c,v 2.0.2.41.2.27 1998/11/22 01:50:15 darrenr Exp $ */ /* * Copy data from an mbuf chain starting "off" bytes from the beginning, --- 1151,1157 ---- * SUCH DAMAGE. * * @(#)uipc_mbuf.c 8.2 (Berkeley) 1/4/94 ! * $Id: fil.c,v 2.0.2.41.2.29 1998/11/28 02:25:25 darrenr Exp $ */ /* * Copy data from an mbuf chain starting "off" bytes from the beginning, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 04:10:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20753 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 04:10:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA20685 for ; Sun, 6 Dec 1998 04:09:55 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.150]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA636A; Sun, 6 Dec 1998 13:09:43 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] 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: Sun, 06 Dec 1998 13:15:13 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Andrzej Bialecki Subject: Re: System V init (was: Linux to be deployed in Mexican schools; Cc: hackers@FreeBSD.ORG, Eivind Eklund , Dan Busarow , ADRIAN Filipi-Martin , Matthew Dillon , Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 01-Dec-98 Andrzej Bialecki wrote: > On Tue, 1 Dec 1998, Amancio Hasty wrote: > >> > http://www.freebsd.org/~picobsd/picobsd/doc/UCI.html >> >> This looks very interesting . have you decided on a network protocol or >> do you think that you will need a new network protocol? > > No, I haven't decided yet almost anything... I thought about SNMP. The idea we came with was based on embedded systems so keep that in mind with regard to some ideas... SNMP was a short-term available answer to managing the devices et al. > Well, this is still a proposal only - a food for thought. But I'd love to > hear comments on this, and suggestions. Eventually, I'll try to implement > parts of it... As soon as we come up with a reasonable modularity scheme. Basically it's something like Matt proposed but it ennumerates and depends rather in a different style. Cisco fans (and in lesser Shiva/ShivOS fans) might recognise the modularity built-up of the devices and other relevant configuration `files'. One thing was to access this configuration `database' by means of HTTP, CLI or SNMP. --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 08:10:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09591 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 08:10:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lily.ezo.net (lily.ezo.net [206.102.130.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09575; Sun, 6 Dec 1998 08:10:04 -0800 (PST) (envelope-from jflowers@ezo.net) Received: from crocus (c3-1d196.neo.rr.com [24.93.233.196]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id LAA01244; Sun, 6 Dec 1998 11:09:51 -0500 (EST) Message-ID: <000d01be213b$625d6eb0$848266ce@crocus.ezo.net> From: "Jim Flowers" To: , Subject: Help with TCP listen() function Date: Sun, 6 Dec 1998 12:10:53 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01BE2111.78BC2770" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000A_01BE2111.78BC2770 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am trying to port a cable modem (roadrunner) login program written for = linux to freebsd 2.2.7 before the Dec 15 deadline. Should have been = suspicious when it compiled cleanly without error message. The program runs up to the point of setting up a TCP socket to request a = login sequence using functions: socket() htons() bind() listen() and then quits with errnum for "Operation not supported". The function calls seem to be correctly written and do not return any = errors when called (except for listen()). Is this a correct sequence to establish a passive tcp connection? Is = there a better way to do it? Is there a knowledge base for converting = linux code to run on FreeBSD? References for the correct way to write = code to establish tcp connections? If a review of the code segment would be helpful, it is brief and = follows. Thanks Jim Flowers //------------------------------------------------------------ // RRListen() - Creates a listen socket for session status and // restart requests int RRListen(unsigned short *listenport) { unsigned short port; int s; struct sockaddr_in saddr; if ((s =3D socket (AF_INET, SOCK_DGRAM, 0)) < 0) { syslog(LOG_ERR, "Error creating listen socket: %m"); return -1; } // Bind first available port starting at 7770 port =3D 7770; saddr.sin_family =3D AF_INET; saddr.sin_addr.s_addr =3D INADDR_ANY; do { saddr.sin_port =3D htons(port); errno =3D 0; if (bind(s, (struct sockaddr *) &saddr, sizeof(struct = sockaddr_in)) < 0) { if (errno !=3D EADDRINUSE) { syslog(LOG_ERR, "Error binding listen socket: %m"); close(s); return -1; } else { port++; } } } while (errno =3D=3D EADDRINUSE); if (listen(s, 1) < 0) { syslog(LOG_ERR, "Error listening on socket: %m"); close(s); return -1; } *listenport =3D port; syslog(LOG_INFO, "Established listener on port: %i", port); return s; ) -------------------------------------------------------------------------= ------ ------=_NextPart_000_000A_01BE2111.78BC2770 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I am trying to port a cable modem = (roadrunner)=20 login program written for linux to freebsd 2.2.7 before the Dec 15=20 deadline.  Should have been suspicious when it compiled cleanly = without=20 error message.
 
The program runs up to the point of setting up a TCP = socket to=20 request a login sequence using functions:
 
socket()
htons()
bind()
listen()
 
and then quits with errnum for "Operation not=20 supported".
 
The function calls seem to be correctly written and = do not=20 return any errors when called (except for listen()).
 
Is this a correct sequence to establish a passive = tcp=20 connection?  Is there a better way to do it? Is there a knowledge = base for=20 converting linux code to run on FreeBSD?  = References=20 for the correct way to write code to establish tcp = connections?
 
If a review of the code segment would be helpful, it = is brief=20 and follows.
 
Thanks
Jim Flowers <jflowers@ezo.net>
 
 
//------------------------------------------------------------//=20 RRListen() - Creates a listen socket for session status=20 and
//          &nbs= p;  =20 restart requests
int RRListen(unsigned short=20 *listenport)
{
 unsigned short port;
   int=20 s;
   struct sockaddr_in saddr;
 
   if ((s =3D socket = (AF_INET,=20 SOCK_DGRAM, 0)) < 0) {
      = syslog(LOG_ERR,=20 "Error creating listen socket: = %m");
     =20 return -1;
   }
 
 // Bind first available port = starting at=20 7770
   port =3D 7770;
   saddr.sin_family =3D = AF_INET;
   saddr.sin_addr.s_addr =3D = INADDR_ANY;
   do=20 {
    saddr.sin_port =3D=20 htons(port);
      errno =3D=20 0;
      if (bind(s, (struct sockaddr *) = &saddr,=20 sizeof(struct sockaddr_in)) < 0) {
 if (errno !=3D = EADDRINUSE)=20 {
          =20 syslog(LOG_ERR, "Error binding listen socket:=20 %m");
          = ;=20 close(s);
          = return=20 -1;
         } else=20 {
   =20 port++;
        =20 }
      }
 } while (errno =3D=3D=20 EADDRINUSE);
 
 if (listen(s, 1) < 0)=20 {
     syslog(LOG_ERR, "Error listening on = socket:=20 %m");
     = close(s);
    =20 return -1;
   }
 
   *listenport =3D = port;
  =20 syslog(LOG_INFO, "Established listener on port: %i",=20 port);
   return s;
)
----------------------------------------------------------------= ---------------
------=_NextPart_000_000A_01BE2111.78BC2770-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 08:17:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10340 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 08:17:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10322; Sun, 6 Dec 1998 08:17:27 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.1/8.9.1) with ESMTP id LAA54526; Sun, 6 Dec 1998 11:17:23 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199812061617.LAA54526@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jim Flowers" cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Help with TCP listen() function References: <000d01be213b$625d6eb0$848266ce@crocus.ezo.net> In-reply-to: Your message of "Sun, 06 Dec 1998 12:10:53 EST." <000d01be213b$625d6eb0$848266ce@crocus.ezo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 06 Dec 1998 11:17:22 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem is that you're not trying to do a TCP "listen" operation; you're creating a UDP datagram socket, and not a TCP (SOCK_STREAM) type socket. The listen system call isn't defined to work on datagram sockets because there are no new connections to be accepted. This is probably a freebsd-questions mailing list issue for any follow-up. louie > > ------=_NextPart_000_000A_01BE2111.78BC2770 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > I am trying to port a cable modem (roadrunner) login program written for = > linux to freebsd 2.2.7 before the Dec 15 deadline. Should have been = > suspicious when it compiled cleanly without error message. > > The program runs up to the point of setting up a TCP socket to request a = > login sequence using functions: > > socket() > htons() > bind() > listen() > > and then quits with errnum for "Operation not supported". > > The function calls seem to be correctly written and do not return any = > errors when called (except for listen()). > > Is this a correct sequence to establish a passive tcp connection? Is = > there a better way to do it? Is there a knowledge base for converting = > linux code to run on FreeBSD? References for the correct way to write = > code to establish tcp connections? > > If a review of the code segment would be helpful, it is brief and = > follows. > > Thanks > Jim Flowers > > > //------------------------------------------------------------ > // RRListen() - Creates a listen socket for session status and > // restart requests > int RRListen(unsigned short *listenport) > { > unsigned short port; > int s; > struct sockaddr_in saddr; > > if ((s =3D socket (AF_INET, SOCK_DGRAM, 0)) < 0) { > syslog(LOG_ERR, "Error creating listen socket: %m"); > return -1; > } > > // Bind first available port starting at 7770 > port =3D 7770; > saddr.sin_family =3D AF_INET; > saddr.sin_addr.s_addr =3D INADDR_ANY; > do { > saddr.sin_port =3D htons(port); > errno =3D 0; > if (bind(s, (struct sockaddr *) &saddr, sizeof(struct = > sockaddr_in)) < 0) { > if (errno !=3D EADDRINUSE) { > syslog(LOG_ERR, "Error binding listen socket: %m"); > close(s); > return -1; > } else { > port++; > } > } > } while (errno =3D=3D EADDRINUSE); > > if (listen(s, 1) < 0) { > syslog(LOG_ERR, "Error listening on socket: %m"); > close(s); > return -1; > } > > *listenport =3D port; > syslog(LOG_INFO, "Established listener on port: %i", port); > return s; > ) > -------------------------------------------------------------------------= > ------ > > ------=_NextPart_000_000A_01BE2111.78BC2770 > Content-Type: text/html; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > > > > > http-equiv=3DContent-Type> > > > >
I am trying to port a cable modem = > (roadrunner)=20 > login program written for linux to freebsd 2.2.7 before the Dec 15=20 > deadline.  Should have been suspicious when it compiled cleanly = > without=20 > error message.
>
 
>
The program runs up to the point of setting up a TCP = > socket to=20 > request a login sequence using functions:
>
 
>
socket()
>
htons()
>
bind()
>
listen()
>
 
>
and then quits with errnum for "Operation not=20 > supported".
>
 
>
The function calls seem to be correctly written and = > do not=20 > return any errors when called (except for listen()).
>
 
>
Is this a correct sequence to establish a passive = > tcp=20 > connection?  Is there a better way to do it? Is there a knowledge = > base for=20 > converting linux code to run on FreeBSD?  = > References=20 > for the correct way to write code to establish tcp = > connections?
>
 
>
If a review of the code segment would be helpful, it = > is brief=20 > and follows.
>
 
>
Thanks
>
Jim Flowers < href=3D"mailto:jflowers@ezo.net">jflowers@ezo.net>
>
 
>
 
>
size=3D2>//------------------------------------------------------------ R>//=20 > RRListen() - Creates a listen socket for session status=20 > and
//          &nbs= > p;  =20 > restart requests
int RRListen(unsigned short=20 > *listenport)
{
 unsigned short port;
   int=20 > s;
   struct sockaddr_in saddr;
>
 
>
   if ((s =3D socket = > (AF_INET,=20 > SOCK_DGRAM, 0)) < 0) {
      = > syslog(LOG_ERR,=20 > "Error creating listen socket: = > %m");
     =20 > return -1;
   }
>
 
>
 // Bind first available port = > starting at=20 > 7770
   port =3D 7770;
   saddr.sin_family =3D = > > AF_INET;
   saddr.sin_addr.s_addr =3D = > INADDR_ANY;
   do=20 > {
    saddr.sin_port =3D=20 > htons(port);
      errno =3D=20 > 0;
      if (bind(s, (struct sockaddr *) = > &saddr,=20 > sizeof(struct sockaddr_in)) < 0) {
 if (errno !=3D = > EADDRINUSE)=20 > {
          =20 > syslog(LOG_ERR, "Error binding listen socket:=20 > %m");
          = > ;=20 > close(s);
          = > return=20 > -1;
         } else=20 > {
   =20 > port++;
        =20 > }
      }
 } while (errno =3D=3D=20 > EADDRINUSE);
>
 
>
 if (listen(s, 1) < 0)=20 > {
     syslog(LOG_ERR, "Error listening on = > socket:=20 > %m");
     = > close(s);
    =20 > return -1;
   }
>
 
>
   *listenport =3D = > port;
  =20 > syslog(LOG_INFO, "Established listener on port: %i",=20 > port);
   return s;
)
>
size=3D2>----------------------------------------------------------------= > ---------------
> > ------=_NextPart_000_000A_01BE2111.78BC2770-- > > > 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 Dec 6 08:50:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14066 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 08:50:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14061; Sun, 6 Dec 1998 08:50:42 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id RAA14250; Sun, 6 Dec 1998 17:50:35 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id RAA14848; Sun, 6 Dec 1998 17:27:45 +0100 (MET) (envelope-from j) Message-ID: <19981206172744.53389@uriah.heep.sax.de> Date: Sun, 6 Dec 1998 17:27:44 +0100 From: J Wunsch To: freebsd-hackers@FreeBSD.ORG, cvs-committers@FreeBSD.ORG Subject: Re: getting to -Wunused Reply-To: Joerg Wunsch References: <199812060032.QAA01400@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199812060032.QAA01400@bubba.whistle.com>; from Archie Cobbs on Sat, Dec 05, 1998 at 04:32:44PM -0800 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Archie Cobbs wrote: > (d) Static functions that are declared and defined, but never used: > > (i) Some of these are defined #ifdef DDB, and are clearly meant > for debugging purposes (they're not used, but they're handy > to call from the debugger to print out stuff, etc). These > are "legitimate" unused functions. I think those should not be defined `static'. If they are meant to be called from within DDB, it's necessary to maintain a globally unique function name anyway, so why having it `static'? (Of course, the function remains in an `apparently unsued' state, but for a non-static function, the compiler should be silent for this.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 08:52:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14395 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 08:52:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from godzilla.zeta.org.au ([203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14387; Sun, 6 Dec 1998 08:52:24 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA22562; Mon, 7 Dec 1998 03:52:14 +1100 Date: Mon, 7 Dec 1998 03:52:14 +1100 From: Bruce Evans Message-Id: <199812061652.DAA22562@godzilla.zeta.org.au> To: archie@whistle.com, cvs-committers@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: getting to -Wunused Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It looks like the next kernel compilation -W flag to be slayed is >the "-Wunused" flag (see bsd.kern.mk).. right now, compiling LINT >with this flag yeilds about 350 unused variable or function warnings. Only 266 now (after lprintf fixes?). Actually, plain -W is next. Among other warnings, it gives an additional 2763 warnings for unused function parameters. (This is documented in gcc.info but not in gcc.1.) Most of these are not bogons and can't be fixed nicely, so the bogons reported by -Wunused should be fixed first. > (d) Static functions that are declared and defined, but never used: > > (i) Some of these are defined #ifdef DDB, and are clearly meant > for debugging purposes (they're not used, but they're handy > to call from the debugger to print out stuff, etc). These > are "legitimate" unused functions. No, these are illegitimate. The should be attached to the ddb command table so that they are both used and easier to use. Use the DDB_COMMAND and DDB_SHOW_COMMAND macros for this. Don't break the warning by decaring the functions as __unused. (Bug: these macros usually add dummy args that make it harder to call the functions directly. Direct calls are still useful, at least from gdb.) > Step #2. Add "__attribute__ ((unused))" to all cases of (d)(i), that is, > obviously legitimate unused functions (I count only 2 so far). __attribute__(()) should not be used outside of , especially when there is already a suitable macro there, namely `__unused'. `__attribute__ ((unused))' has 1 style bug and 1 real bug. >Note that Steps #1 and #2 will *not* eliminate all the unused variable >warnings, because I can't do a kernel compile with every possible >permutation of kernel options.. but it should get most of them. You should check for variables that are used in ifdefed code and ifdef the variables. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 09:01:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15118 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 09:01:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15113; Sun, 6 Dec 1998 09:01:31 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id SAA46299; Sun, 6 Dec 1998 18:00:34 +0100 (CET) To: Bruce Evans cc: archie@whistle.com, cvs-committers@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: getting to -Wunused In-reply-to: Your message of "Mon, 07 Dec 1998 03:52:14 +1100." <199812061652.DAA22562@godzilla.zeta.org.au> Date: Sun, 06 Dec 1998 18:00:34 +0100 Message-ID: <46296.912963634@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >You should check for variables that are used in ifdefed code and ifdef >the variables. See also: src/tools/tools/kernxref/* -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 09:03:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15411 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 09:03:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from godzilla.zeta.org.au ([203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15406; Sun, 6 Dec 1998 09:02:59 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id EAA23009; Mon, 7 Dec 1998 04:02:55 +1100 Date: Mon, 7 Dec 1998 04:02:55 +1100 From: Bruce Evans Message-Id: <199812061702.EAA23009@godzilla.zeta.org.au> To: cvs-committers@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, j@uriah.heep.sax.de Subject: Re: getting to -Wunused Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> (i) Some of these are defined #ifdef DDB, and are clearly meant >> for debugging purposes (they're not used, but they're handy >> to call from the debugger to print out stuff, etc). These >> are "legitimate" unused functions. > >I think those should not be defined `static'. If they are meant to >be called from within DDB, it's necessary to maintain a globally >unique function name anyway, so why having it `static'? Mainly because they show up as noise in staticness checkers such as kernxref.sh. Anyway, _all_ functions should have globally unique names so that they can be referenced from within ddb. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 09:11:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15980 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 09:11:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15939 for ; Sun, 6 Dec 1998 09:10:59 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id MAA03252; Sun, 6 Dec 1998 12:09:59 -0500 (EST) Date: Sun, 6 Dec 1998 12:09:58 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 Reply-To: zhihuizhang To: hackers cc: dfr@nlsystems.com Subject: Definition of kstack and PTDpde in locore.s 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, Back in August, I posted a question about whether .set _xx, 30 in assembly defines the value of xx or the address of xx (xx is the counterpart of _xx in C). The response I got is that the address of xx is 30. (note that xx without preceding "_" is used in C). So the address of PTDpde is PTD + (PTDI * PAGE_SIZE) (see locore.s). This explains why the statement (unsigned)PTDpde & PG_FRAME gives the "physical" address of the page directory page of the current address space. We often use the following condition in pmap.c to see if the given pmap uses the same page directory page as the curent address space. if ((((unsigned)pmap->pm_pdir[PTDPTDI]) & PG_FRAME) == (((unsigned) PTDpde) & PG_FRAME)) { ... } So far, it is fine for me. Yesterday, I came across the symbol kstack which is defined similary via the .set directive in locore.s. However, in pmap.c, I find the following usage: m = pmap_allocpte(pmap, (vm_offset_t) kstack); So kstack must be a virtual address (I means its value). However, according to my undestanding derived from PTDpde, the kstack should be stored at the fixed virtual address (VADDR(KSTKPTDI, KSTKPTE)), its value is another thing (should be initialized some where). But the pmap_allocpte() statement clearly requires kstack's value and, I guess the kernel stack for each process should be at the same VA. So, what does the following statement do (in locore.s): .set _kstack,USRSTACK (note: USRSTACK = VADDR(KSTKPTDI, KSTKPTEOFF)) Does it give the address of kstack or value of kstack? The GAS only says it gives the value of the symbol. I really have problem with mixed assembly and C programming when they reference the same symbols (one with the preceding "_" and one without "_"). I hope some one can clarify these stuff for me. Thanks a lot. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 10:50:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23614 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 10:50:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ip126.directhost.net (ip126.directhost.net [209.67.132.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23609 for ; Sun, 6 Dec 1998 10:50:37 -0800 (PST) (envelope-from rode@directhost.net) Received: from ip012 (ip012.directhost.net [209.67.132.12]) by ip126.directhost.net (8.9.1/8.8.8) with SMTP id KAA21830 for ; Sun, 6 Dec 1998 10:50:35 -0800 (PST) Message-ID: <003701be213c$63c594c0$0c8443d1@ip012.directhost.net> From: "Rod Ebrahimi" To: Subject: NFS Customization Date: Sun, 6 Dec 1998 09:18:06 -0800 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 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was curious as to where I could find more information about customization of NFS and advanced NFS networking using FreeBSD 3.0 Release... Any information would be helpful. Thank you in advance. Rod -- Rod Ebrahimi v:714.897.4444 DirectHOST Internet p:714.806.1357 http://www.directhost.net/ mailto:rode@directhost.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 11:06:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24969 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 11:06:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24954; Sun, 6 Dec 1998 11:05:59 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id KAA16485; Sun, 6 Dec 1998 10:58:16 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma016483; Sun, 6 Dec 98 10:57:54 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id KAA13176; Sun, 6 Dec 1998 10:57:53 -0800 (PST) From: Archie Cobbs Message-Id: <199812061857.KAA13176@bubba.whistle.com> Subject: Re: getting to -Wunused In-Reply-To: <46296.912963634@critter.freebsd.dk> from Poul-Henning Kamp at "Dec 6, 98 06:00:34 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Sun, 6 Dec 1998 10:57:53 -0800 (PST) Cc: bde@zeta.org.au, archie@whistle.com, cvs-committers@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Poul-Henning Kamp writes: > >You should check for variables that are used in ifdefed code and ifdef > >the variables. > > See also: src/tools/tools/kernxref/* Cool.. we can make "Step 5" the removal of non-static unused functions :-) By the way, I neede to add "-aout": Index: kernxref.sh =================================================================== RCS file: /home/ncvs/src/tools/tools/kernxref/kernxref.sh,v retrieving revision 1.9 diff -u -r1.9 kernxref.sh --- kernxref.sh 1998/11/27 10:18:56 1.9 +++ kernxref.sh 1998/12/06 18:57:57 @@ -13,7 +13,7 @@ # kernel. cd /sys/compile/LINT -nm -gon `echo *.o /lkm/*.o | tr ' ' '\012' | egrep -v '(aicasm|genassym)'` | +nm -aout -gon `echo *.o /lkm/*.o | tr ' ' '\012' | egrep -v '(aicasm|genassym)'` | tr : ' ' | awk ' NF > 1 { if (length($2) == 8) { -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 11:14:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25705 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 11:14:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25700; Sun, 6 Dec 1998 11:14:36 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id UAA54792; Sun, 6 Dec 1998 20:13:47 +0100 (CET) To: Archie Cobbs cc: bde@zeta.org.au, cvs-committers@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: getting to -Wunused In-reply-to: Your message of "Sun, 06 Dec 1998 10:57:53 PST." <199812061857.KAA13176@bubba.whistle.com> Date: Sun, 06 Dec 1998 20:13:47 +0100 Message-ID: <54790.912971627@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812061857.KAA13176@bubba.whistle.com>, Archie Cobbs writes: >Poul-Henning Kamp writes: >> >You should check for variables that are used in ifdefed code and ifdef >> >the variables. >> >> See also: src/tools/tools/kernxref/* > >Cool.. we can make "Step 5" the removal of non-static unused functions :-) >By the way, I neede to add "-aout": Sure, go ahead and commit it. > >Index: kernxref.sh >=================================================================== >RCS file: /home/ncvs/src/tools/tools/kernxref/kernxref.sh,v >retrieving revision 1.9 >diff -u -r1.9 kernxref.sh >--- kernxref.sh 1998/11/27 10:18:56 1.9 >+++ kernxref.sh 1998/12/06 18:57:57 >@@ -13,7 +13,7 @@ > # kernel. > > cd /sys/compile/LINT >-nm -gon `echo *.o /lkm/*.o | tr ' ' '\012' | egrep -v '(aicasm|genassym)'` | >+nm -aout -gon `echo *.o /lkm/*.o | tr ' ' '\012' | egrep -v '(aicasm|genassym)'` | > tr : ' ' | awk ' > NF > 1 { > if (length($2) == 8) { > >-Archie > >___________________________________________________________________________ >Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 13:43:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07994 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 13:43:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from circe.bonn-online.com (circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07988 for ; Sun, 6 Dec 1998 13:43:43 -0800 (PST) (envelope-from lederer@bonn-online.com) Received: from bonn-online.com (ppp156.dialin.bonn-online.com [194.162.223.156]) by circe.bonn-online.com (8.8.8/8.8.5) with ESMTP id WAA21996 for ; Sun, 6 Dec 1998 22:43:30 +0100 Message-ID: <366AFAAD.DB256896@bonn-online.com> Date: Sun, 06 Dec 1998 22:44:13 +0100 From: Sebastian Lederer X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Testers wanted 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 developing an X11-based installation program for FreeBSD, currently named "Total Installation". You can get some preliminary information about it at: http://www.stud.fh-rhein-sieg.de/~sleder2s/totali.html One of its features is that it automatically creates an XF86Config file by scanning the PCI bus for the graphics card and doing some other guesswork. So what I would like you to do is to test this X autoconfiguration module and see if it produces a valid XF86Config file for your system. To do so, please get the file http://www.stud.fh-rhein-sieg.de/~sleder2s/Xstart.tar.gz , unpack it, type "make" and run the script "start.sh" as root (root access is required to scan the pci bus and to start the X server with a specific configuration file). The XF86Config file will be generated and placed in the /tmp directory. If it works, you will get the standard X screen (in 640x480, 60Hz) and an xterm. To get out, simply exit the shell inside the xterm window. But please make sure that the mouse moves correctly before. To have any chance for success, you need: - a PCI/AGP graphics card with at least 2MB RAM - PS/2 mouse , serial-pnp mouse recognized by moused(8) or ms-compatible mouse on first serial port - XFree86 installed (esp. the X server for your card) - FreeBSD 2.2.[78] or 3.0 Make sure that moused(8) isn't running before starting the script, as it will try to start moused itself. If you don't use moused in your normal configuration, also kill it afterwards ("killall moused"). Please let me know if you tried it, regardless of whether it worked or not. Also let me know which graphics card and mouse configuration you tested it on. BTW, it worked for me on S3-Trio64V+ and Matrox Mystique cards with PS/2- and serial M$-mice. Should work on FreeBSD 3.0 and 2.2.7/2.2.8. Thanks in advance and best regards, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 20:05:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11203 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 20:05:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from godzilla.zeta.org.au ([203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11198; Sun, 6 Dec 1998 20:05:50 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA03585; Mon, 7 Dec 1998 15:05:39 +1100 Date: Mon, 7 Dec 1998 15:05:39 +1100 From: Bruce Evans Message-Id: <199812070405.PAA03585@godzilla.zeta.org.au> To: archie@whistle.com, phk@critter.freebsd.dk Subject: Re: getting to -Wunused Cc: bde@zeta.org.au, cvs-committers@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Cool.. we can make "Step 5" the removal of non-static unused functions :-) >By the way, I neede to add "-aout": Use `OBJFORMAT=aout kernxref.sh'. >Index: kernxref.sh >=================================================================== >RCS file: /home/ncvs/src/tools/tools/kernxref/kernxref.sh,v >retrieving revision 1.9 >diff -u -r1.9 kernxref.sh >--- kernxref.sh 1998/11/27 10:18:56 1.9 >+++ kernxref.sh 1998/12/06 18:57:57 >@@ -13,7 +13,7 @@ > # kernel. > > cd /sys/compile/LINT >-nm -gon `echo *.o /lkm/*.o | tr ' ' '\012' | egrep -v '(aicasm|genassym)'` | >+nm -aout -gon `echo *.o /lkm/*.o | tr ' ' '\012' | egrep -v '(aicasm|genassym)'` | > tr : ' ' | awk ' > NF > 1 { > if (length($2) == 8) { > Bugs in this: - it breaks kernxref.sh some more for elf kernels. LKMs always have a.out format, but the kernel may have elf format. kernxref.sh should look at modules instead of LKMs, but since modules are in the default format, that will only work when the kernel is in the default format. - it makes a line longer than 80 characters. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 6 20:26:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13452 for freebsd-hackers-outgoing; Sun, 6 Dec 1998 20:26:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13447 for ; Sun, 6 Dec 1998 20:26:08 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id UAA18789; Sun, 6 Dec 1998 20:18:27 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma018787; Sun, 6 Dec 98 20:18:13 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id UAA14502; Sun, 6 Dec 1998 20:18:13 -0800 (PST) From: Archie Cobbs Message-Id: <199812070418.UAA14502@bubba.whistle.com> Subject: Re: getting to -Wunused In-Reply-To: <199812070405.PAA03585@godzilla.zeta.org.au> from Bruce Evans at "Dec 7, 98 03:05:39 pm" To: bde@zeta.org.au (Bruce Evans) Date: Sun, 6 Dec 1998 20:18:13 -0800 (PST) Cc: phk@critter.freebsd.dk, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Bruce Evans writes: > >By the way, I neede to add "-aout": > > Use `OBJFORMAT=aout kernxref.sh'. Surely there's a way to have the script detect OBJFORMAT automatically. How about this... if file vers.o | grep -q ELF; then OBJFORMAT="elf"; else OBJFORMAT="aout"; fi OBJFORMAT=${OBJFORMAT} nm -gon ... -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 02:37:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13253 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 02:37:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13248 for ; Mon, 7 Dec 1998 02:37:16 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA06405; Mon, 7 Dec 1998 10:07:51 GMT Date: Mon, 7 Dec 1998 10:07:51 +0000 (GMT) From: Doug Rabson To: zhihuizhang cc: hackers Subject: Re: Definition of kstack and PTDpde in locore.s 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 Sun, 6 Dec 1998, zhihuizhang wrote: > > Hi, Back in August, I posted a question about whether .set _xx, 30 in > assembly defines the value of xx or the address of xx (xx is the > counterpart of _xx in C). The response I got is that the address of xx is > 30. (note that xx without preceding "_" is used in C). > > So the address of PTDpde is PTD + (PTDI * PAGE_SIZE) (see locore.s). This > explains why the statement (unsigned)PTDpde & PG_FRAME gives the > "physical" address of the page directory page of the current address > space. We often use the following condition in pmap.c to see if the given > pmap uses the same page directory page as the curent address space. > > if ((((unsigned)pmap->pm_pdir[PTDPTDI]) & PG_FRAME) == > (((unsigned) PTDpde) & PG_FRAME)) { ... } > > So far, it is fine for me. Yesterday, I came across the symbol kstack > which is defined similary via the .set directive in locore.s. However, in > pmap.c, I find the following usage: > > m = pmap_allocpte(pmap, (vm_offset_t) kstack); > > So kstack must be a virtual address (I means its value). However, > according to my undestanding derived from PTDpde, the kstack should be > stored at the fixed virtual address (VADDR(KSTKPTDI, KSTKPTE)), its value > is another thing (should be initialized some where). But the > pmap_allocpte() statement clearly requires kstack's value and, I guess the > kernel stack for each process should be at the same VA. So, what does the > following statement do (in locore.s): > > .set _kstack,USRSTACK (note: USRSTACK = VADDR(KSTKPTDI, KSTKPTEOFF)) > > Does it give the address of kstack or value of kstack? The GAS only says > it gives the value of the symbol. > > I really have problem with mixed assembly and C programming when they > reference the same symbols (one with the preceding "_" and one without > "_"). I hope some one can clarify these stuff for me. > > Thanks a lot. Is this in the 2.2 source tree? We used to put the kernel stack of all processes at the same virtual address (traditionally the struct user for each process which includes the stack was always mapped in the same place and could be accessed using the global variable 'u'). I think that with the definition: .set _kstack, USRSTACK then from C, you could have: extern char kstack[]; assert(&kstack[0] == (char*) USRSTACK); i.e. to find the top of the kernel stack, take the address of kstack. For the 3.0 line, the virtual address of the struct user is different for each process which makes some things easier (debugging and probably SMP I guess) at the expense of using two pages of the kernel's virtual address space per process. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 03:14:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15755 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 03:14:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15749; Mon, 7 Dec 1998 03:14:29 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id MAA24342; Mon, 7 Dec 1998 12:13:19 +0100 (MET) Date: Mon, 7 Dec 1998 12:12:51 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Brian Cully cc: Doug Rabson , Kazutaka YOKOTA , sos@FreeBSD.ORG, hackers@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: major/minor numbers In-Reply-To: <19981203150137.D26279@kublai.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 > Has anybody looked at NetBSD's wscons? I believe it already has support > for multiple mice and keyboards, it's already cross-platform, and it > supports the USB devices. Kazu mentioned that he has working code, so let's look at that first. Support for the USB devices: I guess that I noticed, because I had to comment it out. And yes they have multiple console support. but if you can remember I put up a discussion on hackers about this and the general consensus was that multiple consoles is a bit silly, one because of cheap hardware and second because of the fact that more than one video card in a system seems to be less than straightforward, allthough it has been done. But why not have support for multiple consoles? I do not see why not. And which stack to use, I ahve no idea what the console stack on NetBSD looks like, so if you rip it out you might run into more trouble than a complete new stack would give you. So, Kazu, our star, shine some light on us. Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 03:21:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16112 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 03:21:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16097 for ; Mon, 7 Dec 1998 03:21:11 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id MAA24580 for ; Mon, 7 Dec 1998 12:21:31 +0100 (MET) Date: Mon, 7 Dec 1998 12:21:02 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD hackers mailing list Subject: Re: major/minor numbers 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 > Oh, you are right. You mean something like: > > device mse0 at isa? ... # bus mouse > device psm0 at isa? ... # PS/2 mouse > > controller uhci0 > controller usb0 > device ums0 > > pseudo-device mouse 3 # or more, if we like > pseudo-device kbd 2 Why is this? (same for keyboard) We don't need to specify this I believe. Dynamic allocation would do fine I think, especially if you only do a hand-off. But a much better solution would be to create a mouse bus attaching to the root bus, and connect all the mice to that one. Unit numbers will be increasing, so we will only need one major number for that one, one naming scheme, like mouse[0-9]+, in /dev. Sysmouse could integrate with that as well. Dynamic attachment and detachment is straightforward or automatic, implemented in the mouse bus. Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 06:07:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01026 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 06:07:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01021 for ; Mon, 7 Dec 1998 06:07:07 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id JAA11093; Mon, 7 Dec 1998 09:06:57 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id JAA00289; Mon, 7 Dec 1998 09:41:06 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id JAA26369; Mon, 7 Dec 1998 09:01:45 -0500 (EST) Date: Mon, 7 Dec 1998 09:01:45 -0500 (EST) From: Thomas David Rivers Message-Id: <199812071401.JAA26369@lakes.dignus.com> To: marcs@znep.com, nate@mt.sri.com Subject: Re: TCP bug Cc: dillon@apollo.backplane.com, eischen@vigrid.com, hackers@FreeBSD.ORG, luigi@labinfo.iet.unipi.it In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok - As I understood this discussion (which seemed clear to me); the problem was that an internal node (behind the firewall) couldn't get to some web sites because of fragmentation issues. The low MTU at the firewall/gateway broke path MTU discovery.. So - a possible work-around to the problem should be to set the SL/IP MTU at 1500 at the gateway - right? Well - I tried that, and I still can't (from an internal node) "see" http://www.aol.com (it just waits forever trying to receive some 40K something-or-other). But, I can rlogin to the gateway and "see" it just fine. Did I misunderstand? - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 06:51:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04440 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 06:51:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA04152 for ; Mon, 7 Dec 1998 06:48:09 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id QAA13393; Mon, 7 Dec 1998 16:36:07 +0200 (EET) (envelope-from ru) Date: Mon, 7 Dec 1998 16:36:06 +0200 From: Ruslan Ermilov To: Thomas David Rivers Cc: marcs@znep.com, nate@mt.sri.com, dillon@apollo.backplane.com, eischen@vigrid.com, hackers@FreeBSD.ORG, luigi@labinfo.iet.unipi.it Subject: Re: TCP bug Message-ID: <19981207163606.A7575@ucb.crimea.ua> Mail-Followup-To: Thomas David Rivers , marcs@znep.com, nate@mt.sri.com, dillon@apollo.backplane.com, eischen@vigrid.com, hackers@FreeBSD.ORG, luigi@labinfo.iet.unipi.it References: <199812071401.JAA26369@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.17i In-Reply-To: <199812071401.JAA26369@lakes.dignus.com>; from Thomas David Rivers on Mon, Dec 07, 1998 at 09:01:45AM -0500 X-Operating-System: FreeBSD 2.2.7-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 07, 1998 at 09:01:45AM -0500, Thomas David Rivers wrote: > Ok - > > As I understood this discussion (which seemed clear to me); the > problem was that an internal node (behind the firewall) couldn't > get to some web sites because of fragmentation issues. The low > MTU at the firewall/gateway broke path MTU discovery.. No, the problem is not with low MTU, but because AOL is blocking ICMP: PING aol.com (152.163.210.29): 56 data bytes 36 bytes from www2-r10-P5-0-0.tpopr-rri.aol.com (152.163.133.6): Communication prohibited by filter Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 5400 68cb 0 0000 ea 01 894d 194.93.177.113 152.163.210.29 ^C --- aol.com ping statistics --- 22 packets transmitted, 0 packets received, 100% packet loss > > So - a possible work-around to the problem should be to set the > SL/IP MTU at 1500 at the gateway - right? Does your router run FreeBSD? If yes, how did you change MTU on SLIP? -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 06:52:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04533 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 06:52:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA04525 for ; Mon, 7 Dec 1998 06:52:18 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id JAA15953; Mon, 7 Dec 1998 09:52:07 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id KAA00348; Mon, 7 Dec 1998 10:32:18 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id JAA00490; Mon, 7 Dec 1998 09:52:38 -0500 (EST) Date: Mon, 7 Dec 1998 09:52:38 -0500 (EST) From: Thomas David Rivers Message-Id: <199812071452.JAA00490@lakes.dignus.com> To: rivers@dignus.com, ru@ucb.crimea.ua Subject: Re: TCP bug Cc: dillon@apollo.backplane.com, eischen@vigrid.com, hackers@FreeBSD.ORG, luigi@labinfo.iet.unipi.it, marcs@znep.com, nate@mt.sri.com In-Reply-To: <19981207163606.A7575@ucb.crimea.ua> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Mon, Dec 07, 1998 at 09:01:45AM -0500, Thomas David Rivers wrote: > > Ok - > > > > As I understood this discussion (which seemed clear to me); the > > problem was that an internal node (behind the firewall) couldn't > > get to some web sites because of fragmentation issues. The low > > MTU at the firewall/gateway broke path MTU discovery.. > > No, the problem is not with low MTU, but because AOL is blocking ICMP: > > PING aol.com (152.163.210.29): 56 data bytes > 36 bytes from www2-r10-P5-0-0.tpopr-rri.aol.com (152.163.133.6): Communication prohibited by filter > Vr HL TOS Len ID Flg off TTL Pro cks Src Dst > 4 5 00 5400 68cb 0 0000 ea 01 894d 194.93.177.113 152.163.210.29 > > ^C > --- aol.com ping statistics --- > 22 packets transmitted, 0 packets received, 100% packet loss Which messes up the Path MTU discovery... or so I thought... > > > > > So - a possible work-around to the problem should be to set the > > SL/IP MTU at 1500 at the gateway - right? > > Does your router run FreeBSD? If yes, how did you change MTU on SLIP? Yes, it's a 3.0-RELEASE box. To change the MTU I simply specified mtu 1500 on the ifconfig line for SL/IP. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 07:37:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09362 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 07:37:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08844 for ; Mon, 7 Dec 1998 07:33:01 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id RAA25067; Mon, 7 Dec 1998 17:30:11 +0200 (EET) (envelope-from ru) Date: Mon, 7 Dec 1998 17:30:10 +0200 From: Ruslan Ermilov To: Thomas David Rivers Cc: hackers@FreeBSD.ORG Subject: Re: TCP bug Message-ID: <19981207173010.A25022@ucb.crimea.ua> Mail-Followup-To: Thomas David Rivers , hackers@FreeBSD.ORG References: <19981207163606.A7575@ucb.crimea.ua> <199812071452.JAA00490@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.17i In-Reply-To: <199812071452.JAA00490@lakes.dignus.com>; from Thomas David Rivers on Mon, Dec 07, 1998 at 09:52:38AM -0500 X-Operating-System: FreeBSD 2.2.7-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 07, 1998 at 09:52:38AM -0500, Thomas David Rivers wrote: > Yes, it's a 3.0-RELEASE box. To change the MTU I simply specified > mtu 1500 on the ifconfig line for SL/IP. And your peer's MTU is equal to 1500 too, right? -- Ruslan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 07:40:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09789 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 07:40:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09783 for ; Mon, 7 Dec 1998 07:40:38 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id KAA21924; Mon, 7 Dec 1998 10:40:44 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id LAA00431; Mon, 7 Dec 1998 11:20:57 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id KAA01029; Mon, 7 Dec 1998 10:41:16 -0500 (EST) Date: Mon, 7 Dec 1998 10:41:16 -0500 (EST) From: Thomas David Rivers Message-Id: <199812071541.KAA01029@lakes.dignus.com> To: rivers@dignus.com, ru@ucb.crimea.ua Subject: Re: TCP bug Cc: hackers@FreeBSD.ORG In-Reply-To: <19981207173010.A25022@ucb.crimea.ua> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Dec 07, 1998 at 09:52:38AM -0500, Thomas David Rivers wrote: > > Yes, it's a 3.0-RELEASE box. To change the MTU I simply specified > > mtu 1500 on the ifconfig line for SL/IP. > > And your peer's MTU is equal to 1500 too, right? > > -- > Ruslan > Yep - I checked with them first. At least, my ISP claimed it was... - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 08:07:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12779 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 08:07:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12325 for ; Mon, 7 Dec 1998 08:05:08 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id RAA01333; Mon, 7 Dec 1998 17:58:05 +0200 (EET) (envelope-from ru) Date: Mon, 7 Dec 1998 17:58:04 +0200 From: Ruslan Ermilov To: Thomas David Rivers Cc: hackers@FreeBSD.ORG Subject: Re: TCP bug Message-ID: <19981207175804.A1183@ucb.crimea.ua> Mail-Followup-To: Thomas David Rivers , hackers@FreeBSD.ORG References: <19981207173010.A25022@ucb.crimea.ua> <199812071541.KAA01029@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.17i In-Reply-To: <199812071541.KAA01029@lakes.dignus.com>; from Thomas David Rivers on Mon, Dec 07, 1998 at 10:41:16AM -0500 X-Operating-System: FreeBSD 2.2.7-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 07, 1998 at 10:41:16AM -0500, Thomas David Rivers wrote: > > On Mon, Dec 07, 1998 at 09:52:38AM -0500, Thomas David Rivers wrote: > > > Yes, it's a 3.0-RELEASE box. To change the MTU I simply specified > > > mtu 1500 on the ifconfig line for SL/IP. > > > > And your peer's MTU is equal to 1500 too, right? > > > > -- > > Ruslan > > > > Yep - I checked with them first. At least, my ISP claimed it was... > Umm. Have you tried to disable PMTU on your FreeBSD box? -- Ruslan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 08:07:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12797 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 08:07:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12789 for ; Mon, 7 Dec 1998 08:07:10 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id LAA05430 for ; Mon, 7 Dec 1998 11:08:48 GMT Message-Id: <199812071108.LAA05430@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 07 Dec 1998 11:06:28 -0500 To: hackers@FreeBSD.ORG From: Dennis Subject: 3.0-RELEASE clear source? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG there is no source to the /usr/bin/clear program, and the binary provided in the distribution complains about "bad achitecture". Is this program antiquated or is this an oversite? DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 08:10:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13153 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 08:10:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13148 for ; Mon, 7 Dec 1998 08:10:38 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id LAA25660; Mon, 7 Dec 1998 11:10:43 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id LAA00463; Mon, 7 Dec 1998 11:50:57 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id LAA01157; Mon, 7 Dec 1998 11:11:16 -0500 (EST) Date: Mon, 7 Dec 1998 11:11:16 -0500 (EST) From: Thomas David Rivers Message-Id: <199812071611.LAA01157@lakes.dignus.com> To: rivers@dignus.com, ru@ucb.crimea.ua Subject: Re: TCP bug Cc: hackers@FreeBSD.ORG In-Reply-To: <19981207175804.A1183@ucb.crimea.ua> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Mon, Dec 07, 1998 at 10:41:16AM -0500, Thomas David Rivers wrote: > > > On Mon, Dec 07, 1998 at 09:52:38AM -0500, Thomas David Rivers wrote: > > > > Yes, it's a 3.0-RELEASE box. To change the MTU I simply specified > > > > mtu 1500 on the ifconfig line for SL/IP. > > > > > > And your peer's MTU is equal to 1500 too, right? > > > > > > -- > > > Ruslan > > > > > > > Yep - I checked with them first. At least, my ISP claimed it was... > > > > Umm. Have you tried to disable PMTU on your FreeBSD box? > Nope.. do you mean on the interior nodes or the gateway - or both? (Some of my interior nodes aren't FreeBSD... so I may not have that option.) And, I thought I would find something about that in the sysctls - say, net.inet.XXX - but nothing jumps out at me... which sysctl would disable MTU-D? - Thanks! - - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 08:28:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14613 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 08:28:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14605 for ; Mon, 7 Dec 1998 08:28:44 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id AAA19880; Tue, 8 Dec 1998 00:28:15 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812071628.AAA19880@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson cc: zhihuizhang , hackers Subject: Re: Definition of kstack and PTDpde in locore.s In-reply-to: Your message of "Mon, 07 Dec 1998 10:07:51 GMT." Date: Tue, 08 Dec 1998 00:28:11 +0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > On Sun, 6 Dec 1998, zhihuizhang wrote: [..] > > Is this in the 2.2 source tree? We used to put the kernel stack of all > processes at the same virtual address (traditionally the struct user for > each process which includes the stack was always mapped in the same place > and could be accessed using the global variable 'u'). I think that with > the definition: > > .set _kstack, USRSTACK > > then from C, you could have: > > extern char kstack[]; > > assert(&kstack[0] == (char*) USRSTACK); > > i.e. to find the top of the kernel stack, take the address of kstack. > > For the 3.0 line, the virtual address of the struct user is different for > each process which makes some things easier (debugging and probably SMP I > guess) at the expense of using two pages of the kernel's virtual address > space per process. For 2.2, we have it mapped twice, once at the fixed virtual address in process space, as well as the two pages in kernel space. The 3.0 change was to remove the stack from the user space in order to allow address space sharing for thread support. However, this probably has to change. What we really need is a fixed kernel address space for the kstack, and an alternate kstack to be mappable (think ptrace etc, registers on another process at the time of a trap may (I think) be on it's kstack. This could be wrong, it's a while since I looked). This way an address space could be shared thousands of times without using '"thousands" times 2' pages of KVM space. This would go part of the way towards solving a few outstanding problems with address space sharing (rfork/ threading) with SMP too. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 08:30:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15011 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 08:30:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14971 for ; Mon, 7 Dec 1998 08:30:06 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id LAA23286; Mon, 7 Dec 1998 11:33:47 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 7 Dec 1998 11:33:47 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Dennis cc: hackers@FreeBSD.ORG Subject: Re: 3.0-RELEASE clear source? In-Reply-To: <199812071108.LAA05430@etinc.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 it's a shell script that wraps 'tput' #!/bin/sh - # # Copyright (c) 1989, 1993 # The Regents of the University of California. All rights reserved. # ...... exec tput clear Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Mon, 7 Dec 1998, Dennis wrote: > > there is no source to the /usr/bin/clear program, and the binary > provided in the distribution complains about "bad achitecture". > > Is this program antiquated or is this an oversite? > > DB > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 08:53:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17765 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 08:53:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17607 for ; Mon, 7 Dec 1998 08:50:05 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id SAA09918; Mon, 7 Dec 1998 18:43:13 +0200 (EET) (envelope-from ru) Date: Mon, 7 Dec 1998 18:43:12 +0200 From: Ruslan Ermilov To: Thomas David Rivers Cc: hackers@FreeBSD.ORG Subject: Re: TCP bug Message-ID: <19981207184312.A7011@ucb.crimea.ua> Mail-Followup-To: Thomas David Rivers , hackers@FreeBSD.ORG References: <19981207175804.A1183@ucb.crimea.ua> <199812071611.LAA01157@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.17i In-Reply-To: <199812071611.LAA01157@lakes.dignus.com>; from Thomas David Rivers on Mon, Dec 07, 1998 at 11:11:16AM -0500 X-Operating-System: FreeBSD 2.2.7-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 07, 1998 at 11:11:16AM -0500, Thomas David Rivers wrote: > > Umm. Have you tried to disable PMTU on your FreeBSD box? > > > > Nope.. do you mean on the interior nodes or the gateway - or both? > (Some of my interior nodes aren't FreeBSD... so I may not have that option.) > I mean the FreeBSD box you are sitting on and from which you can't access www.aol.com. > And, I thought I would find something about that in the sysctls - say, > net.inet.XXX - but nothing jumps out at me... which sysctl would disable > MTU-D? MTU can be disabled on per-route basis. It is neither clear, nor documented. This can be done by locking MTU on a route. For example, if you want to disable PMTU-D on default, you should say: # route change default -lock -mtu 1500 (or whatever you have it set to) ! Note, that if you specify -mtu without parameter (this is what came to my ! mind first), route command will coredump. Now, you should be able to check that PMTU-D is disabled by: a) ``route get default'' will show mtu as 1500L, i.e. 1500 and locked; b) ``route get www.aol.com'' will show the same mtu, because this route is cloned from the default (or maybe you have direct route to AOL?); c) ``tcpdump'' won't show DF bit in outgoing packets (this is for sure). BR, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 09:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18658 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 09:01:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18653 for ; Mon, 7 Dec 1998 09:01:41 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA10329; Mon, 7 Dec 1998 09:57:04 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA02647; Mon, 7 Dec 1998 09:57:02 -0700 Date: Mon, 7 Dec 1998 09:57:02 -0700 Message-Id: <199812071657.JAA02647@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Thomas David Rivers Cc: ru@ucb.crimea.ua, dillon@apollo.backplane.com, eischen@vigrid.com, hackers@FreeBSD.ORG, luigi@labinfo.iet.unipi.it, marcs@znep.com, nate@mt.sri.com Subject: Re: TCP bug In-Reply-To: <199812071452.JAA00490@lakes.dignus.com> References: <19981207163606.A7575@ucb.crimea.ua> <199812071452.JAA00490@lakes.dignus.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > So - a possible work-around to the problem should be to set the > > > SL/IP MTU at 1500 at the gateway - right? > > > > Does your router run FreeBSD? If yes, how did you change MTU on SLIP? > > Yes, it's a 3.0-RELEASE box. To change the MTU I simply specified > mtu 1500 on the ifconfig line for SL/IP. You have to set the MTU on the 'incoming' line for slip. I use sliplogin on the incoming side, so in /etc/sliphome/slip.login I have # Bringup the line /sbin/ifconfig sl$1 inet $4 $5 netmask $6 msu 1500 Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 10:36:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29463 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 10:36:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29437 for ; Mon, 7 Dec 1998 10:36:42 -0800 (PST) (envelope-from guido@gvr.org) Received: (from guido@localhost) by gvr.gvr.org (8.8.8/8.8.5) id TAA18222; Mon, 7 Dec 1998 19:35:25 +0100 (MET) Message-ID: <19981207193525.A18185@gvr.org> Date: Mon, 7 Dec 1998 19:35:25 +0100 From: Guido van Rooij To: Jun-ichiro itojun Itoh Cc: "Jordan K. Hubbard" , Andreas Klemm , Eivind Eklund , hackers@FreeBSD.ORG Subject: Re: Can we just come to a decision on IPv6 and IPSec? References: <19981203191001.A28037@gvr.org> <27487.912737451@coconut.itojun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <27487.912737451@coconut.itojun.org>; from Jun-ichiro itojun Itoh on Fri, Dec 04, 1998 at 11:10:51AM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 04, 1998 at 11:10:51AM +0900, Jun-ichiro itojun Itoh wrote: > > One thing we don't implement intentionally is automatic tunnelling > (packets to ::10.1.1.1 automatically tunnelled over IPv6-over-IPv4 > tunnel to 10.1.1.1). Hmm..what does happen when I have a IPV6/V4 host that has an IPV6 native address (so no V4 compatible address) that wants to communicate to an IPv4 host? Do I need to set up IPV4 specific routes to a dual stack machine that does the tunneling for me? -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 11:07:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01604 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 11:07:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from turmeric.itojun.org (ietf-177-42.mtg.ietf.org [198.67.177.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01599 for ; Mon, 7 Dec 1998 11:07:50 -0800 (PST) (envelope-from itojun@turmeric.itojun.org) Received: from localhost (localhost [127.0.0.1]) by turmeric.itojun.org (8.8.5/3.7W) with ESMTP id EAA02047; Tue, 8 Dec 1998 04:07:31 +0900 (JST) To: Guido van Rooij cc: hackers@FreeBSD.ORG reply-to: freebsd-net@FreeBSD.ORG In-reply-to: guido's message of Mon, 07 Dec 98 19:35:25 +0100. <19981207193525.A18185@gvr.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: IPv6-over-IPv4 auto tunnel cc: itojun@itojun.org From: Jun-ichiro itojun Itoh Date: Tue, 08 Dec 1998 04:07:31 +0900 Message-ID: <2045.913057651@turmeric.itojun.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think this may not fit well to hackers, so I added reply-to: freebsd-net into headers. >> One thing we don't implement intentionally is automatic tunnelling >> (packets to ::10.1.1.1 automatically tunnelled over IPv6-over-IPv4 >> tunnel to 10.1.1.1). >Hmm..what does happen when I have a IPV6/V4 host that has an IPV6 >native address (so no V4 compatible address) that wants to communicate >to an IPv4 host? Do I need to set up IPV4 specific routes to >a dual stack machine that does the tunneling for me? Your story has nothing to do with auto tunnel. Automatic tunnel (::10.1.1.1) is only for communication between two IPv4/v6 dual stack hosts. For a IPv6-only host (or IPv4/v6 dual stack host without IPv4 address) to communicate with IPv4 host, you need to have IPv6-to-IPv4 translator (TCP relay server like socks or KAME FAITH, or web proxy) between two. There's no magical way. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 11:27:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03343 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 11:27:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp3.erols.com (smtp3.erols.com [207.172.3.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03338 for ; Mon, 7 Dec 1998 11:27:02 -0800 (PST) (envelope-from shmit@natasya.noc.erols.net) Received: from natasya.noc.erols.net (natasya.noc.erols.net [207.172.25.236]) by smtp3.erols.com (8.8.8/8.8.5) with ESMTP id OAA13538; Mon, 7 Dec 1998 14:26:58 -0500 (EST) Received: (from shmit@localhost) by natasya.noc.erols.net (8.9.1/8.9.1) id OAA01953; Mon, 7 Dec 1998 14:26:58 -0500 (EST) Message-ID: <19981207142658.P26279@kublai.com> Date: Mon, 7 Dec 1998 14:26:58 -0500 From: Brian Cully To: tj-fbsd@funbox.demon.co.uk, freebsd-hackers@FreeBSD.ORG Subject: Re: Sysconfig, or, the SysV vs. BSD init wars Reply-To: shmit@kublai.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from tj-fbsd@funbox.demon.co.uk on Sat, Dec 05, 1998 at 03:54:17PM +0000 X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 05, 1998 at 03:54:17PM +0000, tj-fbsd@funbox.demon.co.uk wrote: > However, I find myself thinking that shell scripts (or a monolithic > script) are very flexible, easy to alter and to check, and more than > adequate for the job. For my part, I don't see the necessity (or, I'm > afraid, the desirability) for changing from script(s). The problem with shell scripts is that doing dependency checking and DAG traversal is difficult (to say the least). There's also no good way of grouping things that belong together (short of `linux_exec', `linux_foo', etc.,.). Plus, you have a hard time turning a shell script into a replacement for init (which is something that you can do with what I've done). I wish I could have kept the shell, but it's not really powerful enough for what I want to do. -- Brian Cully Macintosh -- we might not get everything right, but at least we knew the century was going to end. -- Douglas Adams, on the Y2K problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 11:52:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06519 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 11:52:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alive.znep.com (207-178-54-226.go2net.com [207.178.54.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06475 for ; Mon, 7 Dec 1998 11:52:12 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id LAA00142; Mon, 7 Dec 1998 11:47:15 -0800 (PST) (envelope-from marcs@znep.com) Date: Mon, 7 Dec 1998 11:47:15 -0800 (PST) From: Marc Slemko To: Ruslan Ermilov , Thomas David Rivers cc: hackers@FreeBSD.ORG Subject: Re: TCP bug In-Reply-To: <19981207163606.A7575@ucb.crimea.ua> 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, 7 Dec 1998, Ruslan Ermilov wrote: > On Mon, Dec 07, 1998 at 11:11:16AM -0500, Thomas David Rivers wrote: > > > Umm. Have you tried to disable PMTU on your FreeBSD box? > > > > > > > Nope.. do you mean on the interior nodes or the gateway - or both? > > (Some of my interior nodes aren't FreeBSD... so I may not have that option.) > > > > I mean the FreeBSD box you are sitting on and from which you can't access > www.aol.com. That isn't overly likely to be an issue in this case. A tcpdump will show for sure the ack for that packet is getting back or not. On Mon, 7 Dec 1998, Thomas David Rivers wrote: > > On Mon, Dec 07, 1998 at 09:52:38AM -0500, Thomas David Rivers wrote: > > > Yes, it's a 3.0-RELEASE box. To change the MTU I simply specified > > > mtu 1500 on the ifconfig line for SL/IP. > > > > And your peer's MTU is equal to 1500 too, right? > > > > -- > > Ruslan > > > > Yep - I checked with them first. At least, my ISP claimed it was... Use ppp. It really makes stuff like this much easier since it actually supports negotiation for things. To check if the MTU is 1500, use: ping -s 1472 host-on-the-other-size while doing a tcpdump. Look to see if the response is fragmented or not. If it is fragmented, then the MTU isn't 1500. Note that someone stupidly changed -s so you have to be root to use it, which makes it a PITA to use ping for trying to debug network problems and really doesn't stop someone who wants to flood someone with traffic. On Mon, 7 Dec 1998, Thomas David Rivers wrote: > Ok - > > As I understood this discussion (which seemed clear to me); the > problem was that an internal node (behind the firewall) couldn't > get to some web sites because of fragmentation issues. The low > MTU at the firewall/gateway broke path MTU discovery.. > > > So - a possible work-around to the problem should be to set the > SL/IP MTU at 1500 at the gateway - right? That is one possible workaround if you are seeing the same problem. Does: marcs@alive:~$ telnet www.aol.com 80 Trying 152.163.210.28... Connected to aol.com. Escape character is '^]'. HEAD / HTTP/1.0 * * HTTP/1.0 200 OK MIME-Version: 1.0 Date: Mon, 07 Dec 1998 19:47:01 GMT Server: NaviServer/2.0 AOLserver/2.3 Content-Type: text/html Content-Length: 41177 Last-Modified: Mon, 07 Dec 1998 17:21:49 GMT Version: Mon, 07 Dec 1998 17:21:49 GMT Connection closed by foreign host. work? The lines with the * are what you enter, the second one is blank. On Mon, 7 Dec 1998, Ruslan Ermilov wrote: > On Mon, Dec 07, 1998 at 09:01:45AM -0500, Thomas David Rivers wrote: > > Ok - > > > > As I understood this discussion (which seemed clear to me); the > > problem was that an internal node (behind the firewall) couldn't > > get to some web sites because of fragmentation issues. The low > > MTU at the firewall/gateway broke path MTU discovery.. > > No, the problem is not with low MTU, but because AOL is blocking ICMP: > > PING aol.com (152.163.210.29): 56 data bytes > 36 bytes from www2-r10-P5-0-0.tpopr-rri.aol.com (152.163.133.6): Communication prohibited by filter > Vr HL TOS Len ID Flg off TTL Pro cks Src Dst > 4 5 00 5400 68cb 0 0000 ea 01 894d 194.93.177.113 152.163.210.29 > > ^C > --- aol.com ping statistics --- > 22 packets transmitted, 0 packets received, 100% packet loss While the blame should be assigned to someone who is filtering, it is important to note that just because you can't ping someone doesn't mean they are filtering all ICMP. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 12:09:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10036 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 12:09:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA10028 for ; Mon, 7 Dec 1998 12:09:09 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zn6xg-0002vt-00; Mon, 7 Dec 1998 13:08:52 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id NAA05124 for ; Mon, 7 Dec 1998 13:07:30 -0700 (MST) Message-Id: <199812072007.NAA05124@harmony.village.org> To: hackers@FreeBSD.ORG Subject: How could this work? Date: Mon, 07 Dec 1998 13:07:30 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was looking at the libretto confin program that was just ported to FreeBSD via the ports mechanism. It has code that looks like: movl 8(%ebp),%eax movl 12(%ebp),%ebx movl 16(%ebp),%ecx inb $0x0b2,%al /* invoke SMI */ How the heck can that work? I'm confused... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 12:32:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12384 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 12:32:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m2-22-dbn.dial-up.net [196.34.155.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12374 for ; Mon, 7 Dec 1998 12:32:37 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA00262; Mon, 7 Dec 1998 22:31:10 +0200 (SAT) From: Robert Nordier Message-Id: <199812072031.WAA00262@ceia.nordier.com> Subject: Re: How could this work? In-Reply-To: <199812072007.NAA05124@harmony.village.org> from Warner Losh at "Dec 7, 98 01:07:30 pm" To: imp@village.org (Warner Losh) Date: Mon, 7 Dec 1998 22:31:02 +0200 (SAT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Warner Losh wrote: > I was looking at the libretto confin program that was just ported to > FreeBSD via the ports mechanism. It has code that looks like: > > movl 8(%ebp),%eax > movl 12(%ebp),%ebx > movl 16(%ebp),%ecx > inb $0x0b2,%al /* invoke SMI */ > > How the heck can that work? I'm confused... IIRC, reads and writes involving port 0xb2 are done for their side-effects (to cause an SMI, put CPU into sleep mode, etc). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 12:33:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12503 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 12:33:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA12498 for ; Mon, 7 Dec 1998 12:33:49 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zn7Lf-0002wy-00; Mon, 7 Dec 1998 13:33:39 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id NAA05466; Mon, 7 Dec 1998 13:32:18 -0700 (MST) Message-Id: <199812072032.NAA05466@harmony.village.org> To: Robert Nordier Subject: Re: How could this work? Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 07 Dec 1998 22:31:02 +0200." <199812072031.WAA00262@ceia.nordier.com> References: <199812072031.WAA00262@ceia.nordier.com> Date: Mon, 07 Dec 1998 13:32:18 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812072031.WAA00262@ceia.nordier.com> Robert Nordier writes: : IIRC, reads and writes involving port 0xb2 are done for their : side-effects (to cause an SMI, put CPU into sleep mode, etc). I guess I'm asking how this happens? Can you provide more details, or a pointer to same? Many thanks... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 12:49:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14138 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 12:49:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA14133 for ; Mon, 7 Dec 1998 12:49:02 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id PAA09500; Mon, 7 Dec 1998 15:48:33 -0500 Date: Mon, 7 Dec 1998 15:48:33 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@FreeBSD.ORG Subject: write combining memory on pci 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 any good ideas on how to turn this on in 3.0 for a given memory address range? Thanks ron Ron Minnich |"Using Windows NT, which is known to have some rminnich@sarnoff.com | failure modes, on a warship is similar to hoping (609)-734-3120 | that luck will be in our favor"- A. Digiorgio ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 13:05:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15528 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 13:05:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15521 for ; Mon, 7 Dec 1998 13:05:49 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id OAA07499; Mon, 7 Dec 1998 14:05:34 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812072105.OAA07499@panzer.plutotech.com> Subject: Re: write combining memory on pci In-Reply-To: from "Ron G. Minnich" at "Dec 7, 98 03:48:33 pm" To: rminnich@Sarnoff.COM (Ron G. Minnich) Date: Mon, 7 Dec 1998 14:05:34 -0700 (MST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Ron G. Minnich wrote... > any good ideas on how to turn this on in 3.0 for a given memory address > range? Isn't there usually a BIOS option to do that? I think it's called USWC or something like that. (Uniform Speculative Write Combining?) I don't think it generally covers a specific address range, though. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 13:09:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16237 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 13:09:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16232 for ; Mon, 7 Dec 1998 13:09:04 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id VAA60074; Mon, 7 Dec 1998 21:08:46 GMT Message-ID: <366C43DD.A7DA16F4@tdx.co.uk> Date: Mon, 07 Dec 1998 21:08:45 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" CC: "Ron G. Minnich" , hackers@FreeBSD.ORG Subject: Re: write combining memory on pci References: <199812072105.OAA07499@panzer.plutotech.com> 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: > > Ron G. Minnich wrote... > > any good ideas on how to turn this on in 3.0 for a given memory address > > range? > > Isn't there usually a BIOS option to do that? I think it's called USWC or > something like that. (Uniform Speculative Write Combining?) I don't think > it generally covers a specific address range, though. Both my P-Pro systems have this option, and AFAIK it worked as above (i.e. 'all on' or 'all off')... Win NT survives with it on, until I try to use the sound card, and FreeBSD, Linux & Win'95 all die within seconds with it on... Which is a bit of a pitty, as I also seem to remember reading it gives a huge performance win on writes ;-) - Maybe there is such a thing as 'too fast'... -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 13:14:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16795 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 13:14:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA16788 for ; Mon, 7 Dec 1998 13:14:12 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id QAA09577; Mon, 7 Dec 1998 16:14:08 -0500 Date: Mon, 7 Dec 1998 16:14:08 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@FreeBSD.ORG Subject: Re: write combining memory on pci In-Reply-To: <366C43DD.A7DA16F4@tdx.co.uk> 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, 7 Dec 1998, Karl Pielorz wrote: > Both my P-Pro systems have this option, and AFAIK it worked as above (i.e. > 'all on' or 'all off')... Win NT survives with it on, until I try to use the > sound card, and FreeBSD, Linux & Win'95 all die within seconds with it on Hmm, that is bad news. I have some cards from a company that only run fast with write combining turned ON. However, if they crash the OS with it on, it might not be such a good deal. Guess I'll have to use the cards as a master, not a target for PIO writes. As ever, the rule with PCI: don't get the CPU involved in data transfer :-) > Which is a bit of a pitty, as I also seem to remember reading it gives a huge > performance win on writes ;-) - Maybe there is such a thing as 'too fast'... something on order of at least 2x. It would be nice to have ... ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 13:41:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19693 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 13:41:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19676 for ; Mon, 7 Dec 1998 13:41:05 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id VAA60305; Mon, 7 Dec 1998 21:40:57 GMT Message-ID: <366C4B68.DB46F3CF@tdx.co.uk> Date: Mon, 07 Dec 1998 21:40:56 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "Ron G. Minnich" CC: hackers@FreeBSD.ORG Subject: Re: write combining memory on pci References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Ron G. Minnich" wrote: > Hmm, that is bad news. I have some cards from a company that only run fast > with write combining turned ON. However, if they crash the OS with it on, > it might not be such a good deal. > > Guess I'll have to use the cards as a master, not a target for PIO > writes. As ever, the rule with PCI: don't get the CPU involved in data > transfer :-) Remember - this was with 'indiscriminate' USWC, you may be able to get away with it if you can enable it for certain regions only... Maybe a trip to the Intel website, or a look through the fastvid code (which will turn on Write Combining + other bits for only certain areas might help)... > something on order of at least 2x. It would be nice to have ... Yeah, I also read it does the equivalent of 'fire and forget' for memory, i.e. you can have overlapping multiple writes arriving out of order... OK, for video - who cares :) ... But for other large memory regions? - Could be fun ;-) -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 13:44:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20127 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 13:44:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20114 for ; Mon, 7 Dec 1998 13:44:26 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA12451 for ; Mon, 7 Dec 1998 14:44:22 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA06810; Mon, 7 Dec 1998 14:44:22 -0700 Date: Mon, 7 Dec 1998 14:44:22 -0700 Message-Id: <199812072144.OAA06810@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hackers@FreeBSD.ORG Subject: Wchar support in FreeBSD X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any 3rd party libraries that support the 'wchar' stuff? IBM just made it's Jikes compiler available as an 'Open Source Project', and I'd like to make a FreeBSD-native version. However, it requires the native wchar support (which exists in Win32, Solaris, and Linux), but not in FreeBSD. Any clues how I can easily get around this? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 13:52:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21019 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 13:52:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21005 for ; Mon, 7 Dec 1998 13:52:14 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Mon, 7 Dec 1998 21:50:11 -0000 Message-ID: From: Paul Richards To: "'Ron G. Minnich'" , hackers@FreeBSD.ORG Subject: RE: write combining memory on pci Date: Mon, 7 Dec 1998 21:50:01 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Ron G. Minnich [mailto:rminnich@Sarnoff.COM] > Sent: Monday, December 07, 1998 9:14 PM > To: hackers@FreeBSD.ORG > Subject: Re: write combining memory on pci > > > > On Mon, 7 Dec 1998, Karl Pielorz wrote: > > Both my P-Pro systems have this option, and AFAIK it worked > as above (i.e. > > 'all on' or 'all off')... Win NT survives with it on, until > I try to use the > > sound card, and FreeBSD, Linux & Win'95 all die within > seconds with it on > > Hmm, that is bad news. I have some cards from a company that > only run fast > with write combining turned ON. However, if they crash the OS > with it on, > it might not be such a good deal. I've got it turned on in my BIOS and it's not done any harm. It's an Asus P2B-DS with 2 P-II 300s in it running FreeBSD current. Not sure if anything is making use of this feature though. Paul Richards Ph.D. Originative Solutions Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 14:07:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22631 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 14:07:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ceia.nordier.com (m2-27-dbn.dial-up.net [196.34.155.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22614 for ; Mon, 7 Dec 1998 14:07:34 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id AAA01520; Tue, 8 Dec 1998 00:05:53 +0200 (SAT) From: Robert Nordier Message-Id: <199812072205.AAA01520@ceia.nordier.com> Subject: Re: How could this work? In-Reply-To: <199812072032.NAA05466@harmony.village.org> from Warner Losh at "Dec 7, 98 01:32:18 pm" To: imp@village.org (Warner Losh) Date: Tue, 8 Dec 1998 00:05:45 +0200 (SAT) Cc: rnordier@nordier.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Warner Losh wrote: > In message <199812072031.WAA00262@ceia.nordier.com> Robert Nordier writes: > : IIRC, reads and writes involving port 0xb2 are done for their > : side-effects (to cause an SMI, put CPU into sleep mode, etc). > > I guess I'm asking how this happens? Can you provide more details, or > a pointer to same? Any read from the APM control register (port 0xb2 for certain chipsets) causes STPCLK# to be asserted, and the CPU goes into Stop-Grant State, from where it can enter Sleep State or return to Normal State. The Pentium II Processor Developer's Manual, Chapter 7, covers SMI#, STPCLK#, SLP#, etc; and there's a description of SMM in Vol. III of the Intel Architecture Software Developer's Manual. (Both available in acrobat format at the Intel web site literature center.) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 14:07:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22648 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 14:07:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22618 for ; Mon, 7 Dec 1998 14:07:35 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.1/8.6.9) with ESMTP id WAA03166; Mon, 7 Dec 1998 22:49:59 +0100 (CET) Message-Id: <199812072149.WAA03166@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: "Ron G. Minnich" cc: hackers@FreeBSD.ORG Subject: Re: write combining memory on pci Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 07 Dec 1998 16:14:08 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Dec 1998 22:49:59 +0100 From: Gary Jennejohn Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Ron G. Minnich" writes: > >On Mon, 7 Dec 1998, Karl Pielorz wrote: >> Both my P-Pro systems have this option, and AFAIK it worked as above (i.e. >> 'all on' or 'all off')... Win NT survives with it on, until I try to use the >> sound card, and FreeBSD, Linux & Win'95 all die within seconds with it on > >Hmm, that is bad news. I have some cards from a company that only run fast >with write combining turned ON. However, if they crash the OS with it on, >it might not be such a good deal. > >Guess I'll have to use the cards as a master, not a target for PIO >writes. As ever, the rule with PCI: don't get the CPU involved in data >transfer :-) > >> Which is a bit of a pitty, as I also seem to remember reading it gives a hug >e >> performance win on writes ;-) - Maybe there is such a thing as 'too fast'... > >something on order of at least 2x. It would be nice to have ... > an example of this is the fastvid lkm originally written by John Dyson and modified by Lars Koeller. It's available on Lars' home page (which you can find by looking at the README in hte xperfmon++ port, I believe). This seems to be a general-purpose write combine thingy, since it applies to a range of memory. Maybe you can modify it to meet your requirements. I use this on a PPro system (and I've tried it on a P-II, but the system became unstable - which may not heve been due to fastvid), so it may also work for you. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 14:19:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24115 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 14:19:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24110 for ; Mon, 7 Dec 1998 14:19:35 -0800 (PST) (envelope-from k@numeri.campus.luth.se) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.8.8/8.8.8) with ESMTP id XAA03758; Mon, 7 Dec 1998 23:23:56 +0100 (CET) (envelope-from k@numeri.campus.luth.se) Message-Id: <199812072223.XAA03758@numeri.campus.luth.se> X-Mailer: exmh version 2.0.2 2/24/98 To: "Ron G. Minnich" cc: hackers@FreeBSD.ORG Subject: Re: write combining memory on pci In-reply-to: Your message of "Mon, 07 Dec 1998 15:48:33 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Mon, 07 Dec 1998 23:23:56 +0100 From: Johan Karlsson Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA24111 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Mon, 07 Dec 1998 15:48:33 EST, "Ron G. Minnich" wrote: >any good ideas on how to turn this on in 3.0 for a given memory address >range? > This can be done using the MTRRs (Memory Type Range Registers) on a Ppro or PII. There are some functions in i386/i386/pmap.c to read and write those registers. (I don't know if the registers are enabled by default) For more info about the registers see http://www.intel.com/design/pro/manuals chapter 9 in "Intel Architecture Software Developer's Manual, Volume 3: System Programming Guide" Usualy the BIOS sets these registers. You can screw up the memory management bad if you don't know what you are doing. Take small steps :-) /Johan K -- Johan Karlsson mailto:k@numeri.campus.luth.se SWEDEN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 18:34:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23962 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 18:34:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun1.cc.binghamton.edu (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23956 for ; Mon, 7 Dec 1998 18:34:06 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id VAA24310; Mon, 7 Dec 1998 21:33:56 -0500 (EST) Date: Mon, 7 Dec 1998 21:33:55 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun1 Reply-To: zhihuizhang To: Doug Rabson cc: hackers Subject: Re: Definition of kstack and PTDpde in locore.s 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 Mon, 7 Dec 1998, Doug Rabson wrote: > > So far, it is fine for me. Yesterday, I came across the symbol kstack > > which is defined similary via the .set directive in locore.s. However, in > > pmap.c, I find the following usage: > > > > m = pmap_allocpte(pmap, (vm_offset_t) kstack); > > > Is this in the 2.2 source tree? We used to put the kernel stack of all > processes at the same virtual address (traditionally the struct user for > each process which includes the stack was always mapped in the same > place and could be accessed using the global variable 'u'). I think > that with the definition: > > .set _kstack, USRSTACK > > then from C,you could have: > > extern char kstack[]; > > assert(&kstack[0] == (char*)USRSTACK); > This seems to me that the VALUE of kstack (which is a fixed address in user virtual address space) is USRSTACK. But what is the address of kstack, i.e., where is kstack itself stored? > i.e. to find the top of the kernel stack, take the address of kstack. > Yes. I am looking into the 2.2.x source code. The KVA for UPAGES of each process is different, each consuming UPAGES of KVA. This explains why the size of u_map is set to be maxproc * UPAGES * page_size. (u_map is a submap of kern_map). These U areas at the same time also occupy the same size of VA in its process's virtual adderss space. I guess this double mapping of U pages is for (1) allow kernel access to the U pages of all active processes at any time; (2) No need to save and restore address mapping information during a context switch. While these topics are not easy to understand, my question is really a simpler one - a question of mixed GAS (assembly) and C programming. If the virtual address of the kernel stack in each process's address space (not in kernel) is the same as USRSTACK. Then according to the usage of pmap_allocpte() above, the value of kstack should be USRSTACK, not its address. But you said that PTDpde's address (not its value) is defined by .set directive in locore.s. This expains why (unsigned) PTDpde & PG_FRAME gives the physical address of the page directory page. So the address of kstack must be USRSTACK (not its value), since they are defined in the SAME way. Could you please explain this discrepancy for me? Thanks very much for your help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 19:06:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27557 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 19:06:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.novator.com (ns.novator.com [199.45.114.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27549 for ; Mon, 7 Dec 1998 19:06:55 -0800 (PST) (envelope-from vmg@ns.novator.com) Received: (from vmg@localhost) by ns.novator.com (8.8.8/8.8.8) id WAA03519 for hackers@freebsd.org; Mon, 7 Dec 1998 22:02:46 -0500 (EST) Message-Id: <199812080302.WAA03519@ns.novator.com> Subject: Is it possible? To: hackers@FreeBSD.ORG Date: Mon, 7 Dec 1998 22:02:46 -0500 (EST) From: "Victor Granic" X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have run into the proverbial brick wall. I am the administrator of a fairly busy electronic commerce Web site, www.ftd.com. Because of the demand placed on a single server, I implemented a load balancing solution that utilizes NFS in the back end. The versions of FreeBSD that I have tested (2.2.7 and 3.0) do not support exclusive advisory locks over NFS. Last week I was directed to Terry Lambert's Web page on the freebsd.org Web server. He makes available several patches for the kernel sources that supposedly fix the locking bugs. I attempted to patch both versions of FreeBSD that I have installed. On both systems the patch command failed to patch all the required files and the differences were too great to edit by hand. My motivation for sending this message is simple. I am an avid supporter of free software and open source initiatives. I have used FreeBSD in the past and I have always had very good experiences implementing Web servers, and firewalls. My current project on the FTD Web site is dependent on locking over NFS. Is there a solution to my problem? Truely, the last thing I would want to do to solve this problem is to have to purchase a commercial version of UNIX from Sun or some other behemoth. This is also my last resort as I have already posted to the FreeBSD newgroups and mailing lists without any response to my query. Thank you, Victor Granic -- Victor Granic.................................email: vmg@ftd.com FTD Internet, Web Admin.........................tel: 416-260-5131 Novator Systems, Ltd............................fax: 416-260-2924 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 20:01:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04565 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 20:01:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lab321.ru (anonymous1.omsk.net.ru [62.76.128.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04555 for ; Mon, 7 Dec 1998 20:01:46 -0800 (PST) (envelope-from kev@lab321.ru) Received: from www.lab321.ru (kev@www.lab321.ru [62.76.129.65]) by lab321.ru (8.9.1a/8.9.1a) with SMTP id JAA05828 for ; Tue, 8 Dec 1998 09:54:41 +0600 (OS) Date: Tue, 8 Dec 1998 09:54:41 +0600 (OS) From: Eugeny Kuzakov To: hackers@FreeBSD.ORG Subject: Another trap 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! Can anybody say me - what is it ? Bad memory ? IdlePTD 279000 current pcb at 235270 panic: page fault #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 266 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:266 #1 0xf0113972 in panic (fmt=0xf01e93bf "page fault") at ../../kern/kern_shutdown.c:400 #2 0xf01e9faa in trap_fatal (frame=0xefbffedc) at ../../i386/i386/trap.c:772 #3 0xf01e9a6c in trap_pfault (frame=0xefbffedc, usermode=0) at ../../i386/i386/trap.c:681 #4 0xf01e96f7 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = -263953956, tf_ebp = -272629976, tf_isp = -272630012, tf_ebx = -263953956, tf_edx = 1072738565, tf_ecx = -272105356, tf_eax = 524404, tf_trapno = 12, tf_err = 0, tf_eip = -266437133, tf_cs = 8, tf_eflags = 66070, tf_esp = -228636672, tf_ss = -225926656}) at ../../i386/i386/trap.c:324 #5 0xf01e7df3 in pmap_remove_pages (pmap=0xf25f4864, sva=0, eva=4022329344) at ../../i386/i386/pmap.c:2605 #6 0xf010dbbe in exit1 (p=0xf288a200, rv=0) at ../../kern/kern_exit.c:186 #7 0xf010da84 in exit (p=0xf288a200, uap=0xefbfff94, retval=0xefbfff84) at ../../kern/kern_exit.c:106 #8 0xf01ea1e7 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 0, tf_esi = -1, tf_ebp = -272638552, tf_isp = -272629788, tf_ebx = 537395296, tf_edx = 0, tf_ecx = 537333036, tf_eax = 1, tf_trapno = 12, tf_err = 7, tf_eip = 537343133, tf_cs = 31, tf_eflags = 646, tf_esp = -272638572, tf_ss = 39}) at ../../i386/i386/trap.c:920 #9 0x2007349d in ?? () Cannot access memory at address 0xefbfddac. (kgdb) q -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru ICQ#: 5885106 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 21:13:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11300 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 21:13:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11295 for ; Mon, 7 Dec 1998 21:13:46 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA35272; Mon, 7 Dec 1998 21:13:30 -0800 (PST) (envelope-from dillon) Date: Mon, 7 Dec 1998 21:13:30 -0800 (PST) From: Matthew Dillon Message-Id: <199812080513.VAA35272@apollo.backplane.com> To: "Victor Granic" Cc: hackers@FreeBSD.ORG Subject: Re: Is it possible? References: <199812080302.WAA03519@ns.novator.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hello, : :I have run into the proverbial brick wall. I am the administrator of :a fairly busy electronic commerce Web site, www.ftd.com. Because of :the demand placed on a single server, I implemented a load balancing :solution that utilizes NFS in the back end. The versions of FreeBSD :that I have tested (2.2.7 and 3.0) do not support exclusive advisory :locks over NFS. Last week I was directed to Terry Lambert's Web page :on the freebsd.org Web server. He makes available several patches :for the kernel sources that supposedly fix the locking bugs. :... I think Terry's stuff addressed kernel bugs. In order for locking to work between NFS hosts, rpc.lockd needs to be implemented and nobody has taken up the task yet. It's been a thorn in FreeBSD's side for a while now. The RPC framework is in place, but none of the routine have been implemented yet. -Matt :Thank you, : :Victor Granic : :... : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 21:51:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15136 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 21:51:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15131 for ; Mon, 7 Dec 1998 21:51:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA35618; Mon, 7 Dec 1998 21:51:03 -0800 (PST) (envelope-from dillon) Date: Mon, 7 Dec 1998 21:51:03 -0800 (PST) From: Matthew Dillon Message-Id: <199812080551.VAA35618@apollo.backplane.com> To: Charles Henrich Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Large memory size per process? References: <19981205100451.10207@orbit.flnet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :When compiling a kernel with 2GB for the max DSIZ we get integer overflows all :over the place. At 1.5GB we only get one in the elf loader, and it seems to :work okay set that way. 2GB I get all sorts of overflows in the vm subsystem :and havent tried to run that way. Due to this Im assuming that its impossible :to get large processes in FreeBSD without some major work, is this true? : :-Crh : : Charles Henrich Manex Visual Effects henrich@flnet.com : : http://orbit.flnet.com/~henrich : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message Hmm. Well, it looks like it should be possible. imgact_elf.c would be a problem. kern/kern_resource.c would be ok if MAXDSIZ were cast to unsigned or turned into a quad_t or rlim_t. The other instances would require overflow checks but ought to work reasonably well. However, increasing MAXDSIZ decreases the VM space available for mmap() and SysV shared memory and could create other problems. Are you actually running a program that uses that much data space or is your program using mmap()? You may be able to work around the problem temporarily by using a smaller MAXDSIZ and instead using mmap() to allocate memory. -Matt apollo:/usr/src/sys# fgrep MAXDSIZ */*.c kern/imgact_elf.c: addr = 2L*MAXDSIZ; /* May depend on OS type XXX */ kern/kern_resource.c: if (limp->rlim_cur > MAXDSIZ) kern/kern_resource.c: limp->rlim_cur = MAXDSIZ; kern/kern_resource.c: if (limp->rlim_max > MAXDSIZ) kern/kern_resource.c: limp->rlim_max = MAXDSIZ; kern/sysv_shm.c: attach_va = round_page((vm_offset_t)p->p_vmspace->vm_taddr + MAXTSIZ + MAXDSIZ); vm/vm_glue.c: p->p_rlimit[RLIMIT_DATA].rlim_max = MAXDSIZ; vm/vm_mmap.c: else if (addr < round_page((vm_offset_t)p->p_vmspace->vm_daddr + MAXDSIZ)) vm/vm_mmap.c: addr = round_page((vm_offset_t)p->p_vmspace->vm_daddr + MAXDSIZ); Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 7 22:19:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17425 for freebsd-hackers-outgoing; Mon, 7 Dec 1998 22:19:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17412 for ; Mon, 7 Dec 1998 22:18:58 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.56.138]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA20FC; Tue, 8 Dec 1998 07:18:52 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19981207193525.A18185@gvr.org> Date: Tue, 08 Dec 1998 07:24:29 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Guido van Rooij Subject: Re: Can we just come to a decision on IPv6 and IPSec? Cc: hackers@FreeBSD.ORG, Eivind Eklund , Andreas Klemm , "Jordan K. Hubbard" , Jun-ichiro itojun Itoh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Dec-98 Guido van Rooij wrote: > On Fri, Dec 04, 1998 at 11:10:51AM +0900, Jun-ichiro itojun Itoh wrote: >> >> One thing we don't implement intentionally is automatic tunnelling >> (packets to ::10.1.1.1 automatically tunnelled over IPv6-over-IPv4 >> tunnel to 10.1.1.1). > > Hmm..what does happen when I have a IPV6/V4 host that has an IPV6 > native address (so no V4 compatible address) that wants to communicate > to an IPv4 host? Do I need to set up IPV4 specific routes to > a dual stack machine that does the tunneling for me? If I remember correctly, at the moment we are all tunneling over IPv4 to 6-Bone using the IPv4 addresses which get stripped as soon as the packets reach their tunnel gateway. So in general you only provide the default route for IPv6 to the tunnel gateway using the -tunnel option in route (at least that's how I did it using BSDi). It's an obvious choice to make the default gateway from yer internal LAN to the Internet the dual stack machine/tunneling gateway. The rest of the hosts simply use the tunneling gateway by it's native IPv4 address. Note that when approximately 50% uses IPv6 encapsulation in IPv4 packets we are going to switch it all around ;) Unfortunately, man ifconfig route | grep tunnel yields nothing, we do have a tunnel option somewhere right? --- Jeroen Ruigrok van der Werven Pax vobiscum... asmodai(at)wxs.nl Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 00:11:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA27058 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 00:11:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA26939 for ; Tue, 8 Dec 1998 00:10:00 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id KAA04908; Tue, 8 Dec 1998 10:03:26 +0200 (EET) (envelope-from ru) Date: Tue, 8 Dec 1998 10:03:25 +0200 From: Ruslan Ermilov To: Marc Slemko Cc: Thomas David Rivers , hackers@FreeBSD.ORG Subject: Re: TCP bug Message-ID: <19981208100325.A2574@ucb.crimea.ua> Mail-Followup-To: Marc Slemko , Thomas David Rivers , hackers@FreeBSD.ORG References: <19981207163606.A7575@ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.17i In-Reply-To: ; from Marc Slemko on Mon, Dec 07, 1998 at 11:47:15AM -0800 X-Operating-System: FreeBSD 2.2.7-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 07, 1998 at 11:47:15AM -0800, Marc Slemko wrote: > On Mon, 7 Dec 1998, Ruslan Ermilov wrote: > > > > I mean the FreeBSD box you are sitting on and from which you can't access > > www.aol.com. > > That isn't overly likely to be an issue in this case. A tcpdump will show > for sure the ack for that packet is getting back or not. > Tcpdump will show that packets have no DF bit set. > > > As I understood this discussion (which seemed clear to me); the > > > problem was that an internal node (behind the firewall) couldn't > > > get to some web sites because of fragmentation issues. The low > > > MTU at the firewall/gateway broke path MTU discovery.. > > > > No, the problem is not with low MTU, but because AOL is blocking ICMP: > > > > PING aol.com (152.163.210.29): 56 data bytes > > 36 bytes from www2-r10-P5-0-0.tpopr-rri.aol.com (152.163.133.6): Communication prohibited by filter > > Vr HL TOS Len ID Flg off TTL Pro cks Src Dst > > 4 5 00 5400 68cb 0 0000 ea 01 894d 194.93.177.113 152.163.210.29 > > > > ^C > > --- aol.com ping statistics --- > > 22 packets transmitted, 0 packets received, 100% packet loss > > While the blame should be assigned to someone who is filtering, it is > important to note that just because you can't ping someone doesn't mean > they are filtering all ICMP. > Using telnet is a bad idea to test whether PMTU-D works on not. Telnet produces small packets, so you'll never receive "fragmentation needed and DF is set" message. For the same reason, you can't test whether a site is blocking ICMP type 3 code 4 messages. -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 00:15:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA27454 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 00:15:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA27449 for ; Tue, 8 Dec 1998 00:14:59 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id AAA85156; Tue, 8 Dec 1998 00:14:37 -0800 (PST) To: "Victor Granic" cc: hackers@FreeBSD.ORG Subject: Re: Is it possible? In-reply-to: Your message of "Mon, 07 Dec 1998 22:02:46 EST." <199812080302.WAA03519@ns.novator.com> Date: Tue, 08 Dec 1998 00:14:37 -0800 Message-ID: <85152.913104877@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have run into the proverbial brick wall. I am the administrator of > a fairly busy electronic commerce Web site, www.ftd.com. Because of > the demand placed on a single server, I implemented a load balancing > solution that utilizes NFS in the back end. The versions of FreeBSD Hmmm. Well, as you've already noted, NFS is not really sufficient to this task and never has been. There has never been any locking with our NFS and, as evidence would tend to suggest, never a degree of interest on anyone's part sufficient to actually motivate them to implement the functionality. Even with working NFS locks, it's also probably an inferior solution to what many folks are doing and that's load balancing at the IP level. Something like the Coyote Point Systems Equalizer package (which is also based on FreeBSD, BTW) which takes n boxes and switches the traffic for them from one FreeBSD box using load metrics and other heuristics to determine the best match for a request would be a fine solution, as would any of the several other similar products on the market. Unless you're up for doing an NFS lock implementation, that is. Terry's patches only address some purported bugs in the general NFS code, they don't actually implement the lock daemon and other functionality you'd need to have truly working NFS locks. Evidently, this isn't something which has actually interested Terry enough to do either. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 01:24:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04224 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 01:24:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04217 for ; Tue, 8 Dec 1998 01:24:25 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA09822; Tue, 8 Dec 1998 09:24:30 GMT Date: Tue, 8 Dec 1998 09:24:30 +0000 (GMT) From: Doug Rabson To: zhihuizhang cc: hackers Subject: Re: Definition of kstack and PTDpde in locore.s 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 Mon, 7 Dec 1998, zhihuizhang wrote: > > On Mon, 7 Dec 1998, Doug Rabson wrote: > > > > So far, it is fine for me. Yesterday, I came across the symbol kstack > > > which is defined similary via the .set directive in locore.s. However, in > > > pmap.c, I find the following usage: > > > > > > m = pmap_allocpte(pmap, (vm_offset_t) kstack); > > > > > > Is this in the 2.2 source tree? We used to put the kernel stack of all > > processes at the same virtual address (traditionally the struct user for > > each process which includes the stack was always mapped in the same > > place and could be accessed using the global variable 'u'). I think > > that with the definition: > > > > .set _kstack, USRSTACK > > > > then from C,you could have: > > > > extern char kstack[]; > > > > assert(&kstack[0] == (char*)USRSTACK); > > > > This seems to me that the VALUE of kstack (which is a fixed address in > user virtual address space) is USRSTACK. But what is the address of > kstack, i.e., where is kstack itself stored? > > > i.e. to find the top of the kernel stack, take the address of kstack. > > > > Yes. I am looking into the 2.2.x source code. The KVA for UPAGES of each > process is different, each consuming UPAGES of KVA. This explains why the > size of u_map is set to be maxproc * UPAGES * page_size. (u_map is a > submap of kern_map). These U areas at the same time also occupy the same > size of VA in its process's virtual adderss space. I guess this double > mapping of U pages is for (1) allow kernel access to the U pages of all > active processes at any time; (2) No need to save and restore address > mapping information during a context switch. > > While these topics are not easy to understand, my question is really a > simpler one - a question of mixed GAS (assembly) and C programming. > > If the virtual address of the kernel stack in each process's address space > (not in kernel) is the same as USRSTACK. Then according to the usage of > pmap_allocpte() above, the value of kstack should be USRSTACK, not its > address. > > But you said that PTDpde's address (not its value) is defined by .set > directive in locore.s. This expains why (unsigned) PTDpde & PG_FRAME > gives the physical address of the page directory page. So the address of > kstack must be USRSTACK (not its value), since they are defined in the > SAME way. Could you please explain this discrepancy for me? > > Thanks very much for your help. The '.set' directive is setting the address of kstack to USRSTACK. In C, you can declare kstack in various different ways. One way is: char kstack; ... p = &kstack; /* p == USRSTACK */ another is: char kstack[]; ... p = &kstack[0]; /* p == USRSTACK */ The assembly language symbol for a global array or a global char (or anything) is the address where the array or char is to be stored. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 02:33:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10004 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 02:33:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09996 for ; Tue, 8 Dec 1998 02:33:20 -0800 (PST) (envelope-from Reinier.Bezuidenhout@KryptoKom.DE) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id LAA14652 for ; Tue, 8 Dec 1998 11:33:18 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1beta6) id kwa14646; Tue Dec 08 11:32:59 1998 Received: by Cirdan.KryptoKom.DE (8.8.5/8.8.5) with ESMTP id LAA12258 for ; Tue, 8 Dec 1998 11:28:27 +0100 Original: Received: (from bez@localhost) by borg.kryptokom.de (8.8.8/8.8.8) id LAA08899 for freebsd-hackers@freebsd.org; Tue, 8 Dec 1998 11:40:01 +0100 (CET) (envelope-from bez) From: Reinier Bezuidenhout Message-Id: <199812081040.LAA08899@borg.kryptokom.de> Subject: kernel and ioctl call to kernel function To: freebsd-hackers@FreeBSD.ORG Date: Tue, 8 Dec 1998 11:40:01 +0100 (CET) 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 ... We have implemented a funtion in the kernel that does some operations on data given to the function. This function can be called from within the kernel AND from user level via a ioctl call. What will happen if the kernel calls this function after the user level process also called this function via the ioctl or vice versa. Does the one wait for the other before the function is entered ??? I see some strange behaviour where the user level process never seems to hang (no characters are echo'd to the screen anymore, I can still swap vertual screens, but to character input and the num-lock still worlks :) ). The kernel call to this function, however, seems to continue working without any problem. How is this "simultanious" call to the same function handled ?? Thanx Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 02:35:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10241 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 02:35:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from starlab.ifmo.ru (starlab.ifmo.ru [194.85.164.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10227 for ; Tue, 8 Dec 1998 02:34:56 -0800 (PST) (envelope-from antonenk@starlab.ifmo.ru) Received: from starlab.ifmo.ru ([194.85.164.87]) by starlab.ifmo.ru (8.8.5/RUNNet-270398) with ESMTP id NAA00479 for ; Tue, 8 Dec 1998 13:35:00 +0300 (EET) Message-ID: <366D00FC.5C6B3E1C@starlab.ifmo.ru> Date: Tue, 08 Dec 1998 13:35:40 +0300 From: "Leonid A.Antonenkov" X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-Hackers@FreeBSD.ORG Subject: 100VG AnyLAN drivers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's up with 100VG AnyLAN drivers? I search all Internet but without any results. Answer me anything... Sincerely yours, Leonid A.Antonenkov antonenk@starlab.ifmo.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 06:25:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29767 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 06:25:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nimbus.superior.net (nimbus.superior.net [206.153.96.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29762 for ; Tue, 8 Dec 1998 06:25:28 -0800 (PST) (envelope-from robert@superior.net) Received: (from robert@localhost) by nimbus.superior.net (8.8.8/8.8.8/RB) id JAA25501 for freebsd-hackers@freebsd.org; Tue, 8 Dec 1998 09:25:24 -0500 (EST) From: Robert Blayzor Message-Id: <199812081425.JAA25501@nimbus.superior.net> Subject: FreeBSD 2.2.8-stable buildworld breaks... To: freebsd-hackers@FreeBSD.ORG Date: Tue, 8 Dec 1998 09:25:24 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL40 (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 I am trying to make buildworld on FreeBSD 2.2.8-stable cvsup'd to 12/8/98 (morning) and when I do so, I get about 3/4's of the way through the buildworld and get: Any ideas? mkdep -f .depend -a -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC -DDEMANGLE_CPLUSPLUS -I/usr/obj/usr/src/tmp/usr/include /usr/src/gnu/usr.bin/ld/ld.c /usr/src/gnu/usr.bin/ld/symbol.c /usr/src/gnu/usr.bin/ld/lib.c /usr/src/gnu/usr.bin/ld/shlib.c /usr/src/gnu/usr.bin/ld/warnings.c /usr/src/gnu/usr.bin/ld/support.c /usr/src/gnu/usr.bin/ld/rrs.c /usr/src/gnu/usr.bin/ld/xbits.c /usr/src/gnu/usr.bin/ld/i386/md.c /usr/src/gnu/usr.bin/ld/../.. /../contrib/gcc/cplus-dem.c ===> gnu/usr.bin/ld/ldconfig rm -f .depend mkdep -f .depend -a -I/usr/src/gnu/usr.bin/ld/ldconfig/.. -I/usr/src/gnu/usr.bin/ld/ldconfig -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386 -I/usr/obj/usr/src/tmp/usr/include /usr/src/gnu/usr.bin/ld/ldconfig/ldconfig.c /usr/src/gnu/usr.bin/ld/ldconfig/../shlib.c /usr/src/gnu/usr.bin/ld/ldconfig/../support.c ===> gnu/usr.bin/ld/ldd rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/src/tmp/usr/include /usr/src/gnu/usr.bin/ld/ldd/ldd.c /usr/src/gnu/usr.bin/ld/ldd/sods.c ===> gnu/usr.bin/ld/rtld rm -f .depend mkdep -f .depend -a -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -DRTLD -I/usr/obj/usr/src/tmp/usr/include /usr/src/gnu/usr.bin/ld/rtld/../i386/mdprologue.S mkdep -f .depend -a -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -DRTLD -I/usr/obj/usr/src/tmp/usr/include /usr/src/gnu/usr.bin/ld/rtld/rtld.c /usr/src/gnu/usr.bin/ld/rtld/malloc.c /usr/src/gnu/usr.bin/ld/rtld/../shlib.c /usr/src/gnu/usr.bin/ld/rtld/../i386/md.c /usr/src/gnu/usr.bin/ld/rtld/../support.c /usr/src/gnu/usr.bin/ld/rtld/sbrk.c ===> gnu/usr.bin/man ===> gnu/usr.bin/man/lib sed -e 's,%apropos%,/usr/bin/apropos,' -e 's,%whatis%,/usr/bin/whatis,' -e 's,%pager%,more -s,' -e 's,%troff%,/usr/bin/groff -man,' -e 's,%nroff%,/usr/bin/groff -Wall -mtty-char -Tascii -man,' -e 's,%tbl%,/usr/bin/tbl,' -e 's,%col%,/usr/bin/col,' -e 's,%pic%,/usr/bin/pic,' -e 's,%eqn%,,' -e 's,%neqn%,/usr/bin/eqn -Tascii,' -e 's,%vgrind%,/usr/bin/vgrind,' -e 's,%refer%,/usr/bin/refer,' -e 's,%grap%,,' -e 's,%zcat%,/usr/bin/zcat,' -e 's,%manpath_config_file%,/etc/manpath.config,' -e 's,%compress%,/u sr/bin/gzip -c,' -e 's,%compext%,.gz,' /usr/src/gnu/usr.bin/man/lib/config.h_dist > config.h sed: 1: "s,%whatis%,/usr/bin/wha ...": bad flag in substitute command: 's' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- Robert Blayzor robert@superior.net Telecon Communications MIS/Programmer/Admin Network Engineer 131 Enterprise Rd. Superior Net Services 518-762-3456 Johnstown, NY 12095 "FreeBSD! Turning PC's into Workstations!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 06:58:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02220 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 06:58:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cave.garant.ru (cave.garant.ru [195.209.33.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02199 for ; Tue, 8 Dec 1998 06:58:32 -0800 (PST) (envelope-from taurus@cave.garant.ru) Received: from localhost (taurus@localhost) by cave.garant.ru (8.9.1/8.9.1) with ESMTP id RAA25314 for ; Tue, 8 Dec 1998 17:52:53 +0300 (MSK) (envelope-from taurus@cave.garant.ru) Date: Tue, 8 Dec 1998 17:52:53 +0300 (MSK) From: "Andrew A. Bely" To: freebsd-hackers@FreeBSD.ORG Subject: Cross-compiling for FreeBSD 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 Sorry for bringing up such subject again... Some tasks we solve at our job requires cross-compilers to FreeBSD (both 2.2.6 or 2.2.7 and 3.0-RELEASE) hosted on Solaris 2.6 (x86 platform). I try to build this cross-compilers both from GCC 2.7.2.3 and egcs 1.1b distributions using i386-pc-freebsd(elf) as targets for 2.2.x (3.0) respectively. Both of them does not works. The problem looks like I've got wrong binutils (built from binutils 2.9.1). At least, nm (and also ld, of course) configured for i386-pc-freebsd does not understand formats of some object files from native libc.a. 3.0 cross has another problem, related to binutils again, I think. Some symbols from object files has one more underscore char than in native libs, but some has one underscore lost. At second, I have only crt1.o (not crt0.o) startup object file and ld.so is named as ld-elf.so. I've looked up through mail list archives and find that I probably needs the ElfKit written by John D. Polstra. But all links points to his FTP site, that does not contain ElfKit (any more ?). Also I probably needs some binutils patches and hints on making it works. Please, please, please! Help me! Thanks. Important! I'm not subscribed to this mailiing list, so, please, CC me any replies to Andrew A. Bely Software developer in Garant-Service, Moscow, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 11:32:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00812 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 11:32:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA00807 for ; Tue, 8 Dec 1998 11:32:50 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id OAA11071; Tue, 8 Dec 1998 14:32:42 -0500 Date: Tue, 8 Dec 1998 14:32:42 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@FreeBSD.ORG Subject: boot CDROM 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 built bootable cdrom's for freebsd a year ago, and can't for the life of me remember how i made them bootable. That is, I can build iso root images easily, and I know how to use mkisofs, etc. But I can't remember what i had to do to make a cdrom that was bootable, not just a file system image. help ? :=) Ron Ron Minnich |"Using Windows NT, which is known to have some rminnich@sarnoff.com | failure modes, on a warship is similar to hoping (609)-734-3120 | that luck will be in our favor"- A. Digiorgio ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 11:40:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01467 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 11:40:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01449; Tue, 8 Dec 1998 11:40:06 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA19045; Tue, 8 Dec 1998 11:38:45 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma019039; Tue, 8 Dec 98 11:38:16 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA02380; Tue, 8 Dec 1998 11:38:16 -0800 (PST) From: Archie Cobbs Message-Id: <199812081938.LAA02380@bubba.whistle.com> Subject: Re: FreeBSD 2.2.8-stable buildworld breaks... In-Reply-To: <199812081425.JAA25501@nimbus.superior.net> from Robert Blayzor at "Dec 8, 98 09:25:24 am" To: robert@superior.net (Robert Blayzor) Date: Tue, 8 Dec 1998 11:38:16 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Robert Blayzor writes: > sed: 1: "s,%whatis%,/usr/bin/wha ...": bad flag in substitute command: 's' > *** Error code 1 This is my fault.. I'm fixing it now.. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 12:00:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03333 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 12:00:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ozz.etrust.ru ([195.2.84.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03326 for ; Tue, 8 Dec 1998 12:00:31 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id WAA13363 for ; Tue, 8 Dec 1998 22:54:11 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Tue, 8 Dec 1998 22:54:10 +0300 (MSK) From: oZZ!!! To: hackers@FreeBSD.ORG Subject: About Alladin5 chipset... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Does FreeBSD support motherboard with Alladin5 chipset ? Rgdz, ïÓÏËÉÎ óÅÒÇÅÊ aka oZZ, osa@FreeBSD.org.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 12:22:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05451 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 12:22:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05444; Tue, 8 Dec 1998 12:22:41 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA19791; Tue, 8 Dec 1998 12:21:54 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma019787; Tue, 8 Dec 98 12:21:38 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA02670; Tue, 8 Dec 1998 12:21:38 -0800 (PST) From: Archie Cobbs Message-Id: <199812082021.MAA02670@bubba.whistle.com> Subject: sed problem To: freebsd-hackers@FreeBSD.ORG Date: Tue, 8 Dec 1998 12:21:38 -0800 (PST) Cc: jkh@FreeBSD.ORG, jdp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 I'm trying to fix the sed problem, but.. cvs server: [12:07:09] waiting for mjacob's lock in /home/ncvs/src/usr.bin/sed This lock has been held since 8:11 am -- suspiciously close to the time the power went out in SF this morning.. Could somebody who has the ability fix this (and email me when done)? Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 12:27:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05789 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 12:27:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bamboo.verinet.com (bamboo.verinet.com [204.144.246.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05784 for ; Tue, 8 Dec 1998 12:27:36 -0800 (PST) (envelope-from allenc@bamboo.verinet.com) Received: (from allenc@localhost) by bamboo.verinet.com (8.8.8/8.7.1) id NAA24541 for hackers@freebsd.org; Tue, 8 Dec 1998 13:27:31 -0700 Date: Tue, 8 Dec 1998 13:27:31 -0700 From: Allen Campbell Message-Id: <199812082027.NAA24541@bamboo.verinet.com> To: hackers@FreeBSD.ORG Subject: sysinstall Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What bits, if any, of sysinstall's successor are currently available? I have read in -hackers and -commit about the desire to replace sysinstall. I thought I had read that Mike Smith was currently working on this. -- Allen Campbell | Lurking at the bottom of the allenc@verinet.com | gravity well, getting old. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 12:46:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07569 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 12:46:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA07445 for ; Tue, 8 Dec 1998 12:46:07 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id TAA17379; Tue, 8 Dec 1998 19:38:40 +0100 From: Luigi Rizzo Message-Id: <199812081838.TAA17379@labinfo.iet.unipi.it> Subject: Re: boot CDROM To: rminnich@Sarnoff.COM (Ron G. Minnich) Date: Tue, 8 Dec 1998 19:38:40 +0100 (MET) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Ron G. Minnich" at Dec 8, 98 02:32:23 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I built bootable cdrom's for freebsd a year ago, and can't for the life > of me remember how i made them bootable. That is, I can build iso root > images easily, and I know how to use mkisofs, etc. But I can't remember > what i had to do to make a cdrom that was bootable, not just a file > system image. it is some mkisofs option (either inmkisofs 1.10 or 1.11) which tells what to use as a bootable image (which must be a floppy image). I am not sure if it can be larger than 1.44MB, actually that would be nice for some apps, given that now CDR media and CDROM readers cost almost the same as floppies and floppy drives respectively. luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 13:23:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11814 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 13:23:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from colin.muc.de (colin.muc.de [193.174.4.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA11792 for ; Tue, 8 Dec 1998 13:23:23 -0800 (PST) (envelope-from lutz@muc.de) Received: from tavari.muc.de ([193.174.4.22]) by colin.muc.de with SMTP id <140565-1>; Tue, 8 Dec 1998 22:23:03 +0100 Received: (from daemon@localhost) by tavari.muc.de (8.8.8/8.8.7) id WAA01691; Tue, 8 Dec 1998 22:19:55 +0100 (CET) Received: from ripley(192.168.42.202) by morranon via smap (V2.1) id xma001684; Tue, 8 Dec 98 22:19:47 +0100 From: "Lutz Albers" To: "Nate Williams" , Subject: RE: Wchar support in FreeBSD Date: Tue, 8 Dec 1998 22:19:35 +0100 Message-ID: <001901be22f0$746f4fe0$ca2aa8c0@ripley.tavari.muc.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal In-reply-to: <199812072144.OAA06810@mt.sri.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there any 3rd party libraries that support the 'wchar' stuff? IBM > just made it's Jikes compiler available as an 'Open Source Project', and > I'd like to make a FreeBSD-native version. > > However, it requires the native wchar support (which exists in Win32, > Solaris, and Linux), but not in FreeBSD. > > Any clues how I can easily get around this? Do a mailing list search on "wchar.h functions from Solaris/Linux". There was a thread where Terry claimed that XView 3.2 contained wchar support. -- Lutz Albers, lutz@muc.de, pgp key available from Do not take life too seriously, you will never get out of it alive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 13:27:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12283 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 13:27:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12276 for ; Tue, 8 Dec 1998 13:27:14 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA21937; Tue, 8 Dec 1998 14:27:08 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA13924; Tue, 8 Dec 1998 14:27:07 -0700 Date: Tue, 8 Dec 1998 14:27:07 -0700 Message-Id: <199812082127.OAA13924@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Lutz Albers" Cc: "Nate Williams" , Subject: RE: Wchar support in FreeBSD In-Reply-To: <001901be22f0$746f4fe0$ca2aa8c0@ripley.tavari.muc.de> References: <199812072144.OAA06810@mt.sri.com> <001901be22f0$746f4fe0$ca2aa8c0@ripley.tavari.muc.de> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is there any 3rd party libraries that support the 'wchar' stuff? IBM > > just made it's Jikes compiler available as an 'Open Source Project', and > > I'd like to make a FreeBSD-native version. > > > > However, it requires the native wchar support (which exists in Win32, > > Solaris, and Linux), but not in FreeBSD. > > > > Any clues how I can easily get around this? > > Do a mailing list search on "wchar.h functions from Solaris/Linux". There > was a thread where Terry claimed that XView 3.2 contained wchar support. Thanks for the pointer! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 13:29:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12569 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 13:29:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12558; Tue, 8 Dec 1998 13:29:39 -0800 (PST) (envelope-from jdp@polstra.com) Received: from kerouac.polstra.com (kerouac.polstra.com [206.213.73.11]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id NAA27951; Tue, 8 Dec 1998 13:29:31 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by kerouac.polstra.com (8.8.8/8.8.8) id NAA00341; Tue, 8 Dec 1998 13:29:27 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812082021.MAA02670@bubba.whistle.com> Date: Tue, 08 Dec 1998 13:29:27 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Archie Cobbs Subject: RE: sed problem Cc: jkh@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I fixed it. John On 08-Dec-98 Archie Cobbs wrote: > I'm trying to fix the sed problem, but.. > > cvs server: [12:07:09] waiting for mjacob's lock in > /home/ncvs/src/usr.bin/sed > > This lock has been held since 8:11 am -- suspiciously close > to the time the power went out in SF this morning.. > > Could somebody who has the ability fix this (and email me > when done)? > > Thanks, > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 13:36:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13548 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 13:36:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13541 for ; Tue, 8 Dec 1998 13:36:04 -0800 (PST) (envelope-from kaleb@ics.com) Received: from ics.com (sunoco.ics.com [140.186.40.142]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id QAA04869 Tue, 8 Dec 1998 16:35:53 -0500 (EST) Message-ID: <366D9BB8.CB2D98FF@ics.com> Date: Tue, 08 Dec 1998 16:35:53 -0500 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: Wchar support in FreeBSD References: <199812072144.OAA06810@mt.sri.com> <001901be22f0$746f4fe0$ca2aa8c0@ripley.tavari.muc.de> <199812082127.OAA13924@mt.sri.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: > > > > Is there any 3rd party libraries that support the 'wchar' stuff? > > Do a mailing list search on "wchar.h functions from Solaris/Linux". There > > was a thread where Terry claimed that XView 3.2 contained wchar support. > > Thanks for the pointer! Libc has the basic stuff: wcslen, mbstowcs, wcstombs, etc. The rest, e.g. wcscat, wcscpy, etc, you can roll your own on -- there's no rocket science involved. -- Kaleb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 14:02:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17481 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 14:02:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: (from jha@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17474 for freebsd-hackers; Tue, 8 Dec 1998 14:02:34 -0800 (PST) (envelope-from jha) From: John Aughey Message-Id: <199812082202.OAA17474@hub.freebsd.org> Subject: Pseudo Disk in Userland? To: freebsd-hackers Date: Tue, 8 Dec 1998 14:02:34 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL32 (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 Hello- I'm wanting to create a kernel device that pretends to be a physical disk but actually exists in some other form. What I want to do is have the requests be given to a userland process that actually services the request. I understand some subsystems such as NFS use a similar approach. Can someone point me to some simple code that works in this way? Thank you John Aughey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 14:29:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21055 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 14:29:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21042 for ; Tue, 8 Dec 1998 14:29:31 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA27552 for hackers@FreeBSD.ORG; Tue, 8 Dec 1998 23:29:23 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 9F594155B; Tue, 8 Dec 1998 23:09:55 +0100 (CET) Date: Tue, 8 Dec 1998 23:09:55 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: Can we just come to a decision on IPv6 and IPSec? Message-ID: <19981208230955.A16874@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: <1958.912571118@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: <1958.912571118@zippy.cdrom.com>; from Jordan K. Hubbard on Tue, Dec 01, 1998 at 07:58:38PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4871 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jordan K. Hubbard: > This fence rail is pointy and cold and I think we're all going to come > down with an embarrassing medical condition if we keep sitting on it. I just got a mail from Francis -- he's at the IETF with also the KAME developpers -- and he said they've decided to write a unified version of the IPv6 stack. I don't have more details for the moment but if it gets done, it would solve our problems... Francis: -=-=- PS: nous avons profite de la presence de tous les principaux "developpeurs" d'IPv6 sur *BSD pour decider de faire une version Unifiee (entre les IPv6, pas les *BSD :-). -=-=- Translation: -=-=- PS: we took the opportunity of the the presence of all major IPv6 developpers on *BSD to decide to make a unified version (of the IPv6 stack not the *BSD :-)). -=-=- -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 15:01:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24467 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 15:01:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omahpop1.omah.uswest.net (omahpop1.omah.uswest.net [204.26.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA24460 for ; Tue, 8 Dec 1998 15:01:21 -0800 (PST) (envelope-from opsys@open-systems.net) Received: (qmail 17547 invoked by alias); 8 Dec 1998 23:01:13 -0000 Delivered-To: fixup-hackers@FreeBSD.ORG@fixme Received: (qmail 17532 invoked by uid 0); 8 Dec 1998 23:01:11 -0000 Received: from dialup177.omah.uswest.net (HELO pinkfloyd.open-systems.net) (209.180.100.177) by omahpop1.omah.uswest.net with SMTP; 8 Dec 1998 23:01:11 -0000 Date: Tue, 8 Dec 1998 17:01:10 -0600 (CST) From: "Open Systems Inc." To: Ollivier Robert cc: hackers@FreeBSD.ORG Subject: Re: Can we just come to a decision on IPv6 and IPSec? In-Reply-To: <19981208230955.A16874@keltia.freenix.fr> 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, 8 Dec 1998, Ollivier Robert wrote: > I just got a mail from Francis -- he's at the IETF with also the KAME > developpers -- and he said they've decided to write a unified version of > the IPv6 stack. Well as the saying goes, it might be too little to late so to speak. Japan and France recently hopped on the "clinton-anti-privacy" bandwagon along with 31 other countries that now prevent them from exporting strong crypto. I have no idea how this impacts things. But this is far from being a GoodThing(tm). We will just have to wait and see how this unfolds. Chris -- "Join Team-FreeBSD on cracking RC5-64! grab you client now and HELP OUT! http://www.distributed.net/cgi/select.cgi" ===================================| Open Systems FreeBSD Consulting. FreeBSD 2.2.8 is available now! | Phone: 402-573-9124 -----------------------------------| 3335 N. 103 Plaza #14, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 18:18:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16802 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 18:18:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.communique.no (www.communique.no [193.212.204.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA16788 for ; Tue, 8 Dec 1998 18:18:28 -0800 (PST) (envelope-from are@communique.no) Received: (qmail 7470 invoked by uid 1001); 9 Dec 1998 02:23:03 -0000 Date: Wed, 9 Dec 1998 03:23:03 +0100 (CET) From: Are Bryne To: FreeBSD hackers Subject: Stripping /usr/obj/usr/src executables... Message-ID: Organization: Communique DA MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, It would be nice to know why the /usr/obj/usr/src/*/* executables aren't stripped. This only happens during the installworld stage... How about a switch somewhere in make.conf for this to be done already during buildworld. You save a few megabytes, and a little time too, with multiple installworlds. Thanks in advance, Are Bryne To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 18:51:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19705 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 18:51:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19700 for ; Tue, 8 Dec 1998 18:51:28 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id SAA18400; Tue, 8 Dec 1998 18:51:02 -0800 (PST) To: Allen Campbell cc: hackers@FreeBSD.ORG Subject: Re: sysinstall In-reply-to: Your message of "Tue, 08 Dec 1998 13:27:31 MST." <199812082027.NAA24541@bamboo.verinet.com> Date: Tue, 08 Dec 1998 18:51:01 -0800 Message-ID: <18396.913171861@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What bits, if any, of sysinstall's successor are currently available? I > have read in -hackers and -commit about the desire to replace > sysinstall. I thought I had read that Mike Smith was currently working > on this. Mike, I and Eugene (a contractor in Russia) are working on it. What we've decided to do is start with the new package system since the idea has always been that sysinstall would be little more than a wrapper around a much more powerful packaging system which handled all the dependency, registration and upgrade functionality. Sysinstall itself would do little more than set up disks and figure out how to get packages from a wide variety of media. In any case, the new package system is still very much a WIP and also has some pretty hefty prerequisites: Qt 1.40 or later. TurboVision 0.6 or later. gcc 2.8.1 or later (also including egcs). The latter is the biggie for most folks since 2.7.2, our current compiler, has C++ support which is broken in too many ways for Eugene to write the kind of C++ code he wanted to write (he's a big fan of templates and MI). Since we've wanted to upgrade our compiler toolchain for some time, I figured this was as good a justification as any and am still looking for a team to jump in with egcs 1.1.1 and start looking at the integration issues. Both Poul-Henning Kamp, John Polstra and Peter Wemm have looked into this a bit already but time constraints will probably prevent any of them from doing anything more substantive than that for awhile. In other words, people are welcome to jump in on this one! :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 20:49:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00805 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 20:49:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fan.net.au (fan.net.au [203.20.92.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00800 for ; Tue, 8 Dec 1998 20:49:22 -0800 (PST) (envelope-from q@fan.net.au) Received: from gromit.fan.net.au (gromit.fan.net.au [203.23.133.34]) by fan.net.au (8.9.1/8.9.1) with SMTP id OAA12947 for ; Wed, 9 Dec 1998 14:49:08 +1000 (EST) Date: Wed, 9 Dec 1998 14:49:08 +1000 (EST) From: Q To: freebsd-hackers@FreeBSD.ORG Subject: Documentation on writing Loadable modules for 3.0 anyone? 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 Howdy all, I am hoping some kind sole out there has some preliminary doco on writing lkm's for FreeBSD 3.0. A little while ago I wrote a FreeBSD 2.2 device driver for my packard bell infra-red receiver. It workes great, but I have now migrated to 3.0 and need to port the lkm to the new interface. Specifically I need to know how to use the ttpoll stuff now that d_select_t isn't used anymore. I haven't spent much time on it yet, but I think it's going to end up taking a while if I have to keep greping through kernel source and other device drivers :) Anyone got an update for the LKM faq? please... :) Seeya...Q -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _____ / Quinton Dolan - q@fan.net.au __ __/ / / __/ / / Systems Administrator / __ / _/ / / Fast Access Network __/ __/ __/ ____/ / - / Gold Coast, QLD, Australia _______ / Ph: +61 7 5574 1050 \_\ SAGE-AU Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 21:36:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04892 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 21:36:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04884 for ; Tue, 8 Dec 1998 21:36:17 -0800 (PST) (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.8/3.6W) with ESMTP id OAA11948; Wed, 9 Dec 1998 14:35:33 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.6W/hotaka/98111120) with ESMTP id OAA20084; Wed, 9 Dec 1998 14:35:32 +0900 (JST) Message-Id: <199812090535.OAA20084@hotaka.csl.sony.co.jp> To: hackers@FreeBSD.ORG Cc: Anto Prijosoesilo Subject: HZ more than 500 in -stable Date: Wed, 09 Dec 1998 14:35:31 +0900 From: Kenjiro Cho Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anto Prijosoesilo reported to me that the 2.2.8 kernel panics with divide by zero in adjtime() when HZ is set to more than 500. The cause of the problem is that "tickadj" is initialized to 0 and this problem was already fixed in -current by bde on Jun 21. Any objections to merge this fix into -stable? (ALTQ and dummynet work better with a higher timer resolution.) --Kenjiro =================================================================== RCS file: /home/ncvs/src/sys/conf/param.c,v retrieving revision 1.27 retrieving revision 1.28 diff -p -u -r1.27 -r1.28 --- src/sys/conf/param.c 1998/05/15 20:10:54 1.27 +++ /home/ncvs/src/sys/conf/param.c 1998/06/21 12:22:35 1.28 @@ -36,7 +36,7 @@ * SUCH DAMAGE. * * @(#)param.c 8.3 (Berkeley) 8/20/94 - * $Id: param.c,v 1.27 1998/05/15 20:10:54 wollman Exp $ + * $Id: param.c,v 1.28 1998/06/21 12:22:35 bde Exp $ */ #include "opt_sysvipc.h" @@ -70,7 +70,7 @@ #endif int hz = HZ; int tick = 1000000 / HZ; -int tickadj = 30000 / (60 * HZ); /* can adjust 30ms in 60s */ +int tickadj = howmany(30000, 60 * HZ); /* can adjust 30ms in 60s */ #define NPROC (20 + 16 * MAXUSERS) #define MAXFILES (NPROC*2) int maxproc = NPROC; /* maximum # of processes */ =================================================================== 1.28 Sun Jun 21 12:22:35 1998 UTC by bde Round tickadj up. This prevents tickadj from being 0 when HZ > 500, which makes adjtime(2) useless and confuses xntpd(8) into refusing to start even when it would use the kernel PLL instead of adjtime(). The result is the same as recommended by tickadj(8), at least when HZ divides 10^6. Of course, you wouldn't want to actually use adjtime() when HZ is large. In the silly boundary case of HZ == 10^6, tickadj == tick == 1 so the clock stops while adjtime() is active. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 8 21:42:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05431 for freebsd-hackers-outgoing; Tue, 8 Dec 1998 21:42:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05426 for ; Tue, 8 Dec 1998 21:42:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id VAA18950; Tue, 8 Dec 1998 21:42:16 -0800 (PST) To: Brian Reichert Cc: hackers@FreeBSD.ORG Subject: Re: sysinstall In-reply-to: Your message of "Tue, 08 Dec 1998 22:51:11 EST." <19981208225111.A19337@numachi.com> Date: Tue, 08 Dec 1998 21:42:15 -0800 Message-ID: <18946.913182135@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I've got time on my hands right now (between contracts), and would > like to see if I could be helpful to this effort... > > If not you, who should I talk to? I'm it for now, I guess. OK, the first thing we need to do is figure out how to get egcs (and the new libg++ it depends on) "contribified" and into the tree. That is to say that: 1. The portions of egcs which constitute the actual compiler (vs its support libs, many of which are already in the tree) need to go unchanged, on a vendor branch, into /usr/src/contrib/gcc. 2. The FreeBSD-specific changes, that is what's produced by the "post-config" scenario, get checked in on the head branch (so we can still bring new versions of egcs in on the vendor branch and just merge our changes in from time to time). 3. The "skeleton" makefiles which go with it, that being what's in /usr/src/gnu/usr.bin/gcc and /usr/src/gnu/lib/libg++ (among a few other bits), need to be updated to match the new contribified egcs. 4. The whole mess needs to be tested with "make world" until everyone is sure that it's actually going to work in place of 2.7.2.1. As you can see, this is no small job but it's pretty critical if we're ever going to drag FreeBSD's compiler technology into the 20th century. As far as I know, both OpenBSD and NetBSD have already completed this step. > PS: On a complete aside, do you know who would know about a FreeBSD > BoF at LISA in Boston this week? Talk to David Greenman - as our sole representative there this year, it's his job to set up the BOF. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 00:04:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17584 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 00:04:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hermes.hrz.uni-bielefeld.de (hermes.hrz.uni-bielefeld.de [129.70.4.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17560; Wed, 9 Dec 1998 00:04:05 -0800 (PST) (envelope-from lkoeller@post.uni-bielefeld.de) Received: from pollux.hrz.uni-bielefeld.de (9134@pollux.hrz.uni-bielefeld.de [129.70.4.58]) by hermes.hrz.uni-bielefeld.de (8.8.6/8.8.6) with ESMTP id JAA29016; Wed, 9 Dec 1998 09:03:46 +0100 (MET) Received: from localhost by pollux.hrz.uni-bielefeld.de with SMTP (8.7.1/16.2) id IAA23097; Wed, 9 Dec 1998 08:03:45 GMT Message-Id: <199812090803.IAA23097@pollux.hrz.uni-bielefeld.de> X-Mailer: exmh version 2.0.2 2/24/98 From: Lars =?iso-8859-1?Q?K=F6ller?= To: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Syslog with ELF problem X-Face: eCcoCV}FjV*O{6>[1$XP/e%]TJhEw2MF33dFh)^HM7Gfd=[/(4+0a$~ Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24998 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 01:48:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA24985 for ; Wed, 9 Dec 1998 01:48:06 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA18514; Wed, 9 Dec 1998 08:39:43 +0100 From: Luigi Rizzo Message-Id: <199812090739.IAA18514@labinfo.iet.unipi.it> Subject: Re: HZ more than 500 in -stable To: kjc@csl.sony.co.jp (Kenjiro Cho) Date: Wed, 9 Dec 1998 08:39:43 +0100 (MET) Cc: hackers@FreeBSD.ORG, antop@netscape.net In-Reply-To: <199812090535.OAA20084@hotaka.csl.sony.co.jp> from "Kenjiro Cho" at Dec 9, 98 02:35:12 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anto Prijosoesilo reported to me that > the 2.2.8 kernel panics with divide by zero in adjtime() when HZ is > set to more than 500. ... > Any objections to merge this fix into -stable? > > (ALTQ and dummynet work better with a higher timer resolution.) of course go for it! luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 02:52:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29833 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 02:52:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.mod.uk (relay.mod.uk [192.5.29.50]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA29828 for ; Wed, 9 Dec 1998 02:52:54 -0800 (PST) (envelope-from druid@atc.dera.gov.uk) Received: from hermes.dra.hmg.gb by relay.mod.uk with local SMTP id ; Wed, 9 Dec 1998 10:43:55 +0000 Received: from atc.dera.gov.uk by hermes.dra.hmg.gb (MX V4.2 VAX) with SMTP; Wed, 09 Dec 1998 10:43:33 GMT Received: from atc.dera.gov.uk by atc.dera.gov.uk (SMI-8.6/SMI-SVR4) id KAA09145; Wed, 9 Dec 1998 10:43:28 GMT Message-ID: <366E5451.D95C8C6D@atc.dera.gov.uk> Date: Wed, 09 Dec 1998 10:43:29 +0000 From: Mark Templeton Organization: ATC Systems Group, DERA Malvern X-Mailer: Mozilla 4.05 [en] (X11; I; SunOS 5.6 sun4u) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Memory holes for ISA device drivers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OS is 2.2.5 Card is on ISA bus, preferably at 0xA00000. How do I create a (physical) memory hole for a card, as the card holds 64k shared memory? The target system BIOS does not support the 15-16M memory hole. pmap_mapdev() maps physical to virtual memory, but does not create a hole. How do I create a memory hole? Mark. -- 0 00000000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 The Druid 0 B1013, DERA Malvern, Internet: Mark.Templeton@atc.dera.gov.uk St Andrews Road, Janet : Mark.Templeton@uk.mod.hermes Malvern, Worcs., WR14 3PS, Phone: +44-1684-894213 United Kingdom, Fax: +44-1684-894109 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 06:39:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20764 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 06:39:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from beowulf.utmb.edu (beowulf.utmb.edu [129.109.59.83]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20759 for ; Wed, 9 Dec 1998 06:39:13 -0800 (PST) (envelope-from bdodson@beowulf.utmb.edu) Received: (from bdodson@localhost) by beowulf.utmb.edu (8.8.8/8.8.6) id IAA03589; Wed, 9 Dec 1998 08:37:11 -0600 (CST) Date: Wed, 9 Dec 1998 08:37:11 -0600 (CST) Message-Id: <199812091437.IAA03589@beowulf.utmb.edu> From: "M. L. Dodson" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hackers@FreeBSD.ORG Subject: Re: sysinstall In-Reply-To: <18396.913171861@zippy.cdrom.com> References: <199812082027.NAA24541@bamboo.verinet.com> <18396.913171861@zippy.cdrom.com> X-Mailer: VM 6.22 under 19.15p7 XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard writes: > > What bits, if any, of sysinstall's successor are currently available? I > > have read in -hackers and -commit about the desire to replace > > sysinstall. I thought I had read that Mike Smith was currently working > > on this. > [deleted] > In any case, the new package system is still very much a WIP and also > has some pretty hefty prerequisites: > > Qt 1.40 or later. > TurboVision 0.6 or later. > gcc 2.8.1 or later (also including egcs). > > The latter is the biggie for most folks since 2.7.2, our current > compiler, has C++ support which is broken in too many ways for Eugene > to write the kind of C++ code he wanted to write (he's a big fan of > templates and MI). Since we've wanted to upgrade our compiler > toolchain for some time, I figured this was as good a justification as > any and am still looking for a team to jump in with egcs 1.1.1 and > start looking at the integration issues. Both Poul-Henning Kamp, John > Polstra and Peter Wemm have looked into this a bit already but time > constraints will probably prevent any of them from doing anything more > substantive than that for awhile. In other words, people are welcome > to jump in on this one! :) > > - Jordan If I might, I would like to suggest that any project along this line look to include g77 as well as C++ as part of the base system. This would help those of us interested in using FBSD for number crunching. I can generate some testing time, including compiling and testing some pretty hefty computational chemistry packages. Unfortunately, I'm a biochemist who knows about computers, not a computer scientist who knows about biochemistry, so my time would only be usefully used in a testing mode. Thanks, Bud Dodson -- M. L. Dodson bdodson@scms.utmb.edu 409-772-2178 FAX: 409-772-1790 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 08:36:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00755 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 08:36:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gvinpin.grad.kiev.ua (KievglavArhit-UTC-28k8.ukrtel.net [195.5.25.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00715 for ; Wed, 9 Dec 1998 08:35:50 -0800 (PST) (envelope-from Ruslan@Shevchenko.Kiev.UA) Received: from Shevchenko.Kiev.UA (kulshedra [10.0.1.99]) by gvinpin.grad.kiev.ua (8.8.7/8.8.7) with ESMTP id SAA15358 for ; Wed, 9 Dec 1998 18:33:49 +0200 Message-ID: <366EC309.4E81E900@Shevchenko.Kiev.UA> Date: Wed, 09 Dec 1998 18:35:54 +0000 From: Ruslan Shevchenko Reply-To: rssh@grad.kiev.ua X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: inclusion of system headers. Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Question: Are exists some reasons, for existing next situation: A.h refer to something, including in B.h, but A.h not include B.h . I think, this is design bug. In FreeBSD such situation, at least with and , which breaks clear compiling of erlang (which yesteday was releasing as open source with NPL-style license). > -DHAVE_FINITE=3D1 -DHAVE_DIRENT_H=3D1 -DSTDC_HEADERS=3D1 -DHAVE_SYS_WAIT_= ... > known-freebsd3.0/gzio.o -c -I/usr/home/rssh/erlang/erlang-47.4.0/erts/sys= > tem/emulator/zlib /usr/home/rssh/erlang/erlang-47.4.0/erts/system/emulato= > r/drv/gzio.c > In file included from /usr/home/rssh/erlang/erlang-47.4.0/erts/system/emu= > lator/sys.unix/driver_int.h:30, > from /usr/home/rssh/erlang/erlang-47.4.0/erts/system/emu= > lator/runtime/driver.h:30, > from /usr/home/rssh/erlang/erlang-47.4.0/erts/system/emu= > lator/drv/gzio.c:29: > /usr/include/sys/uio.h:88: parse error before `readv' > /usr/include/sys/uio.h:88: warning: data definition has no type or storag= Wow, long output... :-) Which seems to be the real cause of the error. The fix is to edit the file erts/system/emulator/sys.unix/driver_int.h and add #include just before the inclusion of sys/uio.h. Thanks for trying it out! P.S, I doubted this message as misc bug-report. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 08:51:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01809 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 08:51:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01804 for ; Wed, 9 Dec 1998 08:51:32 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id LAA43113; Wed, 9 Dec 1998 11:54:59 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 9 Dec 1998 11:54:59 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: rssh@grad.kiev.ua cc: hackers@FreeBSD.ORG Subject: Re: inclusion of system headers. In-Reply-To: <366EC309.4E81E900@Shevchenko.Kiev.UA> 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, 9 Dec 1998, Ruslan Shevchenko wrote: > > Question: > > Are exists some reasons, for existing next situation: > > A.h refer to something, including in B.h, but A.h not include B.h . > > I think, this is design bug. > > In FreeBSD such situation, at least with and , > which breaks clear compiling of erlang (which yesteday was releasing > as open source with NPL-style license). > > I thought the same too, however it was explained to me that several people spent a long time unwinding the headers. >From what i guess the problem of chaning the headers like linux does is: a) you may wish to redefine certain types for odd/masochistic reasons. b) it slows compile time signifigantly c) it's a solution for people who don't really know what goes where, and FreeBSD should encourage good programming practicies. Basically if you RTFM on functions and read most programming texts they will explain what to include and where. Lastly, why not have #include just suck in the whole include/* ? doesn't sound too apetizing now does it? :) Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 09:13:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03656 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 09:13:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gvinpin.grad.kiev.ua (KievglavArhit-UTC-28k8.ukrtel.net [195.5.25.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03628 for ; Wed, 9 Dec 1998 09:13:46 -0800 (PST) (envelope-from Ruslan@Shevchenko.Kiev.UA) Received: from Shevchenko.Kiev.UA (kulshedra [10.0.1.99]) by gvinpin.grad.kiev.ua (8.8.7/8.8.7) with ESMTP id TAA15496; Wed, 9 Dec 1998 19:11:26 +0200 Message-ID: <366ECBDA.BB19E1F2@Shevchenko.Kiev.UA> Date: Wed, 09 Dec 1998 19:13:31 +0000 From: Ruslan Shevchenko Reply-To: rssh@grad.kiev.ua X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Alfred Perlstein CC: rssh@grad.kiev.ua, hackers@FreeBSD.ORG Subject: Re: inclusion of system headers. References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > On Wed, 9 Dec 1998, Ruslan Shevchenko wrote: > > > > > Question: > > > > Are exists some reasons, for existing next situation: > > > > A.h refer to something, including in B.h, but A.h not include B.h . > > > > I think, this is design bug. > > > > In FreeBSD such situation, at least with and , > > which breaks clear compiling of erlang (which yesteday was releasing > > as open source with NPL-style license). > > > > > > I thought the same too, however it was explained to me that several people > spent a long time unwinding the headers. > > >From what i guess the problem of chaning the headers like linux does is: > > a) you may wish to redefine certain types for odd/masochistic reasons. ???? > b) it slows compile time signifigantly ??? #ifndef __A_H #include A.h #endif it is 3 strings of empty cpp output on one header inclusion. Is it really slow compilation ? Where and when it was ? > > c) it's a solution for people who don't really know what goes where, > and FreeBSD should encourage good programming practicies. > Why FreeBSD is not writeln in assembler ? Mininmizing of dependences between different modules is one of axioms of software engeneering. Seriosly. > > Basically if you RTFM on functions and read most programming texts > they will explain what to include and where. > But why to do this work n times, during porting of each software package, if this work can be complete eliminated once. > > Lastly, why not have #include just suck in the whole include/* ? > doesn't sound too apetizing now does it? :) > In general, you want, that "only correct writeln software" must be easy ported to FreeBSD. And you minimize source code compability between FreeBSD and other systems, when software is not writeln in correct esoteric stream ;) More usefull, I think, is maximize source code compability, is better, then create artiffical difficultes for porting. > > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > -- There are operating systems, and then there's FreeBSD. > -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 09:30:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05137 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 09:30:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05116 for ; Wed, 9 Dec 1998 09:30:04 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id MAA43170; Wed, 9 Dec 1998 12:33:49 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 9 Dec 1998 12:33:49 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: rssh@grad.kiev.ua cc: hackers@FreeBSD.ORG Subject: Re: inclusion of system headers. In-Reply-To: <366ECBDA.BB19E1F2@Shevchenko.Kiev.UA> 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, 9 Dec 1998, Ruslan Shevchenko wrote: > > On Wed, 9 Dec 1998, Ruslan Shevchenko wrote: > > > > > > > > Question: > > > > > > Are exists some reasons, for existing next situation: > > > > > > A.h refer to something, including in B.h, but A.h not include B.h . > > > > > > I think, this is design bug. > > > > > > In FreeBSD such situation, at least with and , > > > which breaks clear compiling of erlang (which yesteday was releasing > > > as open source with NPL-style license). > > > > > > > > > > I thought the same too, however it was explained to me that several people > > spent a long time unwinding the headers. > > > > >From what i guess the problem of chaning the headers like linux does is: > > > > a) you may wish to redefine certain types for odd/masochistic reasons. > > ???? Read it again. > > b) it slows compile time signifigantly > > ??? > > #ifndef __A_H > #include A.h > #endif > > it is 3 strings of empty cpp output on one header inclusion. > Is it really slow compilation ? Where and when it was ? uh, no. Usually the #ifndef is inside the included file, which means opening the include files multiple times and parsing them just to abort. > > > > c) it's a solution for people who don't really know what goes where, > > and FreeBSD should encourage good programming practicies. > > > > Why FreeBSD is not writeln in assembler ? > > Mininmizing of dependences between different modules is one of axioms > of software engeneering. Seriosly. Seriously, chain everything off stdio.h, release your own version, call it 'AnnoyingBSD'. (or Lin** :) ) Or, you could make one big header file called "unix.h" > > > > Basically if you RTFM on functions and read most programming texts > > they will explain what to include and where. > > > > But why to do this work n times, during porting of each software > package, if this work can be complete eliminated once. See previous answer. > > > > Lastly, why not have #include just suck in the whole include/* ? > > doesn't sound too apetizing now does it? :) > > > > In general, you want, that "only correct writeln software" must > be easy ported to FreeBSD. And you minimize source code compability > between FreeBSD and other systems, when software is not writeln in > correct esoteric stream ;) > > More usefull, I think, is maximize source code compability, is better, > then create artiffical difficultes for porting. including the correct header files is hardly a portability issue. In fact, when following the FreeBSD include path code will most always compile correctly on Linux/Solaris/other unicies. I didn't make this design decision, Jordan told me about it and that a lot of work was done to get it this way. You can also garner information about a Program by looking at what header files it includes, this would totally defeat the purpose. You may find inconsistancies with what I'm saying, ie. some headers DO include other files, however if you look closely the nested includes are mostly there only to grab FreeBSD specific includes. lastly, what is "writeln" ? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 09:59:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08167 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 09:59:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08157 for ; Wed, 9 Dec 1998 09:59:10 -0800 (PST) (envelope-from fjoe@husky.iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id XAA27190; Wed, 9 Dec 1998 23:58:01 +0600 (NS) X-Authentication-Warning: iclub.nsu.ru: fjoe owned process doing -bs Date: Wed, 9 Dec 1998 23:58:01 +0600 (NS) From: Max Khon X-Sender: fjoe@iclub.nsu.ru Reply-To: Max Khon To: luigi@iet.unipi.it, freebsd-hackers@FreeBSD.ORG Subject: ESS1868 patches 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! Patches for luigi sound driver code to support ESS1868 (and probably ESS688, ESS1668) are available at http://iclub.nsu.ru/~fjoe. Currently these patches are tested only with ESS1868 PNP sound card. 22Khz playback is not supported (only 44Khz stereo was tested -- i just wanted to play my mp3's) -- will be done soon. Full duplex is not supported. Recording stuff was not tested. ESS1668 cards probably need some patches in probing code. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 11:34:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18199 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 11:34:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18194 for ; Wed, 9 Dec 1998 11:34:31 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id LAA46855; Wed, 9 Dec 1998 11:34:26 -0800 (PST) (envelope-from dillon) Date: Wed, 9 Dec 1998 11:34:26 -0800 (PST) From: Matthew Dillon Message-Id: <199812091934.LAA46855@apollo.backplane.com> To: hackers@FreeBSD.ORG Subject: IBM Jikes (java source -> byte code compiler) released in open-source form Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The thing compiles using, in jikesos/jikes/src/Makefile as shown below. It works! I'm impressed! -Matt # g++ definitions (RedHat 5.* - glibc) CC=g++ # use -W to see warnings (should review from time to time) CCREQUIREDFLAGS= -DGNU_LIBC5 -DUNIX -funsigned-char -c -DTYPE_bool -ansi -I. CCDEBUGFLAGS=-DTEST -g CCOPTFLAGS=-O CCFLAGS=$(CCREQUIREDFLAGS) $(CCDEBUGFLAGS) CCFLAGS=$(CCREQUIREDFLAGS) $(CCOPTFLAGS) ERASE=rm -f EXECUTABLE=jikes LD=g++ LDDEBUGFLAGS=-g LDFLAGS=-L. -o$(EXECUTABLE) O=o SYSOBJECTS= Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 12:01:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20467 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 12:01:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20458 for ; Wed, 9 Dec 1998 12:01:25 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id OAA00422; Wed, 9 Dec 1998 14:59:48 -0500 (EST) Date: Wed, 9 Dec 1998 14:59:47 -0500 (EST) From: Chuck Robey To: Matthew Dillon cc: hackers@FreeBSD.ORG Subject: Re: IBM Jikes (java source -> byte code compiler) released in open-source form In-Reply-To: <199812091934.LAA46855@apollo.backplane.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, 9 Dec 1998, Matthew Dillon wrote: > The thing compiles using, in jikesos/jikes/src/Makefile as shown below. > It works! I'm impressed! Can you be a little more detailed about the environment of your test app? JDK?.? ? Any JFC in the app? I'm really curious. > > -Matt > > # g++ definitions (RedHat 5.* - glibc) > CC=g++ > # use -W to see warnings (should review from time to time) > CCREQUIREDFLAGS= -DGNU_LIBC5 -DUNIX -funsigned-char -c -DTYPE_bool -ansi -I. > CCDEBUGFLAGS=-DTEST -g > CCOPTFLAGS=-O > CCFLAGS=$(CCREQUIREDFLAGS) $(CCDEBUGFLAGS) > CCFLAGS=$(CCREQUIREDFLAGS) $(CCOPTFLAGS) > ERASE=rm -f > EXECUTABLE=jikes > LD=g++ > LDDEBUGFLAGS=-g > LDFLAGS=-L. -o$(EXECUTABLE) > O=o > SYSOBJECTS= > > Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet > Communications & God knows what else. > (Please include original email in any response) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 13:52:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03051 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 13:52:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA03042 for ; Wed, 9 Dec 1998 13:52:11 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA22754 for hackers@freebsd.org; Wed, 9 Dec 1998 16:57:06 -0500 From: Bill Paul Message-Id: <199812092157.QAA22754@skynet.ctr.columbia.edu> Subject: Code review request (new MII support) To: hackers@FreeBSD.ORG Date: Wed, 9 Dec 1998 16:57:04 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The past couple of days I've been experimenting with the MII/PHY support code from NetBSD (sys/dev/mii). This code provides support for MII transceivers attached to ethernet controllers. Many (hell, most) of the fast ethernet controllers on the market today include support for MII-compliant transceivers. At the moment, all of the drivers for ethernet cards that use MII transceivers have their own MII support code, and handle autonegotiation and media selection themselves. The result is a fair amount of duplicated code. The NetBSD MII support (which I think is meant to emulate similar support in BSD/OS) allows ethernet drivers to avoid having to deal with the gruntwork of autonegotiation and media selection and reduces code duplication. I also allows PHYs drivers to handle quirks themselves rather than having to put hacks directly into ethernet drivers, and makes it easier to deal with vendors who like to mix and match controllers and PHYs a lot. Getting it to work properly on FreeBSD was complicated by the fact that NetBSD makes copious use of and src/kern/subr_autoconf.c for device configuration, whereas we have all but forgotten about them. (I assume this is because somebody out there has an incredibly spiffy replacement that will do everything they do plus more, right? Right? Uh... hello, is this thing on? *tap* *tap*) Anyway. I have it working okay for now. One of the things I had to do was substitute struct ifnet for struct device in a few places where the MII code expects to find the device struct for its parent device (in this case, an ethernet driver). I also kludged up a glue module to take the place of the autoconfig support that we don't have. My version uses a linker set much like the PCI drivers: each PHY driver adds its set of probe/attach routines to the linker set with DATA_SET(), and the match routine cycles through them all to find a driver that supports a given PHY. The result looks something like this: pn0: <82c168/82c169 PNIC 10/100BaseTX> rev 0x21 int a irq 11 on pci0.10.0 pn0: Ethernet address: 00:a0:cc:3a:5f:fe mii0: OUI 0x1e0400 model 0x0000 rev 0 at pn0 phy 1 lxtphy0: LXT970 10/100 media interface, rev. 0 lxtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: rev 0x06 int a irq 10 on pci0.12.0 vr0: Ethernet address: 00:80:c8:4b:9c:90 mii1: OUI 0x006040 model 0x0000 rev 0 at vr0 phy 8 dvphy0: Davicom 10/100 media interface, rev. 0 dvphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto What I would like to do is add this support to 3.0-current and then convert the drivers that need MII/PHY support to use it. I have a copy of the code at http://www.freebsd.org/~wpaul/MII/mii.tar.gz. This includes the core MII code, PHY drivers, glue routines and two sample ethernet drivers converted to use the MII support (if_pn and if_vr). In order to use the code, you have to do the following: - mkdir /sys/dev/mii - copy everything except if_pn* and if_vr* to /sys/dev/mii - append files.FreeBSD to /sys/conf/files - copy if_pn* and if_vr* to /sys/pci - add the following to your kernel config file: controller mii0 device pn0 device vr0 What I would like are comments and suggestions, particularly about how to improve the way the code is configured into the kernel; what I did for now is just a quick hack to get everything built. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 13:59:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03623 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 13:59:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03614 for ; Wed, 9 Dec 1998 13:59:37 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id NAA51425; Wed, 9 Dec 1998 13:59:01 -0800 (PST) (envelope-from dillon) Date: Wed, 9 Dec 1998 13:59:01 -0800 (PST) From: Matthew Dillon Message-Id: <199812092159.NAA51425@apollo.backplane.com> To: Chuck Robey Cc: hackers@FreeBSD.ORG Subject: Re: IBM Jikes (java source -> byte code compiler) released in open-source form References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Wed, 9 Dec 1998, Matthew Dillon wrote: : :> The thing compiles using, in jikesos/jikes/src/Makefile as shown below. :> It works! I'm impressed! : :Can you be a little more detailed about the environment of your test :app? JDK?.? ? Any JFC in the app? I'm really curious. The apps I compiled up to test it were Java projects I am involved in, JDK based. I was using the JDK's 'java' binary to run them. Oh, I had to create an empty "wchar.h" header file too. jikes seems quite fast at compiling up the Java, and I am very impressed at the cleanliness of the source. If Sun gets its act together and opens up their JDK sources it will be even better. -Matt :> # g++ definitions (RedHat 5.* - glibc) :> CC=g++ :> # use -W to see warnings (should review from time to time) :> CCREQUIREDFLAGS= -DGNU_LIBC5 -DUNIX -funsigned-char -c -DTYPE_bool -ansi -I. :> CCDEBUGFLAGS=-DTEST -g :> CCOPTFLAGS=-O :> CCFLAGS=$(CCREQUIREDFLAGS) $(CCDEBUGFLAGS) :> CCFLAGS=$(CCREQUIREDFLAGS) $(CCOPTFLAGS) :> ERASE=rm -f :> EXECUTABLE=jikes :> LD=g++ :> LDDEBUGFLAGS=-g :> LDFLAGS=-L. -o$(EXECUTABLE) :> O=o :> SYSOBJECTS= :> : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 14:58:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08900 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 14:58:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08893 for ; Wed, 9 Dec 1998 14:58:06 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA12514; Wed, 9 Dec 1998 14:56:39 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma012512; Wed, 9 Dec 98 14:56:14 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA26226; Wed, 9 Dec 1998 14:56:14 -0800 (PST) From: Archie Cobbs Message-Id: <199812092256.OAA26226@bubba.whistle.com> Subject: Re: IBM Jikes (java source -> byte code compiler) released in open-source form In-Reply-To: <199812092159.NAA51425@apollo.backplane.com> from Matthew Dillon at "Dec 9, 98 01:59:01 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 9 Dec 1998 14:56:13 -0800 (PST) Cc: chuckr@mat.net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 So who's doing the jikes port? If nobody, send me the patches and I'll create one. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 15:11:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10041 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 15:11:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10035 for ; Wed, 9 Dec 1998 15:11:29 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA25448; Wed, 9 Dec 1998 15:01:45 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdb25440; Wed Dec 9 23:01:38 1998 Message-ID: <366F010A.FF6D5DF@whistle.com> Date: Wed, 09 Dec 1998 15:00:26 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Ollivier Robert CC: hackers@FreeBSD.ORG Subject: Re: Can we just come to a decision on IPv6 and IPSec? References: <1958.912571118@zippy.cdrom.com> <19981208230955.A16874@keltia.freenix.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This would be wonderful! I hope it can be done.. Maybe we can get some confirmation from one of the KAME guys that they too are serious about this and that they too are willing to sacrifice some of their code for pieces of INRIA code, and visa versa. A roadmap would be nice.. Maybe starting with an estimate on when .h files might be made compatible. julian Ollivier Robert wrote: > > According to Jordan K. Hubbard: > > This fence rail is pointy and cold and I think we're all going to come > > down with an embarrassing medical condition if we keep sitting on it. > > I just got a mail from Francis -- he's at the IETF with also the KAME > developpers -- and he said they've decided to write a unified version of > the IPv6 stack. > > I don't have more details for the moment but if it gets done, it would > solve our problems... [...] Translation: > -=-=- > PS: we took the opportunity of the the presence of all major IPv6 > developpers on *BSD to decide to make a unified version (of the IPv6 > stack not the *BSD :-)). > -=-=- > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 > > 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 Wed Dec 9 15:52:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14772 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 15:52:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14767 for ; Wed, 9 Dec 1998 15:52:11 -0800 (PST) (envelope-from mpro@marketpro.com) Received: from tuna.surfspin.com (root@ip51.surfspin.com [207.211.84.51] (may be forged)) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id PAA27146 for ; Wed, 9 Dec 1998 15:52:12 -0800 (PST) Received: from marketpro.com (dynamic22.pm04.san-rafael.best.com [206.184.127.214]) by tuna.surfspin.com (8.8.8/8.8.8) with ESMTP id PAA00308 for ; Wed, 9 Dec 1998 15:59:30 -0800 (PST) Message-ID: <366F0ECE.F1018624@marketpro.com> Date: Wed, 09 Dec 1998 15:59:10 -0800 From: MarketPro Organization: MarketPro Computer Shows X-Mailer: Mozilla 4.06 [en] (Win98; I) MIME-Version: 1.0 To: freebsd-hackers@freefall.cdrom.com Subject: looking for help Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I need to find a freeBSD programer to help finish a web hosting project. I am located in northern Ca, Petaluma, Santa Rosa, I have a programer but he is only available on weekends, and i sometimes need help before that. This will be an on going project. I hope you can help. Thanks, Ed Knapp Please respond to programer@ev-int.net -- MarketPro Computer Shows For Show Schedule and info contact http://marketpro.com Phone- 800-708-7555 Fax- 415 456-2011 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 17:34:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00445 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 17:34:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (33-sweet.camalott.com [208.239.153.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00401 for ; Wed, 9 Dec 1998 17:34:18 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id TAA27645; Wed, 9 Dec 1998 19:33:37 -0600 (CST) (envelope-from joelh) To: Alfred Perlstein Cc: Dennis , hackers@FreeBSD.ORG Subject: Re: 3.0-RELEASE clear source? References: From: Joel Ray Holveck Date: 09 Dec 1998 19:33:36 -0600 In-Reply-To: Alfred Perlstein's message of "Mon, 7 Dec 1998 11:33:47 -0500 (EST)" Message-ID: <86iufkeq6n.fsf@detlev.UUCP> Lines: 20 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> there is no source to the /usr/bin/clear program, and the binary >> provided in the distribution complains about "bad achitecture". >> Is this program antiquated or is this an oversite? > it's a shell script that wraps 'tput' > #!/bin/sh - > # > # Copyright (c) 1989, 1993 > # The Regents of the University of California. All rights reserved. > # > ...... > exec tput clear And if you still want the source, it is in /usr/src/usr.bin/tput/clear.sh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 17:40:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01260 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 17:40:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-db.dialup.hilink.com.au [203.2.144.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01250 for ; Wed, 9 Dec 1998 17:40:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01712; Wed, 9 Dec 1998 17:23:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812100123.RAA01712@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Paul cc: hackers@FreeBSD.ORG Subject: Re: Code review request (new MII support) In-reply-to: Your message of "Wed, 09 Dec 1998 16:57:04 EST." <199812092157.QAA22754@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 Dec 1998 17:23:44 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The past couple of days I've been experimenting with the MII/PHY > support code from NetBSD (sys/dev/mii). This code provides support > for MII transceivers attached to ethernet controllers. Many (hell, most) > of the fast ethernet controllers on the market today include support > for MII-compliant transceivers. At the moment, all of the drivers for > ethernet cards that use MII transceivers have their own MII support > code, and handle autonegotiation and media selection themselves. The > result is a fair amount of duplicated code. Funny, I remember saying this a while back. Nice to see that someone's doing the real work on it though. 8) > Getting it to work properly on FreeBSD was complicated by the fact that > NetBSD makes copious use of and src/kern/subr_autoconf.c > for device configuration, whereas we have all but forgotten about them. > (I assume this is because somebody out there has an incredibly spiffy > replacement that will do everything they do plus more, right? Right? > Uh... hello, is this thing on? *tap* *tap*) Correct. You want to be talking to Doug Rabson (dfr), and perhaps Nick Hibma (n_hibma) and Nicolas Souchu (nsouch) (all @freebsd.org). We do indeed have a very spiffy new bus infrastructure, which would take to your situation here very well. > What I would like are comments and suggestions, particularly about > how to improve the way the code is configured into the kernel; what I > did for now is just a quick hack to get everything built. To see the new bus code in action, look at eg. sys/dev/iic. Nick was also working on some sample bus/driver code. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 20:41:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27258 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 20:41:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27247 for ; Wed, 9 Dec 1998 20:41:07 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA04742; Wed, 9 Dec 1998 21:41:00 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id VAA20842; Wed, 9 Dec 1998 21:41:00 -0700 Date: Wed, 9 Dec 1998 21:41:00 -0700 Message-Id: <199812100441.VAA20842@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Matthew Dillon Cc: hackers@FreeBSD.ORG Subject: Re: IBM Jikes (java source -> byte code compiler) released in open-source form In-Reply-To: <199812091934.LAA46855@apollo.backplane.com> References: <199812091934.LAA46855@apollo.backplane.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The thing compiles using, in jikesos/jikes/src/Makefile as shown below. > It works! I'm impressed! Yep. I sent email about this yesterday, and if you create a dummy 'wchar.h' it works fine. In the future, java stuff should be posted to FreeBSD-java. (Yes, we have mailing lists for everything. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 20:54:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27937 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 20:48:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27931 for ; Wed, 9 Dec 1998 20:48:06 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA04800; Wed, 9 Dec 1998 21:47:55 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id VAA20933; Wed, 9 Dec 1998 21:47:54 -0700 Date: Wed, 9 Dec 1998 21:47:54 -0700 Message-Id: <199812100447.VAA20933@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Archie Cobbs Cc: dillon@apollo.backplane.com (Matthew Dillon), chuckr@mat.net, hackers@FreeBSD.ORG Subject: Re: IBM Jikes (java source -> byte code compiler) released in open-source form In-Reply-To: <199812092256.OAA26226@bubba.whistle.com> References: <199812092159.NAA51425@apollo.backplane.com> <199812092256.OAA26226@bubba.whistle.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So who's doing the jikes port? If nobody, send me the > patches and I'll create one. It's not really a patch some much as creation of a bogus wchar.h, and a slight modification to a Makefile. Matt, do you want the honors? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 21:31:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02424 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 21:31:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02418 for ; Wed, 9 Dec 1998 21:31:00 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA54229; Wed, 9 Dec 1998 21:30:51 -0800 (PST) (envelope-from dillon) Date: Wed, 9 Dec 1998 21:30:51 -0800 (PST) From: Matthew Dillon Message-Id: <199812100530.VAA54229@apollo.backplane.com> To: Nate Williams Cc: Archie Cobbs , chuckr@mat.net, hackers@FreeBSD.ORG Subject: Re: IBM Jikes (java source -> byte code compiler) released in open-source form Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> patches and I'll create one. : :It's not really a patch some much as creation of a bogus wchar.h, and a :slight modification to a Makefile. : :Matt, do you want the honors? Ok, I'll try. Having never created a port before, this may take a few hours :-) -Matt :Nate : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 21:54:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04722 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 21:54:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04717 for ; Wed, 9 Dec 1998 21:54:28 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id VAA19413; Wed, 9 Dec 1998 21:52:42 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma019409; Wed, 9 Dec 98 21:52:32 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id VAA16802; Wed, 9 Dec 1998 21:52:32 -0800 (PST) From: Archie Cobbs Message-Id: <199812100552.VAA16802@bubba.whistle.com> Subject: Re: IBM Jikes (java source -> byte code compiler) released in open-source form In-Reply-To: <199812100530.VAA54229@apollo.backplane.com> from Matthew Dillon at "Dec 9, 98 09:30:51 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 9 Dec 1998 21:52:32 -0800 (PST) Cc: nate@mt.sri.com, chuckr@mat.net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Matthew Dillon writes: > :Matt, do you want the honors? > > Ok, I'll try. Having never created a port before, this may take a > few hours :-) It's fun & easy! :-) When I did the skip port, the only difficulty I ran into is the requirement that you split the patch into separate 1-file-per-patch patchfiles... that port patches ~70 files. I wrote a little program called 'diffburst' to do this, given the input from "diff -u -r ...". Lemme know if you want it (should I commit it to tools?) Also, "make install; make deinstall" tells you if your PLIST is incorret. I think there's something called "portlint" but I don't know anything about it. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 22:37:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08817 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 22:37:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08812 for ; Wed, 9 Dec 1998 22:37:40 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA66981; Wed, 9 Dec 1998 22:37:33 -0800 (PST) (envelope-from dillon) Date: Wed, 9 Dec 1998 22:37:33 -0800 (PST) From: Matthew Dillon Message-Id: <199812100637.WAA66981@apollo.backplane.com> To: Archie Cobbs Cc: nate@mt.sri.com, chuckr@mat.net, hackers@FreeBSD.ORG Subject: Port tgz for jikes available for comment (was Re: IBM Jikes) References: <199812100552.VAA16802@bubba.whistle.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would appreciate any and all comments on my attempt to create a port for jikes: ( I haven't commited this yet ). Here is the URL to the .tgz of my proposed port. http://www.backplane.com/FreeBSD/ (index) http://www.backplane.com/FreeBSD/jikes-0.41.tgz (actual url) (Note: the MASTER_SITES currently lists my personal web server which, needless to say, is not going to be the official master site since my poor DSL line probably couldn't handle all the downloads. I would need help getting the IBM distribution placed on the correct FreeBSD site). I have no idea whether I've done this right. It seems to work :-) Once I've fixed things in response to the comments, I will commit the port (or should I get specific permission from Satoshi first?). Since IBM seems to be intent on ensuring that people read their license agreement, I have a .if/.endif check for READ_IBM_LICENSE and @echo instructions and abort as appropriate if it isn't set in /etc/make.conf.local. Comments on that methodology would also be appreciated (do I have to set RESTRICTED too ?) IBM hasn't supplied a man page. Use the -h option to jikes for help. The grand result of the port is to install a single program, /usr/local/bin/jikes -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 9 22:51:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10163 for freebsd-hackers-outgoing; Wed, 9 Dec 1998 22:51:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10152 for ; Wed, 9 Dec 1998 22:51:39 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.0/8.9.0) with SMTP id AAA17471; Thu, 10 Dec 1998 00:51:26 -0600 (CST) Date: Thu, 10 Dec 1998 00:51:26 -0600 (CST) From: Steve Price To: Matthew Dillon cc: Archie Cobbs , nate@mt.sri.com, chuckr@mat.net, hackers@FreeBSD.ORG Subject: Re: Port tgz for jikes available for comment (was Re: IBM Jikes) In-Reply-To: <199812100637.WAA66981@apollo.backplane.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, 9 Dec 1998, Matthew Dillon wrote: # Since IBM seems to be intent on ensuring that people read their license # agreement, I have a .if/.endif check for READ_IBM_LICENSE and @echo # instructions and abort as appropriate if it isn't set in # /etc/make.conf.local. Comments on that methodology would also be # appreciated (do I have to set RESTRICTED too ?) There are a number of ways to fix this. Probably the easiest is to require the user fetch the distfile manually, that way we remain clean regardless of what IBM does with their license. Two examples of how this is done are ports/security/bro and ports/security/fwtk. Marking it RESTRICTED at least for now wouldn't hurt either. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 02:15:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03264 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 02:15:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA03244 for ; Thu, 10 Dec 1998 02:14:55 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id MAA13534; Thu, 10 Dec 1998 12:14:01 +0200 (EET) Date: Thu, 10 Dec 1998 12:14:01 +0200 (EET) From: Narvi To: oZZ!!! cc: hackers@FreeBSD.ORG Subject: Re: About Alladin5 chipset... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id CAA03259 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 8 Dec 1998, oZZ!!! wrote: > > Hello! > Does FreeBSD support motherboard with Alladin5 chipset ? > Naturally. Sander There is no love, no good, no happiness and no future - all these are just illusions. > Rgdz, > ïÓÏËÉÎ óÅÒÇÅÊ aka oZZ, > osa@FreeBSD.org.ru > > > 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 Dec 10 07:29:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04427 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 07:29:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wopr.inetu.net (wopr.inetu.net [207.18.13.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04422 for ; Thu, 10 Dec 1998 07:29:21 -0800 (PST) (envelope-from dev@wopr.inetu.net) Received: from localhost (dev@localhost) by wopr.inetu.net (8.8.8/8.8.5) with SMTP id KAA05590 for ; Thu, 10 Dec 1998 10:29:01 -0500 (EST) Date: Thu, 10 Dec 1998 10:29:01 -0500 (EST) From: Dev To: hackers@FreeBSD.ORG Subject: FreeBSD C/C++ Programmer 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'm sorry if this is off-topic. We really need skilled FreeBSD programmers, and I have tried everywhere! IMMEDIATE JOB OPENING INetU (pronouned I Net You) is looking to hire several creative and motived computer professionals. All full-time employees are covered by a comprehensive benefits package including medical benefits and paid vacations. INetU, Inc. 744 Roble Road Suite 70 Allentown, PA 18103 Ph: (610) 266-7441 ext. 101 Fx: (610) 266-7434 E-Mail: jobs@inetu.com Postion Available: UNIX Software Developer Responsibilities: INetU is currently seeking a UNIX C/C++ and PERL programmer to develop our software products. Most of our products have a strong focus on electronic commerce and virtual server technology. The job would include software design, development, testing and documentation. We would prefer someone with 5 to 10 years of experience, but would be willing to speak with anyone who feels they have UNIX programming talent. Required Skills: Fluent in C and C++, Knowledgable in BSD UNIX system calls and socket programming. Accurate software planning and projection skills. Knowledge of Internet protocols (HTTP, FTP and TCP/IP). Web server installation and configuration experience. Strong relational database and SQL skilsl a plus. Strong work ethic. Hours: Full time Please call, fax or apply in person. Dev Chanchani - INetU, Inc.(tm) - http://www.INetU.net Electronic commerce - Web development - Web hosting dev@INetU.net - Phone: (610) 266-7441 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 07:34:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04774 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 07:34:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04759 for ; Thu, 10 Dec 1998 07:33:56 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id QAA20589; Thu, 10 Dec 1998 16:33:25 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA00496; Thu, 10 Dec 1998 16:33:24 +0100 (MET) Message-ID: <19981210163323.A371@follo.net> Date: Thu, 10 Dec 1998 16:33:23 +0100 From: Eivind Eklund To: Matthew Dillon , Archie Cobbs Cc: nate@mt.sri.com, chuckr@mat.net, hackers@FreeBSD.ORG Subject: Re: Port tgz for jikes available for comment (was Re: IBM Jikes) References: <199812100552.VAA16802@bubba.whistle.com> <199812100637.WAA66981@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812100637.WAA66981@apollo.backplane.com>; from Matthew Dillon on Wed, Dec 09, 1998 at 10:37:33PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 09, 1998 at 10:37:33PM -0800, Matthew Dillon wrote: > Since IBM seems to be intent on ensuring that people read their license > agreement, I have a .if/.endif check for READ_IBM_LICENSE and @echo > instructions and abort as appropriate if it isn't set in > /etc/make.conf.local. Comments on that methodology would also be > appreciated (do I have to set RESTRICTED too ?) You know you can force a display of a license for a port (intended just for this situation) by putting pkg/MESSAGE in the port? > IBM hasn't supplied a man page. Use the -h option to jikes for help. > The grand result of the port is to install a single program, > /usr/local/bin/jikes I'd appreciate a 'dummy manpage' saying a couple of brief words about what it is, and saying you can run jikes -h to get help. There might be room for a URL in there, too. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 07:38:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05103 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 07:38:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05096 for ; Thu, 10 Dec 1998 07:38:02 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id HAA00506; Thu, 10 Dec 1998 07:37:13 -0800 (PST) To: Dev cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD C/C++ Programmer In-reply-to: Your message of "Thu, 10 Dec 1998 10:29:01 EST." Date: Thu, 10 Dec 1998 07:37:13 -0800 Message-ID: <502.913304233@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm sorry if this is off-topic. We really need > skilled FreeBSD programmers, and I have tried > everywhere! Understood, but please confine such postings to freebsd-jobs in the future nonetheless. It keeps the signal-to-noise ratio of this mailing list higher if people stick to purely technical topics and it also saves you the embarassment of some engineer-type going: > Allentown, PA 18103 "Hey, isn't that the town that Billy Joel sings about? The place where all the steel industry left and the standard of living plummeted and only a madman would actually want to move *to* rather than away from? That place?" ... which you just don't get as a general rule in freebsd-jobs. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 10:03:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22948 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 10:03:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22942 for ; Thu, 10 Dec 1998 10:03:29 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id KAA92350; Thu, 10 Dec 1998 10:03:18 -0800 (PST) (envelope-from dillon) Date: Thu, 10 Dec 1998 10:03:18 -0800 (PST) From: Matthew Dillon Message-Id: <199812101803.KAA92350@apollo.backplane.com> To: Eivind Eklund Cc: Archie Cobbs , nate@mt.sri.com, chuckr@mat.net, hackers@FreeBSD.ORG Subject: Re: Port tgz for jikes available for comment (was Re: IBM Jikes) References: <199812100552.VAA16802@bubba.whistle.com> <199812100637.WAA66981@apollo.backplane.com> <19981210163323.A371@follo.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> /etc/make.conf.local. Comments on that methodology would also be :> appreciated (do I have to set RESTRICTED too ?) : :You know you can force a display of a license for a port (intended just for :this situation) by putting pkg/MESSAGE in the port? Ahhh.. ok, I'll do that. :> IBM hasn't supplied a man page. Use the -h option to jikes for help. :> The grand result of the port is to install a single program, :> /usr/local/bin/jikes : :I'd appreciate a 'dummy manpage' saying a couple of brief words about what :it is, and saying you can run jikes -h to get help. There might be room for :a URL in there, too. : :Eivind. No problem. If I understand bsd.port.mk properly, I should be able to clear MASTER_SITES and it will look on ftp.freebsd.org. Presumably we can put IBM's .tgz archive there. I'm going to go ahead and commit it that way. How do we install a distribution (or have a distribution installed) on ftp.freebsd.org? -Matt :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 10:45:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28143 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 10:45:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28075 for ; Thu, 10 Dec 1998 10:45:33 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id SAA15255; Thu, 10 Dec 1998 18:45:22 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id MAA00471; Thu, 10 Dec 1998 12:09:45 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199812101209.MAA00471@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Max Khon cc: luigi@iet.unipi.it, freebsd-hackers@FreeBSD.ORG Subject: Re: ESS1868 patches In-reply-to: Your message of "Wed, 09 Dec 1998 23:58:01 +0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Dec 1998 12:09:44 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hi, there! > > Patches for luigi sound driver code to support ESS1868 (and probably > ESS688, ESS1668) are available at http://iclub.nsu.ru/~fjoe. > Currently these patches are tested only with ESS1868 PNP sound card. > 22Khz playback is not supported (only 44Khz stereo was tested -- i just > wanted to play my mp3's) -- will be done soon. Full duplex is not > supported. Recording stuff was not tested. ESS1668 cards probably need > some patches in probing code. I've just tried this on a Sony laptop - it works well, and stops my mic from screaming (feedback) murder if I haven't already switched it down. I'll commit the changes (with a couple of compiler warnings fixed) tonight. > /fjoe Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 13:56:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24424 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 13:56:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24417 for ; Thu, 10 Dec 1998 13:56:14 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id PAA27450 for ; Thu, 10 Dec 1998 15:56:01 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812102156.PAA27450@ns.tar.com> From: "Richard Seaman, Jr." To: "hackers@freebsd.org" Date: Thu, 10 Dec 98 15:56:01 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: pread/pwrite Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know if there is any interest in X/Open pread, pwrite calls. Essentially, they implement atomic seek/write and atomic seek/read calls. They are more useful in threaded apps where you would need a file lock between a seek/write or seek/read, but even in single threaded apps can allow you to avoid a syscall. Attached is an implementation. If there is interest, and if the implementation meets with approval, I'll submit a PR. Or, perhaps someone would want to commit it directly. I welcome any comments. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 13:57:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24703 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 13:57:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24697 for ; Thu, 10 Dec 1998 13:57:29 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id PAA27463 for ; Thu, 10 Dec 1998 15:57:22 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812102157.PAA27463@ns.tar.com> From: "Richard Seaman, Jr." To: "hackers@freebsd.org" Date: Thu, 10 Dec 98 15:57:21 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=_=_=IMA.BOUNDARY.F3ROVL138764=_=_=_" Subject: Re: pread/pwrite Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --_=_=_=IMA.BOUNDARY.F3ROVL138764=_=_=_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Thu, 10 Dec 98 15:56:01 -0600, Richard Seaman, Jr. wrote: >I don't know if there is any interest in X/Open pread, pwrite >calls. Essentially, they implement atomic seek/write and >atomic seek/read calls. They are more useful in threaded >apps where you would need a file lock between a seek/write >or seek/read, but even in single threaded apps can allow >you to avoid a syscall. > >Attached is an implementation. If there is interest, and >if the implementation meets with approval, I'll submit >a PR. Or, perhaps someone would want to commit it directly. > >I welcome any comments. Whoops. Forgot the attachment. --_=_=_=IMA.BOUNDARY.F3ROVL138764=_=_=_ Content-Type: application/octet-stream; name="preaddiffs.gz" Content-Transfer-Encoding: base64 H4sICPlBcDYAA3ByZWFkZGlmZnMA7Vp7U9tIEv/bfIoOe5UDIz8k2WCcI1UEnD3XEuyyzT5qb0sl pJGtQ5a0GhmWy+a7X/fMSJYcmYVLyO7dLQVoNNM909P964dGGoYu+6UPfugEK5e1VqHPU7e52Dn5 9J+dydkUPD9gfWgtoiVrhc4tb/HEaW2upt3uJCxNfHbrh3NI8ML9KAS9aRg7ru950HCgkdAt5ALW 6/X8pqYfH/da7aOWroNu9o1uv31cE9yNRmODSjdaehsMvd8x+m2Tpin+iGn19rGm6x0QHTSD7DgG bDd2ANgvKUtC1FkKUZz6oavRlSWJuOLvKyTC0RrMGd2CZY339rBDA2dhJ1AHJwp5Cj/+pKmW7N7f J8adA/jK99AsHlyOrKvL4XR2bo0ng1P8/91kOBsgAef+v5iFC8QJs10oLHAb+S7UNZAEKJDnWSlN XGS6S/yUFaUSQjzA+hUL0Q7YQPmUcDVrPJoOv7emo6vJ2UD2i24L5T2zLOzhabJyUkj9Jbu1g1c1 /GnVgbOAOemesQ/11s5Qwi/wr1v457T4PW+9s28YwaaJMHleHG5ddisgu0clQHaPoCQtoafYoSCn t4wOtHt9HYHZq4lZCFYVlBk4EcK6UQ1Ow9B0oyfBCfDuYnj5zfTgZBlEzk3TgOUqlK3iWLQK0yb5 jmoVxmI7XaD5PRz21u2dFzkBAQwH6XJb4kyYcysGnFsviZaqqS5LPi8RcwQQDtFFDEGhI402SNN4 7stBbCVxU7pxtnHlhF9446BuY3n9nfRQCQjT1HTzeBMQCGnHDgJkt6y8XRhH3wwdO2W0/3W7QHBn +6Q7upjqqi6d8m1MQhYUJ6ILjdFVYqbpe/ACo4MfMncPo9pYb7dNS3+zXxTYWTDXwohpxYkfIe+9 tbR/oe1XDPghDvwDuWu/wZYkYgzDHEswCGVYUjrbwNIfR2eQdcSq8QdTYlXcVp7x5SK2XHB7rC6H auXBwmdkk2LuUautt0yMuUbfPO6bIjoLiKxJHhWWO12t215XDHRrZPBqvk2z5CvuQjE57FIB4e7C rky81ysP25IMwuv7lPHdDeYDwRw/lht2RQqnRI4hZFewV0lyu55MVgIqcfvRLXOgjpddSYEtJ0yF VNMFnA+mZ5PheDYcXarJJjhZpXaOe5re7mYhKo64n6KNmgCzBQNE1IqhkJDiTRwJlIHNeeT46F8u 3PnpAvjKWYAdInd0/U9GwnEM68obmrT+OEZ/uorR9EjrMM69VYCVzTIOGC2mFTaMTTt0ixrANoJo hVUdCRGultcoA4okFAm2k64wFtxLuyErxIHtoGi+pEfleyxpqlqxjbXiYWb7Z9wrzYeXHBLY9jAm 0WoQs8SLkiUX63B7yWgPNGDzoh4OQMNq1mFYo6YLGxdKRT8HymSCd+7fsjDfhYCQrQCFNyRutBL1 azgn9yMWctxsb00qZ0ncgwdNc5CLpBVB/lx2qkyj3Y6md48LRf9hV9OPemsnXosgSw2hyW9tcKGZ b3KoBIvCRrogclwc41ViJ/eljR2QTX1SwJKFZHhbmIpocMaMJstBinW8ZnVWSYKMuNUwSksTqa1u rk5Xx0qayncng9nV5BK+Pb24Gkyxb+gVTKMJUeA31ItSSFMgJqVxqZtAgLVMI/IahAOtWteHWMod 5jUsbRmfnsKIHps4lTuQRrgR16cEK7aDw1Eu/GAyGU2mCvqTbTi584NAbgq1gBbDvfWlYXu6pvfW hv3U1bWSEz5alCrFGHpbM/TuGoSGiR2dXNaxnaQqeoglbArJIsqgt3FAV+S+K2WOk4jM+Vc0W4Bo FdHFdt0E+4DH6BUCVYMgh+5pwCMNNlC6tO8zh4vCPHB5EU55J0xNmsHNINebABqpPYfGne9iEBsk 1DlM4c3P2IbB8BLBhl0zifJiFLGT+YrQK3wixBCJxVGZeToejgeKTXnAZtBEr/FjlDCBt8O3I2Es 3Jw02XQwgNOL6Yhuv0/AXcVggFZZxGTl1perYtSKW8uYw1IZc5hVhgIvqv1xIdNp14iTIFSgeYZK Rh4lbNQPTy1onjjJY+oaWUh/rsLmO5qtOpTpmCWMgr50/QgfLdqZxsiB5PY8dofBVEZSTLYUHX5e MY4AplMfcivlaLJGWK5Q3mtKJUihybCiqJY2RicZmKkjwmRvi+TOMRkHLnFJKKFrLGT25v51wNZp SpQOReXjzaNqh4O1cquKBzFATowR9PNUD9Iiw3fji8G7weXslIwCl6OZyFq0GXgw527PPkcFkx1h R69bzPQSPp+a6jM9PZjrM6LNZF9g/tzZfnspVllW3S18LEgRvUzoJWWhTJXr9A8j5EvufI5YgYZe HMxxOw+iaztAdCe+jWDcYppjrLmKJ6899KbjTmaaJ+TnouMiUssmKSbp3NQiS3u2H+QiF7Eoh6Xz ISoEZskA3pZMbvQ0wzQLmbyDHYf5c4Fwcq7sV8rldpJgzMAIlXiYZEmBYBqNa/QukmNO9etDiVsG m//V1O1hmA6qkreV5Ae4XyZ3Fxbcmrp1s5S7dTM/8hUYyW7U64vDlt7B9EGpudOpCe7iKfHm6wuz 3z6qht6xZubP2rXlTRi5zQhCO4x4wFhMbY/zWwcbmDpCvMQICryII49InXhG6xPNSB4SZeeZkToV uvdZQPTyQF805KlmlB1nKkaEChr8JooF0WKVutEdLcv9ucwsqh2kPLWdG8H2Atn8eVFomoKleSO2 /QRv5NlapKqcKDtAo2JeHJnJN02w+5f3zbOryflw8qHVbMriq3j8vruNeGmHG4TCmVHFuSv/v6pY ThGrLamDymdUvPJ4qplvWBJS8WzNWcgS32k+84ui6jW3+n2n7PcdE8qykpeWeoq+3db7XbNvHNbE PIS2raQPvygysaoxi2UOdhjtvMz5IC3VqmNQhro6VcSlUraErBChV3Tr15HW9Icp/Y0no9nI+rtF RYssqAWzhcmAw3vsrdHLT8+lN4c1KuNrVMaLO/UKUhTy1JH9yIIeVGKhkQ+l946tOpxOvp5eTQfn UiZcAf+LdfdiDVZ2vC/mz+SJsL6PxZIJm/ucEvjHstaRjWjeV9GJ5F/3qiehQZdxXMRzYziBuPE6 ttSOFcnKj8DGf8U++eBh40X0BhHixqE3sCIZ4zxt0Z9pA+s+bL6SJiALfDObnJ4NPprwBkEop1y/ qCUreLC3t7eic/t93Gnjtefuw+sTQJGpbYW0Cw6//krEZIU9j/aSDUdi+EfF+dM+nJzA5dXFRZkB xywvwOLhJbyll9SCrC2MUVPlx97gzen5W/EiWcgkmdJ7zPkvTuB89sN4YH17OTofbHCJ0kGykcqa +Gdd21hjnsCeQ2cZltpXhq6cKsCnjhMQYznUamSMJv5ZSIGjL3MzFAfQGjiml/slKrG/oeebWE8O r2F4ObPenX6/Ib+om/bLUyWM42PtdtmSOxy8Go4s0mV5iLO5F8zVMHrCZDpGMJRpCPgCj5WgEb5e Q2fHDaSJ7WDY0vAJ75aqdieK76lIFIiSZK1srzjDeIR7JE/DtvX14HI42pe7ldjDJe1NCNakLjd2 KjFNMBMoWDt8rdiR8RWGBZozP9mrK+qY44XUarv7CCwNzYp60NTsTsLcfSUo8W+YAdFHMr58CdnE J/j4MJjOTiczhXIB8/UgKmGCI4We70ZXF+dvLkZn36h1amVfpgUaJ1BeuWq/Dzj7dhuQ7Lks7dwi mC38aE8EJbIzkxGS3FjLwYWqkrbTCiGo/LVHTcyAeMbC/sf2TyDUpeKhxPia6YMMOi0qOhFhU3w4 o3j5cVYBkVVge1aprGmPuprRKxyzmB1T66w/yUG1x6KYCUg/0+HXKnTgCOW57VZ4fl2Lb3a0HEvP pHSZw+XDX0HdT8nhgrk6iW+cyH1SKleZW6z21NRdEPGPnbv/2zK3AOmfqfvzpG6hzD9z92Nzt3Dq 7clbevjvlb7FumtyAWtJV5lvDijf/CdZHzYsDk/JRPCkTFTxHE2pgjeXNoXJL/ckXVx1+1c8G5/x dGFTXvU0XezLv7ukD4KNfgcfkulErdvNnqcriB/xZuxI1zpHhTNd2ZE/UZvmYW06O6+9mZ7X3ovP g+mQhtRAn9kCmUF0qk9rVYbMPrhVb7c0eaCDPypRcM9auGkCdfqfsda5IhYTYxDn+6/EE71pHm3I cBO4/H4pJUBRfCWFs3Szr4VdO7UF+wGy9wS7+LYXJ1Av1dSDdraLvBAoy17eVz7jcfWMsgDIptyo MH5zYgXiFU+a137YSv04+3vuj9crl9x+FFQ+CQIpIKFJtNSb217L6EK7228bfZ3e3HYEvHKKR6Gz a2jdwmkP3ebl8VfZCdvf+DxN75uL19Qpg7384lx+XbT9i/PyJCLyqVnWvamL0e7jzsC/pt5/AxUc 6lpqMAAA --_=_=_=IMA.BOUNDARY.F3ROVL138764=_=_=_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 14:21:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28407 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 14:21:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alive.znep.com (sense-sea-MegaSub-1-222.oz.net [216.39.144.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28394 for ; Thu, 10 Dec 1998 14:21:36 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id OAA12834; Thu, 10 Dec 1998 14:20:22 -0800 (PST) (envelope-from marcs@znep.com) Date: Thu, 10 Dec 1998 14:20:22 -0800 (PST) From: Marc Slemko To: "Richard Seaman, Jr." cc: "hackers@freebsd.org" Subject: Re: pread/pwrite In-Reply-To: <199812102156.PAA27450@ns.tar.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 Thu, 10 Dec 1998, Richard Seaman, Jr. wrote: > I don't know if there is any interest in X/Open pread, pwrite > calls. Essentially, they implement atomic seek/write and > atomic seek/read calls. They are more useful in threaded > apps where you would need a file lock between a seek/write > or seek/read, but even in single threaded apps can allow > you to avoid a syscall. > > Attached is an implementation. If there is interest, and > if the implementation meets with approval, I'll submit > a PR. Or, perhaps someone would want to commit it directly. > > I welcome any comments. (not necessarily addressed specifically at pread/pwrite, but it does apply to it because of how it is used...) Where is the locking if multiple threads are reading and/or writing from or to the same descriptor at the same time? If you have x threads reading from a descriptor opened from a file on disk, do x-1 of them have to wait until the first one finishes before they can do anything? What about with mixed reading/writing? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 14:28:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29623 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 14:28:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29615 for ; Thu, 10 Dec 1998 14:28:49 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id RAA46180; Thu, 10 Dec 1998 17:32:35 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 10 Dec 1998 17:32:35 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Marc Slemko cc: "Richard Seaman, Jr." , "hackers@freebsd.org" Subject: Re: pread/pwrite 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, 10 Dec 1998, Marc Slemko wrote: > On Thu, 10 Dec 1998, Richard Seaman, Jr. wrote: > > > I don't know if there is any interest in X/Open pread, pwrite > > calls. Essentially, they implement atomic seek/write and > > atomic seek/read calls. They are more useful in threaded > > apps where you would need a file lock between a seek/write > > or seek/read, but even in single threaded apps can allow > > you to avoid a syscall. > > > > Attached is an implementation. If there is interest, and > > if the implementation meets with approval, I'll submit > > a PR. Or, perhaps someone would want to commit it directly. > > > > I welcome any comments. > > (not necessarily addressed specifically at pread/pwrite, but it does > apply to it because of how it is used...) > > Where is the locking if multiple threads are reading and/or writing > from or to the same descriptor at the same time? If you have x > threads reading from a descriptor opened from a file on disk, do > x-1 of them have to wait until the first one finishes before they can > do anything? > > What about with mixed reading/writing? >From looking at the diffs what I think what he implemented was a seek+(write|read) in one syscall. Meaning you do not have to lock an fd when seeking and then writing since it's one syscall it's atomic. This saves on syscalls in general, and helps thread coders save on locking overhead. (Basically if you plan to seek, then read/write, unless you lock on the fd, you risk another thread moving the file pointer out from under you.) plus... solaris and IRIX have it, we should too, doncha think? Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 14:31:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29969 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 14:31:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alive.znep.com (sense-sea-MegaSub-1-222.oz.net [216.39.144.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29964 for ; Thu, 10 Dec 1998 14:31:49 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id OAA12874; Thu, 10 Dec 1998 14:30:34 -0800 (PST) (envelope-from marcs@znep.com) Date: Thu, 10 Dec 1998 14:30:34 -0800 (PST) From: Marc Slemko To: Alfred Perlstein cc: "Richard Seaman, Jr." , "hackers@freebsd.org" Subject: Re: pread/pwrite 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, 10 Dec 1998, Alfred Perlstein wrote: > On Thu, 10 Dec 1998, Marc Slemko wrote: > > > On Thu, 10 Dec 1998, Richard Seaman, Jr. wrote: > > > > > I don't know if there is any interest in X/Open pread, pwrite > > > calls. Essentially, they implement atomic seek/write and > > > atomic seek/read calls. They are more useful in threaded > > > apps where you would need a file lock between a seek/write > > > or seek/read, but even in single threaded apps can allow > > > you to avoid a syscall. > > > > > > Attached is an implementation. If there is interest, and > > > if the implementation meets with approval, I'll submit > > > a PR. Or, perhaps someone would want to commit it directly. > > > > > > I welcome any comments. > > > > (not necessarily addressed specifically at pread/pwrite, but it does > > apply to it because of how it is used...) > > > > Where is the locking if multiple threads are reading and/or writing > > from or to the same descriptor at the same time? If you have x > > threads reading from a descriptor opened from a file on disk, do > > x-1 of them have to wait until the first one finishes before they can > > do anything? > > > > What about with mixed reading/writing? > > >From looking at the diffs what I think what he implemented was a > seek+(write|read) in one syscall. > > Meaning you do not have to lock an fd when seeking and then writing since No, I'm talking about how the kernel handles it. It needs to do various amounts of locking in various areas. When there are kernel threads that people are writing multithreaded programs to use, this matters a lot. Yes, pwrite and pread are good to have. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 14:37:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00620 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 14:37:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from satty.npi.msu.su (satty.npi.msu.su [158.250.20.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00602 for ; Thu, 10 Dec 1998 14:37:49 -0800 (PST) (envelope-from dima@zippy.machaon.ru) Received: from zippy.machaon.ru ([195.230.75.134]) by satty.npi.msu.su (8.9.1a/8.9.1) with ESMTP id BAA17124; Fri, 11 Dec 1998 01:37:13 +0300 (MSK) Date: Fri, 11 Dec 1998 01:37:12 +0300 (MSK) From: Dmitry Khrustalev To: "Richard Seaman, Jr." cc: "hackers@freebsd.org" , dima@bog.msu.su Subject: Re: pread/pwrite In-Reply-To: <199812102156.PAA27450@ns.tar.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 Thu, 10 Dec 1998, Richard Seaman, Jr. wrote: NetBSD uses: 173 STD { ssize_t sys_pread(int fd, void *buf, \ size_t nbyte, int pad, off_t offset); } 174 STD { ssize_t sys_pwrite(int fd, const void *buf, \ size_t nbyte, int pad, off_t offset); } -Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 14:42:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01320 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 14:42:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01312 for ; Thu, 10 Dec 1998 14:42:33 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.0/8.9.0) with SMTP id QAA28989; Thu, 10 Dec 1998 16:42:13 -0600 (CST) Date: Thu, 10 Dec 1998 16:42:13 -0600 (CST) From: Steve Price To: "Richard Seaman, Jr." cc: "hackers@freebsd.org" Subject: Re: pread/pwrite In-Reply-To: <199812102157.PAA27463@ns.tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can you send this patch as a followup to kern/8011? Seems someone else has an interest in this too and may be able to help you test it. -steve On Thu, 10 Dec 1998, Richard Seaman, Jr. wrote: # On Thu, 10 Dec 98 15:56:01 -0600, Richard Seaman, Jr. wrote: # # >I don't know if there is any interest in X/Open pread, pwrite # >calls. Essentially, they implement atomic seek/write and # >atomic seek/read calls. They are more useful in threaded # >apps where you would need a file lock between a seek/write # >or seek/read, but even in single threaded apps can allow # >you to avoid a syscall. # > # >Attached is an implementation. If there is interest, and # >if the implementation meets with approval, I'll submit # >a PR. Or, perhaps someone would want to commit it directly. # > # >I welcome any comments. # # Whoops. Forgot the attachment. # # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 14:46:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01777 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 14:46:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01770 for ; Thu, 10 Dec 1998 14:46:33 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id RAA46208; Thu, 10 Dec 1998 17:50:35 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 10 Dec 1998 17:50:35 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Marc Slemko cc: "hackers@freebsd.org" Subject: Re: pread/pwrite 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, 10 Dec 1998, Marc Slemko wrote: > > > (not necessarily addressed specifically at pread/pwrite, but it does > > > apply to it because of how it is used...) > > > > > > Where is the locking if multiple threads are reading and/or writing > > > from or to the same descriptor at the same time? If you have x > > > threads reading from a descriptor opened from a file on disk, do > > > x-1 of them have to wait until the first one finishes before they can > > > do anything? > > > > > > What about with mixed reading/writing? > > > > >From looking at the diffs what I think what he implemented was a > > seek+(write|read) in one syscall. > > > > Meaning you do not have to lock an fd when seeking and then writing since > > No, I'm talking about how the kernel handles it. It needs to do various > amounts of locking in various areas. When there are kernel threads that > people are writing multithreaded programs to use, this matters a lot. > > Yes, pwrite and pread are good to have. I would think it only needs to lock the fd. without pwrite/pread: higher level lock ----- | seek() -> locks then unlocks fd | .... | read/write() -> locks then unlocks fd unlock ---- with pwrite/pread: p(read|write)() -> locks fd It makes sense, especially since generally the only reason for a seek is to read or write data. You can save 2 spinlocks with pread/pwrite, the single lock may be held longer but not enough to be an issue afaik. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 16:43:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17603 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 16:43:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA17598 for ; Thu, 10 Dec 1998 16:43:11 -0800 (PST) (envelope-from jrs@enteract.com) Received: (qmail 13357 invoked from network); 11 Dec 1998 00:43:04 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 11 Dec 1998 00:43:04 -0000 Date: Thu, 10 Dec 1998 18:43:04 -0600 (CST) From: John Sconiers To: freebsd-hackers@FreeBSD.ORG Subject: XWindows programing 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 Greetings, can some one point me to some info on xwindows programming. Starting a project and looking to find out somebasic and intermediate stuff. Thanks JOHN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 17:54:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24299 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 17:54:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24294 for ; Thu, 10 Dec 1998 17:54:26 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id UAA60954; Thu, 10 Dec 1998 20:53:23 -0500 (EST) Date: Thu, 10 Dec 1998 20:53:23 -0500 (EST) From: Chuck Robey To: John Sconiers cc: freebsd-hackers@FreeBSD.ORG Subject: Re: XWindows programing 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, 10 Dec 1998, John Sconiers wrote: > Greetings, > > can some one point me to some info on xwindows programming. Starting > a project and looking to find out somebasic and intermediate stuff. Several different approaches you could take, depending on how hard your head is. I'll try to summarize, but I just know I'm going to miss someone's favorite ... oh, well ... 1. You could use a script language type approach, like tcl. This hides most of the horrible detail, so if you're more worried about getting the task done than in pure learning, such an approach is pretty good. Drawbacks include some definite loss of efficiency, but it's much less severe than it might sound, because most GUI programming isn't all that speed dependent. 2. One step below, find a language like Java. Does all the graphics stuff, about the same level of efficiency as well written tcl. I personally like it better than tcl, because I think the syntax is a lot more regular, and the library support is fantastic. Very good support via public tools AND very good commerical support, too. Drawbacks as in tcl, and it still hides most of the detail. Oh, yeah, extremely portable, too. 3. One big step back down are libraries like gnome, kde, V, I won't even try to name them all here. Usually done in C++, these make building the code a lot more simple, because all the X calls are wrapped up in classes that do a good job of setting defaults. If you like C++, this is a good choice. 4. Next step down is going to C, where the X calls are really written in. I'm going to suggest at this level, the Motif libraries, because the widgets are written more regularly, documented much better, and your choice of widgets to use is wider. You are going to have to deal with all those lousy defaults, but there is a wealth of Motif code out there, and if you MUST go down to this level, you'll appreciate Motif, and see why people use it. 5. Bottom level, using the X toolkit (Xt) libraries. Looks something like Motif code, but the choices of widgets are more restricted. Consider it Motif programming for masochists. This is in C, and probably the best docs are the LARGE set of manuals from O'Reilly. You *could* be crazy and suggest that there's one more step down, the X libs themselves. I think I reserve that for folks writing new toolkits, people with too much time on their hands. If you pick a level here, reading suggestions could be made, many folks reading this have already tried what you're going to do, and have favorites to suggest. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 18:56:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00887 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 18:56:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00878 for ; Thu, 10 Dec 1998 18:56:26 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id TAA00715; Thu, 10 Dec 1998 19:56:18 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpd000682; Thu Dec 10 19:56:14 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id TAA12902; Thu, 10 Dec 1998 19:56:10 -0700 (MST) From: Terry Lambert Message-Id: <199812110256.TAA12902@usr09.primenet.com> Subject: Re: Wchar support in FreeBSD To: kaleb@ics.com (Kaleb S. KEITHLEY) Date: Fri, 11 Dec 1998 02:56:10 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <366D9BB8.CB2D98FF@ics.com> from "Kaleb S. KEITHLEY" at Dec 8, 98 04:35:53 pm X-Mailer: ELM [version 2.4 PL25] 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 > > > > Is there any 3rd party libraries that support the 'wchar' stuff? > > > Do a mailing list search on "wchar.h functions from Solaris/Linux". There > > > was a thread where Terry claimed that XView 3.2 contained wchar support. > > > > Thanks for the pointer! > > Libc has the basic stuff: wcslen, mbstowcs, wcstombs, etc. > > The rest, e.g. wcscat, wcscpy, etc, you can roll your own on -- there's > no rocket science involved. I sent a copy of the XWchar.tar.Z code to Nate under seperate cover. I also pointed him to the OMRON corporation patches, which add needed modifications for Japanese and other multibyte languages. Since it is very hard to find this, I will duplicate the pointer here: http://ftp.umu.se/pub/unix/src/X11R5_ftp/contrib-fixes/Xwchar/ 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 Dec 10 19:36:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05448 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 19:36:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05433 for ; Thu, 10 Dec 1998 19:36:37 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (lavender.rad.cc.keio.ac.jp [131.113.16.115]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id MAA23111; Fri, 11 Dec 1998 12:36:10 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.8.8/3.6W) id MAA14177; Fri, 11 Dec 1998 12:36:09 +0900 (JST) Date: Fri, 11 Dec 1998 12:36:09 +0900 (JST) Message-Id: <199812110336.MAA14177@lavender.yy.cs.keio.ac.jp> To: brian@Awfulhak.org Cc: fjoe@husky.iclub.nsu.ru, luigi@iet.unipi.it, freebsd-hackers@FreeBSD.ORG, sanpei@sanpei.org, fwkg7679@mb.infoweb.ne.jp Subject: Re: ESS1868 patches In-Reply-To: Your message of "Thu, 10 Dec 1998 21:09:44 JST". <199812101209.MAA00471@keep.lan.Awfulhak.org> From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG brian@Awfulhak.org wrote >> > Patches for luigi sound driver code to support ESS1868 (and probably >> > ESS688, ESS1668) are available at http://iclub.nsu.ru/~fjoe. >> > Currently these patches are tested only with ESS1868 PNP sound card. >> > 22Khz playback is not supported (only 44Khz stereo was tested -- i just >> > wanted to play my mp3's) -- will be done soon. Full duplex is not >> > supported. Recording stuff was not tested. ESS1668 cards probably need >> > some patches in probing code. >> >> I've just tried this on a Sony laptop - it works well, and stops my >> mic from screaming (feedback) murder if I haven't already switched it >> down. Mr. Kurosawa and I are developing Sound driver for ESS18xx with Luigi driver. Latest snapshot is in experimental directory of 2.2.8-RELEASE: ftp://ftp.freebsd.org/pub/FreeBSD/2.2.8-RELEASE/xperimnt/ESS/ But our current driver has problem, I think fjoe's drive also have same problem at heavy load. Current Problem: Some time (CPU was heavy load?), sound change to white noise. And also with using mpg123 player and selected some files, when one file is ended and change to another file, also sound change to white noise... --- Our source code is managed by CVS. http://www.jp.freebsd.org/cgi/cvsweb.cgi/ESS/?cvsroot=freebsd-jp and you can get latest snap files via CVSup from cvsup.jp.FreeBSD.ORG, jp-ess as collection name. Cheers. MIHIRA Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 21:48:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18916 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 21:48:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (56-sweet.camalott.com [208.239.153.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18910 for ; Thu, 10 Dec 1998 21:48:47 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id XAA35518; Thu, 10 Dec 1998 23:48:24 -0600 (CST) (envelope-from joelh) To: Alfred Perlstein Cc: rssh@grad.kiev.ua, hackers@FreeBSD.ORG Subject: Re: inclusion of system headers. References: From: Joel Ray Holveck Date: 10 Dec 1998 23:48:22 -0600 In-Reply-To: Alfred Perlstein's message of "Wed, 9 Dec 1998 12:33:49 -0500 (EST)" Message-ID: <8667bjgrfd.fsf@detlev.UUCP> Lines: 17 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> b) it slows compile time signifigantly >> it is 3 strings of empty cpp output on one header inclusion. >> Is it really slow compilation ? Where and when it was ? > uh, no. Usually the #ifndef is inside the included file, which means > opening the include files multiple times and parsing them just to abort. Many modern compilers (including gcc) will detect when an entire header file is #ifdef'd, and DTRT. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 22:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19684 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 22:01:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gvinpin.grad.kiev.ua (KievglavArhit-UTC-28k8.ukrtel.net [195.5.25.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19676 for ; Thu, 10 Dec 1998 22:01:39 -0800 (PST) (envelope-from Ruslan@Shevchenko.Kiev.UA) Received: from Shevchenko.Kiev.UA (kulshedra [10.0.1.99]) by gvinpin.grad.kiev.ua (8.8.7/8.8.7) with ESMTP id HAA22275; Fri, 11 Dec 1998 07:59:37 +0200 Message-ID: <3670D170.D8F70884@Shevchenko.Kiev.UA> Date: Fri, 11 Dec 1998 08:01:52 +0000 From: Ruslan Shevchenko Reply-To: rssh@grad.kiev.ua X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Alfred Perlstein CC: rssh@grad.kiev.ua, hackers@FreeBSD.ORG Subject: Re: inclusion of system headers. References: <8667bjgrfd.fsf@detlev.UUCP> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck wrote: > >>> b) it slows compile time signifigantly > >> it is 3 strings of empty cpp output on one header inclusion. > >> Is it really slow compilation ? Where and when it was ? > > uh, no. Usually the #ifndef is inside the included file, which means Which is yet one design bug: #ifndef must be inside and outside. > > > opening the include files multiple times and parsing them just to To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 22:06:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20182 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 22:06:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (56-sweet.camalott.com [208.239.153.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20177 for ; Thu, 10 Dec 1998 22:06:38 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id AAA35596; Fri, 11 Dec 1998 00:06:07 -0600 (CST) (envelope-from joelh) To: Chuck Robey Cc: John Sconiers , freebsd-hackers@FreeBSD.ORG Subject: Re: XWindows programing References: From: Joel Ray Holveck Date: 11 Dec 1998 00:06:05 -0600 In-Reply-To: Chuck Robey's message of "Thu, 10 Dec 1998 20:53:23 -0500 (EST)" Message-ID: <863e6ngqlu.fsf@detlev.UUCP> Lines: 18 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 4. Next step down is going to C, where the X calls are really written > in. I'm going to suggest at this level, the Motif libraries, > because the widgets are written more regularly, documented much > better, and your choice of widgets to use is wider. You are going > to have to deal with all those lousy defaults, but there is a > wealth of Motif code out there, and if you MUST go down to this > level, you'll appreciate Motif, and see why people use it. Do you object to Athena? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 22:08:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20276 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 22:08:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20271 for ; Thu, 10 Dec 1998 22:08:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id WAA03106; Thu, 10 Dec 1998 22:07:17 -0800 (PST) To: Joel Ray Holveck cc: Chuck Robey , John Sconiers , freebsd-hackers@FreeBSD.ORG Subject: Re: XWindows programing In-reply-to: Your message of "11 Dec 1998 00:06:05 CST." <863e6ngqlu.fsf@detlev.UUCP> Date: Thu, 10 Dec 1998 22:07:16 -0800 Message-ID: <3103.913356436@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Do you object to Athena? Can we get this the heck out of -hackers? I don't see what X Window System programming has to do with freebsd-hackers and this topic already has its own forums. I've already chewed out the original poster for raising that question here. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 10 23:17:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27404 for freebsd-hackers-outgoing; Thu, 10 Dec 1998 23:17:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA27398 for ; Thu, 10 Dec 1998 23:17:24 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zoMp3-0001CZ-00; Fri, 11 Dec 1998 00:17:09 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id AAA00589; Fri, 11 Dec 1998 00:15:33 -0700 (MST) Message-Id: <199812110715.AAA00589@harmony.village.org> To: Steve Price Subject: Re: Port tgz for jikes available for comment (was Re: IBM Jikes) Cc: Matthew Dillon , Archie Cobbs , nate@mt.sri.com, chuckr@mat.net, hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 10 Dec 1998 00:51:26 CST." References: Date: Fri, 11 Dec 1998 00:15:33 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Steve Price writes: : Two examples of how this is done are ports/security/bro and : ports/security/fwtk. Marking it RESTRICTED at least for now : wouldn't hurt either. And ports/security/socks5. It works great, until they release a new version and remove the old one. But with socks5 we're stuck with it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 00:47:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06333 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 00:47:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06210 for ; Fri, 11 Dec 1998 00:45:49 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id OAA13129; Fri, 11 Dec 1998 14:21:29 +0600 (NS) Date: Fri, 11 Dec 1998 14:21:29 +0600 (NS) From: Max Khon To: Brian Somers cc: Max Khon , luigi@iet.unipi.it, freebsd-hackers@FreeBSD.ORG Subject: Re: ESS1868 patches In-Reply-To: <199812101209.MAA00471@keep.lan.Awfulhak.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 hi, there! On Thu, 10 Dec 1998, Brian Somers wrote: > > Patches for luigi sound driver code to support ESS1868 (and probably > > ESS688, ESS1668) are available at http://iclub.nsu.ru/~fjoe. > > Currently these patches are tested only with ESS1868 PNP sound card. > > 22Khz playback is not supported (only 44Khz stereo was tested -- i just > > wanted to play my mp3's) -- will be done soon. Full duplex is not > > supported. Recording stuff was not tested. ESS1668 cards probably need > > some patches in probing code. > > I've just tried this on a Sony laptop - it works well, and stops my > mic from screaming (feedback) murder if I haven't already switched it > down. > > I'll commit the changes (with a couple of compiler warnings fixed) > tonight. ah, wait, wait.... there are some known problems with my patches: one of them is incorrect stop/abort handling in sb_callback all of them will be fixed soon. /fjoe PS 22Khz playback works well. i was wrong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 00:49:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06769 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 00:49:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06741 for ; Fri, 11 Dec 1998 00:48:47 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id OAA13937; Fri, 11 Dec 1998 14:37:06 +0600 (NS) Date: Fri, 11 Dec 1998 14:37:06 +0600 (NS) From: Max Khon To: MIHIRA Yoshiro cc: brian@Awfulhak.org, fjoe@husky.iclub.nsu.ru, luigi@iet.unipi.it, freebsd-hackers@FreeBSD.ORG, fwkg7679@mb.infoweb.ne.jp Subject: Re: ESS1868 patches In-Reply-To: <199812110336.MAA14177@lavender.yy.cs.keio.ac.jp> 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 Fri, 11 Dec 1998, MIHIRA Yoshiro wrote: > Mr. Kurosawa and I are developing Sound > driver for ESS18xx with Luigi driver. Latest snapshot is in > experimental directory of 2.2.8-RELEASE: > > ftp://ftp.freebsd.org/pub/FreeBSD/2.2.8-RELEASE/xperimnt/ESS/ > > But our current driver has problem, I think fjoe's drive also have > same problem at heavy load. > > Current Problem: > Some time (CPU was heavy load?), sound change to white > noise. > And also with using mpg123 player and selected some files, > when one file is ended and change to another file, > also sound change to white noise... i have the same problem with OPTi931 soundcard /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 01:01:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08147 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 01:01:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ikar.elect.ru ([195.161.50.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08128; Fri, 11 Dec 1998 01:01:24 -0800 (PST) (envelope-from pavel@ikar.elect.ru) Received: from localhost (pavel@localhost) by ikar.elect.ru (8.8.7/8.8.7) with SMTP id MAA00772; Fri, 11 Dec 1998 12:01:14 +0300 (MSK) (envelope-from pavel@ikar.elect.ru) Date: Fri, 11 Dec 1998 12:01:14 +0300 (MSK) From: "Pavel V. Antipov" To: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Help me please ! 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 ! How can I make floppy image ? How can I make boot floppy image ? Where can I get some info about making floppy images ? Thank you ! Pavel E-mail:pavel@ikar.elect.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 02:32:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16163 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 02:32:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from omnix.net (omnix.net [194.183.217.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16156 for ; Fri, 11 Dec 1998 02:32:35 -0800 (PST) (envelope-from didier@omnix.net) Received: from localhost (didier@localhost) by omnix.net (8.8.7/8.8.7) with SMTP id IAA19622 for ; Fri, 11 Dec 1998 08:52:20 GMT (envelope-from didier@omnix.net) Date: Fri, 11 Dec 1998 09:52:20 +0100 (CET) From: Didier Derny To: hackers@FreeBSD.ORG Subject: Adaptec ANA 6944A TX and/or PCI 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 Hi, I'm trying to use two Adaptec ANA 6944A TX (4 port) 10/100 BaseT board. - each board is working fine separately. - both board are not working used simultanously - Nothing special during the boot (dmesg seems ok) I made the following experience: ifconfig de0 inet 192.168.5.1 netmask 255.255.255.0 ifconfig de4 inet 192.168.6.1 netmask 255.255.255.0 then I ping both networks simultaneously and got a message telling me that the the ethernet / ip addresses were not comming from the right source. ip from de0 with the ethernet address of de4 (ports were numbered from de0 to de3 for the first board and from de4 to de7 for the second board) My guess: when the first board is initialized everything is ok, then when the second board is initialized the io ports of the second board are allocated at the same location than for the first board. I ran the adaptec diagnostics, he saw two boards effectively, he saw the same io ports at the same adresses 0xc800, 0xc400... but I'm not sure if it's a relative or absolute address. The other possibility is a problem in the allocations of ports in the if_de.c driver. It is sure that when trying to ping de0 alone, de4 is activated If it's a pci problem, is there any possibility to override the PCI configuration to avoid this problem. Thanks for your help -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 04:36:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA00736 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 04:36:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA00731 for ; Fri, 11 Dec 1998 04:36:42 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id HAA64602; Fri, 11 Dec 1998 07:34:36 -0500 (EST) Date: Fri, 11 Dec 1998 07:34:36 -0500 (EST) From: Chuck Robey To: Joel Ray Holveck cc: John Sconiers , freebsd-hackers@FreeBSD.ORG Subject: Re: XWindows programing In-Reply-To: <863e6ngqlu.fsf@detlev.UUCP> 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 11 Dec 1998, Joel Ray Holveck wrote: > > 4. Next step down is going to C, where the X calls are really written > > in. I'm going to suggest at this level, the Motif libraries, > > because the widgets are written more regularly, documented much > > better, and your choice of widgets to use is wider. You are going > > to have to deal with all those lousy defaults, but there is a > > wealth of Motif code out there, and if you MUST go down to this > > level, you'll appreciate Motif, and see why people use it. > > Do you object to Athena? I *knew* I'd forget one. Of course not, I'd put Athena as just below Motif in the hierarchy I was forming. Not as complete a set as Motif, not quite as well documented, but much more easily programmed than going straight to Xt. I'd put it nearer to Motif than to Xt, but Motif is still a lot more useable, don't you think? I'm trying to keep my bias towards free software from pushing me away from Motif, here. > > Happy hacking, > joelh > > -- > Joel Ray Holveck - joelh@gnu.org > Fourth law of programming: > Anything that can go wrong wi > sendmail: segmentation violation - core dumped > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 04:48:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02134 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 04:48:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pyrl.eye (ppp-143.isl.net [199.3.25.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA02099 for ; Fri, 11 Dec 1998 04:48:01 -0800 (PST) (envelope-from ortmann@sparc.isl.net) Received: (from ortmann@localhost) by pyrl.eye (8.9.1/8.9.1) id GAA62575 for freebsd-hackers@freebsd.org; Fri, 11 Dec 1998 06:47:51 -0600 (CST) (envelope-from ortmann) From: Daniel Ortmann Message-Id: <199812111247.GAA62575@pyrl.eye> Subject: freebsd.org network attacks? To: freebsd-hackers@FreeBSD.ORG Date: Fri, 11 Dec 1998 06:47:49 -0600 (CST) 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 During the past 2 weeks I have had *no* cvsup sessions complete during the first try; that is rare. I know I am not the only one. Is it just a bad section of internet? Is freebsd.org undergoing network attacks? How would we know? Has anyone considered this before? Has anyone taken action to guard against it? traceroute to opus.cts.cwu.edu (198.104.92.71), 30 hops max, 40 byte packets 1 ascend.isl.net (199.3.25.13) 142.044 ms 139.861 ms 146.659 ms 2 sp-router.isl.net (199.3.25.2) 151.184 ms 123.086 ms 118.056 ms 3 sl-gw5-chi-4-6-T1.sprintlink.net (144.228.59.53) 137.227 ms 134.329 ms 151.780 ms 4 144.228.50.23 (144.228.50.23) 151.535 ms 154.649 ms 153.574 ms 5 sl-bb2-sea-2-1-0.sprintlink.net (144.228.8.105) 192.608 ms 175.523 ms 181.397 ms 6 sl-bb10-sea-1-1.sprintlink.net (144.232.6.25) 180.056 ms 208.125 ms 206.655 ms 7 sl-gw5-sea-0-0-0.sprintlink.net (144.232.6.58) 211.838 ms 197.011 ms 209.025 ms 8 sl-nwnet-2-0-0.sprintlink.net (144.228.97.18) 205.279 ms 222.554 ms 190.671 ms 9 hssi3-0.seabr2-gw.nw.verio.net (198.104.194.49) 182.007 ms 180.463 ms 188.231 ms 10 fe9-0.seabr1-gw.nw.verio.net (204.200.9.5) 212.167 ms 194.923 ms 205.338 ms 11 wak20-gw.nwnet.net (204.200.241.1) 209.849 ms 195.494 ms 183.737 ms 12 seauw1-FE0-0-0.wa-k20.net (198.32.170.24) 208.903 ms 195.724 ms 184.059 ms 13 cwu-H2-0.bacc.wa-k20.net (205.175.104.6) 220.759 ms 214.637 ms 205.161 ms 14 205.175.104.227 (205.175.104.227) 218.442 ms 205.847 ms 198.326 ms 15 sahalee00.gw.cwu.edu (198.104.98.1) 211.198 ms 193.438 ms 194.555 ms 16 opus.cts.cwu.edu (198.104.92.71) 223.316 ms 202.129 ms 211.846 ms -- Daniel Ortmann IBM Circuit Technology 2414 30 av NW, #D E315, bldg 040-2 Rochester, MN 55901 3605 Hwy 52 N 507.288.7732 (h) 507.253.6795 (w) ortmann@isl.net ortmann@us.ibm.com -- "The answers are so simple and we all know where to look, but it's easier just to avoid the question." -- Kansas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 04:57:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03067 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 04:57:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03060 for ; Fri, 11 Dec 1998 04:57:16 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id NAA16717 for ; Fri, 11 Dec 1998 13:57:05 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id NAA16825 for hackers@freebsd.org; Fri, 11 Dec 1998 13:57:01 +0100 (MET) Message-ID: <19981211135700.J5444@follo.net> Date: Fri, 11 Dec 1998 13:57:00 +0100 From: Eivind Eklund To: hackers@FreeBSD.ORG Subject: Getting DDB tracedumps outside DDB Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to debug some code that is indirectly called from a lot of places; to be able to get an overview of the calling patterns, I'd like to dump out a number of backtraces. Unfortunately, the function is called in a real-time environment (I'm trying to debug a call descriptor leak in i4b), so setting a breakpoint, showing a trace, and continuing is likely to create problems. I tried adding #ifdef DDB db_stack_trace_cmd(NULL, 0, -1, "unused, I think"); #endif to the start of the function in question, but this just got me a double fault. If anybody know how to invoke this properly, I'd appreciate it. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 07:18:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17095 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 07:18:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17080 for ; Fri, 11 Dec 1998 07:18:14 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id KAA26655; Fri, 11 Dec 1998 10:17:57 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id KAA04047; Fri, 11 Dec 1998 10:59:18 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id KAA04220; Fri, 11 Dec 1998 10:18:29 -0500 (EST) Date: Fri, 11 Dec 1998 10:18:29 -0500 (EST) From: Thomas David Rivers Message-Id: <199812111518.KAA04220@lakes.dignus.com> To: bright@hotjobs.com, joelh@gnu.org Subject: Re: inclusion of system headers. Cc: hackers@FreeBSD.ORG, rssh@grad.kiev.ua In-Reply-To: <8667bjgrfd.fsf@detlev.UUCP> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>> b) it slows compile time signifigantly > >> it is 3 strings of empty cpp output on one header inclusion. > >> Is it really slow compilation ? Where and when it was ? > > uh, no. Usually the #ifndef is inside the included file, which means > > opening the include files multiple times and parsing them just to abort. > > Many modern compilers (including gcc) will detect when an entire > header file is #ifdef'd, and DTRT. Yes - and many others (unfortunately) won't. A likely counter argument is that doesn't too much matter - why do we care about them... Well - because other people use the header files in other offerings, for example.. I rather support the approach the current header files. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 07:19:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17454 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 07:19:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17444 for ; Fri, 11 Dec 1998 07:19:20 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id JAA45380; Fri, 11 Dec 1998 09:19:07 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812111519.JAA45380@ns.tar.com> From: "Richard Seaman, Jr." To: "Marc Slemko" Cc: "hackers@freebsd.org" Date: Fri, 11 Dec 98 09:19:06 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: pread/pwrite Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 10 Dec 1998 14:20:22 -0800 (PST), Marc Slemko wrote: >(not necessarily addressed specifically at pread/pwrite, but it does >apply to it because of how it is used...) > >Where is the locking if multiple threads are reading and/or writing >from or to the same descriptor at the same time? If you have x >threads reading from a descriptor opened from a file on disk, do >x-1 of them have to wait until the first one finishes before they can >do anything? > >What about with mixed reading/writing? Well, I'm no expert on the FreeBSD kernel, and know even less about FreeBSD SMP. But, here's my understanding (and I hope someone will correct me if I'm wrong). In the uniprocessor case, it is my understanding that the kernel is nonpreemtive. Thus, if pread/pwrite are syscalls, no locking is needed any more than it is needed for read/write. In the SMP case, you need locking, I think. My understanding is that FreeBSD currently has a kernel "giant lock". Moving to more fine grained locking could require locking fd's, but as long as that is not implemented for read/write, I don't see that its needed for pread/pwrite. If I'm wrong about this, then the pread/pwrite implementation I've supplied is not correct. And, based on this, I think read/write (or pread/pwrite) is effectively ordered (one thread at a time accessing an fd) by the nature of the kernel (uniprocessor) or by the locks (SMP). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 07:22:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17664 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 07:22:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail-oak-1.pilot.net (mail-oak-1.pilot.net [198.232.147.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17659 for ; Fri, 11 Dec 1998 07:22:18 -0800 (PST) (envelope-from wadlow@pilot.net) Received: from corsair.pilot.net (corsair.pilot.net [204.48.17.12]) by mail-oak-1.pilot.net with ESMTP id HAA11335 for ; Fri, 11 Dec 1998 07:22:10 -0800 (PST) Received: from arrow.pilot.net (arrow.pilot.net [204.48.17.29]) by corsair.pilot.net with ESMTP id HAA21326 for ; Fri, 11 Dec 1998 07:22:10 -0800 (PST) Received: from localhost (wadlow@localhost) by arrow.pilot.net (arrow) with ESMTP id HAA04706 for ; Fri, 11 Dec 1998 07:22:09 -0800 (PST) Date: Fri, 11 Dec 1998 07:22:09 -0800 (PST) From: Tom Wadlow To: freebsd-hackers@FreeBSD.ORG Subject: A problem with SCSI 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 built a system on 3.0-RELEASE, with a SCSI disk. The system works fine, except that occasionally, the da driver says: "Invalidating pack", and drops the disk offline and everything hangs. This is unfortunate. Reading through the code, there seemed to have been a bunch of changes made recently to the sys/cam/scsi/scsi_da.c code (among others) that deal with invalidating packs. Seeing this, I upgraded my /sys to 3.0-CURRENT last night, rebuilt the kernel and rebooted. This morning I woke to a crashed system and an "Invalidating pack" message on the console. Thus far, I've built 3 different SCSI systems from 3.0-RELEASE, and two of them have had this problem, with the third complaining about da related issues, but not dying. The third machine is a system that ran the 3.0-mumble-SNAP release from the CD for months without problem. So I don't think it is a hardware problem. What can I do to fix or workaround this problem? A quick answer would be appreciated, as the system which is crashing is one that I *really* need to be stable, and I'd rather not have to downrev to 2.2.x, which I'm going to need to do very soon, like today, if I can't get this issue stabilized. Thanks, --Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 07:31:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18610 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 07:31:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dei.calldei.com (dei.calldei.com [205.179.37.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18604 for ; Fri, 11 Dec 1998 07:31:02 -0800 (PST) (envelope-from phoenix@calldei.com) Received: (from phoenix@localhost) by dei.calldei.com (8.9.0/8.7.3) id HAA18012; Fri, 11 Dec 1998 07:30:48 -0800 (PST) Date: Fri, 11 Dec 1998 07:30:48 -0800 (PST) From: Chris Costello Message-Id: <199812111530.HAA18012@dei.calldei.com> To: freebsd-hackers@FreeBSD.ORG, ortmann@sparc.isl.net Subject: Re: freebsd.org network attacks? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Daniel Ortmann > Subject: freebsd.org network attacks? > To: freebsd-hackers@FreeBSD.ORG > Date: Fri, 11 Dec 1998 06:47:49 -0600 (CST) > > During the past 2 weeks I have had *no* cvsup sessions complete during > the first try; that is rare. I know I am not the only one. > > Is it just a bad section of internet? Maybe. > > Is freebsd.org undergoing network attacks? This has nothing to do with freefall.cdrom.com (aka www.freebsd.org). Pay attention to the host you're actually reaching. The host you're trying to connect to is opus.cts.ctw.edu. It may be anything from a bad route, loaded server, network attacks on any end. Server: dei.calldei.com Address: 205.179.37.1 Non-authoritative answer: Name: opus.cts.cwu.edu Address: 198.104.92.71 Aliases: cvsup.freebsd.org -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 07:35:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19270 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 07:35:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19255 for ; Fri, 11 Dec 1998 07:35:32 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id JAA59487; Fri, 11 Dec 1998 09:35:15 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812111535.JAA59487@ns.tar.com> From: "Richard Seaman, Jr." To: "Marc Slemko" Cc: "hackers@freebsd.org" Date: Fri, 11 Dec 98 09:35:15 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: pread/pwrite Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 Dec 98 09:19:06 -0600, Richard Seaman, Jr. wrote: >In the uniprocessor case, it is my understanding that the kernel >is nonpreemtive. Thus, if pread/pwrite are syscalls, no locking >is needed any more than it is needed for read/write. A follow-up clarification. The implementation of read/write and pread/pwrite in sys_generic.c all call an underlying device specific read/write. There is synchronization needed in most cases to handle interrupts, but this is done within the device specific read/write. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 08:29:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25171 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 08:29:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25088; Fri, 11 Dec 1998 08:29:35 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id KAA59758; Fri, 11 Dec 1998 10:29:15 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812111629.KAA59758@ns.tar.com> From: "Richard Seaman, Jr." To: "freebsd-gnats-submit@freebsd.org" , "info@highwind.com" , "Steve Price" Cc: "hackers@freebsd.org" Date: Fri, 11 Dec 98 10:29:14 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=_=_=IMA.BOUNDARY.F3T4CP138764=_=_=_" Subject: Re: kern/8011: libc_r does not have pread() or pwrite() interfaces Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --_=_=_=IMA.BOUNDARY.F3T4CP138764=_=_=_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Thu, 10 Dec 1998 16:42:13 -0600 (CST), Steve Price wrote: >Can you send this patch as a followup to kern/8011? Seems >someone else has an interest in this too and may be able >to help you test it. Ok. Done. The original patch did not implement pread/pwrite in libc_r, which was what kern/8011 requested. The attached patch also adds a libc_r implementation, which is less tested than the first patch. --_=_=_=IMA.BOUNDARY.F3T4CP138764=_=_=_ Content-Type: application/octet-stream; name="preaddiffs.gz" Content-Transfer-Encoding: base64 H4sICBJGcTYAA3ByZWFkZGlmZnMA7Vt5c9tGlv+b/hRtZysrUuABkJREOnKVLNFeVmRSRUpxUtkU CsJBYkQCGACUosnou+97r7uBBgTqSCwnMzssUWj0+fqdvz44Dhz31yHzA3u1cdz2JvCT1GktXx3+ 8c+r2fGcef7KHbL2Mly77cC+TtpJbLfLo2nXr2I3jX332g8WLIZH4ocB01uG8crxPY81bdaM8ZVl BDYajeylpg8GB+3OflvXmd4dGv1hZ1Cj1s1ms1RLN9p6hxn6sGcMO13sRv1Qt3pnoOl6j1EG9sAz BgzSzVeMub+mbhwAz1IWRqkfOBo+3TimJ/y9hUpQWmMLF1+ZaZ7t7ECGxuylFbMGs8MgSdnPv2gi xbPrdWz4apd943sgFo9NpubFZDw/PzHPZqMj+P95Nj4fQYUk8f/hmjBAFLuWw5QBrkPfYQ2N8QpA kOeZKXasNrqJ/dRVqSIiHmj6jRuAHCAB9AniaubZdD7+0ZxPL2bHI55P2SbQe2yakJOk8cZOWeqv 3Wtr9bYGn3aDJe7KtdMdo84a7Vdjrn4r/7INX7ud3CbtT9aVi2rTAjV5WT3cOuxWhezvFxSyv88K 1KL2qBlC5fS20WOdg6EOinlQo15QrSpqSuUEFdaNauU0DE03DrhyMvbpdDz5fr57uF6F9lXLYOtN wFNqWbgJ0hbajkgpZZGVLkH8HhR7efrV66wCKhgU4uO60DJ27WsqsK+9OFyLpHisk0WhcgIKBEX4 oCKmZKRhqWoaLXxeCKk4anEzlhMXRviVJ87Ea8SffxIfKhWi29X07qCsEKDStrVaQXPTzNJKOdhm YFupi/PP00qFG8tH3uGjK57i0Su+RkikwjjyLliGT64zLd9jr8E7+IHr7IBXO9M7na6pv6+rBNtL 1zHBY5pR7IfQ9tZcW7/i9CsK/AAK/hda1x5pFsdUBm7OjcEJSV0SPCvp0l+HZ0xmRCLxF2Nild8W lvH1PDYfcLuvLrpqYcFkMzyJPne/3dHbXfC5xrA7GHbJO5OK5FW4WwZk0Rv2B+DDK62w19f6nRwx 4Ksh1av1IZXBl94C6py9QQDhvGFveOC93HiQ5tVYcHmbusmbUuNdahw9tTV7QyEcAzm4kDfUvIqS 67wzjgRE4PbDa9dmDXi84TUgZQcpUTVfspPR/Hg2PjsfTyeisxl0VsmdwYGmd/rSRUVh4qcgoxZj 50uXgUZtXCCSpfAShaRlzEqS0PbBvhx246dLlmzsJbMCaB1e/s1F4hJw68IaWjj+WQT2dBGB6KGu 7SaJt1kBsllHKxcH05QJQ9IKHJUDkAYl2gCqQyKCzfoSaACSiJHMstMN+IJbLjdoyqKVZQNpPq8P zPfcuCWwYgew4p6U/QvOFfuDR6YSkPbAJ+FoLHJjL4zXCY2TWGsX54AFVqLyYZdpgGZtFzBqurRg oJTyE4aRjNou/Gs3yGZBKmQJhYIXJDfcEH4NFmh+2AQNV86thXAWyd19UDS7GUmaquQvJafKMNrv aXp/oID+vb6mD7q5EeckcKhBnPzBYg5rZZMcC8LCoJkusToMDv4qtuLbwsR2UaY+MmDtBih4i0SF daBHWUfGoHL35a617W1xHNAvd325gvppKKgweRcY5UzZAln9GI1WrmI3Sx/UlDOCD41NQOt4c6Ip YEhDsm1QYtyYGwMR+yB9N+Fm5bBLHFEDQsBVpbASYwkoIRACtAqlBxth711IuUJXQDG10sykBHcz CXKfNhudX8wm7Iej04vRHPKAuFxlOZvZI2oHhPBhkQ5SesxG4wCM1wy9JtqHVq2DewBx9zJsj6TB qjIIcTmZIAwEBoEuOz4CD+IaFIexJH40m01nc+ESZtvs58YHRtOkQKTAB5jbkCv8YE8zOrnC/9HR tYJzejIpVYwx9I5m6P3cOA0IsMZeRuuZFafCq9IQFoYq8r7ghRIGLirxHU5zFIcozv8Gsa1AB8jr Wo4TQx5LIvAWZG2jVWZzR6sk1FhJf9bWrXREYZA5dC+ELm9I1MgZmAy0er9izdRasOaN74BzH8WY OU7Z+79Dmo3GE1A2yDrnFqx6VytebND0yA4DCB0AGouN52fjs5FoJgy2HEzAI/gRUBizD+MPUxIW TI6LbD4asaPT+RRff4yZs4mYwbRKcCdh6NdDd2LErfBurwDv9iRiJn0R6fsAr9epYUtUIaVOhvBg fd4Z9va+AMLjWywlXPVcoPfMTp6C9/gC40sBvs/YW7Ur0yF6Ggq/dH0fllwdyTE0ID49z70BZ8o9 KYAQ9A5/37gJKDDuhqFZCUPj2Gm9AXovMcRCDY27FVFrbYF34o4ZM0KIBxaFqmTJQwd1BaoEprHk qCbxIS7m8ZUglcp8jGhPwVS7OXOrQBUVoBGDB/0yqIpLZPzp7HT0aTQ5P0KhsMn0nKIWToY9iEW2 R599RWT7BgSEjoqAuPr8UQgk+fQgBpKVfhcIKjV+CgqSTRQYtJ3OJ+GgDIVSP48BIm4NT0NEkrAv AolkZ0/FRNuBfCUo5/wBG3eJD6kbcECRgyQ2hXbxjZ+ARbGmrhZm1r1YhZfWCnxA7FsgxC0KPND0 fWXf3uigAmfbPM9AMap7A3suskqFMplBEJbxLH+VkaxaLC/mLgoYTZaN6xJvC94xDjSj21VmstfV jANdzoRcYSKWNQXEY8UxeFbw47EHUAQZyLpG8xJ8ENKxwNXPQ/CGK+G/K8DxIJitqiCOGWfb/18H 4SgDbgU4ereAcPRudmBAOiJfxOHXXlvvQZDFk4Ner0at1TOG8uFXd9jZr1a9gdbNdmpq66sgdFoh C6wgTFauG2HaS5JrGxIQYAN4RKAU8KANs1Dsl4f5fnjItxjlbngo9hRvfXeF9flxECX4nngoN8NF Q1AVEPhVGFGl5SZ1whscNvEXPP6K9CpNUsu+omavoZm/UInGLtw0S0SWH8ML35kNBRYM5fYrLnlo w5WfU7I3//Vb6/hidjKe3bVbLQ5R1cObN9sqr62gVJGMGVicbRD9f2Ux7yISUxLb3C/IeGHxuLK4 cuMAlxjmwg3c2LdbL3zMWD3mVrvvFe2+12VFWtFKCzmqbXf0Yb87NPZq1A9q29aqDx8zdgEMdlUw 2MVY2pdqe8cl1W6AU2YNsScNQ6Xumkm4hge8+WG2Of9pjt+z2fR8av6PieiMLzuosQnBIGG/QW4N j849B8+da7jYqeFih97EATYtdzBDfviyh4nAgiV3hVPrdoMdzT7OL+ajE04TjAD/adydSGMbK6pT /5KeEFZBEQ0Zuws/wQB+n9YGNMM6v1XVo+Df8Ko7wULHTWAQz4nYIYua7yJTzFhU2fghs+CfmseX ZxY8KHcVgt7YeH5PwRj66VC+5Ia9iSH5losAJfD9+ezoeHSvwytQQt5lfsyPUvDYzs7OBk996jDT 5jvPqbN3hwxIxrQZ4CwS9s9/YmWUwo6Hc5HFIRX/LFr+UmeHh2xycXpabABlprcC8PAt+4BXHKha h4RRE/BjZ/T+6OQDXUMgmnij9BZi/utDdnL+09nI/GEyPRmVWhF04M2QZS34mpcWYMxDtmPjjo8p 5iW1K6u1Aph+yKgsU7UaCqMFXxNqQOm3mRjUApAGlOnFfK6VkN/Us0nknbN3bDw5Nz8d/Viin3BT vdhV7Caw+N9OW3wDhRfjqYm8LBYl7sJbLUQxWMJsfgbKUKyDik/6WKk0ZOs1MHaYQBpbNq4hYB18 7dLKI7pFkEgaxau15Vyhh7MpzBEtDdLmx9FkPK3z2XLdgyGtsgrWOC9LM+U6jWpGWpAbfE3NkO2U YtJmaSc7DVE7SuCBbLWcOiiWBmIFPmiidzt2nbogFNuXxADahzR++y2THR/C8mE0Pz+anQstJzXP C4EJMyhRcj5PL05P3p9Oj78X49SKtowDNA9ZceSq+T5g7NtlgLRntHQyiUC08MMdckooZ5d7SDRj LVMuYBWXnaa4oOJdoRr1APoMwP7nzi+M2CX8IdfxvNEddzptBJ2gYXNYnKG/vB9VGEUVtj2qVGLa /T6snpTNqG6vq/XyC13A9ojAzAr5Mx9/FK4DSjDObZfCy/OabnxpmS69ENN5DOeLP4Xdz4nh1Lg6 iJf2Lf9QKBeRm0Z7buhWSPxrx+5/tchNSvqf0P1lQjcx8z+x+6mxm4x6e/DmFv5nhW8aN69Oas3r VcabXYw3vyfqs5LE2XMiEXtWJKpYR9OWdmttoZv8eitpddTtd8BKl8D6rEyvWE2redmtXTwSNIY9 WCTjjlq/L9fTFZUfX1H39nWtt6/s6fKMbEXd7e7V5ucntffzk9pvdLkcN2mQDXhJm6EYKFNczBYR Ul7XFmeAGt/QgY8IFIlnLp00Zg38L5s2ElGZOgYnntTf0oq+290v0XC1cpLbNacASPEFFfbakXfN HSu1qPkuND+g5nQzHDoQR49ioS1nkQGBIu3FeWU9Dqp75ABAdllCGI92LJR4k8StSz9op34kvy/9 04fKIbdvBRV3ghgnELWJUuJ8+6Bt9FmnP+wYQx3Pt3ukXlmNJ2ln39D6ym4Pvmbw+Bu5w/ZdskjT 29byHWZyZ89/r8Dvpm3/vUKxE/J8opc8N3XA293PXPmXmHt/w37DD8TkkxZxL72T9+jwT76tUKIa RVDMyrf16e6CcTDsdbO7C1VV80uqvWGvem9/0NMGipAHeOMtu8PAlzoSw8RoKbTPR5gyv5jwJFsu Oam6RNq4KIhlVIc0QsG3ArW2G4ysHGDJbYKHdE7I/oaH/enST4YKJuEjVKDNTl3p6zS0r/JjOETs sR+lEPTkyazaJU4Xwqn54cTEYL6DU4M0X+gi9q0LdCvgBPT/EU8S6doBKAFfOa1DvGMEU5Jd0/yw XyEuANcpnl7+DLAaAis6XoDPU/Po+PgToGBJPXZ/vHSBft/Lp+AneOeBTgTuzYEmIXE1LNBPppPT nzDOq3mfZ5J8HODDo33W6PYXkE8onuOZGrLoYlJmUl2USkk0dZFzp0zpjJ9FA+LEuwF0aM2NhK/x MahmY98skbxMLuXbgDQ2aZ2ibqhodfZdLiUu2seYP5lOOIIjCQPTeFta5ggOFJCeQIAi/+jj0XiS wUzgj7TMTdB8h6Gx5TnwR8urt6U6iGQA26cm/kIq3KQ7pGmZFhDTZm4iFI3OkeNNhAef+dUWnEcu seLwaguBSCspoMOiJLUgoJ7NQcAz8/PR+FwTdZERpvlhfDoyTQ1Sp+MJpIpkyqolvc3JvKE7MqKO StflLegDjwhZBTkZFN+2CeUcz9UU8bnkcS1W1234uYR+ruTbHX/eMXcFy0rZlVrlLtPfh5X+Tt1b 4V5T7KxkMfLx2MVPv/684CXG334U3SkeRXdYmXI1gIk8EcEG7c4+Yo8+ABS9Rn2pIaxQOY9hUH+w 5WBK1/Su+uNMyDCMveeGsWcAyIeimXRj90JaTULVoPi2WWerQ/mDTBERv3YQJA48IQryhd9fNQwW ZlGKg59nvzMOFjt9YiDku2BPiYTZrGhGmZdMmBW7KHRSKjl6FigPnx3M6gor+X4GqkQYMR5eYU58 HyC07U2c0MWlTZD6K34t6tfItdFF8wtdsn1+6z2/0IVTETfNkFCLZTRzRoq2hdBOuqbo0gMIIduX LkCEWlBGBtykBTRgu0i4BAisyd/EzgmVKSFMlQldd4pBi2F+4gabcnctH56skL2T9lcMg9+7bkRb a5tAXkwvX4zLK8uu7wVAdBa7h9yDSEIFOmngLcEHeI4/Nc9NJ2vEWcmvDS5x+49aIaKIsWoCAUOl Dlsokwe+krVDDko/SfFSGzGKrikqQwzlq8KsjEDccgPWfUdoayvIymHYfbQFEAx5z/Ea+dTvhKDr /2ZY7PO/FhYjLpHnswLuXBSG3MNkd0/R6wpXwJXVCrI2ihuLXbB/CpnCBd8sgZnXYHjIBXnXlTeT t4Md3ykrrECGOO3X2eigdkFhgYHzPSpSSB2u/cUyI+AfbhwqXOBMCCQPMsx53xNlBIOpJvKarass 0BQi0QbAHoQRqDq79ddy9zyaJG2zzkNWJfjFEPpU8Pt/Nzeki2FEAAA= --_=_=_=IMA.BOUNDARY.F3T4CP138764=_=_=_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 11:21:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14940 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 11:21:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14912 for ; Fri, 11 Dec 1998 11:20:57 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA00622; Fri, 11 Dec 1998 19:20:31 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id HAA41630; Fri, 11 Dec 1998 07:52:21 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199812110752.HAA41630@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: sanpei@sanpei.org (MIHIRA Yoshiro) cc: brian@Awfulhak.org, fjoe@husky.iclub.nsu.ru, luigi@iet.unipi.it, freebsd-hackers@FreeBSD.ORG, fwkg7679@mb.infoweb.ne.jp Subject: Re: ESS1868 patches In-reply-to: Your message of "Fri, 11 Dec 1998 12:36:09 +0900." <199812110336.MAA14177@lavender.yy.cs.keio.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Dec 1998 07:52:21 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did jump the gun with this - and didn't even go via Luigi. I had a lot of embarassment at work over this; I got a new laptop, suspended and resumed and got the whole department looking at me for the best part of a minute while I figured out how to get a mixer program to shut it up. I've only actually worked there for about a month :-/ If the consensus is that the changes should be backed out, be my guest (or give me a shout and I'll pull them back out). > brian@Awfulhak.org wrote > >> > Patches for luigi sound driver code to support ESS1868 (and probably > >> > ESS688, ESS1668) are available at http://iclub.nsu.ru/~fjoe. > >> > Currently these patches are tested only with ESS1868 PNP sound card. > >> > 22Khz playback is not supported (only 44Khz stereo was tested -- i just > >> > wanted to play my mp3's) -- will be done soon. Full duplex is not > >> > supported. Recording stuff was not tested. ESS1668 cards probably need > >> > some patches in probing code. > >> > >> I've just tried this on a Sony laptop - it works well, and stops my > >> mic from screaming (feedback) murder if I haven't already switched it > >> down. > > Mr. Kurosawa and I are developing Sound > driver for ESS18xx with Luigi driver. Latest snapshot is in > experimental directory of 2.2.8-RELEASE: > > ftp://ftp.freebsd.org/pub/FreeBSD/2.2.8-RELEASE/xperimnt/ESS/ > > But our current driver has problem, I think fjoe's drive also have > same problem at heavy load. > > Current Problem: > Some time (CPU was heavy load?), sound change to white > noise. > And also with using mpg123 player and selected some files, > when one file is ended and change to another file, > also sound change to white noise... > --- > Our source code is managed by CVS. > > http://www.jp.freebsd.org/cgi/cvsweb.cgi/ESS/?cvsroot=freebsd-jp > > and you can get latest snap files via CVSup from > cvsup.jp.FreeBSD.ORG, jp-ess as collection name. > > Cheers. > MIHIRA Yoshiro > -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 11:31:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16079 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 11:31:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16071 for ; Fri, 11 Dec 1998 11:31:39 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zoYHi-000I5lC; Fri, 11 Dec 1998 14:31:30 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: suggestion To: hackers@FreeBSD.ORG Date: Fri, 11 Dec 1998 14:31:30 -0500 (EST) 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 Modify the source tree such that the contents of /usr/share/skel do not get automatically updated with make world (treat like /etc). If significant updates are made to the system standard for local use, this would be much appreciated... Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 12:08:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20914 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 12:08:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20904 for ; Fri, 11 Dec 1998 12:08:53 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA299065779; Fri, 11 Dec 1998 09:16:19 -0500 Date: Fri, 11 Dec 1998 09:16:19 -0500 (EST) From: Bill Fumerola To: Archie Cobbs Cc: Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: IBM Jikes (java source -> byte code compiler) released in open-source form In-Reply-To: <199812100552.VAA16802@bubba.whistle.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, 9 Dec 1998, Archie Cobbs wrote: > Also, "make install; make deinstall" tells you if your PLIST is > incorret. I think there's something called "portlint" but I don't > know anything about it. portlint (/usr/ports/devel/portlint) is your friend. Run it either in the current directory of the port or as argv[1] as the directory you want to check. It will spit out some of the more obvious errors, and make the lives of the ports-dudes easier. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Fri Dec 11 12:30:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23874 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 12:30:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23866 for ; Fri, 11 Dec 1998 12:30:17 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id PAA13018 for ; Fri, 11 Dec 1998 15:30:02 -0500 (EST) Date: Fri, 11 Dec 1998 15:30:02 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: freebsd-hackers@FreeBSD.ORG Subject: status of NFS? 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, We're getting ready to replace two important production machines running 2.1.7.1 with two running our stable snap (980825). We currently run nfs between them to allow shell users to read mail locally (yes, I know about IMAP, but the solution we have works well now...). Basically the mail server export /var/mail to the shell machine and the shell machine exports /home so user's procmailrc's can be read, etc. NFS is over a private 100Mb network on a second nic. I'd just like to get a feel from everyone as to what the best options for NFS in this situation are. Right now, even with "soft" and "intr" flags, I get un-killable processes should one of the mounts go away. Generally, reboots are required to get everything back in sync after a failure. I'm now using a line like so: 10.0.0.1:/var/mail /var/mail nfs rw,bg,intr,soft,nfsv3,tcp,nosuid,nodev,noexec Looking at the archives, people seem to have better luck with v2 over udp. Thoughts? Thanks, Charles --- Charles Sprickman spork@super-g.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 13:10:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00433 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 13:10:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00412; Fri, 11 Dec 1998 13:10:34 -0800 (PST) (envelope-from sarrage@msn.com) From: sarrage@msn.com Received: from ul1.satlink.com (ul1.satlink.com [200.0.224.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id NAA29708; Fri, 11 Dec 1998 13:10:26 -0800 (PST) Received: from your (1Cust124.tnt3.springfield2.ma.da.uu.net [208.251.119.124]) by ul1.satlink.com (8.8.8/8.8.8) with SMTP id RAA22719; Fri, 11 Dec 1998 17:45:20 -0300 (GMT-3) Message-Id: <199812112045.RAA22719@ul1.satlink.com> Date: 12/11/98 3:39:26 AM Pacific Daylight Time Reply-To: sarrage@msn.com To: sarrage@msn.com Subject: resume Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG MIKE A. SARRAGE Springfield, Massachusetts 01107 Phone: (413) 733-9872 MARKETING / BUSINESS DEVELOPMENT / MEDIA Marketing, International Business, International Trade, International Economics, Publishing, Internet Commerce and Print Media Specialist Extensive Educational Background, Superior Analytical, Quantitative and Computer Skills Visionary, multidisciplined and degreed leader with strong growth record in production and profitability. Talented communicator and presenter. Enthusiastic, creative and focused with unusual ability to identify and act on opportunities. A self-starter with transferable marketing and leadership skills, committed to achieving organizational and personal goals and objectives. Strong customer service orientation with ability to integrate marketing, sales service strategies and alliance building techniques into existing business plans. Able to initiate change and implement concepts. PROFESSIONAL EXPERIENCE MANAGING DIRECTOR 1992 - Present International Business Directories, Inc. Springfield, Massachusetts Combine exceptional market cognizance with a practiced business sense. Publish Hong Kong and U.S. Exporters Directories. Drive the development and implementation of market expansion strategies. Generate customized marketing and presentational strategies to maximize account development opportunities with the largest customers. Place advertisements in international business and airline magazines, trade magazines and the Internet. Optimized the use of targeted international direct mail to promote contract sales to advertisers. • Established long-term alliances and relationships; continue to sell directories to over 14,000 North American companies, and to companies in over 60 countries. Placed advertisements in over 80 major publications. • Established a profitable Internet web site in a commission based partnership with over 400 affiliate web sites. • Advised clients on product sources, international risk assessment, economic conditions, international trade and product market potential. INDEPENDENT AGENT 1991 - 1992 Hong Kong Trade Development Council U.S., Canadian & Mexican Markets Pioneered new territories and spearheaded the marketing of trade directories throughout the U.S., Canada and Mexico. Networked with, and provided information to, key groups and individuals. Developed comprehensive marketing plans; researched and targeted key prospects. Created print advertisements; performed media placement, telephone marketing, fulfillment and product source referrals. Demonstrated winning presentations. Executed administrative tasks and special projects to achieve objectives. • Generated over 18,000 trade inquiries from 18 countries; increased trade volume by more than $40,000,000 in less than 1 year. • Collaborated with 5 Hong Kong Trade Development Offices to answer and follow up on product source inquiries. Continued Confidential Resume of MIKE A. SARRAGE Page 2 EXECUTIVE MANAGEMENT 1985 - 1990 World Auto Exchange / Marco Auto Sales Springfield, Massachusetts / New York, New York Coordinated business development, fulfillment, administrative, public relations and marketing activities for these exporters with annual export sales volume of $10,000,000+. Utilized planning and organizing skills, negotiation and authority to achieve market objectives and quality performance standards. Configured price models; oversaw U.S. transportation, customs, international shipping and export documentation of exported vehicles. • Participated in market valuation, purchase and export of 800+ automobiles per year. EDUCATION & TRAINING Western New England College - Springfield, Massachusetts MASTER OF BUSINESS ADMINISTRATION, 1995 BACHELOR OF ARTS IN ECONOMICS, 1989 Additional courses, seminars and workshops: 18 graduate credits beyond MBA, including some Ph.D.-level work in macro-economics COMPETENCIES Lotus 123 • Lotus Freelance Graphics • Lotus Approach • Excel • PowerPoint Word • Pagemaker • WordPerfect • MS Front Page INTERESTS & ACTIVITIES Reading / Travel / Outdoor activities PERSONAL Willing to perform work related travel / Willing to relocate Date of Birth: July 12, 1966 REFERENCES AND FURTHER DATA AVAILABLE UPON REQUEST To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 14:59:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12540 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 14:59:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12535 for ; Fri, 11 Dec 1998 14:59:06 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id RAA27964 for ; Fri, 11 Dec 1998 17:58:56 -0500 (EST) Date: Fri, 11 Dec 1998 17:58:56 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: freebsd-hackers@FreeBSD.ORG Subject: Re: status of NFS? 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 An addendum... Any idea what causes this? root@shell[/home/spork]# mount /dev/sd0s1a on / (local) /dev/sd0s1d on /tmp (local, nodev, nosuid) /dev/sd0s1e on /usr (local, nodev) /dev/sd0s1f on /usr/local (local, nodev, nosuid) /dev/sd0s1g on /usr/local/tars (local, nodev, nosuid) /dev/sd0s1h on /var (local, nodev, nosuid) /dev/sd1s1e on /staff (NFS exported, local, nodev) /dev/sd1s1f on /home (NFS exported, local, nodev, nosuid) procfs on /proc (local) 10.0.0.1:/var/mail on /var/mail (nodev, noexec, nosuid) 10.0.0.1:/var/mail on /var/mail (nodev, noexec, nosuid) 10.0.0.1:/var/mail on /var/mail (nodev, noexec, nosuid) ??? Weird. Charles --- Charles Sprickman spork@super-g.com --- On Fri, 11 Dec 1998, spork wrote: > Hi, > > We're getting ready to replace two important production machines running > 2.1.7.1 with two running our stable snap (980825). We currently run nfs > between them to allow shell users to read mail locally (yes, I know about > IMAP, but the solution we have works well now...). Basically the mail > server export /var/mail to the shell machine and the shell machine exports > /home so user's procmailrc's can be read, etc. NFS is over a private > 100Mb network on a second nic. > > I'd just like to get a feel from everyone as to what the best options for > NFS in this situation are. Right now, even with "soft" and "intr" flags, > I get un-killable processes should one of the mounts go away. Generally, > reboots are required to get everything back in sync after a failure. I'm > now using a line like so: > > 10.0.0.1:/var/mail /var/mail nfs > rw,bg,intr,soft,nfsv3,tcp,nosuid,nodev,noexec > > Looking at the archives, people seem to have better luck with v2 over udp. > > Thoughts? > > Thanks, > > Charles > > --- > Charles Sprickman > spork@super-g.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 Fri Dec 11 20:59:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14532 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 20:59:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14527 for ; Fri, 11 Dec 1998 20:59:50 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.sanpei.org (u4168.seaple.icc.ne.jp [203.140.32.168]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id NAA01958; Sat, 12 Dec 1998 13:59:31 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.8.8/3.6W) id MAA19696; Sat, 12 Dec 1998 12:11:56 +0900 (JST) Message-Id: <199812120311.MAA19696@lavender.yy.cs.keio.ac.jp> To: brian@Awfulhak.org, luigi@iet.unipi.it Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ESS1868 patches In-Reply-To: Your message of "Fri, 11 Dec 1998 07:52:21 +0000" References: <199812110752.HAA41630@keep.lan.Awfulhak.org> X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 12 Dec 1998 12:11:56 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. Brian and Luigi. >I did jump the gun with this - and didn't even go via Luigi. I had a >lot of embarassment at work over this; I got a new laptop, suspended >and resumed and got the whole department looking at me for the best >part of a minute while I figured out how to get a mixer program to >shut it up. > >I've only actually worked there for about a month :-/ I already solved SBPro and ESS18xx mixer problem with Luigi's driver and I posted Problem Report(pr) as below....... Sometime I discussed about this PR on multimedia mailing list and hardware mailing list..... but not yet hackers mailing list..... i386/8684: [Patch] Sound only come out from left channel with SBPro/pcm0 >If the consensus is that the changes should be backed out, be my >guest (or give me a shout and I'll pull them back out). Did you have a white noise problem, brian? I and some user reported this problem with our patch and fjoe patch. OSS/FreeBSD commercial sound driver does not have this problem, by experience. I do not mind whether back out or not fjoe's patch. I only hope to fix white noise problem and have a good FreeBSD life :) Cheers. MIHIRA Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 11 22:42:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23426 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 22:42:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23420 for ; Fri, 11 Dec 1998 22:42:36 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id WAA22448 for ; Fri, 11 Dec 1998 22:42:27 -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 sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id WAA15757 for ; Fri, 11 Dec 1998 22:42:26 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id WAA21633 for hackers@freebsd.org; Fri, 11 Dec 1998 22:42:25 -0800 (PST) Date: Fri, 11 Dec 1998 22:42:25 -0800 (PST) From: Don Lewis Message-Id: <199812120642.WAA21633@salsa.gv.tsc.tdk.com> To: hackers@FreeBSD.ORG Subject: restricting sysctl -w when securelevel > 0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to add some security related sysctl knobs and I don't want them to be changeable when securelevel > 0. Rather than using SYSCTL_PROC and defining several very similar handlers, I think it would be better to add a generic way of limiting write access when securelevel > 0. Comments? --- kern/kern_sysctl.c.orig Tue Dec 8 20:40:52 1998 +++ kern/kern_sysctl.c Fri Dec 11 22:27:10 1998 @@ -804,7 +804,8 @@ return ENOENT; found: /* If writing isn't allowed */ - if (req->newptr && !((*oidpp)->oid_kind & CTLFLAG_WR)) + if (req->newptr && (!((*oidpp)->oid_kind & CTLFLAG_WR) || + (((*oidpp)->oid_kind & CTLFLAG_SECURE) && securelevel > 0))) return (EPERM); /* Most likely only root can write */ --- sys/sysctl.h.orig Sat Sep 5 19:23:09 1998 +++ sys/sysctl.h Fri Dec 11 22:24:37 1998 @@ -78,6 +78,7 @@ #define CTLFLAG_RW (CTLFLAG_RD|CTLFLAG_WR) #define CTLFLAG_NOLOCK 0x20000000 /* XXX Don't Lock */ #define CTLFLAG_ANYBODY 0x10000000 /* All users can set this var */ +#define CTLFLAG_SECURE 0x08000000 /* Permit set only if securelevel<=0 */ /* * USE THIS instead of a hardwired number from the categories below To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 12 02:55:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10309 for freebsd-hackers-outgoing; Sat, 12 Dec 1998 02:55:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10304 for ; Sat, 12 Dec 1998 02:55:25 -0800 (PST) (envelope-from k@numeri.campus.luth.se) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.8.8/8.8.8) with ESMTP id LAA11884; Sat, 12 Dec 1998 11:59:30 +0100 (CET) (envelope-from k@numeri.campus.luth.se) Message-Id: <199812121059.LAA11884@numeri.campus.luth.se> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG cc: brodnik@sm.luth.se Subject: Special memory with know phys addr -> kernel virt addr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 12 Dec 1998 11:59:29 +0100 From: Johan Karlsson Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I have a special memory, which I try to access using 3.0-current as of 981113, located at physical address from my_mem_phys_start_addr to my_mem_phys_start_addr. During the memory scan loop in i386/i386/machdep.c:init386 this memory is marked as bad and will therefor not be used by the VM. Now I want to be able to use this memory in the kernel. This is how I try to do it ============== phys_size = my_mem_phys_end_addr - my_mem_phys_start_addr; /* * Allocate a submap in the kernel virtual memory map */ my_mem_kernel_submap = kmem_suballoc(kernel_map, &my_mem_kernel_submap_min, &my_mem_kernel_submap_max, phys_size); /* * Map phys pages into submap */ my_mem_virtual_base = my_mem_kernel_submap_min; my_mem_virtual_top = pmap_map(my_mem_virtual_base, my_mem_phys_start_addr, my_mem_phys_end_addr, VM_PROT_READ | VM_PROT_WRITE); =========== The function with this code is runned by SYSINIT(my_mem, SI_SUB_DRIVERS, SI_ORDER_FIRST, my_mem_init, NULL) When I reboot my machine with my new kernel it panic printing "kmem_suballoc: unable to change range to submap" which is found in vm/vm_kern.c:kmem_suballoc. I used 2.2.x before but I had to move to 3.0 since I needed some other functions. When I did the same thing in 2.2.x no panic occured. Is there somthing wrong with the way I try to do this? or is there a known problem with kmem_suballoc ? Thanks for any help with my problem. /Johan K -- Johan Karlsson mailto:k@numeri.campus.luth.se SWEDEN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 12 06:16:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27804 for freebsd-hackers-outgoing; Sat, 12 Dec 1998 06:16:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27748 for ; Sat, 12 Dec 1998 06:15:59 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id PAA20189; Sat, 12 Dec 1998 15:15:57 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA24244; Sat, 12 Dec 1998 15:15:57 +0100 (MET) Message-ID: <19981212151556.R5444@follo.net> Date: Sat, 12 Dec 1998 15:15:56 +0100 From: Eivind Eklund To: Tom Torrance at home , hackers@FreeBSD.ORG Subject: Re: suggestion References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Tom Torrance at home on Fri, Dec 11, 1998 at 02:31:30PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 11, 1998 at 02:31:30PM -0500, Tom Torrance at home wrote: > Modify the source tree such that the contents of /usr/share/skel > do not get automatically updated with make world (treat like /etc). > > If significant updates are made to the system standard for local > use, this would be much appreciated... This mod would be wrong. The user is _not_ supposed to need to edit /usr. The right solution would probably be to move /usr/share/skel to /etc/skel, or to provide a way of re-directing where the skel files are looked for. Do you feel enough about this to supply patches? Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 12 06:18:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28164 for freebsd-hackers-outgoing; Sat, 12 Dec 1998 06:18:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28152 for ; Sat, 12 Dec 1998 06:18:16 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id PAA20217; Sat, 12 Dec 1998 15:18:15 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA24267; Sat, 12 Dec 1998 15:18:15 +0100 (MET) Message-ID: <19981212151814.S5444@follo.net> Date: Sat, 12 Dec 1998 15:18:14 +0100 From: Eivind Eklund To: Don Lewis , hackers@FreeBSD.ORG Subject: Re: restricting sysctl -w when securelevel > 0 References: <199812120642.WAA21633@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812120642.WAA21633@salsa.gv.tsc.tdk.com>; from Don Lewis on Fri, Dec 11, 1998 at 10:42:25PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 11, 1998 at 10:42:25PM -0800, Don Lewis wrote: > > I want to add some security related sysctl knobs and I don't want them > to be changeable when securelevel > 0. Rather than using SYSCTL_PROC > and defining several very similar handlers, I think it would be better to > add a generic way of limiting write access when securelevel > 0. > > Comments? I like this concept. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 12 12:06:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22694 for freebsd-hackers-outgoing; Sat, 12 Dec 1998 12:06:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22688 for ; Sat, 12 Dec 1998 12:06:57 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id MAA19479; Sat, 12 Dec 1998 12:06:55 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id MAA11452; Sat, 12 Dec 1998 12:06:55 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 12 Dec 1998 12:06:55 -0800 (PST) Message-Id: <199812122006.MAA11452@vashon.polstra.com> To: eivind@yes.no Subject: Re: restricting sysctl -w when securelevel > 0 Newsgroups: polstra.freebsd.hackers In-Reply-To: <19981212151814.S5444@follo.net> References: <199812120642.WAA21633@salsa.gv.tsc.tdk.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981212151814.S5444@follo.net>, Eivind Eklund wrote: > On Fri, Dec 11, 1998 at 10:42:25PM -0800, Don Lewis wrote: > > > > I want to add some security related sysctl knobs and I don't want them > > to be changeable when securelevel > 0. Rather than using SYSCTL_PROC > > and defining several very similar handlers, I think it would be better to > > add a generic way of limiting write access when securelevel > 0. > > > > Comments? > > I like this concept. Me too. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 12 13:46:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00750 for freebsd-hackers-outgoing; Sat, 12 Dec 1998 13:46:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00729 for ; Sat, 12 Dec 1998 13:46:10 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id VAA23426; Sat, 12 Dec 1998 21:46:05 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id UAA02165; Sat, 12 Dec 1998 20:15:03 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199812122015.UAA02165@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: MIHIRA Sanpei Yoshiro cc: brian@Awfulhak.org, luigi@iet.unipi.it, freebsd-hackers@FreeBSD.ORG Subject: Re: ESS1868 patches In-reply-to: Your message of "Sat, 12 Dec 1998 12:11:56 +0900." <199812120311.MAA19696@lavender.yy.cs.keio.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 12 Dec 1998 20:15:03 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > >If the consensus is that the changes should be backed out, be my > >guest (or give me a shout and I'll pull them back out). > > Did you have a white noise problem, brian? I and some user > reported this problem with our patch and fjoe patch. OSS/FreeBSD > commercial sound driver does not have this problem, by experience. I guess it was white noise: As the machine comes up, you can hear feedback from the mic (located in the centre, just above the keyboard and just between the two speakers that are on the bottom left/right of the lid underneath the LCD. The feedback goes away if you switch the microphone volume down to zero. If you don't, suspending & resuming will cause the white noise/feedback, and zeroing the mic volume will stop it. > I do not mind whether back out or not fjoe's patch. I only hope to > fix white noise problem and have a good FreeBSD life :) Well, it seems to fix the white noise. I'm not audio expert, so I think the best I can do at this point is try out the other patches and report if they work for me. I'll leave it to Luigi to make the decisions :-] I'll follow up tomorrow. > Cheers. > MIHIRA Yoshiro -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 12 14:25:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04687 for freebsd-hackers-outgoing; Sat, 12 Dec 1998 14:25:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04682 for ; Sat, 12 Dec 1998 14:25:18 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA24309; Sat, 12 Dec 1998 22:02:22 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id WAA08065; Sat, 12 Dec 1998 22:03:34 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199812122203.WAA08065@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Somers cc: MIHIRA Sanpei Yoshiro , luigi@iet.unipi.it, freebsd-hackers@FreeBSD.ORG Subject: Re: ESS1868 patches In-reply-to: Your message of "Sat, 12 Dec 1998 20:15:03 GMT." <199812122015.UAA02165@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 12 Dec 1998 22:03:27 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > > I do not mind whether back out or not fjoe's patch. I only hope to > > fix white noise problem and have a good FreeBSD life :) > > Well, it seems to fix the white noise. I'm not audio expert, so I > think the best I can do at this point is try out the other patches > and report if they work for me. I'll leave it to Luigi to make the > decisions :-] > > I'll follow up tomorrow. Oops. The other patches (http://www.jp.freebsd.org/~sanpei/pcm0-ESS.tar.gz) seem to be for 2.2 only :-/ I run -current on my laptop, so I can't test them. Anyone have any other ESS1868 they'd like me to test ? Should I try the xperiment stuff ? Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 12 15:07:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08492 for freebsd-hackers-outgoing; Sat, 12 Dec 1998 15:07:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08476; Sat, 12 Dec 1998 15:07:08 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id AAA25047; Sun, 13 Dec 1998 00:07:04 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id AAA27336; Sun, 13 Dec 1998 00:07:04 +0100 (MET) Message-ID: <19981213000659.A5444@follo.net> Date: Sun, 13 Dec 1998 00:06:59 +0100 From: Eivind Eklund To: Dag-Erling Smorgrav , Matt Dillon Cc: hackers@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern vfs_syscalls.c References: <199812122107.NAA12093@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Dag-Erling Smorgrav on Sat, Dec 12, 1998 at 11:49:20PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 12, 1998 at 11:49:20PM +0100, Dag-Erling Smorgrav wrote: > Speaking of kernel dumps, what happens to physical memory pages when > they're not in use? Are they zeroed? If not, is it possible to add a > kernel option that zeroes out unused pages, or fills them with a fixed > pattern (e.g. f001f001 og deadbeef)? That would make kernel dumps more > compressible... They are zeroed so approx 1/2 the free pages are zeroed. The percentage was based on John's intuition. The reason to not zero all is that zeroing still cost CPU cache lines, I think. The zeroing is done in the idle loop, or when there are "way too few zeroed pages available". All of this is from my memory of the code, so you should check with reality (the code itself). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 12 16:11:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15934 for freebsd-hackers-outgoing; Sat, 12 Dec 1998 16:11:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15923 for ; Sat, 12 Dec 1998 16:11:37 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA29953; Sat, 12 Dec 1998 17:11:35 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd029884; Sat Dec 12 17:11:26 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id RAA12494; Sat, 12 Dec 1998 17:11:20 -0700 (MST) From: Terry Lambert Message-Id: <199812130011.RAA12494@usr01.primenet.com> Subject: Re: Is it possible? To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sun, 13 Dec 1998 00:11:19 +0000 (GMT) Cc: vmg@novator.com, hackers@FreeBSD.ORG In-Reply-To: <85152.913104877@zippy.cdrom.com> from "Jordan K. Hubbard" at Dec 8, 98 00:14:37 am X-Mailer: ELM [version 2.4 PL25] 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 have run into the proverbial brick wall. I am the administrator of > > a fairly busy electronic commerce Web site, www.ftd.com. Because of > > the demand placed on a single server, I implemented a load balancing > > solution that utilizes NFS in the back end. The versions of FreeBSD > > Hmmm. Well, as you've already noted, NFS is not really sufficient to > this task and never has been. There has never been any locking with > our NFS and, as evidence would tend to suggest, never a degree of > interest on anyone's part sufficient to actually motivate them to > implement the functionality. This isn't true. Actually, Jordan was going to do this as a project in a class he was taking taught by Kirk McKusick... > Even with working NFS locks, it's also probably an inferior solution > to what many folks are doing and that's load balancing at the IP > level. Something like the Coyote Point Systems Equalizer package > (which is also based on FreeBSD, BTW) which takes n boxes and switches > the traffic for them from one FreeBSD box using load metrics and other > heuristics to determine the best match for a request would be a fine > solution, as would any of the several other similar products on the > market. This is potentially true. > Unless you're up for doing an NFS lock implementation, that is. > Terry's patches only address some purported bugs in the general NFS > code, they don't actually implement the lock daemon and other > functionality you'd need to have truly working NFS locks. Evidently, > this isn't something which has actually interested Terry enough to do > either. :-) Actually, my patches addressed all of the kernel locking issues not related to implementation of the NFS client RPC code, and not related to the requisite rpc.lockd code. I didn't do the rpc.lockd code because you were going to. I didn't do the NFS client RPC code because I didn't have working rpc.lockd on which to base an implemetnation. The patches were *not* gratuitous reorganization, as I believe I can prove; they addressed architectural issues only in as much as it was required to address them for (1) binary compatability with previous fcntl(2) based non-proxy locking, (2) support of the concept of proxy locking at all, and (3) dealing with the issue of a stacking VFS consuming an NFS client VFS layer, and the necessity of splitting lock assertions across one or more inferior VFS's, and the corresponding need to be able to abort a lock coelesce on a first VFS if the operation could not be completed on the second. Here is my architecture document, which should describe the patches I've done (basically, all the generic kernel work), and the small amount of work necessary to be done in user space, and in the NFS client code. Hopefully, someone with commit priviledges will approach these ideas, since I've personally approached them three times without success in getting them committed. PS: I'm pretty sure BSDI examined my code before engaging in their own implementation, given the emails I exchanged with them over it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. ========================================================================== NFS LOCKING 1.0.0.0 Introduction NFS locking is generally desirable. BSDI has implemented NFS locking, purportedly using some of my FreeBSD patchese as a starting point, to achieve the first implementation of NFS locking not derived from Sun source code. What's unfortunate about this is that they neglected to release the code as open source (so far). 2.0.0.0 Server side locking Server side locking is, by far, the easiest NFS locking problem to solve, Server side locking is support for allowing clients to asser locks against files on an NFS server. 2.1.0.0 Theory of operation Server side locking is implemented by allowing the client to make RPC requests which are proxied to the server file space via one or more processes (generally, two: rpc.lockd and rpc.statd). Operations are proxied into the local collision domain, and enforced both against and by local locks, depending on order of operation. 2.2.0.0 rpc.statd The purpose of rpc.statd is to provide host status data to machines that it is monitoring. This is generally used to allow client machines to reassert locks (since the NFS protocol is nominally stateless) following a server restart. This means we can generally ignore rpc.statd for the purposes of this discussion. 2.3.0.0 rpc.lockd The purpose of rpc.lockd is to provide responses for file and record locking requests to client machines. Because NFS is nominally stateless, but locks themselves are nominally stateful, there must be a container for the lock state. In a UNIX system, containers for lock state are called "processes". They provide an ownership context for the locks, such that the locks can be discarded when th NFS services are discontinued. As such, the rpc.lockd is an essential part of the resource and state tracking mechanism for NFS locks. The current FreeBSD rpc.lockd unconditionally grants lock requests; this is sufficient for Solaris interoperability, since Solaris will complain bitterly if there is not a lockd for a Solaris client to talk to, but is of rather limited utility otherwise, since locks are not enforced, even in the NFS collision domain, let alone between that domain and other processes on the FreeBSD machine. Note that it is possible to enforce the NFS locks within the NFS collision domain solely in the rpc.lockd itself, but this is generally not a sufficient answer, both because of architectural issues having to do with with the current rpc.lockd impelemtnation's handling of blocked requests (it has none) and the 2.3.1.0 Interface problems in FreeBSD FreeBSD has a number of interface problems that prevent implementation of a functional rpc.lockd that enforces locks within both collision domains. 2.3.1.1 FreebSD problem #1: Conversion of NFS handles to FD's Historically, NFS locks have been asserted by converting an NFS file handle into an open file descriptor, and then asserting the proxy lock against the descriptor. SOLOUTION FreeBSD must implement an F_CNVT interface, to allow the rpc.lockd to convert an NFS handle into an open file descriptor. This is the first step in asserting a lock: get a file descriptor for use as a handle to the local locking mechanisms to perform operations on behalf of client machines. 2.3.1.2 FreeBSD problem #2: POSIX lock-release-on-close semantics The second problem FreeBSD faces is that a lock release by a process is implicit in POSIX locking semantics. This will not work in FreeBSD, since the same process proxies locks for multiple remote processes, and the semantic enforcement needs to occur on a per remote process basis, not on a per rpc.lockd basis. SOLOUTION FreeBSD must implement the fcntl option F_NONPOSIX for flagging descriptors on which POSIX unlock semantics must not be enforced. This resovles the proxy dissoloution problem, whereby a lock release by one remote client's process will not destroy the locks held by all other remote client's processes, as would happen if POSIX semantics were enforced on that descriptor. It also resolves the case where multiple locks are being proxied using one descriptor ("descriptor caching"). The rpc.lockd engages in descriptor caching by creating a hash based on the device/inode pair for each fd that results from a converted NFS file handle. The purpose of this is twofold: First, it allows a single descriptor to be resource counted for multiple clients such that descriptors are conserved. Second, since the file handle presented by one client may not match the file handle presented by another, either because of intentional NFS server drift to prevent session hijacking, or because of local FS semantics, such as loopback mounts, union mounts, etc., it provides a common rendesvous point for the rpc.lockd. 2.3.1.3 FreeBSD problem #3: lack of support for proxy operations The FreeBSD fcntl(2) interface lacks the ability to note the use of a descriptor as proxy, as well as the identity of the proxied host id and process id. In general, what this means is that there is no support for proxying locks into the kernel. SunOS 4.1.3 solved this problem once; since that is the reference implemetnation for NFS locking, even today, inside Sun Microsystems, there is no need to reinvent the wheel (if someone feels the needs, at least this time, make it round). SOLOUTION FreeBSD must implement F_RGETLK, F_RSETLK, and F_RSETLKW. In addition, the flock structure must be extended, as follows: /* old flock structure -- required for binary compatability*/ struct oflock { off_t l_start; /* starting offset */ off_t l_len; /* len = 0 means until end of file */ pid_t l_pid; /* lock owner */ short l_type; /* lock type: read/write, etc. */ short l_whence; /* type of l_start */ }; /* new flock structure -- required for NFS/SAMBA*/ struct flock { off_t l_start; /* starting offset */ off_t l_len; /* len = 0 means until end of file */ pid_t l_pid; /* lock owner */ short l_type; /* lock type: read/write, etc. */ short l_whence; /* type of l_start */ short l_version; /* avoid future compat. problems*/ long l_rsys; /* remote system id*/ pid_t l_rpid; /* remote lock owner*/ }; The use of an overlay structure solves the pending binary compatability easily an elegantly: the l_version, l_rpid, and l_rsys fields are defaulted for the F_GETLK, F_SETLK, and F_SETLKW commands. This means that they are copied in using the same size as they previously used, and binary compatability is maintained. For the F_RGETLK, F_RSETLK, and F_RSETLKW commands, since they did not previously exist, binary compatability is unnecessary, and they can copy in the non-default l_version, l_rpid, l_rsys identifiers. By fiat, the oflock l_version is 0, and the flock version is 1. Also by fiat, the value of l_rsys is -1 for local locks. In particular, l_rsys is the IPv4 address of the requester, and -1 is illegal, and therefore useful as a cookie for "localhost". This provides the framework whereby proxy operations can be supported by FreeBSD. 2.3.1.4 FreeBSD problem #4: No support for l_rsys and l_rpid. Having an interface is only part of the battle. FreeBSD also fails to support l_rsys and l_rpid internally. These values must be used as uniquifiers; that is, the value of l_pid alone is not sufficient. When l_rsys is not -1 (localhost), the values of l_rsys and l_rpid must also be considered in determining whether or not locks may be coelesced. SOLOUTION Add Support to the FreeBSD locking subsystem to allow for support of these values to use in preventing coelescence and in determining lock equality. This work is rather trivial, but important. As we shall see in section 3, "Client side locking", we will want to defer our modifications until we have a complete picture of the issues for *both* client and server requiriments. 2.3.1.5 FreeBSD problem #5: Not all local FS's support locking We can say that any local FS that we may wish to mount really wants to be NFS exportable. Without getting into the issues of the FreeBSD VFS mount code, mount handilng, and mappinf of mounted FS's into the user visible hierarchy, it is very easy to see that one requirement for supporting locking is that the underlying FS's must also support locking. SOLOUTION Make all underlying FS's support locking by taking it out of the FS, and placing it at a higher layer. Specifically, hang the lock list off the generic vnode, not off the FS specific inode. This is an obvious simplification that reaps many benefits. However, a we will discover in section 3, "Client side locking", we wil want to defer our modifications until we have a complete picture of the issues for *both* client and server requiriments. Specifically, for VFS stacking to function correctly where an inferior VFS happens to be the NFS client VFS, we must preserve the VOP_ADVLOCK interface as a veto-based mechanism, where local media FS's never veto the operation (deferring to the upper level code that manages the lock off the vnode), whereas the NFS client code may, in fact, veto the operation (as could any other VFS that proxies operations, e.g., an SMBFS). 2.3.2.0 Requirements for rpc.lockd Once the FreeBSD interface issues have been addressed, it is necessary to address the rpc.lockd itself. These issues are primarily algorithmic in nature. 2.3.2.1 When any request is made When a client makes a request, the first thing that the rpc.lockd must do is check the client handle hash list to determine if the rpc.lockd already has a descriptor open on that file *for that handle*. If a descriptor is not open for the handle, the rpc.lockd must convert the NFS file handle into a file descriptor. The rpc.lockd then fstats the descriptor to obtain the dev_t and ino_t fields. This uniquely identifies the file to the FreeBSD system in a way that, for security reasons, the handle alone can not. Note: If the FreeBSD system chose to avoid some of the anti-hijack precations it takes, this step could be avoided, and the handle itself used as a unique identifier. The POSIX lock-release-on-close semantics are disabled via an fcntl using th F_NONPOSIX command. Given the unique identifier, a hash is computed to determine if some other client somewhere has the file open. If so, the structure referencing the already open FD's reference count is incremented, and the FD is closed. The client handle hash is updated so that subsequent operations in the same handle do not So there are two hash tables involved: the client handle hash, and the open file hash. Use of these hashes guarantees the minimum descriptor footprint possible for the rpc.lockd. Since this is the most scarce resource on the server, this is what we must optimize. We note at this point what we noted earlier: we must have at least one descriptor per file in which locks are being asserted, since we are the process container for the locks. 2.3.2.2 F_RGETLK This is a straight-forward request. The request is not a blocking request, so it is made, and the result is returned. The rpc.lockd fills out the l_rpid and l_rsys as necessary to make the request. 2.3.2.3 F_RSETLK This is likewise non-blocking, and therefore likewise relatively trivial. 2.3.2.4 F_RSETLKW This operation is the tough one. Because the operation would block, we have an implementation decision. To reduce overhead, we first try F_RSETLK; if it succeeds, we return success. This is by far the most common outcome, given most lock contention mechanisms in most well written FS client software (note: FS, not NFS: programs are clients of FS services, even for local FS's). If this returns EAGAIN, then we must decide how to perform the operation. We can either fork, and have the forked process close all its copies of the descriptors, except the one of interest, and then implement F_RSETLKW as a blocking operation, or we can implement F_RSETLKW as a queued operation. Finally, we could set up a time, and use F_RSETLK exclisively, until it succeeeds. This last is unacceptable, since it does not guarantee order of grant equals order of enqueueing, and thus may break program expectations on semantics, resulting in deadly embrace deadlocks between processes. Given that FreeBSD supports the concepts of sharing a descriptor table between processes (via vfork(2)), the fork option is by far the most attractive, with the caveat that we use the vfork to get a copy of the descriptor table shared so as to not double the fd footprint, even for a short period of time. We can likewise enqueue state, and process SIGCLD to ensure that the parent rpc.lockd knows about all pending and successful requests (necessary for proper operation of the rpc.statd daemon). 2.3.2.5 Back to the general Now we can go back to discussing the general implementaiton. The rpc.lockd must decrement the reference count when locks held by a given process are removed. It can either do this by maintaining a shadow, or, preferentially, by, after a lock is released, performing an F_RGETLK. This is part of the resource tracking for opn descriptors in the rpc.lockd. If the request indicates that there are no more locks held by that l_rsys/l_rpid pair, then the fd reference count is decremented, and the per handle hash is removed from the list. If the reference count goes to zero, then the descriptor is closed. DISCUSSION It is useful to implement late-bingding closes. Specifically, it is useful to not actually delete the reference immediately. SOLOUTION The handle refernces, instead of being deleted, are thrown ont a clock list. If the handles are rereferenced within a tunable time frame, then they are removed from the list and placed back into use; otherwise, after sufficient time has elapsed, they are inactivated as above. This resolves the case of a single client generating a lot of unnecessary rpc.lockd activity by issuing lock-unlock pairs that would cause the references to bounce up and down, requiring a lot of system calls. It preserves the NFS handle hash for a time after the operation nominally completes, in the expectation of future operations by that client. 3.0.0.0 Client side locking Client side locking is much harder than server side locking. Client side locking allows clients to request locks from remote NFS servers on behalf of local processes running on the client machine. 3.1.0.0 Theory of operation Client side locking is implemented by the client NFS code in the kernel making RPC requests against the server, much in the same way that NFS clients operate when making FS operation requests against NFS servers. It is simultaneously more difficult because of the code being located in the kernel, and less difficult, since there is a process context (the reqiesting process) to act as a conatiner ofr the operation until it is completed by the server. Server side locking is implemented by allowing the client to make RPC requests which are proxied to the server file space via one or more processes (generally, two: rpc.lockd and rpc.statd). Operations are proxied into the local collision domain, and enforced both against and by local locks, depending on order of operation. 3.1.1.0 Interface problems in FreeBSD FreeBSD has a number of interface problems that prevent implementation of a functional NFS client locking. 3.1.1.1 FreeBSD problem #1: VFS stacking and coelescence Locks, when asserted, are coelesced by l_pid. If they are asserted by a hosted OS API, e.g., an NFS, AppleTalk, or SAMBA server, they are coelesced by l_rsys and l_rpid, as well; we can ignore all by l_pid in the general case, since exporting an exported FS is foolish and dangerous. When locks are asserted, then, the locks are coelesced if the lock is successful. Thus, If a process had a file [FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF] Protected by the locks: [111111111] [2222222222] [FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF] And asserted a third lock: [333333333333333333] [111111111] [2222222222] [FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF] That lock would be coelesced: [111111111111111111111111111111111] [FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF] For a local media FS, this is not a problem, since the operation occurs locally, and is serialized by virtue of that fact. But for an NFS client, the lock behaviour is less serialized. Consider the case of a VFS stacking layer that stacks two filesystems, and makes the files within them appear to be two extents of a single file. We can imagine that this would be useful for combined log files for a cluster of machines, and for other reasons (there are many other examples; this is merely the simplest). So we have: [ffffffffffffffff][FFFFFFFFFFFFFFFFFFFFFFFFFFF] Lets perform the same locks: [111111111] [2222222222] [ffffffffffffffff][FFFFFFFFFFFFFFFFFFFFFFFFFFF] So far, so good. Now the third lock: [333333333333333333] [111111111] [2222222222] [ffffffffffffffff][FFFFFFFFFFFFFFFFFFFFFFFFFFF] Colesce, phase one: [33333333] [1111111111111111] [2222222222] [ffffffffffffffff][FFFFFFFFFFFFFFFFFFFFFFFFFFF] Oops! The second phase fails because Some other client has the lock: [XX] Now we need to back out the operation on the first FS: [33333333] [111111111] [ffffffffffffffff] Leaving: [1111111] [ffffffffffffffff] Ut-oh: looks like we're screwed. SOLOUTION Delayed coelescing. The locks are asserted, but they are not committed (coelesced) until all the operations have been deemed successful. By dividing the phases of asserting vs. committing, we can delay the coelesceing until we know that all locks are successfully asserted. How do we do this? Very simply, we convert the VOP_ADVLOCK to be a veto mechanism, instead of the mechainsm by which the lock code is acutally called, and we move the locking operations to upper level (common) code. At the same time, we make the OS more robust, since there is only one place, instead of many, where the code is called. For stacking layers that stack on more than one VFS, and for proxy layers, such as NFS, SMB, or AppleTalk client layers, the operation is a veto, where the operation is proxied, and if the proxy fails, then the operation is vetoed. So in general, VOP_ADVLOCK becomes a "return(1);" for most of the VFS layers, with specific exceptions for particular layer types, which *may* veto the operation by the upper level code. If the operation is not vetoed by the upper level code, then the upper level code commits the operation, and the lock ranges are coelesced. 3.1.1.2 FreeBSD problem #2: What if the NFS layer is first? If the NFS layer is first, and the operation is subsequently vetoed, how is the NFS coelesce backed out? SOLOUTION The shadow graph. The NFS client, for each given vnode (nfsnode), must seperately maintain the locks agains the node on a per process basis. What this means is that when a process asserts a lock on an NFS accessed file, the NFS client lockign code must maintain an uncoelesced lock graph. This is because the lock graph *will* be coelesced on the server. In order to back out the operation: [33333333] [111111111] [ffffffffffffffff] | v [1111111111111111] [ffffffffffffffff] The client must keep knowledge of the fact that these locks are seperate. This implies that locks that result in type demotions are not type demoted to the server (i.e., locks against the server are only asserted in promote-only mode so that if they are backed out, there will not have been a demotion, for example, from write to read, on the server). There is currently code in SAMBA which models this, since SAMBA's consumtiopn of the host FS is similar to an NFS clients consumption of an NFS server's FS. 3.2.0.0 The client NFS VFS layer's RPC calls So far no one has implemented this. In general, it is more important to be a server than it is to be a client, at this time. The amount of effort to implement this, if one has the ISO documents, or, more obliquely and therefore more difficult, the rpc.lockd code in the FreeBSD source tree, is pretty small. This would make a good one quarter project for a Batcholer of Science in Computer Science independent study credit. 3.3.0.0 Discussion In general, all of the issues for an NFS client in FreeBSD apply equally to the idea of an AppleTalk or SMB client in FreeBSD. It is likely that FreeBSD will want to support the ability to operate as a desktop (and therefore client) OS, even if this is not the primary niche into which it is currently being driven by the developers. 4.0.0.0 End Of Document ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 12 16:24:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16860 for freebsd-hackers-outgoing; Sat, 12 Dec 1998 16:24:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16854 for ; Sat, 12 Dec 1998 16:24:46 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id RAA15011; Sat, 12 Dec 1998 17:24:40 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd014967; Sat Dec 12 17:24:36 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id RAA13176; Sat, 12 Dec 1998 17:24:35 -0700 (MST) From: Terry Lambert Message-Id: <199812130024.RAA13176@usr01.primenet.com> Subject: Re: pread/pwrite To: marcs@znep.com (Marc Slemko) Date: Sun, 13 Dec 1998 00:24:35 +0000 (GMT) Cc: lists@tar.com, hackers@FreeBSD.ORG In-Reply-To: from "Marc Slemko" at Dec 10, 98 02:20:22 pm X-Mailer: ELM [version 2.4 PL25] 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 > (not necessarily addressed specifically at pread/pwrite, but it does > apply to it because of how it is used...) > > Where is the locking if multiple threads are reading and/or writing > from or to the same descriptor at the same time? If you have x > threads reading from a descriptor opened from a file on disk, do > x-1 of them have to wait until the first one finishes before they can > do anything? Locking is unnecessary, since the intent of the lock is to prevent moving the file pointer around. If you wrapper the operations at all, it should be for call conversion. I really don't know why this would be necessary on a local FS, and since seeks don't apply to things like serial ports, there's no reason for using pread/pwrite instead of read/write, so pread/pwrite is not really useful in terms of call conversion. Hmmm. Given the implemetnation, I would expect them to error out on non-seekable devices, in fact. Actually pread/pwrite is how SunOS 4.1.3 implemented liblwp, which was Sun's first released threading implementation, and which was also user space. 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 Sat Dec 12 23:58:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27699 for freebsd-hackers-outgoing; Sat, 12 Dec 1998 23:58:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27694 for ; Sat, 12 Dec 1998 23:58:35 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (ppp099.dialup.st.keio.ac.jp [131.113.27.99]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id QAA29782; Sun, 13 Dec 1998 16:56:28 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.8.8/3.6W) id QAA24183; Sun, 13 Dec 1998 16:56:25 +0900 (JST) Message-Id: <199812130756.QAA24183@lavender.yy.cs.keio.ac.jp> To: brian@Awfulhak.org Cc: luigi@iet.unipi.it, freebsd-hackers@FreeBSD.ORG Subject: Re: ESS1868 patches In-Reply-To: Your message of "Sat, 12 Dec 1998 22:03:27 +0000" References: <199812122203.WAA08065@keep.lan.Awfulhak.org> X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 13 Dec 1998 16:56:25 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The other patches (http://www.jp.freebsd.org/~sanpei/pcm0-ESS.tar.gz) >seem to be for 2.2 only :-/ I run -current on my laptop, so I can't >test them. Sorry, I forgot to update these files. I created tarball only for 2.2, but I maintain sys/i386/isa/snd files for releng22 and 3.0-RELEASE and current tree. http://www.jp.freebsd.org/cgi/cvsweb.cgi/ESS/?cvsroot=freebsd-jp and you can get latest snap files via CVSup from cvsup.jp.FreeBSD.ORG, jp-ess as collection name. Tag names are same as original FreeBSD source CVS repository, RELENG_2_2, head. And especially for 3.0-RELEASE is RELENG_3_0_0. Now I create snap-shot tarball for all branches. http://www.jp.freebsd.org/~sanpei/snd-ESS-2.2-19981213.tar.gz http://www.jp.freebsd.org/~sanpei/snd-ESS-3.0R-19981213.tar.gz http://www.jp.freebsd.org/~sanpei/snd-ESS-current-19981213.tar.gz Cheers. MIHIRA Yoshiro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message