Firefox 6 is out

At Mozilla the trains run on time. The open source group is out with its second rapid release browser today, providing users with improved functionality and performance.

Firefox 6, which is being officially released by Mozilla today, follows Firefox 5, which debuted in July. Both Firefox 5 and 6 are part of Mozilla's new rapid release cycle, which aims to deliver more browser updates with incremental features. Previously Mozilla had released major browser update on a less predictable cycle with long with development cycles of a year or longer in between releases.

While the new rapid release cycle does not present the same volume of new features as the longer release cycles, Mozilla is confident that the process is working.

https://www.mozilla.com/en-US/firefox/new/

Scratchpad, a tool that included in the new Firefox, is intended to make it simple to quickly enter, execute, test and refine JavaScript snippets in Firefox without needing to work in a one-line console for web developer.

Firefox 6 is now available for desktop (Windows, Mac and Linux) and Android users.

Ubuntu Linux: apt-get upgrade invalid content-range header

"The HTTP server sent an invalid Content-Range header (IP: IP Address)"

Sometime you encounter this error, when update your system using sudo apt-get update && sudo apt-get upgrade. This could be caused by some incomplete packages downloaded that still cached in /var/cache/apt/archives/partial.

Open your terminal, go to the particular folder by typing cd /var/cache/apt/archives/partial and remove all the incomplete download packages using sudo rm *, and try again.

Steps To Kill Backgound Process In Unix/Linux)

The background on this:

One of our operation was running a application hosted in Unix and some cron jobs had been scheduled to run periodically, to produce an output file and stored in a fixed directory for some business purposes.

But sometime, operation has to some settings and in order to reflect the new setting, the cron job has to be kill and relaunch. There's no GUI interface for this and operation has to log a ticket to the helpdesk to get it done. But every helpdesk ticket that raise, there's a ticket cost and operation has to pay, in regardless whether it has been resolve at the agree period.

This is what I had came with for that operation, for them to DIY, to kill the scheduled job before relaunch it to reflect the new setting. It should works on  Linux as well.


These are the processes that required.

Process that required to kill a task in unix.

Step one: List the process and get the process ID

ps -ef|grep <username>

Step two: kill the process

kill <Process ID>

It is that simple!.

Permanent Link