On Fri, Jun 08, 2007 at 10:41:40PM -0400, Kenneth R Westerback wrote:
> This is very odd on several fronts. First, someone has obviously
> been writing on the MBR for no good reason. I just tested an fdisk
> compiled to day and noticed no oddities on my i386.
>
> Second, the fact that you find a d
On 6/8/07, Theo de Raadt <[EMAIL PROTECTED]> wrote:
> c: 7168196763 unused 0 0 # Cyl 0*- 4461
> d: 210445263 4.2BSD 2048 16384 132 # Cyl 0*- 130
Ah -- your 'c' partition does not start at 0.
It's an old FreeBSD partition on yo
> c: 7168196763 unused 0 0 # Cyl 0*-
> 4461
> d: 210445263 4.2BSD 2048 16384 132 # Cyl 0*-
> 130
Ah -- your 'c' partition does not start at 0.
It's an old FreeBSD partition on your disk. That should not work; it
is bunk. W
This is very odd on several fronts. First, someone has obviously
been writing on the MBR for no good reason. I just tested an fdisk
compiled to day and noticed no oddities on my i386.
Second, the fact that you find a disklabel. Since we no longer store
or look for disklabels in FreeBSD partitions
On Thu, Jun 07, 2007 at 04:58:18PM -0500, Emilio Perea wrote:
> On Thu, Jun 07, 2007 at 07:50:24PM +0200, Otto Moerbeek wrote:
> > I have thinking a bit more about the problem, and it is very likely the
> > following scenario happened:
> >
> > 1. Kernel upgrade by source.
> >
> > 2. Reboot
> >
>
5 matches
Mail list logo
