TUHS December 2003

tuhs@tuhs.org

20 participants
18 discussions

by norman＠nose.cita.utoronto.ca

I've assembled some notes from old manuals and other sources on the formats used for on-disk file systems through the Seventh Edition: http://www.cita.utoronto.ca/~norman/old-unix/old-fs.html 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.)

1 year

by Larry J. Blunk

Apologies if this has been answered before, but I noticed that there are AT&T copyright notices in the kernel sources for Unix Edition 5, but they were removed in Edition 6. You can still see the comment blocks for the notices in Edition 6, but the notices themselves have been removed. Does anyone have the history on this? I noticed that USL registered Editions 5, 6, 7 and 32V in 1992. I would assume that Editions 4 and earlier are free and clear because, prior to 1978, registration was a requirement for protection. Further, since USL waited longer than 5 years to register the copyrights for 5, 6, 7 and 32V, these may be free and clear as well. As I understand it, Editions 7 and 32V could have had copyright protection without registration since they were released after 1978. However, because they lacked copyright notices when released, they may very well be considered public domain. It was not until 1989 that the requirement for including copyright notices was dropped.

19 years, 5 months

by norman＠nose.cs.utoronto.ca

Larry J. Blunk: Apologies if this has been answered before, but I noticed that there are AT&T copyright notices in the kernel sources for Unix Edition 5, but they were removed in Edition 6. [...] I noticed that USL registered Editions 5, 6, 7 and 32V in 1992. I would assume that Editions 4 and earlier are free and clear [...] As I understand it, Editions 7 and 32V could have had copyright protection without registration since they were released after 1978. However, because they lacked copyright notices when released, they may very well be considered public domain. It was not until 1989 that the requirement for including copyright notices was dropped. ======== Notwithstanding other comments about the history, for practical purposes none of this matters for Seventh Edition and 32V and anything earlier, because Caldera (as it then was) open-licensed them in January 2002; see http://www.tuhs.org/Archive/Caldera-license.pdf. To be precise, that license covers 32-bit 32V UNIX 16 bit UNIX Versions 1, 2, 3, 4, 5, 6, 7 with specific exclusion of System III and System V and successors. That is why source code for the Seventh Edition system (for example) is openly accessibly on the TUHS web server. Among those whose dog work produced first a hobbyist-specific per-person license, then the current BSD-like license, was Warren Toomey, who manages that web server and this mailing list. I don't think it will give him a swollen head (or a wooden leg) to thank him now and then, and I do so here. Long-time readers know all that, but those who have joined us recently might not. Norman Wilson Toronto ON

19 years, 5 months

RE: Fw: RATE RQST FROM RIO JANERIO TO JEDDAH PORT

by zmkm zmkm

