sudo apt-get install tint2
Add bottom taskbar in Ubuntu:
http://www.howtogeek.com/189819/how-to-add-a-taskbar-to-the-desktop-in-ubuntu-14.04/
2015. március 13., péntek
2015. március 11., szerda
Run JAVA applications in Wine
Run JAVA app inside Wine on Linux:
- Download 32-bit Oracle JRE, extract to /home/USERNAME/.wine/drive_c/Program Files (x86)
- Add JRE to PATH (run: wine regedit)
[HKEY_CURRENT_USER\Environment]
"PATH"="C:\\Program Files (x86)\\jre\\bin"
- [OPTIONAL] In Wine settings, set version to Windows XP
- Download 32-bit Oracle JRE, extract to /home/USERNAME/.wine/drive_c/Program Files (x86)
- Add JRE to PATH (run: wine regedit)
[HKEY_CURRENT_USER\Environment]
"PATH"="C:\\Program Files (x86)\\jre\\bin"
- [OPTIONAL] In Wine settings, set version to Windows XP
2015. február 19., csütörtök
Repeater beállítása
Cél: jelenlegi vezeték nélküli hálózat hatósugarának kiterjesztése egy REPEATER eszközzel.
Példa a felépítésre:
ÚTVÁLASZTÓ (ROUTER) - Internetre kapcsolódó eszköz
STATIKUS CÍM
IP cím pl.: 192.168.1.100
DHCP BE
|
| WLAN ---)))
|
WiFi elosztó - REPEATER
STATIKUS CÍM - DHCP és tűzfal KIKAPCSOLVA
|
| WLAN ---)))
|
PC/egyéb kliens
STATIKUS CÍM
IP cím pl.: 192.168.1.1
GW+DNS is ROUTER IP (192.168.1.100)
stb.
FONTOS!
Ugyanazon az alhálózaton kell lenni az eszközöknek, hogy kommunikálni tudjanak!
http://en.wikipedia.org/wiki/Subnetwork
"As it looks Johnny your two devices are on different Subnets, thats why they can't communicate!
You will need to change the IP of the Linksys to 192.168.0.2 for them to be able to communicate. You will also need to disable the DHCP (if it is turned on) on the Linksys.
You can find both of these settings on the Linksys configuration under LAN Settings.
Also if there is a firewall running on the Linksys turning it off will make things easier for you. The D-Link will handle the firewalling for your network!
Turn off the D-Link and set up the Linksys as I described above. When finished the setup save you settings and turn the D-Link back on and you should be fine!
Cheers!"
http://www.tomshardware.co.uk/forum/40841-43-wireless-repeater-headache
Példa a felépítésre:
ÚTVÁLASZTÓ (ROUTER) - Internetre kapcsolódó eszköz
STATIKUS CÍM
IP cím pl.: 192.168.1.100
DHCP BE
|
| WLAN ---)))
|
WiFi elosztó - REPEATER
STATIKUS CÍM - DHCP és tűzfal KIKAPCSOLVA
IP cím pl.: 192.168.1.101
GW+DNS is ROUTER IP (192.168.1.100)|
| WLAN ---)))
|
PC/egyéb kliens
STATIKUS CÍM
IP cím pl.: 192.168.1.1
GW+DNS is ROUTER IP (192.168.1.100)
stb.
FONTOS!
Ugyanazon az alhálózaton kell lenni az eszközöknek, hogy kommunikálni tudjanak!
http://en.wikipedia.org/wiki/Subnetwork
"As it looks Johnny your two devices are on different Subnets, thats why they can't communicate!
You will need to change the IP of the Linksys to 192.168.0.2 for them to be able to communicate. You will also need to disable the DHCP (if it is turned on) on the Linksys.
You can find both of these settings on the Linksys configuration under LAN Settings.
Also if there is a firewall running on the Linksys turning it off will make things easier for you. The D-Link will handle the firewalling for your network!
Turn off the D-Link and set up the Linksys as I described above. When finished the setup save you settings and turn the D-Link back on and you should be fine!
Cheers!"
http://www.tomshardware.co.uk/forum/40841-43-wireless-repeater-headache
2015. január 13., kedd
CODE_n
Kellene egy kis hátszél a Nagy Ötlethez?
"The CODE_n initiative offers an ecosystem designed to network digital pioneers and support the development of new, digital business models."
"The CODE_n initiative offers an ecosystem designed to network digital pioneers and support the development of new, digital business models."
2014. november 14., péntek
ActiveMQ on Ubuntu 14.04 x64 VPS - Solve OutOfMemoryError, Could not reserve enough space for object heap
You need some tweaks to run ActiveMQ in a resource-constrained VPS environment, I've tried this on a VPS that had 2GB RAM.
0. Download ActiveMQ, extract to /opt/activemq and run:
./activemq setup
1. Tweak JAVA minimum heap memory and max heap size - run and also put this line to ~/.bashrc :
export JAVA_OPTS="-Xms128m -Xmx512m"
Verify settings:
echo $JAVA_OPTS
-Xms128m -Xmx512m
echo $_JAVA_OPTIONS
(empty)
2. Limit resource usage (memoryUsage -> 32MB):
nano conf/activemq.xml
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage limit="32 mb"/>
</memoryUsage>
<storeUsage>
<storeUsage limit="10 gb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="10 gb"/>
</tempUsage>
</systemUsage>
</systemUsage>
3. Comment out a few transport Connectors
<transportConnectors>
<!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
<transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
<!-- <transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
<transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
<transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
<transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
-->
</transportConnectors>
4. Set ACTIVEMQ_OPTS_MEMORY and ACTIVEMQ_OPTS
nano /etc/default/activemq
# Set jvm memory configuration
if [ -z "$ACTIVEMQ_OPTS_MEMORY" ] ; then
ACTIVEMQ_OPTS_MEMORY="-Xms128M -Xmx512M"
fi
# Uncomment to enable audit logging
#ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS -Dorg.apache.activemq.audit=true"
ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS -Dorg.apache.activemq.UseDedicatedTaskRunner=false"
5. Setting up proper passwords:
/opt/activemq/conf# nano jetty-realm.properties
# username: password [,rolename ...]
Error messages on a VPS with 2GB RAM before tweaks:
INFO: Loading '/etc/default/activemq'
INFO: Using java '/usr/bin/java'
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
opt/activemq/bin/activemq console
INFO: Loading '/etc/default/activemq'
INFO: Using java '/usr/bin/java'
INFO: Starting in foreground, this is just for debugging purposes (stop process by pressing CTRL+C)
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:714)
at java.lang.ref.Finalizer.<clinit>(Finalizer.java:226)
./activemq: 453: ./activemq: Cannot fork
ERROR: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.activemq.xbean.XBeanBrokerService#0' defined in class path resource [activemq.xml]: Invocation of init method failed; nested exception is java.lang.OutOfMemoryError: unable to create new native thread
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.activemq.xbean.XBeanBrokerService#0' defined in class path resource [activemq.xml]: Invocation of init method failed; nested exception is java.lang.OutOfMemoryError: unable to create new native thread
See also:
http://activemq.apache.org/javalangoutofmemory.html
0. Download ActiveMQ, extract to /opt/activemq and run:
./activemq setup
1. Tweak JAVA minimum heap memory and max heap size - run and also put this line to ~/.bashrc :
export JAVA_OPTS="-Xms128m -Xmx512m"
Verify settings:
echo $JAVA_OPTS
-Xms128m -Xmx512m
echo $_JAVA_OPTIONS
(empty)
2. Limit resource usage (memoryUsage -> 32MB):
nano conf/activemq.xml
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage limit="32 mb"/>
</memoryUsage>
<storeUsage>
<storeUsage limit="10 gb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="10 gb"/>
</tempUsage>
</systemUsage>
</systemUsage>
3. Comment out a few transport Connectors
<transportConnectors>
<!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
<transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
<!-- <transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
<transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
<transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
<transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
-->
</transportConnectors>
4. Set ACTIVEMQ_OPTS_MEMORY and ACTIVEMQ_OPTS
nano /etc/default/activemq
# Set jvm memory configuration
if [ -z "$ACTIVEMQ_OPTS_MEMORY" ] ; then
ACTIVEMQ_OPTS_MEMORY="-Xms128M -Xmx512M"
fi
# Uncomment to enable audit logging
#ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS -Dorg.apache.activemq.audit=true"
ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS -Dorg.apache.activemq.UseDedicatedTaskRunner=false"
5. Setting up proper passwords:
/opt/activemq/conf# nano jetty-realm.properties
# username: password [,rolename ...]
Error messages on a VPS with 2GB RAM before tweaks:
INFO: Loading '/etc/default/activemq'
INFO: Using java '/usr/bin/java'
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
opt/activemq/bin/activemq console
INFO: Loading '/etc/default/activemq'
INFO: Using java '/usr/bin/java'
INFO: Starting in foreground, this is just for debugging purposes (stop process by pressing CTRL+C)
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:714)
at java.lang.ref.Finalizer.<clinit>(Finalizer.java:226)
./activemq: 453: ./activemq: Cannot fork
ERROR: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.activemq.xbean.XBeanBrokerService#0' defined in class path resource [activemq.xml]: Invocation of init method failed; nested exception is java.lang.OutOfMemoryError: unable to create new native thread
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.activemq.xbean.XBeanBrokerService#0' defined in class path resource [activemq.xml]: Invocation of init method failed; nested exception is java.lang.OutOfMemoryError: unable to create new native thread
Environment details:
ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 127259
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 127259
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
See also:
http://activemq.apache.org/javalangoutofmemory.html
2014. november 12., szerda
Kiegészítő LaTeX csomagok használata a Gummi, illetve TeX Live szerkesztőkben (Ubuntu 14.04)
Gummi TeX szerkesztő telepítése:
sudo apt-get install gummi
Futassuk az alábbi két parancsot a Terminálból:
cd ~/.config/gummi
ln -s /usr/share/texmf-texlive
EN: Use additional LaTeX / TeX packages for Gummi or TeX Live on Ubuntu
sudo apt-get install gummi
Futassuk az alábbi két parancsot a Terminálból:
cd ~/.config/gummi
ln -s /usr/share/texmf-texlive
EN: Use additional LaTeX / TeX packages for Gummi or TeX Live on Ubuntu
- Figure out where you installed the extra packages, from TeX Live or whatever else. (For me, they live at /usr/share/texmf-texlive/.)
- Create a symbolic link within the Gummi configuration folder to the TeXLive files:
- cd ~/.config/gummi
ln -s /usr/share/texmf-texlive
Experimentation suggests that pointing Gummi at the top-level directory is sufficient for access to all of the subfolders. If it fits the structure of your machine better, you could also copy or move the files — but I’d stick with a symbolic link unless you have a good plan in mind. - cd ~/.config/gummi
2014. november 3., hétfő
GRUB és indítóképernyő testreszabás
EN: Customize GRUB wallpaper and boot splash logo - Ubuntu 14.04
GRUB háttérkép beállítása:
Válasszunk ki egy nem-indexelt, RGB típusú PNG képet 640x480-as felbontásban (wallpaper.png)
sudo cp wallpaper.png /boot/grub/
sudo update-grub
Indítóképernyő:
Töltsd le és csomagold ki a ZIP fájlt:
http://data.hu/get/8188574/ubuntu-boot-myimage.zip
sudo cp -r ubuntu-boot-myimage '/lib/plymouth/themes'
sudo mv '/lib/plymouth/themes/default.plymouth' '/lib/plymouth/themes/default.plymouth.backup'
sudo ln -s '/lib/plymouth/themes/ubuntu-boot-myimage/ubuntu-faded-screen.plymouth' '/lib/plymouth/themes/default.plymouth'
sudo update-initramfs -u
GRUB háttérkép beállítása:
Válasszunk ki egy nem-indexelt, RGB típusú PNG képet 640x480-as felbontásban (wallpaper.png)
sudo cp wallpaper.png /boot/grub/
sudo update-grub
Indítóképernyő:
Töltsd le és csomagold ki a ZIP fájlt:
http://data.hu/get/8188574/ubuntu-boot-myimage.zip
sudo cp -r ubuntu-boot-myimage '/lib/plymouth/themes'
sudo mv '/lib/plymouth/themes/default.plymouth' '/lib/plymouth/themes/default.plymouth.backup'
sudo ln -s '/lib/plymouth/themes/ubuntu-boot-myimage/ubuntu-faded-screen.plymouth' '/lib/plymouth/themes/default.plymouth'
sudo update-initramfs -u
Feliratkozás:
Bejegyzések (Atom)