When done correctly, “Secure Boot” is designed to protect against malware by preventing computers from loading unauthorized binary programs when booting. In practice, this means that computers implementing it won’t boot unauthorized operating systems — including initially authorized systems that have been modified without being re-approved.

The biggest issue with the “Secure Boot” system, is that it’ll create a vendor-lockin. This has been seen with the android system as well, but it’ll be Microsft pulling the strings on this one.

Some other interesting reads on Secure Boot:

http://arstechnica.com/business/news/2011/09/windows-8-secure-boot-will-complicate-linux-installs.ars

http://www.osnews.com/story/25180

grep “Invalid user” /var/log/auth.log | less

This resulted in quite a nice list:

Mar 13 20:13:21 tuxbox sshd[31985]: Invalid user oracle from 82.165.193.197
Mar 13 20:13:21 tuxbox sshd[31988]: Invalid user test from 82.165.193.197
Mar 13 20:13:24 tuxbox sshd[32001]: Invalid user demon from 82.165.193.197
Mar 13 20:13:25 tuxbox sshd[32007]: Invalid user test from 82.165.193.197
Mar 13 20:13:26 tuxbox sshd[32011]: Invalid user abcd from 82.165.193.197
Mar 13 20:13:26 tuxbox sshd[32014]: Invalid user abc from 82.165.193.197
Mar 13 20:13:27 tuxbox sshd[32017]: Invalid user tt from 82.165.193.197
Mar 14 07:44:29 tuxbox sshd[22844]: Invalid user adi from 124.232.130.2
Mar 14 07:44:32 tuxbox sshd[22854]: Invalid user salina from 124.232.130.2
Mar 14 07:44:35 tuxbox sshd[22865]: Invalid user cadi from 124.232.130.2
Mar 14 07:44:37 tuxbox sshd[22863]: Invalid user adi from 124.232.130.2
Mar 14 07:44:39 tuxbox sshd[22876]: Invalid user inger from 124.232.130.2
Mar 14 07:44:43 tuxbox sshd[22888]: Invalid user adi from 124.232.130.2
Mar 14 07:44:43 tuxbox sshd[22883]: Invalid user cady from 124.232.130.2
Mar 14 07:44:45 tuxbox sshd[22895]: Invalid user adis from 124.232.130.2
Mar 14 07:44:48 tuxbox sshd[22907]: Invalid user muie from 124.232.130.2
Mar 14 07:44:49 tuxbox sshd[22911]: Invalid user cai from 124.232.130.2
Mar 14 07:44:52 tuxbox sshd[22917]: Invalid user alesa from 124.232.130.2
Mar 14 07:44:54 tuxbox sshd[22929]: Invalid user muie from 124.232.130.2
Mar 14 07:44:55 tuxbox sshd[22932]: Invalid user cailin from 124.232.130.2
Mar 14 07:44:58 tuxbox sshd[22944]: Invalid user foster from 124.232.130.2
Mar 14 07:45:04 tuxbox sshd[22969]: Invalid user braila from 124.232.130.2
Mar 14 07:45:09 tuxbox sshd[22984]: Invalid user domnul from 124.232.130.2
Mar 14 07:45:15 tuxbox sshd[23000]: Invalid user conor from 124.232.130.2
Mar 14 07:45:24 tuxbox sshd[23014]: Invalid user excalibur from 124.232.130.2
Mar 14 07:45:30 tuxbox sshd[23037]: Invalid user soft from 124.232.130.2
Mar 14 07:45:36 tuxbox sshd[23050]: Invalid user peste from 124.232.130.2
Mar 14 07:45:42 tuxbox sshd[23063]: Invalid user lookoo from 124.232.130.2
Mar 14 07:45:47 tuxbox sshd[23077]: Invalid user trandafir from 124.232.130.2
Mar 14 07:45:57 tuxbox sshd[23099]: Invalid user dinamo from 124.232.130.2
Mar 14 07:46:05 tuxbox sshd[23116]: Invalid user steaua from 124.232.130.2
Mar 14 07:46:10 tuxbox sshd[23134]: Invalid user frati from 124.232.130.2
Mar 14 07:46:16 tuxbox sshd[23147]: Invalid user colombo from 124.232.130.2
Mar 14 09:53:53 tuxbox sshd[7154]: Invalid user direccion from 118.69.202.195
Mar 14 10:09:31 tuxbox sshd[9634]: Invalid user simon from 118.69.202.195
Mar 14 10:09:35 tuxbox sshd[9643]: Invalid user server from 118.69.202.195
Mar 14 10:09:38 tuxbox sshd[9652]: Invalid user linux from 118.69.202.195
Mar 14 10:09:43 tuxbox sshd[9660]: Invalid user info from 118.69.202.195
Mar 14 10:09:50 tuxbox sshd[9681]: Invalid user operator from 118.69.202.195
Mar 14 10:09:55 tuxbox sshd[9690]: Invalid user guest from 118.69.202.195
Mar 14 10:09:59 tuxbox sshd[9709]: Invalid user webadmin from 118.69.202.195
Mar 14 10:10:05 tuxbox sshd[9722]: Invalid user user from 118.69.202.195
Mar 14 10:10:09 tuxbox sshd[9732]: Invalid user user from 118.69.202.195
Mar 14 10:10:12 tuxbox sshd[9741]: Invalid user ftp from 118.69.202.195
Mar 14 10:10:16 tuxbox sshd[9750]: Invalid user oracle from 118.69.202.195
Mar 14 10:10:19 tuxbox sshd[9759]: Invalid user oracle from 118.69.202.195
Mar 14 10:10:23 tuxbox sshd[9769]: Invalid user test from 118.69.202.195
Mar 14 10:10:28 tuxbox sshd[9781]: Invalid user soporte from 118.69.202.195
Mar 14 10:10:31 tuxbox sshd[9789]: Invalid user postgres from 118.69.202.195
Mar 14 10:10:34 tuxbox sshd[9798]: Invalid user henry from 118.69.202.195
Mar 14 10:10:38 tuxbox sshd[9806]: Invalid user admin from 118.69.202.195
Mar 14 10:10:41 tuxbox sshd[9816]: Invalid user test from 118.69.202.195
Mar 14 10:10:45 tuxbox sshd[9824]: Invalid user user1 from 118.69.202.195
Mar 14 10:10:48 tuxbox sshd[9838]: Invalid user user2 from 118.69.202.195
Mar 14 10:10:52 tuxbox sshd[9847]: Invalid user user3 from 118.69.202.195
Mar 14 10:10:55 tuxbox sshd[9856]: Invalid user user4 from 118.69.202.195
Mar 14 10:10:59 tuxbox sshd[9870]: Invalid user username from 118.69.202.195
Mar 14 10:11:02 tuxbox sshd[9879]: Invalid user username from 118.69.202.195
Mar 14 10:11:06 tuxbox sshd[9888]: Invalid user testing from 118.69.202.195
Mar 14 10:11:09 tuxbox sshd[9897]: Invalid user webadmin from 118.69.202.195
Mar 14 10:11:12 tuxbox sshd[9905]: Invalid user trixbox1 from 118.69.202.195
Mar 14 10:11:15 tuxbox sshd[9914]: Invalid user testing from 118.69.202.195
Mar 14 10:11:19 tuxbox sshd[9922]: Invalid user test from 118.69.202.195
Mar 14 10:11:24 tuxbox sshd[9931]: Invalid user xbox from 118.69.202.195
Mar 14 10:11:27 tuxbox sshd[9943]: Invalid user mysql from 118.69.202.195
Mar 14 10:11:31 tuxbox sshd[9952]: Invalid user mysql from 118.69.202.195
Mar 14 10:11:34 tuxbox sshd[9961]: Invalid user mysql from 118.69.202.195
Mar 14 10:11:37 tuxbox sshd[9973]: Invalid user mysql from 118.69.202.195
Mar 14 10:11:49 tuxbox sshd[9999]: Invalid user oracle from 118.69.202.195
Mar 14 10:11:53 tuxbox sshd[10012]: Invalid user phpl from 118.69.202.195
Mar 14 10:11:56 tuxbox sshd[10021]: Invalid user user from 118.69.202.195
Mar 14 10:12:00 tuxbox sshd[10030]: Invalid user maggie from 118.69.202.195
Mar 14 10:12:03 tuxbox sshd[10039]: Invalid user usuario from 118.69.202.195
Mar 14 10:12:07 tuxbox sshd[10048]: Invalid user usuario from 118.69.202.195
Mar 14 10:12:10 tuxbox sshd[10056]: Invalid user usuario from 118.69.202.195
Mar 14 10:12:13 tuxbox sshd[10065]: Invalid user user from 118.69.202.195
Mar 14 10:12:17 tuxbox sshd[10074]: Invalid user user from 118.69.202.195
Mar 14 10:12:20 tuxbox sshd[10082]: Invalid user oracle from 118.69.202.195
Mar 14 10:12:23 tuxbox sshd[10091]: Invalid user oracle from 118.69.202.195
Mar 14 10:12:27 tuxbox sshd[10100]: Invalid user oracle from 118.69.202.195
Mar 14 10:12:31 tuxbox sshd[10114]: Invalid user oracle from 118.69.202.195
Mar 14 10:12:34 tuxbox sshd[10124]: Invalid user oracle from 118.69.202.195
Mar 14 10:12:38 tuxbox sshd[10132]: Invalid user oracle from 118.69.202.195
Mar 14 10:12:41 tuxbox sshd[10141]: Invalid user oracle from 118.69.202.195
Mar 14 10:12:45 tuxbox sshd[10151]: Invalid user oracle from 118.69.202.195
Mar 14 10:12:48 tuxbox sshd[10160]: Invalid user oracle from 118.69.202.195
Mar 14 10:12:52 tuxbox sshd[10169]: Invalid user oracle from 118.69.202.195
Mar 14 10:12:56 tuxbox sshd[10177]: Invalid user oracle from 118.69.202.195
Mar 14 10:12:59 tuxbox sshd[10188]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:03 tuxbox sshd[10196]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:08 tuxbox sshd[10205]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:11 tuxbox sshd[10218]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:15 tuxbox sshd[10227]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:19 tuxbox sshd[10241]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:23 tuxbox sshd[10250]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:26 tuxbox sshd[10260]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:30 tuxbox sshd[10269]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:33 tuxbox sshd[10278]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:37 tuxbox sshd[10287]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:40 tuxbox sshd[10296]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:44 tuxbox sshd[10304]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:47 tuxbox sshd[10314]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:51 tuxbox sshd[10323]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:55 tuxbox sshd[10332]: Invalid user oracle from 118.69.202.195
Mar 14 10:13:59 tuxbox sshd[10342]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:02 tuxbox sshd[10352]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:06 tuxbox sshd[10361]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:09 tuxbox sshd[10374]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:12 tuxbox sshd[10382]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:15 tuxbox sshd[10390]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:19 tuxbox sshd[10399]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:22 tuxbox sshd[10408]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:26 tuxbox sshd[10417]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:29 tuxbox sshd[10426]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:33 tuxbox sshd[10435]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:36 tuxbox sshd[10443]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:39 tuxbox sshd[10452]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:43 tuxbox sshd[10460]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:46 tuxbox sshd[10469]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:49 tuxbox sshd[10478]: Invalid user oracle from 118.69.202.195
Mar 14 10:14:53 tuxbox sshd[10487]: Invalid user oracle from 118.69.202.195
Mar 14 10:15:03 tuxbox sshd[10504]: Invalid user oracle from 118.69.202.195
Mar 14 17:53:46 tuxbox sshd[4219]: Invalid user test from 81.1.192.16
Mar 14 17:53:48 tuxbox sshd[4224]: Invalid user testuser from 81.1.192.16
Mar 14 17:53:49 tuxbox sshd[4229]: Invalid user test1 from 81.1.192.16
Mar 14 17:53:50 tuxbox sshd[4234]: Invalid user test from 81.1.192.16
Mar 14 17:53:52 tuxbox sshd[4238]: Invalid user test from 81.1.192.16
Mar 14 17:53:53 tuxbox sshd[4243]: Invalid user test from 81.1.192.16
Mar 14 17:53:55 tuxbox sshd[4248]: Invalid user testing from 81.1.192.16
Mar 14 17:54:03 tuxbox sshd[4276]: Invalid user admin from 81.1.192.16
Mar 14 17:54:04 tuxbox sshd[4281]: Invalid user admin from 81.1.192.16
Mar 14 17:54:06 tuxbox sshd[4286]: Invalid user admin from 81.1.192.16
Mar 14 17:55:01 tuxbox sshd[4486]: Invalid user jeep from 81.1.192.16
Mar 14 17:55:02 tuxbox sshd[4490]: Invalid user alan from 81.1.192.16
Mar 14 17:55:03 tuxbox sshd[4495]: Invalid user jim from 81.1.192.16
Mar 14 17:55:05 tuxbox sshd[4500]: Invalid user postgres from 81.1.192.16
Mar 14 17:55:06 tuxbox sshd[4505]: Invalid user stuff from 81.1.192.16
Mar 14 17:55:08 tuxbox sshd[4509]: Invalid user tom from 81.1.192.16
Mar 14 17:55:09 tuxbox sshd[4514]: Invalid user adam from 81.1.192.16
Mar 14 17:55:13 tuxbox sshd[4528]: Invalid user gov from 81.1.192.16
Mar 14 17:55:16 tuxbox sshd[4538]: Invalid user pgsql from 81.1.192.16
Mar 14 17:55:17 tuxbox sshd[4542]: Invalid user adm from 81.1.192.16
Mar 14 17:55:20 tuxbox sshd[4552]: Invalid user postgres from 81.1.192.16
Mar 14 17:55:23 tuxbox sshd[4561]: Invalid user email from 81.1.192.16
Mar 14 17:55:24 tuxbox sshd[4566]: Invalid user oracle from 81.1.192.16
Mar 14 17:55:25 tuxbox sshd[4571]: Invalid user users from 81.1.192.16
Mar 14 17:55:27 tuxbox sshd[4576]: Invalid user user from 81.1.192.16
Mar 14 17:55:28 tuxbox sshd[4580]: Invalid user test from 81.1.192.16
Mar 14 17:55:30 tuxbox sshd[4585]: Invalid user david from 81.1.192.16
Mar 14 17:55:31 tuxbox sshd[4590]: Invalid user lynx from 81.1.192.16
Mar 14 17:55:32 tuxbox sshd[4595]: Invalid user music from 81.1.192.16
Mar 14 17:55:34 tuxbox sshd[4599]: Invalid user user from 81.1.192.16
Mar 14 17:55:35 tuxbox sshd[4604]: Invalid user user from 81.1.192.16
Mar 14 17:55:36 tuxbox sshd[4609]: Invalid user user from 81.1.192.16
Mar 14 17:55:38 tuxbox sshd[4614]: Invalid user user from 81.1.192.16
Mar 14 17:55:39 tuxbox sshd[4618]: Invalid user rpcuser from 81.1.192.16
Mar 14 17:55:41 tuxbox sshd[4623]: Invalid user rpcuser from 81.1.192.16
Mar 14 17:55:42 tuxbox sshd[4628]: Invalid user guest from 81.1.192.16
Mar 14 17:56:31 tuxbox sshd[4808]: Invalid user apple from 81.1.192.16
Mar 14 17:56:36 tuxbox sshd[4823]: Invalid user brian from 81.1.192.16
Mar 14 17:56:43 tuxbox sshd[4852]: Invalid user log from 81.1.192.16
Mar 14 17:56:45 tuxbox sshd[4857]: Invalid user qmailq from 81.1.192.16
Mar 14 17:56:46 tuxbox sshd[4862]: Invalid user qscand from 81.1.192.16
Mar 14 17:56:52 tuxbox sshd[4881]: Invalid user rosa from 81.1.192.16
Mar 14 17:56:53 tuxbox sshd[4885]: Invalid user rosa from 81.1.192.16
Mar 14 17:57:44 tuxbox sshd[5071]: Invalid user video from 81.1.192.16
Mar 14 17:57:45 tuxbox sshd[5075]: Invalid user admin from 81.1.192.16
Mar 14 17:59:19 tuxbox sshd[5406]: Invalid user guset from 81.1.192.16
Mar 14 17:59:32 tuxbox sshd[5454]: Invalid user guest from 81.1.192.16
Mar 14 18:00:30 tuxbox sshd[5658]: Invalid user apache from 81.1.192.16
Mar 14 18:00:31 tuxbox sshd[5663]: Invalid user david from 81.1.192.16
Mar 14 18:00:33 tuxbox sshd[5668]: Invalid user web from 81.1.192.16
Mar 14 18:00:34 tuxbox sshd[5673]: Invalid user cyberjohn from 81.1.192.16
etc…

As long as you have a towel, there’s no need to panic!
I studied the log in detail and there were luckily no successful logins other than my own (with a valid keypair).

Quick solution to do a first line of defense:

sudo apt-get install denyhosts

DenyHosts:

DenyHosts is a script intended to be run by Linux system administrators to help thwart SSH server attacks (also known as dictionary based attacks and brute force attacks).

Now the only thing I needed to do next was configure DenyHosts so that it’ll sync the known blocked ip’s from the official DenyHosts database.
How to do this is well explained in the configuration file.

sudo nano /etc/denyhosts.conf

You can set the email, purge and sync options.
Adjust like you want.

After not such a long time you can list the denied hosts as follows:

sudo less /etc/hosts.deny

-!- Irssi: Error in script twirssi:
Timestamp out of bounds

This is (most likely) the result of a wrong system date/time.
Quite easy to solve, just sync it to an NTP server.
Open a terminal and enter:

ntpdate pool.ntp.org

Try to load the script again and login.
All should be fine now.

TMPTIME=0
SULOGIN=no
DELAYLOGIN=no
UTC=no #Set according to your system (BIOS) clock.
VERBOSE=no
EDITMOTD=yes
FSCKFIX=no

These values are being used by the scripts at /etc/rcS.d/ that get invoked during boot (even in single user mode)

To be clear, this is not an Ubuntu error. It is simply the Windows that never assumes the system-clock to be in UTC.

If you wish to adjust this in the Windows installation execute regedit and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

Change the RealTimeIsUniversal value to 1.

If you’re simply looking for a wach to change your hardwareclock on linux you can check my other article on Changing date and/or time on Linux.

ffmpeg will do the trick.
Say you want to cut the flash movie in pieces of 10 minutes, you can do this like this:

ffmpeg -i filename.flv -ss "00:00:00" -t "00:10:00" filename_chunk.flv
ffmpeg -i filename.flv -ss "00:10:00" -t "00:20:00" filename_chunk2.flv
ffmpeg -i filename.flv -ss "00:20:00" -t "00:30:00" filename_chunk3.flv
...

Now you’re ready to upload your video’s.

But now, there are proprietary Linux drivers released by ATI/AMD

1. First, you should update your system (just to be sure).
   

   sudo apt-get update
   sudo apt-get upgrade

2. If you’ve been using older drivers, remove them.
   

   sudo apt-get remove –purge xserver-xorg-video-radeon

3. Download the install package from the AMD suppot pages and make it executable
   

   chmod +x ati-driver-installer*.run

4. Run the installer as sudo-user
   

   sudo ./ati-driver-installer*.run

5. Reboot

Enjoy!

The Linux 2.6.38 kernel carries the ATI Radeon HD 6000 open source support. (just fyi!)
If you encounter problems or found this post helpful, it would be nice to leave a comment below.
This way, I can adjust it to the needs of my readers.

As all wise people should do, I’ve been using OpenSSH to connect to it.
Solely  connected to it from my netbook, as my desktop Ubuntu computer died after the purchase of a new ATI (curse you) Graphics card.
But now, I managed to revive my desktop (yay!) and wanted to log in on my server.
Setted up the key and wanted to transfer it to my authorized hosts file… but that gave me a bloody error:

Permission denied (publickey).

So I started to digg around and checked filepermissions, ssh_config file etc… But all seemed ok.
But then I found this little nasty openSSH Bug on launchpad.

Simply running “ssh-add” on the client fixed the problem!

Ssh-add adds identities to the authentication agent, ssh-agent. When run without arguments, it adds the file %HOME%/.ssh/identity. Alternative file names can be given on the command line. If any file requires a passphrase, ssh-add asks for the passphrase from the user.

I’m not sure how this could’ve helped, but hey, its a workaround that actually works

Profile:
You don’t have to be an Ubuntu/Linux expert.
If you can testify about your experiences and suggest to Windows-programs,
can already make a difference.
Most people we lend a word on the fair, have none or little of Ubuntu/Linux/Computer experience.

Fun fact:
As an exhibitor you don’t have to pay the entrance fee, but between helping out, you can take our time to look around and find awesome deals.

How:
Add your name to the ubuntu-wiki page:
https://wiki.ubuntu.com/BelgianTeam/ComputerFairs/Ghent_2011-01-31
OR
Let me know trough mail ubuntu@mimor.be

Please in both of these cases, mention whether you’ll be helping out a full day or several hours.
That’s all you need to do.
If you can provide items such as demolaptop(s), camera, etc. .. you may also add it to the wiki page.

Hope to see you soon.

=====================================

Gezocht:
Mensen die willen helpen op de Ubuntu stand tijdens de Dipro beurs in Gent op 30 Jan 2011.
Indien het niet mogelijk is om de volledige dag aanwezig te zijn, zijn enkele uren hulp ook altijd welkom.

Profiel:
Je hoeft geen Ubuntu/linux/computer expert te zijn.
Als je kan getuigen over jouw ervaringen en uitleg geven over alternatieven voor Windows programma’s,
kan je al een verschil maken.
De meeste mensen die we op de beurs ten woord staan, hebben helemaal geen of weinig van Ubuntu/Linux.

Leuk weetje:
Als medewerker van de stand hoef je geen toegangsgeld te betalen, maar kan je tussendoor wel rond kijken en toffe deals vinden.

