Date: Tue, 31 Oct 2000 15:30:17 -0500 From: Hurf Sheldon <hurf@Graphics.Cornell.EDU> To: freebsd-questions@freebsd.org Subject: Re: BSD Stable from 4.1 CD-ROMS? Message-ID: <39FF2BD9.6640F14A@graphics.cornell.edu> References: <39FEE9C2.1D6B7DC5@graphics.cornell.edu> <39FEF0F0.C86A5492@i-clue.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Cristoph, Thanks for the info - re: the releases - aha! re: the disks, our 4.0 Release system made 5 partitions on the disk on a twin system. As it is now we have root, swap, usr and var and can't create any more partitions. This was seemingly forced on us by the slice manager and disk label editor. re: the update scheme - this includes ports & packages as well? kind regards, hurf, Moral: If you fix it before it breaks, you get weekends off. Christoph Sold wrote: > > Hurf Sheldon schrieb: > > > > Hi Folks, > > Some questions re: FreeBSD installs. > > I've just installed 4.1 from the CD-Rom dated August. Is that considered > > the "stable"? We installed the "X with kernel sources" selection > > with no extras save linux and 3.2 binary compatability. > > It is 4.1-RELEASE. Have a look at > /usr/share/doc/handboook/current-stable.html to learn what current > distinguises from stable and that in turn from release. > > To put a long story short: current is the bleeding edge, stable gets the > occasional bugfix, and release is stable at some point in time a while > ago. stable and current are continuously updated, while release is not. > > > During the install the disk format routine would only allow 4 partitions > > (9gb SCSI on adaptec 2940) - anything further was given the device entry > > "X" > > This is a limit of the PC architecture. FreeBSD does not nett PC > partitions like Linux (in BSD lingo, a partition is a "slice"). One > slice (PC lingo "partition") is enough to hold all the BSD partitions > you may think of. > > > After boot and kernel rebuild (for dual cpus ), we can't mount the > > CDROM for additional package installs (from /stand/sysinstall) - we get the > > error - "bad super block" > > Usually /stand/sysinstall is right about such things. > > > We have several FreeBSD systems, now spanning 3.2->4.1. I'm curious what > > schemes people are using to keep a group of systems updated as > > painlessly as possible. There are 3 fronts: The system software, the packages and > > the ports that we'd like to be able to keep synced among the systems. > > What has been successful? > > I got a playbox to check everything out, a production masterserver > containing the source happily making worl if the playbox was successful > up to all the tasks tested, and several production boxes, which get > updated when the need arises. > > Morale: if it ain't broken, don't fix it. > > Just my .02$ > -Christoph Sold - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39FF2BD9.6640F14A>