Re: Bug#277972: glibc: Please change the remaining instances of 'lib64' to 'lib' on amd64
On 04-Oct-24 23:24, Kurt Roeckx wrote: On Sun, Oct 24, 2004 at 10:18:15PM +0200, Andreas Jochens wrote: This patch is harmless with respect to any LSB requirement. The name of the dynamic loader, which is coded into every binary can only be changed in the gcc package. This patch does not change that. I don't know what you all changed in the gcc-3.4 archive. But this is what I now get with something I just compiled: ldd test libc.so.6 = /lib/libc.so.6 (0x002a9566d000) /lib/ld-linux-x86-64.so.2 = /lib/ld-linux-x86-64.so.2 (0x002a95556000) While with the pure64 archive with either gcc-3.3 of 3.4 it's still pointing to /lib64/ld-linux-x86-64.so.2 I patched the gcc-3.4 package in the amd64/gcc-3.4 archive to get that result. For the patch I used please look at BTS #277852. I recompiled the complete amd64/gcc-3.4 archive with that patch and without the '/lib64' and '/usr/lib64' symlinks in place. I still have to reupload most of the recompiled packages to alioth but you should be able to debootstrap a new chroot from the amd64/gcc-3.4 archive and do a 'rm /lib64' without making the system unusable. which installs a symlink '/lib64/ld-lsb-x86-64.so.2' which points to '/lib/ld-linux-x86-64-so.2' (actually, the current ^ Should probably atleast be a . Yes, of course. [...] We should also make sure that programs build on an other distro can be run on debian so I think we also need to have a /lib64/ld-linux-x86-64.so.2 provided in some way. I fully agree with that. However, we do not have such a symlink yet. The pure64 archive has a patched 'base-files' package which creates such a symlink, but the maintainer of 'base-files' rejected that patch because he said it should be done by the 'glibc' package and I think his decision is correct. Logically it would belong in the 'libc6' package. It tried to put the symlink there, but this caused the system to stop working during updates of the 'libc6' package. We could easily have that symlink if we decided to make our binaries independent of the '/lib64' directory. Still, this particular patch is harmless in all these respects. The patch which really changes something is the patch to gcc which changes the name which is coded into every binary. Regards Andreas Jochens
package updates in Sarge AMD64
Hello, After using the Sarge AMD64 distribution for some time, I did notice the Package.gz file gets updated but the packages inside the archive don't. (I'm talking about the distribution at: http://debian-amd64.alioth.debian.org/sarge/dists/sarge/) Is this due to a technical problem, or a shortage on manpower? Some package are broken (koffice), and the versions from unstable can't be installed due to dependencies on more recent libraries. Running unstable is not a option. We need to have a production system by December. We need a 64 bit distribution for a cluster project. Or should we switch to a other distribution? Best regards, Bert.
Re: K8S Pro (S2882UG3NR) + Sil 3114 (Raid 1) + Sarge
Hi Lennart and Hugo, so what you 2 are saying is that bsically a Sil3114 is as good or bad as any other software raid with the exception that it can start a boot process while on the other hand being proprietory ?? If I create a Software raid with f.e. Debian and I decide to Dual boot into Mandrake, Suse ... whatever should that work ? Best regards Nils Valentin On Monday 25 October 2004 01:58, Lennart Sorensen wrote: On Sun, Oct 24, 2004 at 12:04:48AM +0900, Nils Valentin wrote: just read your reply once more. Just for the records: Iam looking for hardware raid. I already ahev Suse Linux up and running and actually just want debian to be able to access the drives the same way (after the reboot). That is (without the hardware raid) basically a typical dual boot setup. Shouldnt there be a Driver for the Sil3114 Controller ? I know that Tyan makes the drivers for Suse and Redhat. I was hoping that perhaps a nice driver developer is reading this and spend a few hours of devoted motivation to get this done ;-) Best regards A SiS3114 is NOT hardware raid. It is software, just secret proprietary software. If you want hardware raid with open source drivers, you have to get a 3ware card or a scsi raid card. Those are the only choices at the moment. Other hardware ide/sata raid cards exist, but not with open source drivers that I am aware off. Lennart Sorensen -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/
Re: K8S Pro (S2882UG3NR) + Sil 3114 (Raid 1) + Sarge
On Mon, Oct 25, 2004 at 11:09:55PM +0900, Nils Valentin wrote: so what you 2 are saying is that bsically a Sil3114 is as good or bad as any other software raid with the exception that it can start a boot process while on the other hand being proprietory ?? Yes, that's about it. Just two points: If I understand it correctly, the SiI3114 chip doesn't know anything about the boot process -- that piece of functionality is dependent on and provided by the BIOS of the card (or motherboard). Note also that it's SiI (capital i), not Sil (lower case L). If I create a Software raid with f.e. Debian and I decide to Dual boot into Mandrake, Suse ... whatever should that work ? Yes, provided the other OSes know about the software RAID array you've created (so you need the kernel support, the user-space tools, and whatever user-space configuration is necessary). Hugo. -- === Hugo Mills: [EMAIL PROTECTED] carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- I'm all for giving people enough rope to shoot themselves in --- the foot -- Andreas Dilger signature.asc Description: Digital signature
Re: K8S Pro (S2882UG3NR) + Sil 3114 (Raid 1) + Sarge
Hi Johan, was that ahint for using the 2410SA from Adaptec or can I use the 2410SA driver with the SiI3114 ? Best regards Nils Valentin On Tuesday 26 October 2004 00:12, Johan Groth wrote: Lennart Sorensen wrote: On Sun, Oct 24, 2004 at 12:04:48AM +0900, Nils Valentin wrote: just read your reply once more. Just for the records: Iam looking for hardware raid. I already ahev Suse Linux up and running and actually just want debian to be able to access the drives the same way (after the reboot). That is (without the hardware raid) basically a typical dual boot setup. Shouldnt there be a Driver for the Sil3114 Controller ? I know that Tyan makes the drivers for Suse and Redhat. I was hoping that perhaps a nice driver developer is reading this and spend a few hours of devoted motivation to get this done ;-) Best regards A SiS3114 is NOT hardware raid. It is software, just secret proprietary software. If you want hardware raid with open source drivers, you have to get a 3ware card or a scsi raid card. Those are the only choices at the moment. Other hardware ide/sata raid cards exist, but not with open source drivers that I am aware off. The driver for Adaptec 2410SA (SATA raid PCI-66/64bit) are open source. They are included in the kernel. /Johan - Symbian Software Ltd is a company registered in England and Wales with registered number 4190020 and registered office at 2-6 Boundary Row, Southwark, London, SE1 8HP, UK. This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify [EMAIL PROTECTED] and delete the message and any attachments accompanying it immediately. Neither Symbian nor any of its subsidiaries accepts liability for any corruption, interception, amendment, tampering or viruses occurring to this message in transit or for any message sent by its employees which is not in compliance with Symbian corporate policy. -- kind regards Nils Valentin Tokyo/Japan http://www.be-known-online.com/mysql/
Re: K8S Pro (S2882UG3NR) + Sil 3114 (Raid 1) + Sarge
Nils Valentin wrote: Hi Johan, was that ahint for using the 2410SA from Adaptec or can I use the 2410SA driver with the SiI3114 ? It was a reply to Lennart Sorensen's comment: Other hardware ide/sata raid cards exist, but not with open source drivers that I am aware off. But I can recommend the Adaptec 2410SA (hardware raid) as I'm using it myself. Haven't had any problems with that card. You cannot use the Adaptec drivers with the SiI3114. Totally different chipsets are being used. /Johan - Symbian Software Ltd is a company registered in England and Wales with registered number 4190020 and registered office at 2-6 Boundary Row, Southwark, London, SE1 8HP, UK. This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify [EMAIL PROTECTED] and delete the message and any attachments accompanying it immediately. Neither Symbian nor any of its subsidiaries accepts liability for any corruption, interception, amendment, tampering or viruses occurring to this message in transit or for any message sent by its employees which is not in compliance with Symbian corporate policy.
Re: AMD64 CDs/DVDs
On Sun, Oct 24, 2004 at 11:45:16PM +0100, Steve McIntyre wrote: I did however patch debian-cd, but I never really got it working properly. Maybe I just don't know how to use it. I'll try to dig up the changes I've made to it tomorrow and send them to you. Cool, thanks. I'll try and merge the changes into debian-cd too. I've attached a cvs diff of the changes I've made and I've also attached the new files. Kurt ? data/sarge/amd64_businesscard_udeb_include ? data/sarge/amd64_netinst_udeb_include ? data/sarge/amd64_udeb_include ? data/sarge/exclude-udebs-amd64 ? tools/boot/sarge/boot-amd64 Index: build_all.sh === RCS file: /cvs/debian-boot/debian-cd/build_all.sh,v retrieving revision 1.14 diff -u -r1.14 build_all.sh --- build_all.sh9 Jul 2004 14:50:34 - 1.14 +++ build_all.sh25 Oct 2004 19:26:52 - @@ -6,7 +6,7 @@ TMP_OUT=$OUT -for ARCH in i386 alpha arm hppa ia64 m68k mips mipsel powerpc s390 sparc +for ARCH in i386 amd64 alpha arm hppa ia64 m68k mips mipsel powerpc s390 sparc do export ARCH echo Now we're going to build CD for $ARCH ! Index: update-cd === RCS file: /cvs/debian-boot/debian-cd/update-cd,v retrieving revision 1.10 diff -u -r1.10 update-cd --- update-cd 12 Jul 2004 21:20:43 - 1.10 +++ update-cd 25 Oct 2004 19:26:52 - @@ -48,7 +48,7 @@ VERBOSE=2 export VERBOSE BASEDIR SECTS -ARCHLIST=alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc src # all dealt with specially +ARCHLIST=alpha arm hppa i386 amd64 ia64 m68k mips mipsel powerpc s390 sparc src # all dealt with specially export TDIR NONFREE NONUS VER MIRROR CODENAME OUT BASEDIR Index: data/sarge/README.html.in === RCS file: /cvs/debian-boot/debian-cd/data/sarge/README.html.in,v retrieving revision 1.5 diff -u -r1.5 README.html.in --- data/sarge/README.html.in 5 May 2004 15:30:37 - 1.5 +++ data/sarge/README.html.in 25 Oct 2004 19:26:52 - @@ -18,6 +18,7 @@ #endif #undef i386 +#undef amd64 #undef alpha #undef powerpc #undef ppc @@ -355,7 +356,7 @@ A href=%%install/floppy/%%/install/floppy//a /tt -#if ARCHi386 || ARCHalpha || ARCHpowerpc || ARCHsparc +#if ARCHi386 || ARCHamd64 || ARCHalpha || ARCHpowerpc || ARCHsparc P For the impatient ones: #endif @@ -366,7 +367,7 @@ P #endif -#if ARCHi386 || ARCHpowerpc +#if ARCHi386 || ARCHamd64 || ARCHpowerpc #if ARCHi386 You can also #else Index: tasks/base-sarge === RCS file: /cvs/debian-boot/debian-cd/tasks/base-sarge,v retrieving revision 1.6 diff -u -r1.6 base-sarge --- tasks/base-sarge1 Oct 2004 15:11:14 - 1.6 +++ tasks/base-sarge25 Oct 2004 19:26:52 - @@ -7,7 +7,7 @@ * * The script used to generate this file is : -for arch in alpha arm i386 ia64 m68k powerpc sparc mips mipsel hppa s390 +for arch in alpha arm i386 amd64 ia64 m68k powerpc sparc mips mipsel hppa s390 do echo #ifdef ARCH_$arch debootstrap --arch $arch --print-debs $CODENAME | tr ' ' '\n' | grep -v ^$ @@ -411,6 +411,133 @@ psmisc pcmcia-cs ipchains +iptables + +#ifdef ARCH_amd64 +base-files +base-passwd +bash +bsdutils +coreutils +libacl1 +libattr1 +debconf +debconf-i18n +liblocale-gettext-perl +libtext-wrapi18n-perl +libtext-charwidth-perl +debianutils +diff +dpkg +dselect +libblkid1 +e2fsprogs +e2fslibs +libcomerr2 +libss2 +libuuid1 +findutils +grep +gzip +hostname +libcap1 +libc6 +libdb1-compat +libdb3 +libncurses5 +libnewt0.51 +libpam-modules +libpam-runtime +libpam0g +libperl5.8 +libpopt0 +login +makedev +mawk +modutils +mount +ncurses-base +ncurses-bin +passwd +perl-base +procps +sed +slang1a-utf8 +initscripts +sysvinit +sysv-rc +tar +util-linux +whiptail +libgcc1 +gcc-3.3-base +libstdc++5 +libtext-iconv-perl +zlib1g +adduser +apt +apt-utils +libdb4.2 +at +base-config +aptitude +libsigc++-1.2-5c102 +bsdmainutils +console-common +console-tools +libconsole +console-data +cpio +cron +dhcp-client +ed +exim4 +exim4-base +exim4-config +exim4-daemon-light +libgnutls10 +libgcrypt7 +libgpg-error0 +libopencdk8 +libtasn1-2 +fdutils +gettext-base +groff-base +ifupdown +info +klogd +libssl0.9.7 +liblzo1 +zlib1g +liblockfile1 +libpcre3 +libwrap0 +logrotate +mailx +man-db +libgdbm3 +manpages +nano +net-tools +netbase +netkit-inetd +iputils-ping +nvi +ppp +pppconfig +pppoe +pppoeconf +libpcap0.7 +sysklogd +tasksel +libtextwrap1 +tcpd +telnet +libtext-iconv-perl +wget +pciutils +setserial +psmisc iptables #endif Index: tasks/debian-installer === RCS file: /cvs/debian-boot/debian-cd/tasks/debian-installer,v retrieving revision 1.22 diff -u -r1.22 debian-installer --- tasks/debian-installer 6 Oct 2004 20:38:24 - 1.22 +++
find did not work
Hello , I have a problem with findutils_4.1.20-4 , find and locate wont work . the problem existed till 2 weeks . so the wenn i try to compile a file i get following error find debian -type d | xargs rmdir -p --ignore-fail-on-non-empty rmdir: zu wenige Argumente make: *** [install] Fehler 123 kfind and dlocate works What i have to do ? any help are welcome greetings central
Re: K8S Pro (S2882UG3NR) + Sil 3114 (Raid 1) + Sarge
On Mon, Oct 25, 2004 at 11:09:55PM +0900, Nils Valentin wrote: so what you 2 are saying is that bsically a Sil3114 is as good or bad as any other software raid with the exception that it can start a boot process while on the other hand being proprietory ?? If I create a Software raid with f.e. Debian and I decide to Dual boot into Mandrake, Suse ... whatever should that work ? Linux software raid is entirely portable between distributions, although you may have to tell each distribution to look for software raid (the partition type set to raid autodetect helps of course, but does nothing unless raid is looked for). Part of the bad of using a proprietary software raid is that you need a driver that is binary only, and doesn't come with standard kernels and may not even be available or compileable (if it has a wrapper) on the kernel you want. Software raid on the other hand is controller independant and should work with any kernel that has software raid support. Booting is slightly more involved although not very. Len Sorensen
Find wont work
Hello , I have a problem with findutils_4.1.20-4 , find and locate wont work . the problem existed till 2 weeks . so the wenn i try to compile a file i get following error find debian -type d | xargs rmdir -p --ignore-fail-on-non-empty rmdir: zu wenige Argumente make: *** [install] Fehler 123 kfind and dlocate works What i have to do ? any help are welcome greetings central
