10:53 a.m.
Hi every
What is the matter with fedora 9?
it introduced a NetworkManager which prohibits networking.
programs are acessible only as root user: xsane just does nothing as
non-root user.
openoffice blocks its drop-downs in the main menu for 20 seconds, if you
are not root. if you are root, everything is as good/as bad as with
fedora 8, thanks very much.
openldap breaks down every now and then, and stays with a corrupt
sleepycat database, which is not revoverable.
could the relevant persons please provide an update to fedora 9 as soon
as possible? thanks very much.
very angry
suomi
1:34 p.m.
Craig White wrote:
First of all, Tom didn't qualify his comments on NetworkManager
which is
very useful in some instances and apparently is installed as the default
networking daemon if you install from Live CD. His suggestion to turn it
off:
- lacked any suggestion that you need to turn on the regular 'network'
daemon in its place instead
Did you read the post you copied? He suggested that you turn
NetworkMangler off, and the traditional (functional) network daemon in
the very next line! It's the line between the disabling of NM and the
line that says "reboot" if you are having problems finding it.
- lacked any consideration of wireless or dhcpcd client needs
Which work as they did in FC8 (and all the way back to FC4).
With respect your your efforts making Fedora 9 work to your
expectations, you've sort of proven your own problems to yourself but
contributed nothing to fixing any issues that may exist.
He provided a three line fix for the NM problem, while I knew that
already I'm sure some people didn't.
One of the
great things about this list is that if you can figure out how to ask
the questions, you can get your problems solved.
Craig
On Wed, 2008-06-25 at 07:02 +0800, Robert M. Bernabe wrote:
> newbie here... trying to make linux work as a gui interface with
> postgresql... found fc9 unworkable too as compared to fc8....our own opinion
> is that fc9 has implemented some features we don't understand. e.eg. off the
> bat, after installation...the samba services status appear unknown in the
> services window...I think so do other services (somebody posted a reason for
> it I think... but it involves several 'classic' prompt windows edits...) so
> for now we are sticking to fc8...thankful for all the efforts plugged into
> the fedora project in general... but just wishing we understood the thinking
> behind the changes in fc9...
>
>
>
> ----- Original Message -----
> From: "Tom Horsley" <tom.horsley(a)att.net>
> To: <fedora-list(a)redhat.com>
> Sent: Wednesday, June 25, 2008 5:37 AM
> Subject: Re: What is the matter with fedora 9?
>
>
>> On Tue, 24 Jun 2008 17:53:37 +0200
>> fedora <fedora(a)ayni.com> wrote:
>>
>>> it introduced a NetworkManager which prohibits networking.
>> Don't know about the other problems, but for me this makes
>> networking function just like always:
>>
>> chkconfig --level 2345 NetworkManager off
>> chkconfig --level 2345 network on
>> reboot
>>
>> That turns off NetworkManager and goes back to the old nasty
>> stick-in-the-mud networking that actually works :-).
>>
>> NetworkManager may be good for folks with laptops who flit
>> about from one hotspot to another, but it is hopeless for
>> us more ordinary network users who have static IPs or even
>> DHCP networks initialized at boot time and unchanging after
>> that. It should never have arbitrarily been made the default.
>>
>> --
>> fedora-list mailing list
>> fedora-list(a)redhat.com
>> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
4:40 a.m.
2008/6/27 Andrew Kelly <akelly(a)corisweb.org>:
> And they are nothing at all like the [whatever the opposite of flat
> earth folks are] who think things like NetworkManager and PulseAudio are
> the holy grail because there are circumstances where these are valuable
> tools in spite of the huge volume of other, more common, circumstances
> where they are in fact less useful than hammered dung. And why must the
> not-flat-earth-folks then disparage the flat-earth-folks for pointing
> out exactly this fact?
There is absolutely nothing wrong with NetworkManager. Circumstances
where it appears not to have worked are always due to your wilful
negligence or fevered delusions. In fact, its divine perfection is so
great that it would be sullied by condescending to provide meaningful
documentation or diagnostics.
--
imalone
4:11 a.m.
On Mon, 2008-06-30 at 10:49 +0200, Tomasz Torcz wrote:
Dnia 2008-06-27, pią o godzinie 13:52 +0100, Timothy Murphy pisze:
> Mikkel L. Ellertson wrote:
>
> > One problem for a lot of people is that NM does not open the network
> > connection until the user logs in. This is a problem for anything
> > that needs a network connection before you log in.
>
> I agree.
> What is the rationale behind this decision?
Weren't new GDM meant to solve this issue?
It can't resolve this issue,
when it isn't running.
It was said to allow
running userspace daemons (like gnome-power-manager and nm-applet)
on login screen.
These suffer from the same design flaw: They presume a running
desktop.
Ralf
3:49 a.m.
Dnia 2008-06-27, pią o godzinie 13:52 +0100, Timothy Murphy pisze:
Mikkel L. Ellertson wrote:
> One problem for a lot of people is that NM does not open the network
> connection until the user logs in. This is a problem for anything
> that needs a network connection before you log in.
I agree.
What is the rationale behind this decision?
Weren't new GDM meant to solve this issue? It was said to allow
running userspace daemons (like gnome-power-manager and nm-applet)
on login screen.
--
Tomasz Torcz
6:38 a.m.
On Fri, 2008-06-27 at 14:13 -0400, max bianco wrote:
It already does everything, its never given me a problem. Wired or
wireless take your pick. Of course when I decide to buy a piece of
hardware, I generally avoid the cheap crap
I can't say that I've had a hardware problem with it, but just that it's
not that good at working with a system. Linux is full of services,
services that need a functioning network, services that don't work well
if the network is down or starts up too late. Network Manager doesn't
start up early enough.
If one network card is 20 bucks cheaper than the other and they do
the
same thing, there is a good reason, cheaper usually means "We cut more
corners".
Not always. Some things are cheap because they have captured the mass
market, and have sales numbers in their favour.
The big problem is built in hardware that can't be avoided, and systems
where you can't easily add to (e.g. laptops).
--
[tim@localhost ~]$ uname -r
2.6.25.6-55.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
1:13 p.m.
On Fri, Jun 27, 2008 at 11:08 AM, Tim <ignored_mailbox(a)yahoo.com.au> wrote:
On Fri, 2008-06-27 at 13:52 +0100, Timothy Murphy wrote:
> Incidentally, is there such a thing as NetworkManagerDispatcher now?
Apparently not. It would seem that NetworkManager does it all, rather
than have a separate service for scripts. Just wait, soon it will do
everything... :-\
It already does everything, its never given me a problem. Wired or
wireless take your pick. Of course when I decide to buy a piece of
hardware, I generally avoid the cheap crap because the cheap crap
usually costs me time which equals money. It may not be true in all
cases but I know people that consistently buy the cheapest hardware
they can find and consistently have problems. All hardware is not
created equal. If one network card is 20 bucks cheaper than the other
and they do the same thing, there is a good reason, cheaper usually
means "We cut more corners".
--
If opinions were really like assholes we'd each have just one
10:08 a.m.
On Fri, 2008-06-27 at 13:52 +0100, Timothy Murphy wrote:
Incidentally, is there such a thing as NetworkManagerDispatcher now?
Apparently not. It would seem that NetworkManager does it all, rather
than have a separate service for scripts. Just wait, soon it will do
everything... :-\
--
[tim@localhost ~]$ uname -r
2.6.25.6-55.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
7:52 a.m.
Mikkel L. Ellertson wrote:
One problem for a lot of people is that NM does not open the network
connection until the user logs in. This is a problem for anything
that needs a network connection before you log in.
I agree.
What is the rationale behind this decision?
It seems very strange.
I've found scripts in /etc/NetworkManager/dispatcher.d/ very useful
for counteracting this "feature", eg starting NFS mounts over WiFi.
Incidentally, is there such a thing as NetworkManagerDispatcher now?
It is mentioned in the ridiculously short NM man page.
Which does not mention any files in the home directory
that are written or read by NM;
I assume there must be some since NM waits until login to start?
3:52 a.m.
On Thu, 2008-06-26 at 14:00 -0700, Craig White wrote:
<snip>
The thing I love about flat earth folks who disparage things like
NetworkManager and PulseAudio is that they are consistently blind to the
fact that there are circumstances where these are valuable tools.
Craig
Indeed.
Yes.
And they are nothing at all like the [whatever the opposite of flat
earth folks are] who think things like NetworkManager and PulseAudio are
the holy grail because there are circumstances where these are valuable
tools in spite of the huge volume of other, more common, circumstances
where they are in fact less useful than hammered dung. And why must the
not-flat-earth-folks then disparage the flat-earth-folks for pointing
out exactly this fact?
I can use a nine pound brick to get into my locked car. In the right
circumstances I'd even call it a valuable tool and count myself blessed
for having had it available to me. But for the most part, there are more
desirable and functional ways of getting into my locked car, and I'm
happy to make them my first choice. Yes even when the nine pound brick
seems to be on sale at every corner grocery, and/or given to me in lieu
of keys when I buy my next car.
You know (and this is probably just me venting some workplace
frustrations, so forgive me), you don't often hear people bitching about
stuff that works. Especially when it works as expected, without any kind
of intervention.
Andy
4 p.m.
On Thu, 2008-06-26 at 14:34 -0400, Bill Davidsen wrote:
Craig White wrote:
> First of all, Tom didn't qualify his comments on NetworkManager which is
> very useful in some instances and apparently is installed as the default
> networking daemon if you install from Live CD. His suggestion to turn it
> off:
> - lacked any suggestion that you need to turn on the regular 'network'
> daemon in its place instead
Did you read the post you copied? He suggested that you turn
NetworkMangler off, and the traditional (functional) network daemon in
the very next line! It's the line between the disabling of NM and the
line that says "reboot" if you are having problems finding it.
----
I missed that - thanks - appreciate the sarcasm too.
----
> - lacked any consideration of wireless or dhcpcd client needs
Which work as they did in FC8 (and all the way back to FC4).
----
actually, NM is pretty much the same in F8/F9. Clearly someone with a
laptop would rather use NM.
I think the issue you see is users who install from Live CD because the
installer will active Network Manager by default based on assumptions
made by the installer.
----
> With respect your your efforts making Fedora 9 work to your
> expectations, you've sort of proven your own problems to yourself but
> contributed nothing to fixing any issues that may exist.
He provided a three line fix for the NM problem, while I knew that
already I'm sure some people didn't.
----
The thing I love about flat earth folks who disparage things like
NetworkManager and PulseAudio is that they are consistently blind to the
fact that there are circumstances where these are valuable tools.
Craig
3:34 p.m.
On Thu, 2008-06-26 at 14:46 -0400, Bill Davidsen wrote:
fedora wrote:
> Hi every
>
> What is the matter with fedora 9?
>
> it introduced a NetworkManager which prohibits networking.
NetworkMangler has been around since FC6 (at least), by making it the
default it became impossible to ignore. It does the right thing in cases
where you have one hardwire or wireless connection which can see only
one AP. For all other cases wait for the human readable documentation
which will be here... or maybe not, since it was coming with FC7, 8, and 9.
The
above is clearly not true, I use NM in environments where there are
3 or 4 APs to choose from.
> programs are acessible only as root user: xsane just does nothing as
> non-root user.
More likely to be a device permission problem, in my experience. Blame
hal or SElinux, it's not that hard to fix.
> openoffice blocks its drop-downs in the main menu for 20 seconds, if you
> are not root. if you are root, everything is as good/as bad as with
> fedora 8, thanks very much.
Other people have said that's because when they upgraded they left stuff
in various "dot" directories. Doesn't happen in clean installs, at least
that I've noticed.
> openldap breaks down every now and then, and stays with a corrupt
> sleepycat database, which is not revoverable.
I didn't see your bugzilla on that.
>
> could the relevant persons please provide an update to fedora 9 as soon
> as possible? thanks very much.
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
=======================================================================
Your own qualities will help prevent your advancement in the world.
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam(a)sbcglobal.net
2:23 p.m.
Stephen Berg (Contractor) wrote:
Bill Davidsen wrote:
After about a dozen installs of Fedora 9 I cannot agree with you on
that. On every system save one there is only one network connection, in
each of those cases it's been /dev/eth0 and NM would not enable the
connection by default.
Maybe there's documentation on the way that will make NM a breeze to
configure but until that time it's out the window. I disable the
NetworkManager service and enable the network service during kickstart
installs. All my systems have a statically leased DHCP address and it
works just fine.
Bottom line for me: NM breaks far more than it fixes.
One problem for a lot of people is that NM does not open the network
connection until the user logs in. This is a problem for anything
that needs a network connection before you log in.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
2:18 p.m.
New subject: What is the matter with fedora 9? ... Network Manager rocks !
Stephen Berg (Contractor) wrote:
>>
>> it introduced a NetworkManager which prohibits networking.
>
> NetworkMangler has been around since FC6 (at least), by making it the
> default it became impossible to ignore. It does the right thing in
> cases where you have one hardwire or wireless connection which can see
> only one AP. For all other cases wait for the human readable
> documentation which will be here... or maybe not, since it was coming
> with FC7, 8, and 9.
>
After about a dozen installs of Fedora 9 I cannot agree with you on
that. On every system save one there is only one network connection, in
each of those cases it's been /dev/eth0 and NM would not enable the
connection by default.
Maybe there's documentation on the way that will make NM a breeze to
configure but until that time it's out the window. I disable the
NetworkManager service and enable the network service during kickstart
installs. All my systems have a statically leased DHCP address and it
works just fine.
Bottom line for me: NM breaks far more than it fixes.
My NM esperience is instead absolutely positive. I have tryed it since
F7, but at that time I was very disappointed and turned it off, as in
F8. In F9 I just wanted to give last chance and NM won.
I have a very standard hardware: Realtek RTL-8139 (wired) and Intel
2200BG (wireless), perhaps this is a key ingredient.
It connects virtually to everything: I tested it over wireless
connections (free, wep, wpa, wpa2), and wired ones, sometimes PPP over a
modem. Some connections require manual IP settings, that I have
configured in NM by editing the connections: all of them work flawlessly.
I have noticed only a bug (due to wpa_supplicant, namely): while
connecting to a wireless network with a hidden essid, sometimes the
connection attempts fail and I have to restart NM service in order to
get a successful connection. After the wpa_supplicant today update, that
problem is fixed and NM is a charm.
The only criticism is about the documentation: is very lacking at this
stage.
My 2 cents.
Andrea
2:16 p.m.
Stephen Berg (Contractor) wrote:
Bill Davidsen wrote:
> fedora wrote:
>> Hi every
>>
>> What is the matter with fedora 9?
>>
>> it introduced a NetworkManager which prohibits networking.
>
> NetworkMangler has been around since FC6 (at least), by making it the
> default it became impossible to ignore. It does the right thing in
> cases where you have one hardwire or wireless connection which can
> see only one AP. For all other cases wait for the human readable
> documentation which will be here... or maybe not, since it was coming
> with FC7, 8, and 9.
>
After about a dozen installs of Fedora 9 I cannot agree with you on
that. On every system save one there is only one network connection,
in each of those cases it's been /dev/eth0 and NM would not enable the
connection by default.
Maybe there's documentation on the way that will make NM a breeze to
configure but until that time it's out the window. I disable the
NetworkManager service and enable the network service during kickstart
installs. All my systems have a statically leased DHCP address and it
works just fine.
Bottom line for me: NM breaks far more than it fixes.
People who keep home directories across installs are the ones facing the
most issues with NM on F9.
Its almost always a good idea to get a copy of gconf-cleaner and use it
before testing out the abilities of the the new release.
On F9, be sure to remove any NM references to eth0, or any other hard
wired interface. gconf-editor is good for that.
The new version of NM and system-config-network now work together. You
MUST enable NM control, and start interface at boot, in
system-config-network.
If you just want to tweak the file, edit
/etc/sysconfig/network-scripts/ifcfg-eth0 and make sure that the
following two lines appear in there.
ONBOOT=yes
NM_CONTROLLED=yes
Now NM will happily manage the interface.
Good Luck!
1:53 p.m.
Bill Davidsen wrote:
fedora wrote:
> Hi every
>
> What is the matter with fedora 9?
>
> it introduced a NetworkManager which prohibits networking.
NetworkMangler has been around since FC6 (at least), by making it the
default it became impossible to ignore. It does the right thing in
cases where you have one hardwire or wireless connection which can see
only one AP. For all other cases wait for the human readable
documentation which will be here... or maybe not, since it was coming
with FC7, 8, and 9.
After about a dozen installs of Fedora 9 I cannot agree with you on
that. On every system save one there is only one network connection, in
each of those cases it's been /dev/eth0 and NM would not enable the
connection by default.
Maybe there's documentation on the way that will make NM a breeze to
configure but until that time it's out the window. I disable the
NetworkManager service and enable the network service during kickstart
installs. All my systems have a statically leased DHCP address and it
works just fine.
Bottom line for me: NM breaks far more than it fixes.
1:46 p.m.
fedora wrote:
Hi every
What is the matter with fedora 9?
it introduced a NetworkManager which prohibits networking.
NetworkMangler has been around since FC6 (at least), by making it the
default it became impossible to ignore. It does the right thing in cases
where you have one hardwire or wireless connection which can see only
one AP. For all other cases wait for the human readable documentation
which will be here... or maybe not, since it was coming with FC7, 8, and 9.
programs are acessible only as root user: xsane just does nothing as
non-root user.
More likely to be a device permission problem, in my experience. Blame
hal or SElinux, it's not that hard to fix.
openoffice blocks its drop-downs in the main menu for 20 seconds, if
you
are not root. if you are root, everything is as good/as bad as with
fedora 8, thanks very much.
Other people have said that's because when they upgraded they left stuff
in various "dot" directories. Doesn't happen in clean installs, at least
that I've noticed.
openldap breaks down every now and then, and stays with a corrupt
sleepycat database, which is not revoverable.
I didn't see your bugzilla on that.
could the relevant persons please provide an update to fedora 9 as soon
as possible? thanks very much.
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
7:47 p.m.
sorry I forgot to mention that we posted the bug in bugzilla
already...although it's probably really low priority since it's just a gui
status bug and only the gui doesn't work ...command prompt edits fixes
it...the other services that have an unknown status...well we haven't gotten
around to figuring out why they are like that...will post details in
bugzilla though...sorry what I meant was from fc7-8 it was a seemless
upgrade but we really hit roadblocks with fc9 and we are still trying to
figure out why...although honestly we are more concentrated on pg right
now...we just tried fc9 and rolled back to fc8.
:( sorry again for the miscom...
----- Original Message -----
From: "Craig White" <craigwhite(a)azapple.com>
To: "For users of Fedora" <fedora-list(a)redhat.com>
Sent: Wednesday, June 25, 2008 8:14 AM
Subject: Re: What is the matter with fedora 9?
First of all, Tom didn't qualify his comments on NetworkManager
which is
very useful in some instances and apparently is installed as the default
networking daemon if you install from Live CD. His suggestion to turn it
off:
- lacked any suggestion that you need to turn on the regular 'network'
daemon in its place instead
- lacked any consideration of wireless or dhcpcd client needs
With respect your your efforts making Fedora 9 work to your
expectations, you've sort of proven your own problems to yourself but
contributed nothing to fixing any issues that may exist. One of the
great things about this list is that if you can figure out how to ask
the questions, you can get your problems solved.
Craig
On Wed, 2008-06-25 at 07:02 +0800, Robert M. Bernabe wrote:
> newbie here... trying to make linux work as a gui interface with
> postgresql... found fc9 unworkable too as compared to fc8....our own
> opinion
> is that fc9 has implemented some features we don't understand. e.eg. off
> the
> bat, after installation...the samba services status appear unknown in the
> services window...I think so do other services (somebody posted a reason
> for
> it I think... but it involves several 'classic' prompt windows edits...)
> so
> for now we are sticking to fc8...thankful for all the efforts plugged
> into
> the fedora project in general... but just wishing we understood the
> thinking
> behind the changes in fc9...
>
>
>
> ----- Original Message -----
> From: "Tom Horsley" <tom.horsley(a)att.net>
> To: <fedora-list(a)redhat.com>
> Sent: Wednesday, June 25, 2008 5:37 AM
> Subject: Re: What is the matter with fedora 9?
>
>
> > On Tue, 24 Jun 2008 17:53:37 +0200
> > fedora <fedora(a)ayni.com> wrote:
> >
> >> it introduced a NetworkManager which prohibits networking.
> >
> > Don't know about the other problems, but for me this makes
> > networking function just like always:
> >
> > chkconfig --level 2345 NetworkManager off
> > chkconfig --level 2345 network on
> > reboot
> >
> > That turns off NetworkManager and goes back to the old nasty
> > stick-in-the-mud networking that actually works :-).
> >
> > NetworkManager may be good for folks with laptops who flit
> > about from one hotspot to another, but it is hopeless for
> > us more ordinary network users who have static IPs or even
> > DHCP networks initialized at boot time and unchanging after
> > that. It should never have arbitrarily been made the default.
> >
> > --
> > fedora-list mailing list
> > fedora-list(a)redhat.com
> > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
1:05 a.m.
Hi every
i have found the couse or at least a work araund for slow working
openoffice:
if your openoffice is not responsive when clicking toolbar buttons in
the head line, the cause may be in your .gnome*, your .gconf*, or your
.x* directories. when i removed all of them and logged-in from afresh,
openoffice worked nicely.
suomi
Bassel Safadi wrote:
On Tue, Jun 24, 2008 at 6:53 PM, fedora <fedora(a)ayni.com
<mailto:fedora@ayni.com>> wrote:
could the relevant persons please provide an update to fedora 9 as
soon as possible? thanks very much.
there are a lot of updates and fixes, just type
yum update
very angry
cool down please, there is a very big effort behind fedora, so please
don't just say (What is the matter with fedora), there are already a lot
of answers and solutions for your problems
7:14 p.m.
First of all, Tom didn't qualify his comments on NetworkManager which is
very useful in some instances and apparently is installed as the default
networking daemon if you install from Live CD. His suggestion to turn it
off:
- lacked any suggestion that you need to turn on the regular 'network'
daemon in its place instead
- lacked any consideration of wireless or dhcpcd client needs
With respect your your efforts making Fedora 9 work to your
expectations, you've sort of proven your own problems to yourself but
contributed nothing to fixing any issues that may exist. One of the
great things about this list is that if you can figure out how to ask
the questions, you can get your problems solved.
Craig
On Wed, 2008-06-25 at 07:02 +0800, Robert M. Bernabe wrote:
newbie here... trying to make linux work as a gui interface with
postgresql... found fc9 unworkable too as compared to fc8....our own opinion
is that fc9 has implemented some features we don't understand. e.eg. off the
bat, after installation...the samba services status appear unknown in the
services window...I think so do other services (somebody posted a reason for
it I think... but it involves several 'classic' prompt windows edits...) so
for now we are sticking to fc8...thankful for all the efforts plugged into
the fedora project in general... but just wishing we understood the thinking
behind the changes in fc9...
----- Original Message -----
From: "Tom Horsley" <tom.horsley(a)att.net>
To: <fedora-list(a)redhat.com>
Sent: Wednesday, June 25, 2008 5:37 AM
Subject: Re: What is the matter with fedora 9?
> On Tue, 24 Jun 2008 17:53:37 +0200
> fedora <fedora(a)ayni.com> wrote:
>
>> it introduced a NetworkManager which prohibits networking.
>
> Don't know about the other problems, but for me this makes
> networking function just like always:
>
> chkconfig --level 2345 NetworkManager off
> chkconfig --level 2345 network on
> reboot
>
> That turns off NetworkManager and goes back to the old nasty
> stick-in-the-mud networking that actually works :-).
>
> NetworkManager may be good for folks with laptops who flit
> about from one hotspot to another, but it is hopeless for
> us more ordinary network users who have static IPs or even
> DHCP networks initialized at boot time and unchanging after
> that. It should never have arbitrarily been made the default.
>
> --
> fedora-list mailing list
> fedora-list(a)redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
6:02 p.m.
newbie here... trying to make linux work as a gui interface with
postgresql... found fc9 unworkable too as compared to fc8....our own opinion
is that fc9 has implemented some features we don't understand. e.eg. off the
bat, after installation...the samba services status appear unknown in the
services window...I think so do other services (somebody posted a reason for
it I think... but it involves several 'classic' prompt windows edits...) so
for now we are sticking to fc8...thankful for all the efforts plugged into
the fedora project in general... but just wishing we understood the thinking
behind the changes in fc9...
----- Original Message -----
From: "Tom Horsley" <tom.horsley(a)att.net>
To: <fedora-list(a)redhat.com>
Sent: Wednesday, June 25, 2008 5:37 AM
Subject: Re: What is the matter with fedora 9?
On Tue, 24 Jun 2008 17:53:37 +0200
fedora <fedora(a)ayni.com> wrote:
> it introduced a NetworkManager which prohibits networking.
Don't know about the other problems, but for me this makes
networking function just like always:
chkconfig --level 2345 NetworkManager off
chkconfig --level 2345 network on
reboot
That turns off NetworkManager and goes back to the old nasty
stick-in-the-mud networking that actually works :-).
NetworkManager may be good for folks with laptops who flit
about from one hotspot to another, but it is hopeless for
us more ordinary network users who have static IPs or even
DHCP networks initialized at boot time and unchanging after
that. It should never have arbitrarily been made the default.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
4:37 p.m.
On Tue, 24 Jun 2008 17:53:37 +0200
fedora <fedora(a)ayni.com> wrote:
it introduced a NetworkManager which prohibits networking.
Don't know about the other problems, but for me this makes
networking function just like always:
chkconfig --level 2345 NetworkManager off
chkconfig --level 2345 network on
reboot
That turns off NetworkManager and goes back to the old nasty
stick-in-the-mud networking that actually works :-).
NetworkManager may be good for folks with laptops who flit
about from one hotspot to another, but it is hopeless for
us more ordinary network users who have static IPs or even
DHCP networks initialized at boot time and unchanging after
that. It should never have arbitrarily been made the default.
12:10 p.m.
fedora wrote:
What is the matter with fedora 9?
it introduced a NetworkManager which prohibits networking.
programs are acessible only as root user: xsane just does nothing as
non-root user.
openoffice blocks its drop-downs in the main menu for 20 seconds, if you
are not root. if you are root, everything is as good/as bad as with
fedora 8, thanks very much.
openldap breaks down every now and then, and stays with a corrupt
sleepycat database, which is not revoverable.
You would do better to post your complaints separately,
and document them a little more clearly.
In what sense does NM "prohibit networking" (for you)?
11:14 a.m.
On Tue, Jun 24, 2008 at 6:53 PM, fedora <fedora(a)ayni.com> wrote:
could the relevant persons please provide an update to fedora 9 as
soon as
possible? thanks very much.
there are a lot of updates and fixes, just type
yum update
very angry
cool down please, there is a very big effort behind fedora, so please don't
just say (What is the matter with fedora), there are already a lot of
answers and solutions for your problems
5796
days inactive
5802
days old
25 comments
18 participants
participants (18)
-
Aaron Konstam -
Andrea Mastellone -
Andrew Kelly -
Bassel Safadi -
Bill Davidsen -
Craig White -
fedora -
Ian Malone -
max -
Mikkel -
Phil Meyer -
Ralf Corsepius -
Robert M. Bernabe -
Stephen Berg (Contractor) -
Tim -
Timothy Murphy -
Tom Horsley -
Tomasz Torcz