A heads up for those of you who have already seen the announcement
over the weekend.
I'm at 33 requests, I'm looking for at least 75. If you are
interested but haven't sent in the details stop procrastinating and
get your requests in.
If you've forgotten what I'm talking about, refresh your memory here:
Please do not reply back to this thread. I'm guaranteed to lose the
request in the big inbox pile unless you do the following:
Subject: LWN subscription request
Your real name
Your fas accountname
your lwn accountname to be granted a subscription
-jef"You'd think giving away freebies would be easier"spaleta
today I have some kind of bad day - I'm filing many bugs and doing many
things I wouldn't do in a usual day.
I considered using prelink months ago but I was afraid.
I run "prelink -amR" today, but I saw warning about PIC.
I've read in Gentoo's docs that shared libraries must be compiled with
We do we have -fPIC in CFLAGS not, while prelink in repo?
This is a new thread spawning from the "3.6% of heads up: Please correct your
#includes or optflags use" thread.
I would like to propose to add "-Werror-implicit-function-declaration" to the
default optflags. Why? Because missing prototypes can cause all sorts of problems:
Anything (any function) that returns a pointer, will be a problem when compiled
on 64 bit without a prototype, as the compiler will assume the return type is
an int, and then cast that to a pointer as needed.
Anything returning a float / double will be a problem regardless of 32/64 bits
as only 32 bits of the returned floating point number will be taken and
interpreted as an int (and then cast back to a float / double if used as such).
Any function called with arguments of different type then expected (for example
a float, where the function expects an int or visa versa) will have the same
Which is why I say: fix them all.
I just installed the Fedora 9 Beta release and am doing a full system
update as we speak.
While downloading the updates nothing is wrong.. it just downloads and
that's it. But when installing the updates i get a ton of selinux
notices!! and this is just a default Fedora 9 beta followed by a yum
Also another issue that i noticed was when looking at a flash
animation in firefox.. when i want to play the animation selinux
(again) drops in and tells me i can't. (or i need to run a command to
get it working).
Now i've tried to run selinux on Fedora 7 and 8 for as long as
possible just to see how long i can get around it.. i did some
commands in that time as well but i always end up with disabling
I have no idea how other users are using fedora in a normal every day
usage without disabling selinux.. i agree that a firewall should be in
linux but selinux just doesn't seem mature yet (if it will ever be).
Perhaps it's time to start considering to turn off selinux and remove
it out of the fedora kernel completely? As long as it's blaming here
when i install updates or simply browse the web than selinux gets shut
So.. how are you doing this?
Btw.. justging from the selinux stats here:
http://smolts.org/static/stats/stats.html it says that nearly 50%
(48.4%) is turning off selinux. And my guess is that all fedora
servers keep it on making up the other 50%.
With the switch to upstart, we obviated the need for /etc/inittab (upstart
does not need it, nor read it.)
Initially, we added a quick hack that read /etc/inittab solely to determine
the default runlevel. Based on a bug I filed (#432384), we changed that so
that the key for runlevel 3 vs. runlevel 5 is GRAPHICAL in /etc/sysconfig/init,
and we'e planning to just remove the inittab file to make things more obvious.
I'm open to better ideas, though - should we ship a trimmed inittab that
contains *only* the initdefault line? Should we introduce a new configuration
flag somewhere else? Does it really matter in the long run?
I have a suggestion about the default software for Fedora:
First: In Latin America most part of people does´t have a fast Internet
conection, and for this reason is difficult to install new software by YUM.
Second: An important point that experts evaluate on a S.O. is "ready out of
the box" and you supose how many changes you have to do to leave Fedora
With this ideas my suggestion is to include many software by default on
Fedora (Especially in Fedora LiveCD)
- Linux Terminal Server (tsclient)
- Fedora Frog (Easy front-end)
- Nautilus (always use browser by default)
And why not? we can do easy including by default the most common
repositories for Fedora:
I hope my suggestion will be taken into account. Remember, this idea is
designed to do Fedora more competitive and more easy for the final user.
Fedora Ambassador for Colombia
Fedora 8 Kernel Linux 2.6.24 + Gnome
I'm curious why the packaging guidelines aren't more specific re: the
requirements for the BuildRoot tag.
To my mind, the BuildRoot is a purely internal "implementation detail"
of the build process, and no package should really depend on any
specific detail of the BuildRoot value/location.
So, I'm wondering:
1) Why doesn't Fedora specify a single BuildRoot value that all packages
"MUST" use (and possibly script an update of all existing .spec files).
2) Going further, why not remove BuildRoot from all .spec files, and
simply cause the "defined correct" value to be used without "manual"
It seems one/both of the above would make reviewing easier; one less
thing to check (or only a single precise thing to check for, without
interpretation of what a "sane" BuildRoot is)
I feel I must be missing something given the flexibility allowed by the
guidelines. Any insight appreciated.
first, I am not entirely sure this the right list for this kind of
issue, so I apologise in advance in case it isn't. And now for the
At home I am connected to home network, most of the time wireless, but
when wired the issue seems to be same. The connection of the home
network to outside is quite buggy and traffic drops quite often to zero
or near zero values, and sometimes the connection is even lost (it's via
wifi, unfortunately with low visibility to the router we connect to).
What bugs me is that when the connection is in its near-dead state my
Fedora is very low responsive. For example I tried to open terminal (via
key shortcut) and it didn't pop up at least for ten seconds, and then
instantly when I disabled my network connections. This low
responsiveness happens whenever the traffic drops to zero or near zero
(and a lot of packets is lost). CPU load is at normal during the 'lags'.
Also already loaded applications seems to behave decently.
My question is:
Is this behaviour to be expected or is it a bug? I don't know exactly
how these things work, but I fail to imagine how can network problems
affect system responsiveness...
Thanks for your thoughts,
Versions of the components I think might be relevant to this issue: