На главную Инструменты Панель оптимизатора

Новости Реклама у нас Обратная связь

06.09.2017 в 12:01 Старт проекта

Google pr	26.11.2014

Яндекс ТиЦ	25.06.2019
поиск	28.06.2019
каталог	16.01.2018

⚑ Установить информеры апдейтов на сайт

Витрина ссылок[Добавить]

Заработок в интернете без вложений

Анализ сайта

Войти или зарегистрироваться

Забыли пароль?

Главная Инструменты Анализ сайта

Данный инструмент поможет Вам Выполнить анализ сайта по наиболее значимым показателям сайта.

URL	neutrino.es (WHOIS IP, WHOIS DOMAIN)
Заголовок	synaptic fault - mind dumped
Ключевые слова	(нет)
Описание	(нет)
Тэг h1	<a href="http://blog.neutrino.es">synaptic fault</a>
Размер страницы	62.92 Kb
Кодировка	UTF-8
IP сайта	51.38.59.69 Все сайты на IP
Скорость загрузки	15.98 Kb/s
Время загрузки	3.94 sec
Перенаправление	http://blog.neutrino.es/
Внутренние / внешние ссылки	Анализ
Анализ контента страницы	Выполнить
Посетителей за сутки по LI	?
Посетителей за месяц по LI	?
Сервер сайта	ns3118092.ip-51-38-59.eu
Расположение датацентра	?
Сервер	Apache
Хостинг № ❶	👍 Сервис рекомендует!
Стоимость сайта	Узнать стоимость сайта ₽

Постоянная ссылка на страницу

http://hroni.ru/tools/analysis/neutrino.es

Основные показатели сайта[ Скрыть ]

Яндекс ИКС:

Склей домена: Нет

С WWW

Без WWW

Яндекс Ранг: 0 из 6

Яндекс.Каталог: (не описан в каталоге)

Повысить индекс качества сайта (ИКС) регистрируя сайт на форумах

Google PageRank: 0 из 10

Alexa Traffic Rank: ?

Alexa Traffic Rank (график):

Счетчик Live Internet:

Поисковый трафик с Google[ Скрыть ]

Backlink History (Majestic SEO)[ Скрыть ]

Наличие сайта в каталогах[ Скрыть ]

Яндекс Каталог: (Нет)	Посмотреть	DMOZ:	Посмотреть
Google каталог:	Посмотреть	Mail.ru:	Посмотреть
Aport:	Посмотреть	Rambler Top 100:	Посмотреть

Проиндексировано страниц[ Скрыть ]

Яндекс:	Посмотреть	Google:	Посмотреть
Bing:	Посмотреть	Yahoo:	Посмотреть
Rambler:	Посмотреть

Ссылаются на сайт из[ Скрыть ]

Яндекс:	Посмотреть	Сайты из Я-Каталога:	Посмотреть
Яндекс блоги:	Посмотреть	Google:	Посмотреть
Google блоги:	Посмотреть	Yahoo:	Посмотреть
Bing:	Посмотреть	Rambler:	Посмотреть
Яндекс картинки:	Посмотреть	Google картинки:	Посмотреть

Дополнительная информация[ Скрыть ]

В кэше Google:	Посмотреть	В кэше Yandex:	Посмотреть
Похожие сайты в Google:	Посмотреть	История сайта:	Посмотреть
Упоминания в Ответы@Mail.ru:	Посмотреть	Поиск плагиата:	Посмотреть

Дополнительные инструменты[ Скрыть ]

Проверка валидности HTML:	Посмотреть	Проверка валидности CSS:	Посмотреть
Ping\Traceroute\DNS:	Посмотреть	Скорость загрузки страницы:	Посмотреть

Данные страницы[ Скрыть ]

Ответ сервера

Файл robots.txt, размер: 59.19 Kb , проверить на Яндекс.Вебмастер

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US">
<head profile="http://gmpg.org/xfn/11">
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
	<title>synaptic fault - mind dumped</title>
		<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" />
	<link rel="stylesheet" type="text/css" media="all" href="http://blog.neutrino.es/wp-content/themes/neutrino/style.css" />
	<link rel="pingback" href="http://blog.neutrino.es/xmlrpc.php" />
	<link rel="alternate" type="application/rss+xml" title="synaptic fault » Feed" href="http://blog.neutrino.es/feed/" />
