Date: Sat, 6 Apr 1996 16:24:55 +0200 (MET DST) From: =?iso-8859-1?Q?=22=C5ge?= =?iso-8859-1?Q?R=F8bekk=22?= <aagero@aage.priv.no> To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-bugs@freebsd.org Subject: Re: Hangs after editing a disklabel Message-ID: <199604061424.QAA01975@birk04.studby.uio.no> In-Reply-To: <199604061351.PAA01053@uriah.heep.sax.de> (message from J Wunsch on Sat, 6 Apr 1996 15:51:30 %2B0200 (MET DST))
next in thread | previous in thread | raw e-mail | index | archive | help
| > I sent to 3 different accounts, all of which received the mail with | > these header fields. The only known problem is that the From:-field | > does not have a proper rfc1522-encoding. | | ...and ``ISO-8859-1'' not being uppercase. :-) That seems to confuse | elm, so it finally claims it's unknown-8bit. I've corrected the | charset name in this mail manually, and restarted elm, now it works. rfc1522, line 145: Both "encoding" and "charset" names are case-independent. Thus the charset name "ISO-8859-1" is equivalent to "iso-8859-1", and the encoding named "Q" may be spelled either "Q" or "q". | > Same problem. What else than a cosmetic change is it to use sd0 | > instead of rsd0c. | | Since you don't need to know whether the correct device is /dev/rsd0, | /dev/rsd0c, /dev/rsd0d, /dev/rsd0s1, /dev/rsd0s1c, /dev/rsd0s1d, | /dev/rsd0.ctl, or whatever it might be tomorrow. ah ok. | > And since this does not leave a core dump, it's hard | > to identify the cause. | | You probably need DDB for it. I'm using X most of the time, so there might be some console output which I am not able to read. Is it possible to make the panic routine switch to the console? -aage
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604061424.QAA01975>