1. As example, we have an iso file (ubuntu-8.04-desktop-i386.iso) which size is 699 Mb
root@hardy:/home/bearisusanto/test# ls -alh
total 700M
-rwx——  1 bearisusanto root         700M 2008-06-02 03:22 ubuntu-8.04-desktop-i386.iso2. Before doing split process, first make MD5 file from ubuntu-8.04-desktop-i386.iso for ensuring that there is not a change for the file when its join again
root@hardy:/home/bearisusanto/test# md5sum ubuntu-8.04-desktop-i386.iso > MD5SUM.txt
root@hardy:/home/bearisusanto/test# cat MD5SUM.txt
8895167a794c5d8dedcc312fc62f1f1f  ubuntu-8.04-desktop-i386.iso

3. For splitting ubuntu-8.04-desktop-i386.iso to be a file which the size maximal 400Mb for each file, we type the command
root@hardy:/home/bearisusanto/test# split -d -b 400m ubuntu-8.04-desktop-i386.iso ubuntu-8.04-desktop-i386.iso.part

4. If we check in the directory, there is two 2 which is the result from splitting process
-rwx——  1 bearisusanto root         700M 2008-06-02 03:22 ubuntu-8.04-desktop-i386.iso
-rw-r–r–  1 root         root         400M 2008-10-31 23:13 ubuntu-8.04-desktop-i386.iso.part00
-rw-r–r–  1 root         root         300M 2008-10-31 23:13 ubuntu-8.04-desktop-i386.iso.part01

5. To join the two file to be one file as the same with the original file, we use “cat” command but the original have to be deleted first.
root@hardy:/home/bearisusanto/test# rm ubuntu-8.04-desktop-i386.iso
root@hardy:/home/bearisusanto/test# cat ubuntu-8.04-desktop-i386.iso.part00 ubuntu-8.04-desktop-i386.iso.part01 > ubuntu-8.04-desktop-i386.iso

6. For ensuring that there is no difference with the original file, we have to validate with using MD5SUM.txt which have made for the first time.
root@hardy:/home/bearisusanto/test# md5sum -c MD5SUM.txt
ubuntu-8.04-desktop-i386.iso: OK

Data which has been deleted maybe could be recovered with recovery software, It could be dangerous if there is an important file that somebody couldn’t know the contents.

To reduce the risk, that someone could recovered our files, we can do deleting process permanently with using software utility which have permanent delete ability. In Linux platform, we have utility like SHRED and WIPE.

Here is the usage the two utility.

1. Deleting data using SHRED

   I take a sample to delete USB Flashdisk (UFD) permanently.

   - Use command fdisk -l to know the UFD location

   root@hardy:/# fdisk -l

   …

   Disk /dev/sdb: 1026 MB, 1026555392 bytes

   129 heads, 16 sectors/track, 971 cylinders

   Units = cylinders of 2064 * 512 = 1056768 bytes

   Disk identifier: 0x28eff17f

   Device Boot Start End Blocks Id System

   /dev/sdb1 * 1 972 1002487+ b W95 FAT32

   Partition 1 has different physical/logical endings:

   phys=(977, 128, 16) logical=(971, 52, 15)

   - From the information in the above, we knows that UFD is located at /dev/sdb1.

   Before we doing manual delete, do umount the UFD from system.

   First, see the mount UFD partition location use command df -h

   root@hardy:/# df -h

   …

   /dev/sdb1 978M 347M 631M 36% /media/BENNY

   - Now, we can permanently delete our file using shred command

   root@hardy:/# shred –verbose -u /dev/sdb1

   …

   shred: /dev/sdb1: pass 1/25 (random) … 126MiB/3.8GiB 3%

   …

   - For default, command above will do overwrite iteration 25 times. If, this is too long we could use option -n

   root@hardy:/# shred –verbose -u -n 5 /dev/sdb1

   - Now, all data in UFD is permanently deleted. To using UFD again, we have to format it

1. Deleting data using WIPE

   Except shred, we have wipe command which the have ability like shred.

   root@hardy:/# wipe -kq /dev/sdb1

   Okay to WIPE 1 special file ? (Yes/No) yes

   Wiping /dev/sdb1, pass 0 in quick mode [ 3884 / 1026555392]

To know the detail of wipe command, we could see from the manual

root@hardy:/#man wipe

]]> http://ubuntunow.wordpress.com/2008/11/06/shreading-data/feed/ 0 bearisusanto http://ubuntunow.wordpress.com/2008/10/06/finding-files/ http://ubuntunow.wordpress.com/2008/10/06/finding-files/#comments Mon, 06 Oct 2008 08:42:47 +0000 bearisusanto http://ubuntunow.wordpress.com/2008/10/06/finding-files/ ]]> You now know what each major directory holds, but it still doesn’t really help you find things. I mean, you could go looking through directories, but there are quicker ways. There are four main file search commands.

