From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan9port venti FreeBSD
Date: Sat, 31 Dec 2005 10:36:41 +0000 [thread overview]
Message-ID: <392010f8703d4ce0b6fdf23283fa296b@vitanuova.com> (raw)
In-Reply-To: <E1EsYGB-0001AI-E9@quenix1.dyndns.org>
>>It seems that the major device number have change from FreeBSD 4.X to
i wonder how many years it will be before the unix clones undo that
aspect of the original design that could do with a change?
you might have thought that devfs would fix it, but no,
and furthermore, there's still mknod, `to recover deleted device entries'.
next prev parent reply other threads:[~2005-12-31 10:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 4:07 Serge Gagnon
2005-12-21 4:43 ` Russ Cox
2005-12-21 4:44 ` Russ Cox
2005-12-27 19:41 ` Serge Gagnon
2005-12-30 19:40 ` Russ Cox
2005-12-31 4:22 ` Serge Gagnon
2005-12-31 10:36 ` C H Forsyth [this message]
2005-12-31 13:50 ` Russ Cox
[not found] <200512210421.jBL4LmZv058701@gate.bitblocks.com>
2005-12-22 18:22 ` Serge Gagnon
2005-12-22 19:04 ` Russ Cox
2005-12-22 20:06 ` Serge Gagnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=392010f8703d4ce0b6fdf23283fa296b@vitanuova.com \
--to=forsyth@vitanuova.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).