mamun tks for the prompt reply but we need the rate to malaysia not to jeddah and the rate must be break bulk because cntr will be very expensive. since each shipment is about 15 000 tons (fifteen thousand tons) it means we'll need about 700 cntrs !!! , and the contract will be about 150.000 tons divided into 10 shipments of 15 000 each . break bulk will be much cheaper , pls try to find some one else very urgently try shipco people maybe they can do it. pls mamun this is very important and top urgent , also I need reply overnight as client is losing patience. tks & rgs zouhair >From: mamun <mam_moudayfer(a)awalnet.net.sa> >To: new_zmkm(a)hotmail.com >Subject: Fw: RATE RQST FROM RIO JANERIO TO JEDDAH PORT >Date: Tue, 23 Dec 2003 09:55:09 +0300 > >Zouz > >Here is the reply fm brazil , as they can not offer service by Breakbulk. >pls comments. >Rgds/Mamun > >-----Original Message----- >From: Alexandre Jacomo <alexandre(a)unicarrier.com.br> >To: asad_moudayfer(a)awalnet.net.sa <asad_moudayfer(a)awalnet.net.sa> >Date: Monday, December 22, 2003 10:01 PM >Subject: RATE RQST FROM RIO JANERIO TO JEDDAH PORT > > >Dear Mr Asad Moudayfer > >Thank you for your below rate request. Pls be advised our best rate: > >From Rio de Janeiro Port to Jeddah Port >Cntr 20' std: US$ 2100 + $200 Baf >Cntr 40' std: US$ 3100 + $400 Baf >TT 45 days via Singapore >Charges in Rio de Janeiro Port >US$ 25 BL >US$ 50 per cntr 20' or 40' Capatazias - Brazilian THC > >Break Bulk from Rio de Janeiro Port to Port Klang/Malaysia >Unfortunately we can't offer this service, because we can't use our BL to >Break Bulk cargo. > >Rgds, > >Alexandre Jácomo > Commercial Dept. > UnicarrieR Ltd. - The Friendshipper > Tel.: 5511 3253 5334 Fax: 5511 3253 5277 > Email: alexandre(a)unicarrier.com.br > Web: www.unicarrier.com.br > Neutralidade - Segurança - Ética >----- Original Message ----- >From: Asad >To: Alexandre >Sent: Monday, December 22, 2003 2:10 PM >Subject: Fw: RATE RQST FROM RIO JANERIO TO JEDDAH PORT > > > >Dear Alexandre > >Ref to our mail below earlier few minutes. > >Please note, we want rates by Break-bulk from fob RIO JANERIO upto PORT >KLANG/MALAYSIA >COMMODITY : RAW SUGAR IN BAGS TOTAL 150 THOUSAND TON / 15 THOUSAND TONS IN >EACH LOT. > >Please name the carrier & T/Time along with your best obtainable Bulk >rates at your earliest. > >Best Regards > >Mamun >Moudayfer & Bros co. >Riyadh - Ksa > >-----Original Message----- >From: Asad <asad_moudayfer(a)awalnet.net.sa> >To: Alexandre <alexandre(a)unicarrier.com.br> >Date: Monday, December 22, 2003 6:46 PM >Subject: RATE RQST FROM RIO JANERIO TO JEDDAH PORT > > >Dear Mr. Alexandre >Good Day > >Please provide us your best possible FOB ocean freight rate for 1X40fit & >1X20fit cntr from RIO JANERIO to Jeddah port. The commodity is sugar. > >We will appriceate about your soonest reply. > >Thanks & Best Regards > >Asad >Moudayfer & Bros Co >Riyadh >K.s.a. _________________________________________________________________ Working moms: Find helpful tips here on managing kids, home, work and yourself. http://special.msn.com/msnbc/workingmom.armx

19 years, 5 months

Re: [TUHS] question about mkfs(8) and stdio

by msokolov＠ivan.Harhan.ORG

Kenneth Stailey <kstailey(a)yahoo.com> wrote: > Did stdio buffering change over time? Line buffering was a Berkeley innovation. stdout became line-buffered by default (when it is a terminal) in 4.0BSD. 4.2BSD added setlinebuf(3) to allow people to make stdout or stderr line-buffered when they want to. 4.3BSD extended it to work on any stream, not just stdout or stderr. > If you look at an old BSD mkfs for cylinder-group style file systems (not 7th > Ed filesystems) Ahmm, you call that old? To me it's new... It's a (wonderful) 4.2BSD innovation. > but I have memories that the superblocks were printed out one at a time as if > fflush(stdout) was called between them rather than one line at a time with > line-buffered stdio. I use 4.3BSD-* systems every day and have been for the past several years, and you can take my word for it that on all 4.3BSD-* systems, including Quasijarus, plain 4.3, and Ultrix the alternate superblock list output from mkfs/newfs appears one line at a time on the tty. > At some point I thought "SysV must have broke this" I'm curious, where does SysV fit into this? It's the wonderful 4.2BSD filesystem a BSD-only thing that Missed'em-five people treated as a satanic manifestation? > since newfs would print out > a complete row of superblock numbers at once with a big delay between the rows That's exactly what it does. BTW mkfs = newfs. mkfs was/is the original UNIX filesystem creator. It was almost completely rewritten in 4.2BSD to create the new filesystems. At the same time the newfs program was written as a user- friendly front-end to mkfs (it merely exec'ed mkfs with a bunch of options). The situation remained in 4.3. In 4.3-Tahoe/Quasijarus mkfs.c and newfs.c are compiled and linked into one binary called newfs, CSRG was forced to do this in order to support disk labels. MS

19 years, 5 months

Re: [TUHS] question about mkfs(8) and stdio

by John Holden

> you will see the super block backup loop does not fflush(stdio) between > printf()s Was there a 'setbuf(stdout, NULL)' at the beginning? This would force immediate output from any printf's (less efficient than a fflush)

19 years, 5 months

question about mkfs(8) and stdio

by Kenneth Stailey

Did stdio buffering change over time? If you look at an old BSD mkfs for cylinder-group style file systems (not 7th Ed filesystems) you will see the super block backup loop does not fflush(stdio) between printf()s printf("super-block backups (for fsck -b#) at:"); for (cylno = 0; cylno < sblock.fs_ncg; cylno++) { initcg(cylno); if (cylno % 10 == 0) printf("\n"); printf(" %d,", fsbtodb(&sblock, cgsblock(&sblock, cylno))); } but I have memories that the superblocks were printed out one at a time as if fflush(stdout) was called between them rather than one line at a time with line-buffered stdio. At some point I thought "SysV must have broke this" since newfs would print out a complete row of superblock numbers at once with a big delay between the rows rather than each superblock number with a short delay between each number. But when I go searching the oldest BSD code has no fflush(stdout) the way modern FreeBSD does: for (cylno = 0; cylno < sblock.fs_ncg; cylno++) { initcg(cylno, utime); if (mfs) continue; j = snprintf(tmpbuf, sizeof(tmpbuf), " %ld%s", fsbtodb(&sblock, cgsblock(&sblock, cylno)), cylno < (sblock.fs_ncg-1) ? "," : "" ); if (i + j >= width) { printf("\n"); i = 0; } i += j; printf("%s", tmpbuf); fflush(stdout); } Did stdio buffering change over time so that line buffering became the default? Thanks, Ken __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree

19 years, 5 months

RE: [pups] pdp11/73 memory

by Fred N. van Kempen

Hi all, > No. The uVAX memory requires special PMI stuff (carried over those > ribbon cables) that the PDP-11 CPUs don't grok. At least, that's > what I've always been told. Correct. --f

19 years, 5 months

[pups] pdp11/73 memory

by Christos Papachristou

I recently found a cabinet with a MicroVAX II (in 2 BA23 enclosures) and quite a lot storage devices on it. I plan to replace the MicroVAX II CPU module (M7606-AA) with a pdp11/73 CPU module (M8192) . I only have a 512k RAM module (M8067LA) for the pdp11/73 . The microVAX has two quad height memory modules , but I haven't checked yet whether they are 1, 2 ,4 or 8 megs each (ie M7607,M7608 or M7609) .Is it possible to keep some of the MicroVAX memory modules if they are below or equal to 4 megs?

19 years, 5 months

Re: [pups] pdp11/73 memory

by Carl Lowenstein

> From: "Christos Papachristou" <chpap(a)ics.forth.gr> > To: <pups(a)minnie.tuhs.org> > Date: Fri, 12 Dec 2003 18:31:12 +0200 > Subject: [pups] pdp11/73 memory > > I recently found a cabinet with a MicroVAX II (in 2 BA23 enclosures) and > quite a lot storage devices on it. I plan to replace the MicroVAX II CPU > module (M7606-AA) with a pdp11/73 CPU module (M8192) . I only have a > 512k RAM module (M8067LA) for the pdp11/73 . The microVAX has two quad > height memory modules , but I haven't checked yet whether they are 1, 2 > ,4 or 8 megs each (ie M7607,M7608 or M7609) .Is it possible to keep some > of the MicroVAX memory modules if they are below or equal to 4 megs? No. MicroVAX memory uses a different interconnect scheme. It is not in the Qbus address space. carl -- carl lowenstein marine physical lab u.c. san diego clowenst(a)ucsd.edu

19 years, 5 months

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

1991

1990

TUHS December 2003