Date: Sat, 5 Oct 2002 01:02:15 +0200 (CEST) From: Marco Beishuizen <mbeis@wxs.nl> To: Kevin Oberman <oberman@es.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: burncd error Message-ID: <Pine.BSF.4.44.0210050050160.88118-100000@yokozuna.bsd> In-Reply-To: <20021004224201.365685D04@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <mbeis@wxs.nl> > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.44.0210050050160.88118-100000>