On May 15, 2:52 am, st...@quintile.net (Steve Simon) wrote:
Anyone got a script to generate a bootable plan9.iso cdrom image,
the mkfiles in /sys/lib/dist seem quite labs-specific.
-Steve
I don't have anything automated, but you first generate a bootable
floppy or small HD image, then feed
2009/5/19 rsbohn rsb...@gmail.com:
On May 15, 2:52 am, st...@quintile.net (Steve Simon) wrote:
Anyone got a script to generate a bootable plan9.iso cdrom image,
the mkfiles in /sys/lib/dist seem quite labs-specific.
-Steve
maht has some details on this. The stuff in /sys/lib/dist is indeed
On Tue May 19 08:25:47 EDT 2009, kokam...@hera.eonet.ne.jp wrote:
What is the most important difference between the two?
Would you please post it to 9fans?
i sent a more complete answer off list (which i've lost).
the main difference is that with nupas you don't have to
load the entire mailbox
When booting the installcd on my ibm xserve 305 it says;
Bios call failed: bios loading disabled
no plan9.ini
then it gives me a boot from: prompt but it doesn't matter which ide
interface or device i try, it just brings me back to the prompt.
FreeBSD is installed on this particular machine right
Hi !
It seems that Plan9 boot loader doesn't support modern hardware from IBM :(
May be someone from IBM can help :)
P.S.: I have some IBM HS21 servers and I wish to use Plan9 on them.
2009/5/19 nocturnal sweh...@gmail.com
pci (or linux lspci -n) output would be helpful.
- erik
Sorry, I have HS21's, but I've never tried booting native on them.
Part of the problem will no doubt be that the CDROM is over a USB and
seems to be flakey even when installing certain Linux distros. My
solution (and the easiest path here) is to just use a virtualization
environment on the blades
Ignore the complaint about the BIOS; it's a red herring. Lots of
BIOSes have bugs that prevent 9load from booting through them, but
unless you're attempting to boot from bios0 or sdB0, 9load is not
using the BIOS to boot.
