Date: Sat, 25 Jan 2003 14:38:02 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: "Eugene M. Kim" <ab@astralblue.net> Cc: Alexey Dokuchaev <danfe@nsu.ru>, Gordon Tetlow <gordont@gnf.org>, Garance A Drosihn <drosih@rpi.edu>, arch@FreeBSD.ORG Subject: Re: CFR: Volume labels in FFS Message-ID: <3E3311CA.5646F3AA@mindspring.com> References: <20030124212259.GJ53114@roark.gnf.org> <p05200f17ba5764ef8e3a@[128.113.24.47]> <20030124215753.GM53114@roark.gnf.org> <20030124222718.GN53114@roark.gnf.org> <3E31C4F5.972AA69C@mindspring.com> <20030125120433.GA24687@regency.nsu.ru> <20030125185338.GA54691@purple.the-7.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"Eugene M. Kim" wrote: > > > > I can also forsee being able to hook into devd to do some > > > > automounting magic for things like zip disks and cdroms > > > > (obviously not with FFS, but cd9660 support would be a good > > > > thing to have once GEOM recognizes cdroms). > > > > > > That's what "Last mounted on" is for. > > > > > > Gotta wonder why we need volume devices, when we know where we > > > are going to mount the thing... > > > > I second Terry here; seeing little-to-none sense in volume lables as > > they are. > > `Last mounted on' is useful only when a disk is assumed to be used on > one computer. If you wanted to mount a removable data disk at /data on > computer A but at /mydata on computer B and so on, we do need some > volume label. You all misunderstand. I was asking why you were introducing another field in the superblock, rather than using the "last mounted on" field. Maybe I should point out that the "last mounted on" field is write-only, and no one uses it, particularly since it is not longer possible to open the block device and examine a live FS (given that there are no longer block devices). I'll also point out that the only reason an FS type has to be able to distinguish a root mount from a non-root mount boils down to two things: o Covering the moint point, which should be done in upper level code anyway, since it's an operation common to all FS's in the non-root mount case o Setting of the "last mounted on" data contents in the superblock Even if nothing else happens, and you decide to keep around this appendix of "last mounted on", at the very least, the code should be reorganized so that the setting/getting of it is a new VFSOP. Note that I first suggested doing this, and provided code that did this, in 1996. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E3311CA.5646F3AA>