<link rel="alternate" type="application/rss+xml" title="synaptic fault » Comments Feed" href="http://blog.neutrino.es/comments/feed/" />
		 
		 
<link rel='stylesheet' id='myshare_style-css'  href='http://blog.neutrino.es/wp-content/plugins/my-share-widget/my-share-widget.css?ver=4.3.1' type='text/css' media='all' />
 
 
 
 
 
<link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://blog.neutrino.es/xmlrpc.php?rsd" />
<link rel="wlwmanifest" type="application/wlwmanifest+xml" href="http://blog.neutrino.es/wp-includes/wlwmanifest.xml" /> 
<meta name="generator" content="WordPress 4.3.1" />
	<link rel="stylesheet" href="http://blog.neutrino.es/wp-content/plugins/jquery-syntax/wp-fixes.css" type="text/css" media="screen" />

unlocking rootfs via ssh login in initramfs
-------------------------------------------

You can unlock your rootfs on bootup from remote, using ssh to log in to the
booting system while it's running with the initramfs mounted.

Setup
-----

For remote unlocking to work, the following packages have to be installed
before building the initramfs: dropbear busybox

The file /etc/initramfs-tools/initramfs.conf holds the configuration options
used when building the initramfs. It should contain BUSYBOX=y (this is set as
the default when the busybox package is installed) to have busybox installed
into the initramfs, and should not contain DROPBEAR=n, which would disable
installation of dropbear to initramfs. If set to DROPBEAR=y, dropbear will
be installed in any case; if DROPBEAR isn't set at all, then dropbear will only
be installed in case of an existing cryptroot setup.

The host keys used for the initramfs are dropbear_dss_host_key and
dropbear_rsa_host_key, both located in/etc/initramfs-tools/etc/dropbear/.
If they do not exist when the initramfs is compiled, they will be created
automatically. Following are the commands to create them manually:

# dropbearkey -t dss -f /etc/initramfs-tools/etc/dropbear/dropbear_dss_host_key
# dropbearkey -t rsa -f /etc/initramfs-tools/etc/dropbear/dropbear_rsa_host_key

As the initramfs will not be encrypted, publickey authentication is assumed.
The key(s) used for that will be taken from
/etc/initramfs-tools/root/.ssh/authorized_keys.
If this file doesn't exist when the initramfs is compiled, it will be created
and /etc/initramfs-tools/root/.ssh/id_rsa.pub will be added to it.
If the latter file doesn't exist either, it will be generated automatically -
you will find the matching private key which you will later need to log in to
the initramfs under /etc/initramfs-tools/root/.ssh/id_rsa (or id_rsa.dropbear
in case you need it in dropbear format). Following are the commands to do the
respective steps manually:

To create a key (in dropbear format):

# dropbearkey -t rsa -f /etc/initramfs-tools/root/.ssh/id_rsa.dropbear

To convert the key from dropbear format to openssh format:

# /usr/lib/dropbear/dropbearconvert dropbear openssh \
	/etc/initramfs-tools/root/.ssh/id_rsa.dropbear \
	/etc/initramfs-tools/root/.ssh/id_rsa

To extract the public key:

# dropbearkey -y -f /etc/initramfs-tools/root/.ssh/id_rsa.dropbear | \
	grep "^ssh-rsa " > /etc/initramfs-tools/root/.ssh/id_rsa.pub

To add the public key to the authorized_keys file:

# cat /etc/initramfs-tools/root/.ssh/id_rsa.pub >> /etc/initramfs-tools/root/.ssh/authorized_keys

In case you want some interface to get configured using dhcp, setting DEVICE= in
/etc/initramfs-tools/initramfs.conf should be sufficient.  The initramfs should
also honour the ip= kernel parameter.
In case you use grub, you probably might want to set it in /boot/grub/menu.lst,
either in the '# kopt=' line or appended to specific 'kernel' line(s).
The ip= kernel parameter is documented in Documentation/nfsroot.txt in the
kernel source tree.

Issues
------

Don't forget to run update-initramfs when you changed the config to make it
effective!

Collecting enough entropy for the ssh daemon sometimes seems to be an issue.
Startup of the ssh daemon might be delayed until enough entropy has been
retrieved. This is non-blocking for the startup process, so when you are at the
console you won't have to wait for the sshd to complete its startup.

Unlocking procedure
-------------------

To unlock from remote, you could do something like this:

# ssh -o "UserKnownHostsFile=~/.ssh/known_hosts.initramfs" \
	-i "~/id_rsa.initramfs" root@initramfshost.example.com \
	"echo -ne \"secret\" >/lib/cryptsetup/passfifo"

This example assumes that you have an extra known_hosts file 
"~/.ssh/known_hosts.initramfs" which holds the cryptroot system's host-key,
that you have a file "~/id_rsa.initramfs" which holds the authorized-key for
the cryptroot system, that the cryptroot system's name is
"initramfshost.example.com", and that the cryptroot passphrase is "secret"

-- <debian@x.ray.net>, Wed, 30 Sep 2009
</pre>
		</div>
			</div>
		<div class="post post-210 type-post status-publish format-standard hentry category-igalia tag-fpga tag-hardware tag-kernel" id="post-210">
		<h2 class="title"><a href="http://blog.neutrino.es/2011/openrisc-making-the-stack-100-free/" title="Permalink to OpenRISC: Making the stack 100% free">OpenRISC: Making the stack 100% free</a></h2>
		<div class="post-info-top">
			<span class="post-info-date">
				Posted on Tuesday, 21st June 2011							</span>
			<span id="gotocomments"><a href="http://blog.neutrino.es/2011/openrisc-making-the-stack-100-free/#comments">1 comment</a></span>
		</div>
		<div class="clear"></div>
		<div class="entry">
			<p><a href="http://en.wikipedia.org/wiki/OpenRISC" target="_blank">OpenRISC</a> is the flagship project of the <a href="http://en.wikipedia.org/wiki/OpenCores" target="_blank">OpenCores</a> community. This project aims to develop a series of general purpose open source RISC CPU architectures.</p>
<p>The OpenRISC 1200 (OR1200) is a <a href="http://en.wikipedia.org/wiki/Soft_microprocessor" target="_blank">synthesizable CPU core</a> that runs on FPGAs from a broad number of vendors, and is currently being used in a number of successful industrial projects. This CPU is an open source implementation (LGPL) of the OpenRISC 1000 RISC architecture.</p>
<p>These days the project has reached an important milestone: <a href="https://lkml.org/lkml/2011/6/19/47" target="_blank">they have submitted their patches for review to the Linux kernel mailing list</a> and hopefully they will get it merged, so Linux will officially support the OpenRISC architecture.</p>
<p>This are exciting news!</p>
<p>If you have a FPGA board you can load it with the <a href="http://opencores.org/or1k/OR1K:Community_Portal#Get_source_code" target="_blank">OpenRISC softcore</a> and execute Linux on it (<a href="http://www.youtube.com/watch?v=2bSOzV--DbU" target="_blank">demo video</a>).</p>
<p>But if you don’t have one, then you can try the nice OpenRISC emulator: its easy and funny.<br />
Here is <a href="http://openrisc.net/toolchain-build.html" target="_blank">a link to the detailed howto</a>, and here is my cheat sheet:</p>
<div class="wp_syntax">
<div class="code">
<pre class="sh" style="font-family: monospace;">
sudo apt-get install build-essential libmpc-dev lzop git-core
sudo apt-get build-dep gcc-4.4
mkdir ~/openrisc
cd ~/openrisc
git clone git://openrisc.net/jonas/or1ksim-svn
cd or1ksim-svn
./configure && make && sudo make install
cd ~/openrisc
git clone git://openrisc.net/jonas/toolchain
cd toolchain
git submodule update --init
# go for a coffee
export PATH=~/openrisc/toolchain/bin:$PATH
make PREFIX=~/openrisc/toolchain
cd linux
make ARCH=openrisc defconfig
make CROSS_COMPILE=or32-linux-
# go for a tea
sim -f arch/openrisc/or1ksim.cfg vmlinux
</pre>
</div>
</div>
<p>And voila! You are running a 100% free system, from the CPU to the Operating System, including the <a href="http://en.wikipedia.org/wiki/Wishbone_%28computer_bus%29" target="_blank">Wishbone bus</a> <img src="http://blog.neutrino.es/wp-includes/images/smilies/simple-smile.png" alt=":)" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
<div class="wp_syntax">
<div class="code">
<pre class="sh" style="font-family: monospace;">
# cat /proc/cpuinfo
cpu                     : OpenRISC-18
revision                : 1
dcache size             : 8192 kB
dcache block size       : 16 bytes
icache size             : 8192 kB
icache block size       : 16 bytes
immu                    : 64 entries, 1 ways
dmmu                    : 64 entries, 1 ways
bogomips                : 40.00
</pre>
</div>
</div>
<p>As the OpenRISC 1000 is now considered stable, the OpenCores project is trying to build a cost-efficient ASIC with this design to get improved performance. They launched <a href="http://opencores.org/donation" target="_blank">a call for donations in 2011</a> with the aim to produce the first ASIC in Q1 2012.</p>
<p>I am willing to get one of this!</p>
<p></p>
<link rel="stylesheet" href="http://people.igalia.com/clopez/quote.css" />
<blockquote><p>The open-source methodology is here to stay, just take a look at the success story behind Linux/Android, and all the great benefits that open-source offers. We now need to take the next step with open-source hardware development, meaning to actually create “true” open-source Semiconductor components in order to stay competitive, and to make sure that smaller companies can compete with large Semiconductor giants. So please join us and help us rewrite the history books for hardware development…</p></blockquote>
		</div>
			</div>
		<div class="post post-157 type-post status-publish format-standard hentry category-igalia tag-hardware tag-power-management tag-usb" id="post-157">
		<h2 class="title"><a href="http://blog.neutrino.es/2011/dont-eject-your-usb-storage-stop-it/" title="Permalink to Don’t eject your USB storage: stop it!">Don’t eject your USB storage: stop it!</a></h2>
		<div class="post-info-top">
			<span class="post-info-date">
				Posted on Wednesday, 9th March 2011							</span>
			<span id="gotocomments"><a href="http://blog.neutrino.es/2011/dont-eject-your-usb-storage-stop-it/#respond">No comments</a></span>
		</div>
		<div class="clear"></div>
		<div class="entry">
			<p>This is probably one of the biggest mistakes I’ve dragged for more time as Linux user, in part for not reading the man pages and in part by assuming too much from the name of an executable.</p>
