linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Anthony Brock <brocka@sterlingcgi.com>
Subject: Re: [uml-devel] Re: pcap cross-linking [PATCH]
Date: Fri, 23 Dec 2005 17:11:26 +0100	[thread overview]
Message-ID: <200512231711.27326.blaisorblade@yahoo.it> (raw)
In-Reply-To: <CGEGKKNGBDKPCKOKKGFEIEBACDAA.brocka@sterlingcgi.com>

On Thursday 22 December 2005 18:57, Anthony Brock wrote:
> I don't think the attachment made it into the email.
It was in the previous one but I had forgot to describe it - sorry for the 
misunderstanding.

> However, I am 
> attaching one that we've used with good success. It allows us to also
> specify a "nice" level for the UML kernel in addition to the chroot-setuid.
Nice tool, well written.

Only one minor complaint: you do the following sequence (excluding error 
paths):

	chdir(chroot_dir);
	chroot(chroot_dir);

this will fail needlessly if a relative path is used.

Replacing the chroot with chroot(".") would be better, IMHO.

One question: would 
	chroot(chroot_dir);
	chdir("/");
work equally well?
I've not seen it used so I wonder (a bit) if there can be some hidden bug.
-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade

	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2005-12-23 16:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-18 19:03 [uml-devel] pcap cross-linking Antoine Martin
2005-12-19 16:16 ` [uml-devel] " Blaisorblade
2005-12-19 18:33   ` [uml-devel] Re: pcap cross-linking [PATCH] Antoine Martin
2005-12-19 19:27     ` Blaisorblade
2005-12-19 21:47       ` Antoine Martin
2005-12-20 14:23         ` Blaisorblade
2005-12-20 16:25           ` Antoine Martin
2005-12-20 19:24             ` Blaisorblade
2005-12-20 20:01     ` Rob Landley
2005-12-20 20:24       ` Antoine Martin
2005-12-20 20:43       ` Blaisorblade
2005-12-21 18:13         ` Blaisorblade
2005-12-22 17:57           ` Anthony Brock
2005-12-23 16:11             ` Blaisorblade [this message]
2005-12-26  7:47               ` Anthony Brock
2005-12-29 20:12               ` Rob Landley
2006-01-01 18:51                 ` Blaisorblade
2006-01-01 21:01                   ` Rob Landley
2006-01-02 20:10                     ` Blaisorblade
2005-12-19 18:39   ` [uml-devel] Re: pcap cross-linking Blaisorblade

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=200512231711.27326.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=brocka@sterlingcgi.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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