mezzoblue ß Design Theft: Crossing the Line
But the question of theft of design material is an interesting one, because most have different definitions of when a piece of work can be considered a rip-off. How much does it have to look like the original? How much has to be changed for it to be considered a new work? Is it even ethical to start with someone else’s material and create your own work out of it?
A Showcase of Material Found on Peer-to-Peer Networks throughout the World. Here you will find Everything from Raunchy Personal Photos to Confidential Police Reports.
Very interesting to see the kinds of things people are sharing on P2P networks- especially the things they don’t know about!
Slashdot | Stirring The GNOME Fires
An interesting read for Gnome users, and even those who don’t use Gnome but are interested in where it’s going in the future.
XHTML Validator to RSS source : Ben Hammersley
The code for the W3 XHTML validator to RSS widget. The W3C Validator has an option, not too well known, to give its results in XML, and this is based on that.
Free Menu Designs – e-lusion.com
Need a block menu fast!
Below are simple CSS menu designs for you to download and use any way you see fit.
You can download the complete set, or an individual menu by clicking the Download Menu button located on each menu.
Nuclear Elephant: File Sharing Experiment
It has always been my belief that various industries have actually earned more revenue as a direct result of file sharing, and that file sharing works FOR the industry. Recent figures such as the music industry’s latest earnings report have proven this.
Research Says Linux Servers Mostly Hack-Free
According to new research published by Evans Data this week, a significant majority of Linux servers have never been infected with a virus and have never been compromised by a malicious attack.
According to the survey results, of the users that had reported malicious attacks, valid internal users caused 23 percent of them. The stat is something that further serves to highlight that those internal threats, regardless of operating system, are something for IT admins to be vigilant about.
I’ve received several emails wondering how I have incorporated Gallery into WordPress. Well, my Gallery installation is in no way related to my WordPress installation- the only similarity is the design.
Specs:
Gallery v 1.4.3
WordPress v 1.0.2
To accomplish the “integration,” you need to look at your code and figure out where the content on your pages starts and ends.
For instance, say your site is organized like this:
[header]
[menu]
[content]
[footer]
You will have to identify 2 parts:
- The code leading to the start of [content]
- The code that the follows [content]*
*Note that we will NOT be using the side menu in this example, so you will need to delete that code. By not using the menu, the gallery will take up the full area, rather than having a column on the right side. To accomplish this, you will have to modify your stylesheet so that #content expands the full width, rather than leaving room for #menu. More on that later.
Once Gallery is installed, there should be a folder called “html_wrap” which contains several files. We will be using “wrapper.header.default” and “wrapper.footer.default” to wrap our design code around the Gallery code.
If you open “wrapper.header.default” or “wrapper.footer.default” you will see some php code in the file. We will put our design code AFTER all of this, so when you start to add yours in, make sure you press enter a few times after ALL of that code that Gallery has written in that file.
A default install of WordPress should have something like the following on the “index.php” page. Using this as an example, I will show you what to trim out for use in our Gallery’s wrapper files.
Now, for our “wrapper.header.default” file, we need to remove the WordPress parts and keep the basic design skeleton. We need to include everything from the beginning to where our content would normally begin. Here is a trimmed down version of the previous example.
Alright, we have now broken up our code and put them in our correct Gallery files. Next, we need to make a copy of our CSS file. If you are using the default WordPress then yours is probably called wp-layout.css and in your main WordPress folder (the same folder as index.php was). Download that file and save it to your computer as we will be editing the #content section now. Make sure you save the newly edited stylesheet in the folder you have specified the link for in “wrapper.header.default”
In the default file, #content looks something like this:
#content {
margin: 30px 13em 0 3em;
padding-right: 60px;
}
We want to remove the padding on the right side, as well as make the widths on the sides of the content equal. We should now have:
#content {
margin: 30px 3em 0 3em;
}
That should be all of the steps now- trimming the original file, placing the top section in “wrapper.header.default” and the bottom section in “wrapper.footer.default,” and modifying the original stylesheet to stretch it across the page. Let’s see a screenshot of what we’ve got: Original WordPress Index.php and new Gallery following our same design and stylesheet.
If you have any questions, simply leave a comment here or use the contact page to email me.
If you are interested in what each part of the index.php page does in WordPress check out http://weblogtoolscollection.com/b2-img/index.phps
If you are wondering what each part of the css file does in WordPress check out http://blog.nuclearmoose.com/wp-docs/wp-layout-explained.htm
Secure Shell (SSH) and Secure Copy (SCP) are important alternatives to the less secure Telnet and FTP. Because Telnet and FTP do not encrypt their passwords, these programs can become security hazards. SSH will give you an encrypted data stream for remotely logging into your Linux box while SCP will allow you to transfer files in an encrypted environment.
Most distros already have SSH and SCP installed- if for some reason yours does not, check your package manager to install it.
SSH:
First, make sure the SSH daemon is running on your box:
[root@debian:/home/pibby]# pgrep sshd
11623
Note: pgrep looks through the currently running processes and lists the process IDs which matches the selection criteria to stdout. Your process number will be different from mine- we are only concerned with the fact that sshd is running. If you receive no output then you need to start it manually.
To start or stop SSH/sshd in Debian:
[root@debian:/home/pibby]# /etc/init.d/ssh start
Starting OpenBSD Secure Shell server: sshd.
[root@debian:/home/pibby]# /etc/init.d/ssh stop
Stopping OpenBSD Secure Shell server: sshd.
Logging into the Remote Box
The basic form of logging in consists of the command ‘ssh’ and the ‘username’ of a user on the ‘hostaddress’:
[pibby@debian:/home/pibby]$ ssh username@hostaddress
For the purpose of the tutorial I will be using the username ‘user’ on ’192.168.1.100′ (indicating a computer on my home network). The host address could be the IP of the remote computer, a domain name, etc.
[pibby@debian:/home/pibby]$ ssh user@192.168.1.100
In the event that SSH is not running on it’s usual port 22, you can specify the port like this (-p #):
[pibby@debian:/home/pibby]$ ssh -p 8181 user@192.168.1.100
When you first login, you will likely be presented with a message similar to the following:
The authenticity of host ’192.168.1.100 (192.168.1.100)’ can’t be established.
RSA key fingerprint is d2:b2:ce:4a:01:33:e8:47:ca:3d:4d:c5:e5:60:d3:16.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ’192.168.1.100′ (RSA) to the list of known hosts.
user@debian_linux:~$
You are now securely logged onto your Linux box!
SCP:
Unlike FTP, SCP does not allow anonymous downloads. SCP requires a username and password and provides a secure, encrypted environment for transferring files. SCP runs on the same TCP port as SSH, so if SSH is running then SCP will be running as well.
The basic format for copying a file from a remote computer to your computer is:
[pibby@debian:/home/pibby]$ scp username@hostaddress:remotefile localdirectory
[pibby@debian:/home/pibby]$ scp user@192.168.1.100:/home/user/file.txt /home/pibby/files/
If you need to specify a different port (-P #)- notice that a capital P is used in SCP, lowercase in ssh:
[pibby@debian:/home/pibby]$ scp -P 8181 user@192.168.1.100:/home/user/file.txt /home/pibby/files/
The basic format for copying a file to a remote computer from your computer is:
[pibby@debian:/home/pibby]$ scp localfile username@hostaddress:remotedirectory
[pibby@debian:/home/pibby/pictures]$ scp picture.jpg user@192.168.1.100:/home/user/files/
If copying multiple files simply list them all with a space between:
[pibby@debian:/home/pibby/pictures]$ scp picture.jpg picture2.jpg /home/pibby/Desktop/picture3.jpg user@192.168.1.100:/home/user/files/
That’s all there is to it!
Well that concludes my quick tutorial on SSH and SCP. For more information please read the man pages for these programs ‘man ssh’ and ‘man scp’ or check out http://www.linuxquestions.org
Hello! My name is Katie, I'm 27 and from Houston, TX. I am a hardworking and passionate freelance web designer with a degree in eBusiness Web Development who creates clean and professional looking websites of the highest quality. I specialize in standards-based XHTML and CSS web development. The sites I develop are built to be search engine friendly!
You can find me on Twitter at @pibby for my latest updates. I am an avid computer user and my OS of choice is Mac OS X. I am most happy at home with my loving husband, Drew, and our two loud but adorable dogs, Toby and Shelby.
