Re: [JOS-Kernel] Device as a digital resource

[Gilbert Carl Herschberger II]

At 07:32 PM 3/21/00 +0200, Al <[EMAIL PROTECTED]> wrote:
>device:zipdrive:scsi://localhost/bus/scsi/6/attached
>
>and
>
>device:zipdrive:scsi//localhost/bus/scsi/6/attached/disk
>
>
>The first URI points to the Zip drive itself, the second to the disk
>*inside* the Zip drive.

Oh, I see where you might be going. You're looking for something like the
/dev subdirectory on Linux/UNIX. Would you like every device to have a node
in the file subsystem?

If so, the file: and in: schemes returns an instance of InputStream. The
out: scheme returns an instance of OutputStream. Today, all these URIs work
on virtual machines for Linux.

To open a floppy disk device:

file://localhost/dev/fd0
in:file:/dev/fd0
out:file:/dev/fd0

To open a hard drive device:

file://localhost/dev/hd0
in:file:/dev/hd0
out:file:/dev/hd0

To open a tty: device:

file://localhost/dev/tty0
in:file:/dev/tty0
out:file:/dev/tty0

The file: scheme is a major scheme. Experience has shown that host and port
should have been an optional part of the file: scheme. Both host and port
are optional for the in: and out: schemes. For example, use these URI to
open a file in the current directory:

in:file:example.txt -> java.lang.InputStream
out:file:example.txt -> java.lang.OutputStream


_______________________________________________
Kernel maillist  -  [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel