Standard disclaimer
---------------------

* Most of muLinux commands are simple scripts. They are intented as 
  curiosity, as emergency tools and for educational purpose.
  Generally, they works fine -- but use carefully. My intention was'nt
  to recreate a LINUX system by scratch, but dust on a Linux kernel.

  CONTROL-C do interrupt; exit from VI editor with "ESCAPE : q" 

* Don't ask me for Linux related questions: I can't to surrogate the
  proper Linux newsgroups, neither FAQ, HOWTO and docs. 

* Buy a booklet on Linux/UNIX, like "Linux for dummies", 
 "Linux's Secrets" (Barkakati), etc.

* Read any doc! Read any doc! My disgousting english is'nt a good excuse.
  You are "root", the privileged user. The "root" user (the super-user)
  is really Superman: can destroy an HD in ONE second, with Linux.

* Leggi ogni doc! Leggi ogni doc! Il mio pessimo italiano non e' una
  buona scusa. Tu sei "root", l'utente privilegiato. L'utente "root"
  (detto anche super-user) e' veramente superman: puo' distruggere
  un hard-disk in UN secondo, con Linux.


To Avoid accidents
----------------

	+ don't extract startup floppy before shutdown finished
	+ don't extract startup floppy when mounted ( setup -s, first)
	+ unmount /startup floppy with "umount /startup"
	+ don't touch SCSI hard-disks
	+ don't try to mount NT partition with this kernel
	+ don't setup swap if you are not sure
	+ never use mkfs.ext2
	+ never that:  cp my_file /dev/hdb1 !!!! Any data loss.
	+ never that:  cat my_file > /dev/hdb1 !!!! Any data loss.
	+ rm -r is more powerful: it can erase mounted disks completely!
	+ in UMSDOS muLinux, don't remove the dir DOS: this is'nt
	  a copy, this is THE ORIGINAL one :)

If something goes wrong
------------------------


Explore your hardware:

        + "fdisk" show your hard-disk partitions. "fdisk -l | less"
        + "dmesg|less" show what LINUX know about your hardware
        + go in /proc and look inside the files:

                        # cat interrupts
                        # cat devices
Look in /var/log.


Start muLinux in "maintenance mode".
------------------------------------

1) UMSDOS installation:

                c:> loadlin mulinuz initrd=root.gz init=/etc/rc.1

2) Floppy muLinux

                At the "boot:" prompt, issue:

                boot: mulinux init=/etc/rc.1


Confortable Mini applications - work in progress
------------------------------------------------

	Try:

	menu, rna, pion, info, help, mon, ...


Browse your file system 
------------------------

	+ start "pion" file manager
		
			# pion

	+ Look in /bin and /usr/bin for command available
	+ Look in /setup/fun if you wish to learn about setup

Check mounted partitions:
--------------------------
	
	+ Use "df" to show mounted partitions
	+ Issue a "mount" command (sorry for this name ...)

And, finally,
Spindown an HD, if the noise leave you a little confused :)))
--------------------------------------------------------

		# hdparm -y /dev/hdb1


