Changes

Jump to navigation Jump to search
no edit summary
Line 79: Line 79:  
= Limey Linux Instllation on a Large Compact Flash Card =
 
= Limey Linux Instllation on a Large Compact Flash Card =
   −
=== Written by Randy Hammock - KC6HUR ===
+
=== This section was Written by Randy Hammock - KC6HUR ===
 +
 
 
The following is the procedure I use to load Limey Linux onto a CF card. Since the CF card I was configuring in this example is significantly larger than Limey boot image, I also configured the remaining space on the CF card to be a Linux partition that can be used for additional storage (can you say audio files?). This procedure has been used to configure CF cards up to 4GB without any problems.
 
The following is the procedure I use to load Limey Linux onto a CF card. Since the CF card I was configuring in this example is significantly larger than Limey boot image, I also configured the remaining space on the CF card to be a Linux partition that can be used for additional storage (can you say audio files?). This procedure has been used to configure CF cards up to 4GB without any problems.
   Line 88: Line 89:  
Once you have down loaded the image from the Limey Linux web site and  un-tarred it, you need to copy the image to the CF card using the Linux '''dd''' command. '''Note: You must be root or use the sudo command for the following procedures to work:'''
 
Once you have down loaded the image from the Limey Linux web site and  un-tarred it, you need to copy the image to the CF card using the Linux '''dd''' command. '''Note: You must be root or use the sudo command for the following procedures to work:'''
   −
<code>root@sierra:/home/rhammock# dd if=cfimg-d201gly2-1.0.6 of=/dev/sdc</code>
+
    root@sierra:/home/rhammock# dd if=cfimg-d201gly2-1.0.6 of=/dev/sdc
 
+
    250880+0 records in
<code>250880+0 records in</code>
+
    250880+0 records out
 
+
    128450560 bytes (128 MB) copied, 233.421 s, 550 kB/s
<code>250880+0 records out</code>
  −
 
  −
<code>128450560 bytes (128 MB) copied, 233.421 s, 550 kB/s</code>
      
The Limey Linux image has now been copied onto the CF card. We will now create a Linux partition so that remainder of the card can be used for additional storage.
 
The Limey Linux image has now been copied onto the CF card. We will now create a Linux partition so that remainder of the card can be used for additional storage.
   −
<code>root@sierra:/home/rhammock# fdisk /dev/sdc</code>
+
    root@sierra:/home/rhammock# fdisk /dev/sdc
   −
<code>The number of cylinders for this disk is set to 4036.</code>
+
The number of cylinders for this disk is set to 4036.
 
+
There is nothing wrong with that, but this is larger than 1024,
<code>There is nothing wrong with that, but this is larger than 1024,</code>
+
and could in certain setups cause problems with:
 
+
1) software that runs at boot time (e.g., old versions of LILO)
<code>and could in certain setups cause problems with:</code>
+
2) booting and partitioning software from other OSs
 
+
(e.g., DOS FDISK, OS/2 FDISK)
<code>1) software that runs at boot time (e.g., old versions of LILO)</code>
  −
 
  −
<code>2) booting and partitioning software from other OSs</code>
  −
 
  −
<code>(e.g., DOS FDISK, OS/2 FDISK)</code>
      
Using the '''p''' command we can see that about 25% of the CF card is being used by the Limey Linux boot partition:
 
Using the '''p''' command we can see that about 25% of the CF card is being used by the Limey Linux boot partition:
   −
<code>Command (m for help): p</code>
+
Command (m for help): p
 
  −
<code>Disk /dev/sdc: 512 MB, 512483328 bytes</code>
  −
 
  −
<code>4 heads, 62 sectors/track, 4036 cylinders</code>
  −
 
  −
<code>Units = cylinders of 248 * 512 = 126976 bytes</code>
     −
<code>Disk identifier: 0x00000000</code>
+
Disk /dev/sdc: 512 MB, 512483328 bytes
 +
4 heads, 62 sectors/track, 4036 cylinders
 +
Units = cylinders of 248 * 512 = 126976 bytes
 +
Disk identifier: 0x00000000
   −
<code>Device Boot     Start         End     Blocks   Id System</code>
+
Device Boot Start End Blocks Id System
 
+
/dev/sdc1 * 1 1011 125333 6 FAT16
<code>/dev/sdc1   *           1       1011     125333   6 FAT16</code>
      
The '''n''' command is used to create a new partition. This will be a primary partition and use number 2 since 1 is the boot partition. Just press Enter for the First cylinder and Last cylinder questions to accept the default conditions which be to use the remainder of the CF card.
 
The '''n''' command is used to create a new partition. This will be a primary partition and use number 2 since 1 is the boot partition. Just press Enter for the First cylinder and Last cylinder questions to accept the default conditions which be to use the remainder of the CF card.
   −
<code>Command (m for help): n</code>
+
Command (m for help): n
 
+
Command action
<code>Command action</code>
+
e extended
 
+
p primary partition (1-4)
<code>e   extended</code>
+
p
 
+
Partition number (1-4): 2
<code>p   primary partition (1-4)</code>
+
First cylinder (1012-4036, default 1012):
 
+
Using default value 1012
<code>p</code>
+
Last cylinder or +size or +sizeM or +sizeK (1012-4036, default 4036):
 