which
The first is the which(1) command. which is usually used to locate a program quickly. It just searches your PATH and returns the first instance it finds and the directory path to it. Take this example:

% which bash
/bin/bash

From that you see that bash is in the /bin directory. This is a very limited command for searching, since it only searches your PATH.

whereis
The whereis(1) command works similar to which, but can also search for man pages and source files. A whereis search for bash should return this:

% whereis bash
bash: /bin/bash /usr/bin/bash /usr/man/man1/bash.1.gz

This command not only told us where the actual program is located, but also where the online documentation is stored. Still, this command is limited. What if you wanted to search for a specific configuration file? You can’t use which or whereis for that.

find
The find(1) command allows the user to search the filesystem with a rich collection of search predicates. Users may specify a search with filename wildcards, ranges of modification or creation times, or other advanced properties. For example, to search for the default xinitrc¤ FORMTEXT
file on the system, the following command could be used.

% find / -name xinitrc
/var/X11R6/lib/xinit/xinitrc

find will take a while to run, since it has to traverse the entire root directory tree. And if this command is run as a normal user, there will be permission denied errormessages for directories that only root can see. But find found our file, so that’s good. If only it could be a bit faster…

slocate
The slocate(1) command searches the entire filesystem, just like the find command can do, but it searches a database instead of the actual filesystem. The database is set to automatically update every morning, so you have a somewhat fresh listing of files on your system. You can manually run updatedb(1) to update the slocate database (before running updatedb by hand, you must first su to the root user). Here’s an example of slocate in action:

% slocate xinitrc # we don’t have to go to the root
/var/X11R6/lib/xinit/xinitrc
/var/X11R6/lib/xinit/xinitrc.fvwm2
/var/X11R6/lib/xinit/xinitrc.openwin
/var/X11R6/lib/xinit/xinitrc.twm

We got more than what we were looking for, and quickly too.With these commands, you should be able to find whatever you’re looking for on your Linux system.

Ubuntu has default pdf reader when we installed it, but adobe acrobat is the most popular reader.

Now, its shows how to install it in ubuntu.

1. Open terminal

2. sudo wget http://www.medibuntu.org/sources.list.d/hardy.list -O /etc/apt/sources.list.d/medibuntu.list

3. sudo apt-get update && sudo apt-get install medibuntu-keyring && sudo apt-get update

4. sudo apt-get install acroread

• File command
-Linux command that displays the file type of a specified filename

• Text file
- File that stores information in a readable text format
• Some filenames inside each user’s home directory represent important configuration
files or program directories
• Hidden files
– Files that are not normally displayed to the user via
common filesystem commands

List option :
-a or –all = list all filenames
-A or –almost-all = List most filenames (excludes the . and .. special files)
-C = lists filenames in column format
–color=n = list filenames without sorting
-f = lists all filenames without sorting
-F or –classify = lists filenames classified by file type
–full-time = lists filenames in long format and displays the full modification time
-l = lists filenames in long format
-lh or -l –human-readable = lists filenames in long format with human-readable (easy-to-read)
-lG or -l –no-group or -o = lists filenames in long format but omits the group information
-r or –reverse = list filenames reverse sorted
-R or –recursive = lists filenames in the specified directory and all subdirectories
-s = lists filenames and their associated size in kilobytes (K)
-S = lists filenames sorted by file size
-t = lists filenames sorted by modification time
-U = lists filenames without sorting
-x = lists filenames in rows rather than in columns

Note :
When you see this message :
/usr/lib/vmware/bin/vmware /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1:version ‘GCC_3.4′ not found (required by /usr/lib/libcairo.so.2)

………
Remove the folder libgcc_s.so.1 on /usr/lib/vmware/lib

8.    From the first windows choose Localhost
9.    Goto ‘Help’ and choose ‘Enter Serial Number’
10.    Without serial number, you can not running virtualization
11.    Click “Create a new virtual machine”
12.    Select “Typical” on Virtual Machine Configuration
13.    Choose guest operating system
14.    Define the virtual machine name and location
15.    Choose network connection
16.    Specify disk size
17.    Finish
18.    Now you could install the new operating system

let’s say that you open up a Root Terminal and issue the hdparm command:

hdparm -h

You should see a list of commands that you can issue.

The first two commands that you want to look at are

hdparm -i /dev/hda
hdparm -I /dev/hda
hdparm -i /dev/hda1
hdparm -I /dev/hda1

Now let’s day that your dma is set to off and you wish to set it to on. Then you’d hdparm -d1 /dev/hda
But if you wish to make it so that that setting is set during bootup, you know that we will have to gedit /etc/hdparm.conf.

So, open up a Root Terminal, cd over to /etc and sudo gedit hdparm.conf
Go to the end of the file and highlight & copy

