Chris Zakelj wrote:
Shawn K. Quinn wrote:
On Sun, 2005-07-10 at 00:16 -0400, Nick Holland wrote:
BTW: your 10G drive probably has a jumper to bring it below 8G or 2G,
which is more than enough for a firewall, and will speed the boot.
You will lose the rest of your disk, however.
What's the advantage to this over simply configuring the BIOS to
recognize the disk up to its limit? All the BIOS ever needs to see is
the first 504M/2G/8G of the disk which is where the root filesystem is,
right? And from what I have read, a root filesystem should almost never
be larger than 504M anyway, right?
Because some BIOSes are seriously damaged. I had an old P-90 that
refused to even POST with anything larger than a 2G drive. Lying to
get the system to POST, then putting your kernel within the BIOS' boot
window will get you far enough to let the kernel take over, letting
you use the full drive capacity (usually).
Hi,
Sorry to follow up on such an old post, but it really caught my
attention now that I am facing the same problem. I have inherited a
cpu0: Intel Pentium II ("GenuineIntel" 686-class, 512KB L2 cache) 349 MHz
with an old
wd0: 16-sector PIO, LBA, 4028MB, 8249472 sectors
I want to put a new HD in and install OpenBSD. It's an old "True Blue"
IBP PC350 & there are no bios updates available for a drive > 14 gig.
If I do as suggested, configure the BIOS so it sees the new (80G) drive
as a 14 Gig, and just pretend that everything is OK, it will work?
I usually make my / partition only 256M, so keeping it low should not be
a problem. What about drive geometry? Is there going to be conflicts?
I ask, because once I buy the drive & open it, I can't return it, and
that would be an expensive experiment!
Thanks,
Steve
