Debian, Ubuntu, Linux, Gnu, software libero Ubuntu, Quantal Quetzal, Raring Ringtail, Linux, Ubuntulandia, Giochi tag foto 3 Mandelbulber, grafica, multimedia, Linux, Ubuntulandia Conky, Ubuntu, Linux, Ubuntulandia, Quantal Quetzal, Raring Ringtail Python, Ubuntu, Linux, programmazione Ubuntu 13.04, Raring Ringtail, Canonical, Linux Android, Linux, Ubuntu Internet Explorer, Firefox, Chrome, Safari, internet browsers, Ubuntulandia Linux Mint, distribuzioni, Ubuntulandia

lunedì 25 febbraio 2008

A proposito di Gutsy Gibbon.

* Il 18 Ottobre 2007 è stata rilasciata Ubuntu 7.10.
* Il nome in codice che le è stata data è Gutsy Gibbon ed è il successore di Ubuntu 7.04 Feisty Fawn
* Gutsy sarà supportata per 18 mesi sia per la versioni desktop che per quella server.
* Gli utenti che hanno bisogno di un periodo di aggiornamenti più lungo possono continuare ad usare Ubuntu 6.06 LTS, con aggiornamenti per la sicurezza fino al 2011, piuttosto che fare l'aggiornamento o installare la versione 7.10.
http://questchile.files.wordpress.com/2007/06/ubuntu-gutsy-gibbon.jpg

Come scoprire la versione che state usando

* In Gutsy andate in Sistema -> Amministrazione -> Monitor di sistema -> Tab Sistema

o in tutte le versioni e derivate di Ubuntu usate questo comando:

lsb_release -a

Nuove versioni di Ubuntu

* Ubuntu ha un ciclo di rilascio semestrale
* le nuove release avvengono in Aprile ed in Ottobre
* il prossimo rilascio è programmato per il 24 Aprile 2008 e sarà Ubuntu 8.04 (Hardy Heron) ovvero Gutsy+1.
* Hardy Heron sarà una versione LTS (Supporto a lungo termine) e avrà aggiornamenti di sicurezza per cinque anni per la versione server e di tre anni per la versione desktop.

Se state usando una vecchia versione di Ubuntu, dovreste prendere in considerazione l'aggiornamento a Gutsy. Ci sono stati considerevoli miglioramenti in questa versione, ed il programma di aggiornamento di Gutsy faciliterà la transizione a versioni future. Se invece siete in ambiente operativo o se tutto funziona perfettamente potreste preferire di rimanere con una versione LTS.

  • Dapper è l'ultima versione LTS. Gutsy+1 sarà la prossima versione LTS.

Ubuntu 7.10 Guide e Link

Schermate Ubuntu

Galleria Schermate Ubuntu 7.10

Kubuntu 7.10 Guide e Link

Schermate Kubuntu

Galleria Schermate Kubuntu 7.10

Xubuntu 7.10 Guide e Link

Schermate Xubuntu

Galleria Schermate Xubuntu 7.10

Edubuntu 7.10 Guide e Link

Sito Ufficiale Edubuntu Wikipedia: Edubuntu


Wikipedia: Gobuntu

07/02 - Anche il governo giapponese aderisce allo standard ODF

05/02 - Come masterizzare un file superiore ai 4 GB in Linux con K3b

03/02 - Ubuntu 8.04 Hardy Heron: alpha 3

31/01 - Backup e Restore in Ubuntu, ecco come fare!

25/01 - Hardy Heron Roadmap

22/01 - Restore completa soluzione per il backup in Linux

18/01 - Ripristinare MBR di Windows usando Ubuntu LiveCd

17/01 - 10 piccoli accorgimenti per chi ha installato KDE 4

14/01 - NasBackup, soluzione di backup open source


Universo Linux

18/02 - XFiles tree synchronization and cross validation

15/02 - Tape Oriented Backup is a general driver for making and maintening backups

14/02 - Compiz, rilasciata la nuova versione 0.70

13/02 - Tbackup, un ottimo programma per i backup su nastro

11/02 - Blag, distro Linux basata su Fedora Core



mercoledì 20 febbraio 2008

Rilasciata la nuova versione di ScribeFire

Disponibile per il download la nuova versione 1.4.5 del popolare ScribeFire, l'estensione che permette di inserire i post nel proprio blog evitando di loggarsi ogni volta.

Una volta installata l'estensione apparirà in basso a destra l'icona di un taccuino con una matita. Cliccateci sopra una sola volta e vi aprirà la finestra per inserire i post. Per inserire poi i dati dei vostri blogs cliccate su "Launch account wizard" e seguite la procedura richiesta.

