Linux Container Development
 help / color / mirror / Atom feed
From: Louis Rilling <Louis.Rilling-aw0BnHfMbSpBDgjK7y7TUQ@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: how to handle devpts
Date: Tue, 1 Dec 2009 10:37:08 +0100	[thread overview]
Message-ID: <20091201093708.GC2430@hawkmoon.kerlabs.com> (raw)
In-Reply-To: <20091130202223.GA20224-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2620 bytes --]

Hi Serge,

On 30/11/09 14:22 -0600, Serge E. Hallyn wrote:
> We currently checkpoint and restart unix98 ptys in the kernel.
> So what do we want to do about the userspace part?  In particular,
> if I run the following test program and checkpoint it, it
> has `tty` open.  What do we want to do about that?
> 
> Just having user-cr/restart.c take an option to mount a new
> instance of devpts isn't enough - we don't get hooked up to
> restart.c's stdin/out obviously, and restart succeeds but the
> restarted program exists with -EIO.  At the same time, just
> doing a cradvise type of thing to plug fds 0,1,2 suffice for
> this testcase, but not for something more complicated which
> also has other unix98 ptys open.

In Kerrighed we are implementing something à-la-cradvise: we allow the
caller of sys_restart() to give replacement fds for arbitrary files. To achieve
this, each checkpointed file descriptor (struct file) has a unique key, and
sys_restart() takes a substitution table in parameter, where an entry is a
pair (key, fd).

In Kerrighed sys_checkpoint() exports a human-readable table of checkpointed
file descriptors, with types, fd in each checkpointed task, etc.
With Oren's patchset, I presume that some userspace tool could extract such a
table from the checkpoint.

Hope this makes the discussion progress...

Louis

> 
> Do we require that it be run in screen?  Then what about the
> screen session's terminals themselves?
> 
> Anyway, I have this feeling that other have already thought
> through this, so here is the simple program for discussion:
> 
> #include <stdio.h>
> #include <curses.h>
> #include <string.h>
> 
> int main(int argc, char *argv[])
> {
> #define MAXLEN 20
> 	char input[MAXLEN+1];
> 	int i = 0;
> 
> 	initscr();
> 	cbreak();
> 	//noecho();
> 	nonl();
> 	intrflush(stdscr, FALSE);
> 	keypad(stdscr, TRUE);
> 
> 	addstr("Enter some text: ");
> 	memset(input, 0, MAXLEN+1);
> 	while (1) {
> 		input[i] = getch();
> 		if (input[i] == KEY_ENTER || input[i]=='\r')
> 			break;
> 		i++;
> 		if (i == MAXLEN)
> 			break;
> 	}
> 	endwin();
> 	printf("I read the text: %s\n", input);
> 	return 0;
> }
> 
> -serge
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers

-- 
Dr Louis Rilling			Kerlabs
Skype: louis.rilling			Batiment Germanium
Phone: (+33|0) 6 80 89 08 23		80 avenue des Buttes de Coesmes
http://www.kerlabs.com/			35700 Rennes

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 206 bytes --]

_______________________________________________
Containers mailing list
Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
https://lists.linux-foundation.org/mailman/listinfo/containers

  parent reply	other threads:[~2009-12-01  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 20:22 how to handle devpts Serge E. Hallyn
     [not found] ` <20091130202223.GA20224-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-12-01  9:37   ` Louis Rilling [this message]
     [not found]     ` <20091201093708.GC2430-Hu8+6S1rdjywhHL9vcZdMVaTQe2KTcn/@public.gmane.org>
2009-12-01 15:02       ` Serge E. Hallyn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091201093708.GC2430@hawkmoon.kerlabs.com \
    --to=louis.rilling-aw0bnhfmbspbdgjk7y7tuq@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox