Launched in 2004, dmesgd aims to provide a user-submitted repository of searchable *BSD dmesgs. The dmesg(8) command displays the system message buffer's content, and during boot a copy is saved to /var/run/dmesg.boot. This buffer contains the operating system release, name and version, a list of devices identified, plus a whole host of other useful information. We hope others find this resource useful and further contribute to its growth. Contact us at [ admin at lists dot nycbug dot org ].
Date: 2005-02-10 13:33:23
From: euro-au
Description: VAX 4000-m300 (Pele). 128mb ram KA-670 cpu 8VUPs of T-T-T-T-throbbing poweh uNF!
trion: {26} dmesg NetBSD 2.0 ([_EMAIL_XXXXXXXXXXXXXX] $) #0: Fri Dec 3 07:35:03 GMT+8 2004 uridium@trion:/usr/src/sys/arch/vax/compile/trion VAX 4000/300 cpu0: KA670, ucode rev 17 total memory = 127 MB avail memory = 121 MB mainbus0 (root) ibus0 at mainbus0 ze0 at ibus0 ze0: hardware address [_MAC_XXXXXXXXXX] device shac at ibus0 not configured uba0 at ibus0: Q22 uda0 at uba0 csr 172150 vec 774 ipl 17 mscpbus0 at uda0: version 6 model 13 mscpbus0: DMA burst size set to 4 ra0 at mscpbus0 drive 0: RA90 ra1 at mscpbus0 drive 3: RRD40 Kernelized RAIDframe activated ra0: size 2055033 sectors ra1: no disk label: size 208600 sectors boot device: ra0 root on ra0a dumps on ra0b root file system type: ffs trion: {27} uname -a NetBSD trion 2.0 NetBSD 2.0 ([_EMAIL_XXXXXXXXXXXXXX] $) #0: Fri Dec 3 07:35:03 GMT+8 2004 uridium@trion:/usr/src/sys/arch/vax/compile/trion vax trion: {28}