Date: Sun, 24 Nov 1996 11:59:10 -0800 (PST) From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com> To: darrylo@sr.hp.com Cc: jkh@time.cdrom.com, current@freefall.freebsd.org Subject: Re: 2.2-ALPHA install failure Message-ID: <199611241959.LAA00651@GndRsh.aac.dev.com> In-Reply-To: <199611241853.AA130971631@hpnmhjw.sr.hp.com> from Darryl Okahata at "Nov 24, 96 10:53:50 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Humm... let me see... if I get this right (I don't use sysinstall, but
> > > I have seen this X/1/1 translation thing it does) sysinstall defaults to
> > > a X/1/1 translation, and even goes so far as to write that into the
> > > MBR on a ``dangerously dedicated'' install.
> >
> > This was what phk recommended as proper "hint" values for libdisk in
> > the dangerously-dedicated case. What would you suggest instead?
>
> How about the values of "historical_bogus_partition_table", as
> given in sys/i386/isa/diskslice_machdep.c?
>
> The data for partition 3 is:
> sysid 165,(FreeBSD/NetBSD/386BSD)
> start 0, size 50000 (24 Meg), flag 80
> beg: cyl 0/ sector 1/ head 0;
> end: cyl 1023/ sector 63/ head 255
^^ bogus (ie this means 62 sectors!!)
>
I would like to also see that corrected/changed to:
The data for partition 3 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 0, size 2097152 (1024 Meg), flag 80
beg: cyl 0/ sector 1/ head 0;
end: cyl 1023/ sector 32/ head 63
Or atleast make size == cyl * sec * head (ie 1024*64*255 == 16711680)
my reasoning is that any third party fdisk program that sees the current
bogus table likes to try and ``fix it'' and usually ends up doing quite
the wrong thing : -(.
--
Rod Grimes rgrimes@gndrsh.aac.dev.com
Accurate Automation, Inc. Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611241959.LAA00651>