esiste però una terza alternativa: la riparazione fai-da-te.

strategie consigliate:

1. provare i software che tentano il restore dei pixel addormentati (es.  jscreenfix )
2. tentare con la pressione per ridistribuire il liquido nelle aree interessate
3. vedi il punto 2 ma in maniera ripetuta (guarda il video per i dettagli)

Post from: blog of { marco siviero DOT org };

come tentare di riparare un pixel danneggiato su un monitor LCD

1. # aptitude install leafnode
2. editare /etc/news/leafnode/config (a fine post vi è un config funzionante, basta un solo server da cui sincronizzare le news)
3. aggiungere in /etc/hosts.allow la classe della vostra LAN in questo formato (premettendo che la Vs. LAN sia una 10.2.1.0/24):
leafnode: 10.2.1.
4. # /etc/init.d/openbsd-inetd restart
5. editare /etc/cron.d/leafnode così:

# Cron entries for Leafnode
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
*/6 * * * * news if [ -x /etc/news/leafnode/do-fetch-news ]; then /etc/news/leafnode/do-fetch-news; fi >/dev/null 2>&1
19 3 * * * news texpire -v >/dev/null 2>&1

6. # mkdir /var/lock/news ; chown news.news /var/lock/news

7. # su news -c  ‘/usr/sbin/fetchnews -v’

8. collegatevi con il vostro client NNTP preferito impostando solo l’indirizzo del server e dopo aver scaricato la lista dei Newsgroups disponibili fate le vostre sottoscrizioni: Leafnode si occuperà di scaricare tutti i messaggi relativi, sincronizzandosi ogni (6) minuti con i vari servers impostati.

file /etc/news/leafnode/config :

## /etc/news/leafnode/config [from http://marcosivieroDOTorg/blog]
## Unread articles will be deleted after this many days if
## you don’t define special expire times. Mandatory.
expire = 65

## This is the NNTP server leafnode fetches its news from.
## You need read and post access to it. Mandatory.
server = NEWS.XXXXXXXXXXXX.COM
##
## All the following parameters are optional
##

## Important and recommended setting:
## Fetch only a few articles when we subscribe a new newsgroup. The
## default is to fetch all articles.
## As leafnode forgets the article numbers of its upstream server when
## a group is marked as uninteresting, and later marked interesting
## again, you may end up downloading ALL articles from the upstream
## in that group. So uncomment and adjust this line:
initialfetch = 3000

## Debugging setting:
##
## This MUST be accompanied by syslog.conf changes!
## ————————————————
## Make sure you’ve also read the TROUBLESHOOTING section in README.
##
## The higher, the more output will be logged – note the debugging
## output is copious in any case, so leave this at 0 for normal use,
## and set to 1, 2 or 3 only for debugging.
# debugmode = 3

## I have free access to my news server. If you don’t have, comment out
## the following two lines and change them accordingly.
##username = USER
##password = PWD

## By default, leafnode only serves connections from addresses in the
## local networks and drops those from outside. An IPv4 address is
## considered local if it is within the networks (IP/netmask) of the local
## interfaces. An IPv6 address is considered local if it is site-local,
## link-local or the loopback address (::1).
##
## You can enable remote access by doing:
## 1. enabling access for single static IPs (or subnetworks) through
## your super server (xinetd, tcpserver) or, if the service is wrapped by
## tcpd, hosts.allow/hosts.deny configuration,
## 2. disabling access for all other hosts (default to deny),
## 3. testing that “deny” works, to avoid abuse of your server,
## 4. uncommenting this option, capitalizing the “strangers” subword and
## setting the value to 42.
##
## WARNING: ENABLING THIS OPTION IS DANGEROUS. YOU AGREE TO BE LIABLE
## FOR ALL ABUSE OF YOUR SERVER WHEN THIS OPTION IS ENABLED.
## IF ANYTHING ABOUT ITEMS 1. TO 3. ABOVE IS UNCLEAR, DO NOT ENABLE THIS!
## IF YOU ARE NOT FAMILIAR WITH ACCESS CONTROL, OR YOUR CLIENTS ARE ON
## DYNAMIC IPS, YOU MUST NOT ENABLE THIS. (You can use other, authenticated,
## methods of access instead, for instance SSH tunnels.)
##
# allowstrangers = 0

## Standard news servers run on port 119, reserved for NNTP, so that’s
## the default port fetchnews wants to connect to. If your ISP’s news
## server (or other “upstream”) does not listen on this standard port,
## you can set the “port” option. Note that it is only relevant for
## fetchnews, for leafnode, set the port in your inetd.conf, xinetd.conf
## file or tcpsvd/tcpserver command line, whatever is relevant for your
## system. Leafnode does not currently support SSL.
## Give “port” a numeric value, example:
# port = 9119

## If you want to guarantee that the stdout/stderr are line buffered
## (GNU libc sets them to full buffering if they are redirected to
## files), then set this:
# linebuffer = 1

## This is another news server which stores some groups that are not
## available on the first one. You can define username, password and port
## for each server separately.
##server = NEWS.YYYYYYY.COM
##nopost = 1
# username = xenu
# password = secret

## This is a news server which does not understand the
## “LIST NEWSGROUP news.group” command. For this reason, we don’t try to
## download newsgroups descriptions when getting new newsgroups. This is
## achieved by putting “nodesc = 1″ somewhere behind the server
## line.
##server = NEWS.ZZZZZZZZZ.COM
##nopost = 1
# nodesc = 1

## Here we have another news server which has a very slow connection. For
## that reason, we wait a full minute before we give up trying to connect.
## The default is 10 seconds.
##server = NEWS.NNNNNNNN.COM
##nopost = 1
# timeout = 60

## Disable the updating of the active file unless specifically requested
## in order to minimise network usage as much as possible. The active
## file can be updated manually with the “-f” option to fetchnews.
# server = even.slower.example.com
# noactive = 1

## And this is a news server you only want to pull news from, but never
## post to. You can also use this as a workaround if you do not have posting
## permission on the server while it still greets you with a 200 code.
## The default is: nopost = 0
# server = lurk-only.example.com
# nopost = 1

## And this is a news server you only want to post to, but never
## fetch messages from. If set, noactive = 1 is also assumed.
## The default is: noread = 0
# server = post-only.example.com
# noread = 1

## And this is a news server with broken XOVER. Forbid XOVER,
## leafnode will use XHDR. XHDR may be slower or faster than XOVER,
## depending how many of the maxlines/minlines, maxbytes, maxage
## and similar options.
## The default is: noxover = 0
# server = post-only.example.com
# noxover = 1

## The post_anygroup parameter affects posting and makes leafnode skip
## the check if the newsgroup is carried by the respective server.
## Use this on servers that allow only posting, but no “GROUP” commands.
## Note: do not enable unless you know you may post to that server, your
## postings might end up in the failed.postings directory otherwise.
# server = post-only.example.com
# post_anygroup = 1

## This shows how a server is configured that only has specific news
## groups. Note that this parameter is a PCRE, not a wildmat! See
## pcre(3), pcrepattern(3) or pcre(7), depending on your PCRE version.
## IMPORTANT: you must run fetchnews -f to make changes to this
## option effective.
# server = cnews.corel.com
# only_groups_pcre = corel\.

## Another option related to and depending on this only_groups_pcre option
## is relevant for posting; if set, ALL groups in a Newsgroups: header
## of a cross-posting will must match before the article is posted to
## the server. If unset, ANY group that match
es allows the post.
# only_groups_match_all = 1

## Non-standard expire times (glob(7) wildcard constructs possible)
#
# groups too big to hold articles 20 days:
# groupexpire comp.os.linux.* = 5
#
# very interesting, hold articles longer:
# groupexpire any.local.newsgroup = 100
#
# archive this group (fetchnews uses the global expire to figure the
# maxage, but texpire will skip it):
# groupexpire my.archived.group = -1

## Never fetch more than this many articles from one group in one run.
## Be careful with this; setting it much below 1000 is probably a bad
## idea.
maxfetch = 1500

## If you want to use leafnode like an offline newsreader (e.g. Forte
## Agent) you can download headers and bodies separately if you set
## delaybody to 1. In this case, fetch will only download the headers
## and only when you select an article, it will download the body.
## This can save a huge amount of bandwith if only few articles are really
## read from groups with lots of postings.
## This feature works not very well with Netscape, though (which is not
## a fault of Leafnode).
# delaybody = 0

## If you have configured delaybody mode and your newsreader doesn’t
## cope with articles changing their numbers but not their Message-ID
## such as Knode, then try setting this switch to 1, which
## will make fetchnews keep the article number.
## You’ll have to switch the article body cache off though in your
## newsreader.
# delaybody_in_situ = 0

