Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Apr 2004 14:02:00 -0700
From:      Brooks Davis <brooks@one-eyed-alien.net>
To:        Randy Bush <randy@psg.com>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: very current won't mount /tmp
Message-ID:  <20040412210200.GB5340@Odin.AC.HMC.Edu>
In-Reply-To: <16505.6623.99276.241321@roam.psg.com>
References:  <16505.6623.99276.241321@roam.psg.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--DBIVS5p969aUjpLe
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Apr 11, 2004 at 07:11:43PM +0900, Randy Bush wrote:
> very current (08:00gmt the 11th)
> thinkpad t40p
>=20
> make world and kernel
> boot single abuser to do the installworld
>=20
> can mount drives one at a time until i get to /tmp which is
> defined as
>=20
>     md /tmp mfs -s131072,rw,nosuid,nodev,noatime 0 0
>=20
> locks up
>=20
> as installworld has not happened, it should not be the new
> automagic /tmp mfs.  or am i misunderstanding that?

The new auto /tmp creation code should only kick in after you run
mergemaster.  Even then, it shouldn't have any effect in single user
mode because it hasn't been run yet at that point.  If you're being really
paranoid, you simply verifying that nothing is mounted on /tmp before
trying to mount it yourself should eliminate that from the equation.

-- Brooks

--=20
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4

--DBIVS5p969aUjpLe
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAewPHXY6L6fI4GtQRAsYfAKDQth7vVG1vSqxn9mZLeKTAa7IhkQCgz1Lu
vW2ap6g/wmGn4RjRV6+CwGw=
=nCAp
-----END PGP SIGNATURE-----

--DBIVS5p969aUjpLe--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040412210200.GB5340>