PC 386sx
	4Mb de RAM
	Disquetera de 1.44Mb
	Monitor Hercules o Monócromo

	PC 486DX 120 Mhz o superior
	16Mb de RAM
	Disquetera de 1.44Mb
	Monitor VGA/SVGA
	Ratón
	Modem

	Descomprimir DOSTOOLS.zip en un directorio temporal Nota:Si estás usando Windos puedes utilizar Winzip o pkunzip o cualquier otra utilidad para descomprimir los ficheros en un directorio temporal
	Copiar mulinux*.tgz a ese mismo directorio temporal
	Para poder instalar muLinux, tienes que estar en un entorno DOS puro. Por tanto si estas usando W95/98 o NT debes rearrancar el sistema. Justo antes de que aparezca el logo de Windows tienes que pulsar F8 y seleccionar "Sólo símbolo del sistema".
	Una vez hecho esto, cambia al directorio temporal donde tengas los ficheros de linux
	Ejecuta el fichero Install.bat
	Sigue las instrucciones y vete introduciendo los disquetes según te los vayan pidiendo
	El sistema rearrancará
	Inserta el primer disquete de muLinux. Si no lo haces W95/98 arrancarán
	Cuando te lo pidan inserta el disquete de XWindows

From: "J.R. Pena" <[email protected]>
To: [email protected]  

Dear Michele,
     Hi!  You might want to look over this e-mail that I'm sending you.  
I think you might find it useful.  Thanks again!  

					-J.R.  

On Tue, 26 Jan 1999, Pete Nelson wrote:
> Forgive me, I'm stuck on a DOS box.  

>  6.  Now run the Install.Bat file.
> 
>  7.  Simply follow the directions, and insert two disks when prompted.
> 
>  8.  The system will now reboot.
> <<
> Which is OK, but how do you make the floppies to begin with?  There is
> nothing in the install.bat to write to the floppies (if it was unix, and
> the tar path was /mnt/floppy . . .)
  

  Dear Pete,
       Hi!  Thanks for bringing this to my attention.  Ok.  Let me explain.
  You're right that the Install.Bat file doesn't contain any lines to
  write to the floppies.  Instead of doing so, the Install.Bat file actually
  runs an instance of Linux.  In Linux, you'll be asked to enter the 
  path for the mulinux image files.  Afterwards, Linux will ask
  you if you'd like to create a swap file (for use with virtual memory.)  

  When you're entering the path for the location of the swap files, keep
  in mind that /dev/hda1 refers to your C:\ drive.  (If you're use
  a hard disk that has multiple partitions, keep in mind that /dev/hda2
  refers to the extended partition.  Therefore, the next partition referrs
  to /dev/hda3.  I'm going to create a small chart to explain what I mean.  

   Let's say you're using a 1.2 GB HD.  The HD has been partitioned into
   4 different partitions.  

   Linux Name  		 DOS/Windows 3.x/Windows 95 & 98/NT name
     /dev/hda1			  	C:\
     /dev/hda3				D:\
     /dev/hda4				E:\
     /dev/hda5				F:\  

  It's not necessary to create a swap file (use virtual memory), unless 
  you're using a PC that has less than 8 MB of RAM.  Yet, it wouldn't hurt
  if you would create a swap file, either.  In fact, the author of 
  muLinux recommends that you use a swap file if you plan to run X-Windows.
  So, when you're prompted to create a swap file be sure to express your
  desired amount of memory in kilobytes (K).  For instance, 1 MB = 1024K,
  4 MB = 4096 K,  8 MB = 8192K.  

  Finally, the part that you asked about. (Hehe, sorry about the needed
  explaination for entering the path and creating a swap file.)  You're
  now going to be asked to enter some 3.5" high-density disks.  The
  first disk will used to create an image disk for the boot/usr/root disk,
  while the second disk will contain a copy of X-Windows.  (Keep in mind
  that creating a disk for the X-Windows environment is optional.)
   

  Don't worry about actually formatting the disks.  Linux will take care
  of that itself.  In fact, Linux will format the disks to a 1.72 MB 
  capacity, and will even verify them.  If the disks contain any badj
  sectors at all, Linux will prompt you to enter a new batch of disks.
  Believe me, this is a rather simply process.  But it does get frustrating
  when you have a bunch of disks that have bad sectors on them.
    

  When the two image disks have been made, Linux will shut it self down and
  will reboot.  Now enter the first disk that you made, the boot/root/usr
  disk.  If you made a copy of X-Windows, be sure to insert the disk when
  prompted.  About this time, you'll be asked to create a configuration
  for muLinux.  Simply follow the instructions, and enter the appropriate
  paramters. 
  

  That's about it!  I hope this helps you.  If it doesn't let me know.  
  There's also a way to put muLinux on your hard drive.  (This is called
  cloning.) If you're interesting in doing this, just ask me.  I'd
  be happy to explain.   
  

> I'm excited about the concept of microlinux, but just wish I could get
> it working!
> --  

  Yes, I know you mean.  It took me a long time to figure out how to get
  muLinux myself.  But it was certainly worth it!!  I think muLinux is
  better than a full distribution of Linux, like RedHat and Slackware.
  For one, muLinux is portable.  Since muLinux fits on two disks, it 
  can be distributed much more easily than using CDs.  muLinux can also
  be used to show the power of using Linux at a demonstration at 
  school or at work.  I hope you enjoy using muLinux as much as I.  If 
  you any more questions, just let me know.  

  Sincerely yours,
  J.R. Pena  

  P.S.  Please note that Linux is not Unix.  While Linux is based
        on Unix, Linux has pretty much evolved on itself.  In fact, Linux
        doesn't use any AT&T or BSD code, at all!  So, to answer your  
        question, in Linux the device name for a floppy drive isn't  
        /dev/floppy.  It actually depends on the number of disk drives 
        that you have.  If you have a 3.5" 1.44 MB drive as your first disk 
        drive, which is referred to as A:\ in the DOS/Windows world, it 
        would be referred to as /dev/fd0 in Linux.  A 5.25" 1.2 MB drive is 
        referred to as /dev/fd1.   

        This particular naming system applies to everything as well, like 
        modems.  An internal modem on COM 1 inthe DOS world, is called ttys0 
        in Linux.  Com2 would be referred to as ttys2 in the Linux world.
        One more thing, an internal IDE CD-ROM drive is considered to be
        /dev/hdd under muLinux. 
     

        Again, I hope this helps!  If not, let me know.   -J.R.