|
From: <hzu...@ra...> - 2004-01-06 14:46:01
|
On 01/06/2004 09:19:51 AM Diego Torres wrote: >On Mon, Jan 05, 2004 at 09:10:15PM -0500, Heiko Zuerker wrote: >> >>># CONFIG_NLS_KOI8_U is not set >> >>>-# CONFIG_NLS_UTF8 is not set >> >>>+CONFIG_NLS_UTF8=y >> >> >> >>Why are you setting UTF-8 as default ? > >i've been working with it, and i would like to propose some new changes >to the .config kernel file: > >CONFIG_NLS_DEFAULT="iso8859-15" >CONFIG_NLS_CODEPAGE_437=m >CONFIG_NLS_CODEPAGE_850=m >CONFIG_NLS_ISO8859_1=m >CONFIG_NLS_ISO8859_15=y >CONFIG_NLS_UTF8=m > >that is, everything as modules, and only 8859-15 inside the kernel. >heiko, if >everything is ok for you, say something :) I thought UTF-8 is the new standard? >more things: our glibc is updated? No, why? >and: > >CONFIG_CODA_FS=m > >i'll start doing some tests. the beauty of coda is that near everything >is >in userspace. That change you can do. Heiko |
|
From: <hzu...@ra...> - 2004-01-06 15:52:58
|
On 01/06/2004 09:58:31 AM Diego Torres wrote: >On Tue, Jan 06, 2004 at 09:36:33AM -0500, hzu...@ra... >wrote: > >> >CONFIG_NLS_DEFAULT="iso8859-15" >> >CONFIG_NLS_CODEPAGE_437=m >> >CONFIG_NLS_CODEPAGE_850=m >> >CONFIG_NLS_ISO8859_1=m >> >CONFIG_NLS_ISO8859_15=y >> >CONFIG_NLS_UTF8=m > >> >that is, everything as modules, and only 8859-15 inside the kernel. >> >heiko, if everything is ok for you, say something :) >> >> I thought UTF-8 is the new standard? > >yes, but after a lot of testing & reading i've changed my mind. with >utf-8 >you have multibyte characters representation (>127), and for example >midnightcommander is not ready. redhat has done a lot of work on >improving that, and they have patched versions of mc, mutt, etc, but >i don't like using them on dl. so lets clean things on 8859-15 (that >supports everyone using devil-linux) and leave utf-8 for dl2.0 :) > >also samba provides "unix charset" so the utf-8 default can be changed. > >This are the best documents i've found about utf-8 and 8859-15 support. >http://melkor.dnp.fmph.uniba.sk/~garabik/debian-utf8/howto.html >http://www.debian.org/doc/manuals/debian-euro-support/ch-configure.en.ht >ml Doesn't look like we got much of a choice... ;-) >> >more things: our glibc is updated? >> >> No, why? > >utf-8 needs the latests glibc available, i mean, latests glibc is needed >to use utf-8 :) We switch to the new glibc, once it comes out. >> >CONFIG_CODA_FS=m >> > >> >i'll start doing some tests. the beauty of coda is that near >everything >> >is in userspace. >> >> That change you can do. > >but i don't promise anything, since there is no beer :) The first step is getting the Kernel support up and running, then you can get a beer and work on the rest. Heiko |
|
From: Diego T. <dt...@co...> - 2004-01-06 16:55:29
|
On Tue, Jan 06, 2004 at 10:49:44AM -0500, hzu...@ra... wrote: > >but i don't promise anything, since there is no beer :) > > The first step is getting the Kernel support up and running, then you can > get a beer and work on the rest. how is everything going with 1.0.x? have we got a 2.4.24? i was surprised to hear that you're working/backporting things to dl1.0. aren't users upgrading to latest cvs' version? -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |
|
From: Bruce S. <bw...@ar...> - 2004-01-06 18:05:50
|
> i was surprised to hear that you're working/backporting things to dl1.0. > aren't users upgrading to latest cvs' version? 1.0 is the latest stable version. It still needs to have security and bug fixes. The average user should be using the 1.0 version. 1.1 is the development version, and may not always be completely stable. All new features and major changes go into 1.1, and it takes awhile to get all the bugs out. 1.0 only gets fixes, so it remains stable. Think of it like the Linux kernel. 2.5 is the development version, and at the same time 2.4 is still being maintained. Most end users are still using 2.4. (yeah, I know 2.6 is out now, but forget about that :) - BS |
|
From: <hzu...@ra...> - 2004-01-06 18:39:58
|
On 01/06/2004 01:05:48 PM Bruce Smith wrote: >> i was surprised to hear that you're working/backporting things to >dl1.0. >> aren't users upgrading to latest cvs' version? > >1.0 is the latest stable version. It still needs to have security and >bug fixes. The average user should be using the 1.0 version. > >1.1 is the development version, and may not always be completely stable. >All new features and major changes go into 1.1, and it takes awhile to >get all the bugs out. 1.0 only gets fixes, so it remains stable. > >Think of it like the Linux kernel. 2.5 is the development version, and >at the same time 2.4 is still being maintained. Most end users are >still using 2.4. (yeah, I know 2.6 is out now, but forget about that :) There's not much I can add there, except that the i486 version of 1.0.4 already is on SF and the FTP Server. i686 is still compiling ( I NEED A FASTER BUILD MACHINE). Heiko |
|
From: Diego T. <dt...@co...> - 2004-01-06 19:04:02
|
On Tue, Jan 06, 2004 at 01:12:32PM -0500, hzu...@ra... wrote: > There's not much I can add there, except that the i486 version of 1.0.4 > already is on SF and the FTP Server. > i686 is still compiling ( I NEED A FASTER BUILD MACHINE). me too :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |
|
From: Diego T. <dt...@co...> - 2004-01-06 14:58:56
|
On Tue, Jan 06, 2004 at 09:36:33AM -0500, hzu...@ra... wrote: > >CONFIG_NLS_DEFAULT="iso8859-15" > >CONFIG_NLS_CODEPAGE_437=m > >CONFIG_NLS_CODEPAGE_850=m > >CONFIG_NLS_ISO8859_1=m > >CONFIG_NLS_ISO8859_15=y > >CONFIG_NLS_UTF8=m > >that is, everything as modules, and only 8859-15 inside the kernel. > >heiko, if everything is ok for you, say something :) > > I thought UTF-8 is the new standard? yes, but after a lot of testing & reading i've changed my mind. with utf-8 you have multibyte characters representation (>127), and for example midnightcommander is not ready. redhat has done a lot of work on improving that, and they have patched versions of mc, mutt, etc, but i don't like using them on dl. so lets clean things on 8859-15 (that supports everyone using devil-linux) and leave utf-8 for dl2.0 :) also samba provides "unix charset" so the utf-8 default can be changed. This are the best documents i've found about utf-8 and 8859-15 support. http://melkor.dnp.fmph.uniba.sk/~garabik/debian-utf8/howto.html http://www.debian.org/doc/manuals/debian-euro-support/ch-configure.en.html > > >more things: our glibc is updated? > > No, why? utf-8 needs the latests glibc available, i mean, latests glibc is needed to use utf-8 :) > >CONFIG_CODA_FS=m > > > >i'll start doing some tests. the beauty of coda is that near everything > >is in userspace. > > That change you can do. but i don't promise anything, since there is no beer :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |