search for: xcs_msg_t

...-I /usr/local/lib/ocaml -Wall -g \ \ -o pdb_caml_xcs.o " pdb_caml_xcs.c pdb_caml_xcs.c:27:23: error: xcs_proto.h: No such file or directory pdb_caml_xcs.c: In function ''xcs_write_message'': pdb_caml_xcs.c:87: error: ''xcs_msg_t'' undeclared (first use in this function) pdb_caml_xcs.c:87: error: (Each undeclared identifier is reported only once pdb_caml_xcs.c:87: error: for each function it appears in.) pdb_caml_xcs.c:87: error: syntax error before ''my_msg'' pdb_caml_xcs.c:90: error: ''my_...

Just forwarding this changelog from yesterday. xcs now uses Unix domain sockets in unstable. This was a hot thread a couple months back with strong opinions on both sides and no clear resolution on the list, so I thought some people might like to know the developers'' resolution. This should be good news for those seeking tighter dom0''s, particularly those who

...;is_dead) { >- remove_domain(dom); >+ struct domain *n; >+ >+ while (dom != NULL) { >+ n = dom->next; >+ if (dom->is_dead) >+ remove_domain(dom); >+ dom = n; > } > } > > static void handle_tty_read(struct domain *dom) > { > ssize_t len; >- xcs_msg_t msg; >- >- msg.type = XCS_REQUEST; >- msg.u.control.remote_dom = dom->domid; >- msg.u.control.msg.type = CMSG_CONSOLE; >- msg.u.control.msg.subtype = CMSG_CONSOLE_DATA; >- msg.u.control.msg.id = 1; >- >- len = read(dom->tty_fd, msg.u.control.msg.msg, 60); >+ char ms...