On 3/22/10, Dan Naumov <dan.nau...@gmail.com> wrote:
> The ZFS bootloader has been changed in 8-STABLE compared to
> 8.0-RELEASE. Reinstall your boot blocks.

Thanks for pointers, I will run gpart to reinstall bootcode on my SD card.


> Is there any particular reason you are upgrading from a production
> release to a development branch of the OS?

I've read that FreeBSD kernel supports 3D acceleration in ATI R7xx
chipset and as I own motherboard with HD3300 built-in I thought that I
would give it a try. I upgraded to see if there is any progress with
¿zfs? I don't really know if it's zfs related, but at certain load, my
system crashes, and reboots. It happens only when using bonnie++ to
benchmark I/O. And I'm a little bit to lazy to prepare my system for
coredumps - I don't have swap slice for crashdumps, because I wanted
to simplify adding drives to my raidz1 configuration. Could anyone
tell me what's needed, besides having swap to produce good crashdump?

At first I didn't knew that I am upgrading to bleeding edge/developer
branch of FreeBSD.  I'll come straight out with it,  8.0-STABLE sounds
more stable than 8.0-RELEASE-p2, which I was running before upgrade ;)
I'm a little confused with FreeBSD release cycle at first I compared
it with Debian release cycle,  because I'm most familiar to it, and I
used it a lot before using FreeBSD. Debian development is more
one-dimensional - unstable/testing/stable/oldstable whereas FreeBSD
has two stable branches - 8.0 and 7.2 which are actively developed.
But still I am confused with FreeBSD naming and it's relation with
tags which are used in standard-supfile. We have something like this:
9.0-CURRENT -> tag=.
8.0-STABLE -> tag=RELENG_8
8.0-RELEASE-p2 ->  tag=RELENG_8_0 ? (btw what does p2 mean?)
If someone patient could explain it to me I'd be grateful.
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Reply via email to