On Tue, 25 Mar 2003, Steve Kargl wrote:

SK>On Tue, Mar 25, 2003 at 10:11:00AM +0100, Christian Brueffer wrote:
SK>> On Mon, Mar 24, 2003 at 09:43:17PM +0200, Giorgos Keramidas wrote:
SK>> > On 2003-03-24 19:14, Christian Brueffer <[EMAIL PROTECTED]> wrote:
SK>> > > I'll write a small manpage this evening which says that MAKEDEV is
SK>> > > gone now with a short summary of what devfs does.  Does that resolve
SK>> > > your worries?
SK>> >
SK>> > If you write a detailed description of devfs please add it to devfs(5)
SK>> > and just replace the existing manpage of MAKEDEV with something like:
SK>> >
SK>> >  The MAKEDEV script was deprecated by devfs(5) and geom(4) and
SK>> >  removed from FreeBSD after GEOM became mandatory.  Please see
SK>> >  the devfs(5), devfs(8), geom(4) and mount_devfs(8) manpages for
SK>> >  more details.
SK>> >
SK>> > This should be enough IMHO to point the reader to the right place.
SK>> >
SK>> > - Giorgos
SK>> >
SK>>
SK>> That was my original intent.  I'm still uncertain if it would be better
SK>> to write a small manpage or just create a MLINK to one of the devfs
SK>> pages...
SK>>
SK>
SK>Are you going to write a man page everytime a feature
SK>is deprecated?  MAKEDEV is dead and gone.  At most
SK>create the MLINK.

MAKEDEV has been in unix since at least version 7. That's about 30 years.
If you deprecate a feature, that has been on virtually all unices for 30
years, it makes sense.

Each time I type 'man vnconfig' (I don't use mdconfig often enough to
remember which is actual and which of it is not there anymore) I'm puzzled
that the mdconfig man page pops up. In that case it is easy to understand,
that the functionality is almost the same. If I type 'man MAKEDEV' and
devfs pops up, I have to think much more to find out, that these are
somehow related.

harti
-- 
harti brandt,
http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private
[EMAIL PROTECTED], [EMAIL PROTECTED]

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

Reply via email to