What type of ram do I have?

Problem: I wanna look at RAM I may be able to buy but I don't know what memory type I already have and even though my computer is right next to me it is still to far for me to go to to open up and see what type of ram it takes.

System details:
Ubuntu 9.04
uname -a: Linux Moneque 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

Solution:
use lshw

tl;dr....sudo lshw


*nix Systems come with a bunch of ls things; lshw, lsusb, and lspci are a few that I know of. lshw will list everything your computer recognizes as part of it, though I donno if that's printers and the such as well. lsusb Will list the details of your usb bus bits. lspci Will list your pci devices, video cards and sound rcards, this includes pci-e.

to use lshw you can fire up a terminal and type

lshw

That will, at least on my system, probably cry about wanting to be super user.....

aggitan@Moneque:~$ lshw
WARNING: you should run this program as super-user.
moneque                   
    description: Computer
    width: 32 bits
  *-core
       description: Motherboard
       physical id: 0               

The information this displays is good enough for somethings, like if you want to know a bit about your processor and so on. However some details, like the memory type will be omitted.

To fix this we run it with sudo....

sudo lshw

and that should give us more details.....

aggitan@Moneque:~$ sudo lshw
moneque                   
    description: Desktop Computer
    product: System Product Name
    vendor: System manufacturer
    version: System Version
    serial: System Serial Number
    width: 32 bits
    capabilities: smbios-2.3 dmi-2.3 smp-1.4 smp
    configuration: boot=normal chassis=desktop cpus=2 uuid=A0E172FB-7331-DC11-8A81-001E8C259ED7
  *-core
       description: Motherboard
       product: M2R32-MVP
       vendor: ASUSTeK Computer INC.
       physical id: 0

Now, depending on your system you may get more information that can be displayed on your screen at any one time so you'll need/want to pipe the output to a file.

sudo lshw >> somefile

If the file doesn't exist it will be created and written to.

So as far as the memory problem goes we want the segment that starts with
*-memory, it will tell us: where the modules are, how big they are, and what type they are.

*-memory
          description: System Memory
          physical id: 45
          slot: System board or motherboard
          size: 2GiB
        *-bank:0
             description: DIMM DDR2 Synchronous 800 MHz (1.2 ns)
             product: PartNum0
             vendor: Manufacturer0
             physical id: 0
             serial: SerNum0
             slot: DIMM0
             size: 1GiB
             width: 64 bits
             clock: 800MHz (1.2ns)
        *-bank:1
             description: DIMM DDR2 [empty]
             product: PartNum1
             vendor: Manufacturer1
             physical id: 1
             serial: SerNum1
             slot: DIMM1
        *-bank:2
             description: DIMM DDR2 Synchronous 800 MHz (1.2 ns)
             product: PartNum2
             vendor: Manufacturer2
             physical id: 2
             serial: SerNum2
             slot: DIMM2
             size: 1GiB
             width: 64 bits
             clock: 800MHz (1.2ns)
        *-bank:3
             description: DIMM DDR2 [empty]
             product: PartNum3
             vendor: Manufacturer3
             physical id: 3
             serial: SerNum3
             slot: DIMM3

The important parts here are the descriptions, it looks like my system is rocking DDR2 and the modules I have are running at 800MHz. So I would want to look at getting more DDR2 RAM that operates at 800MHz

Huge Log Files

Problem:
-- The VM has limited space
-- You're getting a filesystem full error message
-- A log file has gotten ridiculously large (1.5GB in my case)


Details:
-- FreeBSD system 6.2-STABLE

Oct  9 06:00:00 system kernel: pid 13311 (dd), uid 2 inumber 47118 on /var: filesystem full


%df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/ad0s1a    496M     64M    392M    14%    /
devfs          1.0K    1.0K      0B   100%    /dev
/dev/ad0s1e    496M     26K    456M     0%    /tmp
/dev/ad0s1f    9.7G    2.2G    6.7G    25%    /usr
/dev/ad0s1d    1.9G    1.8G   -2.8M   100%    /var


%ls -alh
total 1720980
drwxr-xr-x   3 root  wheel     1.5K Oct  9 03:01 .
drwxr-xr-x  24 root  wheel     512B Oct  8 16:50 ..
....
-rw-r--r--   1 root  wheel     1.4G Oct  9 07:02 httpd-access.log
-rw-r--r--   1 root  wheel     247M Oct  8 22:53 httpd-error.log

Solutions:
-- Backup, remove, and recreate the files
-- Backup and use the built in tool: truncate
-- Delete everything.

Let's do it:
the filesystem full error message will tell you which filesystem is full, to view details about your other filesystems use the df command

%df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/ad0s1a    496M     64M    392M    14%    /
devfs          1.0K    1.0K      0B   100%    /dev
/dev/ad0s1e    496M     26K    456M     0%    /tmp
/dev/ad0s1f    9.7G    2.2G    6.7G    25%    /usr
/dev/ad0s1d    1.9G    1.8G   -2.8M   100%    /var

