From: KenUnix <ken.unix.guy@gmail.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780
Date: Wed, 15 Mar 2023 07:09:45 -0400 [thread overview]
Message-ID: <CAJXSPs_PTBq7+ciEk4oNbYMQwo+tZK39LhW=J2P_bN9L1AbV2Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2303151948590.67613@aneurin.horsfall.org>
[-- Attachment #1: Type: text/plain, Size: 2050 bytes --]
In: /usr/src/uts/vax/cf
This is what is in conf.c:
struct cdevsw cdevsw[] = {
/* 0*/ conopen, conclose, conread, conwrite,
conioctl, 0,
/* 1*/ dzopen, dzclose, dzread, dzwrite, dzioctl,
dz_tty,
/* 2*/ syopen, nulldev, syread, sywrite, syioctl, 0,
/* 3*/ nulldev, nulldev, mmread, mmwrite, nodev, 0,
/* 4*/ gdopen, gdclose, gdread, gdwrite, nodev, 0,
/* 5*/ htopen, htclose, htread, htwrite, nodev, 0,
/* 6*/ nodev, nodev, nodev, nodev, nodev, 0,
/* 7*/ nodev, nodev, nodev, nodev, nodev, 0,
/* 8*/ erropen, errclose, errread, nodev, nodev, 0,
};
In "master" sample entries are:
ts11 4 36 115 ts 4 1 5 1 5
tu78 1 36 515 hu 0 1 5 4 5
rm05 1 76 515 hm 0 0 4 8 5
nsc 4 77 5 nsc 8 0 10 1 5
ndb ct
*lp11 4 73 5 lp 4 0 6 1 4*
dn11 4 32 6 dn 8 0 7 4 5
vp 4 33 5 vp 16 0 14 1 5
vp
dmc11 8 37 6 dmc 8 0 19 1 5
Those numbers do not mean much to me.
Does this help in determining major/minor number for lp?
Thanks
Ken
On Wed, Mar 15, 2023 at 4:53 AM Dave Horsfall <dave@horsfall.org> wrote:
> On Wed, 15 Mar 2023, arnold@skeeve.com wrote:
>
> [...]
>
> > That is, 'c' for character device, major device is the index in cdevsw,
> > and minor device indicates which physical one to use. Since you only
> > have one, it should be 0.
>
> There's also the possibility of using the upper-order bits to pass flags,
> although there's not a lot that you can do with a printer (control of page
> throw, etc).
>
> -- Dave
>
--
End of line
JOB TERMINATED
[-- Attachment #2: Type: text/html, Size: 3158 bytes --]
next prev parent reply other threads:[~2023-03-15 11:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 0:59 Noel Chiappa
2023-03-15 8:05 ` arnold
2023-03-15 8:52 ` Dave Horsfall
2023-03-15 11:09 ` KenUnix [this message]
2023-03-15 11:59 Noel Chiappa
2023-03-15 21:03 ` Warren Toomey via TUHS
2023-03-15 21:08 ` Clem Cole
2023-03-15 21:15 ` Luther Johnson
2023-03-15 21:18 ` Seth Morabito
2023-03-15 21:22 ` Larry McVoy
2023-03-15 21:27 ` Clem Cole
2023-03-15 21:38 ` KenUnix
2023-03-16 23:18 ` Clem Cole
2023-03-16 23:48 ` Charles H. Sauer (he/him)
2023-03-17 1:08 ` Steve Nickolas
2023-03-15 21:46 ` Steve Nickolas
2023-03-15 21:50 ` Luther Johnson
2023-03-15 21:56 ` steve jenkin
2023-03-15 22:15 ` Larry McVoy
2023-03-15 23:30 ` Warner Losh
2023-03-15 23:41 ` Luther Johnson
2023-03-16 0:29 ` Warner Losh
2023-03-16 0:36 ` Rich Salz
2023-03-16 1:55 ` G. Branden Robinson
2023-03-16 21:14 ` Dave Horsfall
2023-03-17 0:33 ` Rich Salz
2023-03-17 1:05 ` segaloco via TUHS
2023-03-17 2:03 ` G. Branden Robinson
2023-03-17 3:17 ` Dave Horsfall
2023-03-16 1:15 ` Larry McVoy
2023-03-16 2:14 ` Luther Johnson
2023-03-15 23:44 ` Brad Spencer
2023-03-16 4:37 ` Dave Horsfall
2023-03-15 22:25 Noel Chiappa
2023-03-15 22:39 ` segaloco via TUHS
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='CAJXSPs_PTBq7+ciEk4oNbYMQwo+tZK39LhW=J2P_bN9L1AbV2Q@mail.gmail.com' \
--to=ken.unix.guy@gmail.com \
--cc=dave@horsfall.org \
--cc=tuhs@tuhs.org \
/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).