9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] fossil option -m
Date: Sat, 18 Aug 2012 19:17:35 +0100	[thread overview]
Message-ID: <e50bf22e893a18cd120fb8df75c38ec7@hamnavoe.com> (raw)
In-Reply-To: <f35ce7b2235098a4ed7a745bc7993469@rei2.9hal>

> yes, bootrc basicly does the same stuff as the c based /boot/boot
> did before. we found that the other 30 odd programs can come in handy.
> especially when you try to boot a kernel on a odd machines where
> theres no working disks (yet :-)).

Yes, I've found the same approach useful while developing an sd/mmc
card driver for the raspberry pi.  I started with this inital boot.rc:

#!/boot/rc -m /boot/rcmain

/boot/echo boot...
/boot/bind -c /boot /bin
bind '#p' /proc
bind '#d' /fd
bind -a '#P' /dev
bind -a '#t' /dev
bind -a '#S' /dev
echo -n rpi >/dev/hostowner
echo fdisk...
fdisk -p /dev/sdM0/data >/dev/sdM0/ctl
cat /dev/sdM0/ctl
dossrv -f/dev/sdM0/dos
mount -c /srv/dos /mnt
exec /boot/rc -m/boot/rcmain -i

And for sd driver testing there's no need for a paqfs - a handful
of useful programs can just be stuck into /boot directly:

bootdir
	boot.rc			boot
	/arm/bin/rc
	/rc/lib/rcmain
	/arm/bin/mount
	/arm/bin/unmount
	/arm/bin/bind
	/arm/bin/echo
	/arm/bin/cat
	/arm/bin/cmp
	/arm/bin/ls
	/arm/bin/ps
	/arm/bin/dd
	/arm/bin/xd
	/arm/bin/rm
	/arm/bin/mkdir
	/arm/bin/disk/fdisk
	/arm/bin/dossrv

But all this is now obsolete [see next message].




  reply	other threads:[~2012-08-18 18:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18  5:03 arisawa
2012-08-18  5:30 ` erik quanstrom
2012-08-18  5:40   ` John Floren
2012-08-18 10:04     ` arisawa
2012-08-18 11:14       ` Richard Miller
2012-08-18 14:57       ` erik quanstrom
2012-08-18 16:23         ` cinap_lenrek
2012-08-18 17:11           ` erik quanstrom
2012-08-18 18:05             ` cinap_lenrek
2012-08-18 18:17               ` Richard Miller [this message]
2012-08-18 11:12   ` Richard Miller
2012-08-18 11:36     ` David du Colombier
2012-08-18 13:02       ` Richard Miller
2012-08-18 14:53         ` erik quanstrom
2012-08-19  9:04           ` David du Colombier
2012-08-19 15:04             ` erik quanstrom
2012-08-19 16:06               ` Bakul Shah
2012-08-19 16:08                 ` cinap_lenrek
2012-08-19 16:15                   ` Richard Miller
2012-08-19 16:17                 ` erik quanstrom
     [not found]   ` <CAL4LZyimqPZVQGmTDXzKBJsJNUaLsCEQBZz4qY8YSCb7pMkypA@mail.gmail.c>
2012-08-18 15:00     ` erik quanstrom
2012-08-18 15:18       ` erik quanstrom

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=e50bf22e893a18cd120fb8df75c38ec7@hamnavoe.com \
    --to=9fans@hamnavoe.com \
    --cc=9fans@9fans.net \
    /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).