Tampilkan postingan dengan label Desktop. Tampilkan semua postingan
Tampilkan postingan dengan label Desktop. Tampilkan semua postingan

Selasa, 09 Agustus 2011

Fedora 16 Features With Desktop, Virtualization, Etc

Fedora 16 (codenamed Verne) is set to be released at the end of October while the software string freeze and alpha change deadline just passed this week, with the only alpha release being scheduled to take place in mid-August. Fedora 16 is set to continue in Red Hat's tradition of contributing real innovations to the Linux stack, with some of the new Verne features being talked about in this posting...

Comments (0)Add Comment
You must be logged in to post a comment. Please register if you do not have an account yet.
busy

View the original article here

Desktop Summit 2011: Copyright Assignment, Wayland & Beer


View the original article here

Jumat, 22 Juli 2011

The Linux Desktop: We've Arrived.

Linux Desktop articles are all over the place. I can hardly open up a browser without tripping over one. Most of them are negative whine-fests, complaining that Linux is too hard for new users, or has become too dumbed-down for technical users, or the fonts are ugly, or the next generation desktop environments are too different, or... well I could go on, but I think you get the point.
Comments (0)Add Comment
You must be logged in to post a comment. Please register if you do not have an account yet.
busy

View the original article here

Senin, 04 Juli 2011

Keeping the Desktop Dream Alive: Q&A With Linux Foundation's Jim Zemlin, Part 1

In 2007, Linux was heralded as the desktop of the future. However, the history of Linux on the desktop has been a story of strong support from a relatively small group of diehards but little real impact on the market as a whole. And by last year, there was even talk that the dream of the Linux desktop had been shattered. Why is Linux not doing so well on front-end desktops and on laptops? LinuxInsider sat down with Linux Foundation Executive Director Jim Zemlin for an exclusive interview to get to the bottom of things.


View the original article here

Keeping the Desktop Dream Alive: Q&A With Linux Foundation's Jim Zemlin, Part 2

Where is Linux going? For Part 2 of this interview, LinuxInsider continued speaking with Linux Foundation Executive Director Jim Zemlin to discuss Linux in a wider variety of technology, new programs intended to make it easier for businesses to switch to open source computing, and open source's ability to compete in the consumer mobile space. "A third-party provider could set that up as a service and allow a turnkey approach to creating white-label app stores for all kinds of different devices," he said.


View the original article here

Rabu, 29 Juni 2011

The Linux Kernel Power Problems On Older Desktop Hardware

As mentioned last week, a plethora of Linux power tests are on the way now that we have found an AC power meter with USB interface that works under Linux and we've been able to integrate nicely into the Phoronix Test Suite and its sensor monitoring framework. In this article is one of the first tests that have been completed using this power-measuring device as we monitored the Linux kernel power consumption for an old Intel Pentium 4 and ATI Radeon 9200 system for the past several kernel releases. Even this very old desktop system looks to be affected by the kernel power problems.


View the original article here

Rabu, 22 Juni 2011

Hone Your Desktop Clipboards with Parcellite on Linux

If you're a normal desktop Linux user, it has probably been while since you thought about the X Window System. Modern distros let you configure your video card without ever touching xorg.conf, and by and large the window managers and GUI toolkits just work without getting in your way. But there is still one lingering pain point: the clipboard. Between most user apps, cut, copy and paste work without a hitch, but terminals, text editors like Emacs and Vim, and a few other stragglers refuse to cooperate. If that sounds familiar, consider checking out Parcellite.


Parcellite is a lightweight clipboard manager that sits unobtrusively in the top panel, but smooths over the rough spots of inter-app cut-and-paste behavior. The latest version is 1.0.2, which fixes a few bugs that slipped in after the recent 1.0 stable release. You can get source code packages on the project's download site, but there is a pretty good chance your distribution already packages it. Distro-provided packages might not include the latest release, simply due to how recent it is, however.


Whether or not it is worth installing from source depends on your exact needs. 1.0.x adds a few interesting features over the 0.9 series provided by most distros, such as the ability to search through Parcellite's clipboard history in as-you-type mode, and the ability to reposition where the clipboard history pop-up appears. Neither one of those is core functionality, but your mileage may vary. If you do build from source, Parcellite depends on basic GNOME stack libraries: GTK+, Pango, Cairo, etc.; nothing out of the ordinary.


At the heart of Parcellite's behavior is its ability to synchronize the two distinct X selection methods: the CLIPBOARD selection and the PRIMARY selection. In typical X fashion, the official designations for both are in all caps, so we'll use that format to distinguish them from generic usage of either term.


The PRIMARY selection is whatever is highlighted by the cursor; you often see this functionality when you highlight text in a terminal window using the mouse. Mouse-1 (the left button) starts the selection, Mouse-2 (the right button) ends it, and Mouse-3 (the middle button) inserts the selection. This old relic is still useful today because the keyboard shortcuts Control-C and Control-X are often captured by the shell and mapped to other functions if you type them inside a terminal window, but mouse clicks aren't.


In contrast, the CLIPBOARD selection is what is copied whenever you explicitly give a "copy" command to the current app — generally by Control-C or a button press, but potentially a different key combination. Yes, the world would be simpler if PRIMARY and CLIPBOARD were always the same, but that isn't going to happen any time soon.


You can launch Parcellite from the command line with parcellite —. The current version places a clipboard icon in the GNOME 2 panel's notification area; no word yet on an app-indicator for Unity or a GNOME Shell port. When in use the panel icon is essentially a system-wide clipboard menu: click it and you'll get a history of your copied items (25 entries long, by default), from which you can select whichever suits your fancy. The history is preserved across sessions, which is a nice touch.


Right-click on the icon to open the preferences dialog. The Behavior tab hold the important options. At the top, the "Clipboards" section has three checkboxes: one for "Use Copy" (which makes Parcellite watch CLIPBOARD), one for "Use Primary" (which watches PRIMARY), and one for "Synchronize clipboards (which keeps them in sync with each other). That is the core of the magic, of course, but the other options are worth looking at, too.


You can set how many history items to save — including none, in which case Parcellite just syncs CLIPBOARD and PRIMARY to whichever is most-recently-used — plus alter where the history list pops up (which honestly I have not discovered a use-case for). Another use case entirely is available in the "Miscellaneous" section, where you can have Parcellite copy only URLs to the history. That can be useful if you share a lot of links. Miscellaneous also lets you toggle on the search-as-you-type functionality, which can be good if you like to save a lengthy history.


Finally, the Display tab allows you to tweak a few display settings, such as the sort order (newest-to-oldest or vice versa), how many characters wide to make the history pop-up, and whether to truncate the beginning, middle, or end of selections that are too long.


If all you care about is freeing up the mental energy you used to expend keeping CLIPBOARD and PRIMARY straight in your mind, you're all set. But Parcellite has a few other tricks up its sleeve.


For one thing, despite the fact that the history menu shows you your actual selections, it also makes them all editable. That's not particularly handy if you're cutting and pasting in an email, but when you're writing something complex (code, an article, your new free software license), it can turn the clipboard into a handy saved-block-of-text storage system. Particularly when writing tutorials, I reuse lots of HTML fragments to mark up commands (imagine a long ifup command, littered with and tags). With Parcellite I can write the first one, copy it, then cut down the selection to just the generic portion and re-use it at will.


Parcellite also supports configuring "actions" (i.e., custom commands) that take the clipboard selection as an argument. The simplest example would be an action like wget %s -- the %s variable is replaced by the selection, so whenever you copy a URL, you can bring up Parcellite's actions menu and download it with one click. Users can also write actions to perform search-and-replace, dictionary lookup, or anything else. By default, Control-Alt-A opens the actions menu, but this is configurable.


Another nice touch is that Parcellite is usable from the command line. So if you have to SSH into your machine from a remote location, you can retrieve your clipboard history, or add to it. From a shell, you can type echo "http://some.url.youll/otherwise/forget" | parcellite and the URL will be added to your Parcellite selection history. Type parcellite -c to see your CLIPBOARD history, and parcellite -p to see your PRIMARY history (although naturally they will be the same if you sync them).


If you ask me, Parcellite's ability to unify the two main X selection methods is something that really ought to be built right into GNOME and the other desktop environments; it's just that useful, and I've never had occasion to want the two to be separate. On the other hand, I do use Emacs every day, and I really like having Emacs' slightly-different "kill" and "yank" behavior available when I'm writing. Owing to its heritage, Emacs is one of those programs that, like the terminal, has always exposed the difference between CLIPBOARD and PRIMARY.


You can use Parcellite with Emacs naively to keep the program's kill-ring synchronized with the system-wide clipboard, but if you're a heavy Emacser, you may want some more flexibility. For that, EmacsWiki.org has a nice summary of the copy-and-paste options and how they affect Emacs's interaction with the system clipboard -- and thus, with Parcellite.


Personally, I've never been unlucky enough to have to use Vim, but if that lot does befall you, I would recommend looking at the corresponding page on the Vim wiki for a detailed look at that application's copy and paste behavior. It, like Emacs, has different expectations of CLIPBOARD and PRIMARY, which can lead to conflicts if you're not careful.


These days, most other common applications with sync with Parcellite without incident, but if you do find another one with its own brand of clipboard behavior, be sure to share it. Parcellite is under active development again (after a few years off following the 0.9 series), so your feedback could improve the app and help out some other user at the same time.


View the original article here

Jumat, 03 Juni 2011

The ChromiumPC from Xi3 Is the First Desktop Ready to Run ChromeOS [Hardware]

The ChromiumPC modular computer, first unveiled by Xi3 last year, is ready to ship this summer, with an architecture designed specifically for Chrome.View the original article here

The Perfect Desktop - Linux Mint 11 (Katya)

This tutorial shows how you can set up a Linux Mint 11 (Katya) desktop that is a full-fledged replacement for a Windows desktop, i.e. that has all the software that people need to do the things they do on their Windows desktops. The advantages are clear: you get a secure system without DRM restrictions that works even on old hardware, and the best thing is: all software comes free of charge. Linux Mint 11 is a Linux distribution based on Ubuntu 11.04 that has lots of packages in its repositories (like multimedia codecs, Adobe Flash, Adobe Reader, Skype, Google Earth, etc.) that are relatively hard to install on other distributions; it therefore provides a user-friendly desktop experience even for Linux newbies.


View the original article here

Kamis, 02 Juni 2011

Ubuntu Desktop 8.04 LTS Reaches End of Life

The desktop version of Ubuntu 8.04 LTS has officially reached its end of life. Hardy Heron users are advised to upgrade to a later release to continue receiving updates


View the original article here

Selasa, 31 Mei 2011

How To Upgrade From Fedora 14 To Fedora 15 (Desktop & Server)

This article describes how you can upgrade your Fedora 14 system to Fedora 15. The upgrade procedure works for both desktop and server installations.


I do not issue any guarantee that this will work for you!


The commands in this article must be executed with root privileges. Open a terminal (on a Fedora 14 desktop, go to Applications > System Tools > Terminal) and log in as root, or if you log in with a regular user, type

su


to become root.


Please make sure that the system that you want to upgrade has more than 600 MB of RAM - otherwise the system might hang when it tries to reboot with the following message (leaving you with an unusable system):

Trying to unpack rootfs image as initramfs...


First we must upgrade the rpm package:

yum update rpm


Then we install the latest updates:

yum -y update


Next we clean the yum cache:

yum clean all


If you notice that a new kernel got installed during yum -y update, you should reboot the system now:

reboot


(After the reboot, log in as root again, either directly or with the help of

su


)


Now we come to the upgrade process. We can do this with preupgrade (preupgrade will also take care of your RPMFusion packages).


Install preupgrade...

yum install preupgrade


... and call it like this:

preupgrade


The preupgrade wizard will then start on your desktop. Select Fedora 15 (Lovelock). Afterwards the system is being prepared for the upgrade.


At the end, click on the Reboot Now button.


During the reboot, the upgrade is being performed. This can take quite a long time, so please be patient.


Afterwards, you can log into your new Fedora 15 desktop.


First we must upgrade the rpm package:

yum update rpm


Then we install the latest updates:

yum -y update


Next we clean the yum cache:

yum clean all


If you notice that a new kernel got installed during yum -y update, you should reboot the system now:

reboot


(After the reboot, log in as root again, either directly or with the help of

su


)


Now we come to the upgrade process. We can do this with preupgrade.


Install preupgrade...

yum install preupgrade


... and call it like this:

preupgrade-cli


It will show you a list of releases that you can upgrade to. If all goes well, it should show something like Fedora 15 (Lovelock) in the list:

[root@server1 ~]# preupgrade-cli
Loaded plugins: blacklist, langpacks, whiteout
No plugin match for: rpm-warm-cache
No plugin match for: remove-with-leaves
No plugin match for: auto-update-debuginfo
Adding en_US to language list
Loaded plugins: langpacks, presto, refresh-packagekit
Adding en_US to language list
please give a release to try to pre-upgrade to
valid entries include:
"Fedora 15 (Lovelock)"
[root@server1 ~]#


To upgrade, append the release string to the preupgrade-cli command:

preupgrade-cli "Fedora 15 (Lovelock)"


Preupgrade will also take care of your RPMFusion packages, so all you have to do after preupgrade has finished is to reboot:

reboot


During the reboot, the upgrade is being performed. This can take quite a long time, so please be patient. Afterwards, you can log into your new Fedora 15 server.



View the original article here

Kamis, 26 Mei 2011

How To Upgrade Ubuntu 10.10 (Maverick Meerkat) To 11.04 (Natty Narwhal) (Desktop & Server)

Version 1.0
Author: Falko Timme
Follow me on Twitter
Last edited 04/28/2011


The new Ubuntu 11.04 (Natty Narwhal) has just been released. This guide shows how you can upgrade your Ubuntu 10.10 desktop and server installations to Ubuntu 11.04.


This document comes without warranty of any kind! I do not issue any guarantee that this will work for you!


Start the Update Manager (System > Administration > Update Manager):


The Update Manager should show that a new distribution release (11.04) is available. Click on the Upgrade button to start the distribution upgrade:


 A window with the release notes for 11.04 comes up. Click on Upgrade again:

 The upgrade tool is now being downloaded. Afterwards, type in your password:

 The upgrade is being prepared:

 Click on Start Upgrade to finally begin with the upgrade process:

 The upgrade packages are now being downloaded...

 ... and installed. This can take some time, so please be patient.

 At the end of the upgrade process, you should remove obsolete packages:

 

The system needs to be rebooted to complete the upgrade, therefore click on Restart Now:


 When you log in, Ubuntu 11.04 will by default start the new Unity desktop which requires that your hardware supports 3D acceleration. If it doesn't, you can choose the Ubuntu Classic desktop at the login screen instead:

 After the reboot, you can use your new Ubuntu 11.04 desktop (because I used a virtual machine for this tutorial, the system has no 3D support, that's why you see the Ubuntu Classic desktop in the screenshot below):

 ow To Upgrade Ubuntu 10.10 (Maverick Meerkat) To 11.04 (Natty Narwhal) (Desktop & Server) - Page 2

View the original article here

How To Secure Your Ubuntu 10.10 Desktop With LinOTP 2

This howto will guide you to set up a LinOTP standalone one time password authentication backend on your Linux machine. This enables you to add two factor authentication with one time passwords to your desktop login.

LinOTP is a modular OTP (one time password) solution, that supports many different OTP tokens. LinOTP is written in python, based on pylons and apache. It comes as open source licensed under the AGPLv3. Additional functionalities, maintenance and support can be licensed in an Enterprise Edition.

This howto should run on Ubuntu 10.10 and Debian Squeeze.

You can either download the necessary packages from the LinOTP website or you can add the online repository to your repositories and install them with apt-get.

This Howto will use the second way to install the software.

First you need to add the GPG key, that was used to sign the packages:

wget http://linotp.org/apt/LSE\ LinOTP2\ Packaging\ linotp2@lsexperts.de\ \(0xF86258E5\)\ pub.as
sudo apt-key add http://linotp.org/apt/LSE\ LinOTP2\ Packaging\ linotp2@lsexperts.de\ \(0xF86258E5\)\ pub.asc

Then add the repository to your system:

sudo add-apt-repository "deb http://linotp.org/apt/ubuntu lucid linotp2ce"

Now you can install the LinOTP server, the management client and the PAM module:

sudo apt-get install linotp linotpuseridresolver libpam-linotp linotpadminclientce

When installing the linotp package you are asked several questions:

Do you want to run LinOTP 2 via Apache2? -> Yes
Enter admin password for the new LinOTP admin account. -> think of one
Do you want to create a self signed ceritficate? -> Yes
What SQL database do you want to use for the token database? -> Mysql
database hostname: -> localhost
Name of Token database -> LinOTP2
database user -> linotp2
database users password: -> think of one
Enter MySQL root password
Do you want to create the tables: -> yes

During the installation the encryption key /etc/linotp2/encKey will be created. Be sure to also enter the MySQL root password, so the database will be created, too.

Now you got two possibilities to manage the LinOTP server and OTP tokens. You can either use the command line client linotpadmin.py or the web interface located at

https://localhost/manage

Please note: If you got and "internal server error" take a look at /var/log/apache2/error.log. It could be, that the access rights of the directory /var/log/linotp are not right. Also the whole directory /etc/linotp2 needs to be owned by the user linotp.

LinOTP reads users by so called UserIdResolvers. The APGLv3 version comes with the PasswdUserIdResolver, that can be used to read users from flat files like the /etc/passwd. You can also create a new file that contains the users, as long as you stick to the passwd format.

The Enterprise Edition also provides Resolvers for users located in LDAP and SQL databases.

You may use the management web ui or the command line client to setup your LinOTP server. You need to configure a UserIdResolver and a default realm. You may do this by issuing the following commands:

linotpadm.py --url=https://localhost --admin=admin --command=setresolver --resolver=defaultPW --rtype=FILE --rf_file=/etc/passwd

That reads the users from the /etc/passwd file. You will get a JSON feedback like this:

{ u'status': True,....}

Now you need to add this resolver to your default realm:

linotpadm.py --url=https://localhost --admin=admin --command=setrealm --realm=defrealm --resolver=useridresolver.PasswdIdResolver.IdResolver.defaultPW
linotpadm.py --url=https://localhost --admin=admin --command=setdefaultrealm --realm=defrealm

You can either check it in the web ui or issue the command:

linotpadm.py --url=https://localhost --admin=admin --command=listuser

You should see the list of your users. Now you are ready to assign tokens to your user.

You may want to enroll an OTP token, now. In this example we enroll an motp token (you could also enroll an OATH Token or a Google authenticator) on our mobile phone. Download the app from http://motp.sourceforge.net and install it on your phone. You may initialize the token by entering 0000 as PIN on the phone. An init-secret will be displayed.

linotpadm.py --url=https://localhost --admin=admin --command=inittoken --user=cornelius --type=motp --otpkey=860e2e9bf9d50665 --serial=1 --otppin=1234

This means, that you generated an mOTP token that gets assigned to the user "cornelius". The otpkey is the init-secret that was displayed on your phone. You may choose a serial (serial number) as you like to. The otppin is the PIN you will enter on the phone to generate an otp value.

Optionally you may set an OTP PIN, which is a fixed password part, that you need to enter in front (depending on the parameter PrependPIN) of the OTP value:

linotpadm.py --url=https://localhost --admin=admin --command=set --pin=Password --serial=1

Alternatively you can use the management web interface, to enroll the token.

Now you are ready to generate your first OTP value! Go to the portal site:

https://localhost/auth/index

and enter your username and as password the OTP PIN you set and the otp value you generated with your phone. If you fail to authenticate, you might mistyped the init secret or the time of your phone might be out of sync.

Now we will setup PAM to enable you to authenticate to your desktop. The security module /lib/security/pam_linotp.so was installed to your system. You may now set up otp authentication. We choose to do it modular:

cp /etc/pam.d/common-auth /etc/pam.d/common-linotp

In /etc/pam.d/common-linotp change the line:

auth [success=1 default=ignore] pam_unix.so nullok_secure

to

auth [success=1 default=ignore] pam_linotp.so debug nosslhostnameverify nosslcertverify url=https://localhost/validate/simplecheck realm=defrealm resConf=defaultPW

Please note, that when using "debug" option, many many information - also the password! - will be written to the auth.log.

You may now use the common-linotp in any PAM configuration instead of common-auth, where you like to. I.e. you may change the line in /etc/pam.d/gdm:

@include common-auth

to

@include common-linotp

Now you will need to authenticate with OTP to your Gnome desktop! Note that you will also need to change /etc/pam.d/gnome-screensaver if you also want to unlock the desktop using OTP. You will not be asked for "Password" anymore but for "Your OTP".

If you fail to authenticate you may also take a look into /var/log/auth.log.



View the original article here