Jakiś czas temu zacząłem pisać pracę doktorską. Do tematu chciałem podejść jak najbardziej profesjonalnie – nie tylko jeśli chodzi o zawartość, ale i o skład tekstu. W ręce wpadł mi bardzo poręczny edytor LYX.

Jeśli chcesz by Twój tekst wyglądał schludnie i nie masz czasu do zmarnowania, to gorąco polecam.

Jedną z ciekawszych propozycji do pisania tego typu treści jest layout polski mwbk.layout – jest to format książki w języku polskim. Bardzo przydatna rzecz – problem w tym, że po zainstalowaniu LYX’a, domyślnie nie ma tego układu. Żeby go dograć wystarczy:

sudo apt-get install tetex-extra

Teraz coś na deser, dla tych którzy mają do czynienia w dużą ilością cytowań – JabRef.

Miłego pisania!


rsyslog captures wrt54gl tomato’s logs

1. Edit the /etc/rsyslogd.conf file for allowing the rsyslog server to accept logs from UDP (port 514), by uncommenting the following lines:

# provides UDP syslog reception
$ModLoad imudp
$UDPServerRun 514

By default, rsyslogd will treat the remote logs as if they were local ones (meaning, among other things, the entries will end up in the same logfiles where the local logs are stored). In my setup, I found convenient to override that behaviour and instead place all the logs from my router in a different file:

2. (Optional) Create the file /etc/rsyslogd.d/openwrt.conf with the following contents:

:source, isequal, "myrouter.mydomain" /var/log/mylogfile.log
:source, isequal, "myrouter.mydomain" ~

The first line logs the entries coming from „myrouter.mydomain” (can be expressed as an IP as well) into /varlog/mylogfile.log, while the second one prevents any further processing of the entry by discarding it (note the final tilde ~). A more complete description of the different configuration options [1] and example configurations [2] can be found on the rsyslogd man pages and wiki.

Hope it helps someone.

[1] http://www.rsyslog.com/doc-rsyslog_conf.html
[2] http://wiki.rsyslog.com/index.php/Configuration_Samples

This tutorial was wrote by diego.mics on openwrt forum

ssh on wrt54gl with tomato

  1. Login to your AccessPoint
  2. Click Administration->Admin access
  3. Set
  • Enable at Startup YES
  • Remote Access YES
  • Remote Port 2222
  • Port 22
  • Allow Password Login NO
  • Authorized Keys – you have to generete this with ssh-keygen outside

Here is how to generate authorized key:

ssh-keygen -t rsa

Cat and paste the *pub key to the Authorized Keys field and click SAVE.

…give it a litle bit of time…sip some (admin’s) coffee…

All you have to do is:

ssh -p 2222 root@ 

Happy ssh-ing 🙂


Tomato on WRT54GL Linksys

  1. Download Tomato sofrware, from here.
  2. Log into you Access Point and go to: Administration-> Firmware Upgrade.
  3. Load WRT54G_WRT54GL.bin and click UPGRADE.
  4. Drink some (admin’s)coffee…and wait for it….
  5. Enjoy

RAID5 failed to run set md2

Subject: RAID md2 failed to run
mdadm: failed to RUN_ARRAY /dev/md2 Invalid argument

1. Check the mdadm configuration: /etc/mdadm/mdadm.conf (or just /etc/mdadm.conf) and see what kind of devices are present in the array /dev/md2
cat /etc/mdadm/mdadm.conf
2. Stop the failed array
mdadm -S /dev/md2
3. Assemble the array
mdadm --assemble --force /dev/md2 /dev/sdc5 /dev/sdd5 /dev/sda5 /dev/sdb5
4. Reboot


Archive your mail

Hi everyone,

Today I would like to write about a problem that rather touches, pretty much, everyone. Because of our lazy nature, we have problems with cleaning. Especially, something that we do not have to – that is just what most of us use to think, as it comes to mail boxes. One can have a lot of e-mail boxes and collect as many e-mail as you can get. The problem starts when we have to waste our precious time, for really stupid things, like waiting until our mail box to opens up? Imagine (or you do not have to imagine, because you have it already)…

Archiving e-mails can be really simple if you know how to do it right.

Ok. Now the real life situation – as it turns out really common. I am using pine, INBOX e-mails are in mbox format and send-mail and others are in MAILDIR format. My pine started to read the e-mails slower and slower as the INBOX and other folders got bigger and bigger.

Here is a simple solution which I have found recently in one of the linux newspapers: ARCHIVEMAIL. It is based on python and works fast.

If you have python (>= 2.3), than the installation is easy as A…B…C

Here is typical line command:

archivemail -d 30 -o mail-archived PATH

This would archive e-mail older than 30 days to directory called mail-archived. You can use -n to „dry-run” – just show what would be done.


Pine’s „From” and „Reply-To” headers trick

Today, I was wondering how to manually enable the “From:” field using Pine (Messaging System).

Customized-hdrs comes with help (M Main menu – > C Config. -> customized-hdrs From: Name Lastname <email@domain>) option. This option does not explicitly show the „From” field, but only changes the header. What if you would like to change the header without mixing up with the pine’s configuration every time?

Situation: One need to send a forwarded message to a group and does not want to have replies for individual e-mail address, but wants to ensure that replies will be send to the original sender of the message.

To do this there are at least two ways:

Hard way. Have to do this every time:

  1. Paste the text that you want to send to all users in the new message.
  2. Postpone the message (^O)
  3. Quit pine (Q) and edit manually the header “From”, then save the message
  4. Open pine and use compose (C) to resume (y, when asked) to resume to the postponed message

Easy and simple way. Configure it once and use frequently.

  1. Use standard customized-hdrs (read above)
  2. When composing the new message use the ^R (Rich Header) function
  3. Change the “From:” header field
  4. Send the message (^X)

As I said, easy and simple. Remember that changing “From” field can be used if the system administrator configured the mail server with permissions to change headers. This function is tricky so you have to make sure that you fully understand what you are doing.

Let’s keep in touch pine’rs :-)


I have found even easier solution, here. Again Customized-hdrs have to be used:

  1. Define in Customized-hdrs : Reply-To: Name Lastname <email@domain>
  2. While composing message use ^R (Rich Header) function
  3. Change the value of Reply-To header

Remember: „PINE gives us the power we need to crush those who oppose us…”

Hope you liked it.

Google Adsense


Sierpień 2019
Pon W Śr Czw Pt S N
« Maj