<p>When working with USB storage I was used to plug it, mount it, do some stuff with it, sync, unmount, <span style="text-decoration: line-through;">eject</span> and unplug it. And seems that <a href="http://linux.die.net/man/1/eject">eject</a> does not apply to USB storage, only to <em>“ejectable”</em> media: <em>CD/DVD/Floppies…</em></p>
<p>So, the right way to stop an USB storage device is to use:</p>
<div class="wp_syntax">
<div class="code">
<pre class="sh" style="font-family: monospace;">sdparm --command=stop /dev/device</pre>
</div>
</div>
<p>Anyway I recommend you to check out the following script that does it very nicely, <a href="http://elliotli.blogspot.com/2009/01/safely-remove-usb-hard-drive-in-linux.html">plus another useful things like unbinding it</a>. The script is here: <a href="https://github.com/liyan/suspend-usb-device"><strong>suspend-usb-device</strong></a></p>
<p>PS: I’m afraid that I was not the only unwary out there that was “ejecting” the USB storage before unplugging it, so I hope you can find this tip useful hehe 😀</p>
		</div>
			</div>
		<div class="post post-137 type-post status-publish format-standard hentry category-igalia tag-applet tag-gnome tag-hardware tag-networking tag-rfkill tag-wireless" id="post-137">
		<h2 class="title"><a href="http://blog.neutrino.es/2011/rfkill-applet-for-gnome/" title="Permalink to RFKill Applet for GNOME">RFKill Applet for GNOME</a></h2>
		<div class="post-info-top">
			<span class="post-info-date">
				Posted on Thursday, 20th January 2011							</span>
			<span id="gotocomments"><a href="http://blog.neutrino.es/2011/rfkill-applet-for-gnome/#comments">1 comment</a></span>
		</div>
		<div class="clear"></div>
		<div class="entry">
			<p>I don’t like to use wireless devices if I can avoid them, I am a bit paranoid with this things and also I have empirically checked that always that I use the wireless of my laptop for a long time I end with headaches. If you are worried about this too I encourage you to watch the documentary <em>“surrounded by waves”</em> (just google it)</p>
<p>And one of the things that I miss on my Asus laptop is that it lacks of a button switch for turning on / off the wireless and bluetooh devices. Months ago I discovered the <a href="http://wireless.kernel.org/en/users/Documentation/rfkill">rfkill</a> utility (package wireless-tools on Debian/Ubuntu) and I loved it. I used to disable or enable the wireless devices from the terminal with this utility, but soon I realized that it was not comfortable to open a terminal and run the commands each time.</p>
<p>So as part of my hackfest time here at <a href="http://www.igalia.com">Igalia</a> I wrote an applet for GNOME that lets the user to disable or enable the emission of radiation from RF devices with a simple click on the applet icon. I took the inspiration for this from the GNOME power manager inhibit applet.</p>
<p>It also polls the system for the status of the RF devices and updates the icon showed, so it works also as a notification applet that will display the <a href="http://gitorious.org/gnome-rfkill-applet/gnome-rfkill-applet/blobs/master/icons/rfkill-applet-a.png">emitting icon</a> if only one of the RF devices of your system is activated and the <a href="http://gitorious.org/gnome-rfkill-applet/gnome-rfkill-applet/blobs/master/icons/rfkill-applet-b.png">inhibited icon</a> if all RF devices are blocked. Finally, if a problem is found or you don’t have RF devices on your system then it will display the <a href="http://gitorious.org/gnome-rfkill-applet/gnome-rfkill-applet/blobs/master/icons/rfkill-applet-c.png">unknown icon</a>.</p>
<p><a href="http://gitorious.org/gnome-rfkill-applet"><img class="aligncenter size-full wp-image-136" title="GNOME RFKill Applet" src="http://blog.neutrino.es/wp-content/uploads/2011/01/gnome-rfkill-applet.jpg" alt="GNOME RFKill Applet" width="458" height="195" /></a></p>
<p>You can get it <a href="http://gitorious.org/gnome-rfkill-applet">from gitorious</a>.</p>
<p>I hope you find it useful 😉</p>
		</div>
			</div>
	<div id="pagination"><a href="http://blog.neutrino.es/page/2/" >Next page »</a></div></div>
<div id="sidebar-border">
	<div id="rss_border">
		<div class="rss_border">
			<div id="rss_wrap">
				<div class="rss_wrap">
										<a class="rss " href="http://blog.neutrino.es/feed/" rel="nofollow" title="RSS Feed">RSS Feed</a>
										<a class="twitter" href="http://twitter.com/#!/cl0p3z" rel="nofollow" title="Follow me on twitter.">Follow me on twitter.</a>
																				<a class="googleplus" href="https://plus.google.com/102582740940760717352" rel="nofollow" title="Google+">Google+</a>
									</div>
			</div>
		</div>
	</div>
	<div id="sidebar">

