Export Pictures to Picasa, Flickr,SmugMug,23hq,web album with Ubuntu


I have searched all over the web for an application/hack to do this and I finally found something since google's picasa doesnt do it yet which is sad...

Download F-Spot Here
open a terminal where you downloaded f-spot
apt-get install sqlite
dpkg -i f-spot*.deb
Then go to Applications-> Graphics-> F-Spot Photo Manager
Click on import to import your pictures, and select the picture album location.
Then once its done importing, you can then export pictures.

First to do this you must select the pictures you want exported by holding in ctrl and selecting the pictures with your mouse.

Then click File-> Export-> PicasaWeb...

Click Add next to gallery, and enter your picasa/google username and password.
Click OK

Now you can add album's, and export the photo's you selected, you can make them public or private when you click ok to export

Expand full post here...

Comments

Make your WPA Uncrackable and Unhackable On Ubuntu or any OS

I have known about this page for quite a while now, I think I decided not to share it because I hack peoples wep/wpa networks lol.. But anyways this site generates completely random Ultra High Security passwords that are generated just for you, the site never gives the same password twice and uses some extremely advanced scrambling technology to generate these passphrases.

Wep is easily crackable but if you use a stronger/longer password it may take longer to crack.

As for WPA, using an ultra secure password is pretty much uncrackable to my knowledge.

"Every time this page is displayed, our server generates a unique set of custom, high quality, cryptographic-strength password strings which are safe for you to use:"

Here is a c/p from the site
What makes these perfect and safe?

Every one is completely random (maximum entropy) without any pattern, and the cryptographically-strong pseudo random number generator we use guarantees that no similar strings will ever be produced again.

Also, because this page will only allow itself to be displayed over a snoop-proof and proxy-proof high-security SSL connection, and it is marked as having expired back in 1999, this page which was custom generated just now for you will not be cached or visible to anyone else.

Therefore, these password strings are just for you. No one else can ever see them or get them. You may safely take these strings as they are, or use chunks from several to build your own if you prefer, or do whatever you want with them. Each set displayed are totally, uniquely yours — forever.

The "Application Notes" section below discusses various aspects of using these random passwords for locking down wireless WEP and WPA networks, for use as VPN shared secrets, as well as for other purposes.

The "Techie Details" section at the end describes exactly how these super-strong maximum-entropy passwords are generated (to satisfy the uber-geek inside you).

Generate your Ultra Secure Password Here

Expand full post here...

Comments

Dell releases custom Ubuntu 7.04 ISOs with drivers and fixes

Dell has released a custom "remastered" Ubuntu 7.04 installation CD ISO that can be used to install Ubuntu on an Inspiron 1420 or 530. The ISO automatically installs all of the drivers and fixes that are required to make Ubuntu fully functional on those systems.

Dell laptops with Ubuntu preinstalled currently ship with a regular Ubuntu 7.04 installation CD that can be used to reinstall the operating system from scratch after reformatting. Unfortunately, the default Ubuntu installation does not include the best drivers so dell has a new remastered custom ubuntu cd just for you.

The "remastered" installation ISO could also be used by Inspiron 1420 and 530 owners who didn't buy their laptops with Ubuntu preinstalled, but wish to install it themselves...

Dell Remastered Ubuntu 7.04 ISO

Dell Linux Engineering team has a remastered copy of the Ubuntu 7.04 Live CD available for download. It includes native system hardware support and many of the fixes listed below. The media will help you get the system installed and running with the necessary drivers.

The media has been created specifically to resolve issues on the following system:

  • Inspiron E1505N
  • Inspiron 1420N
  • Inspiron 530N

Download Dell Ubuntu Image

DISCLAIMER: These images are both unofficial Dell recovery media. They are not officially Dell-supported. Do not call Dell Technical support with questions about this image, or software installed by this image, as they will not be able to help you. To get help, please send an email to the Dell linux-desktops mailing list.

  • Latest Dell Install DVD Image
  • Latest Dell Install CD Image


NOTE: After installation, be sure to update to the latest system software.


NOTE: The CD image has been modified to remove components such as OpenOffice to make room for additional Dell specific drivers and fixes.



Expand full post here...

Comments

Ubuntu VS Fedora on Google Trends

ubuntu fedora
It seems fedora is loosing popularity and Ubuntu is rapidly gaining popularity, although fedora has been around and has a bit of seniority since it is sponsored by Red Hat Linux. I used to run Red Hat Linux and I loved it, although Ubuntu's Simplicity, configurability, stability, speed, and ease of use completely got me. It takes me 25 minutes to completely reinstall Ubuntu and have all my applications restored via AptOnCD. Ubuntu is also headed by a very Intelligent & Inspiring Person, Mark Shuttleworth
Ubuntu has great leadership and a great community, I hope everyone gets to be a part of it someday.

Expand full post here...

Comments

Ubuntu VS PcLinuxOS on Google Trends


pclinuxos ubuntu

I really dont see why distrowatch.org is reporting that PCLinuxOS is more popular, id think the worlds top search engine stats should be actively on Distrowatch.org instead of their pathetic rating system, check out these stats!

Expand full post here...

Comments

Tweak Ubuntu Boot Processes & Runlevels

I personally like gui tools but I also tweak my bootable applications via the command line.
Here is what I use:

Command line tools:

rcconf - This tool configures system services in connection with system

This is my favorite cmd-line app

sysv-rc-conf - sysv-rc-conf provides a terminal GUI for managing "/etc/rc{runlevel}.d/"
symlinks. The interface comes in two different flavors, one that simply
allows turning services on or off and another that allows for more fine tuned
management of the symlinks. Unlike most runlevel config programs, you can
edit startup scripts for any runlevel, not just your current one.
runlevels. It turns on/off services using the scripts in
/etc/init.d/. Rcconf works with System-V style runlevel configuration.
It is a TUI(Text User Interface) frontend to the update-rc.d command.

GUI Tools:

bum - Boot-Up Manager is a graphical tool to allow easy configuration
of init services in user and system runlevels, as far as changing
Start/Stop services priority.
This baby kicks ass


services-admin - The standard services administration tool for ubuntu
A small known fact about this application is that you can rightclick on the service and change the run-level's

You can simply grab these tools via sudo apt-get install application-listed-above

Here is a quick explaination on Ubuntu & Linux runlevels that effect applications that boot:

Linux run levels are numbered 0 through 6. Run levels stop at six for practical and historical reasons, but it is entirely possible to have more if desired.

The following table summarizes the User Linux run levels:

* 0 System Halt
* 1 Single user
* 2 Full multi-user mode (Default)
* 3-5 Same as 2
* 6 System Reboot

Special Run Levels

Run level 0 is the system halt condition. Nearly all modern X86 computers will power off automatically when run level 0 is reached. Older X86 computers, and various different architectures will remain powered on and display a message referring to the halt condition.

Run Level 1 is known as ’single user’ mode. A more apt description would be ‘rescue’, or ‘trouble-shooting’ mode. In run level 1, no daemons (services) are started. Hopefully single user mode will allow you to fix whatever made the transition to rescue mode necessary.

(You can boot into single user mode typically by using your boot loader, lilo or grub, to add the word ’single’ to the end of the kernel command line).

Run levels 2 through 5 are full multi-user mode and are the same in a default User Linux (Debian) system. It is a common practice in other Linux distributions to use run level 3 for a text console login and run level 5 for a graphical login.

Run level 6 is used to signal system reboot. This is just like run level 0 except a reboot is issued at the end of the sequence instead of a power off.

In the interests of completeness, there is also a runlevel ‘S’ that the system uses on it’s way to another runlevel. Read the man page for the init command (”For manpage click here”) for more information, but you can safely skip this for all practical purposes.

Run Levels Location

Like everything else in a Linux system, run levels are defined by files in the file system. All the run level files are found in the /etc directory according to the following table:

/etc/rc0.d Run level 0
/etc/rc1.d Run level 1
/etc/rc2.d Run level 2
/etc/rc3.d Run level 3
/etc/rc4.d Run level 4
/etc/rc5.d Run level 5
/etc/rc6.d Run level 6

Each defined run level should have an rcX.d directory where X is the run level number. The contents of the rcX.d directory determines what happens at that run level.

Change run levels in Debian and Ubuntu Linux

Before we change run levels it might help to find out which run level is current. Use the ‘runlevel’ command to tell you two things: The last run level, and the current run level. Here is the command and the output shown together due to the sparsity of the output:

# runlevel N 2

The ‘N’ stands for none, meaning there has been no run level change since powering up.

The init system controls run levels, but then again, the init system pretty much controls everything. The init system will be looked at in detail in a future article.

The primary command used to change run levels is ‘telinit’.

#telinit 3

telinit takes one argument on the command line. As always, see the man page for full details. Normally the argument will be one of: 0,1,2,3,4,5,6, or the letter ‘S’. As you may have guessed, the numbers correspond to the run level you wish to move to. Using the ‘S’, for single-user, is the same as the number 1, but don’t do it; the ‘S’ runlevel is intended for use by the UserLinux (Debian)system.

A note of caution is warranted here. You can easily use the telinit command to reboot (run level 6), or shutdown (run level 0) the system, but it is not recommended. Certain programs need special processing for an orderly shutdown. Bypassing the expected shutdown sequence can have dire effects on your data. Older _Unix_ systems are especially sensitive to shutdown/bootup operations.

The preferred method for a serious runlevel change is ’shutdown’. There are easier mnemonics, but in a running system they all point to the ’shutdown’ command. You can use the ‘halt’, or ‘poweroff’ command to stop a system and the ‘reboot’ command to restart your system. In each case they call the ’shutdown’ command with different parameters.

If you wanted runlevel 3 to be the default, then you need to edit /etc/inittab.

# The default runlevel.

id:2:initdefault:

You’d change the ‘2′ to a ‘3′. Next time you reboot, your system will start in runlevel 3. There will be no display manager running in runlevel 3, because you turned it off. Therefore, runlevel 3 will become text only, and it will be the default. If that’s what you want to do.

Adding a new service

You can only add a new service to the boot sequence if a script in /etc/init.d exists. In that case the following command will install it with default settings (foo being the name of a script in /etc/init.d).

#update-rc.d foo default

Removing a service

A service may only be removed after the script in /etc/init.d as deleted already. If so, the following command will remove its references (foo being the name of a script in /etc/init.d).

#update-rc.d foo remove

If you want to remove a service without removing the start/stop script as well, you may consider using the file-rc package and editing the runlevel configuration file /etc/runlevel.conf. When using the SysV method you should rename the start/stop script, then call update-rc.d and then rename the start/stop script back to its old name.

Some of the content for this article source from here


Expand full post here...

Comments

Clean up Ubuntu Junk Files!

If your like me and like to do a bit of spring cleaning, or daily cleaning if your a tweak a-holic, these tips will help you clean up your ubuntu installation, enjoy.
Tip #1 - Getting rid of Residual Config packages

In Synaptic Package Manger, there is a built-in feature that gets rid of old Residual Config packages. Residual Config packages are usually dependency packages that are left behind after you uninstall a package from your machine. To use this feature, go to System > Administration > Synaptic Package Manager. On the bottom left hand corner of the window, click the Status button. In the list above the Sections, Status, Search, and Custom buttons, you should see the following text:

