Bug 29138 - Eigene Partitionierung
Eigene Partitionierung
Status: CLOSED FIXED
Product: Z_Univention Corporate Client (UCC)
Classification: Unclassified
Component: Image management
unspecified
Other Linux
: P5 normal
: UCC 1.0
Assigned To: Stefan Gohmann
Erik Damrose
: interim-3
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-09 15:45 CET by Stefan Gohmann
Modified: 2013-03-26 09:14 CET (History)
3 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2012-11-09 15:45:21 CET
Es sollte möglich sein, dass eine eigene Partitionierung verwendet wird, damit beispielsweise ein verschlüsseltes LVM verwendet werden kann.
Comment 1 Ingo Steuwer univentionstaff 2012-12-10 20:41:42 CET
Ich wurde heute auf Verschlüsselung im UCC-Rollout (auf Notebooks) angesprochen.
Comment 2 Stefan Gohmann univentionstaff 2012-12-20 09:24:35 CET
Es wird jetzt versucht das Skript /sbin/custom_partition auszuführen, wenn es verfügbar ist. Wenn das Skript nicht verfügbar ist, dann wird die lokale Partitionierung verwendet.

Es sollte ein Beispielpaket erstellt werden, welches ein verschlüsseltes LVM erstellt.
Comment 3 Stefan Gohmann univentionstaff 2013-01-07 07:08:36 CET
Aus Bug #28037

(In reply to comment #9)
> QUESTIONS:
> 
> Sollten wird vielleicht im toolkit Paket ein Beispiel für sbin/custom_partition
> mitbringen?
> 
> Ich habe das mit folgendem getestet:
> 
> partition_device="$1"
> parted -s "${partition_device}" mklabel GPT
> disk_size=$(/sbin/parted -s "${partition_device}" unit MB print | sed -ne
> "s|^Disk ${partition_device}: ||;s|MB$||p")
> type="primary"
> parted -s "${partition_device}" mkpart "$type" "10" "60"
> parted -s "${partition_device}" set 1 bios_grub on
> parted -s "${partition_device}" mkpart "$type" "61" "161"
> parted -s "${partition_device}" mkpart "$type" "162" "$disk_size"
> /sbin/mkfs.ext3 "${partition_device}2"
> /sbin/mkfs.ext3 "${partition_device}3"
> mkdir -p /ucc_tmp/root
> mkdir -p /ucc_tmp/boot
> mount "${partition_device}3" /ucc_tmp/root
> touch /ucc_tmp/root/ucc_root_device
> echo "/dev/loop0    /   ext3   errors=remount-ro   0   1" >>/ucc_tmp/fstab
> echo "${partition_device}2     /boot ext3 defaults    0   2" >>/ucc_tmp/fstab
> echo "${partition_device} ext3 /boot" >> /ucc_tmp/copy_files
> 
>
Comment 4 Stefan Gohmann univentionstaff 2013-01-12 01:16:41 CET
Es gibt jetzt ein custom_partiton Beispiel welches LVM und cryptsetup verwendet.
Comment 5 Moritz Muehlenhoff univentionstaff 2013-02-04 10:27:09 CET
In the partition script the confirmation to partition the hard disk cannot be entered on a Thinkpad X201. I suppose a similar workaround is needed as for the standard partition setup
Comment 6 Stefan Gohmann univentionstaff 2013-02-05 07:32:26 CET
Please try again with the current version. Now the partition script is started with the input of /dev/console.

I wasn't able to reproduce it on different hardware.
Comment 7 Erik Damrose univentionstaff 2013-02-06 14:55:12 CET
Tested with the fix from rev38926. The example custom_partition script contained a typo (custonmer instead of customer).

sbin/custom_partition is executed if it is present in the initrd -> OK
The example custom_partition script creates an encrypted partition -> OK
Plymouth is deactivated to enable user interaction -> OK

-> Verified
Comment 8 Moritz Muehlenhoff univentionstaff 2013-03-26 09:14:18 CET
UCC 1.0 has been released: 
http://forum.univention.de/viewtopic.php?f=26&t=2417
http://forum.univention.de/viewtopic.php?f=54&t=2418

If this error occurs again, please use "Clone This Bug".