From 1f7e7501660123ff8f26e8c65e75c2b282b933ef Mon Sep 17 00:00:00 2001
From: dzwdz
Date: Fri, 8 Jul 2022 14:40:44 +0200
Subject: syscall/fs_respond: get the file id from the buf argument

Previously, file ids could only be positive integers, so their range
was 31 bits - not enough to represent the entire memory. Now, pointers
can be safely used as file ids.
---
 src/init/driver/ansiterm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/init/driver/ansiterm.c')

diff --git a/src/init/driver/ansiterm.c b/src/init/driver/ansiterm.c
index 4d98972..b7f0b04 100644
--- a/src/init/driver/ansiterm.c
+++ b/src/init/driver/ansiterm.c
@@ -83,7 +83,7 @@ void ansiterm_drv(void) {
 					break;
 				}
 				// TODO check path
-				_syscall_fs_respond(NULL, 1, 0);
+				_syscall_fs_respond(NULL, 0, 0);
 				break;
 
 			case VFSOP_WRITE:
-- 
cgit v1.2.3