Installing LILO - Revision history

Mgloff at 19:10, 16 November 2015

2015-11-16T19:10:56Z

Kyoungmeyer: FinalDraft, one minor issue

2015-11-16T18:40:07Z

FinalDraft, one minor issue

Mdean: Modified per note and marked for Review.

2015-11-13T21:52:33Z

Modified per note and marked for Review.

Mdean: Fixed use of templates.

2015-11-10T18:07:37Z

Fixed use of templates.

Mdean: /* Workaround for the Ubuntu Automounter (and Possibly Others) */

2015-01-12T19:51:32Z

‎Workaround for the Ubuntu Automounter (and Possibly Others)

Mdean: Made use of new indent argument to the clo tag.

2014-11-18T04:18:44Z

Made use of new indent argument to the clo tag.

Mdean: testing

2014-11-18T04:10:46Z

testing

Mdean: Fixed bug.

2014-11-14T21:44:08Z

Fixed bug.

Mdean: Fixed template usage for blocks of commands.

2014-11-14T21:43:23Z

Fixed template usage for blocks of commands.

Mdean: Made use of new clio template.

2014-11-14T05:00:36Z

Made use of new clio template.

@@ Line 1: / Line 1: @@
-{{todo|Final Draft (12.16.13-03:15->MD+);(12.16.13-12:50->MD);(12.16.13-13:40->MD);(12.16.13-13:45->MW+);(12.16.13-18:20->KY+);(03.06.14-15:40->BS-);(04.11.14-16:40->BS+)(11.12.14->MD+)(11.10.2015-12:05->MD+);(11.13.2015-15:50->MD+);(11.16.2015-12:38->KY+)|Mike Dean|project=oe 4,oe 5,md,mw,ky,bs,FinalDraft}}
+{{todo|Complete (12.16.13-03:15->MD+);(12.16.13-12:50->MD);(12.16.13-13:40->MD);(12.16.13-13:45->MW+);(12.16.13-18:20->KY+);(03.06.14-15:40->BS-);(04.11.14-16:40->BS+)(11.12.14->MD+)(11.10.2015-12:05->MD+);(11.13.2015-15:50->MD+);(11.16.2015-12:38->KY+);(11.16.2015-13:10->MG+)|Mike Dean|project=oe 4,oe 5,md,mw,ky,bs,MG,Complete}}
 {{#seo:
@@ Line 95: / Line 95: @@
 {{clio|exit|hostname=debian}}
 {{clio|cd ..|pwd=/mnt/cfcard|hostname=debian}}
 {{clio|umount cfcard|pwd=/mnt|hostname=debian}}
 {{clos}}

@@ Line 1: / Line 1: @@
-{{todo|Review (12.16.13-03:15->MD+);(12.16.13-12:50->MD);(12.16.13-13:40->MD);(12.16.13-13:45->MW+);(12.16.13-18:20->KY+);(03.06.14-15:40->BS-);(04.11.14-16:40->BS+)(11.12.14->MD+)(11.10.2015-12:05->MD+);(11.13.2015-15:50->MD+)|Mike Dean|project=oe 4,oe 5,md,mw,ky,bs,Review}}
+{{todo|Final Draft (12.16.13-03:15->MD+);(12.16.13-12:50->MD);(12.16.13-13:40->MD);(12.16.13-13:45->MW+);(12.16.13-18:20->KY+);(03.06.14-15:40->BS-);(04.11.14-16:40->BS+)(11.12.14->MD+)(11.10.2015-12:05->MD+);(11.13.2015-15:50->MD+);(11.16.2015-12:38->KY+)|Mike Dean|project=oe 4,oe 5,md,mw,ky,bs,FinalDraft}}
 {{#seo:
@@ Line 105: / Line 105: @@
 On many Linux desktops, a memory card will be automounted when it is inserted.  While this is a nice convenience feature for most users, it comes at the expense of developers.  This automount feature can be a source of frustration for those who haven't already found a way around the issues it causes.
-Fortunately, we at EMAC have already found a method which works reliably on our recommended Linux distribution, Ubuntu 12.04 LTS, and have documented it here. On other systems, such as Debian, a workaround may not be needed.  For a system which automounts, see below.
+Fortunately, we at EMAC have already found a method which works reliably on our recommended Linux distribution, Ubuntu 14.04 LTS, and have documented it here. On other systems, such as Debian, a workaround may not be needed.  For a system which automounts, see below.
 <cl>1. Insert the flash card into the development machine's card reader and wait for the file browser window to appear.  If a messagebox appears asking you to choose what to do, tell it to open a file browser for browsing the files on the card.

@@ Line 1: / Line 1: @@
-{{todo|Revise - Revise with tips on reinstalling LILO when installing a new kernel (12.16.13-03:15->MD+);(12.16.13-12:50->MD);(12.16.13-13:40->MD);(12.16.13-13:45->MW+);(12.16.13-18:20->KY+);(03.06.14-15:40->BS-);(04.11.14-16:40->BS+)(11.12.14->MD+)(11.10.2015-12:05->MD+)|Mike Dean|project=oe 4,oe 5,md,SEOKWREV,mw,ky,bs,Revise}}
+{{todo|Review (12.16.13-03:15->MD+);(12.16.13-12:50->MD);(12.16.13-13:40->MD);(12.16.13-13:45->MW+);(12.16.13-18:20->KY+);(03.06.14-15:40->BS-);(04.11.14-16:40->BS+)(11.12.14->MD+)(11.10.2015-12:05->MD+);(11.13.2015-15:50->MD+)|Mike Dean|project=oe 4,oe 5,md,mw,ky,bs,Review}}
 {{#seo:
@@ Line 24: / Line 24: @@
 The <code>-C</code> (capital C) switch tells <code>lilo</code> to use the configuration file specified after the switch when installing itself.
 ===Installing LILO Onto a Removable Drive===

@@ Line 1: / Line 1: @@
-{{todo|Revise - Revise with tips on reinstalling LILO when installing a new kernel (12.16.13-03:15->MD+);(12.16.13-12:50->MD);(12.16.13-13:40->MD);(12.16.13-13:45->MW+);(12.16.13-18:20->KY+);(03.06.14-15:40->BS-);(04.11.14-16:40->BS+)(11.12.14->MD+)|Mike Dean|project=oe 4,oe 5,md,SEOKWREV,mw,ky,bs,Revise}}
+{{todo|Revise - Revise with tips on reinstalling LILO when installing a new kernel (12.16.13-03:15->MD+);(12.16.13-12:50->MD);(12.16.13-13:40->MD);(12.16.13-13:45->MW+);(12.16.13-18:20->KY+);(03.06.14-15:40->BS-);(04.11.14-16:40->BS+)(11.12.14->MD+)(11.10.2015-12:05->MD+)|Mike Dean|project=oe 4,oe 5,md,SEOKWREV,mw,ky,bs,Revise}}
 {{#seo:
@@ Line 17: / Line 17: @@
 The easiest way to install LILO onto the local system's Master Boot Record, using the default configuration file (<code>/etc/lilo.conf</code>), is to type:
-{{cli|root@oe:/# lilo|hostname=oe}}
+{{cli|lilo|hostname=oe}}
 This method works well for systems where only a small change is required to the default configuration, but is not often what is desired on an embedded system.  Many times, an alternate file will be used to store the new configuration so that a breaking change to a known-good configuration file will not leave the system without a usable configuration file.  If a configuration file in an alternate location needs to be used, it will have to be specified like this:
-{{cli|root@oe:/# lilo -C /etc/alternate_lilo_configuration_file.conf|hostname=oe}}
+{{cli|lilo -C /etc/alternate_lilo_configuration_file.conf|hostname=oe}}
 The <code>-C</code> (capital C) switch tells <code>lilo</code> to use the configuration file specified after the switch when installing itself.
@@ Line 38: / Line 38: @@
   i. Insert the flash card into the development system's card reader.
   * Find out where the device node for the card was created (assuming the development machine uses <code>udev</code>) by using <code>dmesg</code>.
-{{clo|indent=2}}
+{{clo|indent=1}}
 {{clio|dmesg | tail -n 15|hostname=debian|username=user}}
 ...<br />
@@ Line 56: / Line 56: @@
 {{clos}}
   * Since the device node <code>sdb1</code> was created for the flash card (in this example), that device needs to be mounted somewhere accessible.  In this example, the <code>/mnt/cfcard</code> directory is used:
-{{clo|indent=2}}
+{{clo|indent=1}}
 {{clio|sudo su|hostname=debian|username=user}}
 [sudo] password for user:<br />
@@ Line 64: / Line 64: @@
 {{clos}}
 * Bind mount the device nodes into the filesystem so that LILO will be able to communicate with the flash card:
-{{clo|indent=1}}
+{{clo}}
 {{clio|cd /mnt/cfcard|hostname=debian}}
 {{clio|mount --bind /dev dev/|pwd=/mnt/cfcard|hostname=debian}}
@@ Line 71: / Line 71: @@
 * <code>chroot</code> into the filesystem:
-{{clo|indent=1}}
+{{clo}}
 {{clio|chroot .|pwd=/mnt/cfcard|hostname=debian}}
 {{clio||hostname=debian}}
@@ Line 77: / Line 77: @@
 * Run <code>lilo</code> with the appropriate LILO configuration file.  Be sure to double check to ensure that the configuration file is correct, because a mistake here could render the desktop system unbootable.
-{{clo|indent=1}}
+{{clo}}
 {{clio|lilo -C /etc/lilo.conf.boot|hostname=debian}}
 Warning: '/proc/partitions' does not exist, disk scan bypassed<br />
@@ Line 86: / Line 86: @@
 Note that the warning here is normal, because LILO is being installed inside a chroot which doesn't have a mounted <code>/proc</code> virtual filesystem.
 * Exit the chroot and unmount the device:
-{{clo|indent=1}}
+{{clo}}
 {{clio|exit|hostname=debian}}
 {{clio|cd ..|pwd=/mnt/cfcard|hostname=debian}}
@@ Line 106: / Line 106: @@
 {{cli|sudo mkdir /mnt/cfcard|username=user|hostname=ubuntu}}
 * Find out the device name of the card by looking for the location where the card was mounted.  The file browser window will list the name of the card under Devices in the left pane.  Often times, the name will be EMAC_OE.  Look for this name in the output of the <code>df</code> command:
-{{clo|indent=1}}
+{{clo}}
 {{clio|df -hT | grep EMAC|username=user|hostname=ubuntu}}
 Filesystem                      Type      Size  Used Avail Use% Mounted on<br />
@@ Line 113: / Line 113: @@
 * From the output of this command, we can see that the <code>/media/EMAC_OE</code> mountpoint was mounted onto the <code>/dev/sdb1</code> device.  Therefore, this is the device needed for the next step.
 * Now, switch to the root user account (if not already running as root) and mount the device on the directory from step 3, without unmounting it first:
-{{clo|indent=1}}
+{{clo}}
 {{clio|sudo su|username=user|hostname=ubuntu}}
@@ Line 122: / Line 122: @@
 * Bind mount the host system's <code>/dev</code> directory to the cfcard's <code>/dev</code> directory.  This will provide the device node file that will be needed for LILO to be able to talk to the flash card.
-{{clo|indent=1}}
+{{clo}}
 {{clio|cd /mnt/cfcard|hostname=ubuntu}}
 {{clio|mount --bind /dev dev/|pwd=/mnt/cfcard|hostname=ubuntu}}
@@ Line 129: / Line 129: @@
 * Now, use the <code>chroot</code> command to make the directory where the card is mounted the effective root directory for this terminal session:
-{{clo|indent=1}}
+{{clo}}
 {{clio|chroot .|pwd=/mnt/cfcard|hostname=ubuntu}}
 {{clio||pwd=/mnt/cfcard|hostname=ubuntu}}
@@ Line 137: / Line 137: @@
 {{warning|If you overwrite the bootloader on your desktop, '''it will render your desktop system unbootable!'''  Make sure to double check this if you value the ability to boot your desktop.}}
 * When you are sure you're using the right device node, run LILO to install the bootloader:
-{{clo|indent=1}}
+{{clop}}
-{{clio|lilo -C /etc/lilo.conf.boot|hostname=ubuntu}}
+{{cliop|lilo -C /etc/lilo.conf.boot|hostname=ubuntu}}
-Warning: '/proc/partitions' does not exist, disk scan bypassed<br />
+Warning: '/proc/partitions' does not exist, disk scan bypassed
-Added emac-oe *<br />
+Added emac-oe *
-One warning was issued.<br />
+One warning was issued.
-{{clio||hostname=ubuntu}}
+{{cliop||hostname=ubuntu}}
-{{clos}}
+{{closp}}
 The warning, in this case, is normal.  It appears because this is a fake "running system," which means the virtual files in the <code>/proc/</code> filesystem aren't mounted and able to provide information; hence, the non-existence of the <code>/proc/partitions</code> file.
 * Now, you need to umount the device:
-{{clo|indent=1}}
+{{clo}}
 {{clio|exit|hostname=ubuntu}}
 {{clio|cd ..|pwd=/mnt/cfcard|hostname=ubuntu}}

@@ Line 124: / Line 124: @@
 {{clo|indent=1}}
 {{clio|cd /mnt/cfcard|hostname=ubuntu}}
 {{clio|mount --bind /dev dev/|pwd=/mnt/cfcard|hostname=ubuntu}}
 {{clio||pwd=/mnt/cfcard|hostname=ubuntu}}