|
FreeBSD Installation and Upgrading Installing and upgrading FreeBSD. |
|
Thread Tools | Display Modes |
|
||||
The third attempt was successful. I saw an updated src/Makefile creep in during a csup. It may have something to do with it. I also cleared out the CPUTYPE setting from /etc/make.conf, though I hardly think that was the problem, since it's been in there for over a hundred builds on dozens of machines, ever since the pentium4 target was added. Anyhoo, back in business. Thanks for reading
|
|
|||
This bit me as well yesterday and now my email server is down
I hope to get it up soon, I used sysinstall to see if I could revert back to 7.0-RELEASE but I lost all access to the server after a reboot. I hope that it didn't mess everything up to much. |
|
||||
When I rebooted for the first time (after the first make installworld) I lost (remote) access to the server as well; it pinged, but no ports were open. When I had physical access to the machine I saw it hung right after an ntpdate command (during the loading of daemons). A simple Ctl+C set the wheels in motion again. It didn't happen a second time, though. The interesting thing was that all other binary stuff (/bin, /usr/bin, /usr/sbin, etc.) worked. Only cc and its associated helpers were actually in disrepair.
|
|
|||
All I have is remote access, I'm in London and the server is in Berlin.
I got my ISP on it so hopefully they can get me up and running soon. |
|
||||
When running -STABLE, always be sure to subscribe to the stable@freebsd.org mailing list. There was a big HEAD'S UP about this on the list yesterday. Everything should be working today, though.
|
|
|||
True but I've been running stable on my servers for as long as I can remember and this was the first time I had such a big failure. I finally am now able to get back into my system and I'm rebuilding everything.
|
|
||||
Quote:
Quote:
However, if you are using it in a work/production environment, where 99.95% uptime is generally expected (and that .05% is always announced days if not weeks in advance), those unexpected outages could mean some tense moments between you and your boss. |
|
||||
Ah, but in situations where you need 99.95% uptime, you have a testing environment setup where every little update gets tested before it hits the production servers, so there's not much risk to running -STABLE in that setup.
Bottom line to running -STABLE (or -CURRENT): subscribe to the relevant mailing list, and always stay a couple days behind the major MFCs and other imports. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
-Release vs. -Stable | guitarscn | OpenBSD Installation and Upgrading | 3 | 2nd October 2008 02:32 PM |
aaccli - stable | carpman | FreeBSD Ports and Packages | 0 | 9th July 2008 03:04 PM |
Running -stable and using packages | ai-danno | OpenBSD Installation and Upgrading | 4 | 4th June 2008 03:18 AM |
OpenBSD -STABLE | BSDfan666 | OpenBSD General | 6 | 21st May 2008 10:10 PM |
-stable question | jwhal | OpenBSD General | 9 | 15th May 2008 12:29 AM |