On Mon, Jan 20, 2014 at 7:20 PM, Yoann Padioleau wrote:
> Hi,
>
> in 9/pc/mem.h it says:
> /*
> * Address spaces
> */
> #define KZERO 0xF000 /* base of kernel address
> space */
> #define KTZERO (KZERO+0x10)/* first address in kernel
> text - 9l
On Mon Jan 20 20:21:28 EST 2014, p...@fb.com wrote:
> Hi,
>
> in 9/pc/mem.h it says:
> /*
> * Address spaces
> */
> #define KZERO 0xF000 /* base of kernel
> address space */
> #define KTZERO (KZERO+0x10)/* first address in
> kernel t
Hi,
in 9/pc/mem.h it says:
/*
* Address spaces
*/
#define KZERO 0xF000 /* base of kernel address space
*/
#define KTZERO (KZERO+0x10)/* first address in kernel text
- 9load sits below */
and in 9/pc/mkfile:
# must match mem.h
APBOOTSTRAP=0xF00
On Mon, Jan 20, 2014 at 07:15:45PM +0100, cinap_len...@felloff.net wrote:
> xd does output buffering. only when the buffer is full or it gets
> to the end of the file (never in case of /dev/mouse) it writes to
> the output.
>
> you can disable buffering with the -u flag, see xd(1) in the
> manual.
xd does output buffering. only when the buffer is full or it gets
to the end of the file (never in case of /dev/mouse) it writes to
the output.
you can disable buffering with the -u flag, see xd(1) in the
manual.
--
cinap
Hello all.
Is it normal that i can't see any output of cat /dev/mouse | xd?
I see cat /dev/mouse output, cat anyfile | xd output, but no cat /dev/mouse | xd
output.
On 20 January 2014 06:49, Amol Dixit wrote:
> I
see intro(5): "All requests on a connection share the same fid space"
If several clients share one connection, as intro(5) says:
"the agent managing the sharing must arrange that no two clients choose the
same fid".
That happens for instance with
