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
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 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
I have belatedly made the change from lilo to grub carefully
converting my lilo config to grub'ese. It seems to work as
However, I have a couple of questions which I cannot track down
in any off-line source (man, info, howto's etc.) and I am not able to
trawl google or list archive with a time-limited unmetered dial-up
connection at present.
1. In lilo I always used the boot-floppy option so as not to upset
WinME. How do I do something similar in grub?
2. When the bootloader menu appeared in lilo I could interactively
overide the default runlevel (ie: boot to runlevel 3 not 5)
when necessary. How is this achieved in the grub menu?
I will accept a URL to the appropriate list archive entry or web page.
Apologies if this has been dealt with before.
** Message sent via KDE KMail v1.7.2 on SuSE Linux v8.2
** Please reply in the format that this message is sent.
What are people using for anti-virus software? I've got BitDefender
running on my machine, but I'd like to find something zero-cost that
has a nice GUI so that when I set up boxes for friends and family,
they can use it.
Regularly (and automatically) updated virus definitions are a must,