[EMAIL PROTECTED] writes:
>
> Hello all.
>
> I've tried the standard disks, after login all I can do is change
> directory, ls says "ls: Out of memory" as does free. I compiled for x86
> only, slightly smaller Image (2k less) but the same result.
> (( I'm using the 0.0.73 kernel and the 0.14.6 dev ))
A 512K machine will not do a very good job of running the standard disk
set at the moment due to the excess amnmount of data memory (32K) used be
every running process. The standard root disk (and com
>
> Do I have to make the root disk from scratch, can I just fix init.?
>
> I tried the boot-root disk (nicest solution), but this gives the disk error
> referred to in the faq. Doing the hex-hack on this as detailed has no
> (discernable) effect. Am I missing something?
You are running out of memory because of the number of prcesses the
standard root disk runs, and the size of their data segments.
The standard root disk runs init, and then login of 3 virtual consoles.
After you login, you then have init, 2*login, and one sh running,
and the memory total looks like this:-
Low area for BIOS/system 64K
Kernel 128K
Buffers 64K
init 32+K
login * 2 32+K *2
sh ~64K
TOTAL 416K
It is fairly easy to see that at this stage there is very little free, and
it is almost certainly fragmented, so ls has dificulty running.
You may have more luck running l, which is a minimal l substitute.
You can get a more minimal root disk by re-compiling init so it only
launches login on 1 virtual console.
Change this line in init.c
#define NUM_TTYS 3
to
#define NUM_TTYS 1
run make, and copy the init binary to /bin/init on your root floppy,
and reboot ELKS.
>
> Specs on T1100= 512k ram, 8088 cpu, 1tty, 1pr, 720k floppy
>
> Is there a simple way to write the Image (68k) to a minix 720 disk, or the
> root for that matter. When I write then mount the root disk it shows as
> having 2k free, 360k being the disks new size.
>
If you want to create a root disk on a 720K disk with a true 720K
filesystem on it, use tar to get a tarball of the files on the old root
disk, use "mkfs.minix -n 14 720" to build a new minix v1 filesystem on the
disk in question, and then use tar to re-write the files. The root image is
an image of a 360K filesystem, and that filesystem cannot take more than
360K no matter what disk it is written to.
Al
