cpan2spec
by Patrick Dupre
Hello,
to create rpm package from cpan package, it has been recommanded
to use cpan2spec. However, I canot fond this package for fedora?
Any idea?
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
10 years, 10 months
F19 no longer includes OpenJDK7-jre in the LiveCD :-(
by Fernando Cassia
Who was the genius who decided Fedora 19 XFCE should no longer include
the OpenJDK 7 JRE like F18 did?.
This causes me lots of hassle.
:-(
FC
--
During times of Universal Deceit, telling the truth becomes a revolutionary act
Durante épocas de Engaño Universal, decir la verdad se convierte en un
Acto Revolucionario
- George Orwell
10 years, 10 months
Proposal: ReadOnlyDirectories /etc and /usr for network-services
by Reindl Harald
-------- Original-Nachricht --------
Betreff: Proposal: ReadOnlyDirectories /etc and /usr for network-services
Datum: Mon, 22 Jul 2013 00:02:02 +0200
Von: Reindl Harald <h.reindl(a)thelounge.net>
An: Mailing-List fedora-devel <devel(a)lists.fedoraproject.org>
Hi
has anybody considered to put the following as default in systemd-units of
network services? cross-posting to users-list intented because i think it
is a good idea to bring it to a broader userbase!
ReadOnlyDirectories=/etc
ReadOnlyDirectories=/usr
http://www.freedesktop.org/software/systemd/man/systemd.exec.html
additionally having the RPM database to accessable for network-services
is fine, set for all listed below and reduces the attack surface
InaccessibleDirectories=/var/lib/rpm
InaccessibleDirectories=/var/lib/yum
__________________________________________________
this would greatly reduce the impact of a possible root-exploit
and IMHO make installing a rootkit hard to impossible while
it is a good compromise to read-only /usr on a own partition
without make system-administration via SSH harder
__________________________________________________
currently i am in prodcution with it for the following services
most of them real production (customer-services) and a few on
home-servers or even not available in the Fedora repos
* asterisk
* dbmail
* dhcpd
* dnsmasq
* dovecot (running as IMAP/POP3 proxy and SASL)
* hostapd
* httpd
* hylafax
* iaxmodem
* mailgraph
* mpd
* mpdscribble
* mysqld
* named
* netatalk
* ntpd
* open-vm-tools
* openvpn
* postfix
* prosody
* pulseaudio (systemwide)
* pure-ftpd
* rsyslog
* smbd
* smokeping
* unbound
* vnstat
* xinetd (TFTP)
__________________________________________________
exeptiopns:
* trafficserver
it touchs /etc/trafficserver at startup
"ReadOnlyDirectories=/usr" is fine
* mediathomb
refuses for whatever reason to start with read-only /etc
"ReadOnlyDirectories=/usr" is fine
10 years, 10 months
Bumblebee and Fedora 19
by Junayeed Ahnaf
Hello,
I'm trying to install bumblebee on my laptop. But when I'm trying "optirun glxgears info" this error is showing:
[root@localhost nirjhor]# optirun glxgears info
[ 1691.769152] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "mouse" (module does not exist, 0)
[ 1691.769189] [ERROR]Aborting because fallback start is disabled.
[root@localhost nirjhor]#
Just for the info :
[root@localhost nirjhor]# lspci -vnn | grep '\''[030[02]\]'
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
01:00.0 3D controller [0302]: NVIDIA Corporation GK107M [GeForce GT 740M] [10de:0fdf] (rev a1)
[root@localhost nirjhor]#
Can anyone help me solve it?
Junayeed Ahnaf Nirjhor
Software Engineer @ Hulu
Twitter @ Nirjhor
10 years, 10 months
Re: cannot open device with Xsane
by Antonio M
: ** Message: No devices in use, exit
Jul 21 16:19:06 Pc-campeggio-001 xsane: common/utils.c 187: unable to load
library libm.so: libm.so: impossibile aprire il file oggetto condiviso:
File o directory non esistente
Jul 21 16:19:06 Pc-campeggio-001 xsane: common/utils.c 68: unable to open
/var/lib/hp/hplip.state: File o directory non esistente
Jul 21 16:19:06 Pc-campeggio-001 xsane: common/utils.c 118:
validate_plugin_version() Failed to get Plugin version from
[/var/lib/hp/hplip.state]
Jul 21 16:19:06 Pc-campeggio-001 xsane: common/utils.c 156: Plugin version
is not matching
Jul 21 16:19:06 Pc-campeggio-001 xsane: common/utils.c 219: Invalid Library
hanlder pLibHandler = NULL.
this is the output from var/log/messages
2013/7/21 Antonio M <antonio.montagnani(a)gmail.com>
> same packages installed, scanner is recognized by Xsane ...but then I get
> the error:
>
> it is not possible to open device:
> "hpaio:/usb/HP_Color_LaserJet_CM1312_MFP?serial=00CNF8BCG91J":there is an
> error during I/O of device. Translation may not be correct
>
>
> 2013/7/21 Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
>
>> On 07/21/2013 03:51 PM, Antonio M wrote:
>>
>>> on a fresh F19 installation when I start Xsane or simple scanning,
>>> multifunction printer is recognized, asHP MFC 1312, but it says that
>>> device "hpaio...." cannot be opened.
>>>
>>> Any hint??
>>>
>>> --
>>> Antonio Montagnani
>>> Skype : amontag52
>>>
>>> Linux Fedora 19 Schroedinger's cat
>>>
>>>
>>>
>> Which sane components did you install?
>>
>> On my box:
>>
>> sane-backends-1.0.23-13.fc19.**x86_64
>> sane-backends-devel-1.0.23-13.**fc19.x86_64
>> sane-frontends-1.0.14-16.fc19.**x86_64
>> xsane-common-0.999-3.fc19.x86_**64
>> libsane-hpaio-3.13.6-2.fc19.**x86_64
>> xsane-0.999-3.fc19.x86_64
>> sane-backends-drivers-cameras-**1.0.23-13.fc19.x86_64
>> sane-backends-drivers-**scanners-1.0.23-13.fc19.x86_64
>> sane-backends-libs-1.0.23-13.**fc19.x86_64
>>
>> Especially, did you install sane-backends and sane-backends-drivers-**
>> scanners?
>>
>> Regards
>>
>> Joachim Backes
>>
>> --
>>
>> Fedora release 19 (Schrödinger’s Cat): Kernel-3.9.9-302.fc19.x86_64
>>
>> Joachim Backes <joachim.backes(a)rhrk.uni-kl.de**>
>> https://www-user.rhrk.uni-kl.**de/~backes<https://www-user.rhrk.uni-kl.de/~backes>
>>
>
>
>
> --
> Antonio Montagnani
> Skype : amontag52
>
> Linux Fedora 19 Schroedinger's cat
>
--
Antonio Montagnani
Skype : amontag52
Linux Fedora 19 Schroedinger's cat
10 years, 10 months
cannot open device with Xsane
by Antonio M
on a fresh F19 installation when I start Xsane or simple scanning,
multifunction printer is recognized, asHP MFC 1312, but it says that device
"hpaio...." cannot be opened.
Any hint??
--
Antonio Montagnani
Skype : amontag52
Linux Fedora 19 Schroedinger's cat
10 years, 10 months
add application launcher
by Patrick Dupre
Hello,
I already post about this issue.
in Fedora 18 I was able to add an application launcher by clicking right
on the application menu or by using alacarte
This option does not work in fedora 19. Is there an alternative?
Is it a bug?
Thank for your help.
Regards.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
10 years, 10 months
Open MPI problem After F17 -> F18 Upgrade
by Kevin H. Hobbs
After I updated my home computer from Fedora 17 to 18 MPI programs
stopped working.
I have a very simple program :
#include <stdlib.h>
#include <stdio.h>
#include <mpi.h>
int main( int argc, char * argv[] )
{
int rank, size;
MPI_Init(&argc, &argv);
MPI_Comm_rank(MPI_COMM_WORLD, &rank);
MPI_Comm_size(MPI_COMM_WORLD, &size);
printf("my rank is %i of %i\n", rank, size );
MPI_Finalize();
return EXIT_SUCCESS;
}
I can compile it with :
mpicc -g -o mpi_simple mpi_simple.c
but when I run it with :
mpirun -n 1 ./mpi_simple
I get :
[murron.hobbs-hancock:05668] [[55801,1],0] ORTE_ERROR_LOG: Error in file
util/nidmap.c at line 148
[murron.hobbs-hancock:05668] [[55801,1],0] ORTE_ERROR_LOG: Error in file
ess_env_module.c at line 174
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):
orte_util_nidmap_init failed
--> Returned value Error (-1) instead of ORTE_SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):
orte_ess_set_name failed
--> Returned value Error (-1) instead of ORTE_SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during MPI_INIT; some of which are due to configuration or environment
problems. This failure appears to be an internal failure; here's some
additional information (which may only be relevant to an Open MPI
developer):
ompi_mpi_init: orte_init failed
--> Returned "Error" (-1) instead of "Success" (0)
--------------------------------------------------------------------------
[murron.hobbs-hancock:05668] [[55801,1],0] ORTE_ERROR_LOG: Error in file
runtime/orte_init.c at line 128
[murron.hobbs-hancock:5668] *** An error occurred in MPI_Init
[murron.hobbs-hancock:5668] *** on a NULL communicator
[murron.hobbs-hancock:5668] *** Unknown error
[murron.hobbs-hancock:5668] *** MPI_ERRORS_ARE_FATAL: your MPI job will
now abort
--------------------------------------------------------------------------
An MPI process is aborting at a time when it cannot guarantee that all
of its peer processes in the job will be killed properly. You should
double check that everything has shut down cleanly.
Reason: Before MPI_INIT completed
Local host: murron.hobbs-hancock
PID: 5668
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun has exited due to process rank 0 with PID 5668 on
node murron.hobbs-hancock exiting improperly. There are two reasons this
could occur:
1. this process did not call "init" before exiting, but others in
the job did. This can cause a job to hang indefinitely while it waits
for all processes to call "init". By rule, if one process calls "init",
then ALL processes must call "init" prior to termination.
2. this process called "init", but exited without calling "finalize".
By rule, all processes that call "init" MUST call "finalize" prior to
exiting or it will be considered an "abnormal termination"
This may have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--------------------------------------------------------------------------
I'm actually able to run the generated executable on another computer
just fine.
I tried using gdb to step through util/nidmap.c from 148 but whatever
goes wrong is too far away for me to find it.
Does anybody have any clue where I should look?
10 years, 10 months
Transmission daemon not starting in Fedora 19
by Suvayu Ali
Hi,
I'm having trouble starting transmission-daemon. When I try to start it
with systemctl, it hangs:
# systemctl start transmission-daemon.service
If I let it be for a few minutes (~5), it finishes with a failure. The
log is extremely unhelpful. This is very strange because it was working
just fine until a few days ago.
Jul 16 01:20:00 <hostname> systemd[1]: Starting Transmission BitTorrent Daemon...
-- Subject: Unit transmission-daemon.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit transmission-daemon.service has begun starting up.
Jul 16 01:21:30 <hostname> systemd[1]: transmission-daemon.service operation timed out. Terminating.
Jul 16 01:21:33 <hostname> transmission-daemon[13592]: Closing transmission session... done.
Jul 16 01:21:33 <hostname> systemd[1]: Failed to start Transmission BitTorrent Daemon.
-- Subject: Unit transmission-daemon.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428b...
--
-- Unit transmission-daemon.service has failed.
--
-- The result is failed.
Jul 16 01:21:33 <hostname> systemd[1]: Unit transmission-daemon.service entered failed state.
Any ideas how I can debug this?
--
Suvayu
Open source is the future. It sets us free.
10 years, 10 months