Re: aptitude not working

2016-11-14 Thread Richard Braun
On Mon, Nov 14, 2016 at 04:52:25PM +0100, Richard Braun wrote: > > (btw: can you read out these values later on, with a command similar to > > dmesg? pausing VirtualBOX and typing out things is boring) Ah, by the way, practically none of us run the Hurd on VirtualBox, and it's known to behave badl

Re: aptitude not working

2016-11-14 Thread Richard Braun
On Mon, Nov 14, 2016 at 11:55:46AM +0100, Riccardo Mottola wrote: > how do I know actually which console I am running? could it be meaningful? > I have the issue also when running aptitude from a remote console (e.g. > through telnet) Well, telnet and ssh are remote so they're subject to netdde ha

Re: aptitude not working

2016-11-14 Thread Richard Braun
On Mon, Nov 14, 2016 at 11:53:44AM +0100, Riccardo Mottola wrote: > I increased the allocated RAM size of the VM to 1024MB and now I read this: Try 2g or even 3g. > (btw: can you read out these values later on, with a command similar to > dmesg? pausing VirtualBOX and typing out things is boring)

Re: aptitude not working

2016-11-14 Thread Riccardo Mottola
Hi Richard, Richard Braun wrote: From what you describe, it doesn't seem to be a hang caused by this. With your amount of memory, you shouldn't even have a HIGHMEM segment, which makes bugs even less likely. So I don't know what happened to your system, or if you're doing something wrong or not

Re: aptitude not working

2016-11-14 Thread Riccardo Mottola
Hi, Richard Braun wrote: Yes, but specifically : vm_page: page table size: 786414 entries (43008k) vm_page: DMA: pages: 4080 (15M), free: 0 (0M) vm_page: DMA: min:500 low:600 high:1000 vm_page: DIRECTMAP: pages: 233472 (912M), free: 217899 (851M) vm_page: DIRECTMAP: min:11673 low:14008 high:233