nothing i can do can make the pink line funnier, so i shan’t try.
Mar 28 21:19:23 qbert sendmail[23176]: k2SN1fN4023117: SYSERR(root): Error writing control file ./tfk2SN1fN4023177: I/O error
Mar 28 21:19:56 qbert scsi: WARNING: /pci@1f,4000/scsi@3/sd@0,0 (sd0):
Mar 28 21:19:56 qbert disk not responding to selection
Mar 28 21:19:56 qbert scsi: WARNING: /pci@1f,4000/scsi@3/sd@0,0 (sd0):
Mar 28 21:19:56 qbert disk not responding to selection
Mar 28 21:19:56 qbert ufs_log: WARNING: Error writing ufs log
Mar 28 21:19:56 qbert ufs_log: WARNING: ufs log for / changed state to Error
Mar 28 21:19:56 qbert ufs_log: WARNING: Please umount(1M) / and run fsck(1M)
[sld@qbert (SunOS)] /home/sld> df -k
ksh: df: not found
[sld@qbert (SunOS)] /home/sld> echo *
*
well, that’s not much of a good sign there. not that i expected one, but, y’know, stupid hope springs eternal.
[sld@qbert (SunOS)] /home/sld> cd /
ksh: /: bad directory
and that was about the part where i started laughing. my poor little computer! oh well. at least i saw it coming: it’d been making noises of vague unhappiness (even if not syslogging any actual errors) for like a month now, so i backed up the important bits to my other workstation. the only part i’m really bummed about is that since it blew up, well, everything, there’s no uptime to read the nonexistent utmp file so i could say what qbert’s uptime was at the time that it blew up. it was pushing two years, IIRC — it hadn’t cracked 700 yet, but it was probably up to the 690s. alas. poor little qbert. you were a good workstation.
