TUHS

tuhs@tuhs.org

47 participants
6503 discussions

by Wesley Parish

Anyone thought of asking him if he could contribute his Concurrent Pascal and Solo, etc, to PUPS? Just a thought. Welsey Parish -- Mau e ki, "He aha te mea nui?" You ask, "What is the most important thing?" Maku e ki, "He tangata, he tangata, he tangata." I reply, "It is people, it is people, it is people."

22 years

Re: [pups] 2.11BSD device config trouble

by Steven M. Schultz

Hi - > From: Jochen Kunz <jkunz(a)unixag-kl.fh-kl.de> > I am preparing my PDP-11/73 for my exhibition at the VCFe. I want to get > the DHV11 (M3104) and a four port DLV11J clone to work. At the moment I > get upon boot: > > autoconfig: warning: more than three handlers for device cn on line 38. That is not a normal message. I believe autoconfig is saying that is something wrong with line 38 of /etc/dtab > dhv ? csr 160440 vector 310 didn't interrupt. > ra 0 csr 172150 vector 154 vectorset attached > ra 1 csr 160334 vector 764 vectorset attached > rx ? csr 177170 vector 264 skipped: No CSR. > tms 0 csr 174500 vector 260 vectorset attached > ts 0 csr 172520 vector 224 attached > cn 1 csr 176540 vector 344 no address found for kl/dl-11 > What is wrong with the "cn" devices? Is 'cn 1 ...' line 38 of the /etc/dtab file? Did you compile a kernel with NKL set to 5 (1 for the console and 4 for the DLV11J)? Cheers, Steven Schultz

22 years

Re: [pups] 2.11BSD device config trouble

by Steven M. Schultz

Hi - > From: Jochen Kunz <jkunz(a)unixag-kl.fh-kl.de> > > > cn 1 csr 176540 vector 344 no address found for kl/dl-11 > > Is 'cn 1 ...' line 38 of the /etc/dtab file? > Yes: > cn 1 176540 344 5 cnrint cnxint Interesting. I do not recall any particular problem getting additional DL devices recognized (the 11/93 had 7 of them). Seeing the 'no address found' error is *strange* though - that would indicate that 'autoconfig' could not find 'cnrint' or 'cnxint' in the /unix symbol table. Look at /sys/autoconfig and you can see where that message is coming from. If you do nm /unix | egrep 'cnxint|cnrint' what do you see? > NKL 4 # KL11, DL11 > The card has four ports, one of them is the console. (The M8192 CPU card > has no SLU / ROM / ...) Ah, ok. My 11/73 has a SLU/ROM card and the console is on that. I also have a DHV installed (alas, the system is powered down now so I can not check for more information). > But I would prefere to get the DHV11 working. It seams that this device > is more suitable for multi user operation. Yes, it's a little better. Not as nice as a DHQ-11 though (which can run in DHU or DHV modes - with DHU mode having much better silo handling). I forget the exact error you were getting on the DHV but if it was 'no interrupt' then it might be that the DHV clone is not behaving exactly like a DEC DHV In /sys/autoconfig/dhvauto.c here is how the probing attempts to force an interrupt: dhvprobe(addr,vector) struct dhvdevice *addr; int vector; { if ( grab ( &(addr->dhvcsr) ) & DHV_CS_MCLR ) DELAY(35000L); if ( grab ( &(addr->dhvcsr) ) & (DHV_CS_MCLR|DHV_CS_DFAIL) ) return ( 0 ); stuff ( DHV_CS_RI | DHV_CS_RIE, &(addr->dhvcsr) ); DELAY(3500L); stuff ( 0, &(addr->dhvcsr) ); return(ACP_IFINTR); } Either 3500 microseconds (very approximately of course) is too short of a wait _or_ the method of trying to generate an interrupt is not correct. You can try changing 'ACP_IFINTR' to 'ACP_EXISTS' which tells autoconf to not care if the device interrupted or not. > ** Last Mounted on / > ** Root file system > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Free List > BLK(S) MISSING > SALVAGE? y > > ** Phase 6 - Salvage Free List > 1364 files, 11625 used, 2430 free > > ***** FILE SYSTEM WAS MODIFIED ***** > > But on the next reboot I get the same when running fsck. Any hints? How are you rebooting? With the "reboot" command or by using the 'halt' button? You do not want to use the 'reboot' command because that does a "sync" which flushes the disc cache (and superblock) back out to disc - that overwrites the work that 'fsck' did. A few 'missing' blocks is not a serious problem though and can be ignored. Cheers, Steven Schultz

22 years

Re: [pups] 2.11BSD device config trouble

by Steven M. Schultz

Hi! > From: David Evans <dfevans(a)bbcr.uwaterloo.ca> > > cn 1 176540 344 5 cnrint cnxint > > to the end of this line? Perhaps the autoconfig parser becomes confused > if there aren't any. I don't think that's the problem in this case - the error that is being printed out: cn 1 csr 176540 vector 344 no address found for kl/dl-11 comes from what appears to be a missing entry (or an entry that autoconfig can't find) in the /unix kernel symbol table. One way, I think, this can happen is when booting an alternate kernel (/genunix instead of /unix). THe only suggestion I have at this point is to turn on debugging in autoconfig. To do this go into /sys/autoconfig/main.c and add a line that forces 'debug = 1;', then install (after saving the original ;)) autoconfig into /etc and reboot. Hopefully useful info about what autoconfig is doing will be printed. > Mine is at least correctly identified by autoconfig, though I've never > attached a terminal to it to see whether the ports actually do anything. > The post that's vanished included my dhv line from /etc/dtab but, except > for the goofy CSR I used for some reason that I cannot now remember, it If I find the time I'll power up the 11/73 and see what it says but I've had a DHV11 on the system for years (it's how I got the RTS/CTS flow control working). My suspicion is that the DHV clone isn't behaving 100% like a DEC DHV card. > > BTW: Never play with the SMD cables when the machine is running. Now I > > get: > > Is the disk write-inhibited? Doing a 'reboot' (which performs a sync(2) call) will overwrite what fsck has done - when the message about "reboot" comes out you should use the front panel or ODT to simply halt the cpu and then start the boot process cold. Cheers, Steven Schultz

22 years

[pups] 2.11BSD device config trouble

by Jochen Kunz

Hi. I am preparing my PDP-11/73 for my exhibition at the VCFe. I wane get the DHV11 (M3104) and a four port DLV11J colne to work. At the moment I get upon boot: autoconfig: warning: more than three handlers for device cn on line 38. dhv ? csr 160440 vector 310 didn't interrupt. ra 0 csr 172150 vector 154 vectorset attached ra 1 csr 160334 vector 764 vectorset attached rx ? csr 177170 vector 264 skipped: No CSR. tms 0 csr 174500 vector 260 vectorset attached ts 0 csr 172520 vector 224 attached cn 1 csr 176540 vector 344 no address found for kl/dl-11 Extract from /etc/dtab: # grep '^[a-zA-Z]' /etc/dtab dhv ? 160440 310 5 dhvrint dhvxint # dhv terminal mux ra ? 172150 154 5 raintr # uda50, rqdx1/2/3 ra ? 160334 764 5 raintr # uda50, rqdx1/2/3 rx ? 177170 264 5 rxintr # rx01/02 tms ? 174500 260 5 tmsintr # tmscp driver ts ? 172520 224 5 tsintr # ts11 driver cn 1 176540 344 5 cnrint cnxint cn 2 176550 354 5 cnrint cnxint cn 3 176560 364 5 cnrint cnxint What is wrong with the "cn" devices? I checked the CSRs of the DHV11 and the DLV11J cards with the "show qbus" command on a MicroVAX 4000-200 to be sure that the CSRs are where I am expecting them: >>>sh q Scan of Qbus I/O Space -20000120 (760440) = 009D DHQ11/DHV11/CXA16/CXB16/CXY08 -20000122 (760442) = F081 -20000124 (760444) = 0000 -20000126 (760446) = 0000 -20000128 (760450) = 0000 -2000012A (760452) = 0000 -2000012C (760454) = 0000 -2000012E (760456) = 0000 -20001940 (774500) = 0000 TQK50/TQK70/TU81E/RV20/KFQSA-TAPE -20001942 (774502) = 0BC0 -20001D60 (776540) = 0000 DLV11J -20001D62 (776542) = 0000 -20001D64 (776544) = 0080 -20001D66 (776546) = 0000 -20001D68 (776550) = 0000 DLV11J -20001D6A (776552) = 0000 -20001D6C (776554) = 0080 -20001D6E (776556) = 0000 -20001D70 (776560) = 0000 DLV11J -20001D72 (776562) = 0000 -20001D74 (776564) = 0080 -20001D76 (776566) = 0000 -20001F40 (777500) = 0020 IPCR -20001F70 (777560) = 0000 -20001F72 (777562) = 0000 -20001F74 (777564) = 0080 -20001F76 (777566) = 0000 -- tschüß, Jochen Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/

22 years

cross reference tool for pre-K&R C

by nao

Hi, I really enjoy hacking ancient unix rather seriously and want a cross reference tools for them. Since some of them are written in pre-K&R C, modern tools are not very useful. Is there any cross reference tool for pre-K&R C source codes? BTW, early UNIX assembler document has bugs which state '>>' and '<<' are shift operators despite that really '\>' and '\<' are. I wonder where these bugs came from... Cheers, - nao

22 years, 1 month

Re: [TUHS] 2.11BSD license question: porting software to NetBSD

by Igor Sobrado

> On Friday, 18 April 2003 at 18:56:16 +0200, Igor Sobrado wrote: > > > > I asked to the people of the NetBSD Foundation about the possibility > > of adding those commands to the base system (as a part of the tarball > > with documentation tools) but they think that it is not possible, > > as a consequence of a licensing issue. I supposed that all the > > software provided in the 2.11BSD was under a BSD license, but it > > looks like 2.11BSD is a closed source release. > > That's not correct any more. Who were you talking to at the NetBSD > project? Hi Greg. I am worried with possible licensing issues with AT&T's Documenter's Workbench (DWB). In fact, AT&T retained the copyright and distribution rights on those parts of the UNIX documentation tools they developed some years ago. That is the reason we have [nt]roff, but not diction (diction(1), explain(1), suggest(1)) and style(1). Last days, Perry E. Metzger observed that 2.11BSD was closed source: "And it is closed source. Sorry. We aren't allowed to use code that did not originate in V7/32V. If Caldera did not specifically release the sources, we cannot use them. If your claim is that diction and style were not in 32V, then we have no rights to them." Well, in a previous email Perry observed that: "I appreciate all this and I thank you for doing the work, but please do your work against a version we have clear ability to use." In short, he does not says that "we cannot add diction(1) and style(1) to NetBSD" only that *license terms are NOT clear*. What I do *not* want to do, is asking for adding a piece of code that will report problems to the NetBSD Foundation. They are doing a superb job, and I do not want to start a legal problem adding some tools whose license is not clear. On the other hand, Steven M. Schultz observed that "Not 100% - much of it is covered by the BSD license and the Caldera/SCO/whatever license(s)". I believe that diction(1) and style(1) are covered by a different license agreement, but I did not find it in the source code. > > Can someone, please, helping me on this matter? What should I do? > > Should I just drop this software? > > We discussed the Caldera release of "ancient UNIX" on this mailing > list recently. Caldera (now SCO again) was supposed to make some kind > of official statement, but it's taking its time. Well, there are some operating systems under Caldera's agreement (a BSD-style license), including v7 and 32V, but looks like 2.11BSD is *not* under those terms. In fact, it is not available through Caldera, it is in tuhs, not covered by Caldera's license agreement. (at least I think that it is right...) I am not a lawyer, only a Physics grad student working on a Ph. D. on CS. I have no idea about the legal status of 2.11BSD or, to be more precise, about the status of diction(1) and style(1). Cheers, Igor. -- Igor Sobrado, UK34436 - sobrado(a)acm.org

22 years, 1 month

2.11BSD license question: porting software to NetBSD

by Igor Sobrado

Hello. I have just finished porting diction(1) and style(1) from 2.11BSD to the NetBSD operating system. Those utilities are a part of the AT&T Documenter's Workbench (DWB), and are not available on the v7 and 32V UNIX releases. I asked to the people of the NetBSD Foundation about the possibility of adding those commands to the base system (as a part of the tarball with documentation tools) but they think that it is not possible, as a consequence of a licensing issue. I supposed that all the software provided in the 2.11BSD was under a BSD license, but it looks like 2.11BSD is a closed source release. Can someone, please, helping me on this matter? What should I do? Should I just drop this software? Cheers, Igor. -- Igor Sobrado, UK34436 - sobrado(a)acm.org

22 years, 1 month

Re: TUHS digest, Vol 1 #145 - 2 msgs

by Larry McVoy

> I am fairly sure that 4.2BSD had manual pages for mmap, but it didn't > work. Right. Joy left Berkeley and joined Sun and the work got done at Sun. I'm pretty sure that SunOS 4.0 was the first release with mmap working as it was described. I was at Sun for the 4.1 release; 4.0 was the new VM system, and it wasn't "new" like "we changed some stuff", it was new as in everything was rewritten. The 4.0 VM system had segmap, read/write were implemented with segmap in the kernel (you did a read, the kernel mapped page, started a bcopy and would fault on itself if the page wasn't there or had no TLB entry). Etc. I have postscript of the papers on that, still very good reading if someone wants them. -- --- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm

22 years, 1 month

Did SunOS 3 have mmap(2)?

by Warren Toomey

Hi all, I just received a query: did SunOS 3 have a working mmap(2)? My vague memory says no, but I don't have access to a 3.5 box any more to find out. Can anybody help out here? Warren

22 years, 1 month

[pups] ISO9660 filesystem on 2.11BSD

by David Evans

Has anyone tried to do such a thing? Would anybody care? -- David Evans (NeXTMail/MIME OK) dfevans(a)bbcr.uwaterloo.ca Ph.D. Candidate, Computer/Synth Junkie http://bbcr.uwaterloo.ca/~dfevans/ University of Waterloo "Default is the value selected by the composer Ontario, Canada overridden by your command." - Roland TR-707 Manual

22 years, 1 month

Re: [TUHS] PDP11/34 boot problems, here i am again :)

by Carl Lowenstein

> From: asbesto <asbesto(a)freaknet.org> > To: tuhs(a)tuhs.org > Subject: [TUHS] PDP11/34 boot problems, here i am again :) > > well, i think now we have a more complete knowledge of the REAL > problem ! > > the M7891 board (128K x 18 bit MOS MEMORY MODULE) have the D2 red=20 > led light turned ON when turning on the CPU ! > > this means PARITY ERROR on this board :( > > checking the board we found 2 problems: > > 1) a 74LS175 chip named E15 on our schematic diagram, that seem > phisically BROKEN on an edge (there is a fessure on the plastic > DIP package). i can't change it now because i don't have a=20 > soldering station here to do a nice job, but looking the chip i > think it may work... While you probably _do_ have a real hardware problem with the broken IC, I think that the red Parity Error light on first turn-on is normal behavior. The MOS memory comes up with random values, and about half of them will have the wrong parity. Some software routine must turn off parity error detection and write a known data pattern (all 0's) to each memory location. I don't remember whether this is something that is done by the boot ROM of an 11/34. carl -- carl lowenstein marine physical lab u.c. san diego clowenst(a)ucsd.edu

22 years, 1 month

RE: [TUHS] PDP11/34 boot problems, here i am again :)

by Gooijen H

"asbesto" wrote: > 1) a 74LS175 chip named E15 on our schematic diagram, that seem > phisically BROKEN on an edge (there is a fessure on the plastic > DIP package). i can't change it now because i don't have a > soldering station here to do a nice job, but looking the chip i > think it may work... I never remove IC's in *one* go. The chances that you damage the multi-layer board beyond repair are real. This is what I do. I use a dremel tool (small motor with sharp rotating blade) to cut the pins of the IC one by one. Don't use a cutting tool to cut the pins because the side force might push the remainder of the pin through the solder joint thus damaging the board. After you have cut all the pins the IC just falls of the board. Now, you can use a fine hot soldering iron and remove the pins one by one use a pair of squeezers. good luck with your repairs, - Henk.

22 years, 1 month

PDP11/34 boot problems, here i am again :)

by asbesto

well, some months ago i asked for help booting a pdp11/34 here at freaknet medialab :) well, i think now we have a more complete knowledge of the REAL problem ! the M7891 board (128K x 18 bit MOS MEMORY MODULE) have the D2 red led light turned ON when turning on the CPU ! this means PARITY ERROR on this board :( checking the board we found 2 problems: 1) a 74LS175 chip named E15 on our schematic diagram, that seem phisically BROKEN on an edge (there is a fessure on the plastic DIP package). i can't change it now because i don't have a soldering station here to do a nice job, but looking the chip i think it may work... 2) a 5 Kohm 4-resistor bridge named R22 on our diagram, that is phisically BROKEN. this bridge give +5V on signals named DATA OC L, CSR OC L, OC L and X ADD OC L. i changed it with a 4.7Kohm 4-resistor bridge, without any result. (maybe the 74ls175 is really broken :) an other ipothesys may be: some electrolitic capacitor in short circuit. we had this problem on a decwriter III ! :) the real problem is: if we aren't able to repair the M7891 board, where can we find a "new" one ??? can somebody help us ? it's a shame for us to have our pdp11/34 offline :(( any help is appreciated ! *:) -- [asbesto : freaknet medialab : radio#cybernet : GPG key on keyservers] [ MAIL ATTACH, SPAM, HTML, WORD, and msgs larger than 95K > /dev/null ] [http://www.freaknet.org/asbesto :::::: http://kyuzz.org/radiocybernet]

22 years, 1 month

[pups] VAX support

by robin.birch＠royalmail.com

Hi All, I know that this isn't pdp related but the people are here who know :-). Is there an available unix that supports lance and dssi on a VAX 3400 and/or is there anyone working on this. Regards Robin This email and any attachments are confidential and intended for the addressee only. If you are not the named recipient, you must not use, disclose, reproduce, copy or distribute the contents of this communication. If you have received this in error, please contact the sender and then delete this email from your system.

22 years, 1 month

Franz Lisp platforms

by L.J. Buitinck

while trying to build Franz Lisp (from 4.3 BSD) on VAX/ULTRIX 4.5, I noticed its peculiar list of supported platforms: use: lispconf type where type is one of vax_4_1 vax_4_1a vax_4_1c vax_4_2 vax_4_3 vax_eunice_vms sun_4_1c sun_unisoft dual_unisoft pixel_unisoft sun_4_2beta lisa_unisys3 mc500_2_0 I was especially surprised by "lisa_unisys3". is that Unisoft SysIII for the Apple Lisa?! and does anyone know what {dual,pixel}_unisoft and mc500_2_0 mean? -- If I travelled to the end of the rainbow As Dame Fortune did intend, Murphy would be there to tell me The pot's at the other end. Lars Buitinck

22 years, 1 month

Re: [pups] booting RT11 from alternate controller

by Jonathan Engdahl

I'll have to try this with the RQDX3 as primary and the SCSI as secondary. Maybe BSD is smart enough to do it right. In any case, I have the source for the BSD boot code, and I can fix it. It will be a pain, though, having to type the alternate address every time I boot BSD. I'd probably have to restructure /dev and /etc/fstab also, and who knows what else. Maybe it would be easier to change the jumpers if I needed to run RT11. I don't use RT11 that much, but I'd like to have it available. -- Jonathan Engdahl http://users.safeaccess.com/engdahl "The things which are seen are temporary, but the things which are not seen are eternal." II Cor. 4:18 ----- Original Message ----- From: "Fred N. van Kempen" <Fred.van.Kempen(a)microwalt.nl> To: "Jonathan Engdahl" <j.r.engdahl(a)adelphia.net> Sent: Wednesday, April 02, 2003 5:58 AM Subject: RE: [pups] booting RT11 from alternate controller Jonathan, > I have a PDP-11/53 with a SCSI controller at 172150, and an > RQDX3 at 172144. This works for the ROM, but most PDP-11 operating systems will refuse to boot from anything but the "default" controller of any kind, meaning, an MSCP controller it will only accept at 172150. The OS itself can deal with them, but not so for the boot-level code that loads them. I have tried similar setups with an 11/83 using an ESDI disk controller at MSCP #0 (doing KDA50 emu), and an RQDX3 at MSCP #1 (just for the floppies, indeed) and that didnt work either, with RT11, MicroRSX and Ultrix. --f

22 years, 1 month

[pups] booting RT11 from alternate controller

by Jonathan Engdahl

I have a PDP-11/53 with a SCSI controller at 172150, and an RQDX3 at 172144. There are a couple SCSI drives on the primary controller, and an RX50 on the RQDX3. Everything seems to work OK, and I can read the floppies, except I cannot boot RT11 from a floppy. From the 11/53 boot ROM you can say B/A DU0 It will then ask for the address of the alternate controller. It reads from the floppy, then it reads from both hard drives, then hangs. What I hunch is happening is that the boot ROM reads the RT11 boot sector from the floppy, but then the boot sector tries to continue booting from the hard drives, which isn't going to work, because they are 2.11BSD formatted. The objective is to have some non-RQDX3 hard drive controller as the primary, and a secondary RQDX3 for the floppy, and to be able to boot UNIX from the hard drive, and RT11 from the floopy. Any ideas on how to accomplish this? -- Jonathan Engdahl http://users.safeaccess.com/engdahl "The things which are seen are temporary, but the things which are not seen are eternal." II Cor. 4:18

22 years, 1 month

[pups] V7 setjmp/longjmp

by Dennis Ritchie

Helbig remarked (quoting Davidson): > >Yes, you are right - V7 restores the register variables to a state which > >is consistent with the other auto variables in the function - ie the value > >which they had when longjmp was called. > > > >The caveats about not relying on register variables applied to V6. > Nope, even in V6, register variables are restored to the values they had > when reset(III) was called! (reset() is the name of longjmp() in V6). > By the way, reset() is much smaller than longjmp() but provides the same > functionality. > I wonder why longjmp() was rewritten. Setjmp/longjmp do more (setjmp returns different values for the initial call and the longjmp-invoked one). But the thing that would become more important is that the PDP-11 compiler's calling sequence was especially friendly toward restoring register values-- it just worked automatically. Other machines and compilers were not so friendly. This is why ANSI and ISO had to put in special rules about promising to preserve only things marked volatile. We've been through this before. Dennis

22 years, 2 months

Re: [pups] V7 setjmp/longjmp

by Wolfgang Helbig

>X-Unix-From: michael_davidson(a)pacbell.net Tue Dec 31 17:04:50 2002 >Date: Tue, 31 Dec 2002 08:02:37 -0800 >From: Michael Davidson <michael_davidson(a)pacbell.net> >User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 >X-Accept-Language: en-us >MIME-Version: 1.0 >To: Wolfgang Helbig <helbig(a)Informatik.BA-Stuttgart.DE> >CC: pups(a)minnie.tuhs.org >Subject: Re: [pups] V7 setjmp/longjmp >Content-Transfer-Encoding: 7bit > >Wolfgang Helbig wrote: >>You can trust register variables when setjmp() returns the second time. Then >>the registers are restored to the values they had when the "next" function was >>called, that is the "values as of the time longjmp() was called" (quoted from >>longjmp(3)'s man page. Thus any variable behaves the same, regardless of its >>storage class. >> >Yes, you are right - V7 restores the register variables to a state which >is consistent with the other auto variables in the function - ie the value >which they had when longjmp was called. > >The caveats about not relying on register variables applied to V6. Nope, even in V6, register variables are restored to the values they had when reset(III) was called! (reset() is the name of longjmp() in V6). By the way, reset() is much smaller than longjmp() but provides the same functionality. I wonder why longjmp() was rewritten. Wolfgang.

22 years, 2 months

Re: [pups] Totally off topic question

by Peter Turnbull

On Mar 21, 19:31, Ian King wrote: > Yup. I used to do that, but had an older version of sendmail and got > 'co-opted' as a relay host for a spammer. :-( I've seen a few attempts to do that. I should point out that even if you only run sendmail for the benefit of machines on your own network, and even if you use a dialup (rather than always-on) connection, you want the ant-relay stuff. I see regular attempts to connect to port 25 on my hub, even though it's behind a dynamic IP address on an ISDN dialup (I also see regular attempts to connect to the telnet, ssh, and ftp ports, and others, maybe 2-3 times a week. If you run a common operating system, don't assume that a dynamic IP address, or NAT, or using a dialup, gives any worthwhile protection). > FWIW: rather than update sendmail and hack another .cf, I bought a > Windows-based mail server Nowadays, it's easy to use m4 to set up sendmail.cf for the common sorts of home use -- just define the settings for masquerading and smarthost, and press go (more or less). The only time you need to hack it a bit is if you want something unusual, like some mail going to the local machine and some forwarded to other machines on your network, or using UUCP. > Instead, I use my free time to hack 2.11BSD and UNIX v6! :-) I have to admit that sounds like a better use of the time :-) -- Pete Peter Turnbull Network Manager University of York

22 years, 2 months

Re: [pups] Totally off topic question

by Peter Turnbull

On Mar 21, 23:04, Robin Birch wrote: > I am probably going to get a broadband connection to wherever I end up. > I will then network all of the various boxes together and connect > everything (including the PDP) to the Internet. I intend having one box > set up as a server [...] > In case the above seems stupid the idea is to take all email through a > server, weed out all incoming rubbish, and route it to various > individual's (partner, daughter etc.) PCs. This is exactly what I do, though I have the sending and receiving sides of the email equation separate. I have one machine that acts as a mail hub. It runs sendmail with a custom sendmail.cf which is capable of delivering internal mail either to /var/mail, which is then exported to other machines, or via UUCP or SMTP to other machines. It also batches up outgoing mail and sends it to my ISP's mail server ("Smart Host") at specific times of the day (mine's not an always-on connection). All the other machines either use UUCP, or use sendmail with the "nullclient" .cf file, to send mail to my hub machine. No reason why the hub couldn't run a POP3 server for the benefit of Windoze PCs as well, but I've never felt the need :-) If you go that route, I'd suggest you think about IMAP rather than POP, though. As far as getting mail from my ISP, I use fetchmail -- but if you do this, be sure that your ISP puts something in the headers that makes it easy for fetchmail to tell which user it's really for (don't forget about mailing lists), and that you have a catchall rule to handle mail you didn't think of. If you have an always-on connection, you could have your DNS MX record(s) set to point to your hub machine, and needn't use fetchmail. However, if you do that, be sure to set up sendmail with anti-relaying and all the proper security patches. -- Pete Peter Turnbull Network Manager University of York

22 years, 2 months

[pups] Totally off topic question

by Robin Birch

Hi Everyone, Sorry for asking this here but you are probably the best people to ask. I'm in the process of packing up my house to redecorate it and move to another. As a result my 11/83 has been packed up and I won't get to play for some time :-(. However, the question - I am probably going to get a broadband connection to wherever I end up. I will then network all of the various boxes together and connect everything (including the PDP) to the Internet. I intend having one box set up as a server for FTP, email and so on and everything else using that. I will probably use a Linux box for this. Can I get a pop3 system for it that will talk to sendmail (only because sendmail is the only mail system that I have used) or can I get a reasonable pop3 server for Linux. Anybody else has ideas on how I should do this then hints tips etc. gratefully received. In case the above seems stupid the idea is to take all email through a server, weed out all incoming rubbish, and route it to various individual's (partner, daughter etc.) PCs. Cheers Robin -- Robin Birch

22 years, 2 months

Re: [pups] Progress on 2.11BSD kernel

by Steven M. Schultz

Hi - > From: "Ian King" <iking(a)killthewabbit.org> > I tried changing the partition type with disklabel -e -r but, when I exited > vi, I got an error message saying that the type I'd provided was not valid. > Viewing the label (with disklabel -r) showed the fstype set to 'unknown'. "unknown" or "unused" On my virtual 11 I see disklabel report: 8 partitions: # size offset fstype [fsize bsize] a: 16720 0 2.11BSD 1024 1024 # (Cyl. 0 - 39) b: 8360 16720 swap # (Cyl. 40 - 59) c: 340670 0 unused 1024 1024 # (Cyl. 0 - 814) h: 315590 25080 2.11BSD 1024 1024 # (Cyl. 60 - 814) > Just for grins, I tried modifying the drive type, too - no success there, > either. The disklabel utility isn't having any of that; again it claims > 'unknown'. Ah, that says something is corrupt somewhere. If you look at /usr/include/sys/disklabel.h you'll see the table of filesystem types: static char *fstypenames[] = { "unused", "swap", "Version 6", "Version 7", "System V", "2.11BSD", "Eighth Edition", "4.2BSD", "MSDOS", "4.4LFS", "unknown", "HPFS", "ISO9660", 0 }; So for 'unknown' to appear there would need to be a 10 in the type field instead of a 5 (for "2.11BSD"). 'unused' is a 0 obviously. Try booting up a standalone disklabel and see what it says without a kernel getting involved. Steve

22 years, 2 months

Re: [pups] Progress on 2.11BSD kernel

by Steven M. Schultz

Hi - > From: "Ian King" <iking(a)killthewabbit.org> > Now I know I'm missing something. I tried following your advice, using the > disklabel utility running under the old kernel. From what you say below, I Which part of the advice? ;) The part of the advice that might be most useful was to put a copy of the standalone disklabel program in / and boot it - NOT run the usermode version while the system is running. cd /sys/pdpstand make cp disklabel / then reboot the system and at the ':' prompt enter ra(0,0)disklabel there are things that can be done with the standalone version that are either impractical under a kernel (because the 'a'/root partition is open/busy) or because the standalone version has no safety checks. > assume you are referring to the 'fstype' parameter on the partition, not the > 'type' parameter for the drive, correct? The drive type is MSCP, and the > partition fstype is 2.11BSD. 'fstype' is what I had in mind. a: 16720 0 2.11BSD 1024 1024 # (Cyl. 0 - 39) > I tried changing the partition type with disklabel -e -r but, when I exited > vi, I got an error message saying that the type I'd provided was not valid. > Viewing the label (with disklabel -r) showed the fstype set to 'unknown'. Now I am confused. 2.11BSD is correct - but then it's "unknown" and that would cause the 'iinit' panic that started this thread of discussion. Down the path of logic that results in a 'iinit' panic and the 'no fs' there's a check for the filesystem type and "unknown" was the likely cause (or at least that was the hope). If the standalone disklabel program says it's "2.11BSD" then there's something else going on - the next likely thought is that 'rootdev' or related entity isn't set to the device that is the actual root filesystem. > Just for grins, I tried modifying the drive type, too - no success there, > either. The disklabel utility isn't having any of that; again it claims > 'unknown'. That's not used for anything important. > Oh well, while I'm waiting for your reply I can rebuild my kernel with a > higher MAXUSERS parameter. :-) ~12 is a good number - not much need for more than that as a rule. Steve

22 years, 2 months

Jump to page:

2025

2024

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