Date: Thu, 7 Jan 1999 15:55:57 -0700 From: Nate Williams <nate@mt.sri.com> To: Julian Elischer <julian@whistle.com> Cc: Nate Williams <nate@mt.sri.com>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf Makefile.i386 Message-ID: <199901072255.PAA25135@mt.sri.com> In-Reply-To: <36953862.59E2B600@whistle.com> References: <199901072037.NAA22536@mt.sri.com> <Pine.BSF.3.95.990107124507.3875I-100000@current1.whistle.com> <199901072101.OAA22809@mt.sri.com> <36952F5F.2781E494@whistle.com> <199901072214.PAA24446@mt.sri.com> <36953862.59E2B600@whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > And there is no way to upgrade the upgrade code? You have no control > > over what the upgrade code does? > > You get new upgrade code with the upgrade, but that will only be used > in the NEXT upgrade. Sounds like you have to do 'upgrades'. > > C'mon, I have a *REALLY* hard time believing that your upgrading doesn't > > allow for the possibility of running aribitrary commands. > > no the upgrade code didn't have the ability to run arbitrary code > BEFORE booting into the new system. It should, because it's possible that you would need to move /etc files and such. But, stating what it *should* be able to do at this point is a moot point. > > Or you can upgrade the bootblocks on that hardware. If you can install > > and run software, then you can upgrade the bootblocks. > > yes but that would require 2 upgrades in a row.. Which is IMO the only 'acceptable' technical solution, and one many large companies have done, for people that are even more clueless than the Whistle owners. :) > I'm not saying it's impossible but it flies in the face of > "don't annoy the custommer". Or customer even. :) > In the end we may end up with a > double upgrade, but that is a pain because > we only retain 1 backwards revision on the machine so the > custommer could not revert to the old system they were running > after the 2nd upgrade should things go wrong with it. Doesn't it seem like no matter how far we try to think ahead, something always pops up that we never considered. :) > > > Asking a custommer to upgrade twice in a row for a single upgrade > > > is a big 'custommer satisfaction' thing, that must be taken > > > very seriously. > > > > Symantec did this with Visual Cafe, and Intuit did this with Quicken. > > The former has a couple hundred thousand users, and the latter has an > > installed base larger than all of FreeBSD, so I don't think this is > > an 'unacceptable' solution. > > You may be right. That's a decision for 'marketting'. Remember that this > is an 'appliance' that should "just work" so the custommer > expectation is that they shouldn't have to do very much.... > > > Mind you, a 'boundary' release between major branches of the code > does have some advantages. State their getting 2X performance, and the internal disk is being replaced by something that is twice as big or something. :) :) :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901072255.PAA25135>