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

On Thu, Jun 23, 2005 at 12:20:00PM +0900, YAMAMOTO Takashi wrote:
> > Implement expansion of special "magic" strings in symlinks into
> > system-specific values.  Submitted by Chris Demetriou in Nov 1995 (!)
> > in PR kern/1781, modified only slighly by me.
> >=20
> > This is enabled on a per-mount basis with the MNT_MAGICLINKS mount
> > flag.  It can be enabled at mountroot() time by building the kernel
> > with the ROOTFS_MAGICLINKS option.
> >=20
> > The following magic strings are supported by the implementation:
> >=20
> > 	@machine	value of MACHINE for the system
> > 	@machine_arch	value of MACHINE_ARCH for the system
> > 	@hostname	the system host name, as set with sethostname()
> > 	@domainname	the system domain name, as set with setdomainname()
> > 	@kernel_ident	the kernel config file name
> > 	@osrelease	the releaes number of the OS
> > 	@ostype		the name of the OS (always "NetBSD" for NetBSD)
>=20
> is there any os which uses the compatible semantics with this?
> why don't you follow the existing conventions like tru64 cdsl or
> dragonfly varsym?

I think Plan 9 has equivalent functionality, too.

	-is

--9jxsPFA5p3P2qPhR
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQEVAgUBQrqcAzCn4om+4LhpAQFPswgApDR8OeOacVy27eo6BXKUFbYm8BKEJNj1
9Xt54obI/3wd6uRAAs6ouBA9LWpEgkmoCu3ADfJHOFQbVnAg/PfmjW3apG3IsrD6
RPvNiz5isDXhlFowy0bML0MF2rt+NtH/bY7i3dAAIDYxxnBwY/MkFdNZgbPlq7Jp
qGgtrQXDbji18qSlVRb9hl6Hd7P9vnB6pqdH91HArs91c9UgpbxeFm3ntFj5ROlF
vqFRrJqi/jLi2jmLMdnwdeHnqwZxZRSLhEKjmWyvTDFbJcYeKoaydvoo0wVnahVb
8yl0hPDjppbJ0PKWMOLXih8EvEUgFRueD2naJxQZ3kTfCUa+dL9ihw==
=E3cR
-----END PGP SIGNATURE-----

--9jxsPFA5p3P2qPhR--