<div id="qtranslate-3" class="widget widget_qtranslate"><h3 class="widgettitle">Language</h3><ul class="qtrans_language_chooser" id="qtranslate-3-chooser"><li class="lang-en active"><a href="http://blog.neutrino.es/" hreflang="en" title="English"><span>English</span></a></li><li class="lang-es"><a href="http://blog.neutrino.es/es/" hreflang="es" title="Español"><span>Español</span></a></li></ul><div class="qtrans_widget_end"></div></div><div id="tag_cloud-3" class="widget widget_tag_cloud"><h3 class="widgettitle">Tags</h3><div class="tagcloud"><a href='http://blog.neutrino.es/tag/apache/' class='tag-link-16' title='1 topic' style='font-size: 8pt;'>apache</a>
<a href='http://blog.neutrino.es/tag/applet/' class='tag-link-19' title='1 topic' style='font-size: 8pt;'>Applet</a>
<a href='http://blog.neutrino.es/tag/debian/' class='tag-link-32' title='1 topic' style='font-size: 8pt;'>debian</a>
<a href='http://blog.neutrino.es/tag/email/' class='tag-link-9' title='1 topic' style='font-size: 8pt;'>email</a>
<a href='http://blog.neutrino.es/tag/fpga/' class='tag-link-23' title='1 topic' style='font-size: 8pt;'>fpga</a>
<a href='http://blog.neutrino.es/tag/game/' class='tag-link-5' title='1 topic' style='font-size: 8pt;'>game</a>
<a href='http://blog.neutrino.es/tag/git/' class='tag-link-33' title='1 topic' style='font-size: 8pt;'>Git</a>
<a href='http://blog.neutrino.es/tag/gnome/' class='tag-link-17' title='1 topic' style='font-size: 8pt;'>GNOME</a>
<a href='http://blog.neutrino.es/tag/hack/' class='tag-link-4' title='4 topics' style='font-size: 19.666666666667pt;'>hack</a>
<a href='http://blog.neutrino.es/tag/hardware/' class='tag-link-7' title='5 topics' style='font-size: 22pt;'>hardware</a>
<a href='http://blog.neutrino.es/tag/kernel/' class='tag-link-13' title='4 topics' style='font-size: 19.666666666667pt;'>kernel</a>
<a href='http://blog.neutrino.es/tag/linux/' class='tag-link-35' title='2 topics' style='font-size: 13.25pt;'>linux</a>
<a href='http://blog.neutrino.es/tag/meego/' class='tag-link-12' title='1 topic' style='font-size: 8pt;'>meego</a>
<a href='http://blog.neutrino.es/tag/networking/' class='tag-link-8' title='4 topics' style='font-size: 19.666666666667pt;'>networking</a>
<a href='http://blog.neutrino.es/tag/openembedded/' class='tag-link-42' title='1 topic' style='font-size: 8pt;'>OpenEmbedded</a>
<a href='http://blog.neutrino.es/tag/packages/' class='tag-link-14' title='1 topic' style='font-size: 8pt;'>packages</a>
<a href='http://blog.neutrino.es/tag/performance/' class='tag-link-41' title='1 topic' style='font-size: 8pt;'>performance</a>
<a href='http://blog.neutrino.es/tag/power-management/' class='tag-link-22' title='1 topic' style='font-size: 8pt;'>power management</a>
<a href='http://blog.neutrino.es/tag/procmail/' class='tag-link-11' title='1 topic' style='font-size: 8pt;'>procmail</a>
<a href='http://blog.neutrino.es/tag/python/' class='tag-link-10' title='1 topic' style='font-size: 8pt;'>python</a>
<a href='http://blog.neutrino.es/tag/rfkill/' class='tag-link-18' title='1 topic' style='font-size: 8pt;'>RFKill</a>
<a href='http://blog.neutrino.es/tag/sec/' class='tag-link-3' title='3 topics' style='font-size: 16.75pt;'>Security</a>
<a href='http://blog.neutrino.es/tag/ssd/' class='tag-link-34' title='1 topic' style='font-size: 8pt;'>ssd</a>
<a href='http://blog.neutrino.es/tag/tor/' class='tag-link-37' title='1 topic' style='font-size: 8pt;'>tor</a>
<a href='http://blog.neutrino.es/tag/trim/' class='tag-link-36' title='1 topic' style='font-size: 8pt;'>trim</a>
<a href='http://blog.neutrino.es/tag/usb/' class='tag-link-21' title='1 topic' style='font-size: 8pt;'>usb</a>
<a href='http://blog.neutrino.es/tag/virtualization/' class='tag-link-15' title='1 topic' style='font-size: 8pt;'>virtualization</a>
<a href='http://blog.neutrino.es/tag/war/' class='tag-link-6' title='1 topic' style='font-size: 8pt;'>war</a>
<a href='http://blog.neutrino.es/tag/webkit-2/' class='tag-link-40' title='2 topics' style='font-size: 13.25pt;'>webkit</a>
<a href='http://blog.neutrino.es/tag/wireless/' class='tag-link-20' title='1 topic' style='font-size: 8pt;'>wireless</a>
<a href='http://blog.neutrino.es/tag/yocto/' class='tag-link-43' title='1 topic' style='font-size: 8pt;'>Yocto</a></div>
</div><div id="categories-3" class="widget widget_categories"><h3 class="widgettitle">Categories</h3>		<ul>
	<li class="cat-item cat-item-24"><a href="http://blog.neutrino.es/category/planet/igalia/" title="planet.igalia.com posts">http://planet.igalia.com</a>
</li>
	<li class="cat-item cat-item-39"><a href="http://blog.neutrino.es/category/planet/webkit/" title="planet.webkit.org posts">http://planet.webkit.org</a>
</li>
	<li class="cat-item cat-item-38"><a href="http://blog.neutrino.es/category/planet/webkitgtk/" title="planet.webkitgtk.org posts">http://planet.webkitgtk.org</a>
</li>
	<li class="cat-item cat-item-31"><a href="http://blog.neutrino.es/category/planet/security/" title="planetsecurity stuff">http://planetsecurity.org</a>
</li>
		</ul>
</div>

</div>
</div></div>
<div class="clear"></div>
<div id="footer">
	<div id="footer-inside">
		<p>
	<a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/" target="_blank"><img alt="Creative Commons License" style="border-width:0" src="http://blog.neutrino.es/wp-content/themes/neutrino/images/CC_88x31.png" class="floatleft" /></a>
	All content on <a xmlns:cc="http://creativecommons.org/ns#" href="http://blog.neutrino.es/" property="cc:attributionName" rel="cc:attributionURL">this site</a> is licensed under the <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/" target="_blank">Creative Commons Attribution-ShareAlike 3.0 License</a>.

</p>
		<span id="back-to-top">↑ <a href="#" rel="nofollow" title="Back to top">Top</a></span>
	</div>
</div>
</body>
</html>