Hi,
Currently, values set in /etc/sysctl.conf are set on boot when sysctl
-p -e is called. This happens in /etc/network. Of course, setting
values for kernel modules not loaded at that point has no effect.
This caught me out recently, as I tried to set a value for one of the
conntrack modules. Because the relevant module wasn't loaded until
shorewall started on my system, and because shorewall is started after
the network, the setting didn't do anything. The way I fixed it is by
adding sysctl -e -p to rc.local, so that it is ran after all the other
init scripts. However, I could see that this approach might be unwise
since the nfs script uses sysctl to change some values, and
potentially that could be undone by bad settings in sysctl.conf.
My question then is: should there not be a service that runs sysctl on
boot, as the last thing before rc.local? I have seen this on other
distributions. This would make the following statement true: If you
want to make a change to /proc/sys persistent across reboots, then add
it to /etc/sysctl.conf. It currently isn't always true due to the
timing of systl being run, but that statement is, for many, expected
behaviour.
Thoughts?
Jonathan.

Does bluetooth automatically work for anyone? I'm seeing the following
problems:
bluetooth service always fails to start at boot - address in use
- can be started by hand after
bluetooth-applet doesn't seem to get run at login
- works fine if started by hand
It seems like stuff is working, just not automatically.
tjb
--
=======================================================================
| Thomas Baker email: tjb(a)unh.edu |
| Systems Programmer |
| Research Computing Center voice: (603) 862-4490 |
| University of New Hampshire fax: (603) 862-1761 |
| 332 Morse Hall |
| Durham, NH 03824 USA http://wintermute.sr.unh.edu/~tjb |
=======================================================================

My T61 has the Nvidia Quadro NV140M video card. I tested the x86_64
live dvd and installed the x86_64 DVD. This message covers
platform-specific issues that I encountered.
Live DVD:
- The DVD won't boot into X. If I boot to runlevel 3 and attempt to
system-config-display, there are two problems.
(1) The Monitor section of xorg.conf is missing.
(2) The nv driver hangs with a black screen. The keyboard is still
functional and I can reboot with <CTRL>-<ALT>-<F1> <CTRL>-<ALT>-<DEL>.
Hand-editing xorg.conf to create a Monitor section and using the vesa
driver restores X functionality.
- I used gparted to resize NTFS partitions and partition the drive. It
hung at the end of the resize operation without confirming it is
finished (although the operation appears to have completed). Also,
gparted quits after the rescan step after each operation set.
Installation:
- Have to install with "vesa" kernel option. The nv driver boots to a
black screen.
- On the Disk Druid screen, the screen is not repainted after opening
and closing popups.
- The display is only configured for 800x600.
Post-Installation:
- Display issues (as above--nv driver and Monitor detection don't work).
The new nv drivers don't help.
- Screen brightness is erratic. The screen brightness applet appears,
but whatever controls I hit, brightness changes randomly up or down and
does not get fully bright or dim. If I switch to a VC, I can control
the brightness, but ^@ characters appear on the display.
- X server doesn't terminate on logout--I have to <CTRL>-<ALT>-<BKSP> to
kill it.
- Suspend doesn't work at all. Select Suspend from the power applet and
the machine starts to suspend, the light comes on, then the light goes
off and the machine is live, except that the display is black. I can
reboot as above.
- Hibernate appears to work, but on resume I get a message that
hibernate failed.
- Stopping the bluetooth service on reboot or shutdown fails, although
starting on bootup succeeds. Have not tested bluetooth functionality
otherwise.
Can anyone confirm these behaviors and that they are bugs? I'll file
them, if so. Workarounds welcome too.
There are some other issues I'll post later, but they don't seem
hardware related.

The i810switch program has been around for a while, and it forces the
Intel i810 - i945 series video chips to enable or disable the external
VGA or LCD panel video output devices on a laptop. i810switch has not
had an update since June 2005.
In Fedora 8, the xrandr application provides this same functionality,
natively in the Xorg subsystem.
In my limited testing, xrandr works on the i810 class hardware I have
access to.
I'd like to drop i810switch from the distribution for Fedora 8, and
add a release note suggesting users of i810switch use xrandr instead.
Thoughts?
Thanks,
Matt
--
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux

Hi all,
A couple of days ago I filed this (fairly detailed bug):
https://bugzilla.redhat.com/show_bug.cgi?id=304551
About opengl rendering problems with a certain app on an other wise perfectly
fine working opengl setup, and explaining that downgrading mesa-libGL and not
making any other changes fixes this. Notice the and not making any other
changes. Iow this is in no way a configuration problem.
So I got his canned response:
"Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this
information.
Thanks in advance."
Which is not the first time, and which just plain sucks! This looks as if it
was added without even taken a look at the bug, as the requested info ranges
from little relevant to compeltely unrelevant. This does not motivate me (at
all) to take the time to fill proper detailed bug reports!
So can we please stop with this kind of canned responses, I understand they can
be usefull but before adding them atleast read the bug and consider if they are
relevant.
Thanks & Regards,
Hans

We gonna start an Rpmfusion Fedora spin giving user
the much wanted/needed media support in Fedora.
With strictly the media support ( ugly-plugins etc. ) and the rpmfusion
repo installed,
and excluding AMD and Nvidia drivers
will we need Rename the spin or could it be released under Fedora name
and artwork? * Legal/others
If needed to change the name/artwork would FedoriansFusion be A OK
If naming/artwork is changed could we include the AMD and Nvidia drivers?
Will this be available on fedoraprojects.org as in
will Max Spevack put his money where is mouth is so I quote Max
"So go forth and mix your own Fedora. And then come back and share it
with us, and we’ll put it up on the _*Fedora website for others to use
also.*_"
ref. ( http://www.redhatmagazine.com/2007/05/31/remixing-fedora-7/ )
Or was this just a pr c...
It would be interesting download stats Fedora VS Fedora with media
support :)
If everything is done outside US hosted outside US created outside US
how much legal
jibber jabber comes from that ? Not for US residents version of Fedora?
Best regards
Johann B.
--
Johann B. Gudmundsson. RHCE,CCSA
Unix System Engineer.
IT Management.
Reiknistofnun University of Iceland.
Taeknigardi, Dunhaga 5. Email: johannbg(a)hi.is
IS-107 Reykjavik. Phone: +354-525-4267
Iceland. Fax: +354-552-8801

As I've mentioned in previous emails to this list,
system-config-printers depends on pirut for installing other packages.
Specifically, s-c-p calls /usr/bin/system-install-packages to install
new print drivers.
PackageKit has two helpers like this, pk-install-package and
pk-install-file. The former allows a script or program to install
"openoffice.org" using the PackageKit daemon (asking PolicyKit auth and
resolving the package_id etc.) and the latter allows installing local
files such as /tmp/moo-1.23.rpm
How do I go about making s-c-p call into PackageKit instead? I'm
guessing I have to "provide" /usr/bin/system-install-packages in the
PackageKit spec file, and then install a symlink to pk-install-package -
this would then leave two packages owning the same file.
What's the Fedora way of solving this - maybe alternatives (which might
be overkill) or maybe some cleverness in s-c-p?
Thanks,
Richard.