Subject: Re: dump(8) behaviour
To: Manuel Bouyer <firstname.lastname@example.org>
From: Greywolf <email@example.com>
Date: 04/02/2000 10:50:54
On Sun, 2 Apr 2000, Manuel Bouyer wrote:
# On Sun, Apr 02, 2000 at 01:55:52AM -0800, Greywolf wrote:
# > Is there a reason that dump(8) looks in the mount table instead of the
# > fstab when it's matching devices to directories? Is it really that
# > common that you'll want to dump a subdirectory which matches an unmounted
# > device?
# > I'm too used to sunisms, I guess. I like being able to type:
# > # dump 0bsdf 63 6000 54000 /usr
# > and have it deduce that /usr is really associated with an unmounted
# > device instead of trying to do a partial dump of the /usr directory
# > under the root filesystem.
# On the other hand you may want to dump /mnt, which is a temporary
# mount not in the fstab. If we look at the fstab only we'll have a partial
# dump of / instead of the expected filesystem ... I'm not sure this is a big
# deal; I always give devices names anyway :)
Fine. Teach me to type when tired.
I meant, "Shouldn't it try to resolve the mount point, i.e. go to mount
table, then to fstab, before punting and dumping the named point as a
# Manuel Bouyer <firstname.lastname@example.org>
Microsoft: "Where do you want to go today?"
Linux: "Where do you want to be tomorrow?"
BSD: "Are you guys coming, or what?"