Posts Tagged 'debian'

Amilo Pro v2030

Alright I finally got Debian installed on the Amilo Pro 2030 laptop. There were a few problems that I managed to solve, like an invisible mouse pointer/cursor and the wireless. So I’d like to share the solutions here:

    Invisible pointer:

edit /etc/X11/xorg.conf

Section “Device”
Identifier “Configured Video Device”
Option “HWCursor” “off”
Option “SWCursor” “on”


    Wireless(with internet access available, e.g. ethernet):

Add the contrib repositories to /etc/apt/sources.list
e.g. deb lenny main contrib

apt-get update
apt-get install b43-fwcutter

Download and setup the firmware when prompted.

Voila. Now get something to manage your connections according to your windows manager, I use wicd with LXDE.

Why Use SSH?

This is a short practical introduction to SSH and how you can benefit from using it, or atleast how I have. The secure shell (SSH) network protocol is often unknown to new linux users, and probably to 99% of all only-Windows users πŸ˜€ SSH is used for remote connections over a network, both computers could be in the same LAN, or you could connect to an external ip from the outside world.

I remember when my friend helped me configure something in Debian with SSH from his home. At that point I didn’t actually see how I could personally benefit from it other than being helped to fix things. Later I got more interested in server stuff, but after giving my second monitor away to the same friend who helped my with the config, I started working with SSH to avoid switching one monitor between 2 computers.

These days I try to install the OpenSSH server on my server-box asap, so that I can have the monitor for the pc that actually has a graphical interface πŸ˜€ With Debian/Ubuntu you can find the openssh-server packet on the install cd and in the repositories, if it’s not installed already. You also need a client for the system that you are connecting from, openssh-client for Debian/Ubuntu, and I use Putty for Windows. You can apt-get the Debian packages.

SSH is easy to set up. For example with a fresh install of a distribution, I try to get the openssh-server up and running asap after I get my net setup. This helps me troubleshoot and follow install instructions on my other computer while working on the monitorless computer. I can’t solve everything without a proper browser! Another scenario is if xorg doesn’t work anymore so you can’t really look for help in e.g. google, but luckily you’ve got the openssh-server running and: 1.) another working computer at home 2.) your friend who will let you use his computer for a few minutes. One way or another you can find help much easyer, and continue messing around sooner πŸ˜› Right now I’ve got this pc, with my TinyXp Beast edition, connected to my Debian server with SSH. Both computers are sitting next to each other but I’ve only got one monitor, convenient. As you can see SSH can make your life easyer.

Hopefully this gets the basic idea of SSH through, and opens new doors to linux users. You can find more on how to setup SSH on your distribution by googling around now that you definately want to start using it πŸ˜€


These are my .Xdefaults that are for xterm.

! Black
*color0: #5A5A5A
*color8: #3e3e3e
! Red
*color1: #FF4747
*color9: #FF6767
! Green
*color2: #AFC81C
*color10: #bFC81C
! Yellow
*color3: #FDD338
*color11: #F4D461
! Blue
*color4: #619AF4
*color12: #5496FF
! Purple
*color5: #5F5A90
*color13: #826AB1
! Cyan
*color6: #47E0FF
*color14: #2ED9FB
! White
*color7: #FFFFFF
*color15: #DEDEDE

!xterm settings
xterm*background: #333333
xterm*foreground: #efefcf
xterm*dynamicColors: true
!xterm*utf8: 2
xterm*eightBitInput: true
xterm*saveLines: 32767
xterm*scrollTtyOutput: false
xterm*scrollBar: false
xterm*loginShell: true
xterm*faceName: Bitstream Vera Sans Mono:pixelsize=12
xterm*jumpScroll: true
xterm*multiScroll: true
xterm*toolBar: false

Xcursor.theme: DMZ
Xcursor.size: 24


It’s been a while since I last wrote anything. The reason being that I’ve been using the once only-a-server-box as my everyday pc since my newer one died on me. This endeavour has forced me to use linux even more and I’ve learned a lot. Right now I have a very minimal Debian install with Fluxbox. I have my old posts saved up in my gmail and on the computer. Earlier today I was trying to download the files from gmail, but ran into a scary scenario. When I made a tar backup of all the stuff that used to be on the server (not very much) I had to change the file extesion to .dat so that gmail would allow me to upload it. Then when I was ready to download it today I could not because the gmail anti-virus claimed that it contained a virus after a scan. Obviously the file didn’t contain a virus, the anti-virus just though it was suspicious. Later I tried to forward it to my hotmail account, but gmail displayed ”One of your attachments contained a virus and could not be sent. Remove attachment and send”. Finally I downloaded icedove (almost same as thunderbird) and fortunately I was able to download the file. So I suppose also other similary email clients can bypass this anti-virus, e.g. Outlook.

Setting up a Battlenet/pvpgn-1.8.1 server

Here is how I installed my pvpgn (bnet) server. It will be installed on linux without the mysql or pgsql support, which are used to store account information and only benefit servers with more than 100 active users or if you need to have ladder information appear on your website. In this installation simple file form was used.

Download the pvpgn file from here and upload+extract it to some folder on your server.

Once extracted open the src subdirectory inside the main folder, type in console cd /path-to-pvpgn/src

Then type ./configure –prefix=<path-where-you-want-to-install> or just ./configure to default install in /usr/local

In console type: make and once that is done without errors, type: make install

Now install the support files from here and extract into, by default install directory: /usr/local/var/files

The configuration file is located in, by default install directory: /usr/local/etc/ – and its the bnetd.conf file. I didn’t have to configure anything other than the server name.

The server should work with just that. If you are behind a router like I am, then you should open ports 6200 and 6112… or that’s what I did πŸ˜€

Finally start your server by typing: /usr/local/sbin/bnetd (that’s again the default install directory)

Thats all! It would be nice to hear if this helps someone or if something should be edited, so leave comments πŸ˜‰


Surfed to this website, which I found very easy to follow, and on which I found reference to something amazing. Even though I had my basic LAMP server up and running, I found something more to include. I decided to install Webmin, which is a free server control panel.

Their website had a Debian package that made things relatively easy. Surprisingly enough, everything installed perfectly, and I though something was wrong since I didn’t have to configure anything πŸ˜€ However, when I tried to access the url to the panel from my Winxp pc, nothing seemed to work. So I tested https://localhost:10000 (Webmin port) from the server box, and it worked. Even though Webmin couldn’t be accessed from anywhere else then my server itself, the holy grail of server control was presented to me! Webmin isn’t just any kind of connection between you and your server, it’s much more. You can play around with your whole linux installation, for example it has a command line and download/upload function, which basically means I could ditch puTTy and Filezilla for good.

So this meant that even though I could only reach Webmin from one location, I wouldn’t let that put me down, since now I had more motivation than ever to make things work. Then after a long while of pondering, I realized the obvious… my router wasn’t letting anything go through port 10000. So I forwarded the port and then with a nervous right hand finger clicked refresh in my browser. I felt extremely relaxed when my browser asked if I wanted to accept the websites’ ssl certificate, which I did, and then I was flying past login to the kick-ass control panel πŸ˜›