diff options
| author | marcel <marcel@FreeBSD.org> | 2011-11-07 16:21:50 +0000 |
|---|---|---|
| committer | marcel <marcel@FreeBSD.org> | 2011-11-07 16:21:50 +0000 |
| commit | 7952c4cb03288bf37926317c876ffb237f526ef8 (patch) | |
| tree | 8f9bb87ce0fe827fa698d7b9eb159c4fcf2125ed /sys/fs/tmpfs | |
| parent | 0c56cf839d3e773173db46a972d3792e8a36820d (diff) | |
| download | FreeBSD-src-7952c4cb03288bf37926317c876ffb237f526ef8.zip FreeBSD-src-7952c4cb03288bf37926317c876ffb237f526ef8.tar.gz | |
Don astbestos garment and remove the warning about TMPFS being experimental
-- highly experimental even. So far the closest to a bug in TMPFS that people
have gotten to relates to how ZFS can take away from the memory that TMPFS
needs. One can argue that such is not a bug in TMPFS. Irrespective, even if
there is a bug here and there in TMPFS, it's not in our own advantage to
scare people away from using TMPFS. I for one have been using it, even with
ZFS, very successfully.
Diffstat (limited to 'sys/fs/tmpfs')
| -rw-r--r-- | sys/fs/tmpfs/tmpfs_vfsops.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/sys/fs/tmpfs/tmpfs_vfsops.c b/sys/fs/tmpfs/tmpfs_vfsops.c index 9d23bd2..74aeba1 100644 --- a/sys/fs/tmpfs/tmpfs_vfsops.c +++ b/sys/fs/tmpfs/tmpfs_vfsops.c @@ -156,9 +156,6 @@ tmpfs_mount(struct mount *mp) return EOPNOTSUPP; } - printf("WARNING: TMPFS is considered to be a highly experimental " - "feature in FreeBSD.\n"); - vn_lock(mp->mnt_vnodecovered, LK_SHARED | LK_RETRY); error = VOP_GETATTR(mp->mnt_vnodecovered, &va, mp->mnt_cred); VOP_UNLOCK(mp->mnt_vnodecovered, 0); |
