Tech Talks

Master Your Linux Keyboard (And Fix Caps Lock Forever) Exorcising Caps Lock Want to get rid of the evil caps lock key without mutilating your keyboard? Want to give those silly Windows keys useful jobs, or put all those extra multi-media keys to work? Want to become a powerhouse keyboarding commando? Then come along and join the fun, because Linux has all kinds of good tools for taming wayward keyboards and increasing your efficiency. In this two-part series we're going to use xmodmap, XBindKeys, and KeyTouch to create custom keybindings for launching applications and running commands. The placement of the caps lock key is a demonstration of malicious cunning. It's above the shift key and it's usually oversized, so it's way too easy to hit it when you don't want to, which for me is all the time. On a case-sensitive operating system it's not all that useful anyway. Unhappy users often resort to remedies like prying it off entirely or covering it with duct tap

Got lame server errors? Are you exposing your bind version? Are lame-server errors filling up your logs? Are you letting bind send its version out to potential attackers? You can fix these issues with some simple changes. Simple Bind Configuration Changes Lame Server Errors If you look in your message logs, you may see an error about a "lame server". A lame server is when the NS record for a domain specifies a server that is not authoritative for the domain. For example, the NS record for www.domain.com may list ns1.domain.com as one of its nameserver; however, if you actually query ns1.domain.com, the nameserver does not answer as an authoritative server. The latter is do to a mis-configuration of that nameserver not yours. Lame servers are increasingly common as more and more people run their own DNS -- often with improper configurations. Errors will look something like this in your messages log: lame server resolving 'www.domain.com' (in 'domain.com'?) :

  After installing SUSE 10.0 Display was not working Graphics Card : Matrox G 400 Monitor : Samsung SyncMaster 594 MG 1. I logged into runlevel 3 and tried to fire up X11 systemp5:~ # startx xauth: creating new authority file /root/.serverauth.8991 X Window System Version 6.9.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 6.9 Build Operating System: SuSE Linux [ELF] SuSE Current Operating System: Linux systemp5 2.6.16.21-0.8-ppc64 #1 SMP Mon Jul 3 18:25:39 UTC 2006 ppc64 Build Date: 17 June 2006 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul 13 18:41:41 2007 (==) Using config file: "/etc/X11/xorg.conf" (EE) No device

SuSe 10.2 on IBM P 520 with Apache2 ,Tomcat 6 ,JSDK 1.4.2 and Jboss 4.0.5.GA Reference for known problems http://entropy.brneurosci.org/linuxsetup82.html Installed SUSE 10 Patitiions /dev/sda1 is of type PReP.And its size is 10 MB /dev/sda5 9.9G 1003M 8.4G 11% / /dev/sda2 99M 18M 77M 19% /boot /dev/sda8 26G 345M 25G 2% /home /dev/sda6 9.9G 1.7G 7.7G 18% /usr /dev/sda7 20G 291M 19G 2% /var 1. X display system was not working during the Installation and after installation. An error message describing about insufficient memory was displayed at the startup of installation.But its not able to get into BIOS settings. But it is working remotely through SSH.So the problem is it is not having the proper driver for the monitor connected. Tried a. xf86config b. xorgcfg 3. yast -i xorg-x11* 2. useradd won't work We can add a user called USER