Here is a simplified 'more' command for Unix V7:
/*********************************************************************
* UNIX pager (v7 compatible) Chipmaster and KenUnix
*
* cc -o more more.c
*
* Usage examples:
* man wall | more
* more xyz
* more abc def xyz
*
* Started February 15th, 2023 YeOlPiShack.net
*
* This is the ultimately dumbest version of more I have experienced.
* Its main purpose is to illustrate the use of /dev/tty to interact
* with the user while in a filter role (stdin -> stdout). This also
* leaves stderr clear for actual errors.
*
*
* NOTES on Antiquity:
*
* - The early C syntax didn't allow for combining type information
* in the parenthesized argument list only the names were listed.
* Then a "variable" list followed the () and preceded the { that
* declared the types for the argument list.
*
* - There is no "void", specifically there is no distinction
* between a function that returns an int or nothing at all.
*
* - Many of the modern day header files aren't there.
*
* - Apparently "/dev/tty" couldn't be opened for both reading and
* writing on the same FD... at least not in our VM.
*
* - Apparently \a wasn't defined yet either. So I use the raw code
* \007.
*
* - Modern compilers gripe if you do an assignment and comparison in
* the same statement without enclosing the assignment in (). The
* original compilers did not. So if it looks like there are too
* many ()s it's to appease the modern compiler gods.
*
* - I'm not sure where they hid errno if there was one. I'd think
* there had to be. Maybe Kernighan or Pike knows...
*
*********************************************************************/
#include <stdio.h>
/*** Let's make some assumptions about our terminal columns and lines. ***/
#define T_COLS 80
#define T_LINES 24
/*** Let's set up our global working environment ***/
FILE *cin; /* TTY (in) */
FILE *cout; /* | (out) */
int ct = 0;
/*** message to stderr and exit with failure code ***/
err(msg)
char *msg;
{
fputs(msg, stderr);
exit(1);
}
/*** A poor man's CLear Screen ***
*
* Yup! This is how they used to do it, so says THE Kenrighan & Pike!
* termcap?!?! What's that?
*/
cls()
{
int x;
for(x=0; x<T_LINES; ++x) fputc('\n', cout);
ct = 0; /* reset global line count */
}
/*** The PAUSE prompt & wait ***/
pause()
{
char in[T_COLS+1]; /* TTY input buffer */
fflush(stdout); /*JIC*/
fputs("--- [ENTER] to continue --- Ctrl-d exits ", cout);
fflush(cout);
if(!fgets(in, 81, cin)) {
/* ^D / EOF */
fputc('\n', cout); /* cleaner terminal */
exit(0);
}
}
/*** Read and page a "file" ***/
int pg(f)
FILE *f;
{
char buf[T_COLS+1]; /* input line: usual term width + \0 */
/*** read and page stdin ***/
while(fgets(buf, sizeof(buf), f)) {
/* page break at T_LINES */
if(++ct==T_LINES) {
pause();
ct = 1;
}
fputs(buf, stdout);
}
return 0;
}
/*** Let's do some paging!! ***/
int main(argc, argv)
int argc;
char *argv[];
{
FILE *in;
int x, er;
/*** Grab a direct line to the TTY ***/
if(!(cin=fopen("/dev/tty", "r")) || !(cout=fopen("/dev/tty", "w")))
err("\007Couldn't get controlling TTY\n");
/*** with CLI args ***/
if(argc>1) {
er = 0;
for(x=1; x<argc; ++x) {
if(argc>2) {
if(!er) cls();
er = 0;
/* remember all user interaction is on /dev/tty (cin/cout) */
fprintf(cout, ">>> %s <<<\n", argv[x]);
pause();
}
/* - is tradition for stdin */
if(strcmp("-", argv[x])==0) {
pg(stdin);
/* it must be a file! */
} else if((in=fopen(argv[x], "r"))) {
pg(in);
fclose(in);
} else {
/* errors go on stderr... JIC someone want to log */
fprintf(stderr, "Could not open '%s'!\n", argv[x]);
fflush(stderr);
er = 1; /* this prevents cls() above. */
}
}
/*** no args - read and page stdin ***/
} else {
pg(stdin);
}
return 0;
}
End...
--
WWL 📚
In 'more.c' there is a typo
Line 154
replace
fprnntf(stderr, "Could not open '%s'!\n", argv[x]);
with
fprintf(stderr, "Could not open '%s'!\n", argv[x]);
--
WWL 📚
All,
If you think unix ends without x, just move along, nothing to see here.
Otherwise, I thought I would share the subject of my latest post and a
link with those of you interested in such things.
Recently, I've been tooling around trying to wrap my head around x
windows and wanted to give programming it a shot at the xlib level... on
my mac, if possible. So, I bought a copy of Adrian Nye's Xlib
Programming Manual for Version 11 R4/R5, aka Volume One of The
Definitive Guides to the X Window System, published, get this... 30+
years ago, in 1992 :) and started reading like a madman. As usual, this
was an example of great technical writing from the prior millenium,
something rarely found today.
Anyway, I hunted up the source code examples as published, unpacked
them, did a few environmental things to my mac, and built my first xlib
application from that source. A few tweaks to my XQuartz configuration
and I was running the application in twm on my mac, with a root window.
To read about it and see it in all of its glory, check it out here:
https://decuser.github.io/operating-systems/mojave/x-windows/2023/01/24/x-w…
The same sort of setup works with Linux, FreeBSD, or my latest
environment DragonFly BSD. It's not the environment that I find
interesting, but rather the X Window System itself, but this is my way
of entering into that world. If you are interested in running X Windows,
not as an integrated system on your mac (where x apps run in aqua
windows), but with a 'regular' window manager, and you haven't figured
out how, this is one way.
On the provocateur front - is X part of unix? I mean this in oh so many
nuanced ways, so read into it as you will. I would contend, torpedoes be
damned, that it is :).
Will
Sandy wrote the original CDL tool set. It had a graphical front end that provided for chips , pins,
wires etc and generated a connectivity list which was then consumed by wire wrap and other back end
tools. We had Tek 4014 terminals at the time (late 70s is what I recall) which made all this
reasonable.
I took it over the code base at some point and among other things added macros so that repeated wire
to chip connection patterns and names could be generated without the labor intensive one wire at a
time e.g. wire[0-7] connects to pin[0-7]. The macro would be expanded so that wire0 connected to
pin0 etc. This later system was call UCDS - Unix Circuit Design System.
UCDS was used by Joe Condon for the chess machine that he and Ken built. Ken may remember more
about this. It was also one of the reasons that BTL got a $1B Navy contract.
Steve
Good day everyone, I'm emailing to start a thread on part of my larger UNIX/TS 4.x project that is coming to a conclusion. Lots of info here, so pardon the lack of brevity.
Over the course of the past month or so I've been diffing all of the manual pages between System III and System V to produce a content-accurate set of typesetter sources for the UNIX Release 4.1 (3B20S) manual I found a while back. I've completed my shallow pass of everything (all pages accounted for, generally complete, except the permuted index) and am now about halfway through my second pass (detailed, three-way diffs, documenting changes) and thought I'd share a few findings to kick off what will likely be more exposition of the 3.x->4.x->5.x->SysV time-period vis-a-vis available documentation. Most analysis here will center specifically around the contents of the 4.1 3B20S manual and later Documents For UNIX 4.0 as those are the only documents I've found for 4.x. I mention that as there are whole subsystems excluded from this manual that show back up in my 5.0 manual, so I suspect they were pieces that weren't ready for 3B-20 at the time but were in other installations. Fortran, SNOBOL, Honeywell 6000 communication, and the old lpr print system are absent, for instance. Anywho, as I wrap up what I can prove, then I'll probably swoop through and compare these SysIII to SysV to at least document what may have happened in that timeframe, if anything. If I'm lucky there are no visible changes in the man pages meaning they were nominally identical between the various versions. We'll see.
Also a disclaimer, this is entirely documentation based. I have not yet cross-referenced changes I see in manuals with changes observed between code revisions. A later phase of my project will be doing this sort of analysis to try and reconstruct some idea of what code changes were 3-to-4 and which ones were 4-to-5, but that's quite a ways away. All that to say, a manual page could entirely be updated much later than a change it describes, so if something in code contradicts anything in the manuals, the code is obviously what the system was actually doing at the time. The manual is just how well someone bothered to document it.
The sections I've finished thus far are 2 - System Calls, 5 - Miscellaneous Facilities, and 6 - Games, and the frontmatter/intro section. Here's a bit of digest on what I've gone over with a fine toothed comb thus far:
3.x->4.x:
---------
There is a general trend towards platform-independence that already started with merging of PDP-11 and VAX support into a single-ish codebase ala 3.x. This trend continues with indicating that machine discrepancies (and obsolescence) will be noted in the mast head of pertinent manual entries. References to adb are dropped from this intro section. Additionally, a new section numbering is applied to the User's and Administrator's Manuals (which are split by the way). This starts the numbering/split scheme we continue to see in 5.0 and SysV a year or so later, where sections 4, 5, and 7 are shuffled to stick device files in section 7 and in turn split off 1M, 7, and 8 into a separate Administrator's Manual (a_man vs u_man). Unfortunately, since this split did occur at 4.x, I don't have the 1M, 7, and 8 sections to compare with, the copy of the manual I nabbed was just the User's Manual. If someone has a UNIX Administrator's Manual Release 4.x that they'd be willing to offer up for scanning/analysis, that would definitely help complete the circle.
Other frontmatter changes imply a move more towards commercialize-able literature. The Editors are commented out as indicated by the SysV manual sources later on. Unfortunately this means my goal of documenting authorship remains unattainable at present, but in any case, somewhere along the way the responsibility was shifted from Lab 364 (3.x) to Lab 4542 (5.x). An acknowledgement from the Lab 364 folks in the 3.x manual is dropped entirely, not even commented out. This acknowledgement thanks the efforts of those who assembled the V6, V7, PWB/2.0, and UNIX/TS 1.1 manuals (what I wouldn't give for the latter two...). Another change regarding commercialized literature is the reference to UNIX for Beginners in the intro section is replaced with a reference the "UNIX User's Guide". This manual does show up by SysV, but I don't know if this implies they were running those sets this way by the time of 4.1. Arnold Robbins provided Documents for UNIX 4.0 last year which is very much still the old /usr/doc *roff documents, so either they were pre-empting the material they would start to produce with 5.x, or there is yet another set of potential 4.x documents floating around out there.
In any case, there are a handful of changes to 2 - system calls:
- intro reflects that error.h has been renamed to errno.h
- The "SysV" IPC shows up here in 4.1. I forget who mentioned it but someone has mentioned in the past 4.0 and 4.1 had different IPC systems, so this isn't that illuminating unfortunately.
- A minimum of 1 character for filenames is noted. I suppose around this time someone won the "well it doesn't *say* you can't have a zero character file name" pedantic argument.
- Various areas where groups are referred to, text is updated to ensure it is understood the author means "effective" group
- brk, exec, exit, and fork pages all now have verbiage concerning how they interact with IPC
- brk clarifies that added space is initialized to zero
- exec adds verbiage about argc, argv, envp, and environ, and notes that ENOEXEC doesn't apply to execlp and execvp
- fork adds a thorough description of which attributes of the parent process are passed down
- kill elaborates that real or effective user (and group) can influence permissions
- ptrace updates adb references to sdb and adds 3B-20 verbiage
- setuid consolidates explanations of setuid and setgid, no noticed change to functionality
- signal now defers to exit(2) to describe termination actions and changes header references from signal.h to sys/signal.h
- sys3b is added for 3B-20-specific system calls
- utsname gains the machine field (for -m)
- wait now stashes the signal number causing a return in the upper byte of the status word
And then under 5 - misc:
- Many pages used a .so directive to directly populate a given header. By SysV this has been changed to include the text in the pages directly. Unsure exactly what 4.x did but I went with the latter
- eqnchar loses the scrL, less-than-or-equal-to, and greater-than-or-equal-to character replacements
- ldfcn is added, this is the general description page for what will become the COFF library, at this stage it is very 3B-20 oriented in description
- man adds the \*(Tm trademark indicator
- mosd and mptx macro pages are added
- mv's macro page is pretty much rewritten to include the actual macros, the version in 3.x simply referred to there being macros and a manual coming soon
- types in 3.0 has variable sizes for cnt_t and label_t depending on VAX or not. 4.x seems to remove this discrepancy and always present the VAX sizes
And finally under 6 - games:
- A note about using cron to restrict access has been removed, unknown if this is a stylistic choice or because cron is a 1M and therefore no longer in this manual
- chess and sky both have their FILES sections removed
- jotto is added
- ttt gains a note that the cubic variant does not work on VAX
- wump is no longer PDP-11 only as of 4.1
Other stuff not fully digested yet:
- It appears what would become COFF (Common Object File Format) had its beginnings as the 3B-20 object file format for UNIX/TS 4.x. The 3B-20 object-related stuff becomes the more general versions in 5.x.
- The LP print service has its start in 4.x.
- SysV IPC appears to be largely there by 4.1, with only icprm missing as far as I could tell.
- 4.x introduces the termio system.
- 4.1 may signal the start of distributing guidance material as "Guides" rather than "Documents For UNIX". There are a number of tech report citations that have been updated to reflect this.
4.x->5.x:
---------
As for the 4.x->5.x for these same items (I'll mention 4.x->5.x and 5.x->SysV both):
- Sys V adds a notice that the manual describes features of the 3B20S which is not out. No such notice is in the 5.0 manuals, so this was specifically for outside consumption
- The BTL version of the 5.0 manual features the return of the acknowledgements page as well as a preface describing the manual and DIV 452's involvement. If there was a BTL version of 4.x manuals, I suspect they may have also included this as it was in the 3.0 manual.
- Sys V begins the "The UNIX System" nomenclature in earnest.
- Otherwise the frontmatter seems pretty much unchanged from 4.x to 5.x, the only discrepancies arise in the BTL and SysV variants
In 2 - system calls:
- adds a few required headers
- shmop appears to have changed headers slightly, requiring ipc.h and shm.h instead of shmem.h
- signal states that apparently SIGCLD is now reset when caught
- sys3b adds syscalls 3, 9, and 10, for attaching to an address translation buffer, changing the default field test set utility-id, and changing FPU flag bits respectively
- times switches to the tms struct from the tbuffer struct. Same fields but slight change in names. Times also notes that times are given in 1/100th of a second for WECo processors (1/60th for DEC).
In 5 - misc:
- ldfcn is moved to section 4 and drops 3B-20 specificity, signaling the start of COFF in earnest
- term adds names for TELETYPE 40/4 and 4540 as well as IBM Model 3270 terminals
- types adds the uint (unsigned int) and key_t (long) types
And there are actually no noteworthy changes to section 6.
So general takeaways thus far on the 4->5 transition:
- COFF becomes formalized here rather than being the 3B-20 format that might get extended to things
- "The UNIX System" nomenclature begins with System V
- 3B20S starts showing up in external literature but isn't openly available yet
- 3B-20 support is still growing and being used as a model for "generic" components, especially COFF and SGS
- CB-UNIX init is moved over starting with 5.0
---------
There'll definitely be more to come as I do my second pass of sections 1, 3, and 4. As things begin to wrap up I also intend to upload the manual restoration somewhere, probably archive.org. I still intend to scan the physical copy sometime later this year, but this'll get info out so people can research things, and of course if any discrepancy ever arises I'll happily pull the original manual page and scan it as proof of anything odd.
My biggest takeaway from what I've covered thus far is this clarifies the history of COFF a bit. Wikipedia states that COFF was a System V innovation, which commercially, it very well was. However, this documentation demonstrates that it began life likely as a 3B-20-specific format that was then applicable to others. This now places, COFF, LP, *and* IPC all as things credited to System V that really started with at most UNIX/TS 4.1.
The more I look at things, the more 5.0 appears to actually be a minor release compared to what all was going on in the 4.x era. From 4.1 to 5.0 the largest changes I see thus far are the addition of CB-UNIX init, generalization of COFF from a 3B-20 object format, and otherwise just clerical, marketing, and accuracy improvements to the literature. This statement will be qualified much better as I turn over more ground on this, but that's the general gist I've been gathering as I go through this: 3.x->4.x saw the introduction of a great number of soon-to-be-ubiquitous parts of UNIX and then 4.x->5.x and on to System V saw those components being tuned and the release being shepherded along into a viable commercial solution.
As with anything, this is of course, all based on analysis of documents, so if there are any inaccuracies in anything, I apologize and welcome corrections/clarifications. Hopefully by the end of all of this there'll be enough content to draft up a proper Wikipedia article on the "System IV" that never was and correct what truly was a System V innovation vs what just finally popped out of USL with that version. If you made it all the way here, thanks for reading!
- Matt G.
The subject of Communication Files on DTSS came up recently, and Doug
linked to this wonderful note:
https://www.cs.dartmouth.edu/~doug/DTSS/commfiles.pdf
Over on the Multicians list, I raised a question about the history of the
DTSS emulator on Multics in response to that, which sadly broke down into
antagonism, the details of which aren't terribly interesting. But Barry
Margolin suggested that the closest modern Unix analogue of Communication
Files were pseudo-TTYs, that had generated a dustup here. Doug's note
suggests that Plan 9's userspace filesystems, aided and abetted by mutable
namespaces and 9P as a common sharing mechanism, were a closer analogy.
But I wonder if multiplexed files were perhaps an earlier analogue; my
cursory examination of mpx(2) shows some similarities to the description of
the DTSS mechanism.
But I confess that I know very little about these, other than that they
seem to be an evolutionary dead end (they don't survive in any modern Unix
that I'm aware of, at any rate). I don't see much about them in my
archives; Paul Ruizendaal mentioned them tangentially in 2020 in relation
to non-blocking IO: they are, apparently, due to Chessen?
Does anyone have the story here?
- Dan C.
Hi all,
Today, as I was tooling around on stack overflow, I decided to ask a
question on meta. For those of you who don't know, stack overflow is
supposedly a q&a site. There are zillions of answers to quite a few "how
to do i do x" style questions. Folks upvote and downvote the answers and
the site is a goto for a lot of developers. I've used it since it came
online - back in the late 2000's. I have a love hate relationship with
the site. When there's a good answer to a question that I have, I love
it. When they downvote fringe cases that I care about to the point where
they effectively become gray literature that is near on impossible to
locate - I hate it. Meta is supposedly where you go to ask questions
about the stack.
Yesterday, I asked this question:
Do you know of any studies that have been done around downvoted
content, specifically on stack overflow or stack exchange?
By way of background - I find any questions or answers that are on
the border (+1, 0, -1) as dubiously helpful, but when the downvotes
pile up, much like upvotes, the answers become interesting to me
again as they give me insights I might miss otherwise.
After a slew of why would you think that was interesting, there's no
value with upvotes and downvotes, and your question is unclear responses
along with, as of now, 31 downvotes net, the question was closed for
lack of clarity. My answer, which was informed by some of the comments was:
There don't appear to be any papers on downvoting specific to Stack
Overflow. You can find a good list of known academic papers using
Stack Exchange data in the list hosted on Stack Exchange Meta
(link). It is an attempt to keep a current list of works up to date.
The Stack Exchange Data Explorer (link) is an open API for doing
data research, if you want to dig into the data yourself.
Which was quickly downvoted 9 times net.
To see the entire debacle:
https://meta.stackoverflow.com/questions/423080/are-there-any-serious-studi…
Anyhow, other than what I perceive to be a decidely hostile environment
for asking questions, it is still actually a useful resource.
Wow, have times changed though on the hostility front.
So, it got me thinking...
What was it like in the very beginning of things (well, ok, maybe not
the very beginning, but around and after the advent of v6 and when it
was at or around 50 sites) for folks needing answers to questions
related to unix?
The questions... and for the love of Pete, don't downvote me anymore
today, I'm a fragile snowflake, and I might just cry...
What was the mechanism - phone, email, dropbox of questions, snail mail,
saint bernardnet, what?
What was the mood - did folks quickly tire of answering questions and
get snippy, or was it all roses?
When did those individual inquiries get too much and what change was
made to aggregate things?
I'm thinking there may have been overlap between unix users and
usenet... Also, I remember using fidonet for some of my early question
about linux, but that was 1991, many years after the rise of unix.
Thanks,
Will
