Reading some mails on the GIMP mail list, I ran across the procedure
to install some more fonts for not only Gimp, but the system and
StarOffice to use also. Well, I installed the fonts, went to the
shell and issued the command xset fp+ <font directory> and then the
rehash command and all fonts are there! Ok, that went well, but each
time I restart the system, I have to do it all over again? Is there
a way to make it permanent and read the new fonts like it does the
ones the system installs or is that a no-no?
end of line
xset fp+ <new font directory>
xset fp rehash
---KMail 1.2--- SuSE Linux v7.2---
Registered Linux User #225206
/tracerb(a)sprintmail.com/ *Magic Page Products*
*Team Amiga* http://home.sprintmail.com/~tracerb
-----BEGIN PGP SIGNED MESSAGE-----
I'm having a problem with some mails handled by one particular rule in
procmail - all the rest are being handled ok. The .procmailrc goes like
* ^Received: from correo.foo.es
* ^Received: from (ruebert.ieee.org|engine.ieee.org|hormel3.ieee.org|boldfish.ieee.org|aries3.…)
The problem is that mail matching the "^Received" clause above goes to the
"/var/spool/mail/cer" folder instead of the "$HOME/Mail/in_foo" that
corresponds. The log is this, showing a write error:
procmail: No match on "^List-Id: <husky-discuss.lists.sourceforge.net>"
procmail: Executing "/usr/bin/spamc"
procmail: No match on "^X-Spam-Status: Yes"
procmail: No match on "^^rom[ ]"
procmail: No match on "^From.*FETCHMAIL-DAEMON(a)nimrodel.valinor"
procmail: No match on "^To.*virusalert(a)nimrodel.valinor"
procmail: No match on "^From.*(MAILER-DAEMON|postmaster)(a)nimrodel.valinor"
procmail: Match on "^Received: from correo.foo.es"
procmail: No match on "^Received: from (ruebert.ieee.org|engine.ieee.org|hormel3.ieee.org|boldfish.ieee.org|aries3.…)"
procmail: No match on "(^(Mailing-List:|Precedence:.*(junk|bulk|list)|To: Multiple recipients of |(((Resent-)?(From|Sender)|X-Envelope-From):|>?From )([^>]*[^(.%@a-z0-9])?(Post(ma?(st(e?r)?|n)|office)|(send)?Mail(er)?|daemon|m(mdf|ajordomo)|n?uucp|LIST(SERV|proc)|NETSERV|o(wner|ps)|r(e(quest|sponse)|oot)|b(ounce|bs\.smtp)|echo|mirror|s(erv(ices?|er)|mtp(error)?|ystem)|A(dmin(istrator)?|MMGR|utoanswer))(([^).!:a-z0-9][-_a-z0-9]*)?[%@> ][^<)]*(\(.*\).*)?)?$([^>]|$)))"
procmail: Assigning "LASTFOLDER=/home/cer/Mail/in_foo"
procmail: Opening "/home/cer/Mail/in_foo"
procmail: Acquiring kernel-lock
So far, normal.
procmail: Error while writing to "/home/cer/Mail/in_foo"
procmail: Truncated file to former size
A write error. What write error?
procmail: No match on "^Received: from pop.tiscali.es"
procmail: Extraneous locallockfile ignored
procmail: Bypassed locking "/var/spool/mail/cer.lock"
procmail: Assigning "LASTFOLDER=/var/spool/mail/cer"
procmail: Opening "/var/spool/mail/cer"
procmail: Acquiring kernel-lock
procmail: Notified comsat: "cer@0:/var/spool/mail/cer"
>From sombody(a)somewhere.com Wed Aug 31 20:17:13 2005
Folder: /var/spool/mail/cer 952289
I have copied over the emails in /home/cer/Mail/in_foo to another folder,
then deleted, recreated in_foo, and finally copied back all the emails.
The folder has 57Mb (392 emails) and Pine seems happy with it, no
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76
-----END PGP SIGNATURE-----
I don't remember seeing this problem on the list.
KMail print on screen is clear and most letters are
separated. When I print out a mail, some letters,
particularly the "t", the "si" and the "sk" combinations
are scrunched together with adjoining letters.
I am printing to an HP 2200D laserjet. The
typeface on screen (and on paper) is a
sans-serif font. Even on screen, it is slightly
scrunched in spots. "ri" and "ti" and "tt" and "th" are
too close together.
I have been trying to get a tarball of transcode to compile on my SUSE
9.2 system. Every pkg I have d/l'd from the sites listed on the
Transcode Wiki page:
are unopenable. Every one, including the beta versions. Have I made one
of those embarrassing newby errors? Konqi Filemgr says :
"The file does not exist" even tho it lists it.
Is there a location for a transcode I can open and compile?
p.s. The pkgs are unopenable on my SUSE 8.2 sys also
Proud SUSE user since 5.2
Loving SUSE 9.2
My BLOG == http://vancampen.org/blog
While attempting to stop a video playing on Macro Media Flash Player 7,
I managed to lock out everything. I could not move the mouse cursor,
the arrow keys and the rest of the kb didn't work, ctl-alt-del did nothing.
None of the function keys did anything. (The video was something downloaded
from the 'net via Firefox.) I wound up pulling the big switch, as us hams
like to say. Is there anything else I could have done?
I'm trying to put Linux to practical use, and this is the first time I've seen
10.0 crash, so it's good, but not fool-proof. (If something can be broken,
this fool will break it!)
good idea - please see here:
Hope this is detailed enough...
BTW, thats my first wiki entry ever...
Am Sonntag, 24. April 2005 22:36 schrieb Richard Bos:
> Op zondag 24 april 2005 23:36, schreef Sven Haberer:
> > If desired, I could post a short description how I did this...
> If you can put it own the wiki (http://www.susewiki.org): than we can all
> maintain it.
> Richard Bos
> Without a home the journey is endless
I wonder if anyone has any experience of getting the wireless eth-card in
a Dell Latitude D600 to work for SuSE 9.2? The card is an Intel
PRO/Wireless 2200BG. It is recognised by the system as such, and I am able
to configure it in Yast without any obvious problems. However, it doesn't
get an IP-address. This is in contrast with the same laptop in the same
location booting the XP partition, in which case it finds the network,
gets an IP and chats away happily. The setup is the same for SuSE and XP:
DHCP, named ssid, WEP-ASCII-5char encryption.
The following may be relevant version numbers
During boot I get the following messages (some of which sound a bit
omnious, but I am not certain how serious they are) that I interpret as
related to the problem
<4>ieee80211_crypt: unsupported module, tainting kernel. ("tainting is
<7>ieee80211_crypt: registered algorithm 'NULL'
<4>ieee80211: unsupported module, tainting kernel.
<4>ipw2200: unsupported module, tainting kernel.
<6>ipw2200: Intel(R) PRO/Wireless 2200 Network Driver, 0.8
<6>ipw2200: Copyright(c) 2003-2004 Intel Corporation
<6>eth1: Setting MAC to 00:0e:35:ad:e3:81
and the later on when trying to connect
eth1 device: Intel Corp. PRO/Wireless 2200BG (rev 05)
eth1 configuration: wlan-id-00:0e:35:ad:e3:81
ERROR: command 'iwconfig eth1 mode Managed' returned
Error for wireless request "Set Mode" (8B06) :
SET failed on device eth1 ; Operation not supported.
eth1 (DHCP) . . . . . no IP address yet... backgrounding.
If anyone recognise the problem and has a solution to it I would be for
Please also be gentle with me if/when replying. I am a bit of a beginner
and don't handle jargon very well.
I have a 4-year old DELL desktop with a heavy CRT monitor that I'm going
to give away soon .
I also have a 2 month old laptop. Both computers run Linux/SuSE.
I would like to buy an external disk to save most of my s/w
development now residing on my old desktop.
But I would like to be able to use it also with my laptop.
Both computers have some USB ports so I daresay an external USB disk
would be fine ..
I'd appreciate some suggestion about a USB reliable, large capacity but
portable, external disk or
any alternative solution.
Thank you in advance.
I have a fileserver running SuSE 8.0 with 2 IDE Drives and a
SCSI RAID (RAID5). The system boots up to one of the IDE drives,
and the SCSI RAID drive runs as a mounted filesystem (/dev/md0).
(all filesystems are REISERFS).
The SCSI RAID drive has crashed (won't boot up), and I need to
recover it (repair it, through some utility).
The software does not seem to want to mount the disks, even though
the SCSI BIOS (Adaptec) recognizes the disks, and they are listed as
I tried to repair the disk(s) (with reiserfsck), but it produced an
reiserfs_open: bread failed reading block 2
reiserfs_open: bread failed reading block 16
reiserfs_open: neither new nor old reiserfs form found on /dev/md0
The literature suggested that this error message is hardware related
(either a disk is physically damaged, or maybe the RAID isn't
recognized), but again, the disks are recognized (and therefore,
so is the SCSI Card).
I tried to boot up with SuSE CD 1 in Recovery mode, but not sure
what to do there (i.e., after the root prompt - just run reiserfsck?).
Literature suggests there are plenty of tools to handle disk recovery,
and especially RAID support, I can't find reference to them
The installation of the RAID was trivial (using the YAST2
partitioning GUI window on startup), and yet recovery seems to be a
mystery. This can't be right.
Does anyone know where there are "decent" and "usable" recovery tools?
OR ... does anyone know what "specifically" to do in this case? Can
I re-partition without formatting, and recover the existing data?
Any help is appreciated - I'm sure I'm missing something "obvious", but
can't find "obviously" what to do in the literature, docs, etc.
School of Engineering and Applied Science
University of California, Los Angeles