#/dev/hda {
# mult_sect_io = 16
# write_cache = off
# dma = on
#}

Now right click / paste it at the very end of the file (after starting a new line after hitting carriage return).

Now remove the # from the front of all those new lines you’ve copied from the end of YOUR file.

This is where you’ll be making all your changes.

You would first make sure that your setting a command in the Root Terminal will work.

So let’s say that when I did a hdparm /dev/hda command I got back

/dev/hda:
multcount = 0 (off)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 58168/16/63, sectors = 58633344, start = 0

So I give this command hdparm -d1 -m1 /dev/hda
Now when I hdparm /dev/hda I get

/dev/hda:
setting multcount to 1
multcount = 1 (on)
setting dma to 1
dma = 1 (on)

So I would now modify my hdparm.conf to read

/dev/hda {
mult_sect_io = 32
dma = on
}

save it and reboot.

Please note that these are commands in a mock up. In no way do I endorse your putting in mult_sect_io = 32 if your HD cannot support it. The same would go for all the other commands.

Since all you want to do is set DMA, you’d

/dev/hda {
dma = on
}

<save, reboot>

But before rebooting I would hdparm /dev/hda. This is what it looks like now (after issuing an hdparm -c1 -d1 -m1 /dev/hda command:

/dev/hda:
multcount = 1 (on)
IO_support = 1 (32-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 58168/16/63, sectors = 58633344, start = 0

You should see some new messages regarding hdparm when it is booting up.

Just be careful when playing around with the ATA settings. The numbers don’t quite go the way you’d expect.

Now, you’ll want to test all your settings before ever touching /etc/hdparm.conf.
The commands to do that are:

hdparm -t /dev/hda
hdparm -T /dev/hda

But just testing /dev/hda is really testing just the channel and not the drive itself.

So you should really be saying

hdparm -t /dev/hda1
hdparm -T /dev/hda1

for example.

(I think this may work. I’ve never had to use it to set individual drive settings. And I doubt that you could turn on DMA for just one drive on a chain as the DMA setting affects the controller which will in turn affect each individual drive. But it may give you different test results when testing a drive; at least it did me.)

/dev/hda1 {
dma = on
}

So my advice is:

Issue a ‘set’ command in a Root Terminal.
Run a -i, -I, -t and -T test.
Only then commit the changes to /etc/hdparm.conf and reboot.

As always, it is best if you make a backup of all your precious data onto a CDR before making radical changes. And always have your Ubuntu Live CD at the ready.

From /etc/hdparm.conf:
Note that if the init script causes boot problems, you can pass ‘nohdparm’ on the kernel command line, and the script will not be run.

Thanks a lot for your tutorial

Installation Procedure:

Option 1: Install with Wubi Ubuntu Installer

The easiest installation option for Windows versions of the Wind/Advent 4211 is to use the Wubi Ubuntu installer directly from Windows. This will allow you to try out Ubuntu without partitioning your hard drive. HowtoForge.com has written a detailed tutorial for using Wubi.

To then upgrade your Wubi install to a standard Ubuntu system, use the Loopmounted Virtual Partition Manager (LVPM). LVPM allows you to transfer all the data, settings, and applications from your original Wubi install to a dedicated partition. LVPM can be found in Ubuntu under: Applications => System Tools

If, after using LVPM, you get a can’t mount partition error, then you will need to edit grub. The LPVM installation has worked, grub just needs to be set to use the correct partiion.

Firstly, to fix grub temporarily so you can get into Ubuntu: Reboot the machine, wait till the menu comes up giving you the list of boot options, make sure the top item is selected, (Ubuntu 8.04.1, kernel 2.6.24-19-generic) then hit e to edit the item.

This will give you an edit screen and stop the boot countdown.

There should be three lines on the screen. Scroll down to the line that says:

root ()/ubuntu/disks

and change it to:

root (hd0,X)

X should be the partition number you transferred Ubuntu to using LVPM minus 1.

e.g. In my case I transferred Ubuntu to sda5, so my line read root (hd0,4)

Once this line is edited, hit Enter to accept the editing, then b to boot.

Ubuntu should now boot up. You can make the changes permanent to fix your boot forever, by making the same changes in /boot/grub/menu.lst

Option 2: Install With Ubuntu 8.04.1 Desktop CD (GUI)

A second installation option is to use an Ubuntu installation CD (or USB Pen Drive).

Note: With the release of Ubuntu Hardy Heron 8.04.1, it appears that earlier problems installing with the Ubuntu GUI installer have been resolved. If, however, you would prefer to install Ubuntu using a text interface installer, use the “Install with Alternate Desktop CD” instructions in the next section below.

1. Download Hardy Heron 8.04.1 (PC (Intelx86) desktop CD) from here: http://releases.ubuntu.com/8.04.1/ (Tested and confirmed to work by Malarcy in this forum thread).
2. Burn the “ubuntu-8.04.1-desktop-i386.iso” image to a CD.
3. Optional: You can install Ubuntu on the Wind/Advent 4211 using a USB Pen Drive. To create a bootable live USB Pen Drive, use UNetbootin – The Universal Netbbot Installer OR follow the instructions for creating a Persistent Ubuntu 8.04 USB Pen Drive at PenDriveLinux.com.
4. Boot system with F11 pressed and the install media (External USB CD-ROM or USB Pen Drive) connected. When prompted, select the drive containing your Ubuntu 8.04.1 .iso image.
5. Click on the “Install” icon on the Live Desktop.
6. Optional – Manually Partition Hard Drive: While allowing the Ubuntu Installer to automatically partition your hard drive during installation is acceptable, it can be beneficial to manually edit your partition table. Before getting started, it is recommended that you first review each of the 9 steps below. For additional information about partitioning your hard drive, you may also want to reference this guide.
   1. During installation, choose “Manually edit partition table.”
   2. Select the partition you want to resize and press Enter.
   3. Select “Size” and press Enter.
   4. Select “Yes” and press Enter.
   5. Type a new size in Gigabytes for your partition. On the Wind/Advent 4211, it’s recommended you free up AT LEAST 15 GB of free space for your Ubuntu install (see number 8 below for more info/suggestions on partition sizing). Press Enter when happy with your changes. It may take some time to apply the changes.
   6. Create a “swap” partition. It should be 1-2 times the amount of RAM you have (1000-2000MB). Swap helps with memory management and multi-tasking–you can read more about swap partitions (also called “Paging”) here.
   7. Create a root “/” partition (Ext3) for your Ubuntu installation (5-10GB). This will be where the Ubuntu OS and applications live.
   8. Create a “/home” partition (Ext3) for your user files (this should be at least 5-10GB though you could opt to make it bigger–keep reading for more info). Creating a “/home” partition will allow you to reinstall Ubuntu and/or do a clean install (instead of an upgrade) when a new version of Ubuntu comes along. One option when sizing this partition is to make “/home” serve as a shared partition between Ubuntu and Windows. To later read and write to this Ext3 partition from Windows, simply install Ext2 Installable File System for Windows.
   9. Select “Finish partitioning and write changes to disk”.

Note: If you opted to install Ubuntu with a USB Pen Drive, afterwards you will need to edit /etc/fstab and make sure that /media/cdrom0 points to the CD drive and not to the USB stick.

Open /etc/fstab for editing:

sudo gedit /etc/fstab

Find a line like this (usually the last line): /dev/sdXX /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

and comment it out by placing a # at the beginning (or simply delete it).

But its more easy now with wxDownload Fast, wxDownload Fast (also known as wxDFast) is an open source download manager. It is multi-platform and builds on Windows(2k,XP), Linux and Mac OS X(binary still not available). Besides that, it is a multi-threaded download manager. This means that it can split a file into several pieces and download the pieces simultaneously.

Created in C++ using the wxWidgets(wxWindows) library.

Features

• Faster downloads (with Segmented/Multi-threaded/Accelerated transfers)
• Download resuming (Pause and restart where you stopped)
• Download scheduling
• Organizes files you have already downloaded
• View server messages (HTTP, FTP, file://). No HTTPS support.
• Available in multiple languages and easily translated. Now available in Portuguese [Brazil], Spanish, English, German, Russian, Hungarian, Armenian, Indonesian and Dutch
• Connection to HTTP/FTP servers which require a password
• Calculates the MD5/SHA1 checksum of downloaded files so they can be easily verified
• Metalink support
• Firefox integration through FlashGot
• Can be used as a portable download manager (Windows only)
• Can be used over proxy servers(HTTP proxy support)

All this Ubuntu packages are available in http://www.getdeb.net/

- General information: Kernel version, Distribution release,Hostname/domainname, some important software versions.
- CPU information: Name/vendor, Frequency, L2 Cache, model/family/stepping.
- Memory information: Total, Free, Cached, Active/inactive, Swap.
- IDE information: Disks CD/DVD-roms, Model, Capacity, Cache.
- Filesystem information: Filesystem disk space usage(mounted partitions).
- Hardware information: Motherboard chipset, IDE interface, VGA contoller,
Multimedia controllers(sound cards), Ethernet cards.
- USB information: USB controllers.
- NVIDIA information: Graphic card model, AGP rate, Fast writes/SBA, Driver
version. (accelerated linux driver needed)
- Other information: Sound card details, Input devices, Screen resolution.

Install sysinfo in Ubuntu

Install sysinfo using the following command

sudo aptitude install sysinfo

This will complete the installation.

Using Sysinfo

If yo want to open go to Applications—>System Tools—>Sysinfo

Thanks for ubuntu geek