Since posting via gmane seems not to have propagated through to the
main list I am sending this separately:
Anne Wilson <cannewilson <at> googlemail.com> writes:
> Maybe they can't. Some problems can't be fixed until we get 4.1. On the
> whole, though, I agree with you. It took a little getting used to, but I do
> like it. I'll put up with its shortcomings while it is 4.0. 4.1 is only a
> few weeks away.
This has been one of those threads that last and last - and it seems to me
that occasionally frustration with an issue builds up and eventually we
get these everlasting complaints sessions.
I think everyone would probably agree that KDE4 is not perfect at present
but I feel we should accept the real experts' view that underlying this new
desktop is a concept that will eventually not just supercede the old KDE (3.5)
but will eventually yield a lovely desktop that we will get to love
when it is polished and optimised - but it will take a little time.
If you have ever done any programming yourself you will know that getting
optimised bug free code first time round almost never happens barring a
miracle - so let's give the devs a break and allow them a bit of time without
too much heckling! A little praise might no go amiss at times either!
I accept that a calculated risk was taken in including KDE as 4.0.3 in F9
but I also accept their judgement and we may well be seeing strong praise
rather than condemnation in F10's lifetime when we reach 4.1+ or 4.2.
As has been said a number of times - you can always stay with F8 for the
moment until KDE4 has 4.1 out the door and that will be in a month or so.
That will still be some months before F10 release by which time KDE4 should
hopefully be a really nice desktop.
I am filing bugs in BZ when I find issues and all of us who are using KDE4
should contribute to its development by doing this. Certainly I have found
that the few people who get changes implemented are generally very responsive
and do a great job in either amending things for Fedora or represent Fedora
Most of the complainers do not directly fix things - so we all perhaps need
a little patience and do our bit to help rather than simply grumble.
i am currently using f8 with most of updates install. not sure if ifup/ifdown
is among them.
i have a growing concern about operation of ifup and ifdown.
i am noticing that when i 'ifdown eth0' is still see flashing of ethernet led
on a 2wire 2701hg-b dsl modem.
it was my understanding that using ifup and ifdown that this 2 commands would
bring ethernet connection up and down, but ethernet led on modem is now making
me believe other wise.
just what do commands actually do?
as 'user' what is/are better command or commands to use without 'su' or 'sudo'
to connect ethernet to modem?
in a free world without fences, who needs gates.
I'm trying to install F9 on a machine that doesn't have a DVD drive. I
burned the boot.iso and boot from that.
I mount the install DVD on another machine and NFS export it. I can
mount the exported directory on another machine (and even that machine
booted with its current F7).
I boot for the boot ISO and select NFS install. I assign the IPv4
address, netmask, gateway, and nameserver as they are defined for other
machines on the LAN and specify the IP address and directory of the NFS
serving machine. IPv6 is disabled.
But the installer is always unable to mount the NFS volume.
Is there something I'm missing?
Clemson University Math Sciences
mjs AT clemson DOT edu
I am having newbie problems with boinc, ports and SELinux -- I think.
Networks and SELinux are two subjects I have put off learning to any
rudimentary depth. So here goes.
I can get Boinc to connect to the World Community Grid immediately after
first download and install. (I have removed it and re-installed to test
this). But after a reboot I can no longer connect to any of the project
I went to the WCG forum and explained my problem. The response was --
open ports 80 and 443.
'netstat' does not list 80 or 443 as present, i.e, as active.
SELinux is in permissible mode.
SELinux gives the following for those two ports.
http_port_t tcp s0 80
http_port_t tcp s0 443
So ... where do I go from here?
Fedora 9, Gnome 2.22.2
Evo.2.22.2, Emacs 22.2.1
I've been running several F8 and F9 machines behind a KVM switch
against what seemed the current high-end monitor in local stores. (My old
LCD, which was 1280x1024, died suddenly.)
The first weirdness, of several, is that my three PCs all handled
it well enough to be usable under F8, albeit not optimally -- they try
variously to treat the display or the hardware, or both, as anything from
1280x1024 to 1680x1050 (which is what it is), and often fail when they're
This is the case even though I do my upgrades, and especially
installs, with the subject machine out from behind the KVM switch,
connected directly (and alone, of course) to the peripherals, so that it
can do any necessary negotiating with them, unimpeded by the KVM switch.
(In the past, that has sufficed. Once they're configured, they
can be put behind the switch again.)
One machine actually shows *almost* the model number (w2207,
without the h) -- but that's not in the list of all monitors that Fedora
Is there some secret driver somewhere that I should be getting?
One reason I bought this on is that HP is supposed to be linux-
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Remember I know precious little of what I am talking about.
I re-installed Fedora 8 and now I can get a reverse ssh tunnel (from
server to home) by typing on the server:
> ssh -R 2022:server.ip:22 home(a)home.ip
Then when at the home computer, I type:
> ssh -p 2022 server@localhost
This works fine. The only problem is the connection always times out
even though I've changed the sshd_config files on both machines to keep
it alive. I've restarted the sshd daemon also. Not sure why the
connection keeps closing.
My wife is currently visiting her family in Mauritius, and has taken her laptop
along with her. Her laptop runs Fedora 8 and I have set up network manager on
it so it will automatically grab any available Internet connection without any
further action required on her part. This works fine here, both with a
wireless and a wired connection. Switch on, blammo! Connection established,
However, she advises me that the connection at her mother's house uses a Sagem
Fast 800 E3 modem that has only a usb connection, and when she plugs it into a
usb port on her laptop nothing happens. (On the actual modem, the word Fast is
written as F@st.)
A bit of Google searching tells me that this modem is based on the Eagle
chipset (whatever that is) and that there are apparently Linux drivers available
for this thing, somewhere. Making things more interesting, it appears that
this Sagem is a French outfit, and most of the documentation that I can find is
written in French.
Is there an easy way to make this modem work with Fedora 8? My wife is by no
means a "techie"; she just uses whatever software I provide for her, and there
is no way in the world that she will be able to compile a kernel module on her
own, or anything like that.
"yum search sagem" gives me no results, and "yum search eagle" gives me nothing
relevant. I'm pretty sure I could call her on the phone and talk her through a
"yum install whatever" and reboot, but I have no idea what I should tell her to
I hate to have to tell her that she hauled her laptop all the way from here to
Mauritius for nothing, but I'm starting to think that's the situation.
Any suggestions are welcome.
MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com
i am having a system with the linux fedora core installed in it. could
anyone tell about the free keyloggers used in the linux fedora core systems
and the proper installtion of the same, so that all the keystrokes can be
viewed with all the details.