Re: Filesystem stability?
We've been running ReiserFS on a Debian Opteron cluster head node (4TB hardware RAID), on another Debian Opteron backup machine (1.5TB on several drives), and on several 32-bit Debian boxes without any issues... Brian Oborn Cameron Patrick wrote: Mark Ferlatte wrote: What filesystems are you guys using, and anyone had any bad experiences? I'm a big fan of reiserfs but have heard problems with people using it on amd64 (and also alpha, which suggests it might be a general 64-bit cleanliness issue). Cameron. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Filesystem stability?
Mark Ferlatte wrote: > What filesystems are you guys using, and anyone had any bad experiences? I'm a big fan of reiserfs but have heard problems with people using it on amd64 (and also alpha, which suggests it might be a general 64-bit cleanliness issue). Cameron. signature.asc Description: Digital signature
Re: Filesystem stability?
On Mon, 11 Jul 2005 18:18:15 -0700, Mark Ferlatte <[EMAIL PROTECTED]> wrote: > > I've heard rumours that some of the Linux filesystems aren't as stable > as they should be on AMD64; in particular, I've heard of bad things > happening with JFS and XFS. > > That being said, I can't find anything even approaching authoritative, > so I thought I'd ask: > > What filesystems are you guys using, and anyone had any bad > experiences? I use ext3, and love it. I used to use ReiserFS (and swore by it), but got BADLY burned a couple of years ago (what was initially a single corrupted file was turned into a totally trashed partition by the Reiser tools, and I ended up losing the entire partition) and haven't touched it since. Regards, Ozz. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
debian-amd64@lists.debian.org
Software by the original manufacturer&at generic prices& http://jvtda.3ap0623e0d3si43.shoatmache.com One good turn deserves another. It's never too late to be what you might have been. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Super software, swell prices, splendid service.
Only our software is guaranteed 100% legal. http://rid.pwbmso70mhpwmq7.stitchebnle.net To him who is in fear everything rustles. I don't want to be anyone but the person I am. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Filesystem stability?
El lun, 11-07-2005 a las 18:18 -0700, Mark Ferlatte escribió: > I've heard rumours that some of the Linux filesystems aren't as stable > as they should be on AMD64; in particular, I've heard of bad things > happening with JFS and XFS. > > That being said, I can't find anything even approaching authoritative, > so I thought I'd ask: > > What filesystems are you guys using, and anyone had any bad experiences? > > M I'm using on my desktop and on a production server XFS with no problem -- Angel Claudio Alvarez Usuario Linux Registrado 143466 GPG Public Key en http://pgp.mit.edu key fingerprint = 3AED D95B 7E2D E954 61C8 F505 1884 473C FC8C 8AC4 signature.asc Description: This is a digitally signed message part
Evolution Calendar & Tasks crashing
I'm not sure what could have caused it, but everytime I try to access my calendars or my tasks in Evolution, it crashes. It hasn't done this until very recently, so I'm not sure what could have caused it. I'm running Debian etch with Evolution 2.2.2. I know this isn't very detailed, but I'm not sure what else to include... Thanks in advance, -Stephen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Filesystem stability?
I've heard rumours that some of the Linux filesystems aren't as stable as they should be on AMD64; in particular, I've heard of bad things happening with JFS and XFS. That being said, I can't find anything even approaching authoritative, so I thought I'd ask: What filesystems are you guys using, and anyone had any bad experiences? M signature.asc Description: Digital signature
Re: Mkinitrd problems
Mon, Jul 11, 2005 at 01:15:05PM +0200 Goswin von Brederlow <[EMAIL PROTECTED]> napisał: > Try adding set -x to the script and trace why it fails. Might be > something trivial. Looks like script changes working directory to: /tmp/mkinitrd.XX/initrd and then executes "mkcramfs /tmp/mkinitrd.XX/initrd outfile" so outfile goes to /tmp/mkinitrd.XX/initrd I think that author forgot to add "cd $ORIGDIR" somewhere. > > MfG > Goswin > > PS: and yes, file abug. critical might be overkill though. > It is already filed. Bug #310395 - 49 days old. -- Grzegorz Andrelczyk | Wszechświat - kilka praktycznych informacji: [EMAIL PROTECTED] | 1.Obszar: nieskończony; 2. Import: brak; www.nie-panikuj.w.pl | 3.Eksport: brak; 4.Ludność: brak; 5.Waluta: brak; | 6.Sztuka: brak; 7.Seks: brak. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KMail segfaults
This is a known bug, with information here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=317098 A quick fix is to run kontact and click on the "mail" section. This is just kmail running as a kpart instead of a separate application, so all your settings and mail will be there. Interestingly, it does not crash when run this way. (This works fine for me on my amd64 install). Thomas [EMAIL PROTECTED] On Monday 11 July 2005 02:13, Wolfgang Pausch wrote: > Hello, > > a few days ago, I made a dist-upgrade for my amd64-system. Everything > seemed to work fine, at least I got no error-messages. > > However, since then, whenever I start kmail, it just prints "Segmentation > fault" and exits without even opening its window. > > I have attached a list with (nearly all) debs I installed/upgraded during > that dist-upgraded (just an ls from the directory I stored the files I > downloaded elsewhere). Interestingly, it seems that kmail was not upgraded. > > BTW: Has apt a logfile keeping track about what changed? > > apt-cache policy kmail returns: > > kmail: > Installed: 4:3.3.2-3 > Candidate: 4:3.3.2-3 > Version table: > *** 4:3.3.2-3 0 > 500 http://ftp.de.debian.org sid/main Packages > 100 /var/lib/dpkg/status > > Now: What can I do about that? Can I make kmail print a more verbose > error-message? > > Thanks for help, please cc me since I'm not on the list. > > Wolfgang -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
KMail segfaults
Hello, a few days ago, I made a dist-upgrade for my amd64-system. Everything seemed to work fine, at least I got no error-messages. However, since then, whenever I start kmail, it just prints "Segmentation fault" and exits without even opening its window. I have attached a list with (nearly all) debs I installed/upgraded during that dist-upgraded (just an ls from the directory I stored the files I downloaded elsewhere). Interestingly, it seems that kmail was not upgraded. BTW: Has apt a logfile keeping track about what changed? apt-cache policy kmail returns: kmail: Installed: 4:3.3.2-3 Candidate: 4:3.3.2-3 Version table: *** 4:3.3.2-3 0 500 http://ftp.de.debian.org sid/main Packages 100 /var/lib/dpkg/status Now: What can I do about that? Can I make kmail print a more verbose error-message? Thanks for help, please cc me since I'm not on the list. Wolfgang Packages adduser_3.64_all.deb apt-utils_0.6.38_amd64.deb apt_0.6.38_amd64.deb aptitude_0.2.15.9-3_amd64.deb arts_1.3.2-4_all.deb base-config_2.66_all.deb cpp-3.3_3.3.6-7_amd64.deb cpp-4.0_4.0.0-12_amd64.deb cpp_4.0.0-1_amd64.deb debconf-i18n_1.4.52_all.deb debconf_1.4.52_all.deb dhcp3-client_3.0.2-1_amd64.deb dhcp3-common_3.0.2-1_amd64.deb doc-linux-html_2005.06-1_all.deb dpkg-dev_1.13.10_all.deb dpkg_1.13.10_amd64.deb dselect_1.13.10_amd64.deb e2fslibs_1.38-1_amd64.deb e2fsprogs_1.38-1_amd64.deb esound-common_0.2.36-1_all.deb exim4-base_4.52-1_amd64.deb exim4-config_4.52-1_all.deb exim4-daemon-light_4.52-1_amd64.deb exim4_4.52-1_all.deb fbset_2.1-17_amd64.deb findutils_4.2.22-2_amd64.deb gcc-3.3-base_3.3.6-7_amd64.deb gcc-3.3_3.3.6-7_amd64.deb gcc-4.0-base_4.0.0-12_amd64.deb gcc-4.0_4.0.0-12_amd64.deb gcc_4.0.0-1_amd64.deb gettext-base_0.14.5-1_amd64.deb gv_3.6.1-12_amd64.deb gzip_1.3.5-11_amd64.deb iptables_1.3.1-2_amd64.deb kdelibs-bin_3.3.2-7_amd64.deb kdelibs-data_3.3.2-7_all.deb kdelibs4_3.3.2-7_amd64.deb kdelibs_3.3.2-7_all.deb kernel-package_9.001_all.deb lbxproxy_4.3.0.dfsg.1-14_amd64.deb libant1.6-java_1.6.5-1_all.deb libarts1_1.3.2-4_amd64.deb libartsc0_1.3.2-4_amd64.deb libasound2_1.0.9-2_amd64.deb libaspell15_0.60.3-1_amd64.deb libblkid1_1.38-1_amd64.deb libbz2-1.0_1.0.2-7_amd64.deb libcomerr2_1.38-1_amd64.deb libdb4.2_4.2.52-19_amd64.deb libdb4.3_4.3.28-2_amd64.deb libdevmapper1.01_1.01.03-1_amd64.deb libdps1_4.3.0.dfsg.1-14_amd64.deb libedit2_2.9.cvs.20050518-2_amd64.deb libesd0_0.2.36-1_amd64.deb libfreetype6_2.1.10-1_amd64.deb libgcc1_4.0.0-12_amd64.deb libglib2.0-0_2.6.5-1_amd64.deb libice6_4.3.0.dfsg.1-14_amd64.deb libjack0.100.0-0_0.100.0-2_amd64.deb libldap2_2.1.30-11_amd64.deb liblocale-gettext-perl_1.05-1_amd64.deb libmad0_0.15.1b-2.1_amd64.deb libncurses5-dev_5.4-8_amd64.deb libncurses5_5.4-8_amd64.deb libncursesw5_5.4-8_amd64.deb libnewt0.51_0.51.6-26_amd64.deb libpcre3_5.0-1.1_amd64.deb libselinux1_1.24-1_amd64.deb libsensors3_2.9.1-3_amd64.deb libslang2_2.0.4-2_amd64.deb libsm6_4.3.0.dfsg.1-14_amd64.deb libsmbclient_3.0.14a-6_amd64.deb libss2_1.38-1_amd64.deb libstdc++5_3.3.6-7_amd64.deb libtext-iconv-perl_1.4-1_amd64.deb libuuid1_1.38-1_amd64.deb libx11-6_4.3.0.dfsg.1-14_amd64.deb libxaw7_4.3.0.dfsg.1-14_amd64.deb libxext6_4.3.0.dfsg.1-14_amd64.deb libxft1_4.3.0.dfsg.1-14_amd64.deb libxi6_4.3.0.dfsg.1-14_amd64.deb libxmu6_4.3.0.dfsg.1-14_amd64.deb libxmuu1_4.3.0.dfsg.1-14_amd64.deb libxp6_4.3.0.dfsg.1-14_amd64.deb libxpm4_4.3.0.dfsg.1-14_amd64.deb libxrandr2_4.3.0.dfsg.1-14_amd64.deb libxrender1_0.9.0-2_amd64.deb libxt6_4.3.0.dfsg.1-14_amd64.deb libxtrap6_4.3.0.dfsg.1-14_amd64.deb libxtst6_4.3.0.dfsg.1-14_amd64.deb libxv1_4.3.0.dfsg.1-14_amd64.deb lilo_22.6.1-6.2_amd64.deb login_4.0.3-35_amd64.deb logrotate_3.7-5_amd64.deb man-db_2.4.3-1_amd64.deb mc_4.6.0-4.6.1-pre4-2_amd64.deb menu_2.1.25_amd64.deb nano_1.3.8-1_amd64.deb ncurses-base_5.4-8_all.deb ncurses-bin_5.4-8_amd64.deb net-tools_1.60-15_amd64.deb openssh-client_4.1p1-5_amd64.deb openssh-server_4.1p1-5_amd64.deb passwd_4.0.3-35_amd64.deb perl-base_5.8.7-3_amd64.deb perl-modules_5.8.7-3_all.deb perl-suid_5.8.7-3_amd64.deb perl_5.8.7-3_amd64.deb proxymngr_4.3.0.dfsg.1-14_amd64.deb python2.3_2.3.5-6_amd64.deb python_2.3.5-3_all.deb reportbug_3.15_all.deb ssh_4.1p1-5_all.deb tar_1.15.1-2_amd64.deb tasksel_2.25_all.deb twm_4.3.0.dfsg.1-14_amd64.deb unzip_5.52-3_amd64.deb wget_1.10-2_amd64.deb whiptail_0.51.6-26_amd64.deb xprint-common_0.1.0.alpha1-11_all.deb xprint_0.1.0.alpha1-11_amd64.deb xprt-xprintorg_0.1.0.alpha1-11_all.deb zip_2.31-3_amd64.deb zlib1g_1.2.2-6_amd64.deb
Re: amd64-specific bug in XPDF based programs?
On 7/10/05, Volker Schlecht <[EMAIL PROTECTED]> wrote: > Hi, > > as of recently I have experienced serious (read: undecipherable output) > display bugs when trying to view certain PDF documents (i.e. > http://www.dnt.de/dl/58/SportyAdventur-eng-rgb.pdf). in xpdf-based viewers > (xpdf-reader, evince, kpdf). Looks perfectly fine here, with sarge+ubuntu and X.org 6.8.2 with ATI binary driver. Although, gv seems to screw it up, as does kghostview. gs itself is fine. So there is indeed something broken. Thomas
Re: Using 4GB with amd64 - problems with NVidia graphics kerneldriver
> Does it work fine with the nv driver? No, the 6600GT is not downward compatible. This was the first thing I checked, some weeks ago. In the meantime I have tried the nvidia installer for the latest version, 7667, but got the following error message when loading the module: NVRM: loading NVIDIA Linux x86_64 NVIDIA Kernel Module 1.0-7667 Fri Jun 17 07: +14:03 PDT 2005 NVRM: RM/client version mismatch!! NVRM:aborting to avoid catastrophe! ... For now it seems the only way to make it work is the debian way via nvidia-kernel-common, nvidia-kernel-source, recompiling the module, make-kpkg, and dpkg -i ... but you made me look closer at the NVidia homepage, more specifically the forum, where I found this: >The attached patch addresses an X startup problem on Linux/x86-64 >em64t systems with 4GB of RAM (or more, i.e. SWIOTLB >configurations) >using SuSE Linux 9.3 (e.g. Linux 2.6.5-7.147) and Linux 2.6.8 >kernels. To patch 1.0-71714 and install the updated driver, please >follow the instructions below. Unfortunately, even with the patched 7174 driver I get exactly the same oops. I've tried to patch the driver towards 7667 and get an even weirder error message than with the installer: nvidia: Unknown symbol rm_is_legacy_device This is definitely a bug, I'll have to notify Nvidia and hope for the best. I've noticed that sk98lin (I've patched my kernel with the non-GPL version) also has a problem with 4GB (i.e. memory hole switched on): sk98lin: Network Device Driver v8.16.2.3 (C)Copyright 1999-2005 Marvell(R). ACPI: PCI interrupt :03:00.0[A] -> GSI 16 (level, low) -> IRQ 16 PCI: Setting latency timer of device :03:00.0 to 64 PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device :03:00.0 SKGE: PCI setup failed: 2 All other things seem to work (at first glance), even my self-compiled Xvnc runs ok. Why is it always only the non-GPL drivers that have problems? :->> Best, Alex -- Dr.techn. Alexander K. Seewald Austrian Research Institute [EMAIL PROTECTED] for Artificial Intelligence www.oefai.at Information wants to be free; Information also wants to be expensive (S.Brant) --- alex.seewald.at -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with firefox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks a lot, it works. I don't know why i ran into this problem, but it's solved. Thanks again. Rathgeb Markus wrote: > 1 #!/bin/sh > 2 ARGS="" > 3 for i in "$@" ; do > 4ARGS="$ARGS '$i'" > 5 done > 6 exec dchroot -c ia32 -d "`basename $TEST`" "$ARGS" > > i changed the line 4 to > ARGS="$ARGS $i" > and it worked again > >> "The URL is not valid and cannot be loaded". >> The problem comes from "http://";, if I simply write www.yahoo.com, it >> works, but then firefox tells this address can't be found. > > > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC0qc63M6ekcMWoxURAmmtAJ4wr1G6IRjcMFWBLxKw1BpXiwHKbACgodtx VuGD3u3IMtWNr3Y8kdBZfhI= =YHTj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling true amd64 binaries on woody?
Turbo Fredriksson <[EMAIL PROTECTED]> writes: > I'm still stuck on/in woody on all my systems. Can't change just > yet (I'm working on it), but in the meantime I'm trying to > create packages that's true amd64. > > The kernel is from sarge (true amd64 kernel), but the rest > of the system is pure woody. > > I was hoping that all I had to do was to get dpkg recompiled, > and that worked somewhat. That's quite impossible. It is hard enough to build 64bit software manualy on i386. What you need is a 64bit chroot. Use cdebootstrap -aamd64 to make one and then work in there. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: iptables on amd64 kernel
Jakub Nadolny <[EMAIL PROTECTED]> writes: > Hi, > > I have just upgraded my hardware to AMD64 and installed kernel-image > 2.6.8-11-amd64-k8. So all packages remain in i386 version. Everything > works fine, but iptables does not work: > > # iptables -L > iptables v1.3.1: can't initialize iptables table `filter': Bad file > descriptor > Perhaps iptables or your kernel needs to be upgraded. > > Kernel and iptables upgrade did not help. Can I ask you for help? > What should I do to have iptables running with amd64 kernel? iptables has an alignment problem in one of its data structures. Under 64bit the aligment changes and then 32bit iptables fails to communicate with the kernel. > I have installed also iptables_1.3.1-2_amd64.deb (with --force-all), but > result is the same. That is rather strange. In what way does it fail? That would have been my suggestion and works fine here. > I use Debian testing. > > Thank you in advance! > Jakub MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mkinitrd problems
gandrel <[EMAIL PROTECTED]> writes: > Hello list. > > Yesterdey I spotted two problems with mkinitrd: > > $Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $ > >>from Sid with up to date updates. > > > 1. In /usr/sbin/mkinitrd script is (or was) with "find" in line 601 > > There is: > > find /proc/scsi -type d -mindepth 1 -maxdepth 1 \ > > and should be: > > find /proc/scsi -mindepth 1 -maxdepth 1 -type d \ > > If not "find" shouts about sequence of options and arguments. Stupid find. :) A minor inconvenience at best. > 2. mkinitrd don't produce output. > > I run: > > mkinitrd -o "image_name" "version" > > and there is no output file. > > Critical bug? > > I run minitrd with option "-k" and build initrd image with mkcramfs. > > > Anybody else can confirm those errors? Or they are just on my system. Try adding set -x to the script and trace why it fails. Might be something trivial. MfG Goswin PS: and yes, file abug. critical might be overkill though. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Dell PE 2850 and installation problem
Hi all, I try to installing Debian AMD64 on Dell PE 2850-Xeon 64bit. Debian not recognize my RAID controller because megaraid2 driver not take part in amd64 cd. I install debian in external USB storage and compile kernel 2.6.12 with megaraid drivers. I edit menu.1st title Debian GNU/Linux, kernel 2.6.8-11-em64t-p4-smp Default root(hd0,1) kernel /boot/vmlinuz root=/dev/sda2 ro console=tty0 initrd /boot/initrd.img savedefault boot title Kernel-2.6.12-Leoman-em64t-smp root(hd0,1) kernel /boot/vmlinuz-2.6.12-Leoman-em64t-smp root=/dev/sda2 ro console=tty0 and re-install grub. I reboot to machine and boot loader says; VFS: cannot open root device "sda2" unknown-block(0,0) Please append a correct "root=" boot option Kernel Panic - not syncing: VFS: to mount root fs on unknown-block(0,0) I think change device address. I try boot old kernel and add a this line; (hd2)/dev/sdc (because attached two scsi disk on machine) and change menu.1st title Kernel-2.6.12-Leoman-em64t-smp root(hd2,1) re-install grub and reboot grub says; no disk and patition How can i resolve this problem? -- Leoman HEDE
Re: Compiling true amd64 binaries on woody?
Turbo Fredriksson wrote: > I'm still stuck on/in woody on all my systems. Can't change just > yet (I'm working on it), but in the meantime I'm trying to > create packages that's true amd64. But there is no woody amd64. So your statement is confusing. If you are talking about woody do you mean x86 woody? You want to cross compile to produce an amd64 binary on woody? If that is your question then I think that is too difficult. Better to create a sid chroot and cross compile from there. If that is not what you are asking then please explain further. > The kernel is from sarge (true amd64 kernel), but the rest > of the system is pure woody. Again, there is no woody for amd64. The earliest possible would be an early sarge release candidate. So your statement confuses me. Bob signature.asc Description: Digital signature
Re: iptables on amd64 kernel
On Mon, 2005-07-11 at 11:45 +0200, Jörg Ebeling wrote: > Hi Jakub, > > I've the same on a server machine since weeks. > > I could solve the problem by installing the 'amd64-libs' and a manually > install of 'iptables_1.2.11-10_amd64.deb' with '--force-architecture'. > > Well it works without any further problems (by me). The annoying thing > is that apt/aptitude always tries to update the iptables package. I did the same thing except I put an "=" next to it in dselect to keep it from getting upgraded. -s signature.asc Description: This is a digitally signed message part
Dell PE 2850 and installation problem
Hi all, I try to installing Debian AMD64 on Dell PE 2850-Xeon 64bit. Debian not recognize my RAID controller because megaraid2 driver not take part in amd64 cd. I install debian in external USB storage and compile kernel 2.6.12 with megaraid drivers. I edit menu.1st title Debian GNU/Linux, kernel 2.6.8-11-em64t-p4-smp Default root(hd0,1) kernel /boot/vmlinuz root=/dev/sda2 ro console=tty0 initrd /boot/initrd.img savedefault boot title Kernel-2.6.12-Leoman-em64t-smp root(hd0,1) kernel /boot/vmlinuz-2.6.12-Leoman-em64t-smp root=/dev/sda2 ro console=tty0 and re-install grub. I reboot to machine and boot loader says; VFS: cannot open root device "sda2" unknown-block(0,0) Please append a correct "root=" boot option Kernel Panic - not syncing: VFS: to mount root fs on unknown-block(0,0) I think change device address. I try boot old kernel and add a this line; (hd2)/dev/sdc (because attached two scsi disk on machine) and change menu.1st title Kernel-2.6.12-Leoman-em64t-smp root(hd2,1) re-install grub and reboot grub says; no disk and patition How can i resolve this problem? -- Leoman HEDE Bi bok deil kendisi
Re: multiarch/bi-arch status (ETA) question
On Fri, Jul 08, 2005 at 08:23:10PM +0200, Goswin von Brederlow wrote: > > $ apt-cache show liferea-mozilla > > [...] > > Depends: liferea (= 0.9.1-1), mozilla-browser, [...] > > > > Gabor > > Does that dlopen mozilla? Looking at the /proc/.../maps file it does. 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]
Re: GPG burns my notebook!
I have installed gdesklets to monitoring cpu, memory, ecc via desktop, and so I have discovered strange behaviour. Example: launch from root 'cfdisk' too see partition and close it normally. On gdesklets I read CPU working ~99%. Top confirms cfdisk 'burn' my cpu and so 'killall cfdisk'. After a few of seconds, I read again CPU working ~99%. Top show 'top' self use my cpu 99% and 'killall' again. It's same thing with 'gpg' at start of this thread. Have you any idea? Thanks, Giulio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: fill free space partition
> > Yes I thought same things above, but I hope for a program avoids deleting > > and re-making partitions manually, just it expands them. I'm not partition > > expert, but on WinXP I have Partition Magic 8. Could does it the 'trick' > > (if you know it)? > > Sure, I did use it once with ext3 partitions and it worked fine, but you > still need to more or less tell it what to do. I think there's no way to > move the beginning of an ext2 partition short of rewriting it, and I > don't know if PM can do that (and I think 8.05 couldn't). > > There's nothing wrong with deleting and re-making the partitions. You'll > keep the same device names after you're done, and you can always > double-check that the data was properly copied before removing the > temporary partitions. Hi, Partition Magic and Parted, permit move and resize of a partition. But in my case, nothing works. I have / (root) in a primary partition, and swap+/home included in a extended partition (and so logical partitions as well freespace). I tried various 'movement', but not works. Not works just a 'simple' resizing of /home partition to include remain freespace too. Have you any idea? Thanks, Giulio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re : amd64-specific bug in XPDF based programs?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 11.07.2005 13:58:55, Clive Menzies a écrit : On (11/07/05 13:19), Miroslav Maiksnar wrote: > Dne ne 10. ?ervence 2005 14:55 Volker Schlecht napsal(a): > > Hi, > > > > as of recently I have experienced serious (read: undecipherable output) > > display bugs when trying to view certain PDF documents (i.e. > > http://www.dnt.de/dl/58/SportyAdventur-eng-rgb.pdf). in xpdf-based viewers > > (xpdf-reader, evince, kpdf). > > Displayed without glitch with xpdf (3.00-13) and kpdf (3.3.2-2) on my amd64 > sarge box. > > Could it be caused by some missing fonts (wrong font substitution)? Volker filed a bug #317708 which has now been reassigned to libfreetype6 An extract from the bug correspondence: >'Replacing libfreetype6 with 2.1.7-2.4 on debian sid > makes the problem disappear.' I've just reinstalled this version and effectively there is no garbage with evince... Regards Clive Jean-Luc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC0mikXit3lz9m7V4RAkXlAKColIC50z2GLn/SSpp5QcrqJzujBgCggunq 6yBonNQa4UHnuvV5BvXkoGM= =V3Kw -END PGP SIGNATURE-
Re: amd64-specific bug in XPDF based programs?
On (11/07/05 13:19), Miroslav Maiksnar wrote: > Dne ne 10. ?ervence 2005 14:55 Volker Schlecht napsal(a): > > Hi, > > > > as of recently I have experienced serious (read: undecipherable output) > > display bugs when trying to view certain PDF documents (i.e. > > http://www.dnt.de/dl/58/SportyAdventur-eng-rgb.pdf). in xpdf-based viewers > > (xpdf-reader, evince, kpdf). > > Displayed without glitch with xpdf (3.00-13) and kpdf (3.3.2-2) on my amd64 > sarge box. > > Could it be caused by some missing fonts (wrong font substitution)? Volker filed a bug #317708 which has now been reassigned to libfreetype6 An extract from the bug correspondence: >'Replacing libfreetype6 with 2.1.7-2.4 on debian sid > makes the problem disappear.' Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: amd64-specific bug in XPDF based programs?
Dne ne 10. července 2005 14:55 Volker Schlecht napsal(a): > Hi, > > as of recently I have experienced serious (read: undecipherable output) > display bugs when trying to view certain PDF documents (i.e. > http://www.dnt.de/dl/58/SportyAdventur-eng-rgb.pdf). in xpdf-based viewers > (xpdf-reader, evince, kpdf). Displayed without glitch with xpdf (3.00-13) and kpdf (3.3.2-2) on my amd64 sarge box. Could it be caused by some missing fonts (wrong font substitution)? Mixi
Re: fglrx, Kernel 2.6.12 and GCC4
Hi Basile, > I do not care about 3D acceleration (I'm using X mostly for emacs, > xterm & mozilla), but I do care about using my whole 1280x800 lcd > screen (in native resolution; it does already works with VESA in > 1024*768). Do you have radeonfb in your kernel? Greetings, Tobias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re : Mkinitrd problems
Mon, Jul 11, 2005 at 09:32:11AM + Jean-Luc Coulon (f5ibh) <[EMAIL PROTECTED]> napisał: > > If you use the -o option with a relative path, it doesnt create the > initrd. > > Try to specify an absolute path: -o /boot/initrd.img for example Thanks. With absolute path mkinitrd creates outfile. > I don't know if it is a bug or a feature For me it is a bug. But we can vote. ;) And maybe somebody knows a reason why mkinitrd with -o option with a relative path should not create outfile? -- Grzegorz Andrelczyk | Wszechświat - kilka praktycznych informacji: [EMAIL PROTECTED] | 1.Obszar: nieskończony; 2. Import: brak; www.nie-panikuj.w.pl | 3.Eksport: brak; 4.Ludność: brak; 5.Waluta: brak; | 6.Sztuka: brak; 7.Seks: brak. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: iptables on amd64 kernel
Hi Jakub, I've the same on a server machine since weeks. I could solve the problem by installing the 'amd64-libs' and a manually install of 'iptables_1.2.11-10_amd64.deb' with '--force-architecture'. Well it works without any further problems (by me). The annoying thing is that apt/aptitude always tries to update the iptables package. Maybe someone else knows a better solution. Cya Joerg Jakub Nadolny wrote: Hi, I have just upgraded my hardware to AMD64 and installed kernel-image 2.6.8-11-amd64-k8. So all packages remain in i386 version. Everything works fine, but iptables does not work: # iptables -L iptables v1.3.1: can't initialize iptables table `filter': Bad file descriptor Perhaps iptables or your kernel needs to be upgraded. Kernel and iptables upgrade did not help. Can I ask you for help? What should I do to have iptables running with amd64 kernel? I have installed also iptables_1.3.1-2_amd64.deb (with --force-all), but result is the same. I use Debian testing. Thank you in advance! Jakub -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re : Mkinitrd problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 11.07.2005 10:59:28, gandrel a écrit : Hello list. Yesterdey I spotted two problems with mkinitrd: $Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $ from Sid with up to date updates. 1. In /usr/sbin/mkinitrd script is (or was) with "find" in line 601 There is: find /proc/scsi -type d -mindepth 1 -maxdepth 1 \ and should be: find /proc/scsi -mindepth 1 -maxdepth 1 -type d \ If not "find" shouts about sequence of options and arguments. 2. mkinitrd don't produce output. I run: mkinitrd -o "image_name" "version" and there is no output file. Critical bug? I run minitrd with option "-k" and build initrd image with mkcramfs. Anybody else can confirm those errors? Or they are just on my system. If you use the -o option with a relative path, it doesnt create the initrd. Try to specify an absolute path: -o /boot/initrd.img for example I don't know if it is a bug or a feature Jean-Luc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC0jybXit3lz9m7V4RAq11AKCTbN7DrOOoDmJQ1rhAu11hovPCZgCbBd9V /juZcfhs00bUorTY1bRkq7I= =SSY+ -END PGP SIGNATURE-
Mkinitrd problems
Hello list. Yesterdey I spotted two problems with mkinitrd: $Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $ from Sid with up to date updates. 1. In /usr/sbin/mkinitrd script is (or was) with "find" in line 601 There is: find /proc/scsi -type d -mindepth 1 -maxdepth 1 \ and should be: find /proc/scsi -mindepth 1 -maxdepth 1 -type d \ If not "find" shouts about sequence of options and arguments. 2. mkinitrd don't produce output. I run: mkinitrd -o "image_name" "version" and there is no output file. Critical bug? I run minitrd with option "-k" and build initrd image with mkcramfs. Anybody else can confirm those errors? Or they are just on my system. -- Grzegorz Andrelczyk | Wszechświat - kilka praktycznych informacji: [EMAIL PROTECTED] | 1.Obszar: nieskończony; 2. Import: brak; www.nie-panikuj.w.pl | 3.Eksport: brak; 4.Ludność: brak; 5.Waluta: brak; | 6.Sztuka: brak; 7.Seks: brak. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
iptables on amd64 kernel
Hi, I have just upgraded my hardware to AMD64 and installed kernel-image 2.6.8-11-amd64-k8. So all packages remain in i386 version. Everything works fine, but iptables does not work: # iptables -L iptables v1.3.1: can't initialize iptables table `filter': Bad file descriptor Perhaps iptables or your kernel needs to be upgraded. Kernel and iptables upgrade did not help. Can I ask you for help? What should I do to have iptables running with amd64 kernel? I have installed also iptables_1.3.1-2_amd64.deb (with --force-all), but result is the same. I use Debian testing. Thank you in advance! Jakub -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Compiling true amd64 binaries on woody?
I'm still stuck on/in woody on all my systems. Can't change just
yet (I'm working on it), but in the meantime I'm trying to
create packages that's true amd64.
The kernel is from sarge (true amd64 kernel), but the rest
of the system is pure woody.
I was hoping that all I had to do was to get dpkg recompiled,
and that worked somewhat.
Looking at what's happening when 'debuild' is building a package,
I found 'dpkg-architecture -qDEB_HOST_ARCH' (which is run by
'dpkg-gencontrol'). Running 'dpkg-architecture' without params
will give me:
- s n i p -
DEB_BUILD_ARCH=amd64
DEB_BUILD_GNU_CPU=x86_64
DEB_BUILD_GNU_SYSTEM=linux
DEB_BUILD_GNU_TYPE=x86_64-linux
DEB_HOST_ARCH=i386
DEB_HOST_GNU_CPU=i386
DEB_HOST_GNU_SYSTEM=linux
DEB_HOST_GNU_TYPE=i386-linux
- s n i p -
So, is there a trick to fool 'dpkg-architecture' ('debuild' or
'dpkg-gencontrol' etc) that it should use the 'DEB_BUILD_ARCH'
instead?
I guess I _could_ hack '/usr/lib/dpkg/controllib.pl:findarch()'
to retreive the 'DEB_BUILD_ARCH' value instead of the current
'DEB_HOST_ARCH' but I was hoping for something smarter...
--
AK-47 Panama 747 Ortega Noriega Albanian critical nuclear security
toluene counter-intelligence Serbian ammunition cracking BATF
[See http://www.aclu.org/echelonwatch/index.html for more about this]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re : Flash kills Firefox (ia32)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 11.07.2005 02:31:19, Chris Wakefield a écrit : On July 10, 2005 09:12 am, Jean-Luc Coulon (f5ibh) wrote: > The free flash plugin kills mozilla, firefox, galeon, epiphany and > everything based on the Gecko engine. > > From you chroot, after removing the libflash-mozplugin and its > dependancies do: > > apt-get install flashplugin-nonfree > > And you will get an non-free (according to Debian policy) but workable > package. Greetings: Can you post your non-free sources.list? It seems to be in contrib: [EMAIL PROTECTED] # apt-cach policy flashplugin-nonfree flashplugin-nonfree: Installé : 7.0.25-5 Candidat : 7.0.25-5 Table de version : *** 7.0.25-5 0 500 ftp://ftp.de.debian.org sid/contrib Packages 100 /var/lib/dpkg/status # Sid deb ftp://ftp.de.debian.org/debian/ sid main non-free contrib It is only an installer, it download the binary from macromedia siet at configure time Thank You, Chris W. Jean-Luc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC0h8JXit3lz9m7V4RAhgeAKCu6wAjm0J9DGBqnSOoS9GirSejkwCfUTgl Y+Af9kiWtjJ4ppHWGZGYrsA= =3ecZ -END PGP SIGNATURE-
