Starange?
by jarmo
Quite often I can see in TOP /usr/libexec/we action. Has anybody any
idea, what this might be and what makes it running? If I look into
/usr/libexec I can't find "we" from there.
Jarmo
10 years
RE: Coding Practice [was Re: Serious OpenSSL vulnerability]
by J.Witvliet@mindef.nl
-----Original Message-----
From: users-bounces(a)lists.fedoraproject.org [mailto:users-bounces@lists.fedoraproject.org] On Behalf Of g
Sent: woensdag 9 april 2014 9:19
To: users(a)lists.fedoraproject.org
Subject: Re: Coding Practice [was Re: Serious OpenSSL vulnerability]
On 04/09/14 11:35, Jonathan Ryshpan wrote:
<<>>
> It's an interesting question why Net infrastructure code
> continues to be written in C, a language that provides no
> automatic checks for buffer overflow, which (if I understand right) is the opening for this security breach, along with so
> many others. And why is the code run on hardware that provides
> no such checks? There have been languages and system that check
> for overflow available for 40 years.
from early times, c, c++ and the various "enhancements", were used because it was a universal language that code/source, could be written under 1 cpu and transferred to another and still run because code/source was run thru a cpu specific compiler.
something that could be done with basic, fortran, python, and other 'high level' languages. but, with the most efficient language, assembler, such could not be.
c and c++ are not interchangeable in there code. nor is c++ an enhancement or super set of c. they are each in their own world.
because of all the routines that where built up for c/c++, it soon became a sudo standard in programming. yet it falls short in ability of specific uses and will never replace fortran, python and other high levels.
c/c++ is a very inefficient language, yet it has been accepted as 'the language to learn and use'. a very bad misconception.
compactors have been written for c/c++, but even after many hours to days, and longer of running compactors, c/c++ still fail to be reduced to what can be done with high level languages, and will never come any where near the compactness of assembler.
the worst fault of c/c++ is buffer overflow, yet know one seems to really care. mainly an attitude of 'if it overflows, we will worry about it then'. not the best way to think.
if one were to run an analysis of programs that are hacked and of security that has been broken, one would find that what is written with c/c++ is the easiest to hack and break. a nature of the beast.
> Why doesn't anyone use them?
because they are easy to understand, learn and use.
-----Original Message-----
Sorry, but I have to disagree.
I date back from the ages where one _had_ to learn & write in assembly, mainly because other languages were way to slow.
And I was pleasantly surprised that drivers for network-cards and disks could be written in "C" without timing errors.
The quality of the code is not related to the language being used. Only to the person doing the coding.
Relying on others to do checking only breeds lazy programmers and bloated code.
And whatever language you use, people can still create unreadable spaghetti-code ;-)
______________________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
10 years
Blank Desktop (KDE, Xfce, Gnome) After SELinux Change
by Brian Hanks
I'm hoping that someone has experienced something similar to this and
can help point me in the correct direction. I was getting %posttrans
errors and yum was hanging during kernel updates. I read several posts
and also found some articles via Google search that suggested that
changing SELinux to Permissive would fix the problem, so I made the
change in both /etc/selinux/config and in the SELinux admin tool. I
rebooted and found that I had a blank Xfce desktop, so I switched to KDE
which was also blank, so I switched to Gnome which was also blank.
Applications still function in Xfce, but the desktop environment is
blank. KDE and Gnome are more broken, so they are not that functional.
The good news is that I was able to update the kernel without getting
the errors. The bad news is that even after changing SELinux back to
the previous settings the desktop is still blank. I've also tried to
completely disable SELinux, but it's still blank.
Let me know if you have any thoughts or solutions.
Thanks,
Brian
10 years
Can Fedora run on Lenovo ThinkPad T430?
by Oliver Ruebenacker
Hello,
Is it at all possible to run Fedora on a Lenovo ThinkPad T430 without
crashing three to five times per day? Has any one been able to do this?
That is my experience. I'm on F20. Today, there were some update,
including a new kernel, which made things worse, and now it won't boot into
the latest kernel at all.
Windows 8 on same machine runs fine (it's dual-boot with GRUB going
first).
I have been having these problems since months. I always, thought, maybe
with the next update, things will get better, but they haven't. I might
just give up on Fedora.
Thanks!
Best,
Oliver
--
Oliver Ruebenacker
Founder at Relomics Consulting <http://www.relomics.com>
Be always grateful, but never satisfied.
10 years
Can not retrieve metalink for repository fedora/20/i386
by David Mehler
Hello,
I've been having update problems since yesterday on my f20 system. I
keep getting the above message can not retrieve metalink repository
fedora/20/i386.
At first I thought the repos were down, but a host and ping shows they're up.
I googled and saw similar issues, but without a fix, I'm hoping
someone can help me get my yum working again. If I change
skip_if_unavailable in fedora/20/i386 to true I then get the same
error with fedora/20/update repo, if I set that one to
skip_if_unavailable to true the process works, but I don't get any
updates. Here's my nonworking repo setup:
#yum update
One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:
yum-config-manager --disable <repoid>
4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Cannot retrieve metalink for repository: fedora/20/i386. Please verify
its path and try again
and my repo setup:
fedora.repo:
[fedora]
name=Fedora $releasever - $basearch
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasev...
enabled=1
metadata_expire=7d
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False
fedora-updates.repo:
[updates]
name=Fedora $releasever - $basearch - Updates
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/
metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released...
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False
remi.repo:
[remi]
name=Les RPM de remi pour Fedora $releasever - $basearch
#baseurl=http://rpms.famillecollet.com/fedora/$releasever/remi/$basearch/
mirrorlist=http://rpms.famillecollet.com/fedora/$releasever/remi/mirror
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-remi
rpmfusion-free.repo:
[rpmfusion-free]
name=RPM Fusion for Fedora $releasever - Free
#baseurl=http://download1.rpmfusion.org/free/fedora/releases/$releasever/Everything/$basearch/os/
mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-$rele...
enabled=1
metadata_expire=7d
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-$releasever
rpmfusion-free-updates.repo:
[rpmfusion-free-updates]
name=RPM Fusion for Fedora $releasever - Free - Updates
#baseurl=http://download1.rpmfusion.org/free/fedora/updates/$releasever/$basearch/
mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-updat...
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-$releasever
Help appreciated.
Thanks.
Dave.
10 years
Some failures at boot-time
by antonio montagnani
I noted some failures at boot time: digging I found:
[root@Fujiantonio antonio] systemctl | grep failed
rngd.service loaded failed failed Hardware RNG Entropy Gatherer Daemon
systemd-sysctl.service loaded failed failed Apply Kernel Variables
[root@Fujiantonio antonio]# journalctl -a -b _SYSTEMD_UNIT=systemd-sysctl.service --no-pager
-- Logs begin at mer 2014-03-12 22:00:56 CET, end at lun 2014-04-14 13:24:40 CEST. --
[root@Fujiantonio antonio]# systemctl -l status systemd-sysctl.service
systemd-sysctl.service - Apply Kernel Variables
Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static)
Active: failed (Result: exit-code) since lun 2014-04-14 08:54:03 CEST; 4h 32min ago
Docs: man:systemd-sysctl.service(8)
man:sysctl.d(5)
Process: 512 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=1/FAILURE)
Main PID: 512 (code=exited, status=1/FAILURE)
apr 14 08:54:03 Fujiantonio systemd[1]: Starting Apply Kernel Variables...
apr 14 08:54:03 Fujiantonio systemd[1]: systemd-sysctl.service: main process exited, code=exited, status=1/FAILURE
apr 14 08:54:03 Fujiantonio systemd[1]: Failed to start Apply Kernel Variables.
apr 14 08:54:03 Fujiantonio systemd[1]: Unit systemd-sysctl.service entered failed state.
Is this connected to any known bug??
Antonio
10 years
brother mfc-j5910DW support?
by Aleksandar Kostadinov
Hello,
I was wondering if anybody used this device with fedora 20? I'm
considering to buy one. I see some drivers on brother web site but seems
somehow old. I'd like to print and scan over wifi.
Thank you!
10 years
Laptop bootup randomly stalls
by Richard Shaw
My wife's laptop has been having some sort of problem booting up since F18,
though I have no idea if the current problem with F20 is the same problem
or not.
The bootup process will randomly stall and most of the time you can't get
to a VT though it isn't locked up as a Ctl-Alt-Del will cause a proper
shutdown and reboot. There's a lot of noise trying to find the issue in
journalctl -b -1 (after a successful boot) but I think MAYBE this is it...
Apr 11 07:56:43 ladyhobbes.localdomain dbus-daemon[723]: dbus[723]:
[system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Apr 11 07:56:43 ladyhobbes.localdomain dbus[723]: [system] Failed to
activate service 'org.freedesktop.PolicyKit1': timed out
Apr 11 07:56:43 ladyhobbes.localdomain dbus-daemon[723]: dbus[723]:
[system] Failed to activate service 'org.freedesktop.systemd1': timed out
Apr 11 07:56:43 ladyhobbes.localdomain dbus[723]: [system] Failed to
activate service 'org.freedesktop.systemd1': timed out
Apr 11 07:56:43 ladyhobbes.localdomain dbus-daemon[723]: dbus[723]:
[system] Failed to activate service 'org.freedesktop.ColorManager': timed
out
Apr 11 07:56:43 ladyhobbes.localdomain dbus-daemon[723]: dbus[723]:
[system] Activating systemd to hand-off: service
name='org.freedesktop.ColorManager' unit='colord.se
Apr 11 07:56:43 ladyhobbes.localdomain dbus[723]: [system] Failed to
activate service 'org.freedesktop.ColorManager': timed out
Apr 11 07:56:43 ladyhobbes.localdomain dbus[723]: [system] Activating
systemd to hand-off: service name='org.freedesktop.ColorManager'
unit='colord.service'
Apr 11 07:56:44 ladyhobbes.localdomain dbus-daemon[723]: dbus[723]:
[system] Failed to activate service 'org.freedesktop.Accounts': timed out
Apr 11 07:56:44 ladyhobbes.localdomain dbus[723]: [system] Failed to
activate service 'org.freedesktop.Accounts': timed out
Apr 11 07:56:44 ladyhobbes.localdomain gdm[727]: Failed to contact
accountsservice: Error calling StartServiceByName for
org.freedesktop.Accounts: GDBus.Error:org.freed
Apr 11 07:56:44 ladyhobbes.localdomain kernel: traps: gdm-simple-slav[863]
trap int3 ip:7f4e822604e9 sp:7fff0619c650 error:0
Apr 11 07:56:45 ladyhobbes.localdomain abrt-hook-ccpp[1110]: Saved core
dump of pid 863 (/usr/libexec/gdm-simple-slave) to
/var/tmp/abrt/ccpp-2014-04-11-07:56:44-863 (2
Apr 11 07:56:45 ladyhobbes.localdomain systemd[1]: Received SIGRTMIN+21
from PID 226 (plymouthd).
Apr 11 07:56:45 ladyhobbes.localdomain dbus-daemon[723]: dbus[723]:
[system] Rejected send message, 1 matched rules; type="method_call",
sender=":1.4" (uid=0 pid=727 co
Apr 11 07:56:45 ladyhobbes.localdomain dbus-daemon[723]: dbus[723]:
[system] Activating systemd to hand-off: service
name='org.freedesktop.Accounts' unit='accounts-daem
Apr 11 07:56:45 ladyhobbes.localdomain dbus[723]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.4" (uid=0 pid=727
comm="/usr/sbin/gdm
Apr 11 07:56:45 ladyhobbes.localdomain dbus[723]: [system] Activating
systemd to hand-off: service name='org.freedesktop.Accounts'
unit='accounts-daemon.service'
Apr 11 07:56:45 ladyhobbes.localdomain gdm[727]: Child process 1119 was
already dead.
Apr 11 07:56:45 ladyhobbes.localdomain gdm[727]: GLib-GObject:
g_object_ref: assertion 'object->ref_count > 0' failed
Apr 11 07:56:45 ladyhobbes.localdomain gdm[727]: GLib-GObject:
g_object_unref: assertion 'object->ref_count > 0' failed
Apr 11 07:56:45 ladyhobbes.localdomain gdm[727]: GdmDisplay: display lasted
0.345361 seconds
Apr 11 07:56:45 ladyhobbes.localdomain systemd[1]: Started Wait for
Plymouth Boot Screen to Quit.
Apr 11 07:56:45 ladyhobbes.localdomain dbus-daemon[723]: dbus[723]:
[system] Rejected send message, 1 matched rules; type="method_call",
sender=":1.4" (uid=0 pid=727 co
Apr 11 07:56:45 ladyhobbes.localdomain dbus[723]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.4" (uid=0 pid=727
comm="/usr/sbin/gdm
Any pointers?
Thanks,
Richard
10 years