Attachment 31636 Details for Bug 24999 – git formatted patch

[patch] git formatted patch

0003-Bug-24999-Hide-Compaq-recovery-partition-type-0x12.patch (text/plain), 1.41 KB, created by Martin Pitt on 2009-12-01 13:16:41 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Martin Pitt

Created: 2009-12-01 13:16:41 UTC

Size: 1.41 KB

patch

obsolete

>From 0fa80778844499c5e9b9e2b928a3ef1a80720c95 Mon Sep 17 00:00:00 2001
>From: Martin Pitt <martin.pitt@ubuntu.com>
>Date: Mon, 9 Nov 2009 15:00:50 +0100
>Subject: [PATCH 3/4] =?UTF-8?q?Bug=2024999=20=E2=80=94=20Hide=20Compaq=20recovery=20partition=20type=200x12?=
>MIME-Version: 1.0
>Content-Type: text/plain; charset=UTF-8
>Content-Transfer-Encoding: 8bit
>
>http://www.win.tue.nl/~aeb/partitions/partition_types-1.html lists MBR type
>0x12 as "configuration/rescue", used by Compaq, IBM, Intel, and NCR.
>
>https://bugs.launchpad.net/bugs/451304
>---
> data/80-udisks.rules |    2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
>diff --git a/data/80-udisks.rules b/data/80-udisks.rules
>index d0e57d0..dac0109 100644
>--- a/data/80-udisks.rules
>+++ b/data/80-udisks.rules
>@@ -161,7 +161,7 @@ ENV{UDISKS_PARTITION_SCHEME}=="apm", ENV{UDISKS_PARTITION_TYPE}=="Apple_Bootstra
> # special MBR partition types (EFI, hidden, etc.)
> # see http://www.win.tue.nl/~aeb/partitions/partition_types-1.html
> ENV{UDISKS_PARTITION_SCHEME}=="mbr", \
>-  ENV{UDISKS_PARTITION_TYPE}=="0x00|0x11|0x14|0x16|0x17|0x1b|0x1c|0x1e|0x27|0x3d|0x84|0x8d|0x90|0x91|0x92|0x93|0x97|0x98|0x9a|0x9b|0xbb|0xc2|0xc3|0xdd|0xef", \
>+  ENV{UDISKS_PARTITION_TYPE}=="0x00|0x11|0x12|0x14|0x16|0x17|0x1b|0x1c|0x1e|0x27|0x3d|0x84|0x8d|0x90|0x91|0x92|0x93|0x97|0x98|0x9a|0x9b|0xbb|0xc2|0xc3|0xdd|0xef", \
>   ENV{UDISKS_PRESENTATION_HIDE}="1"
> 
> # special GUID-identified partition types
>-- 
>1.6.5
>

Actions: View | Splinter Review

Attachments on bug 24999: 31067 | 31636

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.