Hi hackers,
i have an Intel Core 2 server with on-board pseudo hardware SATA RAID
-- Intel MatrixRAID. The RAID itself is configured in RAID1. The server is
running FreeBSD 6.2-Release/AMD64.
Since several days i have being found the follwoing messages in the
system
At Mon, 11 Jun 2007 13:12:04 -0700,
Chuck Swiger wrote:
If you ever use it, fdisk /dev/rdisk0 will show things differently.
The first partition with id 0xEE will should start at LBA 40 and end
at LBA 409640.
OK: although that surprises me a bit, perhaps trying to get Windows
XP (which
Matthew Dillon wrote:
It really sounds like they are making an accomodation for BIOS
booting or older Windows booting... or *something* of that sort. The
fact that the bootability bit is not set in the MBR (I'm not sure about
that, is it set or not?)... that seems to imply a
At Mon, 11 Jun 2007 13:33:42 -0700 (PDT),
Matthew Dillon wrote:
: # gpt -r show /dev/rdisk0
:start size index contents
:0 1 PMBR
:1 1 Pri GPT header
:2 32 Pri GPT table
: 34
Jeremy Chadwick [EMAIL PROTECTED] writes:
One could enable use of this with some loader.conf variable like
loader_frames=ascii or (default) loader_frames=cp437, possibly
even a vt100 type (using VT100 line-drawing characters).
It should probably be the default.
I'm not familiar with forth,
On Tue, Jun 12, 2007 at 04:07:40PM +0200, Dag-Erling Smørgrav wrote:
Jeremy Chadwick [EMAIL PROTECTED] writes:
One could enable use of this with some loader.conf variable like
loader_frames=ascii or (default) loader_frames=cp437, possibly
even a vt100 type (using VT100 line-drawing
Jeremy Chadwick [EMAIL PROTECTED] writes:
On Tue, Jun 12, 2007 at 04:07:40PM +0200, Dag-Erling Smørgrav wrote:
Jeremy Chadwick [EMAIL PROTECTED] writes:
One could enable use of this with some loader.conf variable like
loader_frames=ascii or (default) loader_frames=cp437, possibly
even
Hi.
I just have a few queries regarding kqueue. Ive read through the tutorial
given on the netbsd page, as well as the pdf detailing kqueue.
What I want to do is write a single threaded server for listening for
connections, and then check if they are ready to be read from for each
connection.
Cole wrote:
I wanted to know, what must be done when the sockets/file
descriptors close. Do I need to decrease number_events and
resort the events array so that all the active kevents are
sequential without any closed sockets still in that array?
It occurs to me, you might be trying to use
Cole wrote:
If I do the above, and just keep increasing number_events and
just mark the kevent as EV_DISABLED or EV_DELETE then all it
does is return that event as soon as I call kevent() with the
following values: ident : 7, filter : -1, flags : 16384
That flags value is EV_ERROR. It
Title says it all -- is there a particular reason why malloc/bzero
should be used instead of calloc?
-Garrett
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to
Another simple question (I hope):
Is there any reason why shell commands should be used in place of a
C command (in this case chmod via vsystem instead of the chmod(2)
function)? It seems like the fork / exec would be more expensive with
the shell command, but any area where code could be
12 matches
Mail list logo
