HDTenEightyP/NetNews huggingface dataset:
From: barrett@decsws.enet.dec.com (Keith Barrett)
Newsgroups: comp.unix.amiga
Subject: High speed modem use under Amiga UNIX
Date: 27 Jul 92 15:14:48 GMT
Reply-To: barrett@pamsrc.enet.dec.com
Organization: Digital Equipment Corp.



	I recently purchased a 14.4k V.32/V.42bis modem.
Under AmigaDOS, this is working fine. Under Amiga UNIX I have this
working correctly for dial-out UUCP connections, but dial-in attempts
(for interactive shells or uucp) are failing to log in. What happens is
usually the systems posts the "Login:" prompt, but after entering your user-id
the password prompt never appears. Other times, it just plain hangs up.

These modems require setting your serial port baud usage to a high rate
(19.2 or more), and hardware handshaking. I highly suspect my problem lies
in my serial port settings (ttydefs).

I'm using entry 38400M (2.03 UNIX is suppose to work reliably at that rate,
and my problem-free dial-outs seem to confirm this). I've tried modifying it to
do a "-ixon -ixoff -ixany ctsxon rtsxoff", but this doesn't solve the problem.
I've also tried forcing the modem into doing a 9600 baud connection, and/or
various combinations of error correction and compression -- all produced the
same results (the modems always connected fine, but UNIX wasn't happy with
the usage). I've also tried the 19200M entry -- no difference.

Does anyone have this working? If so, what terminal settings should I be
using? What am I possibly missing? I'd like to get this working; especially
since some of my dial-in users are also local 14.4k modem sites. Perhaps
someone can post their /etc/ttydefs entry for this?

[BTW - My /Systems baud rate entries match the baud rate of the port,
as well as the /Devices file]

Thanks

Keith Barrett

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Statements expressed are solely mine   | Internet:   barrett@pamsrc.enet.dec.com
and do not represent any employer.     | UUCP:    ...!decwrl!pamsrc.enet!barrett
  // "My life is my own!" -The Prisoner| DDN: barrett%pamsrc.enet@decwrl.dec.com
\X/  Amiga 3000UXD: The Next Generation| Digital Equipment Corp./DECmessageQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: janc@amix.commodore.com (Jan Carlson)
Newsgroups: comp.unix.amiga
Subject: Re: AmigaUNIX 2.1 on A2000
Date: 24 Jul 92 23:18:59 GMT
Organization: Amiga UNIX Software Development

In article <1992Jul23.165759.2711@csdvax.csd.unsw.edu.au> 89u7491@csdvax.csd.unsw.edu.au writes:
>I have an A2000 with the GVP combo (68030 + SCSI controller) with 5 MEG fast
>RAM and 1 MEG chip and a 120 MEG HD. Can anyone give me some information on 
>setting unix up with this configuration (I realise that I will also need a tape
> drive). As fas as I know the A3000UX has some unix stuff in ROM, how does 
>an A2000 unix user get around this? 

Most 68030 accelerator boards that include the 68882 FPU chip and at
least 4mb of fast ram should be able to run AmigaUNIX.

You WILL need Kickstart 2.0 roms unless your accelerator is an A2620 or A2630.

Scsi controllers need AmigaUNIX drivers to run them.  Drivers for all
the Commodore scsi boards are built into the AmigaUNIX kernel.  Other
scsi controller manufacturers can write scsi drivers for AmigaUNIX.
AmigaUNIX allows adding drivers.

The A2091 should be useable even with other accelerator boards.
From: rhealey@kas.helios.mn.org (Rob Healey)
Newsgroups: comp.unix.amiga
Subject: Re: sysadm menu
Date: 30 Jul 92 13:51:09 GMT
Organization: Rob's home system, Hopkins, MN

In article <1992Jul22.223717.15030@bernina.ethz.ch> wild@nessie.cs.id.ethz.ch (Markus Wild) writes:
=I was browsing around /usr/sadm/sysadm, and found that in the add-ons
=directory, there are lots of help files, not normally available on the
=sysadm menu. After reading the sysadm man page, I guess those are pre-R4
=or `alien' help files (`alien' is not that probable, BNU's there as
=well). Now.. according to the manpage, those help files should be available
=under their own menu item on the main menu, however, they are not.
=
=This is under 2.03, is there a certain command that enables those 
=additional help files? They look nice, and I'd like at least try them
=out until I decide not to use them ;-))
=
	A few more are enabled under 2.1 but not all of them. Check out an
	Intel version of SVR4 and then add the missing or incomplete
	files... 2.1 gives access to the printer and FACE config menus. The
	backup/restore menus are still disabled because they are alot
	more complex and were removed by previous maintainers of AmigaUNIX
	who thought them either extraineous or stupid... B^(.

		-Rob
From: barnettj@pookie.crd.ge.com (Janet A Barnett)
Newsgroups: comp.unix.amiga
Subject: Re: X11R5 under AMIX
Date: 28 Jul 92 11:01:09 GMT
Organization: GE Corp. Research & Development, Schenectady, NY

In article <1992Jul27.204945.23041@cbfsb.cb.att.com> kmg@cbnewsg.cb.att.com (keith.gabryelski) writes:
>A public domain X11R5 port has been done to Amiga Unix and is on the
>standard distribution tape.  The monochrome X11R5 is working fine.
>UofLowell/DMI support has been added but isn't generally available.
>
>Pax, Keith
>-- 
>ag@monique.UUCP		Keith Gabryelski		kmg@usl.com

I've got a DMI board. What are the plans for UofLowell/DMI support?

Allen Barnett
(whose wife graciously allowed to use her account)
Newsgroups: comp.unix.amiga
From: miracle@sctc.com (Barry Miracle)
Subject: Amiga X-Terminal
Keywords: X-Terminal
Organization: SCTC
Date: Tue, 21 Jul 1992 20:20:00 GMT

I know about DNet, but I was wondering if anyone knows how to set up a
Amiga as a X-Terminal?

Barry Miracle
mirace@sctc.com
From: ericb@sierra.com (Eric Blood "intern")
Newsgroups: comp.unix.amiga
Subject: Re: Minix
Date: 22 Jul 92 19:19:41 GMT
Distribution: comp.unix.amiga
Organization: Sierra Geophysics Inc.,  Kirkland, Wa

In article <2940003@.grenoble.hp.com> gael@.grenoble.hp.com (Gael_MARZIOU) writes:
>>     Could someone tell me exactly what Minix for the Amiga is?  

>Be happy, you're not dreaming.
>Minix is an operating systems that has been written by Andrew Tanenbaum, Minix
>runs on PC, ATARI, SPARC, MAC and AMIGA.
>It's compatible with UNIX systems calls, some things are missing but as it comes
>with full sources you can add what you want (if you can :-)), typically, X11
>and networking is missing.
>Most of the GNU software has been ported. 
>You can try a limited demo on Fish #525 then you can purchase it from 
>Prentice hall for about 180 $US.
>Then you will have to update twice with free updates (1.5.10.1 and 1.5.10.2)
>available by anonymous ftp.
>With minix 1.5.10.2 you will have limited HD support, in fact it supports the 
>A590, A2091 and A3000 HD. Also this version runs on 68000, 68010, 68020 and 
>68030 processors.
>
>~ Gael Marziou          |  email : gael@hpgndl71.grenoble.hp.com              ~

The FAQ for Minix says that will only work on a 68000, not a 68020, or 68030.
Other things come up like there is no hard drive support out of the box,
you need to find a driver.  Without internet access, I would think that
would be difficult.  Also it is $168 US.  With that information, I bought
the version for my IBM.  I got it up and running, but would have prefered
the Amiga version for my A3000.  Now, is the FAQ correct or can I run
Minix with my A3000 and hard drive?

Eric V. Blood
ericb@sierra.com
Newsgroups: comp.unix.amiga
From: sangster@news.ans.net (Paul Sangster)
Subject: 2.1 Installation problems (take 2)
Date: Sat, 25 Jul 1992 18:42:44 GMT
Distribution: comp
Organization: Advanced Network & Services - Reston, VA


