|Summary:||diskdruid and the silo 1024 barrier.|
|Product:||[Retired] Red Hat Linux||Reporter:||Jeremiah Johnson <jjohnson>|
|Component:||installer||Assignee:||Jay Turner <jturner>|
|Status:||CLOSED NOTABUG||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2000-02-09 00:04:47 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Jeremiah Johnson 1999-09-29 09:05:18 UTC
A problem that I thought was solved has turned up again, but this time on the sparc platform. The problem being that the linux kernel must be (as quoted from the doc) " below a magic boundary 1GB from the start of the disk. " What I normally do to fix this is create a partition, say sda1 and make that /boot. This works quite well on x86 systems. However, DiskDruid will *NOT* let you put /boot on a partition other than / with RH6.0sparc. The only other way around this is to make a small / and make sure its sda1. I feel the /boot way is better.
Comment 1 Jay Turner 2000-02-08 13:46:59 UTC
Sparc does not have this limit, so this is not something that you need to worry about on a 4M or 4C sparc. You are allowed to create a /boot partition on a 4U machine however.
Comment 2 Jeremiah Johnson 2000-02-08 19:33:59 UTC
According to the silo documentation sparc does has this (1024)limitation. I have encountered the problem on a sparcstation 20. DiskDruid doesn't let me make the partition anyways, if i try to create a partition named " /boot " it says that /boot *must* be on the / partition. Even if sparc doesnt have the barrier I should beable to make a /boot partition. As my cpu just died in my ss20 I have not been able to test to see if 6.1 is affected here.
Comment 3 Jay Turner 2000-02-09 00:04:59 UTC
Due to limitations on the sparc, you will not be able to create a separate /boot partition on a 4M sparc (same for a 4C) So, the only machine that you will be able to create a separate /boot partition on is a 4U machine.