From owner-freebsd-current Thu Feb 27 16: 4:43 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B772A37B401; Thu, 27 Feb 2003 16:04:41 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id D935443FB1; Thu, 27 Feb 2003 16:04:40 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0207.cvx40-bradley.dialup.earthlink.net ([216.244.42.207] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18oY11-0004mN-00; Thu, 27 Feb 2003 16:04:40 -0800 Message-ID: <3E5EA745.F1910337@mindspring.com> Date: Thu, 27 Feb 2003 16:03:17 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: David Schultz Cc: John Baldwin , Garance A Drosihn , current@FreeBSD.ORG, Geoffrey , Ruslan Ermilov Subject: Re: Any ideas why we can't even boot a i386 ? References: <3E5E9A93.9B51DC87@mindspring.com> <20030227234408.GA89380@HAL9000.homeunix.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4d2b9c01bf33d954fea4fb28a36cc9956548b785378294e88350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Schultz wrote: > Thus spake Terry Lambert : > > John Baldwin wrote: > > > I doubt the usefulness of this. i386 kernels were just accidentally > > > broken for almost a month and a half without anyone noticing. > > > > People who build embedded devices that need to be supported in > > the field, and want to worry about their software, and not the > > platform it runs on, don't use -current, FWIW. > > Moot point. People who build embedded devices have separate, > usually modern, machines for building their kernels. They also outsource their hardware, and have to provide a "golden master" CDROM. Internally, they also tend to want a build environment that is the same as the environment on their target platform, which they then use for cross-building on those "separate, usually modern, machines". What that boils down to is that you build a CDROM as if you were going to install on the target machine with a CDROM drive, even if the thing doesn't have a CDROM drive. Likewise, when you have a room full of appliance boxes that are rack-mounted, and have serial consoles, no CDROM, no floppy, or other removable media, the normal way you use to install an image is to boot up the current image, copy over the sysinstall from an already installed bootstrap system with a CDROM drive, and then NFS mount the CDROM, and run the sysinstall from the serial console, and lie and tell it the thing was mounted locally. This isn't like a build-out at an ISP or hosting company, where you can PXE everything because you're never going to ship anything to a customer site, so it's OK if some machine reboots, gets your boot server, and installs a new image (a disaster, if it happened to a closed box shipped to a customer site!). If you've never built a closed-box appliance, then you are probably not familiar with the operational differences you have to live with, compared to something like Yahoo or RackSpace, etc.. BTW: I would say the vast majority of FreeBSD installations are in open-box places like Yahoo, RackSpace, etc., where the boxes are all cloned out from a template, and never leave the premises or end up under the physical control of an end user. BUT... I would say that the *second-most* numerous set of FreeBSD installs is in closed-box systems from companies like Whistle, IBM, ClickArray, NetScaler, etc., who are building appliances (makes me wonder how many Soekris boxes are out there running FreeBSD). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message