On Sat, Sep 29, 2012 at 05:50:05PM +0200, intrigeri wrote:
> > What's your opinion? Should I proceed in adding a custom
> > `python-dbus` to the multikernel branch?
>
> Please proceed: at least so that we can verify that this hack
> workarounds the bug in various settings.
Done. Merged in experim
On Sat, Sep 29, 2012 at 08:42:37PM +0200, intrigeri wrote:
> These Vagrant / memory tweaks made in the feature/multikernel branch
> should be re-done there, as they conflicted with those made in
> feature/vagrant and since then merged into devel, which I've just
> merged back into feature/multikern
anonym wrote (06 Sep 2012 09:18:03 GMT) :
> 05/09/12 23:38, anonym wrote:
>> 04/09/12 14:52, intrigeri:
>>> So, I just merged the feature/multikernel branch into experimental.
>>
>> Built and so far tested in VirtualBox.
> I forgot to say that this pushed the amount of RAM required to build
> Tai
Hi,
Ague Mill wrote (28 Sep 2012 15:27:18 GMT) :
> So my hack have been to add a call to `dbus_thread_init_default()`
> in the initialization of the Python `dbus` module. And it looks like
> it solve the issue. I have not been able to get the installer to
> crash after installing the modified `pyt
On Thu, Sep 27, 2012 at 11:57:06AM +0200, intrigeri wrote:
> anonym wrote (27 Sep 2012 09:38:32 GMT) :
> > This was in Tails built from feature/multikernel.
>
> Thank you. I updated the ticket accordingly. So, next step is: somehow
> fix our USB installer vs. the 686-pae kernel. I'm not committing
anonym wrote (27 Sep 2012 09:38:32 GMT) :
> This was in Tails built from feature/multikernel.
Thank you. I updated the ticket accordingly. So, next step is: somehow
fix our USB installer vs. the 686-pae kernel. I'm not committing to do
it any time soon.
12/09/12 11:05, intrigeri wrote:
> hi,
>
> anonym wrote (06 Sep 2012 18:27:37 GMT) :
>> The crash occurs on my (64-bit) laptop. :/
>
> Do you mean, on your own system (if so: both kernel / userspace
> 64-bits? Debian Wheezy?) or within Tails feature/multikernel with the
> 686-pae kernel?
This wa
Hi,
> From: intrigeri
> Date: Wed, 12 Sep 2012 11:05:56 +0200
>
[...]
>
> anonym wrote (06 Sep 2012 18:27:37 GMT) :
> > The crash occurs on my (64-bit) laptop. :/
>
> Do you mean, on your own system (if so: both kernel / userspace
> 64-bits? Debian Wheezy?) or within Tails feature/multikernel
hi,
anonym wrote (06 Sep 2012 18:27:37 GMT) :
> The crash occurs on my (64-bit) laptop. :/
Do you mean, on your own system (if so: both kernel / userspace
64-bits? Debian Wheezy?) or within Tails feature/multikernel with the
686-pae kernel?
___
tails-de
anonym wrote (11 Sep 2012 15:32:01 GMT) :
> 11/09/12 14:14, Ague Mill wrote:
>> This does not feel right. The `ifcpu64.c32` module should be copied
>> from the same syslinux package than the one that is going to be
>> used later on by live-build, not by the one installed in the
>> building system.
11/09/12 14:14, Ague Mill wrote:
> On Tue, Sep 04, 2012 at 02:52:53PM +0200, intrigeri wrote:
>> So, I just merged the feature/multikernel branch into experimental.
>
> Looks like `20-syslinux_detect_cpu` has an issue. In commit 0194501a7,
> syslinux was added as a system-wide dependency (for Vagr
On Tue, Sep 04, 2012 at 02:52:53PM +0200, intrigeri wrote:
> So, I just merged the feature/multikernel branch into experimental.
Looks like `20-syslinux_detect_cpu` has an issue. In commit 0194501a7,
syslinux was added as a system-wide dependency (for Vagrant) to build
Tails.
This does not feel r
On Thu, Sep 6, 2012 at 12:38 AM, anonym wrote:
> This won't work. Even with PAE, processes cannot have more than 4 GB of
> memory (after all, pointers are still 32 bit = 4 GB).
>
> [...]
>
> It's seems we still have to wait for Ague's wipe_memory GRUB module.
You can stop suffering from the NIH s
04/09/12 14:52, intrigeri wrote:
> Hi,
>
> for various reasons (supporting big amounts of RAM, supporting >1 CPU
> core, NX bit), we want to ship a 686-pae kernel in addition to the
> current (486, non-SMP) one we already have, and make the bootloader
> autodetect the most appropriate kernel depen
anonym wrote (06 Sep 2012 09:18:03 GMT) :
> I forgot to say that this pushed the amount of RAM required to build
> Tails in-memory to over 6 GiB (at least when using Vagrant) so
> I pushed commit 974805d to bump it to 7 GiB.
I don't use Vagrant (yet?) so I don't care that much, but for those
who h
05/09/12 23:38, anonym wrote:
> 04/09/12 14:52, intrigeri:
>> So, I just merged the feature/multikernel branch into experimental.
>
> Built and so far tested in VirtualBox.
I forgot to say that this pushed the amount of RAM required to build
Tails in-memory to over 6 GiB (at least when using Vagr
04/09/12 14:52, intrigeri:
> Hi,
>
> for various reasons (supporting big amounts of RAM, supporting >1 CPU
> core, NX bit), we want to ship a 686-pae kernel in addition to the
> current (486, non-SMP) one we already have, and make the bootloader
> autodetect the most appropriate kernel depending o
Hi,
for various reasons (supporting big amounts of RAM, supporting >1 CPU
core, NX bit), we want to ship a 686-pae kernel in addition to the
current (486, non-SMP) one we already have, and make the bootloader
autodetect the most appropriate kernel depending on what the
CPU supports.
Work towards
18 matches
Mail list logo
