Showing posts with label general. Show all posts
Showing posts with label general. Show all posts

Linus Torvalds ditches KDE 4 for GNOME




Linus Torvalds says he has ditched KDE for good and is now sleeping with its arch rival GNOME. Oh well, rhetoric apart, he says the move over to GNOME happened because in KDE 4, he found it quite bothersome that he couldn't get his Right mouse button to access the right menu he wanted. In short, he ran into usability issues while using KDE 4.0.


In an interview given to Rodney Gedda of "Computer World" - Australia, he had this to say, and I quote :
I used to be a KDE user. I thought KDE 4.0 was such a disaster I switched to GNOME. I hate the fact that my right button doesn't do what I want it to do. But the whole "break everything" model is painful for users and they can choose to use something else.

I realise the reason for the 4.0 release, but I think they did it badly. They did so may changes it was a half-baked release. It may turn out to be the right decision in the end and I will re-try KDE, but I suspect I'm not the only person they lost.

I am sure the GNOME camp must be rejoicing in having won over a high profile Linux user to their side. This when a few years back, Linus Torvalds had gone on record severely criticizing GNOME for over simplifying the user interface.

Linus Torvalds was in Australia to attend the annual linux.conf.au organised by Linux Australia. While he was rather critical of KDE 4 in its current form, he did say it was a good thing for Nokia to release Qt as LGPL. Among other things, he also gives his views on Microsoft Windows 7 advising Microsoft to release sooner and decouple the operating system from the applications. A really interesting interview.



Digg Google Bookmarks reddit Mixx StumbleUpon Technorati Yahoo! Buzz DesignFloat Delicious BlinkList Furl

Features in Linux kernels 2.6.28 and 2.6.29



Linux kernel has in recent times seen numerous advances. And the latest versions of the Linux kernel namely 2.6.28 and 2.6.29 have some fabulous features in-built into them.

Topping over 10 million lines of code, the current day Linux kernel is no push over and is forming a serious threat to its competition.

Some of the features that are there in the more recent Linux kernels are as follows:
  • New file systems - Linux kernel supports a new file system called Ext4. Ext4 supports large number of files of greater size and deeper directory structures. Another file system which is still in experimental mode but is soon going to be a choice for Linux users is the Btrfs file system which competes with ZFS in features.

  • Better memory management for the Linux kernel graphics stack.

  • Boot tracer - This is a feature in built into the new kernels, which will allow the developers to find possible ways in which they can further reduce the time taken for the Linux kernel to completely boot up.

  • Freezer - This new feature helps you to easily migrate your operating system to a new host.

  • Improved virtual memory scalability

  • Disk improvements - Such as better support for solid state devices, improvements for ATA hard disks and so on. For instance, Linux kernel now provides protection against sudden jolts and shocks in ATA hard disks.



Digg Google Bookmarks reddit Mixx StumbleUpon Technorati Yahoo! Buzz DesignFloat Delicious BlinkList Furl

Thunderbird to open links in Firefox



If you use Mozilla Thunderbird with KDE you already know that by default Thunderbird open hyperlinks in konqueror. If konqueror your main browser - this post is not for you ;-) Below you can find way how-to force Thunderbird to open hyperlinks in Firefox.

First thing that we need to do is create shell script:
#!/bin/bash
url="$1"
exec /path/to/firefox "$url"


Save that script to Thunderbird default folder. In my case: ~/.mozilla-thunderbird
Now, make that script executable.

Please close Thunderbird and open file prefs.js in your favorite text editor. You can find that file inside Thunderbird profile directory. For example:

~/.mozilla-thunderbird/XXXXXX.default/prefs.js


Now you need add following strings to the end of prefs.js

user_pref("network.protocol-handler.app.ftp", "~/.mozilla-thunderbird/openlink.sh");
user_pref("network.protocol-handler.app.http", "~/.mozilla-thunderbird/openlink.sh");
user_pref("network.protocol-handler.app.https", "~/.mozilla-thunderbird/openlink.sh");


Where openlink.sh file shell script that we saved before.

Now just start Thunderbird and click to any link. It should always open it in Firefox.

I don’t know why Thunderbird didn’t use system default browser either i dont know why there is no settings about broswer in Thunderbird Preferences. I hope this will be fixed sometime, because way above is not clear and not portable.  Usually same methods called “hack”

Digg Google Bookmarks reddit Mixx StumbleUpon Technorati Yahoo! Buzz DesignFloat Delicious BlinkList Furl

pop3s server using stunnel



it’s not a secret that POP3 (Post Office Protocol) is unsecure protocol. All data, including passwords (!) between POP3 server and PC is going in plain text. POP3, like some other protocols (telnet, ftp, etc) absolutely not resistant to sniffing attacks. Even if you sure that your network or PC is secure you can’t trust your ISP network, that potentially can be compromised. Below you can find how-to secure your POP3 server in few easy steps. This how-to is actual for people who can’t or don’t want to change their POP3 server software, but want be secure.

First, download and install the latest stunnel version. I have use freebsd port of stunnel, but you can also get it on stunnel.org. Next you need generate SSL certificate:
cd /etc/ssl
openssl req -new -x509 -days 9999 \
-nodes -config openssl.cnf -out mail.pem \
-keyout mail.pem


Country Name (2 letter code) [AU]:ISO_Country_Code_Here
State or Province Name (full name) [Some-State]:State
Locality Name (eg, city) []:City
Organization Name (eg, company) [Internet Widgits Pty Ltd]:Org_Name
Organizational Unit Name (eg, section) []:
Common Name (eg, YOUR name) []:your_pop3_server_fqdn (important)
Email Address []:Some_Email


I prefer to use official SSL certificates, because with self-signed certificate e-mail clients always show warning message (that little annoying)

Now we need create config for stunnel. Here is my working config:
cert = /etc/ssl/mail.pem
sslVersion = all
exec = /usr/local/libexec/popa3d
output = /var/log/stunnel.log
ciphers = HIGH
debug = 6
If you have a lot of POP3 accounts it’s better to set sslVersion value to “all” because some old POP3 clients may not understand SSLv3/TLSv1

As last step you need shutdown your pop3 client and start new, secure version. In my case i need to remove pop3 from inetd.conf and add new, pop3s service:
# grep pop3s /etc/inetd.conf
pop3s stream tcp nowait root /usr/local/sbin/stunnel stunnel /etc/mail/stunnel.conf

After that you just need to restart inetd.
From client side in mail client settings must be choosen SSL or TLS connection and port 995 instead of 110. Secure Authentication must be unset, because we don’t really have POP3S server, there is only secure tunnel between PC and POP3 server.

Stay secure!

Digg Google Bookmarks reddit Mixx StumbleUpon Technorati Yahoo! Buzz DesignFloat Delicious BlinkList Furl

KDE4 in -current /testing and other Slackware news



That’s right — KDE version 4.1 is now part of Slackware -current (in the /testing directory), so for everyone who can’t wait to try it out, have a look at it! We’re all (very happily) using it here now, and it has come a long way since the first 4.x release. Congratulations to the KDE team for the fine work (and many thanks to Robby Workman and Heinz Wiesinger for all the help with build scripts and testing for the initial Slackware packaging of KDE4). Have fun!

Also, we recently commissioned Mark from Senile Felines Designs to create a unique alternate Slackware Logo, as we were getting a number of bug reports that the old logo could not be read easily while standing on one’s head. We think he did a great job with it! If you like the new logo, we are selling shirts, stickers and other products with it at the Official Slackware CafePress Store, and if the design proves to be popular we’ll likely have some of these products mass produced for the main Slackware Store. Meanwhile, you can help support the Slackware project, _and_ be the first on your block to show off the new Slackware ambigram logo!

source: http://slackware.com

Digg Google Bookmarks reddit Mixx StumbleUpon Technorati Yahoo! Buzz DesignFloat Delicious BlinkList Furl

Small Laptops vs. Large Laptops



Is portability or performance king when it comes to laptops? Read below to find two Linux geeks’ opposing viewpoints on the matter.

Ever since its inception, the Linux space has been full of contention. From the initial Minix vs. Linux debates to GNOME vs. KDE to distribution holy wars, it seems for any Linux question, people with strong opinions are willing to join the flame fest. In this column, we throw a little fuel on the fire with an article dedicated to promoting two conflicting points of view. This month, Bill Childers and Kyle Rankin tackle an issue near and dear to their hearts—small laptops vs. large laptops.

Kyle: I have always been a fan of small laptops. When I look back, I was probably first inspired by Penny’s computer book on Inspector Gadget. My very first laptop was a Toshiba Libretto 50CT—a 75MHz mini-laptop about the size of a VHS tape (those of you who remember 75MHz computers should also remember what a VHS tape is, and for the rest of you, there’s always Wikipedia). Ever since the Libretto, all of my laptops have had 10.6″ screens or smaller, and that is my personal standard for a small laptop. I just don’t understand the current trend of 15″–17″ Sport Utility Laptops (SULs). Some of these SULs are almost of the size of those luggable computers of yesteryear—so big you have to get a special bag to carry them, and so big that most vendors hesitate to refer to them as laptops and call them notebook computers instead. For me, a true laptop should be extremely portable and should have excellent battery life.

Bill: I used to like small laptops, but then I got better. I had an HP200LX palmtop for a long time—it was the only portable PC I could afford. That thing had an 80186 running at 8MHz and ran on two AA batteries. It had CGA graphics and was the epitome of cool. Then I stepped into the modern era and started getting systems that would let me do actual work. A system with a 15″ or 17″ screen isn’t a luggable unless you’re a little girly-man. It’s a system that’s capable of doing anything from standard office tasks to CAD work to playing the latest and greatest 3-D games—all the power of a desktop PC, except I can hang out on the couch. Or in my hammock. What’s wrong with that?

Kyle: I wouldn’t call what Bill has a “laptop” until he has someone else’s lap beside him. I heard he has a Mac cube too. It’s pretty sad when your desktop is smaller than your laptop.

Bill: Hey, have you seen me lately? It fits on my ever-increasing lap. Let’s see you do any kind of graphics on that single-lung Yugo of a computer. Yeah, that’s what I thought. It’s also nice to have the added heat-generating capacity of the larger laptop in the winter months. Just put a kid by each exhaust fan and no more complaining about being cold. And, no jokes about Star Wars or “exhaust ports”, please. It’s not the Death Star.

Kyle: That’s no laptop, it’s a space station. Sure, he may be able to play video games made in the 21st century, but you should see him deathmatch with me in Quake III. Anyway, when his laptop’s battery runs out a few seconds after booting, he hits the escape latch, and my laptop pops out like a pod full of droids from the Death Star. One advantage to my small laptop is I don’t need a suitcase to carry it around. I use a nice, small vinyl case made for a portable DVD player. Okay, so it looks like a man purse, but it’s small all the same.

Bill: I don’t need a suitcase. It fits in a backpack. Okay, the backpack has an aluminum frame, but that’s just for decoration. Hmm, yours cost the same as mine, yet mine can do twice as much work as yours. Who got the better value? And, I get a workout when carrying it as a bonus. Besides, when a server falls on my bag, the aluminum frame lets my computer just shrug it off like an NFL lineman. What happened when a server fell on your laptop, Kyle?

Kyle: Wow. That was below the belt. Too soon, man, too soon. You don’t have to worry about servers hurting your laptop, because when they fall near it, the laptop’s gravitational pull causes the server to orbit it. You can get an inexpensive tiny laptop too. So what if its specs are the same as your BlackBerry? It can run a Web browser. Don’t get me wrong, I can see some advantages to having Bill’s laptop on my lap, but right now, I’d like to keep my sperm count where it is.

Bill: Hey, that’s not an issue, I’ve had my kids. Plus, I have 4GB of RAM in my system. I may not use all 4GB, but it’s nice to know I have it on tap should I decide that I need it. How much memory can Kyle shoehorn into his dinky box?

Kyle: He needs all 4GB so he can start his mail client. As a mutt user, I guess I just don’t need as much RAM, but that’s for a different Point/Counterpoint column.

Bill: Hey, Gmail doesn’t take any more RAM than Firefox. Besides, I start my mail client only when I need to write a long message or a Linux Journal article. Like you said above, I have a BlackBerry for all other e-mail duty.

Kyle: For me, battery life is the key. I can sit for most of a workday on a single charge. When Bill wants to work from a coffee shop, he definitely needs his power cord. When he wants to work outside, he has to fire up his diesel generator.

Bill: Diesel generator? Hardly. My Precision M90 laptop can run for a little more than an hour on battery. While that’s not your “all day” runtime, it’s plenty of time for me to knock out the work I need to do before hunting for a power outlet.

Kyle: This is ultimately what it comes down to for me: when I have work to do, I don’t want to hunt for an outlet, and when I work on an airplane, I like that I can fully open my laptop on the seat-back tray, even if the person in front of me leans all the way back. Today, you can get a dual-core processor even in mini-notebooks. When you combine that with a solid-state drive, you don’t even have to sacrifice performance to go ultraportable. I want a laptop that fits on my lap, lasts most of the day, yet still has plenty of power for everything I do. These days, a number of laptops fit the bill—even if they don’t fit Bill.

Bill: “Even if they don’t fit Bill?” Wow, man, you said I hit below the belt, yet you bust out a fat joke. My main thing is, I need a system that doesn’t feel like I’d break it if I looked at it wrong. It’s got to have the horsepower to do anything I throw at it and be something I can haul around comfortably. Opening it on an airplane is obviously a non-starter, but I’ve gotten to the point where the last thing on my mind when on an airplane is doing work. Heck, I’m management now. I just fire up my BlackBerry’s media player and put my feet up in business class while the nice flight attendants bring me drinks. You can sit back in coach and “work”, Morlock. The bottom line for our readers is they need to make the decision that works best for them.

Kyle Rankin is a Senior Systems Administrator in the San Francisco Bay Area and the author of a number of books, including Knoppix Hacks and Ubuntu Hacks for O’Reilly Media. He is currently the president of the North Bay Linux Users’ Group.

Bill Childers is an IT Manager in Silicon Valley, where he lives with his wife and two children. He enjoys Linux far too much, and he probably should get more sun from time to time. In his spare time, he does work with the Gilroy Garlic Festival, but he does not smell like garlic.

Digg Google Bookmarks reddit Mixx StumbleUpon Technorati Yahoo! Buzz DesignFloat Delicious BlinkList Furl

System Overview Linux



It’s important to understand how a Linux system is put together before diving into the various configuration aspects. A Linux system is significantly different from a DOS or Windows system (or even a Macintosh), but these sections will help you get acquainted with the layout so that you can easily configure your system to meet your needs.

File System Layout

The first noticeable difference between Slackware Linux and a DOS or Windows system is the filesystem. For starters, we do not use drive letters to denote different partitions. Under Linux, there is one main directory. You can relate this to the C: drive under DOS. Each partition on your system is mounted to a directory on the main directory. It’s kind of like an ever-expanding hard disk.

We call the main directory the root directory, and it’s denoted with a single slash (/). This concept may seem strange, but it actually makes life easy for you when you want to add more space. For example, let’s say you run out of space on the drive that has /home on it. Most people install Slackware and make one big root drive. Well, since a partition can be mounted to any directory, you can simply go to the store and pick up a new hard drive and mount it to /home. You’ve now “grafted” on some more space to your system. And all without having to move many things around.

Below, you will find descriptions of the major top level directories under Slackware.

/bin
Essential user programs are stored here. These represent the bare minimum set of programs required for a user to use the system. Things like the shell and the filesystem commands (ls, cp, and so on) are stored here. The /bin directory usually doesn’t receive modification after installation. If it does, it’s usually in the form of package upgrades that we provide.
/boot
Files that are used by the Linux Loader (LILO). This directory also receives little modification after an installation.
/cdrom
Remember that all drives have to be mounted to a directory on the main root directory? Well, /cdrom is provided as a mount point for your CD-ROM drive.
/dev
Everything in Linux is treated as a file, even hardware devices like serial ports, hard disks, and scanners. In order to access these devices, a special file called a device node has to be present. All device nodes are stored in the /dev directory. You will find this to be true across many UNIX-like operating systems.
/etc
This directory holds system configuration files. Everything from the X Window configuration file, the user database, to the system startup scripts. The system administrator will become quite familiar with this directory over time.
/home
Linux is a multiuser operating system. Each user on the system is given an account and a unique directory for personal files. This directory is called the user’s “home” directory. The /home directory is provided as the default location for user home directories.
/lib
System libraries that are required for basic operation are stored here. The C library, the dynamic loader, the ncurses library, and kernel modules are among the things stored here.
/lost+found
When the system boots, the filesystems are checked for any errors. If errors are detected, the fsck program is run to see if any can be corrected. The corrected parts of the filesystem are written to the /lost+found directory.
/mnt
This directory is provided as a temporary mount point for working on hard disks or removable drives.
/opt
Optional software packages. The idea behind /opt is that each software package installs to /opt/<software package>, which makes it easy to remove later. Slackware distributes some things in /opt (such as KDE in /opt/kde), but you are free to add anything you want to /opt.
/proc
This is a unique directory. It’s not really part of the filesystem, but a virtual filesystem that provides access to kernel information. Various pieces of information that the kernel wants you to know are conveyed to you through “files” in the /proc directory. You can also send information to the kernel through some of these “files”. Try doing cat /proc/cpuinfo.
/root
The system administrator is known as “root” on the system. root’s home directory is kept in /root instead of /home/root. The reason is simple. What if /home was a different partition from / and it could not be mounted? root would naturally want to log in and repair the problem. If his home directory was on the damaged filesystem, it would make it difficult for him to log in.
/sbin
Essential programs that are run by root and during the system bootup process are kept here. Normal users will not run programs in this directory.
/tmp
The temporary storage location. All users have read and write access to this directory.
/usr
This is the big directory on a Linux system. Everything else pretty much goes here, programs, documentation, the kernel source code, and the X Window system. This is the directory to which you will most likely be installing programs.
/var
System log files, cache data, and program lock files are stored here. This is the directory for frequently-changing data.
You should now have a good feel for which directories contain what on the filesystem. The next section will help you find specific files easily, so you don’t have to do it by hand.

Digg Google Bookmarks reddit Mixx StumbleUpon Technorati Yahoo! Buzz DesignFloat Delicious BlinkList Furl

man | System Help



man (short for “manual”) is a traditional form of online documentation in Unix and Linux operating systems. Specially formatted files, “man pages”, are written for most commands and distributed with the software. Running man somecommand will display the man page for (naturally) the command or program somecommand.

Because there are so many of them, man pages are grouped into enumerated sections. This system has been around so long that you will often see commands, programs, and even programming library functions referred to with their man section number. For instance, you might see man(1). This tells you that man is documented in section 1 (user commands); you can specify that you want the section 1 man page for “man” with the command man 1 man. Specifying the section that man should look in is useful in the case of multiple items with the same name.


Table 2-1. Man Page Sections






































SectionContents
Section 1user commands (intro only)
Section 2system calls
Section 3C library calls
Section 4devices (e.g., hd, sd)
Section 5file formats and protocols (e.g., wtmp, /etc/passwd, nfs)
Section 6games (intro only)
Section 7conventions, macro packages, etc. (e.g., nroff, ascii)
Section 8system administration (intro only)


In addition to man(1), there are the commands whatis(1) and apropos(1), whose shared purpose is to make it easier to find information in the man system. whatis gives a very brief description of system commands, somewhat in the style of a pocket command reference. apropos is used to search for a man page containing a given keyword.

See their man pages for details.

The /usr/doc Directory


The source for most packages that we build comes with some sort of documentation. README files, usage instructions, license files… any sort of documentation that comes with the source is included and installed on your system in the /usr/doc directory.

If man pages don’t provide enough information, /usr/doc should be your next stop.


HOWTOs and mini-HOWTOs


It is the true spirit of community that brings you the HOWTO/mini-HOWTO collection. These files are exactly what they sound like– documents describing how to do stuff. If you install the HOWTO collection package, HOWTOs will be installed to /usr/doc/Linux-HOWTOs and the mini-HOWTOs to /usr/doc/Linux-mini-HOWTOs.

Also included in the same package is a collection of FAQs (Frequently Asked Questions lists– with answers) which are installed to the same place.

These files are well worth reading whenever you’re not quite sure how to proceed with something. An amazing range of topics are covered in sometimes surprising detail.


Digg Google Bookmarks reddit Mixx StumbleUpon Technorati Yahoo! Buzz DesignFloat Delicious BlinkList Furl

Open Source and Free Software



Within the Linux community, there are two major ideological movements at work. The Free Software movement, which we’ll get into in a moment, is working toward the goal of making all software free of intellectual property restrictions, which it believes hamper technical improvement and work against the good of the community. The Open Source movement is working toward most of the same goals, but takes a more “pragmatic” approach to them, preferring to base its arguments on the economic and technical merits of making source code freely available, rather than the moral and ethical principles that drive the Free Software Movement.

The Free Software movement is headed up by the Free Software Foundation, which is a fund-raising organization for the GNU project. Free software is more of an ideology. The oft-used expression is “free speech, not free beer”. In essence, free software is an attempt to guarantee certain rights for both users and developers. These freedoms include the freedom to run the program for any reason, the freedom to study and modify the source code, the freedom to redistribute the source, and the freedom to share any modifications you make. In order to guarantee these freedoms, the GNU General Public License (GPL) was created. The GPL, in brief, provides that anyone distributing a compiled program which is licensed under the GPL must also provide source code, and is free to make modifications to the program as long as those modifications are also made available in source code form. This guarantees that once a program is “opened” to the community, it cannot be “closed” except by consent of every author of every piece of code (even the modifications) within it. Most Linux programs are licensed under the GPL.

It is important to note that the GPL does not say anything about price. As odd as it may sound, you can charge for free software. The “free” part is in the liberties you have with the source code, not in the price you pay for the software. (However, once someone has sold you, or even given you, a compiled program licensed under the GPL they are obligated to provide its source code as well.)

At the forefront of the younger Open Source movement, the Open Source Initiative is an organization that solely exists to gain support for open source software. That is, software that has the source code available as well as the ready-to-run program. They do not offer a specific license, but instead they support the various types of open source licenses available.

The idea behind the OSI is to get more companies behind open source by allowing them to write their own open source licenses and have those licenses certified by the Open Source Initiative. Many companies want to release source code, but do not want to use the GPL. Since they cannot radically change the GPL, they are offered the opportunity to provide their own license and have it certified by this organization.

While the Free Software Foundation and the Open Source Initiative work to help each other, they are not the same thing. The Free Software Foundation uses a specific license and provides software under that license. The Open Source Initiative seeks support for all open source licenses, including the one from the Free Software Foundation. The grounds on which each argues for making source code freely available sometimes divides the two movements, but the very fact that two ideologically diverse groups are working toward the same goal lends credence to the efforts of each.

Digg Google Bookmarks reddit Mixx StumbleUpon Technorati Yahoo! Buzz DesignFloat Delicious BlinkList Furl

What is Slackware?



Slackware was the first Linux distribution to achieve widespread use. It was started by Patrick Volkerding in late 1992. He had gotten introduced to Linux when he needed an inexpensive LISP interpreter for a project. At that time, there were very few distributions, so Patrick went with the distribution from Soft Landing Systems (SLS Linux).

However, SLS had some problems, so Patrick started to fix little bugs as he found them. Eventually, he decided to merge all of those fixes into his own distribution for himself and friends. This private distribution quickly gained popularity, and Patrick made it available to the public under the name of Slackware.

Along the way, Patrick added new things to the distribution like a user-friendly installation program based on a menuing system and the concept of package management. This allows users to easily add, remove, or upgrade software packages from their system.

Digg Google Bookmarks reddit Mixx StumbleUpon Technorati Yahoo! Buzz DesignFloat Delicious BlinkList Furl

What is Linux?



Linux was started by Linus Torvalds in 1991 as a personal project. He was looking for a way to run a Unix-based operating system without spending a lot of money. In addition, he wanted to learn the ins-and-outs of the 386 processor. It was released free-of-charge to the public so that anyone could hack on it and make improvements under the GNU General Public License

Today, Linux has grown into a major player in the operating system market. It has been ported to run on a variety of architectures including Compaq’s Alpha, Sun’s SPARC and UltraSPARC, and Motorola’s PowerPC chips (through Apple Macintosh and IBM RS/6000 computers, for example). Linux is now being developed by hundreds (if not thousands) of programmers from all over the world. It runs programs like Sendmail, Apache, and BIND, which is some of the most popular server software on the Internet.

The term “Linux” really only refers to the kernel - the core of the operating system. This part is responsible for controlling your processor, memory, hard drives, and peripherals. That’s all that Linux really does. It controls the operations of your computer and makes sure that all the programs behave. All those programs that make Linux useful are developed by independant groups. The kernel and programs are bundled together by various companies and individuals to make an operating system. We call this a Linux distribution.

Digg Google Bookmarks reddit Mixx StumbleUpon Technorati Yahoo! Buzz DesignFloat Delicious BlinkList Furl

Popular Posts