From owner-freebsd-mobile Sun Mar 30 13:31:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA14086 for mobile-outgoing; Sun, 30 Mar 1997 13:31:16 -0800 (PST) Received: from mexico.brainstorm.eu.org (mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA14079 for ; Sun, 30 Mar 1997 13:31:11 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id XAA23034 for ; Sun, 30 Mar 1997 23:31:00 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id XAA30811 for freebsd-mobile@freebsd.org; Sun, 30 Mar 1997 23:30:48 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id VAA21106; Sun, 30 Mar 1997 21:46:20 +0200 (CEST) Message-ID: <19970330214619.36224@keltia.freenix.fr> Date: Sun, 30 Mar 1997 21:46:19 +0200 From: Ollivier Robert To: freebsd-mobile@freebsd.org Subject: Re: sendmail & the roving laptop References: <9703271656.AA13189@sneezy> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 In-Reply-To: <9703271656.AA13189@sneezy>; from Kent Hauser on Thu, Mar 27, 1997 at 11:56:33AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3153 Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Kent Hauser: > 1) sendmail refuses to *not* do a dns lookup even when the "no dns" option > is specified. While my laptop nameserver has all of the local records, > it can't do a real lookup while travelling. > > This causes sendmail to hang & not send the mail. Use FEATURE(nocanonify). nodns is not doing anything useful now. > 2) all mail is either locally delivered or queued. If mail to a > co-worker is queued for uucp xmission, then my mail is also queued. > If mail to me is locally delivered, then co-worker mail is also & > bounces. What about sending your sendmail config file (.mc) either to the list (although it is not really appropriate) or to me directly ? -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #41: Sun Mar 23 23:01:22 CET 1997 From owner-freebsd-mobile Tue Apr 1 16:19:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA17148 for mobile-outgoing; Tue, 1 Apr 1997 16:19:29 -0800 (PST) Received: from rmsq.com (rmsq.com [204.133.95.70]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA17121; Tue, 1 Apr 1997 16:19:18 -0800 (PST) Received: (from baldrick@localhost) by rmsq.com (8.8.5/8.8.5) id RAA02478; Tue, 1 Apr 1997 17:18:47 -0700 (MST) Date: Tue, 1 Apr 1997 17:18:47 -0700 (MST) From: Just Baldrick Message-Id: <199704020018.RAA02478@rmsq.com> To: freebsd-mobile@freebsd.org, freebsd-questions@freebsd.org Subject: FreeBSD-2.2.1 Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, FreeBSD-2.2.1 works fine on Pentium Pro machines, but we are unable to get to the install stage on a Pentium laptop (BIT Computers). The boot floppy appears to be going through correctly, but at the very last stage the screen is corrupted and the machine hangs. A previous 2.2-SNAP boot floppy worked fine - any ideas? Thanks, Geoff Martindale From owner-freebsd-mobile Fri Apr 4 09:56:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA22814 for mobile-outgoing; Fri, 4 Apr 1997 09:56:24 -0800 (PST) Received: from rmsq.com (rmsq.com [204.133.95.70]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA22780; Fri, 4 Apr 1997 09:56:15 -0800 (PST) Received: (from baldrick@localhost) by rmsq.com (8.8.5/8.8.5) id KAA13669; Fri, 4 Apr 1997 10:55:47 -0700 (MST) Date: Fri, 4 Apr 1997 10:55:47 -0700 (MST) From: Just Baldrick Message-Id: <199704041755.KAA13669@rmsq.com> To: baldrick@rmsq.com, freebsd-mobile@freebsd.org, freebsd-questions@freebsd.org Subject: Re: FreeBSD-2.2.1 Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, > unable to get to the install stage on >a Pentium laptop (BIT Computers). >The boot floppy appears to be going through correctly, >but at the very last stage the screen is corrupted >and the machine hangs. >A previous 2.2-SNAP boot floppy worked fine - any ideas? we just tried the following suggestion from David Greenman >setting flags 0x1 for npx0 (via -c at Boot:). There is a problem with >the optimized bcopy code and some VGA cards. This worked - I don't know why setting a flag for a math co-processor fixes some interaction between bcopy code (string manipulation?) and VGA cards but setting the flag to 0x1 via -c in the boot floppy and subsequently adding to the kernal conf file enabled us to put up 2.2.1 on the laptop thanks Thanks, Geoff Martindale From owner-freebsd-mobile Fri Apr 4 10:59:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA26216 for mobile-outgoing; Fri, 4 Apr 1997 10:59:01 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA26189; Fri, 4 Apr 1997 10:58:50 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id KAA01814; Fri, 4 Apr 1997 10:58:37 -0800 (PST) Date: Fri, 4 Apr 1997 10:58:37 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Just Baldrick cc: freebsd-mobile@freebsd.org, freebsd-questions@freebsd.org Subject: Re: FreeBSD-2.2.1 In-Reply-To: <199704041755.KAA13669@rmsq.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 4 Apr 1997, Just Baldrick wrote: > >setting flags 0x1 for npx0 (via -c at Boot:). There is a problem with > >the optimized bcopy code and some VGA cards. > > This worked - I don't know why setting a flag for a math co-processor > fixes some interaction between bcopy code (string manipulation?) > and VGA cards > but setting the flag to 0x1 via -c in the boot floppy > and subsequently adding to the kernal conf file > enabled us to put up 2.2.1 on the laptop > thanks I saw that and it blew me away. Thanks for the hint David. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-mobile Fri Apr 4 16:56:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA13731 for mobile-outgoing; Fri, 4 Apr 1997 16:56:44 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA13710; Fri, 4 Apr 1997 16:56:39 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id QAA14294; Fri, 4 Apr 1997 16:56:40 -0800 (PST) Message-Id: <199704050056.QAA14294@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Doug White cc: Just Baldrick , freebsd-mobile@freebsd.org, freebsd-questions@freebsd.org Subject: Re: FreeBSD-2.2.1 In-reply-to: Your message of "Fri, 04 Apr 1997 10:58:37 PST." From: David Greenman Reply-To: dg@root.com Date: Fri, 04 Apr 1997 16:56:40 -0800 Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Fri, 4 Apr 1997, Just Baldrick wrote: > >> >setting flags 0x1 for npx0 (via -c at Boot:). There is a problem with >> >the optimized bcopy code and some VGA cards. >> >> This worked - I don't know why setting a flag for a math co-processor >> fixes some interaction between bcopy code (string manipulation?) >> and VGA cards >> but setting the flag to 0x1 via -c in the boot floppy >> and subsequently adding to the kernal conf file >> enabled us to put up 2.2.1 on the laptop >> thanks > >I saw that and it blew me away. Thanks for the hint David. Incidently, the npx0 flags is a kludge. We don't yet have a way of toggling generic kernel flags in userconfig, so instead Bruce is using the unused flags on npx0 (which is a required device). This behavior will go away at some point... -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-mobile Fri Apr 4 22:36:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA23675 for mobile-outgoing; Fri, 4 Apr 1997 22:36:17 -0800 (PST) Received: from critter.dk.tfs.com (phk.cybercity.dk [195.8.133.247]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA23655; Fri, 4 Apr 1997 22:36:04 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id IAA02822; Sat, 5 Apr 1997 08:34:58 +0200 (CEST) To: dg@root.com cc: Doug White , Just Baldrick , freebsd-mobile@freebsd.org, freebsd-questions@freebsd.org Subject: Re: FreeBSD-2.2.1 In-reply-to: Your message of "Fri, 04 Apr 1997 16:56:40 -0800." <199704050056.QAA14294@root.com> Date: Sat, 05 Apr 1997 08:34:58 +0200 Message-ID: <2820.860222098@critter> From: Poul-Henning Kamp Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199704050056.QAA14294@root.com>, David Greenman writes: >>On Fri, 4 Apr 1997, Just Baldrick wrote: >> >>> >setting flags 0x1 for npx0 (via -c at Boot:). There is a problem with >>> >the optimized bcopy code and some VGA cards. >>> >>> This worked - I don't know why setting a flag for a math co-processor >>> fixes some interaction between bcopy code (string manipulation?) >>> and VGA cards >>> but setting the flag to 0x1 via -c in the boot floppy >>> and subsequently adding to the kernal conf file >>> enabled us to put up 2.2.1 on the laptop >>> thanks >> >>I saw that and it blew me away. Thanks for the hint David. > > Incidently, the npx0 flags is a kludge. We don't yet have a way of toggling >generic kernel flags in userconfig, so instead Bruce is using the unused >flags on npx0 (which is a required device). This behavior will go away at >some point... In the case of the P5-bcopy it isn't at all inappropriate when you consider the implementation... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-mobile Sat Apr 5 01:54:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA29531 for mobile-outgoing; Sat, 5 Apr 1997 01:54:00 -0800 (PST) Received: from mexico.brainstorm.eu.org (mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA29526 for ; Sat, 5 Apr 1997 01:53:54 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id LAA01561 for ; Sat, 5 Apr 1997 11:53:36 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id CAA21003 for freebsd-mobile@freebsd.org; Sat, 5 Apr 1997 02:29:14 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id CAA19776; Sat, 5 Apr 1997 02:20:42 +0200 (CEST) Message-ID: <19970405022042.06450@keltia.freenix.fr> Date: Sat, 5 Apr 1997 02:20:42 +0200 From: Ollivier Robert To: freebsd-mobile@freebsd.org Subject: Re: FreeBSD-2.2.1 References: <199704041755.KAA13669@rmsq.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 In-Reply-To: <199704041755.KAA13669@rmsq.com>; from Just Baldrick on Fri, Apr 04, 1997 at 10:55:47AM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3153 Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Just Baldrick: > This worked - I don't know why setting a flag for a math co-processor > fixes some interaction between bcopy code (string manipulation?) > and VGA cards The flag is not really for the npx itself but it was easier to give "hints" to the kernel this way rather than as an option... Another example is that when you want to specify your memory size (necessary when you have more than 64 MB), you'll do it by specifying an iosiz... cf /sys/i386/conf/LINT: # `iosiz' for npx0: # This can be used instead of the MAXMEM option to set the memory size. If # it is nonzero, then it overrides both the MAXMEM option and the memory # size reported by the BIOS. Setting it at boot time using userconfig # takes # effect on the next reboot after the change has been recorded in the # kernel # binary (the size is used early in the boot before userconfig has a chance # to change it). -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #41: Sun Mar 23 23:01:22 CET 1997