From owner-freebsd-current Sat May 30 12:09:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17846 for freebsd-current-outgoing; Sat, 30 May 1998 12:09:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17841 for ; Sat, 30 May 1998 12:09:39 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA10772; Sat, 30 May 1998 12:01:45 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd010703; Sat May 30 19:01:16 1998 Date: Sat, 30 May 1998 12:01:12 -0700 (PDT) From: Julian Elischer To: "Jordan K. Hubbard" cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-Reply-To: <15986.896513020@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 May 1998, Jordan K. Hubbard wrote: > > 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. :-) yeah, but I can fix that.. :-) > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message