[Emc-commit] documents/lyx User_BDI_Install.lyx,1.4,1.5

[<ray...@us...>]

Update of /cvsroot/emc/documents/lyx
In directory sc8-pr-cvs1:/tmp/cvs-serv16707

Modified Files:
	User_BDI_Install.lyx 
Log Message:
added dual boot and more on live

Index: User_BDI_Install.lyx
===================================================================
RCS file: /cvsroot/emc/documents/lyx/User_BDI_Install.lyx,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** User_BDI_Install.lyx	21 Jul 2003 13:15:02 -0000	1.4
--- User_BDI_Install.lyx	13 Aug 2003 21:24:29 -0000	1.5
***************
*** 89,100 ****
   this distribution.
   This is the greatest advantage of the 2.xx series.
!  It will run well on very old very slow computers.
  \layout Standard
  
! It's biggest limitation is in the graphical interface stuff which will seem
!  a bit dated if you are acustomed to state of the art systems.
!  A second limitation for2.xx is that it was set up for hardware a couple
   of years ago.
   This means that it is limited in the kinds of devices that it will recognize.
  \layout Standard
  
--- 89,104 ----
   this distribution.
   This is the greatest advantage of the 2.xx series.
!  It will run well on very old very slow computers as long as they have a
!  pentium processor.
  \layout Standard
  
! The biggest limitation of the 2.xx series is in the graphical interface stuff
!  which will seem a bit dated if you are acustomed to state of the art systems.
!  A second limitation for 2.xx is that it was set up for hardware a couple
   of years ago.
   This means that it is limited in the kinds of devices that it will recognize.
+  This is most often true for the newest on-board graphics and network drivers.
+  If you have these, the basic install will go okay but you will have to
+  cast about the web to find drivers for them.
  \layout Standard
  
***************
*** 123,130 ****
   will be more than you need.
   With it you will get some of the features that you may want for networking
!  and for browsing about the web.
   You should think of the TNG as an experimental version rather than one
   intended for the single task of making a machine move.
!  You should also think that this version may not be kept up to date.
  \layout Subsection
  
--- 127,142 ----
   will be more than you need.
   With it you will get some of the features that you may want for networking
!  and for browsing the web.
   You should think of the TNG as an experimental version rather than one
   intended for the single task of making a machine move.
!  You should also know before you purchase it, that this version may not
!  be kept up to date.
!  As of March 2003, Paul has indicated that he will probably not be maintaining
!  it any more than it was at that time.
!  We may make updates rpms available for the emc and rcslib portions of this
!  release.
!  These will be held in the dropbox at linuxcnc.org and will be named TNG-(emc
!  or rcslib)-update(datecode).rpm.
!  Source will also be available as .s.rpm.
  \layout Subsection
  
***************
*** 150,158 ****
  \layout Standard
  
! To run from the CD you pop in in the cd drive and reboot your computer.
!  It will start up Linux, a simple window manager, and the EMC without doing
!  anything to your computer.
!  The only big requirement is that your computer be able to boot from a CDROM
!  device.
  \layout Section
  
--- 162,168 ----
  \layout Standard
  
! The most recent copies of this include some ways to customize it so that
!  you can use one of these for a specific machine.
!  
  \layout Section
  
***************
*** 387,392 ****
  BDI Live will boot and run an EMC from the CDROM device if your computer
   will boot from CD.
!  This mode of operation requires not space on a hard drive and does not
!  alter the installation of any other OS on the computer.
  \layout Standard
  
--- 397,402 ----
  BDI Live will boot and run an EMC from the CDROM device if your computer
   will boot from CD.
!  This mode of operation requires no space on a hard drive and does not alter
!  the installation of any other OS on the computer.
  \layout Standard
  
***************
*** 394,398 ****
   you to edit the INI and RUN files and save VAR and TBL values.
   The addition of these directories to your hard drive do not alter the proper
!  operation of any other OS on that hard drive.
  \layout Section
  
--- 404,577 ----
   you to edit the INI and RUN files and save VAR and TBL values.
   The addition of these directories to your hard drive do not alter the proper
!  operation of any other OS used for that hard drive.
! \layout Subsection
! 
! Boot Options
! \layout Standard
! 
! At boot you have the possibility to enter bootoptions.
!  First you specify a label:
! \layout Description
! 
! morphix This is the default way of booting morphix.
!  
! \layout Description
! 
! morphix-ide which disables ide-scsi if you have problems with reading from
!  a cdrom burner of this type.
! \layout Description
! 
! fb1024x768 To use fixed framebuffer graphics of this resolution
! \layout Description
! 
! fb800x600 To use fixed framebuffer graphics at this resolution
! \layout Description
! 
! expert Expert lets you configure your hardware interactively.
!  Then you specify zero or more of the following options, like so: morphix
!  wheelmouse screen=1280x1024
! \layout Standard
! 
! The expert bootoptions:
! \layout Description
! 
! wheelmouse Enable wheelmouse support
! \layout Description
! 
! forceusb=yes Forces USB to be loaded, fixes certain USB problems.
! \layout Description
! 
! lang=us / lang=bg|be|ch|cn|cs|cz|da|de|dk|es|fi|fr|it|ja|nl|pl|ru|sk|tr|tw|uk|us
!  might not work for everyone
! \layout Description
! 
! keyboard=us loads keymap for a certain language as above.
! \layout Standard
! 
! console keyboard boot options
! \layout Description
! 
! xkeyboard=us X keyboard
! \layout Description
! 
! screen=1280x1024 Define XFree resolution (1600x1200 etc)
! \layout Description
! 
! depth=24 Define XFree colordepth
! \layout Description
! 
! xvrefresh=60 Set vertical refresh rate
! \layout Description
! 
! hsync=60 Set horizontal sync rate (not tested)
! \layout Description
! 
! xmodule=ati|radeon|fbdev|vesa|savage|s3|nv|i810|mga|svga|tseng Define XFree
!  v4 module
! \layout Description
! 
! 2 Runlevel 2, doesn't load mainmodules, debugging.
! \layout Description
! 
! floppyconfig start "morphix.sh" from floppydisk
! \layout Description
! 
! no?? noapic noagp noapm nodma nomce nofirewire nopcmcia noscsi noswap nousb
!  nosmp noaudio Skips loading of item
! \layout Description
! 
! pci=biosirq Will force the use of the BIOS assigned Interrupt ReQuests on
!  the PCI bus.
!  Possible cure for non-functioning hardware.
!  Very handy for unruly IRQ conflicts.
!  Look at dmesg and cat /proc/pci to find out if you have any such troubles.
! \layout Description
! 
! gmt|uce Hardware clock is set to GMT/UCE.
! \layout Description
! 
! home=scan Set home directory.
!  'scan' will search for morphix.img in the root of all partitions.
!  Be carefull when creating the home-dir, Do NOT use the entire partition
!  unless you know what you are doing.
!  Other options could be, home=/dev/hda1 home=/mnt/hda1.
! \layout Description
! 
! vga=normal Boot without vesa-framebuffer.
!  This is default, for the 'old' bootscreen use vga=791
! \layout Description
! 
! alsa attempts to autodetect alsa
! \layout Description
! 
! alsa=alsa-module attempts to load a soundcard with this alsa module.
! \layout Description
! 
! home=/dev/device / home=/mnt/device / home=scan Attempts to load the persistanth
! ome from fat/ext2/ext3/reiser/xfs device.
! \layout Description
! 
! floppyconfig Starts the morphix.sh file from floppy during boottime, for
!  quick&dirty hacks.
!  
! \layout Description
! 
! blocktrans=yes Keeps translucency from being loaded, debugging only (your
!  system won't correctly boot X with this option)
! \layout Description
! 
! testcd Checks if the CD was burned correctly.
! \layout Description
! 
! newx11 Tries to detect different modelines for X, up for testing.
! \layout Description
! 
! toram Tries to copy the cdrom to ram at boottime, up for testing.
!  Takes a while to copy to ram, limited by speed of cd/dvd.
!  
! \layout Description
! 
! tohd=hda1 Tries to copy the cdrom to harddisk, a "poor man's installer",
!  for when there is enough harddisk space but not enough ram to boot, for
!  speeding up.
!  up for testing.
! \layout Description
! 
! fromhd=hda1 Boots from a system setup using tohd.
! \layout Description
! 
! modules-disk This patch adds the interactive functionality like known from
!  expert mode to insert a disk with modules to find KNOPPIX-Image, but unlike
!  expert mode this has only effect on linuxrc and knoppix-autoconfig runs
!  automatically ...".
!  Use at your own risk ;)
! \layout Standard
! 
! Booting with "morphix-ide" might help those that have had trouble booting
!  in the past.
!  If this works for the majority, then we will make it the default.
!  The current default uses SCSI emulation for the CD-ROM drive which can
!  cause a few problems.
! \layout Standard
! 
! Also supported is custom ini, var, tbl, and nml files - If any emc.* are
!  found in /cdrom/emc, these are copied across to /usr/local/emc and added
!  to the menu list.
!  N.B.
!  ini files *must* be run with "generic.run -ini foo.ini" due in part to the
!  BDI-Live changes to the run scripts.
!  The Menu & tool bar entries use a name extracted from the MACHINE variable
!  within the emc.ini.
!  Any files found in /cdrom/emc/programs will be copied across to /usr/local/emc/
! programs where they will be accessable by the usual methods.
!  Also included is the ability to run a customisation script so that menus,
!  icons, etc, can be modified to suit a target customer.
!  dos2unix has been added just in case any files have been edited on a Windows
!  box and the CD has been remastered with MagicISO (or similar Win software).
! \layout Standard
! 
! The customising script can be used to modify the menu/tool bar, replace
!  icons, or secretly install Linux on the host box.
!  
  \layout Section
  
***************
*** 408,411 ****
--- 587,904 ----
  
  (add this and include the lilo problems for the early release candidates)
+ \layout Standard
+ 
+ BDI Install Guide
+ \layout Section
+ 
+ Dual boot Introduction
+ \begin_float footnote 
+ \layout Standard
+ 
+ This section is a copyright work of Sagar Behere, July 2003.
+  This document is released under the GNU Free Documentation License.
+  See Appendex for detail.
+  
+ \emph on 
+ be...@sa...
+ \end_float 
+ \layout Standard
+ 
+ First of all, the title is a misnomer.
+  BDI stands for 
+ \emph on 
+ brain dead install
+ \emph default 
+  so you shouldn't need a guide to its installation.
+  However, there are times when you want a BDI install to coexist with your
+  existing GNU/Linux or Microsoft installations.
+  At such times it takes a little tweaking to boot BDI smoothly.
+  This document explains the procedure.
+ \layout Standard
+ 
+ Firstly, backup everything critical.
+  It is extremely improbable that there will be data loss due to something
+  going wrong, but still, it is preferable to err on the side of caution.
+  Data will be safe, but your PC may not boot.
+  This is often enough to throw people into violent fits of panic.
+  I mention it here to reassure you that in case something goes wrong (unlikely),
+  your data is still there :-)
+ \layout Standard
+ 
+ People will boot into their OS of choice, normally through one of the following
+  four methods: LILO, Loadlin, GRUB or a third party boot loader.
+  I have no experience with the last two, so we'll concentrate on the rest.
+  
+ \layout Standard
+ 
+ Throughout this document I'll be assuming that you have either Microsoft
+  Windows 95/98 and/or GNU/Linux already installed.
+ \layout Subsection
+ 
+ The BDI install
+ \layout Standard
+ 
+ Make a separate partition to install BDI on.
+  It does not matter if this partition is on a separate disk, primary or
+  logical.
+  (If you don't know what this means, you don't need to bother with it) A
+  partition size of about 2.5 GB should be safe for almost all installs.
+  Now install the BDI as you would install any regular GNU/Linux distribution,
+  with the exception that if you already have some version of GNU/Linux,
+  you should not install LILO.
+ \layout Standard
+ 
+ IMPORTANT:
+ \series bold 
+  DO *NOT* INSTALL LILO IF YOU ALREADY HAVE GNU/LINUX INSTALLED!!!
+ \layout Standard
+ 
+ Not installing LILO can be achieved by un-checking a box on the same screen
+  where it asks you if you want to install LILO on the MBR or on another
+  partition.
+ \layout Standard
+ 
+ If you have only MS Windows installed, then you should install LILO into
+  the MBR.
+ \layout Standard
+ 
+ Choose your packages, setup the video and complete the installation.
+ \layout Subsection
+ 
+ Booting the BDI
+ \layout Standard
+ 
+ A little theory here.
+ \layout Standard
+ 
+ At this point, you have installed BDI onto your hard disk, but you lack
+  the ability to boot into it.
+  When your PC boots, here is what actually happens.
+  A small program called the boot loader looks around for a 
+ \emph on 
+ kernel
+ \emph default 
+ .
+  The kernel is the core of the operating system.
+  When you say 
+ \begin_inset Quotes eld
+ \end_inset 
+ 
+ linux
+ \begin_inset Quotes erd
+ \end_inset 
+ 
+ , you are (should be) referring to this kernel.
+  Now, once the boot loader chooses a kernel, it loads this into memory and
+  then all kinds of interesting things happen, until you find yourself staring
+  at a login screen.
+  When you installed the BDI, you got a kernel which is to be used along
+  with it.
+  However, you have not yet told your boot-loader where this kernel is and
+  how it should be loaded.
+ \layout Standard
+ 
+ The technique for instructing the various boot-loaders will now be covered.
+ \layout Subsubsection
+ 
+ LILO
+ \layout Standard
+ 
+ LILO stands for LInux LOader.
+  The name is deceptive.
+  LILO can also boot other operating systems, like MS windows.
+  If you have GNU/Linux installed, you might be using LILO to boot into it,
+  or your windows installation.
+  The configuration file '/etc/lilo.conf' decides how LILO behaves.
+  The file will have a section like
+ \layout LyX-Code
+ 
+ image=/boot/vmlinuz 
+ \layout LyX-Code
+ 
+ label=linux 
+ \layout LyX-Code
+ 
+ read-only 
+ \layout LyX-Code
+ 
+ root=/dev/hda6
+ \layout Standard
+ 
+ The image= line tells LILO where the kernel is located.
+  In this case, the kernel is the file 
+ \begin_inset Quotes eld
+ \end_inset 
+ 
+ vmlinuz
+ \begin_inset Quotes erd
+ \end_inset 
+ 
+ , in the /boot directory.
+  (If you check out this file, you might find that it is a link to another
+  file.
+  That's quite alright).
+  The label= field decides what text is displayed at the LILO prompt.
+  
+ \begin_inset Quotes eld
+ \end_inset 
+ 
+ read-only
+ \begin_inset Quotes erd
+ \end_inset 
+ 
+  means that the / partition should initially be loaded in read-only mode.
+  We need not go into the reason for this, but it is essential.
+  The root= line specifies the root (/) partition which the kernel should
+  work with.
+  There can be a number of sections like this, one for each kernel you have.
+ \layout Standard
+ 
+ Can you now guess how to make the BDI work with LILO? Its simple.
+ \layout Standard
+ 
+ You need to tell LILO where the BDI kernel is.
+  So get a copy of the BDI kernel and copy it some place where LILO can find
+  it.
+  For example, copy it into the /boot directory of your current GNU/Linux
+  installation.
+  To do this, you'll have to access the partition where BDI is installed,
+  grab its kernel from there, and copy it to /boot.
+  Lets assume that BDI is installed on /dev/hda7.
+  So
+ \layout LyX-Code
+ 
+ # mkdir /bdi
+ \layout LyX-Code
+ 
+ # mount /dev/hda7 /bdi
+ \layout LyX-Code
+ 
+ # cp -v /bdi/boot/vmlinuz-x.x.xxx-xxx /boot/bdi
+ \layout LyX-Code
+ 
+ # umount /bdi
+ \layout LyX-Code
+ 
+ # rmdir /bdi
+ \layout Standard
+ 
+ Here, vmlinuz-x.x.xxx-xxx is the file to which /bdi/boot/vmlinuz points to.
+  For example, in BDI-2.18, it is vmlinuz-2.2.18-rtl3.0.
+  The file /boot/bdi is your required kernel, and its root partition is /dev/hda7.
+  Now add a section like the one below into your /etc/lilo.conf (back it up
+  first)
+ \layout LyX-Code
+ 
+ image=/boot/bdi 
+ \layout LyX-Code
+ 
+ label=BDI
+ \layout LyX-Code
+ 
+ read-only 
+ \layout LyX-Code
+ 
+ root=/dev/hda7
+ \layout Standard
+ 
+ Now, you have to make LILO read the configuration file and understand the
+  new settings.
+  So run the command
+ \layout LyX-Code
+ 
+ # /sbin/lilo -v
+ \layout Standard
+ 
+ The next time you boot, you'll see a label 
+ \begin_inset Quotes eld
+ \end_inset 
+ 
+ BDI
+ \begin_inset Quotes erd
+ \end_inset 
+ 
+ .
+  Hitting it will take you to the BDI.
+ \layout Subsubsection
+ 
+ Loadlin
+ \layout Standard
+ 
+ Loadlin is a DOS based program that is used to boot the linux kernel.
+  If you are using Loadlin, you must be already proficient in its use.
+  Simply copy the BDI kernel into your DOS dir, and use a command like 
+ \layout LyX-Code
+ 
+ loadlin bdi root=/dev/hda7
+ \layout Subsection
+ 
+ If something goes wrong
+ \layout Standard
+ 
+ Ok.
+  Something happened and the system won't boot anymore.
+  It happens to all of us.
+  The important thing is not to panic.
+  Go get a coffee or take a walk.
+  Come back when you are calm once again :-)
+ \layout Standard
+ 
+ If you only had windows previously, then use its boot disk (you have one,
+  don't you?) or boot from the Windows CD and at the command prompt type
+  
+ \layout LyX-Code
+ 
+ c:> fdisk /mbr
+ \layout Standard
+ 
+ This will return things to their normal state.
+ \layout Standard
+ 
+ Or, you might have GNU/Linux previously installed, and now LILO fails to
+  boot into any OS.
+ \layout Standard
+ 
+ In this case, boot into the first install CD (or the BDI CD) and go into
+  rescue mode when you reach a prompt.
+  Booting into rescue mode is pretty simple.
+  Instructions are given on the screen.
+  Most of the times, it is simply a matter of typing
+ \layout LyX-Code
+ 
+ linux rescue
+ \layout Standard
+ 
+ at the prompt.
+ \layout Standard
+ 
+ Once into rescue mode, you'll land up at a shell.
+  Mount your original GNU/Linux / partition, chroot to it, replace the lilo.conf
+  with your back up version and rerun LILO.
+ \layout LyX-Code
+ 
+ # mkdir /foo
+ \layout LyX-Code
+ 
+ # mount /dev/hda6 /foo
+ \layout LyX-Code
+ 
+ # chroot /foo
+ \layout LyX-Code
+ 
+ # mv -v /backup/of/lilo.conf /etc/lilo.conf
+ \layout LyX-Code
+ 
+ # /sbin/lilo -v
+ \layout LyX-Code
+ 
+ # <press ctrl+D>
+ \layout LyX-Code
+ 
+ # reboot
+ \layout Standard
+ 
+ This will restore LILO to its original state.
+  Read this section once again, determine what went wrong, and try again.
  \layout Section
  
***************
*** 487,491 ****
  \layout Standard
  
! This sort of failure is normall do to a miss match between the speed at
   which your computer can run and the speed that is computed from a couple
   of the variables in the ini file.
--- 980,986 ----
  \layout Standard
  
! You're jumping way ahead here.
!  The full answers are a part of the setup that you will do in chapter ???.
!  This sort of failure is normall do to a miss match between the speed at
   which your computer can run and the speed that is computed from a couple
   of the variables in the ini file.
***************
*** 494,503 ****
   Try to run sim.run script and if that's ok, use that .ini file as base for
   your own ini-file.
!  Later on we'll put couple of working ini-files here.
!  For now, you can find them from 
! \begin_inset LatexCommand \htmlurl[http://www.linuxcnc.org/dropbox]{http://www.linuxcnc.org/dropbox}
! 
! \end_inset 
! 
! 
  \the_end
--- 989,992 ----
   Try to run sim.run script and if that's ok, use that .ini file as base for
   your own ini-file.
!  
  \the_end