Updating compiler suite

Since every attempt to produce a compiler for my NAS that can be used to compile the OpenJDK failed, I decided to create a toolchain on the NAS to compile this stuff. The reason for a separate toolchain is that libraries are needed that are used by the running system. Replacing them is a bad idea. Therefore I set up a native toolchain to compile other programs into the running system. Basically this is the same as the first couple of chapters form the Linux from Scratch (Version 6.5) approach, which I used as guidance. The following listing does not produce the desired results but it is never the less a good starting point. „Updating compiler suite“ weiterlesen

Bootproblems with Linux

Recently I made some changes on my network. This resulted in chaos so I decided that I reboot my Linux machine. This piece of hardware is already a bit older and in dire need of replacement. There are legacy installations of Windows XP and Windows 98 which are seldom used. Due to the hardware limits this is installed as dual boot.
I restarted the machine and Windows got up even though Linux was the default in the grub bootloader.
„Bootproblems with Linux“ weiterlesen

Yet another Try to get Java running

Since the original aim was to have a Java runtime on my NAS I tried this description and failed. Based on the error message I recieved when calling java -version, I figure that the binaries are not compatible. Therefore I am back to either cross compile or compile a native toolchain to compile on the NAS.

Network with Linux not working

Half a year ago I bought a Notebook (Lenovo 3000 N500). It came with Windows Vista pre-installed. With Windows everything seemed to work. I could hook the notebook to the network and thereby access the internet. Since Windows is just not ‚it‘ I installed Ubuntu. There only the wireless networking worked. Serious web research did not offer any solutions. Therefore I describe it here:
If you issue the ifconfig command you will only get the lo loopback interface and if enabled the wlan0 interface. The device eth0 is available under /dev. If you issue ifconfig eth0 the interface information is displayed, though no IP is assigned. If you try to bring it up through ifconfig up eth0 you will receive the error No such device even though we verified the existence of the device.
It seems to me like a hardware problem which windows is better suited to handle. I get the impression that Windows™ is expected to handle faulty harware or hardware configuration.
The solution to hook the notebook up with the network with Linux was to buy an external USB adapter for the network. I choose the D-Link DUB-E100 since it is verified to work with Linux (Kernel version 2.4.22).