From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Hansen Subject: Re: [RFC][PATCH] Devices visibility container Date: Wed, 26 Sep 2007 08:36:12 -0700 Message-ID: <1190820972.26982.359.camel@localhost> References: <46F77523.9020001@openvz.org> <46F8BD33.5040108@openvz.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: "Eric W. Biederman" Cc: Linux Containers , Paul Menage , Pavel Emelyanov List-Id: containers.vger.kernel.org On Tue, 2007-09-25 at 07:30 -0600, Eric W. Biederman wrote: > Pavel Emelyanov writes: > > > > Oh! Can you provide us an example when after the migration some > > device's major+minor pair change on the same device? > > SCSI disks on a SAN. Network accessible block devices. > All kinds of logical/virtual devices like ttys, the loop device, and > ramdisks. > > It isn't especially frequent that something cares, but fundamentally > the same issues apply. To be clear, this just covers cases where an application has _internalized_ the device number, right? Most applications should be pretty happy with the devices having persistent device names across a restart, and we can do that with udev and no kernel patching. -- Dave