Gmail Thunderbird Configuration
by Ali Helmy
Hey mates,
I followed the simple steps offered on the gmail help site about configuring
gmail with thunderbird
Then I enabled pop access from settings in my gmail account on the web
Now when i try to make thunderbird connect, it loads a little while then
says connection to pop.gmail.com timed out
any ideas?
--
A. Helmy
18 years, 1 month
trigger scim
by Yuandan Zhang
Hi,
I updated to FC5(fresh installation). the scim was installed too. However, I
can't trigger scim. there is link at the home dir
.xinput.d/default -> /etc/X11/xinit/xinput.d/scim
the
/etc/X11/xinit/xinput.d/scim is
XIM=SCIM
XIM_PROGRAM=scim
XIM_ARGS="-d"
GTK_IM_MODULE=scim
SCIM_QTIMM_XINPUT=/etc/X11/xinit/xinput.d/scim-qtimm
[ -r "${SCIM_QTIMM_XINPUT}" ] && . ${SCIM_QTIMM_XINPUT}
unset SCIM_QTIMM_XINPUT
# override with xim for now
QT_IM_MODULE=xim
The scim setup, ctrl+space was set to trigger scim, but there was no
response after hit ctrl + space.
if i log in, setting chinese as the system language, the trigger command is
working, but not when set English as the system language. how to fix this?
Yuandan
18 years, 1 month
FC5 Gtk fonts -- not as nice as FC4?
by Ian Pilcher
Am I the only person who thinks that the font rendering in Gtk
applications has regressed between FC4 and FC5?
--
========================================================================
Ian Pilcher i.pilcher(a)comcast.net
========================================================================
18 years, 1 month
help on installing fedora on HP compaq nx6125
by Pushparaj Shetty
Hi all,
I tried to install fedora core4 on my HP compaq nx 6125 notebook.
After boot from CD it asks for the mode of installation
(graphics/text). Then a blank screen appears without any progress.
My processor is AMD turion 64 bit. I have a free space of 15GB out of 60 GB.
Kindly help how do i solve the problem?
thanks
Pushparaj
18 years, 1 month
firefox problem
by David Pettersson
Hi,
I saved my home directory under FC3 to a DVD. Then I installed FC5 and
moved my .mozilla file on the DVD to my new home directory. When I try
to start firefox I get an error msg telling me that firefox "is already
running, but is not responding". There is no file in .mozilla to that
match *lock*. If I remove .mozilla firefox starts but then I lose my
valueable bookmarks and passwords.
Does anyone else have this problem?
I came to think of the problem with the DVD renaming files (so .mozilla
is actually _mozilla on the DVD and I had to rename it when copying it
back). Do anyone have a list of filenames from .mozilla/firefox in FC3
to send me, so I can see how to rename them back if this should be the
problem?
Thanks
David
18 years, 1 month
kmod-nvidia-1.0.8178-6.2.6.16_1.2080_FC5
by Eric Tanguy
I just installed the new 2.6.16 kernel and
xorg-x11-drv-nvidia-1.0.8178-7.lvn5
kmod-nvidia-1.0.8178-6.2.6.16_1.2080_FC5
all seems to work fine except if i try to run glxgears :
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't get an RGB, Double-buffered visual
what's the problem ?
I have to enable something manually ?
Thanks Eric
18 years, 1 month
compiling pam_mount for FC5
by Roman Maeder
I couldn't find any rpms for pam_mount-0.12.2 for FC5 and tried to compile
it myself. I didn't get very far, as the "make" output at the end shows.
The file in question is /usr/include/linux/loop.h, which belongs to
glibc-kernheaders-3.0-5.2, so this seems to be up-to-date. Any ideas?
Roman
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./../include -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -DG_DISABLE_DEPRECATED -D_LARGEFILE_SOURCE=1
-D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -D_REENTRANT -Wall -Waggregate-return
-Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wshadow
-Wstrict-prototypes -Winline -pipe -g -O2 -MT mount.lo -MD -MP
-MF .deps/mount.Tpo -c mount.c -fPIC -DPIC -o .libs/mount.o
In file included from mount.c:54:
/usr/include/linux/loop.h:31:2: error: #error "Wrong dev_t in loop.h"
mount.c:75: warning: 'struct loop_info64' declared inside parameter list
mount.c:75: warning: its scope is only this definition or declaration, which
is probably not what you want
mount.c: In function 'already_mounted':
mount.c:184: error: storage size of 'loopdev' isn't known
mount.c:184: warning: unused variable 'loopdev'
mount.c: At top level:
mount.c:944: warning: 'struct loop_info64' declared inside parameter list
mount.c:945: error: conflicting types for 'loop_bk'
mount.c:75: error: previous declaration of 'loop_bk' was here
mount.c:951:6: error: #error
-------------------------------------------------------------------
mount.c:952:6: error: #error Your userspace kernel headers
(/usr/include/linux/) are out of date
mount.c:953:6: error: #error This is NOT a pam-mount bug, but one of your
distribution.
mount.c:954:6: error: #error
-------------------------------------------------------------------
mount.c: In function 'loop_bk':
mount.c:956: error: 'LOOP_GET_STATUS64' undeclared (first use in this
function)
mount.c:956: error: (Each undeclared identifier is reported only once
mount.c:956: error: for each function it appears in.)
mount.c:961: error: dereferencing pointer to incomplete type
make[2]: *** [mount.lo] Error 1
make[2]: Leaving directory `/usr/local/src/pam_mount-0.12.2/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/pam_mount-0.12.2'
make: *** [all] Error 2
18 years, 1 month
Software Raid 5 (FC5)
by Mark Yarbrough
During install time I was made 10 raid partitions across 5 500GB SATA
drives. The final partition /dev/md8 wouldn't partition format and anaconda
would crash telling me that the partition couldn't be formatted, and
required a reboot. After the 3rd attempt I figured that the partitions are
all the same size so I will just format it when I am in the running
operating system.
I took a look at my partitions using fdisk (take note that all 5 are the
same save the drive number it self) <see paste at bottom>
The partitions are there. /dev/sdX11 is the partition that I am trying to
use. I tried to make the raid partitions to no avail. I looked at
/etc/mdadm.conf and saw that /dev/md8 is there. From my limited
understanding I am under the assumption that the raid is made and all I need
to do is format it. I try to format it and I get the error reporting the
device size to be zero. The partitions are clearly not zero. I am now
stuck. What should I do next?
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 28683 230396166 fd Linux raid
autodetect
/dev/sda2 28684 38882 81923467+ fd Linux raid
autodetect
/dev/sda3 38883 41432 20482875 fd Linux raid
autodetect
/dev/sda4 41433 60801 155581492+ 5 Extended
/dev/sda5 41433 43344 15358108+ fd Linux raid
autodetect
/dev/sda6 43345 45256 15358108+ fd Linux raid
autodetect
/dev/sda7 45257 46658 11261533+ fd Linux raid
autodetect
/dev/sda8 46659 47933 10241406 fd Linux raid
autodetect
/dev/sda9 47934 49208 10241406 fd Linux raid
autodetect
/dev/sda10 49209 49845 5116671 fd Linux raid
autodetect
/dev/sda11 49846 60796 87963876 fd Linux raid
autodetect
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 28683 230396166 fd Linux raid
autodetect
/dev/sdb2 28684 38882 81923467+ fd Linux raid
autodetect
/dev/sdb3 38883 41432 20482875 fd Linux raid
autodetect
/dev/sdb4 41433 60801 155581492+ 5 Extended
/dev/sdb5 41433 43344 15358108+ fd Linux raid
autodetect
/dev/sdb6 43345 45256 15358108+ fd Linux raid
autodetect
/dev/sdb7 45257 46658 11261533+ fd Linux raid
autodetect
/dev/sdb8 46659 47933 10241406 fd Linux raid
autodetect
/dev/sdb9 47934 49208 10241406 fd Linux raid
autodetect
/dev/sdb10 49209 49845 5116671 fd Linux raid
autodetect
/dev/sdb11 49846 60796 87963876 fd Linux raid
autodetect
Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 28683 230396166 fd Linux raid
autodetect
/dev/sdc2 28684 38882 81923467+ fd Linux raid
autodetect
/dev/sdc3 38883 41432 20482875 fd Linux raid
autodetect
/dev/sdc4 41433 60801 155581492+ 5 Extended
/dev/sdc5 41433 43344 15358108+ fd Linux raid
autodetect
/dev/sdc6 43345 45256 15358108+ fd Linux raid
autodetect
/dev/sdc7 45257 46658 11261533+ fd Linux raid
autodetect
/dev/sdc8 46659 47933 10241406 fd Linux raid
autodetect
/dev/sdc9 47934 49208 10241406 fd Linux raid
autodetect
/dev/sdc10 49209 49845 5116671 fd Linux raid
autodetect
/dev/sdc11 49846 60796 87963876 fd Linux raid
autodetect
Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 28683 230396166 fd Linux raid
autodetect
/dev/sdd2 28684 38882 81923467+ fd Linux raid
autodetect
/dev/sdd3 38883 41432 20482875 fd Linux raid
autodetect
/dev/sdd4 41433 60801 155581492+ 5 Extended
/dev/sdd5 41433 43344 15358108+ fd Linux raid
autodetect
/dev/sdd6 43345 45256 15358108+ fd Linux raid
autodetect
/dev/sdd7 45257 46658 11261533+ fd Linux raid
autodetect
/dev/sdd8 46659 47933 10241406 fd Linux raid
autodetect
/dev/sdd9 47934 49208 10241406 fd Linux raid
autodetect
/dev/sdd10 49209 49845 5116671 fd Linux raid
autodetect
/dev/sdd11 49846 60796 87963876 fd Linux raid
autodetect
Disk /dev/sde: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sde1 * 1 28683 230396166 fd Linux raid
autodetect
/dev/sde2 28684 38882 81923467+ fd Linux raid
autodetect
/dev/sde3 38883 41432 20482875 fd Linux raid
autodetect
/dev/sde4 41433 60801 155581492+ 5 Extended
/dev/sde5 41433 43344 15358108+ fd Linux raid
autodetect
/dev/sde6 43345 45256 15358108+ fd Linux raid
autodetect
/dev/sde7 45257 46658 11261533+ fd Linux raid
autodetect
/dev/sde8 46659 47933 10241406 fd Linux raid
autodetect
/dev/sde9 47934 49208 10241406 fd Linux raid
autodetect
/dev/sde10 49209 49845 5116671 fd Linux raid
autodetect
/dev/sde11 49846 60796 87963876 fd Linux raid
autodetect
# mdadm.conf written out by anaconda
DEVICE partitions
MAILADDR root
ARRAY /dev/md8 level=raid5 num-devices=5
uuid=fc489661:c7e54273:f9a60c82:fb747b29
ARRAY /dev/md6 level=raid5 num-devices=5
uuid=eac1a77f:5278bfcd:4ae75c92:7ecde09b
ARRAY /dev/md3 level=raid5 num-devices=5
uuid=1e94cb1d:f84f5a3b:1e0ff333:408d5bb7
ARRAY /dev/md5 level=raid5 num-devices=5
uuid=f5bfaf8b:8a591cf0:d73b7d31:4c07a93b
ARRAY /dev/md1 level=raid5 num-devices=5
uuid=0bf1a445:323d5326:5a7a92fc:1c346c33
ARRAY /dev/md9 level=raid5 num-devices=5
uuid=f5811eae:cfb21182:41881dcf:739f1bad
ARRAY /dev/md4 level=raid5 num-devices=5
uuid=348c95b9:df7feee6:41713309:a9324496
ARRAY /dev/md0 level=raid5 num-devices=5
uuid=bf7ef721:318d6d4e:b626b349:5f9c7e15
ARRAY /dev/md7 level=raid5 num-devices=5
uuid=a196ca52:c6700579:ff5a0379:9d6c9084
ARRAY /dev/md2 level=raid5 num-devices=5
uuid=5e0d3003:e65e36d0:25158ed3:f81e126d
18 years, 1 month
FC5 RAID 1 - booting off either drive
by Laurence Vanek
Greetings -
To my surprise, fresh install of FC5 with RAID 1 configured at install
time went without a hitch. I have /dev/md0 defined on /boot
partitions. It boots fine with this setup.
I had my FC4 system setup this exact way except I found that I had to
manually install grub on one of the disks to permit booting off either
one if the other is down.
Does anyone know of a way to check for the presence of grub on each
drive (obviously its on hda since it boots presently) to see if this
needs to be done for FC5 also without powering down each drive in turn &
attempting to boot?
18 years, 1 month