Quote:
Installed
Installed (local or obsolete)
Not installed
Residual config
Click on the "Residual config" text. (If the "Residual config dialogue does not appear, that means you do not have any Residual Config packages on your machine and you can skip down to Tip #2.) Do you see the packages that popped up in the window on the right? Those are the Residual Config packages. To get rid of these pests, click on the box to the left of the package name and select "Mark for Complete Removal". After you have done that for all of the Residual Config packages, look at the top of the Synaptic Package Manger window. Do you see the green check mark with the text "Apply" right under it? Click that button, and you'll flush all those Residual Config packages down the toilet!

Tip #2 - Getting rid of partial packages
This is yet another built-in feature, but this time it is not used in Synaptic Package Manager. It is used in the Terminal. To access the Terminal, go to Applications > Accessories > Terminal. Now, in the Terminal, key in the following command (or you can just copy and paste from here):

sudo apt-get autoclean


Enter your password when prompted and press Enter. See the package names that appeared in the Terminal? Those were partial packages that have just been deleted. Say goodbye! That's it! This command deletes the not-so-fully-downloaded packages that you acquire when a package that is being downloaded is suddenly cancelled. This is my favorite little trick when it comes to getting rid of junk files.

Tip #3 - Getting rid of unnecessary locale data
For this tip, you need to download the "localepurge" package found in Synaptic Package Manager. "localepurge" is just a simple script to recover diskspace wasted for unneeded locale files and localized man pages. It will automagically be invoked upon completion of any apt installation run.

To open Synaptic Package Manager, follow the instructions in Tip #1. After opening up Synaptic Package Manager, click the Sections button on the bottom left hand corner of the window, if it is not already clicked. Next, at the top of the Synaptic Package Manager window, click the Search button. In the search window, key in the following text :

localepurge
Did the "localepurge" package popup in the package window? It probably did, unless you do not have the correct Repositories. Now, click on the box next to the "localepurge" package name. Click on Mark for Installation. Now click the Apply button at the top of the window and wait for the downloading and installing of the "localepurge" package to finish. Once it is done, a new window should popup that has a bunch of abbreviations on it. for example:

en
fr
po
sp
ka
etc...
You want to select the abbreviation of the language that you speak, or use with Ubuntu, ignoring the capitalized ones. For example, I speak english, so I would select the "en" abbreviation. A french speaker would select the "fr" abbreviation. So on and so forth... Then click next. All done!

Tip #4 - Getting rid of "orphaned" packages - For this tip, you need to download the "deborphan" package found in Synaptic Package Manager. "deborphan" finds "orphaned" packages on your system. It determines which packages have no other packages depending on their installation, and shows you a list of these packages. It is most useful when finding libraries, but it can be used on packages in all sections...

To open Synaptic Package Manager, follow the instructions in Tip #1. After opening up Synaptic Package Manager, click the Sections button on the bottom left hand corner of the window, if it is not already clicked. Next, at the top of the Synaptic Package Manager window, click the Search button. In the search window, key in the following text :

Quote:
deborphan
Did the "deborphan" package popup in the package window? It probably did, unless you do not have the correct Repositories. Now, click on the box next to the "deborphan" package name. Click on Mark for Installation. Now click the Apply button at the top of the window and wait for the downloading and installing of the "deborphan" package to finish. Once that is done, open up the Terminal. Instructions for doing that are located in Tip #2. After you have gotten the Terminal open, key in the following command (or copy and paste from here):

Code:
sudo deborphan | xargs sudo apt-get -y remove --purge


Enter your password when prompted and press Enter. See the package names that appeared in the Terminal? Those were orphaned packages that have just been deleted. Say goodbye! This is my second favorite way of dealing with junk files.


Tip #5 - Adding a "Find orphaned packages" to Synaptic Package Manager - This is not really much of a tip on how to get rid of junk files. It's more like adding a "deborphan" shortcut to Synaptic Package Manager so that you don't have to use the Terminal to find "orphaned" packages.

Please note: You must have the "deborphan" package installed or else this will not work.

To start this out, open up Synaptic Package Manager with the instructions from Tip #1. Now, at the top of the Synaptic Package Manager window, click the Settings button, followed by the Filters button. In the Filters window, on the bottom left hand corner, push the New button. You can name the new Filter if you like, but it is not necessary. I named mine "Orphaned". With your new Filter selected, in the "Status" tab on the right, click the Deselect All button. Next, check the "Orphaned" option under the "Other" category. Then click the OK button.

To use this new filter, click the Custom button on the bottom left hand corner of the Synaptic Package Manager window. You should see the following text, or something similiar :

Quote:
Broken
Marked Changes
(Whatever you named your "deborphan" Filter)
Package with Debconf
Search Filter
Click on the "(Whatever you named your "deborphan Filter)" text. Do you see the packages that popped up in the window on the right? Those are the "orphaned" packages. To get rid of these buggers, click on the box to the left of the package name and select "Mark for Complete Removal". After you have done that for all of the "orphaned" packages, look at the top of the Synaptic Package Manger window. Do you see the green check mark with the text "Apply" right under it? Click that button, and you'll get rid of all the "orphaned" packages forever (Probably)!


Expand full post here...

Comments

Clicky Web Analytics