From: Alan Carvalho de Assis <acassis@gmail.com>
To: Jody Bruchon <jody@jodybruchon.com>
Cc: linux-8086@vger.kernel.org
Subject: Re: ELKS disk images updated
Date: Sun, 19 Feb 2012 16:20:17 -0200 [thread overview]
Message-ID: <CAG4Y6eSFZ3ARAxLvpELnSs7LMXWhZJL9fkQ1sXJ9Vj7jyMxSUw@mail.gmail.com> (raw)
Hi Jody,
It worked fine on QEMU ($ qemu -fda full3 -no-fd-bootchk)
Nice to see ELKS bringing back to life.
Do you think it is possible to port busybox (and uClibc) to 8086?
I noticed which summing up just the binaries bigger than 8000 bytes it
is more than 300KB :
ash 50652
banner 8396
ed 13092
getty 8156
install 14336
ktcp 22148
login 8556
ls 14196
man 15736
passwd 11344
proto 12228
remsync 20096
sash 9792
sh 50652 (symbolic link to ash ?)
stty 16148
synctree 18420
tar 8864
telnet 11036
tget 9276
urlget 12376
vi 34980
xargs 8320
Using busybox we could get a complete system (with even more programs)
in less than 300KB.
Best Regards,
Alan
On 2/19/12, Jody Bruchon <jody@jodybruchon.com> wrote:
> I have taken the liberty of updating the ELKS disk images to include the
> shiny new 0.1.4 kernel. I have also noticed many very strange bugs
> leading to infinite loops or locking myself out of the system (at least
> in QEMU). These can be fixed down the road. I am also going to try to
> disassemble the MINIX boot files at some point, since the only boot
> loader source we have is the bootsect.S in the kernel tree, which is
> useless if you want to load from a filesystem and not just dump the
> kernel straight to the disk. Also, note that the floppy signature for
> larger disk images is not present, so for QEMU in particular, you must
> specify the -no-fd-bootchk option. Once I disassemble the boot code
> (don't have time to do it right now), I'll fix this problem as well.
>
> Anyway, have a look at the disk images:
> https://sourceforge.net/projects/elks/files/ELKS%20Disk%20Images/0.1.4/
>
> Jody Bruchon
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next reply other threads:[~2012-02-19 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-19 18:20 Alan Carvalho de Assis [this message]
[not found] <4F41458F.9030506@jodybruchon.com>
2012-02-19 18:57 ` ELKS disk images updated Jody Bruchon
2012-02-19 23:12 ` Alan Carvalho de Assis
-- strict thread matches above, loose matches on Subject: below --
2012-02-19 17:09 Jody Bruchon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAG4Y6eSFZ3ARAxLvpELnSs7LMXWhZJL9fkQ1sXJ9Vj7jyMxSUw@mail.gmail.com \
--to=acassis@gmail.com \
--cc=jody@jodybruchon.com \
--cc=linux-8086@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).