Sheldon Hearn <[EMAIL PROTECTED]> writes:
> On Wed, 01 Aug 2001 09:39:58 MST, Dima Dorfman wrote:
> > How about fixing mdmfs to be bug-compatible (eew, Microsoft term) with
> > mount_mfs if it's called as "mount_*" (e.g., argv[0] is "mount_"), and
> > be sane otherwise?  I'll do this if people think that'd be okay.
> People already have to learn a new name.  They may as well learn the
> name of one that has sensible defaults.

They don't have to learn a new name:

        cd /sbin && ln -s mdmfs mount_mfs && shutdown -r now

the existing fstab entries should work.  Well, they should, but don't,
since mdmfs doesn't do some of the stupid and undocumented things that
mount_mfs used to.  This is what I'd like to fix (but optionally, so
mdmfs can be used for other things, like implementing the rc.conf
knob, too).

> I'm in favour of the current behaviour but I _still_ think you should
> commit my patches that add a "mount /tmp in mfs" option to rc.conf.

I don't know where you got the idea that I thought your rc.conf knob
was a bad idea.  Actually, before I imported mdmfs, dougb@ said he was
going to do something similar (if not just change your patch to use
mdmfs), but he appears to have disappeared (probably busy with
$real_life stuff).

Below is the etc/rc part of your patch converted to use mdmfs.  I'd be
glad to see that (and the other parts) applied, but I can't speak for
others (although nobody objected that I know of).

WARNING: whitespace/tab corruption
WARNING: untested

Index: etc/rc
RCS file: /home/ncvs/src/etc/rc,v
retrieving revision 1.250
diff -u -d -r1.250 rc
--- etc/rc      2001/01/21 20:57:13     1.250
+++ etc/rc      2001/01/29 16:17:47
@@ -196,6 +196,23 @@

+case ${swap_backed_tmp_size} in
+[Nn][Oo] | '')
+       ;;
+       echo 'Mounting swap-backed /tmp'
+       mdmfs -s ${swap_backed_tmp_size} -p ${swap_backed_tmp_perm} md /tmp
+       ;;
 umount -a >/dev/null 2>&1

 # Mount everything except nfs filesystems.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to