+
Using default value 4036
<code>Partition number (1-4): 2</code>
  −
 
  −
<code>First cylinder (1012-4036, default 1012):</code>
  −
 
  −
<code>Using default value 1012</code>
  −
 
  −
<code>Last cylinder or +size or +sizeM or +sizeK (1012-4036, default 4036):</code>
  −
 
  −
<code>Using default value 4036</code>
      
Use the '''p''' command to examine our current configuration.
 
Use the '''p''' command to examine our current configuration.
   −
<code>Command (m for help): p</code>
+
Command (m for help): p
 
  −
<code>Disk /dev/sdc: 512 MB, 512483328 bytes</code>
  −
 
  −
<code>4 heads, 62 sectors/track, 4036 cylinders</code>
  −
 
  −
<code>Units = cylinders of 248 * 512 = 126976 bytes</code>
  −
 
  −
<code>Disk identifier: 0x00000000</code>
     −
<code>Device    Boot      Start      End      Blocks  Id  System</code>
+
Disk /dev/sdc: 512 MB, 512483328 bytes
 +
4 heads, 62 sectors/track, 4036 cylinders
 +
Units = cylinders of 248 * 512 = 126976 bytes
 +
Disk identifier: 0x00000000
   −
<code>/dev/sdc1   *           1       1011     125333   6 FAT16</code>
+
Device Boot Start End Blocks Id System
 
+
/dev/sdc1 * 1 1011 125333 6 FAT16
<code>/dev/sdc2           1012       4036     375100   83 Linux</code>
+
/dev/sdc2 1012 4036 375100 83 Linux
    
We must now write this configuration out to the CF card using the '''w''' command.
 
We must now write this configuration out to the CF card using the '''w''' command.
   −
<code>Command (m for help): w</code>
+
Command (m for help): w
 +
The partition table has been altered!
   −
<code>The partition table has been altered!</code>
+
Calling ioctl() to re-read partition table.
   −
<code>Calling ioctl() to re-read partition table.</code>
+
WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
 +
The kernel still uses the old table.
 +
The new table will be used at the next reboot.
 +
Syncing disks.
   −
<code>WARNING: Re-reading the partition table failed with error 16: Device or resource busy.</code>
  −
  −
<code>The kernel still uses the old table.</code>
  −
  −
<code>The new table will be used at the next reboot.</code>
  −
  −
<code>Syncing disks.</code>
      
We must now format the newly created partition. To do this we will use the '''mkfs''' (Make Filesystem) command. From above, we see that the Linux partition is located on /dev/sdc2 (the second partition on /dev/sdc). Remember, your system might have the CF card configured as a different device.
 
We must now format the newly created partition. To do this we will use the '''mkfs''' (Make Filesystem) command. From above, we see that the Linux partition is located on /dev/sdc2 (the second partition on /dev/sdc). Remember, your system might have the CF card configured as a different device.
   −
<code>root@sierra:/home/rhammock# mkfs -t ext2 /dev/sdc2</code>
+
root@sierra:/home/rhammock# mkfs -t ext2 /dev/sdc2
 
+
mke2fs 1.40.8 (13-Mar-2008)
<code>mke2fs 1.40.8 (13-Mar-2008)</code>
+
Filesystem label=
 
+
OS type: Linux
<code>Filesystem label=</code>
+
Block size=1024 (log=0)
 
+
Fragment size=1024 (log=0)
<code>OS type: Linux</code>
+
93840 inodes, 375100 blocks
 
+
18755 blocks (5.00%) reserved for the super user
<code>Block size=1024 (log=0)</code>
+
First data block=1
 
+
Maximum filesystem blocks=67633152
<code>Fragment size=1024 (log=0)</code>
+
46 block groups
 
+
8192 blocks per group, 8192 fragments per group
<code>93840 inodes, 375100 blocks</code>
+
2040 inodes per group
 
+
Superblock backups stored on blocks:
<code>18755 blocks (5.00%) reserved for the super user</code>
+
8193, 24577, 40961, 57345, 73729, 204801, 221185
 
  −
<code>First data block=1</code>
  −
 
  −
<code>Maximum filesystem blocks=67633152</code>
  −
 
  −
<code>46 block groups</code>
  −
 
  −
<code>8192 blocks per group, 8192 fragments per group</code>
  −
 
  −
<code>2040 inodes per group</code>
  −
 
  −
<code>Superblock backups stored on blocks:</code>
  −
 
  −
<code>8193, 24577, 40961, 57345, 73729, 204801, 221185</code>
     −
<code>Writing inode tables: done</code>
+
Writing inode tables: done
 +
Writing superblocks and filesystem accounting information: done
   −
<code>Writing superblocks and filesystem accounting information: done</code>
+
This filesystem will be automatically checked every 31 mounts or
 +
180 days, whichever comes first. Use tune2fs -c or -i to override.
   −
<code>This filesystem will be automatically checked every 31 mounts or</code>
     −
<code>180 days, whichever comes first.  Use tune2fs -c or -i to override.</code>
      
Because Ubuntu remounted the boot partition and opened a File Browser window for that partition when we finished creating the Linux partition, close the File Browser window then unmount the device as was done before.
 
Because Ubuntu remounted the boot partition and opened a File Browser window for that partition when we finished creating the Linux partition, close the File Browser window then unmount the device as was done before.

Navigation menu