## To avoid spam, you can select the maximum number of crosspostings
## that are allowed in incoming postings. Setting this below 5 is
## probably a bad idea. The default is unlimited crossposting.
maxcrosspost = 4

## If you suffer from repeatedly receiving old postings (this happens
## sometimes when an upstream server goes into hiccup mode) you can
## refuse to receive them with the parameter “maxage” which tells the
## maximum allowed age of an article in days. A value of 0 indicates that
## no checking should be performed. The default maxage is 10 days.
## WARNING: maxage can be overridden by expire! See the clamp_maxage
## parameter below.
maxage = 30

## By default, maxage is limited to groupexpire (if applicable) or
## expire (otherwise). On some rare occasions, this limit may be
## undesirable. To avoid this maxage manipulation, uncomment this line:
clamp_maxage = 0

## maxlines will make fetch reject postings that are longer than a certain
## amount of lines.
# maxlines = 100

## minlines will make fetch reject postings that are shorter than a certain
## amount of lines.
# minlines = 2

## maxbytes will make fetch reject postings that are larger
maxbytes = 50000

## timeout_short determines how many days fetch gets a newsgroup which
## has been accidentally opened. The default is two days.
timeout_short = 7

## timeout_long determines how many days fetch will wait before not getting
## an unread newsgroup any more. The default is seven days.
timeout_long = 15

## timeout_active determines how many days fetch will wait before re-reading
## the whole active file. The default is 90 days.
timeout_active = 30

## timeout_client determines how many seconds of inactivity to allow before
## a client is forcibly disconnected. The default is 15 mins (900s). Optional.
timeout_client = 1800

## timeout_fetchnews determines how many seconds fetchnews will wait for
## a server reply before assuming the server has become wedged.
## The default is 5 mins (300s). Optional.
timeout_fetchnews = 180

## timeout_lock determines how long the leafnode programs retry to
## obtain the lock file. The default is 5 seconds.
## Note you can use the LN_LOCK_TIMEOUT environment variable to override
## this.
# timeout_lock = 900

## If you want to have your newsreader score/kill on Xref: lines, you might
## want to uncomment this.
create_all_links = 1

## If you want to filter out certain regular expressions in the header,
## create a “filterfile” (how this is done is explained in the README)
## and set
# filterfile = /etc/leafnode/filters

## Note that filtering usually means HEAD and BODY are downloaded
## separately, so fetchnews has to wait for the packets TWICE to travel
## to the server and back. If you have a fast link with high latencies
## (for example a DSL line with interleaving or a satellite link), it
## may be faster to request header and body in a single command and
## discard the body. Note that the filter applies to the header only in
## either case because PCRE matching is expensive.
##
## If you have one of the high-latency high-throughput links and have
## enough free traffic left or a flat rate (no per-MByte billing), uncomment
## this:
# article_despite_filter = 1

## If your newsreader does not supply a Message-ID for your postings
## Leafnode will supply one, using the hostname of the machine it is
## running on. If this hostname is not suitable, this parameter can be
## used to override it. Do not use a fantasy name, it may interfere with
## the propagation of your messages. Most modern newsreaders do provide
## a Message-ID.
hostname = MYHOSTNAME.SERVER.TLD

## You can also override the From: header address shown in placeholder
## articles. It should be the news administrator’s mail address.
newsadmin = postmaster@MYHOSTNAME.SERVER.TLD

## If in your local Usenet hierarchy, posting unencoded 8-bit data in
## headers is condoned, uncomment this option to allow this. 8-bit data
## in headers is officially illegal, although the header character set
## may change to UTF-8 soon.
# allow_8bit_headers = 1

Post from: blog of { marco siviero DOT org };

[HOW TO] installare Leafnode NNTP Server su Linux Debian 5 (Lenny)

nulla di più semplice:

# fdisk /dev/sdc

Command (m for help): b
Reading disklabel of /dev/sdc1 at sector 64.
BSD disklabel command (m for help): p

8 partitions:
# start end size fstype [fsize bsize cpg]
a: 1* 1959* 1958* 4.2BSD 2048 16384 28552
b: 1959* 2220* 261* swap
c: 1* 91201 91200* unused 0 0
d: 2220* 6136* 3916* 4.2BSD 2048 16384 28552
e: 6136* 91201 85065* 4.2BSD 2048 16384 28552

con fdisk usare l’opzione ‘b’ e poi la classica ‘p’ per vedere le partizioni BSD

ora diamoci un ordine mentale con
# cat /proc/partitions

….
8 33 732572001 sdc1
8 37 15728640 sdc5
8 38 2097152 sdc6
8 39 31457280 sdc7
8 40 683288929 sdc8

e quindi montiamo in read only (il kernel deve essere stato compilato con l’opzione UFS file system support (read only) nel menù Miscellaneous filesystems):

mkdir /mnt/freebsd{1,6,7,8}
mount -t ufs -o ro,ufstype=ufs2,nodev,nosuid /dev/sdc1 /mnt/freebsd1
mount -t ufs -o ro,ufstype=ufs2,nodev,nosuid /dev/sdc6 /mnt/freebsd6
mount -t ufs -o ro,ufstype=ufs2,nodev,nosuid /dev/sdc7 /mnt/freebsd7
mount -t ufs -o ro,ufstype=ufs2,nodev,nosuid /dev/sdc8 /mnt/freebsd8

N.B: /dev/sdc5 (la lettera ‘b‘ dell’output di fdisk) è swap area.

se voleste mettere il tutto dentro /etc/fstab:

/dev/sdc1 /mnt/freebsd1 ufs auto,ro,ufstype=ufs2,nodev,nosuid 0 0
/dev/sdc6 /mnt/freebsd2 ufs auto,ro,ufstype=ufs2,nodev,nosuid 0 0
/dev/sdc7 /mnt/freebsd3 ufs auto,ro,ufstype=ufs2,nodev,nosuid 0 0
/dev/sdc8 /mnt/freebsd4 ufs auto,ro,ufstype=ufs2,nodev,nosuid 0 0

Post from: blog of { marco siviero DOT org };

montare partizioni con filesystem UFS2 (FreeBSD) su Linux

BIsogna procurarsi : un Wii remote, un ricevitore bluetooth, i LEDs infrarossi e alcuni cavi.

costo complessivo: circa 50$ (a fronte di un costo della WII che supera i 250 euro)

io sarei molto interessato, qualcuno ne sa di più? o meglio ancora, ha già provato?

How To Build Your Own Wii In 10 Minutes – video powered by Metacafe

via: blogmond.com

Post from: blog of { marco siviero DOT org };

costruire una WII da un PC / notebook

adesso, senza creare paure inutili, ma tenendo conto anche delle leggi di Murphy è, a mio avviso, opportuno crearsi un backup completo sempre sincronizzato.

valutando tutte le ipotesi e le migliaia di posts in rete sull’argomento, io ho scelto il backup online; in maniera tale che non gravi sui miei stanchi hard disks, e affinchè possa avere anche, ovunque io sia, uno storico completo non solo delle mails ricevute ma anche di quelle inviate.

se pensate sia una cosa complicata da realizzare vi sbagliate: è semplice e veloce.

requisiti:

1. browser Mozilla Firefox
2. account di posta per il backup (io consiglio Yahoo Mail in quanto non ha limiti di storage)

istruzioni:

1. installare il plugin per FIrefox: Greasemonkey
2. installare lo script per Greasemonkey: Gmail Auto BCC (tramite questo script imposteremo una sola volta l’indirizzo dell’ account di backup a cui inviare in BCC (copia carbone nascosta) tutte le mails che invieremo)
3. impostare in Gmail sotto Impostazioni–>Inoltro e POP ‘Inoltra una copia del messaggio‘ qui inserire l’indirizzo della mail di backup e subito sotto impostate ‘Conserva la Posta Gmail in Posta in arrivo‘
4. ricordarsi di installare l’accoppiata Greasemonkey-Auto BCC su tutte le postazioni su cui lavorate (es. casa, ufficio)
5. [OPZIONALE ma raccomandato]: nell’ account di backup crearsi dei filtri, in maniera tale da poter avere separate le mail inviate da quelle ricevute. eventualmente si possono fare altri filtri per dividere le mail spedite da Gmail con identità diversa (quelli in cui si usano le credenziali di un altro account per spedire)

finito: da oggi tutte le mail inviate e ricevute risiederanno su clusters lontani fra loro, in quanto devono per forza essere ubicati in posizioni geografiche differenti, in una parola: ridondanza.

comunque se avete soluzioni migliori scrivete pure…

Post from: blog of { marco siviero DOT org };

fare il backup di gmail su un altro servizio online che comprenda anche tutte le mails spedite