Just wanted to let you know that i've done a pretty large update of
The biggest change is that it now contains the huge updated services
file now along with fixes for quite a few bugs.
Also pathmunge will now be available for login or non-login shells in
/etc/profile.d/, so feel free to use that now there too (some 3rd party
packages seem to want to use it ;)
Also, /usr/X11R6/bin is no more. We don't have a single file in
/usr/X11R6 left, so this is one of the final steps of the modular
If you should still need it you can easily dump a pathmunge script in
/etc/profile.d/x11r6.sh that just contains
Please give the package some beating and let me know (via bugzilla) if
anything broke for you (which i don't expect, but who knows ;).
Read ya, Phil
Philipp Knirsch | Tel.: +49-711-96437-470
Development | Fax.: +49-711-96437-111
Red Hat GmbH | Email: Phil Knirsch <phil(a)redhat.de>
Hauptstaetterstr. 58 | Web: http://www.redhat.de/
Motd: You're only jealous cos the little penguins are talking to me.
What Mono versions are planned shipped with FC5?
Reason I am asking is that Banshee now demands 2.8, but it seems
Fedora currently only ships 2.4. I was told f-spot also demands 2.8 at
On Mon, 30 Jan 2006 13:40:36 -0500 Bill Nottingham (notting redhat com) wrote:
> Should be fixed in gphoto2-2.1.99-5, which should hit rawhide tomorrow.
> You'll have to replug after upgrading.
I also opened a bug, after posting. it is 179315.
I posted in bugzilla for the udev package but it was "routed" by
bugzilla to hal.
The camera is seen from root.
I thought that within the interaction between udev and hal to
associate device names,
symlinks and permissions when plugging devices, the permission part
was responsibility of udev,
for example with settings inside /etc/udev/permissions.d directory .....
You instead are saying that is a matter of gphoto2...??
I think that I'm missing something here...
Thanks for your clarifications
With today updates I'm not able to access my digicamera from digikam.
It is about one month I don't use it so I don't know exact time problem arose.
I think it depends on recent hotplug changes.
In 21/01 rawhide report we have
Removed package hotplug
>From non root user:
[valeria@fedora ~]$ gphoto2 --auto-detect Modello Porta
[root@fedora ~]# gphoto2 --auto-detect
Kodak CX7525 usb:
Kodak CX7525 usb:002,002
gphoto2 --version gives:
gphoto2 2.1.99 i386-redhat-linux-gcc, popt, exif, no
cdk, no aa, jpeg, readline
libgphoto2 2.1.99 i386-redhat-linux-gcc, EXIF, no /proc/meminfo
libgphoto2_port 0.5.2 i386-redhat-linux-gcc, USB, serial
Should I have to re-install hotplug or what?
What program/daemon would have to care about correct handling
permission of usb devices
for non root users?
Remi Collet (Liste(a)famillecollet.com) said:
> >* Thu Jan 26 2006 Christopher Aillon <caillon(a)redhat.com> - 1.5-5
> >- Ship langpacks again from upstream
> >- Stop providing MozillaFirebird and mozilla-firebird
> Why not having a separate "langpack" RPM for each langage as OOo ?
> firefox-langpack-fr for example ?
> Everyone probably don't need all the langages. And updates will be
> simpler (not affecting the langpack).
It makes enumerating the packages to install *much* more of a PITA.
Every time you add a new langpack to the distro, you need to add
separate metadata elsewhere...
Can somebody point me to latest docs on inotify? Is this inotify.txt
from the kernel-docs rpm supposed to be current?
I tried to use it from a test program but I get:
test.o: In function `main':test.c:(.text+0x43): warning: warning:
inotify_add_watch is not implemented and will always fail
:test.c:(.text+0x15): warning: warning: inotify_init is not implemented
and will always fail
I'm hoping this is just me doing something wrong. Hasn't inotify been
in Rawhide for some time now?
I've got a laptop that needs "novesa" to start the installer going. The
installer won't start without it, and will hang on a blank screen.
Do we maintain a blacklist of vesa-deficient hardware, and, if so, which
bugzilla product do I submit my particulars to?
This thread generated no traction on fedora-list so I'll ask here as
there might be more chance somebody here can answer the kernel hooks
Is there a cool curses app that can tell you which PID is writing to
which file handle, on what device and at what speed ?
I've been wondering how to get this sort of info out of existing tools
(lsof, top, etc) without success.
Would the right kernel hooks be in place to at least write something
like this ?
iostat is useful, but I'm after something a little more intuitive,
iostat can't handle a PID as an argument for example.
NAME PID BLOCKS/W BLOCKS/R KB/s FD "FILE NAME" DEVICE
httpd 4836 45 1 53 13 /var/log/httpd/xxx /dev/hda2
And so on..
Diagnosing disk IO problems would be far easier if one had a tool that
could give "at a glace" detail into what is doing what and where..
iostat shows you what disk, or which partition is busy, but not what PID
is doing the i/o. So one must go back to lsof and get a list of open
handles on that partition or device and guess which one is pushing the