View previous topic :: View next topic |
Author |
Message |
garylin n00b
Joined: 12 May 2004 Posts: 1
|
Posted: Wed May 12, 2004 9:11 am Post subject: help!!!! |
|
|
i want to intall gentoo in my SUN ULtra2
but the SILO is 1.4.4
i am a newer ......so can you tell me how to downgrade to the silo 1.3???
how to use the code "emerge =sys-boot/silo-1.3.1-r1 "??? |
|
Back to top |
|
|
Luud Apprentice
Joined: 05 Jun 2003 Posts: 246 Location: Netherlands
|
Posted: Wed May 12, 2004 12:12 pm Post subject: |
|
|
Doesn't this work for you? Code: |
# emerge /usr/portage/sys-boot/silo-1.3.1-r1.ebuild
|
See Portage Manual, section "Merging Packages".
Good luck! _________________ "Great minds don't think alike. If they did, the patent office would only have about fifty inventions." - Wally |
|
Back to top |
|
|
Ferris Retired Dev
Joined: 13 Jan 2003 Posts: 426 Location: N. Virginia (USA)
|
Posted: Wed May 12, 2004 12:13 pm Post subject: |
|
|
Are you sure you need to downgrade? silo-1.4.4 should work for you on U2.
But if you really need to downgrade, something like the following should work, assuming
your silo.conf is in /boot:
Code: |
emerge =sys-boot/silo-1.3.1-r1
silo -C /boot/silo.conf -f
|
You would do this as two commands while logged in as root after (or well into) your install,
because you need /boot to be on the disk you are going to boot from.
Best is to do the install without doing this. As long as you can boot from the CD (or whereever you are
booting from), you don't have to worry about it unless you need it, and on U2, you shouldn't.
If you want to know how silo works, look at http://www.sparc-boot.org and the flow
diagram at http://www.sparc-boot.org/how.html
I hope this is of some use.
Regards, |
|
Back to top |
|
|
ciaranm Retired Dev
Joined: 19 Jul 2003 Posts: 1719 Location: In Hiding
|
Posted: Wed May 12, 2004 7:37 pm Post subject: |
|
|
Luud wrote: | Doesn't this work for you? Code: |
# emerge /usr/portage/sys-boot/silo-1.3.1-r1.ebuild
|
|
Don't do that. It causes all sorts of horrid breakages. Instead, either:
Code: | emerge \<sys-boot/silo-1.4 |
or add Code: | >=sys-boot/silo-1.4 | to /etc/portage/package.mask |
|
Back to top |
|
|
Luud Apprentice
Joined: 05 Jun 2003 Posts: 246 Location: Netherlands
|
Posted: Thu May 13, 2004 7:50 am Post subject: |
|
|
Hi ciaranm,
Are these "horrid breakages" specific to sparc (or even silo) or is the example given in the documentation not good? (If so, I think it should be changed.)
Cheers _________________ "Great minds don't think alike. If they did, the patent office would only have about fifty inventions." - Wally |
|
Back to top |
|
|
ciaranm Retired Dev
Joined: 19 Jul 2003 Posts: 1719 Location: In Hiding
|
Posted: Thu May 13, 2004 12:09 pm Post subject: |
|
|
Well... emerge /path/to/ebuild has its uses. However, it shouldn't be used for day to day things or for getting a specific version. The issue being, emerge /path/to/ebuild doesn't update world or virtuals, so in effect portage doesn't think the package in question has been installed. |
|
Back to top |
|
|
Sugarat Guru
Joined: 24 Jul 2002 Posts: 348
|
Posted: Thu May 13, 2004 2:43 pm Post subject: |
|
|
How come U2's dont work with newer SILO's ? _________________ --[ UltraSPARC ]--
Accept no imitations |
|
Back to top |
|
|
ciaranm Retired Dev
Joined: 19 Jul 2003 Posts: 1719 Location: In Hiding
|
Posted: Thu May 13, 2004 2:57 pm Post subject: |
|
|
They do. Or rather, most of them do. If anyone knew why a few of them b0rked we'd be able to fix it. |
|
Back to top |
|
|
|