> Date: Sat, 5 Oct 2002 00:29:48 +0200 (CEST) > From: Marco Beishuizen <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > 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: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
