Date: Thu, 20 Nov 1997 14:48:40 -0700 From: Nate Williams <nate@mt.sri.com> To: Ken Key <key@cs.utk.edu> Cc: Nate Williams <nate@mt.sri.com>, freebsd-mobile@freebsd.org Subject: Re: boot floppies for 2.2.5-STABLE that speak PCMCIA? Message-ID: <199711202148.OAA11511@mt.sri.com> In-Reply-To: <199711202142.QAA23366@duncan.cs.utk.edu> References: <199711202022.NAA11157@mt.sri.com> <199711202142.QAA23366@duncan.cs.utk.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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. > > Ah, I've also been pulling the RELENG_2_2 tag via cvsup, which I now assume > maps to 2.2.5-STABLE. That is true, but you're not getting a SNAP, you're getting the bits. A 'SNAP' is a snapshot/build of the sources at a particular point in time, while what you have is sources, but no binaries or any 'tested' build environment. > Now I'm confused. I had assumed the 3.0-*-SNAP's > were "freebsd-current" and the 2.2-*-SNAPS were "freebsd-stable", per the > handbook. If the 2.2-*-SNAPs aren't RELENG_2_2, what are they? I don't think there have been any SNAP's that have been made since 2.2.5 was released, so any 2.2 SNAPS won't have any post-2.2.5R changes in them. > > 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. > > That's what I eventually want to do but I'm worried about failure modes > with the upgrade interacting with PAO already on the system. There shouldn't be any failure modes interacting badly with PAO. You just need to make sure to update your /etc files with the FreeBSD versions when you do your upgrade like you would do with *ANY* source upgrade and it should go fine. > However, it now sounds like my choice for doing the wipe means putting PAO > back on after partitioning/newfs'ing and then cvsup/build/upgrade. If you put PAO back, then you're in the same boat you are in now. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711202148.OAA11511>