Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Also, when doing a lot of things at once, for example backup/reinstall/restore... (Or even scarier, upgrade a VPS's OS in place, remove several user accounts, replace one web app with another, and upgrade WordPress -- you get the idea.) I've found it's a good idea to take things slowly and reboot a lot. The Linux OS ecosystem has a lot of hidden traps where you can seriously break your system and not actually find out until a reboot or a power failure; an intentional reboot is a kind of smoke test for that kind of user error or packager error because you find out pretty soon after the failure occurred. On Fri, Dec 14, 2012 at 7:28 AM, Jerry Feldman <gaf at blu.org> wrote: > Most crashes are caused by cockpit error. > > On 12/13/2012 09:43 PM, Will Rico wrote: > > Well, I tracked down the culprit in this mystery and the trail pointed > > to dumb user, not bad video driver. >
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |