From owner-freebsd-questions Fri Oct 4 15:42: 4 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 D8C0137B401 for ; Fri, 4 Oct 2002 15:42:02 -0700 (PDT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48A8443E6E for ; Fri, 4 Oct 2002 15:42:02 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP id MUA74016; Fri, 04 Oct 2002 15:42:01 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Postfix) with ESMTP id 365685D04; Fri, 4 Oct 2002 15:42:01 -0700 (PDT) To: Marco Beishuizen Cc: freebsd-questions@FreeBSD.ORG Subject: Re: burncd error In-reply-to: Your message of "Sat, 05 Oct 2002 00:29:48 +0200." Date: Fri, 04 Oct 2002 15:42:01 -0700 From: "Kevin Oberman" Message-Id: <20021004224201.365685D04@ptavv.es.net> 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 > 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. 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