Bug#312554: libc6: if_nameindex(3) returns broken list of network interfaces
On Wed, Jun 08, 2005 at 08:30:42PM +0200, Hans Ulrich Niedermann wrote: The returned list - does not contain all network interface names like the man page says. It only includes those which have an IPv4 address configured on them. - does not contain one [structure] for every interface present like the libc6 info page says. It contains one if_nameindex structure for every IPv4 address configured on the interface. Well, glibc 2.3.2 uses ioctl(SIOCGIFCONF) to get the list of network addresses. However the Linux kernel implements this ioctl for IPV4 only, and the IPV4 implementation returns one ifconf structure for every configured address. So what are you seeing is just glibc reporting whatever it gets from the kernel. You can try glibc 2.3.5 from experimental which AFAIK uses netlink instead of SIOCGIFCONF. However that may bring other problems since netlink is not a reliable protocol and it may drop messages if the machine is loaded. Gabor -- - MTA SZTAKI Computer and Automation Research Institute Hungarian Academy of Sciences - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Rolex Replica Bernadette
REPLICASONLINE - WE NEVER COMPROMISE ON QUALITY Rolex replica is our speciality We guarantee lowest prices and highest quality We are the Direct manufacturers. For top quality rolex watchs pleas visit: http://www.chooseyourwatch4u.com cayuga sm mckenna fyk [2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ppc64 biarch toolchain and 64bit powerpc kernels ...
Hello, Now that sarge is released, and we are concentrating on the upcoming etch release, as shown with the new c++ toolchain announcement from doko, i plan to retire the 32bit kernels for power3 and power4, and to pass as soon as possible to 64bit kernels for those arches. I have already built a -pseries version, which altough not power4 optimized, will run on everything but legacy iseries (those predating the power5 ones), which was successfully tested on both pmacs G5 (a dying race now it seems though), and IBM power5 boxes (altough the ones with logical partitions still seem to be somewhat buggy). And plan to do a -legacy-iseries build as well as a power4 optimized version in the near future. These kernels where built in a sarge chroot using the ubuntu biarch ppc64 toolchain, and i am already building .udebs for those kernels, as well as daily d-i images, and have an unofficial .udeb archive which will provide those .udebs. I lacked time to patch base-installer and net-fetcher or whatever it is called to get the .udebs from there though, and would like these packages to get integrated in sid and then etch as fast as possible, to make testing of this stuff easier. So, i would like to ask the debian toolchain maintainers what is the expected timeframe to get a ppc64 biarch toolchain in sid or even experimental ? Or should i rely on the ubuntu toolchain, and use that to upload kernels to sid in the near future ? Together with a statically built procps naturally ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ppc64 biarch toolchain and 64bit powerpc kernels ...
On Fri, Jun 10, 2005 at 07:09:51PM +0200, Sven Luther wrote: timeframe to get a ppc64 biarch toolchain in sid or even experimental ? Or should i rely on the ubuntu toolchain, and use that to upload kernels to sid in the near future ? Together with a statically built procps naturally ? The sid procpc works just fine with ppc64 kernel, no need to mess with it at all. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312902: Missing UTF-8 locales
Package: locales Version: 2.3.2.ds1-22 Severity: normal Hi, The following locales exist in SUPPORTED, but lack a UTF-8 variant. aa_DJ af_ZA an_ES br_FR bs_BA gd_GB ka_GE lg_UG mi_NZ oc_FR om_KE so_DJ so_KE so_SO tg_TJ tl_PH uz_UZ yi_US zh_SG It would be great if all our locales support UTF-8 for etch. I'm not familiar with glibc locale data, but if there's any grunt work I can do to help with this, I'm very willing to assist. Regards, Roger -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-rc6 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages locales depends on: ii debconf 1.4.51 Debian configuration management sy ii libc6 [glibc-2.3.2.ds1-22] 2.3.2.ds1-22 GNU C Library: Shared libraries an -- debconf information: * locales/default_environment_locale: None * locales/locales_to_be_generated: aa_ER UTF-8, aa_ET UTF-8, am_ET UTF-8, ar_AE.UTF-8 UTF-8, ar_BH.UTF-8 UTF-8, ar_DZ.UTF-8 UTF-8, ar_EG.UTF-8 UTF-8, ar_IN UTF-8, ar_IQ.UTF-8 UTF-8, ar_JO.UTF-8 UTF-8, ar_KW.UTF-8 UTF-8, ar_LB.UTF-8 UTF-8, ar_LY.UTF-8 UTF-8, ar_MA.UTF-8 UTF-8, ar_OM.UTF-8 UTF-8, ar_QA.UTF-8 UTF-8, ar_SA.UTF-8 UTF-8, ar_SD.UTF-8 UTF-8, ar_SY.UTF-8 UTF-8, ar_TN.UTF-8 UTF-8, ar_YE.UTF-8 UTF-8, be_BY.UTF-8 UTF-8, bg_BG.UTF-8 UTF-8, bn_BD UTF-8, bn_IN UTF-8, byn_ER UTF-8, ca_ES.UTF-8 UTF-8, cs_CZ.UTF-8 UTF-8, cy_GB.UTF-8 UTF-8, da_DK.UTF-8 UTF-8, de_AT.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, de_BE.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, de_CH.UTF-8 UTF-8, de_DE.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, de_LU.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, el_GR.UTF-8 UTF-8, en_AU.UTF-8 UTF-8, en_BW.UTF-8 UTF-8, en_CA.UTF-8 UTF-8, en_DK.UTF-8 UTF-8, en_GB.UTF-8 UTF-8, en_HK.UTF-8 UTF-8, en_IE.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, en_IN UTF-8, en_NZ.UTF-8 UTF-8, en_SG.UTF-8 UTF-8, en_US.UT F-8 UTF-8, en_ZA.UTF-8 UTF-8, en_ZW.UTF-8 UTF-8, es_AR.UTF-8 UTF-8, es_BO.UTF-8 UTF-8, es_CL.UTF-8 UTF-8, es_CO.UTF-8 UTF-8, es_CR.UTF-8 UTF-8, es_DO.UTF-8 UTF-8, es_EC.UTF-8 UTF-8, es_ES.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, es_GT.UTF-8 UTF-8, es_HN.UTF-8 UTF-8, es_MX.UTF-8 UTF-8, es_NI.UTF-8 UTF-8, es_PA.UTF-8 UTF-8, es_PE.UTF-8 UTF-8, es_PR.UTF-8 UTF-8, es_PY.UTF-8 UTF-8, es_SV.UTF-8 UTF-8, es_US.UTF-8 UTF-8, es_UY.UTF-8 UTF-8, es_VE.UTF-8 UTF-8, et_EE.UTF-8 UTF-8, eu_ES.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, eu_FR.UTF-8 UTF-8, fa_IR UTF-8, fi_FI.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, fo_FO.UTF-8 UTF-8, fr_BE.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, fr_CA.UTF-8 UTF-8, fr_CH.UTF-8 UTF-8, fr_FR.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, fr_LU.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, ga_IE.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, [EMAIL PROTECTED] UTF-8, [EMAIL PROTECTED] UTF-8, gl_ES.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, gv_GB.UTF-8 UTF-8, he_IL.UTF-8 UTF-8, hi_IN UTF-8, hr_HR.UTF-8 UTF-8, hu_HU.UTF-8 U TF-8, id_ID.UTF-8 UTF-8, is_IS.UTF-8 UTF-8, it_CH.UTF-8 UTF-8, it_IT.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, iw_IL.UTF-8 UTF-8, ja_JP.UTF-8 UTF-8, kl_GL.UTF-8 UTF-8, kn_IN UTF-8, ko_KR.UTF-8 UTF-8, kw_GB.UTF-8 UTF-8, lo_LA UTF-8, lt_LT.UTF-8 UTF-8, lv_LV.UTF-8 UTF-8, mk_MK.UTF-8 UTF-8, ml_IN UTF-8, mn_MN UTF-8, mr_IN UTF-8, ms_MY.UTF-8 UTF-8, mt_MT.UTF-8 UTF-8, nb_NO.UTF-8 UTF-8, ne_NP UTF-8, nl_BE.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, nl_NL.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, nn_NO.UTF-8 UTF-8, no_NO.UTF-8 UTF-8, om_ET UTF-8, pa_IN UTF-8, pl_PL.UTF-8 UTF-8, pt_BR.UTF-8 UTF-8, pt_PT.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, ro_RO.UTF-8 UTF-8, ru_RU.UTF-8 UTF-8, ru_UA.UTF-8 UTF-8, se_NO UTF-8, sid_ET UTF-8, sk_SK.UTF-8 UTF-8, sl_SI.UTF-8 UTF-8, so_ET UTF-8, sq_AL.UTF-8 UTF-8, sr_YU.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, st_ZA.UTF-8 UTF-8, sv_FI.UTF-8 UTF-8, [EMAIL PROTECTED] UTF-8, sv_SE.UTF-8 UTF-8, ta_IN UTF-8, te_IN UTF-8, th_TH.UTF-8 UTF-8, ti_ER UTF-8, ti_ET UTF-8, tig_ER UTF-8 , tr_TR.UTF-8 UTF-8, tt_RU.UTF-8 UTF-8, uk_UA.UTF-8 UTF-8, ur_PK UTF-8, [EMAIL PROTECTED] UTF-8, vi_VN UTF-8, wa_BE.UTF-8 UTF-8, xh_ZA.UTF-8 UTF-8, zh_CN.UTF-8 UTF-8, zh_HK.UTF-8 UTF-8, zh_TW.UTF-8 UTF-8, zu_ZA.UTF-8 UTF-8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ppc64 biarch toolchain and 64bit powerpc kernels ...
On Fri, Jun 10, 2005 at 07:16:02PM +0200, Christoph Hellwig wrote: On Fri, Jun 10, 2005 at 07:09:51PM +0200, Sven Luther wrote: timeframe to get a ppc64 biarch toolchain in sid or even experimental ? Or should i rely on the ubuntu toolchain, and use that to upload kernels to sid in the near future ? Together with a statically built procps naturally ? The sid procpc works just fine with ppc64 kernel, no need to mess with it at all. Oh, fine, so there is no risk of overflow of the process id. What about the sarge procps ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ppc64 biarch toolchain and 64bit powerpc kernels ...
On Fri, Jun 10, 2005 at 07:36:08PM +0200, Sven Luther wrote: On Fri, Jun 10, 2005 at 07:16:02PM +0200, Christoph Hellwig wrote: On Fri, Jun 10, 2005 at 07:09:51PM +0200, Sven Luther wrote: timeframe to get a ppc64 biarch toolchain in sid or even experimental ? Or should i rely on the ubuntu toolchain, and use that to upload kernels to sid in the near future ? Together with a statically built procps naturally ? The sid procpc works just fine with ppc64 kernel, no need to mess with it at all. Oh, fine, so there is no risk of overflow of the process id. The process id in Linux is always 32bits, and unless you tweak /proc/sys/kernel/pid-max the actual range used is even smaller. What about the sarge procps ? It shouldn't be any different. I have been running ppc64 kernels with sarge for a long time. And if there's a bug in procps somewhere where it can't deal with some fields beeing bigger in 64bit kernels that should be fixed in procps instead of needing another set of binaries. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Looking for cheap high-quality software?
Shopping for software? Now in your language currency! http://nvc.8xcnb781ni8fn98.goodingdn.com Union gives strength. Human excellence means nothing unless it works with the consent of God. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ppc64 biarch toolchain and 64bit powerpc kernels ...
On Fri, Jun 10, 2005 at 07:09:51PM +0200, Sven Luther wrote: Or should i rely on the ubuntu toolchain, and use that to upload kernels to sid in the near future ? *NO.* There is no excuse for uploading packages to unstable/main that can't be built using Debian! -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#312927: glibc: Please use UTF-8 as the default locale codeset
Package: glibc
Severity: normal
Tags: patch
Hi,
UTF-8 is now ready for use as the default character set in Debian.
Most other major distributions (e.g. RedHat, SuSE) switched to
UTF-8 last year, if not before. We should seriously consider doing
the same.
The current locale package allows one to choose the locales to generate
using debconf, and takes the list from i18n/SUPPORTED. I don't for one
moment propose to drop any supported locales. The following patch
reorders SUPPORTED when embedding the list in locales.config, so that
UTF-8 locales are listed before all other locales, which are placed at
the end of the list. I've also added a small note to the debconf
template to make the user aware that UTF-8 locales are recommended, but
the other locales are still available should they be needed.
Regards,
Roger
--- glibc-2.3.2.ds1.old/debian/rules.d/debhelper.mk 2005-06-10
11:04:53.0 +0100
+++ glibc-2.3.2.ds1/debian/rules.d/debhelper.mk 2005-06-10 21:22:07.0
+0100
@@ -225,7 +225,7 @@
done
# Substitute __SUPPORTED_LOCALES__.
- perl -i -pe 'BEGIN {undef $$/; open(IN,
debian/tmp-libc/usr/share/i18n/SUPPORTED); $$j=IN;}
s/__SUPPORTED_LOCALES__/$$j/g;' debian/locales.config
+ perl -i -pe 'BEGIN {open(IN,
debian/tmp-libc/usr/share/i18n/SUPPORTED); $$u = $$j = ; while (IN) { if
(/UTF\-8/) { $$u .= $$_; } else { $$j .= $$_; } } $$u .= $$j;}
s/__SUPPORTED_LOCALES__/$$u/g;' debian/locales.config
# Generate common substvars files.
echo locale:Depends=$(shell perl debian/debver2localesdep.pl
$(DEB_VERSION)) tmp.substvars
--- glibc-2.3.2.ds1.old/debian/debhelper.in/locales.templates 2005-06-10
11:04:53.0 +0100
+++ glibc-2.3.2.ds1/debian/debhelper.in/locales.templates 2005-06-10
21:35:57.0 +0100
@@ -8,6 +8,10 @@
Choose which locales to generate. The selection will be saved to
`/etc/locale.gen', which you can also edit manually (you need to run
`locale-gen' afterwards).
+ .
+ UTF-8 locales are recommended. Locales using old national character sets
+ are provided for backwards-compatibility, but should not be used unless
+ strictly required.
Template: locales/default_environment_locale
Type: select
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-rc6
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#310550: marked as done (locales: locale-gen fails: cannot lock locale archive)
Your message dated Fri, 10 Jun 2005 23:46:48 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#310550: locale-gen fails: cannot lock locale archive has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 24 May 2005 10:30:08 + From [EMAIL PROTECTED] Tue May 24 03:30:07 2005 Return-path: [EMAIL PROTECTED] Received: from postman4.arcor-online.net (postman.arcor.de) [151.189.20.158] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DaWfn-S4-00; Tue, 24 May 2005 03:30:07 -0700 Received: from [127.0.0.1] (G16d6.g.pppool.de [80.185.22.214]) (authenticated bits=0) by postman.arcor.de (8.13.4/8.13.4) with ESMTP id j4OAU3gN018002; Tue, 24 May 2005 12:30:04 +0200 (MEST) Message-Id: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Rolf Leggewie [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: locales: locale-gen fails: cannot lock locale archive X-Mailer: reportbug 3.8 Date: Tue, 24 May 2005 12:11:21 +0200 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: locales Version: 2.3.2.ds1-21 Severity: important Hi, for some reason I do not fully understand locale-gen fails on my system. The only thing unusual in this respect is that /usr is mounted over NFS (usually ro, but set to rw before calling locale-gen). no-root-squash is set for the exported directory corresponding to /usr. Here is the output. # locale-gen Generating locales... de_DE.ISO-8859-1... done [EMAIL PROTECTED] lock locale archive /usr/lib/locale/locale-archive: Permission denied Best regards Rolf Leggewie -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: [EMAIL PROTECTED], LC_CTYPE=ja_JP.eucJP (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Versions of packages locales depends on: ii debconf 1.4.30.13Debian configuration management sy ii libc6 [glibc-2.3.2.ds1-21] 2.3.2.ds1-21 GNU C Library: Shared libraries an -- debconf information: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = C, LC_ALL = (unset), LC_MONETARY = C, LC_NUMERIC = C, LC_MESSAGES = ja_JP.eucJP, LC_COLLATE = C, LC_CTYPE = ja_JP.eucJP, LC_TIME = C, LANG = [EMAIL PROTECTED] are supported and installed on your system. perl: warning: Falling back to the standard locale (C). locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory * locales/default_environment_locale: None * locales/locales_to_be_generated: de_DE ISO-8859-1, [EMAIL PROTECTED] UTF-8, [EMAIL PROTECTED] ISO-8859-15, en_US.ISO-8859-15 ISO-8859-15, en_US.UTF-8 UTF-8, ja_JP.EUC-JP EUC-JP, ja_JP.UTF-8 UTF-8 --- Received: (at 310550-done) by bugs.debian.org; 10 Jun 2005 21:49:47 + From [EMAIL PROTECTED] Fri Jun 10 14:49:47 2005 Return-path: [EMAIL PROTECTED] Received: from main.uucpssh.org [212.27.33.224] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DgrNq-0002FF-00; Fri, 10 Jun 2005 14:49:47 -0700 Received: from localhost (localhost [127.0.0.1]) by main.uucpssh.org (Postfix) with ESMTP id 0752B7CA2C for [EMAIL PROTECTED]; Fri, 10 Jun 2005 23:49:44 +0200 (CEST) Received: by main.uucpssh.org (Postfix, from userid 10) id C10F77CB38; Fri, 10 Jun 2005 23:49:43 +0200 (CEST) Received: by localhost.localdomain (Postfix, from userid 1000) id 6640123D56; Fri, 10 Jun 2005 23:46:48 +0200 (CEST) Date: Fri, 10 Jun 2005 23:46:48 +0200 To: [EMAIL PROTECTED] Subject: Re: Bug#310550: locale-gen fails: cannot lock locale archive Message-ID: [EMAIL PROTECTED] References: [EMAIL
