The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: szigi@ik.bme.hu (SZIGETI Szabolcs)
Subject: [TUHS] v6on286
Date: Wed, 9 Jul 2003 09:00:25 +0200	[thread overview]
Message-ID: <003201c345e7$c5e2c180$26f34298@ik.bme.hu> (raw)
In-Reply-To: <D1A0AB08F3098B446877CCCA3BAEB14D@usagi.tsukino.pinku.zzn.com>


> Screen goes blank except for a block flashing cursor.  The keyboard
> does not respond - not even the lights - indicating that the machine
> is either in a PM loop or completely hung.
>
> Has anyone had better luck than me?
>
> Or have I had better luck than everyone else (author excluded)?


Hi,

Sorry, I don't have the soruces with me right now, so I can't be exact, but
I'll check next week.

You need to have a root disk (floppy or hdd), with /etc/init and stuff.

To
do this, first compile unix with the "built in shell". Check te Makefile for
the #define! Also set the root device in the kernel (floppy or hdd).

Make a floppy or hdd (be careful with the sector numbers, mkfs works with
absolute sectors, so it's easy to overwrite another partition) with the dos
based mkfs. Start the kernel with built in shell. It should create /dev/tty
automatically, and then you can populate the rest of the /dev directory.

There is a tool (sorry, I don't remenber the names, but check the source) to
transfer files, via an ather floppy, which is a horrible kludge, first you
write one file on it using one of the utilities, then start the kernel, and
using one of the built in commands you write it into the filesystem. This
has to be done one-by-one.

You can exit the kernel via shift-escape (?), but do a sync before.
Once you have the root floppy, recompile the kernel without the shell.

Now about the bug: I think I broke something in the inode code (I once
wanted to rewrite the code in ansi c, and then lost the original), so
currently, it won't mount the root fs. With plenty of printf's in the kernel
it's possible to debug :-).

Regards,

    Szabolcs



  parent reply	other threads:[~2003-07-09  7:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08  5:21 Steve Nickolas
2003-07-08 15:07 ` Maciek Bieszczad
2003-07-09  7:00 ` SZIGETI Szabolcs [this message]
2003-07-08 16:08 Steve Nickolas
     [not found] <20030709002523.GA7146@minnie.tuhs.org>
2003-07-09  2:34 ` Maciek Bieszczad
2003-07-09 16:25 Steve Nickolas
2003-08-08 22:14 JStevens
2003-08-11 18:38 JStevens

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='003201c345e7$c5e2c180$26f34298@ik.bme.hu' \
    --to=szigi@ik.bme.hu \
    /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 NNTP newsgroup(s).