Date: Wed, 4 Oct 2000 21:01:30 -0500 From: Jim Graham <jim@n5ial.gnt.net> To: freebsd-questions@freebsd.org Subject: FreeBSD 4.1.1: problems with Joliet CDs, xterm, and xconsole Message-ID: <20001004210130.A6509@n5ial.gnt.net>
next in thread | raw e-mail | index | archive | help
First, I'm a brand new FreeBSD user (old Unix user...new to FreeBSD),
and have not yet joined the mailing list. I apologize for having to
ask this, but please CC me at jim@n5ial.gnt.net for now.
I've run into three problems so far that I haven't found answers on:
1) Joliet CDs ... put simply, the Joliet extensions seem to be
ignored. When I mount a CD that I created at work (where I'm
stuck with Windoze boxes), the CD is mounted, but the filenames
are all garbled 8.3 filenames. What am I doing wrong? I *REALLY*
need to be able to read CDs created from work...and if I have to
go back and re-create all of them w/o Joliet, it's going to be a
serious PITA.....
2) I've noticed that, quite often, output to an xterm ends up clobbering
the root window (at seemingly random locations) instead of going to
the xterm itself. Any idea what might be causing that? This is a
completely new one to me..... Btw, it is *NOT* console output. That
would be too easy to explain. It's just output from things like a
compile, reading a man page, etc.
3) Even after reading the FAQ ("When I run xconsole, I get ``Couldn't open
console''), and editing fbtab as specified (and, FWIW, even after a
reboot after a kernel build), I can't open the console using xconsole
unless I use xdm. Ok, temporary solution, use xdm. But is there a
solution that will work with startx? Or have I just missed something?
Oh, and one other thing.... When I installed vim from the ports
distribution, I noticed a major problem when trying to exit...I get a
message saying something along the lines of "Vim finished" (or close to
that), but vim doesn't actually exit until I use ^Z followed by kill %1.
My solution is (I hope---I'll be trying this shortly) to fall back on an
older vim (which I use everywhere else) that I'll compile myself, but I'd
still like to know if anyone else has seen this, and what they did to fix
it.... If nothing else, I'd just like to find out what I'm doing wrong!
:-)
Suggestions? Comments? Help? All appreciated....
Thanks,
--jim
PS: Thanks to this list, btw, for *SOLVING* a problem that I ran into
the first night with this new computer (AMD 650 MHz Athlon)....
Using the FreeBSD 4.0 CD that I had Monday, the system refused to
boot (conflict with the motherboard's anti-virus nonsense). A post
on this list confirmed for me that the new 4.1.1 CD I got the next
day would work. That was a big relief, and I needed it...so thanks!
--
73 DE N5IAL (/4) | "This 'telephone' has too many shortcomings to be
jim@n5ial.gnt.net | seriously considered as a means of communication.
ICBM / Hurricane: | The device is inherently of no value to us."
30.39735N 86.60439W | --Western Union internal memo, 1876
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?20001004210130.A6509>