Hoe:
Voeg je naam toe aan deze Ubuntu-be Wiki pagina:
https://wiki.ubuntu.com/BelgianTeam/ComputerFairs/Ghent_2011-01-31
OF
Laat het me weten via mail op ubuntu@mimor.be

Gelieve in de twee gevallen te vermelden of je een volledige dag of enkele uren zal helpen.
Dat is het enige dat je hoeft te doen.
Indien je items van de lijst kan verzorgen zoals demo laptop(s), fototoestel, etc… mag je dit ook telkens aanvullen op de wiki pagina.

Hopelijk tot binnenkort.

Mvg,

Mike Morraye

First check the current time of your hardwareclock:

hwclock -r

Then add the right date/time to your systemclock.
In the example provided you’ll find some strange long number.
You have to read it like this (from left to right):
[01] = month (Jan) | [14] = day | [0231] = time (02:31) | [2011] = year

sudo date 011402312011

Now sync your hardware clock with the date/time you’ve just set:

sudo hwclock --systohc

Check if the hardware clock is synced right:

sudo hwclock -r

Profit!

I’ve just send out the news to the mailing list of Ubuntu-be and the Whitespace to confirm that i’ll organise the release party for the upcoming LTS version of Ubuntu.
The event will take place Thursday the 13th of May in the Whitespace.
I’m still looking for people whom have some knowledge of something Ubuntu-related and have the guts to give a lightningtalk or a demo.
At the moment of writing, I’ve had 1 confirmation from a guy with Balls! Mandel.
He did a talk about desktopcouch at fosdem this year, and will bring an improved version of that to the Release party.
If you have questions, let me know.
I’m available at the #Ubuntu-be channel on freenode, or just PM me (mimor) or use the comment section below.

