Evolution uses very small Fonts in F8
by Jonathan Ryshpan
I've just installed Fedora 8, and the fonts used in Evolution and some
other applications have become very small, about 8 pts. In the past
these fonts were controlled by gnome-font-properties, but this
application does not seem to exist in F8. I've tried
gnome-control-center->Appearance->Fonts, but changing a font here
doesn't seem to change anything, now even the fonts used by
gnome-control-center itself, which appear to be the same 8-point fonts
used in evolution. gnome-settings-daemon is running,
(/usr/libexec/gnome-settings-daemon to be exact), so this should be in
order. gconf-editor says that that Evolution uses 13 pt fonts, which it
doesn't.
Should an additional daemon be running? Or are some needed fonts
missing? I'm running KDE as my desktop, so its font control system may
have started to conflict with Gnome's.
Thanks - jon
16 years, 6 months
- 1
- 0
streaming video metrics
by Mark Haney
We have a couple of our customers (we're a non-profit ISP) that are
looking to start offering streaming/flash video from their websites.
One of their questions has been about metrics of those videos. Are
there any tools that track that specifically, or possibly any tricks to
doing it?
I'm not a streaming video newbie, but metrics are a new thing for me.
--
Recedite, plebes! Gero rem imperialem!
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
Call (866) ERC-7110 for after hours support
16 years, 6 months
- 5
- 9
Problems with NIS and automount on fedora8
by Wallace, Brooke
I'm trying to bring up a machine on our network with fedora8.
The install went well, and it was working until we tried to tie it into
NIS.
I did the prescribed edits to /etc/yp.conf, auto.master, nsswitch, etc.
But can't seem to get things working. We have many RHEL4 and RHEL5
systems working just fine. I tried makeing these files exactly the same
as those system, but still no go.
Currently the systems X11 greeter is no longer starting up (it was
initially) - now it just hangs after everything appears to come up
normally from a reboot.
Switching to single user mode...
I can ping systems on the network using IP addresses - no problem
Using hostnames w/ or w/o domain name is now finding the IP, but then
generates the following messages:
# ping hostbar.domainfoo.com
PING hostbar.domainfoo.com (172,12.34.56) 56(84) bytes of data.
do_ypcall: clnt_call: RPC: Timed out
do_ypcall: clnt_call: RPC: Timed out
64 bytes from hostbar.domainfoo.com (172.12.34.56): icmp_seq=1 ttl=254
time=0.470 ms
--- hostbar.domainfoo.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.470/0.470/0.470/0.000 ms
I saw some posts about do_ypcall ... RPC: Timed out. One mentioned the
nscd, so I started that service, others pretty much sounded like syntax
errors in config files, firewall, or bad cables.
I'm pretty sure I ruled out bad eth driver, cables, and connection since
I can ping using ip address, and I can even connect via samba, using
"user" authentication and ship files to the machine w/no problems or
delays observed.
My IT guy is hapring on the fact that its a new fedora release and may
not work on my hardware (drivers), or that another machine on the
network has got the same IP as mine using DHCP (since our routers are
losy).
So again the real issue is getting NIS to work. This is what my config
is:
/etc/yp.conf:
ypserver 172.12.34.56 # this is the correct address of our yp server
(same as other linux hosts on the network are using)
domain domainfoo.com broadcast # this is the correct domain as well
/etc/auto.master:
/mnt/pkg /etc/auto.pkg -g
/mnt/sweng /etc/auto.sweng -g
/usr2 yp:auto.home
/etc/auto.pkg:
RPM.rhel4WS_FOO -fstype=nfs
somehost.domainfoo.com:/pkg.RHEL_4/FOOpackages
/etc/auto.sweng
archives -fstype=nfs anotherhost.domainfoo.com:/opt/mnt/bar/archives
I've also added the following to the end of /etc/passwd as per
instructions from our IT docs (although current linux system do not have
this):
+::::::
I guess auto.home is on the NIS server....
One more note: I am able to see /mnt/pkg/RPM.rhel4WS_FOO w/o
problems....
Any help someone can give me, or pointers to things to try would be very
much appreciated. Unfortunately our IT guys are afraid of Linux and just
want to support Winblows and thier ancient Solaris systems.
-Brooke
16 years, 6 months
- 2
- 1
Kickstart and DHCP
by Gary Schlachter
I have a PXE boot setup trying to install FC7. After the PXE boot and
the vmlinuz and initrd.img are loaded, I am attempting to load FC7 via
NFS from kickstart. My kickstart file is loaded but when the server
attempts to acquire an IP address via DHCP before NFS mounted the drive,
it times out after multiple DHCP requests. Using ethereal, it appears
the DHCP server is responding correctly with the same IP address the PXE
server gave previously. For some currently unknown reason, the DHCP
response is ignored. Any ideas on why this would happen?
Gary
16 years, 6 months
- 2
- 1
FC7 on my lappy, F8 dvd in drive, fresh powerup
by Gene Heskett
HP-dv5120us, amd turion 64 bit cpu, gig of ram, 100 GB drive.
It gets to the bit about skipping the media test (it already passed that
several times previously on this dvd)
then I get a blue screen with the prompts across the bottom, and a
"Welcome to Fedora for 386"
across the top, and it sits there. And it does this regardless of the mode I
choose to do the install/upgrade.
Whats Next?
Thanks.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
You will be awarded a medal for disregarding safety in saving someone.
16 years, 6 months
- 4
- 12