From owner-freebsd-current Sat May 30 00:26:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09015 for freebsd-current-outgoing; Sat, 30 May 1998 00:26:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09004 for ; Sat, 30 May 1998 00:26:09 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id AAA15994; Sat, 30 May 1998 00:23:40 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Poul-Henning Kamp cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Sat, 30 May 1998 09:04:38 +0200." <15401.896511878@critter.freebsd.dk> Date: Sat, 30 May 1998 00:23:40 -0700 Message-ID: <15986.896513020@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The logical thing would be for "undelete" to work here... Assuming removals became whiteouts, yes. The only fs I know which currently does that is unionfs, however. > Have you tried that ? See above - what good would that do? :) I even tried it with unionfs, just for grins, and it wouldn't allow me to change anything at all. :) Oh yeah, Eivind: I also tried the mv trick, mounting the 2nd instance and then moving a file over? Works great, but with an unforseen side-effect: You can't unmount the 2nd filesystem instance after that. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message