Fedora

While looking at the log file on my Raspberry Pi (running Fedora 20 Remix), I noticed that the date/time didn’t look right. # date Mon Jul 21 09:01:18 EDT 2014 # timedatectl Local time: Mon 2014-07-21 08:56:16 EDT Universal time: Mon 2014-07-21 12:56:16 UTC Timezone: n/a (EDT, -0400) NTP enabled: yes NTP synchronized: yes RTC in local TZ: no DST active: yes Last DST change: DST began at Sun 2014-03-09 01:59:59 EST Sun 2014-03-09 03:00:00 EDT Next DST change: DST ends (the clock jumps one hour backwards) at Sun 2014-11-02 01:59:59 EDT Sun 2014-11-02 01:00:00 EST EDT is a North American Eastern Daylight Time, which is 4 hours behind UTC. You can read more about it here. In my case, I prefer the time zone set to AEST (Australian Eastern Standard Time), which is 10 hour ahead of UTC. ...

This is just a quick note to remind myself how to enable or disable services using Systemd. In this example, I’m using denyhosts service. Check if a service is running. # systemctl status denyhosts denyhosts.service - SSH log watcher Loaded: loaded (/usr/lib/systemd/system/denyhosts.service; disabled) Active: inactive (dead) Start a service and verify its running status: # systemctl start denyhosts # systemctl status denyhosts denyhosts.service - SSH log watcher Loaded: loaded (/usr/lib/systemd/system/denyhosts.service; disabled) Active: active (running) since Thu 2014-07-17 01:44:29 EDT; 1min 25s ago Process: 15722 ExecStart=/usr/bin/denyhosts.py --daemon --config=/etc/denyhosts.conf (code=exited, status=0/SUCCESS) Process: 15719 ExecStartPre=/bin/rm -f /run/lock/subsys/denyhosts (code=exited, status=0/SUCCESS) Main PID: 19367 (denyhosts.py) CGroup: /system.slice/denyhosts.service └─19367 /usr/bin/python /usr/bin/denyhosts.py --daemon --config=/etc/denyhosts.conf Jul 17 01:44:29 pidora.local systemd[1]: PID file /run/lock/subsys/denyhosts not readable (yet?) after start. Jul 17 01:44:29 pidora.local systemd[1]: Started SSH log watcher. Check if a denyhosts service is enabled or not: ...

The Eclipse IDE that comes bundle with Android Development Tools (ADT) crashes when run on my laptop running Fedora. The error message which logged to console is: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x0000003cc2270061, pid=9653, tid=140330452297472 # # JRE version: Java(TM) SE Runtime Environment (7.0_55-b13) (build 1.7.0_55-b13) # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.55-b03 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libsoup-2.4.so.1+0x70061] soup_session_feature_detach+0x11 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # Fortunately, there’s a way to fix this problem by opening ‘eclipse.ini’ file, in my case: ...

From the command line: # yum install -y kde-runtime.x86_64 kdm @kde-desktop Optionally, if you want to run KDM instead of GDM: # systemctl disable gdm # systemctl stop gdm # systemctl start kdm Note: This guide should work on Fedora 19 as well; but I haven’t tested it. Source: http://marcofalchi.blogspot.com.au/2013/10/fedora-1920-install-kde-kdm-swith-from.html

Add the following to /etc/yum.repos.d/google-chrome.repo: google-chrome] name=google-chrome - 64-bit baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64 enabled=1 gpgcheck=1 gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub Pick a version, stable, beta or unstable and install with the following command: # yum install google-chrome-stable Ref: http://www.if-not-true-then-false.com/2010/install-google-chrome-with-yum-on-fedora-red-hat-rhel/