http://unattended.sourceforge.net/advanced.php#netboot
http://gparted.sourceforge.net/livepxe.php
http://www.debian-administration.org/articles/478
https://help.ubuntu.com/community/Installation/QuickNetboot
by "compiling" together these 4 articles above - I've got a netboot server that allows to install Ubuntu or run it in rescue mode (used it twice to restore grub), install WinXP-SP3, run gparted live "cd"
packages installed: dhcp3-server, pxe, tftpd-hpa
netboot image: http://archive.ubuntu.com/ubuntu/dists/intrepid/main/installer-i386/current/images/netboot/netboot.tar.gz
ubuntu netboot menu from image above modified to contain items from "unattended" and "gparted"
and this one, of course http://syslinux.zytor.com/wiki/index.php/PXELINUX
Пʼятниця, 27 березня 2009 р.
Пʼятниця, 6 березня 2009 р.
How to use your city map to add streets to openstreetmap
Мітки:
josm,
maps,
metacarta,
modestmaps,
openstreetmap
1. we need a scanned hi-res bitmap image of a map
2. go to http://labs.metacarta.com/rectifier/ and upload your map
3. you will see two map viewers: left - your image; right - reference map
4. click "+" sign at the right side of reference map viewer and pick a map provider (I've chosen google satellite)
5. set 5-6 control markers on both maps (I've added seven)
6. from a drop-down menu below reference map select linear or quadratic fit (seems to me that linear is faster but less accurate)
7. click "warp!"
8. download and install josm or "sudo apt-get install josm"
9. start josm. go to "edit"->"preferences"->"plugins" (fifth tab from top, the one with a plug)
10. find and check "wmsplugin". apply settings. restart josm.
(if everything is fine, next time you start josm it has to have "WMS" menu item in main menu)
11. go to openstreetmap and find the place you want to add streets to and copy the "permalink" url, e.g.
http://www.openstreetmap.org/?lat=49.54782&lon=25.59045&zoom=15&layers=B000FTF
(don't forget to sign up at OSM otherwise you won't be able to save your edits online)
11a. in josm go to "edit"->"preferences"->"network" (second tab) and enter your OSM username and password.
12. in josm go to "file"->"download from OSM"->"Bounding Box" and paste the above url into text box signed "URL from www.openstreetmap.org"->"ok"
13. you will get a "Data Layer" containing streets (make sure the "layers" pane is visible and use "select tool" to check out street names)
14. go to "WMS"->"Rectified Image...". enter your metacarta image id (just the number, e.g. if your map is located at http://labs.metacarta.com/rectifier/map/74, you enter 74)
15. now you get a new layer called "rectifier id=74". click "Data Layer" to see it on top of image layer.
16. add some streets.
17. "file"->"upload to OSM"
18. according to osm wiki - results will show up in a few days
and that's it.
2. go to http://labs.metacarta.com/rectifier/ and upload your map
3. you will see two map viewers: left - your image; right - reference map
4. click "+" sign at the right side of reference map viewer and pick a map provider (I've chosen google satellite)
5. set 5-6 control markers on both maps (I've added seven)
6. from a drop-down menu below reference map select linear or quadratic fit (seems to me that linear is faster but less accurate)
7. click "warp!"
8. download and install josm or "sudo apt-get install josm"
9. start josm. go to "edit"->"preferences"->"plugins" (fifth tab from top, the one with a plug)
10. find and check "wmsplugin". apply settings. restart josm.
(if everything is fine, next time you start josm it has to have "WMS" menu item in main menu)
11. go to openstreetmap and find the place you want to add streets to and copy the "permalink" url, e.g.
http://www.openstreetmap.org/?lat=49.54782&lon=25.59045&zoom=15&layers=B000FTF
(don't forget to sign up at OSM otherwise you won't be able to save your edits online)
11a. in josm go to "edit"->"preferences"->"network" (second tab) and enter your OSM username and password.
12. in josm go to "file"->"download from OSM"->"Bounding Box" and paste the above url into text box signed "URL from www.openstreetmap.org"->"ok"
13. you will get a "Data Layer" containing streets (make sure the "layers" pane is visible and use "select tool" to check out street names)
14. go to "WMS"->"Rectified Image...". enter your metacarta image id (just the number, e.g. if your map is located at http://labs.metacarta.com/rectifier/map/74, you enter 74)
15. now you get a new layer called "rectifier id=74". click "Data Layer" to see it on top of image layer.
16. add some streets.
17. "file"->"upload to OSM"
18. according to osm wiki - results will show up in a few days
and that's it.
Четвер, 22 січня 2009 р.
Flash Switcher Ubuntu Issues
Мітки:
firefox,
flash,
flash switcher,
linux,
ubuntu
There's a really useful firefox extension for flash/flex developers called Flash Switcher there are win, mac and linux version of it so I decided to try it in Ubuntu.
The way it works is really simple:
- after installing the extension you get a flash icon in status bar with a menu listing your current flash plugin version and two more from the plugin's local repository - those are 7.0 and 9.0 by default. You set the "Firefox plugins directory" in settings to tell the extensions where is your flash plugin located. Each time you change flash plugin version - it gets rewrited by the version you chose from extension's menu.
First thing I decided to do is to add a few more:
1) current ubuntu's "flashplugin-nonfree" lib (that's the one playing sound through pulseaudio so I really need it)
2) and flashplugin developer version (the one that allows debugging you know)
for that I've created two more folders at extension's path:
~/.mozilla/firefox/.default/extensions/flash_switcher@sephiroth.it/plugins/linux/ (the folder containing linux flash plugins of different versions)
10.0 dev and 10.0 ubuntu
and copied the libflashplugin.so to each one (debug version is at adobe's site and the ubuntu's is in /usr/lib/flashplugin-nonfree)
Next thing I've been confused by was that the extension didn't switch anything according to about:plugins flash plugin was still version 10:
By default, the extension uses ~/.mozilla/plugins dir to write the flash plugin lib to, but... there is a symbolic link to /usr/lib/flashplugin-nonfree/libflashplugin.so named @flashplugin-nonfree or something like that which overrides the lib placed into .mozilla/plugins dir by the flash switcher extension... so I decided to fix it in a bit inappropriate way - I made /usr/lib/flashplugin-nonfree writable and set it a "Firefox Plugins Directory" in flash switcher's settings. That fixed the issue.
The way it works is really simple:
- after installing the extension you get a flash icon in status bar with a menu listing your current flash plugin version and two more from the plugin's local repository - those are 7.0 and 9.0 by default. You set the "Firefox plugins directory" in settings to tell the extensions where is your flash plugin located. Each time you change flash plugin version - it gets rewrited by the version you chose from extension's menu.
First thing I decided to do is to add a few more:
1) current ubuntu's "flashplugin-nonfree" lib (that's the one playing sound through pulseaudio so I really need it)
2) and flashplugin developer version (the one that allows debugging you know)
for that I've created two more folders at extension's path:
~/.mozilla/firefox/
10.0 dev and 10.0 ubuntu
and copied the libflashplugin.so to each one (debug version is at adobe's site and the ubuntu's is in /usr/lib/flashplugin-nonfree)
Next thing I've been confused by was that the extension didn't switch anything according to about:plugins flash plugin was still version 10:
By default, the extension uses ~/.mozilla/plugins dir to write the flash plugin lib to, but... there is a symbolic link to /usr/lib/flashplugin-nonfree/libflashplugin.so named @flashplugin-nonfree or something like that which overrides the lib placed into .mozilla/plugins dir by the flash switcher extension... so I decided to fix it in a bit inappropriate way - I made /usr/lib/flashplugin-nonfree writable and set it a "Firefox Plugins Directory" in flash switcher's settings. That fixed the issue.
Пʼятниця, 9 січня 2009 р.
http://www.quotile-sequencer.com
http://www.glitchds.com/quotile-new-pc-midi-sequencer-written-in-processing/
Середа, 3 грудня 2008 р.
automatic keyboard layout convertion tool
Мітки:
kde,
keyboard input language,
keyboard layout,
linux
kxneur (gxneur)
useful for those who often forgets to switch keyboard layout.
useful for those who often forgets to switch keyboard layout.
Вівторок, 9 вересня 2008 р.
host lookup problems and hacky solutions
I got this really weird problem today: x apps couldn't connect XMing host saying "cannot connect to X server".
After some trials & errors - I defined that linux box can't resolve "localhost" host and its own local hostname "ninja"...
/etc/nsswitch.conf shows:
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
(files go first)
/etc/hosts is all right too...
nslookup shows that it tries to resolve localhost and ninja using dsl isp nameservers
ping shows "unknown host 'localhost'" or something like that - why doesn't it use hosts file? I still don't know... after some time on linux community forums I've decided to fix it my way and here is how I did it:
1) first of all, I turned off some pppoe up and down scripts that rewrite /etc/resolv.conf:
# these must be chmoded to non-executables
# ip-up script uses run-parts that runs all the executable files
sudo chmod -x /etc/ppp/ip-up.d/0000usepeerdns
sudo chmod -x /etc/ppp/ip-up.d/0dns-up
sudo chmod -x /etc/ppp/ip-up.d/dns-totd
# I think these can be left executable, but just to be sure...
sudo chmod -x /etc/ppp/ip-down.d/0000usepeerdns
sudo chmod -x /etc/ppp/ip-down.d/0dns-up
sudo chmod -x /etc/ppp/ip-down.d/dns-totd
# after poff and pon dsl-provider resolv conf remains the same (see 2) so it worked
2) /etc/resolv.conf was looking this way before:
nameserver 195.5.46.12
nameserver 195.5.46.10
search local.lan
these values were set automatically on dsl link up
I changed it to this:
nameserver 192.168.1.2
#nameserver 195.5.46.12
#nameserver 195.5.46.10
#search local.lan
I have to mention that I have bind9 up and running successfully as a local dns server for a few months (so I won't be describing bind9 setup here)
3) bind9 has a "localhost" zone already configured so at this point I could already ping localhost alright. I needed to be able to ping "ninja" hostname, so here's what I did:
- opened bind config file in editor
sudo nano /etc/bind/named.conf
- added "ninja" zone to it
zone "ninja" {
type master;
file "/etc/bind/db.ninja";
};
- added zone definition file /etc/bind/db.ninja mentioned above
sudo nano /etc/bind/db.ninja
;
; BIND data file for local loopback interface
;
$TTL 604800
@ IN SOA ninja. root.ninja. (
2 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
@ IN NS ninja.
@ IN A 192.168.1.2
and it pings.
P.S. XMing is alive again
After some trials & errors - I defined that linux box can't resolve "localhost" host and its own local hostname "ninja"...
/etc/nsswitch.conf shows:
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
(files go first)
/etc/hosts is all right too...
nslookup shows that it tries to resolve localhost and ninja using dsl isp nameservers
ping shows "unknown host 'localhost'" or something like that - why doesn't it use hosts file? I still don't know... after some time on linux community forums I've decided to fix it my way and here is how I did it:
1) first of all, I turned off some pppoe up and down scripts that rewrite /etc/resolv.conf:
# these must be chmoded to non-executables
# ip-up script uses run-parts that runs all the executable files
sudo chmod -x /etc/ppp/ip-up.d/0000usepeerdns
sudo chmod -x /etc/ppp/ip-up.d/0dns-up
sudo chmod -x /etc/ppp/ip-up.d/dns-totd
# I think these can be left executable, but just to be sure...
sudo chmod -x /etc/ppp/ip-down.d/0000usepeerdns
sudo chmod -x /etc/ppp/ip-down.d/0dns-up
sudo chmod -x /etc/ppp/ip-down.d/dns-totd
# after poff and pon dsl-provider resolv conf remains the same (see 2) so it worked
2) /etc/resolv.conf was looking this way before:
nameserver 195.5.46.12
nameserver 195.5.46.10
search local.lan
these values were set automatically on dsl link up
I changed it to this:
nameserver 192.168.1.2
#nameserver 195.5.46.12
#nameserver 195.5.46.10
#search local.lan
I have to mention that I have bind9 up and running successfully as a local dns server for a few months (so I won't be describing bind9 setup here)
3) bind9 has a "localhost" zone already configured so at this point I could already ping localhost alright. I needed to be able to ping "ninja" hostname, so here's what I did:
- opened bind config file in editor
sudo nano /etc/bind/named.conf
- added "ninja" zone to it
zone "ninja" {
type master;
file "/etc/bind/db.ninja";
};
- added zone definition file /etc/bind/db.ninja mentioned above
sudo nano /etc/bind/db.ninja
;
; BIND data file for local loopback interface
;
$TTL 604800
@ IN SOA ninja. root.ninja. (
2 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
@ IN NS ninja.
@ IN A 192.168.1.2
and it pings.
P.S. XMing is alive again
Понеділок, 8 вересня 2008 р.
"global" domain name with dynamic ip
Мітки:
dynamic dns,
linux
Recently, I've started to want a globally-accessible, dedicated domain name for my linux box, instead of the one dyndns services give, e.g. yourhost.dyndnsservice.domain etc - so I've registered an .info domain for 2 bucks (there was some promotion so I got lucky) at godaddy and began to look for a way to bind it my linux box - it turned out that my current dyndns service wants about $25 for that (a bit too much I guess).
finally I've found http://www.dnsexit.com/ which does it for free. you need to sign up, add your domain, set their nameservers in domain control panel as registrar's website, setup dynamic ip client to update and that's it
finally I've found http://www.dnsexit.com/ which does it for free. you need to sign up, add your domain, set their nameservers in domain control panel as registrar's website, setup dynamic ip client to update and that's it
Підписатися на:
Дописи (Atom)
