[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] console interface

  • To: Hannes Mehnert <hannes@xxxxxxxxxxx>
  • From: Anil Madhavapeddy <anil@xxxxxxxxxx>
  • Date: Mon, 14 Nov 2016 15:04:34 +0000
  • Cc: mirageos-devel <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 14 Nov 2016 15:04:42 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=recoil.org; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=eCtNQWNmK6R3k5/bnQqSXDbmrhFcECAgt5jVm8KVdB7P2phxe8r Q+mx+ig5G/v2UngnMB8BPRcrMLaDvpJoLPBOiPgn0sgozvxHgYcTpiAzKoZ59Zqf JYekcT1FAAmp3aOyDCS806RD2cOAU3zkEH880p2QWCmwWaQ72llK0/PE=
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>

On 12 Nov 2016, at 15:45, Hannes Mehnert <hannes@xxxxxxxxxxx> wrote:
> I tried to find the reasoning behind the log functions in the module
> type CONSOLE (using the git history).
> Some facts:
> - Nowadays (since 15th October 2014, or Mirage-2.0.0) a CONSOLE is a
> FLOW (and thus has read/write/writev/close)
> - there is a log_s : t -> string -> unit io
> - and a log : t -> string -> unit

The use of 'log' and 'log_s' date wayyy back to when we log to an
emergency console, and don't really fit in once the library ecosystem
caught up and we have proper logging infrastructure now.

This PR seems to go in the right direction to clean things up.  Thanks!


MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.