In message <[EMAIL PROTECTED]>, David Gilbert writes:
>But filesystems also have persistence. In the trivial case, the
>persistence of the object (say ... a disk) preserved the filesystems
>node. But if I walk into /dev and change the permissions on a node,
>this persists only until the next reb
On Thu, 9 Oct 2003, David Gilbert wrote:
DG>> "Daniel" == Daniel O'Connor <[EMAIL PROTECTED]> writes:
DG>
DG>Daniel> The only reason most people will ever touch /dev is to either
DG>Daniel> make devices (hence no longer necessary with devfs), or change
DG>Daniel> permissions. The later is more
> "Daniel" == Daniel O'Connor <[EMAIL PROTECTED]> writes:
Daniel> The only reason most people will ever touch /dev is to either
Daniel> make devices (hence no longer necessary with devfs), or change
Daniel> permissions. The later is more difficult with devfs, but IMHO
Daniel> the tradeoff is w
>> I read that too. That appears to be just about all the information about
>> the new devfs that there is,
>> short of reading the source code.
You shouldn't need to do that. You can, more or less entirely forget
about DEVFS unless you are a device driver writer.
If you needed to run mknod(8)
Hiya
> I read that too. That appears to be just about all the information about
> the new devfs that there is,
> short of reading the source code.
If you look in /usr/share/doc (or someplace like that) there's a document
describing the rationale behind devfs and its implementation - it's geared
Derek Ragona wrote:
If you read the early adopters doc at:
http://www.freebsd.org/releases/5.1R/early-adopter.html
You will se it clearly says:
"MAKEDEV is no longer available, nor is it required. FreeBSD 5.X uses a
device filesystem, which automatically creates device nodes on demand. For
mor
If you read the early adopters doc at:
http://www.freebsd.org/releases/5.1R/early-adopter.html
You will se it clearly says:
"MAKEDEV is no longer available, nor is it required. FreeBSD 5.X uses a
device filesystem, which automatically creates device nodes on demand. For
more information, please
On Wed, 8 Oct 2003, ecsd wrote:
e>Given that FreeBSD 5.1 is on the shelf in a box at CompUSA for sale to the
e>general public, I think the proper thing to do is address the matter of
e>documenting the revised operation of the devices in 5.X, rather than tell
e>people to downgrade if they don't und
Given that FreeBSD 5.1 is on the shelf in a box at CompUSA for sale to the
general public, I think the proper thing to do is address the matter of
documenting the revised operation of the devices in 5.X, rather than tell
people to downgrade if they don't understand the behavior of their system,
bes
On Tuesday 07 October 2003 18:01, ecsd wrote:
> I have a WintTV card that should be /dev/bktr0. I have tried using "devfs"
> to remedy this:
>
> host[157] # fxtv
> open("/dev/bktr0") failed: No such file or directory
>
> but I cannot see what to do, precisely and in order, to make the device
> exis
In message <[EMAIL PROTECTED]>, ecsd writes:
>MAKEDEV was the cheese since year zero. [...]
I suggest you stick with 4-stable until you have caught up with
the changes and the documentation.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
Poul-Henning Kamp writes:
In message <[EMAIL PROTECTED]>, ecsd writes:
with MAKEDEV gone, the mystery is how to use devfs.
In /dev I have ad3, but I cannot "disklabel -e /dev/ad3s1d",
nor can I "disklabel -e /dev/ad3", and I can't determine
what minor device numbers to assign for mknod to create
th
In message <[EMAIL PROTECTED]>, ecsd writes:
>with MAKEDEV gone, the mystery is how to use devfs.
>In /dev I have ad3, but I cannot "disklabel -e /dev/ad3s1d",
>nor can I "disklabel -e /dev/ad3", and I can't determine
>what minor device numbers to assign for mknod to create
>the partition entries.
13 matches
Mail list logo
