From owner-freebsd-mobile Thu Nov 20 12:22:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA04265 for mobile-outgoing; Thu, 20 Nov 1997 12:22:48 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA04259 for ; Thu, 20 Nov 1997 12:22:42 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA20520; Thu, 20 Nov 1997 13:22:40 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA11157; Thu, 20 Nov 1997 13:22:37 -0700 Date: Thu, 20 Nov 1997 13:22:37 -0700 Message-Id: <199711202022.NAA11157@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ken Key Cc: freebsd-mobile@freebsd.org Subject: Re: boot floppies for 2.2.5-STABLE that speak PCMCIA? In-Reply-To: <199711201914.OAA10214@duncan.cs.utk.edu> References: <199711201914.OAA10214@duncan.cs.utk.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've been running v2.2.2-PAO on a ThinkPad 560 w/ LinkSys EC2T. > Per the comments of Nate Williams the past few weeks, it sounds like > I want to run v2.2.5-STABLE (is that the same as the 2.2-YYMMDD-SNAP?) No, it's not the same. I don't believe there has been an updated 2.2.5-STABLE snap. > to > get support for my Sony PRD-650WM Diskman (SCSI CD-ROM with rebadged > Adaptec 1460) to work. Mine works great. :) > When I pull the 971119 2.2 and 3.0 SNAP boot > floppies, the installation procedure doesn't enable the LinkSys ed device, > which makes it rather difficult to install over the net. Are there > different boot floppy images I should be using for a laptop PCMCIA network > install? Can you use your existing setup to update just the sources and build from that using CVSup/CTM? That's the 'standard' way of updating, and it let's you continue to update as changes are made once you get things setup initially. The handbook has information on how to do that. I don't know anything about PAO, so I can't say. Nate