From owner-freebsd-current Sun Oct 8 0: 2:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from hun.org (hun.org [216.190.28.252]) by hub.freebsd.org (Postfix) with ESMTP id 5C5C137B503; Sun, 8 Oct 2000 00:02:15 -0700 (PDT) Received: by hun.org (Postfix, from userid 1001) id 04A381C2AB; Sun, 8 Oct 2000 07:02:12 +0000 (GMT) From: attila! X-Organization: hun.org, over 40 years beyond the fringe home for unpenitent hackers and anarcho-cryptophreaks Die-Spammers: Spammers cheerfully broiled and served with Stubbs's "Inferno" Wicked Chicken Wing Sauce Mailer: FreeBSD 5.0-20000925 with XEmacs V21.1.10 (see alt.religion.emacs) Ballistic: N 37.218497 W 113.614979 To: freebsd-current@freebsd.org, freebsd-ports@freebsd.org Subject: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds Message-Id: <20001008070212.04A381C2AB@hun.org> Date: Sun, 8 Oct 2000 07:02:12 +0000 (GMT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- ***************************************************** POSTFIX should be included in /usr/src/contrib freebsd.org and freefall use it... time for an easy choice ***************************************************** (1) 28 Sep: tried installing postfix-current 'pkg' --nogo! Blew sendmail out of the water --repaired.... (2) 28 Sep: tried installing postfix-current 'port' -nogo! Blew sendmail out of the water --repaired... again. (3) 01 Oct: go for good ol' manual compile, from Wietse's tar file! BINGO! (see 'by the numbers' following) However, being of the suspicious type, before compiling, I did grep for possible missing FREEBSD5 definitions --there were two in the util/sys_defs.h file. Having suffered through close to 20 years of configuring sendmail.cf since BSD4.2 first released, I promptly deleted sendmail from my systems.... sorry Eric; m4 has its place, but .cf is not one of them; the syntax sucks, and the whole thing is an unnecessary, condescending mindfsck(1). ************************************************* Fryin' the egg, or doin' the deal by the numbers: ************************************************* Poor man's guide to installing 'Postfix' (a) pick a directory and 'tar -zxf snapshot-20000531.tar.gz' (b) 'cd snapshot-20000531' (c) 'grep FREEBSD */[ch]' showed util/sys_defs.h was missing two FREEBSD5 declarations --modify accordingly. patch for util/sys_defs.h +++ sys_defs.h Fri Oct 6 13:13:16 2000 @@ -47,11 +47,13 @@ #define HAS_ST_GEN /* struct stat contains inode generation number */ #endif - -#if defined(FREEBSD2) || defined(FREEBSD3) || defined(FREEBSD4) +#if defined(FREEBSD2) || defined(FREEBSD3) || defined(FREEBSD4) \ + || defined(FREEBSD5) #define HAS_DUPLEX_PIPE #endif - -#if defined(OPENBSD2) || defined(FREEBSD3) || defined(FREEBSD4) +#if defined(OPENBSD2) || defined(FREEBSD3) || defined(FREEBSD4) \ + || defined(FREEBSD5) #define HAS_ISSETUGID #endif (d) make (do config and create all makefiles) (e) make (again, do the big number) (f) add to /etc/master.passwd (with 'vi_pwd' or execute 'pwd_mkdb' after editing): postfix:*:70:70::0:0:Postfix Owner:/nonexistent:/sbin/nologin check that uid/gid numbers do not conflict with other users (g) add to /etc/groups: postfix:*:70: postdrop:*:72: Check that gid numbers do not conflict. postfix gid must match postfix gid in master.passwd entry. The separate 'postdrop' group is required for the maildrop directory which must not be group owned by postfix itself. -rwxr-sr-x 1 root postdrop 223526 Oct 1 00:35 /usr/sbin/postdrop drwx-wx--T 2 postfix postdrop 512 Oct 6 17:31 /var/spool/postfix/maildrop (h) /usr/tmpdir is required for linking. so as 'root', do 'mkdir /usr/tmpdir && make install' Most questions can be defaulted although I did elect to use the SETUGID maildrop file. I chose/accepted directories: configuration: /etc/postfix/ user programs: /usr/sbin/ daemons: /usr/libexec/postfix/ queue: /var/spool/postfix/ mans: /usr/local/man/ which keeps the concept of mail uniform. Then, as 'root': cd /etc/postfix rm -f aliases* ln -s /etc/aliases aliases ln -s /etc/aliases.db aliases.db I had done the same in /etc/mail for the latest version of sendmail to leave 'aliases' in its historical location as '/etc/aliases' (i) As 'root', execute postfix start which creates the necessary spool directories and behaves like a default sendmail system. The standard '/etc/postfix/main.cf' will use 'gethostname(3)' 'and getdomainname(3)'. Once it starts, check directory permissions, files, etc. postfix check Fix whatever is called out (if anything); then, although I did not find it necessary, it is recommended to: postfix stop postfix start to make sure everything is cleared and updated. (j) Leave sendmail running to flush its queue, or if '/var/spool/mqueue' is empty, kill 'sendmail'. After postfix is installed, 'mailq' only looks at the postfix queue; so: /usr/libexec/sendmail/sendmail -bp will show the old sendmail queue; the original sendmail at this point is only monitoring its own queue. (k) Create or add to file /etc/rc.local # ---- /etc/rc.local ---- # # 0a04 1650 attila create file and add postfix start # # if [ -r /etc/defaults/rc.conf ]; then . /etc/defaults/rc.conf source_rc_confs elif [ -r /etc/rc.conf ]; then . /etc/rc.conf fi case ${postfix_enable} in [Yy][Ee][Ss]) if [ -f /usr/sbin/postfix ]; then echo -n ' postfix'; /usr/sbin/postfix ${postfix_flags} fi ;; esac # # ---- end rc.local ---- (l) disable sendmail in /etc/rc.conf sendmail_enable="NO" (m) enable postfix in /etc/rc.conf postfix_enable="YES" postfix_flags="start" When you reboot, postfix, not sendmail, will be active. (n) If your machine is the end destination with a single name where gethostname(3) == getdomainname(3), the installed /etc/postfix/main.cf file is all you need to run in basic mode. I trimmed /etc/postfix/main.cf to the essentials and added local machine destinations handled on the server. If you are running the machine as the final destination, the defaults basically do it all until you start playing with the filters and the rest of the special goodies in the collection of /etc/postfix/sample.------.cf files plus user contributed code which can be found on: www.postfix.org I changed the 'undisclosed_recipients_header' since the default 'To: undisclosed recipients:;' format is obnoxious and is not accepted by some mail transport agents. The modification does not create a 'To: ' line, but the 'X-Listmgr: lists@hun.org' is included in the header. # ---- /etc/postfix/main.cf ---- # # Global Postfix configuration file: main.cf # # derived from main.cf-original # # 0a02 0400 attila initialize # variables set by INSTALL.sh --also see, but do not change main.cf.default queue_directory = /var/spool/postfix command_directory = /usr/sbin daemon_directory = /usr/libexec/postfix mail_owner = postfix local_destination_concurrency_limit = 2 default_destination_concurrency_limit = 10 debugger_command = PATH=/usr/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5 # variables set by attila (none required for default operation) # # indent continuing lines, do not use '\' # # OBVIOUS: DO NOT USE MY mydestination LINES # IF YOU DO, YOU WILL NOT RECEIVE ANY MAIL (bummer) # but don't worry, it will not be sent to me either, # just bounce, messing up your mailing list subscriptions! debug_peer_level = 1 smtpd_banner = $myhostname ESMTP $mail_name ($mail_version) #undisclosed_recipients_header = X-Listmgr: lists@hun.org #mydestination = hun.org, localhost.hun.org, hun.net, attila.org, # mail.hun.org, www.hun.org, ftp.hun.org, hun10.hun.org, # hun11.hun.org, hun12.hun.org, hun13.hun.org, hun14.hun.org # # ---- end main.cf ---- (o) CAUTION: 'make world' reinstalls 'sendmail' even when NO_SENDMAIL=YES # do not build sendmail and related programs is included in '/etc/make.conf'; 'make world' may not compile sendmail, but it restores the symbolic link during 'make installworld': /usr/sbin/sendmail -> /usr/sbin/mailcap which blows away postfix' 'sendmail' interface. My alternative was: 'cp /usr/sbin/sendmail /usr/sbin/postmail' I had written a two step intermediate mail interface some time ago to eliminate the wait for sendmail to do its thing; so, all that was necessary was to change its target and all user mail programs on this network followed right along. otherwise, modify mail, Mail, Emacs, Pine, whatever to call: /usr/sbin/postmail ---- end ---- -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: latin1 Comment: No safety this side of the grave; never was, never will be iQBFAwUBOeAbia/ciqw+xvOFAQHCZgGAg2AMA/0WOrzbo8kOx6zERvBIgVtRahN2 YkWr4Q/oOgeQXmhi59hD1dAmEA1/f3iC =87j0 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 0:49:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from hun.org (hun.org [216.190.28.252]) by hub.freebsd.org (Postfix) with ESMTP id 0747A37B503 for ; Sun, 8 Oct 2000 00:49:08 -0700 (PDT) Received: by hun.org (Postfix, from userid 1001) id 4DB1E1C2AB; Sun, 8 Oct 2000 07:49:06 +0000 (GMT) From: attila! Organization: hun.org, over 40 years beyond the fringe home for unpenitent hackers and anarcho-cryptophreaks Die-Spammers: Spammers cheerfully broiled and served with Stubbs's "Inferno" Wicked Chicken Wing Sauce Mailer: FreeBSD 5.0-20000925 with XEmacs V21.1.10 (see alt.religion.emacs) Ballistic: N 37.218497 W 113.614979 In-reply-to: <14815.51152.842361.329859@guru.mired.org> To: Mike Meyer Cc: freebsd-current@freebsd.org Subject: re: sio problems? Message-Id: <20001008074906.4DB1E1C2AB@hun.org> Date: Sun, 8 Oct 2000 07:49:06 +0000 (GMT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG on Sat, 7 Oct 2000 20:03:12 -0500 (CDT), Mike Meyer said: > I recently got my digital camera back out, and started pulling the old > pictures from it. I noticed something I hadn't ever seen before - silo > overflows from the sio port. At the moment, I'm wondering if this is a > known problem that is being investigated (SMPNG comes to mind), or > something new. > sio0/irq4 and sio1/irq3 are inactive sio2/irq5 is ppp 121 ?? Ss 4:55.69 /usr/sbin/ppp -quiet -ddial -nat papchap sio2 has also shown 7500+ irq buffer over-flows in 85 hours; this problem predates PRE_SMPNG; I don't remember when exactly since I was having problems with SCSI/da ahc (aic 7880 onboard --ASUS P2L97S-440BX-- driving 2 IBM 68 pin UltraWides) driver stalling with SCB block 6 timeouts which made my -current compiles unusable from roughly 25 Aug until it cleared with a build on 24 Sep after the SMPNG cutover (I am not holding at PRE_SMPNG). Other than the sio irq overflows, which does not seem to particularly impact performance and which I am sure will be solved, I think team has done a superb job with the SMPNG cutover. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 0:51:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from hun.org (hun.org [216.190.28.252]) by hub.freebsd.org (Postfix) with ESMTP id DEC1137B66C for ; Sun, 8 Oct 2000 00:51:21 -0700 (PDT) Received: by hun.org (Postfix, from userid 1001) id 693D71C2AB; Sun, 8 Oct 2000 07:51:20 +0000 (GMT) From: attila! Organization: hun.org, over 40 years beyond the fringe home for unpenitent hackers and anarcho-cryptophreaks Die-Spammers: Spammers cheerfully broiled and served with Stubbs's "Inferno" Wicked Chicken Wing Sauce Mailer: FreeBSD 5.0-20000925 with XEmacs V21.1.10 (see alt.religion.emacs) Ballistic: N 37.218497 W 113.614979 To: freebsd-current@freebsd.org Subject: very high CPU time demand from process #10 ('idle') Message-Id: <20001008075120.693D71C2AB@hun.org> Date: Sun, 8 Oct 2000 07:51:20 +0000 (GMT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- ps -ax -- 0 ?? DLs 0:00.40 (swapper) 1 ?? ILs 0:00.07 /sbin/init -- 2 ?? DL 0:04.23 (pagedaemon) 3 ?? DL 0:00.65 (vmdaemon) 4 ?? DL 0:00.70 (bufdaemon) 5 ?? DL 0:44.85 (syncer) 10 ?? RL 4986:29.70 (idle) 11 ?? WL 5:43.86 (softinterrupt) 12 ?? DL 24:58.44 (random) 13 ?? WL 0:05.88 (irq10: ahc0) 14 ?? WL 0:00.00 (irq11: dc0) 15 ?? WL 0:14.91 (irq1: atkbd0) 16 ?? WL 0:46.60 (irq12: psm0) 17 ?? WL 0:00.00 (irq6: fdc0) 18 ?? WL 0:00.08 (irq7: ppc0) 19 ?? WL 3:19.82 (irq0: clk) 20 ?? RL 5:43.47 (irq8: rtc) What is process 10? Is this literally a representation of the CPU idle time accumulation for the 85 hours since boot? Despite the enormous time burn on 'idle' it does not show on 'top'. -- top -- last pid: 20622; load averages: 0.08, 0.06, 0.02 up 3+13:52:34 07:14:04 69 processes: 1 running, 67 sleeping, 1 zombie CPU states: 0.0% user, 0.0% nice, 1.2% system, 0.0% interrupt, 98.8% idle Mem: 81M Active, 18M Inact, 18M Wired, 4852K Cache, 22M Buf, 1764K Free Swap: 512M Total, 33M Used, 479M Free, 6% Inuse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 2:47:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from dataloss.net (massive.dataloss.net [212.189.232.193]) by hub.freebsd.org (Postfix) with SMTP id 84B6737B502 for ; Sun, 8 Oct 2000 02:47:47 -0700 (PDT) Received: (qmail 7831 invoked by uid 1000); 8 Oct 2000 09:46:47 -0000 Date: Sun, 8 Oct 2000 11:46:47 +0200 From: Peter van Dijk To: freebsd-current@FreeBSD.ORG Subject: Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds Message-ID: <20001008114647.A7756@dataloss.net> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <20001008070212.04A381C2AB@hun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001008070212.04A381C2AB@hun.org>; from attila@hun.org on Sun, Oct 08, 2000 at 07:02:12AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 08, 2000 at 07:02:12AM +0000, attila! wrote: [snip] > > (o) CAUTION: 'make world' reinstalls 'sendmail' even when > > NO_SENDMAIL=YES # do not build sendmail and related programs > > is included in '/etc/make.conf'; 'make world' may not > compile sendmail, but it restores the symbolic link during > 'make installworld': > > /usr/sbin/sendmail -> /usr/sbin/mailcap > > which blows away postfix' 'sendmail' interface. > > My alternative was: > > 'cp /usr/sbin/sendmail /usr/sbin/postmail' > > I had written a two step intermediate mail interface some > time ago to eliminate the wait for sendmail to do its > thing; so, all that was necessary was to change its > target and all user mail programs on this network followed > right along. Actually, mailwrapper (I don't know about this mailcap thing, I'm only running STABLE right now for lack of machines) does this job. Have you looked at /etc/mail/mailer.conf? The sendmail binary in /usr/sbin has no relation to sendmail - it's the mailwrapper, which is a good concept. Otherwise, nice to see such a howto. Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 2:59:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhost.netbenefit.co.uk (mailhost.netbenefit.co.uk [212.53.64.39]) by hub.freebsd.org (Postfix) with ESMTP id C8A7737B66D for ; Sun, 8 Oct 2000 02:59:18 -0700 (PDT) Received: from usercp54.uk.uudial.com ([62.188.156.83] helo=alveley.org) by mailhost.netbenefit.co.uk with esmtp (NetBenefit 1.5) id 13iDEb-0007sg-00 for FreeBSD-current@FreeBSD.org; Sun, 08 Oct 2000 10:59:11 +0100 Message-ID: <39E04566.AA25C074@alveley.org> Date: Sun, 08 Oct 2000 10:59:02 +0100 From: "Dampure, Pierre Y." X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.org Subject: Puzzling 'ps aux' output Content-Type: multipart/mixed; boundary="------------FE5CA51A7B494A342E057D37" X-RBL-Warning: (dul.maps.vix.com) See Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------FE5CA51A7B494A342E057D37 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Just noticed that some of the processes running on my system (-current as of Oct 2) seem to report a startup time in UTC rather than local time (see attached). Is this normal behaviour? [(dampurep)~]: uptime 10:54AM up 41 mins, 2 users, load averages: 0.10, 0.05, 0.01 [(dampurep)~]: uname -a FreeBSD bladerunner.alveley.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Oct 2 08:05:22 BST 2000 toor@bladerunner.alveley.org:/usr/obj/usr/src/sys/BLADERUNNER i386 PYD --------------FE5CA51A7B494A342E057D37 Content-Type: text/plain; charset=us-ascii; name="ps.out" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ps.out" USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 11 80.2 0.0 0 0 ?? RL 11:13AM 24:44.42 (idle: cpu0) root 10 79.1 0.0 0 0 ?? RL 11:13AM 24:44.13 (idle: cpu1) root 19 25.8 0.0 0 0 ?? ML 11:13AM 27:37.72 (irq9: acpi0) root 471 6.4 0.8 4368 4116 p1 S+ 10:43AM 1:14.20 cvsup -g -L 2 -P m -z /etc/src-supfile root 377 1.0 0.6 3700 2920 ?? S 10:20AM 0:12.01 xterm -ls root 15 0.0 0.0 0 0 ?? WL 11:13AM 0:02.01 (irq16: ahc0) root 16 0.0 0.0 0 0 ?? WL 11:13AM 0:00.00 (irq17: pcm0) root 17 0.0 0.0 0 0 ?? WL 11:13AM 0:00.00 (irq14: ata0) root 18 0.0 0.0 0 0 ?? WL 11:13AM 0:00.00 (irq15: ata1) root 2 0.0 0.0 0 0 ?? DL 11:13AM 0:00.00 (acpi) root 20 0.0 0.0 0 0 ?? WL 11:13AM 0:00.31 (irq1: atkbd0) root 21 0.0 0.0 0 0 ?? WL 11:13AM 0:01.98 (irq12: psm0) root 22 0.0 0.0 0 0 ?? WL 11:13AM 0:00.00 (irq6: fdc0) root 23 0.0 0.0 0 0 ?? WL 11:13AM 0:00.00 (irq7: ppc0) root 24 0.0 0.0 0 0 ?? WL 11:13AM 0:10.02 (irq0: clk) root 25 0.0 0.0 0 0 ?? WL 11:13AM 0:09.46 (irq8: rtc) root 3 0.0 0.0 0 0 ?? DL 11:13AM 0:00.01 (pagedaemon) root 4 0.0 0.0 0 0 ?? DL 11:13AM 0:00.00 (vmdaemon) root 5 0.0 0.0 0 0 ?? DL 11:13AM 0:00.05 (bufdaemon) root 6 0.0 0.0 0 0 ?? DL 11:13AM 0:01.04 (syncer) root 52 0.0 50.6 262532 262500 ?? ILs 11:13AM 0:02.82 mfs /dev/da1s1b /tmp (mount_mfs) root 74 0.0 0.0 208 92 ?? Is 11:13AM 0:00.00 adjkerntz -i root 129 0.0 0.1 952 624 ?? Is 10:13AM 0:00.07 syslogd -s daemon 133 0.0 0.1 952 512 ?? Is 10:13AM 0:00.00 /usr/sbin/portmap root 153 0.0 0.2 1076 800 ?? Is 10:13AM 0:00.02 inetd -wW root 155 0.0 0.2 1000 780 ?? Ss 10:13AM 0:00.02 cron root 158 0.0 0.1 960 664 ?? Is 10:13AM 0:00.00 /usr/sbin/lpd root 161 0.0 0.3 1584 1372 ?? Ss 10:13AM 0:00.03 sendmail: accepting connections (sendmail) root 165 0.0 0.3 2156 1376 ?? Is 10:13AM 0:00.65 /usr/sbin/sshd root 213 0.0 0.3 1920 1588 ?? Ss 10:13AM 0:00.19 /usr/local/sbin/httpd pgsql 244 0.0 0.1 724 528 con- I 10:13AM 0:00.00 /bin/sh /usr/local/pgsql/bin/pg_ctl -w start pgsql 245 0.0 0.3 4144 1712 con- I 10:13AM 0:00.03 /usr/local/pgsql/bin/postmaster -i -o -F (postgres) nobody 253 0.0 0.3 1980 1668 ?? I 10:13AM 0:00.01 /usr/local/sbin/httpd nobody 254 0.0 0.3 1980 1668 ?? I 10:13AM 0:00.01 /usr/local/sbin/httpd nobody 255 0.0 0.3 1980 1668 ?? I 10:13AM 0:00.01 /usr/local/sbin/httpd nobody 256 0.0 0.3 1980 1668 ?? I 10:13AM 0:00.01 /usr/local/sbin/httpd nobody 257 0.0 0.3 1980 1668 ?? I 10:13AM 0:00.01 /usr/local/sbin/httpd root 267 0.0 0.3 2892 1460 ?? Is 10:13AM 0:00.06 /usr/X11R6/bin/xdm root 272 0.9 23.6 122912 122372 ?? Ss 10:13AM 0:46.49 /usr/X11R6/bin/X -auth /usr/X11R6/lib/X11/xdm/authdir/authfiles/A:0-SXC267 (XF root 273 0.0 0.1 960 648 v0 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv0 root 274 0.0 0.1 960 652 v1 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv1 root 275 0.0 0.1 960 652 v2 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv2 root 276 0.0 0.1 960 652 v3 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv3 root 277 0.0 0.1 960 652 v4 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv4 root 278 0.0 0.1 960 652 v5 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv5 root 279 0.0 0.1 960 652 v6 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv6 root 280 0.0 0.1 960 652 v7 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv7 root 281 0.0 0.1 960 652 v8 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv8 root 282 0.0 0.1 960 652 v9 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv9 root 283 0.0 0.1 960 652 va Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyva root 284 0.0 0.4 3016 2320 ?? Is 10:13AM 0:00.09 /usr/X11R6/bin/xdm dampurep 297 0.0 0.8 5032 4304 ?? Ss 10:14AM 0:03.50 wmaker dampurep 307 0.0 0.3 2344 1448 ?? S 10:14AM 0:02.28 wmCalClock nobody 324 0.0 0.3 1980 1664 ?? I 10:14AM 0:00.01 /usr/local/sbin/httpd root 329 0.0 0.6 3796 2900 ?? S 10:15AM 0:01.23 xterm -ls -T X Terminal dampurep 330 0.0 0.2 1092 944 p0 Ss 10:15AM 0:00.07 -bash (bash) dampurep 378 0.0 0.2 1096 952 p1 Is 10:20AM 0:00.12 -bash (bash) root 465 0.0 0.2 1096 952 p1 I 10:42AM 0:00.05 -su (bash) root 470 0.0 0.2 1036 864 p1 I+ 10:43AM 0:00.00 /usr/local/bin/bash /usr/local/bin/cvsupdate root 0 0.0 0.0 0 0 ?? DLs 11:13AM 0:00.01 (swapper) dampurep 493 0.0 0.1 560 376 p0 R+ 10:54AM 0:00.00 ps aux root 1 0.0 0.1 556 332 ?? ILs 11:13AM 0:00.01 /sbin/init -- root 12 0.0 0.0 0 0 ?? WL 11:13AM 0:06.20 (softinterrupt) root 13 0.0 0.0 0 0 ?? DL 11:13AM 0:02.99 (random) root 14 0.0 0.0 0 0 ?? WL 11:13AM 0:00.16 (irq19: fxp0) --------------FE5CA51A7B494A342E057D37-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 4:28:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from neo.skynet.be (neo.skynet.be [195.238.2.53]) by hub.freebsd.org (Postfix) with ESMTP id 9F82937B503; Sun, 8 Oct 2000 04:28:03 -0700 (PDT) Received: from [10.0.1.2] (dialup774.brussels2.skynet.be [194.78.236.198]) by neo.skynet.be (Postfix) with ESMTP id C74636D08; Sun, 8 Oct 2000 13:27:21 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20001008070212.04A381C2AB@hun.org> References: <20001008070212.04A381C2AB@hun.org> Date: Sun, 8 Oct 2000 13:14:14 +0200 To: attila! , freebsd-current@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG From: Brad Knowles Subject: Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:02 AM +0000 2000/10/8, attila! wrote: > (a) pick a directory and 'tar -zxf snapshot-20000531.tar.gz' > > (b) 'cd snapshot-20000531' Three things: 1. You don't tell people where to get the postfix software. Start with , and select a mirror site close to you. 2. You mention the use of snapshots, but this is not recommended practice for sites new to postfix. Instead, start with the most recent "release" version, e.g., postfix-19991231-pl09. According to Wietse, the "snapshot" versions are: Work-in-progress code, subject to change, needs testing before it can become an official release. However, these versions are what he runs on his own systems, so it's probably better than the official "production" release version of code from most anyone else. 3. If you want to build postfix with libraries that Wietse does not consider "standard" for your platform, this will take just a bit more work. I have a "MAKEAS" script that I keep at the root of my /usr/local/src/postfix directory structure, and whenever I go to build a new version, I just execute: $ sh ../MAKEAS And it does all the "hard" preparation work for me, which I can then just follow up with a: $ make; sh INSTALL.sh According to the instructions. Currently, my MAKEAS script contains the following (with backslashes to escape the line-breaks I manually added to prevent mis-wrapping): make makefiles CCARGS="-I/usr/local/BerkeleyDB/include \ -DHAS_DB -DPATH_DB_H='' \ -L/usr/local/BerkeleyDB/lib" AUXLIBS="-ldb" \ LDFLAGS="-L/usr/local/BerkeleyDB/lib" LIBS="-ldb" \ SYSLIBS="-ldb" Note that this implies that on this machine I have previously built and installed the Berkeley db 2.7.7 (built with "../dist/configure --enable-compat185", because postfix uses only the db 1.85 interfaces) and BIND 8.2.2-P5 (or whatever the latest version is that you want to install) packages. Note that Berkeley db 3.0 installs in a slightly different directory, and that I've had problems with it causing runtime failures, etc.... Recent snapshot releases have added features for performing simple one line body_check regexp matching (like the older header_check), added support for DSNs, and a new "fast ETRN" feature that will avoid flushing the entire queue when a single site wants mail for them to be flushed (which now makes postfix more suitable for use at an ISP that provides backup MX services for its customers). -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 4:56:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id A0FFB37B502; Sun, 8 Oct 2000 04:56:22 -0700 (PDT) Received: from silvia.hip.berkeley.edu (sji-ca7-112.ix.netcom.com [209.109.235.112]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id HAA07665; Sun, 8 Oct 2000 07:56:19 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.11.0/8.11.0) id e98BuGD84544; Sun, 8 Oct 2000 04:56:16 -0700 (PDT) (envelope-from asami) To: current@FreeBSD.org, stable@FreeBSD.org Subject: Re: cvs commit: CVSROOT avail References: <200010081150.EAA04996@freefall.freebsd.org> From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami) Date: 08 Oct 2000 04:56:13 -0700 In-Reply-To: Satoshi Asami's message of "Sun, 8 Oct 2000 04:50:45 -0700 (PDT)" Message-ID: Lines: 25 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it only took 17 hours. :) I tried my best to be careful but I'm sure there are some ports that broke as a result, so please be gentle! By the way, if you are expecting CVS to suddenly run faster, don't be disappointed by it running as slow as ever. The speedup will only come when the Attics are cleaned (a few months later) by the CVS meisters. -PW === From: Satoshi Asami Date: Sun, 8 Oct 2000 04:50:45 -0700 (PDT) X-FreeBSD-CVS-Branch: HEAD asami 2000/10/08 04:50:45 PDT Modified files: . avail Log: The conversion is over. Revision Changes Path 1.128 +2 -2 CVSROOT/avail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 5: 5:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id B4E5C37B66D for ; Sun, 8 Oct 2000 05:05:33 -0700 (PDT) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id NAA61919 for current@freebsd.org; Sun, 8 Oct 2000 13:05:32 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id NAA84378 for ; Sun, 8 Oct 2000 13:02:33 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 8 Oct 2000 13:02:33 +0100 To: current@freebsd.org From: Bob Bishop Subject: ahc-related panics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm getting repeatable panics with -current, related to ahc. I'm seeing lots of ahc:0:A:0: ahc_intr - referenced scb not valid during seqint 0x71 scb(nn) WARNING no cammand for scb nn (cmdcmplt) plus the WARNING without the other message. Eventually it panics with a kernel-mode page fault, typically either in ahc_set_recoveryscb() in the softinterrupt thread or in ahc_match_scb() in the ahc interrupt thread. This is an SMP box building the world with -j8, so fairly busy. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 5:20:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id BAA8437B503 for ; Sun, 8 Oct 2000 05:20:16 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e98CMCh01218; Sun, 8 Oct 2000 05:22:13 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010081222.e98CMCh01218@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: acpi-jp@jp.freebsd.org Cc: current@freebsd.org Subject: Latest ACPI megapatch update Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Oct 2000 05:22:12 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://people.freebsd.org/~msmith/acpica-bsd-20001008.tar.gz New in this patch: - Fixes for the EC code (error handling) - Fixes for power/sleep button handling (should work for both control method and fixed buttons) - Host:PCI bridges are now detected and attached using ACPI rather than by rummaging in PCI configuration space. (If this fails, we fall back to the old techniques). - Print the current temperature in detected thermal zones (just cosmetic, and reveals that some machines are a bit confused already). Comments, suggestions, bugfixes, etc. welcome as per usual. It looks like we will be switching to this codebase fairly soon (the acpi-jp folks have been discussing this), so anyone with an interest in it is encouraged to tinker. There is a known problem with this code and the Dell Inspiron 7500 (and possibly other laptops with similar BIOS AML) which I'm trying to fix. Don't expect it to work there yet. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 5:24:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id D3B2037B503 for ; Sun, 8 Oct 2000 05:24:19 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id XAA25952; Sun, 8 Oct 2000 23:24:08 +1100 Date: Sun, 8 Oct 2000 23:24:03 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: "Dampure, Pierre Y." Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Puzzling 'ps aux' output In-Reply-To: <39E04566.AA25C074@alveley.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Oct 2000, Dampure, Pierre Y. wrote: > Just noticed that some of the processes running on my system (-current > as of Oct 2) seem to report a startup time in UTC rather than local time > (see attached). Is this normal behaviour? Yes, everything started before adjkerntz has the wrong time because the kernel believed that even the clock was on UTC before adjkerntz adjusted it. This is not a new bug, but it is more obvious now that there are more processes started before adjkerntz. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 6: 7:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 61F9437B502; Sun, 8 Oct 2000 06:07:50 -0700 (PDT) Received: from localhost (go9xe1@localhost [127.0.0.1] (may be forged)) by green.dyndns.org (8.11.0/8.11.0) with ESMTP id e98D7f510854; Sun, 8 Oct 2000 09:07:46 -0400 (EDT) (envelope-from green@FreeBSD.org) Message-Id: <200010081307.e98D7f510854@green.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: attila! Cc: freebsd-current@FreeBSD.org Subject: Re: very high CPU time demand from process #10 ('idle') In-Reply-To: Message from attila! of "Sun, 08 Oct 2000 07:51:20 -0000." <20001008075120.693D71C2AB@hun.org> From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Oct 2000 09:07:41 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG attila! wrote: > What is process 10? Is this literally a representation of > the CPU idle time accumulation for the 85 hours since > boot? Yes. > Despite the enormous time burn on 'idle' it does not show > on 'top'. That's probably because top(1) hides stuff from you by default. Try using top -S. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 6:28: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from volatile.chemicals.tacorp.com (ci391991-a.grnvle1.sc.home.com [24.9.31.75]) by hub.freebsd.org (Postfix) with ESMTP id 5594C37B66C; Sun, 8 Oct 2000 06:28:03 -0700 (PDT) Received: (from morganw@localhost) by volatile.chemicals.tacorp.com (8.11.1/8.11.1) id e98DRxx24417; Sun, 8 Oct 2000 09:27:59 -0400 (EDT) (envelope-from morganw) Date: Sun, 8 Oct 2000 09:27:59 -0400 (EDT) From: Wesley Morgan To: Tony Fleisher Cc: "David O'Brien" , Steve Kargl , FreeBSD Current Subject: Re: make installkernel broken by recent manpage changes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since we are on the subject of installing kernels, i noticed last night that the target "make kernel-install" (not part of world) will cause your modules to be moved into modules.old. It looks like the routine that moved the kernel -> kernel.old was not changed or something like that. Or maybe this is what was intended... But it surely was not what I expected. Shouldnt the tree be pushed over to "old" under different circumstances (like a new module installation, and of course for the install target)? On Sat, 7 Oct 2000, Tony Fleisher wrote: > I just ran through this myself trying to update to newest -current. > I am not exactly sure what caused the breakage (perhaps some > changes inthe share/mk/* files?), nor what the "proper" fix is, > however I was able to get the kernel to install properly by adding > NOMANCOMPRESS=true in the > following Makefiles: > -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ wesleymorgan@home.com _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 8:15: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR8-44.accesscable.net [24.138.8.44]) by hub.freebsd.org (Postfix) with ESMTP id 3DA0937B66C for ; Sun, 8 Oct 2000 08:15:03 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.0) with ESMTP id e98FDfB06047; Sun, 8 Oct 2000 12:13:43 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 8 Oct 2000 12:13:41 -0300 (ADT) From: The Hermit Hacker To: Bob Bishop Cc: current@FreeBSD.ORG Subject: Re: ahc-related panics In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG try the newest cvsup sources ... justin just committed a change that allowed me to get through a 'make buildworld' over here, where I was getting the error listed before previous to it ... On Sun, 8 Oct 2000, Bob Bishop wrote: > Hi, > > I'm getting repeatable panics with -current, related to ahc. I'm seeing lots of > > ahc:0:A:0: ahc_intr - referenced scb not valid during seqint 0x71 scb(nn) > WARNING no cammand for scb nn (cmdcmplt) > > plus the WARNING without the other message. Eventually it panics with a > kernel-mode page fault, typically either in ahc_set_recoveryscb() in the > softinterrupt thread or in ahc_match_scb() in the ahc interrupt thread. > > This is an SMP box building the world with -j8, so fairly busy. > > > -- > Bob Bishop (0118) 977 4017 international code +44 118 > rb@gid.co.uk fax (0118) 989 4254 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 8:56:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [64.20.73.233]) by hub.freebsd.org (Postfix) with ESMTP id 3326437B503 for ; Sun, 8 Oct 2000 08:56:16 -0700 (PDT) Received: from boom.forrie.com (getbent@forrie.ne.mediaone.net [24.147.129.124]) by forrie.net with id e98FuAF24122 for ; Sun, 8 Oct 2000 11:56:10 -0400 (EDT) Message-Id: <4.3.2.7.2.20001008115223.021adcf0@64.20.73.233> X-Sender: forrie@64.20.73.233 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 08 Oct 2000 11:52:55 -0400 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: current.freebsd.org FTP wedged Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI, you get the FTP login prompt, but it hangs thereafter. Looks like something is wedged. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 9:20:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id 5BEA737B502 for ; Sun, 8 Oct 2000 09:20:13 -0700 (PDT) Received: (qmail 85273 invoked by uid 100); 8 Oct 2000 16:20:12 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14816.40636.858363.525382@guru.mired.org> Date: Sun, 8 Oct 2000 11:20:12 -0500 (CDT) To: attila! Cc: freebsd-current@FreeBSD.ORG Subject: re: sio problems? In-Reply-To: <20001008074906.4DB1E1C2AB@hun.org> References: <14815.51152.842361.329859@guru.mired.org> <20001008074906.4DB1E1C2AB@hun.org> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG attila! writes: > on Sat, 7 Oct 2000 20:03:12 -0500 (CDT), Mike Meyer said: > > I recently got my digital camera back out, and started pulling the old > > pictures from it. I noticed something I hadn't ever seen before - silo > > overflows from the sio port. At the moment, I'm wondering if this is a > > known problem that is being investigated (SMPNG comes to mind), or > > something new. > Other than the sio irq overflows, which does not seem to > particularly impact performance and which I am sure will be > solved, I think team has done a superb job with the SMPNG > cutover. Well, it's making a serious impact on performance for camera. I wasn't able to reliably download images at even half speed. I gave up and dropped from 115K to 9.6K. I can probably get better speed than that, but even if it's 28K, that's noticable :-(. On the other hand, that's the only real problem I've seen. Unfortunately, I haven't used the thing since the hardware was cutover from -stable, so I can't pin it down either. ; Sun, 8 Oct 2000 09:53:48 -0700 (PDT) Received: from www.goldendeckcasino.com (adsl-61-143-206.mia.bellsouth.net [208.61.143.206]) by mail1.mia.bellsouth.net (3.3.5alt/0.75.2) with SMTP id MAA26486; Sun, 8 Oct 2000 12:53:32 -0400 (EDT) From: bubblehead32@hotmail.com Message-Id: <200010081653.MAA26486@mail1.mia.bellsouth.net> To: <> Subject: WOW!!! Highest Payouts Around!!!!!!!! Date: Sun, 08 Oct 2000 12:45:38 -0400 X-Sender: bubblehead32@hotmail.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 X-MSMail-Priority: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Its just like being there. Go to www.goldendeckcasino.com/goldendeckcasino/links/2769.html. If you would like to be removed from these mailings in the future please mailto:bubblehead32@hotmail.com?subject=remove To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 9:54:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id C2FAE37B503 for ; Sun, 8 Oct 2000 09:54:38 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id JAA65223 for freebsd-current@FreeBSD.ORG; Sun, 8 Oct 2000 09:54:38 -0700 (PDT) (envelope-from obrien) Date: Sun, 8 Oct 2000 09:54:38 -0700 From: "David O'Brien" To: FreeBSD Current Subject: Re: make installkernel broken by recent manpage changes Message-ID: <20001008095437.A64866@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20001007120510.E73312@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: ; from takhus@takhus.mind.net on Sat, Oct 07, 2000 at 04:40:35PM -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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ===> joy > install -C -c -o root -g wheel -m 555 joy.ko /boot/kernel > install -C -c -o root -g wheel -m 444 joy.8.gz /usr/share/man/man8 > install: joy.8.gz: No such file or directory > *** Error code 71 Since the manpages are being moved elsewhere, I went ahead and removed them from the Makefile's since they were causing problems. -- -- David (obrien@FreeBSD.org) Gnu is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 10:27:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 0E20237B66C for ; Sun, 8 Oct 2000 10:27:20 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e98HRFr24204; Mon, 9 Oct 2000 02:27:16 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: keichii@peorth.iteration.net Cc: rb@gid.co.uk, current@freebsd.org Subject: Re: Recent kernels won't boot In-Reply-To: <20001007195242.C45189@peorth.iteration.net> References: <20001007195242.C45189@peorth.iteration.net> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001009022715Q.iwasaki@jp.FreeBSD.org> Date: Mon, 09 Oct 2000 02:27:15 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 12 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Oct 07, 2000 at 03:30:25PM +0100, Bob Bishop scribbled: > | Kernels built from recent cvsup (<24 hrs) quit immediately on boot, back to > | the BIOS, no messages no nothin'. > > Try removing the ACPI options in kernel and apply Mike Smith's latest > ACPI megapatches. Please also include info on your hardware/BIOS when > your system cannot boot like your situation. I encountered the same problem in opposite condition. I think ACPI is not related with this problem, it was simply kernel size ( >4MB) for me. I removed some device drivers and options from my kernel config then the problem was solved. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 11:24:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 41C3337B502; Sun, 8 Oct 2000 11:24:30 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA00455; Sun, 8 Oct 2000 11:24:24 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id e98IONe30695; Sun, 8 Oct 2000 11:24:23 -0700 (PDT) (envelope-from jdp) Date: Sun, 8 Oct 2000 11:24:23 -0700 (PDT) From: jdp@polstra.com Message-Id: <200010081824.e98IONe30695@vashon.polstra.com> To: current@freebsd.org Reply-To: current@freebsd.org Cc: obrien@freebsd.org Subject: Re: cvs servers load In-Reply-To: <20001007115607.A73312@dragon.nuxi.com> References: <39DF3A3C.B46A3A32@software-munitions.com> <200010071719.e97HJWO29176@vashon.polstra.com> <20001007115607.A73312@dragon.nuxi.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20001007115607.A73312@dragon.nuxi.com>, David O'Brien wrote: > > Where is cvsup8? I get the fastest ping times to it. A traceroute > implies it is also in Seatle, WA. Yes, it's in Seattle too. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 11:27:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 2955037B502 for ; Sun, 8 Oct 2000 11:27:29 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA00471; Sun, 8 Oct 2000 11:27:13 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id e98IRDR30729; Sun, 8 Oct 2000 11:27:13 -0700 (PDT) (envelope-from jdp) Date: Sun, 8 Oct 2000 11:27:13 -0700 (PDT) From: jdp@polstra.com Message-Id: <200010081827.e98IRDR30729@vashon.polstra.com> To: current@freebsd.org Reply-To: current@freebsd.org Cc: wkb@freebie.demon.nl Subject: Re: cvs servers load In-Reply-To: <20001007214439.D93146@freebie.demon.nl> References: <39DF3A3C.B46A3A32@software-munitions.com> <200010071719.e97HJWO29176@vashon.polstra.com> <20001007115607.A73312@dragon.nuxi.com> <20001007214439.D93146@freebie.demon.nl> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20001007214439.D93146@freebie.demon.nl>, Wilko Bulte wrote: > Time to put the cvsup servers on the map with ICBM coordinates > maybe? The US CVSup mirrors are listed by state in the FreeBSD Handbook at http://www.freebsd.org/handbook/cvsup.html#CVSUP-MIRRORS Physical location often doesn't mean much, though. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 12:31:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 9068C37B672; Sun, 8 Oct 2000 12:31:06 -0700 (PDT) Received: by puck.firepipe.net (Postfix, from userid 1000) id 524FD18F7; Sun, 8 Oct 2000 14:31:11 -0500 (EST) Date: Sun, 8 Oct 2000 14:31:11 -0500 From: Will Andrews To: Brad Knowles Cc: attila! , freebsd-current@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds Message-ID: <20001008143111.D539@puck.firepipe.net> Reply-To: Will Andrews References: <20001008070212.04A381C2AB@hun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from blk@skynet.be on Sun, Oct 08, 2000 at 01:14:14PM +0200 X-Operating-System: FreeBSD 4.1-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 08, 2000 at 01:14:14PM +0200, Brad Knowles wrote: > 2. You mention the use of snapshots, but this is not > recommended practice for sites new to postfix. Instead, > start with the most recent "release" version, e.g., > postfix-19991231-pl09. > > According to Wietse, the "snapshot" versions are: > > Work-in-progress code, subject to change, needs > testing before it can become an official release. > > However, these versions are what he runs on his own > systems, so it's probably better than the official > "production" release version of code from most anyone > else. Heh.. Wietse uses so-called ``experimental'' Postfix on his systems. And there are *LOTS* of people who think that whatever Wietse runs is good enough for them.. so this statement had better be hased on personal experience about the actual stability of ``experimental''. -- Will Andrews - Physics Computer Network wench The Universal Answer to All Problems - "It has something to do with physics." -- Comic on door of Room 240, Physics Building, Purdue University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 12:37: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 9139637B502 for ; Sun, 8 Oct 2000 12:37:03 -0700 (PDT) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id UAA65940; Sun, 8 Oct 2000 20:36:15 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id UAA85182; Sun, 8 Oct 2000 20:13:31 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <20001009022715Q.iwasaki@jp.FreeBSD.org> References: <20001007195242.C45189@peorth.iteration.net> <20001007195242.C45189@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 8 Oct 2000 20:13:32 +0100 To: Mitsuru IWASAKI From: Bob Bishop Subject: Re: Recent kernels won't boot Cc: keichii@peorth.iteration.net, current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 02:27 +0900 9/10/00, Mitsuru IWASAKI wrote: >I think ACPI is not related with this problem, it was simply >kernel size ( >4MB) for me. I removed some device drivers and options >from my kernel config then the problem was solved. That was it. Is the 4MB kernel size limit documented anywhere? -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 13: 6:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 5ADAB37B66D for ; Sun, 8 Oct 2000 13:06:18 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13iMi9-000GKM-00 for current@freebsd.org; Sun, 08 Oct 2000 20:06:17 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e98K8MB99105 for current@freebsd.org; Sun, 8 Oct 2000 22:08:22 +0200 (CEST) (envelope-from wkb) Date: Sun, 8 Oct 2000 22:08:22 +0200 From: Wilko Bulte To: current@freebsd.org Subject: Re: cvs servers load Message-ID: <20001008220822.C98882@freebie.demon.nl> References: <39DF3A3C.B46A3A32@software-munitions.com> <200010071719.e97HJWO29176@vashon.polstra.com> <20001007115607.A73312@dragon.nuxi.com> <20001007214439.D93146@freebie.demon.nl> <200010081827.e98IRDR30729@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200010081827.e98IRDR30729@vashon.polstra.com>; from jdp@polstra.com on Sun, Oct 08, 2000 at 11:27:13AM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 08, 2000 at 11:27:13AM -0700, jdp@polstra.com wrote: > In article <20001007214439.D93146@freebie.demon.nl>, Wilko Bulte > wrote: > > > Time to put the cvsup servers on the map with ICBM coordinates > > maybe? > > The US CVSup mirrors are listed by state in the FreeBSD Handbook at > > http://www.freebsd.org/handbook/cvsup.html#CVSUP-MIRRORS > > Physical location often doesn't mean much, though. True, but avoiding intercontinental links is generally advisable. -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 13:11:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from apoq.skynet.be (apoq.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 3BAEB37B681; Sun, 8 Oct 2000 13:11:02 -0700 (PDT) Received: from [10.0.1.2] (dialup1759.brussels.skynet.be [194.78.234.223]) by apoq.skynet.be (Postfix) with ESMTP id C1846992D; Sun, 8 Oct 2000 22:10:57 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20001008143111.D539@puck.firepipe.net> References: <20001008070212.04A381C2AB@hun.org> <20001008143111.D539@puck.firepipe.net> Date: Sun, 8 Oct 2000 22:10:33 +0200 To: Will Andrews From: Brad Knowles Subject: Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds Cc: attila! , freebsd-current@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:31 PM -0500 2000/10/8, Will Andrews wrote: > Heh.. Wietse uses so-called ``experimental'' Postfix on his systems. > And there are *LOTS* of people who think that whatever Wietse runs is > good enough for them.. so this statement had better be hased on personal > experience about the actual stability of ``experimental''. I quoted directly from the postfix web page, when I said that the snapshot versions are: Work-in-progress code, subject to change, needs testing before it can become an official release. I've been involved with postfix since long before it became known by this name, and all during that process, the recommended version that people are encouraged to run is the latest "official release" version. Myself, I run the next-to-latest snapshot version on our production systems, but you'd better be prepared to deal with any problems that may occur if you want to do the same. Otherwise, you shouldn't be running a snapshot version. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 13:40:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3]) by hub.freebsd.org (Postfix) with ESMTP id 717E837B502 for ; Sun, 8 Oct 2000 13:40:53 -0700 (PDT) Received: (from bugs@localhost) by freebsd.netcom.com (8.8.8+Sun/8.8.8) id PAA05628 for freebsd-current@freebsd.org; Sun, 8 Oct 2000 15:41:07 -0500 (CDT) From: Mark Hittinger Message-Id: <200010082041.PAA05628@freebsd.netcom.com> Subject: a.out binaries die in -current recently To: freebsd-current@freebsd.org Date: Sun, 8 Oct 2000 15:41:07 -0500 (CDT) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For the past couple of days the old style binaries don't work under -current, they simply core. FYI Mark Hittinger Earthlink bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 14:22:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from hun.org (hun.org [216.190.28.252]) by hub.freebsd.org (Postfix) with ESMTP id 9950A37B503; Sun, 8 Oct 2000 14:22:48 -0700 (PDT) Received: by hun.org (Postfix, from userid 1001) id 856EF1C2AB; Sun, 8 Oct 2000 21:22:46 +0000 (GMT) From: attila! X-Organization: hun.org, over 40 years beyond the fringe home for unpenitent hackers and anarcho-cryptophreaks X-Die-Spammers: Spammers cheerfully broiled and served with Stubbs's "Inferno" Wicked Chicken Wing Sauce X-Mailer: FreeBSD 5.0-20000925 with XEmacs V21.1.10 (see alt.religion.emacs) X-Ballistic: N 37.218497 W 113.614979 In-Reply-To: References: <20001008143111.D539@puck.firepipe.net>, , <20001008070212.04A381C2AB@hun.org> Cc: Brad Knowles , Will Andrews To: freebsd-current@freebsd.org, freebsd-ports@freebsd.org Subject: Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds Message-Id: <20001008212246.856EF1C2AB@hun.org> Date: Sun, 8 Oct 2000 21:22:46 +0000 (GMT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG on 8 Oct 2000 13:14:14 +0200, Brad Knowles responded: + At 7:02 AM +0000 2000/10/8, attila! wrote: + + > (a) pick a directory and 'tar -zxf snapshot-20000531.tar.gz' + > + > (b) 'cd snapshot-20000531' + + Three things: + + 1. You don't tell people where to get the postfix software. + + Start with , and + select a mirror site close to you. True, I did not; thanx for pointing that out! I already had the code, both from the 'ports' version which did not install correctly, and one I had pulled down. A selection (more at www.postfix.org). ftp://ftp.merit.edu/postfix/experimental/ ftp://ftp.tux.org/pub/net/postfix/experimental/ ftp://ftp.utoronto.ca/mirror/packages/postfix/experimental/ ftp://ftp.samurai.com/pub/postfix/experimental/ ftp://ftp.nl.uu.net/pub/unix/mail/postfix/experimental/ ftp://ftp.cs.tu-berlin.de/pub/net/mail/postfix/experimental/ ftp://ftp.mira.net/pub/unix/mail/postfix/experimental/ ftp://coda.nctu.edu.tw/network/mail/postfix/experimental/ + 2. You mention the use of snapshots, but this is not + recommended practice for sites new to postfix. Instead, + start with the most recent "release" version, e.g., + postfix-19991231-pl09. + + According to Wietse, the "snapshot" versions are: + + Work-in-progress code, subject to change, needs + testing before it can become an official release. + + However, these versions are what he runs on his own + systems, so it's probably better than the official + "production" release version of code from most anyone + else. I look at 'snapshots' philosophically; if I willingly track FreeBSD-5.0-current, I am obviously accustomed to the risks therein. As I mentioned, FreeBSD-current has 'snapshot-20000531' available in both the 'pkg' and 'ports' libraries. Most sites that I am aware of are using the snapshot-50000531 release, and as you point out, Wietse uses it on his site(s), which is more than enough of a recommendation from my perspective. 20000531 also represents a major 'cut-point'. 20001001 is the most current which Wietse is now running and stating that it is 'production quality'. Obviously, I will port 20001001 this afternoon! on Sun, 8 Oct 2000 22:10:33 +0200, Brad Knowles responded: = on 2:31 PM -0500 2000/10/8, Will Andrews wrote: = = > Heh.. Wietse uses so-called ``experimental'' Postfix on his systems. = > And there are *LOTS* of people who think that whatever Wietse runs is = > good enough for them.. so this statement had better be hased on personal = > experience about the actual stability of ``experimental''. = = I quoted directly from the postfix web page, when I said that the = snapshot versions are: = = Work-in-progress code, subject to change, needs testing before = it can become an official release. = = I've been involved with postfix since long before it became known = by this name, and all during that process, the recommended version = that people are encouraged to run is the latest "official release" = version. = = Myself, I run the next-to-latest snapshot version on our = production systems, but you'd better be prepared to deal with any = problems that may occur if you want to do the same. Otherwise, you = shouldn't be running a snapshot version. not only good advice, but mandatory... however, I may be a little crazier as I will port the _latest_ version this afternoon! Nothing ventured, nothing gained. on 8 Oct 2000 13:14:14 +0200, Brad Knowles responded: (cont) + 3. [re: non-standard dbm libraries and MAKEAS] + + [snip] + Berkeley db 2.7.7 (built with "../dist/configure + --enable-compat185", because postfix uses only the db 1.85 + interfaces) + [snip] Why not consider the use of the mysql interface which provides dynamic aliasing? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 17:37:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from hun.org (hun.org [216.190.28.252]) by hub.freebsd.org (Postfix) with ESMTP id F17F337B502 for ; Sun, 8 Oct 2000 17:37:32 -0700 (PDT) Received: by hun.org (Postfix, from userid 1001) id A75DA1C2AB; Mon, 9 Oct 2000 00:37:30 +0000 (GMT) From: attila! X-Organization: hun.org, over 40 years beyond the fringe home for unpenitent hackers and anarcho-cryptophreaks X-Die-Spammers: Spammers cheerfully broiled and served with Stubbs's "Inferno" Wicked Chicken Wing Sauce X-Mailer: FreeBSD 5.0-20000925 with XEmacs V21.1.10 (see alt.religion.emacs) X-Ballistic: N 37.218497 W 113.614979 In-Reply-To: <20001008114647.A7756@dataloss.net> References: <20001008070212.04A381C2AB@hun.org> To: Peter van Dijk Cc: freebsd-current@FreeBSD.ORG Subject: Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds Message-Id: <20001009003730.A75DA1C2AB@hun.org> Date: Mon, 9 Oct 2000 00:37:30 +0000 (GMT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- on Sun, 8 Oct 2000 11:46:47 +0200, Peter van Dijk said: > Actually, mailwrapper (I don't know about this mailcap thing, > I'm only running STABLE right now for lack of machines) does > this job. Have you looked at /etc/mail/mailer.conf? The sendmail > binary in /usr/sbin has no relation to sendmail - it's the > mailwrapper, which is a good concept. What needs to be considered, in maintaining postfix for the 'conventional' interface of sendmail (as of 8.10) is: /usr/bin/mailq -> /usr/sbin/sendmail /usr/bin/newaliases -> /usr/sbin/sendmail /usr/sbin/sendmail -> /usr/sbin/mailwrapper and, given that Wietse's /usr/bin/sendmail does essentially the same thing as sendmail's /usr/sbin/mailwrapper except that it is based on the declarations in /etc/postfix/main.cf rather than /etc/mail/mailer.conf, it seems the probable 'sane' solution is to install Wietse's 'sendmail' as /usr/sbin/postmail (which I have done) and use the soft links: /usr/bin/mailq -> /usr/sbin/sendmail /usr/bin/newaliases -> /usr/sbin/sendmail /usr/sbin/sendmail -> /usr/sbin/postmail which I have now done on my network. Then, if 'installworld' tramples /usr/sbin/sendmail, it only means changing the symbolic link; meanwhile, no-one needs to put the intermediate spooler in that I use (unless they want to play double safe). Secondly, I am quite comfortable with postfix, having ported it in for about 18 months --not as long as Brad Knowles, but long enough. Wietse writes good, clean, and organized code! I plan to communicate same to Wietse along with the patch file for 'src/util/sys_defs.h' and see what happens; it's his program. > Otherwise, nice to see such a howto. Thank you; I will refine it out, plus get it ready for inclusion in the /usr/src/contrib tree if so permitted. I am a firm believer in KISS for the unwashed, and will therefore establish the initial configuration with defaults to eliminate the questions in the install script. I am perfectly well willing to maintain it in cvs format. attila out... -- M$ -Where do you want to go today? Linux -Where do you want to go tomorrow? Freebsd -Are you guys coming or what? If you don't understand or are scared by any of the above, ask your parents or an adult to help you. -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: latin1 Comment: No safety this side of the grave; never was, never will be iQBFAwUBOeES3q/ciqw+xvOFAQETBAF/Y8nGb60iopT70u4XU1NdTUWuGYw3SNBi ADOM5A/d83mcS7+CQkg+RrvvMTSXoZiH =d3yh -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 18:10:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 085B037B66C for ; Sun, 8 Oct 2000 18:10:53 -0700 (PDT) Received: (from kris@localhost) by citusc17.usc.edu (8.9.3/8.9.3) id SAA36843; Sun, 8 Oct 2000 18:11:25 -0700 (PDT) Date: Sun, 8 Oct 2000 18:11:25 -0700 From: Kris Kennaway To: Mike Meyer Cc: current@FreeBSD.ORG Subject: Re: sio problems? Message-ID: <20001008181125.A36812@citusc17.usc.edu> References: <14815.51152.842361.329859@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14815.51152.842361.329859@guru.mired.org>; from mwm@mired.org on Sat, Oct 07, 2000 at 08:03:12PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 07, 2000 at 08:03:12PM -0500, Mike Meyer wrote: > I recently got my digital camera back out, and started pulling the old > pictures from it. I noticed something I hadn't ever seen before - silo > overflows from the sio port. At the moment, I'm wondering if this is a > known problem that is being investigated (SMPNG comes to mind), or > something new. The sio device doesnt work well at high speed because of the recent SMPng changes. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 18:18:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.gplsucks.org (mail.gplsucks.org [63.227.213.93]) by hub.freebsd.org (Postfix) with ESMTP id 86EED37B502 for ; Sun, 8 Oct 2000 18:18:21 -0700 (PDT) Received: from localhost (bwoods2@localhost) by mail.gplsucks.org (8.11.1/8.11.1) with ESMTP id e991IUd52900 for ; Sun, 8 Oct 2000 18:18:30 -0700 (PDT) Date: Sun, 8 Oct 2000 18:18:29 -0700 (PDT) From: Bill Woods mail To: freebsd-current@freebsd.org Subject: current.freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG whats up with current.freebsd.org, its not allowing anon ftp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 18:44:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id D693237B66C for ; Sun, 8 Oct 2000 18:44:03 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id VAA03526; Sun, 8 Oct 2000 21:43:01 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Sun, 8 Oct 2000 21:43:01 -0400 (EDT) From: "Brandon D. Valentine" To: attila! Cc: Peter van Dijk , freebsd-current@FreeBSD.ORG Subject: Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds In-Reply-To: <20001009003730.A75DA1C2AB@hun.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Oct 2000, attila! wrote: > Thank you; I will refine it out, plus get it ready for > inclusion in the /usr/src/contrib tree if so permitted. I > am a firm believer in KISS for the unwashed, and will > therefore establish the initial configuration with defaults > to eliminate the questions in the install script. > > I am perfectly well willing to maintain it in cvs format. You and a million other crusaders. Sorry to rain on your parade but what you're discussing borders on a religious jihad. Were we all not already tired of the endless flamefests that spawn from every discussion concerning the MTA in the base system, I'm sure you would have a mailbox full of flames by now. If you go look through the archives you will find countless threads waging the sendmail vs. qmail vs. postfix vs. exim vs. "i wrote this simple mailer last week..." war. The fact of the matter remains that it will take an event of astronomical proportions to finally reach a consensus on that issue. Quite frankly, if you prepare postfix for inclusion in the contrib tree your time will be completely wasted. Sendmail is there, works, and is being actively maintained by a member of the actual sendmail team. That's far more than can be said for other parts of the contrib tree and if you'd like to help out I'm sure there are other areas that need more attention. I'm save you the frustration now, please, don't waste your time. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 18:57: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from veldy.net (w028.z064001117.msp-mn.dsl.cnc.net [64.1.117.28]) by hub.freebsd.org (Postfix) with ESMTP id 0F4CE37B502 for ; Sun, 8 Oct 2000 18:57:04 -0700 (PDT) Received: from cascade (cascade.veldy.net [192.168.0.1]) by veldy.net (Postfix) with SMTP id 569E58C2C; Sun, 8 Oct 2000 20:58:03 -0500 (CDT) Message-ID: <002101c03194$092d79f0$0100a8c0@cascade> From: "Thomas T. Veldhouse" To: "Bill Woods mail" , "FreeBSD-Current, " References: Subject: Re: current.freebsd.org Date: Sun, 8 Oct 2000 20:55:44 -0500 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And releng4.freebsd.org is totally missing from the Internet. I suppose they are having another hardware problem again? Seems FreeBSD is a bit tough on hardware these days. Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "Bill Woods mail" To: Sent: Sunday, October 08, 2000 8:18 PM Subject: current.freebsd.org > whats up with current.freebsd.org, its not allowing anon ftp > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 19:13:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.gplsucks.org (mail.gplsucks.org [63.227.213.93]) by hub.freebsd.org (Postfix) with ESMTP id 40E5637B502 for ; Sun, 8 Oct 2000 19:13:52 -0700 (PDT) Received: from localhost (bwoods2@localhost) by mail.gplsucks.org (8.11.1/8.11.1) with ESMTP id e992Dv157280; Sun, 8 Oct 2000 19:13:57 -0700 (PDT) Date: Sun, 8 Oct 2000 19:13:56 -0700 (PDT) From: Bill Woods mail To: "Thomas T. Veldhouse" Cc: Bill Woods mail , " FreeBSD-Current," Subject: Re: current.freebsd.org In-Reply-To: <002101c03194$092d79f0$0100a8c0@cascade> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yea, guess so, but I cant help but notice this started after the buyout by BSDI........ On Sun, 8 Oct 2000, Thomas T. Veldhouse wrote: > And releng4.freebsd.org is totally missing from the Internet. I suppose > they are having another hardware problem again? Seems FreeBSD is a bit tough > on hardware these days. > > Tom Veldhouse > veldy@veldy.net > > ----- Original Message ----- > From: "Bill Woods mail" > To: > Sent: Sunday, October 08, 2000 8:18 PM > Subject: current.freebsd.org > > > > whats up with current.freebsd.org, its not allowing anon ftp > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 19:20: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 5A57637B66C for ; Sun, 8 Oct 2000 19:20:04 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id DC4391C6B; Sun, 8 Oct 2000 22:20:03 -0400 (EDT) Date: Sun, 8 Oct 2000 22:20:03 -0400 From: Bill Fumerola To: Bill Woods mail Cc: "Thomas T. Veldhouse" , " FreeBSD-Current," Subject: Re: current.freebsd.org Message-ID: <20001008222003.C38472@jade.chc-chimes.com> References: <002101c03194$092d79f0$0100a8c0@cascade> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bwoods2@uswest.net on Sun, Oct 08, 2000 at 07:13:56PM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 08, 2000 at 07:13:56PM -0700, Bill Woods mail wrote: > Yea, guess so, but I cant help but notice this started after the buyout by > BSDI........ The clue boat left the docks and you were standing on the pier. Might I suggest a long walk... -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 19:21:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 7F7CC37B66C for ; Sun, 8 Oct 2000 19:21:18 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e992NEh03297; Sun, 8 Oct 2000 19:23:14 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010090223.e992NEh03297@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bill Woods mail Cc: "Thomas T. Veldhouse" , " FreeBSD-Current, " Subject: Re: current.freebsd.org In-reply-to: Your message of "Sun, 08 Oct 2000 19:13:56 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Oct 2000 19:23:14 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yea, guess so, but I cant help but notice this started after the buyout by > BSDI........ Uh, folks, releng4 is hosted at (and donated by) Yahoo, and BSDi have exactly *nothing* to do with its availability or otherwise. Before making absurd allegations like this, please apply a few neurons to the task. Note also that you're insulting those of us that choose to work for BSDi in the name of FreeBSD; not really the brighest of things to do. > On Sun, 8 Oct 2000, Thomas T. Veldhouse wrote: > > > And releng4.freebsd.org is totally missing from the Internet. I suppose > > they are having another hardware problem again? Seems FreeBSD is a bit tough > > on hardware these days. > > > > Tom Veldhouse > > veldy@veldy.net > > > > ----- Original Message ----- > > From: "Bill Woods mail" > > To: > > Sent: Sunday, October 08, 2000 8:18 PM > > Subject: current.freebsd.org > > > > > > > whats up with current.freebsd.org, its not allowing anon ftp > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" 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-current" in the body of the message From owner-freebsd-current Sun Oct 8 21:38:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41]) by hub.freebsd.org (Postfix) with ESMTP id 1D3CE37B503; Sun, 8 Oct 2000 21:38:14 -0700 (PDT) Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net) by dfw-smtpout1.email.verio.net with esmtp (Exim 3.12 #7) id 13iUhZ-0004do-00; Mon, 09 Oct 2000 04:38:13 +0000 Received: from [204.1.90.43] (helo=power) by dfw-mmp3.email.verio.net with smtp (Exim 3.161 #1) id 13iUhZ-0004ID-00; Mon, 09 Oct 2000 04:38:13 +0000 From: "Tony Johnson" To: "Mike Smith" , "Bill Woods mail" Cc: "Thomas T. Veldhouse" , " FreeBSD-Current, " Subject: RE: current.freebsd.org Date: Sun, 8 Oct 2000 23:38:11 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <200010090223.e992NEh03297@mass.osd.bsdi.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was downloading 1007 this weekend and getting 7-8k a second from current.freebsd.org. What they are saying is not totally inaccurate. Please stop dis-respecting other peoples comments just because you do not agree with them! What is your comment to this... Microsoft Windows 2000 [Version 5.00.2195] (C) Copyright 1985-2000 Microsoft Corp. D:\>ping releng4.freebsd.org Pinging usw3.FreeBSD.org [209.180.6.227] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 209.180.6.227: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms D:\> From my Sun Box... SunOS 5.8 login: gjohnson Password: Last login: Wed Sep 27 18:00:31 from adsl-204-1-90-43 bash-2.04$ ping releng4.freebsd.org no answer from releng4.freebsd.org bash-2.04$ I don't think they have anything to do with hte cabling of relen4... -----Original Message----- From: owner-freebsd-current@FreeBSD.ORG [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Mike Smith Sent: Sunday, October 08, 2000 9:23 PM To: Bill Woods mail Cc: Thomas T. Veldhouse; FreeBSD-Current, Subject: Re: current.freebsd.org > Yea, guess so, but I cant help but notice this started after the buyout by > BSDI........ Uh, folks, releng4 is hosted at (and donated by) Yahoo, and BSDi have exactly *nothing* to do with its availability or otherwise. Before making absurd allegations like this, please apply a few neurons to the task. Note also that you're insulting those of us that choose to work for BSDi in the name of FreeBSD; not really the brighest of things to do. > On Sun, 8 Oct 2000, Thomas T. Veldhouse wrote: > > > And releng4.freebsd.org is totally missing from the Internet. I suppose > > they are having another hardware problem again? Seems FreeBSD is a bit tough > > on hardware these days. > > > > Tom Veldhouse > > veldy@veldy.net > > > > ----- Original Message ----- > > From: "Bill Woods mail" > > To: > > Sent: Sunday, October 08, 2000 8:18 PM > > Subject: current.freebsd.org > > > > > > > whats up with current.freebsd.org, its not allowing anon ftp > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" 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-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 22:20: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3721337B502; Sun, 8 Oct 2000 22:20:04 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e995K1N19959; Sun, 8 Oct 2000 22:20:01 -0700 (PDT) Date: Sun, 8 Oct 2000 22:20:00 -0700 From: Alfred Perlstein To: Tony Johnson Cc: Mike Smith , Bill Woods mail , "Thomas T. Veldhouse" , " FreeBSD-Current, " Subject: Re: current.freebsd.org Message-ID: <20001008222000.K272@fw.wintelcom.net> References: <200010090223.e992NEh03297@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from gjohnson@gs.verio.net on Sun, Oct 08, 2000 at 11:38:11PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please get mailer that doesn't quote the messages you're replying to in such a brain dead manner. * Mike Smith wrote: > > Uh, folks, releng4 is hosted at (and donated by) Yahoo, and BSDi have > exactly *nothing* to do with its availability or otherwise. > > Before making absurd allegations like this, please apply a few neurons to > the task. Note also that you're insulting those of us that choose to > work for BSDi in the name of FreeBSD; not really the brighest of things > to do. * Tony Johnson [001008 21:38] wrote: > I was downloading 1007 this weekend and getting 7-8k a second from > current.freebsd.org. What they are saying is not totally inaccurate. > > Please stop dis-respecting other peoples comments just because you do not > agree with them! What is your comment to this... [snip] My comment would be: "you just don't get it" People are not disputing that services may have been down. People _are_ disputing that these services being down has any political agenda regarding various partnerships that the FreeBSD project has made, collabiration with BSDi, Yahoo or martians from area 51. They're requesting that people stop blowing smoke and spreading rumor, innuendo and FUD. Machines go down, networks go down, deal with it! thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 22:33:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id BC96D37B503 for ; Sun, 8 Oct 2000 22:33:45 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e995WrX00585; Sun, 8 Oct 2000 22:32:54 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Bill Woods mail Cc: "Thomas T. Veldhouse" , " FreeBSD-Current, " Subject: Re: current.freebsd.org In-Reply-To: Message from Bill Woods mail of "Sun, 08 Oct 2000 19:13:56 PDT." Date: Sun, 08 Oct 2000 22:32:53 -0700 Message-ID: <581.971069573@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sorry, but BSDi's dead-alien based UPS (as described in that fine documentary film "repo man") has been unreliable lately and the machines haven't been staying up. We've also been forced by the silicon valley personnel crunch to hire a new system administrator who's a little strange (he refers to himself as "Elvis Preston" and makes odd little hip-thrusts at the system rack when he thinks nobody is looking) and frequently missing, so the machines don't always get rebooted properly when the DABUPS comes back up. We regret the inconvenience, etc etc. - Jordan P.S. Unbelievers also claim that both releng4.freebsd.org and current.freebsd.org are actually at USWest and totally outside the realm of BSDi's control, but you can't put too much trust in what they say. > Yea, guess so, but I cant help but notice this started after the buyout by > BSDI........ > > > > On Sun, 8 Oct 2000, Thomas T. Veldhouse wrote: > > > And releng4.freebsd.org is totally missing from the Internet. I suppose > > they are having another hardware problem again? Seems FreeBSD is a bit toug h > > on hardware these days. > > > > Tom Veldhouse > > veldy@veldy.net > > > > ----- Original Message ----- > > From: "Bill Woods mail" > > To: > > Sent: Sunday, October 08, 2000 8:18 PM > > Subject: current.freebsd.org > > > > > > > whats up with current.freebsd.org, its not allowing anon ftp > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 22:36:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from dfw-smtpout4.email.verio.net (dfw-smtpout4.email.verio.net [129.250.36.44]) by hub.freebsd.org (Postfix) with ESMTP id 79F7237B66C; Sun, 8 Oct 2000 22:36:00 -0700 (PDT) Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net) by dfw-smtpout4.email.verio.net with esmtp (Exim 3.12 #7) id 13iVbT-0006Wx-00; Mon, 09 Oct 2000 05:35:59 +0000 Received: from [204.1.90.43] (helo=power) by dfw-mmp3.email.verio.net with smtp (Exim 3.161 #1) id 13iVbT-0005yF-00; Mon, 09 Oct 2000 05:35:59 +0000 From: "Tony Johnson" To: "Alfred Perlstein" Cc: "Mike Smith" , "Bill Woods mail" , "Thomas T. Veldhouse" , " FreeBSD-Current, " Subject: RE: current.freebsd.org Date: Mon, 9 Oct 2000 00:35:58 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20001008222000.K272@fw.wintelcom.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wow. Is it just me or does FreeBSD like to point fingers at everything that is not the issue. I do not believe that my mailer has anything to do with this. If you cannot roll with the punches, then that is your problem. Well deal with it and get releng4 back up. if "piss off" is an exceptable answer here, then I'd like for u to say so. Obviously "You do not get it" -----Original Message----- From: Alfred Perlstein [mailto:bright@wintelcom.net] Sent: Monday, October 09, 2000 12:20 AM To: Tony Johnson Cc: Mike Smith; Bill Woods mail; Thomas T. Veldhouse; FreeBSD-Current, Subject: Re: current.freebsd.org Please get mailer that doesn't quote the messages you're replying to in such a brain dead manner. * Mike Smith wrote: > > Uh, folks, releng4 is hosted at (and donated by) Yahoo, and BSDi have > exactly *nothing* to do with its availability or otherwise. > > Before making absurd allegations like this, please apply a few neurons to > the task. Note also that you're insulting those of us that choose to > work for BSDi in the name of FreeBSD; not really the brighest of things > to do. * Tony Johnson [001008 21:38] wrote: > I was downloading 1007 this weekend and getting 7-8k a second from > current.freebsd.org. What they are saying is not totally inaccurate. > > Please stop dis-respecting other peoples comments just because you do not > agree with them! What is your comment to this... [snip] My comment would be: "you just don't get it" People are not disputing that services may have been down. People _are_ disputing that these services being down has any political agenda regarding various partnerships that the FreeBSD project has made, collabiration with BSDi, Yahoo or martians from area 51. They're requesting that people stop blowing smoke and spreading rumor, innuendo and FUD. Machines go down, networks go down, deal with it! thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 22:42:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 197FA37B503; Sun, 8 Oct 2000 22:42:23 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e995g8X00655; Sun, 8 Oct 2000 22:42:08 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: "Tony Johnson" Cc: "Alfred Perlstein" , "Mike Smith" , "Bill Woods mail" , "Thomas T. Veldhouse" , " FreeBSD-Current, " Subject: Re: current.freebsd.org In-Reply-To: Message from "Tony Johnson" of "Mon, 09 Oct 2000 00:35:58 CDT." Date: Sun, 08 Oct 2000 22:42:07 -0700 Message-ID: <651.971070127@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well deal with it and get releng4 back up. That reminds me of a joke: Q. "What do engineers use for birth control?" A. "Their personalities." We now return you to our regularly scheduled content-free discussion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 22:45:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from dfw-smtpout3.email.verio.net (dfw-smtpout3.email.verio.net [129.250.36.43]) by hub.freebsd.org (Postfix) with ESMTP id E403937B502 for ; Sun, 8 Oct 2000 22:45:11 -0700 (PDT) Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net) by dfw-smtpout3.email.verio.net with esmtp (Exim 3.12 #7) id 13iVkM-0003MU-00; Mon, 09 Oct 2000 05:45:10 +0000 Received: from [204.1.90.43] (helo=power) by dfw-mmp3.email.verio.net with smtp (Exim 3.161 #1) id 13iVkL-00067c-00; Mon, 09 Oct 2000 05:45:09 +0000 From: "Tony Johnson" To: "Jordan Hubbard" , "Bill Woods mail" Cc: "Thomas T. Veldhouse" , " FreeBSD-Current, " Subject: RE: current.freebsd.org Date: Mon, 9 Oct 2000 00:45:08 -0500 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.2911.0) In-Reply-To: <581.971069573@winston.osd.bsdi.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard. I just want to say publicly that since I have been cvsup-ing Freebsd 3.0-Current (with this when the SMP/CAM code came out.) I just want to apologize to you since cooler heads prevail. Peace bro -----Original Message----- From: owner-freebsd-current@FreeBSD.ORG [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Jordan Hubbard Sent: Monday, October 09, 2000 12:33 AM To: Bill Woods mail Cc: Thomas T. Veldhouse; FreeBSD-Current, Subject: Re: current.freebsd.org I'm sorry, but BSDi's dead-alien based UPS (as described in that fine documentary film "repo man") has been unreliable lately and the machines haven't been staying up. We've also been forced by the silicon valley personnel crunch to hire a new system administrator who's a little strange (he refers to himself as "Elvis Preston" and makes odd little hip-thrusts at the system rack when he thinks nobody is looking) and frequently missing, so the machines don't always get rebooted properly when the DABUPS comes back up. We regret the inconvenience, etc etc. - Jordan P.S. Unbelievers also claim that both releng4.freebsd.org and current.freebsd.org are actually at USWest and totally outside the realm of BSDi's control, but you can't put too much trust in what they say. > Yea, guess so, but I cant help but notice this started after the buyout by > BSDI........ > > > > On Sun, 8 Oct 2000, Thomas T. Veldhouse wrote: > > > And releng4.freebsd.org is totally missing from the Internet. I suppose > > they are having another hardware problem again? Seems FreeBSD is a bit toug h > > on hardware these days. > > > > Tom Veldhouse > > veldy@veldy.net > > > > ----- Original Message ----- > > From: "Bill Woods mail" > > To: > > Sent: Sunday, October 08, 2000 8:18 PM > > Subject: current.freebsd.org > > > > > > > whats up with current.freebsd.org, its not allowing anon ftp > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 22:56:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 0C7AF37B502; Sun, 8 Oct 2000 22:56:49 -0700 (PDT) Received: from gorean.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id WAA70233; Sun, 8 Oct 2000 22:56:42 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39E15E1A.BC21F4AF@gorean.org> Date: Sun, 08 Oct 2000 22:56:42 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT-100 i386) X-Accept-Language: en MIME-Version: 1.0 To: phk@freebsd.org, current@freebsd.org Subject: src/sys/dev/syscons/scvesactl.c broken Content-Type: multipart/mixed; boundary="------------91719CB7ABAA29632FCADCE8" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------91719CB7ABAA29632FCADCE8 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Version 1.16 of src/sys/dev/syscons/scvesactl.c, removing broke the kernel build for me. Attached is the relevant log, and my kernel file. Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? --------------91719CB7ABAA29632FCADCE8 Content-Type: text/plain; charset=us-ascii; name="kernel.build" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="kernel.build" cc -c -O -march=pentiumpro -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/syscons/scvesactl.c In file included from ../../dev/syscons/scvesactl.c:41: ../../dev/fb/fbreg.h:57: syntax error before `video_adapter_t' ../../dev/fb/fbreg.h:57: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:58: syntax error before `video_adapter_t' ../../dev/fb/fbreg.h:58: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:59: syntax error before `*' ../../dev/fb/fbreg.h:59: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:60: syntax error before `*' ../../dev/fb/fbreg.h:60: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:61: syntax error before `*' ../../dev/fb/fbreg.h:61: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:62: syntax error before `*' ../../dev/fb/fbreg.h:63: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:64: syntax error before `*' ../../dev/fb/fbreg.h:65: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:66: syntax error before `*' ../../dev/fb/fbreg.h:66: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:67: syntax error before `*' ../../dev/fb/fbreg.h:67: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:68: syntax error before `*' ../../dev/fb/fbreg.h:68: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:69: syntax error before `*' ../../dev/fb/fbreg.h:69: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:70: syntax error before `*' ../../dev/fb/fbreg.h:70: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:71: syntax error before `*' ../../dev/fb/fbreg.h:71: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:72: syntax error before `*' ../../dev/fb/fbreg.h:72: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:73: syntax error before `*' ../../dev/fb/fbreg.h:73: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:74: syntax error before `*' ../../dev/fb/fbreg.h:74: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:75: syntax error before `*' ../../dev/fb/fbreg.h:76: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:77: syntax error before `*' ../../dev/fb/fbreg.h:77: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:82: syntax error before `*' ../../dev/fb/fbreg.h:82: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:83: syntax error before `*' ../../dev/fb/fbreg.h:83: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:84: syntax error before `*' ../../dev/fb/fbreg.h:84: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:85: syntax error before `*' ../../dev/fb/fbreg.h:86: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:87: syntax error before `*' ../../dev/fb/fbreg.h:87: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:88: syntax error before `*' ../../dev/fb/fbreg.h:88: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:154: syntax error before `*' ../../dev/fb/fbreg.h:154: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:155: syntax error before `*' ../../dev/fb/fbreg.h:155: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:157: syntax error before `*' ../../dev/fb/fbreg.h:158: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:162: syntax error before `*' ../../dev/fb/fbreg.h:162: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:164: syntax error before `*' ../../dev/fb/fbreg.h:164: warning: type defaults to `int' in declaration of `vid_get_adapter' ../../dev/fb/fbreg.h:164: warning: data definition has no type or storage class ../../dev/fb/fbreg.h:202: syntax error before `video_adapter_t' ../../dev/fb/fbreg.h:202: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:203: syntax error before `video_adapter_t' ../../dev/fb/fbreg.h:204: warning: function declaration isn't a prototype ../../dev/fb/fbreg.h:206: syntax error before `*' ../../dev/fb/fbreg.h:206: warning: function declaration isn't a prototype In file included from ../../dev/syscons/scvesactl.c:42: ../../dev/syscons/syscons.h:278: field `smode' has incomplete type ../../dev/syscons/syscons.h:607: syntax error before `*' ../../dev/syscons/syscons.h:607: warning: function declaration isn't a prototype ../../dev/syscons/scvesactl.c: In function `vesa_ioctl': ../../dev/syscons/scvesactl.c:61: `SW_TEXT_132x25' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:61: (Each undeclared identifier is reported only once ../../dev/syscons/scvesactl.c:61: for each function it appears in.) ../../dev/syscons/scvesactl.c:61: `SW_TEXT_132x30' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:62: `SW_TEXT_132x43' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:62: `SW_TEXT_132x50' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:63: `SW_TEXT_132x60' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:64: dereferencing pointer to incomplete type ../../dev/syscons/scvesactl.c:64: `V_ADP_MODECHANGE' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:69: `SW_VESA_C80x60' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:70: `SW_VESA_C132x25' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:71: `SW_VESA_C132x43' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:72: `SW_VESA_C132x50' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:73: `SW_VESA_C132x60' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:74: dereferencing pointer to incomplete type ../../dev/syscons/scvesactl.c:76: `M_VESA_BASE' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:80: `SW_VESA_32K_320' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:80: `SW_VESA_64K_320' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:81: `SW_VESA_FULL_320' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:83: `SW_VESA_CG640x400' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:85: `SW_VESA_CG640x480' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:86: `SW_VESA_32K_640' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:86: `SW_VESA_64K_640' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:87: `SW_VESA_FULL_640' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:89: `SW_VESA_800x600' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:89: `SW_VESA_CG800x600' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:90: `SW_VESA_32K_800' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:90: `SW_VESA_64K_800' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:91: `SW_VESA_FULL_800' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:93: `SW_VESA_1024x768' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:93: `SW_VESA_CG1024x768' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:94: `SW_VESA_32K_1024' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:94: `SW_VESA_64K_1024' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:95: `SW_VESA_FULL_1024' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:97: `SW_VESA_1280x1024' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:97: `SW_VESA_CG1280x1024' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:98: `SW_VESA_32K_1280' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:98: `SW_VESA_64K_1280' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:99: `SW_VESA_FULL_1280' undeclared (first use in this function) ../../dev/syscons/scvesactl.c:100: dereferencing pointer to incomplete type ../../dev/syscons/scvesactl.c:65: warning: unreachable code at beginning of switch statement *** Error code 1 Stop in /usr/amd/slave/usr/current/src/sys/compile/MASTER. --------------91719CB7ABAA29632FCADCE8 Content-Type: text/plain; charset=us-ascii; name="MASTER" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="MASTER" # $Id: MASTER,v 1.20 2000/10/09 03:25:48 doug Exp doug $ machine i386 cpu I686_CPU ident MASTER maxusers 32 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #makeoptions CONF_CFLAGS=-fno-builtin #Don't allow use of memcmp, etc. options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options DEVFS #Device Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV # install a CDEV entry in /dev options IPFILTER #ipfilter support options IPFILTER_LOG #ipfilter logging options DIAGNOSTIC options INVARIANT_SUPPORT options INVARIANTS options DDB # strings -n 3 /kernel | sed -n 's/^___//p' > MYKERNEL options INCLUDE_CONFIG_FILE # Include this file in kernel device isa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices options AHC_ALLOW_MEMIO # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device pass # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc 1 device atkbd device psm device vga device pcm # To include support for VESA video modes options VESA # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc 1 # Floating point support - do not disable. device npx # Serial (COM) ports device sio # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer # PCI Ethernet NICs. device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices - the number indicates how many units to allocated. device random # Entropy device device loop # Network loopback device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) device bpf # Berkeley packet filter device snp device speaker # Incredibly cool temperature reading stuff device smbus device intpm device smb --------------91719CB7ABAA29632FCADCE8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 23: 1:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id BE0B537B502 for ; Sun, 8 Oct 2000 23:01:43 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e9961er28099; Mon, 9 Oct 2000 15:01:40 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: rb@gid.co.uk Cc: iwasaki@jp.FreeBSD.org, keichii@peorth.iteration.net, current@freebsd.org Subject: Re: Recent kernels won't boot In-Reply-To: References: <20001007195242.C45189@peorth.iteration.net> <20001009022715Q.iwasaki@jp.FreeBSD.org> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001009150139M.iwasaki@jp.FreeBSD.org> Date: Mon, 09 Oct 2000 15:01:39 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That was it. Is the 4MB kernel size limit documented anywhere? I don't know :-) I luckily noticed this by a lot of trials. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 23: 1:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3455137B66E for ; Sun, 8 Oct 2000 23:01:48 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e9961lF21098; Sun, 8 Oct 2000 23:01:47 -0700 (PDT) Date: Sun, 8 Oct 2000 23:01:47 -0700 From: Alfred Perlstein To: Tony Johnson Cc: " FreeBSD-Current, " Subject: Re: current.freebsd.org Message-ID: <20001008230146.L272@fw.wintelcom.net> References: <20001008222000.K272@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from gjohnson@gs.verio.net on Mon, Oct 09, 2000 at 12:35:58AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Tony Johnson [001008 22:36] wrote: > Wow. Is it just me or does FreeBSD like to point fingers at everything that > is not the issue. I do not believe that my mailer has anything to do with > this. If you cannot roll with the punches, then that is your problem. I don't even think your mailer would be suitable as a crop sustaining fertilizer. > Well deal with it and get releng4 back up. Sure, why don't you hand me the keys to the colo place where it's at or make a commitment to pay my company for the bandwidth and rackspace to maintain a releng4 mirror, I really wouldn't mind that at all. > if "piss off" is an exceptable answer here, then I'd like for u to say so. Tony, you have a remarkable way of putting things into perspective, and I couldn't have said it better myself. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 8 23: 8:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 848A637B503 for ; Sun, 8 Oct 2000 23:08:13 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9969xh03937; Sun, 8 Oct 2000 23:10:00 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010090610.e9969xh03937@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mitsuru IWASAKI Cc: rb@gid.co.uk, keichii@peorth.iteration.net, current@freebsd.org Subject: Re: Recent kernels won't boot In-reply-to: Your message of "Mon, 09 Oct 2000 15:01:39 +0900." <20001009150139M.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Oct 2000 23:09:59 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That was it. Is the 4MB kernel size limit documented anywhere? > > I don't know :-) I luckily noticed this by a lot of trials. I'm not aware of any 4MB limit on kernel size (and I ought to be if there is one 8). Can you run the details past me? (I've regularly booted much larger kernels in the past...) -- ... 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-current" in the body of the message From owner-freebsd-current Mon Oct 9 0: 1:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 99DFA37B66C for ; Mon, 9 Oct 2000 00:01:09 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e9970vN92537; Mon, 9 Oct 2000 09:00:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Doug Barton Cc: current@FreeBSD.ORG Subject: Re: src/sys/dev/syscons/scvesactl.c broken In-Reply-To: Your message of "Sun, 08 Oct 2000 22:56:42 PDT." <39E15E1A.BC21F4AF@gorean.org> Date: Mon, 09 Oct 2000 09:00:57 +0200 Message-ID: <92535.971074857@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you sure your tree is entirely in sync ? I can't reproduce your problem here with the NOTES/LINT kernel... > Version 1.16 of src/sys/dev/syscons/scvesactl.c, removing > broke the kernel build for me. Attached is the >relevant log, and my kernel file. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 0: 7:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id EAF9A37B66C for ; Mon, 9 Oct 2000 00:07:23 -0700 (PDT) Received: from gorean.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id AAA71283; Mon, 9 Oct 2000 00:04:49 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39E16E11.4EF30A64@gorean.org> Date: Mon, 09 Oct 2000 00:04:49 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT-100 i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: src/sys/dev/syscons/scvesactl.c broken References: <92535.971074857@critter> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > Are you sure your tree is entirely in sync ? Yes... I've checked it several times. > I can't reproduce your problem here with the NOTES/LINT kernel... The following patch got my kernel compiled and running, although I can't say it's the right thing to do. I'll cvsup again and do a cvs update -A just to double check, but I'm pretty sure that this is a good tree, and it's happening for me on two different machines with similar kernel confs. Doug Index: scvesactl.c =================================================================== RCS file: /usr/ncvs/src/sys/dev/syscons/scvesactl.c,v retrieving revision 1.16 diff -u -r1.16 scvesactl.c --- scvesactl.c 2000/10/08 21:33:54 1.16 +++ scvesactl.c 2000/10/09 06:37:05 @@ -35,6 +35,8 @@ #include #include #include +#include +#include #include > > Version 1.16 of src/sys/dev/syscons/scvesactl.c, removing > > broke the kernel build for me. Attached is the > >relevant log, and my kernel file. -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 0: 8:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 9C92237B66C; Mon, 9 Oct 2000 00:08:45 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e9978gr51577; Mon, 9 Oct 2000 16:08:42 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: msmith@freebsd.org Cc: iwasaki@jp.FreeBSD.org, rb@gid.co.uk, keichii@peorth.iteration.net, current@freebsd.org Subject: Re: Recent kernels won't boot In-Reply-To: <200010090610.e9969xh03937@mass.osd.bsdi.com> References: <20001009150139M.iwasaki@jp.FreeBSD.org> <200010090610.e9969xh03937@mass.osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001009160841N.iwasaki@jp.FreeBSD.org> Date: Mon, 09 Oct 2000 16:08:41 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 69 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not aware of any 4MB limit on kernel size (and I ought to be if there > is one 8). Can you run the details past me? (I've regularly booted much > larger kernels in the past...) OK, I built 5 kernels based on the same kerne config file giving some modifications. Here is the result. boot? kernel size description ( (+)Add (-)Delete ) -------+---------------+---------------------------------------------- OK 4007152 (+)device acpica NG 4182845 (+)device acpica (+)options ACPI_DEBUG OK 4011963 (+)device acpica (+)options ACPI_DEBUG (-)USB stuff OK 3470869 GENERIC OK 16022220 config -g GENERIC Mysteriously, kernel.debug (16MB) does boot... Ah, probably section size limitation? % size ACPICA/kernel* GENERIC/kernel* text data bss dec hex filename 3176366 370104 172152 3718622 38bdde ACPICA/kernel.big 3058264 346724 165848 3570836 367c94 ACPICA/kernel.normal 3009909 368024 169688 3547621 3621e5 ACPICA/kernel.small 2745241 206872 152184 3104297 2f5e29 GENERIC/kernel 2745241 206872 152184 3104297 2f5e29 GENERIC/kernel.debug Maybe /boot/ stuff is reltated with this too. % ls -ltR /boot total 908 drwxr-xr-x 2 root wheel 3072 10/ 8 15:50 kernel -r-xr-xr-x 1 root wheel 159744 10/ 8 15:49 liloboot -r-xr-xr-x 1 root wheel 157696 10/ 8 15:49 pxeboot -r-xr-xr-x 1 root wheel 157696 10/ 8 15:49 cdboot drwxr-xr-x 2 root wheel 512 10/ 8 15:49 defaults -r-xr-xr-x 1 root wheel 155648 10/ 8 15:49 loader -r--r--r-- 1 root wheel 7680 10/ 8 15:49 boot2 -r--r--r-- 1 root wheel 512 10/ 8 15:49 boot1 -r--r--r-- 1 root wheel 512 10/ 8 15:49 boot0 -r--r--r-- 1 root wheel 512 10/ 8 15:49 mbr drwxr-xr-x 2 root wheel 512 10/ 7 11:29 kernel.old -rw-r--r-- 1 root wheel 7816 10/ 6 02:08 loader.conf -rw-r--r-- 1 root wheel 1440 10/ 4 19:23 device.hints -r-xr-xr-x 1 root wheel 155648 10/ 2 16:35 loader.old -r--r--r-- 1 root wheel 7577 9/27 10:57 loader.4th -r--r--r-- 1 root wheel 35170 9/27 10:57 support.4th drwxr-xr-x 2 root wheel 512 9/16 18:33 modules -rw-r--r-- 1 root wheel 24 8/ 4 23:58 kernel.conf -r--r--r-- 1 root wheel 12064 4/17 16:33 loader.help -r--r--r-- 1 root wheel 338 1/31 2000 loader.rc /boot/kernel: total 8536 -r-xr-xr-x 1 root wheel 20741 10/ 8 15:50 if_wi.ko : -r-xr-xr-x 1 root wheel 15097 10/ 8 15:49 3dfx.ko -r-xr-xr-x 1 root wheel 3891459 10/ 8 15:40 kernel /boot/defaults: total 8 -r--r--r-- 1 root wheel 7979 9/19 04:38 loader.conf /boot/kernel.old: total 3768 -r-xr-xr-x 1 root wheel 3844898 10/ 7 11:29 kernel /boot/modules: Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 0:19: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 8BB3737B502 for ; Mon, 9 Oct 2000 00:19:07 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e997J0N92768; Mon, 9 Oct 2000 09:19:00 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Doug Barton Cc: current@FreeBSD.ORG Subject: Re: src/sys/dev/syscons/scvesactl.c broken In-Reply-To: Your message of "Mon, 09 Oct 2000 00:04:49 PDT." <39E16E11.4EF30A64@gorean.org> Date: Mon, 09 Oct 2000 09:19:00 +0200 Message-ID: <92766.971075940@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39E16E11.4EF30A64@gorean.org>, Doug Barton writes: >Poul-Henning Kamp wrote: >> >> Are you sure your tree is entirely in sync ? > > Yes... I've checked it several times. > >> I can't reproduce your problem here with the NOTES/LINT kernel... OK, found it, two negative options in NOTES/LINT prevented a lot of syscons code from being covered by NOTES/LINT. I'll commit in a sec... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 0:21: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id AA7D037B502 for ; Mon, 9 Oct 2000 00:20:56 -0700 (PDT) Received: from gorean.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id AAA71539; Mon, 9 Oct 2000 00:20:52 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39E171D3.EC866171@gorean.org> Date: Mon, 09 Oct 2000 00:20:51 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT-100 i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: src/sys/dev/syscons/scvesactl.c broken References: <92766.971075940@critter> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <39E16E11.4EF30A64@gorean.org>, Doug Barton writes: > >Poul-Henning Kamp wrote: > >> > >> Are you sure your tree is entirely in sync ? > > > > Yes... I've checked it several times. > > > >> I can't reproduce your problem here with the NOTES/LINT kernel... > > OK, found it, two negative options in NOTES/LINT prevented a lot > of syscons code from being covered by NOTES/LINT. > > I'll commit in a sec... Cool... you da man. :) Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 0:26:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5911E37B503; Mon, 9 Oct 2000 00:26:45 -0700 (PDT) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA17885; Mon, 9 Oct 2000 00:26:40 -0700 Date: Mon, 9 Oct 2000 00:26:39 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: Mitsuru IWASAKI , rb@gid.co.uk, keichii@peorth.iteration.net, current@FreeBSD.ORG Subject: Re: Recent kernels won't boot In-Reply-To: <200010090610.e9969xh03937@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not aware of any 4MB limit on kernel size (and I ought to be if there > is one 8). Can you run the details past me? (I've regularly booted much > larger kernels in the past...) Alpha? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 1: 4: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from netplex.com.au (adsl-64-163-195-99.dsl.snfc21.pacbell.net [64.163.195.99]) by hub.freebsd.org (Postfix) with ESMTP id 4951237B502; Mon, 9 Oct 2000 01:04:05 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e99841G14893; Mon, 9 Oct 2000 01:04:01 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200010090804.e99841G14893@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: Mitsuru IWASAKI , rb@gid.co.uk, keichii@peorth.iteration.net, current@FreeBSD.ORG Subject: Re: Recent kernels won't boot In-Reply-To: <200010090610.e9969xh03937@mass.osd.bsdi.com> Date: Mon, 09 Oct 2000 01:04:01 -0700 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > That was it. Is the 4MB kernel size limit documented anywhere? > > > > I don't know :-) I luckily noticed this by a lot of trials. > > I'm not aware of any 4MB limit on kernel size (and I ought to be if there > is one 8). Can you run the details past me? (I've regularly booted much > larger kernels in the past...) Uhh, are you sure? Ignore the size of the file, what does 'size(1)' say about these large kernels? Does text+data+bss excede 4MB? I have a nagging suspicion that we only set up 4MB of page tables during the early part of the bootstrap process in locore.s. (forgive me for not looking, I have a most evil headache and locore.s is no way to improve it :-). Thinking about it some more, there may be a 3MB limit as we load above 1MB. I recall some heavy magic with the SMP bootstrap where we only use one PTD slot for 0-4MB in early boot.... Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 2:10:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id EC48E37B503; Mon, 9 Oct 2000 02:10:43 -0700 (PDT) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id KAA72685; Mon, 9 Oct 2000 10:09:28 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id JAA86947; Mon, 9 Oct 2000 09:52:55 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <200010090804.e99841G14893@netplex.com.au> References: <200010090610.e9969xh03937@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 9 Oct 2000 09:52:54 +0100 To: Peter Wemm From: Bob Bishop Subject: Re: Recent kernels won't boot Cc: Mike Smith , Mitsuru IWASAKI , keichii@peorth.iteration.net, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 01:04 -0700 9/10/00, Peter Wemm wrote: >Mike Smith wrote: >> > > That was it. Is the 4MB kernel size limit documented anywhere? >> > >> > I don't know :-) I luckily noticed this by a lot of trials. >> >> I'm not aware of any 4MB limit on kernel size (and I ought to be if there >> is one 8). Can you run the details past me? (I've regularly booted much >> larger kernels in the past...) > >Uhh, are you sure? Ignore the size of the file, what does 'size(1)' say >about these large kernels? Does text+data+bss excede 4MB? I have a >nagging suspicion that we only set up 4MB of page tables during the early >part of the bootstrap process in locore.s. (forgive me for not looking, >I have a most evil headache and locore.s is no way to improve it :-). >Thinking about it some more, there may be a 3MB limit as we load above >1MB. I recall some heavy magic with the SMP bootstrap where we only use one >PTD slot for 0-4MB in early boot.... Example: % size kernel*/kernel text data bss dec hex filename 3302182 206816 2265368 5774366 581c1e kernel.old/kernel 2947194 207168 168152 3322514 32b292 kernel/kernel Same kernel config except that top one includes KTR options and won't boot, bottom one has no KTR and boots OK. I've been running with SMP_DEBUG, KTR and the rest for a while, this trouble started a few days ago. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 4:34:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from dataloss.net (massive.dataloss.net [212.189.232.193]) by hub.freebsd.org (Postfix) with SMTP id 682FA37B66D for ; Mon, 9 Oct 2000 04:34:09 -0700 (PDT) Received: (qmail 11001 invoked by uid 1000); 9 Oct 2000 11:33:24 -0000 Date: Mon, 9 Oct 2000 13:33:24 +0200 From: Peter van Dijk To: freebsd-current@FreeBSD.ORG Subject: Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds Message-ID: <20001009133324.B9384@dataloss.net> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <20001008070212.04A381C2AB@hun.org> <20001008114647.A7756@dataloss.net> <20001009003730.A75DA1C2AB@hun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001009003730.A75DA1C2AB@hun.org>; from attila@hun.org on Mon, Oct 09, 2000 at 12:37:30AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 09, 2000 at 12:37:30AM +0000, attila! wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > on Sun, 8 Oct 2000 11:46:47 +0200, Peter van Dijk said: > > > Actually, mailwrapper (I don't know about this mailcap thing, > > I'm only running STABLE right now for lack of machines) does > > this job. Have you looked at /etc/mail/mailer.conf? The sendmail > > binary in /usr/sbin has no relation to sendmail - it's the > > mailwrapper, which is a good concept. > > What needs to be considered, in maintaining postfix for the > 'conventional' interface of sendmail (as of 8.10) is: > > /usr/bin/mailq -> /usr/sbin/sendmail > /usr/bin/newaliases -> /usr/sbin/sendmail > /usr/sbin/sendmail -> /usr/sbin/mailwrapper > > and, given that Wietse's /usr/bin/sendmail does essentially > the same thing as sendmail's /usr/sbin/mailwrapper except Stop that. Don't touch mailwrapper. Leave it in. We like it. Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 6:46:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from gateway.symark.com (firewall.symark.westlake.iswest.net [207.178.203.34]) by hub.freebsd.org (Postfix) with ESMTP id EC9FE37B503 for ; Mon, 9 Oct 2000 06:46:37 -0700 (PDT) Received: (from mailer@localhost) by gateway.symark.com (8.9.3/8.9.3) id GAA20940 for ; Mon, 9 Oct 2000 06:46:31 -0700 Received: from camel.symark.com(128.1.1.97) by gateway.symark.com via smap (V2.1+anti-relay+anti-spam) id xma020938; Mon, 9 Oct 00 06:46:18 -0700 Received: by localhost with Microsoft MAPI; Mon, 9 Oct 2000 06:47:50 -0700 Message-ID: <01C031BC.D7B04500.ggross@symark.com> From: Glen Gross Reply-To: "ggross@symark.com" To: "'current@freebsd.org'" Subject: FW: problem w/ new pcm feeder + emu10k1 in 4.1.1-stable Date: Mon, 9 Oct 2000 06:47:49 -0700 Organization: Symark Software X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Glendon Gross [SMTP:gross@clones.com] Sent: Sunday, October 08, 2000 6:23 AM To: Bjoern Fischer Cc: Cameron Grant; freebsd-stable@FreeBSD.ORG Subject: Re: problem w/ new pcm feeder + emu10k1 in 4.1.1-stable I wonder if this has anything to do with why my Soundwave 128 PCI is not recognized. It shows up as an "unknown card" during boot: Script started on Sun Oct 8 06:12:35 2000 % dmesg | grep unknown pci0: (vendor=0x1073, dev=0x000d) at 9.0 irq 11 % exit % exit Script done on Sun Oct 8 06:12:50 2000 I have another FreeBSD box which is working fine with the SB AWE-64 card, so I was hoping there might be a way to get this card to work. The card professes Soundblaster Pro/16 and OPL3 compatibility. On Sun, 8 Oct 2000, Bjoern Fischer wrote: > Hello Cameron, > > I was curious about your new pcm feeder, so I cvsuped to 4.1.1-STABLE > (Sun Oct 8 00:22:45 CEST 2000) and made world and new kernel. > > The SNDCTL_DSP_SETFMT ioctl *always* returns EINVAL :-( > > Hardware: SB Live! 1024 / EMU10K1 > > I turned on some debug switches and got this while trying to > start esd (esound). I have chosen esound because esd tries many > different formats for SNDCTL_DSP_SETFMT before giving up: > > installing feeder: 8to16le > installing feeder: 16leto8 > installing feeder: monotostereo8 > installing feeder: monotostereo16 > installing feeder: stereotomono8 > installing feeder: stereotomono16 > installing feeder: endian > installing feeder: sign8 > installing feeder: sign16le > installing feeder: ulawtou8 > installing feeder: u8toulaw > open snd0 subdev 0 flags 0x00000003 mode 0x00002000 > close snd0 subdev 0 > open snd0 subdev 3 flags 0x00000006 mode 0x00002000 > want format 8 > not mapped, flags 0, want speed 8000, try speed 48000, got speed 48000, not mapped, flags 8, find feeder type 3, got 0 > r = 22 > FIOASYNC > SNDCTL_DSP_SETFRAGMENT 0x01000008 > SNDCTL_DSP_SETFRAGMENT 256 frags, 256 sz > want format 16 > not mapped, flags 8, find feeder type 3, got 0 > close snd0 subdev 3 > chn_flush c->flags 0x00003000 > open snd0 subdev 3 flags 0x00000006 mode 0x00002000 > want format 8 > not mapped, flags 8, find feeder type 3, got 0 > FIOASYNC > SNDCTL_DSP_SETFRAGMENT 0x01000008 > SNDCTL_DSP_SETFRAGMENT 256 frags, 256 sz > want format 8 > not mapped, flags 8, find feeder type 3, got 0 > close snd0 subdev 3 > chn_flush c->flags 0x00003000 > open snd0 subdev 3 flags 0x00000006 mode 0x00002000 > want format 8 > not mapped, flags 8, find feeder type 3, got 0 > FIOASYNC > SNDCTL_DSP_SETFRAGMENT 0x01000008 > SNDCTL_DSP_SETFRAGMENT 256 frags, 256 sz > want format 16 > not mapped, flags 8, find feeder type 3, got 0 > close snd0 subdev 3 > chn_flush c->flags 0x00003000 > open snd0 subdev 3 flags 0x00000006 mode 0x00002000 > want format 8 > not mapped, flags 8, find feeder type 3, got 0 > FIOASYNC > SNDCTL_DSP_SETFRAGMENT 0x01000008 > SNDCTL_DSP_SETFRAGMENT 256 frags, 256 sz > want format 8 > not mapped, flags 8, find feeder type 3, got 0 > close snd0 subdev 3 > chn_flush c->flags 0x00003000 > open snd0 subdev 3 flags 0x00000006 mode 0x00002000 > want format 8 > not mapped, flags 8, find feeder type 3, got 0 > FIOASYNC > SNDCTL_DSP_SETFRAGMENT 0x01000008 > SNDCTL_DSP_SETFRAGMENT 256 frags, 256 sz > want format 16 > not mapped, flags 8, find feeder type 3, got 0 > close snd0 subdev 3 > chn_flush c->flags 0x00003000 > open snd0 subdev 3 flags 0x00000006 mode 0x00002000 > want format 8 > not mapped, flags 8, find feeder type 3, got 0 > FIOASYNC > SNDCTL_DSP_SETFRAGMENT 0x01000008 > SNDCTL_DSP_SETFRAGMENT 256 frags, 256 sz > want format 8 > not mapped, flags 8, find feeder type 3, got 0 > close snd0 subdev 3 > chn_flush c->flags 0x00003000 > open snd0 subdev 3 flags 0x00000006 mode 0x00002000 > want format 8 > not mapped, flags 8, find feeder type 3, got 0 > FIOASYNC > SNDCTL_DSP_SETFRAGMENT 0x01000008 > SNDCTL_DSP_SETFRAGMENT 256 frags, 256 sz > want format 8 > not mapped, flags 8, find feeder type 3, got 0 > close snd0 subdev 3 > chn_flush c->flags 0x00003000 > open snd0 subdev 3 flags 0x00000006 mode 0x00002000 > want format 8 > not mapped, flags 8, find feeder type 3, got 0 > ... > > Any idea what's causing this? > > Bjoern > > -- > -----BEGIN GEEK CODE BLOCK----- > GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ > K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ > ------END GEEK CODE BLOCK------ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 7: 1: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from neo.skynet.be (neo.skynet.be [195.238.2.53]) by hub.freebsd.org (Postfix) with ESMTP id 9AE1F37B502; Mon, 9 Oct 2000 07:00:57 -0700 (PDT) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by neo.skynet.be (Postfix) with ESMTP id 58F596CAE; Mon, 9 Oct 2000 16:00:08 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20001008212246.856EF1C2AB@hun.org> References: <20001008143111.D539@puck.firepipe.net>, , <20001008070212.04A381C2AB@hun.org> <20001008212246.856EF1C2AB@hun.org> Date: Mon, 9 Oct 2000 13:58:19 +0200 To: attila! , freebsd-current@freebsd.org, freebsd-ports@freebsd.org From: Brad Knowles Subject: Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds Cc: Will Andrews Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:22 PM +0000 2000/10/8, attila! wrote: > I look at 'snapshots' philosophically; if I willingly track > FreeBSD-5.0-current, I am obviously accustomed to the risks > therein. Understood. I just wanted to point out the philosophical differences from the postfix perspective, and thought that it was important that this be made explicit. > 20001001 is the most current which Wietse is now running and > stating that it is 'production quality'. Obviously, I will > port 20001001 this afternoon! No, 20001005 is the latest snapshot I know of, and appears to be what Wietse is running himself: $ telnet spike.porcupine.org. 25 Trying 168.100.189.2... Connected to spike.porcupine.org. Escape character is '^]'. 220 spike.porcupine.org ESMTP Postfix (Snapshot-20001005) quit 221 Bye Connection closed by foreign host. However, I would not be too surprised if what he was running is actually slightly later than this (i.e., another snapshot in progress), and it just identifies itself as Snapshot-20001005. > Why not consider the use of the mysql interface which > provides dynamic aliasing? The machines where I run this code don't strictly need a MySQL interface for aliases. Although we do keep our internal aliases in a MySQL database, I do not believe that it is in a format that would be suitable for use with postfix, and therefore I'd have to create yet another MySQL database that *was* in the proper format. This would likely lead to synchronization problems, etc.... -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 8:36:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from logger.gamma.ru (logger.gamma.ru [194.186.254.23]) by hub.freebsd.org (Postfix) with ESMTP id 4D3EB37B66C for ; Mon, 9 Oct 2000 08:36:42 -0700 (PDT) Received: (from ivt@localhost) by logger.gamma.ru (8.9.3/8.9.3) id TAA02572 for current@FreeBSD.ORG; Mon, 9 Oct 2000 19:36:37 +0400 (MSD) From: Igor Timkin Message-Id: <200010091536.TAA02572@logger.gamma.ru> Subject: today's panic To: current@FreeBSD.ORG Date: Mon, 9 Oct 2000 19:36:33 +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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today's current (buildworld+build kernel), check out at ~10.00 GMT. I have this problem during 6-7 days, the stable version for me: FreeBSD newsfeed.gamma.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Oct 2 21:56:00 MSD 2000 ivt@newsfeed.gamma.ru:/usr/obj/usr/src/sys/NEWSFEED i386 I haven't any problems till this date. Server: P2B-DS, BIOS rev. 1012. kgdb: (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /news/crash/kernel.0 (kgdb) core-file /news/crash/vmcore.0 SMP 2 cpus IdlePTD 2813952 initial pcb at 23e720 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 00000000 fault virtual address = 0xc fault code = supervisor read, page not present instruction pointer = 0x8:0xc015d616 stack pointer = 0x10:0xe2312da4 frame pointer = 0x10:0xe2312dd4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 388 (innd) trap number = 12 panic: page fault cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 syncing disks... 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 giving up on 20 buffers Uptime: 1m46s dumping to dev #da/25, offset 80572 dump 1023 1022 1021 1020 1019 1018 1017 1016 1015 1014 1013 1012 1011 1010 1009 [...] 6 5 4 3 2 1 0 --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:476 476 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:476 #1 0xc014a52f in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:317 #2 0xc014a954 in poweroff_wait (junk=0xc0217b6f, howto=-611008192) at /usr/src/sys/kern/kern_shutdown.c:569 #3 0xc01eb544 in trap_fatal (frame=0xe2312d64, eva=12) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc01eb2a5 in trap_pfault (frame=0xe2312d64, usermode=0, eva=12) at /usr/src/sys/i386/i386/trap.c:853 #5 0xc01eae03 in trap (frame={tf_fs = -500105192, tf_es = -500105200, tf_ds = -1072300016, tf_edi = 49, tf_esi = 64, tf_ebp = -500093484, tf_isp = -500093552, tf_ebx = -1015227740, tf_edx = 0, tf_ecx = -611008192, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1072310762, tf_cs = 8, tf_eflags = 66050, tf_esp = -1015227740, tf_ss = 64}) at /usr/src/sys/i386/i386/trap.c:436 #6 0xc015d616 in selscan (p=0xdb94c140, ibits=0xe2312e28, obits=0xe2312e1c, nfd=62) at /usr/src/sys/sys/file.h:187 182 struct proc *p; 183 { 184 int error; 185 186 fhold(fp); 187 error = (*fp->f_ops->fo_poll)(fp, events, cred, p); 188 fdrop(fp, p); 189 return (error); 190 } 191 (kgdb) print *fp $1 = {f_list = {le_next = 0x0, le_prev = 0x0}, f_flag = 0, f_type = 0, f_count = 0, f_msgcount = 0, f_cred = 0x0, f_ops = 0x0, f_seqcount = 0, ^^^^^^^^^^^ f_nextoff = 0, f_offset = 0, f_data = 0x0} #7 0xc015d371 in select (p=0xdb94c140, uap=0xe2312f80) at /usr/src/sys/kern/sys_generic.c:709 #8 0xc01eb960 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = -1078001617, tf_edi = 300, tf_esi = 134660576, tf_ebp = -1077937204, tf_isp = -500092972, tf_ebx = -1077937332, tf_edx = 246, tf_ecx = -1, tf_eax = 93, tf_trapno = 7, tf_err = 2, tf_eip = 672214604, tf_cs = 31, tf_eflags = 515, tf_esp = -1077937568, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1139 ---Type to continue, or q to quit--- #9 0xc01dc294 in Xint0x80_syscall () #10 0x805707d in ?? () #11 0x804a671 in ?? () dmesg -v: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Mon Oct 9 16:11:26 MSD 2000 ivt@newsfeed.gamma.ru:/usr/obj/usr/src/sys/NEWSFEED Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (451.03-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x387fbff real memory = 1073729536 (1048564K bytes) avail memory = 1042202624 (1017776K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc029d000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 4.0 on pci0 isa0: on isab0 pci0: at 4.1 pci0: at 4.2 irq 19 Timecounter "PIIX" frequency 3579545 Hz pci0: at 4.3 ahc0: port 0xd000-0xd0ff mem 0xe2000000-0xe2000fff irq 19 at device 6.0 on pci0 aic7890/91: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xb800-0xb8ff mem 0xe1800000-0xe1800fff irq 17 at device 11.0 on pci0 aic7890/91: Wide Channel A, SCSI Id=7, 32/255 SCBs fxp0: port 0xb400-0xb41f mem 0xe1000000-0xe10fffff,0xe3000000-0xe3000fff irq 16 at device 12.0 on pci0 fxp0: Ethernet address 00:a0:c9:a3:5a:85 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 isa_dmainit(2, 1024) failed fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IP packet filtering initialized, divert disabled, rule-based forwarding enabled, default to deny, logging disabled Waiting 3 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0a da6 at ahc1 bus 0 target 2 lun 0 da6: Fixed Direct Access SCSI-3 device da6: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da6: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da5 at ahc1 bus 0 target 1 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da5: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da4 at ahc1 bus 0 target 0 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da4: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) WARNING: / was not properly dismounted SMP: AP CPU #1 Launched! vinum: loaded vinum: reading configuration from /dev/da3d vinum: updating configuration from /dev/da2d vinum: updating configuration from /dev/da1d vinum: updating configuration from /dev/da0d Kernel cobfig: # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the NOTES configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.279 2000/09/22 23:39:47 ps Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident NEWSFEED maxusers 256 #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking #options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] #options SOFTUPDATES #Enable FFS soft updates support #options MFS #Memory Filesystem #options DEVFS #Device Filesystem #options MD_ROOT #MD is a potential root device #options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, NFS required #options MSDOSFS #MSDOS Filesystem #options CD9660 #ISO 9660 Filesystem #options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor #options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support #options SYSVSHM #SYSV-style shared memory #options SYSVMSG #SYSV-style message queues #options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extentions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV # install a CDEV entry in /dev options INCLUDE_CONFIG_FILE # Include this file in kernel options NO_F00F_HACK # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O device isa #device eisa device pci #options COMPAT_OLDISA # compatability shims for lnc, le #options COMPAT_OLDPCI # compatability shims for lnc, vx # Floppy drives device fdc # ATA and ATAPI devices #device ata #device atadisk # ATA disk drives #device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives #options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers #device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices options AHC_ALLOW_MEMIO #device amd # AMD 53C974 (Teckram DC-390(T)) #device isp # Qlogic family #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') #device adv #device adw #device bt #device aha 1 #device aic # RAID controllers interfaced to the SCSI subsystem #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device dpt # DPT Smartcache III, IV - See NOTES for options! #device mly # Mylex AcceleRAID/eXtremeRAID # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) #device sa # Sequential Access (tape etc) #device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers #device aac # Adaptec FSA RAID #device ida # Compaq Smart RAID #device amr # AMI MegaRAID #device mlx # Mylex DAC960 family # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc 1 device atkbd #device psm device vga # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc 1 # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # PCCARD (PCMCIA) support #device card #device pcic # Serial (COM) ports device sio # Parallel port #device ppc #device ppbus # Parallel port bus (required) #device lpt # Printer #device plip # TCP/IP over parallel #device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. #device de # DEC/Intel DC21x4x (``Tulip'') device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device vx # 3Com 3c590, 3c595 (``Vortex'') #device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. #device miibus # MII bus support #device dc # DEC/Intel 21143 and various workalikes #device pcn # AMD Am79C79x PCI 10/100 NICs #device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device ste # Sundance ST201 (D-Link DFE-550TX) #device tl # Texas Instruments ThunderLAN #device tx # SMC 9432TX (83c170 ``EPIC'') #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F #device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. #device ed #device ex #device ep #device fe #device cs #device sn # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attatement needed # and resources will always be dynamically assigned by the pccard code. #device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those paremeters here. #device an # BayStack 660 and others #device awi # Xircom pccard ethernet #device xe # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie #device le #device lnc # Pseudo devices - the number indicates how many units to allocated. device random # Entropy device device loop # Network loopback device ether # Ethernet support #device sl # Kernel SLIP #device ppp 1 # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) #device md # Memory "disks" #device gif 4 # IPv6 and IPv4 tunneling #device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter device vlan 4 #VLAN support # USB support #device uhci # UHCI PCI->USB interface #device ohci # OHCI PCI->USB interface #device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices #device ugen # Generic #device uhid # "Human Interface Devices" #device ukbd # Keyboard #device ulpt # Printer #device umass # Disks/Mass storage - Requires scbus and da #device ums # Mouse #device urio # Diamond Rio 500 MP3 player # USB Ethernet, requires mii #device aue # ADMtek USB ethernet #device cue # CATC USB ethernet #device kue # Kawasaki LSI USB ethernet options IPFIREWALL #firewall options IPFIREWALL_FORWARD #enable transparent proxy support options NMBCLUSTERS=8192 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 9: 0:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from logger.gamma.ru (logger.gamma.ru [194.186.254.23]) by hub.freebsd.org (Postfix) with ESMTP id 7C3A737B502 for ; Mon, 9 Oct 2000 09:00:49 -0700 (PDT) Received: (from ivt@localhost) by logger.gamma.ru (8.9.3/8.9.3) id UAA02769; Mon, 9 Oct 2000 20:00:45 +0400 (MSD) From: Igor Timkin Message-Id: <200010091600.UAA02769@logger.gamma.ru> Subject: Re: today's panic In-Reply-To: <200010091536.TAA02572@logger.gamma.ru> "from Igor Timkin at Oct 9, 2000 07:36:33 pm" To: Igor Timkin Date: Mon, 9 Oct 2000 20:00:44 +0400 (MSD) Cc: current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Today's current (buildworld+build kernel), check out at ~10.00 GMT. > I have this problem during 6-7 days, the stable version for me: > FreeBSD newsfeed.gamma.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Oct 2 21:56:00 MSD 2000 ivt@newsfeed.gamma.ru:/usr/obj/usr/src/sys/NEWSFEED i386 > I haven't any problems till this date. The same proble on another server (no crash dump). IP: c01502d8 nm /boot/kernel/kernel | grep c0150 | sort c015025c t pollscan c015031c T openbsd_poll c015032c T seltrue c0150338 T selrecord c0150378 T selwakeup c0150400 T pipe c0150588 t pipespace c01505f0 t pipeinit c0150690 t pipe_read c015098c t pipe_build_write_buffer c0150b44 t pipe_destroy_write_buffer c0150bc8 t pipe_clone_write_buffer c0150c04 t pipe_direct_write c0150edc t pipe_write dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Mon Oct 9 14:41:38 MSD 2000 ivt@mail.gamma.ru:/usr/obj/usr/src/sys/MAIL Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 300682964 Hz CPU: Pentium II/Pentium II Xeon/Celeron (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping = 3 Features=0x80f9ff real memory = 134217728 (131072K bytes) avail memory = 127950848 (124952K bytes) Preloaded elf kernel "kernel" at 0xc0292000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 atapci0: Busmastering DMA enabled ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 pci0: at 4.3 pci0: (vendor=0x9004, dev=0x8078) at 6.0 irq 9 de0: port 0xb800-0xb87f mem 0xe2800000-0xe280007f irq 9 at device 9.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:40:33:a2:ae:fe de1: port 0xb400-0xb47f mem 0xe2000000-0xe200007f irq 12 at device 10.0 on pci0 de1: 21140A [10-100Mb/s] pass 2.2 de1: address 00:40:33:a2:af:01 ed0: port 0xb000-0xb01f irq 10 at device 11.0 on pci0 ed0: address 00:00:1c:3a:3a:39, type NE2000 (16 bit) pci0: at 12.0 irq 11 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 ed1 at port 0x240-0x25f iomem 0xd8000 irq 5 on isa0 ed1: address 00:c0:6c:54:12:37, type NE2000 (16 bit) fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources DUMMYNET initialized (000608) IP packet filtering initialized, divert disabled, rule-based forwarding enabled, default to deny, logging disabled ad0: 7339MB [15907/15/63] at ata0-master UDMA33 ad2: 7339MB [15907/15/63] at ata1-master UDMA33 Mounting root from ufs:/dev/ad0a WARNING: / was not properly dismounted de0: enabling 100baseTX port de1: enabling 100baseTX port vinum: loaded vinum: reading configuration from /dev/ad2s1d vinum: updating configuration from /dev/ad0s1d de1: link down: cable problem? de1: enabling 10baseT port de1: enabling Full Duplex 10baseT port link_elf: symbol card_set_res_flags_desc undefined To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 10:19:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 0988937B672 for ; Mon, 9 Oct 2000 10:19:50 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e99GmAD02194; Mon, 9 Oct 2000 17:48:10 +0100 (BST) (envelope-from nik) Date: Mon, 9 Oct 2000 17:47:56 +0100 From: Nik Clayton To: Jordan Hubbard Cc: Bill Woods mail , "Thomas T. Veldhouse" , " FreeBSD-Current, " Subject: Re: current.freebsd.org Message-ID: <20001009174756.A2168@canyon.nothing-going-on.org> References: <581.971069573@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <581.971069573@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Sun, Oct 08, 2000 at 10:32:53PM -0700 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 08, 2000 at 10:32:53PM -0700, Jordan Hubbard wrote: > We've also been forced by the > silicon valley personnel crunch to hire a new system administrator > who's a little strange (he refers to himself as "Elvis Preston" and > makes odd little hip-thrusts at the system rack when he thinks nobody > is looking) and frequently missing, Huh? Sounds like unfurl to me. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 11:52:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from msa.hinet.net (msa.hinet.net [168.95.4.211]) by hub.freebsd.org (Postfix) with ESMTP id 2E54137B503 for ; Mon, 9 Oct 2000 11:52:12 -0700 (PDT) Received: from CoreBit.com (h216.s180.ts.hinet.net [168.95.180.216]) by msa.hinet.net (8.8.8/8.8.8) with ESMTP id CAA20019 for ; Tue, 10 Oct 2000 02:52:06 +0800 (CST) Message-ID: <39E213F5.448F177B@CoreBit.com> Date: Tue, 10 Oct 2000 02:52:37 +0800 From: Donny Lee Organization: CoreBit Technologies X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: port tree clean? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, is port tree back for cvsup? -- // Donny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 11:53:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.prosyst.com (ns.prosyst.com [195.14.248.50]) by hub.freebsd.org (Postfix) with SMTP id B16D437B66D for ; Mon, 9 Oct 2000 11:53:07 -0700 (PDT) Received: (qmail 17327 invoked from network); 9 Oct 2000 19:00:00 -0000 Received: from alpharetta.regusus.com (HELO ty) (12.29.78.1) by ns.prosyst.com with SMTP; 9 Oct 2000 19:00:00 -0000 Reply-To: From: "Ty Worthy" To: Subject: Free computer Date: Mon, 9 Oct 2000 14:52:55 -0400 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Visit http://www.afrocencheck.com and Enter to Win: FREE COMPUTER $1000.00 FREE AFROCENCHECKS Sign the Guestbook and you are automatically entered to WIN! Also everyone who signs the guestbook recieves a FREE GIFT! Please remember to mention " campaign EM" in the comments section and your FREE gift is on the way! Bonus - Send this email to 5 friends and we will automatically give you five additional entries to win the cash and prizes. Send this email to 10 friends and recieve ten additional entries to win the cash and prizes. More entries equals greater chances to WIN!!!! Extra Bonus - During the month of October we are awarding the individual with the most referrals $250.00 cash!!! Good Luck :) AfrocenCheck strongly supports anti-spamming laws. We truly believe in your right to privacy. To unsubscribe, simply press reply - type unsubscribe in the title and your name will be removed immediately. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 12:17:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from dataloss.net (massive.dataloss.net [212.189.232.193]) by hub.freebsd.org (Postfix) with SMTP id 5521C37B502 for ; Mon, 9 Oct 2000 12:17:21 -0700 (PDT) Received: (qmail 11923 invoked by uid 1000); 9 Oct 2000 19:16:42 -0000 Date: Mon, 9 Oct 2000 21:16:42 +0200 From: Peter van Dijk To: freebsd-current@FreeBSD.ORG Subject: Re: port tree clean? Message-ID: <20001009211642.I9384@dataloss.net> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <39E213F5.448F177B@CoreBit.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39E213F5.448F177B@CoreBit.com>; from donny@CoreBit.com on Tue, Oct 10, 2000 at 02:52:37AM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 10, 2000 at 02:52:37AM +0800, Donny Lee wrote: > > Hi there, > > is port tree back for cvsup? Yes. Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 12:29:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from msa.hinet.net (msa.hinet.net [168.95.4.211]) by hub.freebsd.org (Postfix) with ESMTP id 3AAD237B66E for ; Mon, 9 Oct 2000 12:29:48 -0700 (PDT) Received: from CoreBit.com (h216.s180.ts.hinet.net [168.95.180.216]) by msa.hinet.net (8.8.8/8.8.8) with ESMTP id DAA29927 for ; Tue, 10 Oct 2000 03:29:47 +0800 (CST) Message-ID: <39E21CCA.7109C6BE@CoreBit.com> Date: Tue, 10 Oct 2000 03:30:18 +0800 From: Donny Lee Organization: CoreBit Technologies X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.org Subject: Re: port tree clean? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter wrote: >> Hi there, >> is port tree back for cvsup? > Yes. Thanks, Peter. -- // Donny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 12:30:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 0A2C837B66F; Mon, 9 Oct 2000 12:30:29 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e99JU2i29929; Mon, 9 Oct 2000 12:30:02 -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 Date: Mon, 09 Oct 2000 12:30:32 -0700 (PDT) From: John Baldwin To: bde@FreeBSD.org, current@FreeBSD.org Subject: sio patch to add mutexes.. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey gang, I have some patches to add per-softc spin mutexes to the sio code in place of the old COM_LOCK. Since spin mutexes already dink with interrupts, this also allows all the *_intr() cruft to go away. Unfortunately, I can't get the current sio to work on any of the boxes here because DCD is never raised, so I don't know if this breaks anything, though it doesn't seem to fix my bxoes. :-/ The patch is availabe at http://www.FreeBSD.org/~jhb/patches/sio.patch, and included inline here for those w/o web access: Index: sio.c =================================================================== RCS file: /home/ncvs/src/sys/isa/sio.c,v retrieving revision 1.316 diff -u -r1.316 sio.c --- sio.c 2000/10/05 23:09:54 1.316 +++ sio.c 2000/10/06 06:11:29 @@ -96,12 +96,6 @@ #endif #include -/* XXX - this is ok because we only do sio fast interrupts on i386 */ -#ifndef __i386__ -#define disable_intr() -#define enable_intr() -#endif - #define LOTS_OF_EVENTS 64 /* helps separate urgent events from input */ #define CALLOUT_MASK 0x80 @@ -284,6 +278,8 @@ */ u_char obuf1[256]; u_char obuf2[256]; + + struct mtx intrlock; /* spin mutex used in the interrupt handler */ }; #ifdef COM_ESP @@ -759,7 +755,6 @@ u_int flags = device_get_flags(dev); int rid; struct resource *port; - int intrsave; rid = xrid; port = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid, @@ -771,6 +766,7 @@ com->bst = rman_get_bustag(port); com->bsh = rman_get_bushandle(port); + mtx_init(&com->intrlock, "sio interrupt lock", MTX_SPIN); #if 0 /* * XXX this is broken - when we are first called, there are no @@ -856,9 +852,7 @@ * but mask them in the processor as well in case there are some * (misconfigured) shared interrupts. */ - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); /* EXTRA DELAY? */ /* @@ -955,9 +949,9 @@ CLR_FLAG(dev, COM_C_IIR_TXRDYBUG); } sio_setreg(com, com_cfcr, CFCR_8BITS); - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); bus_release_resource(dev, SYS_RES_IOPORT, rid, port); + mtx_destroy(&com->intrlock); return (iobase == siocniobase ? 0 : result); } @@ -996,8 +990,7 @@ irqmap[3] = isa_irq_pending(); failures[9] = (sio_getreg(com, com_iir) & IIR_IMASK) - IIR_NOPEND; - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); irqs = irqmap[1] & ~irqmap[0]; if (bus_get_resource(idev, SYS_RES_IRQ, 0, &xirq, NULL) == 0 && @@ -1026,6 +1019,7 @@ break; } bus_release_resource(dev, SYS_RES_IOPORT, rid, port); + mtx_destroy(&com->intrlock); return (iobase == siocniobase ? 0 : result); } @@ -1116,7 +1110,6 @@ int rid; struct resource *port; int ret; - int intrstate; rid = xrid; port = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid, @@ -1155,6 +1148,7 @@ com->tx_fifo_size = 1; com->obufs[0].l_head = com->obuf1; com->obufs[1].l_head = com->obuf2; + mtx_init(&com->intrlock, "sio interrupt lock", MTX_SPIN); com->data_port = iobase + com_data; com->int_id_port = iobase + com_iir; @@ -1185,10 +1179,8 @@ com->it_in.c_ispeed = com->it_in.c_ospeed = comdefaultrate; } else com->it_in.c_ispeed = com->it_in.c_ospeed = TTYDEF_SPEED; - intrstate = save_intr(); if (siosetwater(com, com->it_in.c_ispeed) != 0) { - COM_UNLOCK(); - restore_intr(intrstate); + mtx_exit(&com->intrlock, MTX_SPIN); /* * Leave i/o resources allocated if this is a `cn'-level * console, so that other devices can't snarf them. @@ -1197,8 +1189,7 @@ bus_release_resource(dev, SYS_RES_IOPORT, rid, port); return (ENOMEM); } - COM_UNLOCK(); - restore_intr(intrstate); + mtx_exit(&com->intrlock, MTX_SPIN); termioschars(&com->it_in); com->it_out = com->it_in; @@ -1432,8 +1423,6 @@ goto out; } } else { - int intrsave; - /* * The device isn't open, so there are no conflicts. * Initialize it. Initialization is done twice in many @@ -1493,9 +1482,7 @@ } } - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); (void) inb(com->line_status_port); (void) inb(com->data_port); com->prev_modem_status = com->last_modem_status @@ -1507,8 +1494,7 @@ outb(com->intr_ctl_port, IER_ERXRDY | IER_ETXRDY | IER_ERLS | IER_EMSC); } - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); /* * Handle initial DCD. Callout devices get a fake initial * DCD (trapdoor DCD). If we are callout, then any sleeping @@ -1730,7 +1716,8 @@ } /* - * Call this function with COM_LOCK. It will return with the lock still held. + * Call this function with the per-softc intrlock mutex held. It will return + * with the lock still held. */ static void sioinput(com) @@ -1741,7 +1728,6 @@ u_char line_status; int recv_data; struct tty *tp; - int intrsave; buf = com->ibuf; tp = com->tp; @@ -1764,9 +1750,7 @@ * semantics instead of the save-and-disable semantics * that are used everywhere else. */ - intrsave = save_intr(); - COM_UNLOCK(); - enable_intr(); + mtx_exit(&com->intrlock, MTX_SPIN); incc = com->iptr - buf; if (tp->t_rawq.c_cc + incc > tp->t_ihiwat && (com->state & CS_RTS_IFLOW @@ -1787,8 +1771,7 @@ tp->t_lflag &= ~FLUSHO; comstart(tp); } - restore_intr(intrsave); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); } while (buf < com->iptr); } else { do { @@ -1797,9 +1780,7 @@ * semantics instead of the save-and-disable semantics * that are used everywhere else. */ - intrsave = save_intr(); - COM_UNLOCK(); - enable_intr(); + mtx_exit(&com->intrlock, MTX_SPIN); line_status = buf[com->ierroff]; recv_data = *buf++; if (line_status @@ -1814,8 +1795,7 @@ recv_data |= TTY_PE; } (*linesw[tp->t_line].l_rint)(recv_data, tp); - restore_intr(intrsave); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); } while (buf < com->iptr); } com_events -= (com->iptr - com->ibuf); @@ -1835,14 +1815,17 @@ siointr(arg) void *arg; { + struct com_s *com; + #ifndef COM_MULTIPORT - COM_LOCK(); - siointr1((struct com_s *) arg); - COM_UNLOCK(); + com = (struct com_s *)arg; + + mtx_enter(&com->intrlock, MTX_SPIN); + siointr1(com); + mtx_exit(&com->intrlock, MTX_SPIN); #else /* COM_MULTIPORT */ bool_t possibly_more_intrs; int unit; - struct com_s *com; /* * Loop until there is no activity on any port. This is necessary @@ -1851,15 +1834,11 @@ * devices, then the edge from one may be lost because another is * on. */ - COM_LOCK(); do { possibly_more_intrs = FALSE; for (unit = 0; unit < sio_numunits; ++unit) { com = com_addr(unit); - /* - * XXX COM_LOCK(); - * would it work here, or be counter-productive? - */ + mtx_enter(&com->intrlock, MTX_SPIN); if (com != NULL && !com->gone && (inb(com->int_id_port) & IIR_IMASK) @@ -1867,10 +1846,9 @@ siointr1(com); possibly_more_intrs = TRUE; } - /* XXX COM_UNLOCK(); */ + mtx_exit(&com->intrlock, MTX_SPIN); } } while (possibly_more_intrs); - COM_UNLOCK(); #endif /* COM_MULTIPORT */ } @@ -2264,7 +2242,6 @@ siopoll() { int unit; - int intrsave; if (com_events == 0) return; @@ -2283,9 +2260,7 @@ * Discard any events related to never-opened or * going-away devices. */ - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); incc = com->iptr - com->ibuf; com->iptr = com->ibuf; if (com->state & CS_CHECKMSR) { @@ -2293,43 +2268,33 @@ com->state &= ~CS_CHECKMSR; } com_events -= incc; - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); continue; } if (com->iptr != com->ibuf) { - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); sioinput(com); - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); } if (com->state & CS_CHECKMSR) { u_char delta_modem_status; - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); delta_modem_status = com->last_modem_status ^ com->prev_modem_status; com->prev_modem_status = com->last_modem_status; com_events -= LOTS_OF_EVENTS; com->state &= ~CS_CHECKMSR; - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); if (delta_modem_status & MSR_DCD) (*linesw[tp->t_line].l_modem) (tp, com->prev_modem_status & MSR_DCD); } if (com->state & CS_ODONE) { - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); com_events -= LOTS_OF_EVENTS; com->state &= ~CS_ODONE; - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); if (!(com->state & CS_BUSY) && !(com->extra_state & CSE_BUSYCHECK)) { timeout(siobusycheck, com, hz / 100); @@ -2357,7 +2322,6 @@ u_char dlbl; int s; int unit; - int intrsave; /* do historical conversions */ if (t->c_ispeed == 0) @@ -2429,7 +2393,6 @@ * the speed change atomically. Keeping interrupts disabled is * especially important while com_data is hidden. */ - intrsave = save_intr(); (void) siosetwater(com, t->c_ispeed); if (divisor != 0) { @@ -2517,8 +2480,7 @@ if (com->state >= (CS_BUSY | CS_TTGO)) siointr1(com); - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); splx(s); comstart(tp); if (com->ibufold != NULL) { @@ -2529,8 +2491,8 @@ } /* - * This function must be called with interrupts enabled and the com_lock - * unlocked. It will return with interrupts disabled and the com_lock locked. + * This function must be called with the per-softc interrupt mutex released + * and will return with it obtained. */ static int siosetwater(com, speed) @@ -2552,8 +2514,7 @@ for (ibufsize = 128; ibufsize < cp4ticks;) ibufsize <<= 1; if (ibufsize == com->ibufsize) { - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); return (0); } @@ -2563,8 +2524,7 @@ */ ibuf = malloc(2 * ibufsize, M_DEVBUF, M_NOWAIT); if (ibuf == NULL) { - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); return (ENOMEM); } @@ -2582,8 +2542,7 @@ * Read current input buffer, if any. Continue with interrupts * disabled. */ - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); if (com->iptr != com->ibuf) sioinput(com); @@ -2612,16 +2571,13 @@ struct com_s *com; int s; int unit; - int intrsave; unit = DEV_TO_UNIT(tp->t_dev); com = com_addr(unit); if (com == NULL) return; s = spltty(); - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); if (tp->t_state & TS_TTSTOP) com->state &= ~CS_TTGO; else @@ -2634,8 +2590,7 @@ && com->state & CS_RTS_IFLOW) outb(com->modem_ctl_port, com->mcr_image |= MCR_RTS); } - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); if (tp->t_state & (TS_TIMEOUT | TS_TTSTOP)) { ttwwakeup(tp); splx(s); @@ -2651,9 +2606,7 @@ sizeof com->obuf1); com->obufs[0].l_next = NULL; com->obufs[0].l_queued = TRUE; - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); if (com->state & CS_BUSY) { qp = com->obufq.l_next; while ((next = qp->l_next) != NULL) @@ -2665,8 +2618,7 @@ com->obufq.l_next = &com->obufs[0]; com->state |= CS_BUSY; } - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); } if (tp->t_outq.c_cc != 0 && !com->obufs[1].l_queued) { com->obufs[1].l_tail @@ -2674,9 +2626,7 @@ sizeof com->obuf2); com->obufs[1].l_next = NULL; com->obufs[1].l_queued = TRUE; - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); if (com->state & CS_BUSY) { qp = com->obufq.l_next; while ((next = qp->l_next) != NULL) @@ -2688,18 +2638,14 @@ com->obufq.l_next = &com->obufs[1]; com->state |= CS_BUSY; } - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); } tp->t_state |= TS_BUSY; } - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); if (com->state >= (CS_BUSY | CS_TTGO)) siointr1(com); /* fake interrupt to start output */ - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); ttwwakeup(tp); splx(s); } @@ -2710,14 +2656,11 @@ int rw; { struct com_s *com; - int intrsave; com = com_addr(DEV_TO_UNIT(tp->t_dev)); if (com == NULL || com->gone) return; - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); if (rw & FWRITE) { if (com->hasfifo) #ifdef COM_ESP @@ -2744,8 +2687,7 @@ com_events -= (com->iptr - com->ibuf); com->iptr = com->ibuf; } - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); comstart(tp); } @@ -2757,7 +2699,6 @@ { int mcr; int msr; - int intrsave; if (how == DMGET) { bits = TIOCM_LE; /* XXX - always enabled while open */ @@ -2789,9 +2730,7 @@ mcr |= MCR_RTS; if (com->gone) return(0); - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); switch (how) { case DMSET: outb(com->modem_ctl_port, @@ -2804,8 +2743,7 @@ outb(com->modem_ctl_port, com->mcr_image &= ~mcr); break; } - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); return (0); } @@ -2853,7 +2791,6 @@ { struct com_s *com; int unit; - int intrsave; sio_timeout_handle = timeout(comwakeup, (void *)NULL, sio_timeout); @@ -2865,12 +2802,9 @@ com = com_addr(unit); if (com != NULL && !com->gone && (com->state >= (CS_BUSY | CS_TTGO) || com->poll)) { - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); siointr1(com); - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); } } @@ -2892,13 +2826,10 @@ u_int delta; u_long total; - intrsave = save_intr(); - disable_intr(); - COM_LOCK(); + mtx_enter(&com->intrlock, MTX_SPIN); delta = com->delta_error_counts[errnum]; com->delta_error_counts[errnum] = 0; - COM_UNLOCK(); - restore_intr(intrsave); + mtx_exit(&com->intrlock, MTX_SPIN); if (delta == 0) continue; total = com->error_counts[errnum] += delta; -- 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-current" in the body of the message From owner-freebsd-current Mon Oct 9 13:45:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.prosyst.com (ns.prosyst.com [195.14.248.50]) by hub.freebsd.org (Postfix) with SMTP id CC8B237B66C for ; Mon, 9 Oct 2000 13:45:47 -0700 (PDT) Received: (qmail 21656 invoked from network); 9 Oct 2000 20:53:05 -0000 Received: from alpharetta.regusus.com (HELO ty) (12.29.78.1) by ns.prosyst.com with SMTP; 9 Oct 2000 20:53:05 -0000 Reply-To: From: "Ty Worthy" To: Subject: FREE COMPUTER Date: Mon, 9 Oct 2000 16:46:29 -0400 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Visit http://www.afrocencheck.com and Enter to Win: FREE COMPUTER $1000.00 FREE AFROCENCHECKS Sign the Guestbook and you are automatically entered to WIN! Also everyone who signs the guestbook recieves a FREE GIFT! Please remember to mention " campaign EM" in the comments section and your FREE gift is on the way! Bonus - Send this email to 5 friends and we will automatically give you five additional entries to win the cash and prizes. Send this email to 10 friends and recieve ten additional entries to win the cash and prizes. More entries equals greater chances to WIN!!!! Extra Bonus - During the month of October we are awarding the individual with the most referrals $250.00 cash!!! Good Luck :) AfrocenCheck strongly supports anti-spamming laws. We truly believe in your right to privacy. To unsubscribe, simply press reply - type unsubscribe in the title and your name will be removed immediately. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 14: 4:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9C65737B502 for ; Mon, 9 Oct 2000 14:04:44 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e99L4hY09539; Mon, 9 Oct 2000 15:04:43 -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.9.3/8.8.3) with ESMTP id PAA14722; Mon, 9 Oct 2000 15:04:42 -0600 (MDT) Message-Id: <200010092104.PAA14722@harmony.village.org> To: Donny Lee Subject: Re: port tree clean? Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 10 Oct 2000 02:52:37 +0800." <39E213F5.448F177B@CoreBit.com> References: <39E213F5.448F177B@CoreBit.com> Date: Mon, 09 Oct 2000 15:04:42 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39E213F5.448F177B@CoreBit.com> Donny Lee writes: : is port tree back for cvsup? Yes. UPDATING even has been updated saying so :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 16: 3:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id DCA2937B503; Mon, 9 Oct 2000 16:03:52 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e99N27i35570; Mon, 9 Oct 2000 16:02:07 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e99MxYF84751; Mon, 9 Oct 2000 15:59:34 -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: <200010090610.e9969xh03937@mass.osd.bsdi.com> Date: Mon, 09 Oct 2000 15:59:33 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Mike Smith Subject: Re: Recent kernels won't boot Cc: current@FreeBSD.ORG, keichii@peorth.iteration.net, rb@gid.co.uk, Mitsuru IWASAKI Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Oct-00 Mike Smith wrote: >> > That was it. Is the 4MB kernel size limit documented anywhere? >> >> I don't know :-) I luckily noticed this by a lot of trials. > > I'm not aware of any 4MB limit on kernel size (and I ought to be if there > is one 8). Can you run the details past me? (I've regularly booted much > larger kernels in the past...) I think the PSE optimization may limit us to a 4mb kernel size? Perhaps options DISABLE_PSE would work around it then? -- 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-current" in the body of the message From owner-freebsd-current Mon Oct 9 18:36: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id D930B37B503 for ; Mon, 9 Oct 2000 18:35:56 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e9A1Z1I87697; Tue, 10 Oct 2000 11:05:01 +0930 (CST) (envelope-from grog) Date: Tue, 10 Oct 2000 11:05:00 +0930 From: Greg Lehey To: attila! Cc: freebsd-current@FreeBSD.org Subject: Re: very high CPU time demand from process #10 ('idle') Message-ID: <20001010110500.A87663@wantadilla.lemis.com> References: <20001008075120.693D71C2AB@hun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20001008075120.693D71C2AB@hun.org>; from attila@hun.org on Sun, Oct 08, 2000 at 07:51:20AM +0000 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 8 October 2000 at 7:51:20 +0000, attila! wrote: > -- ps -ax -- > > 0 ?? DLs 0:00.40 (swapper) > 1 ?? ILs 0:00.07 /sbin/init -- > 2 ?? DL 0:04.23 (pagedaemon) > 3 ?? DL 0:00.65 (vmdaemon) > 4 ?? DL 0:00.70 (bufdaemon) > 5 ?? DL 0:44.85 (syncer) > 10 ?? RL 4986:29.70 (idle) > 11 ?? WL 5:43.86 (softinterrupt) > 12 ?? DL 24:58.44 (random) > 13 ?? WL 0:05.88 (irq10: ahc0) > 14 ?? WL 0:00.00 (irq11: dc0) > 15 ?? WL 0:14.91 (irq1: atkbd0) > 16 ?? WL 0:46.60 (irq12: psm0) > 17 ?? WL 0:00.00 (irq6: fdc0) > 18 ?? WL 0:00.08 (irq7: ppc0) > 19 ?? WL 3:19.82 (irq0: clk) > 20 ?? RL 5:43.47 (irq8: rtc) > > What is process 10? It's the idle process. > Is this literally a representation of the CPU idle time > accumulation for the 85 hours since boot? Yes. > Despite the enormous time burn on 'idle' it does not show on > 'top'. Yes, that didn't seem to make sense. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 19: 1:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from hub.org (hub.org [216.126.84.1]) by hub.freebsd.org (Postfix) with ESMTP id 6691137B502 for ; Mon, 9 Oct 2000 19:01:12 -0700 (PDT) Received: from localhost (scrappy@localhost) by hub.org (8.10.1/8.10.1) with ESMTP id e9A21BC36126 for ; Mon, 9 Oct 2000 22:01:11 -0400 (EDT) Date: Mon, 9 Oct 2000 22:01:11 -0400 (EDT) From: "Marc G. Fournier" To: freebsd-current@freebsd.org Subject: can't get into single user mode - panic: ffs_valloc: dup alloc Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG morning all ... Well, I swear I have to be missing something here that is going to make me slap my forehead, but I can't get into single user mode :( I hit the space bar, type in 'boot -s' and it goes through all the normal start up procedures, sets up the networking, etc ... The reason I'm trying to get into single user mode is cause I can't get into multi-user without it doing: ================= Recovering vi editor sessions mode = 0100600, inum = 729, fs = /tmp panic: ffs_valloc: dup alloc cpuid = 0; lapic.id = 00000000 Debugger("panic") CPU0 stopping CPUs: 0x00000002... stopped and a trace of: Debugger() @ +0x38 panic() @ +0xa0 ffs_valloc() @ +0xf5 ufs_makeinode() @ +0x5a ufs_create() @ +0x28 ufs_vnoperate() @ +0x15 Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@{postgresql|isc}.org ICQ#7615664 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 19: 7:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 2378D37B503 for ; Mon, 9 Oct 2000 19:07:19 -0700 (PDT) Received: by puck.firepipe.net (Postfix, from userid 1000) id 416901908; Mon, 9 Oct 2000 21:07:25 -0500 (EST) Date: Mon, 9 Oct 2000 21:07:25 -0500 From: Will Andrews To: Mark Hittinger Cc: freebsd-current@FreeBSD.ORG Subject: Re: a.out binaries die in -current recently Message-ID: <20001009210725.L1067@puck.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , Mark Hittinger , freebsd-current@FreeBSD.ORG References: <200010082041.PAA05628@freebsd.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010082041.PAA05628@freebsd.netcom.com>; from bugs@freebsd.netcom.com on Sun, Oct 08, 2000 at 03:41:07PM -0500 X-Operating-System: FreeBSD 4.1-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 08, 2000 at 03:41:07PM -0500, Mark Hittinger wrote: > For the past couple of days the old style binaries don't work under -current, > they simply core. Well, my attitude would be "so what?". But others may find a valid need for a.out binaries *shrug*. -- Will Andrews - Physics Computer Network wench The Universal Answer to All Problems - "It has something to do with physics." -- Comic on door of Room 240, Physics Building, Purdue University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 20:10:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from munin.odin-corporation.com (munin.odin-corporation.com [216.233.173.18]) by hub.freebsd.org (Postfix) with ESMTP id 37A8737B503 for ; Mon, 9 Oct 2000 20:10:51 -0700 (PDT) Received: from odin-corporation.com (localhost [127.0.0.1]) by munin.odin-corporation.com (8.9.3/8.9.1) with ESMTP id WAA46254 for ; Mon, 9 Oct 2000 22:10:50 -0500 (CDT) (envelope-from lars@odin-corporation.com) Message-ID: <39E288B9.8D933602@odin-corporation.com> Date: Mon, 09 Oct 2000 22:10:50 -0500 From: Lars Fredriksen Organization: Odin Corporation X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: no, en MIME-Version: 1.0 To: current@freebsd.org Subject: Compaq wl100 driver? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Has anyone ported the prism2 driver from linux to FreeBSD to run the Compaq/Samsung etc wl100 wireless ethernet cards? Anyone writing a new driver for it? Thanks, Lars To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 20:21:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 6A83F37B503 for ; Mon, 9 Oct 2000 20:21:29 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id XAA20016; Mon, 9 Oct 2000 23:21:27 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 9 Oct 2000 23:21:27 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Marc G. Fournier" Cc: freebsd-current@freebsd.org Subject: Re: can't get into single user mode - panic: ffs_valloc: dup alloc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Oct 2000, Marc G. Fournier wrote: > Well, I swear I have to be missing something here that is going to > make me slap my forehead, but I can't get into single user mode :( > > I hit the space bar, type in 'boot -s' and it goes through all the > normal start up procedures, sets up the networking, etc ... > > The reason I'm trying to get into single user mode is cause I > can't get into multi-user without it doing: That's interesting -- this morning, I hit a ffs_valloc: dup alloc panic following a buildworld. I assumed it was to do with my local ACL patches, although I have been unable to find a bug that could trigger it. I'm wondering if this isn't some sort of locking issue in VFS. I managed to trigger it in ufs_mkdir(), as I introduced a potentially location for blocking where previously none existed, suggesting that perhaps some UFS code is playing fast and loose with vnode locks. This panic is generated when FFS tries to recycle a vnode, but discovers it has a non-zero mode, indicating that it is in use elsewhere in the system, which should never happen. BTW, do you have FFS_EXTATTR enabled? Anyhow, I'm going to see if I can get it to be reproduceable here. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 20:24:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from hub.org (hub.org [216.126.84.1]) by hub.freebsd.org (Postfix) with ESMTP id 574DF37B502; Mon, 9 Oct 2000 20:24:45 -0700 (PDT) Received: from localhost (scrappy@localhost) by hub.org (8.10.1/8.10.1) with ESMTP id e9A3Oip79250; Mon, 9 Oct 2000 23:24:44 -0400 (EDT) Date: Mon, 9 Oct 2000 23:24:44 -0400 (EDT) From: "Marc G. Fournier" To: Robert Watson Cc: freebsd-current@freebsd.org Subject: Re: can't get into single user mode - panic: ffs_valloc: dup alloc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Oct 2000, Robert Watson wrote: > On Mon, 9 Oct 2000, Marc G. Fournier wrote: > > > Well, I swear I have to be missing something here that is going to > > make me slap my forehead, but I can't get into single user mode :( > > > > I hit the space bar, type in 'boot -s' and it goes through all the > > normal start up procedures, sets up the networking, etc ... > > > > The reason I'm trying to get into single user mode is cause I > > can't get into multi-user without it doing: > > That's interesting -- this morning, I hit a ffs_valloc: dup alloc panic > following a buildworld. I assumed it was to do with my local ACL patches, > although I have been unable to find a bug that could trigger it. I'm > wondering if this isn't some sort of locking issue in VFS. I managed to > trigger it in ufs_mkdir(), as I introduced a potentially location for > blocking where previously none existed, suggesting that perhaps some UFS > code is playing fast and loose with vnode locks. This panic is > generated when FFS tries to recycle a vnode, but discovers it has a > non-zero mode, indicating that it is in use elsewhere in the system, > which should never happen. > > BTW, do you have FFS_EXTATTR enabled? not that I've enabled ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 20:33:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id F2CD637B502 for ; Mon, 9 Oct 2000 20:33:07 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e9A3X5G04487 for ; Tue, 10 Oct 2000 12:33:05 +0900 (JST) Date: Tue, 10 Oct 2000 12:33:05 +0900 Message-ID: <7msnq54bgu.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: current@FreeBSD.ORG Subject: Re: cvs servers load In-Reply-To: In your message of "7 Oct 2000 14:59:27 GMT" <39DF3A3C.B46A3A32@software-munitions.com> References: <39DF3A3C.B46A3A32@software-munitions.com> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7 Oct 2000 14:59:27 GMT, Dennis Glatting wrote: > Any running load information on the CVS servers available? I'd like to > adjust my pointers to help spread the load. My current pointers, for > myself and two clients, is cvsup3. Most of servers in Japan have load statistics. But of course, servers in US are prefered... http://home.jp.freebsd.org/stats/mrtg/cvsup/index.en.html This statistics built with ucd-snmp and mrtg toolchain. If many US servers provide stats like this, users can select low-load server. -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 22:40:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DA9B637B66D for ; Mon, 9 Oct 2000 22:40:12 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e9A5eAY11419; Mon, 9 Oct 2000 23:40:11 -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.9.3/8.8.3) with ESMTP id XAA23280; Mon, 9 Oct 2000 23:40:09 -0600 (MDT) Message-Id: <200010100540.XAA23280@harmony.village.org> To: Will Andrews Subject: Re: a.out binaries die in -current recently Cc: Mark Hittinger , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 09 Oct 2000 21:07:25 CDT." <20001009210725.L1067@puck.firepipe.net> References: <20001009210725.L1067@puck.firepipe.net> <200010082041.PAA05628@freebsd.netcom.com> Date: Mon, 09 Oct 2000 23:40:09 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001009210725.L1067@puck.firepipe.net> Will Andrews writes: : On Sun, Oct 08, 2000 at 03:41:07PM -0500, Mark Hittinger wrote: : > For the past couple of days the old style binaries don't work under -current, : > they simply core. : : Well, my attitude would be "so what?". But others may find a valid need : for a.out binaries *shrug*. netscape. % file /usr/local/lib/netscape/navigator-4.72.us.bin /usr/local/lib/netscape/navigator-4.72.us.bin: FreeBSD/i386 compact demand paged dynamically linked executable % Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 22:46:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 56EF937B66D for ; Mon, 9 Oct 2000 22:46:12 -0700 (PDT) Received: by puck.firepipe.net (Postfix, from userid 1000) id 1CA761908; Tue, 10 Oct 2000 00:46:24 -0500 (EST) Date: Tue, 10 Oct 2000 00:46:24 -0500 From: Will Andrews To: Warner Losh Cc: Will Andrews , Mark Hittinger , freebsd-current@FreeBSD.ORG Subject: Re: a.out binaries die in -current recently Message-ID: <20001010004624.S1067@puck.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , Warner Losh , Mark Hittinger , freebsd-current@FreeBSD.ORG References: <20001009210725.L1067@puck.firepipe.net> <200010082041.PAA05628@freebsd.netcom.com> <20001009210725.L1067@puck.firepipe.net> <200010100540.XAA23280@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010100540.XAA23280@harmony.village.org>; from imp@village.org on Mon, Oct 09, 2000 at 11:40:09PM -0600 X-Operating-System: FreeBSD 4.1-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 09, 2000 at 11:40:09PM -0600, Warner Losh wrote: > netscape. Nope. BSDI Netscape bins don't require a.out libs. -- Will Andrews - Physics Computer Network wench The Universal Answer to All Problems - "It has something to do with physics." -- Comic on door of Room 240, Physics Building, Purdue University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 9 22:48:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 40FA637B503 for ; Mon, 9 Oct 2000 22:48:47 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e9A5mjY11455; Mon, 9 Oct 2000 23:48:45 -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.9.3/8.8.3) with ESMTP id XAA23384; Mon, 9 Oct 2000 23:48:44 -0600 (MDT) Message-Id: <200010100548.XAA23384@harmony.village.org> To: Will Andrews Subject: Re: a.out binaries die in -current recently Cc: Mark Hittinger , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 10 Oct 2000 00:46:24 CDT." <20001010004624.S1067@puck.firepipe.net> References: <20001010004624.S1067@puck.firepipe.net> <20001009210725.L1067@puck.firepipe.net> <200010082041.PAA05628@freebsd.netcom.com> <20001009210725.L1067@puck.firepipe.net> <200010100540.XAA23280@harmony.village.org> Date: Mon, 09 Oct 2000 23:48:44 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001010004624.S1067@puck.firepipe.net> Will Andrews writes: : On Mon, Oct 09, 2000 at 11:40:09PM -0600, Warner Losh wrote: : > netscape. : : Nope. BSDI Netscape bins don't require a.out libs. Ah. It is still an a.out binary... You are right it is staticlly linked. I'll stop making trouble now... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 2: 6:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id C77F637B502 for ; Tue, 10 Oct 2000 02:06:06 -0700 (PDT) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id KAA16714 for current@freebsd.org; Tue, 10 Oct 2000 10:06:00 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id JAA90182 for ; Tue, 10 Oct 2000 09:48:05 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 10 Oct 2000 09:48:05 +0100 To: current@freebsd.org From: Bob Bishop Subject: -current grinds exceeding slow Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, What's happened recently to make -current so slow? make world kernel FreeBSD 5.0-CURRENT #11: Sat Sep 30 15:07:06 BST 2000 >>> elf make world started on Fri Oct 6 08:33:20 BST 2000 >>> elf make world completed on Fri Oct 6 13:30:13 BST 2000 ...just under 5hrs make world kernel FreeBSD 5.0-CURRENT #0: Sun Oct 8 13:37:48 BST 2000 >>> elf make world started on Sun Oct 8 15:09:39 BST 2000 >>> elf make world completed on Mon Oct 9 16:35:00 BST 2000 ...over 25hrs The machine feels very sluggish too, and the snake sometimes wiggles to a standstill. This is a UP box, I've got an SMP box with the same symptoms. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 5:44:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from valcho.net (valcho.net [208.10.211.61]) by hub.freebsd.org (Postfix) with SMTP id 76F2537B503 for ; Tue, 10 Oct 2000 05:44:23 -0700 (PDT) Received: (qmail 25292 invoked by uid 1000); 10 Oct 2000 12:44:15 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 10 Oct 2000 12:44:15 -0000 Date: Tue, 10 Oct 2000 08:44:15 -0400 (EDT) From: Valentin Chopov To: freebsd-current@freebsd.org Subject: after errors in SCSI (Adaptec 29160), 5.0 freezes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG System is freezes, no panic, no reboot, need cold reset to restart... Thanks, Val This is from /var/log/messages : Oct 10 00:10:11 squid /boot/kernel/kernel: (da2:ahc0:0:2:0): Invalidating pack Oct 10 00:10:44 squid last message repeated 10 times Oct 10 00:11:03 squid last message repeated 6 times Oct 10 00:11:07 squid /boot/kernel/kernel: (da2:ahc0:0:2:0): SCB 0x60 - timed out while idle, SEQADDR == 0x3 Oct 10 00:11:07 squid /boot/kernel/kernel: sg[0] - Addr 0x2af1d000 : Length 4096 Oct 10 00:11:07 squid /boot/kernel/kernel: sg[1] - Addr 0x1c85e000 : Length 2048 Oct 10 00:11:07 squid /boot/kernel/kernel: (da2:ahc0:0:2:0): SCB 96: Immediate reset. Flags = 0x4040 Oct 10 00:11:07 squid /boot/kernel/kernel: (da2:ahc0:0:2:0): no longer in timeout, status = 34b Oct 10 00:11:07 squid /boot/kernel/kernel: ahc0: Issued Channel A Bus Reset. 32 SCBs aborted -------- dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Mon Oct 9 16:29:43 EDT 2000 valentin@squid.seidata.com:/usr/src/sys/compile/SQUID Timecounter "i8254" frequency 1193072 Hz CPU: Pentium III/Pentium III Xeon/Celeron (733.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x387fbff real memory = 805240832 (786368K bytes) config> di pcic0 No such device: pcic0 Invalid command or syntax. Type `?' for help. config> di sn0 No such device: sn0 Invalid command or syntax. Type `?' for help. config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di le0 No such device: le0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> di ed0 No such device: ed0 Invalid command or syntax. Type `?' for help. config> di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config> di bt0 No such device: bt0 Invalid command or syntax. Type `?' for help. config> di aic0 No such device: aic0 Invalid command or syntax. Type `?' for help. config> di aha0 No such device: aha0 Invalid command or syntax. Type `?' for help. config> di adv0 No such device: adv0 Invalid command or syntax. Type `?' for help. config> q avail memory = 779165696 (760904K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 12 IOAPIC #0 intpin 17 -> irq 10 IOAPIC #0 intpin 18 -> irq 11 IOAPIC #0 intpin 19 -> irq 15 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02c2000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02c209c. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 12 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f at device 7.1 on pci0 atapci0: Busmastering DMA enabled ata0: at 0x1f0 irq 14 on atapci0 fxp0: port 0xd800-0xd81f mem 0xd7000000-0xd70fffff,0xd7201000-0xd7201fff irq 10 at device 17.0 on pci0 fxp0: Ethernet address 00:90:27:12:fa:89 fxp1: port 0xdc00-0xdc1f mem 0xd7100000-0xd71fffff,0xd7200000-0xd7200fff irq 11 at device 18.0 on pci0 fxp1: Ethernet address 00:90:27:12:e0:85 ahc0: port 0xe000-0xe0ff mem 0xd7202000-0xd7202fff irq 15 at device 19.0 on pci0 aic7892: Wide Channel A, SCSI Id=7, 32/255 SCBs fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 isa_dmainit(2, 1024) failed fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IP packet filtering initialized, divert disabled, rule-based forwarding enabled, default to accept, logging disabled IP Filter: v3.4.9 initialized. Default = pass all, Logging = disabled ad0: 6180MB [13395/15/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) WARNING: / was not properly dismounted SMP: AP CPU #1 Launched! icmp-response bandwidth limit 275/200 pps To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 6: 6:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id DDF3237B66C for ; Tue, 10 Oct 2000 06:06:34 -0700 (PDT) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id OAA23400 for current@FreeBSD.ORG; Tue, 10 Oct 2000 14:06:33 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id NAA90665 for ; Tue, 10 Oct 2000 13:35:57 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 10 Oct 2000 13:35:57 +0100 To: current@FreeBSD.ORG From: Bob Bishop Subject: ed0: warning - receiver ring buffer overrun Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm seeing lots of: ed0: warning - receiver ring buffer overrun This box is building the world with sources via NFS. What gives? -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 8:35:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from hun.org (hun.org [216.190.28.252]) by hub.freebsd.org (Postfix) with ESMTP id BF79937B502 for ; Tue, 10 Oct 2000 08:35:54 -0700 (PDT) Received: by hun.org (Postfix, from userid 1001) id 16E5C1C2AB; Tue, 10 Oct 2000 15:35:42 +0000 (GMT) From: attila! X-Organization: hun.org, over 40 years beyond the fringe home for unpenitent hackers and anarcho-cryptophreaks X-Die-Spammers: Spammers cheerfully broiled and served with Stubbs's "Inferno" Wicked Chicken Wing Sauce X-Mailer: FreeBSD 5.0-20000925 with XEmacs V21.1.10 (see alt.religion.emacs) X-Ballistic: N 37.218497 W 113.614979 In-Reply-To: References: <20001008212246.856EF1C2AB@hun.org>, <20001008143111.D539@puck.firepipe.net>, , <20001008070212.04A381C2AB@hun.org>, <20001008212246.856EF1C2AB@hun.org> To: Brad Knowles Cc: freebsd-current@freebsd.org Subject: Re: POSTFIX-- version 20001005 Message-Id: <20001010153542.16E5C1C2AB@hun.org> Date: Tue, 10 Oct 2000 15:35:42 +0000 (GMT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG on Mon, 9 Oct 2000 13:58:19 +0200, Brad Knowles replied: + [snip] + + At 9:22 PM +0000 2000/10/8, attila! wrote: + + > 20001001 is the most current which Wietse is now running and + > stating that it is 'production quality'. Obviously, I will + > port 20001001 this afternoon! + + No, 20001005 is the latest snapshot I know of, and appears to be + what Wietse is running himself: You are correct --it was a typo on my part.... There was no 20001001; 20000924 was the previous! I compiled and verified 20001005 last night and will install it on hun.org later this morning when I get a chance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 9: 7:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id E0CB437B66F for ; Tue, 10 Oct 2000 09:07:18 -0700 (PDT) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id MAA03811; Tue, 10 Oct 2000 12:07:17 -0400 (EDT) (envelope-from mwlucas) Date: Tue, 10 Oct 2000 12:07:17 -0400 From: Michael Lucas To: "Marc G. Fournier" Cc: freebsd-current@FreeBSD.ORG Subject: Re: can't get into single user mode - panic: ffs_valloc: dup alloc Message-ID: <20001010120717.A3746@blackhelicopters.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from scrappy@hub.org on Mon, Oct 09, 2000 at 10:01:11PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's not just you. I just assumed I had done something wrong. Hitting ^C during bootup fsck gets me a single-user prompt. On Mon, Oct 09, 2000 at 10:01:11PM -0400, Marc G. Fournier wrote: > > morning all ... > > Well, I swear I have to be missing something here that is going to > make me slap my forehead, but I can't get into single user mode :( > > I hit the space bar, type in 'boot -s' and it goes through all the > normal start up procedures, sets up the networking, etc ... > > The reason I'm trying to get into single user mode is cause I > can't get into multi-user without it doing: > > ================= > Recovering vi editor sessions > mode = 0100600, inum = 729, fs = /tmp > panic: ffs_valloc: dup alloc > cpuid = 0; lapic.id = 00000000 > Debugger("panic") > > CPU0 stopping CPUs: 0x00000002... stopped > > > and a trace of: > > Debugger() @ +0x38 > panic() @ +0xa0 > ffs_valloc() @ +0xf5 > ufs_makeinode() @ +0x5a > ufs_create() @ +0x28 > ufs_vnoperate() @ +0x15 > > Marc G. Fournier scrappy@hub.org > Systems Administrator @ hub.org > scrappy@{postgresql|isc}.org ICQ#7615664 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 9:35: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 9B4AF37B502; Tue, 10 Oct 2000 09:34:57 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e9AGYpr28656; Wed, 11 Oct 2000 01:34:51 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: jhb@FreeBSD.ORG Cc: msmith@FreeBSD.ORG, current@FreeBSD.ORG, keichii@peorth.iteration.net, rb@gid.co.uk, iwasaki@jp.FreeBSD.org Subject: Re: Recent kernels won't boot In-Reply-To: References: <200010090610.e9969xh03937@mass.osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001011013450X.iwasaki@jp.FreeBSD.org> Date: Wed, 11 Oct 2000 01:34:50 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 12 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> > That was it. Is the 4MB kernel size limit documented anywhere? > >> > >> I don't know :-) I luckily noticed this by a lot of trials. > > > > I'm not aware of any 4MB limit on kernel size (and I ought to be if there > > is one 8). Can you run the details past me? (I've regularly booted much > > larger kernels in the past...) > > I think the PSE optimization may limit us to a 4mb kernel size? Perhaps > options DISABLE_PSE would work around it then? I tried `options DISABLE_PSE', but no effect... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 10: 8:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR8-44.accesscable.net [24.138.8.44]) by hub.freebsd.org (Postfix) with ESMTP id BBE5B37B66C for ; Tue, 10 Oct 2000 10:08:00 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.0) with ESMTP id e9AH6O212386; Tue, 10 Oct 2000 14:06:28 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 10 Oct 2000 14:06:24 -0300 (ADT) From: The Hermit Hacker To: Michael Lucas Cc: freebsd-current@FreeBSD.ORG Subject: Re: can't get into single user mode - panic: ffs_valloc: dup alloc In-Reply-To: <20001010120717.A3746@blackhelicopters.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Oct 2000, Michael Lucas wrote: > It's not just you. I just assumed I had done something wrong. > > Hitting ^C during bootup fsck gets me a single-user prompt. ah, good, that got me back up and running, thanks :) > > On Mon, Oct 09, 2000 at 10:01:11PM -0400, Marc G. Fournier wrote: > > > > morning all ... > > > > Well, I swear I have to be missing something here that is going to > > make me slap my forehead, but I can't get into single user mode :( > > > > I hit the space bar, type in 'boot -s' and it goes through all the > > normal start up procedures, sets up the networking, etc ... > > > > The reason I'm trying to get into single user mode is cause I > > can't get into multi-user without it doing: > > > > ================= > > Recovering vi editor sessions > > mode = 0100600, inum = 729, fs = /tmp > > panic: ffs_valloc: dup alloc > > cpuid = 0; lapic.id = 00000000 > > Debugger("panic") > > > > CPU0 stopping CPUs: 0x00000002... stopped > > > > > > and a trace of: > > > > Debugger() @ +0x38 > > panic() @ +0xa0 > > ffs_valloc() @ +0xf5 > > ufs_makeinode() @ +0x5a > > ufs_create() @ +0x28 > > ufs_vnoperate() @ +0x15 > > > > Marc G. Fournier scrappy@hub.org > > Systems Administrator @ hub.org > > scrappy@{postgresql|isc}.org ICQ#7615664 > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > Michael Lucas > mwlucas@blackhelicopters.org > http://www.blackhelicopters.org/~mwlucas/ > Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 10:14: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 9891F37B502 for ; Tue, 10 Oct 2000 10:13:57 -0700 (PDT) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id TAA15488; Tue, 10 Oct 2000 19:14:26 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 13j2yL-0001sW-00 for ; Tue, 10 Oct 2000 19:13:49 +0200 Date: Tue, 10 Oct 2000 19:13:49 +0200 From: Szilveszter Adam To: freebsd-current@FreeBSD.ORG Subject: Re: can't get into single user mode - panic: ffs_valloc: dup alloc Message-ID: <20001010191349.A7196@petra.hos.u-szeged.hu> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <20001010120717.A3746@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: ; from scrappy@hub.org on Tue, Oct 10, 2000 at 02:06:24PM -0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 10, 2000 at 02:06:24PM -0300, The Hermit Hacker wrote: > On Tue, 10 Oct 2000, Michael Lucas wrote: > > > It's not just you. I just assumed I had done something wrong. > > > > Hitting ^C during bootup fsck gets me a single-user prompt. > > ah, good, that got me back up and running, thanks :) What system are you expriencing this on? I have rebuilt this beast today and had no such probs... "boot -s" works fine. -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 10:23: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id A95AA37B502 for ; Tue, 10 Oct 2000 10:23:00 -0700 (PDT) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id NAA04290; Tue, 10 Oct 2000 13:22:56 -0400 (EDT) (envelope-from mwlucas) Date: Tue, 10 Oct 2000 13:22:55 -0400 From: Michael Lucas To: Szilveszter Adam Cc: freebsd-current@FreeBSD.ORG Subject: Re: can't get into single user mode - panic: ffs_valloc: dup alloc Message-ID: <20001010132255.A4214@blackhelicopters.org> References: <20001010120717.A3746@blackhelicopters.org> <20001010191349.A7196@petra.hos.u-szeged.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001010191349.A7196@petra.hos.u-szeged.hu>; from sziszi@petra.hos.u-szeged.hu on Tue, Oct 10, 2000 at 07:13:49PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 10, 2000 at 07:13:49PM +0200, Szilveszter Adam wrote: > On Tue, Oct 10, 2000 at 02:06:24PM -0300, The Hermit Hacker wrote: > > On Tue, 10 Oct 2000, Michael Lucas wrote: > > > > > It's not just you. I just assumed I had done something wrong. > > > > > > Hitting ^C during bootup fsck gets me a single-user prompt. > > > > ah, good, that got me back up and running, thanks :) > > What system are you expriencing this on? > > I have rebuilt this beast today and had no such probs... "boot -s" works fine. I'm experiencing this on a -current from sources supped on Oct 03. turtledawn~;uname -a FreeBSD turtledawn.blackhelicopters.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Oct 3 10:58:59 EDT 2000 mwlucas@turtledawn.blackhelicopters.org:/usr/obj/usr/src/sys/TURTLEDAWN i386 turtledawn~; The first line on /usr/sup/src-all/checkouts.cvs:. F 5 970574708 (I forget how to get the date out of this, but surely the brainy sorts out there remember how...) System is a Toshiba Satellite 2210 CDT. More info on request. ==ml -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 10:43: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR8-44.accesscable.net [24.138.8.44]) by hub.freebsd.org (Postfix) with ESMTP id 0B55737B502 for ; Tue, 10 Oct 2000 10:43:01 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.0) with ESMTP id e9AHeK327199; Tue, 10 Oct 2000 14:40:20 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 10 Oct 2000 14:40:19 -0300 (ADT) From: The Hermit Hacker To: Szilveszter Adam Cc: freebsd-current@FreeBSD.ORG Subject: Re: can't get into single user mode - panic: ffs_valloc: dup alloc In-Reply-To: <20001010191349.A7196@petra.hos.u-szeged.hu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Oct 2000, Szilveszter Adam wrote: > On Tue, Oct 10, 2000 at 02:06:24PM -0300, The Hermit Hacker wrote: > > On Tue, 10 Oct 2000, Michael Lucas wrote: > > > > > It's not just you. I just assumed I had done something wrong. > > > > > > Hitting ^C during bootup fsck gets me a single-user prompt. > > > > ah, good, that got me back up and running, thanks :) > > What system are you expriencing this on? -current as of two days ago ... am just rebuilding based on todays sources now ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 10:50:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from logger.gamma.ru (logger.gamma.ru [194.186.254.23]) by hub.freebsd.org (Postfix) with ESMTP id B44D437B67F for ; Tue, 10 Oct 2000 10:50:16 -0700 (PDT) Received: (from ivt@localhost) by logger.gamma.ru (8.9.3/8.9.3) id VAA12934; Tue, 10 Oct 2000 21:50:05 +0400 (MSD) From: Igor Timkin Message-Id: <200010101750.VAA12934@logger.gamma.ru> Subject: Re: can't get into single user mode - panic: ffs_valloc: dup alloc In-Reply-To: <20001010120717.A3746@blackhelicopters.org> "from Michael Lucas at Oct 10, 2000 12:07:17 pm" To: Michael Lucas Date: Tue, 10 Oct 2000 21:50:05 +0400 (MSD) Cc: "Marc G. Fournier" , freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I hit the space bar, type in 'boot -s' and it goes through all the > > normal start up procedures, sets up the networking, etc ... 'boot -s' don't work for me, I use 'boot /boot/kernel/kernel -s' instead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 11: 6: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 37D3937B66C for ; Tue, 10 Oct 2000 11:06:04 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13j3mt-00064l-00; Tue, 10 Oct 2000 18:06:03 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e9AI8BC08299; Tue, 10 Oct 2000 20:08:11 +0200 (CEST) (envelope-from wkb) Date: Tue, 10 Oct 2000 20:08:11 +0200 From: Wilko Bulte To: Bob Bishop Cc: current@freebsd.org Subject: Re: ed0: warning - receiver ring buffer overrun Message-ID: <20001010200811.A8273@freebie.demon.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from rb@gid.co.uk on Tue, Oct 10, 2000 at 01:35:57PM +0100 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 10, 2000 at 01:35:57PM +0100, Bob Bishop wrote: > Hi, > > I'm seeing lots of: > > ed0: warning - receiver ring buffer overrun > > This box is building the world with sources via NFS. What gives? Something not servicing the ed0 card fast enough? FWIW: my -current build on a PPro 200 took it's normal 3-something hours. -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 11:15: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 1F96037B502 for ; Tue, 10 Oct 2000 11:15:01 -0700 (PDT) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id UAA19063; Tue, 10 Oct 2000 20:15:35 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 13j3vW-00029F-00 for ; Tue, 10 Oct 2000 20:14:58 +0200 Date: Tue, 10 Oct 2000 20:14:58 +0200 From: Szilveszter Adam To: freebsd-current@FreeBSD.ORG Subject: Re: can't get into single user mode - panic: ffs_valloc: dup alloc Message-ID: <20001010201458.A8137@petra.hos.u-szeged.hu> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <20001010120717.A3746@blackhelicopters.org> <20001010191349.A7196@petra.hos.u-szeged.hu> <20001010132255.A4214@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: <20001010132255.A4214@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Tue, Oct 10, 2000 at 01:22:55PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 10, 2000 at 01:22:55PM -0400, Michael Lucas wrote: > I'm experiencing this on a -current from sources supped on Oct 03. > > turtledawn~;uname -a > FreeBSD turtledawn.blackhelicopters.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Oct 3 10:58:59 EDT 2000 mwlucas@turtledawn.blackhelicopters.org:/usr/obj/usr/src/sys/TURTLEDAWN i386 > turtledawn~; Here: FreeBSD fonix.hos.u-szeged.hu 5.0-CURRENT FreeBSD 5.0-CURRENT #23: Tue Oct 10 13 :05:58 CEST 2000 root@fonix.hos.u-szeged.hu:/usr/src/sys/compile/FONIX i386 and I have just checked (by rebooting) that 'boot -s' indeed works. > System is a Toshiba Satellite 2210 CDT. More info on request. OK, so this is a laptop, right? Mine is a desktop machine. May be relevant or maybe not. Another datapoint: I always do a full make world before building a new kernel (because I only need a new kernel at that time.) Maybe you should try with recent sources? (Well, I had to upgrade anyway, because I got a cool panic on each shutdown due to an ufs_extattr related bug that was fixed today... -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 11:19:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id 3D8A537B502 for ; Tue, 10 Oct 2000 11:19:44 -0700 (PDT) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.11.2.PreAlpha0/8.11.2.PreAlpha0) id e9AIJh272726; Tue, 10 Oct 2000 11:19:43 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14819.23999.720997.102041@horsey.gshapiro.net> Date: Tue, 10 Oct 2000 11:19:43 -0700 (PDT) From: Gregory Neil Shapiro To: freebsd-current@FreeBSD.ORG Subject: HEADS UP: sendmail related changes X-Mailer: VM 6.75 under 21.2 (beta36) "Notus" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following changes have been made in -CURRENT: 1. mail.local(8) is no longer installed as a set-user-id binary. If you are using a /etc/mail/sendmail.cf from the default sendmail.cf included with FreeBSD any time after 3.1.0, you are fine. If you are using a hand-configured sendmail.cf and mail.local for delivery, check to make sure the F=S flag is set on the Mlocal line. Those with .mc files who need to add the flag can do so by adding the following line to their your .mc file and regenerating the sendmail.cf file: MODIFY_MAILER_FLAGS(`LOCAL', `+S')dnl Note that FEATURE(`local_lmtp') already does this. 2. sendmail(8) is now built with STARTTLS support unless NO_OPENSSL is set. 3. The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY commands. 4. Now using sendmail's version of vacation(1). This change should be transparent except for the new options/features available. 5. The sendmail cf building tools (contrib/sendmail/cf) are installed in /usr/share/sendmail/cf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 12:16:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from pimout4-int.prodigy.net (pimout4-ext.prodigy.net [207.115.63.103]) by hub.freebsd.org (Postfix) with ESMTP id CFFE937B502 for ; Tue, 10 Oct 2000 12:16:18 -0700 (PDT) Received: from bimetic1 (adsl-64-123-1-97.dsl.austtx.swbell.net [64.123.1.97]) by pimout4-int.prodigy.net (8.10.1/8.10.1) with SMTP id e9AJGGZ132240 for ; Tue, 10 Oct 2000 15:16:17 -0400 Reply-To: From: "Campbell Angus" To: Subject: subscribe Date: Tue, 10 Oct 2000 14:15:15 -0500 Message-ID: <000501c032ee$6b81ae40$61017b40@bimetic1> 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 CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 14: 3:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.houston.rr.com (sm1.texas.rr.com [24.93.35.54]) by hub.freebsd.org (Postfix) with ESMTP id 49FE537B502 for ; Tue, 10 Oct 2000 14:03:43 -0700 (PDT) Received: from bloop.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Tue, 10 Oct 2000 16:05:39 -0500 Received: from bloop.craftncomp.com (localhost.craftncomp.com [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e9AL39G23508 for ; Tue, 10 Oct 2000 16:03:09 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200010102103.e9AL39G23508@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: Where has cvs-cur gone? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Oct 2000 16:03:08 -0500 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last one I can find in the FTP repository is cvs-cur.6772.gz. Where are the more recent ones? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 14:13:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 410A537B66D for ; Tue, 10 Oct 2000 14:13:37 -0700 (PDT) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id RAA05630; Tue, 10 Oct 2000 17:13:32 -0400 (EDT) (envelope-from mwlucas) Date: Tue, 10 Oct 2000 17:13:32 -0400 From: Michael Lucas To: Igor Timkin Cc: "Marc G. Fournier" , freebsd-current@FreeBSD.ORG Subject: Re: can't get into single user mode - panic: ffs_valloc: dup alloc Message-ID: <20001010171332.A5592@blackhelicopters.org> References: <20001010120717.A3746@blackhelicopters.org> <200010101750.VAA12934@logger.gamma.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200010101750.VAA12934@logger.gamma.ru>; from ivt@logger.gamma.ru on Tue, Oct 10, 2000 at 09:50:05PM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 10, 2000 at 09:50:05PM +0400, Igor Timkin wrote: > > > I hit the space bar, type in 'boot -s' and it goes through all the > > > normal start up procedures, sets up the networking, etc ... > > 'boot -s' don't work for me, I use 'boot /boot/kernel/kernel -s' instead. You're right. It's off to doc-land for this, I suppose. Although shouldn't BOOT_SINGLE still work? ==ml -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 15:35:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 6403237B503 for ; Tue, 10 Oct 2000 15:35:44 -0700 (PDT) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id XAA34975; Tue, 10 Oct 2000 23:35:42 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id XAA04578; Tue, 10 Oct 2000 23:08:49 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <20001010200811.A8273@freebie.demon.nl> References: ; from rb@gid.co.uk on Tue, Oct 10, 2000 at 01:35:57PM +0100 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 10 Oct 2000 23:08:47 +0100 To: Wilko Bulte From: Bob Bishop Subject: Re: ed0: warning - receiver ring buffer overrun Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 20:08 +0200 10/10/00, Wilko Bulte wrote: >On Tue, Oct 10, 2000 at 01:35:57PM +0100, Bob Bishop wrote: >> Hi, >> >> I'm seeing lots of: >> >> ed0: warning - receiver ring buffer overrun >> >> This box is building the world with sources via NFS. What gives? > >Something not servicing the ed0 card fast enough? That would be consistent with what I'm seeing. >FWIW: my -current build >on a PPro 200 took it's normal 3-something hours. NFS seems to be horrendously slow right now, my builds are taking 5 times as long as expected. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 15:35:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id A25BB37B679 for ; Tue, 10 Oct 2000 15:35:48 -0700 (PDT) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id XAA34976; Tue, 10 Oct 2000 23:35:46 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id XAA04586; Tue, 10 Oct 2000 23:12:58 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <20001010200811.A8273@freebie.demon.nl> References: ; from rb@gid.co.uk on Tue, Oct 10, 2000 at 01:35:57PM +0100 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 10 Oct 2000 23:12:56 +0100 To: Wilko Bulte From: Bob Bishop Subject: Re: ed0: warning - receiver ring buffer overrun Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, >> ed0: warning - receiver ring buffer overrun One more datapoint: I have two boxes doing this, both with ed but one is ISA, the other is PCI. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 16:31: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id BA30337B66C for ; Tue, 10 Oct 2000 16:30:57 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e9ANUnG18189 for ; Wed, 11 Oct 2000 08:30:50 +0900 (JST) Date: Wed, 11 Oct 2000 08:30:49 +0900 Message-ID: <7mvgv02s0m.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: current@FreeBSD.ORG Subject: Re: ed0: warning - receiver ring buffer overrun In-Reply-To: In your message of "10 Oct 2000 22:36:15 GMT" References: <20001010200811.A8273@freebie.demon.nl> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10 Oct 2000 22:36:15 GMT, Bob Bishop wrote: > One more datapoint: I have two boxes doing this, both with ed but one is > ISA, the other is PCI. I don't have statistics, but I feel very slow on my SMP box with recent -current (with NFS, fxp0). -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 18: 5:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id D99F537B502 for ; Tue, 10 Oct 2000 18:05:32 -0700 (PDT) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA14670; Wed, 11 Oct 2000 10:35:19 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 11 Oct 2000 10:35:19 +0930 (CST) From: "Daniel O'Connor" To: Bob Bishop Subject: RE: -current grinds exceeding slow Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Oct-00 Bob Bishop wrote: > make world kernel FreeBSD 5.0-CURRENT #11: Sat Sep 30 15:07:06 BST 2000 > >>> elf make world started on Fri Oct 6 08:33:20 BST 2000 > >>> elf make world completed on Fri Oct 6 13:30:13 BST 2000 > > ...just under 5hrs > > > make world kernel FreeBSD 5.0-CURRENT #0: Sun Oct 8 13:37:48 BST 2000 > >>> elf make world started on Sun Oct 8 15:09:39 BST 2000 > >>> elf make world completed on Mon Oct 9 16:35:00 BST 2000 > > ...over 25hrs > > The machine feels very sluggish too, and the snake sometimes wiggles to a > standstill. > > This is a UP box, I've got an SMP box with the same symptoms. 'Me too'. I notice it gets MUCH worse when using NFS, and just bad when using UFS (don't know if it is FS specific or just the fact that NFS is networked though). --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 18:31:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id AF0D937B503 for ; Tue, 10 Oct 2000 18:31:15 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e9B1VDG00584 for ; Wed, 11 Oct 2000 10:31:14 +0900 (JST) Date: Wed, 11 Oct 2000 10:31:13 +0900 Message-ID: <7mlmvwqi3i.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: savecore cannot find device? User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My boot message of today said: Oct 11 10:18:10 waterblue savecore: /dev/#C:116:0x20001: No such file or directory And swap entry in /etc/fstab is: /dev/ad0s1b none swap sw 0 0 This is non-DEVFS environment. Am I missing some point of updating? -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 18:56: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from volatile.chemicals.tacorp.com (ci391991-a.grnvle1.sc.home.com [24.9.31.75]) by hub.freebsd.org (Postfix) with ESMTP id 908C537B66C for ; Tue, 10 Oct 2000 18:55:57 -0700 (PDT) Received: (from morganw@localhost) by volatile.chemicals.tacorp.com (8.11.1/8.11.1) id e9B1tg890570; Tue, 10 Oct 2000 21:55:42 -0400 (EDT) (envelope-from morganw) Date: Tue, 10 Oct 2000 21:55:42 -0400 (EDT) From: Wesley Morgan To: Jun Kuriyama Cc: Current Subject: Re: savecore cannot find device? In-Reply-To: <7mlmvwqi3i.wl@waterblue.imgsrc.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mine has been saying something similar for a week or so now. I just figured it was me and ignored it. Manually running savecore gives no error and works fine. On Wed, 11 Oct 2000, Jun Kuriyama wrote: > My boot message of today said: > Oct 11 10:18:10 waterblue savecore: /dev/#C:116:0x20001: No such file or directory > > And swap entry in /etc/fstab is: > /dev/ad0s1b none swap sw 0 0 > > > This is non-DEVFS environment. Am I missing some point of updating? > > > -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ wesleymorgan@home.com _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 19:33:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 0152937B502 for ; Tue, 10 Oct 2000 19:33:50 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.1/8.11.1) id e9B2del00824; Tue, 10 Oct 2000 19:39:40 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200010110239.e9B2del00824@troutmask.apl.washington.edu> Subject: Re: savecore cannot find device? In-Reply-To: <7mlmvwqi3i.wl@waterblue.imgsrc.co.jp> from Jun Kuriyama at "Oct 11, 2000 10:31:13 am" To: Jun Kuriyama Date: Tue, 10 Oct 2000 19:39:40 -0700 (PDT) Cc: Current 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jun Kuriyama wrote: > My boot message of today said: > Oct 11 10:18:10 waterblue savecore: /dev/#C:116:0x20001:\ > No such file or directory > This is occurring on my machine also. It makes it fairly hard to get a crash. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 19:37:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 035ED37B66E for ; Tue, 10 Oct 2000 19:37:38 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.0/8.11.0) id e9B2bI229791; Wed, 11 Oct 2000 06:37:18 +0400 (MSD) (envelope-from ache) Date: Wed, 11 Oct 2000 06:37:15 +0400 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: Steve Kargl Cc: Jun Kuriyama , Current Subject: Re: savecore cannot find device? Message-ID: <20001011063714.A29773@nagual.pp.ru> References: <7mlmvwqi3i.wl@waterblue.imgsrc.co.jp> <200010110239.e9B2del00824@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010110239.e9B2del00824@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Tue, Oct 10, 2000 at 07:39:40PM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 10, 2000 at 07:39:40PM -0700, Steve Kargl wrote: > Jun Kuriyama wrote: > > My boot message of today said: > > Oct 11 10:18:10 waterblue savecore: /dev/#C:116:0x20001:\ > > No such file or directory > > > > This is occurring on my machine also. It makes it fairly > hard to get a crash. I got this too. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 19:38:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.chuckr.org (picnic.chuckr.org [216.254.96.118]) by hub.freebsd.org (Postfix) with ESMTP id D462837B66E for ; Tue, 10 Oct 2000 19:38:47 -0700 (PDT) Received: from localhost (chuckr@localhost) by picnic.chuckr.org (8.11.0/8.9.3) with ESMTP id e9B2d7v63342; Tue, 10 Oct 2000 22:39:07 -0400 (EDT) (envelope-from chuckr@picnic.chuckr.org) Date: Tue, 10 Oct 2000 22:39:06 -0400 (EDT) From: Chuck Robey To: Stephen Hocking Cc: current@FreeBSD.ORG Subject: Re: Where has cvs-cur gone? In-Reply-To: <200010102103.e9AL39G23508@bloop.craftncomp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Oct 2000, Stephen Hocking wrote: > Last one I can find in the FTP repository is cvs-cur.6772.gz. Where are the > more recent ones? I'm sorry, I have been recovering from recent surgery again, and just got back to reading email. The vinum volume that ctm resides on has disappeared, and all the usual suspects are being rounded up .... seriously, it looks like Ulf (who physically controls that machine) took them offline for some reason, I don't know why, I have an email off to him about it. Least I won't have to use that "recovering from surgery" excuse anymore. This last surgery, it finally worked! No more time in the body shop anymore!! yea!! Now I can get back to my main hobby (harrassing BSD folks .... bwahahahhah) I just got in touch with Ulf (just now). ctm-repair now in progress. > > > Stephen > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.chuckr.org| electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 19:43:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id 3A2C337B66C for ; Tue, 10 Oct 2000 19:43:50 -0700 (PDT) Received: from software-munitions.com (fwiw.plaintalk.bellevue.wa.us [206.129.5.157]) by btw.plaintalk.bellevue.wa.us (8.11.1/8.11.1) with ESMTP id e9B2hcs45826 for ; Tue, 10 Oct 2000 19:43:39 -0700 (PDT) Message-ID: <39E3D3DA.CCC0AFC4@software-munitions.com> Date: Tue, 10 Oct 2000 19:43:38 -0700 From: Dennis Glatting X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: ipfw and state expiration Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using IPFW with the keep-state primitive on DNS and NTP queries (e.g., [1]). I've noticed, however, the number of dynamic rules only increase -- there appears to be no pruning of the dynamic rules. Looking through the code I only see a call to prune dynamic rules (via remove_dyn_rule()) when the number of rules exceed some maximum, rather at some time interval to insure dynamic rules are short lived. Is this indeed the case? Aren't dynamic rules suppose to be short lived? Did I not configure something improperly? [1] $fwcmd add allow udp from any to ${wip} 53 via ${wif} keep-state To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 19:51:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id 469A137B66E for ; Tue, 10 Oct 2000 19:51:09 -0700 (PDT) Received: from software-munitions.com (fwiw.plaintalk.bellevue.wa.us [206.129.5.157]) by btw.plaintalk.bellevue.wa.us (8.11.1/8.11.1) with ESMTP id e9B2p8s45930 for ; Tue, 10 Oct 2000 19:51:08 -0700 (PDT) Message-ID: <39E3D59C.33D0779C@software-munitions.com> Date: Tue, 10 Oct 2000 19:51:08 -0700 From: Dennis Glatting X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: ipfw and state expiration References: <39E3D3DA.CCC0AFC4@software-munitions.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to follow up. It seems TCP states are expired but UDP states are not. Dennis Glatting wrote: > > I am using IPFW with the keep-state primitive on DNS and NTP queries > (e.g., [1]). I've noticed, however, the number of dynamic rules only > increase -- there appears to be no pruning of the dynamic rules. > Looking through the code I only see a call to prune dynamic rules (via > remove_dyn_rule()) when the number of rules exceed some maximum, > rather at some time interval to insure dynamic rules are short lived. > > Is this indeed the case? Aren't dynamic rules suppose to be short > lived? Did I not configure something improperly? > > [1] $fwcmd add allow udp from any to ${wip} 53 via ${wif} keep-state > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 19:58:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id 0CE1637B66D for ; Tue, 10 Oct 2000 19:58:13 -0700 (PDT) Received: (qmail 1963 invoked by uid 100); 11 Oct 2000 02:58:12 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14819.55108.312169.132976@guru.mired.org> Date: Tue, 10 Oct 2000 21:58:12 -0500 (CDT) To: current@freebsd.org Subject: video mpeg broken? X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that something has broken plaympeg - at least for video. In trying to play video back, I get a black window and no images. Audio playback seems fine. This is something I don't do often, so I'm not sure when it happened. Anyone else seeing this? Anyone working on it? Thanx, ; Tue, 10 Oct 2000 20:08:15 -0700 (PDT) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.11.1/8.11.0) id e9B36mK14819; Wed, 11 Oct 2000 10:06:48 +0700 (NOVST) (envelope-from nnd) Date: Wed, 11 Oct 2000 10:06:48 +0700 (NOVST) Message-Id: <200010110306.e9B36mK14819@wint.itfs.nsk.su> From: Nickolay Dudorov To: Mike Meyer Cc: current@freebsd.org Subject: Re: video mpeg broken? In-Reply-To: <14819.55108.312169.132976@guru.mired.org> User-Agent: tin/1.5.6-20000803 ("Dust") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <14819.55108.312169.132976@guru.mired.org> you wrote: > It seems that something has broken plaympeg - at least for video. In > trying to play video back, I get a black window and no images. Audio > playback seems fine. This is something I don't do often, so I'm not > sure when it happened. > > Anyone else seeing this? Anyone working on it? I've seen this "black window" with plaympeg also. It sometimes help if I move the window - after that I can see the video. (My system - -current with XFree86-4.01 and Matrox MGA G200 AGP, SDL -1.1.4, SMPEG - 0.4.0). N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 20:12:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id 8E6AC37B502 for ; Tue, 10 Oct 2000 20:12:11 -0700 (PDT) Received: (qmail 2417 invoked by uid 100); 11 Oct 2000 03:12:05 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14819.55941.832171.603489@guru.mired.org> Date: Tue, 10 Oct 2000 22:12:05 -0500 (CDT) To: Nickolay Dudorov Cc: current@FreeBSD.ORG Subject: Re: video mpeg broken? In-Reply-To: <200010110306.e9B36mK14819@wint.itfs.nsk.su> References: <14819.55108.312169.132976@guru.mired.org> <200010110306.e9B36mK14819@wint.itfs.nsk.su> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nickolay Dudorov writes: > In article <14819.55108.312169.132976@guru.mired.org> you wrote: > > It seems that something has broken plaympeg - at least for video. In > > trying to play video back, I get a black window and no images. Audio > > playback seems fine. This is something I don't do often, so I'm not > > sure when it happened. > I've seen this "black window" with plaympeg also. > It sometimes help if I move the window - after that I can see > the video. (My system - -current with XFree86-4.01 and > Matrox MGA G200 AGP, SDL -1.1.4, SMPEG - 0.4.0). Well, that doesn't work here. The system is -current (as of Saturday), XFree86-4.0.1, Diamond Viper 550, SDL-1.1.5, SMPEG-0.4.0. Thanx, To: Mike Meyer Cc: Nickolay Dudorov , ports@FreeBSD.org Subject: Re: video mpeg broken? Message-ID: <20001010211653.A35997@norn.cm.nu> References: <14819.55108.312169.132976@guru.mired.org> <200010110306.e9B36mK14819@wint.itfs.nsk.su> <14819.55941.832171.603489@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Mutt/1.2.5i-jp0 In-Reply-To: <14819.55941.832171.603489@guru.mired.org>; from mwm@mired.org on Tue, Oct 10, 2000 at 10:12:05PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 10, 2000 at 10:12:05PM -0500, Mike Meyer wrote: > Nickolay Dudorov writes: > > In article <14819.55108.312169.132976@guru.mired.org> you wrote: > > > It seems that something has broken plaympeg - at least for video. In > > > trying to play video back, I get a black window and no images. Audio > > > playback seems fine. This is something I don't do often, so I'm not > > > sure when it happened. > > I've seen this "black window" with plaympeg also. > > It sometimes help if I move the window - after that I can see > > the video. (My system - -current with XFree86-4.01 and > > Matrox MGA G200 AGP, SDL -1.1.4, SMPEG - 0.4.0). > > Well, that doesn't work here. The system is -current (as of Saturday), > XFree86-4.0.1, Diamond Viper 550, SDL-1.1.5, SMPEG-0.4.0. These messages are better suited to -ports. I've only seen this problem with 1.1.5, 1.1.4 works fine. It also affects smpeg-0.4.1. I haven't updated the port to that version yet because I can't tell if it works or not :-). -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 20:33:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from lavender.sanpei.org (nat06.st.keio.ac.jp [131.113.17.16]) by hub.freebsd.org (Postfix) with ESMTP id 8C5FB37B502; Tue, 10 Oct 2000 20:33:19 -0700 (PDT) Received: (from sanpei@localhost) by lavender.sanpei.org (8.11.0/3.7W) id e9B3XBP05435; Wed, 11 Oct 2000 12:33:11 +0900 (JST) Message-Id: <200010110333.e9B3XBP05435@lavender.sanpei.org> To: current@FreeBSD.org Cc: jkh@FreeBSD.org Subject: [Patch] card_irq was confused in release/sysinstall/pccard.c In-Reply-To: Your message of "Tue, 10 Oct 2000 12:42:09 +0900" X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 11 Oct 2000 12:33:06 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found card_irq was confused in release/sysinstall/pccard. In Some code, card_irq was used in global variable(variable_set2), and in others, char pointer.... and never set -i option for pccardd in installation time. 139 char *card_irq = ""; <--- char * 190 /* get card_irq out of CardIrq somehow */ 191 if (CardIrq) { 192 for (i = 0; i < IRQ_COUNT; i++) { 193 if ((CardIrq & IrqTable[i].my_bit) != 0) { 194 sprintf(temp, "%s %s", card_irq, IrqTable[i].my_flag); ~~~~~~~~ char * 195 variable_set2("card_irq", temp, 1); <-- global!! 196 } 197 } 198 } 237 strcat(pccardd_cmd, card_irq); <-- char * 240 variable_set2("pccardd_flags", card_irq, 1); <-- char * I think we need to fix like this. --- MIHIRA, Sanpei Yoshiro Yokohama, Japan. --- release/sysinstall/pccard.c.org Tue Oct 10 12:35:09 2000 +++ release/sysinstall/pccard.c Tue Oct 10 12:36:24 2000 @@ -136,7 +136,7 @@ int pcic_mem = 0xd0000; int beep_newstat; char card_device[16]; - char *card_irq = ""; + char card_irq[256] = ""; char temp[256]; char *spcic_mem; char pccardd_cmd[256]; @@ -192,7 +192,7 @@ for (i = 0; i < IRQ_COUNT; i++) { if ((CardIrq & IrqTable[i].my_bit) != 0) { sprintf(temp, "%s %s", card_irq, IrqTable[i].my_flag); - variable_set2("card_irq", temp, 1); + strcpy(card_irq, temp); } } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 21:11:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id AAD8C37B502 for ; Tue, 10 Oct 2000 21:11:39 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 14ACE28732; Wed, 11 Oct 2000 11:11:29 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 01DAA2865C for ; Wed, 11 Oct 2000 11:11:28 +0700 (ALMST) Date: Wed, 11 Oct 2000 11:11:28 +0700 (ALMST) From: Boris Popov To: freebsd-current@freebsd.org Subject: 'dup alloc' panic - more details needed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Call to all who experienced this panic - please provide mount(8) output for filesystem in question, so one can gather statistic about mount/ffs options. It seems that the one of the recent commits just disclosed a very old bug somewhere in ffs and/or VFS. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 22:50:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 4A62C37B66D for ; Tue, 10 Oct 2000 22:50:07 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id QAA24413; Wed, 11 Oct 2000 16:49:50 +1100 Date: Wed, 11 Oct 2000 16:49:45 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Jun Kuriyama Cc: Current Subject: Re: savecore cannot find device? In-Reply-To: <7mlmvwqi3i.wl@waterblue.imgsrc.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Oct 2000, Jun Kuriyama wrote: > My boot message of today said: > Oct 11 10:18:10 waterblue savecore: /dev/#C:116:0x20001: No such file or directory > > And swap entry in /etc/fstab is: > /dev/ad0s1b none swap sw 0 0 > > This is non-DEVFS environment. Am I missing some point of updating? Probably that you shouldn't have downgraded savecore by updating it :-). savecore now uses devname() but devname() is too unreliable to use for anything except informational output. There are several failure modes. When devname() can't find the device name by looking up dev.db or using sysctl kern.devname, it invents a name of the above form. Apparently, the device name "ad0s1b" is not understood by the kernel when savecore is run (early in /etc/rc). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 23:41: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from msa.hinet.net (msa.hinet.net [168.95.4.211]) by hub.freebsd.org (Postfix) with ESMTP id EDCC637B502 for ; Tue, 10 Oct 2000 23:40:58 -0700 (PDT) Received: from CoreBit.com (h40.s180.ts.hinet.net [168.95.180.40]) by msa.hinet.net (8.8.8/8.8.8) with ESMTP id OAA21820 for ; Wed, 11 Oct 2000 14:40:44 +0800 (CST) Message-ID: <39E40B8F.409B352F@CoreBit.com> Date: Wed, 11 Oct 2000 14:41:19 +0800 From: Donny Lee X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.org Subject: package for fetch mails? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, My fbsd box is (ADSL) connected to the net through dynamic IPs, so no mails are able to send in, they go to the account offered by my ISP. i need to check mail manually a period of time. Is there any package that can be used to fetch mails back to my fbsd box in every 10 or 20 min. automatically? -- // Donny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 23:46:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id C281B37B503 for ; Tue, 10 Oct 2000 23:46:41 -0700 (PDT) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 323895D84; Wed, 11 Oct 2000 08:46:36 +0200 (CEST) Date: Wed, 11 Oct 2000 08:46:36 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Donny Lee Cc: FreeBSD-current@FreeBSD.org Subject: Re: package for fetch mails? In-Reply-To: <39E40B8F.409B352F@CoreBit.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My fbsd box is (ADSL) connected to the net through dynamic IPs, > so no mails are able to send in, they go to the account offered > by my ISP. i need to check mail manually a period of time. > > Is there any package that can be used to fetch mails back to > my fbsd box in every 10 or 20 min. automatically? Yes, check out fetchmail: http://www.freebsd.org/cgi/ports.cgi?query=fetchmail&stype=all But in the future please send such questions to the freebsd-questions mailing list, not to freebsd-current. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 23:51: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from ockle.nanoteq.co.za (ockle.nanoteq.co.za [196.37.91.32]) by hub.freebsd.org (Postfix) with ESMTP id 0705937B502 for ; Tue, 10 Oct 2000 23:50:40 -0700 (PDT) Received: (from johan@localhost) by ockle.nanoteq.co.za (8.9.3/8.9.3) id JAA18085; Wed, 11 Oct 2000 09:02:05 +0200 (SAST) (envelope-from johan) 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: <39E40B8F.409B352F@CoreBit.com> Date: Wed, 11 Oct 2000 09:02:05 +0200 (SAST) Reply-To: jkruger@oskar.nanoteq.co.za Organization: Nanoteq From: Johan Kruger To: Donny Lee Subject: RE: package for fetch mails? Cc: FreeBSD-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Use xfmail, a little bit old proggie, but very practical and generic. Set it up to check your mail every x minutes, using the mail server as a pop3 server ( xfmail wil log in, give your password to the server, retrieve the mail, and spool it to a file usually /var/mail/your_user_account_on_your_pc which will keep the messages) Try it , neat little proggie P.S. If you use current ,download the port and rebuild it using xforms-0.88.1 libraries On 11-Oct-00 Donny Lee wrote: > > Hi there, > > My fbsd box is (ADSL) connected to the net through dynamic IPs, > so no mails are able to send in, they go to the account offered > by my ISP. i need to check mail manually a period of time. > > Is there any package that can be used to fetch mails back to > my fbsd box in every 10 or 20 min. automatically? > > -- > // Donny > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- Unix Software Developer/Engineer E-Mail: Johan Kruger Date: 11-Oct-00 Time: 08:57:16 All good things come to those who ... runs FreeBSD ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 10 23:56:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from msa.hinet.net (msa.hinet.net [168.95.4.211]) by hub.freebsd.org (Postfix) with ESMTP id 1983A37B503 for ; Tue, 10 Oct 2000 23:56:19 -0700 (PDT) Received: from CoreBit.com (h40.s180.ts.hinet.net [168.95.180.40]) by msa.hinet.net (8.8.8/8.8.8) with ESMTP id OAA29834 for ; Wed, 11 Oct 2000 14:56:13 +0800 (CST) Message-ID: <39E40F2B.1C2186F1@CoreBit.com> Date: Wed, 11 Oct 2000 14:56:43 +0800 From: Donny Lee X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSd-current@FreeBSD.org Subject: Re: package for fetch mails? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Blaz Zupan wrote: > Yes, check out fetchmail: > http://www.freebsd.org/cgi/ports.cgi?query=fetchmail&stype=all > But in the future please send such questions to the freebsd-questions mailing > list, not to freebsd-current. Thanks to all replies, and sorry too. I figure i do put the question in a wrong place after i posted. -- // Donny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 1:53:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id C9CC637B503 for ; Wed, 11 Oct 2000 01:53:12 -0700 (PDT) Received: (qmail 54146 invoked by uid 100); 11 Oct 2000 08:53:07 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14820.10867.8261.441382@guru.mired.org> Date: Wed, 11 Oct 2000 03:53:07 -0500 (CDT) To: current@freebsd.org Subject: Upgrading -stable -> -current, boot failure? X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a system with 4.1-STABLE installed. I mount -current sources on it, do make buildworld/buildkernel/installkernel/installworld and reboot. The boot loader runs, gives me the "booting default in..." countdown, prints "|", and then stops. After thrashing the disks (with *no* boot messages), I get a prompt from init. Since the same sources build and boot properly elsewhere, I assume I've missed a step. I normally run mergemaster after installworld and rebooting singleuser. Could someone provide the clue I've not got? thanx, ; Wed, 11 Oct 2000 02:39:51 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e9B9dWN80456; Wed, 11 Oct 2000 11:39:33 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: Jun Kuriyama , Current Subject: Re: savecore cannot find device? In-Reply-To: Your message of "Wed, 11 Oct 2000 16:49:45 +1100." Date: Wed, 11 Oct 2000 11:39:32 +0200 Message-ID: <80454.971257172@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Bruce Ev ans writes: >Probably that you shouldn't have downgraded savecore by updating it >:-). savecore now uses devname() but devname() is too unreliable to >use for anything except informational output. It always were: boot log in mv /dev/something /dev/other # devname(3) gives wrong output -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 2:53:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 4100037B66D for ; Wed, 11 Oct 2000 02:53:16 -0700 (PDT) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.11.0/8.11.0) with ESMTP id e9B9rBB26123; Wed, 11 Oct 2000 11:53:11 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.11.0/8.11.0) with ESMTP id e9B9rB820139; Wed, 11 Oct 2000 11:53:11 +0200 (MET DST) Received: (from localhost) by curry.mchp.siemens.de (8.11.0/8.11.0) id e9B9rBJ34534; Date: Wed, 11 Oct 2000 11:53:10 +0200 From: Andre Albsmeier To: Chuck Robey Cc: current@FreeBSD.ORG Subject: Re: Where has cvs-cur gone? Message-ID: <20001011115310.A68893@curry.mchp.siemens.de> References: <200010102103.e9AL39G23508@bloop.craftncomp.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 chuckr@picnic.chuckr.org on Tue, Oct 10, 2000 at 10:39:06PM -0400 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10-Oct-2000 at 22:39:06 -0400, Chuck Robey wrote: > On Tue, 10 Oct 2000, Stephen Hocking wrote: > > > Last one I can find in the FTP repository is cvs-cur.6772.gz. Where are the > > more recent ones? > > I'm sorry, I have been recovering from recent surgery again, and just got > back to reading email. The vinum volume that ctm resides on has > disappeared, and all the usual suspects are being rounded up > .... seriously, it looks like Ulf (who physically controls that > machine) took them offline for some reason, I don't know why, I have an > email off to him about it. > > Least I won't have to use that "recovering from surgery" excuse > anymore. This last surgery, it finally worked! No more time in the body > shop anymore!! yea!! Now I can get back to my main hobby (harrassing BSD > folks .... bwahahahhah) > > I just got in touch with Ulf (just now). ctm-repair now in progress. Great, thanks. In my desperation I sent a PR for this: 21909 I think it can be closed then... -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 5:24:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 6658337B66D for ; Wed, 11 Oct 2000 05:24:17 -0700 (PDT) Received: from [194.97.50.135] (helo=mx2.freenet.de) by mout0.freenet.de with esmtp (Exim 3.16 #20) id 13jKve-0007z1-00; Wed, 11 Oct 2000 14:24:14 +0200 Received: from a3876.pppool.de ([213.6.56.118] helo=Magelan.Leidinger.net) by mx2.freenet.de with esmtp (Exim 3.16 #20) id 13jKve-0002vy-00; Wed, 11 Oct 2000 14:24:14 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.1/8.11.1) with ESMTP id e9BAZPn01847; Wed, 11 Oct 2000 12:35:26 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200010111035.e9BAZPn01847@Magelan.Leidinger.net> Date: Wed, 11 Oct 2000 12:35:24 +0200 (CEST) From: Alexander Leidinger Subject: Re: can't get into single user mode - panic: ffs_valloc: dup alloc To: mwlucas@blackhelicopters.org Cc: ivt@logger.gamma.ru, scrappy@hub.org, freebsd-current@FreeBSD.ORG In-Reply-To: <20001010171332.A5592@blackhelicopters.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10 Oct, Michael Lucas wrote: >> > > I hit the space bar, type in 'boot -s' and it goes through all the >> > > normal start up procedures, sets up the networking, etc ... >> >> 'boot -s' don't work for me, I use 'boot /boot/kernel/kernel -s' instead. > > You're right. It's off to doc-land for this, I suppose. No, it was a bug in /boot/loader.4th(?) and it's fixed since 1-2 days. You are reading your cvs-all mail? Bye, Alexander. -- If Bill Gates had a dime for every time a Windows box crashed... ...Oh, wait a minute, he already does. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 5:46:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (gate.interxion.com [194.153.74.13]) by hub.freebsd.org (Postfix) with ESMTP id 60CF137B503; Wed, 11 Oct 2000 05:46:51 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id e9BCklC12390; Wed, 11 Oct 2000 14:46:47 +0200 (CEST) (envelope-from adrian) Date: Wed, 11 Oct 2000 14:45:27 +0200 From: Adrian Chadd To: freebsd-fs@freebsd.org Cc: freebsd-current@freebsd.org Subject: IFS commit candidate Message-ID: <20001011144527.A12272@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've brought IFS up to the latest -current and it has survived my testing and stressing. I am currently debugging a version of squid which will handle an IFS disk to provide solid performance details. You can find the IFS code plus modified copies of mount and fsck at http://www.freebsd.org/~adrian/ifs/ . Please take a look and comment as I am looking to commit this sometime within the next week or two into -current. Thanks! Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 6: 5: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (Postfix) with ESMTP id 7E2CA37B503 for ; Wed, 11 Oct 2000 06:05:00 -0700 (PDT) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.9.3/8.9.3) with ESMTP id PAA20313; Wed, 11 Oct 2000 15:05:28 +0200 (CEST) (envelope-from k@numeri.campus.luth.se) Message-Id: <200010111305.PAA20313@numeri.campus.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andre Albsmeier Cc: current@FreeBSD.ORG Subject: Re: Where has cvs-cur gone? In-Reply-To: Your message of "Wed, 11 Oct 2000 11:53:10 +0200." <20001011115310.A68893@curry.mchp.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Oct 2000 15:05:28 +0200 From: Johan Karlsson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Wed, 11 Oct 2000 11:53:10 +0200, Andre Albsmeier wrote: > > Great, thanks. In my desperation I sent a PR for this: 21909 > I think it can be closed then... > > -Andre Hi Please submit close request as follow-ups to the PR in question in the future. That way they do not get lost in the black hole called freebsd-current. I have closed your PR. Thanks Johan K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 6:10:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 544C137B502 for ; Wed, 11 Oct 2000 06:10:27 -0700 (PDT) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer goliath.siemens.de) Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.11.0/8.11.0) with ESMTP id e9BD71q00741; Wed, 11 Oct 2000 15:07:01 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail3.siemens.de (8.11.0/8.11.0) with ESMTP id e9BD71317117534; Wed, 11 Oct 2000 15:07:01 +0200 (MEST) Received: (from localhost) by curry.mchp.siemens.de (8.11.0/8.11.0) id e9BD71J35415; Date: Wed, 11 Oct 2000 15:07:01 +0200 From: Andre Albsmeier To: Johan Karlsson Cc: Andre Albsmeier , current@FreeBSD.ORG Subject: Re: Where has cvs-cur gone? Message-ID: <20001011150701.B76212@curry.mchp.siemens.de> References: <20001011115310.A68893@curry.mchp.siemens.de> <200010111305.PAA20313@numeri.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010111305.PAA20313@numeri.campus.luth.se>; from k@numeri.campus.luth.se on Wed, Oct 11, 2000 at 03:05:28PM +0200 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11-Oct-2000 at 15:05:28 +0200, Johan Karlsson wrote: > At Wed, 11 Oct 2000 11:53:10 +0200, Andre Albsmeier wrote: > > > > Great, thanks. In my desperation I sent a PR for this: 21909 > > I think it can be closed then... > > > > -Andre > > > Hi > Please submit close request as follow-ups to the PR in question > in the future. That way they do not get lost in the black hole called > freebsd-current. Sure, I would have done so as soon as CTMs are working again. > > I have closed your PR. OK, no problem. -Andre > > Thanks > Johan K -- BSD, from the people who brought you TCP/IP. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 9:27: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 2D89937B66C; Wed, 11 Oct 2000 09:26:56 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id e9BGQrW89641; Wed, 11 Oct 2000 19:26:53 +0300 (EEST) (envelope-from ru) Date: Wed, 11 Oct 2000 19:26:53 +0300 From: Ruslan Ermilov To: current@FreeBSD.org Subject: Re: pam.conf and r(logind|shd) Message-ID: <20001011192653.B88648@sunbay.com> Mail-Followup-To: current@FreeBSD.org References: <20001006204327.A8112@sunbay.com> <20001010200340.B42287@sunbay.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="tjCHc7DPkfUGtrlw" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001010200340.B42287@sunbay.com>; from ru@FreeBSD.org on Tue, Oct 10, 2000 at 08:03:40PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --tjCHc7DPkfUGtrlw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I am going to nuke the PAM support for rshd and rlogind in -current tomorrow (local time) if I won't get any objections till that date. -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --tjCHc7DPkfUGtrlw Content-Type: message/rfc822 Content-Disposition: inline Return-Path: Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id e9AH3em42884; Tue, 10 Oct 2000 20:03:40 +0300 (EEST) (envelope-from ru) Date: Tue, 10 Oct 2000 20:03:40 +0300 From: Ruslan Ermilov To: Robert Watson , Mark Murray Cc: Warner Losh , security-officer@FreeBSD.org Subject: Re: pam.conf and r(logind|shd) Message-ID: <20001010200340.B42287@sunbay.com> References: <20001006204327.A8112@sunbay.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 rwatson@FreeBSD.org on Fri, Oct 06, 2000 at 02:28:57PM -0400 On Fri, Oct 06, 2000 at 02:28:57PM -0400, Robert Watson wrote: > > On Fri, 6 Oct 2000, Ruslan Ermilov wrote: > > > On Fri, Oct 06, 2000 at 11:19:37AM -0600, Warner Losh wrote: > > > In message <20001006201540.B7215@sunbay.com> Ruslan Ermilov writes: > > > : I've just committed a fix to rlogind(8) to make it compile without -DNO_PAM. > > > : Now, (in both -current and -stable), to enable rlogind(8) and sshd(8) user > > > : will have to enable them in both /etc/inetd.conf and /etc/pam.conf. > > > > > > I'm not sure that I like changes like this being merged into -stable > > > so quickly. This change I'm having problems understanding, so I'll > > > need some time to go look at them and see what I think. > > > > > You are (being the Security Officer) don't like the change which > > doubly-disables r-foo tools?! I can't believe that :-) > > The change aspects that are worrying are: > > 1) Substantial structural change to the authentication path by moving to > PAM for r*, and in the -STABLE branch no less. This is a comment based > on the clarity of the commit message, so I'm not willing to commit > to more criticism than this, as I haven't read the patches, just the > commit message. If the code being run is still the same, clearly it > doesn't make much difference. > > 2) Additional (and in my mind, unnecessary) authorization point for r* > enabling in /etc/pam.conf. Is there a reason why it isn't enough to > just have the traditional service toggle in inetd.conf? We have > entries in pam.conf so that numerous default-disabled features are > enableable without modifying pam.conf, include xdm which isn't even > in the base source tree. Increasing configuration complexity can > dramatically increase the risk associated with possible > misconfigurations as well as operator frustration, rather than improve > practical security. > Actually, I also think that both rlogind(8) and rshd(8) should be PAM-free. The reasons are: 1) rlogind(8) calls login(1) (with -f if user passed .rhosts authentication), which itself is a PAM-enabled application. Moreover, the current PAM code in rlogind(8) is broken, if you try something interactive, say pam_unix.so in /etc/pam.conf for `rshd' entry. 2) rshd(8) is not suitable for interactive PAM modules, since it does not allocate a pty(4). Hence, I am asking Mark for approval to remove the PAM bits from rshd, rlogind, and pam.conf. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --tjCHc7DPkfUGtrlw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 10:53:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 5812137B66C; Wed, 11 Oct 2000 10:53:26 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13jQ49-000BNW-00; Wed, 11 Oct 2000 19:53:21 +0200 Received: from grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.1/8.11.1) with ESMTP id e9BHrbq87539; Wed, 11 Oct 2000 19:53:37 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200010111753.e9BHrbq87539@grimreaper.grondar.za> To: Ruslan Ermilov Cc: current@FreeBSD.org Subject: Re: pam.conf and r(logind|shd) References: <20001011192653.B88648@sunbay.com> In-Reply-To: <20001011192653.B88648@sunbay.com> ; from Ruslan Ermilov "Wed, 11 Oct 2000 19:26:53 +0300." Date: Wed, 11 Oct 2000 19:53:37 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am going to nuke the PAM support for rshd and rlogind in -current > tomorrow (local time) if I won't get any objections till that date. Agreed. login(8) is the right "focus" for PAM in this case. M > -- > Ruslan Ermilov Oracle Developer/DBA, > ru@sunbay.com Sunbay Software AG, > ru@FreeBSD.org FreeBSD committer, > +380.652.512.251 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age > > --tjCHc7DPkfUGtrlw > Content-Type: message/rfc822 > Content-Disposition: inline > > Return-Path: > Received: (from ru@localhost) > by whale.sunbay.crimea.ua (8.11.0/8.11.0) id e9AH3em42884; > Tue, 10 Oct 2000 20:03:40 +0300 (EEST) > (envelope-from ru) > Date: Tue, 10 Oct 2000 20:03:40 +0300 > From: Ruslan Ermilov > To: Robert Watson , Mark Murray > Cc: Warner Losh , security-officer@FreeBSD.org > Subject: Re: pam.conf and r(logind|shd) > Message-ID: <20001010200340.B42287@sunbay.com> > References: <20001006204327.A8112@sunbay.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 rwatson@FreeBSD.org on Fri, Oct 06, 2000 at 02:28:57PM -0400 > > On Fri, Oct 06, 2000 at 02:28:57PM -0400, Robert Watson wrote: > > > > On Fri, 6 Oct 2000, Ruslan Ermilov wrote: > > > > > On Fri, Oct 06, 2000 at 11:19:37AM -0600, Warner Losh wrote: > > > > In message <20001006201540.B7215@sunbay.com> Ruslan Ermilov writes: > > > > : I've just committed a fix to rlogind(8) to make it compile without -D NO_PAM. > > > > : Now, (in both -current and -stable), to enable rlogind(8) and sshd(8) user > > > > : will have to enable them in both /etc/inetd.conf and /etc/pam.conf. > > > > > > > > I'm not sure that I like changes like this being merged into -stable > > > > so quickly. This change I'm having problems understanding, so I'll > > > > need some time to go look at them and see what I think. > > > > > > > You are (being the Security Officer) don't like the change which > > > doubly-disables r-foo tools?! I can't believe that :-) > > > > The change aspects that are worrying are: > > > > 1) Substantial structural change to the authentication path by moving to > > PAM for r*, and in the -STABLE branch no less. This is a comment based > > on the clarity of the commit message, so I'm not willing to commit > > to more criticism than this, as I haven't read the patches, just the > > commit message. If the code being run is still the same, clearly it > > doesn't make much difference. > > > > 2) Additional (and in my mind, unnecessary) authorization point for r* > > enabling in /etc/pam.conf. Is there a reason why it isn't enough to > > just have the traditional service toggle in inetd.conf? We have > > entries in pam.conf so that numerous default-disabled features are > > enableable without modifying pam.conf, include xdm which isn't even > > in the base source tree. Increasing configuration complexity can > > dramatically increase the risk associated with possible > > misconfigurations as well as operator frustration, rather than improve > > practical security. > > > Actually, I also think that both rlogind(8) and rshd(8) should be PAM-free. > The reasons are: > > 1) rlogind(8) calls login(1) (with -f if user passed .rhosts authentication), > which itself is a PAM-enabled application. Moreover, the current PAM code > in rlogind(8) is broken, if you try something interactive, say pam_unix.so > in /etc/pam.conf for `rshd' entry. > > 2) rshd(8) is not suitable for interactive PAM modules, since it does not > allocate a pty(4). > > Hence, I am asking Mark for approval to remove the PAM bits from rshd, > rlogind, and pam.conf. > > > Cheers, > -- > Ruslan Ermilov Oracle Developer/DBA, > ru@sunbay.com Sunbay Software AG, > ru@FreeBSD.org FreeBSD committer, > +380.652.512.251 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age > > --tjCHc7DPkfUGtrlw-- > -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 11:39:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from merc95.us.sas.com (merc95.us.sas.com [149.173.6.5]) by hub.freebsd.org (Postfix) with ESMTP id ADB9D37B503 for ; Wed, 11 Oct 2000 11:39:16 -0700 (PDT) Received: from merc95.us.sas.com ([127.0.0.1]) by merc95.us.sas.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2651.58) id 4W38ZGQD; Wed, 11 Oct 2000 14:39:15 -0400 Received: from 10.28.149.26 by merc95.us.sas.com (InterScan E-Mail VirusWall NT); Wed, 11 Oct 2000 14:39:14 -0400 (Eastern Daylight Time) Received: from frink.unx.sas.com (frink.unx.sas.com [10.26.1.13]) by mozart.unx.sas.com (8.9.3 (PHNE_18979)/8.9.3) with ESMTP id OAA20101; Wed, 11 Oct 2000 14:39:14 -0400 (EDT) Received: (from dagill@localhost) by frink.unx.sas.com (8.11.0/8.9.1) id e9BIdD109717; Wed, 11 Oct 2000 14:39:13 -0400 (EDT) (envelope-from dagill) Date: Wed, 11 Oct 2000 14:39:13 -0400 From: Dave Gillham To: Mark Murray Cc: current@FreeBSD.org Subject: Re: pam.conf and r(logind|shd) Message-ID: <20001011143913.A8461@unx.sas.com> References: <20001011192653.B88648@sunbay.com> <200010111753.e9BHrbq87539@grimreaper.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010111753.e9BHrbq87539@grimreaper.grondar.za>; from mark@grondar.za on Wed, Oct 11, 2000 at 07:53:37PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am going to nuke the PAM support for rshd and rlogind in -current > > tomorrow (local time) if I won't get any objections till that date. > > Agreed. login(8) is the right "focus" for PAM in this case. We currently utilize PAM in rshd to restrict access to certain servers based on local criteria when users attempt to rsh non-interactively (in which, I believe, login(8) is not called). We don't object to PAM being removed, but we would like to see an equivalent mechanism supported. -dave > > > -- > > Ruslan Ermilov Oracle Developer/DBA, > > ru@sunbay.com Sunbay Software AG, > > ru@FreeBSD.org FreeBSD committer, > > +380.652.512.251 Simferopol, Ukraine > > > > http://www.FreeBSD.org The Power To Serve > > http://www.oracle.com Enabling The Information Age > > > > --tjCHc7DPkfUGtrlw > > Content-Type: message/rfc822 > > Content-Disposition: inline > > > > Return-Path: > > Received: (from ru@localhost) > > by whale.sunbay.crimea.ua (8.11.0/8.11.0) id e9AH3em42884; > > Tue, 10 Oct 2000 20:03:40 +0300 (EEST) > > (envelope-from ru) > > Date: Tue, 10 Oct 2000 20:03:40 +0300 > > From: Ruslan Ermilov > > To: Robert Watson , Mark Murray > > Cc: Warner Losh , security-officer@FreeBSD.org > > Subject: Re: pam.conf and r(logind|shd) > > Message-ID: <20001010200340.B42287@sunbay.com> > > References: <20001006204327.A8112@sunbay.com> 5844I-100000@fledge.watson.org> > > Mime-Version: 1.0 > > Content-Type: text/plain; charset=us-ascii > > Content-Disposition: inline > > User-Agent: Mutt/1.2.5i > > In-Reply-To: ; > from rwatson@FreeBSD.org on Fri, Oct 06, 2000 at 02:28:57PM -0400 > > > > On Fri, Oct 06, 2000 at 02:28:57PM -0400, Robert Watson wrote: > > > > > > On Fri, 6 Oct 2000, Ruslan Ermilov wrote: > > > > > > > On Fri, Oct 06, 2000 at 11:19:37AM -0600, Warner Losh wrote: > > > > > In message <20001006201540.B7215@sunbay.com> Ruslan Ermilov writes: > > > > > : I've just committed a fix to rlogind(8) to make it compile without -D > NO_PAM. > > > > > : Now, (in both -current and -stable), to enable rlogind(8) and sshd(8) > user > > > > > : will have to enable them in both /etc/inetd.conf and /etc/pam.conf. > > > > > > > > > > I'm not sure that I like changes like this being merged into -stable > > > > > so quickly. This change I'm having problems understanding, so I'll > > > > > need some time to go look at them and see what I think. > > > > > > > > > You are (being the Security Officer) don't like the change which > > > > doubly-disables r-foo tools?! I can't believe that :-) > > > > > > The change aspects that are worrying are: > > > > > > 1) Substantial structural change to the authentication path by moving to > > > PAM for r*, and in the -STABLE branch no less. This is a comment based > > > on the clarity of the commit message, so I'm not willing to commit > > > to more criticism than this, as I haven't read the patches, just the > > > commit message. If the code being run is still the same, clearly it > > > doesn't make much difference. > > > > > > 2) Additional (and in my mind, unnecessary) authorization point for r* > > > enabling in /etc/pam.conf. Is there a reason why it isn't enough to > > > just have the traditional service toggle in inetd.conf? We have > > > entries in pam.conf so that numerous default-disabled features are > > > enableable without modifying pam.conf, include xdm which isn't even > > > in the base source tree. Increasing configuration complexity can > > > dramatically increase the risk associated with possible > > > misconfigurations as well as operator frustration, rather than improve > > > practical security. > > > > > Actually, I also think that both rlogind(8) and rshd(8) should be PAM-free. > > The reasons are: > > > > 1) rlogind(8) calls login(1) (with -f if user passed .rhosts authentication), > > which itself is a PAM-enabled application. Moreover, the current PAM code > > in rlogind(8) is broken, if you try something interactive, say pam_unix.so > > in /etc/pam.conf for `rshd' entry. > > > > 2) rshd(8) is not suitable for interactive PAM modules, since it does not > > allocate a pty(4). > > > > Hence, I am asking Mark for approval to remove the PAM bits from rshd, > > rlogind, and pam.conf. > > > > > > Cheers, > > -- > > Ruslan Ermilov Oracle Developer/DBA, > > ru@sunbay.com Sunbay Software AG, > > ru@FreeBSD.org FreeBSD committer, > > +380.652.512.251 Simferopol, Ukraine > > > > http://www.FreeBSD.org The Power To Serve > > http://www.oracle.com Enabling The Information Age > > > > --tjCHc7DPkfUGtrlw-- > > > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- David Gillham, x3835 dagill@unx.sas.com SAS Institue Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 11:42:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id C89C737B66E for ; Wed, 11 Oct 2000 11:42:44 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9BIfei92164; Wed, 11 Oct 2000 11:41:40 -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: Date: Wed, 11 Oct 2000 11:42:14 -0700 (PDT) From: John Baldwin To: Bob Bishop Subject: RE: -current grinds exceeding slow Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Oct-00 Bob Bishop wrote: > Hi, > > What's happened recently to make -current so slow? > > make world kernel FreeBSD 5.0-CURRENT #11: Sat Sep 30 15:07:06 BST 2000 >>>> elf make world started on Fri Oct 6 08:33:20 BST 2000 >>>> elf make world completed on Fri Oct 6 13:30:13 BST 2000 > > ...just under 5hrs > > > make world kernel FreeBSD 5.0-CURRENT #0: Sun Oct 8 13:37:48 BST 2000 >>>> elf make world started on Sun Oct 8 15:09:39 BST 2000 >>>> elf make world completed on Mon Oct 9 16:35:00 BST 2000 > > ...over 25hrs > > The machine feels very sluggish too, and the snake sometimes wiggles to a > standstill. I don't know. Can you try to narrow down the date by cvsupping or cvs updating with date tags to see when it started slowing down? > This is a UP box, I've got an SMP box with the same symptoms. -- 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-current" in the body of the message From owner-freebsd-current Wed Oct 11 11:42:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id D8C6C37B66D for ; Wed, 11 Oct 2000 11:42:43 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9BIffi92168; Wed, 11 Oct 2000 11:41:41 -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: <14820.10867.8261.441382@guru.mired.org> Date: Wed, 11 Oct 2000 11:42:15 -0700 (PDT) From: John Baldwin To: Mike Meyer Subject: RE: Upgrading -stable -> -current, boot failure? Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Oct-00 Mike Meyer wrote: > I've got a system with 4.1-STABLE installed. I mount -current sources > on it, do make buildworld/buildkernel/installkernel/installworld and > reboot. The boot loader runs, gives me the "booting default in..." > countdown, prints "|", and then stops. After thrashing the disks (with > *no* boot messages), I get a prompt from init. > > Since the same sources build and boot properly elsewhere, I assume > I've missed a step. I normally run mergemaster after installworld and > rebooting singleuser. Could someone provide the clue I've not got? You are missing /boot/device.hints. Boot the system and you can get into multiuser fine (or you should be able to, at least), then cp /sys/i386/conf/GENERIC.hints /boot/device.hints and edit to taste. > thanx, > -- 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-current" in the body of the message From owner-freebsd-current Wed Oct 11 12:28:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay2.inwind.it (relay2.inwind.it [212.141.53.73]) by hub.freebsd.org (Postfix) with ESMTP id 8855C37B6E2 for ; Wed, 11 Oct 2000 12:02:34 -0700 (PDT) Received: from bartequi.ottodomain.org (62.98.154.130) by relay2.inwind.it (5.1.046) id 39CB0979003BB142; Wed, 11 Oct 2000 21:01:58 +0200 From: Salvo Bartolotta Date: Wed, 11 Oct 2000 20:03:04 GMT Message-ID: <20001011.20030400@bartequi.ottodomain.org> Subject: Re: Upgrading -stable -> -current, boot failure? To: Mike Meyer Cc: freebsd-current@FreeBSD.ORG References: <14820.10867.8261.441382@guru.mired.org> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 10/11/00, 9:53:07 AM, Mike Meyer wrote regarding Upgrading -stable -> -current, boot failure?: > I've got a system with 4.1-STABLE installed. I mount -current sources > on it, do make buildworld/buildkernel/installkernel/installworld and > reboot. The boot loader runs, gives me the "booting default in..." > countdown, prints "|", and then stops. After thrashing the disks (with= > *no* boot messages), I get a prompt from init. > Since the same sources build and boot properly elsewhere, I assume > I've missed a step. I normally run mergemaster after installworld and > rebooting singleuser. Could someone provide the clue I've not got? > thanx, > Surely you configured the hints stuff ? Best regards, Salvo (running PRE_SMPNG without any problems -- so far) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 14:23:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.hexanet.fr (speedfreak.hexanet.fr [194.98.140.14]) by hub.freebsd.org (Postfix) with ESMTP id E265E37B503 for ; Wed, 11 Oct 2000 14:23:44 -0700 (PDT) Received: from zippy (localhost [127.0.0.1]) by zippy.hexanet.fr (8.11.1/8.11.1) with ESMTP id e9BLPaY01076 for ; Wed, 11 Oct 2000 23:25:40 +0200 (CEST) (envelope-from nighty@zippy.hexanet.fr) Message-Id: <200010112125.e9BLPaY01076@zippy.hexanet.fr> Reply-To: chris@hexanet.fr From: "Christophe Prevotaux" X-Mailer: NMH 1.0.4 To: current@freebsd.org Subject: [HELP] Problems with new version of CURRENT MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1073.971299536.1@zippy> Date: Wed, 11 Oct 2000 23:25:36 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As you can see below after I cvsuped and made world today I got the following problems with my GATEWAY 2000 Solo 2150 Laptop and CURRENT Could someone help me solve these problems Module can't register problem random dev problem linux emulation can't load problem usb0 problem unknow ressources ( I think it can't recognize my sound card ) I am willing to test anything devellopers will want me to test on this machine in order to fix all these things among which the sound support for this laptop which is supposed to be es1371 ==== dmesg ================================ Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Wed Oct 11 14:45:37 CEST 2000 root@mydomain :/usr/obj/usr/src/sys/MYKERNEL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 167706624 (163776K bytes) avail memory = 158994432 (155268K bytes) Preloaded elf kernel "kernel" at 0xc03b2000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03b209c. Preloaded elf module "splash_bmp.ko" at 0xc03b20ec. Preloaded elf module "ipfw.ko" at 0xc03b2190. Preloaded elf module "random.ko" at 0xc03b222c. module_register: module random already exists! Module random failed to register: 17 Pentium Pro MTRR support enabled WARNING: Driver mistake: repeat make_dev("random") WARNING: Driver mistake: repeat make_dev("urandom") md0: Malloc disk module_register_init: MOD_LOAD (splash_bmp, c039a82c, 0) error 2 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 9 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1050-0x105f at device 7.1 on pci0 atapci0: Busmastering DMA enabled ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x1060-0x107f at device 7.2 on pci0 uhci0: Invalid irq 255 uhci0: Please switch on USB support and switch PNP-OS to 'No' in BIOS device_probe_and_attach: uhci0 attach returned 6 pci0: at 7.3 pcic-pci0: irq 9 at device 8.0 on pci0 pcic-pci0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] pcic-pci1: irq 9 at device 8.1 on pci0 pcic-pci1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] pci0: (vendor=0x1102, dev=0x8938) at 9.0 irq 5 pci0: at 10.0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pcic0: at port 0x3e0 iomem 0xd0000 on isa0 pcic0: Polling mode pccard0: on pcic0 pccard1: on pcic0 pmtimer0 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled ad0: 11513MB [23392/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a pccard: card inserted, slot 0 pccard: card inserted, slot 1 ed1 at port 0x240-0x25f irq 3 slot 0 on pccard0 ed1: address 00:00:e8:7f:0f:34, type NE2000 (16 bit) module_register: module isa/ed already exists! Module isa/ed failed to register: 17 module_register: module isa/ed already exists! Module isa/ed failed to register: 17 module_register: module pccard/ed already exists! Module pccard/ed failed to register: 17 module_register: module pci/ed already exists! Module pci/ed failed to register: 17 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: configured irq 3 not in bitmap of probed irqs 0 uhci0: port 0x1060-0x107f at device 7.2 on pci0 uhci0: Invalid irq 255 uhci0: Please switch on USB support and switch PNP-OS to 'No' in BIOS device_probe_and_attach: uhci0 attach returned 6 -- =================================================================== Christophe Prevotaux Email: chris@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 BP415 Fax: +33 (0)3 26 79 30 06 51689 Reims Cedex 2 FRANCE =================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 15:33:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from dell.dannyland.org (dell.dannyland.org [64.81.36.13]) by hub.freebsd.org (Postfix) with ESMTP id AD4F837B66C for ; Wed, 11 Oct 2000 15:33:46 -0700 (PDT) Received: by dell.dannyland.org (Postfix, from userid 1001) id 3C6645BEC; Wed, 11 Oct 2000 15:34:42 -0700 (PDT) Date: Wed, 11 Oct 2000 15:34:42 -0700 From: dannyman To: "Brandon D. Valentine" Cc: attila! , Peter van Dijk , freebsd-current@FreeBSD.ORG Subject: Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds Message-ID: <20001011153441.B27786@dell.dannyland.org> References: <20001009003730.A75DA1C2AB@hun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from bandix@looksharp.net on Sun, Oct 08, 2000 at 09:43:01PM -0400 X-Loop: djhoward@uiuc.edu X-URL: http://www.dannyland.org/~dannyman/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 08, 2000 at 09:43:01PM -0400, Brandon D. Valentine wrote: > On Mon, 9 Oct 2000, attila! wrote: > > I am perfectly well willing to maintain it in cvs format. > > You and a million other crusaders. > > Sorry to rain on your parade but what you're discussing borders on a > religious jihad. Were we all not already tired of the endless > flamefests that spawn from every discussion concerning the MTA in the > base system, I'm sure you would have a mailbox full of flames by now. [...] > Sendmail is there, works, and is being actively maintained by a member > of the actual sendmail team. That's far more than can be said for other > parts of the contrib tree and if you'd like to help out I'm sure there > are other areas that need more attention. I'm save you the frustration > now, please, don't waste your time. I am a Postfix weenie. I don't care what the "default" MTA that comes with FreeBSD is, but I like that 4.x is better at giving you a choice in the matter. If someone wanted to maintain Postfix in the FreeBSD source tree as an alternative to Sendmail, I don't see what's wrong with that ... same for Qmail and the like. The main objection I would seis that you're then bloating FreeBSD's source tree with every MTA known to man. The answer? Jihad? Or make EVERY MTA an option for the base system? Or just do as has been done for time immemorial and leave Sendmail where it has always been ... :) -danny -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 15:39:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id AB65C37B66D for ; Wed, 11 Oct 2000 15:39:51 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 036571C6A; Wed, 11 Oct 2000 18:39:50 -0400 (EDT) Date: Wed, 11 Oct 2000 18:39:50 -0400 From: Bill Fumerola To: dannyman Cc: "Brandon D. Valentine" , attila! , Peter van Dijk , freebsd-current@FreeBSD.ORG Subject: Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds Message-ID: <20001011183950.E38472@jade.chc-chimes.com> References: <20001009003730.A75DA1C2AB@hun.org> <20001011153441.B27786@dell.dannyland.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20001011153441.B27786@dell.dannyland.org>; from dannyman@dannyland.org on Wed, Oct 11, 2000 at 03:34:42PM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 11, 2000 at 03:34:42PM -0700, dannyman wrote: > I am a Postfix weenie. I don't care what the "default" MTA that comes with > FreeBSD is, but I like that 4.x is better at giving you a choice in the > matter. If someone wanted to maintain Postfix in the FreeBSD source tree as > an alternative to Sendmail, I don't see what's wrong with that ... same for > Qmail and the like. The main objection I would seis that you're then bloating > FreeBSD's source tree with every MTA known to man. The answer? Jihad? Or > make EVERY MTA an option for the base system? Or just do as has been done for > time immemorial and leave Sendmail where it has always been ... :) For the hundred millionth time, the right way to do all of this is in the "everything is a package" approach, which everyone agrees is the right answer, but no one has turned out code to do yet. All time spent anywhere other then churning out the code for the that design is wasted. We don't need another MTA in the default system, some would argue we don't need the current on we have. We do need a more configurable install and adding more MTAs isn't going to help. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 16:25: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from falcon.sourcee.com (falcon.sourcee.com [12.11.130.185]) by hub.freebsd.org (Postfix) with ESMTP id 77F0837B503 for ; Wed, 11 Oct 2000 16:24:59 -0700 (PDT) Received: (from evan@localhost) by falcon.sourcee.com (8.9.3/8.9.3) id TAA12415 for freebsd-current@freebsd.org; Wed, 11 Oct 2000 19:24:58 -0400 (EDT) Date: Wed, 11 Oct 2000 19:24:58 -0400 From: Evan Tsoukalas To: freebsd-current@freebsd.org Subject: Solved: panic: pmap_release Message-ID: <20001011192458.D27322@sourcee.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: email message Content-Disposition: inline User-Agent: Mutt/1.1.9i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, Just wanted to thank everyone for their response to my August 30th EDT post. Especially to Doug White, who offered up the correct solution in telling me to replace the CPU cache and saved me from having to futilely swap RAID cards. After more than thirty straight days without a crash, I can officially tear my hair out about something else. ;-) -- Regards, Evan Tsoukalas Systems Administrator Source Electronics Corporation evan@sourcee.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 20:53:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id 4337637B502 for ; Wed, 11 Oct 2000 20:53:23 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e9C3fTG00863 for ; Thu, 12 Oct 2000 12:41:30 +0900 (JST) Date: Thu, 12 Oct 2000 12:41:29 +0900 Message-ID: <7mn1gaenfa.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: current@FreeBSD.ORG Subject: RE: -current grinds exceeding slow In-Reply-To: In your message of "11 Oct 2000 18:43:14 GMT" References: User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11 Oct 2000 18:43:14 GMT, John Baldwin wrote: > I don't know. Can you try to narrow down the date by cvsupping or > cvs updating with date tags to see when it started slowing down? I've checked with -D '2000-10-03 00:00:00 GMT' and -D '2000-10-04 12:00:00 GMT'. With previous kernel, "time find /usr/obj" returns 65 seconds, but with later kernel, it returns 547 seconds (/usr/obj is NFS mounted from localhost). Top command shows many processes locked with MUTEX status. It seems this is caused by jasone's commit at 3rd Oct... -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 21: 7:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id E861537B502 for ; Wed, 11 Oct 2000 21:07:52 -0700 (PDT) Received: (qmail 77461 invoked by uid 1142); 12 Oct 2000 04:07:52 -0000 Date: 11 Oct 2000 21:07:52 -0700 Date: Wed, 11 Oct 2000 21:07:42 -0700 From: Jason Evans To: Jun Kuriyama Cc: current@FreeBSD.ORG Subject: Re: -current grinds exceeding slow Message-ID: <20001011210742.B11949@canonware.com> References: <7mn1gaenfa.wl@waterblue.imgsrc.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <7mn1gaenfa.wl@waterblue.imgsrc.co.jp>; from kuriyama@imgsrc.co.jp on Thu, Oct 12, 2000 at 12:41:29PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 12, 2000 at 12:41:29PM +0900, Jun Kuriyama wrote: > At 11 Oct 2000 18:43:14 GMT, > John Baldwin wrote: > > I don't know. Can you try to narrow down the date by cvsupping or > > cvs updating with date tags to see when it started slowing down? > > I've checked with -D '2000-10-03 00:00:00 GMT' and -D '2000-10-04 > 12:00:00 GMT'. With previous kernel, "time find /usr/obj" returns 65 > seconds, but with later kernel, it returns 547 seconds (/usr/obj is > NFS mounted from localhost). > > Top command shows many processes locked with MUTEX status. It seems > this is caused by jasone's commit at 3rd Oct... Do you have the SMP_DEBUG kernel option enabled? My changes added lots of mutexes to the kernel, and mtx_validate() iterates through all mutexes for mtx_init() and mtx_destroy() calls if SMP_DEBUG is enabled. I'm working on a change that will use a pool of mutexes that are allocated at boot time, which will make this slow down go away, but it may be a while before it gets checked in. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 21:31:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from hermes.dialup.ru (hermes.dialup.ru [194.87.16.230]) by hub.freebsd.org (Postfix) with ESMTP id 397DD37B502 for ; Wed, 11 Oct 2000 21:31:24 -0700 (PDT) Received: (from ache@localhost) by hermes.dialup.ru (8.11.1/8.11.1) id e9C4Uk600284 for current@freebsd.org; Thu, 12 Oct 2000 08:30:46 +0400 (MSD) (envelope-from ache) Date: Thu, 12 Oct 2000 08:29:30 +0400 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: current@freebsd.org Subject: savecore "fixing" patch for review Message-ID: <20001012082930.A276@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- rc.bak Thu Oct 12 08:23:33 2000 +++ rc Thu Oct 12 08:25:22 2000 @@ -331,6 +331,10 @@ echo '.' +# Build devices database +# +dev_mkdb + # Enable dumpdev so that savecore can see it. # /var/crash should be a directory or a symbolic link # to the crash directory if core dumps are to be saved. @@ -372,10 +376,6 @@ if [ -n "${network_pass2_done}" ]; then network_pass3 fi - -# Build ps databases -# -dev_mkdb # Check the password temp/lock file # -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 22:17:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id D032B37B502 for ; Wed, 11 Oct 2000 22:17:49 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e9C5HlG00517 for ; Thu, 12 Oct 2000 14:17:48 +0900 (JST) Date: Thu, 12 Oct 2000 14:17:47 +0900 Message-ID: <7m3di2ljt0.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: current@FreeBSD.ORG Subject: Re: -current grinds exceeding slow In-Reply-To: In your message of "11 Oct 2000 21:07:52 -0700" <20001011210742.B11949@canonware.com> References: <7mn1gaenfa.wl@waterblue.imgsrc.co.jp> <20001011210742.B11949@canonware.com> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12 Oct 2000 04:08:04 GMT, Jason Evans wrote: > Do you have the SMP_DEBUG kernel option enabled? Yes, I had SMP_DEBUG in my kernel configuration. > My changes added lots of mutexes to the kernel, and mtx_validate() iterates > through all mutexes for mtx_init() and mtx_destroy() calls if SMP_DEBUG is > enabled. I'm working on a change that will use a pool of mutexes that are > allocated at boot time, which will make this slow down go away, but it may > be a while before it gets checked in. Thank you for your information. I've disabled SMP_DEBUG and it works with usual speed! I'll keep disabled until your modification will come. -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 11 22:42:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id AB5AC37B502 for ; Wed, 11 Oct 2000 22:42:42 -0700 (PDT) Received: (from kris@localhost) by citusc17.usc.edu (8.9.3/8.9.3) id WAA09510; Wed, 11 Oct 2000 22:42:58 -0700 (PDT) Date: Wed, 11 Oct 2000 22:42:58 -0700 From: Kris Kennaway To: Christophe Prevotaux Cc: current@FreeBSD.ORG Subject: Re: [HELP] Problems with new version of CURRENT Message-ID: <20001011224258.A9498@citusc17.usc.edu> References: <200010112125.e9BLPaY01076@zippy.hexanet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010112125.e9BLPaY01076@zippy.hexanet.fr>; from chris@hexanet.fr on Wed, Oct 11, 2000 at 11:25:36PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 11, 2000 at 11:25:36PM +0200, Christophe Prevotaux wrote: > Could someone help me solve these problems > > Module can't register problem > random dev problem > linux emulation can't load problem > usb0 problem > unknow ressources ( I think it can't recognize my sound card ) It's -current. All of these things are to be expected (except the usb problem, where you need to actually do what the error message tells you to do, and the linux problem, which you forgot to describe.) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 0:13:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id 61D6537B503 for ; Thu, 12 Oct 2000 00:13:34 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e9C7DVG01755 for ; Thu, 12 Oct 2000 16:13:32 +0900 (JST) Date: Thu, 12 Oct 2000 16:13:31 +0900 Message-ID: <7mzokajzvo.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: Fragments refused by ipfw User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know which commit causes this problem, but recent my kernel falls into this situation. Host A is my desktop box (-current), host B is NFS server (3-stable). Sometimes (at heavy load on NFS?), my access to NFS server is locked. At that time, following messages are logged. ipfw: -1 Refuse UDP hostB hostA in via fxp0 Fragment = 925 I used ipfw with default accept but no rules. I have not seen such message before. Does someone get same situation? -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 1:34: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id F283A37B503 for ; Thu, 12 Oct 2000 01:33:59 -0700 (PDT) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.109]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id LAA00998; Thu, 12 Oct 2000 11:33:32 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.0/8.9.3) with ESMTP id e9C8XVF04179; Thu, 12 Oct 2000 11:33:31 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <39E57755.53072464@FreeBSD.org> Date: Thu, 12 Oct 2000 11:33:25 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@FreeBSD.org, gshapiro@gshapiro.net Subject: World is broken in sendmail if crypto sources is not installed Content-Type: multipart/mixed; boundary="------------AFA1A9E3BBA1A36BDD97AFA6" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------AFA1A9E3BBA1A36BDD97AFA6 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Please fix breakage (see attached logs). -Maxim --------------AFA1A9E3BBA1A36BDD97AFA6 Content-Type: application/x-gzip; name="breaklog.gz" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="breaklog.gz" H4sICCZ35TkCA2JyZWFrbG9nAN1aW2/aMBR+51f4GQnSQNt1kTqJrTChbS2imbo35NiO8Ijj zHbQ+u9rp4Gg9WmyaaSDQPhCPvvzObbPhdvb20+o1mqsM15GmpVUYF4MlECjHI0pq2zLQOxs 4aQBjTCyr9Eysk9GpFaKlSbSikRvkKLx2L2JLI3iWddsf+z1PC9JUVOGRnf386e7z+57+djU 0qX9XNti+mX1tJ6tVvO16/gxW23W86/zX7b8mM7WafrdNW8Wi/XGFjcPm/S0Gp9W0of1/Jub rt5ixXT0cxHJ7PebyfPpzXXTeJgc8lqfCBcc6zHxRVEVptgwb6As3xip2M4biBSSBECRRcGI CYBT5iFAjJJFCJy94cJfWBQzIUt/GFbwPVP+ONIW/afDyj0rZOW/PEz5c9oyTJny36ACEyUD oARYX4ErfwzC/TF4YQJonQixkyqstJU09Z/On5rV/vNRdjIkDwBDeMXto95IGu+Zq/gD5Rrr ADBbYTjZFTzzh1J7pYXx3xTa4CwEiPE/bvSzZn95ACB3TwU4/ozCxH9X1NR/fWvNwki7NgF2 g712NXdX+GBZopwXDLVmJUW5kiKMbZnE02TgqU9tZbxN4vgiQfZ6LrW2fdo1oXuJdE22rwyk QpTbk8fakc/noXU0dpP4BhSzzvpOphegmLXuADSBHf0TeMScw5RMLqCxevXgkvgKGrHWpYSm iAcfN4kve+MViMHltBtT4ZL2sJgHTx+clrShhz615By8ulgINIk1wRlo98sxWgSNWBu+gqaE 7aEx+QiMVQVQVC7iCG5btSYbrEvrJJgKTQvb6C409+EQboYmrpP4NzRqXUAe2qF4yBD0ySsQ g/jU5XMW7/sv5jG50eeZFYzD9Oo/1jPcqNfdqBmX7zXqh27UiokedKfJZ4E7OF8TbOBoHTN+ 0Ji1uUNotJpkJjTTv8uugmPWpHv7VMLmD5oJIlJUri+3GIwOhsMhmitlf0kkZSgexIi56r8d kzN0vACYmxLHWCoAAA== --------------AFA1A9E3BBA1A36BDD97AFA6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 6:44: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id 500ED37B503 for ; Thu, 12 Oct 2000 06:43:57 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e9CDhqG03619 for ; Thu, 12 Oct 2000 22:43:54 +0900 (JST) Date: Thu, 12 Oct 2000 22:43:52 +0900 Message-ID: <7mk8be9ntz.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: aue0 should register devices with make_dev()? User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've installworld'ed on my laptop and plugged USB ethernet device (aue0). It seems it worked without problem but I got warning message like this: Oct 12 22:25:00 leda /boot/kernel/kernel: WARNING: driver bpf should register devices with make_dev() (dev_t = "#bpf/0") I don't know what this means, but I hope this helps someone who knows how to fix it... -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 7:13: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from martens.math.ntnu.no (martens.math.ntnu.no [129.241.15.250]) by hub.freebsd.org (Postfix) with SMTP id 8E95337B503 for ; Thu, 12 Oct 2000 07:12:58 -0700 (PDT) Received: (qmail 7421 invoked by uid 29119); 12 Oct 2000 14:12:57 -0000 Date: Thu, 12 Oct 2000 16:12:57 +0200 (MET DST) From: Per Kristian Hove X-Sender: perhov@martens.math.ntnu.no To: freebsd-stable@FreeBSD.org, freebsd-current@FreeBSD.org Subject: cvsup.no.FreeBSD.org downtime Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvsup.no.FreeBSD.org will be down for approx. 15 minutes somewhere between 10:00 UTC to 10:30 UTC tomorrow (2000-10-13) due to network equipment upgrades. -- Per Kristian Hove Principal engineer Dept. of Mathematical Sciences Norwegian University of Science and Technology To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 7:35:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 74B7A37B502; Thu, 12 Oct 2000 07:35:39 -0700 (PDT) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id PAA80294; Thu, 12 Oct 2000 15:35:38 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id PAA09535; Thu, 12 Oct 2000 15:33:57 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 12 Oct 2000 15:33:57 +0100 To: John Baldwin From: Bob Bishop Subject: RE: -current grinds exceeding slow Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 11:42 -0700 11/10/00, John Baldwin wrote: >On 10-Oct-00 Bob Bishop wrote: >> Hi, >> >> What's happened recently to make -current so slow? >> [etc] > >I don't know. Can you try to narrow down the date by cvsupping or >cvs updating with date tags to see when it started slowing down? More data: it's networking that's doing it, not NFS per se. I'm doing a build with local sources on one of the affected boxes, on first impression looks like that is up to speed. Both my affected boxes have ed NICs, I'll see if I can scare up a different card to try in case it's the ed driver. Watch this space... -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 8:31:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from bsdconspiracy.net (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 1BC3037B66C for ; Thu, 12 Oct 2000 08:31:14 -0700 (PDT) Received: from zaphod.softweyr.com ([204.68.178.35] helo=softweyr.com ident=wes) by bsdconspiracy.net with esmtp (Exim 3.14 #1) id 13jkHw-0006fN-00; Thu, 12 Oct 2000 08:28:56 -0700 Message-ID: <368DD68D.8381D426@softweyr.com> Date: Sat, 02 Jan 1999 01:19:25 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Bill Fumerola Cc: dannyman , "Brandon D. Valentine" , "attila!" , Peter van Dijk , freebsd-current@FreeBSD.ORG Subject: Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds References: <20001009003730.A75DA1C2AB@hun.org> <20001011153441.B27786@dell.dannyland.org> <20001011183950.E38472@jade.chc-chimes.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: > > On Wed, Oct 11, 2000 at 03:34:42PM -0700, dannyman wrote: > > > I am a Postfix weenie. I don't care what the "default" MTA that comes with > > FreeBSD is, but I like that 4.x is better at giving you a choice in the > > matter. If someone wanted to maintain Postfix in the FreeBSD source tree as > > an alternative to Sendmail, I don't see what's wrong with that ... same for > > Qmail and the like. The main objection I would seis that you're then bloating > > FreeBSD's source tree with every MTA known to man. The answer? Jihad? Or > > make EVERY MTA an option for the base system? Or just do as has been done for > > time immemorial and leave Sendmail where it has always been ... :) > > For the hundred millionth time, the right way to do all of this is in the > "everything is a package" approach, which everyone agrees is the right answer, > but no one has turned out code to do yet. Yes! Yes! Yes! -- Where am I, and what am I doing in this handbasket? Wes Peters wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 9:53:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from catnip.freemail.ne.jp (catnip.freemail.ne.jp [210.235.164.46]) by hub.freebsd.org (Postfix) with SMTP id C59DB37B503 for ; Thu, 12 Oct 2000 09:53:47 -0700 (PDT) Received: (qmail 7509 invoked by alias); 12 Oct 2000 23:33:22 +0900 Received: (qmail 17221 invoked from network); 12 Oct 2000 23:19:43 +0900 Received: from unknown (HELO default) (210.155.148.54) by catnip.freemail.ne.jp with SMTP; 12 Oct 2000 23:19:43 +0900 Message-ID: <015801c03457$71e97be0$02fc0bca@default> From: "=?iso-2022-jp?B?GyRCRWw1fiUvJSQlOjgmNWYycRsoQg==?=" To: Subject: =?iso-2022-jp?B?GyRCOl9CcDduPH0bKEIyOBskQkt8ISE6bjZIJE8hViVhJWIhVxsoQg==?= =?iso-2022-jp?B?GyRCJEAkMSEhNCtNNk1XQUcwbEBaJEokNxsoQg==?= Date: Thu, 12 Oct 2000 21:02:44 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG $B!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z(B $B!z!!%@%$%d%k(BQ2$B%/%$%:$NLdBj$rJR$CC<$+$iD4$Y$F$7$^$($P!*!z(B $B!z!!$3$3$^$G$OC/$K$b;W$$$D$/M}6~$G$9$,!&!&!&!&!&!&!&!&!&!&!&!&!&!&!&(B $B!z(B $B!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z!z(B $B!}%@%$%d%k(BQ2$B%/%$%:$H$O!)(B $B#Q#2EEOC$GA*Br7A<0$N%/%$%:$KD)@o$7!"$?$H$($P#1#5LdB3$1$F@52r$r(B $B=P$9$H#1#0K|1_$,;YJ'$o$l$^$9!#Be=~$H$7$F#Q#2NA6b$,2]$;$i$l$k(B $B$N$G!"M5!"$"$kDxEY$NF|K\8lF~NOG=NO$,;q3J$G$9!#5o=;CO$O(B $B9qFb$J$i86B'2D$G$9$,$4$/5)$K#Q#2$,;H$($J$$CO0h$b$"$j$^$9!#(B $B$^$?!"L$@.G/$O$*CG$j$7$F$*$j$^$9!#(B $B!}J]>Z6b$H2qHq(B $B$^$?!"6HZ6b$r$*MB$+$j$7$^$9!#$3$l$O(B $B0J2<$N%1!<%9$K8B$jKW<}$5$l$^$9!#(B $B!&LdBj56B$$,L@Gr!J%R%C%HN($,J?6Q$NH>J,0J2l9g(B $B!&2<5-$N%a%j%C%H6!M?$,7QB3$5$l$F$$$k$K$b$+$+$o$i$:2q0wB&$NET(B $B9g$K$h$j#1G/0JFb$KB`2q$9$k>l9g(B $B??LLL\$KJs9p$7$FD:$1$k2q0w$OEv2q$K$H$C$F$b$G$9$N$G!"L50UL#(B $B$J=|L>$O@dBP$K$$$?$7$^$;$s!#$^$?!"7n!9#1K|1_$N2qHq$r$*4j$$(B $B$7$F$$$^$9!#$3$l$O!"=i7n$N>^6b3MF@8e$+$iD'<}$7$^$9!#(B $B!}!VEl5~%/%$%:8&5f2q!W%a%s%P!<$N%a%j%C%H(B $BKh7n#3l9g$*CG$j$9$k$?$a!K$@$1!#(B $B!}Dy@Z$j$O(B $B:#2s?75,$K%o%s%f%K%C%H!J$8$e$&$V$s$JLdBj?t$r3NJ]$9$k$N$KI,MW$J?M?t!K(B $BJT@.$7$^$9!#Dj?t=!#(B $B!}?=9~$_$O(B quiz000@your-house.com $B$^$G!#$=$N:]!"#77eM9JXHV9f$rH>3Q$G%a!<%kBj$H$7$F$/$@$5$$!#(B $B$^$?!"K\J8$K$OG/Np@-JL$H%a!<%k%"%I%l%9$r5-$7$F$/$@$5$$!#(B $B8=CJ3,$G$O0J>e$,@bL@$N$9$Y$F$G$9!#%N%&%O%&$NHkL)$,(B $B$"$j$^$9$N$G$4l9g$,$"$j$^$9!#(B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 10: 5:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id 8EFCC37B502; Thu, 12 Oct 2000 10:05:15 -0700 (PDT) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.11.2.PreAlpha0/8.11.2.PreAlpha0) id e9CH5EE42480; Thu, 12 Oct 2000 10:05:14 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14821.61258.561633.791329@horsey.gshapiro.net> Date: Thu, 12 Oct 2000 10:05:14 -0700 (PDT) From: Gregory Neil Shapiro To: Maxim Sobolev Cc: current@FreeBSD.org Subject: Re: World is broken in sendmail if crypto sources is not installed In-Reply-To: <39E57755.53072464@FreeBSD.org> References: <39E57755.53072464@FreeBSD.org> X-Mailer: VM 6.75 under 21.2 (beta36) "Notus" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sobomax> Please fix breakage (see attached logs). I've removed STARTTLS support for time being. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 10:17:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 8012F37B66C for ; Thu, 12 Oct 2000 10:17:44 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9CHGdi20940; Thu, 12 Oct 2000 10:16:39 -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: Date: Thu, 12 Oct 2000 10:17:15 -0700 (PDT) From: John Baldwin To: Bob Bishop Subject: RE: -current grinds exceeding slow Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Oct-00 Bob Bishop wrote: > Hi, > > At 11:42 -0700 11/10/00, John Baldwin wrote: >>On 10-Oct-00 Bob Bishop wrote: >>> Hi, >>> >>> What's happened recently to make -current so slow? >>> [etc] >> >>I don't know. Can you try to narrow down the date by cvsupping or >>cvs updating with date tags to see when it started slowing down? > > More data: it's networking that's doing it, not NFS per se. I'm doing a > build with local sources on one of the affected boxes, on first impression > looks like that is up to speed. > > Both my affected boxes have ed NICs, I'll see if I can scare up a different > card to try in case it's the ed driver. Watch this space... It's not. My current box that is having problems has an fxp0 card. BTW, what speed is your processor? I'm curious because the PPro 200 I have here is having problems, but the PIII-700 isn't very affected. -- 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-current" in the body of the message From owner-freebsd-current Thu Oct 12 10:34:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 78EFC37B502 for ; Thu, 12 Oct 2000 10:34:34 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id TAA03521 for freebsd-current@freebsd.org; Thu, 12 Oct 2000 19:34:37 +0200 (CEST) (envelope-from kuku) Date: Thu, 12 Oct 2000 19:34:37 +0200 (CEST) From: Christoph Kukulies Message-Id: <200010121734.TAA03521@gilberto.physik.rwth-aachen.de> To: freebsd-current@freebsd.org Subject: locate dumps core Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup'ed -current yesterday into my living 6 months old -current, built world, tweaked here and there to get kernel config file working, disk devide nodes etc. am up and running again but locate dumps core at the end of the list of found files. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de "The Hammond Tonewheel Organ - God's harmonica" http://blues.physik.rwth-aachen.de/hammond.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 11: 5:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 72DA837B502; Thu, 12 Oct 2000 11:05:43 -0700 (PDT) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id TAA88528; Thu, 12 Oct 2000 19:05:42 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id SAA10093; Thu, 12 Oct 2000 18:40:36 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 12 Oct 2000 18:40:37 +0100 To: John Baldwin From: Bob Bishop Subject: RE: -current grinds exceeding slow Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 10:17 -0700 12/10/00, John Baldwin wrote: [...] >It's not. My current box that is having problems has an fxp0 card. >BTW, what speed is your processor? I'm curious because the PPro 200 >I have here is having problems, but the PIII-700 isn't very affected. Try removing SMP_DEBUG from your config (see Message-ID: <20001011210742.B11949@canonware.com> from Jason Evans on this thread). -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 11:31:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 04EF637B66C for ; Thu, 12 Oct 2000 11:31:51 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 951D51C41; Thu, 12 Oct 2000 14:31:50 -0400 (EDT) Date: Thu, 12 Oct 2000 14:31:50 -0400 From: Bill Fumerola To: Jun Kuriyama Cc: Current Subject: Re: Fragments refused by ipfw Message-ID: <20001012143150.C37870@jade.chc-chimes.com> References: <7mzokajzvo.wl@waterblue.imgsrc.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <7mzokajzvo.wl@waterblue.imgsrc.co.jp>; from kuriyama@imgsrc.co.jp on Thu, Oct 12, 2000 at 04:13:31PM +0900 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 12, 2000 at 04:13:31PM +0900, Jun Kuriyama wrote: > Host A is my desktop box (-current), host B is NFS server (3-stable). > Sometimes (at heavy load on NFS?), my access to NFS server is locked. > At that time, following messages are logged. > > ipfw: -1 Refuse UDP hostB hostA in via fxp0 Fragment = 925 > > I used ipfw with default accept but no rules. I have not seen such > message before. To be perfectly honest I don't see what code path could cause this, if it hits the default rule we jump out of ipfw right away: for (; chain; chain = LIST_NEXT(chain, chain)) { again: f = chain->rule; if (f->fw_number == IPFW_DEFAULT_RULE) goto got_match ; [...] got_match: #if STATEFUL /* stateful ipfw */ /* * If not a dynamic match (q == NULL) and keep-state, install * a new dynamic entry. */ if (q == NULL && f->fw_flg & IP_FW_F_KEEP_S) install_state(chain); #endif *flow_id = chain ; /* XXX set flow id */ /* Update statistics */ f->fw_pcnt += 1; f->fw_bcnt += ip->ip_len; f->timestamp = time_second; /* Log to console if desired */ if ((f->fw_flg & IP_FW_F_PRN) && fw_verbose) ipfw_report(f, ip, rif, oif); /* Take appropriate action */ switch (f->fw_flg & IP_FW_F_COMMAND) { case IP_FW_F_ACCEPT: return(0); That's the entire codepath of a default rule hit. The message you're seeing is from ipfw_report(), which shouldn't be called from the default rule match either. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 14:52:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id 4589337B503 for ; Thu, 12 Oct 2000 14:52:10 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e9CLq9N96349 for ; Thu, 12 Oct 2000 23:52:09 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: Patch review: DELAY.patch From: Poul-Henning Kamp Date: Thu, 12 Oct 2000 23:52:09 +0200 Message-ID: <96347.971387529@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://phk.freebsd.dk/patch/DELAY.patch Move DELAY() and sysbeep() from to and remove unneeded #includes of -- 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-current" in the body of the message From owner-freebsd-current Thu Oct 12 14:53:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id 9DD2037B503 for ; Thu, 12 Oct 2000 14:53:43 -0700 (PDT) Received: from backup.af.speednet.com.au (backup.af.speednet.com.au [172.22.2.4]) by backup.af.speednet.com.au (8.11.0/8.11.0) with ESMTP id e9CLrYa63098 for ; Fri, 13 Oct 2000 08:53:35 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Fri, 13 Oct 2000 08:53:34 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: freebsd-current@FreeBSD.ORG Subject: NOMAN Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was trying to build a minimul (RELENG_4) system from sources and noticed that there is no mention of disabling the building and installing of man pages. Should the NOMAN knob be documented in both /etc/defaults/make.conf and /usr/src/Makefile.inc1 ? --- /usr/src/etc/defaults/make.conf-orig Mon Sep 25 19:08:01 2000 +++ /usr/src/etc/defaults/make.conf Fri Oct 13 08:33:17 2000 @@ -69,4 +69,5 @@ #NOINFO= true # do not make or install info files #NOLIBC_R= true # do not build libc_r (re-entrant version of libc) +#NOMAN= true # do not build and install man pages #NOPERL= true # To avoid building perl #NOPROFILE= true # Avoid compiling profiled libraries --- /usr/src/Makefile.inc1-orig Tue Oct 10 01:28:47 2000 +++ /usr/src/Makefile.inc1 Fri Oct 13 08:48:34 2000 @@ -13,4 +13,5 @@ # -DNOSHARE do not go into share subdir # -DNOINFO do not make or install info files +# -DNOMAN do not make or install man files # -DNOLIBC_R do not build libc_r. # -DNO_FORTRAN do not build g77 and related libraries. -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 16: 9:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 6CE5937B66C; Thu, 12 Oct 2000 16:09:56 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id QAA08778; Thu, 12 Oct 2000 16:10:51 -0700 (PDT) Message-Id: <200010122310.QAA08778@implode.root.com> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: Patch review: DELAY.patch In-reply-to: Your message of "Thu, 12 Oct 2000 23:52:09 +0200." <96347.971387529@critter> From: David Greenman Reply-To: dg@root.com Date: Thu, 12 Oct 2000 16:10:51 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >http://phk.freebsd.dk/patch/DELAY.patch > >Move DELAY() and sysbeep() from to >and remove unneeded #includes of What's the motivation of this change? To bring it into the MI area? -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 16:40:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 58F4D37B502 for ; Thu, 12 Oct 2000 16:40:47 -0700 (PDT) Received: from localhost (cshumway@localhost) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9CNdia32977; Thu, 12 Oct 2000 16:39:44 -0700 (PDT) (envelope-from cshumway@bsdi.com) X-Authentication-Warning: pike.osd.bsdi.com: cshumway owned process doing -bs Date: Thu, 12 Oct 2000 16:39:44 -0700 (PDT) From: Christopher Shumway X-Sender: cshumway@pike.osd.bsdi.com To: Mike Meyer Cc: current@FreeBSD.ORG Subject: Re: Upgrading -stable -> -current, boot failure? In-Reply-To: <14820.10867.8261.441382@guru.mired.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Oct 2000, Mike Meyer wrote: > I've got a system with 4.1-STABLE installed. I mount -current sources > on it, do make buildworld/buildkernel/installkernel/installworld and > reboot. The boot loader runs, gives me the "booting default in..." > countdown, prints "|", and then stops. After thrashing the disks (with > *no* boot messages), I get a prompt from init. > > Since the same sources build and boot properly elsewhere, I assume > I've missed a step. I normally run mergemaster after installworld and > rebooting singleuser. Could someone provide the clue I've not got? Do you have an /boot/device.hints? This file tells the kernel where to find devices at boot time, including a console. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 17: 6:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 8D81037B503; Thu, 12 Oct 2000 17:06:12 -0700 (PDT) Received: from cain.gsoft.com.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.3) with ESMTP id JAA08088; Fri, 13 Oct 2000 09:35:59 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 13 Oct 2000 09:35:58 +0930 (CST) From: "Daniel O'Connor" To: Bob Bishop Subject: RE: -current grinds exceeding slow Cc: current@FreeBSD.org, John Baldwin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Oct-00 Bob Bishop wrote: > >It's not. My current box that is having problems has an fxp0 card. > >BTW, what speed is your processor? I'm curious because the PPro 200 > >I have here is having problems, but the PIII-700 isn't very affected. > Try removing SMP_DEBUG from your config (see > Message-ID: <20001011210742.B11949@canonware.com> > from Jason Evans on this thread). That worked for me... Does anyone here run the really new version of Licq? I know it sounds dumb, but it seems that if I run it and do some reasonably heavy disk, processes start getting stuck in things like vnlock, inode and ffsvgt... --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 17:25:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id C3F6A37B502; Thu, 12 Oct 2000 17:25:10 -0700 (PDT) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA13774; Thu, 12 Oct 2000 20:24:55 -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 UAA24303; Thu, 12 Oct 2000 20:24:54 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA24299; Thu, 12 Oct 2000 20:24:53 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Thu, 12 Oct 2000 20:24:53 -0400 (EDT) From: Kenneth Wayne Culver To: "Daniel O'Connor" Cc: Bob Bishop , current@FreeBSD.ORG, John Baldwin Subject: RE: -current grinds exceeding slow In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I use 0.85, I had some wierd problems with it in -CURRENT. I've moved down to 4.1.1-STABLE till some of this stuff in -CURRENT cools down. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Fri, 13 Oct 2000, Daniel O'Connor wrote: > > On 12-Oct-00 Bob Bishop wrote: > > >It's not. My current box that is having problems has an fxp0 card. > > >BTW, what speed is your processor? I'm curious because the PPro 200 > > >I have here is having problems, but the PIII-700 isn't very affected. > > Try removing SMP_DEBUG from your config (see > > Message-ID: <20001011210742.B11949@canonware.com> > > from Jason Evans on this thread). > > That worked for me... > > Does anyone here run the really new version of Licq? > > I know it sounds dumb, but it seems that if I run it and do some reasonably > heavy disk, processes start getting stuck in things like vnlock, inode and > ffsvgt... > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 18:27:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id A845437B66C for ; Thu, 12 Oct 2000 18:27:15 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e9D1R9G10294 for ; Fri, 13 Oct 2000 10:27:09 +0900 (JST) Date: Fri, 13 Oct 2000 10:27:09 +0900 Message-ID: <7md7h5a5ua.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: FreeBSD-current@FreeBSD.org Subject: Re: Fragments refused by ipfw In-Reply-To: In your message of "Thu, 12 Oct 2000 14:31:50 -0400" <20001012143150.C37870@jade.chc-chimes.com> References: <7mzokajzvo.wl@waterblue.imgsrc.co.jp> <20001012143150.C37870@jade.chc-chimes.com> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Thu, 12 Oct 2000 14:31:50 -0400, Bill Fumerola wrote: > > ipfw: -1 Refuse UDP hostB hostA in via fxp0 Fragment = 925 > > > > I used ipfw with default accept but no rules. I have not seen such > > message before. > > To be perfectly honest I don't see what code path could cause this, if > it hits the default rule we jump out of ipfw right away: Hmm, ipfw_report() seems printed message above is happend with f == NULL condition. But ipfw_report() is called after checking f->fw_flg... Something strange... -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 19:15:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 137E637B502 for ; Thu, 12 Oct 2000 19:15:46 -0700 (PDT) Received: (qmail 15510 invoked by uid 0); 13 Oct 2000 02:15:42 -0000 Received: from p3ee2161a.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.26) by mail.gmx.net with SMTP; 13 Oct 2000 02:15:42 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id VAA25182 for freebsd-current@freebsd.org; Thu, 12 Oct 2000 21:57:27 +0200 Date: Thu, 12 Oct 2000 21:57:27 +0200 From: Gerhard Sittig To: freebsd-current@freebsd.org Subject: Re: locate dumps core Message-ID: <20001012215726.F31338@speedy.gsinet> Mail-Followup-To: freebsd-current@freebsd.org References: <200010121734.TAA03521@gilberto.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200010121734.TAA03521@gilberto.physik.rwth-aachen.de>; from kuku@gilberto.physik.rwth-aachen.de on Thu, Oct 12, 2000 at 07:34:37PM +0200 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 12, 2000 at 19:34 +0200, Christoph Kukulies wrote: > > I cvsup'ed -current yesterday into my living 6 months > old -current, built world, tweaked here and there to get > kernel config file working, disk devide nodes etc. > am up and running again but locate dumps core at the end > of the list of found files. Isn't a core dump something you could easily get a stack trace from? This could give more clues than "it doesn't work" ... virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 20:26: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id 33D4237B503 for ; Thu, 12 Oct 2000 20:26:01 -0700 (PDT) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.11.2.PreAlpha0/8.11.2.PreAlpha0) id e9D3Q0v49066; Thu, 12 Oct 2000 20:26:00 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14822.32968.776955.127706@horsey.gshapiro.net> Date: Thu, 12 Oct 2000 20:26:00 -0700 (PDT) From: Gregory Neil Shapiro To: freebsd-current@FreeBSD.org Subject: sendmail STARTTLS In-Reply-To: <200010020113.SAA71517@bubba.whistle.com> References: <14806.44340.887777.120946@horsey.gshapiro.net> <200010020113.SAA71517@bubba.whistle.com> X-Mailer: VM 6.75 under 21.2 (beta36) "Notus" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The STARTTLS version of sendmail has been added in src/secure/usr.sbin/sendmail/. src/usr.sbin/sendmail will continue to be the non-STARTTLS version for those who do not have the secure distribution installed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 20:28:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id DB62E37B502 for ; Thu, 12 Oct 2000 20:28:15 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e9D3S9V03304 for FreeBSD-current@FreeBSD.ORG; Fri, 13 Oct 2000 12:58:09 +0930 (CST) (envelope-from grog) Date: Fri, 13 Oct 2000 12:58:09 +0930 From: Greg Lehey To: FreeBSD current users Subject: Panic "m_copydata, negative off" out of tcp_output Message-ID: <20001013125809.K2593@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been having a few panics lately with a PRE_SMPNG snap: kgdb) bt #0 dumpsys () at ../../kern/kern_shutdown.c:461 #1 0xc01cf043 in boot (howto=256) at ../../kern/kern_shutdown.c:302 #2 0xc01cf3e5 in panic (fmt=0xc037db85 "m_copydata, negative off %d") at ../../kern/kern_shutdown.c:550 #3 0xc01edd02 in m_copydata (m=0x0, off=-1, len=1, cp=0xc0cd7970 "xmission\003com") at ../../kern/uipc_mbuf.c:766 #4 0xc02356a0 in tcp_output (tp=0xcb54d720) at ../../netinet/tcp_output.c:590 #5 0xc02343f3 in tcp_input (m=0xc0cd7900, off0=20, proto=6) at ../../netinet/tcp_input.c:2249 #6 0xc022e5d2 in ip_input (m=0xc0cd7900) at ../../netinet/ip_input.c:750 #7 0xc022e62f in ipintr () at ../../netinet/ip_input.c:778 Does anybody recognize this? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 20:56:47 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id 13D9B37B502; Thu, 12 Oct 2000 20:56:45 -0700 (PDT) Date: Thu, 12 Oct 2000 20:56:45 -0700 From: John DeBoskey To: freebsd-current@FreeBSD.org Subject: Review: ptrace doc update / minor code question-correction Message-ID: <20001012205644.B95681@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been working with ptrace() and thought I'd take the time to make a minor update to the man page: Index: ptrace.2 =================================================================== RCS file: /home/ncvs/src/lib/libc/sys/ptrace.2,v retrieving revision 1.14 diff -u -r1.14 ptrace.2 --- ptrace.2 2000/05/04 13:09:15 1.14 +++ ptrace.2 2000/10/13 03:39:46 @@ -143,6 +143,13 @@ .Fa data provides a signal number to be delivered to the traced process as it resumes execution, or 0 if no signal is to be sent. +.It Dv PT_STEP +The traced process is single stepped one instruction. +The +.Fa addr +and +.Fa data +fields are not used. .It Dv PT_KILL The traced process terminates, as if .Dv PT_CONTINUE @@ -306,7 +313,9 @@ .Xr execve 2 , .Xr sigaction 2 , .Xr wait 2 , -.Xr execv 3 +.Xr execv 3 , +.Xr i386_clr_watch 3 , +.Xr i386_set_watch 3 .Sh HISTORY A .Fn ptrace Also, in looking at the ptrace code, I'd like to make the following minor change to remove a bogus parameter check: Index: sys_process.c =================================================================== RCS file: /home/ncvs/src/sys/kern/sys_process.c,v retrieving revision 1.52 diff -u -r1.52 sys_process.c --- sys_process.c 2000/08/30 04:49:07 1.52 +++ sys_process.c 2000/10/13 03:52:03 @@ -322,7 +322,7 @@ case PT_STEP: case PT_CONTINUE: case PT_DETACH: - if ((unsigned)uap->data >= NSIG) + if ((uap->req != PT_STEP) && ((unsigned)uap->data >= NSIG)) return EINVAL; PHOLD(p); Comments welcome! Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 12 22:25: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id D5BD737B503 for ; Thu, 12 Oct 2000 22:25:00 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e9D5OkN97473; Fri, 13 Oct 2000 07:24:46 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: dg@root.com Cc: current@FreeBSD.ORG Subject: Re: Patch review: DELAY.patch In-Reply-To: Your message of "Thu, 12 Oct 2000 16:10:51 PDT." <200010122310.QAA08778@implode.root.com> Date: Fri, 13 Oct 2000 07:24:46 +0200 Message-ID: <97471.971414686@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200010122310.QAA08778@implode.root.com>, David Greenman writes: >> >>http://phk.freebsd.dk/patch/DELAY.patch >> >>Move DELAY() and sysbeep() from to >>and remove unneeded #includes of > > What's the motivation of this change? To bring it into the MI area? To reduce the number of cut&paste mistakes in . I blive about 200 instances of #include are removed by that patch. -- 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-current" in the body of the message From owner-freebsd-current Thu Oct 12 22:37: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id 9574C37B503 for ; Thu, 12 Oct 2000 22:37:06 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e9D5b4G00576 for ; Fri, 13 Oct 2000 14:37:05 +0900 (JST) Date: Fri, 13 Oct 2000 14:37:04 +0900 Message-ID: <7md7h55mkf.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: FreeBSD-current@FreeBSD.ORG Subject: Re: Fragments refused by ipfw In-Reply-To: In your message of "12 Oct 2000 07:13:47 GMT" <7mzokajzvo.wl@waterblue.imgsrc.co.jp> References: <7mzokajzvo.wl@waterblue.imgsrc.co.jp> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12 Oct 2000 07:13:47 GMT, Jun Kuriyama wrote: > Host A is my desktop box (-current), host B is NFS server (3-stable). > Sometimes (at heavy load on NFS?), my access to NFS server is locked. > At that time, following messages are logged. > > ipfw: -1 Refuse UDP hostB hostA in via fxp0 Fragment = 925 > > I used ipfw with default accept but no rules. I have not seen such > message before. I found ipfw_report(NULL, ..) is called at this point. ----- ip_fw.c:1305 bogusfrag: if (fw_verbose) ipfw_report(NULL, ip, rif, oif); goto dropit; } ----- After some debug, PULLUP_TO() in case IPPROTO_UDP. Is reason for this failing of m_pullup()? ----- ip_fw.c:1001 case IPPROTO_UDP : PULLUP_TO(hlen + sizeof(struct udphdr)); udp =(struct udphdr *)((u_int32_t *)ip + ip->ip_hl); dst_port = udp->uh_dport ; src_port = udp->uh_sport ; break; ----- -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 0:36:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 5D15F37B503 for ; Fri, 13 Oct 2000 00:36:46 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id DDEE91C41; Fri, 13 Oct 2000 03:36:45 -0400 (EDT) Date: Fri, 13 Oct 2000 03:36:45 -0400 From: Bill Fumerola To: Jun Kuriyama Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Fragments refused by ipfw Message-ID: <20001013033645.M37870@jade.chc-chimes.com> References: <7mzokajzvo.wl@waterblue.imgsrc.co.jp> <7md7h55mkf.wl@waterblue.imgsrc.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <7md7h55mkf.wl@waterblue.imgsrc.co.jp>; from kuriyama@imgsrc.co.jp on Fri, Oct 13, 2000 at 02:37:04PM +0900 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 13, 2000 at 02:37:04PM +0900, Jun Kuriyama wrote: > After some debug, PULLUP_TO() in case IPPROTO_UDP. Is reason for this > failing of m_pullup()? Yes. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 0:45:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 33FA737B674; Fri, 13 Oct 2000 00:45:02 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id JAA06813; Fri, 13 Oct 2000 09:45:03 +0200 (CEST) (envelope-from kuku) Date: Fri, 13 Oct 2000 09:45:03 +0200 (CEST) From: Christoph Kukulies Message-Id: <200010130745.JAA06813@gilberto.physik.rwth-aachen.de> To: freebsd-current@freebsd.org Subject: scp times out or gets crc errors Cc: isdn@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm getting strange crc errors and timeouts when trying to use scp (secure rcp from ssh) to copy some files. kuku> scp *.jpg remotehost: kuku@remotehost.de's password: kukuck1.jpg 100% |*****************************| 196 KB 00:06 Read from remote host kuku@remotehost.de: Operation timed out lost connection I'm not sure whether it could be also an isdn issue so I'm cc'ing to the isdn list. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 0:49: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 6F17037B502; Fri, 13 Oct 2000 00:49:01 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id JAA06870; Fri, 13 Oct 2000 09:49:03 +0200 (CEST) (envelope-from kuku) Date: Fri, 13 Oct 2000 09:49:03 +0200 From: Christoph Kukulies To: Christoph Kukulies Cc: freebsd-current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: scp times out or gets crc errors Message-ID: <20001013094903.A6840@gil.physik.rwth-aachen.de> References: <200010130745.JAA06813@gilberto.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200010130745.JAA06813@gilberto.physik.rwth-aachen.de>; from kuku@gilberto.physik.rwth-aachen.de on Fri, Oct 13, 2000 at 09:45:03AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forgot to mention that it's -current of two days ago while it used to work on a 6 months old -current. On Fri, Oct 13, 2000 at 09:45:03AM +0200, Christoph Kukulies wrote: > I'm getting strange crc errors and timeouts when trying to use scp (secure > rcp from ssh) to copy some files. > > kuku> scp *.jpg remotehost: > kuku@remotehost.de's password: > kukuck1.jpg 100% |*****************************| 196 KB 00:06 > Read from remote host kuku@remotehost.de: Operation timed out > lost connection > > I'm not sure whether it could be also an isdn issue so I'm cc'ing to the > isdn list. > > -- > Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 5:22:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id 4EEA637B503 for ; Fri, 13 Oct 2000 05:22:21 -0700 (PDT) Received: (qmail 31372 invoked by uid 100); 13 Oct 2000 12:22:20 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14822.65148.853175.915459@guru.mired.org> Date: Fri, 13 Oct 2000 07:22:20 -0500 (CDT) To: current@freebsd.org Subject: /boot partition? X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just curious - now that the kernel has moved into /boot/kernel/kernel, does anyone know how well would it work to put /boot in it's own partition (possibly in it's own slice)? Thanx, ; Fri, 13 Oct 2000 06:36:05 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e9DDa4N00592 for ; Fri, 13 Oct 2000 15:36:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: DO_DEFLATE / PPP_DEFLATE confusion ? From: Poul-Henning Kamp Date: Fri, 13 Oct 2000 15:36:04 +0200 Message-ID: <590.971444164@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can somebody please figure out if this option should be called DO_DEFLATE or PPP_DEFLATE please ?? Poul-Henning Index: conf/options =================================================================== RCS file: /home/ncvs/src/sys/conf/options,v retrieving revision 1.230 diff -u -r1.230 options --- conf/options 2000/10/03 18:06:24 1.230 +++ conf/options 2000/10/13 12:38:44 @@ -257,6 +257,8 @@ NETATALK opt_atalk.h PPP_BSDCOMP opt_ppp.h PPP_DEFLATE opt_ppp.h +DO_DEFLATE opt_ppp.h +DO_BSD_COMPRESS opt_ppp.h PPP_FILTER opt_ppp.h SLIP_IFF_OPTS opt_slip.h TCP_COMPAT_42 opt_compat.h Index: i386/conf/NOTES =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/NOTES,v retrieving revision 1.836 diff -u -r1.836 NOTES --- i386/conf/NOTES 2000/10/10 14:23:04 1.836 +++ i386/conf/NOTES 2000/10/13 12:34:02 @@ -498,6 +498,8 @@ options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpf) +options DO_DEFLATE #??? +options DO_BSD_COMPRESS #??? device ef # Multiple ethernet frames support options ETHER_II # enable Ethernet_II frame Index: net/bsd_comp.c =================================================================== RCS file: /home/ncvs/src/sys/net/bsd_comp.c,v retrieving revision 1.11 diff -u -r1.11 bsd_comp.c --- net/bsd_comp.c 1999/08/28 00:48:14 1.11 +++ net/bsd_comp.c 2000/10/13 12:39:22 @@ -43,6 +43,7 @@ * $FreeBSD: src/sys/net/bsd_comp.c,v 1.11 1999/08/28 00:48:14 peter Exp $ */ +#include "opt_ppp.h" #include #include #include Index: net/ppp_deflate.c =================================================================== RCS file: /home/ncvs/src/sys/net/ppp_deflate.c,v retrieving revision 1.12 diff -u -r1.12 ppp_deflate.c --- net/ppp_deflate.c 1999/08/28 00:48:26 1.12 +++ net/ppp_deflate.c 2000/10/13 12:39:41 @@ -29,6 +29,7 @@ * OR MODIFICATIONS. */ +#include "opt_ppp.h" #include #include #include -- 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-current" in the body of the message From owner-freebsd-current Fri Oct 13 8:18:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (roaming.cacheboy.net [203.56.168.69]) by hub.freebsd.org (Postfix) with ESMTP id E072437B502 for ; Fri, 13 Oct 2000 08:18:39 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id e9DFHbQ20523 for freebsd-current@freebsd.org; Fri, 13 Oct 2000 17:17:37 +0200 (CEST) (envelope-from adrian) Date: Fri, 13 Oct 2000 17:17:37 +0200 From: Adrian Chadd To: freebsd-current@freebsd.org Subject: HEADS UP: fsck wrappers gotcha Message-ID: <20001013171737.A20476@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As pointed out by mr Sobolev, the fsck wrappers will blindly try to execute fsck_$FS regardless of whether its there or not, and fail if it isn't. This is a gotcha for non-fsck'able fses right now, such as nfs and ntfs. The solution, which I forgot to add in my email, is to set pass to 0. This forces fsck to NOT consider the FS for fsck-on-boot, and should make things quieter. Note that swap / procfs in /etc/fstab already use dump/pass = 0, but this is just to make sure. Just FYI, Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 8:38: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from valcho.net (valcho.net [208.10.211.61]) by hub.freebsd.org (Postfix) with SMTP id AEAA037B66C for ; Fri, 13 Oct 2000 08:38:00 -0700 (PDT) Received: (qmail 10434 invoked by uid 1000); 13 Oct 2000 15:37:57 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 13 Oct 2000 15:37:57 -0000 Date: Fri, 13 Oct 2000 11:37:57 -0400 (EDT) From: Valentin Chopov To: freebsd-current@freebsd.org Subject: ata-raid.c Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ata-raid.c is missing from sys/conf/files Val To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 9:11:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 5602237B503 for ; Fri, 13 Oct 2000 09:11:22 -0700 (PDT) Received: by peorth.iteration.net (Postfix, from userid 1001) id 9B8E85730B; Fri, 13 Oct 2000 11:11:25 -0500 (CDT) Date: Fri, 13 Oct 2000 11:11:25 -0500 From: "Michael C . Wu" To: Mike Meyer Cc: current@freebsd.org Subject: Re: /boot partition? Message-ID: <20001013111125.A318@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <14822.65148.853175.915459@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14822.65148.853175.915459@guru.mired.org>; from mwm@mired.org on Fri, Oct 13, 2000 at 07:22:20AM -0500 X-FreeBSD-Header: This is a subliminal message from the vast FreeBSD conspiracy project. X-Operating-System: FreeBSD peorth.iteration.net 4.1.1-RELEASE FreeBSD 4.1.1-RELEASE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 13, 2000 at 07:22:20AM -0500, Mike Meyer scribbled: | Just curious - now that the kernel has moved into /boot/kernel/kernel, | does anyone know how well would it work to put /boot in it's own | partition (possibly in it's own slice)? I do not think loader can see stuff in other partitions. The loader also resides in /boot. Besides, if you can't mount / (including /etc), there really is no point to keep /boot somewhere else. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 9:18:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 44E0D37B66C for ; Fri, 13 Oct 2000 09:18:24 -0700 (PDT) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.109]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id e9DGK9m04003; Fri, 13 Oct 2000 19:20:09 +0300 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.0/8.9.3) with ESMTP id e9DGI8U52616; Fri, 13 Oct 2000 19:18:08 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <39E735BD.8BDA697C@FreeBSD.org> Date: Fri, 13 Oct 2000 19:18:05 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "Michael C . Wu" Cc: Mike Meyer , current@FreeBSD.org Subject: Re: /boot partition? References: <14822.65148.853175.915459@guru.mired.org> <20001013111125.A318@peorth.iteration.net> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Michael C . Wu" wrote: > On Fri, Oct 13, 2000 at 07:22:20AM -0500, Mike Meyer scribbled: > | Just curious - now that the kernel has moved into /boot/kernel/kernel, > | does anyone know how well would it work to put /boot in it's own > | partition (possibly in it's own slice)? > > I do not think loader can see stuff in other partitions. Nope, the loader can load stuff from other partitions, even from some strange ones like msdos ;), so theoretically it should be possible to have /boot, or even /boot/kernel, on another partition (it may require to tweak loader config files, though), but I really do not see any reasons behind such weird setup. > The loader also resides in /boot. > Besides, if you can't mount / (including /etc), there really is no > point to keep /boot somewhere else. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 9:56:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 167AC37B503 for ; Fri, 13 Oct 2000 09:56:11 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.1/8.11.1) id e9DH1x507471 for freebsd-current@freebsd.org; Fri, 13 Oct 2000 10:01:59 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200010131701.e9DH1x507471@troutmask.apl.washington.edu> Subject: removing global from tree To: FreeBSD Current Date: Fri, 13 Oct 2000 10:01:59 -0700 (PDT) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In revision 1.148 of src/usr.bin/Makefile, the hook for building global was removed. This was 3.5 month ago. Is it time to move src/contrib/global and src/usr.bin/global into the attic? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 10:52: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 6662237B502 for ; Fri, 13 Oct 2000 10:51:54 -0700 (PDT) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G2D00934QX42V@field.videotron.net> for FreeBSD-current@FreeBSD.ORG; Fri, 13 Oct 2000 13:51:04 -0400 (EDT) Date: Fri, 13 Oct 2000 13:55:15 -0400 (EDT) From: Bosko Milekic Subject: Re: Panic "m_copydata, negative off" out of tcp_output In-reply-to: <20001013125809.K2593@wantadilla.lemis.com> X-Sender: bmilekic@jehovah.technokratis.com To: Greg Lehey Cc: FreeBSD current users Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this with code before or after the race condition in the sockbuf limiting code was fixed? On Fri, 13 Oct 2000, Greg Lehey wrote: > I've been having a few panics lately with a PRE_SMPNG snap: [...] > Does anybody recognize this? > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 11:29:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from eeyore.local.dohd.org (d0030.dtk.chello.nl [213.46.0.30]) by hub.freebsd.org (Postfix) with ESMTP id 4CB0237B66F for ; Fri, 13 Oct 2000 11:29:21 -0700 (PDT) Received: by eeyore.local.dohd.org (Postfix, from userid 1008) id AA0ECBB0B; Fri, 13 Oct 2000 20:29:23 +0200 (MET DST) Date: Fri, 13 Oct 2000 20:29:23 +0200 From: Mark Huizer To: current@freebsd.org Subject: Hangs on 'heavy' diskaccess Message-ID: <20001013202923.A728@dohd.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A few of my machines are getting hangs, running -current. At the moment of the hang, everything freezes, no more keyboard response, so I can't do any debugging. What I know about the machine at the moment is this: It's doing disk intensitive stuff (like a cvsup mirror doing a cvsup to sync with the master). So it seems like it is deadlocking in there somewhere. Do other people have these problems as well? Mark -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 12:22:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 00F2C37B66E for ; Fri, 13 Oct 2000 12:22:36 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA67922; Fri, 13 Oct 2000 21:30:31 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200010131930.VAA67922@freebsd.dk> Subject: Re: Hangs on 'heavy' diskaccess In-Reply-To: <20001013202923.A728@dohd.cx> from Mark Huizer at "Oct 13, 2000 08:29:23 pm" To: freebsd@dohd.org (Mark Huizer) Date: Fri, 13 Oct 2000 21:30:31 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Mark Huizer wrote: > A few of my machines are getting hangs, running -current. At the moment > of the hang, everything freezes, no more keyboard response, so I can't > do any debugging. > > What I know about the machine at the moment is this: > It's doing disk intensitive stuff (like a cvsup mirror doing a cvsup to > sync with the master). So it seems like it is deadlocking in there > somewhere. > > Do other people have these problems as well? Yes, I cant use -current for that exact reason.... Go back to PRE_SMPNG and things work again.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 12:25: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from eeyore.local.dohd.org (d0030.dtk.chello.nl [213.46.0.30]) by hub.freebsd.org (Postfix) with ESMTP id E4AE637B671 for ; Fri, 13 Oct 2000 12:25:04 -0700 (PDT) Received: by eeyore.local.dohd.org (Postfix, from userid 1008) id 449B5BB0A; Fri, 13 Oct 2000 21:25:01 +0200 (MET DST) Date: Fri, 13 Oct 2000 21:25:00 +0200 From: Mark Huizer To: current@freebsd.org Subject: Re: Hangs on 'heavy' diskaccess Message-ID: <20001013212500.A14024@dohd.cx> References: <20001013202923.A728@dohd.cx> <200010131930.VAA67922@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <200010131930.VAA67922@freebsd.dk>; from sos@freebsd.dk on Fri, Oct 13, 2000 at 09:30:31PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 13, 2000 at 09:30:31PM +0200, Soren Schmidt wrote: > It seems Mark Huizer wrote: > > A few of my machines are getting hangs, running -current. At the moment > > of the hang, everything freezes, no more keyboard response, so I can't > > do any debugging. > > > > What I know about the machine at the moment is this: > > It's doing disk intensitive stuff (like a cvsup mirror doing a cvsup to > > sync with the master). So it seems like it is deadlocking in there > > somewhere. > > > > Do other people have these problems as well? > > Yes, I cant use -current for that exact reason.... > > Go back to PRE_SMPNG and things work again.... > > -Søren Hmm... I was trying to find a way to do something debugable here :-( sounds like a tough problem. Mark -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 12:50: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from eeyore.local.dohd.org (d0030.dtk.chello.nl [213.46.0.30]) by hub.freebsd.org (Postfix) with ESMTP id 3B4F437B670 for ; Fri, 13 Oct 2000 12:50:07 -0700 (PDT) Received: by eeyore.local.dohd.org (Postfix, from userid 1008) id 3812ABB0A; Fri, 13 Oct 2000 21:50:05 +0200 (MET DST) Date: Fri, 13 Oct 2000 21:50:05 +0200 From: Mark Huizer To: current@freebsd.org Subject: latest changes to pci/if_* Message-ID: <20001013215004.A16974@dohd.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seem to miss a definition for struct mtx: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing -prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -no stdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/mii/dcphy.c In file included from ../../dev/mii/dcphy.c:69: ../../pci/if_dcreg.h:679: field `dc_mtx' has incomplete type *** Error code 1 -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 14:48:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR8-44.accesscable.net [24.138.8.44]) by hub.freebsd.org (Postfix) with ESMTP id 370F437B66D for ; Fri, 13 Oct 2000 14:48:26 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.0) with ESMTP id e9DLkxp03796; Fri, 13 Oct 2000 18:46:59 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 13 Oct 2000 18:46:59 -0300 (ADT) From: The Hermit Hacker To: Mark Huizer Cc: current@FreeBSD.ORG Subject: Re: Hangs on 'heavy' diskaccess In-Reply-To: <20001013202923.A728@dohd.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Oct 2000, Mark Huizer wrote: > A few of my machines are getting hangs, running -current. At the moment > of the hang, everything freezes, no more keyboard response, so I can't > do any debugging. > > What I know about the machine at the moment is this: > It's doing disk intensitive stuff (like a cvsup mirror doing a cvsup to > sync with the master). So it seems like it is deadlocking in there > somewhere. > > Do other people have these problems as well? yup, I can usually trigger it with a simple 'make world', but a 'make -j16 world' accelerates it ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 15:11:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9A06F37B66D; Fri, 13 Oct 2000 15:11:49 -0700 (PDT) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id AAA36737; Sat, 14 Oct 2000 00:11:47 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.0/8.11.0) with SMTP id e9DJTOG52192; Fri, 13 Oct 2000 21:29:30 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <008b01c0354b$f2820340$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: "Maxim Sobolev" , "Michael C . Wu" Cc: "Mike Meyer" , References: <14822.65148.853175.915459@guru.mired.org> <20001013111125.A318@peorth.iteration.net> <39E735BD.8BDA697C@FreeBSD.org> Subject: Re: /boot partition? Date: Fri, 13 Oct 2000 21:24:37 +0200 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Michael C . Wu" wrote: > > > On Fri, Oct 13, 2000 at 07:22:20AM -0500, Mike Meyer scribbled: > > | Just curious - now that the kernel has moved into /boot/kernel/kernel, > > | does anyone know how well would it work to put /boot in it's own > > | partition (possibly in it's own slice)? > > > > I do not think loader can see stuff in other partitions. > > Nope, the loader can load stuff from other partitions, even from some strange > ones like msdos ;), so theoretically it should be possible to have /boot, or > even /boot/kernel, on another partition (it may require to tweak loader config > files, though), but I really do not see any reasons behind such weird setup. > Is it possible to boot from very large disks? If not, then somebody might want to have a small /boot and the entire rest of the disk as / Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 15:33:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 3D16137B671 for ; Fri, 13 Oct 2000 15:33:15 -0700 (PDT) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id SAA05650 for freebsd-current@freebsd.org; Fri, 13 Oct 2000 18:32:55 -0400 (EDT) Date: Fri, 13 Oct 2000 18:32:55 -0400 (EDT) From: Daniel Eischen Message-Id: <200010132232.SAA05650@pcnet1.pcnet.com> To: freebsd-current@freebsd.org Subject: Recent thread changes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just committed some changes to the threads library and would appreciate feedback from anyone running threaded applications. They include fixes that -stable could really use. This commit also implements zero system call thread context switching in the threads library. Switching between threads is now much faster than before this change. At the end is a performance test for thread switches. The test program creates 10 threads that do nothing but pthread_yield(). Please realize that this is not an example of a typical application. Some applications may not see any noticeable improvement. The range of valid priorities has also changed, perhaps requiring a library version bump. The range of valid priorities is not visible outside of the threads library. The only way it can be determined is through trial and error, so it _shouldn't_ be an issue. BTW, _PTHREADS_INVARIANTS is the default for a while until I'm sure there aren't any major problems. The performance hit should be negligible. Edit src/lib/libc_r/Makefile to turn it off. Before After ------------------------------------------------------------- Thread 0 iterations: 35400 Thread 0 iterations: 259131 Thread 1 iterations: 35400 Thread 1 iterations: 259131 Thread 2 iterations: 35399 Thread 2 iterations: 259131 Thread 3 iterations: 35399 Thread 3 iterations: 259130 Thread 4 iterations: 35399 Thread 4 iterations: 259130 Thread 5 iterations: 35399 Thread 5 iterations: 259130 Thread 6 iterations: 35399 Thread 6 iterations: 259130 Thread 7 iterations: 35399 Thread 7 iterations: 259130 Thread 8 iterations: 35399 Thread 8 iterations: 259130 Thread 9 iterations: 35399 Thread 9 iterations: 259130 Total iterations: 353992 Total iterations: 2591303 real 0m10.043s real 0m10.153s user 0m3.558s user 0m9.947s sys 0m6.445s sys 0m0.010s -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 17:26:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 8729137B66D for ; Fri, 13 Oct 2000 17:26:24 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9E0QKA47932 for ; Fri, 13 Oct 2000 17:26:20 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: current@freebsd.org Subject: Kernel breakage in tonite's -current Date: Fri, 13 Oct 2000 17:26:20 -0700 Message-ID: <47929.971483180@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -c /usr/src/sys/modules/mii/../../dev/mii/dcphy.c In file included from /usr/src/sys/modules/mii/../../dev/mii/dcphy.c:69: @/pci/if_dcreg.h:679: field `dc_mtx' has incomplete type *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 13 18:40: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 5104E37B66F for ; Fri, 13 Oct 2000 18:40:01 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9E1dh537610; Fri, 13 Oct 2000 18:39:43 -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: <47929.971483180@winston.osd.bsdi.com> Date: Fri, 13 Oct 2000 18:40:02 -0700 (PDT) From: John Baldwin To: Jordan Hubbard Subject: RE: Kernel breakage in tonite's -current Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Oct-00 Jordan Hubbard wrote: > cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ > -I@/../include -mpreferred-stack-boundary=2 -c /usr/src/sys/modules/mii/../.. > /dev/mii/dcphy.c > In file included from /usr/src/sys/modules/mii/../../dev/mii/dcphy.c:69: > @/pci/if_dcreg.h:679: field `dc_mtx' has incomplete type > *** Error code 1 Bill Paul fixed this several hours ago. cvsup and try again. :-) -- 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-current" in the body of the message From owner-freebsd-current Fri Oct 13 20:41:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B4EFC37B675 for ; Fri, 13 Oct 2000 20:41:39 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id UAA05435 for ; Fri, 13 Oct 2000 20:41:39 -0700 Date: Fri, 13 Oct 2000 20:38:34 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: modules again non-shareable? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Didn't this get fixed a while back? I have a shared /sys (nfs mounted) so I can work from the same source for i386 && alpha- I loopback mount the compile directory (would that nullfs worked!)- but now something seems to have changed so that turdlets are being created in the modules directory? What happened? [ compilation here on a freshly populated modules.... wierd... tstsys/modules/syscons/logo/machine/alpha_cpu.h: In function `alpha_pal_wrusp': /tstsys/modules/syscons/logo/machine/alpha_cpu.h:512: invalid register name `$16' for register variable /tstsys/modules/syscons/logo/machine/alpha_cpu.h:517: unknown register name `$25' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:517: unknown register name `$24' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:517: unknown register name `$23' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:517: unknown register name `$22' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:517: unknown register name `$1' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h: In function `alpha_pal_wrperfmon': /tstsys/modules/syscons/logo/machine/alpha_cpu.h:523: invalid register name `$0' for register variable /tstsys/modules/syscons/logo/machine/alpha_cpu.h:524: invalid register name `$16' for register variable /tstsys/modules/syscons/logo/machine/alpha_cpu.h:525: invalid register name `$17' for register variable /tstsys/modules/syscons/logo/machine/alpha_cpu.h:530: unknown register name `$25' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:530: unknown register name `$24' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:530: unknown register name `$23' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:530: unknown register name `$22' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:530: unknown register name `$1' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h: In function `alpha_pal_rdusp': /tstsys/modules/syscons/logo/machine/alpha_cpu.h:537: invalid register name `$0' for register variable /tstsys/modules/syscons/logo/machine/alpha_cpu.h:542: unknown register name `$25' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:542: unknown register name `$24' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:542: unknown register name `$23' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:542: unknown register name `$22' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:542: unknown register name `$1' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h: In function `alpha_pal_whami': /tstsys/modules/syscons/logo/machine/alpha_cpu.h:549: invalid register name `$0' for register variable /tstsys/modules/syscons/logo/machine/alpha_cpu.h:554: unknown register name `$25' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:554: unknown register name `$24' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:554: unknown register name `$23' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:554: unknown register name `$22' in `asm' /tstsys/modules/syscons/logo/machine/alpha_cpu.h:554: unknown register name `$1' in `asm' In file included from /tstsys/modules/syscons/logo/logo_saver.c:32: @/sys/systm.h: At top level: @/sys/systm.h:142: warning: conflicting types for built-in function `memcpy' *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 0: 6: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id ECC8137B66F for ; Sat, 14 Oct 2000 00:06:05 -0700 (PDT) Received: (qmail 38406 invoked by uid 100); 13 Oct 2000 17:39:24 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14823.18636.646339.740562@guru.mired.org> Date: Fri, 13 Oct 2000 12:39:24 -0500 (CDT) To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: /boot partition? In-Reply-To: <39E735BD.8BDA697C@FreeBSD.org> References: <14822.65148.853175.915459@guru.mired.org> <20001013111125.A318@peorth.iteration.net> <39E735BD.8BDA697C@FreeBSD.org> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev writes: > "Michael C . Wu" wrote: > > On Fri, Oct 13, 2000 at 07:22:20AM -0500, Mike Meyer scribbled: > > | Just curious - now that the kernel has moved into /boot/kernel/kernel, > > | does anyone know how well would it work to put /boot in it's own > > | partition (possibly in it's own slice)? > > I do not think loader can see stuff in other partitions. > Nope, the loader can load stuff from other partitions, even from some strange > ones like msdos ;), so theoretically it should be possible to have /boot, or > even /boot/kernel, on another partition (it may require to tweak loader config > files, though), but I really do not see any reasons behind such weird setup. Since you implied a question... This is a standard setup for Linux, so Linux people dealing with problems with the root file system try and make it work in -stable (with no luck). The best example would be to make /boot one file system so you can get vinum loaded and running, then have everything else on a vinum disk. This minimizes the set of things you don't have on vinum. ; Sat, 14 Oct 2000 00:29:52 -0700 (PDT) Received: from fmrl02.sul.t-online.de by mailout00.sul.t-online.com with smtp id 13kLlN-0003vN-00; Sat, 14 Oct 2000 09:29:49 +0200 Received: from neutron.cichlids.com (520050424122-0001@[62.158.38.6]) by fmrl02.sul.t-online.com with esmtp id 13kLlK-0mwyn2C; Sat, 14 Oct 2000 09:29:46 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 13AC0AB91; Sat, 14 Oct 2000 09:31:36 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 5323A14B29; Sat, 14 Oct 2000 09:29:50 +0200 (CEST) Date: Sat, 14 Oct 2000 09:29:50 +0200 To: Warner Losh Cc: Wesley Morgan , current@FreeBSD.ORG Subject: Re: pcmcia and ed Message-ID: <20001014092950.B7171@cichlids.cichlids.com> Mail-Followup-To: alex@cichlids.cichlids.com, Warner Losh , Wesley Morgan , current@FreeBSD.ORG References: <200010071803.MAA01359@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010071803.MAA01359@harmony.village.org>; from imp@village.org on Sat, Oct 07, 2000 at 12:03:15PM -0600 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. From: alex@big.endian.de (Alexander Langer) X-Sender: 520050424122-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Warner Losh (imp@village.org): > The module name should be if_ed. I'll go fix it. Did you do this already? And if so, where? I'd love to know. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 1:12:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 81BF937B66E; Sat, 14 Oct 2000 01:12:09 -0700 (PDT) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.9.3) with UUCP id e9E8C7U81384; Sat, 14 Oct 2000 10:12:07 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.0/8.11.0) with ESMTP id e9E7TsG96216; Sat, 14 Oct 2000 09:29:55 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Sat, 14 Oct 2000 09:29:53 +0200 (CEST) From: Leif Neland To: Gregory Neil Shapiro Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP: sendmail related changes In-Reply-To: <14819.23999.720997.102041@horsey.gshapiro.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Oct 2000, Gregory Neil Shapiro wrote: > The following changes have been made in -CURRENT: > > 1. mail.local(8) is no longer installed as a set-user-id binary. > > If you are using a /etc/mail/sendmail.cf from the default sendmail.cf > included with FreeBSD any time after 3.1.0, you are fine. If you are > using a hand-configured sendmail.cf and mail.local for delivery, check > to make sure the F=S flag is set on the Mlocal line. Those with .mc > files who need to add the flag can do so by adding the following line to > their your .mc file and regenerating the sendmail.cf file: Is there a way to make make world use my own sendmail.mc? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 1:13:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id C237037B66D for ; Sat, 14 Oct 2000 01:13:31 -0700 (PDT) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.11.2.PreAlpha0/8.11.2.PreAlpha0) id e9E8DR149531; Sat, 14 Oct 2000 01:13:27 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14824.5543.162884.941930@horsey.gshapiro.net> Date: Sat, 14 Oct 2000 01:13:27 -0700 (PDT) From: Gregory Neil Shapiro To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP: sendmail related changes In-Reply-To: References: <14819.23999.720997.102041@horsey.gshapiro.net> X-Mailer: VM 6.75 under 21.2 (beta36) "Notus" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG leifn> Is there a way to make make world use my own sendmail.mc? There will be soon. I hope to have it in place before or during BSDcon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 3: 4: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id E56AA37B66C for ; Sat, 14 Oct 2000 03:04:03 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id DAA04787; Sat, 14 Oct 2000 03:03:58 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id e9EA3vc44149; Sat, 14 Oct 2000 03:03:57 -0700 (PDT) (envelope-from jdp) Date: Sat, 14 Oct 2000 03:03:57 -0700 (PDT) From: jdp@polstra.com Message-Id: <200010141003.e9EA3vc44149@vashon.polstra.com> To: current@freebsd.org Reply-To: current@freebsd.org Cc: sgk@troutmask.apl.washington.edu Subject: Re: removing global from tree In-Reply-To: <200010131701.e9DH1x507471@troutmask.apl.washington.edu> References: <200010131701.e9DH1x507471@troutmask.apl.washington.edu> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200010131701.e9DH1x507471@troutmask.apl.washington.edu>, Steve Kargl wrote: > In revision 1.148 of src/usr.bin/Makefile, the hook for building > global was removed. This was 3.5 month ago. Is it time to move > src/contrib/global and src/usr.bin/global into the attic? Yes, it should have been done at the time it was removed from the Makefile. 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-current" in the body of the message From owner-freebsd-current Sat Oct 14 3: 9: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A74BA37B66C for ; Sat, 14 Oct 2000 03:09:02 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id DAA04822; Sat, 14 Oct 2000 03:08:54 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id e9EA8sG44179; Sat, 14 Oct 2000 03:08:54 -0700 (PDT) (envelope-from jdp) Date: Sat, 14 Oct 2000 03:08:54 -0700 (PDT) From: jdp@polstra.com Message-Id: <200010141008.e9EA8sG44179@vashon.polstra.com> To: current@freebsd.org Cc: eischen@vigrid.com Subject: Re: Recent thread changes In-Reply-To: <200010132232.SAA05650@pcnet1.pcnet.com> References: <200010132232.SAA05650@pcnet1.pcnet.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200010132232.SAA05650@pcnet1.pcnet.com>, Daniel Eischen wrote: > > I've just committed some changes to the threads library > and would appreciate feedback from anyone running threaded > applications. They include fixes that -stable could really > use. > > This commit also implements zero system call thread context > switching in the threads library. Switching between threads > is now much faster than before this change. This sounds like great stuff! > The range of valid priorities has also changed, perhaps > requiring a library version bump. The range of valid priorities > is not visible outside of the threads library. The only > way it can be determined is through trial and error, so > it _shouldn't_ be an issue. I thought you could get that information with sched_get_priority_min() and sched_get_priority_max(). Is that not the case? 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-current" in the body of the message From owner-freebsd-current Sat Oct 14 3:27:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id AAA6A37B66C for ; Sat, 14 Oct 2000 03:27:52 -0700 (PDT) Received: (from kris@localhost) by citusc17.usc.edu (8.9.3/8.9.3) id DAA10757; Sat, 14 Oct 2000 03:29:49 -0700 (PDT) Date: Sat, 14 Oct 2000 03:29:49 -0700 From: Kris Kennaway To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: modules again non-shareable? Message-ID: <20001014032949.A10733@citusc17.usc.edu> 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 mjacob@feral.com on Fri, Oct 13, 2000 at 08:38:34PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 13, 2000 at 08:38:34PM -0700, Matthew Jacob wrote: > would that nullfs worked! It does, modulo remaining bugs which Boris hasnt yet fixed. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 4:20:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 9981437B66C for ; Sat, 14 Oct 2000 04:20:43 -0700 (PDT) Received: (qmail 6395 invoked by uid 0); 14 Oct 2000 11:20:39 -0000 Received: from p3ee21638.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.56) by mail.gmx.net with SMTP; 14 Oct 2000 11:20:39 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id MAA29141 for current@FreeBSD.ORG; Sat, 14 Oct 2000 12:35:59 +0200 Date: Sat, 14 Oct 2000 12:35:58 +0200 From: Gerhard Sittig To: current@FreeBSD.ORG Subject: Re: /boot partition? Message-ID: <20001014123558.K25237@speedy.gsinet> Mail-Followup-To: current@FreeBSD.ORG References: <14822.65148.853175.915459@guru.mired.org> <20001013111125.A318@peorth.iteration.net> <39E735BD.8BDA697C@FreeBSD.org> <14823.18636.646339.740562@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14823.18636.646339.740562@guru.mired.org>; from mwm@mired.org on Fri, Oct 13, 2000 at 12:39:24PM -0500 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 13, 2000 at 12:39 -0500, Mike Meyer wrote: > > [ ... separate /boot partition ... ] > > Since you implied a question... > > This is a standard setup for Linux, so Linux people dealing with > problems with the root file system try and make it work in -stable > (with no luck). The best example would be to make /boot one file > system so you can get vinum loaded and running, then have everything > else on a vinum disk. This minimizes the set of things you don't have > on vinum. Since you bring the Linux analogy in ... There's a mechanism used by some Linux distros (strictly speaking: available to all Linux users, but rarely used by default) to have a ramdisk with the kernel and essential drivers. This ramdisk can be handled by many boot managers and the effect is that - you don't need all the drivers you need for booting in the kernel itself -- they can be modules, too - you can have all your fses in software raid configuration and yet survive the boot stage, since the boot kernel won't have a need to touch and handle the raid configuration But I feel that a separate /boot partition will never work when you can't reach the / fs -- where are you going to mount the /boot fs? The idea is always that you have to bring in everything you need to get over the initial steps. Without vinum drivers and setup tools you cannot access vinum volumes. And when the tools live on a vinum volume themselves, you're trapped. That's when you need a separate "selfcontained" mechanism -- like a mfs or ramdisk thing. BTW: One of the most commonly seen failures is to compile a new kernel and not updating the ramdisk needed for booting ... virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 5:35:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id B7A4637B502 for ; Sat, 14 Oct 2000 05:35:43 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id FAA89247; Sat, 14 Oct 2000 05:35:28 -0700 (PDT) (envelope-from obrien) Date: Sat, 14 Oct 2000 05:35:27 -0700 From: "David O'Brien" To: Steve Kargl Cc: FreeBSD Current Subject: Re: removing global from tree Message-ID: <20001014053527.B89181@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200010131701.e9DH1x507471@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010131701.e9DH1x507471@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Fri, Oct 13, 2000 at 10:01:59AM -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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 13, 2000 at 10:01:59AM -0700, Steve Kargl wrote: > In revision 1.148 of src/usr.bin/Makefile, the hook for building > global was removed. This was 3.5 month ago. Is it time to move > src/contrib/global and src/usr.bin/global into the attic? Wow, that is still there. I forgot about it. I'll take care of this weekend. On Sat, Oct 14, 2000 at 03:03:57AM -0700, jdp@polstra.com wrote: > Yes, it should have been done at the time it was removed from the > Makefile. I didn't put it in the Attic when I disconnected it from the build in case someone came forward screaming about removing it. I figured it was much easier to back out a Makefile commit than get things from the Attic back to being alive. I had actually forgotten about it as no one did come forward. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 6:34:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 08E1E37B66C for ; Sat, 14 Oct 2000 06:34:39 -0700 (PDT) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id JAA15512; Sat, 14 Oct 2000 09:34:16 -0400 (EDT) Date: Sat, 14 Oct 2000 09:34:15 -0400 (EDT) From: Daniel Eischen To: jdp@polstra.com Cc: current@freebsd.org Subject: Re: Recent thread changes In-Reply-To: <200010141008.e9EA8sG44179@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Oct 2000 jdp@polstra.com wrote: > In article <200010132232.SAA05650@pcnet1.pcnet.com>, > Daniel Eischen wrote: > > The range of valid priorities has also changed, perhaps > > requiring a library version bump. The range of valid priorities > > is not visible outside of the threads library. The only > > way it can be determined is through trial and error, so > > it _shouldn't_ be an issue. > > I thought you could get that information with sched_get_priority_min() > and sched_get_priority_max(). Is that not the case? Not really. Those return the kernels POSIX priority range for processes. I am unsure as to how to deal with those in the threads library; do we want to wrap those system calls and return thread priority ranges? The kernels range for SCHED_OTHER is -20 .. 20, and 0 .. 31 for SCHED_FIFO and SCHED_RR. The threads library priority range changed from 0 .. 126 to 0 .. 31 (for all scheduling classes). Anyone using sched_get_priority_{min|max} for _thread_ priority ranges would have problems if the scheduling class was SCHED_OTHER, but wouldn't see any difference for SCHED_FIFO or SCHED_RR. Still, I know this change breaks at least one port; lang/gnat uses the full range of priorities, only because it was my port and I knew the priority range of the threads library. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 7:57:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 2066437B502; Sat, 14 Oct 2000 07:57:42 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id KAA64151; Sat, 14 Oct 2000 10:57:45 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Sat, 14 Oct 2000 10:57:45 -0400 (EDT) From: "Brandon D. Valentine" To: Gregory Neil Shapiro Cc: Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP: sendmail related changes In-Reply-To: <14824.5543.162884.941930@horsey.gshapiro.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Oct 2000, Gregory Neil Shapiro wrote: >leifn> Is there a way to make make world use my own sendmail.mc? > >There will be soon. I hope to have it in place before or during BSDcon. At one time there was a make.conf knob for it, is that not still around? -- Brandon D. Valentine "Few things are harder to put up with than the annoyance of a good example." -- Mark Twain, Pudd'nhead Wilson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 9: 8:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail4.nycap.rr.com (mail4-1.nyroc.rr.com [24.92.33.20]) by hub.freebsd.org (Postfix) with ESMTP id EA17A37B671 for ; Sat, 14 Oct 2000 09:08:15 -0700 (PDT) Received: from [24.161.45.173] ([24.169.217.142]) by mail4.nycap.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-59787U250000L250000S0V35) with SMTP id com for ; Sat, 14 Oct 2000 12:12:20 -0400 Received: (qmail 24914 invoked by uid 1001); 14 Oct 2000 16:08:14 -0000 Date: Sat, 14 Oct 2000 12:08:14 -0400 From: Hasan Diwan To: freebsd-current@freebsd.org Subject: problems and suggestions (CURRENT) Message-ID: <20001014120814.A24853@thor.nycap.rr.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="liOOAslEiF7prFVr" X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sometime between October 6 and yesterday (I haven't verified with today's sources), make installkernel dies with a usage message for the install command. buildworld and buildkernel go through ok. I believe the issue is in the order the arguments are called, and if I knew which =2Emk file told this, I'd provide a patch.=20 'boot -s' appears to have stopped working as well during the same time period. NFS portmapper dies on startup. This also happened during the same time period. The last has to do with the 'ed' driver and the latest Netgear PCMCIA FA410TX card. I have a program to write the speed info to the EPROM and am wondering if/when it will be included in the kernel.=20 --=20 Hasan Diwan [hdiwan@pobox.com] :) Rensselaer Polytechnic Institute=20 Computer Science Department http://www.pobox.com/~hdiwan --liOOAslEiF7prFVr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQCVAwUBOeiE7vitTU38wbMJAQENOAP/TzSbbVPJqC7jR0WCpT964IdDmrXttj13 jLGOUt2t1XW9ayuVt8jztS/KCILQr/lVQnotPwnVMS9b+tjIRo7VOpwHNviAgpQ8 HCOzwIrgkLAqx1MwjOq2ayS/Q7ogY4+NFw99F9t1td8fKDo3elHq0sqPLnsBmlUl 1+FnfyeFSTU= =rp6I -----END PGP SIGNATURE----- --liOOAslEiF7prFVr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 9:55:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 71A5037B671 for ; Sat, 14 Oct 2000 09:55:16 -0700 (PDT) Received: (qmail 10152 invoked by uid 0); 14 Oct 2000 16:55:15 -0000 Received: from p3ee21601.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.1) by mail.gmx.net with SMTP; 14 Oct 2000 16:55:15 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id PAA29484 for freebsd-current@freebsd.org; Sat, 14 Oct 2000 15:57:10 +0200 Date: Sat, 14 Oct 2000 15:57:10 +0200 From: Gerhard Sittig To: FreeBSD Current Subject: Re: removing global from tree Message-ID: <20001014155710.P25237@speedy.gsinet> Mail-Followup-To: FreeBSD Current References: <200010131701.e9DH1x507471@troutmask.apl.washington.edu> <20001014053527.B89181@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20001014053527.B89181@dragon.nuxi.com>; from obrien@freebsd.org on Sat, Oct 14, 2000 at 05:35:27AM -0700 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 14, 2000 at 05:35 -0700, David O'Brien wrote: > > I didn't put it in the Attic when I disconnected it from the > build in case someone came forward screaming about removing it. > I figured it was much easier to back out a Makefile commit than > get things from the Attic back to being alive. I had actually > forgotten about it as no one did come forward. Up to now I always thought "the Attic" is something CVS itself takes care of when "cvs rm"ing files. What's that special thing needing manual intervention or special attention you've been talking about lately? Is it for performance reasons or for the warm fuzzy feelings of having "not too rotten a repo"? Sorry for being OT. Of course I welcome pointers to existing documentation and FAQs, too. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 11:14: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 9FE1237B502 for ; Sat, 14 Oct 2000 11:13:56 -0700 (PDT) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id LAA84277; Sat, 14 Oct 2000 11:18:45 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id LAA14274; Sat, 14 Oct 2000 11:16:32 -0700 (PDT) (envelope-from john) Message-Id: <200010141816.LAA14274@john.baldwin.cx> 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: <20001014155710.P25237@speedy.gsinet> Date: Sat, 14 Oct 2000 11:16:32 -0700 (PDT) From: John Baldwin To: Gerhard Sittig Subject: Re: removing global from tree Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Oct-00 Gerhard Sittig wrote: > On Sat, Oct 14, 2000 at 05:35 -0700, David O'Brien wrote: >> >> I didn't put it in the Attic when I disconnected it from the >> build in case someone came forward screaming about removing it. >> I figured it was much easier to back out a Makefile commit than >> get things from the Attic back to being alive. I had actually >> forgotten about it as no one did come forward. > > Up to now I always thought "the Attic" is something CVS itself > takes care of when "cvs rm"ing files. What's that special thing > needing manual intervention or special attention you've been > talking about lately? Is it for performance reasons or for the > warm fuzzy feelings of having "not too rotten a repo"? It is where CVS puts files when you cvs rm them. You just have to do the actual cvs rm/cvs ci. David was cautious because if he had to back the change out, he didn't want to have to try to cvs add all of the files back in. -- 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-current" in the body of the message From owner-freebsd-current Sat Oct 14 12:43:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from netplex.com.au (adsl-64-163-195-99.dsl.snfc21.pacbell.net [64.163.195.99]) by hub.freebsd.org (Postfix) with ESMTP id DCEE237B66F; Sat, 14 Oct 2000 12:43:13 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e9EJhDG47230; Sat, 14 Oct 2000 12:43:13 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200010141943.e9EJhDG47230@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gregory Neil Shapiro Cc: Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP: sendmail related changes In-Reply-To: <14824.5543.162884.941930@horsey.gshapiro.net> Date: Sat, 14 Oct 2000 12:43:13 -0700 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gregory Neil Shapiro wrote: > leifn> Is there a way to make make world use my own sendmail.mc? > > There will be soon. I hope to have it in place before or during BSDcon. Yes, there has been one for ages. Add: "SENDMAIL_CF= myfile.cf" to /etc/make.conf, and the sendmail makefiles will build it from myfile.mc and install it as part of every buildworld. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 13: 0:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id BFDC937B66C for ; Sat, 14 Oct 2000 13:00:47 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA08497; Sat, 14 Oct 2000 13:00:44 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id e9EK0hn47439; Sat, 14 Oct 2000 13:00:43 -0700 (PDT) (envelope-from jdp) Date: Sat, 14 Oct 2000 13:00:43 -0700 (PDT) From: jdp@polstra.com Message-Id: <200010142000.e9EK0hn47439@vashon.polstra.com> To: current@freebsd.org Reply-To: current@freebsd.org Cc: eischen@vigrid.com Subject: Re: Recent thread changes In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Daniel Eischen wrote: > On Sat, 14 Oct 2000 jdp@polstra.com wrote: > > In article <200010132232.SAA05650@pcnet1.pcnet.com>, > > Daniel Eischen wrote: > > > The range of valid priorities has also changed, perhaps > > > requiring a library version bump. The range of valid priorities > > > is not visible outside of the threads library. The only > > > way it can be determined is through trial and error, so > > > it _shouldn't_ be an issue. > > > > I thought you could get that information with sched_get_priority_min() > > and sched_get_priority_max(). Is that not the case? > > Not really. Those return the kernels POSIX priority range for > processes. Hmm, that's not how I interpret the POSIX spec. Here are some excerpts from section 13.2, "Scheduling Policies". That's in the chapter which describes all of the sched_XXX() functions. This model discusses only processor scheduling for runnable threads ... There is, conceptually, one thread list for each priority. Any runnable thread may be on any thread list. Multiple scheduling policies shall be provided. Each nonempty thread list is ordered, contains a head as one end of its order, and a tail as the other. The purpose of a scheduling policy is to define the allowable operations on this set of lists. Each process shall be controlled by an associated scheduling policy and priority. These parameters may be specified by explicit application execution of the sched_setscheduler() or sched_setparam() functions. Each thread shall be controlled by an associated scheduling policy and priority. These parameters may be specified by explicit application execution of the pthread_setschedparam() function. And then in the discussion of the SCHED_FIFO scheduling policy in section 13.2.1, it says: (4) When a running thread calls the sched_setparam() function, the priority of the process specified in the function call is modified to the priority specified by the param argument. If the thread whose priority has been modified is a running thread or is runnable, runnable thread [sic] it then becomes the tail of the thread list for its new priority. (5) When a running thread calls the pthread_setschedparam() function, the thread specified in the function call is modified to the specified policy and the priority specified by the param argument. (6) If a thread whose policy or priority has been modified is a running thread or is runnable, runnable thread [sic] it then becomes the tail of the thread list for its new priority. ... For this policy, valid priorities shall be within the range returned by the function sched_get_priority_max() and sched_get_priority_min() when SCHED_FIFO is provided as the parameter. So it seems clear that the same range of priorities shall apply to individual threads as well as to processes. (SCHED_RR is similar in these respects.) 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-current" in the body of the message From owner-freebsd-current Sat Oct 14 13:28:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.houston.rr.com (sm1.texas.rr.com [24.93.35.54]) by hub.freebsd.org (Postfix) with ESMTP id 3901537B66C for ; Sat, 14 Oct 2000 13:28:43 -0700 (PDT) Received: from bloop.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sat, 14 Oct 2000 15:30:35 -0500 Received: from bloop.craftncomp.com (localhost.craftncomp.com [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e9EKRqG00714 for ; Sat, 14 Oct 2000 15:27:53 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200010142027.e9EKRqG00714@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: cvs-cur snapshots have stopped again. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Oct 2000 15:27:52 -0500 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could someone please restart them? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 13:48:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id C33BA37B66C for ; Sat, 14 Oct 2000 13:48:10 -0700 (PDT) Received: (qmail 6056 invoked by uid 0); 14 Oct 2000 20:48:09 -0000 Received: from p3ee21601.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.1) by mail.gmx.net with SMTP; 14 Oct 2000 20:48:09 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id WAA30073 for freebsd-current@FreeBSD.ORG; Sat, 14 Oct 2000 22:32:11 +0200 Date: Sat, 14 Oct 2000 22:32:11 +0200 From: Gerhard Sittig To: FreeBSD Current Subject: Re: removing global from tree Message-ID: <20001014223211.T25237@speedy.gsinet> Mail-Followup-To: FreeBSD Current References: <20001014155710.P25237@speedy.gsinet> <200010141816.LAA14274@john.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200010141816.LAA14274@john.baldwin.cx>; from jhb@FreeBSD.ORG on Sat, Oct 14, 2000 at 11:16:32AM -0700 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 14, 2000 at 11:16 -0700, John Baldwin wrote: > > On 14-Oct-00 Gerhard Sittig wrote: > > > > Up to now I always thought "the Attic" is something CVS > > itself takes care of when "cvs rm"ing files. What's that > > special thing needing manual intervention or special > > attention you've been talking about lately? Is it for > > performance reasons or for the warm fuzzy feelings of having > > "not too rotten a repo"? > > It is where CVS puts files when you cvs rm them. You just have > to do the actual cvs rm/cvs ci. David was cautious because if > he had to back the change out, he didn't want to have to try to > cvs add all of the files back in. Isn't it true that all the "log", "diff", "up -r" and such commands still work in the expected way? That's the reason for having "the Attic", I thought. Not to remove the repo file when the working file expires, but to keep the history and to restore any previous revision thereof when requested. Backing out an rm'ed file should be as difficult as doing the sequence I just tested to make sure: F=toberemoved.txt touch $F cvs add $F cvs ci -m "touched only" # creation time (birth, still a lot to learn) $EDITOR $F cvs ci -m "filled with real content" # that's when it's needed and existent rm $F cvs rm $F cvs ci -m "removed the file" # that's when it died # time passes, nobody misses the gone file, but then ... F=toberemoved.txt # the name is misleading now :) cvs log $F REV=1.2 # the one before removal cvs up -p -r$REV $F > $F cvs add $F cvs ci -m "revived file $F" # and everything could be like before ... The "cvs log $F" snippet even gives hope for the repo according to "there could be too much bloat". Have a look at the changed lines count, obviously only state changes: ----------------------------------------------------------------- revision 1.4 date: 2000/10/14 20:10:15; author: sittig; state: Exp; lines: +0 -0 revived it ---------------------------- revision 1.3 date: 2000/10/14 20:08:33; author: sittig; state: dead; lines: +0 -0 removed it ---------------------------- revision 1.2 date: 2000/10/14 20:08:00; author: sittig; state: Exp; lines: +49 -0 filled with rc.conf ---------------------------- revision 1.1 date: 2000/10/14 20:07:24; author: sittig; state: Exp; touched ----------------------------------------------------------------- I understand that this thread is OT here. But I feel that David wants to know this, too. And maybe others. So I would like to renew my question "Why does anyone feel the need to care about cvs' internals if not for knowing better?". This must be some very special requirement why anyone feels like fiddling manually with it. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 13:54:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 7477C37B66D for ; Sat, 14 Oct 2000 13:54:45 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9EKsdA53343 for ; Sat, 14 Oct 2000 13:54:40 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: current@freebsd.org Subject: Our kernel just got too big again. :) Date: Sat, 14 Oct 2000 13:54:39 -0700 Message-ID: <53339.971556879@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We've blown out the kern.flp image. Time for me to chop something out again, unless there are any other suggestions. :| - Jordan ------- Forwarded Message Return-Path: root@usw2.freebsd.org Delivery-Date: Sat Oct 14 06:50:52 2000 Return-Path: Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9EDopA52343 for ; Sat, 14 Oct 2000 06:50:52 -0700 (PDT) (envelope-from root@usw2.freebsd.org) Received: from hub.freebsd.org (hub.FreeBSD.org [216.136.204.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id C733C6E2504 for ; Sat, 14 Oct 2000 06:50:55 -0700 (PDT) Received: by hub.freebsd.org (Postfix) id B4E3237B66C; Sat, 14 Oct 2000 06:50:55 -0700 (PDT) Delivered-To: jkh@freebsd.org Received: from usw2.freebsd.org (usw2.freebsd.org [209.180.6.226]) by hub.freebsd.org (Postfix) with ESMTP id 6B36537B502 for ; Sat, 14 Oct 2000 06:50:55 -0700 (PDT) Received: (from root@localhost) by usw2.freebsd.org (8.11.1/8.11.0) id e9EDosg03413 for build-reports@freebsd.org; Sat, 14 Oct 2000 08:50:54 -0500 (CDT) (envelope-from root) Date: Sat, 14 Oct 2000 08:50:54 -0500 (CDT) From: USW2 Root Message-Id: <200010141350.e9EDosg03413@usw2.freebsd.org> To: build-reports@freebsd.org Subject: -current build report for Sat Oct 14 02:07:34 CDT 2000 Doing nightly build attempt for 5.0-20001014-CURRENT at Sat Oct 14 02:07:34 CDT 2000 Updating source tree... Making release... Release build of 5.0-20001014-CURRENT was an abject failure. cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/atkbd_isa.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/atkbdc_isa.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/fd.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/ppc.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/psm.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/sio.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/syscons_isa.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/vga_isa.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../kern/subr_diskmbr.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../libkern/divdi3.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../libkern/moddi3.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../libkern/qdivrem.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../libkern/udivdi3.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../libkern/umoddi3.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 setdef0.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vnode_if.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 param.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 hints.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 config.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 setdef1.c touch hack.c cc -elf -shared -nostdlib hack.c -o hack.So rm -f hack.c sh ../../conf/newvers.sh BOOTMFS cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking BOOTMFS text data bss dec hex filename 2573747 199288 147896 2920931 2c91e3 BOOTMFS install -c -m 555 -o root -g wheel -fschg BOOTMFS /R/stage/kernels mv /R/stage/kernels/BOOTMFS /R/stage/image.kern/kernel Setting up /boot directory for kern floppy /R/stage/image.kern/kernel: 54.8% -- replaced with /R/stage/image.kern/kernel.gz sh -e /usr/src/release/scripts/doFS.sh /R/stage/floppies/kern.flp /R/stage /mnt 1440 /R/stage/image.kern 80000 fd1440 disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 6. Warning: 1216 sector(s) in last cylinder unallocated /dev/rvnn0c: 2880 sectors in 1 cylinders of 1 tracks, 4096 sectors 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32 cpio: write error: No space left on device *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 14: 0:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D744D37B502 for ; Sat, 14 Oct 2000 14:00:23 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA07807; Sat, 14 Oct 2000 14:00:15 -0700 Date: Sat, 14 Oct 2000 13:57:07 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jordan Hubbard Cc: current@FreeBSD.ORG Subject: Re: Our kernel just got too big again. :) In-Reply-To: <53339.971556879@winston.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had asked for a 3rd floppy earlier that we could put f/w images and other drivers on. Now that we have a mostly loadable system, it strikes me that this would be an excellent time to trim down the GENERIC to the common denominator per-platform and then have compressed driver images available on a 3rd floppy if people need them. > We've blown out the kern.flp image. Time for me to chop something > out again, unless there are any other suggestions. :| > > - Jordan > ------- Forwarded Message > > Return-Path: root@usw2.freebsd.org > Delivery-Date: Sat Oct 14 06:50:52 2000 > Return-Path: > Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) > by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9EDopA52343 > for ; Sat, 14 Oct 2000 06:50:52 -0700 (PDT) > (envelope-from root@usw2.freebsd.org) > Received: from hub.freebsd.org (hub.FreeBSD.org [216.136.204.18]) > by mx1.FreeBSD.org (Postfix) with ESMTP id C733C6E2504 > for ; Sat, 14 Oct 2000 06:50:55 -0700 (PDT) > Received: by hub.freebsd.org (Postfix) > id B4E3237B66C; Sat, 14 Oct 2000 06:50:55 -0700 (PDT) > Delivered-To: jkh@freebsd.org > Received: from usw2.freebsd.org (usw2.freebsd.org [209.180.6.226]) > by hub.freebsd.org (Postfix) with ESMTP id 6B36537B502 > for ; Sat, 14 Oct 2000 06:50:55 -0700 (PDT) > Received: (from root@localhost) > by usw2.freebsd.org (8.11.1/8.11.0) id e9EDosg03413 > for build-reports@freebsd.org; Sat, 14 Oct 2000 08:50:54 -0500 (CDT) > (envelope-from root) > Date: Sat, 14 Oct 2000 08:50:54 -0500 (CDT) > From: USW2 Root > Message-Id: <200010141350.e9EDosg03413@usw2.freebsd.org> > To: build-reports@freebsd.org > Subject: -current build report for Sat Oct 14 02:07:34 CDT 2000 > > Doing nightly build attempt for 5.0-20001014-CURRENT at Sat Oct 14 02:07:34 CDT 2000 > Updating source tree... > Making release... > Release build of 5.0-20001014-CURRENT was an abject failure. > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/atkbd_isa.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/atkbdc_isa.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/fd.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/ppc.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/psm.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/sio.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/syscons_isa.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/vga_isa.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../kern/subr_diskmbr.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../libkern/divdi3.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../libkern/moddi3.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../libkern/qdivrem.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../libkern/udivdi3.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../libkern/umoddi3.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 setdef0.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vnode_if.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 param.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 hints.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 config.c > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 setdef1.c > touch hack.c > cc -elf -shared -nostdlib hack.c -o hack.So > rm -f hack.c > sh ../../conf/newvers.sh BOOTMFS > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c > linking BOOTMFS > text data bss dec hex filename > 2573747 199288 147896 2920931 2c91e3 BOOTMFS > install -c -m 555 -o root -g wheel -fschg BOOTMFS /R/stage/kernels > mv /R/stage/kernels/BOOTMFS /R/stage/image.kern/kernel > Setting up /boot directory for kern floppy > /R/stage/image.kern/kernel: 54.8% -- replaced with /R/stage/image.kern/kernel.gz > sh -e /usr/src/release/scripts/doFS.sh /R/stage/floppies/kern.flp /R/stage /mnt 1440 /R/stage/image.kern 80000 fd1440 > disklabel: ioctl DIOCWLABEL: Operation not supported by device > Warning: Block size restricts cylinders per group to 6. > Warning: 1216 sector(s) in last cylinder unallocated > /dev/rvnn0c: 2880 sectors in 1 cylinders of 1 tracks, 4096 sectors > 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 32 i/g) > super-block backups (for fsck -b #) at: > 32 > cpio: write error: No space left on device > *** Error code 1 > > Stop in /usr/src/release. > *** Error code 1 > > Stop in /usr/src/release. > *** Error code 1 > > Stop in /usr/src/release. > > ------- End of Forwarded Message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 14: 8:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 22DAF37B502 for ; Sat, 14 Oct 2000 14:08:38 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9EL8VA53422; Sat, 14 Oct 2000 14:08:31 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: Our kernel just got too big again. :) In-Reply-To: Message from Matthew Jacob of "Sat, 14 Oct 2000 13:57:07 PDT." Date: Sat, 14 Oct 2000 14:08:30 -0700 Message-ID: <53418.971557710@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I had asked for a 3rd floppy earlier that we could put f/w images and other That sounds nice in theory, but somebody needs to write the code which deals with floppy switching and module loading before this is anything but yet another request. How's your forth? :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 14:15:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 0D88837B503 for ; Sat, 14 Oct 2000 14:15:29 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA24596; Sat, 14 Oct 2000 14:15:26 -0700 (PDT) (envelope-from obrien) Date: Sat, 14 Oct 2000 14:15:26 -0700 From: "David O'Brien" To: Jordan Hubbard Cc: current@freebsd.org Subject: Re: Our kernel just got too big again. :) Message-ID: <20001014141526.A24566@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <53339.971556879@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <53339.971556879@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Sat, Oct 14, 2000 at 01:54:39PM -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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 14, 2000 at 01:54:39PM -0700, Jordan Hubbard wrote: > We've blown out the kern.flp image. Time for me to chop something > out again, unless there are any other suggestions. :| Things the Alpha has already diked out: ncr SYS* (not just SYSVMSG) lpt \ ppi / should not be needed for PLIP installs vpo (should it get turned on again) ugen uhid ulpt urio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 14:20:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 88F3B37B66F for ; Sat, 14 Oct 2000 14:20:08 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA07873; Sat, 14 Oct 2000 14:20:06 -0700 Date: Sat, 14 Oct 2000 14:16:59 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jordan Hubbard Cc: current@FreeBSD.ORG Subject: Re: Our kernel just got too big again. :) In-Reply-To: <53418.971557710@winston.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I had asked for a 3rd floppy earlier that we could put f/w images and other > > That sounds nice in theory, but somebody needs to write the code which > deals with floppy switching and module loading before this is anything > but yet another request. How's your forth? :) Hmm?... my forth is poor, but I don't believe that's the issue. If I understand how the floppies currently work is that it's just like our normal boot loader- we start coming up. If you want to load other drivers or modules (like ispfw), you hit the 'other than Enter' to stop the loading progress, switch floppies and load ispfw, davicom ethernet, a splash screen with jordan's face, whatever...then you type 'boot'- then the normal mfsroot floppy handoff works. The loader for i386 uses bios services to read a DOS filesystem on a floppy or the C , D, E and so on drive, right? This wasn't 'just another request'- although you hearing it from me might make you think so. You asked "what should we do?". I responded with something which I believe might 'just work' if you make 3rd floppy. I'll take a couple of minutes to go try it if I can find what I did with my 4.1 floppies unless you're sure this doesn't work. If you're email to -current was "only answers with patches against -current will be heard", you really should have said so. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 14:40: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 4AEB437B503 for ; Sat, 14 Oct 2000 14:40:05 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.1/8.11.1) id e9ELjeH15907; Sat, 14 Oct 2000 14:45:40 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200010142145.e9ELjeH15907@troutmask.apl.washington.edu> Subject: Re: removing global from tree In-Reply-To: <20001014223211.T25237@speedy.gsinet> from Gerhard Sittig at "Oct 14, 2000 10:32:11 pm" To: Gerhard Sittig Date: Sat, 14 Oct 2000 14:45:40 -0700 (PDT) Cc: FreeBSD Current 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gerhard Sittig wrote: > On Sat, Oct 14, 2000 at 11:16 -0700, John Baldwin wrote: > > > > On 14-Oct-00 Gerhard Sittig wrote: > > > > > > Up to now I always thought "the Attic" is something CVS > > > itself takes care of when "cvs rm"ing files. What's that > > > special thing needing manual intervention or special > > > attention you've been talking about lately? Is it for > > > performance reasons or for the warm fuzzy feelings of having > > > "not too rotten a repo"? > > > > It is where CVS puts files when you cvs rm them. You just have > > to do the actual cvs rm/cvs ci. David was cautious because if > > he had to back the change out, he didn't want to have to try to > > cvs add all of the files back in. > > Isn't it true that all the "log", "diff", "up -r" and such > commands still work in the expected way? That's the reason for > having "the Attic", I thought. Not to remove the repo file when > the working file expires, but to keep the history and to restore > any previous revision thereof when requested. Backing out an > rm'ed file should be as difficult as doing the sequence I just > tested to make sure: > If I understands cvs docs, the problem isn't with individual files. Cvs doesn't handle the removal and restoration of directories very well. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 15:56:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 1FA5837B502 for ; Sat, 14 Oct 2000 15:56:27 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA25210; Sat, 14 Oct 2000 15:56:23 -0700 (PDT) (envelope-from obrien) Date: Sat, 14 Oct 2000 15:56:23 -0700 From: "David O'Brien" To: Jordan Hubbard Cc: current@freebsd.org Subject: Re: Our kernel just got too big again. :) Message-ID: <20001014155623.D24566@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <53339.971556879@winston.osd.bsdi.com> <20001014141526.A24566@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: <20001014141526.A24566@dragon.nuxi.com>; from obrien@freebsd.org on Sat, Oct 14, 2000 at 02:15:26PM -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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Oct 14, 2000 at 01:54:39PM -0700, Jordan Hubbard wrote: > We've blown out the kern.flp image. Time for me to chop something > out again, unless there are any other suggestions. :| Mind if I commit this patch? Index: dokern.sh =================================================================== RCS file: /home/ncvs/src/release/scripts/dokern.sh,v retrieving revision 1.35 diff -u -r1.35 dokern.sh --- dokern.sh 2000/09/29 03:24:03 1.35 +++ dokern.sh 2000/10/14 22:55:45 @@ -72,7 +72,15 @@ -e '/SOFTUPDATES/d' \ -e '/MFS/d' \ -e '/NFS_ROOT/d' \ + -e '/ncr/d' \ -e '/atapist/d' \ + -e '/lpt/d' \ + -e '/ppi/d' \ + -e '/vpo/d' \ + -e '/ugen/d' \ + -e '/uhid/d' \ + -e '/ulpt/d' \ + -e '/urio/d' \ -e '/maxusers/d' \ -e 's/ident.*GENERIC/ident BOOTMFS/g' @@ -115,6 +123,7 @@ -e '/ulpt/d' \ -e '/umass/d' \ -e '/ums/d' \ + -e '/urio/d' \ -e '/aue/d' \ -e '/cue/d' \ -e '/kue/d' \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 16: 7:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 1B03137B66D for ; Sat, 14 Oct 2000 16:07:33 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id QAA25319; Sat, 14 Oct 2000 16:07:30 -0700 (PDT) (envelope-from obrien) Date: Sat, 14 Oct 2000 16:07:29 -0700 From: "David O'Brien" To: Gerhard Sittig Cc: FreeBSD Current Subject: Re: removing global from tree Message-ID: <20001014160729.A25235@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20001014155710.P25237@speedy.gsinet> <200010141816.LAA14274@john.baldwin.cx> <20001014223211.T25237@speedy.gsinet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001014223211.T25237@speedy.gsinet>; from Gerhard.Sittig@gmx.net on Sat, Oct 14, 2000 at 10:32:11PM +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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 14, 2000 at 10:32:11PM +0200, Gerhard Sittig wrote: > Backing out an rm'ed file should be as difficult as doing the sequence > I just tested to make sure: > > F=toberemoved.txt Coming up with the "F" list can be more than just ``ls -R /home/ncvs/src/contrib/global'' as older versions of global might have had files that weren't part of the the last version. Thus I'd have had to keep the commit message (or go find it in the archive, which would be some effort), to get the real list of files to revive. > F=toberemoved.txt # the name is misleading now :) > cvs log $F > REV=1.2 # the one before removal > cvs up -p -r$REV $F > $F > cvs add $F > cvs ci -m "revived file $F" > # and everything could be like before ... As you've just shown, this can be a real PITA. > But I feel that David wants to know this, too. Huh? Do what?? I fully understand how to remove, add, and revive files in the repo. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 16:50:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 71F9B37B671 for ; Sat, 14 Oct 2000 16:50:09 -0700 (PDT) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id QAA85125; Sat, 14 Oct 2000 16:54:59 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id QAA14626; Sat, 14 Oct 2000 16:52:47 -0700 (PDT) (envelope-from john) Message-Id: <200010142352.QAA14626@john.baldwin.cx> 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: <20001014223211.T25237@speedy.gsinet> Date: Sat, 14 Oct 2000 16:52:46 -0700 (PDT) From: John Baldwin To: Gerhard Sittig Subject: Re: removing global from tree Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Oct-00 Gerhard Sittig wrote: > On Sat, Oct 14, 2000 at 11:16 -0700, John Baldwin wrote: >> >> On 14-Oct-00 Gerhard Sittig wrote: >> > >> > Up to now I always thought "the Attic" is something CVS >> > itself takes care of when "cvs rm"ing files. What's that >> > special thing needing manual intervention or special >> > attention you've been talking about lately? Is it for >> > performance reasons or for the warm fuzzy feelings of having >> > "not too rotten a repo"? >> >> It is where CVS puts files when you cvs rm them. You just have >> to do the actual cvs rm/cvs ci. David was cautious because if >> he had to back the change out, he didn't want to have to try to >> cvs add all of the files back in. > > Isn't it true that all the "log", "diff", "up -r" and such > commands still work in the expected way? That's the reason for > having "the Attic", I thought. Not to remove the repo file when > the working file expires, but to keep the history and to restore > any previous revision thereof when requested. Backing out an > rm'ed file should be as difficult as doing the sequence I just > tested to make sure: Yes. The trick is getting the list of files you just deleted, esp. when you are taking out several directories of stuff. David's point was to not make the task overly difficult, but instead to simply do teh Makefile change first, to make the change easier to revert if necessary, as it would then only require one edit and commit, rather than having to generate a list of files to re-add and commit as well. Geez, he knows how CVS works, he was just trying to save some time. -- 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-current" in the body of the message From owner-freebsd-current Sat Oct 14 17:12:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 7EB1C37B66E for ; Sat, 14 Oct 2000 17:12:41 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9F0CXA53857; Sat, 14 Oct 2000 17:12:34 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: Our kernel just got too big again. :) In-Reply-To: Message from Matthew Jacob of "Sat, 14 Oct 2000 14:16:59 PDT." Date: Sat, 14 Oct 2000 17:12:33 -0700 Message-ID: <53853.971568753@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm?... my forth is poor, but I don't believe that's the issue. If I > understand how the floppies currently work is that it's just like our normal > boot loader- we start coming up. If you want to load other drivers or modules > (like ispfw), you hit the 'other than Enter' to stop the loading progress, > switch floppies and load ispfw, davicom ethernet, a splash screen with > jordan's face, whatever...then you type 'boot'- then the normal mfsroot flopp The problem with such an approach is that it's not very user-friendly to first-time installers who have no idea how to drive the loader. Let's not forget the linux installation floppy saga and all the confusion it's caused people just in trying to figure out which floppies to use. That would be where the forth hackery comes in - an additional set of menu options which make it a no-brainer to insert the kernel module floppy. > you're sure this doesn't work. If you're email to -current was "only answers > with patches against -current will be heard", you really should have said so. No, that wasn't the point of my email. My email was originally intended to solicit suggestions about options to remove from the kernel so that the *existing* mechanism would go back to working again. Adding a 3rd floppy to the mix is an option which has occurred to all of us at one time or another and even been a topic for fierce debate in the FreeBSD mailing lists. I would have preferred not to go there in this thread. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 17:16:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DE8B437B66D for ; Sat, 14 Oct 2000 17:16:16 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA08136; Sat, 14 Oct 2000 17:16:14 -0700 Date: Sat, 14 Oct 2000 17:13:07 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jordan Hubbard Cc: current@FreeBSD.ORG Subject: Re: Our kernel just got too big again. :) In-Reply-To: <53853.971568753@winston.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hmm?... my forth is poor, but I don't believe that's the issue. If I > > understand how the floppies currently work is that it's just like our normal > > boot loader- we start coming up. If you want to load other drivers or modules > > (like ispfw), you hit the 'other than Enter' to stop the loading progress, > > switch floppies and load ispfw, davicom ethernet, a splash screen with > > jordan's face, whatever...then you type 'boot'- then the normal mfsroot flopp > > The problem with such an approach is that it's not very user-friendly > to first-time installers who have no idea how to drive the loader. > Let's not forget the linux installation floppy saga and all the > confusion it's caused people just in trying to figure out which > floppies to use. That would be where the forth hackery comes in - an > additional set of menu options which make it a no-brainer to insert the > kernel module floppy. Okay. It's your thuktun, as Niven would write.... > > > you're sure this doesn't work. If you're email to -current was "only answers > > with patches against -current will be heard", you really should have said so. > > No, that wasn't the point of my email. My email was originally > intended to solicit suggestions about options to remove from the > kernel so that the *existing* mechanism would go back to working > again. Adding a 3rd floppy to the mix is an option which has occurred > to all of us at one time or another and even been a topic for fierce > debate in the FreeBSD mailing lists. I would have preferred not to go > there in this thread. :) Okay. I have no suggestions as to what to remove then. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 17:30:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id BCE0C37B66C for ; Sat, 14 Oct 2000 17:29:10 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e9F0T9n38633; Sat, 14 Oct 2000 18:29:09 -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.9.3/8.8.3) with ESMTP id SAA89576; Sat, 14 Oct 2000 18:27:53 -0600 (MDT) Message-Id: <200010150027.SAA89576@harmony.village.org> To: alex@big.endian.de (Alexander Langer) Subject: Re: pcmcia and ed Cc: Wesley Morgan , current@FreeBSD.ORG In-reply-to: Your message of "Sat, 14 Oct 2000 09:29:50 +0200." <20001014092950.B7171@cichlids.cichlids.com> References: <20001014092950.B7171@cichlids.cichlids.com> <200010071803.MAA01359@harmony.village.org> Date: Sat, 14 Oct 2000 18:27:53 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001014092950.B7171@cichlids.cichlids.com> Alexander Langer writes: : Thus spake Warner Losh (imp@village.org): : : > The module name should be if_ed. I'll go fix it. : : Did you do this already? : : And if so, where? No. I haven't. I just spend a fair amount of time wonking on a current -current kernel to get any ed card to work. looks like interrupts just aren't happening at all :-(. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 17:35:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4243837B670; Sat, 14 Oct 2000 17:35:38 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA08180; Sat, 14 Oct 2000 17:35:38 -0700 Date: Sat, 14 Oct 2000 17:32:30 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: Jordan Hubbard , current@FreeBSD.ORG Subject: Re: Our kernel just got too big again. :) In-Reply-To: <200010150034.e9F0Ysf00965@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The problem with such an approach is that it's not very user-friendly > > to first-time installers who have no idea how to drive the loader. > > Most of the relevant modules can actually be tried by sysinstall. In the > CD case we can just put them on the CDROM. I'd be inclined to look for > somewhere that you can fit ~110k and put nfs.ko.gz there. 8) I was thinking about making sure that drivers that would get you to your install media would be what you'd load- nothing else. This would include network drivers... > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 19:33:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (termroom.bsdcon.org [206.55.247.2]) by hub.freebsd.org (Postfix) with ESMTP id 8A36637B66F for ; Sat, 14 Oct 2000 19:33:39 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9F0Ysf00965; Sat, 14 Oct 2000 17:34:54 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010150034.e9F0Ysf00965@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jordan Hubbard Cc: mjacob@feral.com, current@freebsd.org Subject: Re: Our kernel just got too big again. :) In-reply-to: Your message of "Sat, 14 Oct 2000 17:12:33 PDT." <53853.971568753@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Oct 2000 17:34:54 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem with such an approach is that it's not very user-friendly > to first-time installers who have no idea how to drive the loader. Most of the relevant modules can actually be tried by sysinstall. In the CD case we can just put them on the CDROM. I'd be inclined to look for somewhere that you can fit ~110k and put nfs.ko.gz there. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 19:33:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (termroom.bsdcon.org [206.55.247.2]) by hub.freebsd.org (Postfix) with ESMTP id 4ADEB37B66E for ; Sat, 14 Oct 2000 19:33:39 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9F0hwf01063; Sat, 14 Oct 2000 17:43:58 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010150043.e9F0hwf01063@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: current@freebsd.org Subject: Re: Our kernel just got too big again. :) In-reply-to: Your message of "Sat, 14 Oct 2000 17:32:30 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Oct 2000 17:43:58 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > The problem with such an approach is that it's not very user-friendly > > > to first-time installers who have no idea how to drive the loader. > > > > Most of the relevant modules can actually be tried by sysinstall. In the > > CD case we can just put them on the CDROM. I'd be inclined to look for > > somewhere that you can fit ~110k and put nfs.ko.gz there. 8) > > I was thinking about making sure that drivers that would get you to your > install media would be what you'd load- nothing else. This would include > network drivers... That'd work; we could offload a lot of storage drivers (CAM, RAID, etc are all loadable...) -- ... 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-current" in the body of the message From owner-freebsd-current Sat Oct 14 19:59:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id E8FC537B66D for ; Sat, 14 Oct 2000 19:59:17 -0700 (PDT) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.11.1/8.11.0) id e9F2waX38313; Sun, 15 Oct 2000 09:58:36 +0700 (NOVST) (envelope-from nnd) Date: Sun, 15 Oct 2000 09:58:36 +0700 (NOVST) Message-Id: <200010150258.e9F2waX38313@wint.itfs.nsk.su> From: Nickolay Dudorov To: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/include endian.h In-Reply-To: <200010150045.RAA70717@freefall.freebsd.org> X-Newsgroups: itfs.freebsd.cvs.all User-Agent: tin/1.5.6-20000803 ("Dust") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200010150045.RAA70717@freefall.freebsd.org> you wrote: > brian 2000/10/14 17:45:19 PDT > > Modified files: > sys/i386/include endian.h > Log: > Redefine __word_swap_long, __byte_swap_long and __byte_swap_word > as inline functions, renaming them to __uint16_swap_uint32, > __uint8_swap_uint32 and __uint8_swap_uint16. > > Doing it properly suggested by: msmith > Reviewed by: msmith > > Revision Changes Path > 1.19 +33 -36 src/sys/i386/include/endian.h After this commit 'make buildworld' breaks in 'src/lib/msun/src'. I can 'make all' in the 'src/lib/msun' directory after the next patch: Index: math_private.h =================================================================== RCS file: /scratch/CVS/src/lib/msun/src/math_private.h,v retrieving revision 1.6 diff -b -u -r1.6 math_private.h --- math_private.h 1999/08/28 00:06:43 1.6 +++ math_private.h 2000/10/15 02:52:59 @@ -17,8 +17,8 @@ #ifndef _MATH_PRIVATE_H_ #define _MATH_PRIVATE_H_ -#include #include +#include /* The original fdlibm code used statements like: n0 = ((*(int*)&one)>>29)^1; * index of high word * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 20:14:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from afs.itc.keio.ac.jp (afs.itc.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (Postfix) with SMTP id 33EB737B502 for ; Sat, 14 Oct 2000 20:14:25 -0700 (PDT) Received: (qmail 9526 invoked from network); 15 Oct 2000 03:14:23 -0000 Received: from pppb60.yk.rim.or.jp (HELO localhost.FromTo.Cc) (202.247.186.160) by afs.itc.keio.ac.jp with SMTP; 15 Oct 2000 03:14:23 -0000 Date: Sun, 15 Oct 2000 12:14:19 +0900 Message-ID: <86aec6iyno.wl@ringo.FromTo.Cc> From: Tatsumi Hosokawa To: mjacob@feral.com Cc: jkh@winston.osd.bsdi.com, current@FreeBSD.ORG Subject: Re: Our kernel just got too big again. :) In-Reply-To: In your message of "Sat, 14 Oct 2000 13:57:07 -0700 (PDT)" References: <53339.971556879@winston.osd.bsdi.com> User-Agent: Wanderlust/1.1.0 (Overjoyed) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 9) (Canyonlands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Sat, 14 Oct 2000 13:57:07 -0700 (PDT), Matthew Jacob wrote: > > I had asked for a 3rd floppy earlier that we could put f/w images and other > drivers on. Now that we have a mostly loadable system, it strikes me that this > would be an excellent time to trim down the GENERIC to the common denominator > per-platform and then have compressed driver images available on a 3rd floppy > if people need them. It's a nice idea, but this means that boot.flp can exceed 2.88MB limit. As far as I know, the maximum size of boot image of El-Torito bootable CD-ROM is 2.88MB. When I install from CD-ROM, I have to enable ATAPI or SCSI drivers first, and then load Network dirvers and so on. When I install from the net, I have to enable Ethernet, PLIP or PPP drivers first, and then load ATAPI or SCSI drivers and so on. Currently, sysinstall supports two types of install media: local media and remote media. Boot.flp should be capable of loading drivers from the install media. Local media installation: Disk1-1: kernel, atapi + scsi drivers Disk2: sysinstall and utilities Disk3: driver disk Remote media installation: Disk1-2: kernel, network drivers Disk2: sysinstall and utilities Disk3: driver disk I think that disk 2 and 3 can be shared by them. Sysinstall have to ask user about installation media first, and then get compressed *.ko modules from the installation media. P.S.: Japanese/Korean boot.flp for 4.1.1 will be available in a few days (test version is available at http://people.freebsd.org/~hosokawa/boot-ja/), and I believe that it can be ported to -current easily, but it needs pty support in the Disk1 currently.... -- --------------------------- Tatsumi Hosokawa hosokawa@itc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 21: 0:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id D32E237B66F for ; Sat, 14 Oct 2000 21:00:17 -0700 (PDT) Received: (qmail 59653 invoked by uid 100); 15 Oct 2000 04:00:16 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14825.11216.657473.62158@guru.mired.org> Date: Sat, 14 Oct 2000 23:00:16 -0500 (CDT) To: current@freebsd.org Subject: system lockups in -current - during boot. X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm getting hard lockups booting a -current kernel supped about 6 hours ago. If I try to boot multiuser, I get a message about the ethernet interface being configured, and then nothing. If I boot single user, it comes up fine, and I can configure the NIC. The system then locks up maybe 10 seconds later, doing nothing but tapping return every so often. I don't get enough response to start a debugger in either case. The best data I can contribute is a dmesg from the same hardware booting -stable. Suggestions? Pointers? Fixes? Oct 14 23:27:24 eve /kernel: AMD Features=0x80000800 Oct 14 23:27:24 eve /kernel: real memory = 67043328 (65472K bytes) Oct 14 23:27:24 eve /kernel: avail memory = 62480384 (61016K bytes) Oct 14 23:27:24 eve /kernel: Preloaded elf kernel "kernel" at 0xc02d3000. Oct 14 23:27:24 eve /kernel: K6-family MTRR support enabled (2 registers) Oct 14 23:27:24 eve /kernel: npx0: on motherboard Oct 14 23:27:24 eve /kernel: npx0: INT 16 interface Oct 14 23:27:24 eve /kernel: pcib0: on motherboard Oct 14 23:27:24 eve /kernel: pci0: on pcib0 Oct 14 23:27:24 eve /kernel: pcib2: at device 1.0 on pci0 Oct 14 23:27:24 eve /kernel: pci1: on pcib2 Oct 14 23:27:24 eve /kernel: pci1: at 0.0 irq 11 Oct 14 23:27:24 eve /kernel: isab0: at device 7.0 on pci0 Oct 14 23:27:24 eve /kernel: isa0: on isab0 Oct 14 23:27:24 eve /kernel: atapci0: port 0xe000-0xe00f at device 7.1 on pci0 Oct 14 23:27:24 eve /kernel: ata0: at 0x1f0 irq 14 on atapci0 Oct 14 23:27:24 eve /kernel: ata1: at 0x170 irq 15 on atapci0 Oct 14 23:27:24 eve /kernel: uhci0: port 0xe400-0xe41f irq 10 at device 7.2 on pci0 Oct 14 23:27:24 eve /kernel: usb0: on uhci0 Oct 14 23:27:24 eve /kernel: usb0: USB revision 1.0 Oct 14 23:27:24 eve /kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Oct 14 23:27:24 eve /kernel: uhub0: 2 ports with 2 removable, self powered Oct 14 23:27:24 eve /kernel: ugen0: Diamond Multimedia Systems, Inc. SupraExpress 56e USB V.90, rev 1.00/1.00, addr 2 Oct 14 23:27:24 eve /kernel: xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xe800-0xe87f mem 0xeb000000-0xeb00007f irq 5 at device 10.0 on pci0 Oct 14 23:27:24 eve /kernel: xl0: Ethernet address: 00:50:04:84:ac:f1 Oct 14 23:27:24 eve /kernel: miibus0: on xl0 Oct 14 23:27:24 eve /kernel: xlphy0: <3Com internal media interface> on miibus0 Oct 14 23:27:24 eve /kernel: xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Oct 14 23:27:24 eve /kernel: pci0: (vendor=0x1274, dev=0x5000) at 12.0 irq 5 Oct 14 23:27:24 eve /kernel: pcib1: on motherboard Oct 14 23:27:24 eve /kernel: pci2: on pcib1 Oct 14 23:27:24 eve /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Oct 14 23:27:24 eve /kernel: fdc0: FIFO enabled, 8 bytes threshold Oct 14 23:27:24 eve /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Oct 14 23:27:24 eve /kernel: atkbdc0: at port 0x60,0x64 on isa0 Oct 14 23:27:24 eve /kernel: atkbd0: flags 0x1 irq 1 on atkbdc0 Oct 14 23:27:24 eve /kernel: kbd0 at atkbd0 Oct 14 23:27:24 eve /kernel: psm0: irq 12 on atkbdc0 Oct 14 23:27:24 eve /kernel: psm0: model Generic PS/2 mouse, device ID 0 Oct 14 23:27:24 eve /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Oct 14 23:27:24 eve /kernel: sc0: at flags 0x100 on isa0 Oct 14 23:27:24 eve /kernel: sc0: VGA <16 virtual consoles, flags=0x300> Oct 14 23:27:24 eve /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Oct 14 23:27:24 eve /kernel: sio0: type 16550A Oct 14 23:27:24 eve /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Oct 14 23:27:24 eve /kernel: sio1: type 16550A Oct 14 23:27:24 eve /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Oct 14 23:27:24 eve /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode Oct 14 23:27:24 eve /kernel: ppc0: FIFO with 16/16/16 bytes threshold Oct 14 23:27:24 eve /kernel: lpt0: on ppbus0 Oct 14 23:27:24 eve /kernel: lpt0: Interrupt-driven port Oct 14 23:27:24 eve /kernel: ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable Oct 14 23:27:24 eve /kernel: ad0: 9765MB [19841/16/63] at ata0-master using UDMA33 Oct 14 23:27:24 eve /kernel: ata1-master: DMA limited to UDMA33, non-ATA66 compliant cable Oct 14 23:27:24 eve /kernel: ad2: 19541MB [39704/16/63] at ata1-master using UDMA33 Oct 14 23:27:24 eve /kernel: acd0: CDROM at ata1-slave using PIO4 Oct 14 23:27:24 eve /kernel: Mounting root from ufs:/dev/ad0s2a Oct 14 23:27:24 eve /kernel: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled Oct 14 18:27:33 eve login: ROOT LOGIN (root) ON ttyv0 Oct 14 18:28:13 eve su: mwm to root on /dev/ttyp0 Oct 14 21:25:13 eve /kernel: WARNING: R/W mount of /usr denied. Filesystem is not clean - run fsck Oct 14 21:34:22 eve shutdown: reboot by mwm: Oct 14 21:34:25 eve syslogd: exiting on signal 15 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 21: 3:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3]) by hub.freebsd.org (Postfix) with ESMTP id 4ED9D37B502 for ; Sat, 14 Oct 2000 21:03:13 -0700 (PDT) Received: (from bugs@localhost) by freebsd.netcom.com (8.8.8+Sun/8.8.8) id XAA02106 for freebsd-current@freebsd.org; Sat, 14 Oct 2000 23:03:15 -0500 (CDT) From: Mark Hittinger Message-Id: <200010150403.XAA02106@freebsd.netcom.com> Subject: today's -current xl0 wigs out To: freebsd-current@freebsd.org Date: Sat, 14 Oct 2000 23:03:15 -0500 (CDT) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Upon an 'ifconfig xl0' the kernel hangs. If I don't ifconfig xl0 I can still use pppd ok. pcib0: at pcibus 0 on motherboard pci0: on pcib0 pci0: at 7.3 pci0: at 10.0 irq 11 xl0: <3Com 3c905-TX Fast Etherlink XL> port 0x6400-0x643f irq 10 at device 12.0 on pci0 xl0: Ethernet address: 00:60:08:15:f9:49 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto FYI Later Mark Hittinger Earthlink bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 21:20:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id C9E9637B66D for ; Sat, 14 Oct 2000 21:20:41 -0700 (PDT) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id AAA00063; Sun, 15 Oct 2000 00:20:21 -0400 (EDT) Date: Sun, 15 Oct 2000 00:20:11 -0400 (EDT) From: Daniel Eischen To: current@freebsd.org Subject: Re: Recent thread changes In-Reply-To: <200010142000.e9EK0hn47439@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Oct 2000 jdp@polstra.com wrote: > In article , > Daniel Eischen wrote: > > On Sat, 14 Oct 2000 jdp@polstra.com wrote: > > > > > > I thought you could get that information with sched_get_priority_min() > > > and sched_get_priority_max(). Is that not the case? > > > > Not really. Those return the kernels POSIX priority range for > > processes. > > Hmm, that's not how I interpret the POSIX spec. Here are some > excerpts from section 13.2, "Scheduling Policies". That's in the > chapter which describes all of the sched_XXX() functions. > > This model discusses only processor scheduling for runnable > threads ... > > There is, conceptually, one thread list for each priority. Any > runnable thread may be on any thread list. Multiple scheduling > policies shall be provided. Each nonempty thread list is > ordered, contains a head as one end of its order, and a tail as > the other. The purpose of a scheduling policy is to define the > allowable operations on this set of lists. > > Each process shall be controlled by an associated scheduling > policy and priority. These parameters may be specified by > explicit application execution of the sched_setscheduler() or > sched_setparam() functions. > > Each thread shall be controlled by an associated scheduling > policy and priority. These parameters may be specified by > explicit application execution of the pthread_setschedparam() > function. So far I read this as saying the sched_XXX functions operate on processes, whereas the pthread_{set|get}schedparam functions operate on threads. > > And then in the discussion of the SCHED_FIFO scheduling policy in > section 13.2.1, it says: > > (4) When a running thread calls the sched_setparam() function, > the priority of the process specified in the function call is > modified to the priority specified by the param argument. > If the thread whose priority has been modified is a running > thread or is runnable, runnable thread [sic] it then becomes > the tail of the thread list for its new priority. This contradicts itself and is where I think it is unclear. Where does it state that the _threads_ priority is modified? It only says that the process priority is modified. When it goes on to say "If the thread whose priority has been modified...", it's assuming something that was never stated as a requirement. > (5) When a running thread calls the pthread_setschedparam() > function, the thread specified in the function call is > modified to the specified policy and the priority specified by > the param argument. The above is a clearly stated requirement. If they had meant for the threads priority to be changed by sched_setparam(), then it should have been stated just as it has been above (5). > (6) If a thread whose policy or priority has been modified is > a running thread or is runnable, runnable thread [sic] it then > becomes the tail of the thread list for its new priority. Unless it holds a priority protection or inheritence mutex, in which case it gets added to the head of the thread list for its new priority. This case is often forgotten (see 13.6.1.2). > ... > > For this policy, valid priorities shall be within the range > returned by the function sched_get_priority_max() and > sched_get_priority_min() when SCHED_FIFO is provided as the > parameter. > > So it seems clear that the same range of priorities shall apply to > individual threads as well as to processes. (SCHED_RR is similar in > these respects.) For SCHED_FIFO and SCHED_RR, we don't have a problem because both the threads library and kernel now agree that the range is 0..31. SCHED_OTHER is a problem because the threads library treats SCHED_OTHER as SCHED_RR with range 0..31. The kernel treats SCHED_OTHER traditionally with range -20..20. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 21:28:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3]) by hub.freebsd.org (Postfix) with ESMTP id 5678937B502 for ; Sat, 14 Oct 2000 21:28:49 -0700 (PDT) Received: (from nc0548@localhost) by freebsd.netcom.com (8.8.8+Sun/8.8.8) id XAA02237 for freebsd-current@freebsd.org; Sat, 14 Oct 2000 23:29:03 -0500 (CDT) From: Mark Hittinger Message-Id: <200010150429.XAA02237@freebsd.netcom.com> Subject: re: today's -current xl0 wigs out To: freebsd-current@freebsd.org Date: Sat, 14 Oct 2000 23:29:03 -0500 (CDT) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In if_xl.c at the very beginning of xl_attach() it looks like there is a leftover splimp(). Bill seems to have replaced all the others with a LOCK macro. Further down in xl_attach there is a LOCK macro so maybe we just have to remove that leftover splimp(). Trying that now. Later Mark Hittinger Earthlink bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 22: 0:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id D04B537B670 for ; Sat, 14 Oct 2000 22:00:39 -0700 (PDT) Received: (qmail 21113 invoked by uid 100); 15 Oct 2000 05:00:34 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14825.14833.995861.497795@guru.mired.org> Date: Sun, 15 Oct 2000 00:00:33 -0500 (CDT) To: Mark Hittinger Cc: freebsd-current@FreeBSD.ORG Subject: Re: today's -current xl0 wigs out In-Reply-To: <200010150403.XAA02106@freebsd.netcom.com> References: <200010150403.XAA02106@freebsd.netcom.com> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Hittinger writes: > Upon an 'ifconfig xl0' the kernel hangs. If I don't ifconfig xl0 I can > still use pppd ok. Well, you're not alone. I note that the same code works fine in my machine with an fxp. ; Sat, 14 Oct 2000 22:03:59 -0700 (PDT) Received: (from bugs@localhost) by freebsd.netcom.com (8.8.8+Sun/8.8.8) id AAA02436 for freebsd-current@freebsd.org; Sun, 15 Oct 2000 00:04:13 -0500 (CDT) From: Mark Hittinger Message-Id: <200010150504.AAA02436@freebsd.netcom.com> Subject: re: today's -current xl0 wigs out To: freebsd-current@freebsd.org Date: Sun, 15 Oct 2000 00:04:13 -0500 (CDT) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well getting rid of the leftover splimp() didn't clear up the problem. Maybe we need to move the mtx_init and XL_LOCK up to where the splimp() was. Later Mark Hittinger Earthlink bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 14 23:31:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from tigers.cableinet.net (tigers.cableinet.net [193.38.113.20]) by hub.freebsd.org (Postfix) with SMTP id 47E5837B670 for ; Sat, 14 Oct 2000 23:31:31 -0700 (PDT) Received: (qmail 31721 invoked from network); 15 Oct 2000 06:20:52 -0000 Received: from unknown (HELO gateway.openc.co.uk) (195.188.55.130) by tigers.cableinet.net with SMTP; 15 Oct 2000 06:20:52 -0000 Received: from LocalHost - 63.20.61.117 by gateway.openc.co.uk with Microsoft SMTPSVC(5.5.1774.114.11); Sun, 15 Oct 2000 07:32:28 +0100 From: nufyug@myrealbox.com Message-Id: To: RunningBanks@gocubs.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Subject: Find Out ANYTHING About ANYONE!!! Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7BIT Date: Sat, 14 Oct 2000 23:31:50 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG THIS NEW AMAZING SOFTWARE TOOL HELPS YOU FIND OUT ALMOST ANYTHING ABOUT ANYONE - CLICK ON URL BELOW TO VISIT OUR WEBSITE http://www.canadianwebs.com/hf/syurown/ ********************************************************** Find out almost EVERYTHING you ever wanted to know about: Your friends Your family Your enemies Your employees Yourself - Is Someone Using Your Identity? Even your boss! DID YOU KNOW you can search for ANYONE, ANYTIME, ANYWHERE, right on the Internet.. This mammoth COLLECTION of Internet investigative tools & research sites will provide you with NEARLY 400 GIGANTIC SEARCH RESOURCES to locate information on: People you trust Screen new tenants or roommates Housekeepers Current or past employment People you work with License plate number with name and address Unlisted phone numbers Long lost friends A new or old LOVE INTEREST You can even VERIFY your own CREDIT REPORTS so you can correct WRONG information These are only a few things you can do, There is no limit to the power of this information tool!! CLICK ON URL BELOW TO VISIT OUR WEBSITE http://www.canadianwebs.com/hf/syurown/ ****************************************************** To be removed from our mailing list, click below mailto:akroneques@mailohio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message