Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: Bootscreen | Date | 28 Jan 2003 10:46:04 -0800 |
| |
Followup to: <200301281515.15611.roy@karlsbakk.net> By author: Roy Sigurd Karlsbakk <roy@karlsbakk.net> In newsgroup: linux.dev.kernel > > You'll never send an engineer out to replace a set-top-box. You'll just wait > for the customer to return the box and send out a new one. Software doesn't > fail on those - it's some 99.9% hardware failure. If you get a hang or panic > or something, the boxes usually have watchdogs to take care of that (and then > reboot automatically). The average computer-frightened user getting an STB > from the VoD/IPTV company (or her ISP) don't want to see any kernel > gibberish. They just want a nice splash screen telling them "everything's > gonna be alright in 45 seconds" or something. Trouble shooting is > done in the lab after the box is returned >
Right, which is why those boxes when running Linux invariably direct their kernel messages to a debugging port of some sort (usually a serial port.)
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |