From: brad@heeltoe.com (Brad Parker)
Subject: [Unix-jun72] init
Date: Sun, 04 May 2008 08:54:34 -0400 [thread overview]
Message-ID: <15542.1209905674@mini> (raw)
In-Reply-To: <Pine.BSI.4.64.0805031915580.20114@malasada.lava.net>
Tim Newsham wrote:
>I looked through init briefly and the version from s2.tar.gz is
>slightly different than the one in the pdf printout. In the printout
>/dev/rk0 is mounted on /usr at boot time. In the s2 version the
>string "/usr" is still present, but the call to mount is gone
>and so is the "/dev/rk0" string.
yes, I noticed that. I looked for strings in the binary init and
didn't see /dev/rk0.
>The init source is fairly short and shouldn't be too hard to type
>in or get from ocr. Has anyone yet worked through the details of
>using the V7 compiler to make 0405 binaries? Also has anyone
>successfully used a populated /usr on rk0 yet?
I think you can hack the header with dd.
I have gotten /usr to mount but something it not right. check says it
has files but the mount does something odd and nothing appears under the
mount point.
-brad
prev parent reply other threads:[~2008-05-04 12:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 5:19 Tim Newsham
2008-05-04 5:31 ` Tim Newsham
2008-05-04 6:29 ` [TUHS] comparing s1 frags, s2 bits, 1ed and jun72 print out Tim Newsham
2008-05-04 20:18 ` [Unix-jun72] 0407 binaries on 1ed Tim Newsham
2008-05-04 22:33 ` Warren Toomey
2008-05-05 0:00 ` Tim Newsham
2008-05-05 1:17 ` [Unix-jun72] Another RK mount program Warren Toomey
2008-05-05 1:23 ` [Unix-jun72] No luck with C compiler yet, but an idea Warren Toomey
2008-05-05 1:56 ` Tim Newsham
2008-05-05 23:01 ` [Unix-jun72] uppercase input Warren Toomey
2008-05-04 6:50 ` [Unix-jun72] init Warren Toomey
2008-05-04 8:41 ` [Unix-jun72] Yes, a mount command Warren Toomey
2008-05-04 12:54 ` Brad Parker [this message]
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=15542.1209905674@mini \
--to=brad@heeltoe.com \
/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).