>> -current for my laptop is TOTALLY BROKEN right now. >> I am building a modified version of -current right now.
the only reason was for you was kettenis@ http://www.openbsd.org/cgi-bin/cvsweb/src/sys/arch/amd64/pci/pci_machdep.c "I'm sick and tired of people doing misalgned reads and writes to PCI config space and not noticing because they only test on amd64. So enforce alignment there as well, at least for a little while such that we find those bugs and force people to fix them." >> This version may or may NOT work. >> >> -current is OFTEN BROKEN. >> -current is often broken just for certain particular computers. >> -current often breaks packages only. These packages may need to be modified >> and re-compiled! >> >> -current is great, but very risky. You may do everything perfect and still >> get a broken system! >> >> If you fail to boot and get >> ddb> >> >> or it freezes up without warning, you will have to fix those problems. >> >> Sometimes -current works perfectly, sometimes not. >> >> Chris Bennett >> > > Odd. I've been running -current, upgrading various architectures almost > weekly, for more than a decade. I can't recall more than a couple of > times where -current wasn't working. > > It does happen, but rarely and usually only for a very particular set > of machines. e.g. with a particular driver. I would expect -current would probably break right around hackathons, but that is to be expected. Just before a hackathon, sync your tree, and sync your tree a few days after the hackathon. Or if the devs ask to test features. Or tree breaks, when the devs WANT it to break to flush out the bugs. Otherwise it usually doesn't break. When I pointed it out privately to some guy a few months ago, he put me in his killfile. go figure...
