Freenode now officially supports SSL connections and SASL certificate authentication on all servers. From the FAQ page:
Accessing freenode Via SSL:
freenode now provides SSL client access on all servers. If your client is not configured to verify SSL certificates, then you can simply connect, with SSL enabled, on port 6697, 7000 or 7070.
This site provides instructions on how to enable secure connections to Freenode with Irssi on Debian.
I recently came into the possession of a Canon EOS 400D (Rebel XTi). I had previously owned compact Canons, and while it was not technically a new camera, the 400D was the first camera that allowed me to tinker with exposure settings to obtain more creative shots.
As this was a hand-me-down present, I wasn’t entirely fussy with what I received. The lens that came with the camera was a Canon EF 28-80mm which probably was included in a camera kit at some point. While it wasn’t the best Canon lens available, I didn’t mind as I was rather new to DSLR photography, and I was more concerned with knowing how to properly handle the camera and lens.
I have watched countless YouTube tutorials on the fundamentals of photography (exposure settings & “rules”), and I was overwhelmingly inspired to create. I took several candid shots around the house, and I was able to produce photos that I feel were far superior to any of the ones I had taken in the past.
From Fedora Wiki - Other repositories:
There are a number of third-party software repositories for Fedora. They typically have more liberal licensing policies and provide software packages that Fedora excludes for various reasons. These software repositories are not officially affiliated or endorsed by the Fedora Project. Use them at your own discretion.
For the RPMFusion repository (a merger of Dribble, FreshRPMs, and rpm.livna.org), as root:
# rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm
For the Adobe repository, which provides both Flash player and Adobe Reader:
# rpm -Uvh http://linuxdownload.adobe.com/adobe-release/adobe-release-i386-1.0-1.noarch.rpm
Finally, for the Skype repository, manually create /etc/yum.repos.d/skype.repo containing:
1 |
|
To obtain unrar for F13: as root, create /etc/yum.repos.d/atrpms.repo with contents:
1 |
|
Then, import the repo’s GPG key:
# rpm --import http://atrpms.net/RPM-GPG-KEY.atrpms
Finally:
# yum update
# yum --enablerepo=atrpms install unrar
To get the codec packages required for mp3 (and other media formats not natively supported by F13,) as root:
# rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
# yum install gstreamer-plugins-bad gstreamer-ffmpeg gstreamer-plugins-ugly -y
To get flash working in F13 (i386), visit the Adobe Flash site, select YUM for Linux, and accept the download.
Then, as root:
# rpm -ivh adobe-release-i386-1.0-1.noarch.rpm
.. and then import the provided GPG key:
# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-adobe-linux
To confirm that yum can now access Adobe RPM packages, check to see if /etc/yum.repos.d/adobe-linux-i386.repo exists, and that it contains:
1 |
|
Then, it’s simply a matter of installing the required packages:
# yum install flash-plugin alsa-plugins-pulseaudio libcurl nspluginwrapper
During yum operation, you’ll notice the error Warning: RPMDB altered outside of yum. This cannot be avoided as we are dealing with third-party packages. To read more about the error, visit James Antill’s blog entry.
NB: Flash in Fedora 13 is still a CPU-hog, though I’ve now found that this applies to Flash in Linux in general. Where Flash in Windows Vista on the same box would use roughly 10-15% CPU time, Fedora would see 50-60% CPU usage. The problem is compounded by multiple flash sources on a single page - such pages employ flash-based advertisements that, without fail, degrade system performance.
If the Grub boot-loader resides on the MBR of any disk other than the first (per BIOS’ detection,) you may encounter a issue where Grub does not refer to the first BIOS-bootable disk as (hd0).
I had to trick Grub into mapping my first SATA drive (detected as (hd1) by Grub) as the first boot device, in order for Windows to boot properly:
1 |
|
In the pursuit of ‘fair’ bandwidth sharing with my housemates (who aren’t making financial contributions to net use,) I’ve implemented the following QOS setup to prioritise my CS:Source traffic over HTTP traffic and other miscellaneous traffic.
Updated: 12 Nov 2012
To avoid having wasted space in embedded gists, make the following changes to `user/themes/k2/style.css`:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
*** system/themes/k2/style.css 2010-06-21 22:15:10.587118909 +0800
--- user/themes/k2/style.css 2010-06-27 21:22:38.248366535 +0800
***************
border: 1px solid #999;
}
+ /*-
+ Github Gists
+ */
+
+ .gist { text-indent:0 !important; }
+ .gist-highlight { line-height: 1.2em !important;}
+
/* Peace and forgiveness */
/* Learn more about the other K2: http://en.wikipedia.org/wiki/K2 */
The default themes in Habari are placed in system/themes/. To make any customizations to a theme, it is often better to create a duplicate copy in user/themes/, and to work from there.
To be able to distinguish between the two versions of a theme in Habari’s theme selector, you need to modify the tag in theme.xml, e.g. with the following changes to themes/k2/theme.xml:
1 |
|