Well I wasn't able to stimulate much discussion with this problem last post,
so maybe with some additional info someone might be able to help me through
this nightmare install.

I have a 3000UX-D with an external Wangtek 150M tape drive and an extra
internal Maxtor LXT213S disk.  After paying the $$$$$$$ for the tape drive
and 2.1 upgrade package, I attempted to do the upgrade.  Primarily I was
just taking the default (to make things simple I thought) and just wanted
to install 2.1 over the existing 1.1 partition filesystems.

The install script made that an easy choice and proceeded smoothly through
the upgrade until the "Installing Amiga Unix Essential Component".  This
immediately follows the creating of the desired filesystem.  Everything
was going well for the first few minutes and then the nightmare began. 

a3091: 0x4F 1 0x78EAD98

After my last post, Jan sent me a reply and is trying to help work 
through this problem.  He indicated that the error is related to the SCSI
disk.  This seems likely since after the above error message the drive
light stays permanently light.  But I am installing on my original UXD
quantum hard drive (?).

Here are some clues:
1) Before trying this upgrade I was able to install all of the 1.1 
optional packages onto the Maxtor (under 1.1 of course).

2) I was able to tar to the tape drive to back my filesystems with no
problems (from the quantum).

3) Currently I have tried the following arrangements in hopes of another
clue becoming apparent.

+  I removed the Maxtor from the SCSI chain (no luck)
+  I hooked the tape drive up to the internal chain with no Maxtor (same)
+  I hit the side of the machine (suprisingly no luck)

Is it possible that I have a bad copy of the install tape? Anyone have
any options for me to try?

Sigh,

Paul
-- 
_______________________________________________________________________
Paul Sangster                        Snail mail: 1895 Preston White Dr. 
Advanced Network & Services                      Suite 310
Information & Applications Services Group        Reston, Va 22091
From: ford@yoda.uucp (Mike "Ford" Ditto)
Newsgroups: comp.unix.amiga
Subject: Re: 2.1 won't boot or load from A2091 with A2090A and ST-251
Date: 25 Jul 92 03:44:16 GMT
Reply-To: ford@yoda.uucp (Mike "Ford" Ditto)
Organization: Omnicron Data Systems
Keywords: multiple SCSI boot
Summary: "SCSI bus number" is important

In article <1992Jul23.143750.6202@infonode.ingr.com>
dave@xanadu.reston.ingr.com writes:
>After several days of experimentation (playing) with Unix without 
>incident, I put the 2090A back in so I could do some AmigaDos work.  
>I then tried to boot Unix again from the boot menu and got this:
>
>	S5mountroot VOP_OPEN
>	WARNING: nfs_mountroot called
>	PANIC: ufs_mountroot: cannot mount root: errno 89
>	(dump info)
>
>Even with the ST-251 disconnected from the 2090A, as long as the 2090A is
>plugged in, Unix Panics trying to boot from the 2091.

The Amiga Unix install software only scans the first SCSI bus for disk
devices.

When you have multiple SCSI busses on your system, they are numbered
by increasing autoconfig address order.  Since the system assigns
autoconfig addresses in the order that cards are found, and that is
determined by the hardware, there is a consistent and predictable
numbering of SCSI interface cards.  On an A2000 the slot closest to
the CPU is first.  On an A3000 the slot closest to the motherboard is
first.

The Unix kernel is stored in your boot partition with built-in
knowlege of which partition to mount as root.  For SCSI devices, this
is stored as a SCSI bus number, SCSI target ID, and partition number.

Therefore, you can not move a disk around between SCSI busses.  This
includes inserting another controller in a "lower" slot, since that
has the effect of renumbering the "higher" SCSI interface.

>Now, if the system failed to boot Unix at all, I could understand things
>little better.  That it partially boots from the 2091 with the 2090A 
>installed has me puzzled..

