From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 14 Mar 2003 08:22:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 14 Mar 2003 08:22:35 -0500 Received: from hera.cwi.nl ([192.16.191.8]:39825 "EHLO hera.cwi.nl") by vger.kernel.org with ESMTP id ; Fri, 14 Mar 2003 08:22:34 -0500 From: Andries.Brouwer@cwi.nl Date: Fri, 14 Mar 2003 14:33:21 +0100 (MET) Message-Id: To: Andries.Brouwer@cwi.nl, t_benk@web.de Subject: Re: [util-linux] cfdisk bug? Cc: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org From: Timo Benk [report on cfdisk failure where other *fdisk work, where things are fine with different size partitions, where things are fine when the bootable bit is set] Ha - I see what happens. You have CONFIG_ACORN_PARTITION_POWERTEC set. The Acorn code checks an 8-bit checksum over block 0, and believes that you have an Acorn partition when that checksum is OK. So, everybody has a chance of 1 in 256 of having her block 0 recognized as a POWERTEC partition. And indeed, minor changes will fix the situation. Assuming that you do not actually have an Acorn, you can switch off this configuration option. I'll cc this to linux-kernel, so that problem and solution are documented on a public list. And maybe someone who knows about Acorns can add a test to make it less likely that an Acorn is recognized by accident. Andries