Skip to main content

Building up a Linux Home Server

My trusted Buffalo LS2 has finally call up its day.. all because of me .. as per my previous posting about the NAS. I broke the ribbon cable and I don't really fancy trying to desolder/resolder back the cable. I was eyeing a NAS replacement, mainly a Buffalo Linkstation Live + Torrent (1TB) which has price tag of RM600 but since I've 1TB WD HD already, I was thinking of building my own home server. I don't fancy going to LowYat due to many reasons .. among them 1) it always packed with people 2) it is hard to get a parking 3) I don't want to stuck in KL jam .. so, I headed up to LowYat's Forum instead. Initially, was looking for a better looking HTPC enclosure but ughh.. at RM400 w/o power supply, I ended up getting a chepo AOpen's Transformer look enclosure.

The following parts were ordered today:

Aopen G326/Black w/ 400W 12cm fan PSU : RM 269
Intel Atom D945GCLF2 (ATOM 330) w/ Built-in 1.6Ghz Dual Core ITX Mobo : RM 280
Kingmax 1GB DDR2/800 RM 88

Postage for the above is RM12 as quoted. With RM649, I believe it is worth more than a purpose built NAS.

Since Saturday is a Public Holiday, I guess I'm getting the parts on Monday .. surely couldn't wait to put them together.

Anyway, the OS of choice will be either Debian/Lenny or Ubuntu Server though someone has suggested OpenSolaris because of the ZFS file system. I'm more inclined to Linux since I've been using it since ages ago.

Update Mon 19/10: Received the motherboard/process + RAM. Still waiting for the enclosure.

Update Tue 20/10: Received the casing now and done building up the system. Tried booting the Ubuntu Server installation disc from USB but it won't work.. had to install old CD ROM to the server now.

Comments

Popular posts from this blog

Raspberry Pi + svxlink = Low power echolink node

What is the easiest way to get echolink node up and running on raspberry pi? Surely, get a premade image which has everything inside. I've created one image which can fit into 2GB SD card for this, just follow the following steps to get it up and running:

For hardware, you need to have the following:
Raspberry Pi for sure, with a minimum 4GB SD cardA USB echolink interface, can be commercially sourced or DIY. There are many DIY schematics out there that you could follow.  Here is the configuration on how to get the things working together, courtesy of svxlink.de website:

For software:
Download the following prepared image from google drive, it is based on raspbian-2015-02-16 image and has pre-installed svxlink-14.08. raspi-wheezy-svxlink.img.zipUnzip the file and copy it to your SD card using the following instructions that can be found here.Boot up the RasPi, if you do not have an HDMI monitor, you may want to access the RasPi from your terminal emulator (putty or the like), connec…

Configuring TechniColor TG784N V3 (Maxis issued broadband router) to use different DNS servers

Previous write up deleted. It seems to change the DNS servers in as shown on the status, but it does not really work.

Check the following website, this seems to work:

http://www.o2help.co.uk/router-change-dns/

This can be done from the WEB GUI too, go into the following configuration path:


In my example above, I'm using paid service unblock-us instead of google public DNS servers.

Debugging DMEE

I've come across many posting on the Internet (via google search), people asking on how to debug a DMEE for payment program. One of the few suggestion was to create a user exit just before the node that we would like to debug and put our breakpoint there. It seems that SAP has built-in this feature without needing us to create a user exit (available in ECC 6, have no idea if this is available on prior releases). Here is how you can put your breakpoint without any coding.

1. Display your DMEE tree using transaction: DMEE_DEBUG.


2. Click on the node that you would like to debug.
3. Go to conditions tab, you could see the Set Breakpoint button. Click to set.



4. Run the SAPFPAYM and specified the payment run date/id, payment format etc. SAP will stop at the node which you point your breakpoint at, as in 2.
5. To remove your breakpoint, just run the DMEE_DEBUG again, there is an option to delete all own breakpoints or all.