Looks like our /var directory is full. There are few things, that I know of, that would grow and cause this directory to fill; the log files.

use the cd command to cd to the directory the logs are located at

%cd /var/log/

use the list command with the proper flags to view files and their human-readable sizes

%ls -alh
total 1720980
drwxr-xr-x   3 root  wheel     1.5K Oct  9 03:01 .
drwxr-xr-x  24 root  wheel     512B Oct  8 16:50 ..
....
-rw-r--r--   1 root  wheel     1.4G Oct  9 07:02 httpd-access.log
-rw-r--r--   1 root  wheel     247M Oct  8 22:53 httpd-error.log

Looks like we have some pretty large files there, the G means gigabytes and the M means megabytes. While it is generally believed that bigger is better this is a bit much.
We can either delete these two files and recreate them or shave off some of the extra fluff.

Take a quick look at the manual page for truncate. Then put on your robe and wizard's hat. Once you're set You can speak the magic words:

truncate -c -s -900m httpd-access.log

And this should chop your file down a fair bit. You can keep using this command and modify the number until you get the file down to what you feel is a reasonable size.

%ls -alh
total 1720980
drwxr-xr-x   3 root  wheel     1.5K Oct 11 00:00 .
drwxr-xr-x  24 root  wheel     512B Oct 10 18:14 ..
....
-rw-r--r--   1 root  wheel     7.5M Oct 11 00:25 httpd-access.log
-rw-r--r--   1 root  wheel     7.3M Oct 11 00:17 httpd-error.log

All that's left now is to take off the robe and wizard's hat....and put it all away...

Project Outline: N.O.’ing

I want to make a conjugation practice program thing for Japanese. Japanese programming is pretty systemic so it should lend its self to being programmed by me fairly easily. I’m naming it “Not only ‘ing” and abreviating it as: N.O.’ing

This is a fancy name because there is more to conjugation than just attacking “ing” to a verb and N.O.’ing can be read as Knowing...Shouldn’t have to explain this.

So here is the outline:

1. Project Name:

   1. Knowing~

   2. N.O.’ing

   3. Not Only ‘ing

2. Project Type:

   1. Educational

3. Project Details:

   1. Description: A platform for going over various types of Japanese Conjugation rules

   2. Web based application PHP/*SQL application

      1. Focused on mobile usage: UMPC, Mobile Phones(?), PSP, and the Nintendo DS

      2. ultra lite

   3. *nix desktop application

   4. Web based tracking?

4. Project Work Flow:

   1. Figure out table:

      1. How many tables will I need?

      2. How to link tables to store info related to another.

      3. General DB table design.

      4. Create a modular, extensible database(table?) to hold verbs with their:

         1. Conjugation rules

         2. Japanese line type/name

         3. Grammatical Categorization

         4. Miscellaneous Details

         5. Conjugation Formulas

         6. Room to add more (stuff)

      5. How to avoid the orz

   2. Figure out script to table design

      1. MySQL+PHP or PostGres + PHP or....?

   3. Figure out front end to back-end script

      1. CSS, HTML and JavaScript

      2. How much JavaScript is too much JavaScript?

   4. Theming

      1. PSP theme

         1. How can this be made quick and easy, to use, as a web app. for the PSP?

         2. PSP does not have touch screen

         3. PSP has a large screen

      2. DS theme

         1. DS has two screens

         2. Very few browsers for the original DS

         3. F.O.S.S. Browser for the DS ain’t the best.

         4. DS has one touch screen

      3. UMPC

         1. Generally like a desktop theme?

         2. UMPC may have touch screen

         3. UMPC may not have touch screen

         4. UMPC may be windows based

         5. UMPC may have a proprietary OS

         6. Drop UMPC support?

   5. Web Based Tracking?

      1. Is it within my range?

      2. Can/Will I get help

      3. How to do web based tracking?

         1. Login + password

         2. syncing user progress from multiple devices

         3. User metrics

         4. User updates

      4. orz

   6. orz

5. orz

Project Outline: "Not this year...."

I want to make a game, a short little game with a simple plot based off a New-Years resolution. Here is my project outline for the game. I suppose I'll write what I get/make as I get/make

1. Project Name:

   1. “Not this year....”

2. Project Type:

   1. Game

3. Project Details:

   1. Description: A simple dating sim like game

   2. Cross platform game using the Ren'Py Visual Novel Engine

   3. Requirements: Ren'Py, Visual Art, Audio Art

4. Project WorkFlow:

   1. Write storyline(Story Telling)

      1. Character design

         1. How many characters?

         2. What kind of characters?

         3. Main character

         4. Secondary characters?

         5. Other, background, characters

      2. Time-Line

         1. When did the story start

         2. When did the story end

         3. what are the times and dates the story focuses on?

      3. Location

         1. Is there only one location?

         2. What are other locations?

         3. Key places?

         4. Location art.

      4. Create Art

         1. Location art

         2. Character art

         3. BGM

         4. SFX

   2. Code Events

      1. Scripting language is python

      2. General Dev needs very little intensive python