On Wed, Nov 16, 2016 at 11:03:44AM +0100, Riccardo Mottola wrote:
> Miguel Figueiredo wrote:
> >I think not. I've "always" seen one the annoying small thing in aptitude
> >in Hurd, pressing q to quit and it does not quits. If i repeat the q and
> >then Ctrl+C, it quits and I see the on the
Hi,
Richard Braun wrote:
I increased the allocated RAM size of the VM to 1024MB and now I read this:
Try 2g or even 3g.
I can't allocate more.. 2G is about the limit for my host, but I did
allocate 2048 MB of ram, did a "fresh boot", accessed directly root and
started aptitude and issued
Hi,
Miguel Figueiredo wrote:
I think not. I've "always" seen one the annoying small thing in
aptitude in Hurd, pressing q to quit and it does not quits. If i
repeat the q and then Ctrl+C, it quits and I see the on the console.
I've seen this on Virtualbox, but now i have it on qemu with
On 07-11-2016 13:44, Riccardo Mottola wrote:
Hi,
anybody of you using aptitude?
It has a strange malfunction to me: I select the action on packages
(e.g. opdate or install) then confirm the next review step then, if
necessary, downloads will happen, then it hangs. It never starts
You're much better off using qemu. You can read about how to set up an
instant development environment here:
https://www.gnu.org/software/hurd/contributing.html#index4h2
Do not pass the "|-no-kvm-irqchip" |||option. Also the default *img
file is only has space for about 2 GBs I think. You may
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
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
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
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
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
On Mon, Nov 07, 2016 at 05:34:23PM +0100, Riccardo Mottola wrote:
> do you mean what vm_page reports at the earliest stages of boot?
> It says 751M in pages, 733M free
Yes, but specifically :
vm_page: page table size: 786414 entries (43008k)
vm_page: DMA: pages: 4080 (15M), free: 0 (0M)
vm_page:
Hi Richard,
Richard Braun wrote:
On Mon, Nov 07, 2016 at 04:59:09PM +0100, Riccardo Mottola wrote:
it still had plenty of free RAM, the system wasn't doing anything else.
Let's assume that's the case, although it may still happen that, between
two top samples, the system could allocate a huge
On Mon, Nov 07, 2016 at 04:59:09PM +0100, Riccardo Mottola wrote:
> it still had plenty of free RAM, the system wasn't doing anything else.
Let's assume that's the case, although it may still happen that, between
two top samples, the system could allocate a huge amount of memory and
hang. And
Hi,
Richard Braun wrote:
On Mon, Nov 07, 2016 at 03:51:26PM +0100, Riccardo Mottola wrote:
I did try checking top in a second terminal.
On opening, aptitude has 66mb RES 132MB virtual
after "g" it grows just a little more, I hit gh once again and It ramps up
to 72Mb RES, 128 VIRT... and staus
On Mon, Nov 07, 2016 at 03:51:26PM +0100, Riccardo Mottola wrote:
> I did try checking top in a second terminal.
> On opening, aptitude has 66mb RES 132MB virtual
> after "g" it grows just a little more, I hit gh once again and It ramps up
> to 72Mb RES, 128 VIRT... and staus there, 9% of memory.
Hi,
Richard Braun wrote:
I use aptitude and have no such problem. On the other hand, the Hurd
may be hanging. Using aptitude can lead to large memory usage, which
can increase swap usage, and fill kernel memory (in older kernels at
least).
So, what's your version of GNU Mach ? And how much
On Mon, Nov 07, 2016 at 02:49:35PM +0100, Richard Braun wrote:
> So, what's your version of GNU Mach ? And how much memory do you have
> on your system ?
We also know network can just randomly hang because of bugs in the
netdde server.
--
Richard Braun
On Mon, Nov 07, 2016 at 02:44:13PM +0100, Riccardo Mottola wrote:
> anybody of you using aptitude?
> It has a strange malfunction to me: I select the action on packages (e.g.
> opdate or install) then confirm the next review step then, if necessary,
> downloads will happen, then it hangs. It never
Hi,
anybody of you using aptitude?
It has a strange malfunction to me: I select the action on packages
(e.g. opdate or install) then confirm the next review step then, if
necessary, downloads will happen, then it hangs. It never starts
unpacking/configuring things. I can hit ctr-lc and notice
19 matches
Mail list logo
