From owner-freebsd-questions Fri Oct 4 16: 2:20 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4603937B401 for ; Fri, 4 Oct 2002 16:02:18 -0700 (PDT) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5166D43E6E for ; Fri, 4 Oct 2002 16:02:17 -0700 (PDT) (envelope-from mbeis@wxs.nl) Received: from yokozuna.bsd ([213.10.35.60]) by smtp02.wxs.nl (Netscape Messaging Server 4.15) with ESMTP id H3HBZS01.DCT; Sat, 5 Oct 2002 01:02:16 +0200 Date: Sat, 5 Oct 2002 01:02:15 +0200 (CEST) From: Marco Beishuizen Reply-To: Marco Beishuizen To: Kevin Oberman Cc: freebsd-questions@FreeBSD.ORG Subject: Re: burncd error In-Reply-To: <20021004224201.365685D04@ptavv.es.net> Message-ID: Homepage: FreeBSD: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 4 Oct 2002, the wise Kevin Oberman spoke, and said: > > Date: Sat, 5 Oct 2002 00:29:48 +0200 (CEST) > > From: Marco Beishuizen > > Sender: mbeis@yokozuna.bsd > > > > Thanks! It worked great. I have one remark though: the option > > "-allow-lower-case" wasn't recognised by mkisofs. Looking at the manpage > > it should be "-allow-lowercase". :-) But this was of course one of those > > days... > > I really should have done a cut and paste on the command or pulled in > my shell script that runs mkisofs, but it's on a different system and > it seemed easier to just type it in. > > > > Eventually, I didn't use the option "-allow-lowercase", but the cd has no > > problems of using lowercase characters. All files I copied to the cd show > > up like the way they appear in FreeBSD. > > I suspected that both -allow-lowercase and -allow-multidot were > implicit in -r, but I had never actually tried it. > > > The remarkable thing was actually, that when I used the wrong option, > > mkisofs says it doesn't recognise the option, quits the program, and > > returns to the prompt in my xterm, but now my xterm shows up with > > unrecognisable characters (normally for me: root@hostname, now something > > like: %^(%^%(%^&()_)_*). > > > > Did I hit a bug? > > Could you have wound up using a different character set? If you do a > hard reset on the xterm, does it start working right? Do characters > echo correctly? I'll admit that I have never seen this. I never changed my character set since I installed FreeBSD. I did change it in applications such as Pine and LyX from ISO-8859-1 to ISO-8859-15 for special characters used in Europe, but never system wide. I am using the standard bourne shell in FreeBSD by the way. When I exit the xterm and restart it the problem is gone, and works it ok. > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > Marco -- So far as I can remember, there is not one word in the Gospels in praise of intelligence. -- Bertrand Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message