When you use the boot menu, you explicitly tell the boot code from
which SCSI bus, etc., to load the kernel.  But this does not tell the
kernel to use a SCSI bus/ID/partition other than the one it was
configured for.  You must make sure that your boot partition (and your
other partitions which are mounted automatically) remain at the same
SCSI bus/ID/partition numbers.

In conclusion, with the configuration you describe, your problems will
go away if you put the A2091 at a "lower" slot than the A2090.

					-=] Ford [=-

"The term most often used in this	(In Real Life:  Mike Ditto)
 manual is `implementation-defined'."	ford@yoda.uucp
 - SVR4 Programmer's Guide: POSIX	uunet!cbmvax!kenobi!ford
From: barrett@aminet.uucp (Keith Barrett)
Newsgroups: comp.unix.amiga
Subject: Re: Amiga X-Terminal
Keywords: X-Terminal
Date: 23 Jul 92 03:28:28 GMT
Reply-To: barrett%aminet@nuconvex.com
Distribution: usa
Organization: Waterbury USENET/UUCP
X-Copyright: (c) 1992 Keith Barrett; May be distributed freely, Not for sale
X-Disclaimer: Statements expressed are not representitive of any employer
X-NewsSoftware: XRN V6.17 Amiga UNIX SVR4

In article <1992Jul21.202000.4819@sctc.com>, miracle@sctc.com (Barry Miracle) writes:
>I know about DNet, but I was wondering if anyone knows how to set up a
>Amiga as a X-Terminal?


There are 2 basic ways.

1) If you are running Amiga UNIX and have an ethernet card, you
have all you need. Just start the X server locally, then start your
window manager (locally or remote), and X displays on the remote system.
You'll need a color board if you want color X. 

2) If you have AmigaDOS, you'll need GfxBASE's X window product, an
ethernet card, and either a TCP/IP software package or TSSnet (DECnet)
by Syndesis. This offers the advantage of 16 color X using the native
hardware, more screen resolution variations, the OpenLook Motif and TWM
window managers, and using DECnet or TCP/IP for the transport.


I do both, and they both work very well. I'm often torn between the
convience of using the b/w windows under UNIX (I run UNIX constantly,
but don't have a color board), or the more feature laden ADOS one
(color, scrollable screen, DECnet).

I connect to VAX/VMS stations using DECwindows -- works cool.

-kgb

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
UUCP: nuconvex.com!aminet!barrett             Keep circulating the tapes - MST3k
DDN: barrett%aminet.uucp@decwrl.dec.com    // My life is my own - the prisoner
Alternate: barrett@pamsrc.enet.dec.com   \X/  Amiga 3000UX - The Next Generation
--------------------------------------------------------------------------------
From: barnettj@pookie.crd.ge.com (Janet A Barnett)
Newsgroups: comp.unix.amiga
Subject: UNIX on a 2000 Redux
Summary: A FAQ probably
Date: 27 Jul 92 02:18:45 GMT
Organization: GE Corp. Research & Development, Schenectady, NY

I imagine this is a FAQ, but I just found this group, so here goes.

I would like to run Amix on my 2000. Though talks with various people
around the country, I've determined a few things: one needs an
accelerator with FPU, min. 4Mb memory, Commodore SCSI board, (immense)
harddisk and a tape drive. Am I missing anything?

I tried to order a 2091 and 240 Quantum SCSI disk. The tech at the
mail order house told me the Quantum did not work with the 2091. So,
is there another disk drive in the 200Mb ballpark that does work with
the 2091? (My local dealer's tech said rev. 7 of the 2091's ROM was
not yet released, but that it (perhaps) fixed this(?)) I also read in
comp.unix.amiga, here, that a SCSI driver comes on the distribution
tape. Will this effectively replace the ROM on the card and allow use
of the Quantum drive under UNIX (but not AmigaDOS)?

Thanks in advance.

Allen Barnett
(whose wife graciously allowed to use her account)
Newsgroups: comp.unix.amiga
From: crash@ckctpa.UUCP (Frank "Crash" Edwards)
Subject: Re: SCSI-2 drive works with A-3000?
Date: Tue, 21 Jul 1992 23:07:14 GMT
Distribution: usa
Reply-To: crash%ckctpa@tct.com (Frank "Crash" Edwards)
Organization: Edwards & Edwards Consulting

seanr@lobo.rmhs.colorado.edu (Sean Reifschneider) writes:
>Well, I've got Amiga UNIX on the way, and am looking to upgrade my Maxtor
>200MB drive to the new Fujitsu 520MB drive.  It's listed as a SCSI-2 drive
>so I was wondering if it would even work with the 3000s controller.  Some
>time ago I heard about an upgrade for the 3000 that would make it SCSI-2
>compatable.  Would I have to get one of those, and if I do, how much and
>where can I get it?

I thought the prior mention of SCSI-II in this group was regarding the
feasibility of dropping a newer Western Digital chip into the box in
place of the current SCSI-I chip.  That speaks nothing for the additional
engineering work (cabling, hookup, power, shielding, etc).

>Thanks,
>Sean
>(hoping his UNIX will be happy with 400MB. ;-)

Don't count on it.      :-)
-- 
Frank "Crash" Edwards            King Marine Electronics, Inc.
Home: 813/786-3675               Work: 813/530-3411
    "Chaka; when the walls fell."
From: barnettj@pookie.crd.ge.com (Janet A Barnett)
Newsgroups: comp.unix.amiga
Subject: Contents of Amiga UNIX package
Summary: What's in there?
Date: 27 Jul 92 02:41:03 GMT
Organization: GE Corp. Research & Development, Schenectady, NY

Could someone outline the contents of the Amiga UNIX package. I'd like
to know what kind of hardware it supports, what software is included,
and maybe a few details of how SysV.4 compares to something like SunOS
(things like sockets, job control and filename length limits
(<14chars?), for example). How much source code is included? What's
your typical page and swap space? Anything that might constitute
useful information on deciding whether this is for me.

As may be clear now, I am decidedly naive about this (having had only
a few years of experience with Sun machines and the Cray version of
UNIX) and any helpful information would be appreciated.

If you have the stamina to write extensively on these subjects, please
send e-mail.

Thanks in adavnce for any and all help.

Allen Barnett
(whose wife graciouly allowed to use her account)
From: ricks@odin.isc-br.com (Rick Schaeffer 99)
Newsgroups: comp.unix.amiga
Subject: Re: High speed modem use under Amiga UNIX
Date: 28 Jul 92 01:42:37 GMT
Organization: ISC-Bunker Ramo, An Olivetti Company

In article <1992Jul27.151448.5100@nntpd.lkg.dec.com> barrett@pamsrc.enet.dec.com writes:
>
>
>	I recently purchased a 14.4k V.32/V.42bis modem.
>Under AmigaDOS, this is working fine. Under Amiga UNIX I have this
>working correctly for dial-out UUCP connections, but dial-in attempts
>(for interactive shells or uucp) are failing to log in. What happens is
>usually the systems posts the "Login:" prompt, but after entering your user-id
>the password prompt never appears. Other times, it just plain hangs up.
>

I had similar problems getting a US Robotics V.32bis modem to work.  Finally
solved it with a combination of tricks.  The biggest problem with incoming
logins was with the modem "chattering" with the login program.  This
was fixed so that the modem only sends status messages (like OK, etc) when
in originate mode.  This is set in the USR by using "atq2e0" (you also
don't want echo on).  I had a lot of trouble using the port bi-directionally
and finally solved that by writing a new dialer script:
  USRV32  =,-,    "" ATQ0E0M1V1&M4\r OK\r\n \eATDT\T\r\c CONNECT

Lastly, you will want to program the modem so that it connects to the
computer at a FIXED rate.  I don't think there is a standard way to
do this...on the Robotics it is "at&b1" which causes the modem to stay
at the rate of the last outgoing call and you have to remember to
dial out manually at the baud rate you are going to run ttymon at.

Since making these changes, the modem has worked very well at 38400
baud...both incoming and outgoing.  I often run SLIP over it at
that rate with absolutely no problems.
--
Rick Schaeffer          UUCP:  uunet!isc-br.isc-br.com!ricks
ISC-Bunker Ramo                ricks@isc-br.isc-br.com
Box TAF-C8              Phone: (509)927-5114
Spokane, WA  99220      Home:  (509)928-3533
Newsgroups: comp.unix.amiga
From: sangster@news.ans.net (Paul Sangster)
Subject: Re: 2.1 Install problems
Date: Sat, 25 Jul 1992 20:37:39 GMT
Organization: Advanced Network & Services - Reston, VA
Followup-To:  sangster@ans.net

Ooops, I think I made a typo on my previous post.  The error message 
output during the installation of 2.1 is actually the following:

a3091: 0x49 1 0x78EAD98
          ^
This was mistakenly reported as an 'F'.  Actually it may have been
an 
'F' before I started trying different configurations, but now its a
'9'.  Does this give a better clue?

I have a Wangtek 5150ES with a #30559 board (although the label says
#30603-240).  I have heard that RP2 & RP3 are the DIP/SIP resistor
packs and they are in my board.  Anyone out there have a similar
configuration?

Thanks again,

Paul

-- 
_______________________________________________________________________
Paul Sangster                        Snail mail: 1895 Preston White Dr. 
Advanced Network & Services                      Suite 310
Information & Applications Services Group        Reston, Va 22091
Xref: sparky comp.unix.internals:1633 comp.unix.questions:9585
From: gram@aim1.aztec.co.za (Graham Wheeler)
Newsgroups: comp.unix.internals,comp.unix.questions
Subject: Re: Termio ioctls panicking system! Help!
Date: 30 Jul 92 13:14:02 GMT
Article-I.D.: aim1.gram.712502042
Organization: Aztec Information Management

urlichs@smurf.sub.org (Matthias Urlichs) writes:

>In comp.unix.internals, article <gram.712252068@aim1>,
>  gram@aim1.aztec.co.za (Graham Wheeler) writes:
>< 
>< I still would like to know why ldterm passes these ioctls on after I send
>< it a DO_CANON message from my driver. Also, although the system no longer

>It has to. Keep in mind that you also have to set the baud rate et al.
>There's no way to do this from a line discipline!

Yup, after carefully re-reading the ldterm docs I noticed that it does pass
the ioctl on. However, I still have a problem (as you would have noticed from
my other postings). The TCGETA ioctl that is passed to my driver has no 
attached buffer (that is, mp->b_cont is NULL). If I acknowledge this ioctl,
(and whether or not I actually allocate space for a termio structure myself),
my entire OS dies (no panic, just silence). I can understand it killing the
connection, or hanging that connection, but for the whole OS to just expire
is a bit excessive, IMHO.

In the case when I allocated a termio structure myself in a message
continuation block, I was still just filling this with zeros. Perhaps this
is enough to kill a UNIX system; if so, that is quite disturbing. I will
try this again and put in some more sensible values, particularly for the
c_cflag field, and see what happens - it could well work.

I will keep the net posted with my progress with this problem, as I think
it is of general interest to STREAMS users.

BTW, my postings in the last few days have been quite vitriolic at times.
This is a reflection of the frustration I have been feeling at being unable
to make any headway with these problems for the last two weeks. Don't get me
wrong; I think UNIX, and STREAMS, are great (I *did* ask my boss, in jest,
when we were going to go OS/2 ;-) ). I just think the STREAMS 
documentation has got a hell of a lot of room for improvement. It comes
across as a patchwork that has been added to as STREAMS has developed,
but actually should be rewritten from scratch so that one doesn't have to
be a detective to work out the finer points. I hope I haven't offended
anyone too much with my complaints.

Yours slightly mollified
Graham

-- 
Graham Wheeler                     | "That which is weak conquers the strong,
Software Systems Engineer/Student  | that which is soft conquers the hard."
Aztec Information Management/UCT   | 		Lao Tzu - Tao Te Ching Ch. 78
gram@aim1.aztec.co.za / gram@cs.uct.ac.za 
Newsgroups: comp.unix.internals