[lug] How can I test a codepage module?
mhirsch at nubridges.com
Fri Aug 23 07:22:26 MDT 2002
On Thu, 2002-08-22 at 21:10, D. Stimits wrote:
> Michael Hirsch wrote:
> > I have a production box that has a kernel which doesn't have the
> > standard code pages installed on it. It doesn't appear to be a problem,
> > but there are errors in /var/log/messages.
> > I compiled those modules, and have a test machine with the same kernel.
> > The modules load fine on the test machine, but I have no idea how to
> > test whether they are working. I don't know how to generate the errors
> > at will. The only way I know to test would be to install the modules on
> > the production machine, but I'd *really* like to test them, first.
> > So, how can I force codepage to be used? The ones in question are the
> > standard wester european ones: nls_iso8859-1 nls_cp437
> > Any tips appreciated. This has long been a mystery to me, but I never
> > really needed to understand it, before.
> > Thanks,
> > Michael
> If you logged in to a regular console, and used a text-based web browser
> (e.g., lynx), and went to a web page using that character set, maybe it
> would show up correctly. I'm not sure if using an X11-based browser
> would depend on the same support, maybe it would use other fonts.
Thanks, that should work. I found another way. For some reason smbfs
wants these code pages when it mounts a windows share. I could generate
error messages by mounting share. After installing the modules the
messages went away.
More information about the LUG