From owner-freebsd-hackers Sun Jul 15 1: 8: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (discworld.nanolink.com [195.24.48.189]) by hub.freebsd.org (Postfix) with SMTP id A421B37B401 for ; Sun, 15 Jul 2001 01:07:51 -0700 (PDT) (envelope-from roam@ringworld.nanolink.com) Received: (qmail 48064 invoked by uid 1000); 15 Jul 2001 08:12:01 -0000 Date: Sun, 15 Jul 2001 11:12:01 +0300 From: Peter Pentchev To: Giorgos Keramidas Cc: hackers@FreeBSD.ORG Subject: Re: mail failed, returning to sender Message-ID: <20010715111201.A2245@ringworld.oblivion.bg> Mail-Followup-To: Giorgos Keramidas , hackers@FreeBSD.ORG References: <20010715063652.A13774@hades.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010715063652.A13774@hades.hell.gr>; from keramida@ceid.upatras.gr on Sun, Jul 15, 2001 at 06:36:52AM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 15, 2001 at 06:36:52AM +0300, Giorgos Keramidas wrote: > From: daemon@provi.de > Subject: mail failed, returning to sender > Date: Sun, Jul 15, 2001 at 04:10:41AM +0200 > > > freebsd-hackers-digest Saturday, July 14 2001 Volume 05 : Number 180 > > Doesn't mail that failed to deliver get this poor guy unsubscribed > automagically, if it happens more than a few times? It probably does, if it is bounced to the right address :( I have a strong suspicion that the MTA at provi.de does not really honor the Return-Path, that should point to owner-listname, and sends the bounce to listname instead.. this way, the Majordomo bounce handlers never realize that this is a bounce. G'luck, Peter -- I had to translate this sentence into English because I could not read the original Sanskrit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 1:24:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 9864337B401 for ; Sun, 15 Jul 2001 01:24:30 -0700 (PDT) (envelope-from julian@elischer.org) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id DAA78009; Sun, 15 Jul 2001 03:12:13 -0700 (PDT) Message-ID: <3B515097.6551A530@elischer.org> Date: Sun, 15 Jul 2001 01:13:11 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Matt Dillon Cc: Leo Bicknell , Drew Eckhardt , hackers@FreeBSD.ORG Subject: Re: Network performance tuning. References: <200107130128.f6D1SFE59148@earth.backplane.com> <200107130217.f6D2HET67695@revolt.poohsticks.org> <20010712223042.A77503@ussenterprise.ufp.org> <200107131708.f6DH8ve65071@earth.backplane.com> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matt Dillon wrote: > > I took a look at the paper Leo pointed out to me: > > http://www.psc.edu/networking/auto.html > > It's a very interesting paper, and the graphs do in fact show the type > of instability that can occur. The code is a mess, though. I think it > is possible to generate a much less noisy patch set by taking a higher > level approach to solving the problem. there are a couple of problems that can occur: Imagine the following scenario.. machine (with fixed buffer size) is transmitting at N bps on average, but occasionally cannot send because the window is less than that needed for continuous sending. because of that, an intermediate queue does not overflow.. Now, we add adjustable queue sizes.. and suddenly we are overflowing the intermediate queue, and dropping packets. Since we don't have SACK we are resending lots of data and dropping back the window size at regular intervals. thus it is possible that under some situations teh adjustable buffer size may result in WORSE throughput. That brings up one thing I never liked about the current TCP, which is that we need to keep testing the upper window size to ensure that we notice if the bandwidth increases. Unfortunatly the only way we can do this is by increasing the windowsize, until we lose a packet (again). There was an interesting paper that explored loss-avoidance techniques. these included noticing teh increased latency that can occur when an intermediate node starts to become overloaded. Unfortunatly, usually we are not the person overloading it so us backing off doesn't help a lot in many cases. I did some work at whistle trying to predict and control remote congestion, but it was mostly useful when the slowest link was your local loop and didn't help much if the link was firther away. Still, it did allow interactive sessions to run in prarllel with bulk sessions and still get reasonable reaction times. basically I metered out the ACKS going the other way (out) in order to minimise the incoming queue size at the remote end of the incoming link. :-) This is all getting a bit far from the original topic, but I do worry that we may increase our packet loss with variable buffers and thus reduce throughout in the cases where teh fixed buffer was getting 80% or so of the theoretical throughout. julian  > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 2:44:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 1610F37B403 for ; Sun, 15 Jul 2001 02:43:45 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f6F9hhx06763; Sun, 15 Jul 2001 02:43:43 -0700 (PDT) (envelope-from dillon) Date: Sun, 15 Jul 2001 02:43:43 -0700 (PDT) From: Matt Dillon Message-Id: <200107150943.f6F9hhx06763@earth.backplane.com> To: Matt Dillon Cc: Leo Bicknell , Drew Eckhardt , hackers@FreeBSD.ORG Subject: eXperimental bandwidth delay product code (was Re: Network performance tuning.) References: <200107130128.f6D1SFE59148@earth.backplane.com> <200107130217.f6D2HET67695@revolt.poohsticks.org> <20010712223042.A77503@ussenterprise.ufp.org> <200107131708.f6DH8ve65071@earth.backplane.com> <20010713132903.A21847@ussenterprise.ufp.org> <200107131847.f6DIlJv67457@earth.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok, here is a patch set that tries to adjust the transmit congestion window and socket buffer space according to the bandwidth product of the link. THIS PATCH IS AGAINST STABLE! I make calculations based on bandwidth and round-trip-time. I spent a lot of time trying to write an algorithm that just used one or the other, but it turns out that bandwidth is only a stable metric when you are reducing the window, and rtt is only a stable metric when you are increasing the window. The algorithm is basically: decrease the window until we notice that the throughput is going down, then increase the window until we notice the RTT is going up (indicating buffering in the network). However, it took quite a few hours for me to find something that worked across a wide range of bandwidths and pipe delays. I had to deal with oscillations at high bandwidths, instability with the metrics being used in certain situations, and calculation overshoot and undershoot due to averaging. The biggest breakthrough occured when I stopped trying to time the code based on each ack coming back but instead timed it based on the round-trip-time interval (using the rtt calculation to trigger the windowing code). I used dummynet (aka 'ipfw pipe') as well as my LAN and two T1's two test it. sysctl's: net.inet.tcp.tcp_send_dynamic_enable 0 - disabled (old behavior) (default) 1 - enabled, no debugging output 2 - enabled, debug output to console (only really useful when testing one or two connections). net.inet.tcp.tcp_send_dynamic_min min buffering (4096 default) This parameter specifies the absolute smallest buffer size the dynamic windowing code will go down to. The default is 4096 bytes. You may want to set this to 4096 or 8192 to avoid degenerate conditions on very high speed networks, or if you want to enforce a minimum amount of socket buffering. I got some pretty awesome results when I tested it... I was able to create a really slow, low bandwidth dummynet link, start a transfer that utilizes 100% of the bandwidth, and I could still type in another xterm window that went through the same dummynet. There are immediate uses for something like this for people who have modem links, not to mention many other reasons. -Matt Index: kern/uipc_socket.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v retrieving revision 1.68.2.16 diff -u -r1.68.2.16 uipc_socket.c --- kern/uipc_socket.c 2001/06/14 20:46:06 1.68.2.16 +++ kern/uipc_socket.c 2001/07/13 04:05:38 @@ -519,12 +519,44 @@ snderr(so->so_proto->pr_flags & PR_CONNREQUIRED ? ENOTCONN : EDESTADDRREQ); } - space = sbspace(&so->so_snd); + + /* + * Calculate the optimal write-buffer size and then reduce + * by the amount already in use. Special handling is required + * to ensure that atomic writes still work as expected. + * + * Note: pru_sendpipe() only returns the optimal transmission + * pipe size, which is roughly equivalent to what can be + * transmitted and unacked. To avoid excessive process + * wakeups we double the returned value for our recommended + * buffer size. + */ + if (so->so_proto->pr_usrreqs->pru_sendpipe == NULL) { + space = sbspace(&so->so_snd); + } else { + space = (*so->so_proto->pr_usrreqs->pru_sendpipe)(so) * 2; + if (atomic && space < resid + clen) + space = resid + clen; + if (space < so->so_snd.sb_lowat) + space = so->so_snd.sb_lowat; + if (space > so->so_snd.sb_hiwat) + space = so->so_snd.sb_hiwat; + space = sbspace_using(&so->so_snd, space); + } + if (flags & MSG_OOB) space += 1024; + + /* + * Error out if the request is impossible to satisfy. + */ if ((atomic && resid > so->so_snd.sb_hiwat) || clen > so->so_snd.sb_hiwat) snderr(EMSGSIZE); + + /* + * Block if necessary. + */ if (space < resid + clen && uio && (atomic || space < so->so_snd.sb_lowat || space < clen)) { if (so->so_state & SS_NBIO) @@ -537,6 +569,7 @@ goto restart; } splx(s); + mp = ⊤ space -= clen; do { Index: kern/uipc_usrreq.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_usrreq.c,v retrieving revision 1.54.2.5 diff -u -r1.54.2.5 uipc_usrreq.c --- kern/uipc_usrreq.c 2001/03/05 13:09:01 1.54.2.5 +++ kern/uipc_usrreq.c 2001/07/13 03:56:02 @@ -427,7 +427,7 @@ uipc_connect2, pru_control_notsupp, uipc_detach, uipc_disconnect, uipc_listen, uipc_peeraddr, uipc_rcvd, pru_rcvoob_notsupp, uipc_send, uipc_sense, uipc_shutdown, uipc_sockaddr, - sosend, soreceive, sopoll + sosend, soreceive, sopoll, pru_sendpipe_notsupp }; /* Index: net/raw_usrreq.c =================================================================== RCS file: /home/ncvs/src/sys/net/raw_usrreq.c,v retrieving revision 1.18 diff -u -r1.18 raw_usrreq.c --- net/raw_usrreq.c 1999/08/28 00:48:28 1.18 +++ net/raw_usrreq.c 2001/07/13 03:56:12 @@ -296,5 +296,5 @@ pru_connect2_notsupp, pru_control_notsupp, raw_udetach, raw_udisconnect, pru_listen_notsupp, raw_upeeraddr, pru_rcvd_notsupp, pru_rcvoob_notsupp, raw_usend, pru_sense_null, raw_ushutdown, - raw_usockaddr, sosend, soreceive, sopoll + raw_usockaddr, sosend, soreceive, sopoll, pru_sendpipe_notsupp }; Index: net/rtsock.c =================================================================== RCS file: /home/ncvs/src/sys/net/rtsock.c,v retrieving revision 1.44.2.4 diff -u -r1.44.2.4 rtsock.c --- net/rtsock.c 2001/07/11 09:37:37 1.44.2.4 +++ net/rtsock.c 2001/07/13 03:56:16 @@ -266,7 +266,7 @@ pru_connect2_notsupp, pru_control_notsupp, rts_detach, rts_disconnect, pru_listen_notsupp, rts_peeraddr, pru_rcvd_notsupp, pru_rcvoob_notsupp, rts_send, pru_sense_null, rts_shutdown, rts_sockaddr, - sosend, soreceive, sopoll + sosend, soreceive, sopoll, pru_sendpipe_notsupp }; /*ARGSUSED*/ Index: netatalk/ddp_usrreq.c =================================================================== RCS file: /home/ncvs/src/sys/netatalk/ddp_usrreq.c,v retrieving revision 1.17 diff -u -r1.17 ddp_usrreq.c --- netatalk/ddp_usrreq.c 1999/04/27 12:21:14 1.17 +++ netatalk/ddp_usrreq.c 2001/07/13 03:56:25 @@ -581,5 +581,6 @@ at_setsockaddr, sosend, soreceive, - sopoll + sopoll, + pru_sendpipe_notsupp }; Index: netatm/atm_aal5.c =================================================================== RCS file: /home/ncvs/src/sys/netatm/atm_aal5.c,v retrieving revision 1.6 diff -u -r1.6 atm_aal5.c --- netatm/atm_aal5.c 1999/10/09 23:24:59 1.6 +++ netatm/atm_aal5.c 2001/07/13 03:56:40 @@ -101,7 +101,8 @@ atm_aal5_sockaddr, /* pru_sockaddr */ sosend, /* pru_sosend */ soreceive, /* pru_soreceive */ - sopoll /* pru_sopoll */ + sopoll, /* pru_sopoll */ + pru_sendpipe_notsupp /* pru_sendpipe */ }; #endif Index: netatm/atm_usrreq.c =================================================================== RCS file: /home/ncvs/src/sys/netatm/atm_usrreq.c,v retrieving revision 1.6 diff -u -r1.6 atm_usrreq.c --- netatm/atm_usrreq.c 1999/08/28 00:48:39 1.6 +++ netatm/atm_usrreq.c 2001/07/13 03:58:57 @@ -73,6 +73,10 @@ pru_sense_null, /* pru_sense */ atm_proto_notsupp1, /* pru_shutdown */ atm_proto_notsupp3, /* pru_sockaddr */ + NULL, /* pru_sosend */ + NULL, /* pru_soreceive */ + NULL, /* pru_sopoll */ + pru_sendpipe_notsupp /* pru_sendpipe */ }; #endif Index: netgraph/ng_socket.c =================================================================== RCS file: /home/ncvs/src/sys/netgraph/ng_socket.c,v retrieving revision 1.11.2.3 diff -u -r1.11.2.3 ng_socket.c --- netgraph/ng_socket.c 2001/02/02 11:59:27 1.11.2.3 +++ netgraph/ng_socket.c 2001/07/13 03:59:30 @@ -907,7 +907,8 @@ ng_setsockaddr, sosend, soreceive, - sopoll + sopoll, + pru_sendpipe_notsupp }; static struct pr_usrreqs ngd_usrreqs = { @@ -930,7 +931,8 @@ ng_setsockaddr, sosend, soreceive, - sopoll + sopoll, + pru_sendpipe_notsupp }; /* Index: netinet/ip_divert.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/ip_divert.c,v retrieving revision 1.42.2.3 diff -u -r1.42.2.3 ip_divert.c --- netinet/ip_divert.c 2001/02/27 09:41:15 1.42.2.3 +++ netinet/ip_divert.c 2001/07/13 03:59:47 @@ -540,5 +540,5 @@ pru_connect_notsupp, pru_connect2_notsupp, in_control, div_detach, div_disconnect, pru_listen_notsupp, in_setpeeraddr, pru_rcvd_notsupp, pru_rcvoob_notsupp, div_send, pru_sense_null, div_shutdown, - in_setsockaddr, sosend, soreceive, sopoll + in_setsockaddr, sosend, soreceive, sopoll, pru_sendpipe_notsupp }; Index: netinet/raw_ip.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/raw_ip.c,v retrieving revision 1.64.2.6 diff -u -r1.64.2.6 raw_ip.c --- netinet/raw_ip.c 2001/07/03 11:01:46 1.64.2.6 +++ netinet/raw_ip.c 2001/07/13 03:59:56 @@ -680,5 +680,5 @@ pru_connect2_notsupp, in_control, rip_detach, rip_disconnect, pru_listen_notsupp, in_setpeeraddr, pru_rcvd_notsupp, pru_rcvoob_notsupp, rip_send, pru_sense_null, rip_shutdown, - in_setsockaddr, sosend, soreceive, sopoll + in_setsockaddr, sosend, soreceive, sopoll, pru_sendpipe_notsupp }; Index: netinet/tcp_input.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_input.c,v retrieving revision 1.107.2.15 diff -u -r1.107.2.15 tcp_input.c --- netinet/tcp_input.c 2001/07/08 02:21:43 1.107.2.15 +++ netinet/tcp_input.c 2001/07/15 09:23:07 @@ -132,6 +132,14 @@ &drop_synfin, 0, "Drop TCP packets with SYN+FIN set"); #endif +int tcp_send_dynamic_enable = 0; +SYSCTL_INT(_net_inet_tcp, OID_AUTO, tcp_send_dynamic_enable, CTLFLAG_RW, + &tcp_send_dynamic_enable, 0, "enable dynamic control of sendspace"); +int tcp_send_dynamic_min = 4096; +SYSCTL_INT(_net_inet_tcp, OID_AUTO, tcp_send_dynamic_min, CTLFLAG_RW, + &tcp_send_dynamic_min, 0, "set minimum dynamic buffer space"); + + struct inpcbhead tcb; #define tcb6 tcb /* for KAME src sync over BSD*'s */ struct inpcbinfo tcbinfo; @@ -142,8 +150,9 @@ struct tcphdr *, struct mbuf *, int)); static int tcp_reass __P((struct tcpcb *, struct tcphdr *, int *, struct mbuf *)); -static void tcp_xmit_timer __P((struct tcpcb *, int)); +static void tcp_xmit_timer __P((struct tcpcb *, int, tcp_seq)); static int tcp_newreno __P((struct tcpcb *, struct tcphdr *)); +static void tcp_ack_dynamic_cwnd(struct tcpcb *tp, struct socket *so); /* Neighbor Discovery, Neighbor Unreachability Detection Upper layer hint. */ #ifdef INET6 @@ -931,12 +940,16 @@ tp->snd_nxt = tp->snd_max; tp->t_badrxtwin = 0; } - if ((to.to_flag & TOF_TS) != 0) - tcp_xmit_timer(tp, - ticks - to.to_tsecr + 1); - else if (tp->t_rtttime && - SEQ_GT(th->th_ack, tp->t_rtseq)) - tcp_xmit_timer(tp, ticks - tp->t_rtttime); + /* + * note: do not include a sequence number + * for anything but t_rtttime timings, see + * tcp_xmit_timer(). + */ + if (tp->t_rtttime && + SEQ_GT(th->th_ack, tp->t_rtseq)) + tcp_xmit_timer(tp, tp->t_rtttime, tp->t_rtseq); + else if ((to.to_flag & TOF_TS) != 0) + tcp_xmit_timer(tp, to.to_tsecr - 1, 0); acked = th->th_ack - tp->snd_una; tcpstat.tcps_rcvackpack++; tcpstat.tcps_rcvackbyte += acked; @@ -1927,11 +1940,14 @@ * Since we now have an rtt measurement, cancel the * timer backoff (cf., Phil Karn's retransmit alg.). * Recompute the initial retransmit timer. + * + * note: do not include a sequence number for anything + * but t_rtttime timings, see tcp_xmit_timer(). */ - if (to.to_flag & TOF_TS) - tcp_xmit_timer(tp, ticks - to.to_tsecr + 1); - else if (tp->t_rtttime && SEQ_GT(th->th_ack, tp->t_rtseq)) - tcp_xmit_timer(tp, ticks - tp->t_rtttime); + if (tp->t_rtttime && SEQ_GT(th->th_ack, tp->t_rtseq)) + tcp_xmit_timer(tp, tp->t_rtttime, tp->t_rtseq); + else if (to.to_flag & TOF_TS) + tcp_xmit_timer(tp, to.to_tsecr - 1, 0); /* * If all outstanding data is acked, stop retransmit @@ -1955,25 +1971,40 @@ /* * When new data is acked, open the congestion window. - * If the window gives us less than ssthresh packets - * in flight, open exponentially (maxseg per packet). - * Otherwise open linearly: maxseg per window - * (maxseg^2 / cwnd per packet). - */ - { - register u_int cw = tp->snd_cwnd; - register u_int incr = tp->t_maxseg; - - if (cw > tp->snd_ssthresh) - incr = incr * incr / cw; - /* + * We no longer use ssthresh because it just does not work + * right. Instead we try to avoid packet loss alltogether + * by avoiding excessive buffering of packet data in the + * network. + * * If t_dupacks != 0 here, it indicates that we are still * in NewReno fast recovery mode, so we leave the congestion * window alone. */ - if (tcp_do_newreno == 0 || tp->t_dupacks == 0) - tp->snd_cwnd = min(cw + incr,TCP_MAXWIN<snd_scale); + + if (tcp_do_newreno == 0 || tp->t_dupacks == 0) { + if (tp->t_txbandwidth && tcp_send_dynamic_enable) { + tcp_ack_dynamic_cwnd(tp, so); + } else { + int incr = tp->t_maxseg; + if (tp->snd_cwnd > tp->snd_ssthresh) + incr = incr * incr / tp->snd_cwnd; + tp->snd_cwnd += incr; + } + /* + * Enforce the minimum and maximum congestion window. + * Remember, this whole section is hit when we get a + * good ack so our window is at least 2 packets. + */ + if (tp->snd_cwnd > (TCP_MAXWIN << tp->snd_scale)) + tp->snd_cwnd = TCP_MAXWIN << tp->snd_scale; + if (tp->snd_cwnd < tp->t_maxseg * 2) + tp->snd_cwnd = tp->t_maxseg * 2; } + + /* + * Clean out buffered transmit data that we no longer need + * to keep around. + */ if (acked > so->so_snd.sb_cc) { tp->snd_wnd -= so->so_snd.sb_cc; sbdrop(&so->so_snd, (int)so->so_snd.sb_cc); @@ -2531,19 +2562,135 @@ panic("tcp_pulloutofband"); } +/* + * Dynamically adjust the congestion window. The sweet spot is slightly + * higher then the point where the bandwidth begins to degrade. Beyond + * that and the extra packets wind up being buffered in the network. + * + * We use an assymetric algorithm. We increase the window until we see + * a 5% increase the round-trip-time (SRTT). We then assume that this is + * the saturation point and decrease the window until we see a loss in + * bandwidth. + * + * This routine is master-timed off the round-trip time of the packet, + * allowing us to count round trips. Since bandwidth changes need at + * least an rtt cycle to occur, this is much better then counting packets + * and should be independant of bandwidth, pipe size, etc... + */ + +#define CWND_COUNT_START 2*1 +#define CWND_COUNT_DECR 2*3 +#define CWND_COUNT_INCR (CWND_COUNT_DECR + 2*8) +#define CWND_COUNT_STABILIZED (CWND_COUNT_INCR + 2*4) +#define CWND_COUNT_IMPROVING (CWND_COUNT_STABILIZED + 2*2) +#define CWND_COUNT_NOT_IMPROVING (CWND_COUNT_IMPROVING + 2*8) + +static void +tcp_ack_dynamic_cwnd(struct tcpcb *tp, struct socket *so) +{ + /* + * Make adjustments only at every complete round trip. + */ + if ((tp->t_txbwcount & 1) == 0) + return; + ++tp->t_txbwcount; + if (tp->t_txbwcount == CWND_COUNT_START) { + /* + * Set a rtt performance loss target of 20% + */ + tp->t_last_txbandwidth = tp->t_srtt + tp->t_srtt / 5; + } else if (tp->t_txbwcount >= CWND_COUNT_DECR && + tp->t_txbwcount < CWND_COUNT_INCR && + tp->t_srtt < tp->t_last_txbandwidth) { + /* + * Increase cwnd in maxseg chunks until we hit our target. + * The target represents the point where packets are starting + * to be buffered significantly in the network. + */ + tp->snd_cwnd += tp->t_maxseg; + tp->t_txbwcount = CWND_COUNT_START; + + /* + * snap target, required to avoid oscillation at high + * bandwidths + */ + if (tp->t_last_txbandwidth > tp->t_srtt + tp->t_srtt / 5) + tp->t_last_txbandwidth = tp->t_srtt + tp->t_srtt / 5; + /* + * Switch directions if we hit the top. + */ + if (tp->snd_cwnd >= so->so_snd.sb_hiwat || + tp->snd_cwnd >= (TCP_MAXWIN << tp->snd_scale)) { + tp->snd_cwnd = min(so->so_snd.sb_hiwat, (TCP_MAXWIN << tp->snd_scale)); + tp->t_txbwcount = CWND_COUNT_INCR - 2; + } + } else if (tp->t_txbwcount == CWND_COUNT_INCR) { + /* + * We hit 5% performance loss. Do nothing (wait until + * we stabilize). + */ + } else if (tp->t_txbwcount == CWND_COUNT_STABILIZED) { + /* + * srtt started to go up, we are at the pipe limit and + * must be at the maximum bandwidth. Reduce the window + * size until we loose 5% of our bandwidth. Use smaller + * chunks to avoid overshooting. + */ + tp->t_last_txbandwidth = tp->t_txbandwidth - tp->t_txbandwidth / 20; + tp->snd_cwnd -= tp->t_maxseg / 3; + } else if (tp->t_txbwcount >= CWND_COUNT_IMPROVING && + tp->t_txbandwidth > tp->t_last_txbandwidth) { + /* + * We saw an improvement, bump the window again, loop this + * state. If the pipeline isn't full then adding another + * packet should improve bandwidth by t_maxseg. Use seg / 4 + * to deal with any noise. + */ + tp->snd_cwnd -= tp->t_maxseg / 3; + + /* + * snap target, required to avoid oscillation at high + * bandwidths + */ + tp->t_txbwcount = CWND_COUNT_STABILIZED; + if (tp->t_last_txbandwidth < tp->t_txbandwidth - tp->t_txbandwidth / 20) + tp->t_last_txbandwidth = tp->t_txbandwidth - tp->t_txbandwidth / 20; + /* + * Switch directions if we hit bottom. + */ + if (tp->snd_cwnd < tcp_send_dynamic_min || + tp->snd_cwnd <= tp->t_maxseg * 2) { + tp->snd_cwnd = max(tcp_send_dynamic_min, tp->t_maxseg); + tp->t_txbwcount = 0; + } + } else if (tp->t_txbwcount >= CWND_COUNT_NOT_IMPROVING) { + /* + * No improvement, start upward again. loop to recalculate + * the -5%. We can recalculate immediately and do not require + * additional stabilization time. + */ + tp->snd_cwnd += tp->t_maxseg / 2; + tp->t_txbwcount = 0; + } +} + /* - * Collect new round-trip time estimate - * and update averages and current timeout. + * Collect new round-trip time estimate and update averages, current timeout, + * and transmit bandwidth. */ static void -tcp_xmit_timer(tp, rtt) +tcp_xmit_timer(tp, rtttime, rtseq) register struct tcpcb *tp; - int rtt; + int rtttime; + tcp_seq rtseq; { - register int delta; + int delta; + int rtt; tcpstat.tcps_rttupdated++; tp->t_rttupdated++; + + rtt = ticks - rtttime; if (tp->t_srtt != 0) { /* * srtt is stored as fixed point with 5 bits after the @@ -2582,8 +2729,30 @@ tp->t_srtt = rtt << TCP_RTT_SHIFT; tp->t_rttvar = rtt << (TCP_RTTVAR_SHIFT - 1); } - tp->t_rtttime = 0; tp->t_rxtshift = 0; + + /* + * Calculate the transmit-side throughput, in bytes/sec. This is + * used to dynamically size the congestion window to the pipe. We + * average over 2 packets only. rtseq is only passed for t_rtttime + * based timings, which in turn only occur on an interval close to + * the round trip time of the packet. We have to do this in order + * to get accurate bandwidths without having to take a long term + * average, which blows up the dynamic windowing algorithm. + */ + if (rtseq && rtt) { + tp->t_rtttime = 0; + if (tp->t_last_rtseq) { + int bw; + + bw = (rtseq - tp->t_last_rtseq) * hz / rtt; + bw = (tp->t_txbandwidth + bw) / 2; + tp->t_txbandwidth = bw; + tp->t_txbwcount |= 1; + } + tp->t_last_rtseq = rtseq; + tp->t_last_rtttime = rtttime; + } /* * the retransmit should happen at rtt + 4 * rttvar. Index: netinet/tcp_usrreq.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_usrreq.c,v retrieving revision 1.51.2.7 diff -u -r1.51.2.7 tcp_usrreq.c --- netinet/tcp_usrreq.c 2001/07/08 02:21:44 1.51.2.7 +++ netinet/tcp_usrreq.c 2001/07/15 05:31:52 @@ -494,6 +494,47 @@ } /* + * Calculate the optimal transmission pipe size. This is used to limit the + * amount of data we allow to be buffered in order to reduce memory use, + * allowing connections to dynamically adjust to the bandwidth product of + * their links. + * + * For tcp we return approximately the congestion window size, which + * winds up being the bandwidth delay product in a lossless environment. + */ +static int +tcp_usr_sendpipe(struct socket *so) +{ + struct inpcb *inp; + int size = so->so_snd.sb_hiwat; + + if (tcp_send_dynamic_enable && (inp = sotoinpcb(so)) != NULL) { + struct tcpcb *tp; + + if ((tp = intotcpcb(inp)) != NULL) { + size = tp->snd_cwnd; + if (size > tp->snd_wnd) + size = tp->snd_wnd; + + /* + * debugging & minimum transmit buffer availability + */ + if (tcp_send_dynamic_enable > 1) { + static int last_hz; + + if (last_hz != ticks / hz) { + last_hz = ticks / hz; + printf("tcp_user_sendpipe: size=%d bw=%d lbw=%d count=%d srtt=%d\n", size, tp->t_txbandwidth, tp->t_last_txbandwidth, tp->t_txbwcount, tp->t_srtt); + } + } + if (size < tcp_send_dynamic_min) + size = tcp_send_dynamic_min; + } + } + return(size); +} + +/* * Do a send by putting data in output queue and updating urgent * marker if URG set. Possibly send more data. Unlike the other * pru_*() routines, the mbuf chains are our responsibility. We @@ -674,7 +715,7 @@ tcp_usr_connect, pru_connect2_notsupp, in_control, tcp_usr_detach, tcp_usr_disconnect, tcp_usr_listen, in_setpeeraddr, tcp_usr_rcvd, tcp_usr_rcvoob, tcp_usr_send, pru_sense_null, tcp_usr_shutdown, - in_setsockaddr, sosend, soreceive, sopoll + in_setsockaddr, sosend, soreceive, sopoll, tcp_usr_sendpipe }; #ifdef INET6 @@ -683,7 +724,7 @@ tcp6_usr_connect, pru_connect2_notsupp, in6_control, tcp_usr_detach, tcp_usr_disconnect, tcp6_usr_listen, in6_mapped_peeraddr, tcp_usr_rcvd, tcp_usr_rcvoob, tcp_usr_send, pru_sense_null, tcp_usr_shutdown, - in6_mapped_sockaddr, sosend, soreceive, sopoll + in6_mapped_sockaddr, sosend, soreceive, sopoll, tcp_usr_sendpipe }; #endif /* INET6 */ Index: netinet/tcp_var.h =================================================================== RCS file: /home/ncvs/src/sys/netinet/tcp_var.h,v retrieving revision 1.56.2.7 diff -u -r1.56.2.7 tcp_var.h --- netinet/tcp_var.h 2001/07/08 02:21:44 1.56.2.7 +++ netinet/tcp_var.h 2001/07/15 07:25:48 @@ -95,6 +95,7 @@ #define TF_SENDCCNEW 0x08000 /* send CCnew instead of CC in SYN */ #define TF_MORETOCOME 0x10000 /* More data to be appended to sock */ #define TF_LQ_OVERFLOW 0x20000 /* listen queue overflow */ +#define TF_BWSCANUP 0x40000 int t_force; /* 1 if forcing out a byte */ tcp_seq snd_una; /* send unacknowledged */ @@ -128,6 +129,11 @@ u_long t_starttime; /* time connection was established */ int t_rtttime; /* round trip time */ tcp_seq t_rtseq; /* sequence number being timed */ + int t_last_rtttime; + tcp_seq t_last_rtseq; /* sequence number being timed */ + int t_txbandwidth; /* transmit bandwidth/delay */ + int t_last_txbandwidth; + int t_txbwcount; int t_rxtcur; /* current retransmit value (ticks) */ u_int t_maxseg; /* maximum segment size */ @@ -371,6 +377,8 @@ extern int tcp_do_newreno; extern int ss_fltsz; extern int ss_fltsz_local; +extern int tcp_send_dynamic_enable; +extern int tcp_send_dynamic_min; void tcp_canceltimers __P((struct tcpcb *)); struct tcpcb * Index: netinet/udp_usrreq.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/udp_usrreq.c,v retrieving revision 1.64.2.11 diff -u -r1.64.2.11 udp_usrreq.c --- netinet/udp_usrreq.c 2001/07/03 11:01:47 1.64.2.11 +++ netinet/udp_usrreq.c 2001/07/13 04:00:17 @@ -923,6 +923,6 @@ pru_connect2_notsupp, in_control, udp_detach, udp_disconnect, pru_listen_notsupp, in_setpeeraddr, pru_rcvd_notsupp, pru_rcvoob_notsupp, udp_send, pru_sense_null, udp_shutdown, - in_setsockaddr, sosend, soreceive, sopoll + in_setsockaddr, sosend, soreceive, sopoll, pru_sendpipe_notsupp }; Index: netinet6/raw_ip6.c =================================================================== RCS file: /home/ncvs/src/sys/netinet6/raw_ip6.c,v retrieving revision 1.7.2.3 diff -u -r1.7.2.3 raw_ip6.c --- netinet6/raw_ip6.c 2001/07/03 11:01:55 1.7.2.3 +++ netinet6/raw_ip6.c 2001/07/13 04:00:25 @@ -733,5 +733,5 @@ pru_connect2_notsupp, in6_control, rip6_detach, rip6_disconnect, pru_listen_notsupp, in6_setpeeraddr, pru_rcvd_notsupp, pru_rcvoob_notsupp, rip6_send, pru_sense_null, rip6_shutdown, - in6_setsockaddr, sosend, soreceive, sopoll + in6_setsockaddr, sosend, soreceive, sopoll, pru_sendpipe_notsupp }; Index: netipx/ipx_usrreq.c =================================================================== RCS file: /home/ncvs/src/sys/netipx/ipx_usrreq.c,v retrieving revision 1.26.2.1 diff -u -r1.26.2.1 ipx_usrreq.c --- netipx/ipx_usrreq.c 2001/02/22 09:44:18 1.26.2.1 +++ netipx/ipx_usrreq.c 2001/07/13 04:00:38 @@ -89,7 +89,7 @@ ipx_connect, pru_connect2_notsupp, ipx_control, ipx_detach, ipx_disconnect, pru_listen_notsupp, ipx_peeraddr, pru_rcvd_notsupp, pru_rcvoob_notsupp, ipx_send, pru_sense_null, ipx_shutdown, - ipx_sockaddr, sosend, soreceive, sopoll + ipx_sockaddr, sosend, soreceive, sopoll, pru_sendpipe_notsupp }; struct pr_usrreqs ripx_usrreqs = { @@ -97,7 +97,7 @@ ipx_connect, pru_connect2_notsupp, ipx_control, ipx_detach, ipx_disconnect, pru_listen_notsupp, ipx_peeraddr, pru_rcvd_notsupp, pru_rcvoob_notsupp, ipx_send, pru_sense_null, ipx_shutdown, - ipx_sockaddr, sosend, soreceive, sopoll + ipx_sockaddr, sosend, soreceive, sopoll, pru_sendpipe_notsupp }; /* Index: netipx/spx_usrreq.c =================================================================== RCS file: /home/ncvs/src/sys/netipx/spx_usrreq.c,v retrieving revision 1.27.2.1 diff -u -r1.27.2.1 spx_usrreq.c --- netipx/spx_usrreq.c 2001/02/22 09:44:18 1.27.2.1 +++ netipx/spx_usrreq.c 2001/07/13 04:00:46 @@ -107,7 +107,7 @@ spx_connect, pru_connect2_notsupp, ipx_control, spx_detach, spx_usr_disconnect, spx_listen, ipx_peeraddr, spx_rcvd, spx_rcvoob, spx_send, pru_sense_null, spx_shutdown, - ipx_sockaddr, sosend, soreceive, sopoll + ipx_sockaddr, sosend, soreceive, sopoll, pru_sendpipe_notsupp }; struct pr_usrreqs spx_usrreq_sps = { @@ -115,7 +115,7 @@ spx_connect, pru_connect2_notsupp, ipx_control, spx_detach, spx_usr_disconnect, spx_listen, ipx_peeraddr, spx_rcvd, spx_rcvoob, spx_send, pru_sense_null, spx_shutdown, - ipx_sockaddr, sosend, soreceive, sopoll + ipx_sockaddr, sosend, soreceive, sopoll, pru_sendpipe_notsupp }; void Index: netkey/keysock.c =================================================================== RCS file: /home/ncvs/src/sys/netkey/keysock.c,v retrieving revision 1.1.2.2 diff -u -r1.1.2.2 keysock.c --- netkey/keysock.c 2001/07/03 11:02:00 1.1.2.2 +++ netkey/keysock.c 2001/07/13 04:00:51 @@ -586,7 +586,7 @@ key_disconnect, pru_listen_notsupp, key_peeraddr, pru_rcvd_notsupp, pru_rcvoob_notsupp, key_send, pru_sense_null, key_shutdown, - key_sockaddr, sosend, soreceive, sopoll + key_sockaddr, sosend, soreceive, sopoll, pru_sendpipe_notsupp }; /* sysctl */ Index: netnatm/natm.c =================================================================== RCS file: /home/ncvs/src/sys/netnatm/natm.c,v retrieving revision 1.12 diff -u -r1.12 natm.c --- netnatm/natm.c 2000/02/13 03:32:03 1.12 +++ netnatm/natm.c 2001/07/13 04:01:15 @@ -413,7 +413,7 @@ natm_usr_detach, natm_usr_disconnect, pru_listen_notsupp, natm_usr_peeraddr, pru_rcvd_notsupp, pru_rcvoob_notsupp, natm_usr_send, pru_sense_null, natm_usr_shutdown, - natm_usr_sockaddr, sosend, soreceive, sopoll + natm_usr_sockaddr, sosend, soreceive, sopoll, pru_sendpipe_notsupp }; #else /* !FREEBSD_USRREQS */ Index: sys/protosw.h =================================================================== RCS file: /home/ncvs/src/sys/sys/protosw.h,v retrieving revision 1.28.2.2 diff -u -r1.28.2.2 protosw.h --- sys/protosw.h 2001/07/03 11:02:01 1.28.2.2 +++ sys/protosw.h 2001/07/13 04:02:15 @@ -228,6 +228,7 @@ struct mbuf **controlp, int *flagsp)); int (*pru_sopoll) __P((struct socket *so, int events, struct ucred *cred, struct proc *p)); + int (*pru_sendpipe) __P((struct socket *so)); }; int pru_accept_notsupp __P((struct socket *so, struct sockaddr **nam)); @@ -240,6 +241,7 @@ int pru_rcvd_notsupp __P((struct socket *so, int flags)); int pru_rcvoob_notsupp __P((struct socket *so, struct mbuf *m, int flags)); int pru_sense_null __P((struct socket *so, struct stat *sb)); +#define pru_sendpipe_notsupp NULL #endif /* _KERNEL */ Index: sys/socketvar.h =================================================================== RCS file: /home/ncvs/src/sys/sys/socketvar.h,v retrieving revision 1.46.2.5 diff -u -r1.46.2.5 socketvar.h --- sys/socketvar.h 2001/02/26 04:23:21 1.46.2.5 +++ sys/socketvar.h 2001/07/13 03:47:25 @@ -188,9 +188,11 @@ * still be negative (cc > hiwat or mbcnt > mbmax). Should detect * overflow and return 0. Should use "lmin" but it doesn't exist now. */ -#define sbspace(sb) \ - ((long) imin((int)((sb)->sb_hiwat - (sb)->sb_cc), \ +#define sbspace_using(sb, hiwat) \ + ((long) imin((int)((hiwat) - (sb)->sb_cc), \ (int)((sb)->sb_mbmax - (sb)->sb_mbcnt))) + +#define sbspace(sb) sbspace_using(sb, (sb)->sb_hiwat) /* do we have to send all at once on a socket? */ #define sosendallatonce(so) \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 3:49:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hpux37.dc.engr.scu.edu (hpux37.dc.engr.scu.edu [129.210.16.37]) by hub.freebsd.org (Postfix) with ESMTP id 5C9E937B403 for ; Sun, 15 Jul 2001 03:49:31 -0700 (PDT) (envelope-from dclark@applmath.scu.edu) Received: from localhost (dclark@localhost) by hpux37.dc.engr.scu.edu (8.10.2/8.10.2) with ESMTP id f6CHo6L26365 for ; Thu, 12 Jul 2001 10:50:07 -0700 (PDT) Date: Thu, 12 Jul 2001 10:50:06 -0700 (PDT) From: "Dorr H. Clark" To: freebsd-hackers@freebsd.org Subject: now OK, was - need help: gdb -k 4.16/7 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Some time ago, I wrote: > I am experimenting with porting an application > from the FreeBSD 2.2.x series to a more modern release, > and as such I have occaision to debug kernel core files > under the old release using the gdb -k option > (saved via savecore). The problem is the old kernel > has been customized with a different load address > (new style 0xC0000000 vs. old style 0xF0000000). > ... The problem is the resulting gdb -k sessions > are not fully functional... 80% of all problems that appear to be OS problems are really application problems. This was one of them. It turns out that there were more changes than just the load address, the application malloc() calls in the custom kernel had also been changed from 512, 1k, & 2k (sub-page fragments) to full page allocations (actually multi-page). As you may know, FreeBSD malloc()s of sub-page fragments in the kernel are permanent, when they are freed they are put on queues according to size buckets. In contrast, freeing multiple whole pages truly frees the pages, including unmapping! So when the kernel went down, the at_shutdown() call was freeing all the memory, and unmapping it. This side effect was never noticed in the old system, the debugging of cores was actually relying on the stale mapping of freed memory (I didn't do this code myself, so I didn't catch it before). The fix was only to free() in in the at_shutdown() call IF a normal shutdown is in progress (i.e.- not a panic, page_fault, etc.). I just wanted to share the absolution of the product for the permanent record. The custom FreeBSD kernel is doing the Right Thing (tm), gdb is doing the Right Thing (tm), savecore and wddump() are doing the Right Thing (tm), and when the application code is doing the right thing the cores are completely debuggable. Thanks for the previous responses, it was helpful in straightening this bug out, -Dorr H. Clark Santa Clara University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 4:19:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 9FA4D37B401 for ; Sun, 15 Jul 2001 04:19:49 -0700 (PDT) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.11.4/8.11.1) id f6FBJFK60907; Sun, 15 Jul 2001 06:19:15 -0500 (CDT) Date: Sun, 15 Jul 2001 06:19:15 -0500 From: Tim To: Matt Dillon Cc: Leo Bicknell , Drew Eckhardt , hackers@FreeBSD.ORG Subject: Re: eXperimental bandwidth delay product code (was Re: Network performance tuning.) Message-ID: <20010715061915.A59691@futuresouth.com> References: <200107130128.f6D1SFE59148@earth.backplane.com> <200107130217.f6D2HET67695@revolt.poohsticks.org> <20010712223042.A77503@ussenterprise.ufp.org> <200107131708.f6DH8ve65071@earth.backplane.com> <20010713132903.A21847@ussenterprise.ufp.org> <200107131847.f6DIlJv67457@earth.backplane.com> <200107150943.f6F9hhx06763@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107150943.f6F9hhx06763@earth.backplane.com>; from dillon@earth.backplane.com on Sun, Jul 15, 2001 at 02:43:43AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Cool! We were just commenting that it's too bad dummynet/ALTQ really couldn't help the interactive response for us dial-up users. Anyway, I just tried this on my dial-up connection on a fresh -STABLE but don't really notice any appreciable difference. net.inet.tcp.tcp_send_dynamic_enable: 1 net.inet.tcp.tcp_send_dynamic_min: 1024 (tried it with default 4096 too) My ssh response is still about 3 or 4 seconds behind my typing. What should a dial-up user expect? Thanks! Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 7: 3:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by hub.freebsd.org (Postfix) with ESMTP id ADC5E37B406 for ; Sun, 15 Jul 2001 07:03:11 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 4397817D28; Sun, 15 Jul 2001 16:03:10 +0200 (CEST) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.11.4/8.11.3) id f6FDxff15191 for hackers@freebsd.org; Sun, 15 Jul 2001 15:59:41 +0200 (CEST) (envelope-from schweikh) Date: Sun, 15 Jul 2001 15:59:41 +0200 From: Jens Schweikhardt To: hackers@freebsd.org Subject: Whitespace at end of line Message-ID: <20010715155941.C1165@schweikhardt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hello, world\n Dima and /me recently started weeding out white space at end of line for the man pages. I want to widen the weeding to include as much files as possible under /usr/src. We currently have 280kbytes (yes, more than a quarter meg) sitting there; that's counting only the spaces and tabs at EOL, not the whole line. I've got a perl script that removes the white space at EOL automagically, but before I break anything I would like to ask the combined hacker wisdom if you can think of any occasion where whitespace at EOL would be significant and must not be removed. The script already skips non-plain and binary files (as detected by perl's -T/-B file test operators). The only case I can think of right now is a file where we have a backslash followed by whitespace followed by EOL. Removing the whitespace may change semantics if the file type supports the notion of backslash continuation lines, eg. a shell script with echo foo\ <- with a space after the \ bar in it, which would turn to echo "foobar" instead of echo "foo " and executing bar. However, C source should be safe to just s/[ \t]+$//g, I can't think of a valid way to have {backslash whitespace EOL} in C source outside of comments (where the whitespace can safely be removed because the backslash has no continuation semantics.) Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 7:33:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id 2D64837B405 for ; Sun, 15 Jul 2001 07:33:54 -0700 (PDT) (envelope-from bicknell@ussenterprise.ufp.org) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id f6FEXYt64766; Sun, 15 Jul 2001 10:33:34 -0400 (EDT) (envelope-from bicknell) Date: Sun, 15 Jul 2001 10:33:34 -0400 From: Leo Bicknell To: Julian Elischer Cc: Matt Dillon , Leo Bicknell , Drew Eckhardt , hackers@FreeBSD.ORG Subject: Re: Network performance tuning. Message-ID: <20010715103334.A64293@ussenterprise.ufp.org> Mail-Followup-To: Leo Bicknell , Julian Elischer , Matt Dillon , Leo Bicknell , Drew Eckhardt , hackers@FreeBSD.ORG References: <200107130128.f6D1SFE59148@earth.backplane.com> <200107130217.f6D2HET67695@revolt.poohsticks.org> <20010712223042.A77503@ussenterprise.ufp.org> <200107131708.f6DH8ve65071@earth.backplane.com> <3B515097.6551A530@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B515097.6551A530@elischer.org>; from julian@elischer.org on Sun, Jul 15, 2001 at 01:13:11AM -0700 Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 15, 2001 at 01:13:11AM -0700, Julian Elischer wrote: > This is all getting a bit far from the original topic, but > I do worry that we may increase our packet loss with variable buffers and thus > reduce throughout in the cases where teh fixed buffer was getting 80% > or so of the theoretical throughout. Packet loss is not always a bad thing. Let me use an admittedly extreme example: Consider a backup server across country from four machines it's trying to back up nightly. So we have high (let's say 70ms) RTT's, and let's say for the sake of argument the limiting factor is a DS-3 in the middle, 45 MBits/sec. Each connection can get 16384 * 1000 / 70 = 234057 bytes/sec, or about 1.87 Mbits/sec. Multiply by the 4 machines, and we get network utilization of 7.48 Mbits/sec, about 16% of the DS-3. Now, we implement some sort of code that can increase the amount of socket buffering space. As a result, the window can grow (per connection) large enough to fill a DS-3, so the 4 hosts must fight for the bandwidth available. I don't have any great math for how we get here, but TCP in normal situations rarely produces more than 5% packet loss (10% absolute max), since it backs off when congestion occurs. I'll go with 5% as an upper bound. With that packet loss, TCP now gets the DS-3 much closer to full, let's say 90%, or 40.5 Mbits/sec (it should be higher than 90%, but again, I'm worst casing). In the aggregate that will be spread across the 4 connections evenly, or 10.12 Mbits/sec per connection. The question to be asked is, which is better, 1.87 MBit's sec with no packet loss, or 10.12 Mbits/sec w/5% packet loss. Clearly the latter gives better performance, even with packet loss. Clearly knowing the end to end link bandwidth and 'just' filling it would be better, but packet loss, at least in the concept of TCP flow control is not all bad. Something else to remember is not everyone plays fair, so if we stay to 80% of available, and everyone else pushes to packet loss we will in general be pushed out. -- Leo Bicknell - bicknell@ufp.org Systems Engineer - Internetworking Engineer - CCIE 3440 Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 8: 2: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 56A3C37B408 for ; Sun, 15 Jul 2001 08:02:02 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f6FF1hV86115; Sun, 15 Jul 2001 17:01:45 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f6FF1o426789; Sun, 15 Jul 2001 17:01:50 +0200 (CEST) Date: Sun, 15 Jul 2001 17:01:49 +0200 From: Bernd Walter To: Tim Cc: Matt Dillon , Leo Bicknell , Drew Eckhardt , hackers@FreeBSD.ORG Subject: Re: eXperimental bandwidth delay product code (was Re: Network performance tuning.) Message-ID: <20010715170149.C26435@cicely20.cicely.de> References: <200107130128.f6D1SFE59148@earth.backplane.com> <200107130217.f6D2HET67695@revolt.poohsticks.org> <20010712223042.A77503@ussenterprise.ufp.org> <200107131708.f6DH8ve65071@earth.backplane.com> <20010713132903.A21847@ussenterprise.ufp.org> <200107131847.f6DIlJv67457@earth.backplane.com> <200107150943.f6F9hhx06763@earth.backplane.com> <20010715061915.A59691@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010715061915.A59691@futuresouth.com>; from tim@futuresouth.com on Sun, Jul 15, 2001 at 06:19:15AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 15, 2001 at 06:19:15AM -0500, Tim wrote: > Cool! We were just commenting that it's too bad dummynet/ALTQ really > couldn't help the interactive response for us dial-up users. Anyway, I > just tried this on my dial-up connection on a fresh -STABLE but don't > really notice any appreciable difference. > > net.inet.tcp.tcp_send_dynamic_enable: 1 > net.inet.tcp.tcp_send_dynamic_min: 1024 (tried it with default 4096 too) > > My ssh response is still about 3 or 4 seconds behind my typing. What > should a dial-up user expect? If you don't see a difference with a dial-up line you see exactly what is expected from this - which is a good sign. The situations where it should bring performance are different from yours. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 9:57:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 7D8C537B403 for ; Sun, 15 Jul 2001 09:57:11 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f6FGv5308274; Sun, 15 Jul 2001 09:57:05 -0700 (PDT) (envelope-from dillon) Date: Sun, 15 Jul 2001 09:57:05 -0700 (PDT) From: Matt Dillon Message-Id: <200107151657.f6FGv5308274@earth.backplane.com> To: Tim Cc: Leo Bicknell , Drew Eckhardt , hackers@FreeBSD.ORG Subject: Re: eXperimental bandwidth delay product code (was Re: Network performance tuning.) References: <200107130128.f6D1SFE59148@earth.backplane.com> <200107130217.f6D2HET67695@revolt.poohsticks.org> <20010712223042.A77503@ussenterprise.ufp.org> <200107131708.f6DH8ve65071@earth.backplane.com> <20010713132903.A21847@ussenterprise.ufp.org> <200107131847.f6DIlJv67457@earth.backplane.com> <200107150943.f6F9hhx06763@earth.backplane.com> <20010715061915.A59691@futuresouth.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :Cool! We were just commenting that it's too bad dummynet/ALTQ really :couldn't help the interactive response for us dial-up users. Anyway, I :just tried this on my dial-up connection on a fresh -STABLE but don't :really notice any appreciable difference. : :net.inet.tcp.tcp_send_dynamic_enable: 1 :net.inet.tcp.tcp_send_dynamic_min: 1024 (tried it with default 4096 too) : :My ssh response is still about 3 or 4 seconds behind my typing. What :should a dial-up user expect? : :Thanks! : :Tim Well, what this code does is manage the case where you are streaming data in the transmit direction *and* trying to type at the same time over another connection. It will not improve latency on an idle connection that you are typing over. Even in the streaming case with this algorithm the minimum window is two t_maxseg packets and that will have a noticeable effect on latency over a dialup no matter what. What this protocol is supposed to save you from, at least insofar as a dialup goes, is that it should prevent an upload from killing terminal performance entirely (e.g. it should prevent 10-20 second latency on keystrokes). 3-4 seconds of latency over an idle dialup is really bad. I still get sub-second responsiveness when I run ssh over a dialup. I always use compression over dialups (ssh -C ...) and it makes a big difference. This protocol also tends to devolve into a degenerate small-buffer case (which is what it is supposed to do) when the connection is running over a low bandwidth high latency link. It only takes a two or three packet window to fill the link in such cases and the minimum is two packets. You might be able to improve performance by negotiating a smaller MTU (if this is a PPP connection), but no matter what you will never do better then the normal typing performance on an idle link that you already get. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 10: 5:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 3B71B37B407 for ; Sun, 15 Jul 2001 10:05:23 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f6FH5Gd08326; Sun, 15 Jul 2001 10:05:16 -0700 (PDT) (envelope-from dillon) Date: Sun, 15 Jul 2001 10:05:16 -0700 (PDT) From: Matt Dillon Message-Id: <200107151705.f6FH5Gd08326@earth.backplane.com> To: Leo Bicknell Cc: Julian Elischer , Leo Bicknell , Drew Eckhardt , hackers@FreeBSD.ORG Subject: Re: Network performance tuning. References: <200107130128.f6D1SFE59148@earth.backplane.com> <200107130217.f6D2HET67695@revolt.poohsticks.org> <20010712223042.A77503@ussenterprise.ufp.org> <200107131708.f6DH8ve65071@earth.backplane.com> <3B515097.6551A530@elischer.org> <20010715103334.A64293@ussenterprise.ufp.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Packet loss is not always a bad thing. Let me use an admittedly :extreme example: : :Consider a backup server across country from four machines it's :trying to back up nightly. So we have high (let's say 70ms) RTT's, :and let's say for the sake of argument the limiting factor is a :DS-3 in the middle, 45 MBits/sec. : :Each connection can get 16384 * 1000 / 70 = 234057 bytes/sec, or :about 1.87 Mbits/sec. Multiply by the 4 machines, and we get :network utilization of 7.48 Mbits/sec, about 16% of the DS-3. : :Now, we implement some sort of code that can increase the amount :of socket buffering space. As a result, the window can grow (per :connection) large enough to fill a DS-3, so the 4 hosts must fight :for the bandwidth available. : :I don't have any great math for how we get here, but TCP in normal :situations rarely produces more than 5% packet loss (10% absolute :max), since it backs off when congestion occurs. I'll go with 5% :as an upper bound. With that packet loss, TCP now gets the DS-3 :much closer to full, let's say 90%, or 40.5 Mbits/sec (it should :be higher than 90%, but again, I'm worst casing). In the aggregate :that will be spread across the 4 connections evenly, or 10.12 :Mbits/sec per connection. : :The question to be asked is, which is better, 1.87 MBit's sec with :no packet loss, or 10.12 Mbits/sec w/5% packet loss. Clearly the :latter gives better performance, even with packet loss. : :Clearly knowing the end to end link bandwidth and 'just' filling it :would be better, but packet loss, at least in the concept of TCP :flow control is not all bad. Something else to remember is not :everyone plays fair, so if we stay to 80% of available, and everyone :else pushes to packet loss we will in general be pushed out. : :-- :Leo Bicknell - bicknell@ufp.org Well, 4 connections isn't enough to generate packet loss. All that happens is that routers inbetween start buffering the packets. If you had a *huge* tcp window size then the routers inbetween could run out of packet space and then packet loss would start to occur. Routers tend to have a lot of buffer space, though. The real killer is run-away latencies rather then packet loss. On the other hand, something like the experimental bandwidth delay product code I posted would do very well running 4 connections over such a link, because it would detect the point where the routers start buffering the data (by noticing the increased latency) and back-off before the packet loss occured. It doesn't care how many connections are running in parallel. The downside is that the algorithm becomes less stable as you increase the number of connections going between the same two end points. The stability in the face of lots of parallel connections is something that needs to be tested. Also, the algorithm is less helpful when it has to figure out the optimal transmit buffer size for every new connection (consider a web server). I am considering ripping out the ssthresh junk from the stack, which does not work virtually at all, and using the route table's ssthresh field to set the initial buffer size for the algorithm. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 10:14: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id 20D7037B403 for ; Sun, 15 Jul 2001 10:14:02 -0700 (PDT) (envelope-from bicknell@ussenterprise.ufp.org) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id f6FHDpP72154; Sun, 15 Jul 2001 13:13:51 -0400 (EDT) (envelope-from bicknell) Date: Sun, 15 Jul 2001 13:13:51 -0400 From: Leo Bicknell To: Matt Dillon Cc: Leo Bicknell , Julian Elischer , Drew Eckhardt , hackers@FreeBSD.ORG Subject: Re: Network performance tuning. Message-ID: <20010715131351.A72087@ussenterprise.ufp.org> Mail-Followup-To: Leo Bicknell , Matt Dillon , Leo Bicknell , Julian Elischer , Drew Eckhardt , hackers@FreeBSD.ORG References: <200107130128.f6D1SFE59148@earth.backplane.com> <200107130217.f6D2HET67695@revolt.poohsticks.org> <20010712223042.A77503@ussenterprise.ufp.org> <200107131708.f6DH8ve65071@earth.backplane.com> <3B515097.6551A530@elischer.org> <20010715103334.A64293@ussenterprise.ufp.org> <200107151705.f6FH5Gd08326@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107151705.f6FH5Gd08326@earth.backplane.com>; from dillon@earth.backplane.com on Sun, Jul 15, 2001 at 10:05:16AM -0700 Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 15, 2001 at 10:05:16AM -0700, Matt Dillon wrote: > Well, 4 connections isn't enough to generate packet loss. All > that happens is that routers inbetween start buffering the packets. > If you had a *huge* tcp window size then the routers inbetween could > run out of packet space and then packet loss would start to occur. > Routers tend to have a lot of buffer space, though. The real killer > is run-away latencies rather then packet loss. Sure it is, in a lot of cases. Keep in mind RED is becoming the default (in paritcular one major router vendor ships with it as the default now), so in general routers will discard packets _before_ they will buffer them. > Also, the algorithm is less helpful when it has to figure out the > optimal transmit buffer size for every new connection (consider a web > server). I am considering ripping out the ssthresh junk from the stack, > which does not work virtually at all, and using the route table's > ssthresh field to set the initial buffer size for the algorithm. This would probably be a big win, as in web-server type cases there are many small connections back to back. Now, if you want a really radical idea, how about not doing slow-start on the second-nth connection, but starting where the previous connection left off. Whoa, that's loaded with issues. :-) -- Leo Bicknell - bicknell@ufp.org Systems Engineer - Internetworking Engineer - CCIE 3440 Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 10:32:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 72A0537B401 for ; Sun, 15 Jul 2001 10:32:40 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f6FHWd008447; Sun, 15 Jul 2001 10:32:39 -0700 (PDT) (envelope-from dillon) Date: Sun, 15 Jul 2001 10:32:39 -0700 (PDT) From: Matt Dillon Message-Id: <200107151732.f6FHWd008447@earth.backplane.com> To: Leo Bicknell , Julian Elischer , Drew Eckhardt , hackers@FreeBSD.ORG Subject: Re: Network performance tuning. References: <200107130128.f6D1SFE59148@earth.backplane.com> <200107130217.f6D2HET67695@revolt.poohsticks.org> <20010712223042.A77503@ussenterprise.ufp.org> <200107131708.f6DH8ve65071@earth.backplane.com> <3B515097.6551A530@elischer.org> <20010715103334.A64293@ussenterprise.ufp.org> <200107151705.f6FH5Gd08326@earth.backplane.com> <20010715131351.A72087@ussenterprise.ufp.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :On Sun, Jul 15, 2001 at 10:05:16AM -0700, Matt Dillon wrote: :> Well, 4 connections isn't enough to generate packet loss. All :> that happens is that routers inbetween start buffering the packets. :> If you had a *huge* tcp window size then the routers inbetween could :> run out of packet space and then packet loss would start to occur. :> Routers tend to have a lot of buffer space, though. The real killer :> is run-away latencies rather then packet loss. : :Sure it is, in a lot of cases. Keep in mind RED is becoming the :default (in paritcular one major router vendor ships with it as :the default now), so in general routers will discard packets _before_ :they will buffer them. That isn't what RED does, not really. Basically it statistically drops packets at an ever-increasing rate as the buffer fills up. It does NOT prevent packet buffering from occuring, and it doesn't kick in the moment buffering is used -- the buffer has to start to fill up significantly before RED has an effect. I personally do not believe that RED has a future or, if it does, that it will wind up only kicking in when queues would otherwise start to drop packets anyway, as a fail-safe rather then as a prime bandwidth management system. The bandwidth delay product code kicks in instantly - before a significant number of packets get queued at the router, so it is effectively under RED's radar. And if packet loss does occur NewReno takes over again, so the bandwidth delay code will not interfere with NewReno (or whatever we do to deal with packet loss). :> Also, the algorithm is less helpful when it has to figure out the :> optimal transmit buffer size for every new connection (consider a web :> server). I am considering ripping out the ssthresh junk from the stack, :> which does not work virtually at all, and using the route table's :> ssthresh field to set the initial buffer size for the algorithm. : :This would probably be a big win, as in web-server type cases there are :many small connections back to back. : :Now, if you want a really radical idea, how about not doing slow-start :on the second-nth connection, but starting where the previous connection :left off. : :Whoa, that's loaded with issues. :-) : :-- :Leo Bicknell - bicknell@ufp.org re: slow-start. Actually I think this would work quite well in regards to setting the initial buffer size. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 11:20:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 8C11437B403 for ; Sun, 15 Jul 2001 11:20:14 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f6FIJvY71927; Sun, 15 Jul 2001 11:19:57 -0700 (PDT) (envelope-from obrien) Date: Sun, 15 Jul 2001 11:19:57 -0700 From: "David O'Brien" To: Jens Schweikhardt Cc: hackers@freebsd.org Subject: Re: Whitespace at end of line Message-ID: <20010715111956.A71874@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010715155941.C1165@schweikhardt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010715155941.C1165@schweikhardt.net>; from schweikh@schweikhardt.net on Sun, Jul 15, 2001 at 03:59:41PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 15, 2001 at 03:59:41PM +0200, Jens Schweikhardt wrote: > Dima and /me recently started weeding out white space at end of line for > the man pages. I want to widen the weeding to include as much files as > possible under /usr/src. Please do not do this to the .[ch] files. It makes diffs to stable harder. You may not know this, but in the early history of the "new" CVS tree (ie. /home/ncvs vs. /home/cvs) with the 4.4BSD Lite code someone did this (including pulling files off the vendor branch). In the end this has really irritated *many* a FreeBSD developer. Please leave such cleanup to when people are in the files cleaning up other style nits so we don't have 1 million commits, each taking care of just one point of style(9). And as you mentioned in your email, there are cases where you could change the semantics. If one is doing a few files at a time, they can catch the semantic changes. When doing it in-mass using a script, you will miss at least one. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 11:25:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.131]) by hub.freebsd.org (Postfix) with ESMTP id 3D59937B408; Sun, 15 Jul 2001 11:25:09 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA17078; Sun, 15 Jul 2001 20:25:06 +0200 (CEST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.4/8.11.4) id f6FIP5B03080; Sun, 15 Jul 2001 20:25:05 +0200 (CEST) (envelope-from wkb) Date: Sun, 15 Jul 2001 20:25:05 +0200 From: Wilko Bulte To: "David O'Brien" Cc: Jens Schweikhardt , hackers@FreeBSD.ORG Subject: Re: Whitespace at end of line Message-ID: <20010715202505.A94801@freebie.xs4all.nl> References: <20010715155941.C1165@schweikhardt.net> <20010715111956.A71874@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010715111956.A71874@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Sun, Jul 15, 2001 at 11:19:57AM -0700 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 15, 2001 at 11:19:57AM -0700, David O'Brien wrote: > On Sun, Jul 15, 2001 at 03:59:41PM +0200, Jens Schweikhardt wrote: > > Dima and /me recently started weeding out white space at end of line for > > the man pages. I want to widen the weeding to include as much files as > > possible under /usr/src. > > Please do not do this to the .[ch] files. It makes diffs to stable harder. > > You may not know this, but in the early history of the "new" CVS tree > (ie. /home/ncvs vs. /home/cvs) with the 4.4BSD Lite code someone did this > (including pulling files off the vendor branch). In the end this has > really irritated *many* a FreeBSD developer. Please leave such cleanup to > when people are in the files cleaning up other style nits so we don't > have 1 million commits, each taking care of just one point of style(9). > > And as you mentioned in your email, there are cases where you could > change the semantics. If one is doing a few files at a time, they can > catch the semantic changes. When doing it in-mass using a script, you > will miss at least one. Maybe I'm just plain dim today (I will add a beer to rectify this situation at first convenience..) but what is so bad about some trailing whitespace that a massive commit-a-thlon is called for? just wondering, Wilko -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte "Youth is not a time in life, it is a state of mind" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 12:30:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 71CE637B407 for ; Sun, 15 Jul 2001 12:30:25 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f6FJTme08965; Sun, 15 Jul 2001 12:29:48 -0700 (PDT) (envelope-from dillon) Date: Sun, 15 Jul 2001 12:29:48 -0700 (PDT) From: Matt Dillon Message-Id: <200107151929.f6FJTme08965@earth.backplane.com> To: Julian Elischer Cc: Leo Bicknell , Drew Eckhardt , hackers@FreeBSD.ORG Subject: Re: Network performance tuning. References: <200107130128.f6D1SFE59148@earth.backplane.com> <200107130217.f6D2HET67695@revolt.poohsticks.org> <20010712223042.A77503@ussenterprise.ufp.org> <200107131708.f6DH8ve65071@earth.backplane.com> <3B515097.6551A530@elischer.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Now, we add adjustable queue sizes.. and suddenly we are overflowing the :intermediate :queue, and dropping packets. Since we don't have SACK we are resending :lots of data and dropping back the window size at regular intervals. thus :it is possible that under some situations teh adjustable buffer size :may result in WORSE throughput. :That brings up one thing I never liked about the current TCP, :which is that we need to keep testing the upper window size to ensure that :we notice if the bandwidth increases. Unfortunatly the only way we can do this :is by :increasing the windowsize, until we lose a packet (again). : :There was an interesting paper that explored loss-avoidance techniques. :these included noticing teh increased latency that can occur when :an intermediate node starts to become overloaded. Unfortunatly, :usually we are not the person overloading it so us backing off :doesn't help a lot in many cases. I did some work at whistle :trying to predict and control remote congestion, but it was mostly useful :when the slowest link was your local loop and didn't help much if the :link was firther away. :Still, it did allow interactive sessions to run in prarllel with bulk :sessions and still get reasonable reaction times. basically I metered :out the ACKS going the other way (out) in order to minimise the :incoming queue size at the remote end of the incoming link. :-) : :This is all getting a bit far from the original topic, but :I do worry that we may increase our packet loss with variable buffers and thus :reduce throughout in the cases where teh fixed buffer was getting 80% :or so of the theoretical throughout. : :julian Well, it can't be worse then it is now... now it increases the window size until it hits the sendspace limit or hits packet loss. I tried both mechanisms... checking for the bandwidth to plateau while increasing the window size, which didn't work very well, and looking for the increased latency, which worked quite nicely. When decreasing the window size checking for the latency to bottom-out didn't work very well but checking for the bandwidth to start to drop did. The algorithm as posted is still not very stable - I had to use 5% hysteresis to get anything approaching a reasonable result, but it shouldn't go off into the weeds either (I hope). The method definitely work best when the constriction is near either end of the pipe, i.e. like your DSL line or T1 or modem, or the destination's DSL line or T1 or modem or whatever. When the constriction is in the middle of the network I completely agree with you... the algorithm breaks down. You can still figure it out statistically, but it takes far too long to remove the noise from the measurements. On the otherhand, if the routers were able to insert a feedback metric in the packet (e.g. like ttl but measuring something else), I think the middle-of-the-network problem could be solved. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 13:15:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by hub.freebsd.org (Postfix) with ESMTP id 4395837B406; Sun, 15 Jul 2001 13:15:08 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 1B0E417D2E; Sun, 15 Jul 2001 22:15:07 +0200 (CEST) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.11.4/8.11.3) id f6FKFRu02464; Sun, 15 Jul 2001 22:15:27 +0200 (CEST) (envelope-from schweikh) Date: Sun, 15 Jul 2001 22:15:27 +0200 From: Jens Schweikhardt To: "David O'Brien" Cc: hackers@freebsd.org Subject: Re: Whitespace at end of line Message-ID: <20010715221527.B1084@schweikhardt.net> References: <20010715155941.C1165@schweikhardt.net> <20010715111956.A71874@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010715111956.A71874@dragon.nuxi.com>; from obrien@freebsd.org on Sun, Jul 15, 2001 at 11:19:57AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David et al, On Sun, Jul 15, 2001 at 11:19:57AM -0700, David O'Brien wrote: # On Sun, Jul 15, 2001 at 03:59:41PM +0200, Jens Schweikhardt wrote: # > Dima and /me recently started weeding out white space at end of line for # > the man pages. I want to widen the weeding to include as much files as # > possible under /usr/src. # # Please do not do this to the .[ch] files. It makes diffs to stable harder. I see. Dima suggested in private email that I/we MFC such changes relatively fast in order to avoid that; of course this would be done only after md5 "approval" of the binaries. # You may not know this, but in the early history of the "new" CVS tree # (ie. /home/ncvs vs. /home/cvs) with the 4.4BSD Lite code someone did this # (including pulling files off the vendor branch). In the end this has # really irritated *many* a FreeBSD developer. Please leave such cleanup to # when people are in the files cleaning up other style nits so we don't # have 1 million commits, each taking care of just one point of style(9). OK, then I think it's best to tell developers@ about my script in freefall:~schweikh/bin/ws-at-eol which by default will only print the names of the files and optionally the line numbers/lines. Committers are encouraged to make use of it as they see fit. Folks, please remember to make separate commits for content changes and whitespace changes. $ ws-at-eol usage: ws-at-eol [options] directory ... Find whitespace at end-of-line in text files. Options: --help show this help text --remove remove whitespace at EOL using in-place editing --showlines print lines that have whitespace at EOL to stdout. EOL is marked by a $ sign, followed by a sequence of s and t characters for each space or tab. Examples: ws-at-eol /usr/src/share/man Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 13:52: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from anansi.vpha.health.ufl.edu (anansi.vpha.health.ufl.edu [159.178.78.153]) by hub.freebsd.org (Postfix) with ESMTP id A63AF37B407 for ; Sun, 15 Jul 2001 13:51:52 -0700 (PDT) (envelope-from sridharv@ufl.edu) Received: (from dymphna@localhost) by anansi.vpha.health.ufl.edu (8.9.3/8.9.3) id QAA14164; Sun, 15 Jul 2001 16:51:51 -0400 Date: Sun, 15 Jul 2001 16:51:51 -0400 From: sridharv@ufl.edu Message-Id: <200107152051.QAA14164@anansi.vpha.health.ufl.edu> X-Authentication-Warning: anansi.vpha.health.ufl.edu: dymphna set sender to sridharv@ufl.edu using -f To: freebsd-hackers@freebsd.org Reply-To: sridharv@ufl.edu MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP3 Imap webMail Program 2.0.10 X-Originating-IP: 128.227.205.209 Subject: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG am a kernel newbie. i tried adding code to the kernel and compiled it and installed . when i tried rebooting my new image the kernel panics with a fatal trap 12: page fault ( for which i know the reason). How do i boot the system now. how can i revert back to an earlier image? or how can i do it from a floppy? pl help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 13:55:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from anansi.vpha.health.ufl.edu (anansi.vpha.health.ufl.edu [159.178.78.153]) by hub.freebsd.org (Postfix) with ESMTP id DCBA137B403 for ; Sun, 15 Jul 2001 13:55:18 -0700 (PDT) (envelope-from sridharv@ufl.edu) Received: (from dymphna@localhost) by anansi.vpha.health.ufl.edu (8.9.3/8.9.3) id QAA14233; Sun, 15 Jul 2001 16:55:17 -0400 Date: Sun, 15 Jul 2001 16:55:17 -0400 From: sridharv@ufl.edu Message-Id: <200107152055.QAA14233@anansi.vpha.health.ufl.edu> X-Authentication-Warning: anansi.vpha.health.ufl.edu: dymphna set sender to sridharv@ufl.edu using -f To: freebsd-hackers@freebsd.org Reply-To: sridharv@ufl.edu MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP3 Imap webMail Program 2.0.10 X-Originating-IP: 128.227.205.209 Subject: help with booting Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG sorry for posting this mesg again- i forgot the subject.. :) am a kernel newbie. i tried adding code to the kernel and compiled it and installed . when i tried rebooting my new image the kernel panics with a fatal trap 12: page fault ( for which i know the reason). How do i boot the system now. how can i revert back to an earlier image? or how can i do it from a floppy? pl help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 14: 9:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from thought.adamantsys.com (w120.z064002057.sjc-ca.dsl.cnc.net [64.2.57.120]) by hub.freebsd.org (Postfix) with ESMTP id 0A88037B401 for ; Sun, 15 Jul 2001 14:09:35 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost.adamantsys.com [127.0.0.1]) by thought.adamantsys.com (8.11.4/8.11.2) with ESMTP id f6FL8Z901993; Sun, 15 Jul 2001 14:08:39 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Date: Sun, 15 Jul 2001 14:08:35 -0700 (PDT) From: "Brian W. Buchanan" X-X-Sender: To: Cc: Subject: Re: help with booting In-Reply-To: <200107152055.QAA14233@anansi.vpha.health.ufl.edu> Message-ID: <20010715140435.G93162-100000@thought.adamantsys.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG When you ran 'make install' after building your kernel, it renamed your old kernel to kernel.old. When the bootloader countdown starts, press the spacebar (or any key except ENTER) and you will get the bootloader prompt. Type "unload" and then "boot /kernel.old". In the future, plese direct questions like this to freebsd-questions@freebsd.org. Thanks. Brian -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org On Sun, 15 Jul 2001 sridharv@ufl.edu wrote: > sorry for posting this mesg again- i forgot the > subject.. :) > > am a kernel newbie. i tried adding code to the kernel > and compiled it and installed . when i tried rebooting > my new image the kernel panics with a fatal trap 12: > page fault ( for which i know the reason). How do i > boot the system now. how can i revert back to an > earlier image? or how can i do it from a floppy? > pl help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 16: 1:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from anansi.vpha.health.ufl.edu (anansi.vpha.health.ufl.edu [159.178.78.153]) by hub.freebsd.org (Postfix) with ESMTP id E5C5437B403 for ; Sun, 15 Jul 2001 16:01:28 -0700 (PDT) (envelope-from sridharv@ufl.edu) Received: (from dymphna@localhost) by anansi.vpha.health.ufl.edu (8.9.3/8.9.3) id TAA16828; Sun, 15 Jul 2001 19:01:18 -0400 Date: Sun, 15 Jul 2001 19:01:18 -0400 From: sridharv@ufl.edu Message-Id: <200107152301.TAA16828@anansi.vpha.health.ufl.edu> X-Authentication-Warning: anansi.vpha.health.ufl.edu: dymphna set sender to sridharv@ufl.edu using -f To: freebsd-hackers@freebsd.org Reply-To: sridharv@ufl.edu MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP3 Imap webMail Program 2.0.10 X-Originating-IP: 128.227.176.75 Subject: init Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG i need to TAILQ_INIT a queue at kernel startup .. how can i do it in my code? reg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 16:14:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id D525137B401 for ; Sun, 15 Jul 2001 16:14:33 -0700 (PDT) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.11.4/8.11.1) id f6FNEL994273; Sun, 15 Jul 2001 18:14:21 -0500 (CDT) Date: Sun, 15 Jul 2001 18:14:20 -0500 From: Tim To: Matt Dillon Cc: Leo Bicknell , Drew Eckhardt , hackers@FreeBSD.ORG Subject: Re: eXperimental bandwidth delay product code (was Re: Network performance tuning.) Message-ID: <20010715181420.A92412@futuresouth.com> References: <200107130128.f6D1SFE59148@earth.backplane.com> <200107130217.f6D2HET67695@revolt.poohsticks.org> <20010712223042.A77503@ussenterprise.ufp.org> <200107131708.f6DH8ve65071@earth.backplane.com> <20010713132903.A21847@ussenterprise.ufp.org> <200107131847.f6DIlJv67457@earth.backplane.com> <200107150943.f6F9hhx06763@earth.backplane.com> <20010715061915.A59691@futuresouth.com> <200107151657.f6FGv5308274@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107151657.f6FGv5308274@earth.backplane.com>; from dillon@earth.backplane.com on Sun, Jul 15, 2001 at 09:57:05AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ah, I didn't realize that it only affects the transmit end - so I am guessing it is similar to what ALTQ does? BTW, I didn't mean to imply that it was an idle link - I saturated the link with a download in the background while testing. I am also running an MTU of 576 already. Note that I could get the effect I want with Dummynet and introduce probability packet loss on traffic other than interactive traffic but it completely kill performance on everything else (not necessarily a bad thing). One of my colleagues use Dummynet and allocate 1kb/s to ssh and that seems to strive a somewhat better balance. He only turns it on when he's downloading something though - where I'd like to find a scenario where I can leave it on permanently. It would be nice for us lowly dial-up users to allow some sort of transfer on the background and still have a reasonable interactive performance - with reasonable total throughput to boot. Maybe it's easier to get that DSL connection (I would have already, if I don't hate our ILEC so much). Thanks, Tim On Sun, Jul 15, 2001 at 09:57:05AM -0700, Matt Dillon wrote: > > : > :Cool! We were just commenting that it's too bad dummynet/ALTQ really > :couldn't help the interactive response for us dial-up users. Anyway, I > :just tried this on my dial-up connection on a fresh -STABLE but don't > :really notice any appreciable difference. > : > :net.inet.tcp.tcp_send_dynamic_enable: 1 > :net.inet.tcp.tcp_send_dynamic_min: 1024 (tried it with default 4096 too) > : > :My ssh response is still about 3 or 4 seconds behind my typing. What > :should a dial-up user expect? > : > :Thanks! > : > :Tim > > Well, what this code does is manage the case where you are streaming > data in the transmit direction *and* trying to type at the same time > over another connection. It will not improve latency on an idle > connection that you are typing over. Even in the streaming case with > this algorithm the minimum window is two t_maxseg packets and that > will have a noticeable effect on latency over a dialup no matter what. > What this protocol is supposed to save you from, at least insofar as a > dialup goes, is that it should prevent an upload from killing terminal > performance entirely (e.g. it should prevent 10-20 second latency on > keystrokes). > > 3-4 seconds of latency over an idle dialup is really bad. I still > get sub-second responsiveness when I run ssh over a dialup. I always > use compression over dialups (ssh -C ...) and it makes a big > difference. > > This protocol also tends to devolve into a degenerate small-buffer > case (which is what it is supposed to do) when the connection is > running over a low bandwidth high latency link. It only takes a two > or three packet window to fill the link in such cases and the minimum > is two packets. > > You might be able to improve performance by negotiating a smaller MTU > (if this is a PPP connection), but no matter what you will never do > better then the normal typing performance on an idle link that > you already get. > > -Matt > > > 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 Jul 15 17:51:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 3069137B403 for ; Sun, 15 Jul 2001 17:51:42 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 010AF6ACC4; Mon, 16 Jul 2001 10:21:14 +0930 (CST) Date: Mon, 16 Jul 2001 10:21:13 +0930 From: Greg Lehey To: sridharv@ufl.edu Cc: freebsd-hackers@freebsd.org Subject: Failed hack attempt (was: your mail) Message-ID: <20010716102113.E24152@wantadilla.lemis.com> References: <200107152051.QAA14164@anansi.vpha.health.ufl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107152051.QAA14164@anansi.vpha.health.ufl.edu>; from sridharv@ufl.edu on Sun, Jul 15, 2001 at 04:51:51PM -0400 Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, 15 July 2001 at 16:51:51 -0400, sridharv@ufl.edu wrote: > am a kernel newbie. i tried adding code to the kernel > and compiled it and installed . when i tried rebooting > my new image the kernel panics with a fatal trap 12: > page fault ( for which i know the reason). How do i > boot the system now. how can i revert back to an > earlier image? or how can i do it from a floppy? As a kernel newbie, you should get used to this kind of problem. Plan ahead. If you *do* run into trouble, and you want help, you need to give more information. Basically, though, you need to use kernel.old, which is either a file in / or a directory in /boot. You should also apply the same rules described in http://echunga.lemis.com/questions.html, including a descriptive subject. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 18: 8:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id 4959237B403 for ; Sun, 15 Jul 2001 18:08:05 -0700 (PDT) (envelope-from dphoenix@bravenet.com) Received: (qmail 29204 invoked by uid 1001); 16 Jul 2001 01:13:37 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 16 Jul 2001 01:13:37 -0000 Date: Sun, 15 Jul 2001 18:13:37 -0700 (PDT) From: Dan To: Subject: pagedaemon + vmdaemon Message-ID: <20010715181123.A29164-100000@gandalf.bravenet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 2 14.2 0.0 0 0 ?? DL Tue11AM 4:35.33 (pagedaemon) root 3 12.7 0.0 0 0 ?? DL Tue11AM 1:56.25 (vmdaemon) Cpu kept hitting high load averages on machines for about 1 min periods on some machines on some apache servers. I wrote a script to catch the offending processes and it seems to be these ones. Ideas on why they would be taking that much cpu? -- Dan +------------------------------------------------------+ | BRAVENET WEB SERVICES | | dan@bravenet.com | | screen;cd /usr/src;make buildworld;cd ~ | | cp MYKERNEL /sys/i386/conf;cd /usr/src | | make buildkernel KERNCONF=MYKERNEL | |make installkernel KERNCONF=MYKERNEL;make installworld| +______________________________________________________+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 18:49:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 8455637B403 for ; Sun, 15 Jul 2001 18:49:21 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 966 invoked by uid 1000); 16 Jul 2001 01:49:19 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 16 Jul 2001 01:49:19 -0000 Date: Sun, 15 Jul 2001 20:49:19 -0500 (CDT) From: Mike Silbersack To: Bill Paul Cc: Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 In-Reply-To: <20010713180434.7D25937B401@hub.freebsd.org> Message-ID: <20010715204819.N769-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 13 Jul 2001, Bill Paul wrote: > For those who have gigabit ethernet NICs based on the National > Semiconductor DP83820 and DP83821 controller chips and want to use > them with FreeBSD 4.2 and 4.3, there is a driver kit now available > at the following URL: ... > These cards are all extremely cheap (some can be had for under $100) > and fairly easy to find. (I now have one in my workstation.) They could > potentially become extremely popular, which is why I'm making a driver > retrofit kit available. Anyone running a recent 4-STABLE or 5.0-CURRENT > system should already have the necessary driver support. How do these perform compared to the more expensive gigabit cards? Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 19: 1:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id A3A4D37B401 for ; Sun, 15 Jul 2001 19:01:18 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 1010 invoked by uid 1000); 16 Jul 2001 02:01:13 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 16 Jul 2001 02:01:13 -0000 Date: Sun, 15 Jul 2001 21:01:13 -0500 (CDT) From: Mike Silbersack To: Jens Schweikhardt Cc: David O'Brien , Subject: Re: Whitespace at end of line In-Reply-To: <20010715221527.B1084@schweikhardt.net> Message-ID: <20010715205955.U769-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 15 Jul 2001, Jens Schweikhardt wrote: > David et al, > > On Sun, Jul 15, 2001 at 11:19:57AM -0700, David O'Brien wrote: > # On Sun, Jul 15, 2001 at 03:59:41PM +0200, Jens Schweikhardt wrote: > # > Dima and /me recently started weeding out white space at end of line for > # > the man pages. I want to widen the weeding to include as much files as > # > possible under /usr/src. > # > # Please do not do this to the .[ch] files. It makes diffs to stable harder. > > I see. Dima suggested in private email that I/we MFC such changes > relatively fast in order to avoid that; of course this would be done > only after md5 "approval" of the binaries. Whether you MFC it or not, you're going to cause a lot of commit log pollution. I don't think it's worth the hassle when all we're talking about is trailing whitespace. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 21:33: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp-1.enteract.com (smtp-1.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 238D537B401 for ; Sun, 15 Jul 2001 21:33:01 -0700 (PDT) (envelope-from dscheidt@tumbolia.com) Received: from shell-3.enteract.com (shell-3.enteract.com [207.229.143.42]) by smtp-1.enteract.com (Postfix) with ESMTP id B37D5427CE; Sun, 15 Jul 2001 23:32:59 -0500 (CDT) Date: Sun, 15 Jul 2001 23:32:59 -0500 (CDT) From: David Scheidt X-X-Sender: To: Mike Silbersack Cc: Jens Schweikhardt , Subject: Re: Whitespace at end of line In-Reply-To: <20010715205955.U769-100000@achilles.silby.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 15 Jul 2001, Mike Silbersack wrote: : :On Sun, 15 Jul 2001, Jens Schweikhardt wrote: :> I see. Dima suggested in private email that I/we MFC such changes :> relatively fast in order to avoid that; of course this would be done :> only after md5 "approval" of the binaries. : :Whether you MFC it or not, you're going to cause a lot of commit log :pollution. I don't think it's worth the hassle when all we're talking :about is trailing whitespace. : Not only commitlog pollution, but also repository file growth, and wasted bandwidth from those cvsuping the changes. My cvsup of the repository took ~4 times as long when the changes were made to the man pages. You said it would save ~250K in the source tree. What's it do to the size of the whole repository? -- dscheidt@tumbolia.com Bipedalism is only a fad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 21:33:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp-out.hamburg.pop.de (smtp-out.hamburg.pop.de [195.222.210.86]) by hub.freebsd.org (Postfix) with ESMTP id DF0DB37B403 for ; Sun, 15 Jul 2001 21:33:29 -0700 (PDT) (envelope-from ) Received: from mail.hamburg.pop.de ([193.98.9.7] helo=mail.provi.de) by smtp-out.hamburg.pop.de with esmtp (Exim 3.22 #1) id 15M05J-0008OE-00 for hackers@freebsd.org; Mon, 16 Jul 2001 06:34:17 +0200 Received: from daemon by mail.provi.de with local (Exim 3.20 #2) id 15M04W-0005w1-00 for hackers@FreeBSD.ORG; Mon, 16 Jul 2001 06:33:28 +0200 From: To: Subject: mail failed, returning to sender X-No-Resend: True Message-Id: Date: Mon, 16 Jul 2001 06:33:28 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG |------------------------- Message log follows: -----------------------| | no valid recipients were found for this message | |----------------------------------------------------------------------| | t.schmeissel@mail.hh.provi.de - unknown user |----------------------------------------------------------------------| German translation: Sie haben Ihre eMail an die Adresse "t.schmeissel@mail.hh.provi.de" gerichtet. Der hintere Teil der Adresse ("Domain"), "@mail.hh.provi.de", ist gueltig, der Benutzernamen jedoch nicht. Ueberpruefen Sie bitte insbesondere diesen Teil der eMail-Adresse! Sie erhalten im Anhang die ersten zehn Zeilen Ihrer Original-eMail zurueck. Mit freundlichen Gruessen, Point of Presence GmbH, Hamburg ------------------------------------------------------------------------ From owner-freebsd-hackers-digest@freebsd.org Mon Jul 16 06:33:28 2001 Return-path: Envelope-to: t.schmeissel@mail.hh.provi.de Delivery-date: Mon, 16 Jul 2001 06:33:28 +0200 Received: from mx2.freebsd.org ([216.136.204.119]) by mail.provi.de with smtp (Exim 3.20 #2) id 15M04U-0005vr-00 for t.schmeissel@mail.hh.provi.de; Mon, 16 Jul 2001 06:33:26 +0200 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id BA5D855E36; Sun, 15 Jul 2001 21:33:08 -0700 (PDT) (envelope-from owner-freebsd-hackers-digest@FreeBSD.ORG) Received: by hub.freebsd.org (Postfix, from userid 538) id 71CFE37B405; Sun, 15 Jul 2001 21:33:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with SMTP id 574202E8036; Sun, 15 Jul 2001 21:33:08 -0700 (PDT) (envelope-from owner-freebsd-hackers-digest) Received: by hub.freebsd.org (bulk_mailer v1.12); Sun, 15 Jul 2001 21:33:08 -0700 From: owner-freebsd-hackers-digest@FreeBSD.ORG (freebsd-hackers-digest) To: freebsd-hackers-digest@FreeBSD.ORG Subject: freebsd-hackers-digest V5 #181 Reply-To: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers-digest@FreeBSD.ORG Precedence: bulk Message-ID: Date: Sun, 15 Jul 2001 21:33:08 -0700 (PDT) freebsd-hackers-digest Sunday, July 15 2001 Volume 05 : Number 181 In this issue: mail failed, returning to sender Re: mail failed, returning to sender Re: math library difference between linux emulation and native freebsd (and native linux) Re: math library difference between linux emulation and native freebsd (and native linux) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 22:25:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 0403137B401; Sun, 15 Jul 2001 22:25:22 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f6G5N5V136202; Mon, 16 Jul 2001 01:23:05 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20010715221527.B1084@schweikhardt.net> References: <20010715155941.C1165@schweikhardt.net> <20010715111956.A71874@dragon.nuxi.com> <20010715221527.B1084@schweikhardt.net> Date: Mon, 16 Jul 2001 01:23:03 -0400 To: Jens Schweikhardt , "David O'Brien" From: Garance A Drosihn Subject: Re: Whitespace at end of line Cc: hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 10:15 PM +0200 7/15/01, Jens Schweikhardt wrote: >David et al, > >On Sun, Jul 15, 2001 at 11:19:57AM -0700, David O'Brien wrote: ># ># Please do not do this to the .[ch] files. It makes diffs to stable ># harder. > >I see. Dima suggested in private email that I/we MFC such changes >relatively fast in order to avoid that; of course this would be done >only after md5 "approval" of the binaries. Also note that your reason for changing this is the disk space consumed by the extra blanks. You're going to be combatting that by using up disk space for patches (at least as far as my systems are concerned, because I cvsup the CVS tree and not any specific release). ># Please leave such cleanup to ># when people are in the files cleaning up other style nits so we don't ># have 1 million commits, each taking care of just one point of style(9). > >OK, then I think it's best to tell developers@ about my script in >freefall:~schweikh/bin/ws-at-eol which by default will only print the >names of the files and optionally the line numbers/lines. Committers are >encouraged to make use of it as they see fit. Folks, please remember to >make separate commits for content changes and whitespace changes. I am not in favor of a generic sweep to remove blank space, but the script will be useful to use when working on some source for other reasons. Thanks. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 15 23:19: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id 5D5EE37B40A for ; Sun, 15 Jul 2001 23:18:56 -0700 (PDT) (envelope-from vel@bugz.infotecs.ru) Received: (from root@localhost) by bugz.infotecs.ru (8.11.1/8.11.1) id f6G6XVl21904 for freebsd-hackers@freebsd.org; Mon, 16 Jul 2001 10:33:31 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200107160633.f6G6XVl21904@bugz.infotecs.ru> Subject: Re: DDB & mp3's In-Reply-To: <3B4F3FA9.DE60DFDA@mindspring.com> "from Terry Lambert at Jul 13, 2001 11:36:25 am" To: freebsd-hackers@freebsd.org Date: Mon, 16 Jul 2001 10:33:31 +0400 (MSD) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > diman wrote: > > > > Hi, folks. > > When I switch to DDB to check something or debug something > > usefull, mp3 player process (mpg123) hangs up and dissonate > > me. So guys how do you do in such a case? I'm shure that > > I'm not one having such a problem. ;-) > > > > Maybe someone has allready ported mp3's player to kernel, > > or even built it in DDB? > > > > What would be your suggestion? > > You are kidding, right? You do actually know how DDB works? I think you can overcome this by running FreeBSD you're debugging on vmware virtual machine (that is, just FreeBSD on FreeBSD under vmware). Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 7:27: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id BFFF037B401 for ; Mon, 16 Jul 2001 07:26:58 -0700 (PDT) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id QAA48911; Mon, 16 Jul 2001 16:20:41 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200107161420.QAA48911@info.iet.unipi.it> Subject: Re: eXperimental bandwidth delay product code (was Re: Network performance tuning.) In-Reply-To: <20010715061915.A59691@futuresouth.com> from Tim at "Jul 15, 2001 06:19:15 am" To: Tim Date: Mon, 16 Jul 2001 16:20:40 +0200 (CEST) Cc: Matt Dillon , Leo Bicknell , Drew Eckhardt , hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Cool! We were just commenting that it's too bad dummynet/ALTQ really > couldn't help the interactive response for us dial-up users. Anyway, I i haven't seen the beginning of the thread but surely both altq and dummynet can help, with the CBQ/WFQ support. In the case of dummynet, you can pace incoming traffic as well, at your endpoint. This means you act after the bottleneck, but the effect is that this way you will delay acks, and so slow down the connection eating a lot of bandwidth, and in the steady state this keeps the queue very short even before the bottleneck. Much like what products like packeteer do. cheers luigi > just tried this on my dial-up connection on a fresh -STABLE but don't > really notice any appreciable difference. > > net.inet.tcp.tcp_send_dynamic_enable: 1 > net.inet.tcp.tcp_send_dynamic_min: 1024 (tried it with default 4096 too) > > My ssh response is still about 3 or 4 seconds behind my typing. What > should a dial-up user expect? > > Thanks! > > Tim > > 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 Jul 16 7:36:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 813FE37B40E for ; Mon, 16 Jul 2001 07:36:08 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f6GEZr618012; Mon, 16 Jul 2001 07:35:53 -0700 (PDT) (envelope-from obrien) Date: Mon, 16 Jul 2001 07:35:53 -0700 From: "David O'Brien" To: David Scheidt Cc: hackers@freebsd.org Subject: Re: Whitespace at end of line Message-ID: <20010716073552.A17926@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010715205955.U769-100000@achilles.silby.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dscheidt@tumbolia.com on Sun, Jul 15, 2001 at 11:32:59PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 15, 2001 at 11:32:59PM -0500, David Scheidt wrote: > ..., and wasted bandwidth from those cvsuping the changes. > My cvsup of the repository took > ~4 times as long when the changes were made to the man pages. *sigh* Are we now a hostage to CVSup times? Put it in cron and do it at 3am when you don't really care how long it takes. You would not have survived the `sup' days if you think CVSup takes a long time. I can only laugh at the "wasted bandwidth" comment. Any idea how much BW was being taken up by Napster related traffic until a month ago?? CVSup, with its low BW design of only sending diffs, pales in comparison. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 7:42:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 516F837B405 for ; Mon, 16 Jul 2001 07:42:23 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA11019; Mon, 16 Jul 2001 10:41:56 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id KAA07952; Mon, 16 Jul 2001 10:41:56 -0400 (EDT) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA07948; Mon, 16 Jul 2001 10:41:56 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Mon, 16 Jul 2001 10:41:55 -0400 (EDT) From: Kenneth Wayne Culver To: Luigi Rizzo Cc: Tim , Matt Dillon , Leo Bicknell , Drew Eckhardt , hackers@FreeBSD.ORG Subject: Re: eXperimental bandwidth delay product code (was Re: Network performance tuning.) In-Reply-To: <200107161420.QAA48911@info.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have been testing this over a very slow (barely ever over 24000 bps due to a crappy phone line) dial-up link, and as expected, over an idle line there is no difference (typing in an interactive ssh session seems a little quicker, but that could just be me). The gain comes when someone is downloading over the link and I try to type in an interactive ssh session. (I'm sharing the link with 1 other computer). Without the sysctl turned on typing in the "interactive" session results in a 10-15 second wait before anything appears on the screen; but with the sysctl turned on the wait is 2-3 seconds. I'd say that's pretty good work :-) Ken On Mon, 16 Jul 2001, Luigi Rizzo wrote: > > Cool! We were just commenting that it's too bad dummynet/ALTQ really > > couldn't help the interactive response for us dial-up users. Anyway, I > > i haven't seen the beginning of the thread but surely both altq > and dummynet can help, with the CBQ/WFQ support. > > In the case of dummynet, you can pace incoming traffic as well, > at your endpoint. This means you act after the bottleneck, > but the effect is that this way > you will delay acks, and so slow down the connection eating a lot of > bandwidth, and in the steady state this keeps the queue very > short even before the bottleneck. > Much like what products like packeteer do. > > cheers > luigi > > > just tried this on my dial-up connection on a fresh -STABLE but don't > > really notice any appreciable difference. > > > > net.inet.tcp.tcp_send_dynamic_enable: 1 > > net.inet.tcp.tcp_send_dynamic_min: 1024 (tried it with default 4096 too) > > > > My ssh response is still about 3 or 4 seconds behind my typing. What > > should a dial-up user expect? > > > > Thanks! > > > > Tim > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 8:35:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id 255B937B401 for ; Mon, 16 Jul 2001 08:35:22 -0700 (PDT) (envelope-from freebsd@tarakan-network.com) Received: from chojin (chojin [192.168.69.2]) by tarakan-network.com (8.11.4/8.11.3) with SMTP id f6GFZE826565 for ; Mon, 16 Jul 2001 17:35:14 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <007001c10e0c$f02d94c0$0245a8c0@chojin> From: "Chojin" To: Subject: Cron program core dumped (signal 11) Date: Mon, 16 Jul 2001 17:35:27 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_006D_01C10E1D.B3840A20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG C'est un message de format MIME en plusieurs parties. ------=_NextPart_000_006D_01C10E1D.B3840A20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I update & recompiled my system and my kernel. After reboot, I see cron program doesn't work it exits on a signal 11 (core dumped). MD5 (/usr/sbin/cron) =3D e56aa049cf7216f3c3f8e2ada7e9b4f3 Someone could help me ? Regards, Chojin ------=_NextPart_000_006D_01C10E1D.B3840A20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
 
I update & recompiled my system and my=20 kernel.
After reboot, I see cron program doesn't = work
it exits on a signal 11 (core dumped).
 
MD5 (/usr/sbin/cron) =3D=20 e56aa049cf7216f3c3f8e2ada7e9b4f3
 
Someone could help me ?
 
Regards,
 
Chojin
------=_NextPart_000_006D_01C10E1D.B3840A20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 8:42:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail8.sdc1.sfba.home.com (femail8.sdc1.sfba.home.com [24.0.95.88]) by hub.freebsd.org (Postfix) with ESMTP id 06B8537B405 for ; Mon, 16 Jul 2001 08:42:20 -0700 (PDT) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.159]) by femail8.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010716154217.KRFF7782.femail8.sdc1.sfba.home.com@home.com> for ; Mon, 16 Jul 2001 08:42:17 -0700 Message-ID: <3B530A66.26902DD4@home.com> Date: Mon, 16 Jul 2001 11:38:14 -0400 From: Ted Sikora X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.5 i686) X-Accept-Language: en-US, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: wu-ftpd Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anyone know how to set simultaneous downloads for users to 2 in /etc/ftpaccess for wu-ftpd? -- Ted Sikora admin@unixos2.org http://www.unixos2.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 8:48: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id 4688F37B406 for ; Mon, 16 Jul 2001 08:48:07 -0700 (PDT) (envelope-from mark@whistle.com) Received: from [10.1.10.118] (PBG4.whistle.com [207.76.207.129]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id IAA82475; Mon, 16 Jul 2001 08:47:10 -0700 (PDT) Mime-Version: 1.0 X-Sender: mark-ml@207.76.206.1 Message-Id: In-Reply-To: <007001c10e0c$f02d94c0$0245a8c0@chojin> References: <007001c10e0c$f02d94c0$0245a8c0@chojin> Date: Mon, 16 Jul 2001 08:47:23 -0700 To: "Chojin" , From: Mark Peek Subject: Re: Cron program core dumped (signal 11) Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 5:35 PM +0200 7/16/01, Chojin wrote: >I update & recompiled my system and my kernel. >After reboot, I see cron program doesn't work >it exits on a signal 11 (core dumped). > >MD5 (/usr/sbin/cron) = e56aa049cf7216f3c3f8e2ada7e9b4f3 > >Someone could help me ? You have a malformed cron entry which is missing the username field. If you correct it, cron will not core dump. We are testing a patch to prevent the core dump which should be committed soon. Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 8:49:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.39]) by hub.freebsd.org (Postfix) with SMTP id 856C537B403 for ; Mon, 16 Jul 2001 08:49:07 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 58002 invoked by uid 1000); 16 Jul 2001 15:53:18 -0000 Date: Mon, 16 Jul 2001 18:53:18 +0300 From: Peter Pentchev To: Chojin Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Cron program core dumped (signal 11) Message-ID: <20010716185318.E56285@ringworld.oblivion.bg> References: <007001c10e0c$f02d94c0$0245a8c0@chojin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <007001c10e0c$f02d94c0$0245a8c0@chojin>; from freebsd@tarakan-network.com on Mon, Jul 16, 2001 at 05:35:27PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [redirected to -stable, where this most probably belongs..] On Mon, Jul 16, 2001 at 05:35:27PM +0200, Chojin wrote: > Hello, > > I update & recompiled my system and my kernel. > After reboot, I see cron program doesn't work > it exits on a signal 11 (core dumped). > > MD5 (/usr/sbin/cron) = e56aa049cf7216f3c3f8e2ada7e9b4f3 > > Someone could help me ? Does cron also segfault if you run it from the command line as root (by just typing cron at the command prompt)? If it does, can you try the following series of commands.. cd /usr/src/usr.sbin/cron make cleandir depend make CFLAGS="-ggdb -g3" STRIP="" all install ..then run '/usr/sbin/cron' from the command line, and see if it leaves a coredump in the current directory. If it does, then do the following: gdb /usr/sbin/cron /path/to/cron.core (at the gdb prompt) bt info local up info local up info local [repeat until highest level] Hm. Now that I kinda tested this, cron doesn't seem to leave a corefile. Well, still.. this message was redirected to -stable in the hope that somebody there would know better how to help :\ G'luck, Peter -- This sentence claims to be an Epimenides paradox, but it is lying. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 8:52:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 4496337B403 for ; Mon, 16 Jul 2001 08:52:19 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.130.87.Dial1.SanJose1.Level3.net [209.245.130.87]) by scaup.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id IAA04892; Mon, 16 Jul 2001 08:52:17 -0700 (PDT) Message-ID: <3B530DD6.E3604F32@mindspring.com> Date: Mon, 16 Jul 2001 08:52:54 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jim.Pirzyk@disney.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: math library difference between linux emulation and native freebsd (and native linux) References: <200107141809.f6EI9M809946@snoopy.fan.fa.disney.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jim.Pirzyk@disney.com wrote: > > So I have stumbled across a linux emulation bug in freebsd. Below > is the program that returns different results based on FreeBSD, > Linux or Linux emulation under FreeBSD. [ ... ] > There are only two shared libaries in common (libc and libm) and > both are the same on FreeBSD (in /compat/linux) and Linux. > > So any ideas on where the program is going wrong? man fpsetround The defaults for the Linux emulator are different than the defaults for Linux. Linux sets some stuff up wrong, and then assumes that it's set up wrong. If you want to get exactly the same answers as for Linux, you will need to set the hardware up the same. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 9: 0:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id 06AE937B40F for ; Mon, 16 Jul 2001 09:00:04 -0700 (PDT) (envelope-from freebsd@tarakan-network.com) Received: from chojin (chojin [192.168.69.2]) by tarakan-network.com (8.11.4/8.11.3) with SMTP id f6GFxo827016; Mon, 16 Jul 2001 17:59:50 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <002101c10e10$5edea640$0245a8c0@chojin> From: "Chojin" To: "Peter Pentchev" Cc: References: <007001c10e0c$f02d94c0$0245a8c0@chojin> <20010716185318.E56285@ringworld.oblivion.bg> Subject: Re: Cron program core dumped (signal 11) Date: Mon, 16 Jul 2001 18:00:01 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > cd /usr/src/usr.sbin/cron > make cleandir depend > make CFLAGS="-ggdb -g3" STRIP="" all install > > ..then run '/usr/sbin/cron' from the command line, and see if it > leaves a coredump in the current directory. If it does, then > do the following: > > gdb /usr/sbin/cron /path/to/cron.core > (at the gdb prompt) > bt > info local > up > info local > up > info local > [repeat until highest level] > > Hm. Now that I kinda tested this, cron doesn't seem to leave > a corefile. Well, still.. this message was redirected to -stable > in the hope that somebody there would know better how to help :\ > > G'luck, > Peter > > -- > This sentence claims to be an Epimenides paradox, but it is lying. > Okay, I followed your instructions: GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... Core was generated by `cron'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libutil.so.3...done. Reading symbols from /usr/lib/libc.so.4...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x804e59b in env_free (envp=0x0) at env.c:44 44 for (p = envp; *p; p++) (gdb) bt #0 0x804e59b in env_free (envp=0x0) at env.c:44 #1 0x804c166 in free_entry (e=0x805a8c0) at entry.c:77 #2 0x804de44 in load_entry (file=0x2810ab98, error_func=0x804b8dc , pw=0x280fd780, envp=0x80576d0) at entry.c:423 #3 0x804badf in load_user (crontab_fd=6, pw=0x280fd780, name=0xbfbff9d4 "rico") at user.c:105 #4 0x804ab37 in process_crontab (uname=0xbfbff9d4 "rico", fname=0xbfbff9d4 "rico", tabname=0xbfbff8d4 "tabs/rico", statbuf=0xbfbffb4c, new_db=0xbfbffadc, old_db=0xbfbffbd4) at database.c:252 #5 0x804a76c in load_database (old_db=0xbfbffbd4) at database.c:120 #6 0x8049b92 in main (argc=1, argv=0xbfbffc34) at cron.c:116 #7 0x8049941 in _start () (gdb) info local p = (char **) 0x0 (gdb) up #1 0x804c166 in free_entry (e=0x805a8c0) at entry.c:77 77 env_free(e->envp); (gdb) info local No locals. (gdb) up #2 0x804de44 in load_entry (file=0x2810ab98, error_func=0x804b8dc , pw=0x280fd780, envp=0x80576d0) at entry.c:423 423 free_entry(e); (gdb) info local ecode = e_username e = (entry *) 0x805a8c0 ch = 47 cmd = "/hom0,20,40\00003/articuno/Articuno.botchk >/dev/null 2>&1\000file", '\000' , "TÜ\a(\000r\006(", '\000' , "4Ý\a(\000r\006(", '\000' , "´Ý\a(\000r\006(", '\000' , "Tß\a(\000r\006(\000\000\000\000\000\000\000\000tß\a(\000r\006(", '\000' , "éY\005(\237\214\004\b¬ÿ\a(\000\000\000\000\216Y\005(h6\006(@\200\006(", '\000' , "@\200\006\001"... envstr = "\001\000\000\000\000daryn003\00003\000n\000\000/usr/bin:/usr/sbin", '\000' , "ÄÕ\a(\000r\006(", '\000' , "´Ö\a(\000r\006(", '\000' , "äÖ\a(\000r\006(", '\000' , "´×\a(\000r\006(Ä×\a(\000r\006(\000\000\000\000\000\000\000\000ä×\a(\000r\00 6(", '\000' , "\224Ù\a(\000r\006(", '\000' , "´Ú\a(\000r\006(\000\000\000\000\000\000\000\000ÔÚ\a(\000r\006(", '\000' , "<78>"... prev_env = (char **) 0x8053860 (gdb) up #3 0x804badf in load_user (crontab_fd=6, pw=0x280fd780, name=0xbfbff9d4 "rico") at user.c:105 105 e = load_entry(file, log_error, pw, envp); (gdb) info local envstr = "0,20,40 * * * * /home/rico/poulet/scripts/botchk\000Articuno.botchk >/dev/null 2>&1\000\200\006(", '\000' , "@\200\006\001,õ¿¿;Y\005(\227\026\b(ü\234°\006\000r\006(îX\005(h6\006(Ä\215\ a(\000\000\000\000éY\005(\227\026\b(\217*\005(\000\000\000\000\216Y\005(h6\0 06(\000\000\000\000\2009\006(éY\005(n\t\b(n\t\b(\004\000\000\000\004\000\000 \000 \207\016(Ùø¿¿Ôù¿¿\004\000"... file = (FILE *) 0x2810ab98 u = (user *) 0x80538a0 e = (entry *) 0x805a840 status = 0 envp = (char **) 0x80576d0 tenvp = (char **) 0x8057060 (gdb) up #4 0x804ab37 in process_crontab (uname=0xbfbff9d4 "rico", fname=0xbfbff9d4 "rico", tabname=0xbfbff8d4 "tabs/rico", statbuf=0xbfbffb4c, new_db=0xbfbffadc, old_db=0xbfbffbd4) at database.c:252 252 u = load_user(crontab_fd, pw, fname); (gdb) info local pw = (struct passwd *) 0x280fd780 crontab_fd = 6 u = (user *) 0x0 (gdb) up #5 0x804a76c in load_database (old_db=0xbfbffbd4) at database.c:120 120 process_crontab(fname, fname, tabname, (gdb) info local fname = "rico", '\000' tabname = "tabs/rico\000003\000\000(àþ\a(\000\000\000\001\216Y\005(h6\006(@\200\006(\0 00\000\000\000\210%\006(Lù¿¿@\200\006\001Hù¿¿;Y\005(éY\005(\b\214\004\bT1\b( \001\000\000\000\216Y\005(h6\006(@\200\006(\000\000\000\000h6\006(@\200\006\ 001@\200\006\001|ù¿¿;Y\005(JÞ\016(Ç\000\000\000\000\000\000\000\003", '\000' , "$Þ\016(è\214\017(\000r\006(\000p\006(\000r\006(\000r\006\001ìù¿¿°ù¿¿\220×\0 16(\003", '\000' , "è\214\017(\000\000\000\000\000\000\000\000E\216\004\b\"ô"... dir = (DIR *) 0x8053200 statbuf = {st_dev = 160772, st_ino = 63030, st_mode = 33152, st_nlink = 1, st_uid = 0, st_gid = 0, st_rdev = 263485, st_atimespec = {tv_sec = 995296924, tv_nsec = 0}, st_mtimespec = {tv_sec = 992364997, tv_nsec = 0}, st_ctimespec = { tv_sec = 992364997, tv_nsec = 0}, st_size = 333, st_blocks = 2, st_blksize = 8192, st_flags = 0, st_gen = 1442709759, st_lspare = 0, st_qspare = {0, 0}} syscron_stat = {st_dev = 160768, st_ino = 70865, st_mode = 33188, st_nlink = 1, st_uid = 0, st_gid = 0, st_rdev = 295944, st_atimespec = {tv_sec = 995296924, tv_nsec = 0}, st_mtimespec = {tv_sec = 986929430, tv_nsec = 0}, st_ctimespec = { tv_sec = 988309741, tv_nsec = 0}, st_size = 637, st_blocks = 2, st_blksize = 8192, st_flags = 0, st_gen = 732393885, st_lspare = 0, st_qspare = {0, 0}} dp = (struct dirent *) 0x8058078 new_db = {head = 0x8053060, tail = 0x8053800, mtime = 995279104} u = (user *) 0x28067200 nu = (user *) 0x1 (gdb) up #6 0x8049b92 in main (argc=1, argv=0xbfbffc34) at cron.c:116 116 load_database(&database); (gdb) info local database = {head = 0x0, tail = 0x0, mtime = 0} (gdb) up #7 0x8049941 in _start () (gdb) info local No symbol table info available. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 9: 0:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from enterprise.spock.org (cm-24-29-85-81.nycap.rr.com [24.29.85.81]) by hub.freebsd.org (Postfix) with ESMTP id 582FC37B409 for ; Mon, 16 Jul 2001 09:00:32 -0700 (PDT) (envelope-from jon@enterprise.spock.org) Received: (from jon@localhost) by enterprise.spock.org serial EF600Q3T-B7F8823f6GG0Nj95068F7T for freebsd-hackers@freebsd.org; Mon, 16 Jul 2001 12:00:23 -0400 (EDT) (envelope-from jon)$ Date: Mon, 16 Jul 2001 12:00:23 -0400 From: Jonathan Chen To: freebsd-hackers@freebsd.org Subject: NEWCARD updates Message-ID: <20010716120023.A92982@enterprise.spock.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: telnet/1.1x Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG For a while now I've been playing with NEWCARD, and I ended up making a lot of changes. I would appreciate any comments on them. Since there are a number of large changes, I'm not going to commit right away. You can find the diffs at http://people.freebsd.org/~jon/newcard.diff (.gz version also available if you don't feel like downloading 140k) This should apply cleanly on any -CURRENT this month. (if yours is older, the fix is trivial) You may also need to apply http://people.freebsd.org/~jon/pci_enable_io.diff if your -CURRENT is before June 10. Briefly, the significant changes include: * Way better resource management in pccbb, pccard and cardbus. * pccard hot-removal now appears to work. * support pre-fetchable memory in cardbus. * update cardbus to support new pci bus interface functions. * FINALLY fix cardbus CIS reading, it should no longer freeze your machine. (I seem to recall fixing this before, but oh well...) * variable renames in pccbb cause I was getting confused which was which. What's not there: * style(9) complience in portions of code (will fix those separately) * a simpler version of the cis reading interface * a complete implementation of CIS tuple parsing Again, I would appreciate any testing and/or comments on this. BTW, does anyone have a copy of the pccard specs, or know of some other resource for a complete description of cis tuples? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 9:36: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.39]) by hub.freebsd.org (Postfix) with SMTP id 2B7E337B405 for ; Mon, 16 Jul 2001 09:35:51 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 58637 invoked by uid 1000); 16 Jul 2001 16:39:56 -0000 Date: Mon, 16 Jul 2001 19:39:56 +0300 From: Peter Pentchev To: Chojin Cc: freebsd-hackers@FreeBSD.org Subject: Re: Cron program core dumped (signal 11) Message-ID: <20010716193956.H56285@ringworld.oblivion.bg> Mail-Followup-To: Chojin , freebsd-hackers@FreeBSD.org References: <007001c10e0c$f02d94c0$0245a8c0@chojin> <20010716185318.E56285@ringworld.oblivion.bg> <002101c10e10$5edea640$0245a8c0@chojin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002101c10e10$5edea640$0245a8c0@chojin>; from freebsd@tarakan-network.com on Mon, Jul 16, 2001 at 06:00:01PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 16, 2001 at 06:00:01PM +0200, Chojin wrote: > > cd /usr/src/usr.sbin/cron > > make cleandir depend > > make CFLAGS="-ggdb -g3" STRIP="" all install > > > > ..then run '/usr/sbin/cron' from the command line, and see if it > > leaves a coredump in the current directory. If it does, then > > do the following: > > > > gdb /usr/sbin/cron /path/to/cron.core > > (at the gdb prompt) > > bt > > info local > > up > > info local > > up > > info local > > [repeat until highest level] > > > > Hm. Now that I kinda tested this, cron doesn't seem to leave > > a corefile. Well, still.. this message was redirected to -stable > > in the hope that somebody there would know better how to help :\ > > > > G'luck, > > Peter > > > > -- > > This sentence claims to be an Epimenides paradox, but it is lying. > > > > Okay, I followed your instructions: (I purposefully redirected this to -stable.. since you don't want to acknowledge it is a -stable issue, staying on -hackers this time..) The stack trace you posted seems to imply that cron is dying while processing rico's crontab, and is dying at such a point in the code that would indicate that rico's account has expired. Is that the case? If so, then the easiest thing for you to do would be to remove rico's crontab (crontab -u rico -l > rico.cron.save && crontab -u rico -r) until rico's account is reactivated or totally removed. G'luck, Peter -- .siht ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 9:36:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 496E437B403 for ; Mon, 16 Jul 2001 09:36:16 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.130.87.Dial1.SanJose1.Level3.net [209.245.130.87]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA16452; Mon, 16 Jul 2001 09:35:51 -0700 (PDT) Message-ID: <3B53180D.F73197A2@mindspring.com> Date: Mon, 16 Jul 2001 09:36:29 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matt Dillon Cc: Leo Bicknell , Julian Elischer , Drew Eckhardt , hackers@FreeBSD.ORG Subject: Re: Network performance tuning. References: <200107130128.f6D1SFE59148@earth.backplane.com> <200107130217.f6D2HET67695@revolt.poohsticks.org> <20010712223042.A77503@ussenterprise.ufp.org> <200107131708.f6DH8ve65071@earth.backplane.com> <3B515097.6551A530@elischer.org> <20010715103334.A64293@ussenterprise.ufp.org> <200107151705.f6FH5Gd08326@earth.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matt Dillon wrote: > Also, the algorithm is less helpful when it has to figure out the > optimal transmit buffer size for every new connection (consider a web > server). I am considering ripping out the ssthresh junk from the stack, > which does not work virtually at all, and using the route table's > ssthresh field to set the initial buffer size for the algorithm. The "state of the art" for initial window size is flow monitoring at the next hop router, with feedback to the host system. A gross approximation is called "fast start". ClickArray has a patch for this, which could potentially be released back to FreeBSD; I will check with TPTB... it's a pretty trivial version of the RFC'ed initial window scaling. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 9:41:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id C861B37B403; Mon, 16 Jul 2001 09:41:53 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.130.87.Dial1.SanJose1.Level3.net [209.245.130.87]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA15033; Mon, 16 Jul 2001 09:41:44 -0700 (PDT) Message-ID: <3B53196E.CF1C2110@mindspring.com> Date: Mon, 16 Jul 2001 09:42:22 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Wilko Bulte Cc: "David O'Brien" , Jens Schweikhardt , hackers@FreeBSD.ORG Subject: Re: Whitespace at end of line References: <20010715155941.C1165@schweikhardt.net> <20010715111956.A71874@dragon.nuxi.com> <20010715202505.A94801@freebie.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wilko Bulte wrote: > Maybe I'm just plain dim today (I will add a beer to rectify this situation > at first convenience..) but what is so bad about some trailing whitespace > that a massive commit-a-thlon is called for? > > just wondering, > Wilko You use emacs, don't you? 8-) 8-) -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 9:57:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id EA84737B401; Mon, 16 Jul 2001 09:57:22 -0700 (PDT) Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 In-Reply-To: <20010715204819.N769-100000@achilles.silby.com> from Mike Silbersack at "Jul 15, 2001 08:49:19 pm" To: silby@silby.com (Mike Silbersack) Date: Mon, 16 Jul 2001 09:57:22 -0700 (PDT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20010716165722.EA84737B401@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > On Fri, 13 Jul 2001, Bill Paul wrote: > > > For those who have gigabit ethernet NICs based on the National > > Semiconductor DP83820 and DP83821 controller chips and want to use > > them with FreeBSD 4.2 and 4.3, there is a driver kit now available > > at the following URL: > ... > > These cards are all extremely cheap (some can be had for under $100) > > and fairly easy to find. (I now have one in my workstation.) They could > > potentially become extremely popular, which is why I'm making a driver > > retrofit kit available. Anyone running a recent 4-STABLE or 5.0-CURRENT > > system should already have the necessary driver support. > > How do these perform compared to the more expensive gigabit cards? > > Mike "Silby" Silbersack > They're "okay." The NatSemi chip has one flaw, which is that RX buffers must be aligned on a 64-bit boundary. None of the more expensive NICs have this restriction. The correct way to deal with this is to copy frames on receive to fixup the alignment, but I decided to make this conditional for this driver: on the i386 platform, the driver omits the copy since unaligned accesses are allowed, and the performance hit for copying is severe when you're using jumbo frames. On the alpha, you have to do the copy. The chip has some nifty features though: hardware VLAN tag insertion and removal, TCP/IP checksum offload on receive and transmit, 2048-bit multicast hash filter, and 4 pattern match buffers for use with WOL. The transmit checksum offload has to be turned off if you use jumbo frames larger than about 8K, because the chip only has an 8K transmit FIFO. There is also support for interrupt moderation. For $90 to $120, they're a good bargain. You should be able get at least 300 to 400Mbps on good x86 hardware (with TCP). -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 10: 0:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 977E037B401 for ; Mon, 16 Jul 2001 10:00:16 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.130.87.Dial1.SanJose1.Level3.net [209.245.130.87]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id KAA25499; Mon, 16 Jul 2001 10:00:13 -0700 (PDT) Message-ID: <3B531DC2.DD8B9D1B@mindspring.com> Date: Mon, 16 Jul 2001 10:00:50 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: sridharv@ufl.edu Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: init References: <200107152301.TAA16828@anansi.vpha.health.ufl.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG sridharv@ufl.edu wrote: > > i need to TAILQ_INIT a queue at kernel startup .. how > can i do it in my code? > reg Grep for "SYSINIT" in the kernel sources. Do your initialization as late as possible, but before the queue is used. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 10: 7:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id B8B6837B408 for ; Mon, 16 Jul 2001 10:07:41 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.130.87.Dial1.SanJose1.Level3.net [209.245.130.87]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id KAA03660; Mon, 16 Jul 2001 10:07:39 -0700 (PDT) Message-ID: <3B531F81.8C6B4C05@mindspring.com> Date: Mon, 16 Jul 2001 10:08:17 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dan Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pagedaemon + vmdaemon References: <20010715181123.A29164-100000@gandalf.bravenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dan wrote: > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > root 2 14.2 0.0 0 0 ?? DL Tue11AM 4:35.33 (pagedaemon) > root 3 12.7 0.0 0 0 ?? DL Tue11AM 1:56.25 (vmdaemon) > > Cpu kept hitting high load averages on machines for about 1 min periods on > some machines on some apache servers. I wrote a script to catch the > offending processes and it seems to be these ones. Ideas on why they would > be taking that much cpu? Generally speaking, it probably means that you are swapping a lot because you are running more programs than you have RAM available to run. If you add RAM, or run fewer programs, this will go away. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 10:10:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id ACAE537B401; Mon, 16 Jul 2001 10:10:33 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.130.87.Dial1.SanJose1.Level3.net [209.245.130.87]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id KAA17995; Mon, 16 Jul 2001 10:10:29 -0700 (PDT) Message-ID: <3B53202B.270086D5@mindspring.com> Date: Mon, 16 Jul 2001 10:11:07 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Silbersack Cc: Bill Paul , hackers@FreeBSD.ORG Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 References: <20010715204819.N769-100000@achilles.silby.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Silbersack wrote: > > For those who have gigabit ethernet NICs based on the National > > Semiconductor DP83820 and DP83821 controller chips and want to use > > them with FreeBSD 4.2 and 4.3, there is a driver kit now available > > at the following URL: > ... > > These cards are all extremely cheap (some can be had for under $100) > > and fairly easy to find. (I now have one in my workstation.) They could > > potentially become extremely popular, which is why I'm making a driver > > retrofit kit available. Anyone running a recent 4-STABLE or 5.0-CURRENT > > system should already have the necessary driver support. > > How do these perform compared to the more expensive gigabit cards? Read the driver. In general, they require an extra copy because of the inability of the card to DMA on a reasonable boundry. Bill's commentary in his drivers is frequently enlightening, and often amusing... 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 10:15:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (Postfix) with ESMTP id 725DD37B403; Mon, 16 Jul 2001 10:15:10 -0700 (PDT) (envelope-from terryl@air.rose.hp.com) Received: from air.rose.hp.com (air.rose.hp.com [15.8.145.103]) by atlrel2.hp.com (Postfix) with ESMTP id 0022FBA5; Mon, 16 Jul 2001 13:15:07 -0400 (EDT) Received: (from terryl@localhost) by air.rose.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) id KAA03562; Mon, 16 Jul 2001 10:04:18 -0700 (PDT) From: Terry Lee Message-Id: <200107161704.KAA03562@air.rose.hp.com> Subject: Re: HP9000/L1000 To: freebsd-hackers@freebsd.org Date: Mon, 16 Jul 2001 10:04:17 PDT Cc: danny@AlphaZed.com, obrien@freebsd.org, jhb@freebsd.org, scanner@jurai.net, hm@kts.org Reply-To: terryl@rose.hp.com X-Mailer: Elm [revision: 212.5] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG To All, Recently, a few people mentioned that there is interest in porting FreeBSD to HP's PA-RISC platforms. The following URL has documentation and an early release of the Linux PA-RISC port. I am not affiliated with the project, but I would like to see FreeBSD on more platforms. I hope the URL helps. http://parisc-linux.org -- Terry Lee Hewlett-Packard Company terryl@rose.hp.com Internet and Applications Systems Lab Tel: (916) 748-2352 8000 Foothills Blvd., MS 5596 Fax: (916) 748-2337 Roseville, CA 95747-5596 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 10:19:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id F226E37B401 for ; Mon, 16 Jul 2001 10:19:23 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f6GHImO15977; Mon, 16 Jul 2001 10:18:48 -0700 (PDT) (envelope-from dillon) Date: Mon, 16 Jul 2001 10:18:48 -0700 (PDT) From: Matt Dillon Message-Id: <200107161718.f6GHImO15977@earth.backplane.com> To: Luigi Rizzo Cc: Tim , Leo Bicknell , Drew Eckhardt , hackers@FreeBSD.ORG Subject: Re: eXperimental bandwidth delay product code (was Re: Network performance tuning.) References: <200107161420.QAA48911@info.iet.unipi.it> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :i haven't seen the beginning of the thread but surely both altq :and dummynet can help, with the CBQ/WFQ support. : :In the case of dummynet, you can pace incoming traffic as well, :at your endpoint. This means you act after the bottleneck, :but the effect is that this way :you will delay acks, and so slow down the connection eating a lot of :bandwidth, and in the steady state this keeps the queue very :short even before the bottleneck. :Much like what products like packeteer do. : : cheers : luigi I don't know much about CBQ (Class Based Queuing) and WFQ (Weighted Fair Queueing), but my impression is that these protocols would only effect the transmit side (like the patch I posted) and would also have to be implemented at the router nodes rather then simply at the end points. Of course, for a modem your end point *is* a router node so that would probably work ok. The patch I posted, implementing bandwidth delay product adjustments to the transmit window, should work extremely well with a modem or DSL line (where the bandwidth restriction occurs near the end points rather then in the middle of the network), but again it only effects outgoing data. I'm looking at Julian's algorithms to see if there is a receive side solution I can implement that wouldn't conflict with the transmit side solution. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 10:42:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id 3549E37B401 for ; Mon, 16 Jul 2001 10:42:39 -0700 (PDT) (envelope-from freebsd@tarakan-network.com) Received: from chojin (chojin [192.168.69.2]) by tarakan-network.com (8.11.4/8.11.3) with SMTP id f6GHgS827661; Mon, 16 Jul 2001 19:42:29 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <001b01c10e1e$a9bf9f80$0245a8c0@chojin> From: "Chojin" To: "Peter Pentchev" Cc: References: <007001c10e0c$f02d94c0$0245a8c0@chojin> <20010716185318.E56285@ringworld.oblivion.bg> <002101c10e10$5edea640$0245a8c0@chojin> <20010716193956.H56285@ringworld.oblivion.bg> Subject: Re: Cron program core dumped (signal 11) Date: Mon, 16 Jul 2001 19:42:14 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In fact, rico account has expired. I removed expiration ,then now cron works. But I thought cron had no problem if an account expires. Strange... :p Thanks for all. Regards. Chojin ----- Original Message ----- From: "Peter Pentchev" To: "Chojin" Cc: Sent: Monday, July 16, 2001 6:39 PM Subject: Re: Cron program core dumped (signal 11) > On Mon, Jul 16, 2001 at 06:00:01PM +0200, Chojin wrote: > > > cd /usr/src/usr.sbin/cron > > > make cleandir depend > > > make CFLAGS="-ggdb -g3" STRIP="" all install > > > > > > ..then run '/usr/sbin/cron' from the command line, and see if it > > > leaves a coredump in the current directory. If it does, then > > > do the following: > > > > > > gdb /usr/sbin/cron /path/to/cron.core > > > (at the gdb prompt) > > > bt > > > info local > > > up > > > info local > > > up > > > info local > > > [repeat until highest level] > > > > > > Hm. Now that I kinda tested this, cron doesn't seem to leave > > > a corefile. Well, still.. this message was redirected to -stable > > > in the hope that somebody there would know better how to help :\ > > > > > > G'luck, > > > Peter > > > > > > -- > > > This sentence claims to be an Epimenides paradox, but it is lying. > > > > > > > Okay, I followed your instructions: > > (I purposefully redirected this to -stable.. since you don't want > to acknowledge it is a -stable issue, staying on -hackers this time..) > > The stack trace you posted seems to imply that cron is dying while > processing rico's crontab, and is dying at such a point in the code > that would indicate that rico's account has expired. Is that the case? > If so, then the easiest thing for you to do would be to remove rico's > crontab (crontab -u rico -l > rico.cron.save && crontab -u rico -r) > until rico's account is reactivated or totally removed. > > G'luck, > Peter > > -- > .siht ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 10:42:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-r08.mx.aol.com (imo-r08.mx.aol.com [152.163.225.104]) by hub.freebsd.org (Postfix) with ESMTP id 7708637B421 for ; Mon, 16 Jul 2001 10:42:47 -0700 (PDT) (envelope-from Bsdguru@aol.com) Received: from Bsdguru@aol.com by imo-r08.mx.aol.com (mail_out_v31.7.) id n.3d.e7348af (3964) for ; Mon, 16 Jul 2001 13:42:39 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <3d.e7348af.2884818f@aol.com> Date: Mon, 16 Jul 2001 13:42:39 EDT Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 07/16/2001 1:11:09 PM Eastern Daylight Time, tlambert2@mindspring.com writes: > > How do these perform compared to the more expensive gigabit cards? > > Read the driver. > > In general, they require an extra copy because of the inability > of the card to DMA on a reasonable boundry. > > Bill's commentary in his drivers is frequently enlightening, > and often amusing... 8-). > Maybe at some point he'll "get" that the boundry issue is a pci bus-mastering spec issue and not a controller design flaw, as he seems to harp on this in just about every driver? A more important question is "are these 32-bit cards, and if so, do they have enough internal buffer to do sustained 1GB transfers". Generally 32-bit PCI is too slow for GB, as it cant do sustained 1GB transfers. Some 32-bit GB cards are just a total waste. Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 10:43: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 1088737B406; Mon, 16 Jul 2001 10:42:57 -0700 (PDT) (envelope-from matt-l@pacbell.net) Received: from fire (1Cust227.tnt1.pasadena.ca.da.uu.net [63.28.226.227]) by albatross.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id KAA22920; Mon, 16 Jul 2001 10:42:55 -0700 (PDT) Message-ID: <001b01c10e1d$e1d4e1b0$6503c23f@XGforce.com> Reply-To: "matt" From: "matt" To: , Cc: "FreeBSD-ISP" Subject: router question Date: Mon, 16 Jul 2001 10:36:41 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anyone know if there's a inbound T1 line with RJ45 connector will work with my FreeBSD box without connecting to a CISCO router first? In another word, hook FreeBSD box directly to the T1's RJ45. Or i have to buy a CISCO router to have the T1 RJ45 connect to it, then from router to a switch, and then to FreeBSD? ====================================== WWW.XGFORCE.COM The Next Generation Load Balance and Fail Safe Server Clustering Software for the Internet. ====================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 10:50:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from zero.namba1.com (zero.namba1.com [64.75.169.20]) by hub.freebsd.org (Postfix) with ESMTP id 9811037B401; Mon, 16 Jul 2001 10:50:13 -0700 (PDT) (envelope-from aaron@namba1.com) Received: from [134.173.120.17] by zero.namba1.com (NTMail 5.02.0001/QC8568.34.ce8cdec7) with ESMTP id qiibaaaa for freebsd-hackers@freebsd.org; Mon, 16 Jul 2001 07:50:07 -1000 From: "Aaron Namba" To: "matt" , , Cc: "FreeBSD-ISP" Subject: RE: router question Date: Mon, 16 Jul 2001 10:49:44 -0700 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <001b01c10e1d$e1d4e1b0$6503c23f@XGforce.com> Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Depends of course on whether you need routing... -----Original Message----- From: owner-freebsd-isp@FreeBSD.ORG [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of matt Sent: Monday, July 16, 2001 10:37 AM To: freebsd-hackers@freebsd.org; freebsd-net@freebsd.org Cc: FreeBSD-ISP Subject: router question Does anyone know if there's a inbound T1 line with RJ45 connector will work with my FreeBSD box without connecting to a CISCO router first? In another word, hook FreeBSD box directly to the T1's RJ45. Or i have to buy a CISCO router to have the T1 RJ45 connect to it, then from router to a switch, and then to FreeBSD? ====================================== WWW.XGFORCE.COM The Next Generation Load Balance and Fail Safe Server Clustering Software for the Internet. ====================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" 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 Jul 16 10:54:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from server.soekris.com (soekris.com [216.15.61.44]) by hub.freebsd.org (Postfix) with ESMTP id 785A637B401 for ; Mon, 16 Jul 2001 10:54:12 -0700 (PDT) (envelope-from soren@soekris.com) Received: from soekris.com (soren.soekris.com [192.168.1.4]) by server.soekris.com (8.9.2/8.9.2) with ESMTP id KAA21572; Mon, 16 Jul 2001 10:54:13 -0700 (PDT) (envelope-from soren@soekris.com) Message-ID: <3B532A40.6BC65369@soekris.com> Date: Mon, 16 Jul 2001 10:54:08 -0700 From: Soren Kristensen Organization: Soekris Engineering X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bsdguru@aol.com Cc: hackers@FreeBSD.ORG Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 References: <3d.e7348af.2884818f@aol.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Bsdguru@aol.com wrote: > > In a message dated 07/16/2001 1:11:09 PM Eastern Daylight Time, > tlambert2@mindspring.com writes: > > > > How do these perform compared to the more expensive gigabit cards? > > > > Read the driver. > > > > In general, they require an extra copy because of the inability > > of the card to DMA on a reasonable boundry. > > > > Bill's commentary in his drivers is frequently enlightening, > > and often amusing... 8-). > > > > Maybe at some point he'll "get" that the boundry issue is a pci bus-mastering > spec issue and not a controller design flaw, as he seems to harp on this in > just about every driver? That's incorrect, there no nothing limiting a PCI device for doing busmastering on a byte boundary.... The reason why not that many devices support it, especially on the receive side, is that the circuit gets more complicated. Another thing, since there is all this hardware that requires alignment, maybe we should consider modifying FreeBSD so receive buffers are aligned, afaik, Linux use aligned receive buffers.... But I don't know how complicated that would be, so please don't flame me :-) > A more important question is "are these 32-bit cards, and if so, do they have > enough internal buffer to do sustained 1GB transfers". Generally 32-bit PCI > is too slow for GB, as it cant do sustained 1GB transfers. Some 32-bit GB > cards are just a total waste. > Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 11: 3:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-r02.mx.aol.com (imo-r02.mx.aol.com [152.163.225.98]) by hub.freebsd.org (Postfix) with ESMTP id C48F137B401 for ; Mon, 16 Jul 2001 11:03:52 -0700 (PDT) (envelope-from Bsdguru@aol.com) Received: from Bsdguru@aol.com by imo-r02.mx.aol.com (mail_out_v31.7.) id n.82.d1cd459 (3964) for ; Mon, 16 Jul 2001 14:03:48 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <82.d1cd459.28848684@aol.com> Date: Mon, 16 Jul 2001 14:03:48 EDT Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 07/16/2001 1:54:25 PM Eastern Daylight Time, soren@soekris.com writes: > > Maybe at some point he'll "get" that the boundry issue is a pci bus- > mastering > > spec issue and not a controller design flaw, as he seems to harp on this > in > > just about every driver? > > That's incorrect, there no nothing limiting a PCI device for doing > busmastering on a byte boundary.... The reason why not that many devices > support it, especially on the receive side, is that the circuit gets > more complicated. > the fact that you can "fudge" it in circuitry doesnt change the way that transfers work. B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 11:15:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail5.carolina.rr.com (fe5.southeast.rr.com [24.93.67.52]) by hub.freebsd.org (Postfix) with ESMTP id A60C037B403; Mon, 16 Jul 2001 11:15:24 -0700 (PDT) (envelope-from khayman@carolina.rr.com) Received: from carolina.rr.com ([168.215.135.201]) by mail5.carolina.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Mon, 16 Jul 2001 14:15:22 -0400 Message-ID: <3B532F3A.95B68A8E@carolina.rr.com> Date: Mon, 16 Jul 2001 14:15:22 -0400 From: khayman X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Aaron Namba Cc: matt , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, FreeBSD-ISP Subject: Re: router question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG also, just because it terminates in RJ45 (and are you sure it's rj45, or does the male connector just look like it) does not mean that it is ethernet. Our cisco 7200 series routers have cards in them with what looks like rj45 ports (female). They are actually rj48 (different pin-outs i think) and are integrated csu/dsu's that'll take that connector off a channelized t1. Its actually a serial interface. I would say in all likelihood, the answer to your question is "no". You need something that'll take the serial signal off the t1 and convert it to ethernet at layer2. Unless of course you have a csu/dsu in your fBSD box. hope this helps. Aaron Namba wrote: > > Depends of course on whether you need routing... > > -----Original Message----- > From: owner-freebsd-isp@FreeBSD.ORG > [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of matt > Sent: Monday, July 16, 2001 10:37 AM > To: freebsd-hackers@freebsd.org; freebsd-net@freebsd.org > Cc: FreeBSD-ISP > Subject: router question > > Does anyone know if there's a inbound T1 line with RJ45 > connector will work with my FreeBSD box without > connecting to a CISCO router first? In another word, > hook FreeBSD box directly to the T1's RJ45. > > Or i have to buy a CISCO router to have the T1 RJ45 > connect to it, then from router to a switch, and then to > FreeBSD? > > ====================================== > WWW.XGFORCE.COM > The Next Generation Load Balance and > Fail Safe Server Clustering Software > for the Internet. > ====================================== > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > > 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 Jul 16 11:23:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id 9525637B406; Mon, 16 Jul 2001 11:23:33 -0700 (PDT) (envelope-from rbraun@apple.com) Received: from apple.com (A17-129-100-225.apple.com [17.129.100.225]) by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id LAA11845; Mon, 16 Jul 2001 11:23:33 -0700 (PDT) Received: from scv3.apple.com (scv3.apple.com) by apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Mon, 16 Jul 2001 11:23:26 -0700 Received: from ibook (il0204a-dhcp65.apple.com [17.202.45.193]) by scv3.apple.com (8.9.3/8.9.3) with ESMTP id LAA01529; Mon, 16 Jul 2001 11:23:26 -0700 (PDT) Date: Mon, 16 Jul 2001 11:21:55 -0700 X-Mailer: Apple Mail (2.402) Mime-Version: 1.0 (Apple Message framework v402) Cc: Aaron Namba , matt , freebsd-hackers@freebsd.org, freebsd-net@freebsd.org, FreeBSD-ISP Message-Id: <7059E29D-7A17-11D5-B921-003065AD81C0@ibook.apple.com> Content-Transfer-Encoding: 7bit In-Reply-To: <3B532F3A.95B68A8E@carolina.rr.com> Content-Type: text/plain; format=flowed; charset=us-ascii Subject: Re: router question From: Rob Braun To: khayman Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Several companies, one of which is LanMedia Corporation (LMC), sell PCI cards that handle T1s and include an integrated CSU/DSU. So, yes, you can terminate a T1 on your PC. Find one of these cards and you're all set. I believe FreeBSD already has a driver for the LMC cards. Rob On Monday, July 16, 2001, at 11:15 AM, khayman wrote: > also, just because it terminates in RJ45 (and are you sure it's rj45, or > does the male connector just look like it) does not mean that it is > ethernet. Our cisco 7200 series routers have cards in them with what > looks like rj45 ports (female). They are actually rj48 (different > pin-outs i think) and are integrated csu/dsu's that'll take that > connector off a channelized t1. Its actually a serial interface. > > I would say in all likelihood, the answer to your question is "no". You > need something that'll take the serial signal off the t1 and convert it > to ethernet at layer2. Unless of course you have a csu/dsu in your fBSD > box. > > hope this helps. > > Aaron Namba wrote: >> >> Depends of course on whether you need routing... >> >> -----Original Message----- >> From: owner-freebsd-isp@FreeBSD.ORG >> [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of matt >> Sent: Monday, July 16, 2001 10:37 AM >> To: freebsd-hackers@freebsd.org; freebsd-net@freebsd.org >> Cc: FreeBSD-ISP >> Subject: router question >> >> Does anyone know if there's a inbound T1 line with RJ45 >> connector will work with my FreeBSD box without >> connecting to a CISCO router first? In another word, >> hook FreeBSD box directly to the T1's RJ45. >> >> Or i have to buy a CISCO router to have the T1 RJ45 >> connect to it, then from router to a switch, and then to >> FreeBSD? >> >> ====================================== >> WWW.XGFORCE.COM >> The Next Generation Load Balance and >> Fail Safe Server Clustering Software >> for the Internet. >> ====================================== >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-isp" in the body of the message >> >> 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 11:33:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.131]) by hub.freebsd.org (Postfix) with ESMTP id 2937C37B401; Mon, 16 Jul 2001 11:33:12 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA00154; Mon, 16 Jul 2001 20:33:07 +0200 (CEST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.4/8.11.4) id f6GIX6b01199; Mon, 16 Jul 2001 20:33:06 +0200 (CEST) (envelope-from wkb) Date: Mon, 16 Jul 2001 20:33:06 +0200 From: Wilko Bulte To: Terry Lambert Cc: "David O'Brien" , Jens Schweikhardt , hackers@FreeBSD.ORG Subject: Re: Whitespace at end of line Message-ID: <20010716203306.A1163@freebie.xs4all.nl> References: <20010715155941.C1165@schweikhardt.net> <20010715111956.A71874@dragon.nuxi.com> <20010715202505.A94801@freebie.xs4all.nl> <3B53196E.CF1C2110@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B53196E.CF1C2110@mindspring.com>; from tlambert2@mindspring.com on Mon, Jul 16, 2001 at 09:42:22AM -0700 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 16, 2001 at 09:42:22AM -0700, Terry Lambert wrote: > Wilko Bulte wrote: > > Maybe I'm just plain dim today (I will add a beer to rectify this situation > > at first convenience..) but what is so bad about some trailing whitespace > > that a massive commit-a-thlon is called for? > > > > just wondering, > > Wilko > > You use emacs, don't you? No, vi. My first experiences with Unix (SysV.2) were in the days that Emacs was considered anti-social (on 8MB memory machines with 68020 CPUs). W/ -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte "Youth is not a time in life, it is a state of mind" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 11:39:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 48D9837B406 for ; Mon, 16 Jul 2001 11:39:07 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 13446 invoked by uid 1001); 16 Jul 2001 18:39:05 +0000 (GMT) To: wkb@freebie.xs4all.nl Cc: tlambert2@mindspring.com, obrien@FreeBSD.ORG, schweikh@schweikhardt.net, hackers@FreeBSD.ORG Subject: Re: Whitespace at end of line From: sthaug@nethelp.no In-Reply-To: Your message of "Mon, 16 Jul 2001 20:33:06 +0200" References: <20010716203306.A1163@freebie.xs4all.nl> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 16 Jul 2001 20:39:04 +0200 Message-ID: <13444.995308744@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > You use emacs, don't you? > > No, vi. My first experiences with Unix (SysV.2) were in the days that > Emacs was considered anti-social (on 8MB memory machines with 68020 CPUs). What, you mean you *haven't* run emacs on a Sun-3/50 with 4 Mbytes? :-) Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 11:40:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp7.xs4all.nl (smtp7.xs4all.nl [194.109.127.133]) by hub.freebsd.org (Postfix) with ESMTP id 761B037B403; Mon, 16 Jul 2001 11:40:14 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp7.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA14036; Mon, 16 Jul 2001 20:40:11 +0200 (CEST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.4/8.11.4) id f6GIe9T01333; Mon, 16 Jul 2001 20:40:09 +0200 (CEST) (envelope-from wkb) Date: Mon, 16 Jul 2001 20:40:09 +0200 From: Wilko Bulte To: sthaug@nethelp.no Cc: tlambert2@mindspring.com, obrien@FreeBSD.ORG, schweikh@schweikhardt.net, hackers@FreeBSD.ORG Subject: Re: Whitespace at end of line Message-ID: <20010716204009.A1308@freebie.xs4all.nl> References: <20010716203306.A1163@freebie.xs4all.nl> <13444.995308744@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <13444.995308744@verdi.nethelp.no>; from sthaug@nethelp.no on Mon, Jul 16, 2001 at 08:39:04PM +0200 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 16, 2001 at 08:39:04PM +0200, sthaug@nethelp.no wrote: > > > You use emacs, don't you? > > > > No, vi. My first experiences with Unix (SysV.2) were in the days that > > Emacs was considered anti-social (on 8MB memory machines with 68020 CPUs). > > What, you mean you *haven't* run emacs on a Sun-3/50 with 4 Mbytes? :-) No. I did run SunOS 3.5 on them but that was without Emacs. The 3/50 was an upgrade of our 2/120 ;-) Ever tried compiling X on a 2/120? :) W/ -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte "Youth is not a time in life, it is a state of mind" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 12:10:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-62.dsl.lsan03.pacbell.net [63.207.60.62]) by hub.freebsd.org (Postfix) with ESMTP id 1962B37B401 for ; Mon, 16 Jul 2001 12:10:14 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2AD0967378; Mon, 16 Jul 2001 12:10:13 -0700 (PDT) Date: Mon, 16 Jul 2001 12:10:11 -0700 From: Kris Kennaway To: Chojin Cc: Peter Pentchev , freebsd-hackers@FreeBSD.ORG Subject: Re: Cron program core dumped (signal 11) Message-ID: <20010716121011.D94139@xor.obsecurity.org> References: <007001c10e0c$f02d94c0$0245a8c0@chojin> <20010716185318.E56285@ringworld.oblivion.bg> <002101c10e10$5edea640$0245a8c0@chojin> <20010716193956.H56285@ringworld.oblivion.bg> <001b01c10e1e$a9bf9f80$0245a8c0@chojin> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="AbQceqfdZEv+FvjW" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001b01c10e1e$a9bf9f80$0245a8c0@chojin>; from freebsd@tarakan-network.com on Mon, Jul 16, 2001 at 07:42:14PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --AbQceqfdZEv+FvjW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 16, 2001 at 07:42:14PM +0200, Chojin wrote: > In fact, rico account has expired. > I removed expiration ,then now cron works. >=20 > But I thought cron had no problem if an account expires. > Strange... :p Yeah, it shouldn't do that. Kris --AbQceqfdZEv+FvjW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7UzwSWry0BWjoQKURAhxXAJsG/o4O8pENbvD/AWMMHBmS9JyaUACeOKt/ gTXHC75cNH6VTseHJSUFYAA= =3DqF -----END PGP SIGNATURE----- --AbQceqfdZEv+FvjW-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 12:31:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 2833437B401 for ; Mon, 16 Jul 2001 12:31:20 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f6GJV2x21201; Mon, 16 Jul 2001 12:31:02 -0700 (PDT) (envelope-from obrien) Date: Mon, 16 Jul 2001 12:31:02 -0700 From: "David O'Brien" To: Terry Lambert Cc: Wilko Bulte , Jens Schweikhardt , hackers@FreeBSD.ORG Subject: Re: Whitespace at end of line Message-ID: <20010716123102.D20942@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010715155941.C1165@schweikhardt.net> <20010715111956.A71874@dragon.nuxi.com> <20010715202505.A94801@freebie.xs4all.nl> <3B53196E.CF1C2110@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B53196E.CF1C2110@mindspring.com>; from tlambert2@mindspring.com on Mon, Jul 16, 2001 at 09:42:22AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 16, 2001 at 09:42:22AM -0700, Terry Lambert wrote: > Wilko Bulte wrote: > > Maybe I'm just plain dim today (I will add a beer to rectify this situation > > at first convenience..) but what is so bad about some trailing whitespace > > that a massive commit-a-thlon is called for? > > > > just wondering, > > Wilko > > You use emacs, don't you? What does vi vs. emacs have to do with it? -- -- David, a Vi user. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 12:37:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id CA38A37B403; Mon, 16 Jul 2001 12:37:36 -0700 (PDT) Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 In-Reply-To: <200107161829.LAA23310@smtpout.mac.com> from Josh Osborne at "Jul 16, 2001 02:28:55 pm" To: stripes@mac.com (Josh Osborne) Date: Mon, 16 Jul 2001 12:37:36 -0700 (PDT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20010716193736.CA38A37B403@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > On Monday, July 16, 2001, at 12:57 PM, Bill Paul wrote: > [...] > > The chip has some nifty features though: hardware VLAN tag insertion > > and removal, TCP/IP checksum offload on receive and transmit, 2048-bit > > multicast hash filter, and 4 pattern match buffers for use with WOL. > > What is WOL? Wake on LAN. > > The transmit checksum offload has to be turned off if you use jumbo > > frames larger than about 8K, because the chip only has an 8K transmit > > FIFO. There is also support for interrupt moderation. > > Does it automatically not checksum packets >8K, or does A Bad Thing > happen if you fail to turn it off first? It does a Bad Thing (tm). In my testing, trying to send a frame larger than 8170 bytes puts the transmitter to sleep. Normally, the chip acknowledges transmit commands with three interrupt indications: TX DMA done (packet was transfered to the chip), TX done (packet made it to the wire), TX idle (TX queue empty, waiting for more packets). If you have transmit checksums enabled and send a frame larger than 8170 bytes, you get the TX DMA done interrupt, but nothing else. The transmitter stops responding after that, and eventually a watchdog timeout is triggered which resets the NIC. The driver disables TX checksum offloading if you set the MTU above a certain threshold. I think at that point, the performance gain from using jumbo frames is greater than that of using TX checksum offload anyway (for sustained transfers anyway). For the record, the chip allows TX checksum offload on a global or per-packet basis. I use the per-packet method, and simply don't set the "I want TX checksums computed" bits in the TX DMA descriptors once the MTU is set above the threshold (I also clear the if_hwassist flags so the OS will go back to computing the checksums itself). -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 12:56:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 055B037B408; Mon, 16 Jul 2001 12:56:51 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f6GJulV95697; Mon, 16 Jul 2001 21:56:48 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f6GJvTP01551; Mon, 16 Jul 2001 21:57:29 +0200 (CEST) Date: Mon, 16 Jul 2001 21:57:28 +0200 From: Bernd Walter To: Wilko Bulte Cc: sthaug@nethelp.no, tlambert2@mindspring.com, obrien@FreeBSD.ORG, schweikh@schweikhardt.net, hackers@FreeBSD.ORG Subject: Re: Whitespace at end of line Message-ID: <20010716215728.A1477@cicely20.cicely.de> References: <20010716203306.A1163@freebie.xs4all.nl> <13444.995308744@verdi.nethelp.no> <20010716204009.A1308@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010716204009.A1308@freebie.xs4all.nl>; from wkb@freebie.xs4all.nl on Mon, Jul 16, 2001 at 08:40:09PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 16, 2001 at 08:40:09PM +0200, Wilko Bulte wrote: > On Mon, Jul 16, 2001 at 08:39:04PM +0200, sthaug@nethelp.no wrote: > > > > You use emacs, don't you? > > > > > > No, vi. My first experiences with Unix (SysV.2) were in the days that > > > Emacs was considered anti-social (on 8MB memory machines with 68020 CPUs). > > > > What, you mean you *haven't* run emacs on a Sun-3/50 with 4 Mbytes? :-) > > No. I did run SunOS 3.5 on them but that was without Emacs. The 3/50 was > an upgrade of our 2/120 ;-) Ever tried compiling X on a 2/120? :) It's even not fun with these: ticso@cicely41:~> dmesg | head NetBSD 1.5V (CICELY41) #1: Sat May 19 21:52:45 CEST 2001 ticso@cicely41.cicely.de:/net/10.1.1.22/var/d21/NetBSD/src/sys/arch/sun3/compile/CICELY41 Model: sun3 60 fpu: mc68881 total memory = 24576 KB avail memory = 21888 KB using 166 buffers containing 1328 KB of memory mainbus0 (root) obio0 at mainbus0 zsc0 at obio0 addr 0x0 ipl 6: (softpri 3) ticso@cicely41:~> uptime 9:48PM up 43 days, 6:42, 3 users, load averages: 0.18, 0.12, 0.09 I also own two 3/50 but 4M is not realy much today. But now that NetBSD has official support for sun2 Machines ;) -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 13: 3:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 8FEA537B406 for ; Mon, 16 Jul 2001 13:03:31 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.4/8.11.2) with ESMTP id f6GK3Pv72692; Mon, 16 Jul 2001 13:03:25 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010715181123.A29164-100000@gandalf.bravenet.com> Date: Mon, 16 Jul 2001 13:03:33 -0700 (PDT) From: John Baldwin To: Dan Subject: RE: pagedaemon + vmdaemon Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 16-Jul-01 Dan wrote: > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > root 2 14.2 0.0 0 0 ?? DL Tue11AM 4:35.33 (pagedaemon) > root 3 12.7 0.0 0 0 ?? DL Tue11AM 1:56.25 (vmdaemon) > > Cpu kept hitting high load averages on machines for about 1 min periods on > some machines on some apache servers. I wrote a script to catch the > offending processes and it seems to be these ones. Ideas on why they would > be taking that much cpu? These processes manage the VM paging, so perhaps you are running low on memory and trashing? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 13:57: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from maildrop.dub-t3-1.nwcgroup.com (maildrop.dub-t3-1.nwcgroup.com [195.129.80.17]) by hub.freebsd.org (Postfix) with ESMTP id 560CA37B407 for ; Mon, 16 Jul 2001 13:56:49 -0700 (PDT) (envelope-from customerservice@playnetwork.com) Received: from maildrop (localhost [127.0.0.1]) by maildrop.dub-t3-1.nwcgroup.com (Postfix) with ESMTP id 1246C4A55 for ; Mon, 16 Jul 2001 21:56:49 +0100 (IST) Message-ID: <147932411.995317009073.JavaMail.nwdmail@maildrop> Date: Mon, 16 Jul 2001 20:56:49 +0000 (GMT+00:00) From: Reply-To: customerservice@playnetwork.com To: hackers@FreeBSD.org Subject: Save Up To 70% On Music For Your Business! Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_31696_868680955.995317009070" X-mailer: NewWorld Direct Java Mail Program X-uri: http://www.newworldcommerce.com X-Complaints: abuse@nwcgroup.com X-Bounce-Info: A7owHoJg~wGApCB6OX.ceN~xyHRS0~zNs6FH+GH+D5+oS~Lx+LO+BMEdA+VXS+1a8h+yOicZ1eb~di~Gfjhi+9PP+GS+bA~UQNl~HjWV+4In~cjnr~umxk+ZlMk Return-Errors-To: customerservice@playnetwork.com X-Errors-To: customerservice@playnetwork.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear Are you currently playing the radio as your in-store music source? Are you tired of all the deejay chatter and endless advertising? OR, are you using a CD player - and find your customers and employees hear the same music over and over because you're too busy to change CDs or buy new ones? Are you uncertain about paying ASCAP, BMI, or SESAC music licensing fees? Introducing PlayNetwork Online, a monthly subscription service that resolves all your business music issues. http://www.nwd42.com/s.asp?N=Zwm8Yq3701v~HNHIEGDCEOYJCHGDFHJhO Best of all it's available to you at an affordable monthly fee. If you'd like to learn more about this exciting new music service, please click on the link below for information regarding the benefits of professionally programmed music and details on our special introductory offer. Add life to your business with music. PlayNetwork Online. Imagine music your way. http://www.nwd42.com/s.asp?N=Zwm8Yq3701v~HNHIEGDCEOYJCHGDFHJhO Click here to configure your eMail preference: http://www.nwd42.com/s.asp?N=Zwm8Yq3701v~HNHIEGDCEOYJCHGDFHJXb Click here to unsubscribe: http://www.nwd42.com/s.asp?N=Zwm8Yq3701v~HNHIEGDCEOYJCHGDFHJfN The following text is for MIME compliant client programs. ------=_Part_31696_868680955.995317009070 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Description: Plain Text mail part Dear Are you currently playing the radio as your in-store music source? Are you tired of all the deejay chatter and endless advertising? OR, are you using a CD player - and find your customers and employees hear the same music over and over because you're too busy to change CDs or buy new ones? Are you uncertain about paying ASCAP, BMI, or SESAC music licensing fees? Introducing PlayNetwork Online, a monthly subscription service that resolves all your business music issues. http://www.nwd42.com/s.asp?N=Zwm8Yq3701v~HNHIEGDCEOYJCHGDFHJhO Best of all it's available to you at an affordable monthly fee. If you'd like to learn more about this exciting new music service, please click on the link below for information regarding the benefits of professionally programmed music and details on our special introductory offer. Add life to your business with music. PlayNetwork Online. Imagine music your way. http://www.nwd42.com/s.asp?N=Zwm8Yq3701v~HNHIEGDCEOYJCHGDFHJhO Click here to configure your eMail preference: http://www.nwd42.com/s.asp?N=Zwm8Yq3701v~HNHIEGDCEOYJCHGDFHJXb Click here to unsubscribe: http://www.nwd42.com/s.asp?N=Zwm8Yq3701v~HNHIEGDCEOYJCHGDFHJfN ------=_Part_31696_868680955.995317009070 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Description: HTML mail part - external links Welcome
=09 =09
=09 =09 =09=09 =09 =09<= td align=3Dleft width=3D"100%">
If you cannot read this eMail, please go to
http://www.nwd42.= com/s.asp?N=3DZwm8Yq3701v~HNHIEGDCEOYJCHGDFHJhO
=09=09=09 =09=09=09=20 =09=09=09 =09=09=09 =09=09=09
3D""
=09=09
Welcome= !
=09=09
FINALLY, AFFORDABLE MUSIC FOR YOUR BUSINESS!
3D""

3D""=
 
<= IMG SRC=3D"http://www.nwd42.com/offer/PlayNetwork/Images/banner5%2ejpg" BOR= DER=3D0 ALT=3D"">
&n= bsp;

Visit our web = site and subscribe today.
Add life to your business with music!
3D""
 
<= TR>
3D""
Or Call Us At 1-866-752-9321 For M= ore Information.
 
Call Me
eMail Us
3D""<= /TD>

=
SUBSCRIBE TODAY AND SAVE!
=09 =09=09 =09

=09 =09=09=20 =09=09=09 =09=09=09=09 =09=09=09 =09=09
=09 =09 =09 =09=09 =09=09=09 =09 =09=09=09 =09=09=09=09 =09=09=09 =09=09
=09=09Click he= re to configure your eMail preference:
http://www.nwd42.com/s.asp?N=3D= Zwm8Yq3701v~HNHIEGDCEOYJCHGDFHJXb =09
=09=09=09=09=09 =09=09=09=09=09Click here to unsubscribe:
http://www.nwd42.com/s.asp?N=3DZwm8Yq3701v= ~HNHIEGDCEOYJCHGDFHJfN =09=09=09=09
=09
------=_Part_31696_868680955.995317009070-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 15:56:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id 3A7E237B409; Mon, 16 Jul 2001 15:56:44 -0700 (PDT) (envelope-from rh@matriplex.com) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id PAA40161; Mon, 16 Jul 2001 15:56:33 -0700 (PDT) (envelope-from rh@matriplex.com) Date: Mon, 16 Jul 2001 15:56:33 -0700 (PDT) From: Richard Hodges To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 In-Reply-To: <20010716165722.EA84737B401@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 16 Jul 2001, Bill Paul wrote: > They're "okay." The NatSemi chip has one flaw, which is that RX buffers > must be aligned on a 64-bit boundary. None of the more expensive NICs have > this restriction. Go ahead and beat me up if you have to :-) But why is there _any_ issue with RX buffer alignment? I get some mbufs and set the data pointer to any point I want, or I get a cluster, which is always on a 2k boundary. Now TX buffers are a problem - I have to take what I get and just "deal with it". If both start address and length need to be aligned, then I'm pretty much screwed - I have to copy... All the best, -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. Product Manager | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 16:26:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gateway.dignus.com (sdsl-66-80-58-206.dsl.lax.megapath.net [66.80.58.206]) by hub.freebsd.org (Postfix) with ESMTP id 63C1737B403 for ; Mon, 16 Jul 2001 16:26:39 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by gateway.dignus.com (8.11.3/8.11.3) with ESMTP id f6GNQQ413115 for ; Mon, 16 Jul 2001 19:26:26 -0400 (EDT) (envelope-from rivers@dignus.com) Received: (from rivers@localhost) by lakes.dignus.com (8.11.3/8.11.3) id f6GNQ4a38454 for freebsd-hackers@freebsd.org; Mon, 16 Jul 2001 19:26:04 -0400 (EDT) (envelope-from rivers) Date: Mon, 16 Jul 2001 19:26:04 -0400 (EDT) From: Thomas David Rivers Message-Id: <200107162326.f6GNQ4a38454@lakes.dignus.com> To: freebsd-hackers@freebsd.org Subject: Debugging natd? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The machine I redirected telnet too has changed IP addresses... And; I discovered after simply changing my natd_flags in /etc/rc.conf that natd isn't properly redirecting the port. I checked the messages log (/var/log/alias.log) and nothing appears to be amiss. (And, I've got -l on the natd_flags; but nothing is showing up in syslog) Here's the flags (this is 4.3-RELEASE): natd_flags="-l -m -u -redirect_port tcp 10.1.0.11:telnet NNNN -redirect_port udp 10.1.0.11:telnet NNNN -redirect_port tcp 10.1.0.26:telnet NNNN -redirect_port u dp 10.1.0.26:telnet NNNN" (The previous/working IP addreses were 10.0.0.11 & 10.0.0.26.) So - per the subject - just how does one start debugging a problem like this - what tools are around to try and figure things out? - 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 Jul 16 16:29:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id 199E037B409 for ; Mon, 16 Jul 2001 16:29:14 -0700 (PDT) (envelope-from dphoenix@bravenet.com) Received: (qmail 53231 invoked by uid 1001); 16 Jul 2001 23:34:52 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 16 Jul 2001 23:34:52 -0000 Date: Mon, 16 Jul 2001 16:34:52 -0700 (PDT) From: Dan To: John Baldwin Cc: Subject: RE: pagedaemon + vmdaemon In-Reply-To: Message-ID: <20010716163402.D48387-100000@gandalf.bravenet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ya it seems it is running into swap abit..... hmmm watching apache with truss i see alot of error #35's in the sys calls....what is that related to again? On Mon, 16 Jul 2001, John Baldwin wrote: > Date: Mon, 16 Jul 2001 13:03:33 -0700 (PDT) > From: John Baldwin > To: Dan > Cc: freebsd-hackers@FreeBSD.org > Subject: RE: pagedaemon + vmdaemon > > > On 16-Jul-01 Dan wrote: > > > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > > root 2 14.2 0.0 0 0 ?? DL Tue11AM 4:35.33 (pagedaemon) > > root 3 12.7 0.0 0 0 ?? DL Tue11AM 1:56.25 (vmdaemon) > > > > Cpu kept hitting high load averages on machines for about 1 min periods on > > some machines on some apache servers. I wrote a script to catch the > > offending processes and it seems to be these ones. Ideas on why they would > > be taking that much cpu? > > These processes manage the VM paging, so perhaps you are running low on memory > and trashing? > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 16:34:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 7C0DB37B407; Mon, 16 Jul 2001 16:34:36 -0700 (PDT) Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 In-Reply-To: from Richard Hodges at "Jul 16, 2001 03:56:33 pm" To: rh@matriplex.com (Richard Hodges) Date: Mon, 16 Jul 2001 16:34:36 -0700 (PDT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20010716233436.7C0DB37B407@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > On Mon, 16 Jul 2001, Bill Paul wrote: > > > They're "okay." The NatSemi chip has one flaw, which is that RX buffers > > must be aligned on a 64-bit boundary. None of the more expensive NICs have > > this restriction. > > Go ahead and beat me up if you have to :-) But why is there _any_ issue > with RX buffer alignment? I get some mbufs and set the data pointer to > any point I want, or I get a cluster, which is always on a 2k boundary. The OS wants the _payload_ to be aligned on a 32-bit boundary. It tries to do 32-bit accesses to the IP header, and the NFS code also does 32-bit accesses when trying to un-XDR NFS requests. In both cases, the code assumes that the data will be aligned on a 32-bit boundary. On the x86, the alignment doesn't matter: you can do 32-bit loads and stores from arbitrary boundaries and the CPU will fake things up for you so that you won't generate an unaligned access trap, though there will be a slight performance penalty. But on other CPUs such as the alpha, SPARC, PPC and (I suspect) the IA-64, unaligned accesses in the kernel generate a fatal trap and a panic. In user space, an unaligned access may result in a bus error, unless the OS is kind enough to handle the trap, which I believe FreeBSD/alpha does. The problem is that the ethernet frame header is only 14 bytes, which means when the chip DMAs to a 32-bit or 64-bit aligned buffer, the payload, which immediately follows the ethernet frame header, ends up on a 16-bit boundary, which is not what we want. You can fix this in one of two ways: if the chip allows it, you can offset the RX buffer address by two bytes and thereby force the payload to be 32-bit aligned, or you can copy the data to a new buffer with the right alignment. Having the chip do it for you is obviously the prefered approach. The chips supported by the fxp, xl, pcn, tl, ste, ti, sk, wx and lge drivers support this. The latter four are all gigE chipsets. Now, before any of you armchair geniuses out there start chiming in with your incredibly brilliant solutions for this problem which you just made up on the spot, forget it. This issue has been discussed to death and there's just no easy way around it. Terry Lambert and Alfred Perlstein, this means you. I mean it. Put down the keyboard and back away from the computer or *blam!* I'll shoot. > Now TX buffers are a problem - I have to take what I get and just > "deal with it". If both start address and length need to be aligned, > then I'm pretty much screwed - I have to copy... Most chips place no restrictions on the alignment of TX buffers. The only exceptions I know of where the chip API simply doesn't permit it are the RealTek 8139/if_rl (surprise) and the VIA Rhine I and Rhine II/if_vr. -Bill ============================================================================= -Bill Paul (925) 691-2800 | Senior Engineer, Master of Unix-Fu wpaul@osd.bsdi.com | Wind River Systems ============================================================================= "I like zees guys. Zey are fonny guys. Just keel one of zem." -- The 3 Amigos ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 16:42:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 3BD8737B40A for ; Mon, 16 Jul 2001 16:42:25 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA86502; Mon, 16 Jul 2001 18:37:29 -0700 (PDT) Date: Mon, 16 Jul 2001 18:37:27 -0700 (PDT) From: Julian Elischer To: Soren Kristensen Cc: Bsdguru@aol.com, hackers@FreeBSD.ORG Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 In-Reply-To: <3B532A40.6BC65369@soekris.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The proble is that teh ethernet header is 14 bytes so you must choose to allighn either the whole packet, or the IP header, but you cannot do both. On Mon, 16 Jul 2001, Soren Kristensen wrote: > Hi, > > Bsdguru@aol.com wrote: > > > > In a message dated 07/16/2001 1:11:09 PM Eastern Daylight Time, > > tlambert2@mindspring.com writes: > > > > > > How do these perform compared to the more expensive gigabit cards? > > > > > > Read the driver. > > > > > > In general, they require an extra copy because of the inability > > > of the card to DMA on a reasonable boundry. > > > > > > Bill's commentary in his drivers is frequently enlightening, > > > and often amusing... 8-). > > > > > > > Maybe at some point he'll "get" that the boundry issue is a pci bus-mastering > > spec issue and not a controller design flaw, as he seems to harp on this in > > just about every driver? > > That's incorrect, there no nothing limiting a PCI device for doing > busmastering on a byte boundary.... The reason why not that many devices > support it, especially on the receive side, is that the circuit gets > more complicated. > > Another thing, since there is all this hardware that requires alignment, > maybe we should consider modifying FreeBSD so receive buffers are > aligned, afaik, Linux use aligned receive buffers.... But I don't know > how complicated that would be, so please don't flame me :-) > > > A more important question is "are these 32-bit cards, and if so, do they have > > enough internal buffer to do sustained 1GB transfers". Generally 32-bit PCI > > is too slow for GB, as it cant do sustained 1GB transfers. Some 32-bit GB > > cards are just a total waste. > > > > > Soren > > 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 Jul 16 16:54:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id 2158137B407; Mon, 16 Jul 2001 16:54:35 -0700 (PDT) (envelope-from rh@matriplex.com) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id QAA40303; Mon, 16 Jul 2001 16:54:33 -0700 (PDT) (envelope-from rh@matriplex.com) Date: Mon, 16 Jul 2001 16:54:32 -0700 (PDT) From: Richard Hodges To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 In-Reply-To: <20010716233436.7C0DB37B407@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 16 Jul 2001, Bill Paul wrote: > > On Mon, 16 Jul 2001, Bill Paul wrote: > > > > > They're "okay." The NatSemi chip has one flaw, which is that RX buffers > > > must be aligned on a 64-bit boundary. None of the more expensive NICs have > > > this restriction. > > > > Go ahead and beat me up if you have to :-) But why is there _any_ issue > > with RX buffer alignment? I get some mbufs and set the data pointer to > > any point I want, or I get a cluster, which is always on a 2k boundary. > > The OS wants the _payload_ to be aligned on a 32-bit boundary. It tries > to do 32-bit accesses to the IP header, and the NFS code also does 32-bit > accesses when trying to un-XDR NFS requests. Oh... I see... I guess you could grab an mbuf and copy just the IP header for that, no? (Just curious at this point :-) > But on other CPUs such as the alpha, SPARC, PPC and (I suspect) the > IA-64, unaligned accesses in the kernel generate a fatal trap and a > panic. In user space, an unaligned access may result in a bus error, > unless the OS is kind enough to handle the trap, which I believe > FreeBSD/alpha does. I don't think that is the case. I seem to remember FreeBSD Alpha 4.3 sysinstall croaking on me once with an alignment error. > Most chips place no restrictions on the alignment of TX buffers. The only > exceptions I know of where the chip API simply doesn't permit it are the > RealTek 8139/if_rl (surprise) and the VIA Rhine I and Rhine II/if_vr. And the IDT 77211 ATM SAR chip. Fortunately, most of the PDUs I see are perfectly aligned, and no copy is needed. Thanks for the explanation! -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. Product Manager | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 17: 9:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 3A9A437B405; Mon, 16 Jul 2001 17:09:48 -0700 (PDT) Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 In-Reply-To: from Richard Hodges at "Jul 16, 2001 04:54:32 pm" To: rh@matriplex.com (Richard Hodges) Date: Mon, 16 Jul 2001 17:09:48 -0700 (PDT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20010717000948.3A9A437B405@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > The OS wants the _payload_ to be aligned on a 32-bit boundary. It tries > > to do 32-bit accesses to the IP header, and the NFS code also does 32-bit > > accesses when trying to un-XDR NFS requests. > > Oh... I see... I guess you could grab an mbuf and copy just the IP > header for that, no? (Just curious at this point :-) That doesn't work for the NFS case: an XDR-encoded packet may contain lots of different fields separated by 32-bit length markers. Also, there's a religious issue, namely a violation of protocol boundaries. This is an ethernet driver: it's not supposed to have any really intimate knowledge of IP or TCP or UDP, so you really don't want to go mucking about with the frame payload if you can avoid it. (Lastly, my goal here is to make the card work, not re-write the innards of the networking stack or NFS. I really don't want intimate knowledge of IP, TCP or UDP either. :) > > But on other CPUs such as the alpha, SPARC, PPC and (I suspect) the > > IA-64, unaligned accesses in the kernel generate a fatal trap and a > > panic. In user space, an unaligned access may result in a bus error, > > unless the OS is kind enough to handle the trap, which I believe > > FreeBSD/alpha does. > > I don't think that is the case. I seem to remember FreeBSD Alpha 4.3 > sysinstall croaking on me once with an alignment error. No no: an unaligned access trap in the kernel is fatal, but an unaligned access trap in a *user-space* process is not. Once in a while you will see messages on the console about unaligned access traps generated by user programs, but these don't panic the system. In the case of FreeBSD/alpha, we fake it up so know about the problem but the process keeps running. Some OSes (e.g. Solaris) clobber the process with a SIGBUS. Some would argue the latter behavior is better since it makes it easier to find and fix what is probably a bug in the first place. -Bill -- ============================================================================= -Bill Paul (925) 691-2800 | Senior Engineer, Master of Unix-Fu wpaul@osd.bsdi.com | Wind River Systems ============================================================================= "I like zees guys. Zey are fonny guys. Just keel one of zem." -- The 3 Amigos ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 17:25:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hades.hell.gr (patr530-b034.otenet.gr [195.167.121.162]) by hub.freebsd.org (Postfix) with ESMTP id 0787237B40E; Mon, 16 Jul 2001 17:25:54 -0700 (PDT) (envelope-from keramida@ceid.upatras.gr) Received: by hades.hell.gr (Postfix, from userid 1001) id 03F052C5; Tue, 17 Jul 2001 01:27:34 +0300 (EEST) Date: Tue, 17 Jul 2001 01:27:34 +0300 From: Giorgos Keramidas To: David O'Brien Cc: Terry Lambert , Wilko Bulte , Jens Schweikhardt , hackers@FreeBSD.ORG Subject: Re: Whitespace at end of line Message-ID: <20010717012733.A589@hades.hell.gr> References: <20010715155941.C1165@schweikhardt.net> <20010715111956.A71874@dragon.nuxi.com> <20010715202505.A94801@freebie.xs4all.nl> <3B53196E.CF1C2110@mindspring.com> <20010716123102.D20942@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010716123102.D20942@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Mon, Jul 16, 2001 at 12:31:02PM -0700 X-PGP-Fingerprint: 3A 75 52 EB F1 58 56 0D - C5 B8 21 B6 1B 5E 4A C2 X-URL: http://students.ceid.upatras.gr/~keramida/index.html Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: David O'Brien Subject: Re: Whitespace at end of line Date: Mon, Jul 16, 2001 at 12:31:02PM -0700 > On Mon, Jul 16, 2001 at 09:42:22AM -0700, Terry Lambert wrote: > > Wilko Bulte wrote: > > > Maybe I'm just plain dim today (I will add a beer to rectify this situation > > > at first convenience..) but what is so bad about some trailing whitespace > > > that a massive commit-a-thlon is called for? > > > > > > just wondering, > > > Wilko > > > > You use emacs, don't you? > > What does vi vs. emacs have to do with it? It's probably one of those rumours that Emacs likes playing smart and $ adding whitespace to the end of wrapped lines. Lies, damn lies. $ $ -giorgos $ $ (a happy emacs user who also feels comfortable with vi, joe, pico, whatever) $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 17:29: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id F300537B403 for ; Mon, 16 Jul 2001 17:29:04 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 74523 invoked by uid 1000); 17 Jul 2001 00:29:03 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Jul 2001 00:29:03 -0000 Date: Mon, 16 Jul 2001 19:29:03 -0500 (CDT) From: Mike Silbersack To: Terry Lambert Cc: Bill Paul , Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 In-Reply-To: <3B53202B.270086D5@mindspring.com> Message-ID: <20010716192714.O74348-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 16 Jul 2001, Terry Lambert wrote: > Mike Silbersack wrote: > > How do these perform compared to the more expensive gigabit cards? > > Read the driver. True, I could've done that, but it would've taken effort. > Bill's commentary in his drivers is frequently enlightening, > and often amusing... 8-). Yeah, I've noticed that in the others. The realtek driver seems to be one of the best. I'm quite looking forward to seeing his comments in that driver book he's working on. ;-) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 17:40:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f78.law11.hotmail.com [64.4.17.78]) by hub.freebsd.org (Postfix) with ESMTP id 63AB737B401 for ; Mon, 16 Jul 2001 17:40:37 -0700 (PDT) (envelope-from part_lion@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 16 Jul 2001 17:40:37 -0700 Received: from 24.130.176.212 by lw11fd.law11.hotmail.msn.com with HTTP; Tue, 17 Jul 2001 00:40:37 GMT X-Originating-IP: [24.130.176.212] From: "Joesh Juphland" To: hackers@freebsd.org Subject: trying to do two pcmcia network cards (ep0 ep1) Date: Mon, 16 Jul 2001 18:40:37 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 17 Jul 2001 00:40:37.0244 (UTC) FILETIME=[18B46BC0:01C10E59] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG /etc/rc.conf looks like this: pccard_enable="YES" pccard_mem="DEFAULT" pccardd_flags=" -i 10 -i 15" removable_interfaces="ep0 ep1" /etc/defaults/pccard.conf has this: io 0x240-0x360 irq 10 15 memory 0xd4000 96k and I added a second config line to the ep0 line like this: config auto "ep" 10 config auto "ep" 15 (the rest of the 3c589 A/B/C/D entry is unchanged) So when I boot with the two 3com cards in the system, only one of them works - it comes up at port 0x240-0x24f irq 10 slot 0. When the second one tries to come up, it says: "No free configuration for card 3com...." Any help is appreciated. I would also like to know what "no free configuration for..." means - does that mean there is no free irq for it ? or something else ? thanks! _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 17:46:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 849E337B406 for ; Mon, 16 Jul 2001 17:46:14 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f6H0j8N33016; Mon, 16 Jul 2001 17:45:08 -0700 (PDT) (envelope-from dillon) Date: Mon, 16 Jul 2001 17:45:08 -0700 (PDT) From: Matt Dillon Message-Id: <200107170045.f6H0j8N33016@earth.backplane.com> To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Weird named problem - IN A for nameservers being lost! References: <5.1.0.14.0.20010622153827.02fa0da0@mail.Go2France.com> <5.1.0.14.0.20010622153827.02fa0da0@mail.Go2France.com> <5.1.0.14.0.20010623185802.04051eb0@mail.Go2France.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've been trying to track down a weird problem with our mail system suddenly believing that a host does not exist, or timing out in DNS. I tracked it down to the DNS server, but I am not entirely sure what is going on. What appears to be happening is that the glue IN A record for the NS server for a domain is getting lost, and the NS record is remaining. When named gets into this state, it doesn't seem to be able to recover... it sees the NS record but it can't resolve it because the glue record is gone, and it doesn't try to get it after that. If you look at the cache dumps and dig output below, you can clearly see the timeout for fuji.jamcracker.com is less then the timeout for jamcracker.com AFTER we've looked up other elements for fuji, which means that when it timed out, that IN A record will be gone. But that IN A record is the IP address for the NS. So when it times out, the jamcracker entry is left there with no NS records whatsoever. I believe what is happening is that something is looking up other records for fuji, and this is replacing the original glue record with the real IN A record, but also changing the timeouts somehow and causing fuji's record to timeout early. As far as I can tell, this is an extremely serious bug in named. I am running 8.2.3. This has occured with several mail destinations, not just jamcracker. I went through jamcrackers whole DNS hierarchy and everything is setup properly, including all the timeouts (they are all set to 3600 seconds). Has anyone else seen this? Anyone know what is going on here? -Matt --- Here is a cache dump of a case where 'nslookup -query=mx jamcracker.com' no longer works. Everything with jamcracker in it is being dumped: jamcracker 2436 IN SOA fuji.jamcracker.com. hostmaster.jamcracker.com. ( 2001062900 10800 3600 1728000 3600 ) ;Cr=auth [216.32.126.150] ; 2436 IN AAAA fuji.jamcracker.com. hostmaster.jamcracker.com. ( ; 2001062900 10800 3600 1728000 3600 );jamcracker.com.;NODATA ;-$ ;Cr=auth [216.32.126.150] 2436 IN NS fuji.jamcracker.com. ;Cr=auth [216.32.126.150] 2436 IN A 66.35.217.100 ;Cr=auth [216.32.126.150] And here is a cache dump after I restart named and do the same nslookup: jamcracker 3591 IN NS fuji.jamcracker.com. ;Cr=auth [216.32.126.150] 3591 IN MX 5 va2mc.ummailbox.net. ;Cr=auth [216.32.126.150] $ORIGIN jamcracker.com. fuji 3591 IN A 66.35.220.151 ;Cr=addtnl [216.32.126.150] And here is a dump after named has been running a while: jamcracker 2016 IN NS fuji.jamcracker.com. ;Cr=auth [216.32.126.150] 2016 IN MX 5 va2mc.ummailbox.net. ;Cr=auth [216.32.126.150] 2206 IN SOA fuji.jamcracker.com. hostmaster.jamcracker.com. ( 2001062900 10800 3600 1728000 3600 ) ;Cr=auth [66.35.220.151] ; 2206 IN AAAA fuji.jamcracker.com. hostmaster.jamcracker.com. ( ; 2001062900 10800 3600 1728000 3600 );jamcracker.com.;NODATA ;-$ ;Cr=auth [66.35.220.151] 3140 IN A 66.35.217.100 ;Cr=auth [66.35.220.151] $ORIGIN jamcracker.com. fuji 1846 IN A 66.35.220.151 ;NT=13 Cr=addtnl [216.32.126.150] ; 2213 IN AAAA fuji.jamcracker.com. hostmaster.jamcracker.com. ( ; 2001062900 10800 3600 1728000 3600 );jamcracker.com.;NODATA ;-$ ; And here is the dig output. earth:/etc/namedb# dig jamcracker.com ; <<>> DiG 8.3 <<>> jamcracker.com ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1 ;; QUERY SECTION: ;; jamcracker.com, type = A, class = IN ;; ANSWER SECTION: jamcracker.com. 50m27s IN A 66.35.217.100 ;; AUTHORITY SECTION: jamcracker.com. 31m43s IN NS fuji.jamcracker.com. ;; ADDITIONAL SECTION: fuji.jamcracker.com. 28m53s IN A 66.35.220.151 ;; Total query time: 1 msec ;; FROM: earth.backplane.com to SERVER: default -- 127.0.0.1 ;; WHEN: Mon Jul 16 17:36:13 2001 ;; MSG SIZE sent: 32 rcvd: 83 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 17:54:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wilma.widomaker.com (wilma.widomaker.com [204.17.220.5]) by hub.freebsd.org (Postfix) with ESMTP id 0171037B40C for ; Mon, 16 Jul 2001 17:54:26 -0700 (PDT) (envelope-from shannon@daydream.shannon.net) Received: from [209.96.179.158] (helo=escape.shannon.net) by wilma.widomaker.com with esmtp (Exim 3.22 #2) id 15MJ84-0007W4-00 for freebsd-hackers@freebsd.org; Mon, 16 Jul 2001 20:54:25 -0400 Received: from daydream (daydream.shannon.net [192.168.1.10]) by escape.shannon.net (8.11.0/8.8.8) with ESMTP id f6H0Ree28232 for ; Mon, 16 Jul 2001 20:27:40 -0400 (EDT) Received: from shannon by daydream with local (Exim 3.12 #1 (Debian)) id 15MIiC-0002EX-00 for ; Mon, 16 Jul 2001 20:27:40 -0400 Date: Mon, 16 Jul 2001 20:27:40 -0400 From: Charles Shannon Hendrix To: freebsd-hackers@freebsd.org Subject: Re: Whitespace at end of line Message-ID: <20010716202739.B8491@widomaker.com> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20010715155941.C1165@schweikhardt.net> <20010715111956.A71874@dragon.nuxi.com> <20010715202505.A94801@freebie.xs4all.nl> <3B53196E.CF1C2110@mindspring.com> <20010716123102.D20942@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010716123102.D20942@dragon.nuxi.com> User-Agent: Mutt/1.3.18i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 16, 2001 at 12:31:02PM -0700, David O'Brien wrote: > On Mon, Jul 16, 2001 at 09:42:22AM -0700, Terry Lambert wrote: > > Wilko Bulte wrote: > > > Maybe I'm just plain dim today (I will add a beer to rectify this > > > situation at first convenience..) but what is so bad about some trailing > > > whitespace that a massive commit-a-thlon is called for? > > > > > > just wondering, > > > Wilko > > > > You use emacs, don't you? > > What does vi vs. emacs have to do with it? The beer. -- "Castles are sacked in war, Chieftains are scattered far, Truth is a fixed star, Eileen aroon!" -- Gerald Griffin ______________________________________________________________________ Charles Shannon Hendrix s h a n n o n @ w i d o m a k e r . c o m To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 17:58: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 4297C37B408 for ; Mon, 16 Jul 2001 17:57:59 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 82830 invoked by uid 1000); 17 Jul 2001 00:57:57 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Jul 2001 00:57:57 -0000 Date: Mon, 16 Jul 2001 19:57:57 -0500 (CDT) From: Mike Silbersack To: Matt Dillon Cc: Len Conrad , Subject: Re: Weird named problem - IN A for nameservers being lost! In-Reply-To: <200107170045.f6H0j8N33016@earth.backplane.com> Message-ID: <20010716195409.U74787-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 16 Jul 2001, Matt Dillon wrote: > I've been trying to track down a weird problem with our mail system > suddenly believing that a host does not exist, or timing out in DNS. > > I tracked it down to the DNS server, but I am not entirely sure what is > going on. What appears to be happening is that the glue IN A record > for the NS server for a domain is getting lost, and the NS record is > remaining. When named gets into this state, it doesn't seem to be able > to recover... it sees the NS record but it can't resolve it because > the glue record is gone, and it doesn't try to get it after that. This looks like a problem brought up on the djbdns mailing list a long while ago. When the NS records listed with the roots and the NS records returned by the NSes don't match (or share any NSes whatsoever, for that matter), BIND breaks as you've described. The resolution, as I recall, was "don't do that!" Bind 9 might handle the case correctly, as might djbdns. In any case, the admins of jamcracker.com should be synchronizing their NS listings. Here's how it is now: > dig jamcracker.com NS ; <<>> DiG 8.3 <<>> jamcracker.com NS ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2 ;; QUERY SECTION: ;; jamcracker.com, type = NS, class = IN ;; ANSWER SECTION: jamcracker.com. 2D IN NS SCA03.SEC.DNS.EXODUS.NET. jamcracker.com. 2D IN NS SCA02.SEC.DNS.EXODUS.NET. > dig jamcracker.com NS @sca03.sec.dns.exodus.net ; <<>> DiG 8.3 <<>> jamcracker.com NS @sca03.sec.dns.exodus.net ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; QUERY SECTION: ;; jamcracker.com, type = NS, class = IN ;; ANSWER SECTION: jamcracker.com. 1H IN NS fuji.jamcracker.com. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 18:14:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 9A1B437B401 for ; Mon, 16 Jul 2001 18:14:09 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f6H1E5P33636; Mon, 16 Jul 2001 18:14:05 -0700 (PDT) (envelope-from dillon) Date: Mon, 16 Jul 2001 18:14:05 -0700 (PDT) From: Matt Dillon Message-Id: <200107170114.f6H1E5P33636@earth.backplane.com> To: Mike Silbersack Cc: Len Conrad , Subject: Re: Weird named problem - IN A for nameservers being lost! References: <20010716195409.U74787-100000@achilles.silby.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : : :On Mon, 16 Jul 2001, Matt Dillon wrote: : :> I've been trying to track down a weird problem with our mail system :> suddenly believing that a host does not exist, or timing out in DNS. :> :> I tracked it down to the DNS server, but I am not entirely sure what is :> going on. What appears to be happening is that the glue IN A record :> for the NS server for a domain is getting lost, and the NS record is :> remaining. When named gets into this state, it doesn't seem to be able :> to recover... it sees the NS record but it can't resolve it because :> the glue record is gone, and it doesn't try to get it after that. : :This looks like a problem brought up on the djbdns mailing list a long :while ago. When the NS records listed with the roots and the NS records :returned by the NSes don't match (or share any NSes whatsoever, for that :matter), BIND breaks as you've described. : :The resolution, as I recall, was "don't do that!" Bind 9 might handle the :case correctly, as might djbdns. In any case, the admins of :jamcracker.com should be synchronizing their NS listings. : :Here's how it is now: I don't think that's it... if you look at the dumps, there were no timeouts in the 2-day range. The original glue NS records (from exodus) had already been completely replaced by the NS record from their zone. Everything in their zones is already synchronized. -Matt :> dig jamcracker.com NS : :; <<>> DiG 8.3 <<>> jamcracker.com NS :;; res options: init recurs defnam dnsrch :;; got answer: :;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 :;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2 :;; QUERY SECTION: :;; jamcracker.com, type = NS, class = IN : :;; ANSWER SECTION: :jamcracker.com. 2D IN NS SCA03.SEC.DNS.EXODUS.NET. :jamcracker.com. 2D IN NS SCA02.SEC.DNS.EXODUS.NET. : :> dig jamcracker.com NS @sca03.sec.dns.exodus.net : :; <<>> DiG 8.3 <<>> jamcracker.com NS @sca03.sec.dns.exodus.net :; (1 server found) :;; res options: init recurs defnam dnsrch :;; got answer: :;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 :;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 :;; QUERY SECTION: :;; jamcracker.com, type = NS, class = IN : :;; ANSWER SECTION: :jamcracker.com. 1H IN NS fuji.jamcracker.com. : :Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 18:14:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 5D65137B403 for ; Mon, 16 Jul 2001 18:14:36 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA21847; Mon, 16 Jul 2001 21:14:34 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f6H1E5713549; Mon, 16 Jul 2001 21:14:05 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15187.37213.737818.957614@grasshopper.cs.duke.edu> Date: Mon, 16 Jul 2001 21:14:05 -0400 (EDT) To: Bsdguru@aol.com Cc: hackers@freebsd.org Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 In-Reply-To: <3d.e7348af.2884818f@aol.com> References: <3d.e7348af.2884818f@aol.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bsdguru@aol.com writes: > A more important question is "are these 32-bit cards, and if so, do they have > enough internal buffer to do sustained 1GB transfers". Generally 32-bit PCI > is too slow for GB, as it cant do sustained 1GB transfers. Some 32-bit GB > cards are just a total waste. The two cards that I have experience with are the Netgear GA622T and SMC9462TX. Both are 64-bit/66MHz cards. The first nge cards we tried were a pair of Netgear GA622T boards. They leave a lot to be desired. We put them in our Dell PowerEdge 4400 boxes (Serverworks chipset with interleaved ram and 64-bit/66MHz PCI, 733MHz Xeon) & hooked them up through our Extreme Summit 7i Gigabit switch (Copper). They have a decent packets/second rate for minimally sized packets (155,000 packets/sec or so), but they have serious trouble filling the link with UDP packets -- even with jumbo frames, I can't seem to push more than 450Mb/sec out of them. At this point, we figured the NatSemi DP8382x was just a lousy chipset, so we ordered a pair of SMC9462TX boards. Based on comments which used to be in the lge driver, we assumed that they used the Level 1 LXT1001 chips. However, we found out that the SMC9462TX boards that we have use the NatSemi DP8382x. (Perhaps the SMC9462SX uses the LXT1001?) We were pleasantly surprised to learn that the nge based SMC boards do perform well. Using the same hosts & switch as above, we can nearly fill the link with 1500 byte packets (950Mb/sec, I think). And they can also sustain more than 155,000 minimally sized packets/sec. They can easily fill the link with jumbo frames, but then there's that 8k tx fifo checksum limitation. Hope this helps, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 18:26:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4E3AF37B40A; Mon, 16 Jul 2001 18:21:08 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA21967; Mon, 16 Jul 2001 21:20:30 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f6H1K1H13673; Mon, 16 Jul 2001 21:20:01 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15187.37568.940540.297591@grasshopper.cs.duke.edu> Date: Mon, 16 Jul 2001 21:20:00 -0400 (EDT) To: wpaul@freebsd.org (Bill Paul) Cc: rh@matriplex.com (Richard Hodges), hackers@freebsd.org Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 In-Reply-To: <20010717000948.3A9A437B405@hub.freebsd.org> References: <20010717000948.3A9A437B405@hub.freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill Paul writes: > by user programs, but these don't panic the system. In the case of > FreeBSD/alpha, we fake it up so know about the problem but the process > keeps running. Some OSes (e.g. Solaris) clobber the process with a > SIGBUS. Some would argue the latter behavior is better since it makes > it easier to find and fix what is probably a bug in the first place. Actually, you can control this behaviour with the uac (1) command on FreeBSD/alpha. 'uac -s' causes unaligned access errors to result in a SIGBUS being delivered to the parent and its future descendants. You can also enable/disable printing of errors, etc. Really handy when you're using a ghostscript not built w/Compaq C. Also, Tru64 has a similar command with the same name and different syntax. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 18:32:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id E210537B42B for ; Mon, 16 Jul 2001 18:30:04 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 23813 invoked by uid 1000); 17 Jul 2001 01:29:13 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Jul 2001 01:29:13 -0000 Date: Mon, 16 Jul 2001 20:29:13 -0500 (CDT) From: Mike Silbersack To: Matt Dillon Cc: Len Conrad , Subject: Re: Weird named problem - IN A for nameservers being lost! In-Reply-To: <200107170114.f6H1E5P33636@earth.backplane.com> Message-ID: <20010716201723.P74787-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 16 Jul 2001, Matt Dillon wrote: > I don't think that's it... if you look at the dumps, there were no timeouts > in the 2-day range. The original glue NS records (from exodus) had already > been completely replaced by the NS record from their zone. Everything in > their zones is already synchronized. > > -Matt If I recall correctly, what you're describing above *causes* the problem. Their NSes have to be synced with the roots. I tried searching the archives, and I can't find the messages talking about the topic. I did find djb's page with his rants about dns breakages, and at the end of one he mentions: "Beware that, because of the ``credibility'' rules described above, the NS records from the child servers must include the NS records from the parent. Otherwise an attacker can break BIND's access to the child servers." This is from: http://cr.yp.to/djbdns/notes.html So, there's something to it, though I no longer remember exactly why. Read through that page, he seems to be trying to explain the problem. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 19:21:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 2780A37B405 for ; Mon, 16 Jul 2001 19:21:47 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f6H2Lcj36277; Mon, 16 Jul 2001 19:21:38 -0700 (PDT) (envelope-from dillon) Date: Mon, 16 Jul 2001 19:21:38 -0700 (PDT) From: Matt Dillon Message-Id: <200107170221.f6H2Lcj36277@earth.backplane.com> To: Mike Silbersack Cc: Len Conrad , Subject: Re: Weird named problem - IN A for nameservers being lost! References: <20010716201723.P74787-100000@achilles.silby.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : : :On Mon, 16 Jul 2001, Matt Dillon wrote: : :> I don't think that's it... if you look at the dumps, there were no timeouts :> in the 2-day range. The original glue NS records (from exodus) had already :> been completely replaced by the NS record from their zone. Everything in :> their zones is already synchronized. :> :> -Matt : :If I recall correctly, what you're describing above *causes* the problem. :Their NSes have to be synced with the roots. : :I tried searching the archives, and I can't find the messages talking :about the topic. I did find djb's page with his rants about dns :breakages, and at the end of one he mentions: : :"Beware that, because of the ``credibility'' rules described above, the NS :records from the child servers must include the NS records from the :parent. Otherwise an attacker can break BIND's access to the child :servers." : :This is from: http://cr.yp.to/djbdns/notes.html : :So, there's something to it, though I no longer remember exactly why. :Read through that page, he seems to be trying to explain the problem. : :Mike "Silby" Silbersack Interesting. He describes in the section about 'expiring glue' creating loops in the DNS server, but doesn't mention a particular bug. However, there's another section where he mentions something about bind reducing the TTL by 5% for certain credibility cases. Going back to my original posting... the NS is 2016 and fuji is 1846 = 170 = 5%. I think This credibility stuff reducing the TTL in named is responsible for these blowups. I am going to email the bind group with this whole mess to see what they have to say. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 20: 1:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 8E0A537B401 for ; Mon, 16 Jul 2001 19:58:40 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 429 invoked by uid 1000); 17 Jul 2001 02:58:38 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Jul 2001 02:58:38 -0000 Date: Mon, 16 Jul 2001 21:58:38 -0500 (CDT) From: Mike Silbersack To: Matt Dillon Cc: Len Conrad , Subject: Re: Weird named problem - IN A for nameservers being lost! In-Reply-To: <200107170221.f6H2Lcj36277@earth.backplane.com> Message-ID: <20010716215231.T417-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 16 Jul 2001, Matt Dillon wrote: > Interesting. He describes in the section about 'expiring glue' > creating loops in the DNS server, but doesn't mention a particular > bug. > > However, there's another section where he mentions something about > bind reducing the TTL by 5% for certain credibility cases. > > Going back to my original posting... the NS is 2016 and fuji > is 1846 = 170 = 5%. > > I think This credibility stuff reducing the TTL in named is > responsible for these blowups. I am going to email the bind group > with this whole mess to see what they have to say. > > -Matt I wish you luck in getting it fixed. That 5% may have been intended for removal; 8.1.2 used to reduce the TTL by 5% for _each_ query. That was clearly removed for 8.2, but perhaps the initial decrement was forgotten. However, the problem probably indicates a more serious problem in 8.x's resolver, which may be fixed in 9 and is not intended to be backported. I guess Mark'll have to answer that. (He seems to read and reply to -security, so he appears reachable.) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 20: 3:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp-out.hamburg.pop.de (smtp-out.hamburg.pop.de [195.222.210.86]) by hub.freebsd.org (Postfix) with ESMTP id 779F237B411 for ; Mon, 16 Jul 2001 20:01:52 -0700 (PDT) (envelope-from ) Received: from mail.hamburg.pop.de ([193.98.9.7] helo=mail.provi.de) by smtp-out.hamburg.pop.de with esmtp (Exim 3.22 #1) id 15ML8C-0005Cz-00 for hackers@freebsd.org; Tue, 17 Jul 2001 05:02:40 +0200 Received: from daemon by mail.provi.de with local (Exim 3.20 #2) id 15ML7P-00070X-00 for hackers@FreeBSD.ORG; Tue, 17 Jul 2001 05:01:51 +0200 From: To: Subject: mail failed, returning to sender X-No-Resend: True Message-Id: Date: Tue, 17 Jul 2001 05:01:51 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG |------------------------- Message log follows: -----------------------| | no valid recipients were found for this message | |----------------------------------------------------------------------| | t.schmeissel@mail.hh.provi.de - unknown user |----------------------------------------------------------------------| German translation: Sie haben Ihre eMail an die Adresse "t.schmeissel@mail.hh.provi.de" gerichtet. Der hintere Teil der Adresse ("Domain"), "@mail.hh.provi.de", ist gueltig, der Benutzernamen jedoch nicht. Ueberpruefen Sie bitte insbesondere diesen Teil der eMail-Adresse! Sie erhalten im Anhang die ersten zehn Zeilen Ihrer Original-eMail zurueck. Mit freundlichen Gruessen, Point of Presence GmbH, Hamburg ------------------------------------------------------------------------ From owner-freebsd-hackers-digest@freebsd.org Tue Jul 17 05:01:51 2001 Return-path: Envelope-to: t.schmeissel@mail.hh.provi.de Delivery-date: Tue, 17 Jul 2001 05:01:51 +0200 Received: from mx2.freebsd.org ([216.136.204.119]) by mail.provi.de with smtp (Exim 3.20 #2) id 15ML7O-00070G-00 for t.schmeissel@mail.hh.provi.de; Tue, 17 Jul 2001 05:01:50 +0200 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 84C0055DB9; Mon, 16 Jul 2001 20:01:31 -0700 (PDT) (envelope-from owner-freebsd-hackers-digest@FreeBSD.ORG) Received: by hub.freebsd.org (Postfix, from userid 538) id AA8F437B411; Mon, 16 Jul 2001 20:01:30 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with SMTP id 8EF8E2E8039; Mon, 16 Jul 2001 20:01:30 -0700 (PDT) (envelope-from owner-freebsd-hackers-digest) Received: by hub.freebsd.org (bulk_mailer v1.12); Mon, 16 Jul 2001 20:01:30 -0700 From: owner-freebsd-hackers-digest@FreeBSD.ORG (freebsd-hackers-digest) To: freebsd-hackers-digest@FreeBSD.ORG Subject: freebsd-hackers-digest V5 #182 Reply-To: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers-digest@FreeBSD.ORG Precedence: bulk Message-ID: Date: Mon, 16 Jul 2001 20:01:30 -0700 (PDT) freebsd-hackers-digest Monday, July 16 2001 Volume 05 : Number 182 In this issue: mail failed, returning to sender Re: Whitespace at end of line Re: DDB & mp3's Re: eXperimental bandwidth delay product code (was Re: Network performance tuning.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 21:31:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hall.mail.mindspring.net (hall.mail.mindspring.net [207.69.200.60]) by hub.freebsd.org (Postfix) with ESMTP id 0157D37B403 for ; Mon, 16 Jul 2001 21:31:13 -0700 (PDT) (envelope-from panis@mindspring.com) Received: from smui00.slb.mindspring.net (smui00.slb.mindspring.net [199.174.114.20]) by hall.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id AAA11807 for ; Tue, 17 Jul 2001 00:31:13 -0400 (EDT) From: panis@mindspring.com Received: by smui00.slb.mindspring.net id AAA0000025423; Tue, 17 Jul 2001 00:31:13 -0400 (EDT) Date: Tue, 17 Jul 2001 00:31:12 -0400 To: freebsd-hackers@freebsd.org Message-ID: X-Originating-IP: 165.247.19.97 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG auth a170165f subscribe freebsd-hackers panis@mindspring.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 21:45:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id EDD9A37B405; Mon, 16 Jul 2001 21:45:39 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f6H4jVE37861; Mon, 16 Jul 2001 21:45:31 -0700 (PDT) (envelope-from dillon) Date: Mon, 16 Jul 2001 21:45:31 -0700 (PDT) From: Matt Dillon Message-Id: <200107170445.f6H4jVE37861@earth.backplane.com> To: Mike Silbersack Cc: Len Conrad , dougb@freebsd.org, Subject: Re: Weird named problem - IN A for nameservers being lost! References: <20010716215231.T417-100000@achilles.silby.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :... :> Interesting. He describes in the section about 'expiring glue' :> creating loops in the DNS server, but doesn't mention a particular :> bug. :> :> However, there's another section where he mentions something about :> bind reducing the TTL by 5% for certain credibility cases. :> :> Going back to my original posting... the NS is 2016 and fuji :> is 1846 = 170 = 5%. :> :> I think This credibility stuff reducing the TTL in named is :> responsible for these blowups. I am going to email the bind group :> with this whole mess to see what they have to say. :> :> -Matt : :I wish you luck in getting it fixed. That 5% may have been intended for :removal; 8.1.2 used to reduce the TTL by 5% for _each_ query. That was :clearly removed for 8.2, but perhaps the initial decrement was forgotten. : :However, the problem probably indicates a more serious problem in 8.x's :resolver, which may be fixed in 9 and is not intended to be backported. I :guess Mark'll have to answer that. (He seems to read and reply to :-security, so he appears reachable.) : :Mike "Silby" Silbersack I submitted a bug report. Mark and I are talking about it. Basically what it comes down to is that the 5% code is still there, but conditionalized with NOADDITIONAL. That is, if you set NOADDITIONAL then the 5% code is ripped out. I also took a look on Google. The problem appears to be well known for a long time, I just don't know why the bind guys haven't ripped out this 5% code stuff. I am going to commit a change to /usr/src/usr.sbin/named/Makefile.inc (in -current and MFC to -stable 3 days later) that turns on NOADDITIONAL and effectively fixes this problem for 8.2.x. Hopefully the bind guys will rip out the code entirely, it just doesn't belong there. I mean, it's ok for bind to fail instantly, or to allow the case, but it isn't ok for bind to allow the case 40 minutes and then fail from that point on until it's restarted. Judging from the Google, this has been the source of many, many problems, and I don't quite understand why it wasn't ripped out last year. I am also CCing Doug Barton, who appears to be responsible for bind8 in ports. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 23:15:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from saturn.cs.uml.edu (saturn.cs.uml.edu [129.63.8.2]) by hub.freebsd.org (Postfix) with ESMTP id 675B537B406 for ; Mon, 16 Jul 2001 23:15:31 -0700 (PDT) (envelope-from acahalan@saturn.cs.uml.edu) Received: (from acahalan@localhost) by saturn.cs.uml.edu (8.11.0/8.11.2) id f6H6FU5376195; Tue, 17 Jul 2001 02:15:30 -0400 (EDT) Date: Tue, 17 Jul 2001 02:15:30 -0400 (EDT) Message-Id: <200107170615.f6H6FU5376195@saturn.cs.uml.edu> From: "Albert D. Cahalan" To: freebsd-hackers@FreeBSD.ORG Cc: Jim.Pirzyk@disney.com, tlambert2@mindspring.com Subject: Re: math library difference between linux emulation and native freebsd (and native linux) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert writes: > Jim.Pirzyk@disney.com wrote: >> There are only two shared libaries in common (libc and libm) and >> both are the same on FreeBSD (in /compat/linux) and Linux. >> >> So any ideas on where the program is going wrong? > > man fpsetround That won't change a thing. Both systems round to nearest. > The defaults for the Linux emulator are different than > the defaults for Linux. Linux sets some stuff up wrong, FreeBSD sets stuff up wrong. This is a choice between bad and worse, since the CPU does not support what you want. An x86 CPU has a rounding precision that may be set for float, double, or long double. FreeBSD sets the CPU to make double work, giving extra fraction bits for float and truncating long double. Linux sets the CPU to make long double work, giving extra fraction bits for both float and long double. Now what is worse, getting some extra bits in an intermediate calculation or truncation? Note that the FreeBSD setting causes _both_ problems. See float_t, double_t, FLT_EVAL_METHOD and FLT_ROUNDS in the 1999 C standard for ways to deal with x86 hardware. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 16 23:47:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from xfreek.mindriot.net (24-168-212-220.he.cox.rr.com [24.168.212.220]) by hub.freebsd.org (Postfix) with SMTP id 2C6ED37B407 for ; Mon, 16 Jul 2001 23:47:23 -0700 (PDT) (envelope-from rootx11@xfreek.mindriot.net) Received: (qmail 1554 invoked by uid 1001); 17 Jul 2001 01:52:34 -0000 Date: 17 Jul 2001 01:52:34 -0000 Message-ID: <20010717015234.1553.qmail@xfreek.mindriot.net> From: rootx11@xfreek.mindriot.net To: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello. I am reading TCP/IP Illustrated and it is making references to variables in the BSD4.4 code. I would like to use these same variables, specifically the variable ifnet, which was declared in BSD4.4 as a struct ifnet *ifnet, according to TCP/IP Illustrated. The name of the variable has changed, i think and do not know how to figure out what the new name is. Is there any way I could figure out? For anyone who has TCP/IP Illustrated, on page 64 it makes references to ifnet in the second table half way down. Please reply to rootx11@xfreek.mindriot.net Thanks you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 0: 5:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from orotal.panku.pc.ashlandfiber.net (063-151-110-116.pc.ashlandfiber.net [63.151.110.116]) by hub.freebsd.org (Postfix) with ESMTP id EE04337B409 for ; Tue, 17 Jul 2001 00:05:23 -0700 (PDT) (envelope-from louisk@bend.com) Received: (from louisk@localhost) by orotal.panku.pc.ashlandfiber.net (8.11.2/8.11.2) id f6H74lF02781; Tue, 17 Jul 2001 00:04:47 -0700 X-Authentication-Warning: orotal.panku.pc.ashlandfiber.net: louisk set sender to louisk@bend.com using -f Subject: From: Louis Kowolowski To: freebsd-hackers@freebsd.org Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 17 Jul 2001 00:04:47 -0700 Message-Id: <995353487.2709.0.camel@orotal> Mime-Version: 1.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 0:49: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail11.sdc1.sfba.home.com (femail11.sdc1.sfba.home.com [24.0.95.107]) by hub.freebsd.org (Postfix) with ESMTP id 3642537B401 for ; Tue, 17 Jul 2001 00:48:56 -0700 (PDT) (envelope-from btdang@home.com) Received: from home.com ([24.248.85.196]) by femail11.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010717074855.UPKA18785.femail11.sdc1.sfba.home.com@home.com>; Tue, 17 Jul 2001 00:48:55 -0700 Message-ID: <3B53EF21.7B387962@home.com> Date: Tue, 17 Jul 2001 00:54:09 -0700 From: Bruce Dang Organization: Boys & Girls Clubs X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: rootx11@xfreek.mindriot.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: References: <20010717015234.1553.qmail@xfreek.mindriot.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG look in /usr/include/net/if_var.h rootx11@xfreek.mindriot.net wrote: > > Hello. > I am reading TCP/IP Illustrated and it is making references to variables in > the BSD4.4 code. I would like to use these same variables, specifically the > variable ifnet, which was declared in BSD4.4 as a struct ifnet *ifnet, > according to TCP/IP Illustrated. The name of the variable has changed, i think > and do not know how to figure out what the new name is. Is there any way I > could figure out? For anyone who has TCP/IP Illustrated, on page 64 it makes > references to ifnet in the second table half way down. Please reply to > rootx11@xfreek.mindriot.net > Thanks you. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 1:11:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id 4161B37B405 for ; Tue, 17 Jul 2001 01:11:28 -0700 (PDT) (envelope-from vel@bugz.infotecs.ru) Received: (from vel@localhost) by bugz.infotecs.ru (8.11.1/8.11.1) id f6H8QMN00466 for freebsd-hackers@freebsd.org; Tue, 17 Jul 2001 12:26:22 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200107170826.f6H8QMN00466@bugz.infotecs.ru> Subject: disabling reboot on kernel panic To: freebsd-hackers@freebsd.org Date: Tue, 17 Jul 2001 12:26:22 +0400 (MSD) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, maybe it's a bit offtopic, but still: how can I disable reboot on kernel panic in 15 seconds, so that it just hangs and I'm able to see what happened when I come ? Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 1:22:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 537C537B403 for ; Tue, 17 Jul 2001 01:22:13 -0700 (PDT) (envelope-from brandt@fokus.gmd.de) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id KAA08234 for ; Tue, 17 Jul 2001 10:22:11 +0200 (MET DST) Date: Tue, 17 Jul 2001 10:22:11 +0200 (CEST) From: Harti Brandt To: Subject: Really simple patch... Message-ID: <20010717101638.V11504-100000@beagle.fokus.gmd.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Could please somebody make this little, trivial and obviuos patch, I requested it a while ago, or should I make a PR for it?? Hi, ()s are missing around the macro argument in cv_waitq_empty. The call if(!(cv_waitq_empty(&sc->foo_cv))) ... will otherwise fail to compile. harti Index: condvar.h =================================================================== RCS file: /usr/ncvs/src/sys/sys/condvar.h,v retrieving revision 1.2 diff -r1.2 condvar.h 66c66 < #define cv_waitq_empty(cvp) (TAILQ_EMPTY(&cvp->cv_waitq)) --- > #define cv_waitq_empty(cvp) (TAILQ_EMPTY(&(cvp)->cv_waitq)) -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 1:25:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 4B62637B415 for ; Tue, 17 Jul 2001 01:25:32 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f6H8PBn94592; Tue, 17 Jul 2001 10:25:11 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Harti Brandt Cc: hackers@FreeBSD.ORG Subject: Re: Really simple patch... In-Reply-To: Your message of "Tue, 17 Jul 2001 10:22:11 +0200." <20010717101638.V11504-100000@beagle.fokus.gmd.de> Date: Tue, 17 Jul 2001 10:25:11 +0200 Message-ID: <94590.995358311@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG fixed. In message <20010717101638.V11504-100000@beagle.fokus.gmd.de>, Harti Brandt writes: > >Could please somebody make this little, trivial and obviuos patch, I >requested it a while ago, or should I make a PR for it?? > >Hi, > >()s are missing around the macro argument in cv_waitq_empty. The call > > if(!(cv_waitq_empty(&sc->foo_cv))) > ... > >will otherwise fail to compile. > >harti > >Index: condvar.h >=================================================================== >RCS file: /usr/ncvs/src/sys/sys/condvar.h,v >retrieving revision 1.2 >diff -r1.2 condvar.h >66c66 >< #define cv_waitq_empty(cvp) (TAILQ_EMPTY(&cvp->cv_waitq)) >--- >> #define cv_waitq_empty(cvp) (TAILQ_EMPTY(&(cvp)->cv_waitq)) > > >-- >harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private > brandt@fokus.gmd.de, harti@begemot.org > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 1:27:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id DA63337B405 for ; Tue, 17 Jul 2001 01:27:07 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f6H8R6V00545; Tue, 17 Jul 2001 10:27:06 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f6H8S1J03906; Tue, 17 Jul 2001 10:28:01 +0200 (CEST) Date: Tue, 17 Jul 2001 10:28:01 +0200 From: Bernd Walter To: "Eugene L. Vorokov" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: disabling reboot on kernel panic Message-ID: <20010717102800.A3843@cicely20.cicely.de> References: <200107170826.f6H8QMN00466@bugz.infotecs.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107170826.f6H8QMN00466@bugz.infotecs.ru>; from vel@bugz.infotecs.ru on Tue, Jul 17, 2001 at 12:26:22PM +0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jul 17, 2001 at 12:26:22PM +0400, Eugene L. Vorokov wrote: > Hello, > > maybe it's a bit offtopic, but still: how can I disable reboot on kernel > panic in 15 seconds, so that it just hangs and I'm able to see what > happened when I come ? compile with DDB or if you enable crashdumps in rc.conf you will have the reason for crashing in the dump while the machine still reboots. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 1:31:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 7C62237B403; Tue, 17 Jul 2001 01:31:51 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f6H8VnV00573; Tue, 17 Jul 2001 10:31:49 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f6H8WkE03915; Tue, 17 Jul 2001 10:32:46 +0200 (CEST) Date: Tue, 17 Jul 2001 10:32:45 +0200 From: Bernd Walter To: Dan Cc: John Baldwin , freebsd-hackers@FreeBSD.ORG Subject: Re: pagedaemon + vmdaemon Message-ID: <20010717103245.B3843@cicely20.cicely.de> References: <20010716163402.D48387-100000@gandalf.bravenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010716163402.D48387-100000@gandalf.bravenet.com>; from dphoenix@bravenet.com on Mon, Jul 16, 2001 at 04:34:52PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 16, 2001 at 04:34:52PM -0700, Dan wrote: > > ya it seems it is running into swap abit..... > hmmm watching apache with truss i see alot of error #35's > in the sys calls....what is that related to again? /usr/include/errno.h says: #define EAGAIN 35 /* Resource temporarily unavailable */ It is quite normal in some programdesigns. What you are looking for is either someone whoe sells you ram or find something that is missusing ram. Maybe you have enabled to much httpd processes in the config or some ugly (cgi/php) script running. We once had an customer which was using php and on starting of the script he initialised a very big bunch of tables... -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 2:28:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id EC90D37B405 for ; Tue, 17 Jul 2001 02:28:07 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id 4E1B43E28; Tue, 17 Jul 2001 02:28:07 -0700 (PDT) To: "Eugene L. Vorokov" Cc: freebsd-hackers@freebsd.org Subject: Re: disabling reboot on kernel panic In-Reply-To: <200107170826.f6H8QMN00466@bugz.infotecs.ru>; from vel@bugz.infotecs.ru on "Tue, 17 Jul 2001 12:26:22 +0400 (MSD)" Date: Tue, 17 Jul 2001 02:28:07 -0700 From: Dima Dorfman Message-Id: <20010717092807.4E1B43E28@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Eugene L. Vorokov" writes: > Hello, > > maybe it's a bit offtopic, but still: how can I disable reboot on kernel > panic in 15 seconds, so that it just hangs and I'm able to see what > happened when I come ? Set PANIC_REBOOT_WAIT_TIME to -1. > > Regards, > Eugene > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 3:23:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 31E2E37B401 for ; Tue, 17 Jul 2001 03:23:42 -0700 (PDT) (envelope-from LConrad@Go2France.com) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id A4E2816B20 for ; Tue, 17 Jul 2001 12:23:34 +0200 (CEST) Received: from IBM-HIRXKN66F0W.Go2France.com [195.115.185.184] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id A4093B4F0128; Tue, 17 Jul 2001 12:31:37 +0200 Message-Id: <5.1.0.14.0.20010717120221.03aa6ec8@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 17 Jul 2001 12:24:28 +0200 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: Re: Weird named problem - IN A for nameservers being lost! In-Reply-To: <200107170045.f6H0j8N33016@earth.backplane.com> References: <5.1.0.14.0.20010622153827.02fa0da0@mail.Go2France.com> <5.1.0.14.0.20010622153827.02fa0da0@mail.Go2France.com> <5.1.0.14.0.20010623185802.04051eb0@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > If you look at the cache dumps and dig output below, you can clearly > see the timeout for fuji.jamcracker.com is less then the timeout > for jamcracker.com AFTER we've looked up other elements for fuji, > which means that when it timed out, that IN A record will be gone. > But that IN A record is the IP address for the NS. So when it times > out, the jamcracker entry is left there with no NS records whatsoever. If a resolver needs the ip for an hostname, it looks it up. If the A has expired earlier than the NS, so what? The resolver queries anew for the A of the NS hostname. It´s available at the authoritative NS, a much more credible source than a cache which can be poisoned. > I believe what is happening is that something is looking up other > records for fuji, and this is replacing the original glue record with > the real IN A record sounds like a good idea, no? Turn on query logging to try to see that "something" ? >, but also changing the timeouts somehow and > causing fuji's record to timeout early. There´s no requirement that NS and A records have the same TTL, is there? There´s no requirement for a referral to even include glue, either. > This has occured with several mail destinations, not just > jamcracker. I went through jamcrackers whole DNS hierarchy and > everything is setup > properly, including all the timeouts (they are all set to 3600 seconds). > > Has anyone else seen this? Anyone know what is going on here? All BIND8 machines should be running in "anti-cache-poisoning" mode, ie, with option for recursion off or restricted to trusted ip´s AND "fetch-glue no;". Both are required to defend against cache poisoning. This should equate to the compile option NOADDITIONAL, I think. In BIND9, there is no option for "fetch-glue no". It is the hard-wired default. btw, about 30% of internet nameservers are have poisonable caches. btw, the people at Men&Mice have tried to work with MS about this since NT4 DNS and W2K DNS are both poisonable out of the box, contrary to MS´s intentions for W2K DNS, requiring a registry hack to fix. You might run with "fetch-glue no" and restricted recursion to see if it helps with your unequal timeouts and the apparent re-fetching of "real" glue. Sorry, I´ve come into this thread a little late. Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 9: 4:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id BD85637B406 for ; Tue, 17 Jul 2001 09:04:31 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.4/8.11.2) with ESMTP id f6HG4Rv88578; Tue, 17 Jul 2001 09:04:27 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010716163402.D48387-100000@gandalf.bravenet.com> Date: Tue, 17 Jul 2001 09:04:32 -0700 (PDT) From: John Baldwin To: Dan Subject: RE: pagedaemon + vmdaemon Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 16-Jul-01 Dan wrote: > > ya it seems it is running into swap abit..... > hmmm watching apache with truss i see alot of error #35's > in the sys calls....what is that related to again? From sys/errno.h: /* non-blocking and interrupt i/o */ #define EAGAIN 35 /* Resource temporarily unavailable */ Check the syscall in question to see what resource you are running out of. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 9:12: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 0EFAE37B403; Tue, 17 Jul 2001 09:11:58 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.129.200.Dial1.SanJose1.Level3.net [209.245.129.200]) by snipe.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA15590; Tue, 17 Jul 2001 09:11:40 -0700 (PDT) Message-ID: <3B5463E1.BE28526C@mindspring.com> Date: Tue, 17 Jul 2001 09:12:17 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Richard Hodges Cc: Bill Paul , hackers@FreeBSD.ORG Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Richard Hodges wrote: > > On Mon, 16 Jul 2001, Bill Paul wrote: > > > They're "okay." The NatSemi chip has one flaw, which is that RX buffers > > must be aligned on a 64-bit boundary. None of the more expensive NICs have > > this restriction. > > Go ahead and beat me up if you have to :-) But why is there _any_ issue > with RX buffer alignment? I get some mbufs and set the data pointer to > any point I want, or I get a cluster, which is always on a 2k boundary. Because of the ethernet header being 14 bytes instead of 16, and the Alpha requiring aligned access for structure members when the remainder of the packet is cast to IP and TCP headers, respectively. While you can do an unaligned access on x86, it _is_ more expensive, and may result in more bus cycles than you would otherwise spend. Actually, since the 486, it's been possible for us to turn on unaligned access exceptions on the x86. We should probably consider doing this, to ensure better performance, and to avoid the unnecessary bus overhead we eat for unaligned access today... not to mention how it could shake out the drivers. > Now TX buffers are a problem - I have to take what I get and just > "deal with it". If both start address and length need to be aligned, > then I'm pretty much screwed - I have to copy... No, exactly ythe opposite: the TX buffer is _not_ a problem. This is because it's assembled from mbuf's, so you can actually put it on a 16 byte boundary, and index the mbuf into only the forst 14 bytes of the packet for the header. This means that the transmit queue can have mbufs with aligned access, while the receive queue can't, unless the DMA engine can DMA onto an initial odd boundary, or can break up the DMA into a 14 byte part, plus the remainder on a 16 byte boundary. Bill explains this very well in person, as well as in the current commentary in a couple of his drivers, once you understand the issue. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 9:15: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id BF47037B403; Tue, 17 Jul 2001 09:15:01 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.129.200.Dial1.SanJose1.Level3.net [209.245.129.200]) by snipe.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA02409; Tue, 17 Jul 2001 09:15:00 -0700 (PDT) Message-ID: <3B5464AA.ABF18DE6@mindspring.com> Date: Tue, 17 Jul 2001 09:15:38 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bill Paul Cc: Richard Hodges , hackers@FreeBSD.ORG Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 References: <20010716233436.7C0DB37B407@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill Paul wrote: > Now, before any of you armchair geniuses out there start chiming in > with your incredibly brilliant solutions for this problem which you > just made up on the spot, forget it. This issue has been discussed > to death and there's just no easy way around it. > > Terry Lambert and Alfred Perlstein, this means you. I mean it. Put > down the keyboard and back away from the computer or *blam!* I'll shoot. I agree with you entirely: the chips that do not allow this are incredibly brain damaged. But I _do_ have a fix... 8-)... don't buy brain-damaged hardware. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 9:21: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 1DBFA37B405 for ; Tue, 17 Jul 2001 09:21:03 -0700 (PDT) (envelope-from LConrad@Go2France.com) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 35F6B16B20 for ; Tue, 17 Jul 2001 18:21:01 +0200 (CEST) Received: from IBM-HIRXKN66F0W.Go2France.com [195.115.185.184] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id A7D07BA90128; Tue, 17 Jul 2001 18:29:04 +0200 Message-Id: <5.1.0.14.0.20010717181833.00bb1eb0@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 17 Jul 2001 18:21:55 +0200 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: Re: Weird named problem - IN A for nameservers being lost! In-Reply-To: <5.1.0.14.0.20010717120221.03aa6ec8@mail.Go2France.com> References: <200107170045.f6H0j8N33016@earth.backplane.com> <5.1.0.14.0.20010622153827.02fa0da0@mail.Go2France.com> <5.1.0.14.0.20010622153827.02fa0da0@mail.Go2France.com> <5.1.0.14.0.20010623185802.04051eb0@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here´s an explanation from today´s BIND-users traffic: To: comp-protocols-dns-bind@moderators.isc.org Path: not-for-mail From: Barry Margolin Newsgroups: comp.protocols.dns.bind Subject: Re: Am I wrong? References: <9j1i3n$jkv@pub3.rc.vix.com> Organization: Genuity, Cambridge, MA Higher-level servers are only queried if you don't have the NS records for a domain cached. It's possible for a server to have the following records in its cache: cobranetworks.net. 1D IN NS ns1.cobranetworks.net. cobranetworks.net. 1D IN NS ns1.granitecanyon.com. ns1.cobranetworks.net. 1H IN A 195.82.104.220 ns1.granitecanyon.com. 1D IN A 205.166.226.38 An hour later, the ns1.cobranetworks.net A record will be removed from the cache, but the remaining records will still be there. If someone then tries to look up ns1.cobranetworks.net, a recursive query will be sent to ns1.granitecanyon.com. It's not necessary to consult a .net or root server, because we still have a usable NS record for cobranetworks.net. This is why you need to duplicate glue records in the domain itself. -- Barry Margolin, barmar@genuity.net Genuity, Burlington, MA http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 9:24:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 1A70E37B403; Tue, 17 Jul 2001 09:24:33 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.129.200.Dial1.SanJose1.Level3.net [209.245.129.200]) by snipe.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA20940; Tue, 17 Jul 2001 09:24:26 -0700 (PDT) Message-ID: <3B5466E0.1FD1FA96@mindspring.com> Date: Tue, 17 Jul 2001 09:25:04 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Giorgos Keramidas Cc: "David O'Brien" , Wilko Bulte , Jens Schweikhardt , hackers@FreeBSD.ORG Subject: Re: Whitespace at end of line References: <20010715155941.C1165@schweikhardt.net> <20010715111956.A71874@dragon.nuxi.com> <20010715202505.A94801@freebie.xs4all.nl> <3B53196E.CF1C2110@mindspring.com> <20010716123102.D20942@dragon.nuxi.com> <20010717012733.A589@hades.hell.gr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Giorgos Keramidas wrote: > > > > Maybe I'm just plain dim today (I will add a beer to > > > > rectify this situation at first convenience..) but what > > > > is so bad about some trailing whitespace that a massive > > > > commit-a-thlon is called for? > > > > > > You use emacs, don't you? > > > > What does vi vs. emacs have to do with it? > > It's probably one of those rumours that Emacs likes playing smart and $ > adding whitespace to the end of wrapped lines. Lies, damn lies. $ > $ > -giorgos $ > $ > (a happy emacs user who also feels comfortable with vi, joe, pico, whatever) $ Got it in one... $ -- Terry $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 9:45: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 90F8337B403 for ; Tue, 17 Jul 2001 09:44:58 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.129.200.Dial1.SanJose1.Level3.net [209.245.129.200]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA24252; Tue, 17 Jul 2001 09:44:53 -0700 (PDT) Message-ID: <3B546BA9.37E9F437@mindspring.com> Date: Tue, 17 Jul 2001 09:45:29 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Albert D. Cahalan" Cc: freebsd-hackers@FreeBSD.ORG, Jim.Pirzyk@disney.com Subject: Re: math library difference between linux emulation and native freebsd (and native linux) References: <200107170615.f6H6FU5376195@saturn.cs.uml.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Albert D. Cahalan" wrote: > >> There are only two shared libaries in common (libc and libm) and > >> both are the same on FreeBSD (in /compat/linux) and Linux. > >> > >> So any ideas on where the program is going wrong? > > > > man fpsetround > > That won't change a thing. Both systems round to nearest. Look at the other items on that man page, as well. I didn't list them all. > > The defaults for the Linux emulator are different than > > the defaults for Linux. Linux sets some stuff up wrong, > > FreeBSD sets stuff up wrong. This is a choice between bad > and worse, since the CPU does not support what you want. FreeBSD complies strictly with the IEEE FP standard. Linux fails to set 0x37f into the mask before doing its calculations, and assumes that the OS has done this for it. In Linux it's true, in the emulator, it's not; the fix is obvious: somone who uses the Linux emulator should fix this. One obvious reason that the Linux approach is wrong is that it ends up requiring the save and restore of FP registers on context switches, which is overhead they ate anyway, by doing TSS based context switching. The amount of state with SSE is up to something like an additional 512 bytes -- that's ungodly overhead, since most programs don't use this context at all. > An x86 CPU has a rounding precision that may be set for > float, double, or long double. FreeBSD sets the CPU to > make double work, giving extra fraction bits for float > and truncating long double. Linux sets the CPU to make > long double work, giving extra fraction bits for both > float and long double. Now what is worse, getting some > extra bits in an intermediate calculation or truncation? > Note that the FreeBSD setting causes _both_ problems. FreeBSD's settings do not cause problems for FreeBSD; as has been observed in this thread, FreeBSD gets the right answer when you run the code native, just as Linux does; the emulator gets the wrong answer, but the problem is really the programs assuming that the mask will be set by the OS to the "magic" correct value. As also noted in this thread, Mathematica under the Linux emulator gets the _right_ answer. Clearly, the authors of Mathematica know to not make ignorant assumptions about the default state of hardware. > See float_t, double_t, FLT_EVAL_METHOD and FLT_ROUNDS in > the 1999 C standard for ways to deal with x86 hardware. The standards are not x86 specific; the fp*() functions are. It is probably worthwhile to solve this problem by doing a "brand" of floating point using Linux binaries, rather than eating the additional context switch overhead for all Linux programs... there _are_ reasons that Linux binaries running on the FreeBSD Linux ABI are frequently faster than when running natively on Linux. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 9:56:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 868AC37B405 for ; Tue, 17 Jul 2001 09:56:19 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6HGuGS32097; Tue, 17 Jul 2001 09:56:17 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Tue, 17 Jul 2001 09:56:13 -0700 (PDT) From: Matthew Jacob Reply-To: To: Terry Lambert Cc: Subject: x86 unaligned access followup. In-Reply-To: <3B5463E1.BE28526C@mindspring.com> Message-ID: <20010717095413.G83710-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Actually, since the 486, it's been possible for us to turn on unaligned > access exceptions on the x86. We should probably consider doing this, to > ensure better performance, and to avoid the unnecessary bus overhead we > eat for unaligned access today... not to mention how it could shake out > the drivers. Now *that* is a very cool idea. As Johnny Carson would say "I did not know that". How would this be done? I assume it's some bit-flip for the chip? D'ya have a sample bit 'o code for this? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 10:34: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id B2EDE37B40B for ; Tue, 17 Jul 2001 10:33:59 -0700 (PDT) (envelope-from rh@matriplex.com) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id KAA42306; Tue, 17 Jul 2001 10:33:57 -0700 (PDT) (envelope-from rh@matriplex.com) Date: Tue, 17 Jul 2001 10:33:57 -0700 (PDT) From: Richard Hodges To: Terry Lambert Cc: hackers@FreeBSD.ORG Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 In-Reply-To: <3B5463E1.BE28526C@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 17 Jul 2001, Terry Lambert wrote: > Richard Hodges wrote: > > Go ahead and beat me up if you have to :-) But why is there _any_ issue > > with RX buffer alignment? I get some mbufs and set the data pointer to > > any point I want, or I get a cluster, which is always on a 2k boundary. > > Because of the ethernet header being 14 bytes instead of 16, Yes, I see it now. It is pretty obvious (now) that the ethernet header and the payload cannot both be aligned. > > Now TX buffers are a problem - I have to take what I get and just > > "deal with it". If both start address and length need to be aligned, > > then I'm pretty much screwed - I have to copy... > > No, exactly ythe opposite: the TX buffer is _not_ a problem. This > is because it's assembled from mbuf's, so you can actually put it > on a 16 byte boundary, and index the mbuf into only the forst 14 > bytes of the packet for the header. It is still a problem. If the hardware requires buffer start and length to be word aligned, I have to copy the entire mbuf chain if it is not perfectly aligned to start with. The very rare exception is if an mbuf in the middle just happens to have a length off by exactly the alignment offset - in that case I can stop there, so long as the rest of the chain is aligned, of course. This is a very real issue for me (in the form of the IDT 77211 ATM SAR...) To be fair, this may not be a great example, since I don't have an ethernet header to worry about. -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. Product Manager | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 10:35: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natpost.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 496A137B403 for ; Tue, 17 Jul 2001 10:35:00 -0700 (PDT) (envelope-from freebsd-ml@econos.de) Received: from stefan-bt (p3E9B8E20.dip.t-dialin.net [62.155.142.32]) by post.webmailer.de (8.9.3/8.8.7) with SMTP id TAA22338; Tue, 17 Jul 2001 19:34:54 +0200 (MET DST) From: Stefan Hoffmeister To: tlambert2@mindspring.com Cc: "Albert D. Cahalan" , freebsd-hackers@FreeBSD.ORG, Jim.Pirzyk@disney.com Subject: Re: math library difference between linux emulation and native freebsd (and native linux) Date: Tue, 17 Jul 2001 19:34:21 +0200 Organization: Econos Message-ID: References: <200107170615.f6H6FU5376195@saturn.cs.uml.edu> <3B546BA9.37E9F437@mindspring.com> In-Reply-To: <3B546BA9.37E9F437@mindspring.com> X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : On Tue, 17 Jul 2001 09:45:29 -0700, Terry Lambert wrote: >One obvious reason that the Linux approach is wrong is >that it ends up requiring the save and restore of FP >registers on context switches, which is overhead they >ate anyway, by doing TSS based context switching. The >amount of state with SSE is up to something like an >additional 512 bytes -- that's ungodly overhead, since >most programs don't use this context at all. Except that - AFAIK - Linux won't do that. Linux install traps, causing the first FPU and SSE instruction to fault (might as well be only the SSE instructions). Upon the fault, the context structure size is switched. IOW, Linux does not blindly have an FPU context size of 512 bytes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 10:55:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id DFC6537B401; Tue, 17 Jul 2001 10:55:27 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id TAA18955; Tue, 17 Jul 2001 19:55:26 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id 8B5DF14AF5; Tue, 17 Jul 2001 19:55:26 +0200 (CEST) Date: Tue, 17 Jul 2001 19:55:26 +0200 From: Alexander Langer To: Terry Lambert Cc: Bill Moran , freebsd-hackers@FreeBSD.ORG, freebsd-config@FreeBSD.ORG Subject: Re: Package based configuration control Message-ID: <20010717195526.C804@zerogravity.kawo2.rwth-aachen.d> References: <20010706144935.A61843@xor.obsecurity.org> <3B4650D0.97F10B83@bellatlantic.net> <20010707002340.B16071@widomaker.com> <20010707004731V.jkh@osd.bsdi.com> <3B49F8D5.2C9BFA73@mindspring.com> <3B4A0124.26025FB5@iowna.com> <3B4A1423.E8E365E@mindspring.com> <3B4A1E70.18A550B7@iowna.com> <3B4B2538.6FAC0C40@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B4B2538.6FAC0C40@mindspring.com>; from tlambert2@mindspring.com on Tue, Jul 10, 2001 at 08:54:32AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Terry Lambert (tlambert2@mindspring.com): > A surprising number of people have expressed an interest > in working on a package-based install in private email, > so it's probably an idea whose time has come. We should I think the base distribution will be a package in libh. We will have more neat[tm] stuff in it. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 11: 4:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from saturn.cs.uml.edu (saturn.cs.uml.edu [129.63.8.2]) by hub.freebsd.org (Postfix) with ESMTP id 9FBBB37B403 for ; Tue, 17 Jul 2001 11:04:33 -0700 (PDT) (envelope-from acahalan@saturn.cs.uml.edu) Received: (from acahalan@localhost) by saturn.cs.uml.edu (8.11.0/8.11.2) id f6HI2OV422095; Tue, 17 Jul 2001 14:02:24 -0400 (EDT) From: "Albert D. Cahalan" Message-Id: <200107171802.f6HI2OV422095@saturn.cs.uml.edu> Subject: Re: math library difference between linux emulation and native freebsd To: tlambert2@mindspring.com Date: Tue, 17 Jul 2001 14:02:24 -0400 (EDT) Cc: acahalan@cs.uml.edu (Albert D. Cahalan), freebsd-hackers@FreeBSD.ORG, Jim.Pirzyk@disney.com In-Reply-To: <3B546BA9.37E9F437@mindspring.com> from "Terry Lambert" at Jul 17, 2001 09:45:29 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert writes: > "Albert D. Cahalan" wrote: >>> The defaults for the Linux emulator are different than >>> the defaults for Linux. Linux sets some stuff up wrong, >> >> FreeBSD sets stuff up wrong. This is a choice between bad >> and worse, since the CPU does not support what you want. > > FreeBSD complies strictly with the IEEE FP standard. As long as you don't ever use "float" or "long double", yes. The "float" type isn't seriously broken, while "long double" is. > Linux fails to set 0x37f into the mask before doing > its calculations, and assumes that the OS has done this > for it. In Linux it's true, in the emulator, it's not; You mean "Linux apps fail to..." I think. ^^^^ Certainly. The initial FPU control word is part of the ABI. Explicitly setting this would mark a process as being an FPU user, which would then be shown in "ps" output. Setting cast-in-stone defaults is also a waste of CPU time. > One obvious reason that the Linux approach is wrong is > that it ends up requiring the save and restore of FP > registers on context switches, which is overhead they > ate anyway, by doing TSS based context switching. No and no. (that was true at one time) >> An x86 CPU has a rounding precision that may be set for >> float, double, or long double. FreeBSD sets the CPU to >> make double work, giving extra fraction bits for float >> and truncating long double. Linux sets the CPU to make >> long double work, giving extra fraction bits for both >> float and long double. Now what is worse, getting some >> extra bits in an intermediate calculation or truncation? >> Note that the FreeBSD setting causes _both_ problems. > > FreeBSD's settings do not cause problems for FreeBSD; as > has been observed in this thread, FreeBSD gets the right > answer when you run the code native, just as Linux does; Try again with "long double". > the emulator gets the wrong answer, but the problem is > really the programs assuming that the mask will be set > by the OS to the "magic" correct value. It's no worse than assuming /dev/null will exist. >> See float_t, double_t, FLT_EVAL_METHOD and FLT_ROUNDS in >> the 1999 C standard for ways to deal with x86 hardware. > > The standards are not x86 specific; the fp*() functions > are. The standards have what you need to deal with x86 hardware. They give software a way to handle evaluation with excess fraction bits in intermediate calculations. Most fp*() functions work great on a SPARC with Solaris. The precision control isn't quite x86-specific. The i860 has this problem too AFAIK. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 11: 5: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from saturn.cs.uml.edu (saturn.cs.uml.edu [129.63.8.2]) by hub.freebsd.org (Postfix) with ESMTP id 8A00437B403 for ; Tue, 17 Jul 2001 11:04:58 -0700 (PDT) (envelope-from acahalan@saturn.cs.uml.edu) Received: (from acahalan@localhost) by saturn.cs.uml.edu (8.11.0/8.11.2) id f6HI2OV422095; Tue, 17 Jul 2001 14:02:24 -0400 (EDT) From: "Albert D. Cahalan" Message-Id: <200107171802.f6HI2OV422095@saturn.cs.uml.edu> Subject: Re: math library difference between linux emulation and native freebsd To: tlambert2@mindspring.com Date: Tue, 17 Jul 2001 14:02:24 -0400 (EDT) Cc: acahalan@cs.uml.edu (Albert D. Cahalan), freebsd-hackers@FreeBSD.ORG, Jim.Pirzyk@disney.com In-Reply-To: <3B546BA9.37E9F437@mindspring.com> from "Terry Lambert" at Jul 17, 2001 09:45:29 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert writes: > "Albert D. Cahalan" wrote: >>> The defaults for the Linux emulator are different than >>> the defaults for Linux. Linux sets some stuff up wrong, >> >> FreeBSD sets stuff up wrong. This is a choice between bad >> and worse, since the CPU does not support what you want. > > FreeBSD complies strictly with the IEEE FP standard. As long as you don't ever use "float" or "long double", yes. The "float" type isn't seriously broken, while "long double" is. > Linux fails to set 0x37f into the mask before doing > its calculations, and assumes that the OS has done this > for it. In Linux it's true, in the emulator, it's not; You mean "Linux apps fail to..." I think. ^^^^ Certainly. The initial FPU control word is part of the ABI. Explicitly setting this would mark a process as being an FPU user, which would then be shown in "ps" output. Setting cast-in-stone defaults is also a waste of CPU time. > One obvious reason that the Linux approach is wrong is > that it ends up requiring the save and restore of FP > registers on context switches, which is overhead they > ate anyway, by doing TSS based context switching. No and no. (that was true at one time) >> An x86 CPU has a rounding precision that may be set for >> float, double, or long double. FreeBSD sets the CPU to >> make double work, giving extra fraction bits for float >> and truncating long double. Linux sets the CPU to make >> long double work, giving extra fraction bits for both >> float and long double. Now what is worse, getting some >> extra bits in an intermediate calculation or truncation? >> Note that the FreeBSD setting causes _both_ problems. > > FreeBSD's settings do not cause problems for FreeBSD; as > has been observed in this thread, FreeBSD gets the right > answer when you run the code native, just as Linux does; Try again with "long double". > the emulator gets the wrong answer, but the problem is > really the programs assuming that the mask will be set > by the OS to the "magic" correct value. It's no worse than assuming /dev/null will exist. >> See float_t, double_t, FLT_EVAL_METHOD and FLT_ROUNDS in >> the 1999 C standard for ways to deal with x86 hardware. > > The standards are not x86 specific; the fp*() functions > are. The standards have what you need to deal with x86 hardware. They give software a way to handle evaluation with excess fraction bits in intermediate calculations. Most fp*() functions work great on a SPARC with Solaris. The precision control isn't quite x86-specific. The i860 has this problem too AFAIK. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 11:28:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 375DE37B401 for ; Tue, 17 Jul 2001 11:28:45 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f6HISin27399 for ; Tue, 17 Jul 2001 14:28:44 -0400 (EDT) Date: Tue, 17 Jul 2001 14:28:36 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@opal To: freebsd-hackers@freebsd.org Subject: SPARE_USRSPACE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Can anyone tell me why FreeBSD has 256 bytes of spare space in the user area? Thanks. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 11:39:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id 323B337B401 for ; Tue, 17 Jul 2001 11:39:08 -0700 (PDT) (envelope-from karsten@rohrbach.de) Received: (qmail 25261 invoked by uid 1000); 17 Jul 2001 18:44:23 -0000 Date: Tue, 17 Jul 2001 20:44:23 +0200 From: "Karsten W. Rohrbach" To: Matt Dillon Cc: hackers@FreeBSD.ORG Subject: Re: Swapping in diskless ? (was :Re: [hackers] Re: getting rid of sysinstall) Message-ID: <20010717204423.J18481@mail.webmonster.de> Mail-Followup-To: "Karsten W. Rohrbach" , Matt Dillon , hackers@FreeBSD.ORG References: <20010712143205.D4589@sneakerz.org> <3B4E1C69.A6DC0397@herbelot.com> <15182.63564.476492.390695@trooper.velocet.net> <3B4F3A22.EF2AC90A@herbelot.com> <15183.17942.995110.382797@trooper.velocet.net> <200107132227.f6DMR8071313@earth.backplane.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="pWJxWxNlJUNgDlXi" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107132227.f6DMR8071313@earth.backplane.com>; from dillon@earth.backplane.com on Fri, Jul 13, 2001 at 03:27:08PM -0700 X-Arbitrary-Number-Of-The-Day: 42 X-URL: http://www.webmonster.de/ X-Disclaimer: My opinions do not necessarily represent those of my employer Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --pWJxWxNlJUNgDlXi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Matt Dillon(dillon@earth.backplane.com)@2001.07.13 15:27:08 +0000: > Also, do performance testing with dynamic-linked verses static-linked > binaries. Static-linked binaries may look larger, but they have a=20 > much lower dirty-page overhead then the dynamically linked equivalent. > It depends on the situation but it is definitely worth testing. yup, and for highvolume dumbfire boxes (static web content, ftp server) i also have one box running with options NO_SWAPPING and carefully calculated limits in the userland. runs like a charm. i use the swap partition mostly to hold a crashdump if i'm trying something weird ;-) /k --=20 > question =3D ( to ) ? be : ! be; // Wm. Shakespeare KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.n= et/ karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- catch@spam.de GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 B= F46 Please do not remove my address from To: and Cc: fields in mailing lists. 1= 0x --pWJxWxNlJUNgDlXi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7VIeHM0BPTilkv0YRAmPPAJ0R74GvVT9MiO2rbXmC5jVO+xlbHgCgkwyf 0/g+k6Srz1+2mj/feORlQUA= =U1dd -----END PGP SIGNATURE----- --pWJxWxNlJUNgDlXi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 13:13:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from naboo.ethz.ch (naboo.ethz.ch [129.132.17.66]) by hub.freebsd.org (Postfix) with ESMTP id D1C6537B401 for ; Tue, 17 Jul 2001 13:13:11 -0700 (PDT) (envelope-from carlo@vis.ethz.ch) Received: by naboo.ethz.ch (Postfix, from userid 224) id 5F62C275B7; Tue, 17 Jul 2001 22:13:10 +0200 (CEST) Subject: CTM is down again To: freebsd-hackers@freebsd.org Date: Tue, 17 Jul 2001 22:13:10 +0200 (CEST) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010717201310.5F62C275B7@naboo.ethz.ch> From: carlo@vis.ethz.ch (Carlo Dapor) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear fellow hackers I haven't received any CTMs since July 12th. Am I the only one ? My guess is that the main distribution point is malfunctioning. Can anybody with closer access to the 'feeder' check into it ? Thanks ! Ciao, dewrweil, -- Carlo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 14:10: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web.cs.ndsu.NoDak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id 47E4937B40C for ; Tue, 17 Jul 2001 14:10:02 -0700 (PDT) (envelope-from tinguely@web.cs.ndsu.NoDak.edu) Received: (from tinguely@localhost) by web.cs.ndsu.NoDak.edu (8.11.1/8.11.1) id f6HLA1s14278 for freebsd-hackers@freebsd.org; Tue, 17 Jul 2001 16:10:01 -0500 (CDT) (envelope-from tinguely) Date: Tue, 17 Jul 2001 16:10:01 -0500 (CDT) From: mark tinguely Message-Id: <200107172110.f6HLA1s14278@web.cs.ndsu.NoDak.edu> To: freebsd-hackers@freebsd.org Subject: BIOS reading physical RAM Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anyone have a reference to the values of "type" field in the Intel BIOS physical system RAM mapping? I am curious why we are using only entries of type "0x01". --mark tinguely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 14:30:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (cust-P5-R1-241.POOL.ESR.SJO.wwc.com [206.112.104.241]) by hub.freebsd.org (Postfix) with ESMTP id 1F76B37B403 for ; Tue, 17 Jul 2001 14:30:21 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f6HLUFJ02145; Tue, 17 Jul 2001 14:30:17 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200107172130.f6HLUFJ02145@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: mark tinguely Cc: freebsd-hackers@freebsd.org Subject: Re: BIOS reading physical RAM In-reply-to: Your message of "Tue, 17 Jul 2001 16:10:01 CDT." <200107172110.f6HLA1s14278@web.cs.ndsu.NoDak.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 17 Jul 2001 14:30:07 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Does anyone have a reference to the values of "type" field in the Intel > BIOS physical system RAM mapping? > > I am curious why we are using only entries of type "0x01". This table (from Ralf Brown's Interrupt List) is self-explanatory: Values for System Memory Map address type: 01h memory, available to OS 02h reserved, not available (e.g. system ROM, memory-mapped device) 03h ACPI Reclaim Memory (usable by OS after reading ACPI tables) 04h ACPI NVS Memory (OS is required to save this memory between NVS sessions) other not defined yet -- treat as Reserved -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 14:49:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 3B92C37B431 for ; Tue, 17 Jul 2001 14:49:10 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.4/8.11.2) with ESMTP id f6HLmmv94152; Tue, 17 Jul 2001 14:48:49 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010717095413.G83710-100000@wonky.feral.com> Date: Tue, 17 Jul 2001 14:48:58 -0700 (PDT) From: John Baldwin To: Matthew Jacob Subject: RE: x86 unaligned access followup. Cc: hackers@FreeBSD.org, Terry Lambert Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 17-Jul-01 Matthew Jacob wrote: > > >> Actually, since the 486, it's been possible for us to turn on unaligned >> access exceptions on the x86. We should probably consider doing this, to >> ensure better performance, and to avoid the unnecessary bus overhead we >> eat for unaligned access today... not to mention how it could shake out >> the drivers. > > > Now *that* is a very cool idea. As Johnny Carson would say "I did not know > that". How would this be done? I assume it's some bit-flip for the chip? > D'ya have a sample bit 'o code for this? It's the AC bit in eflags. > -matt -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 17:42:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp5ve.mailsrvcs.net (smtp5vepub.gte.net [206.46.170.26]) by hub.freebsd.org (Postfix) with ESMTP id 46EDA37B405 for ; Tue, 17 Jul 2001 17:42:30 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-117-20.nnj.dialup.bellatlantic.net [151.198.117.20]) by smtp5ve.mailsrvcs.net (8.9.1/8.9.1) with ESMTP id AAA29182904; Wed, 18 Jul 2001 00:41:20 GMT Message-ID: <3B54DB2F.90621945@bellatlantic.net> Date: Tue, 17 Jul 2001 20:41:19 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Julian Elischer Cc: Soren Kristensen , Bsdguru@aol.com, hackers@FreeBSD.ORG Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer wrote: > > The proble is that teh ethernet header is 14 bytes so you must choose > to allighn either the whole packet, or the IP header, but you cannot do > both. Hm, it seems to be a waste of CPU time memory bandwidth: only the IP and TCP headers have to be aligned but the payload in most cases will be copied over once again to the user space anyway. So, theoretically speaking, this can be solved at the level of the upper protocols: IP and TCP and UDP and NFS are doing m_pullup() anyway (if neccessary), so a call named like m_pullup_align(mp, len, alignment) can be implemented and used instead of m_pullup() to both ensure the minimal length of the buffer chunk and its proper alignment. The difficult thing in such an implementation will be to make sure that all the protocols have been updated to use it. -SB > On Mon, 16 Jul 2001, Soren Kristensen wrote: > > > Hi, > > > > Bsdguru@aol.com wrote: > > > > > > In a message dated 07/16/2001 1:11:09 PM Eastern Daylight Time, > > > tlambert2@mindspring.com writes: > > > > > > > > How do these perform compared to the more expensive gigabit cards? > > > > > > > > Read the driver. > > > > > > > > In general, they require an extra copy because of the inability > > > > of the card to DMA on a reasonable boundry. > > > > > > > > Bill's commentary in his drivers is frequently enlightening, > > > > and often amusing... 8-). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 18:26:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta01.chello.no (mta01.chello.no [212.186.255.12]) by hub.freebsd.org (Postfix) with ESMTP id 3079437B405 for ; Tue, 17 Jul 2001 18:26:49 -0700 (PDT) (envelope-from handaa@chello.no) Received: from magnus ([62.179.146.41]) by mta01.chello.no (InterMail vK.4.03.00.00 201-232-121 license e9baf6250a3e09baf933190ee5f5f2b0) with SMTP id <20010718012818.EREN19663.mta01@magnus> for ; Wed, 18 Jul 2001 03:28:18 +0200 Message-ID: <000b01c10f28$42f2c740$0200a8c0@chello.no> From: "Magnus" To: Subject: System unable to resolve hostnames Date: Wed, 18 Jul 2001 03:23:33 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2462.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FreeBSD Alpha.chello.no 4.3-RELEASE FreeBSD I have a wierd problem, where the system is unable to resolve hostnames. Even though I have configured resolv.conf, here is the output of the file: search chello.no nameserver 212.186.255.29 nameserver 212.186.255.30 I have checked the addresses, and they are correct. Have also tried using those DNS server on a win box, wich works fine. I am able to ping numerical addresses, however, when I try to ping hostnames I get: "ping: cannot resolve freebsd.org: unknown host" Have tried several adresses, all with the same result. This happens also when I try to ftp, http with lynx, ntp update, they all fail to connect when I use hostnames. What makes it even more wierd, is that I am able to resolv hostnames by using 'nslookup'. prompt # nslookup freebsd.org server: dnscache01.chello.no address: 212.186.255.29 Name: Freebsd.org address: 216.136.204.21 Wich means I am able to resolve hostnames, DNS is working, however applications like ping, ftp etc. fails to resolve hostnames. How does the application resolve hostnames, what can cause what I am experiencing ? I would like to resolve this problem, if someone could shed some light on this problem. I would greatly appreciate it. If you need more feedback, to trouble shoot this problem. Let me know, and I will reply as soon as possible. Magnus Oslo, Norway To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 18:37:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 4253C37B41F for ; Tue, 17 Jul 2001 18:37:51 -0700 (PDT) (envelope-from ben@FreeBSD.org) Received: from strontium.shef.vinosystems.com ([192.168.91.36] ident=ben) by scientia.demon.co.uk with smtp (Exim 3.30 #1) id 15MgHd-000ACD-00; Wed, 18 Jul 2001 02:37:49 +0100 Date: Wed, 18 Jul 2001 02:37:48 +0100 From: Ben Smithurst To: Magnus Cc: freebsd-hackers@FreeBSD.org Subject: Re: System unable to resolve hostnames Message-ID: <20010718023748.O59863@strontium.shef.vinosystems.com> References: <000b01c10f28$42f2c740$0200a8c0@chello.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="mSxgbZZZvrAyzONB" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000b01c10f28$42f2c740$0200a8c0@chello.no> X-PGP-Key: http://www.smithurst.org/ben/pgp-key.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --mSxgbZZZvrAyzONB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Magnus wrote: > What makes it even more wierd, is that I am able to resolv hostnames by > using > 'nslookup'. > prompt # nslookup freebsd.org > server: dnscache01.chello.no > address: 212.186.255.29 >=20 > Name: Freebsd.org > address: 216.136.204.21 >=20 > Wich means I am able to resolve hostnames, DNS is working, however > applications like ping, ftp etc. fails to resolve hostnames. > How does the application resolve hostnames, what can cause what I > am experiencing ? Seems like this sort of thing could happen if you didn't have 'bind' listed in /etc/host.conf. I'm not sure -hackers is the most appropriate list either. --=20 Ben Smithurst / ben@FreeBSD.org --mSxgbZZZvrAyzONB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7VOhrbPzJ+yzvRCwRAi9kAKDSWsksOvA1SrsVIh83tRDIQOqRVwCfWjst Zwg8bUMm3SLv4igh1BKVmF0= =lMTt -----END PGP SIGNATURE----- --mSxgbZZZvrAyzONB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 19:44:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from technokratis.com (modemcable052.174-202-24.mtl.mc.videotron.ca [24.202.174.52]) by hub.freebsd.org (Postfix) with ESMTP id 4315837B401 for ; Tue, 17 Jul 2001 19:44:10 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by technokratis.com (8.11.3/8.11.3) id f6I2tXv92717; Tue, 17 Jul 2001 22:55:33 -0400 (EDT) (envelope-from bmilekic) Date: Tue, 17 Jul 2001 22:55:33 -0400 From: Bosko Milekic To: Mike Silbersack Cc: Leo Bicknell , freebsd-hackers@FreeBSD.ORG Subject: Re: Network performance roadmap. Message-ID: <20010717225533.B92264@technokratis.com> References: <20010713101107.B9559@ussenterprise.ufp.org> <20010713162440.Q24914-100000@achilles.silby.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010713162440.Q24914-100000@achilles.silby.com>; from silby@silby.com on Fri, Jul 13, 2001 at 04:37:46PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jul 13, 2001 at 04:37:46PM -0500, Mike Silbersack wrote: > Jiangyi Liu has been working on mbuf limiting code for the past week or > so. What he has is pretty complete, I expect to get most of it committed > once Bosko gets back. Well, I'm back. I'm now going to bed but my INBOX awaits. > Mike "Silby" Silbersack -- Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 22: 4:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f187.law11.hotmail.com [64.4.17.187]) by hub.freebsd.org (Postfix) with ESMTP id AFAE537B401; Tue, 17 Jul 2001 22:04:43 -0700 (PDT) (envelope-from part_lion@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 17 Jul 2001 22:04:43 -0700 Received: from 24.130.176.212 by lw11fd.law11.hotmail.msn.com with HTTP; Wed, 18 Jul 2001 05:04:43 GMT X-Originating-IP: [24.130.176.212] From: "Joesh Juphland" To: hackers@freebsd.org Cc: freebsd-mobile@freebsd.org Subject: please confirm or deny - bridging possible between PC cards ? Date: Tue, 17 Jul 2001 23:04:43 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 18 Jul 2001 05:04:43.0607 (UTC) FILETIME=[28494670:01C10F47] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok, so I finally got two identical "ep" cards to come up at the same time and both work. Thanks. But when I run: sysctl -w net.link.ether.bridge=1 Nothing happens. They don't get put in promiscuous mode, and bridging does not get turned on, even though I have bridging in my kernel. Can anyone shed any light on this subject ? Does it not work with pc cards ? Or is there a secret trick I need to do ? thanks. _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 22: 5:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp-out.hamburg.pop.de (smtp-out.hamburg.pop.de [195.222.210.86]) by hub.freebsd.org (Postfix) with ESMTP id EF7D737B401 for ; Tue, 17 Jul 2001 22:05:25 -0700 (PDT) (envelope-from ) Received: from mail.hamburg.pop.de ([193.98.9.7] helo=mail.provi.de) by smtp-out.hamburg.pop.de with esmtp (Exim 3.22 #1) id 15MjXE-0002jJ-00 for hackers@freebsd.org; Wed, 18 Jul 2001 07:06:08 +0200 Received: from daemon by mail.provi.de with local (Exim 3.20 #2) id 15MjWR-0004IS-00 for hackers@FreeBSD.ORG; Wed, 18 Jul 2001 07:05:19 +0200 From: To: Subject: mail failed, returning to sender X-No-Resend: True Message-Id: Date: Wed, 18 Jul 2001 07:05:19 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG |------------------------- Message log follows: -----------------------| | no valid recipients were found for this message | |----------------------------------------------------------------------| | t.schmeissel@mail.hh.provi.de - unknown user |----------------------------------------------------------------------| German translation: Sie haben Ihre eMail an die Adresse "t.schmeissel@mail.hh.provi.de" gerichtet. Der hintere Teil der Adresse ("Domain"), "@mail.hh.provi.de", ist gueltig, der Benutzernamen jedoch nicht. Ueberpruefen Sie bitte insbesondere diesen Teil der eMail-Adresse! Sie erhalten im Anhang die ersten zehn Zeilen Ihrer Original-eMail zurueck. Mit freundlichen Gruessen, Point of Presence GmbH, Hamburg ------------------------------------------------------------------------ From owner-freebsd-hackers-digest@freebsd.org Wed Jul 18 07:05:19 2001 Return-path: Envelope-to: t.schmeissel@mail.hh.provi.de Delivery-date: Wed, 18 Jul 2001 07:05:19 +0200 Received: from mx2.freebsd.org ([216.136.204.119]) by mail.provi.de with smtp (Exim 3.20 #2) id 15MjWQ-0004I2-00 for t.schmeissel@mail.hh.provi.de; Wed, 18 Jul 2001 07:05:18 +0200 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id BF12555C32; Tue, 17 Jul 2001 22:04:55 -0700 (PDT) (envelope-from owner-freebsd-hackers-digest@FreeBSD.ORG) Received: by hub.freebsd.org (Postfix, from userid 538) id F184937B405; Tue, 17 Jul 2001 22:04:54 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with SMTP id D86A12E8036; Tue, 17 Jul 2001 22:04:54 -0700 (PDT) (envelope-from owner-freebsd-hackers-digest) Received: by hub.freebsd.org (bulk_mailer v1.12); Tue, 17 Jul 2001 22:04:54 -0700 From: owner-freebsd-hackers-digest@FreeBSD.ORG (freebsd-hackers-digest) To: freebsd-hackers-digest@FreeBSD.ORG Subject: freebsd-hackers-digest V5 #183 Reply-To: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers-digest@FreeBSD.ORG Precedence: bulk Message-ID: Date: Tue, 17 Jul 2001 22:04:54 -0700 (PDT) freebsd-hackers-digest Tuesday, July 17 2001 Volume 05 : Number 183 In this issue: mail failed, returning to sender [none] Re: Weird named problem - IN A for nameservers being lost! Re: math library difference between linux emulation and native freebsd (and native linux) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 22: 9:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f233.law11.hotmail.com [64.4.17.233]) by hub.freebsd.org (Postfix) with ESMTP id E53B137B403; Tue, 17 Jul 2001 22:09:24 -0700 (PDT) (envelope-from part_lion@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 17 Jul 2001 22:09:24 -0700 Received: from 24.130.176.212 by lw11fd.law11.hotmail.msn.com with HTTP; Wed, 18 Jul 2001 05:09:24 GMT X-Originating-IP: [24.130.176.212] From: "Joesh Juphland" To: hackers@freebsd.org Cc: freebsd-mobile@freebsd.org Subject: Details ... (please confirm or deny pccard bridging) Date: Tue, 17 Jul 2001 23:09:24 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 18 Jul 2001 05:09:24.0765 (UTC) FILETIME=[CFDE94D0:01C10F47] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG /etc/rc.conf looks like this: pccard_enable="YES" pccard_mem="DEFAULT" pccardd_flags=" -i 10 -i 15" removable_interfaces="ep0 ep1" network_interfaces="lo0" (I have tried with and without that last lo0 line) and /etc/defaults/pccard.conf looks like this: config auto "ep0" 10 config auto "ep1" 15 so anyway, both cards come up just fine, LED on the dongle is lit, and everything is great - BUT - when I sysctl -w net.link.ether.bridge=1 nothing happens ... nobody goes into promiscuous mode... any ideas ? thanks! _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 22:28:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from roulen-gw.morning.ru (roulen-gw.morning.ru [195.161.98.242]) by hub.freebsd.org (Postfix) with ESMTP id DC3D437B406; Tue, 17 Jul 2001 22:28:05 -0700 (PDT) (envelope-from poige@morning.ru) Received: from NIC1 (seven.ld [192.168.11.7]) by roulen-gw.morning.ru (Postfix) with ESMTP id 10175127; Wed, 18 Jul 2001 13:28:04 +0800 (KRAST) Date: Wed, 18 Jul 2001 13:28:20 +0800 From: Igor Podlesny X-Mailer: The Bat! (v1.52 Beta/7) UNREG / CD5BF9353B3B7091 Organization: Morning Network X-Priority: 3 (Normal) Message-ID: <1185771218.20010718132820@morning.ru> To: Wes Peters Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re[2]: Flight of the rat, living wreck..... In-Reply-To: <3B3E0D93.79738728@softweyr.com> References: <754836544.20010630185133@morning.ru> <3B3E0D93.79738728@softweyr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Igor Podlesny wrote: >> > /* >> > * Macro for finding the interface (ifnet structure) corresponding to one >> > * of our IP addresses. >> > */ >> > #define INADDR_TO_IFP(addr, ifp) \ >> > /* struct in_addr addr; */ \ >> > /* struct ifnet *ifp; */ \ >> > { \ >> > register struct in_ifaddr *ia; \ >> > \ >> > for (ia = in_ifaddrhead.tqh_first; \ >> >> // so here we start looking through the queue >> >> > ia != NULL >> >> // sanity (I'd have written just (ia)) >> >> > && ((ia->ia_ifp->if_flags & IFF_POINTOPOINT)? \ >> >> // hm. special case if the interface is PTP >> >> > IA_DSTSIN(ia):IA_SIN(ia))->sin_addr.s_addr != (addr).s_addr; \ >> >> // so it is like: if it is PTP, then we using DST address in comparison >> // with addr.s_addr >> >> // it is the time I started to ask myself why it is so? why we're (ok, >> // they're) checking for remote ip-address if the head comment >> // says: >> // * Macro for finding the interface (ifnet structure) corresponding to one >> // * of our IP addresses. >> // ^^^ >> // ^^^ > With point-to-point connections, the address at the opposite end of the > connection is always used in the route table. When the interface is > created as a point-to-point interface, a route is automatically entered > from the local address to the opposite address. The "corresponding" > in the comment at the beginning of the macro is interpreted rather loosely. From http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/in_var.h : > Backout damage to the INADDR_TO_IFP() macro in revision 1.7. > > This macro was supposed to only match local IP addresses of > interfaces, so, this comment supports the idea that the macro itself was incorrect. > and all consumers of this macro assume this as > well. (See IP_MULTICAST_IF and IP_ADD_MEMBERSHIP socket > options in the ip(4) manpage.) > > This fixes a major security breach in IPFW-based firewalls Actually, this doesn't (didn't) and Ruslan (ru@freebsd.org) was wrong pointing out this in the comment... It was just a mistake affecting to remote peer only. Local ip anyway was protected with 'me'. (it did fit to the macros as well as remote ip did and this fact is the only erroneous in the situation) > where the `me' keyword would match the other end of a P2P > link. > > PR: kern/28567 -- Igor mailto:poige@morning.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 22:43:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 885) id 342AB37B403; Tue, 17 Jul 2001 22:43:44 -0700 (PDT) Date: Tue, 17 Jul 2001 22:43:44 -0700 From: Eric Melville To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Cc: hackers@FreeBSD.org Subject: Re: cvs commit: src/gnu/lib/libdialog checklist.c menubox.c radiolist.c textbox.c tree.c yesno.c Message-ID: <20010717224344.A9904@FreeBSD.org> References: <200107180521.f6I5Lbg64954@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107180521.f6I5Lbg64954@freefall.freebsd.org>; from eric@FreeBSD.org on Tue, Jul 17, 2001 at 10:21:37PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Modified files: > gnu/lib/libdialog checklist.c menubox.c radiolist.c > textbox.c tree.c yesno.c > Log: > Improve the interface provided by libdialog. Move a cursor around over > the components and trigger actions based on its position. This reduces > the need to remember the functions of various keys, and makes the > interface more consistant across library. This eliminates the problem where people would exit a menu when they really wanted to select an item (the space/enter confusion), amongst other things. I intend to MFC this sometime before 4.4-RELEASE, potentially along with some things people from mailing lists have submitted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 17 23:54:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id B421637B403 for ; Tue, 17 Jul 2001 23:54:43 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f6I6sgF27272; Wed, 18 Jul 2001 00:54:42 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f6I6sdo46972; Wed, 18 Jul 2001 00:54:40 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107180654.f6I6sdo46972@harmony.village.org> To: bmah@packetdesign.com Subject: Re: Development for older FreeBSD releases Cc: Greg Black , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 11 Jul 2001 14:32:18 PDT." <200107112132.f6BLWNb81831@nimitz.packetdesign.com> References: <200107112132.f6BLWNb81831@nimitz.packetdesign.com> <200107112113.f6BLDgQ81686@nimitz.packetdesign.com> Date: Wed, 18 Jul 2001 00:54:39 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200107112132.f6BLWNb81831@nimitz.packetdesign.com> Bruce A. Mah writes: : Unfortunately it's not guaranteed...a lot of new hardware has been : released since December 1998 (the date of 2.2.8-RELEASE). :-p Copy the 2.2.8 cdrom onto a disk. Put your sources in that tree. Chroot. you now have the 2.2.8 compilers. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 0:29:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by hub.freebsd.org (Postfix) with ESMTP id B0BAD37B405; Wed, 18 Jul 2001 00:29:48 -0700 (PDT) (envelope-from stijn@pcwin002.win.tue.nl) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.11.4/8.11.4) id f6I7Tja13408; Wed, 18 Jul 2001 09:29:45 +0200 (CEST) (envelope-from stijn) Date: Wed, 18 Jul 2001 09:29:45 +0200 From: Stijn Hoop To: Eric Melville Cc: hackers@freebsd.org Subject: Re: cvs commit: src/gnu/lib/libdialog checklist.c menubox.c radiolist.c textbox.c tree.c yesno.c Message-ID: <20010718092945.A13105@pcwin002.win.tue.nl> References: <200107180521.f6I5Lbg64954@freefall.freebsd.org> <20010717224344.A9904@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010717224344.A9904@FreeBSD.org>; from eric@freebsd.org on Tue, Jul 17, 2001 at 10:43:44PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jul 17, 2001 at 10:43:44PM -0700, Eric Melville wrote: > > Modified files: > > gnu/lib/libdialog checklist.c menubox.c radiolist.c > > textbox.c tree.c yesno.c > > Log: > > Improve the interface provided by libdialog. Move a cursor around over > > the components and trigger actions based on its position. This reduces > > the need to remember the functions of various keys, and makes the > > interface more consistant across library. > > This eliminates the problem where people would exit a menu when they really > wanted to select an item (the space/enter confusion), amongst other things. *THANK YOU* I can't tell any more how many times this annoying libdialog has bitten me in this regard. > I intend to MFC this sometime before 4.4-RELEASE, potentially along with > some things people from mailing lists have submitted. Even better - I take it sysinstall then uses 'sane' space/enter combo's also (it being a consumer of libdialog)? --Stijn -- I wish there was a knob on the TV to turn up the intelligence. There's a knob called `brightness', but it doesn't work." -- Gallagher To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 0:53:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f197.law11.hotmail.com [64.4.17.197]) by hub.freebsd.org (Postfix) with ESMTP id 54B9037B401; Wed, 18 Jul 2001 00:53:46 -0700 (PDT) (envelope-from anandfranklin@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 18 Jul 2001 00:53:46 -0700 Received: from 203.200.20.3 by lw11fd.law11.hotmail.msn.com with HTTP; Wed, 18 Jul 2001 07:53:45 GMT X-Originating-IP: [203.200.20.3] From: "Anand Franklin J" To: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: Hi(some clarifcation about sysctl usage in ifconfig) Date: Wed, 18 Jul 2001 07:53:45 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 18 Jul 2001 07:53:46.0062 (UTC) FILETIME=[C5A916E0:01C10F5E] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, The below code is part of ifconfig which use sysctl: 1:mib[0] = CTL_NET; 2:mib[1] = PF_ROUTE; 3:mib[2] = 0; 4:mib[3] = 0; /* address family */ 5:mib[4] = NET_RT_IFLIST; 6:mib[5] = 0; /* if particular family specified, only ask about it */ 7:if (afp) 8: mib[3] = afp->af_af; 9:if (sysctl(mib, 6, NULL, &needed, NULL, 0) < 0) 10: errx(1, "iflist-sysctl-estimate"); 11:if ((buf = malloc(needed)) == NULL) errx(1, "malloc"); 12:if (sysctl(mib, 6, buf, &needed, NULL, 0) < 0) errx(1, "actual retrieval of interface table"); the doubts are: 1) what is the purpose of the above c statements. 2)how are the mib values stored before finding its value line from 1->8 3)line from 9->11 is clear, that is it finds the length of the buffer to be allocated. 4)what is the significance of line 12 and what will the buf variable will contain. with regard's franklin. _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 1: 7: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 6FCD937B405 for ; Wed, 18 Jul 2001 01:07:05 -0700 (PDT) (envelope-from fmela0@sm.socccd.cc.ca.us) Received: from sm.socccd.cc.ca.us (pool0116.cvx4-bradley.dialup.earthlink.net [209.178.146.116]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA19551 for ; Wed, 18 Jul 2001 01:07:04 -0700 (PDT) Message-ID: <3B554445.193CE946@sm.socccd.cc.ca.us> Date: Wed, 18 Jul 2001 01:09:41 -0700 From: Farooq Mela X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Quick question about x86 asm Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi -hackers, I'm developing some assembly routines that are called from a C library under FreeBSD. Some of these routines do not return anything (ie, prototyped in C, their return type is 'void'). Does the compiler expect that the asm routines that don't return anything will preserve the value of %eax? That is, must we push it and later pop it before returning from the routine, or are we free to modify it as we please without restoring its value to what it was when the routine was called? Thanks. -- farooq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 2: 7:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 3FE5637B406 for ; Wed, 18 Jul 2001 02:07:37 -0700 (PDT) (envelope-from brandt@fokus.gmd.de) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id LAA12077 for ; Wed, 18 Jul 2001 11:07:35 +0200 (MET DST) Date: Wed, 18 Jul 2001 11:07:35 +0200 (CEST) From: Harti Brandt To: Subject: Format checking for sbuf_printf... Message-ID: <20010718110432.P20739-100000@beagle.fokus.gmd.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hello, given that the various printf's in systm.h are format-checked, it probably makes sense to add this to sbuf_printf also. Could somebody please commit this? harti Index: sbuf.h =================================================================== RCS file: /usr/ncvs/src/sys/sys/sbuf.h,v retrieving revision 1.6 diff -c -r1.6 sbuf.h *** sbuf.h 2001/07/03 21:46:42 1.6 --- sbuf.h 2001/07/17 12:05:28 *************** *** 58,64 **** int sbuf_bcpy(struct sbuf *s, const char *str, size_t len); int sbuf_cat(struct sbuf *s, const char *str); int sbuf_cpy(struct sbuf *s, const char *str); ! int sbuf_printf(struct sbuf *s, const char *fmt, ...); int sbuf_putc(struct sbuf *s, int c); int sbuf_overflowed(struct sbuf *s); void sbuf_finish(struct sbuf *s); --- 58,64 ---- int sbuf_bcpy(struct sbuf *s, const char *str, size_t len); int sbuf_cat(struct sbuf *s, const char *str); int sbuf_cpy(struct sbuf *s, const char *str); ! int sbuf_printf(struct sbuf *s, const char *fmt, ...) __printflike(2, 3); int sbuf_putc(struct sbuf *s, int c); int sbuf_overflowed(struct sbuf *s); void sbuf_finish(struct sbuf *s); -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 3: 1: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f49.law3.hotmail.com [209.185.241.49]) by hub.freebsd.org (Postfix) with ESMTP id E2D1737B406 for ; Wed, 18 Jul 2001 03:00:57 -0700 (PDT) (envelope-from drinkster3@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 18 Jul 2001 03:00:57 -0700 Received: from 195.74.96.17 by lw3fd.law3.hotmail.msn.com with HTTP; Wed, 18 Jul 2001 10:00:57 GMT X-Originating-IP: [195.74.96.17] From: "Richard Drinkwater" To: freebsd-hackers@freebsd.org Subject: Pspell/Aspell ports compilation Date: Wed, 18 Jul 2001 11:00:57 +0100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 18 Jul 2001 10:00:57.0837 (UTC) FILETIME=[8A8D89D0:01C10F70] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm currently trying to get pspell compiled into PHP, and make pspell use the aspell library. I have managed to get it to work on one box, using 4.3 release, without any trouble, but I can't get it to repeat. When I load something that links to the pspell module which plugs into aspell it claims that the "apsell module cannot be loaded" despite the fact the the DSO is there. The DSO is in LD_LIBRARY_PATH and everything has compiled correctly. Anyone have any ideas why this might be happening and how to fix it? Richard _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 6:29:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from jhs.muc.de (jhs.muc.de [193.149.49.84]) by hub.freebsd.org (Postfix) with ESMTP id E937C37B401 for ; Wed, 18 Jul 2001 06:29:35 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: from park.jhs.private (localhost [127.0.0.1]) by jhs.muc.de (8.11.0/8.11.0) with ESMTP id f6ICMIH77977; Wed, 18 Jul 2001 12:22:18 GMT (envelope-from jhs@park.jhs.private) Message-Id: <200107181222.f6ICMIH77977@jhs.muc.de> To: carlo@vis.ethz.ch (Carlo Dapor) Cc: freebsd-hackers@freebsd.org Subject: Re: CTM is down again In-Reply-To: Message from carlo@vis.ethz.ch (Carlo Dapor) of "Tue, 17 Jul 2001 22:13:10 +0200." <20010717201310.5F62C275B7@naboo.ethz.ch> Date: Wed, 18 Jul 2001 14:22:18 +0200 From: "Julian Stacey Jhs@jhs.muc.de" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Carlo Dapor wrote: > I haven't received any CTMs since July 12th. Am I the only one ? > My guess is that the main distribution point is malfunctioning. Hi, Yes, there is a central problem, being worked on, Announcements on CTM issues are made to ctm-announce@FreeBSD.ORG All ctm recipients should be subscribed to ctm-announce@FreeBSD.ORG if any CTM recipient is not yet subscribed please do so, via majordomo@freebsd.org (& have no fear, it's a very low traffic list, you won't get swamped). Julian J.Stacey Munich Unix (FreeBSD, Linux etc) Consultant http://bim.bsn.com/~jhs/ Ihr Rauchen => mein allergischer Kopfschmerz ! Schnupftabak probieren ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 6:37:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay1.ntu-kpi.kiev.ua (www.ntu-kpi.kiev.ua [212.111.192.161]) by hub.freebsd.org (Postfix) with ESMTP id 32A7437B403 for ; Wed, 18 Jul 2001 06:37:32 -0700 (PDT) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from comsys.ntu-kpi.kiev.ua (eth0.comsys.ntu-kpi.kiev.ua [10.0.1.184]) by relay1.ntu-kpi.kiev.ua (Postfix) with ESMTP id AD9632EF18 for ; Wed, 18 Jul 2001 16:37:23 +0300 (EEST) Received: from pm5149 (pm514-9.comsys.ntu-kpi.kiev.ua [10.18.54.109]) by comsys.ntu-kpi.kiev.ua (8.11.3/8.11.3) with SMTP id f6IDUxt22864 for ; Wed, 18 Jul 2001 16:30:59 +0300 (EEST) Message-ID: <012001c10f85$08ae6b40$6d36120a@comsys.ntukpi.kiev.ua> From: "Andrey Simonenko" To: Subject: libpcap and pthreads Date: Wed, 18 Jul 2001 16:27:39 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, Is it possible to use libpcap with pthreads? (I want to use just pcap_dispatch() function) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 6:37:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay1.ntu-kpi.kiev.ua (www.ntu-kpi.kiev.ua [212.111.192.161]) by hub.freebsd.org (Postfix) with ESMTP id 03E3837B401 for ; Wed, 18 Jul 2001 06:37:32 -0700 (PDT) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from comsys.ntu-kpi.kiev.ua (eth0.comsys.ntu-kpi.kiev.ua [10.0.1.184]) by relay1.ntu-kpi.kiev.ua (Postfix) with ESMTP id A02CB2EFB9; Wed, 18 Jul 2001 16:37:28 +0300 (EEST) Received: from pm5149 (pm514-9.comsys.ntu-kpi.kiev.ua [10.18.54.109]) by comsys.ntu-kpi.kiev.ua (8.11.3/8.11.3) with SMTP id f6IDcKt22883; Wed, 18 Jul 2001 16:38:21 +0300 (EEST) Message-ID: <013001c10f86$0fc53020$6d36120a@comsys.ntukpi.kiev.ua> From: "Andrey Simonenko" To: "Kris Kennaway" Cc: References: <01c201c10468$b6a71e40$6d36120a@comsys.ntukpi.kiev.ua> <20010705143339.A98165@FreeBSD.org> <000901c105ec$61664e80$6d36120a@comsys.ntukpi.kiev.ua> <20010706015003.A49027@xor.obsecurity.org> Subject: Re: Status of dialog(1) and libdialog. Date: Wed, 18 Jul 2001 16:34:59 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: Kris Kennaway Newsgroups: lucky.freebsd.hackers Sent: Friday, July 06, 2001 1:00 PM Subject: Re: Status of dialog(1) and libdialog. > > Just to throw some more fuel onto the fire, Thomas Dickey maintains > his own version of dialog, which is derived from the same parent as > the one in our tree, though somewhat divergent by now (mostly on the > FreeBSD side from local changes/hacks, I think): > > ftp://dickey.his.com/dialog/dialog-0.9a-20010527.tgz > Thanks for URL. I checked this version of Dialog and found out that it inherits bugs which current version of Dialog in FreeBSD has (they both inherit the same bugs from the original version). I tried to fix them, but all patches should be compatible with all programs which use libdialog and this takes some time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 8:48:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id AA72637B403 for ; Wed, 18 Jul 2001 08:48:06 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.138.210.Dial1.SanJose1.Level3.net [209.247.138.210]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id IAA07749; Wed, 18 Jul 2001 08:47:55 -0700 (PDT) Message-ID: <3B55AFD0.65F0C860@mindspring.com> Date: Wed, 18 Jul 2001 08:48:32 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Richard Hodges Cc: hackers@FreeBSD.ORG Subject: Re: NatSemi DP83820 gigE driver kit for 4.2 and 4.3 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Richard Hodges wrote: > > > Now TX buffers are a problem - I have to take what I get and just > > > "deal with it". If both start address and length need to be aligned, > > > then I'm pretty much screwed - I have to copy... > > > > No, exactly ythe opposite: the TX buffer is _not_ a problem. This > > is because it's assembled from mbuf's, so you can actually put it > > on a 16 byte boundary, and index the mbuf into only the forst 14 > > bytes of the packet for the header. > > It is still a problem. If the hardware requires buffer start and length > to be word aligned, I have to copy the entire mbuf chain if it is not > perfectly aligned to start with. The very rare exception is if an mbuf > in the middle just happens to have a length off by exactly the alignment > offset - in that case I can stop there, so long as the rest of the chain > is aligned, of course. This is a very real issue for me (in the form of > the IDT 77211 ATM SAR...) To be fair, this may not be a great example, > since I don't have an ethernet header to worry about. The only issue would be if the DMA on the chip could not support gathering its buffer from multiple sources. This is because you have to at least create mbuf header references (see the "zero copy" NFS code) for the data which you wish to transmit, and seperately create the headers. Unless you are doing headers + 8k payload (e.g. slightly small gigabit "jumbograms"), you aren't going to be able to reference FS buffer cache at an even page boundary (pages are 4k on x86, 8k on Alpha), so it's not like even the sendfile interface DMA's data directly from the disk into the ethernet card. Nor would you want it to do so, really, since it would disable your ability to cache the data, and that would limit you to disk speed, on average. In practice, your disk, not your bus would end up being your speed limiting factor. Even if you had an infinitely fast disk, the transmit buffer on this chip is limited to 8K, so 4K pages may be alright, but 8K pages leave no room for headers. So when you talk about "zero copy", you are generally talking minimally one copy, on data you have on hand (a copy from main memory to card memory), or two copy (a copy from disk or card to main memory to a card) for the data you have to get from somewhere else... in other words, "zero _additional_ copies". In any case, this means your argument doesn't apply to DMA gathering, when transmitting, since the data need not be in contiguous segments of physical RAM -- in other words, the ethernet header can be in a different mbuf cluster than the body of the data, so the body of the data can be alighned, from the host perspective -- and so can the ethernet headers. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 8:58:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from saturn.bsdhome.com (unknown [24.25.2.193]) by hub.freebsd.org (Postfix) with ESMTP id 40F6537B403 for ; Wed, 18 Jul 2001 08:58:38 -0700 (PDT) (envelope-from bsd@bsdhome.com) Received: from neutrino.bsdhome.com (jupiter [192.168.220.13]) by saturn.bsdhome.com (8.11.3/8.11.3) with ESMTP id f6IFwZC19500 for ; Wed, 18 Jul 2001 11:58:36 -0400 (EDT) Received: (from bsd@localhost) by neutrino.bsdhome.com (8.11.4/8.11.4) id f6IFwUF46329 for freebsd-hackers@freebsd.org; Wed, 18 Jul 2001 11:58:30 -0400 (EDT) (envelope-from bsd) Date: Wed, 18 Jul 2001 11:58:25 -0400 From: Brian Dean To: freebsd-hackers@freebsd.org Subject: Re: math library difference between linux emulation and native freebsd (and native linux) Message-ID: <20010718115825.A46264@neutrino.bsdhome.com> References: <200107141809.f6EI9M809946@snoopy.fan.fa.disney.com> <3B530DD6.E3604F32@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B530DD6.E3604F32@mindspring.com>; from tlambert2@mindspring.com on Mon, Jul 16, 2001 at 08:52:54AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG (Choosing a random message to reply to ...) While looking for commercial electronics CAD software for FreeBSD, I came across Whitely Research Inc (http://www.srware.com/) which has this note on their site: http://www.srware.com/linux_numerics.txt In light of this thread, I thought others may be interested in reading this. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 9: 1:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 2A05137B406 for ; Wed, 18 Jul 2001 09:01:38 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f6IG1On41150; Wed, 18 Jul 2001 18:01:28 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Harti Brandt Cc: hackers@FreeBSD.ORG Subject: Re: Format checking for sbuf_printf... In-Reply-To: Your message of "Wed, 18 Jul 2001 11:07:35 +0200." <20010718110432.P20739-100000@beagle.fokus.gmd.de> Date: Wed, 18 Jul 2001 18:01:24 +0200 Message-ID: <41148.995472084@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG done. In message <20010718110432.P20739-100000@beagle.fokus.gmd.de>, Harti Brandt writes: > >hello, > >given that the various printf's in systm.h are format-checked, it probably >makes sense to add this to sbuf_printf also. Could somebody please commit >this? > >harti > >Index: sbuf.h >=================================================================== >RCS file: /usr/ncvs/src/sys/sys/sbuf.h,v >retrieving revision 1.6 >diff -c -r1.6 sbuf.h >*** sbuf.h 2001/07/03 21:46:42 1.6 >--- sbuf.h 2001/07/17 12:05:28 >*************** >*** 58,64 **** > int sbuf_bcpy(struct sbuf *s, const char *str, size_t len); > int sbuf_cat(struct sbuf *s, const char *str); > int sbuf_cpy(struct sbuf *s, const char *str); >! int sbuf_printf(struct sbuf *s, const char *fmt, ...); > int sbuf_putc(struct sbuf *s, int c); > int sbuf_overflowed(struct sbuf *s); > void sbuf_finish(struct sbuf *s); >--- 58,64 ---- > int sbuf_bcpy(struct sbuf *s, const char *str, size_t len); > int sbuf_cat(struct sbuf *s, const char *str); > int sbuf_cpy(struct sbuf *s, const char *str); >! int sbuf_printf(struct sbuf *s, const char *fmt, ...) __printflike(2, 3); > int sbuf_putc(struct sbuf *s, int c); > int sbuf_overflowed(struct sbuf *s); > void sbuf_finish(struct sbuf *s); >-- >harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private > brandt@fokus.gmd.de, harti@begemot.org > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 9: 2:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 4835937B40C for ; Wed, 18 Jul 2001 09:02:20 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.138.210.Dial1.SanJose1.Level3.net [209.247.138.210]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA18161; Wed, 18 Jul 2001 09:02:10 -0700 (PDT) Message-ID: <3B55B328.777D6FA1@mindspring.com> Date: Wed, 18 Jul 2001 09:02:48 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Stefan Hoffmeister Cc: "Albert D. Cahalan" , freebsd-hackers@FreeBSD.ORG, Jim.Pirzyk@disney.com Subject: Re: math library difference between linux emulation and native freebsd (and native linux) References: <200107170615.f6H6FU5376195@saturn.cs.uml.edu> <3B546BA9.37E9F437@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Stefan Hoffmeister wrote: > >One obvious reason that the Linux approach is wrong is > >that it ends up requiring the save and restore of FP > >registers on context switches, which is overhead they > >ate anyway, by doing TSS based context switching. The > >amount of state with SSE is up to something like an > >additional 512 bytes -- that's ungodly overhead, since > >most programs don't use this context at all. > > Except that - AFAIK - Linux won't do that. > > Linux install traps, causing the first FPU and SSE instruction to fault > (might as well be only the SSE instructions). Upon the fault, the context > structure size is switched. > > IOW, Linux does not blindly have an FPU context size of 512 bytes. I didn't say that it did; you need to read more carefully. The part you cut off talked about the consequences of FreeBSD jamming a non-default mask on the FPU, in the context of the FreeBSD Linux ABI. I can think of a tricky way (disable traps, set the mask, reenable them, so as to avoid marking the process), but this will not result in the mask being "right" for the initial FPU utilization of the process... you would end up with a need to do a lot of dancing in the trap code to get this right, and still permit FP context switching, since you would need to take the initial fault, fixup everything _including_ setting the default mask -- and then _only_ for the Linux binaries, and then _only_ if the first FPU instruction was not an attempt to set the mask. This is why FreeBSD does _not_ set the mask to a "default": since the FPU context is lazy-bound, the initial mask you would end up with, unless you did a lot of convoluted stuff, would be the mask of the last FPU-using process that was running, and not the mask you expected. Someone else complained "Linux doesn't do this any more" about my statement "...which is overhead they ate anyway, by doing TSS based context switching..." Yes, I _know_ they don't do this _any more_: hence my use of the verb "ate" (past tense) instead of the verb "eat" (present tense). The statement was to indicate _why_ Linux has an abominable default for the mask, from a historical perspective. The bottom line is that the mask value should _not_ be assumed by correct programs, unless they are intended to rely on the historical Linux default, which is an artifact of their prior context switch algorithm, and not some "good idea", unless your idea of a "good idea" is a convoluted trap handler that requires instruction restart in all but the most trivial cases. I will point, once again, to Mathematica as a "correct" program... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 9:11:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 10B2437B403 for ; Wed, 18 Jul 2001 09:11:33 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.138.210.Dial1.SanJose1.Level3.net [209.247.138.210]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA04921; Wed, 18 Jul 2001 09:11:30 -0700 (PDT) Message-ID: <3B55B557.DADB3107@mindspring.com> Date: Wed, 18 Jul 2001 09:12:07 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Albert D. Cahalan" Cc: freebsd-hackers@FreeBSD.ORG, Jim.Pirzyk@disney.com Subject: Re: math library difference between linux emulation and native freebsd References: <200107171802.f6HI2OV422095@saturn.cs.uml.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Albert D. Cahalan" wrote: > >>> The defaults for the Linux emulator are different than > >>> the defaults for Linux. Linux sets some stuff up wrong, > >> > >> FreeBSD sets stuff up wrong. This is a choice between bad > >> and worse, since the CPU does not support what you want. > > > > FreeBSD complies strictly with the IEEE FP standard. > > As long as you don't ever use "float" or "long double", yes. > The "float" type isn't seriously broken, while "long double" is. Read the standard: the initial state of the mask is undefined by it. > > Linux fails to set 0x37f into the mask before doing > > its calculations, and assumes that the OS has done this > > for it. In Linux it's true, in the emulator, it's not; > > You mean "Linux apps fail to..." I think. > ^^^^ Yes; or more correctly, "incorrect Linux apps fail", since Mathematica is a Linux app, yet does not fail. > Certainly. The initial FPU control word is part of the ABI. > Explicitly setting this would mark a process as being an > FPU user, which would then be shown in "ps" output. > Setting cast-in-stone defaults is also a waste of CPU time. Not to mention what it does to the trap handler for your initial FPU trap. > > One obvious reason that the Linux approach is wrong is > > that it ends up requiring the save and restore of FP > > registers on context switches, which is overhead they > > ate anyway, by doing TSS based context switching. > > No and no. (that was true at one time) "ate" != "eat". See my previous post. I don't need to be corrected: I know how Linux currently operates, and how it has operated historically. IMO, permitting a program using FP to assume that the mask is a specific value before it sets it is as bad as Linux allowing people to use stack crap for the contents of the sockaddr_in struct (a common practice in networking programs written to assume Linux, including the Sun Microsystems SLPv1 reference implementation), or assuming that you can pass a NULL pointer to strcmp()/strcat()/etc., and have the C library treat it as "". > > FreeBSD's settings do not cause problems for FreeBSD; as > > has been observed in this thread, FreeBSD gets the right > > answer when you run the code native, just as Linux does; > > Try again with "long double". Works great... I did mention that I set my FP mask before using FP, because I'm not assuming the state of the mask before my program is marked as an FP-using program, right? > > the emulator gets the wrong answer, but the problem is > > really the programs assuming that the mask will be set > > by the OS to the "magic" correct value. > > It's no worse than assuming /dev/null will exist. Bull. It's infinitely worse. It promotes bad coding practices, a lack of rigor in problem solving, and the assumption that "all the word's Linux" -- which is no better an assumption than "All the world's a VAX". > >> See float_t, double_t, FLT_EVAL_METHOD and FLT_ROUNDS in > >> the 1999 C standard for ways to deal with x86 hardware. > > > > The standards are not x86 specific; the fp*() functions > > are. > > The standards have what you need to deal with x86 hardware. > They give software a way to handle evaluation with excess > fraction bits in intermediate calculations. Yeah: a mask setting function. > Most fp*() functions work great on a SPARC with Solaris. > The precision control isn't quite x86-specific. The i860 > has this problem too AFAIK. Uninitialized behaviour of x86 hardware sucks: what can I say? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 9:19: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 5839037B40B; Wed, 18 Jul 2001 09:19:04 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.138.210.Dial1.SanJose1.Level3.net [209.247.138.210]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA13726; Wed, 18 Jul 2001 09:19:02 -0700 (PDT) Message-ID: <3B55B71C.CA7704BD@mindspring.com> Date: Wed, 18 Jul 2001 09:19:40 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: Matthew Jacob , hackers@FreeBSD.org Subject: Re: x86 unaligned access followup. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > >> Actually, since the 486, it's been possible for us to turn on unaligned > >> access exceptions on the x86. We should probably consider doing this, to > >> ensure better performance, and to avoid the unnecessary bus overhead we > >> eat for unaligned access today... not to mention how it could shake out > >> the drivers. > > > > > > Now *that* is a very cool idea. As Johnny Carson would say "I did not know > > that". How would this be done? I assume it's some bit-flip for the chip? > > D'ya have a sample bit 'o code for this? > > It's the AC bit in eflags. Note that this will not trap 64 bit unaligned accesses, only 32. Also note that this will play hell with some of the recent copy avoidance changes made by Bill Paul to the ethernet drivers, to avoid the expense of copying the packet, with the knowledge that there would be an increased overhead in the resulting packet field unaligned accesses when decoding IP packets... A "shakedown cruise" could end up being very rough... you would effectively need to check an "unaligned access in kernel is OK" flag in many of these instances, and fall back to doing the copy when it was false. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 9:45: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 9F71537B405; Wed, 18 Jul 2001 09:44:56 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.138.210.Dial1.SanJose1.Level3.net [209.247.138.210]) by falcon.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA02119; Wed, 18 Jul 2001 09:44:54 -0700 (PDT) Message-ID: <3B55BD2B.7CB85DF1@mindspring.com> Date: Wed, 18 Jul 2001 09:45:31 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Anand Franklin J Cc: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Hi(some clarifcation about sysctl usage in ifconfig) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Anand Franklin J wrote: > The below code is part of ifconfig which use sysctl: > 1:mib[0] = CTL_NET; > 2:mib[1] = PF_ROUTE; > 3:mib[2] = 0; > 4:mib[3] = 0; /* address family */ > 5:mib[4] = NET_RT_IFLIST; > 6:mib[5] = 0; > > /* if particular family specified, only ask about it */ > 7:if (afp) > 8: mib[3] = afp->af_af; > > 9:if (sysctl(mib, 6, NULL, &needed, NULL, 0) < 0) > 10: errx(1, "iflist-sysctl-estimate"); > 11:if ((buf = malloc(needed)) == NULL) > errx(1, "malloc"); > 12:if (sysctl(mib, 6, buf, &needed, NULL, 0) < 0) > errx(1, "actual retrieval of interface table"); > the doubts are: > 1) what is the purpose of the above c statements. > 2)how are the mib values stored before finding its value > line from 1->8 In the kernel. In other words, they are _not_ writable, they are readable from the kernel. > 3)line from 9->11 is clear, that is it finds the length of the buffer to be > allocated. > 4)what is the significance of line 12 and what will the buf variable will > contain. 9->11 calculate the space and allocate a region for storing the interface list. 12 actually retrieves the list into the allocation space provided (buf). After it runs, if it runs successfully, it will contain a list of interfaces. Probably you want to look at using getifaddrs(3) instead; see the manual page for this library function. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 9:46:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 352C437B406 for ; Wed, 18 Jul 2001 09:46:57 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.138.210.Dial1.SanJose1.Level3.net [209.247.138.210]) by falcon.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA11415; Wed, 18 Jul 2001 09:46:41 -0700 (PDT) Message-ID: <3B55BD97.A6E40F1E@mindspring.com> Date: Wed, 18 Jul 2001 09:47:19 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Farooq Mela Cc: hackers@FreeBSD.ORG Subject: Re: Quick question about x86 asm References: <3B554445.193CE946@sm.socccd.cc.ca.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Farooq Mela wrote: > > Hi -hackers, > > I'm developing some assembly routines that are called from a C library > under FreeBSD. Some of these routines do not return anything (ie, > prototyped in C, their return type is 'void'). Does the compiler > expect that the asm routines that don't return anything will preserve > the value of %eax? That is, must we push it and later pop it before > returning from the routine, or are we free to modify it as we please > without restoring its value to what it was when the routine was > called? cc -S is your friend. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 10:33:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 9178F37B405 for ; Wed, 18 Jul 2001 10:33:21 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15MvD6-0002vX-00 for freebsd-hackers@FreeBSD.org; Wed, 18 Jul 2001 19:34:08 +0200 From: Sheldon Hearn To: freebsd-hackers@FreeBSD.org Subject: Weird problem in 4.3-STABLE Date: Wed, 18 Jul 2001 19:34:08 +0200 Message-ID: <11254.995477648@axl.seasidesoftware.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi folks, I'm busy developing a libdaemon implementation and have come unstuck on a weird problem with functions using variable argument lists in FreeBSD 4.3-STABLE. What I really want is a static inline void function declared in a header file and included in various source files, looking something like this: static inline void xdaemonwarn(char *fmt, ...) { va_list ap; va_start(ap, fmt); if (!daemon_quiet) warn(fmt, ap); va_end(ap); return; } GCC gives "syntax error before 'void'". Fair enough. So obviously, this should be implemented as a macro. But GCC warns that ANSI C doesn't support variable arguments to macros. Fine. So I give up on any semblence of efficiency and settle for a real wrapper. This is where things get interesting. The stdarg(3) manual page says this: Unlike the varargs macros, the stdarg macros do not permit programmers to code a function with no fixed arguments. This problem generates work mainly when converting varargs code to stdarg code, but it also creates difficulties for variadic functions that wish to pass all of their argu­ ments on to a function that takes a va_list argument, such as vfprintf(3). This shouldn't apply to what I'm trying to do, because I have one fixed argument. However, the non-static, non-inline version of the code fragment above, although compiling flawlessly, has trouble at runtime. I call it with two arguments: /* char *path = "/var/run/progname.pid"; */ xdaemonwarn("mkpidfile: %s", path); I get: progname: mkpidfile: : permission denied where represents some high ascii rubbish! So far, the only way I can make this work is: 1) Declare the wrapper functions as taking a bogus, unused first parameter that is an int: void xdaemonwarn(int i __unused, const char *fmt, ...) { ... 2) In the prototype provided to dependent code (via private.h, which CAN'T be included by xdaemonwarn.c), "lie" about the function as follows: void xdaemonwarn(const char *fmt, ...); 3) In the dependent code, call the function as per the lie: /* char *path = "/var/run/progname.pid"; */ xdaemonwarn("mkpidfile: %s", path); This works as expected. I get no warnings from GCC with -Wall -ansi -pedantic and the dependent code prints the expected output. So, um, what the fsck is going on here? :-) Ciao Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 10:43:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.39]) by hub.freebsd.org (Postfix) with SMTP id E8E5237B408 for ; Wed, 18 Jul 2001 10:43:05 -0700 (PDT) (envelope-from roam@ringworld.nanolink.com) Received: (qmail 1176 invoked by uid 1000); 18 Jul 2001 17:47:15 -0000 Date: Wed, 18 Jul 2001 20:47:15 +0300 From: Peter Pentchev To: Sheldon Hearn Cc: freebsd-hackers@FreeBSD.org Subject: Re: Weird problem in 4.3-STABLE Message-ID: <20010718204715.C635@ringworld.oblivion.bg> Mail-Followup-To: Sheldon Hearn , freebsd-hackers@FreeBSD.org References: <11254.995477648@axl.seasidesoftware.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <11254.995477648@axl.seasidesoftware.co.za>; from sheldonh@starjuice.net on Wed, Jul 18, 2001 at 07:34:08PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jul 18, 2001 at 07:34:08PM +0200, Sheldon Hearn wrote: > > Hi folks, > > I'm busy developing a libdaemon implementation and have come unstuck on > a weird problem with functions using variable argument lists in FreeBSD > 4.3-STABLE. > > What I really want is a static inline void function declared in a header > file and included in various source files, looking something like this: > > static inline void > xdaemonwarn(char *fmt, ...) > { > va_list ap; > > va_start(ap, fmt); > if (!daemon_quiet) > warn(fmt, ap); > va_end(ap); > > return; > } Errrrrr. Snipped the rest, since this code snippet contains an important mistake. warn() does not take a va_list as an argument. Try using vwarn(fmt, ap) instead, and your function looks fine. G'luck, Peter -- I've heard that this sentence is a rumor. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 10:43:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 35DC537B401 for ; Wed, 18 Jul 2001 10:43:23 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id C97D83E35; Wed, 18 Jul 2001 10:43:17 -0700 (PDT) To: Sheldon Hearn Cc: freebsd-hackers@FreeBSD.org Subject: Re: Weird problem in 4.3-STABLE In-Reply-To: <11254.995477648@axl.seasidesoftware.co.za>; from sheldonh@starjuice.net on "Wed, 18 Jul 2001 19:34:08 +0200" Date: Wed, 18 Jul 2001 10:43:17 -0700 From: Dima Dorfman Message-Id: <20010718174317.C97D83E35@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sheldon Hearn writes: > static inline void > xdaemonwarn(char *fmt, ...) > { > va_list ap; > > va_start(ap, fmt); > if (!daemon_quiet) > warn(fmt, ap); ^^^^^^ Shouldn't this be `vwarn'? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 10:47:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.39]) by hub.freebsd.org (Postfix) with SMTP id 7F63837B403 for ; Wed, 18 Jul 2001 10:47:23 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 1239 invoked by uid 1000); 18 Jul 2001 17:51:34 -0000 Date: Wed, 18 Jul 2001 20:51:34 +0300 From: Peter Pentchev To: Sheldon Hearn Cc: freebsd-hackers@FreeBSD.org Subject: Re: Weird problem in 4.3-STABLE Message-ID: <20010718205134.D635@ringworld.oblivion.bg> Mail-Followup-To: Sheldon Hearn , freebsd-hackers@FreeBSD.org References: <11254.995477648@axl.seasidesoftware.co.za> <20010718204715.C635@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010718204715.C635@ringworld.oblivion.bg>; from roam@orbitel.bg on Wed, Jul 18, 2001 at 08:47:15PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jul 18, 2001 at 08:47:15PM +0300, Peter Pentchev wrote: > On Wed, Jul 18, 2001 at 07:34:08PM +0200, Sheldon Hearn wrote: > > > > Hi folks, > > > > I'm busy developing a libdaemon implementation and have come unstuck on > > a weird problem with functions using variable argument lists in FreeBSD > > 4.3-STABLE. > > > > What I really want is a static inline void function declared in a header > > file and included in various source files, looking something like this: > > > > static inline void > > xdaemonwarn(char *fmt, ...) > > { > > va_list ap; > > > > va_start(ap, fmt); > > if (!daemon_quiet) > > warn(fmt, ap); > > va_end(ap); > > > > return; > > } > > Errrrrr. Snipped the rest, since this code snippet contains > an important mistake. > > warn() does not take a va_list as an argument. > Try using vwarn(fmt, ap) instead, and your function looks fine. To elaborate a bit: a va_list is a pointer to a memory area where the arguments are stored; a '...' means that this actual memory area lies on the stack. Thus, a va_list is a *pointer* to what warn() expects, and it is exactly this pointer that vwarn() needs. G'luck, Peter -- I am jealous of the first word in this sentence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 11: 8:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sneakerz.org (sneakerz.org [216.33.66.254]) by hub.freebsd.org (Postfix) with ESMTP id 43A5437B406 for ; Wed, 18 Jul 2001 11:08:32 -0700 (PDT) (envelope-from bright@sneakerz.org) Received: by sneakerz.org (Postfix, from userid 1092) id C6D595D010; Wed, 18 Jul 2001 13:08:21 -0500 (CDT) Date: Wed, 18 Jul 2001 13:08:21 -0500 From: Alfred Perlstein To: Sheldon Hearn Cc: freebsd-hackers@FreeBSD.org Subject: Re: Weird problem in 4.3-STABLE Message-ID: <20010718130821.J28164@sneakerz.org> References: <11254.995477648@axl.seasidesoftware.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <11254.995477648@axl.seasidesoftware.co.za>; from sheldonh@starjuice.net on Wed, Jul 18, 2001 at 07:34:08PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Sheldon Hearn [010718 12:33] wrote: > > Hi folks, > > I'm busy developing a libdaemon implementation and have come unstuck on > a weird problem with functions using variable argument lists in FreeBSD > 4.3-STABLE. > > What I really want is a static inline void function declared in a header > file and included in various source files, looking something like this: > > static inline void > xdaemonwarn(char *fmt, ...) > { > va_list ap; > > va_start(ap, fmt); > if (!daemon_quiet) > warn(fmt, ap); > va_end(ap); > > return; > } > > GCC gives "syntax error before 'void'". Fair enough. > > So obviously, this should be implemented as a macro. But GCC warns that > ANSI C doesn't support variable arguments to macros. Fine. I think you have a problem with inline actually. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 11:13:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx2.magma.ca (mx2.magma.ca [206.191.0.250]) by hub.freebsd.org (Postfix) with ESMTP id 74CD237B405 for ; Wed, 18 Jul 2001 11:13:55 -0700 (PDT) (envelope-from louisphilippe@macadamian.com) Received: from mail3.magma.ca (mail3.magma.ca [206.191.0.221]) by mx2.magma.ca (8.9.3/8.9.3) with ESMTP id OAA21448; Wed, 18 Jul 2001 14:13:54 -0400 (EDT) Received: from durandal (mothership.macadamian.com [206.191.21.204]) by mail3.magma.ca (8.9.3/8.9.3) with SMTP id OAA18620; Wed, 18 Jul 2001 14:13:54 -0400 (EDT) Message-ID: <1f9c01c10fb5$3d4ba770$2964a8c0@macadamian.com> From: "Louis-Philippe Gagnon" To: Cc: "Stephane Lussier" Subject: flock/pthread bug? Date: Wed, 18 Jul 2001 14:12:43 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I've been looking for a way to get inter-process synchronization between multithreaded processes. (I need synchronized access to an area of shared memory between multiple instances of the same process) Since I was using SysV shared memory, I had first thought of using SysV semaphores for synchronization; however, the functions semop, semctl (etc) don't seem to be pthread-aware, so that if a semop() call blocks, the entire process is blocked instead of only the calling thread. I then looked at the pthread mutexes, but it looks like the FreeBSD implementation doesn't support PTHREAD_PROCESS_SHARED (at least in 4.3-release; has this changed in -stable or -current?) Then I found out about the flock() function; the man page mentions a different implementation for threaded and non-threaded libraries, so I though this would work with pthreads. This does not appear to be the case. If one program locks a file with flock(LOCK_EX), the next program that tries to lock will be suspended completely, instead of only the calling thread. Given this program : #include #include #include #include void *printf_thread(void *p) { while(1) printf("#"); } void main(void) { pthread_t t; int fd; fd = open("lockfile",O_WRONLY|O_CREAT, 0666); pthread_create(&t,NULL,printf_thread,NULL); flock(fd,LOCK_EX); pthread_join(t,NULL); } (program opens a file, launches a thread (which calls printf() endlessly), locks the file and waits for ^C) The first instance launched will print an infinity of #'s from its printf_thread The second instance (launced from the sae directory, to use the same lock file) will not print anything until the first intance is killed. Since the printf_thread is launched before the flock() call, I expected it to keep running while the main thread blocks; instead, both threads apear to be blocked. (I tried on Linux (RH6.1), the program behaves as I expected) I tried another test before this one (don't have the source anymore, I overwrote the same file), which used only one instance of the program, with 2 threads trying to lock the file I expected something like this : thread 1 locks the file thread 2 tries to lock the file, blocks thread 1 unlocks the file thread 2 gets file lock and unblocks Instead I got thread 1 locks the file thread 2 tries to lock the file, whole process blocks (thread 1 is blocked, can't unlock the file : deadlock) So : -Is flock() supposed to block the whole process? -Is my test program wrong? -Does this look like a bug in libc_r? -Is there a better (working) way of getting interprocess synchronization in multithreaded programs? Thanks. Louis-Philippe Gagnon ps. should I submit problem reports immediately in cases like this, or wait for people's opinions first? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 11:19:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from moutvdom01.kundenserver.de (moutvdom01.kundenserver.de [195.20.224.200]) by hub.freebsd.org (Postfix) with ESMTP id D6B3537B401; Wed, 18 Jul 2001 11:19:45 -0700 (PDT) (envelope-from kuehl@lgk.de) Received: from [195.20.224.209] (helo=mrvdom02.schlund.de) by moutvdom01.kundenserver.de with esmtp (Exim 2.12 #2) id 15MvvD-0004b3-00; Wed, 18 Jul 2001 20:19:43 +0200 Received: from p3ee2e2eb.dip0.t-ipconnect.de ([62.226.226.235] helo=heath.lgk.de) by mrvdom02.schlund.de with esmtp (Exim 2.12 #2) id 15MvvC-0005PJ-00; Wed, 18 Jul 2001 20:19:42 +0200 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: <3B55B71C.CA7704BD@mindspring.com> Date: Wed, 18 Jul 2001 20:25:21 +0200 (CEST) Reply-To: kuehl@lgk.de From: kuehl@lgk.de To: Terry Lambert Subject: Re: x86 unaligned access followup. Cc: hackers@FreeBSD.org, Matthew Jacob , John Baldwin Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Jul-01 Terry Lambert wrote: > John Baldwin wrote: >> It's the AC bit in eflags. > > Note that this will not trap 64 bit unaligned accesses, only 32. And only at pl 3... > Also note that this will play hell with some of the recent > copy avoidance changes made by Bill Paul to the ethernet > drivers, to avoid the expense of copying the packet, with > the knowledge that there would be an increased overhead in > the resulting packet field unaligned accesses when decoding > IP packets... > > A "shakedown cruise" could end up being very rough... you > would effectively need to check an "unaligned access in > kernel is OK" flag in many of these instances, and fall back > to doing the copy when it was false. ...therefore - never mind. Perhaps some app code may break. ;-) Lars To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 11:25: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id BF6D037B401 for ; Wed, 18 Jul 2001 11:25:04 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.4/8.11.2) with ESMTP id f6IIOwv08317; Wed, 18 Jul 2001 11:24:59 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3B55B71C.CA7704BD@mindspring.com> Date: Wed, 18 Jul 2001 11:25:06 -0700 (PDT) From: John Baldwin To: Terry Lambert Subject: Re: x86 unaligned access followup. Cc: hackers@FreeBSD.org, Matthew Jacob Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Jul-01 Terry Lambert wrote: > John Baldwin wrote: >> >> Actually, since the 486, it's been possible for us to turn on unaligned >> >> access exceptions on the x86. We should probably consider doing this, to >> >> ensure better performance, and to avoid the unnecessary bus overhead we >> >> eat for unaligned access today... not to mention how it could shake out >> >> the drivers. >> > >> > >> > Now *that* is a very cool idea. As Johnny Carson would say "I did not know >> > that". How would this be done? I assume it's some bit-flip for the chip? >> > D'ya have a sample bit 'o code for this? >> >> It's the AC bit in eflags. > > Note that this will not trap 64 bit unaligned accesses, only 32. > > Also note that this will play hell with some of the recent > copy avoidance changes made by Bill Paul to the ethernet > drivers, to avoid the expense of copying the packet, with > the knowledge that there would be an increased overhead in > the resulting packet field unaligned accesses when decoding > IP packets... > > A "shakedown cruise" could end up being very rough... you > would effectively need to check an "unaligned access in > kernel is OK" flag in many of these instances, and fall back > to doing the copy when it was false. I didn't say it was a good thing, I was just saying how it was done. :) From Bill's description of the network stuff, it sounds like the unaligned access on x86 is cheaper than the copy that would otherwise be done, so we don't want AC checks in that case anyways. > -- Terry -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 11:28:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kjell.utb.falun.se (gw2.falun.se [192.121.234.252]) by hub.freebsd.org (Postfix) with ESMTP id 9536237B401 for ; Wed, 18 Jul 2001 11:28:52 -0700 (PDT) (envelope-from suid@kjell.utb.falun.se) Received: by kjell.utb.falun.se (Postfix, from userid 1000) id 902D2AE08; Wed, 18 Jul 2001 20:29:10 +0200 (CEST) From: suid To: freebsd-hackers@freebsd.org Subject: KLD Programming X-Mailer: VGP Message-Id: <20010718182910.902D2AE08@kjell.utb.falun.se> Date: Wed, 18 Jul 2001 20:29:10 +0200 (CEST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Godday. I'm quite new to KLD-programming and have a question: Is it possible to read/write to files from a module without too much effort, but still staying in kernelspace? /suid- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 11:33: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 4BC1737B40E for ; Wed, 18 Jul 2001 11:33:01 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from jade (jade.cs.binghamton.edu [128.226.140.161]) by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f6IIWuw28109; Wed, 18 Jul 2001 14:32:56 -0400 (EDT) Date: Wed, 18 Jul 2001 14:32:39 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@jade To: suid Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: KLD Programming In-Reply-To: <20010718182910.902D2AE08@kjell.utb.falun.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yes. But it is not easy. Look at code vfs_vnops.c. You can let a user process open a file and then push the file descriptor into kernel via a special system call. Search the mailing list archive and you will find discussions on how to add a new system call. -Zhihui On Wed, 18 Jul 2001, suid wrote: > > Godday. > > I'm quite new to KLD-programming and have a question: > > Is it possible to read/write to files from a module without > too much effort, but still staying in kernelspace? > > > /suid- > > > 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 Jul 18 11:40:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id ABF6A37B406 for ; Wed, 18 Jul 2001 11:40:23 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA95051; Wed, 18 Jul 2001 13:24:54 -0700 (PDT) Date: Wed, 18 Jul 2001 13:24:53 -0700 (PDT) From: Julian Elischer To: Louis-Philippe Gagnon Cc: freebsd-hackers@FreeBSD.ORG, Stephane Lussier Subject: Re: flock/pthread bug? In-Reply-To: <1f9c01c10fb5$3d4ba770$2964a8c0@macadamian.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG probably you should try : #define LOCK_NB 0x04 /* don't block when locking */ Also if you have shared memory, why not use /* Get a spin lock, handle recursion inline (as the less common case) */ #define _getlock_spin_block(mtxp, tid, type) ({ \ int _res = MTX_UNOWNED; \ \ __asm __volatile ( \ " pushfl;" \ " cli;" \ " " MPLOCKED "" \ " cmpxchgl %3,%1;" /* Try */ \ " jz 2f;" /* got it */ \ " pushl %4;" \ " pushl %5;" \ " call mtx_enter_hard;" /* mtx_enter_hard(mtxp, type, oflags) */ \ " addl $12,%%esp;" \ " jmp 1f;" \ "2: popl %2;" /* save flags */ \ "1:" \ "# getlock_spin_block" \ : "+a" (_res), /* 0 */ \ "+m" (mtxp->mtx_lock), /* 1 */ \ "=m" (mtxp->mtx_savecrit) /* 2 */ \ : "r" (tid), /* 3 (input) */ \ "gi" (type), /* 4 */ \ "g" (mtxp) /* 5 */ \ : "cc", "memory", "ecx", "edx" /* used */ ); \ }) (or similar) taken from -current /sys/i386/include/mutex.h. the key is the cmpxchgl instruction. use the cvsweb interface to explore these instructions. (also look at atomic.h I think) On Wed, 18 Jul 2001, Louis-Philippe Gagnon wrote: > Hi, > > I've been looking for a way to get inter-process synchronization between multithreaded processes. (I need synchronized access to > an area of shared memory between multiple instances of the same process) > > Since I was using SysV shared memory, I had first thought of using SysV semaphores for synchronization; however, the functions > semop, semctl (etc) don't seem to be pthread-aware, so that if a semop() call blocks, the entire process is blocked instead of > only the calling thread. > > I then looked at the pthread mutexes, but it looks like the FreeBSD implementation doesn't support PTHREAD_PROCESS_SHARED (at > least in 4.3-release; has this changed in -stable or -current?) > > Then I found out about the flock() function; the man page mentions a different implementation for threaded and non-threaded > libraries, so I though this would work with pthreads. > > This does not appear to be the case. If one program locks a file with flock(LOCK_EX), the next program that tries to lock will be > suspended completely, instead of only the calling thread. > > Given this program : > > #include > > #include > #include > #include > > void *printf_thread(void *p) > { > while(1) > printf("#"); > } > > void main(void) > { > pthread_t t; > int fd; > > fd = open("lockfile",O_WRONLY|O_CREAT, 0666); > pthread_create(&t,NULL,printf_thread,NULL); > flock(fd,LOCK_EX); > pthread_join(t,NULL); > } > > (program opens a file, launches a thread (which calls printf() endlessly), locks the file and waits for ^C) > > The first instance launched will print an infinity of #'s from its printf_thread > The second instance (launced from the sae directory, to use the same lock file) will not print anything until the first intance is > killed. Since the printf_thread is launched before the flock() call, I expected it to keep running while the main thread blocks; > instead, both threads apear to be blocked. > > (I tried on Linux (RH6.1), the program behaves as I expected) > > I tried another test before this one (don't have the source anymore, I overwrote the same file), which used only one instance of > the program, with 2 threads trying to lock the file > I expected something like this : > thread 1 locks the file > thread 2 tries to lock the file, blocks > thread 1 unlocks the file > thread 2 gets file lock and unblocks > > Instead I got > thread 1 locks the file > thread 2 tries to lock the file, whole process blocks > (thread 1 is blocked, can't unlock the file : deadlock) > > So : > -Is flock() supposed to block the whole process? > -Is my test program wrong? > -Does this look like a bug in libc_r? > -Is there a better (working) way of getting interprocess synchronization in multithreaded programs? > > Thanks. > > Louis-Philippe Gagnon > > ps. should I submit problem reports immediately in cases like this, or wait for people's opinions first? > > > > > 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 Jul 18 11:50: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx2.magma.ca (mx2.magma.ca [206.191.0.250]) by hub.freebsd.org (Postfix) with ESMTP id EF9DC37B406 for ; Wed, 18 Jul 2001 11:50:02 -0700 (PDT) (envelope-from louisphilippe@macadamian.com) Received: from mail3.magma.ca (mail3.magma.ca [206.191.0.221]) by mx2.magma.ca (8.9.3/8.9.3) with ESMTP id OAA00211; Wed, 18 Jul 2001 14:50:03 -0400 (EDT) Received: from durandal (mothership.macadamian.com [206.191.21.204]) by mail3.magma.ca (8.9.3/8.9.3) with SMTP id OAA27370; Wed, 18 Jul 2001 14:50:02 -0400 (EDT) Message-ID: <1fbd01c10fba$499834d0$2964a8c0@macadamian.com> From: "Louis-Philippe Gagnon" To: "Julian Elischer" Cc: References: Subject: Re: flock/pthread bug? Date: Wed, 18 Jul 2001 14:48:51 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: "Julian Elischer" > probably you should try : > > #define LOCK_NB 0x04 /* don't block when locking */ > But I do want to block; I just don't want the whole process to block. > Also if you have shared memory, why not use > > /* Get a spin lock, handle recursion inline (as the less common case) */ [snip inline asembly] > the key is the cmpxchgl instruction. > > use the cvsweb interface to explore these > instructions. (also look at atomic.h I think) > Thanks, I'll try to decypher that. I'd rather have something portable though, and I would still like to know if what I was doing should have worked... Louis-Philippe Gagnon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 11:56:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from furby.ispra.webweaving.org (w149.z064000151.sjc-ca.dsl.cnc.net [64.0.151.149]) by hub.freebsd.org (Postfix) with ESMTP id E574D37B401 for ; Wed, 18 Jul 2001 11:56:46 -0700 (PDT) (envelope-from fanf@furby.ispra.webweaving.org) Received: from fanf by furby.ispra.webweaving.org with local (Exim 3.14 #1) id 15MwlH-00063d-00; Wed, 18 Jul 2001 19:13:31 +0000 Date: Wed, 18 Jul 2001 19:13:31 +0000 From: Tony Finch To: Alfred Perlstein Cc: sthaug@nethelp.no, hackers@FreeBSD.ORG, Jef Poskanzer , Tony Finch Subject: Re: thttpd hack for sendfile and accept filters. Message-ID: <20010718191331.F16082@furby.ispra.webweaving.org> References: <20010420044402.L1790@fw.wintelcom.net> <72342.987768654@verdi.nethelp.no> <72342.987768654@verdi.nethelp.no>; <20010420052337.O1790@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010420052337.O1790@fw.wintelcom.net> Organization: dotat labs Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > >The easiest way would be to have thttpd fork after listening a >pre-determined amount of servers, then they'll all compete calling >accept() to grab connections. This is exactly what we did at Demon, which was for a long time the largest thttpd installation, with about 70,000 vhosts on one machine with a few reverse-proxies in front. I think I sent that patch to Jef, but it is hardly rocket science :-) Tony. -- f.a.n.finch FISHER: NORTHEAST 4 OR 5. RAIN LATER. GOOD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 12: 0:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nomad.tor.lets.net (H74.C220.tor.velocet.net [216.138.220.74]) by hub.freebsd.org (Postfix) with SMTP id 7405D37B403 for ; Wed, 18 Jul 2001 12:00:31 -0700 (PDT) (envelope-from steve@nomad.lets.net) Received: (qmail 3802 invoked by uid 1001); 18 Jul 2001 18:55:36 -0000 Date: Wed, 18 Jul 2001 14:55:36 -0400 From: Steve Shorter To: freebsd-hackers@freebsd.org Subject: oidentd issue on FreeBSD 4.3 ? Message-ID: <20010718145536.B3791@nomad.lets.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Howdy! I built oidentd from ports on FreeBSD 4.3 R. Every time oidentd gets querried it logs an error Error: sysctlbyname: Operation not permitted. I can trace this log message to the source file freebsd4.c and the failure of the system call if (sysctlbyname("net.inet.tcp.getcred",... This fails because the sysctl variable net.inet.tcp.getcred does not seem to exist (sysctl -a), I think. I would like to use oidentd but was wondering how to enable the proper sysctl variable or if you know of some other fix, or what I have done wrong. thanx - steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 12:47:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from taupo.cs.waikato.ac.nz (taupo.cs.waikato.ac.nz [130.217.241.30]) by hub.freebsd.org (Postfix) with ESMTP id 9222C37B403 for ; Wed, 18 Jul 2001 12:47:52 -0700 (PDT) (envelope-from joerg@taupo.cs.waikato.ac.nz) Received: (from joerg@localhost) by taupo.cs.waikato.ac.nz (8.11.3/8.11.1) id f6IJlZH95007; Thu, 19 Jul 2001 07:47:35 +1200 (NZST) (envelope-from joerg) Date: Thu, 19 Jul 2001 07:47:35 +1200 From: Joerg Micheel To: Andrey Simonenko Cc: freebsd-hackers@freebsd.org Subject: Re: libpcap and pthreads Message-ID: <20010719074735.H94236@cs.waikato.ac.nz> References: <012001c10f85$08ae6b40$6d36120a@comsys.ntukpi.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <012001c10f85$08ae6b40$6d36120a@comsys.ntukpi.kiev.ua>; from simon@comsys.ntu-kpi.kiev.ua on Wed, Jul 18, 2001 at 04:27:39PM +0400 Organization: Dept of Computer Science, University of Waikato, Hamilton, New Zealand Project: WAND - Waikato Applied Network Dynamics, DAG Operating-System: ... powered by FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Privjet Andrey, On Wed, Jul 18, 2001 at 04:27:39PM +0400, Andrey Simonenko wrote: > Is it possible to use libpcap with pthreads? > (I want to use just pcap_dispatch() function) I very much doubt so. It's not possible to use it in any kind of multithreaded applications, even with select() scenarios. They implement the Highlander principle - there can be only one (pcap). Sad. Joerg -- Joerg B. Micheel Email: WAND and NLANR MOAT Email: The University of Waikato, CompScience Phone: +64 7 8384794 Private Bag 3105 Fax: +64 7 8585095 Hamilton, New Zealand Plan: PMA, TINE and the DAG's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 14: 8:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 1BCB537B401 for ; Wed, 18 Jul 2001 14:08:48 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.11.4/8.11.4) with ESMTP id f6IL8jh45225 for ; Thu, 19 Jul 2001 04:08:46 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 19 Jul 2001 04:08:44 +0700 (NSS) From: Max Khon To: freebsd-hackers@freebsd.org Subject: arcnet support for FreeBSD (request for review) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, there! I have made second attempt to implement Arcnet support for FreeBSD (the first was made about two years ago and nothing was ever committed) Current bits can be fetched from http://iclub.nsu.ru/~fjoe/arcnet/ In order to use them you should copy dev/, net/ and modules/ to /sys and apply patches from diffs/ if you are running -current or from diffs-stable/ if you are running stable. The most important part is changes to FreeBSD ARP stuff to support link addresses of length != 6 bytes. Both the driver for SMC 90Cx6 adapters and ARP stuff were ported from NetBSD. At this time I tried to make changes to if_ether.c less intrusive (it is not direct port of NetBSD's if_arp.c). The driver is interoperable with Linux Arcnet drivers and works in RFC1201 and RFC1056 modes. I get about 200K via FTP between -stable and -current machines and now trying to build XFree86 3.3.6 on NFS-mounted ports tree. Any feedback is HIGHLY appreciated. Thanks! /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 14:17:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id A0D6137B408 for ; Wed, 18 Jul 2001 14:17:38 -0700 (PDT) (envelope-from tmoestl@gmx.net) Received: (qmail 1145 invoked by uid 0); 18 Jul 2001 21:17:32 -0000 Received: from pd900c7b5.dip.t-dialin.net (HELO forge.local) (217.0.199.181) by mail.gmx.net (mail01) with SMTP; 18 Jul 2001 21:17:32 -0000 Received: from tmm by forge.local with local (Exim 3.30 #1) id 15Myh8-0001WX-00; Wed, 18 Jul 2001 23:17:22 +0200 Date: Wed, 18 Jul 2001 23:17:22 +0200 From: Thomas Moestl To: freebsd-hackers@freebsd.org Cc: "Kenneth D . Merry" Subject: libdevstat interface changes Message-ID: <20010718231722.A5026@crow.dom2ip.de> Mail-Followup-To: Thomas Moestl , freebsd-hackers@freebsd.org, "Kenneth D . Merry" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I want to add support for reading crash dumps to libdevstat. This will allow iostat and vmstat to fully work on crashdumps (with some additional patches). To give this a reasonable interface, a kvm handle needs to be passed to getnumdevs, getgeneration, getversion, checkversion and getdevs. A NULL argument will cause the old behaviour (sysctls will be used to get the data). Additionally, programs that link with libkdevstat will need to link against libkvm. Because of that, the library version number will need to be bumped. While we are doing that, Kenneth and I think that the library function names should all get a descriptive prefix ("devstat_"), so that devstat library calls can easily be recognized in the sources. Compatability functions will be provided under the old names. Because the interface of the library is relatively small, this will hopefully not add much overhead. The old interface will be marked as deprecated and may be removed some day. A library dependency to libkvm will be added, so that dynamically linked executables can use the new library without having to explicitely link to libkvm. This way, we should hopefully be able to avoid breakage of libdevstat-using programs outside of src/ (there are some in the ports, for example). Does anyone spot style or interface issues or compatability pitfalls with this that I have overlooked? If not, this will probably be committed relatively soon together with the new functions that Kenneth has posted on -audit. Thanks, - thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 14:49:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id E78D237B401; Wed, 18 Jul 2001 14:49:21 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id XAA17386; Wed, 18 Jul 2001 23:49:17 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.4/8.11.4) id f6ILmVP99338; Wed, 18 Jul 2001 23:48:31 +0200 (MET DST) (envelope-from j) Date: Wed, 18 Jul 2001 23:48:31 +0200 From: Joerg Wunsch To: hackers@freebsd.org, current@freebsd.org Subject: Large patchset for the floppy driver Message-ID: <20010718234831.D77455@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello all, before leaving for vacation next week, i thought i'd put up the result of my work of the last couple of weeks for a review for those who are interested. The patch itself is available at http://people.freebsd.org/~joerg/fdpatch.txt.gz The following README file (see below) is also available at http://people.freebsd.org/~joerg/README.floppy Suggestions are welcome, but keep in mind that i won't have the opportunity to reply within ca. the next three weeks. ====================================================================== Many changes and improvements to the floppy driver. First of all, something i've meant to implement for years now, but never came around: automatic format (density) selection for the major medium formats. That is, you can stuff your 720 KB medium into your 1.44 MB drive, and simply access /dev/fd0. No questions asked, it will just handle it. :) (If you ever wondered why this didn't happen before, the answer is very simple: i needed the infrastructure to read a sector ID field before. That was one of the recent additions to the driver.) The driver can now handle FM floppies as well as MFM floppies. The NE765 commands in ne765.h have been redefined to no longer make implicit assumptions about MFM, SK, and MT; the driver adds those bits as required. The entire density handling subsystem with its bloated list of different possible media density and its twisted decisions about which drive can handle what has been completely moved out of the kernel, into fdcontrol(8) where it should have been all the time. It's very simple, the basic device (four low order bits equal 0) is the subdevice with automagic density selection, and subdevices 1 through 15 are available for fixed density assignments. By default, all of the latter are being initialized to the drive's maximum possible density. It's up to fdcontrol(8) to customize those subdevices. Subdevice naming has been liberalized; subdevices `a' through `h' are still implemented as pseudo-partitions which just cause a symlink to be created to the master device. Subdevices of the form .NNNN can be arbitrarily created, where .NNNN means between 1 and 4 digits. So you can now either create your subdevices like fd0.1 through fd0.15, or you can still name them by density (as it used to be now, but with a fixed set of allowable names), as in fd1.800 etc. Automagic density selection honors the unit attention bit (aka. changeline signal). It is checked in Fdopen(), and if it is set, the autoselection is started. If you re-open the same device without changing media, no new autoselection is initiated. Some old hacks have been made right, now that the infrastructure seems to be in place. There's no longer a configuration flag to fdc(4) that tells there should be a single 1.44 MB drive assumed without probing. On non-i386 architectures, there's no longer an assumption that all the world is an 1.44 MB drive; on i386 architectures there's no longer the assumption that you could only have two drives that need to be mentioned in the RTC (although you need more than one controller for more drives, and i haven't tested that yet). Drive configuration is now handled through device hints and a `flags' value per drive: the lower 4 bits define the drive type (like in i386 RTC, but shifted right by 4), bit 0x10 disables changeline support, bit 0x20 forces the device to probe successfully without making a seek test first. On i386 architectures, if the device type hasn't been set by the flags, and the fd unit number is 0 or 1, the CMOS RTS is still queried as it used to be (but you could now override this). (Detection of the i386 architecture has been changed to test for _MACHINE_ARCH instead of testing whether we are compiling on __i386__.) O_NONBLOCK handling has been added to support formatting on a device that is normally using density autoselection. Obviously, you cannot autoselect the density of an unformatted medium :), so O_NONBLOCK seemed to be the best way out. Only a limited subset of ioctls is possible in nonblocking mode, then you need to clear the flags with fcntl in order to perform actual IO. Some things in the density structure have been changed: there certainly won't be more than two steps between cylinder, so we can singly fold this feature into a flag bit, where the remaining bits can be used otherwise (currently for MFM vs. FM, and for perpendicular recording which is needed for 2.88 media). There's now a field that allows to specify an offset for the sector numbers on side 2; some very old media used to be formatted that way (and Bruce Evans still has some :). A number of further ioctls have been added to obtain driver and device information. Used in fdcontrol and fdformat. fdcontrol(8) has been heavily rewritten. Densities can be specified in kilobytes, and will then be selected from per-drive type tables, or they can be specified as a feature string (currently only explained in fdsupport.c). A feature string is a comma-separated list of numbers and flag values, where any omitted value defaults to the setting that is currently present (or has been assigned by -f before). The same consistent handling (using the same functions) has been integrated into fdformat(1), replacing all the options there that used up almost all the letters of the abc... ;-) Both utilites now use sysexits(3) for their exit values. TODOs and known Bugs: Some rc script needs to be written to auto-assign twisted density definitions (as we used to have by now) to the various devices. The infrastructure is there, if you just call "fdcontrol /dev/fd0" you get a short description of the drive type (1.44M, 360K etc.), so the rc script can poll all /dev/fd? devices, and call fdcontrol with an appropriate list of possible densities for that drive type. (It should also optionally chmod g+w all those devices, since floppy disk usage is quite more comparable to tape usage than to disk device usage.) The attempt to obtain drive flags from the hints currently fails, and always returns 0. I'm doing something seriously wrong there, but by now could not find /what/. Thus, all the nitty-gritty details about drive flags currently Just Don't Work[tm]. 2.88 MB floppies need to be handled. Should i ever get my 2.88 drive to work, i'll do that. By now, they are ifdef'ed out to 1.44 everywhere. All documentation updates still need to be written. fdwrite(1) needs to be checked whether some of the fdformat(1) changes apply there as well. KLD loading of fdc.ko by now only works for the Y-E data PCMCIA floppy, or for ISA FDCs if you load the KLD first time from within the FORTH loader. Unloading and re-loading it later works then. This seems to be some bug with the bus resource handling, and/or hints processing. Something is totally fishy with formatting on 1.2 MB drives. Maybe it's just the drive i'm using for testing, i don't know. Neither DD or HD media formatted correctly for me, although a 1.44 MB drive on the same controller worked. Formatting weird formats sometimes seems to produce surprises. An attempt to format a 26*128 FM floppy (on a 3.5" DD medium) yielded only head 1 sector IDs recorded, and only wrong cylinder numbers. Needs a bit more investigation. Could be related to the 1.2 MB drive formatting problem. Device hints need to be changed (in particular on !i386 architectures). Of course, this requires that we properly detect the drive flags from the hints first. ;-) -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL 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 Wed Jul 18 14:51: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.quidel.com (webmail.quidel.com [63.125.144.4]) by hub.freebsd.org (Postfix) with ESMTP id 9DFF537B403 for ; Wed, 18 Jul 2001 14:51:01 -0700 (PDT) (envelope-from et@quidel.com) Received: by mail.quidel.com with Internet Mail Service (5.5.2653.19) id ; Wed, 18 Jul 2001 14:58:09 -0700 Message-ID: <9D4A4E19244ED4119BE90050DAD5DD47BC5549@mail.quidel.com> From: Etienne de Bruin To: "'freebsd-hackers@freebsd.org'" Subject: release.8 (4.3-RELEASE) Date: Wed, 18 Jul 2001 14:58:03 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I was reading the Makefile in /usr/src/release and wondering about the for dir in bin sbin ; do \ ln -sf /stand $$dir; \ done part in release.8 - it is my understanding that all that is under /stand is linked to files in $$dir. What does this accomplish? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 15: 2:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 177D337B406 for ; Wed, 18 Jul 2001 15:02:35 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f6IM2WD16988; Wed, 18 Jul 2001 18:02:32 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200107180654.f6I6sdo46972@harmony.village.org> References: <200107112132.f6BLWNb81831@nimitz.packetdesign.com> <200107112113.f6BLDgQ81686@nimitz.packetdesign.com> <200107180654.f6I6sdo46972@harmony.village.org> Date: Wed, 18 Jul 2001 18:02:30 -0400 To: Warner Losh , bmah@packetdesign.com From: Garance A Drosihn Subject: Re: Development for older FreeBSD releases Cc: freebsd-hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 12:54 AM -0600 7/18/01, Warner Losh wrote: >Bruce A. Mah writes: >: Unfortunately it's not guaranteed...a lot of new hardware has been >: released since December 1998 (the date of 2.2.8-RELEASE). :-p > >Copy the 2.2.8 cdrom onto a disk. Put your sources in that tree. >Chroot. you now have the 2.2.8 compilers. Ooo. That's clever, and pretty simple to do. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 15: 6:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id F093A37B403 for ; Wed, 18 Jul 2001 15:06:05 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.4/8.11.2) with ESMTP id f6IM5lv11521; Wed, 18 Jul 2001 15:05:48 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <9D4A4E19244ED4119BE90050DAD5DD47BC5549@mail.quidel.com> Date: Wed, 18 Jul 2001 15:05:57 -0700 (PDT) From: John Baldwin To: Etienne de Bruin Subject: RE: release.8 (4.3-RELEASE) Cc: "freebsd-hackers@freebsd.org" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Jul-01 Etienne de Bruin wrote: > I was reading the Makefile in /usr/src/release and wondering about the > > for dir in bin sbin ; do \ > ln -sf /stand $$dir; \ > done > > part in release.8 - it is my understanding that all that is under /stand is > linked to files in $$dir. > > What does this accomplish? No, it links $$dir to /stand. This creates /sbin and /bin directories so that you can still see /bin/ls even though ls is really in /stand/ls. This is to make a "normal" path work right, and to allow scripts which assume the default location of utilities work. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 15:10: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 7417237B403 for ; Wed, 18 Jul 2001 15:09:52 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f6IM9oF30092; Wed, 18 Jul 2001 16:09:51 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f6IM9oo51937; Wed, 18 Jul 2001 16:09:50 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107182209.f6IM9oo51937@harmony.village.org> To: Garance A Drosihn Subject: Re: Development for older FreeBSD releases Cc: bmah@packetdesign.com, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 18 Jul 2001 18:02:30 EDT." References: <200107112132.f6BLWNb81831@nimitz.packetdesign.com> <200107112113.f6BLDgQ81686@nimitz.packetdesign.com> <200107180654.f6I6sdo46972@harmony.village.org> Date: Wed, 18 Jul 2001 16:09:50 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message Garance A Drosihn writes: : At 12:54 AM -0600 7/18/01, Warner Losh wrote: : >Bruce A. Mah writes: : >: Unfortunately it's not guaranteed...a lot of new hardware has been : >: released since December 1998 (the date of 2.2.8-RELEASE). :-p : > : >Copy the 2.2.8 cdrom onto a disk. Put your sources in that tree. : >Chroot. you now have the 2.2.8 compilers. : : Ooo. That's clever, and pretty simple to do. I have a cdrom that I keep around for just such purposes. I usually mount the cdrom under /228. then mount my home directory under /228/mnt and then sudo chroot /228 /bin/tcsh and do the builds that way. Copying the cdrom is easier to maintain and explain, since I'm sure there are quirks in the above that aren't obvious at the moment. It is a hell of a lot easier than hacking 20-30 different Makefiles to do the right thing, and quicker to setup than a whole new machine. Plus it makes my boss' head hurt, which is always a plus. :-) We have automated scripts that build our products in chroot areas so that we don't have to run the exact version of the software on our development boxes that our embedded systems run in. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 15:46: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.quidel.com (webmail.quidel.com [63.125.144.4]) by hub.freebsd.org (Postfix) with ESMTP id 55EDF37B405; Wed, 18 Jul 2001 15:46:06 -0700 (PDT) (envelope-from et@quidel.com) Received: by mail.quidel.com with Internet Mail Service (5.5.2653.19) id ; Wed, 18 Jul 2001 15:53:11 -0700 Message-ID: <9D4A4E19244ED4119BE90050DAD5DD47BC554A@mail.quidel.com> From: Etienne de Bruin To: 'John Baldwin' , Etienne de Bruin Cc: "freebsd-hackers@freebsd.org" Subject: RE: release.8 (4.3-RELEASE) Date: Wed, 18 Jul 2001 15:53:09 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG But what does this accomplish in the contect of release.8 if our purpose is to 'copy' all the binaries to the new mfsroot? On 18-Jul-01 Etienne de Bruin wrote: > I was reading the Makefile in /usr/src/release and wondering about the > > for dir in bin sbin ; do \ > ln -sf /stand $$dir; \ > done > > part in release.8 - it is my understanding that all that is under /stand is > linked to files in $$dir. > > What does this accomplish? No, it links $$dir to /stand. This creates /sbin and /bin directories so that you can still see /bin/ls even though ls is really in /stand/ls. This is to make a "normal" path work right, and to allow scripts which assume the default location of utilities work. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 18: 8:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 3523637B414; Wed, 18 Jul 2001 18:08:33 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id VAA26143; Wed, 18 Jul 2001 21:08:32 -0400 (EDT) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id VAA04984; Wed, 18 Jul 2001 21:08:31 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id VAA04980; Wed, 18 Jul 2001 21:08:31 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Wed, 18 Jul 2001 21:08:31 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: pci device driver writing newbie Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm currently trying to write a driver for the hardware monitoring function of the Via 686a/b chipset, but I have a problem. I'm trying to get my module (which right now does mostly nothing except probing and attaching) to detect the ACPI function of this chip, but right now pciconf -l shows it as "chip0". I found the devid in /usr/src/sys/pci/pcisupport.c, (0x30571106) and commented that case out, recompiled my kernel, and rebooted, but no luck, it still detects as chip0. What can I do to keep this from happening. This is the only way I can accurately probe and attach this device and find it's base i/o address. Once I have this chip probing and attaching, and have the base io address, I can do the rest of the hardware monitoring functions of this driver on my own. (as a note, to avoid doing floating point calculations in the kernel, and to avoid doing some really nasty hacks that I found in the linux version of this driver, I'll be making the driver return the raw values from the registers, and I'll be writing a library that takes care of making the values that come from the registers useful.) Thanks ahead of time :-) Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 18:55:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (dhcp-221-142.pdc.kth.se [130.237.221.142]) by hub.freebsd.org (Postfix) with ESMTP id 3E00837B401 for ; Wed, 18 Jul 2001 18:55:31 -0700 (PDT) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id DAA69121; Thu, 19 Jul 2001 03:55:43 +0200 (CEST) (envelope-from assar) To: Sheldon Hearn Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Weird problem in 4.3-STABLE References: <11254.995477648@axl.seasidesoftware.co.za> From: Assar Westerlund Date: 19 Jul 2001 03:55:41 +0200 In-Reply-To: Sheldon Hearn's message of "Wed, 18 Jul 2001 19:34:08 +0200" Message-ID: <5lsnftvg0y.fsf@assaris.sics.se> Lines: 36 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sheldon Hearn writes: > static inline void > xdaemonwarn(char *fmt, ...) > { > va_list ap; > > va_start(ap, fmt); > if (!daemon_quiet) > warn(fmt, ap); > va_end(ap); > > return; > } > > GCC gives "syntax error before 'void'". Fair enough. As other people have been saying, you need to use `vwarn'. The following code compiles fine for me with a 4.3-STABLE gcc. /assar #include #include static int daemon_quiet; static inline void xdaemonwarn(const char *fmt, ...) { va_list ap; va_start(ap, fmt); if (!daemon_quiet) vwarn(fmt, ap); va_end(ap); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 19: 8:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sii.linuxsweden.nu (h55n2fls32o867.telia.com [217.208.37.55]) by hub.freebsd.org (Postfix) with ESMTP id F21D137B403 for ; Wed, 18 Jul 2001 19:08:45 -0700 (PDT) (envelope-from siigron@sii.linuxsweden.nu) Received: (from siigron@localhost) by sii.linuxsweden.nu (8.11.4/8.11.3) id f6J46Kk00785; Thu, 19 Jul 2001 06:06:20 +0200 (CEST) (envelope-from siigron) Date: Thu, 19 Jul 2001 06:06:20 +0200 (CEST) From: Joel Wilsson Message-Id: <200107190406.f6J46Kk00785@sii.linuxsweden.nu> To: sheldonh@starjuice.net Subject: Re: Weird problem in 4.3-STABLE Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sheldon Hearn writes: > static inline void > xdaemonwarn(char *fmt, ...) > { > va_list ap; > > va_start(ap, fmt); > if (!daemon_quiet) > warn(fmt, ap); > va_end(ap); > > return; > } > > GCC gives "syntax error before 'void'". Fair enough. $ cat test.c static inline void blah(void) { printf("yada yada yada\n"); } main() { blah(); } $ gcc -ansi -o test test.c test.c:2: syntax error before `void' $ gcc -o test test.c $ cat test2.c static __inline void blah(void) { printf("yada yada yada\n"); } main() { blah(); } $ gcc -ansi -o test2 test2.c $ So either get rid of the -ansi flag, or use __inline instead of inline. Regards, Joel Wilsson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 22:44:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 8B87937B409 for ; Wed, 18 Jul 2001 22:44:38 -0700 (PDT) (envelope-from fmela0@sm.socccd.cc.ca.us) Received: from sm.socccd.cc.ca.us (pool0708.cvx4-bradley.dialup.earthlink.net [209.178.148.198]) by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id WAA29763; Wed, 18 Jul 2001 22:44:20 -0700 (PDT) Message-ID: <3B567452.36965E56@sm.socccd.cc.ca.us> Date: Wed, 18 Jul 2001 22:46:58 -0700 From: Farooq Mela X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: tlambert2@mindspring.com Cc: hackers@FreeBSD.ORG Subject: Re: Quick question about x86 asm References: <3B554445.193CE946@sm.socccd.cc.ca.us> <3B55BD97.A6E40F1E@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > > cc -S is your friend. Right, well that can certainly help, but what gcc generates can be dependant on calling convention, optimization setting, &c &c, and though the code generated in one particular scenario may not be an absolute indicator of it's behavior. In other words, I was looking for more of a "yes" or "no" type response ;-). Anyway, redirecting this question to a gcc list. -- farooq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 23:40: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id C335437B401 for ; Wed, 18 Jul 2001 23:39:41 -0700 (PDT) (envelope-from vel@bugz.infotecs.ru) Received: (from root@localhost) by bugz.infotecs.ru (8.11.1/8.11.1) id f6J6rwa01563; Thu, 19 Jul 2001 10:53:58 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200107190653.f6J6rwa01563@bugz.infotecs.ru> Subject: Re: KLD Programming In-Reply-To: "from Zhihui Zhang at Jul 18, 2001 02:32:39 pm" To: suid@kjell.utb.falun.se Date: Thu, 19 Jul 2001 10:53:58 +0400 (MSD) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Yes. But it is not easy. Look at code vfs_vnops.c. You can let a user > process open a file and then push the file descriptor into kernel via a > special system call. Search the mailing list archive and you will find > discussions on how to add a new system call. > Well, if you aren't going to do intensive file i/o, this is possible (especially on MOD_LOAD) with a very ugly, but working hack: you can simulate that current process is doing the i/o. Take curproc, allocate some memory in it's address space using mmap() (or, preferably, vm_mmap()) with MAP_ANON flag for i/o buffer and then call open(), read(), etc, passing curproc and allocated buffer to them. Do note, however, that you generally can't access the buffer directly with C operators; you should rather use copyin()/copyout(), fubyte()/subyte() functions (see the manual page for them for details). Of course this is no brilliant solution, I'm currently looking for a better one, but this works for me so far for reading a config file on load. Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jul 18 23:47: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id BE38137B403 for ; Wed, 18 Jul 2001 23:46:15 -0700 (PDT) (envelope-from vel@bugz.infotecs.ru) Received: (from root@localhost) by bugz.infotecs.ru (8.11.1/8.11.1) id f6J70o101594 for freebsd-hackers@freebsd.org; Thu, 19 Jul 2001 11:00:50 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200107190700.f6J70o101594@bugz.infotecs.ru> Subject: KLD parameters To: freebsd-hackers@freebsd.org Date: Thu, 19 Jul 2001 11:00:50 +0400 (MSD) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, it seems that I can't pass any parameters to a KLD module when I load it (i.e., some command line). Am I missing something, or if not, why is it like that, on purpose or just no one was willing to implement that ? Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 0: 0:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 08A2937B401 for ; Thu, 19 Jul 2001 00:00:21 -0700 (PDT) (envelope-from murray@meow.osd.bsdi.com) Received: (from murray@localhost) by meow.osd.bsdi.com (8.11.4/8.11.2) id f6J6xSR20161; Wed, 18 Jul 2001 23:59:28 -0700 (PDT) (envelope-from murray) Date: Wed, 18 Jul 2001 23:59:28 -0700 From: Murray Stokely To: Kenneth Wayne Culver Cc: freebsd-hackers@freebsd.org Subject: Re: pci device driver writing newbie Message-ID: <20010718235928.A18388@meow.osd.bsdi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from culverk@wam.umd.edu on Wed, Jul 18, 2001 at 09:08:31PM -0400 X-GPG-Key-ID: 1024D/0E451F7D X-GPG-Key-Fingerprint: E2CA 411D DD44 53FD BB4B 3CB5 B4D7 10A2 0E45 1F7D Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jul 18, 2001 at 09:08:31PM -0400, Kenneth Wayne Culver wrote: > get my module (which right now does mostly nothing except probing and > attaching) to detect the ACPI function of this chip, but right now pciconf > -l shows it as "chip0". I found the devid in > /usr/src/sys/pci/pcisupport.c, (0x30571106) and commented that case out, > recompiled my kernel, and rebooted, but no luck, it still detects as > chip0. What can I do to keep this from happening. This is the only way I The first thing that comes to mind is that you will probably find using a KLD much easier during development for this sort of thing. There is some basic information in the Developer's Handbook about this but it is incomplete : http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ Can you print the return value of pci_get_vendor() in your probe() function to verify that you are getting the same listing that pciconf -l reports? Remember that if pciconf -l returns something like chip=0x2a601093 then 1093 is the vendor ID and 2a60 is the device ID. - Murray To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 0: 4:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id C5B6137B403 for ; Thu, 19 Jul 2001 00:04:09 -0700 (PDT) (envelope-from arr@watson.org) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.4/8.11.4) with SMTP id f6J72fq92820; Thu, 19 Jul 2001 03:02:42 -0400 (EDT) (envelope-from arr@watson.org) Date: Thu, 19 Jul 2001 03:02:40 -0400 (EDT) From: "Andrew R. Reiter" To: "Eugene L. Vorokov" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: KLD parameters In-Reply-To: <200107190700.f6J70o101594@bugz.infotecs.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This was discussed before... I think if you want it, implement it. :-/ andrew On Thu, 19 Jul 2001, Eugene L. Vorokov wrote: > Hello, > > it seems that I can't pass any parameters to a KLD module when I load > it (i.e., some command line). Am I missing something, or if not, why is it > like that, on purpose or just no one was willing to implement that ? > > Regards, > Eugene > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 0:16: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 42A6237B403 for ; Thu, 19 Jul 2001 00:15:52 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.141.193.Dial1.SanJose1.Level3.net [209.247.141.193]) by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA00686; Thu, 19 Jul 2001 00:15:37 -0700 (PDT) Message-ID: <3B56893D.CBACD316@mindspring.com> Date: Thu, 19 Jul 2001 00:16:13 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Weird problem in 4.3-STABLE References: <11254.995477648@axl.seasidesoftware.co.za> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > What I really want is a static inline void function declared in a heade= r > file and included in various source files, looking something like this:= > = > static inline void [ ... ] > GCC gives "syntax error before 'void'". Fair enough. > = > So obviously, this should be implemented as a macro. Not so obvious. The warning should have been the first clue. > But GCC warns that > ANSI C doesn't support variable arguments to macros. Fine. #define VARRADIC macro(x) foo x =2E.. macro((a, b, c, ...)); /* x:=3D(a, b, c, ...), so macro(x) expands to foo(a, b, c, ...)*/ > So I give up on any semblence of efficiency and settle for a real > wrapper. This is where things get interesting. The stdarg(3) manual > page says this: > = > Unlike the varargs macros, the stdarg macros do not permit programmer= s to > code a function with no fixed arguments. This problem generates work= > mainly when converting varargs code to stdarg code, but it also creat= es > difficulties for variadic functions that wish to pass all of their ar= gu=AD > ments on to a function that takes a va_list argument, such as > vfprintf(3). > = > This shouldn't apply to what I'm trying to do, because I have one fixed= > argument. It doesn't. I've often thought cdefs.h needed varradic K&R vs. ANSI wrappers. I've submitted them once or twice... they really clean up the code. [ ... other stuff related to K&R vs. ANSI varradic functions ... ] > So, um, what the fsck is going on here? :-) Well, first, "inline" should really be "__inline"; that's the "error before 'void'" that gcc is complaining about. There are other ways to skin this cat in gcc, including using some "__attribute__" qualifier, or whatever. Try grep'ing through /usr/include/sys/*.h for "inline". Second, questions like this really belong on -questions... or even one of the C language or gcc mailing lists... ;-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 0:22:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id DC5B637B403 for ; Thu, 19 Jul 2001 00:22:50 -0700 (PDT) (envelope-from julian@elischer.org) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id CAA97655; Thu, 19 Jul 2001 02:03:47 -0700 (PDT) Message-ID: <3B568581.5A798B3E@elischer.org> Date: Thu, 19 Jul 2001 00:00:17 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Max Khon Cc: freebsd-hackers@freebsd.org Subject: Re: arcnet support for FreeBSD (request for review) References: Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Max Khon wrote: > > hi, there! what is arcnet? > > I have made second attempt to implement Arcnet support for FreeBSD > (the first was made about two years ago and nothing was ever committed) > probably no committers had arcnet or could test it.. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 0:36:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp-2.enteract.com (smtp-2.enteract.com [207.229.143.4]) by hub.freebsd.org (Postfix) with ESMTP id E628137B401 for ; Thu, 19 Jul 2001 00:36:32 -0700 (PDT) (envelope-from dscheidt@tumbolia.com) Received: from shell-3.enteract.com (shell-3.enteract.com [207.229.143.42]) by smtp-2.enteract.com (Postfix) with ESMTP id 078396874; Thu, 19 Jul 2001 02:35:51 -0500 (CDT) Date: Thu, 19 Jul 2001 02:35:51 -0500 (CDT) From: David Scheidt X-X-Sender: To: Julian Elischer Cc: Max Khon , Subject: Re: arcnet support for FreeBSD (request for review) In-Reply-To: <3B568581.5A798B3E@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 19 Jul 2001, Julian Elischer wrote: :Max Khon wrote: :> :> hi, there! : :what is arcnet? : It's a token-based LAN protocol. It's used in some embedded applications, as its controllers are cheap, it's pretty low-overhead, and has deterministic behavior (you can calculate the worst case time to send a message to another station). Industrial controlers and data acquistion are the two uses that jump out of my memory. -- dscheidt@tumbolia.com Bipedalism is only a fad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 0:39:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from taupo.cs.waikato.ac.nz (taupo.cs.waikato.ac.nz [130.217.241.30]) by hub.freebsd.org (Postfix) with ESMTP id 191DD37B401 for ; Thu, 19 Jul 2001 00:39:36 -0700 (PDT) (envelope-from joerg@taupo.cs.waikato.ac.nz) Received: (from joerg@localhost) by taupo.cs.waikato.ac.nz (8.11.3/8.11.1) id f6J7cnh33069; Thu, 19 Jul 2001 19:38:49 +1200 (NZST) (envelope-from joerg) Date: Thu, 19 Jul 2001 19:38:49 +1200 From: Joerg Micheel To: David Scheidt Cc: Julian Elischer , Max Khon , freebsd-hackers@freebsd.org, joerg@cs.waikato.ac.nz Subject: Re: arcnet support for FreeBSD (request for review) Message-ID: <20010719193849.X8338@cs.waikato.ac.nz> References: <3B568581.5A798B3E@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from dscheidt@tumbolia.com on Thu, Jul 19, 2001 at 02:35:51AM -0500 Organization: Dept of Computer Science, University of Waikato, Hamilton, New Zealand Project: WAND - Waikato Applied Network Dynamics, DAG Operating-System: ... powered by FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jul 19, 2001 at 02:35:51AM -0500, David Scheidt wrote: > On Thu, 19 Jul 2001, Julian Elischer wrote: > > :Max Khon wrote: > :> > :> hi, there! > : > :what is arcnet? > : > > It's a token-based LAN protocol. It's used in some embedded applications, > as its controllers are cheap, it's pretty low-overhead, and has > deterministic behavior (you can calculate the worst case time to send a > message to another station). Industrial controlers and data acquistion are > the two uses that jump out of my memory. David, Julian was kidding you. Read his response again. Joerg -- Joerg B. Micheel Email: WAND and NLANR MOAT Email: The University of Waikato, CompScience Phone: +64 7 8384794 Private Bag 3105 Fax: +64 7 8585095 Hamilton, New Zealand Plan: PMA, TINE and the DAG's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 0:41: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id DC62237B403 for ; Thu, 19 Jul 2001 00:41:01 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15N8RD-0003bJ-00; Thu, 19 Jul 2001 09:41:35 +0200 From: Sheldon Hearn To: tlambert2@mindspring.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Weird problem in 4.3-STABLE In-reply-to: Your message of "Thu, 19 Jul 2001 00:16:13 MST." <3B56893D.CBACD316@mindspring.com> Date: Thu, 19 Jul 2001 09:41:34 +0200 Message-ID: <13844.995528494@axl.seasidesoftware.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 19 Jul 2001 00:16:13 MST, Terry Lambert wrote: > Second, questions like this really belong on -questions... or > even one of the C language or gcc mailing lists... ;-). You're right. I initially had the mail addressed to freebsd-questions and then made the all-too common mistake of thinking "but the guys on -hackers are more likely to know". Of course, that has nothing to do with whether a post is appropriate on a given list. Thanks all the same for the answers, folks. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 0:47:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 0EC0D37B401 for ; Thu, 19 Jul 2001 00:47:21 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.141.193.Dial1.SanJose1.Level3.net [209.247.141.193]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA00084; Thu, 19 Jul 2001 00:47:10 -0700 (PDT) Message-ID: <3B5690A1.8EDD0812@mindspring.com> Date: Thu, 19 Jul 2001 00:47:45 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Louis-Philippe Gagnon Cc: Julian Elischer , freebsd-hackers@FreeBSD.ORG Subject: Re: flock/pthread bug? References: <1fbd01c10fba$499834d0$2964a8c0@macadamian.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Louis-Philippe Gagnon wrote: > > From: "Julian Elischer" > > probably you should try : > > > > #define LOCK_NB 0x04 /* don't block when locking */ > > > But I do want to block; I just don't want the whole process to block. You can't block just a thread, since there is no "queue a lock request" interface, only a "try to get the lock, and return if you can't" or a "block and wait for the lock". In other words, flock() is one call that can't really be reasonably implemented by the threads library, since there is no way to map it safely, and still guarantee against an order inversion deadlock. > > Also if you have shared memory, why not use > > > > /* Get a spin lock, handle recursion inline (as the less common case) */ Using the "cmpxchgl" instruction is your best approach; I personally would not use the whole thing, as Julian suggested, since I think the SMP synchronization ops are much, much heavier than they should be. You don't need that much overhead, you don't need reentrancy, and you don't need it to do counting (neither does SMP). The easiest way to get shared memory is to use mmap() in both programs on a file, and to madvise() the caching and cache writeback off. This is much beeter than SYSV shared memory (shmat, shmget, etc.), since it is properly resource tracked, and you will not have a startup order of operation problem, nor will you have the common problem of trying to get rid of the segments, should any of your programs exit abnormally. > I'd rather have something portable though, and I would > still like to know if what I was doing should have worked... The answer is "no". Threads are not processes, they exist in a single process context, as they currently exist. In the future, what you are doing will work, but will have a very high comparative overhead to other approaches. If you read Stevens, you will see that flock() is much higher overhead than doing semop() calls. To wrap either, you would need to: retry: st = try_non_blocking_get(); if (st == FAIL) { yield(); goto retry; } Note that the "yield" system call is non-standard, and you will buzz-loop somewhat, depressing your priority. You will also have a race window, subject to the "thundering herd" problem. You could put a "sleep(1);" in place of the "yield();" call... this would eliminate the buzzing (somewhat), but would widen the race window. Another alternative is to use a multiended pipe, where you write a single character token down the pipe, and your programs block waiting for a single character read to complete (you could use a FIFO or socket, in place of the pipe). The point is that only a single reader can get the character (the "token") at a time. Unfortuantely, since file I/O is implemented as a conversion of a blocking call to a non-blocking call plus a context switch (normal for a threads library), you still have the "thundering herd" problem. Further, if your intent was to have the callers serviced in the order they called the read, you can't: you will never have a guarantee about who will be permitted to complete the read first. So, for FIFO ordering, there's no way for you to solve the problem; for semop or flock, you can solve the problem portably with a "sleep - retry" loop, and not burn too many cycles (but still lose FIFO ordering). If you absolutely _must_ have a FIFO, then you need to either wait, or install the Linux threads port (Linux threads are hideously expensive, compared to the current FreeBSD threads implementation, since they effectively create a new process for each thread, just like Linux does), and use blocking operations using them. Probably, if you need FIFO ordering, whatever you are doing would be better implemented as a finite state automaton, or a "work-to-do" model, where you don't really care who wins a race in a "thundering herd", since all of your programs waiting on the condition are identical. Worse comes to worse, you should consider implementing your threads as real seperate processes (and not fake ones, like in the Linux threads library). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 0:51:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 58E3337B403; Thu, 19 Jul 2001 00:51:29 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.141.193.Dial1.SanJose1.Level3.net [209.247.141.193]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA08568; Thu, 19 Jul 2001 00:51:27 -0700 (PDT) Message-ID: <3B5691A5.66486B63@mindspring.com> Date: Thu, 19 Jul 2001 00:52:05 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: hackers@FreeBSD.org, Matthew Jacob Subject: Re: x86 unaligned access followup. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > > Also note that this will play hell with some of the recent > > copy avoidance changes made by Bill Paul to the ethernet > > drivers, to avoid the expense of copying the packet, with > > the knowledge that there would be an increased overhead in > > the resulting packet field unaligned accesses when decoding > > IP packets... [ ... ] > I didn't say it was a good thing, I was just saying how it was done. :) > From Bill's description of the network stuff, it sounds like the unaligned > access on x86 is cheaper than the copy that would otherwise be done, so we > don't want AC checks in that case anyways. I don't know if I entriely believe that... it depends on how big the average packets are. For a web server, for example, there is the initial request, and then there's ACK's, so the copy overhead is negligible, and might outweigh the unaligned access overhead, particularly if you could delay the copy until it was abosolutely necessary (e.g. avoid copying the 14 byte ethernet header, etc., and do the copy in ip_input() instead). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 0:56:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 3C2D337B403; Thu, 19 Jul 2001 00:56:13 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.141.193.Dial1.SanJose1.Level3.net [209.247.141.193]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA18369; Thu, 19 Jul 2001 00:56:06 -0700 (PDT) Message-ID: <3B5692BC.77E9D994@mindspring.com> Date: Thu, 19 Jul 2001 00:56:44 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: kuehl@lgk.de Cc: hackers@FreeBSD.org, Matthew Jacob , John Baldwin Subject: Re: x86 unaligned access followup. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG kuehl@lgk.de wrote: > > A "shakedown cruise" could end up being very rough... you > > would effectively need to check an "unaligned access in > > kernel is OK" flag in many of these instances, and fall back > > to doing the copy when it was false. > > ...therefore - never mind. > Perhaps some app code may break. ;-) The point was that this code breaks on some architectures supported by FreeBSD anyway, and moving at least some of the pain onto x86 people would end up minimizing that breakage. Right now, being able to make a bug break all architectures equally looks pretty good to people having to keep up with the x86 port of FreeBSD's rate of breakage of others, like the Alpha, when people with just x86 hardware break things without knowing it. Most of the App code is fixed, since most of it runs on the Alpha without a lot of problems, these days. Your biggest problem is bound to be the non-native ABI's, such as what people call "the Linux emulator", since x86 programmers on Linux aren't nearly as careful with their code. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 1:26: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 347AE37B401 for ; Thu, 19 Jul 2001 01:26:06 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.141.193.Dial1.SanJose1.Level3.net [209.247.141.193]) by scaup.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA09402; Thu, 19 Jul 2001 01:26:00 -0700 (PDT) Message-ID: <3B5699BD.10BE44F8@mindspring.com> Date: Thu, 19 Jul 2001 01:26:37 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Farooq Mela Cc: hackers@FreeBSD.ORG Subject: Re: Quick question about x86 asm References: <3B554445.193CE946@sm.socccd.cc.ca.us> <3B55BD97.A6E40F1E@mindspring.com> <3B567452.36965E56@sm.socccd.cc.ca.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Farooq Mela wrote: > > cc -S is your friend. > > Right, well that can certainly help, but what gcc generates can be > dependant on calling convention, optimization setting, &c &c, and > though the code generated in one particular scenario may not be an > absolute indicator of it's behavior. In other words, I was looking for > more of a "yes" or "no" type response ;-). Anyway, redirecting this > question to a gcc list. The correct assembly code to use is "dependent on the calling convention, &c, &c" of the C code you are going to link it into, so that's not a strong argument. Given a function argument list and return type, it's going to remain pretty constant, so long as you compile your -S function in an isolated environment, such that it has to be capable of linking against other code, once assembled ...in other words, you don't have to worry about the peephole optimizer being able to span multiple object files, so it's not really a problem that involves changes to calling convetion or tail call or other optimization. The answer you were probably looking for is that the eax register is _not_ loaded with a return value in the "void" case, but it may contain a value different than when it went in, anyway, if the register ended up being used for scratch. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 1:29: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 6926F37B405 for ; Thu, 19 Jul 2001 01:29:01 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.141.193.Dial1.SanJose1.Level3.net [209.247.141.193]) by scaup.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA12921; Thu, 19 Jul 2001 01:28:16 -0700 (PDT) Message-ID: <3B569A45.B13F6F80@mindspring.com> Date: Thu, 19 Jul 2001 01:28:53 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Max Khon , freebsd-hackers@FreeBSD.ORG Subject: Re: arcnet support for FreeBSD (request for review) References: <3B568581.5A798B3E@elischer.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer wrote: > > hi, there! > > what is arcnet? Old PC networking standard, limited to 2Mbit/S. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 1:32: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sneakerz.org (sneakerz.org [216.33.66.254]) by hub.freebsd.org (Postfix) with ESMTP id 2733737B405 for ; Thu, 19 Jul 2001 01:32:06 -0700 (PDT) (envelope-from bright@sneakerz.org) Received: by sneakerz.org (Postfix, from userid 1092) id 893C45D01F; Thu, 19 Jul 2001 03:31:47 -0500 (CDT) Date: Thu, 19 Jul 2001 03:31:47 -0500 From: Alfred Perlstein To: Terry Lambert Cc: Julian Elischer , Max Khon , freebsd-hackers@FreeBSD.ORG Subject: Re: arcnet support for FreeBSD (request for review) Message-ID: <20010719033146.Q28164@sneakerz.org> References: <3B568581.5A798B3E@elischer.org> <3B569A45.B13F6F80@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3B569A45.B13F6F80@mindspring.com>; from tlambert2@mindspring.com on Thu, Jul 19, 2001 at 01:28:53AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Terry Lambert [010719 03:29] wrote: > Julian Elischer wrote: > > > hi, there! > > > > what is arcnet? > > Old PC networking standard, limited to 2Mbit/S. My college had it, if they still do I may be able to toss them a FreeBSD cdrom and say "go for it". :) -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 1:47:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from marine.sonic.net (marine.sonic.net [208.201.224.37]) by hub.freebsd.org (Postfix) with SMTP id 8853337B403 for ; Thu, 19 Jul 2001 01:47:28 -0700 (PDT) (envelope-from gharris@sonic.net) Received: (qmail 11673 invoked from network); 19 Jul 2001 08:47:28 -0000 Received: from buzz.sonic.net (208.201.224.78) by marine.sonic.net with SMTP; 19 Jul 2001 08:47:28 -0000 Received: from quadrajet.sonic.net (adsl-209-204-185-65.sonic.net [209.204.185.65]) by buzz.sonic.net (8.11.2/8.8.5) with ESMTP id f6J8lSJ10618; Thu, 19 Jul 2001 01:47:28 -0700 X-envelope-info: Received: (from guy@localhost) by quadrajet.sonic.net (8.9.3/8.9.3) id BAA00380; Thu, 19 Jul 2001 01:47:25 -0700 (PDT) (envelope-from gharris) Date: Thu, 19 Jul 2001 01:47:25 -0700 From: Guy Harris To: Joerg Micheel Cc: Andrey Simonenko , freebsd-hackers@freebsd.org Subject: Re: libpcap and pthreads Message-ID: <20010719014725.A344@quadrajet.sonic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Is it possible to use libpcap with pthreads? > > (I want to use just pcap_dispatch() function) > > I very much doubt so. It's not possible to use it in any kind of > multithreaded applications, even with select() scenarios. That's a BPF problem, not a libpcap problem; see PR kern/22063 "bpf when used with the select system call with timeout doesn't forward packets on timeout", which includes a patch (although it's uuencoded and, at least when you view that PR over the Web, the uuencoded text doesn't appear to be valid). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 4:13:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 7FE6837B403; Thu, 19 Jul 2001 04:13:15 -0700 (PDT) (envelope-from brandt@fokus.gmd.de) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id NAA01678; Thu, 19 Jul 2001 13:13:14 +0200 (MET DST) Date: Thu, 19 Jul 2001 13:13:14 +0200 (CEST) From: Harti Brandt To: Cc: Subject: ypbind broken... Message-ID: <20010719130934.K35300-100000@beagle.fokus.gmd.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, The last commit to ypbind (1.34) breaks parsing of the -S option. The following patch should fix this. harti Index: ypbind.c =================================================================== RCS file: /usr/ncvs/src/usr.sbin/ypbind/ypbind.c,v retrieving revision 1.34 diff -c -r1.34 ypbind.c *** ypbind.c 2001/07/13 14:10:09 1.34 --- ypbind.c 2001/07/19 11:06:07 *************** *** 415,423 **** ypsetmode = YPSET_LOCAL; else if (strcmp("-s", argv[i]) == 0) ypsecuremode++; ! else if (strcmp("-S", argv[i]) == 0 && argc > i) yp_restricted_mode(argv[i+1]); ! else if (strcmp("-m", argv[i]) == 0) yp_manycast++; else errx(1, "unknown option: %s", argv[i]); --- 415,424 ---- ypsetmode = YPSET_LOCAL; else if (strcmp("-s", argv[i]) == 0) ypsecuremode++; ! else if (strcmp("-S", argv[i]) == 0 && argc > i) { yp_restricted_mode(argv[i+1]); ! i++; ! } else if (strcmp("-m", argv[i]) == 0) yp_manycast++; else errx(1, "unknown option: %s", argv[i]); -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 4:33:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id D3A0E37B6E9 for ; Thu, 19 Jul 2001 04:33:40 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id 75D693E2F; Thu, 19 Jul 2001 04:33:40 -0700 (PDT) To: Harti Brandt Cc: hackers@freebsd.org Subject: Re: ypbind broken... In-Reply-To: <20010719130934.K35300-100000@beagle.fokus.gmd.de>; from brandt@fokus.gmd.de on "Thu, 19 Jul 2001 13:13:14 +0200 (CEST)" Date: Thu, 19 Jul 2001 04:33:40 -0700 From: Dima Dorfman Message-Id: <20010719113340.75D693E2F@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Harti Brandt writes: > > Hi, > > The last commit to ypbind (1.34) breaks parsing of the -S option. > The following patch should fix this. Oops, my fault; I've applied a variant of this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 6:47:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx2.magma.ca (mx2.magma.ca [206.191.0.250]) by hub.freebsd.org (Postfix) with ESMTP id 7775237B401 for ; Thu, 19 Jul 2001 06:47:40 -0700 (PDT) (envelope-from louisphilippe@macadamian.com) Received: from mail3.magma.ca (mail3.magma.ca [206.191.0.221]) by mx2.magma.ca (8.9.3/8.9.3) with ESMTP id JAA23957; Thu, 19 Jul 2001 09:47:38 -0400 (EDT) Received: from durandal (mothership.macadamian.com [206.191.21.204]) by mail3.magma.ca (8.9.3/8.9.3) with SMTP id JAA07462; Thu, 19 Jul 2001 09:47:38 -0400 (EDT) Message-ID: <203501c11059$35755420$2964a8c0@macadamian.com> From: "Louis-Philippe Gagnon" To: Cc: References: <1fbd01c10fba$499834d0$2964a8c0@macadamian.com> <3B5690A1.8EDD0812@mindspring.com> Subject: Re: flock/pthread bug? Date: Thu, 19 Jul 2001 09:46:27 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Lots of ideas to try (esp. since I don't need FIFO); thanks! LPG ----- Original Message ----- From: "Terry Lambert" > Louis-Philippe Gagnon wrote: > > > > From: "Julian Elischer" > > > probably you should try : > > > > > > #define LOCK_NB 0x04 /* don't block when locking */ > > > > > But I do want to block; I just don't want the whole process to block. > > You can't block just a thread, since there is no "queue a > lock request" interface, only a "try to get the lock, and > return if you can't" or a "block and wait for the lock". > > In other words, flock() is one call that can't really be > reasonably implemented by the threads library, since > there is no way to map it safely, and still guarantee > against an order inversion deadlock. > > > > > Also if you have shared memory, why not use > > > > > > /* Get a spin lock, handle recursion inline (as the less common case) */ > > > Using the "cmpxchgl" instruction is your best approach; > I personally would not use the whole thing, as Julian > suggested, since I think the SMP synchronization ops > are much, much heavier than they should be. You don't > need that much overhead, you don't need reentrancy, and > you don't need it to do counting (neither does SMP). > > The easiest way to get shared memory is to use mmap() in > both programs on a file, and to madvise() the caching and > cache writeback off. This is much beeter than SYSV shared > memory (shmat, shmget, etc.), since it is properly resource > tracked, and you will not have a startup order of operation > problem, nor will you have the common problem of trying to > get rid of the segments, should any of your programs exit > abnormally. > > > I'd rather have something portable though, and I would > > still like to know if what I was doing should have worked... > > The answer is "no". Threads are not processes, they exist > in a single process context, as they currently exist. In > the future, what you are doing will work, but will have a > very high comparative overhead to other approaches. > > If you read Stevens, you will see that flock() is much > higher overhead than doing semop() calls. > > To wrap either, you would need to: > > retry: > st = try_non_blocking_get(); > if (st == FAIL) { > yield(); > goto retry; > } > > Note that the "yield" system call is non-standard, and you > will buzz-loop somewhat, depressing your priority. You > will also have a race window, subject to the "thundering > herd" problem. You could put a "sleep(1);" in place of > the "yield();" call... this would eliminate the buzzing > (somewhat), but would widen the race window. > > Another alternative is to use a multiended pipe, where > you write a single character token down the pipe, and > your programs block waiting for a single character read > to complete (you could use a FIFO or socket, in place of > the pipe). The point is that only a single reader can > get the character (the "token") at a time. > > Unfortuantely, since file I/O is implemented as a > conversion of a blocking call to a non-blocking call > plus a context switch (normal for a threads library), > you still have the "thundering herd" problem. > > Further, if your intent was to have the callers serviced > in the order they called the read, you can't: you will > never have a guarantee about who will be permitted to > complete the read first. > > So, for FIFO ordering, there's no way for you to solve > the problem; for semop or flock, you can solve the problem > portably with a "sleep - retry" loop, and not burn too > many cycles (but still lose FIFO ordering). > > If you absolutely _must_ have a FIFO, then you need to > either wait, or install the Linux threads port (Linux > threads are hideously expensive, compared to the current > FreeBSD threads implementation, since they effectively > create a new process for each thread, just like Linux > does), and use blocking operations using them. > > Probably, if you need FIFO ordering, whatever you are > doing would be better implemented as a finite state > automaton, or a "work-to-do" model, where you don't > really care who wins a race in a "thundering herd", > since all of your programs waiting on the condition > are identical. > > Worse comes to worse, you should consider implementing > your threads as real seperate processes (and not fake > ones, like in the Linux threads library). > > -- Terry > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 7: 4:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scribble.fsn.hu (scribble.fsn.hu [193.224.40.95]) by hub.freebsd.org (Postfix) with SMTP id 4A88D37B403 for ; Thu, 19 Jul 2001 07:04:31 -0700 (PDT) (envelope-from bra@fsn.hu) Received: (qmail 45952 invoked by uid 1000); 19 Jul 2001 14:04:24 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 19 Jul 2001 14:04:24 -0000 Date: Thu, 19 Jul 2001 16:04:24 +0200 (CEST) From: Attila Nagy To: Subject: NFS local mount Message-ID: <20010719155719.N45187-100000@scribble.fsn.hu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I am currently installing a machine on which I want to replace the NULL and/or UNIONFS mounts with NFS. NFS server and client on the same machine, to be exact, for jailing purposes (this seems to be the most stable). The problem is, that at the FreeBSD boot process the NFS filesystems are mounted before the NFS-related daemons are started, so I can't do this in a clean way (from /etc/fstab). Are there any objections to swap those two? I mean starting the NFS server and after that mounting the NFS filesystems? A machine can be both of them, and this way it would be nice to simply place some lines into /etc/fstab, instead of hacking with /etc/rc.local and /etc/rc.conf. Thanks, -------------------------------------------------------------------------- Attila Nagy e-mail: Attila.Nagy@fsn.hu Budapest Polytechnic (BMF.HU) @work: +361 210 1415 (194) H-1084 Budapest, Tavaszmezo u. 15-17. cell.: +3630 306 6758 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 7:14:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 3EA7337B401 for ; Thu, 19 Jul 2001 07:14:56 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA15026; Thu, 19 Jul 2001 10:14:53 -0400 (EDT) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id KAA02260; Thu, 19 Jul 2001 10:14:53 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA02256; Thu, 19 Jul 2001 10:14:53 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Thu, 19 Jul 2001 10:14:53 -0400 (EDT) From: Kenneth Wayne Culver To: Murray Stokely Cc: freebsd-hackers@freebsd.org Subject: Re: pci device driver writing newbie In-Reply-To: <20010718235928.A18388@meow.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > On Wed, Jul 18, 2001 at 09:08:31PM -0400, Kenneth Wayne Culver wrote: > > get my module (which right now does mostly nothing except probing and > > attaching) to detect the ACPI function of this chip, but right now pciconf > > -l shows it as "chip0". I found the devid in > > /usr/src/sys/pci/pcisupport.c, (0x30571106) and commented that case out, > > recompiled my kernel, and rebooted, but no luck, it still detects as > > chip0. What can I do to keep this from happening. This is the only way I > > The first thing that comes to mind is that you will probably find > using a KLD much easier during development for this sort of thing. > There is some basic information in the Developer's Handbook about this > but it is incomplete : > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ > Yep, I already looked at that :-) I'm using a kld for development for the very reason that I don't have to keep rebooting to test. The print of the pci_get_devid in my probe function returns 2 values, and they correspond to the device that say "none0" and "none1" beside them. chip0 reports chip=0x30571106. According to the documentation I have for the via chipset, this is what is supposed be reported for this chip. It's the ACPI device on my via686a chipset. What I did was comment out the case for that devid number from pcisupport.c in /usr/src/sys/pci (I'm working on stable right now) and recompiled my kernel, but that doesn't seem to have made any difference. I'm at work now so I can't try anything else until this evening. One thing I'll try is doing a config -r KERNEL to get rid of all the obj files and recompile everything; I have the feeling that pcisupport.c never compiled over again. Anyway, thanks for your help. > Can you print the return value of pci_get_vendor() in your probe() > function to verify that you are getting the same listing that pciconf > -l reports? Remember that if pciconf -l returns something like > chip=0x2a601093 then 1093 is the vendor ID and 2a60 is the device ID. > I guess the vendor ID for this chip would be 0x1106 then Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 7:37: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from anansi.vpha.health.ufl.edu (anansi.vpha.health.ufl.edu [159.178.78.153]) by hub.freebsd.org (Postfix) with ESMTP id 0260637B403 for ; Thu, 19 Jul 2001 07:37:06 -0700 (PDT) (envelope-from sridharv@ufl.edu) Received: (from dymphna@localhost) by anansi.vpha.health.ufl.edu (8.9.3/8.9.3) id KAA03175; Thu, 19 Jul 2001 10:37:05 -0400 Date: Thu, 19 Jul 2001 10:37:05 -0400 From: sridharv@ufl.edu Message-Id: <200107191437.KAA03175@anansi.vpha.health.ufl.edu> X-Authentication-Warning: anansi.vpha.health.ufl.edu: dymphna set sender to sridharv@ufl.edu using -f To: freebsd-hackers@freebsd.org Reply-To: sridharv@ufl.edu MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP3 Imap webMail Program 2.0.10 X-Originating-IP: 128.227.205.209 Subject: inpcb question Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have written a kernel module and modified the stack code ( at the socket layer) to send control to my module. I am trying to access the inpcb structure associated with that particular socket. struct in_pcb* inp = sotoinpcb(so); if (inp) .... processing though the pbc structure is allocated i am getting a page fault everytime when i try to access it. any idea? my code is in the socket layer..i checked up the udp routines.. they do pretty much the same thing.. any help? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 9: 1:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from netbank.com.br (garrincha.netbank.com.br [200.203.199.88]) by hub.freebsd.org (Postfix) with ESMTP id 0AB7B37B406 for ; Thu, 19 Jul 2001 09:01:17 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from surriel.ddts.net (1-231.ctame701-1.telepar.net.br [200.181.137.231]) by netbank.com.br (Postfix) with ESMTP id 2C12E46807; Thu, 19 Jul 2001 12:59:59 -0300 (BRST) Received: from localhost (kujtnl@localhost [127.0.0.1]) by surriel.ddts.net (8.11.4/8.11.2) with ESMTP id f6JG17F09452; Thu, 19 Jul 2001 13:01:07 -0300 Date: Thu, 19 Jul 2001 13:01:07 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Terry Lambert Cc: Julian Elischer , Max Khon , Subject: Re: arcnet support for FreeBSD (request for review) In-Reply-To: <3B569A45.B13F6F80@mindspring.com> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 19 Jul 2001, Terry Lambert wrote: > Julian Elischer wrote: > > > hi, there! > > > > what is arcnet? > > Old PC networking standard, limited to 2Mbit/S. I believe there is also 16 and 100 Mbit arcnet hardware available ;) At least, so I was told by one happy arcnet fan. Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://distro.conectiva.com/ Send all your spam to aardvark@nl.linux.org (spam digging piggy) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 9: 9:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nerd.geekythings.com (nerd.geekythings.com [204.138.241.6]) by hub.freebsd.org (Postfix) with ESMTP id 6071737B406 for ; Thu, 19 Jul 2001 09:09:31 -0700 (PDT) (envelope-from marc@geekythings.com) Received: from localhost (marc@localhost) by nerd.geekythings.com (8.11.2/8.9.2) with ESMTP id f6JG7Ag17184; Thu, 19 Jul 2001 12:07:10 -0400 (EDT) Date: Thu, 19 Jul 2001 12:07:10 -0400 (EDT) From: Marc X-Sender: marc@localhost To: Rik van Riel Cc: Terry Lambert , Julian Elischer , Max Khon , freebsd-hackers@FreeBSD.ORG Subject: Re: arcnet support for FreeBSD (request for review) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 19 Jul 2001, Rik van Riel wrote: > > > what is arcnet? > > > > Old PC networking standard, limited to 2Mbit/S. > > I believe there is also 16 and 100 Mbit arcnet > hardware available ;) That's just plain scary ;-) Although I guess Arcnet does have it's niche applications. -marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 9: 9:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx01-a.netapp.com (mx01-a.netapp.com [198.95.226.53]) by hub.freebsd.org (Postfix) with ESMTP id 86BCB37B405 for ; Thu, 19 Jul 2001 09:09:41 -0700 (PDT) (envelope-from boshea@netapp.com) Received: from frejya.corp.netapp.com (frejya.corp.netapp.com [10.10.20.91]) by mx01-a.netapp.com (8.11.1/8.11.1/NTAP-1.2) with ESMTP id f6JG2gX26249; Thu, 19 Jul 2001 09:02:42 -0700 (PDT) Received: from shaolin.hq.netapp.com (localhost [127.0.0.1]) by frejya.corp.netapp.com (8.11.1/8.11.1/NTAP-1.2) with ESMTP id f6JG2fc12361; Thu, 19 Jul 2001 09:02:41 -0700 (PDT) Received: (from boshea@localhost) by shaolin.hq.netapp.com (8.9.3/8.9.3) id JAA17767; Thu, 19 Jul 2001 09:02:40 -0700 (PDT) (envelope-from boshea) Date: Thu, 19 Jul 2001 09:02:40 -0700 From: "Brian O'Shea" To: Joerg Micheel Cc: Andrey Simonenko , freebsd-hackers@FreeBSD.ORG Subject: Re: libpcap and pthreads Message-ID: <20010719090240.R489@ricochet.net> Reply-To: boshea@ricochet.net Mail-Followup-To: Brian O'Shea , Joerg Micheel , Andrey Simonenko , freebsd-hackers@FreeBSD.ORG References: <012001c10f85$08ae6b40$6d36120a@comsys.ntukpi.kiev.ua> <20010719074735.H94236@cs.waikato.ac.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20010719074735.H94236@cs.waikato.ac.nz>; from joerg@cs.waikato.ac.nz on Thu, Jul 19, 2001 at 07:47:35AM +1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You could put the code that calls pcap_dispatch() in a separate single- threaded process and communicate with your multithreaded application via an IPC mechanism such as pipes or shared memory. -brian On Thu, Jul 19, 2001 at 07:47:35AM +1200, Joerg Micheel wrote: > Privjet Andrey, > > On Wed, Jul 18, 2001 at 04:27:39PM +0400, Andrey Simonenko wrote: > > Is it possible to use libpcap with pthreads? > > (I want to use just pcap_dispatch() function) > > I very much doubt so. It's not possible to use it in any kind of > multithreaded applications, even with select() scenarios. They > implement the Highlander principle - there can be only one (pcap). > Sad. > -- Brian O'Shea To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 9:30:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 9761737B401 for ; Thu, 19 Jul 2001 09:30:40 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.11.4/8.11.4) with ESMTP id f6JGT3F52750; Thu, 19 Jul 2001 23:29:03 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Thu, 19 Jul 2001 23:29:02 +0700 (NSS) From: Max Khon To: Marc Cc: Rik van Riel , Terry Lambert , Julian Elischer , freebsd-hackers@FreeBSD.ORG Subject: Re: arcnet support for FreeBSD (request for review) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, there! On Thu, 19 Jul 2001, Marc wrote: > > I believe there is also 16 and 100 Mbit arcnet > > hardware available ;) > > That's just plain scary ;-) Although I guess Arcnet does have it's niche > applications. yes. it is often used as solution for "last mile" problem and people ask for Arcnet drivers because they do not want to install Linux box for that /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 9:41: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.39]) by hub.freebsd.org (Postfix) with SMTP id 54FF437B406 for ; Thu, 19 Jul 2001 09:41:04 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 17114 invoked by uid 1000); 19 Jul 2001 16:45:13 -0000 Date: Thu, 19 Jul 2001 19:45:13 +0300 From: Peter Pentchev To: "Andrew R. Reiter" Cc: "Eugene L. Vorokov" , freebsd-hackers@FreeBSD.ORG Subject: Re: KLD parameters Message-ID: <20010719194513.C10583@ringworld.oblivion.bg> Mail-Followup-To: "Andrew R. Reiter" , "Eugene L. Vorokov" , freebsd-hackers@FreeBSD.ORG References: <200107190700.f6J70o101594@bugz.infotecs.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from arr@watson.org on Thu, Jul 19, 2001 at 03:02:40AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Actually, it is implemented - to some extent - in -current via the hints mechanism. There is still some more work to be done, though :) G'luck, Peter -- "yields falsehood, when appended to its quotation." yields falsehood, when appended to its quotation. On Thu, Jul 19, 2001 at 03:02:40AM -0400, Andrew R. Reiter wrote: > > This was discussed before... I think if you want it, implement it. :-/ > > andrew > > On Thu, 19 Jul 2001, Eugene L. Vorokov wrote: > > > Hello, > > > > it seems that I can't pass any parameters to a KLD module when I load > > it (i.e., some command line). Am I missing something, or if not, why is it > > like that, on purpose or just no one was willing to implement that ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 9:43:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.39]) by hub.freebsd.org (Postfix) with SMTP id 8DCA437B401 for ; Thu, 19 Jul 2001 09:43:25 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 17139 invoked by uid 1000); 19 Jul 2001 16:47:35 -0000 Date: Thu, 19 Jul 2001 19:47:35 +0300 From: Peter Pentchev To: Louis-Philippe Gagnon Cc: tlambert2@mindspring.com, freebsd-hackers@FreeBSD.ORG Subject: Re: flock/pthread bug? Message-ID: <20010719194735.D10583@ringworld.oblivion.bg> Mail-Followup-To: Louis-Philippe Gagnon , tlambert2@mindspring.com, freebsd-hackers@FreeBSD.ORG References: <1fbd01c10fba$499834d0$2964a8c0@macadamian.com> <3B5690A1.8EDD0812@mindspring.com> <203501c11059$35755420$2964a8c0@macadamian.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <203501c11059$35755420$2964a8c0@macadamian.com>; from louisphilippe@macadamian.com on Thu, Jul 19, 2001 at 09:46:27AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jul 19, 2001 at 09:46:27AM -0400, Louis-Philippe Gagnon wrote: > Lots of ideas to try (esp. since I don't need FIFO); thanks! > > LPG > > ----- Original Message ----- > From: "Terry Lambert" [snip] > > To wrap either, you would need to: > > > > retry: > > st = try_non_blocking_get(); > > if (st == FAIL) { > > yield(); > > goto retry; > > } > > > > Note that the "yield" system call is non-standard, and you > > will buzz-loop somewhat, depressing your priority. You > > will also have a race window, subject to the "thundering > > herd" problem. You could put a "sleep(1);" in place of > > the "yield();" call... this would eliminate the buzzing > > (somewhat), but would widen the race window. I don't know if Terry was talking about the sched_yield() syscall, but if he was, then sched_yield(2) exists, at least in 4.x, and is documented as POSIX-compliant. G'luck, Peter -- "yields falsehood, when appended to its quotation." yields falsehood, when appended to its quotation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 10: 1:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hmsa.com (hmsa.com [205.172.19.178]) by hub.freebsd.org (Postfix) with ESMTP id 6C75C37B403 for ; Thu, 19 Jul 2001 10:01:55 -0700 (PDT) (envelope-from tyoung@hmsa.com) Received: from hmsa.com ([10.1.73.41]) by hmsa.com (8.9.3/8.9.3) with ESMTP id GAA23747; Thu, 19 Jul 2001 06:55:40 -1000 (HST) Message-ID: <3B5710F6.93B2C42C@hmsa.com> Date: Thu, 19 Jul 2001 06:55:19 -1000 From: Terrance Young X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: en,ja,pdf MIME-Version: 1.0 To: Rik van Riel Cc: Terry Lambert , Julian Elischer , Max Khon , freebsd-hackers@FreeBSD.ORG Subject: Re: arcnet support for FreeBSD (request for review) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Arcnet is pretty bullet proof (at least from what I've seen) sheesh the thing runs with open ended connectors, half eaten thru cable, splitters upon splitters upon splitters... well from what I've seen in some businesses it's a wonder its worked heh... Rik van Riel wrote: > On Thu, 19 Jul 2001, Terry Lambert wrote: > > Julian Elischer wrote: > > > > hi, there! > > > > > > what is arcnet? > > > > Old PC networking standard, limited to 2Mbit/S. > > I believe there is also 16 and 100 Mbit arcnet > hardware available ;) > Yup, Thomas Conrad had cards that came with a proprietary 100 Mbit Arcnet card and one other company that escapes my memory at the moment, Not too sure about the 16Mbit ones though. > > At least, so I was told by one happy arcnet fan. > > Rik > -- > Virtual memory is like a game you can't win; > However, without VM there's truly nothing to lose... > > http://www.surriel.com/ http://distro.conectiva.com/ > > Send all your spam to aardvark@nl.linux.org (spam digging piggy) > > 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 Jul 19 10: 3:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id B8F3737B406 for ; Thu, 19 Jul 2001 10:03:29 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA99853; Thu, 19 Jul 2001 11:52:40 -0700 (PDT) Date: Thu, 19 Jul 2001 11:52:37 -0700 (PDT) From: Julian Elischer To: Joerg Micheel Cc: David Scheidt , Max Khon , freebsd-hackers@freebsd.org Subject: Re: arcnet support for FreeBSD (request for review) In-Reply-To: <20010719193849.X8338@cs.waikato.ac.nz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 19 Jul 2001, Joerg Micheel wrote: > On Thu, Jul 19, 2001 at 02:35:51AM -0500, David Scheidt wrote: > > On Thu, 19 Jul 2001, Julian Elischer wrote: > > > > :Max Khon wrote: > > :> > > :> hi, there! > > : > > :what is arcnet? > > : > > > > It's a token-based LAN protocol. It's used in some embedded applications, > > as its controllers are cheap, it's pretty low-overhead, and has > > deterministic behavior (you can calculate the worst case time to send a > > message to another station). Industrial controlers and data acquistion are > > the two uses that jump out of my memory. > > David, Julian was kidding you. Read his response again. I'm flattered that you think I was kidding.. actually I had no clue what Arcnet was :-) > > Joerg > -- > Joerg B. Micheel Email: > WAND and NLANR MOAT Email: > The University of Waikato, CompScience Phone: +64 7 8384794 > Private Bag 3105 Fax: +64 7 8585095 > Hamilton, New Zealand Plan: PMA, TINE and the DAG's > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 10:39: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id BD09137B403 for ; Thu, 19 Jul 2001 10:39:03 -0700 (PDT) (envelope-from LConrad@Go2France.com) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 920E616B13 for ; Thu, 19 Jul 2001 19:39:01 +0200 (CEST) Received: from IBM-HIRXKN66F0W.Go2France.com [195.115.185.184] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id AD5193CA0128; Thu, 19 Jul 2001 19:48:01 +0200 Message-Id: <5.1.0.14.0.20010719193435.0275a008@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 19 Jul 2001 19:39:52 +0200 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: Re: arcnet support for FreeBSD (request for review) In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >That's just plain scary ;-) Although I guess Arcnet does have it's niche >applications. niche now (reliable, cheap, shielded & transformer-coupled for nasty e/m environments), but in the 80's, Novell basically built itself up to 80% market share and the LAN marketpalce on ARCnet´s back, while Ethernet was playing stupid linear bus topology games. Len < worked for Datapoint when ARCnet went commerical in 1977 > http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 10:57:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 4451237B401 for ; Thu, 19 Jul 2001 10:56:58 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.3/8.9.3) with ESMTP id f6JHuuF64970; Thu, 19 Jul 2001 10:56:57 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f6JHuua42023; Thu, 19 Jul 2001 10:56:56 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <9D4A4E19244ED4119BE90050DAD5DD47BC554A@mail.quidel.com> Date: Thu, 19 Jul 2001 10:56:55 -0700 (PDT) From: John Baldwin To: Etienne de Bruin Subject: RE: release.8 (4.3-RELEASE) Cc: "freebsd-hackers@freebsd.org" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Jul-01 Etienne de Bruin wrote: > But what does this accomplish in the contect of release.8 if our purpose is > to 'copy' all the binaries to the new mfsroot? All the binaries live in /stand. You have /stand/ls, /stand/sysinstall, etc. all as one big crunch file. The /bin and /sbin symlinks allow you to find the binaries in /stand that are normally in /bin and /sbin in their normal location. So in the mfsroot you end up with this: /stand ls hardlink to sysinstall crunch sysinstall ... (other binaries) /bin -> /stand /sbin -> /stand That way you can use /bin/ls to find the ls binary in /stand. > On 18-Jul-01 Etienne de Bruin wrote: >> I was reading the Makefile in /usr/src/release and wondering about the >> >> for dir in bin sbin ; do \ >> ln -sf /stand $$dir; \ >> done >> >> part in release.8 - it is my understanding that all that is under /stand > is >> linked to files in $$dir. >> >> What does this accomplish? > > No, it links $$dir to /stand. This creates /sbin and /bin directories so > that > you can still see /bin/ls even though ls is really in /stand/ls. This is to > make a "normal" path work right, and to allow scripts which assume the > default > location of utilities work. > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 11: 6:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.quidel.com (webmail.quidel.com [63.125.144.4]) by hub.freebsd.org (Postfix) with ESMTP id 4BA9537B401 for ; Thu, 19 Jul 2001 11:06:42 -0700 (PDT) (envelope-from et@quidel.com) Received: by mail.quidel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 19 Jul 2001 11:13:05 -0700 Message-ID: <9D4A4E19244ED4119BE90050DAD5DD47BC554E@mail.quidel.com> From: Etienne de Bruin To: "'freebsd-hackers@freebsd.org'" Subject: roll of /stand in mfsroot Date: Thu, 19 Jul 2001 11:13:05 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG (I meant to post this to freebsd-hackers instead of freebsd-questions) > I am in the process of building a mfsroot that I want to > write_mfs_in_kernel. Because I don't really have any space constraints it > is my understanding that all I need to do is build up my directories, gzip > and copy to mfsroot.flp (with help of vnconfig ofcourse). > > My question relates to the required directories (reading release.8 in > /usr/src/release/Makefile). > > Can I just use the directories stated in > /usr/src/release/boot_crunch.config and copy them plainly to my mfsroot? > > Also, the /stand dir is bugging me - do I need it? or can I just use the > plain /bin and /sbin directories? > > Thanks > > > eT > -- > Etienne de Bruin : eT@quidel.com > Quidel Corporation : http://www.quidel.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 11:33:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id DD1F737B403 for ; Thu, 19 Jul 2001 11:33:31 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.3/8.9.3) with ESMTP id f6JIXSF65287; Thu, 19 Jul 2001 11:33:28 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f6JIXQw42095; Thu, 19 Jul 2001 11:33:26 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3B5692BC.77E9D994@mindspring.com> Date: Thu, 19 Jul 2001 11:33:26 -0700 (PDT) From: John Baldwin To: Terry Lambert Subject: Re: x86 unaligned access followup. Cc: Matthew Jacob , hackers@FreeBSD.ORG, kuehl@lgk.de Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 19-Jul-01 Terry Lambert wrote: > kuehl@lgk.de wrote: >> > A "shakedown cruise" could end up being very rough... you >> > would effectively need to check an "unaligned access in >> > kernel is OK" flag in many of these instances, and fall back >> > to doing the copy when it was false. >> >> ...therefore - never mind. >> Perhaps some app code may break. ;-) > > The point was that this code breaks on some architectures > supported by FreeBSD anyway, and moving at least some of > the pain onto x86 people would end up minimizing that > breakage. > > Right now, being able to make a bug break all architectures > equally looks pretty good to people having to keep up with > the x86 port of FreeBSD's rate of breakage of others, like > the Alpha, when people with just x86 hardware break things > without knowing it. It is very rare that the alpha port is broken as you describe. Sometimes a bug will have a different affect on the alpha than on x86, but except for bugs in sys/alpha that x86'ers won't be committing, very few of the bugs break just the alpha and not the x86 as well. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 11:38:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 8C5F737B401 for ; Thu, 19 Jul 2001 11:38:13 -0700 (PDT) (envelope-from msinz@wgate.com) Received: from sinz.eng.tvol.net ([10.32.2.99]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 3LH07KM4; Thu, 19 Jul 2001 14:37:49 -0400 Received: from wgate.com (localhost [127.0.0.1]) by sinz.eng.tvol.net (8.11.3/8.11.3) with ESMTP id f6JIc7N77239; Thu, 19 Jul 2001 14:38:08 -0400 (EDT) (envelope-from msinz@wgate.com) Message-ID: <3B57290F.15C009A5@wgate.com> Date: Thu, 19 Jul 2001 14:38:07 -0400 From: Michael Sinz Organization: WorldGate Communications Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Attila Nagy Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS local mount References: <20010719155719.N45187-100000@scribble.fsn.hu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Attila Nagy wrote: > > Hello, > > I am currently installing a machine on which I want to replace the NULL > and/or UNIONFS mounts with NFS. NFS server and client on the same machine, > to be exact, for jailing purposes (this seems to be the most stable). > > The problem is, that at the FreeBSD boot process the NFS filesystems are > mounted before the NFS-related daemons are started, so I can't do this in > a clean way (from /etc/fstab). > > Are there any objections to swap those two? I mean starting the NFS server > and after that mounting the NFS filesystems? That would be nice since I have a problem here at WorldGate where a number of machines mount drives from eachother. If only one of them goes down at a time things are fine, but after a power outage they all block trying to mount each other and thus never start up the NFS server such that they can mount each other. My "solution" has been to have the NFS mounts happen as a background process and thus letting the rest of the network startup run and thus getting to start the NFS servers which then answer these background NFS mount requests. I had been meaning to ask if there was a reason why NFS mounts happened before NFS servers were started but life kept getting in the way :-) -- Michael Sinz ---- Worldgate Communications ---- msinz@wgate.com A master's secrets are only as good as the master's ability to explain them to others. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 11:41:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id DF20137B401; Thu, 19 Jul 2001 11:41:28 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (mjacob@wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6JIfRS66833; Thu, 19 Jul 2001 11:41:28 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 19 Jul 2001 11:41:20 -0700 (PDT) From: Matthew Jacob Reply-To: To: John Baldwin Cc: Terry Lambert , , Subject: Re: x86 unaligned access followup. In-Reply-To: Message-ID: <20010719113955.H50024-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > It is very rare that the alpha port is broken as you describe. Sometimes > a bug will have a different affect on the alpha than on x86, but except > for bugs in sys/alpha that x86'ers won't be committing, very few of the bugs > break just the alpha and not the x86 as well. Generally this is true. Most of the alpha vs. x86 issues are found in compilation. Actually, to be fair, we'd have to consider all the kernel subsystems that have *not* in fact been tested on alpha. The dozens of warnings from NetGraph or CODA code indicate that there might be problems there, for instance. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 12: 1:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ra.eng.mindspring.net (ra.eng.mindspring.net [207.69.192.184]) by hub.freebsd.org (Postfix) with SMTP id 0C60137B408 for ; Thu, 19 Jul 2001 12:01:39 -0700 (PDT) (envelope-from sudish@mindspring.com) Received: (qmail 4026 invoked by uid 52477); 19 Jul 2001 19:01:12 -0000 To: Cc: John Baldwin , Terry Lambert , , Subject: Re: x86 unaligned access followup. References: <20010719113955.H50024-100000@wonky.feral.com> From: Sudish Joseph Date: 19 Jul 2001 15:01:12 -0400 In-Reply-To: <20010719113955.H50024-100000@wonky.feral.com> (Matthew Jacob's message of "Thu, 19 Jul 2001 11:41:20 -0700 (PDT)") Message-ID: Lines: 10 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) XEmacs/21.2 (Hera) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Jacob writes: > Actually, to be fair, we'd have to consider all the kernel subsystems that > have *not* in fact been tested on alpha. The dozens of warnings from NetGraph > or CODA code indicate that there might be problems there, for instance. NetGraph certainly has some 32-bit asssumptions embedded in it that actively break on an Alpha. See kern/27767. -- Sudish Joseph To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 12:12:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 578D837B409; Thu, 19 Jul 2001 12:12:26 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (mjacob@wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6JJCOS67364; Thu, 19 Jul 2001 12:12:24 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 19 Jul 2001 12:12:16 -0700 (PDT) From: Matthew Jacob Reply-To: To: Sudish Joseph Cc: John Baldwin , Terry Lambert , , Subject: Re: x86 unaligned access followup. In-Reply-To: Message-ID: <20010719121156.J50024-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Cool. Thanks. I'll rip it out of modules builds for alpha then- it'll save some time in kernel rebuilds. On 19 Jul 2001, Sudish Joseph wrote: > Matthew Jacob writes: > > Actually, to be fair, we'd have to consider all the kernel subsystems that > > have *not* in fact been tested on alpha. The dozens of warnings from NetGraph > > or CODA code indicate that there might be problems there, for instance. > > NetGraph certainly has some 32-bit asssumptions embedded in it that > actively break on an Alpha. See kern/27767. > > -- > Sudish Joseph > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 14:29:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id C1EF337B403 for ; Thu, 19 Jul 2001 14:29:12 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f6JLTBe05328; Thu, 19 Jul 2001 17:29:11 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FD9D73@l04.research.kpn.com> References: <59063B5B4D98D311BC0D0001FA7E452205FD9D73@l04.research.kpn.com> Date: Thu, 19 Jul 2001 17:29:10 -0400 To: freebsd-hackers@FreeBSD.ORG From: Garance A Drosihn Subject: RE: Suggestions for sysinstall / disklabel Cc: Bill Moran Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here's an example where the current behavior of sysinstall and/or disklabel got in the way of what I intended to do. Once I figured out what exactly was happening, I understand why it happens and how to get around it. Certainly I was doing a non-standard setup, but it "seemed simple enough", and the installer made it much more confusing. I have a large disk. I want to break it up into DOS-style slices of: s0: 1.87 gig - "not freebsd" s1: 1.25 gig - "not freebsd" s2: 2.75 gig - for booting into freebsd-stable s3: 17.x gig - for booting into freebsd-current, & holding home directories and the cvs repository. The disk was initially formatted to be a freebsd disk, and after I ran fdisk to pick new slice-sizes, every time freebsd boots it complains that the partition table in slice 0 is larger than the slice. (I have not actually installed anything in that slice yet). While that's true, whatever is complaining about that should not care about that because that partition IS NOT A FREEBSD SLICE, and nothing in my fstab refers to it... Anyway, back to the install. So I want to break up the two freebsd slices to be: s3: 2.75 gig - fbsd 4 2816m a: 96 M = 4.3 / e: 96 M = 5.x /x5/xRoot b: 256 M = /swap f: 96 M = 4.3 /xRoot g: 128 M = 4.3 /var h: 2.1 G = 4.3 /usr s4: 17.x gig - fbsd 5 a: 96 M = 5.x /x5 f: 128 M = /tmp g: 128 M = 5.x /x5/var h: 2.0 G = 5.x /x5/usr e: 512 M = /usr/home b: 10.1 G = /usr/cvs "/x5" is meant to be "/ for release 5", "/x5/var" is meant to be "/var for release 5", and "/x5/usr" is meant to be "/usr for release 5". Note that I do want to initialize both partitions at once, because both my "stable" and "current" systems will reference partitions which are in both slices. The "/xRoot" and "/x5/xRoot" partitions aren't particularly interesting for this discussion. other than those are extra partitions I do want to create there... During the disklabel step in the install process (an install I'm doing off the 4.3-release CD's), I go thru and create all the partitions on slice 3 with no trouble. So far so good. I go to create a "/x5" partition in slice 4, but it creates it as "partition e" instead of "partition a". I don't want it as partition e. Now, remember that during the boot-up process, the "boot0" code requires that the "partition to boot from" be the first partition in the slice. The "boot1" code assumes that the "partition to boot from" is labelled "partition a". So, that partition which I will want to be "/ for release 5" needs to be both the first partition in the slice, and it needs to be labelled "partition a". (Mind you, I only know this due to 20/20 hindsight. I couldn't have described it that clearly when I was trying to do this...). Why does disklabel make it "partition e"? Because it knows that it should use "partition a" for the partition which will be mounted as "/". Since I want to call this partition "/x5", it decides it must make it partition 'e' so that the 'a' label will still be available when (it assumes) I will later define that partition. Okay, so I go to trick disklabel. I rename the "a" partition in slice 3 to be something else, and go to create "/" is slice 4 (just so it will be partition a). But of course, disklabel knows it's utterly bogus to create "/" in slice 4 if the first freebsd slice is slice 3, so it won't let me do it. On the other hand, it only tells me "you aren't permitted to do that", and I'm in too stupid a mood to notice the obvious... I keep thinking that maybe slice 4 is too far into the disk, and maybe there is still a limit where you can only boot off the first 2 gig or 4 gig of a disk. Eventually I give up and create /x5 in slice 3 (as partition 'e' there). For awhile I stumble along by always booting up from slice 3, and then interrupting that boot process and typing in the commands to boot from slice 3 partition e when I want freebsd-current. This was interesting actually, as I learned a lot about what the new loader can do and how it works. Pretty nice stuff there. I tried booting from the first partition on slice 4 several times, but initially it didn't occur to me that since the slice was still labelled partition e, 'boot1' would not be able to work right. I finally realized that, and ran 'disklabel -r -e ad0s4c' to just rename partition 'a' to 'e' and visa-versa. I reboot into stable, fix the /etc/fstab for current (slice 4), and now it's working the way I wanted it. I can have slice 3 boot into release 4 and slice 4 boot into release 5. The problem for me here were all minor issues in disklabel during the install process, but they ended up causing a lot of run-around and man-page-reading before I sorted them out. Pretty much all of what it was doing was "sensible" once I understood it, it just happened to get in the way of what I personally wanted to do. And when you're sitting there with an empty 20-gig disk and no operating systems, you're not in much of a mood to go exploring into esoteric details of how all these pieces fit together. Perhaps this is the most frustrating thing about sysinstall, because when you run into a problem you can't just do a "half-assed job now, and fix it later". You have to figure it out right then or you're simply stuck. Anyway, the above is a long-winded justification for the following suggestions: 1) if disklabel has already been told about '/', then it should not try and reserve partition 'a' of OTHER SLICES to also be '/'. The first partition created in those other slices should just be labelled partition 'a'. 2) similarly, if it already has swap space defined, then it should not try to reserve partition 'b' of other slices to be swap. The second partition defined in those other slices should be labelled partition 'b'. [I don't feel quite as strongly about that, though] 3) somewhat more informative error messages might be nice, although I realize we also have the need to keep all of this code as small as possible, so an install can still be done via floppies. It would have been nice if it had said "You can't put '/' in slice 4 when booting from slice 3", for instance, instead of "You are not permitted to do that" (without mentioning the reason you're not permitted to do it). I came close to redoing the fdisk-step just to get slice 4 under the 4-gig mark, because I was guessing wrong as to the reason I was not permitted to create '/' there. Thinking about what people said about alpha installs, perhaps the following is another strategy disklabel could take. On the other hand, this may cause as many problems as it tries to solve. 4) never reserve 'a' or 'b'. Always create partitions in the order people typed them in, except that WHEN someone says they want to create '/', THEN both move that partition to the front of the slice and name it 'a' (renaming other partitions as needed). WHEN someone asks for swap, THEN name that partition 'b' and rename other partitions to match. I realize none of this is a crisis. I'm just trying to think up suggestions of how the initial disk-partitioning steps could be made a bit more user-friendly, even for deranged users like me. I would also note that I have been doing installs since 2.2.7, and I do also appreciate that this whole process has been getting better and better with each release. I just think there are still ways it could be made more flexible and "friendly", without getting into the way of people who really do know what they are doing. [btw, what is partition 'd' reserved for? why is it skipped over? certainly that's not an important question, I was just curious...] -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 15:34:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [64.211.219.50]) by hub.freebsd.org (Postfix) with ESMTP id 7973037B401 for ; Thu, 19 Jul 2001 15:34:06 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id PAA15550; Thu, 19 Jul 2001 15:33:57 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpdAAAXcaWrE; Thu Jul 19 15:33:45 2001 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id PAA14287; Thu, 19 Jul 2001 15:41:20 -0700 (MST) From: Terry Lambert Message-Id: <200107192241.PAA14287@usr05.primenet.com> Subject: Re: inpcb question To: sridharv@ufl.edu Date: Thu, 19 Jul 2001 22:41:10 +0000 (GMT) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ] I have written a kernel module and modified the stack ] code ( at the socket layer) to send control to my ] module. I am trying to access the inpcb structure ] associated with that particular socket. ] struct in_pcb* inp = sotoinpcb(so); ] if (inp) ] .... processing ] ] ] though the pbc structure is allocated i am getting a ] page fault everytime when i try to access it. ] any idea? my code is in the socket layer..i checked up ] the udp routines.. they do pretty much the same thing.. ] any help? It may be that the packets you are processing are not IP packets, and therefore do not have an in_pcb in them. Verify that they are IP packets first, e.g.: if (so->so_proto->pr_domain->dom_family == PF_INET) { struct in_pcb* inp = sotoinpcb(so); if (inp) { ... processing ... } } Pretty obvious in retrospect, eh? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 15:47:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from voyager.galileo.edu (samsara.galileo.edu [216.230.140.134]) by hub.freebsd.org (Postfix) with SMTP id 9E9D237B40E for ; Thu, 19 Jul 2001 15:47:32 -0700 (PDT) (envelope-from obonilla@galileo.edu) Received: (qmail 7052 invoked by uid 1001); 19 Jul 2001 22:48:02 -0000 Date: Thu, 19 Jul 2001 16:48:02 -0600 From: Oscar Bonilla To: freebsd-hackers@freebsd.org Subject: PF_LOCAL in getaddrinfo Message-ID: <20010719164802.A7043@galileo.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Mailer: Mutt 1.2i (2000-05-09) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I was trying to compile OpenLDAP 2 with support for ldapi:/// which uses the PF_LOCAL family. However, I've discovered that the PF_LOCAL entry in getaddrinfo is ifdef'd out. This is the relevant code for /usr/src/lib/libc/net/getaddrinfo.c #if 0 { PF_LOCAL, 0, ANY, ANY, NULL, 0x01 }, #endif Is this an error in the way OpenLDAP uses getaddrinfo or is there a reason for not supporting AF_LOCAL in calls to getaddrinfo? Thanks, -Oscar -- pgp public key: finger obonilla@galileo.edu pgp fingerprint: 9735 2F52 D499 17E2 D03B 5960 241D 09EA 349F 923E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 16:45:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 3D23B37B405 for ; Thu, 19 Jul 2001 16:45:25 -0700 (PDT) (envelope-from fmela0@sm.socccd.cc.ca.us) Received: from sm.socccd.cc.ca.us (pool0274.cvx14-bradley.dialup.earthlink.net [209.179.39.19]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id QAA14729 for ; Thu, 19 Jul 2001 16:45:23 -0700 (PDT) Message-ID: <3B5771B0.D5575CAC@sm.socccd.cc.ca.us> Date: Thu, 19 Jul 2001 16:48:00 -0700 From: Farooq Mela X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Status of agpgart device Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi hackers@, What is the status of the /dev/agpgart device? (I'm running 4.3-STABLE with a recent cvsup). Is it working, perhaps using a compatible interface with the linux device the of the same name (I can dream can't I ;-) ? I ask because I recently tried compiling Utah-GLX with AGP acceleration support, and it requires a /dev/agpgart device, but the testgart program errors out when it tries to ioctl the agpgart device. The Utah-GLX website all provides a tarball (http://utah-glx.sourceforge.net/gart/agpgart-freebsd-20000619.tar.gz) which includes a FreeBSD agpgart driver (as a KLD), but it fails to compile. I believe it was for the FreeBSD 3.x series, and has tons of compile errors. The documentation for the driver also states the as part of the installation, a /dev/agpgart must be built, yet I already had a /dev/agpgart device. This leads me to believe this driver is a bit antiquated. Any ideas? -- farooq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 17:10:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 6035237B401 for ; Thu, 19 Jul 2001 17:10:37 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (mjacob@wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6K0AUS71315; Thu, 19 Jul 2001 17:10:30 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 19 Jul 2001 17:10:21 -0700 (PDT) From: Matthew Jacob Reply-To: To: Geoff Mohler Cc: Subject: Re: wx0 jumbo frame support explosions.. In-Reply-To: Message-ID: <20010719171010.X50024-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Finally following up on this... was this with -current or -stable? On Mon, 9 Jul 2001, Geoff Mohler wrote: > When I enable jumbo frames in /usr/src/sys/pci.if_wx.c, and then set it > via 'ifconfig wx0 mtu 9000' once the new kernel is booted..my system > immediately goes zonkers...not even healthy enough to log. Just kernel > panic and reboot. > > Idears? > > --- > ****************************************** > *New & Improved: http://www.speedtoys.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 Thu Jul 19 17:34:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 7723D37B405 for ; Thu, 19 Jul 2001 17:34:35 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 20 Jul 2001 01:34:34 +0100 (BST) To: freebsd-hackers@freebsd.org Subject: Default retry behaviour for mount_nfs Date: Fri, 20 Jul 2001 01:34:34 +0100 From: Ian Dowse Message-ID: <200107200134.aa51462@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Shortly after the TI-RPC changes in -current, the default retry behaviour for mount_nfs was changed. Previously, mount_nfs would keep retrying for a long time (~1 week) if the server didn't respond, but since revision 1.40 of mount_nfs.c, it gives up on non-background mounts after one attempt. I didn't back out this change in default behaviour in my later commits to this file, since it seemed like a more reasonable default; NFS filesystems listed in fstab listed without any options can no longer hang the boot process waiting for the server to respond, and background mounts will succeed whenever the server comes up. I subsequently MFC'd this about 3 weeks ago. What I just remembered the other day is that there are a class of situations where you do want certain NFS mounts to hang the boot process if the server is down. These include cases where an NFS filesystem is critical to the boot process, so the machine will get stuck if it tries to proceed without it. The changes to mount_nfs had broken support for that situation, but I committed a fix to -current today that allows you to add `-R0' to the mount options to force mount_nfs to retry forever. So the question is - should I keep the new behaviour that is probably a better default and will catch out fewer new users but may surprise some experienced users, or should I revert to the traditional default where `-R1' or `-b' are required to avoid boot-time hangs? Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 17:36:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 1B0C037B401 for ; Thu, 19 Jul 2001 17:36:36 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (mjacob@wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6K0aWS71702; Thu, 19 Jul 2001 17:36:32 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 19 Jul 2001 17:36:24 -0700 (PDT) From: Matthew Jacob Reply-To: To: Ian Dowse Cc: Subject: Re: Default retry behaviour for mount_nfs In-Reply-To: <200107200134.aa51462@salmon.maths.tcd.ie> Message-ID: <20010719173612.Y50024-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FWIW, I vote 'yes' on the question in the last paragraph. On Fri, 20 Jul 2001, Ian Dowse wrote: > > Shortly after the TI-RPC changes in -current, the default retry > behaviour for mount_nfs was changed. Previously, mount_nfs would > keep retrying for a long time (~1 week) if the server didn't respond, > but since revision 1.40 of mount_nfs.c, it gives up on non-background > mounts after one attempt. > > I didn't back out this change in default behaviour in my later > commits to this file, since it seemed like a more reasonable default; > NFS filesystems listed in fstab listed without any options can no > longer hang the boot process waiting for the server to respond, > and background mounts will succeed whenever the server comes up. > I subsequently MFC'd this about 3 weeks ago. > > What I just remembered the other day is that there are a class of > situations where you do want certain NFS mounts to hang the boot > process if the server is down. These include cases where an NFS > filesystem is critical to the boot process, so the machine will > get stuck if it tries to proceed without it. The changes to mount_nfs > had broken support for that situation, but I committed a fix to > -current today that allows you to add `-R0' to the mount options > to force mount_nfs to retry forever. > > So the question is - should I keep the new behaviour that is probably > a better default and will catch out fewer new users but may surprise > some experienced users, or should I revert to the traditional > default where `-R1' or `-b' are required to avoid boot-time hangs? > > Ian > > 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 Jul 19 18:18:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 2196437B401 for ; Thu, 19 Jul 2001 18:18:50 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (mjacob@wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6K1IjS72274; Thu, 19 Jul 2001 18:18:45 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 19 Jul 2001 18:18:36 -0700 (PDT) From: Matthew Jacob Reply-To: To: Ian Dowse Cc: Subject: Re: Default retry behaviour for mount_nfs In-Reply-To: <200107200134.aa51462@salmon.maths.tcd.ie> Message-ID: <20010719181731.O50024-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > So the question is - should I keep the new behaviour that is probably > a better default and will catch out fewer new users but may surprise > some experienced users, or should I revert to the traditional > default where `-R1' or `-b' are required to avoid boot-time hangs? > Sorry- let me be clearer: FWIW, I vote that we rever to the traditional default and require -R1 or -b to avoid boot time hangs. The standard behaviour for most NFS implementations that I'm aware of would do this. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 18:51:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from speedracer.speedtoys.com (speedracer.speedtoys.com [216.36.69.26]) by hub.freebsd.org (Postfix) with ESMTP id E252F37B405 for ; Thu, 19 Jul 2001 18:51:35 -0700 (PDT) (envelope-from gemohler@www.speedtoys.com) Received: from localhost (gemohler@localhost) by speedracer.speedtoys.com (8.11.3/8.11.1) with ESMTP id f6K250c10218; Thu, 19 Jul 2001 19:05:00 -0700 (PDT) Date: Thu, 19 Jul 2001 19:04:59 -0700 (PDT) From: Geoff Mohler X-Sender: gemohler@speedracer.speedtoys.com To: Matthew Jacob Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: wx0 jumbo frame support explosions.. In-Reply-To: <20010719171010.X50024-100000@wonky.feral.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FreeBSD speedracer.speedtoys.com 4.3-RELEASE FreeBSD 4.3-RELEASE #3: On Thu, 19 Jul 2001, Matthew Jacob wrote: > > Finally following up on this... was this with -current or -stable? > > > On Mon, 9 Jul 2001, Geoff Mohler wrote: > > > When I enable jumbo frames in /usr/src/sys/pci.if_wx.c, and then set it > > via 'ifconfig wx0 mtu 9000' once the new kernel is booted..my system > > immediately goes zonkers...not even healthy enough to log. Just kernel > > panic and reboot. > > > > Idears? > > > > --- > > ****************************************** > > *New & Improved: http://www.speedtoys.com* > > ****************************************** > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > --- ******************************************* *New & Improved: http://www.speedtoys.com * ******************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 19:36:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 885) id BEB1337B406; Thu, 19 Jul 2001 19:36:48 -0700 (PDT) Date: Thu, 19 Jul 2001 19:36:48 -0700 From: Eric Melville To: Stijn Hoop Cc: hackers@freebsd.org Subject: Re: cvs commit: src/gnu/lib/libdialog checklist.c menubox.c radiolist.c textbox.c tree.c yesno.c Message-ID: <20010719193648.A81136@FreeBSD.org> References: <200107180521.f6I5Lbg64954@freefall.freebsd.org> <20010717224344.A9904@FreeBSD.org> <20010718092945.A13105@pcwin002.win.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010718092945.A13105@pcwin002.win.tue.nl>; from stijn@win.tue.nl on Wed, Jul 18, 2001 at 09:29:45AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I can't tell any more how many times this annoying libdialog has bitten me > in this regard. Don't think you're the only one :) > Even better - I take it sysinstall then uses 'sane' space/enter combo's > also (it being a consumer of libdialog)? Yes, my big purpose here was to make sysinstall a little nicer. There may be plans to abandon it, but at very least the next few releases will be using it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 20:14:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 7E1D837B405 for ; Thu, 19 Jul 2001 20:14:25 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6K3EMS73689; Thu, 19 Jul 2001 20:14:22 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 19 Jul 2001 20:14:22 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Geoff Mohler Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: wx0 jumbo frame support explosions.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ah. Well, it doesn't crash in FreeBSD-current. It doesn't work well *either*, but.... I'm curious- was wx0 resident or was it kldload'ed by the ifconfig? -matt On Thu, 19 Jul 2001, Geoff Mohler wrote: > FreeBSD speedracer.speedtoys.com 4.3-RELEASE FreeBSD 4.3-RELEASE #3: > > On Thu, 19 Jul 2001, Matthew Jacob wrote: > > > > > Finally following up on this... was this with -current or -stable? > > > > > > On Mon, 9 Jul 2001, Geoff Mohler wrote: > > > > > When I enable jumbo frames in /usr/src/sys/pci.if_wx.c, and then set it > > > via 'ifconfig wx0 mtu 9000' once the new kernel is booted..my system > > > immediately goes zonkers...not even healthy enough to log. Just kernel > > > panic and reboot. > > > > > > Idears? > > > > > > --- > > > ****************************************** > > > *New & Improved: http://www.speedtoys.com* > > > ****************************************** > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > > > --- > ******************************************* > *New & Improved: http://www.speedtoys.com * > ******************************************* > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 20:17:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from speedracer.speedtoys.com (speedracer.speedtoys.com [216.36.69.26]) by hub.freebsd.org (Postfix) with ESMTP id 6C3F237B407 for ; Thu, 19 Jul 2001 20:17:40 -0700 (PDT) (envelope-from gemohler@www.speedtoys.com) Received: from localhost (gemohler@localhost) by speedracer.speedtoys.com (8.11.3/8.11.1) with ESMTP id f6K3V4D18012; Thu, 19 Jul 2001 20:31:04 -0700 (PDT) Date: Thu, 19 Jul 2001 20:31:04 -0700 (PDT) From: Geoff Mohler X-Sender: gemohler@speedracer.speedtoys.com To: Matthew Jacob Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: wx0 jumbo frame support explosions.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It would crash when I forced the large MTU size when already running at the default MTU size. I would reconfig the Netapp box to jumbo, then ifconfig up the wx0 interface..bang crash. On Thu, 19 Jul 2001, Matthew Jacob wrote: > > Ah. Well, it doesn't crash in FreeBSD-current. It doesn't work well *either*, > but.... > > I'm curious- was wx0 resident or was it kldload'ed by the ifconfig? > > -matt > > > On Thu, 19 Jul 2001, Geoff Mohler wrote: > > > FreeBSD speedracer.speedtoys.com 4.3-RELEASE FreeBSD 4.3-RELEASE #3: > > > > On Thu, 19 Jul 2001, Matthew Jacob wrote: > > > > > > > > Finally following up on this... was this with -current or -stable? > > > > > > > > > On Mon, 9 Jul 2001, Geoff Mohler wrote: > > > > > > > When I enable jumbo frames in /usr/src/sys/pci.if_wx.c, and then set it > > > > via 'ifconfig wx0 mtu 9000' once the new kernel is booted..my system > > > > immediately goes zonkers...not even healthy enough to log. Just kernel > > > > panic and reboot. > > > > > > > > Idears? > > > > > > > > --- > > > > ****************************************** > > > > *New & Improved: http://www.speedtoys.com* > > > > ****************************************** > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > > > > > > > > --- > > ******************************************* > > *New & Improved: http://www.speedtoys.com * > > ******************************************* > > > > > > --- ******************************************* *New & Improved: http://www.speedtoys.com * ******************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 21:49:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id CDC5337B406; Thu, 19 Jul 2001 21:49:46 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f6K4ncn72103; Fri, 20 Jul 2001 06:49:38 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: hackers@freebsd.org, developers@freebsd.org Subject: Close a PR! - we're still not done... From: Poul-Henning Kamp Date: Fri, 20 Jul 2001 06:49:38 +0200 Message-ID: <72101.995604578@critter> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As you can see on http://phk.freebsd.dk/Gnats/ We have managed to shave 600 PR's off the total by doing a concerted effort, and thanks to a few dedicated people we have managed to avoid an increase despite the fact that people have "forgotten" to close PRs again. Basically, we're at 2400 non-closed PRs today, that means that we are at the same level as october 2000. We need to do better than that, once we release 5.0 we will have PR's left right and center and we don't want a couple of thousand old ones cluttering the view. So, CLOSE a PR today! If you are not a committer you do it by submitting a followup with the text This PR can be closed on a line of its own. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 22:13:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gnf.org (firewall.gnf.org [208.44.31.34]) by hub.freebsd.org (Postfix) with ESMTP id 4ED0A37B409; Thu, 19 Jul 2001 22:13:29 -0700 (PDT) (envelope-from gordont@gnf.org) Received: by mail.gnf.org (Postfix, from userid 888) id E3A4E11E50D; Thu, 19 Jul 2001 22:08:38 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id E1CAD11A56A; Thu, 19 Jul 2001 22:08:38 -0700 (PDT) Date: Thu, 19 Jul 2001 22:08:38 -0700 (PDT) From: Gordon Tetlow To: Mike Smith Cc: Subject: Kernel module options Was: Re: Fw: help me!!!! In-Reply-To: <200107142103.f6EL3Ca01348@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 14 Jul 2001, Mike Smith wrote: > > >and how to compile the individual module, which > > >should reflect changes in kenel also? ...... > > Modules are built as part of the kernel build. You can also build > modules idependantly in sys/modules. Note that module code should not > depend on options from the kernel configuration file (or if they do, > these options need to be set up seperately in the module's Makefile). This reminded me of a case I see all too often. I hang out in #freebsd and #freebsdhelp on OPN and all too often, there are people that come into the channel trying to set up their firewall box using ipfw/natd and a GENERIC kernel. Well, as I'm sure everyone is acquainted, you have to compile a kernel to get IPFIREWALL/IPDIVERT into your kernel so you can do natd. I'd love to see one of the following: 1) When compiling the ipfw.ko, include the ipdivert code. 2) A seperate module that is ipfw + divert (ipfwdivert.ko?) 3) Steal an idea from Linux (gasp!), and have module dependencies. ie, load ipfw.ko and then before we load up natd, we check to see if ipdivert.ko is loaded and load it. Alternatively, loading ipdivert.ko (before loading ipfw.ko), will automagically load ipfw.ko since ipfw is needed to get divert running. Now, obviously 1 or 2 should be pretty easy to do. I imagine 3 would require some infrastructure support that isn't there yet. I must say, the only thing I really like about Linux is the efforts they've gone to to make everything modular. Anyway, is there in future in this? -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 22:22:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from softweyr.com (softweyr.com [208.247.99.111]) by hub.freebsd.org (Postfix) with ESMTP id EF93137B405 for ; Thu, 19 Jul 2001 22:22:40 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from localhost.softweyr.com ([127.0.0.1] helo=softweyr.com ident=bd2ff58fd6354b5fc5352d61088ffa07) by softweyr.com with esmtp (Exim 3.16 #1) id 15NSpD-0000gA-00; Thu, 19 Jul 2001 23:27:43 -0600 Message-ID: <3B57C14F.746C95A6@softweyr.com> Date: Thu, 19 Jul 2001 23:27:43 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Joerg Micheel , David Scheidt , Max Khon , freebsd-hackers@freebsd.org Subject: Re: arcnet support for FreeBSD (request for review) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer wrote: > > On Thu, 19 Jul 2001, Joerg Micheel wrote: > > > On Thu, Jul 19, 2001 at 02:35:51AM -0500, David Scheidt wrote: > > > On Thu, 19 Jul 2001, Julian Elischer wrote: > > > > > > :Max Khon wrote: > > > :> > > > :> hi, there! > > > : > > > :what is arcnet? > > > : > > > > > > It's a token-based LAN protocol. It's used in some embedded applications, > > > as its controllers are cheap, it's pretty low-overhead, and has > > > deterministic behavior (you can calculate the worst case time to send a > > > message to another station). Industrial controlers and data acquistion are > > > the two uses that jump out of my memory. > > > > David, Julian was kidding you. Read his response again. > > I'm flattered that you think I was kidding.. > actually I had no clue what Arcnet was :-) Kids these days, eh, Joerg? ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 22:26:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from taupo.cs.waikato.ac.nz (taupo.cs.waikato.ac.nz [130.217.241.30]) by hub.freebsd.org (Postfix) with ESMTP id 60F2E37B405 for ; Thu, 19 Jul 2001 22:26:10 -0700 (PDT) (envelope-from joerg@taupo.cs.waikato.ac.nz) Received: (from joerg@localhost) by taupo.cs.waikato.ac.nz (8.11.3/8.11.1) id f6K5PW499398; Fri, 20 Jul 2001 17:25:32 +1200 (NZST) (envelope-from joerg) Date: Fri, 20 Jul 2001 17:25:32 +1200 From: Joerg Micheel To: Wes Peters Cc: Julian Elischer , David Scheidt , Max Khon , freebsd-hackers@freebsd.org, joerg@cs.waikato.ac.nz Subject: Re: arcnet support for FreeBSD (request for review) Message-ID: <20010720172532.C86361@cs.waikato.ac.nz> References: <3B57C14F.746C95A6@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B57C14F.746C95A6@softweyr.com>; from wes@softweyr.com on Thu, Jul 19, 2001 at 11:27:43PM -0600 Organization: Dept of Computer Science, University of Waikato, Hamilton, New Zealand Project: WAND - Waikato Applied Network Dynamics, DAG Operating-System: ... powered by FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jul 19, 2001 at 11:27:43PM -0600, Wes Peters wrote: > Julian Elischer wrote: > > > > On Thu, 19 Jul 2001, Joerg Micheel wrote: > > > > > On Thu, Jul 19, 2001 at 02:35:51AM -0500, David Scheidt wrote: > > > > On Thu, 19 Jul 2001, Julian Elischer wrote: > > > > > > > > :Max Khon wrote: > > > > :> > > > > :> hi, there! > > > > : > > > > :what is arcnet? > > > > : > > > > > > > > It's a token-based LAN protocol. It's used in some embedded applications, > > > > as its controllers are cheap, it's pretty low-overhead, and has > > > > deterministic behavior (you can calculate the worst case time to send a > > > > message to another station). Industrial controlers and data acquistion are > > > > the two uses that jump out of my memory. > > > > > > David, Julian was kidding you. Read his response again. > > > > I'm flattered that you think I was kidding.. > > actually I had no clue what Arcnet was :-) > > Kids these days, eh, Joerg? ;^) Hmm. Not exactly an oldie myself, but I did have this time warp in my life when coming out of Russia. So, can picture Max' interest in ArcNet, at least at the hobby level. Around here, students build Wavelan's with Lucent cards and an omni antenna and share a 6MBit ADSL link within the neighbourhood. Most students have better Internet access at home for themselves than the whole University :-). Joerg -- Joerg B. Micheel Email: WAND and NLANR MOAT Email: The University of Waikato, CompScience Phone: +64 7 8384794 Private Bag 3105 Fax: +64 7 8585095 Hamilton, New Zealand Plan: PMA, TINE and the DAG's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 22:33:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gnf.org (firewall.gnf.org [208.44.31.34]) by hub.freebsd.org (Postfix) with ESMTP id B9AA237B406 for ; Thu, 19 Jul 2001 22:33:13 -0700 (PDT) (envelope-from gordont@gnf.org) Received: by mail.gnf.org (Postfix, from userid 888) id 7A41611E50F; Thu, 19 Jul 2001 22:28:20 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id 787E811A56A; Thu, 19 Jul 2001 22:28:20 -0700 (PDT) Date: Thu, 19 Jul 2001 22:28:20 -0700 (PDT) From: Gordon Tetlow To: Matthew Jacob Cc: Ian Dowse , Subject: Re: Default retry behaviour for mount_nfs In-Reply-To: <20010719181731.O50024-100000@wonky.feral.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 19 Jul 2001, Matthew Jacob wrote: > > > > So the question is - should I keep the new behaviour that is probably > > a better default and will catch out fewer new users but may surprise > > some experienced users, or should I revert to the traditional > > default where `-R1' or `-b' are required to avoid boot-time hangs? > > > > Sorry- let me be clearer: > > FWIW, I vote that we rever to the traditional default and require -R1 or -b to > avoid boot time hangs. The standard behaviour for most NFS implementations > that I'm aware of would do this. I was playing with a RedHat 7.1 box (kernel 2.4.x) and it continued along after it failed to mount and NFS server. I personally think the non-blocking behavior is better. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 22:38:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 1210237B409 for ; Thu, 19 Jul 2001 22:38:29 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6K5cKS75516; Thu, 19 Jul 2001 22:38:20 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 19 Jul 2001 22:38:20 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Gordon Tetlow Cc: Ian Dowse , freebsd-hackers@FreeBSD.ORG Subject: Re: Default retry behaviour for mount_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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 19 Jul 2001, Gordon Tetlow wrote: > On Thu, 19 Jul 2001, Matthew Jacob wrote: > > > > > > > So the question is - should I keep the new behaviour that is probably > > > a better default and will catch out fewer new users but may surprise > > > some experienced users, or should I revert to the traditional > > > default where `-R1' or `-b' are required to avoid boot-time hangs? > > > > > > > Sorry- let me be clearer: > > > > FWIW, I vote that we rever to the traditional default and require -R1 or -b to > > avoid boot time hangs. The standard behaviour for most NFS implementations > > that I'm aware of would do this. > > I was playing with a RedHat 7.1 box (kernel 2.4.x) and it continued along > after it failed to mount and NFS server. Did it background? > I personally think the non-blocking behavior is better. In some cases, yes, in some cases, no. It's POLA to change it. If I don't care about an FS, I'll set it to be -bg. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 22:46:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gnf.org (firewall.gnf.org [208.44.31.34]) by hub.freebsd.org (Postfix) with ESMTP id 6F87337B408 for ; Thu, 19 Jul 2001 22:46:10 -0700 (PDT) (envelope-from gordont@gnf.org) Received: by mail.gnf.org (Postfix, from userid 888) id 1305111E50D; Thu, 19 Jul 2001 22:41:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id 10F5911A56A; Thu, 19 Jul 2001 22:41:15 -0700 (PDT) Date: Thu, 19 Jul 2001 22:41:15 -0700 (PDT) From: Gordon Tetlow To: Matthew Jacob Cc: Ian Dowse , Subject: Re: Default retry behaviour for mount_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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 19 Jul 2001, Matthew Jacob wrote: > > On Thu, 19 Jul 2001, Gordon Tetlow wrote: > > > On Thu, 19 Jul 2001, Matthew Jacob wrote: > > > > > > So the question is - should I keep the new behaviour that is probably > > > > a better default and will catch out fewer new users but may surprise > > > > some experienced users, or should I revert to the traditional > > > > default where `-R1' or `-b' are required to avoid boot-time hangs? > > > > > > > > > > Sorry- let me be clearer: > > > > > > FWIW, I vote that we rever to the traditional default and require -R1 or -b to > > > avoid boot time hangs. The standard behaviour for most NFS implementations > > > that I'm aware of would do this. > > > > I was playing with a RedHat 7.1 box (kernel 2.4.x) and it continued along > > after it failed to mount and NFS server. > > Did it background? Hmm, I don't believe so. It was a temporary network glitch (damn flaky distribution switch) and the user wasn't able to login via xdm (his home directory was on the NFS partition in question). > > I personally think the non-blocking behavior is better. > > In some cases, yes, in some cases, no. It's POLA to change it. > If I don't care about an FS, I'll set it to be -bg. Hmm, maybe we should implement the notion of "critical_local" and "critical_net" filesystems (a la NetBSD). Heck, I don't even need the distinction between net and local, just critical would do. All remote, critical filesystems would be blocking, and all others not. Sometimes the stick of POLA should be broken. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 22:48:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 954ED37B407 for ; Thu, 19 Jul 2001 22:48:42 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6K5mZS75689; Thu, 19 Jul 2001 22:48:35 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 19 Jul 2001 22:48:34 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Gordon Tetlow Cc: Ian Dowse , freebsd-hackers@FreeBSD.ORG Subject: Re: Default retry behaviour for mount_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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Hmm, I don't believe so. It was a temporary network glitch (damn flaky > distribution switch) and the user wasn't able to login via xdm (his home > directory was on the NFS partition in question). > > > > I personally think the non-blocking behavior is better. > > > > In some cases, yes, in some cases, no. It's POLA to change it. > > If I don't care about an FS, I'll set it to be -bg. > > Hmm, maybe we should implement the notion of "critical_local" and > "critical_net" filesystems (a la NetBSD). Heck, I don't even need the > distinction between net and local, just critical would do. All remote, > critical filesystems would be blocking, and all others not. > > Sometimes the stick of POLA should be broken. Not if it adds work. Oddly enough, one of the few virtues BSD Unix has is that it's very conservative. Well, we could argue this forever- and both of us would be right! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 23:24:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cokane.org (ip-216-23-49-49.adsl.one.net [216.23.49.49]) by hub.freebsd.org (Postfix) with ESMTP id 3440437B405 for ; Thu, 19 Jul 2001 23:24:40 -0700 (PDT) (envelope-from cokane@cokane.org) Received: (from cokane@localhost) by cokane.org (8.11.4/8.11.4) id f6KIRer00486; Fri, 20 Jul 2001 14:27:40 -0400 (EDT) (envelope-from cokane) Date: Fri, 20 Jul 2001 14:27:39 -0400 From: Coleman Kane To: Farooq Mela Cc: hackers@FreeBSD.ORG Subject: Re: Status of agpgart device Message-ID: <20010720142738.A456@evil.apt> References: <3B5771B0.D5575CAC@sm.socccd.cc.ca.us> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B5771B0.D5575CAC@sm.socccd.cc.ca.us>; from fmela0@sm.socccd.cc.ca.us on Thu, Jul 19, 2001 at 04:48:00PM -0700 X-VIM-Settings: vim:ts=4:sw=4:tw=70: X-Operating-System: FreeBSD evil.apt 5.0-CURRENT FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 4.3-RELEASE comes with an agp device. Simply add agp_load=3D"YES" to your /boot/loader.conf file, or device agp to your kernel config file. It=20 only supports certain AGP bridges though, look in /usr/src/sys/pci/agp* for more info. On Thu, Jul 19, 2001 at 04:48:00PM -0700, Farooq Mela wrote, and it was pro= claimed: > Hi hackers@, >=20 > What is the status of the /dev/agpgart device? (I'm running 4.3-STABLE > with a recent cvsup). Is it working, perhaps using a compatible > interface with the linux device the of the same name (I can dream > can't I ;-) ? I ask because I recently tried compiling Utah-GLX with > AGP acceleration support, and it requires a /dev/agpgart device, but > the testgart program errors out when it tries to ioctl the agpgart > device. >=20 > The Utah-GLX website all provides a tarball > (http://utah-glx.sourceforge.net/gart/agpgart-freebsd-20000619.tar.gz) > which includes a FreeBSD agpgart driver (as a KLD), but it fails to > compile. I believe it was for the FreeBSD 3.x series, and has tons of > compile errors. The documentation for the driver also states the as > part of the installation, a /dev/agpgart must be built, yet I already > had a /dev/agpgart device. This leads me to believe this driver is a > bit antiquated. >=20 > Any ideas? >=20 > --=20 > farooq >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message >=20 --9amGYk9869ThD9tj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7WHgZERViMObJ880RAn2QAKCb/BvE/IdW5vwIYI072OBPtPalgACfdP2j aIeaGybL/s04J/d2azioH9Y= =TG8k -----END PGP SIGNATURE----- --9amGYk9869ThD9tj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jul 19 23:56:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 439C037B401 for ; Thu, 19 Jul 2001 23:56:51 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.11.4/8.11.4) with ESMTP id f6K6ull57318 for ; Fri, 20 Jul 2001 13:56:48 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Fri, 20 Jul 2001 13:56:47 +0700 (NSS) From: Max Khon To: freebsd-hackers@freebsd.org Subject: Re: arcnet support for FreeBSD (request for review) In-Reply-To: <20010720172532.C86361@cs.waikato.ac.nz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, there! On Fri, 20 Jul 2001, Joerg Micheel wrote: > Hmm. Not exactly an oldie myself, but I did have this time warp in > my life when coming out of Russia. So, can picture Max' interest in > ArcNet, at least at the hobby level. Around here, students build > Wavelan's with Lucent cards and an omni antenna and share a 6MBit > ADSL link within the neighbourhood. Most students have better Internet > access at home for themselves than the whole University :-). I am not a student as you might think. I graduated from the university about three years ago. The reason I am trying to push Arcnet drivers is that people continue to ask me about availability of Arcnet drivers for FreeBSD. Yes, it's a kind of hobby for me. I'd be very glad if at least ARP code will be committed to FreeBSD tree so I could maintain drivers more easily. Who is the maintainer of ARP code these days? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 1:23:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id D8C0A37B403; Fri, 20 Jul 2001 01:23:36 -0700 (PDT) (envelope-from fmela0@sm.socccd.cc.ca.us) Received: from sm.socccd.cc.ca.us (pool0304.cvx14-bradley.dialup.earthlink.net [209.179.39.49]) by falcon.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA21502; Fri, 20 Jul 2001 01:23:25 -0700 (PDT) Message-ID: <3B57EB1B.632B6EF0@sm.socccd.cc.ca.us> Date: Fri, 20 Jul 2001 01:26:03 -0700 From: Farooq Mela X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Coleman Kane Cc: hackers@FreeBSD.ORG Subject: Re: Status of agpgart device References: <3B5771B0.D5575CAC@sm.socccd.cc.ca.us> <20010720142738.A456@evil.apt> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Right, I've already got that: agp0: mem 0xf8000000-0xfbffffff at device 0.0 on pci0 That still doesnt answer my question about the agpgart (AGP g-something address resolution table, or something similar - needed for high-performance memory transfers). -- Coleman Kane wrote: > > 4.3-RELEASE comes with an agp device. Simply add agp_load="YES" to your > /boot/loader.conf file, or device agp to your kernel config file. It > only supports certain AGP bridges though, look in /usr/src/sys/pci/agp* > for more info. > > On Thu, Jul 19, 2001 at 04:48:00PM -0700, Farooq Mela wrote, and it was proclaimed: > > Hi hackers@, > > > > What is the status of the /dev/agpgart device? (I'm running 4.3-STABLE > > with a recent cvsup). Is it working, perhaps using a compatible > > interface with the linux device the of the same name (I can dream > > can't I ;-) ? I ask because I recently tried compiling Utah-GLX with > > AGP acceleration support, and it requires a /dev/agpgart device, but > > the testgart program errors out when it tries to ioctl the agpgart > > device. > > > > The Utah-GLX website all provides a tarball > > (http://utah-glx.sourceforge.net/gart/agpgart-freebsd-20000619.tar.gz) > > which includes a FreeBSD agpgart driver (as a KLD), but it fails to > > compile. I believe it was for the FreeBSD 3.x series, and has tons of > > compile errors. The documentation for the driver also states the as > > part of the installation, a /dev/agpgart must be built, yet I already > > had a /dev/agpgart device. This leads me to believe this driver is a > > bit antiquated. > > > > Any ideas? > > > > -- > > farooq > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > ---------------------------------------------------------------------- > Part 1.2Type: application/pgp-signature farooq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 1:40: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 1985737B403; Fri, 20 Jul 2001 01:39:58 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f6K8d4V01460; Fri, 20 Jul 2001 01:39:05 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200107200839.f6K8d4V01460@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gordon Tetlow Cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel module options Was: Re: Fw: help me!!!! In-reply-to: Your message of "Thu, 19 Jul 2001 22:08:38 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Jul 2001 01:39:04 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > 3) Steal an idea from Linux (gasp!), and have module dependencies. ie, > load ipfw.ko and then before we load up natd, we check to see if > ipdivert.ko is loaded and load it. Alternatively, loading ipdivert.ko > (before loading ipfw.ko), will automagically load ipfw.ko since ipfw is > needed to get divert running. We've had this support for a long time already; module authors just aren't taking advantage of it. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 2:17:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 2CA5F37B405 for ; Fri, 20 Jul 2001 02:17:10 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id C3FD93E31 for ; Fri, 20 Jul 2001 02:17:09 -0700 (PDT) To: hackers@freebsd.org Subject: Proper way for *config(8) to load corresponding modules Date: Fri, 20 Jul 2001 02:17:09 -0700 From: Dima Dorfman Message-Id: <20010720091709.C3FD93E31@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Most *config(8) programs, such as ifconfig(8), mdconfig(8), and ccdconfig(8), attempt to load their corresponding module if it isn't already loaded, or already compiled into the kernel. Looking at these programs, they achieve this task in (primarily) two different ways. The first uses modfind() then kldload() (e.g., see ccdconfig.c r1.19 l174). Others use a combination of kldnext(), modfnext(), and some loops to do this (e.g., see ifconfig.c r1.64 l1911). Is there any difference between these two, and which one is preferred (I'd think the former if there is no difference). It would be nice if they all did the same thing. Once it's determined which method is preferred, I'd like to propose a kldmaybeload(3) routine that takes a module name and loads it if it's not already loaded or compiled in. For now this just factors out some common code, but it may save headaches later if the kld interface is changed so that neither of these methods work without modification (with a kldmaybeload, it'd be sufficient just to modify the library function). Thanks for any insight. Dima Dorfman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 2:17:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web5301.mail.yahoo.com (web5301.mail.yahoo.com [216.115.106.110]) by hub.freebsd.org (Postfix) with SMTP id 209BE37B403 for ; Fri, 20 Jul 2001 02:17:21 -0700 (PDT) (envelope-from vishubp@yahoo.com) Message-ID: <20010720091720.28756.qmail@web5301.mail.yahoo.com> Received: from [203.200.20.3] by web5301.mail.yahoo.com via HTTP; Fri, 20 Jul 2001 10:17:20 BST Date: Fri, 20 Jul 2001 10:17:20 +0100 (BST) From: =?iso-8859-1?q?vishwanath=20pargaonkar?= Subject: kernel malloc To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, can any one please help me with this. i want allocate a memory in the kernel -a buffer of size 2k to 5k. can i do it using malloc with second parameter as M_TEMP and third as M_WAITOK. can anybody tell me what M_TEMP means .what is maximum malloc i can do with M_TEMP? will the OS allow me to malloc 4k buffer in side kernel??shd i give M_WAITOK or M_DONTWAIT??? please tell me. thanx in advance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 6:42:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id D6DE137B401; Fri, 20 Jul 2001 06:42:21 -0700 (PDT) (envelope-from wiredbrain@earthlink.net) Received: from pflaump (sdn-ar-001flhhilP292.dialsprint.net [168.191.68.30]) by albatross.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id GAA24842; Fri, 20 Jul 2001 06:03:30 -0700 (PDT) Message-ID: <001501c1111d$15b6a660$1e44bfa8@pflaump> Reply-To: "Peter Pflaum" From: "Peter Pflaum" To: Subject: Panel Argues for Changing Social Security Date: Fri, 20 Jul 2001 09:01:45 -0400 Organization: GlobalVillage Schools MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0008_01C110FA.9A6281E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2479.0006 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0008_01C110FA.9A6281E0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0009_01C110FA.9A6BA9A0" ------=_NextPart_001_0009_01C110FA.9A6BA9A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The Bush commission's report said the key date was 2016. That is when = payroll tax revenues flowing into Social Security from workers and = employers will fall short of benefit payments for the first time. At = that point, the system will begin relying in part on interest payments = from its vast holdings of government bonds - the Social Security trust = fund. But the bonds and the interest on them are nothing more than commitments = by the government to help pay future benefits out of general tax = revenues, meaning that Social Security will begin to impinge on the rest = of the budget. http://www.nytimes.com/2001/07/20/politics/20SOCI.html Now if those "trust funds" were invested in other than IOU's from the = Government to the Government they could earn more and be real. = Individual accounts are much more complex - alternative investments = could include foreign bonds which would help the balance of payments - = Bank CD would add to domestic savings and lower interest rates , index = funds are not the only investment alternative.=20 http://www.wiredbrain.com/public-policy.htm suggests a Federal Assets = Management Agency - like other pension funds. If the surplus now coming = into the trust funds over the next 10 years were used to create a real = reserve fund - several trillion dollars would be in the fund. It would = remove the temptation to spend theses funds and have real earning = (compound interest) added to them.=20 ------=_NextPart_001_0009_01C110FA.9A6BA9A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

The Bush commission's report said the key date was 2016. That is when = payroll=20 tax revenues flowing into Social Security from workers and employers = will fall=20 short of benefit payments for the first time. At that point, the system = will=20 begin relying in part on interest payments from its vast holdings of = government=20 bonds =97 the Social Security trust fund.

But the bonds and the interest on them are nothing more than = commitments by=20 the government to help pay future benefits out of general tax revenues, = meaning=20 that Social Security will begin to impinge on the rest of the=20 budget.

 http://ww= w.nytimes.com/2001/07/20/politics/20SOCI.html
 
Now if those "trust funds" = were invested=20 in other than IOU's from the Government to the Government they could = earn more=20 and be real. Individual accounts are much more complex - = alternative=20 investments could include foreign bonds which would help the balance of = payments=20 - Bank CD would add to domestic savings and lower interest rates , index = funds=20 are not the only investment alternative. 
 
 http://www.wiredbrai= n.com/public-policy.htm=20 suggests a Federal Assets Management Agency - like other pension funds. = If the=20 surplus now coming into the trust funds over the next 10 years were used = to=20 create a real reserve fund - several trillion dollars would be in the = fund. It=20 would remove the temptation to spend theses funds and have real earning=20 (compound interest) added to them.
 
 
------=_NextPart_001_0009_01C110FA.9A6BA9A0-- ------=_NextPart_000_0008_01C110FA.9A6281E0 Content-Type: application/octet-stream; name="Panel Argues for Changing Social Security.url" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Panel Argues for Changing Social Security.url" [DEFAULT] BASEURL=http://www.nytimes.com/2001/07/20/politics/20SOCI.html [InternetShortcut] URL=http://www.nytimes.com/2001/07/20/politics/20SOCI.html Modified=406D07661611C10103 ------=_NextPart_000_0008_01C110FA.9A6281E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 6:42:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 7AE4D37B41A; Fri, 20 Jul 2001 06:42:35 -0700 (PDT) (envelope-from wiredbrain@earthlink.net) Received: from pflaump (sdn-ar-001flhhilP292.dialsprint.net [168.191.68.30]) by albatross.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id GAA11407; Fri, 20 Jul 2001 06:08:39 -0700 (PDT) Message-ID: <001601c1111d$7c9be5c0$1e44bfa8@pflaump> Reply-To: "Peter Pflaum" From: "Peter Pflaum" To: "The Rev. John Liebler" References: Subject: Re: CNN.com - Sen. Frist backs embryonic stem cell research - July 19, 2001 Date: Fri, 20 Jul 2001 09:03:27 -0400 Organization: GlobalVillage Schools MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2479.0006 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "The Rev. John Liebler" To: "Peter Pflaum" Sent: Thursday, July 19, 2001 10:03 PM Subject: CNN.com - Sen. Frist backs embryonic stem cell research - July 19, 2001 > These seem reasonable enough, don't they? No maybe 8 of the 10 but these rules come from transplants of the spare parts of brain dead people to others that need them. It assumes that all human living matter, protoplasm, bioplasm, ectoplasm, tissue, living tissue macromolecule, bioplast cell, unicellular organism, have a soul, spirit - true of frogs and fish and our poodles ? How about blood donors ? The problems is with No. 2 - we can use them but we can't be involved with derivation -but can use them. The goal here is to produce cells on a large scale that will replace ones that are not working - cloning of cells not people ( putting DNA from the patient into the cells so they fit better ) many cells lines need to exist because these cells reproduce endlessly while adult cells do not. BUT we can agree on this and move on. As soon as there are active treatments for major problems it can't be put back in the bottle. America is not the world and it will spread at the speed of light. I don't know how the drug companies will control cells but they will figure out a way. > > A senior aide to Frist outlined 10 conditions on which his support is based: > -- A ban on the creation of embryos for research purposes > -- A continued funding ban on "derivation," meaning federal dollars could be > spent to research embryos and stem cells only obtained through private > funding > -- A ban on human cloning > -- An increase in government funding for adult stem cell research > -- A restriction on funding for embryonic stem cell research only in the > earliest embryonic stage > -- A rigorous "informed consent" rule modeled on those now in place for > organ donation, giving donors the right to decide whether to put the embryo > up for adoption or to discard the embryo. If the donor chooses to discard > the embryo, he or she must approve the embryo's use for research. > -- A limit on the number of stem cell "lines" taken from each embryo in > order to minimize bio-ethical problems > -- A new public research oversight mechanism that would establish public > research guidelines, including a national research registry > -- An ongoing scientific and ethical review by The Institute of Medicine and > the creation of an independent presidential advisory panel to review the > bio-ethical implications of stem-cell research. The review would also > require the secretary of Health and Human Services to report to Congress > annually on the status on federal grants for stem cell research. > -- Strengthen and harmonize embryonic research restrictions to mirror fetal > tissue research restrictions > > > > > > http://www.cnn.com/2001/ALLPOLITICS/07/18/stem.cell/index.html > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 7: 0: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from technokratis.com (modemcable052.174-202-24.mtl.mc.videotron.ca [24.202.174.52]) by hub.freebsd.org (Postfix) with ESMTP id 6D7B437B401 for ; Fri, 20 Jul 2001 07:00:01 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by technokratis.com (8.11.3/8.11.3) id f6KECdM12940; Fri, 20 Jul 2001 10:12:39 -0400 (EDT) (envelope-from bmilekic) Date: Fri, 20 Jul 2001 10:12:39 -0400 From: Bosko Milekic To: vishwanath pargaonkar Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: kernel malloc Message-ID: <20010720101239.A12857@technokratis.com> References: <20010720091720.28756.qmail@web5301.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010720091720.28756.qmail@web5301.mail.yahoo.com>; from vishubp@yahoo.com on Fri, Jul 20, 2001 at 10:17:20AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jul 20, 2001 at 10:17:20AM +0100, vishwanath pargaonkar wrote: > Hi, > > can any one please help me with this. i want allocate > a memory in the kernel -a buffer of size 2k to 5k. > can i do it using malloc with second parameter as > M_TEMP and third as M_WAITOK. > > can anybody tell me what M_TEMP means .what is maximum > malloc i can do with M_TEMP? > will the OS allow me to malloc 4k buffer in side > kernel??shd i give M_WAITOK or M_DONTWAIT??? M_TEMP is merely there for statistics gathering. If you're writing a subsystem and plan to malloc() a lot of things for the subsystem you may want to create your own malloc type (see malloc(9)). On another note, remember that if you allocate a 5k buffer with malloc() on x86 where the page size if 4k, that you're not guaranteed to have a physically contiguous backing. > please tell me. > thanx in advance. Regards, -- Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 8:48: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id EC33D37B401 for ; Fri, 20 Jul 2001 08:48:03 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.134.204.Dial1.SanJose1.Level3.net [209.245.134.204]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id IAA19295; Fri, 20 Jul 2001 08:47:53 -0700 (PDT) Message-ID: <3B5852D0.AF5F3569@mindspring.com> Date: Fri, 20 Jul 2001 08:48:32 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Pentchev Cc: Louis-Philippe Gagnon , freebsd-hackers@FreeBSD.ORG Subject: Re: flock/pthread bug? References: <1fbd01c10fba$499834d0$2964a8c0@macadamian.com> <3B5690A1.8EDD0812@mindspring.com> <203501c11059$35755420$2964a8c0@macadamian.com> <20010719194735.D10583@ringworld.oblivion.bg> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Pentchev wrote: > I don't know if Terry was talking about the sched_yield() syscall, > but if he was, then sched_yield(2) exists, at least in 4.x, and is > documented as POSIX-compliant. No. He needs to yield the system CPU, not the CPU for his particular thread. In the user space threads library scheduler, you will just be yielding to another thread. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 9:18: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 5AFD637B403 for ; Fri, 20 Jul 2001 09:17:52 -0700 (PDT) (envelope-from ml@xgforce.com) Received: from fire (1Cust224.tnt1.pasadena.ca.da.uu.net [63.28.226.224]) by falcon.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id JAA12371 for ; Fri, 20 Jul 2001 09:17:51 -0700 (PDT) Message-ID: <002501c11136$ac835980$6503c23f@XGforce.com> Reply-To: "MJL" From: "MJL" To: Subject: gigabit card drivers Date: Fri, 20 Jul 2001 09:11:44 -0700 Organization: XGforce.COM X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does 4.3 version support 3com or d-link's gigabit ethernet card? ====================================== WWW.XGFORCE.COM The Next Generation Load Balance and Fail Safe Server Clustering Software for the Internet. ====================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 9:21:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gwdu60.gwdg.de (gwdu60.gwdg.de [134.76.98.60]) by hub.freebsd.org (Postfix) with ESMTP id F049C37B403 for ; Fri, 20 Jul 2001 09:21:48 -0700 (PDT) (envelope-from kheuer@gwdu60.gwdg.de) Received: from localhost (kheuer@localhost) by gwdu60.gwdg.de (8.11.3/8.9.3) with ESMTP id f6KGLkm97208; Fri, 20 Jul 2001 18:21:46 +0200 (CEST) (envelope-from kheuer@gwdu60.gwdg.de) Date: Fri, 20 Jul 2001 18:21:46 +0200 (CEST) From: Konrad Heuer To: MJL Cc: Subject: Re: gigabit card drivers In-Reply-To: <002501c11136$ac835980$6503c23f@XGforce.com> Message-ID: <20010720182034.C97191-100000@gwdu60.gwdg.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 20 Jul 2001, MJL wrote: > Does 4.3 version support 3com or d-link's gigabit > ethernet card? Yes, I've a system running perfectly with a 3Com 3c985-SX gigabit card. Regards Konrad Konrad Heuer Personal Bookmarks: Gesellschaft f=FCr wissenschaftliche Datenverarbeitung mbH G=D6ttingen http://www.freebsd.org Am Fa=DFberg, D-37077 G=D6ttingen http://www.daemonnews.o= rg Deutschland (Germany) kheuer@gwdu60.gwdg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 9:29:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 28B1A37B405 for ; Fri, 20 Jul 2001 09:29:16 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.134.204.Dial1.SanJose1.Level3.net [209.245.134.204]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA14975; Fri, 20 Jul 2001 09:29:03 -0700 (PDT) Message-ID: <3B585C76.696F1E2A@mindspring.com> Date: Fri, 20 Jul 2001 09:29:42 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: mjacob@feral.com Cc: Ian Dowse , freebsd-hackers@FreeBSD.ORG Subject: Re: Default retry behaviour for mount_nfs References: <20010719181731.O50024-100000@wonky.feral.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > So the question is - should I keep the new behaviour that is probably > > a better default and will catch out fewer new users but may surprise > > some experienced users, or should I revert to the traditional > > default where `-R1' or `-b' are required to avoid boot-time hangs? > > > > Sorry- let me be clearer: > > FWIW, I vote that we rever to the traditional default and require > -R1 or -b to avoid boot time hangs. The standard behaviour for most > NFS implementations that I'm aware of would do this. I agree; people at work have bitched about this. We have a FreeBSD NFS server that's flakey. The other thing is that it appears to break amd behaviour. (I couldn't tell which of the two questions he was voting in favor of, either, since there is one before the "or" and one after). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 9:32:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id DB55E37B401 for ; Fri, 20 Jul 2001 09:32:22 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6KGWFS83906; Fri, 20 Jul 2001 09:32:15 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Fri, 20 Jul 2001 09:32:15 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Terry Lambert Cc: Ian Dowse , freebsd-hackers@FreeBSD.ORG Subject: Re: Default retry behaviour for mount_nfs In-Reply-To: <3B585C76.696F1E2A@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Matthew Jacob wrote: > > > So the question is - should I keep the new behaviour that is probably > > > a better default and will catch out fewer new users but may surprise > > > some experienced users, or should I revert to the traditional > > > default where `-R1' or `-b' are required to avoid boot-time hangs? > > > > > > > Sorry- let me be clearer: > > > > FWIW, I vote that we rever to the traditional default and require > > -R1 or -b to avoid boot time hangs. The standard behaviour for most > > NFS implementations that I'm aware of would do this. > > I agree; people at work have bitched about this. We have a > FreeBSD NFS server that's flakey. > > The other thing is that it appears to break amd behaviour. > > (I couldn't tell which of the two questions he was voting > in favor of, either, since there is one before the "or" and > one after). That's why I submitted a followup after Ian poked me. It's funny- I tend to think of myself as being totally transparent. Why should I need to explain what I meant then? :-) -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 9:32:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by hub.freebsd.org (Postfix) with ESMTP id 526E437B40D for ; Fri, 20 Jul 2001 09:32:31 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id SAA10095 for ; Fri, 20 Jul 2001 18:32:30 +0200 (CEST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.4/8.11.4) id f6KGWTX09055 for freebsd-hackers@freebsd.org; Fri, 20 Jul 2001 18:32:29 +0200 (CEST) (envelope-from wkb) Date: Fri, 20 Jul 2001 18:32:29 +0200 From: Wilko Bulte To: freebsd-hackers@freebsd.org Subject: dual booting -stable & -current Message-ID: <20010720183229.A9022@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm probably completely dim today so please bear with me :/ Thing is I want to setup a dual-boot box, running -stable & -current. This box, a P2/266 has a 30G IDE disk. What I did is create ad0s1 -> 256MB -> holds root for -stable ad0s2 -> 256MB -> was supposed to hold root for -current ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable ad0s4 -> ditto for -current My recollection is that as long as you keep the root partitions <2 (or 8) GB it should be bootable. Hence this somewhat strange slicing. Thing is, 4.3R refuses to install it's root on ad0s2 (4.3 because I want to go current from there). I'm probably missing something obvious here? -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte "Youth is not a time in life, it is a state of mind" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 9:40:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id D133937B407 for ; Fri, 20 Jul 2001 09:40:56 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.134.204.Dial1.SanJose1.Level3.net [209.245.134.204]) by hawk.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA10070; Fri, 20 Jul 2001 09:40:25 -0700 (PDT) Message-ID: <3B585F1F.C6FCB9AC@mindspring.com> Date: Fri, 20 Jul 2001 09:41:03 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: mjacob@feral.com Cc: Gordon Tetlow , Ian Dowse , freebsd-hackers@FreeBSD.ORG Subject: Re: Default retry behaviour for mount_nfs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > Hmm, maybe we should implement the notion of "critical_local" and > > "critical_net" filesystems (a la NetBSD). Heck, I don't even need the > > distinction between net and local, just critical would do. All remote, > > critical filesystems would be blocking, and all others not. > > > > Sometimes the stick of POLA should be broken. > > Not if it adds work. I think the non-critical ones are the ones with the "-R1" option set... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 9:49:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.the-i-pa.com (mail.the-i-pa.com [151.201.71.132]) by hub.freebsd.org (Postfix) with SMTP id 649C637B407 for ; Fri, 20 Jul 2001 09:49:20 -0700 (PDT) (envelope-from wmoran@iowna.com) Received: (qmail 93130 invoked from network); 20 Jul 2001 16:59:35 -0000 Received: from unknown (HELO iowna.com) (151.201.71.193) by mail.the-i-pa.com with SMTP; 20 Jul 2001 16:59:35 -0000 Message-ID: <3B58601D.ACB852A5@iowna.com> Date: Fri, 20 Jul 2001 12:45:17 -0400 From: Bill Moran X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-hackers@FreeBSD.ORG Subject: [OT] POLA? (was Re: Default retry behaviour for mount_nfs) References: <3B585F1F.C6FCB9AC@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > Sometimes the stick of POLA should be broken. Off topic, I know, but it's going to bother me. What's POLA? -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 9:52:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 1A28B37B403 for ; Fri, 20 Jul 2001 09:52:44 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6KGqaS84248; Fri, 20 Jul 2001 09:52:36 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Fri, 20 Jul 2001 09:52:36 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Bill Moran Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: [OT] POLA? (was Re: Default retry behaviour for mount_nfs) In-Reply-To: <3B58601D.ACB852A5@iowna.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 'Principle of Least Astonishment' and something we should import from NetBSD: pilt > uname -a NetBSD pilt 1.5.1_ALPHA NetBSD 1.5.1_ALPHA (PILT) #5: Thu Feb 8 12:01:03 PST 2001 mjacob@pilt:/export/src/NetBSD-1.5/syssrc/sys/arch/i386/compile/PILT i386 pilt > /usr/games/wtf POLA POLA: principle of least astonishment pilt > /usr/games/wtf IIRC IIRC: if I recall correctly I'll leave it up to you all to imagine what 'wtf WTF' is. On Fri, 20 Jul 2001, Bill Moran wrote: > > > > > Sometimes the stick of POLA should be broken. > > Off topic, I know, but it's going to bother me. > > What's POLA? > > -Bill > > 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 Jul 20 10:13:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id A7D5437B407 for ; Fri, 20 Jul 2001 10:13:29 -0700 (PDT) (envelope-from so@server.i-clue.de) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id TAA06651; Fri, 20 Jul 2001 19:21:23 +0200 Message-ID: <3B58673F.E3BFC0F3@i-clue.de> Date: Fri, 20 Jul 2001 19:15:43 +0200 From: Christoph Sold Reply-To: so@server.i-clue.de X-Mailer: Mozilla 4.78 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Bill Moran Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: [OT] POLA? (was Re: Default retry behaviour for mount_nfs) References: <3B585F1F.C6FCB9AC@mindspring.com> <3B58601D.ACB852A5@iowna.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill Moran wrote: > > > > > Sometimes the stick of POLA should be broken. > > Off topic, I know, but it's going to bother me. > > What's POLA? Policy Of Least Astonishment -- doing changes in a way which will annoy the least number of users. HTH -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 10:26:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 8BEED37B405; Fri, 20 Jul 2001 10:26:01 -0700 (PDT) (envelope-from wiredbrain@earthlink.net) Received: from pflaump (sdn-ar-001flhhilP195.dialsprint.net [158.252.127.107]) by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id JAB24274; Fri, 20 Jul 2001 09:52:38 -0700 (PDT) Message-ID: <001301c1113d$24b4f200$6b7ffc9e@pflaump> Reply-To: "Peter Pflaum" From: "Peter Pflaum" To: Subject: Finding something useful - Among the protesters Date: Fri, 20 Jul 2001 12:52:35 -0400 Organization: GlobalVillage Schools MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_000F_01C1111A.D9C3E340" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2479.0006 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000F_01C1111A.D9C3E340 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0010_01C1111A.D9C3E340" ------=_NextPart_001_0010_01C1111A.D9C3E340 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The protest is a good example of Globalization -=20 "What is happening now hasn't happened since the anti-Vietnam war = protests of the 1960s," he told me. "Young people from around the globe = are coming together to campaign for economic justice - and our movement = is growing." BBC News BUSINESS Among the protesters She says the protests are as much about cultural as economic concerns, = and praises the "radical street warriors" for showing the world that you = cannot dehumanise people and for "reclaiming our most human desires."=20 It is important to understand the social psychological base for the = protest. These people feel left out - big means less individual feeling = of participation, of being part of the whole. A global peace corps and = person-to-person contacts to help people feel global - part of a larger = humanity. There should be ways of redirecting all this energy into = productive activity - conflict resolution - social services - projects = in the poor world building practical projects - maybe financed by the = world bank - a IMF / world bank international youth corps in health, = education, economic development would be a good start.=20 ------=_NextPart_001_0010_01C1111A.D9C3E340 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
The protest is a good example = of=20 Globalization -
"What is happening now hasn't happened = since the=20 anti-Vietnam war protests of the 1960s," he told me. "Young people from = around=20 the globe are coming together to campaign for economic justice - and our = movement is growing."

 BBC News  BUSINESS  Among the protesters
 

She says the protests are as much about cultural as economic = concerns, and=20 praises the "radical street warriors" for showing the world that you = cannot=20 dehumanise people and for "reclaiming our most human desires."

It is important to understand the social psychological base for the = protest.=20 These people feel left out - big means less individual feeling of = participation,=20 of being part of the whole. A global peace corps and person-to-person = contacts=20 to help people feel global - part of a larger humanity. There should be = ways of=20 redirecting all this energy into productive activity - conflict = resolution -=20 social services - projects in the poor world building practical projects = - maybe=20 financed by the world bank - a IMF / world bank international youth = corps in=20 health, education, economic development would be a good start.=20

------=_NextPart_001_0010_01C1111A.D9C3E340-- ------=_NextPart_000_000F_01C1111A.D9C3E340 Content-Type: application/octet-stream; name="BBC News BUSINESS Among the protesters.url" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="BBC News BUSINESS Among the protesters.url" [DEFAULT] BASEURL=3Dhttp://newsvote.bbc.co.uk/hi/english/business/newsid_939000/939= 982.stm [InternetShortcut] URL=3Dhttp://newsvote.bbc.co.uk/hi/english/business/newsid_939000/939982.= stm Modified=3DE03962103B11C10199 ------=_NextPart_000_000F_01C1111A.D9C3E340-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 10:28:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from euphoria.confusion.net (dementia.confusion.net [205.166.119.16]) by hub.freebsd.org (Postfix) with ESMTP id 4EC5437B405 for ; Fri, 20 Jul 2001 10:28:42 -0700 (PDT) (envelope-from stuyman@euphoria.confusion.net) Received: from localhost (localhost [127.0.0.1]) by euphoria.confusion.net (8.11.2/8.11.2) with SMTP id f6KHSPo03589; Fri, 20 Jul 2001 10:28:25 -0700 (PDT) Date: Fri, 20 Jul 2001 10:28:23 -0700 (PDT) From: Laurence Berland To: Matthew Jacob Cc: Bill Moran , freebsd-hackers@FreeBSD.ORG Subject: Re: [OT] POLA? (was Re: Default retry behaviour for mount_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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 20 Jul 2001, Matthew Jacob wrote: > > I'll leave it up to you all to imagine what 'wtf WTF' is. > We all know it stands for "what's that for?"... :) Laurence Berland http://www.isp.northwestern.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 11:43: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 1CCE137B405; Fri, 20 Jul 2001 11:42:54 -0700 (PDT) (envelope-from wiredbrain@earthlink.net) Received: from pflaump (sdn-ar-001flhhilP195.dialsprint.net [158.252.127.107]) by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id JAA13101; Fri, 20 Jul 2001 09:38:10 -0700 (PDT) Message-ID: <000901c1113a$db8b4f40$6b7ffc9e@pflaump> Reply-To: "Peter Pflaum" From: "Peter Pflaum" To: Subject: Pflaum on BBC News TALKING POINT Globalisation Good or bad Date: Fri, 20 Jul 2001 12:38:07 -0400 Organization: GlobalVillage Schools MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0005_01C11118.D403F140" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2479.0006 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C11118.D403F140 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0006_01C11118.D403F140" ------=_NextPart_001_0006_01C11118.D403F140 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I will be on this program Sunday at 10 - 11 AM on BBC - it is a webcast http://newsvote.bbc.co.uk/hi/english/talking_point/newsid_1444000/1444930= .stm BBC News TALKING POINT Globalisation Good or bad ------=_NextPart_001_0006_01C11118.D403F140 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I will be on this program = Sunday at 10 -=20 11 AM on BBC - it is a webcast
 
http://newsvote.bbc.co.uk/hi/english/talking_point/newsid_1= 444000/1444930.stm

 BBC=20 News  TALKING POINT  Globalisation Good or bad ------=_NextPart_001_0006_01C11118.D403F140-- ------=_NextPart_000_0005_01C11118.D403F140 Content-Type: application/octet-stream; name="BBC News TALKING POINT Globalisation Good or bad.url" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="BBC News TALKING POINT Globalisation Good or bad.url" [DEFAULT] BASEURL=3Dhttp://newsvote.bbc.co.uk/hi/english/talking_point/newsid_14440= 00/1444930.stm [InternetShortcut] URL=3Dhttp://newsvote.bbc.co.uk/hi/english/talking_point/newsid_1444000/1= 444930.stm Modified=3DE04DDDFA3911C10110 ------=_NextPart_000_0005_01C11118.D403F140-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 11:47:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.the-i-pa.com (mail.the-i-pa.com [151.201.71.132]) by hub.freebsd.org (Postfix) with SMTP id 0C15637B407 for ; Fri, 20 Jul 2001 11:47:13 -0700 (PDT) (envelope-from wmoran@iowna.com) Received: (qmail 94302 invoked from network); 20 Jul 2001 18:57:28 -0000 Received: from unknown (HELO iowna.com) (151.201.71.193) by mail.the-i-pa.com with SMTP; 20 Jul 2001 18:57:28 -0000 Message-ID: <3B587BBD.DA0E1D8A@iowna.com> Date: Fri, 20 Jul 2001 14:43:09 -0400 From: Bill Moran X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad References: <000901c1113a$db8b4f40$6b7ffc9e@pflaump> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anyone have any explanation as to why this is coming through -hackers? > Peter Pflaum wrote: > > I will be on this program Sunday at 10 - 11 AM on BBC - it is a webcast > > http://newsvote.bbc.co.uk/hi/english/talking_point/newsid_1444000/1444930.stm > > BBC News TALKING POINT Globalisation Good or bad > > Name: BBC News TALKING POINT Globalisation Good or bad.url > BBC News TALKING POINT Globalisation Good or bad.url Type: unspecified type (application/octet-stream) > Encoding: quoted-printable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 11:53: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 053BB37B401 for ; Fri, 20 Jul 2001 11:53:02 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6KIqxS88998; Fri, 20 Jul 2001 11:52:59 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Fri, 20 Jul 2001 11:52:59 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Bill Moran Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad In-Reply-To: <3B587BBD.DA0E1D8A@iowna.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG No. Peter Pflaum responded when I asked him with a "Quoi???????!?!?!?!".... On Fri, 20 Jul 2001, Bill Moran wrote: > Does anyone have any explanation as to why this is coming through -hackers? > > > Peter Pflaum wrote: > > > > I will be on this program Sunday at 10 - 11 AM on BBC - it is a webcast > > > > http://newsvote.bbc.co.uk/hi/english/talking_point/newsid_1444000/1444930.stm > > > > BBC News TALKING POINT Globalisation Good or bad > > > > Name: BBC News TALKING POINT Globalisation Good or bad.url > > BBC News TALKING POINT Globalisation Good or bad.url Type: unspecified type (application/octet-stream) > > Encoding: quoted-printable > > 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 Jul 20 11:54:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.the-i-pa.com (mail.the-i-pa.com [151.201.71.132]) by hub.freebsd.org (Postfix) with SMTP id 4261237B407 for ; Fri, 20 Jul 2001 11:54:24 -0700 (PDT) (envelope-from wmoran@iowna.com) Received: (qmail 94390 invoked from network); 20 Jul 2001 19:04:39 -0000 Received: from unknown (HELO iowna.com) (151.201.71.193) by mail.the-i-pa.com with SMTP; 20 Jul 2001 19:04:39 -0000 Message-ID: <3B587D6C.80AC252D@iowna.com> Date: Fri, 20 Jul 2001 14:50:20 -0400 From: Bill Moran X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mjacob@feral.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Are you saying that he didn't even send them? Matthew Jacob wrote: > > No. Peter Pflaum responded when I asked him with a "Quoi???????!?!?!?!".... > > On Fri, 20 Jul 2001, Bill Moran wrote: > > > Does anyone have any explanation as to why this is coming through -hackers? > > > > > Peter Pflaum wrote: > > > > > > I will be on this program Sunday at 10 - 11 AM on BBC - it is a webcast > > > > > > http://newsvote.bbc.co.uk/hi/english/talking_point/newsid_1444000/1444930.stm > > > > > > BBC News TALKING POINT Globalisation Good or bad > > > > > > Name: BBC News TALKING POINT Globalisation Good or bad.url > > > BBC News TALKING POINT Globalisation Good or bad.url Type: unspecified type (application/octet-stream) > > > Encoding: quoted-printable > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 11:54:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id E943C37B401 for ; Fri, 20 Jul 2001 11:54:52 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6KIsoS89083; Fri, 20 Jul 2001 11:54:50 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Fri, 20 Jul 2001 11:54:50 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Bill Moran Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad In-Reply-To: <3B587D6C.80AC252D@iowna.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG He's saying "Huh?" and presumably 'looking into it'. On Fri, 20 Jul 2001, Bill Moran wrote: > Are you saying that he didn't even send them? > > Matthew Jacob wrote: > > > > No. Peter Pflaum responded when I asked him with a "Quoi???????!?!?!?!".... > > > > On Fri, 20 Jul 2001, Bill Moran wrote: > > > > > Does anyone have any explanation as to why this is coming through -hackers? > > > > > > > Peter Pflaum wrote: > > > > > > > > I will be on this program Sunday at 10 - 11 AM on BBC - it is a webcast > > > > > > > > http://newsvote.bbc.co.uk/hi/english/talking_point/newsid_1444000/1444930.stm > > > > > > > > BBC News TALKING POINT Globalisation Good or bad > > > > > > > > Name: BBC News TALKING POINT Globalisation Good or bad.url > > > > BBC News TALKING POINT Globalisation Good or bad.url Type: unspecified type (application/octet-stream) > > > > Encoding: quoted-printable > > > > > > 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 > > 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 Jul 20 11:55:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 540FB37B409 for ; Fri, 20 Jul 2001 11:55:22 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6KItKS89100; Fri, 20 Jul 2001 11:55:20 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Fri, 20 Jul 2001 11:55:20 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Bill Moran Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad In-Reply-To: <3B587D6C.80AC252D@iowna.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG My guess, fwiw, is that somebody subscribed freebsd-hackers to some eGroup toy and this is why this is happening. Joy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 11:58:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.the-i-pa.com (mail.the-i-pa.com [151.201.71.132]) by hub.freebsd.org (Postfix) with SMTP id B8B9037B401 for ; Fri, 20 Jul 2001 11:58:14 -0700 (PDT) (envelope-from wmoran@iowna.com) Received: (qmail 94461 invoked from network); 20 Jul 2001 19:08:30 -0000 Received: from unknown (HELO iowna.com) (151.201.71.193) by mail.the-i-pa.com with SMTP; 20 Jul 2001 19:08:30 -0000 Message-ID: <3B587E53.E6AFFC7C@iowna.com> Date: Fri, 20 Jul 2001 14:54:11 -0400 From: Bill Moran X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mjacob@feral.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > My guess, fwiw, is that somebody subscribed freebsd-hackers to some eGroup toy > and this is why this is happening. Joy. I don't know. If it's coming from some eGroup, why is it originating at what looks like a dialup address, and running through Earthling? Looks like SPAM to me. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 11:59:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 4F6C637B408; Fri, 20 Jul 2001 11:59:17 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f6KIxHV13195; Fri, 20 Jul 2001 11:59:17 -0700 Date: Fri, 20 Jul 2001 11:59:17 -0700 From: Brooks Davis To: net@freebsd.org, hackers@freebsd.org Subject: interface cloning MFC Message-ID: <20010720115917.A12408@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I plan to MFC the network interface cloning support and the gif modularization early next week unless someone has objections. I'd like to get it in before the code slush and since I'll be leaving for a week on the 31st, that means sometime early to mid next week to allow for any bug reports. I don't really expect any problems. A diff is available at: http://people.freebsd.org/~brooks/patches/gif-stable.diff apply with: cd /usr/src mkdir sys/modules/if_gif sys/modules/if_stf patch < gif-stable.diff -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7WH+EXY6L6fI4GtQRAshQAKDOlk6+HByY2Uq2P0vHFEU9EooHGQCgzWBo t7BFPcqq68lqe2XXGW/j51g= =FQ+o -----END PGP SIGNATURE----- --huq684BweRXVnRxX-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 12: 9:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.oskarmobil.cz (smtp1.oskarmobil.cz [217.77.161.133]) by hub.freebsd.org (Postfix) with ESMTP id E140537B401; Fri, 20 Jul 2001 12:09:03 -0700 (PDT) (envelope-from Milon.Papezik@oskarmobil.cz) Received: from wh01ex01.ceskymobil.cz (wh01ex01.ceskymobil.cz [172.20.116.17]) by smtp1.oskarmobil.cz (8.11.2/8.11.1) with ESMTP id f6KJ8ju02796; Fri, 20 Jul 2001 21:08:45 +0200 (CEST) (envelope-from Milon.Papezik@oskarmobil.cz) Received: by wh01ex01.ceskymobil.cz with Internet Mail Service (5.5.2653.19) id <39DWST4T>; Fri, 20 Jul 2001 21:07:00 +0200 Message-ID: From: Milon Papezik To: "'hardware@freebsd.org'" , "'hackers@freebsd.org'" Cc: "'Jeff Sapp'" , "'jlemon@freebsd.org'" Subject: RE: Compaq DL380 Date: Fri, 20 Jul 2001 21:07:00 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-2" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, I need to MFC changes in ida driver, which start backround firmware processing on Integrated SmartArray controllers (this allows automatic on-line rebuild of failed drives). I am going to do it in next few days. I understood that I shall avoid all changes for interrupt-entropy harvesting. Is there something more I shall avoid ? Thanks in advance, Milon -- milon.papezik@oskarmobil.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 12:20:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 2996337B401; Fri, 20 Jul 2001 12:20:48 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f6KJKOs57891; Fri, 20 Jul 2001 14:20:24 -0500 (CDT) (envelope-from jlemon) Date: Fri, 20 Jul 2001 14:20:24 -0500 From: Jonathan Lemon To: Milon Papezik Cc: "'hardware@freebsd.org'" , "'hackers@freebsd.org'" , "'Jeff Sapp'" , "'jlemon@freebsd.org'" Subject: Re: Compaq DL380 Message-ID: <20010720142024.X74461@prism.flugsvamp.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jul 20, 2001 at 09:07:00PM +0200, Milon Papezik wrote: > Hi all, > > I need to MFC changes in ida driver, which start backround > firmware processing on Integrated SmartArray controllers > (this allows automatic on-line rebuild of failed drives). > > I am going to do it in next few days. I understood that I shall > avoid all changes for interrupt-entropy harvesting. > > Is there something more I shall avoid ? No, other than the buf/bio changes make the diffs harder to read. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 12:33:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (d211.dhcp212-26.cybercable.fr [212.198.26.211]) by hub.freebsd.org (Postfix) with ESMTP id 8D84737B401 for ; Fri, 20 Jul 2001 12:33:32 -0700 (PDT) (envelope-from thierry@herbelot.com) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id VAA06880; Fri, 20 Jul 2001 21:31:37 +0200 (CEST) (envelope-from thierry@herbelot.com) Message-ID: <3B588760.E5875DBB@herbelot.com> Date: Fri, 20 Jul 2001 21:32:48 +0200 From: Thierry Herbelot X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Wilko Bulte Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: dual booting -stable & -current References: <20010720183229.A9022@freebie.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > I'm probably completely dim today so please bear with me :/ > Thing is I want to setup a dual-boot box, running -stable & -current. > This box, a P2/266 has a 30G IDE disk. > > What I did is create > ad0s1 -> 256MB -> holds root for -stable > ad0s2 -> 256MB -> was supposed to hold root for -current > ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable > ad0s4 -> ditto for -current > > My recollection is that as long as you keep the root partitions <2 (or 8) GB > it should be bootable. Hence this somewhat strange slicing. > > Thing is, 4.3R refuses to install it's root on ad0s2 (4.3 because I want > to go current from there). > > I'm probably missing something obvious here? here's what I have on my (just -Stable for the moment) workstation : multi# fdisk ad4 ******* Working on device /dev/ad4 ******* parameters extracted from in-core disklabel are: cylinders=35390 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 2457441 (1199 Meg), flag 0 The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 4095504, size 31577616 (15418 Meg), flag 0 he data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 2457504, size 1638000 (799 Meg), flag 80 (active) The data for partition 4 is: // main bootable partition multi# disklabel -r ad4s1 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 102400 0 4.2BSD 1024 8192 16 on / b: 860160 102400 swap shared swap c: 2457441 0 unused 0 0 e: 40960 962560 4.2BSD 1024 8192 16 on /var f: 1453921 1003520 4.2BSD 1024 8192 16 on /usr // alternate bootable partition (will be -Current) multi# disklabel -r ad4s3 # size offset fstype [fsize bsize bps/cpg] a: 102400 0 4.2BSD 1024 8192 16 on alternate / c: 1638000 0 unused 0 0 e: 40960 102400 4.2BSD 1024 8192 16 alt. /var f: 1494640 143360 4.2BSD 1024 8192 16 alt. /usr multi# disklabel -r ad4s2 # size offset fstype [fsize bsize bps/cpg] c: 31577616 0 unused 0 0 e: 31577616 0 4.2BSD 0 0 0 shared expanse you may want to use a similar setup (with larger bootable partitions : my setup was initially one only 2G partition, but I cut it this way, with a shared swap to be able to dual-boot) PS : I also had problems with a 40G disk on my oldish P-II/266 : it would not boot from the large disk (I just added a spare 8G which I boot from) -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 12:38: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 9D80A37B407; Fri, 20 Jul 2001 12:37:53 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.4/8.11.4) with ESMTP id f6KJbpl26743; Fri, 20 Jul 2001 20:37:51 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f6KJbog13481; Fri, 20 Jul 2001 20:37:50 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200107201937.f6KJbog13481@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Brooks Davis Cc: net@FreeBSD.ORG, hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: interface cloning MFC In-Reply-To: Message from Brooks Davis of "Fri, 20 Jul 2001 11:59:17 PDT." <20010720115917.A12408@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Jul 2001 20:37:50 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I plan to MFC the network interface cloning support and the gif > modularization early next week unless someone has objections. I'd like > to get it in before the code slush and since I'll be leaving for a week > on the 31st, that means sometime early to mid next week to allow for any > bug reports. I don't really expect any problems. Good stuff. > A diff is available at: > > http://people.freebsd.org/~brooks/patches/gif-stable.diff You forgot: Index: LINT =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/Attic/LINT,v retrieving revision 1.749.2.64 diff -u -r1.749.2.64 LINT --- LINT 2001/06/29 21:14:24 1.749.2.64 +++ LINT 2001/07/20 19:35:42 @@ -509,7 +509,7 @@ options ETHER_SNAP # enable Ethernet_802.2/SNAP frame # for IPv6 -pseudo-device gif 4 #IPv6 and IPv4 tunneling +pseudo-device gif #IPv6 and IPv4 tunneling pseudo-device faith 1 #for IPv6 and IPv4 translation pseudo-device stf #6to4 IPv6 over IPv4 encapsulation I'm just rebuilding the world now :) I'll let you know how I get on. Thanks for your work. -- Brian http://www.freebsd-services.com/ 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 Jul 20 12:52: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 8C38737B405; Fri, 20 Jul 2001 12:52:03 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f6KJpq619635; Fri, 20 Jul 2001 12:51:52 -0700 Date: Fri, 20 Jul 2001 12:51:52 -0700 From: Brooks Davis To: Brian Somers Cc: net@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: interface cloning MFC Message-ID: <20010720125152.A18620@Odin.AC.HMC.Edu> References: <200107201937.f6KJbog13481@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107201937.f6KJbog13481@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Fri, Jul 20, 2001 at 08:37:50PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ibTvN161/egqYuK8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 20, 2001 at 08:37:50PM +0100, Brian Somers wrote: > > A diff is available at: > >=20 > > http://people.freebsd.org/~brooks/patches/gif-stable.diff >=20 > You forgot: >=20 > Index: LINT > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/sys/i386/conf/Attic/LINT,v > retrieving revision 1.749.2.64 > diff -u -r1.749.2.64 LINT > --- LINT 2001/06/29 21:14:24 1.749.2.64 > +++ LINT 2001/07/20 19:35:42 > @@ -509,7 +509,7 @@ > options ETHER_SNAP # enable Ethernet_802.2/SNAP frame > =20 > # for IPv6 > -pseudo-device gif 4 #IPv6 and IPv4 tunneling > +pseudo-device gif #IPv6 and IPv4 tunneling > pseudo-device faith 1 #for IPv6 and IPv4 translation > pseudo-device stf #6to4 IPv6 over IPv4 encapsulation Oops, I've updated the diff. I'll be committing the appropriate fix to NOTES shortly, since I forgot that in the first round. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --ibTvN161/egqYuK8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7WIvXXY6L6fI4GtQRAqsVAKCejQ+LbtXD0n3nzwIWpzG+zkTeHACgkdLz i1YyLERB2qCNxYuy5HJSKKg= =rl2p -----END PGP SIGNATURE----- --ibTvN161/egqYuK8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 14:24:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id ED6FE37B401 for ; Fri, 20 Jul 2001 14:24:13 -0700 (PDT) (envelope-from conrad@apple.com) Received: from apple.com (A17-129-100-225.apple.com [17.129.100.225]) by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id OAA13113 for ; Fri, 20 Jul 2001 14:24:13 -0700 (PDT) Received: from scv3.apple.com (scv3.apple.com) by apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id for ; Fri, 20 Jul 2001 14:24:13 -0700 Received: from [17.202.43.185] (wa.apple.com [17.202.43.185]) by scv3.apple.com (8.9.3/8.9.3) with ESMTP id OAA23516 for ; Fri, 20 Jul 2001 14:24:12 -0700 (PDT) X-Sender: conrad@mail.apple.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 20 Jul 2001 14:24:01 -0700 To: freebsd-hackers@freebsd.org From: Conrad Minshall Subject: NETBIOS Browsing? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anyone know of any code which would help in browsing a Windows "Network Neighbourhood"? Something which would make broadcasts to find all the netbios name servers, and then query them to discover more. Code from Samba's "nmblookup" would be fine but it is GPL. -- Conrad Minshall ... conrad@apple.com ... 408 974-2749 Alternative email addresses: rad@acm.org and conrad@mac.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 14:43:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id EF02137B406 for ; Fri, 20 Jul 2001 14:43:21 -0700 (PDT) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id XAA07390; Fri, 20 Jul 2001 23:43:20 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f6KLi0O28534; Fri, 20 Jul 2001 23:44:00 +0200 (CEST) (envelope-from alex) Date: Fri, 20 Jul 2001 23:44:00 +0200 From: Alexander Langer To: Conrad Minshall Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NETBIOS Browsing? Message-ID: <20010720234400.B28408@fump.kawo2.rwth-aachen.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from conrad@apple.com on Fri, Jul 20, 2001 at 02:24:01PM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Conrad Minshall (conrad@apple.com): > Does anyone know of any code which would help in browsing a Windows > "Network Neighbourhood"? Something which would make broadcasts to find all > the netbios name servers, and then query them to discover more. Code from > Samba's "nmblookup" would be fine but it is GPL. xsmbrowser is a GREAT tools, which is even better than Microsofts Network Neighbourhood. I use it to browser our LAN with 200+ PCs and it's very comfortable (and has less bugs than M$' crap) You can find it in the ports collection. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 14:45: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 994A737B41C for ; Fri, 20 Jul 2001 14:44:54 -0700 (PDT) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id XAA07461; Fri, 20 Jul 2001 23:44:53 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f6KLjX428573; Fri, 20 Jul 2001 23:45:33 +0200 (CEST) (envelope-from alex) Date: Fri, 20 Jul 2001 23:45:32 +0200 From: Alexander Langer To: Conrad Minshall Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NETBIOS Browsing? Message-ID: <20010720234532.A28557@fump.kawo2.rwth-aachen.de> References: <20010720234400.B28408@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010720234400.B28408@fump.kawo2.rwth-aachen.de>; from alex@big.endian.de on Fri, Jul 20, 2001 at 11:44:00PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ouch, I should actually read more carefully what you were asking, sorry. I guess smbfs doesn't help you here (don't know if it actually browses, but at least it's SMB stuff) Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 14:52:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by hub.freebsd.org (Postfix) with ESMTP id ACDD037B401 for ; Fri, 20 Jul 2001 14:52:26 -0700 (PDT) (envelope-from conrad@apple.com) Received: from apple.com (A17-129-100-225.apple.com [17.129.100.225]) by mail-out2.apple.com (8.9.3/8.9.3) with ESMTP id OAA08890 for ; Fri, 20 Jul 2001 14:52:26 -0700 (PDT) Received: from scv2.apple.com (scv2.apple.com) by apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Fri, 20 Jul 2001 14:52:18 -0700 Received: from [17.202.43.185] (wa.apple.com [17.202.43.185]) by scv2.apple.com (8.11.3/8.11.3) with ESMTP id f6KLqHw29739; Fri, 20 Jul 2001 14:52:17 -0700 (PDT) X-Sender: conrad@mail.apple.com Message-Id: In-Reply-To: <20010720234400.B28408@fump.kawo2.rwth-aachen.de> References: ; from conrad@apple.com on Fri, Jul 20, 2001 at 02:24:01PM -0700 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 20 Jul 2001 14:51:50 -0700 To: Alexander Langer From: Conrad Minshall Subject: Re: NETBIOS Browsing? Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 2:44 PM -0700 7/20/01, Alexander Langer wrote: >> Does anyone know of any code which would help in browsing a Windows >> "Network Neighbourhood"? Something which would make broadcasts to find all >> the netbios name servers, and then query them to discover more. Code from >> Samba's "nmblookup" would be fine but it is GPL. > >xsmbrowser is a GREAT tools, which is even better than Microsofts >Network Neighbourhood. I use it to browser our LAN with 200+ PCs >and it's very comfortable (and has less bugs than M$' crap) Thank you. I should have mentioned"xsmbrowser". Unfortunately it is GPL and uses Samba (also GPL). ...bcc to the author of xsmbrowser -- Conrad Minshall ... conrad@apple.com ... 408 974-2749 Alternative email addresses: rad@acm.org and conrad@mac.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 14:56:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by hub.freebsd.org (Postfix) with ESMTP id 6632837B406 for ; Fri, 20 Jul 2001 14:56:08 -0700 (PDT) (envelope-from conrad@apple.com) Received: from apple.con (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.9.3/8.9.3) with ESMTP id OAA09439 for ; Fri, 20 Jul 2001 14:56:07 -0700 (PDT) Received: from scv3.apple.com (scv3.apple.com) by apple.con (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Fri, 20 Jul 2001 14:54:21 +0100 Received: from [17.202.43.185] (wa.apple.com [17.202.43.185]) by scv3.apple.com (8.9.3/8.9.3) with ESMTP id OAA02095; Fri, 20 Jul 2001 14:56:05 -0700 (PDT) X-Sender: conrad@mail.apple.com Message-Id: In-Reply-To: <20010720234532.A28557@fump.kawo2.rwth-aachen.de> References: <20010720234400.B28408@fump.kawo2.rwth-aachen.de>; from alex@big.endian.de on Fri, Jul 20, 2001 at 11:44:00PM +0200 <20010720234400.B28408@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 20 Jul 2001 14:55:42 -0700 To: Alexander Langer From: Conrad Minshall Subject: Re: NETBIOS Browsing? Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 2:45 PM -0700 7/20/01, Alexander Langer wrote: >Ouch, I should actually read more carefully what you were asking, >sorry. > >I guess smbfs doesn't help you here (don't know if it actually >browses, but at least it's SMB stuff) Extending smbfs with browsing is exactly what I wish to do. -- Conrad Minshall ... conrad@apple.com ... 408 974-2749 Alternative email addresses: rad@acm.org and conrad@mac.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 15: 0:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id CA2D337B401 for ; Fri, 20 Jul 2001 15:00:10 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id RAA46608; Fri, 20 Jul 2001 17:58:19 -0400 (EDT) Date: Fri, 20 Jul 2001 17:58:18 -0400 (EDT) From: "Matthew N. Dodd" To: Julian Elischer Cc: Max Khon , freebsd-hackers@FreeBSD.ORG Subject: Re: arcnet support for FreeBSD (request for review) In-Reply-To: <3B568581.5A798B3E@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 19 Jul 2001, Julian Elischer wrote: > probably no committers had arcnet or could test it.. I have it and tried to test it last time with no success. I'll try and find some time to look at this stuff. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 15:28: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 80F4037B406 for ; Fri, 20 Jul 2001 15:27:50 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 20 Jul 2001 23:27:49 +0100 (BST) To: tlambert2@mindspring.com Cc: mjacob@feral.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Default retry behaviour for mount_nfs In-Reply-To: Your message of "Fri, 20 Jul 2001 09:29:42 PDT." <3B585C76.696F1E2A@mindspring.com> Date: Fri, 20 Jul 2001 23:27:47 +0100 From: Ian Dowse Message-ID: <200107202327.aa64363@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3B585C76.696F1E2A@mindspring.com>, Terry Lambert writes: >> FWIW, I vote that we rever to the traditional default and require >> -R1 or -b to avoid boot time hangs. The standard behaviour for most >> NFS implementations that I'm aware of would do this. > >I agree; people at work have bitched about this. We have a >FreeBSD NFS server that's flakey. Ok, from the small set of responses so far, it seems that the most acceptable option is to change mount_nfs to behave in the old way where it will retry forever by default even in foreground mode. Below is a proposed patch that does this. It also adds two paragraphs near the start of the manpage which describe the default behaviour and point readers at the relevant options. Comments welcome. >The other thing is that it appears to break amd behaviour. Does amd use mount_nfs(8)? I thought it did the mount syscalls directly. Ian Index: mount_nfs.8 =================================================================== RCS file: /dump/FreeBSD-CVS/src/sbin/mount_nfs/mount_nfs.8,v retrieving revision 1.27 diff -u -r1.27 mount_nfs.8 --- mount_nfs.8 2001/07/19 21:11:48 1.27 +++ mount_nfs.8 2001/07/20 22:20:35 @@ -71,6 +71,28 @@ .%T "NFS: Network File System Version 3 Protocol Specification" , Appendix I. .Pp +By default, +.Nm +keeps retrying until the mount eventually succeeds. +This behaviour is intended for filesystems listed in +.Xr fstab 5 +that are critical to the boot process. +For non-critical filesystems, the +.Fl R +and +.Fl b +flags provide mechanisms to prevent the boot process from hanging +if the server is unavailable. +.Pp +If the server becomes unresponsive while an NFS filesystem is +mounted, any new or outstanding file operations on that filesystem +will hang uninterruptibly until the server comes back. +To modify this default behaviour, see the +.Fl i +and +.Fl s +flags. +.Pp The options are: .Bl -tag -width indent .It Fl 2 @@ -126,12 +148,8 @@ help, but for normal desktop clients this does not apply.) .It Fl R Set the mount retry count to the specified value. -A retry count of zero means to keep retrying forever. -By default, -.Nm -retries forever on background mounts (see the -.Fl b -option), and otherwise tries just once. +The default is a retry count of zero, which means to keep retrying +forever. There is a 60 second delay between each attempt. .It Fl T Use TCP transport instead of UDP. Index: mount_nfs.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/sbin/mount_nfs/mount_nfs.c,v retrieving revision 1.45 diff -u -r1.45 mount_nfs.c --- mount_nfs.c 2001/07/19 21:11:48 1.45 +++ mount_nfs.c 2001/07/20 21:37:19 @@ -486,7 +486,8 @@ name = *argv; if (retrycnt == -1) - retrycnt = (opflags & BGRND) ? 0 : 1; + /* The default is to keep retrying forever. */ + retrycnt = 0; if (!getnfsargs(spec, nfsargsp)) exit(1); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 16: 3:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cokane.org (ip-216-23-49-49.adsl.one.net [216.23.49.49]) by hub.freebsd.org (Postfix) with ESMTP id F1D0237B401 for ; Fri, 20 Jul 2001 16:03:29 -0700 (PDT) (envelope-from cokane@cokane.org) Received: (from cokane@localhost) by cokane.org (8.11.4/8.11.4) id f6LB6XT77378; Sat, 21 Jul 2001 07:06:33 -0400 (EDT) (envelope-from cokane) Date: Sat, 21 Jul 2001 07:06:31 -0400 From: Coleman Kane To: Farooq Mela Cc: hackers@FreeBSD.ORG Subject: Re: Status of agpgart device Message-ID: <20010721070631.A72108@evil.apt> References: <3B5771B0.D5575CAC@sm.socccd.cc.ca.us> <20010720142738.A456@evil.apt> <3B57EB1B.632B6EF0@sm.socccd.cc.ca.us> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B57EB1B.632B6EF0@sm.socccd.cc.ca.us>; from fmela0@sm.socccd.cc.ca.us on Fri, Jul 20, 2001 at 01:26:03AM -0700 X-VIM-Settings: vim:ts=4:sw=4:tw=70: X-Operating-System: FreeBSD evil.apt 5.0-CURRENT FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable For the i440BX, it should be fully operational and work just exactly like the linux counterpart. You shouldn't need the agpgart tarball, it sohuld=20 work (but only in XFree86 3.3.6). XFree86 4.x uses DRI exclusively. If you want to use that, you should visit dri.sourceforge.net. On Fri, Jul 20, 2001 at 01:26:03AM -0700, Farooq Mela wrote, and it was pro= claimed: > Hi, >=20 > Right, I've already got that: >=20 > agp0: mem > 0xf8000000-0xfbffffff at device 0.0 on pci0 >=20 > That still doesnt answer my question about the agpgart (AGP > g-something address resolution table, or something similar - needed > for high-performance memory transfers). >=20 > -- Coleman Kane wrote: > >=20 > > 4.3-RELEASE comes with an agp device. Simply add agp_load=3D"YES" to yo= ur > > /boot/loader.conf file, or device agp to your kernel config file. It > > only supports certain AGP bridges though, look in /usr/src/sys/pci/agp* > > for more info. > >=20 > > On Thu, Jul 19, 2001 at 04:48:00PM -0700, Farooq Mela wrote, and it was= proclaimed: > > > Hi hackers@, > > > > > > What is the status of the /dev/agpgart device? (I'm running 4.3-STABLE > > > with a recent cvsup). Is it working, perhaps using a compatible > > > interface with the linux device the of the same name (I can dream > > > can't I ;-) ? I ask because I recently tried compiling Utah-GLX with > > > AGP acceleration support, and it requires a /dev/agpgart device, but > > > the testgart program errors out when it tries to ioctl the agpgart > > > device. > > > > > > The Utah-GLX website all provides a tarball > > > (http://utah-glx.sourceforge.net/gart/agpgart-freebsd-20000619.tar.gz) > > > which includes a FreeBSD agpgart driver (as a KLD), but it fails to > > > compile. I believe it was for the FreeBSD 3.x series, and has tons of > > > compile errors. The documentation for the driver also states the as > > > part of the installation, a /dev/agpgart must be built, yet I already > > > had a /dev/agpgart device. This leads me to believe this driver is a > > > bit antiquated. > > > > > > Any ideas? > > > > > > -- > > > farooq > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > >=20 > > ---------------------------------------------------------------------- > > Part 1.2Type: application/pgp-signature >=20 > farooq >=20 --KsGdsel6WgEHnImy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7WWI3ERViMObJ880RAsoPAJ9hBH+QLEh4RDaWjnng4w/q+qCHQwCg3grG uA5VMZZ2ROmegEOJCv9Teno= =Xfuc -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 16:13:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp7.xs4all.nl (smtp7.xs4all.nl [194.109.127.133]) by hub.freebsd.org (Postfix) with ESMTP id E25B537B405 for ; Fri, 20 Jul 2001 16:13:10 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp7.xs4all.nl (8.9.3/8.9.3) with ESMTP id BAA27572; Sat, 21 Jul 2001 01:13:05 +0200 (CEST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.4/8.11.4) id f6KND3E12151; Sat, 21 Jul 2001 01:13:03 +0200 (CEST) (envelope-from wkb) Date: Sat, 21 Jul 2001 01:13:03 +0200 From: Wilko Bulte To: Thierry Herbelot Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: dual booting -stable & -current Message-ID: <20010721011303.A12137@freebie.xs4all.nl> References: <20010720183229.A9022@freebie.xs4all.nl> <3B588760.E5875DBB@herbelot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B588760.E5875DBB@herbelot.com>; from thierry@herbelot.com on Fri, Jul 20, 2001 at 09:32:48PM +0200 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jul 20, 2001 at 09:32:48PM +0200, Thierry Herbelot wrote: > Wilko Bulte wrote: > > > > I'm probably completely dim today so please bear with me :/ > > Thing is I want to setup a dual-boot box, running -stable & -current. > > This box, a P2/266 has a 30G IDE disk. > > > > What I did is create > > ad0s1 -> 256MB -> holds root for -stable > > ad0s2 -> 256MB -> was supposed to hold root for -current > > ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable > > ad0s4 -> ditto for -current > > > > My recollection is that as long as you keep the root partitions <2 (or 8) GB > > it should be bootable. Hence this somewhat strange slicing. > > > > Thing is, 4.3R refuses to install it's root on ad0s2 (4.3 because I want > > to go current from there). > > > > I'm probably missing something obvious here? > > here's what I have on my (just -Stable for the moment) workstation : > multi# fdisk ad4 > ******* Working on device /dev/ad4 ******* > parameters extracted from in-core disklabel are: > cylinders=35390 heads=16 sectors/track=63 (1008 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: ... > you may want to use a similar setup (with larger bootable partitions : > my setup was initially one only 2G partition, but I cut it this way, > with a shared swap to be able to dual-boot) But does your system boot from the 'second' FreeBSD installation? > PS : I also had problems with a 40G disk on my oldish P-II/266 : it > would not boot from the large disk (I just added a spare 8G which I boot > from) Hmmm. Wilko [who remembers why all his other systems are SCSI.. ] -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte "Youth is not a time in life, it is a state of mind" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 16:29:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 884B637B401; Fri, 20 Jul 2001 16:29:16 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.4/8.11.4) with ESMTP id f6KNTDL00732; Sat, 21 Jul 2001 00:29:14 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f6KNTDg17187; Sat, 21 Jul 2001 00:29:13 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200107202329.f6KNTDg17187@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Brooks Davis Cc: net@FreeBSD.ORG, hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: interface cloning MFC In-Reply-To: Message from Brooks Davis of "Fri, 20 Jul 2001 11:59:17 PDT." <20010720115917.A12408@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Jul 2001 00:29:13 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I plan to MFC the network interface cloning support and the gif > modularization early next week unless someone has objections. I'd like > to get it in before the code slush and since I'll be leaving for a week > on the 31st, that means sometime early to mid next week to allow for any > bug reports. I don't really expect any problems. > > A diff is available at: > > http://people.freebsd.org/~brooks/patches/gif-stable.diff > > apply with: > > cd /usr/src > mkdir sys/modules/if_gif sys/modules/if_stf > patch < gif-stable.diff > > -- Brooks This works nicely on my -stale box. Thanks. One niggle though :) It's probably worth changing ``$FreeBSD: ........$'' to ``$FreeBSD$'' in your patched version. Without this, mergemaster assumes that the new version in /usr/src/etc is the same as the /etc version (same Ids). This caused a problem here, I fixed the problem and went to prepare a patch for you.... the patch file came up empty -- you already had the missing ``create'' in your patches (of course) :*D Cheers. -- Brian http://www.freebsd-services.com/ 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 Jul 20 16:35:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 4AF5437B405; Fri, 20 Jul 2001 16:35:32 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f6KNZTH17835; Fri, 20 Jul 2001 16:35:29 -0700 Date: Fri, 20 Jul 2001 16:35:29 -0700 From: Brooks Davis To: Brian Somers Cc: net@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: interface cloning MFC Message-ID: <20010720163529.A16952@Odin.AC.HMC.Edu> References: <200107202329.f6KNTDg17187@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107202329.f6KNTDg17187@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Sat, Jul 21, 2001 at 12:29:13AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 21, 2001 at 12:29:13AM +0100, Brian Somers wrote: > This works nicely on my -stale box. Thanks. >=20 > One niggle though :) It's probably worth changing=20 > ``$FreeBSD: ........$'' to ``$FreeBSD$'' in your patched version. =20 > Without this, mergemaster assumes that the new version in /usr/src/etc=20 > is the same as the /etc version (same Ids). This caused a problem=20 > here, I fixed the problem and went to prepare a patch for you.... the=20 > patch file came up empty -- you already had the missing ``create'' in=20 > your patches (of course) :*D I've updated the patch again. I'd run into that problem but didn't think to just unexpand the $FreeBSD$ and then promptly forgot about it. Thanks, Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --fUYQa+Pmc3FrFX/N Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7WMBAXY6L6fI4GtQRArnqAKDPTEYpw1WAqplg9RkswXuCEzm/MgCg3FEo Bc8amOhnFtHbb7FSrSujYiM= =OVqW -----END PGP SIGNATURE----- --fUYQa+Pmc3FrFX/N-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 17:26: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (cust-P5-R6-162.POOL.ESR.SJO.wwc.com [206.112.109.162]) by hub.freebsd.org (Postfix) with ESMTP id 23DF937B405; Fri, 20 Jul 2001 17:26:04 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f6L0QId01552; Fri, 20 Jul 2001 17:26:20 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200107210026.f6L0QId01552@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Milon Papezik Cc: "'hardware@freebsd.org'" , "'hackers@freebsd.org'" , "'Jeff Sapp'" , "'jlemon@freebsd.org'" Subject: Re: Compaq DL380 In-reply-to: Your message of "Fri, 20 Jul 2001 21:07:00 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Jul 2001 17:26:18 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This sounds great; nothing else I can think of. Compaq are happy about this. 8) > I need to MFC changes in ida driver, which start backround > firmware processing on Integrated SmartArray controllers > (this allows automatic on-line rebuild of failed drives). > > I am going to do it in next few days. I understood that I shall > avoid all changes for interrupt-entropy harvesting. > > Is there something more I shall avoid ? > > Thanks in advance, > Milon > -- > milon.papezik@oskarmobil.cz > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 17:27:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (cust-P5-R6-162.POOL.ESR.SJO.wwc.com [206.112.109.162]) by hub.freebsd.org (Postfix) with ESMTP id 4E48537B401; Fri, 20 Jul 2001 17:27:30 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f6L0Rld01571; Fri, 20 Jul 2001 17:27:48 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200107210027.f6L0Rld01571@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jonathan Lemon Cc: Milon Papezik , "'hardware@freebsd.org'" , "'hackers@freebsd.org'" , "'Jeff Sapp'" , "'jlemon@freebsd.org'" Subject: Re: Compaq DL380 In-reply-to: Your message of "Fri, 20 Jul 2001 14:20:24 CDT." <20010720142024.X74461@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Jul 2001 17:27:47 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > I need to MFC changes in ida driver, which start backround > > firmware processing on Integrated SmartArray controllers > > (this allows automatic on-line rebuild of failed drives). > > > > I am going to do it in next few days. I understood that I shall > > avoid all changes for interrupt-entropy harvesting. > > > > Is there something more I shall avoid ? > > No, other than the buf/bio changes make the diffs harder to read. If you wanted to try to keep the two unified, there are macros in a few of my drivers that hide these. They're ugly, but they work. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 17:30:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp7ve.mailsrvcs.net (smtp7vepub.gte.net [206.46.170.28]) by hub.freebsd.org (Postfix) with ESMTP id DBBD137B40A for ; Fri, 20 Jul 2001 17:30:02 -0700 (PDT) (envelope-from info@wpi2001.com) Received: from wpi2001.com (client-141-150-248-226.delval.dialup.bellatlantic.net [141.150.248.226]) by smtp7ve.mailsrvcs.net (8.9.1/8.9.1) with SMTP id AAA45496921 for ; Sat, 21 Jul 2001 00:30:01 GMT Message-Id: <200107210030.AAA45496921@smtp7ve.mailsrvcs.net> From: "Washington Promotions International" To: Subject: Official America's Cup Jubilee Announcement Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Date: Fri, 20 Jul 2001 20:29:10 -0400 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG WASHINGTON PROMOTIONS INTERNATIONAL HONORED BY THE AMERICA'S CUP JUBILEE 2001 The America's Cup Jubilee Governing Committee in Cowes, United Kingdom has selected Washington Promotions International as the official U.S.A. merchandise licensee for the 150th Anniversary of the America's Cup. Please visit this web site to see the array of clothing, compasses, barometers and other commemorative items. http://wpi2001.com/index2.html Individuals, yacht and sailing clubs, and corporations everywhere, currently have the opportunity to acquire special items with ACJ2001 logo. Additionally, you may also choose to add your own logo to these fine items. This is a once in a lifetime opportunity to celebrate an event of this caliber and prestige. Please post to your newsletter or bulletin board. If you have any questions contact: Vassil C. Yanco (281)292-9810 Office (281)292-9331 Fax E-mail: info@wpi2001.com Web Site: http://wpi2001.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 17:43:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id EEDE737B405 for ; Fri, 20 Jul 2001 17:43:24 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f6L0hL477782; Fri, 20 Jul 2001 20:43:21 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <3B588760.E5875DBB@herbelot.com> References: <20010720183229.A9022@freebie.xs4all.nl> <3B588760.E5875DBB@herbelot.com> Date: Fri, 20 Jul 2001 20:43:19 -0400 To: Thierry Herbelot , Wilko Bulte From: Garance A Drosihn Subject: Re: dual booting -stable & -current Cc: freebsd-hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 9:32 PM +0200 7/20/01, Thierry Herbelot wrote: >Wilko Bulte wrote: >> >> I'm probably completely dim today so please bear with me :/ >> Thing is I want to setup a dual-boot box, running -stable & -current. >> This box, a P2/266 has a 30G IDE disk. >> >> What I did is create >> ad0s1 -> 256MB -> holds root for -stable >> ad0s2 -> 256MB -> was supposed to hold root for -current >> ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable >> ad0s4 -> ditto for -current >> >> My recollection is that as long as you keep the root partitions <2 (or 8) GB >> it should be bootable. Hence this somewhat strange slicing. >> >> Thing is, 4.3R refuses to install it's root on ad0s2 (4.3 because I want >> to go current from there). >> > > I'm probably missing something obvious here? Somehow I missed the beginning of this thread. I suspect you're running into the same issue I recently described in a message in the thread on "Suggestions for sysinstall / disklabel" in -hackers. I think I sent it in the last two or three days. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 19: 5:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web13608.mail.yahoo.com (web13608.mail.yahoo.com [216.136.175.119]) by hub.freebsd.org (Postfix) with SMTP id 7AC8537B403 for ; Fri, 20 Jul 2001 19:05:26 -0700 (PDT) (envelope-from websoft@yahoo.com) Message-ID: <20010721020526.74531.qmail@web13608.mail.yahoo.com> Received: from [210.74.232.43] by web13608.mail.yahoo.com via HTTP; Fri, 20 Jul 2001 19:05:26 PDT Date: Fri, 20 Jul 2001 19:05:26 -0700 (PDT) From: Yifeng Xu Subject: MFC FFS dirpref code? To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG could anyone think about MFC FFS dirpref code? is it still not enough stable in CURRENT? I heard OpenBSD 2.9 has it already. __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 19: 8:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (okc-27-141-144.mmcable.com [24.27.141.144]) by hub.freebsd.org (Postfix) with SMTP id AF23037B401 for ; Fri, 20 Jul 2001 19:08:45 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 93730 invoked by uid 100); 21 Jul 2001 02:08:45 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15192.58413.140597.213683@guru.mired.org> Date: Fri, 20 Jul 2001 21:08:45 -0500 To: Wilko Bulte Cc: freebsd-hackers@freebsd.org Subject: Re: dual booting -stable & -current In-Reply-To: <20010720183229.A9022@freebie.xs4all.nl> References: <20010720183229.A9022@freebie.xs4all.nl> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wilko Bulte types: > I'm probably completely dim today so please bear with me :/ > Thing is I want to setup a dual-boot box, running -stable & -current. > This box, a P2/266 has a 30G IDE disk. > > What I did is create > ad0s1 -> 256MB -> holds root for -stable > ad0s2 -> 256MB -> was supposed to hold root for -current > ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable > ad0s4 -> ditto for -current > > Thing is, 4.3R refuses to install it's root on ad0s2 (4.3 because I want > to go current from there). If you've already got -stable installed on ad0s1, why not mount the -current partitions on your -stable system, and then build and install those on -current? I just did mine that way to begin with, and thus avoided any problems with sysinstall. If you're tight on disk space - though it doesn't look like you are - you can save a bit by using the same swap partition for both systems. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 19:13:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 9FA8437B401 for ; Fri, 20 Jul 2001 19:13:45 -0700 (PDT) (envelope-from billf@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1098) id 5491381D01; Fri, 20 Jul 2001 21:13:35 -0500 (CDT) Date: Fri, 20 Jul 2001 21:13:35 -0500 From: Bill Fumerola To: Bill Moran Cc: mjacob@feral.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad Message-ID: <20010720211335.W2759@elvis.mu.org> References: <3B587E53.E6AFFC7C@iowna.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B587E53.E6AFFC7C@iowna.com>; from wmoran@iowna.com on Fri, Jul 20, 2001 at 02:54:11PM -0400 X-Operating-System: FreeBSD 4.3-FEARSOME-20010712 i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jul 20, 2001 at 02:54:11PM -0400, Bill Moran wrote: > > My guess, fwiw, is that somebody subscribed freebsd-hackers to some eGroup toy > > and this is why this is happening. Joy. > > I don't know. If it's coming from some eGroup, why is it originating at what > looks like a dialup address, and running through Earthling? > Looks like SPAM to me. It's not coming from eGroups. -- Bill Fumerola / 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 Jul 20 20:54:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f25.pav2.hotmail.com [64.4.37.25]) by hub.freebsd.org (Postfix) with ESMTP id CADC737B408 for ; Fri, 20 Jul 2001 20:54:33 -0700 (PDT) (envelope-from weiguang_shi@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 20 Jul 2001 20:54:33 -0700 Received: from 129.128.29.150 by pv2fd.pav2.hotmail.msn.com with HTTP; Sat, 21 Jul 2001 03:54:32 GMT X-Originating-IP: [129.128.29.150] From: "Weiguang SHI" To: freebsd-hackers@freebsd.org Subject: jmp after setting PE? Date: Fri, 20 Jul 2001 21:54:32 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 21 Jul 2001 03:54:33.0113 (UTC) FILETIME=[D9E02090:01C11198] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Please forgive me if this seems too easy. "http://people.freebsd.org/~jhb/386htm/s10_03.htm" says: Immediately after setting the PE flag, the initialization code must flush the processor's instruction prefetch queue by executing a JMP instruction. The 80386 fetches and decodes instructions and addresses before they are used; however, after a change into protected mode, the prefetched instruction information (which pertains to real-address mode) is no longer valid. A JMP forces the processor to discard the invalid information. "/home/src/sys/i386/i386" says: 329 /* Now enable paging */ 330 movl R(_IdlePTD), %eax 331 movl %eax,%cr3 /* load ptd addr into mm 332 movl %cr0,%eax /* get control word */ 333 orl $CR0_PE|CR0_PG,%eax /* enable paging */ 334 movl %eax,%cr0 /* and let's page NOW! * 335 336 #ifdef BDE_DEBUGGER 337 /* 338 * Complete the adjustments for paging so that we can keep tracing throu 339 * initi386() after the low (physical) addresses for the gdt and idt bec 340 * invalid. 341 */ 342 call bdb_commit_paging 343 #endif 344 345 pushl $begin /* jump to high virtuali 346 ret My question is "where is the "jmp" instruction which is supposed to immediately follow the instruction setting PE? Or do I miss anything? Thanks Weiguang PS. I am looking at 4.3 stable. _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 21: 6:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 840E937B408 for ; Fri, 20 Jul 2001 21:06:20 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f6L469r53456; Fri, 20 Jul 2001 21:06:09 -0700 (PDT) (envelope-from obrien) Date: Fri, 20 Jul 2001 21:06:09 -0700 From: "David O'Brien" To: Wilko Bulte Cc: freebsd-hackers@freebsd.org Subject: Re: dual booting -stable & -current Message-ID: <20010720210609.A53370@dragon.nuxi.com> Reply-To: freebsd-hackers@freebsd.org References: <20010720183229.A9022@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010720183229.A9022@freebie.xs4all.nl>; from wkb@freebie.xs4all.nl on Fri, Jul 20, 2001 at 06:32:29PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jul 20, 2001 at 06:32:29PM +0200, Wilko Bulte wrote: > I'm probably completely dim today so please bear with me :/ > Thing is I want to setup a dual-boot box, running -stable & -current. > This box, a P2/266 has a 30G IDE disk. > > What I did is create > ad0s1 -> 256MB -> holds root for -stable > ad0s2 -> 256MB -> was supposed to hold root for -current > ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable > ad0s4 -> ditto for -current You are getting bit by the "root" aliasing code (IIRC this is the right way to describe the problem). This makes it impossible to install multiple copies of FreeBSD on a single disk w/o hacking around the system. :-( The way to do this, is 1st install -stable. Create all four slices in the disk slice editor. In the label editor, do your normal thing, but don't bother doing anything with ad0s2. Continue with install as usual. Boot again from CDROM or floppies and enter the slice editor. Change the partition type of ad0s1 from 165 (FreeBSD FFS) to something else. Write this change to disk and exit from sysinstall. Now install -current in the normal way. When you enter the slice editor you will see that all is as you want it. Make sure you choose easyboot vs. leaving the MBR alone or choosing "standard". You should now be able to create your -current root on ad0s2 and mount the partitions on ad0s3 and ad0s4 (change flag to not newfs them of course). Continue install as usual. Reboot using CDROM or floppies, enter slice editor and set the partition type of ad0s1 back to "165". Write changes, exit, reboot and do your F1 / F2 choice from booteasy. You might be able to optimize the number of times booting from CDROM to change the partition type of ad0s1. -- -- David (obrien@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 Jul 20 21:27:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id DE92137B405 for ; Fri, 20 Jul 2001 21:27:40 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f6L4RUO53751; Fri, 20 Jul 2001 21:27:30 -0700 (PDT) (envelope-from obrien) Date: Fri, 20 Jul 2001 21:27:26 -0700 From: "David O'Brien" To: Garance A Drosihn Cc: freebsd-hackers@FreeBSD.ORG, Bill Moran Subject: Re: Suggestions for sysinstall / disklabel Message-ID: <20010720212726.B53370@dragon.nuxi.com> Reply-To: freebsd-hackers@FreeBSD.ORG References: <59063B5B4D98D311BC0D0001FA7E452205FD9D73@l04.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from drosih@rpi.edu on Thu, Jul 19, 2001 at 05:29:10PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jul 19, 2001 at 05:29:10PM -0400, Garance A Drosihn wrote: > Now, remember that during the boot-up process, the "boot0" code requires > that the "partition to boot from" be the first partition in the slice. > The "boot1" code assumes that the "partition to boot from" is labelled > "partition a". So, that partition which I will want to be "/ for > release 5" needs to be both the first partition in the slice, and it > needs to be labelled "partition a". That is not true. You can put `b' at the beginning of the slice (what I think you mean by "first partition"), followed by `a' and the result boots just fine. [this is for i386 only!, this is not true for the Alpha] > Why does disklabel make it "partition e"? Because it knows that it > should use "partition a" for the partition which will be mounted > as "/". You did a lot of extra work to undo this. Just let sysinstall make it `e' and do your normal install. Then boot into your 4.3 and run disklabel da0s3 (or ad0s3). Go to the `e' and change it to `a' and save the label. Edit /etc/fstab and change the da0s3e to da0s3a. Or better yet, don't create anything within the da0s3 slice -- leave that to when you install -current in that slice. See my other email I just sent for instructions around the next problem sysinstall will give you. > Anyway, the above is a long-winded justification for the following > suggestions: > 1) if disklabel has already been told about '/', then it > should not try and reserve partition 'a' of OTHER SLICES > to also be '/'. The first partition created in those > other slices should just be labelled partition 'a'. I don't want my data partition in say sd0s4 to be `a'. `a' implies root. So your suggestion will irritate some. > 2) similarly, if it already has swap space defined, then > it should not try to reserve partition 'b' of other > slices to be swap. The second partition defined in > those other slices should be labelled partition 'b'. What is wrong with having more than one slice with swap in it? Nothing. Of course I don't really know what you mean by "second partition defined". Sysinstall orders the location of the [BSD] partitions within the slice in the order you create the [BSD] partitions. Sysinstall also knows that swap is always `b' and root is always `a'. Sysinstall skips `d' because `d' used to mean the entire disk in pre-2.2.6. (`d' would behave how others coming from non-PC Unixes would expect `c' to behave) So you'll have to change your wording to be a little more exact for others to follow your proposal. > Thinking about what people said about alpha installs, perhaps the > following is another strategy disklabel could take. On the other > hand, this may cause as many problems as it tries to solve. > > 4) never reserve 'a' or 'b'. Always create partitions in the > order people typed them in, except that WHEN someone says > they want to create '/', THEN both move that partition > to the front of the slice and name it 'a' (renaming other > partitions as needed). NO! Many want to put swap at the "beginning" of the disk as that is the fastest part of the disk. The i386 has no problems booting from a partition that is not located at the beginning of the disk(slice). The problem with the Alpha is people try the same "trick", but it does not work. -- -- David (obrien@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 Jul 20 22:14:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 8C1C437B405 for ; Fri, 20 Jul 2001 22:14:07 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f6L5E6F40183; Fri, 20 Jul 2001 23:14:06 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f6L5E5o71150; Fri, 20 Jul 2001 23:14:05 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107210514.f6L5E5o71150@harmony.village.org> To: Julian Elischer Subject: Re: arcnet support for FreeBSD (request for review) Cc: Max Khon , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 19 Jul 2001 00:00:17 PDT." <3B568581.5A798B3E@elischer.org> References: <3B568581.5A798B3E@elischer.org> Date: Fri, 20 Jul 2001 23:14:05 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3B568581.5A798B3E@elischer.org> Julian Elischer writes: : what is arcnet? Old, pre-ethernet technology. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 22:44: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 6D01837B406 for ; Fri, 20 Jul 2001 22:43:57 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f6L5hu427076; Sat, 21 Jul 2001 01:43:56 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20010720212726.B53370@dragon.nuxi.com> References: <59063B5B4D98D311BC0D0001FA7E452205FD9D73@l04.research.kpn.com> <20010720212726.B53370@dragon.nuxi.com> Date: Sat, 21 Jul 2001 01:43:50 -0400 To: freebsd-hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Suggestions for sysinstall / disklabel Cc: Bill Moran Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 9:27 PM -0700 7/20/01, David O'Brien wrote: >On Thu, Jul 19, 2001 at 05:29:10PM -0400, Garance A Drosihn wrote: >> Now, remember that during the boot-up process, the "boot0" code requires >> that the "partition to boot from" be the first partition in the slice. >> The "boot1" code assumes that the "partition to boot from" is labelled >> "partition a". So, that partition which I will want to be "/ for >> release 5" needs to be both the first partition in the slice, and it >> needs to be labelled "partition a". > >That is not true. You can put `b' at the beginning of the slice (what >I think you mean by "first partition"), followed by `a' and the result >boots just fine. [this is for i386 only!, this is not true for the Alpha] Oh. But that is only an option for the swap partition, not some other UFS partition? Right? I'm still a little fuzzy on how these parts fit together. So boot0 just looks for the first UFS partition in the slice you selected, and assumes it is root? > > Why does disklabel make it "partition e"? Because it knows that it >> should use "partition a" for the partition which will be mounted >> as "/". > >You did a lot of extra work to undo this. Just let sysinstall make >it `e' and do your normal install. Then boot into your 4.3 and run >disklabel da0s3 (or ad0s3). Go to the `e' and change it to `a' and >save the label. Edit /etc/fstab and change the da0s3e to da0s3a. Yeah. Eventually I figured that out. I am not one to casually run disklabel to change partition names on an already-running system (in fact, this was the first time I have ever run disklabel directly). >Or better yet, don't create anything within the da0s3 slice -- leave that >to when you install -current in that slice. See my other email I just >sent for instructions around the next problem sysinstall will give you. I "needed" to create partitions in both slices for stable, due to the way I wanted to set things up. And I intended to install 4.3, update to stable, copy the 4.3-specific {/,/var,/usr} to the /x5 equivalent partitions (if you remember my naming scheme), and then update THAT to turn it into current. So, I did really want stable to come up with all of the partitions (both stable and current) that I defined. > > Anyway, the above is a long-winded justification for the following >> suggestions: >> 1) if disklabel has already been told about '/', then it >> should not try and reserve partition 'a' of OTHER SLICES >> to also be '/'. The first partition created in those >> other slices should just be labelled partition 'a'. > >I don't want my data partition in say sd0s4 to be `a'. `a' implies >root. So your suggestion will irritate some. But if "you" (meaning the "user doing the install") are creating a data partition in a "second slice", doesn't that pretty much imply that it can't possibly be root? [note that I don't have a long history of formatting unix partitions, so it wouldn't surprise me if I am suggesting things which seem weird to people with a longer history in bsd's]. [I'm not sure I made this obvious in my previous message, but these suggestions were meant for the situation where the user is doing a single install where they are spraying freebsd slices across multiple partitions -- as was in the case in the example I gave] In any case, sysinstall already will create 'a' partitions which are not "root", if you just ask it to create enough of them that it has run out of letters. Why should I care if it irritates "some" people if I what to use partition 'a' on a second slice as /home? It's my disk, it works, it does not break anything. [or does it?] > > 2) similarly, if it already has swap space defined, then > > it should not try to reserve partition 'b' of other >> slices to be swap. The second partition defined in >> those other slices should be labelled partition 'b'. > >What is wrong with having more than one slice with swap in it? >Nothing. Er, yeah. I do agree. I think I forgot some extra sentence in this suggestion, because I meant that to sound more like an "there should be a way that a user could tell sysinstall", and not that "sysinstall should never reserve 'b' for swap". At the time I was writing this I did mean to allow for swap partitions in multiple slices, although in my specific case I (personally, on my disk) knew that I only wanted one swap partition. I wanted disklabel to let me name things "the way I wanted", instead of "the way it thinks is good for me". >Of course I don't really know what you mean by "second partition >defined". Sysinstall orders the location of the [BSD] partitions within >the slice in the order you create the [BSD] partitions. Sysinstall also >knows that swap is always `b' and root is always `a'. Sysinstall skips >`d' because `d' used to mean the entire disk in pre-2.2.6. (`d' would >behave how others coming from non-PC Unixes would expect `c' to behave) >So you'll have to change your wording to be a little more exact for >others to follow your proposal. Yes, you've the right idea of what I meant, even if I didn't phrase it quite right. "Second partition defined" was supposed to mean "the second one I asked sysinstall to create in that slice". What sysinstall does makes good sense for the partitions I am creating in my "first freebsd slice". I'm just saying that [maybe] it should not use those same rules when I start creating partitions in a second slice. Ie, here I am doing an install in two slices. Sysinstall should not care why I am daft enough to do that, but it should assume that if I am creating partitions in two slices as part of an INSTALL, then I really do mean to have all of those partitions to be active (mounted) in the resulting system. > > Thinking about what people said about alpha installs, perhaps the >> following is another strategy disklabel could take. On the other >> hand, this may cause as many problems as it tries to solve. >> >> 4) never reserve 'a' or 'b'. Always create partitions in the >> order people typed them in, except that WHEN someone says >> they want to create '/', THEN both move that partition >> to the front of the slice and name it 'a' (renaming other >> partitions as needed). > >NO! Many want to put swap at the "beginning" of the disk as that is >the fastest part of the disk. The i386 has no problems booting from a >partition that is not located at the beginning of the disk(slice). The >problem with the Alpha is people try the same "trick", but it does not >work. Hmm. Okay. As I say, I'm still fuzzy on how some of these pieces fit together when installing a system. I end up doing a new (fresh, clean) install about every six months, and with each one I figure out a few more details. Certainly I don't want to suggest anything which gets in the way of some other user's idea of how their install should go. I am just trying to describe what I went thru, and suggest ways which would have made it easier for me to do what I wanted. I just make the suggestions, I don't guarantee they are GOOD suggestions... :-) I am sure that anyone with a long history of installs could have set up exactly what I wanted with very little pain, but it would be nice if a new-ish freebsd user could do things like this without needing to become an expert about every little detail of how these pieces fit together. While what I wanted to do is a bit unusual, my goal seems perfectly reasonable and workable, and yet I had to fight my way around what sysinstall/disklabel thought "was good for me". If it had just done what I asked it to do (without it helpfully renaming those partitions in the second slice), then I could have been up-and-running in very little time. I would have had exactly what I wanted, and I would not have had to learn a lot about the loader, or disklabel, or send naive questions to any freebsd mailing lists. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 22:53:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gnf.org (firewall.gnf.org [208.44.31.34]) by hub.freebsd.org (Postfix) with ESMTP id 7003237B401; Fri, 20 Jul 2001 22:53:08 -0700 (PDT) (envelope-from gordont@gnf.org) Received: by mail.gnf.org (Postfix, from userid 888) id F1CA511E50E; Fri, 20 Jul 2001 22:48:18 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id EF8B011A56A; Fri, 20 Jul 2001 22:48:18 -0700 (PDT) Date: Fri, 20 Jul 2001 22:48:18 -0700 (PDT) From: Gordon Tetlow To: Mike Smith Cc: Subject: Re: Kernel module options Was: Re: Fw: help me!!!! In-Reply-To: <200107200839.f6K8d4V01460@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 20 Jul 2001, Mike Smith wrote: > > 3) Steal an idea from Linux (gasp!), and have module dependencies. ie, > > load ipfw.ko and then before we load up natd, we check to see if > > ipdivert.ko is loaded and load it. Alternatively, loading ipdivert.ko > > (before loading ipfw.ko), will automagically load ipfw.ko since ipfw is > > needed to get divert running. > > We've had this support for a long time already; module authors just > aren't taking advantage of it. Is this documented anywhere? If so, can you toss a pointer? I'd be interested in learning a little kernel hacking, and I can't imagine this would be *that* hard to implement. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 23: 8:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 7A8D437B401 for ; Fri, 20 Jul 2001 23:08:30 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f6L68T494316 for ; Sat, 21 Jul 2001 02:08:29 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20010720210609.A53370@dragon.nuxi.com> References: <20010720183229.A9022@freebie.xs4all.nl> <20010720210609.A53370@dragon.nuxi.com> Date: Sat, 21 Jul 2001 02:08:27 -0400 To: freebsd-hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: dual booting -stable & -current Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 9:06 PM -0700 7/20/01, David O'Brien wrote: >On Fri, Jul 20, 2001, Wilko Bulte wrote: > > Thing is I want to setup a dual-boot box, running -stable & -current. > > >> What I did is create >> ad0s1 -> 256MB -> holds root for -stable >> ad0s2 -> 256MB -> was supposed to hold root for -current >> ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable >> ad0s4 -> ditto for -current > >You are getting bit by the "root" aliasing code (IIRC this is the >right way to describe the problem). This makes it impossible to >install multiple copies of FreeBSD on a single disk w/o hacking >around the system. :-( While I understand the steps you described, it seems to me we should be able to come up with an easier way to do this. What you described is probably quite straightforward to you, but that's because you're already familiar with all the programs you're referring to, and you've worked with them long enough that it's all second-nature to you. Me, I'm hoping to do the installs I want to do without having to become as much of an expert... :-) I think there should be a way to do this which does not require quite so many steps, and so much flip-flopping between programs. The tactic I described in the other thread was ALMOST easy, if I had just understood a little more of what was going on. And I suspect that with a few changes [somewhere...], we could make that strategy work without having to change the type of slices, or having to run diskedit to rename partitions within the slices we've created. >Now install -current in the normal way. When you enter the slice >editor you will see that all is as you want it. In my situation, I had the 4.3-release CD at home, and a very slow network connection. So, "the normal way" for me to install current is to install 4.3 first, and then use cvsup & buildworld to get to 5. I don't know how normal that would seem to other people, but given that that is how I intended to do it, then I just have this feeling that there should be some easier way to get thru the sysinstall/disklabel issues without becoming an expert with renaming partition types, etc. obviously I need to learn a bit more and do a little more thinking before I can say exactly what that "easier way" is, but I do think it's possible... -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 23:38:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (d211.dhcp212-26.cybercable.fr [212.198.26.211]) by hub.freebsd.org (Postfix) with ESMTP id E1B5537B401 for ; Fri, 20 Jul 2001 23:38:19 -0700 (PDT) (envelope-from thierry@herbelot.com) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id IAA08089; Sat, 21 Jul 2001 08:37:07 +0200 (CEST) (envelope-from thierry@herbelot.com) Message-ID: <3B59234D.CAADC791@herbelot.com> Date: Sat, 21 Jul 2001 08:38:05 +0200 From: Thierry Herbelot X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Cc: Wilko Bulte Subject: Re: dual booting -stable & -current References: <20010720183229.A9022@freebie.xs4all.nl> <20010720210609.A53370@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Fri, Jul 20, 2001 at 06:32:29PM +0200, Wilko Bulte wrote: > > I'm probably completely dim today so please bear with me :/ > > Thing is I want to setup a dual-boot box, running -stable & -current. > > This box, a P2/266 has a 30G IDE disk. > > > > What I did is create > > ad0s1 -> 256MB -> holds root for -stable > > ad0s2 -> 256MB -> was supposed to hold root for -current > > ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable > > ad0s4 -> ditto for -current > > You are getting bit by the "root" aliasing code (IIRC this is the right > way to describe the problem). This makes it impossible to install > multiple copies of FreeBSD on a single disk w/o hacking around the > system. :-( I do not understand what this problem is : - I've got one system with two bootable FreeBSD "BIOS" partitions (the one I already sent info about (these are two -Stable versions) and both versions have been installed via /stand/sysinstall - Another system runs with two FreeBSD "BIOS" partitions (used to switch between 3-Stable and 4-Stable) the boot0 boot selector is used to switch between releases - a third (a notebook) has one FreeBSD "BIOS" partition and used to be shared between 4-Stable and -Current (using all 8 FreeBSD partitions in the slice and using the loader to select ad0s4a or ad0s4e for root partition) - In this case, /stand/sysinstall was unable to create all 8 FreeBSD partitions : I had to first install FreeBSD on ad0s3, cut 8 partitions in ad0s4, then reinstall in ad0s4. [SNIP] -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jul 20 23:56:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id CBB1C37B403 for ; Fri, 20 Jul 2001 23:56:31 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f6L6uU471122; Sat, 21 Jul 2001 02:56:30 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: <59063B5B4D98D311BC0D0001FA7E452205FD9D73@l04.research.kpn.com> <20010720212726.B53370@dragon.nuxi.com> Date: Sat, 21 Jul 2001 02:56:28 -0400 To: freebsd-hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Suggestions for sysinstall / disklabel Cc: Bill Moran Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 1:43 AM -0400 7/21/01, Garance A Drosihn wrote: >[I'm not sure I made this obvious in my previous message, but these >suggestions were meant for the situation where the user is doing a >single install where they are spraying freebsd slices across multiple >partitions -- as was in the case in the example I gave] I meant "spraying freebsd PARTITIONS across multiple dos-style SLICES". I keep getting those two terms mixed up... -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 0: 5:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gnf.org (firewall.gnf.org [208.44.31.34]) by hub.freebsd.org (Postfix) with ESMTP id 07FA237B403; Sat, 21 Jul 2001 00:05:44 -0700 (PDT) (envelope-from gordont@gnf.org) Received: by mail.gnf.org (Postfix, from userid 888) id 9813C11E50E; Sat, 21 Jul 2001 00:00:54 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id 94A9611A56A; Sat, 21 Jul 2001 00:00:54 -0700 (PDT) Date: Sat, 21 Jul 2001 00:00:54 -0700 (PDT) From: Gordon Tetlow To: Mike Smith Cc: Subject: Re: Kernel module options Was: Re: Fw: help me!!!! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 20 Jul 2001, Gordon Tetlow wrote: > Is this documented anywhere? If so, can you toss a pointer? I'd be > interested in learning a little kernel hacking, and I can't imagine this > would be *that* hard to implement. Nm, I was too lazy to check before, but apparently man module has lots of interesting information. Sorry about that. I'll go off into a corner and read now. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 0:22:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 7F57937B403 for ; Sat, 21 Jul 2001 00:22:10 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f6L7M8496710; Sat, 21 Jul 2001 03:22:08 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <3B59234D.CAADC791@herbelot.com> References: <20010720183229.A9022@freebie.xs4all.nl> <20010720210609.A53370@dragon.nuxi.com> <3B59234D.CAADC791@herbelot.com> Date: Sat, 21 Jul 2001 03:22:04 -0400 To: Thierry Herbelot , freebsd-hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: dual booting -stable & -current Cc: Wilko Bulte Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 8:38 AM +0200 7/21/01, Thierry Herbelot wrote: >David O'Brien wrote: > > You are getting bit by the "root" aliasing code (IIRC this is the > > right way to describe the problem). This makes it impossible to > > install multiple copies of FreeBSD on a single disk w/o hacking > > around the system. :-( > >I do not understand what this problem is : >- I've got one system with two bootable FreeBSD "BIOS" partitions > (the one I already sent info about (these are two -Stable > versions) and both versions have been installed via > /stand/sysinstall How did you do those two installs though? David is not saying that dual-booting does not work. He is saying that the sysinstall step can get in your way, depending on how you try to create the two systems you want to boot between. Once you GET the slices and partitions set up right, then the booting process can easily handle multiple freebsd systems on a single disk. For instance, in the following sequence you should not run into any trouble with sysinstall: first set up a dual-boot system with the first dos-style slice being Windows, and the second one holding freebsd. after running this way for awhile, you decide that you do not need windows any more. So you again boot off the FreeBSD cd, you blow away Windows, and you install a second snapshot of freebsd on the slice which used to be Windows. For both of those freebsd installs, at the time of the install the first slice on the disk which was of type freebsd was also the slice that you wanted root (the '/' partition) of the new installation to be on. So, sysinstall has no trouble with what you want to do. Where you have trouble is if you have two dos-style slices defined, both of type freebsd, and you want sysinstall to install into the second of those two slices. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 0:37:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 60CEB37B403 for ; Sat, 21 Jul 2001 00:37:55 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.134.98.Dial1.SanJose1.Level3.net [209.245.134.98]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA06609; Sat, 21 Jul 2001 00:37:49 -0700 (PDT) Message-ID: <3B593172.1AD11A3@mindspring.com> Date: Sat, 21 Jul 2001 00:38:26 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ian Dowse Cc: mjacob@feral.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Default retry behaviour for mount_nfs References: <200107202327.aa64363@salmon.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ian Dowse wrote: > > In message <3B585C76.696F1E2A@mindspring.com>, Terry Lambert writes: > >> FWIW, I vote that we rever to the traditional default and require > >> -R1 or -b to avoid boot time hangs. The standard behaviour for most > >> NFS implementations that I'm aware of would do this. > > > >I agree; people at work have bitched about this. We have a > >FreeBSD NFS server that's flakey. > > Ok, from the small set of responses so far, it seems that the most > acceptable option is to change mount_nfs to behave in the old way > where it will retry forever by default even in foreground mode. > Below is a proposed patch that does this. It also adds two paragraphs > near the start of the manpage which describe the default behaviour > and point readers at the relevant options. Comments welcome. > > >The other thing is that it appears to break amd behaviour. > > Does amd use mount_nfs(8)? I thought it did the mount syscalls > directly. I don't care to understand the bowels of amd, since I see enough of their product... 8-|. But it seems the behaviour changed between 4.3 and later, and it's been a problem (things like "cd" time out instead of waiting until they can get a good grip on the NFS server. Very frustrating, when your CVS tree or home directory lives on another machine. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 0:45: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 769F437B405 for ; Sat, 21 Jul 2001 00:45:02 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.134.98.Dial1.SanJose1.Level3.net [209.245.134.98]) by falcon.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA01723; Sat, 21 Jul 2001 00:45:00 -0700 (PDT) Message-ID: <3B593321.26C7B02F@mindspring.com> Date: Sat, 21 Jul 2001 00:45:37 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Cc: Wilko Bulte Subject: Re: dual booting -stable & -current References: <20010720183229.A9022@freebie.xs4all.nl> <20010720210609.A53370@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: > On Fri, Jul 20, 2001 at 06:32:29PM +0200, Wilko Bulte wrote: > > I'm probably completely dim today so please bear with me :/ > > Thing is I want to setup a dual-boot box, running -stable & -current. > > This box, a P2/266 has a 30G IDE disk. > > > > What I did is create > > ad0s1 -> 256MB -> holds root for -stable > > ad0s2 -> 256MB -> was supposed to hold root for -current > > ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable > > ad0s4 -> ditto for -current > > You are getting bit by the "root" aliasing code (IIRC this is the right > way to describe the problem). This makes it impossible to install > multiple copies of FreeBSD on a single disk w/o hacking around the > system. :-( > > The way to do this, is 1st install -stable. > Create all four slices in the disk slice editor. In the label editor, do > your normal thing, but don't bother doing anything with ad0s2. Continue > with install as usual. You can do this pretty trivially by using the new boot code, and setting the "root dev". When booting, hit the spacebar during the countdown, type "unload", and then type "set rootdev=xxx", where "xxx" is your root device you want to boot from. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 1: 8:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx.nsu.ru (mx.nsu.ru [193.124.215.71]) by hub.freebsd.org (Postfix) with ESMTP id 0B40A37B401 for ; Sat, 21 Jul 2001 01:08:07 -0700 (PDT) (envelope-from lucky@land3.nsu.ru) Received: from land3.nsu.ru (land3.nsu.ru [193.124.213.230]) by mx.nsu.ru (8.9.1/8.9.3) with ESMTP id PAA07670 for ; Sat, 21 Jul 2001 15:07:07 +0700 (NOVST) Received: from localhost (lucky@localhost) by land3.nsu.ru (8.11.4/8.11.4) with ESMTP id f6L870D12618 for ; Sat, 21 Jul 2001 15:07:00 +0700 (NOVST) (envelope-from lucky@land3.nsu.ru) Date: Sat, 21 Jul 2001 15:07:00 +0700 (NOVST) From: Alexey Privalov To: freebsd-hackers@freebsd.org Subject: strange with named Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi all. i have FreeBSD 4.3-STABLE and named 8.2.3-REL. everyday i see following strings in my log: Jul 21 13:43:17 host named[124]: denied update from [196.127.211.51].1475 for "host.domain" Jul 21 13:48:17 host named[124]: denied update from [196.127.211.51].1486 for "host.domain" Jul 21 13:58:18 host named[124]: denied update from [196.127.211.51].1501 for "host.domain" what i must do for fixed it? and where is a bug? (on server or on that machine). thanks for all. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 3:10:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from active.ath.cx (ras8-p117.hfa.netvision.net.il [62.0.103.117]) by hub.freebsd.org (Postfix) with ESMTP id 1EF4E37B403 for ; Sat, 21 Jul 2001 03:10:20 -0700 (PDT) (envelope-from amir@boom.org.il) Received: by active.ath.cx (Postfix, from userid 1000) id 5ABC76E7BB; Sat, 21 Jul 2001 13:10:13 +0300 (IDT) Received: from localhost (localhost [127.0.0.1]) by active.ath.cx (Postfix) with ESMTP id 13B3B6A9CE for ; Sat, 21 Jul 2001 13:10:13 +0300 (IDT) Date: Sat, 21 Jul 2001 13:10:12 +0300 (IDT) From: Amir Shalem X-X-Sender: To: Subject: question about ttys Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG in kernel, when I have (struct tty*)cur_tty pointer how can I know if the cur_tty is a console (ttyv) ? or X windows ? I'm writing a wheel support for console, but it creates problem with the X windows. thanks, Amir. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 3:12:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 4585237B401 for ; Sat, 21 Jul 2001 03:12:28 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.134.98.Dial1.SanJose1.Level3.net [209.245.134.98]) by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id DAA20593; Sat, 21 Jul 2001 03:11:06 -0700 (PDT) Message-ID: <3B595554.4C5245EB@mindspring.com> Date: Sat, 21 Jul 2001 03:11:32 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Alexey Privalov Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: strange with named References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alexey Privalov wrote: > > hi all. > i have FreeBSD 4.3-STABLE and named 8.2.3-REL. > everyday i see following strings in my log: > > Jul 21 13:43:17 host named[124]: denied update from [196.127.211.51].1475 for "host.domain" > Jul 21 13:48:17 host named[124]: denied update from [196.127.211.51].1486 for "host.domain" > Jul 21 13:58:18 host named[124]: denied update from [196.127.211.51].1501 for "host.domain" > > what i must do for fixed it? and where is a bug? (on server or on that > machine). Most likely, this is an NT box which has detected a nameserver and is trying to be "helpful" by "updating" you, since it's the primary domain controller, knows everything, and you know nothing (or you would have won the election for domain controller). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 4:23:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id ECB4637B405 for ; Sat, 21 Jul 2001 04:23:51 -0700 (PDT) (envelope-from netch@iv.nn.kiev.ua) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id OJB54935; Sat, 21 Jul 2001 14:23:33 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.11.4/8.11.4) id f6LB0Wa06508; Sat, 21 Jul 2001 14:00:32 +0300 (EEST) (envelope-from netch) Date: Sat, 21 Jul 2001 14:00:32 +0300 From: Valentin Nechayev To: Alexey Privalov Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: strange with named Message-ID: <20010721140032.A6439@iv.nn.kiev.ua> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from lucky@land3.nsu.ru on Sat, Jul 21, 2001 at 03:07:00PM +0700 X-42: On Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sat, Jul 21, 2001 at 15:07:00, lucky (Alexey Privalov) wrote about "strange with named": > Jul 21 13:43:17 host named[124]: denied update from [196.127.211.51].1475 for "host.domain" > Jul 21 13:48:17 host named[124]: denied update from [196.127.211.51].1486 for "host.domain" > Jul 21 13:58:18 host named[124]: denied update from [196.127.211.51].1501 for "host.domain" Nothing wrong with your named if such updates are really disallowed. Wrong ACL if they are right. Most probably a Win2000 host with misconfigured DNS is on this address. This question is IMO more appropriate for -questions. /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 6:47:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 376AC37B405 for ; Sat, 21 Jul 2001 06:47:30 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 21 Jul 2001 14:47:29 +0100 (BST) To: freebsd-hackers@freebsd.org Subject: fdisk(8) adjusting to head/cylinder bounderies Date: Sat, 21 Jul 2001 14:47:29 +0100 From: Ian Dowse Message-ID: <200107211447.aa29342@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG For about a year, fdisk(8) has had code that automatically adjusts partitions to begin on a head boundary and end on a cylinder boundary. This is fine in most situations, but the way it is implemented makes it awkward to override, and more importantly it is way too easy to mess up an existing partition that is not properly aligned on a head/cylinder boundary. Currently, fdisk never asks the user for confirmation of changes to the partition start and size. It just prints out a message such as WARNING: adjusting start offset of partition to 12345 to fall on a head boundary and then it immediately goes on to print out the full slice details, so that warning is easily missed. It is possible to avoid the automatic adjustment by answering "y" to the Explicitly specify beg/end address? question that refers to setting the c/h/s parameters, but if you do that, then you can't make use of the automatic c/h/s calculation. This problem bites me almost every time I use fdisk, since we have a lot of disks that have been split into multiple partitions to get around the 7 partitions/slice limit. I have always just changed the slice to end exactly where the last partition ends, so having fdisk rounding that down by a few sectors is not desirable. These disks are generally SCSI, contain only FreeBSD partitions, and the BIOSes we work with have never had problems with partitions that are not head/cylinder aligned. Below is a patch that makes fdisk request user confirmation before making any changes to the start and end of partitions. It also untangles the automatic c/h/s calculation from the start/size adjustment, and doesn't set the partition type to 0 if the adjustment fails. I haven't put a great deal of thought into the specifics of the patch, so any comments or suggestions are welcome. I just want to avoid the behaviour where carefully calculated partition parameters supplied by the user get changed automatically with only an easily- missed warning printed. Ian Index: fdisk.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/sbin/i386/fdisk/fdisk.c,v retrieving revision 1.50 diff -u -r1.50 fdisk.c --- fdisk.c 2001/07/13 16:48:56 1.50 +++ fdisk.c 2001/07/21 12:02:01 @@ -548,6 +548,7 @@ Decimal("sysid (165=FreeBSD)", partp->dp_typ, tmp); Decimal("start", partp->dp_start, tmp); Decimal("size", partp->dp_size, tmp); + sanitize_partition(partp); if (ok("Explicitly specify beg/end address ?")) { @@ -572,8 +573,6 @@ partp->dp_esect = DOSSECT(tsec,tcyl); partp->dp_ehd = thd; } else { - if (!sanitize_partition(partp)) - partp->dp_typ = 0; dos(partp->dp_start, partp->dp_size, &partp->dp_scyl, &partp->dp_ssect, &partp->dp_shd); dos(partp->dp_start + partp->dp_size - 1, partp->dp_size, @@ -1398,6 +1397,17 @@ max_end = partp->dp_start + partp->dp_size; + if (partp->dp_start % dos_sectors != 0 || + (partp->dp_start + partp->dp_size) % dos_sectors != 0) { + if (partp->dp_start % dos_sectors != 0) + warnx("WARNING: partition does not begin on a head boundary"); + if ((partp->dp_start + partp->dp_size) % dos_sectors != 0) + warnx("WARNING: partition does not end on a cylinder boundary"); + warnx("WARNING: this may confuse the BIOS or other operating systems"); + if (!ok("Correct this automatically?")) + return(1); + } + /* * Adjust start upwards, if necessary, to fall on an head boundary. */ @@ -1412,9 +1422,7 @@ "ERROR: unable to adjust start of partition to fall on a head boundary"); return (0); } - warnx( - "WARNING: adjusting start offset of partition\n\ - to %u to fall on a head boundary", + warnx("WARNING: adjusting start offset of partition to %u", (u_int)(prev_head_boundary + dos_sectors)); partp->dp_start = prev_head_boundary + dos_sectors; } @@ -1434,10 +1442,7 @@ return (0); } if (adj_size != partp->dp_size) { - warnx( - "WARNING: adjusting size of partition to %u to end on a\n\ - cylinder boundary", - (u_int)adj_size); + warnx("WARNING: adjusting size of partition to %u", (u_int)adj_size); partp->dp_size = adj_size; } if (partp->dp_size == 0) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 7:28: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from saturn.bsdhome.com (unknown [24.25.2.193]) by hub.freebsd.org (Postfix) with ESMTP id B7DB837B405 for ; Sat, 21 Jul 2001 07:27:54 -0700 (PDT) (envelope-from bsd@bsdhome.com) Received: from neutrino.bsdhome.com (jupiter [192.168.220.13]) by saturn.bsdhome.com (8.11.3/8.11.3) with ESMTP id f6LEReC15395; Sat, 21 Jul 2001 10:27:41 -0400 (EDT) Received: (from bsd@localhost) by neutrino.bsdhome.com (8.11.4/8.11.4) id f6LERZR06624; Sat, 21 Jul 2001 10:27:35 -0400 (EDT) (envelope-from bsd) Date: Sat, 21 Jul 2001 10:27:35 -0400 From: Brian Dean To: Ian Dowse Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fdisk(8) adjusting to head/cylinder bounderies Message-ID: <20010721102735.A6275@neutrino.bsdhome.com> References: <200107211447.aa29342@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107211447.aa29342@salmon.maths.tcd.ie>; from iedowse@maths.tcd.ie on Sat, Jul 21, 2001 at 02:47:29PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Jul 21, 2001 at 02:47:29PM +0100, Ian Dowse wrote: > Below is a patch that makes fdisk request user confirmation before > making any changes to the start and end of partitions. Please allow this behaviour to be overridden by a flag that can specified so that scripts don't suddenly stop and wait for input. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 7:56: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id E4F7737B405 for ; Sat, 21 Jul 2001 07:56:00 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 21 Jul 2001 15:56:00 +0100 (BST) To: Brian Dean Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fdisk(8) adjusting to head/cylinder bounderies In-Reply-To: Your message of "Sat, 21 Jul 2001 10:27:35 EDT." <20010721102735.A6275@neutrino.bsdhome.com> Date: Sat, 21 Jul 2001 15:55:59 +0100 From: Ian Dowse Message-ID: <200107211556.aa51144@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010721102735.A6275@neutrino.bsdhome.com>, Brian Dean writes: >On Sat, Jul 21, 2001 at 02:47:29PM +0100, Ian Dowse wrote: > >> Below is a patch that makes fdisk request user confirmation before >> making any changes to the start and end of partitions. > >Please allow this behaviour to be overridden by a flag that can >specified so that scripts don't suddenly stop and wait for input. Sorry, I should have mentioned this; the patch only changes the interactive case. The code to adjust the partition offsets and sizes for config file based updates using the -f option has not changed. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 9:44:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (d211.dhcp212-26.cybercable.fr [212.198.26.211]) by hub.freebsd.org (Postfix) with ESMTP id EBF4537B403 for ; Sat, 21 Jul 2001 09:44:36 -0700 (PDT) (envelope-from thierry@herbelot.com) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id SAA08826; Sat, 21 Jul 2001 18:43:23 +0200 (CEST) (envelope-from thierry@herbelot.com) Message-ID: <3B59B15A.5C8E8851@herbelot.com> Date: Sat, 21 Jul 2001 18:44:10 +0200 From: Thierry Herbelot X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Garance A Drosihn Cc: freebsd-hackers@FreeBSD.ORG, Wilko Bulte Subject: Re: dual booting -stable & -current References: <20010720183229.A9022@freebie.xs4all.nl> <20010720210609.A53370@dragon.nuxi.com> <3B59234D.CAADC791@herbelot.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Garance A Drosihn wrote: > [SNIP] > > How did you do those two installs though? David is not saying that I don't remember very well : it may well have been done via cloning an existing slice via dump/restore (thus no sysinstall troubles ...) [SNIP] > > Where you have trouble is if you have two dos-style slices defined, > both of type freebsd, and you want sysinstall to install into the > second of those two slices. ^^^^^^ OK, got it : I also installed a 3.5.1 from CD/sysinstall, but it was on the 3rd BIOS partition, where the 4th was also FreeBSD (but situated in the disk *after* ad0s3 which was to be the new boot partition) [SNIP] BTW : thanks for the *detailed* explanation -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 9:55: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by hub.freebsd.org (Postfix) with ESMTP id 9BF2937B403 for ; Sat, 21 Jul 2001 09:54:56 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id SAA04986 for ; Sat, 21 Jul 2001 18:54:54 +0200 (CEST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.4/8.11.4) id f6LGssD18516 for freebsd-hackers@freebsd.org; Sat, 21 Jul 2001 18:54:54 +0200 (CEST) (envelope-from wkb) Date: Sat, 21 Jul 2001 18:54:54 +0200 From: Wilko Bulte To: freebsd-hackers@freebsd.org Subject: Re: dual booting -stable & -current Message-ID: <20010721185454.A18482@freebie.xs4all.nl> References: <20010720183229.A9022@freebie.xs4all.nl> <20010720210609.A53370@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010720210609.A53370@dragon.nuxi.com>; from nobody@NUXI.com on Fri, Jul 20, 2001 at 09:06:09PM -0700 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jul 20, 2001 at 09:06:09PM -0700, David O'Brien wrote: > On Fri, Jul 20, 2001 at 06:32:29PM +0200, Wilko Bulte wrote: > > I'm probably completely dim today so please bear with me :/ > > Thing is I want to setup a dual-boot box, running -stable & -current. > > This box, a P2/266 has a 30G IDE disk. > > > > What I did is create > > ad0s1 -> 256MB -> holds root for -stable > > ad0s2 -> 256MB -> was supposed to hold root for -current > > ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable > > ad0s4 -> ditto for -current > > You are getting bit by the "root" aliasing code (IIRC this is the right > way to describe the problem). This makes it impossible to install > multiple copies of FreeBSD on a single disk w/o hacking around the > system. :-( Thanks a lot for making me feel less dim ;-) This indeed fixed it. I always though Unix^WFreeBSD was supposed to allow you to shoot yourself in the foot. sysinstall obviously decided it needed to outsmart me. Duh.. W/ -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte "Youth is not a time in life, it is a state of mind" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 10: 1:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by hub.freebsd.org (Postfix) with ESMTP id 139EC37B406 for ; Sat, 21 Jul 2001 10:01:11 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id TAA08055; Sat, 21 Jul 2001 19:01:06 +0200 (CEST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.4/8.11.4) id f6LH15f18566; Sat, 21 Jul 2001 19:01:05 +0200 (CEST) (envelope-from wkb) Date: Sat, 21 Jul 2001 19:01:05 +0200 From: Wilko Bulte To: freebsd-hackers@FreeBSD.ORG Cc: Garance A Drosihn , Bill Moran Subject: Re: Suggestions for sysinstall / disklabel Message-ID: <20010721190105.B18482@freebie.xs4all.nl> References: <59063B5B4D98D311BC0D0001FA7E452205FD9D73@l04.research.kpn.com> <20010720212726.B53370@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010720212726.B53370@dragon.nuxi.com>; from nobody@NUXI.com on Fri, Jul 20, 2001 at 09:27:26PM -0700 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jul 20, 2001 at 09:27:26PM -0700, David O'Brien wrote: > On Thu, Jul 19, 2001 at 05:29:10PM -0400, Garance A Drosihn wrote: > > Anyway, the above is a long-winded justification for the following > > suggestions: > > 1) if disklabel has already been told about '/', then it > > should not try and reserve partition 'a' of OTHER SLICES > > to also be '/'. The first partition created in those > > other slices should just be labelled partition 'a'. > > I don't want my data partition in say sd0s4 to be `a'. `a' implies root. > So your suggestion will irritate some. Like me (if that counts ;-) > > 2) similarly, if it already has swap space defined, then > > it should not try to reserve partition 'b' of other > > slices to be swap. The second partition defined in > > those other slices should be labelled partition 'b'. > > What is wrong with having more than one slice with swap in it? > Nothing. On the same disk it does not make too much sense, but it should not be illegal. > > 4) never reserve 'a' or 'b'. Always create partitions in the > > order people typed them in, except that WHEN someone says > > they want to create '/', THEN both move that partition > > to the front of the slice and name it 'a' (renaming other > > partitions as needed). > > NO! Many want to put swap at the "beginning" of the disk as that is the > fastest part of the disk. The i386 has no problems booting from a People optimising the speed of the swap device are in a state of sin anyway. They should go out and buy some more memory to make their working set fit in core. [I know.. this is taking shortcuts. ] > partition that is not located at the beginning of the disk(slice). The > problem with the Alpha is people try the same "trick", but it does not > work. No.. -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte "Youth is not a time in life, it is a state of mind" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 11:46:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id AA6DD37B406 for ; Sat, 21 Jul 2001 11:46:09 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f6LIk2u98311; Sat, 21 Jul 2001 11:46:02 -0700 (PDT) (envelope-from obrien) Date: Sat, 21 Jul 2001 11:46:02 -0700 From: "David O'Brien" To: Wilko Bulte Cc: freebsd-hackers@freebsd.org Subject: Re: dual booting -stable & -current Message-ID: <20010721114602.A98232@dragon.nuxi.com> Reply-To: freebsd-hackers@freebsd.org References: <20010720183229.A9022@freebie.xs4all.nl> <20010720210609.A53370@dragon.nuxi.com> <20010721185454.A18482@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010721185454.A18482@freebie.xs4all.nl>; from wkb@freebie.xs4all.nl on Sat, Jul 21, 2001 at 06:54:54PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Jul 21, 2001 at 06:54:54PM +0200, Wilko Bulte wrote: > This indeed fixed it. I always though Unix^WFreeBSD was supposed to allow > you to shoot yourself in the foot. sysinstall obviously decided it needed > to outsmart me. Not so much out smart you, but the code that maps da0a to da0sXa is what gets in the way. It isn't smart enough (or maybe it is too convoluted to make it so). Mike Smith (and maybe JHB) would be the one that can explain this is propoer detail. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 11:55:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 18E4437B401 for ; Sat, 21 Jul 2001 11:55:32 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f6LItKF05260; Sat, 21 Jul 2001 11:55:20 -0700 (PDT) (envelope-from dillon) Date: Sat, 21 Jul 2001 11:55:20 -0700 (PDT) From: Matt Dillon Message-Id: <200107211855.f6LItKF05260@earth.backplane.com> To: Ian Dowse Cc: tlambert2@mindspring.com, mjacob@feral.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Default retry behaviour for mount_nfs References: <200107202327.aa64363@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :In message <3B585C76.696F1E2A@mindspring.com>, Terry Lambert writes: :>> FWIW, I vote that we rever to the traditional default and require :>> -R1 or -b to avoid boot time hangs. The standard behaviour for most :>> NFS implementations that I'm aware of would do this. :> :>I agree; people at work have bitched about this. We have a :>FreeBSD NFS server that's flakey. : :Ok, from the small set of responses so far, it seems that the most :acceptable option is to change mount_nfs to behave in the old way :where it will retry forever by default even in foreground mode. :Below is a proposed patch that does this. It also adds two paragraphs :near the start of the manpage which describe the default behaviour :and point readers at the relevant options. Comments welcome. : :>The other thing is that it appears to break amd behaviour. : :Does amd use mount_nfs(8)? I thought it did the mount syscalls :directly. : :Ian I'm going to throw in my two cents and agree here... backout the change so the original behavior is restored. Generally speaking when you have a foreground NFS mount in /etc/fstab, it's something important. And you want background mounts to stick around 'forever' too, because the network they are going through might take time to come up (wireless, pccardd, dialup). If someone doesn't want to wait for an NFS mount during boot they can 'bg' it, or 'noauto' it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 11:57:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from enterprise.spock.org (cm-24-29-85-81.nycap.rr.com [24.29.85.81]) by hub.freebsd.org (Postfix) with ESMTP id A9EBA37B401 for ; Sat, 21 Jul 2001 11:57:51 -0700 (PDT) (envelope-from jon@enterprise.spock.org) Received: (from jon@localhost) by enterprise.spock.org serial EF600Q3T-B7F; Sat, 21 Jul 2001 14:57:47 -0400 (EDT) (envelope-from jon)$ Date: Sat, 21 Jul 2001 14:57:47 -0400 From: Jonathan Chen To: Michael Sinz Cc: Attila Nagy , freebsd-hackers@FreeBSD.ORG Subject: Re: NFS local mount Message-ID: <20010721145747.B59221@enterprise.spock.org> References: <20010719155719.N45187-100000@scribble.fsn.hu> <3B57290F.15C009A5@wgate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: telnet/1.1x In-Reply-To: <3B57290F.15C009A5@wgate.com>; from msinz@wgate.com on Thu, Jul 19, 2001 at 02:38:07PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jul 19, 2001 at 02:38:07PM -0400, Michael Sinz wrote: > I had been meaning to ask if there was a reason why NFS mounts happened > before NFS servers were started but life kept getting in the way :-) If /usr was nfs mounted on a machine, then /usr needs to be mounted before nfsd was loaded, and portmap/rpcgen lives in /usr and nfsd requires one of those. Not to mention there are probably other services loaded before nfsd which may require nfs moutned directories. In general, it is a good idea to first setup vital parts of the system (like networking or mounting directories) before offering other services (such as nfsd). Possible ways to fix this includes: - do nothing, let those who run these circular nfs-mount systems fix it themselves. Perhaps recommend -o bg in the handbook or something. - setup a flag, nfs_mount_delayed="YES|NO" in rc.conf - do something in fstab which distingushes nfs mounts which can be delayed * a new nfs_delayed fstype [this screams EVILE HACK!], or * a new "delayable" option (how's that different from bg?) * overload the Pass number in fstab, nobody fscks over nfs anyway. Thoughts? -Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 12:54:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 15C0F37B403 for ; Sat, 21 Jul 2001 12:54:12 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f6LJsBq92138 for ; Sat, 21 Jul 2001 12:54:11 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f6LJsAk34902; Sat, 21 Jul 2001 12:54:10 -0700 (PDT) (envelope-from jdp) Date: Sat, 21 Jul 2001 12:54:10 -0700 (PDT) Message-Id: <200107211954.f6LJsAk34902@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Subject: Re: dual booting -stable & -current In-Reply-To: <20010720210609.A53370@dragon.nuxi.com> References: <20010720183229.A9022@freebie.xs4all.nl> <20010720210609.A53370@dragon.nuxi.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20010720210609.A53370@dragon.nuxi.com>, David O'Brien wrote: > On Fri, Jul 20, 2001 at 06:32:29PM +0200, Wilko Bulte wrote: > > I'm probably completely dim today so please bear with me :/ > > Thing is I want to setup a dual-boot box, running -stable & -current. > > This box, a P2/266 has a 30G IDE disk. > > > > What I did is create > > ad0s1 -> 256MB -> holds root for -stable > > ad0s2 -> 256MB -> was supposed to hold root for -current > > ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable > > ad0s4 -> ditto for -current > > You are getting bit by the "root" aliasing code (IIRC this is the right > way to describe the problem). This makes it impossible to install > multiple copies of FreeBSD on a single disk w/o hacking around the > system. :-( > > The way to do this, is 1st install -stable. > Create all four slices in the disk slice editor. In the label editor, do > your normal thing, but don't bother doing anything with ad0s2. Continue > with install as usual. > > Boot again from CDROM or floppies and enter the slice editor. Change the > partition type of ad0s1 from 165 (FreeBSD FFS) to something else. Write > this change to disk and exit from sysinstall. [...] The other way to do it is to install both -current and -stable on the same slice, but in different partitions within the slice. That works even on the Alpha, which doesn't have slices. For example, my dual-boot Alpha is set up like this: da0a / and /usr and /var for -current da0b swap for both -current and -stable da0e /a (user files) for both -current and -stable da0f / and /usr and /var for -stable da0g /c (user files) for both -current and -stable By default this boots into -current. If I want to boot stable, I press a key while the loader's spinner is spinning, and then type: unload set currdev="disk0f" set module_path="/modules" boot /kernel Of course if you want to boot into -stable by default, you can put this into your /boot/loader.conf file: currdev="disk0f" bootfile="/kernel" module_path="/modules" Note, this stuff should go into -current's /boot/loader.conf, because current's loader is used even when booting -stable. You should make sure you arrange things so that the "a" partition holds -current's root filesystem rather than -stable's. The theory here is that -current's loader is more likely to be able to load -stable than vice versa. (This may not matter as much on the i386, but it seems to be important on the Alpha.) (If it seems like I have some minor details wrong in the above, I probably do. Things have been changing fast in -current.) Then you just have to set up your /etc/fstab files right for each system. In my case, -current's looks like this (irrelevant lines omitted): /dev/da0b none swap sw 0 0 /dev/da0a / ufs rw 1 1 /dev/da0f /stable ufs rw 2 2 /dev/da0e /a ufs rw 2 2 /dev/da0g /c ufs rw 2 2 and -stable's looks like this: /dev/da0b none swap sw 0 0 /dev/da0f / ufs rw 1 1 /dev/da0a /current ufs rw 2 2 /dev/da0e /a ufs rw 2 2 /dev/da0g /c ufs rw 2 2 In each case the other system's root filesystem is mounted as "/stable" or "/current" so you can tweak one system from the other. This is particularly handy on the Alpha, where -current periodically falls on its spear and makes a bloody mess. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 13:56:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id A658637B401 for ; Sat, 21 Jul 2001 13:56:25 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f6LKuOJ146848 for ; Sat, 21 Jul 2001 16:56:25 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20010720210609.A53370@dragon.nuxi.com> References: <20010720183229.A9022@freebie.xs4all.nl> <20010720210609.A53370@dragon.nuxi.com> Date: Sat, 21 Jul 2001 16:56:22 -0400 To: freebsd-hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: dual booting -stable & -current Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 9:06 PM -0700 7/20/01, David O'Brien wrote: >The way to do this, is first install -stable. >[...] > >Now install -current in the normal way. >[...] > >You might be able to optimize the number of times booting from >CDROM to change the partition type of ad0s1. It occurs to me that it is actually pretty simple to have two freebsd installs on i386, in two separate slices. The thing a person needs to keep in mind is that at the time of any given attempt to install freebsd, they need to be installing freebsd into the lowest-numbered slice of type freebsd. So let's say you want to set up a disk with just two slices, and some snapshot of freebsd in both slices. For the First install: In the fdisk step, create two dos-style slices. Make slice 0 be of type 'dos', and slice 1 of type freebsd. The disklabel step will ignore slice 0. Create freebsd partitions in slice 1. Finish your complete install. For the second install: in the fdisk step, delete slice 0, and create a new slice 0 which is of type freebsd. the disklabel step will see both slices of type freebsd, and you want to create new freebsd partitions in slice 0. You might want to add mount points for the already-existing partitions in slice 1 (if you want those partitions to be mounted when running this snapshot of freebsd), but do NOT delete them or newfs them! Just set mount points. finish the install. I'm pretty sure that should work fine. The more I think about this strategy, the more I think I'm going to try and rebuild my home machine using it, just to make sure it works the way I think it should. I just need to get back my 4.3-release cd's from the person I lent them to... - - - - - - Things get a little more complicated for the user who wants both freebsd installations to reference partitions in the slice of the alternate freebsd install. If you do want that (as I do), then the best way to get there is probably to FIRST get both the installs done without any cross-references. After both installs are up and running, then go back and fix up /etc/fstab on each install to add the partitions wanted from the alternate installation. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 19:17:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by hub.freebsd.org (Postfix) with ESMTP id 1F46A37B401 for ; Sat, 21 Jul 2001 19:17:31 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: by sharmas.dhs.org (Postfix, from userid 500) id 267E05DD97; Sat, 21 Jul 2001 19:17:47 -0700 (PDT) Date: Sat, 21 Jul 2001 19:17:47 -0700 From: Arun Sharma To: hackers@freebsd.org Subject: libc_r, signals and modifying sigcontext Message-ID: <20010721191747.A32529@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greetings. I'm trying to port an application to FreeBSD. I have a signal handler registered using signal(2). It modifies the data pointed to by the third argument - of type sigcontext (specifically sc_eip) - so that the execution would resume at a different point). However, when execution resumes, it resumes at the same point where it was interrupted. A quick search of the archives brought up this thread: http://groups.google.com/groups?hl=en&safe=off&th=6d5b8c3ead4a79ab,5&seekm=9fo8vq%241ma8%241%40FreeBSD.csie.NCTU.edu.tw#p I tried: _thread_sys_sigreturn(sc); as suggested, but truss shows that sigreturn is failing. So my question is: what is the correct way to modify the sigcontext in FreeBSD ? Are there other multi threaded apps (using pthreads, linked to libc_r), which do this ? -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jul 21 19:56: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by hub.freebsd.org (Postfix) with ESMTP id 8A9C037B405 for ; Sat, 21 Jul 2001 19:56:06 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: by sharmas.dhs.org (Postfix, from userid 500) id 508985DD97; Sat, 21 Jul 2001 19:56:20 -0700 (PDT) Date: Sat, 21 Jul 2001 19:56:20 -0700 From: Arun Sharma To: hackers@freebsd.org Subject: Re: libc_r, signals and modifying sigcontext Message-ID: <20010721195620.A32616@sharmas.dhs.org> References: <20010721191747.A32529@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <20010721191747.A32529@sharmas.dhs.org>; from arun@sharmas.dhs.org on Sat, Jul 21, 2001 at 07:17:47PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Jul 21, 2001 at 07:17:47PM -0700, Arun Sharma wrote: > Greetings. I'm trying to port an application to FreeBSD. I have > a signal handler registered using signal(2). It modifies the > data pointed to by the third argument - of type sigcontext (specifically > sc_eip) - so that the execution would resume at a different point). > > However, when execution resumes, it resumes at the same point where > it was interrupted. A quick search of the archives brought up this > thread: Another data point: the problem doesn't happen with IBM's MxN pthread library ported to FreeBSD (mainly because it uses libc and not libc_r). http://oss.software.ibm.com/developerworks/opensource/pthreads/ I wonder how the scheduler activations based stuff is going to handle this case. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message