Re: How to recover from corrupted memory
On Wed, 17 Mar 2010 20:25:27 +1100, hce wrote: .. dr-s-w---T 24576 2594201913 1635839568 1637221952 ***1970-01-01*** 10:00 .. I scored a similar entry when my HD had an unreadable sector. In my case, the offending file could be *moved*. So I created a dummy directory, moved the unreadable file to the dummy directory and ran my updatedb etc with a parameter that ignored the dummy directory. The only permanent cure (in my case) was to reformat the partition that contained the unreadable sector. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hns7n7$r7...@dough.gmane.org
Re: debian utility question
On Tue, 22 Apr 2008 22:03:00 +1200, Chris Bannister wrote: On Sun, Apr 20, 2008 at 05:45:26AM -0500, Jude DaShiell wrote: Does debian have a utility I can run to check and repair disk permissions? Hi Jude, What is the output of the following command: lsof /usr/bin/dpkg Queries from a lurker: When running the above command as user, I get: lsof: WARNING: can't stat() xfs file system /dev/.static/dev Output information may be incomplete. Should the command be run as root; and if so, what might get broken ? Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernel -upgrade query
The tutorial at : http://linuxbasics.org/tutorials/during/uuid_naming?rev=1207514451 includes the following entry: | One notable problem is that newer kernels use scsi nomenclature for | drives. If doing a kernel upgrade it is probably best to first convert | fstab entries to UUID rather than /dev/hdax. Does this apply to Debian kernel upgrades? Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Exim4 - local mail deliveries
On Sun, 09 Mar 2008 00:04:51 +0200, Andrei Popescu wrote: On Sat, Mar 08, 2008 at 09:48:16PM +, Felix Karpfen wrote: logcheck.conf offers a choice of where to send notifications. I had set it to [EMAIL PROTECTED]. It looks as though I would have spared myself a lot of headaches, if I had selected [EMAIL PROTECTED] Why is that? Your exim config was ... incomplete. Very true. And, if I had chosen [EMAIL PROTECTED] in the logcheck.conf, exim4.config would still be incomplete! All is well that ends well. And many thanks to all who helped. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Exim4 - local mail deliveries
On Fri, 07 Mar 2008 20:02:22 +0100, Florian Kulzer wrote: On Thu, Mar 06, 2008 at 21:22:40 +, Felix Karpfen wrote: After switching to mbox format, I can receive echo just a test... | mail -s test-local [EMAIL PROTECTED] when run from a user terminal. ziltch for echo just a test... | mail -s test-local 2 $USER That means that exim4 knows how to do local deliveries, but it does not seem to realize that carrot.cabbagepatch is local. (The first command above sends mail to [EMAIL PROTECTED], the second one to [EMAIL PROTECTED]) and ziltch if either command is run as root. Mails to [EMAIL PROTECTED] get redirected to [EMAIL PROTECTED], which does not work; mails to [EMAIL PROTECTED] get stuck immediately. SNIP Logcheck and other demons use the hostname in /etc/mailname. Exim does not realize that this is the same machine, which means that you have to fix your exim configuration and/or your /etc/hosts file. logcheck.conf offers a choice of where to send notifications. I had set it to [EMAIL PROTECTED]. It looks as though I would have spared myself a lot of headaches, if I had selected [EMAIL PROTECTED] I would try this: Run dpkg-reconfigure exim4-config and make sure that system mail name is set to carrot.cabbagepatch and other destinations for which mail is accepted is set to localhost;carrot.cabbagepatch. Then try the mail commands again. Did that (although the screen indicated that exim4 already recognised localhost and carrot.cabbage.patch). Now everything works. Thank you for the help. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Exim4 - local mail deliveries
On Wed, 05 Mar 2008 21:05:48 +0100, Florian Kulzer wrote: On Mon, Mar 03, 2008 at 20:22:12 +, Felix Karpfen wrote: Since switching to Debian Etch, I no longer get messages (from cron and logcheck) delivered to my user-mailbox. Exim 4 delivers them to the mail-queue in /var/spool/exim4/input; when the queue is emptied, they appear to end up in /dev/null. The Lenny/Sid version of exim4 has a debconf dialog question that lets you *choose between mbox format in /var/mail* and Maildir format in home directory. Etch offers the same choice and this may have been one of my problems. After switching to mbox format, I can receive echo just a test... | mail -s test-local [EMAIL PROTECTED] when run from a user terminal. ziltch for echo just a test... | mail -s test-local 2 $USER and ziltch if either command is run as root. In case it is relevant: $ echo $USER felixk and the only entry in /etc/mailname is the name of the localhost (carrot.cabbage.patch). Messages from logcheck continue to be delivered to /var/spool/exim4/input. The following logcheck header may reveal something: | 1JX43I-00015E-M3-H | logcheck 111 115 | [EMAIL PROTECTED] | 1204763620 0 | -ident logcheck | -received_protocol local | -body_linecount 266 | -auth_id logcheck | -auth_sender [EMAIL PROTECTED] | -allow_unqualified_recipient | -allow_unqualified_sender | -local | XX | 1 | [EMAIL PROTECTED] | | 205P Received: from logcheck by carrot.cabbage.patch with local (Exim 4.63) | (envelope-from [EMAIL PROTECTED]) | id 1JX43I-00015E-M3 | for [EMAIL PROTECTED]; Thu, 06 Mar 2008 11:33:40 +1100 | 031T To: [EMAIL PROTECTED] | 071 Subject: Reboot: carrot.cabbage.patch 2008-03-06 11:33 Security Events | 053I Message-Id: [EMAIL PROTECTED] | 061F From: logcheck system account [EMAIL PROTECTED] | 038 Date: Thu, 06 Mar 2008 11:33:40 +1100 It is worth flagging that it might now be a feature of logcheck to send its notifications *only* to another computer. While the posting problems on my box barely warrant the attention that they have received, I supply these further details in the hope that my experiences may identify an exim.config problem/bug. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Exim4 - local mail deliveries
Since switching to Debian Etch, I no longer get messages (from cron and logcheck) delivered to my user-mailbox. Exim 4 delivers them to the mail-queue in /var/spool/exim4/input; when the queue is emptied, they appear to end up in /dev/null. The following uncovered advice in man update-exim4.conf: | dc_localdelivery | | name of the default transport for local mail delivery. Defaults to | mail_spool if unset, use maildir_home for delivery to ~/Maildir/. This | setting does not correspond to a Debconf question and needs to be set | manually. is too cryptic for me. I would welcome a fuller explanation of what it says, and guidance on the correct entry in update-exim4.conf to post local mail to my user-mailbox. In case it is relevant, my postmaster alias is root and my root alias is the normal user. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Non-understood advice - was Re: dist-upgrade from sarge to etch - package
On Mon, 11 Feb 2008 23:13:58 +0100, Florian Kulzer wrote: On Mon, 11 Feb 2008 23:13:58 +0100, Florian Kulzer wrote: On Mon, Feb 11, 2008 at 21:45:24 +, Felix Karpfen wrote: On Sun, 10 Feb 2008 23:00:13 +0100, Florian Kulzer wrote: Please post the output of: grep ^Origin /var/lib/apt/lists/*_Release No output The ~O match of aptitude relies on the Origin: ... statement in the Release files AFAIK, so it will not work here. There is a Release file on DVD1 in the /dist/etch directory. It contains md5sums. No reference to Origin. If that computer is connected to the internet at all then you should have the security repository included anyhow. Currently it is present in /etc/apt/sources.list and commented out :-(. When I get my courage up to use apt-zip, I will remove the mark and bring my OS up-to-date. Hitherto, all the flagged security issues have been local and hence are not a problem when there is only one user. Thank you for taking the time to clarify my confusion. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Non-understood advice - was Re: dist-upgrade from sarge to etch - package
On Sun, 10 Feb 2008 23:00:13 +0100, Florian Kulzer wrote: Please post the output of: grep ^Origin /var/lib/apt/lists/*_Release No output Perhaps ls -lt /var/lib/apt/lists will tell you something. It lists: total 19224 -rw-r- 1 root root 0 2008-01-20 21:10 lock drwxr-xr-x 2 root root 6 2007-06-07 11:09 partial -rw-r--r-- 1 root root 8563083 2007-06-07 07:29 Debian%20GNU_Linux%204.0%20r0%20%5fEtch%5f%20-%20Official%20i386%20DVD%20Binary-3%2020070407-11:40_dists_unstable_main_binary-i386_Packages -rw-r--r-- 1 root root 153166 2007-06-07 07:29 Debian%20GNU_Linux%204.0%20r0%20%5fEtch%5f%20-%20Official%20i386%20DVD%20Binary-3%2020070407-11:40_dists_unstable_contrib_binary-i386_Packages -rw-r--r-- 1 root root 5637840 2007-06-07 07:25 Debian%20GNU_Linux%204.0%20r0%20%5fEtch%5f%20-%20Official%20i386%20DVD%20Binary-2%2020070407-11:40_dists_unstable_main_binary-i386_Packages -rw-r--r-- 1 root root 48687 2007-06-07 07:25 Debian%20GNU_Linux%204.0%20r0%20%5fEtch%5f%20-%20Official%20i386%20DVD%20Binary-2%2020070407-11:40_dists_unstable_contrib_binary-i386_Packages -rw-r--r-- 1 root root 5253161 2007-06-07 07:22 Debian%20GNU_Linux%204.0%20r0%20%5fEtch%5f%20-%20Official%20i386%20DVD%20Binary-1%2020070407-11:40_dists_unstable_main_binary-i386_Packages -rw-r--r-- 1 root root 18707 2007-06-07 07:22 Debian%20GNU_Linux%204.0%20r0%20%5fEtch%5f%20-%20Official%20i386%20DVD%20Binary-1%2020070407-11:40_dists_unstable_contrib_binary-i386_Packages Felix -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Non-understood advice - was Re: dist-upgrade from sarge to etch - package
On Sun, 10 Feb 2008 15:31:27 +0100, Florian Kulzer wrote: What do you see when you run apt-cache policy a2ps adduser alsa-base ? The following: | a2ps: | Installed: 1:4.13b.dfsg.1-1 | Candidate: 1:4.13b.dfsg.1-1 | Version table: | *** 1:4.13b.dfsg.1-1 0 | 500 cdrom://[Debian GNU/Linux 4.0 r0 _Etch_ - Official i386 DVD Binary-1 20070407-11:40] unstable/main Packages | 100 /var/lib/dpkg/status | adduser: | Installed: 3.102 | Candidate: 3.102 | Version table: | *** 3.102 0 | 500 cdrom://[Debian GNU/Linux 4.0 r0 _Etch_ - Official i386 DVD Binary-1 20070407-11:40] unstable/main Packages | 100 /var/lib/dpkg/status | alsa-base: | Installed: 1.0.13-5 | Candidate: 1.0.13-5 | Version table: | *** 1.0.13-5 0 | 500 cdrom://[Debian GNU/Linux 4.0 r0 _Etch_ - Official i386 DVD Binary-1 20070407-11:40] unstable/main Packages | 100 /var/lib/dpkg/status Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Non-understood advice - was Re: dist-upgrade from sarge to etch - package
On Fri, 08 Feb 2008 18:40:09 -0800, Daniel Burrows wrote: On Fri, Feb 08, 2008 at 08:54:02PM +, Felix Karpfen [EMAIL PROTECTED] I recollect running a command that identified non-Debian packages as part of the upgrade to Etch and *the command gave the expected output*. But, alas, I can no longer find what that command was. I'm now completely confused. The problem is just that you want to find the command that you ran before? Am I understanding correctly? Daniel I was hoping that: | aptitude search '~i!~Odebian' was the command that I ran successfully as part of the upgrade from Sarge to Etch and had forgotten. If it is the same command, it is now behaving quite differently. I refrained from posting the output that it now produces because the output is lengthy and I wanted to conserve bandwidth. But here are the first few lines of that output: | i a2ps - GNU a2ps - 'Anything to PostScript' conver | i A abiword-common - WYSIWYG word processor based on GTK2 | i A abiword-gnome- WYSIWYG word processor based on GTK2/GNOME | i abiword-help - online help for AbiWord | i adduser - Add and remove users and groups | i afio - archive file manipulation program | i A akregator- RSS feed aggregator for KDE | i alien- install non-native packages with dpkg | i alsa-base- ALSA driver configuration files | i alsa-oss - ALSA wrapper for OSS applications | i alsa-utils - ALSA utilities I hope that makes things clearer. It is just a niggle. Etch works like a charm! Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Non-understood advice - was Re: dist-upgrade from sarge to etch - package
On Wed, 06 Feb 2008 20:34:14 +, Felix Karpfen wrote: On Tue, 05 Feb 2008 18:54:08 +0100, Florian Kulzer wrote: Check for non-Debian packages on your system by running: aptitude search '~i!~Odebian' As an aptitude-novice, I tried the above command on my fully-operational upgrade from Sarge to Etch. It gave **a long list of installed packages - almost all of which were part of the Debian install***. What have I missed|misunderstood? Firstly, I would like to thank Florian Kulzer and Daniel Burrows for their replies. They failed to address my misunderstanding and the fault was mine. My concern arose not from the absence of vuescan (which - as pointed out - is a monolithic binary package) but the presence of many dozens of packages that were *not* non-Debian packages. The concern arose from the fact that - following the upgrade instructions to the letter - I recollect running a command that identified non-Debian packages as part of the upgrade to Etch and *the command gave the expected output*. But, alas, I can no longer find what that command was. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) Daniel Burrows -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Non-understood advice - was Re: dist-upgrade from sarge to etch - package
On Tue, 05 Feb 2008 18:54:08 +0100, Florian Kulzer wrote: On Tue, 05 Feb 2008 18:54:08 +0100, Florian Kulzer wrote: Check for non-Debian packages on your system by running: aptitude search '~i!~Odebian' As an aptitude-novice, I tried the above command on my fully-operational upgrade from Sarge to Etch. It gave a long list of installed packages - almost all of which were part of the Debian install. The generated list included one of the two non-Debian packages (opera)- deleted during the install and replaced subsequently. It failed to find the only other non-Debian package (vuescan). I also ran the following: | $ aptitude search '~i! ~Odebian' | grep opera* and got : | i eject - ejects CDs and operates CD-Changers | i opera - The Opera Web Browser What have I missed|misunderstood? Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vuescan won't start
On Wed, 30 Jan 2008 16:52:16 -0500, Richard Carter wrote: On Wed, 30 Jan 2008 16:52:16 -0500, Richard Carter wrote: Hi Folks, I'm running debian 4.0 (etch) on a PC with an amd64 processor. SNIP How can I get vuescan to start? I asked a similar question and did not score an answer. I hope that you are luckier. For what it is worth, Vuescan (+ an Epson Perfection 4490 scanner) works with Sarge on my box; but not with Etch. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Enabling TLS support for Exim as server ?
As a perennial Newbie, I find the explanation in /usr/share/doc/exim4-base/examples/exim-gencert a bit too cryptic. What information do I need to have to hand in order to run the above-mentioned script - i.e which requested inputs are mandatory and which are optional? I would like to be able to use both my own ISP and GMail as the servers that forwards my emails to recipients that need authentication. Any other pointers will also be gratefully received. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Epson 4490 + Debian Etch - was lRe: libsane-extras: epson perfection 4490 PHOTO doesn't work on amd64
On Thu, 27 Dec 2007 17:44:28 +0100, Florian Kulzer wrote: If all else fails then you can set up a 32bit chroot environment and run the 32bit version of sane and the epson libraries in there. A related topic - I hope. I have used an Epson 4490 scanner (+ iscan) successfully in a Debian Sarge environment. When I upgraded to Debian Etch, the Epson-supplied versions of iscan + proprietary plugin - /iscan-plugin-gt-x750-1.0.0-1.i386.rpm - started to balk. iscan now sends the following error message: /usr/share/iscan/esfw54.bin/esfw54.bin: Not a directory which is true. There is a file - /usr/share/iscan/esfw54.bin; the directory (?) does not exist. Despite this error, I have - by coaxing and massage - managed to persuade Etch to recognise the scanner. The posting from Florian Kulzer inspired me to revisit the Avasys site. I found that both iscan and the iscan plugin have been updated. The new plugin reads: /iscan-plugin-gt-x750-1.0.0-1.c2.i386.rpm Does any Debian Etch user have experience with this updated version of the plugin (and with the updated version of iscan [2.10.0-1.c2])? I do not wish to replace something that works badly in Etch with something that does not work all. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Using exim as SMTP-AUTH client
On Thu, 13 Dec 2007 16:49:09 -0500, Celejar wrote: On Thu, 13 Dec 2007 20:24:14 + (UTC) Felix Karpfen [EMAIL PROTECTED] wrote: Are there any problems with having more than one entry in my etc/exim4/passwd.client file? see this thread for an account of some trouble I once had using exim with Gmail: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403583 That reference helped a lot! My error message, when attempting to send mail from my GMail account, was (from memory) virtually identical with that quoted in the bug report. Given that I have exim4/4.63-17, I may be lucky; the bug has been fixed. I shall soon know if that was the problem; at least, I now know where to look. Many thanks Felix -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Using exim as SMTP-AUTH client
I have located the following relevant info in /usr/share/doc/exim4-config/README.Debian.gz: If you want to set up exim as SMTP AUTH client for delivery to your internet access provider's smarthost put the name of the server, your login and password in /etc/exim4/passwd.client. See the man page for exim4-config_files(5) for more information about the required format. This works well for emails sent via my ISP. But I also have a gmail account (as a fallback - in case my ISP bombs out). _My_ ISP does not require SMTP-AUTH; the ISP used by one of my regular correspondents will not accept emails that do not have it. GMail offers relevant info on using GMail + procmail; nothing on using GMail + exim4. My question is: Are there any problems with having more than one entry in my etc/exim4/passwd.client file? All advice will be gratefully received. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Deprecated /etc/network/options'
On Sat, 17 Nov 2007 22:44:21 +0100, gianca wrote: Felix Karpfen ha scritto: When booting Debian Etch, one of the displayed messages reads that the use of etc/network/options is now deprecated and the entries should be transferred to /etc/sysctl.conf. As from /usr/share/doc/netbase/README.Debian, you have to put something like this in /etc/sysctl.conf: -- # ip_forward=no... net.ipv4.ip_forward = 0 # spoofprotect=yes... net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 # syncookies=no ... net.ipv4.tcp_syncookies = 0 Problem solved! Grazie tante. Felix -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Deprecated /etc/network/options'
When booting Debian Etch, one of the displayed messages reads that the use of etc/network/options is now deprecated and the entries should be transferred to /etc/sysctl.conf. Which I did and failed. I now get the following additional error messages: [EMAIL PROTECTED] log]# cat boot | grep error Sat Nov 17 11:25:58 2007: Setting kernel variables...error: ip_forward is an unknown key Sat Nov 17 11:25:58 2007: error: spoofprotect is an unknown key Sat Nov 17 11:25:58 2007: error: syncookies is an unknown key The errors are the three entries that were in /etc/network/options and are now in /etc/sysctl.conf What have I missed|misunderstood? Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian packages without md5sums
On Fri, 05 Oct 2007 18:40:44 +0200, Florian Kulzer wrote: [ Felix, I hope this message also helps with your problem. ] Thank you. The posting gave a full explanation of my observations and a strategy for dealing with the (probably non-existent) problem. Felix -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iscan frustration Compounded!
On Tue, 02 Oct 2007 14:40:54 +0100, Chris Davies wrote: Felix Karpfen [EMAIL PROTECTED] wrote: The problem is similar because Debian Etch (kernel 2.6.18) is looking for the firmware file in the wrong directory. [...] Why should the kernel be looking for a firmware file to send to the scanner? Are you /sure/ this is a kernel issue? I do not believe that it is a kernel issue; I just mentioned the kernel to indicate that I have a standard Etch install - no upgrades!. I suspect it is due to some of the major rationalisations there were introduced in Etch and have not yet been taken onboard by EPSON/EPKOWA in its supplied plugins. Can you post the exact set of messages relating to this, please? The error message - when iscan cannot find the scanner - reads: /usr/share/iscan/esfw54.bin/esfw54.bin : Not a directory This error message is valid. esfw54.bin is not a directory but a file and it is located in /usr/share/iscan/ (I have placed copies in a few other places - just in case the alternatives locations can be found more easily by iscan). Felix -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian packages without md5sums
On Wed, 03 Oct 2007 21:55:17 +0200, Florian Kulzer wrote: On Tue, Oct 02, 2007 at 21:02:41 -0700, Carl Johnson wrote: Is there some way to get the system to re-read the release file? I installed the key after I upgradeed the system to etch, so all packages on my DVDs show as being unverified. I have tried to get it to clear that, but nothing I have tried has worked. Did you try to remove all the DVD-related lines from your /etc/apt/sources.list, **run aptitude update** and then add the DVD(s) again using the apt-cdrom command? I think that should work but I have not tested it. I believe that the above-flagged problem is similar to the one that I posted to this thread. But either I have not understand the suggested solution or the solution is nonviable with my setup. The only entries on my /etc/apt/sources.list relate to my DVDs. The reason is that my connection to the Internet is too slow for viable online dist upgrades; and even if an online aptitude update actually managed to go to completion, I would just end up with an out-of-sync setup. Is there any available strategy that applies to cases like mine? Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iscan frustration Compounded!
On Sun, 30 Sep 2007 09:24:06 -0400, Thomas H. George wrote: On Tue, Sep 25, 2007 at 12:59:26PM -, Chris Davies wrote: Thomas H. George [EMAIL PROTECTED] wrote: I own two Epson scanners, a Perfection 2400 Photo and a Perfection V100 Photo. Neither work with Debian Linux. Check the location of the firmware file, esfw41.bin. A few upgrades ago, my system also lost the configuration entry in /etc/sane.d/snapscan.conf that defined this. There was no esfw41.bin in my system. Depending on the version of iscan that is installed, esfw41.bin is either included in iscan install or is an Epson plugin that has to be downloaded from the Epson website and put into the correct directory (that will enable iscan to find it). My problem is that, since updating to Etch. I no longer know what the correct directory is. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iscan frustration Compounded!
On Tue, 25 Sep 2007 12:59:26 +, Chris Davies wrote: Thomas H. George [EMAIL PROTECTED] wrote: I own two Epson scanners, a Perfection 2400 Photo and a Perfection V100 Photo. Neither work with Debian Linux. Check the location of the firmware file, esfw41.bin. A few upgrades ago, my system also lost the configuration entry in /etc/sane.d/snapscan.conf that defined this. I would be very grateful for further details, since I am an amateur with a similar|worse problem. The problem is similar because Debian Etch (kernel 2.6.18) is looking for the firmware file in the wrong directory. The error message reads: /usr/share/iscan/esfw54.bin/esfw54.bin : Not a directory esfw54.bin is not a directory but a file and it is located in /usr/share/iscan/ (with copies in a few other places - just in case the alternatives locations are easier to find) The problem is worse, because it is intermittent. Whenever I reboot the system, it is a gamble. Sometimes the scanner is found and sometimes I get the above error message. I have no problems if I choose to use Debian Sarge (kernel 2.6.8). All suggestions will be gratefully received. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iscan frustration Compounded!
On Tue, 25 Sep 2007 12:59:26 +, Chris Davies wrote: Thomas H. George [EMAIL PROTECTED] wrote: I own two Epson scanners, a Perfection 2400 Photo and a Perfection V100 Photo. Neither work with Debian Linux. Check the location of the firmware file, esfw41.bin. A few upgrades ago, my system also lost the configuration entry in /etc/sane.d/snapscan.conf that defined this. I would be very grateful for further details, since I am an amateur with a similar|worse problem. The problem is similar because Debian Etch (kernel 2.6.18) is looking for the firmware file in the wrong directory. The error message reads: /usr/share/iscan/esfw54.bin/esfw54.bin : Not a directory esfw54.bin is not a directory but a file and it is located in /usr/share/iscan/ (with copies in a few other places - just in case the alternatives locations are easier to find) The problem is worse, because it is intermittent. Whenever I reboot the system, it is a gamble. Sometimes the scanner is found and sometimes I get the above error message. I have no problems if I choose to use Debian Sarge (kernel 2.6.8). All suggestions will be gratefully received. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iscan frustration Compounded!
On Mon, 24 Sep 2007 12:19:16 -0400, Thomas H. George wrote: On Mon, 24 Sep 2007 12:19:16 -0400, Thomas H. George wrote: I own two Epson scanners, a Perfection 2400 Photo and a Perfection V100 Photo. Neither work with Debian Linux. Both are known to work flawlessly with Windows XP Professional. I hate to reboot to Windows XP Professional and do so only as a last resort. At present I have no choice when I need to scan a document. My remedy is marginally less drastic. I have to boot into Debian Sarge when Etch cannot find my scanner. SNIP The Epson Perfection 2400 is listed in the Sane-Project list as Complete. What was the date of that listing? Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iscan frustration
On Fri, 21 Sep 2007 09:29:40 -0400, Thomas H. George wrote: I was able to run iscan for my Epson Perfection V100 Photo scanner but only as root. This no longer works. I get a message, Could not send a command to scanner. The system is lenny with a 2.6.21 linux-image kernel. I too have encountered encountered problems after upgrading my kernel. My problem is worse. Sometimes, after a reboot, iscan sees the scanner and sometimes it does not. No idea why. When iscan sees the scanner once, it continues to see it after closing and re-opening iscan. But I have to hold my breath every time that I reboot my computer. I had no problems using iscan (with the designated plugin) in the Sarge environment (kernel 2.6.8-2). Have you tried posting a message on the Epson AVASYS bulletin board? I tried, but crashed at Square One; I could not persuade the bulletin board to accept my message :-(. If you can coax the bulletin board to accept your query, I would welcome being told how to do that. Good luck Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian packages without md5sums
On Sun, 23 Sep 2007 17:32:20 +0900, Osamu Aoki wrote:
(Edited)
During etch in testing period, I recall several problems which
errouneously made to report to be unsigned package.
Since gpg-signed packages is an etch innovation, it explains why I
had not encountered before the warning detailed below.
I am still unclear about the point in the installation process at which
the signature of the installed package is checked.
The short story at this end is:
a. I purchased a DVD set of Debian 4.0 from a Debian-listed supplier
and followed the Debian upgrade-instructions on all points except
the final aptitude update step; I assumed that this needed a live
Internet connection and my Internet connection is too slow (which
is why I waited for the release of the Official DVD set before
attempting the upgrade from Sarge).
b. Etch works perfectly. But both during the dist-upgrade and whenever I
now use Synaptic to install a new package from my DVD set, I get a
warning that I am installing software that can't be
authenticated. And that by doing this, a malicious individual could
take control or damage my system.
I have taken the view that the DVD-supplier would not remain in
business for very long if the products that he sold had been doctored
to permit the scenario described above.
But if there is an install-step that would validate the signature on the
installed package, I would be grateful to be pointed to it.
On Tue, 11 Sep 2007 11:15:53 -0700, Andrew Sackville-West wrote:
On Mon, Sep 10, 2007 at 09:17:59PM +, Felix Karpfen wrote:
these errors (untrusted packages) have to do with the new secure-apt
system which uses gpg keys to confirm the signatures on
packages. Install the debian-archive-keyring package and then update.
The package was installed by default during the upgrade to Etch. But
the documentation on how to use it is sparse. A new (December 2003!) apt
routine - apt-key - can now be invoked and offers the following options:
| Usage: apt-key [command] [arguments]
|
| Manage apt's list of trusted keys
|
| apt-key add file - add the key contained in file ('-' for
stdin)
| apt-key del keyid - remove the key keyid
| apt-key update - update keys using the keyring package
| apt-key list- list keys
But How do you use the key(s) listed in /etc/apt/trusted.gpg to
authenticate the individual installed packages.
Oh, dpkg automatically checks it for you when you use apt-get/aptitude
to install package. (Unless you disable it.)
So is the answer to my question:
use aptitude and not Synaptic for installing packages?
Well look for mail archive (debian-user or debian-devel) on archive key
issues. You are not alone.
My next step!
Thank you for the very detailed reply.
Felix
--
Felix Karpfen
Public Key 72FDF9DF (DH/DSA)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian packages without md5sums
On Thu, 13 Sep 2007 12:29:28 -0700, Andrew Sackville-West wrote: On Wed, Sep 12, 2007 at 09:25:39PM +, Felix Karpfen wrote: How do you use the key(s) listed in /etc/apt/trusted.gpg to authenticate the individual installed packages. sorry, beyond me. on my system it just works. Does untrusted have the meaning assigned in gpg - i.e. the content has not been altered, but the signer is unknown? I'm not sure. If so, then I am worrying about nothing!! not if the package is a compromised package that's been signed by the compromiser so that its signature is good but from an untrusted source, but we're outside my understanding here. Mine too. But an out-of-sync repository sounds a much worse fate that the remote possibility that packages on Etch DVDs (from a reputable supplier) were tampered with and then gpg-signed by the tamperer. Thank you for sharing your experience. Felix -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian packages without md5sums
On Thu, 13 Sep 2007 12:29:28 -0700, Andrew Sackville-West wrote: On Wed, Sep 12, 2007 at 09:25:39PM +, Felix Karpfen wrote: How do you use the key(s) listed in /etc/apt/trusted.gpg to authenticate the individual installed packages. sorry, beyond me. on my system it just works. Does untrusted have the meaning assigned in gpg - i.e. the content has not been altered, but the signer is unknown? I'm not sure. If so, then I am worrying about nothing!! not if the package is a compromised package that's been signed by the compromiser so that its signature is good but from an untrusted source, but we're outside my understanding here. Mine too. But an out-of-sync repository sounds a much worse fate that the remote possibility that packages on Etch DVDs (from a reputable supplier) were tampered with and then gpg-signed by the tamperer. Thank you for sharing your experience. Felix -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian packages without md5sums
On Tue, 11 Sep 2007 11:15:53 -0700, Andrew Sackville-West wrote:
On Mon, Sep 10, 2007 at 09:17:59PM +, Felix Karpfen wrote:
The fault is mine/my setup. My connection to the internet is slow;
hence I am reduced to using the DVDs for upgrades. Although I procured
the official Etch DVD set from a supplier listed by Debian, there were
numerous notifications during the dist-upgrade that I was installing
untrusted packages.
these errors (untrusted packages) have to do with the new secure-apt
system which uses gpg keys to confirm the signatures on
packages. Install the debian-archive-keyring package and then update.
The package was installed by default during the upgrade to Etch. But
the documentation on how to use it is sparse. A new (December 2003!) apt
routine - apt-key - can now be invoked and offers the following options:
| Usage: apt-key [command] [arguments]
|
| Manage apt's list of trusted keys
|
| apt-key add file - add the key contained in file ('-' for
stdin)
| apt-key del keyid - remove the key keyid
| apt-key update - update keys using the keyring package
| apt-key list- list keys
But How do you use the key(s) listed in /etc/apt/trusted.gpg to
authenticate the individual installed packages.
I have no wish to re-invent the wheel - even if I knew how. A pointer to
documentation would help. I have the gpg package installed and have used
it occasionally to sign my emails; but there must be a routine for using
the Etch Stable Release Key for checking 1000+ installed Debian
packages.
An afterthought:
Does untrusted have the meaning assigned in gpg - i.e. the content
has not been altered, but the signer is unknown?
If so, then I am worrying about nothing!!
Is there an alternative to aptitude update or do I have to live with the
missing md5sums and untrusted packages?
there is not really any alternative to aptitude update
If the update needs to be done while online, it is probably a lost
cause.
Thank you for taking the time to point me in the right direction.
Felix Karpfen
--
Felix Karpfen
Public Key 72FDF9DF (DH/DSA)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Debian packages without md5sums
By diligent lurking on this NG, I read of and tried the following routines: 1. debsums_gen -l - which gave the following output (first two lines): Checking for packages without md5sums list aalib1 akode alsaplayer at base-config base-files bc bin86 binutils and 2.# aptitude search '~i! ~M' - which started as follows: i a2ps i adduser i afio i alien i alsa-base i alsa-oss i alsa-utils i alsamixergui i alsaplayer i alsaplayer-alsa i alsaplayer-common i alsaplayer-gtk i alsaplayer-oss i antiword i apt i apt-utils i apt-zip i aptitude i aptitude-doc-en i aspell i aspell-en i at i audacity From which I deduce that some packages lost their md5sums during my upgrade from Sarge to Etch and some packages did not. The fault is mine/my setup. My connection to the internet is slow; hence I am reduced to using the DVDs for upgrades. Although I procured the official Etch DVD set from a supplier listed by Debian, there were numerous notifications during the dist-upgrade that I was installing untrusted packages. And, due to my slow internet connection, I refrained from running the recommended aptitude update at the end of the successful dist-upgrade. Is there an alternative to aptitude update or do I have to live with the missing md5sums and untrusted packages? Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Acceptable CPU temperature range of idle computer?
On Tue, 04 Sep 2007 12:29:08 +0200, Jörg-Volker Peetz wrote: On Tue, 04 Sep 2007 12:29:08 +0200, Jörg-Volker Peetz wrote: Felix Karpfen wrote: Since upgrading from Sarge to Etch, my CPU temperature appears to be running 5-10 deg.C higher Am I heading for a problem? The documentation says that the CPU is: Socket 478 for Intel4/Celeron By diligent lurking, I have discovered the existence of the lshw package. It identifies all the installed hardware; this includes the following info (which may be relevant): *-core description: Motherboard product: P4S800 vendor: ASUSTeK Computer INC. version: ASUS P4S800 ACPI BIOS Revision 1006 (12/31/2003) size: 64KB capacity: 192KB *-cpu description: CPU product: Intel(R) Celeron(R) CPU 2.60GHz vendor: Intel Corp. physical id: 4 bus info: [EMAIL PROTECTED] version: 15.2.9 slot: PGA 478 size: 2600MHz capacity: 3733MHz width: 32 bits clock: 100MHz capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr and I have failed to locate any reference to an acceptable temperature range. All advice will be gratefully received. Although you don't seem to refer to a notebook computer, this site may be of some help: http://www.linuxpowertop.org/ Suggested link is flagged for download. From the supplied description, it looks helpful - even if it does not address my problem directly. On notebook computers with no load I see temperatures (with the command acpi -V) as follows: pentium 4m 1.9 GHz: 45 deg C pentium-m 2 GHz : 41 deg C turion64 MT-40 2.2 GHz: 50 deg C Under load these cpus can heat up far above 60 deg C. From which I conclude that CPUs can cope with temperatures of 60 deg C. Many thanks. Felix -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Acceptable CPU temperature range of idle computer?
On Sat, 01 Sep 2007 21:13:42 -0400, Douglas A. Tutty wrote: On Sat, 01 Sep 2007 21:13:42 -0400, Douglas A. Tutty wrote: On Sat, Sep 01, 2007 at 09:17:44PM +, Felix Karpfen wrote: Since upgrading from Sarge to Etch, my CPU temperature appears to be running 5-10 deg.C higher; SNIP and I have failed to locate any reference to an acceptable temperature range. All advice will be gratefully received. Run top. Do you really have 120 processes actually running? What are they if you consider the computer idle? The info came from KSysGuard - which, I believe, analyses the top data. I can't even load up my P-II lower than about 60% idle momentarily or 80% consistantly. Then again it only has 64 MB ram so to do anything big gets into swapping which gives the CPU pleanty of time to rest :) Looks as though bigger is not always better. I have 512 MB RAM. My CPU works hard; the swap partition is just a decoration - it never gets used. My Athlon64 never gets above 35 C, my video card's GPU never above 40C. Then again, the internal case temp is ambient == 20 C. There are some benefit to living in Canada! Here (Australia) our ambient temperatures (and the motherboard temperatures) creep up to the high 30s in summer; now (our Spring) it is 24 deg C and the CPU temperature is (currently) 44 deg C. Yesterday, during a Systems backup, the CPU temperature reached 62 deg C! And the computer still works today! But, one day my luck will run out. What controlls your fans? I do not think that the fan (I have only one) is the problem. Otherwise the MB temperature would also be higher. Thank you for sharing your experience, Felix -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Acceptable CPU temperature range of idle computer?
Since upgrading from Sarge to Etch, my CPU temperature appears to be running 5-10 deg.C higher; immediately after booting it is a healthy 30 deg.C and it creeps up to 45-50 deg.C within an hour. On the idle (?) computer there are some 120 processes running and the system load is about 40%. Am I heading for a problem? The documentation says that the CPU is: Socket 478 for Intel4/Celeron and I have failed to locate any reference to an acceptable temperature range. All advice will be gratefully received. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unsolved Scanner Problem
On Thu, 23 Aug 2007 08:43:31 -0400, Thomas H. George wrote: SNIP Thinking about this I have concluded that it is not the scanner, it is unlikely that its the sane backend (Iscan uses the sane backend so it is in play for both scanners), it is unlikely that both Iscan and Xsane have the same fault, it is unlikely that it is a udev/usb problem as I have not seen myriad postings on the Debian user's list, so the problem must be with the kernel I complied. Does any one have any idea what I might have done wrong? I ran into (unresolved) scanning-problems when I upgraded from Sarge to Etch. Epson has a bulletin-board for posting scanner problems. Although _I_ have failed dismally in persuading this Bulletin Board to accept my messages, hopefully you can work out how to use it. A starting-point is: http://avasys.jp/hp/menu00500/hpg00442.htm Good luck Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Using apt-zip -was Re: Upgrade on box not on Net
On Thu, 05 Jul 2007 16:02:44 -0400, Celejar wrote: On Thu, 5 Jul 2007 20:25:09 +0100 John K Masters [EMAIL PROTECTED] wrote: Is it possible to upgrade a box not connected to the Internet? This is what the apt-zip package is for. 2 simple queries: 1. ZIP drives are a thing of the past. Presumably apt-zip works equally well with usb memory-sticks; and 2. My daughter - who has broadband access - uses a Mac. Can that be used to download the packages identified by apt-zip? Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to move the master boot record?
On Sat, 30 Jun 2007 23:28:05 +0200, Nigel Henry wrote: I had to add to /etc/modules a couple of modules. I can't remember in which order, but at first I had no mouse pointer showing at all. I modprobed one module, then had the mouse pointer, but couldn't move it, then modprobed the second module, and all was working ok. See the 2 modules below. mousedev psmouse Both the Sarge and the Etch kernels have a psmouse driver; only the Sarge kernel (2.6.8) has a mousedev driver. Armed with this discovery, I took another look at my operational /etc/lilo.conf file. And I now suspect that my current entries are insufficiently precise (and the guidance in the man-page is too cryptic|out-of-date) to load the desired kernels. Given that the relevant entries in my /boot directory read: System.map-2.6.18-4-486 System.map-2.6.8-2-386 config-2.6.18-4-486 config-2.6.8-2-386 initrd.img-2.6.18-4-486 initrd.img-2.6.8-2-386 vmlinuz-2.6.18-4-486 vmlinuz-2.6.8-2-386 what are the needed entries in /etc/lilo.conf that will result in loading Etch with the 2.6.18-4-486 kernel and Sarge with the 2.6.8-2-386 kernel? All advice will be gratefully received. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to move the master boot record?
On Fri, 29 Jun 2007 15:33:09 +0200, Rodolfo Medina wrote: On Fri, 29 Jun 2007 15:33:09 +0200, Rodolfo Medina wrote: I want to do so beacuse: now I'm still using Debian Sarge, which is installed in hda6; I want to install Debian Etch in hda9; then when I'm sure that everything is all right with Etch I want to boot from hda9, so hda6 can be formatted again. Has anyone done this successfully? I faced a similar problem, wrote to linux.debian.user for advice and scored a zero response. In my case I went ahead, made a backup of Sarge to a newly-created partition, checked that I could boot into it and then ran a dist-upgrade on my main Sarge partition. Result: - Etch boots and works perfectly (fortunately); - Sarge boots (despite some fatal notifications during the boot); all the tested programs still work; the mouse does not. Running dpkg-reconfigure xserver-xfree86 achieved nothing. For the record, I use LILO. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Scenario of a failed upgrade - advice request - followup
On Tue, 05 Jun 2007 07:10:06 +1000, Felix Karpfen wrote ([EMAIL PROTECTED]): Since posting the above message, I have confirmed that I can (currently) use LILO to boot both my installed Sarge and my backup Sarge. I can therefore make my queries more concrete. They now read: a) I would like to ensure that after the upgrade to Etch, the 2 image entries in /etc/lilo.conf point to the correct images. The unstated assumption in my posting was that there will be _2_ image entries after the upgrade to Etch. If there is only one backwards-compatible kernel image, then my problems with using it to boot Sarge are a non-issue. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Scenario of a failed upgrade - advice request
This posting - sent via gmane - is my second attempt to send this posting. If the first attempt ultimately reached its intended destination, then I apologise for wasting time and bandwidth. The original message read as follows: | I have acquired a DVD set of the official release of Debian 4.0 and | studied the release notes to the best of my abilities. | | And have taken to heart the included advice to make a full copy of my | current clean and fully operational Sarge installation. | | I am left with one query that is best explained by a hypothetical | situation - which, hopefully, will never happen. | | Assume that my upgrade to Etch has managed to get to the end of the | dist-upgrade step without any obvious major hitch. What steps can I | take - before or after running /sbin/lilo to ensure that the bootloader | will recognise not only the newly-installed Etch but also my backup copy | of Sarge. And - most important - will load the Sarge-backup even if an | attempted boot into Etch fails. | | Specifically what entries should be present in my boot directory, my | /etc/lilo.conf file and (possibly) elsewhere before I shut down the | computer and attempt to reboot. Since posting the above message, I have confirmed that I can (currently) use LILO to boot both my installed Sarge and my backup Sarge. I can therefore make my queries more concrete. They now read: a) I would like to ensure that after the upgrade to Etch, the 2 image entries in /etc/lilo.conf point to the correct images. The sample file in man lilo.conf gives the full path (i.e. /boot/IMAGE) to each image in the (sample) boot directory. Is this mandatory once the boot directory contains more than one image? b) will an attempt to boot into the backup Sarge work if only the etch-upgraded version of initrd is present in the upgraded /boot directory? and c) do the symlinks in the O/S's root need editing? I am aware that I will know the answer to these questions after the upgrade. But forewarned is forearmed.. All advice will be gratefully received. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Using defoma to install heritage truetype fonts
On Mon, 27 Nov 2006 22:33:54 +0100, Florian Kulzer wrote ([EMAIL PROTECTED]): On Mon, Nov 27, 2006 at 06:52:03 +1100, Felix Karpfen wrote: SNIP I was hoping that an alternative route exists, that will enable me to point the TrueType install routine to the directory that contains the few fonts that I already have on my box. SNIP I also seem to remember that both KDE and Gnome have a font installer option somewhere in their configuration dialogs. I know that with KDE you can just right-click on a .ttf file and choose Actions Install. Thank you. That solved my problems. Using fc-cache would have been more elegant. But Debian insisted that the fonts should be present in /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType/. I dutifully followed these instructions by creating symlinks in that directory. But I was too chicken to point fc-cache to the symlinks. Since I am the only user, the offered KDE routine (pointed at the actual files in my home directory) worked perfectly and is adequate. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Using defoma to install heritage truetype fonts
On Fri, 24 Nov 2006 18:16:36 +0100, Michelle Konzack wrote ([EMAIL PROTECTED]): Am 2006-11-21 17:07:03, schrieb Ismael Valladolid Torres: Jan Willem Stumpel escribe: apt-get install msttcorefonts will do (most of) what you want. He'll need to enable the non-free repo in his sources.list. And of cause he need to be On-Line since this Package want to download something from an external Server. Realy bad, if you have no Internet and only CD's or DVD's. Firstly, I would like to thank all who were good enough to reply to my query. Regrettably some of the responses did not make it to my box; the cause is still obscure. However, by following the quotes from the posting from Michelle Konzack - that _did_ make it - I take it that the advice was to use msttcorefonts. I tried that already and the install failed to go to completion for the reason listed above - I was not connected to the internet. And I am reluctant to rerun the package while connected unless I have at least some idea what size of a download I am likely to get. Since I only have a 56k modem, a multi-megabyte download is not undertaken lightly. I was hoping that an alternative route exists, that will enable me to point the TrueType install routine to the directory that contains the few fonts that I already have on my box. Years ago, there were users, with access to both Linux and Windows, who claimed that the Linux substitutes for TrueType fonts were ugly. If this is still the case, then my aesthetic sensibilities are of a low order. As flagged in the original posting, I have lived successfully without my TrueType fonts for more than 12 months and am not convinced that I need them in my current setup (Debian Sarge). I propose to Google the debian.user archives in order to retrieve the postings that I have lost; in the meantime, I hasten to repeat my thanks to all who were good enough to send advice. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upcoming Release of Debian GNU/Linux 4.0 - a beginner's query/request
On Sun, 30 Jul 2006 08:17:34 -0400, hendrik wrote ([EMAIL PROTECTED]): On Sun, Jul 30, 2006 at 07:30:08AM +1000, Felix Karpfen wrote: My thanks also to the other respondents who were good enough to share their experiences. I am especially grateful for the advice from hendrik to keep a copy of the currently-operational system What I said (or should have said) was keep an *operational* copy of the currently-operational system. I actually used extra partitions to store the copy and checked that I could boot it. That is the plan of campaign. Fortunately, thanks to the massive sizes of the current HDs, there is plenty of unused space on the working drive and I have a second drive that is used only for backups (in case the working drive fails). And, of course, a full backup achieves nothing if it cannot be loaded! So changes to lilo.conf and fstab are on the agenda. Thank you for the followup. Felix -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upcoming Release of Debian GNU/Linux 4.0 - a beginner's query/request
On Wed, 26 Jul 2006 19:08:27 -0400, Joey Hess wrote ([EMAIL PROTECTED]): Felix Karpfen wrote: This posting is an advance-request to include update from Debian 3.1 instructions in the proposed release of Debian 4.0. If existing documentation applies, a relevant URL would suffice. http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#s-newkernel Of course that's the instructions for upgrading _to_ debian 3.1, but you get the point. Thank you. That is _exactly_ what I was was searching for. But I looked in the wrong place! I had assumed - incorrectly - that release notes only document the _changes_ in the supplied new version (and had not read them!). I note, from a cursory read, that the dist-upgrade should be run from a console (and not from XWindows). Not as straightforward as it once was, since the system currently defaults to gdm. But I have till December at the earliest to iron out the details. My thanks also to the other respondents who were good enough to share their experiences. I am especially grateful for the advice from hendrik to keep a copy of the currently-operational system (also mentioned in the release-notes) and the fact - mentioned by Gustavo Franco - that that the desktop tasks differ from the main packages. I also noted (from another posting to this NG) that kernel 2.6.17 plays havoc with the XFS filesystem (which I am using) and that the latest release - 2.6.17.7 - corrects the problem. Again, I suspect that this issue will be fully resolved before the stable version of etch is released. Finally, a repeated hearty thank you to all who were good enough to reply to my query. Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Upcoming Release of Debian GNU/Linux 4.0 - a beginner's query/request
By adhering to the install instructions that were on Disk 1 (of a 14-disk CD set) of Debian 3.1, I have ended up with a fully functioning OS. These instructions assume a clean install (which was the case). This posting is an advance-request to include update from Debian 3.1 instructions in the proposed release of Debian 4.0. If existing documentation applies, a relevant URL would suffice. My concern is the upgrade of the kernel. I presume - perhaps incorrectly - that this will need a separate routine. Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: upgrade only if installed
On Wed, 14 Jun 2006 16:41:32 -0700, Bill Thompson wrote ([EMAIL PROTECTED]): On Wed, 14 Jun 2006 18:08:15 -0400 Stephen R Laniel [EMAIL PROTECTED] wrote: I'm pretty certain that you can't do 'apt-get upgrade [package]'; you can only do 'apt-get upgrade' Snip Note to self: Always always always read the fine man-pages) man apt_preferences? Could it be achieved with suitable pinning entries? Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2 tmpfs filesystems mounted?
On Tue, 18 Apr 2006 07:17:36 +1000, Felix Karpfen wrote ([EMAIL PROTECTED]): Since installing Debian 3.1r1 on a healthy HD, everything appears to work. However when I shut it down, there is a complaint about tmpfs running and being switched to read-only mode. SNIP Does something need fixing? My thanks to all who were good enough to reply and advise that they have similar outputs. And now the reason for worrying: Shutting down my computer works perfectly; but the only time that I tried Reboot it got as far as the read-only complaint and then went into an infinite loop. This may just have been a coincidence. I lack the nerve to check if it is repeatable. I had to pull the plug out to get out of the infinite loop and breathed a sigh of relief when I switched the power back on and Debian booted without a murmur. Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
2 tmpfs filesystems mounted?
Since installing Debian 3.1r1 on a healthy HD, everything appears to work. However when I shut it down, there is a complaint about tmpfs running and being switched to read-only mode. Is this what is supposed to happen? df gives the following output: [EMAIL PROTECTED] felixk]$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/hdb5 28822528 4756700 24065828 17% / tmpfs 258328 0258328 0% /dev/shm tmpfs10240 792 9448 8% /dev Does something need fixing? Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Messages sent to printer fail to arrive
I have just completed a clean install of Debian 3.1r1 on a new HD. Most of it works like a charm. CUPS (foomatic) identified my aged printer and supplied the correct driver. But the test message failed to arrive. The following info probably contains the needed clue(s): From syslog: - kernel: lp0 using parport0 (interrupt drive) - udev[3234] creating device node under '/dev/lp0' From printer configuration: - Interface -Printer on Local System -Connected to Parallel Port #1 -URI parallel: /dev/unknown-parallel0 All suggetions (other than buy a new printer) will be gratefully received. Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Creating a journal as an afterthought
On Fri, 10 Mar 2006 12:55:22 -0500, Andrew Cady wrote ([EMAIL PROTECTED]): On Thu, Mar 09, 2006 at 08:11:45AM +1100, Felix Karpfen wrote: [...] The second paragraph suggests that this should have happened automatically when I updated my (very aged) Woody to Debian 3.1r1 (the installed kernel image is now kernel-image-2.6.8-1-386) and changed the entry in /etc/fstab. This does not appear to be the case. Anyway, to verify that a filesystem is journaling, use: tune2fs -l filesystem device|grep 'Filesystem features' And here is what I got: # tune2fs -l /dev/hda6 | grep Filesystem features Filesystem features: filetype sparse_super # tune2fs -l /dev/hda7 | grep Filesystem features Filesystem features: has_journal filetype sparse_super For good measure, I also ran the command on /dev/hda7. This contains the Sarge pre-release and was installed as an .ext3 filesystem. You should see the string has_journal in that line. If you do, don't worry about initrd's complaining. It looks as though the initrd complaint is valid. And adding the journal (by running the command from /dev/hda7) is not a problem. I just wanted to check that I will not break something if I do. The output, that tune2fs -l can produce, was news to me. Thank you for pointing it out. Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: alsaconf successful. No sound!
On Tue, 07 Mar 2006 20:22:55 -0800, Mark Fletcher wrote ([EMAIL PROTECTED]): --- Scott [EMAIL PROTECTED] wrote: Francesco Bochicchio spake thusly on 03/07/2006 02:54 PM: Il Tue, 07 Mar 2006 21:50:14 +0100, Felix Karpfen ha scritto: However when checking the output of a .wav file by running the play command from a console, I get a deafening silence. alsamixer says the the playback master is set at 74. What about the PCM channel? By default with ALSA it is muted and with 0 volume. You need to unmute and raise its volume using alsamixer. Original Poster -- did un-muting the PCM channel and setting its volume solve your problem? If not, try unmuting and setting volume for the Headphone channel. Firstly, I would like to thank all who were good enough to post some advice and apologise for taking so long to report on the outcomes. And secondly I am pleased to report that the problem has either been fixed or has gone away. Given that I followed several suggestions (or my understanding of the suggestions), I am uncertain which made the difference. So here are all the details: In my original posting, I was needlessly brief about the info displayed by alsamixer. alsamixer also reported that my card is SiS SI7012 and my analogue driver is AD1890. According to the kernel docs, the card (SiS SI7012) requires module snd-intel8x0 which is loaded (according to lsmod). My selected sound player (using fvwm2 windows manager) is play(sox). I do not appear to have a Headphone channel, so I cannot unmute it; I did unmute the Phone channel, the Mono Master channel and the Center channel. The PCM channel was already not muted and set at close to the maximum. When exploring the advice in http://alcopop.org/log/2006/02/12/ I got the following output from amixer: # amixer scontents | grep Jack Simple mixer control 'Surround Jack as Input',0 Simple mixer control 'Center/LFE Jack as Input',0 No Line Jack; no Headphone Jack. Both the found Jacks were left off. I have discover1 installed and would need more guidance before I can boot with acpi=off. If it is a service that can be toggled with sysvconfig, then I have no such service. I checked what I had achieved before following up the information supplied by Andrew Sackville-West in ([EMAIL PROTECTED]). and, as mentioned at the start, I now have sound. Again, my thanks to all respondents for their suggestions. Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Creating a journal as an afterthought
I have checked the relevant entry in man tune2fs and, given my limited expertise, I considered it prudent to seek additional guidance. The relevant paragraphs read: ,[ man_page.txt ]- | -j Add an ext3 journal to the filesystem. If the -J option is not | specified, the default journal parameters will be used to create | an appropriately sized journal (given the size of the filesys- | tem) stored within the filesystem. Note that you must be using | a kernel which has ext3 support in order to actually make use of | the journal. | | SNIP | | On some distributions, such as Debian, if an initial ramdisk is | used, the initrd scripts will automatically convert an ext2 root | filesystem to ext3 if the /etc/fstab file specifies the ext3 | filesystem for the root filesystem in order to avoid requiring | the use of a rescue floppy to add an ext3 journal to the root | filesystem. | ` The second paragraph suggests that this should have happened automatically when I updated my (very aged) Woody to Debian 3.1r1 (the installed kernel image is now kernel-image-2.6.8-1-386) and changed the entry in /etc/fstab. This does not appear to be the case. One of the messages displayed when booting the updated setup reads ext3: No journal on filesystem on hda6 . /dev/hda6 is the partition that was updated. What have I missed? Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
alsaconf successful. No sound!
I ran alsaconf on my recently-updated Debian 3.1r1. It worked like a charm and ended with the following messages: Running update-modules... Loading driver... Setting default volumes... === Now ALSA is ready to use. For adjustment of volumes, use your favorite mixer. Have a lot of fun! However when checking the output of a .wav file by running the play command from a console, I get a deafening silence. alsamixer says the the playback master is set at 74. What have I missed? Prior to the update (when using the Sarge pre-release) sound worked OK. Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xfs filesystem and Debian Sarge
I note the Sarge contains a package - xfslibs-dev - that makes it possible to format a partition as an xfs filesystem. Is there any documentation| HOWTO that would enable a rank amateur to use an xfs-formatted partition for installing and running Sarge? Preferably with information on possible problems | headaches that such a venture would entail. Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Crashes and lock-ups in Sarge
On Sun, 15 Jan 2006 09:53:08 -0600, Adam Fabian wrote ([EMAIL PROTECTED]): I would do a clean install, if you don't have known-good backups to restore to the new hard-drive. Tracking down errors because of randomly corrupted files could be your worst nightmare. A bitter pill to swallow. But, I fear that it is probably the best (and certainly the safest) option. It is bad enough to have _one_ HD that performs unpredictably. And no point in copying the errors to a second drive. Thank you for taking the trouble to answer my query. Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Using USB Memory-Stick with Debian - followup
On Sun, 15 Jan 2006 07:49:31 +1100, Felix Karpfen wrote ([EMAIL PROTECTED]): With the help of Google, I have located the following instructions for configuring Debian to recognise the presence of a USB Memory-Stick: Snip Pointers to relevant documentation (that would enable amateurs to understand what is suggested in the recipe) would be welcome. Follow-up: A belated thank you for the suggested pointers. They taught me the Linux vocabulary (usb-storage; flash-memory) which will make the next step easier. In the interval, I had opted to do a dist-upgrade of my (pre-release) Sarge to Debian 3.1 r1. And lost my ability to load XWindows. That problem is now solved (bug #255744) - and I am ready to tackle the the contents of dev HOWTO. Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Using USB Memory-Stick with Debian
With the help of Google, I have located the following instructions for configuring Debian to recognise the presence of a USB Memory-Stick: ,[ memory_stick.txt ]- | USB memory stick | | * plug in Memory-Stick | * become root (su -) | * modprobe usb-storage | * in /etc/fstab: directly after the line with proc /proc ... | add a line like this: | usbdevfs /proc/bus/usb usbdevfs noauto,user 0 0 | * now root may mount the memory stick: mount /dev/sda1 /mnt | and read/write on /mnt | * in /etc/fstab enter a line as follows: | /dev/sda1 /usbstick autouser,noauto0 0 | * mkdir /usbstick | * in /etc/modules add: | # For USB memory stick | usb-storage | * Now every user may mount and umount /usbstick `-- Pointers to relevant documentation (that would enable amateurs to understand what is suggested in the recipe) would be welcome. Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Crashes and lock-ups in Sarge
Since October 2005 I have been experiencing repeated crashes and
lock-ups - of varying degrees of seriousness.
Initially, I attributed these to some software incompatibilities and
sought advice in the relevant users groups.
And was advised that it sounded like a hardware problem - my HD was
on its way out.
Each subsequent crash re-enforced this diagnosis; so I have purchased
and installed a new HD (and a new cable - just in case). Debian 3.1
r1 should be arriving within the next few days and my main remaining
question appeared to be:
Do I start from scratch or copy my existing setup to the new HD
before it dies and refuses to be revived
when I read the following in
http://www.seismo.ethz.ch/linux/debian_software_installation.html:
,[ ext3_error.txt ]-
| Possible Problems with ext3 Journaling filesystem
|
| On one of our PCs, running Kernel 2.6.8, we had a problem during
| mid-October 2004: In the file /var/log/messages we see entries like:
|
| Oct 16 02:43:08 og kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
| Oct 16 02:43:08 og kernel: hda: dma_intr: error=0x84 { DriveStatusError
BadCRC }
|
| When switching to console mode (cntl-alt-F1), we see something like:
| EXT3-fs error (device hda6) in start_transaction: Journal has aborted
|
| What helped, was booting with a Knoppix-CD, then enter su - to become
| root and afterwards enter cat /etc/fstab in order to see, what
| partitions were detected. In our case, the partition where Debian linux
| was running before and has caused problems with the ext3 file system, a
| filesystem check was done as follows: fsck /dev/hda6. The journal file
| was obviously re-created and things worked smooth after a reboot.
|
| Mhh... 10 days later we have the same problem, but this time Knoppix
| cannot create a file /etc/fstab - could this be due to a hardware
| problem? Disk failure? We shut down the PC for one day and were then
| successful in booting it with Knoppix, did a fsck /dev/hda6 and the
| machine booted again.
`
Given that I get virtually identical failure messages when I run
fsck -cc on my suspect drive|partitions, I would be interested in
expert comments before I take my next step.
Felix Karpfen
--
Felix Karpfen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Moving a Debian install in to new hardware?
On Tue, 03 Jan 2006 16:36:43 -0600, Matt Zagrabelny wrote ([EMAIL PROTECTED]): On Tue, 2006-01-03 at 13:19 -0800, Jimmy Liang wrote: What I want to do is to move all that to a new box I have, with dual Xeon. Can you suggest the best way to do this? I'd like to move it to a larger drive, if possible, but its not critical. SNIP 3. If and when I do need to exchange it for the larger drive, how would I go about doing that without any reinstalls? google for copy hard drive or similar words. I took this advice and found: ,[ hd.txt ]- | Hard Disk Upgrade Mini How-To | By Yves Bellefeuille [EMAIL PROTECTED], | and Konrad Hinsen [EMAIL PROTECTED] | | v2.11, 13 April 2000 ` The instructions are detailed and within the scope of rank amateurs. Regrettably, they are slightly out-of-date. Specifically, they envisage the use of ext2 file systems and provide detailed instructions for configuring the lilo boot routine. Are there any more recent texts that spell out how to configure grub for booting the copied system? Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Stock Sarge segfaults, and later crashes!
On Sun, 27 Nov 2005 06:57:56 -0600, Hugo Vanwoerkom wrote ([EMAIL PROTECTED]): Felix Karpfen wrote: On Wed, 23 Nov 2005 15:58:44 -0500, Marty wrote ([EMAIL PROTECTED]): Regrettably, I had the same crash experience twice in the past few weeks. Never before that in 10 years of using PCs. SNIP I attributed the crashes to my non-standard setup - fvwm2 XWindows Manager and Gnome Session Manager. So I flagged the problem with the fvwm user group. And was advised - it sounds like a faulty HD. SNIP What sort of crashes? While I lack the technical knowhow of the previous posters, the symptoms of my crashes sounded the same to me as those reported in this thread.. The running program locked up, the root directory switched to read-only mode and running a manual fsck found a lot of orphans. Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Stock Sarge segfaults, and later crashes!
On Wed, 23 Nov 2005 15:58:44 -0500, Marty wrote
([EMAIL PROTECTED]):
Roberto C. Sanchez wrote:
It sounds like you may have a bad memory module.
I will run some more tests and report back if I find a hardware problem.
Regrettably, I had the same crash experience twice in the past few
weeks.
Never before that in 10 years of using PCs.
And, even more regrettably, I lack the expertise of both of the original
poster and of the follow-up adviser.
But the circumstances in which my crashes occurred were _totally_
different.
I attributed the crashes to my non-standard setup - fvwm2 XWindows Manager
and Gnome Session Manager.
So I flagged the problem with the fvwm user group.
And was advised - it sounds like a faulty HD.
Which is possible. But the computer is 18 months old and my
recent (repeat) crashes only started a few weeks ago.
For what it is worth, I installed Sarge (pre-release) in August 2004,
shortly after purchasing a new computer. And I purchased the new
computer because my 9-year-old computer was starting to groan and I was
attempting to forestall an unrecoverable crash :-{ .
Felix Karpfen
--
Felix Karpfen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrading to linux-2.6.14.2
On Fri, 18 Nov 2005 16:45:55 -0200, Henrique de Moraes Holschuh wrote ([EMAIL PROTECTED]): install and learn to use the kernel-package package, and make-kpkg utility. It will make your life a lot easier. A related request from another (fairly) recent Debian user (with a poor memory): I am aware that the above-requested advice has been asked for and answered many times. How about posting, at regular intervals, an FAQ which lists some basic URLs that point to the wealth of published information on using Debian. Including access to the linux.debian.user archives (with tips for searching the archives - if that needs to be spelled out). Felix Karpfen -- Felix Karpfen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cleaning Sarge's tmp directory
On Sun, 18 Sep 2005 14:37:09 +0200, Maurits van Rees wrote ([EMAIL PROTECTED]): On Sun, Sep 18, 2005 at 07:11:15AM +1000, Felix Karpfen wrote: I suspect that there is a missing cron routine and would welcome the needed pointers in order to persuade the tmp directory to live up to its name. Try apt-get install tmpreaper. My thanks to all three respondents for their advice. Some of the advice added a little to my uncertainties. tmpreaper was news and appears to do everything needed; and _more_! , | Description: | | Cleans up files in directories based on their age This package provides | a program that can be used to clean out temporary-file directories. It | recursively searches the directory, refusing to chdir() across symlinks, | and removes files that haven't been accessed in a user-specified amount | of time. | | ` Assuming that I have got the correct syntax, I got the following in a test-run: , | [EMAIL PROTECTED] felixk]$ tmpreaper --test 24h /tmp/ | (PID 32043) Pretending to clean up directory `/tmp/'. | (PID 32044) Pretending to clean up directory `.X11-unix'. | Not a regular file or directory `X64' -- skipping. | (PID 32044) Back from recursing down `.X11-unix'. | (PID 32044) Pretending to clean up directory `.ICE-unix'. | Not a regular file or directory `2581' -- skipping. | (PID 32044) Back from recursing down `.ICE-unix'. | (PID 32044) Pretending to clean up directory `.font-unix'. | Not a regular file or directory `fs7110' -- skipping. | (PID 32044) Back from recursing down `.font-unix'. | (PID 32044) Pretending to clean up directory `orbit-felixk'. | Not a regular file or directory `linc-9c9-0-7a9ba17e3a8bb' -- skipping. | Pretending to remove file `orbit-felixk/bonobo-activation-register.lock'. | Not a regular file or directory `linc-9e5-0-1006e1133aa3f' -- skipping. | | Remainder snipped | -- In addition, a tmpreaper script has been added to /etc/cron.daily that appears to protect /tmp files and directories that are not meant to be removed. anacron is already installed. But I hesitate to run any rm command as root without knowing which files can safely be removed and which should not be touched. And the advice that the /tmp directory is cleaned at every reboot helps to explain why it did not contain many more files; it fails to explain why a lot of *.jpg files survived for over 8 months. As stated at the beginning, I am grateful for all the advice and tmpreaper appears to solve my problem and protect me from my own defective knowledge. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Cleaning Sarge's tmp directory
As a fairly recent arrival to Debian, I have just viewed the current content of my /tmp directory. And found the following (snipped): , | total 256 | -rw-r--r-- 1 felixk felixk 44215 Jan 22 2003 craig01_small.jpg | -rw-r--r-- 1 felixk felixk 1301 Jan 22 2003 craig02_small.jpg | | SNIP | | drwxr-xr-x 2 felixk felixk 4096 Sep 17 07:57 hsperfdata_felixk | drwx-- 2 felixk felixk 4096 Sep 12 08:35 kde-felixk | drwx-- 2 root root4096 Sep 15 17:02 kde-root | drwx-- 2 felixk felixk 4096 Sep 16 19:46 keyring-I5kAqy | drwx-- 2 felixk felixk 4096 Sep 17 15:37 ksocket-felixk | drwx-- 2 root root4096 Sep 15 17:06 ksocket-root | srwxr-xr-x 1 felixk felixk 0 Sep 16 19:46 mapping-felixk | drwx-- 2 felixk felixk 4096 Sep 12 07:57 mc-felixk | drwx-- 2 root root4096 Sep 12 17:00 mc-root | drwx-- 3 felixk felixk 4096 Sep 12 08:36 mcop-felixk | | SNIP | | -rw-r--r-- 1 felixk felixk 2073 Jan 22 2003 millar03_small.jpg | -rw-r--r-- 1 felixk felixk 1408 Jan 22 2003 millar04_small.jpg | -rw-r--r-- 1 felixk felixk 1361 Jan 22 2003 millar05_small.jpg | drwx-- 2 felixk felixk 4096 Sep 17 15:41 orbit-felixk | drwx-- 2 root root4096 Sep 17 05:54 orbit-root | | SNIP | | -rw--- 1 felixk felixk 4776 Sep 12 08:35 pan_edit_ANNMKc.01.bk | -rw--- 1 felixk felixk 1168 Sep 13 17:30 pan_edit_BRCYUX.01.bk | -rw-r--r-- 1 felixk felixk 1480 Jan 22 2003 trystanupstill_small.jpg | | SNIP | | drwx-- 2 felixk felixk 4096 Sep 17 15:30 v962503 | drwx-- 2 felixk felixk 4096 Sep 17 15:34 v962807o ` I suspect that there is a missing cron routine and would welcome the needed pointers in order to persuade the tmp directory to live up to its name. Felix Karpfen -- Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound problem.
On 2004-12-18, Andreas Janssen [EMAIL PROTECTED] wrote: Hello If it is a sound card and ALSA drivers are installed,. There is the problem! Regrettably, the solution is not clear to me from studying the supplied documentation. The relevant output (now produced by KDE) reads: Sound Driver: 3.8.1a-980706 (ALSA v 1.04 emulation code) Kernel Linux 2.6.8-1-386 #1 Installed drivers Type 10 ALSA emulation Card config No soundcard And the Install-CD supplied by the soundcard manufacturer is primarily designed to be used in conjunction with Windows OSs. The CD does have _one_ entry relating to Linux but this is mainly concerned with installing ALSA on kernel 2.2 and is, presumably irrelevant. The package does include the following modules.conf file - which looks promising: ,[ modules.conf ]- | alias parport_lowlevel parport_pc | alias usb-controller usb-uhci | #alias sound-slot-0 via82cxxx_audio //remark this line, |this is default audio driver | | #== added those lines = | alias char-major-116 snd | options snd snd_major=116 snd_cards_limit=1 | #--- Intel 8x0 and SiS 7012 -- | alias snd-card-0 snd-intel8x0 | options snd-intel8x0 snd_index=0 snd_id=ICH | #--- Via8233 --- | #alias snd-card-0 snd-via8233 | #options snd-via8233 snd_index=0 snd_id=Via8233 | #--- Via686A (B) --- | #alias snd-card-0 snd-via686a | #options snd-via686a snd_index=0 snd_id=Via686 | #--- | alias char-major-14 soundcore | alias sound-slot-0 snd-card-0 | alias sound-service-0-0 snd-mixer-oss | alias sound-service-0-1 snd-seq-oss | alias sound-service-0-3 snd-pcm-oss | alias sound-service-0-8 snd-seq-oss | alias sound-service-0-12 snd-pcm-oss | #= | post-install sound-slot-0 /bin/aumix-minimal | -f /etc/.aumixrc -L /dev/null 21 || : | pre-remove sound-slot-0 /bin/aumix-minimal | -f /etc/.aumixrc -S /dev/null 21 || : ` Is that all that is needed? Felix Karpfen ` Felix Karpfen Public Key 72FDF9DF (DH/DSA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
