<feed xmlns='http://www.w3.org/2005/Atom'>
<title>drakx, branch user/martinw/mga6</title>
<subtitle>Mageia Installer and base platform for many utilities</subtitle>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/drakx/'/>
<entry>
<title>Always tell the kernel about partition table changes when running the classic installer (mga#20074).</title>
<updated>2017-02-20T23:08:36+00:00</updated>
<author>
<name>Martin Whitaker</name>
<email>mageia@martin-whitaker.me.uk</email>
</author>
<published>2017-02-20T21:42:27+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/drakx/commit/?id=ca43ff9c8b9a53cb1d4d68173794556519bac257'/>
<id>ca43ff9c8b9a53cb1d4d68173794556519bac257</id>
<content type='text'>
The automatic rescan of the partition table is triggered by udevd. The
udev rule that causes this is not present on the cut-down system that
runs the classic installer.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The automatic rescan of the partition table is triggered by udevd. The
udev rule that causes this is not present on the cut-down system that
runs the classic installer.
</pre>
</div>
</content>
</entry>
<entry>
<title>Update NEWS</title>
<updated>2017-02-12T12:59:01+00:00</updated>
<author>
<name>Martin Whitaker</name>
<email>mageia@martin-whitaker.me.uk</email>
</author>
<published>2017-02-12T09:18:01+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/drakx/commit/?id=48cef68d42e5d1076b2f3bed4b59be150de48694'/>
<id>48cef68d42e5d1076b2f3bed4b59be150de48694</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Inhibit udisks2 when running drakdisk (mga#20247).</title>
<updated>2017-02-12T12:57:27+00:00</updated>
<author>
<name>Martin Whitaker</name>
<email>mageia@martin-whitaker.me.uk</email>
</author>
<published>2017-02-10T23:43:47+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/drakx/commit/?id=c5512813ad4795f5f3596a7963b84d821604f212'/>
<id>c5512813ad4795f5f3596a7963b84d821604f212</id>
<content type='text'>
This prevents disks/partitions being auto-mounted by e.g. Thunar
when drakdisk probes the disks or makes changes, which can lead
to disk corruption.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This prevents disks/partitions being auto-mounted by e.g. Thunar
when drakdisk probes the disks or makes changes, which can lead
to disk corruption.
</pre>
</div>
</content>
</entry>
<entry>
<title>explicitly probe LVMs in live install</title>
<updated>2017-02-12T11:54:53+00:00</updated>
<author>
<name>Thierry Vignaud</name>
<email>thierry.vignaud@gmail.com</email>
</author>
<published>2017-01-30T09:43:06+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/drakx/commit/?id=bd4c2c2f5c8b92e1cd0e72ba5471dd526c535279'/>
<id>bd4c2c2f5c8b92e1cd0e72ba5471dd526c535279</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Exclude x11-driver-video-vmware from unneeded packages (mga#19979).</title>
<updated>2017-02-12T11:54:53+00:00</updated>
<author>
<name>Martin Whitaker</name>
<email>mageia@martin-whitaker.me.uk</email>
</author>
<published>2016-12-19T14:01:22+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/drakx/commit/?id=b1e9ed8a077baf02f1a0be5959c4b39069bf7183'/>
<id>b1e9ed8a077baf02f1a0be5959c4b39069bf7183</id>
<content type='text'>
It's required by x11-driver-video, and removing that orphans all
the other required x11 video driver packages.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It's required by x11-driver-video, and removing that orphans all
the other required x11 video driver packages.
</pre>
</div>
</content>
</entry>
<entry>
<title>Allow a BIOS boot partition to be located on any disk (mga#20161).</title>
<updated>2017-02-12T11:54:53+00:00</updated>
<author>
<name>Martin Whitaker</name>
<email>mageia@martin-whitaker.me.uk</email>
</author>
<published>2017-02-05T00:03:41+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/drakx/commit/?id=e3662f1c4b563d148b8d6e7e650e93eff89b6df1'/>
<id>e3662f1c4b563d148b8d6e7e650e93eff89b6df1</id>
<content type='text'>
This relaxes the rules in fs::any::is_boot_bios_part_needed to allow
the BIOS boot partition to be located on any disk, not just the disk
containing the root partition. It also ensures that a BIOS boot
partition is never forcibly required in a system with non-GPT disks.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This relaxes the rules in fs::any::is_boot_bios_part_needed to allow
the BIOS boot partition to be located on any disk, not just the disk
containing the root partition. It also ensures that a BIOS boot
partition is never forcibly required in a system with non-GPT disks.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix auto-allocation of BIOS boot partitions (mga#20161, mga#19888).</title>
<updated>2017-02-12T11:54:53+00:00</updated>
<author>
<name>Martin Whitaker</name>
<email>mageia@martin-whitaker.me.uk</email>
</author>
<published>2017-02-04T23:46:14+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/drakx/commit/?id=02ba0f311a04e3fe93985bb75b6e7e99c6315b73'/>
<id>02ba0f311a04e3fe93985bb75b6e7e99c6315b73</id>
<content type='text'>
This adds a specific subroutine, fsedit::auto_allocate_boot_bios_parts
that detects if a BIOS boot partition is needed and allocates it if so.
This allows us to relax the rules in fs::any::is_boot_bios_part_needed
to allow the user to manually allocate the BIOS boot partition on a
different device if they so wish.

In the normal case that installation is confined to a single disk,
this will allocate a single BIOS boot partition on that disk. In
the rare case that installation is spread over multiple disks, it
will allocate a BIOS boot partition on every disk. Given that the
BIOS boot partitions are very small and that this is not a normal
use case (see mga#16055), this seems an acceptable quirk - and does
allow the user to then choose any disk when installing the boot
loader.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This adds a specific subroutine, fsedit::auto_allocate_boot_bios_parts
that detects if a BIOS boot partition is needed and allocates it if so.
This allows us to relax the rules in fs::any::is_boot_bios_part_needed
to allow the user to manually allocate the BIOS boot partition on a
different device if they so wish.

In the normal case that installation is confined to a single disk,
this will allocate a single BIOS boot partition on that disk. In
the rare case that installation is spread over multiple disks, it
will allocate a BIOS boot partition on every disk. Given that the
BIOS boot partitions are very small and that this is not a normal
use case (see mga#16055), this seems an acceptable quirk - and does
allow the user to then choose any disk when installing the boot
loader.
</pre>
</div>
</content>
</entry>
<entry>
<title>Rename partition_table::_default_type to partition_table::default_type.</title>
<updated>2017-02-12T11:54:53+00:00</updated>
<author>
<name>Martin Whitaker</name>
<email>mageia@martin-whitaker.me.uk</email>
</author>
<published>2017-02-04T23:42:51+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/drakx/commit/?id=aeccd33e13b5bd532fe08e5b3f1630935bbd9cfb'/>
<id>aeccd33e13b5bd532fe08e5b3f1630935bbd9cfb</id>
<content type='text'>
The following patches want to use it outside the partition_table module.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The following patches want to use it outside the partition_table module.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix erratic behaviour when telling kernel to delete partitions (mga#20074).</title>
<updated>2017-02-12T11:54:53+00:00</updated>
<author>
<name>Martin Whitaker</name>
<email>mageia@martin-whitaker.me.uk</email>
</author>
<published>2017-02-04T17:11:10+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/drakx/commit/?id=3a76f08fbdd7dc83dc260e6af4f482c600774576'/>
<id>3a76f08fbdd7dc83dc260e6af4f482c600774576</id>
<content type='text'>
When telling the kernel about changes to a DOS partition table, if a
partition was deleted on a disk that also contained an Empty partition,
the kernel also removed the Empty partition from its cached partition
table (and renumbered the other partitions).

Experimentation showed that leaving the udev exec queue active whilst we
were telling the kernel about the changes fixed this problem, although I
don't have an explanation for why it does.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When telling the kernel about changes to a DOS partition table, if a
partition was deleted on a disk that also contained an Empty partition,
the kernel also removed the Empty partition from its cached partition
table (and renumbered the other partitions).

Experimentation showed that leaving the udev exec queue active whilst we
were telling the kernel about the changes fixed this problem, although I
don't have an explanation for why it does.
</pre>
</div>
</content>
</entry>
<entry>
<title>Set fs_type to '' for BIOS boot and Empty partitions.</title>
<updated>2017-02-12T11:54:53+00:00</updated>
<author>
<name>Martin Whitaker</name>
<email>mageia@martin-whitaker.me.uk</email>
</author>
<published>2017-02-04T08:11:50+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/drakx/commit/?id=fbce536146d3257e12d8cea79c150b0175dfeae7'/>
<id>fbce536146d3257e12d8cea79c150b0175dfeae7</id>
<content type='text'>
This prevents misreporting of the partition type in diskdrake if they
located on top of an old partition that contained a valid file system.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This prevents misreporting of the partition type in diskdrake if they
located on top of an old partition that contained a valid file system.
</pre>
</div>
</content>
</entry>
</feed>
