linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Z <rz@linux-m68k.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Phillip Susi <psusi@ubuntu.com>,
	Debian m68k <debian-68k@lists.debian.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>,
	Parted development <parted-devel@lists.alioth.debian.org>
Subject: Re: [parted-devel] Atari label false positives
Date: Fri, 11 May 2018 20:30:55 +0200	[thread overview]
Message-ID: <20180511183054.GB4225@rz.localhost.localdomain> (raw)
In-Reply-To: <461cde4a-4cc2-8dce-538d-2c2af21e5ba3@physik.fu-berlin.de>

[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]

On Fri, May 11, 2018 at 06:10:37PM +0200, John Paul Adrian Glaubitz wrote:

> According to the documentation, p.43 [1], I think offset $01 should always
> contain either "GEM", "BGM" or "XGM". They don't seem to be optional.

The Atari partitioning tables are also used on the Q40/Q60 which breaks
many some assumptions.. no GEM here but instead one of two Q40 specific
types such as "QWA" or "QBD" in the first slot.
BTW I have never seen a low-case or camel-case string in this place,
this should be also used.

> I guess adding those to atari_probe() should help improve the detection
> quite a bit. But I would have to test that first.

It would, however I am not sure what happens if a hard disk is 
repurposed from Atari to PC or the other way around partitioning.
There may be some strings or other data left which could be 
misinterpreted.

> >I think I will at least move atari to be probed after all other labels
> >have failed.

in principle both should be probed, prompting user action if both
find something. They could also return a "score" - based on number of 
partitions recognised, their sizes and other info to give a hint which 
one is likely a non-random hit.


Richard

-- 
Name and OpenPGP keys available from pgp key servers


[-- Attachment #2: Type: application/pgp-signature, Size: 811 bytes --]

  reply	other threads:[~2018-05-11 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2d6f5455-963d-b044-a64d-67634df46071@ubuntu.com>
     [not found] ` <2d6f5455-963d-b044-a64d-67634df46071-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
2018-05-11 15:29   ` Atari label false positives John Paul Adrian Glaubitz
     [not found]     ` <35ad9889-bc13-56bd-7831-f7bb3eea2d1e-1Olz3AKvcsuAKZTfuerNgRvVK+yQ3ZXh@public.gmane.org>
2018-05-11 15:56       ` Phillip Susi
     [not found]         ` <874bf955-d5bc-5d9c-0f87-445da67f3bdd-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
2018-05-11 16:10           ` John Paul Adrian Glaubitz
2018-05-11 18:30             ` Richard Z [this message]
2018-05-11 23:17         ` [parted-devel] " Michael Schmitz
     [not found]           ` <80a28dd6-ce19-e6ed-fc7a-c5561fecf989-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-05-12  7:59             ` John Paul Adrian Glaubitz
2018-05-12  8:41               ` [parted-devel] " Michael Schmitz
     [not found]                 ` <c1bf0748-f7e0-b109-8c9e-26f8a2c70bf3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-05-12 11:24                   ` John Paul Adrian Glaubitz
2018-05-12 19:22                     ` [parted-devel] " Michael Schmitz
2018-05-14 13:02                   ` Phillip Susi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180511183054.GB4225@rz.localhost.localdomain \
    --to=rz@linux-m68k.org \
    --cc=debian-68k@lists.debian.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-m68k@vger.kernel.org \
    --cc=parted-devel@lists.alioth.debian.org \
    --cc=psusi@ubuntu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).