I just started to try and get VirtualBox up and running on this server .. same
configuration as another server I already have a few of them running, but after
a period of time with the install, I get the above error pop up on my remote
console, and pinging to the server itself just dies …
I'm
Further to this … I just did a 'ctl-alt-del' through my remote console, which
appears to have 'unstuck' whatever it was, in that I got a bunch of Login:
prompts scroll up the screen (hit return a few times after it got stuck), after
which it seems to do a full shutdown and reboot, as if
On 24.02.2013 05:09, Jeremy Chadwick wrote:
On Sat, Feb 23, 2013 at 04:13:07PM -0800, Jeremy Chadwick wrote:
On Sun, Feb 24, 2013 at 02:28:08AM +0400, Michael BlackHeart wrote:
2013/2/24 Jeremy Chadwick j...@koitsu.org:
{snipping irrelevant stuff and fixing formatting}
atapci1@pci0:0:31:2:
Le mardi 12 février 2013 21:42:01 Ronald Klop a écrit :
On Tue, 12 Feb 2013 19:44:49 +0100, David Demelier
demelier.da...@gmail.com wrote:
Le mardi 12 février 2013 10:01:10 Andriy Gapon a écrit :
on 12/02/2013 09:57 David Demelier said the following:
Yes I have added debugging option in
Quoth Jeremy Chadwick j...@koitsu.org:
If there are people out there using, for example, SSDs on an ICH7 in
non-AHCI mode, it would be good to know and get pciconf -lvbc output
(specifically the entry for their ATA/SATA controller). But as with all
publicly released operating systems, most
On Sat, 23 Feb 2013 22:31:10 -0800
Jeremy Chadwick j...@koitsu.org wrote:
I downloaded it and looked at the source.
svnup.c:1002: warning: zero-length printf format string
svnup.c:1020: warning: zero-length printf format string
svnup.c:1027: warning: zero-length
On Sat, 2013-02-23 at 22:31 -0800, Jeremy Chadwick wrote:
Also, John, please consider using malloc(3) instead of heap-allocated
buffers like file_buffer[6][] (196608 bytes) and command[] (32769
bytes). I'm referring to this:
Why? I absolutely do not understand why people are always
On Sun, Feb 24, 2013 at 10:19:57AM -0700, Ian Lepore wrote:
On Sat, 2013-02-23 at 22:31 -0800, Jeremy Chadwick wrote:
Also, John, please consider using malloc(3) instead of heap-allocated
buffers like file_buffer[6][] (196608 bytes) and command[] (32769
bytes). I'm referring to this:
On 02/24/2013 03:24 PM, Jeremy Chadwick wrote:
On Sun, Feb 24, 2013 at 10:19:57AM -0700, Ian Lepore wrote:
On Sat, 2013-02-23 at 22:31 -0800, Jeremy Chadwick wrote:
Also, John, please consider using malloc(3) instead of heap-allocated
buffers like file_buffer[6][] (196608 bytes) and command[]
On Sun, 2013-02-24 at 13:24 -0800, Jeremy Chadwick wrote:
On Sun, Feb 24, 2013 at 10:19:57AM -0700, Ian Lepore wrote:
On Sat, 2013-02-23 at 22:31 -0800, Jeremy Chadwick wrote:
Also, John, please consider using malloc(3) instead of heap-allocated
buffers like file_buffer[6][] (196608
On 02/24/2013 05:43 PM, Ian Lepore wrote:
On Sun, 2013-02-24 at 13:24 -0800, Jeremy Chadwick wrote:
On Sun, Feb 24, 2013 at 10:19:57AM -0700, Ian Lepore wrote:
On Sat, 2013-02-23 at 22:31 -0800, Jeremy Chadwick wrote:
Also, John, please consider using malloc(3) instead of heap-allocated
On Sun, Feb 24, 2013 at 04:43:33PM -0700, Ian Lepore wrote:
On Sun, 2013-02-24 at 13:24 -0800, Jeremy Chadwick wrote:
On Sun, Feb 24, 2013 at 10:19:57AM -0700, Ian Lepore wrote:
On Sat, 2013-02-23 at 22:31 -0800, Jeremy Chadwick wrote:
Also, John, please consider using malloc(3)
Quoth Jeremy Chadwick j...@koitsu.org:
On Sun, Feb 24, 2013 at 10:19:57AM -0700, Ian Lepore wrote:
On Sat, 2013-02-23 at 22:31 -0800, Jeremy Chadwick wrote:
Also, John, please consider using malloc(3) instead of heap-allocated
buffers like file_buffer[6][] (196608 bytes) and command[]
On 20 Feb, Jeremy Chadwick wrote:
On Wed, Feb 20, 2013 at 10:29:05PM -0800, Don Lewis wrote:
On 17 Feb, Torfinn Ingolfsen wrote:
Hello,
I'm running FreeBSD 8.3-stable on a machine with an AMD A8-5600K cpu.
tingo@kg-quiet$ uname -a
FreeBSD kg-quiet.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #2:
Ben Morrow wrote this message on Mon, Feb 25, 2013 at 00:28 +:
1. Such buffers exist during the entire program's lifetime even if they
aren't actively used/needed by the program. With malloc(3) and friends,
you're allocating memory dynamically, and you can free(3) when done with
it,
15 matches
Mail list logo