From: Alex Bochannek abochann@cisco.com
Subject: Standalone SPARC.
Date: Sat, 7 Oct 1995 05:01:43 -0400 [thread overview]
Message-ID: <19951007090143.K8MAShbLfVbCmCLCwZ9DnfM3UVnwyFnk2vXrsOR4t9I@z> (raw)
I've got a few questions about this.
1) I successfully unpacked the CD onto my drive. After I was done with
it, I tried to reboot but all I found on the drive (sd1) was the
old SunOS partition I had on it before and none of the new files. I
figure I need to do a (SunOS) format before actually doing this,
correct?
2) Let's say I get my sd1 drive to contain a kfs, how would I use it
in the boot process? The 9ss kernel doesn't really give me a choice
to boot locally. Or can I select il and point to my own address? Or
is there a third boot option like local!#w/w1disk?
3) Does anyone know if there's a way to actually boot the 9ss from the
internal disk? In the UniOsnabrueck paper (thanks for sending it,
Petra) it says you can just do a "boot 9ss". Does that mean if I
take a newly formatted disk under SunOS and do an installboot on
it, it would be happy? I kinda doubt it. Or is there a SPARC
version of home(8)?
4) I had a bunch of trouble with the u9fs stuff. Here some tips how I
finally got it working. I compiled only with the BSD, NEEDPROTO,
and LOG defines. I used gcc and the -ansi option. And I hardcoded
"/plan9" in the chroot in u9fs.c because for some reason inetd
refused to hand over the parameters I had in /etc/inetd.conf. That
was on a sun4m SPARC with 4.1.3_U1.
Thanks a bunch.
Alex.
> Net-boot 9ss on the
> IPX, login as 'none'. You should see a clock and a little window saying
> installation complete, welcome to plan 9, this is rc.
>
> Now set up the local disk and CD rom player, like so:
>
> bind -a '#'w3 /dev (I assume the disk is at SCSI 3, as usual)
> bind -a '#'R6 /dev (this gets the CD player)
>
> (Don't forget the '-a'... /dev gets really small if you do.)
>
> disk/prep /dev/sd3disk
>
> answer 'a' to the question to get the default partitions.
>
> disk/kfs -rb4096 -f/dev/sd3fs (kinda like newfs)
>
> mkdir /n/kfs; mount -c /srv/kfs /n/kfs
>
> Now you have a local filesystem on /n/kfs. Try
>
> disk/kfscmd sync
>
> as a sanity check.
>
> 9660srv (sets up CD player service)
>
> mkdir /n/cdrom; mount -c /srv/9660 /n/cdrom /dev/cd6
>
> Now you have the local disk and CD player ready to go.
>
> disk/kfscmd allow (Not sure if this is really needed, but turning off
> permissions sounded cool.)
>
> Now you want to unpack the CD onto the local disk:
>
> disk/mkfs -a -u /adm/users -s /n/cdrom /lib/proto/allproto |
> disk/mkext -u -v -d/n/kfs -z4096
>
> (This gets a "usage" grumble from mkext but it seems to work. Didn't
> work without the -d/n/kfs, though the manpage implies it should.)
>
> The -v will generate a
>
> x /n/kfs/some/file/name
>
> message as the files are extracted.
>
next reply other threads:[~1995-10-07 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-07 9:01 Alex [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-10-11 7:23 Al
1995-10-10 13:21 Steve
1995-10-10 10:23 Andrew
1995-10-07 17:34 Byron
1995-10-07 1:13 forsyth
1995-10-07 0:30 Jim
1995-10-04 0:08 forsyth
1995-10-03 23:12 Jim
1995-10-03 17:32 Byron
1995-10-03 14:14 Reg
1995-10-03 5:09 Alex
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=19951007090143.K8MAShbLfVbCmCLCwZ9DnfM3UVnwyFnk2vXrsOR4t9I@z \
--to=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).