| Commit message (Collapse) | Author | Age | Files |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is only useful for older BIOSes, that don't support hybrid ISO
which can otherwise be burnt onto USB key as well.
|
|
|
|
|
|
| |
See #684134, though:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684134
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Quoting /usr/share/doc/cryptsetup/README.keyctl :
The current state for dm-crypt in Linux is that it is single threaded, thus
every dm-crypt mapping only uses a single core for crypto operations. To
use the full power of your many-core processor it is thus necessary to
split the dm-crypt device. For Linux software raid arrays the easiest
segmentation is to just put the dm-crypt layer below the software raid
layer.
However, this seems no longer true since 2.6.38, cf.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714806
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c029772125594e31eb1a5ad9e0913724ed9891f2
http://kernelnewbies.org/Linux_2_6_38#head-49f5f735853f8cc7c4d89e5c266fe07316b49f4c
Therefore encrypting the array (instead of assembling an array of encrypted
disks) shouldn't cause a performance cost. Also, it makes the ramdisk much
easier to configure :-)
|
|
|
|
|
|
|
|
|
|
|
|
| |
The non-blocking PRNG /dev/urandom doesn't block if it has been seeded
enough, sadly (e.g., if the entropy pool is empty). Reading a few bytes
from the *blocking* should ensure that "the kernel RNG has [...] reach
full entropy at least once, which guarantees cryptographic quality of
the rest of the /dev/urandom stream." -- Tor bug #10676
https://trac.torproject.org/projects/tor/ticket/10676
See also urandom(4).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
When compiling for x86_86 on a i386 machine or vice versa, the following
warning appears:
dpkg-architecture: warning: specified GNU system type x86_64-linux-gnu does not match gcc system type i486-linux-gnu, try setting a correct CC environment variable
However this is harmless, even if the multilib approach is a bit hacky
and does not replace a proper cross-compiler. Cf. bug #712000
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712000
|
| |
|
|
|
|
| |
Run 'ARCH=amd64 make' to preseed an AMD64 ISO image, etc.
|
|
|
|
| |
(I.e., make lintian happy.)
|
|
|
|
|
| |
Tested with the IntelĀ® Desktop Board DH87RL, BIOS [RLH8710H.86A] version
0323.
|
| |
|
|
|
|
| |
To the latest point release, 7.3.0.
|
| |
|
|
|
|
|
| |
To be clearer, and to follow the recommendation of the FSF, we include
a full header rather than a single sentence.
|
| |
|
|
|
|
|
| |
Replaced [ -n "$string" ] with [ "$string" ], and [ -z "$string" ] with
[ ! "$string" ].
|
| |
|
|
|
|
|
| |
'syslog' is meant for the messages generated internally by syslogd,
whereas 'user' is for user-level messages.
|
| |
|
|
|
|
|
|
| |
Each new VM is attributed a fresh static IPv4 (uniqueness is guaranteed
by merely incrementing the /24), and DNS entries are added libvirt's
dnsmasq instance.
|
|
|
|
|
| |
Move preseed-related stuff in ./preseed/, and vm-related stuff in
./virtualenv/.
|
| |
|
|
|
|
| |
Also, fripost-partman/encryption was renamed to fripost-partman/encrypt.
|
|
|
|
| |
Tested with mkfs.extX only.
|
| |
|
| |
|
|
|
|
| |
Cf. http://stackoverflow.com/questions/6852612/bash-test-for-empty-string-with-x
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|