Potete poi importare il testo dai siti web con un semplice drag&drop, formattarlo come più vi aggrada e alla fine pubblicarlo con un clic su "Publish To:".

Nei repository ufficiali di Ubuntu è possibile ancora scaricare la versione 1.4.2

ScribeFire 1.4.5 has been released. It is compatible with Firefox 1.5 through 3.0b3.

This release includes the following improvements:

  • Adds a confirmation dialog before deleting a note (issue #47)
  • Adds a font dropdown to the editor (issue #7)
  • Adds the ability the float an image to the right or left of text. (issue #1) Select "Align..." from the right-click menu, or click one of the new alignment buttons on the editor toolbar after selecting an image.
  • Adds support for Wordpress's "

venerdì 15 febbraio 2008

FEBE (Firefox Environment Backup Extension) permette un ripristino veloce e automatico di tutto quello che si è salvato sotto forma di backup.

Febe (Firefox Environment Backup Extension) è un’estensione che aiuta a fare backup delle estensioni, dei segnalibri, delle impostazioni, dei cookie e dei temi installati in Firefox.

La particolarità di Febe consiste nel ricreare una ad una tutte le estensioni sotto forma di file .xpi, in modo da poter reinstallare velocemente tutti i propri plugin senza doverli cercare e reinstallare ogni volta e su tutti i computer su cui si utilizza Firefox.

Con pochi clic inoltre Febe permette un ripristino veloce e automatico di tutto quello che si è salvato sotto forma di backup.

Febe realizza il backup delle estensioni, temi, bookmarks, preferences, cookies, plugins, history e tanto altro ancora (immagine 1)

febe - 1

Utilizzo:

Posizioniamoci a questo indirizzo, installiamo FEBE e riavviamo Firefox.
Scegliamo le opzii backup (immagine 1), cartella di destinazione del backup (immagine 2) e premiamo OK.

febe - 2

Non resta che installare Firefox e Febe sul computer di destinazione.

Grazie a Firefox Extension Backup Extension invece potrete effettuare il backup di qualsiasi cosa che è all’interno di firefox, come potete vedere dallo screenshot soprastante le opzioni di scelta sono davvero molte.

Ecco come appare la schermata dopo l'aggiornamento alla nuova versione:

Congratulazioni! Firefox Environment Backup Extension è stata appena installata o aggiornata con successo

Se questa è una nuova installazione si dovranno impostare alcune opzioni prima di effettuare un backup accedendo al menu di Firefox Strumenti > FEBE > Opzioni di FEBE. L'unica opzione da impostare assolutamente è la Cartella di destinazione del backup nella scheda Cartelle, ma è possibile prendere visione delle molte altre opzioni disponibili

Se si sta aggiornando da una precedente versione di FEBE, è necessario ripristinare le opzioni predefinite accedendo dal menu di Firefox Strumenti > FEBE > Opzioni di FEBE alla scheda Rilevazione errori > Varie e facendo clic sul pulsante Ripristina le opzioni predefinite

Se è la prima volta che si utilizza FEBE o si incontrano problemi nell'effettuare backup, ecco alcuni link utili di riferimento:

martedì 12 febbraio 2008

Tape backup software per sistemi Linux

Tapeback riga di comando è un software per il backup di diverse parti di un sistema Linux.

Sostiene aggiungendo backup multipli su un unico nastro, oltre che avere in un arco più nastri di backup. Il suo backup è completamente self-contained; no "database" per cui è necessario per ripristinare una copia di backup.

Reindirizza facilmente il punto di ripristino è anche facilmente realizzato senza complessi di editing di file di configurazione o complessi comandi per entrare a linea di comando.

Il pacchetto comprende anche una piccola patch per il kernel per agevolare in tempo reale, l'individuazione di "unità pronto". Questa patch consente a tapeback di rilevare automaticamente quando viene acceso un nastro nel drive (fine del nastro quando viene colpito durante il backup / restore).



Latest news:

Version 0.8 is out finally. Please test it extensively and PLEASE let me know how your testing is going. This version has several bug fixes (including the earlier mentioned broken code regarding tape spanning - all fixed).

This just in - - - Tapeback has had some initial yet successful testing on a DLT-7000, a DLT-8000, and an SDLT-220 drive. Tape spanning has not yet been tested on these drives yet. Stay tuned...

Future plans include giving you the ability to restore a single file in a backup - including multi-tape backups. I also intend to include extensive logging options and hopefully, I will also be able to get tape changer support going.

Tapeback is open source software, licensed for use under the terms of the GNU General Public License (GPL). Tapeback is copyright (c) 2004 by Ron Gage, with portions copyrighted by Kai Makisara (the guy who wrote the Linux Scsi Tape driver and the userspace ST utility).

Tapeback is a general purpose tape backup and restore utility set that supports modern SCSI based tape drives. The tapeback utility set also includes a kernel patch (should work on both recent 2.4 and 2.6 Linux kernels) to facilitate real-time tape load status reporting. Tapeback supports the following features:

* Works with any size tape drive
* Can append backups to existing tapes - no more wasteful 5 gig backups on 40 gig tapes
* Backups can span multiple tapes as needed
* Support for Full, Incremental and Differential backups
* No Database needed for a backup or a restore
* CLI based utility can be run from a rescue CD (quick and easy disaster recovery)
* Minimal user intervention needed during backup and restore
* File system agnostic - should be able to backup/restore any Linux based filesystem
* Easy restore point redirection

What features would YOU like to see in tapeback? What do you consider to be a "must have" in a tape backup/restore solution? Where do you see tapeback meeting (or failing to meet) your needs? Please let me know what you think tapeback needs.

Tapeback is currently known to work on a SCSI-2 DLT-4000 tape drive (it's the only drive I have access to right now). If you have any information about other tape drives that tapeback works on, I would love to hear from you. Please email me your testing results.

For more information about tapeback, please feel free to email the author.

Installing tapeback
Tapeback is easily installed. Unpack the tar archive, change into the tapeback directory, and type "make && make install".

Installing the kernel patches requires that you (obviously) have the kernel source installed on your computer. Change into the base directory for the kernel source and install the patches like so:

cd /usr/src/linux-2.6.6
patch -p0 < /path/to/tapeback/st.patch
patch -p0 < /path/to/tapeback/mtio.patch

Once these patches are installed, go on with rebuilding and installing the new kernel. Reboot the machine to put the newly patched kernel into use.

At this point, tapeback is ready to run.

venerdì 8 febbraio 2008

Anche il governo giapponese aderisce allo standard ODF

Promuovere l'utilizzo degli standard aperti all'interno di ministeri e pubblica amministrazione. È quanto si è impegnato a fare il Governo giapponese, che ha appena varato nuove linee guida tese a migliorare l'interoperabilità dei software utilizzati all'interno degli uffici pubblici.

La nuova policy, cita espressamente Open Document (ODF) come esempio di "standard aperto e internazionalmente riconosciuto". Una citazione non casuale, visto che ODF Alliance ha promesso di collaborare a stretto contatto con il Giappone per estendere l'uso del formato ODF e di OpenOffice.

"In precedenza gli enti pubblici giapponesi sceglievano i prodotti informatici esclusivamente in base alle loro funzionalità. Con il nuovo framework di interoperabilità, che entra in vigore da subito, il Governo darà la preferenza a quei prodotti che aderiscono agli standard aperti, e che sono in grado di interoperare facilmente con gli altri software", si legge in un comunicato diffuso da ODF Alliance. "Il Giappone diventa la prima nazione asiatica a sostenere gli standard aperti come ODF".

La notizia:

Hello, I would like to mention some points from the Japanese PDF.

First of all, Japan has some very strict new laws on how corporations must handle personal information of individuals to protect their privacy. Along with the changes in the Corporation Law recently, these laws mean that virtually all major corporations in Japan have been rewriting their articles of incorporation, employee manuals, IT department guidelines, and so on. It doesn't mean things are more secure, but it does mean they are supposed to be more secure. IIRC if your company handles the personal information on more than 500 people then you have to implement certain procedures. (Anyway I am not attempting to provide authoritative information here.)

There also have been a number of scandals (mainly at big banks) on customer information being leaked. So now all corporations' fundamental articles include words like "leakage" and "falsification" of information as things that must be prevented. Japanese companies usually have their fiscal year begin April 1 which means that just a couple weeks ago, most corporations had their general shareholders meetings (many on the same day, to avoid organized crime from interfering) where things like this got voted on (if they weren't the previous year). ODF and standards haven't been on the plate but maybe they will be next year with this announcement.

Okay, on to the PDF. The PDF includes definitions of many terms including "vendor lockin", "open standards", etc. ODF and XML are mentioned by name. It seems to be well written (though I have not read the whole thing). It would seem to exclude allowing Microsoft's horrible new format as an open format because it mentions in the vendor lockin definition the nonavailability of an API, or the limitation on ability to implement it due to licensing requirements. IANAL but it would seem that the government has the leeway to make sane judgements, even in the case of for example Microsoft taking over the standards process and making OOXML an international standard. That said, Japan is probably Microsoft's best or second best market.

The document also states clearly that open formats are to be preferred, and must be used to promote exchange of information between ministries. The word "saiyou" (adopt, use) is used in the statements that say software that adopts open standards is desirable. It is not clear that this forbids the software to also support closed formats, but the spirit of the document would seem to prefer fully open software/solutions so that data may not be saved in closed formats, as this would hamper free exchange of information and the ability to store/view the documents into perpetuity.

Here is a translation of section 4.2.3 on page 19. I, Matthew Rosin, hereby release this translated text to the world in the public domain but deny responsibility for any mistakes.

---
4.2.3. Policy related to giving priority to open standards

It is desirable for the government and public organizations to secure the mutual interoperability of information systems between administrative organizations and with related private sector and international organizations, in order to pursue efficient administration and to provide highly convenient service. To this end, it is necessary to procure software for which protocols, APIs, etc. that use interfaces that are compatible with open standards, to the extent to which implementation is possible.

The government and public organizations, in order to secure transparency related to policy, fulfill their responsibility for providing explanations, and realize expanded participation by the citizenry, software must be procured, to the extent to which implementation is possible, for which the formats of data and files are compatible with open standards, in order to guarantee for public documents the ease of access and ability to save and browse over the long term.

Mutual interconnection between related organizations, including governmental organs, and the free exchange of data among them, are prerequisites to being able to efficiently provide within appropriate periods services that are are found to be necessary by the citizenry and related organizations. For this reason, it is desirable to select solutions that adopt open standards which do not depend on functions belonging to specific products, and to use such solutions to implement mutual interoperability. This approach will enable flexible response with regard to development, maintenance, and migration to other systems, and will enable the government and public organizations to avoid being locked in to specific products or services, as well as making it easier to secure freedom of procurement into the future.

With regard to making statements of specific demands and requirements on the occasion of procurement of information systems for the government and public organizations, it is desirable that that functions, data formats or methods not be used in principle which are unique to a single system, but rather to perform procurement with priority given to systems that are based on open standards such as those of international standards and Japanese industrial standards.
---

The next section (4.2.4) of the document is called, "Policy related to selection of the most appropriate information systems". It says that to minimize risk, the following points must be weighed:
- Selection of solutions that provide greatest value for least cost
- Avoidance of excessive reliance on products that do not implement mutual interoperability
- Securing of freedom and flexibility with regard to system development, strengthening of system functions, system integration and system migration.

it also emphasizes choosing the most appropriate solution based on the total software life cycle and specifies that the comparisons be made equally regardless of whether the software is, as they say, "open source software" or "commercial software".

I will also briefly mention one more section, 4.3 Policy on move toward open systems (a direct translation would be "Policy on openization").

This section states that it is necessary and desirableto promote open systems in order to abolish reliance on the technology of a single vendor when newly developing or updating information systems, and that the purpose of this is to ensure fair and transparent procurement, high quality systems for appropriate prices, interchangeability of parts, and expansion of choices in procurement through the system life cycle, and ensures the possibility of choosing different parts or vendors in the future. It says that being able to point to a standard is part of how transparency of procurement is achieved.

Finally, it states that when a choice is being made among parts that are judged otherwise equivalent, then in such cases "standard parts" that are compatible with open standards, and for which there are multiple choices available among parts implementing the standard, must be procured with priority over those parts that depart from standards or for which there are not multiple choices available.

There are a couple more interesting points stated in this section. First, it says from now on, all government information systems procurement shall in principle use software based on the specifications of open standards. And second, it states that in principle the right to be able to modify information systems in the future must be obtained to the extent financially possible in order to secure interoperability, and that when deciding between systems that do not differ greatly, then in order to improve manufacturability and interoperability, the candidates shall be analyzed to determine the merits and drawbacks concerning innovativeness of the software technology being used and the development methods used therein.

Hope this helps understanding the document and will tide you over until an official translation is provided (or someone does the whole thing).

mercoledì 6 febbraio 2008

Come masterizzare un file superiore ai 4 Gb in Linux con K3B

Ecco un interessante tutorial su come masterizzare un file superiore ai 4 Gb in Linux con K3B e l'ausilio di un piccolo ma potente tool di backup: Splitpipe.

Ultima versione stabile rilasciata per Splitpipe: 0.4

Download

Ultima versione stabile rilasciata per K3B: 1.0.5

Download

Screenshots

Dark Orbit    300x250


Main Window with Welcome Screen
and the crystal theme from Everaldo (0.12.x)


Simulation of an Audio CD copy (0.12.x)


The Audio CD project can handle many different audio file formats including audio tracks directly dragged from an audio CD (0.12.x)


Main Window with Welcome Screen (0.10)


Data DVD Burn Dialog (0.10)


Showing info of an empty CDR (0.10)


CD Copy Dialog (0.10)


Main Window with really new Welcome Screen
and the crystal theme from Everaldo (cvs)


Main Window with really new Welcome Screen
and the crystal theme from Everaldo (cvs)


K3b Splash screen (0.12.x)


An audio cue file imported into an audio project (0.12.x)


Data DVD Project (0.10)


Audio Project (0.10)


Showing contents of an audio CD with CDDB support (0.10)


Simulating an Audio CD (0.10)


DVD Formatting Dialog (0.10)

k3b is just a front-end to growisofs, mkisofs, cdrecord, and other assorted programs, so it shouldn't have any limitations of its own, but just reflect those of the programs it calls.


It appears that growisofs in turn calls mkisofs, which is what is complaining about the file being too large. Googling appears to confirm that this is a internal limit of mkisofs.

So the trick is to split the file in two, which first doesn't sound very interesting, unless you have the good tool !

The solution: Splitpipe !

To create backups:
tar c /home | splitpipe -s dvd -o 'growisofs -Z /dev/dvd=/dev/stdin'

To restore backups:
joinpipe /dev/dvd | tar xz

It features checksums, making sure that the dvds are read in correct order, and other usefull features.

But it can also be used to backup the entire /home on multiple DVDs.

Splitpipe is a program that allows the output of a program to span multiple volumes. Volumes might be DVD's, CD's, files, entire hard disks or floppies.

A command line says more than a thousand words:

# tar cz /home | splitpipe -s dvd -o 'growisofs -Z /dev/dvd=/dev/stdin'
To restore:
# joinpipe /dev/dvd | tar xz

The two lines above backup /home to one, or more DVDs, prompting the operator to change media once a volume is full. For more, see Examples, or a screenshot.
Features

* Running MD5 checksum
* Detects truncated volumes
* Impervious to trailing garbage (which you get when piping raw data to cdrecord or growisofs)
* Detects improper order of volumes on restore
Allows user to insert proper volume when this happens
* Each session has a UUID, so volumes from other backups are rejected
Allows user to insert proper volume when this happens
* Large and efficient ringbuffer
* Works with cdrecord, growisofs, bare files and floppies
* Simultaneous display of status, messages and output of script

Roadmap

While splitpipe is a useful program already, much more is in the works!
Restarting

The data format (splitpipe(5)) and buffer of splitpipe have been built such that it is possible to restart failed volumes, provided they fail early enough.

This would allow the operated to continue a backup after, for example, inserting a used DVD instead of an empty one.
Parallel backups

Larry McVoy has provided me with a program he wrote (Thanks!), but never released, that supports redundant backups, made in parallel to multiple tapes. It is a lot like splitpipe in fact, except that it writes to tape and not to arbitrary programs.

The redundant algorithm is interesting and might be implemented in splitpipe, but it would only be helpful to those with mutiple output devices.
Sequential output and input with multiple devices

If you have multiple readers or writers, you could make backups less user intensive. To start a restore, for example, place volumes one and two in your two drives, and start joinpipe.

Once a volume is done, joinpipe could then run a program to eject that volume. The operator could then every once in a while walk by and on seeing an ejected volume, insert the next one.

This would save a lot of waiting by the console.

The same could be done on making backups.



Se ti è piaciuto l'articolo , iscriviti al feed cliccando sull'immagine sottostante per tenerti sempre aggiornato sui nuovi contenuti del blog:


Ultimi post pubblicati


Get Chitika | Premium

Universo Linux

Ultimi articoli pubblicati

RSVP (Raccomandati Se Vi Piacciono)

Antipixels & Counters

SIMBA wirepress tua notizia Segnala Feed Andrix Segnala Feed iFeed WebShake – tecnologia Blogstreet - dove il blog è di casaVero Geek iwinuxfeed.altervista.org Add to Technorati Favorites ElencoSiti Aggregatore Il Bloggatore visitor stats Programming Blogs - Blog Catalog Blog Directory Feedelissimo Paperblog : le migliori informazioni in diretta dai blog Notizie Informatiche