tech-userlevel archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Shared-root diskless netboot, critical local/remote mounts, and rc.conf
> Magic symlinks can do this earlier and work automatically.
They do have a downside, though: they are system-wide. It is not
possible to turn on magiclinks for one link without turning it on for
the whole system. (At least not according to 9.1's symlink(7).)
For most systems, this is not much of a practical problem; few systems
have any desire for non-magic symlinks using the magiclinks syntaxes.
But I really think it should be done with some attribute of the symlink
itself. I'd repurpose the sticky bit for that; the write and set-ID
bits I can see plausible semantics for. (This could even be done
compatibly. vfs_magiclinks is an integer, but is used for only
zero-vs-nonzero and I'd be surprised if anyone sets it to other than 0
or 1; defining, say, 2 to mean "sticky bit controls link magicness"
could work.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mouse%rodents-montreal.org@localhost
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
- References:
- Shared-root diskless netboot, critical local/remote mounts, and rc.conf
- Re: Shared-root diskless netboot, critical local/remote mounts, and rc.conf
- Re: Shared-root diskless netboot, critical local/remote mounts, and rc.conf
- Re: Shared-root diskless netboot, critical local/remote mounts, and rc.conf
- Re: Shared-root diskless netboot, critical local/remote mounts, and rc.conf
- Re: Shared-root diskless netboot, critical local/remote mounts, and rc.conf
Home |
Main Index |
Thread Index |
Old Index