I've assembled some notes from old manuals and other sources
on the formats used for on-disk file systems through the
Additional notes, comments on style, and whatnot are welcome.
(It may be sensible to send anything in the last two categories
directly to me, rather than to the whole list.)
Ronald Natalie <ron(a)ronnatalie.com> wrote:
> I suspect strcpy arrived with the "portable I/O library", an abomination
> that eventually evolved into the stdio library and to this day is still
> stinking up the standard C language.
What's so bad about stdio? That's a genuine question - I've never had
a reason to dislike stdio...
Hi. I have two QIC 6250 tape cartridges that have been in (I hope) dry
boxes for over 15 years. I suspect they're still usable but have no
equipment with which to test them or try to read them.
It'd be nice to get a CD back with copies of what's on them if that's
possible, but that'd be icing on the cake.
Drop me a note and we'll see if we can figure something out for mailing
On another list I am on, a discussion about the history and purpose of
strncpy has arisen. The only reference I have found to it is <
The original reason for strncpy() was when directory names were limited to
14 chars. The other two bytes contained the inode number. For that
particular case, strncpy() worked quite well.
Is that really the reason it came into being?
Just a bit curious,
Nevin ":-)" Liber <mailto:email@example.com> (847) 691-1404
Arnold Robbins has donated a couple of OpenLook CDs to the Unix
Archive. I've put them into Applications/OpenLook.
Here is his note:
I have a CD from ian(a)darwinsys.com dated 9/2005 with
OpenLook-XView-1.0e on it, and what looks like another one with
the same date with version 1.2. I'm still extracting the first
one onto disk; it's in the 550+ Megabyte range. Files are dated 1995.
Right now it's only on minnie until the mirrors pick it up:
Cheers & thanks Arnold & Ian,