Bug#418519: Layout example

I've just remembered that this wishlist exists... Here I've copied our server's current layout as motivational example: $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda8:00 186.3G 0 disk └─sda1 8:10 186.3G 0

Bug#779366: task-kde-desktop: nepomuk-core-runtime missing while nepomuk-core-data with non-working shortcuts exists

Package: task-kde-desktop Version: 3.29 Severity: important Dear Maintainer, I have installed Jessie amd64 form RC1 netinst iso with KDE and OpenSSH tasks selected in virtual machine. In app list I can see "Nepomuk Cleaner" and "Nepomuk Backup" shortcuts, but then I click I get message: "KDEInit

Bug#776002: Other problems

On Sun, 25 Jan 2015 14:34:52 + Ben Hutchings wrote: > What if you set it to "linux-image/wheezy-backports > initramfs-tools/wheezy-backports"? Thank you, that helped! But...I have other problem - ifupdown package is removed during install, and so I have system without network... Here's my

Bug#418519: Reason for having raw disk as physical volume

2015.01.03 17:24, Lennart Sorensen wrote: Also there has to be somewhere to install the bootloader, and blockmapping into the filesystem is a very bad idea Uhm, yes, of course. Bootloader is just before /dev/sda1 partition, which may be /boot or a dummy/unused. Everything in /dev/sda raid v

Bug#418519: Reason for having raw disk as physical volume

2015.01.02 22:13, Geert Stappers wrote: "workaround": use an additional dedicated boot disk[1] With HW Raid, it's exactly what we intended to do: create very small volume (for Linux point of view it's just /dev/sda) to be as "boot disk", containing only boot loader (and maybe /boot), which sh

Bug#418519: Reason for having raw disk as physical volume

Hello, I can tell example where having raw disk as PV is handy: using hardware RAID controllers, such as Areca ones. Raid controllers allows you to add new disks to existing raid array. For example, if you have Raid 10 using four 1TB disks, you can add two more disks and increase capacity from 2T