search for: _automatically_

...ng a 2TB drive. Now, those green drives suck quite hard, but not _that_ hard. I''m guessing the reason for this slowdown is the fill of those three first VDEVs. Now, is there a way, manually or automatically, to somehow balance the data across these LVOLs? My first guess is that doing this _automatically_ will require block pointer rewrite, but then, is there way to hack this thing by hand? PS: Yeah, I know, it''s more disks on the fourth VDEV than on the first three, but this was how wi chose to do it. PPS: c10d1s1 and c11d0s1 is the SLOG mirror, even though zpool iostat doesn''t s...

...E7E7D8B196756E40E80B5EC3A13 sambaPwdLastSet: 1201260229 I did not manually change those properties and i wonder who or why they changed. The result is that my windows client can not log into the domain anymore. I have to remove it fro the domain and add it again. Has anyone an idea why this is _automatically_ happening? Do you need more infos? Thanks, Mario

...ss stuff but it's simpler and easier to maintain that building+maintaining the list of what exactly we need to copy. YMMV :) > 2_ The whole EFI\BOOT\grub directory could potentially be deleted. > IIRC, the initial intention of having both, syslinux.efi and grub.efi > in TAILS was to _automatically_ load the adequate efi binary for each > EFI architecture (x86 / ia32), overcoming a (prior) limitation in > Syslinux. Syslinux 6.04-pre1 already includes a solution for this > situation. We'll see whether intrigeri bites ;). Assuming you're referring to commit 7d9c9ec ("co...

Actually, as you may have questions with some elements you'll see in the log, and especially: Detected Syslinux version: 6.03/20150819 (from '/EFI/BOOT/isolinux.bin') So I should point out that EFI/grub is actually used by the tails people to chain load EFI/Syslinux (hence the ldlinux.e64, ldlinux.c32 as well as isolinux.bin one also sees in /efi/boot/). As a result, in the

...file is worthless for EFI. From the list of files, probably this is not the only file from Syslinux that could be deleted in this ISO image. 2_ The whole EFI\BOOT\grub directory could potentially be deleted. IIRC, the initial intention of having both, syslinux.efi and grub.efi in TAILS was to _automatically_ load the adequate efi binary for each EFI architecture (x86 / ia32), overcoming a (prior) limitation in Syslinux. Syslinux 6.04-pre1 already includes a solution for this situation. We'll see whether intrigeri bites ;). However, I do not see "ldlinux.e32" in the list provided by Pe...