Re: slink installs on sparc1+, but
Harold Hartley wrote:
> I have a sparc I had just installed slink on very nicely....
> but the thing I am having problem with is it still wants to boot up SunOS...
> I thought linux wrote over that when I partitioned the drive...
> but it seems like the slink is on drive 2 and not on drive 1...
>
> I have tried what I can think of and I may have overlooked something...
> I want to use both drives for my linux, so I don't really need to keep the
> sunOS as it is setup for the old place the sparc1+ came from...
> can anyone tell me how to rid the sunOS to put linux to use both drives....
> drive 1 is a 1.02 gig and drive 2 is a 1.5 gig
It all depends on your disk's target ID's... you're going to have to
play with it a bit, but you'll pretty much want to STOP-A to the
OK prompt, and then muck with one of the boot options.
Just type "printenv" to see the options... I believe you're looking for
"boot-disk" or so (I can't STOP-A my SS10 at this instant). Anyways,
commonly it will be set to "disk net"... on old Sparcs you'll want to use
target ID's 0-3... the mapping goes like this:
ID Name
-- ----
0 disk3
1 disk1
2 disk2
3 disk disk0
So if you want to boot from the disk at target ID 0, for example, you
would "setenv boot-file disk3" at the OK prompt... hope this helps. :)
Reply to: