From owner-freebsd-stable Sun Oct 25 00:54:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15854 for freebsd-stable-outgoing; Sun, 25 Oct 1998 00:54:28 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15849 for ; Sun, 25 Oct 1998 00:54:23 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id JAA12592; Sun, 25 Oct 1998 09:53:20 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810250753.JAA12592@gratis.grondar.za> To: "Jordan K. Hubbard" cc: "Scot W. Hetzel" , "FreeBSD-Stable" , "Andrew Boothman" Subject: Re: CTM Release Generation - (Re: Stable and CTM) In-Reply-To: Your message of " Sat, 24 Oct 1998 23:00:13 MST." <10582.909295213@time.cdrom.com> References: <10582.909295213@time.cdrom.com> Date: Sun, 25 Oct 1998 09:53:19 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > The generation of the src-xR delta's are supposed > > to be generated manually after each release by either the CTM maintainer or > > the Release Engineer. > > Not either - I have nothing whatsoever to do with CTM generation. Only > the CTM maintainer does this. ...which is me. The name has changes. You want the most recent "Empty" file and all subsequent ones. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 25 00:58:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16173 for freebsd-stable-outgoing; Sun, 25 Oct 1998 00:58:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16165 for ; Sun, 25 Oct 1998 00:58:41 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id JAA12650; Sun, 25 Oct 1998 09:57:37 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810250757.JAA12650@gratis.grondar.za> To: Andrew Boothman cc: "Scot W. Hetzel" , "FreeBSD-Stable" Subject: Re: CTM Release Generation - (Re: Stable and CTM) In-Reply-To: Your message of " Sat, 24 Oct 1998 22:54:50 +0100." <3.0.5.32.19981024225450.007af190@ice.cream.org> References: <3.0.5.32.19981024225450.007af190@ice.cream.org> Date: Sun, 25 Oct 1998 09:57:36 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Boothman wrote: > At 14:29 24/10/98 -0500, Scot W. Hetzel wrote: > >The generation of the src-xR delta's are supposed > >to be generated manually after each release by either the CTM maintainer or > >the Release Engineer. > > So these deltas are only created at every release instead of every 100 > deltas like the xEmpty's? In theory. In practice we do not have the resources. (This can easily change). > Would it not be better to create an xR delta at the same > time as the xEmpty delta then you could upgrade to the -stable code easily > by downloading the deltas that then come afterwards as well? Disk space is a problem. > By only creating xR deltas during the release of another > version it means that you can only update from release to release and > nothing in between. True. Who pays for the disk to generate these? > >Could somebody please create these Release Deltas, so that this question > >never comes up on the list again. > > Whoops. Do I detect that this has come up on the list before? :-) Yup. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 25 01:15:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA20789 for freebsd-stable-outgoing; Sun, 25 Oct 1998 01:15:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20784 for ; Sun, 25 Oct 1998 01:15:01 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id BAA02486; Sun, 25 Oct 1998 01:13:59 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <3632EBD7.717C0B6F@gorean.org> Date: Sun, 25 Oct 1998 01:13:59 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE-1015 i386) X-Accept-Language: en MIME-Version: 1.0 To: Allen Smith CC: David Greenman , Randy Bush , Marc Gutschner , freebsd-stable@FreeBSD.ORG Subject: Re: Is 'xntpd' broken in -stable? References: <199810091927.MAA14061@implode.root.com> <9810241606.ZM2203@beatrice.rutgers.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Allen Smith wrote: > I've checked with Dave Mills on this issue, and there's an option (-x, > which is unfortunately not in the help files) in ntpd (as opposed to > xntpd, which is about as obsolete/nonsupported as FreeBSD-1.x) Posted this on another list...I disagree with your characterization as much as I'd like to see our version of xntpd updated. The xntpd branch is still maintained and updated, as recently as 4/27/98 for the most recent stable version, and August 10th for the most recent beta. The xntpd server supports version 3 of the protocol, ntpd is version 4. The two branches are relatively equivalent to our -Stable and -Current. At some point we should probably integrate ntp into -current, but the last time this topic came up (about 6 months ago) someone more knowledgeable than me was looking at both sets of sources and decided that ntp wasn't yet ready for prime time. For a long time I had hoped that someone would at least update to a more recent version of xntpd and then move that into the 2.2 branch, but that dream will die with 2.2.8. :-/ Our version of xntpd is prehistoric, and the vast numbers of bug fixes and algorithm improvements we're missing out on boggles the mind. And before anyone mentions it, I volunteered to make a port of the more recent version a while back and was told that it wouldn't be committed. If that has changed I'm still happy to do a port of the more recent version. Doug -- *** Chief Operations Officer, DALnet IRC network *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 25 04:24:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10567 for freebsd-stable-outgoing; Sun, 25 Oct 1998 04:24:41 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ibm.net. (slip166-72-224-27.pa.us.ibm.net [166.72.224.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10562 for ; Sun, 25 Oct 1998 04:24:38 -0800 (PST) (envelope-from placej@ibm.net) Received: (from placej@localhost) by ibm.net. (8.8.8/8.8.8) id IAA00257; Sun, 25 Oct 1998 08:24:23 -0500 (EST) (envelope-from placej) Message-ID: <19981025082423.A237@ka3tis.com> Date: Sun, 25 Oct 1998 08:24:23 -0500 From: "John C. Place" To: freebsd-stable@FreeBSD.ORG Subject: Re: kernel panic from quota? Reply-To: "John C. Place" Mail-Followup-To: freebsd-stable@freebsd.org References: <19981024033231.A6200@homer.louisville.edu> <19981024103119.16296@ka3tis.com> <19981024113253.B3102@homer.louisville.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981024113253.B3102@homer.louisville.edu>; from Keith Stevenson on Sat, Oct 24, 1998 at 11:32:53AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 24, 1998 at 11:32:53AM -0400, Keith Stevenson wrote: > It's my understanding that when the kernel drops core, it leaves behind an > image of your _entire_ VM space. Since this particular box has 512MB of RAM in > it, a 512MB core file seems reasonable to me. (I _like_ having half gig of > RAM!) > That was my point if you limit the amount of ram then you could diagnose the problem with only a 8 or 16MB file. Might make it easier to diagnose. Just a Thought John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 25 08:43:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25483 for freebsd-stable-outgoing; Sun, 25 Oct 1998 08:43:52 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.tfh-berlin.de (mail.tfh-berlin.de [141.64.3.223]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25475 for ; Sun, 25 Oct 1998 08:43:43 -0800 (PST) (envelope-from gregor@rslab04.tfh-berlin.de) Received: from rslab04.tfh-berlin.de (rslab04 [141.64.250.4]) by mail.tfh-berlin.de (8.9.1/8.9.1) with ESMTP id RAA798118 for ; Sun, 25 Oct 1998 17:43:03 +0100 (MEZ) Received: from rslab04.tfh-berlin.de (localhost.home [127.0.0.1]) by rslab04.tfh-berlin.de (8.8.8/8.8.8) with ESMTP id KAA01975 for ; Sun, 25 Oct 1998 10:22:19 +0100 (CET) (envelope-from gregor@rslab04.tfh-berlin.de) Message-ID: <3632EDCA.8FA077B4@rslab04.tfh-berlin.de> Date: Sun, 25 Oct 1998 10:22:18 +0100 From: Gregor Middell Reply-To: midell@tfh-berlin.de X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: FreeBSD-stable@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable midell@tfh-berlin.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 25 08:45:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25655 for freebsd-stable-outgoing; Sun, 25 Oct 1998 08:45:18 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from unix1.it-datacntr.louisville.edu (unix1.it-datacntr.louisville.edu [136.165.4.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25643 for ; Sun, 25 Oct 1998 08:45:15 -0800 (PST) (envelope-from k.stevenson@louisville.edu) Received: from homer.louisville.edu (ktstev01@homer.it-datacntr.louisville.edu [136.165.1.20]) by unix1.it-datacntr.louisville.edu (8.8.8/8.8.7) with ESMTP id LAA28926 for ; Sun, 25 Oct 1998 11:44:40 -0500 Received: (from ktstev01@localhost) by homer.louisville.edu (8.8.8/8.8.8) id LAA22559 for freebsd-stable@freebsd.org; Sun, 25 Oct 1998 11:44:40 -0500 (EST) Message-ID: <19981025114439.C20354@homer.louisville.edu> Date: Sun, 25 Oct 1998 11:44:39 -0500 From: Keith Stevenson To: freebsd-stable@FreeBSD.ORG Subject: Re: kernel panic from quota? References: <19981024033231.A6200@homer.louisville.edu> <19981024103119.16296@ka3tis.com> <19981024113253.B3102@homer.louisville.edu> <19981025082423.A237@ka3tis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981025082423.A237@ka3tis.com>; from John C. Place on Sun, Oct 25, 1998 at 08:24:23AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, now I understand. Thanks for the advice. Unfortunately, this box is the central NFS server for our engineering school's research computing cluster. I won't be able to test it until I can beg some more scheduled downtime out of them. On a followup note, if anyone who is following this thread can point me at some documentation/resources on how to do postmortem work on a kernel core file, I'll be happy to do it myself. I would rather not send-pr(1) this until I can provide more information than "it broke when I did this". Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 On Sun, Oct 25, 1998 at 08:24:23AM -0500, John C. Place wrote: > > > That was my point if you limit the amount of ram then you could diagnose the > problem with only a 8 or 16MB file. Might make it easier to diagnose. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 25 09:12:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27075 for freebsd-stable-outgoing; Sun, 25 Oct 1998 09:12:53 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from samurai.dee.uc.pt (samurai.dee.uc.pt [193.136.205.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27068 for ; Sun, 25 Oct 1998 09:12:51 -0800 (PST) (envelope-from freebsd@samurai.dee.uc.pt) Received: from localhost (freebsd@localhost) by samurai.dee.uc.pt (8.8.8/8.8.7) with SMTP id RAA00401 for ; Sun, 25 Oct 1998 17:12:14 GMT (envelope-from freebsd@samurai.dee.uc.pt) Date: Sun, 25 Oct 1998 17:12:14 +0000 (WET) From: FreeBSD To: stable@FreeBSD.ORG Subject: make release fails Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id JAA27071 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Everytime I do a make release, it fails due to incorrect variable substitution of ${MACHINE}. Why is this happening to me? Is this a problem or am I missing something? See below. Regards, Paulo Menezes mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include cd /; rm -f /sys; ln -s usr/src/sys sys cd /usr/share/locale; set - `cat /usr/src/etc/locale.alias`; while [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; done cd /usr/share/nls; set - `cat /usr/src/etc/locale.alias`; while [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; done; rm -rf POSIX; ln -s C POSIX (cd /usr/src/etc; install -c -o bin -g bin -m 644 aliases amd.map crontab csh.cshrc csh.login csh.logout dm.conf fbtab ftpusers gettytab group hosts host.conf hosts.equiv hosts.lpd inetd.conf login.conf login.access motd modems networks newsyslog.conf phones pccard.conf.sample printcap profile protocols rc rc.conf rc.devfs rc.firewall rc.local rc.network rc.pccard rc.serial rc.shutdown etc./rc. remote security services shells syslog.conf etc./ttys etc./disktab rpc make.conf /usr/src/etc/../gnu/usr.bin/man/manpath/manpath.config /usr/src/etc/../usr.bin/mail/misc/mail.rc /usr/src/etc/../usr.bin/locate/locate/locate.rc /etc; install -c -o bin -g bin -m 755 netstart pccard_ether /etc; install -c -o bin -g bin -m 600 /dev/null /var/cron/log; install -c -o bin -g bin -m 600 master.passwd /etc; ( cd /usr/src/etc/periodic; make install ); ( cd /usr/src/etc/../gnu/usr.bin/send-pr; make etc-gnats-freefall ); ( cd /usr/src/etc/../gnu/libexec/uucp/sample; make install ); ( cd /usr/src/etc/../share/termcap; make etc-termcap ); ( cd /usr/src/etc/../usr.sbin/rmt; make etc-rmt ); ( cd /usr/src/etc/sendmail; make etc-sendmail.cf ); ( cd /usr/src/etc/../sys/i386/boot/biosboot; make install-boothelp ); pwd_mkdb -p -d /etc /etc/master.passwd; install -c -o bin -g bin -m 555 MAKEDEV.local etc./MAKEDEV /dev ) install: etc./rc.: No such file or directory *** Error code 71 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 25 09:23:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27898 for freebsd-stable-outgoing; Sun, 25 Oct 1998 09:23:11 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from papaya.mail.easynet.net (papaya.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA27892 for ; Sun, 25 Oct 1998 09:23:07 -0800 (PST) (envelope-from andrew@sour.cream.org) Received: (qmail 22752 invoked from network); 25 Oct 1998 17:22:31 -0000 Received: from boothman.easynet.co.uk (194.154.100.117) by papaya.mail.easynet.net with SMTP; 25 Oct 1998 17:22:31 -0000 Received: by Boothman.easynet.co.uk (VPOP3 - Unregistered) with SMTP; Sun, 25 Oct 1998 17:20:01 -0000 Message-Id: <3.0.5.32.19981025172000.007cf500@ice.cream.org> X-Sender: andrew@ice.cream.org X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sun, 25 Oct 1998 17:20:00 +0000 To: Mark Murray From: Andrew Boothman Subject: Re: CTM Release Generation - (Re: Stable and CTM) Cc: "FreeBSD-Stable" In-Reply-To: <199810250757.JAA12650@gratis.grondar.za> References: <3.0.5.32.19981024225450.007af190@ice.cream.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Server: VPOP3 V1.2.0d Unregistered Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:57 25/10/98 +0200, Mark Murray wrote: >> Would it not be better to create an xR delta at the same >> time as the xEmpty delta then you could upgrade to the -stable code easily >> by downloading the deltas that then come afterwards as well? > >Disk space is a problem. OK. As a compromise you could possibly only keep the most recent xR delta, and delete the previous one. I realise that this goes against how the CTM system currently works, but it is a good way to get around the disk space problem. -- Andrew Boothman http://sour.cream.org PGP Key Available From Public Servers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 25 09:56:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00482 for freebsd-stable-outgoing; Sun, 25 Oct 1998 09:56:51 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00474 for ; Sun, 25 Oct 1998 09:56:46 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id TAA24686; Sun, 25 Oct 1998 19:55:56 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810251755.TAA24686@gratis.grondar.za> To: Andrew Boothman cc: "FreeBSD-Stable" Subject: Re: CTM Release Generation - (Re: Stable and CTM) In-Reply-To: Your message of " Sun, 25 Oct 1998 17:20:00 GMT." <3.0.5.32.19981025172000.007cf500@ice.cream.org> References: <3.0.5.32.19981024225450.007af190@ice.cream.org> <3.0.5.32.19981025172000.007cf500@ice.cream.org> Date: Sun, 25 Oct 1998 19:55:55 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Boothman wrote: > At 09:57 25/10/98 +0200, Mark Murray wrote: > >> Would it not be better to create an xR delta at the same > >> time as the xEmpty delta then you could upgrade to the -stable code easily > >> by downloading the deltas that then come afterwards as well? > > > >Disk space is a problem. > > OK. As a compromise you could possibly only keep the most recent xR delta, > and delete the previous one. I realise that this goes against how the CTM > system currently works, but it is a good way to get around the disk space > problem. No. The problem is the space to generate, not archive. Multiple copies of the source tree are needed, and a _crapload_ of scratch space. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 25 13:54:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21487 for freebsd-stable-outgoing; Sun, 25 Oct 1998 13:54:45 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dewdrop2.mindspring.com (dewdrop2.mindspring.com [207.69.200.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21482 for ; Sun, 25 Oct 1998 13:54:43 -0800 (PST) (envelope-from tom@chattpiano.com) Received: from chattpiano.com (user-37kbujf.dialup.mindspring.com [207.69.250.111]) by dewdrop2.mindspring.com (8.8.5/8.8.5) with ESMTP id QAA08389; Sun, 25 Oct 1998 16:54:04 -0500 (EST) Received: (from tom@localhost) by chattpiano.com (8.8.8/8.8.7) id QAA19412; Sun, 25 Oct 1998 16:53:01 -0500 (EST) (envelope-from tom) From: Tom Rush Message-Id: <199810252153.QAA19412@chattpiano.com> X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3.0.5.32.19981024183958.007dbe70@ice.cream.org> Date: Sun, 25 Oct 1998 16:53:01 -0500 (EST) To: Andrew Boothman Subject: RE: Stable and CTM Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Oct-98 Andrew Boothman wrote: > Hi, > > I'm interested in tracking -stable so I read the section in the manual > about " Synchronizing Source Trees over the Internet" and because my > FreeBSD box doesn't have a connection to the 'net, I selected CTM as the > best method for staying up-to-date because I can take CTM deltas to my > machine on disk. > > I went to ftp.freebsd.org/pub/FreeBSD/CTM/src-2.2/ to find the most recent > src-2.2.whateverxR227 file so that I could update from the source contained > on my WC 2.2.7-RELEASE CD2. > > Unfortunatly the only transition deltas available where the "xempty" ones. > In other words the ones that allow you to start from a completely empty > source tree. What happened to all the "xR227" transition deltas? I don't think there ever were any. I have used cvsup, and now ctm, to keep my cvs tree up to date. In order to get going with ctm, though, I found it necessary to do quite a bit of manual intervention to sync the tree with the ctm deltas. I cobbled up this script to help with it, which basically checks the md5 checksums to see if the delta is even close to where it should be. To use it, check the date of the files on your CD, then download the deltas that were made on or just before or after that date. Set the variables in the script appropriately, then run it with the delta number you want to check. If files need updating, ctm commands for those files only are echoed into a file that you can then run with /bin/sh. If not, you get some rather feeble instructions about what you might try next. Once things are synced and you have created a .ctm_status file, you can apply the remainder of the deltas normally. This script is by no means production quality. It doesn't do any modifications to the tree by itself, however, so it won't hurt anything to try it. Watch out for files shown as "does not exist" (other than .ctm_status); there probably won't be any, but if there are they would need to be specially handled. --- Tom Rush tom@chattpiano.com --------------- #!/bin/sh # # ctmsync -- script to help sync your source tree with ctm deltas # # Set the following variables: # # Where your sources are SRCTREE=/usr/src # Where your deltas are CTMDIR=${HOME}/CTM # Delta types you want to apply DELTATREE=src-2.2 if [ $# -ne 1 ]; then echo usage: `basename $0` ctm-delta-number exit 1 fi NDELTA=$1 DELTA=${CTMDIR}/${DELTATREE}.${NDELTA}.gz if [ ! -f $DELTA ]; then echo Can\'t find $DELTA exit 1 fi UPDATEFILE=${HOME}/ctmsync-${NDELTA} CTMFTMP=/tmp/ctmsync$$ UPTODATE=0 OUTOFDATE=0 OUTOFSYNC=0 cd $SRCTREE trap "rm -f $CTMFTMP $UPDATEFILE ; exit" 0 1 2 15 gzip -d -c $DELTA | grep '^CTMF' > $CTMFTMP exec < $CTMFTMP while read a file b c d cksum1 cksum2 e do if [ -f $file ]; then set `md5 $file` if [ "$4" = "$cksum1" ]; then echo $file is out of date OUTOFDATE=`expr $OUTOFDATE + 1` echo ctm -v -b ${SRCTREE} -e $file ${DELTA} >> ${UPDATEFILE} elif [ "$4" = "$cksum2" ]; then echo $file is up to date with this delta UPTODATE=`expr $UPTODATE + 1` else echo $file will not sync with this delta OUTOFSYNC=`expr $OUTOFSYNC + 1` fi else echo $file does not exist fi done rm -f $CTMFTMP echo echo You have $OUTOFDATE files out of date, $UPTODATE files up to date, echo and $OUTOFSYNC files out of sync with this delta. echo if [ ${OUTOFDATE} -eq 0 ]; then if [ ${OUTOFSYNC} -gt 0 ]; then echo If you have no out of date files and only some out of sync, then echo you should probably try a later delta. else echo You seem to be up to date for the files in this delta. fi else echo You can update the out of date files with the command: echo \"sh ${UPDATEFILE}\" if [ ${OUTOFSYNC} -gt 0 ]; then echo However, you may need to apply an earlier delta for the echo out of sync files. elif [ ${UPTODATE} -eq 0 ]; then echo Since no files are or up to date or out of sync, you may be echo able to use ctm normally, e.g. \"ctm -v -b $SRCTREE ${DELTA}\". echo But you will need to create .ctm_status using the number of echo the previous delta. fi fi echo echo When you get things in sync, you need to create the file echo ${SRCTREE}/.ctm_status, which contains the latest delta number, echo e.g. \"echo ${NDELTA} \> ${SRCTREE}/.ctm_status\" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 25 18:09:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11943 for freebsd-stable-outgoing; Sun, 25 Oct 1998 18:09:22 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11937 for ; Sun, 25 Oct 1998 18:09:21 -0800 (PST) (envelope-from cy@cwsys.cwsent.com.net.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id SAA15997; Sun, 25 Oct 1998 18:08:46 -0800 (PST) Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by passer.osg.gov.bc.ca, id smtpdV15995; Sun Oct 25 18:07:59 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.8.8/8.6.10) id JAA12128; Sun, 25 Oct 1998 09:32:51 -0800 (PST) Message-Id: <199810251732.JAA12128@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdm11765; Sun Oct 25 09:32:40 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: Kazutaka YOKOTA cc: insane@oneinsane.net, freebsd-stable@FreeBSD.ORG Subject: Re: System will not Complete Shutdown In-reply-to: Your message of "Thu, 22 Oct 1998 10:44:40 +0900." <199810220144.KAA09156@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Oct 1998 09:32:36 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199810220144.KAA09156@zodiac.mech.utsunomiya-u.ac.jp>, Kazutaka YOK OTA writes: > > >I Just built a new box that I am going to make sorta a > >Firewall/Gateway box. Here is the dmesg output. > [...] > >The system works fine untill I issue a shutdown -r now or reboot. > >The system appears to shutdown untill This is the last thing on the screen. > > > >Keyboard reset did not work, attempting CPU shutdown. [snip] > For reasons unintelligible to me, IBM decided to put the CPU reset > circuit wired to the keyboard controller in the IBM AT computer. You > are supposed to instruct the keyboard controller to reset the CPU when > you want to restart the system. > > Unfortunately, the keyboard controller is one of peripheral chips which > often have subtle compatibility problems. The FreeBSD kernel talks to > the keyboard controller in order to reboot the system. If it finds > the reset didn't work, it prints the above message. > > Please add the following option to your kernel configuration file, > rebuild the kernel, and see if it works. > > options "BROKEN_KEYBOARD_RESET" I had similar problems with FreeBSD and OS/2. Replacing the keyboard BIOS (keyboard controller) solved the problem. Apparently the "F" level keyboard BIOS fixes this problem. The "M" level keyboard BIOS will hang during boot of certain operating systems. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 25 18:38:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13894 for freebsd-stable-outgoing; Sun, 25 Oct 1998 18:38:07 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13888 for ; Sun, 25 Oct 1998 18:38:04 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40324>; Mon, 26 Oct 1998 13:36:52 +1100 Date: Mon, 26 Oct 1998 13:36:27 +1100 From: Peter Jeremy Subject: Re: System will not Complete Shutdown To: stable@FreeBSD.ORG Message-Id: <98Oct26.133652est.40324@border.alcanet.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: > For reasons unintelligible to me, IBM decided to put the CPU reset > circuit wired to the keyboard controller in the IBM AT computer. You > are supposed to instruct the keyboard controller to reset the CPU when > you want to restart the system. This particular piece of brokenness is a result of Intel's decision not to provide a protected-mode -> real-mode switch on the 80286. The 286 resets into real mode. If you change it to protected mode, there's no way (other than reset) to get back to real mode. Since the BIOS, M$-DOS and applications ran in real mode, but the extended memory was only accessible in protected mode, the processor needed to switch between real and protected modes. The way around the lack of CPU support for getting from protected mode back to real mode was to write a magic value at a magic address in BIOS-reserved RAM, tell the keyboard controller to reset the CPU and then during the reset processing, check for the magic value and continue execution `normally' if it was found. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 25 19:30:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18715 for freebsd-stable-outgoing; Sun, 25 Oct 1998 19:30:29 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from scn4.scn.org (scn4.scn.org [209.63.95.149]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18709 for ; Sun, 25 Oct 1998 19:30:28 -0800 (PST) (envelope-from bc587@scn.org) Received: from scn.org (bc587@scn [209.63.95.146]) by scn4.scn.org (8.9.1/8.9.1) with ESMTP id TAA11144 for ; Sun, 25 Oct 1998 19:33:56 -0800 (PST) Received: from localhost (bc587@localhost) by scn.org (8.7.5/8.6.12) with SMTP id TAA24174 for ; Sun, 25 Oct 1998 19:37:26 -0800 (PST) Date: Sun, 25 Oct 1998 19:37:26 -0800 (PST) From: Allan Bowhill X-Sender: bc587@scn To: freebsd-stable@FreeBSD.ORG Subject: Using SGML to merge /etc Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everyone, Has anyone given thought to using SGML to update /etc during make world? In principle, it would be well-suited for resolving differences at a high granularity, based on marked content rather than character-level differences. For instance, diff would notice most differing characters in comment fields in rc.conf. When comparing old to new, the merge person is forced to resolve these at the same level as important differences, like the addition of a new configuration option. With the right markup, importance could be attached to fragments of a config file, so the person merging would not have to be concerned with inconsequential changes. Development in this area might make things more automatic. Any thoughts, or has this been discussed already? ------------- Allan Bowhill bc587@scn.org ------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Oct 25 21:59:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03971 for freebsd-stable-outgoing; Sun, 25 Oct 1998 21:59:54 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from chickenbean.ais-gwd.com (chickenbean.com [205.160.97.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03574; Sun, 25 Oct 1998 21:57:41 -0800 (PST) (envelope-from charlespeters@chickenbean.com) Received: from ci1000971-d.sptnbrg1.sc.home.com (ci1000971-d.sptnbrg1.sc.home.com [24.4.115.200]) by chickenbean.ais-gwd.com (8.8.8/8.8.8) with SMTP id BAA02260; Mon, 26 Oct 1998 01:09:12 -0500 (EST) (envelope-from charlespeters@chickenbean.com) Reply-To: From: "Charles A. Peters" To: , , , , , , , , , , , , , , , , Date: Mon, 26 Oct 1998 00:51:11 -0500 Message-ID: <000001be00a5$5e2d8d40$c8730418@ci1000971-d.sptnbrg1.sc.home.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 01:06:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19956 for freebsd-stable-outgoing; Mon, 26 Oct 1998 01:06:51 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from owl.org (owl.org [198.206.215.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19949 for ; Mon, 26 Oct 1998 01:06:47 -0800 (PST) (envelope-from cgull@owl.org) Received: (from cgull@localhost) by owl.org (8.9.1/8.9.1/cgull) id EAA03726; Mon, 26 Oct 1998 04:04:38 -0500 (EST) Message-ID: <19981026040438.38079@owl.org> Date: Mon, 26 Oct 1998 04:04:38 -0500 From: john hood To: Burkard Meyendriesch Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ECC memory support References: <199810222157.XAA04898@Reineke.malepartus.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <199810222157.XAA04898@Reineke.malepartus.de>; from Burkard Meyendriesch on Thu, Oct 22, 1998 at 11:57:01PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 22, 1998 at 11:57:01PM +0200, Burkard Meyendriesch wrote: > thanks for the hint. Yes indeed, I run an AMD K6/233 with ECC enabled; > last night I upgraded my BIOS. Maybe it will help my spurious errors to > disappear... > > But my original questions are still pending: Isn't there any possibility > to detect 1-bit errors even if they are detected and corrected by my > ECC electronics? Isn't there any register of the 82430HX chip set which > can be examined after an memory error NMI? The only thing I could find is I coded this hack up a few weeks ago. It runs from cron. I can't be sure it works because it hasn't reported a single-bit error yet :) It's not exactly user-friendly (you'll need Intel doco to make sense of the ECC register), but you have to know how your motherboard is wired up to make sense of the error report anyway. I'm running it on a '440FX-based board, but my docs on the '430HX indicate it handles ECC reporting basically the same way, through this same register. --jh #!/usr/local/bin/bash PATH=/sbin:/usr/sbin:/bin:/usr/bin i=`pciconf -r pci0:0:0 0x90` SELF=$(( ( $i / 0x100 ) % 2 )) if [ $SELF -ne 0 ] then pciconf -w pci0:0:0 0x90 $i msg="ECC register is $i, register cleared" logger $i echo $i | mail -s "ECC error" root fi -- Mr. Belliveau said, "the difference was the wise, John Hood, cgull intelligent look on the face of the cow." He was @ *so* right. --Ofer Inbar owl.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 01:33:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22247 for freebsd-stable-outgoing; Mon, 26 Oct 1998 01:33:42 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from Gambit.Msk.SU (gambit.msk.su [194.190.206.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22242 for ; Mon, 26 Oct 1998 01:33:38 -0800 (PST) (envelope-from laskavy@Gambit.Msk.SU) Received: (from laskavy@localhost) by Gambit.Msk.SU (8.0/8.9.1) id MAA25235; Mon, 26 Oct 1998 12:32:47 +0300 (MSK) To: Keith Stevenson Cc: freebsd-stable@FreeBSD.ORG Subject: Re: kernel panic from quota? References: <19981024033231.A6200@homer.louisville.edu> From: "Sergei S. Laskavy" Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Date: 26 Oct 1998 12:32:46 +0300 In-Reply-To: Keith Stevenson's message of Sat, 24 Oct 1998 03:32:31 -0400 Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Keith Stevenson writes: > If anyone is interested in doing some post-mortem work, I can make > the core file available via FTP. (It's ~512 MB, so I'm not going to > email it to anyone) Remember, it contains your passwords, maybe even not encrypted... -- FreeBSD Project: http://FreeBSD.org/docproj/ Vim: http://www.vim.org/ $_='$6C86:P$^P|2D<2GJPl=2D<2GJp82>3:E^>D<^DFn';tr#P-~\x20-O#\x20-~#;print To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 05:04:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08112 for freebsd-stable-outgoing; Mon, 26 Oct 1998 05:04:41 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from papaya.mail.easynet.net (papaya.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA08107 for ; Mon, 26 Oct 1998 05:04:37 -0800 (PST) (envelope-from andrew@sour.cream.org) Received: (qmail 248 invoked from network); 26 Oct 1998 13:03:59 -0000 Received: from boothman.easynet.co.uk (194.154.100.117) by papaya.mail.easynet.net with SMTP; 26 Oct 1998 13:03:59 -0000 Message-Id: <3.0.5.32.19981026130353.007b7e90@ice.cream.org> X-Sender: andrew@ice.cream.org X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 26 Oct 1998 13:03:53 +0000 To: Mark Murray From: Andrew Boothman Subject: Re: CTM Release Generation - (Re: Stable and CTM) Cc: "FreeBSD-Stable" In-Reply-To: <199810251755.TAA24686@gratis.grondar.za> References: <3.0.5.32.19981024225450.007af190@ice.cream.org> <3.0.5.32.19981025172000.007cf500@ice.cream.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 19:55 25/10/98 +0200, Mark Murray wrote: >> OK. As a compromise you could possibly only keep the most recent xR delta, >> and delete the previous one. I realise that this goes against how the CTM >> system currently works, but it is a good way to get around the disk space >> problem. > >No. The problem is the space to generate, not archive. Multiple copies >of the source tree are needed, and a _crapload_ of scratch space. Right, OK, sorry for the misunderstanding. As the handbook states, there is no documentation on the creation of CTM deltas so could you enlighten me as to why multiple source trees are needed? Surely it is more or less a diff between the code as frozen on the release date, and the code as it stands today? Failing that, which machine currently produces CTM deltas, and would be charged with creating the release deltas? Could this operation be moved to a machine with more space available? I would really like to see this system set-up one way or another. I'm sorry for pushing this point so much, but I think that it would be a really useful feature for users coming to track -stable or -current for the first time. I'm sure that the majority of such users would already have -Release code from WC CDROM sets, and would appriciate not having to download it all again. :-) Many thanks for your patience. -- Andrew Boothman http://sour.cream.org PGP Key Available From Public Servers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 06:17:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15018 for freebsd-stable-outgoing; Mon, 26 Oct 1998 06:17:59 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14945 for ; Mon, 26 Oct 1998 06:17:44 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id QAA27648; Mon, 26 Oct 1998 16:16:38 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810261416.QAA27648@gratis.grondar.za> To: Andrew Boothman cc: "FreeBSD-Stable" Subject: Re: CTM Release Generation - (Re: Stable and CTM) In-Reply-To: Your message of " Mon, 26 Oct 1998 13:03:53 GMT." <3.0.5.32.19981026130353.007b7e90@ice.cream.org> References: <3.0.5.32.19981024225450.007af190@ice.cream.org> <3.0.5.32.19981025172000.007cf500@ice.cream.org> <3.0.5.32.19981026130353.007b7e90@ice.cream.org> Date: Mon, 26 Oct 1998 16:16:37 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Boothman wrote: > As the handbook states, there is no documentation on the creation of CTM > deltas so could you enlighten me as to why multiple source trees are > needed? Surely it is more or less a diff between the code as frozen on the > release date, and the code as it stands today? Yes. 1 copy for "release code", one copy for "current code". Multiply that by N for our different releases, the CVS tree and the ports collection, and things add up a tad. > Failing that, which machine currently produces CTM deltas, and would be > charged with creating the release deltas? Could this operation be moved to > a machine with more space available? If that is an offer for the machine, then yes, thank you. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org PS if your bot mails me again to tell me about the newspaper balls-up, I may just go postal. There are better solutions; please check out vacation(1). m To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 07:17:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20514 for freebsd-stable-outgoing; Mon, 26 Oct 1998 07:17:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA20458 for ; Mon, 26 Oct 1998 07:16:22 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id OAA02338; Mon, 26 Oct 1998 14:08:55 +0100 From: Luigi Rizzo Message-Id: <199810261308.OAA02338@labinfo.iet.unipi.it> Subject: Re: CTM Release Generation - (Re: Stable and CTM) To: mark@grondar.za (Mark Murray) Date: Mon, 26 Oct 1998 14:08:54 +0100 (MET) Cc: andrew@sour.cream.org, FreeBSD-Stable@FreeBSD.ORG In-Reply-To: <199810261416.QAA27648@gratis.grondar.za> from "Mark Murray" at Oct 26, 98 04:16:18 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Andrew Boothman wrote: > > As the handbook states, there is no documentation on the creation of CTM > > deltas so could you enlighten me as to why multiple source trees are > > needed? Surely it is more or less a diff between the code as frozen on the > > release date, and the code as it stands today? > > Yes. 1 copy for "release code", one copy for "current code". Multiply > that by N for our different releases, the CVS tree and the ports > collection, and things add up a tad. i am just jumping in on the middle of a discussion so apologies if i say stupid things... but isn't everything one needs in the CVS repository so _in theory_ at least one could ask cvs, file by file, to produce the differences without having to replicate things ? And, being things stored in cvs, the deltas from one version to the other of the same file are stored in a reasonable compact way... ... where is the code ? oh yes the code... cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 07:46:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22393 for freebsd-stable-outgoing; Mon, 26 Oct 1998 07:46:41 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22375 for ; Mon, 26 Oct 1998 07:46:32 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id RAA27972; Mon, 26 Oct 1998 17:41:56 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810261541.RAA27972@gratis.grondar.za> To: Luigi Rizzo cc: andrew@sour.cream.org, FreeBSD-Stable@FreeBSD.ORG Subject: Re: CTM Release Generation - (Re: Stable and CTM) In-Reply-To: Your message of " Mon, 26 Oct 1998 14:08:54 +0100." <199810261308.OAA02338@labinfo.iet.unipi.it> References: <199810261308.OAA02338@labinfo.iet.unipi.it> Date: Mon, 26 Oct 1998 17:41:54 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > i am just jumping in on the middle of a discussion so apologies if i > say stupid things... but isn't everything one needs in the CVS > repository so _in theory_ at least one could ask cvs, file by file, to > produce the differences without having to replicate things ? And, being > things stored in cvs, the deltas from one version to the other of the > same file are stored in a reasonable compact way... > > ... where is the code ? oh yes the code... I looked at the end of your message, and you forgot to attach it... ;-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 09:02:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29278 for freebsd-stable-outgoing; Mon, 26 Oct 1998 09:02:41 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.esigroup.com (esiwg.esigroup.com [205.218.124.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29270 for ; Mon, 26 Oct 1998 09:02:39 -0800 (PST) (envelope-from RHall@esigroup.com) Received: by ESIPROD with Internet Mail Service (5.5.1960.3) id ; Mon, 26 Oct 1998 10:56:06 -0600 Message-ID: <2C10B557AEBDD011872500A0C933CDDB4A6168@ESIPROD> From: Roger Hall To: FreeBSD-Stable@FreeBSD.ORG Subject: NIC Config Help Date: Mon, 26 Oct 1998 10:56:04 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a box that was running 2.2.6 just fine (I installed over the internet - which I was very impressed with BTW). I received my 2.2.7 disk set with the Complete FreeBSD, tried to setup booting into X, and discovered the "magic number" issue. So I decided to create a new boot floppy, and re-install from disk 1. Now, my network card isn't found (or the kernel page faults). I'm using a 3Com Etherlink II/16 TP, which has a whole row of jumpers. 300 *original setting 310 330 350 250 280 2A0 2E0 DISABLE C8000 CC000 D8000 *original setting DC000 Previously, ed0 was found at 300, and I know the card was set to D8000, but I can't remember how that translates into "flags" in the visual config editor. I have tried multiple combinations (and two cards), and it is always either not found or faults (right after sc0, which is where ed0 is usually probed). Fatal trap 12: page fault while in kernel mode fault virtual address = 0xefc00000 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01e7363 stack pointer = 0x10:0xefbffefc frame pointer = 0x10:0xefbffefc 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 = 0 () interrupt mask = net tty bio cam panic: page fault The NIC IRQ is 9, and I have no conflicts in the visual editor. Sup wit dat? (The real pain is that I just convinced my organization that this was the best solution for a listserver, and after working for a couple of weeks it's hosed!) :} TIA so mighty, Roger Hall Webmaster http://www.esigroup.com 501.666.4233.296 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 11:21:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10930 for freebsd-stable-outgoing; Mon, 26 Oct 1998 11:21:55 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10925 for ; Mon, 26 Oct 1998 11:21:52 -0800 (PST) (envelope-from rkw@Dataplex.NET) From: rkw@Dataplex.NET Received: from dataplex.net (nomad.dataplex.net [208.2.87.8]) by shrimp.dataplex.net (8.9.1/8.9.1) with ESMTP id RAA19616; Mon, 26 Oct 1998 17:38:27 -0600 (CST) (envelope-from rkw@dataplex.net) Message-Id: <199810262338.RAA19616@shrimp.dataplex.net> Date: Mon, 26 Oct 1998 13:20:49 -0600 (CST) Subject: Re: CTM Release Generation - (Re: Stable and CTM) To: luigi@labinfo.iet.unipi.it cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <199810261308.OAA02338@labinfo.iet.unipi.it> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 Oct, Luigi Rizzo wrote: > i am just jumping in on the middle of a discussion so apologies if i > say stupid things... but isn't everything one needs in the CVS > repository so _in theory_ at least one could ask cvs, file by file, to > produce the differences without having to replicate things ? And, being > things stored in cvs, the deltas from one version to the other of the > same file are stored in a reasonable compact way... The fundamental problem is "_in theory_". In practice, the master CVS tree gets yanked around from time to time. AFAIK, the only way to be certain that you have a correct copy of the tree, as distributed by CTM, is to generate it by actually applying the CTM deltas. As for a shortcut to generating the deltas, I would be more inclined to snoop on a cvsup session and capture a list of files which need attention. You would still need to periodically run a full comparison to make sure that nothing fell through the cracks. The real hangup in the whole process is related to the inefficient way that our sources are stored in single tree. In order to get to the recent 2.2 tree, you have to back out a whole lot of changes to "current" to get back to the branch point and then put many of them back in when you return up the 2.2 history track. I know that the would be more efficient to have a separate tree for tracking 2.2. I also suspect that it would require little extra HD space. The other advantage would be that the old history on the bottom of the rcs files could be removed and stored on a read-only area which chains from the current file. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 11:31:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12107 for freebsd-stable-outgoing; Mon, 26 Oct 1998 11:31:11 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from papaya.mail.easynet.net (papaya.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA12099 for ; Mon, 26 Oct 1998 11:31:05 -0800 (PST) (envelope-from andrew@sour.cream.org) Received: (qmail 18722 invoked from network); 26 Oct 1998 19:29:54 -0000 Received: from boothman.easynet.co.uk (194.154.100.117) by papaya.mail.easynet.net with SMTP; 26 Oct 1998 19:29:54 -0000 Received: by Boothman.easynet.co.uk (VPOP3 - Unregistered) with SMTP; Mon, 26 Oct 1998 19:01:18 -0000 Message-Id: <3.0.5.32.19981026190118.007ac480@ice.cream.org> X-Sender: andrew@ice.cream.org X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 26 Oct 1998 19:01:18 +0000 To: Mark Murray From: Andrew Boothman Subject: Re: CTM Release Generation - (Re: Stable and CTM) Cc: "FreeBSD-Stable" In-Reply-To: <199810261416.QAA27648@gratis.grondar.za> References: <3.0.5.32.19981024225450.007af190@ice.cream.org><3.0.5.32.19981025172000.007cf500@ice.cream.org><3.0.5.32.19981026130353.007b7e90@ice.cream.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Server: VPOP3 V1.2.0d Unregistered Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 16:16 26/10/98 +0200, Mark Murray wrote: >Andrew Boothman wrote: >> As the handbook states, there is no documentation on the creation of CTM >> deltas so could you enlighten me as to why multiple source trees are >> needed? Surely it is more or less a diff between the code as frozen on the >> release date, and the code as it stands today? > >Yes. 1 copy for "release code", one copy for "current code". Multiply >that by N for our different releases, the CVS tree and the ports >collection, and things add up a tad. 650 MBs or so? (plucked out of the air) >> Failing that, which machine currently produces CTM deltas, and would be >> charged with creating the release deltas? Could this operation be moved to >> a machine with more space available? > >If that is an offer for the machine, then yes, thank you. :-) I don't have spare machines just lying about you know. My FreeBSD box has a spare 1.5GB still, but I don't rekon I've got the technical experience to create deltas for the whole project. (I'm still trying to learn the OS) Surely a FreeBSD.org host has a bit of slack space that could be used for something like this? Can anybody comment? It seems a shame that disk space is the only thing stopping CTM from running as documented. Thanks. -- Andrew Boothman http://sour.cream.org PGP Key Available From Public Servers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 11:31:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12137 for freebsd-stable-outgoing; Mon, 26 Oct 1998 11:31:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from papaya.mail.easynet.net (papaya.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA12116 for ; Mon, 26 Oct 1998 11:31:14 -0800 (PST) (envelope-from andrew@sour.cream.org) Received: (qmail 18759 invoked from network); 26 Oct 1998 19:29:56 -0000 Received: from boothman.easynet.co.uk (194.154.100.117) by papaya.mail.easynet.net with SMTP; 26 Oct 1998 19:29:56 -0000 Received: by Boothman.easynet.co.uk (VPOP3 - Unregistered) with SMTP; Mon, 26 Oct 1998 19:10:19 -0000 Message-Id: <3.0.5.32.19981026191018.007ad150@ice.cream.org> X-Sender: andrew@ice.cream.org X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 26 Oct 1998 19:10:18 +0000 To: Luigi Rizzo From: Andrew Boothman Subject: Re: CTM Release Generation - (Re: Stable and CTM) Cc: FreeBSD-Stable@FreeBSD.ORG, mark@grondar.za (Mark Murray) In-Reply-To: <199810261308.OAA02338@labinfo.iet.unipi.it> References: <199810261416.QAA27648@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Server: VPOP3 V1.2.0d Unregistered Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 14:08 26/10/98 +0100, Luigi Rizzo wrote: >i am just jumping in on the middle of a discussion so apologies if i >say stupid things... but isn't everything one needs in the CVS >repository so _in theory_ at least one could ask cvs, file by file, to >produce the differences without having to replicate things ? And, being >things stored in cvs, the deltas from one version to the other of the >same file are stored in a reasonable compact way... > >... where is the code ? oh yes the code... :-) I presumed that this is how deltas are currently created. As Luigi points out it would certainly reduce the disk space requirement. Wouldn't the code the produces deltas currently (by checking what's changed since the last delta) be fairly easily adapted to produce the release deltas (by checking what's changed since the last release)? I cannot really do such devlopment myself, because I'm very new to unix and to FreeBSD and I don't know enough to be able to write such code. (But I know enough to know what I want :-). Does anyone else reading have the expertise/time to take this on? (Assuming that this is all that's needed) Thanks -- Andrew Boothman http://sour.cream.org PGP Key Available From Public Servers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 11:40:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13274 for freebsd-stable-outgoing; Mon, 26 Oct 1998 11:40:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13267 for ; Mon, 26 Oct 1998 11:40:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00622; Mon, 26 Oct 1998 11:40:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810261940.LAA00622@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Roger Hall cc: FreeBSD-Stable@FreeBSD.ORG Subject: Re: NIC Config Help In-reply-to: Your message of "Mon, 26 Oct 1998 10:56:04 CST." <2C10B557AEBDD011872500A0C933CDDB4A6168@ESIPROD> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Oct 1998 11:40:12 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a box that was running 2.2.6 just fine (I installed over the > internet - which I was very impressed with BTW). I received my 2.2.7 > disk set with the Complete FreeBSD, tried to setup booting into X, and > discovered the "magic number" issue. So I decided to create a new boot > floppy, and re-install from disk 1. Now, my network card isn't found (or > the kernel page faults). > > I'm using a 3Com Etherlink II/16 TP, which has a whole row of jumpers. > 300 *original setting > 310 > 330 > 350 > 250 > 280 > 2A0 > 2E0 > > DISABLE > C8000 > CC000 > D8000 *original setting > DC000 > > Previously, ed0 was found at 300, and I know the card was set to D8000, > but I can't remember how that translates into "flags" in the visual > config editor. It doesn't. Leave the flags alone. Set the port and memory addresses to match the card. > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xefc00000 You have the memory address set wrong; set it right. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 11:47:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14101 for freebsd-stable-outgoing; Mon, 26 Oct 1998 11:47:13 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14095 for ; Mon, 26 Oct 1998 11:47:12 -0800 (PST) (envelope-from rkw@Dataplex.NET) From: rkw@Dataplex.NET Received: from dataplex.net (nomad.dataplex.net [208.2.87.8]) by shrimp.dataplex.net (8.9.1/8.9.1) with ESMTP id SAA19664; Mon, 26 Oct 1998 18:05:25 -0600 (CST) (envelope-from rkw@dataplex.net) Message-Id: <199810270005.SAA19664@shrimp.dataplex.net> Date: Mon, 26 Oct 1998 13:46:27 -0600 (CST) Subject: Re: CTM Release Generation - (Re: Stable and CTM) To: andrew@sour.cream.org cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <3.0.5.32.19981026190118.007ac480@ice.cream.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 Oct, Andrew Boothman wrote: > Surely a FreeBSD.org host has a bit of slack space that could be used for > something like this? Can anybody comment? Actually, they abandoned CTM some years ago because of the lack of those resources. I carried it on for a couple years, and now Mark has taken over to chores. I assure you that the resources required anr NOT insignificant. It eats up a lot of disk space, I/O time and CPU time. None of those have come from freebsd.org in quite some time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 12:04:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16101 for freebsd-stable-outgoing; Mon, 26 Oct 1998 12:04:54 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ccsales.com (ccsales.com [216.0.22.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16093; Mon, 26 Oct 1998 12:04:49 -0800 (PST) (envelope-from randyk@ccsales.com) Received: from ntrkcasa (pool96.hiper.net [216.0.22.96]) by ccsales.com (8.9.1/8.9.0) with SMTP id MAA19254; Mon, 26 Oct 1998 12:03:54 -0800 (PST) Message-Id: <3.0.5.32.19981026115650.05103b10@ccsales.com> X-Sender: randyk@ccsales.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 26 Oct 1998 11:56:50 -0800 To: Bill Sandiford , freebsd-current@FreeBSD.ORG From: "Randy A. Katz" Subject: Re: FreeBSD 3.0 Release and pw command - Potential Bug? Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check your $PATH. At 05:28 PM 10/22/98 -0400, Bill Sandiford wrote: > > >We are having a problem with FreeBSD 3.0 Release and it's associated pw >command. We have scripts that used to work perfectly in the 2.2.x line. >The script still works perfectly when we run it manually as root (logged >in at the terminal) however when cron executes the script, the pw commands >in the script don't work. We are executing the script using the crontab >for root. We know that the script is executing because some of the >other commands in the script are happening and working. The script is >designed to add a new user to our system and the line with pw looks >something like this : > >echo password | pw useradd username -h 0 -c "Full Name" -g group -u uid -m -d homedir > >obviously we substitute a correct numeric id for uid and proper groupname >for group, etc. > >We are not sure if this is a problem with our system or a bug with the pw >command that is in the 3.0 release...we have also tried invoking the >script from and inetd process as well.....we have tried this script on 3 >different systems and it doesn't work on any of them except when invoked >manually. > >Any help please!!! > >------------------------------------------ >Bill Sandiford Jr. - Systems Administrator >Interlinks - http://www.interlinks.net >sysop@interlinks.net - bill@interlinks.net >(905)404-0810 > > > > >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-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 12:39:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20247 for freebsd-stable-outgoing; Mon, 26 Oct 1998 12:39:13 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from papaya.mail.easynet.net (papaya.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA20209 for ; Mon, 26 Oct 1998 12:39:06 -0800 (PST) (envelope-from andrew@sour.cream.org) Received: (qmail 18945 invoked from network); 26 Oct 1998 20:37:57 -0000 Received: from boothman.easynet.co.uk (194.154.100.117) by papaya.mail.easynet.net with SMTP; 26 Oct 1998 20:37:57 -0000 Received: by Boothman.easynet.co.uk (VPOP3 - Unregistered) with SMTP; Mon, 26 Oct 1998 20:35:57 -0000 Message-Id: <3.0.5.32.19981026203556.007d5d00@ice.cream.org> X-Sender: andrew@ice.cream.org X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 26 Oct 1998 20:35:56 +0000 To: rkw@Dataplex.NET From: Andrew Boothman Subject: Re: CTM Release Generation - (Re: Stable and CTM) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <199810270005.SAA19664@shrimp.dataplex.net> References: <3.0.5.32.19981026190118.007ac480@ice.cream.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Server: VPOP3 V1.2.0d Unregistered Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 13:46 26/10/98 -0600, rkw@Dataplex.NET wrote: >On 26 Oct, Andrew Boothman wrote: >> Surely a FreeBSD.org host has a bit of slack space that could be used for >> something like this? Can anybody comment? > >Actually, they abandoned CTM some years ago because of the lack of >those resources. I carried it on for a couple years, and now Mark has >taken over to chores. I see. In this respect the handbook desperately needs changing. It needs to reflect the fact that CTM is really no longer a favoured way of staying up to date. I think it's a massive shame, because CTM is ideal for people with 'net access to another box but not the FreeBSD one. However I understand that Mark doesn't have the resources to take on this extra burden as well. I would help out myself, but I don't have the experience or spare time to be helpful. Do you think pleading letters to hackers@freebsd.org (or maybe even to the core team) might help to find someone willing to take this on? -- Andrew Boothman http://sour.cream.org PGP Key Available From Public Servers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 12:46:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21043 for freebsd-stable-outgoing; Mon, 26 Oct 1998 12:46:49 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21029 for ; Mon, 26 Oct 1998 12:46:42 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id WAA28988; Mon, 26 Oct 1998 22:45:50 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810262045.WAA28988@gratis.grondar.za> To: Andrew Boothman cc: freebsd-stable@FreeBSD.ORG Subject: Re: CTM Release Generation - (Re: Stable and CTM) In-Reply-To: Your message of " Mon, 26 Oct 1998 20:35:56 GMT." <3.0.5.32.19981026203556.007d5d00@ice.cream.org> References: <3.0.5.32.19981026190118.007ac480@ice.cream.org> <3.0.5.32.19981026203556.007d5d00@ice.cream.org> Date: Mon, 26 Oct 1998 22:45:49 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Boothman wrote: > I see. In this respect the handbook desperately needs changing. It needs to > reflect the fact that CTM is really no longer a favoured way of staying up > to date. It is, just not in the way you want. > Do you think pleading letters to hackers@freebsd.org (or maybe even to the > core team) might help to find someone willing to take this on? No. Doing it yourself will get you places, though... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 13:12:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23157 for freebsd-stable-outgoing; Mon, 26 Oct 1998 13:12:50 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.esigroup.com (esiwg.esigroup.com [205.218.124.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23151 for ; Mon, 26 Oct 1998 13:12:49 -0800 (PST) (envelope-from RHall@esigroup.com) Received: by ESIPROD with Internet Mail Service (5.5.1960.3) id ; Mon, 26 Oct 1998 15:06:16 -0600 Message-ID: <2C10B557AEBDD011872500A0C933CDDB4A617B@ESIPROD> From: Roger Hall To: Mike Smith Cc: FreeBSD-Stable@FreeBSD.ORG Subject: RE: NIC Config Help Date: Mon, 26 Oct 1998 15:06:15 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the visual config, I only see "Port", "IRQ number" and "Flags" for dev ed0. Where is the memory setting? Is D8000 an appropriate jumper setting? Roger Hall Webmaster http://www.esigroup.com 501.666.4233.296 > -----Original Message----- > From: Mike Smith [SMTP:mike@smith.net.au] > Sent: Monday, October 26, 1998 1:40 PM > To: Roger Hall > Cc: FreeBSD-Stable@FreeBSD.ORG > Subject: Re: NIC Config Help > > > I have a box that was running 2.2.6 just fine (I installed over the > > internet - which I was very impressed with BTW). I received my 2.2.7 > > disk set with the Complete FreeBSD, tried to setup booting into X, > and > > discovered the "magic number" issue. So I decided to create a new > boot > > floppy, and re-install from disk 1. Now, my network card isn't found > (or > > the kernel page faults). > > > > I'm using a 3Com Etherlink II/16 TP, which has a whole row of > jumpers. > > 300 *original setting > > 310 > > 330 > > 350 > > 250 > > 280 > > 2A0 > > 2E0 > > > > DISABLE > > C8000 > > CC000 > > D8000 *original setting > > DC000 > > > > Previously, ed0 was found at 300, and I know the card was set to > D8000, > > but I can't remember how that translates into "flags" in the visual > > config editor. > > It doesn't. Leave the flags alone. Set the port and memory addresses > > to match the card. > > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0xefc00000 > > You have the memory address set wrong; set it right. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 13:18:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23726 for freebsd-stable-outgoing; Mon, 26 Oct 1998 13:18:11 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23720 for ; Mon, 26 Oct 1998 13:18:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01142; Mon, 26 Oct 1998 13:16:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810262116.NAA01142@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Roger Hall cc: Mike Smith , FreeBSD-Stable@FreeBSD.ORG Subject: Re: NIC Config Help In-reply-to: Your message of "Mon, 26 Oct 1998 15:06:15 CST." <2C10B557AEBDD011872500A0C933CDDB4A617B@ESIPROD> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Oct 1998 13:16:55 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In the visual config, I only see "Port", "IRQ number" and "Flags" for > dev ed0. Where is the memory setting? Is D8000 an appropriate jumper > setting? d8000 is fine; there *should* be an 'iomem' field that defaults to 0xd8000. It looks like your kernel has it set to 0 for some reason. Go to the commandline prompt instead of the visual config editor and say "iomem ed0 0xd8000" and then "quit". -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 13:58:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27487 for freebsd-stable-outgoing; Mon, 26 Oct 1998 13:58:01 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27456 for ; Mon, 26 Oct 1998 13:57:53 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id QAA03524; Mon, 26 Oct 1998 16:57:05 -0500 (EST) Received: from john.baldwinfamily.org (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id QAA30722; Mon, 26 Oct 1998 16:57:05 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199810261940.LAA00622@dingo.cdrom.com> Date: Mon, 26 Oct 1998 16:57:04 -0500 (EST) Reply-To: jobaldwi@vt.edu Organization: Virginia Tech From: John Baldwin To: Roger Hall Subject: Re: NIC Config Help Cc: FreeBSD-Stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 26-Oct-98 Mike Smith wrote: >> I have a box that was running 2.2.6 just fine (I installed over the >> internet - which I was very impressed with BTW). I received my 2.2.7 >> disk set with the Complete FreeBSD, tried to setup booting into X, and >> discovered the "magic number" issue. So I decided to create a new boot >> floppy, and re-install from disk 1. Now, my network card isn't found (or >> the kernel page faults). >> >> I'm using a 3Com Etherlink II/16 TP, which has a whole row of jumpers. >> 300 *original setting >> 310 >> 330 >> 350 >> 250 >> 280 >> 2A0 >> 2E0 >> >> DISABLE >> C8000 >> CC000 >> D8000 *original setting >> DC000 >> >> Previously, ed0 was found at 300, and I know the card was set to D8000, >> but I can't remember how that translates into "flags" in the visual >> config editor. > > It doesn't. Leave the flags alone. Set the port and memory addresses > to match the card. > >> Fatal trap 12: page fault while in kernel mode >> fault virtual address = 0xefc00000 > > You have the memory address set wrong; set it right. Roger, Make sure and set the memory address to 0xd80000 and not 0xd8000. (4 zero's) I've been bitten by that one, although with me it just didn't detect the cards instead of page faulting. - --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc As easy as 3.14159265358979323846264338327950288419716 -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNjTvmIjYza302vYpAQE9oAMAqDwQdZ+bMlYCyhxyHrgJU8x/hziB8rc/ OAtWIL9RT0dMdEcGuewCIbGkN841jQM0XP0qCupOkHh1/dD8YkKBVGiRj7v+wZ0d 36YWS/S0rP6LT5W48zhP9bhLouMa7ogy =qjOb -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 14:04:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28311 for freebsd-stable-outgoing; Mon, 26 Oct 1998 14:04:08 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28301 for ; Mon, 26 Oct 1998 14:04:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01407; Mon, 26 Oct 1998 14:03:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810262203.OAA01407@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: jobaldwi@vt.edu cc: Roger Hall , FreeBSD-Stable@FreeBSD.ORG Subject: Re: NIC Config Help In-reply-to: Your message of "Mon, 26 Oct 1998 16:57:04 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Oct 1998 14:03:04 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Previously, ed0 was found at 300, and I know the card was set to D8000, > >> but I can't remember how that translates into "flags" in the visual > >> config editor. > > > > It doesn't. Leave the flags alone. Set the port and memory addresses > > to match the card. > > > >> Fatal trap 12: page fault while in kernel mode > >> fault virtual address = 0xefc00000 > > > > You have the memory address set wrong; set it right. > > Roger, > > Make sure and set the memory address to 0xd80000 and not 0xd8000. (4 zero's) > I've been bitten by that one, although with me it just didn't detect the cards > instead of page faulting. Er, you're off by one. Make sure it's three zeroes, not two. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 15:44:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08939 for freebsd-stable-outgoing; Mon, 26 Oct 1998 15:44:59 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08930 for ; Mon, 26 Oct 1998 15:44:58 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA17457; Mon, 26 Oct 1998 15:44:11 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: rkw@Dataplex.NET cc: andrew@sour.cream.org, freebsd-stable@FreeBSD.ORG Subject: Re: CTM Release Generation - (Re: Stable and CTM) In-reply-to: Your message of "Mon, 26 Oct 1998 13:46:27 CST." <199810270005.SAA19664@shrimp.dataplex.net> Date: Mon, 26 Oct 1998 15:44:10 -0800 Message-ID: <17453.909445450@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, they abandoned CTM some years ago because of the lack of > those resources. I carried it on for a couple years, and now Mark has > taken over to chores. > > I assure you that the resources required anr NOT insignificant. It eats > up a lot of disk space, I/O time and CPU time. None of those have come > from freebsd.org in quite some time. Actually, I could in all honesty probably even get the computer and network resources together to do this here at freebsd.org (or one of our donor-ISP machines), the principal missing element being the manpower to care for it and keep it running (as jdp and others do for cvsupd, for example). Mark and Ulf seemed to have it in hand for awhile, though now it seems that Mark's back to building them in ZA or something without Ulf's ISP resources - I honestly have no idea. What I do know is that if someone came forward and said "I wish to be CTM meister - I will make sure it runs and be a point of contact in the times when it stops doing so if someone will give me the CPU and disk resources. CPU and disk resources are cheap(er) now - if a committed and able volunteer became available, I'm sure something could be worked out WRT that. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 16:46:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15929 for freebsd-stable-outgoing; Mon, 26 Oct 1998 16:46:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from papaya.mail.easynet.net (papaya.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA15906 for ; Mon, 26 Oct 1998 16:45:57 -0800 (PST) (envelope-from andrew@sour.cream.org) Received: (qmail 4371 invoked from network); 27 Oct 1998 00:44:50 -0000 Received: from boothman.easynet.co.uk (194.154.100.117) by papaya.mail.easynet.net with SMTP; 27 Oct 1998 00:44:50 -0000 Received: by Boothman.easynet.co.uk (VPOP3 - Unregistered) with SMTP; Tue, 27 Oct 1998 00:44:00 -0000 Message-Id: <3.0.5.32.19981027004400.007cb100@ice.cream.org> X-Sender: andrew@ice.cream.org X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 27 Oct 1998 00:44:00 +0000 To: "Jordan K. Hubbard" , rkw@Dataplex.NET From: Andrew Boothman Subject: Re: CTM Release Generation - (Re: Stable and CTM) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <17453.909445450@time.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Server: VPOP3 V1.2.0d Unregistered Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 15:44 26/10/98 -0800, Jordan K. Hubbard wrote: >Actually, I could in all honesty probably even get the computer and >network resources together to do this here at freebsd.org (or one of >our donor-ISP machines), the principal missing element being the >manpower to care for it and keep it running (as jdp and others do for >cvsupd, for example). Mark and Ulf seemed to have it in hand for >awhile, though now it seems that Mark's back to building them in ZA or >something without Ulf's ISP resources - I honestly have no idea. What >I do know is that if someone came forward and said "I wish to be CTM >meister - I will make sure it runs and be a point of contact in the >times when it stops doing so if someone will give me the CPU and disk >resources. CPU and disk resources are cheap(er) now - if a committed >and able volunteer became available, I'm sure something could be >worked out WRT that. I would like nothing more then to step forward and say "ME!", believe me. I actually would enjoy taking up a role such as this and giving something back to FreeBSD. Two things stop me from doing so. Firstly, I don't think I have the technical experience to "care for it and keep it running". I've only be using FreeBSD for a short while, with little unix experience before that. I could learn, but that's no instant solution. Secondly, I'm in a _really_ important year of my education. You know the "these exams determine your path for the rest of your life" type year. I don't have a tremendous amount of spare time, and I couldn't take on something like this without knowing how much of a pull on my time it would make. I could perhaps take up half-a-role and share responsibility with someone else. Is anyone else interested? P.S. Tom Rush has sent me a script which he has written which may assist in creating the release deltas. Contact him or myself if it might be of use. -- Andrew Boothman http://sour.cream.org PGP Key Available From Public Servers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 22:19:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15078 for freebsd-stable-outgoing; Mon, 26 Oct 1998 22:19:27 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15073 for ; Mon, 26 Oct 1998 22:19:19 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA00563; Tue, 27 Oct 1998 08:18:24 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810270618.IAA00563@gratis.grondar.za> To: "Jordan K. Hubbard" cc: freebsd-stable@FreeBSD.ORG Subject: Re: CTM Release Generation - (Re: Stable and CTM) In-Reply-To: Your message of " Mon, 26 Oct 1998 15:44:10 PST." <17453.909445450@time.cdrom.com> References: <17453.909445450@time.cdrom.com> Date: Tue, 27 Oct 1998 08:18:23 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > Actually, I could in all honesty probably even get the computer and > network resources together to do this here at freebsd.org (or one of > our donor-ISP machines), the principal missing element being the > manpower to care for it and keep it running (as jdp and others do for > cvsupd, for example). Mark and Ulf seemed to have it in hand for > awhile, though now it seems that Mark's back to building them in ZA or > something without Ulf's ISP resources - I honestly have no idea. What Ulf's machine, Mark doing the babysitting. Short on diskspace, but otherwise works a dream. No CTM meister needed, just a few more facilities :-). > I do know is that if someone came forward and said "I wish to be CTM > meister - I will make sure it runs and be a point of contact in the > times when it stops doing so if someone will give me the CPU and disk > resources. CPU and disk resources are cheap(er) now - if a committed > and able volunteer became available, I'm sure something could be > worked out WRT that. If the CVS tree was CTM'ed before being put onto the CD's (like you did once-or-twice), it would make my life _vastly_ easier, and this whole argument moot. I could even build you a special CVS CTM /ab initio/ delta for the purposes :-). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Oct 26 22:51:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18477 for freebsd-stable-outgoing; Mon, 26 Oct 1998 22:51:25 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18472 for ; Mon, 26 Oct 1998 22:51:24 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id WAA19024; Mon, 26 Oct 1998 22:50:43 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Mark Murray cc: freebsd-stable@FreeBSD.ORG Subject: Re: CTM Release Generation - (Re: Stable and CTM) In-reply-to: Your message of "Tue, 27 Oct 1998 08:18:23 +0200." <199810270618.IAA00563@gratis.grondar.za> Date: Mon, 26 Oct 1998 22:50:42 -0800 Message-ID: <19020.909471042@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ulf's machine, Mark doing the babysitting. Short on diskspace, but > otherwise works a dream. No CTM meister needed, just a few more > facilities :-). OK, just checking. As usual, I was unsure of the CTM situation. :) > If the CVS tree was CTM'ed before being put onto the CD's (like you > did once-or-twice), it would make my life _vastly_ easier, and this > whole argument moot. I could even build you a special CVS CTM /ab > initio/ delta for the purposes :-). Hmmmm. OK, let's talk about this when the next CD comes up - we may be able to work something out. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 27 20:50:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18649 for freebsd-stable-outgoing; Tue, 27 Oct 1998 20:50:21 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18641 for ; Tue, 27 Oct 1998 20:50:16 -0800 (PST) (envelope-from bvandepe@gsoft.com.au) Received: from gsoft.com.au (obtuse.gsoft.com.au [203.38.152.98]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id PAA23781; Wed, 28 Oct 1998 15:19:36 +1030 (CST) Message-ID: <3636A25F.A9EBE88C@gsoft.com.au> Date: Wed, 28 Oct 1998 15:19:35 +1030 From: Brenton Vandepeer Organization: Genesis Software, Pty. Ltd. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-BETA i386) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Excessive memory consumption with gnuplot Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG G'day. I've been observing some curious behaviour from gnuplot under 2.2.7-STABLE. Recent responses from gnuplot gnurus seems to indicate that the problem may be OS specific, rather than strictly gnuplot's fault. (Not being a native gnuplot user I wasn't sure what to expect from the package at first.) Here's the story (see kern/8473): Invoking gnuplot 3.5 under FreeBSD 2.2.7-STABLE causes excessive consumption of memory when displaying data. The problem seems to occur above some threshold in input data file size. For example, input data files above about 1 Mb sometimes give rise to 150 - 200 Mb of swap being consumed. One data file tested with a size of 3 Mb caused ~400 Mb of swap to be consumed. This problem is not repeatable under 3.0-RELEASE, or another OS tested (linex 2.0.0) Here's a brief description of the environment: 2.2.7-STABLE 22/09/98 233 MHz Pentium 32 Mb RAM 630 Mb swap gnuplot 3.5 PL340 I have data files available on request for anyone foolhardy enough to test... Any and all help appreciated. -- Brenton Vandepeer, Genesis Software, Pty Ltd. email: bvandepe@gsoft.com.au Adelaide, Australia. WWW: http://www.gsoft.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Oct 27 22:32:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24760 for freebsd-stable-outgoing; Tue, 27 Oct 1998 22:32:56 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (castles237.castles.com [208.214.165.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24754 for ; Tue, 27 Oct 1998 22:32:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA00939; Tue, 27 Oct 1998 22:31:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810280631.WAA00939@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brenton Vandepeer cc: freebsd-stable@FreeBSD.ORG Subject: Re: Excessive memory consumption with gnuplot In-reply-to: Your message of "Wed, 28 Oct 1998 15:19:35 +1030." <3636A25F.A9EBE88C@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Oct 1998 22:31:46 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here's the story (see kern/8473): > > Invoking gnuplot 3.5 under FreeBSD 2.2.7-STABLE causes excessive > consumption of memory when displaying data. The problem seems to > occur above some threshold in input data file size. For example, > input data files above about 1 Mb sometimes give rise to 150 - > 200 Mb of swap being consumed. One data file tested with a size > of 3 Mb caused ~400 Mb of swap to be consumed. This problem is not > repeatable under 3.0-RELEASE, or another OS tested (linex 2.0.0) Which malloc is/are your gnuplot binaries linked against? Use ldd `which gnuplot` to get a library listing (presuming it's not linked statically). If you take the binary from the 2.2 system and run it on the 3.0 system, does it exhibit the 2.2 or 3.0 behavior? Did you build the gnuplot binaries from the ports collection or were they package installs? Which version(s) of gnuplot are you running? The behaviour you're describing is typical of pathalogically bad malloc() interaction; it's fairly uncommon to see this with the FreeBSD malloc, which is why I ask which one(s) you're using. (There haven't been significant changes to the libc malloc for over a year now.) The contents of /proc//map would also be interesting to see (where is the process ID of the offending gnuplot process). How's the brewing going? Made up for the dent you must have made a few weeks back? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 00:33:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05423 for freebsd-stable-outgoing; Wed, 28 Oct 1998 00:33:17 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tibatong.ihf.rwth-aachen.de (tibatong.ihf.RWTH-Aachen.DE [134.130.90.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05411 for ; Wed, 28 Oct 1998 00:33:06 -0800 (PST) (envelope-from tg@tibatong.ihf.rwth-aachen.de) Received: (from tg@localhost) by tibatong.ihf.rwth-aachen.de (8.8.8/8.8.8) id JAA21288; Wed, 28 Oct 1998 09:32:39 +0100 (CET) (envelope-from tg) To: freebsd-stable@FreeBSD.ORG Subject: How do I debug this? Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=ISO-8859-1 From: Thomas Gellekum Date: 28 Oct 1998 09:32:39 +0100 Message-ID: <87af2hccig.fsf@tibatong.ihf.rwth-aachen.de> Lines: 71 X-Mailer: Gnus v5.6.34/XEmacs 20.4 - "Emerald" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id AAA05419 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Moin, I have a problem debugging the latest windowmaker. It dumps core on receiving SIGBUS before executing main(). A ktrace excerpt looks like: [...] 9572 wmaker CALL open(0x20094000,0,0) 9572 wmaker NAMI "/usr/X11R6/lib/libX11.so.6.1" 9572 wmaker RET open 4 9572 wmaker CALL read(0x4,0xefbfd8b4,0x20) 9572 wmaker GIO fd 4 read 32 bytes "Ì\0\M^FÀ\0À\b\0\0P\0\0\0\0\0\0L×\0\0 \0\0\0\0\0\0\0\0\0\0\0" 9572 wmaker RET read 32/0x20 9572 wmaker CALL mmap(0,0x91000,0x5,0x2,0x4,0,0,0) 9572 wmaker RET mmap 538202112/0x20145000 9572 wmaker CALL close(0x4) 9572 wmaker RET close 0 9572 wmaker CALL mprotect(0x201d1000,0x5000,0x7) 9572 wmaker RET mprotect 0 9572 wmaker CALL mmap(0x201d6000,0,0x7,0x1012,0xffffffff,0,0,0) 9572 wmaker RET mmap 538796032/0x201d6000 9572 wmaker CALL stat(0x200998c3,0xefbfd8ac) 9572 wmaker NAMI "/usr/lib/libm.so.2.0" 9572 wmaker RET stat 0 9572 wmaker CALL stat(0x2009900b,0xefbfd8ac) 9572 wmaker NAMI "/usr/lib/libc.so.3.1" 9572 wmaker RET stat 0 9572 wmaker CALL stat(0x200920a0,0xefbfd8d4) 9572 wmaker NAMI "/usr/lib/libc.so.3.1" 9572 wmaker RET stat 0 9572 wmaker CALL open(0x200920a0,0,0) 9572 wmaker NAMI "/usr/lib/libc.so.3.1" 9572 wmaker RET open 4 9572 wmaker CALL read(0x4,0xefbfd8b4,0x20) 9572 wmaker GIO fd 4 read 32 bytes "Ì\0\M^FÀ\0Ð\^E\0\0@\0\0TÌ\0\0\M^\3\0\0 \0\0\0\0\0\0\0\0\0\0\0" 9572 wmaker RET read 32/0x20 9572 wmaker CALL mmap(0,0x6dc54,0x5,0x2,0x4,0,0,0) 9572 wmaker RET mmap 538796032/0x201d6000 9572 wmaker CALL close(0x4) 9572 wmaker RET close 0 9572 wmaker CALL mprotect(0x20233000,0x4000,0x7) 9572 wmaker RET mprotect 0 9572 wmaker CALL mmap(0x20237000,0xcc54,0x7,0x1012,0xffffffff,0,0,0) 9572 wmaker RET mmap 539193344/0x20237000 9572 wmaker CSW stop kernel 9572 wmaker CSW resume kernel 9572 wmaker CSW stop kernel 9572 wmaker CSW resume kernel 9572 wmaker CSW stop kernel 9572 wmaker CSW resume kernel 9572 wmaker CSW stop kernel 9572 wmaker CSW resume kernel 9572 wmaker CSW stop kernel 9572 wmaker CSW resume kernel 9572 wmaker CSW stop kernel 9572 wmaker CSW resume kernel 9572 wmaker CSW stop kernel 9572 wmaker CSW resume kernel 9572 wmaker PSIG SIGBUS SIG_DFL 9572 wmaker NAMI "wmaker.core" [...] The core dump doesn't give (me) any useful information. Any ideas? tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 01:02:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06995 for freebsd-stable-outgoing; Wed, 28 Oct 1998 01:02:21 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dart.sr.se (dart.SR.SE [193.12.91.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06990; Wed, 28 Oct 1998 01:02:19 -0800 (PST) (envelope-from gunnar@pluto.sr.se) Received: from honken.sr.se ([134.25.128.27]) by dart.sr.se (8.9.1/8.9.0) with ESMTP id KAA27912; Wed, 28 Oct 1998 10:01:40 +0100 (MET) Received: from pluto.sr.se (pluto.SR.SE [134.25.193.91]) by honken.sr.se (8.7.5/8.7.3) with ESMTP id KAA22211; Wed, 28 Oct 1998 10:01:39 +0100 (MET) Received: (from gunnar@localhost) by pluto.sr.se (8.8.8/8.8.8) id KAA12492; Wed, 28 Oct 1998 10:01:39 +0100 (CET) (envelope-from gunnar) Message-ID: <19981028100139.B12354@sr.se> Date: Wed, 28 Oct 1998 10:01:39 +0100 From: Gunnar Flygt To: FreeBSD Questions Cc: freebsd-stable@FreeBSD.ORG Subject: The new release and ports Reply-To: flygt@sr.se Mail-Followup-To: FreeBSD Questions , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How come that several ports now (in the 3.0-RELEASE) are looking for a lib that obviously has to do with kerberos? I don't want kerberos, so I haven't installed it. The error message goes: gunnar@voyager$ xv /usr/libexec/ld-elf.so.1: Shared object "libkrb.so.3" not found and I guess that libkrb.so.3 referres to kerberos? Or? There are others that have put similar questions without answer. I guess someone must know. -- __o regards, Gunnar ---_ \<,_ email: flygt@sr.se ---- (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 01:55:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11006 for freebsd-stable-outgoing; Wed, 28 Oct 1998 01:55:12 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10998; Wed, 28 Oct 1998 01:55:07 -0800 (PST) (envelope-from grg@philol.msu.ru) Received: from localhost (grg@localhost) by isabase.philol.msu.ru (8.9.1/8.9.1) with ESMTP id NAA03692; Wed, 28 Oct 1998 13:53:42 +0300 (MSK) (envelope-from grg@philol.msu.ru) X-Authentication-Warning: isabase.philol.msu.ru: grg owned process doing -bs Date: Wed, 28 Oct 1998 13:53:41 +0300 (MSK) From: Grigoriy Strokin To: flygt@sr.se cc: FreeBSD Questions , freebsd-stable@FreeBSD.ORG Subject: Re: The new release and ports In-Reply-To: <19981028100139.B12354@sr.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998, Gunnar Flygt wrote: > How come that several ports now (in the 3.0-RELEASE) are looking for a > lib that obviously has to do with kerberos? I don't want kerberos, so I > haven't installed it. > > The error message goes: > > gunnar@voyager$ xv > /usr/libexec/ld-elf.so.1: Shared object "libkrb.so.3" not found > > and I guess that libkrb.so.3 referres to kerberos? Or? > > There are others that have put similar questions without answer. I guess > someone must know. > Yes, yes, yes, I write letters to via send-pr, I write to questions@freebsd.org, no responses!!!!!!!!!!!1 Here is one of my previous letters. Hello, I have several problems with ports and packages in new 3.0 relase. 1) Several packages for X, such as fvwm2, xanim, xautolock, xv, xli do not run on my system, because they require libkrb.so, and I don't have Kerberos installed. This problems is solved by using the corresponding versions of those programs from ports and compiling them. However, I am interesting in whether such a situation will ever change. 2) Several ports from FreeBSD/ports-3.0 don't compile: they make gives a message this ports is broken for ELF and exit. I have no solution to this problem. The examples of ports I can't compile are: 1) gcl-2.2.2 GNU Common Lisp 2) kdelibs-1.0 Support libraries for the KDE integrated X11 desktop Grigoriy Strokin surprised FreeBSD user. ---------------------------------------------- P.S. Now I now how to deal with those broken packages: just symlink any valid sharead lib to libkrb and libdes: cd /usr/lib; ln -s libipx.so.2 libkrb.so.3; ln -s libipx.so.2 libdes.so.3 === Grigoriy Strokin, Lomonosov University (MGU), Moscow === === contact info: http://isabase.philol.msu.ru/~grg/ === To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 04:02:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA22005 for freebsd-stable-outgoing; Wed, 28 Oct 1998 04:02:24 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA21828 for ; Wed, 28 Oct 1998 04:02:03 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id KAA10620; Wed, 28 Oct 1998 10:01:00 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199810281201.KAA10620@roma.coe.ufrj.br> Subject: Next -RELEASE suggestion To: stable@FreeBSD.ORG Date: Wed, 28 Oct 1998 10:01:00 -0200 (EDT) Cc: ams@jonny.eng.br (Ana Maria Silva) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I didn't know which list would be better suited for this. I sent to -stable becasue the problem happened with the 2.2.7 CD. Is it possible to use Joliet extensions in the future -RELEASE CDs ? It's incredibly easy to do this with mkhybrid (already in the ports), and it would help a lot to copy files with long file names to Win95. Yes, yes, I know that all distribution files are already in a DOS friendly format, but the packages are not. :) Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 04:06:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23826 for freebsd-stable-outgoing; Wed, 28 Oct 1998 04:06:24 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from thor.KanServu.ca (thor.KanServU.ca [205.206.200.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23821 for ; Wed, 28 Oct 1998 04:06:22 -0800 (PST) (envelope-from sebulgin@kanservu.ca) Received: from thor.kanservu.ca (ts9p16.bmts.com [204.191.101.86]) by thor.KanServu.ca (8.8.5/8.8.5) with SMTP id GAA01652 for ; Wed, 28 Oct 1998 06:54:34 -0500 (EST) Message-Id: <3.0.6.32.19980827190421.0079b930@kanservu.ca> X-Sender: sebulgin@kanservu.ca (Unverified) X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Thu, 27 Aug 1998 19:04:21 -0700 To: FreeBSD-stable@FreeBSD.ORG From: Scott Bulgin Subject: Subscribe Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 04:16:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA24238 for freebsd-stable-outgoing; Wed, 28 Oct 1998 04:16:07 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA24229; Wed, 28 Oct 1998 04:16:02 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id KAA10744; Wed, 28 Oct 1998 10:09:48 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199810281209.KAA10744@roma.coe.ufrj.br> Subject: Re: The new release and ports In-Reply-To: from Grigoriy Strokin at "Oct 28, 98 01:53:41 pm" To: grg@philol.msu.ru (Grigoriy Strokin) Date: Wed, 28 Oct 1998 10:09:48 -0200 (EDT) Cc: flygt@sr.se, questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Grigoriy Strokin) // 2) Several ports from FreeBSD/ports-3.0 don't compile: // they make gives a message this ports is broken for ELF and exit. This is normal. 3.0 was the very first ELF release, and they did not have time to adapt and test every port in an ELF environment. As a consequence, they were marked broken. If you really need a system working, use -stable (2.2.7 or any later 2.2-snap). Thanks Justin, at least we now know which ones work or not. // P.S. Now I now how to deal with those broken [libkrb] packages: // just symlink any valid sharead lib to libkrb and // libdes: // // cd /usr/lib; ln -s libipx.so.2 libkrb.so.3; ln -s libipx.so.2 libdes.so.3 Ouch. :) Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 05:17:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28310 for freebsd-stable-outgoing; Wed, 28 Oct 1998 05:17:42 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28238; Wed, 28 Oct 1998 05:17:38 -0800 (PST) (envelope-from grg@philol.msu.ru) Received: from localhost (grg@localhost) by isabase.philol.msu.ru (8.9.1/8.9.1) with ESMTP id RAA04833; Wed, 28 Oct 1998 17:12:21 +0300 (MSK) (envelope-from grg@philol.msu.ru) X-Authentication-Warning: isabase.philol.msu.ru: grg owned process doing -bs Date: Wed, 28 Oct 1998 17:12:21 +0300 (MSK) From: Grigoriy Strokin To: Joao Carlos Mendes Luis cc: flygt@sr.se, questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: The new release and ports In-Reply-To: <199810281209.KAA10744@roma.coe.ufrj.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998, Joao Carlos Mendes Luis wrote: > #define quoting(Grigoriy Strokin) > // 2) Several ports from FreeBSD/ports-3.0 don't compile: > // they make gives a message this ports is broken for ELF and exit. > > This is normal. 3.0 was the very first ELF release, and they did not > have time to adapt and test every port in an ELF environment. As a > consequence, they were marked broken. If you really need a system > working, use -stable (2.2.7 or any later 2.2-snap). Normal? You forget, however, that I don't use 3.0 SNAP or 3.0 CURRENT, and not even 3.0 BETA, I use 3.0 *RELEASE* :) > > // P.S. Now I now how to deal with those broken [libkrb] packages: > // just symlink any valid sharead lib to libkrb and > // libdes: > // > // cd /usr/lib; ln -s libipx.so.2 libkrb.so.3; ln -s libipx.so.2 libdes.so.3 > > Ouch. :) === Grigoriy Strokin, Lomonosov University (MGU), Moscow === === contact info: http://isabase.philol.msu.ru/~grg/ === To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 06:36:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05029 for freebsd-stable-outgoing; Wed, 28 Oct 1998 06:36:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA04975 for ; Wed, 28 Oct 1998 06:35:53 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA05892; Wed, 28 Oct 1998 13:30:36 +0100 From: Luigi Rizzo Message-Id: <199810281230.NAA05892@labinfo.iet.unipi.it> Subject: Re: Next -RELEASE suggestion To: jonny@jonny.eng.br (Joao Carlos Mendes Luis) Date: Wed, 28 Oct 1998 13:30:35 +0100 (MET) Cc: stable@FreeBSD.ORG, ams@jonny.eng.br In-Reply-To: <199810281201.KAA10620@roma.coe.ufrj.br> from "Joao Carlos Mendes Luis" at Oct 28, 98 10:00:41 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I didn't know which list would be better suited for this. I sent > to -stable becasue the problem happened with the 2.2.7 CD. > > Is it possible to use Joliet extensions in the future -RELEASE > CDs ? It's incredibly easy to do this with mkhybrid (already in the you mean both joliet and rockridge ? otherwise you'd have problems under FreeBSD because i think the cd9660 filesystem does not understand joliet luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 07:35:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11155 for freebsd-stable-outgoing; Wed, 28 Oct 1998 07:35:41 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11136 for ; Wed, 28 Oct 1998 07:35:22 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id NAA13248; Wed, 28 Oct 1998 13:32:39 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199810281532.NAA13248@roma.coe.ufrj.br> Subject: Re: Next -RELEASE suggestion In-Reply-To: <199810281230.NAA05892@labinfo.iet.unipi.it> from Luigi Rizzo at "Oct 28, 98 01:30:35 pm" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Wed, 28 Oct 1998 13:32:39 -0200 (EDT) Cc: jonny@jonny.eng.br, stable@FreeBSD.ORG, ams@jonny.eng.br X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Luigi Rizzo) // > I didn't know which list would be better suited for this. I sent // > to -stable becasue the problem happened with the 2.2.7 CD. // > // > Is it possible to use Joliet extensions in the future -RELEASE // > CDs ? It's incredibly easy to do this with mkhybrid (already in the // // you mean both joliet and rockridge ? otherwise you'd have problems // under FreeBSD because i think the cd9660 filesystem does not understand // joliet Of course, both. :) Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 07:37:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11300 for freebsd-stable-outgoing; Wed, 28 Oct 1998 07:37:41 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11292; Wed, 28 Oct 1998 07:37:33 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id NAA13307; Wed, 28 Oct 1998 13:35:24 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199810281535.NAA13307@roma.coe.ufrj.br> Subject: Re: The new release and ports In-Reply-To: from Grigoriy Strokin at "Oct 28, 98 05:12:21 pm" To: grg@philol.msu.ru (Grigoriy Strokin) Date: Wed, 28 Oct 1998 13:35:24 -0200 (EDT) Cc: jonny@jonny.eng.br, flygt@sr.se, questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Grigoriy Strokin) // On Wed, 28 Oct 1998, Joao Carlos Mendes Luis wrote: // > #define quoting(Grigoriy Strokin) // > // 2) Several ports from FreeBSD/ports-3.0 don't compile: // > // they make gives a message this ports is broken for ELF and exit. // > // > This is normal. 3.0 was the very first ELF release, and they did not // > have time to adapt and test every port in an ELF environment. As a // > consequence, they were marked broken. If you really need a system // > working, use -stable (2.2.7 or any later 2.2-snap). // // Normal? You forget, however, that I don't use // 3.0 SNAP or 3.0 CURRENT, and not even 3.0 BETA, // I use 3.0 *RELEASE* :) Yes, it's normal on 3.0-RELEASE. :) Remember that 3.0 is not yet classified as -stable, and still has lots of problems to be solved before the next release. That's why we'll have a 2.2.8-RELEASE before this year ends. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 09:56:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23673 for freebsd-stable-outgoing; Wed, 28 Oct 1998 09:53:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (castles337.castles.com [208.214.167.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23665; Wed, 28 Oct 1998 09:53:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA03837; Wed, 28 Oct 1998 09:50:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810281750.JAA03837@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Grigoriy Strokin cc: Joao Carlos Mendes Luis , flygt@sr.se, questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: The new release and ports In-reply-to: Your message of "Wed, 28 Oct 1998 17:12:21 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 09:50:42 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 28 Oct 1998, Joao Carlos Mendes Luis wrote: > > > #define quoting(Grigoriy Strokin) > > // 2) Several ports from FreeBSD/ports-3.0 don't compile: > > // they make gives a message this ports is broken for ELF and exit. > > > > This is normal. 3.0 was the very first ELF release, and they did not > > have time to adapt and test every port in an ELF environment. As a > > consequence, they were marked broken. If you really need a system > > working, use -stable (2.2.7 or any later 2.2-snap). > > Normal? You forget, however, that I don't use > 3.0 SNAP or 3.0 CURRENT, and not even 3.0 BETA, > I use 3.0 *RELEASE* :) Yes, normal. Read the release notes. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 10:01:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24388 for freebsd-stable-outgoing; Wed, 28 Oct 1998 10:01:08 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24377 for ; Wed, 28 Oct 1998 10:01:00 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id TAA00477 for stable@FreeBSD.ORG; Wed, 28 Oct 1998 19:00:05 +0100 (CET) Message-ID: <19981028190005.A426@foobar.franken.de> Date: Wed, 28 Oct 1998 19:00:05 +0100 From: Harold Gutch To: stable@FreeBSD.ORG Subject: HD problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, last night all of a sudden my box halted, without panicing or rebooting. After pressing the reset-key, it came back up, and didn't manage to finish fscking a partition on an IDE-disk of mine. Phases 1-4 of fsck passed as normal, but then I got the following errormessages: ** Phase 5 - Check Cyl Groups wd1: interrupt timeout: wd1: status 58 error 0 wd1: interrupt timeout: wd1: status 50 error 1 the last 4 lines being repeated every 30s or so. At this point fsck seemed to repeatedly try to access the same part of the disk over and over again without ever timeouting or stopping. I watched this for about 10 minutes, then rebooted again, booted in singleuser-mode, removed the appropriate entry from my /etc/fstab (luckily this happened on no 'vital' disk) and booted again. bad144 -s -v wd1 behaved very similar to fsck, from the sounds the disk made, I would say that it tried to access one part of the disk over and over again. I haven't freed up enough space to try dd'ing the disk into a file, then mounting it via a vnode, to at least partially save some data, but I hope to achieve this later on tonight. Is there anything else I'm able to do to fix the disk (at least to get to know which parts of it are broken, mark the bad sectors and then do a fsck over the rest or something alike) or can I just hope that the dd will save some of the data ? -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 12:08:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11113 for freebsd-stable-outgoing; Wed, 28 Oct 1998 12:08:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11093 for ; Wed, 28 Oct 1998 12:08:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00390; Wed, 28 Oct 1998 12:06:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810282006.MAA00390@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Harold Gutch cc: stable@FreeBSD.ORG Subject: Re: HD problems In-reply-to: Your message of "Wed, 28 Oct 1998 19:00:05 +0100." <19981028190005.A426@foobar.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 12:06:17 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Your disk is taking longer to handle the error than we allow it to. Your best bet at this point is probably to mount the partition forced readonly (mount -f -o ro), copy everything meaningful off the the partition, then dd zeroes over it to give the drive a chance to remap the sector(s) in question. > > last night all of a sudden my box halted, without panicing or > rebooting. > After pressing the reset-key, it came back up, and didn't manage > to finish fscking a partition on an IDE-disk of mine. Phases 1-4 > of fsck passed as normal, but then I got the following > errormessages: > > ** Phase 5 - Check Cyl Groups > wd1: interrupt timeout: > wd1: status 58 error 0 > wd1: interrupt timeout: > wd1: status 50 error 1 > > the last 4 lines being repeated every 30s or so. > > At this point fsck seemed to repeatedly try to access the same > part of the disk over and over again without ever timeouting or > stopping. > I watched this for about 10 minutes, then rebooted again, booted > in singleuser-mode, removed the appropriate entry from my > /etc/fstab (luckily this happened on no 'vital' disk) and booted > again. > > bad144 -s -v wd1 behaved very similar to fsck, from the sounds the > disk made, I would say that it tried to access one part of the > disk over and over again. > I haven't freed up enough space to try dd'ing the disk into a > file, then mounting it via a vnode, to at least partially save > some data, but I hope to achieve this later on tonight. > Is there anything else I'm able to do to fix the disk (at least > to get to know which parts of it are broken, mark the bad sectors > and then do a fsck over the rest or something alike) or can I > just hope that the dd will save some of the data ? > > -- > bye, logix > > Sleep is an abstinence syndrome wich occurs due to lack of caffein. > Wed Mar 4 04:53:33 CET 1998 #unix, ircnet > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 14:43:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26970 for freebsd-stable-outgoing; Wed, 28 Oct 1998 14:43:56 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26953 for ; Wed, 28 Oct 1998 14:43:24 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id XAA00955; Wed, 28 Oct 1998 23:41:41 +0100 (CET) Message-ID: <19981028234141.A913@foobar.franken.de> Date: Wed, 28 Oct 1998 23:41:41 +0100 From: Harold Gutch To: Mike Smith Cc: stable@FreeBSD.ORG Subject: Re: HD problems References: <19981028190005.A426@foobar.franken.de> <199810282006.MAA00390@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810282006.MAA00390@dingo.cdrom.com>; from Mike Smith on Wed, Oct 28, 1998 at 12:06:17PM -0800 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 28, 1998 at 12:06:17PM -0800, Mike Smith wrote: > Your disk is taking longer to handle the error than we allow it to. Your > best bet at this point is probably to mount the partition forced > readonly (mount -f -o ro), copy everything meaningful off the the > partition, then dd zeroes over it to give the drive a chance to remap > the sector(s) in question. > Is there an easy way to set the timeout-values higher, like patch a couple of lines in the wd-driver to at least give me enough time to backup the whole thing, and then nuke the data that currently still is on it ? I hope this idea isn't foredoomed due to some other reason. If not, I'll try mounting it readonly and then go on... -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 14:49:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27673 for freebsd-stable-outgoing; Wed, 28 Oct 1998 14:49:45 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27661 for ; Wed, 28 Oct 1998 14:49:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00727; Wed, 28 Oct 1998 14:47:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810282247.OAA00727@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Harold Gutch cc: Mike Smith , stable@FreeBSD.ORG Subject: Re: HD problems In-reply-to: Your message of "Wed, 28 Oct 1998 23:41:41 +0100." <19981028234141.A913@foobar.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 14:47:27 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Oct 28, 1998 at 12:06:17PM -0800, Mike Smith wrote: > > Your disk is taking longer to handle the error than we allow it to. Your > > best bet at this point is probably to mount the partition forced > > readonly (mount -f -o ro), copy everything meaningful off the the > > partition, then dd zeroes over it to give the drive a chance to remap > > the sector(s) in question. > > > Is there an easy way to set the timeout-values higher, like patch > a couple of lines in the wd-driver to at least give me enough > time to backup the whole thing, and then nuke the data that currently > still is on it ? > I hope this idea isn't foredoomed due to some other reason. > If not, I'll try mounting it readonly and then go on... Yup. Look for the code that looks like this: /* * Schedule wdtimeout() to wake up after a few seconds. Retrying * unmarked bad blocks can take 3 seconds! Then it is not good that * we retry 5 times. * * On the first try, we give it 10 seconds, for drives that may need * to spin up. * * XXX wdtimeout() doesn't increment the error count so we may loop * forever. More seriously, the loop isn't forever but causes a * crash. * * TODO fix b_resid bug elsewhere (fd.c....). Fix short but positive * counts being discarded after there is an error (in physio I * think). Discarding them would be OK if the (special) file offset * was not advanced. */ if (wdtab[ctrlr].b_errcnt == 0) du->dk_timeout = 1 + 10; else du->dk_timeout = 1 + 3; and change the 10 to 30 or so. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 17:58:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09335 for freebsd-stable-outgoing; Wed, 28 Oct 1998 17:58:25 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09321 for ; Wed, 28 Oct 1998 17:58:18 -0800 (PST) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.9.1/8.9.1) id JAA20221; Thu, 29 Oct 1998 09:57:17 +0800 (GMT) Date: Thu, 29 Oct 1998 09:57:17 +0800 (GMT) From: Michael Robinson Message-Id: <199810290157.JAA20221@public.bta.net.cn> To: logix@foobar.franken.de, stable@FreeBSD.ORG Subject: Re: HD problems Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Harold Gutch : >but then I got the following errormessages: > > ** Phase 5 - Check Cyl Groups > wd1: interrupt timeout: > wd1: status 58 error 0 > wd1: interrupt timeout: > wd1: status 50 error 1 > > the last 4 lines being repeated every 30s or so. This is a known deficiency in the wd driver. Check the mailing list archives for this error message. There was discussion a few months ago about how to increase the interrupt timeout in the driver code to give the disk enough time to report a read error. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Oct 28 23:39:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15615 for freebsd-stable-outgoing; Wed, 28 Oct 1998 23:39:09 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.nitek.ru (nitek.east.ru [195.170.63.240]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15589; Wed, 28 Oct 1998 23:38:39 -0800 (PST) (envelope-from igor@nitek.ru) Received: from igor (igor.nitek.ru [192.168.1.10]) by ns.nitek.ru (8.8.4/8.8.5) with ESMTP id KAA05021; Thu, 29 Oct 1998 10:37:39 +0300 (MSK) Message-Id: <199810290737.KAA05021@ns.nitek.ru> From: "Igor Sysoev" To: " Cc: Subject: Fatal bug in 2.2.5R's lpd Date: Thu, 29 Oct 1998 10:42:35 +0300 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, some time ago I found that 'ct' doesn't work at all at least in lpq. I'd searched mail lists and found mail from Joerg Wunsch: ---------- Date: Fri, 7 Nov 1997 23:39:01 -0800 (PST) From: Joerg Wunsch To: announce@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Fatal bug in 2.2.5R's lpd Message-ID: <199711080739.XAA29381@freefall.freebsd.org> When merging the new `ct' printcap functionality into 2.2-stable right before 2.2.5-RELEASE was due, it's now apparent that I didn't test it enough before. :-( I've introduced a fatal bug that causes all the lpd children sending jobs to remote printers to be killed after the `ct' timeout, even in case the connection came up properly. For small jobs, you won't notice this immediately (the default timeout is 120 seconds, and modern printers can print a lot within this time), but large jobs will ultimately be aborted then. Sorry for the inconvenience. For those of you who do need to operate on remote printers, please either do upgrade to the latest 2.2-stable, or apply the patch below, rebuild and reinstall your lpd. Sorry again, Joerg ---------------- When I try to list queue on turned off remote LaserJet with JetDirect card lpq hangs up for 75 seconds nevertheless ct value I set or even default ct value - 120 seconds. I found it when Windows 95 froze on same time while trying to print or list queue on this printer connected through Samba when printer was turned off. I tried it on FreeBSD 2.2.7. To test it you can simply make dummy remote printer entry in printcap like me: lj|LaserJet 4 with JetDirect:\ :lp=:\ :rm=lj:\ :rq=raw:\ :sd=/var/spool/output/lj504:\ :sh:ct=30:\ :lf=/var/log/lpd-errs: and try to lpq it. with best regards, Igor Sysoev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 06:22:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28082 for freebsd-stable-outgoing; Thu, 29 Oct 1998 06:22:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gatekeeper.salestech.com (gatekeeper.salestech.com [198.153.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28068 for ; Thu, 29 Oct 1998 06:22:53 -0800 (PST) (envelope-from MillikS@salestech.com) Received: from [162.44.80.67] by gatekeeper.salestech.com for id JAA24214; Thu Oct 29 09:22:50 1998 Received: by STIUSATLCX1.salestech.com with Internet Mail Service (5.5.1960.3) id ; Thu, 29 Oct 1998 09:22:49 -0500 Message-ID: <7B62F9E0DD56D111AADB006097A52FCC0465E1@STIUSATLCX1.salestech.com> Subject: Question about Ports Errors Date: Thu, 29 Oct 1998 09:22:48 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain To: "'freebsd-stable@freebsd.org'" From: "Milliken, Scott" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been tracking this list for about a month looking for a message related to this, so if it came up earlier and was already answered, I apologize. I run several machines with 2.2.7-RELEASE and have been having more and more trouble lately with certain ports. Specifically, today, the problems are with /usr/ports/graphics/xpm and /usr/ports/graphics/giflib. Every time I see the same problem - the build errors out with an Error 1 due to a "Malformed conditional" on a line usually like: .if $(({$PORTOBJFORMAT} == "elf" )) I've looked at the code and can get by it if I modify the Makefile so that the condition is commented out and simply execute the steps related to the FALSE condition here (since 2.2.7 isn't elf, of course). However, I would think that someone wrote the code like this for a reason - to support both 2.2.7 and 3.0 with the same ports tree. What package do I need to install (or remake) in order to support the given syntax in the Makefile? Thanks, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 08:09:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10906 for freebsd-stable-outgoing; Thu, 29 Oct 1998 08:09:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sussie.datadesign.se (ns.datadesign.se [194.23.109.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10895 for ; Thu, 29 Oct 1998 08:09:54 -0800 (PST) (envelope-from kaj@interbizz.se) Received: from localhost (sussie.datadesign.se [194.23.109.130]) by sussie.datadesign.se (8.8.5/8.8.7) with ESMTP id RAA07326; Thu, 29 Oct 1998 17:09:48 +0100 (MET) To: MillikS@salestech.com Cc: freebsd-stable@FreeBSD.ORG Cc: kaj@interbizz.se Subject: Re: Question about Ports Errors From: Rasmus Kaj In-Reply-To: Your message of "Thu, 29 Oct 1998 09:22:48 -0500" <7B62F9E0DD56D111AADB006097A52FCC0465E1@STIUSATLCX1.salestech.com> References: <7B62F9E0DD56D111AADB006097A52FCC0465E1@STIUSATLCX1.salestech.com> X-Mailer: Mew version 1.92.4 on XEmacs 20.4 (Emerald) X-URL: http://www.e.kth.se/~kaj/ X-Phone: +46 (0)8 - 692 35 09 / +46 (0)70 640 49 14 X-Attribution: Kaj X-Face: M9cR~WYav<"fu%MaslX0`43PAYY?uIsM8[#E(0\Xuy9rj>4gE\h3jm.7DD?]R8*^7T\o&vT U@[53Dwkuup4[0@gw#~kyu>`unH?kVj9CJa02(h>Ki\+i=%rn%sDf^KC.!?IHkKjMAbkd\jgmphp^' d|Q;OeXEAhq?ybGqOs1CHb6TJT42'C`Krnk61//AOfXtNjj/t'`5>Vw0QX!dKfOL$.f+S"LIuwR<;I Z0Qnnx(F^F]o@*V%TUtEV'1Z[TkOl^FFV9Z~A[b19%}uP*,huCU Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981029170948D.kaj@interbizz.se> Date: Thu, 29 Oct 1998 17:09:48 +0100 X-Dispatcher: imput version 971024 Lines: 34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "MS" == Milliken, Scott writes: MS> [ ... ] the build errors out with an Error 1 due to a "Malformed MS> conditional" on a line usually like: MS> .if $(({$PORTOBJFORMAT} == "elf" )) MS> I've looked at the code and can get by it if I modify the Makefile so MS> that the condition is commented out and simply execute the steps related MS> to the FALSE condition here (since 2.2.7 isn't elf, of course). MS> However, I would think that someone wrote the code like this for a MS> reason - to support both 2.2.7 and 3.0 with the same ports tree. What MS> package do I need to install (or remake) in order to support the given MS> syntax in the Makefile? You should the following line in your /usr/share/mk/bsd.port.mk (I have them starting at line 393) : # Get the object format. PORTOBJFORMAT!= test -x /usr/bin/objformat && /usr/bin/objformat || echo aout CONFIGURE_ENV+= PORTOBJFORMAT=${PORTOBJFORMAT} SCRIPTS_ENV+= PORTOBJFORMAT=${PORTOBJFORMAT} MAKE_ENV+= PORTOBJFORMAT=${PORTOBJFORMAT} PLIST_SUB+= PORTOBJFORMAT=${PORTOBJFORMAT} They are there if you cvsup -stable but, unfortunately, not in the 2.2.7 release. // Rasmus -- kaj@cityonline.se --------------- Rasmus Kaj - http://www.e.kth.se/~kaj/ \ CityOnLine IB Production AB - http://www.CityOnLine.se/ \---------------------------- Pro is to con as progress is to Congress To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 08:17:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11895 for freebsd-stable-outgoing; Thu, 29 Oct 1998 08:17:42 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11882 for ; Thu, 29 Oct 1998 08:17:40 -0800 (PST) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.9.1/8.8.8) id IAA17255; Thu, 29 Oct 1998 08:08:33 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda17253; Thu Oct 29 08:08:18 1998 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.1/8.9.1) id IAA16539; Thu, 29 Oct 1998 08:08:17 -0800 (PST) Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by passer.osg.gov.bc.ca, id smtpdm16537; Thu Oct 29 08:07:24 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.1/8.9.1) id IAA28278; Thu, 29 Oct 1998 08:06:28 -0800 (PST) Message-Id: <199810291606.IAA28278@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdE28276; Thu Oct 29 08:06:20 1998 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Mailer: MH X-Sender: cy To: John Polstra cc: dom@phmit.demon.co.uk, stable@FreeBSD.ORG Subject: Re: -stable to 3.0 transition In-reply-to: Your message of "Mon, 19 Oct 1998 09:22:38 PDT." <199810191622.JAA13720@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 08:06:19 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199810191622.JAA13720@austin.polstra.com>, John Polstra writes: > In article , > Dom Mitchell wrote: > > > How long will a.out builds be supported for? > > I would expect them to be phased out before the next release of 3.x.x. > We are trying to make a point of _not_ becoming a "pick your favorite > object format" OS. Sorry for the lateness of this reply. I hadn't considered the following until considering similar ramifications on a Linux box I manage. A number of people have purchased commercial products based on a.out binaries. I for example have purchased Motif 2.0 and CDE 1.1. I am not concerned about the window manager, however I do have quite a few Motif apps. Does this mean that these apps will stop working once that a.out will no longer be supported? If no-one produces a Motif distribution for FreeBSD ELF, would apps like native FreeBSD Netscape would no longer be supported? Any thoughts? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 08:17:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11910 for freebsd-stable-outgoing; Thu, 29 Oct 1998 08:17:44 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11891 for ; Thu, 29 Oct 1998 08:17:41 -0800 (PST) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.9.1/8.8.8) id FAA16968; Thu, 29 Oct 1998 05:02:28 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda16966; Thu Oct 29 05:02:08 1998 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.1/8.9.1) id FAA15677; Thu, 29 Oct 1998 05:02:06 -0800 (PST) Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by passer.osg.gov.bc.ca, id smtpdW15675; Thu Oct 29 05:01:42 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.1/8.9.1) id FAA23600; Thu, 29 Oct 1998 05:01:38 -0800 (PST) Message-Id: <199810291301.FAA23600@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdR23596; Thu Oct 29 05:01:36 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: John Polstra cc: dom@phmit.demon.co.uk, stable@FreeBSD.ORG Subject: Re: -stable to 3.0 transition In-reply-to: Your message of "Mon, 19 Oct 1998 09:22:38 PDT." <199810191622.JAA13720@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 05:01:33 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199810191622.JAA13720@austin.polstra.com>, John Polstra writes: > In article , > Dom Mitchell wrote: > > > How long will a.out builds be supported for? > > I would expect them to be phased out before the next release of 3.x.x. > We are trying to make a point of _not_ becoming a "pick your favorite > object format" OS. Sorry for the lateness of this reply. I hadn't considered the following until considering similar ramifications on a Linux box I manage. A number of people have purchased commercial products based on a.out binaries. I for example have purchased Motif 2.0 and CDE 1.1. I am not concerned about the window manager, however I do have quite a few Motif apps. Does this mean that these apps will stop working once that a.out will no longer be supported? If no-one produces a Motif distribution for FreeBSD ELF, would apps like native FreeBSD Netscape would no longer be supported? Any thoughts? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 10:52:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02200 for freebsd-stable-outgoing; Thu, 29 Oct 1998 10:52:10 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02122 for ; Thu, 29 Oct 1998 10:51:39 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id TAA04082; Thu, 29 Oct 1998 19:47:00 +0100 (CET) Message-ID: <19981029194659.A3202@foobar.franken.de> Date: Thu, 29 Oct 1998 19:46:59 +0100 From: Harold Gutch To: Mike Smith Cc: stable@FreeBSD.ORG Subject: Re: HD problems References: <19981028234141.A913@foobar.franken.de> <199810282247.OAA00727@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810282247.OAA00727@dingo.cdrom.com>; from Mike Smith on Wed, Oct 28, 1998 at 02:47:27PM -0800 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 28, 1998 at 02:47:27PM -0800, Mike Smith wrote: > > > Your disk is taking longer to handle the error than we allow it to. Your > > > best bet at this point is probably to mount the partition forced > > > readonly (mount -f -o ro), copy everything meaningful off the the > > > partition, then dd zeroes over it to give the drive a chance to remap > > > the sector(s) in question. > > > > > Is there an easy way to set the timeout-values higher, like patch > > a couple of lines in the wd-driver to at least give me enough > > time to backup the whole thing, and then nuke the data that currently > > still is on it ? > > Yup. Look for the code that looks like this: > > if (wdtab[ctrlr].b_errcnt == 0) > du->dk_timeout = 1 + 10; > else > du->dk_timeout = 1 + 3; > > > and change the 10 to 30 or so. > That's from a -CURRENT /usr/src/sys/isa/i386/wd.c, it looks a little different in -STABLE, still i found it, thanks. After a recompile it didn't have any effect, then i switched to the other solution, mounting forced, backed up the stuff, dd'd over the disk and repartitioned. It seems to work again now. I just checked and saw that my wd.c still contains the unpatched line, so I guess I didn't save after patching it *sigh*. Anyway, thanks for the help, I hope the disk is OK now again :). -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 12:22:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16738 for freebsd-stable-outgoing; Thu, 29 Oct 1998 12:22:13 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16571 for ; Thu, 29 Oct 1998 12:21:00 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id VAA15154; Thu, 29 Oct 1998 21:20:34 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id VAA15279; Thu, 29 Oct 1998 21:08:02 +0100 (MET) (envelope-from j) Message-ID: <19981029210802.06312@uriah.heep.sax.de> Date: Thu, 29 Oct 1998 21:08:02 +0100 From: J Wunsch To: Igor Sysoev Cc: stable@FreeBSD.ORG Subject: Re: Fatal bug in 2.2.5R's lpd Reply-To: Joerg Wunsch References: <199810290737.KAA05021@ns.nitek.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199810290737.KAA05021@ns.nitek.ru>; from Igor Sysoev on Thu, Oct 29, 1998 at 10:42:35AM +0300 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Igor Sysoev wrote: > some time ago I found that 'ct' doesn't work at all at least in lpq. > When I try to list queue on turned off remote LaserJet with JetDirect > card lpq hangs up for 75 seconds nevertheless ct value I set or even > default ct value - 120 seconds. It works for me, that's with a newly added entry pointing to a (currently) nonexistant host on my local net: remote:\ :rm=toy:rp=lp:\ :sd=/var/spool/lpd/remote:\ :mx#0:\ :ct#10:\ :sh: /etc/printcap: 65 lines, 1952 characters uriah # mkdir /var/spool/lpd/remote uriah # lpc restart remote remote: cannot open lock file remote: daemon started uriah # lpq -Premote connection to toy is down uriah # time lpq -Premote connection to toy is down 0.016u 0.005s 0:10.02 0.0% 784+860k 0+0io 0pf+0w ^^^^^^^ > lj|LaserJet 4 with JetDirect:\ > :lp=:\ > :rm=lj:\ > :rq=raw:\ > :sd=/var/spool/output/lj504:\ > :sh:ct=30:\ ct#30 It's a numerical entry, not a string-type one. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 12:52:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20095 for freebsd-stable-outgoing; Thu, 29 Oct 1998 12:52:25 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from chumbly.math.missouri.edu (chumbly.math.missouri.edu [128.206.72.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA20090 for ; Thu, 29 Oct 1998 12:52:21 -0800 (PST) (envelope-from rich@chumbly.math.missouri.edu) Received: by chumbly.math.missouri.edu (950413.SGI.8.6.12/940406.SGI.AUTO) for stable@FreeBSD.ORG id OAA16290; Thu, 29 Oct 1998 14:52:18 -0600 From: rich@chumbly.math.missouri.edu (Rich Winkel) Message-Id: <199810292052.OAA16290@chumbly.math.missouri.edu> Subject: RAID support in FBSD? To: stable@FreeBSD.ORG Date: Thu, 29 Oct 1998 14:52:18 -0600 (CST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm new to this raid stuff. I understand you can get a raid which hooks to the scsi bus and looks to the computer like an ordinary (albeit fast) disk. Theoretically this would work without any specific OS support, right? The alternative would be a raid card on the PCI bus, which can move data faster, but would require OS driver support. Of course there's a lot to be said for OS-independent hardware, but aside from the faster speed, are there worthwhile advantages (i.e. access to special features) to be gained by going with a PCI raid card? I understand fbsd supports DPT pci controllers. How do they compare with the competition? The machine would be a 400mhz xeon, a departmental server, with an adaptec 2940 ultra wide/fast controller. Sorry for the open-ended questions, any faq pointers would be much appreciated. Thanks for any help!!! Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 13:09:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22837 for freebsd-stable-outgoing; Thu, 29 Oct 1998 13:09:28 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22832 for ; Thu, 29 Oct 1998 13:09:26 -0800 (PST) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id OAA20635; Thu, 29 Oct 1998 14:07:39 -0700 (MST) (envelope-from brett@peloton.physics.montana.edu) Date: Thu, 29 Oct 1998 14:07:38 -0700 (MST) From: Brett Taylor To: "Milliken, Scott" cc: "'freebsd-stable@freebsd.org'" Subject: Re: Question about Ports Errors In-Reply-To: <7B62F9E0DD56D111AADB006097A52FCC0465E1@STIUSATLCX1.salestech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > What package do I need to install (or remake) in order to support the > given syntax in the Makefile? You need to update your bsd.port.mk file. The easiest way to do this is via the 2.2.7->2.2-STABLE upgrade package: ftp://ftp.freebsd.org/pub/FreeBSD/packages-stable/Latest/227upgrade.tgz Brett ****************************************************************** Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ "There is something uncanny in the noiseless rush of the cyclist, as he comes into view, passes by, and disappears." - Popular Science, 1891 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 13:15:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23915 for freebsd-stable-outgoing; Thu, 29 Oct 1998 13:15:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from jane.lfn.org (jane.lfn.org [209.16.92.240]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA23908 for ; Thu, 29 Oct 1998 13:15:32 -0800 (PST) (envelope-from caj@lfn.org) Received: (qmail 555 invoked by uid 100); 29 Oct 1998 21:15:29 -0000 Date: Thu, 29 Oct 1998 15:15:29 -0600 (CST) From: Craig Johnston To: freebsd-stable@FreeBSD.ORG Subject: make world bombs on -stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While doing a 'make world' of stable, cvsupped today: ===> libobjc mkdep -f .depend -a /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/NXConstStr.m /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Protocol.m /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/NXConstStr.m:22: objc/NXConstStr.h: No such file or directory /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m:28: objc/Object.h: No such file or directory /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m:29: objc/Protocol.h: No such file or directory /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m:30: objc/objc-api.h: No such file or directory /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Protocol.m:27: objc/Protocol.h: No such file or directory /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Protocol.m:28: objc/objc-api.h: No such file or directory mkdep: compile failed *** Error code 1 Stop. Looks like some include files aren't where they are expected to be. I cleaned everything up and tried this again, and got the same result. -Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 13:35:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25725 for freebsd-stable-outgoing; Thu, 29 Oct 1998 13:35:13 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA25719 for ; Thu, 29 Oct 1998 13:35:10 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zYzii-0002OA-00; Thu, 29 Oct 1998 13:35:04 -0800 Date: Thu, 29 Oct 1998 13:35:02 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Rich Winkel cc: stable@FreeBSD.ORG Subject: Re: RAID support in FBSD? In-Reply-To: <199810292052.OAA16290@chumbly.math.missouri.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Rich Winkel wrote: > I'm new to this raid stuff. I understand you can get a raid which > hooks to the scsi bus and looks to the computer like an ordinary > (albeit fast) disk. Theoretically this would work without any specific > OS support, right? More than theory. They work. Disadvantages: limited by speed of the RAID box host bus. More overhead before data hits the disk. Advantages: you can configure the unit from an LCD panel, or VT100 terminal. No need to run special software on your server. > The alternative would be a raid card on the PCI bus, which can move > data faster, but would require OS driver support. > > Of course there's a lot to be said for OS-independent hardware, but > aside from the faster speed, are there worthwhile advantages (i.e. > access to special features) to be gained by going with a PCI raid > card? I understand fbsd supports DPT pci controllers. How do > they compare with the competition? DPT has a whole line of host based RAID controllers. They are probably the best you can get. Very wide operating system support, so they are hardly OS depedent. Disadvantages: FreeBSD can't run the dptmgr software, so online re-config and monitoring is not possible. If, you have a smart drive enclosure, this shouldn't be a big problem. Advantages: a DPT PM334 is probably cheaper than a SCSI-SCSI raid unit. It also doesn't need any precious hard bays to be mounted in either. You also get up to 3 UW SCSI channels per PCI slot. > The machine would be a 400mhz xeon, a departmental server, with > an adaptec 2940 ultra wide/fast controller. > > Sorry for the open-ended questions, any faq pointers would be > much appreciated. > > Thanks for any help!!! > > Rich > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 13:45:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26865 for freebsd-stable-outgoing; Thu, 29 Oct 1998 13:45:27 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.afa.org (mail.afa.org [204.177.40.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA26860 for ; Thu, 29 Oct 1998 13:45:25 -0800 (PST) (envelope-from kdugarm@afa.org) Received: from afa.org (c204-177-40-130.kivex.com [204.177.40.130]) by mail.afa.org (8.6.12/8.6.12) with ESMTP id PAA11702 for ; Thu, 29 Oct 1998 15:46:25 -0500 Message-ID: <3638E222.E2FD55A3@afa.org> Date: Thu, 29 Oct 1998 16:46:10 -0500 From: Katherine DuGarm Reply-To: KDuGarm@afa.org Organization: Air Force Association X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: make world bombs on -stable References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Craig, I tried twice as well with files cvsupped yesterday and last Friday. I didn't record where it bombed, but I got an error code after about 3 hours of processing. The first time I ran make world, the second time I split it and did make buildworld. The crash happens in make buildworld, I never got to make installworld. I was afraid it was just me!! Katherine Craig Johnston wrote: > > While doing a 'make world' of stable, cvsupped today: > > ===> libobjc > mkdep -f .depend -a /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/NXConstStr.m /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Protocol.m > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/NXConstStr.m:22: objc/NXConstStr.h: No such file or directory > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m:28: objc/Object.h: No such file or directory > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m:29: objc/Protocol.h: No such file or directory > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m:30: objc/objc-api.h: No such file or directory > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Protocol.m:27: objc/Protocol.h: No such file or directory > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Protocol.m:28: objc/objc-api.h: No such file or directory > mkdep: compile failed > *** Error code 1 > > Stop. > > Looks like some include files aren't where they are expected to be. > I cleaned everything up and tried this again, and got the same result. > > -Craig > > 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-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 16:41:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23663 for freebsd-stable-outgoing; Thu, 29 Oct 1998 16:41:42 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23646 for ; Thu, 29 Oct 1998 16:41:39 -0800 (PST) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id LAA09952; Fri, 30 Oct 1998 11:41:36 +1100 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma009946; Fri, 30 Oct 98 11:41:25 +1100 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id LAA24531 for ; Fri, 30 Oct 1998 11:41:20 +1100 From: "John Saunders" To: Subject: RE: make world bombs on -stable Date: Fri, 30 Oct 1998 11:41:19 +1100 Message-ID: <005101be039e$02c91040$6cb611cb@saruman.scitec.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just tried it. Looks like you have clobbered your /usr/include directory "make -DCLOBBER includes" before building. Unfortunately the build process seems broken at the moment, I have send-pr'ed the problem. Try this as a temporary workaround... # cd /usr/src/contrib/gcc/objc # make incinstalldir=/usr/include srcdir=.. copy-headers Then retry the make world again (but not the make includes). Cheers. > While doing a 'make world' of stable, cvsupped today: > > ===> libobjc > mkdep -f .depend -a > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/NXConstStr.m > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Protocol.m > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/NXConstStr.m:22 > : objc/NXConstStr.h: No such file or directory > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m:28: > objc/Object.h: No such file or directory > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m:29: > objc/Protocol.h: No such file or directory > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m:30: > objc/objc-api.h: No such file or directory > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Protocol.m:27: > objc/Protocol.h: No such file or directory > /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Protocol.m:28: > objc/objc-api.h: No such file or directory > mkdep: compile failed > *** Error code 1 > > Stop. > > Looks like some include files aren't where they are expected to be. > I cleaned everything up and tried this again, and got the same result. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 20:26:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25643 for freebsd-stable-outgoing; Thu, 29 Oct 1998 20:26:05 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25637 for ; Thu, 29 Oct 1998 20:26:02 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sjx-ca115-43.ix.netcom.com [207.223.162.107]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id UAA15385; Thu, 29 Oct 1998 20:25:55 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id UAA19405; Thu, 29 Oct 1998 20:25:52 -0800 (PST) Date: Thu, 29 Oct 1998 20:25:52 -0800 (PST) Message-Id: <199810300425.UAA19405@silvia.hip.berkeley.edu> To: brett@peloton.physics.montana.edu CC: MillikS@salestech.com, freebsd-stable@FreeBSD.ORG In-reply-to: (message from Brett Taylor on Thu, 29 Oct 1998 14:07:38 -0700 (MST)) Subject: Re: Question about Ports Errors From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * You need to update your bsd.port.mk file. The easiest way to do this is Exactly. Using ports-current (aka ports-stable) without updating your bsd.port.mk is, um, not a good idea. ;) It is actually good that this thing (${PORTOBJFORMAT}) falls flat on its face, at least it tells the user that something is wrong. Otherwise you may not even know that there could be some problems. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 23:40:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12503 for freebsd-stable-outgoing; Thu, 29 Oct 1998 23:40:36 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.nitek.ru (nitek.east.ru [195.170.63.240]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12488 for ; Thu, 29 Oct 1998 23:40:27 -0800 (PST) (envelope-from igor@nitek.ru) Received: from igor (igor.nitek.ru [192.168.1.10]) by ns.nitek.ru (8.8.4/8.8.5) with ESMTP id KAA26629; Fri, 30 Oct 1998 10:39:10 +0300 (MSK) Message-Id: <199810300739.KAA26629@ns.nitek.ru> From: "Igor Sysoev" To: "Joerg Wunsch" Cc: Subject: Re: Fatal bug in 2.2.5R's lpd Date: Fri, 30 Oct 1998 10:44:18 +0300 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > lj|LaserJet 4 with JetDirect:\ > > :lp=:\ > > :rm=lj:\ > > :rq=raw:\ > > :sd=/var/spool/output/lj504:\ > > :sh:ct=30:\ > ct#30 > > It's a numerical entry, not a string-type one. Thank you, it really helps for me because I need to low frozen time in Windows 95 :). But I think CT cann't be set more than 75 seconds because in my 2.2.7 box connect always fails after 75 second timeout even I CT doesn't set and is 120 seconds by default: : time lpq -Plj connection to lj is down 74.54 real 0.00 user 0.00 sys : I think checking errno for ETIMEDOUT in getport() and going to retry in this case may help. I beg my pardon, with best regards, Igor Sysoev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Oct 29 23:48:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13467 for freebsd-stable-outgoing; Thu, 29 Oct 1998 23:48:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13462 for ; Thu, 29 Oct 1998 23:48:53 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: by skraldespand.demos.su id KAA18485; (8.8.8/D) Fri, 30 Oct 1998 10:48:34 +0300 (MSK) Message-ID: <19981030104833.55472@demos.su> Date: Fri, 30 Oct 1998 10:48:33 +0300 From: "Mikhail A. Sokolov" To: Tom Cc: Rich Winkel , stable@FreeBSD.ORG Subject: Re: RAID support in FBSD? References: <199810292052.OAA16290@chumbly.math.missouri.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Tom on Thu, Oct 29, 1998 at 01:35:02PM -0800 Organization: Demos Company, Ltd., Moscow, Russian Federation. X-Point-of-View: Gravity is myth, - the earth sucks. X-Useless-Header: Look ma! It's a # sign! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 29, 1998 at 01:35:02PM -0800, Tom wrote: # On Thu, 29 Oct 1998, Rich Winkel wrote: # DPT has a whole line of host based RAID controllers. They are probably # the best you can get. Very wide operating system support, so they are ^^^^^^^^^^^^^^^^^^^ Usually, DPT is __very__ slow to operate in degraded mode, which makes it way unusable when such things happen. Since the RAID (5, for instance) are supposed to be redundant/working even when in degraded mode, you want SCSI-SCSI box, something from www.infortrend.com. Let me as well issue the following phrase not proving it, since it'd need more than 2 pages of advocacy: since you will not really achieve anything more than 2mb/sec (values provided for ultra1-wide) in production environment, you really want SCSI-SCSI RAIDs which are much more easy to operate, more redundant (see Tom's definitions/disadvantages list). I neither work for infortrend, nor dpt, of course. # hardly OS depedent. # # Disadvantages: FreeBSD can't run the dptmgr software, so online # re-config and monitoring is not possible. If, you have a smart drive # enclosure, this shouldn't be a big problem. # # Advantages: a DPT PM334 is probably cheaper than a SCSI-SCSI raid unit. # It also doesn't need any precious hard bays to be mounted in either. You # also get up to 3 UW SCSI channels per PCI slot. # # > The machine would be a 400mhz xeon, a departmental server, with # > an adaptec 2940 ultra wide/fast controller. # > # > Sorry for the open-ended questions, any faq pointers would be # > much appreciated. # > # > Thanks for any help!!! # > # > Rich # > # # Tom # # # To Unsubscribe: send mail to majordomo@FreeBSD.org # with "unsubscribe freebsd-stable" in the body of the message -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 30 07:17:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20205 for freebsd-stable-outgoing; Fri, 30 Oct 1998 07:17:23 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gatekeeper.salestech.com (gatekeeper.salestech.com [198.153.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20200 for ; Fri, 30 Oct 1998 07:17:21 -0800 (PST) (envelope-from MillikS@salestech.com) Received: from [162.44.80.67] by gatekeeper.salestech.com for id KAA12394; Fri Oct 30 10:17:10 1998 Received: by STIUSATLCX1.salestech.com with Internet Mail Service (5.5.1960.3) id ; Fri, 30 Oct 1998 10:17:09 -0500 Message-ID: <7B62F9E0DD56D111AADB006097A52FCC0465E7@STIUSATLCX1.salestech.com> Subject: RE: RAID support in FBSD? Date: Fri, 30 Oct 1998 10:17:09 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain To: "'stable@freebsd.org'" From: "Milliken, Scott" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ^^^^^^^^^^^^^^^^^^^ Usually, DPT is __very__ slow to operate in > degraded > mode, which makes it way unusable when such things happen. Since > the RAID (5, for instance) are supposed to be redundant/working even > when > in degraded mode, you want SCSI-SCSI box, something from > www.infortrend.com. > Let me as well issue the following phrase not proving it, since it'd > need > more than 2 pages of advocacy: since you will not really achieve > anything > more than 2mb/sec (values provided for ultra1-wide) in production > environment, > you really want SCSI-SCSI RAIDs which are much more easy to operate, > more redundant (see Tom's definitions/disadvantages list). > > I neither work for infortrend, nor dpt, of course. > > [Milliken, Scott] If you really want the fastest performance then you might want to consider a system that moves RAID completely offline from the server. At my office we use several Clariion (from Data General) RAID arrays, which are self contained boxes that have the RAID controller (or dual if you want multiple hosts or fail-over) built into the system. Other companies make similar systems where no specific drivers are needed on the host system. Basically the box appears to the host as a multi-LUN SCSI drive. You pop an Adaptec 2944 UW controller (differential SCSI, as most external arrays do not have single-ended options) and compile your kernel for that adapter. The neat thing about the Clariion is that it is configured through an ASCII terminal connection on the back of it, so you don't have to load up the proprietary software just to configure it (like the Compaq SMART 2 controllers). It also has five SCSI busses internal to the box, so you can have up to 5 members in a RAID grouping with each member on a separate bus. We have several of the 20 bay arrays and they are total screamers. I think you can now get 128MB read + 128 MB write cache on the controllers, but the 64 MB configurations we use are more than adequate. One other idea that I've come across but don't necessarily know if it's fluff or not, is that when you use an external array, you don't have to waste your pipeline's bandwidth with all of the parity data... so in theory it would seem that on a heavily used system reading/writing multiple RAID sets you could get a 20% boost from not having to transfer all that parity data. No, I don't work for DG or even a company that sells external arrays. I just find that they outperform any other system out there and they're the most OS independent solutions out there. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 30 08:20:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26230 for freebsd-stable-outgoing; Fri, 30 Oct 1998 08:20:05 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA26223 for ; Fri, 30 Oct 1998 08:20:03 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zZHHF-0002eg-00; Fri, 30 Oct 1998 08:19:53 -0800 Date: Fri, 30 Oct 1998 08:19:52 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Mikhail A. Sokolov" cc: Rich Winkel , stable@FreeBSD.ORG Subject: Re: RAID support in FBSD? In-Reply-To: <19981030104833.55472@demos.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Mikhail A. Sokolov wrote: > On Thu, Oct 29, 1998 at 01:35:02PM -0800, Tom wrote: > # On Thu, 29 Oct 1998, Rich Winkel wrote: > # DPT has a whole line of host based RAID controllers. They are probably > # the best you can get. Very wide operating system support, so they are > ^^^^^^^^^^^^^^^^^^^ Usually, DPT is __very__ slow to operate in degraded > mode, which makes it way unusable when such things happen. Since > the RAID (5, for instance) are supposed to be redundant/working even when > in degraded mode, you want SCSI-SCSI box, something from www.infortrend.com. All RAID5 units are slow in degraded mode. That is the whole nature of RAID5. I've had DPT PM334 cards go into degraded mode, and no one even noticed, except for the people next to the machine room heard the DPT alarm. I don't know of any host based DPT cards better than DPT. You may find a SCSI-SCSI faster, but that isn't a host based adapater. > Let me as well issue the following phrase not proving it, since it'd need > more than 2 pages of advocacy: since you will not really achieve anything > more than 2mb/sec (values provided for ultra1-wide) in production environment, > you really want SCSI-SCSI RAIDs which are much more easy to operate, > more redundant (see Tom's definitions/disadvantages list). > > I neither work for infortrend, nor dpt, of course. Tom Systems Support Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 30 08:23:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26515 for freebsd-stable-outgoing; Fri, 30 Oct 1998 08:23:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA26510 for ; Fri, 30 Oct 1998 08:23:29 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zZHKe-0002zh-00; Fri, 30 Oct 1998 08:23:25 -0800 Date: Fri, 30 Oct 1998 08:23:23 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Milliken, Scott" cc: "'stable@freebsd.org'" Subject: RE: RAID support in FBSD? In-Reply-To: <7B62F9E0DD56D111AADB006097A52FCC0465E7@STIUSATLCX1.salestech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Milliken, Scott wrote: > > in degraded mode, you want SCSI-SCSI box, something from ... > If you really want the fastest performance then you > might want to consider a system that moves RAID completely offline from ... Thats exactly what a SCSI-SCSI box is, and exactly what is being talked about. No need for your long description. Besides, a host based RAID controler takes RAID processor "offline" too. A DPT PM334 has a dedicated CPU and RAM, it just happens to be on a PCI card. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 30 08:42:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28345 for freebsd-stable-outgoing; Fri, 30 Oct 1998 08:42:09 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gatekeeper.salestech.com (gatekeeper.salestech.com [198.153.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28338 for ; Fri, 30 Oct 1998 08:42:07 -0800 (PST) (envelope-from MillikS@salestech.com) Received: from [162.44.80.67] by gatekeeper.salestech.com for id LAA27983; Fri Oct 30 11:42:00 1998 Received: by STIUSATLCX1.salestech.com with Internet Mail Service (5.5.1960.3) id ; Fri, 30 Oct 1998 11:41:59 -0500 Message-ID: <7B62F9E0DD56D111AADB006097A52FCC0465EA@STIUSATLCX1.salestech.com> Subject: RE: RAID support in FBSD? Date: Fri, 30 Oct 1998 11:41:59 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain To: "'stable@freebsd.org'" From: "Milliken, Scott" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom wrote: > Thats exactly what a SCSI-SCSI box is, and exactly what is being > talked > about. No need for your long description. > I know that and you know that, but I do believe that the original question was a very generic question from someone wanting to implement redundant technology in their university. Using terms like "SCSI-SCSI" with no explanation is rather ambiguous and doesn't really explain what the idea behind the technology is. My understanding was that this mailing list was a forum for people to learn more about FreeBSD, rather than a place to provide solutions with the least amount of words. > > Besides, a host based RAID controler takes RAID processor "offline" > too. > A DPT PM334 has a dedicated CPU and RAM, it just happens to be on a > PCI > card. > You're also limited by the speed of the PCI bus. If you're running a brand-spanking new motherboard with 100 MHz PCI then you *might* be able to come close to the performance of a lower end offline RAID (or SCSI-SCSI). Another advantage of offline RAID that wasn't mentioned and that an in-box RAID has a liability for is power loss. If your power supply goes out in the CPU then you can have corrupted data on the RAID, while if you lose power on the CPU with an offline box, it has a separate power supply. Most quality offline RAIDs have built in battery backup units and redundant power supplies to make sure that this doesn't happen - if the power is lost to the unit it flushes the cache and parks the heads on the drives. This has come in quite handy on more than one occasion (like when a tornado passed within 100 yards of the data center and ripped out all the power lines) when the UPS couldn't keep going indefinitely. I'm not trying to "slam" in-box RAID solutions, but if you're going to go - go all out. (To steal from the Hardee's commercial). If you can't afford an offline RAID solution, in-box is definitely better than no RAID at all. Scott A. Milliken IMS Health Strategic Technologies Systems Integration Group Atlanta, GA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 30 08:53:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29831 for freebsd-stable-outgoing; Fri, 30 Oct 1998 08:53:40 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hschpt06.hou.ucarb.com ([144.68.7.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29826 for ; Fri, 30 Oct 1998 08:53:38 -0800 (PST) (envelope-from miker@hschpt06.hou.ucarb.com) Received: (from miker@localhost) by hschpt06.hou.ucarb.com (8.8.8/8.8.8) id KAA16512; Fri, 30 Oct 1998 10:53:19 -0600 (CST) (envelope-from mikenguyen@sprintmail.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 30 Oct 1998 10:53:19 -0600 (CST) From: Mike Nguyen To: Tom Subject: RE: RAID support in FBSD? Cc: "stable@freebsd.org" , Milliken@hschpt06.hou.ucarb.com, Scott Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Oct-98 Tom uttered: > > On Fri, 30 Oct 1998, Milliken, Scott wrote: > >> > in degraded mode, you want SCSI-SCSI box, something from > ... >> If you really want the fastest performance then you >> might want to consider a system that moves RAID completely offline from > ... > > Thats exactly what a SCSI-SCSI box is, and exactly what is being talked > about. No need for your long description. > > Besides, a host based RAID controler takes RAID processor "offline" too. > A DPT PM334 has a dedicated CPU and RAM, it just happens to be on a PCI > card. A SCSI-SCSI RAID unit that I have had good experiences with are HP AutoRAIDs (whoa, something from HP that isn't overpriced and doesn't suck, though still not exactly cheap). The AutoRAID 12H has 4 SCSIs internally, and 12 disk slots, which with 18.2GB drives can give you 155 GB or so, though of course you can use 9.1GB and 4.3GB drives (one downside: you have to buy drives from HP, they come in a special enclosure). Also, two host SCSI channels, two controller cards w/ up to 128MB cache each; we use the dual paths on our HP 9000s for high availability. The neat thing about these, and this is what makes me recommend them, is that if you don't allocate all the disk space, it will use that unallocated space to keep more frequently used data in RAID 0+1. It's sorta like a HSM setup, where you have the cache for the most recent stuff, down to the RAID 0+1 cache, and then everything is in RAID5. With 9.1GB drives, we have 78GB or so of usable space (after the hot spare and RAID 5 overhead), and we just allocate 70GB, and leave the rest to the RAID 0+1 space. Very fast (though not as fast as EMC, but hey, it's load cheaper), easy to set up (front panel or software w/ HP-UX or LoseNT). I give it a thumbs up. Mike. ------------------------------------------------------------------------------- Mike Nguyen - UNIX Sysadmin and Geek Pager (800) SKY-8888 pin# 1138368 or 1138368@skytel.com "His super power is to turn into a scotch terrier." ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 30 08:57:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00267 for freebsd-stable-outgoing; Fri, 30 Oct 1998 08:57:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA00261 for ; Fri, 30 Oct 1998 08:57:24 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zZHrU-0006UL-00; Fri, 30 Oct 1998 08:57:20 -0800 Date: Fri, 30 Oct 1998 08:57:19 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Milliken, Scott" cc: "'stable@freebsd.org'" Subject: RE: RAID support in FBSD? In-Reply-To: <7B62F9E0DD56D111AADB006097A52FCC0465EA@STIUSATLCX1.salestech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Milliken, Scott wrote: > > Besides, a host based RAID controler takes RAID processor "offline" > > too. > > A DPT PM334 has a dedicated CPU and RAM, it just happens to be on a > > PCI > > card. > > > You're also limited by the speed of the PCI bus. If you're > running a brand-spanking new motherboard with 100 MHz PCI then you > *might* be able to come close to the performance of a lower end offline > RAID (or SCSI-SCSI). Another advantage of offline RAID that wasn't And how are SCSI-SCS boxes not "limited" by PCI? It seems that SCSI-SCSI units are more limited, because they are connected via a 40MB/s (or 80MB/s with ultra2) bus, but host based cards are right on the PCI bus (132MB/s). A low end SCSI-SCSI unit will not exceed the performance of a host base one. Not with the extra overhead. > mentioned and that an in-box RAID has a liability for is power loss. If > your power supply goes out in the CPU then you can have corrupted data > on the RAID, while if you lose power on the CPU with an offline box, it > has a separate power supply. Most quality offline RAIDs have built in > battery backup units and redundant power supplies to make sure that this Two power supplies are worse than one. It only takes one to fail to take down the system, so system MTBF is the MTBF of one power supply divided by two. Besides, if you want the system to be any good at all, you'll put redundant power supplies everywhere. > doesn't happen - if the power is lost to the unit it flushes the cache > and parks the heads on the drives. This has come in quite handy on > more than one occasion (like when a tornado passed within 100 yards of > the data center and ripped out all the power lines) when the UPS > couldn't keep going indefinitely. Then you server should shutdown if it has no power. That's what smart UPSes are for. > I'm not trying to "slam" in-box RAID solutions, but if you're > going to go - go all out. (To steal from the Hardee's commercial). If > you can't afford an offline RAID solution, in-box is definitely better > than no RAID at all. A SCSI-SCSI also makes no sense for small 3 or 5 drive arrays either. > Scott A. Milliken > IMS Health Strategic Technologies > Systems Integration Group > Atlanta, GA Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 30 09:40:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05194 for freebsd-stable-outgoing; Fri, 30 Oct 1998 09:40:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05154 for ; Fri, 30 Oct 1998 09:40:01 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id TAA11672; Fri, 30 Oct 1998 19:39:35 +0200 (EET) Date: Fri, 30 Oct 1998 19:39:34 +0200 (EET) From: Narvi To: "Milliken, Scott" cc: "'stable@freebsd.org'" Subject: RE: RAID support in FBSD? In-Reply-To: <7B62F9E0DD56D111AADB006097A52FCC0465EA@STIUSATLCX1.salestech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Milliken, Scott wrote: [snip] > You're also limited by the speed of the PCI bus. If you're > running a brand-spanking new motherboard with 100 MHz PCI then you > *might* be able to come close to the performance of a lower end offline This is a *GROSS* error. Nobody on this planet is running PCI at 100Mhz. Nobody at all. PCI is still 66Mhz max and AFAIK, Micron is the only one to offer that on the PC platform. [snip] > > Scott A. Milliken > IMS Health Strategic Technologies > Systems Integration Group > Atlanta, GA > Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 30 09:45:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05425 for freebsd-stable-outgoing; Fri, 30 Oct 1998 09:45:38 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05419 for ; Fri, 30 Oct 1998 09:45:25 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id TAA11707; Fri, 30 Oct 1998 19:43:47 +0200 (EET) Date: Fri, 30 Oct 1998 19:43:47 +0200 (EET) From: Narvi To: Tom cc: "Milliken, Scott" , "'stable@freebsd.org'" Subject: RE: RAID support in FBSD? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Tom wrote: > > On Fri, 30 Oct 1998, Milliken, Scott wrote: > > > > Besides, a host based RAID controler takes RAID processor "offline" > > > too. > > > A DPT PM334 has a dedicated CPU and RAM, it just happens to be on a > > > PCI > > > card. > > > > > You're also limited by the speed of the PCI bus. If you're > > running a brand-spanking new motherboard with 100 MHz PCI then you > > *might* be able to come close to the performance of a lower end offline > > RAID (or SCSI-SCSI). Another advantage of offline RAID that wasn't > > And how are SCSI-SCS boxes not "limited" by PCI? > > It seems that SCSI-SCSI units are more limited, because they are > connected via a 40MB/s (or 80MB/s with ultra2) bus, but host based cards > are right on the PCI bus (132MB/s). This is wrong. Max sustained bandwidth for 33Mhz 32bit PCI bus is 80MB/s. 132MB/s is the theoretical peak bandwidth on an infinite burst transfer. For higher bandwidth, you need either wider (64 bit) or faster (66Mhz) PCI bus. Sander There is no love, no good, no happiness and no future - all these are just illusions. > > Tom > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Oct 30 09:55:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06495 for freebsd-stable-outgoing; Fri, 30 Oct 1998 09:55:52 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06489 for ; Fri, 30 Oct 1998 09:55:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA00882; Fri, 30 Oct 1998 09:54:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810301754.JAA00882@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Narvi cc: Tom , "Milliken, Scott" , "'stable@freebsd.org'" Subject: Re: RAID support in FBSD? In-reply-to: Your message of "Fri, 30 Oct 1998 19:43:47 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 09:54:55 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is wrong. Max sustained bandwidth for 33Mhz 32bit PCI bus is 80MB/s. > 132MB/s is the theoretical peak bandwidth on an infinite burst transfer. > For higher bandwidth, you need either wider (64 bit) or faster (66Mhz) PCI > bus. You're presuming on the latency timer here, right? I don't recall there being a cap on the burst length. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 31 06:08:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28733 for freebsd-stable-outgoing; Sat, 31 Oct 1998 06:08:53 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28724 for ; Sat, 31 Oct 1998 06:08:50 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id QAA23770; Sat, 31 Oct 1998 16:08:09 +0200 (EET) Date: Sat, 31 Oct 1998 16:08:09 +0200 (EET) From: Narvi To: Mike Smith cc: Tom , "Milliken, Scott" , "'stable@freebsd.org'" Subject: Re: RAID support in FBSD? In-Reply-To: <199810301754.JAA00882@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Mike Smith wrote: > > This is wrong. Max sustained bandwidth for 33Mhz 32bit PCI bus is 80MB/s. > > 132MB/s is the theoretical peak bandwidth on an infinite burst transfer. > > For higher bandwidth, you need either wider (64 bit) or faster (66Mhz) PCI > > bus. > > You're presuming on the latency timer here, right? I don't recall > there being a cap on the burst length. In the spec, probably yes. But obviously there is a cap on the burst length. The cap is due to the reason that PCI is not AFAIK full-duplex. Once the device has transmitted all data you asked for, it is going to have to pause until you ask for more. FreeBSD does transfers in amounts of max. max_phys_io, right? And ordinary machines have just one PCI<->host bus on which several more things are going on (somebody moves the mouse, a network packet arrives, something is logged to the screen, etc.). > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 31 11:38:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05911 for freebsd-stable-outgoing; Sat, 31 Oct 1998 11:38:33 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (castles325.castles.com [208.214.167.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05906 for ; Sat, 31 Oct 1998 11:38:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00838; Sat, 31 Oct 1998 11:37:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810311937.LAA00838@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Narvi cc: Mike Smith , Tom , "Milliken, Scott" , "'stable@freebsd.org'" Subject: Re: RAID support in FBSD? In-reply-to: Your message of "Sat, 31 Oct 1998 16:08:09 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 11:37:48 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Fri, 30 Oct 1998, Mike Smith wrote: > > > > This is wrong. Max sustained bandwidth for 33Mhz 32bit PCI bus is 80MB/s. > > > 132MB/s is the theoretical peak bandwidth on an infinite burst transfer. > > > For higher bandwidth, you need either wider (64 bit) or faster (66Mhz) PCI > > > bus. > > > > You're presuming on the latency timer here, right? I don't recall > > there being a cap on the burst length. > > In the spec, probably yes. Unless you can say "definitely" yes, I'll contend that the only cap on the burst length is the latency timer. At a typical value around 80 cycles and with an overhead of ~8 cycles to set up/shut down the transfer around the timer, that only loses you 10% of your bus bandwidth. Unfortunately I left my copy of the PCI spec at my last job, so I can't quote chapter and verse. > But obviously there is a cap on the burst length. The cap is due to the > reason that PCI is not AFAIK full-duplex. Once the device has transmitted > all data you asked for, it is going to have to pause until you ask for > more. FreeBSD does transfers in amounts of max. max_phys_io, right? > > And ordinary machines have just one PCI<->host bus on which several more > things are going on (somebody moves the mouse, a network packet arrives, > something is logged to the screen, etc.). Now you're trying to cloud the issue; you originally said "Max sustained bandwidth for 33Mhz 32bit PCI bus is 80MB/s." Now you are trying to say "Maximum bandwidth in some hypothetical typical use is 80MB/s". I suggest you need to do some more math. It's certainly possible to sustain a lot more than 80MB/s, even with multiple masters on the bus. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 31 22:29:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17331 for freebsd-stable-outgoing; Sat, 31 Oct 1998 22:29:16 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mh2.cts.com (mh2.cts.com [209.68.192.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17326 for ; Sat, 31 Oct 1998 22:29:15 -0800 (PST) (envelope-from mdavis@io.cts.com) Received: from io.cts.com (io.cts.com [198.68.174.34]) by mh2.cts.com (8.8.7/8.8.5) with ESMTP id WAA29145 for ; Sat, 31 Oct 1998 22:29:11 -0800 (PST) Received: (from mdavis@localhost) by io.cts.com (8.8.8/8.8.8) id WAA23256 for freebsd-stable@freebsd.org; Sat, 31 Oct 1998 22:29:11 -0800 (PST) (envelope-from mdavis) From: Morgan Davis Message-Id: <199811010629.WAA23256@io.cts.com> Subject: pw touches mailbox file To: freebsd-stable@FreeBSD.ORG Date: Sat, 31 Oct 1998 22:29:11 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The 'pw useradd' function includes an undocumented feature of creating a mailbox file in /var/mail. There is no flag for disabling this, nor is it really necessary since it'll get created by sendmail anyway. But alas, it's there. Unfortunately, the assumption about /var/mail being the location for mailboxes is problematic if /usr/libexec/mail.local has been modified to use an alternate location (e.g., to support Qualcomm Popper's hashed spool directory feature -- /var/mail/j/s/jsmith). Suggestion: If pw must create a mailbox file, it should provide an option for specifying where that file is, or at least write through mail.local to honor any local configuration changes. At the very least, it should have a flag for disabling mailbox creation altogether. --Morgan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Oct 31 23:59:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24617 for freebsd-stable-outgoing; Sat, 31 Oct 1998 23:59:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from csi-x.net (csi-x.net [202.184.73.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA24610 for ; Sat, 31 Oct 1998 23:58:59 -0800 (PST) (envelope-from najib@csi-x.net) Received: from csi-x.net (nobody@csi-x.net [202.184.73.5]) by csi-x.net (8.9.1/8.9.1) with SMTP id QAA11687 for ; Sun, 1 Nov 1998 16:05:02 +0800 (MYT) From: "Muhammad Najib" Reply-to: najib@csi-x.net To: freebsd-stable@FreeBSD.ORG Date: Sun, 1 Nov 1998 16:05:06 -800 Subject: Problem compiling -STABLE Message-id: <363c1632.2da2.0@csi-x.net> X-User-Info: 202.184.73.12 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was wondering .. before this I could compile 2.2.7-STABLE .. but then recently I did cvsup for RELENG_2_2's src-sys and I got this message when I config the config file csi-x# config JeEbSioN Unknown % construct in generic makefile: %VERSREQ= 220000 Kernel build directory is ../../compile/JeEbSioN csi-x# hence ... I just ignore this particular problem .. but then when I finished doing make depend .. and I start doing make ... half way it stop with this error(s) cc -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../.. -I/usr/include -DAPM_BROKEN_STATCLOCK -DIPDIVERT -DFAILSAFE -DCOMPAT_43 -DMSDOSFS -DNFS -DFFS -DIPFILTER -DINET -DKERNEL -c vers.c loading kernel isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment *** Error code 1 Stop. csi-x# I wonder ... what I did wrong here .... please point me :) Thanx in advance ... regards, ****************************************************************** MUHAMMAD NAJIB ABDUL MUKTHI member of My-Linux.ORG CO SYSTEM ADMINISTRATOR http://www.my-linux.org Kolej Damansara Utama 32, Jalan Anson najib@mrsm.org 10400, Pulau Pinang. najib@csi-x.net http://najib.csi-x.net najib@kdupg.edu.my Tel : 012-4717452 najib@my-linux.org ****************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message