The sent mail in English:

Hello to all.
>
> I organize a RP on the 13th of May in honor of the Ubuntu 10.04 (Lucid)
> release.
> This is indeed a Thursday but that’s an official holiday and lot’s of
> the people don’t have to work on Friday.
> What time it’ll take place is yet to be decided.
>
> The RP will take place in the Whitespace (Blekerijstraat 75, Gent,
> Belgium)
> For people wondering what the Whitespace is: http://0×20.be
>
> The space has: power, network, internet, drinks, snacks, beamer, couches
> and I hope we can repair the coffee-machine by then.
> People whom want something else, mention it.
>
> The program is still under construction.
> This moment, my receipt looks like this:
>
> Around 13h we’ll serve a light meet & greet to loosen up the nerves.
> Next, we’ll stimulate the senses wit a series of lightning talks
> accompanied by a spicy serving of freshly cut tips.
> As the Spécial-du-chéf, you can enjoy some trial-and-error-sauce topped
> hands-on sessions.
>
> This part is for sure, but the rest is still work in progress!
>
> This is the rest:
>
> – design of Posters, flyers and web-banners
> – do you know someone, or want to present something yourself? Go for it
> & let me know.
> – spread the word! To your friends, colleagues, your student-club, etc..
> – the pleasure to have YOU with us!
>
> Regards,
>
> Mike Morraye

Or in Dutch:

>
> Hallo iedereen.
>
> Ik organiseer Donderdag, 13 Mei 2010 een RP voor Ubuntu 10.04 (Lucid).
> Dit is inderdaad een donderdag Maar het is een feestdag en vrijdag is
> voor velen dus een brug-dag.
> Van hoe laat tot hoe laat is nog te beslissen.
>
> De RP gaat door in de Whitespace (Blekerijstraat 75, Gent, Belgium)
> Voor wie wil weten wat dit is: http://0×20.be
>
> Locatie heeft: stroomvoorziening, netwerk, internet, (fris-) drank,
> versnaperingen, beamer, zetels en hopelijk kunnen we tegen dan ook de
> koffiezet herstellen.
> Wie nog iets anders wil, laat het gerust weten
>
> Het programma in nog in ontwikkeling.
> Op dit moment zit m’n recept er zo uit:
>
> Rond 13h serveren we een luchtige meet & greet om de zenuwen wat los te
> weken. Hierna prikkelen we de zintuigen met een reeks van pittige
> lightningtalks vergezeld van een portie vers gesneden tips.
> Als spécial du chéf, kunnen de fijnproevers genieten van enkele hands-on
> sessies overgoten met een sausje trial & error.
>
> Dit stuk is zeker, de rest is work in progress!
>
> Hier dus de rest:
>
> – ontwerp Poster & flyer en/of web-banners?
> – ken je iemand, of wil je zelf iets presenteren. Go for it & let me
> know.
> – Spread the word! In je vriendenkring, op het werk, in je
> studentenclub, etc…
> – het genoegen dat JIJ er ook bent!
>
> Mvg,
>
> Mike Morraye