end_request: I/O error, dev 02:3c (floppy), sector 18 cat: write error: Input/output error Done. Reboot now.
Did you format the floppy disk with
fdformat /dev/fd0H1722?or with a bare "fdformat /dev/fd0" ? If yes, please change media.
Ops, this is the problem: the Installer scans only the first level directories. No problem: if you copied in
c:\a\b\c\d specify: /a/b/c/dwhen muLinux ask for path.
You can not copy the archives on to the floppy in such a way, but download everything in one directory in Windows and run the installation as specified in INSTALL.DOS, that is with the commands "makefd.bat" or "boot.bat"
Are you trying to *transport* this archive to the destination hard disk?
If yes, you can use the pkzip feature of multi-disk: compress all with pkzip (in the original machine) using the -& option. The obtained .zip file will be split on a set of 1.44 floppies.
Then, rebuild the archive at the destination, using pkunzip.
setup -s lock
Exact. This message, "16 ramdisk", is only related to the "rd" module - the ramdisk support in the kernel. Everything in muLinux uses RAM, because the filesystem is in RAM, and executable programs use RAM. The temporary disk (/tmp) uses its own ramdisk, with a default size 2048k. During the setup for /tmp the user has the possibility to change this value.
muLinux runs entirely in RAM, so it requires more RAM than usual. You need swap, but setting up a swap using the muLinux script is not possible in 4M, because the scripts fork. You have to reach a prompt and proceed manually:
# .... mount a DOS disk ... # dd if=/dev/zero bs=1k count=4000 of=linux.swp # mkswap linux.swp # sync # swapon linux.swp
Take a look to the /bin/login command in muLinux: this is a script wrapper. It starts:
1. ash, if EXT is *not* mounted (fake 'login') 2. /usr/local/bin/login, if EXT si mounted (the true 'login') 3. /usr/bin/ile, if USR is mounted (the command history),The command history in muLinux is full demanded? not sure what you mean "delegated" to an external program, "ile", used in this way:
# /usr/bin/ile -/etc/ilerc /bin/-ash -si (this is the *fake* case).If you wish to have the command history without USR, put "ile" in /bin, and change /bin/login accordingly.
miterm [-s speed] [-l line] [-e escape-char] For example:
# miterm -l /dev/ttyS1
After the establishing the connection with the modem, you can issue standard AT* commands. Try for example "ATZ". You can dial using:
atx3 atdtxyzwhere xyz is the telephone number.
If the system blocks at the message about "toilet paper", you only started the kernel, but the system itself won't run. Try decreasing the ramdisk_size - when the you see the message "boot:" booting from floppy, type the following carefully:
boot: mulinux f1722 load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=3000 ramdisk_start=597(on a single line) The default value is 4600 in muLinux. You will gain 1.5M, maybe it will works.
You can transport them to the target machine using pkzip: it can split a big archive on to a set of floppy disks (see instructions; multispan).
A very common question, caused by a lack of README reading. If you install under Linux, you have to read the file INSTALL.Linux and use the script "mu".
YOU PUT the ADDONS in the c:\Linux directory? Please, please! This directory is NOT for you, but reserved to UMSDOS filesystem. Put your addons in c:\mu or c:\mulinux or c:\other!
You could find the "lilo" command also in another place: it is in the same directory you decompressed the mulinux.tgz archive. Mount this disk and copy it in /usr/bin, before of cloning.
Basically, the answer is : no. Any ELF package requires an own pool of libraries. muLinux is a libc5, then precompiled libc6 package do not works.
I added part of exential libc6 (from Debian 2.0) in the disk called PERL, but if you put in muLinux some binary from recent Mandrake, they do not works, because my libc6 is old.
I don't like battles that can't be wont [in that I'm like americans :-)]: a little system such muLinux is, can't follow libc state-of-arts, so as precise design muLinux will remains libc5 for a lot.
Recent libc are mega-and-mega! I thing newer Linuxes simply can't run from a floppy disk.
answer from "winsor SMP" email@example.com. Most libc5 application can be installed within muLinux. If you wander through the likes of metalab, you'll see many apps are offered in two flavors, libc5 and glibc (libc6). Using libc5 versions will get you going on the right foot, and if you get errors about lib files you should be able to grab the lib files from metalab as well.
Just be sure that after installing any lib files to either run "ldconfig" or reboot your machine(this is a VERY common mistake made) Another more ponderous option would be to compile apps from the source code using the -static flag in the makefiles........but be warned, this makes GIANT apps(quite similiar to the M$ stuff 8^P) oh yeah..........and be sure to compile those apps on "another" linux box as the+gcc included with muLinux is for learning C only. )
answer from Zeimet Alex firstname.lastname@example.org
I also once had a problem to install mulinux on a 386SX with 4MB. I think it will not be possible to install mulinux with 4MB on a SX, 8MB are required. But installed on a HD it works with 4MB! The trick I found: install mulinux in a UMSDOS directory on a machine with at least 8MB, then copy the whole "linux" directory over network on the 386. (with windows 3.11 for workgroups) Since had I made that, I use my 386SX as a Gateway internet router
Note: It's not possible to boot with a floppy an a 386SX with less than 8MB....or is there anybody who was able to boot with 4MB?
Recent muLinux can load addons also from a file. For example, if the user has cloned using the UMSDOS flavor, and the archive X11.tgz is the directory c:\mulinux (for example), it can be loaded with:
setup -f X11 from=/DOS/mulinux/X11.tgzAs alternative, if you run a muLinux release that nothing know about the new addon, you can try using the script loal.
If you wish to upgrade to a new major release, the best thing is to install from scratch, removing also c:\linux, if you use UMSDOS. I know, this is a crude solution, but muLinux is full-configured, so you lose relatively nothing.
If you only wish to upgrade some addon, you have two solution:
1) setup -f XYZ from=/path/to/XYZ (XYZ is the name of the addon) 2) use the "upgrade" script. It attempt to upgrade selectively only the files that are changed or new.
I have a question/request to you: at home I have two computers, (so, frankly speaking: 2 boxes and 1 monitor, so the second one is without monitor, only the box.) often need to reach the second computer's hard disk, and I don't want to take it out always and take it into the other computer. What I need is to configure this one floppy linux to do everything automatically.
You have to configure muLinux on a PC with monitor. A this point, you save the profile with "setup -s lock". At next run, muLinux do not ask anythink. You must config mulinux with the (minimal) parameters pertinent to destination PC.
Now, put the floppy in the destination PC without monitor and reboot. After that, enter in it with telnet and refine the setup.
These are the steps fo You:
1. point the url http://sunsite.,auc.dk/mulinux 2. enter in the DOWNLOAD-AREA and follow the link "THIS SITE" 3. Now enter in the "current" directory 4. download the X11.tgz, taking care to use shift-left with the mouse