Cool! I think what happened is that the JFS module couldn't map one of
the characters to the current locale's charset, so it ended up mapping the
unprintable character to the character designated for an unprintable
character. And when you try to delete the file with the unprintable
character, it
Mark K. Kim wrote:
Cool! I think what happened is that the JFS module couldn't map one of
the characters to the current locale's charset, so it ended up mapping the
unprintable character to the character designated for an unprintable
character. And when you try to delete the file with the
i think this is a bug on named that was shipped with rh8...
but this is not present on the current named..
On Thursday 27 May 2004 02:35, Ehrhart, Jay wrote:
I have seen this on my Red Hat 8.0 DNS server. Most of the time I can
/etc/init.d/named stop and then start will work. Sometimes
hello there.
anybody can guide me to useful link on settiup up
sendmail + spamassassin.
my sendmail works fine. my spamassassin installed
successfully.
my problem is it seems that sendmail does not know
that spamassassin is existing therefore
spamassassin is not working together with
On Thu 27 May 04, 2:47 PM, Milver S. Nisay [EMAIL PROTECTED] said:
hello there.
anybody can guide me to useful link on settiup up sendmail + spamassassin.
my sendmail works fine. my spamassassin installed successfully.
my problem is it seems that sendmail does not know that
Milver S. Nisay said:
hello there.
anybody can guide me to useful link on settiup up sendmail + spamassassin.
my sendmail works fine. my spamassassin installed successfully.
my problem is it seems that sendmail does not know that spamassassin is
existing therefore
spamassassin is not working
Mark K. Kim wrote:
snip
It's weird that Daniel's kernel didn't have UTF-8 support! I figured it'd
be supported by default
snip
What are the recommended character sets to have in a kernel? Obviously,
it will depend on whether you want exotic languages support. But for
the Joe Shmoe English
Jonathan Stickel said:
Mark K. Kim wrote:
snip
It's weird that Daniel's kernel didn't have UTF-8 support! I figured
it'd
be supported by default
snip
What are the recommended character sets to have in a kernel? Obviously,
it will depend on whether you want exotic languages support. But
I recommend ISO-8859-1 and UTF-8. ISO-8859-1 can handle most latin-based
languages, including English (and is probably the default for everything
you do on the system). UTF-8 *can* handle all other languages, though
whether it will or not depends on the actual charset of the system you're
trying